From: Len Brown <lenb@kernel.org>
To: linux-kernel@vger.kernel.org, tsi@ualberta.ca
Subject: Re: x86_64 2.6.35.* kernels and Intel Xeon X5550
Date: Sat, 16 Oct 2010 03:46:46 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.1010160338280.2238@localhost.localdomain> (raw)
In-Reply-To: <alpine.WNT.1.10.1010152030320.280@tsi>
> > 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.
> This is due to "CONFIG_INTEL_IDLE=y".
Please file a bug report at bugzilla.kernel.org and assign it to me.
Please reproduce using an upstream 2.6.36-rc8 kernel.
Boot a CONFIG_INTEL_IDLE=n kernel and to the bug report...
attach the output from acpidump
'cat /proc/cpuinfo'
'grep . /sys/devices/system/cpu/cpu*/cpuidle/*/*'
'lspci'
Then boot a CONFIG_INTEL_IDLE=y kernel and see what is the highest N that
boots when you boot with "intel_idle.max_cstate=N" (0 will disable
the driver completely) and if any of them boot, for the highest N,
attach to the bug report the complete dmesg and the output from
'grep . /sys/devices/system/cpu/cpu*/cpuidle/*/*'
thanks,
-Len Brown, Intel Open Source Technology Center
next prev parent reply other threads:[~2010-10-16 7:46 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
2010-10-16 7:46 ` Len Brown [this message]
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.LFD.2.00.1010160338280.2238@localhost.localdomain \
--to=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tsi@ualberta.ca \
/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®