From nobody@FreeBSD.org Fri Mar 28 02:29:49 2008 Return-Path: Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 959111065672 for ; Fri, 28 Mar 2008 02:29:49 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21]) by mx1.freebsd.org (Postfix) with ESMTP id 809DD8FC18 for ; Fri, 28 Mar 2008 02:29:49 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.2/8.14.2) with ESMTP id m2S2TWec005745 for ; Fri, 28 Mar 2008 02:29:32 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.2/8.14.1/Submit) id m2S2TWJT005744; Fri, 28 Mar 2008 02:29:32 GMT (envelope-from nobody) Message-Id: <200803280229.m2S2TWJT005744@www.freebsd.org> Date: Fri, 28 Mar 2008 02:29:32 GMT From: Dieter To: freebsd-gnats-submit@FreeBSD.org Subject: 7.0 panics on amd64 Tyan 2865 X-Send-Pr-Version: www-3.1 X-GNATS-Notify: gavin@FreeBSD.org >Number: 122174 >Category: amd64 >Synopsis: [panic] 7.0 no longer includes "device atpic" so fails with APIC disabled >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-amd64 >State: closed >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Mar 28 02:30:02 UTC 2008 >Closed-Date: Sun Dec 05 10:55:53 UTC 2010 >Last-Modified: Sun Dec 05 10:55:53 UTC 2010 >Originator: Dieter >Release: 7.0 >Organization: >Environment: amd64 7.0 generic kernel from release iso >Description: Attempting to update from 6.2 to 7.0 but always get a kernel panic. Tyan Tomcat k8e 2865 mainboard AMD64 nforce4-ultra GENERIC amd64 kernel, nothing custom yet. usable memory = 2134630400 (2035 MB) avail memory = 2060079104 (1964 MB) kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) hptrr: HPT RocketRAID controller driver v1.1 (Feb 24 2008 10:34:18) [ off to a bad start, there is no RocketRAID controller ] acpi0: on motherboard acpi0: could not allocate interrupt ACPI Exception (evevent-0257): AE_ALREADY_EXISTS, Unable to install System Control Interrupt handler [200 70320] acpi0: Could not enable ACPI: AE_ALREADY_EXISTS device_attach: acpi0 attach returned 6 cpu0 on motherboard powernow0: on cpu0 device_attach: powernow0 attach returned 6 pcib0: pcibus 0 on motherboard pci0: on pcib0 pci0: at device 0.0 (no driver attached) isab0: at device 1.0 on pci0 isa0: on isab0 pci0: at device 1.1 (no driver attached) ohci0: mem 0xfebff000-0xfebfffff irq 10 at device 2.0 on pci0 ohci0: Could not allocate irq device_attach: ohci0 attach returned 6 ehci0: mem 0xfebfe000-0xfebfe0ff irq 11 at device 2.1 on pci0 ehci0: Could not allocate irq device_attach: ehci0 attach returned 6 pci0: at device 4.0 (no driver attached) atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xe000-0xe00f at device 6.0 on pci0 ata0: on atapci0 ata0: unable to allocate interrupt device_attach: ata0 attach returned 6 ata1: on atapci0 ata1: unable to allocate interrupt device_attach: ata1 attach returned 6 atapci1: port 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0x cc00-0xcc0f mem 0xfebfb000-0xfebfbfff irq 11 at device 7.0 on pci0 atapci1: unable to map interrupt device_attach: atapci1 attach returned 6 atapci2: port 0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0x b800-0xb80f mem 0xfebfa000-0xfebfafff irq 10 at device 8.0 on pci0 atapci2: unable to map interrupt device_attach: atapci2 attach returned 6 pcib1: at device 9.0 on pci0 pci1: on pcib1 vgapci0: port 0xac00-0xacff mem 0xfc000000-0xfcffffff,0xfdfff000-0xfdffffff irq 12 at device 5.0 on pci1 fwohci0: port 0xa800-0xa87f mem 0xfdffe000-0xfdffe7ff irq 11 at device 6.0 on pci1 fwohci0: Could not allocate irq device_attach: fwohci0 attach returned 6 pci1: at device 7.0 (no driver attached) pci1: at device 7.2 (no driver attached) pcib2: at device 8.0 on pci1 pci2: on pcib2 fwohci1: mem 0xfdeff000-0xfdefffff irq 10 at device 8.0 on pci2 fwohci1: Could not allocate irq device_attach: fwohci1 attach returned 6 ohci1: mem 0xfdefe000-0xfdefefff irq 10 at device 9.0 on pci2 ohci1: Could not allocate irq device_attach: ohci1 attach returned 6 ohci2: mem 0xfdefd000-0xfdefdfff irq 5 at device 9.1 on pci2 ohci2: Could not allocate irq device_attach: ohci2 attach returned 6 ehci1: mem 0xfdefc000-0xfdefc0ff irq 11 at device 9.2 on pci2 ehci1: Could not allocate irq device_attach: ehci1 attach returned 6 pci1: at device 9.0 (no driver attached) pci1: at device 9.2 (no driver attached) de0: port 0xa400-0xa47f mem 0xfdffd000-0xfdffd07f irq 5 at device 10.0 on pci1 de0: Cogent 21040 [10Mb/s] pass 2.4 Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x10 fault code = supervisor read data, page not present instruction pointer = 0x8:0xffffffff8029750e stack pointer = 0x10:0xffffffff80bcc600 frame pointer = 0x10:0xffffff0001253800 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (swapper) trap number = 12 panic: page fault cpuid = 0 Uptime: 1s Automatic reboot in 15 seconds - press a key on the console to abort I tried both acpi_load=YES and NO in loader.conf. I tried the various options (safe mode, etc.) at the loader screen, but always the same panic. >How-To-Repeat: Attempt to boot 7.0 amd64 generic kernel on Tyan 2865. >Fix: >Release-Note: >Audit-Trail: State-Changed-From-To: open->feedback State-Changed-By: gavin State-Changed-When: Fri Mar 28 13:18:53 UTC 2008 State-Changed-Why: To submitter: Can you please try disabling the de(4) driver from the loader (set hint.de.0.disabled="1") to confirm/rule out if that driver is the issue? Also, does a verbose boot give any further clues? Responsible-Changed-From-To: freebsd-bugs->gavin Responsible-Changed-By: gavin Responsible-Changed-When: Fri Mar 28 13:18:53 UTC 2008 Responsible-Changed-Why: Track http://www.freebsd.org/cgi/query-pr.cgi?pr=122174 From: Gavin Atkinson To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/122174: [panic] 7.0 panics on amd64 Tyan 2865 Date: Fri, 28 Mar 2008 13:46:11 +0000 Panic address is in bpf_peers_present() (/usr/src/sys/net/bpf.h:791), I suspect this may be a duplicate of kern/120915. We'll see what the feedback reveals. From: Dieter To: gavin@FreeBSD.org Cc: bug-followup@FreeBSD.org Subject: Re: kern/122174: [panic] 7.0 panics on amd64 Tyan 2865 Date: Fri, 28 Mar 2008 08:28:12 +0100 In message <200803281328.m2SDS880061692@freefall.freebsd.org>, gavin@FreeBSD.org writes: > To submitter: Can you please try disabling the de(4) driver from the > loader (set hint.de.0.disabled="1") to confirm/rule out if that driver > is the issue? Also, does a verbose boot give any further clues? LINES=24 acpi_load=NO <-------<<<< I tried both YES and NO with de disabled autoboot_delay=NO bootfile=kernel comconsole_speed=19200 console=comconsole currdev=disk0s2a: hint.acpi.0.oem=Nvidia hint.acpi.0.revision=1 hint.acpi.0.rsdp=0xf7b80 hint.acpi.0.rsdt=0x7fff3040 hint.atkbd.0.at=atkbdc hint.atkbd.0.irq=1 hint.atkbdc.0.at=isa hint.atkbdc.0.port=0x060 hint.de.0.disabled=1 <-------<<<< as requested hint.fd.0.at=fdc0 hint.fd.0.drive=0 hint.fd.1.at=fdc0 hint.fd.1.drive=1 hint.fdc.0.at=isa hint.fdc.0.drq=2 hint.fdc.0.irq=6 hint.fdc.0.port=0x3F0 hint.ppc.0.at=isa hint.ppc.0.irq=7 hint.psm.0.at=atkbdc hint.psm.0.irq=12 hint.sc.0.at=isa hint.sc.0.flags=0x100 hint.sio.0.at=isa hint.sio.0.flags=0x10 hint.sio.0.irq=4 hint.sio.0.port=0x3F8 hint.sio.1.at=isa hint.sio.1.irq=3 hint.sio.1.port=0x2F8 hint.sio.2.at=isa hint.sio.2.disabled=1 hint.sio.2.irq=5 hint.sio.2.port=0x3E8 hint.sio.3.at=isa hint.sio.3.disabled=1 hint.sio.3.irq=9 hint.sio.3.port=0x2E8 hint.vga.0.at=isa hw.ata.wc=0 interpret=OK kernel=GENERIC kernel_options= kernelname=/boot/GENERIC/kernel loaddev=disk0s2a: mac_ifoff=NO module_path=/boot/GENERIC;/boot/modules prompt=${interpret} rootdev=ad10s1 smbios.bios.reldate=02/17/2005 smbios.bios.vendor=Phoenix Technologies, LTD smbios.bios.version=6.00 PG smbios.chassis.maker= smbios.chassis.serial= smbios.chassis.tag= smbios.chassis.version= smbios.planar.maker= smbios.planar.product=NF-CK804 smbios.planar.serial= smbios.planar.version= smbios.socket.enabled=1 smbios.socket.populated=1 smbios.system.maker= smbios.system.product= smbios.system.serial= smbios.system.version= SMAP type=01 base=0000000000000000 len=0000000000098000 SMAP type=02 base=00000000000f0000 len=0000000000010000 SMAP type=02 base=00000000fec00000 len=0000000000001000 SMAP type=02 base=00000000fee00000 len=0000000000100000 SMAP type=02 base=00000000fefffc00 len=0000000000000400 SMAP type=02 base=00000000ffff0000 len=0000000000010000 SMAP type=02 base=00000000e0000000 len=0000000010000000 SMAP type=03 base=000000007fff3000 len=000000000000d000 SMAP type=04 base=000000007fff0000 len=0000000000003000 SMAP type=02 base=0000000000098000 len=0000000000008000 SMAP type=01 base=0000000000100000 len=000000007fef0000 Copyright (c) 1992-2008 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 7.0-RELEASE #0: Sun Feb 24 10:35:36 UTC 2008 root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel "/boot/GENERIC/kernel" at 0xffffffff80bc8000. Calibrating clock(s) ... i8254 clock: 1193234 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 1808342444 Hz CPU: AMD Athlon(tm) 64 Processor 3000+ (1808.34-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x20ff0 Stepping = 0 Features=0x78bfbff Features2=0x1 AMD Features=0xe2500800 AMD Features2=0x1 L1 2MB data TLB: 8 entries, fully associative L1 2MB instruction TLB: 8 entries, fully associative L1 4KB data TLB: 32 entries, fully associative L1 4KB instruction TLB: 32 entries, fully associative L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L2 2MB unified TLB: 0 entries, disabled/not present L2 4KB data TLB: 512 entries, 4-way associative L2 4KB instruction TLB: 512 entries, 4-way associative L2 unified cache: 512 kbytes, 64 bytes/line, 1 lines/tag, 16-way associative usable memory = 2134630400 (2035 MB) Physical memory chunk(s): 0x0000000000001000 - 0x0000000000093fff, 602112 bytes (147 pages) 0x0000000000cc5000 - 0x000000007c39ffff, 2070786048 bytes (505563 pages) avail memory = 2060079104 (1964 MB) ath_rate: version 1.2 wlan_amrr: wlan: <802.11 Link Layer> null: random: nfslock: pseudo-device kbd: new array size 4 kbd1 at kbdmux0 mem: io: ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) hptrr: HPT RocketRAID controller driver v1.1 (Feb 24 2008 10:34:18) ACPI: RSDP @ 0x0xf7b80/0x0014 (v 0 Nvidia) ACPI: RSDT @ 0x0x7fff3040/0x002C (v 1 Nvidia AWRDACPI 0x42302E31 AWRD 0x00000000) ACPI: FACP @ 0x0x7fff30c0/0x0074 (v 1 Nvidia AWRDACPI 0x42302E31 AWRD 0x00000000) ACPI: DSDT @ 0x0x7fff3180/0x612B (v 1 NVIDIA AWRDACPI 0x00001000 MSFT 0x0100000E) ACPI: FACS @ 0x0x7fff0000/0x0040 ACPI: MCFG @ 0x0x7fff93c0/0x003C (v 1 Nvidia AWRDACPI 0x42302E31 AWRD 0x00000000) acpi0: on motherboard acpi0: could not allocate interrupt ACPI Exception (evevent-0257): AE_ALREADY_EXISTS, Unable to install System Control Interrupt handler [200 70320] acpi0: Could not enable ACPI: AE_ALREADY_EXISTS device_attach: acpi0 attach returned 6 cpu0 on motherboard powernow0: on cpu0 powernow0: STATUS: 0x12040606040a0a0a powernow0: STATUS: maxfid: 0x0a powernow0: STATUS: maxvid: 0x04 device_attach: powernow0 attach returned 6 pcib0: pcibus 0 on motherboard pci0: on pcib0 pci0: domain=0, physical bus=0 found-> vendor=0x10de, dev=0x005e, revid=0xa3 domain=0, bus=0, slot=0, func=0 class=05-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x0050, revid=0xa3 domain=0, bus=0, slot=1, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x000f, statreg=0x00a0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x0052, revid=0xa2 domain=0, bus=0, slot=1, func=1 class=0c-05-00, hdrtype=0x00, mfdev=1 cmdreg=0x0001, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) intpin=a, irq=12 powerspec 2 supports D0 D3 current D0 map[10]: type I/O Port, range 32, base 0xfc00, size 5, enabled map[20]: type I/O Port, range 32, base 0x1c00, size 6, enabled map[24]: type I/O Port, range 32, base 0x1c40, size 6, enabled found-> vendor=0x10de, dev=0x005a, revid=0xa2 domain=0, bus=0, slot=2, func=0 class=0c-03-10, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) intpin=a, irq=10 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0xfebff000, size 12, enabled found-> vendor=0x10de, dev=0x005b, revid=0xa3 domain=0, bus=0, slot=2, func=1 class=0c-03-20, hdrtype=0x00, mfdev=1 cmdreg=0x0006, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) intpin=b, irq=11 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0xfebfe000, size 8, enable00, mfdev=0 cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x02 (500 ns), maxlat=0x05 (1250 ns) intpin=a, irq=12 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type I/O Port, range 32, base 0xf000, size 8, enabled map[14]: type I/O Port, range 32, base 0xec00, size 8, enabled map[18]: type Memory, range 32, base 0xfebfd000, size 12, enabled found-> vendor=0x10de, dev=0x0053, revid=0xa2 domain=0, bus=0, slot=6, func=0 class=01-01-8a, hdrtype=0x00 type I/O Port, range 32, base 0x9f0, size 3, enabled map[14]: type I/O Port, range 32, base 0xbf0, size 2, enabled map[18]: type I/O Port, range 32, base 0x970, size 3, enabled map[1c]: type I/O Port, range 32, base 0xb70, size 2, enabled map[20]: type I/O Port, range 32, base 0xcc00, size 4, enabled map[24]: type Memory, range 32, base 0xfebfb000, size 12, enabled found-> vendor=0x10de, dev=0x0055, revid=0xa3 domain=0, bus=0, slot=8, func=0 class=01-01-85, hdrtype=0x00, mfdev=0 cmdrenge 32, base 0xb800, size 4, enabled map[24]: type Memory, range 32, base 0xfebfa000, size 12, enabled found-> vendor=0x10de, dev=0x005c, revid=0xa2 domain=0, bus=0, slot=9, func=0 class=06-04-01, hdrtype=0x01, mfdev=0 cmdreg=0x0007, statreg=0x00a0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x0c (3000 ns), maxlat=0x02 (500 ns) found-> vendor=0x10de, dev=0x0057, revid=0xa3 domain=0, bus=0, slot=10, func=0 class=06-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x00b0, cachelns lattimer=0x00 (0 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns) powerspec 2 supports D0 D3 current D0 [ probably a glitch in X11 copy and paste from MSI supports 2 messages, 64 bit the console window ] found-> vendor=0x10de, dev=0x005d, revid=0xa3 domain=0, bus=0, slot=12, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0007, statreg=0x0010, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns) powerspec 2 supports D0 D3 current D0 MSI supports 2 messages, 64 bit found-> vendor=0x10de, dev=0x005d, revid=0xa3 dom00 (0 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns) powerspec 2 supports D0 D3 current D0 MSI supports 2 messages, 64 bit found-> vendor=0x1022, dev=0x1100, revid=0x00 domain=0, bus=0, slot=24, func=0 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0010, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1101, revid=0x00 domain=0, bus=0, slot=24, func=1 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statrcmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) pci0: at device 0.0 (no driver attached) isab0: at device 1.0 on pci0 isa0: on isab0 pci0: at device 1.1 (no driver attached) ohci0: mem 0xfebff000-0xfebfffff irq 10 at device 2.0 on pci0 ohci0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfebff000 ohci0: Could not allocate irq device_attach: ohci0troller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xe000-0xe00f at device 6.0 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xe000 ata0: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 ata0: reset tp1 mask=03 ostat0=50 ostat1=00 ata0: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata0: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 ata0: reset tp2 stat0=00 stat1=00 devices=0x4 ata0: unable to alltat0=50 ostat1=00 ata1: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata1: stat1=0x00 err=0x01 lsb=0x00 msb=0x00 ata1: reset tp2 stat0=50 stat1=00 devices=0x1 ata1: unable to allocate interrupt device_attach: ata1 attach returned 6 atapci1: at device 9.0 on pci0 pcib1: domain 0 pcib1: secondary bus 1 pcib1: subordinate bus 2 pcib1: I/O decode 0x9000-0xafff pcib1: memory decode 0xf8000000-0xfdffffff pcib1: prefetched decode 00xfcffffff: good map[14]: type I/O Port, range 32, base 0xac00, size 8, enabled pcib1: requested I/O range 0xac00-0xacff: in range map[18]: type Memory, range 32, base 0xfdfff000, size 12, enabled pcib1: requested memory range 0xfdfff000-0xfdffffff:vid=0x80 domain=0, bus=1, slot=6, func=0 class=0c-00-10, hdrtype=0x00, mfdev=0 cmdreg=0x0087, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x20 (8000 ns) intpin=a, irq=11 powerspec 2 supports D0 D2 D3rq=10 powerspec 2 supports D0 D3 current D0 map[10]: type Memory, range 32, base 0xf9000000, size 24, enabled pcib1: requested memory range 0xf9000000-0xf9ffffff: good found-> vendor=0x14f1, dev=0x8802, revid=0x05 domain=0, bus=1, slot=7, func=2 class=04-80-00, hdrtype=0x00, mfdev=1 cmdreg=0x0006, statreg=0x0290, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x06 (1500 ns), maxlat=0x58 (22000 ns) intpin=a, irq=10 powerspec 2 supports D0 D3 current D0 map[10]: type Memory, range 32, base 0xf8000000, size 24, enabled pcib1: requested memory range 0xf8000000-0xf8ffffff: good found-> vendor=0x3388, dev=0x0021, revid=0x11 domain=0, bus=1, slot=8, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0007, statreg=0x0290, cachttimer=0x20 (960 ns), mingnt=0x14 (5000 ns), maxlat=0x37 (1375 0 ns) intpin=a, irq=11 powerspec 2 supports D0 D3 current D0 map[10]: type Memory, range 32, base 0xfb000000, size 24, enabled pcib1: requested memory range 0xfb000000-0xfbffffff: good found-> vendor=0x14f1, dev=0x8802, revid=0x05 domain=0, bus=1, slot=9, func=2 class=04-80-00, hdrtype=0x00, mfdev=1 cmdreg=0x0006, statreg=0x0290, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x06 (1500 ns), maxlat=0x58 (22000 ns) intpin= (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=5 map[10]: type I/O Port, range 32, base 0xa400, size 7, enabled pcib1: requested I/O range 0xa400-0xa47f: in range map[14]: type Memory, range 32, base 0xfdffd000, size 7, enabled p 0 pcib2: secondary bus 2 pcib2: subordinate bus 2 pcib2: I/O decode 0x9000-0x9fff pcib2: memory decode 0xfde00000-0xfdefffff pcib2: prefetched decode 0xfea00000-0xfeafffff pci2: on pcib2 pci2: domain=0, physical bus=2 found-> vendor=0x1033, dev=0x00ce, revid=0x01 domain=0, bus=2, slot=8, func=0 class=0c-00-10, hdrtype=0x00, mfdev=0 cmdreg=0x0016, statreg=0x0290, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) int50 ns), maxlat=0x2a (10500 ns) intpin=a, irq=10 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0xfdefe000, size 12, enabled pcib2: requested memory range 0xfdefe000-0xfdefefff: good pcib1: requested memory range 0xfdefe000-0xfdefefff: good found-> vendor=0x1033, dev=0x0035, revid=0x41 domain=0, bus=2, slot=9, func=1 class=0c-03-10, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x01 (250 ns), maxlas D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0xfdefc000, size 8, enabled pcib2: requested memory range 0xfdefc000-0xfdefc0ff: good pcib1: requested memory range 0xfdefc000-0xfdefc0ff: good fwohci1: mem 0xfdeff000-0xn pci2 fwohci1: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfdeff000 fwohci1: Could not allocate irq device_attach: fwohci1 attach returned 6 ohci1: mem 0xfdefe000-0xfdefefff irq 10 at device 9.0 on pci2 ohci1: Reserves for rid 0x10 type 3 at 0xfdefc000 ehci1: Could not allocate irq device_attach: ehci1 attach returned 6 pci1: at device 9.0 (no driver attached) pci1: at device 9.2 (no driver attached) de0: p80 bytes for rid 0x14 type 3 at 0xfdffd000 de0: Cogent 21040 [10Mb/s] pass 2.4 Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x10 fault code = supervisor read data, page not present instruction popanic: page fault cpuid = 0 Uptime: 1s Automatic reboot in 15 seconds - press a key on the console to abort -------- It still thinks I have a RocketRAID controller. This smells like a clue. ata1: unable to allocate interrupt device_attach: ata1 attach returned 6 (and similar for other devices) smells like a clue. I note that the de0 line does NOT say (no driver attached), despite de being disabled in loader. I also tried adding hint.nve.0.disabled="1" hint.nfe.0.disabled="1" as nve is supposed to change to nfe in 7.0. But I get the exact same panic. From: Dieter To: gavin@FreeBSD.org Cc: bug-followup@FreeBSD.org Subject: Re: kern/122174: [panic] 7.0 panics on amd64 Tyan 2865 Date: Fri, 28 Mar 2008 18:24:12 +0100 > Panic address is in bpf_peers_present() (/usr/src/sys/net/bpf.h:791), > I suspect this may be a duplicate of {_kern/120915_}. We'll see what > the feedback reveals. Commented out a bunch of devices I don't have, which gets rid of the rocketraid message. Still complains about irqs and such. Using patch from kern/120915 it gets a tad farther, ending with de0: couldn't map interrupt and then hangs instead of panicing. Reset switch required. Verbose doesn't help. Commented out de driver, building a new kernel now. From: Dieter To: gavin@FreeBSD.org Cc: bug-followup@FreeBSD.org Subject: Re: kern/122174: [panic] 7.0 panics on amd64 Tyan 2865 Date: Fri, 28 Mar 2008 19:42:38 +0100 > Commented out de driver, building a new kernel now. Now it gets to mounting the root filesystem, but it doesn't have any disks available, due to the problems with irqs and such. Lots of devices say things like: Could not allocate irq unable to allocate interrupt attach returned 6 Same results with acpi_load either YES or NO. usable memory = 2139185152 (2040 MB) avail memory = 2064855040 (1969 MB) kbd1 at kbdmux0 acpi0: on motherboard acpi0: could not allocate interrupt ACPI Exception (evevent-0257): AE_ALREADY_EXISTS, Unable to install System Control Interrupt handler [200 70320] acpi0: Could not enable ACPI: AE_ALREADY_EXISTS device_attach: acpi0 attach returned 6 cpu0 on motherboard powernow0: on cpu0 device_attach: powernow0 attach returned 6 pcib0: pcibus 0 on motherboard pci0: on pcib0 pci0: at device 0.0 (no driver attached) isab0: at device 1.0 on pci0 isa0: on isab0 pci0: at device 1.1 (no driver attached) ohci0: mem 0xfebff000-0xfebfffff irq 10 at device 2.0 on pci0 ohci0: Could not allocate irq device_attach: ohci0 attach returned 6 ehci0: mem 0xfebfe000-0xfebfe0ff irq 11 at device 2.1 on pci0 ehci0: Could not allocate irq device_attach: ehci0 attach returned 6 pci0: at device 4.0 (no driver attached) atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xe000-0xe00f at device 6.0 on pci0 ata0: on atapci0 ata0: unable to allocate interrupt device_attach: ata0 attach returned 6 ata1: on atapci0 ata1: unable to allocate interrupt device_attach: ata1 attach returned 6 atapci1: port 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0x cc00-0xcc0f mem 0xfebfb000-0xfebfbfff irq 11 at device 7.0 on pci0 atapci1: unable to map interrupt device_attach: atapci1 attach returned 6 atapci2: port 0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0x b800-0xb80f mem 0xfebfa000-0xfebfafff irq 10 at device 8.0 on pci0 atapci2: unable to map interrupt device_attach: atapci2 attach returned 6 pcib1: at device 9.0 on pci0 pci1: on pcib1 vgapci0: port 0xac00-0xacff mem 0xfc000000-0xfcffffff,0xfdfff000-0xfdffffff irq 12 at device 5.0 on pci1 fwohci0: port 0xa800-0xa87f mem 0xfdffe000-0xfdffe7ff irq 11 at device 6.0 on pci1 fwohci0: Could not allocate irq device_attach: fwohci0 attach returned 6 pci1: at device 7.0 (no driver attached) pci1: at device 7.2 (no driver attached) pcib2: at device 8.0 on pci1 pci2: on pcib2 fwohci1: mem 0xfdeff000-0xfdefffff irq 10 at device 8.0 on pci2 fwohci1: Could not allocate irq device_attach: fwohci1 attach returned 6 ohci1: mem 0xfdefe000-0xfdefefff irq 10 at device 9.0 on pci2 ohci1: Could not allocate irq device_attach: ohci1 attach returned 6 ohci2: mem 0xfdefd000-0xfdefdfff irq 5 at device 9.1 on pci2 ohci2: Could not allocate irq device_attach: ohci2 attach returned 6 ehci1: mem 0xfdefc000-0xfdefc0ff irq 11 at device 9.2 on pci2 ehci1: Could not allocate irq device_attach: ehci1 attach returned 6 pci1: at device 9.0 (no driver attached) pci1: at device 9.2 (no driver attached) pci1: at device 10.0 (no driver attached) nfe0: port 0xb400-0xb407 mem 0xfebf9000-0xfebf9fff irq 5 a t device 10.0 on pci0 nfe0: couldn't allocate IRQ resources device_attach: nfe0 attach returned 6 pcib3: at device 11.0 on pci0 pci3: on pcib3 pcib4: at device 12.0 on pci0 pci4: on pcib4 pcib5: at device 13.0 on pci0 pci5: on pcib5 bge0: mem 0xfe4f0000-0xfe4fffff irq 12 at device 0.0 on pci5 bge0: couldn't map interrupt device_attach: bge0 attach returned 6 pcib6: at device 14.0 on pci0 pci6: on pcib6 orm0: at iomem 0xc0000-0xc7fff,0xc8000-0xcbfff,0xcc000-0xcffff,0xd0000-0xd17ff on isa0 atkbdc0: at port 0x60,0x64 on isa0 ppc0: cannot reserve I/O port range sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A, console sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 1808342599 Hz quality 800 Timecounters tick every 1.000 msec Manual root filesystem specification: : Mount using filesystem eg. ufs:da0s1a ? List valid disk boot devices Abort manual input mountroot> ufs:ad10s1a Trying to mount root from ufs:ad10s1a Manual root filesystem specification: : Mount using filesystem eg. ufs:da0s1a ? List valid disk boot devices Abort manual input mountroot> ? List of GEOM managed disk devices: Manual root filesystem specification: : Mount using filesystem eg. ufs:da0s1a ? List valid disk boot devices Abort manual input mountroot> From: gavin@FreeBSD.org To: Dieter Cc: bug-followup@FreeBSD.org Subject: Re: kern/122174: [panic] 7.0 panics on amd64 Tyan 2865 Date: Sat, 29 Mar 2008 19:42:54 +0000 (GMT) On Fri, 28 Mar 2008, Dieter wrote: >> Commented out de driver, building a new kernel now. > > Now it gets to mounting the root filesystem, but it doesn't > have any disks available, due to the problems with irqs and such. > > Lots of devices say things like: > > Could not allocate irq > unable to allocate interrupt > attach returned 6 > > Same results with acpi_load either YES or NO. OK, given it boots without the de(4) driver in the kernel, my guess is that those issues are related to PR kern/120915. Looking at the IRQ issues you are seeing, can you check to see if you are running with the most recent BIOS? Can you try booting in safe mode from the loader prompt and seeing if that helps at all? BTW, don't worry about the rocketraid messages, all it was saying was that the driver had been loaded, not that a card was detected (similarly, the ath_hal messages). Thanks, Gavin From: Dieter To: gavin@FreeBSD.org Cc: bug-followup@FreeBSD.org Subject: Re: kern/122174: [panic] 7.0 panics on amd64 Tyan 2865 Date: Sat, 29 Mar 2008 16:21:51 +0100 > >> Commented out de driver, building a new kernel now. > > > > Now it gets to mounting the root filesystem, but it doesn't > > have any disks available, due to the problems with irqs and such. > > > > Lots of devices say things like: > > > > Could not allocate irq > > unable to allocate interrupt > > attach returned 6 > > > > Same results with acpi_load either YES or NO. > > OK, given it boots without the de(4) driver in the kernel, my guess is > that those issues are related to PR kern/120915. Looking at the IRQ > issues you are seeing, can you check to see if you are running with the > most recent BIOS? Can you try booting in safe mode from the loader prompt > and seeing if that helps at all? > > BTW, don't worry about the rocketraid messages, all it was saying was that > the driver had been loaded, not that a card was detected (similarly, the > ath_hal messages). Tried no acpi 2 or 3 times, no difference Tried safe mode 2 or 3 times, no difference I notice that if I go into the loader prompt mode, it says acpi is YES, ignoring the =NO in loader.conf. It does pick up the hint.de.0.disabled="1" stuff, so I know it is reading the file. 6.0 booted okay. 6.2 boots okay with no irq/interrupt issues, no "attach returned 6". NetBSD 3.0.1 booted okay. NetBSD 4.0 boots okay. Even that penguin thing boots. So 7.0 is getting something wrong with the irq/interrupts. Did anything APIC (Advanced Programmable Interrupt Controller) related change from 6.x to 7.0 ? From: Dieter To: gavin@FreeBSD.org Cc: bug-followup@FreeBSD.org Subject: Re: kern/122174: [panic] 7.0 panics on amd64 Tyan 2865 Date: Sun, 30 Mar 2008 17:46:09 +0100 Found the following in acpi(4) man page hw.acpi.serialize_methods Allow override of whether methods execute in parallel or not. Enable this for serial behavior, which fixes "AE_ALREADY_EXISTS" But hint.acpi.0.disabled="0" hw.acpi.verbose="1" hw.acpi.serialize_methods="1" hint.apic.0.disabled=1 still gives kbd1 at kbdmux0 acpi0: on motherboard acpi0: could not allocate interrupt ACPI Exception (evevent-0257): AE_ALREADY_EXISTS, Unable to install System Control Interrupt handler [200 70320] acpi0: Could not enable ACPI: AE_ALREADY_EXISTS device_attach: acpi0 attach returned 6 cpu0 on motherboard powernow0: on cpu0 device_attach: powernow0 attach returned 6 ---- Also tried hint.acpi.0.disabled="0" hw.acpi.verbose="1" hw.acpi.serialize_methods="1" hint.apic.0.disabled="0" hw.apic.enable_extint="1" ---- Also tried hint.acpi.0.disabled="1" hw.acpi.verbose="1" hw.acpi.serialize_methods="1" hint.apic.0.disabled="0" hw.apic.enable_extint="1" which gave: kbd1 at kbdmux0 cpu0 on motherboard powernow0: on cpu0 device_attach: powernow0 attach returned 6 pcib0: pcibus 0 on motherboard pci0: on pcib0 pci0: at device 0.0 (no driver attached) isab0: at device 1.0 on pci0 isa0: on isab0 pci0: at device 1.1 (no driver attached) Finally got rid of the AE_ALREADY_EXISTS, but still getting "attach returned 6" and "no driver attached". ---- Also tried hint.acpi.0.disabled="1" hw.acpi.verbose="1" hw.acpi.serialize_methods="1" hint.apic.0.disabled="1" hw.apic.enable_extint="1" ---- Also tried hint.acpi.0.disabled="1" hw.acpi.verbose="1" hw.acpi.serialize_methods="1" hint.apic.0.disabled="0" hw.apic.enable_extint="0" ---- Turned verbose on, powernow0 prints a bit more with acpi disabled, but still finishes with "attach returned 6". kbd: new array size 4 kbd1 at kbdmux0 mem: null: random: io: cpu0 on motherboard powernow0: on cpu0 powernow0: STATUS: 0x12040606040a0a0a powernow0: STATUS: maxfid: 0x0a powernow0: STATUS: maxvid: 0x04 device_attach: powernow0 attach returned 6 pcib0: pcibus 0 on motherboard pci0: on pcib0 pci0: domain=0, physical bus=0 found-> vendor=0x10de, dev=0x005e, revid=0xa3 domain=0, bus=0, slot=0, func=0 class=05-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x0050, revid=0xa3 domain=0, bus=0, slot=1, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x000f, statreg=0x00a0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x0 From: Gavin Atkinson To: Dieter Cc: bug-followup@FreeBSD.org Subject: Re: kern/122174: [panic] 7.0 panics on amd64 Tyan 2865 Date: Mon, 31 Mar 2008 11:12:08 +0100 Can you please confirm that you are running with the most recent BIOS? Also, are you able to attempt to boot a 6.3-RELEASE CD, to see if that works? Thanks, Gavin From: Gavin Atkinson To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/122174: [panic] 7.0 panics on amd64 Tyan 2865 Date: Mon, 31 Mar 2008 14:05:38 +0100 Have also asked for the verbose dmesg and the output of "mptable" and "acpidump -t" under 6.x. From: Dieter To: Gavin Atkinson Cc: bug-followup@FreeBSD.org Subject: Re: kern/122174: [panic] 7.0 panics on amd64 Tyan 2865 Date: Mon, 31 Mar 2008 10:50:07 +0100 > Can you please confirm that you are running with the most recent BIOS? It is not the most recent firmware, but this board does not have a failsafe loader or a dual bios feature, so updating the firmware has been deemed too risky. > Also, are you able to attempt to boot a 6.3-RELEASE CD, to see if that > works? Yes, but it will probably take awhile. Here is "mptable -verbose" under 6.2: =============================================================================== MPTable looking for EBDA pointer @ 0x040e, found, searching EBDA @ 0x0009f800 searching CMOS 'top of mem' @ 0x00098c00 (611K) searching default 'top of mem' @ 0x0009fc00 (639K) searching BIOS @ 0x000f0000 MP FPS found in BIOS @ physical addr: 0x000f3a10 ------------------------------------------------------------------------------- MP Floating Pointer Structure: location: BIOS physical address: 0x000f3a10 signature: '_MP_' length: 16 bytes version: 1.1 checksum: 0x00 mode: Virtual Wire ------------------------------------------------------------------------------- MP Config Table Header: physical address: 0x000f1e10 signature: '' base table length: 0 version: 1.0 checksum: 0x00 OEM ID: '' Product ID: '' OEM table pointer: 0x00000000 OEM table size: 0 entry count: 0 local APIC address: 0x00000000 extended table length: 0 extended table checksum: 0 ------------------------------------------------------------------------------- MP Config Base Table Entries: =============================================================================== "acpidump -t" under 6.2: /* RSD PTR: OEM=Nvidia, ACPI_Rev=1.0x (0) RSDT=0x7fff3040, cksum=152 */ /* RSDT: Length=44, Revision=1, Checksum=178, OEMID=Nvidia, OEM Table ID=AWRDACPI, OEM Revision=0x42302e31, Creator ID=AWRD, Creator Revision=0x0 Entries={ 0x7fff30c0, 0x7fff93c0 } */ /* FACP: Length=116, Revision=1, Checksum=217, OEMID=Nvidia, OEM Table ID=AWRDACPI, OEM Revision=0x42302e31, Creator ID=AWRD, Creator Revision=0x0 FACS=0x7fff0000, DSDT=0x7fff3180 INT_MODEL=PIC Preferred_PM_Profile=Unspecified (0) SCI_INT=9 SMI_CMD=0x142e, ACPI_ENABLE=0xa1, ACPI_DISABLE=0xa0, S4BIOS_REQ=0x0 PSTATE_CNT=0x0 PM1a_EVT_BLK=0x1000-0x1003 PM1a_CNT_BLK=0x1004-0x1005 PM2_CNT_BLK=0x101c-0x101c PM_TMR_BLK=0x1008-0x100b GPE0_BLK=0x1020-0x1027 GPE1_BLK=0x14a0-0x14af, GPE1_BASE=32 P_LVL2_LAT=101 us, P_LVL3_LAT=1001 us FLUSH_SIZE=0, FLUSH_STRIDE=0 DUTY_OFFSET=1, DUTY_WIDTH=3 DAY_ALRM=125, MON_ALRM=126, CENTURY=50 IAPC_BOOT_ARCH= Flags={WBINVD,PROC_C1,SLP_BUTTON,RTC_S4,RESET_REG} RESET_REG=0x00000000:0[0] (Memory), RESET_VALUE=0 */ /* FACS: Length=64, HwSig=0x00000000, Firm_Wake_Vec=0x00000000 Global_Lock= Flags= Version=0 */ /* DSDT: Length=24875, Revision=1, Checksum=252, OEMID=NVIDIA, OEM Table ID=AWRDACPI, OEM Revision=0x1000, Creator ID=MSFT, Creator Revision=0x100000e */ /* MCFG: Length=60, Revision=1, Checksum=34, OEMID=Nvidia, OEM Table ID=AWRDACPI, OEM Revision=0x42302e31, Creator ID=AWRD, Creator Revision=0x0 Base Address= 0x00000000e0000000 Segment Group= 0x0000 Start Bus= 0 End Bus= 255 */ ============================================================================= devinfo under 6.2 says: Interrupt request lines: 0x0 (root0) 0x1 (atkbd0) 0x3 (sio1) 0x4 (sio0) 0x5 (ohci2) 0x6 (fdc0) 0x7 (ppc0) 0x8 (root0) 0x9 (acpi0) 0xa (ohci0) 0xb (ehci0) 0xc (fwohci1) 0xd (root0) 0xe (ata0) 0xf (ata1) so I added this to 7.0's loader.conf hint.root.0.irq="0x0" hint.atkbd.0.irq="0x1" hint.sio.1.irq="0x3" hint.sio.0.irq="0x4" hint.ohci.2.irq="0x5" hint.fdc.0.irq="0x6" hint.ppc.0.irq="0x7" #hint.root.0.irq=0x8" hint.acpi.0.irq="0x9" hint.ohci.0.irq="0xa" hint.ehci.0.irq="0xb" hint.fwohci.1.irq="0xc" #hint.root.0.irq="0xd" hint.ata.0.irq="0xe" hint.ata.1.irq="0xf" I'm not sure what to do about the multiple root0 entries. And there are lots of devices not listed. Anyway it didn't help. ============================================================================= 6.2's loader says: acpi_load=YES autoboot_delay=NO bootfile=kernel comconsole_speed=9600 console=comconsole currdev=disk3s3a: hint.acpi.0.oem=Nvidia hint.acpi.0.revision=1 hint.acpi.0.rsdt=0x7fff3040 hint.atkbd.0.at=atkbdc hint.atkbd.0.irq=1 hint.atkbdc.0.at=isa hint.atkbdc.0.port=0x060 hint.fd.0.at=fdc0 hint.fd.0.drive=0 hint.fd.1.at=fdc0 hint.fd.1.drive=1 hint.fdc.0.at=isa hint.fdc.0.drq=2 hint.fdc.0.irq=6 hint.fdc.0.port=0x3F0 hint.ppc.0.at=isa hint.ppc.0.irq=7 hint.psm.0.at=atkbdc hint.psm.0.irq=12 hint.sc.0.at=isa hint.sc.0.flags=0x100 hint.sio.0.at=isa hint.sio.0.flags=0x10 hint.sio.0.irq=4 hint.sio.0.port=0x3F8 hint.sio.1.at=isa hint.sio.1.irq=3 hint.sio.1.port=0x2F8 hint.sio.2.at=isa hint.sio.2.disabled=1 hint.sio.2.irq=5 hint.sio.2.port=0x3E8 hint.sio.3.at=isa hint.sio.3.disabled=1 hint.sio.3.irq=9 hint.sio.3.port=0x2E8 hint.vga.0.at=isa hw.ata.atapi_dma=1 hw.ata.wc=0 interpret=OK kern.ipc.nmbclusters=256000 kernel=kernel kernel_options= kernelname=/boot/kernel/kernel loaddev=disk3s3a: mac_ifoff=NO module_path=/boot/kernel;/boot/modules prompt=${interpret} smbios.bios.reldate=02/17/2005 smbios.bios.vendor=Phoenix Technologies, LTD smbios.bios.version=6.00 PG smbios.chassis.maker= smbios.chassis.serial= smbios.chassis.tag= smbios.chassis.version= smbios.planar.maker= smbios.planar.product=NF-CK804 smbios.planar.serial= smbios.planar.version= smbios.socket.enabled=1 smbios.socket.populated=1 smbios.system.maker= smbios.system.product= smbios.system.serial= smbios.system.version= 6.2 verbose boot ================================================ SMAP type=01 base=0000000000000000 len=0000000000098000 SMAP type=02 base=00000000000f0000 len=0000000000010000 SMAP type=02 base=00000000fec00000 len=0000000000001000 SMAP type=02 base=00000000fee00000 len=0000000000100000 SMAP type=02 base=00000000fefffc00 len=0000000000000400 SMAP type=02 base=00000000ffff0000 len=0000000000010000 SMAP type=02 base=00000000e0000000 len=0000000010000000 SMAP type=03 base=000000007fff3000 len=000000000000d000 SMAP type=04 base=000000007fff0000 len=0000000000003000 SMAP type=02 base=0000000000098000 len=0000000000008000 SMAP type=01 base=0000000000100000 len=000000007fef0000 ... real memory = 2147418112 (2047 MB) Physical memory chunk(s): 0x0000000000001000 - 0x0000000000097fff, 618496 bytes (151 pages) 0x0000000000b53000 - 0x000000007c39ffff, 2072301568 bytes (505933 pages) avail memory = 2036805632 (1942 MB) wlan: <802.11 Link Layer> ath_rate: version 1.2 null: random: nfslock: pseudo-device kbd: new array size 4 kbd1 at kbdmux0 mem: io: ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) rr232x: RocketRAID 232x controller driver v1.02 (Dec 1 2007 17:12:54) stray irq7 acpi0: on motherboard acpi0: [MPSAFE] pci_open(1): mode 1 addr port (0x0cf8) is 0x80004004 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=058000] [hdr=00] is there (id=005e10de) acpi_bus_number: root bus has no _BBN, assuming 0 acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR AcpiOsDerivePciId: bus 0 dev 1 func 1 acpi_bus_number: root bus has no _BBN, assuming 0 acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR AcpiOsDerivePciId: bus 0 dev 1 func 0 acpi0: Power Button (fixed) acpi_bus_number: root bus has no _BBN, assuming 0 acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR AcpiOsDerivePciId: bus 0 dev 24 func 1 acpi_bus_number: root bus has no _BBN, assuming 0 acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR AcpiOsDerivePciId: bus 0 dev 1 func 0 ACPI timer: 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 -> 10 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 pci_link0: Links after initial probe: Index IRQ Rtd Ref IRQs 0 10 N 0 3 4 5 7 9 10 11 12 14 15 pci_link0: Links after initial validation: Index IRQ Rtd Ref IRQs 0 10 N 0 3 4 5 7 9 10 11 12 14 15 pci_link0: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link1: Links after initial probe: Index IRQ Rtd Ref IRQs 0 5 N 0 3 4 5 7 9 10 11 12 14 15 pci_link1: Links after initial validation: Index IRQ Rtd Ref IRQs 0 5 N 0 3 4 5 7 9 10 11 12 14 15 pci_link1: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link2: Links after initial probe: Index IRQ Rtd Ref IRQs 0 11 N 0 3 4 5 7 9 10 11 12 14 15 pci_link2: Links after initial validation: Index IRQ Rtd Ref IRQs 0 11 N 0 3 4 5 7 9 10 11 12 14 15 pci_link2: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link3: Links after initial probe: Index IRQ Rtd Ref IRQs 0 12 N 0 3 4 5 7 9 10 11 12 14 15 pci_link3: Links after initial validation: Index IRQ Rtd Ref IRQs 0 12 N 0 3 4 5 7 9 10 11 12 14 15 pci_link3: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link4: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link4: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link4: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link5: Links after initial probe: Index IRQ Rtd Ref IRQs 0 10 N 0 3 4 5 7 9 10 11 12 14 15 pci_link5: Links after initial validation: Index IRQ Rtd Ref IRQs 0 10 N 0 3 4 5 7 9 10 11 12 14 15 pci_link5: Links IRQ Rtd Ref IRQs 0 5 N 0 3 4 5 7 9 10 11 12 14 15 pci_link7: Links after initial validation: Index IRQ Rtd Ref IRQs 0 5 N 0 3 4 5 7 9 10 11 12 14 15 pci_link7: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link8: Links after initial probe: Index IRQ Rtd Ref IRQs 0 12 N 0 3 4 5 7 9 10 11 12 14 15 pci_link8: Links after initial validation: Index IRQ Rtd Ref IRQs 0 12 N 0 3 4 pci_link10: Links after initial probe: Index IRQ Rtd Ref IRQs 0 12 N 0 3 4 5 7 9 10 11 12 14 15 pci_link10: Links after initial validation: Index IRQ Rtd Ref IRQs 0 12 N 0 3 4 5 7 9 10 11 12 14 15 pci_link10: Linksink12: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link13: Links after initial probe: Index IRQ Rtd Ref IRQs 0 11 N 0 3 4 5 7 9 10 11 12 14 15 pci_link13: Links after initial vald Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link14: Links after initial probe: Index IRQ Rtd Ref IRQs 0 10 N 0 3 4 5 7 9 10 11 12 14 15 pci_link14: Links after initial validation: Index IRQ Rtd Ref IRQs 0inks after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 16 pci_link16: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 16 pci_link16: Links after disable: Index IRQ Rtd Ref IRQs 0 255 Ninitial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 19 pci_link19: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 19 pci_link19: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 19 pci_link20: Links after initial probe: Index IRQ Rtd Ref IRQs 0 16 N 0 16 pci_link20: Links after initial validation: Index IRQ Rtd Ref IRQs 0 16 N 0 16 pci_link20: Links after disable: Index IRQ Rtd Ref IRQs 2: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link23: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link23: Links after initial validation: Index IRQ Rtd Refndex IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link25: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link26: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link26: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link26: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link27: Links after initial probe: Index 0 20 21 22 23 pci_link29: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link29: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link29: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link30: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link30: Links after initial validation: Index IRQ Rtd Ref IRQs 0 acpi_throttle0: on cpu0 acpi_throttle0: P_CNT from P_BLK 0x1010 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 ACPI: Found matching pin for 0.1.INTA at func 1: 12 ACPI: Found matchireg=0x000f, statreg=0x00a0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x0052, revid=0xa2 bus=0, slot=1, func=1 class=0c-05-00, hdrtype=0x00, mfdev=1 cmdreg=0x0001, statreg=0x00b0, ts D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base febff000, size 12, enabled pcib0: matched entry for 0.2.INTA (src \_SB_.PCI0.LUBA:0) pcib0: slot 2 INTA routed to irq 10 via \_SB_.PCI0.LUBA found-> vendor=0x10de, dev=0x005b, revid=0xa3 bus3 current D0 map[10]: type 4, range 32, base 0000f000, size 8, enabled map[14]: type 4, range 32, base 0000ec00, size 8, enabled map[18]: type 1, range 32, base febfd000, size 12, enabled Icib0: matched entry for 0.4.INTA (src \_SB_.PCI0.LACI:0) found-> vendor=0x10de, dev=0x0053, revid=0xa2 bus=0, slot=6, func=0 class=01-01-8a, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) powerspec 2 support 00000970, size 3, enabled map[1c]: type 4, range 32, base 00000b70, size 2, enabled map[20]: type 4, range 32, base 0000cc00, size 4, enabled map[24]: type 1, range 32, base febfb000, size 12, enabled pcib0: matched entry for 0.7.INTA (src \_SB_e 12, enabled pcib0: matched entry for 0.8.INTA (src \_SB_.PCI0.LFID:0) pcib0: slot 8 INTA routed to irq 10 via \_SB_.PCI0.LFID found-> vendor=0x10de, dev=0x005c, revid=0xa2 bus=0, slot=9, func=0 class=06-04-01, hdrtype=0x01, mfdev=0 cmdreg=0x0007er=0x00 (0 ns), mingnt=0x0c (3000 ns), maxlat=0x02 (500 ns) found-> vendor=0x10de, dev=0x0057, revid=0xa3 bus=0, slot=10, func=0 class=06-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt2, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0007, statreg=0x0010, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x005d, revid=0xa3 bus=0, slot=13, func=0 class=06-04-pe=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1102, revid=0x00 bus=0, slot=24, func=2 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0ttimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1103, revid=0x00 bus=0, slot=24, func=3 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt= ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 10 ports with 10 removable, self powered ehci0: mem 0xfebfe000-0xfebfe0ff irq 11 at device 2.1 on pci0 ehci0: Reserved 0x100 bytes for rid 0x10 type 3 at 0xfebfe000 ehci0: [GIANT-LOCKED] usb1: EHCI version 1.0 usb1: companion controller, 4 ports each: usb0 usb1: on ehci0 usb1: USB revision 2.0 uhub1: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub1: 10 ports with 10 removable, self powered umass0: JMicron USB to ATA/ATAPI Bridge, rev 2.00/1.00, addr 2 umass0:0:0:-1: Attached to scbus0 pci0: at device 4.0 (no driver attached) atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xe000-0xe00f at device 6.0 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xe000 ata0: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 ata0: reset tp1 mask=03 ostat0=50 ostat1=00 ata0: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata0: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 ata0: reset tp2 stat0=00 stat1=00 devices=0x4 ata0: [MPSAFE] ata1: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 ata1: reset tp1 mask=03 ostat0=50 ostat1=00 ata1: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata1: stat1=0x00 err=0x01 lsb=0x00 msb=0x00 ata1: reset tp2 stat0=50 stat1=00 devices=0x1 ata1: [MPSAFE] atapci1: port 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0x cc00-0xcc0f mem 0xfebfb000-0xfebfbfff irq 11 at device 7.0 on pci0 atapci1: Reserved 0x10 bytes for rid 0x20 type 4 at 0xcc00 atapci1: [MPSAFE] atapci1: Reserved 0x1000 bytes for rid 0x24 type 3 at 0xfebfb000 ata2: on atapci1 atapci1: Reserved 0x8 bytes for rid 0x10 type 4 at 0x9f0 atapci1: Reserved 0x4 bytes for rid 0x14 type 4 at 0xbf0 ata2: SATA connect ready time=0ms ata2: sata_connect devices=0x1 ata2: [MPSAFE] ata3: on atapci1 atapci1: Reserved 0x8 bytes for rid 0x18 type 4 at 0x970 atapci1: Reserved 0x4 bytes for rid 0x1c type 4 at 0xb70 ata3: SATA connect ready time=0ms ata3: sata_connect devices=0x1 ata3: [MPSAFE] atapci2: port 0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0x b800-0xb80f mem 0xfebfa000-0xfebfafff irq 10 at device 8.0 on pci0 atapci2: Reserved 0x10 bytes for rid 0x20 type 4 at 0xb800 atapci2: [MPSAFE] atapci2: Reserved 0x1000 bytes for rid 0x24 type 3 at 0xfebfa000 ata4: on atapci2 atapci2: Reserved 0x8 bytes for rid 0x10 type 4 at 0x9e0 atapci2: Reserved 0x4 bytes for rid 0x14 type 4 at 0xbe0 ata4: SATA connect ready time=0ms ata4: sata_connect devices=0x1 ata4: [MPSAFE] ata5: on atapci2 atapci2: Reserved 0x8 bytes for rid 0x18 type 4 at 0x960 atapci2: Reserved 0x4 bytes for rid 0x1c type 4 at 0xb60 ata5: SATA connect ready time=0ms ata5: sata_connect devices=0x1 ata5: [MPSAFE] pcib1: at device 9.0 on pci0 pcib1: secondary bus 1 pcib1: subordinate bus 2 pcib1: I/O decode 0x9000-0xafff pcib1: memory decode 0xf8000000-0xfdffffff pcib1: prefetched decode 0xfea00000-0xfeafffff pcib1: Subtractively decoded bridge. ACPI: Found matching pin for 1.5.INTA at func 0: 12 ACPI: Found matching pin for 1.6.INTA at func 0: 11 ACPI: Found matching pin for 1.7.INTA at func 0: 10 ACPI: Found matching pin for 1.9.INTA at func 0: 11 ACPI: Found matching pin for 1.10.INTA at func 0: 5 pci1: on pcib1 pci1: physical bus=1 found-> vendor=0x1002, dev=0x4752, revid=0x27 bus=1, slot=5, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0087, statreg=0x0290, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x08 (2000 ns), maxlat=0x00 (0 ns) intpin=a, irq=12 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base fc000000, size 24, enabled pcib1: (null) requested memory range 0xfc000000-0xfcffffff: good map[14]: type 4, range 32, base 0000ac00, size 8, enabled pcib1: (null) requested I/O range 0xac00-0xacff: in range map[18]: type 1, range 32, base fdfff000, size 12, enabled pcib1: (null) requested memory range 0xfdfff000-0xfdffffff: good pcib1: matched entry for 1.5.INTA (src \_SB_.PCI0.LNK4:0) pcib1: slot 5 INTA routed to irq 12 via \_SB_.PCI0.LNK4 found-> vendor=0x1106, dev=0x3044, revid=0x80 bus=1, slot=6, func=0 class=0c-00-10, hdrtype=0x00, mfdev=0 cmdreg=0x0087, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x20 (8000 ns) intpin=a, irq=11 powerspec 2 supports D0 D2 D3 current D0 map[10]: type 1, range 32, base fdffe000, size 11, enabled pcib1: (null) requested memory range 0xfdffe000-0xfdffe7ff: good map[14]: type 4, range 32, base 0000a800, size 7, enabled pcib1: (null) requested I/O range 0xa800-0xa87f: in range pcib1: matched entry for 1.6.INTA (src \_SB_.PCI0.LNK3:0) pcib1: slot 6 INTA routed to irq 11 via \_SB_.PCI0.LNK3 found-> vendor=0x14f1, dev=0x8800, revid=0x05 bus=1, slot=7, func=0 class=04-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0006, statreg=0x0290, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x14 (5000 ns), maxlat=0x37 (13750 ns) intpin=a, irq=10 powerspec 2 supports D0 D3 current D0 map[10]: type 1, range 32, base f9000000, size 24, enabled pcib1: (null) requested memory range 0xf9000000-0xf9ffffff: good pcib1: matched entry for 1.7.INTA (src \_SB_.PCI0.LNK1:0) pcib1: slot 7 INTA routed to irq 10 via \_SB_.PCI0.LNK1 found-> vendor=0x14f1, dev=0x8802, revid=0x05 bus=1, slot=7, func=2 class=04-80-00, hdrtype=0x00, mfdev=1 cmdreg=0x0006, statreg=0x0290, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x06 (1500 ns), maxlat=0x58 (22000 ns) intpin=a, irq=10 powerspec 2 supports D0 D3 current D0 map[10]: type 1, range 32, base f8000000, size 24, enabled pcib1: (null) requested memory range 0xf8000000-0xf8ffffff: good pcib1: matched entry for 1.7.INTA (src \_SB_.PCI0.LNK1:0) pcib1: slot 7 INTA routed to irq 10 via \_SB_.PCI0.LNK1 found-> vendor=0x3388, dev=0x0021, revid=0x11 bus=1, slot=8, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0007, statreg=0x0290, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns) found-> vendor=0x14f1, dev=0x8800, revid=0x05 bus=1, slot=9, func=0 class=04-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0006, statreg=0x0290, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x14 (5000 ns), maxlat=0x37 (13750 ns) intpin=a, irq=11 powerspec 2 supports D0 D3 current D0 map[10]: type 1, range 32, base fb000000, size 24, enabled pcib1: (null) requested memory range 0xfb000000-0xfbffffff: good pcib1: matched entry for 1.9.INTA (src \_SB_.PCI0.LNK3:0) pcib1: slot 9 INTA routed to irq 11 via \_SB_.PCI0.LNK3 found-> vendor=0x14f1, dev=0x8802, revid=0x05 bus=1, slot=9, func=2 class=04-80-00, hdrtype=0x00, mfdev=1 cmdreg=0x0006, statreg=0x0290, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x06 (1500 ns), maxlat=0x58 (22000 ns) intpin=a, irq=11 powerspec 2 supports D0 D3 current D0 map[10]: type 1, range 32, base fa000000, size 24, enabled pcib1: (null) requested memory range 0xfa000000-0xfaffffff: good pcib1: matched entry for 1.9.INTA (src \_SB_.PCI0.LNK3:0) pcib1: slot 9 INTA routed to irq 11 via \_SB_.PCI0.LNK3 found-> vendor=0x1011, dev=0x0002, revid=0x24 bus=1, slot=10, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=5 map[10]: type 4, range 32, base 0000a400, size 7, enabled pcib1: (null) requested I/O range 0xa400-0xa47f: in range map[14]: type 1, range 32, base fdffd000, size 7, enabled pcib1: (null) requested memory range 0xfdffd000-0xfdffd07f: good pcib1: matched entry for 1.10.INTA (src \_SB_.PCI0.LNK2:0) pcib1: slot 10 INTA routed to irq 5 via \_SB_.PCI0.LNK2 pci1: at device 5.0 (no driver attached) ... ata0-master: pio=PIO4 wdma=WDMA2 udma=UDMA66 cable=80 wire acd0: setting PIO4 on nForce CK804 chip acd0: setting UDMA66 on nForce CK804 chip acd0: DVDR drive at ata0 as master acd0: read 6890KB/s (6890KB/s) write 6890KB/s (6890KB/s), 2048KB buffer, UDMA66 acd0: Reads: CDR, CDRW, CDDA stream, DVDROM, DVDR, DVDRAM, packet acd0: Writes: CDR, CDRW, DVDR, DVDRAM, test write, burnproof acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray, unlocked acd0: Medium: no/blank disc ata1-master: pio=PIO4 wdma=WDMA2 udma=UDMA100 cable=80 wire ad2: setting PIO4 on nForce CK804 chip ad2: setting UDMA100 on nForce CK804 chip ad2: 305245MB at ata1-master UDMA100 ad2: 625142448 sectors [620181C/16H/63S] 16 sectors/interrupt 1 depth queue GEOM: new disk ad2 ad2: nVidia check1 failed ad2: Adaptec check1 failed ad2: LSI (v3) check1 failed ad2: LSI (v2) check1 failed ad2: FreeBSD check1 failed ata2-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire ad4: 715404MB at ata2-master SATA300 ad4: 1465149168 sectors [1453521C/16H/63S] 16 sectors/interrupt 1 depth queue GEOM: new disk ad4 ad4: nVidia check1 failed ad4: Adaptec check1 failed ad4: LSI (v3) check1 failed ad4: LSI (v2) check1 failed ad4: FreeBSD check1 failed ata3-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire ad6: 715404MB at ata3-master SATA300 ad6: 1465149168 sectors [1453521C/16H/63S] 16 sectors/interrupt 1 depth queue ad6: nVidia check1 failed ad6: Adaptec check1 failed ad6: LSI (v3) check1 failed fdc0: output ready timeout fdc0: input ready timeout fdc0: input ready timeout fdc0: output ready timeout fdc0: input ready timeout fdc0: input ready timeout GEOM: new disk ad6 fdc0: output ready timeout fdc0: input ready timeout fdc0: input ready timeout fdc0: output ready timeout fdc0: input ready timeout fdc0: input ready timeout ad6: LSI (v2) check1 failed ad6: FreeBSD check1 failed ata4-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire ad8: 476940MB at ata4-master SATA300 ad8: 976773168 sectors [969021C/16H/63S] 16 sectors/interrupt 1 depth queue (probe0:ata0:0:0:0): error 22 (probe0:ata0:0:0:0): Unretryable Error ad8: nVidia check1 failed ad8: Adaptec check1 failed ad8: LSI (v3) check1 failed ad8: LSI (v2) check1 failed ad8: FreeBSD check1 failed ata5-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire GEOM: new disk ad8 ad10: 715404MB at ata5-master SATA300 ad10: 1465149168 sectors [1453521C/16H/63S] 16 sectors/interrupt 1 depth queue ad10: nVidia check1 failed ad10: Adaptec check1 failed ad10: LSI (v3) check1 failed ad10: LSI (v2) check1 failed ad10: FreeBSD check1 failed GEOM: new(probe15:ata0:0:0:0): error 6 (probe15:ata0:0:0:0): Unretryable Error disk ad10 (probe15:ata0:0:0:0): error 22 (probe15:ata0:0:0:0): Unretryable Error (probe1:sbp0:0:0:0): error 22 (probe1:sbp0:0:0:0): Unretryable Error (probe2:sbp0:0:1:0): error 22 (probe2:sbp0:0:1:0): Unretryable Error (probe3:sbp0:0:2:0): error 22 (probe3:sbp0:0:2:0): Unretryable Error (probe4:sbp0:0:3:0): error 22 (probe4:sbp0:0:3:0): Unretryable Error (probe5:sbp0:0:4:0): error 22 (probe5:sbp0:0:4:0): Unretryable Error (probe6:sbp0:0:5:0): error 22 (probe6:sbp0:0:5:0): Unretryable Error (probe7:sbp0:0:6:0): error 22 (probe7:sbp0:0:6:0): Unretryable Error (probe8:sbp1:0:0:0): error 22 (probe8:sbp1:0:0:0): Unretryable Error (probe9:sbp1:0:1:0): error 22 (probe9:sbp1:0:1:0): Unretryable Error (probe10:sbp1:0:2:0): error 22 (probe10:sbp1:0:2:0): Unretryable Error (probe11:sbp1:0:3:0): error 22 (probe11:sbp1:0:3:0): Unretryable Error (probe12:sbp1:0:4:0): error 22 (probe12:sbp1:0:4:0): Unretryable Error (probe13:sbp1:0:5:0): error 22 (probe13:sbp1:0:5:0): Unretryable Error (probe14:sbp1:0:6:0): error 22 (probe14:sbp1:0:6:0): Unretryable Error pass0 at umass-sim0 bus 0 target 0 lun 0 pass0: Fixed Direct Access SCSI-2 device pass0: Serial Number pass0: 40.000MB/s transfers pass1 at ata0 bus 0 target 0 lun 0 pass1: Removable CD-ROM SCSI-0 device pass1: 66.000MB/s transfers GEOda0 at umass-sim0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: Serial Number da0: 40.000MB/s transfers da0: 238475MB (488397168 512 byte sectors: 255H 63S/T 30401C) (cd0:ata0:0:0:0): error 6 (cd0:ata0:0:0:0): Unretryable Error cd0 at ata0 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 66.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present M: new disk da0 GEOM: new disk cd0 ATA PseudoRAID loaded (cd0:ata0:0:0:0): error 6 (cd0:ata0:0:0:0): Unretryable Error (cd0:ata0:0:0:0): error 6 (cd0:ata0:0:0:0): Unretryable Error (cd0:ata0:0:0:0): error 6 (cd0:ata0:0:0:0): Unretryable Error Trying to mount root from ufs:/dev/ad8s3a Looks like I have a flow control problem somewhere. :-( There is no floppy drive, and the CD drive has no disk in it. It thinks that SATA cables have 40 wires. I see lots of errors and such, yet the disks work under 6.2. From: John Baldwin To: bug-followup@freebsd.org, freebsd@sopwith.solgatos.com Cc: peter@freebsd.org Subject: Re: kern/122174: [panic] 7.0 fails to allocate interrupts on amd64 Tyan 2865 Date: Mon, 31 Mar 2008 17:10:00 -0400 7.0 doesn't include 'device atpic' in the amd64 GENERIC meaning that FreeBSD/amd64 7.0 basically requires APIC to work. 6.x still has 'atpic' in GENERIC which is why it worked. There really should not be any amd64 machines w/o APIC support such as this one. Peter (cc'd) was the one who turned off 'atpic' in 7. -- John Baldwin From: Dieter To: John Baldwin Cc: bug-followup@freebsd.org, peter@freebsd.org, gavin@freebsd.org Subject: Re: kern/122174: [panic] 7.0 fails to allocate interrupts on amd64 Tyan 2865 Date: Mon, 31 Mar 2008 18:45:22 +0100 > 7.0 doesn't include 'device atpic' in the amd64 GENERIC meaning that > FreeBSD/amd64 7.0 basically requires APIC to work. 6.x still has 'atpic' in > GENERIC which is why it worked. There really should not be any amd64 > machines w/o APIC support such as this one. Peter (cc'd) was the one who > turned off 'atpic' in 7. Ladys and gentlemen, we have a winner! I added 'device atpic' to the config file and a couple attempts later I had a 7.0 shell prompt. Thank you! Suggestion: next time you do something like this, please put a notice in the release notes. From: Dieter To: gavin@FreeBSD.org Cc: bug-followup@FreeBSD.org Subject: Re: kern/122174: [panic] 7.0 panics on amd64 Tyan 2865 Date: Tue, 01 Apr 2008 08:46:05 +0100 > OK, given it boots without the de(4) driver in the kernel, my guess is > that those issues are related to PR kern/120915. Now, with 'device atpic', and patch #1 from PR 120915, kldload if_de works, no panic, and the interface works. Thanks for your help. From: "Peter Wemm" To: freebsd@sopwith.solgatos.com Cc: "John Baldwin" , bug-followup@freebsd.org, gavin@freebsd.org Subject: Re: kern/122174: [panic] 7.0 fails to allocate interrupts on amd64 Tyan 2865 Date: Tue, 1 Apr 2008 14:44:51 -0700 On Mon, Mar 31, 2008 at 10:45 AM, Dieter wrote: > > > 7.0 doesn't include 'device atpic' in the amd64 GENERIC meaning that > > FreeBSD/amd64 7.0 basically requires APIC to work. 6.x still has 'atpic' in > > GENERIC which is why it worked. There really should not be any amd64 > > machines w/o APIC support such as this one. Peter (cc'd) was the one who > > turned off 'atpic' in 7. > > Ladys and gentlemen, we have a winner! > > I added 'device atpic' to the config file and a couple attempts later > I had a 7.0 shell prompt. I have a question.. what sort of machine is this? I'm not aware of any machines that we can run on that don't have an APIC - but I know that many of them can have "IO APIC" disabled in the bios. I've seen bioses that do stupid things like attempting to preconfigure the machine based on the partition type in the MBR. eg: there are certain ASUS boards that turn off USB emulation of the keyboard unless it recognizes the MBR type, or if you boot from floppy / cdrom. > Thank you! > > Suggestion: next time you do something like this, please put a notice in the > release notes. > -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 "If Java had true garbage collection, most programs would delete themselves upon execution." -- Robert Sewell **WANTED TO BUY: Garmin Streetpilot 2650 or 2660. Not later model! ** From: Dieter To: "Peter Wemm" Cc: "John Baldwin" , bug-followup@freebsd.org, gavin@freebsd.org Subject: Re: kern/122174: [panic] 7.0 fails to allocate interrupts on amd64 Tyan 2865 Date: Tue, 01 Apr 2008 15:16:59 +0100 > > > 7.0 doesn't include 'device atpic' in the amd64 GENERIC meaning that > > > FreeBSD/amd64 7.0 basically requires APIC to work. 6.x still has 'atpic' in > > > GENERIC which is why it worked. There really should not be any amd64 > > > machines w/o APIC support such as this one. Peter (cc'd) was the one who > > > turned off 'atpic' in 7. > > > > Ladys and gentlemen, we have a winner! > > > > I added 'device atpic' to the config file and a couple attempts later > > I had a 7.0 shell prompt. > > I have a question.. what sort of machine is this? I'm not aware of > any machines that we can run on that don't have an APIC - but I know > that many of them can have "IO APIC" disabled in the bios. Mainboard is Tyan Tomcat k8e 2865 http://www.tyan.com/products/html/tomcatk8e.html (hopefully the URL still works) Is the APIC part of the nforce4-ultra chipset? (nearly everything else seems to be in there) If the bios disables "IO APIC", can the kernel turn it back on? I had tried both hint.apic.0.disabled="0" and hint.apic.0.disabled="1" but it didn't help. From: "Peter Wemm" To: freebsd@sopwith.solgatos.com Cc: "John Baldwin" , bug-followup@freebsd.org, gavin@freebsd.org Subject: Re: kern/122174: [panic] 7.0 fails to allocate interrupts on amd64 Tyan 2865 Date: Tue, 1 Apr 2008 15:44:53 -0700 On Tue, Apr 1, 2008 at 7:16 AM, Dieter wrote: > > > > 7.0 doesn't include 'device atpic' in the amd64 GENERIC meaning that > > > > FreeBSD/amd64 7.0 basically requires APIC to work. 6.x still has 'atpic' in > > > > GENERIC which is why it worked. There really should not be any amd64 > > > > machines w/o APIC support such as this one. Peter (cc'd) was the one who > > > > turned off 'atpic' in 7. > > > > > > Ladys and gentlemen, we have a winner! > > > > > > I added 'device atpic' to the config file and a couple attempts later > > > I had a 7.0 shell prompt. > > > > I have a question.. what sort of machine is this? I'm not aware of > > any machines that we can run on that don't have an APIC - but I know > > that many of them can have "IO APIC" disabled in the bios. > > Mainboard is Tyan Tomcat k8e 2865 > http://www.tyan.com/products/html/tomcatk8e.html > (hopefully the URL still works) > > Is the APIC part of the nforce4-ultra chipset? (nearly everything else > seems to be in there) > > If the bios disables "IO APIC", can the kernel turn it back on? > > I had tried both > > hint.apic.0.disabled="0" > and > hint.apic.0.disabled="1" > > but it didn't help. > I did some quick internet searches for 'tyan 2865 apic' and came up with a few references where people talked about changing the 'Bios IO APIC settings' between things like 'flat', 'mapped', 'full' etc. Try looking in the bios around there and see what it is set to. It should be 'full' or something like it. We should be able to boot with any of them, but 'full' is best, followed by 'flat' or 'mapped', depending on what they actually mean. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 "If Java had true garbage collection, most programs would delete themselves upon execution." -- Robert Sewell **WANTED TO BUY: Garmin Streetpilot 2650 or 2660. Not later model! ** From: Dieter To: "Peter Wemm" Cc: "John Baldwin" , bug-followup@freebsd.org, gavin@freebsd.org Subject: Re: kern/122174: [panic] 7.0 fails to allocate interrupts on amd64 Tyan 2865 Date: Wed, 02 Apr 2008 13:35:31 +0100 In message , "Peter Wemm" writes: > On Tue, Apr 1, 2008 at 7:16 AM, Dieter wrote: > > > > > 7.0 doesn't include 'device atpic' in the amd64 GENERIC meaning that > > > > > FreeBSD/amd64 7.0 basically requires APIC to work. 6.x still has 'atpic' in > > > > > GENERIC which is why it worked. There really should not be any amd64 > > > > > machines w/o APIC support such as this one. Peter (cc'd) was the one who > > > > > turned off 'atpic' in 7. > > > > > > > > Ladys and gentlemen, we have a winner! > > > > > > > > I added 'device atpic' to the config file and a couple attempts later > > > > I had a 7.0 shell prompt. > > > > > > I have a question.. what sort of machine is this? I'm not aware of > > > any machines that we can run on that don't have an APIC - but I know > > > that many of them can have "IO APIC" disabled in the bios. > > > > Mainboard is Tyan Tomcat k8e 2865 > > http://www.tyan.com/products/html/tomcatk8e.html > > (hopefully the URL still works) > > > > Is the APIC part of the nforce4-ultra chipset? (nearly everything else > > seems to be in there) > > > > If the bios disables "IO APIC", can the kernel turn it back on? > > > > I had tried both > > > > hint.apic.0.disabled="0" > > and > > hint.apic.0.disabled="1" > > > > but it didn't help. > > > > I did some quick internet searches for 'tyan 2865 apic' and came up > with a few references where people talked about changing the 'Bios IO > APIC settings' between things like 'flat', 'mapped', 'full' etc. Try > looking in the bios around there and see what it is set to. It should > be 'full' or something like it. We should be able to boot with any of > them, but 'full' is best, followed by 'flat' or 'mapped', depending on > what they actually mean. I checked my notes, and APIC was turned off for another OS. So FreeBSD can't turn APIC back on? I found a problem with atpic. I built a kernel with atausb instead of umass and the chipset-connected sata drives got assigned different numbers. (See today's (2008-04-02) posting in -drivers.) So there suddenly wasn't a ad4s2 partition to mount as root. sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A, console sio0: [FILTER] sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A sio1: [FILTER] ... acd0: DVDR at ata0-master UDMA66 ad2: 305245MB at ata1-master UDMA100 ad6: 715404MB at ata3-master SATA300 ad8: 715404MB at ata4-master SATA300 ad10: 476940MB at ata5-master SATA300 ad12: 715404MB at ata6-master SATA300 Trying to mount root from ufs:/dev/ad4s2 Manual root filesystem specification: : Mount using filesystem eg. ufs:da0s1a ? List valid disk boot devices Abort manual input mountroot> xxxxxxx~x~x~xfx~xsxsxxxxxxxxlxxxxx{xxxxjxxxtxtxx~xfx~xsxsx~x~xsxs I can't figure out where loader is getting ufs:/dev/ad4s2 ? That was the root partition before the drive number got shifted, but find . | xargs grep -i ad4s2 does not find anything under /boot The loader.conf file includes rootdev=ad6s2 RS-232 keyboard input to mountroot> prompt is getting read as garbage as if it were the wrong baud rate. Output is okay. This only happens with atpic. Without atpic it reads and echos console input ok. Not sure if this is related, but I'll throw it into the pile of data: Loader has a different problem reading input when typing to stop timer, and when reading a number to select a menu item. I have to hold the key down and let it autorepeat awhile. At this point it does read the correct keys, other than ignoring the first few dozen chars. From: John Baldwin To: freebsd@sopwith.solgatos.com Cc: "Peter Wemm" , bug-followup@freebsd.org, gavin@freebsd.org Subject: Re: kern/122174: [panic] 7.0 fails to allocate interrupts on amd64 Tyan 2865 Date: Wed, 2 Apr 2008 18:12:10 -0400 On Wednesday 02 April 2008 08:35:31 am Dieter wrote: > In message , "Peter Wemm" writes: > > On Tue, Apr 1, 2008 at 7:16 AM, Dieter wrote: > > > > > > 7.0 doesn't include 'device atpic' in the amd64 GENERIC meaning > > > > > > that > > > > > > > > > > > > FreeBSD/amd64 7.0 basically requires APIC to work. 6.x still > > > > > > has 'atpic' in GENERIC which is why it worked. There really > > > > > > should not be any amd64 machines w/o APIC support such as this > > > > > > one. Peter (cc'd) was the one who turned off 'atpic' in 7. > > > > > > > > > > Ladys and gentlemen, we have a winner! > > > > > > > > > > I added 'device atpic' to the config file and a couple attempts > > > > > later I had a 7.0 shell prompt. > > > > > > > > I have a question.. what sort of machine is this? I'm not aware of > > > > any machines that we can run on that don't have an APIC - but I know > > > > that many of them can have "IO APIC" disabled in the bios. > > > > > > Mainboard is Tyan Tomcat k8e 2865 > > > http://www.tyan.com/products/html/tomcatk8e.html > > > (hopefully the URL still works) > > > > > > Is the APIC part of the nforce4-ultra chipset? (nearly everything else > > > seems to be in there) > > > > > > If the bios disables "IO APIC", can the kernel turn it back on? > > > > > > I had tried both > > > > > > hint.apic.0.disabled="0" > > > and > > > hint.apic.0.disabled="1" > > > > > > but it didn't help. > > > > I did some quick internet searches for 'tyan 2865 apic' and came up > > with a few references where people talked about changing the 'Bios IO > > APIC settings' between things like 'flat', 'mapped', 'full' etc. Try > > looking in the bios around there and see what it is set to. It should > > be 'full' or something like it. We should be able to boot with any of > > them, but 'full' is best, followed by 'flat' or 'mapped', depending on > > what they actually mean. > > I checked my notes, and APIC was turned off for another OS. > > So FreeBSD can't turn APIC back on? Nope. We need the BIOS to tell us via ACPI or MP Table how the interrupts are physically wired up on the motherboard. W/o the BIOS providing that we don't know which pin on an APIC a given PCI device is using so we can't setup interrupt handlers. > I found a problem with atpic. I built a kernel with atausb instead > of umass and the chipset-connected sata drives got assigned different > numbers. (See today's (2008-04-02) posting in -drivers.) So there > suddenly wasn't a ad4s2 partition to mount as root. That's not an atpic problem, but sounds like the atausb vs umass. > I can't figure out where loader is getting ufs:/dev/ad4s2 ? > That was the root partition before the drive number got shifted, but > find . | xargs grep -i ad4s2 > does not find anything under /boot It reads it from /etc/fstab. > The loader.conf file includes > rootdev=ad6s2 rootdev doesn't do anything anymore AFAIK. You can override it by setting vfs.root.mountfrom yourself. > RS-232 keyboard input to mountroot> prompt is getting read as > garbage as if it were the wrong baud rate. Output is okay. > This only happens with atpic. Without atpic it reads and echos > console input ok. I've seen this break (input not work at all) with APIC, so I think it's a bug that is just getting tickled for some reason. -- John Baldwin From: Dieter To: Gavin Atkinson Cc: John Baldwin , bug-followup@FreeBSD.org Subject: Re: kern/122174: [panic] 7.0 panics on amd64 Tyan 2865 Date: Thu, 03 Apr 2008 16:38:27 +0100 > > > OK, given it boots without the de(4) driver in the kernel, my guess is > > > that those issues are related to PR kern/120915. > > > > Now, with 'device atpic', and patch #1 from PR 120915, > > kldload if_de > > works, no panic, and the interface works. > > > > Thanks for your help. > > Do you know if the second patch from that PR works for you? It's great > news that your system now works, hopefully either "device apic" will be > put back into the kernel config, or whatever bug causes the problems you > were seeing without it are resolved. Same results as Peter Much in PR 120915. Patch#1 works. Patch #2 panics when kldload-ed. Fatal trap 12: page fault while in kernel mode fault virtual address = 0x10 fault code = supervisor read data, page not present instruction pointer = 0x8:0xffffffffae79a92e stack pointer = 0x10:0xffffffffae78b2e0 frame pointer = 0x10:0xffffffffae78b510 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 63 (kldload) trap number = 12 panic: page fault Uptime: 1m30s Cannot dump. No dump device defined. From: John Baldwin To: freebsd@sopwith.solgatos.com Cc: Gavin Atkinson , bug-followup@freebsd.org Subject: Re: kern/122174: [panic] 7.0 panics on amd64 Tyan 2865 Date: Fri, 4 Apr 2008 09:11:10 -0400 On Thursday 03 April 2008 11:38:27 am Dieter wrote: > > > > OK, given it boots without the de(4) driver in the kernel, my guess > > > > is that those issues are related to PR kern/120915. > > > > > > Now, with 'device atpic', and patch #1 from PR 120915, > > > kldload if_de > > > works, no panic, and the interface works. > > > > > > Thanks for your help. > > > > Do you know if the second patch from that PR works for you? It's great > > news that your system now works, hopefully either "device apic" will be > > put back into the kernel config, or whatever bug causes the problems you > > were seeing without it are resolved. > > Same results as Peter Much in PR 120915. Patch#1 works. Patch #2 panics > when kldload-ed. > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x10 > fault code = supervisor read data, page not present > instruction pointer = 0x8:0xffffffffae79a92e > stack pointer = 0x10:0xffffffffae78b2e0 > frame pointer = 0x10:0xffffffffae78b510 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 63 (kldload) > trap number = 12 > panic: page fault > Uptime: 1m30s > Cannot dump. No dump device defined. Did you try the 3rd patch? -- John Baldwin From: Dieter To: John Baldwin Cc: Gavin Atkinson , bug-followup@freebsd.org Subject: Re: kern/122174: [panic] 7.0 panics on amd64 Tyan 2865 Date: Fri, 04 Apr 2008 13:38:39 +0100 In message <200804040911.11096.jhb@freebsd.org>, John Baldwin writes: > > Did you try the 3rd patch? Ah, a 3rd patch has appeared... Patch #3 works for me. From: John Baldwin To: freebsd@sopwith.solgatos.com Cc: Gavin Atkinson , bug-followup@freebsd.org Subject: Re: kern/122174: [panic] 7.0 panics on amd64 Tyan 2865 Date: Sat, 5 Apr 2008 13:28:35 -0400 On Friday 04 April 2008 08:38:39 am Dieter wrote: > In message <200804040911.11096.jhb@freebsd.org>, John Baldwin writes: > > > > Did you try the 3rd patch? > > Ah, a 3rd patch has appeared... > > Patch #3 works for me. So are you fine now with APIC enabled in the BIOS and the patch for de(4)? -- John Baldwin From: Dieter To: John Baldwin Cc: Gavin Atkinson , bug-followup@freebsd.org Subject: Re: kern/122174: [panic] 7.0 panics on amd64 Tyan 2865 Date: Sat, 05 Apr 2008 12:12:46 +0100 > > Patch #3 works for me. > > So are you fine now with APIC enabled in the BIOS and the patch for de(4)? de(4) is fine. Patch #1 works. Patch #3 works. I need APIC disabled in the BIOS, therefore I need "device atpic". From: John Baldwin To: freebsd@sopwith.solgatos.com Cc: Gavin Atkinson , bug-followup@freebsd.org Subject: Re: kern/122174: [panic] 7.0 panics on amd64 Tyan 2865 Date: Sat, 5 Apr 2008 15:29:09 -0400 On Saturday 05 April 2008 07:12:46 am Dieter wrote: > > > Patch #3 works for me. > > > > So are you fine now with APIC enabled in the BIOS and the patch for de(4)? > > de(4) is fine. Patch #1 works. Patch #3 works. > > I need APIC disabled in the BIOS, therefore I need "device atpic". Why do you need APIC disabled in the BIOS? -- John Baldwin From: Dieter To: John Baldwin Cc: Gavin Atkinson , bug-followup@freebsd.org Subject: Re: kern/122174: [panic] 7.0 panics on amd64 Tyan 2865 Date: Mon, 07 Apr 2008 07:48:17 +0100 > > > > Patch #3 works for me. > > > > > > So are you fine now with APIC enabled in the BIOS and the patch for de(4)? > > > > de(4) is fine. Patch #1 works. Patch #3 works. > > > > I need APIC disabled in the BIOS, therefore I need "device atpic". > > Why do you need APIC disabled in the BIOS? FreeBSD is not the only OS the box runs. State-Changed-From-To: feedback->open State-Changed-By: gavin State-Changed-When: Tue May 13 16:52:29 UTC 2008 State-Changed-Why: Feedback was received Responsible-Changed-From-To: gavin->freebsd-amd64 Responsible-Changed-By: gavin Responsible-Changed-When: Tue May 13 16:52:29 UTC 2008 Responsible-Changed-Why: Over to -amd64, for them to decide what to do with this PR. Synopsis: User needs to have APIC disabled in his BIOS because this machine dual-boots with another (unknown) OS. This used to work with FreeBSD 6.x but no longer under 7.x as "device atpic" has been removed from the amd64 kernel. I'll leave the -amd64 maintainers to decide if atpic can/should go back into the kernel. http://www.freebsd.org/cgi/query-pr.cgi?pr=122174 State-Changed-From-To: open->closed State-Changed-By: avg State-Changed-When: Sun Dec 5 10:55:02 UTC 2010 State-Changed-Why: There are no plans to include device atpic into amd64 GENERIC. http://www.freebsd.org/cgi/query-pr.cgi?pr=122174 >Unformatted: