I'm getting this too, running 2.6.24-12.22. On my laptop, it's starting hal that kills it; everything up to then works fine. I've reproduced this by booting with init=/bin/bash, starting dbus, then starting hal. Unfortunately, I can never scroll back far enough to get the initial error.
The earliest errors I can scroll back to go something like this: (transcribed from photo) --- kernel BUG at /build/buildd/linux-2.6.24/debian/build/custom-source-xen/arch/x86/mm/highmem_32-xen.c:42! invalid opcode: 0000 [#9] SMP Modules linked in: [...] --- We then get into lots of this: --- Fixing recursive fault but reboot is needed! BUG: scheduling while atomic: hald/5345/0x00000002 Pid: 5345, comm: hald Tainted: G D 2.6.24-12-xen #1 [<c030e3b8>] schedule+0x318/0x640 [<c01291c0>] do_exit+0x770/0x8b0 [<c0125e8b>] printk+0x1b/0x20 [<c0106397>] die+0x287/0x290 [... see attached photos for rest of the trace ...] --- I have 5 photos which together show that trace in its entirety, if needed. ** Attachment added: "IMG_0109.JPG" http://launchpadlibrarian.net/12891036/IMG_0109.JPG -- crash on start in xen 3.2 https://bugs.launchpad.net/bugs/196571 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
