Ubuntu
linux-source-2.6.20 package

IDE drive hangs boot for ~2 minutes after 2.6.20-13=>2.6.20-14

Bug #103780 reported by arashf
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: linux-source-2.6.20

After upgrading from 2.6.20-13 to 2.6.20-14, the kernel hangs for about 60 seconds at boot and I get the following error:

[ 44.795775] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
[ 44.795783] ata1.00: cmd a0/01:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x12 data 36 in
[ 44.795784] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 51.789679] ata1: port is slow to respond, please be patient (Status 0xd0)
[ 74.772597] ata1: port failed to respond (30 secs, Status 0xd0)
[ 74.772603] ata1: soft resetting port
[ 75.248208] ata1.00: configured for UDMA/33
[ 75.260073] ata1.01: configured for UDMA/33
[ 75.260085] ata1: EH complete
[ 80.752018] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
[ 80.752025] ata1.00: cmd a0/01:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x12 data 36 in
[ 80.752026] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 87.745969] ata1: port is slow to respond, please be patient (Status 0xd0)
[ 110.728881] ata1: port failed to respond (30 secs, Status 0xd0)
[ 110.728887] ata1: soft resetting port
[ 111.204498] ata1.00: configured for UDMA/33
[ 111.212367] ata1.01: configured for UDMA/33
[ 111.212379] ata1: EH complete
[ 116.704313] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
[ 116.704319] ata1.00: cmd a0/01:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x12 data 36 in
[ 116.704321] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 123.698262] ata1: port is slow to respond, please be patient (Status 0xd0)
[ 146.689169] ata1: port failed to respond (30 secs, Status 0xd0)
[ 146.689175] ata1: soft resetting port
[ 147.168773] ata1.00: configured for UDMA/33
[ 147.180638] ata1.01: configured for UDMA/33
[ 147.180651] ata1: EH complete
[ 152.672586] ata1.00: limiting speed to UDMA/25:PIO4
[ 152.672589] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
[ 152.672595] ata1.00: cmd a0/01:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x12 data 36 in
[ 152.672596] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 159.666533] ata1: port is slow to respond, please be patient (Status 0xd0)
[ 182.649448] ata1: port failed to respond (30 secs, Status 0xd0)
[ 182.649453] ata1: soft resetting port
[ 183.125061] ata1.00: configured for UDMA/25
[ 183.136934] ata1.01: configured for UDMA/33
[ 183.136952] ata1: EH complete

After these error, the boot process continues, and everything seems to work fine, except my drive names switch from the traditional /dev/hda1 and /dev/sda1... to /dev/sdf{1,3} and /dev/sde1.

Any ideas?

Revision history for this message
Pelle van der Scheer (pellesimon) wrote :

Got the exact same situation, .13 kernel works just fine ...

Changed in linux-source-2.6.20:
status: Unconfirmed → Confirmed
Revision history for this message
diegoe (diegoe-deactivatedaccount-deactivatedaccount) wrote :

I can confirm this. I have a SiS chipset. The old module was sis5513 (ok, maybe not exactly 13), after kernels starting using libata everything went bad, in all distributions with recent kernels my system takes ages to boot because of this.

Revision history for this message
Brian Murray (brian-murray) wrote :

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 .

Changed in linux-source-2.6.20:
assignee: nobody → ubuntu-kernel-team
Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

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!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

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.

Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

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.

Revision history for this message
Ike Panhc (ikepanhc) wrote :

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. If the issue remains in Jaunty, please test the latest upstream kernel build - https://wiki.ubuntu.com/KernelMainlineBuilds . To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

Changed in linux (Ubuntu):
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.