From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Kernel 2.6.26.5 -> 2.6.27.2 [USB REGRESSION] (USB -> D_STATE)
Date: Sun, 19 Oct 2008 07:26:23 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.1.10.0810190720210.26990@p34.internal.lan> (raw)
With kernel 2.6.27.2, any processes attempting to use USB hang and go into
D-state, I have never had a problem like this before until 2.6.27.2 (I
have not tried 2.6.27.1 or 2.6.27)
# lsusb -v
<hangs>
open("/dev/bus/usb", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY|O_CLOEXEC) = 3
fstat64(3, {st_mode=S_IFDIR|0755, st_size=140, ...}) = 0
getdents(3, /* 7 entries */, 4096) = 112
getdents(3, /* 0 entries */, 4096) = 0
close(3) = 0
open("/dev/bus/usb/001", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY|O_CLOEXEC) = 3
fstat64(3, {st_mode=S_IFDIR|0755, st_size=80, ...}) = 0
getdents(3, /* 4 entries */, 4096) = 64
open("/dev/bus/usb/001/004", O_RDWR) = 4
ioctl(4, USBDEVFS_CONNECTINFO
nut (for UPS) does not start.
nut 4078 0.0 0.0 1964 856 pts/8 D 07:09 0:00 /lib/nut/usbhid-ups -a belkin
root 4170 0.0 0.0 2204 1072 pts/8 D+ 07:11 0:00 lsusb -v
Processes go directly to D-state with 2.6.27.2 for USB.
Booting back to 2.6.26.5 now to see if everything works again.
Back to 2.6.25.5, everything works fine:
# lsusb
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 2040:7501 Hauppauge
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 050d:1100 Belkin Components
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 045e:0039 Microsoft Corp. IntelliMouse Optical
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Relevant configuration files and dmesg output:
http://home.comcast.net/~jpiszcz/2.6.25.5-usb-working.txt
http://home.comcast.net/~jpiszcz/2.6.27.2-usb-broken.txt
http://home.comcast.net/~jpiszcz/linux-2.6.25.5-config
http://home.comcast.net/~jpiszcz/linux-2.6.27.2-config
next reply other threads:[~2008-10-19 11:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-19 11:26 Justin Piszcz [this message]
2008-10-19 11:28 ` Kernel 2.6.26.5 -> 2.6.27.2 [USB REGRESSION] (USB -> D_STATE) Justin Piszcz
2008-10-19 15:34 ` Oliver Neukum
2008-10-19 16:51 ` Justin Piszcz
2008-10-20 14:02 ` Alan Stern
2008-10-20 15:21 ` Justin Piszcz
2008-10-20 16:17 ` Bug fix for pvrusb2 driver [was: Re: Kernel 2.6.26.5 -> 2.6.27.2 [USB REGRESSION] (USB -> D_STATE)] Alan Stern
2008-10-20 16:21 ` Mike Isely
2008-10-20 16:33 ` Justin Piszcz
2008-10-20 16:50 ` Mike Isely
2008-10-20 17:03 ` Justin Piszcz
2008-10-20 17:16 ` Alan Stern
2008-10-20 16:37 ` Mike Isely
2008-10-20 17:29 ` Greg KH
2008-10-20 18:01 ` Michael Krufky
2008-10-23 16:27 ` Mike Isely
2008-10-23 19:15 ` Greg KH
2008-10-23 19:54 ` Mike Isely
2008-10-23 22:04 ` Michael Krufky
2008-10-23 22:11 ` Justin Piszcz
2008-10-24 5:43 ` Mike Isely
2008-10-24 15:29 ` Michael Krufky
2008-10-24 21:30 ` Greg KH
2008-10-19 15:34 ` Kernel 2.6.26.5 -> 2.6.27.2 [USB REGRESSION] (USB -> D_STATE) Alan Stern
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.1.10.0810190720210.26990@p34.internal.lan \
--to=jpiszcz@lucidpixels.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;
as well as URLs for NNTP newsgroup(s).