On Wed, 17 December 2014 Bjorn Helgaas <bhelgaas@xxxxxxxxxx> wrote: > [+cc Petri] > > On Mon, Oct 13, 2014 at 9:47 AM, Bjorn Helgaas <bhelgaas@xxxxxxxxxx> wrote: > > On Sun, Oct 12, 2014 at 8:55 AM, <bugzilla-daemon@xxxxxxxxxxxxxxxxxxx> wrote: > >> https://bugzilla.kernel.org/show_bug.cgi?id=86121 > >> > >> Bug ID: 86121 > >> Summary: Regression: NVIDIA backlight not working after latest > >> vgaarb change > >> Product: Drivers > >> Version: 2.5 > >> Kernel Version: 3.16.5 > >> Hardware: x86-64 > >> OS: Linux > >> Tree: Mainline > >> Status: NEW > >> Severity: normal > >> Priority: P1 > >> Component: PCI > >> Assignee: drivers_pci@xxxxxxxxxxxxxxxxxxxx > >> Reporter: petrihodju@xxxxxxxxx > >> Regression: No > >> > >> Created attachment 153311 > >> --> https://bugzilla.kernel.org/attachment.cgi?id=153311&action=edit > >> kernel boot logs & config > >> > >> I have experienced a regression in backlight control with NVIDIA binary blob > >> driver and kernel 3.16.5. I did a bisect between 3.16.4 and 3.16.5 and found > >> out that the regression happens with commit "ce027dac vgaarb: Don't default > >> exclusively to first video device with mem+io" > >> > >> I have attached kernel boot log with working backlight (commit 7babfd7f) and > >> non-working one (commit ce027dac) plus the config used. > >> > >> I'm running Ubuntu 14.10 > > Ping for status update? There are some more comments in the bugzilla, > but the most recent one is from Oct 25. > > This is a regression, so I'd like to make some progress on it. I'm hoping for more details on how it triggers, e.g. if "BIOS"-configured boot GPU has some effect or when it starts failing (e.g. with/without proprietary nvidia driver, or versus nouveau). >From ACPI code there is nothing that catches my attention tough. On the other hand, for Apple systems GPU switching should probably not include any kind of VGA arbitration switching as VGA is not used at all there... Bruno -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
