public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Dalecki <dalecki@evision-ventures.com>
To: Jens Axboe <axboe@suse.de>
Cc: rwhron@earthlink.net, linux-kernel@vger.kernel.org
Subject: Re: 2.5.9 -- OOPS in IDE code (symbolic dump and boot log included)
Date: Wed, 24 Apr 2002 15:39:48 +0200	[thread overview]
Message-ID: <3CC6B5A4.2050807@evision-ventures.com> (raw)
In-Reply-To: <20020424093021.A21652@rushmore> <20020424133329.GA8988@suse.de>

Uz.ytkownik Jens Axboe napisa?:
> On Wed, Apr 24 2002, rwhron@earthlink.net wrote:
> 
>>>>Oops on 2.5.9 at boot time.
>>>
>>>Could you please introduce two printk("BANG\n") printk("BOOM\n")
>>>aroung the ata_ar_get() in ide-cd? Just to see whatever the
>>>command queue is already up and initialized.
>>
>>This may not be what you wanted:
>>
>>	printk("BANG\n");
>>        ar = ata_ar_get(drive);
>>        printk("BOOM\n");
>>
>>If it is, neither BANG nor BOOM printed before oops.
> 
> 
> Look, the problem is easy. Backout the changes to ide_cdrom_do_request()
> and cdrom_start_read(), then re-add the
> 
> 	HWGROUP(drive)->rq->special = NULL;
> 
> in cdrom_end_request() before calling ide_end_request()
> 
> Something ala, completely untested (not even compiled). See the thread
> about the ide-cd changes being broken.
> 

Jens - this is *not going to work* becouse the DMA methods are
expecting an full ata_request right now.

Uunfortunately pulling the whole ata_ar_get() stuff one
level up to the ide.c file where ->do_request get's called
doesn't work right now.



  reply	other threads:[~2002-04-24 14:42 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-24 13:30 2.5.9 -- OOPS in IDE code (symbolic dump and boot log included) rwhron
2002-04-24 13:33 ` Jens Axboe
2002-04-24 13:39   ` Martin Dalecki [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-24 14:01 rwhron
2002-04-24 13:45 ` Martin Dalecki
2002-04-24  0:56 rwhron
2002-04-24  8:15 ` Martin Dalecki
2002-04-24 13:01   ` Melchior FRANZ
2002-04-23  8:18 Miles Lane
2002-04-23  8:00 ` Martin Dalecki
2002-04-23  9:18   ` Jens Axboe
2002-04-23  8:43     ` Martin Dalecki
2002-04-23  9:54       ` Jens Axboe
2002-04-23 17:39   ` Miles Lane
2002-04-23 17:54     ` Miles Lane
2002-04-24  8:06       ` Martin Dalecki
2002-04-24  9:11         ` Jens Axboe
2002-04-24  8:20           ` Martin Dalecki
2002-04-25 11:07           ` Martin Dalecki
2002-04-25 17:25             ` Jens Axboe
2002-04-25 17:34               ` Jens Axboe
2002-04-25 21:02                 ` Linus Torvalds
2002-04-24  9:29         ` Luigi Genoni
2002-04-23 18:23   ` Melchior FRANZ

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=3CC6B5A4.2050807@evision-ventures.com \
    --to=dalecki@evision-ventures.com \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rwhron@earthlink.net \
    /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