From owner-freebsd-current Thu Sep 14 12:29:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 2A56C37B423 for ; Thu, 14 Sep 2000 12:29:31 -0700 (PDT) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id MAA85518; Thu, 14 Sep 2000 12:28:09 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200009141928.MAA85518@pike.osd.bsdi.com> Subject: Re: SMPNG kernel on UP In-Reply-To: <200009140605.AAA94177@harmony.village.org> from Warner Losh at "Sep 14, 2000 00:05:03 am" To: Warner Losh Date: Thu, 14 Sep 2000 12:28:09 -0700 (PDT) Cc: Mark Murray , current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > In message <200009140602.e8E628n03046@grimreaper.grondar.za> Mark Murray writes: > : > In message <200009080636.e886aCG18672@billy-club.village.org> Warner Losh wri > : tes: > : > : 2) APM is now broken. It worked after the ACPI integration, > : > : but after the SMPNG stuff neither apm -z nor the BIOS keys > : > : seems to suspend. > : > > : > Turns out this isn't the case. > : > : shutdown -p does not turn off the machine for me (Libretto 110ct). > : > : zzz/apm -z gives me "apm: ioctl(APMIO_SUSPEND): Invalid argument" > > I noticed this with the first SMPNG kernel I tried. The newer one > this problem disappeared. Don't know why it would matter, but I may > have missed a commit while in new mexico. It may be a kernel/world sync problem. Although I don't know why the ioctl argument would suddenly become invalid. Maybe it passes in a struct ucred, which changed in size just before the SMPng commit? > Warner -- John Baldwin -- http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message