On Tue, 23 Aug 2005, David Relson wrote: > Yes, last night was good with the 2.6.11 kernel. Today hasn't been > quite as good: > > [EMAIL PROTECTED] ~]# uname -a > Linux osage.osagesoftware.com 2.6.11-12mdk #1 Mon Jun 27 23:18:37 MDT 2005 > i686 AMD Athlon(tm) XP unknown GNU/Linux > > ### hotplug ... > > Aug 22 21:10:19 osage kernel: usb 4-2: new high speed USB device using > ehci_hcd and address 3 > Aug 22 21:10:19 osage kernel: scsi2 : SCSI emulation for USB Mass Storage > devices > Aug 22 21:10:26 osage kernel: Vendor: ST320082 Model: 2A > Rev: 0 0 > Aug 22 21:10:26 osage kernel: Type: Direct-Access > ANSI SCSI revision: 00 > Aug 22 21:10:26 osage kernel: SCSI device sda: 390721968 512-byte hdwr > sectors (200050 MB) > Aug 22 21:10:26 osage kernel: sda: assuming drive cache: write through > Aug 22 21:10:26 osage kernel: SCSI device sda: 390721968 512-byte hdwr > sectors (200050 MB) > Aug 22 21:10:26 osage kernel: sda: assuming drive cache: write through > Aug 22 21:10:26 osage kernel: /dev/scsi/host2/bus0/target0/lun0: p1 > Aug 22 21:10:26 osage kernel: Attached scsi disk sda at scsi2, channel 0, id > 0, lun 0 > Aug 22 21:10:26 osage scsi.agent[13246]: disk at > /devices/pci0000:00/0000:00:10.3/usb4/4-2/4-2:1.0/host2/target2:0:0/2:0:0:0 > Aug 22 21:10:26 osage kernel: FAT: Did not find valid FSINFO signature. > Aug 22 21:10:26 osage kernel: Found signature1 0x00000000 signature2 > 0x00000000 (sector = 1) > Aug 22 21:10:26 osage kernel: FAT: Filesystem panic (dev sda) > Aug 22 21:10:26 osage kernel: fat_get_cluster: invalid cluster chain > (i_pos 0) > Aug 22 21:10:26 osage kernel: File system has been set read-only > Aug 22 21:10:26 osage kernel: ReiserFS: sda1: found reiserfs format "3.6" > with standard journal > Aug 22 21:10:36 osage kernel: ReiserFS: sda1: using ordered data mode > Aug 22 21:10:36 osage kernel: ReiserFS: sda1: journal params: device sda1, > size 8192, journal first block 18, max trans len 1024, max batch 900, max > commit age 30, max trans age 30 > Aug 22 21:10:36 osage kernel: ReiserFS: sda1: checking transaction log (sda1) > Aug 22 21:10:37 osage kernel: ReiserFS: sda1: Using r5 hash to sort names > Aug 22 21:10:37 osage kernel: ReiserFS: sda1: warning: Created .reiserfs_priv > on sda1 - reserved for xattr storage.
> ### TROUBLE ### > Aug 23 14:30:35 osage kernel: usb 4-2: reset high speed USB device using > ehci_hcd and address 3 > Aug 23 14:30:45 osage kernel: scsi: Device offlined - not ready after error > recovery: host 2 channel 0 id 0 lun 0 > Aug 23 14:30:45 osage kernel: SCSI error : <2 0 0 0> return code = 0x50000 > Aug 23 14:30:45 osage kernel: end_request: I/O error, dev sda, sector > 226583353 > Aug 23 14:30:45 osage kernel: scsi2 (0:0): rejecting I/O to offline device > Aug 23 14:30:45 osage kernel: scsi2 (0:0): rejecting I/O to offline device > Aug 23 14:30:45 osage kernel: Buffer I/O error on device sda1, logical block > 8210 > Aug 23 14:30:45 osage kernel: lost page write due to I/O error on sda1 > Aug 23 14:30:45 osage kernel: scsi2 (0:0): rejecting I/O to offline device This is the sort of thing I hope won't occur with 2.6.13. Notice by the way that the disk was set offline, but there's nothing about a disconnection. Under those circumstances you shouldn't see any processes hanging -- just a bunch of I/O errors. Alan Stern ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
