Date: Sun, 11 Jan 2004 17:26:27 -0700 (MST) From: "M. Warner Losh" <imp@bsdimp.com> To: truckman@FreeBSD.org Cc: mobile@FreeBSD.org Subject: Re: More power patches Message-ID: <20040111.172627.84647422.imp@bsdimp.com> In-Reply-To: <200401120002.i0C02F7E031685@gw.catspoiler.org> References: <20040111.155500.121671029.imp@bsdimp.com> <200401120002.i0C02F7E031685@gw.catspoiler.org>
index | next in thread | previous in thread | raw e-mail
In message: <200401120002.i0C02F7E031685@gw.catspoiler.org>
Don Lewis <truckman@FreeBSD.org> writes:
: On 11 Jan, M. Warner Losh wrote:
: > In message: <20040110.140024.12639654.imp@bsdimp.com>
: > "M. Warner Losh" <imp@bsdimp.com> writes:
: > : 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.
: >
: > I think I have a fix for this, and hope to get an updated patch out...
:
: That doesn't appear to be the cause of the breakage I'm seeing ...
:
: > fwohci0: <1394 Open Host Controller Interface> mem 0xc0204000-0xc0207fff,0xc0209000-0xc02097ff irq 11 at device 7.0 on pci2
: > fwohci0: Bus reserved 0x800 bytes for rid 0x10 type 3 at 0xc0209000
:
: Hmn, maybe that is the problem. I just took a closer look and earlier
: in the boot I see:
:
: > cbb0: Lazy allocation of 0x1000 bytes rid 0x10 type 3 at 0xc0209800
:
: I bet cbb0 thinks that it is at 0xc0209000, which might interfere with
: fwohci0.
Yes. That would, since both of them are trying to decode 0xc0209000.
: There is still the issue of the irq breakage caused by the attach
: failure.
I don't understand that one at all.. Unless it is a failure message
is a cut-n-pasto or something weird is happening.
Warner
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040111.172627.84647422.imp>