From: David Brownell <david-b@pacbell.net>
To: Norbert Preining <preining@logic.at>
Cc: linux-usb-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] 2.6.8-rc2-mm2 with usb and input problems
Date: Wed, 4 Aug 2004 19:26:31 -0700 [thread overview]
Message-ID: <200408041926.31293.david-b@pacbell.net> (raw)
In-Reply-To: <20040803081134.GA13745@gamma.logic.tuwien.ac.at>
On Tuesday 03 August 2004 01:11, Norbert Preining wrote:
> Then I tried lsusb, which hang, here is what sysrq-t says:
> lsusb D C0158CDC 0 3942 3849 (NOTLB)
> ...
> Call Trace:
> [<c0158cdc>] link_path_walk+0xa1f/0xd4e
> [<c02d3f5f>] __down+0x8b/0x116
> [<c0118cf9>] default_wake_function+0x0/0xc
> [<e08e0798>] usbdev_open+0x54/0xfa [usbcore]
> [<c02d4144>] __down_failed+0x8/0xc
> [<e08e26ba>] .text.lock.devio+0x5/0xff [usbcore]
> [<c014ba8b>] filp_open+0x4c/0x4e
> [<c014c62d>] vfs_read+0xa9/0xf5
> [<c014c846>] sys_read+0x38/0x59
> [<c0105e4f>] syscall_call+0x7/0xb
Not clear how to read that stack; if it's usbdev_open()
that's making the trouble, lock_kernel() is blocked.
But that doesn't quite make sense to me. Sorry!
- Dave
next prev parent reply other threads:[~2004-08-05 2:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-02 16:28 2.6.8-rc2-mm2 with usb and input problems Norbert Preining
2004-08-02 17:03 ` [linux-usb-devel] " David Brownell
2004-08-02 17:13 ` Norbert Preining
2004-08-03 8:11 ` Norbert Preining
2004-08-05 2:26 ` David Brownell [this message]
2004-08-05 6:51 ` Norbert Preining
2004-08-05 15:37 ` David Brownell
2004-08-10 17:18 ` Norbert Preining
2004-08-10 18:46 ` Alan Stern
2004-08-11 5:20 ` Norbert Preining
2004-08-03 0:08 ` Dmitry Torokhov
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=200408041926.31293.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=preining@logic.at \
/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