Bug#557033: linux-image-2.6.31-1-amd64: Kernel logs WARNING at hpet.c:390.
Subject: linux-image-2.6.31-1-amd64: Kernel logs WARNING at hpet.c:390.
Package: linux-2.6
Version: 2.6.31-1
Severity: normal
*** Please type your report below this line ***
syslog reports WARNING at hpet.c:390.
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).
The computer is a new Intel core i7-860, Chipset P55, Gigabyte P55UD3p,
nVidia Geforce 9600GT. Two Seagate 1TB disks in mirrored RAID
configuration.
The fault initially occurred in the stable lenny distribution with
kernel 2.6.26.
I installed linux-image-2.6.31-1-amd64 from sid to see if it would go
away. It didn't.
A similar fault in linux-image-2.6.26-1-686 was reported in bug report
512617 in January 2009, and closed in July 2009.
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.
-- Package-specific info:
** Version:
Linux version 2.6.31-1-amd64 (Debian 2.6.31-1) (waldi@debian.org) (gcc
version 4.3.4 (Debian 4.3.4-5) ) #1 SMP Sat Oct 24 17:50:31 UTC 2009
** Tainted: W (512)
* Taint on warning.
** Kernel log:
[ 5.049081] sdb14 sdb15 >
[ 5.072861] sd 5:0:0:0: [sdb] Attached SCSI disk
[ 5.081135] sd 4:0:0:0: Attached scsi generic sg0 type 0
[ 5.081153] sd 5:0:0:0: Attached scsi generic sg1 type 0
[ 5.081172] sr 7:0:0:0: Attached scsi generic sg2 type 5
[ 5.236070] device-mapper: uevent: version 1.0.3
[ 5.236630] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01)
initialised: dm-devel@redhat.com
[ 5.926876] PM: Starting manual resume from disk
[ 5.950589] kjournald starting. Commit interval 5 seconds
[ 5.950594] EXT3-fs: mounted filesystem with ordered data mode.
[ 6.702415] udevd version 125 started
[ 6.978535] Monitor-Mwait will be used to enter C-1 state
[ 6.978593] Monitor-Mwait will be used to enter C-2 state
[ 6.998699] Monitor-Mwait will be used to enter C-3 state
[ 6.998762] ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3])
[ 6.998794] processor LNXCPU:00: registered as cooling_device0
[ 6.998799] ACPI: Processor [CPU0] (supports 8 throttling states)
[ 6.998857] input: Power Button as
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
[ 6.998863] ACPI: Power Button [PWRF]
[ 6.999463] input: Power Button as
/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input4
[ 8.203674] alloc irq_desc for 22 on node 0
[ 8.203676] alloc kstat_irqs on node 0
[ 8.203683] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low)
-> IRQ 22
[ 8.203818] HDA Intel 0000:00:1b.0: setting latency timer to 64
[ 9.237210] hda-intel: azx_get_response timeout, switching to polling
mode: last cmd=0x300f0000
[ 10.238531] hda-intel: Codec #3 probe error; disabling it...
[ 10.395179] input: HDA Digital PCBeep as
/devices/pci0000:00/0000:00:1b.0/input/input6
[ 11.412062] EXT3 FS on dm-3, internal journal
[ 12.126089] loop: module loaded
[ 13.937336] kjournald starting. Commit interval 5 seconds
[ 13.937716] EXT3 FS on dm-11, internal journal
[ 13.937724] EXT3-fs: mounted filesystem with ordered data mode.
[ 13.965423] kjournald starting. Commit interval 5 seconds
[ 13.965812] EXT3 FS on dm-12, internal journal
[ 13.965819] EXT3-fs: mounted filesystem with ordered data mode.
[ 14.009809] kjournald starting. Commit interval 5 seconds
[ 14.010186] EXT3 FS on dm-13, internal journal
[ 14.010193] EXT3-fs: mounted filesystem with ordered data mode.
[ 14.052662] kjournald starting. Commit interval 5 seconds
[ 14.053028] EXT3 FS on dm-10, internal journal
[ 14.053035] EXT3-fs: mounted filesystem with ordered data mode.
[ 14.084253] kjournald starting. Commit interval 5 seconds
[ 14.084982] EXT3 FS on dm-5, internal journal
[ 14.084989] EXT3-fs: mounted filesystem with ordered data mode.
[ 14.114298] kjournald starting. Commit interval 5 seconds
[ 14.115028] EXT3 FS on dm-4, internal journal
[ 14.115036] EXT3-fs: mounted filesystem with ordered data mode.
[ 14.141717] Adding 15623172k swap on
/dev/mapper/isw_ifdfaidbh_Volume011. Priority:-1 extents:1
across:15623172k
[ 15.250398] eth1: link up, 100Mbps, full-duplex, lpa 0x45E1
[ 16.903957] lp0: using parport0 (interrupt-driven).
[ 16.919208] ppdev: user-space parallel port driver
[ 25.472787] eth1: no IPv6 routers present
[ 51.106306] r8169: eth0: link down
[ 51.107683] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 65.832568] eth1: no IPv6 routers present
** Network interface configuration:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
Latency: 0
Interrupt: pin B routed to IRQ 34
Region 0: I/O ports at f800 [size=8]
Region 1: I/O ports at f700 [size=4]
Region 2: I/O ports at f600 [size=8]
Region 3: I/O ports at f500 [size=4]
Region 4: I/O ports at f400 [size=32]
Region 5: Memory at fbffd000 (32-bit, non-prefetchable) [size=2K]
Capabilities: <access denied>
Kernel driver in use: ahci
Kernel modules: ahci
Interrupt: pin C routed to IRQ 18
Region 0: Memory at fbffc000 (64-bit, non-prefetchable) [size=256]
Region 4: I/O ports at 0500 [size=32]
Kernel driver in use: i801_smbus
Kernel modules: i2c-i801
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 12
Region 0: Memory at f8000000 (32-bit, non-prefetchable) [size=16M]
Region 1: Memory at e0000000 (64-bit, prefetchable) [size=256M]
Region 3: Memory at f6000000 (64-bit, non-prefetchable) [size=32M]
Region 5: I/O ports at af00 [size=128]
[virtual] Expansion ROM at f9000000 [disabled] [size=512K]
Capabilities: <access denied>
Kernel modules: nvidiafb
02:00.0 SATA controller [0106]: JMicron Technologies, Inc. JMicron
20360/20363 AHCI Controller [197b:2363] (rev 02) (prog-if 01 [AHCI 1.0])
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin B routed to IRQ 17
Region 0: I/O ports at ef00 [size=8]
Region 1: I/O ports at ee00 [size=4]
Region 2: I/O ports at ed00 [size=8]
Region 3: I/O ports at ec00 [size=4]
Region 4: I/O ports at eb00 [size=16]
Capabilities: <access denied>
Kernel driver in use: pata_jmicron
Kernel modules: ide-pci-generic, ata_generic, pata_jmicron
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 33
Region 0: I/O ports at de00 [size=256]
Region 2: Memory at fbaff000 (64-bit, prefetchable) [size=4K]
Region 4: Memory at fbaf8000 (64-bit, prefetchable) [size=16K]
[virtual] Expansion ROM at fba00000 [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: r8169
Kernel modules: r8169
04:00.0 SATA controller [0106]: JMicron Technologies, Inc. JMicron
20360/20363 AHCI Controller [197b:2363] (rev 03) (prog-if 01 [AHCI 1.0])
Latency: 0
Interrupt: pin B routed to IRQ 16
Region 0: I/O ports at cf00 [size=8]
Region 1: I/O ports at ce00 [size=4]
Region 2: I/O ports at cd00 [size=8]
Region 3: I/O ports at cc00 [size=4]
Region 4: I/O ports at cb00 [size=16]
Capabilities: <access denied>
Kernel driver in use: pata_jmicron
Kernel modules: ide-pci-generic, ata_generic, pata_jmicron
Latency: 64 (8000ns min, 16000ns max)
Interrupt: pin A routed to IRQ 16
Region 0: I/O ports at be00 [size=256]
Region 1: Memory at fbcff000 (32-bit, non-prefetchable) [size=256]
Capabilities: <access denied>
Kernel driver in use: 8139too
Kernel modules: 8139too
** USB devices:
Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 002: ID 046d:c529 Logitech, Inc.
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Kernel: Linux 2.6.31-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages linux-image-2.6.31-1-amd64 depends on:
ii debconf [debconf-2.0] 1.5.24 Debian configuration
management sy
ii initramfs-tools [linux-initra 0.92o tools for generating an
initramfs
ii module-init-tools 3.4-1 tools for managing Linux
kernel mo
Versions of packages linux-image-2.6.31-1-amd64 recommends:
ii firmware-linux-free 2.6.31-1 Binary firmware for various
driver
Versions of packages linux-image-2.6.31-1-amd64 suggests:
ii grub 0.97-47lenny2 GRand Unified Bootloader
(Legacy v
pn linux-doc-2.6.31 <none> (no description available)
Versions of packages linux-image-2.6.31-1-amd64 is related to:
pn firmware-bnx2 <none> (no description available)
pn firmware-bnx2x <none> (no description available)
pn firmware-ipw2x00 <none> (no description available)
pn firmware-ivtv <none> (no description available)
pn firmware-iwlwifi <none> (no description available)
pn firmware-linux <none> (no description available)
pn firmware-linux-nonfree <none> (no description available)
pn firmware-qlogic <none> (no description available)
pn firmware-ralink <none> (no description available)
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
11-21-2009, 05:33 PM
Ben Hutchings
Bug#557033: linux-image-2.6.31-1-amd64: Kernel logs WARNING at hpet.c:390.
On Thu, 2009-11-19 at 14:16 +1100, Gerry Butler wrote:
> Subject: linux-image-2.6.31-1-amd64: Kernel logs WARNING at hpet.c:390.
> Package: linux-2.6
> Version: 2.6.31-1
> Severity: normal
>
> *** Please type your report below this line ***
> syslog reports WARNING at hpet.c:390.
>
> 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).
>
> The computer is a new Intel core i7-860, Chipset P55, Gigabyte P55UD3p,
> nVidia Geforce 9600GT. Two Seagate 1TB disks in mirrored RAID
> configuration.
>
> The fault initially occurred in the stable lenny distribution with
> kernel 2.6.26.
>
> I installed linux-image-2.6.31-1-amd64 from sid to see if it would go
> away. It didn't.
[...]
Please report this upstream at <http://bugzilla.kernel.org> under the
product 'Platform Specific/Hardware' and component 'x86-64'. Let us
know the bug number so we can track it.
You may get some useful information for the upstream developers to work
on by booting with 'hpet=verbose' added to the kernel command line.
Ben.
--
Ben Hutchings
Unix is many things to many people,
but it's never been everything to anybody.
02-03-2010, 10:26 AM
maximilian attems
Bug#557033: linux-image-2.6.31-1-amd64: Kernel logs WARNING at hpet.c:390.
On Thu, 19 Nov 2009, Gerry Butler wrote:
> Subject: linux-image-2.6.31-1-amd64: Kernel logs WARNING at hpet.c:390.
> Package: linux-2.6
> Version: 2.6.31-1
> Severity: normal
>
can you still reproduce that with latest 2.6.32?
available in unstable and older one in squeeze
thanks for feedback.
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
02-24-2010, 04:10 PM
maximilian attems
Bug#557033: linux-image-2.6.31-1-amd64: Kernel logs WARNING at hpet.c:390.
hello
[ please keep bug report on cc this is not private conversation
and got lost in such! ]
On Sat, 06 Feb 2010, Gerry Butler wrote:
> Thank you.
>
> I can't start linux at all with 2.6.32.
>
> apt-get warned that some drivers used on the system are unavailable.
you seem to confuse firmware and drivers.
and rtl8168d can not be related to booting unless you are netbooting,
which i kind of doubt.
> It will be a week or more before I can devote more time to it. Anyhow, at this point I don't know how to get the required drivers. When I installed 2.6.31, I didn't need to get any additional drivers.
>
> When I try to boot, very early in the boot process it dumps a trace to the screen then freezes. ctrl-alt-del does nothing, and I need to hit the system reset button to continue (ie, to reboot).
>
> This is how I installed it:
>
> apt-get -t sid install linux-image-2.6-amd64
>
> I'm fairly new to linux (coming from Windows), so I'm not sure if I've just made some stupid mistake.
well unless you can't reproduce the message with 2.6.32
this bug can be closed.
for assistance on the upgrade just use the #debian irc channel.
it is for user support.
kind regards
--
maks
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100224171000.GC11859@stro.at">http://lists.debian.org/20100224171000.GC11859@stro.at
02-26-2010, 12:38 AM
Gerry Butler
Bug#557033: linux-image-2.6.31-1-amd64: Kernel logs WARNING at hpet.c:390.
Good morning
> well unless you can't reproduce the message with 2.6.32
> this bug can be closed.
I can neither confirm nor deny that 2.6.32 fixes bug#557033, because I can't boot 2.6.32, and at the moment I can't devote more time to it.
It's clearly a good policy to close bugs that cannot be confirmed to still exist, so I am happy to close it. We can always create a new bug report (or reopen this one) if the bug still exists when 2.6.32 makes it to a stable release.
Nevertheless, the related bug I entered upstream in bugzilla.kernel.org (14661) seems to be still open. It's been assigned to platform_x86_64@kernel-bugs.osdl.org, but there is no other indication of progress.
In the meantime, bug#557033 doesn't seem to be having any deleterious effect, except for a message in syslog.
Regarding my attempt to boot 2.6.32:
When I installed 2.6.31, it installed and booted cleanly, but 2.6.32 didn't.
> you seem to confuse firmware and drivers.
> and rtl8168d can not be related to booting unless you are netbooting,
> which i kind of doubt.
I know that rtl8168d is the Realtek firmware, but nevertheless the apt log used the terminology "driver not available".
The freeze that occurs early in the boot process for 2.6.32, even before syslog is open, clearly has nothing to do with the Realtek; (as you say, I'm not booting from a network), and probably nothing to do with hpet.c; so that's an entirely different problem.
Thank you for the time you have devoted to it.
Regards
Gerry
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201002261238.01065.gabutler@acslink.net.au">http://lists.debian.org/201002261238.01065.gabutler@acslink.net.au
02-27-2010, 01:22 AM
Ben Hutchings
Bug#557033: linux-image-2.6.31-1-amd64: Kernel logs WARNING at hpet.c:390.
On Fri, 2010-02-26 at 12:38 +1100, Gerry Butler wrote:
[...]
> > you seem to confuse firmware and drivers.
> > and rtl8168d can not be related to booting unless you are
> netbooting,
> > which i kind of doubt.
>
> I know that rtl8168d is the Realtek firmware, but nevertheless the apt
> log used the terminology "driver not available".
>
> The freeze that occurs early in the boot process for 2.6.32, even
> before syslog is open, clearly has nothing to do with the Realtek; (as
> you say, I'm not booting from a network), and probably nothing to do
> with hpet.c; so that's an entirely different problem.
There is a known bug in firmware loading that can lead to a 1 minute
delay in the boot process. Did you wait that long?
Ben.
--
Ben Hutchings
I'm always amazed by the number of people who take up solipsism because
they heard someone else explain it. - E*Borg on alt.fan.pratchett
03-01-2010, 01:25 AM
Gerry Butler
Bug#557033: linux-image-2.6.31-1-amd64: Kernel logs WARNING at hpet.c:390.
I can confirm that Bug#557033 is still present in 2.6.32
Gerry
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201003011325.26969.gabutler@acslink.net.au">http://lists.debian.org/201003011325.26969.gabutler@acslink.net.au
03-01-2010, 01:40 AM
Gerry Butler
Bug#557033: linux-image-2.6.31-1-amd64: Kernel logs WARNING at hpet.c:390.
Yes, I waited more than a minute.
I have subsequently investigated the problem booting 2.6.32 more carefully.
I suspect it is a bug you might want to know about, unrelated to Bug#557033, so I am about to create a fresh bug report.
Some of the information I gave earlier in this thread related to the problem booting 2.6.32 was ill-considered and inaccurate. Please ignore it, and start again with my fresh report.
Gerry
---- Original Message ----:
> There is a known bug in firmware loading that can lead to a 1 minute
> delay in the boot process. Did you wait that long?
Ben.
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201003011340.53660.gabutler@acslink.net.au">http://lists.debian.org/201003011340.53660.gabutler@acslink.net.au