Date: Fri, 22 Jun 2007 13:00:12 +0900 From: Pyun YongHyeon <pyunyh@gmail.com> To: Garance A Drosihn <drosih@rpi.edu> Cc: freebsd-ppc@FreeBSD.org Subject: Re: panic due to 'ds_len > SBP_SEG_MAX' Message-ID: <20070622040012.GC25611@cdnetworks.co.kr> In-Reply-To: <p06240802c29f6670bba9@[128.113.24.47]> References: <p06240801c29dee92a2d7@[128.113.24.47]> <20070620004439.GC13241@cdnetworks.co.kr> <p06240802c29f6670bba9@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jun 20, 2007 at 07:20:52PM -0400, Garance A Drosihn wrote: > At 9:44 AM +0900 6/20/07, Pyun YongHyeon wrote: > >On Tue, Jun 19, 2007 at 04:51:20PM -0400, Garance A Drosihn wrote: > > > > > > This past Sunday I updated my 7.x source tree and compiled everything. > > > When I tried to boot up with the new kernel, I hit a panic: > > > > > > trying to mount root from ufs:/dev/da0s9 > > > panic: ds_len > SBP_SEG_MAX, fix busdma code > > > KDB: enter: panic > > > > > > At the time I was already running late for something else, so I > > > just rebooted into the old kernel and went back to running that. > > > > > > Has anyone else seen this? > > >I have no experience with sbp(4) but I guess _bus_dmamap_loader_buffer > >didn't honor specified DMA tag. > >How about attached one? > > I did a quick test of this change, but I still get the panic. For a record, fix committed to HEAD.(busdma_machdep.c, rev. 1.28) -- Regards, Pyun YongHyeon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070622040012.GC25611>