HI all,
My system started to fail, and I did not change anything, no dist-upgrades previous to fail.
It takes like 10 minutes to start the desktop and the only thing I can see is some fault in nouveau.
I am thinking of swtching to nvidia.
Also, i lost my automatic ability to log into the debian-next channel which was set to log in upon starting Konversation.
Also, I had sound problems but after uninstalling timidity-daemon they disappeared, to my chagrin the system started silently at random after a few days, and I could never figure out why, because a reboot would fix that.
My most pressing issue is the time lag for this system to start the KDE desktop, tried re-installing kde full but that did not work either.
Another thing I tried is a dist-upgrade to fix the issue, same old, but that was after the issue started.
Please what steps do you suggest to diagnose and troubleshoot the nouveau issue?
Looking forward to hear back from you guys.
Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
Possible segfault in nouveau
- sunrat
- Administrator
- Posts: 6412
- Joined: 2006-08-29 09:12
- Location: Melbourne, Australia
- Has thanked: 116 times
- Been thanked: 461 times
Re: Possible segfault in nouveau
Doesn't sound like it's definitely a graphics issue. Any errors showing in journalctl?
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ” Remember to BACKUP!
Those who have lost data
...and those who have not lost data YET ” Remember to BACKUP!
- None1975
- df -h | participant
- Posts: 1388
- Joined: 2015-11-29 18:23
- Location: Russia, Kaliningrad
- Has thanked: 45 times
- Been thanked: 65 times
Re: Possible segfault in nouveau
Hello. You are on testing? Post your sources list here.ckosloff wrote:Looking forward to hear back from you guys.
OS: Debian 12.4 Bookworm / DE: Enlightenment
Debian Wiki | DontBreakDebian, My config files on github
Debian Wiki | DontBreakDebian, My config files on github
Re: Possible segfault in nouveau
#None1975 wrote:Hello. You are on testing? Post your sources list here.ckosloff wrote:Looking forward to hear back from you guys.
Code: Select all
#deb cdrom:[Debian GNU/Linux buster-DI-alpha1 _Buster_ - Official Snapshot amd64 NETINST 20170829-10:02]/ buster main
deb http://ftp.ca.debian.org/debian/ testing main non-free contrib
# deb-src http://ftp.ca.debian.org/debian/ buster main non-free contrib
deb http://ftp.ca.debian.org/debian-security testing/updates main contrib non-free
# deb-src http://ftp.ca.debian.org/debian-security buster/updates main contrib non-free[/code]
This morning I got another ominous error, the infamous: x-z compressed data is corrupt - system halted
Re: Possible segfault in nouveau
I googled the error and somebody in Linuxquestions.org had the same $hize, BIOS error memory set too high speed, I will go into BIOS settings and load fail safe defaults, post results here.
After powering off, system starts with a time lag, but it does start, meaning that compressed data is OK, just not read properly.
The baby (me) wanted to use his toy at high speed.
After powering off, system starts with a time lag, but it does start, meaning that compressed data is OK, just not read properly.
The baby (me) wanted to use his toy at high speed.
Re: Possible segfault in nouveau
Setting the BIOS to optimized defaults, did not solve problem.
But I think I found what is causing the segfault: I just stumbled upon a bug report that has already been processed, apparently package libcap-ng0 is causing segfault at boot, precisely my problem.
I cannot just remove that package because it will remove a ton of other packages, including apt, thus rendering my system unusable, I wouldn't be able to reinstall anything if apt is missing.
I might decide to nuke the bastard anyway and reinstall apt from a rescue disk, I installed my system from a netinst CD, which has the bare minimum, dunno if I will be able to install apt from it.
Any ideas?
But I think I found what is causing the segfault: I just stumbled upon a bug report that has already been processed, apparently package libcap-ng0 is causing segfault at boot, precisely my problem.
I cannot just remove that package because it will remove a ton of other packages, including apt, thus rendering my system unusable, I wouldn't be able to reinstall anything if apt is missing.
I might decide to nuke the bastard anyway and reinstall apt from a rescue disk, I installed my system from a netinst CD, which has the bare minimum, dunno if I will be able to install apt from it.
Any ideas?
- sunrat
- Administrator
- Posts: 6412
- Joined: 2006-08-29 09:12
- Location: Melbourne, Australia
- Has thanked: 116 times
- Been thanked: 461 times
Re: Possible segfault in nouveau
I found a bug report that refers to the testing/unstable version causing segfault with apache/httpd.
You didn't say, but are you running a server on testing/sid? That's pretty brave. As usual, breakages are expected and it will probably be fixed in the near furture.
Bug - https://bugs.debian.org/cgi-bin/bugrepo ... bug=904808
You didn't say, but are you running a server on testing/sid? That's pretty brave. As usual, breakages are expected and it will probably be fixed in the near furture.
Bug - https://bugs.debian.org/cgi-bin/bugrepo ... bug=904808
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ” Remember to BACKUP!
Those who have lost data
...and those who have not lost data YET ” Remember to BACKUP!