D-Link DFE-580TX 4 port NIC problems
Mario Doering
we have a D-Link DFE-580TX 4 port network card in our main router.
It works pretty well most of the time, even though an error
message pops up in dmesg every now and then (sometimes once a day
sometimes once every few hours).
But every few weeks those error messages increase rapidly, spamming
dmesg. When this happens the system does not react anymore and pushing
the reset button is the only option left.
I googled around and found out that other users have same problem,
but no solution to this.
Part of the message log is located here:
http://test.dedenet.de/messages.gz
or
http://test.dedenet.de/messages.txt
uname -a
Linux router1 2.6.19-gentoo-r5 #1 Sat Feb 17 17:04:03 CET 2007 i686 AMD
Athlon(tm) XP AuthenticAMD GNU/Linux
driver:
[ 17.364707] sundance.c:v1.2 11-Sep-2006 Written by Donald Becker
[ 17.364711] http://www.scyld.com/network/sundance.html
[ 17.364844] ACPI: PCI Interrupt 0000:03:04.0[A] -> GSI 17 (level,
low) -> IRQ 17 [ 17.365396] eth1: D-Link DFE-580TX 4 port Server
Adapter at 0001bc00, 00:0d:88:cc:a5:f0, IRQ 17. [ 17.366350] eth1:
MII PHY found at address 1, status 0x7829 advertising 01e1.
[ 17.676491] ACPI: PCI Interrupt 0000:03:05.0[A] -> GSI 18 (level,
low) -> IRQ 18 [ 17.676912] eth2: D-Link DFE-580TX 4 port Server
Adapter at 0001b800, 00:0d:88:cc:a5:f1, IRQ 18. [ 17.677864] eth2:
MII PHY found at address 1, status 0x7809 advertising 01e1.
[ 17.987730] ACPI: PCI Interrupt 0000:03:06.0[A] -> GSI 19 (level,
low) -> IRQ 16 [ 17.988107] eth3: D-Link DFE-580TX 4 port Server
Adapter at 0001b400, 00:0d:88:cc:a5:f2, IRQ 16. [ 17.989059] eth3:
MII PHY found at address 1, status 0x7829 advertising 01e1.
[ 18.298910] ACPI: PCI Interrupt 0000:03:07.0[A] -> GSI 16 (level,
low) -> IRQ 19 [ 18.299320] eth4: D-Link DFE-580TX 4 port Server
Adapter at 0001b000, 00:0d:88:cc:a5:f3, IRQ 19. [ 18.300272] eth4:
MII PHY found at address 1, status 0x7809 advertising 01e1.
No such error message appears for about 7-10 days after a reboot. Maybe
there is some kind of buffer running full?
Do you need any additional info?
Please CC me :-)
Regards,
Mario.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majo...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Andrew Morton
(cc netdev)
Mario Doering
are there any news or questions on this issue?
Mario.
Clemens Koller
Mario Doering schrieb:
> Hello,
>
> are there any news or questions on this issue?
Can you try the latest kernel to see if the same problem
persists?
Is there any kernel version where it was working fine?
Regards,
--
Clemens Koller
__________________________________
R&D Imaging Devices
Anagramm GmbH
Rupert-Mayer-Straße 45/1
Linhof Werksgelände
D-81379 München
Tel.089-741518-50
Fax 089-741518-19
http://www.anagramm-technology.com
adi
> Can you try the latest kernel to see if the same problem
> persists?
> Is there any kernel version where it was working fine?
In my case, this is 'problem' occur when I do run snmpd on
the same machine, and I saw that snmpd doing something
like this:
...
} else if (ioctl(fd, SIOCDEVPRIVATE, &ifr) >= 0) {
new_ioctl_nums = 1;
}
....
That cause sundance printing a lot of debug messages (i.e netdev_ioctl()
in sundance.c) .. periodically, as long as snmpd running :-)
Regards,
P.Y. Adi Prasaja
Mario Doering
Clemens Koller <clemens...@anagramm.de> wrote:
> Hi, Mario!
>
> Mario Doering schrieb:
> > Hello,
> >
> > are there any news or questions on this issue?
>
> Can you try the latest kernel to see if the same problem
> persists?
> Is there any kernel version where it was working fine?
Hello Clemens,
I have tried different kernerls with no success so far. I have not
tried a 2.6.22 kernel yet, but I can do so of course.
It would take some time then again to wait for the error to arise ;-)
Bye,
Mario.