From: Dave Jones <davej@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Luca Montecchiani <luca.montecchiani@teamfab.it>,
linux-kernel@vger.kernel.org
Subject: Re: [OOPS] Linux 2.2.21pre[23]
Date: Thu, 7 Mar 2002 17:17:56 +0100 [thread overview]
Message-ID: <20020307171756.F29587@suse.de> (raw)
In-Reply-To: <3C878FC8.86FCC3@teamfab.it> <E16j0fe-0002m9-00@the-village.bc.nu>
In-Reply-To: <E16j0fe-0002m9-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Thu, Mar 07, 2002 at 04:23:10PM +0000
On Thu, Mar 07, 2002 at 04:23:10PM +0000, Alan Cox wrote:
> > Unable to handle kernel paging request at virtual address 756e654f
> Thats not good. We tried to use a piece of ascii text as a pointer 8)
"une0". Hmm. First guess was it was part of "unexpected interrupt",
but thats the wrong case.
> > my 0.2 euro on: [Backport a lot of x86 setup] ;)
> Ditto - especially the MCE changes.
I just did a quick glance at the code, and realised I goofed, and
AMD & Centaur CPUs won't get to the mcheck_init call.
Unrelated to this incident, but a problem all the same.
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-03-07 16:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-02 12:07 Linux 2.2.21pre2 Alan Cox
2002-03-07 16:05 ` [OOPS] Linux 2.2.21pre[23] Luca Montecchiani
2002-03-07 16:23 ` Alan Cox
2002-03-07 16:17 ` Dave Jones [this message]
2002-03-07 16:29 ` Luca Montecchiani
2002-03-07 16:39 ` Dave Jones
2002-03-07 17:06 ` Luca Montecchiani
2002-03-07 17:11 ` Dave Jones
2002-03-07 17:26 ` SOLVED " Luca Montecchiani
2002-03-07 17:20 ` Alan Cox
2002-03-11 8:44 ` Ext2/3 uid/gid support Erik Meusel
2002-03-11 8:47 ` Mike Fedyk
2002-03-11 9:22 ` Erik Meusel
2002-03-11 15:21 ` Matthias Andree
2002-03-11 16:44 ` Andreas Dilger
2002-03-12 1:48 ` Andrew Hatfield
-- strict thread matches above, loose matches on Subject: below --
2002-03-07 19:42 [OOPS] Linux 2.2.21pre[23] Julian Anastasov
2002-03-07 19:48 ` Richard B. Johnson
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=20020307171756.F29587@suse.de \
--to=davej@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.montecchiani@teamfab.it \
/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