mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Avuton Olrich <avuton@gmail.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: Kernel panic: Machine check exception
Date: Wed, 7 Dec 2005 18:46:04 -0800	[thread overview]
Message-ID: <3aa654a40512071846j247bd4a2r264da0904fa300fb@mail.gmail.com> (raw)
In-Reply-To: <m1wtiicwbv.fsf@ebiederm.dsl.xmission.com>

On 12/6/05, Eric W. Biederman <ebiederm@xmission.com> wrote:
> In this case bank 4 is the appropriate bank.  Although the
> other bits don't look right for a memory error.  I wonder
> if it is that darn iommu fault again.

You know, I have to say you _have_ to be right. While the MCE happens
at random times, since I've compiled without IOMMU in it has been
smooth sailing, when normally I would have locked up a few times by
now (Right after I send out this reply surely it will lockup). So, I
will end this thread by saying with that if you're using a Gigabyte
K8N51GMF-9 it's advisable to turn off IOMMU for now, if you get
lockups.

--
avuton
--
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

      parent reply	other threads:[~2005-12-08  2:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-19  9:45 Avuton Olrich
2005-11-19  9:55 ` Avuton Olrich
2005-11-19 10:02 ` Arjan van de Ven
2005-11-19 10:04   ` Avuton Olrich
2005-11-19 13:24 ` Alan Cox
2005-11-19 20:54   ` Avuton Olrich
2005-11-19 21:48     ` Alan Cox
2005-11-19 22:24       ` Nix
2005-12-06 11:13       ` Eric W. Biederman
2005-12-06 13:23         ` Avuton Olrich
2005-12-06 19:45         ` Andi Kleen
2005-12-06 18:45           ` Avuton Olrich
2005-12-06 18:47             ` Andi Kleen
2005-12-08  2:46         ` Avuton Olrich [this message]

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=3aa654a40512071846j247bd4a2r264da0904fa300fb@mail.gmail.com \
    --to=avuton@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=ebiederm@xmission.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®