[opensuse] Nasty USB kernel error causes usb drive disconnect and disconnect of ALL mounted smb network shares
Guys, I have had a strange occurrence with a USB drive attached to my computer. I don't know if this is due to the new ext4 format on the usb drive or a kernel error affecting the usb subsystem. The usb drive I have has another install on it with / as ext4 and /home still ext3 per the 11.2 setup defaults. When I connect the drive to 11.2 the connection and automount work like they are supposed to. However, anywhere from 1 - 30 minutes later, a kernel error occurs that knocks the drive and all partitions off-line AND disconnects all smb mounted drives. Here is a snippet of the log entries. Full log at: http://www.3111skyline.com/download/openSUSE_bugs/112/kernel/kernel-error-us... Nov 19 15:31:42 alchemy kernel: [75027.512129] ------------[ cut here ]------------ Nov 19 15:31:42 alchemy kernel: [75027.512186] WARNING: at /usr/src/packages/BUILD/kernel-desktop-2.6.31.5/linux-2.6.31/fs/notify/inotify/inotify_fsnotify.c:129 idr_callback+0x67/0x90() Nov 19 15:31:42 alchemy kernel: [75027.512216] Hardware name: Satellite P205D Nov 19 15:31:42 alchemy kernel: [75027.512230] inotify closing but id=0 for entry=ffff8800d20a1898 in group=ffff880118d81780 still in idr. Probably leaking memory Nov 19 15:31:42 alchemy kernel: [75027.512254] Modules linked in: st ide_gd_mod ide_cd_mod nls_utf8 cifs ip6t_LOG xt_tcpudp xt_pkttype ipt_LOG xt_limit cryptd crypto_wq aes_x86_64 aes_generic snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device edd af_packet radeon drm ip6t_REJECT nf_conntrack_ipv6 ip6table_raw xt_NOTRACK ipt_REJECT xt_state iptable_raw iptable_filter cpufreq_conservative cpufreq_userspace ip6table_mangle cpufreq_powersave powernow_k8 nf_conntrack_netbios_ns nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables ip6table_filter ip6_tables x_tables fuse loop dm_mod arc4 ecb cryptomgr aead pcompress crypto_blkcipher pcmcia crypto_hash snd_hda_codec_realtek crypto_algapi snd_hda_intel snd_hda_codec sdhci_pci ath5k mac80211 sr_mod snd_hwdep amd64_edac_mod tifm_7xx1 yenta_socket ohci1394 rsrc_nonstatic snd_pcm edac_core k8temp pcspkr joydev tifm_core sg cdrom ath sdhci battery mmc_core ieee1394 video pcmcia_core ac shpchp pci_hotplug i2c_piix4 cfg80211 button rfkill snd_timer snd snd_page_alloc r8169 ext Nov 19 15:31:42 alchemy kernel: 4 jbd2 crc16 fan processor ide_pci_generic atiixp ide_core ata_generic pata_atiixp thermal thermal_sys [last unloaded: preloadtrace] Nov 19 15:31:42 alchemy kernel: [75027.512770] Pid: 7787, comm: kded Not tainted 2.6.31.5-0.1-desktop #1 Nov 19 15:31:42 alchemy kernel: [75027.512786] Call Trace: Nov 19 15:31:42 alchemy kernel: [75027.512828] [<ffffffff81011a19>] try_stack_unwind+0x189/0x1b0 Nov 19 15:31:42 alchemy kernel: [75027.512854] [<ffffffff8101025d>] dump_trace+0xad/0x3a0 Nov 19 15:31:42 alchemy kernel: [75027.512877] [<ffffffff81011524>] show_trace_log_lvl+0x64/0x90 Nov 19 15:31:42 alchemy kernel: [75027.512900] [<ffffffff81011573>] show_trace+0x23/0x40 Nov 19 15:31:42 alchemy kernel: [75027.512925] [<ffffffff81551ee2>] dump_stack+0x81/0x9e Nov 19 15:31:42 alchemy kernel: [75027.512950] [<ffffffff8106aec0>] warn_slowpath_common+0x80/0xd0 Nov 19 15:31:42 alchemy kernel: [75027.512973] [<ffffffff8106af9b>] warn_slowpath_fmt+0x4b/0x70 Nov 19 15:31:42 alchemy kernel: [75027.512995] [<ffffffff8118b9b7>] idr_callback+0x67/0x90 Nov 19 15:31:42 alchemy kernel: [75027.513056] [<ffffffff81287b2c>] idr_for_each+0x9c/0x110 Nov 19 15:31:42 alchemy kernel: [75027.513089] [<ffffffff8118b921>] inotify_free_group_priv+0x31/0x60 Nov 19 15:31:42 alchemy kernel: [75027.513121] [<ffffffff81188e22>] fsnotify_final_destroy_group+0x32/0x60 Nov 19 15:31:42 alchemy kernel: [75027.513152] [<ffffffff81188f88>] fsnotify_put_group+0xb8/0xd0 Nov 19 15:31:42 alchemy kernel: [75027.513183] [<ffffffff8118bcbd>] inotify_release+0x3d/0x70 Nov 19 15:31:42 alchemy kernel: [75027.513217] [<ffffffff8114dbc9>] __fput+0xe9/0x220 Nov 19 15:31:42 alchemy kernel: [75027.513246] [<ffffffff8114dd28>] fput+0x28/0x50 Nov 19 15:31:42 alchemy kernel: [75027.513283] [<ffffffff81149547>] filp_close+0x67/0xb0 Nov 19 15:31:42 alchemy kernel: [75027.513314] [<ffffffff8106d907>] put_files_struct+0x87/0x100 Nov 19 15:31:42 alchemy kernel: [75027.513345] [<ffffffff8106d9dc>] exit_files+0x5c/0x80 Nov 19 15:31:42 alchemy kernel: [75027.513375] [<ffffffff8106f41e>] do_exit+0x17e/0x3c0 Nov 19 15:31:42 alchemy kernel: [75027.513404] [<ffffffff8106f6b8>] do_group_exit+0x58/0xd0 Nov 19 15:31:42 alchemy kernel: [75027.513435] [<ffffffff8106f755>] sys_exit_group+0x25/0x40 Nov 19 15:31:42 alchemy kernel: [75027.513466] [<ffffffff8100c682>] system_call_fastpath+0x16/0x1b Nov 19 15:31:42 alchemy kernel: [75027.513508] [<00007fc214ba3c08>] 0x7fc214ba3c08 Nov 19 15:31:42 alchemy kernel: [75027.513528] ---[ end trace 036570030a664eac ]--- Nov 19 15:31:42 alchemy kernel: [75027.513549] entry->group=(null) inode=(null) wd=4096 <snip> Nov 19 18:20:25 alchemy laptop-mode: Adjusting 2.6 kernel parameters to disable laptop mode. Nov 19 18:20:25 alchemy laptop-mode: /sys/kernel/debug not found in PARTITIONS. Nov 19 18:20:25 alchemy laptop-mode: /sys/kernel/security not found in PARTITIONS. Nov 19 18:20:44 alchemy kernel: [10092.013951] ISO 9660 Extensions: Microsoft Joliet Level 3 Nov 19 18:20:44 alchemy kernel: [10092.157800] ISO 9660 Extensions: RRIP_1991A Nov 19 20:37:26 alchemy kernel: [18293.804949] lp: driver loaded but no devices found Nov 19 20:37:26 alchemy kernel: [18293.900397] ppdev: user-space parallel port driver Nov 19 23:12:47 alchemy kernel: [27614.916307] ath5k phy0: unsupported jumbo Nov 19 23:17:33 alchemy kernel: [27901.371065] usb 1-2: new high speed USB device using ehci_hcd and address 3 Nov 19 23:17:33 alchemy kernel: [27901.487101] usb 1-2: New USB device found, idVendor=152d, idProduct=2338 Nov 19 23:17:33 alchemy kernel: [27901.487137] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=5 Nov 19 23:17:33 alchemy kernel: [27901.487155] usb 1-2: Product: USB to ATA/ATAPI Bridge Nov 19 23:17:33 alchemy kernel: [27901.487170] usb 1-2: Manufacturer: JMicron Nov 19 23:17:33 alchemy kernel: [27901.487182] usb 1-2: SerialNumber: 222256D1009C Nov 19 23:17:33 alchemy kernel: [27901.487522] usb 1-2: configuration #1 chosen from 1 choice Nov 19 23:17:33 alchemy kernel: [27901.489407] scsi6 : SCSI emulation for USB Mass Storage devices Nov 19 23:17:33 alchemy kernel: [27901.489802] usb-storage: device found at 3 Nov 19 23:17:33 alchemy kernel: [27901.489808] usb-storage: waiting for device to settle before scanning Nov 19 23:17:34 alchemy kernel: [27902.490176] scsi 6:0:0:0: Direct-Access ST932032 5AS SDM1 PQ: 0 ANSI: 2 CCS Nov 19 23:17:34 alchemy kernel: [27902.491175] sd 6:0:0:0: Attached scsi generic sg2 type 0 Nov 19 23:17:34 alchemy kernel: [27902.492454] usb-storage: device scan complete Nov 19 23:17:34 alchemy kernel: [27902.522537] sd 6:0:0:0: [sdb] 625142448 512-byte logical blocks: (320 GB/298 GiB) Nov 19 23:17:34 alchemy kernel: [27902.523751] sd 6:0:0:0: [sdb] Write Protect is off Nov 19 23:17:34 alchemy kernel: [27902.523782] sd 6:0:0:0: [sdb] Mode Sense: 00 38 00 00 Nov 19 23:17:34 alchemy kernel: [27902.523790] sd 6:0:0:0: [sdb] Assuming drive cache: write through Nov 19 23:17:34 alchemy kernel: [27902.526271] sd 6:0:0:0: [sdb] Assuming drive cache: write through Nov 19 23:17:35 alchemy kernel: [27902.526323] sdb: sdb1 sdb2 sdb3 sdb4 Nov 19 23:17:35 alchemy kernel: [27902.896183] sd 6:0:0:0: [sdb] Assuming drive cache: write through Nov 19 23:17:35 alchemy kernel: [27902.896222] sd 6:0:0:0: [sdb] Attached SCSI disk Nov 19 23:18:06 alchemy kernel: [27933.803081] usb 1-2: reset high speed USB device using ehci_hcd and address 3 Nov 19 23:18:36 alchemy kernel: [27964.020066] usb 1-2: reset high speed USB device using ehci_hcd and address 3 Nov 19 23:19:13 alchemy kernel: [28000.803086] usb 1-2: reset high speed USB device using ehci_hcd and address 3 Nov 19 23:19:28 alchemy kernel: [28015.905071] usb 1-2: device descriptor read/64, error -110 Nov 19 23:19:43 alchemy kernel: [28031.108069] usb 1-2: device descriptor read/64, error -110 Nov 19 23:19:43 alchemy kernel: [28031.311072] usb 1-2: reset high speed USB device using ehci_hcd and address 3 Nov 19 23:19:58 alchemy kernel: [28046.413082] usb 1-2: device descriptor read/64, error -110 Nov 19 23:20:14 alchemy kernel: [28061.616069] usb 1-2: device descriptor read/64, error -110 Nov 19 23:20:14 alchemy kernel: [28061.819069] usb 1-2: reset high speed USB device using ehci_hcd and address 3 Nov 19 23:20:14 alchemy kernel: [28062.243051] usb 1-2: device not accepting address 3, error -71 Nov 19 23:20:14 alchemy kernel: [28062.345314] usb 1-2: reset high speed USB device using ehci_hcd and address 3 Nov 19 23:20:25 alchemy kernel: [28072.747067] usb 1-2: device not accepting address 3, error -110 Nov 19 23:20:25 alchemy kernel: [28072.747183] sd 6:0:0:0: Device offlined - not ready after error recovery Nov 19 23:20:25 alchemy kernel: [28072.747237] sd 6:0:0:0: [sdb] Unhandled error code Nov 19 23:20:25 alchemy kernel: [28072.747385] sd 6:0:0:0: [sdb] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK Nov 19 23:20:25 alchemy kernel: [28072.747409] end_request: I/O error, dev sdb, sector 53528580 Nov 19 23:20:25 alchemy kernel: [28072.747431] Buffer I/O error on device sdb4, logical block 0 Nov 19 23:20:25 alchemy kernel: [28072.747453] Buffer I/O error on device sdb4, logical block 1 Nov 19 23:20:25 alchemy kernel: [28072.747469] Buffer I/O error on device sdb4, logical block 2 Nov 19 23:20:25 alchemy kernel: [28072.747486] Buffer I/O error on device sdb4, logical block 3 Nov 19 23:20:25 alchemy kernel: [28072.747503] Buffer I/O error on device sdb4, logical block 4 Nov 19 23:20:25 alchemy kernel: [28072.747512] Buffer I/O error on device sdb4, logical block 5 Nov 19 23:20:25 alchemy kernel: [28072.747519] Buffer I/O error on device sdb4, logical block 6 Nov 19 23:20:25 alchemy kernel: [28072.747527] Buffer I/O error on device sdb4, logical block 7 Nov 19 23:20:25 alchemy kernel: [28072.747543] Buffer I/O error on device sdb4, logical block 8 Nov 19 23:20:25 alchemy kernel: [28072.747752] sd 6:0:0:0: rejecting I/O to offline device Nov 19 23:20:25 alchemy kernel: [28072.747842] sd 6:0:0:0: [sdb] Unhandled error code Nov 19 23:20:25 alchemy kernel: [28072.747858] sd 6:0:0:0: [sdb] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK Nov 19 23:20:25 alchemy kernel: [28072.747878] end_request: I/O error, dev sdb, sector 53528708 Nov 19 23:20:25 alchemy kernel: [28072.748103] sd 6:0:0:0: rejecting I/O to offline device Nov 19 23:20:25 alchemy kernel: [28072.748169] sd 6:0:0:0: rejecting I/O to offline device Nov 19 23:20:25 alchemy kernel: [28072.748260] sd 6:0:0:0: rejecting I/O to offline device Nov 19 23:20:25 alchemy kernel: [28072.748293] usb 1-2: USB disconnect, address 3 Nov 19 23:20:25 alchemy kernel: [28072.748300] sd 6:0:0:0: rejecting I/O to offline device Nov 19 23:20:25 alchemy kernel: [28072.855055] usb 1-2: new high speed USB device using ehci_hcd and address 4 Nov 19 23:20:25 alchemy kernel: [28072.981040] usb 1-2: device descriptor read/64, error -71 Nov 19 23:20:30 alchemy kernel: [28078.206065] usb 1-2: device descriptor read/64, error -71 Nov 19 23:20:30 alchemy kernel: [28078.409069] usb 1-2: new high speed USB device using ehci_hcd and address 5 Nov 19 23:20:30 alchemy kernel: [28078.548243] usb 1-2: device descriptor read/64, error -71 Nov 19 23:20:41 alchemy kernel: [28088.761069] usb 1-2: device descriptor read/64, error -71 Nov 19 23:20:41 alchemy kernel: [28088.964070] usb 1-2: new high speed USB device using ehci_hcd and address 6 Nov 19 23:20:51 alchemy kernel: [28099.366060] usb 1-2: device not accepting address 6, error -110 Nov 19 23:20:51 alchemy kernel: [28099.417345] hub 1-0:1.0: unable to enumerate USB device on port 2 Nov 19 23:21:33 alchemy kernel: [28140.805088] usb 1-2: new high speed USB device using ehci_hcd and address 8 Nov 19 23:21:33 alchemy kernel: [28140.921050] usb 1-2: New USB device found, idVendor=152d, idProduct=2338 Nov 19 23:21:33 alchemy kernel: [28140.921089] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=5 Nov 19 23:21:33 alchemy kernel: [28140.921107] usb 1-2: Product: USB to ATA/ATAPI Bridge Nov 19 23:21:33 alchemy kernel: [28140.921122] usb 1-2: Manufacturer: JMicron Nov 19 23:21:33 alchemy kernel: [28140.921134] usb 1-2: SerialNumber: 222256D1009C Nov 19 23:21:33 alchemy kernel: [28140.921640] usb 1-2: configuration #1 chosen from 1 choice Nov 19 23:21:33 alchemy kernel: [28140.923927] scsi7 : SCSI emulation for USB Mass Storage devices Nov 19 23:21:33 alchemy kernel: [28140.924873] usb-storage: device found at 8 Nov 19 23:21:33 alchemy kernel: [28140.924883] usb-storage: waiting for device to settle before scanning Nov 19 23:21:34 alchemy kernel: [28141.925259] scsi 7:0:0:0: Direct-Access ST932032 5AS SDM1 PQ: 0 ANSI: 2 CCS Nov 19 23:21:34 alchemy kernel: [28141.931805] sd 7:0:0:0: Attached scsi generic sg2 type 0 Nov 19 23:21:34 alchemy kernel: [28141.934500] usb-storage: device scan complete Nov 19 23:21:34 alchemy kernel: [28141.951408] sd 7:0:0:0: [sdb] 625142448 512-byte logical blocks: (320 GB/298 GiB) Nov 19 23:21:34 alchemy kernel: [28141.964372] sd 7:0:0:0: [sdb] Write Protect is off Nov 19 23:21:34 alchemy kernel: [28141.964394] sd 7:0:0:0: [sdb] Mode Sense: 00 38 00 00 Nov 19 23:21:34 alchemy kernel: [28141.964405] sd 7:0:0:0: [sdb] Assuming drive cache: write through Nov 19 23:21:34 alchemy kernel: [28141.966441] sd 7:0:0:0: [sdb] Assuming drive cache: write through Nov 19 23:21:34 alchemy kernel: [28141.966489] sdb: sdb1 sdb2 sdb3 sdb4 Nov 19 23:21:34 alchemy kernel: [28142.329129] sd 7:0:0:0: [sdb] Assuming drive cache: write through Nov 19 23:21:34 alchemy kernel: [28142.329169] sd 7:0:0:0: [sdb] Attached SCSI disk Nov 19 23:21:35 alchemy kernel: [28143.104874] kjournald starting. Commit interval 15 seconds Nov 19 23:21:35 alchemy kernel: [28143.160204] kjournald starting. Commit interval 15 seconds Nov 19 23:21:35 alchemy kernel: [28143.160592] EXT3 FS on sdb3, internal journal Nov 19 23:21:35 alchemy kernel: [28143.160606] EXT3-fs: mounted filesystem with ordered data mode. Nov 19 23:21:35 alchemy kernel: [28143.162994] EXT3 FS on sdb4, internal journal Nov 19 23:21:35 alchemy kernel: [28143.163017] EXT3-fs: mounted filesystem with ordered data mode. Nov 19 23:31:30 alchemy kernel: [28737.803090] usb 1-2: reset high speed USB device using ehci_hcd and address 8 Nov 19 23:32:00 alchemy kernel: [28768.020047] usb 1-2: reset high speed USB device using ehci_hcd and address 8 Nov 19 23:32:37 alchemy kernel: [28804.803097] usb 1-2: reset high speed USB device using ehci_hcd and address 8 Nov 19 23:32:47 alchemy kernel: [28814.915062] usb 1-2: device descriptor read/64, error -71 Nov 19 23:32:47 alchemy kernel: [28815.153078] usb 1-2: device descriptor read/64, error -71 Nov 19 23:32:47 alchemy kernel: [28815.356065] usb 1-2: reset high speed USB device using ehci_hcd and address 8 Nov 19 23:33:02 alchemy kernel: [28830.458065] usb 1-2: device descriptor read/64, error -110 Nov 19 23:33:18 alchemy kernel: [28845.661074] usb 1-2: device descriptor read/64, error -110 Nov 19 23:33:18 alchemy kernel: [28845.864062] usb 1-2: reset high speed USB device using ehci_hcd and address 8 Nov 19 23:33:23 alchemy kernel: [28851.278070] usb 1-2: device not accepting address 8, error -110 Nov 19 23:33:23 alchemy kernel: [28851.380096] usb 1-2: reset high speed USB device using ehci_hcd and address 8 Nov 19 23:33:24 alchemy kernel: [28851.803056] usb 1-2: device not accepting address 8, error -71 Nov 19 23:33:24 alchemy kernel: [28851.803183] sd 7:0:0:0: Device offlined - not ready after error recovery Nov 19 23:33:24 alchemy kernel: [28851.803220] sd 7:0:0:0: [sdb] Unhandled error code Nov 19 23:33:24 alchemy kernel: [28851.803234] sd 7:0:0:0: [sdb] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK Nov 19 23:33:24 alchemy kernel: [28851.803277] end_request: I/O error, dev sdb, sector 199411716 Nov 19 23:33:24 alchemy kernel: [28851.803405] sd 7:0:0:0: rejecting I/O to offline device Nov 19 23:33:24 alchemy kernel: [28851.803460] usb 1-2: USB disconnect, address 8 Nov 19 23:33:24 alchemy kernel: [28851.812524] Aborting journal on device sdb4. Nov 19 23:33:24 alchemy kernel: [28851.812659] journal commit I/O error Nov 19 23:33:24 alchemy kernel: [28851.881415] ------------[ cut here ]------------ Nov 19 23:33:24 alchemy kernel: [28851.881466] WARNING: at /usr/src/packages/BUILD/kernel-desktop-2.6.31.5/linux-2.6.31/fs/buffer.c:1158 mark_buffer_dirty+0xa6/0xd0() <snip> So far this seems to effect the x86_64 box and not the i586 box. I have the same drive attached to the i586 box right now and the logs are clean and the drive is working fine.. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
David C. Rankin wrote:
Guys,
I have had a strange occurrence with a USB drive attached to my computer. I don't know if this is due to the new ext4 format on the usb drive or a kernel error affecting the usb subsystem. The usb drive I have has another install on it with / as ext4 and /home still ext3 per the 11.2 setup defaults. When I connect the drive to 11.2 the connection and automount work like they are supposed to.
However, anywhere from 1 - 30 minutes later, a kernel error occurs that knocks the drive and all partitions off-line AND disconnects all smb mounted drives. Here is a snippet of the log entries. Full log at:
http://www.3111skyline.com/download/openSUSE_bugs/112/kernel/kernel-error-us...
Nov 19 15:31:42 alchemy kernel: [75027.512129] ------------[ cut here ]------------ Nov 19 15:31:42 alchemy kernel: [75027.512186] WARNING: at /usr/src/packages/BUILD/kernel-desktop-2.6.31.5/linux-2.6.31/fs/notify/inotify/inotify_fsnotify.c:129 idr_callback+0x67/0x90() Nov 19 15:31:42 alchemy kernel: [75027.512216] Hardware name: Satellite P205D Nov 19 15:31:42 alchemy kernel: [75027.512230] inotify closing but id=0 for entry=ffff8800d20a1898 in group=ffff880118d81780 still in idr. Probably leaking memory Nov 19 15:31:42 alchemy kernel: [75027.512254] Modules linked in: st ide_gd_mod ide_cd_mod nls_utf8 cifs ip6t_LOG xt_tcpudp xt_pkttype ipt_LOG xt_limit cryptd crypto_wq aes_x86_64 aes_generic snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device edd af_packet radeon drm ip6t_REJECT nf_conntrack_ipv6 ip6table_raw xt_NOTRACK ipt_REJECT xt_state iptable_raw iptable_filter cpufreq_conservative cpufreq_userspace ip6table_mangle cpufreq_powersave powernow_k8 nf_conntrack_netbios_ns nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables ip6table_filter ip6_tables x_tables fuse loop dm_mod arc4 ecb cryptomgr aead pcompress crypto_blkcipher pcmcia crypto_hash snd_hda_codec_realtek crypto_algapi snd_hda_intel snd_hda_codec sdhci_pci ath5k mac80211 sr_mod snd_hwdep amd64_edac_mod tifm_7xx1 yenta_socket ohci1394 rsrc_nonstatic snd_pcm edac_core k8temp pcspkr joydev tifm_core sg cdrom ath sdhci battery mmc_core ieee1394 video pcmcia_core ac shpchp pci_hotplug i2c_piix4 cfg80211 button rfkill snd_timer snd snd_page_alloc r8169 ext Nov 19 15:31:42 alchemy kernel: 4 jbd2 crc16 fan processor ide_pci_generic atiixp ide_core ata_generic pata_atiixp thermal thermal_sys [last unloaded: preloadtrace] Nov 19 15:31:42 alchemy kernel: [75027.512770] Pid: 7787, comm: kded Not tainted 2.6.31.5-0.1-desktop #1 Nov 19 15:31:42 alchemy kernel: [75027.512786] Call Trace: Nov 19 15:31:42 alchemy kernel: [75027.512828] [<ffffffff81011a19>] try_stack_unwind+0x189/0x1b0 Nov 19 15:31:42 alchemy kernel: [75027.512854] [<ffffffff8101025d>] dump_trace+0xad/0x3a0 Nov 19 15:31:42 alchemy kernel: [75027.512877] [<ffffffff81011524>] show_trace_log_lvl+0x64/0x90 Nov 19 15:31:42 alchemy kernel: [75027.512900] [<ffffffff81011573>] show_trace+0x23/0x40 Nov 19 15:31:42 alchemy kernel: [75027.512925] [<ffffffff81551ee2>] dump_stack+0x81/0x9e Nov 19 15:31:42 alchemy kernel: [75027.512950] [<ffffffff8106aec0>] warn_slowpath_common+0x80/0xd0 Nov 19 15:31:42 alchemy kernel: [75027.512973] [<ffffffff8106af9b>] warn_slowpath_fmt+0x4b/0x70 Nov 19 15:31:42 alchemy kernel: [75027.512995] [<ffffffff8118b9b7>] idr_callback+0x67/0x90 Nov 19 15:31:42 alchemy kernel: [75027.513056] [<ffffffff81287b2c>] idr_for_each+0x9c/0x110 Nov 19 15:31:42 alchemy kernel: [75027.513089] [<ffffffff8118b921>] inotify_free_group_priv+0x31/0x60 Nov 19 15:31:42 alchemy kernel: [75027.513121] [<ffffffff81188e22>] fsnotify_final_destroy_group+0x32/0x60 Nov 19 15:31:42 alchemy kernel: [75027.513152] [<ffffffff81188f88>] fsnotify_put_group+0xb8/0xd0 Nov 19 15:31:42 alchemy kernel: [75027.513183] [<ffffffff8118bcbd>] inotify_release+0x3d/0x70 Nov 19 15:31:42 alchemy kernel: [75027.513217] [<ffffffff8114dbc9>] __fput+0xe9/0x220 Nov 19 15:31:42 alchemy kernel: [75027.513246] [<ffffffff8114dd28>] fput+0x28/0x50 Nov 19 15:31:42 alchemy kernel: [75027.513283] [<ffffffff81149547>] filp_close+0x67/0xb0 Nov 19 15:31:42 alchemy kernel: [75027.513314] [<ffffffff8106d907>] put_files_struct+0x87/0x100 Nov 19 15:31:42 alchemy kernel: [75027.513345] [<ffffffff8106d9dc>] exit_files+0x5c/0x80 Nov 19 15:31:42 alchemy kernel: [75027.513375] [<ffffffff8106f41e>] do_exit+0x17e/0x3c0 Nov 19 15:31:42 alchemy kernel: [75027.513404] [<ffffffff8106f6b8>] do_group_exit+0x58/0xd0 Nov 19 15:31:42 alchemy kernel: [75027.513435] [<ffffffff8106f755>] sys_exit_group+0x25/0x40 Nov 19 15:31:42 alchemy kernel: [75027.513466] [<ffffffff8100c682>] system_call_fastpath+0x16/0x1b Nov 19 15:31:42 alchemy kernel: [75027.513508] [<00007fc214ba3c08>] 0x7fc214ba3c08 Nov 19 15:31:42 alchemy kernel: [75027.513528] ---[ end trace 036570030a664eac ]--- Nov 19 15:31:42 alchemy kernel: [75027.513549] entry->group=(null) inode=(null) wd=4096
<snip>
Nov 19 18:20:25 alchemy laptop-mode: Adjusting 2.6 kernel parameters to disable laptop mode. Nov 19 18:20:25 alchemy laptop-mode: /sys/kernel/debug not found in PARTITIONS. Nov 19 18:20:25 alchemy laptop-mode: /sys/kernel/security not found in PARTITIONS. Nov 19 18:20:44 alchemy kernel: [10092.013951] ISO 9660 Extensions: Microsoft Joliet Level 3 Nov 19 18:20:44 alchemy kernel: [10092.157800] ISO 9660 Extensions: RRIP_1991A Nov 19 20:37:26 alchemy kernel: [18293.804949] lp: driver loaded but no devices found Nov 19 20:37:26 alchemy kernel: [18293.900397] ppdev: user-space parallel port driver Nov 19 23:12:47 alchemy kernel: [27614.916307] ath5k phy0: unsupported jumbo Nov 19 23:17:33 alchemy kernel: [27901.371065] usb 1-2: new high speed USB device using ehci_hcd and address 3 Nov 19 23:17:33 alchemy kernel: [27901.487101] usb 1-2: New USB device found, idVendor=152d, idProduct=2338 Nov 19 23:17:33 alchemy kernel: [27901.487137] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=5 Nov 19 23:17:33 alchemy kernel: [27901.487155] usb 1-2: Product: USB to ATA/ATAPI Bridge Nov 19 23:17:33 alchemy kernel: [27901.487170] usb 1-2: Manufacturer: JMicron Nov 19 23:17:33 alchemy kernel: [27901.487182] usb 1-2: SerialNumber: 222256D1009C Nov 19 23:17:33 alchemy kernel: [27901.487522] usb 1-2: configuration #1 chosen from 1 choice Nov 19 23:17:33 alchemy kernel: [27901.489407] scsi6 : SCSI emulation for USB Mass Storage devices Nov 19 23:17:33 alchemy kernel: [27901.489802] usb-storage: device found at 3 Nov 19 23:17:33 alchemy kernel: [27901.489808] usb-storage: waiting for device to settle before scanning Nov 19 23:17:34 alchemy kernel: [27902.490176] scsi 6:0:0:0: Direct-Access ST932032 5AS SDM1 PQ: 0 ANSI: 2 CCS Nov 19 23:17:34 alchemy kernel: [27902.491175] sd 6:0:0:0: Attached scsi generic sg2 type 0 Nov 19 23:17:34 alchemy kernel: [27902.492454] usb-storage: device scan complete Nov 19 23:17:34 alchemy kernel: [27902.522537] sd 6:0:0:0: [sdb] 625142448 512-byte logical blocks: (320 GB/298 GiB) Nov 19 23:17:34 alchemy kernel: [27902.523751] sd 6:0:0:0: [sdb] Write Protect is off Nov 19 23:17:34 alchemy kernel: [27902.523782] sd 6:0:0:0: [sdb] Mode Sense: 00 38 00 00 Nov 19 23:17:34 alchemy kernel: [27902.523790] sd 6:0:0:0: [sdb] Assuming drive cache: write through Nov 19 23:17:34 alchemy kernel: [27902.526271] sd 6:0:0:0: [sdb] Assuming drive cache: write through Nov 19 23:17:35 alchemy kernel: [27902.526323] sdb: sdb1 sdb2 sdb3 sdb4 Nov 19 23:17:35 alchemy kernel: [27902.896183] sd 6:0:0:0: [sdb] Assuming drive cache: write through Nov 19 23:17:35 alchemy kernel: [27902.896222] sd 6:0:0:0: [sdb] Attached SCSI disk Nov 19 23:18:06 alchemy kernel: [27933.803081] usb 1-2: reset high speed USB device using ehci_hcd and address 3 Nov 19 23:18:36 alchemy kernel: [27964.020066] usb 1-2: reset high speed USB device using ehci_hcd and address 3 Nov 19 23:19:13 alchemy kernel: [28000.803086] usb 1-2: reset high speed USB device using ehci_hcd and address 3 Nov 19 23:19:28 alchemy kernel: [28015.905071] usb 1-2: device descriptor read/64, error -110 Nov 19 23:19:43 alchemy kernel: [28031.108069] usb 1-2: device descriptor read/64, error -110 Nov 19 23:19:43 alchemy kernel: [28031.311072] usb 1-2: reset high speed USB device using ehci_hcd and address 3 Nov 19 23:19:58 alchemy kernel: [28046.413082] usb 1-2: device descriptor read/64, error -110 Nov 19 23:20:14 alchemy kernel: [28061.616069] usb 1-2: device descriptor read/64, error -110 Nov 19 23:20:14 alchemy kernel: [28061.819069] usb 1-2: reset high speed USB device using ehci_hcd and address 3 Nov 19 23:20:14 alchemy kernel: [28062.243051] usb 1-2: device not accepting address 3, error -71 Nov 19 23:20:14 alchemy kernel: [28062.345314] usb 1-2: reset high speed USB device using ehci_hcd and address 3 Nov 19 23:20:25 alchemy kernel: [28072.747067] usb 1-2: device not accepting address 3, error -110 Nov 19 23:20:25 alchemy kernel: [28072.747183] sd 6:0:0:0: Device offlined - not ready after error recovery Nov 19 23:20:25 alchemy kernel: [28072.747237] sd 6:0:0:0: [sdb] Unhandled error code Nov 19 23:20:25 alchemy kernel: [28072.747385] sd 6:0:0:0: [sdb] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK Nov 19 23:20:25 alchemy kernel: [28072.747409] end_request: I/O error, dev sdb, sector 53528580 Nov 19 23:20:25 alchemy kernel: [28072.747431] Buffer I/O error on device sdb4, logical block 0 Nov 19 23:20:25 alchemy kernel: [28072.747453] Buffer I/O error on device sdb4, logical block 1 Nov 19 23:20:25 alchemy kernel: [28072.747469] Buffer I/O error on device sdb4, logical block 2 Nov 19 23:20:25 alchemy kernel: [28072.747486] Buffer I/O error on device sdb4, logical block 3 Nov 19 23:20:25 alchemy kernel: [28072.747503] Buffer I/O error on device sdb4, logical block 4 Nov 19 23:20:25 alchemy kernel: [28072.747512] Buffer I/O error on device sdb4, logical block 5 Nov 19 23:20:25 alchemy kernel: [28072.747519] Buffer I/O error on device sdb4, logical block 6 Nov 19 23:20:25 alchemy kernel: [28072.747527] Buffer I/O error on device sdb4, logical block 7 Nov 19 23:20:25 alchemy kernel: [28072.747543] Buffer I/O error on device sdb4, logical block 8 Nov 19 23:20:25 alchemy kernel: [28072.747752] sd 6:0:0:0: rejecting I/O to offline device Nov 19 23:20:25 alchemy kernel: [28072.747842] sd 6:0:0:0: [sdb] Unhandled error code Nov 19 23:20:25 alchemy kernel: [28072.747858] sd 6:0:0:0: [sdb] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK Nov 19 23:20:25 alchemy kernel: [28072.747878] end_request: I/O error, dev sdb, sector 53528708 Nov 19 23:20:25 alchemy kernel: [28072.748103] sd 6:0:0:0: rejecting I/O to offline device Nov 19 23:20:25 alchemy kernel: [28072.748169] sd 6:0:0:0: rejecting I/O to offline device Nov 19 23:20:25 alchemy kernel: [28072.748260] sd 6:0:0:0: rejecting I/O to offline device Nov 19 23:20:25 alchemy kernel: [28072.748293] usb 1-2: USB disconnect, address 3 Nov 19 23:20:25 alchemy kernel: [28072.748300] sd 6:0:0:0: rejecting I/O to offline device Nov 19 23:20:25 alchemy kernel: [28072.855055] usb 1-2: new high speed USB device using ehci_hcd and address 4 Nov 19 23:20:25 alchemy kernel: [28072.981040] usb 1-2: device descriptor read/64, error -71 Nov 19 23:20:30 alchemy kernel: [28078.206065] usb 1-2: device descriptor read/64, error -71 Nov 19 23:20:30 alchemy kernel: [28078.409069] usb 1-2: new high speed USB device using ehci_hcd and address 5 Nov 19 23:20:30 alchemy kernel: [28078.548243] usb 1-2: device descriptor read/64, error -71 Nov 19 23:20:41 alchemy kernel: [28088.761069] usb 1-2: device descriptor read/64, error -71 Nov 19 23:20:41 alchemy kernel: [28088.964070] usb 1-2: new high speed USB device using ehci_hcd and address 6 Nov 19 23:20:51 alchemy kernel: [28099.366060] usb 1-2: device not accepting address 6, error -110 Nov 19 23:20:51 alchemy kernel: [28099.417345] hub 1-0:1.0: unable to enumerate USB device on port 2 Nov 19 23:21:33 alchemy kernel: [28140.805088] usb 1-2: new high speed USB device using ehci_hcd and address 8 Nov 19 23:21:33 alchemy kernel: [28140.921050] usb 1-2: New USB device found, idVendor=152d, idProduct=2338 Nov 19 23:21:33 alchemy kernel: [28140.921089] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=5 Nov 19 23:21:33 alchemy kernel: [28140.921107] usb 1-2: Product: USB to ATA/ATAPI Bridge Nov 19 23:21:33 alchemy kernel: [28140.921122] usb 1-2: Manufacturer: JMicron Nov 19 23:21:33 alchemy kernel: [28140.921134] usb 1-2: SerialNumber: 222256D1009C Nov 19 23:21:33 alchemy kernel: [28140.921640] usb 1-2: configuration #1 chosen from 1 choice Nov 19 23:21:33 alchemy kernel: [28140.923927] scsi7 : SCSI emulation for USB Mass Storage devices Nov 19 23:21:33 alchemy kernel: [28140.924873] usb-storage: device found at 8 Nov 19 23:21:33 alchemy kernel: [28140.924883] usb-storage: waiting for device to settle before scanning Nov 19 23:21:34 alchemy kernel: [28141.925259] scsi 7:0:0:0: Direct-Access ST932032 5AS SDM1 PQ: 0 ANSI: 2 CCS Nov 19 23:21:34 alchemy kernel: [28141.931805] sd 7:0:0:0: Attached scsi generic sg2 type 0 Nov 19 23:21:34 alchemy kernel: [28141.934500] usb-storage: device scan complete Nov 19 23:21:34 alchemy kernel: [28141.951408] sd 7:0:0:0: [sdb] 625142448 512-byte logical blocks: (320 GB/298 GiB) Nov 19 23:21:34 alchemy kernel: [28141.964372] sd 7:0:0:0: [sdb] Write Protect is off Nov 19 23:21:34 alchemy kernel: [28141.964394] sd 7:0:0:0: [sdb] Mode Sense: 00 38 00 00 Nov 19 23:21:34 alchemy kernel: [28141.964405] sd 7:0:0:0: [sdb] Assuming drive cache: write through Nov 19 23:21:34 alchemy kernel: [28141.966441] sd 7:0:0:0: [sdb] Assuming drive cache: write through Nov 19 23:21:34 alchemy kernel: [28141.966489] sdb: sdb1 sdb2 sdb3 sdb4 Nov 19 23:21:34 alchemy kernel: [28142.329129] sd 7:0:0:0: [sdb] Assuming drive cache: write through Nov 19 23:21:34 alchemy kernel: [28142.329169] sd 7:0:0:0: [sdb] Attached SCSI disk Nov 19 23:21:35 alchemy kernel: [28143.104874] kjournald starting. Commit interval 15 seconds Nov 19 23:21:35 alchemy kernel: [28143.160204] kjournald starting. Commit interval 15 seconds Nov 19 23:21:35 alchemy kernel: [28143.160592] EXT3 FS on sdb3, internal journal Nov 19 23:21:35 alchemy kernel: [28143.160606] EXT3-fs: mounted filesystem with ordered data mode. Nov 19 23:21:35 alchemy kernel: [28143.162994] EXT3 FS on sdb4, internal journal Nov 19 23:21:35 alchemy kernel: [28143.163017] EXT3-fs: mounted filesystem with ordered data mode. Nov 19 23:31:30 alchemy kernel: [28737.803090] usb 1-2: reset high speed USB device using ehci_hcd and address 8 Nov 19 23:32:00 alchemy kernel: [28768.020047] usb 1-2: reset high speed USB device using ehci_hcd and address 8 Nov 19 23:32:37 alchemy kernel: [28804.803097] usb 1-2: reset high speed USB device using ehci_hcd and address 8 Nov 19 23:32:47 alchemy kernel: [28814.915062] usb 1-2: device descriptor read/64, error -71 Nov 19 23:32:47 alchemy kernel: [28815.153078] usb 1-2: device descriptor read/64, error -71 Nov 19 23:32:47 alchemy kernel: [28815.356065] usb 1-2: reset high speed USB device using ehci_hcd and address 8 Nov 19 23:33:02 alchemy kernel: [28830.458065] usb 1-2: device descriptor read/64, error -110 Nov 19 23:33:18 alchemy kernel: [28845.661074] usb 1-2: device descriptor read/64, error -110 Nov 19 23:33:18 alchemy kernel: [28845.864062] usb 1-2: reset high speed USB device using ehci_hcd and address 8 Nov 19 23:33:23 alchemy kernel: [28851.278070] usb 1-2: device not accepting address 8, error -110 Nov 19 23:33:23 alchemy kernel: [28851.380096] usb 1-2: reset high speed USB device using ehci_hcd and address 8 Nov 19 23:33:24 alchemy kernel: [28851.803056] usb 1-2: device not accepting address 8, error -71 Nov 19 23:33:24 alchemy kernel: [28851.803183] sd 7:0:0:0: Device offlined - not ready after error recovery Nov 19 23:33:24 alchemy kernel: [28851.803220] sd 7:0:0:0: [sdb] Unhandled error code Nov 19 23:33:24 alchemy kernel: [28851.803234] sd 7:0:0:0: [sdb] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK Nov 19 23:33:24 alchemy kernel: [28851.803277] end_request: I/O error, dev sdb, sector 199411716 Nov 19 23:33:24 alchemy kernel: [28851.803405] sd 7:0:0:0: rejecting I/O to offline device Nov 19 23:33:24 alchemy kernel: [28851.803460] usb 1-2: USB disconnect, address 8 Nov 19 23:33:24 alchemy kernel: [28851.812524] Aborting journal on device sdb4. Nov 19 23:33:24 alchemy kernel: [28851.812659] journal commit I/O error Nov 19 23:33:24 alchemy kernel: [28851.881415] ------------[ cut here ]------------ Nov 19 23:33:24 alchemy kernel: [28851.881466] WARNING: at /usr/src/packages/BUILD/kernel-desktop-2.6.31.5/linux-2.6.31/fs/buffer.c:1158 mark_buffer_dirty+0xa6/0xd0()
<snip>
So far this seems to effect the x86_64 box and not the i586 box. I have the same drive attached to the i586 box right now and the logs are clean and the drive is working fine..
Dave it looks like to me got hardware starting to fail try a live cd on the box if you can -- Hans Krueger hanskrueger007@roadrunner.com registered Linux user 289023 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 11/21/2009 5:33 AM, Hans Krueger wrote:
Nov 19 23:17:33 alchemy kernel: [27901.487101] usb 1-2: New USB device
found, idVendor=152d, idProduct=2338
This is a known issue in Ubuntu land... https://bugs.launchpad.net/ubuntu/+source/linux/+bug/387161 (see post 74) Supposedly fixed in libatasmart, by blacklisting Jmicron controllers: This bug was fixed in the package libatasmart - 0.15-3 --------------- libatasmart (0.15-3) unstable; urgency=low * atasmart.c: Blacklist JMicron drives 152d:233[89] as well, since they were also confirmed to cause USB resets on SMART probing. (LP: #387161, https://bugzilla.redhat.com/show_bug.cgi?id=515881) -- Martin Pitt <email address hidden> Thu, 24 Sep 2009 11:26:24 +0200 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 21 November 2009 07:33:22 and regarding:
Dave it looks like to me got hardware starting to fail try a live cd on the box if you can
Humm, OK, I'll give the live CD a go in the morning. I suspect it is something suse related, because with the drive in question, if I install it as a normal harddrive in my laptop, it works great. Also, I swapped drives in my Laptop to updated the Archlinux install. I attached the same usb drive to the Arch Linux box and it did just fine, no errors and no disconnects, The Arch kernel is: 26-2.6.31.6-1 Same box, same usb drive, works fine on arch, disconnectint in 11.2. That's what has me thinking 11.2 may be to blame. I'll try the live CD and let you know. If you think of anything else, please let me know. Thanks -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 22 November 2009 01:57:36 am David C. Rankin wrote:
On Saturday 21 November 2009 07:33:22 and regarding:
Dave it looks like to me got hardware starting to fail try a live cd on the box if you can
Humm,
OK, I'll give the live CD a go in the morning. I suspect it is something suse related, because with the drive in question, if I install it as a normal harddrive in my laptop, it works great. Also, I swapped drives in my Laptop to updated the Archlinux install. I attached the same usb drive to the Arch Linux box and it did just fine, no errors and no disconnects, The Arch kernel is:
26-2.6.31.6-1
Google that drive controller chip set Dave. This is not failing hardware. Its a known problem, and I believe I posted a link to a bugzilla work around in a prior email -- If stupidity got us into this mess, then why can't it get us out? - Will Rogers -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
John Andersen wrote:
On Sunday 22 November 2009 01:57:36 am David C. Rankin wrote:
On Saturday 21 November 2009 07:33:22 and regarding:
Dave it looks like to me got hardware starting to fail try a live cd on the box if you can Humm,
OK, I'll give the live CD a go in the morning. I suspect it is something suse related, because with the drive in question, if I install it as a normal harddrive in my laptop, it works great. Also, I swapped drives in my Laptop to updated the Archlinux install. I attached the same usb drive to the Arch Linux box and it did just fine, no errors and no disconnects, The Arch kernel is:
26-2.6.31.6-1
Google that drive controller chip set Dave.
This is not failing hardware.
Its a known problem, and I believe I posted a link to a bugzilla work around in a prior email
Damn you good! John.... I'll research it and post any helpful info I find. This issue has just blown my mind. I've picked through so many log entries my head is swimming. This particular sever at home has been bulletproof since I built it. It handles massive defferenced backups nightly at 4:00 pulling my complete office to my house via remote rsync, It handles video transfers all the time and I have been intimately familiar with its logs since the day I first loaded 10.3 on it in '07. Never before has it had a single hiccup until I connected to it remotely from 11.2. I know it isn't a new kernel bug because I'm running 2.6.32-1 right now on Arch, and it works fine with the server. I'll read and post anything interesting. Thanks again John! -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 22 November 2009 03:57:36 and regarding:
On Saturday 21 November 2009 07:33:22 and regarding:
Dave it looks like to me got hardware starting to fail try a live cd on the box if you can
Humm,
OK, I'll give the live CD a go in the morning. I suspect it is something suse related, because with the drive in question, if I install it as a normal harddrive in my laptop, it works great. Also, I swapped drives in my Laptop to updated the Archlinux install. I attached the same usb drive to the Arch Linux box and it did just fine, no errors and no disconnects, The Arch kernel is:
26-2.6.31.6-1
Same box, same usb drive, works fine on arch, disconnectint in 11.2. That's what has me thinking 11.2 may be to blame. I'll try the live CD and let you know. If you think of anything else, please let me know. Thanks
(live cd worked fine in the testing I did with the USB drive)
Guys,
There is a problem with 11.2 x86_64 that causes disk corruption on USB and Remote filesystems when you connect to them. I have probably spent the better part of 20 hours picking through longs and running fsck and testing to try and identify the issue. I still do not understand it, but I have experienced it on two separate remote filesystems (the first over a USB connection, the second over ssh/sftp/fish connections to my 10.3 server). My first post about it was in this thread. My second (which I can't find right now) was a reply to John Bennett who experienced disk corruption.
Ah hah! found the second thread, my reply was sent Friday in "Re: [opensuse] Deleting corrupted files".
I don't know if this is related (I strongly suspect it is, but that is just my hunch), but I first noticed screwed up characters in 'mc'. The little scrollbars and lines were not the noral ascii line drawing and extended characters, but instead were funky 'A' or 'a' characters with the little 'circles' or 'degree sysmbols' over them. (I have screenshots somewhere, but we have all seen these characters when encoding is fubar)
Let me know if anyone wants to see them, and I'll track them down. (files are spread over several machines due to this (what I will call BUG) requring a complete wipe of my 11.2 laptop install, and complete backup and recovery of a 500G dmraid /home partition on my 10.3 server). (not exactly a simple fsck issue)
The corruption problem occurred when connecting from my 11.2 x86_64 install on my 11.0 laptop either to a usb connected hard drive or when connecting via ssh, fish or sftp and then copying files to/from my laptop or performing remote operation of the remote filesystems (copying, moving, deleting, etc...).
The 11.2 install on my laptop was a 'plain-Jane' install where partitions were the normal /, /home, swap in a dual-boot setup with XP. The install was done via 'upgrade' with the 11.2 dvd (md5sums confirmed and install media check passed). The 'upgrade' was in reaity a fresh install that formatted / as ext4 but preserved /home as ext3. I first noticed the characters in mc, and then noticed the 'LC_** not set' messages when connecting from my laptop to the server via ssh. I understood that this was a language issue, but the language was set properly in yast -> sysconfig-editor, and in kde and gnome control panels. (I have several posts on the LC_ issues previously).
After connecting from 11.2, the usb drive I was connecting to started throwing errors and would disconnect (which started this thread originally). I can't recall whether is was a matter of hours or a day or two later when I noticed the errors in my server logs. (I connect to and manage files on my home server 10 times a day eith via ssh, sftp, smb or fish). The disk corruption on my server began after my connection from 11.2 and the errors took the form:
<snip>
Dec 3 18:05:42 nirvana kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Dec 3 18:05:42 nirvana kernel: ata3.00: BMDMA stat 0x25
Dec 3 18:05:42 nirvana kernel: ata3.00: cmd 25/00:08:33:0c:8c/00:00:34:00:00/e0 tag 0 cdb 0x0 data 4096 in
Dec 3 18:05:42 nirvana kernel: res 51/40:00:39:0c:8c/40:00:34:00:00/e0 Emask 0x9 (media error)
Dec 3 18:05:42 nirvana kernel: ata3.00: configured for UDMA/133
Dec 3 18:05:42 nirvana kernel: ata3: EH complete
Dec 3 18:05:44 nirvana kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Dec 3 18:05:44 nirvana kernel: ata3.00: BMDMA stat 0x25
Dec 3 18:05:44 nirvana kernel: ata3.00: cmd 25/00:08:33:0c:8c/00:00:34:00:00/e0 tag 0 cdb 0x0 data 4096 in
Dec 3 18:05:44 nirvana kernel: res 51/40:00:39:0c:8c/40:00:34:00:00/e0 Emask 0x9 (media error)
Dec 3 18:05:44 nirvana kernel: ata3.00: configured for UDMA/133
Dec 3 18:05:44 nirvana kernel: ata3: EH complete
Dec 3 18:05:46 nirvana kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Dec 3 18:05:46 nirvana kernel: ata3.00: BMDMA stat 0x25
Dec 3 18:05:46 nirvana kernel: ata3.00: cmd 25/00:08:33:0c:8c/00:00:34:00:00/e0 tag 0 cdb 0x0 data 4096 in
Dec 3 18:05:46 nirvana kernel: res 51/40:00:39:0c:8c/40:00:34:00:00/e0 Emask 0x9 (media error)
Dec 3 18:06:30 nirvana kernel: ata3.00: configured for UDMA/133
Dec 3 18:06:30 nirvana kernel: ata3: EH complete
Dec 3 18:06:30 nirvana kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Dec 3 18:06:30 nirvana kernel: ata3.00: BMDMA stat 0x25
Dec 3 18:06:30 nirvana kernel: ata3.00: cmd 25/00:08:33:0c:8c/00:00:34:00:00/e0 tag 0 cdb 0x0 data 4096 in
Dec 3 18:06:30 nirvana kernel: res 51/40:00:39:0c:8c/40:00:34:00:00/e0 Emask 0x9 (media error)
Dec 3 18:06:30 nirvana kernel: ata3.00: configured for UDMA/133
Dec 3 18:06:30 nirvana kernel: ata3: EH complete
Dec 3 18:06:30 nirvana kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Dec 3 18:06:30 nirvana kernel: ata3.00: BMDMA stat 0x25
Dec 3 18:06:30 nirvana kernel: ata3.00: cmd 25/00:08:33:0c:8c/00:00:34:00:00/e0 tag 0 cdb 0x0 data 4096 in
Dec 3 18:06:30 nirvana kernel: res 51/40:00:39:0c:8c/40:00:34:00:00/e0 Emask 0x9 (media error)
Dec 3 18:06:30 nirvana kernel: ata3.00: configured for UDMA/133
Dec 3 18:06:30 nirvana kernel: ata3: EH complete
Dec 3 18:06:30 nirvana kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Dec 3 18:06:30 nirvana kernel: ata3.00: BMDMA stat 0x25
Dec 3 18:06:30 nirvana kernel: ata3.00: cmd 25/00:08:33:0c:8c/00:00:34:00:00/e0 tag 0 cdb 0x0 data 4096 in
Dec 3 18:06:30 nirvana kernel: res 51/40:00:39:0c:8c/40:00:34:00:00/e0 Emask 0x9 (media error)
Dec 3 18:06:30 nirvana kernel: ata3.00: configured for UDMA/133
Dec 3 18:06:30 nirvana kernel: sd 2:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
Dec 3 18:06:30 nirvana kernel: sd 2:0:0:0: [sda] Sense Key : Medium Error [current] [descriptor]
Dec 3 18:06:30 nirvana kernel: Descriptor sense data with sense descriptors (in hex):
Dec 3 18:06:30 nirvana kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
Dec 3 18:06:30 nirvana kernel: 34 8c 0c 39
Dec 3 18:06:30 nirvana kernel: sd 2:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed
Dec 3 18:06:30 nirvana kernel: end_request: I/O error, dev sda, sector 881593401
Dec 3 18:06:30 nirvana kernel: ata3: EH complete
Dec 3 18:06:30 nirvana kernel: sd 2:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB)
Dec 3 18:06:30 nirvana kernel: sd 2:0:0:0: [sda] Write Protect is off
Dec 3 18:06:30 nirvana kernel: sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
Dec 3 18:06:30 nirvana kernel: sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO
<snip>
I was sure it was a simple coincidence that the usb disconnects just happened and would be fixed with an update, and that I just happened to start having server /home partition corruption at that time. After all, my 10.3 server has been running error free since 10.3 was released (Oct. '07 IIRC). So it was 2 years old, but in reality operates under a fairly light load mosly idling (spell check is still broke sorry;-) except for backups. So I had no reason to expect a disk failure, but figured it just happened.
Then I saw John's post discussing almost identical errors and things just seemed to curious to be coincidence. Then the threads about "Deleting corrupted files" started hitting the list.
I don't know enough about filesystems to understand how or why file corruption occurs or how different encoding/language/LC_/etc. bugs could cause or contribute to it, but I think we have a real problem with the current 11.2 x86_64 release. I know from my experience with my usb drive and my server, that the errors were directly related to connection from my new 11.2 x86_64 laptop. My 11.2 install there finally experienced complete meltdown and I had to wipe and reinstall. I have configured the laptop, but haven't had time to do too much additional testing. (not to mention not wanting to spend another 4 hours repairing the 2 disk dmraid /home on my server again -- fsck of 500G takes a long time, and hitting
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2009-12-06 at 17:37 -0600, David C. Rankin wrote:
There is a problem with 11.2 x86_64 that causes disk corruption on USB and Remote filesystems when you connect to them.
What type of filesystem, and what type of remote connection?
Dec 3 18:05:42 nirvana kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Dec 3 18:05:42 nirvana kernel: ata3.00: BMDMA stat 0x25 Dec 3 18:05:42 nirvana kernel: ata3.00: cmd 25/00:08:33:0c:8c/00:00:34:00:00/e0 tag 0 cdb 0x0 data 4096 in Dec 3 18:05:42 nirvana kernel: res 51/40:00:39:0c:8c/40:00:34:00:00/e0 Emask 0x9 (media error)
"Media error" sounds to be a hardware error.
Dec 3 18:06:30 nirvana kernel: sd 2:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed
And that is indeed a hardware error, a really bad one. End of life for hard disk, typically. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkscSzcACgkQtTMYHG2NR9XPzgCdGbO61CwJ8RGO38g16IntOsdE tAgAninlhGQ4fZaAXR0eyCilfpyuQM9l =1r6r -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 06 December 2009 18:24:13 and regarding:
On Sunday, 2009-12-06 at 17:37 -0600, David C. Rankin wrote:
There is a problem with 11.2 x86_64 that causes disk corruption on USB and Remote filesystems when you connect to them.
What type of filesystem, and what type of remote connection?
ext2
Dec 3 18:05:42 nirvana kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Dec 3 18:05:42 nirvana kernel: ata3.00: BMDMA stat 0x25 Dec 3 18:05:42 nirvana kernel: ata3.00: cmd 25/00:08:33:0c:8c/00:00:34:00:00/e0 tag 0 cdb 0x0 data 4096 in Dec 3 18:05:42 nirvana kernel: res 51/40:00:39:0c:8c/40:00:34:00:00/e0 Emask 0x9 (media error)
"Media error" sounds to be a hardware error.
Yep, that's what I thought, but it isn't. Like I said, I do NOT understand it, but from the language/encoding weirdness I saw (and still see on my 11.2 x86_64 laptop) I would be willing to bet that there is a problem with the remote execution of filesystem commands that somehow garbles the remote filesystem. I have spent a lot of time on this and I have done a great deal of comparison between connecting remotely with XP, 10.3, 11.0, Arch Linux, and the 11.2 laptop and the only box that causes corruption over usb or remote ssh/smb/fish/sftp is the 11.2 laptop. (I'm using the same laptop right now (I have 3 hard drives for it) running Arch Linux and it is working perfectly). I also have 10.3 on the 3rd drive and both Arch Linux, 10.3 and 11.0 (on the drive before 11.2) work perfectly with usb and remotely with 0 zero errors or corruption. Connection from this laptop with 11.2 is the only instance where I have consistent corruption issues. Also, (I don't see how this could be related, but you never know), 11.2 x86_64 has terrible video driver issues on this box. Wild guess, but maybe there is a hardware error occurring related to a xorg/mesa or drm call that is affecting the remote communication??? (like I said very wild guess). However, after the 11.2 drm update, X is dead on 11.2. The only way I can get x to run is to explicitly use the radeon "Device" in xorg.conf and then the video will make you sea-sick. Enlightenment E16 will not run (you can start it, but all decorations are gone and backgrounds are blank) Compiz whitescreens (compositing failure) and desktop effects can NOT be enabled in kde4. Strangely compiz works fine in gnome... (I don't think it is related, but you guys that know more about video interrupt interaction with the other hardware busses will have to ponder the thought)
Dec 3 18:06:30 nirvana kernel: sd 2:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed
And that is indeed a hardware error, a really bad one. End of life for hard disk, typically.
Again, that is what I thought, but it was just corruption caused by the remote connection. Here are the logs since the last repair and 300G of file transfers:
Here is the sequence and history of the errors beginning with the connection from my 11.2 x86_64 box. The full logs from __ are here:
The first error occurs withinn 20 minutes of my first connection from my 11.2 laptop and su to root. I had installed on 11/17 at approximately 00:00 UTC (18:00 on the 16th localtime) The server is nirvana, my laptop is alchemy connecting at 192.168.6.102. I have marked the specific events with '---' at the start:
---
Nov 17 03:08:41 nirvana sshd[22185]: Accepted publickey for david from 192.168.6.102 port 59448 ssh2
Nov 17 03:08:46 nirvana su: (to root) david on /dev/pts/3
Nov 17 03:10:01 nirvana /usr/sbin/cron[23394]: (david) CMD (/home/david/linux/scripts/Learn_as_spam_cron)
Nov 17 03:12:01 nirvana /usr/sbin/cron[23414]: (drr) CMD (/usr/local/bin/Learn_as_spam_cron)
Nov 17 03:14:01 nirvana /usr/sbin/cron[23430]: (deborah) CMD (/usr/local/bin/Learn_as_spam_cron)
Nov 17 03:16:01 nirvana /usr/sbin/cron[23489]: (zachry) CMD (/usr/local/bin/Learn_as_spam_cron)
Nov 17 03:18:01 nirvana /usr/sbin/cron[24289]: (sydney) CMD (/usr/local/bin/Learn_as_spam_cron)
Nov 17 03:18:29 nirvana dhcpd: Wrote 0 deleted host decls to leases file.
Nov 17 03:18:29 nirvana dhcpd: Wrote 0 new dynamic host decls to leases file.
Nov 17 03:18:29 nirvana dhcpd: Wrote 38 leases to leases file.
Nov 17 03:20:00 nirvana dhcpd: DHCPREQUEST for 192.168.6.120 from 00:25:00:df:fe:2c (iPod-touch-2) via eth0
Nov 17 03:20:00 nirvana dhcpd: DHCPACK on 192.168.6.120 to 00:25:00:df:fe:2c (iPod-touch-2) via eth0
Nov 17 03:21:26 nirvana dhcpd: DHCPREQUEST for 192.168.6.120 from 00:25:00:df:fe:2c (iPod-touch-2) via eth0
Nov 17 03:21:26 nirvana dhcpd: DHCPACK on 192.168.6.120 to 00:25:00:df:fe:2c (iPod-touch-2) via eth0
Nov 17 03:24:11 nirvana dhcpd: DHCPREQUEST for 192.168.6.120 from 00:25:00:df:fe:2c (iPod-touch-2) via eth0
Nov 17 03:24:11 nirvana dhcpd: DHCPACK on 192.168.6.120 to 00:25:00:df:fe:2c (iPod-touch-2) via eth0
Nov 17 03:24:11 nirvana dhcpd: DHCPDISCOVER from 00:25:00:df:fe:2c (iPod-touch-2) via eth0
Nov 17 03:24:12 nirvana dhcpd: DHCPOFFER on 192.168.6.120 to 00:25:00:df:fe:2c (iPod-touch-2) via eth0
---
Nov 17 03:28:04 nirvana shadow[24998]: group already exists - group=ntadmin, by=0
Nov 17 03:28:04 nirvana dbus-daemon: Unable to reload configuration: Element
On Sun, Dec 6, 2009 at 6:37 PM, David C. Rankin
There is a problem with 11.2 x86_64 that causes disk corruption on USB and Remote filesystems when you connect to them. I have probably spent the better part Dec 3 18:05:42 nirvana kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Dec 3 18:05:42 nirvana kernel: ata3.00: BMDMA stat 0x25 Dec 3 18:05:42 nirvana kernel: ata3.00: cmd 25/00:08:33:0c:8c/00:00:34:00:00/e0 tag 0 cdb 0x0 data 4096 in Dec 3 18:05:42 nirvana kernel: res 51/40:00:39:0c:8c/40:00:34:00:00/e0 Emask 0x9 (media error) Dec 3 18:05:42 nirvana kernel: ata3.00: configured for UDMA/133 Dec 3 18:05:42 nirvana kernel: ata3: EH complete Dec 3 18:05:44 nirvana kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
I had similar problems on my son's machine with 11.2/x86. It's an AthlonXP 3200+. I'll have to check the motherboard(Abit something). When I used the onboard IDE controller, the DMA mode would finally drop back to UDMA/33. I was using an 80GB that was fine and tested several times in other machines. I did get some corruption. However, I pulled the drive and used the onboard SATA controller which seemed to be ok. However, I don't have the machine handy ATM. I figured it was a bug in the chipset, but couldn't find a way to fix it. I guess I'll install 11.0 on it and see what happens. Probably won't have time to mess with it before the weekend(if then - moving and his machine is packed up).... Wish I had done more troubleshooting now.. Oh well. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
Carlos E. R. -
David C. Rankin -
Hans Krueger -
John Andersen -
Larry Stotler