[redhat-lspp] lspp 66 kernel released
Eric Paris
eparis at redhat.com
Mon Feb 26 19:33:40 UTC 2007
I've been rebooting the .67 kernel (same as .65 but with more debug
features turned on and I expect to see this in your repo soon) over and
over on my one machine and haven't seen any problems. Can you tell me
what your audit rules look like and what operations you may be done on
this before this panic?
-Eric
On Sun, 2007-02-25 at 19:28 -0500, Steve Grubb wrote:
> On Sunday 25 February 2007 15:04:00 Steve Grubb wrote:
> > Please let me know if there any problems with this kernel.
>
> I just saw a panic on shutdown with this kernel that the lspp.65 kernel does
> not have:
>
> Kernel panic - not syncing: nmi watchdog
> BUG: warning at kernel/panic.c:137/panic() (Not tainted)
>
> Call Trace:
> <NMI> [<ffffffff8008b476>] panic+0x1e3/0x1f4
> [<ffffffff80069261>] _show_stack_0xdb/0xea
> [<ffffffff80069354>] show_registers+0xe4/0x100
> [<ffffffff8006300b>] die_nmi+0x66/0xa3
> [<ffffffff8006368d>] nmi_watchdog_tick+0x105/0x1a6
> [<ffffffff80063374>] default_do_nmi+0x86/0x214
> [<ffffffff80063771>] do_nmi_0x43/0x61
> [<ffffffff80062c2f>] nmi+0x7f/0x88
> [<ffffffff801ffdce>] sock_destroy_inode+0x0/0x10
> [<ffffffff8005fd61>]__write_lock_failed+0x9/0x20
> <<EOE>> [<ffffffff800626c3>] _write_lock_irq+0xf/0x10
> [<ffffffff80015177>] do_exit_0x548/0x8b1
> [<ffffffff80046eae>] cpuset_exit+0x0/0x6c
> [<ffffffff8002abcf>] get_signal_to_deliver+0x427/0x456
> [<ffffffff80059109>] do_notify_resume+0x9c/0x7a9
> [<ffffffff8009d486>] enqueue_hrtimer+0x55/0x70
> [<ffffffff8003bb2c>] hrtimer_start+0xbc/0xce
> [<ffffffff800b2261>] audit_syscall_exit+0x2cd/0x2ec
> [<ffffffff8005b362>] int_signal+0x12/0x17
>
> --
> redhat-lspp mailing list
> redhat-lspp at redhat.com
> https://www.redhat.com/mailman/listinfo/redhat-lspp
More information about the redhat-lspp
mailing list