Since the 3.x kernel (afaicr) the kernel panics occassionally on boot. No trace is left in messages(/var/log/dmesg). The debug output says that there is a NULL pointer dereferenciation when starting the Plymouth graphical boot screen. Now here comes a screen shot:
Interesting, since I have booted 3.4.6-1.1-desktop with nomodeset (All the KMS related stuff is still bleeding edge; at me KMS does not work at all at the moment (regression): https://bugzilla.novell.com/show_bug.cgi?id=776569).
uploaded image: www.elstel.com/uploads/kernel-oops/kernel_panic_20120824_100717.jpg, www.elstel.org/uploads/kernel-oops/kernel_panic_20120824_100717.jpg (please try next day; not accessible at the moment.)
Please attach the screenshot to the bug so it doesn't get lost
Created attachment 78471 [details] better compressed screenshot
Thanks - stupid bug in the ite remote control driver, enabling interrupts before registering the device. Which as you say would give panics some of he time but not others. Commit 9ef449c6b31bb6a8e6dedc24de475a3b8c79be20 doesn't move it far enough
Created attachment 78481 [details] Fix ISR registration The attached patch has been compile-tested only, but it should do the trick. As Alan pointed out, commit 9ef449c6b31bb6a8e6dedc24de475a3b8c79be20 didn't moved the ISR registration far enough. Please let me know if this solves the problem. I'll be sending this patch for review to lkml as well.
Created attachment 78491 [details] Fix ISR registration V2 Ugh! Please ignore the previous patch, I attached the wrong version. Previous patch was the untested one (it didn't compile)
seems resolved for newer kernels.