netdev - Re: [Bugme-new] [Bug 12877] New: tg3: eth0 transit timed out, resetting -> dead NIC

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: <49E3B4A0.8040009@birkenwald.de>
Date:	Mon, 13 Apr 2009 23:54:40 +0200
From:	Bernhard Schmidt <berni@...kenwald.de>
To:	Matt Carlson <mcarlson@...adcom.com>
CC:	Michael Chan <mchan@...adcom.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"bugme-daemon@...zilla.kernel.org" <bugme-daemon@...zilla.kernel.org>
Subject: Re: [Bugme-new] [Bug 12877] New: tg3: eth0 transit timed out,	resetting
 -> dead NIC

Hi Matt,

>>> I'm now switching to eth1.
>> Bernhard, any word on what happened?
> 
> So far so good. In the last week my watchdog (cannot reach the default
> gateway) triggered once, but since there were no "PCI Memory Mapped IO
> Disabled!!!!" messages in the logfile I assume that was a real network
> problem. Since the box ran fine for months initially and the first two
> occurances of this issue were two weeks apart I cannot say for sure, but
> it definitely feels better than the "once in two days" in the end.

No crashes in the last two weeks.

Do you have any further suggestions how to debug this or should we 
accept that portsharing doesn't work very well? This is the second 
problem we can directly attribute to the sharing with the iLO (the first 
one being the "no IPv6 unless the port is in promiscous mode", we had a 
thread about this here on netdev a few months ago).

Bernhard
--
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