Re: [Intel-gfx] snd_hda_intel 0000:00:1f.3: No response from codec, resetting bus: last cmd=

2019-11-19 Thread Paul Menzel
Dear Tomáš,


On 2019-11-04 18:31, Tomas Janousek wrote:

> On Mon, Nov 04, 2019 at 01:57:54PM +0100, Paul Menzel wrote:
>> On the Dell XPS 13 9380 with Debian Sid/unstable with Linux 5.3.7
>> resuming0with Dell’s Thunderbolt TB16 dock connected, Linux spews
>> the errors below.
>>
>> ```
>> [0.00] Linux version 5.3.0-1-amd64 (debian-ker...@lists.debian.org) 
>> (gcc version 9.2.1 20191008 (Debian 9.2.1-9)) #1 SMP Debian 5.3.7-1 
>> (2019-10-19)
>> […]
>> [1.596619] pci :00:1f.3: Adding to iommu group 12
>> [   14.536274] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
>> [   14.544100] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
>> i915_audio_component_bind_ops [i915])
>> [   14.760751] input: HDA Intel PCH Headphone Mic as 
>> /devices/pci:00/:00:1f.3/sound/card0/input16
>> [   14.760790] input: HDA Intel PCH HDMI as 
>> /devices/pci:00/:00:1f.3/sound/card0/input17
>> [  156.614284] snd_hda_intel :00:1f.3: No response from codec, disabling 
>> MSI: last cmd=0x20270503
>> [  157.622232] snd_hda_intel :00:1f.3: No response from codec, resetting 
>> bus: last cmd=0x20270503
>> [  158.626371] snd_hda_intel :00:1f.3: No response from codec, resetting 
>> bus: last cmd=0x20370503
>> [  159.634102] snd_hda_intel :00:1f.3: No response from codec, resetting 
>> bus: last cmd=0x201f0500
>> [  161.678121] snd_hda_intel :00:1f.3: No response from codec, resetting 
>> bus: last cmd=0x20270503
>> [  162.682272] snd_hda_intel :00:1f.3: No response from codec, resetting 
>> bus: last cmd=0x20370503
>> [  163.694234] snd_hda_intel :00:1f.3: No response from codec, resetting 
>> bus: last cmd=0x201f0500
>> [  165.730142] snd_hda_intel :00:1f.3: No response from codec, resetting 
>> bus: last cmd=0x20270503
>> […]
>> ```
> 
> Debian's 5.3.0-1-amd64 has a corrupted signature on the snd-hda-codec-hdmi
> module which prevents the module from loading and causes these errors. Further
> details here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942881
> 
> Workaround: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942881#20

Thank you so much for pointing me to that bug report. The problem is now fixed
in linux-image 5.3.9-1.

Takashi, could a sanity check be added to `snd_hda_intel` to see if the codec
module is loaded?


Kind regards,

Paul



smime.p7s
Description: S/MIME Cryptographic Signature
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] snd_hda_intel 0000:00:1f.3: No response from codec, resetting bus: last cmd=

2019-11-04 Thread Tomas Janousek
Hi Paul,

On Mon, Nov 04, 2019 at 01:57:54PM +0100, Paul Menzel wrote:
> On the Dell XPS 13 9380 with Debian Sid/unstable with Linux 5.3.7
> resuming0with Dell’s Thunderbolt TB16 dock connected, Linux spews
> the errors below.
> 
> ```
> [0.00] Linux version 5.3.0-1-amd64 (debian-ker...@lists.debian.org) 
> (gcc version 9.2.1 20191008 (Debian 9.2.1-9)) #1 SMP Debian 5.3.7-1 
> (2019-10-19)
> […]
> [1.596619] pci :00:1f.3: Adding to iommu group 12
> [   14.536274] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
> [   14.544100] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
> i915_audio_component_bind_ops [i915])
> [   14.760751] input: HDA Intel PCH Headphone Mic as 
> /devices/pci:00/:00:1f.3/sound/card0/input16
> [   14.760790] input: HDA Intel PCH HDMI as 
> /devices/pci:00/:00:1f.3/sound/card0/input17
> [  156.614284] snd_hda_intel :00:1f.3: No response from codec, disabling 
> MSI: last cmd=0x20270503
> [  157.622232] snd_hda_intel :00:1f.3: No response from codec, resetting 
> bus: last cmd=0x20270503
> [  158.626371] snd_hda_intel :00:1f.3: No response from codec, resetting 
> bus: last cmd=0x20370503
> [  159.634102] snd_hda_intel :00:1f.3: No response from codec, resetting 
> bus: last cmd=0x201f0500
> [  161.678121] snd_hda_intel :00:1f.3: No response from codec, resetting 
> bus: last cmd=0x20270503
> [  162.682272] snd_hda_intel :00:1f.3: No response from codec, resetting 
> bus: last cmd=0x20370503
> [  163.694234] snd_hda_intel :00:1f.3: No response from codec, resetting 
> bus: last cmd=0x201f0500
> [  165.730142] snd_hda_intel :00:1f.3: No response from codec, resetting 
> bus: last cmd=0x20270503
> […]
> ```

Debian's 5.3.0-1-amd64 has a corrupted signature on the snd-hda-codec-hdmi
module which prevents the module from loading and causes these errors. Further
details here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942881

Workaround: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942881#20

-- 
Tomáš Janoušek, a.k.a. Pivník, a.k.a. Liskni_si, http://work.lisk.in/
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] snd_hda_intel 0000:00:1f.3: No response from codec, resetting bus: last cmd=

2019-11-04 Thread Takashi Iwai
On Mon, 04 Nov 2019 15:58:25 +0100,
Mika Westerberg wrote:
> 
> On Mon, Nov 04, 2019 at 02:19:21PM +0100, Takashi Iwai wrote:
> > On Mon, 04 Nov 2019 14:10:24 +0100,
> > Mika Westerberg wrote:
> > > 
> > > Hi,
> > > 
> > > On Mon, Nov 04, 2019 at 01:57:54PM +0100, Paul Menzel wrote:
> > > > Dear Linux folks,
> > > > 
> > > > 
> > > > On the Dell XPS 13 9380 with Debian Sid/unstable with Linux 5.3.7
> > > > resuming0with Dell’s Thunderbolt TB16 dock connected, Linux spews
> > > > the errors below.
> > > 
> > > I have this machine here so can try to reproduce it as well.
> > > 
> > > > ```
> > > > [0.00] Linux version 5.3.0-1-amd64 
> > > > (debian-ker...@lists.debian.org) (gcc version 9.2.1 20191008 (Debian 
> > > > 9.2.1-9)) #1 SMP Debian 5.3.7-1 (2019-10-19)
> > > > […]
> > > > [1.596619] pci :00:1f.3: Adding to iommu group 12
> > > > [   14.536274] snd_hda_intel :00:1f.3: enabling device ( -> 
> > > > 0002)
> > > > [   14.544100] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
> > > > i915_audio_component_bind_ops [i915])
> > > > [   14.760751] input: HDA Intel PCH Headphone Mic as 
> > > > /devices/pci:00/:00:1f.3/sound/card0/input16
> > > > [   14.760790] input: HDA Intel PCH HDMI as 
> > > > /devices/pci:00/:00:1f.3/sound/card0/input17
> > > > [  156.614284] snd_hda_intel :00:1f.3: No response from codec, 
> > > > disabling MSI: last cmd=0x20270503
> > > > [  157.622232] snd_hda_intel :00:1f.3: No response from codec, 
> > > > resetting bus: last cmd=0x20270503
> > > > [  158.626371] snd_hda_intel :00:1f.3: No response from codec, 
> > > > resetting bus: last cmd=0x20370503
> > > > [  159.634102] snd_hda_intel :00:1f.3: No response from codec, 
> > > > resetting bus: last cmd=0x201f0500
> > > > [  161.678121] snd_hda_intel :00:1f.3: No response from codec, 
> > > > resetting bus: last cmd=0x20270503
> > > > [  162.682272] snd_hda_intel :00:1f.3: No response from codec, 
> > > > resetting bus: last cmd=0x20370503
> > > > [  163.694234] snd_hda_intel :00:1f.3: No response from codec, 
> > > > resetting bus: last cmd=0x201f0500
> > > > [  165.730142] snd_hda_intel :00:1f.3: No response from codec, 
> > > > resetting bus: last cmd=0x20270503
> > > > […]
> > > > ```
> > > > 
> > > > In the bug report *[Intel Ice Lake, snd-hda-intel, HDMI] "No
> > > > response from codec" (after display hotplug?)* [1], note it’s a
> > > > different model, Takashi comments that this is a Thunderbolt or
> > > > i915 issue.
> > > 
> > > :00:1f.3 is on PCH so not sure how it could be related to
> > > Thunderbolt, well or i915 for that matter.
> > 
> > It's the HD-audio controller PCI device and both HDMI and onboard
> > codecs are on that bus.  HDMI codec a shadow device of GPU, so it has
> > a strong dependency on i915 GPU driver.  The power of HD-audio bus and
> > codec is controlled over DRM audio component ops, so the power-on must
> > have been notified to GPU side, but still something seems missing.
> > ANd, with the dock, the other parties come to play into the game, so
> > it becomes more complex...
> 
> OK, thanks for explaining. Then I guess i915 may be related. However,
> that traffic for sure does not go over Thunderbolt fabric (PCIe and DP
> does).

Well, here HDMI codec I meant is for both HDMI and DP.  Its audio
device is common for both display types.


thanks,

Takashi
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] snd_hda_intel 0000:00:1f.3: No response from codec, resetting bus: last cmd=

2019-11-04 Thread Mika Westerberg
On Mon, Nov 04, 2019 at 02:19:21PM +0100, Takashi Iwai wrote:
> On Mon, 04 Nov 2019 14:10:24 +0100,
> Mika Westerberg wrote:
> > 
> > Hi,
> > 
> > On Mon, Nov 04, 2019 at 01:57:54PM +0100, Paul Menzel wrote:
> > > Dear Linux folks,
> > > 
> > > 
> > > On the Dell XPS 13 9380 with Debian Sid/unstable with Linux 5.3.7
> > > resuming0with Dell’s Thunderbolt TB16 dock connected, Linux spews
> > > the errors below.
> > 
> > I have this machine here so can try to reproduce it as well.
> > 
> > > ```
> > > [0.00] Linux version 5.3.0-1-amd64 
> > > (debian-ker...@lists.debian.org) (gcc version 9.2.1 20191008 (Debian 
> > > 9.2.1-9)) #1 SMP Debian 5.3.7-1 (2019-10-19)
> > > […]
> > > [1.596619] pci :00:1f.3: Adding to iommu group 12
> > > [   14.536274] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
> > > [   14.544100] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
> > > i915_audio_component_bind_ops [i915])
> > > [   14.760751] input: HDA Intel PCH Headphone Mic as 
> > > /devices/pci:00/:00:1f.3/sound/card0/input16
> > > [   14.760790] input: HDA Intel PCH HDMI as 
> > > /devices/pci:00/:00:1f.3/sound/card0/input17
> > > [  156.614284] snd_hda_intel :00:1f.3: No response from codec, 
> > > disabling MSI: last cmd=0x20270503
> > > [  157.622232] snd_hda_intel :00:1f.3: No response from codec, 
> > > resetting bus: last cmd=0x20270503
> > > [  158.626371] snd_hda_intel :00:1f.3: No response from codec, 
> > > resetting bus: last cmd=0x20370503
> > > [  159.634102] snd_hda_intel :00:1f.3: No response from codec, 
> > > resetting bus: last cmd=0x201f0500
> > > [  161.678121] snd_hda_intel :00:1f.3: No response from codec, 
> > > resetting bus: last cmd=0x20270503
> > > [  162.682272] snd_hda_intel :00:1f.3: No response from codec, 
> > > resetting bus: last cmd=0x20370503
> > > [  163.694234] snd_hda_intel :00:1f.3: No response from codec, 
> > > resetting bus: last cmd=0x201f0500
> > > [  165.730142] snd_hda_intel :00:1f.3: No response from codec, 
> > > resetting bus: last cmd=0x20270503
> > > […]
> > > ```
> > > 
> > > In the bug report *[Intel Ice Lake, snd-hda-intel, HDMI] "No
> > > response from codec" (after display hotplug?)* [1], note it’s a
> > > different model, Takashi comments that this is a Thunderbolt or
> > > i915 issue.
> > 
> > :00:1f.3 is on PCH so not sure how it could be related to
> > Thunderbolt, well or i915 for that matter.
> 
> It's the HD-audio controller PCI device and both HDMI and onboard
> codecs are on that bus.  HDMI codec a shadow device of GPU, so it has
> a strong dependency on i915 GPU driver.  The power of HD-audio bus and
> codec is controlled over DRM audio component ops, so the power-on must
> have been notified to GPU side, but still something seems missing.
> ANd, with the dock, the other parties come to play into the game, so
> it becomes more complex...

OK, thanks for explaining. Then I guess i915 may be related. However,
that traffic for sure does not go over Thunderbolt fabric (PCIe and DP
does).
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] snd_hda_intel 0000:00:1f.3: No response from codec, resetting bus: last cmd=

2019-11-04 Thread Takashi Iwai
On Mon, 04 Nov 2019 14:10:24 +0100,
Mika Westerberg wrote:
> 
> Hi,
> 
> On Mon, Nov 04, 2019 at 01:57:54PM +0100, Paul Menzel wrote:
> > Dear Linux folks,
> > 
> > 
> > On the Dell XPS 13 9380 with Debian Sid/unstable with Linux 5.3.7
> > resuming0with Dell’s Thunderbolt TB16 dock connected, Linux spews
> > the errors below.
> 
> I have this machine here so can try to reproduce it as well.
> 
> > ```
> > [0.00] Linux version 5.3.0-1-amd64 (debian-ker...@lists.debian.org) 
> > (gcc version 9.2.1 20191008 (Debian 9.2.1-9)) #1 SMP Debian 5.3.7-1 
> > (2019-10-19)
> > […]
> > [1.596619] pci :00:1f.3: Adding to iommu group 12
> > [   14.536274] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
> > [   14.544100] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
> > i915_audio_component_bind_ops [i915])
> > [   14.760751] input: HDA Intel PCH Headphone Mic as 
> > /devices/pci:00/:00:1f.3/sound/card0/input16
> > [   14.760790] input: HDA Intel PCH HDMI as 
> > /devices/pci:00/:00:1f.3/sound/card0/input17
> > [  156.614284] snd_hda_intel :00:1f.3: No response from codec, 
> > disabling MSI: last cmd=0x20270503
> > [  157.622232] snd_hda_intel :00:1f.3: No response from codec, 
> > resetting bus: last cmd=0x20270503
> > [  158.626371] snd_hda_intel :00:1f.3: No response from codec, 
> > resetting bus: last cmd=0x20370503
> > [  159.634102] snd_hda_intel :00:1f.3: No response from codec, 
> > resetting bus: last cmd=0x201f0500
> > [  161.678121] snd_hda_intel :00:1f.3: No response from codec, 
> > resetting bus: last cmd=0x20270503
> > [  162.682272] snd_hda_intel :00:1f.3: No response from codec, 
> > resetting bus: last cmd=0x20370503
> > [  163.694234] snd_hda_intel :00:1f.3: No response from codec, 
> > resetting bus: last cmd=0x201f0500
> > [  165.730142] snd_hda_intel :00:1f.3: No response from codec, 
> > resetting bus: last cmd=0x20270503
> > […]
> > ```
> > 
> > In the bug report *[Intel Ice Lake, snd-hda-intel, HDMI] "No
> > response from codec" (after display hotplug?)* [1], note it’s a
> > different model, Takashi comments that this is a Thunderbolt or
> > i915 issue.
> 
> :00:1f.3 is on PCH so not sure how it could be related to
> Thunderbolt, well or i915 for that matter.

It's the HD-audio controller PCI device and both HDMI and onboard
codecs are on that bus.  HDMI codec a shadow device of GPU, so it has
a strong dependency on i915 GPU driver.  The power of HD-audio bus and
codec is controlled over DRM audio component ops, so the power-on must
have been notified to GPU side, but still something seems missing.
ANd, with the dock, the other parties come to play into the game, so
it becomes more complex...


thanks,

Takashi
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] snd_hda_intel 0000:00:1f.3: No response from codec, resetting bus: last cmd=

2019-11-04 Thread Mika Westerberg
Hi,

On Mon, Nov 04, 2019 at 01:57:54PM +0100, Paul Menzel wrote:
> Dear Linux folks,
> 
> 
> On the Dell XPS 13 9380 with Debian Sid/unstable with Linux 5.3.7
> resuming0with Dell’s Thunderbolt TB16 dock connected, Linux spews
> the errors below.

I have this machine here so can try to reproduce it as well.

> ```
> [0.00] Linux version 5.3.0-1-amd64 (debian-ker...@lists.debian.org) 
> (gcc version 9.2.1 20191008 (Debian 9.2.1-9)) #1 SMP Debian 5.3.7-1 
> (2019-10-19)
> […]
> [1.596619] pci :00:1f.3: Adding to iommu group 12
> [   14.536274] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
> [   14.544100] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
> i915_audio_component_bind_ops [i915])
> [   14.760751] input: HDA Intel PCH Headphone Mic as 
> /devices/pci:00/:00:1f.3/sound/card0/input16
> [   14.760790] input: HDA Intel PCH HDMI as 
> /devices/pci:00/:00:1f.3/sound/card0/input17
> [  156.614284] snd_hda_intel :00:1f.3: No response from codec, disabling 
> MSI: last cmd=0x20270503
> [  157.622232] snd_hda_intel :00:1f.3: No response from codec, resetting 
> bus: last cmd=0x20270503
> [  158.626371] snd_hda_intel :00:1f.3: No response from codec, resetting 
> bus: last cmd=0x20370503
> [  159.634102] snd_hda_intel :00:1f.3: No response from codec, resetting 
> bus: last cmd=0x201f0500
> [  161.678121] snd_hda_intel :00:1f.3: No response from codec, resetting 
> bus: last cmd=0x20270503
> [  162.682272] snd_hda_intel :00:1f.3: No response from codec, resetting 
> bus: last cmd=0x20370503
> [  163.694234] snd_hda_intel :00:1f.3: No response from codec, resetting 
> bus: last cmd=0x201f0500
> [  165.730142] snd_hda_intel :00:1f.3: No response from codec, resetting 
> bus: last cmd=0x20270503
> […]
> ```
> 
> In the bug report *[Intel Ice Lake, snd-hda-intel, HDMI] "No
> response from codec" (after display hotplug?)* [1], note it’s a
> different model, Takashi comments that this is a Thunderbolt or
> i915 issue.

:00:1f.3 is on PCH so not sure how it could be related to
Thunderbolt, well or i915 for that matter.

> Please tell me, how to debug this further.

Unfortunately I don't know much about the HDA driver so can't really
suggest anything.
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

[Intel-gfx] snd_hda_intel 0000:00:1f.3: No response from codec, resetting bus: last cmd=

2019-11-04 Thread Paul Menzel
Dear Linux folks,


On the Dell XPS 13 9380 with Debian Sid/unstable with Linux 5.3.7
resuming0with Dell’s Thunderbolt TB16 dock connected, Linux spews
the errors below.

```
[0.00] Linux version 5.3.0-1-amd64 (debian-ker...@lists.debian.org) 
(gcc version 9.2.1 20191008 (Debian 9.2.1-9)) #1 SMP Debian 5.3.7-1 (2019-10-19)
[…]
[1.596619] pci :00:1f.3: Adding to iommu group 12
[   14.536274] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
[   14.544100] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[   14.760751] input: HDA Intel PCH Headphone Mic as 
/devices/pci:00/:00:1f.3/sound/card0/input16
[   14.760790] input: HDA Intel PCH HDMI as 
/devices/pci:00/:00:1f.3/sound/card0/input17
[  156.614284] snd_hda_intel :00:1f.3: No response from codec, disabling 
MSI: last cmd=0x20270503
[  157.622232] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20270503
[  158.626371] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20370503
[  159.634102] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x201f0500
[  161.678121] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20270503
[  162.682272] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20370503
[  163.694234] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x201f0500
[  165.730142] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20270503
[…]
```

In the bug report *[Intel Ice Lake, snd-hda-intel, HDMI] "No
response from codec" (after display hotplug?)* [1], note it’s a
different model, Takashi comments that this is a Thunderbolt or
i915 issue.

Please tell me, how to debug this further.


Kind regards,

Paul


[1]: https://bugzilla.kernel.org/show_bug.cgi?id=205229
 "205229 - [Intel Ice Lake, snd-hda-intel, HDMI] "No response from codec" 
(after display hotplug?)"
[0.463803] pci :3f:00.0: PME# supported from D3cold
[0.464089] pci :3e:01.0: PCI bridge to [bus 3f]
[0.464111] pci :3e:01.0:   bridge window [mem 0xc400-0xc40f]
[0.464220] pci :3e:04.0: PCI bridge to [bus 40-6d]
[0.464241] pci :3e:04.0:   bridge window [mem 0xc410-0xd9ff]
[0.464256] pci :3e:04.0:   bridge window [mem 0x8000-0xa9ff 
64bit pref]
[0.464560] pci :6e:00.0: [1344:5410] type 00 class 0x010802
[0.464583] pci :6e:00.0: reg 0x10: [mem 0xdc30-0xdc303fff 64bit]
[0.464870] pci :00:1d.4: PCI bridge to [bus 6e]
[0.464873] pci :00:1d.4:   bridge window [mem 0xdc30-0xdc3f]
[0.468165] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 11 12 14 15) *0
[0.468218] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 10 11 12 14 15) *1
[0.468269] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 10 11 12 14 15) *0
[0.468320] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 11 12 14 15) *0
[0.468371] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 10 11 12 14 15) *0
[0.468422] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 11 12 14 15) *0
[0.468473] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 10 11 12 14 15) *0
[0.468524] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 10 11 12 14 15) *0
[0.482170] ACPI: EC: interrupt unblocked
[0.482180] ACPI: EC: event unblocked
[0.482196] ACPI: \_SB_.PCI0.LPCB.ECDV: GPE=0x6e, EC_CMD/EC_SC=0x934, 
EC_DATA=0x930
[0.482197] ACPI: \_SB_.PCI0.LPCB.ECDV: Boot DSDT EC used to handle 
transactions and events
[0.482653] pci :00:02.0: vgaarb: setting as boot VGA device
[0.482653] pci :00:02.0: vgaarb: VGA device added: 
decodes=io+mem,owns=io+mem,locks=none
[0.482653] pci :00:02.0: vgaarb: bridge control possible
[0.482653] vgaarb: loaded
[0.482752] EDAC MC: Ver: 3.0.0
[0.483874] Registered efivars operations
[0.483874] PCI: Using ACPI for IRQ routing
[0.519201] PCI: pci_cache_line_size set to 64 bytes
[0.519918] e820: reserve RAM buffer [mem 0x0009e000-0x0009]
[0.519919] e820: reserve RAM buffer [mem 0x2a059000-0x2bff]
[0.519920] e820: reserve RAM buffer [mem 0x3a927000-0x3bff]
[0.519920] e820: reserve RAM buffer [mem 0x48e0-0x4bff]
[0.519921] e820: reserve RAM buffer [mem 0x4ae80-0x4afff]
[0.520127] hpet0: at MMIO 0xfed0, IRQs 2, 8, 0, 0, 0, 0, 0, 0
[0.520129] hpet0: 8 comparators, 64-bit 24.00 MHz counter
[0.521960] clocksource: Switched to clocksource tsc-early
[0.528569] VFS: Disk quotas dquot_6.6.0
[0.528579] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[0.528668] AppArmor: AppArmor Filesystem Enabled
[0.528677] pnp: PnP ACPI init
[0.528744] system 00:00: [mem 0x4000-0x403f] could not be reserved
[0.528747] system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)