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] [day] [month] [year] [list]

Message-ID: <20090414182922.GB12475@xw6200.broadcom.net>
Date:	Tue, 14 Apr 2009 11:29:22 -0700
From:	"Matt Carlson" <mcarlson@...adcom.com>
To:	"Bernhard Schmidt" <berni@...kenwald.de>
cc:	"Matthew Carlson" <mcarlson@...adcom.com>,
	"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

On Mon, Apr 13, 2009 at 02:54:40PM -0700, Bernhard Schmidt wrote:
> 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).

No, I think we need to get this to work with portsharing.  We just need
to figure out what it is about it that causes these types of errors.

I talked to the firmware maintainer here.  We have a couple ideas that
might uncover what is happening.  Our next step is to develop a set of
tests that will show under what assumptions the firmware is operating.
Once we have that, I'll ask you to patch your driver so that we can see
what is happening from your end.

Stay tuned.

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