From: erik quanstrom <quanstro@labs.coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] CD iso image and SATA CDROM on P5Q Pro
Date: Wed, 3 Mar 2010 10:16:11 -0500 [thread overview]
Message-ID: <0d856b51faffcfcea85665df0a5b8187@coraid.com> (raw)
In-Reply-To: <2b9cb0389bf139380b5362028df0a9d7@hera.eonet.ne.jp>
> > should be harmless. are you running maybe
> > an old kernel?
>
> No, I downloaded the live-cd image about a few days ago.
>
> I also see the messages while running fossil only like:
> sdiahci: drive 1 in state ready
> sdiahci: drive 2 won't come up; in state new after 10 resets
> sdE2: wait ready: [new] task=50 sstate=113
the first message is of course from 9load.
>
> This drive 2 is DVD-RAM drive as I wrote yesterday (connected to SATA 3).
> Then, I think kernel thinks the drive 2 must be HDD drive, but it's not.
> How we can teach the kernel it's DVD drive but not HDD.
> Does your recent change can do this?
the first error doesn't really have anything to do with the
type of drive. this is at the sata negotiation level;
this is the hba's phy talking to the drive's phy.
the second error could be either
(a) a driver bug. the sources driver may have trouble
with some bugs in the sb600 that you've got.
(b) a misbehaving drive. if this is the case, the drive
could be unhealthy.
if you don't mind trying the 9atom kernel, it
would be worth investigating if all this is already
fixed. if you already have a working machine, there
both 9load and the kernels are at
ftp://ftp.quanstro.net/other/
if the error persists, there are some tests that are
easier with the new kernels since we can send
arbitrary ata commands.
- erik
next prev parent reply other threads:[~2010-03-03 15:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 11:11 kokamoto
2010-03-02 13:59 ` erik quanstrom
2010-03-02 14:34 ` kokamoto
2010-03-02 14:43 ` erik quanstrom
2010-03-03 10:51 ` kokamoto
2010-03-03 13:21 ` erik quanstrom
2010-03-03 15:00 ` kokamoto
2010-03-03 15:16 ` erik quanstrom [this message]
2010-03-04 11:06 ` kokamoto
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=0d856b51faffcfcea85665df0a5b8187@coraid.com \
--to=quanstro@labs.coraid.com \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).