ACPI Exception causes slow boot

Bug #215179 reported by DanielRoesler
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned
Nominated for Hardy by DanielRoesler

Bug Description

I am trying Hardy Heron 8.04 beta, on my Sager NP6260 laptop. Every time I boot, the process hangs on an ACPI Exception for around 43 seconds (I timed it). The whole rest of the boot takes around 57 seconds, so this is huge chunk of time.

Specifically:
[ 19.170638] ACPI Exception (processor_core-0816): AE_NOT_FOUND, Processor Device is not present [20070126]

I have not experience this time delay on Gutsy or Feisty. I'm not sure if the error occurred on previous installations, but if it did, it didn't cause such a long a delay.

I have attached my dmesg and bootchart. The bootchart doesn't appear to show any delay. Does it not start until after this bug occurs?

Revision history for this message
DanielRoesler (diafygi) wrote :
Revision history for this message
DanielRoesler (diafygi) wrote :
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information.

Please include the information as separate attachments:
 * Output of uname -a
    * uname -a > uname.txt
 * Output of sudo lspci -vvnn
    * sudo lspci -vvnn > lspci.txt
 * Output of sudo dmidecode
    * sudo dmidecode > dmidecode.txt
 * Try to suspend/hibernate and then restart the system and attach /var/log/kern.log.0
 * Tarball of /proc/acpi directory. You can't just tar all files because their content sometimes changes etc.
    * cp -r /proc/acpi /tmp
    * tar -cvjf ~/acpi.tar.bz /tmp/acpi
    * attach acpi.tar.bz from your home directory

Changed in linux-meta:
status: New → Incomplete
Revision history for this message
DanielRoesler (diafygi) wrote :
Revision history for this message
DanielRoesler (diafygi) wrote :
Revision history for this message
DanielRoesler (diafygi) wrote :
Revision history for this message
DanielRoesler (diafygi) wrote :
Revision history for this message
DanielRoesler (diafygi) wrote :
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

This is indeed a bit confusing, because your bootchart doesn't suggest any delay. From looking at the timestamps in your log, I think that the ACPI Exception message might be a red herring. Did you have to boot in recovery mode to see this message? If not, is your usplash working at all, and could you try recovery mode to see if you get a similar delay?

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
DanielRoesler (diafygi) wrote :

Okay, I installed Intrepid Ibex Alpha 5 and the bug appears to go away. There is no longer a delay when booting. Thanks a bunch!

Changed in linux:
status: Incomplete → Fix Released
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.