public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Guillaume Chazarain <guichaz@gmail.com>,
	linux-kernel@vger.kernel.org, Greg Kroah-Hartman <gregkh@suse.de>,
	Alan Stern <stern@rowland.harvard.edu>,
	Oliver Neukum <oliver@neukum.org>, Alan Ott <alan@signal11.us>,
	linux-usb@vger.kernel.org, linux-input@vger.kernel.org,
	Mat <jackdachef@gmail.com>, Andreas Bombe <aeb@debian.org>,
	Alex Riesen <raa.lkml@gmail.com>
Subject: Re: [BUG, Regression, bisected] USB mouse causes bug on 1st insert, ignored on 2nd insert, lsusb stuck at usbdev_open
Date: Mon, 20 Sep 2010 09:19:53 -0400	[thread overview]
Message-ID: <4C975F79.9060609@turmel.org> (raw)
In-Reply-To: <alpine.LNX.2.00.1009201440140.26813@pobox.suse.cz>

On 09/20/2010 08:42 AM, Jiri Kosina wrote:
> On Mon, 20 Sep 2010, Guillaume Chazarain wrote:
> 
>>> The USB mouse I use with my laptop is causing a BUG when inserted.  It works at that
>>> point, but if removed and re-inserted, it is ignored.  Also, after the 2nd insert,
>>> other USB devices (like my thumb drive) are also ignored.
>>>
>>> [   37.450777] BUG: unable to handle kernel NULL pointer dereference at (null)
>>> [   37.451148] IP: [<ffffffff817d0991>] hiddev_open+0xc1/0x220
>>> [   37.452036] PGD 1131a0067 PUD 113036067 PMD 0
>>> [   37.452924] Oops: 0000 [#1] PREEMPT SMP
>>> [   37.453336] last sysfs file: /sys/devices/platform/toshiba_acpi/backlight/toshiba/max_brightness
>>> [   37.453336] CPU 1
>>> [   37.453336] Modules linked in: tpm_infineon iwlagn iwlcore tifm_7xx1 tpm_tis toshiba_bluetooth toshiba_acpi tifm_core pcmcia sdhci_pci yenta_socket sdhci [last unloaded: scsi_wait_scan]
>>> [   37.453336]
>>> [   37.453336] Pid: 3117, comm: hald-probe-hidd Not tainted 2.6.36-rc4-00166-g151b6a5 #28 Portable PC/TECRA A9
>>> [   37.453336] RIP: 0010:[<ffffffff817d0991>]  [<ffffffff817d0991>] hiddev_open+0xc1/0x220
> 
> Could please those of you who are able to reproduce the problem (from a 
> quick test seems that I am not) use 'addr2line' utility to convert the RIP 
> value (ffffffff817d0991 in this case) to the line number inside of 
> hiddev_open(), so that we can see whether it's something behind 
> usbhid_find_interface() causing NULL pointer dereference, or whether it is 
> intfdata being NULL and thus going to hid->hiddev faults?

I couldn't quickly figure out how to recover the uncompressed kernel from
the vmlinuz (lzma) short of recompiling.  Here's the relevant section of System.map
if that's of any use....

# grep 'ffffffff817d0' /boot/System.map-2.6.36-rc4-00166-g151b6a5 
ffffffff817d0190 T usbhid_lookup_quirk
ffffffff817d02e0 T usbhid_quirks_exit
ffffffff817d0380 T usbhid_quirks_init
ffffffff817d05e0 t hiddev_lookup_report
ffffffff817d0690 t hiddev_write
ffffffff817d06b0 t hiddev_poll
ffffffff817d0720 t hiddev_usbd_probe
ffffffff817d0730 T hiddev_exit
ffffffff817d0750 T hiddev_disconnect
ffffffff817d07e0 t hiddev_fasync
ffffffff817d0800 t hiddev_release
ffffffff817d08d0 t hiddev_open
ffffffff817d0af0 t hiddev_ioctl_string
ffffffff817d0c70 t hiddev_ioctl_usage

If there's a tool to expand vmlinuz => vmlinux, I love to hear about it.  If you
need me to recompile to get what you need, I can do that.

> (sticking two printk()s in there should do the same as well).

If you give me a patch with exactly the debug stuff you want, I can compile that instead.

Unfortunately, I have some work to do later today that I have to boot this box into Windows
for (CADD), so my compiling and testing window is narrow (until tomorrow).

Phil

  reply	other threads:[~2010-09-20 13:20 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-20  1:33 [BUG, Regression, bisected] USB mouse causes bug on 1st insert, ignored on 2nd insert, lsusb stuck at usbdev_open Phil Turmel
2010-09-20  9:43 ` Guillaume Chazarain
2010-09-20 10:47   ` Phil Turmel
2010-09-20 12:42   ` Jiri Kosina
2010-09-20 13:19     ` Phil Turmel [this message]
2010-09-20 13:25       ` Jiri Kosina
2010-09-20 13:56         ` Mat
2010-09-20 15:10           ` Jiri Kosina
2010-09-20 17:05             ` Mat
2010-09-20 17:40             ` Phil Turmel
2010-09-21 12:31               ` Jiri Kosina
2010-09-21 13:57                 ` Jiri Kosina
2010-09-21 14:48                   ` Heinz Diehl
2010-09-21 14:55                     ` Jiri Kosina
2010-09-21 14:30                 ` Alan Stern
2010-09-21 14:40                   ` Jiri Kosina
2010-09-21 14:42                     ` Phil Turmel
2010-09-21 14:54                   ` Phil Turmel
2010-09-21 16:08                     ` Gabriel C
2010-09-22  9:47                       ` Mat
2010-09-24 16:46                         ` Greg KH
2010-09-21 16:50                   ` Greg KH
2010-09-21 16:55                     ` Jiri Kosina
2010-09-21 17:07                       ` Greg KH
2010-09-21 17:14                         ` Jiri Kosina
2010-09-20 20:55             ` Alan Stern
2010-09-20 22:48               ` Jiri Kosina
2010-09-21  0:41                 ` Andreas Bombe
2010-09-20 14:11         ` Phil Turmel
2010-09-20 19:35 ` Maciej Rutecki

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=4C975F79.9060609@turmel.org \
    --to=philip@turmel.org \
    --cc=aeb@debian.org \
    --cc=alan@signal11.us \
    --cc=gregkh@suse.de \
    --cc=guichaz@gmail.com \
    --cc=jackdachef@gmail.com \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=oliver@neukum.org \
    --cc=raa.lkml@gmail.com \
    --cc=stern@rowland.harvard.edu \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox