From: Andre Tomt <lkml@tomt.net>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: Magnus Stenman <stone@hkust.se>
Subject: Re: oops on P4 i875 w/ 2 gig RAM [2.4 stuff]
Date: Fri, 28 Nov 2003 13:52:19 +0100 [thread overview]
Message-ID: <1070023938.29985.35.camel@slurv.pasop.tomt.net> (raw)
In-Reply-To: <3FC72D71.9090708@hkust.se>
On Fri, 2003-11-28 at 12:11, Magnus Stenman wrote:
> nobody has any clues?
>
> you know, there *is* a juicy kernel BUG in there
Looks like you use a Red Hat kernel, it's heavily patched, and has thus
its own set of problems. You're probably better off bugging Red Hat
instead.
next prev parent reply other threads:[~2003-11-28 12:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-24 11:42 oops on P4 i875 w/ 2 gig RAM Magnus Stenman
2003-11-28 11:11 ` oops on P4 i875 w/ 2 gig RAM [2.4 stuff] Magnus Stenman
2003-11-28 12:52 ` Andre Tomt [this message]
2003-11-28 13:06 ` Markus Hästbacka
2003-11-28 14:43 ` Zoran Davidovac
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=1070023938.29985.35.camel@slurv.pasop.tomt.net \
--to=lkml@tomt.net \
--cc=linux-kernel@vger.kernel.org \
--cc=stone@hkust.se \
/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
Powered by JetHome