linux-kernel - Re: x86_64 2.6.35.* kernels and Intel Xeon X5550

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-id: <alpine.LFD.2.00.1010160338280.2238@localhost.localdomain>
Date:	Sat, 16 Oct 2010 03:46:46 -0400 (EDT)
From:	Len Brown <lenb@...nel.org>
To:	linux-kernel@...r.kernel.org, tsi@...berta.ca
Subject: Re: x86_64 2.6.35.* kernels and Intel Xeon X5550

> > 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/