Re: [Nouveau] nouveau failure 5.14-rc1 and -rc2
Excellent, thanks. I could have done a git bisect from another box. I didn't think of it. Regards Sid. On 21/07/2021 14:16, Karol Herbst wrote: actually.. it was already found in this thread: https://lore.kernel.org/lkml/YOC4uekpD7iA3xPi@Red/T/ fixes incoming. On Wed, Jul 21, 2021 at 3:13 PM Karol Herbst wrote: fyi: I am able to reproduce it on my machine and will figure out what's wrong. Thanks! On Mon, Jul 19, 2021 at 10:53 PM Sid Boyce wrote: Also sent this to kernel mailing list. I saw an earlier kernel mailing list post (week 8 - 15 July) that so far hasn't made it into 5.14-rc. GPU's are GeForce GTX 1650, and 2 with GeForce GTX 1050 Ti. 3 systems affected, nothing displayed during boot up. I use ssh from a running system to look at dmesg output. [Mon Jul 19 00:02:06 2021] hid-generic 0003:0CCD:0028.0004: input,hidraw3: USB HID v1.00 Device [USB Audio] on usb-:05:00.3-4/input3 [Mon Jul 19 00:02:06 2021] usb 5-6: new full-speed USB device number 4 using xhci_hcd [Mon Jul 19 00:02:06 2021] usb 5-6: config 1 has an invalid interface number: 2 but max is 1 [Mon Jul 19 00:02:06 2021] usb 5-6: config 1 has no interface number 1 [Mon Jul 19 00:02:06 2021] usb 5-6: New USB device found, idVendor=0b05, idProduct=18f3, bcdDevice= 1.00 [Mon Jul 19 00:02:06 2021] usb 5-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [Mon Jul 19 00:02:06 2021] usb 5-6: Product: AURA LED Controller [Mon Jul 19 00:02:06 2021] usb 5-6: Manufacturer: AsusTek Computer Inc. [Mon Jul 19 00:02:06 2021] usb 5-6: SerialNumber: 9876543210 [Mon Jul 19 00:02:06 2021] hid-generic 0003:0B05:18F3.0005: hiddev96,hidraw4: USB HID v1.11 Device [AsusTek Computer Inc. AURA LED Controller] on usb-:05:00.3-6/input2 [Mon Jul 19 00:02:07 2021] nouveau :08:00.0: DRM: VRAM: 4096 MiB [Mon Jul 19 00:02:07 2021] nouveau :08:00.0: DRM: GART: 1048576 MiB [Mon Jul 19 00:02:07 2021] nouveau :08:00.0: DRM: TMDS table version 2.0 [Mon Jul 19 00:02:07 2021] nouveau :08:00.0: DRM: DCB version 4.0 [Mon Jul 19 00:02:07 2021] nouveau :08:00.0: DRM: DCB outp 00: 02000300 [Mon Jul 19 00:02:07 2021] nouveau :08:00.0: DRM: DCB outp 01: 01000302 00020030 [Mon Jul 19 00:02:07 2021] nouveau :08:00.0: DRM: DCB outp 02: 04011380 [Mon Jul 19 00:02:07 2021] nouveau :08:00.0: DRM: DCB outp 03: 08011382 00020030 [Mon Jul 19 00:02:07 2021] nouveau :08:00.0: DRM: DCB outp 04: 02022362 00020010 [Mon Jul 19 00:02:07 2021] nouveau :08:00.0: DRM: DCB conn 00: 1030 [Mon Jul 19 00:02:07 2021] nouveau :08:00.0: DRM: DCB conn 01: 0100 [Mon Jul 19 00:02:07 2021] nouveau :08:00.0: DRM: DCB conn 02: 2261 [Mon Jul 19 00:02:07 2021] nouveau :08:00.0: DRM: failed to initialise sync subsystem, -28 [Mon Jul 19 00:02:07 2021] nouveau :08:00.0: bus: MMIO write of 0002 FAULT at 13c154 [ PRIVRING ] [Mon Jul 19 00:02:07 2021] nouveau: probe of :08:00.0 failed with error -28 [Mon Jul 19 00:02:08 2021] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none. [Mon Jul 19 00:02:08 2021] systemd-journald[286]: Received SIGTERM from PID 1 (systemd). [Mon Jul 19 00:02:09 2021] systemd[1]: systemd 248.3+suse.30.ge9a23d9e06 running in system mode. (+PAM +AUDIT +SELINUX +APPARMOR -IMA -SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN -IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified) [Mon Jul 19 00:02:09 2021] systemd[1]: Detected architecture x86-64. [Mon Jul 19 00:02:21 2021] systemd-sysv-generator[619]: SysV service '/etc/init.d/vmware-USBArbitrator' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. [Mon Jul 19 00:02:21 2021] systemd-sysv-generator[619]: SysV service '/etc/init.d/webmin' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. [Mon Jul 19 00:02:21 2021] systemd-sysv-generator[619]: SysV service '/etc/init.d/vmware' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. [Mon Jul 19 00:02:22 2021] systemd[1]: /etc/systemd/system/tmp.mount: symlinks are not allowed for units of this type, rejecting. [Mon Jul 19 00:02:23 2021] systemd[1]: /usr/lib/systemd/system/netdata.service:14: PIDFile= references a path below legacy directory /var/run/, updating /var/run/netdata/netdata.pid → /run/netdata/netdata.pid; please update the unit file accordingly. [Mon Jul 19 00:02:23 2021] systemd[1]: /usr/lib/systemd/system/plymouth-start.service:15: Unit configured to use KillMode=none. This is unsafe
[Nouveau] nouveau failure 5.14-rc1 and -rc2
with result 'exit-code'. [Mon Jul 19 00:02:23 2021] systemd[1]: Stopped Entropy Daemon based on the HAVEGE algorithm. [Mon Jul 19 00:02:23 2021] systemd[1]: initrd-switch-root.service: Deactivated successfully. [Mon Jul 19 00:02:23 2021] systemd[1]: Stopped Switch Root. [Mon Jul 19 00:02:23 2021] systemd[1]: systemd-journald.service: Scheduled restart job, restart counter is at 1. [Mon Jul 19 00:02:23 2021] systemd[1]: Created slice system-getty.slice. [Mon Jul 19 00:02:23 2021] systemd[1]: Created slice system-modprobe.slice. [Mon Jul 19 00:02:23 2021] systemd[1]: Created slice User and Session Slice. [Mon Jul 19 00:02:23 2021] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks ___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] 5.6-rc3 nouveau failure, 5.6-rc2 OK
[94.455712] [T411] nouveau :07:00.0 disp ctor failed, -12 Welcome to openSUSE Tumbleweed 20200224 - Kernel 5.6.0-rc3 (tty1) ens3s0: 192.168.10.214 ... login: I can login here but X does not start -- lspci 07:00.0 VGA compatible controller: NVIDIA Corporation TU117 [GeForce GTX 1650] (rev a1) from dmesg:- [Wed Feb 26 22:42:39 2020] nouveau :07:00.0: NVIDIA TU117 (167000a1) [Wed Feb 26 22:42:39 2020] nouveau :07:00.0: bios: version 90.17.2a.00.39 [Wed Feb 26 22:44:12 2020] nouveau :07:00.0: disp ctor failed, -12 [Wed Feb 26 22:44:12 2020] nouveau: probe of :07:00.0 failed with error -12 Another box with VGA compatible controller: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] (rev a1) boots to graphical environment with 5.6-rc3. tindog:~ # dmesg -T|grep nouveau [Mon Feb 24 12:50:16 2020] nouveau :07:00.0: NVIDIA GF106 (0c3100a1) [Mon Feb 24 12:50:16 2020] nouveau :07:00.0: bios: version 70.26.37.00.01 [Mon Feb 24 12:50:16 2020] nouveau :07:00.0: fb: 4096 MiB GDDR5 [Mon Feb 24 12:50:17 2020] nouveau :07:00.0: DRM: VRAM: 4096 MiB [Mon Feb 24 12:50:17 2020] nouveau :07:00.0: DRM: GART: 1048576 MiB [Mon Feb 24 12:50:17 2020] nouveau :07:00.0: DRM: TMDS table version 2.0 [Mon Feb 24 12:50:17 2020] nouveau :07:00.0: DRM: DCB version 4.0 [Mon Feb 24 12:50:17 2020] nouveau :07:00.0: DRM: DCB outp 00: 02000300 [Mon Feb 24 12:50:17 2020] nouveau :07:00.0: DRM: DCB outp 01: 01000302 00020030 [Mon Feb 24 12:50:17 2020] nouveau :07:00.0: DRM: DCB outp 02: 04011380 [Mon Feb 24 12:50:17 2020] nouveau :07:00.0: DRM: DCB outp 03: 08011382 00020030 [Mon Feb 24 12:50:17 2020] nouveau :07:00.0: DRM: DCB outp 04: 02022362 00020010 [Mon Feb 24 12:50:17 2020] nouveau :07:00.0: DRM: DCB conn 00: 1030 [Mon Feb 24 12:50:17 2020] nouveau :07:00.0: DRM: DCB conn 01: 0100 [Mon Feb 24 12:50:17 2020] nouveau :07:00.0: DRM: DCB conn 02: 2261 [Mon Feb 24 12:50:17 2020] nouveau :07:00.0: DRM: MM: using COPY0 for buffer copies [Mon Feb 24 12:50:17 2020] nouveau :07:00.0: DRM: allocated 1920x1080 fb: 0x6, bo 8db05e25 [Mon Feb 24 12:50:17 2020] fbcon: nouveaudrmfb (fb0) is primary device [Mon Feb 24 12:50:17 2020] nouveau :07:00.0: fb0: nouveaudrmfb frame buffer device [Mon Feb 24 12:50:17 2020] [drm] Initialized nouveau 1.3.1 20120801 for :07:00.0 on minor 0 I have tried the new firmware, result is the same. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=2277987a593d54c1e922a9f25445802071015f42 Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks ___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] GF114 [GeForce GTX 560 Ti] (rev a1) slow and flickering display
May also be useful. 73 ... Sid. On 29/06/16 15:19, Ilia Mirkin wrote: Please provide your dmesg and xorg logs from the affected machine. Thanks, -ilia On Wed, Jun 29, 2016 at 8:17 AM, Sid Boyce <sbo...@blueyonder.co.uk> wrote: I recently replaced a 8600 GT with the above card on openSUSE Tumbleweed x86_64. The screen now flickers and when I change desktops it takes a some 10 to 15 seconds to display the new windows. e.g if I change from desktop 1 (konsole) to desktop 8 (thunderbird) it switches but konsole is displayed for 10 to 15 seconds before thunderbird appears. Occasionally the screen flickers wildly before settling down again. I don't see any errors in dmesg. 01:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 Ti] (rev a1) # rpm -qa|grep nouveau libvdpau_nouveau-11.2.2-139.2.x86_64 xf86-video-nouveau-1.0.12-1.3.x86_64 libdrm_nouveau2-2.4.68-1.2.x86_64 libXvMC_nouveau-32bit-11.2.2-139.2.x86_64 libvdpau_nouveau-32bit-11.2.2-139.2.x86_64 libXvMC_nouveau-11.2.2-139.2.x86_64 libdrm_nouveau2-32bit-2.4.68-1.2.x86_64 2 other boxes are OK with the cards below, all 3 boxes are at the same software levels. 01:00.0 VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT 610] (rev a1) 05:00.0 VGA compatible controller: NVIDIA Corporation G84 [GeForce 8600 GT] (rev a1) Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks ___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks kdm.log.gz Description: GNU Zip compressed data ___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] GF114 [GeForce GTX 560 Ti] (rev a1) slow and flickering display
dmesg is filled with audit message noise so I've attached boot.msg instead. 73 ... Sid. On 29/06/16 15:19, Ilia Mirkin wrote: Please provide your dmesg and xorg logs from the affected machine. Thanks, -ilia On Wed, Jun 29, 2016 at 8:17 AM, Sid Boyce <sbo...@blueyonder.co.uk> wrote: I recently replaced a 8600 GT with the above card on openSUSE Tumbleweed x86_64. The screen now flickers and when I change desktops it takes a some 10 to 15 seconds to display the new windows. e.g if I change from desktop 1 (konsole) to desktop 8 (thunderbird) it switches but konsole is displayed for 10 to 15 seconds before thunderbird appears. Occasionally the screen flickers wildly before settling down again. I don't see any errors in dmesg. 01:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 Ti] (rev a1) # rpm -qa|grep nouveau libvdpau_nouveau-11.2.2-139.2.x86_64 xf86-video-nouveau-1.0.12-1.3.x86_64 libdrm_nouveau2-2.4.68-1.2.x86_64 libXvMC_nouveau-32bit-11.2.2-139.2.x86_64 libvdpau_nouveau-32bit-11.2.2-139.2.x86_64 libXvMC_nouveau-11.2.2-139.2.x86_64 libdrm_nouveau2-32bit-2.4.68-1.2.x86_64 2 other boxes are OK with the cards below, all 3 boxes are at the same software levels. 01:00.0 VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT 610] (rev a1) 05:00.0 VGA compatible controller: NVIDIA Corporation G84 [GeForce 8600 GT] (rev a1) Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks ___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks Xorg.0.log.gz Description: GNU Zip compressed data boot.msg.gz Description: GNU Zip compressed data ___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] GF114 [GeForce GTX 560 Ti] (rev a1) slow and flickering display
I recently replaced a 8600 GT with the above card on openSUSE Tumbleweed x86_64. The screen now flickers and when I change desktops it takes a some 10 to 15 seconds to display the new windows. e.g if I change from desktop 1 (konsole) to desktop 8 (thunderbird) it switches but konsole is displayed for 10 to 15 seconds before thunderbird appears. Occasionally the screen flickers wildly before settling down again. I don't see any errors in dmesg. 01:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 Ti] (rev a1) # rpm -qa|grep nouveau libvdpau_nouveau-11.2.2-139.2.x86_64 xf86-video-nouveau-1.0.12-1.3.x86_64 libdrm_nouveau2-2.4.68-1.2.x86_64 libXvMC_nouveau-32bit-11.2.2-139.2.x86_64 libvdpau_nouveau-32bit-11.2.2-139.2.x86_64 libXvMC_nouveau-11.2.2-139.2.x86_64 libdrm_nouveau2-32bit-2.4.68-1.2.x86_64 2 other boxes are OK with the cards below, all 3 boxes are at the same software levels. 01:00.0 VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT 610] (rev a1) 05:00.0 VGA compatible controller: NVIDIA Corporation G84 [GeForce 8600 GT] (rev a1) Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks ___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] [[Bug 94990] Latest 4.6rc4 kernel, no booting on gtx970
On 23/04/16 13:00, nouveau-requ...@lists.freedesktop.org wrote: [Bug 94990] Latest 4.6rc4 kernel, no booting on gtx970 I had something similar with a VGA compatible controller: NVIDIA Corporation G84 [GeForce 8600 GT] (rev a1) YaST2/mkinitrd.log:W: Possible missing firmware "nvidia/gm204/acr/bl.bin" for kernel module "nouveau.ko" Same message for all .bin files on openSUSE Tumbleweed. The files were all there under /lib/firmware/nvidia/gm204. Forcing a reinstall of the kernel-firmware package solved it. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks ___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] 3.19.0-rc1 nouvea build failure on GeForce GT 610 only
CHK kernel/config_data.h CC [M] drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.o drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.c: In function ‘nvd0_dmaobj_bind’: drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.c:54:8: error: ‘GM204_DISP_CORE_CHANNEL_DMA’ undeclared (first use in this function) case GM204_DISP_CORE_CHANNEL_DMA: ^ drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.c:54:8: note: each undeclared identifier is reported only once for each function it appears in scripts/Makefile.build:257: recipe for target 'drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.o' failed make[4]: *** [drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.o] Error 1 scripts/Makefile.build:402: recipe for target 'drivers/gpu/drm/nouveau' failed make[3]: *** [drivers/gpu/drm/nouveau] Error 2 scripts/Makefile.build:402: recipe for target 'drivers/gpu/drm' failed make[2]: *** [drivers/gpu/drm] Error 2 scripts/Makefile.build:402: recipe for target 'drivers/gpu' failed make[1]: *** [drivers/gpu] Error 2 Makefile:938: recipe for target 'drivers' failed make: *** [drivers] Error 2 01:00.0 VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT 610] (rev a1) No problems on 2 other boxes with GeForce 8600 GT] (rev a1) Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] 3.19.0-rc1 nouvea build failure on GeForce GT 610 only
On 22/12/14 13:54, Paul Bolle wrote: On Mon, 2014-12-22 at 14:37 +0100, Paul Bolle wrote: On Mon, 2014-12-22 at 13:01 +, Sid Boyce wrote: CHK kernel/config_data.h CC [M] drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.o drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.c: In function ‘nvd0_dmaobj_bind’: drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.c:54:8: error: ‘GM204_DISP_CORE_CHANNEL_DMA’ undeclared (first use in this function) case GM204_DISP_CORE_CHANNEL_DMA: ^ drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.c:54:8: note: each undeclared identifier is reported only once for each function it appears in scripts/Makefile.build:257: recipe for target 'drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.o' failed make[4]: *** [drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.o] Error 1 scripts/Makefile.build:402: recipe for target 'drivers/gpu/drm/nouveau' failed make[3]: *** [drivers/gpu/drm/nouveau] Error 2 scripts/Makefile.build:402: recipe for target 'drivers/gpu/drm' failed make[2]: *** [drivers/gpu/drm] Error 2 scripts/Makefile.build:402: recipe for target 'drivers/gpu' failed make[1]: *** [drivers/gpu] Error 2 Makefile:938: recipe for target 'drivers' failed make: *** [drivers] Error 2 01:00.0 VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT 610] (rev a1) Why would that controller influence the build? No problems on 2 other boxes with GeForce 8600 GT] (rev a1) I ran into this error twice, while building Fedora 21 kernel rpms for v3.19-rc1 on my outdated ThinkPad X41 (which uses i915, for what it's worth). The error made very little sense to me. Especially since it didn't happen when building in the local git repository. So I basically, well, scrubbed the rpmbuild environment. And then the the third attempt to build kernels rpm succeeded! I assumed a hardware failure (see outdated above) and made a mental note to investigate that one of these days. But your report makes me think it's not my hardware. Could there be some _random_ failure with this driver in the build? Very odd... A theory based on Mark's message in https://lkml.org/lkml/2014/12/8/602 : My two failed builds somehow used previous version of class.h, that didn't yet have commit 1f89b4756fb8 (drm/gm204/disp: initial support) applied. It's that commit which added the define for GM204_DISP_CORE_CHANNEL_DMA. Is that even possible? Perhaps rpmbuild has a surprising way to handle symlinks? All very puzzling... Paul Bolle I did a git pull up to 3.19-rc1 separately on the 3 boxes and used the .config from 3.18.0 as the base of make oldconfig. When the build failed I did make mrproper and used the .config from one of the other boxes, then from the other, all 3 .config gave the same error. Successfully rebooted one of the boxes. sabre:~ # uname -r 3.19.0-rc1-smp+ Regards ... Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] Problem with kernels 3.15.0-rc and GF114 [GeForce, GTX 560 Ti] (rev a1) **FIXED**
Whatever the problem was, kernel 3.15.0-rc5 fixed it. I am not in a position to do a git bisect at present. Regards Sid. On 02/05/14 18:17, nouveau-requ...@lists.freedesktop.org wrote: Subject: [Nouveau] Problem with kernels 3.15.0-rc and GF114 [GeForce GTX 560 Ti] (rev a1) Message-ID:53638fa1.6020...@blueyonder.co.uk Content-Type: text/plain; charset=ISO-8859-1; format=flowed On the slipstream box I have no problems with 3.14.0 kernel. With 3.15.0-rc kernels, in KDE some applications fail to start - e.g kmix, some like thunderbird come up but are not usable, e.g clicking to display a message text, nothing happens and sometimes screens won't switch. slipstream:~ # lspci 01:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 Ti] (rev a1) slipstream:~ # uname -r 3.14.0-smp+ On the 2 other systems with the same openSUSE 13.2 Milestone 0 distro and identical software levels and packages but different video cards there is no problem - both up and running on vanilla kernel 3.15.0-rc3 since Monday. sabre:~ # lspci 01:00.0 VGA compatible controller: NVIDIA Corporation G84 [GeForce 8600 GT] (rev a1) sabre:~ # uname -r 3.15.0-rc3-smp+ tindog:~ # lspci 01:00.0 VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT 610] (rev a1) tindog:~ # uname -r 3.15.0-rc3-smp+ On all systems the kernel config is identical. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] Problem with kernels 3.15.0-rc and GF114 [GeForce GTX 560 Ti] (rev a1)
On the slipstream box I have no problems with 3.14.0 kernel. With 3.15.0-rc kernels, in KDE some applications fail to start - e.g kmix, some like thunderbird come up but are not usable, e.g clicking to display a message text, nothing happens and sometimes screens won't switch. slipstream:~ # lspci 01:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 Ti] (rev a1) slipstream:~ # uname -r 3.14.0-smp+ On the 2 other systems with the same openSUSE 13.2 Milestone 0 distro and identical software levels and packages but different video cards there is no problem - both up and running on vanilla kernel 3.15.0-rc3 since Monday. sabre:~ # lspci 01:00.0 VGA compatible controller: NVIDIA Corporation G84 [GeForce 8600 GT] (rev a1) sabre:~ # uname -r 3.15.0-rc3-smp+ tindog:~ # lspci 01:00.0 VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT 610] (rev a1) tindog:~ # uname -r 3.15.0-rc3-smp+ On all systems the kernel config is identical. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [PATCH] Fix hang problem with GeForce GT 560 Ti and nouveau in 3.13-rc
-- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks This patch stops a console hang with VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 Ti] (rev a1) 3.13-rc defines NVDEV_SUBDEV_MC as nvc3_mc_oclass, it needs to be defined as nvc0_mc_oclass Signed off by: Sid Boyce (sbo...@blueyonder.co.uk) Tested by: Sid Boyce (sbo...@blueyonder.co.uk) --- drivers/gpu/drm/nouveau/core/engine/device/nvc0.c 1 -+ 1 file changed, 1 insertion(+), 1 deletion(-) INDEX: linux/drivers/gpu/drm/nouveau/core/engine/device/nvc0.c = diff -up a/drivers/gpu/drm/nouveau/core/engine/device/nvc0.c b/drivers/gpu/drm/nouveau/core/engine/device/nvc0.c --- a/drivers/gpu/drm/nouveau/core/engine/device/nvc0.c 2013-11-23 13:03:23.797604441 + +++ b/drivers/gpu/drm/nouveau/core/engine/device/nvc0.c 2014-01-02 02:13:32.445643092 + @@ -161,7 +161,7 @@ nvc0_identify(struct nouveau_device *dev device-oclass[NVDEV_SUBDEV_THERM ] = nva3_therm_oclass; device-oclass[NVDEV_SUBDEV_MXM] = nv50_mxm_oclass; device-oclass[NVDEV_SUBDEV_DEVINIT] = nvc0_devinit_oclass; - device-oclass[NVDEV_SUBDEV_MC ] = nvc3_mc_oclass; + device-oclass[NVDEV_SUBDEV_MC ] = nvc0_mc_oclass; device-oclass[NVDEV_SUBDEV_BUS] = nvc0_bus_oclass; device-oclass[NVDEV_SUBDEV_TIMER ] = nv04_timer_oclass; device-oclass[NVDEV_SUBDEV_FB ] = nvc0_fb_oclass; ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] Possible 3.13-rc nouveau regression with GT 560 Ti
On 31/12/13 10:36, Ilia Mirkin wrote: On Tue, Dec 31, 2013 at 5:14 AM, Sid Boyce sbo...@blueyonder.co.uk wrote: System x86_64 with openSUSE 13.1. X.Org version: 1.14.99.905 openSUSE 12.2 kernels boot successfully into a graphical screen, login to KDE4, etc. all normal. 3.13-rc kernels boot fully with X running but no graphical screen and it freezes in VC with not all the startup messages displayed but I could ssh in from another box to check dmesg and logs. Xorg.0.log which I thought I had saved did not log an error. dmesg said nouveau Playlist update failed. Changed the GeForce GT 560 Ti for a GeForce 8600 GT and 3.13.0-rc6 is up and running. If necessary I can go back to the GT 560 Ti to gather dmesg and Xorg log information. Having a dmesg would be nice. One thing I can think of off-hand is that 3.13-rc has MSI turned on by default. You can turn it off by adding nouveau.config=NvMSI=0 to your kernel cmdline. If that doesn't help, a bisect restricted to drivers/gpu/drm/nouveau should show the offending commit fairly quickly. -ilia Adding nouveau.config=NvMSI=0 to the command line fixed the problem. So it looks like commit 049ffa8ab33a63b3bff672d1a0ee6a35ad253fe8 introduced it. Thanks Ilia, Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] Possible 3.13-rc nouveau regression with GT 560 Ti
On 01/01/14 00:55, Ilia Mirkin wrote: On Tue, Dec 31, 2013 at 7:41 PM, Sid Boyce sbo...@blueyonder.co.uk wrote: On 31/12/13 10:36, Ilia Mirkin wrote: On Tue, Dec 31, 2013 at 5:14 AM, Sid Boyce sbo...@blueyonder.co.uk wrote: System x86_64 with openSUSE 13.1. X.Org version: 1.14.99.905 openSUSE 12.2 kernels boot successfully into a graphical screen, login to KDE4, etc. all normal. 3.13-rc kernels boot fully with X running but no graphical screen and it freezes in VC with not all the startup messages displayed but I could ssh in from another box to check dmesg and logs. Xorg.0.log which I thought I had saved did not log an error. dmesg said nouveau Playlist update failed. Changed the GeForce GT 560 Ti for a GeForce 8600 GT and 3.13.0-rc6 is up and running. If necessary I can go back to the GT 560 Ti to gather dmesg and Xorg log information. Having a dmesg would be nice. One thing I can think of off-hand is that 3.13-rc has MSI turned on by default. You can turn it off by adding nouveau.config=NvMSI=0 to your kernel cmdline. If that doesn't help, a bisect restricted to drivers/gpu/drm/nouveau should show the offending commit fairly quickly. -ilia Adding nouveau.config=NvMSI=0 to the command line fixed the problem. So it looks like commit 049ffa8ab33a63b3bff672d1a0ee6a35ad253fe8 introduced it. Any chance you might mmiotrace the blob (version 325 or later) to see which registers it fiddles with? Or alternatively, if you have a NVCE card (you never did end up providing the logs which would have made that apparent), could you try replacing nvc3_mc_oclass with nvc0_mc_oclass for the 0xce case in drivers/gpu/drm/nouveau/core/engine/device/nvc0.c? (and boot without the MSI disabling.) The switch has already been made for NVC8 in 0bae1d61c75 -- perhaps there are more odd ones. -ilia I'll have a look tomorrow - it is a NVCE card.. With everything running at the moment # echo mmiotrace /sys/kernel/debug/tracing/current_tracer bash: echo: write error: Invalid argument I shall build a new kernel (3.13.0-rc51) with the change case 0xce: device-cname = GF114; device-oclass[NVDEV_SUBDEV_VBIOS ] = nouveau_bios_oclass; device-oclass[NVDEV_SUBDEV_GPIO ] = nv50_gpio_oclass; device-oclass[NVDEV_SUBDEV_I2C] = nv94_i2c_oclass; device-oclass[NVDEV_SUBDEV_CLOCK ] = nvc0_clock_oclass; device-oclass[NVDEV_SUBDEV_THERM ] = nva3_therm_oclass; device-oclass[NVDEV_SUBDEV_MXM] = nv50_mxm_oclass; device-oclass[NVDEV_SUBDEV_DEVINIT] = nvc0_devinit_oclass; device-oclass[NVDEV_SUBDEV_MC ] = nvc3_mc_oclass; Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks [97.740] This is a pre-release version of the X server from The X.Org Foundation. It is not supported in any way. Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/. Select the xorg product for bugs you find in this release. Before reporting bugs in pre-release versions please check the latest version in the X.Org Foundation git repository. See http://wiki.x.org/wiki/GitPage for git access instructions. [97.740] X.Org X Server 1.14.99.905 (1.15.0 RC 5) Release Date: 2013-12-19 [97.740] X Protocol Version 11, Revision 0 [97.740] Build Operating System: openSUSE SUSE LINUX [97.740] Current Operating System: Linux slipstream 3.13.0-rc6-smp+ #1 SMP PREEMPT Mon Dec 30 15:47:46 GMT 2013 x86_64 [97.740] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.13.0-rc6-smp+ root=UUID=9e02a4c0-c401-4874-a706-30ec3f0a98aa nouveau.config=NvMSI=0 quiet splash [97.740] Build Date: 22 December 2013 07:18:32PM [97.740] [97.740] Current version of pixman: 0.32.4 [97.740] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [97.740] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [97.740] (==) Log file: /var/log/Xorg.0.log, Time: Wed Jan 1 00:26:25 2014 [97.741] (==) Using config directory: /etc/X11/xorg.conf.d [97.741] (==) Using system config directory /usr/share/X11/xorg.conf.d [97.741] (==) No Layout section. Using the first Screen section. [97.741] (==) No screen section available. Using defaults. [97.741] (**) |--Screen Default Screen Section (0) [97.741] (**) | |--Monitor default monitor [97.741] (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. [97.741] (==) Automatically adding devices [97.741] (==) Automatically enabling devices [97.741] (==) Automatically adding GPU
Re: [Nouveau] Possible 3.13-rc nouveau regression with GT 560 Ti
On 01/01/14 18:46, Ilia Mirkin wrote: On Wed, Jan 1, 2014 at 9:04 AM, Sid Boyce sbo...@blueyonder.co.uk wrote: On 01/01/14 00:55, Ilia Mirkin wrote: On Tue, Dec 31, 2013 at 7:41 PM, Sid Boyce sbo...@blueyonder.co.uk wrote: On 31/12/13 10:36, Ilia Mirkin wrote: Having a dmesg would be nice. One thing I can think of off-hand is that 3.13-rc has MSI turned on by default. You can turn it off by adding nouveau.config=NvMSI=0 to your kernel cmdline. If that doesn't help, a bisect restricted to drivers/gpu/drm/nouveau should show the offending commit fairly quickly. -ilia Adding nouveau.config=NvMSI=0 to the command line fixed the problem. So it looks like commit 049ffa8ab33a63b3bff672d1a0ee6a35ad253fe8 introduced it. Any chance you might mmiotrace the blob (version 325 or later) to see which registers it fiddles with? Or alternatively, if you have a NVCE card (you never did end up providing the logs which would have made that apparent), could you try replacing nvc3_mc_oclass with nvc0_mc_oclass for the 0xce case in drivers/gpu/drm/nouveau/core/engine/device/nvc0.c? (and boot without the MSI disabling.) The switch has already been made for NVC8 in 0bae1d61c75 -- perhaps there are more odd ones. -ilia Fails exactly the same. case 0xc3: device-cname = GF106; device-oclass[NVDEV_SUBDEV_VBIOS ] = nouveau_bios_oclass; device-oclass[NVDEV_SUBDEV_GPIO ] = nv50_gpio_oclass; device-oclass[NVDEV_SUBDEV_I2C] = nv94_i2c_oclass; device-oclass[NVDEV_SUBDEV_CLOCK ] = nvc0_clock_oclass; device-oclass[NVDEV_SUBDEV_THERM ] = nva3_therm_oclass; device-oclass[NVDEV_SUBDEV_MXM] = nv50_mxm_oclass; device-oclass[NVDEV_SUBDEV_DEVINIT] = nvc0_devinit_oclass; device-oclass[NVDEV_SUBDEV_MC ] = nvc0_mc_oclass; device-oclass[NVDEV_SUBDEV_BUS] = nvc0_bus_oclass; device-oclass[NVDEV_SUBDEV_TIMER ] = nv04_timer_oclass; That's the 0xc3 case... you have a nvce card, not nvc3 -- you would need to change the NVDEV_SUBDEV_MC line to nvc0_mc_oclass for the 0xce case. The dmesg and Xorg.0.log with the problem captured across a ssh link. # ps fax|grep X 5633 pts/0S+ 0:00 \_ grep --color=auto X 5160 tty7 Ss+0:08 \_ /usr/bin/Xorg -br :0 vt7 -nolisten tcp -auth /var/lib/kdm/AuthFiles/A:0-yqspza Also # echo mmiotrace /sys/kernel/debug/tracing/current_tracer -bash: echo: write error: Invalid argument. Take a look at https://wiki.ubuntu.com/X/MMIOTracing -ilia Of course it's a GF114. Made the change and it boots without the command line change. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] Possible 3.13-rc nouveau regression with GT 560 Ti
On 02/01/14 02:40, Ilia Mirkin wrote: On Wed, Jan 1, 2014 at 9:36 PM, Sid Boyce sbo...@blueyonder.co.uk wrote: On 01/01/14 18:46, Ilia Mirkin wrote: On Wed, Jan 1, 2014 at 9:04 AM, Sid Boyce sbo...@blueyonder.co.uk wrote: On 01/01/14 00:55, Ilia Mirkin wrote: On Tue, Dec 31, 2013 at 7:41 PM, Sid Boyce sbo...@blueyonder.co.uk wrote: On 31/12/13 10:36, Ilia Mirkin wrote: Having a dmesg would be nice. One thing I can think of off-hand is that 3.13-rc has MSI turned on by default. You can turn it off by adding nouveau.config=NvMSI=0 to your kernel cmdline. If that doesn't help, a bisect restricted to drivers/gpu/drm/nouveau should show the offending commit fairly quickly. -ilia Adding nouveau.config=NvMSI=0 to the command line fixed the problem. So it looks like commit 049ffa8ab33a63b3bff672d1a0ee6a35ad253fe8 introduced it. Any chance you might mmiotrace the blob (version 325 or later) to see which registers it fiddles with? Or alternatively, if you have a NVCE card (you never did end up providing the logs which would have made that apparent), could you try replacing nvc3_mc_oclass with nvc0_mc_oclass for the 0xce case in drivers/gpu/drm/nouveau/core/engine/device/nvc0.c? (and boot without the MSI disabling.) The switch has already been made for NVC8 in 0bae1d61c75 -- perhaps there are more odd ones. -ilia Fails exactly the same. case 0xc3: device-cname = GF106; device-oclass[NVDEV_SUBDEV_VBIOS ] = nouveau_bios_oclass; device-oclass[NVDEV_SUBDEV_GPIO ] = nv50_gpio_oclass; device-oclass[NVDEV_SUBDEV_I2C] = nv94_i2c_oclass; device-oclass[NVDEV_SUBDEV_CLOCK ] = nvc0_clock_oclass; device-oclass[NVDEV_SUBDEV_THERM ] = nva3_therm_oclass; device-oclass[NVDEV_SUBDEV_MXM] = nv50_mxm_oclass; device-oclass[NVDEV_SUBDEV_DEVINIT] = nvc0_devinit_oclass; device-oclass[NVDEV_SUBDEV_MC ] = nvc0_mc_oclass; device-oclass[NVDEV_SUBDEV_BUS] = nvc0_bus_oclass; device-oclass[NVDEV_SUBDEV_TIMER ] = nv04_timer_oclass; That's the 0xc3 case... you have a nvce card, not nvc3 -- you would need to change the NVDEV_SUBDEV_MC line to nvc0_mc_oclass for the 0xce case. The dmesg and Xorg.0.log with the problem captured across a ssh link. # ps fax|grep X 5633 pts/0S+ 0:00 \_ grep --color=auto X 5160 tty7 Ss+0:08 \_ /usr/bin/Xorg -br :0 vt7 -nolisten tcp -auth /var/lib/kdm/AuthFiles/A:0-yqspza Also # echo mmiotrace /sys/kernel/debug/tracing/current_tracer -bash: echo: write error: Invalid argument. Take a look at https://wiki.ubuntu.com/X/MMIOTracing -ilia Of course it's a GF114. Made the change and it boots without the command line change. Great! Care to send a patch? -ilia Here it is. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks --- /usr/src/linux-3.13.0-rc6/drivers/gpu/drm/nouveau/core/engine/device/nvc0.c 2013-11-23 13:03:23.797604441 + +++ /usr/src/linux-3.13.0-rc61/drivers/gpu/drm/nouveau/core/engine/device/nvc0.c 2014-01-02 02:13:32.445643092 + @@ -161,7 +161,7 @@ device-oclass[NVDEV_SUBDEV_THERM ] = nva3_therm_oclass; device-oclass[NVDEV_SUBDEV_MXM] = nv50_mxm_oclass; device-oclass[NVDEV_SUBDEV_DEVINIT] = nvc0_devinit_oclass; - device-oclass[NVDEV_SUBDEV_MC ] = nvc3_mc_oclass; + device-oclass[NVDEV_SUBDEV_MC ] = nvc0_mc_oclass; device-oclass[NVDEV_SUBDEV_BUS] = nvc0_bus_oclass; device-oclass[NVDEV_SUBDEV_TIMER ] = nv04_timer_oclass; device-oclass[NVDEV_SUBDEV_FB ] = nvc0_fb_oclass; ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
