Hi,
I have the following problem since 2.4.17 on my laptop with a PC-Card
network card. When something is sent over the network the kernel prints
"kernel: svc: bad direction 65537, dropping request"
into the syslog and the network stops working. It does start to work again
after some time. This happenes without any scheme, but frequently when trying
to access NFS mounts.
Dec 22 16:23:18 sneaky kernel: nfs: server spot not responding, still trying
Dec 22 16:23:44 sneaky kernel: svc: bad direction 65537, dropping request
Dec 22 16:23:47 sneaky kernel: nfs: server spot OK
Dec 22 16:23:49 sneaky kernel: svc: bad direction 65537, dropping request
Dec 22 16:23:58 sneaky last message repeated 3 times
What is this message about and what triggers it? I found some
occurences of this in the lkml archive. Like
http://lists.kernelnotes.de/linux-kernel/Week-of-Mon-20011008/044888.html but
this does not apply to this.
I became aware of this problem with 2.4.17, however there is also a
syslog entry with the very same message when the system was running 2.4.16.
But with .17 I get the error quite frequently and the network stops working.
The network card running in the system (if the driver might be the
problem) is identified as
Dec 22 16:21:52 sneaky kernel: tulip.c:v0.91g-ppc 7/16/99 [email protected] (modi
fied by [email protected] for XIRCOM CBE, fixed by Doug Ledford)
Dec 22 16:21:52 sneaky kernel: eth0: ADMtek Centaur-C rev 17 at 0x200,
00:E0:98:96:88:DC, IRQ 11.
by the kernel. I'm running with pcmcia-cs 3.1.30 that loads the
following modules:
Module Size Used by
nfs 69008 1 (autoclean)
lockd 45904 1 (autoclean) [nfs]
sunrpc 58208 1 (autoclean) [nfs lockd]
tulip_cb 31872 2
cb_enabler 2528 2 [tulip_cb]
ds 6672 1 [cb_enabler]
i82365 22256 1
pcmcia_core 41440 0 [cb_enabler ds i82365]
nls_iso8859-1 2880 1 (autoclean)
nls_cp437 4384 1 (autoclean)
vfat 9264 1 (autoclean)
fat 29120 0 (autoclean) [vfat]
I would be glad for any hints. If you need more details about the
system I'll provide it. Um... help? :)
Bye
Oliver
--
Oliver Feiler [email protected]
http://www.lionking.org/~kiza/pgpkey PGP key ID: 0x561D4FD2
http://www.lionking.org/~kiza/
Never mind. There was an IP address collision on the network I didn't notice
that caused the problem (I think). Looks like everything works again. I feel
stupid now.
Oliver
--
Oliver Feiler [email protected]
http://www.lionking.org/~kiza/pgpkey PGP key ID: 0x561D4FD2
http://www.lionking.org/~kiza/