KERNEL PANIC on booting installation media - Acer TravelMate B116 - Details Inside
87 views
Skip to first unread message
Guest
Aug 28, 2019, 8:29:16 AM8/28/19
to qubes...@googlegroups.com
Dear List,
I have recently re-discovered Qubes and it is wonderful to see how far it has come in the past years and I thought it worth to giving it a try.
Alas, a kernel panic on booting the installation media. I have tried all 3 latest versions (4.0.2-rc1; 4.0.1, 3.2.1) available and get a similar error.
By using the kernel_delay=10 and removed the "quiet" option from the GRUB commandline, I was able to capture the attached console debug messages and stitch them together - image quality is not great, but readable. They were taken from the 4.0.1 image. I have looked at the referenced source file, but don't have enough experience with the kernel source to understand what is going on, other than some interrupt related issue. In any case, it seems to be quite a fundamental issue, which manifests in all 3 versions AND on 2 different Travelmate B series machines. I have searched online and been unable to find any similar issue.
Line 513 of "events_base.c"
Hopefully this can be bypassed with the right kernel parameter, allowing the installation of Qubes? Any pointers to fix or bypass this issue will be appreciated. I can provide further debug info if required.
The hardware is a TravelMate B116-M, booted from USB with the 4.0.1 iso image.
https://www.acer.com/ac/en/US/content/support-product/6088?b=1
Thanks for your help!
I have recently re-discovered Qubes and it is wonderful to see how far it has come in the past years and I thought it worth to giving it a try.
Alas, a kernel panic on booting the installation media. I have tried all 3 latest versions (4.0.2-rc1; 4.0.1, 3.2.1) available and get a similar error.
By using the kernel_delay=10 and removed the "quiet" option from the GRUB commandline, I was able to capture the attached console debug messages and stitch them together - image quality is not great, but readable. They were taken from the 4.0.1 image. I have looked at the referenced source file, but don't have enough experience with the kernel source to understand what is going on, other than some interrupt related issue. In any case, it seems to be quite a fundamental issue, which manifests in all 3 versions AND on 2 different Travelmate B series machines. I have searched online and been unable to find any similar issue.
Line 513 of "events_base.c"
---snip--- BUG_ON(info->type != IRQT_PIRQ); ---snip---I have tried different kernel options to see if anything changes, but had not much success in narrowing down the problem. It has also been a while since I was involved with linux at that level and I see a number of new parameters. Different Bios settings (legacy/UEFI) have also not had any noticable impact.
Hopefully this can be bypassed with the right kernel parameter, allowing the installation of Qubes? Any pointers to fix or bypass this issue will be appreciated. I can provide further debug info if required.
The hardware is a TravelMate B116-M, booted from USB with the 4.0.1 iso image.
https://www.acer.com/ac/en/US/content/support-product/6088?b=1
Thanks for your help!
awokd
Aug 28, 2019, 5:23:19 PM8/28/19
to qubes...@googlegroups.com
Guest:
between them, like a webcam? If so, disable it in BIOS, then try a
reinstall. If not, disable all possible integrated peripherals (or
enable all if you've disabled something) and try again.
> Dear List,
>
> I have recently re-discovered Qubes and it is wonderful to see how far it has
> come in the past years and I thought it worth to giving it a try.
>
> Alas, a kernel panic on booting the installation media. I have tried all 3
> latest versions (4.0.2-rc1; 4.0.1, 3.2.1) available and get a similar error.
>
> I have recently re-discovered Qubes and it is wonderful to see how far it has
> come in the past years and I thought it worth to giving it a try.
>
> Alas, a kernel panic on booting the installation media. I have tried all 3
> latest versions (4.0.2-rc1; 4.0.1, 3.2.1) available and get a similar error.
> I have looked at the referenced source file, but don't
> have enough experience with the kernel source to understand what is going on,
> other than some interrupt related issue. In any case, it seems to be quite a
> fundamental issue, which manifests in all 3 versions AND on 2 different
> Travelmate B series machines. I have searched online and been unable to find any
> similar issue.
> have enough experience with the kernel source to understand what is going on,
> other than some interrupt related issue. In any case, it seems to be quite a
> fundamental issue, which manifests in all 3 versions AND on 2 different
> Travelmate B series machines. I have searched online and been unable to find any
> similar issue.
> The hardware is a TravelMate B116-M, booted from USB with the 4.0.1 iso image.
> https://www.acer.com/ac/en/US/content/support-product/6088?b=1
Update BIOS first. Do those Acers have a hardware peripheral in common
> https://www.acer.com/ac/en/US/content/support-product/6088?b=1
between them, like a webcam? If so, disable it in BIOS, then try a
reinstall. If not, disable all possible integrated peripherals (or
enable all if you've disabled something) and try again.
Guest
Aug 29, 2019, 7:17:15 AM8/29/19
to awokd, qubes...@googlegroups.com
Awokd,
One of the machines is a B117-M and the other is a B116-M. The previous boot debug is from the B116-M.
1) BIOS was updated to the latest available 1.23 and 1.24 on the B116-M and B117-M respectively - still getting the KERNEL PANIC on both machines.
2) Tried disabling all non essential peripherals in the bios (Audio, Wifi, LAN, Webcam, SDcard reader - leaving only the USB ports enabled), but without any success before and after the BIOS Upgrade. Still getting the KERNEL PANIC.
If I had to guess I would point at the intel chipset as the common denominator? Is there a way to tweak the kernel to work around this? A failsafe option?
I would really love to give Qubes a try! Thanks for any further insight or pointers.
At 23:22 28/08/2019, 'awokd' via qubes-users wrote:
>Update BIOS first. Do those Acers have a hardware peripheral in common
>between them, like a webcam? If so, disable it in BIOS, then try a
>reinstall. If not, disable all possible integrated peripherals (or
>enable all if you've disabled something) and try again.
>
>--
>You received this message because you are subscribed to the Google Groups "qubes-users" group.
>To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users...@googlegroups.com.
>To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/9626ab96-acd6-8d04-346a-3a546c0b7cd3%40danwin1210.me.
One of the machines is a B117-M and the other is a B116-M. The previous boot debug is from the B116-M.
1) BIOS was updated to the latest available 1.23 and 1.24 on the B116-M and B117-M respectively - still getting the KERNEL PANIC on both machines.
2) Tried disabling all non essential peripherals in the bios (Audio, Wifi, LAN, Webcam, SDcard reader - leaving only the USB ports enabled), but without any success before and after the BIOS Upgrade. Still getting the KERNEL PANIC.
If I had to guess I would point at the intel chipset as the common denominator? Is there a way to tweak the kernel to work around this? A failsafe option?
I would really love to give Qubes a try! Thanks for any further insight or pointers.
At 23:22 28/08/2019, 'awokd' via qubes-users wrote:
>Update BIOS first. Do those Acers have a hardware peripheral in common
>between them, like a webcam? If so, disable it in BIOS, then try a
>reinstall. If not, disable all possible integrated peripherals (or
>enable all if you've disabled something) and try again.
>
>You received this message because you are subscribed to the Google Groups "qubes-users" group.
>To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users...@googlegroups.com.
>To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/9626ab96-acd6-8d04-346a-3a546c0b7cd3%40danwin1210.me.
Guest
Aug 31, 2019, 12:45:26 PM8/31/19
to qubes...@googlegroups.com
I am thinking it should be possible to isolate the problem and then possibly recompile the kernel and create a custom or failsafe installation medium? OR install on a different machine, customize the kernel and then move to the laptop? Hm, that might work.
Any further pointers are appreciated.
>To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/E1i3IQM-0003Om-1J%40node1.secure-shield.at.
Any further pointers are appreciated.
awokd
Aug 31, 2019, 2:22:27 PM8/31/19
to qubes...@googlegroups.com
Guest:
an interrupt that's not physical, but a lot of this is above my pay grade!
Does it have a NVMe controller? Can you put it in SATA compatible mode,
or if a regular storage controller IDE instead of AHCI?
Otherwise, try booting a regular distro on it and copying & pasting "cat
/proc/interrupts" here.
> I am thinking it should be possible to isolate the problem and then possibly recompile the kernel and create a custom or failsafe installation medium? OR install on a different machine, customize the kernel and then move to the laptop? Hm, that might work.
>
> Any further pointers are appreciated.
>
>
> At 13:16 29/08/2019, Guest wrote:
>> Awokd,
>>
>> One of the machines is a B117-M and the other is a B116-M. The previous boot debug is from the B116-M.
>>
>> 1) BIOS was updated to the latest available 1.23 and 1.24 on the B116-M and B117-M respectively - still getting the KERNEL PANIC on both machines.
>>
>> 2) Tried disabling all non essential peripherals in the bios (Audio, Wifi, LAN, Webcam, SDcard reader - leaving only the USB ports enabled), but without any success before and after the BIOS Upgrade. Still getting the KERNEL PANIC.
>>
>> If I had to guess I would point at the intel chipset as the common denominator? Is there a way to tweak the kernel to work around this? A failsafe option?
>>
>> I would really love to give Qubes a try! Thanks for any further insight or pointers.
>>
>> At 23:22 28/08/2019, 'awokd' via qubes-users wrote:
>>
>>> Update BIOS first. Do those Acers have a hardware peripheral in common
>>> between them, like a webcam? If so, disable it in BIOS, then try a
>>> reinstall. If not, disable all possible integrated peripherals (or
>>> enable all if you've disabled something) and try again.
Spent some time digging through code. Looks like it is somehow grabbing
>
> Any further pointers are appreciated.
>
>
> At 13:16 29/08/2019, Guest wrote:
>> Awokd,
>>
>> One of the machines is a B117-M and the other is a B116-M. The previous boot debug is from the B116-M.
>>
>> 1) BIOS was updated to the latest available 1.23 and 1.24 on the B116-M and B117-M respectively - still getting the KERNEL PANIC on both machines.
>>
>> 2) Tried disabling all non essential peripherals in the bios (Audio, Wifi, LAN, Webcam, SDcard reader - leaving only the USB ports enabled), but without any success before and after the BIOS Upgrade. Still getting the KERNEL PANIC.
>>
>> If I had to guess I would point at the intel chipset as the common denominator? Is there a way to tweak the kernel to work around this? A failsafe option?
>>
>> I would really love to give Qubes a try! Thanks for any further insight or pointers.
>>
>> At 23:22 28/08/2019, 'awokd' via qubes-users wrote:
>>
>>> Update BIOS first. Do those Acers have a hardware peripheral in common
>>> between them, like a webcam? If so, disable it in BIOS, then try a
>>> reinstall. If not, disable all possible integrated peripherals (or
>>> enable all if you've disabled something) and try again.
an interrupt that's not physical, but a lot of this is above my pay grade!
Does it have a NVMe controller? Can you put it in SATA compatible mode,
or if a regular storage controller IDE instead of AHCI?
Otherwise, try booting a regular distro on it and copying & pasting "cat
/proc/interrupts" here.
Guest
Sep 1, 2019, 3:39:17 AM9/1/19
to qubes...@googlegroups.com
The requested details are inline below.
I really appreciate you looking into this - Thanks. If there are any other thoughts and ideas to try to isolate the problem am happy to try and revert.
At 20:21 31/08/2019, 'awokd' via qubes-users wrote:
>>> At 23:22 28/08/2019, 'awokd' via qubes-users wrote:
>>>
>>>> Update BIOS first. Do those Acers have a hardware peripheral in common
>>>> between them, like a webcam? If so, disable it in BIOS, then try a
>>>> reinstall. If not, disable all possible integrated peripherals (or
>>>> enable all if you've disabled something) and try again.
>
>Spent some time digging through code. Looks like it is somehow grabbing
>an interrupt that's not physical, but a lot of this is above my pay grade!
I get that often when looking at code ;-)
>Does it have a NVMe controller?
Nothing like it - a simple SATA controller (see below for lspci output)
>Can you put it in SATA compatible mode,
>or if a regular storage controller IDE instead of AHCI?
No, the BIOS does not have and such options - no SATA compatible option in the BIOS and no IDE controller available in hardware.
>Otherwise, try booting a regular distro on it and copying & pasting "cat
>/proc/interrupts" here.
Below are the outputs of /proc/interrupts, lspci, lsusb, and uname. Taken on the latest tails, with all possible peripherals disabled in the bios.
---snip---
cat /proc/interrupts:
CPU0 CPU1 CPU2 CPU3
0: 8 0 0 0 IO-APIC 2-edge timer
1: 0 0 444 0 IO-APIC 1-edge i8042
8: 0 0 0 0 IO-APIC 8-edge rtc0
9: 0 2 0 0 IO-APIC 9-fasteoi acpi, INT0002
12: 0 140 0 0 IO-APIC 12-edge i8042
18: 0 0 0 0 IO-APIC 18-fasteoi i801_smbus
32: 0 0 0 0 IO-APIC 32-fasteoi 808622C1:00
43: 0 0 0 0 IO-APIC 43-fasteoi dw:dmac-1
45: 0 52 0 0 IO-APIC 45-fasteoi mmc0
115: 0 0 41183 0 PCI-MSI 327680-edge xhci_hcd
116: 0 0 0 1883 PCI-MSI 311296-edge ahci[0000:00:13.0]
117: 27211 0 0 0 PCI-MSI 32768-edge i915
118: 0 0 0 0 hdmi_lpe_audio_irqchip -hdmi_lpe_audio_irq_handler hdmi-lpe-audio
119: 0 0 0 0 INT0002 Virtual GPIO 2 ACPI:Event
120: 0 0 0 0 PCI-MSI 180224-edge proc_thermal
NMI: 14 15 17 16 Non-maskable interrupts
LOC: 71011 66702 72938 68160 Local timer interrupts
SPU: 0 0 0 0 Spurious interrupts
PMI: 14 15 17 16 Performance monitoring interrupts
IWI: 171 20 11 17 IRQ work interrupts
RTR: 0 0 0 0 APIC ICR read retries
RES: 14206 11466 11147 11923 Rescheduling interrupts
CAL: 8511 6653 4262 5411 Function call interrupts
TLB: 235 283 104 108 TLB shootdowns
TRM: 0 0 0 0 Thermal event interrupts
THR: 0 0 0 0 Threshold APIC interrupts
DFR: 0 0 0 0 Deferred Error APIC interrupts
MCE: 0 0 0 0 Machine check exceptions
MCP: 3 3 3 3 Machine check polls
HYP: 0 0 0 0 Hypervisor callback interrupts
HRE: 0 0 0 0 Hyper-V reenlightenment interrupts
HVS: 0 0 0 0 Hyper-V stimer0 interrupts
ERR: 0
MIS: 0
PIN: 0 0 0 0 Posted-interrupt notification event
NPI: 0 0 0 0 Nested posted-interrupt event
PIW: 0 0 0 0 Posted-interrupt wakeup event
lcpci:
00:00.0 Host bridge: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series SoC Transaction Register (rev 21)
00:02.0 VGA compatible controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller (rev 21)
00:0b.0 Signal processing controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Power Management Controller (rev 21)
00:13.0 SATA controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series SATA Controller (rev 21)
00:14.0 USB controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series USB xHCI Controller (rev 21)
00:1a.0 Encryption controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Trusted Execution Engine (rev 21)
00:1f.0 ISA bridge: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCU (rev 21)
00:1f.3 SMBus: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx SMBus Controller (rev 21)
00:00.0 0600: 8086:2280 (rev 21)
00:02.0 0300: 8086:22b1 (rev 21)
00:0b.0 1180: 8086:22dc (rev 21)
00:13.0 0106: 8086:22a3 (rev 21)
00:14.0 0c03: 8086:22b5 (rev 21)
00:1a.0 1080: 8086:2298 (rev 21)
00:1f.0 0601: 8086:229c (rev 21)
00:1f.3 0c05: 8086:2292 (rev 21)
lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
uname -a:
Linux amnesia 4.19.0-5-amd64 #1 SMP Debian 4.19.37-4 (2019-06-17) x86_64 GNU/Linux
---snip---
I really appreciate you looking into this - Thanks. If there are any other thoughts and ideas to try to isolate the problem am happy to try and revert.
At 20:21 31/08/2019, 'awokd' via qubes-users wrote:
>>> At 23:22 28/08/2019, 'awokd' via qubes-users wrote:
>>>
>>>> Update BIOS first. Do those Acers have a hardware peripheral in common
>>>> between them, like a webcam? If so, disable it in BIOS, then try a
>>>> reinstall. If not, disable all possible integrated peripherals (or
>>>> enable all if you've disabled something) and try again.
>
>Spent some time digging through code. Looks like it is somehow grabbing
>an interrupt that's not physical, but a lot of this is above my pay grade!
>Does it have a NVMe controller?
>Can you put it in SATA compatible mode,
>or if a regular storage controller IDE instead of AHCI?
>Otherwise, try booting a regular distro on it and copying & pasting "cat
>/proc/interrupts" here.
---snip---
cat /proc/interrupts:
CPU0 CPU1 CPU2 CPU3
0: 8 0 0 0 IO-APIC 2-edge timer
1: 0 0 444 0 IO-APIC 1-edge i8042
8: 0 0 0 0 IO-APIC 8-edge rtc0
9: 0 2 0 0 IO-APIC 9-fasteoi acpi, INT0002
12: 0 140 0 0 IO-APIC 12-edge i8042
18: 0 0 0 0 IO-APIC 18-fasteoi i801_smbus
32: 0 0 0 0 IO-APIC 32-fasteoi 808622C1:00
43: 0 0 0 0 IO-APIC 43-fasteoi dw:dmac-1
45: 0 52 0 0 IO-APIC 45-fasteoi mmc0
115: 0 0 41183 0 PCI-MSI 327680-edge xhci_hcd
116: 0 0 0 1883 PCI-MSI 311296-edge ahci[0000:00:13.0]
117: 27211 0 0 0 PCI-MSI 32768-edge i915
118: 0 0 0 0 hdmi_lpe_audio_irqchip -hdmi_lpe_audio_irq_handler hdmi-lpe-audio
119: 0 0 0 0 INT0002 Virtual GPIO 2 ACPI:Event
120: 0 0 0 0 PCI-MSI 180224-edge proc_thermal
NMI: 14 15 17 16 Non-maskable interrupts
LOC: 71011 66702 72938 68160 Local timer interrupts
SPU: 0 0 0 0 Spurious interrupts
PMI: 14 15 17 16 Performance monitoring interrupts
IWI: 171 20 11 17 IRQ work interrupts
RTR: 0 0 0 0 APIC ICR read retries
RES: 14206 11466 11147 11923 Rescheduling interrupts
CAL: 8511 6653 4262 5411 Function call interrupts
TLB: 235 283 104 108 TLB shootdowns
TRM: 0 0 0 0 Thermal event interrupts
THR: 0 0 0 0 Threshold APIC interrupts
DFR: 0 0 0 0 Deferred Error APIC interrupts
MCE: 0 0 0 0 Machine check exceptions
MCP: 3 3 3 3 Machine check polls
HYP: 0 0 0 0 Hypervisor callback interrupts
HRE: 0 0 0 0 Hyper-V reenlightenment interrupts
HVS: 0 0 0 0 Hyper-V stimer0 interrupts
ERR: 0
MIS: 0
PIN: 0 0 0 0 Posted-interrupt notification event
NPI: 0 0 0 0 Nested posted-interrupt event
PIW: 0 0 0 0 Posted-interrupt wakeup event
lcpci:
00:00.0 Host bridge: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series SoC Transaction Register (rev 21)
00:02.0 VGA compatible controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller (rev 21)
00:0b.0 Signal processing controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Power Management Controller (rev 21)
00:13.0 SATA controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series SATA Controller (rev 21)
00:14.0 USB controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series USB xHCI Controller (rev 21)
00:1a.0 Encryption controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Trusted Execution Engine (rev 21)
00:1f.0 ISA bridge: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCU (rev 21)
00:1f.3 SMBus: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx SMBus Controller (rev 21)
00:00.0 0600: 8086:2280 (rev 21)
00:02.0 0300: 8086:22b1 (rev 21)
00:0b.0 1180: 8086:22dc (rev 21)
00:13.0 0106: 8086:22a3 (rev 21)
00:14.0 0c03: 8086:22b5 (rev 21)
00:1a.0 1080: 8086:2298 (rev 21)
00:1f.0 0601: 8086:229c (rev 21)
00:1f.3 0c05: 8086:2292 (rev 21)
lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
uname -a:
Linux amnesia 4.19.0-5-amd64 #1 SMP Debian 4.19.37-4 (2019-06-17) x86_64 GNU/Linux
---snip---
awokd
Sep 1, 2019, 7:18:16 AM9/1/19
to qubes...@googlegroups.com
Guest:
might be related to the below 4.
> HYP: 0 0 0 0 Hypervisor callback interrupts
> HRE: 0 0 0 0 Hyper-V reenlightenment interrupts
> HVS: 0 0 0 0 Hyper-V stimer0 interrupts
feature or malware?
> 00:1a.0 Encryption controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Trusted Execution Engine (rev 21)
Is Secure Boot disabled?
> The requested details are inline below.
>
>
> Below are the outputs of /proc/interrupts, lspci, lsusb, and uname. Taken on the latest tails, with all possible peripherals disabled in the bios.
>
> ---snip---
> cat /proc/interrupts:
> CPU0 CPU1 CPU2 CPU3
>
> ---snip---
> cat /proc/interrupts:
> CPU0 CPU1 CPU2 CPU3
> 118: 0 0 0 0 hdmi_lpe_audio_irqchip -hdmi_lpe_audio_irq_handler hdmi-lpe-audio
> 119: 0 0 0 0 INT0002 Virtual GPIO 2 ACPI:Event
These two look different. Can you disable hdmi audio? That Virtual GPIO
> 119: 0 0 0 0 INT0002 Virtual GPIO 2 ACPI:Event
might be related to the below 4.
> HYP: 0 0 0 0 Hypervisor callback interrupts
> HRE: 0 0 0 0 Hyper-V reenlightenment interrupts
> HVS: 0 0 0 0 Hyper-V stimer0 interrupts
> PIN: 0 0 0 0 Posted-interrupt notification event
These 4 make it look like you are running in a Hypervisor. Some security
feature or malware?
> 00:1a.0 Encryption controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Trusted Execution Engine (rev 21)
awokd
Sep 1, 2019, 7:46:36 AM9/1/19
to qubes...@googlegroups.com
'awokd' via qubes-users:
>> HYP: 0 0 0 0 Hypervisor callback interrupts
>> HRE: 0 0 0 0 Hyper-V reenlightenment interrupts
>> HVS: 0 0 0 0 Hyper-V stimer0 interrupts
>
>> PIN: 0 0 0 0 Posted-interrupt notification event
Meant
>> HYP: 0 0 0 0 Hypervisor callback interrupts
>> HRE: 0 0 0 0 Hyper-V reenlightenment interrupts
>> HVS: 0 0 0 0 Hyper-V stimer0 interrupts
>
>> PIN: 0 0 0 0 Posted-interrupt notification event
NPI: 0 0 0 0 Nested
posted-interrupt event
instead of PIN.
posted-interrupt event
awokd
Sep 1, 2019, 1:56:25 PM9/1/19
to qubes...@googlegroups.com
'awokd' via qubes-users:
Try checking /proc/interrupts in a different distro too, like Mint maybe.
Guest
Sep 2, 2019, 5:09:38 PM9/2/19
to qubes...@googlegroups.com
The below info was collected from a debian running on the B116-M. Have added /poc/cpuinfo for completeness (see below).
Thanks for your looking into this!
At 19:55 01/09/2019, 'awokd' via qubes-users wrote:
>'awokd' via qubes-users:
>> 'awokd' via qubes-users:
>>
>>>> HYP: 0 0 0 0 Hypervisor callback interrupts
>>>> HRE: 0 0 0 0 Hyper-V reenlightenment interrupts
>>>> HVS: 0 0 0 0 Hyper-V stimer0 interrupts
>>>
>>>> PIN: 0 0 0 0 Posted-interrupt notification event
>>
>> Meant
>> NPI: 0 0 0 0 Nested
>> posted-interrupt event
>>
>> instead of PIN.
>>
>>> These 4 make it look like you are running in a Hypervisor. Some security
>>> feature or malware?
I doubt that. The CPU has virtualization capabilities and I imagine that these are the corresponding interrupts? The info is the same on the debian installation.
>Try checking /proc/interrupts in a different distro too, like Mint maybe.
Done. Please check below.
---snip---
12: 0 4154 0 0 IO-APIC 12-edge i8042
115: 0 0 722 0 PCI-MSI 327680-edge xhci_hcd
116: 0 0 0 11738 PCI-MSI 311296-edge ahci[0000:00:13.0]
117: 0 327153 0 0 PCI-MSI 1572864-edge enp3s0
118: 1376 0 0 0 PCI-MSI 32768-edge i915
119: 0 0 0 0 chv-gpio 81 80860F14:01 cd
120: 0 0 0 0 INT0002 Virtual GPIO 2 ACPI:Event
121: 0 0 0 0 PCI-MSI 180224-edge proc_thermal
122: 381 0 0 0 PCI-MSI 442368-edge snd_hda_intel:card0
NMI: 3 4 2 2 Non-maskable interrupts
LOC: 28546 75431 12343 24582 Local timer interrupts
IWI: 0 0 0 0 IRQ work interrupts
CAL: 3911 4248 2151 2040 Function call interrupts
TLB: 25 16 37 33 TLB shootdowns
MIS: 0
00:1c.0 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Express Port #1 (rev 21)
00:1c.2 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Express Port #3 (rev 21)
00:1c.3 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Express Port #4 (rev 21)
02:00.0 Network controller: Intel Corporation Wireless 3165 (rev 81)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
00:1c.0 0604: 8086:22c8 (rev 21)
00:1c.2 0604: 8086:22cc (rev 21)
00:1c.3 0604: 8086:22ce (rev 21)
03:00.0 0200: 10ec:8168 (rev 15)
Bus 001 Device 003: ID 0951:1624 Kingston Technology DataTraveler G2
vendor_id : GenuineIntel
cpu family : 6
model : 76
model name : Intel(R) Pentium(R) CPU N3700 @ 1.60GHz
stepping : 3
microcode : 0x35e
cpu MHz : 480.005
cache size : 1024 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 4
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch epb pti tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat
bugs : cpu_meltdown spectre_v1 spectre_v2 mds msbds_only
bogomips : 3200.00
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 76
model name : Intel(R) Pentium(R) CPU N3700 @ 1.60GHz
stepping : 3
microcode : 0x35e
cpu MHz : 480.008
cache size : 1024 KB
physical id : 0
siblings : 4
core id : 1
cpu cores : 4
apicid : 2
initial apicid : 2
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch epb pti tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat
bugs : cpu_meltdown spectre_v1 spectre_v2 mds msbds_only
bogomips : 3200.00
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 2
vendor_id : GenuineIntel
cpu family : 6
model : 76
model name : Intel(R) Pentium(R) CPU N3700 @ 1.60GHz
stepping : 3
microcode : 0x35e
cpu MHz : 480.000
cache size : 1024 KB
physical id : 0
siblings : 4
core id : 2
cpu cores : 4
apicid : 4
initial apicid : 4
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch epb pti tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat
bugs : cpu_meltdown spectre_v1 spectre_v2 mds msbds_only
bogomips : 3200.00
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 3
vendor_id : GenuineIntel
cpu family : 6
model : 76
model name : Intel(R) Pentium(R) CPU N3700 @ 1.60GHz
stepping : 3
microcode : 0x35e
cpu MHz : 495.106
cache size : 1024 KB
physical id : 0
siblings : 4
core id : 3
cpu cores : 4
apicid : 6
initial apicid : 6
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch epb pti tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat
bugs : cpu_meltdown spectre_v1 spectre_v2 mds msbds_only
bogomips : 3200.00
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
---snip---
Thanks for your looking into this!
At 19:55 01/09/2019, 'awokd' via qubes-users wrote:
>'awokd' via qubes-users:
>> 'awokd' via qubes-users:
>>
>>>> HYP: 0 0 0 0 Hypervisor callback interrupts
>>>> HRE: 0 0 0 0 Hyper-V reenlightenment interrupts
>>>> HVS: 0 0 0 0 Hyper-V stimer0 interrupts
>>>
>>>> PIN: 0 0 0 0 Posted-interrupt notification event
>>
>> Meant
>> NPI: 0 0 0 0 Nested
>> posted-interrupt event
>>
>> instead of PIN.
>>
>>> These 4 make it look like you are running in a Hypervisor. Some security
>>> feature or malware?
>Try checking /proc/interrupts in a different distro too, like Mint maybe.
---snip---
CPU0 CPU1 CPU2 CPU3
0: 8 0 0 0 IO-APIC 2-edge timer
1: 0 0 1179 0 IO-APIC 1-edge i8042
0: 8 0 0 0 IO-APIC 2-edge timer
8: 0 0 0 0 IO-APIC 8-edge rtc0
9: 0 0 0 0 IO-APIC 9-fasteoi acpi, INT0002
12: 0 4154 0 0 IO-APIC 12-edge i8042
18: 0 0 0 0 IO-APIC 18-fasteoi i801_smbus
32: 0 0 0 0 IO-APIC 32-fasteoi 808622C1:00
43: 0 0 0 0 IO-APIC 43-fasteoi dw:dmac-1
45: 0 52 0 0 IO-APIC 45-fasteoi mmc0
47: 0 0 0 0 IO-APIC 47-fasteoi mmc1
32: 0 0 0 0 IO-APIC 32-fasteoi 808622C1:00
43: 0 0 0 0 IO-APIC 43-fasteoi dw:dmac-1
45: 0 52 0 0 IO-APIC 45-fasteoi mmc0
115: 0 0 722 0 PCI-MSI 327680-edge xhci_hcd
116: 0 0 0 11738 PCI-MSI 311296-edge ahci[0000:00:13.0]
117: 0 327153 0 0 PCI-MSI 1572864-edge enp3s0
118: 1376 0 0 0 PCI-MSI 32768-edge i915
119: 0 0 0 0 chv-gpio 81 80860F14:01 cd
120: 0 0 0 0 INT0002 Virtual GPIO 2 ACPI:Event
121: 0 0 0 0 PCI-MSI 180224-edge proc_thermal
122: 381 0 0 0 PCI-MSI 442368-edge snd_hda_intel:card0
NMI: 3 4 2 2 Non-maskable interrupts
LOC: 28546 75431 12343 24582 Local timer interrupts
SPU: 0 0 0 0 Spurious interrupts
PMI: 3 4 2 2 Performance monitoring interrupts
IWI: 0 0 0 0 IRQ work interrupts
RTR: 0 0 0 0 APIC ICR read retries
RES: 4352 4169 1980 1953 Rescheduling interrupts
CAL: 3911 4248 2151 2040 Function call interrupts
TLB: 25 16 37 33 TLB shootdowns
TRM: 0 0 0 0 Thermal event interrupts
THR: 0 0 0 0 Threshold APIC interrupts
DFR: 0 0 0 0 Deferred Error APIC interrupts
MCE: 0 0 0 0 Machine check exceptions
MCP: 8 8 8 8 Machine check polls
THR: 0 0 0 0 Threshold APIC interrupts
DFR: 0 0 0 0 Deferred Error APIC interrupts
MCE: 0 0 0 0 Machine check exceptions
HYP: 0 0 0 0 Hypervisor callback interrupts
HRE: 0 0 0 0 Hyper-V reenlightenment interrupts
HVS: 0 0 0 0 Hyper-V stimer0 interrupts
ERR: 0
HRE: 0 0 0 0 Hyper-V reenlightenment interrupts
HVS: 0 0 0 0 Hyper-V stimer0 interrupts
MIS: 0
PIN: 0 0 0 0 Posted-interrupt notification event
NPI: 0 0 0 0 Nested posted-interrupt event
PIW: 0 0 0 0 Posted-interrupt wakeup event
00:00.0 Host bridge: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series SoC Transaction Register (rev 21)
00:02.0 VGA compatible controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller (rev 21)
00:0b.0 Signal processing controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Power Management Controller (rev 21)
00:13.0 SATA controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series SATA Controller (rev 21)
00:14.0 USB controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series USB xHCI Controller (rev 21)
00:02.0 VGA compatible controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller (rev 21)
00:0b.0 Signal processing controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Power Management Controller (rev 21)
00:13.0 SATA controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series SATA Controller (rev 21)
00:14.0 USB controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series USB xHCI Controller (rev 21)
00:1a.0 Encryption controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Trusted Execution Engine (rev 21)
00:1b.0 Audio device: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller (rev 21)
00:1c.0 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Express Port #1 (rev 21)
00:1c.2 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Express Port #3 (rev 21)
00:1c.3 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Express Port #4 (rev 21)
00:1f.0 ISA bridge: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCU (rev 21)
00:1f.3 SMBus: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx SMBus Controller (rev 21)
02:00.0 Network controller: Intel Corporation Wireless 3165 (rev 81)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
00:00.0 0600: 8086:2280 (rev 21)
00:02.0 0300: 8086:22b1 (rev 21)
00:0b.0 1180: 8086:22dc (rev 21)
00:13.0 0106: 8086:22a3 (rev 21)
00:14.0 0c03: 8086:22b5 (rev 21)
00:1a.0 1080: 8086:2298 (rev 21)
00:1b.0 0403: 8086:2284 (rev 21)
00:02.0 0300: 8086:22b1 (rev 21)
00:0b.0 1180: 8086:22dc (rev 21)
00:13.0 0106: 8086:22a3 (rev 21)
00:14.0 0c03: 8086:22b5 (rev 21)
00:1a.0 1080: 8086:2298 (rev 21)
00:1c.0 0604: 8086:22c8 (rev 21)
00:1c.2 0604: 8086:22cc (rev 21)
00:1c.3 0604: 8086:22ce (rev 21)
00:1f.0 0601: 8086:229c (rev 21)
00:1f.3 0c05: 8086:2292 (rev 21)
02:00.0 0280: 8086:3165 (rev 81)
00:1f.3 0c05: 8086:2292 (rev 21)
03:00.0 0200: 10ec:8168 (rev 15)
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0a2a Intel Corp.
Bus 001 Device 003: ID 0951:1624 Kingston Technology DataTraveler G2
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 76
model name : Intel(R) Pentium(R) CPU N3700 @ 1.60GHz
stepping : 3
microcode : 0x35e
cpu MHz : 480.005
cache size : 1024 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 4
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch epb pti tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat
bugs : cpu_meltdown spectre_v1 spectre_v2 mds msbds_only
bogomips : 3200.00
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 76
model name : Intel(R) Pentium(R) CPU N3700 @ 1.60GHz
stepping : 3
microcode : 0x35e
cpu MHz : 480.008
cache size : 1024 KB
physical id : 0
siblings : 4
core id : 1
cpu cores : 4
apicid : 2
initial apicid : 2
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch epb pti tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat
bugs : cpu_meltdown spectre_v1 spectre_v2 mds msbds_only
bogomips : 3200.00
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 2
vendor_id : GenuineIntel
cpu family : 6
model : 76
model name : Intel(R) Pentium(R) CPU N3700 @ 1.60GHz
stepping : 3
microcode : 0x35e
cpu MHz : 480.000
cache size : 1024 KB
physical id : 0
siblings : 4
core id : 2
cpu cores : 4
apicid : 4
initial apicid : 4
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch epb pti tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat
bugs : cpu_meltdown spectre_v1 spectre_v2 mds msbds_only
bogomips : 3200.00
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 3
vendor_id : GenuineIntel
cpu family : 6
model : 76
model name : Intel(R) Pentium(R) CPU N3700 @ 1.60GHz
stepping : 3
microcode : 0x35e
cpu MHz : 495.106
cache size : 1024 KB
physical id : 0
siblings : 4
core id : 3
cpu cores : 4
apicid : 6
initial apicid : 6
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch epb pti tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat
bugs : cpu_meltdown spectre_v1 spectre_v2 mds msbds_only
bogomips : 3200.00
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
---snip---
awokd
Sep 2, 2019, 8:46:54 PM9/2/19
to qubes...@googlegroups.com
Guest:
> I doubt that. The CPU has virtualization capabilities and I imagine that these are the corresponding interrupts? The info is the same on the debian installation.
>
>> Try checking /proc/interrupts in a different distro too, like Mint maybe.
>
> Done. Please check below.
Thanks. Hope I'm not leading you on a wild goose chase.
> 118: 1376 0 0 0 PCI-MSI 32768-edge i915
> 119: 0 0 0 0 chv-gpio 81 80860F14:01 cd
> 120: 0 0 0 0 INT0002 Virtual GPIO 2 ACPI:Event
117: 27211 0 0 0 PCI-MSI 32768-edge
i915
2 ACPI:Event
That odd interrupt changed in Debian. I wonder if it is
https://www.spinics.net/lists/kernel/msg2709360.html. Link is to a
kernel issue that was occurring with i915 HDMI LPE on interrupt
initialization, so it is in a similar place as the Xen events_base.c
interrupt initialization we are seeing.
If there is no way to disable HDMI audio completely, perhaps try the
external monitor or blacklist suggestions in here:
https://github.com/QubesOS/qubes-issues/issues/5247.
> I doubt that. The CPU has virtualization capabilities and I imagine that these are the corresponding interrupts? The info is the same on the debian installation.
>
>> Try checking /proc/interrupts in a different distro too, like Mint maybe.
>
> Done. Please check below.
> 118: 1376 0 0 0 PCI-MSI 32768-edge i915
> 119: 0 0 0 0 chv-gpio 81 80860F14:01 cd
> 120: 0 0 0 0 INT0002 Virtual GPIO 2 ACPI:Event
i915
118: 0 0 0 0
hdmi_lpe_audio_irqchip -hdmi_lpe_audio_irq_handler hdmi-lpe-audio
119: 0 0 0 0 INT0002 Virtual GPIO
hdmi_lpe_audio_irqchip -hdmi_lpe_audio_irq_handler hdmi-lpe-audio
2 ACPI:Event
That odd interrupt changed in Debian. I wonder if it is
https://www.spinics.net/lists/kernel/msg2709360.html. Link is to a
kernel issue that was occurring with i915 HDMI LPE on interrupt
initialization, so it is in a similar place as the Xen events_base.c
interrupt initialization we are seeing.
If there is no way to disable HDMI audio completely, perhaps try the
external monitor or blacklist suggestions in here:
https://github.com/QubesOS/qubes-issues/issues/5247.
Guest
Sep 5, 2019, 5:48:05 PM9/5/19
to qubes...@googlegroups.com
Hi Awokd,
>Thanks. Hope I'm not leading you on a wild goose chase.
Most tech things are once you get involved in the details ;-)
>That odd interrupt changed in Debian. I wonder if it is
>https://www.spinics.net/lists/kernel/msg2709360.html. Link is to a
>kernel issue that was occurring with i915 HDMI LPE on interrupt
>initialization, so it is in a similar place as the Xen events_base.c
>interrupt initialization we are seeing.
I read through it and do have an Intel graphics system, but I could not find any other similarities.
>If there is no way to disable HDMI audio completely, perhaps try the
>external monitor or blacklist suggestions in here:
>https://github.com/QubesOS/qubes-issues/issues/5247.
No option exists to disable HDMI Audio, or any VGA options for that matter in the BIOS ;-/
Blacklisting the kernel module had no noticeable effect on the KERNEL PANIC ;-/
Somebody off list suggested that I recompile the kernel with a known good config and only bring in the (diff) XEN options. That could work, but really sounds like a rabbit hole. I also hear that Qubes is notoriously incompatible on laptops? I wonder why this would be. Many other distros seem to have at least a failsafe boot option with some basic support. Is it security or visualization related related?
I guess it makes little sense to try older installation media before 3.2.1? Is there any ETA for a new kernel qubes version? Is it possible that 4.0.2 will receive a different kernel version in its final release?
Unless there are any other easy ideas available, I guess this is the end of the road for me and I will have to make do with Debian and Virtualbox?
Good day!
>Thanks. Hope I'm not leading you on a wild goose chase.
>That odd interrupt changed in Debian. I wonder if it is
>https://www.spinics.net/lists/kernel/msg2709360.html. Link is to a
>kernel issue that was occurring with i915 HDMI LPE on interrupt
>initialization, so it is in a similar place as the Xen events_base.c
>interrupt initialization we are seeing.
>If there is no way to disable HDMI audio completely, perhaps try the
>external monitor or blacklist suggestions in here:
>https://github.com/QubesOS/qubes-issues/issues/5247.
Blacklisting the kernel module had no noticeable effect on the KERNEL PANIC ;-/
Somebody off list suggested that I recompile the kernel with a known good config and only bring in the (diff) XEN options. That could work, but really sounds like a rabbit hole. I also hear that Qubes is notoriously incompatible on laptops? I wonder why this would be. Many other distros seem to have at least a failsafe boot option with some basic support. Is it security or visualization related related?
I guess it makes little sense to try older installation media before 3.2.1? Is there any ETA for a new kernel qubes version? Is it possible that 4.0.2 will receive a different kernel version in its final release?
Unless there are any other easy ideas available, I guess this is the end of the road for me and I will have to make do with Debian and Virtualbox?
Good day!
awokd
Sep 5, 2019, 7:20:11 PM9/5/19
to qubes...@googlegroups.com
Guest:
> Hi Awokd,
>> If there is no way to disable HDMI audio completely, perhaps try the
>> external monitor or blacklist suggestions in here:
>> https://github.com/QubesOS/qubes-issues/issues/5247.
>
> No option exists to disable HDMI Audio, or any VGA options for that matter in the BIOS ;-/
>
> Blacklisting the kernel module had no noticeable effect on the KERNEL PANIC ;-/
How about connecting the external (HDMI audio supporting) monitor? If
it's the issue I linked, maybe making HDMI audio use an interrupt will
work around it.
> Somebody off list suggested that I recompile the kernel with a known good config and only bring in the (diff) XEN options. That could work, but really sounds like a rabbit hole. I also hear that Qubes is notoriously incompatible on laptops? I wonder why this would be. Many other distros seem to have at least a failsafe boot option with some basic support. Is it security or visualization related related?
Qubes requires both Xen and Linux compatibility. Other distros have it
easy and only need Linux compat. Xen plays a major & differentiating
role in the security Qubes can provide.
> I guess it makes little sense to try older installation media before 3.2.1? Is there any ETA for a new kernel qubes version? Is it possible that 4.0.2 will receive a different kernel version in its final release?
Wouldn't bother with older. Kernel 5.something is available in the
testing repo. Easiest way I can think to get it would be to pull the
laptop hard drive, install Qubes on it from a different machine, update
kernel, then move hard drive back. You could also build a custom ISO
with the 5.x kernel, but that gets a bit involved:
https://www.qubes-os.org/doc/qubes-iso-building/, and there's no
guarantee it will fix the issue. Maybe others on the list or lurking
have an easier method.
> Unless there are any other easy ideas available, I guess this is the end of the road for me and I will have to make do with Debian and Virtualbox?
"Easy" = buy a different laptop! :) Afraid I'm out of other ideas. Next
might be to try to apply a similar code fix/workaround in events_base.c,
recompile, etc., but that's getting pretty in-depth for something I
could be completely wrong about. Hope you get a chance to use Qubes some
day.
> Hi Awokd,
>> If there is no way to disable HDMI audio completely, perhaps try the
>> external monitor or blacklist suggestions in here:
>> https://github.com/QubesOS/qubes-issues/issues/5247.
>
> No option exists to disable HDMI Audio, or any VGA options for that matter in the BIOS ;-/
>
> Blacklisting the kernel module had no noticeable effect on the KERNEL PANIC ;-/
it's the issue I linked, maybe making HDMI audio use an interrupt will
work around it.
> Somebody off list suggested that I recompile the kernel with a known good config and only bring in the (diff) XEN options. That could work, but really sounds like a rabbit hole. I also hear that Qubes is notoriously incompatible on laptops? I wonder why this would be. Many other distros seem to have at least a failsafe boot option with some basic support. Is it security or visualization related related?
easy and only need Linux compat. Xen plays a major & differentiating
role in the security Qubes can provide.
> I guess it makes little sense to try older installation media before 3.2.1? Is there any ETA for a new kernel qubes version? Is it possible that 4.0.2 will receive a different kernel version in its final release?
testing repo. Easiest way I can think to get it would be to pull the
laptop hard drive, install Qubes on it from a different machine, update
kernel, then move hard drive back. You could also build a custom ISO
with the 5.x kernel, but that gets a bit involved:
https://www.qubes-os.org/doc/qubes-iso-building/, and there's no
guarantee it will fix the issue. Maybe others on the list or lurking
have an easier method.
> Unless there are any other easy ideas available, I guess this is the end of the road for me and I will have to make do with Debian and Virtualbox?
might be to try to apply a similar code fix/workaround in events_base.c,
recompile, etc., but that's getting pretty in-depth for something I
could be completely wrong about. Hope you get a chance to use Qubes some
day.
Guest
Sep 8, 2019, 2:38:39 PM9/8/19
to qubes...@googlegroups.com
At 01:19 06/09/2019, 'awokd' via qubes-users wrote:
>How about connecting the external (HDMI audio supporting) monitor? If
>it's the issue I linked, maybe making HDMI audio use an interrupt will
>work around it.
Sorry, did not mention it explicitly, but yes I did try this and no, there was the same kernel panic. So no betterment.
>How about connecting the external (HDMI audio supporting) monitor? If
>it's the issue I linked, maybe making HDMI audio use an interrupt will
>work around it.
>Wouldn't bother with older. Kernel 5.something is available in the
>testing repo. Easiest way I can think to get it would be to pull the
>laptop hard drive, install Qubes on it from a different machine, update
>kernel, then move hard drive back. You could also build a custom ISO
>with the 5.x kernel, but that gets a bit involved:
>https://www.qubes-os.org/doc/qubes-iso-building/, and there's no
>guarantee it will fix the issue. Maybe others on the list or lurking
>have an easier method.
>"Easy" = buy a different laptop! :)
Reply all
Reply to author
Forward
0 new messages