-
-
Notifications
You must be signed in to change notification settings - Fork 46
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
kernel NULL pointer dereference in xenbus_thread, Linux 6.1.57 on openQA #8638
Comments
Reported upstream at https://lore.kernel.org/xen-devel/ZO0WrR5J0xuwDIxW@mail-itl/ |
Specific crash message:
|
happens on 6.1.75 too crash message
|
I've begun to see instability in my qubes with random crashing. Probably started after I implemented this fix to my Xen configuration. Only affecting Whonix based qubes that I've noticed. Dom0 kernel is 6.6.29-1 Here is the log:
|
Another backtrace, this time from 6.6.25 (internal ref: a3): Details
|
@scallyob how often do you get it? can you narrow down when (what operations, applications etc) it is most likely to happen? I get it about once a month, and it's too infrequent for any kind of debugging... |
@marmarek Last two were 4 days apart. Different qubes. Those were the only 2 I captured logs for. Both were whonix gateways. Others have all been Whonix gateways and 1 time it was a Whonix workstation. So the gateways are just running in the background, I'm not actively doing anything with them when they crash, but they usually have services actively running through them. |
Just got another one. Was main sys-whonix. Was using Tor Browser in anon-whonix and changing settings with qvm-prefs on another whonix workstation when I saw it go down. Same errors in the logs. Seems like every 4 days now, which is a significant problem for me. One thing I'm trying is I've had "Include in memory balancing checked" on qubes in the past. I turned it off for others that had crashed, but was still checked for sys-whonix. Will report back on whether there's any patterns there. |
First crash in 2 weeks
I increased to 2GB RAM and 2 VCPUS. |
Observation
openQA test in scenario qubesos-4.1-release-upgrade-x86_64-install_default@64bit fails in
release_upgrade
kernel NULL pointer dereference, stack trace
Test suite description
The test is about release upgrade R4.1->R4.2, but the crash looks unrelated to the specific workload.
Reproducible
Fails since (at least) Build 2023102123-4.1 (current job)
Similar crash was observed also on a real hardware in a domU on an older kernel: 6.1.43.
Expected result
Last good: 2023101101-4.1 (or more recent)
Further details
Always latest result in this scenario: latest
The text was updated successfully, but these errors were encountered: