Bug#488273: linux-image-2.6.25-2-amd64: Hangs on a Dell Poweredge 850
On Fri, Jun 27, 2008 at 04:01:07PM +0200, Gábor Gombás wrote:
> Package: linux-image-2.6.25-2-amd64
> Version: 2.6.25-5
> Severity: normal
>
>
> Hi,
>
> Kernel 2.6.25 hangs on a Dell PowerEdge 850. This is the lockup captured
> with netconsole:
>
> [ 873.350023] NMI Watchdog detected LOCKUP on CPU 0
> [ 873.350023] CPU 0
> [ 873.350023] Modules linked in: ac battery ipt_REJECT xt_multiport iptable_nat nf_nat ipt_LOG ipt_recent nf_conntrack_ipv4 xt_state nf_conntrack xt_tcpudp ip6table_filter ip6_tables ipv6 iptable_filter ip_tables x_tables 8021q netconsole configfs ipmi_devintf ipmi_si ipmi_msghandler i2c_i801 i3000_edac rng_core button edac_core evdev i2c_core dcdbas pcspkr iTCO_wdt shpchp pci_hotplug ext3 jbd mbcache dm_mirror dm_snapshot dm_mod raid1 md_mod ide_generic ide_cd_mod cdrom sd_mod piix ide_core ata_piix ata_generic libata scsi_mod dock ehci_hcd tg3 uhci_hcd thermal processor fan
> [ 873.350023] Pid: 0, comm: swapper Not tainted 2.6.25-2-amd64 #1
> [ 873.350023] RIP: 0010:[<ffffffff802201c0>] [<ffffffff802201c0>] hpet_rtc_interrupt+0x116/0x2f7
> [ 873.350023] RSP: 0018:ffffffff805c3ed8 EFLAGS: 00000097
> [ 873.350023] RAX: 0000000000000000 RBX: 0000000000000002 RCX: 0000000000000000
> [ 873.350023] RDX: 00000000dba8fa91 RSI: 0000000000000002 RDI: 0000000000000002
> [ 873.350023] RBP: 000000010002226c R08: 0000000000000000 R09: ffff8100010070a0
> [ 873.350023] R10: ffff81010fab7e20 R11: ffff81010fab5200 R12: 00000000000000a6
> [ 873.350023] R13: 0000000000000000 R14: ffffffff805879e0 R15: 0000000000000000
> [ 873.350023] FS: 0000000000000000(0000) GS:ffffffff80520000(0000) knlGS:0000000000000000
> [ 873.350023] CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
> [ 873.350023] CR2: 00007fd937409000 CR3: 000000010d5d3000 CR4: 00000000000006e0
> [ 873.350023] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> [ 873.350023] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> [ 873.350023] Process swapper (pid: 0, threadinfo ffffffff80558000, task ffffffff804ee4a0)
> [ 873.350023] Stack: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
> [ 873.350023] ffffffff00000000 ffffffff802495ab ffffffff8021263b ffff81010d48f140
> [ 873.350023] 0000000000000000 0000000000000000 0000000000000008 ffffffff8026c077
> [ 873.350023] Call Trace:
> [ 873.350023] <IRQ> [<ffffffff802495ab>] ? ktime_get_ts+0x17/0x48
> [ 873.350023] [<ffffffff8021263b>] ? read_tsc+0x5/0x7
> [ 873.350023] [<ffffffff8026c077>] ? handle_IRQ_event+0x2c/0x61
> [ 873.350023] [<ffffffff8026d5fe>] ? handle_edge_irq+0xe0/0x120
> [ 873.350023] [<ffffffff8020f41c>] ? do_IRQ+0x6d/0xd9
> [ 873.350023] [<ffffffff8020c34d>] ? ret_from_intr+0x0/0x19
> [ 873.350023] <EOI> [<ffffffff802206e4>] ? native_safe_halt+0x2/0x3
> [ 873.350023] [<ffffffff8020ae96>] ? default_idle+0x3b/0x6e
> [ 873.350023] [<ffffffff8020ae5b>] ? default_idle+0x0/0x6e
> [ 873.350023] [<ffffffff8020af52>] ? cpu_idle+0x89/0xb3
> [ 873.350023]
> [ 873.350023]
> [ 873.350023] Code: f2 1f 00 bf 0a 00 00 00 48 89 c3 e8 5f 26 ff ff 48 89 de 41 88 c4 48 c7 c7 70 e6 5c 80 e8 bf f2 1f 00 45 84 e4 78 04 eb 12 f3 90 <48> 8b 05 b9 66 33 00 48 29 e8 48 83 f8 04 76 ee 48 c7 c7 70 e6
> [ 873.350023] ---[ end trace c6ed53b4da5f3a22 ]---
> [ 873.350039] Kernel panic - not syncing: Aiee, killing interrupt handler!
>
> I've had lockups with self-compiled 2.6.25 kernels on other hardware as
> well, all related to hpet_rtc_interrupt; see the LKML archive for the
> details. This is the first time I've tried a Debian-packaged 2.6.25, and
> it also hangs. The workaround recommended on LKML was to disable
> CONFIG_HPET_EMULATE_RTC (it cannot be disabled in the menu, you have to
> edit the configuration by hand). This workaround seems to work for me:
>
> $ uname -a
> Linux boogie 2.6.25 #3 SMP Thu Jun 12 13:32:35 CEST 2008 x86_64 GNU/Linux
> $ uptime
> 15:57:16 up 15 days, 1:43, 13 users, load average: 0.24, 0.57, 0.65
>
> Without the workaround, I never got an uptime more than a couple of
> hours. So I suggest applying the workaround to the Debian package as
> well.
Does this error still occur with more recent kernel versions?
Cheers,
Moritz
Reply to: