From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows 98) Description of problem: The RedHat 8.0 is hang at boot to SMP mode after disable the Hyper Threading mode of CPU (P4). But boot into normal mode is OK. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.Install the RedHat 8.0 with the HyperThreading enabled CPU 2.Boot to SMP mode : OK (The CPU HyperThreading enabled) 3.Boot to SMP mode : hang (if the CPU HyperThreading disabled) Additional info: 1.Install the RedHat 7.3 with the HyperThreading enabled CPU 2.Boot to SMP mode : OK (The CPU HyperThreading enabled) 3.Boot to SMP mode : OK (if the CPU HyperThreading disabled)
how many physical cpu's do you have? one? if you have HT off you should then probably just boot into the UP kernel...
Yes, this is only happne in one physical cpu and disable the HT, and then enter the SMP mode. If two physical cpu and disable the HT, and enter the SMP mode, it's ok. But in RedHat 7.3 it is OK to boot into SMP mode with HT disable, so out customer just us ask why?
Dear Arjan van de Ven on, So,does the system hang is normal(or acceptable) that plugged single processor to enter the SMP mode in RedHat 8.0?
1 phsyical, 2 logical CPU's should just work with the SMP kernel. 1 phsyical, 1 logical CPU doesnt' work on all machines unfortionatly with the SMP kernel
Dear Arjan van de Ven on, Thanks for your comments. Our customer just wandering that in RedHat v7.3, it is OK to install/operate the the Linux with "1 phsyical, 1 logical CPU" in SMP mode, but in RedHat 8.0, it's failed. The RedHat Linux was installed by "1 phsyical, 2 logical CPU's", and the disable th HyperThreading ==> "1 phsyical, 1 logical CPU". Then in v7.3 it is OK to enter Linux enviroment, but in v8.0 it is failed. So, which verion is correct for this operation?
Thanks for the bug report. However, Red Hat no longer maintains this version of the product. Please upgrade to the latest version and open a new bug if the problem persists. The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, and if you believe this bug is interesting to them, please report the problem in the bug tracker at: http://bugzilla.fedora.us/