yes, it is still the same that both modules get loaded at boot time.
Why should there be any change since there has been no change in the
code concerning 8139 for several versions. And the problem with dropped
packages is __NOT__ fixed with removing one of the modules. I am sorry
that I didn't report that behavior earlier, but the strange thing is
that for a while it worked and after a certain amount(can not specify
the exact number) of received packages, the package dropping started
again.
I filed an other bug report 486793 which is strongly related to this one
(we emailed about it in November). So I think this two bugs should be
merged or 475575 can be downgraded - as far as I can tell there is no
lasting change in behavior when removing 8139cp so it is just
unexpected/wrong that both modules get loaded. The actual serious bug
(full duplex is not available and so many packages get dropped that
networking with this hardware is useless) is described in 486793.
cheers,
Sebastian
Moritz Muehlenhoff wrote:
On Fri, Apr 11, 2008 at 08:41:59PM +0200, Sebastian Schleehauf wrote:
Package: linux-image-2.6
Severity: important
--- Please enter the report below this line. ---
Hi,
at boot time 8139too and 8139cp get loaded. This causes many package
collisions and drops resulting in a horribly slow connection, even tough
it should be about 100Mbit. By removing the 8139cp module things start
to work proper ( no more new collisions according to /proc/net/dev). For
now I blacklisted the module but this seems to be a problem for lots of
people (according to google). I am filing this bug against
linux-image-2.6 since this applies to lots of kernels ( I am not even
sure if this bug should be against the kernel or udev).
Does this error still occur with more recent kernel versions?
Cheers,
Moritz
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
