From: "Randy.Dunlap" <rddunlap@osdl.org>
To: <davidsen@tmr.com>
Cc: <akpm@osdl.org>, <cswingle@iarc.uaf.edu>, <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0-test4: Unable to handle kernel NULL pointer dereference
Date: Thu, 28 Aug 2003 19:33:55 -0700 (PDT) [thread overview]
Message-ID: <32865.4.4.25.4.1062124435.squirrel@www.osdl.org> (raw)
In-Reply-To: <Pine.LNX.3.96.1030828220150.466A-100000@gatekeeper.tmr.com>
> On Thu, 28 Aug 2003, Andrew Morton wrote:
>
>> Christopher Swingley <cswingle@iarc.uaf.edu> wrote:
>> >
>> > kernel: Unable to handle kernel NULL pointer dereference at virtual
>> address 00000000 ...
>> > kernel: EIP is at find_inode_fast+0x1a/0x60
>> > ...
>> > model name : AMD Athlon(tm) XP 1800+
>> > ...
>>
>> You've been bitten by the athlon-prefetch(0)-goes-oops problem.
>>
>> Nobody seems to be working this, so I'll be sending the below in to Linus.
>
> Let's not. If this goes in the Athlon users will get bad performance,
> reliable operation, and no one will blame anything but the Athlon... If it
> keeps oopsing hopefully people will complain and it will get fixed.
>
> Taking out features instead of fixing them is a bad president, this is not a
> driver for an obsolete ISA card, this is a performance boost for a very
> current CPU. I'm surprised AMD hasn't looked at it themselves.
Is this the same issue as
http://marc.theaimsgroup.com/?l=linux-kernel&m=106080170017645&w=2
in which AMD said, "Let us get back to you, ok?" on Aug. 13?
~Randy
next prev parent reply other threads:[~2003-08-29 2:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-28 15:34 Christopher Swingley
2003-08-28 20:10 ` Andrew Morton
2003-08-29 2:06 ` Bill Davidsen
2003-08-29 2:32 ` Andrew Morton
2003-08-29 2:33 ` Randy.Dunlap [this message]
2003-08-29 2:40 ` Andrew Morton
2003-08-29 10:06 ` Alan Cox
2003-08-29 14:17 ` Hollis Blanchard
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=32865.4.4.25.4.1062124435.squirrel@www.osdl.org \
--to=rddunlap@osdl.org \
--cc=akpm@osdl.org \
--cc=cswingle@iarc.uaf.edu \
--cc=davidsen@tmr.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
all inboxes | Powered by JetHome®