From owner-freebsd-acpi@FreeBSD.ORG Fri Nov 16 23:23:45 2007 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 5C95B16A46D; Fri, 16 Nov 2007 23:23:45 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.freebsd.org (Postfix) with ESMTP id DFBF513C468; Fri, 16 Nov 2007 23:23:44 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.6/8.13.6) with ESMTP id lAGNNKdK024238; Fri, 16 Nov 2007 18:23:20 -0500 (EST) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: David Wolfskill Date: Fri, 16 Nov 2007 18:23:14 -0500 User-Agent: KMail/1.6.2 References: <200711161338.54270.jkim@FreeBSD.org> <200711161626.46834.jkim@FreeBSD.org> <20071116230910.GZ7943@bunrab.catwhisker.org> In-Reply-To: <20071116230910.GZ7943@bunrab.catwhisker.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200711161823.17730.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV 0.91.2/4820/Fri Nov 16 17:50:55 2007 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: freebsd-acpi@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: [Call for Testers] ACPI-CA 20071114 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: Fri, 16 Nov 2007 23:23:45 -0000 On Friday 16 November 2007 06:09 pm, David Wolfskill wrote: > On Fri, Nov 16, 2007 at 04:26:43PM -0500, Jung-uk Kim wrote: > > ... > > 'Undefined symbol "__mb_sb_limit" is totally unrelated to ACPI, > > i.e., it is caused by recent API breakage. > > That's what I thought, but I also thought it would be useful for me > to report what I saw, rather than what I thought I should have > seen. :-} > > > I think 'make buildworld; make > > installworld' should fix it. Anyway, thanks for testing! > > Well, I re-booted again -- in a slightly different environment (one > where I have a DHCP server on the net), and didn't see a recurrence > of that whine about __mb_sb_limit. > > (I always do a "make buildworld && make kernel && make > installworld" (with appropriate invocations of assorted other > things, such as mergemaster).) > > I tried the Fn+Esc keyboard chord to suspend the machine (from > vty0, rather than X); the power LED started blinking, but screen > didn't even blank. I then tried to resume the machine (by pressing > & releasing the power button quickly); that caused the display to > blank, but I couldn't get it "un-blanked." So I flipped to vty2 > and logged in (blind) and issued "sudo reboot" (which worked). > > On reboot, I tried using "sudo zzz" to suspend the machine. That > did not cause the power LED to blink, but it did cause the display > to blank. I tried pressing & releasing the power button quickly; no > noticable effect. I tried using the Fn+F8 keyboard chord to cause > the display to show something, and it showed what looked like a > strange "test pattern" (sort like a bunch of vertical lines made of > hyphens). Pressing the Fn+F8 keybaord chord again powered the > machine off again, rather quickly. Apparently the disk buffers > were flaushed though, as no file systems were dirty. > > FWIW, I'm pretty sure this is the same (fairly broken) behavior as > I see now. > > The machine is a Dell Inspiron 8200. You mean it did not improve nor regress anything, right? Jung-uk Kim