From: Tobias Klauser <tklauser@access.unizh.ch>
To: linux-hotplug@vger.kernel.org
Subject: Re: usb multicard reader problems
Date: Sat, 16 Apr 2005 16:10:30 +0000 [thread overview]
Message-ID: <20050416161030.GA769@neon> (raw)
In-Reply-To: <4212FDE6000C59D9@mail-5.tiscali.it>
Please keep it on the list.
On Sat, Apr 16, 2005 at 01:01:39PM +0200, ziettopeu@tiscali.it wrote:
> read below the log pasted:
> Apr 14 21:32:33 localhost kernel: SCSI device sdc: 253952 512-byte hdwr sectors
> (130 MB)
> Apr 14 21:32:33 localhost kernel: sdc: Write Protect is off
> Apr 14 21:32:33 localhost kernel: sdc: assuming drive cache: write through
> Apr 14 21:32:33 localhost kernel: sdc: sdc1
> Apr 14 21:32:33 localhost kernel: Attached scsi removable disk sdc at scsi7,
> channel 0, id 0, lun 0
> Apr 14 21:32:33 localhost scsi.agent[5186]: disk at /devices/pci0000:00/0000:00:02.2/usb1/1-6/1-6:1.0/host7/7:0:0:0
> Apr 14 21:32:34 localhost fstab-sync[5277]: added mount point /media/usbdisk1
> for /dev/sdc1
> Apr 14 21:32:39 localhost kernel: sdc : READ CAPACITY failed.
> Apr 14 21:32:39 localhost kernel: sdc : status=0, message\0, host=7, driver\0
>
> Apr 14 21:32:39 localhost kernel: sdc : sense not available.
> Apr 14 21:32:39 localhost kernel: sdc: Write Protect is off
> Apr 14 21:32:39 localhost kernel: sdc: assuming drive cache: write through
> Apr 14 21:32:39 localhost kernel: sdc : READ CAPACITY failed.
> Apr 14 21:32:39 localhost kernel: sdc : status=0, message\0, host=7, driver\0
>
> Apr 14 21:32:39 localhost kernel: sdc : sense not available.
> Apr 14 21:32:39 localhost kernel: sdc: Write Protect is off
> Apr 14 21:32:39 localhost kernel: sdc: assuming drive cache: write through
> Apr 14 21:32:39 localhost kernel: sdc:<3>Buffer I/O error on device sdc,
> logical block 0
> Apr 14 21:32:39 localhost kernel: Buffer I/O error on device sdc, logical
> block 0
> Apr 14 21:32:39 localhost kernel: Buffer I/O error on device sdc, logical
> block 262143
> Apr 14 21:32:39 localhost kernel: Buffer I/O error on device sdc, logical
> block 262143
> Apr 14 21:32:39 localhost kernel: Buffer I/O error on device sdc, logical
> block 0
> Apr 14 21:32:39 localhost kernel: unable to read partition table
> Apr 14 21:32:39 localhost kernel: usb 1-6: USB disconnect, address 8
> Apr 14 21:32:40 localhost fstab-sync[5359]: removed mount point /media/usbdisk1
> for /dev/sdc1
> Apr 14 21:32:43 localhost kernel: ohci_hcd 0000:00:02.1: wakeup
> Apr 14 21:32:44 localhost kernel: usb 3-3: new full speed USB device using
> address 5
> Apr 14 21:32:44 localhost kernel: scsi8 : SCSI emulation for USB Mass Storage
> devices
> Apr 14 21:32:44 localhost kernel: Vendor: IC Model: USB Storage-CFC
> Rev: 322E
> Apr 14 21:32:44 localhost kernel: Type: Direct-Access
> ANSI SCSI revision: 02
> Apr 14 21:32:45 localhost kernel: sdc: Spinning up disk....ready
> Apr 14 21:32:45 localhost kernel: SCSI device sdc: 254464 512-byte hdwr sectors
> (130 MB)
> Apr 14 21:32:45 localhost kernel: sdc: Write Protect is off
> Apr 14 21:32:45 localhost kernel: sdc: assuming drive cache: write through
> Apr 14 21:32:49 localhost kernel: sdc:<4>usb 3-3: control timeout on ep0in
> Apr 14 21:32:49 localhost wait_for_sysfs[5383]: either wait_for_sysfs (udev
> 039) needs an update to handle the device '/devices/pci0000:00/0000:00:02.1/usb3/3-3/3-3:1.0'
> properly (no bus device link) or the sysfs-support of your device's driver
> needs to be fixed, please report to <linux-hotplug-devel@lists.sourceforge.net>
> Apr 14 21:32:49 localhost wait_for_sysfs[5399]: either wait_for_sysfs (udev
> 039) needs an update to handle the device '/devices/pci0000:00/0000:00:02.1/usb3/3-3/3-3:1.0/host8/8:0:0:0'
> properly (no bus device link) or the sysfs-support of your device's driver
> needs to be fixed, please report to <linux-hotplug-devel@lists.sourceforge.net>
> Apr 14 21:32:50 localhost wait_for_sysfs[5407]: either wait_for_sysfs (udev
> 039) needs an update to handle the device '/block/sdc' properly (no bus device
> link) or the sysfs-support of your device's driver needs to be fixed, please
> report to <linux-hotplug-devel@lists.sourceforge.net>
Looks like your udev package needs an update, at least the message
above should go away then. The rest of the messages seem either kernel
or hal related.
> Apr 14 21:32:59 localhost hal.hotplug[5409]: timout(10000 ms) waiting for
> /devices/pci0000:00/0000:00:02.1/usb3/3-3/3-3:1.0
> Apr 14 21:32:59 localhost hal.hotplug[5413]: timout(10000 ms) waiting for
> /devices/pci0000:00/0000:00:02.1/usb3/3-3/3-3:1.0/host8/8:0:0:0
> Apr 14 21:33:09 localhost scsi.agent[5457]: Attribute /sys/devices/pci0000:00/0000:00:02.1/usb3/3-3/3-3:1.0/host8/8:0:0:0/type
> does not exist
> Apr 14 21:33:50 localhost kernel: end_request: I/O error, dev fd0, sector
> 0
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2005-04-16 16:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-16 0:57 usb multicard reader problems ziettopeu
2005-04-16 8:43 ` Tobias Klauser
2005-04-16 16:10 ` Tobias Klauser [this message]
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=20050416161030.GA769@neon \
--to=tklauser@access.unizh.ch \
--cc=linux-hotplug@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.