From: Andi Kleen <ak@suse.de>
To: "Bryan O'Sullivan" <bos@serpentine.com>
Cc: ak@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [2.5.72] Oops on x86_64 running 32-bit code
Date: Thu, 19 Jun 2003 00:45:16 +0200 [thread overview]
Message-ID: <20030618224516.GF3543@wotan.suse.de> (raw)
In-Reply-To: <1055976017.25153.74.camel@serpentine.internal.keyresearch.com>
On Wed, Jun 18, 2003 at 03:40:17PM -0700, Bryan O'Sullivan wrote:
> Call Trace:<ffffffff80113b38>??default_do_nmi+56?? <ffffffff8011c787>??do_nmi+87??
> <ffffffff801126dc>??nmi+112?? <ffffffff801320f2>??load_balance+34??
Looks quite garbled. Is it reproducible?
-Andi
next prev parent reply other threads:[~2003-06-18 22:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-18 22:40 [2.5.72] Oops on x86_64 running 32-bit code Bryan O'Sullivan
2003-06-18 22:45 ` Andi Kleen [this message]
2003-06-18 22:51 ` Bryan O'Sullivan
2003-06-18 23:06 ` Andi Kleen
2003-06-18 23:14 ` Bryan O'Sullivan
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=20030618224516.GF3543@wotan.suse.de \
--to=ak@suse.de \
--cc=bos@serpentine.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.