Re: NMI lockup in fib_sync_down

Phil Oester <[email protected]> wrote:
>
> Trying to update from 2.6.10 to 2.6.11 on a gateway, and keep
>  getting an NMI lockup:
> 
>  NMI Watchdog detected LOCKUP on CPU1, eip c026a8d4, registers:
>  CPU:    1
>  EIP:    0060:[<c026a8d4>]    Not tainted VLI
>  EFLAGS: 00001482   (2.6.11) 
>  EIP is at fib_sync_down+0x74/0x140

This is believed to be fixed in current kernels.  Please retest 2.6.12-rc4
or 2.6.12-rc3-mm1 (neither are released yet) and let us know if the problem
is still there?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: NMI lockup
    • From: Phil Oester <[email protected]>

• References:
  • NMI lockup in fib_sync_down
    • From: Phil Oester <[email protected]>

• Prev by Date: Re: which ioctls matter across filesystems
• Next by Date: Re: [Ext2-devel] [RFC] Adding multiple block allocation
• Previous by thread: NMI lockup in fib_sync_down
• Next by thread: Re: NMI lockup
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]