SMP interrupt problem
Scott Bennett
bennett at cs.niu.edu
Fri Feb 22 12:22:25 UTC 2008
On Fri, 22 Feb 2008 11:38:42 +0000 Rob <fbsdq at kuhl.co.uk> wrote:
>I have a system with two dual core CPUS. I have installed 6.3 release and have
>the SMP kernel running.
>
>FreeBSD 6.3-RELEASE #0: Wed Jan 16 04:45:45 UTC 2008
> root at dessler.cse.buffalo.edu:/usr/obj/usr/src/sys/SMP
>Timecounter "i8254" frequency 1193182 Hz quality 0
>CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2799.22-MHz 686-class CPU)
> Origin = "GenuineIntel" Id = 0xf29 Stepping = 9
>
>Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
> Features2=0x4400<CNXT-ID,xTPR>
> Logical CPUs per core: 2
Actually, the above says you have two *single-core* CPUs with
hyperthreading enabled.
>real memory = 1073676288 (1023 MB)
>avail memory = 1037307904 (989 MB)
>ACPI APIC Table: <A M I OEMAPIC >
>FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
> cpu0 (BSP): APIC ID: 0
> cpu1 (AP): APIC ID: 1
> cpu2 (AP): APIC ID: 6
> cpu3 (AP): APIC ID: 7
>MADT: Forcing active-low polarity and level trigger for SCI
>ioapic0 <Version 2.0> irqs 0-23 on motherboard
>ioapic1 <Version 2.0> irqs 24-47 on motherboard
>ioapic2 <Version 2.0> irqs 48-71 on motherboard
>kbd1 at kbdmux0
>ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
>hptrr: HPT RocketRAID controller driver v1.1 (Jan 16 2008 04:43:12)
>acpi0: <A M I OEMRSDT> on motherboard
>acpi0: Power Button (fixed)
>Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
>acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
>cpu0: <ACPI CPU> on acpi0
>acpi_throttle0: <ACPI CPU Throttling> on cpu0
>cpu1: <ACPI CPU> on acpi0
>cpu2: <ACPI CPU> on acpi0
>cpu3: <ACPI CPU> on acpi0
>pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
>pci0: <ACPI PCI bus> on pcib0
>pcib1: <ACPI PCI-PCI bridge> at device 2.0 on pci0
>pci2: <ACPI PCI bus> on pcib1
>pcib2: <ACPI PCI-PCI bridge> at device 29.0 on pci2
>pci4: <ACPI PCI bus> on pcib2
>..
>..
>..
>Timecounters tick every 1.000 msec
>hptrr: no controller detected.
>ad0: 76319MB <WDC WD800JB-00FSA0 77.07W77> at ata0-master UDMA100
>SMP: AP CPU #1 Launched!
>SMP: AP CPU #2 Launched!
>SMP: AP CPU #3 Launched!
>
>Once it is running it seems to just be busy doing interrupts.
>
>When "idle" top -C -S shows:
>
>last pid: 811; load averages: 1.00, 0.67, 0.31 up 0+00:04:24 07:32:53
>65 processes: 6 running, 43 sleeping, 16 waiting
>CPU states: 0.0% user, 0.0% nice, 0.0% system, 43.6% interrupt, 56.4% idle
>Mem: 7376K Active, 4768K Inact, 18M Wired, 8336K Buf, 963M Free
>Swap: 1024M Total, 1024M Free
>
> PID USERNAME THR PRI NICE SIZE RES STATE C TIME CPU COMMAND
> 13 root 1 171 52 0K 8K RUN 0 3:43 99.02% idle: cpu0
> 23 root 1 -52 -171 0K 8K CPU2 2 2:51 85.11% irq9: acpi0
Have you looked to see which device(s) you have at IRQ 9? Is there some
problem with the device(s)?
> 11 root 1 171 52 0K 8K RUN 2 0:55 12.89% idle: cpu2
> 37 root 1 171 52 0K 8K pgzero 0 0:00 0.00% pagezero
> 15 root 1 -32 -151 0K 8K WAIT 0 0:00 0.00% swi4: clock s
> 0 root 1 96 0 0K 0K WAIT 1 0:00 0.00% swapper
> 4 root 1 -8 0 0K 8K - 0 0:00 0.00% g_down
> 3 root 1 -8 0 0K 8K - 0 0:00 0.00% g_up
>
>If anyone has an idea what the problem is I would be grateful for any advice.
>
You deleted part of the startup messages, so we can't see what you have
at IRQ 9. Go back and look at either dmesg(1) output or /var/log/messages
to find out what device(s) interrupt(s) at IRQ 9. Then check for anything
weird about the device activity.
Scott Bennett, Comm. ASMELG, CFIAG
**********************************************************************
* Internet: bennett at cs.niu.edu *
*--------------------------------------------------------------------*
* "A well regulated and disciplined militia, is at all times a good *
* objection to the introduction of that bane of all free governments *
* -- a standing army." *
* -- Gov. John Hancock, New York Journal, 28 January 1790 *
**********************************************************************
More information about the freebsd-questions
mailing list