From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jens Axboe Subject: Re: Oops on boot with TCQ enabled (VIA KT133A) Date: Sat, 19 Oct 2002 11:15:18 +0200 Sender: linux-kernel-owner@vger.kernel.org Message-ID: <20021019091518.GG871@suse.de> References: <200210190241.49618.jan@jandittmer.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <200210190241.49618.jan@jandittmer.de> To: Jan Dittmer Cc: Linux Kernel List , linux-ide@vger.kernel.org List-Id: linux-ide@vger.kernel.org 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. > > jan > > > Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 > ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx > VP_IDE: IDE controller at PCI slot 00:07.1 > VP_IDE: chipset revision 6 > VP_IDE: not 100% native mode: will probe irqs later > ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx > VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci00:07.1 > ide0: BM-DMA at 0x9000-0x9007, BIOS settings: hda:DMA, hdb:pio > ide1: BM-DMA at 0x9008-0x900f, BIOS settings: hdc:DMA, hdd:DMA > hda: IC35L060AVVA07-0, ATA DISK drive > hda: DMA disabled > IDE init is ugly:Call Trace: > [] ide_do_drive_cmd+0x8f/0x180 > [] ide_diag_taskfile+0x88/0xa0 > [] ide_raw_taskfile+0x16/0x20 > [] ide_tcq_configure+0x77/0xe0 > [] ide_enable_queued+0x46/0xb0 > [] __ide_dma_queued_on+0x48/0x50 > [] ide_init_queue+0x75/0x80 > [] init_irq+0x2b6/0x380 > [] hwif_init+0x106/0x220 > [] probe_hwif_init+0x1c/0x70 > [] ide_setup_pci_device+0x3d/0x70 > [] via_init_one+0x33/0x40 > [] init+0x2f/0x180 > [] init+0x0/0x180 > [] kernel_thread_helper+0x5/0x10 > > hda: bad special flag: 0x03 > IDE init is ugly:Call Trace: > [] ide_do_drive_cmd+0x8f/0x180 > [] ide_diag_taskfile+0x88/0xa0 > [] ide_raw_taskfile+0x16/0x20 > [] ide_tcq_configure+0xa6/0xe0 > [] ide_enable_queued+0x46/0xb0 > [] __ide_dma_queued_on+0x48/0x50 > [] ide_init_queue+0x75/0x80 > [] init_irq+0x2b6/0x380 > [] hwif_init+0x106/0x220 > [] probe_hwif_init+0x1c/0x70 > [] ide_setup_pci_device+0x3d/0x70 > [] via_init_one+0x33/0x40 > [] init+0x2f/0x180 > [] init+0x0/0x180 > [] 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? -- Jens Axboe