Date: Fri, 17 Jan 2003 18:33:03 +0100 From: Thomas Moestl <tmm@freebsd.org> To: Harti Brandt <brandt@fokus.gmd.de> Cc: sparc@freebsd.org Subject: Re: Problem with iommu_dvmamap_create Message-ID: <20030117173303.GD304@crow.dom2ip.de> In-Reply-To: <20030117181111.R45050@beagle.fokus.gmd.de> References: <20030117151958.U715@beagle.fokus.gmd.de> <20030117160857.GB304@crow.dom2ip.de> <20030117171317.F44530@beagle.fokus.gmd.de> <20030117171111.GC304@crow.dom2ip.de> <20030117181111.R45050@beagle.fokus.gmd.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 2003/01/17 at 18:19:59 +0100, Harti Brandt wrote: > On Fri, 17 Jan 2003, Thomas Moestl wrote: > TM>BUS_DMAMAP_NSEGS (and BUS_SPACE_MAXSIZE) is pretty arbitrary, the only > TM>thing to limit is the stack space used by the segment array. In the > TM>current setting, 272 bytes are used at most, which is less than 1.5 > TM>minimal function frames. Values such as 64 should still be OK. > > Would it be possible if you change it just there? Yes, I'll do that with the next update. > I have an ATA controller from which I boot, a hme card and an adaptec > 29160, but I don't use the SCSI disk at the moment. Hmmm, none of these has boundary requirements of a form that were broken previously. The lowaddr breakage also affects none of them (it was quite harmless for the class of the PCI devices that is currently supported). > What I did to trigger the error was: > > 1) compile the code with the '3 * HE_....' changed to 1. > 2) install, kldload, ifconfig up -> ok > 3) compile the original code > 3) kldunload, install, kldload, ifconfig up -> baaaah > > 'baaaah' means, that a lot of strange things happen: the driver gets a lot > of interrupts, but the interrupt status words (these are written per DMA) > are invalid. when kldunloading sometimes I get a repeated loop of 'fast > data mmu ... miss' and ddb prompts. After booting (I need to switch the > machine off to do this!) the nvram checksum is usually bad and the machine > ofw status is reset. I tried to find the problem for 3 days now.... With > your patch applied things seem better, but I still fail to see why :-) So do I. Can you maybe put the full code of the driver in question somewhere for download? Thanks, - Thomas -- Thomas Moestl <tmoestl@gmx.net> http://www.tu-bs.de/~y0015675/ <tmm@FreeBSD.org> http://people.FreeBSD.org/~tmm/ PGP fingerprint: 1C97 A604 2BD0 E492 51D0 9C0F 1FE6 4F1D 419C 776C To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-sparc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030117173303.GD304>