Your message dated Wed, 10 Jul 2013 17:31:22 +0200 with message-id <[email protected]> and subject line Re: [squeeze] WARNING at arch/x86/kernel/hpet.c:390 (Re: problem(?) with hpet at boot time) has caused the Debian Bug report #572339, regarding problem(?) with hpet at boot time to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 572339: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572339 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: linux-image-2.6.32-trunk-amd64 Version: 2.6.32-5 I get this at boot time: [ 20.223662] ------------[ cut here ]------------ [ 20.327765] WARNING: at /build/buildd-linux-2.6_2.6.32-5-amd64-9RvY2G/linux-2.6-2.6.32/debian/build/source_amd64_none/arch/x86/kernel/hpet.c:390 hpet_next_event+0x52/0x77() [ 20.548082] Hardware name: S3420GP [ 20.655840] Modules linked in: snd_pcsp snd_pcm snd_timer snd soundcore snd_page_alloc i2c_i801 evdev i2c_core processor(+) ext3 jbd mbcache sg sr_mod sd_mod cdrom crc_t10dif usbhid ide_pci_generic hid ide_core ata_generic ehci_hcd ata_piix usbcore nls_base igb dca libata 3w_9xxx scsi_mod e1000e button thermal fan thermal_sys [last unloaded: scsi_wait_scan] [ 20.990638] Pid: 0, comm: swapper Not tainted 2.6.32-trunk-amd64 #1 [ 21.099023] Call Trace: [ 21.203387] [<ffffffff8102b587>] ? hpet_next_event+0x52/0x77 [ 21.306823] [<ffffffff8102b587>] ? hpet_next_event+0x52/0x77 [ 21.406201] [<ffffffff8104dc34>] ? warn_slowpath_common+0x77/0xa3 [ 21.504580] [<ffffffff8102b587>] ? hpet_next_event+0x52/0x77 [ 21.602332] [<ffffffff8106fa83>] ? tick_dev_program_event+0x2d/0x95 [ 21.700266] [<ffffffff8106f501>] ? tick_broadcast_oneshot_control+0x9c/0xf4 [ 21.798280] [<ffffffff8106eecb>] ? tick_notify+0x218/0x36e [ 21.895260] [<ffffffff81068215>] ? notifier_call_chain+0x29/0x4c [ 21.991939] [<ffffffff8106e903>] ? clockevents_notify+0x31/0x109 [ 22.088291] [<ffffffffa01903f7>] ? acpi_idle_enter_bm+0x172/0x29e [processor] [ 22.185531] [<ffffffff812278f2>] ? menu_select+0x145/0x205 [ 22.282136] [<ffffffff81226bf3>] ? cpuidle_idle_call+0x95/0xee [ 22.377302] [<ffffffff8100fe6f>] ? cpu_idle+0xa2/0xda [ 22.470879] ---[ end trace e88579a6cd9c6b2a ]--- The machine seemms to work, though. Regards Harri
--- End Message ---
--- Begin Message ---On Fri, Jun 29, 2012 at 09:26:36AM +0200, Harald Dunkel wrote: > 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. Ok, closing. Wheezy is stable and includes 3.2. Cheers, Moritz
--- End Message ---
