linux-kernel - Re: Natsemi DP83815 driver spaming

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]

Date:	Tue, 1 May 2007 22:27:51 +0100
From:	Mark Brown <broonie@...ena.org.uk>
To:	Rafał Bilski <rafalbilski@...eria.pl>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: Natsemi DP83815 driver spaming

On Tue, May 01, 2007 at 09:52:30PM +0200, Rafał Bilski wrote:

> >  * 2) check for sudden death of the NIC:
> >  *    It seems that a reference set for this chip went out with incorrect info,
> >  *    and there exist boards that aren't quite right.  An unexpected voltage
> >  *    drop can cause the PHY to get itself in a weird state (basically reset).
> >  *    NOTE: this only seems to affect revC chips.

> Code commented out and NIC is working OK. Strange.
> eth0: DSPCFG accepted after 0 usec.
> eth0: link up.
> eth0: Setting full-duplex based on negotiated link capability.
> dspcfg = 0x00000000  np->dspcfg = 0x00005060

Oh, that's entertaining.  I have to confess that I've never seen an that
triggered the workaround before - adding the maintainer, Tim Hockin, who
may be able to shed some light on the expected behaviour here?

-- 
"You grabbed my hand and we fell into it, like a daydream - or a fever."

Download attachment "signature.asc" of type "application/pgp-signature" (308 bytes)