Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #79841

Bug#1042753: nouveau: Screen remains black.

From Diederik de Haas <didi.debian@cknow.org>
Newsgroups linux.debian.bugs.dist, linux.debian.kernel
Subject Bug#1042753: nouveau: Screen remains black.
Date 2023-07-31 20:40 +0200
Message-ID <GXFYd-46ZV-1@gated-at.bofh.it> (permalink)
References <GXyDn-41RD-7@gated-at.bofh.it> <GXE65-45Qp-1@gated-at.bofh.it> <GXyDn-41RD-7@gated-at.bofh.it> <GXE65-45Qp-1@gated-at.bofh.it>
Organization Connecting Knowledge

Cross-posted to 2 groups.

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

On Monday, 31 July 2023 18:20:12 CEST Olaf Skibbe wrote:
> > If there is a 6.1 kernel that does work, then it helps if you can find the
> > latest 6.1 kernel which works and (thus) the first kernel version where it
> > stopped working.
> 
> I installed 6.1.0-9-amd64 now from the standard repositories and
> graphics works. Hope this is sufficient to narrow it down

Yep, now we know it's a regression between 6.1.27-1 and 6.1.38-2.

https://wiki.debian.org/DebianKernel/GitBisect describes the best way as it
would identify the exact (upstream) commit which introduced the problem.
If you can do that, great.

If not, we can try to make an educated guess
me@pc:~/dev/kernel.org/linux$ git log --oneline v6.1.27..v6.1.38 -- drivers/gpu/drm/nouveau/
62aecf23f3d1 drm/nouveau: add nv_encoder pointer check for NULL
fb725beca62d drm/nouveau/dp: check for NULL nv_connector->native_mode
90748be0f4f3 drm/nouveau: don't detect DSM for non-NVIDIA device
5a144bad3e75 nouveau: fix client work fence deletion race

This is the list of commits to the nouveau driver between those versions.
I've attached 4 patches created with `git revert <commit-id>`

https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#id-1.6.6.4
describes a procedure for "Simple patching and building" and the idea is to
pass these 4 patches as argument to `test-patches`.
The idea is to build a new 6.1.38 kernel, but with the 4 above mentioned
commits reverted and then boot into your new kernel and see if that resolves
the issue (too). If that's the case, then it's 1 of those 4 commits that's
causing the problem. Ideally that would be reduced to 1 specific patch, but
there isn't one that jumps out for me.

@Ben/Salvatore (=actual Debian kernel maintainers):
Did I describe it correctly? And does `test-patches` need to be run when
booted into the 6.1.38 kernel or does that not matter?
Does 1 of those 4 patches/commits stand out for you as the most likely cause?

Cheers,
  Diederik

Back to linux.debian.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Bug#1042753: nouveau: Screen remains black. Olaf Skibbe <news@kravcenko.com> - 2023-07-31 12:50 +0200
  Processed: Re: Bug#1042753: nouveau: Screen remains black. "Debian Bug Tracking System" <owner@bugs.debian.org> - 2023-07-31 13:20 +0200
  Bug#1042753: nouveau: Screen remains black. Diederik de Haas <didi.debian@cknow.org> - 2023-07-31 13:20 +0200
    Bug#1042753: nouveau: Screen remains black. Olaf Skibbe <news@kravcenko.com> - 2023-07-31 18:40 +0200
      Bug#1042753: nouveau: Screen remains black. Diederik de Haas <didi.debian@cknow.org> - 2023-07-31 20:40 +0200
        Bug#1042753: nouveau: Screen remains black. Olaf Skibbe <news@kravcenko.com> - 2023-07-31 22:00 +0200
          Bug#1042753: nouveau: Screen remains black. Diederik de Haas <didi.debian@cknow.org> - 2023-07-31 22:50 +0200
            Bug#1042753: nouveau: Screen remains black. Olaf Skibbe <news@kravcenko.com> - 2023-08-02 00:30 +0200
              Bug#1042753: nouveau: Screen remains black. Diederik de Haas <didi.debian@cknow.org> - 2023-08-02 01:20 +0200
                Bug#1042753: nouveau: Screen remains black. Olaf Skibbe <news@kravcenko.com> - 2023-08-02 18:30 +0200
                Bug#1042753: nouveau: Screen remains black. Diederik de Haas <didi.debian@cknow.org> - 2023-08-02 19:40 +0200
  Bug#1042753: nouveau bug in linux/6.1.38-2 Olaf Skibbe <news@kravcenko.com> - 2023-08-02 23:40 +0200
    Bug#1042753: nouveau bug in linux/6.1.38-2 Thorsten Leemhuis <regressions@leemhuis.info> - 2023-08-04 14:50 +0200
  Bug#1042753: nouveau bug in linux/6.1.38-2 Karol Herbst <kherbst@redhat.com> - 2023-08-04 14:30 +0200
    Bug#1042753: nouveau bug in linux/6.1.38-2 Olaf Skibbe <news@kravcenko.com> - 2023-08-04 15:00 +0200
    Bug#1042753: nouveau bug in linux/6.1.38-2 Olaf Skibbe <news@kravcenko.com> - 2023-08-04 20:20 +0200
      Bug#1042753: nouveau bug in linux/6.1.38-2 Karol Herbst <kherbst@redhat.com> - 2023-08-05 01:20 +0200
  Bug#1042753: nouveau bug in linux/6.1.38-2 Karol Herbst <kherbst@redhat.com> - 2023-08-04 15:00 +0200
  Bug#1042753: nouveau bug in linux/6.1.38-2 Diederik de Haas <didi.debian@cknow.org> - 2023-08-04 15:50 +0200
  Processed: Re: Bug#1042753: nouveau bug in linux/6.1.38-2 "Debian Bug Tracking System" <owner@bugs.debian.org> - 2023-08-05 12:50 +0200
  Bug#1042753: nouveau bug in linux/6.1.38-2 Diederik de Haas <didi.debian@cknow.org> - 2023-08-05 12:50 +0200
    Bug#1042753: nouveau bug in linux/6.1.38-2 Salvatore Bonaccorso <carnil@debian.org> - 2023-08-24 23:40 +0200
  Processed: Re: Bug#1042753: nouveau bug in linux/6.1.38-2 "Debian Bug Tracking System" <owner@bugs.debian.org> - 2023-08-24 23:40 +0200

csiph-web