[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ATA] and re(4) stability issues
- To: Pyun YongHyeon <pyunyh_(_at_)_gmail_(_dot_)_com>
- Subject: Re: [ATA] and re(4) stability issues
- From: Victor Balada Diaz <victor_(_at_)_bsdes_(_dot_)_net>
- Date: Thu, 11 Dec 2008 08:57:07 +0100
- Cc: freebsd-stable_(_at_)_freebsd_(_dot_)_org, freebsd-amd64_(_at_)_freebsd_(_dot_)_org
On Wed, Dec 10, 2008 at 09:07:19PM +0900, Pyun YongHyeon wrote:
> On Wed, Dec 10, 2008 at 12:32:25PM +0100, Victor Balada Diaz wrote:
> > Also i didn't see any problem with interfaces going up and down,
> > but that usually happen after some hours of uptime, so i'll let
> > you know if the error happens again.
After writing to the HD with dd for a few hours and using
stress -i 10 -d 10 the machine lost connectivity. I waited until
today to be sure if the machine hung, paniced or just lost network
connectivity. I don't have local access or serial access, so this
is the only way i could do it. I've seen in the logs during the
night various messages of:
Dec 10 00:33:49 yac kernel: re0: watchdog timeout
Dec 10 00:33:49 yac kernel: re0: link state changed to DOWN
Dec 10 00:33:52 yac kernel: re0: link state changed to UP
The interface never recovered and i wasn't able to ping the machine
until i rebooted. Nagios was checking all the time and no recovery
The netstat -i in daily scripts shows just one Oerrs. I'm used to
have a lot of them, but seems this time the card didn't recover from
the only one. I also want to say that this is not a regression, as
it happened before with 7.1 -BETA 2 code.
Is there anything more i can try?
La prueba más fehaciente de que existe vida inteligente en otros
planetas, es que no han intentado contactar con nosotros.
freebsd-amd64_(_at_)_freebsd_(_dot_)_org mailing list
To unsubscribe, send any mail to "freebsd-amd64-unsubscribe_(_at_)_freebsd_(_dot_)_org"
Visit your host, monkey.org