Max Ignatenko wrote:
Hi,
Sorry for a late reply!
First of all, thank you for taking time to investigate and even providing a
fix (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230993) ! Your patch
makes perfect sense to me and modifying userspace memory from kernel is
indeed something I did
Hi,
Sorry for a late reply!
First of all, thank you for taking time to investigate and even providing a
fix (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230993) ! Your patch
makes perfect sense to me and modifying userspace memory from kernel is
indeed something I didn't consider to be a pr
On 8/25/18 11:51 PM, Theron wrote:
A recent change in CURRENT has sysutils/acpi_call reliably cause a
kernel panic
The problem is with the port itself, not with CURRENT. A bug is filed
accordingly.
___
freebsd-current@freebsd.org mailing list
https
On Sat, Aug 25, 2018 at 11:51:21PM -0400, Theron wrote:
>
> A recent change in CURRENT has sysutils/acpi_call reliably cause a
> kernel panic when run on a Dell XPS laptop system. I bisected this to
> r336876: Use SMAP on amd64. I would have thought that this is a simple
> compatibility probl
