On Thu, Dec 24, 2009 at 02:04:25PM +0100, Peter Palfrader wrote: > On Tue, 22 Dec 2009, Peter Palfrader wrote: > > > On Tue, 22 Dec 2009, Peter Palfrader wrote: > > > > > > If that doesn't help perhaps disable CONFIG_HID_GYRATION, > > > > but from your other oops something more seems to be broken anyways. > > > > > > This is a static kernel - no module support. Anyway, I also tried > > > without CONFIG_USB_HID (which pulls in all the other HID_* things) but > > > no luck. > > > > However, disabling all of HID (CONFIG_HID_SUPPORT=n) makes the system > > boot (Previously HID, HIDRAW and HID_SUPPORT were still enabled). It's suspicious if you don't have such devices, that would point to something being confused in the driver probing layer. > > However, I still see panics on boot occassionally, tho not so often or > reproducible. So far only on dl385 (opteron) systems. Multiple systems and the same oopses? > > And all of the backtraces go through sysfs_new_dirent() near the top. Please post full oopses. -Andi -- ak@xxxxxxxxxxxxxxx -- Speaking for myself only. -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
