From: Jeff Garzik <jgarzik@pobox.com>
To: Alexander Sbitnev <nwshuras@dezcom.mephi.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SX8 stability issue
Date: Wed, 11 Jan 2006 14:29:49 -0500 [thread overview]
Message-ID: <43C55CAD.90609@pobox.com> (raw)
In-Reply-To: <204883.20060111160652@dezcom.mephi.ru>
Alexander Sbitnev wrote:
> Working with Promise SX8 card for a while we still can't get NCQ
> working stable for both original promise and vanilla kernel drivers.
> We using latest firmware 1.00.0.37 and kernels from 2.6.8 up to 2.6.15.
> Problems occured at least on two different hardware platforms.
> We don't played with max_queue option (or it's header file analog value) yet,
> keeping it on default value.
> Controller work almost stable while NCQ option disabled in BIOS.
> Once feature enabled in BIOS the system become hanging on IO with next
> error messages appearing in the kernel log:
>
> syslog.0:Jan 10 23:30:57 cell kernel: sx8(0000:01:06.0): unhandled event type 16
> syslog.0:Jan 10 23:31:18 cell kernel: sx8(0000:01:06.0): unhandled event type 16
> syslog.0:Jan 10 23:31:40 cell kernel: sx8(0000:01:06.0): unhandled event type 16
> syslog.0:Jan 10 23:32:01 cell kernel: sx8(0000:01:06.0): unhandled event type 16
> syslog.0:Jan 10 23:32:18 cell kernel: end_request: I/O error, dev sx8/0, sector 220064
> syslog.0:Jan 10 23:32:18 cell kernel: Buffer I/O error on device sx8/0, logical block 27508
> syslog.0:Jan 10 23:32:18 cell kernel: lost page write due to I/O error on sx8/0
> syslog.0:Jan 10 23:32:18 cell kernel: Buffer I/O error on device sx8/0, logical block 27509
> syslog.0:Jan 10 23:32:18 cell kernel: lost page write due to I/O error on sx8/0
> syslog.0:Jan 10 23:32:18 cell kernel: Buffer I/O error on device sx8/0, logical block 27510
>
> We don't really sure this problem is a 100% linux related, but it is
> still persist after big hardware upgrade (From dual Pentium III to
> Dual Opteron based system recomended for this controller).
Well, the in-kernel sx8 driver does not use NCQ at all, so you would
have to have modified the driver to turn it on. Presumably this means
there is a bug in your modifications?
> Maybe it is not right way at all to turn NCQ in BIOS? Мауве we must
> just increase max_queue parameter while keeping NCQ in BIOS disabled?
This is the best first step...
Jeff
next prev parent reply other threads:[~2006-01-11 19:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-11 13:06 SX8 stability issue Alexander Sbitnev
2006-01-11 19:29 ` Jeff Garzik [this message]
2006-01-12 11:13 ` Re[2]: " Alexander Sbitnev
2006-01-17 15:01 ` Jeff Garzik
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=43C55CAD.90609@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nwshuras@dezcom.mephi.ru \
/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