i just hit this again. The stacktrace is identical except for this bit:
other info that might help us debug this:
2 locks held by usplash_write/2182:
#0: (&tty->atomic_write_lock){--..}, at: [<c11fff5e>]
mutex_lock_interruptible+0x1c/0x1f
#1: (&dev->_xmit_lock){-+..}, at: [<c11a5118>] dev_queue_xmit+0x183/0x24b
-
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.17-mm3 -- BUG: illegal lock usage -- illegal {softirq-on-W} -> {in-softirq-R} usage.
- From: "Miles Lane" <[email protected]>
- Re: 2.6.17-mm3 -- BUG: illegal lock usage -- illegal {softirq-on-W} -> {in-softirq-R} usage.
- From: Ingo Molnar <[email protected]>
- [patch] lockdep, annotate slocks: turn lockdep off for them
- From: Ingo Molnar <[email protected]>
- Re: [patch] lockdep, annotate slocks: turn lockdep off for them
- From: Ingo Molnar <[email protected]>
- Re: [patch] lockdep, annotate slocks: turn lockdep off for them
- From: Herbert Xu <[email protected]>
- Re: [patch] lockdep, annotate slocks: turn lockdep off for them
- From: Ingo Molnar <[email protected]>
- Re: [patch] lockdep, annotate slocks: turn lockdep off for them
- From: "Miles Lane" <[email protected]>
- Re: [patch] lockdep, annotate slocks: turn lockdep off for them
- From: Ingo Molnar <[email protected]>
- Re: [patch] lockdep, annotate slocks: turn lockdep off for them
- From: "Miles Lane" <[email protected]>
- 2.6.17-mm3 -- BUG: illegal lock usage -- illegal {softirq-on-W} -> {in-softirq-R} usage.
- Prev by Date: Re: ACPI: Device [kobj-name] is not power manageable
- Next by Date: Re: SA_TRIGGER_* vs. SA_SAMPLE_RANDOM
- Previous by thread: Re: [patch] lockdep, annotate slocks: turn lockdep off for them
- Next by thread: Re: [patch] lockdep, annotate slocks: turn lockdep off for them
- Index(es):
 |