The problem is in the acpi.ko module. Until recently - I could use an older version of the module and it worked fine. But recent changes to the kernel have rendered this oloder module unusable. During bootup - no apm module is created in /dev - so apm does not work and there is no battery monitoring or other apm features available. Disabling acpi does not work as my sound ceases to function - no mixer device is created. All in all - this bug is creating many different problems and needs a fix. The following is the output from dmesg after booting: 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-CURRENT #2: Thu Jul 3 07:37:55 PDT 2003 root@Tolkienslair.atlantis:/usr/obj/usr/src/sys/CALIGULA Preloaded elf kernel "/boot/kernel/kernel" at 0xc0771000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc07711cc. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 847398071 Hz CPU: Intel Pentium III (847.40-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x686 Stepping = 6 Features=0x383f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE> real memory = 268283904 (255 MB) avail memory = 252563456 (240 MB) Pentium Pro MTRR support enabled npx0: <math processor> on motherboard npx0: INT 16 interface acpi0: <DELL CPi R > on motherboard pcibios: BIOS version 2.10 Using $PIR table, 9 entries at 0xc00fbd80 Timecounter "ACPI-safe" frequency 3579545 Hz acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 acpi_cpu0: <CPU> port 0x530-0x537 on acpi0 acpi_tz0: <thermal zone> port 0x530-0x537 on acpi0 acpi_acad0: <AC adapter> on acpi0 acpi_cmbat0: <Control method Battery> on acpi0 acpi_cmbat1: <Control method Battery> on acpi0 acpi_lid0: <Control Method Lid Switch> on acpi0 acpi_button0: <Power Button> on acpi0 acpi_button1: <Sleep Button> on acpi0 pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0 pci0: <ACPI PCI bus> on pcib0 pcib0: slot 7 INTD is routed to irq 11 pcib0: slot 8 INTA is routed to irq 5 pcib0: slot 16 INTA is routed to irq 11 agp0: <Intel 82443BX (440 BX) host to PCI bridge> mem 0xf4000000-0xf7ffffff at device 0.0 on pci0 pcib1: <ACPI PCI-PCI bridge> at device 1.0 on pci0 pci1: <ACPI PCI bus> on pcib1 pcib1: slot 0 INTA is routed to irq 11 pci1: <display, VGA> at device 0.0 (no driver attached) cbb0: <TI1420 PCI-CardBus Bridge> at device 3.0 on pci0 cardbus0: <CardBus bus> on cbb0 pccard0: <16-bit PCCard bus> on cbb0 pcib0: slot 3 INTA is routed to irq 11 cbb1: <TI1420 PCI-CardBus Bridge> at device 3.1 on pci0 cardbus1: <CardBus bus> on cbb1 pccard1: <16-bit PCCard bus> on cbb1 pcib0: slot 3 INTA is routed to irq 11 isab0: <PCI-ISA bridge> at device 7.0 on pci0 isa0: <ISA bus> on isab0 atapci0: <Intel PIIX4 UDMA33 controller> port 0x860-0x86f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: <Intel 82371AB/EB (PIIX4) USB controller> port 0xdce0-0xdcff irq 11 at device 7.2 on pci0 usb0: <Intel 82371AB/EB (PIIX4) USB controller> on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ums0: Logitech USB Mouse, rev 1.10/6.10, addr 2, iclass 3/1 ums0: 4 buttons and Z dir. pci0: <bridge, PCI-unknown> at device 7.3 (no driver attached) pci0: <multimedia, audio> at device 8.0 (no driver attached) pci0: <simple comms> at device 16.0 (no driver attached) atkbdc0: <Keyboard controller (i8042)> port 0x64,0x60 irq 1 on acpi0 atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: <PS/2 Mouse> irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 orm0: <Option ROM> at iomem 0xc0000-0xcffff on isa0 pmtimer0 on isa0 fdc0: <Enhanced floppy controller (i82077, NE72065 or clone)> at port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: <Parallel port bus> on ppc0 plip0: <PLIP network interface> on ppbus0 lpt0: <Printer> on ppbus0 lpt0: Interrupt-driven port ppi0: <Parallel I/O> on ppbus0 sc0: <System console> at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 10.000 msec ACPI-0293: *** Warning: Buffer created with zero length in AML ACPI-0293: *** Warning: Buffer created with zero length in AML ACPI-0293: *** Warning: Buffer created with zero length in AML ACPI-0293: *** Warning: Buffer created with zero length in AML dc0: <Xircom X3201 10/100BaseTX> port 0x1000-0x107f mem 0x88002000-0x880027ff,0x88002800-0x88002fff irq 11 at device 0.0 on cardbus0 dc0: Ethernet address: 00:10:a4:c1:e8:20 miibus0: <MII bus> on dc0 tdkphy0: <TDK 78Q2120 media interface> on miibus0 tdkphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto sio4: <Xircom Cardbus modem> port 0x1080-0x1087 mem 0x88002000-0x880027ff,0x88002800-0x88002fff irq 11 at device 0.1 on cardbus0 sio4: type 16550A sio4: unable to activate interrupt in fast mode - using normal mode ACPI-0293: *** Warning: Buffer created with zero length in AML -0166: *** Error: UtAllocate: Attempt to allocate zero bytes ACPI-0293: *** Warning: Buffer created with zero length in AML -0166: *** Error: UtAllocate: Attempt to allocate zero bytes ACPI-0293: *** Warning: Buffer created with zero length in AML -0166: *** Error: UtAllocate: Attempt to allocate zero bytes ACPI-0293: *** Warning: Buffer created with zero length in AML -0166: *** Error: UtAllocate: Attempt to allocate zero bytes ata1-slave: timeout waiting for interrupt ata1-slave: ATAPI identify failed ad0: 11513MB <IBM-DARA-212000> [23392/16/63] at ata0-master UDMA33 acd0: DVD-ROM <TOSHIBA DVD-ROM SD-C2402> at ata1-master UDMA33 Mounting root from ufs:/dev/ad0s1a ACPI-0293: *** Warning: Buffer created with zero length in AML -0166: *** Error: UtAllocate: Attempt to allocate zero bytes ACPI-0293: *** Warning: Buffer created with zero length in AML -0166: *** Error: UtAllocate: Attempt to allocate zero bytes ACPI-0293: *** Warning: Buffer created with zero length in AML -0166: *** Error: UtAllocate: Attempt to allocate zero bytes ACPI-0293: *** Warning: Buffer created with zero length in AML -0166: *** Error: UtAllocate: Attempt to allocate zero bytes ltmdm0: <Lucent Winmodem> port 0xd400-0xd4ff,0xdcd8-0xdcdf mem 0xf3ffdc00-0xf3ffdcff irq 11 at device 16.0 on pci0 ltmdm0: type Virtual 16550A ACPI-0293: *** Warning: Buffer created with zero length in AML -0166: *** Error: UtAllocate: Attempt to allocate zero bytes ACPI-0293: *** Warning: Buffer created with zero length in AML -0166: *** Error: UtAllocate: Attempt to allocate zero bytes ACPI-0293: *** Warning: Buffer created with zero length in AML -0166: *** Error: UtAllocate: Attempt to allocate zero bytes ACPI-0293: *** Warning: Buffer created with zero length in AML -0166: *** Error: UtAllocate: Attempt to allocate zero bytes ACPI-0293: *** Warning: Buffer created with zero length in AML -0166: *** Error: UtAllocate: Attempt to allocate zero bytes ACPI-0293: *** Warning: Buffer created with zero length in AML -0166: *** Error: UtAllocate: Attempt to allocate zero bytes ACPI-0293: *** Warning: Buffer created with zero length in AML -0166: *** Error: UtAllocate: Attempt to allocate zero bytes ACPI-0293: *** Warning: Buffer created with zero length in AML -0166: *** Error: UtAllocate: Attempt to allocate zero bytes ACPI-0293: *** Warning: Buffer created with zero length in AML -0166: *** Error: UtAllocate: Attempt to allocate zero bytes ACPI-0293: *** Warning: Buffer created with zero length in AML -0166: *** Error: UtAllocate: Attempt to allocate zero bytes ACPI-0293: *** Warning: Buffer created with zero length in AML -0166: *** Error: UtAllocate: Attempt to allocate zero bytes ACPI-0293: *** Warning: Buffer created with zero length in AML -0166: *** Error: UtAllocate: Attempt to allocate zero bytes pcm0: <ESS Technology Maestro3> port 0xd800-0xd8ff mem 0xf3ffe000-0xf3ffffff irq 5 at device 8.0 on pci0 pcm0: <SigmaTel STAC9721/23 AC97 Codec> Fix: acpi.ko is fubar. How-To-Repeat: Occurs every bootup.
Charlie & wrote: >>Number: 54066 >>Category: advocacy >>Synopsis: ACPI repeating error messages at boot time - no apm device created. >>Confidential: no >>Severity: serious >>Priority: high >>Responsible: freebsd-advocacy >>State: open >>Quarter: >>Keywords: >>Date-Required: >>Class: sw-bug >>Submitter-Id: current-users >>Arrival-Date: Thu Jul 03 09:10:18 PDT 2003 >>Closed-Date: >>Last-Modified: >>Originator: Charlie & >>Release: FreeBSD 5.1-CURRENT i386 >>Organization: >>Environment: > > > > System: FreeBSD Tolkienslair.atlantis 5.1-CURRENT FreeBSD 5.1-CURRENT #2: Thu Jul 3 07:37:55 PDT 2003 root@Tolkienslair.atlantis:/usr/obj/usr/src/sys/CALIGULA i386 > =================== > > Dell - Inspiron 4000 laptop > > > > >>Description: > > > > The problem is in the acpi.ko module. Until recently - I could use an older > version of the module and it worked fine. But recent changes to the > kernel have rendered this oloder module unusable. > > During bootup - no apm module is created in /dev - so apm does not work > and there is no battery monitoring or other apm features available. > > Disabling acpi does not work as my sound ceases to function - no mixer > device is created. All in all - this bug is creating many different problems > and needs a fix. > [..snip dmesg..] > >>How-To-Repeat: > > > > Occurs every bootup. > > > >>Fix: > > > > acpi.ko is fubar. I am having the same problems on my Inspiron 4100 in case we need multiple testers. I am running 5.1-RELEASE. This should probably not be an "advocacy" problem however.. Eric -- ------------------------------------------------------------------ Eric Anderson Systems Administrator Centaur Technology Attitudes are contagious, is yours worth catching? ------------------------------------------------------------------
Responsible Changed From-To: freebsd-advocacy->freebsd-bugs Misfiled PR
State Changed From-To: open->feedback You state that you are using an old acpi.ko module. This isn't supported - it is expected that changes to the kernel over time will render old modules unusable. Can you please retry with an up-to-date acpi.ko built from the same sources as your kernel?
On Sat, Jul 12, 2003 at 10:55:47PM -0700, Michael Dill wrote: > Kris: > > My apology for being unclear in my bug report. I 'was' using an older > acpi.ko until it ceased to work. The dmesg text that I included in my > report is from a recent kernel and acpi.ko module. The problem is - all > the current ones since the initial release of 5.0_CURRENT have given > this error on my Dell Inspiron 4000. > > My perusal of other bug reports and usenet msg's show that many others > with Dells are having the same or similar problems. > > Hope this clears things up a bit. Anything else you would have me do, > just let me know. I would love to see this bug fixed. Thanks, OK. It's possible it's an ACPI bug. I'm currently trying to determine where ACPI PRs should be assigned so the relevant developers are aware of them. Kris
Responsible Changed From-To: freebsd-bugs->acpi-jp@jp.freebsd.org Assign to ACPI maintainers
Please cvsup to 5.1-CURRENT and test the new version of ACPICA. It has a fix for the zero-length alloc problem. -Nate
I've also been experiencing this problem on my Inspiron 3700 (APM had been working fine until I cvsup'd and built a new kernel on July 10). I've upgraded to 5.1-CURRENT of july 24 (kernel and world); I still see the UtAllocate errors, and apm(8) still thinks I have no batteries inserted.
I am looking into the 0 length errors you're getting. Can you please run: acpidump -o myname.dsdt > myname.asl and send me a URL to these two files? Thanks, Nate
On Aug 08, Nate Lawson wrote: > I am looking into the 0 length errors you're getting. Can you please run: > acpidump -o myname.dsdt > myname.asl > and send me a URL to these two files? Nate, Thanks for the followup. Let me know if there's any other way I can help. http://kstar.dyndns.org:8080/acpi/ - Kurt
I have received both of your DSDTs and am looking into this. I'm pretty busy so it may take me a little while to get anywhere. -Nate
---------- Forwarded message ---------- Date: Tue, 12 Aug 2003 20:00:42 +0200 From: Christoph P. Kukulies <kuku@physik.rwth-aachen.de> On Tue, Aug 12, 2003 at 09:59:44AM -0700, Nate Lawson wrote: > There is supposed to be a workaround for this in the current acpi version > but apparently it's not catching all the calls to UtAllocate(). I am > tracking down this problem. You can do: > acpidump -o christoph.dsdt > christoph.asl > and then send me a URL to those two files. Also, see PR bin/54066 > I will be working on this there. http://kukulies.org/christoph.dsdt http://kukulies.org/christoph.asl
Responsible Changed From-To: acpi-jp@jp.freebsd.org->njl I'll handle acpi problems.
State Changed From-To: feedback->closed I am pretty certain this is fixed. Let me know if it recurs.