Axel> Stepen Drew wrote,
>> Hi All,
>> I compiled the 3com 509 driver as a module (kernel 1.99.8) and I get
>> the double lock on device queue message followed by the flood of socket
>> destroyed delayed messages whereas Axel doesn't (the machine is an old
>> 386, 4Mb Ram which I use as a printer server) Very Strange! :)
Axel> that's wrong. I got them, _WHEN_ I used the 3c509 driver as module.
Axel> now the 3c509 driver is directly compiled into the kernel and the
Axel> double lock on device queue message wasn't seen anymore.
Axel> i'll take this as a hint and build/use a kernel WITHOUT ANY
Axel> modules support. perhaps the problem isn't in the networking at
Axel> all :-(. this is _really_ strange :-)
I am getting the ``double lock on device queue'' on a kernel without
any module support whatsoever -- most recently was 16-May (1.99.4).
What I don't understand about the ``socket destroy delayed'' spew is
why I'm only getting one stuck socket. It doesn't take more than an
hour or two of uptime to start, so it would seem logical that more
sockets would get stuck as well, but they don't.
-- steve@miranova.com baur Unsolicited commercial e-mail will be proofread for $250/hour. Andrea Seastrand: For your vote on the Telecom bill, I will vote for anyone except you in November.