-
-
Notifications
You must be signed in to change notification settings - Fork 14.1k
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
Nouveau segfault when launching X11 Display Manager #170856
Comments
Here's dmesg output: https://gist.github.com/vlinkz/c15793a41d18843ab6a826d6a7458c53.
|
I'm having a simliar issue, except I don't have NVIDIA. I am using a Thinkpad E580 with an i7-8550U, AMD ATI Radeon RX 550 (dedicated gpu), and an Intel UHD Graphics 620 (intergrated gpu). I've had many issues with this AMD gpu, so I just assumed it was something to do with that and didn't open an issue here. However, there is clearly something else happening here. I am currently bisecting nixpkgs to find which commit is causing the breakage, and am up to 91 commits. I'll post the commit here once I find it. Bisect log so far (skipping commits if a system dependency cannot build)
|
Maybe #169443 also related? Although unsure why |
It's quite weird. I'm not sure if #169443 is related as my X.log backtrace is basically the exact same as yours:
Full X.log
I have now bisected up to these commits, and I see a few xorg updates that are likely the issue: Suspected commits (`git bisect view --oneline`)
|
In that case, it's probably an issue with the Xorg modesetting driver, given that the same issues appear on both amdgpu and nouveau drivers. Before I was specifically looking for issues with nouveau, but good to know that that's not the complete issue |
If I had to guess I'd think the culprit is |
It is certainly some change within #153994. Only once this PR is merged does X fail to start. Alright, let me know how you go. |
I can reproduce this issue on my XPS 9575, which has an intel/AMD combination of GPUs. @vcunat @dasj19 Would it be wise to revert #153994 until the problem is solved? It leaves NixOS in an unbootable state for multiple people. Stack trace as follows:
My journal also prints a somewhat longer stack trace: Longer stack trace
Some X related config settings in my configuration: {
services.xserver = {
enable = true;
xkbOptions = "eurosign:e";
videoDrivers = [ "amdgpu" "intel" "vesa" ];
wacom.enable = true;
};
hardware = {
opengl = {
driSupport32Bit = true;
extraPackages32 = [pkgs.pkgsi686Linux.libva];
};
};
} |
I have tested this on my machine and yes, X starts just fine after reverting only 3312352. |
Took forever to build, but reverting 3312352 fixed the issue for me as well on the latest unstable. Probably should revert this before 22.05 |
I'm a bit afraid that reverting to that old xorg-server branch will have other negative consequences, especially in longer term. Can you try this patch instead? #171113 |
Patch did not seem to work for me. Same issue with identical logs. I'll try rebuilding it again just in case though Edit: Still doesn't seem to work |
X still segfaults for me with the patch applied too. I also have identical logs. |
I think I'm getting the same issue on my Dell XPS 9510. What's our favourite work-around at the moment? |
I'd hope that PR #174140 |
I'm having this issue on Dell XPS 15 9510. I guess #174140 hasn't landed into release-22.05 yet? |
I hasn't even landed in unstable/master, though I expect that to happen within days. |
Is #174140 a temporary fix? Should this stay open? |
I woud argue that the best issue to track this, is the original xorg/xserver issue: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1304 Once that is fixed, and possibly any other bugs that render it inoperable, the package can be updated again in nixpkgs. |
This issue has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/gui-not-starting-after-upgrade-to-22-05/19534/6 |
Describe the bug
I have a Dell XPS 9550, which has both an Intel I7 and Nvidia 950M. When I do a fresh NixOS install (using NixOS-unstable), by default lightdm and sddm both cause a segmentation fault that seems to be related to nouveau. Disabling the nouveau driver with
modprobe -r nouveau
allows me to restart the display manager and launch a desktop environment. This happend with both SDDM and KDE Plasma, and Light with Pantheon. Log: https://gist.github.com/vlinkz/62e48c55793402d98746b92ad50ccea8Steps To Reproduce
Steps to reproduce the behavior:
Expected behavior
Display manager starting
Additional context
"intel"
toxserver.videoDrivers
also works, but seemed to be disabled by default in [RFC] NixOS Xorg service: should we removeintel
from defaultvideoDrivers
#55520 and nixos/xserver: drop intel from videoDrivers #55583boot.kernelParams = [ "nouveau.modeset=0" ]
makes it workNotify maintainers
Not sure who
Metadata
22.05pre372961.e10da1c7f54 - Not working
21.11.337266.feea25c5865 - Working
The text was updated successfully, but these errors were encountered: