[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
More power patches
- Subject: More power patches
- From: imp at bsdimp.com (M. Warner Losh)
- Date: Sun Jan 11 16:26:53 2004
In message: <200401120002_(_dot_)_i0C02F7E031685_(_at_)_gw_(_dot_)_catspoiler_(_dot_)_org>
Don Lewis <truckman_(_at_)_FreeBSD_(_dot_)_org> writes:
: On 11 Jan, M. Warner Losh wrote:
: > In message: <20040110_(_dot_)_140024_(_dot_)_12639654_(_dot_)_imp_(_at_)_bsdimp_(_dot_)_com>
: > "M. Warner Losh" <imp_(_at_)_bsdimp_(_dot_)_com> writes:
: > : In message: <20040110093526_(_dot_)_13ec4aa5_(_dot_)_nork_(_at_)_FreeBSD_(_dot_)_org>
: > : Norikatsu Shigemura <nork_(_at_)_FreeBSD_(_dot_)_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
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
I don't understand that one at all.. Unless it is a failure message
is a cut-n-pasto or something weird is happening.