On Tue, 23 Aug 2005 10:30:16 -0400 (EDT)
Alan Stern wrote:

> On Mon, 22 Aug 2005, David Relson wrote:
> 
> > Hi Alan,
> > 
> > I took a shot at building 2.6.13-rc6 and running it.  Unfortunately it
> > complained on reboot - "unable to mount root fs on
> > unknown-block(3,1)".  As a guess, it's complaining because my root fs
> > is ext3 and that's built as a module.  In any case I've not yet had a
> > chance to experiment more.
> 
> An ext3 root fs can cause problems.  Normally people include the ext3
> driver module in their initrd image.
> 
> > I _did_ start badblocks at yesterday.  Between 20:00 yesterday and
> > 17:00 today, it applied its 4 bit patterns to the 48M blocks of the
> > drive, didn't hang, and found zero errors
> 
> That sounds very good.  This is still with 2.6.11?
> 
> > Tonight I'll run full backups of my 2 machines, a process that usually
> > produces a "drive disconnect" state.
> 
> Alan Stern

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.

### Alt-SysReq-T

Aug 22 23:39:31 osage kernel: khubd         S C043C888     0  1199      1       
   4668   790 (L-TLB)
Aug 22 23:39:31 osage kernel: df0a3f8c 00000046 df0ba5b0 c043c888 0000526b 
e08753ba c15f20b8 00000002 
Aug 22 23:39:31 osage kernel:        e307f427 0000526b df0ba5b0 000015e0 
e312ee64 0000526b df74a190 df0a2000 
Aug 22 23:39:31 osage kernel:        df0a2000 df0a3fb4 df0a3fec e0875786 
00000009 df0a3fa8 df0a2000 00000000 
Aug 22 23:39:31 osage kernel: Call Trace:
Aug 22 23:39:31 osage kernel:  [pg0+540977030/1068971008] hub_thread+0x86/0x100 
[usbcore]
Aug 22 23:39:31 osage kernel:  [<e0875786>] hub_thread+0x86/0x100 [usbcore]
Aug 22 23:39:31 osage kernel:  [kernel_thread_helper+5/16] 
kernel_thread_helper+0x5/0x10
Aug 22 23:39:31 osage kernel:  [<c0101305>] kernel_thread_helper+0x5/0x10

### Alt-SysReq-T

Aug 22 23:41:47 osage kernel: khubd         S C043C888     0  1199      1       
   4668   790 (L-TLB)
Aug 22 23:41:47 osage kernel: df0a3f8c 00000046 df0ba5b0 c043c888 0000526b 
e08753ba c15f20b8 00000002 
Aug 22 23:41:47 osage kernel:        e307f427 0000526b df0ba5b0 000015e0 
e312ee64 0000526b df74a190 df0a2000 
Aug 22 23:41:47 osage kernel:        df0a2000 df0a3fb4 df0a3fec e0875786 
00000009 df0a3fa8 df0a2000 00000000 
Aug 22 23:41:47 osage kernel: Call Trace:
Aug 22 23:41:47 osage kernel:  [pg0+540977030/1068971008] hub_thread+0x86/0x100 
[usbcore]
Aug 22 23:41:47 osage kernel:  [<e0875786>] hub_thread+0x86/0x100 [usbcore]
Aug 22 23:41:47 osage kernel:  [kernel_thread_helper+5/16] 
kernel_thread_helper+0x5/0x10
Aug 22 23:41:47 osage kernel:  [<c0101305>] kernel_thread_helper+0x5/0x10

### 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

### Alt-SysRq-T

Aug 23 19:09:34 osage kernel: SysRq : Show State

Aug 23 19:09:34 osage kernel: khubd         S C043C888     0  1199      1       
   4668   790 (L-TLB)
Aug 23 19:09:34 osage kernel: df0a3f8c 00000046 df0ba5b0 c043c888 0000526b 
e08753ba c15f20b8 00000002 
Aug 23 19:09:34 osage kernel:        e307f427 0000526b df0ba5b0 000015e0 
e312ee64 0000526b df74a190 df0a2000 
Aug 23 19:09:34 osage kernel:        df0a2000 df0a3fb4 df0a3fec e0875786 
00000009 df0a3fa8 df0a2000 00000000 
Aug 23 19:09:34 osage kernel: Call Trace:
Aug 23 19:09:34 osage kernel:  [pg0+540977030/1068971008] hub_thread+0x86/0x100 
[usbcore]
Aug 23 19:09:34 osage kernel:  [<e0875786>] hub_thread+0x86/0x100 [usbcore]
Aug 23 19:09:34 osage kernel:  [kernel_thread_helper+5/16] 
kernel_thread_helper+0x5/0x10
Aug 23 19:09:34 osage kernel:  [<c0101305>] kernel_thread_helper+0x5/0x10

Aug 23 19:09:34 osage kernel: scsi_eh_2     S C043C3E0     0 13121      1       
  13122 24620 (L-TLB)
Aug 23 19:09:34 osage kernel: df755f74 00000046 dec37ac0 c043c3e0 df755f50 
c028f0c8 cbabb140 c15b9050 
Aug 23 19:09:34 osage kernel:        d0853c00 df755f70 dfce0020 00005a18 
758c1eaa 00008b30 dec37c10 df755fd4 
Aug 23 19:09:34 osage kernel:        df754000 00000246 df755fb4 c033bb0f 
df755fdc dec37ac0 00000000 00000001 
Aug 23 19:09:34 osage kernel: Call Trace:
Aug 23 19:09:34 osage kernel:  [__down_interruptible+127/240] 
__down_interruptible+0x7f/0xf0
Aug 23 19:09:34 osage kernel:  [<c033bb0f>] __down_interruptible+0x7f/0xf0
Aug 23 19:09:34 osage kernel:  [__down_failed_interruptible+10/16] 
__down_failed_interruptible+0xa/0x10
Aug 23 19:09:34 osage kernel:  [<c033bb9a>] __down_failed_interruptible+0xa/0x10
Aug 23 19:09:34 osage kernel:  [pg0+541243611/1068971008] 
.text.lock.scsi_error+0x39/0x3e [scsi_mod]
Aug 23 19:09:34 osage kernel:  [<e08b68db>] .text.lock.scsi_error+0x39/0x3e 
[scsi_mod]
Aug 23 19:09:34 osage kernel:  [kernel_thread_helper+5/16] 
kernel_thread_helper+0x5/0x10
Aug 23 19:09:34 osage kernel:  [<c0101305>] kernel_thread_helper+0x5/0x10

Aug 23 19:09:34 osage kernel: usb-storage   S C043C3E0     0 13122      1       
  18883 13121 (L-TLB)
Aug 23 19:09:34 osage kernel: dc6f7f4c 00000046 d75af040 c043c3e0 0000000d 
dec37ac0 c043c888 0000001f 
Aug 23 19:09:34 osage kernel:        00000000 00000000 cf82c1a0 0000032f 
2f8a4304 00008b2e d75af190 dfd44308 
Aug 23 19:09:34 osage kernel:        dc6f6000 00000246 dc6f7f8c c033bb0f 
dfd44310 d75af040 00000000 00000001 
Aug 23 19:09:34 osage kernel: Call Trace:
Aug 23 19:09:34 osage kernel:  [__down_interruptible+127/240] 
__down_interruptible+0x7f/0xf0
Aug 23 19:09:34 osage kernel:  [<c033bb0f>] __down_interruptible+0x7f/0xf0
Aug 23 19:09:34 osage kernel:  [__down_failed_interruptible+10/16] 
__down_failed_interruptible+0xa/0x10
Aug 23 19:09:34 osage kernel:  [<c033bb9a>] __down_failed_interruptible+0xa/0x10
Aug 23 19:09:34 osage kernel:  [pg0+540758364/1068971008] 
.text.lock.usb+0x17/0x9b [usb-storage]
Aug 23 19:09:34 osage kernel:  [<e084015c>] .text.lock.usb+0x17/0x9b 
[usb-storage]
Aug 23 19:09:34 osage kernel:  [kernel_thread_helper+5/16] 
kernel_thread_helper+0x5/0x10
Aug 23 19:09:34 osage kernel:  [<c0101305>] kernel_thread_helper+0x5/0x10

Aug 23 19:09:34 osage kernel: reiserfs/0    S C043C3E0     0 13377      9       
  11301    82 (L-TLB)
Aug 23 19:09:34 osage kernel: d648ff44 00000046 dfce0020 c043c3e0 fffffffb 
00000000 00000000 00000096 
Aug 23 19:09:34 osage kernel:        00000202 d648ff44 c2338590 00000f95 
758e5a6a 00008b30 dfce0170 de45a388 
Aug 23 19:09:34 osage kernel:        dee33a00 00000202 d648ffbc c0182845 
00000000 d648ff70 00000000 de45a398 
Aug 23 19:09:34 osage kernel: Call Trace:
Aug 23 19:09:34 osage kernel:  [worker_thread+501/560] worker_thread+0x1f5/0x230
Aug 23 19:09:34 osage kernel:  [<c0182845>] worker_thread+0x1f5/0x230
Aug 23 19:09:34 osage kernel:  [kthread+154/224] kthread+0x9a/0xe0
Aug 23 19:09:34 osage kernel:  [<c018646a>] kthread+0x9a/0xe0
Aug 23 19:09:34 osage kernel:  [kernel_thread_helper+5/16] 
kernel_thread_helper+0x5/0x10
Aug 23 19:09:34 osage kernel:  [<c0101305>] kernel_thread_helper+0x5/0x10



-------------------------------------------------------
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

Reply via email to