Bug 9445 - CPU falis APIC tests - Gigabyte P35-DQ6 + Intel Core 2 Quad Q6700
Summary: CPU falis APIC tests - Gigabyte P35-DQ6 + Intel Core 2 Quad Q6700
Status: REJECTED INSUFFICIENT_DATA
Alias: None
Product: ACPI
Classification: Unclassified
Component: Config-Interrupts (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: ykzhao
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-11-23 17:13 UTC by Brandon Ros
Modified: 2008-02-18 07:03 UTC (History)
2 users (show)

See Also:
Kernel Version: 2.6.23.8
Subsystem:
Regression: ---
Bisected commit-id:


Attachments

Description Brandon Ros 2007-11-23 17:13:22 UTC
Most recent kernel where this bug did not occur: Unkown.
Distribution: All.
Hardware Environment: Gigabyte P35-DQ6 F7b BIOs, 2GB DDR2-1066 5-5-5-15, PCI-E 16x 8800GTS 640mb, Intel Core 2 Quad Q6700
Software Environment: None, upon kernel initilization.
Problem Description: The motherboard specifications on the website claims to have ACPI 1.0b. Upon a kernel boot, the CPU fails APIC tests.

Steps to reproduce: Have a kernel attempt to initilalize.
Comment 1 Len Brown 2007-11-26 21:41:38 UTC
APIC - Advanced Programmable Interrupt Controller
is different from
ACPI - Advanced Configuration and Powermanagement Interface

Though sometimes the later is needed to properly configure the former,
sometimes the APIC can also be enumerated by MPS (Multi-processor Spec).

do you still have this problem when you try to boot with "acpi=off"?

Are there any BIOS options related to the IO-APIC?
What if you boot with "noapic" or "nolapic"?
Comment 2 Brandon Ros 2007-11-30 19:36:03 UTC
The problem is APIC related, not APCI, sorry.
The APIC problems happen when trying to initiate the 4 cores of my 1
processor.
I will try downgrading BIOs.
Then I will try boot options.

On Nov 27, 2007 12:41 AM, <bugme-daemon@bugzilla.kernel.org> wrote:

> http://bugzilla.kernel.org/show_bug.cgi?id=9445
>
>
> len.brown@intel.com changed:
>
>           What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>                 CC|                            |acpi-
>                   |                            |bugzilla@
> lists.sourceforge.n
>                   |                            |et
>          Component|BIOS                        |Config-Interrupts
>            Summary|Gigabyte P35-DQ6 + Intel    |CPU falis APIC tests -
>                   |Core 2 Quad Q6700           |Gigabyte P35-DQ6 + Intel
>                   |                            |Core 2 Quad Q6700
>
>
>
>
> ------- Comment #1 from len.brown@intel.com  2007-11-26 21:41 -------
> APIC - Advanced Programmable Interrupt Controller
> is different from
> ACPI - Advanced Configuration and Powermanagement Interface
>
> Though sometimes the later is needed to properly configure the former,
> sometimes the APIC can also be enumerated by MPS (Multi-processor Spec).
>
> do you still have this problem when you try to boot with "acpi=off"?
>
> Are there any BIOS options related to the IO-APIC?
> What if you boot with "noapic" or "nolapic"?
>
>
> --
> Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
>
The problem is APIC related, not APCI, sorry.<br>The APIC problems happen when trying to initiate the 4 cores of my 1 processor.<br>I will try downgrading BIOs.<br>Then I will try boot options.<br><br><div class="gmail_quote">
On Nov 27, 2007 12:41 AM,  &lt;<a href="mailto:bugme-daemon@bugzilla.kernel.org">bugme-daemon@bugzilla.kernel.org</a>&gt; wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<a href="http://bugzilla.kernel.org/show_bug.cgi?id=9445" target="_blank">http://bugzilla.kernel.org/show_bug.cgi?id=9445</a><br><br><br><a href="mailto:len.brown@intel.com">len.brown@intel.com</a> changed:<br><br> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; What &nbsp; &nbsp;|Removed &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |Added
<br>----------------------------------------------------------------------------<br> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; CC| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|acpi-<br> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|bugzilla@lists.sourceforge.n<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|et<br> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Component|BIOS &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|Config-Interrupts<br> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Summary|Gigabyte P35-DQ6 + Intel &nbsp; &nbsp;|CPU falis APIC tests -<br> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |Core 2 Quad Q6700 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |Gigabyte P35-DQ6 + Intel
<br> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|Core 2 Quad Q6700<br><br><br><br><br>------- Comment #1 from <a href="mailto:len.brown@intel.com">len.brown@intel.com</a> &nbsp;2007-11-26 21:41 -------<br>APIC - Advanced Programmable Interrupt Controller
<br>is different from<br>ACPI - Advanced Configuration and Powermanagement Interface<br><br>Though sometimes the later is needed to properly configure the former,<br>sometimes the APIC can also be enumerated by MPS (Multi-processor Spec).
<br><br>do you still have this problem when you try to boot with &quot;acpi=off&quot;?<br><br>Are there any BIOS options related to the IO-APIC?<br>What if you boot with &quot;noapic&quot; or &quot;nolapic&quot;?<br><font color="#888888">
<br><br>--<br>Configure bugmail: <a href="http://bugzilla.kernel.org/userprefs.cgi?tab=email" target="_blank">http://bugzilla.kernel.org/userprefs.cgi?tab=email</a><br>------- You are receiving this mail because: -------<br>
You reported the bug, or are watching the reporter.<br></font></blockquote></div><br>
Comment 3 Fu Michael 2007-12-03 01:18:46 UTC
please attach necessary info:

1) dmesg output
2) acpidump output
3) lspci -vvxxx
Comment 4 ykzhao 2007-12-14 00:47:07 UTC
Please attach the acpidump output.
Please set CONFIG_ACPI_DEBUG and attach the dmesg output with apic=debug
Comment 5 Brandon Ros 2007-12-14 15:39:22 UTC
I apologize for the delay.
Could someone please provide me with a way to test the latest Linux kernel (being able to set boot flags) with no installation of Linux?

I will try and find the time to install Linux and give all output of anything needed.
Comment 6 Len Brown 2007-12-28 22:05:51 UTC
how was the original APIC failure observed,
did you boot a Linux installation CDROM or something?
if yes, you should have the opportunity to add kernel
boot parameters (such as "acpi=off") to the boot cmdline
before the kernel is launched.  Sometimes there is
a window for them, and sometimes you get a GRUB
menu, where you need to type "e" to edit a boot entry
on the menu and "b" to boot it when done.

Can you describe the failure in more detail --
screen capture, console log, or specific error
messages or error behavior.

Is windows or some other OS currently running properly
on this system?  Does it see and use all the CPUs?
What is its interrupt configuration?

please don't reply to this message with an HTML message.
If your mailer has no option, then please go to the web
page and type your comments directly into the bug report.
Comment 7 Brandon Ros 2007-12-30 19:02:41 UTC
Mac OS X 86 10.5.1 Leopard uses ACPI just fine.
Windows Vista uses ACPI just fine.
This is all on another hard drive.

I will use gentoo LiveCD to boot.
Comment 8 ykzhao 2008-02-18 07:03:40 UTC
Since there is no response for two months, the bug will be rejected.
If the problem still exists, please reopen it.
Thanks. 

Note You need to log in before you can comment on or make changes to this bug.