-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Thinkpad X1 Carbon 3rd Gen, hangs without starting the debugger. #164
Comments
Is this a regression? Are you able to ssh into the machine when the hang occurs? |
I don't think it's a regression. I've had this issue since I've switched to FreeBSD 3 months ago. Couldn't pinpoint the culprit but now I'm relatively sure. Haven't tried to ssh into the machine, I'll try to have another machine in reach when this happens again. |
Just in case, is there information I should collect once this happens again? |
If you're able, it would be useful to get output of "sudo procstat -kka" and "dmesg". As a more extreme measure, you can try and get a kernel dump by panicking the system from the ssh session "sudo sysctl debug.kdb.panic=1", assuming you have configured a dump device (check with "dumpon -l"). |
It happened again but the machine was not reachable via |
Happened again at home. No connection via |
Here is some dmesg output from my system (not crashed). Are these warnings normal?
|
Have you tried setting the following in /boot/loader.conf? These should help increase the likely hood of capturing a core for analysis: dev.drm.drm_skip_ddb=1 |
Haven't tried that yet. Put the setting in there, let's see what happens. |
I know that this question is not directly related to the issue but I'm having issues setting up a dumpdev with an encrypted swap device on my system. dumpdev is set to AUTO and I've tried using the "late" option in fstab for the swap partition. It always complains about not finding a suitable dump device. Am I missing something? |
I've turned off geli for the time being and the crash happened shortly after that. Sadly the kernel didn't dump any information regarding the crash. |
I've updated this weekend and crashes now seem to happen more frequently, currently on a daily basis. Not sure if this is related to the update or me just triggering whatever causes the crash more often. |
Hi,
I've been having this issue for a month now and I'm pretty sure that it's related to KMS.
My machine basically just hangs, no panic or whatsoever (hence I don't have any useful
information yet).
I've tried running X using
scfb
for about 3 weeks and had now issues (apart from being unable to adjust screen brightness and lots of power consumption). Switched on KMS againthis weekend and today (a couple of days later) it froze again. I'm really not sure what to report here since it everything just freezes without yielding any information. I also have
no way of reproducing the issue, it just happens around once or twice a week. So I thought
I'd open this issue to collect some data.
Kind regards,
raichoo
The text was updated successfully, but these errors were encountered: