Bug 14661 - syslog reports WARNING at hpet.c:390.
Summary: syslog reports WARNING at hpet.c:390.
Status: CLOSED OBSOLETE
Alias: None
Product: Platform Specific/Hardware
Classification: Unclassified
Component: x86-64 (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: platform_x86_64@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-22 03:05 UTC by James Watson
Modified: 2012-06-14 14:17 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.31
Subsystem:
Regression: No
Bisected commit-id:


Attachments
lspci output and syslog extract (127.94 KB, text/plain)
2009-11-22 03:05 UTC, James Watson
Details

Description James Watson 2009-11-22 03:05:55 UTC
Created attachment 23866 [details]
lspci output and syslog extract

The system appears to run normally, except for a single message from
GNOME: "Your system had a kernel failure". However, hpet.c:390 is an
invocation of macro WARN_ON_ONCE, so I wonder if the system might be taking a performance hit if the fault is actually occurring many times (see below for more information on this).

I have attached a syslog, which I obtained after booting with hpet=verbose. 

I have also reported the fault as Debian bug report 557033. 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557033

The computer is a new Intel core i7-860, Chipset P55, Gigabyte P55UD3p, nVidia Geforce 9600GT. Two Seagate 1TB disks in mirrored RAID configuration.

History of my installation: Initially I installed the 32-bit version of
lenny: debian-502-i386-DVD-n.iso. When I booted the system, it wrote WARNING messages from hpet.c at the rate of megabytes per minute. I then installed the 64-bit version of lenny: debian-503-amd64-DVD-n.iso.

hpet.c:390 from linux-image-2.6.31-1-amd64 invokes WARN_ON_ONCE, but my previous
experience with the 32-bit distribution makes me believe that the fault is in fact occurring many times per second, and hence I wonder if there might be a performance hit.
Comment 1 Alan 2012-06-14 14:16:57 UTC
Closing as obsolete, if this is still seen with modern kernels please update the bug, thanks

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