[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b93822910703191217g6dcfbc9enc4a56aff176fb370@mail.gmail.com>
Date: Mon, 19 Mar 2007 20:17:56 +0100
From: "Stefan Prechtel" <stefan.prechtel@...glemail.com>
To: tglx@...utronix.de
Cc: linux-kernel@...r.kernel.org, mingo@...e.hu, johnstul@...ibm.com
Subject: Re: BUG lapic: Can't boot on battery (2.6.21-rc{1,2,3,4})
> (Bugzilla)
> Does booting w/ clocksource=acpi_pm avoid the problem?
No, it doesn't.
I hope it's ok that I added your email to CC.
2007/3/19, Stefan Prechtel <stefan.prechtel@...glemail.com>:
> Hi!
>
> If the ac-cable is plugged in, I can start my Notebook (HP nx6325)
> without any problems.
> On battery the kernel hanging around and it takes "hours" to boot the
> kernel and the system is *very* slow. For example an init-skript takes
> very long until it's started.
>
> I did a git-bisect and found out that this is the first bad commit:
> commit e9e2cdb412412326c4827fc78ba27f410d837e6e
> Author: Thomas Gleixner <tglx@...utronix.de>
> Date: Fri Feb 16 01:28:04 2007 -0800
>
> [PATCH] clockevents: i386 drivers
>
> Add clockevent drivers for i386: lapic (local) and PIT/HPET
> (global). Update
> the timer IRQ to call into the PIT/HPET driver's event handler and the
> lapic-timer IRQ to call into the lapic clockevent driver. The
> assignement of
> timer functionality is delegated to the core framework code and replaces the
> compile and runtime evalution in do_timer_interrupt_hook()
>
> Use the clockevents broadcast support and implement the lapic_broadcast
> function for ACPI.
>
> No changes to existing functionality.
>
> So I tried to boot with nolapic on battery and with this option the
> kernel (and system) starts as it should.
> If you need more information, I will send it to you.
>
> Regards,
> Stefan Prechtel
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists