FS#5456 - kernel 2.6.18-4 ata2 errors on Dell OptiPlex GX280

Attached to Project: Arch Linux
Opened by Samuel Winchenbach (swinchen) - Wednesday, 27 September 2006, 17:17 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture not specified
Severity High
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

After upgrading to kernel 2.6.18-4 (from the 2.6.17-x series) the following shows up during boot:

<... snip ...>
ICH6: IDE controller at PCI slot 0000:00:1f.1
ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 16 (level, low) -> IRQ 16
ICH6: chipset revision 3
ICH6: not 100% native mode: will probe irqs later
ICH6: neither IDE port enabled (BIOS)
libata version 2.00 loaded.
ata_piix 0000:00:1f.2: version 2.00
ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
ACPI: PCI Interrupt 0000:00:1f.2[C] -> GSI 20 (level, low) -> IRQ 18
PCI: Setting latency timer of device 0000:00:1f.2 to 64
ata1: SATA max UDMA/133 cmd 0xFE00 ctl 0xFE12 bmdma 0xFEA0 irq 18
ata2: SATA max UDMA/133 cmd 0xFE20 ctl 0xFE32 bmdma 0xFEA8 irq 18
scsi0 : ata_piix
ata1.00: ATA-7, max UDMA/133, 312581808 sectors: LBA48
ata1.00: ata1: dev 0 multi count 8
ata1.00: configured for UDMA/133
scsi1 : ata_piix
ata2: port is slow to respond, please be patient
ata2: port failed to respond (30 secs)
ata2: SRST failed (status 0xFF)
ata2: SRST failed (err_mask=0x100)
ata2: softreset failed, retrying in 5 secs
ata2: SRST failed (status 0xFF)
ata2: SRST failed (err_mask=0x100)
ata2: softreset failed, retrying in 5 secs
ata2: SRST failed (status 0xFF)
ata2: SRST failed (err_mask=0x100)
ata2: reset failed, giving up
Vendor: ATA Model: WDC WD1600JS-00M Rev: 02.0
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
sda: sda1 sda2 sda3
sd 0:0:0:0: Attached scsi disk sda
<... End Snip ...>

The system is unmodified, using only stock hardware. Marked as high, not critical because the system still seems to boot and function properly.

Ask if more information is needed.
This task depends upon

Closed by  Roman Kyrylych (Romashka)
Wednesday, 07 February 2007, 16:34 GMT
Reason for closing:  Fixed
Comment by Tobias Powalowski (tpowa) - Thursday, 28 September 2006, 06:08 GMT
ata_probe_timeout is a module parameter you can use to lower the timeout time,
add this to modprobe.conf
option libata ata_probe_timeout=<seconds>
and try to add /etc/modprobe.conf to initcpio image
FILES="/etc/modprobe.conf"
perhaps it helps
Comment by Samuel Winchenbach (swinchen) - Thursday, 28 September 2006, 13:23 GMT
Did as described (except option should be options and I replaced <seconds> with 5) ran "sudo mkinitcpio -g kernel26.img" then "sudo cp kernel26.img /boot" and restarted. Did not make any difference.
Comment by Joshua (twiistedkaos) - Monday, 16 October 2006, 23:16 GMT
I followed the exact instructions, still get the error
Comment by Tobias Powalowski (tpowa) - Sunday, 05 November 2006, 07:32 GMT
still valid in new 18.2 kernel?
Comment by Samuel Winchenbach (swinchen) - Monday, 06 November 2006, 14:38 GMT
Yes, the bug is still there. :(
Comment by Tobias Powalowski (tpowa) - Saturday, 02 December 2006, 15:47 GMT
you could try .19 kernel but be aware that for ata_piix you need to change to sdx name scheme and hdx is no more
Comment by Samuel Winchenbach (swinchen) - Monday, 04 December 2006, 14:47 GMT
Yes, it is still there. Although it is now ata4 not ata2.
Comment by Tobias Powalowski (tpowa) - Tuesday, 06 February 2007, 13:46 GMT
status on kernel 2.6.20 from testing?
Comment by Samuel Winchenbach (swinchen) - Tuesday, 06 February 2007, 14:03 GMT
Hmmm, I don't see 2.6.20 in testing. Perhaps it hasn't hit the FTP yet. I will let you know as soon as I get it.
Comment by Samuel Winchenbach (swinchen) - Wednesday, 07 February 2007, 13:15 GMT
2.6.20 took care of the problem. It also took care of a very similar problem I was having on my home computer. I guess this one can be to bed. Thanks :)

Loading...