Le 25.11.2007 21:39, Laurent Riffard a écrit :
> Le 25.11.2007 08:37, James Bottomley a écrit :
>> On Sat, 2007-11-24 at 23:59 +0100, Laurent Riffard wrote:
>>> Le 24.11.2007 14:26, James Bottomley a écrit :
>>>> OK, could you post dmesgs again, please. I actually tested this
>>> with an
>>>> aic79xx card, and for me it does cause Domain Validation to succeed
>>>> again.
>>> James,
>>>
>>> Here is a dmesg produced by 2.6.24-rc3-mm1 + your patch "separates
>>> the
>>> BLOCK and QUIESCE states
>>> correctly" (http://lkml.org/lkml/2007/11/24/8).
>>>
[...]
>>> [ 25.521256] scsi0 : pata_via
>>> [ 25.521711] scsi1 : pata_via
>>> [ 25.524089] ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xb800 irq 14
>>> [ 25.524176] ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xb808 irq 15
>>> [ 25.683141] ata1.00: ATA-5: ST340016A, 3.75, max UDMA/100
>>> [ 25.683208] ata1.00: 78165360 sectors, multi 16: LBA
>>> [ 25.683475] ata1.01: ATA-7: Maxtor 6Y080L0, YAR41BW0, max UDMA/133
>>> [ 25.684116] ata1.01: 160086528 sectors, multi 16: LBA
>>> [ 25.691127] ata1.00: configured for UDMA/100
>>> [ 25.699142] ata1.01: configured for UDMA/100
>>> [ 26.170860] ata2.00: ATAPI: HL-DT-ST DVDRAM GSA-4165B, DL05, max UDMA/33
>>> [ 26.171562] ata2.01: ATAPI: CD-950E/AKU, A4Q, max MWDMA2, CDB intr
>>> [ 26.330839] ata2.00: configured for UDMA/33
>>> [ 26.490828] ata2.01: configured for MWDMA2
>>> [ 26.503014] scsi 0:0:0:0: Direct-Access ATA ST340016A 3.75 PQ: 0 ANSI: 5
>>> [ 26.504670] scsi 0:0:1:0: Direct-Access ATA Maxtor 6Y080L0 YAR4 PQ: 0 ANSI: 5
>>> [ 26.509842] scsi 1:0:0:0: CD-ROM HL-DT-ST DVDRAM GSA-4165B DL05 PQ: 0 ANSI: 5
>>> [ 26.511673] scsi 1:0:1:0: CD-ROM E-IDE CD-950E/AKU A4Q PQ: 0 ANSI: 5
>> [...]
>>> [ 60.216113] sd 0:0:0:0: [sda] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK
>>> [ 60.216124] end_request: I/O error, dev sda, sector 16460
>> I think this one's quite easy: PATA devices in libata are queue depth 1
>> (since they don't do NCQ). Thus, they're peculiarly sensitive to the
>> bug where we fail over queue depth requests.
>>
>> On the other hand, I don't see how a filesystem request is getting
>> REQ_FAILFAST ... unless there's a bio or readahead issue involved.
>> Anyway, could you try this patch:
>>
>> http://marc.info/?l=linux-scsi&m=119592627425498
>>
>> Which should fix the queue depth issue, and see if the errors go away?
>
> No, this one doesn't help...
still happens with 2.6.24-rc3-mm2...
--
laurent
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- 2.6.24-rc3-mm1
- Re: 2.6.24-rc3-mm1: I/O error, system hangs
- Re: 2.6.24-rc3-mm1: I/O error, system hangs
- Re: 2.6.24-rc3-mm1: I/O error, system hangs
- Re: 2.6.24-rc3-mm1: I/O error, system hangs
- Re: 2.6.24-rc3-mm1: I/O error, system hangs
- Re: 2.6.24-rc3-mm1: I/O error, system hangs
- Re: 2.6.24-rc3-mm1: I/O error, system hangs
- Re: 2.6.24-rc3-mm1: I/O error, system hangs
- Re: 2.6.24-rc3-mm1: I/O error, system hangs
- Re: 2.6.24-rc3-mm1: I/O error, system hangs
- Re: 2.6.24-rc3-mm1: I/O error, system hangs
- Re: 2.6.24-rc3-mm1: I/O error, system hangs
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
