Re: Sticky IO-APIC problem
"Randy.Dunlap" <[EMAIL PROTECTED]> wrote: >I can't find an Intel BN810E board at intel.com or by searching >at google.com. Are you sure that's the correct name/ID for it? >Do you have any web page references for it? Sorry, it was an Intel CA810E board. (http://www.intel.com/support/motherboards/desktop/ca810e/) -- Colin The CompNerd Network: http://www.compnerd.com/ Where a nerd can be a nerd. Get your free [EMAIL PROTECTED]! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Sticky IO-APIC problem
Randy.Dunlap [EMAIL PROTECTED] wrote: I can't find an Intel BN810E board at intel.com or by searching at google.com. Are you sure that's the correct name/ID for it? Do you have any web page references for it? Sorry, it was an Intel CA810E board. (http://www.intel.com/support/motherboards/desktop/ca810e/) -- Colin The CompNerd Network: http://www.compnerd.com/ Where a nerd can be a nerd. Get your free [EMAIL PROTECTED]! - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Sticky IO-APIC problem
"Randy.Dunlap" <[EMAIL PROTECTED]> wrote: >What mobo (model/name) is it? >Can you give us the output from "lspci -vv"? OK, it's an Intel BN810E Desktop Board; here's the output from lspci -vv: [root@fortytwo /root]# lspci -vv 00:00.0 Host bridge: Intel Corporation 82810E GMCH [Graphics Memory Controller Hub] (rev 03) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- Reset- FastB2B- 00:1f.0 ISA bridge: Intel Corporation 82801AA ISA Bridge (LPC) (rev 02) Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- This shows that Linux mapped the APIC (part of the processor). >It says nothing about mapping any IO APICs (unless you deleted >that part :). Oops, sorry -- misunderstood the meaning of the message. 8-P >So, how does one know if a (UP) system has an IO APIC and that >Linux can be configured to use the UP IO APIC code?... > >(That's a serious question: does an IO APIC show up in lspci output?) > >And why do you think that this system has an IO APIC? >Is it documented to have one? >[just digging for clues] There's no IO-APIC in the lspci output, but that's because it's integrated as part of the i810 chipset; it's probably hidden to keep people from tinkering with the settings -- there's not much one can do to modify an interrupt controller that wouldn't end badly 8=;-) (according to Intel's docs, the IO-APIC's carried somewhere on the 82801AA I/O Controller Hub, and I quote:) >From Intel's 82801AA I/O Controller Hub Datasheet >(http://developer.intel.com/design/chipsets/datashts/29065503.pdf): Features List: (page 3) ... - Interrupt Controller - Two cascaded 82C59 - Integrated IO-APIC capability - 15 Interrupt support in 8259 mode, 24 Interrupt support in IO-APIC mode ... 82801AA Simplified Block Diagram: (page 4) SERIRQ <---> | | PIRQ[A..D]# <--> | | IRQ[14..15] ---> | Interrupt |<--- APICCLK ---> | | APICD[1..0] <--> |___| 82801AA Datasheet Introduction: (page 25) Advanced Programmable Interrupt Controller (APIC) In addition to the standard ISA compatible interrupt controller (PIC) described in the previous section, the ICH incorporates the Advanced Programmable Interrupt Controller (APIC). While the standard interrupt controller is intended for use in a uni-processor system, APIC can be used in either a uni-processor or multi-processor system. Hope this clears up some confusion. -- Colin The CompNerd Network: http://www.compnerd.com/ Where a nerd can be a nerd. Get your free [EMAIL PROTECTED]! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Sticky IO-APIC problem
Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > This shows that Linux mapped the APIC (part of the processor). > It says nothing about mapping any IO APICs (unless you deleted > that part :). > Correct. Linux always enables the APIC, but it needs some bios tables for the IO APIC. And the IO APIC is not present on all uniprocessor motherboards. > So, how does one know if a (UP) system has an IO APIC and that > Linux can be configured to use the UP IO APIC code?... Figure out which ICH is used (lspci?), then check Intel's documentation. But even if an io apic is present, Linux can only use it if a MP table is present. Afaik ACPI tables are not yet supported on i386, but ia64 already supports detecting the IO APIC's based on ACPI tables. -- Manfred - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Sticky IO-APIC problem
Colin Bayer scribed: | I have a Pentium III 933/133 (Coppermine, stepping 6) in an Intel-manufactured | i810 motherboard (hey, I What mobo (model/name) is it? Can you give us the output from "lspci -vv"? | know it's a lame chipset, but it was on sale). On boot, the kernel (version | 2.4.6-pre8) identifies and maps the | IO-APIC onboard, but does not assign any IRQs to it. | | The relevant boot log snippet follows. | | [root@fortytwo i386]# cat /var/log/dmesg | ... | ... | mapped APIC to e000 (0121c000) This shows that Linux mapped the APIC (part of the processor). It says nothing about mapping any IO APICs (unless you deleted that part :). So, how does one know if a (UP) system has an IO APIC and that Linux can be configured to use the UP IO APIC code?... (That's a serious question: does an IO APIC show up in lspci output?) And why do you think that this system has an IO APIC? Is it documented to have one? [just digging for clues] | Kernel command line: auto BOOT_IMAGE=linux-test ro root=307 | BOOT_FILE=/boot/vmlinuz-2.4.6-pre8 | devfs=mount pirq=9,4 | PIRQ redirection, working around broken MP-BIOS. | ... PIRQ0 -> IRQ 9 | ... PIRQ1 -> IRQ 4 | ... | ... | | And /proc/interrupts: | [root@fortytwo i386]# cat /proc/interrupts |CPU0 | 0: 79409 XT-PIC timer | 1: 5911 XT-PIC keyboard | 2: 0 XT-PIC cascade | 4: 990 XT-PIC es1371 | 8: 1 XT-PIC rtc | 9: 26402 XT-PIC usb-uhci, serial | 11: 16473 XT-PIC i810@PCI:0:1:0 | 14: 5152 XT-PIC ide0 | 15: 47 XT-PIC ide1 | NMI: 0 | ERR: 0 | MIS: 0 | [root@fortytwo i386]# | | This problem also occurs when booting without the pirq switch. I've configured | everything the way it's | mentioned in Documentation/i386/IO-APIC.txt, but it doesn't help. Anyway, thx in | advance for the help. ~Randy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Sticky IO-APIC problem
Colin Bayer scribed: | I have a Pentium III 933/133 (Coppermine, stepping 6) in an Intel-manufactured | i810 motherboard (hey, I What mobo (model/name) is it? Can you give us the output from lspci -vv? | know it's a lame chipset, but it was on sale). On boot, the kernel (version | 2.4.6-pre8) identifies and maps the | IO-APIC onboard, but does not assign any IRQs to it. | | The relevant boot log snippet follows. | | [root@fortytwo i386]# cat /var/log/dmesg | ... | ... | mapped APIC to e000 (0121c000) This shows that Linux mapped the APIC (part of the processor). It says nothing about mapping any IO APICs (unless you deleted that part :). So, how does one know if a (UP) system has an IO APIC and that Linux can be configured to use the UP IO APIC code?... (That's a serious question: does an IO APIC show up in lspci output?) And why do you think that this system has an IO APIC? Is it documented to have one? [just digging for clues] | Kernel command line: auto BOOT_IMAGE=linux-test ro root=307 | BOOT_FILE=/boot/vmlinuz-2.4.6-pre8 | devfs=mount pirq=9,4 | PIRQ redirection, working around broken MP-BIOS. | ... PIRQ0 - IRQ 9 | ... PIRQ1 - IRQ 4 | ... | ... | | And /proc/interrupts: | [root@fortytwo i386]# cat /proc/interrupts |CPU0 | 0: 79409 XT-PIC timer | 1: 5911 XT-PIC keyboard | 2: 0 XT-PIC cascade | 4: 990 XT-PIC es1371 | 8: 1 XT-PIC rtc | 9: 26402 XT-PIC usb-uhci, serial | 11: 16473 XT-PIC i810@PCI:0:1:0 | 14: 5152 XT-PIC ide0 | 15: 47 XT-PIC ide1 | NMI: 0 | ERR: 0 | MIS: 0 | [root@fortytwo i386]# | | This problem also occurs when booting without the pirq switch. I've configured | everything the way it's | mentioned in Documentation/i386/IO-APIC.txt, but it doesn't help. Anyway, thx in | advance for the help. ~Randy - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Sticky IO-APIC problem
Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit This shows that Linux mapped the APIC (part of the processor). It says nothing about mapping any IO APICs (unless you deleted that part :). Correct. Linux always enables the APIC, but it needs some bios tables for the IO APIC. And the IO APIC is not present on all uniprocessor motherboards. So, how does one know if a (UP) system has an IO APIC and that Linux can be configured to use the UP IO APIC code?... Figure out which ICH is used (lspci?), then check Intel's documentation. But even if an io apic is present, Linux can only use it if a MP table is present. Afaik ACPI tables are not yet supported on i386, but ia64 already supports detecting the IO APIC's based on ACPI tables. -- Manfred - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Sticky IO-APIC problem
Randy.Dunlap [EMAIL PROTECTED] wrote: What mobo (model/name) is it? Can you give us the output from lspci -vv? OK, it's an Intel BN810E Desktop Board; here's the output from lspci -vv: [root@fortytwo /root]# lspci -vv 00:00.0 Host bridge: Intel Corporation 82810E GMCH [Graphics Memory Controller Hub] (rev 03) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- Latency: 0 00:01.0 VGA compatible controller: Intel Corporation 82810E CGC [Chipset Graphics Controller] (rev 03) (prog-if 00 [VGA]) Subsystem: Intel Corporation: Unknown device 4332 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 Interrupt: pin A routed to IRQ 11 Region 0: Memory at f800 (32-bit, prefetchable) [size=64M] Region 1: Memory at ffa8 (32-bit, non-prefetchable) [size=512K] Capabilities: [dc] Power Management version 1 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:1e.0 PCI bridge: Intel Corporation 82801AA PCI Bridge (rev 02) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=64 I/O behind bridge: d000-dfff Memory behind bridge: ff80-ff8f Prefetchable memory behind bridge: f6a0-f6af BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- Reset- FastB2B- 00:1f.0 ISA bridge: Intel Corporation 82801AA ISA Bridge (LPC) (rev 02) Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 00:1f.1 IDE interface: Intel Corporation 82801AA IDE (rev 02) (prog-if 80 [Master]) Subsystem: Intel Corporation 82801AA IDE Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 Region 4: I/O ports at ffa0 [size=16] 00:1f.2 USB Controller: Intel Corporation 82801AA USB (rev 02) (prog-if 00 [UHCI]) Subsystem: Intel Corporation 82801AA USB Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 Interrupt: pin D routed to IRQ 9 Region 4: I/O ports at ef80 [size=32] 00:1f.3 SMBus: Intel Corporation 82801AA SMBus (rev 02) Subsystem: Intel Corporation 82801AA SMBus Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Interrupt: pin B routed to IRQ 10 Region 4: I/O ports at efa0 [size=16] 01:0a.0 Multimedia audio controller: Ensoniq ES1371 [AudioPCI-97] (rev 09) Subsystem: Ensoniq Creative Sound Blaster AudioPCI64V, AudioPCI128 Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=slow TAbort- TAbort+ MAbort- SERR- PERR- Latency: 64 (3000ns min, 32000ns max) Interrupt: pin A routed to IRQ 4 Region 0: I/O ports at df00 [size=64] Capabilities: [dc] Power Management version 2 Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 01:0b.0 Serial controller: US Robotics/3Com 56K FaxModem Model 5610 (rev 01) (prog-if 02 [16550]) Subsystem: US Robotics/3Com: Unknown device baba Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Interrupt: pin A routed to IRQ 9 Region 0: I/O ports at dff0 [size=8] Capabilities: [dc] Power Management version 2 Flags: PMEClk- DSI- D1- D2+ AuxCurrent=0mA PME(D0+,D1-,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=2 PME- [root@fortytwo /root]# This shows that Linux mapped the APIC (part of the processor). It says nothing about mapping any IO APICs (unless you deleted that part :). Oops,
Sticky IO-APIC problem
'K, here's the deal. I have a Pentium III 933/133 (Coppermine, stepping 6) in an Intel-manufactured i810 motherboard (hey, I know it's a lame chipset, but it was on sale). On boot, the kernel (version 2.4.6-pre8) identifies and maps the IO-APIC onboard, but does not assign any IRQs to it. The relevant boot log snippet follows. [root@fortytwo i386]# cat /var/log/dmesg ... ... mapped APIC to e000 (0121c000) Kernel command line: auto BOOT_IMAGE=linux-test ro root=307 BOOT_FILE=/boot/vmlinuz-2.4.6-pre8 devfs=mount pirq=9,4 PIRQ redirection, working around broken MP-BIOS. ... PIRQ0 -> IRQ 9 ... PIRQ1 -> IRQ 4 ... ... And /proc/interrupts: [root@fortytwo i386]# cat /proc/interrupts CPU0 0: 79409 XT-PIC timer 1: 5911 XT-PIC keyboard 2: 0 XT-PIC cascade 4:990 XT-PIC es1371 8: 1 XT-PIC rtc 9: 26402 XT-PIC usb-uhci, serial 11: 16473 XT-PIC i810@PCI:0:1:0 14: 5152 XT-PIC ide0 15: 47 XT-PIC ide1 NMI: 0 ERR: 0 MIS: 0 [root@fortytwo i386]# This problem also occurs when booting without the pirq switch. I've configured everything the way it's mentioned in Documentation/i386/IO-APIC.txt, but it doesn't help. Anyway, thx in advance for the help. -- Colin The CompNerd Network: http://www.compnerd.com/ Where a nerd can be a nerd. Get your free [EMAIL PROTECTED]! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Sticky IO-APIC problem
'K, here's the deal. I have a Pentium III 933/133 (Coppermine, stepping 6) in an Intel-manufactured i810 motherboard (hey, I know it's a lame chipset, but it was on sale). On boot, the kernel (version 2.4.6-pre8) identifies and maps the IO-APIC onboard, but does not assign any IRQs to it. The relevant boot log snippet follows. [root@fortytwo i386]# cat /var/log/dmesg ... ... mapped APIC to e000 (0121c000) Kernel command line: auto BOOT_IMAGE=linux-test ro root=307 BOOT_FILE=/boot/vmlinuz-2.4.6-pre8 devfs=mount pirq=9,4 PIRQ redirection, working around broken MP-BIOS. ... PIRQ0 - IRQ 9 ... PIRQ1 - IRQ 4 ... ... And /proc/interrupts: [root@fortytwo i386]# cat /proc/interrupts CPU0 0: 79409 XT-PIC timer 1: 5911 XT-PIC keyboard 2: 0 XT-PIC cascade 4:990 XT-PIC es1371 8: 1 XT-PIC rtc 9: 26402 XT-PIC usb-uhci, serial 11: 16473 XT-PIC i810@PCI:0:1:0 14: 5152 XT-PIC ide0 15: 47 XT-PIC ide1 NMI: 0 ERR: 0 MIS: 0 [root@fortytwo i386]# This problem also occurs when booting without the pirq switch. I've configured everything the way it's mentioned in Documentation/i386/IO-APIC.txt, but it doesn't help. Anyway, thx in advance for the help. -- Colin The CompNerd Network: http://www.compnerd.com/ Where a nerd can be a nerd. Get your free [EMAIL PROTECTED]! - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
