Re: [Nasty crash on boot] was Re: 2.6.19-rc2-mm2

> > Pid: 5, comm: ksoftirqd/1 Not tainted 2.6.19-rc2-mm2 #1
> > RIP: 0010:[<ffffffff80267849>]  [<ffffffff80267849>] dump_trace+0x3a9/0x422

This might have been related to the uninitialized cpu variable which
made the interrupt stacks uninitialized
Another patch broke that and gcc even warned about it but I only fixed  
it today.

It was only in -mm* for a short time too.

-Andi

-
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.19-rc2-mm2
    • From: Andrew Morton <[email protected]>
  • [Nasty crash on boot] was Re: 2.6.19-rc2-mm2
    • From: Reuben Farrelly <[email protected]>
  • Re: [Nasty crash on boot] was Re: 2.6.19-rc2-mm2
    • From: Andrew Morton <[email protected]>

• Prev by Date: Re: Strange errors from e1000 driver (2.6.18)
• Next by Date: Re: Hopefully, kmalloc() will always succeed, but if it doesn't then....
• Previous by thread: Re: [Nasty crash on boot] was Re: 2.6.19-rc2-mm2
• Next by thread: Re: 2.6.19-rc2-mm2
• 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]