ACPI

http://bugzilla.kernel.org/show_bug.cgi?id=5768





------- Additional Comments From rcrocomb@...  2005-12-21 13:44 -------
Created an attachment (id=6874)
 --> (http://bugzilla.kernel.org/attachment.cgi?id=6874&action=view)
dmesg of 2.6.15-rc6 with acpi=on (default)


------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.kernel.org/show_bug.cgi?id=5768





------- Additional Comments From rcrocomb@...  2005-12-21 13:45 -------
Created an attachment (id=6875)
 --> (http://bugzilla.kernel.org/attachment.cgi?id=6875&action=view)
lspci -vvv of 2.6.15-rc6 with acpi=off


------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.kernel.org/show_bug.cgi?id=5768





------- Additional Comments From rcrocomb@...  2005-12-21 13:45 -------
Created an attachment (id=6876)
 --> (http://bugzilla.kernel.org/attachment.cgi?id=6876&action=view)
lspci -vvv of 2.6.15-rc6 with acpi=on (default)


------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.kernel.org/show_bug.cgi?id=5757





------- Additional Comments From trilight@...  2005-12-21 04:21 -------
Thanks for looking into this btw !

I already attached the dmesg of a working kernel, even 2 working kernels, 2.4.32
without acpi support and noapic, and 2.6.14.4 with acpi + apic support, please
check the previous attachment. (they're in the dmesg file)

So this is what i could note from my monitor just before the reboot occurs:

Booting processor 1/1 eip 2000 
Not responding
Inquiring remote APIC #6
... APIC #1 ID: FAILED
... APIC #1 VERSION: FAILED
... APIC #1 SPIV: FAILED
CPU #1 not responding - cannot use it
Booting processor 1/6 eip 2000
Not responding
... APIC #6 ID: FAILED
... APIC #6 VERSION: FAILED
... APIC #6 SPIV: FAILED
CPU #6 not responding - cannot use it
Booting processor 1/7 eip 2000
NOt responding
... APIC #7 ID: FAILED
... APIC #7 VERSION: FAILED
... APIC #7 SPIV: FAILED
CPU #7 not responding - cannot use it

btw, i noticed when i used acpi=debug the system kept rebooting, even after 17
reboots it did not continue. So i didn't use acpi=debug and now it booted after
3 reboots. So this is also something which we need to look at i guess.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.kernel.org/show_bug.cgi?id=5757





------- Additional Comments From trilight@...  2005-12-21 04:42 -------
I also tried a few days ago to change a bit of code in smpboot.c according to
the following:

     /*
                 * allow APs to start initializing.
                 */
                Dprintk("Before Callout %d.\n", cpu);
                cpu_set(cpu, cpu_callout_map);
                Dprintk("After Callout %d.\n", cpu);

                /*
                 * Wait 5s total for a response
                 */
                for (timeout = 0; timeout < 50000; timeout++) {
                        if (cpu_isset(cpu, cpu_callin_map))
--------------------------> cpu_online_map
                                break; /* It has booted */
                        udelay(100);
                }

                if (cpu_isset(cpu, cpu_callin_map)) {
--------------------------------> cpu_online_map
                        /* number CPUs logically, starting from 1 (BSP is 0)
*/
                        Dprintk("CPU has booted.\n");
                } else {
                        boot_error = 1;
                        if (*((volatile unsigned char
*)phys_to_virt(SMP_TRAMPOLINE_BASE))
                                        == 0xA5)
                                /* trampoline started but...? */
                                printk("Stuck ??\n");
                        else
                                /* trampoline code not run */
                                printk("Not responding.\n");
#if APIC_DEBUG
                        inquire_remote_apic(apicid);
#endif
                } 



I replaced cpu_callin_map to cpu_online_map, this caused the system not reboot
but show various crashes and continue with the first cpu to boot.


I got it from this link:

http://groups.google.com/group/linux.kernel/browse_frm/thread/ee892bb3680aa46f/58194aedd45afe9b?tvc=1#58194aedd45afe9b


although it was meant for a 64bit system it did at least something.


------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.kernel.org/show_bug.cgi?id=5757





------- Additional Comments From trilight@...  2005-12-21 05:02 -------
When it finished booting, i did a cat /proc/cpuinfo and i see only 1 cpu with
the previous change in smpboot.c. When i do cat /proc/interrupts then i see 4
cpu's but only 1 handling interrupts and the rest has 0.


------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.kernel.org/show_bug.cgi?id=5757





------- Additional Comments From trilight@...  2005-12-21 05:10 -------
I have to correct myself, it seems after a few reboots that even with the change
in smpboot.c it still reboots sometimes and not finishing boot.

the only way now is with acpi=off noapic to get a normal boot.


------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.kernel.org/show_bug.cgi?id=3410





------- Additional Comments From trenn@...  2005-12-21 01:33 -------
Created an attachment (id=6869)
 --> (http://bugzilla.kernel.org/attachment.cgi?id=6869&action=view)
Return value invertion prevents cpufreq cooling in passive cooling mode


------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.