From owner-freebsd-mobile@FreeBSD.ORG  Sat Jan 10 13:00:43 2004
Return-Path: <owner-freebsd-mobile@FreeBSD.ORG>
Delivered-To: freebsd-mobile@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 7E48B16A4CE; Sat, 10 Jan 2004 13:00:43 -0800 (PST)
Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 5D24943D58; Sat, 10 Jan 2004 13:00:42 -0800 (PST)
	(envelope-from imp@bsdimp.com)
Received: from localhost (warner@rover2.village.org [10.0.0.1])
	by harmony.village.org (8.12.10/8.12.9) with ESMTP id i0AL0fET028341;
	Sat, 10 Jan 2004 14:00:41 -0700 (MST)
	(envelope-from imp@bsdimp.com)
Date: Sat, 10 Jan 2004 14:00:24 -0700 (MST)
Message-Id: <20040110.140024.12639654.imp@bsdimp.com>
To: nork@FreeBSD.org
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <20040110093526.13ec4aa5.nork@FreeBSD.org>
References: <20040107.171023.63338658.imp@bsdimp.com>
	<20040110093526.13ec4aa5.nork@FreeBSD.org>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
cc: mobile@FreeBSD.org
Subject: Re: More power patches
X-BeenThere: freebsd-mobile@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Mobile computing with FreeBSD <freebsd-mobile.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-mobile>,
	<mailto:freebsd-mobile-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-mobile>
List-Post: <mailto:freebsd-mobile@freebsd.org>
List-Help: <mailto:freebsd-mobile-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-mobile>,
	<mailto:freebsd-mobile-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Jan 2004 21:00:43 -0000

In message: <20040110093526.13ec4aa5.nork@FreeBSD.org>
            Norikatsu Shigemura <nork@FreeBSD.org> writes:
: cbb1: Lazy allocation of 0x1000 bytes rid 0x10 type 3 at 0xe0203d00
                          ^^^^^^^                          ^^^^^^^^^^

This is the problem.  Notice the alignment of the resource allocated.
This is bogus.

Warner