Date: Wed, 12 Feb 2020 12:30:38 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 237463] aacraid(4) doesn't work on powerpc64 Message-ID: <bug-237463-227-9HWvoMqeUv@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-237463-227@https.bugs.freebsd.org/bugzilla/> References: <bug-237463-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237463 Leandro Lupori <luporl@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |In Progress --- Comment #3 from Leandro Lupori <luporl@FreeBSD.org> --- Status update: After converting all FIB structures needed by aacraid.c and aacraid_cam.c to big-endian, when needed, the driver started going further, but there were still some issues: - sense data was causing a buffer overflow, because of wrong max sense len logic - after several read/write operations, the kernel was panic'ing in bus_dmamap_sync(). This was due to a missing aac_unmap_command() in the SYNC path. (I'm currently holding the patches until I have a minimal working version of aacraid driver). Now I'm able to perform several reads and writes, sometimes even complete a FreeBSD install from ISO to disk, but there is still (at least) one issue remaining. After some time of disk activity, write commands begin to fail with Selection Timeout errors. They usually fail 3 times in a row and the periph is then destroyed. After some debugging, I've noticed the timeouts start to occur right after receiving an AIF interrupt. For some reason I don't know yet, the response to an AifRequest in SYNC mode comes with no AIF information, so I don't know what the adapter is trying to tell me. Any help or debugging tip is appreciated! -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-237463-227-9HWvoMqeUv>