From: Stephan von Krawczynski <skraw@ithnet.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: USB lockup in 2.4.18-pre8
Date: Tue, 14 May 2002 18:05:26 +0200 [thread overview]
Message-ID: <20020514180526.4b1691a0.skraw@ithnet.com> (raw)
Hello,
beginning with 2.4.18-pre7 I notice a complete system lockup using a SANDISK
SDDR-05 compactflash USB adapter.
I used the device in earlier kernel versions with the "UHCI Alternate Driver",
but in 2.4.18-pre7 I experienced a complete system lockup when mounting the
flash card. So I switched over to "UHCI (Intel ..." device, which worked ok in
2.4.18-pre7.
Unfortunately starting with 2.4.18-pre8 I had to find out that now both
UHCI-drivers produce the lockup. Since I did not find any hints in lkml from
others I thought it might be worth dropping a note...
I am willing to try out whatever is necessary.
Regards,
Stephan
some system infos:
00:04.2 USB Controller: VIA Technologies, Inc. UHCI USB (rev 16)
00:04.3 USB Controller: VIA Technologies, Inc. UHCI USB (rev 16)
May 3 13:40:44 admin kernel: usb.c: registered new driver usbdevfs
May 3 13:40:44 admin kernel: usb.c: registered new driver hub
May 3 13:40:44 admin kernel: usb-uhci.c: $Revision: 1.275 $ time 13:31:52 May 3 2002
May 3 13:40:44 admin kernel: usb-uhci.c: High bandwidth mode enabled
May 3 13:40:44 admin kernel: usb-uhci.c: USB UHCI at I/O 0xd400, IRQ 5
May 3 13:40:44 admin kernel: usb-uhci.c: Detected 2 ports
May 3 13:40:44 admin kernel: usb.c: new USB bus registered, assigned bus number 1
May 3 13:40:44 admin kernel: hub.c: USB hub found
May 3 13:40:44 admin kernel: hub.c: 2 ports detected
May 3 13:40:44 admin kernel: usb-uhci.c: USB UHCI at I/O 0xd000, IRQ 5
May 3 13:40:44 admin kernel: usb-uhci.c: Detected 2 ports
May 3 13:40:44 admin kernel: usb.c: new USB bus registered, assigned bus number 2
May 3 13:40:44 admin kernel: hub.c: USB hub found
May 3 13:40:44 admin kernel: hub.c: 2 ports detected
May 3 13:40:44 admin kernel: usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
May 3 13:40:44 admin kernel: hub.c: USB new device connect on bus1/1, assigned device number 2
May 3 13:40:44 admin kernel: usb.c: USB device 2 (vend/prod 0x781/0x1) is not claimed by any active driver.
May 3 13:40:44 admin kernel: Initializing USB Mass Storage driver...
May 3 13:40:44 admin kernel: usb.c: registered new driver usb-storage
May 3 13:40:44 admin kernel: scsi3 : SCSI emulation for USB Mass Storage devices
May 3 13:40:44 admin kernel: Vendor: Model: Rev:
May 3 13:40:44 admin kernel: Type: Direct-Access ANSI SCSI revision: 02
May 3 13:40:44 admin kernel: Attached scsi removable disk sdb at scsi3, channel 0, id 0, lun 0
May 3 13:40:44 admin kernel: usb-uhci.c: interrupt, status 3, frame# 1433
May 3 13:40:44 admin kernel: Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
May 3 13:40:44 admin kernel: sdb : READ CAPACITY failed.
May 3 13:40:44 admin kernel: sdb : status = 1, message = 00, host = 0, driver = 08
May 3 13:40:44 admin kernel: Current sd00:00: sns = 70 2
May 3 13:40:44 admin kernel: ASC=3a ASCQ= 0
May 3 13:40:44 admin kernel: Raw sense data:0x70 0x00 0x02 0x00 0x00 0x00 0x00 0x08 0x00 0x00 0x00 0x00 0x3a 0x00 0x00 0x00
May 3 13:40:44 admin kernel: sdb : block size assumed to be 512 bytes, disk size 1GB.
May 3 13:40:44 admin kernel: sdb: I/O error: dev 08:10, sector 0
May 3 13:40:44 admin kernel: I/O error: dev 08:10, sector 0
May 3 13:40:44 admin kernel: unable to read partition table
May 3 13:40:44 admin kernel: WARNING: USB Mass Storage data integrity not assured
May 3 13:40:44 admin kernel: USB Mass Storage device found at 2
May 3 13:40:44 admin kernel: USB Mass Storage support registered.
next reply other threads:[~2002-05-14 16:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-14 16:05 Stephan von Krawczynski [this message]
2002-05-14 15:14 ` USB lockup in 2.4.18-pre8 Greg KH
2002-05-14 16:17 ` USB lockup in 2.4.18-pre8 <-- typo 2.4.19-pre8 Stephan von Krawczynski
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=20020514180526.4b1691a0.skraw@ithnet.com \
--to=skraw@ithnet.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.