From: Reinhard Nissl <rnissl@gmx.de>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: linux-kernel@vger.kernel.org, "Brown, Len" <len.brown@intel.com>
Subject: Re: processor module locks up hyperthreading enabled machine
Date: Tue, 01 Nov 2005 23:47:09 +0100 [thread overview]
Message-ID: <4367F06D.2080405@gmx.de> (raw)
In-Reply-To: <88056F38E9E48644A0F562A38C64FB6005FDFBEA@scsmsx403.amr.corp.intel.com>
Hi,
I'm sorry for the delay. Here are the results:
Pallipadi, Venkatesh wrote:
> 1) Does this problem go way if you boot with maxcpus=1?
No.
The modules are loaded via initrd and SuSE prints the name of the module
before loading it. So I get on console
Loading processor
ACPI: CPU0 (power states:C1[C1])
ACPI: CPU0 (power states:C1[C1])
Loading thermal
Loading fan
Waiting for device /dev/sda1 to appear: ok
Attempting manual resume
Loading jdb
Loading ext
Waiting for device /dev/sda2 to appear: ok
rootfs: major=8 minor=2 devn=2050
Then the system freezes.
Without the maxcpus argument the freeze happens already in front of the
above "Loading thermal" line.
> 2) Does the problem go away if you not load the acpi processor module?
Yes.
When I remove processor (and thermal as it has a dependency on
processor) to be loaded by initrd then the freeze happens at some time
later when acpid gets started, as SuSE loads these modules at that time
again in case they were not loaded already.
When I remove loading the processor (and thermal) module at this
location too, then the system is running ok so far besides the
restrictions which result from not loading these modules.
What should I try next?
Bye.
--
Dipl.-Inform. (FH) Reinhard Nissl
mailto:rnissl@gmx.de
next prev parent reply other threads:[~2005-11-01 22:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-13 0:59 processor module locks up hyperthreading enabled machine Pallipadi, Venkatesh
2005-11-01 22:47 ` Reinhard Nissl [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-04 4:05 Pallipadi, Venkatesh
2005-11-01 22:54 Pallipadi, Venkatesh
2005-11-02 19:29 ` Reinhard Nissl
2005-10-12 21:29 Reinhard Nissl
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=4367F06D.2080405@gmx.de \
--to=rnissl@gmx.de \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=venkatesh.pallipadi@intel.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