Re: Wolk 4.9 smp cpu detection and initialization problems
Marc-Christian Petersen <[email protected]>
| Newsgroups | gmane.linux.wolk.devel |
|---|---|
| Organization | Working Overloaded Linux Kernel |
| Message-ID | <[email protected]> |
On Monday 15 September 2003 16:15, Olaf Unterkofler wrote: Hi Olaf, > Sorry to say, but these buggers still don't play nice. > Here is the current situation: > 1. 4.10-pre5 introduces a few new comile and dependancy errors. They are > also present on my workstation :-( > 2. Kernel built with maxcpus=4 > - boot with vga=0x317:system lockup on framebuffer initialization. > - boot with vga=ask (80x50): a) boot ok > b) only first physical cpu is initialized > c) hwbootscan from SuSE locks the machine > hard > d) Xfree start locks the machine hard > (pci-scan ?) > > - boot with maxcpus=1 and vga=0x317: a) boot ok > b) hwbootscan from SuSE locks the > machine hard > c) Xfree start locks the machine > hard > - boot with acpi=off (BIOS and commandline): same as above, 2 CPUs > recognized (Phys 0 ?), but only one can be initialized. and you are sure anything previous to v4.9s (means v4.8s and lower) worked fine? ciao, Marc ------------------------------------------------------- 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