From: Joshua Hoblitt <j_kernel@hoblitt.com>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
bugme-daemon@bugzilla.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Bug 11388] New: 2.6.27-rc3 warns about MTRR range; only 3 of 16gb of memory is usable
Date: Fri, 22 Aug 2008 14:22:35 -1000 [thread overview]
Message-ID: <20080823002235.GL23377@hoblitt.com> (raw)
In-Reply-To: <86802c440808212148k74e56fa2mdb2e329ed4df1271@mail.gmail.com>
I've confirmed that the boards in these systems are Tyan Tempest i5400PW
(S5397)s. We've discovered a workload that will deadlock the system
under both 2.6.24.2 and -tip kernel with the mtrr masking patch. The
only thing unusual about this workload is that one of the binaries in
it constantly segvs... Is it possible that these deadlocks (no kernel
oops on console) are caused by MSR setup wierdness or is it likely unrelated?
-J
--
On Thu, Aug 21, 2008 at 09:48:41PM -0700, Yinghai Lu wrote:
> On Thu, Aug 21, 2008 at 8:56 PM, Ingo Molnar <mingo@elte.hu> wrote:
> >
> > * Ingo Molnar <mingo@elte.hu> wrote:
> >
> >> i've tidied up your patch (see the commit below) and have queued it up
> >> in x86/urgent. It seems fairly safe and i guess we can push it to
> >> v2.6.27 if Joshua reports test success. Joshua, could you give it a go
> >> please?
> >
> > or just try the latest tip/master - please check whether you are getting
> > the right amount of RAM out of box plus this warning message:
> >
> >> WARN_ON("mtrr: your BIOS has set up an incorrect mask, fixing it up.\n");
> >
>
> according to his dmesg, it works.
>
> may need to change it to WARN_ON only print one time
>
> YH
next prev parent reply other threads:[~2008-08-23 0:22 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-11388-27@http.bugzilla.kernel.org/>
2008-08-21 1:04 ` [Bug 11388] New: 2.6.27-rc3 warns about MTRR range; only 3 of 16gb of memory is usable Andrew Morton
2008-08-21 1:20 ` Yinghai Lu
2008-08-21 1:49 ` Yinghai Lu
2008-08-21 11:44 ` Ingo Molnar
2008-08-21 11:56 ` Ingo Molnar
2008-08-21 15:39 ` Yinghai Lu
2008-08-22 3:51 ` Ingo Molnar
2008-08-22 4:45 ` Yinghai Lu
2008-08-21 20:55 ` Joshua Hoblitt
2008-08-21 21:51 ` Yinghai Lu
2008-08-21 23:33 ` Joshua Hoblitt
2008-08-22 0:10 ` Joshua Hoblitt
2008-08-22 0:28 ` Yinghai Lu
2008-08-22 0:29 ` Joshua Hoblitt
2008-08-22 1:00 ` Joshua Hoblitt
2008-08-22 1:10 ` Joshua Hoblitt
2008-08-22 1:55 ` Yinghai Lu
2008-08-22 2:15 ` Joshua Hoblitt
2008-08-22 2:26 ` Yinghai Lu
2008-08-22 3:24 ` Yinghai Lu
2008-08-22 3:50 ` Ingo Molnar
2008-08-22 3:56 ` Ingo Molnar
2008-08-22 4:48 ` Yinghai Lu
2008-08-23 0:22 ` Joshua Hoblitt [this message]
2008-08-23 5:52 ` Yinghai Lu
2008-08-23 10:43 ` Ingo Molnar
2008-08-26 8:35 ` Joshua Hoblitt
2008-08-26 8:42 ` Ingo Molnar
2008-08-25 21:43 ` Joshua Hoblitt
2008-08-22 6:16 ` Yinghai Lu
2008-08-22 6:24 ` Ingo Molnar
2008-08-23 23:53 ` Arjan van de Ven
2008-08-25 9:17 ` Ingo Molnar
2008-08-22 3:26 ` Joshua Hoblitt
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=20080823002235.GL23377@hoblitt.com \
--to=j_kernel@hoblitt.com \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=yhlu.kernel@gmail.com \
/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