From owner-freebsd-current Mon Feb 17 15: 3:21 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3C3F237B401 for ; Mon, 17 Feb 2003 15:03:09 -0800 (PST) Received: from lenny.anarcat.ath.cx (dsl-135-123.aei.ca [66.36.135.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3065943FA3 for ; Mon, 17 Feb 2003 15:03:07 -0800 (PST) (envelope-from anarcat@lenny.anarcat.ath.cx) Received: from lenny.anarcat.ath.cx (localhost.anarcat.ath.cx [127.0.0.1]) by lenny.anarcat.ath.cx (8.12.6/8.12.6) with ESMTP id h1HN38ri000714 for ; Mon, 17 Feb 2003 18:03:08 -0500 (EST) (envelope-from anarcat@lenny.anarcat.ath.cx) Received: (from anarcat@localhost) by lenny.anarcat.ath.cx (8.12.6/8.12.6/Submit) id h1HN38io000713 for freebsd-current@freebsd.org; Mon, 17 Feb 2003 18:03:08 -0500 (EST) Date: Mon, 17 Feb 2003 18:03:08 -0500 From: The Anarcat To: freebsd-current@freebsd.org Subject: reproducable ACPI hang on 5.0-RELEASE + Asus A7V mobo Message-ID: <20030217230308.GA594@lenny.anarcat.ath.cx> Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="opJtzjQTFsWo+cga" Content-Disposition: inline User-Agent: Mutt/1.5.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --opJtzjQTFsWo+cga Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello! I've been experimenting quite a bit with the new ACPI stuff from 5.0-release. I can reliably hang my box using acpiconf -s 3, both from X and the console. In X, upon wakeup, the screen is trashed with color strips. In the console, I can actually get some interaction back, but the whole thing hangs after a few seconds anyways. This is with an almost GENERIC kernel (attached), on a Asus A7V KT133 motherboard. Any concrete way to debug this? Cause a panic? Should I report this somewhere else since 5.0 !=3D 5.x-current? :) A. 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.0-RELEASE #1: Sun Feb 16 23:11:48 EST 2003 anarcat@lenny.anarcat.ath.cx:/usr/src/sys/i386/compile/LENNII Preloaded elf kernel "/boot/kernel/kernel" at 0xc06a9000. Preloaded elf module "/boot/kernel/snd_emu10k1.ko" at 0xc06a90a8. Preloaded elf module "/boot/kernel/snd_pcm.ko" at 0xc06a9158. Preloaded elf module "/boot/kernel/radeon.ko" at 0xc06a9204. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc06a92b0. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 1008992864 Hz CPU: AMD Duron(tm) Processor (1008.99-MHz 686-class CPU) Origin =3D "AuthenticAMD" Id =3D 0x670 Stepping =3D 0 Features=3D0x383f9ff AMD Features=3D0xffffffffc0440000 real memory =3D 1207877632 (1151 MB) avail memory =3D 1167048704 (1112 MB) Initializing GEOMetry subsystem Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15 Using $PIR table, 9 entries at 0xc00f1750 acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-fast" frequency 3579545 Hz acpi_timer0: <24-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0 acpi_cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xe6000000-0xe7f= fffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 drm0: port 0xd800-0xd8ff mem 0xd7000000-0xd700ffff= ,0xd8000000-0xdfffffff irq 11 at device 0.0 on pci1 info: [drm] AGP at 0xe6000000 32MB info: [drm] Initialized radeon 1.1.1 20010405 on minor 0 isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xb800-0xb80f at device 4.1 on= pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xb400-0xb41f irq 9 at device 4.2 o= n pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xb000-0xb01f irq 9 at device 4.3 o= n pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pci0: at device 4.4 (no driver attached) vr0: port 0x9400-0x94ff mem 0xd6800000-0= xd68000ff irq 9 at device 9.0 on pci0 vr0: Ethernet address: 00:50:ba:64:e3:6a miibus0: on vr0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pcm0: port 0x9000-0x901f irq 5 at device 10.0 on pci0 atapci1: port 0x7000-0x703f,0x7400-0x7403,0x780= 0-0x7807,0x8000-0x8003,0x8400-0x8407 mem 0xd6000000-0xd601ffff irq 10 at de= vice 17.0 on pci0 ata2: at 0x8400 on atapci1 ata3: at 0x7800 on atapci1 fdc0: port 0x3f7,0x= 3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0 port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model MouseMan+, device ID 0 orm0: