netdev - Re: D-Link DFE-580TX 4 port NIC problems

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070727113044.76630826@snibbles.dedenet.de>
Date:	Fri, 27 Jul 2007 11:30:44 +0200
From:	Mario Doering <mario@...enet.de>
To:	linux-kernel@...r.kernel.org
Cc:	netdev@...r.kernel.org
Subject: Re: D-Link DFE-580TX 4 port NIC problems

Hello,

are there any news or questions on this issue?


Mario.



On Wed, 9 May 2007 03:27:00 -0700
Andrew Morton <akpm@...ux-foundation.org> wrote:

> On Wed, 9 May 2007 12:01:42 +0200 Mario Doering <mario@...enet.de>
> wrote:
> 
> > Hello,
> > 
> > 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 :-)
> 
> (cc netdev)
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html