9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] oh, no! (again)
Date: Tue, 11 Aug 2009 10:17:57 -0400	[thread overview]
Message-ID: <57b27d94ec43d411388a3b78812ca749@quanstro.net> (raw)
In-Reply-To: <3BBB12CF4EFF4040B38542759379E3CD02791E@XMAIL.asuch.cas.cz>

> sdiahci: drive 0 in state ready after 0 resets   # SATA HD with Plan 9 system on it

that's good.  i hope i've corrected the debug prints.
in this case drive n is sdEn.

> sdiahci: drive 1 won't come up; in state new after 10 resets   # SATA DVD
> sdE1 waitready: [new] task=50 sstat=113
> sdE1 waitready: [new] task=50 sstat=113
> sdE1 waitready: [new] task=50 sstat=113
> sdE1 waitready: [new] task=50 sstat=113
> sdE1 not responding; offline

unfortunately, task=50 and sstat=113 are what we want, but the
old 9load driver just isn't getting the picture.

> sdiahci: drive 2 won't come up; in state portreset after 10 resets
> sdiahci: drive 3 won't come up; in state portreset after 10 resets

this is also bogus.  there's no drive to reset.

> sdiahci: drive 0 in state missing after 0 resets   # strange!
> sdiahci: drive 1 in state missing after 0 resets   # strange!

bug.  probablly a drive power mgmt problem.  was this a seperate boot?

also,
> init: starting /bin/rc
> sdE0: i/o error d0 @206,672

that is Eicrc | Eunc | Eidnf =
	interface crc error,
	uncorrectable read error
	no user-accessable sector.

this is a jmicron bug.  i haven't yet had in my possession a jmicron
controller, so this will be interesting, but the new driver does have
code to work around this very issue.

- erik



  parent reply	other threads:[~2009-08-11 14:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-11 13:28 cej
2009-08-11 13:55 ` erik quanstrom
2009-08-11 14:17 ` erik quanstrom [this message]
2009-08-11 16:12   ` cej
2009-08-11 16:26     ` erik quanstrom
2009-08-11 17:57       ` erik quanstrom
2009-08-11 19:04         ` David Leimbach
2009-08-11 19:25           ` erik quanstrom
2009-08-11 20:51             ` Fernan Bolando
2009-08-11 21:17               ` erik quanstrom
     [not found]               ` <7ed7d1dd2bafb28e91ed462c526409e6@quanstro.net>
2009-08-12 12:12                 ` Fernan Bolando
2009-08-12 12:40                   ` erik quanstrom
     [not found]                   ` <5e44a853596c9d4a4a751c14d0878855@quanstro.net>
2009-08-12 14:06                     ` Fernan Bolando
2009-08-13 14:10         ` Fernan Bolando
2009-08-13 14:33           ` erik quanstrom
     [not found]           ` <855df96e3e51a2f75d1bce104eddda2f@quanstro.net>
2009-08-13 14:49             ` Fernan Bolando
2009-08-13 14:54               ` erik quanstrom

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=57b27d94ec43d411388a3b78812ca749@quanstro.net \
    --to=quanstro@quanstro.net \
    --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).