[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <200702220538.39341.vinctre@videotron.ca>
Date: Thu, 22 Feb 2007 05:38:39 -0500
From: Veronique & Vincent <vinctre@...eotron.ca>
To: Pete Zaitcev <zaitcev@...hat.com>, Jiri Kosina <jikos@...os.cz>
Cc: marcel@...tmann.org, vincent.fortier1@...gc.ca,
linux-kernel@...r.kernel.org
Subject: Re: Boot time Bluetooth BUG: warning: (value > m) at hid-core.c:793
>
> > > I've set up the hid-core.c to DEBUG mode... and it literally got pretty
verbose...
>
> > thanks for the output. Is this really the full output? The important part
> > - report descriptor dump - seems to be missing in the output (it should
> > read something like "hid-core.c: report descriptor (size XY, read YZ) =
> > ... some hexadecimal numbers". This should be output by the time the HID
> > device is connected.
The full dmesg with define DEBUG was included in the original message. Unless
something else was needed?
> Can I get something useful without a kernel recompile, with something
> like evtest? I have users on Fedora hitting this too. It very likely is
> a regression caused by the new unified HID.
I was actually getting that on a stock FC6 kernel. The dmesg output comes
from a recompiled vanilla 2.6.19.x with the exact same configuration BUT the
modified define's in hid-core.c and a local version appended to the .config
file. So this BUG does not only affect FC6 users but also the vanilla
kernel.
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=227598
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=228755
Good thing, I've added myself to the CC list of both.
>
> -- Pete
>
- vin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists