Bug 141973 - Kernel problem with Hyperthreading
Summary: Kernel problem with Hyperthreading
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Kernel (show other bugs)
Version: unspecified
Hardware: i386 SuSE Linux 10.0
: P5 - None : Critical
Target Milestone: ---
Assignee: Thomas Renninger
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-08 23:29 UTC by Pedro Zenon
Modified: 2006-01-10 14:41 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Pedro Zenon 2006-01-08 23:29:24 UTC 
I have a Toshiba Laptop, when i install SuSE 10.0 i have to change the kernel-smp to a default kernel that' s because the kernel-smp do not boot. I think it is because of the hiperthreading, but i disable the hyperthreading in the bios and it's continue with the problem. How i can solve it. Ahh, other thing the only way the kernel-smp works is if i disable all the api's api=off on grup window. 


I hope you can help me on it.
Comment 1 Olaf Kirch 2006-01-09 16:11:14 UTC 
So does it work if you install kernel-default instead of kernel-smp?
Comment 2 Pedro Zenon 2006-01-09 23:08:16 UTC 
Yes, the only way that it's work is if i install the kernel-default
Comment 3 Lars Marowsky-Bree 2006-01-10 11:22:31 UTC 
Sounds like an ACPI problem.
Comment 5 Thomas Renninger 2006-01-10 13:12:57 UTC 
This could already be fixed.
I can tell you for sure if you attach the output of acpidmp.

Olaf, Andreas, how can I point people to a recent 10.0 branch kernel for testing?
In ftp.suse.com/pub/people/mantel/kotd/10.0-x86_64/SL100_BRANCH/kernel-*
there are only tar.gz s.
Comment 6 Andreas Gruenbacher 2006-01-10 14:41:46 UTC 
Please point people at ftp://ftp.suse.com/pub/projects/kernel/kotd instead, even though this does not explain your problem.

The problem is how we expire kernels in /mounts/dist/kerneltest/: we only have limited space there, so we expire old kernels automatically. The last update in SL100_BRANCH was a while back (up until today's update), and so all kernels from there got eventually removed. This has happened repeatedly already, but I don't know a good way how to fix it. If you can come up with a better approach how to keep /mounts/dist/kerneltest/ to a given maximum size without being even more unfair, that would be great ;)

Tomorrow's kotd will have the SL100_BRANCH kernel from today.