I suggest trying 2.4.19-pre8 first. This has the fix for the deadlock that I'm
aware of in it. If that still doesn't work, then try and send me as much
information as the system will let you extract. What I'm most interested
o State of the sockets (netstat -t on both client and server)
o Values of /proc/sys/net/ipv4/tcp_[rw]mem and tcp_mem
o Does the nbd client get stuck in the D state before or after any other
processes doing I/O through nbd? This is useful as it tells me whether
the problem is on a transmit or receive.
o Was your system low on memory at the time ?
o Were you trying to use nbd as a swap device ?
> I am using 2.4.16 with xfs patch from SGI. It may not be the acenic
> driver problem, I can reproduce the deadlock in a 100 base-T network
> using eepro100 driver. Closing the server did not release the deadlock.
> What else can I try?
[original messages cut here]
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue May 07 2002 - 22:00:28 EST