From: Marc Aurele La France <tsi@ualberta.ca>
To: linux-kernel@vger.kernel.org, Len Brown <len.brown@intel.com>
Subject: Re: x86_64 2.6.35.* kernels and Intel Xeon X5550
Date: Fri, 15 Oct 2010 20:42:35 -0600 (Mountain Daylight Time) [thread overview]
Message-ID: <alpine.WNT.1.10.1010152030320.280@tsi> (raw)
In-Reply-To: <alpine.WNT.2.00.1010071055420.1672@cluij.ucs.ualberta.ca>
On Thu, 7 Oct 2010, Marc Aurele La France wrote:
> I administer a cluster composed of a mixture of various Opteron models and
> Intel Xeon X5550's. The 2.6.34.*, and prior, kernels run fine on all of
> them. The 2.6.35 series also runs fine on the Opterons, but not on the
> Xeon's. All of these are CONFIG_GENERIC_CPU kernels.
> On the Xeon's, 2.6.35 hangs early on, upon the first test of trace events
> (in kernel/trace/trace_events.c:event_trace_self_tests()). When disabling
> all tracing, debugging, etc., it still hangs but slightly later. The
> megaraid_sas module is loaded, detects the adapter, but never gets around to
> registering it with the SCSI layer.
> Core2-specific kernels also hang the same way, as do UP kernels. I've tried
> backing out certain commits that seemed likely candidates, but have yet to
> stumble upon the one (or more) that is causing this.
> Does anyone have any ideas?
This is due to "CONFIG_INTEL_IDLE=y". "m" or "n", the hang doesn't occur.
Of the kernels I've tested, INTEL_IDLE first appears in 2.6.34-git15. So,
technically, this is not a regression against 2.6.34.
This does, however, amount to a vote of non-confidence against intel_idle.c.
Marc.
+----------------------------------+----------------------------------+
| Marc Aurele La France | work: 1-780-492-9310 |
| Academic Information and | fax: 1-780-492-1729 |
| Communications Technologies | email: tsi@ualberta.ca |
| 352 General Services Building +----------------------------------+
| University of Alberta | |
| Edmonton, Alberta | Standard disclaimers apply |
| T6G 2H1 | |
| CANADA | |
+----------------------------------+----------------------------------+
next prev parent reply other threads:[~2010-10-16 2:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 17:17 Marc Aurele La France
2010-10-16 2:42 ` Marc Aurele La France [this message]
2010-10-16 7:46 ` Len Brown
2010-10-18 16:46 ` Marc Aurele La France
2010-10-18 20:48 ` Marc Aurele La France
2010-10-20 0:22 ` Henrique de Moraes Holschuh
2010-10-20 1:04 ` Marc Aurele La France
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=alpine.WNT.1.10.1010152030320.280@tsi \
--to=tsi@ualberta.ca \
--cc=len.brown@intel.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 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®