Re: Wolk 4.10-pre6 smp cpu detection and initialization problems

Hi Marc,


On Thu, 18 Sep 2003, Marc-Christian Petersen wrote:
>
> > - Booting with vga=0x317 now works again
> good.
>
> > - Still only physical CPU 0 is getting initialized.
> fuck :(
>
> > - NEW: /proc/interrupts entry has disappeared ??
> yes, mistake by me. Already fixed in my local tree.
>
> > - Xfree startup still causes system deadlock
> fuck
>
> > - SuSE hwbootscan still causes system deadlock
> fuck
>
> I really don't understand why this happens.

Your'e not the only one :-(

>
> > - The compile errors mentioned for pre-5 are still there.
> > - Only following dependany error is left over:
> > depmod: *** Unresolved symbols in
> > /lib/modules/2.4.20-wolk4.10s/kernel/drivers/usb/usbnet.o depmod: 	crc32_le
>
> Ok, I'll fix it up.
>

Thanks

> Please try the attached .config and see if it works better. Thanks.

Sorry - no.


> It seems SMP itself is very stable and works correct. At least my 2 SMP
> Systems I have access to are working very nicely, but both lacks HT support.
> Seems HT is the culprit.

I disabled HT in the BIOS - but still only CPU0 gets initialized. I have
the strange feekling, that it might be an IO/APIC problem. These new
boards are full of APICV, PCI-bridges and other stuff that love to cause
headaches.

>
> -----------------------------------------------------------------------------
> And now the 3rd time: Please do yourself a favor and remove _ALL_ 'not needed
> modules/drivers for the testing machine' in the .config!!!!!!!!!!!!!!!!!!!!!!
> -----------------------------------------------------------------------------
>

OK, OK !!

> Please make further tests _ONLY_ with needed options on the kernel config.
> Maybe the problem is with something you've selected?!
>

I threw out quite a lot, but no luck as to finding a solution.

> What XFree driver are you using? Try to disable almost everything which is not
> needed to narrow things down! agpgart, nvidia shit or whatever.
>

I'm using the ATI video drivers.

> I've disabled grsecurity completely in the attached .config too. Please have a
> look into REPORTING-BUGS in the kernel source directory. There you'll see,
> disable grsec at all if you're experiencing problems! There you'll also see,
> enable KDB!!
>

I didn't expect grescurity to be active at that stage (kernel boot).

> Please make your and my life easier and read the file and do so. It's
> essential to narrow things down. And again, SuSE has ~30 developers, WOLK has
> me, so if SuSE works and WOLK not, it's bad but 30 vs. 1 is not a thing you
> have to compare ;)

Hey, I'm not complaining - youe are doing great work !! But I need
somthing to see if the hardware is causing the problem or if it's a
software issue.

> P.S.: If you have some spare time, please try v4.0s, then v4.1s and so on and
> see when the problem occurs first, or if v4.0 has the same problems also.

I will be on site at various customers the next few days, so I can't
promise to try every version - but I'll give v4.0 a try.

I will also give a stock 2.4.22 kernel a try - maybe the problem is fixed
there. If necessary, I can wait for WOLK 5 on these SMP systems .......
but I really prefer your work to that of SuSE.

> Thank you very much.

Hey - I have to thank you for your help and patience !!


-- 
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