From: "Keith Chew" <keith.chew@gmail.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: PCI card initialisation at boot
Date: Mon, 12 Nov 2007 04:22:15 +1300 [thread overview]
Message-ID: <20f65d530711110722k3d2bf658hb44ceaa036b9962c@mail.gmail.com> (raw)
Hi
I am looking for someone to help explain my findings, which I have
searched the net but could not find any related infomation.
We have 40 linux PCs deployed in a mobile environment, so they are
subjected to pretty harsh conditions that can cause BIOS corruptions.
In one of the units, I noticed the kernel had difficulty initialising
the PCI card, with messages stating that the PCI resource/address is
invalid (I am very sorry that I did not manage to capture the exact
output). It continues to boot to userspace, but the machine hangs when
the user app tries to access the pci card.
Rebooting the PC several times gave the same message, so at least the
problem was consistent. Removing the PCI card from the slot, and
putting a spare card, solved the problem. Then, putting the first card
back worked again.
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)".
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?
Regards
Keith
next reply other threads:[~2007-11-11 15:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-11 15:22 Keith Chew [this message]
2007-11-11 16:11 ` Andi Kleen
2007-11-11 16:46 ` Alan Cox
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=20f65d530711110722k3d2bf658hb44ceaa036b9962c@mail.gmail.com \
--to=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®