From: Jens Axboe <axboe@suse.de>
To: Adam Kropelin <akropel1@rochester.rr.com>
Cc: Dave Jones <davej@suse.de>,
Martin Dalecki <dalecki@evision-ventures.com>,
linux-kernel@vger.kernel.org
Subject: Re: [OOPS] 2.5.8-dj1 reading /proc/ide/.../identify
Date: Thu, 18 Apr 2002 08:12:09 +0200 [thread overview]
Message-ID: <20020418061209.GE858@suse.de> (raw)
In-Reply-To: <02ac01c1e666$95ddac70$02c8a8c0@kroptech.com>
On Wed, Apr 17 2002, Adam Kropelin wrote:
> The following oops is reproducable on 2.5.8-dj1 here.
>
> cat /proc/ide/ide0/hda/identify a few times and *bang*.
>
> The system usually takes one more command after the oops,
> then locks solid. The oops never makes it to syslog.
Problem has been solved in later kernels. Fix is in the patch I just
sent to you in the other thread, the archives should also hold a message
from me explaining what the problem is and how to fix it (see static ar,
return to pool, ATA_AR_RETURN/ATA_AR_POOL).
--
Jens Axboe
prev parent reply other threads:[~2002-04-18 6:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-17 23:21 [OOPS] 2.5.8-dj1 reading /proc/ide/.../identify Adam Kropelin
2002-04-18 6:12 ` Jens Axboe [this message]
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=20020418061209.GE858@suse.de \
--to=axboe@suse.de \
--cc=akropel1@rochester.rr.com \
--cc=dalecki@evision-ventures.com \
--cc=davej@suse.de \
--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