From: Adam Kropelin <akropel1@rochester.rr.com>
To: hugh@veritas.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: scsi_io_completion oops on 2.4.10-pre5
Date: Mon, 10 Sep 2001 19:35:49 -0400 [thread overview]
Message-ID: <01091019354900.05688@devbox> (raw)
Hugh Dickens wrote:
> On Sun, 9 Sep 2001, Adam Kropelin wrote:
> > The below oops is easily reproducable for me under 2.4.10-pre5.
> > Unable to handle kernel paging request at virtual address 46454c22
> > >>EIP; c020c444 <scsi_io_completion+88/370> <=====
>
> Although there's nothing about this to link it with the page_alloc.c
> BUGs, that's clearly corruption ("LEF), and the page_alloc.c BUGs
> were caused by double use of a page: I wouldn't trust 2.4.10-pre5,
> think you should try to reproduce on -pre6 or -pre7 instead.
Sound advice, indeed. 2.4.10-pre7 handles everything I can throw
at it. I guess I just picked a bad Linus kernel to start with...
Thanks for the pointer.
--Adam
next reply other threads:[~2001-09-10 23:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-10 23:35 Adam Kropelin [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-10 2:41 scsi_io_completion oops on 2.4.10-pre5 Adam Kropelin
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=01091019354900.05688@devbox \
--to=akropel1@rochester.rr.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
/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