From: Martin Dalecki <dalecki@evision-ventures.com>
To: Jens Axboe <axboe@suse.de>
Cc: Mikael Pettersson <mikpe@csd.uu.se>, linux-kernel@vger.kernel.org
Subject: Re: 2.5.8 IDE oops (TCQ breakage?)
Date: Wed, 17 Apr 2002 13:33:39 +0200 [thread overview]
Message-ID: <3CBD5D93.30501@evision-ventures.com> (raw)
In-Reply-To: <200204161749.TAA16333@harpo.it.uu.se> <3CBD45BD.4040209@evision-ventures.com> <20020417120817.GA800@suse.de> <20020417122502.GB800@suse.de>
Jens Axboe wrote:
> On Wed, Apr 17 2002, Jens Axboe wrote:
>
>>On Wed, Apr 17 2002, Martin Dalecki wrote:
>>
>>>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);
>>>
>>>OK it could be that the tca goesn't get allocated if there
>>>was no chipset selected. Lets have a look...
>>
>>Add a drive->using_dma check to ide_dma_queued_on in ide-tcq.c, it needs
>>to look like this:
>>
>>ide_tcq_dmaproc()
>>{
>>
>> ...
>>
>> case ide_dma_queued_off:
>> enable_tcq = 0;
>> case ide_dma_queued_on:
>> if (!drive->using_dma)
>> return 1;
>> return ide_enable_queued(drive, enable_tcq);
>> default:
>> break;
>> }
>>
>>that should fix it.
Yes I see. However for now I will just concentrate on ide-cd.c and
await you to merge up with IDE 37 OK? (It should be easy this time :-).
next prev parent reply other threads:[~2002-04-17 12:35 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
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 [this message]
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=3CBD5D93.30501@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox