From: Matthew Jacob <mjacob@feral.com>
To: Patrick Mansfield <patmans@us.ibm.com>
Cc: Andrew Morton <akpm@digeo.com>, Mark Wong <markw@osdl.org>,
linux-scsi@vger.kernel.org
Subject: Re: 2.5.63-mm2
Date: Wed, 5 Mar 2003 23:38:23 -0800 (PST) [thread overview]
Message-ID: <20030305233253.P20267@mailhost.quaver.net> (raw)
In-Reply-To: <20030305133305.A16075@beaverton.ibm.com>
> Though I still do not know why the feral gets a time out but qlogicisp
> does not. It is apparently a read that times out while mounting root for
> the first time (readonly), so this is not the first read sent to the drive
The command in question that's timing out is "ABOUT FIRMWARE".
If at reset you see the pattern "ISP " in mailbox registers 1, 2, 3
you're supposed to be at the hard PROM- i.e., no firmware has been
loaded and set running by system boot procedures. Unfortunately you get
some platforms where if this is not set this means that the card is
neither in hard reset state (i.e., running out of it's prom) nor
actually running f/w. Hence the timeout on the command.
I've always considered this a relatively minor buglet as it doesn't
occur on *that* many systems but I should probably fix it.
-matt
prev parent reply other threads:[~2003-03-06 7:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030302180959.3c9c437a.akpm@digeo.com>
[not found] ` <1046815078.12931.79.camel@ibm-b>
2003-03-05 7:40 ` 2.5.63-mm2 Andrew Morton
2003-03-05 17:38 ` 2.5.63-mm2 Mike Anderson
2003-03-05 18:52 ` 2.5.63-mm2 Mike Anderson
2003-03-05 21:33 ` 2.5.63-mm2 Patrick Mansfield
2003-03-05 22:01 ` 2.5.63-mm2 Mike Anderson
2003-03-06 7:38 ` Matthew Jacob [this message]
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=20030305233253.P20267@mailhost.quaver.net \
--to=mjacob@feral.com \
--cc=akpm@digeo.com \
--cc=linux-scsi@vger.kernel.org \
--cc=markw@osdl.org \
--cc=mjacob@quaver.net \
--cc=patmans@us.ibm.com \
/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