Boot time is over 3 minutes with new motherboard

[Thomas Novin]

After buying a new motherboard my boot time is over three minutes and the DVD player doesn't work at all.

May 12 21:19:53 thnov-desktop kernel: [ 37.815688] ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
May 12 21:19:53 thnov-desktop kernel: [ 37.815755] ata1.01: cmd a0/01:00:00:60:00/00:00:00:00:00/b0 tag 0 dma 96 in
May 12 21:19:53 thnov-desktop kernel: [ 37.815757] cdb 12 00 00 00 60 00 00 00 00 00 00 00 00 00 00 00
May 12 21:19:53 thnov-desktop kernel: [ 37.815759] res 40/00:02:00:24:00/00:00:00:00:00/b0 Emask 0x4 (timeout)
May 12 21:19:53 thnov-desktop kernel: [ 37.815931] ata1.01: status: { DRDY }
May 12 21:19:53 thnov-desktop kernel: [ 37.815998] ata1: soft resetting link
May 12 21:19:53 thnov-desktop kernel: [ 38.323733] ata1.01: configured for UDMA/33
May 12 21:19:53 thnov-desktop kernel: [ 38.323794] ata1: EH complete
May 12 21:19:53 thnov-desktop kernel: [ 43.817729] ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
May 12 21:19:53 thnov-desktop kernel: [ 43.817796] ata1.01: cmd a0/01:00:00:60:00/00:00:00:00:00/b0 tag 0 dma 96 in
May 12 21:19:53 thnov-desktop kernel: [ 43.817798] cdb 12 00 00 00 60 00 00 00 00 00 00 00 00 00 00 00
May 12 21:19:53 thnov-desktop kernel: [ 43.817799] res 40/00:02:00:24:00/00:00:00:00:00/b0 Emask 0x4 (timeout)
May 12 21:19:53 thnov-desktop kernel: [ 43.817971] ata1.01: status: { DRDY }
May 12 21:19:53 thnov-desktop kernel: [ 43.818038] ata1: soft resetting link
May 12 21:19:53 thnov-desktop kernel: [ 44.329793] ata1.01: configured for UDMA/33
May 12 21:19:53 thnov-desktop kernel: [ 44.329855] ata1: EH complete
May 12 21:19:53 thnov-desktop kernel: [ 49.823790] ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
May 12 21:19:53 thnov-desktop kernel: [ 49.823857] ata1.01: cmd a0/01:00:00:60:00/00:00:00:00:00/b0 tag 0 dma 96 in
May 12 21:19:53 thnov-desktop kernel: [ 49.823859] cdb 12 00 00 00 60 00 00 00 00 00 00 00 00 00 00 00
May 12 21:19:53 thnov-desktop kernel: [ 49.823861] res 40/00:02:00:24:00/00:00:00:00:00/b0 Emask 0x4 (timeout)
May 12 21:19:53 thnov-desktop kernel: [ 49.824032] ata1.01: status: { DRDY }
May 12 21:19:53 thnov-desktop kernel: [ 49.824099] ata1: soft resetting link
May 12 21:19:53 thnov-desktop kernel: [ 50.335829] ata1.01: configured for UDMA/33
May 12 21:19:53 thnov-desktop kernel: [ 50.335891] ata1: EH complete
May 12 21:19:53 thnov-desktop kernel: [ 55.829833] ata1.01: limiting speed to UDMA/25:PIO4
May 12 21:19:53 thnov-desktop kernel: [ 55.829891] ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
May 12 21:19:53 thnov-desktop kernel: [ 55.829958] ata1.01: cmd a0/01:00:00:60:00/00:00:00:00:00/b0 tag 0 dma 96 in
May 12 21:19:53 thnov-desktop kernel: [ 55.829960] cdb 12 00 00 00 60 00 00 00 00 00 00 00 00 00 00 00
May 12 21:19:53 thnov-desktop kernel: [ 55.829962] res 40/00:02:00:24:00/00:00:00:00:00/b0 Emask 0x4 (timeout)
May 12 21:19:53 thnov-desktop kernel: [ 55.830126] ata1.01: status: { DRDY }
May 12 21:19:53 thnov-desktop kernel: [ 55.830193] ata1: soft resetting link
May 12 21:19:53 thnov-desktop kernel: [ 56.341875] ata1.01: configured for UDMA/25
May 12 21:19:53 thnov-desktop kernel: [ 56.341947] ata1: EH complete

Found a couple of other bugs with similar issues but they seem to have problems with freezes, not long boot times or unavailable DVD-players.

$ lsb_release -rd
Description: Ubuntu 8.04
Release: 8.04

$ uname -r
2.6.24-16-generic

----
Found in dmesg:
[ 49.964577] scsi scan: 96 byte inquiry failed. Consider BLIST_INQUIRY_36 for this device

[Thomas Novin (thomasn80)]

Oh, btw, the motherboard is a Gigabyte GA-EP35-DS3.

http://www.gigabyte.com.tw/Products/Motherboard/Products_Overview.aspx?ClassValue=Motherboard&ProductID=2741&ProductName=GA-EP35-DS3

South Bridge Intel® ICH9:

   1. 4 x SATA 3Gb/s connectors (SATAII0, SATAII1, SATAII4, SATAII5) supporting up to 4 SATA 3Gb/s devices

GIGABYTE SATA2 chip:

   1. 1 x IDE connector supporting ATA-133/100/66/33 and up to 2 IDE devices
   2. 2 x SATA 3Gb/s connectors (GSATAII0, GSATAII1) supporting up to 2 SATA 3Gb/s devices
   3. Support for SATA RAID 0, RAID 1, and JBOD

[Patrick Kilgore (patrick-kilgore)]

Thanks for your bug report and for your contribution to ubuntu. In order to determine if this issue is usplash related, would you boot your computer with usplash disabled and then shutdown to see if you can reproduce the issue? To disable usplash for one boot time, you can follow these steps :

1.Press Esc during Grub boot delay to access the boot menu.
2.Select your actual Ubuntu boot line and press "e" to edit it.
3.Select the "kernel" line and press "e" to edit it.
4.At the end of the line, remove "splash" and "quiet" and press "enter".
5.Type "b" to boot the custom boot line.

[Thomas Novin (thomasn80)]

Hello

This did not have any effect.

[Patrick Kilgore (patrick-kilgore)]

Thanks, can you include the following information? Please post everything except uname -a as seperate attachments, as pasting them into the comments breaks formatting and causes significant difficulty in debugging.

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" after a fresh boot 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 [WWW] https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance!

[Thomas Novin (thomasn80)]

$ uname -a
Linux thnov-desktop 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008 i686 GNU/Linux

[Patrick Kilgore (patrick-kilgore)]

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

[kiev1 (sys-sys-admin)]

I have the same problem
dublicate -> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/217920

[Thomas Novin (thomasn80)]

What does that suggestion mean? "Consider BLIST_INQUIRY_36 for this device"?

[Thomas Novin (thomasn80)]

My problem is solved. A number of things has changed since my original report so I don't know what did it.

- BIOS changes
- Kernel upgrade
- Re-attachment of the device + cabling

$ apt-cache policy linux-image-generic
linux-image-generic:
  Installed: 2.6.24.19.21
  Candidate: 2.6.24.19.21
  Version table:
 *** 2.6.24.19.21 0
        500 http://se.archive.ubuntu.com hardy-updates/main Packages
        100 /var/lib/dpkg/status
     2.6.24.18.20 0
        500 http://se.archive.ubuntu.com hardy-security/main Packages
     2.6.24.16.18 0
        500 http://se.archive.ubuntu.com hardy/main Packages

[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.

[Thomas Novin (thomasn80)]

Moving to Invalid since the problem is gone..?

[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.

[driventokill (melancholy-knight)]

I have the same problem.It has lasted for about 1 year.I wait for every new released linux condition,but I got disappointed every time.who can give some useful suggests to fix it..

[Thomas Novin (thomasn80)]

I got the problem back again after needing to reset my BIOS. Obviously it was some setting in the BIOS that I had changed from the default value that solved this problem for me. Now I only need to find out which value that was... :)

[Thomas Novin (thomasn80)]

I never found the BIOS settings again but now after upgrade to Lucid the problem is fixed!