[1888] in athena10
Re: [Debathena] #165: HPET clock is broken on Dell 760 Hardware
daemon@ATHENA.MIT.EDU (Debathena Trac)
Thu Mar 26 14:09:15 2009
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
From: "Debathena Trac" <debathena@MIT.EDU>
Cc: debathena@mit.edu
To: wdc@mit.edu
Date: Thu, 26 Mar 2009 18:08:50 -0000
Reply-To:
Message-ID: <049.f69c04d725d94d2b2ada295cf5691bf1@mit.edu>
In-Reply-To: <040.0d9798ed56269c044b0f582f54c81772@mit.edu>
Content-Transfer-Encoding: 8bit
#165: HPET clock is broken on Dell 760 Hardware-----------------------+----------------------------------------------------
Reporter: wdc | Owner:
Type: defect | Status: new
Priority: critical | Component: dotfiles
Resolution: | Keywords:
-----------------------+----------------------------------------------------
Old description:
> Symptom:
>
> Boot Intrepid, or a variety of 2.6.26-based systems and see infinite
> spewage of errors.
>
> This is apparently a recently discovered bug with a trivial patch.
> See:
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=512617
>
> The patch being:
>
> http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.28.y.git;a=commitdiff;h=1de5b0854623d30d01d72cd4ea323eb5f39d1f16
>
> We should probably make sure this patch is in Jaunty, and gets an SRU
> into Intrepid, and possibly Hardy. The lack of this patch renders the
> system essentially unusable. When you reboot as the final phase of the
> install it looks like your system is hung with constant and un-
> interruptable spew. The seeming only way to get round it is to power
> cycle the machine.
>
> This spewage seems to run in the background of a seemingly fine system
> causing tremendous slowness, and filling up the disk with log output.
>
> So this is a biggie folks!
New description:
When you boot from older Intrepid media, you see an spew of kernel oops
messages. The apparent work-around for this is to power cycle the
machine.
A one-line change to print the error message only once is incorporated
into the Intrepid update kernel, so this symptom only affects systems
lacking the update kernel.
The warning is reporting a fault in the HPET clock which *IS* real.
It takes forever for the system to boot up, and logging in takes rather
long. The work around is to boot with the option acpi=off.
When you boot Jaunty, even from media as recent as 3/24, you get a blank
screen unless you use the boot option acpi=off.
We need to find out where the fault lies and get it fixed.
--
Comment(by wdc):
Revised description to reflect current understanding of the problem.
-- Ticket URL: <http://debathena.mit.edu/trac/ticket/165#comment:2>Debathena <http://debathena.mit.edu/>MIT Debian-Athena Project
