Re: PII SMP system hangs during boot with ACPI enabled
On Tue, 25 Nov 2003, John Polstra wrote: On 24-Nov-2003 Nate Lawson wrote: Please also send the output of acpidump -t -d jdp-P2.asl I booted the 5.1R live CD in an attempt to get this output. I discovered that the machine hangs the same way with 5.1R as it does with -current. (When I originally installed 5.1R, the machine had an older, non-ACPI BIOS.) I've attached the verbose boot messages from 5.1R, in case that's worth anything. Such a shame -- it gets within a hair's breadth of running init, but it just can't quite make it all the way there. Would you try this patch? http://people.freebsd.org/~jhb/patches/acpi_sci.patch -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: PII SMP system hangs during boot with ACPI enabled
On 23-Nov-2003 John Polstra wrote: I have an old dual PII/400 system that I'm trying to set up as a -current scratchbox. The motherboard is a Tyan S1836DLUAN with the Intel 440BX chipset. I upgraded the BIOS to the latest from Tyan's web site. It is supposed to support ACPI. I'm using -current from around noon Pacific time, November 23 (today). The system boots and runs fine if I disable ACPI either in loader.conf or in the BIOS, but if ACPI is enabled it hangs fairly late in the boot, right after these messages: lo0: bpf attached acpi_cpu0: set speed to 100.0% acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0% It's not a totally solid hang. For instance, the scroll lock key works and allows me to scroll forward and backward through the syscons output. I've attached the verbose boot messages. Is this system Just Too Old? Try http://www.FreeBSD.org/~jhb/patches/acpi_irq.patch -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PII SMP system hangs during boot with ACPI enabled
Nate Lawson writes: No way! Good (non-386) equipment is never to old. :) Please add debug.acpi.disable=cpu to loader.conf or type that in at the loader prompt. If it boots ok, we'll have to debug the acpi_cpu_startup path. Speaking of which, I have a Good (see above...) motherboard looking for a worthy home. It's a dual 266MHZ processor PII motherboard (Supermicro P6DLE) with 256MB of ram. It was running just fine when I removed it from it's case (I upgraded that box to a 370DLE). It's been comfortably running -stable for a long time, and deserves a good home. Some info is available at: http://www.supermicro.com/PRODUCT/MotherBoards/440LX/p6dle.htm It's free to anyone who can convince me that they'll give it a good home. g. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PII SMP system hangs during boot with ACPI enabled
On 29-Nov-2003 George Hartzell wrote: Speaking of which, I have a Good (see above...) motherboard looking for a worthy home. There's an alias [EMAIL PROTECTED] just for such offers. :-) John ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PII SMP system hangs during boot with ACPI enabled
On 24-Nov-2003 Nate Lawson wrote: Please also send the output of acpidump -t -d jdp-P2.asl I booted the 5.1R live CD in an attempt to get this output. I discovered that the machine hangs the same way with 5.1R as it does with -current. (When I originally installed 5.1R, the machine had an older, non-ACPI BIOS.) I've attached the verbose boot messages from 5.1R, in case that's worth anything. Such a shame -- it gets within a hair's breadth of running init, but it just can't quite make it all the way there. John SMAP type=01 base= len=0009fc00 SMAP type=02 base=0009fc00 len=0400 SMAP type=02 base=000e len=0002 SMAP type=01 base=0010 len=0fee SMAP type=03 base=0ffe len=00018000 SMAP type=04 base=0fff8000 len=8000 SMAP type=02 base=fec0 len=1000 SMAP type=02 base=fee0 len=1000 SMAP type=02 base=fffc len=0004 Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.1-RELEASE #0: Mon Jun 9 19:20:51 GMT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel /boot/kernel/kernel at 0xc0b0c000. Preloaded mfs_root /boot/mfsroot at 0xc0b0c250. Preloaded elf module /boot/kernel/acpi.ko at 0xc0b0c294. Calibrating clock(s) ... i8254 clock: 1193040 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter i8254 frequency 1193182 Hz Calibrating TSC clock ... TSC clock: 400910451 Hz Timecounter TSC frequency 400910451 Hz CPU: Pentium II/Pentium II Xeon/Celeron (400.91-MHz 686-class CPU) Origin = GenuineIntel Id = 0x652 Stepping = 2 Features=0x183fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CM OV,PAT,PSE36,MMX,FXSR real memory = 268304384 (255 MB) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x00b33000 - 0x0fb39fff, 251686912 bytes (61447 pages) avail memory = 248926208 (237 MB) bios32: Found BIOS32 Service Directory header at 0xc00fdb40 bios32: Entry = 0xfdb50 (c00fdb50) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf+0xdb71 pnpbios: Found PnP BIOS data at 0xc00f72c0 pnpbios: Entry = f:6964 Rev = 1.0 Other BIOS signatures found: wlan: 802.11 Link Layer null: null device, zero device random: entropy source mem: memory I/O Pentium Pro MTRR support enabled md0: Preloaded image /boot/mfsroot 4423680 bytes at 0xc06877a4 npx0: math processor on motherboard npx0: INT 16 interface acpi0: TYANCP TYANTBLE on motherboard ACPI-1287: *** Error: Method execution failed [\_SB_.PCI0.SBRG.PS2M._STA] (N ode 0xc12a11a0), AE_AML_REGION_LIMIT ACPI-0175: *** Error: Method execution failed [\_SB_.PCI0.SBRG.PS2M._STA] (N ode 0xc12a11a0), AE_AML_REGION_LIMIT pci_open(1):mode 1 addr port (0x0cf8) is 0x805c pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=71908086) pcibios: BIOS version 2.10 AcpiOsDerivePciId: bus 0 dev 7 func 0 acpi0: power button is handled as a fixed feature programming model. ACPI timer looks BAD min = 2, max = 5, width = 3 ACPI timer looks BAD min = 2, max = 6, width = 4 ACPI timer looks BAD min = 2, max = 5, width = 3 ACPI timer looks BAD min = 2, max = 5, width = 3 ACPI timer looks BAD min = 2, max = 6, width = 4 ACPI timer looks BAD min = 2, max = 5, width = 3 ACPI timer looks BAD min = 2, max = 5, width = 3 ACPI timer looks BAD min = 2, max = 5, width = 3 ACPI timer looks BAD min = 2, max = 5, width = 3 ACPI timer looks BAD min = 2, max = 5, width = 3 Timecounter ACPI-safe frequency 3579545 Hz AcpiOsDerivePciId: bus 0 dev 0 func 0 AcpiOsDerivePciId: bus 0 dev 0 func 0 AcpiOsDerivePciId: bus 0 dev 7 func 0 ACPI-1287: *** Error: Method execution failed [\_SB_.PCI0.SBRG.PS2M._STA] (N ode 0xc12a11a0), AE_AML_REGION_LIMIT ACPI-0175: *** Error: Method execution failed [\_SB_.PCI0.SBRG.PS2M._STA] (N ode 0xc12a11a0), AE_AML_REGION_LIMIT acpi_timer0: 24-bit timer at 3.579545MHz port 0x408-0x40b on acpi0 acpi_cpu0: CPU on acpi0 acpi_cpu1: CPU on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 initial configuration \_SB_.LNKA irq 10: [ 3 4 5 6 7 9 10 11 12 14 15] 0.1.0 \_SB_.LNKB irq 9: [ 3 4 5 6 7 9 10 11 12 14 15] 0.1.1 \_SB_.LNKD irq 11: [ 3 4 5 6 7 9 10 11 12 14 15] 0.7.3 \_SB_.LNKA irq 10: [ 3 4 5 6 7 9 10 11 12 14 15] 0.19.0 \_SB_.LNKB irq 9: [ 3 4 5 6 7 9 10 11 12 14 15] 0.19.1 \_SB_.LNKC irq 0: [ 3 4 5 6 7 9 10 11 12 14 15] 0.19.2 \_SB_.LNKD irq 11: [ 3 4 5 6 7 9 10 11 12 14 15] 0.19.3 \_SB_.LNKB irq 9: [ 3 4 5 6 7 9 10 11 12 14 15] 0.20.0 \_SB_.LNKC irq 0: [ 3 4 5 6 7 9 10 11 12 14 15] 0.20.1 \_SB_.LNKD irq 11: [ 3 4
Re: PII SMP system hangs during boot with ACPI enabled
On 24-Nov-2003 Nate Lawson wrote: Please add debug.acpi.disable=cpu to loader.conf or type that in at the loader prompt. If it boots ok, we'll have to debug the acpi_cpu_startup path. Thanks. It still hangs even with debug.acpi.disable=cpu. I have attached the verbose boot messages. They are essentially the same as the previous messages, except that the acpi_cpu messages are gone now as expected. If there's anything else I should try, just let me know. John SMAP type=01 base= len=0009fc00 SMAP type=02 base=0009fc00 len=0400 SMAP type=02 base=000e len=0002 SMAP type=01 base=0010 len=0fee SMAP type=03 base=0ffe len=00018000 SMAP type=04 base=0fff8000 len=8000 SMAP type=02 base=fec0 len=1000 SMAP type=02 base=fee0 len=1000 SMAP type=02 base=fffc len=0004 Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.2-BETA #1: Sun Nov 23 13:32:22 PST 2003 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/VASHON Preloaded elf kernel /boot/kernel/kernel at 0xc07bc000. ACPI APIC Table: TYANCP TYANTBLE Calibrating clock(s) ... i8254 clock: 1193039 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter i8254 frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 400911753 Hz CPU: Pentium II/Pentium II Xeon/Celeron (400.91-MHz 686-class CPU) Origin = GenuineIntel Id = 0x652 Stepping = 2 Features=0x183fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CM OV,PAT,PSE36,MMX,FXSR real memory = 268304384 (255 MB) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x0010 - 0x003f, 3145728 bytes (768 pages) 0x00829000 - 0x0fb39fff, 254873600 bytes (62225 pages) avail memory = 255262720 (243 MB) APIC ID: physical 0, logical 0:0 APIC ID: physical 1, logical 0:1 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 bios32: Found BIOS32 Service Directory header at 0xc00fdb40 bios32: Entry = 0xfdb50 (c00fdb50) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf+0xdb71 pnpbios: Found PnP BIOS data at 0xc00f72c0 pnpbios: Entry = f:6964 Rev = 1.0 Other BIOS signatures found: APIC: CPU 0 has ACPI ID 1 APIC: CPU 1 has ACPI ID 2 MADT: Found IO APIC ID 2, Vector 0 at 0xfec0 ioapic0: intpin 0 - ExtINT (edge, activehi) ioapic0: intpin 1 - irq 1 (edge, activehi) ioapic0: intpin 2 - irq 2 (edge, activehi) ioapic0: intpin 3 - irq 3 (edge, activehi) ioapic0: intpin 4 - irq 4 (edge, activehi) ioapic0: intpin 5 - irq 5 (edge, activehi) ioapic0: intpin 6 - irq 6 (edge, activehi) ioapic0: intpin 7 - irq 7 (edge, activehi) ioapic0: intpin 8 - irq 8 (edge, activehi) ioapic0: intpin 9 - irq 9 (edge, activehi) ioapic0: intpin 10 - irq 10 (edge, activehi) ioapic0: intpin 11 - irq 11 (edge, activehi) ioapic0: intpin 12 - irq 12 (edge, activehi) ioapic0: intpin 13 - irq 13 (edge, activehi) ioapic0: intpin 14 - irq 14 (edge, activehi) ioapic0: intpin 15 - irq 15 (edge, activehi) ioapic0: intpin 16 - irq 16 (level, activelo) ioapic0: intpin 17 - irq 17 (level, activelo) ioapic0: intpin 18 - irq 18 (level, activelo) ioapic0: intpin 19 - irq 19 (level, activelo) ioapic0: intpin 20 - irq 20 (level, activelo) ioapic0: intpin 21 - irq 21 (level, activelo) ioapic0: intpin 22 - irq 22 (level, activelo) ioapic0: intpin 23 - irq 23 (level, activelo) MADT: intr override: source 0, irq 2 ioapic0: Routing IRQ 0 - intpin 2 ioapic0: intpin 2 trigger: edge ioapic0: intpin 2 polarity: active-hi MADT: intr override: source 9, irq 20 ioapic0: intpin 9 disabled ioapic0: intpin 20 trigger: level ioapic0: intpin 20 polarity: active-hi ioapic0 Version 1.1 irqs 0-23 on motherboard cpu0 BSP: ID: 0x VER: 0x00040011 LDR: 0x0100 DFR: 0x0fff lint0: 0x00010700 lint1: 0x0400 TPR: 0x SVR: 0x01ff null: null device, zero device random: entropy source mem: memory I/O Pentium Pro MTRR support enabled acpi0: TYANCP TYANTBLE on motherboard acpi0: Overriding SCI Interrupt from IRQ 9 to IRQ 20 pci_open(1):mode 1 addr port (0x0cf8) is 0x805c pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=71908086) pcibios: BIOS version 2.10 AcpiOsDerivePciId: bus 0 dev 7 func 0 acpi0: Power Button (fixed) ACPI timer looks BAD min = 2, max = 5, width = 3 ACPI timer looks BAD min = 2, max = 5, width = 3 ACPI timer looks BAD min = 2, max = 5, width = 3 ACPI timer looks BAD min = 2, max = 6, width = 4 ACPI timer looks BAD min = 2, max = 6, width = 4 ACPI timer looks BAD min = 2, max = 5, width = 3 ACPI timer looks BAD min = 2, max = 6, width = 4 ACPI timer
Re: PII SMP system hangs during boot with ACPI enabled
On Mon, 24 Nov 2003, John Polstra wrote: On 24-Nov-2003 Nate Lawson wrote: Please add debug.acpi.disable=cpu to loader.conf or type that in at the loader prompt. If it boots ok, we'll have to debug the acpi_cpu_startup path. Thanks. It still hangs even with debug.acpi.disable=cpu. I have attached the verbose boot messages. They are essentially the same as the previous messages, except that the acpi_cpu messages are gone now as expected. Ok, that indicates that it's not the acpi_cpu changes. If there's anything else I should try, just let me know. Please also send the output of acpidump -t -d jdp-P2.asl If you can break to the debugger after it has hung, a tr would be nice. -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PII SMP system hangs during boot with ACPI enabled
On Mon, 24 Nov 2003, John Polstra wrote: On 24-Nov-2003 Nate Lawson wrote: Please add debug.acpi.disable=cpu to loader.conf or type that in at the loader prompt. If it boots ok, we'll have to debug the acpi_cpu_startup path. Thanks. It still hangs even with debug.acpi.disable=cpu. I have attached the verbose boot messages. They are essentially the same as the previous messages, except that the acpi_cpu messages are gone now as expected. If there's anything else I should try, just let me know. It's a long shot, but what about setting kern.timecounter.hardware to i8254. It appears your ACPI timer is bad. The reason why I suggest this is that it seems like interrupts are being lost. -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PII SMP system hangs during boot with ACPI enabled
On 24-Nov-2003 Nate Lawson wrote: Please also send the output of acpidump -t -d jdp-P2.asl When I try to run that command, I get: acpidump: sysctl machdep.acpi_root does not point to RSDP The sysctl command shows that machdep.acpi_root is 0. Remember, though, in order to boot it I had to disable ACPI in /boot/loader.conf. If you can break to the debugger after it has hung, a tr would be nice. The fact that it didn't occur to me to try that says a lot about how long I've been away from -current. :-( I've attached traces from two different boots. They seem to vary somewhat. I can supply line numbers on request. John db trace siointr1(c298d000,0,c06c9bb7,6a0,cdb64a04) at siointr1+0xec siointr(c298d000,c06a7546,c070bf40,c2944100,4) at siointr+0x35 intr_execute_handlers(c129f88c,cdb64a1c,cdb64a64,c065ca63,34) at intr_execute_ha ndlers+0xc8 lapic_handle_intr(34) at lapic_handle_intr+0x3a Xapic_isr1() at Xapic_isr1+0x33 --- interrupt, eip = 0xc053b9a4, esp = 0xcdb64a60, ebp = 0xcdb64a64 --- wakeup(c2944100,0,c06a7546,140,6c) at wakeup+0x4 AcpiOsSignalSemaphore(c2944100,1) at AcpiOsSignalSemaphore+0xa8 AcpiUtReleaseMutex(9,30,c295e8c0,c295e760,cdb64acc) at AcpiUtReleaseMutex+0x8c AcpiUtReleaseToCache(3,c295e760,cdb64ad8,c045ac17,c295e760) at AcpiUtReleaseToCa che+0x8c AcpiPsFreeOp(c295e760,cdb64afc,c045ab37,c12a0800,0) at AcpiPsFreeOp+0x30 AcpiPsDeleteCompletedOp(c12a0800,0,c12a0800,c295e7c0,c12a0800) at AcpiPsDeleteCo mpletedOp+0x17 AcpiPsGetNextWalkOp(c12a0800,c295e760,c045ac00,c2967080,c295e8c0) at AcpiPsGetNe xtWalkOp+0x77 AcpiPsDeleteParseTree(c295e8c0,c12a0c00,c12a0de4,0,cdb64bf4) at AcpiPsDeletePars eTree+0x9a AcpiPsCompleteThisOp(c12a0c00,c295e8c0,0,c12a0c10,150) at AcpiPsCompleteThisOp+0 x1b8 AcpiPsParseLoop(c12a0c00,c2967340,cdb64c14,c12a0c00,c12a0de4) at AcpiPsParseLoop +0x6c8 AcpiPsParseAml(c12a0c00,c2967380,c295ca80,ce5b5ac0,d) at AcpiPsParseAml+0x7c AcpiPsxExecute(c295ca80,0,cdb64c9c,c295ca80,0) at AcpiPsxExecute+0x202 AcpiNsExecuteControlMethod(c295ca80,0,cdb64c9c,c2944180,c294dedc) at AcpiNsExecu teControlMethod+0x5f AcpiNsEvaluateByHandle(c295ca80,0,0,76,c295ca80) at AcpiNsEvaluateByHandle+0x96 AcpiEvAsynchExecuteGpeMethod(c294dedc,0,c06a7461,7b,0) at AcpiEvAsynchExecuteGpe Method+0x8c acpi_task_thread(0,cdb64d48,c06b7385,311,5f616964) at acpi_task_thread+0x105 fork_exit(c0474e20,0,cdb64d48) at fork_exit+0xb4 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xcdb64d7c, ebp = 0 --- db c ~Stopped at siointr1+0xec: jmp siointr1+0x220 db show all procs pid proc uarea uid ppid pgrp flag stat wmesgwchan cmd 48 c299a8d4 d26330000 0 0 204 [IWAIT] swi0: tty:sio 47 c28f0a98 ce57a0000 0 0 204 new [RUNQ] usbtask 46 c28f0c5c ce57b0000 0 0 204 new [RUNQ] usb0 8 c28f0e20 ce57c0000 0 0 204 new [RUNQ] acpi_task2 7 c2935000 ce57d0000 0 0 204 new [RUNQ] acpi_task1 6 c29351c4 ce57e0000 0 0 204 [CPU 0] acpi_task0 45 c2935388 ce57f0000 0 0 204 [IWAIT] swi7: acpitaskq 44 c293554c ce580 0 0 204 new [IWAIT] swi3: cambio 43 c2935710 ce5810000 0 0 204 new [IWAIT] swi2: camnet 42 c29358d4 ce5820000 0 0 204 new [IWAIT] swi5:+ 5 c2935a98 ce5830000 0 0 204 [SLP]tqthr 0xc070f268] taskqueu e 41 c2935c5c ce5a80000 0 0 204 new [IWAIT] swi6:+ 40 c2935e20 ce5a90000 0 0 204 [IWAIT] swi7: task queue 39 c2937000 ce5aa0000 0 0 204 [RUNQ] random 4 c28e154c ce54a0000 0 0 204 [RUNQ] g_down 3 c28e1710 ce54b0000 0 0 204 [RUNQ] g_up 2 c28e18d4 ce54c0000 0 0 204 [RUNQ] g_event 38 c28e1a98 ce54d0000 0 0 204 new [IWAIT] swi4: vm 37 c28e1c5c ce54e0000 0 0 20c [IWAIT] swi8: tty:sio clock 36 c28e1e20 ce54f0000 0 0 204 new [IWAIT] swi1: net 35 c28f ce550 0 0 204 new [IWAIT] irq9: 34 c28f01c4 ce5750000 0 0 204 new [IWAIT] irq0: clk 33 c28f0388 ce5760000 0 0 204 new [IWAIT] irq23: 32 c28f054c ce5770000 0 0 204 new [IWAIT] irq22: 31 c28f0710 ce5780000 0 0 204 new [IWAIT] irq21: 30 c28f08d4 ce5790000 0 0 204 [RUNQ] irq20: acpi0 29 c12ae1c4 cdb490000 0 0 204 new [IWAIT] irq19: fxp0 uhci0 28 c12ae388 cdb4a0000 0 0 204 new [IWAIT] irq18: 27 c12ae54c cdb4b0000 0 0 204 new [IWAIT] irq17: fxp1 26 c12ae710 cdb4c0000 0 0 204 new [IWAIT] irq16: ahc0 ahc1 25 c12ae8d4 cdb710000 0 0 204 new [IWAIT] irq15: ata1 24 c12aea98 cdb720000 0 0 204 [IWAIT] irq14: ata0 23 c12aec5c cdb730000 0 0 204 new [IWAIT] irq13: 22 c12aee20 cdb740000 0 0 204 new
Re: PII SMP system hangs during boot with ACPI enabled
On 24-Nov-2003 Nate Lawson wrote: It's a long shot, but what about setting kern.timecounter.hardware to i8254. It appears your ACPI timer is bad. The reason why I suggest this is that it seems like interrupts are being lost. I put kern.timecounter.hardware=i8254 into /boot/loader.conf, but it didn't make any difference. Are you sure it even works from loader.conf? From the sources it looks like this is a sysctl rather than a tunable. I could change it to a tunable, though, if you think it's worthwhile. John ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PII SMP system hangs during boot with ACPI enabled
In message [EMAIL PROTECTED], John Polstra writes: On 24-Nov-2003 Nate Lawson wrote: It's a long shot, but what about setting kern.timecounter.hardware to i8254. It appears your ACPI timer is bad. The reason why I suggest this is that it seems like interrupts are being lost. I put kern.timecounter.hardware=i8254 into /boot/loader.conf, but it didn't make any difference. Are you sure it even works from loader.conf? From the sources it looks like this is a sysctl rather than a tunable. I could change it to a tunable, though, if you think it's worthwhile. It would be rather complicated to make it a tunable. Far easier to go into the ACPI timecounter and just give it a negative quality, that will disable it. I'm not sure why Nate think this will change anything with respect to interrupts, but I pressume he knows what he's talking about. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PII SMP system hangs during boot with ACPI enabled
On Mon, 24 Nov 2003, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], John Polstra writes: On 24-Nov-2003 Nate Lawson wrote: It's a long shot, but what about setting kern.timecounter.hardware to i8254. It appears your ACPI timer is bad. The reason why I suggest this is that it seems like interrupts are being lost. I put kern.timecounter.hardware=i8254 into /boot/loader.conf, but it didn't make any difference. Are you sure it even works from loader.conf? From the sources it looks like this is a sysctl rather than a tunable. I could change it to a tunable, though, if you think it's worthwhile. It would be rather complicated to make it a tunable. Far easier to go into the ACPI timecounter and just give it a negative quality, that will disable it. I'm not sure why Nate think this will change anything with respect to interrupts, but I pressume he knows what he's talking about. Some ACPI timecounters on old systems would hang on a read from the register and so moving to i8254 would help if it was being used. But farther down, I see that he was already using TSC so it won't make a difference. -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PII SMP system hangs during boot with ACPI enabled
On Mon, 24 Nov 2003, John Polstra wrote:
On 24-Nov-2003 Nate Lawson wrote:
Please also send the output of acpidump -t -d jdp-P2.asl
When I try to run that command, I get:
acpidump: sysctl machdep.acpi_root does not point to RSDP
The sysctl command shows that machdep.acpi_root is 0.
Remember, though, in order to boot it I had to disable ACPI in
/boot/loader.conf.
Yes, I see. You could use an older kernel like the 5.1R cd.
If you can break to the debugger after it has hung, a tr would be nice.
The fact that it didn't occur to me to try that says a lot about how
long I've been away from -current. :-( I've attached traces from
two different boots. They seem to vary somewhat. I can supply line
numbers on request.
Trace 1:
wakeup(c2944100,0,c06a7546,140,6c) at wakeup+0x4
AcpiOsSignalSemaphore(c2944100,1) at AcpiOsSignalSemaphore+0xa8
AcpiUtReleaseMutex(9,30,c295e8c0,c295e760,cdb64acc) at AcpiUtReleaseMutex+0x8c
AcpiUtReleaseToCache(3,c295e760,cdb64ad8,c045ac17,c295e760) at
AcpiUtReleaseToCache+0x8c
Trace 2:
_mtx_unlock_flags(c2944100,0,c06a7546,150,6c) at _mtx_unlock_flags+0x96
AcpiOsSignalSemaphore(c2944100,1) at AcpiOsSignalSemaphore+0xc8
AcpiUtReleaseMutex(9,8,c045f9cc,c2965940,c12a0c00) at AcpiUtReleaseMutex+0x8c
AcpiUtAcquireFromCache(2,cdb64bf4,c0462229,c12a0c00,cdb64c34) at
AcpiUtAcquireFromCache+0x53
Both of these show that acpi_task_thread is calling a task and then
AcpiOsSignalSemaphore is hanging. I'm wondering if your system can't
handle the acpi interrupt being moved to irq 20. Please try this
(untested) patch that should disable moving the SCI to irq 20. jhb can
probably address this better than I.
-Nate
Index: /sys/i386/acpica/madt.c
===
RCS file: /home/ncvs/src/sys/i386/acpica/madt.c,v
retrieving revision 1.7
diff -u -r1.7 madt.c
--- /sys/i386/acpica/madt.c 14 Nov 2003 22:26:29 - 1.7
+++ /sys/i386/acpica/madt.c 24 Nov 2003 21:51:02 -
@@ -538,11 +538,13 @@
}
if (intr-Source != intr-GlobalSystemInterrupt) {
+#if 0
/* XXX: This assumes that the SCI uses IRQ 9. */
if (intr-GlobalSystemInterrupt 15 intr-Source == 9)
acpi_OverrideInterruptLevel(
intr-GlobalSystemInterrupt);
else
+#endif
ioapic_remap_vector(new_ioapic, new_pin, intr-Source);
if (madt_find_interrupt(intr-Source, old_ioapic,
old_pin) != 0)
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PII SMP system hangs during boot with ACPI enabled
On 24-Nov-2003 Nate Lawson wrote: On Mon, 24 Nov 2003, John Polstra wrote: On 24-Nov-2003 Nate Lawson wrote: Please also send the output of acpidump -t -d jdp-P2.asl When I try to run that command, I get: acpidump: sysctl machdep.acpi_root does not point to RSDP The sysctl command shows that machdep.acpi_root is 0. Remember, though, in order to boot it I had to disable ACPI in /boot/loader.conf. Yes, I see. You could use an older kernel like the 5.1R cd. I'll try that, and send you the dump if I can get one. Both of these show that acpi_task_thread is calling a task and then AcpiOsSignalSemaphore is hanging. I'm wondering if your system can't handle the acpi interrupt being moved to irq 20. Please try this (untested) patch that should disable moving the SCI to irq 20. jhb can probably address this better than I. I tried your patch, but it didn't change the behavior any. John ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PII SMP system hangs during boot with ACPI enabled
On 24-Nov-2003 Nate Lawson wrote: Trace 1: wakeup(c2944100,0,c06a7546,140,6c) at wakeup+0x4 AcpiOsSignalSemaphore(c2944100,1) at AcpiOsSignalSemaphore+0xa8 AcpiUtReleaseMutex(9,30,c295e8c0,c295e760,cdb64acc) at AcpiUtReleaseMutex+0x8c AcpiUtReleaseToCache(3,c295e760,cdb64ad8,c045ac17,c295e760) at AcpiUtReleaseToCache+0x8c Trace 2: _mtx_unlock_flags(c2944100,0,c06a7546,150,6c) at _mtx_unlock_flags+0x96 AcpiOsSignalSemaphore(c2944100,1) at AcpiOsSignalSemaphore+0xc8 AcpiUtReleaseMutex(9,8,c045f9cc,c2965940,c12a0c00) at AcpiUtReleaseMutex+0x8c AcpiUtAcquireFromCache(2,cdb64bf4,c0462229,c12a0c00,cdb64c34) at AcpiUtAcquireFromCache+0x53 Both of these show that acpi_task_thread is calling a task and then AcpiOsSignalSemaphore is hanging. I'm wondering if your system can't handle the acpi interrupt being moved to irq 20. Please try this (untested) patch that should disable moving the SCI to irq 20. As I mentioned a minute ago, the patch didn't help. But I grabbed another stack trace while I was at it. This one is quite different from the others. I don't think it's different because of your patch, though. I saw one like this earlier, but thought it might have been an anomaly caused by my own mucking around in DDB. siointr1(c298d000,0,c06c9b97,6a0,cdb5ec70) at siointr1+0xec siointr(c298d000,c053a016,c06d88a0,c06e7ae0,4) at siointr+0x35 intr_execute_handlers(c129f88c,cdb5ec88,cdb5eccc,c065ca43,34) at intr_execute_handlers+0xc8 lapic_handle_intr(34) at lapic_handle_intr+0x3a Xapic_isr1() at Xapic_isr1+0x33 --- interrupt, eip = 0xc053a4ea, esp = 0xcdb5eccc, ebp = 0xcdb5eccc --- critical_exit(c070af20,1,c06b8c37,14b,0) at critical_exit+0x2a _mtx_unlock_spin_flags(c070af20,0,c06b74f7,23a,c294954c) at _mtx_unlock_spin_flags+0x9d ithread_loop(c12a6800,cdb5ed48,c06b7365,311,0) at ithread_loop+0x26e fork_exit(c0520150,c12a6800,cdb5ed48) at fork_exit+0xb4 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xcdb5ed7c, ebp = 0 --- John ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PII SMP system hangs during boot with ACPI enabled
On Mon, 24 Nov 2003, John Polstra wrote: On 24-Nov-2003 Nate Lawson wrote: Trace 1: wakeup(c2944100,0,c06a7546,140,6c) at wakeup+0x4 AcpiOsSignalSemaphore(c2944100,1) at AcpiOsSignalSemaphore+0xa8 AcpiUtReleaseMutex(9,30,c295e8c0,c295e760,cdb64acc) at AcpiUtReleaseMutex+0x8c AcpiUtReleaseToCache(3,c295e760,cdb64ad8,c045ac17,c295e760) at AcpiUtReleaseToCache+0x8c Trace 2: _mtx_unlock_flags(c2944100,0,c06a7546,150,6c) at _mtx_unlock_flags+0x96 AcpiOsSignalSemaphore(c2944100,1) at AcpiOsSignalSemaphore+0xc8 AcpiUtReleaseMutex(9,8,c045f9cc,c2965940,c12a0c00) at AcpiUtReleaseMutex+0x8c AcpiUtAcquireFromCache(2,cdb64bf4,c0462229,c12a0c00,cdb64c34) at AcpiUtAcquireFromCache+0x53 Both of these show that acpi_task_thread is calling a task and then AcpiOsSignalSemaphore is hanging. I'm wondering if your system can't handle the acpi interrupt being moved to irq 20. Please try this (untested) patch that should disable moving the SCI to irq 20. As I mentioned a minute ago, the patch didn't help. But I grabbed another stack trace while I was at it. This one is quite different from the others. I don't think it's different because of your patch, though. I saw one like this earlier, but thought it might have been an anomaly caused by my own mucking around in DDB. siointr1(c298d000,0,c06c9b97,6a0,cdb5ec70) at siointr1+0xec siointr(c298d000,c053a016,c06d88a0,c06e7ae0,4) at siointr+0x35 intr_execute_handlers(c129f88c,cdb5ec88,cdb5eccc,c065ca43,34) at intr_execute_handlers+0xc8 lapic_handle_intr(34) at lapic_handle_intr+0x3a Xapic_isr1() at Xapic_isr1+0x33 --- interrupt, eip = 0xc053a4ea, esp = 0xcdb5eccc, ebp = 0xcdb5eccc --- critical_exit(c070af20,1,c06b8c37,14b,0) at critical_exit+0x2a _mtx_unlock_spin_flags(c070af20,0,c06b74f7,23a,c294954c) at _mtx_unlock_spin_flags+0x9d ithread_loop(c12a6800,cdb5ed48,c06b7365,311,0) at ithread_loop+0x26e fork_exit(c0520150,c12a6800,cdb5ed48) at fork_exit+0xb4 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xcdb5ed7c, ebp = 0 --- Someone more familiar with ithread_loop should probably answer this. One workaround might be to enable ACPI_NO_SEMAPHORES on your box. -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PII SMP system hangs during boot with ACPI enabled
On 25-Nov-2003 Nate Lawson wrote: Someone more familiar with ithread_loop should probably answer this. One workaround might be to enable ACPI_NO_SEMAPHORES on your box. I built and booted a kernel with ACPI_NO_SEMAPHORES, but it still hangs at the same point in the boot. The stack trace is attached. It looks pretty similar to the others. John sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x100 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounters tick every 10.000 msec acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0% ~Stopped at siointr1+0xec: jmp siointr1+0x220 db trace siointr1(c298e000,0,c06c9567,6a0,cdb61b58) at siointr1+0xec siointr(c298e000,cdb61bf4,c045a145,c12a0de4,4) at siointr+0x35 intr_execute_handlers(c129f88c,cdb61b70,cdb61bd8,c065c5a3,34) at intr_execute_ha ndlers+0xc8 lapic_handle_intr(34) at lapic_handle_intr+0x3a Xapic_isr1() at Xapic_isr1+0x33 --- interrupt, eip = 0xc0457d70, esp = 0xcdb61bb4, ebp = 0xcdb61bd8 --- AcpiNsGetNextNode(bbc5,cdb61bf4,c044a8b7,c12a0c00,0) at AcpiNsGetNextNode AcpiDsTerminateControlMethod(c12a0c00,c2959700,cdb61c14,c12a0c00,c12a0de4) at Ac piDsTerminateControlMethod+0xed AcpiPsParseAml(c12a0c00,c294fcc0,c2951aa0,ce5b5ac0,d) at AcpiPsParseAml+0x15b AcpiPsxExecute(c2951aa0,0,cdb61c9c,c2951aa0,0) at AcpiPsxExecute+0x202 AcpiNsExecuteControlMethod(c2951aa0,0,cdb61c9c,c0702694,c294dedc) at AcpiNsExecu teControlMethod+0x5f AcpiNsEvaluateByHandle(c2951aa0,0,0,76,c2951aa0) at AcpiNsEvaluateByHandle+0x96 AcpiEvAsynchExecuteGpeMethod(c294dedc,0,c06a6f81,7b,0) at AcpiEvAsynchExecuteGpe Method+0x8c acpi_task_thread(0,cdb61d48,c06b6d35,311,2e636466) at acpi_task_thread+0x105 fork_exit(c0474e20,0,cdb61d48) at fork_exit+0xb4 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xcdb61d7c, ebp = 0 --- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PII SMP system hangs during boot with ACPI enabled
No way! Good (non-386) equipment is never to old. :) Please add debug.acpi.disable=cpu to loader.conf or type that in at the loader prompt. If it boots ok, we'll have to debug the acpi_cpu_startup path. -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
