On 12/22/2011 04:46 PM, fred smith wrote:
On Wed, Dec 21, 2011 at 08:30:23PM -0700, Corey Henderson wrote:
On 12/21/2011 8:23 PM, fred smith wrote:
<snip> > > If you come up empty (all the same kernel modules exist in both) then > it's likely a bug in some kernel module. The "emergency_shell" part of > dracut may be useful in debug this. When you reboot, during the grub > menu, add this to the kernel's command line: > > rdbreak=cmdline > > During the boot process, you'll get dropped to a command line, and can > run some of the basic commands provided intisde the initramfs. > > If you look at the "init" file inside the initramfs, you can see the > different points you'll end up with with different arguments to rdbreak; > ie, pre-udev, initqueue, etc.
Having gotten nowhere, so far, I tried the above. I haven't any clue what would be helpful to do when it hits a "breakpoint", but I just typed "exit" to drop back out of the shell, a couple of times. it eventually got to where it said "starting udev" then a few seconds later the dump appeard on the screen again. but there seemed to be more of it shown so I took a photo of it. If you feel like taking a look to see if you can figure it out, you can find it at:
http://users.rcn.com/fredricksmith/dump.jpg
I don't know what any of it means, except that it mentions modprobe, and it appears that the stack trace has something to do with sound, perhaps modprobe croaks when loading/munging drivers for sound.
If anyone of you can make more sense of it than I, I'd appreciate the help.
There is a new kernel building right now that might fix something ... though I do not see anything specifically about your cpu.
Here is the errata link:
http://rhn.redhat.com/errata/RHSA-2011-1849.html
If everything builds it should be released in a couple of hours.