ata2 2.6.20-13-generic ata2: port is slow to respond

Thanks for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies . There is also a newer version of the kernel that came out today that you should try first. Thanks in advance!

Linux infecto-lapi 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux

here is my dmesg when uptaime is low, and can be found other informations, maybe kernel wersions mismatch but the error is and was the same for many kernels.

I have just upgraded from Edgy to Feisty on my laptops and workstation. The laptops seem to have gone fine, the workstation has not. When I try and boot with the 2.6.20-15 kernel, it hangs for a while and then drops out to Busybox with prompt (initramfs) and the message:

    ata2: port failed to respond

Clearly this is a blocker! I am not sure how to get dmesg type information since it won't actually boot so I don't get a record.

If I boot the old 2.6.17-11 kernel then everything works fine. The "uname -a" information is:

Linux balin 2.6.17-11-generic #2 SMP Tue Mar 13 23:32:38 UTC 2007 i686 GNU/Linux

I could attach the dmesg etc. record is that is helpful.

If I try the 2.6.20-15 recover boot then I see messages looking a little like the above which is why I have attached to this bug report rather than create a new one. If this was the wrong thing to do, I can always start a new entry.

I am at a total loss to know how to proceed on this one. 2.6.17-11 is fine 2.6.20-15 is totally broken on this one machine although fine on others :-(

Thanks.

I have this problem in fiesty too, Fresh clean install.

Adding the lspci -vvnn output from my machine running 2.6.17-11

Adding the dmesg output from the 2.6.17-11 boot as I can't actually boot 2.6.20.

The recent kernel upgrade, to 2.6.20-16 appears to have fixed the problem. I can boot this kernel and it appears to work well.

I have the same issue (lenovo thinkpad t43) and 2.6.20-16 does not fix it for me

# uname -a
Linux sterni 2.6.20-16-386 #2 Thu Jun 7 20:16:13 UTC 2007 i686 GNU/Linux

# hdparm -i /dev/sr0

/dev/sr0:

 Model=UJDA765 DVD/CDRW , FwRev=1.70 , SerialNo=
 Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic }
 RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
 BuffType=unknown, BuffSize=512kB, MaxMultSect=0
 (maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
 IORDY=yes, tPIO={min:180,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes: pio0 pio1 pio2 pio3 pio4
 DMA modes: sdma0 sdma1 sdma2 mdma0 mdma1 mdma2
 UDMA modes: udma0 *udma1 udma2
 AdvancedPM=no
 Drive conforms to: ATA/ATAPI-5 T13 1321D revision 3: ATA/ATAPI-1 ATA/ATAPI-2 ATA/ATAPI-3 ATA/ATAPI-4 ATA/ATAPI-5

 * signifies the current active mode

# hdparm /dev/sr0

/dev/sr0:
 IO_support = 0 (default 16-bit)
 readonly = 0 (off)
 readahead = 256 (on)
 HDIO_GETGEO failed: Inappropriate ioctl for device

I get this when putting a cd into the drive:
Jul 10 14:56:22 localhost kernel: [ 1376.764000] sr 1:0:0:0: SCSI error: return code = 0x08000002
Jul 10 14:56:22 localhost kernel: [ 1376.764000] sr0: Current: sense key: No Sense
Jul 10 14:56:22 localhost kernel: [ 1376.764000] <<vendor>> ASC=0xd0 ASCQ=0xffASC=0xd0 <<vendor>> ASCQ=0xff
Jul 10 14:56:22 localhost kernel: [ 1376.764000] FMK, EOM
Jul 10 14:56:22 localhost kernel: [ 1376.764000] end_request: I/O error, dev sr0, sector 2712
Jul 10 14:56:32 localhost kernel: [ 1386.764000] res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
Jul 10 14:56:39 localhost kernel: [ 1393.764000] ata2: port is slow to respond, please be patient (Status 0xd0)
Jul 10 14:57:02 localhost kernel: [ 1416.780000] ata2: soft resetting port
Jul 10 14:57:03 localhost kernel: [ 1417.264000] ata2.00: configured for UDMA/25
Jul 10 14:57:03 localhost kernel: [ 1417.264000] ata2: EH complete
Jul 10 14:57:33 localhost kernel: [ 1447.264000] ata2.00: qc timeout (cmd 0xa0)
Jul 10 14:57:33 localhost kernel: [ 1447.264000] res 51/51:03:00:00:00/00:00:00:00:00/a0 Emask 0x5 (timeout)
Jul 10 14:57:40 localhost kernel: [ 1454.264000] ata2: port is slow to respond, please be patient (Status 0xd0)
Jul 10 14:58:03 localhost kernel: [ 1477.280000] ata2: soft resetting port
Jul 10 14:58:03 localhost kernel: [ 1477.764000] ata2.00: configured for UDMA/25
Jul 10 14:58:03 localhost kernel: [ 1477.764000] ata2: EH complete

On Tuesday 10 of July 2007 14:04:58 Stefan Kost wrote:
> I have the same issue (lenovo thinkpad t43) and 2.6.20-16 does not fix
> it for me
>
> # uname -a
> Linux sterni 2.6.20-16-386 #2 Thu Jun 7 20:16:13 UTC 2007 i686 GNU/Linux
i`m better i have

Linux sraptok 2.6.22-7-generic #1 SMP Mon Jun 25 17:33:14 GMT 2007 i686
GNU/Linux

thats gutsy. and problem is too unresolverd.

MM

Feisty (all updates installed) gives me the same while massive disk io:

Jul 23 19:43:51 aga kernel: [ 9803.056906] res 40/00:00:cf:fa:c4/84:00:11:00:00/e
d Emask 0x4 (timeout)
Jul 23 19:43:58 aga kernel: [ 9810.049851] ata3: port is slow to respond, please be patien
t (Status 0xd0)
Jul 23 19:44:21 aga kernel: [ 9833.029527] ata3: soft resetting port
Jul 23 19:44:21 aga kernel: [ 9833.195458] ATA: abnormal status 0xD0 on port 0x0001bc07
Jul 23 19:44:21 aga kernel: [ 9833.205603] ATA: abnormal status 0xD0 on port 0x0001bc07
Jul 23 19:44:21 aga kernel: [ 9833.215744] ATA: abnormal status 0xD0 on port 0x0001bc07
Jul 23 19:44:21 aga kernel: [ 9833.233553] ata3.00: ata_hpa_resize 1: sectors = 312581808,
 hpa_sectors = 312581808
Jul 23 19:44:21 aga kernel: [ 9833.241507] ata3.00: ata_hpa_resize 1: sectors = 312581808,
 hpa_sectors = 312581808
Jul 23 19:44:21 aga kernel: [ 9833.241515] ata3.00: configured for UDMA/133
Jul 23 19:44:21 aga kernel: [ 9833.241531] ata3: EH complete
Jul 23 19:44:21 aga kernel: [ 9833.257419] SCSI device sda: 312581808 512-byte hdwr sector
s (160042 MB)
Jul 23 19:44:21 aga kernel: [ 9833.257577] sda: Write Protect is off
Jul 23 19:44:21 aga kernel: [ 9833.276013] SCSI device sda: write cache: enabled, read cac
he: enabled, doesn't support DPO or FUA

More details - it happens with both kernels:
Linux xxx 2.6.20-16-generic
Linux xxx 2.6.20-16-i386

Could someone please fix this? Or raise priority. Its quite annoying to not be able to use the cd-rom.

I have that trouble to. Here is all of attachments:

Please check SATA port or replace cable.
I've took other cable and plug it to other SATA port.
No errors since... about a week

Linux petrata 2.6.20-16-generic #2 SMP Fri Aug 31 00:55:27 UTC 2007 i686 GNU/Linux

This is happening to me when I run k3b:
Sep 14 21:17:00 petrata kernel: [ 233.472645] res 40/00:03:00:00:20/00:00:00:00:00/b0 Emask 0x4 (timeout)
Sep 14 21:17:07 petrata kernel: [ 240.472535] ata2: port is slow to respond, please be patient (Status 0xd0)
Sep 14 21:17:30 petrata kernel: [ 263.475021] ata2: soft resetting port
Sep 14 21:17:32 petrata kernel: [ 264.670780] ata2.00: configured for UDMA/33
Sep 14 21:17:32 petrata kernel: [ 264.834448] ata2.01: configured for UDMA/66
Sep 14 21:17:32 petrata kernel: [ 264.834488] ata2: EH complete

I have a LITE-ON DVDRW SOHW-1673S. with firmware JS05. I have updated it to JS0D.
Before the update, the above would take about 5 minutes, and k3b would not find the burner. If I closed k3b and ran it again, the hard disk light would stay lit and it would never get started. The drive is locked.
After the update, k3b takes about 10-20 seconds to get going and otherwise works fine (just testing now with a CDRW).

Attached is the start of the k3b run.
It hangs at this point:
(K3bDevice::Device) /dev/scd1: checking for RAW_R96R
(K3bDevice::ScsiCommand) failed:
                           command: GET PERFORMANCE (ac)
                           errorcode: 72
                           sense key: NO SENSE (2)
                           asc: 0
                           ascq: 3

I get the same error in 2.6.24 (hardy haron) and fresh compiled 2.6.25.4. Unfortunately I can't replace the cable, because I'm working on a laptop.

Michiel, did you ever get this resolved. I've got a Toshiba A10 that's having the same problem; also running hardy haron. I don't think I was getting these errors initially so I'm not sure what's happened. I can use the DVD-rom for other things and I've used it for burning ISO's recently but... when I try to watch a dvd I get these errors in the messages log.

end_request: I/O error, dev sr0

uname -a:
Linux slc34128843ulx 2.6.24-19-generic #1 SMP Wed Jun 18 14:43:41 UTC 2008 i686 GNU/Linux

I've attached the two log's that Brian requested up front.

No it hasn't been resolved. It isn't as bad as before. It happens every ~30-60 seconds instead of every 3 seconds

uname -a:
Linux mercurius 2.6.24-19-generic #1 SMP Wed Jun 18 14:15:37 UTC 2008 x86_64 GNU/Linux

I think I have found the solution (read it somewhere but forgot where). My laptop seems to have a Hitachi and it doesn't do complete NCQ. Some of their drives seem to be blacklisted, but I guess mine isn't (HTS541010G9AT00).

To solve the problem add this line to your /etc/rc.local
sh -c "echo 1 > /sys/block/sda/device/queue_depth"
This will disable NCQ.

Please correct me if I'm wrong.

I reinstalled the gstreamer stuff and mplayer and I've stopped seeing the messages. I'm not sure how at this point but I'm not complaining.

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!

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.

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.

Unfortunately it seems this bug is still an issue. Can you confirm this issue exists with the most recent Jaunty Jackalope 9.04 release - http://www.ubuntu.com/news/ubuntu-9.04-desktop . Please let us know your results. Thanks.

Hi, I have been running Hardy for quite some time. I upgraded to Intrepid and experienced this problem so reverted back to Hardy with no problems.

I have recently upgraded to Jaunty vi Intrepid and the problem as returned.

I have attached the information requested.
Uname = 2.6.28-3-rt #12-Ubuntu SMP PREEMPT RT Fri Apr 17 10:09:11 UTC 2009 i686 GNU/Linux

HI, since my last post I have removed the CD (slave) reader from my system and left the DVD r/w (master) alone.
The problem has gone.

The startup time is now much shorter than it was under Hardy. I wonder if the problem existed under Hardy but no error messages were displayed?

Regards

This might be right, you should have checked the log file, or what you
can do now is download Splunk it can index all the logs and your problem
becomes a lot easier as it tells you when something happened and what
was it...

On Thu, 2009-07-23 at 16:13 +0000, Adrian Pollard wrote:
> HI, since my last post I have removed the CD (slave) reader from my system and left the DVD r/w (master) alone.
> The problem has gone.
>
> The startup time is now much shorter than it was under Hardy. I
> wonder if the problem existed under Hardy but no error messages were
> displayed?
>
> Regards
>
--
Thanks,
Vikram

No response since last query for updated information.