From: Nick Hastings <nicholaschastings@gmail.com>
To: "Limonciello, Mario" <mario.limonciello@amd.com>
Cc: Lyude Paul <lyude@redhat.com>, Lukas Wunner <lukas@wunner.de>,
kherbst@redhat.com, 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)
Date: Fri, 2 Jun 2023 08:55:11 +0900 [thread overview]
Message-ID: <ZHkv32h2F/AYmIqk@xps> (raw)
In-Reply-To: <fe0ab1fa-6ed6-dc64-8165-8fc70669317b@amd.com>
Hi,
* Limonciello, Mario <mario.limonciello@amd.com> [230602 01:18]:
> +Lyude, Lukas, Karol
>
> On 5/31/2023 6:40 PM, Nick Hastings wrote:
> >
> > * Nick Hastings <nicholaschastings@gmail.com> [230530 16:01]:
> > > * Mario Limonciello <mario.limonciello@amd.com> [230530 13:00]:
> > <snip>
> > > > As you're actually loading nouveau, can you please try nouveau.runpm=0 on
> > > > the kernel command line?
> > > I'm not intentionally loading it. This machine also has intel graphics
> > > which is what I prefer. Checking my
> > > /etc/modprobe.d/blacklist-nvidia-nouveau.conf
> > > I see:
> > >
> > > blacklist nvidia
> > > blacklist nvidia-drm
> > > blacklist nvidia-modeset
> > > blacklist nvidia-uvm
> > > blacklist ipmi_msghandler
> > > blacklist ipmi_devintf
> > >
> > > So I thought I had blacklisted it but it seems I did not. Since I do not
> > > want to use it maybe it is better to check if the lock up occurs with
> > > nouveau blacklisted. I will try that now.
> > I blacklisted nouveau and booted into a 6.1 kernel:
> > % uname -a
> > Linux xps 6.1.0-9-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.27-1 (2023-05-08) x86_64 GNU/Linux
> >
> > It has been running without problems for nearly two days now:
> > % uptime
> > 08:34:48 up 1 day, 16:22, 2 users, load average: 1.33, 1.26, 1.27
> >
> > Regards,
> >
> > Nick.
>
> Thanks, that makes a lot more sense now.
>
> Nick, Can you please test if nouveau works with runtime PM in the
> latest 6.4-rc?
I reported this twice already. I guess it was lost since for some
reason emails in this thread are not being trimmed. I'll repeat here:
I did eventually see a lockup of this kernel. On the console I saw:
[ 151.035036] vfio-pci 0000:01:00.0 Unable to change power state from D3cold to D0, device inaccessible
I did not see the other two lines that were present in earlier lock ups.
Regards,
Nick.
next prev parent reply other threads:[~2023-06-01 23:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[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] ` <168471337231.1913606.15905047692536779158.reportbug@xps>
[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
[not found] ` <ZHP4IqxBUPuVRvRV@xps>
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 22:34 ` Nick Hastings
2023-06-30 13:02 ` 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 [this message]
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=ZHkv32h2F/AYmIqk@xps \
--to=nicholaschastings@gmail.com \
--cc=1036530@bugs.debian.org \
--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=mario.limonciello@amd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox