From: Ondrej Zary <linux@rainbow-software.org>
To: Oliver Neukum <oliver@neukum.org>
Cc: Alan Stern <stern@rowland.harvard.edu>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: debugging oops after disconnecting Nexio USB touchscreen
Date: Thu, 3 Dec 2009 10:30:21 +0100 [thread overview]
Message-ID: <200912031030.22460.linux@rainbow-software.org> (raw)
In-Reply-To: <200912021042.04557.oliver@neukum.org>
On Wednesday 02 December 2009, Oliver Neukum wrote:
> Am Mittwoch, 2. Dezember 2009 09:52:08 schrieb Ondrej Zary:
> > It shows "prev is NULL, qh=f6581080, ehci->async=f6581000".
> >
> > The problem is that activating usbmon causes the problem to disappear. No
> > errors in maybe 15 attempts. It appeared on 2nd attempt after unloading
> > usbmon.
>
> That suggests a use after free bug, which usbmon prevents holding
> an additional reference.
> Are you using SLAB_DEBUG?
Just tried 2.6.32-rc8-next-20091202 with SLAB_DEBUG enabled and got this:
BUG: unable to handle kernel paging request at 6b6b6b6b
IP: [<f7c649a3>] qh_completions+0x6c/0x400
Call Trace:
lapic_next_event
ehci_work
tick_dev_program_event
tick_program_event
hrtimer_interrupt
ehci_watchdog+0x0/0x37
ehci_watchdog+0x2b/0x37
run_timer_softirq
__do_softirq
irq_exit
do_IRQ
common_interrupt
acpi_idle_enter_bm
cpuidle_idle_call
cpu_idle
start_kernel
Code: 00 00 00 00 3c 03 88 44 24 1f 0f 94 c0 81 ea ec 00 00 00 0f b6 c0 89 44
24 14 89 14 24 8b 46 0c 31 db bd 8d ff ff ff c6 46 28 00 <8b> 08 89 4c 24 10
e9 ec 02 00 00 83 e8 38 85 db 89 44 24 24 8b
--
Ondrej Zary
next prev parent reply other threads:[~2009-12-03 9:30 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-27 13:38 debugging oops after disconnecting Nexio USB touchscreen Ondrej Zary
2009-11-27 18:19 ` Alan Stern
2009-11-30 15:30 ` Ondrej Zary
2009-11-30 20:19 ` Alan Stern
2009-12-01 10:06 ` Ondrej Zary
2009-12-01 15:11 ` Alan Stern
2009-12-02 8:52 ` Ondrej Zary
2009-12-02 9:42 ` Oliver Neukum
2009-12-03 9:30 ` Ondrej Zary [this message]
2009-12-02 15:58 ` Alan Stern
2009-12-03 12:31 ` Ondrej Zary
2009-12-03 19:39 ` Alan Stern
2009-12-03 20:55 ` Ondrej Zary
2009-12-03 22:22 ` Alan Stern
2009-12-04 12:22 ` Ondrej Zary
2009-12-04 15:47 ` Alan Stern
2009-12-04 19:17 ` Ondrej Zary
2009-12-04 19:34 ` Alan Stern
2009-12-04 19:55 ` Ondrej Zary
2009-12-04 21:24 ` Alan Stern
2009-12-07 9:02 ` Ondrej Zary
2009-12-07 15:22 ` Alan Stern
2009-12-08 9:03 ` Ondrej Zary
2009-12-08 15:03 ` Alan Stern
2009-12-08 15:21 ` Ondrej Zary
2009-12-07 15:07 ` Ondrej Zary
2009-12-07 16:02 ` Alan Stern
2009-12-10 15:40 ` Ondrej Zary
2009-12-10 20:38 ` Alan Stern
2009-12-11 19:42 ` Ondrej Zary
2009-12-11 20:49 ` Alan Stern
2009-12-05 7:36 ` Andreas Mohr
2009-12-05 17:16 ` Alan Stern
2009-12-06 11:38 ` Andreas Mohr
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=200912031030.22460.linux@rainbow-software.org \
--to=linux@rainbow-software.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oliver@neukum.org \
--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