netdev - Re: oops/warning report for the week of November 26, 2008

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: <20081130085820.GA13944@core.hellgate.ch>
Date:	Sun, 30 Nov 2008 09:58:20 +0100
From:	Roger Luethi <rl@...lgate.ch>
To:	Francois Romieu <romieu@...zoreil.com>
Cc:	Arjan van de Ven <arjan@...ux.intel.com>,
	Jay Cliburn <jcliburn@...il.com>,
	NetDev <netdev@...r.kernel.org>
Subject: Re: oops/warning report for the week of November 26, 2008

On Fri, 28 Nov 2008 20:50:18 +0100, Francois Romieu wrote:
> Arjan van de Ven <arjan@...ux.intel.com> :
> [...]
> > For me, sis900 and r8169 stand out; if you look at the data in the
> > table above, both of these are an order of magnitude more frequent than
> > the rest of the pack.
> 
> via-rhine + via_rhine = 438: it does not look too good either.

Agreed. I was kinda hoping I'd get some clues for free when other drivers
get fixed :-).

> Is there an (ideally automated) way to retrieve more information ?
> 
> The r8169 driver handles three different chipsets and a plethora of
> phys. The "XID" line printed by the driver could hint at some specific
> PHY for instance.

For the Rhine, knowing the PCI rev would help identify problems tied to
specific models.

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