From: "Garrett Serack" <Garrett_Serack@cpr.ca>
To: <linux-kernel@vger.kernel.org>
Subject: RE: Related Problems? [WAS: 2.6.0-test4: Unable to handle kernel NULL pointer dereference]
Date: Fri, 29 Aug 2003 10:41:04 -0600 [thread overview]
Message-ID: <68D2A80760018245B05351CDCACF543601DFDA@CALGARYMAIL04.cpr.ca> (raw)
My guess now is that they are not completely related, the fdisk one I think is fixed by 2.6.0-test4-mm-3, and the other two are not, but may be fixed by the other patch (~disable-athlon-prefetch) that was posted.
hmmm
G
-----Original Message-----
From: linux-kernel-owner@vger.kernel.org
[mailto:linux-kernel-owner@vger.kernel.org]On Behalf Of Garrett Serack
Sent: Friday, August 29, 2003 8:01 AM
To: linux-kernel@vger.kernel.org
Subject: Related Problems? [WAS: 2.6.0-test4: Unable to handle kernel
NULL pointer dereference]
I'm experiencing all of the problems in referenced in posts
"2.6.0-test4: Unable to handle kernel NULL pointer dereference"
"2.6.0-test4-mm2: fdisk causes Oops" (I get it with Lilo)
"2.6.0-test4 and hardware reports a non fatal incident"
Am I right in assuming that these are all related problems? It seems that they all appeared at once, when I went to 2.6.0-test4-mm2.
And, did these get fixed with 2.6.0-test4-mm3 ?
Thanks
Garrett
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2003-08-29 16:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-29 16:41 Garrett Serack [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-29 14:01 Garrett Serack
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=68D2A80760018245B05351CDCACF543601DFDA@CALGARYMAIL04.cpr.ca \
--to=garrett_serack@cpr.ca \
--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®