Date: Thu, 4 Jan 2001 16:45:26 -0800 (PST) From: Matthew Jacob <mjacob@feral.com> To: =?ISO-8859-1?Q?G=E9rard_Roudier?= <groudier@club-internet.fr> Cc: Yoriaki FUJIMORI <fujimori@grafin.fujimori.cache.waseda.ac.jp>, freebsd-alpha@FreeBSD.ORG Subject: Re: bus_dmamap_load Message-ID: <Pine.LNX.4.21.0101041642370.16662-100000@zeppo.feral.com> In-Reply-To: <Pine.LNX.4.10.10101042102170.1781-100000@linux.local>
index | next in thread | previous in thread | raw e-mail
On Thu, 4 Jan 2001, [ISO-8859-1] Gérard Roudier wrote: > > > On Thu, 4 Jan 2001, Matthew Jacob wrote: > > > The trick now is to figure out who is passing a bogus value > > to bus_dmamap_load. The value of buf_len (0xfaae8000) looks > > suspicious. > > > > Since I hve essentially the same h/w (except for the symbios card) in a PC164 > > that runs 4.2 just fine, I would suspect the sym driver. But needs to happen > > is some better debugging for this. I take it that you aren't really running on > > this h/w yet (i.e, you haven't been able to install)? > > Btw, you missed the `de' driver that also performs bus_dmamap_load() on > mbuf's as a possible candidate. That's why I said 'possibly'.... And because pretty much the sole difference between his PC164 and mine is the Symbios card..... > > Would be interesting to shut the `de' board and to give a try with a > different network board long enough to see if it makes difference. No, no, no, since he's actually running with this, the smart thing to do is to put a panic to DDB to get a traceback, i.e.: options DDB and change the printf in alpha/busdma_machdep.c to a panic. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the messagehome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.21.0101041642370.16662-100000>