Date: Tue, 23 Sep 2008 00:18:20 +0200 From: "Marco Trillo" <marcotrillo@gmail.com> To: "Maxim Sobolev" <sobomax@freebsd.org> Cc: freebsd-ppc@freebsd.org Subject: Re: Call for testers: Apple ATA DMA Message-ID: <b9c23c9f0809221518t343660b5k40877e132bba98ed@mail.gmail.com> In-Reply-To: <48D8186F.4020308@FreeBSD.org> References: <48D389EE.9000207@FreeBSD.org> <48D3AD50.8070505@freebsd.org> <48D69679.1080701@freebsd.org> <48D7F437.1040603@FreeBSD.org> <48D80DDD.2080309@freebsd.org> <48D8186F.4020308@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On Tue, Sep 23, 2008 at 12:13 AM, Maxim Sobolev <sobomax@freebsd.org> wrote: >>> I was able to "fix" the problem by making ata_macio probe function >>> returning ENXIO always. My guess is that ATA chipset on this machine is >>> somehow accessible through two different buses (macio and pci), which >>> creates some weird conflicts, but I might be wrong. Hopefully you will have >>> better idea, I can provide any assistance needed to fix the issue properly. >>> See 342.png screenshot. Dmesg with hacked ata_macio is as follows: >> >> Interesting -- it looks like all the interrupts are arriving on the second >> (DBDMA) IRQ. Could you try setting USE_DBDMA_IRQ to 0 in ata_macio.c and >> re-enabling ata_macio? There is something funny with how these interrupts >> are triggered currently and they can set off interrupt storms like this. > > I've done that, but it has not changed anything. I still see interrupt storm > on irq 12. Try deleting the USE_DBDMA_IRQ definition line from ata_macio.c instead of just defining it to 0, so the "ifdef USE_DBDMA_IRQ" stuff is not compiled. Hope that helps, Marco.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b9c23c9f0809221518t343660b5k40877e132bba98ed>