Created attachment 145592 [details] xorg.0.log with xorg backtrace Geforce 2 since debian 10 crash when starting mate-session (but not with xfce4-session or showing gdm3 or lightdm). I have also downgrade xorg-server-core to debian 9 and I get the same crash. All was working with debian 9 (and 4.9 kernel). I have tried 4.19 and 4.9 kernel : both crash. If I launch mate-session from command line in a xfce4-session, mate-session works. The backtrace of Xorg.0.log is the same as https://termbin.com/7avc I put it in attachment since I have not the non working computer with me. Later I will give a working Xorg.0.log (with xfce4) and the non working (with mate).
You have a bigger problem ... your GeForce2 is reporting as a Riva TNT2! That's a weird stack trace -- looks like it got corrupted. The "nouveau" address doesn't map to a function at all, and the present_register_complete_notify frames appear questionable to me. How much debugging are you able to do? Do you have a second computer and know how to work gdb?
Thanks for your answer. Sorry, I give you this "pastebin" since I'm away from my computer. This log has a Riva TNT2, but mine a Geforce 2. But they gives the "same" backtrace. I will give you the two log files (mate-session and xfce4-session) from my computer in few days. gdb is difficult for me, I will need help. I'm not sure if I need two computers since I can still use the computer in console mode after the crash. The crash does not freeze the computer : with lightdm, I get the infinite connect loop.
Le 30/09/2019 a 12:06:01 +0000, bugzilla-daemon@freedesktop.org a ecrit : > https://bugs.freedesktop.org/show_bug.cgi?id=111868 > > --- Comment #1 from Ilia Mirkin <imirkin@alum.mit.edu> --- > You have a bigger problem ... your GeForce2 is reporting as a Riva TNT2! Sorry, I give you this "pastebin" since I'm away from my computer. This log has a Riva TNT2, but mine a Geforce 2. But they gives the "same" backtrace. > > That's a weird stack trace -- looks like it got corrupted. The "nouveau" > address doesn't map to a function at all, and the > present_register_complete_notify frames appear questionable to me. So I will give you the two log file from my computer in few days. > > How much debugging are you able to do? Do you have a second computer and know > how to work gdb? > gdb is difficult for me, I will need help. I'm not sure I need two computer since I can still use the computer in console mode after the crash. The crash does not freeze the computer : with lightdm, I get the infinite connect loop. Thanks, alain prignet
OK, alternatively do you have a fool-proof sequence of steps to reproduce this? You originally made it sound like mate-session was the thing, but but then in later comments you say that it's actually fine. Like let's say I run xinit and then run mate-session from within the terminal -- is that enough? (I'd like to avoid dealing with gdm3 as much as possible.)
Yes I have a fool-proof sequence to reproduce it, even not using gdm3 or lightdm. I can reproduce it using "startx" and an .xinitrc containing only "exec mate-session". Since the computer does not freeze, I can reproducing at demand. (The bug is not show when having in .xinitrc "exec xfce4-session", or when using gdm3 or lightdm with xfce, even if launching mate-session during the xfce4 session)
Great, thanks. I'll work on reproducing locally. I think we spoke on IRC a while back -- sorry I didn't actually get around to investigating -- you said that it only reproduced consistently with like TNT2, not with the later GPUs like NV34 (which I happen to have plugged in, which is why I'm asking).
I have a very old Geforce 2. But according to the file I found on termbin, it is the same with a Riva TNT2. This is the only nvidia card I have. My other are Intel.
Created attachment 145664 [details] startx with .xinitrc "exec mate-session". it fails.
Created attachment 145665 [details] startx with .xinitrc "exec xfce4-session". it works.
Above the 2 "real" log files. In console mode, (real user, not root), I launch startx with .xinitrc as describe.
This patch may help: https://patchwork.freedesktop.org/patch/335616/ I believe that primarily GPUs with 32MB of VRAM (or less) would be affected. However it may also have a rarer effect on larger-VRAM devices.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues/508.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.