From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: linux-kernel@vger.kernel.org
Cc: linux-usb@vger.kernel.org, Alan Piszcz <ap@solarrain.com>
Subject: Re: 2.6.39.2: usb kernel panic/oops: schedule+ehci_irq+0x266/0x830
Date: Wed, 6 Jul 2011 04:15:25 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1107060412440.27258@p34.internal.lan> (raw)
In-Reply-To: <alpine.DEB.2.02.1107051742290.3983@p34.internal.lan>
On Tue, 5 Jul 2011, Justin Piszcz wrote:
> Hi,
>
> I plan to build a new machine in the future (one with console access) but in
> the meantime, after my PSU replacement, the host is still having issues, I've
> turned off bluetooth wireless (built into the DP55KG) and will see if it
> panics again, link the latest panic/oops/etc:
>
> http://home.comcast.net/~jpiszcz/20110705/IMG_2875.JPG
>
> schedule+0x266/0x830
> common_interrupt+0xe/0x13
> ehci_irq+0x20f/0x230
>
> Is this a valid kernel bug?
>
> I have another box (diff MOBO and all running 2.6.39.x no issues) but it does
> not have built-in bluetooth, I am also running a USB (non-winmodem) on this
> host as well, can anyone comment on this?
>
> 16: 70587 0 0 0 0 0 11675
> 0 IO-APIC-fasteoi ehci_hcd:usb1
>
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
> Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
> Bus 001 Device 003: ID 2001:f103 D-Link Corp. DUB-H7 7-port USB 2.0 hub
> Bus 001 Device 004: ID 0baf:0303 U.S. Robotics
> Bus 001 Device 005: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS
> Bus 001 Device 006: ID 413c:1002 Dell Computer Corp. Keyboard Hub
> Bus 001 Device 007: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
> Bus 001 Device 008: ID 413c:2002 Dell Computer Corp. SK-8125 Keyboard
> Bus 001 Device 009: ID 0461:4d15 Primax Electronics, Ltd Dell Optical Mouse
>
> I also use munin to poll the UPS for various information, could this be a bug
> in the USB driver for this chipset/motherboard?
>
> Can polling various USB devices, running a hylafax server, etc, cause a bug
> to pop up more easily in the USB subsystem vs. just using a keyboard for
> example, I assume so?
>
> Comments?
>
> Thanks.
>
> Justin.
>
Any thoughts on this error?
I've run 3 memtest passes and put the box under severe CPU / disk / I/O
load etc and there are no issues, but it appears when USB devices get
used, the kernel panics. Next test will probably be to remove all USB
devices and just use PS/2 and see if the problem goes away but I was
curious if anyone could comment on the that dump:
http://home.comcast.net/~jpiszcz/20110705/IMG_2875.JPG
As to what might be causing this otherwise? Thanks!
Memtest86 v4.20(latest): 3 passes, no problems:
http://home.comcast.net/~jpiszcz/20110706/IMG_2879.JPG
Justin.
next prev parent reply other threads:[~2011-07-06 8:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 21:51 Justin Piszcz
2011-07-06 8:15 ` Justin Piszcz [this message]
2011-07-06 13:46 ` Justin Piszcz
2011-07-06 14:41 ` Alan Stern
2011-07-06 20:14 ` Justin Piszcz
2011-07-06 20:38 ` Alan Stern
2011-07-06 14:40 ` Alan Stern
2011-07-06 20:14 ` Justin Piszcz
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=alpine.DEB.2.02.1107060412440.27258@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=ap@solarrain.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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
all inboxes | Powered by JetHome®