From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Randy.Dunlap" Subject: Re: An unexpected IO-APIC was found Date: Fri, 11 Jul 2003 13:43:48 -0700 Sender: linux-smp-owner@vger.kernel.org Message-ID: <20030711134348.098dabbd.rddunlap@osdl.org> References: <20030711174300.52EFB40042@papaya> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Id: Content-Type: text/plain; charset="us-ascii" To: Gerbrand Oudenaarden Cc: linux-smp@vger.kernel.org On Fri, 11 Jul 2003 18:16:22 +0200 Gerbrand Oudenaarden wrote: | Hi, | | dmesg asked me to send a message to this address. | | My configuration: | | Supermicro P4SCA Mainboard | Single Pentium 4 2,8 GHz Processor | 3 * 512 MB SDRAM DDR 400 | 4 * 200 GB Maxtor harddisks on Promise TX2000 IDE Raid card | 1 * 3 GB Compaq IDE harddisk on mainboard IDE controller | | | I have the following problem: a few minutes after booting up with this | custom-compiled 2.4.21 kernel, the system freezes. | | Oops: unable to handle kernel NULL pointer dereference at virtual address | 00000000 | [...] | Kernel Panic | | I disabled hyperthreading in the BIOS. When I enable hyperthreading, I am | getting the same message. | | hope this contributes to something. | | ------ Forwarded Message | From: root@papaya.engagetv.com (root) | Date: Fri, 11 Jul 2003 19:43:00 +0200 (CEST) | To: undisclosed-recipients: ; | | Linux version 2.4.21 (root@papaya) (gcc version 3.3.1 20030626 (Debian | prerelease)) #5 Fri Jul 11 19:10:24 CEST 2003 ... | testing the IO APIC....................... | | IO APIC #2...... | .... register #00: 02000000 | ....... : physical APIC id: 02 | ....... : Delivery Type: 0 | ....... : LTS : 0 | .... register #01: 00178020 | ....... : max redirection entries: 0017 | ....... : PRQ implemented: 1 | ....... : IO APIC version: 0020 | .... register #02: 00178020 | ....... : arbitration: 00 | An unexpected IO-APIC was found. If this kernel release is less than | three months old please report this to linux-smp@vger.kernel.org Hi, This unexpected IO APIC has already been fixed. If you want someone to address the kernel panic (above), please send the full Oops/panic message text. -- ~Randy