On Wed, Feb 08, 2012 at 09:45:58AM +0000, Russell King - ARM Linux wrote: > On Tue, Feb 07, 2012 at 04:08:23PM -0800, Kevin Hilman wrote: > > Víctor M. Jáquez L. <vjaquez@xxxxxxxxxx> writes: > > > If it helps, I observed the same issue in a beagleboard rev B6, with > > > v3.3-rc2 > > > > Great, thanks. Can you share your ~/.config? > > If it helps, ARM Kautobuild V2 is up and running (assuming I don't break > the scripts again) at: > > http://www.arm.linux.org.uk/developer/build/ > > from where the build configs I use (and the exact ones used in those > compiles) are available. These aren't configs in arch/arm/configs. FYI, it now has one boot log for the 4430SDP, which is the only platform I've enabled so far, and it requires me to manually power up the board (so it's not going to happen for every build, which means the boot results will only be up there for a day until I can sort out a more automatic solution.) It's not too good at detecting boots that 'pass' rather than 'fail' - at the moment, it assumes it passed if it gets to the end of its script, so this needs to be found from the boot log. Currently, that means getting a login prompt. If anyone wants to develop a pcre regexp to detect oopses, warnings, panics and other failures - my current for the page generation are: errors: /^.*?\b(error|can't register|fail(ed)?)\b.*?$/mi warnings: /^.*?\bwarning\b.*?$/mi note that they operate on multi-line strings (hence the 'm' suffix and the use of non-greedy "*?" as opposed to the greedy "*"). Install pcre and see pcrepattern(3) for more information on pcre regexps if you're unfamiliar with these. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
