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
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
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
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.
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
'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
'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
>
Guest:
> 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
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
Guest:
> 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
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.
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
Guest:
> 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)
13 matches
Mail list logo
