Hang during boot: intrepid 2.6.27-3 hp pavilion

Bug #273318 reported by gpk
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: linux-image

On a dual-core AMD laptop (an HP Pavilion G6062EA), Intrepid hangs during boot. Not quite completely, though. You can hit <enter> or <esc> and it staggers on for a while. After about 13 keypresses, it does eventually finish booting. It then runs nicely (except that X is messed up...).

The behaviour is the same with "noapic" and/or "noapictimer" . This is a regression relative to 8.04, as it booted very nicely then. Both now and then, you need "noapic" to get the USB to work. (That's another bug, but a pretty standard one, these days.)

I attach /var/log/syslog . You can see where I hit <enter> by the several-second jumps in the time.

I attach /var/log/syslog from a boot with default parameters (e,g. "ro").

Revision history for this message
gpk (gpk-kochanski) wrote :
Revision history for this message
gpk (gpk-kochanski) wrote :

...actually with "noapic" and "noapictimer", it does boot. It gets up to the point of
"configuring network interfaces" and then hangs there, but eventually (after about 1 minute)
something times out and the boot proceeds. Again, neither of these arguments was needed
for 8.041 .

I attach that /var/log/syslog here

By the way, this is an entirely current version of intrepid, installed from alpha-5 and
updated/upgraded this evening.

Incidentally, it hangs on shutdown. Some mixture of <enter> <esc> and waiting seems to be necessary.
It takes at least a minute or two to turn off.

Revision history for this message
gpk (gpk-kochanski) wrote :

Here's the /var/log/syslog for a boot with "noapic" . Again, we get lots of hangs, and if you pound the keyboard enough, it eventually boots.

Revision history for this message
gpk (gpk-kochanski) wrote :

Incidentally, sometimes you needed to hit <esc>. <enter> was not always enough to shake it loose. Perhaps that's a clue.

---------------

Here's the /var/log/syslog from a boot with "noapictimer" . It does boot, but there is a long hang at "configuring network interfaces". Didn't need this flag before with 8.041.

Revision history for this message
gpk (gpk-kochanski) wrote :

Here's the result of lspci -vv

The system is intrepid, updated to a couple of hours ago. It was installed from an intrepid alpha-5 CD, then upgraded via aptitude.

Revision history for this message
Leandro Pereira de Lima e Silva (leandro-limaesilva) wrote :

Isn't it the same bug as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/263782 ?

gpk, make a test with Stefan's kernel...

Revision history for this message
gpk (gpk-kochanski) wrote :

It's probably not the same bug. I get no screen corruption, and unlike 263782,
booting with noapictimer almost solves the problem. Also, I see no intermittency:
the boot process is exactly the same every time. (I've done at least a dozen
boots with "noapic" and at least 6 or 7 with "noapictimer".

I'll test with stefan's kernel ASAP, though.

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

Hi gpk,

This actually sounds more like bug 254668. Please take a look let us know. Stefan is also working with the bug reporters there. Thanks.

Changed in linux-meta:
status: New → Incomplete
Revision history for this message
gpk (gpk-kochanski) wrote :

Problem still exists in Beta version with 2.6.27-7 kernel.

Actually, it does not seem to be 254688. (Or, so Stefan Bader concluded.)
The problem there doesn't respond to noapictimer, while my problem does.
See this:

vnieto wrote on 2008-09-10: (permalink)
> Also I put on this boot line on grub menu.lst:
> "kernel /boot/vmlinuz-2.6.27-2-generic root=UUID=88917a1d-a2f6-4e3f-8742-d770e2b58ce4 ro splash locale=es_ES > noapictimer"
> and work fine, I don't see any bad thing.
> ...
> I use amd64 x2 and 2.6.27-2-generic
Stefan Bader wrote on 2008-09-10: (permalink)
>
>@vnieto,
>
> noapictimer prevents the kernel from using the local apic timer. However this option is only used for 64bit kernels and > only takes effect with multiple CPU (cores). So it is not a solution for the 32bit kernel also handled here.
>
> You can try the smb5 test kernel from http://people.ubuntu.com/~smb/bug254668/ which should allow you to boot
> without the noapictimer option.

Revision history for this message
gpk (gpk-kochanski) wrote :

> You can try the smb5 test kernel from http://people.ubuntu.com/~smb/bug254668/ which should allow you to boot
> without the noapictimer option.

No luck. I download it, then
sudo dpkg -i linux-image-2.6.27-3-generic_2.6.27-3.3smb5_amd64.deb
then boot with the 2.6.27-3 kernel found in grub's menu, and I still need to keep
hitting keys.

gpk (gpk-kochanski)
Changed in linux-meta:
status: Incomplete → New
Revision history for this message
Leandro Pereira de Lima e Silva (leandro-limaesilva) wrote :

Same problem here, 2.6.27-7 still has it in release candidate.

Changed in linux-meta:
status: New → Confirmed
Revision history for this message
urielshaolin (uriel-shaolin) wrote :

mismo problema!

same problem! mexican user with a hp pavilion dv6951la notebook!
ubuntu 8.10 64 bits

Revision history for this message
Sheldon (leewsb) wrote :

I have the same problem. I have a dv9618ca (dv9500) and I have exactly the same problem. However, I found that if you boot with pci=noacpi it boots and works fine.

Revision history for this message
Jhosman Lizarazo (jhosman) wrote :
Brad Figg (brad-figg)
affects: linux-meta (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.