Dear Forumers,
I have been battling all day with a problem I can find very little information about and I was hoping you could give me a hand. I'm putting this issues in this forum only because I only did a fresh new install today and have been trying to resolve the issue basically the better part of the day.
My machine(workstation):
CPU: Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz
MB: ASUS PRIME Z270-P
RAM: 16GB(2x8GB Kingston Hyperx)(not sure which ones, can check if necessary)
HDD: 1TB Samsung 850 Evo
Graphics Card: Intel built-in(with SCFB driver).
I did a fresh FreeBSD(11 stable) installation this morning from USB bootonly image. All the software I installed I installed from ports with the exception of
eventually(before I brought up the X server) I did a
I started debugging and the only way I could test whether
The output of
I am new to
and used
This is the ouput of it once I run sysctl -a:
And this is repeating restlessly...
Also,
And the part I don't have is where
Now the reason I am posting to the forums is because the only information about this issue I can find has to do with some bug reports mainly on laptops and also very very old(with the exception of one from August).
https://lists.freebsd.org/pipermail/freebsd-usb/2016-August/014377.html
https://lists.freebsd.org/pipermail/freebsd-acpi/2007-September/004015.html
Now I am sure I am missing something, but this is as far as I can go. Do let me know if you would like more information.
Thank you in advance!
I have been battling all day with a problem I can find very little information about and I was hoping you could give me a hand. I'm putting this issues in this forum only because I only did a fresh new install today and have been trying to resolve the issue basically the better part of the day.
My machine(workstation):
CPU: Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz
MB: ASUS PRIME Z270-P
RAM: 16GB(2x8GB Kingston Hyperx)(not sure which ones, can check if necessary)
HDD: 1TB Samsung 850 Evo
Graphics Card: Intel built-in(with SCFB driver).
I did a fresh FreeBSD(11 stable) installation this morning from USB bootonly image. All the software I installed I installed from ports with the exception of
ffmpeg
(as it wouldn't install from ports).eventually(before I brought up the X server) I did a
sysctl -a | grep something
and the shell just froze. I could see things I write, Ctrl+C or Ctrl+Z but I couldn't kill the process. I tried to do kill -9
from a different shell but no luck there.I started debugging and the only way I could test whether
sysctl -a
works is by putting it inside tmux
. That way round I could kill the pane if it froze and run it again.The output of
sysctl -a
seemed normal to the part it just stops working(printing out hundreds of values).I am new to
dtrace
but decided to debug with it. I followed the handbook manual, enabled dtrace
: kldload dtraceall
and used
/usr/share/dtrace/blocking sysctl
to monitor what's happening with sysctl -a
This is the ouput of it once I run sysctl -a:
Code:
sysctl(874) is blocking... kernel`_sleep+0x1fd kernel`AcpiOsAcquireMutex+0xe8 kernel`AcpiUtAcquireMutex+0x3a kernel`AcpiExEnterInterpreter+0xb kernel`AcpiNsEvaluate+0x1e8 kernel`AcpiUtEvaluateObject+0x4d kernel`AcpiUtExecute_HID+0x27 kernel`AcpiGetObjectInfo+0xd9 kernel`acpi_child_pnpinfo_str_method+0x24 kernel`device_sysctl_handler+0x11b kernel`sysctl_root_handler_locked+0xbf kernel`sysctl_root+0x1f6 kernel`userland_sysctl+0x1c4 kernel`sys___sysctl+0x74 kernel`amd64_syscall+0x4ce kernel`0xffffffff80f8442b libc.so.7`___sysctl+0xa sysctl`0x402b7d sysctl`0x401c61 sysctl`0x401aff sysctl`0x40159f ld-elf.so.1`0x800626000
And this is repeating restlessly...
Also,
dmesg
started piping out this:Code:
ACPI Exception: AE_ERROR, Thread 100635 could not acquire Mutex [0x0] (20160527/utmutex-345) ACPI Error: Could not acquire AML Interpreter mutex (20160527/exutils-104) ACPI Error: Mutex [0x0] is not acquired, cannot release (20160527/utmutex-386) ACPI Error: Could not release AML Interpreter mutex (20160527/exutils-147) ACPI Exception: AE_ERROR, Thread 100635 could not acquire Mutex [0x0] (20160527/utmutex-345) ACPI Error: Could not acquire AML Interpreter mutex (20160527/exutils-104) ACPI Error: Mutex [0x0] is not acquired, cannot release (20160527/utmutex-386) ACPI Error: Could not release AML Interpreter mutex (20160527/exutils-147) ACPI Exception: AE_ERROR, Thread 100616 could not acquire Mutex [0x0] (20160527/utmutex-345) ACPI Error: Could not acquire AML Interpreter mutex (20160527/exutils-104) ACPI Error: Mutex [0x0] is not acquired, cannot release (20160527/utmutex-386) ACPI Error: Could not release AML Interpreter mutex (20160527/exutils-147) ACPI Exception: AE_ERROR, Thread 100616 could not acquire Mutex [0x0] (20160527/utmutex-345) ACPI Error: Could not acquire AML Interpreter mutex (20160527/exutils-104) ACPI Error: Mutex [0x0] is not acquired, cannot release (20160527/utmutex-386) ACPI Error: Could not release AML Interpreter mutex (20160527/exutils-147)
And the part I don't have is where
sysctl -a
cuts off(I'm going to post it first thing in the morning) but the last row had to do with acpi too.Now the reason I am posting to the forums is because the only information about this issue I can find has to do with some bug reports mainly on laptops and also very very old(with the exception of one from August).
https://lists.freebsd.org/pipermail/freebsd-usb/2016-August/014377.html
https://lists.freebsd.org/pipermail/freebsd-acpi/2007-September/004015.html
Now I am sure I am missing something, but this is as far as I can go. Do let me know if you would like more information.
Thank you in advance!