reassign 572339 src:linux-2.6 2.6.32-9
tags 572339 = moreinfo
quit

Hi Harri,

Harald Dunkel wrote:

> I get this at boot time:
>
> [ 18.521817] ------------[ cut here ]------------
> [ 18.521823] WARNING: at /build/mattems-linux-2.6_2.6.32-9-amd64-NYTFdD/linux-2.6-2.6.32-9/debian/build/source_amd64_none/arch/x86/kernel/hpet.c:392 hpet_next_event+0x52/0x77()
> [ 18.521825] Hardware name: S3420GP
> [ 18.521826] Modules linked in: processor ext3 jbd mbcache sg sd_mod crc_t10dif sr_mod cdrom ide_pci_generic ide_core usbhid hid ata_generic ata_piix libata ehci_hcd igb usbcore nls_base 3w_9xxx dca e1000e scsi_mod button thermal fan thermal_sys [last unloaded: scsi_wait_scan]
> [ 18.521837] Pid: 0, comm: swapper Not tainted 2.6.32-3-amd64 #1
> [ 18.521838] Call Trace:
> [ 18.521841] [<ffffffff8102b587>] ? hpet_next_event+0x52/0x77
> [ 18.521843] [<ffffffff8102b587>] ? hpet_next_event+0x52/0x77
> [ 18.521846] [<ffffffff8104dbf0>] ? warn_slowpath_common+0x77/0xa3
> [ 18.521848] [<ffffffff8102b587>] ? hpet_next_event+0x52/0x77
> [ 18.521852] [<ffffffff8106fa87>] ? tick_dev_program_event+0x2d/0x95
> [ 18.521854] [<ffffffff8106f505>] ? tick_broadcast_oneshot_control+0x9c/0xf4
> [ 18.521856] [<ffffffff8106eecf>] ? tick_notify+0x218/0x36e
> [ 18.521859] [<ffffffff810681bd>] ? notifier_call_chain+0x29/0x4c
> [ 18.521861] [<ffffffff8106e8fb>] ? clockevents_notify+0x31/0x115
> [ 18.521864] [<ffffffffa018c4f6>] ? acpi_idle_enter_bm+0x26a/0x29e [processor]
> [ 18.521867] [<ffffffffa018c3fe>] ? acpi_idle_enter_bm+0x172/0x29e [processor]
> [ 18.521871] [<ffffffff8122e7d6>] ? menu_select+0x145/0x205
> [ 18.521873] [<ffffffff8122dad7>] ? cpuidle_idle_call+0x95/0xee
> [ 18.521877] [<ffffffff8100fe90>] ? cpu_idle+0xa2/0xda
> [ 18.521879] ---[ end trace b560c22fc289f32e ]---

Do you still have access to this hardware? If so, what kernel are you
using these days and how does it behave?

If 3.x.y kernels reproduce this, we should reopen it upstream. If they
don't, we can try to find what change fixed it and apply that to stable.

Hope that helps,
Jonathan



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/20120628214300.GA7824@burratino

Hi Jonathan,

I've got a new PC in the meantime (running Squeeze and
the 3.2.x backports kernel). I am sorry, but the old PC
is running Testing now.

AFAICS the problem doesn't come up with the 3.2.x kernel.
>From my side its OK to drop this bug report.


Regards

Harri



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4FED58AC.3020501@aixigo.de">http://lists.debian.org/4FED58AC.3020501@aixigo.de

tags 572339 - moreinfo
fixed 572339 linux/3.2.20-1
quit

Harald Dunkel wrote:

> AFAICS the problem doesn't come up with the 3.2.x kernel.

Ok, nice to hear. Marking so.

> From my side its OK to drop this bug report.

Thanks for the update.

I'd prefer to get this fixed in squeeze if it's easy. Leaving this
open for now in case someone has time to find the relevant patch, but
if nothing happens in a few months then we should probably close it,
yes.

Jonathan



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/20120629090241.GD3430@burratino