From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Alan Stern" <stern@rowland.harvard.edu>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
linux-usb-devel@lists.sourceforge.net,
"Greg Kroah-Hartman" <gregkh@suse.de>
Subject: Re: Problem: irq 217: nobody cared + backtrace
Date: Fri, 4 Aug 2006 16:36:33 +0200 [thread overview]
Message-ID: <9a8748490608040736n5c9ea078x79f4ce56b613703a@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0608031158560.7384-100000@iolanthe.rowland.org>
On 03/08/06, Alan Stern <stern@rowland.harvard.edu> wrote:
>
> Has this happened more than once?
Seems to happen consistently after ~100000 interrupts.
> In case it happens again, here's how
> you can get more information. Turn on CONFIG_USB_DEBUG and
> CONFIG_DEBUG_FS, and mount a debugfs filesystem somewhere (say
> /sys/kernel/debug). Then after the problem occurs, save a copy of
>
> /sys/kernel/debug/uhci/0000:00:1d.1
>
# cat /sys/kernel/debug/uhci/0000:00:1d.1
Root-hub state: auto-stopped FSBR: 0
HC status
usbcmd = 0048 Maxp32 CF EGSM
usbstat = 0020 HCHalted
usbint = 0002
usbfrnum = (1)160
flbaseadd = 37428160
sof = 40
stat1 = 0080
stat2 = 0080
Most recent frame: 458 (88) Last ISO frame: 458 (88)
> That will indicate whether the UHCI controller thinks it is sending an
> interrupt request.
>
And just for completenes, here's the backtrace I got just before
saving the above info :
irq 217: nobody cared (try booting with the "irqpoll" option)
[<c0103a3c>] show_trace_log_lvl+0x152/0x165
[<c0103a5e>] show_trace+0xf/0x13
[<c0103b59>] dump_stack+0x15/0x19
[<c013846e>] __report_bad_irq+0x24/0x7f
[<c0138552>] note_interrupt+0x6b/0xd5
[<c0137ca8>] __do_IRQ+0xf4/0x100
[<c01050a1>] do_IRQ+0x95/0xbc
[<c0103502>] common_interrupt+0x1a/0x20
[<c0137b7e>] handle_IRQ_event+0x20/0x56
[<c0137c4c>] __do_IRQ+0x98/0x100
[<c01050a1>] do_IRQ+0x95/0xbc
[<c0103502>] common_interrupt+0x1a/0x20
[<c0100e64>] mwait_idle+0x30/0x35
[<c0100d45>] cpu_idle+0x78/0x81
[<c04cc7fb>] start_kernel+0x173/0x19d
[<c0100210>] 0xc0100210
DWARF2 unwinder stuck at 0xc0100210
Leftover inexact backtrace:
=======================
handlers:
[<c02c5c22>] (usb_hcd_irq+0x0/0x53)
Disabling IRQ #217
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2006-08-04 14:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 14:17 Jesper Juhl
2006-08-03 16:08 ` Alan Stern
2006-08-04 14:36 ` Jesper Juhl [this message]
2006-08-04 15:54 ` Alan Stern
2006-08-04 22:40 ` Jesper Juhl
2006-08-05 14:48 ` Alan Stern
2006-08-04 16:23 ` Sergio Monteiro Basto
2006-08-07 20:52 ` Sergio Monteiro Basto
2006-08-04 15:33 ` Sergio Monteiro Basto
2006-08-04 17:33 ` Greg KH
[not found] <Pine.LNX.4.44L0.0608041309360.7905-100000@iolanthe.rowland.org>
2006-08-07 1:54 ` Sergio Monteiro Basto
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=9a8748490608040736n5c9ea078x79f4ce56b613703a@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--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
all inboxes | Powered by JetHome®