All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.8 IDE oops (TCQ breakage?)
Date: Tue, 16 Apr 2002 20:07:50 +0200	[thread overview]
Message-ID: <20020416180750.GQ1097@suse.de> (raw)
In-Reply-To: <200204161749.TAA16333@harpo.it.uu.se>

On Tue, Apr 16 2002, Mikael Pettersson wrote:
> I have a 486 box which ran 2.5.7 fine, but 2.5.8 oopses during
> boot at the BUG_ON() in drivers/ide/ide-disk.c, line 360:
> 
> 	if (drive->using_tcq) {
> 		int tag = ide_get_tag(drive);
> 
> 		BUG_ON(drive->tcq->active_tag != -1);
> 
> Relevant .config is
> # CONFIG_PCI is not set
> CONFIG_IDE=y
> CONFIG_BLK_DEV_IDE=y
> CONFIG_BLK_DEV_IDEDISK=y
> CONFIG_IDEDISK_MULTI_MODE=y
> (That's it. No chipset support selected; neither I nor Linux
> has ever detected any known IDE chipset in this box...)
> 
> Why is drive->using_tcq non-zero when CONFIG_BLK_DEV_IDE_TCQ=n
> and the disk is an early/mid-90s 500MB WD drive?

No ata pci adapter selected, probably. Apply 2.5.8-dj1, it should have
the most interesting parts for you. I'll update my stuff tomorrow.

-- 
Jens Axboe


  reply	other threads:[~2002-04-16 18:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-16 17:49 2.5.8 IDE oops (TCQ breakage?) Mikael Pettersson
2002-04-16 18:07 ` Jens Axboe [this message]
2002-04-17  9:51 ` Martin Dalecki
2002-04-17 12:08   ` Jens Axboe
2002-04-17 12:25     ` Jens Axboe
2002-04-17 11:33       ` Martin Dalecki
2002-04-17 12:42         ` Jens Axboe
2002-04-17 14:16         ` Erik Andersen
2002-04-17 13:28           ` Martin Dalecki
  -- strict thread matches above, loose matches on Subject: below --
2002-04-17 20:02 Mikael Pettersson

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=20020416180750.GQ1097@suse.de \
    --to=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@csd.uu.se \
    /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.