Date: Thu, 13 Sep 2018 20:25:35 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 230993] sysutils/acpi_call: Kernel panic since CURRENT r336876 (Use SMAP on amd64) Message-ID: <bug-230993-7788-zYqL7Dmvd2@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-230993-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-230993-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D230993 Jean-S=C3=A9bastien P=C3=A9dron <dumbbell@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #196667|0 |1 is obsolete| | CC| |dumbbell@FreeBSD.org --- Comment #2 from Jean-S=C3=A9bastien P=C3=A9dron <dumbbell@FreeBSD.org> = --- Created attachment 197075 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D197075&action= =3Dedit Patch to fix accesses to userland pointers in kernel module I also hit a kernel panic on a recent laptop (Skylake) with acpi_call, but = not on an older one (Haswell) which probably confirms the SMAP cause. I tried your patch and it was not enough to get rid of the panic because, i= n my case, the kernel fails to read the `path` located in userland. I had to mod= ify it further to use copyin(9) to get the `path`. Here is a new patch (to apply to the port directly) which fixes the problem= for me. I can turn off the discrete GPU of my laptop using acpi_call. The new p= atch includes your initial, that's why I marked yours as obsolete. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-230993-7788-zYqL7Dmvd2>