linux-kernel - Re: intel ahci problem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Mon, 04 Feb 2008 10:02:26 +0300
From:	Evgen L <evgen@....ru>
To:	Tejun Heo <htejun@...il.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: intel ahci problem

Tejun Heo wrote:
> Evgen L wrote:
>   
>> Hi all
>>
>> I have a problem with my Intel SR1550 server (S5000PAL motheboard,
>> SATA/SAS controller, 5 SATA HDD Seagate ST9120822AS ).
>> The four drivers are in two md raid1, which striping by lvm and one
>> drive used separately. I have problem like below with two different
>> drives (ata3 or ata4) and ata5. I look problem like this with RedHat 
>> 2.6.18-53 kernel, 2.6.24-rc8, and today 2.6.24-git5. I reading about any
>> problems like this in lkml.org. There can be this message will help to
>> fix this issue.
>> The complete dmesg in attachment.
>>     
>
> Please post full dmesg including boot log and errors and the result
> "lspci -nn".
>
>   
It's the result of mirror recovery, the next result mkfs.xfs /dev/sde1. 
After that errors, the disks will be find after reset server by power.
The complete dmesg and lspci  in attachments.

md: bind<sdd1>
RAID1 conf printout:
 --- wd:1 rd:2
 disk 0, wo:0, o:1, dev:sdc1
 disk 1, wo:1, o:1, dev:sdd1
md: recovery of RAID array md2
md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
md: using maximum available idle IO bandwidth (but not more than 200000 
KB/sec) for recovery.
md: using 128k window, over a total of 117218176 blocks.
ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata4.00: cmd e7/00:00:00:00:00/00:00:00:00:00/a0 tag 0
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata4.00: status: { DRDY }
ata4: hard resetting link
ata4: port is slow to respond, please be patient (Status 0x80)
ata4: softreset failed (device not ready)
ata4: hard resetting link
ata4: port is slow to respond, please be patient (Status 0x80)
ata4: softreset failed (device not ready)
ata4: hard resetting link
ata4: port is slow to respond, please be patient (Status 0x80)
ata4: softreset failed (device not ready)
ata4: limiting SATA link speed to 1.5 Gbps
ata4: hard resetting link
ata4: softreset failed (device not ready)
ata4: reset failed, giving up
ata4.00: disabled
ata4: EH complete
sd 3:0:0:0: [sdd] Result: hostbyte=DID_BAD_TARGET 
driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdd, sector 234436415
md: super_written gets error=-5, uptodate=0
raid1: Disk failure on sdd1, disabling device.
        Operation continuing on 1 devices
sd 3:0:0:0: [sdd] Result: hostbyte=DID_BAD_TARGET 
driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdd, sector 1764415
sd 3:0:0:0: [sdd] Result: hostbyte=DID_BAD_TARGET 
driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdd, sector 1765439
sd 3:0:0:0: [sdd] Result: hostbyte=DID_BAD_TARGET 
driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdd, sector 1766463
sd 3:0:0:0: [sdd] Result: hostbyte=DID_BAD_TARGET 
driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdd, sector 1767487
sd 3:0:0:0: [sdd] Result: hostbyte=DID_BAD_TARGET 
driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdd, sector 1767615
md: md2: recovery done.
RAID1 conf printout:

+++++++++++++++++++++++

SGI XFS with ACLs, security attributes, realtime, large block numbers, 
no debug enabled
SGI XFS Quota Management subsystem
XFS mounting filesystem sde1
Ending clean XFS mount for filesystem: sde1
sd 4:0:0:0: [sde] Result: hostbyte=DID_OK 
driverbyte=DRIVER_TIMEOUT,SUGGEST_OK
end_request: I/O error, dev sde, sector 839735
sd 4:0:0:0: [sde] Result: hostbyte=DID_OK 
driverbyte=DRIVER_TIMEOUT,SUGGEST_OK
end_request: I/O error, dev sde, sector 841783
sd 4:0:0:0: [sde] Result: hostbyte=DID_OK 
driverbyte=DRIVER_TIMEOUT,SUGGEST_OK
end_request: I/O error, dev sde, sector 842807
sd 4:0:0:0: [sde] Result: hostbyte=DID_OK 
driverbyte=DRIVER_TIMEOUT,SUGGEST_OK
end_request: I/O error, dev sde, sector 845879
sd 4:0:0:0: [sde] Result: hostbyte=DID_OK 
driverbyte=DRIVER_TIMEOUT,SUGGEST_OK
end_request: I/O error, dev sde, sector 902223
sd 4:0:0:0: [sde] Result: hostbyte=DID_OK 
driverbyte=DRIVER_TIMEOUT,SUGGEST_OK
end_request: I/O error, dev sde, sector 908367
Buffer I/O error on device sde1, logical block 104703
lost page write due to I/O error on sde1
Buffer I/O error on device sde1, logical block 104704
lost page write due to I/O error on sde1
Buffer I/O error on device sde1, logical block 104705
lost page write due to I/O error on sde1
Buffer I/O error on device sde1, logical block 104706
lost page write due to I/O error on sde1
Buffer I/O error on device sde1, logical block 104707
lost page write due to I/O error on sde1
Buffer I/O error on device sde1, logical block 104708
lost page write due to I/O error on sde1
Buffer I/O error on device sde1, logical block 104709
lost page write due to I/O error on sde1
Buffer I/O error on device sde1, logical block 104710
lost page write due to I/O error on sde1
Buffer I/O error on device sde1, logical block 104711
lost page write due to I/O error on sde1
Buffer I/O error on device sde1, logical block 104712
lost page write due to I/O error on sde1



View attachment "lspci_nn" of type "text/plain" (1056 bytes)

View attachment "dmesg" of type "text/plain" (37017 bytes)