Changes between Initial Version and Version 2 of Ticket #165


Ignore:
Timestamp:
03/26/09 14:08:50 (15 years ago)
Author:
wdc
Comment:

Revised description to reflect current understanding of the problem.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #165

    • Property Summary changed from 2.6.26 kernel does not get along with Dell 760 Hardware to HPET clock is broken on Dell 760 Hardware
  • Ticket #165 – Description

    initial v2  
    1 Symptom: 
     1When 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. 
    22 
    3 Boot Intrepid, or a variety of 2.6.26-based systems and see infinite spewage of errors. 
     3A 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. 
    44 
    5 This is apparently a recently discovered bug with a trivial patch. 
    6 See: 
     5The warning is reporting a fault in the HPET clock which *IS* real. 
     6It 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. 
    77 
    8 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=512617 
     8When you boot Jaunty, even from media as recent as 3/24, you get a blank screen unless you use the boot option acpi=off. 
    99 
    10 The patch being: 
    11  
    12 http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.28.y.git;a=commitdiff;h=1de5b0854623d30d01d72cd4ea323eb5f39d1f16 
    13  
    14 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. 
    15  
    16 This spewage seems to run in the background of a seemingly fine system causing tremendous slowness, and filling up the disk with log output. 
    17  
    18 So this is a biggie folks! 
     10We need to find out where the fault lies and get it fixed.