From owner-freebsd-acpi@FreeBSD.ORG Sun Nov 1 19:24:36 2009 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1F7B7106566B for ; Sun, 1 Nov 2009 19:24:36 +0000 (UTC) (envelope-from bahamasfranks@gmail.com) Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by mx1.freebsd.org (Postfix) with ESMTP id EFB4E8FC0A for ; Sun, 1 Nov 2009 19:24:35 +0000 (UTC) Received: by pwj8 with SMTP id 8so1601374pwj.3 for ; Sun, 01 Nov 2009 11:24:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=RYcJtetYLamxx5cK54o99BZVfeGE9xdvWD2JMW8QXE4=; b=QiJoHE5btnJar0fhbmpBpwwM3Un8UjjD5KxiryJijNFrO2GDdvur2VOhPyt18pXAjB bxNHnKGmP18fTPc6MCpYfan28S155vaOCpA5KIutU1owdEsS+X+Usf2Gw79uaRtaPBEX 5snXSMF9GrJQQ2QBLfx01ziF59AcI2FYQlmEE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=SX/9MNx888dBdk3M7zxub06KisRe0akgRVsvVkixngK6jrI/YCB2FW0MRUH36l5Eke uKYUNdc19Glu4A5zG2kr6ZQExXCQAtxP5uVJCHvBXITZFmSyxKLK155nA/t1/a/y8Guk RMZ1f7OyqRLial8/ADAuodWTM4D23hSWt2FLs= MIME-Version: 1.0 Received: by 10.142.55.8 with SMTP id d8mr357523wfa.158.1257101743069; Sun, 01 Nov 2009 10:55:43 -0800 (PST) Date: Sun, 1 Nov 2009 11:55:43 -0700 Message-ID: <539c60b90911011055q2444592byac4c2716107786ad@mail.gmail.com> From: Steve Franks To: freebsd-acpi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: suspend help X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Nov 2009 19:24:36 -0000 Hi, I was told on freebsd-questions a couple months back that suspend/resume support is broken on SMP kernels, which is pretty much all my systems in the era of dual-core. Assuming that is not my problem (on amd64 on this particular system), Anyway, when I call acipconf -s3 (in single-user mode or console), my screen flashes black, then comes right back to where is was, but the system is locked. I'm disabling usb, my wifi, linux, and snd_hda in rc.suspend, so I'm probably off on the wrong track, since I can't think of anything else to disable... Thanks, Steve FreeBSD fyre.franks-development.dyndns.biz 8.0-RC1 FreeBSD 8.0-RC1 #0: Thu Sep 17 18:50:57 UTC 2009 root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 2 11:06:47 2009 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D5CC1106568B for ; Mon, 2 Nov 2009 11:06:47 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id A9AF78FC22 for ; Mon, 2 Nov 2009 11:06:47 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nA2B6lkl033494 for ; Mon, 2 Nov 2009 11:06:47 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nA2B6lAn033492 for freebsd-acpi@FreeBSD.org; Mon, 2 Nov 2009 11:06:47 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 2 Nov 2009 11:06:47 GMT Message-Id: <200911021106.nA2B6lAn033492@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-acpi@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-acpi@FreeBSD.org X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Nov 2009 11:06:47 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/139088 acpi [acpi] ACPI Exception: AE_AML_INFINITE_LOOP error o amd64/138210 acpi [acpi] acer aspire 5536 ACPI problems (S3, brightness, o bin/137053 acpi [hang] FreeBSD 8.0 BETA2Compaq Mini 700 locks on boot o kern/137042 acpi [acpi] hp laptop's lcd not wakes up after suspend to r o kern/136808 acpi [acpi] panic when switching to s3 o i386/136008 acpi [acpi] Dell Vostro 1310 will not shutdown (Requires us o bin/135349 acpi [patch] teach acpidump(8) to disassemble arbitrary mem o kern/135070 acpi [acpi] [patch] BIOS resource allocation and FreeBSD AC o kern/132602 acpi [acpi] ACPI Problem with Intel SS4200: System does not o kern/130683 acpi [ACPI] shutdown hangs after syncing disks - ACPI race? o i386/129953 acpi [acpi] ACPI timeout (CDROM) with Shuttle X27D o kern/129618 acpi [acpi] Problem with ACPI on HP Pavilion DV2899 laptop o kern/129563 acpi [acpi] sleep broken on IBM/Lenovo T61 in amd64 mode f kern/128639 acpi [patch] [acpi_asus] acpi for ASUS A6F,A3E,A3F,A3N not f kern/128634 acpi [patch] fix acpi_asus(4) in asus a6f laptop o kern/127581 acpi [patch] [acpi_sony] Add support for more Sony features o kern/124744 acpi [acpi] [patch] incorrect _BST result validation for To o kern/124412 acpi [acpi] power off error on Toshiba M40 laptop o kern/123039 acpi [acpi] ACPI AML_BUFFER_LIMIT errors during boot o kern/121504 acpi [patch] Correctly set hw.acpi.osname on certain machin f kern/121454 acpi [pst] Promise SuperTrak SX6000 does not load during bo o amd64/121439 acpi [boot] Installation of FreeBSD 7.0 fails: ACPI problem o kern/121102 acpi [acpi_fujitsu] [patch] update acpi_fujitsu for the P80 o kern/120515 acpi [acpi] [patch] acpi_alloc_wakeup_handler: can't alloc o kern/119356 acpi [acpi]: i386 ACPI wakeup not work due resource exhaust o kern/119200 acpi [acpi] Lid close switch suspends CPU for 1 second on H o kern/118973 acpi [acpi]: Kernel panic with acpi boot o kern/117605 acpi [acpi] [request] add debug.cpufreq.highest o kern/116939 acpi [acpi] PCI-to-PCI misconfigured for bus three and can o i386/114562 acpi [acpi] cardbus is dead after s3 on Thinkpad T43 with a o kern/114165 acpi [acpi] Dell C810 - ACPI problem s kern/112544 acpi [acpi] [patch] Add High Precision Event Timer Driver f o kern/108954 acpi [acpi] 'sleep(1)' sleeps >1 seconds when speedstep (Cx o kern/108695 acpi [acpi]: Fatal trap 9: general protection fault when in o kern/108488 acpi [acpi] ACPI-1304: *** Error: Method execution failed o kern/108017 acpi [acpi]: Acer Aspire 5600 o kern/106924 acpi [acpi] ACPI resume returns g_vfs_done() errors and ker o kern/105537 acpi [acpi] problems in acpi on HP Compaq nc6320 o kern/104625 acpi ACPI on ASUS A8N-32 SLI/ASUS P4P800 does not show ther o kern/102252 acpi acpi thermal does not work on Abit AW8D (intel 975) o kern/97383 acpi Volume buttons on IBM Thinkpad crash system with ACPI s i386/91748 acpi acpi problem on Acer TravelMare 4652LMi (nvidia panic, s kern/91038 acpi [panic] [ata] [acpi] 6.0-RELEASE on Fujitsu Siemens Am s kern/90243 acpi Laptop fan doesn't turn off (ACPI enabled) (Packard Be o i386/83018 acpi [install] Installer will not boot on Asus P4S8X BIOS 1 f kern/81000 acpi [apic] Via 8235 sound card worked great with FreeBSD 5 o i386/79081 acpi ACPI suspend/resume not working on HP nx6110 o kern/76950 acpi ACPI wrongly blacklisted on Micron ClientPro 766Xi sys s kern/73823 acpi [request] acpi / power-on by timer support o i386/72566 acpi ACPI, FreeBSD disables fan on Compaq Armada 1750 o i386/69750 acpi Boot without ACPI failed on ASUS L5 o kern/56024 acpi ACPI suspend drains battery while in S3 o i386/55661 acpi ACPI suspend/resume problem on ARMADA M700 o i386/54756 acpi ACPI suspend/resume problem on CF-W2 laptop 54 problems total. From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 2 17:03:16 2009 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 509A2106566B for ; Mon, 2 Nov 2009 17:03:16 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 9F5B58FC08 for ; Mon, 2 Nov 2009 17:03:15 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id TAA23185 for ; Mon, 02 Nov 2009 19:03:13 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <4AEF10D0.7020908@icyb.net.ua> Date: Mon, 02 Nov 2009 19:03:12 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.23 (X11/20090825) MIME-Version: 1.0 To: freebsd-acpi@FreeBSD.org X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Subject: for review: retire 'magic' ivar X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Nov 2009 17:03:16 -0000 ACPI bus defines two ivars with similar purposes - magic and private. It seems that this is redundant. Please review the following patch that removes 'magic' ivar. magic is used in three places, please see below for how it is replaced. 1. acpi_cpu magic is used was storing cpu id. Using integer type for that is, of course, more natural, but 'private' (void *) can be used without any problems. 2. acpi_hpet magic is used to distinguish between a device explicitly created in identify and devices auto-created by bus enumeration. The same could be done by examining 'handle' ivar, because bus enumeration always sets handle to non-NULL, but identify doesn't set it. Please note that there is a buglet in current code that doesn't have any practical consequences: magic is set to address of a variable that holds acpi_hpet_devclass, not to the devclass itself. Thus, if hpet driver were ever unloaded and reloaded it wouldn't recognize its device created on the first identify run. 3. acpi_ec magic is used in this driver similarly to acpi_hpet case. Big difference though, is that acpi_ec identify routine also sets handle ivar of explicitly created device. But it also sets private ivar. So we make use of that fact instead: private is set for explicitly created device, while it is not set for auto-created devices. The same buglet with no consequences is also found here. diff --git a/sys/dev/acpica/acpi.c b/sys/dev/acpica/acpi.c index 525824a..4ed7078 100644 --- a/sys/dev/acpica/acpi.c +++ b/sys/dev/acpica/acpi.c @@ -900,9 +900,6 @@ acpi_read_ivar(device_t dev, device_t child, int index, uintptr_t *result) case ACPI_IVAR_HANDLE: *(ACPI_HANDLE *)result = ad->ad_handle; break; - case ACPI_IVAR_MAGIC: - *(uintptr_t *)result = ad->ad_magic; - break; case ACPI_IVAR_PRIVATE: *(void **)result = ad->ad_private; break; @@ -938,9 +935,6 @@ acpi_write_ivar(device_t dev, device_t child, int index, uintptr_t value) case ACPI_IVAR_HANDLE: ad->ad_handle = (ACPI_HANDLE)value; break; - case ACPI_IVAR_MAGIC: - ad->ad_magic = (uintptr_t)value; - break; case ACPI_IVAR_PRIVATE: ad->ad_private = (void *)value; break; diff --git a/sys/dev/acpica/acpi_cpu.c b/sys/dev/acpica/acpi_cpu.c index 8fe9de6..c16dcb1 100644 --- a/sys/dev/acpica/acpi_cpu.c +++ b/sys/dev/acpica/acpi_cpu.c @@ -255,7 +255,7 @@ acpi_cpu_probe(device_t dev) /* Mark this processor as in-use and save our derived id for attach. */ cpu_softc[cpu_id] = (void *)1; - acpi_set_magic(dev, cpu_id); + acpi_set_private(dev, (void*)(intptr_t)cpu_id); device_set_desc(dev, "ACPI CPU"); return (0); @@ -286,7 +286,7 @@ acpi_cpu_attach(device_t dev) sc = device_get_softc(dev); sc->cpu_dev = dev; sc->cpu_handle = acpi_get_handle(dev); - cpu_id = acpi_get_magic(dev); + cpu_id = (int)(intptr_t)acpi_get_private(dev); cpu_softc[cpu_id] = sc; pcpu_data = pcpu_find(cpu_id); pcpu_data->pc_device = dev; diff --git a/sys/dev/acpica/acpi_ec.c b/sys/dev/acpica/acpi_ec.c index a5a81dc..b339ba1 100644 --- a/sys/dev/acpica/acpi_ec.c +++ b/sys/dev/acpica/acpi_ec.c @@ -129,9 +129,6 @@ struct acpi_ec_params { int uid; }; -/* Indicate that this device has already been probed via ECDT. */ -#define DEV_ECDT(x) (acpi_get_magic(x) == (uintptr_t)&acpi_ec_devclass) - /* * Driver softc. */ @@ -332,7 +329,6 @@ acpi_ec_ecdt_probe(device_t parent) params->uid = ecdt->Uid; acpi_GetInteger(h, "_GLK", ¶ms->glk); acpi_set_private(child, params); - acpi_set_magic(child, (uintptr_t)&acpi_ec_devclass); /* Finish the attach process. */ if (device_probe_and_attach(child) != 0) @@ -348,6 +344,7 @@ acpi_ec_probe(device_t dev) ACPI_STATUS status; device_t peer; char desc[64]; + int ecdt; int ret; struct acpi_ec_params *params; static char *ec_ids[] = { "PNP0C09", NULL }; @@ -362,11 +359,12 @@ acpi_ec_probe(device_t dev) * duplicate probe. */ ret = ENXIO; - params = NULL; + ecdt = 0; buf.Pointer = NULL; buf.Length = ACPI_ALLOCATE_BUFFER; - if (DEV_ECDT(dev)) { - params = acpi_get_private(dev); + params = acpi_get_private(dev); + if (params != NULL) { + ecdt = 1; ret = 0; } else if (!acpi_disabled("ec") && ACPI_ID_PROBE(device_get_parent(dev), dev, ec_ids)) { @@ -439,7 +437,7 @@ out: if (ret == 0) { snprintf(desc, sizeof(desc), "Embedded Controller: GPE %#x%s%s", params->gpe_bit, (params->glk) ? ", GLK" : "", - DEV_ECDT(dev) ? ", ECDT" : ""); + ecdt ? ", ECDT" : ""); device_set_desc_copy(dev, desc); } diff --git a/sys/dev/acpica/acpi_hpet.c b/sys/dev/acpica/acpi_hpet.c index ac28031..875ef07 100644 --- a/sys/dev/acpica/acpi_hpet.c +++ b/sys/dev/acpica/acpi_hpet.c @@ -66,8 +66,6 @@ static void acpi_hpet_test(struct acpi_hpet_softc *sc); static char *hpet_ids[] = { "PNP0103", NULL }; -#define DEV_HPET(x) (acpi_get_magic(x) == (uintptr_t)&acpi_hpet_devclass) - struct timecounter hpet_timecounter = { .tc_get_timecount = hpet_get_timecount, .tc_counter_mask = ~0u, @@ -153,8 +151,6 @@ acpi_hpet_identify(driver_t *driver, device_t parent) return; } - /* Record a magic value so we can detect this device later. */ - acpi_set_magic(child, (uintptr_t)&acpi_hpet_devclass); bus_set_resource(child, SYS_RES_MEMORY, 0, hpet->Address.Address, HPET_MEM_WIDTH); } @@ -166,7 +162,7 @@ acpi_hpet_probe(device_t dev) if (acpi_disabled("hpet")) return (ENXIO); - if (!DEV_HPET(dev) && + if (acpi_get_handle(dev) != NULL && (ACPI_ID_PROBE(device_get_parent(dev), dev, hpet_ids) == NULL || device_get_unit(dev) != 0)) return (ENXIO); diff --git a/sys/dev/acpica/acpivar.h b/sys/dev/acpica/acpivar.h index f4d27e4..abfaa8b 100644 --- a/sys/dev/acpica/acpivar.h +++ b/sys/dev/acpica/acpivar.h @@ -88,7 +88,6 @@ struct acpi_softc { struct acpi_device { /* ACPI ivars */ ACPI_HANDLE ad_handle; - uintptr_t ad_magic; void *ad_private; int ad_flags; @@ -224,7 +223,7 @@ extern int acpi_quirks; * attach to ACPI. */ #define ACPI_IVAR_HANDLE 0x100 -#define ACPI_IVAR_MAGIC 0x101 +#define ACPI_IVAR_UNUSED 0x101 /* Unused/reserved. */ #define ACPI_IVAR_PRIVATE 0x102 #define ACPI_IVAR_FLAGS 0x103 @@ -250,7 +249,6 @@ } __ACPI_BUS_ACCESSOR(acpi, handle, ACPI, HANDLE, ACPI_HANDLE) -__ACPI_BUS_ACCESSOR(acpi, magic, ACPI, MAGIC, uintptr_t) __ACPI_BUS_ACCESSOR(acpi, private, ACPI, PRIVATE, void *) __ACPI_BUS_ACCESSOR(acpi, flags, ACPI, FLAGS, int) -- Andriy Gapon From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 3 15:30:07 2009 Return-Path: Delivered-To: freebsd-acpi@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 62C9B1065679 for ; Tue, 3 Nov 2009 15:30:07 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 51FD58FC0A for ; Tue, 3 Nov 2009 15:30:07 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nA3FU6DZ047656 for ; Tue, 3 Nov 2009 15:30:06 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nA3FU60M047653; Tue, 3 Nov 2009 15:30:06 GMT (envelope-from gnats) Date: Tue, 3 Nov 2009 15:30:06 GMT Message-Id: <200911031530.nA3FU60M047653@freefall.freebsd.org> To: freebsd-acpi@FreeBSD.org From: Alexander Best Cc: Subject: Re: kern/136808: [acpi] panic when switching to s3 X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Alexander Best List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 15:30:07 -0000 The following reply was made to PR kern/136808; it has been noted by GNATS. From: Alexander Best To: Cc: Subject: Re: kern/136808: [acpi] panic when switching to s3 Date: Tue, 03 Nov 2009 16:27:19 +0100 (CET) running FreeBSD otaku 9.0-CURRENT FreeBSD 9.0-CURRENT #0 r198850: Tue Nov 3 13:00:55 CET 2009 root@otaku:/usr/obj/usr/src/sys/ARUNDEL i386 shipped with debug.acpi.acpi_ca_version: 20091013 this panic no longer occurs. S3 however still doesn't work. the computer shuts down, but then instantly comes back up again. this however results in a state where no video signal is being sent to the monitor and nothing seems to happen (no hdd activity). after a hard reset the computer boots regularly (with all fs being clean). please ask if you need any more details about configs, sysctl values etc. alex From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 3 16:51:25 2009 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5B7FD106568D for ; Tue, 3 Nov 2009 16:51:25 +0000 (UTC) (envelope-from dgerow@afflictions.org) Received: from slow3-v.mail.gandi.net (slow3-v.mail.gandi.net [217.70.178.89]) by mx1.freebsd.org (Postfix) with ESMTP id 1DC5D8FC12 for ; Tue, 3 Nov 2009 16:51:25 +0000 (UTC) Received: from relay2-v.mail.gandi.net (relay2-v.mail.gandi.net [217.70.178.76]) by slow3-v.mail.gandi.net (Postfix) with ESMTP id 69ACC3BBB6 for ; Tue, 3 Nov 2009 17:18:59 +0100 (CET) Received: from plebeian.afflictions.org (CPE000db917e8b9-CM0019475d4056.cpe.net.cable.rogers.com [99.241.167.27]) by relay2-v.mail.gandi.net (Postfix) with ESMTP id E46C8135D8 for ; Tue, 3 Nov 2009 17:18:57 +0100 (CET) Received: by plebeian.afflictions.org (Postfix, from userid 1001) id 4BB98105C2; Tue, 3 Nov 2009 11:18:48 -0500 (EST) Date: Tue, 3 Nov 2009 11:18:48 -0500 From: Damian Gerow To: freebsd-acpi@freebsd.org Message-ID: <20091103161847.GA46493@plebeian.afflictions.org> References: <539c60b90911011055q2444592byac4c2716107786ad@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <539c60b90911011055q2444592byac4c2716107786ad@mail.gmail.com> User-Agent: Mutt/1.5.20 (2009-06-14) Subject: Re: suspend help X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2009 16:51:25 -0000 Steve Franks wrote: : I was told on freebsd-questions a couple months back that : suspend/resume support is broken on SMP kernels, which is pretty much : all my systems in the era of dual-core. Assuming that is not my : problem (on amd64 on this particular system), I believe that's only true for i386. I currently use S3 sleep without issue regularly, on an SMP amd64 laptop. Which branch are you using? : Anyway, when I call acipconf -s3 (in single-user mode or console), my : screen flashes black, then comes right back to where is was, but the : system is locked. I'm disabling usb, my wifi, linux, and snd_hda in : rc.suspend, so I'm probably off on the wrong track, since I can't : think of anything else to disable... Are you in X at the time? Could you look into setting up something like textdump(4) to see if your system is panicing?