| To: | hgfelger@xxxxxxxxxxx |
|---|---|
| Subject: | Re: ISDN is killing interrupt handler on L2.4.0test9 |
| From: | Henner Eisen <eis@xxxxxxxxxxxxx> |
| Date: | Sun, 22 Oct 2000 01:16:14 +0200 |
| Cc: | netdev@xxxxxxxxxxx, i4ldeveloper@xxxxxxxxxxxxxxxxxxxxxx |
| In-reply-to: | <Pine.LNX.4.10.10010202256400.2056-200000@frog.athome> (liste@hgfelger.de) |
| References: | <Pine.LNX.4.10.10010202256400.2056-200000@frog.athome> |
| Sender: | owner-netdev@xxxxxxxxxxx |
>>>>> "liste" == liste <liste@xxxxxxxxxxx> writes:
liste> reported Warning: kfree_skb passed an skb still on a list
liste> (from <isdn_ppp_push_higher+0x298>).
liste> Maybe, someone knows a bit more, what this message wants to
liste> tell us?
In principal it means that the skb is still queued somewhere when caller
tries to free it. In practice, it frequently indicates that a dangling
skb pointer or a pointer not related to an skb was passed to
kfree_skb(). That's probably what's happening here. The kernel
crash symptoms you describe are also typical for such class of bug.
It also indicates that the bug is probably not inside isdn_ppp, but
somewhere else (in the lower isdn layers, or even somewhere totally
unrelated).
BTW, is your kernel SMP?
Henner
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: ISDN is killing interrupt handler on L2.4.0test9, Henner Eisen |
|---|---|
| Next by Date: | Re: ISDN is killing interrupt handler on L2.4.0test9, Kai Germaschewski |
| Previous by Thread: | Re: ISDN is killing interrupt handler on L2.4.0test9, liste |
| Next by Thread: | Re: ISDN is killing interrupt handler on L2.4.0test9, Kai Germaschewski |
| Indexes: | [Date] [Thread] [Top] [All Lists] |