Date: Sun, 30 Apr 2006 15:22:46 -0700 (PDT) From: =?ISO-8859-1?Q?Mikko_Ty=F6l=E4j=E4rvi?= <mbsd@pacbell.net> To: Mike Silbersack <silby@silby.com> Cc: mobile@freebsd.org Subject: Re: if_bfe and > 1 GB of ram is now fixed (fwd) Message-ID: <20060430151724.N4092@antec.home> In-Reply-To: <20060430163316.B724@odysseus.silby.com> References: <20060429102214.V9858@odysseus.silby.com> <20060430134609.U4092@antec.home> <20060430163316.B724@odysseus.silby.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 30 Apr 2006, Mike Silbersack wrote:
>
> On Sun, 30 Apr 2006, Mikko Työläjärvi wrote:
>
>> Great! However, it does not quite work for me (on -current as of
>> yesterday, with version 1.36 of if_bfe.c). Busdma wants a lock
>> function:
>>
>> panic: driver error: busdma dflt_lock called
>>
>> Using busdma_lock_mutex() and &sc->bfe_mtx results in watchdog
>> timeouts, lots of LORs and no network traffic, so some other lock is
>> apparently needed.
>>
>> Any ideas?
>
> Hm. My bfe machine is running 6.x, so I tested under that only. Can you try
> setting hw.mem=1000M to see if that causes the panic to temporarily go away?
> I'm interested to see if the new code panics only when > 1GB of ram is
> present or if it panics all the time now. :)
Verfied that limiting RAM still works. I guess the code path that
needs the locking isn't being triggered, as it seems to deal with
bounce buffers.
Actually, even with 2G I can get an address via DHCP, do DNS lookups,
ping some hosts and even have a short telnet session without problems.
But starting a web browser or running cvsup instantly results in the
above panic.
/Mikko
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060430151724.N4092>