Posible networking bug in 2.0.35 and bellow :-???

Santiago Garcia Mantinan (manty@geocities.com)
Tue, 21 Jul 1998 10:20:47 +0200 (CEST)


Hi!

kernel: Problem: block on freelist at 030dc808 isn't free.
kernel: kfree of non-kmalloced memory: 001d0388, next= 00000046, order=0
kernel: Aiee, killing interrupt handler
kernel: general protection: 0000
..

Those are some of the errors that I get on 2.0.35 and also on 2.0.34 after
launching pppd on a quite "weird" enviroment, I'm gonna try to describe
the enviroment so you can replicate it and track this down, maybe it is
not a kernel bug but a pppd one :-? but it sounds like kernel to me.

OK, I have two computers A and B, A is a local direct null-modem cable ppp
server and B is the one that gets crashed, both are running Slackware 3.3
and kernels 2.0.34 or 2.0.35 (it happens on both, I haven't gone back to
older ones for trying). B is a Pentium MMX with 64MB of mem, and 120 MB of
swap, no packages of the distribution have been changed to update up to
2.0.35, thus pppd version is 2.2.0f.

Well, the problem only happened to me on this situation, A and B are
conected through an ethernet having the following IPs A:192.168.1.2 and
B:192.168.1.1, I telnet from A to B and do a "su" to launch pppd to test
ppp on A, the routing tables and interfaces on B after the connection are
like this:

lo Link encap:Local Loopback
inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0
UP BROADCAST LOOPBACK RUNNING MTU:3584 Metric:1

eth0 Link encap:Ethernet HWaddr 00:4F:49:03:3C:FA
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

ppp0 Link encap:Point-to-Point Protocol
inet addr:192.168.11.9 P-t-P:192.168.1.2 Mask:255.255.255.0
UP POINTOPOINT RUNNING MTU:296 Metric:1

192.168.1.2 0.0.0.0 255.255.255.255 UH 0 0 1 ppp0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 1 eth0
192.168.11.0 192.168.1.2 255.255.255.0 UG 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 1 lo

Note that the ppp interface on A has the same IP address that its eth0
device, if you change this then the problem doesn't apear.

Well, after some commands on the telnet suid session (maybe killing pppd
and starting it again, but not necesary) the kernel crashes and dumps
messages about memory problems or general protection errors.

If I launch pppd from the console and not from the table the thing goes ok

Well, if any more info needed I'll be pleased to enclose whatever you
want to, I have a syslog full of errors for the lot of times I have
crashed it, I don't include them in here becouse I believe you can
recreate the scenario and get the crash and didn't want to make this
even larger.

That's all for now!

Manty/BestiaTester -> http://www.mantianito.ddns.org

See you in October at the Arroutada Party!
Visit our web http://www.arroutada.ddns.org

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html