From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] sick cpu server; 9load hates my SATA controller
Date: Fri, 23 Jan 2009 18:26:04 -0500 [thread overview]
Message-ID: <43c569b2afe10e24fd9aa96244f229af@quanstro.net> (raw)
In-Reply-To: <509071940901231508y6569a875s99008e8c3bb6b74@mail.gmail.com>
i have been using a sb600-based machine for a couple of years as a
terminal, so i think that your bios configuration might have a lot to
do with your problems. it is probablly tickling bugs in the driver.
would you be able and willing to try booting the 9load at
/n/sources/contrib/quanstro/src/9loadaoe
and try the updated kernel driver at
/n/sources/contrib/quanstro/src/9/pc/*ahci*
?
> About a month ago, the motherboard in my CPU server went bad (visibly
> bulging capacitors!). I finally got the replacement part on RMA from
> the manufacturer and tried getting things going again yesterday. No
> joy, and the problems are strange. The symptoms differ depending on
> whether I have drives on sdE[0,1,3] (as was the case before) or
> sdE[0,1,2].
that's definately a clue. your bios configuration should
be for no raid, all ahci all the time.
> sb600: sata-II with 4 ports
> sdiahci: drive 0 in state ready after 0 resets
> sdiahci: drive 1 in state ready after 0 resets
> sdiahci: drive 2 in state missing after 0 resets
> sdiahci: drive 3 in state ready after 0 resets
> sdE3: i/o error 50 @0
> sdE3: i/o error 50 @1
>
> but (as best I can tell) after "state missing" line all I/O becomes
> dog slow. Characters print at what looks like maybe 300 baud, newlines
> take a few seconds to redraw the screen.
likely howling interrupts due to the i/o error. with ahci,
this has often been a power management issue.
> If I have drives on sdE[0,1,2], the case for the CD is the same, but
> the on-disk kernel gets through asking where root is from, and then
> yields "panic: fault: 0x11c" as it probes the drives. All the on-disk
> kernels perform the same way.
sometimes this is caused by sdata getting spurious interrupts.
if you continue to have trouble, i would be more than
happy to debug this problem offline. just let me know
how it goes.
- erik
prev parent reply other threads:[~2009-01-23 23:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 23:08 Anthony Sorace
2009-01-23 23:26 ` erik quanstrom [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=43c569b2afe10e24fd9aa96244f229af@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).