Re: WARN_ON causes recursive unwind panic

On Wednesday 02 August 2006 23:59, Stephen Hemminger wrote:

> [ 4202.665764]  [<ffffffff8103440e>] run_timer_softirq+0x147/0x1d0
> [ 4202.683541]  [<ffffffff81030bc0>] __do_softirq+0x67/0xf4
> [ 4202.699506]  [<ffffffff8100ab66>] call_softirq+0x1e/0x28

That is already fixed and submitted, but L. hasn't merged the patch yet.

ftp://ftp.firstfloor.org/pub/ak/x86_64/quilt/patches/entry-more-unwind

Also please cc Jan Beulich <[email protected]> with unwinder problems.

-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:
  • WARN_ON causes recursive unwind panic
    • From: Stephen Hemminger <[email protected]>

• Prev by Date: md/dm lockdep bug.
• Next by Date: Re: [patch] x86: rename is_at_popf(), add iret to tests and fix insn length
• Previous by thread: WARN_ON causes recursive unwind panic
• Next by thread: md/dm lockdep bug.
• 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]