Re: 2.6.18-rc1-mm1 panic on boot x86_64 NMI watchdog detected LOCKUP

On 7/11/06, Shailabh Nagar <[email protected]> wrote:

Andrew Morton wrote:
> Thanks.  Shailabh sent the below patch through yesterday.  It looks awfully
> similar.


Yes, this lockup on boot is caused by not initializing the per-cpu
semaphores early enough. The patch below should fix it.

Thanks.  I applied the patch and the system booted :)

Keith
-
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/

---

• References:
  • 2.6.18-rc1-mm1 panic on boot x86_64 NMI watchdog detected LOCKUP
    • From: "Keith Mannthey" <[email protected]>
  • Re: 2.6.18-rc1-mm1 panic on boot x86_64 NMI watchdog detected LOCKUP
    • From: Andrew Morton <[email protected]>
  • Re: 2.6.18-rc1-mm1 panic on boot x86_64 NMI watchdog detected LOCKUP
    • From: Shailabh Nagar <[email protected]>

• Prev by Date: Re: RFC: cleaning up the in-kernel headers
• Next by Date: oops in bttv
• Previous by thread: Re: 2.6.18-rc1-mm1 panic on boot x86_64 NMI watchdog detected LOCKUP
• Next by thread: [PATCH 0/2] mm: measuring resource demand
• 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]