Mailing List Archive: PCI card initialisation at boot

PCI card initialisation at boot

Nov 11, 2007, 7:22 AM

Post #1 of 5 (473 views)

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Re: PCI card initialisation at boot [ In reply to ]

andi at firstfloor

Nov 11, 2007, 8:11 AM

Post #2 of 5 (448 views)

Permalink

"Keith Chew" <keith.chew@gmail.com> writes:
>
> 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 does not directly use the ESCD, but it uses configuration coming
from the BIOS (like PCI bridge setup or ACPI resources) that might
depend on the ESCD depending on your BIOS implementation.

You would probably need to ask someone familiar with your BIOS what
the ESCD influences in your configuration and what Manual allocation
changes exactly.

Most likely the real fix would be to add a checksum to it, but
only the BIOS can do that.

-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Re: PCI card initialisation at boot [ In reply to ]

alan at lxorguk

Nov 11, 2007, 8:46 AM

Post #3 of 5 (439 views)

Permalink

> 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Re: PCI card initialisation at boot [ In reply to ]

Matt_Domsch at dell

Nov 11, 2007, 3:43 PM

Post #4 of 5 (437 views)

Permalink

On Sun, Nov 11, 2007 at 04:46:44PM +0000, Alan Cox wrote:
> Linux by default uses the BIOS resource assignments. It doesn't know
> where those came from other than "the BIOS".

Slightly tangential, but I'm starting to hear requests to have the OS
re-assign resources when it might make better sense. For example, if
you have a graphics card with a 1GB memory allocation, the BIOS may
assign it into address ranges below 4GB because it doesn't know
if the OS will be 32-bit or 64-bit capable. But, it would be
beneficial to have it located above 4GB, and to fill in the (new) hole
below 4GB with RAM. Linux right now doesn't have a way to do this.
It will assign resources for cards that the BIOS left unassigned, but
won't intentionally move resources.

--
Matt Domsch
Linux Technology Strategist, Dell Office of the CTO
linux.dell.com & www.dell.com/linux
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Re: PCI card initialisation at boot [ In reply to ]

hpa at zytor

Nov 11, 2007, 4:22 PM

Post #5 of 5 (438 views)

Permalink

Matt Domsch wrote:
> On Sun, Nov 11, 2007 at 04:46:44PM +0000, Alan Cox wrote:
>> Linux by default uses the BIOS resource assignments. It doesn't know
>> where those came from other than "the BIOS".
>
> Slightly tangential, but I'm starting to hear requests to have the OS
> re-assign resources when it might make better sense. For example, if
> you have a graphics card with a 1GB memory allocation, the BIOS may
> assign it into address ranges below 4GB because it doesn't know
> if the OS will be 32-bit or 64-bit capable. But, it would be
> beneficial to have it located above 4GB, and to fill in the (new) hole
> below 4GB with RAM. Linux right now doesn't have a way to do this.
> It will assign resources for cards that the BIOS left unassigned, but
> won't intentionally move resources.
>

Not really. If the OS is 64-bit capable, it can just use the RAM above
4 GB.

-hpa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/