On Sun, Apr 7, 2013 at 12:53 AM, Peter Butler <pbut...@pt.com> wrote: > OK setting SUBARCH did the trick. Thanks for that. :-)
Can you do a git bisect between 3.8 and 3.9-X to find the evil doer? You'll get the credit. :-) > Here's the output from a crash using the associated build. Too several > boots to trigger the crash - probably some sort of a race condition. Note > that I am doing nothing other than booting up the UML to trigger the crash > (that is, I am not doing anything at the command line). If no crash > occurs I simply do a graceful shutdown and then start it up again (in > order to trigger a crash). In this particular case the crash actually > occurred during the shutdown and triggered this bug: > > BUG: scheduling while atomic: systemd-logind/485/0x00000001 > > Here's the full output: > > bash $ ./linux ubd0=Fedora18-AMD64-root_fs rw mem=4096M con0=fd:0,fd:1 What it your host kernel? At least here on my Laptop (v3.7.x x86_64) I cannot reproduce this. (Also fc18 also guest, same cmd line...) I fear it has to do something with the host side. Toralf saw related crash. Thanks, //richard ------------------------------------------------------------------------------ Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html _______________________________________________ User-mode-linux-devel mailing list User-mode-linux-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
