All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Takashi Iwai <tiwai@suse.de>,
	linux-kernel@vger.kernel.org, regressions@lists.linux.dev,
	dri-devel@lists.freedesktop.org
Subject: Re: [REGRESSION] Missing nouveau backlight control on 6.2.x kernel
Date: Sun, 19 Mar 2023 08:34:55 +0100	[thread overview]
Message-ID: <87ttyhmbxc.wl-tiwai@suse.de> (raw)
In-Reply-To: <09d1ba06-a034-165d-2f7d-fba7d379e026@redhat.com>

On Sat, 18 Mar 2023 17:49:28 +0100,
Hans de Goede wrote:
> 
> Hi Takashi,
> 
> On 3/17/23 11:04, Takashi Iwai wrote:
> > Hi,
> > 
> > we've received a regression report on openSUSE Bugzilla about the
> > missing backlight control of nouveau device:
> >   https://bugzilla.opensuse.org/show_bug.cgi?id=1209296
> > 
> > On 6.1, with acpi_video=native option, the system provided
> > /sys/class/backlight/nv_backlight entry.
> > 
> > On 6.2, with acpi_video=native option, there is no entry in
> > /sys/class/backlight.  And without acpi_video option, it falls back to
> > /sys/class/backlight/acpi_video0, which doesn't work as expected.
> > 
> > Hans, could you check whether the recent change in video_detect.c (or
> > anything else) may influence on this?  My gut feeling is that the
> > culprit could be rather some change in nouveau (so dri-devel is
> > Cc'ed), but I'm not entirely sure...
> 
> As I already told the reporter, who first contacted me by private email about this, all the drivers/acpi/video_detect.c changes which may influence this are also present in 6.1.y (IIRC >= 6.1.5) . So since this is being reported as only happening with 6.2.y I don't think the recent backlight detect rework is involved.
> 
> And even if the recent backlight detect rework were involved, specifying acpi_backlight=native on the kernel commandline (as the reporter was doing before) should still work since it overrides all other backlight detection.
> 
> So yes this seems to be a nouveau bug and should probably be reported following the instructions from: https://nouveau.freedesktop.org/Bugs.html  (which I havealso told the reporter already).

Thanks for verification!


Takashi

WARNING: multiple messages have this Message-ID (diff)
From: Takashi Iwai <tiwai@suse.de>
To: Hans de Goede <hdegoede@redhat.com>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	regressions@lists.linux.dev
Subject: Re: [REGRESSION] Missing nouveau backlight control on 6.2.x kernel
Date: Sun, 19 Mar 2023 08:34:55 +0100	[thread overview]
Message-ID: <87ttyhmbxc.wl-tiwai@suse.de> (raw)
In-Reply-To: <09d1ba06-a034-165d-2f7d-fba7d379e026@redhat.com>

On Sat, 18 Mar 2023 17:49:28 +0100,
Hans de Goede wrote:
> 
> Hi Takashi,
> 
> On 3/17/23 11:04, Takashi Iwai wrote:
> > Hi,
> > 
> > we've received a regression report on openSUSE Bugzilla about the
> > missing backlight control of nouveau device:
> >   https://bugzilla.opensuse.org/show_bug.cgi?id=1209296
> > 
> > On 6.1, with acpi_video=native option, the system provided
> > /sys/class/backlight/nv_backlight entry.
> > 
> > On 6.2, with acpi_video=native option, there is no entry in
> > /sys/class/backlight.  And without acpi_video option, it falls back to
> > /sys/class/backlight/acpi_video0, which doesn't work as expected.
> > 
> > Hans, could you check whether the recent change in video_detect.c (or
> > anything else) may influence on this?  My gut feeling is that the
> > culprit could be rather some change in nouveau (so dri-devel is
> > Cc'ed), but I'm not entirely sure...
> 
> As I already told the reporter, who first contacted me by private email about this, all the drivers/acpi/video_detect.c changes which may influence this are also present in 6.1.y (IIRC >= 6.1.5) . So since this is being reported as only happening with 6.2.y I don't think the recent backlight detect rework is involved.
> 
> And even if the recent backlight detect rework were involved, specifying acpi_backlight=native on the kernel commandline (as the reporter was doing before) should still work since it overrides all other backlight detection.
> 
> So yes this seems to be a nouveau bug and should probably be reported following the instructions from: https://nouveau.freedesktop.org/Bugs.html  (which I havealso told the reporter already).

Thanks for verification!


Takashi

  reply	other threads:[~2023-03-19  7:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-17 10:04 [REGRESSION] Missing nouveau backlight control on 6.2.x kernel Takashi Iwai
2023-03-17 10:04 ` Takashi Iwai
2023-03-18 16:49 ` Hans de Goede
2023-03-18 16:49   ` Hans de Goede
2023-03-19  7:34   ` Takashi Iwai [this message]
2023-03-19  7:34     ` Takashi Iwai

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=87ttyhmbxc.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hdegoede@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.