[lkml]   [2007]   [Oct]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [bug] ata subsystem related crash with latest -git
Ingo Molnar wrote:
> * Jens Axboe <> wrote:
>> --- a/drivers/scsi/scsi_lib.c
>> +++ b/drivers/scsi/scsi_lib.c
>> @@ -39,7 +39,7 @@
>> * (unless chaining is used). Should ideally fit inside a single page, to
>> * avoid a higher order allocation.
>> */
>> -#define SCSI_MAX_SG_SEGMENTS 128
>> +#define SCSI_MAX_SG_SEGMENTS 129
> this one finally made the trick and it's booting fine now, without any
> crashes!

Alas, this didn't help me here. I did manage to capture the error
messages this time, and in the two machines I'm actively testing on,
sata_mv is the driver that's dying in both cases. Machine A
additionally has sata_nv, which is working. Machine B additionally has
ata_piix, which is working. So in both cases, its sata_mv that is
throwing SError complaints:

> ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x400000 action 0x6 frozen
> ata7.00: edma_err 0x04000080, EDMA self-disable
> ata7: SError: { Handshk }
> ata7.00: cmd ca/00:08:c7:40:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data 4096 out
> res 50/00:00:ce:40:00/00:00:00:00:00/e0 Emask 0x100 (unknown error)
> ata7.00: status: { DRDY }
> ata7: hard resetting link
> ata7: SATA link up 1.5 Gbps (SStatus 113 SControl 300)

Still digging... this behavior showed up after libata changes went in,


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2007-10-18 10:27    [W:0.156 / U:2.264 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site