From: Bjorn Helgaas <helgaas@kernel.org>
To: "Alex Xu (Hello71)" <alex_y_xu@yahoo.ca>
Cc: alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.de>,
Roy Spliet <nouveau@spliet.org>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-pm@vger.kernel.org
Subject: Re: Unrecoverable AER error when resuming from RAM (hda regression in 5.7-rc2)
Date: Wed, 22 Apr 2020 15:50:28 -0500 [thread overview]
Message-ID: <20200422205028.GA223132@google.com> (raw)
In-Reply-To: <1587494585.7pihgq0z3i.none@localhost>
[+cc Rafael, linux-pm]
On Tue, Apr 21, 2020 at 03:08:44PM -0400, Alex Xu (Hello71) wrote:
> With 5.7-rc2, after resuming from suspend to RAM, I get:
>
> [ 55.679382] pcieport 0000:00:03.1: AER: Multiple Uncorrected (Non-Fatal) error received: 0000:00:00.0
> [ 55.679405] pcieport 0000:00:03.1: AER: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
> [ 55.679410] pcieport 0000:00:03.1: AER: device [1022:1453] error status/mask=00100000/04400000
> [ 55.679414] pcieport 0000:00:03.1: AER: [20] UnsupReq (First)
> [ 55.679417] pcieport 0000:00:03.1: AER: TLP Header: 40000004 0a0000ff fffc0e80 00000000
> [ 55.679423] amdgpu 0000:0a:00.0: AER: can't recover (no error_detected callback)
> [ 55.679425] snd_hda_intel 0000:0a:00.1: AER: can't recover (no error_detected callback)
> [ 55.679455] pcieport 0000:00:03.1: AER: device recovery failed
I'm not at all confident in my decoding skills, but I *think* the TLP
header decodes to:
Fmt 010b 3 DW header with data (32-bit address)
Type 00000b MWr
Length 0x4 4 DW = 16 bytes
Requester ID 0x0a00 0a:00.0
Byte enables 0xff
Address 0xfffc0e80
which would mean the 0a:00.0 GPU did a 16-byte write to 0xfffc0e80,
and the 00:03.1 Root Port reported that as an Unsupported Request.
I don't know why that would be unless the address is invalid.
Maybe that's supposed to be an MSI address? Maybe a complete dmesg or
/proc/iomem would have a clue?
I feel like this UR issue could be a PCI core issue or maybe some sort
of misuse of PCI power management, but I can't seem to get traction on
it.
> Then the display freezes and the system basically falls apart (can't
> even sudo reboot -f, need to use magic sysrq).
>
> I bisected this to "ALSA: hda: Skip controller resume if not needed".
> Setting snd_hda_intel.power_save=0 resolves the issue.
FWIW, the complete citation is c4c8dd6ef807 ("ALSA: hda: Skip
controller resume if not needed"),
https://git.kernel.org/linus/c4c8dd6ef807, which first appeared in
v5.7-rc2.
> I am using an ASRock B450 Pro4 with Realtek HDA codec:
>
> [ 1.009400] snd_hda_intel 0000:0a:00.1: enabling device (0000 -> 0002)
> [ 1.009425] snd_hda_intel 0000:0a:00.1: Force to non-snoop mode
> [ 1.009653] snd_hda_intel 0000:0c:00.3: enabling device (0000 -> 0002)
> [ 1.021452] snd_hda_codec_generic hdaudioC0D0: ignore pin 0x7, too many assigned pins
> [ 1.021461] snd_hda_codec_generic hdaudioC0D0: ignore pin 0x9, too many assigned pins
> [ 1.021471] snd_hda_codec_generic hdaudioC0D0: ignore pin 0xb, too many assigned pins
> [ 1.021480] snd_hda_codec_generic hdaudioC0D0: ignore pin 0xd, too many assigned pins
> [ 1.021482] snd_hda_codec_generic hdaudioC0D0: autoconfig for Generic: line_outs=0 (0x0/0x0/0x0/0x0/0x0) type:line
> [ 1.021482] snd_hda_codec_generic hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
> [ 1.021483] snd_hda_codec_generic hdaudioC0D0: hp_outs=0 (0x0/0x0/0x0/0x0/0x0)
> [ 1.021484] snd_hda_codec_generic hdaudioC0D0: mono: mono_out=0x0
> [ 1.021484] snd_hda_codec_generic hdaudioC0D0: dig-out=0x3/0x5
> [ 1.021485] snd_hda_codec_generic hdaudioC0D0: inputs:
> [ 1.046053] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC892: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line
> [ 1.046054] snd_hda_codec_realtek hdaudioC1D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
> [ 1.046055] snd_hda_codec_realtek hdaudioC1D0: hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
> [ 1.046055] snd_hda_codec_realtek hdaudioC1D0: mono: mono_out=0x0
> [ 1.046056] snd_hda_codec_realtek hdaudioC1D0: inputs:
> [ 1.046057] snd_hda_codec_realtek hdaudioC1D0: Front Mic=0x19
> [ 1.046058] snd_hda_codec_realtek hdaudioC1D0: Rear Mic=0x18
> [ 1.046058] snd_hda_codec_realtek hdaudioC1D0: Line=0x1a
>
> I also have an ASUS RX 480 graphics card with HDMI audio output.
next prev parent reply other threads:[~2020-04-22 20:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1587494585.7pihgq0z3i.none.ref@localhost>
2020-04-21 19:08 ` Unrecoverable AER error when resuming from RAM (hda regression in 5.7-rc2) Alex Xu (Hello71)
2020-04-21 19:40 ` Takashi Iwai
2020-04-22 20:50 ` Bjorn Helgaas [this message]
2020-04-22 21:25 ` Takashi Iwai
2020-04-22 23:21 ` Bjorn Helgaas
2020-04-23 7:05 ` 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=20200422205028.GA223132@google.com \
--to=helgaas@kernel.org \
--cc=alex_y_xu@yahoo.ca \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nouveau@spliet.org \
--cc=rjw@rjwysocki.net \
--cc=tiwai@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).