Date: Tue, 26 Jul 2005 11:13:40 +0900 (JST) From: "UEMURA (fka. MAENAKA) Tetsuya" <maenaka@pluto.dti.ne.jp> To: freebsd-stable@freebsd.org Subject: Re: em(4) stops passing data Message-ID: <20050726021340.5410A2073@towerrecords.minidns.net> In-Reply-To: <4309.192.168.1.190.1122341800.squirrel@webmail.devrandom.org.uk> References: <4309.192.168.1.190.1122341800.squirrel@webmail.devrandom.org.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
I had had apparently same problem in April. For my time, em0 seemed dead, though no link down message was generated, and could go up again by `ifconfig em0 down; ifconfig em0 up'. My problem was caused by defected power supply which generated around 4.5V instead of 5V, and corrected completely by replacing of power supply. FYI, use physical mean when measuring voltage. Reported in BIOS or monitor software may vary from actual. -- UEMURA (fka. MAENAKA) Tetsuya <maenaka@pluto.dti.ne.jp> Posted on Tue, 26 Jul 2005 02:36:40 +0100 (BST) by author Chris Howells <howells@kde.org> > I have a server with an Asus A7V8X-X motherboard and a Intel 1000 Pro MT > Gigabit ethernet card. I have only had the Gigabit card for a few days, > and all seemed to be well to start with -- but today the card has started > to stop passing data after fairly high network load (for instance it > always stops some way through transferring 4 x 500MB files from a Windows > machine to a drive in the machine using samba). > > After it stops passing data it's impossible to ping the machine, or to > ping other machines from the machine. > > However, the strange bit is that a simple 'ifconfig em0 down && ifconfig > em0 up' "fixes" the problem.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050726021340.5410A2073>