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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/