From: Martin Dalecki <dalecki@evision-ventures.com>
To: rwhron@earthlink.net
Cc: 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 10:15:56 +0200 [thread overview]
Message-ID: <3CC669BC.8090208@evision-ventures.com> (raw)
In-Reply-To: <20020423205601.A21267@rushmore>
Uz.ytkownik rwhron@earthlink.net napisa?:
> It sounds like Jens and Martin have a handle on this
> already. Just in case this helps. No modules.
Yeep.
> Oops on 2.5.9 at boot time.
That is indeed a bit surprising. In esp. since the oops happens at boot time.
Maybe some goot order problem.
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.
next prev parent reply other threads:[~2002-04-24 9:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-24 0:56 2.5.9 -- OOPS in IDE code (symbolic dump and boot log included) rwhron
2002-04-24 8:15 ` Martin Dalecki [this message]
2002-04-24 13:01 ` Melchior FRANZ
-- 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 13:30 rwhron
2002-04-24 13:33 ` Jens Axboe
2002-04-24 13:39 ` Martin Dalecki
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=3CC669BC.8090208@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--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 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.