![]() | |||||||||||||
Messages in this thread |
On Tue, 2003-06-10 at 09:19, Martin Schlemmer wrote: > > On Tue, 2003-06-10 at 08:54, Greg KH wrote: > > > On Tue, Jun 10, 2003 at 07:58:10AM +0200, Martin Schlemmer wrote: > > > > Hi > > > > > > > > I am getting the following during mouse/keyboard is initialized, > > > > but it seems to be more specific to the mouse. Both are USB. > > > > It was fine with last 2.5.69 kernel, but started when i switched > > > > to 2.5.70-bk12 (have not tried vanilla, or earlier 2.5.70 bk's, > > > > as swamped at work). NB: there are no oops 'header'. > > > > > > > > ------------- > > > > Trace; c01a9466 <kobject_get+4c/4e> > > > > Trace; c0201830 <get_device+18/21> > > > > Trace; c0203001 <class_device_add+132/137> > > > > Trace; c0202ec2 <class_device_initialize+16/23> > > > > > > You are hitting the WARN_ON() call in kobject_get(), this isn't a oops. > > > > > > But what is wierd is the calls to class_* for a USB mouse, as I don't > > > think there are any mouse class code in the current kernel. Does your > > > mouse show up under /sys/class anywhere? > > > > > Ok was slightly wrong. It is during init of the USB keyboard, and yes, it is under /sys/class/. I will try to have a look, but currently trying to find out how to get my sensors working. Regards, -- Martin Schlemmer - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2005-03-22 12:36 [W:0.556 / U:0.000 seconds] ©2003-2008 Jasper Spaans | |||||||||||||