From: Ingo Molnar <mingo@elte.hu>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Joshua Hoblitt <j_kernel@hoblitt.com>,
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: Sat, 23 Aug 2008 12:43:11 +0200 [thread overview]
Message-ID: <20080823104311.GC25904@elte.hu> (raw)
In-Reply-To: <86802c440808222252j6f900f1dlfbf1378a7bc35ee4@mail.gmail.com>
* Yinghai Lu <yhlu.kernel@gmail.com> wrote:
> On Fri, Aug 22, 2008 at 5:22 PM, Joshua Hoblitt <j_kernel@hoblitt.com> wrote:
> > 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?
>
> could be other problem.
>
> cpu should be smarter enough to understand the missing bits in mask.
> at least amd cpu. remember that we didn't set mask bits to 40bits with
> opteron with LinuxBIOS, and everything still works well.
yeah. Is the deadlock debuggable? (does nmi_watchdog=1 produce anything
useful, or does the enabling of CONFIG_PROVE_LOCKING=y show anything
weird in the syslog during light, non-deadlocking use of this workload?)
Ingo
next prev parent reply other threads:[~2008-08-23 10:43 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
2008-08-23 5:52 ` Yinghai Lu
2008-08-23 10:43 ` Ingo Molnar [this message]
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=20080823104311.GC25904@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=j_kernel@hoblitt.com \
--cc=linux-kernel@vger.kernel.org \
--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 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.