Re: ACPI problems with this morning's -CURRENT
(To recap: I'm having ACPI problems on a DFI CD70-SC, with both 5.1-R and 5-CURRENT. Booting GENERIC doesn't show any problems, however, so there's a good chance it's a misconfiguration issue.) Thus spake Damian Gerow ([EMAIL PROTECTED]) [15/09/03 17:34]: It's attached. There's no APM in there. I did some more testing -- GENERIC works for the -CURRENT date I stated before, and 5.1-R. As soon as I compile my own kernel, it breaks. Okay, here's a backtrace with debugging. Unfortunately, when dropped to the debugging prompt, I don't know what to do. Attached is the kernel config I used to generate this on 5.1-R, I can re-do this on -CURRENT if need be. Here's a snippet of boot, and the stack backtrace: ... Preloaded elf kernel /boot/kernel/kernel at 0xc04b8000 Preloaded elf module /boot/kernel/acpi.ko at 0xc04b81f4 ... real memory = 536870912 (512 MB) avail memory = 516313088 (492 MB) panic: pmap_mapdev: Couldn't allocate kernel virtual memory Stack backtrace: backtrace(c035b0cc,c03baea0,c0372994,c04dabbc,100) at backtrace+0x17 panic(c0372994,c036f000,0,0,0) at panic+0x93 pmap_mapdev(1fff3000,c036ec14,c04dac48,c04dabcc,c048e880) at pmap_mapdev+0x4b AcpiOsMapMemory(1fff3000,0,c036ec14,c04dabbc,c04dabc4) atAcpiOsMapMemory+0x1e I'm almost certain your problem is defining MAXMEM to 512 MB. Remove that from your kernel config and try again. MAXMEM causes all kinds of problems. If this doesn't solve it, start with the stock GENERIC and add back in your custom kernel options until it fails. The last option you add is the faulty one. -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACPI problems with this morning's -CURRENT
Thus spake Nate Lawson ([EMAIL PROTECTED]) [16/09/03 15:00]: I'm almost certain your problem is defining MAXMEM to 512 MB. Remove that from your kernel config and try again. MAXMEM causes all kinds of problems. If this doesn't solve it, start with the stock GENERIC and add back in your custom kernel options until it fails. The last option you add is the faulty one. I was wondering the same thing myself last night actually... I just pulled that line, and it now works. Which is weird -- I have two other 5.1 machines that I have specified MAXMEM in, without any troubles. It's also strange that this would only be brought out with ACPI...? Anyhow, it's working for me now. If anyone feels like further debugging, I'm all game. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACPI problems with this morning's -CURRENT [SOLVED]
On Tue, 16 Sep 2003, Damian Gerow wrote: Thus spake Nate Lawson ([EMAIL PROTECTED]) [16/09/03 15:00]: I'm almost certain your problem is defining MAXMEM to 512 MB. Remove that from your kernel config and try again. MAXMEM causes all kinds of problems. If this doesn't solve it, start with the stock GENERIC and add back in your custom kernel options until it fails. The last option you add is the faulty one. I was wondering the same thing myself last night actually... I just pulled that line, and it now works. Which is weird -- I have two other 5.1 machines that I have specified MAXMEM in, without any troubles. It's also strange that this would only be brought out with ACPI...? Anyhow, it's working for me now. If anyone feels like further debugging, I'm all game. It probably has something to do with the virtual/physical gymnastics ACPI has to do to map its tables into memory. I have no time to track this down but the output of acpidump -t may help someone else who might be interested. You're looking for the pointers that are stored in RSD PTR. -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACPI problems with this morning's -CURRENT [SOLVED]
Thus spake Nate Lawson ([EMAIL PROTECTED]) [16/09/03 16:24]: I have no time to track this down but the output of acpidump -t may help someone else who might be interested. You're looking for the pointers that are stored in RSD PTR. I'm still on 5.1-R, and there's no '-t' flag to acpidump. However, I've posted the dump on the web: http://www.sentex.net/~damian/acpidump so people can browse as they wish. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACPI problems with this morning's -CURRENT [SOLVED]
On Tue, 16 Sep 2003, Damian Gerow wrote: Thus spake Nate Lawson ([EMAIL PROTECTED]) [16/09/03 16:24]: I have no time to track this down but the output of acpidump -t may help someone else who might be interested. You're looking for the pointers that are stored in RSD PTR. I'm still on 5.1-R, and there's no '-t' flag to acpidump. However, I've posted the dump on the web: http://www.sentex.net/~damian/acpidump so people can browse as they wish. As expected, your ACPI tables are at the top of physmem: RSDT=0x1fff3000. This is only 52k from 512MB. Something in how MAXMEM affects setup of physical memory is truncating physmem by at least 64k. In short, Don't Do That. -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACPI problems with this morning's -CURRENT
Thus spake Nate Lawson ([EMAIL PROTECTED]) [13/09/03 14:42]: The post you reference shows the user with a kernel that has both APM and ACPI installed, apparently. This is not valid. Please report your kernel config. If GENERIC in 2003/9/6 booted fine with ACPI and then your rebuilt kernel from 2003/9/7 fails, it is almost certainly the devices you included. There were no ACPI-related commits in that timeframe. It's attached. There's no APM in there. I did some more testing -- GENERIC works for the -CURRENT date I stated before, and 5.1-R. As soon as I compile my own kernel, it breaks. I'm working on compiling this with debugging, so I can take a closer look at what's going on. ident pandora machine i386 cpu I686_CPU maxusers0 options INCLUDE_CONFIG_FILE #optionsCPU_WT_ALLOC options MAXMEM=(512*1024) options DEVICE_POLLING options HZ=1000 device isa device pci device agp device speaker device random device pty device md device npx device sio options CONSPEED=115200 options GEOM_BDE options GEOM_BSD options GEOM_VOL options SCHED_4BSD options COMPAT_43 options COMPAT_FREEBSD4 options SYSVSHM options SYSVSEM options SYSVMSG options INET options INET6 options IPSEC options IPSEC_ESP device ether device loop device bpf device disc device gif device faith device stf options IPFILTER options IPFILTER_LOG options IPFILTER_DEFAULT_BLOCK options PFIL_HOOKS options RANDOM_IP_ID options ACCEPT_FILTER_DATA options ACCEPT_FILTER_HTTP options TCP_DROP_SYNFIN options FFS options NFSCLIENT options NFSSERVER options PROCFS options PSEUDOFS options SOFTUPDATES options UFS_DIRHASH options UFS_EXTATTR options UFS_EXTATTR_AUTOSTART options UFS_ACL options _KPOSIX_PRIORITY_SCHEDULING options P1003_1B_SEMAPHORES #optionsMAC #optionsMAC_BSDEXTENDED #optionsMAC_SEEOTHERUIDS # These are worth looking into, but require configuration #optionsMAC_BIBA #optionsMAC_LOMAC #optionsMAC_MLS # These two are also worth looking at, and take less configuration #optionsMAC_PARTITION #optionsMAC_PORTACL device atkbdc device atkbd options KBD_INSTALL_CDEV device vga options VGA_ALT_SEQACCESS device splash device sc #device daemon_saver #device fade_saver device fire_saver #device green_saver #device logo_saver #device rain_saver #device star_saver #device warp_saver device ata device atadisk device miibus device fxp device smbus device ichsmb device smb device iicbus device iicbb device iicsmb #device crypto # core crypto support #device cryptodev # /dev/crypto for access to h/w # #device rndtest # FIPS 140-2 entropy tester # #device hifn# Hifn 7951, 7781, etc. #optionsHIFN_DEBUG # enable debugging support: hw.hifn.debug #optionsHIFN_RNDTEST# enable rndtest support # #device ubsec # Broadcom 5501, 5601, 58xx #optionsUBSEC_DEBUG # enable debugging support: hw.ubsec.debug #optionsUBSEC_RNDTEST # enable rndtest support ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACPI problems with this morning's -CURRENT
(To recap: I'm having ACPI problems on a DFI CD70-SC, with both 5.1-R and 5-CURRENT. Booting GENERIC doesn't show any problems, however, so there's a good chance it's a misconfiguration issue.) Thus spake Damian Gerow ([EMAIL PROTECTED]) [15/09/03 17:34]: It's attached. There's no APM in there. I did some more testing -- GENERIC works for the -CURRENT date I stated before, and 5.1-R. As soon as I compile my own kernel, it breaks. I'm working on compiling this with debugging, so I can take a closer look at what's going on. Okay, here's a backtrace with debugging. Unfortunately, when dropped to the debugging prompt, I don't know what to do. Attached is the kernel config I used to generate this on 5.1-R, I can re-do this on -CURRENT if need be. Here's a snippet of boot, and the stack backtrace: ... Preloaded elf kernel /boot/kernel/kernel at 0xc04b8000 Preloaded elf module /boot/kernel/acpi.ko at 0xc04b81f4 ... real memory = 536870912 (512 MB) avail memory = 516313088 (492 MB) panic: pmap_mapdev: Couldn't allocate kernel virtual memory Stack backtrace: backtrace(c035b0cc,c03baea0,c0372994,c04dabbc,100) at backtrace+0x17 panic(c0372994,c036f000,0,0,0) at panic+0x93 pmap_mapdev(1fff3000,c036ec14,c04dac48,c04dabcc,c048e880) at pmap_mapdev+0x4b AcpiOsMapMemory(1fff3000,0,c036ec14,c04dabbc,c04dabc4) at AcpiOsMapMemory+0x1e AcpiTbGetThisTable(c04dac48,c04dac00,c04dac58,c04dac48,c04dac48) at AcpiTbGetThisTable+0xf0 AcpiTbGetTableBody(c04dac48,c04dac00,c04dac58,c0387ebc,c036ec14) at AcpiTbGetTableBody+0x4c AcpiTbGetTable(c04dac48,c04dac58,9,1fff3000,0) at AcpiTbGetTable+0x38 AcpiTbGetTableRsdt(c04daca0,c04daca0,c04dacb4,1,f6010) at AcpiTbGetTableRsdt+0x23 AcpiLoadTables(c04a8bc0,c04a49ac,0,0,0) at AcpiLoadTables+0xa6 acpi_identify(c04a7528,c151cb00,c0379a14,c1506190,c151cb00) at acpi_identify+0xb4 DEVICE_IDENTIFY(c04a7528,c151cb00,c151cb00,c151cb00,c04dad18) at DEVICE_IDENTIFY+0x50 bus_generic_probe(c151cb00,c3fcc098,c04dad34,c01da1b8,c151cb00) at bus_generic_probe+0x2e nexus_attach(c151cb00,c3fcc098,c0379a1c,c151cb00,c151d000) at nexus_attach+0x14 DEVICE_ATTACH(c151cb00,c151cb00,0,c14ea5d8,1) at DEVICE_ATTACH+0x48 device_probe_and_attach(c151cb00,c14ea5d8,c04dad80,c0321635,c151d000) at device_probe_and_attach+0x7d root_bus_configure(c151d000,c0371fdc,0,c04dad98,c01960a5) at root_bus_configure+0x28 configure(0,4d7000,4d7c00,4d7000,0) at configure+0x35 mi_startup() at mi_startup+0xb5 being() at begin+0x2c Debugger(panic) Stopped atDebugger+0x54:xchgl %ebx,in_Debugger.0 db print c01c08b0 db show pcpu cpuid = 0 curthread = 0xc03b4640: pid 0 swapper curpcb = 0 fpcurthread = none idlethread = 0xc151f850: pid 11 idle currentldt = 0x28 db show map Task map 0xc01c08b0: pmap=0x4de80574, nentries=604293056, version=742228750 Fatal trap 12: page fault while in kernel mode fault virtual address = 0x4c70500 fault code = supervisor read, page not present instruction pointer = 0x8:0xc02f3a40 stack pointer = 0x10: 0xc04da940 frame pointer = 0x10: 0xc04da960 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= resume, IOPL = 0 current process = 0 (swapper) kernel: type 12 trap, code=0 Stopped at Debugger+0x54: xchgl %ebx,in_Debugger.0 db Given that I caused a panic while in the debugger, and that I don't know what I'm looking for, I stopped here. (Further 'show map's didn't result in a panic, however.) Note that if I /don't/ boot with ACPI, I can boot just fine, with no power management. ident pandora machine i386 cpu I686_CPU maxusers0 makeoptions DEBUG=-g options DDB options DDB_TRACE options KTRACE options DIAGNOSTIC options INCLUDE_CONFIG_FILE options CPU_FASTER_5X86_FPU options CPU_UPGRADE_HW_CACHE #optionsCPU_WT_ALLOC options MAXMEM=(512*1024) options DEVICE_POLLING options HZ=1000 device isa device pci device agp device speaker device random device pty device md device npx device sio options CONSPEED=115200 options GEOM_BDE options GEOM_BSD options GEOM_VOL options SCHED_4BSD options COMPAT_43 options COMPAT_FREEBSD4 options SYSVSHM options SYSVSEM options SYSVMSG options INET options INET6 options IPSEC options IPSEC_ESP device ether device loop device bpf device disc device gif device faith device stf options IPFILTER options
Re: ACPI problems with this morning's -CURRENT
The post you reference shows the user with a kernel that has both APM and ACPI installed, apparently. This is not valid. Please report your kernel config. If GENERIC in 2003/9/6 booted fine with ACPI and then your rebuilt kernel from 2003/9/7 fails, it is almost certainly the devices you included. There were no ACPI-related commits in that timeframe. -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACPI problems on MSI K7D
Nate Lawson [EMAIL PROTECTED] writes: Please report the dmesg from boot -v as that should help figure out why pci_cfgregopen() fails. Full log attached, both with and without ACPI. Also, I think the following should be \_S3: Name (\SS3, Package (0x04) That shouldn't have any impact on my problem though, should it? DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] Console: serial port BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS 640kB/523200kB available memory FreeBSD/i386 bootstrap loader, Revision 1.1 ([EMAIL PROTECTED], Mon Sep 1 18:48:59 CEST 2003) Loading /boot/defaults/loader.conf /boot/kernel/kernel text=0x1eaadc data=0x22608+0x44e34 syms=[0x4+0x2cfa0+0x4+0x372f6] /boot/kernel/snd_ich.ko text=0x31e4 data=0x284 syms=[0x4+0x960+0x4+0x964] loading required module 'snd_pcm' /boot/kernel/snd_pcm.ko text=0x1412c data=0x24d8+0x1124 syms=[0x4+0x2a20+0x4+0x2e0d] /boot/kernel/usb.ko text=0x1fad0 data=0xc4c+0x168 syms=[0x4+0x2c70+0x4+0x33ce] /boot/kernel/ums.ko text=0x22e0 data=0x168+0x4 syms=[0x4+0x5f0+0x4+0x52f] Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel] in 3 seconds... Type '?' for a list of commands, 'help' for more detailed help. OK boot -v /boot/kernel/acpi.ko text=0x3aa2c data=0x170c+0xec0 syms=[0x4+0x5bf0+0x4+0x7a42] SMAP type=01 base= len=000a SMAP type=02 base=000f len=0001 SMAP type=02 base=fec0 len=0140 SMAP type=01 base=0010 len=1fef SMAP type=03 base=1fff3000 len=d000 SMAP type=04 base=1fff len=3000 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 #9: Mon Sep 1 19:06:40 CEST 2003 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/meali Preloaded elf kernel /boot/kernel/kernel at 0xc0453000. Preloaded elf module /boot/kernel/snd_ich.ko at 0xc04531d8. Preloaded elf module /boot/kernel/snd_pcm.ko at 0xc0453284. Preloaded elf module /boot/kernel/usb.ko at 0xc0453330. Preloaded elf module /boot/kernel/ums.ko at 0xc04533d8. Preloaded elf module /boot/kernel/acpi.ko at 0xc0453480. Calibrating clock(s) ... i8254 clock: 1193232 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter i8254 frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 1363433775 Hz CPU: AMD Athlon(tm) MP 1500+ (1363.43-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x681 Stepping = 1 Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE AMD Features=0xc048MP,AMIE,DSP,3DNow! Data TLB: 32 entries, fully associative Instruction TLB: 16 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 internal cache: 256 kbytes, 64 bytes/line, 1 lines/tag, 8-way associative real memory = 536805376 (511 MB) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x0047d000 - 0x1f6c9fff, 522506240 bytes (127565 pages) avail memory = 516714496 (492 MB) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 - irq 0 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): apic id: 0, version: 0x00040010, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00040010, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 bios32: Found BIOS32 Service Directory header at 0xc00fac90 bios32: Entry = 0xfb100 (c00fb100) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf+0xb130 pnpbios: Found PnP BIOS data at 0xc00fbb30 pnpbios: Entry = f:bb60 Rev = 1.0 Other BIOS signatures found: null: null device, zero device mem: memory I/O Pentium Pro MTRR support enabled random: entropy source SMP: CPU0 bsp_apic_configure(): lint0: 0x00010700 lint1: 0x0400 TPR: 0x SVR: 0x01ff npx0: math processor on motherboard npx0: INT 16 interface acpi0: AMD2P AWRDACPI on motherboard pci_open(1):mode 1 addr port (0x0cf8) is 0x80ff003c pci_open(2):mode 2 enable port (0x0cf8) is 0xff panic: AcpiOsDerivePciId unable to initialize pci bus cpuid = 0; lapic.id = Debugger(panic) Stopped at Debugger+0x4e: xchgl %ebx,in_Debugger.0 db where Debugger(c02d384b,0,c0441336,c04757c4,100) at Debugger+0x4e panic(c0441336,c042c47c,c400e940,c043db4a,1) at panic+0x151 AcpiOsDerivePciId(c3f60b40,c3f60940,c0475804,168,0) at AcpiOsDerivePciId+0x2d AcpiEvPciConfigRegionSetup(c3fa6280,0,0,c047585c,c4004680) at AcpiEvPciConfigRegionSetup+0x224 AcpiEvAddressSpaceDispatch(c3fa6280,0,56,0,8) at AcpiEvAddressSpaceDispatch+0x86 AcpiExAccessRegion(c400e780,0,c047590c,0,c401ae00) at AcpiExAccessRegion+0x70 AcpiExFieldDatumIo(c400e780,0,c047590c,0,14f) at AcpiExFieldDatumIo+0x157
Re: ACPI problems on MSI K7D
On Tue, 9 Sep 2003, Dag-Erling [iso-8859-1] Smørgrav wrote: Nate Lawson [EMAIL PROTECTED] writes: Please report the dmesg from boot -v as that should help figure out why pci_cfgregopen() fails. Full log attached, both with and without ACPI. Perhaps someone who knows our PCI code better could address this? Here is the valid case (without ACPI): pci_open(1):mode 1 addr port (0x0cf8) is 0x80003840 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=700c1022) Here is the invalid case (with ACPI): acpi0: AMD2P AWRDACPI on motherboard pci_open(1):mode 1 addr port (0x0cf8) is 0x80ff003c pci_open(2):mode 2 enable port (0x0cf8) is 0xff panic: AcpiOsDerivePciId unable to initialize pci bus Obviously, the pci_open(2) is bogus. If no one else addresses this, I will try to get to it soon. For now, try changing the panic to a return 0 and see how it affects system operation. Also, I think the following should be \_S3: Name (\SS3, Package (0x04) That shouldn't have any impact on my problem though, should it? Nope, just something I noticed. -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACPI problems with Compaq Evo N610c
On Wed, 30 Jul 2003, Cagle, John (ISS-Houston) wrote: I have a feeling that my acpi table didn't actually get overridden though, due to the following from dmesg: ACPI: DSDT was overridden. -0424: *** Error: UtAllocate: Could not allocate size 6e49202a ACPI-0428: *** Error: Could not allocate table memory for [/* ] length 6e49202a ACPI-0368: *** Error: Could not copy override ACPI table, AE_NO_MEMORY This looks like an unterminated comment character (/*). I see another person's ASL fixed this for you though. -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
ACPI problems with this morning's -CURRENT
I set up a box yesterday to play with -CURRENT on. I used the 2003-09-06 snapshot code from ftp://current.freebsd.org/. Initial setup and boot worked just fine, but when I did a rebuild/reboot last night, this is what I saw: pmap_mapdev: Couldn't alloc kernel virtual memory So thinking I missed some kernel options, I pulled a couple of things, did another cvsup/rebuild/reboot this morning, and got the same thing. I know that various people have been having ongoing issues with ACPI, but this is the first problem I've had with it (I have a couple of other boxen running 5.1-RELEASE and 5-CURRENT). I was able to fix it (and discover that it was ACPI related) by finding this post (even though it's two years old): http://www.geocrawler.com/archives/3/147/2001/8/0/6526228/ The difference is that I'm seeing the pmap_mapdev error immediately after it spits out the 'real memory' and 'avail memory' lines. This is being run on a DFI CD70-SC, 512MB DDR SDRAM, with a Via C3 Nehemiah. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACPI problems on MSI K7D
This is the line that triggers that panic, from /sys/dev/acpica/Osd/OsdHardware.c: if (pci_cfgregopen() == 0) panic(AcpiOsDerivePciId unable to initialize pci bus); Please report the dmesg from boot -v as that should help figure out why pci_cfgregopen() fails. Also, I think the following should be \_S3: Name (\SS3, Package (0x04) -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: ACPI problems with Compaq Evo N610c (fwd)
Hello Doug, From [EMAIL PROTECTED] Fri Sep 5 05:49:49 2003 Not sure if you got a copy of this first time or not... Sorry, no I did not. My mail pickup system got screwed several times lately. -- Forwarded message -- From: Doug Barton [EMAIL PROTECTED] To: Cagle, John (ISS-Houston) [EMAIL PROTECTED] Cc: Tony Maher [EMAIL PROTECTED], Robert Blacquière [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Date: Sun, 31 Aug 2003 19:50:03 -0700 (PDT) Organization: http://www.FreeBSD.org/ Subject: RE: ACPI problems with Compaq Evo N610c I got interested in this recently because I inherited one of these laptops from work. On Wed, 30 Jul 2003, Cagle, John (ISS-Houston) wrote: Which version of the N610C BIOS are you using? (F.14 is the latest on the hp.com website.) I know that the _OSI(Windows 2001) bug will be fixed in the F.15 release, but I don't think the _GL_ portion of your patch will be included. Did you have to remove the Acquire Release of _GL_ in order to get xbat to work? (This is not a problem we see with Linux ACPI in 2.4.21, so I think that FreeBSD's ACPI stack needs updating.) I just updated to F.15, and it does indeed fix the windows bit in the output of 'acpidump -d'. However, even with Tony's recommendation of removing the acquire/release of _GL in methods C12C and C12D, I still can't get xbatt or wmbattery to run, even with the very latest -current (which has had at least one acpi stack upgrade since 7/30). When I run either command, it locks the box tight. If I ever get a cursor back, I have to Ctrl-Alt-Backspace to get out of X, since I can't actually type anything. I have a feeling that my acpi table didn't actually get overridden though, due to the following from dmesg: ACPI: DSDT was overridden. -0424: *** Error: UtAllocate: Could not allocate size 6e49202a ACPI-0428: *** Error: Could not allocate table memory for [/* ] length 6e49202a ACPI-0368: *** Error: Could not copy override ACPI table, AE_NO_MEMORY This certainly seems to be the case. I see ACPI: DSDT was overridden. ACPI-0375: *** Info: Table [DSDT] replaced by host OS Also, the before and after acpidump's don't show anything different. So, I'm curious if wmbatt is still working for Tony and Robert or not with the latest -current. I am currently running FreeBSD k9.home 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Sat Aug 30 11:48:23 EST 2003 [EMAIL PROTECTED]:/var/obj/space/usr/src/sys/K9 i386 and xbatt works (to certain extent - it show s being power cable in and out and shos charging state when first booted up but after insertion/removal of power cord it no longer shows charging stae or time left in battery) If I get a cahnce on weekend I'll update to latest and let you know. The other problem I'm having is that doing 'sysctl -a', or just 'sysctl hw.acpi' locks the system tight for a couple minutes, and never completes. The last line that's printed to the screen is: hw.acpi.thermal.tz1._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 Any ideas on that one? This is becase the DSDT was not overridden. I used to see this as well. -- tonym ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: ACPI problems with Compaq Evo N610c
I got interested in this recently because I inherited one of these laptops from work. On Wed, 30 Jul 2003, Cagle, John (ISS-Houston) wrote: Which version of the N610C BIOS are you using? (F.14 is the latest on the hp.com website.) I know that the _OSI(Windows 2001) bug will be fixed in the F.15 release, but I don't think the _GL_ portion of your patch will be included. Did you have to remove the Acquire Release of _GL_ in order to get xbat to work? (This is not a problem we see with Linux ACPI in 2.4.21, so I think that FreeBSD's ACPI stack needs updating.) I just updated to F.15, and it does indeed fix the windows bit in the output of 'acpidump -d'. However, even with Tony's recommendation of removing the acquire/release of _GL in methods C12C and C12D, I still can't get xbatt or wmbattery to run, even with the very latest -current (which has had at least one acpi stack upgrade since 7/30). When I run either command, it locks the box tight. If I ever get a cursor back, I have to Ctrl-Alt-Backspace to get out of X, since I can't actually type anything. I have a feeling that my acpi table didn't actually get overridden though, due to the following from dmesg: ACPI: DSDT was overridden. -0424: *** Error: UtAllocate: Could not allocate size 6e49202a ACPI-0428: *** Error: Could not allocate table memory for [/* ] length 6e49202a ACPI-0368: *** Error: Could not copy override ACPI table, AE_NO_MEMORY Also, the before and after acpidump's don't show anything different. So, I'm curious if wmbatt is still working for Tony and Robert or not with the latest -current. The other problem I'm having is that doing 'sysctl -a', or just 'sysctl hw.acpi' locks the system tight for a couple minutes, and never completes. The last line that's printed to the screen is: hw.acpi.thermal.tz1._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 Any ideas on that one? Thanks, Doug /boot/loader.conf is now hw.pci.allow_unsupported_io_range=1 acpi_dsdt_load=YES acpi_dsdt_name=/boot/acpi_dsdt.aml -- This .signature sanitized for your protection ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACPI problems with Compaq Evo N610c
I don't seem to have these problems. I use xbattbar without problem. I use this acpi_dsdt code: http://www.guldan.cistron.nl/acpi_dsdt.dsl On Sun, Aug 31, 2003 at 07:50:03PM -0700, Doug Barton wrote: I got interested in this recently because I inherited one of these laptops from work. On Wed, 30 Jul 2003, Cagle, John (ISS-Houston) wrote: I just updated to F.15, and it does indeed fix the windows bit in the output of 'acpidump -d'. However, even with Tony's recommendation of removing the acquire/release of _GL in methods C12C and C12D, I still can't get xbatt or wmbattery to run, even with the very latest -current (which has had at least one acpi stack upgrade since 7/30). When I run either command, it locks the box tight. If I ever get a cursor back, I have to Ctrl-Alt-Backspace to get out of X, since I can't actually type anything. I have a feeling that my acpi table didn't actually get overridden though, due to the following from dmesg: ACPI: DSDT was overridden. -0424: *** Error: UtAllocate: Could not allocate size 6e49202a ACPI-0428: *** Error: Could not allocate table memory for [/* ] length 6e49202a ACPI-0368: *** Error: Could not copy override ACPI table, AE_NO_MEMORY Also, the before and after acpidump's don't show anything different. So, I'm curious if wmbatt is still working for Tony and Robert or not with the latest -current. The other problem I'm having is that doing 'sysctl -a', or just 'sysctl hw.acpi' locks the system tight for a couple minutes, and never completes. The last line that's printed to the screen is: hw.acpi.thermal.tz1._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 Any ideas on that one? Thanks, Doug -- Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? FreeBSD: Are you guys coming or what? OpenBSD: He guys you left some holes out there! pgp0.pgp Description: PGP signature
Re: ACPI problems with Compaq Evo N610c
On Mon, 1 Sep 2003, Robert [unknown-8bit] Blacquière wrote: I don't seem to have these problems. I use xbattbar without problem. Argh. How recent is your -current? I compile regularly, and I was up to date as of this afternoon. I use this acpi_dsdt code: http://www.guldan.cistron.nl/acpi_dsdt.dsl Thanks for the suggestion... I tried that one, but got the same error about not enough memory to load the override file. I attached a verbose dmesg, just in case someone wants to take a look. Doug -- This .signature sanitized for your protection ified - using default frequency Timecounter i8254 frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 1794188892 Hz CPU: Mobile Intel(R) Pentium(R) 4 - M CPU 1.80GHz (1794.19-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf27 Stepping = 7 Features=0xbfebf9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE real memory = 536674304 (511 MB) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x00503000 - 0x1f6aafff, 521830400 bytes (127400 pages) avail memory = 51598 (492 MB) bios32: Found BIOS32 Service Directory header at 0xc00fa000 bios32: Entry = 0xf (c00f) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf+0x3a2 pnpbios: Found PnP BIOS data at 0xc00f4330 pnpbios: Entry = f:435e Rev = 1.0 pnpbios: Event flag at f4356 pnpbios: OEM ID 4d00110e Other BIOS signatures found: null: null device, zero device random: entropy source mem: memory I/O Pentium Pro MTRR support enabled VESA: information block 56 45 53 41 00 02 00 01 00 01 01 00 00 00 22 00 00 01 ff 01 00 01 19 01 00 01 2f 01 00 01 34 01 00 01 82 01 0d 01 0e 01 0f 01 20 01 92 01 93 01 94 01 95 01 96 01 a2 01 a3 01 a4 01 a5 01 a6 01 VESA: 60 mode(s) found VESA: v2.0, 32704k memory, flags:0x1, mode table:0xc03f08e2 (122) VESA: ATI MOBILITY RADEON 7500 VESA: ATI Technologies Inc. P7 01.00 ACPI: DSDT was overridden. -0424: *** Error: UtAllocate: Could not allocate size 50204453 ACPI-0428: *** Error: Could not allocate table memory for [/* R] length 50204453 ACPI-0368: *** Error: Could not copy override ACPI table, AE_NO_MEMORY npx0: math processor on motherboard npx0: INT 16 interface acpi0: COMPAQ CPQ00B7 on motherboard pci_open(1):mode 1 addr port (0x0cf8) is 0x80010014 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=1a308086) pcibios: BIOS version 2.10 acpi_bus_number: root bus has no _BBN, assuming 0 AcpiOsDerivePciId: bus 1 dev 0 func 0 acpi_bus_number: root bus has no _BBN, assuming 0 AcpiOsDerivePciId: bus 0 dev 0 func 0 acpi_bus_number: root bus has no _BBN, assuming 0 AcpiOsDerivePciId: bus 2 dev 6 func 0 acpi_bus_number: root bus has no _BBN, assuming 0 AcpiOsDerivePciId: bus 2 dev 6 func 1 acpi_bus_number: root bus has no _BBN, assuming 0 AcpiOsDerivePciId: bus 0 dev 31 func 0 acpi0: power button is handled as a fixed feature programming model. ACPI timer looks GOOD min = 4, max = 4, width = 0 ACPI timer looks GOOD min = 4, max = 4, width = 0 ACPI timer looks GOOD min = 4, max = 4, width = 0 ACPI timer looks GOOD min = 4, max = 4, width = 0 ACPI timer looks GOOD min = 4, max = 4, width = 0 ACPI timer looks GOOD min = 4, max = 4, width = 0 ACPI timer looks GOOD min = 4, max = 4, width = 0 ACPI timer looks GOOD min = 4, max = 4, width = 0 ACPI timer looks GOOD min = 4, max = 4, width = 0 ACPI timer looks GOOD min = 4, max = 4, width = 0 Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) acpi_cpu0: CPU port 0x530-0x537 on acpi0 mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) acpi_tz0: thermal zone port 0x530-0x537 on acpi0 mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) acpi_tz1: thermal zone port 0x530-0x537 on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 initial configuration \\_SB_.C045.C0C2 irq 0: [ 5 10 11] low,level,sharable 0.31.0 \\_SB_.C045.C0C1 irq 11: [ 5 10 11] low,level,sharable 0.31.1 before setting priority for links \\_SB_.C045.C0C2: interrupts: 51011 penalty: 110 110 210 references: 1 priority: 0 before fixup boot-disabled links - \\_SB_.C045.C0C2: interrupts: 51011 penalty: 110 110 210 references: 1 priority: 143 after fixup boot-disabled links -- arbitrated
Re: ACPI problems with Compaq Evo N610c
Oeps I've put the old one up... Now ik have the new one. I don't load the VESA modules, it seems these are loaded before acpi code is replaced? Robert On Mon, Sep 01, 2003 at 01:49:42AM -0700, Doug Barton wrote: On Mon, 1 Sep 2003, Robert [unknown-8bit] Blacquire wrote: I don't seem to have these problems. I use xbattbar without problem. Argh. How recent is your -current? I compile regularly, and I was up to date as of this afternoon. I use this acpi_dsdt code: http://www.guldan.cistron.nl/acpi_dsdt.dsl Thanks for the suggestion... I tried that one, but got the same error about not enough memory to load the override file. I attached a verbose dmesg, just in case someone wants to take a look. Doug -- -- Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? FreeBSD: Are you guys coming or what? OpenBSD: He guys you left some holes out there! pgp0.pgp Description: PGP signature
Re: ACPI problems with Compaq Evo N610c
Doug Barton wrote: I use this acpi_dsdt code: http://www.guldan.cistron.nl/acpi_dsdt.dsl Thanks for the suggestion... I tried that one, but got the same error about not enough memory to load the override file. I attached a verbose dmesg, just in case someone wants to take a look. | ACPI: DSDT was overridden. | -0424: *** Error: UtAllocate: Could not allocate size 50204453 | ACPI-0428: *** Error: Could not allocate table memory for [/* | R] length 50204453 | ACPI-0368: *** Error: Could not copy override ACPI table, AE_NO_MEMORY I'm going to go out on a limb here and suggest that perhaps the problem is that the damn thing appears to be 50 Megabytes... -- Terry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACPI problems with Compaq Evo N610c
On Mon, 1 Sep 2003, Terry Lambert wrote: Doug Barton wrote: I use this acpi_dsdt code: http://www.guldan.cistron.nl/acpi_dsdt.dsl Thanks for the suggestion... I tried that one, but got the same error about not enough memory to load the override file. I attached a verbose dmesg, just in case someone wants to take a look. | ACPI: DSDT was overridden. | -0424: *** Error: UtAllocate: Could not allocate size 50204453 | ACPI-0428: *** Error: Could not allocate table memory for [/* | R] length 50204453 | ACPI-0368: *** Error: Could not copy override ACPI table, AE_NO_MEMORY I'm going to go out on a limb here and suggest that perhaps the problem is that the damn thing appears to be 50 Megabytes... Well, you could have verified that easily enough for yourself by downloading the file at that URL above. :) It turns out that it's only 142k, which is another reason I think that something very odd is happening. Doug -- This .signature sanitized for your protection ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACPI problems with Compaq Evo N610c
Doug Barton wrote: On Mon, 1 Sep 2003, Terry Lambert wrote: I attached a verbose dmesg, just in case someone wants to take a look. | ACPI: DSDT was overridden. | -0424: *** Error: UtAllocate: Could not allocate size 50204453 | ACPI-0428: *** Error: Could not allocate table memory for [/* | R] length 50204453 | ACPI-0368: *** Error: Could not copy override ACPI table, AE_NO_MEMORY I'm going to go out on a limb here and suggest that perhaps the problem is that the damn thing appears to be 50 Megabytes... Well, you could have verified that easily enough for yourself by downloading the file at that URL above. :) And getting 50M, if your dmesg was right... 8-) 8-). It turns out that it's only 142k, which is another reason I think that something very odd is happening. My guesses, in order, would be (1) an unitialized variable, or (2) it loads sparsely, or (3) it has a really bogus table entry that claims it needs that much memory. It doesn't look magic enough to be a sign extension/signed-unsigned pun error. Other than starting at the code that's supposed to load the table in, and printf'ing until you find out why it's thinks 50M is a nuce number, I don't know what to tell you... -- Terry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Thinkpad R40 and ACPI problems on current
Please submit a PR and send me the PR number. Include full dmesg and a URL to the two files produced by: acpidump -t -d -o my.dsdt my.asl -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Thinkpad R40 and ACPI problems on current
Hi, I have never seen my Notebook shutting down correctly, e.a. I can see the line Powering system off using ACPI and it stays there. Well, it's not critical, because I can still press the power button. But I think it has generally problems with ACPI. This is what I get when booting current (dmesg): acpi0: IBMTP-1Pon motherboard acpi_ec0: embedded controller: ECDT, GPE 0x1c, GLK port 0x66,0x62 on acpi0 pcibios: BIOS version 2.10 Using $PIR table, 12 entries at 0xc00fded0 ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.USB7._INI] (Node 0xc25cd820), AE_AML_REGION_LIMIT acpi0: power button is handled as a fixed feature programming model. Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 acpi_cpu0: CPU port 0x530-0x537 on acpi0 acpi_tz0: thermal zone port 0x530-0x537 on acpi0 acpi_lid0: Control Method Lid Switch on acpi0 acpi_button0: Sleep Button on acpi0 [...] acpi_cmbat0: Control method Battery on acpi0 acpi_cmbat1: Control method Battery on acpi0 acpi_acad0: AC adapter on acpi0 [...] acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0% [...] acpi0: AcpiGetSleepTypeData failed - AE_NOT_FOUND This is _after_ flashing with the latest BIOS. Before flashing, I always got about 2 screens of these Method execution failed messages. After flashing the BIOS the functionality hasn't changed at all, but at least these ugly errors disappeared. I can see the battery status correctly in Gnome2, for example, but what does not work is the sleep and the power button. The sleep button just gives me a message on the console. Playing with acpiconf -s will make the notebook hang. I want to give you information about this notebook and its ACPI capabilities, but I have no idea what's the best way (acpidump?). I could not find any useful hints online and I don't know if it's IBM's fault. Can someone explain what's going on? Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
ACPI problems on Samsung Q10 (AE_AML_NO_RETURN_VALUE /AE_BAD_PARAMETER)
Hi! I recently bought a Samsung Q10 and on both 5.1-RELEASE and -current I get these acpi errors: 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 #0: Sun Jun 22 19:00:44 CEST 2003 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/DEIMOS Preloaded elf kernel /boot/kernel/kernel at 0xc04ee000. Preloaded elf module /boot/kernel/snd_ich.ko at 0xc04ee2bc. Preloaded elf module /boot/kernel/snd_pcm.ko at 0xc04ee368. Preloaded elf module /boot/kernel/acpi.ko at 0xc04ee414. Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 996682387 Hz CPU: Mobile Intel(R) Pentium(R) III CPU - M 1000MHz (996.68-MHz 686-class CPU) Origin = GenuineIntel Id = 0x6b4 Stepping = 4 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 393740288 (375 MB) avail memory = 376864768 (359 MB) Pentium Pro MTRR support enabled npx0: math processor on motherboard npx0: INT 16 interface acpi0: PTLTDRSDT on motherboard pcibios: BIOS version 2.10 Using $PIR table, 9 entries at 0xc00fdf30 acpi0: power button is handled as a fixed feature programming model. Timecounter ACPI-fast frequency 3579545 Hz ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.BAT1._STA] (Node 0xc11ae480), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.BAT1._STA] (Node 0xc11ae480), AE_AML_NO_RETURN_VALUE acpi_timer0: 24-bit timer at 3.579545MHz port 0x8008-0x800b on acpi0 acpi_cpu0: CPU on acpi0 acpi_tz0: thermal zone on acpi0 ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node
Re: ACPI problems on Samsung Q10 (AE_AML_NO_RETURN_VALUE /AE_BAD_PARAMETER)
Hi, I'm seeing similiar things on my setup - both the ACPI Global Lock messages and the wi0 issues. In fact, the wi driver seems to be incredibly unstable - Every half hour or so I need to remove and re-insert the card to regain network connectivity (and ofcourse killall dhclient ; ifconfig wi0 ... ; dhclient wi0 ). I have described my problems in more detail in my thread 'ACPI issues on ThinkPad T21 + Dock'. /Eirik On Mon, 23 Jun 2003 10:40:06 +0200 Hendrik Scholz [EMAIL PROTECTED] wrote: Hi! I recently bought a Samsung Q10 and on both 5.1-RELEASE and -current I get these acpi errors: 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 #0: Sun Jun 22 19:00:44 CEST 2003 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/DEIMOS Preloaded elf kernel /boot/kernel/kernel at 0xc04ee000. Preloaded elf module /boot/kernel/snd_ich.ko at 0xc04ee2bc. Preloaded elf module /boot/kernel/snd_pcm.ko at 0xc04ee368. Preloaded elf module /boot/kernel/acpi.ko at 0xc04ee414. Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 996682387 Hz CPU: Mobile Intel(R) Pentium(R) III CPU - M 1000MHz (996.68-MHz 686-class CPU) Origin = GenuineIntel Id = 0x6b4 Stepping = 4 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE, MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 393740288 (375 MB) avail memory = 376864768 (359 MB) Pentium Pro MTRR support enabled npx0: math processor on motherboard npx0: INT 16 interface acpi0: PTLTDRSDT on motherboard pcibios: BIOS version 2.10 Using $PIR table, 9 entries at 0xc00fdf30 acpi0: power button is handled as a fixed feature programming model. Timecounter ACPI-fast frequency 3579545 Hz ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.BAT1._STA] (Node 0xc11ae480), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.BAT1._STA] (Node 0xc11ae480), AE_AML_NO_RETURN_VALUE acpi_timer0: 24-bit timer at 3.579545MHz port 0x8008-0x800b on acpi0 acpi_cpu0: CPU on acpi0 acpi_tz0: thermal zone on acpi0 ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node
Re: ACPI problems on Samsung Q10 (AE_AML_NO_RETURN_VALUE /AE_BAD_PARAMETER)
Hi! I applied the patch from http://docs.freebsd.org/cgi/getmsg.cgi?fetch=214877+0+archive/2003/freebsd-current/20030615.freebsd-current and the AE_BAD_PARAEMTER error disappers. Hendrik -- Hendrik Scholz - [EMAIL PROTECTED] - http://raisdorf.net/ Forcast for tonight: Dark. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACPI problems on 5.1
On Tue, Jun 17, 2003 at 04:21:41PM +0100, Antony T Curtis wrote: On a Compaq Armada V300 notebook, if I load the acpi module, boot fails after the kernel prints about half a dozen acpi_bus_number: can't get _ADR, fails to detect any of the hardware and panics because of failure to mount root. With the acpi module disabled, the machine is able to boot up. This same machine used to be able to run 5.0-CURRENT with ACPI enabled and I think the ACPICA merge at around May 2003 could be responsible. Hi, Was able to get ACPI working with FreeBSD on my Compaq Evo N800c. I have put up the stuff at my site here - http://khader.net/archives/p/319/c/1#comments Of course, now, acpi_thermal seems to be giving me problems, as it crashes every 5 minutes. Will see if I can get a trace and post the same here. Regards Sid -- Do something unusual today. Pay a bill. Sid Carter - http://khader.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACPI problems on 5.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thanks! I have it working nicely now - without any problems. I decompiled, fixed and compiled... problem sorted :) On Wednesday 18 June 2003 8:58 am, Sid Carter wrote: On Tue, Jun 17, 2003 at 04:21:41PM +0100, Antony T Curtis wrote: On a Compaq Armada V300 notebook, if I load the acpi module, boot fails after the kernel prints about half a dozen acpi_bus_number: can't get _ADR, fails to detect any of the hardware and panics because of failure to mount root. With the acpi module disabled, the machine is able to boot up. This same machine used to be able to run 5.0-CURRENT with ACPI enabled and I think the ACPICA merge at around May 2003 could be responsible. Hi, Was able to get ACPI working with FreeBSD on my Compaq Evo N800c. I have put up the stuff at my site here - http://khader.net/archives/p/319/c/1#comments Of course, now, acpi_thermal seems to be giving me problems, as it crashes every 5 minutes. Will see if I can get a trace and post the same here. Regards Sid - -- Antony T Curtis BSc Unix Analyst Programmer http://homepage.ntlworld.com/antony.t.curtis/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE+8Sq4ql7dp2cddmIRAjtwAJ9zAEI1jC5m7hvLjeHw7N78i1Uf5ACfW9Tf 0wkliqBvDlGpuf9Dc4s/eMo= =E2VV -END PGP SIGNATURE- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
ACPI problems on 5.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On a Compaq Armada V300 notebook, if I load the acpi module, boot fails after the kernel prints about half a dozen acpi_bus_number: can't get _ADR, fails to detect any of the hardware and panics because of failure to mount root. With the acpi module disabled, the machine is able to boot up. This same machine used to be able to run 5.0-CURRENT with ACPI enabled and I think the ACPICA merge at around May 2003 could be responsible. Should I try to get a old copy of the acpica parts or does 5.1 depend on new stuff in it? I am thinking of getting src/sys/dev/acpica and src/sys/contrib/dev/acpica from around 1 April 2003 - -- Antony T Curtis BSc Unix Analyst Programmer http://homepage.ntlworld.com/antony.t.curtis/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE+7zIGql7dp2cddmIRAkXzAKDJqDoXikYCVPmUxaTaM3IVi43KBACgqNie uzODS8XCBODHy8ZRwOVnIDg= =y3on -END PGP SIGNATURE- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
ACPI problems on 5.1-RELEASE
Howdy list, What info do I need to provide, and who do I need to send it to, so that I can get ACPI into a usable state on my IBM A30p thinkpad? The short description of my acpi problems is that I can suspend the laptop with 'acpiconf -s 3', but not with 'acpiconf -s 1', and the laptop never comes back from suspend properly. I have to power down the machine. When I first installed FreeBSD 5.1-Release on this laptop, I could get battery status info out of the 'apm' command, but now it isn't working for some reason. The following are true if the laptop is on battery or mains: apm -l = -1 apm -t = -1 apm -b = 3 apm -a = 1 'apm -b' yields '3', so I assume 'apm' thinks the battery is always charging... My gzipped dmesg.boot is attached. -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
ACPI problems with HEAD and IBM ThinkPad T23
I cvsup'd from 5.0-R to HEAD and enabled ACPI to see if anything had changed in the past 6 months. Indeed, things have, and a few workarounds I had implemented before were no longer needed. However, I still got a host of errors from ACPI upon boot, and some hacks to device.hints were still neccessary to keep my laptop functional through a boot. Attached are my device.hints file and a copy of the dmesg. In particular, the things that bother me are: 1) All of the Method execution failed errors 2) The fact that I have to have a device.hints entry in order to see console message upon boot. (Without this, my system boots up silently and after about 30 seconds, displays the familiar login prompt.) -- Matt Emmerton laptop.dmesg.out Description: Binary data device.hints.out Description: Binary data ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACPI problems with HEAD and IBM ThinkPad T23
From: Matthew Emmerton [EMAIL PROTECTED] Date: Wed, 4 Jun 2003 10:00:53 -0400 Sender: [EMAIL PROTECTED] This is a multi-part message in MIME format. --=_NextPart_000_0069_01C32A80.2F346810 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit I cvsup'd from 5.0-R to HEAD and enabled ACPI to see if anything had changed in the past 6 months. Indeed, things have, and a few workarounds I had implemented before were no longer needed. However, I still got a host of errors from ACPI upon boot, and some hacks to device.hints were still neccessary to keep my laptop functional through a boot. Attached are my device.hints file and a copy of the dmesg. In particular, the things that bother me are: 1) All of the Method execution failed errors 2) The fact that I have to have a device.hints entry in order to see console message upon boot. (Without this, my system boots up silently and after about 30 seconds, displays the familiar login prompt.) On my T30, I get similar messages at startup. Some patches currently under discussion on the ACPI list may (or may not) eliminate them. The messages that the patches (if committed) eliminate are bogus and yours are of the type to be in this class. Take a look at the output of 'sysctl hw.acpi'. The T30 does not support S1, so you need to re-define anything using S1 to use something else or nothing at all. Does S3 work properly? When I suspend my T30, I lose my USB ports until I reboot and suspend does not turn off the backlight on my LCD. (This provides a wonderful demonstration of literal bit rot.) The requirements for hints to get the console to work at boot are surprising. I have never seen this on my T30. How recent is your BIOS? The latest release was on March 6, 2003. I found significant improvement in ACPI after upgrading my firmware! R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACPI problems with HEAD and IBM ThinkPad T23
Matthew Emmerton wrote: I cvsup'd from 5.0-R to HEAD and enabled ACPI to see if anything had changed in the past 6 months. Indeed, things have, and a few workarounds I had implemented before were no longer needed. However, I still got a host of errors from ACPI upon boot, and some hacks to device.hints were still neccessary to keep my laptop functional through a boot. Attached are my device.hints file and a copy of the dmesg. In particular, the things that bother me are: 1) All of the Method execution failed errors As was mentioned in another post, there are many problems and solutions being discussed on the acpi lists. Posting your ASL to those lists might help. 2) The fact that I have to have a device.hints entry in order to see console message upon boot. (Without this, my system boots up silently and after about 30 seconds, displays the familiar login prompt.) This is The Way Things Work. Logial device attachments are no longer compiled into the kernel in 5.x by default (see the entry in GENERIC about this), so you need to define those attachments in the device.hints file. Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACPI problems with HEAD and IBM ThinkPad T23
Matthew Emmerton wrote: I cvsup'd from 5.0-R to HEAD and enabled ACPI to see if anything had changed in the past 6 months. Indeed, things have, and a few workarounds I had implemented before were no longer needed. However, I still got a host of errors from ACPI upon boot, and some hacks to device.hints were still neccessary to keep my laptop functional through a boot. Attached are my device.hints file and a copy of the dmesg. In particular, the things that bother me are: 1) All of the Method execution failed errors As was mentioned in another post, there are many problems and solutions being discussed on the acpi lists. Posting your ASL to those lists might help. What are the lists that I should post to? 2) The fact that I have to have a device.hints entry in order to see console message upon boot. (Without this, my system boots up silently and after about 30 seconds, displays the familiar login prompt.) This is The Way Things Work. Logial device attachments are no longer compiled into the kernel in 5.x by default (see the entry in GENERIC about this), so you need to define those attachments in the device.hints file. Ah, ok. I walked right into this one. I disliked the idea of device.hints (and didn't really understand the overriding concept thereof) so I trashed it and made a minimal version. In my case, the minimal version requires entries for sc0 and fd0. -- Matt Emmerton ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACPI problems with HEAD and IBM ThinkPad T23
On Wed, Jun 04, 2003 at 10:45:21AM -0400, Matthew Emmerton wrote: This is The Way Things Work. Logial device attachments are no longer compiled into the kernel in 5.x by default (see the entry in GENERIC about this), so you need to define those attachments in the device.hints file. Ah, ok. I walked right into this one. I disliked the idea of device.hints (and didn't really understand the overriding concept thereof) so I trashed it and made a minimal version. In my case, the minimal version requires entries for sc0 and fd0. Of which sc0 is a bogus requirement. -- Marcel Moolenaar USPA: A-39004 [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACPI problems with HEAD and IBM ThinkPad T23
- Original Message - From: Kevin Oberman [EMAIL PROTECTED] To: Matthew Emmerton [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Wednesday, June 04, 2003 10:21 AM Subject: Re: ACPI problems with HEAD and IBM ThinkPad T23 From: Matthew Emmerton [EMAIL PROTECTED] Date: Wed, 4 Jun 2003 10:00:53 -0400 Sender: [EMAIL PROTECTED] This is a multi-part message in MIME format. --=_NextPart_000_0069_01C32A80.2F346810 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit I cvsup'd from 5.0-R to HEAD and enabled ACPI to see if anything had changed in the past 6 months. Indeed, things have, and a few workarounds I had implemented before were no longer needed. However, I still got a host of errors from ACPI upon boot, and some hacks to device.hints were still neccessary to keep my laptop functional through a boot. Attached are my device.hints file and a copy of the dmesg. In particular, the things that bother me are: 1) All of the Method execution failed errors 2) The fact that I have to have a device.hints entry in order to see console message upon boot. (Without this, my system boots up silently and after about 30 seconds, displays the familiar login prompt.) On my T30, I get similar messages at startup. Some patches currently under discussion on the ACPI list may (or may not) eliminate them. The messages that the patches (if committed) eliminate are bogus and yours are of the type to be in this class. Ahh. Good to hear. Take a look at the output of 'sysctl hw.acpi'. The T30 does not support S1, so you need to re-define anything using S1 to use something else or nothing at all. Same here. Does S3 work properly? When I suspend my T30, I lose my USB ports until I reboot and suspend does not turn off the backlight on my LCD. (This provides a wonderful demonstration of literal bit rot.) I actually make it a habit to never use power-save modes on my T23 when I'm using FreeBSD - I got bit badly once. When I did try it, I lose my backlight, my ethernet (since I was using my Cisco Aironet 350 pccard at the time) and IIRC the system locked up shortly thereafter. The requirements for hints to get the console to work at boot are surprising. I have never seen this on my T30. As pointed out in another note, this is my fault - I trashed the default device.hints and made a minimal version. In my case, it requires entries for sc0 and fd0. How recent is your BIOS? The latest release was on March 6, 2003. I found significant improvement in ACPI after upgrading my firmware! I upgraded to the latest BIOS before sending this report - the dmesg output was the same between my older BIOS (December, IIRC) and the latest BIOS. -- Matt Emmerton ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: secondary ACPI problems
Kevin Oberman writes: From: Andrew Gallatin [EMAIL PROTECTED] Date: Wed, 19 Mar 2003 17:41:17 -0500 (EST) Sender: [EMAIL PROTECTED] Daniel O'Connor writes: Restart X? :-) I wish. The board seems totally gone after an ACPI suspend. This seems to be a common problem with ATI cards. Work-around for M7 cards (may or may not work for others): Switch to a character display (CTRL-ALT-F2) Turn off the display (Fn-F3 on my ThinkPad) Press any key to turn on display Switch back to X (ALT-F9) This solution seems to be dependant on using a laptop. My box is a desktop. I wish there was something I could do to force a reset like this. Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: secondary ACPI problems
On Sat, 14 Dec 2002, Andrew Gallatin wrote: This does not happen if I do not have rp.ko loaded. I suspect that the rocketport card needs some setup when power is restored. It polls all its ports, so it makes sense that a swi would get clogged. I thought it might be sufficent to unload the driver and reload after resume. However, it doens't appear to be unloadable now. Before I get too far into this, will unloading rp and reloading it suffice, or is there a better way which could just allow me to save and restore the card state so I wouldn't have to reload it on resume? See the device_suspend/resume implementations in various drivers (i.e. rl(4)). -Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: secondary ACPI problems
Nate Lawson writes: On Sat, 14 Dec 2002, Andrew Gallatin wrote: This does not happen if I do not have rp.ko loaded. I suspect that the rocketport card needs some setup when power is restored. It polls all its ports, so it makes sense that a swi would get clogged. I thought it might be sufficent to unload the driver and reload after resume. However, it doens't appear to be unloadable now. Before I get too far into this, will unloading rp and reloading it suffice, or is there a better way which could just allow me to save and restore the card state so I wouldn't have to reload it on resume? See the device_suspend/resume implementations in various drivers (i.e. rl(4)). Wow, what a blast from the past! ;) Shouldn't a driver without a suspend/resume implementation implicitly veto the suspend? That's how OS-X does it. Anyway, I'll worry about this when/if somebody can tell me how to get my video back after suspending to S3: [EMAIL PROTECTED]:0:0: class=0x03 card=0x7106174b chip=0x54461002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies' device = 'Rage 128 Pro AGP 4x' class= display Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: secondary ACPI problems
On Wed, 19 Mar 2003, Andrew Gallatin wrote: Nate Lawson writes: On Sat, 14 Dec 2002, Andrew Gallatin wrote: This does not happen if I do not have rp.ko loaded. I suspect that the rocketport card needs some setup when power is restored. It polls all its ports, so it makes sense that a swi would get clogged. I thought it might be sufficent to unload the driver and reload after resume. However, it doens't appear to be unloadable now. Before I get too far into this, will unloading rp and reloading it suffice, or is there a better way which could just allow me to save and restore the card state so I wouldn't have to reload it on resume? See the device_suspend/resume implementations in various drivers (i.e. rl(4)). Wow, what a blast from the past! ;) I am trying to eliminate a backlog of email. I can only manage actually reading cvs-src and developers it seems. Shouldn't a driver without a suspend/resume implementation implicitly veto the suspend? That's how OS-X does it. Currently the default is null_suspend which returns 0 (i.e. ok). You could create a new default, refuse_suspend and then go to all drivers and add an explicit call to null_suspend but I'm not sure this is the best idea. Anyway, I'll worry about this when/if somebody can tell me how to get my video back after suspending to S3: [EMAIL PROTECTED]:0:0: class=0x03 card=0x7106174b chip=0x54461002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies' device = 'Rage 128 Pro AGP 4x' class= display Sorry, I have no knowledge of video hw except that it does need to be reset on suspend. -Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: secondary ACPI problems
On Thu, 2003-03-20 at 08:28, Andrew Gallatin wrote: Shouldn't a driver without a suspend/resume implementation implicitly veto the suspend? That's how OS-X does it. I don't think so - the reason being that when a lot of this stuff was written it was done for APM. Since the OS doesn't _usually_ have to frob the hardware when using APM the default makes sense. Anyway, I'll worry about this when/if somebody can tell me how to get my video back after suspending to S3: [EMAIL PROTECTED]:0:0: class=0x03 card=0x7106174b chip=0x54461002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies' device = 'Rage 128 Pro AGP 4x' class= display Restart X? :-) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: secondary ACPI problems
Daniel O'Connor writes: Restart X? :-) I wish. The board seems totally gone after an ACPI suspend. This seems to be a common problem with ATI cards. Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: secondary ACPI problems
From: Andrew Gallatin [EMAIL PROTECTED] Date: Wed, 19 Mar 2003 17:41:17 -0500 (EST) Sender: [EMAIL PROTECTED] Daniel O'Connor writes: Restart X? :-) I wish. The board seems totally gone after an ACPI suspend. This seems to be a common problem with ATI cards. Work-around for M7 cards (may or may not work for others): Switch to a character display (CTRL-ALT-F2) Turn off the display (Fn-F3 on my ThinkPad) Press any key to turn on display Switch back to X (ALT-F9) R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ACPI problems: ACPI-1287: *** Error: Method execution failedAE_AML_BUFFER_LIMIT
This IBM X-Series 305 show these ACPI problems. And rebooting the box with ACPI enabled hangs it (deadlock). Feb 13 17:41:05 ibm-01 kernel: acpi0: IBMM51SLon motherboard Feb 13 17:41:05 ibm-01 kernel: ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE31 Feb 13 17:41:05 ibm-01 kernel: ACPI-0625: *** Info: GPE Block1 defined as GPE32 to GPE63 Feb 13 17:41:05 ibm-01 kernel: acpi0: power button is handled as a fixed feature programming model. Feb 13 17:41:05 ibm-01 kernel: Timecounter ACPI-safe frequency 3579545 Hz Feb 13 17:41:05 ibm-01 kernel: unknown: I/O range not supported Feb 13 17:41:05 ibm-01 kernel: unknown: I/O range not supported Feb 13 17:41:05 ibm-01 kernel: acpi_timer0: 32-bit timer at 3.579545MHz port 0x40c-0x40f on acpi0 Feb 13 17:41:05 ibm-01 kernel: acpi_cpu0: CPU on acpi0 Feb 13 17:41:05 ibm-01 kernel: pcib0: ACPI Host-PCI bridge on acpi0 Feb 13 17:41:05 ibm-01 kernel: ACPI-1287: *** Error: Method execution failed, AE_AML_BUFFER_LIMIT Feb 13 17:41:05 ibm-01 last message repeated 19 times Any way to work around this ? Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ACPI problems: ACPI-1287: *** Error: Method execution failedAE_AML_BUFFER_LIMIT
Martin Blapp wrote: This IBM X-Series 305 show these ACPI problems. And rebooting the box with ACPI enabled hangs it (deadlock). Feb 13 17:41:05 ibm-01 kernel: acpi0: on motherboard Feb 13 17:41:05 ibm-01 kernel: ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE31 Feb 13 17:41:05 ibm-01 kernel: ACPI-0625: *** Info: GPE Block1 defined as GPE32 to GPE63 Feb 13 17:41:05 ibm-01 kernel: acpi0: power button is handled as a fixed feature programming model. Feb 13 17:41:05 ibm-01 kernel: Timecounter ACPI-safe frequency 3579545 Hz Feb 13 17:41:05 ibm-01 kernel: unknown: I/O range not supported Feb 13 17:41:05 ibm-01 kernel: unknown: I/O range not supported Feb 13 17:41:05 ibm-01 kernel: acpi_timer0: 32-bit timer at 3.579545MHz port 0x40c-0x40f on acpi0 Feb 13 17:41:05 ibm-01 kernel: acpi_cpu0: on acpi0 Feb 13 17:41:05 ibm-01 kernel: pcib0: on acpi0 Feb 13 17:41:05 ibm-01 kernel: ACPI-1287: *** Error: Method execution failed, AE_AML_BUFFER_LIMIT Feb 13 17:41:05 ibm-01 last message repeated 19 times Any way to work around this ? During boot, stop the bootloader and enter: set hint.acpi.0.disabled=1 then: boot This is documented in the troubleshooting section of the 5.0 installation guide =-) Scott To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: [Problems installing 5.0 RC2 on a Compaq Amarda M700 (acpi problems)]
On Tue, Jan 14, 2003 at 02:13:39PM +1100, Simon Coggins wrote: Hi, I'm having a problem installing 5.0 RC2 from cd onto my Compaq amarda M700 laptop. I get errors from acpi on boot that look like: ACPI-1287: *** Method execution failed. AE_AML_BUFFER_LIMIT And a complaint about tempurature. Then it tries to mount the memory file system and hangs. If I use unset acpi_load it boots up, (lots of unknown pci problems) but it boots and will install. After installation the system will not boot as it can't mount the root file system. I get : setrootbyname failed ffs_mountroot: can't find rootvp root mount failed: 6 If I again do a unset acpi_load, the system boots and I can log in. I've tried set hw.acpi.ec.event_driven=1 and that didn't make a different. I've captured acpidump and dmesg if you want to look at that. http://chaotic.oz.org/other/bsd-5.0/erwin-5.0RC2-acpidump.txt http://chaotic.oz.org/other/bsd-5.0/erwin-5.0RC2-dmesg.txt Any ideas? popular answer these days: disable ACPI -- Simon Coggins (SAGE-AU Member)Email: [EMAIL PROTECTED] Network and System Management Officer Phone: +61-2-4221-3775 Information Technology Systems (ITS) Mobile: 0408 115861 University of Wollongong, 2522, Australia Fax: +61-2-4229-1985 Buki -- PGP public key: http://dev.null.cz/buki.asc /\ \ / ASCII Ribbon Campaign X Against HTML Outlook Mail / \ http://www.thebackrow.net To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: [simon@uow.edu.au: Problems installing 5.0 RC2 on a Compaq Amarda M700 (acpi problems)]
Did you try adding hint.acpi.0.disabled=1 to /boot/device.hints http://www.freebsd.org/cgi/man.cgi?query=device.hintssektion=5manpath=FreeBSD+5.0-current On 14 Jan 2003, Simon Coggins wrote: Sent this to questions@ got no response. Hoping someone in here can help me. - Forwarded message from Simon Coggins [EMAIL PROTECTED] - Date: Sat, 11 Jan 2003 21:56:29 +1100 From: Simon Coggins [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Problems installing 5.0 RC2 on a Compaq Amarda M700 (acpi problems) Organisation: University of Wollongong (http://www.uow.edu.au/) Hi, I'm having a problem installing 5.0 RC2 from cd onto my Compaq amarda M700 laptop. I get errors from acpi on boot that look like: ACPI-1287: *** Method execution failed. AE_AML_BUFFER_LIMIT And a complaint about tempurature. Then it tries to mount the memory file system and hangs. If I use unset acpi_load it boots up, (lots of unknown pci problems) but it boots and will install. After installation the system will not boot as it can't mount the root file system. I get : setrootbyname failed ffs_mountroot: can't find rootvp root mount failed: 6 If I again do a unset acpi_load, the system boots and I can log in. I've tried set hw.acpi.ec.event_driven=1 and that didn't make a different. I've captured acpidump and dmesg if you want to look at that. http://chaotic.oz.org/other/bsd-5.0/erwin-5.0- RC2-acpidump.txt http://chaotic.oz.org/other/- bsd-5.0/erwin-5.0RC2-dmesg.txt Any ideas? -- Simon Coggins (SAGE-AU Member) Email: [EMAIL PROTECTED] Network and System Management Officer Phone: +61-2-4221-3775 Information Technology Systems (ITS) Mobile: 0408 115861 University of Wollongong, 2522, Australia Fax: +61-2-4229-1985 - End forwarded message - -- Simon Coggins (SAGE-AU Member) Email: [EMAIL PROTECTED] Network and System Management Officer Phone: +61-2-4221-3775 Information Technology Systems (ITS) Mobile: 0408 115861 University of Wollongong, 2522, Australia Fax: +61-2-4229-1985 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
[simon@uow.edu.au: Problems installing 5.0 RC2 on a Compaq Amarda M700 (acpi problems)]
Sent this to questions@ got no response. Hoping someone in here can help me. - Forwarded message from Simon Coggins [EMAIL PROTECTED] - Date: Sat, 11 Jan 2003 21:56:29 +1100 From: Simon Coggins [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Problems installing 5.0 RC2 on a Compaq Amarda M700 (acpi problems) Organisation: University of Wollongong (http://www.uow.edu.au/) Hi, I'm having a problem installing 5.0 RC2 from cd onto my Compaq amarda M700 laptop. I get errors from acpi on boot that look like: ACPI-1287: *** Method execution failed. AE_AML_BUFFER_LIMIT And a complaint about tempurature. Then it tries to mount the memory file system and hangs. If I use unset acpi_load it boots up, (lots of unknown pci problems) but it boots and will install. After installation the system will not boot as it can't mount the root file system. I get : setrootbyname failed ffs_mountroot: can't find rootvp root mount failed: 6 If I again do a unset acpi_load, the system boots and I can log in. I've tried set hw.acpi.ec.event_driven=1 and that didn't make a different. I've captured acpidump and dmesg if you want to look at that. http://chaotic.oz.org/other/bsd-5.0/erwin-5.0RC2-acpidump.txt http://chaotic.oz.org/other/bsd-5.0/erwin-5.0RC2-dmesg.txt Any ideas? -- Simon Coggins (SAGE-AU Member)Email: [EMAIL PROTECTED] Network and System Management Officer Phone: +61-2-4221-3775 Information Technology Systems (ITS) Mobile: 0408 115861 University of Wollongong, 2522, Australia Fax: +61-2-4229-1985 - End forwarded message - -- Simon Coggins (SAGE-AU Member)Email: [EMAIL PROTECTED] Network and System Management Officer Phone: +61-2-4221-3775 Information Technology Systems (ITS) Mobile: 0408 115861 University of Wollongong, 2522, Australia Fax: +61-2-4229-1985 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
secondary ACPI problems
Hi, I've got an Intel D845EBG2. I have 2 ACPI related problems I'm looking for advice on: - ATI Rage 128 Pro TF If I suspend to S3 from text mode on console, the screen remains blank after resume. The system is otherwise functional, and can be logged into remotely. If I start X after resume, the system locks solid. If I suspend from inside X, the system locks solid a few seconds after resume. I'm happy to replace the ATI with something which works. So.. is there a cheap AGP4x video card (to drive analog LCD 1280x1024@60Hz) which is known to work well with ACPI on FreeBSD? - rp.ko If I suspend to S3 and resume, the system becomes nearly unusable because it spends all its time in swi6: tty:sio clock (200%, in fact!:) Ping times go from 3ms to 11000ms from nearby powerbook. Commands take seconds to echo, etc. This does not happen if I do not have rp.ko loaded. I suspect that the rocketport card needs some setup when power is restored. It polls all its ports, so it makes sense that a swi would get clogged. I thought it might be sufficent to unload the driver and reload after resume. However, it doens't appear to be unloadable now. Before I get too far into this, will unloading rp and reloading it suffice, or is there a better way which could just allow me to save and restore the card state so I wouldn't have to reload it on resume? Thanks, Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ACPI problems on -current
I am running -current with NEWCARD on a thinkpad x20. The system has a builtin 3com ethernet card that attaches on the xl driver, and I have a wavelan card. Neither network card functions when the ACPI module is loaded, but work perfectly with no acpi. Anyone have any ideas what the problem may be? The error messages I see from the wavelan card seem to indicate an interrupt problem, but it gets the same irq w/o the module and works fine. WNM -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ACPI problems on -current
In message [EMAIL PROTECTED] Wesley Morgan writes: : Anyone have any ideas what the problem may be? The error messages I see : from the wavelan card seem to indicate an interrupt problem, but it gets : the same irq w/o the module and works fine. With all due respect, this report is too vague to do anything useful with. At the very least, we need the error messages, and likely a full boot -v dmesg to even begin to track down the problem. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ACPI problems on -current
I placed the verbose boot dmesg's at www.chemikals.org/acpi and www.chemikals.org/no-acpi Thanks in advance for any help rendered! On Tue, 20 Nov 2001, Warner Losh wrote: In message [EMAIL PROTECTED] Wesley Morgan writes: : Anyone have any ideas what the problem may be? The error messages I see : from the wavelan card seem to indicate an interrupt problem, but it gets : the same irq w/o the module and works fine. With all due respect, this report is too vague to do anything useful with. At the very least, we need the error messages, and likely a full boot -v dmesg to even begin to track down the problem. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-mobile in the body of the message -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ACPI problems
Mike Smith wrote: This is the general form of a different problem. The hints DO NOT supply PNP identifiers. Got it yet? You are adding nothing useful in terms of forward progress on solving his problem by commenting on my postings instead of addressing his issues, which I have at least attempted to address, in the absence of direct participation by you. A quick hack, which was iscussed but not implemented at the time I read the message about it, would be to disable the ACPI timer It's a) implemented and b) documented in the acpi(4) manpage (and has been for some time). Perhaps you are reading only my postings, and have missed the fact that _he is not running ACPI_. Thanks, -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ACPI problems
Since you posted this message to -current, I just assumed you had upgraded to the latest code, and thus were using ACPI (this is the same thing that ended up confusing Mike Smith, who also made the mistake in correcting me to say that ACPI was being loaded twice on your system). Actually, I said that this was a possible problem. The general form of the problem is: 1) PnP BIOS tells FreeBSD about the devices 2) The device.hints tells FreeBSD about the devices This is the general form of a different problem. The hints DO NOT supply PNP identifiers. Got it yet? A quick hack, which was iscussed but not implemented at the time I read the message about it, would be to disable the ACPI timer It's a) implemented and b) documented in the acpi(4) manpage (and has been for some time). To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ACPI problems
Terry Lambert wrote: unknown: PNP0400 can't assign resources unknown: PNP0400 at port 0x378-0x37f on isa0 unknown: PNP0501 can't assign resources unknown: PNP0501 at port 0x3f8-0x3ff on isa0 unknown: PNP0501 can't assign resources unknown: PNP0501 at port 0x2f8-0x2ff on isa0 unknown: PNP0f13 can't assign resources unknown: PNP0f13 at irq 12 on isa0 unknown: PNP0303 can't assign resources unknown: PNP0303 at port 0x60 on isa0 unknown: PNP0800 failed to probe at port 0x61 on isa0 Known problem... see the -current archives. You are attaching twice: once because of ACPI, and again because of the hints. You need to comment the entries out of your hints file to make them not get attached twice. Actually not; You missed my comment that the DMESG was WITHOUT the ACPI module loaded; my real problem was a panic long before the serial probes. These pnp messages may be entries in hints twice? Apparently the AMD chipset is not served correctly by this ACPI code; I have this panic on one system and clock problems on another (Aladdin chipset; not that I love Acer) the clock runs almost exactly twice speed with the new ACPI; correctly without.) I saw a major acpi update come through this evening so I'm trying again... (that is, if strfmon and amd compile :-) -- Pete To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ACPI problems
Pete Carah wrote: Known problem... see the -current archives. It *is* a known problem. You are attaching twice: once because of ACPI, and again because of the hints. You need to comment the entries out of your hints file to make them not get attached twice. It's just not this one, since ACPI fails differently. Actually not; You missed my comment that the DMESG was WITHOUT the ACPI module loaded; my real problem was a panic long before the serial probes. These pnp messages may be entries in hints twice? No. They are PnP detected devices being detected twice. Since you posted this message to -current, I just assumed you had upgraded to the latest code, and thus were using ACPI (this is the same thing that ended up confusing Mike Smith, who also made the mistake in correcting me to say that ACPI was being loaded twice on your system). The general form of the problem is: 1) PnP BIOS tells FreeBSD about the devices 2) The device.hints tells FreeBSD about the devices See the -current list archives for details; look for Subject: of Re: unknown PNP hardware. Apparently the AMD chipset is not served correctly by this ACPI code; I have this panic on one system and clock problems on another (Aladdin chipset; not that I love Acer) the clock runs almost exactly twice speed with the new ACPI; correctly without.) I saw a major acpi update come through this evening so I'm trying again... (that is, if strfmon and amd compile :-) There is another known problem with ACER and ACPI timers, which is most properly fixed, as Mike pointed out, by the code checking to see if the timer is insane, and if it is, discarding it and not using it and going the old route instead. A quick hack, which was iscussed but not implemented at the time I read the message about it, would be to disable the ACPI timer (thinking about this, it should be possible to implement at boot time via sysctl to select the timer without the problem, but I have not tested this, and the timecounter code is rather opaque, in that it templates into hidden state containers which are not really globally accessible [made zero system call time functions hard, but not impossible, to write). -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ACPI problems
Mike Smith wrote: unknown: PNP0501 can't assign resources unknown: PNP0501 at port 0x3f8-0x3ff on isa0 unknown: PNP0501 can't assign resources unknown: PNP0501 at port 0x2f8-0x2ff on isa0 Serial ports... [ ... ] You're smoking crack, again. Hints don't supply PnP IDs. Still a known problem... This looks more like both compiling ACPI into the kernel and loading it as a module, or something else equally bogus; devices are being doubly enumerated by a PnP enumerator (ACPI or the PnP BIOS). Check that you're not manually loading the ACPI module, and that you don't have it compiled into your kernel. OK, I give... why wouldn't the first enumerated instance succeed, but the second instance fail? Did it or did it not previously attach the things? -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ACPI problems
Pete Carah wrote: I have a panic that I haven't seen in the notes so far; if I allow load of the acpi module, it gets a can't allocate memory very early in the boot process. Hopefully the following is complete - KDE2 cut-and-paste didn't work as I expected for a big region. [ ... ] unknown: PNP0400 can't assign resources unknown: PNP0400 at port 0x378-0x37f on isa0 unknown: PNP0501 can't assign resources unknown: PNP0501 at port 0x3f8-0x3ff on isa0 unknown: PNP0501 can't assign resources unknown: PNP0501 at port 0x2f8-0x2ff on isa0 unknown: PNP0f13 can't assign resources unknown: PNP0f13 at irq 12 on isa0 unknown: PNP0303 can't assign resources unknown: PNP0303 at port 0x60 on isa0 unknown: PNP0800 failed to probe at port 0x61 on isa0 Known problem... see the -current archives. You are attaching twice: once because of ACPI, and again because of the hints. You need to comment the entries out of your hints file to make them not get attached twice. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ACPI problems
unknown: PNP0400 can't assign resources unknown: PNP0400 at port 0x378-0x37f on isa0 unknown: PNP0501 can't assign resources unknown: PNP0501 at port 0x3f8-0x3ff on isa0 unknown: PNP0501 can't assign resources unknown: PNP0501 at port 0x2f8-0x2ff on isa0 unknown: PNP0f13 can't assign resources unknown: PNP0f13 at irq 12 on isa0 unknown: PNP0303 can't assign resources unknown: PNP0303 at port 0x60 on isa0 unknown: PNP0800 failed to probe at port 0x61 on isa0 Known problem... see the -current archives. You are attaching twice: once because of ACPI, and again because of the hints. You need to comment the entries out of your hints file to make them not get attached twice. You're smoking crack, again. Hints don't supply PnP IDs. This looks more like both compiling ACPI into the kernel and loading it as a module, or something else equally bogus; devices are being doubly enumerated by a PnP enumerator (ACPI or the PnP BIOS). Check that you're not manually loading the ACPI module, and that you don't have it compiled into your kernel. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ACPI problems
I have a panic that I haven't seen in the notes so far; if I allow load of the acpi module, it gets a can't allocate memory very early in the boot process. Hopefully the following is complete - KDE2 cut-and-paste didn't work as I expected for a big region. Motherboard is ASUS A7V with 1.2G processor. DMESG (with old kernel and without ACPI) follows: -- Copyright (c) 1992-2001 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.0-CURRENT #0: Mon Aug 20 22:26:20 PDT 2001 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/SEAGULL Calibrating clock(s) ... TSC clock: 1208810099 Hz, i8254 clock: 1193250 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter i8254 frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter TSC frequency 1208750410 Hz CPU: AMD Athlon(tm) Processor (1208.75-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x642 Stepping = 2 Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR AMD Features=0xc044b18,AMIE,DSP,3DNow! Data TLB: 24 entries, fully associative Instruction TLB: 16 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 internal cache: 256 kbytes, 64 bytes/line, 1 lines/tag, 8-way associative real memory = 805224448 (786352K bytes) Physical memory chunk(s): 0x1000 - 0x0009dfff, 643072 bytes (157 pages) 0x003cf000 - 0x2ffe3fff, 801198080 bytes (195605 pages) avail memory = 776478720 (758280K bytes) bios32: Found BIOS32 Service Directory header at 0xc00f92a0 bios32: Entry = 0xf0f50 (c00f0f50) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf+0x1150 pnpbios: Found PnP BIOS data at 0xc00fc2b0 pnpbios: Entry = f:c2e0 Rev = 1.0 pnpbios: OEM ID cd041 Other BIOS signatures found: Preloaded elf kernel kernel at 0xc03a9000. null: null device, zero device mem: memory I/O Pentium Pro MTRR support enabled Using $PIR table, 9 entries at 0xc00f1720 npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge at pcibus 0 on motherboard pci0: physical bus=0 map[10]: type 3, range 32, base e600, size 25, enabled found- vendor=0x1106, dev=0x0305, revid=0x03 bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 powerspec 2 supports D0 D3 current D0 found- vendor=0x1106, dev=0x8305, revid=0x00 bus=0, slot=1, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 found- vendor=0x1106, dev=0x0686, revid=0x40 bus=0, slot=4, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 powerspec 2 supports D0 D3 current D0 map[20]: type 4, range 32, base d800, size 4, enabled found- vendor=0x1106, dev=0x0571, revid=0x06 bus=0, slot=4, func=1 class=01-01-8a, hdrtype=0x00, mfdev=0 powerspec 2 supports D0 D3 current D0 map[20]: type 4, range 32, base d400, size 5, enabled found- vendor=0x1106, dev=0x3038, revid=0x16 bus=0, slot=4, func=2 class=0c-03-00, hdrtype=0x00, mfdev=0 intpin=d, irq=5 powerspec 2 supports D0 D3 current D0 map[20]: type 4, range 32, base d000, size 5, enabled found- vendor=0x1106, dev=0x3038, revid=0x16 bus=0, slot=4, func=3 class=0c-03-00, hdrtype=0x00, mfdev=0 intpin=d, irq=5 powerspec 2 supports D0 D3 current D0 found- vendor=0x1106, dev=0x3057, revid=0x40 bus=0, slot=4, func=4 class=06-00-00, hdrtype=0x00, mfdev=0 powerspec 2 supports D0 D3 current D0 map[10]: type 1, range 32, base e180, size 12, enabled map[14]: type 4, range 32, base a400, size 6, enabled map[18]: type 1, range 32, base e100, size 20, enabled found- vendor=0x8086, dev=0x1229, revid=0x08 bus=0, slot=9, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 intpin=a, irq=5 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 4, range 32, base a000, size 3, enabled map[14]: type 4, range 32, base 9800, size 2, enabled map[18]: type 4, range 32, base 9400, size 3, enabled map[1c]: type 4, range 32, base 9000, size 2, enabled map[20]: type 4, range 32, base 8800, size 6, enabled map[24]: type 1, range 32, base e080, size 17, enabled found- vendor=0x105a, dev=0x0d30, revid=0x02 bus=0, slot=17, func=0 class=01-80-00, hdrtype=0x00, mfdev=0 intpin=a, irq=10 powerspec 1 supports D0 D3 current D0 pci0: PCI bus on pcib0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pcib1: secondary bus 1 pcib1: subordinate bus 1 pcib1: I/O decode0xe000-0xdfff pcib1:
