Re: [2.5.72] Oops on x86_64 running 32-bit code

From: Andi Kleen (ak@suse.de)
Date: Wed Jun 18 2003 - 17:45:16 EST

Next message: Greg KH: "Re: [RFC] PCI device list locking - take 2"
Previous message: Con Kolivas: "Re: [PATCH] 2.5.72 O(1) interactivity bugfix"
In reply to: Bryan O'Sullivan: "[2.5.72] Oops on x86_64 running 32-bit code"
Next in thread: Bryan O'Sullivan: "Re: [2.5.72] Oops on x86_64 running 32-bit code"
Reply: Bryan O'Sullivan: "Re: [2.5.72] Oops on x86_64 running 32-bit code"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Next message: Greg KH: "Re: [RFC] PCI device list locking - take 2"
Previous message: Con Kolivas: "Re: [PATCH] 2.5.72 O(1) interactivity bugfix"
In reply to: Bryan O'Sullivan: "[2.5.72] Oops on x86_64 running 32-bit code"
Next in thread: Bryan O'Sullivan: "Re: [2.5.72] Oops on x86_64 running 32-bit code"
Reply: Bryan O'Sullivan: "Re: [2.5.72] Oops on x86_64 running 32-bit code"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Mon Jun 23 2003 - 22:00:27 EST