From: Nathan Dehnel <ncdehnel@gmail.com>
To: linux-smp@vger.kernel.org, Nathan Dehnel <ncdehnel@gmail.com>
Subject: Re: Watching a video in mpv causes soft lockups
Date: Thu, 26 Aug 2021 01:55:54 -0500 [thread overview]
Message-ID: <CAEEhgEuF2G1459XsztJhL7CMDdsPmMD-CiSS_a+W=9ixTV3NhA@mail.gmail.com> (raw)
In-Reply-To: <CAEEhgEvSxK1EcPE=o1OsoYyL3+QciBnvPxUSfP+m3wW1Xt-wPg@mail.gmail.com>
Apparently it only happens when mpv is run without pulseaudio running.
On Wed, Aug 25, 2021 at 2:17 AM Nathan Dehnel <ncdehnel@gmail.com> wrote:
>
> Attached is a dmesg. uname -a:
>
> Linux guixlaptop 5.13.10 #1 SMP 1 x86_64 GNU/Linux
>
> Using the Framework laptop. lspci -k:
>
> 00:00.0 Host bridge: Intel Corporation 11th Gen Core Processor Host
> Bridge/DRAM Registers (rev 01)
> Subsystem: Device f111:0001
> lspci: Unable to load libkmod resources: error -12
> 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 01)
> Subsystem: Device f111:0001
> Kernel driver in use: i915
> 00:04.0 Signal processing controller: Intel Corporation Device 9a03 (rev 01)
> Subsystem: Device f111:0001
> Kernel driver in use: proc_thermal
> 00:06.0 PCI bridge: Intel Corporation 11th Gen Core Processor PCIe
> Controller (rev 01)
> Kernel driver in use: pcieport
> 00:07.0 PCI bridge: Intel Corporation Tiger Lake-LP Thunderbolt PCI
> Express Root Port #0 (rev 01)
> Kernel driver in use: pcieport
> 00:07.1 PCI bridge: Intel Corporation Tiger Lake-LP Thunderbolt PCI
> Express Root Port #1 (rev 01)
> Kernel driver in use: pcieport
> 00:07.2 PCI bridge: Intel Corporation Tiger Lake-LP Thunderbolt PCI
> Express Root Port #2 (rev 01)
> Kernel driver in use: pcieport
> 00:07.3 PCI bridge: Intel Corporation Tiger Lake-LP Thunderbolt PCI
> Express Root Port #3 (rev 01)
> Kernel driver in use: pcieport
> 00:08.0 System peripheral: Intel Corporation Device 9a11 (rev 01)
> Subsystem: Device f111:0001
> 00:0a.0 Signal processing controller: Intel Corporation Device 9a0d (rev 01)
> Subsystem: Device f111:0001
> Kernel driver in use: intel-pmt
> 00:0d.0 USB controller: Intel Corporation Tiger Lake-LP Thunderbolt
> USB Controller (rev 01)
> Subsystem: Device f111:0001
> Kernel driver in use: xhci_hcd
> 00:0d.2 USB controller: Intel Corporation Tiger Lake-LP Thunderbolt
> NHI #0 (rev 01)
> Subsystem: Device f111:0001
> Kernel driver in use: thunderbolt
> 00:0d.3 USB controller: Intel Corporation Tiger Lake-LP Thunderbolt
> NHI #1 (rev 01)
> Subsystem: Device f111:0001
> Kernel driver in use: thunderbolt
> 00:12.0 Serial controller: Intel Corporation Tiger Lake-LP Integrated
> Sensor Hub (rev 20)
> Subsystem: Device f111:0001
> Kernel driver in use: intel_ish_ipc
> 00:14.0 USB controller: Intel Corporation Tiger Lake-LP USB 3.2 Gen
> 2x1 xHCI Host Controller (rev 20)
> Subsystem: Device f111:0001
> Kernel driver in use: xhci_hcd
> 00:14.2 RAM memory: Intel Corporation Tiger Lake-LP Shared SRAM (rev 20)
> Subsystem: Device f111:0001
> 00:15.0 Serial bus controller [0c80]: Intel Corporation Tiger Lake-LP
> Serial IO I2C Controller #0 (rev 20)
> Subsystem: Device f111:0001
> Kernel driver in use: intel-lpss
> 00:15.1 Serial bus controller [0c80]: Intel Corporation Tiger Lake-LP
> Serial IO I2C Controller #1 (rev 20)
> Subsystem: Device f111:0001
> Kernel driver in use: intel-lpss
> 00:15.3 Serial bus controller [0c80]: Intel Corporation Tiger Lake-LP
> Serial IO I2C Controller #3 (rev 20)
> Subsystem: Device f111:0001
> Kernel driver in use: intel-lpss
> 00:16.0 Communication controller: Intel Corporation Tiger Lake-LP
> Management Engine Interface (rev 20)
> Subsystem: Device f111:0001
> 00:16.3 Serial controller: Intel Corporation Device a0e3 (rev 20)
> Subsystem: Device f111:0001
> Kernel driver in use: serial
> 00:1d.0 PCI bridge: Intel Corporation Device a0b1 (rev 20)
> Kernel driver in use: pcieport
> 00:1f.0 ISA bridge: Intel Corporation Tiger Lake-LP LPC Controller (rev 20)
> Subsystem: Device f111:0001
> 00:1f.3 Audio device: Intel Corporation Tiger Lake-LP Smart Sound
> Technology Audio Controller (rev 20)
> Subsystem: Device f111:0001
> Kernel driver in use: snd_hda_intel
> 00:1f.4 SMBus: Intel Corporation Tiger Lake-LP SMBus Controller (rev 20)
> Subsystem: Device f111:0001
> Kernel driver in use: i801_smbus
> 00:1f.5 Serial bus controller [0c80]: Intel Corporation Tiger Lake-LP
> SPI Controller (rev 20)
> Subsystem: Device f111:0001
> Kernel driver in use: intel-spi
> 01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd
> NVMe SSD Controller SM981/PM981/PM983
> Subsystem: Samsung Electronics Co Ltd Device a801
> Kernel driver in use: nvme
> aa:00.0 Network controller: Intel Corporation Device 2725 (rev 1a)
> Subsystem: Intel Corporation Device 0020
> Kernel driver in use: iwlwifi
parent reply other threads:[~2021-08-26 6:55 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAEEhgEvSxK1EcPE=o1OsoYyL3+QciBnvPxUSfP+m3wW1Xt-wPg@mail.gmail.com>]
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='CAEEhgEuF2G1459XsztJhL7CMDdsPmMD-CiSS_a+W=9ixTV3NhA@mail.gmail.com' \
--to=ncdehnel@gmail.com \
--cc=linux-smp@vger.kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).