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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sun, 11 Nov 2007 16:46:44 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	"Keith Chew" <keith.chew@...il.com>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: PCI card initialisation at boot

> 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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ