LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jiri Kosina <jikos@jikos.cz>
To: Veronique & Vincent <vinctre@videotron.ca>
Cc: Pete Zaitcev <zaitcev@redhat.com>,
	marcel@holtmann.org, vincent.fortier1@ec.gc.ca,
	linux-kernel@vger.kernel.org
Subject: Re: Boot time Bluetooth BUG: warning: (value > m) at hid-core.c:793
Date: Thu, 22 Feb 2007 11:46:34 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.64.0702221139500.10496@twin.jikos.cz> (raw)
In-Reply-To: <200702220538.39341.vinctre@videotron.ca>

On Thu, 22 Feb 2007, Veronique & Vincent wrote:

> > > - 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?

Unfortunately it was missing the report descriptor dump. The output should 
look like

drivers/usb/input/hid-core.c: report descriptor (size 59, read 59) = 05 01 
09 06 a1 01 05 07 19 e0 29 e7 15 00 25 01 75 01 95 08 81 02 81 03 95 05 05 
08 19 01 29 05 91 02 95 01 75 03 91 01 95 06 75 08 15 00 26 a4 00 05 07 19 
00 2a a4 00 81 00 c0

and it should appear as soon as you connect the device. If it didn't, I 
suspect that the 

	#define DEBUG_DATA

was not set properly in drivers/usb/input/hid-core.c (only defining DEBUG 
is not enough for report descriptor dump to appear).

> 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.

But so far all reports that have gathered for this bug at me seem to come 
from FC6 ... does hid2hci by any chance in FC6 have any additional patches 
that could be causing it, instead of being a kernel issue?

Thanks,

-- 
Jiri Kosina

  reply	other threads:[~2007-02-22 10:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-20  2:11 Fwd: " Veronique & Vincent
2007-02-20  8:02 ` Jiri Kosina
2007-02-22  2:50   ` Pete Zaitcev
2007-02-22  8:04     ` Jiri Kosina
2007-02-22 10:38     ` Veronique & Vincent
2007-02-22 10:46       ` Jiri Kosina [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-03-05 19:19 Amedee Van Gasse
2007-03-05 21:54 ` Jiri Kosina
     [not found]   ` <1173191358.9292.4.camel@saruman>
2007-03-06 14:44     ` Jiri Kosina
2007-03-23  9:15 ` Jiri Kosina
2007-02-16 12:03 [KJ][PATCH] is_power_of_2 in ia64mm Vignesh Babu BM
2007-02-16 15:02 ` [KJ] [PATCH] " Richard Knutsson
2007-02-16 15:27   ` Boot time Bluetooth BUG: warning: (value > m) at hid-core.c:793 Fortier,Vincent [Montreal]
2007-02-18 21:23     ` Jiri Kosina
2007-02-19  0:25       ` Marcel Holtmann
2007-02-19  9:36         ` Jiri Kosina
2007-02-27 15:54         ` Jiri Kosina
2007-02-27 16:12           ` Fortier,Vincent [Montreal]
     [not found]             ` <Pine.LNX.4.64.0702271713220.10496@twin.jikos.cz>
2007-02-27 20:35               ` Fortier,Vincent [Montreal]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.64.0702221139500.10496@twin.jikos.cz \
    --to=jikos@jikos.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=vincent.fortier1@ec.gc.ca \
    --cc=vinctre@videotron.ca \
    --cc=zaitcev@redhat.com \
    --subject='Re: Boot time Bluetooth BUG: warning: (value > m) at hid-core.c:793' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).