From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Keith Chew" <keith.chew@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: PCI card initialisation at boot
Date: Sun, 11 Nov 2007 16:46:44 +0000 [thread overview]
Message-ID: <20071111164644.7b2c743c@the-village.bc.nu> (raw)
In-Reply-To: <20f65d530711110722k3d2bf658hb44ceaa036b9962c@mail.gmail.com>
> I am guessing that the ESCD has been corrupted, and putting a spare
> device caused the BIOS to reset the ESCD. In the BIOS, it has been
> setup as "Resource allocation by Auto(ESCD)".
Quite possibily. It may also be that the card had simply developed a bad
connection.
> There is another option in the BIOS to set "Resource allocation by
> Manual". I have tried this setting and Linux has no problems booting
> up and using the PCI card.
>
> My question is: Will setting the BIOS to "Resource allocation by
> Manual" prevent the crash from happening in the future? More
> specifically, does Linux still depend on ESCD even if the resource
> allocation is set to Manual?
Linux by default uses the BIOS resource assignments. It doesn't know
where those came from other than "the BIOS". Also as most vendors
checksum the ESCD I'd be suprised if an ESCD error caused the problem,
but I guess you can get unlucky.
Cards can simply lose connection especially if in a dirty, damp or
particularly in a vibration high environment. In the shipping industry,
for example, it is not uncommon to dismantle all the cards from a PC and
refit them then tighten all the screws as a routine maintenance activity.
Alan
next prev parent reply other threads:[~2007-11-11 16:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-11 15:22 Keith Chew
2007-11-11 16:11 ` Andi Kleen
2007-11-11 16:46 ` Alan Cox [this message]
2007-11-11 23:43 ` Matt Domsch
2007-11-12 0:22 ` H. Peter Anvin
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=20071111164644.7b2c743c@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=keith.chew@gmail.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®