All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Jens Axboe <axboe@suse.de>, Jan Dittmer <jan@jandittmer.de>,
	Linux Kernel List <linux-kernel@vger.kernel.org>,
	linux-ide@vger.kernel.org
Subject: Re: Oops on boot with TCQ enabled (VIA KT133A)
Date: Sat, 19 Oct 2002 23:04:34 +0200	[thread overview]
Message-ID: <20021019230434.A800@ucw.cz> (raw)
In-Reply-To: <20021019222403.B3018@ucw.cz>; from vojtech@suse.cz on Sat, Oct 19, 2002 at 10:24:03PM +0200

On Sat, Oct 19, 2002 at 10:24:03PM +0200, Vojtech Pavlik wrote:

> > It's not an oops, and it's not causes by TCQ either. The above is simply
> > a reminder to fix the ide init sequence, because it's probe sequence
> > tries to use drive->disk before it has been set up. That is worked
> > around, but stack is dumped for good measure. So you can feel
> > comfortable using 2.5.44 regardless.
> > 
> > But I'm curious about TCQ on your system, since another VIA user
> > reported problems. Does it appear to work for you?
> 
> It definitely works on my VIA just fine.

Famous last words. I tried to play with the /proc using_tcq setting and
got a filesystem corruption immediately.

-- 
Vojtech Pavlik
SuSE Labs

  reply	other threads:[~2002-10-19 21:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-19  0:41 Oops on boot with TCQ enabled (VIA KT133A) Jan Dittmer
2002-10-19  9:15 ` Jens Axboe
2002-10-19  9:24   ` Jan Dittmer
2002-10-19  9:24     ` Jens Axboe
2002-10-19 15:39       ` Jan Dittmer
2002-10-19 20:24   ` Vojtech Pavlik
2002-10-19 21:04     ` Vojtech Pavlik [this message]
2002-10-20  0:38       ` Jens Axboe
2002-10-20  8:46         ` Vojtech Pavlik
2002-10-20  9:38           ` Jens Axboe
2002-10-20 14:57             ` Jan Dittmer
2002-10-22 20:16             ` Jan Dittmer
2002-10-23 16:02             ` Jan Dittmer

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=20021019230434.A800@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=axboe@suse.de \
    --cc=jan@jandittmer.de \
    --cc=linux-ide@vger.kernel.org \
    --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.