This problem has been resolved (sort of). See the follow up to
"[PATCH] to deal with bad dev->refcnt in unregister_netdevice()"
Thomas Hood
> Here is a patch which may not solve the underlying
> problem but which does prevent the kernel from
> generating an infinite number of error messages
This problem has been resolved (sort of). See the follow up to
"[PATCH] to deal with bad dev-refcnt in unregister_netdevice()"
Thomas Hood
Here is a patch which may not solve the underlying
problem but which does prevent the kernel from
generating an infinite number of error messages
on
Here is a patch which may not solve the underlying
problem but which does prevent the kernel from
generating an infinite number of error messages
on "cardctl eject" and from hanging up on shutdown.
Here is a patch which may not solve the underlying
problem but which does prevent the kernel from
generating an infinite number of error messages
on "cardctl eject" and from hanging up on shutdown.
I have a bit more information about this bug now.
The message "assertion(yadda) failed ..." occurs only
if the eth0 interface has been configured using pump
or dhclient. If the card isn't connected to the network
the message never occurs. If eth0 is merely brought up
and down using ifconfig the
Dear l-k.
I'm still having this problem with kernel 2.4.0:
Conditions:
Linux 2.4.0 compiled on an IBM ThinkPad 600 51U (Pentium II)
laptop with PCMCIA support. Same behavior with integral kernel
PCMCIA, modular kernel PCMCIA and modular Hinds PCMCIA. System
is Progeny Debian beta II.
I have
Dear l-k.
I'm still having this problem with kernel 2.4.0:
Conditions:
Linux 2.4.0 compiled on an IBM ThinkPad 600 51U (Pentium II)
laptop with PCMCIA support. Same behavior with integral kernel
PCMCIA, modular kernel PCMCIA and modular Hinds PCMCIA. System
is Progeny Debian beta II.
I have
7 matches
Mail list logo
