-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I now test with test10pre4
Salut Henner,
I had a quick look into the source. As it always crashed in kfree_skb,
I changed some lines in net/core/skbuff.c (see attached patch). But this
is not a cure - it only does not crash, at least not immediatly.
The section, I changed should report a bug - this reporting did crash the
machine. But it would be a cure, if we could fix this bug, that wants to
get reported
Warning: kfree_skb passed an skb still on a list (from
<isdn_ppp_push_higher+0x298>).
Maybe, someone knows a bit more, what this message wants to tell us?
I tryed to connect with -lzs option, and a second time with noccp -lzs.
The second try did not report the warning, as expected. A ping to the peer
did bothtimes succeed.
Regards hartwig :-)
- --
1024D/339FD693 Hartwig Felger <hgfelger@xxxxxxxxxxx>
Key fingerprint = FB2F 3EE9 345A D55B 6FF2 0EC1 F5B0 684F 339F D693
For the pulic keys, please visit my page.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.0 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE58LWB9bBoTzOf1pMRAp1dAJ95td51p4SKzy33GgzbQn8C8jLLZgCgmIu9
Z8oVr92h6xHXh4XXa243cB4=
=yLfc
-----END PGP SIGNATURE-----
skbuff.c.diff
Description: Text document
|