Re: Wolk 4.9 smp cpu detection and initialization problems

Olaf Unterkofler <[email protected]>
Newsgroups gmane.linux.wolk.devel
Message-ID <[email protected]>
Hi Marcel,

On Sun, 14 Sep 2003, Marcel de Riedmatten wrote:

> Hi Olaf
>
> I am intersted in your problems because I'll soon have similar hardware
> to play with.

Hmmm, it looks loke I am playing the testcandidate again ;-(
>
> >
> > After looking at the boot-logs and "/proc/interrupts", I have the strange
> > feeling that the wolk kernel recognizes the processors (4 in all, thanks
> > to hyperthreading), but does not initialize them correctly.
> > Deactivating hyperthreading or ACPI in the BIOS or via the kernel options
> > results in only two CPUs beeing found (the first physical ?). Only the
>
> yes both have physical id 0
>

I noticed that .....

>
> As a try to narrow the case allow me some observations:
>
>
> 1) you use a lot of laptop like config (cpufreq, acpi stuff). for smp/ht
> you just need
>
> CONFIG_ACPI=y
> CONFIG_ACPI_HT_ONLY=y
> CONFIG_ACPI_BOOT=y
>
>
> 2) you have  CONFIG_HIGHMEM64G=y which is not needed as you a 1 GB of
> ram
>
>

Right - I tried with 4GB - no change. I didn't disable the laptop/ACPI
stuff yet. The config I am using is, as far as CPU/ACPI/memmory stuff
goes, currently identical with the SuSE SMP config.

> > Hope this is enough information to track down the problem - if not, I
> >will try to provide any necessary information.
>
> if it is very unstable some oops would be ok or is it hard lock ?

Hard lock - the beasts stop dead - about 98% of the time (black screen, no
log, no console output), or every once in a while I have a reboot.  As
soon as I disable ACPI (wich happens to disable the second CPU) or the
second CPU directly the system seems to work fine (no lockup, no reboot).
I have the subtle feeling that the kernel tries to pass some
task/interrupt handler or whatever to the second/third/fourth CPU and then
gets stuck. Changing the maximum number of CPUs to more than 4 causes the
system to reboot during kernel initialization - again, without any output
on the console. The machines simply loop in that state until I press the
reset switch.


-- 
Mit freundlichen Gruessen / With kind regards,

Olaf Unterkofler


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
WOLK - Working Overloaded Linux Kernel
[email protected]
https://lists.sourceforge.net/lists/listinfo/wolk-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.