From owner-freebsd-current Thu Sep 14 23: 0:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp02.iafrica.com (smtp02.iafrica.com [196.7.0.140]) by hub.freebsd.org (Postfix) with ESMTP id 8FF0037B423 for ; Thu, 14 Sep 2000 23:00:50 -0700 (PDT) Received: from [196.7.18.138] (helo=grimreaper.grondar.za ident=root) by smtp02.iafrica.com with esmtp (Exim 1.92 #1) id 13ZoYA-0002KN-00; Fri, 15 Sep 2000 08:00:44 +0200 Received: from grimreaper.grondar.za (mark@localhost [127.0.0.1]) by grimreaper.grondar.za (8.11.0/8.11.0) with ESMTP id e8F5xan02671; Fri, 15 Sep 2000 07:59:51 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200009150559.e8F5xan02671@grimreaper.grondar.za> To: John Baldwin Cc: current@FreeBSD.ORG Subject: Re: SMPNG kernel on UP References: <200009141928.MAA85518@pike.osd.bsdi.com> In-Reply-To: <200009141928.MAA85518@pike.osd.bsdi.com> ; from John Baldwin "Thu, 14 Sep 2000 12:28:09 MST." Date: Fri, 15 Sep 2000 07:59:36 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > : 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? Not a synchronization thing. I made sure of that. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message