HP-2140 won't boot with dual-core enabled

Bug #376728 reported by Jeremy Nickurak
This bug report is a duplicate of:  Bug #359441: acpi won't work on HP 2140 Mini Note. Edit Remove
64
This bug affects 6 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: linux-image-2.6.28-12-generic

When dual-core support is enabled in the netbook's BIOS, an HP-2140 fails to boot. (When the machine boots Windows with dual-core support enabled, hyperthreading is available to present 2 CPUs)

There's many lines of kernel output. I can't grab the first ones (they scroll off the screen), but the ones on the screen (excluding the hex codes except for the last couple) are:

clockevents_program_event+0x9a/0x150
tick_dev_program_event+0x33/0xc0
tick_program_event+0x2b/0x40
hrtimer_reprogram+0x95/0xe0
enqueue_hrtimer+75/0xf0
hrtimer_start_range_ns+0xe9/0x1e0
getnstimeofday+0x53/0x110
lapic_next_event+0x13/0x20
getnstimeofday+0x53/0x110
do_page_fault+0x0/0x790
error_code+0x72/0x80
ktime_get+0x19/0x40
generic_smp_call_function_single_interrupt+0x34/0xb0
smp_call_function_single_interrupt+0x1e/0x40
call_function_single_interrupt+0x28/0x30
acpi_idle_enter_simple+0x153/0x18e
cpuidel_idle_call+0x6f/0xd0
rest_init+0x4e/0x60
start_kernel+0x310/0x37c
unknown_bootoption+0x0/0x1f8
__init_begin+0x99/0xa1

Revision history for this message
Jeremy Nickurak (nickurak) wrote :

pci=noacpi doesn't help

acpi=off gets the system booting, but then it a) doesn't see the hyperthreading, and b) X locks with a black screen.

Revision history for this message
Valde_91 (claudio-brenni) wrote :

Also here!

My 2140 boot with dual core option enabled, without the acpi=off option. The 2140 it's faster with this option enabled. Also stand-by works.

The problem is when I hibernate the pc: when I reboot I've got a similar screen, with these kernel's output lines.

And Acpi is able to detect if the lid is open or close, but even if the power-manger is set to stand-by on closed lid, nothing happend.

thanks Valde_91

Revision history for this message
Jeremy Nickurak (nickurak) wrote :

Valde: Are you saying your 2140 boots successfully with dual-core enabled? Mine doesn't boot even once.

The acpi lid-close bug is filed as https://bugs.launchpad.net/bugs/376793

Revision history for this message
Valde_91 (claudio-brenni) wrote :

Yes my Hp 2140 with dual core mode.

But: 1. I've tried only booting up from battery. (following this thread: http://ubuntuforums.org/showthread.php?t=1088743& page=3, the bug is present when you start with AC cable)

        2. I've installed ubuntu with the dual core disabled

Last thing, I don't know if that could do any difference, I use ext4 format on my HD

Bye bye

Valde_91

Revision history for this message
Jeremy Nickurak (nickurak) wrote :

I've since confirmed that this problem only occurs when the AC power is plugged into the computer. If I plug in the AC adapter AFTER booting, I can keep hyperthreading working. I've only tried this for a little while at a time, so it's unclear if there's other side-effects.

Revision history for this message
Valde_91 (claudio-brenni) wrote :

Today i boot my 2140 without the cable. I hibernate the pc. First trying to rebbot fails: I had a screen similar to the one reported. So I forced shut down by pressing the shut down button. Then I rebooted, the 2140 wakes up correctely from hibernation, hyper-treading was still working and even closing the lid put my pc in stand-by.

So I wondering what tyoe of information are reseted in a forces shut down? because after this the ACPI module seems to work perfectly.

thanks Valde

Andrej Zirko (dixon85)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
joko (giorgiochiodi) wrote :

Ah, that's why it doesn't work.
Same problem here. I didn't have this problem with the previous version of ubuntu, only on jaunty...

joko

Revision history for this message
joko (giorgiochiodi) wrote :

My system boots on battery, no luck with the power cable attached.
Sometimes it won't boot even on battery power.

jk

Revision history for this message
Jeremy Nickurak (nickurak) wrote :

http://forums.fedoraforum.org/showthread.php?t=218219 suggests adding a boot_delay=5 kernel parameter to grub.

Revision history for this message
Yan Maurakh (yan-maurakh) wrote :

Guys, did anyone try possible solution? Dit it work ? I'am talking about adding boot_delay=5 in grub or kernel 2.6.29

Revision history for this message
Jeremy Nickurak (nickurak) wrote :

The boot_delay one didn't work for me, but others reported success.

Revision history for this message
Freestyler (freestyler-kiev) wrote :

Have same problem, methods AC Power Off & boot_delay didn't work.

Revision history for this message
Jeremy Nickurak (nickurak) wrote :

Appears to have gone away when I upgraded to kernel 2.6.29-02062904-generic from the kernel-ppa

Revision history for this message
joko (giorgiochiodi) wrote :

thanks, but boot_delay didn't help at all.

Revision history for this message
peter (str3zz) wrote :

confirmed - upgrade to 2.6.29.4 (2.6.29-02062904-generic) from kernel-ppa fix this behaviour

Revision history for this message
wtsch (trash4inbox) wrote :

Is the kernel 2.6.29.4 (2.6.29-02062904-generic) from kernel-ppa optimized for netbooks?

Revision history for this message
Jon Hale (jon-gorillacon) wrote :

Are there up-to-date instructions anywhere for how to perform the upgrade to 2.6.29.4 (2.6.29-02062904-generic) from kernel-ppa?

I seem to be looking at a bunch of out-of-date wikis for doing this and am missing the correct incantation.

Revision history for this message
Jon Hale (jon-gorillacon) wrote :

OK, I figured out how to do that, for other people in the same boat:
wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.29.4/linux-headers-2.6.29-02062904-generic_2.6.29-02062904_i386.deb
wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.29.4/linux-image-2.6.29-02062904-generic_2.6.29-02062904_i386.deb
wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.29.4/linux-headers-2.6.29-02062904_2.6.29-02062904_all.deb

Then:
sudo dpkg linux-*.deb

Then after I rebooted (and changed my bios settings for hyperthreading) linux boots and sees two processors (at least according to the system monitor).

Revision history for this message
Jon Hale (jon-gorillacon) wrote :

typo in my last step... s/b

sudo dpkg -i linux-*.deb

Revision history for this message
Gyorgyi Toth (tgyorgyi27) wrote :

Hi, I tried this suggestion, and I too had the two CPUs in systems monitor, BUT NO WIFI. Has anybody else experienced anything like this? I have booted now 2.6.28-14 and the wifi works again (but of course I had to disable dual core).

Revision history for this message
Bane (rudlavibizon) wrote :

@gyorgyi You need to compile kernel modules for broadcom drivers. I did this with 2.6.29 but unfortunately not with 2.6.30 though some people did it with success. Useful link: http://ubuntuforums.org/showpost.php?p=7389529&postcount=30

Revision history for this message
Gyorgyi Toth (tgyorgyi27) wrote :

@Bane Thank you, I have actually read part of that thread, but am not experienced enough yet to read the right things out of it obviously... I've started using Ubuntu 1 year and 2 months ago, and had fun with learning something week-by-week... and I think I learned most because of the bugs along the way, and of course because of folks ready to spend time answering even very obvious questions.

Revision history for this message
Kenjie.-San (darthkenjie) wrote :

same to me. i am using kubuntu 9.04.
sometimes it was possible for me to start with dualcore and it was recognized, but after rebooting the system did not come up or it was not available.

Revision history for this message
Jocelyn Habib (jhabib) wrote : Re: [Bug 376728] Re: HP-2140 won't boot with dual-core enabled

please try this and will fix your issue http://jhabib.lebos.org/

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.