Messages in this thread |  | | From | Sven Heinicke <> | Date | Thu, 29 Nov 2001 11:14:14 -0500 (EST) | Subject | Re: 2.4.16 freezed up with eepro100 module |
| |
Nathan Poznick writes: > Thus spake Sven Heinicke: > > > > The 2.4.16 kernel finally makes my clients happy with memory > > management. The systems that froz up is a Dell of some sort or other > > with two 1Ghz Pentium IIIs and 4G of memory. But, now I seems to be > > having ethernet problems. With and eepro100 card: > > I've encountered the same problem, with the same hardware setup (I > believe it's a Dell 2400, or something like that), on 2.4.14+xfs. For > me it didn't lock up the entire machine however, it only seemed to > kill the network - I was able to reboot the machine cleanly once I got > to the console. (message from yesterday with the subject 'failed > assertion in tcp.c') I too, am open to suggestions :-) >
I suspect that I would of been able to reboot it if I was at work in the middle of the night. I am unable to try older kernels as until 2.4.16 I had memory issues. The process that was doing so much eth0 is ran for like 3 days before the freeze.
Sven - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |