From owner-freebsd-ia64@FreeBSD.ORG Mon Jun 2 14:51:58 2003 Return-Path: Delivered-To: freebsd-ia64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 28A6F37B401 for ; Mon, 2 Jun 2003 14:51:58 -0700 (PDT) Received: from ns1.xcllnt.net (209-128-86-226.BAYAREA.NET [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E0F343F75 for ; Mon, 2 Jun 2003 14:51:57 -0700 (PDT) (envelope-from marcel@xcllnt.net) Received: from dhcp01.pn.xcllnt.net (dhcp01.pn.xcllnt.net [192.168.4.201]) by ns1.xcllnt.net (8.12.9/8.12.9) with ESMTP id h52Lpvwk003934; Mon, 2 Jun 2003 14:51:57 -0700 (PDT) (envelope-from marcel@piii.pn.xcllnt.net) Received: from dhcp01.pn.xcllnt.net (localhost [127.0.0.1]) by dhcp01.pn.xcllnt.net (8.12.9/8.12.9) with ESMTP id h52LpufA001432; Mon, 2 Jun 2003 14:51:56 -0700 (PDT) (envelope-from marcel@dhcp01.pn.xcllnt.net) Received: (from marcel@localhost) by dhcp01.pn.xcllnt.net (8.12.9/8.12.9/Submit) id h52Lpuqs001431; Mon, 2 Jun 2003 14:51:56 -0700 (PDT) Date: Mon, 2 Jun 2003 14:51:56 -0700 From: Marcel Moolenaar To: Alan Robinson Message-ID: <20030602215156.GB1345@dhcp01.pn.xcllnt.net> References: <20030530132408.A3690@fujitsu-siemens.com> <20030530173029.GB568@dhcp01.pn.xcllnt.net> <20030602133112.A3892@fujitsu-siemens.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030602133112.A3892@fujitsu-siemens.com> User-Agent: Mutt/1.5.4i cc: freebsd-ia64@freebsd.org Subject: Re: /dev/kmem read return value is double requested value X-BeenThere: freebsd-ia64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the IA-64 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jun 2003 21:51:58 -0000 On Mon, Jun 02, 2003 at 01:31:12PM +0200, Alan Robinson wrote: > > > > It helps if you demonstrate the behaviour with some trivial test program > > that people can run too. > > > You are quite correct. I didn't even say the problem only seems to show > up when trying to read info from kld loaded drivers, an example. That's odd. And yes, that can't be right :-) I'll take a look at it when I have a spare cycle. Thanks, -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net