From: Nick Hastings <nicholaschastings@gmail.com>
To: Linux regressions mailing list <regressions@lists.linux.dev>
Cc: Karol Herbst <kherbst@redhat.com>, Lyude Paul <lyude@redhat.com>,
Lukas Wunner <lukas@wunner.de>,
Salvatore Bonaccorso <carnil@debian.org>,
"1036530@bugs.debian.org" <1036530@bugs.debian.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Limonciello, Mario" <Mario.Limonciello@amd.com>
Subject: Re: Regression from "ACPI: OSI: Remove Linux-Dell-Video _OSI string"? (was: Re: Bug#1036530: linux-signed-amd64: Hard lock up of system)
Date: Tue, 27 Jun 2023 07:34:01 +0900 [thread overview]
Message-ID: <ZJoSWftrHO65wmxz@xps> (raw)
In-Reply-To: <ed5f982e-c12c-b3a2-1108-62fba50bf9db@leemhuis.info>
Hi Thorsten,
* Linux regression tracking (Thorsten Leemhuis) <regressions@leemhuis.info> [230626 21:09]:
> Hi, Thorsten here, the Linux kernel's regression tracker. Top-posting
> for once, to make this easily accessible to everyone.
>
> Nick, what's the status/was there any progress? Did you do what Mario
> suggested and file a nouveau bug?
It was not apparent that the suggestion to open "a Nouveau drm bug" was
addressed to me.
> I ask, as I still have this on my list of regressions and it seems there
> was no progress in three+ weeks now.
I have not pursued this further since as far as I could tell I already
provided all requested information and I don't actually use nouveau, so
I blacklisted it.
Regards,
Nick.
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
> --
> Everything you wanna know about Linux kernel regression tracking:
> https://linux-regtracking.leemhuis.info/about/#tldr
> If I did something stupid, please tell me, as explained on that page.
>
> #regzbot backburner: slow progress, likely just affects one machine
> #regzbot poke
>
>
> On 02.06.23 02:57, Limonciello, Mario wrote:
> > [AMD Official Use Only - General]
> >
> >> -----Original Message-----
> >> From: Nick Hastings <nicholaschastings@gmail.com>
> >> Sent: Thursday, June 1, 2023 7:02 PM
> >> To: Karol Herbst <kherbst@redhat.com>
> >> Cc: Limonciello, Mario <Mario.Limonciello@amd.com>; Lyude Paul
> >> <lyude@redhat.com>; Lukas Wunner <lukas@wunner.de>; Salvatore
> >> Bonaccorso <carnil@debian.org>; 1036530@bugs.debian.org; Rafael J.
> >> Wysocki <rafael@kernel.org>; Len Brown <lenb@kernel.org>; linux-
> >> acpi@vger.kernel.org; linux-kernel@vger.kernel.org;
> >> regressions@lists.linux.dev
> >> Subject: Re: Regression from "ACPI: OSI: Remove Linux-Dell-Video _OSI
> >> string"? (was: Re: Bug#1036530: linux-signed-amd64: Hard lock up of system)
> >>
> >> Hi,
> >>
> >> * Karol Herbst <kherbst@redhat.com> [230602 03:10]:
> >>> On Thu, Jun 1, 2023 at 7:21 PM Limonciello, Mario
> >>> <Mario.Limonciello@amd.com> wrote:
> >>>>> -----Original Message-----
> >>>>> From: Karol Herbst <kherbst@redhat.com>
> >>>>> Sent: Thursday, June 1, 2023 12:19 PM
> >>>>> To: Limonciello, Mario <Mario.Limonciello@amd.com>
> >>>>> Cc: Nick Hastings <nicholaschastings@gmail.com>; Lyude Paul
> >>>>> <lyude@redhat.com>; Lukas Wunner <lukas@wunner.de>; Salvatore
> >>>>> Bonaccorso <carnil@debian.org>; 1036530@bugs.debian.org; Rafael J.
> >>>>> Wysocki <rafael@kernel.org>; Len Brown <lenb@kernel.org>; linux-
> >>>>> acpi@vger.kernel.org; linux-kernel@vger.kernel.org;
> >>>>> regressions@lists.linux.dev
> >>>>> Subject: Re: Regression from "ACPI: OSI: Remove Linux-Dell-Video _OSI
> >>>>> string"? (was: Re: Bug#1036530: linux-signed-amd64: Hard lock up of
> >> system)
> >>>>>
> >>>>> On Thu, Jun 1, 2023 at 6:54 PM Limonciello, Mario
> >>>>> <Mario.Limonciello@amd.com> wrote:
> >>>>>>
> >>>>>> [AMD Official Use Only - General]
> >>>>>>
> >>>>>>> -----Original Message-----
> >>>>>>> From: Karol Herbst <kherbst@redhat.com>
> >>>>>>> Sent: Thursday, June 1, 2023 11:33 AM
> >>>>>>> To: Limonciello, Mario <Mario.Limonciello@amd.com>
> >>>>>>> Cc: Nick Hastings <nicholaschastings@gmail.com>; Lyude Paul
> >>>>>>> <lyude@redhat.com>; Lukas Wunner <lukas@wunner.de>; Salvatore
> >>>>>>> Bonaccorso <carnil@debian.org>; 1036530@bugs.debian.org; Rafael
> >> J.
> >>>>>>> Wysocki <rafael@kernel.org>; Len Brown <lenb@kernel.org>; linux-
> >>>>>>> acpi@vger.kernel.org; linux-kernel@vger.kernel.org;
> >>>>>>> regressions@lists.linux.dev
> >>>>>>> Subject: Re: Regression from "ACPI: OSI: Remove Linux-Dell-Video
> >> _OSI
> >>>>>>> string"? (was: Re: Bug#1036530: linux-signed-amd64: Hard lock up of
> >>>>> system)
> >>>>>>>
> >>>>>>> On Thu, Jun 1, 2023 at 6:18 PM Limonciello, Mario
> >>>>>>>>
> >>>>>>>> Lyude, Lukas, Karol
> >>>>>>>>
> >>>>>>>> This thread is in relation to this commit:
> >>>>>>>>
> >>>>>>>> 24867516f06d ("ACPI: OSI: Remove Linux-Dell-Video _OSI string")
> >>>>>>>>
> >>>>>>>> Nick has found that runtime PM is *not* working for nouveau.
> >>>>>>>>
> >>>>>>>
> >>>>>>> keep in mind we have a list of PCIe controllers where we apply a
> >>>>>>> workaround:
> >>>>>>>
> >>>>>
> >> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers
> >>>>>>> /gpu/drm/nouveau/nouveau_drm.c?h=v6.4-rc4#n682
> >>>>>>>
> >>>>>>> And I suspect there might be one or two more IDs we'll have to add
> >>>>>>> there. Do we have any logs?
> >>>>>>
> >>>>>> There's some archived onto the distro bug. Search this page for
> >>>>> "journalctl.log.gz"
> >>>>>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036530
> >>>>>>
> >>>>>
> >>>>> interesting.. It seems to be the same controller used here. I wonder
> >>>>> if the pci topology is different or if the workaround is applied at
> >>>>> all.
> >>>>
> >>>> I didn't see the message in the log about the workaround being applied
> >>>> in that log, so I guess PCI topology difference is a likely suspect.
> >>>>
> >>>
> >>> yeah, but I also couldn't see a log with the usual nouveau messages,
> >>> so it's kinda weird.
> >>>
> >>> Anyway, the output of `lspci -tvnn` would help
> >>
> >> % lspci -tvnn
> >> -[0000:00]-+-00.0 Intel Corporation Device [8086:3e20]
> >> +-01.0-[01]----00.0 NVIDIA Corporation TU117M [GeForce GTX 1650
> >> Mobile / Max-Q] [10de:1f91]
> >
> > So the bridge it's connected to is the same that the quirk *should have been* triggering.
> >
> > May 29 15:02:42 xps kernel: pci 0000:00:01.0: [8086:1901] type 01 class 0x060400
> >
> > Since the quirk isn't working and this is still a problem in 6.4-rc4 I suggest opening a
> > Nouveau drm bug to figure out why.
> >
> >> +-02.0 Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630]
> >> [8086:3e9b]
> >> +-04.0 Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core
> >> Processor Thermal Subsystem [8086:1903]
> >> +-08.0 Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 /
> >> 6th/7th/8th Gen Core Processor Gaussian Mixture Model [8086:1911]
> >> +-12.0 Intel Corporation Cannon Lake PCH Thermal Controller
> >> [8086:a379]
> >> +-14.0 Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller
> >> [8086:a36d]
> >> +-14.2 Intel Corporation Cannon Lake PCH Shared SRAM [8086:a36f]
> >> +-15.0 Intel Corporation Cannon Lake PCH Serial IO I2C Controller #0
> >> [8086:a368]
> >> +-15.1 Intel Corporation Cannon Lake PCH Serial IO I2C Controller #1
> >> [8086:a369]
> >> +-16.0 Intel Corporation Cannon Lake PCH HECI Controller [8086:a360]
> >> +-17.0 Intel Corporation Cannon Lake Mobile PCH SATA AHCI Controller
> >> [8086:a353]
> >> +-1b.0-[02-3a]----00.0-[03-3a]--+-00.0-[04]----00.0 Intel Corporation
> >> JHL6340 Thunderbolt 3 NHI (C step) [Alpine Ridge 2C 2016] [8086:15d9]
> >> | +-01.0-[05-39]--
> >> | \-02.0-[3a]----00.0 Intel Corporation JHL6340
> >> Thunderbolt 3 USB 3.1 Controller (C step) [Alpine Ridge 2C 2016]
> >> [8086:15db]
> >> +-1c.0-[3b]----00.0 Intel Corporation Wi-Fi 6 AX200 [8086:2723]
> >> +-1c.4-[3c]----00.0 Realtek Semiconductor Co., Ltd. RTS525A PCI
> >> Express Card Reader [10ec:525a]
> >> +-1d.0-[3d]----00.0 Samsung Electronics Co Ltd NVMe SSD Controller
> >> SM981/PM981/PM983 [144d:a808]
> >> +-1f.0 Intel Corporation Cannon Lake LPC Controller [8086:a30e]
> >> +-1f.3 Intel Corporation Cannon Lake PCH cAVS [8086:a348]
> >> +-1f.4 Intel Corporation Cannon Lake PCH SMBus Controller
> >> [8086:a323]
> >> \-1f.5 Intel Corporation Cannon Lake PCH SPI Controller
> >> [8086:a324]
> >>
> >>
> >> Regards,
> >>
> >> Nick.
> >
next prev parent reply other threads:[~2023-06-26 22:34 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <168471337231.1913606.15905047692536779158.reportbug@xps>
[not found] ` <ZG3mbc3zdR4KcUW/@eldamar.lan>
[not found] ` <ZG6cY8xjfob4Bvcs@xps>
[not found] ` <ZG98fQ+MD4O0nGGE@eldamar.lan>
[not found] ` <ZG/8cxxTJ9ZzrVPQ@xps>
[not found] ` <ZHCYRmD7YeIWoy2W@eldamar.lan>
[not found] ` <ZHKrC4/G6ZyvRReI@xps>
2023-05-28 6:49 ` Regression from "ACPI: OSI: Remove Linux-Dell-Video _OSI string"? (was: Re: Bug#1036530: linux-signed-amd64: Hard lock up of system) Salvatore Bonaccorso
2023-05-28 12:44 ` Mario Limonciello
2023-05-29 0:56 ` Nick Hastings
2023-05-29 1:14 ` Mario Limonciello
2023-05-29 3:51 ` Nick Hastings
2023-05-29 23:01 ` Nick Hastings
2023-05-30 4:00 ` Mario Limonciello
2023-05-30 7:01 ` Nick Hastings
2023-05-30 11:22 ` Bug#1036530: " Salvatore Bonaccorso
2023-05-31 23:40 ` Nick Hastings
2023-06-01 16:18 ` Limonciello, Mario
2023-06-01 16:33 ` Karol Herbst
2023-06-01 16:54 ` Limonciello, Mario
2023-06-01 17:18 ` Karol Herbst
2023-06-01 17:21 ` Limonciello, Mario
2023-06-01 18:10 ` Karol Herbst
2023-06-02 0:01 ` Nick Hastings
2023-06-02 0:57 ` Limonciello, Mario
2023-06-26 12:09 ` Linux regression tracking (Thorsten Leemhuis)
2023-06-26 12:36 ` Bug#1036530: Info received (Regression from "ACPI: OSI: Remove Linux-Dell-Video _OSI string"? (was: Re: Bug#1036530: linux-signed-amd64: Hard lock up of system)) Debian Bug Tracking System
2023-06-26 22:34 ` Nick Hastings [this message]
2023-06-30 13:02 ` Regression from "ACPI: OSI: Remove Linux-Dell-Video _OSI string"? (was: Re: Bug#1036530: linux-signed-amd64: Hard lock up of system) Thorsten Leemhuis
2023-06-30 13:09 ` Karol Herbst
2023-06-30 21:38 ` Nick Hastings
2023-06-30 21:40 ` Limonciello, Mario
2023-06-30 22:12 ` Nick Hastings
2023-06-01 23:55 ` Nick Hastings
2023-07-07 21:54 ` Lyude Paul
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=ZJoSWftrHO65wmxz@xps \
--to=nicholaschastings@gmail.com \
--cc=1036530@bugs.debian.org \
--cc=Mario.Limonciello@amd.com \
--cc=carnil@debian.org \
--cc=kherbst@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=lyude@redhat.com \
--cc=rafael@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.