From: Vojtech Pavlik <vojtech@suse.cz>
To: Jens Axboe <axboe@suse.de>
Cc: 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 22:24:03 +0200 [thread overview]
Message-ID: <20021019222403.B3018@ucw.cz> (raw)
In-Reply-To: <20021019091518.GG871@suse.de>; from axboe@suse.de on Sat, Oct 19, 2002 at 11:15:18AM +0200
On Sat, Oct 19, 2002 at 11:15:18AM +0200, Jens Axboe wrote:
> On Sat, Oct 19 2002, Jan Dittmer wrote:
> > Box runs nevertheless. Disabled tcq at runtime.
> > Do you need more information? Their seems to be no more fs corruption, as
> > reported earlier.
> > hda: bad special flag: 0x03
> > IDE init is ugly:Call Trace:
> > [<c02722cf>] ide_do_drive_cmd+0x8f/0x180
> > [<c026f4e8>] ide_diag_taskfile+0x88/0xa0
> > [<c026f516>] ide_raw_taskfile+0x16/0x20
> > [<c027dc46>] ide_tcq_configure+0xa6/0xe0
> > [<c027dcc6>] ide_enable_queued+0x46/0xb0
> > [<c027de28>] __ide_dma_queued_on+0x48/0x50
> > [<c026b675>] ide_init_queue+0x75/0x80
> > [<c026b936>] init_irq+0x2b6/0x380
> > [<c026be56>] hwif_init+0x106/0x220
> > [<c026b54c>] probe_hwif_init+0x1c/0x70
> > [<c027bded>] ide_setup_pci_device+0x3d/0x70
> > [<c026a583>] via_init_one+0x33/0x40
> > [<c010508f>] init+0x2f/0x180
> > [<c0105060>] init+0x0/0x180
> > [<c01054f5>] kernel_thread_helper+0x5/0x10
> >
> > hda: tagged command queueing enabled, command queue depth 32
>
> 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.
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2002-10-19 20:24 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 [this message]
2002-10-19 21:04 ` Vojtech Pavlik
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=20021019222403.B3018@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 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).