ifconfig eth0 2000 2.1.7 oopses too w. gated

Michael L. Galbraith (mikeg@mikeg.weiden.de)
Mon, 4 Nov 1996 05:21:34 +0100 (MET)


Rapidly skipping over my misunderstanding of the relationship of mtu and
ip fragmentation - I hope. :)
(I made the assumtion that since linux worked, the hardware limitation was
overcome by fragmenting the data somewhere above the mac layer. wisdom++ )

2.1.7 will also oops if you ifconfig eth0 2000. Why someone would do this
isn't as important as that fact that the kernel _can_ be killed by a dodo.

How can I (technician-dodo) troubleshoot this at least to the point that I
can provide enough information for some "real" programmer to fix it?

I don't have any problems with troubleshooting userspace software, but have
no clue as to how to get the kernel into gdb. I have heard that gdb can be
attached to a running process - running kernel?

If some (1) kernel-guru is willing to point me in the right direction, I'm
ready, willing, (to become) able.