netdev - Re: Realtek 8169 problems with net booting

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: <20081124.135710.83221715.davem@davemloft.net>
Date:	Mon, 24 Nov 2008 13:57:10 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	alan@...rguk.ukuu.org.uk
Cc:	netdev@...r.kernel.org
Subject: Re: Realtek 8169 problems with net booting

From: Alan Cox <alan@...rguk.ukuu.org.uk>
Date: Mon, 24 Nov 2008 18:14:56 +0000

> 8169 does this
> 
> 	pci_set_master
> 	twiddle a few bits
> 	soft reset chip
> 
> The master bit is off when the driver is loaded it appears but surely the
> driver should do
> 
> 	twiddle a few bits
> 	soft reset chip
> 	pci_set_master
> 
> otherwise it has no idea if a warm boot from Linux without neat shutdown,
> or a BIOS tftp has left the chip trying to spew into main memory ?

Yes, a lot of drivers will enable bus mastering before resetting
the chip.

The basic assumption is that the chip is quiescent at driver load
time.

Since switching around this order across the board is too
gigantic a project, I would suggest just handling things on
a case-by-case basis where we know the BIOS or firmware leave
the chip in a crud state like this.
--
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