Bug#1033862: nouveau: watchdog: BUG: soft lockup - CPU#0 stuck for 548s! [kscreenlocker_g:19260]
Package: src:linux Version: 6.1.20-1 Severity: critical File: nouveau Justification: breaks the whole system X-Debbugs-Cc: af...@comcast.net When the above message occurs, the system becomes totally unresponsive and the only way to recover is a hard power-off via the power button held for about 5 seconds. Upon boot, the sddm login screen appears but at 1024x768, which is much less than the monitor is capable of: 1920x1200. xrandr Screen 0: minimum 16 x 16, current 1024 x 768, maximum 32767 x 32767 XWAYLAND0 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1024x768 59.92*+ 800x600 59.86 640x480 59.38 320x240 59.52 720x480 59.71 640x400 59.95 320x200 58.96 1024x576 59.90 864x486 59.92 720x400 59.55 640x350 59.77 After login sometimes the screen goes blank (but the backlight remains on). Hard power off required. Sometimes the gear wheel stops turning and the system freezes. Hard power off required. I have tried to install the nvidia proprietary driver 304 (NVIDIA-Linux-x86_64-304.117.run) which is what this old chip needs but it fails to install. No matter what I do the nouveau driver is in use and cannot be removed. If it were possible for nouveau and/or X/Wayland to access the whole set of resolutions of the system without hard freezes, I'd be happy. Any tricks? Any specific things I could try to figure out the issue? Obviously, in this particular boot the hard freeze did not happen. These lines seem to be relevant (from the logs below): [ 47.892652] nouveau :00:0 d.0: bus: MMIO write of 00340001 FAULT at 00b000 [ 64.113759] nouveau :00:0d.0: bus: MMIO write of 00640001 FAULT at 00b010 [ 64.114792] nouveau :00:0d.0: bus: MMIO write of 00310001 FAULT at 00b020 [ 69.614326] nouveau :00:0d.0: bus: MMIO write of FAULT at 00b020 [ 69.614542] nouveau :00:0d.0: bus: MMIO write of 00640001 FAULT at 00b010 [ 69.615432] nouveau :00:0d.0: bus: MMIO write of 00310001 FAULT at 00b020 [ 70.336843] nouveau :00:0d.0: bus: MMIO write of FAULT at 00b020 [ 70.337057] nouveau :00:0d.0: bus: MMIO write of 00640001 FAULT at 00b010 [ 70.337684] nouveau :00:0d.0: bus: MMIO write of 00660001 FAULT at 00b020 [ 70.357387] nouveau :00:0d.0: bus: MMIO write of FAULT at 00b010 [ 89.666120] nouveau :00:0d.0: bus: MMIO write of 00ca0001 FAULT at 00b010 [ 97.330127] nouveau :00:0d.0: bus: MMIO write of FAULT at 00b010 [ 104.590842] traps: light-locker[4745] trap int3 ip:7f59b65be7d7 sp:7fff472f8690 error:0 in libglib-2.0.so.0.7400.6[7f59b658+8d000] -- Package-specific info: ** Version: Linux version 6.1.0-7-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.20-1 (2023-03-19) ** Command line: BOOT_IMAGE=/boot/vmlinuz-6.1.0-7-amd64 root=UUID=28bd15dd-cd17-45c8-93e0-65decc995980 ro quiet ** Not tainted ** Kernel log: [6.707012] systemd[1]: Starting systemd-journald.service - Journal Service... [6.760881] systemd[1]: Starting systemd-modules-load.service - Load Kernel Modules... [6.762291] systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems... [6.763752] systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices... [6.766133] systemd[1]: Finished kmod-static-nodes.service - Create List of Static Device Nodes. [6.766733] systemd[1]: modprobe@configfs.service: Deactivated successfully. [6.766949] systemd[1]: Finished modprobe@configfs.service - Load Kernel Module configfs. [6.767339] systemd[1]: modprobe@drm.service: Deactivated successfully. [6.767583] systemd[1]: Finished modprobe@drm.service - Load Kernel Module drm. [6.769231] systemd[1]: Mounting sys-kernel-config.mount - Kernel Configuration File System... [6.778991] systemd[1]: modprobe@efi_pstore.service: Deactivated successfully. [6.779202] systemd[1]: Finished modprobe@efi_pstore.service - Load Kernel Module efi_pstore. [6.791834] systemd[1]: Mounted dev-mqueue.mount - POSIX Message Queue File System. [6.792129] systemd[1]: Mounted sys-kernel-debug.mount - Kernel Debug File System. [6.792350] systemd[1]: Mounted sys-kernel-tracing.mount - Kernel Trace File System. [6.792608] systemd[1]: Mounted sys-kernel-config.mount - Kernel Configuration File System. [6.829931] systemd[1]: Mounted dev-hugepages.mount - Huge Pages File System. [6.853427] loop: module loaded [6.854583] systemd[1]: modprobe@loop.service: Deactivated successfully. [6.854794] systemd[1]: Finished modprobe@loop.service - Load Kernel Module loop. [6.857921] fuse: init (API version 7.37) [6.858998] systemd[1]: modprobe@fuse.service: Deactivated successfully. [6.859199] systemd[1]:
Bug#859310: xserver-xorg-video-nvidia-legacy-304xx: Failed to load module nvidia (module does not exist, 0) No drivers available.
Package: xserver-xorg-video-nvidia-legacy-304xx Version: 304.135-2 Severity: grave Tags: patch Justification: renders package unusable Dear Maintainer, * What led up to the situation? All the components of the nvidia-legacy-304xx drivers (kernel and xorg) were working fine in jessie. After an upgrade to stretch, the nouveau driver was unreliable (video artifacts, lock-ups) as it had been before in jessie. I had to manually remove packages, blacklist nouveau, install and compile the kernel driver, etc... After all was done X wouldn't start. These are the relevant lines in Xorg.0.log.old before the fix below: [28.868] (II) LoadModule: "nvidia" [28.907] (WW) Warning, couldn't open module nvidia [28.907] (II) UnloadModule: "nvidia" [28.907] (II) Unloading nvidia [28.907] (EE) Failed to load module "nvidia" (module does not exist, 0) [28.907] (EE) No drivers available. [28.907] (EE) Fatal server error: [28.907] (EE) no screens found(EE) * What exactly did you do that was effective? It appears that the kernel driver packages and the xorg driver packages don't agree as to the location of the nvidia_drv.so file. Creating this symbolic link fixes the problem. ln -s /usr/lib/nvidia/legacy-304xx/nvidia_drv.so /usr/lib/xorg/modules/drivers/nvidia_drv.so * What was the outcome of this action? The X server started correctly. After that it was only a matter of setting it up with nvidia-settings. All the information below was collected by reportbug after the symbolic link above was set up and the system rebooted. The Xorg.0.log.old (also below) reflects the problem and contains the few lines included above. -- Package-specific info: uname -a: Linux graviton 4.9.0-2-686-pae #1 SMP Debian 4.9.13-1 (2017-02-27) i686 GNU/Linux /proc/version: Linux version 4.9.0-2-686-pae (debian-ker...@lists.debian.org) (gcc version 6.3.0 20170221 (Debian 6.3.0-8) ) #1 SMP Debian 4.9.13-1 (2017-02-27) /proc/driver/nvidia/version: NVRM version: NVIDIA UNIX x86 Kernel Module 304.135 Tue Jan 17 14:54:17 PST 2017 GCC version: gcc version 6.3.0 20170321 (Debian 6.3.0-11) lspci 'VGA compatible controller [0300]': 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation NV41 [GeForce 6800] [10de:00c1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation NV41 [GeForce 6800] [10de:0245] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: nvidia Kernel modules: nouveau, nvidia_legacy_304xx dmesg: Device node permissions: crw-rw+ 1 root video 226, 0 Apr 1 19:55 /dev/dri/card0 crw-rw-rw- 1 root root 195, 0 Apr 1 19:55 /dev/nvidia0 crw-rw-rw- 1 root root 195, 255 Apr 1 19:55 /dev/nvidiactl video:x:44:afc,motion OpenGL and NVIDIA library files installed: -rw-r--r-- 1 afc afc 1248 Apr 1 16:50 /etc/X11/xorg.conf lrwxrwxrwx 1 root root 22 Mar 28 22:30 /etc/alternatives/glx -> /usr/lib/mesa-diverted lrwxrwxrwx 1 root root 49 Mar 28 22:30 /etc/alternatives/glx--libEGL.so.1-i386-linux-gnu -> /usr/lib/mesa-diverted/i386-linux-gnu/libEGL.so.1 lrwxrwxrwx 1 root root 48 Mar 28 22:30 /etc/alternatives/glx--libGL.so.1-i386-linux-gnu -> /usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1 lrwxrwxrwx 1 root root 48 Mar 28 22:30 /etc/alternatives/glx--libGL.so.1-i386-linux-gnu -> /usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1 lrwxrwxrwx 1 root root 52 Mar 28 22:30 /etc/alternatives/glx--libGLESv2.so.2-i386-linux-gnu -> /usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so.2 lrwxrwxrwx 1 root root 52 Mar 28 22:30 /etc/alternatives/glx--libGLESv2.so.2-i386-linux-gnu -> /usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so.2 lrwxrwxrwx 1 root root 28 Apr 1 15:44 /etc/alternatives/nvidia -> /usr/lib/nvidia/legacy-304xx lrwxrwxrwx 1 root root 54 Apr 1 15:44 /etc/alternatives/nvidia--libGL.so.1-i386-linux-gnu -> /usr/lib/i386-linux-gnu/nvidia/legacy-304xx/libGL.so.1 lrwxrwxrwx 1 root root 54 Apr 1 15:44 /etc/alternatives/nvidia--libGL.so.1-i386-linux-gnu -> /usr/lib/i386-linux-gnu/nvidia/legacy-304xx/libGL.so.1 lrwxrwxrwx 1 root root 62 Apr 1 15:44 /etc/alternatives/nvidia--libXvMCNVIDIA.so.1-i386-linux-gnu -> /usr/lib/i386-linux-gnu/nvidia/legacy-304xx/libXvMCNVIDIA.so.1 lrwxrwxrwx 1 root root 70 Apr 1 15:44 /etc/alternatives/nvidia--libXvMCNVIDIA_dynamic.so.1-i386-linux-gnu -> /usr/lib/i386-linux-gnu/nvidia/legacy-304xx/libXvMCNVIDIA_dynamic.so.1 lrwxrwxrwx 1 root root 38 Apr 1 15:44 /etc/alternatives/nvidia--libglx.so -> /usr/lib/nvidia/legacy-304xx/libglx.so lrwxrwxrwx 1 root root 62 Apr 1 15:44 /etc/alternatives/nvidia--libnvidia-cfg.so.1-i386-linux-gnu -> /usr/lib/i386-linux-gnu/nvidia/legacy-304xx/libnvidia-cfg.so.1 lrwxrwxrwx 1 root root 61 Apr 1 15:44
Bug#508589: Problem solved by updating the kernel
Since I resurrected this bug with my previous report, I suppose I should forward this fix (from someone else on debian-user) which means that this bug can be closed. It is (as I suspected) a kernel/driver issue solved by going to a backported kernel. - Forwarded message from Rodolfo Medina rodolfo.med...@gmail.com - To: debian-u...@lists.debian.org From: Rodolfo Medina rodolfo.med...@gmail.com Subject: [solved] Re: Kernel updating Date: Tue, 13 Apr 2010 14:06:06 +0200 Rodolfo Medina rodolfo.med...@gmail.com writes: When I close a PPP connection with `C-c', the keyboard gets stuck and I have to reboot the system. The problem is reported here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=508589 In the hope of fixing it by updating the kernel, I want to install a freshly new one from the backport repositories. Can anyone suggest the exact package name? I have Lenny on an old Pentium III. Stephen Powell zlinux...@wowway.com writes: I would suggest linux-image-2.6.32-bpo.3-686 That appears to be the closest to what is in Squeeze right now. The problem seems to be solved updating the kernel. It is easy to do: I added to /etc/apt/sources.list the following line: deb http://www.backports.org/debian lenny-backports main contrib non-free , then connected to internet and did: # apt-get update # apt-get -t etch-backports install linux-image-2.6.32-bpo.3-686 Now, the command `$ls /boot' got the following output: config-2.6.26-1-686 initrd.img-2.6.26-1-686.bak vmlinuz-2.6.26-1-686 config-2.6.32-bpo.3-686 initrd.img-2.6.32-bpo.3-686 vmlinuz-2.6.32-bpo.3-686 grub System.map-2.6.26-1-686 initrd.img-2.6.26-1-686 System.map-2.6.32-bpo.3-686 , and in /boot/grub/menu.lst the new kernel was already listed. Then I rebooted. Bye, Rodolfo - End forwarded message - -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#508589: I also encounter this bug regularly
I'm using an up to date Lenny installation, standard kernel: Linux version 2.6.26-2-686 (Debian 2.6.26-21lenny4) (da...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Tue Mar 9 17:35:51 UTC 2010 I encounter this problem much too often and each time it requires a hard reboot. Strangely, the mouse still works so I can log out of kde, but then the shutdown process hangs until I hit CTRL-ALT-DEL. Then it continues, but the laptop (Dell 8600) doesn't shut down all the way. I have to hold the power button for 10 seconds and then it does shut down. This is a very low level issue. I don't use kppp. This happens with regular poff. I suspect it's related to the cdc_acm driver which is the one being used by my phone (motorola e815) through a usb cable. It's not 100% repeatable. It might be a race condition and I have encountered it most often a couple of seconds after issuing a poff, before disconnecting the usb cable. It does not seem to happen if the ppp connection is terminated by the other side (LCP terminated by peer). A. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#415050: (no subject)
Subject: thinkpad-source: Undefined symbols inter_module_register and inter_module_unregister (2.6.18) Package: thinkpad-source Version: 5.9-2.1 Severity: grave Justification: renders package unusable It appears that inter_module_register() and inter_module_unregister() have been removed from kernel 2.6.18. Since all drivers in this package depend on it, loading fails. I'd provide a patch, but I haven't found the current replacements or functional equivalents of these functions. Hints anyone? -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages thinkpad-source depends on: ii debhelper 5.0.42 helper programs for debian/rules ii devscripts2.9.26 Scripts to make the life of a Debi ii gcc [c-compiler] 4:4.1.1-15 The GNU C compiler ii gcc-3.3 [c-compiler] 1:3.3.6-15 The GNU C compiler ii gcc-4.1 [c-compiler] 4.1.1-21 The GNU C compiler ii make 3.81-2 The GNU version of the make util Versions of packages thinkpad-source recommends: ii dpkg-dev 1.13.25package building tools for Debian ii kernel-package10.067 A utility for building Linux kerne -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#400141: This bug can be fixed by renaming the .s file to .S
I came across this fix by perusing another bug report. It works. Rename the assembler file smapi_call.s to smapi_call.S (capital S). A. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
