From: David Ford <david+hb@blue-labs.org>
To: Ivan Gyurdiev <ivg2@cornell.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: TCQ problems in 2.6.0-test1: the summary
Date: Tue, 22 Jul 2003 07:36:03 -0400 [thread overview]
Message-ID: <3F1D21A3.30504@blue-labs.org> (raw)
In-Reply-To: <3F1C1079.7060103@cornell.edu>
Ivan Gyurdiev wrote:
> > Note, reiserfsck never indicates any problems were found or fixed
> but the problems are none-the-less fixed. (reiser guys: reiserfsck
> --fix-fixable always results in "--fix-fixable ignored")
>
> I think it does that when the root fs is mounted - not sure.
> You should fsck from a different root.
Right, let me just add a harddrive to my notebook ;)
> Jul 19 10:55:31 james hdc: invalidating tag queue (0 commands)
>
>> Jul 19 10:55:41 james ide_tcq_intr_timeout: timeout waiting for
>> completion interrupt
>
>
> Yes - that's in my original email.
>
>> and further disk access causes D state. I upgraded this machine to
>> 2.6.0-test1 and now it's having fits with apic or acpi but that's
>> another email. And a side note, if I have TCQ compiled in w/
>> 2.6.0-test1, the kernel barfs a long 40+ function OOPS on bootup.
>
>
> Jens's patch in my email should fix that.
> However, TCQ seems rather broken to me right now (or maybe it's just my
> machine) - so I'd be careful with it.
noted.
I'm waiting for the next batch of updates, 2.6.0-test1 seems to be quite
broken in several places for several of my machines. :/
david
prev parent reply other threads:[~2003-07-22 11:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-19 22:37 TCQ problems in 2.6.0-test1: the summary Ivan Gyurdiev
2003-07-21 12:33 ` Jens Axboe
2003-07-21 15:58 ` Ivan Gyurdiev
2003-07-21 16:21 ` David Ford
2003-07-21 16:10 ` Ivan Gyurdiev
2003-07-22 11:36 ` David Ford [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=3F1D21A3.30504@blue-labs.org \
--to=david+hb@blue-labs.org \
--cc=ivg2@cornell.edu \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.