ata1: port failed to respond

[Arjan Kon]

Binary package hint: linux-source-2.6.20

daily 20070415 doesn't boot. I get:

BusyBox etc.
etc.
(initramfs)

and after +-15 seconds this appear:

(initramfs)[92.774110] ata1: port failed to respond (30 secs, Status 0xd0)
[95.332400] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
[95.332450] ata2.00: (FMDMA stat 0x25)
[95.332497] ata2.00: cmd a0/01:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x12 d
ata 254 in
[97.826402] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
[97.826451] ata2.00: (FMDMA stat 0x25)
[97.826498] ata2.00: cmd a0/01:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x12 d
ata 254 in

p3 1ghz 815 or 815e chipset. Western Digital harddisk. (Compaq deskpro). Edgy and Dapper boots fine.

Compiled a kernel from kernel.org, kernel 2.6.20.7, this one works fine. I get /dev/hdaX with this one and not /dev/sdaX as Feisty should do.

[Arjan Kon (arj-nkon)]

Boot without quiet and splash boot options

[Arjan Kon (arj-nkon)]

Attachment above was part 2

[Ralph Janke (txwikinger)]

I get the same message during bootup of feisty. It then stops inside an initramfs shell. A simple exit allows then normal bootup, the system seems to work fine afterwoods.

[Ralph Janke (txwikinger)]

Looks to be a duplicate to https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/103608

[Arjan Kon (arj-nkon)]

Exit doesn't help, it gives a new Busybox/shell (including the error: /bin/sh: can't access tty; job control turned off)

[adam0509 (adam050986)]

same here in Xubuntu Feisty,

I use an old MITSUMI CR-4801TE drive.

Initialy, I use "irqpoll" option in 6.06 DAPPER DRAKE to avoid an error happening when mouting file system, but that error appears les less before the blue box shell/main install...

[adam0509 (adam050986)]

http://ubuntuforums.org/showthread.php?p=2517267

[adam0509 (adam050986)]

Duplicate bug :

https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/64587

https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/84603

[Abacus (ubuntu-the-abacus-group)]

Same loop here. Seemed to be caused by old Mitsumi CDROM drive. I used another old drive (Phillips CDRW) and it is installing as I am writing this.

[Arjan Kon (arj-nkon)]

I changed my 10 gb western digital hard disk for a 6 gb Maxtor, and it boots. I was able to install feisty on that disk.

I get some similar errors while booting, but not the port failed to respond error.

[Arjan Kon (arj-nkon)]

Ubuntu 7.10 20070606.1 has simular problems: no /dev/sdX.
But it boots, and so i have some info:

[Adam (adam.russell)]

Kubuntu Feisty Fawn
kernel 2.6.20-16-generic

I believe the problem is occuring with my SATA hard drive, which is a Samsung SP0812C. It stops responding quite often. It seems that most people that are having this problem are fixing it with 'piix', but I have a VIA chipset rather than an Intel one. I will attach some logs below. Relevant dmesg lines:

[ 2416.505383] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
[ 2416.505394] ata1.00: cmd c8/00:90:e6:54:5b/00:00:00:00:00/e2 tag 0 cdb 0x0 data 73728 in
[ 2416.505396] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 2416.505414] ata1: soft resetting port
[ 2416.671775] ATA: abnormal status 0x7F on port 0x0001e007
[ 2416.682280] ATA: abnormal status 0x7F on port 0x0001e007
[ 2416.693332] ata1.00: ata_hpa_resize 1: sectors = 156368016, hpa_sectors = 156368016
[ 2416.705299] ata1.00: ata_hpa_resize 1: sectors = 156368016, hpa_sectors = 156368016
[ 2416.705303] ata1.00: configured for UDMA/100
[ 2416.705314] ata1: EH complete
[ 2416.727567] SCSI device sda: 156368016 512-byte hdwr sectors (80060 MB)
[ 2416.727651] sda: Write Protect is off
[ 2416.727653] sda: Mode Sense: 00 3a 00 00
[ 2416.741889] SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2446.704938] ata1.00: limiting speed to UDMA/33:PIO4
[ 2446.704945] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
[ 2446.704953] ata1.00: cmd c8/00:88:e6:7d:5d/00:00:00:00:00/e1 tag 0 cdb 0x0 data 69632 in
[ 2446.704955] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 2453.697731] ata1: port is slow to respond, please be patient (Status 0xd0)
[ 2476.684824] ata1: port failed to respond (30 secs, Status 0xd0)
[ 2476.684831] ata1: soft resetting port
[ 2476.855210] ATA: abnormal status 0x7F on port 0x0001e007
[ 2476.865714] ATA: abnormal status 0x7F on port 0x0001e007
[ 2476.876786] ata1.00: ata_hpa_resize 1: sectors = 156368016, hpa_sectors = 156368016
[ 2476.888756] ata1.00: ata_hpa_resize 1: sectors = 156368016, hpa_sectors = 156368016
[ 2476.888760] ata1.00: configured for UDMA/33
[ 2476.888771] ata1: EH complete
[ 2476.909818] SCSI device sda: 156368016 512-byte hdwr sectors (80060 MB)
[ 2476.912474] sda: Write Protect is off
[ 2476.912478] sda: Mode Sense: 00 3a 00 00
[ 2476.916458] SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2507.060115] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
[ 2507.060126] ata1.00: cmd c8/00:20:b6:2d:04/00:00:00:00:00/e2 tag 0 cdb 0x0 data 16384 in
[ 2507.060128] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 2514.052911] ata1: port is slow to respond, please be patient (Status 0xd0)
[ 2537.032018] ata1: port failed to respond (30 secs, Status 0xd0)
[ 2537.032025] ata1: soft resetting port
[ 2537.198411] ATA: abnormal status 0x7F on port 0x0001e007
[ 2537.208918] ATA: abnormal status 0x7F on port 0x0001e007
[ 2537.215986] ata1.00: ata_hpa_resize 1: sectors = 156368016, hpa_sectors = 156368016
[ 2537.223961] ata1.00: ata_hpa_resize 1: sectors = 156368016, hpa_sectors = 156368016
[ 2537.223964] ata1.00: configured for U...

[EsbenMoseHansen (kde-mosehansen)]

I think the problem is with the ata_piix module. This page http://www.thinkwiki.org/wiki/Problems_with_SATA_and_Linux suggest several workarounds, none of which are possible from a boot line. The easiest one to do in practice seems to be to ensure that the ide_generic module is loaded before the ata_piix module. I tested that solution from the busybox line, and it seems to work.

But my real workaround would be to play games tonight, and tomorrow I'll get a SATA DVD drive. That hopefully fixes this for good, for me :)

[Brian Murray (brian-murray)]

I am assigning this bug to the 'ubuntu-kernel-team' per their bug policy. For future reference you can learn more about their bug policy at https://wiki.ubuntu.com/KernelTeamBugPolicies .

[Launchpad Janitor (janitor)]

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Arjan Kon (arj-nkon)]

I don't have the system anymore, so I cannot test :(

[Adam (adam.russell)]

I am unable to contribute any further to this bug, as I am no longer using the hardware in question. I will be unsubscribing.

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

[Sean Hunt (coppro)]

This happens to me on 2.6.27. Next time it freezes, I'll post my logs.

[Jim Lieb (lieb)]

This bug report is being closed because we received no response to the previous inquiry for information. Please reopen if this is still an issue in the current Ubuntu release, Jaunty Jackalope 9.04 - http://www.ubuntu.com/getubuntu/download. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.