From: Michael Brown <mbrown@fensystems.co.uk>
To: David Miller <davem@davemloft.net>
Cc: alan@lxorguk.ukuu.org.uk, netdev@vger.kernel.org
Subject: Re: Realtek 8169 problems with net booting
Date: Thu, 4 Dec 2008 17:22:26 +0000 [thread overview]
Message-ID: <200812041722.26935.mbrown@fensystems.co.uk> (raw)
In-Reply-To: <20081124.135710.83221715.davem@davemloft.net>
On Monday 24 November 2008 21:57:10 David Miller wrote:
> 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.
The assumption that the chip is quiescent is invalid in the case of any kind
of boot from SAN (e.g. iSCSI, AoE) via the net device. The INT13-based
bootloader has no way to signal to the boot firmware that it is finished
using the INT13 interface, so the card will always be left in an active
state.
In gPXE, we do what we can to ensure that the card is safe to use when the OS
loads; we edit the RX buffers, ISR, etc. out of the system memory map prior
to starting an iSCSI boot. We don't, however, get a chance to actually
quiesce the chip before the OS driver loads up, so the OS driver must be
prepared to discover the chip in an active state.
Michael
next prev parent reply other threads:[~2008-12-04 17:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-24 18:14 Realtek 8169 problems with net booting Alan Cox
2008-11-24 21:57 ` David Miller
2008-12-04 17:22 ` Michael Brown [this message]
2008-12-04 18:15 ` David Miller
2008-12-04 20:45 ` Michael Brown
2008-12-04 20:59 ` David Miller
2008-12-04 21:44 ` Alan Cox
2008-12-04 21:55 ` David Miller
2008-11-29 20:44 ` Francois Romieu
2008-11-29 21:06 ` Al Viro
2008-11-29 21:28 ` Francois Romieu
2008-11-29 22:47 ` Al Viro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200812041722.26935.mbrown@fensystems.co.uk \
--to=mbrown@fensystems.co.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.