public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt Domsch <Matt_Domsch@dell.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, alan@redhat.com,
	david.balazic@hermes.si
Subject: Re: [PATCH 2.6.9-rc3-mm2] EDD: use EXTENDED READ command, add CONFIG_EDD_SKIP_MBR
Date: Thu, 7 Oct 2004 00:19:39 -0500	[thread overview]
Message-ID: <20041007051939.GA9075@lists.us.dell.com> (raw)
In-Reply-To: <4164C89A.2040408@pobox.com>

On Thu, Oct 07, 2004 at 12:39:54AM -0400, Jeff Garzik wrote:
> Alas, this does not eliminate the 30-second delay on my box.

OK, thanks for trying.  So it's not the READ SECTORS call itself
that's the problem.
 
> Just to re-emphasize, I feel a particularly relevant detail is that my 
> VIA-based Athlon64 box has _all_ PATA ports disabled.
> 
> I am fairly certainly that the delay did not exist when I enabled at 
> least one PATA port, and I can verify this if you would like.

Yeah, that'd be good to know.  The PATA controller doesn't show up in
your lspci results from 5 July, so I'm sure you had it turned off then too.

BIOS reports having 4 disks in your system.  Does that match
what you would expect?

Your boot disk is on this Promise controller, yes?
00:0d.0 RAID bus controller: Promise Technology, Inc. PDC20378
(SATA150 TX) (rev 02)

The second disk is on a different controller though, with its own EDD
3.0-compliant BIOS.
00:0f.0 RAID bus controller: VIA Technologies,
Inc. VIA VT6420 SATA
        RAID Controller (rev 80)
        Subsystem: Micro-Star International Co., Ltd. MSI Neo K8T
	FIS2R mainboard

Then BIOS says you've got two more disks.
Both disks 82 and 83 look remarkably small (20808 sectors each,
~10MB).  And I would bet there's no media present, as there's no
mbr_signature field given...  So BIOS says there's a disk there, but
there really isn't.  Which could cause the kind of timeout you're
seeing.  To what are these attached?  It's the BIOS for this
controller that's probably what's lying.

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

  reply	other threads:[~2004-10-07  5:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-04 21:48 [PATCH 2.6.9-rc3-mm2] EDD: use EXTENDED READ command, add CONFIG_EDD_SKIP_MBR Matt Domsch
2004-10-07  4:01 ` Jeff Garzik
2004-10-07  4:16   ` Andrew Morton
2004-10-07  4:20     ` Jeff Garzik
2004-10-07  4:25       ` Matt Domsch
2004-10-07  4:22     ` Matt Domsch
2004-10-07  4:34 ` Jeff Garzik
2004-10-07  4:39 ` Jeff Garzik
2004-10-07  5:19   ` Matt Domsch [this message]
2004-10-07  5:32     ` Jeff Garzik
  -- strict thread matches above, loose matches on Subject: below --
2004-10-27 16:53 Matt_Domsch

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=20041007051939.GA9075@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