public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@redhat.com>
To: bonganilinux@mweb.co.za (Bongani)
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox),
	mikesw@ns1.whiterose.net (M Sweger),
	linux-kernel@vger.kernel.org, alan@redhat.com
Subject: Re: linux 2.2.21 pre3, pre4 and rc1 problems. (fwd)
Date: Thu, 14 Mar 2002 16:50:19 -0500 (EST)	[thread overview]
Message-ID: <200203142150.g2ELoJr27197@devserv.devel.redhat.com> (raw)
In-Reply-To: <1016142855.14838.5.camel@localhost.localdomain> from "Bongani" at Mar 14, 2002 11:53:54 PM

> on 2.4.19-pre3 and 2.4.19-pre3-aa1. I put a couple of printk's to see
> where the problem was (arch/i386/bluesmoke.c), but after rebooting it
> did not show up. I just vompiled 2.4.19-pre3-aa and 2.4.19-pre3 +
> preempt, I would like o have it solved before I reboot though

The intel cpus get deeply upset if you write to bank zero of the error
reporting registers used by MCE exceptions. The AMD ones want you to do so
and the change that went in was tested on AMD boxes but not Intel.

Revert the bluesmoke.c change and all should be well

  reply	other threads:[~2002-03-14 21:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-14 20:19 linux 2.2.21 pre3, pre4 and rc1 problems. (fwd) M Sweger
2002-03-14 20:25 ` Dave Jones
2002-03-14 21:40 ` Alan Cox
2002-03-14 21:43   ` Alan Cox
2002-03-15 14:07     ` M Sweger
2002-03-15 14:50       ` Alan Cox
2002-03-15 14:58         ` Ville Herva
2002-03-15 19:49           ` M Sweger
2002-03-14 21:53   ` Bongani
2002-03-14 21:50     ` Alan Cox [this message]
2002-03-14 21:59     ` linux 2.2.21 pre3, pre4 and rc1 problems Andreas Dilger

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=200203142150.g2ELoJr27197@devserv.devel.redhat.com \
    --to=alan@redhat.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bonganilinux@mweb.co.za \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikesw@ns1.whiterose.net \
    /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