nouveau.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Karol Herbst <kherbst@redhat.com>
To: sboyce@blueyonder.co.uk
Cc: "nouveau@lists.freedesktop.org" <nouveau@lists.freedesktop.org>
Subject: Re: [Nouveau] nouveau failure 5.14-rc1 and -rc2
Date: Wed, 21 Jul 2021 15:13:39 +0200	[thread overview]
Message-ID: <CACO55tvQr5Te3hgn6OXFba30gQPUy2vOBbYnAMgWXXOHZGxTLA@mail.gmail.com> (raw)
In-Reply-To: <02813601-91da-5ab3-7852-1947c7bbf84c@blueyonder.co.uk>

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 <sboyce@blueyonder.co.uk> 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-0000: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-0000:05:00.3-6/input2
> [Mon Jul 19 00:02:07 2021] nouveau 0000:08:00.0: DRM: VRAM: 4096 MiB
> [Mon Jul 19 00:02:07 2021] nouveau 0000:08:00.0: DRM: GART: 1048576 MiB
> [Mon Jul 19 00:02:07 2021] nouveau 0000:08:00.0: DRM: TMDS table version 2.0
> [Mon Jul 19 00:02:07 2021] nouveau 0000:08:00.0: DRM: DCB version 4.0
> [Mon Jul 19 00:02:07 2021] nouveau 0000:08:00.0: DRM: DCB outp 00:
> 02000300 00000000
> [Mon Jul 19 00:02:07 2021] nouveau 0000:08:00.0: DRM: DCB outp 01:
> 01000302 00020030
> [Mon Jul 19 00:02:07 2021] nouveau 0000:08:00.0: DRM: DCB outp 02:
> 04011380 00000000
> [Mon Jul 19 00:02:07 2021] nouveau 0000:08:00.0: DRM: DCB outp 03:
> 08011382 00020030
> [Mon Jul 19 00:02:07 2021] nouveau 0000:08:00.0: DRM: DCB outp 04:
> 02022362 00020010
> [Mon Jul 19 00:02:07 2021] nouveau 0000:08:00.0: DRM: DCB conn 00: 00001030
> [Mon Jul 19 00:02:07 2021] nouveau 0000:08:00.0: DRM: DCB conn 01: 00000100
> [Mon Jul 19 00:02:07 2021] nouveau 0000:08:00.0: DRM: DCB conn 02: 00002261
> [Mon Jul 19 00:02:07 2021] nouveau 0000:08:00.0: DRM: failed to
> initialise sync subsystem, -28
> [Mon Jul 19 00:02:07 2021] nouveau 0000:08:00.0: bus: MMIO write of
> 00000002 FAULT at 13c154 [ PRIVRING ]
> [Mon Jul 19 00:02:07 2021] nouveau: probe of 0000: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, as it disables systemd's process
> lifecycle management for the service. Please update your service to use
> a safer KillMode=, such as 'mixed' or 'control-group'. Support for
> KillMode=none is deprecated and will eventually be removed.
> [Mon Jul 19 00:02:23 2021] systemd[1]: haveged.service: Main process
> exited, code=exited, status=1/FAILURE
> [Mon Jul 19 00:02:23 2021] systemd[1]: haveged.service: Failed 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 mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

  reply	other threads:[~2021-07-21 13:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-19 20:36 [Nouveau] nouveau failure 5.14-rc1 and -rc2 Sid Boyce
2021-07-21 13:13 ` Karol Herbst [this message]
2021-07-21 13:16   ` Karol Herbst
2021-07-21 16:41     ` Sid Boyce

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CACO55tvQr5Te3hgn6OXFba30gQPUy2vOBbYnAMgWXXOHZGxTLA@mail.gmail.com \
    --to=kherbst@redhat.com \
    --cc=nouveau@lists.freedesktop.org \
    --cc=sboyce@blueyonder.co.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).