|
|
On Wednesday 01 March 2006 19:07, Bill Rugolsky Jr. wrote:
> Mar 1 11:39:27 ti94 kernel: time.c: Lost 1 timer tick(s)! rip
> __do_softirq+0x55/0xd4)
Yes, I bet something forgets to turn on interrupts again and it's picked up by
(and blamed on) the next guy who does an unconditional sti, which happens to be
__do_sofitrq
or idle.
> Time to instrument sata_nv, I suppose. Many thanks for helping to narrow this
> down.
Sprinkle WARN_ON(in_interrupt()) all over the parts that shouldn't have
interrupts
off.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at www.tux.org/lkml/">http://www.tux.org/lkml/
|
|