[Gutsy]Boot up delays and errors on laptop nx6310

Bug #163675 reported by Michał Sędkowski
10
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned
linux-source-2.6.22 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: linux-image-2.6.22-14-generic

Randomly I get such an error message on boot up:
[ 10.604000] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
[ 10.604000] ata1.00: cmd a0/01:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x12 data 96 in
[ 10.604000] res 40/00:02:00:24:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
[ 10.604000] ata1: soft resetting port
[ 11.096000] ata1.00: configured for MWDMA2
[ 11.096000] ata1: EH complete
[ 16.596000] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
[ 16.596000] ata1.00: cmd a0/01:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x12 data 96 in
[ 16.596000] res 40/00:02:00:24:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
[ 16.596000] ata1: soft resetting port
[ 17.088000] ata1.00: configured for MWDMA2
[ 17.088000] ata1: EH complete
[ 22.588000] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
[ 22.588000] ata1.00: cmd a0/01:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x12 data 96 in
[ 22.588000] res 40/00:02:00:24:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
[ 22.588000] ata1: soft resetting port
[ 23.084000] ata1.00: configured for MWDMA2
[ 23.084000] ata1: EH complete
[ 28.584000] ata1.00: limiting speed to MWDMA1:PIO4
[ 28.584000] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
[ 28.584000] ata1.00: cmd a0/01:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x12 data 96 in
[ 28.584000] res 40/00:02:00:24:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
[ 28.584000] ata1: soft resetting port
[ 29.076000] ata1.00: configured for MWDMA1
[ 29.076000] ata1: EH complete
[ 29.076000] scsi scan: 96 byte inquiry failed. Consider BLIST_INQUIRY_36 for this device
[ 29.076000] scsi 0:0:0:0: CD-ROM MATSHITA DVD-RAM UJ-840S 1.11 PQ: 0 ANSI: 5

It also shows up on each wake up from suspend to disk [before loading the system image] and on first "normal" boot up after suspend to disk. When I restart the computer again, everything is fine, and no error is shown. The problem however appears randomly, even if I didn't use hibernation.
Apart from a considerable boot up delay [as show above the error appears four times and before each there is a
5 second delay] the computer starts and works normally.

Tags: cft-2.6.27
Revision history for this message
Michał Sędkowski (sedmich) wrote :

Forgot to mention I use the latest bios F.0D and up-to-date Gutsy with 2.6.22-14-generic kernel.

Revision history for this message
Michał Sędkowski (sedmich) wrote :
Revision history for this message
Michał Sędkowski (sedmich) wrote :
description: updated
Revision history for this message
Anita (a-lewis) wrote :

I confirm. System freezes for maybe 30 seconds here. syslog:

Dec 15 15:27:31 hopalong kernel: [ 4950.512000] ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
Dec 15 15:27:31 hopalong kernel: [ 4950.512000] ata1.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x25 data 8 in
Dec 15 15:27:31 hopalong kernel: [ 4950.512000] res 40/00:03:00:00:00/00:00:00:00:00/b0 Emask 0x4 (timeout)
Dec 15 15:27:42 hopalong kernel: [ 4955.564000] ata1: port is slow to respond, please be patient (Status 0xd0)
Dec 15 15:27:42 hopalong kernel: [ 4960.560000] ata1: device not ready (errno=-16), forcing hardreset
Dec 15 15:27:42 hopalong kernel: [ 4960.560000] ata1: soft resetting port
Dec 15 15:27:42 hopalong kernel: [ 4960.920000] ata1.00: configured for UDMA/100
Dec 15 15:27:42 hopalong kernel: [ 4961.108000] ata1.01: configured for UDMA/25
Dec 15 15:27:42 hopalong kernel: [ 4961.108000] ata1: EH complete
Dec 15 15:27:42 hopalong kernel: [ 4961.124000] sd 0:0:0:0: [sda] 117210240 512-byte hardware sectors (60012 MB)
Dec 15 15:27:42 hopalong kernel: [ 4961.140000] sd 0:0:0:0: [sda] Write Protect is off
Dec 15 15:27:42 hopalong kernel: [ 4961.140000] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Dec 15 15:27:42 hopalong kernel: [ 4961.164000] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Dec 15 15:27:42 hopalong kernel: [ 4961.196000] sd 0:0:0:0: [sda] 117210240 512-byte hardware sectors (60012 MB)
Dec 15 15:27:42 hopalong kernel: [ 4961.212000] sd 0:0:0:0: [sda] Write Protect is off
Dec 15 15:27:42 hopalong kernel: [ 4961.212000] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Dec 15 15:27:42 hopalong kernel: [ 4961.244000] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Revision history for this message
Laszlo Kupcsik (koopac) wrote :

One more confirm. I dont attach any logs, exactly the same what was shown before. HP Compaq nc6320

Revision history for this message
Thomas Aaron (tom-system76) wrote :

Anita's problem has been fixed by following the insructions here:
https://bugs.launchpad.net/system76/+bug/117441

It was caused by an incompatibility between the Ubuntu and the firmware in her CD drive.
At System 76, we ran into this a while back.

Revision history for this message
Laszlo Kupcsik (koopac) wrote :

Hi Thomas! I don't know, perhaps the bugs are related, but it seems to me, that I don't have the problems the two people mentioned above (no serious boot up delay, no CD-DVD problems). I noticed the log message when I played around with suspend. After resume, everything seemed to be fine until I started some stuff on my external USB drive. That's when my system became unresponsive. I had to shut it down. Then I looked around in the log files, and found this before the freeze. I thought, it might have caused it. Now I searched some older logs (well before even thinking about suspend), and found that one can come by this message pretty frequently, no idea what triggers it though...

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

The Hardy Heron Alpha series was recently released. Alpha2 and subsequent releases contain an updated version of the kernel. You can download and try the new Hardy Heron Alpha release from http://cdimage.ubuntu.com/releases/hardy/ . Please note that Alpha3 will be released within the next day or two so you may want to wait. You should be able to then test the new kernel via the LiveCD. Also note that from the LiveCD you can only test Suspend, not Hibernate. If you can, please verify if this bug still exists or not and report back your results. General information regarding the release can also be found here: http://www.ubuntu.com/testing/ .

Changed in linux:
status: New → Incomplete
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

I've opened a new task against the actively developed kernel and am closing the task against linux-source-2.6.22. Thanks!

Changed in linux-source-2.6.22:
status: New → Won't Fix
Revision history for this message
Connor Imes (ckimes) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

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
Connor Imes (ckimes) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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