From owner-freebsd-current@FreeBSD.ORG Thu Feb 5 10:08:24 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D7E8116A4CE; Thu, 5 Feb 2004 10:08:23 -0800 (PST) Received: from mr4.zonelabs.com (mr4.zonelabs.com [208.185.174.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id BDE8443D5A; Thu, 5 Feb 2004 10:08:17 -0800 (PST) (envelope-from jklein@zonelabs.com) Received: from exgate1.zonelabs.com ([172.16.211.232])i15I8E71026070; Thu, 5 Feb 2004 10:08:16 -0800 (PST) Received: from exmb2.zonelabs.com ([172.16.211.235]) by exgate1.zonelabs.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, 5 Feb 2004 10:08:15 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Thu, 5 Feb 2004 10:08:14 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: AE_AML_INVALID_RESOURCE_TYPE error in 5.2-CURRENT Thread-Index: AcPrYqL9wm5WvrHCR42zE5Jetcn/sgArMfIg From: "Jeff Klein" To: "John Baldwin" , X-OriginalArrivalTime: 05 Feb 2004 18:08:15.0776 (UTC) FILETIME=[06B7FA00:01C3EC13] X-Scanned-By: MIMEDefang 2.39 Subject: RE: AE_AML_INVALID_RESOURCE_TYPE error in 5.2-CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Feb 2004 18:08:24 -0000 Thanks for the reply, John. I didn't find an option in the BIOS to allocate an IRQ for VGA. However, when I rebooted, I noticed that I am now getting an additional ACPI error in dmesg (see below). I rebooted again, just to see if it was reproducible and it is. Might this be related to the original error (which occurs earlier in the boot)? Thanks, Jeff PS I have not tried printf's yet. Could you give me an idea of which src files to look at?=20 ----------- ACPI error from dmesg ---------------- acpi_ec0: port 0xca7,0xca6 on acpi0 ACPI-0440: *** Error: Handler for [EmbeddedControl] returned AE_NO_HARDWARE_RESPONSE ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.ISA0.EC0_.ECCW] (Node 0xc615f880), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.ISA0.EC0_.SREC] (Node 0xc615f980), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.ISA0.EC0_.SSLP] (Node 0xc615f7a0), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.ISA0.EC0_._REG] (Node 0xc615fc00), AE_AML_NO_RETURN_VALUE acpi_ec0: can't install address space handler for \\_SB_.PCI0.ISA0.EC0_ - AE_AML_NO_RETURN_VALUE device_probe_and_attach: acpi_ec0 attach returned 6 acpi_ec0: port 0xca7,0xca6 on acpi0 acpi_ec0: can't install address space handler for \\_SB_.PCI0.ISA0.EC0_ - AE_SAME_HANDLER device_probe_and_attach: acpi_ec0 attach returned 6 ------------------ end ACPI error from dmesg ------------------------- -----Original Message----- From: John Baldwin [mailto:jhb@FreeBSD.org]=20 Sent: Wednesday, February 04, 2004 12:57 PM To: Jeff Klein; FreeBSD-current@FreeBSD.org Subject: Re: AE_AML_INVALID_RESOURCE_TYPE error in 5.2-CURRENT On Wednesday 04 February 2004 03:35 pm, Jeff Klein wrote: > Hi All, > > I cvsup'ed to the latest and ran "make buildworld" last night (about 7pm > PST). I was previously running 5.1-RELEASE, but was having problems > with SMP support. The good news is that the SMP support (w/ device > apic) seems to be working well now, but the bad news is that I am > getting a new error in the kernel at boot time: > > can't fetch resources for \\_SB_.LN1_ - AE_AML_INVALID_RESOURCE_TYPE > > -and- > > pcib0: couldn't get PCI interrupt link device _CRS data - > AE_AML_INVALID_RESOURCE_TYPE > > This doesn't seem to be causing any serious problems so far, but I have > only been running on it for less than 24 hours, so it is too early to > tell. Does anyone know if this is serious? (and if there is a > fix/workaround?). Output from dmesg is below. >From your dmesg it doesn't appear serious. Does it go away if you tell your=20 BIOS to allocate an IRQ for the VGA device? Also, can you add a printf to=20 make it print out what the resource type is when it prints that error message=20 perhaps? > Thanks and regards, > Jeff Klein > > ------------------------- dmesg output ----------------------------- > > Copyright (c) 1992-2004 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-CURRENT #1: Tue Feb 3 23:43:49 PST 2004 > root@weckl:/usr/obj/usr/src/sys/WECKL > Preloaded elf kernel "/boot/kernel/kernel" at 0xc07ff000. Preloaded elf > module "/boot/kernel/acpi.ko" at 0xc07ff26c. > ACPI APIC Table: > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Xeon(TM) CPU 2.40GHz (2399.67-MHz 686-class CPU) > Origin =3D "GenuineIntel" Id =3D 0xf27 Stepping =3D 7 > > Features=3D0xbfebfbff ,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > Hyperthreading: 2 logical CPUs > real memory =3D 1073741824 (1024 MB) > avail memory =3D 1045336064 (996 MB) > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > cpu2 (AP): APIC ID: 6 > cpu3 (AP): APIC ID: 7 > ioapic0 irqs 0-15 on motherboard > ioapic1 irqs 16-31 on motherboard > Pentium Pro MTRR support enabled > npx0: [FAST] > npx0: on motherboard > npx0: INT 16 interface > acpi0: on motherboard > pcibios: BIOS version 2.10 > Using $PIR table, 16 entries at 0xc00fdec0 > acpi0: Power Button (fixed) > Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 > can't fetch resources for \\_SB_.LN1_ - AE_AML_INVALID_RESOURCE_TYPE > acpi_timer0: <32-bit timer at 3.579545MHz> port 0x508-0x50b on acpi0 > acpi_cpu0: on acpi0 > acpi_cpu1: on acpi0 > acpi_cpu2: on acpi0 > acpi_cpu3: on acpi0 > acpi_button0: on acpi0 > acpi_button1: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pcib0: couldn't get PCI interrupt link device _CRS data - > AE_AML_INVALID_RESOURCE_TYPE > pci0: at device 2.0 (no driver attached) > fxp0: port 0x2400-0x243f mem > 0xfc000000-0xfc01ffff,0xfc021000-0xfc021fff irq 18 at device 3.0 on pci0 > fxp0: Ethernet address 00:02:b3:52:36:7b > miibus0: on fxp0 > inphy0: on miibus0 > inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > isab0: at device 15.0 on pci0 > isa0: on isab0 > atapci0: port > 0x2440-0x244f,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 at device > 15.1 on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata0: [MPSAFE] > ata1: at 0x170 irq 15 on atapci0 > ata1: [MPSAFE] > ohci0: mem 0xfc022000-0xfc022fff irq 10 > at device 15.2 on pci0 > usb0: OHCI version 1.0, legacy support > usb0: on ohci0 > usb0: USB revision 1.0 > uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 4 ports with 4 removable, self powered > pcib1: on acpi0 > pci1: on pcib1 > em0: port > 0x2460-0x247f mem 0xfc300000-0xfc31ffff,0xfc320000-0xfc33ffff irq 19 at > device 4.0 on pci1 > em0: Speed:N/A Duplex:N/A > pcib2: on acpi0 > pci2: on pcib2 > ahc0: port 0x2800-0x28ff mem > 0xfc700000-0xfc700fff irq 16 at device 9.0 on pci2 > aic7899: Ultra160 Wide Channel A, SCSI Id=3D7, 32/253 SCBs > ahc1: port 0x3000-0x30ff mem > 0xfc701000-0xfc701fff irq 17 at device 9.1 on pci2 > aic7899: Ultra160 Wide Channel B, SCSI Id=3D7, 32/253 SCBs > atkbdc0: port 0x64,0x60 irq 1 on acpi0 > atkbd0: flags 0x1 irq 1 on atkbdc0 > kbd0 at atkbd0 > psm0: irq 12 on atkbdc0 > psm0: model IntelliMouse Explorer, device ID 4 > sio0 port 0x3f8-0x3ff irq 4 on acpi0 > sio0: type 16550A > sio1 port 0x2f8-0x2ff irq 3 on acpi0 > sio1: type 16550A > ppc0 port 0x778-0x77f,0x378-0x37f irq 7 drq 1 on acpi0 > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > ppc0: FIFO with 16/16/8 bytes threshold > ppbus0: on ppc0 > plip0: on ppbus0 > lpt0: on ppbus0 > lpt0: Interrupt-driven port > ppi0: on ppbus0 > fdc0: port > 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > acpi_ec0: port 0xca7,0xca6 on acpi0 > pmtimer0 on isa0 > orm0: