From: Jeroen Vreeken (kzbjxras@mx.dy.fi)
Date: Thu Oct 17 2002 - 22:17:21 EEST
On 2002.10.17 20:41:54 +0200 Kjell Jarl wrote:
> > No it isn't. This bug is only in 0.0.10. What exactly freezes?
>
> I get a kernel panic. Similar to
>
> > <0> Kernel panic: Aiee, killing interrupt handler!
> > In interrupt handler - not syncing
>
> I do not have a recent write down.
>
> I am using a USCC card, which I have been suspecting before. But it
> seems to be related to either netrom/node disconnects possibly with
> outstanding frames or tcp/ip started from node, or an DISC/UA at the
> ax.25 link layer.
>
> I have seen the DISC/UA in listen on a frozen vnc screen before (vnc)
> tcp retried out and the screen wanished.
I have a been chasing a bug that seems similar lately....
It looks like something goes wrong in sock_def_write_space(). It is called
as a result of kfree_skb().
I have been trying to find the cause of it but have been unsuccessfull
sofar.
The problem I have is that it only occurs about once a week, so any fix I
think I make takes at least a week to test :( unless I find a way to
trigger it faster.
Jeroen
-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to terhi.victor@logonet.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
This archive was generated by hypermail 2b30 : Thu Oct 17 2002 - 22:07:48 EEST