Bug 383551 - hpet_late_init panic on VIA Apollo CLE266
hpet_late_init panic on VIA Apollo CLE266
Status: CLOSED DUPLICATE of bug 394981
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Thomas Gleixner
Fedora Extras Quality Assurance
Depends On:
Blocks: K12LTSP
  Show dependency treegraph
Reported: 2007-11-14 17:30 EST by Warren Togami
Modified: 2008-08-02 19:40 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-11-28 15:23:45 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
lspci -v (6.67 KB, text/plain)
2007-11-14 17:32 EST, Warren Togami
no flags Details

  None (edit)
Description Warren Togami 2007-11-14 17:30:54 EST

Intermittently (10-20%) when booting this VIA based thin client, panics very
early in hpet_late_init.  nohpet seems to avoid the problem.  Other
distributions are reportedly not seeing this issue, so this might be a
relatively new kernel bug.
Comment 1 Warren Togami 2007-11-14 17:31:12 EST
Photo of panic
Comment 2 Warren Togami 2007-11-14 17:32:04 EST
Created attachment 259061 [details]
lspci -v
Comment 3 Warren Togami 2007-11-14 17:37:34 EST
davej suggested assigning this to tglx.
Comment 4 Chuck Ebbert 2007-11-14 18:43:34 EST
The code dump at the bottom of the page doesn't match the i586 kernel at all.

8d b4 26 00 00 00 00  is a NOP [leal 0(esi),esi]

Comment 5 Thomas Gleixner 2007-11-14 19:21:24 EST
> davej suggested assigning this to tglx.

/me grumbles :)


"Intermittently (10-20%) when booting this VIA based thin client, panics very
early in hpet_late_init."

Can you please provide the full boot log from one of the other (80-90%)
successful boots ?

Further it might be helpful, if you could capture the boot of a crash via serial

Please add

to the kernel command line and connect the box to a second one with a null
modem cable. On the second box please capture the output of the kernel.


Comment 6 Warren Togami 2007-11-15 13:22:18 EST
I will have physical access to it again tomorrow.
Comment 7 Chuck Ebbert 2007-11-28 15:23:45 EST
More info is available in the newer bug, including full oops captures.
Why a NOP instruction could cause a divide error is a real mystery...

*** This bug has been marked as a duplicate of 394981 ***

Note You need to log in before you can comment on or make changes to this bug.