From: Matt Domsch <Matt_Domsch@dell.com>
To: David Balazic <david.balazic@hermes.si>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, alan@redhat.com,
jgarzik@pobox.com
Subject: Re: [PATCH 2.6.9-rc3-mm2] EDD: use EXTENDED READ command, add CON FIG_EDD_SKIP_MBR
Date: Mon, 18 Oct 2004 08:50:02 -0500 [thread overview]
Message-ID: <20041018135001.GA2721@lists.us.dell.com> (raw)
In-Reply-To: <0C3E356FC19C134F8061D1A69D1F92D90B833F@piramida.hermes.si>
On Mon, Oct 18, 2004 at 08:16:40AM +0200, David Balazic wrote:
> Does not help at all on my system ( Gigabyte GA-7VAXP Ultra , BIOS version
> F7 ).
Crud.
> Only if I select the CONFIG_EDD_SKIP_MBR option, otherwise the
> delay is still there.
Glad that worked. So the problem area is still in reading the first
sector. Jeff's was too, but his BIOS was reporting having disks
present which weren't really there, so the sector read would
eventually time out.
On http://linux.dell.com/dkms/results.html is this simple script
below. This will report whatever is in the /sys/firmware/edd tree.
Also include with this a brief hardware description of your system
(how many disks are actually present, and attached to which
controllers, as you can determine by looking at the cables).
#!/bin/sh
tree /sys
find /sys/firmware/edd -type f -not -name raw_data -print -exec cat
\{\} \;
find /sys/firmware/edd -type f -name raw_data -print -exec hexdump -C
\{\} \;
lspci -vv
lsmod
[ -e /proc/scsi/scsi ] && cat /proc/scsi/scsi
dmidecode
If there's a way to know at runtime if a system has a BIOS that
misrepresents the number of disks present, I'd like to put in such a
quirk. However, this is really really early in system startup, and
I'd prefer not to have to read the DMI tables to do it... Thoughts?
Thanks,
Matt
--
Matt Domsch
Sr. Software Engineer, Lead Engineer
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
parent reply other threads:[~2004-10-18 13:51 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <0C3E356FC19C134F8061D1A69D1F92D90B833F@piramida.hermes.si>]
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=20041018135001.GA2721@lists.us.dell.com \
--to=matt_domsch@dell.com \
--cc=akpm@osdl.org \
--cc=alan@redhat.com \
--cc=david.balazic@hermes.si \
--cc=jgarzik@pobox.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®