From owner-freebsd-alpha Tue Oct 10 18: 2:48 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 006B437B502 for ; Tue, 10 Oct 2000 18:02:47 -0700 (PDT) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id SAA14397; Tue, 10 Oct 2000 18:02:40 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.0/8.11.0) id e9B12d437311; Tue, 10 Oct 2000 18:02:39 -0700 (PDT) (envelope-from jdp) Date: Tue, 10 Oct 2000 18:02:39 -0700 (PDT) From: jdp@polstra.com Message-Id: <200010110102.e9B12d437311@vashon.polstra.com> To: alpha@freebsd.org Cc: gallatin@cs.duke.edu Subject: Re: can read return MORE than you asked for? In-Reply-To: <14819.36145.726782.115049@grasshopper.cs.duke.edu> References: <14819.36145.726782.115049@grasshopper.cs.duke.edu> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <14819.36145.726782.115049@grasshopper.cs.duke.edu>, Andrew Gallatin wrote: > > When looking into the "swapinfo:cannot read blmeta_t" problem, I > discovered that reading /dev/kmem seems to be somewhat broken: > > <..> > lseek(4,0xfffffe00006b8428,-3399988123389603632) = 7046184 (0x6b8428) > read(0x4,0x11ffa2d0,0x8) = 16 (0x10) > <..> > > Note the return value of read -- 2x what we asked for! Ah, but you're on an Alpha, where everything is twice as big. :-) John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message