From: Jeremy Fitzhardinge <jeremy@goop.org>
To: lkml@MoreThan.org
Cc: linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
the arch/x86 maintainers <x86@kernel.org>,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [Bug Fix]: Do 32-bit table calculations in pre-processor
Date: Fri, 03 Jul 2009 12:11:54 -0700 [thread overview]
Message-ID: <4A4E57FA.4000609@goop.org> (raw)
In-Reply-To: <200907031403.34566.lkml@morethan.org>
On 07/03/09 12:03, Michael S. Zick wrote:
> Random system halts, deadlocks with interrupts disabled?
> Yup, that sounds familiar.
>
No, mostly memory corruption, with all sorts of indicative kernel
messages (esp if you have all the debugging options on).
But my point is that if there were something wrong in that particular
piece of code, it would have very widespread effects. It would not be
subtle in the sense of only affecting one or two people.
> If I ever get more than a stopped machine with a glowing power light;
> I will be certain to share.
>
Hm, well that does sound serious, but I think you're barking up the
wrong tree with this particular patch.
J
next prev parent reply other threads:[~2009-07-03 19:12 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-03 18:14 Michael S. Zick
2009-07-03 18:27 ` Andi Kleen
2009-07-03 18:38 ` Michael S. Zick
2009-07-03 19:08 ` Jeremy Fitzhardinge
2009-07-03 19:13 ` Michael S. Zick
2009-07-03 19:30 ` Jeremy Fitzhardinge
2009-07-03 20:03 ` Michael S. Zick
2009-07-03 18:56 ` Jeremy Fitzhardinge
2009-07-03 18:57 ` Jeremy Fitzhardinge
2009-07-03 19:03 ` Michael S. Zick
2009-07-03 19:11 ` Jeremy Fitzhardinge [this message]
2009-07-03 19:18 ` H. Peter Anvin
2009-07-03 19:46 ` Michael S. Zick
2009-07-03 20:00 ` H. Peter Anvin
2009-07-03 19:14 ` H. Peter Anvin
2009-07-03 19:41 ` Michael S. Zick
2009-07-03 19:48 ` H. Peter Anvin
2009-07-03 20:38 ` Michael S. Zick
2009-07-03 20:40 ` H. Peter Anvin
2009-07-03 21:02 ` Michael S. Zick
2009-07-03 22:33 ` H. Peter Anvin
2009-07-04 0:05 ` Michael S. Zick
2009-07-04 0:11 ` H. Peter Anvin
2009-07-03 22:01 ` Michael S. Zick
2009-07-04 13:23 ` Michael S. Zick
2009-07-03 19:33 ` Jeremy Fitzhardinge
2009-07-03 20:07 ` Yinghai Lu
2009-07-03 20:08 ` Yinghai Lu
2009-07-03 20:48 ` Michael S. Zick
2009-07-03 20:45 ` Michael S. Zick
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=4A4E57FA.4000609@goop.org \
--to=jeremy@goop.org \
--cc=ak@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@MoreThan.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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®