Linux Archive - Bug#519158: linux-image-2.6.26-1-686: ATA subsystem crashes and renders single drive unusable

On Tue, Mar 10, 2009 at 06:56:48PM +0100, Michael Rumpler wrote:
> Package: linux-image-2.6.26-1-686
> Version: 2.6.26-13
> Severity: important
>
>
> I am using the following HW configuration:
> Mainboard: Intel D945GCLF2 Mainboard
> Additional SATA Controller: Silicon Image, Inc. SiI 3124
>
> Connected directly to the board: 1 Transcend TS32GSSD25S-M SATA SSD Rev: V082
> Connected to the SiI controller: 3 WDC WD5000ABPS-0 Rev: 02.0
>
> >From time to time (differs from 1 to 4 weeks) the system gets to some
> state where the following kernel messages are logged:
>
> Mar 8 21:19:08 atom kernel: [1953069.141042] ------------[ cut here ]------------
> Mar 8 21:19:08 atom kernel: [1953069.141042] WARNING: at drivers/ata/libata-sff.c:1321 ata_sff_hsm_move+0x5ff/0x674 [libata]()
> Mar 8 21:19:08 atom kernel: [1953069.141042] Modules linked in: tun nfsd auth_rpcgss exportfs nfs lockd nfs_acl sunrpc ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack ip_tables x_tables ipv6 usb_storage smsc47m192 hwmon_vid loop serio_raw rng_core button psmouse asix usbnet snd_pcm snd_timer snd iTCO_wdt i2c_i801 soundcore mii snd_page_alloc i2c_core pcspkr intel_agp agpgart joydev evdev ext3 jbd mbcache dm_mirror dm_log dm_snapshot dm_mod raid456 md_mod async_xor async_memcpy async_tx xor sd_mod ata_piix usbhid hid ff_memless ata_generic sata_sil24 libata scsi_mod piix dock ide_pci_generic ide_core ehci_hcd uhci_hcd usbcore r8169 thermal processor fan thermal_sys
> Mar 8 21:19:08 atom kernel: [1953069.141042] Pid: 0, comm: swapper Tainted: G W 2.6.26-1-686 #1
> Mar 8 21:19:08 atom kernel: [1953069.141042] [<c012256f>] warn_on_slowpath+0x40/0x66
> Mar 8 21:19:08 atom kernel: [1953069.141042] [<c01318e9>] autoremove_wake_function+0xd/0x2d
> Mar 8 21:19:08 atom kernel: [1953069.141042] [<c011845d>] __wake_up_common+0x2e/0x58
> Mar 8 21:19:08 atom kernel: [1953069.141042] [<c011a641>] __wake_up+0x29/0x39
> Mar 8 21:19:08 atom kernel: [1953069.141042] [<f8940b46>] md_wakeup_thread+0x1e/0x20 [md_mod]
> Mar 8 21:19:08 atom kernel: [1953069.141042] [<f8974906>] release_stripe+0x21/0x2e [raid456]
> Mar 8 21:19:08 atom kernel: [1953069.141042] [<f897837a>] raid5_end_write_request+0x0/0x99 [raid456]
> Mar 8 21:19:08 atom kernel: [1953069.141042] [<f88e73d0>] scsi_run_queue+0x200/0x219 [scsi_mod]
> Mar 8 21:19:08 atom kernel: [1953069.141042] [<c01d0175>] elv_queue_empty+0x1d/0x1e
> Mar 8 21:19:08 atom kernel: [1953069.141042] [<f89111d5>] ata_sff_hsm_move+0x5ff/0x674 [libata]
> Mar 8 21:19:08 atom kernel: [1953069.141042] [<f88e7b3b>] scsi_end_request+0x62/0x6b [scsi_mod]
> Mar 8 21:19:08 atom kernel: [1953069.141042] [<f88e863b>] scsi_io_completion+0x1a6/0x363 [scsi_mod]
> Mar 8 21:19:08 atom kernel: [1953069.141042] [<f8911e88>] ata_sff_interrupt+0x127/0x19f [libata]
> Mar 8 21:19:08 atom kernel: [1953069.141042] [<c0151fd2>] handle_IRQ_event+0x23/0x51
> Mar 8 21:19:08 atom kernel: [1953069.141042] [<c01530d1>] handle_fasteoi_irq+0x71/0xa4
> Mar 8 21:19:08 atom kernel: [1953069.141042] [<c0105f3a>] do_IRQ+0x4d/0x63
> Mar 8 21:19:08 atom kernel: [1953069.141043] [<c0108bbf>] mwait_idle+0x0/0x3d
> Mar 8 21:19:08 atom kernel: [1953069.141043] [<c01042a7>] common_interrupt+0x23/0x28
> Mar 8 21:19:08 atom kernel: [1953069.141043] [<c0108bbf>] mwait_idle+0x0/0x3d
> Mar 8 21:19:08 atom kernel: [1953069.141043] [<c0108bee>] mwait_idle+0x2f/0x3d
> Mar 8 21:19:08 atom kernel: [1953069.141043] [<c01025ce>] cpu_idle+0xab/0xcb
> Mar 8 21:19:08 atom kernel: [1953069.141043] =======================
>
> after that the SSD drive connected to the board itself starts to make
> troubles:
>
> Mar 8 21:19:08 atom kernel: [1953069.141042] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> Mar 8 21:19:08 atom kernel: [1953069.141042] ata5.00: BMDMA stat 0x26
> Mar 8 21:19:08 atom kernel: [1953069.141042] ata5.00: cmd ca/00:08:a7:20:14/00:00:00:00:00/e0 tag 0 dma 4096 out
> Mar 8 21:19:08 atom kernel: [1953069.141042] res 51/40:08:a7:20:14/00:00:00:00:00/e0 Emask 0x29 (host bu s error)
> Mar 8 21:19:08 atom kernel: [1953069.141042] ata5.00: status: { DRDY ERR }
> Mar 8 21:19:08 atom kernel: [1953069.141042] ata5.00: error: { UNC }
> Mar 8 21:19:38 atom kernel: [1953106.145781] ata5.00: qc timeout (cmd 0xef)
> Mar 8 21:19:38 atom kernel: [1953106.145818] ata5.00: failed to set xfermode (err_mask=0x4)
> Mar 8 21:19:38 atom kernel: [1953106.145845] ata5: failed to recover some devices, retrying in 5 secs
> Mar 8 21:19:48 atom kernel: [1953119.090028] ata5: link is slow to respond, please be patient (ready=0)
> Mar 8 21:19:53 atom kernel: [1953126.002047] ata5: device not ready (errno=-16), forcing hardreset
> Mar 8 21:19:53 atom kernel: [1953126.002091] ata5: soft resetting link
> Mar 8 21:19:58 atom kernel: [1953132.995359] ata5: link is slow to respond, please be patient (ready=0)
> Mar 8 21:20:03 atom kernel: [1953139.929986] ata5: SRST failed (errno=-16)
> Mar 8 21:20:03 atom kernel: [1953139.930027] ata5: soft resetting link
> Mar 8 21:20:08 atom kernel: [1953146.559721] ata5: link is slow to respond, please be patient (ready=0)
> Mar 8 21:20:13 atom kernel: [1953153.430162] ata5: SRST failed (errno=-16)
> Mar 8 21:20:13 atom kernel: [1953153.430162] ata5: soft resetting link
> Mar 8 21:20:18 atom kernel: [1953161.399126] ata5: link is slow to respond, please be patient (ready=0)
> Mar 8 21:20:48 atom kernel: [1953202.372705] ata5: SRST failed (errno=-16)
> Mar 8 21:20:48 atom kernel: [1953202.372705] ata5: soft resetting link
> Mar 8 21:20:53 atom kernel: [1953209.034395] ata5: SRST failed (errno=-16)
> Mar 8 21:20:53 atom kernel: [1953209.034431] ata5: reset failed, giving up
> Mar 8 21:20:53 atom kernel: [1953209.034459] ata5.00: disabled
> Mar 8 21:20:58 atom kernel: [1953216.334722] ata5: link is slow to respond, please be patient (ready=0)
> Mar 8 21:21:03 atom kernel: [1953223.610483] ata5: device not ready (errno=-16), forcing hardreset
> Mar 8 21:21:03 atom kernel: [1953223.610527] ata5: soft resetting link
> Mar 8 21:21:08 atom kernel: [1953230.476517] ata5: link is slow to respond, please be patient (ready=0)
> Mar 8 21:21:13 atom kernel: [1953237.170795] ata5: SRST failed (errno=-16)
> Mar 8 21:21:13 atom kernel: [1953237.170835] ata5: soft resetting link
> Mar 8 21:21:18 atom kernel: [1953244.294064] ata5: link is slow to respond, please be patient (ready=0)
> Mar 8 21:21:23 atom kernel: [1953251.343216] ata5: SRST failed (errno=-16)
> Mar 8 21:21:23 atom kernel: [1953251.343258] ata5: soft resetting link
> Mar 8 21:21:28 atom kernel: [1953257.898305] ata5: link is slow to respond, please be patient (ready=0)
> Mar 8 21:21:58 atom kernel: [1953297.557344] ata5: SRST failed (errno=-16)
> Mar 8 21:21:58 atom kernel: [1953297.557383] ata5: soft resetting link
> Mar 8 21:22:03 atom kernel: [1953303.191175] ata5: SRST failed (errno=-16)
> Mar 8 21:22:03 atom kernel: [1953303.191210] ata5: reset failed, giving up
> Mar 8 21:22:03 atom kernel: [1953303.191252] ata5: EH complete
> Mar 8 21:19:08 atom kernel: [1953069.141042] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> Mar 8 21:19:08 atom kernel: [1953069.141042] ata5.00: BMDMA stat 0x26
> Mar 8 21:19:08 atom kernel: [1953069.141042] ata5.00: cmd ca/00:08:a7:20:14/00:00:00:00:00/e0 tag 0 dma 4096 out
> Mar 8 21:19:08 atom kernel: [1953069.141042] res 51/40:08:a7:20:14/00:00:00:00:00/e0 Emask 0x29 (host bu s error)
> Mar 8 21:19:08 atom kernel: [1953069.141042] ata5.00: status: { DRDY ERR }
> Mar 8 21:19:08 atom kernel: [1953069.141042] ata5.00: error: { UNC }
> Mar 8 21:19:38 atom kernel: [1953106.145781] ata5.00: qc timeout (cmd 0xef)
> Mar 8 21:19:38 atom kernel: [1953106.145818] ata5.00: failed to set xfermode (err_mask=0x4)
> Mar 8 21:19:38 atom kernel: [1953106.145845] ata5: failed to recover some devices, retrying in 5 secs
> Mar 8 21:19:48 atom kernel: [1953119.090028] ata5: link is slow to respond, please be patient (ready=0)
> Mar 8 21:19:53 atom kernel: [1953126.002047] ata5: device not ready (errno=-16), forcing hardreset
> Mar 8 21:19:53 atom kernel: [1953126.002091] ata5: soft resetting link
> Mar 8 21:19:58 atom kernel: [1953132.995359] ata5: link is slow to respond, please be patient (ready=0)
> Mar 8 21:20:03 atom kernel: [1953139.929986] ata5: SRST failed (errno=-16)
> Mar 8 21:20:03 atom kernel: [1953139.930027] ata5: soft resetting link
> Mar 8 21:20:08 atom kernel: [1953146.559721] ata5: link is slow to respond, please be patient (ready=0)
> Mar 8 21:20:13 atom kernel: [1953153.430162] ata5: SRST failed (errno=-16)
> Mar 8 21:20:13 atom kernel: [1953153.430162] ata5: soft resetting link
> Mar 8 21:20:18 atom kernel: [1953161.399126] ata5: link is slow to respond, please be patient (ready=0)
> Mar 8 21:20:48 atom kernel: [1953202.372705] ata5: SRST failed (errno=-16)
> Mar 8 21:20:48 atom kernel: [1953202.372705] ata5: soft resetting link
> Mar 8 21:20:53 atom kernel: [1953209.034395] ata5: SRST failed (errno=-16)
> Mar 8 21:20:53 atom kernel: [1953209.034431] ata5: reset failed, giving up
> Mar 8 21:20:53 atom kernel: [1953209.034459] ata5.00: disabled
> Mar 8 21:20:58 atom kernel: [1953216.334722] ata5: link is slow to respond, please be patient (ready=0)
> Mar 8 21:21:03 atom kernel: [1953223.610483] ata5: device not ready (errno=-16), forcing hardreset
> Mar 8 21:21:03 atom kernel: [1953223.610527] ata5: soft resetting link
> Mar 8 21:21:08 atom kernel: [1953230.476517] ata5: link is slow to respond, please be patient (ready=0)
> Mar 8 21:21:13 atom kernel: [1953237.170795] ata5: SRST failed (errno=-16)
> Mar 8 21:21:13 atom kernel: [1953237.170835] ata5: soft resetting link
> Mar 8 21:21:18 atom kernel: [1953244.294064] ata5: link is slow to respond, please be patient (ready=0)
> Mar 8 21:21:23 atom kernel: [1953251.343216] ata5: SRST failed (errno=-16)
> Mar 8 21:21:23 atom kernel: [1953251.343258] ata5: soft resetting link
> Mar 8 21:21:28 atom kernel: [1953257.898305] ata5: link is slow to respond, please be patient (ready=0)
> Mar 8 21:21:58 atom kernel: [1953297.557344] ata5: SRST failed (errno=-16)
> Mar 8 21:21:58 atom kernel: [1953297.557383] ata5: soft resetting link
> Mar 8 21:22:03 atom kernel: [1953303.191175] ata5: SRST failed (errno=-16)
> Mar 8 21:22:03 atom kernel: [1953303.191210] ata5: reset failed, giving up
> Mar 8 21:22:03 atom kernel: [1953303.191252] ata5: EH complete
> Mar 8 21:22:03 atom kernel: [1953303.191313] sd 4:0:0:0: [sdd] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_ OK,SUGGEST_OK
> Mar 8 21:22:03 atom kernel: [1953303.191381] end_request: I/O error, dev sdd, sector 1319079
> Mar 8 21:22:03 atom kernel: [1953303.191423] Buffer I/O error on device sdd1, logical block 164877
> Mar 8 21:22:03 atom kernel: [1953303.191460] lost page write due to I/O error on sdd1
> Mar 8 21:22:03 atom kernel: [1953303.195153] sd 4:0:0:0: [sdd] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
> Mar 8 21:22:03 atom kernel: [1953303.195153] end_request: I/O error, dev sdd, sector 1319095
> Mar 8 21:22:03 atom kernel: [1953303.195153] Buffer I/O error on device sdd1, logical block 164879
> Mar 8 21:22:03 atom kernel: [1953303.195153] lost page write due to I/O error on sdd1
> Mar 8 21:22:03 atom kernel: [1953303.407178] sd 4:0:0:0: [sdd] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
> Mar 8 21:22:03 atom kernel: [1953303.407199] end_request: I/O error, dev sdd, sector 1319143
> Mar 8 21:22:03 atom kernel: [1953303.407217] Buffer I/O error on device sdd1, logical block 164885
> Mar 8 21:22:03 atom kernel: [1953303.407226] lost page write due to I/O error on sdd1
> Mar 8 21:22:03 atom kernel: [1953303.407264] sd 4:0:0:0: [sdd] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
> Mar 8 21:22:03 atom kernel: [1953303.407275] end_request: I/O error, dev sdd, sector 29672591
> Mar 8 21:22:03 atom kernel: [1953303.407283] Buffer I/O error on device sdd1, logical block 3709066
> Mar 8 21:22:03 atom kernel: [1953303.407291] lost page write due to I/O error on sdd1
> Mar 8 21:22:03 atom kernel: [1953303.407345] sd 4:0:0:0: [sdd] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
> Mar 8 21:22:03 atom kernel: [1953303.407362] end_request: I/O error, dev sdd, sector 1552671
> Mar 8 21:22:03 atom kernel: [1953303.407378] Buffer I/O error on device sdd1, logical block 194076
> Mar 8 21:22:03 atom kernel: [1953303.407386] lost page write due to I/O error on sdd1
> Mar 8 21:22:03 atom kernel: [1953303.407399] Buffer I/O error on device sdd1, logical block 194077
> Mar 8 21:22:03 atom kernel: [1953303.407409] lost page write due to I/O error on sdd1
> Mar 8 21:22:03 atom kernel: [1953303.407422] Buffer I/O error on device sdd1, logical block 194078
> Mar 8 21:22:03 atom kernel: [1953303.407432] lost page write due to I/O error on sdd1
> Mar 8 21:22:03 atom kernel: [1953303.407467] sd 4:0:0:0: [sdd] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
> Mar 8 21:22:03 atom kernel: [1953303.407484] end_request: I/O error, dev sdd, sector 1553143
> Mar 8 21:22:03 atom kernel: [1953303.407495] Buffer I/O error on device sdd1, logical block 194135
> Mar 8 21:22:03 atom kernel: [1953303.407505] lost page write due to I/O error on sdd1
> Mar 8 21:22:03 atom kernel: [1953303.407522] Buffer I/O error on device sdd1, logical block 194136
> Mar 8 21:22:03 atom kernel: [1953303.407533] lost page write due to I/O error on sdd1
> Mar 8 21:22:03 atom kernel: [1953303.407565] sd 4:0:0:0: [sdd] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
> Mar 8 21:22:03 atom kernel: [1953303.407576] end_request: I/O error, dev sdd, sector 1553487
> Mar 8 21:22:03 atom kernel: [1953303.407584] Buffer I/O error on device sdd1, logical block 194178
> Mar 8 21:22:03 atom kernel: [1953303.407590] lost page write due to I/O error on sdd1
> Mar 8 21:22:03 atom kernel: [1953303.407619] sd 4:0:0:0: [sdd] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
> Mar 8 21:22:03 atom kernel: [1953303.407631] end_request: I/O error, dev sdd, sector 1555327
> Mar 8 21:22:03 atom kernel: [1953303.407660] sd 4:0:0:0: [sdd] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
> Mar 8 21:22:03 atom kernel: [1953303.407670] end_request: I/O error, dev sdd, sector 1555471
> Mar 8 21:22:03 atom kernel: [1953303.407805] sd 4:0:0:0: [sdd] READ CAPACITY failed
> Mar 8 21:22:03 atom kernel: [1953303.407814] sd 4:0:0:0: [sdd] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
> Mar 8 21:22:03 atom kernel: [1953303.407823] sd 4:0:0:0: [sdd] Sense not available.
> Mar 8 21:22:03 atom kernel: [1953303.407823] sd 4:0:0:0: [sdd] Sense not available.
> Mar 8 21:22:03 atom kernel: [1953303.407883] sd 4:0:0:0: [sdd] Write Protect is off
> Mar 8 21:22:03 atom kernel: [1953303.407891] sd 4:0:0:0: [sdd] Mode Sense: 00 00 00 00
> Mar 8 21:22:03 atom kernel: [1953303.407948] sd 4:0:0:0: [sdd] Asking for cache data failed
> Mar 8 21:22:03 atom kernel: [1953303.407955] sd 4:0:0:0: [sdd] Assuming drive cache: write through
> Mar 8 21:22:03 atom kernel: [1953303.195153] Aborting journal on device sdd1.
> Mar 8 21:22:03 atom kernel: [1953303.412058] EXT3-fs error (device sdd1) in ext3_reserve_inode_write: Journal has aborted
> Mar 8 21:22:03 atom kernel: [1953303.412599] Remounting filesystem read-only
>
> directly after that another trace is issued:
>
> Mar 8 21:22:03 atom kernel: [1953303.195153] ------------[ cut here ]------------
> Mar 8 21:22:03 atom kernel: [1953303.195153] WARNING: at fs/buffer.c:1186 mark_buffer_dirty+0x20/0x6a()
> Mar 8 21:22:03 atom kernel: [1953303.195153] Modules linked in: tun nfsd auth_rpcgss exportfs nfs lockd nfs_acl sunrpc ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack ip_tables x_tables ipv6 usb_storage smsc47m192 hwmon_vid loop serio_raw rng_core button psmouse asix usbnet snd_pcm snd_timer snd iTCO_wdt i2c_i801 soundcore mii snd_page_alloc i2c_core pcspkr intel_agp agpgart joydev evdev ext3 jbd mbcache dm_mirror dm_log dm_snapshot dm_mod raid456 md_mod async_xor async_memcpy async_tx xor sd_mod ata_piix usbhid hid ff_memless ata_generic sata_sil24 libata scsi_mod piix dock ide_pci_generic ide_core ehci_hcd uhci_hcd usbcore r8169 thermal processor fan thermal_sys
> Mar 8 21:22:03 atom kernel: [1953303.195153] Pid: 1169, comm: kjournald Tainted: G W 2.6.26-1-686 #1
> Mar 8 21:22:03 atom kernel: [1953303.195153] [<c012256f>] warn_on_slowpath+0x40/0x66
> Mar 8 21:22:03 atom kernel: [1953303.195153] [<c0122a10>] release_console_sem+0x173/0x18c
> Mar 8 21:22:03 atom kernel: [1953303.195153] [<c0118c9b>] update_curr+0x47/0x79
> Mar 8 21:22:03 atom kernel: [1953303.195153] [<c0119d2e>] dequeue_entity+0x13/0x9b
> Mar 8 21:22:03 atom kernel: [1953303.195153] [<c0119c1f>] __dequeue_entity+0x1f/0x71
> Mar 8 21:22:03 atom kernel: [1953303.195153] [<c010296e>] __switch_to+0xa5/0x125
> Mar 8 21:22:03 atom kernel: [1953303.195153] [<c011d3bd>] hrtick_set+0x7a/0xd8
> Mar 8 21:22:03 atom kernel: [1953303.195153] [<c01e4cf6>] __percpu_counter_add+0x4f/0x71
> Mar 8 21:22:03 atom kernel: [1953303.195153] [<c0190293>] mark_buffer_dirty+0x20/0x6a
> Mar 8 21:22:03 atom kernel: [1953303.195153] [<f895f1f9>] __journal_unfile_buffer+0x8/0x11 [jbd]
> Mar 8 21:22:03 atom kernel: [1953303.195153] [<f895f2c3>] journal_refile_buffer+0x35/0x52 [jbd]
> Mar 8 21:22:03 atom kernel: [1953303.195153] [<f8960b5f>] journal_commit_transaction+0x4b4/0xb3d [jbd]
> Mar 8 21:22:03 atom kernel: [1953303.195153] [<c01318dc>] autoremove_wake_function+0x0/0x2d
> Mar 8 21:22:03 atom kernel: [1953303.195153] [<c0129b10>] try_to_del_timer_sync+0x44/0x4a
> Mar 8 21:22:03 atom kernel: [1953303.195153] [<f8963454>] kjournald+0xa5/0x1c6 [jbd]
> Mar 8 21:22:03 atom kernel: [1953303.195153] [<c01318dc>] autoremove_wake_function+0x0/0x2d
> Mar 8 21:22:03 atom kernel: [1953303.195153] [<f89633af>] kjournald+0x0/0x1c6 [jbd]
> Mar 8 21:22:03 atom kernel: [1953303.195153] [<c013181b>] kthread+0x38/0x5d
> Mar 8 21:22:03 atom kernel: [1953303.195153] [<c01317e3>] kthread+0x0/0x5d
> Mar 8 21:22:03 atom kernel: [1953303.412599] [<c01044f3>] kernel_thread_helper+0x7/0x10
> Mar 8 21:22:03 atom kernel: [1953303.412694] =======================
> Mar 8 21:22:03 atom kernel: [1953303.412720] ---[ end trace 1916ed0ecf4dd5f1 ]---
>
> At first sight i thought the SSD is broken and exchanged it with a new
> one of the same type. But th problem remained.
> After all that stuff the SSD is unreadable, the rest of the system (the
> other 3 drives) work without problems.

can you try 2.6.28 sid snapshot, see sid aptline
-> http://wiki.debian.org/DebianKernel

--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org