Kernel 4.19.43 Issues

[William Edward Bailey, II]

Like others have reported, I updated my Qubes system earlier today with
the 4.19.43 kernel along with the xen updates. Past updates have gone
smoothly for the duration of my running Qubes but unfortunately this one
wasn't.

The update itself installed fine with no issues or errors. I was able to
reboot successfully but when the system gets to the normal LightDM user
logon screen, the monitor output is garbled and has many artifacts. If I
attempt to log in, after a few seconds of the system attempting to start
up the Qubes Desktop, I get kicked back out to the login screen again.
The system will keep looping in such a manner.

I'm able to boot back into the system using the older 4.14.116 and
everything works again so I suspected the issue had to do with the
4.19.43 kernel and the system's graphics card.

I'm running an AMD processor with a Radeon R7 graphics card.

Upon searching Google, it appears that there are known issues with the
4.19.x kernels with certain AMD systems/cards.

For example:

https://bugs.freedesktop.org/show_bug.cgi?id=108981

https://forum.manjaro.org/t/upgrade-to-4-19-disables-my-amdgpu/64920/5

Seems that the 4.19.x branch was problematic with some AMD cards.

Since the graphics are borked and I can't get into the system with
4.19.x, what might be the best way to try to troubleshoot what the
specific issue might be?

Thanks in advance.

[Eva Star]

> Seems that the 4.19.x branch was problematic with some AMD cards.
>

Maybe :) But I have problem and there is hybrid index hd + nvidia card (not used). In my case this kernel have problems with CPU :)

[awokd]

Eva Star:

>
>> Seems that the 4.19.x branch was problematic with some AMD cards.
>>
>
> Maybe :) But I have problem and there is hybrid index hd + nvidia card (not used). In my case this kernel have problems with CPU :)
>

For a counterpoint, I think drokmed also had a Radeon card, and their
incompatibility with 4.19 has been mentioned a couple times previously
on this list:
https://www.mail-archive.com/qubes...@googlegroups.com/msg27411.html
https://www.mail-archive.com/qubes...@googlegroups.com/msg27685.html

I have an older Radeon card on one of my Qubes systems. Am currently
running a full backup on it, but will test the update once it completes.
Expect I'll encounter the same problems.

If 4.19 is this problematic, should the update be pulled?

[dro...@gmail.com]

Yes, please pull 4.19.43-1 kernel update, if possible. Would solve my problem.

I was curious if it was the kernel, or the xfce and lightdm, so I tried a fresh install, and when done, reboots fine. Then I didn't update anything, but I did switch over to kde/sddm with fingers crossed, hoping that was it. No such luck. I updated dom0 only, then after reboot, the same ole problem. Computer boots all the way up to the point of login, then when using kde, just appears to stop. PC not locked up, can still toggle numlock and capslock, but ctrl-alt-del doesn't work, have to press power button, then pc shuts down on it's own.

I have an older ATI Radeon card too:

(ATI) now called AMD Mobility Radeon HD 5870
on an Intel ASUS G73Jh 213 laptop

It's not the AMD cpu for me, I have Intel.

I can still get in, booting new Xen 4.8.5-6 with old kernel 4.14.74 (from fresh install).

[Eva Star]

> > If 4.19 is this problematic, should the update be pulled?
>
> Yes, please pull 4.19.43-1 kernel update, if possible. Would solve my problem.
>

Yes, problems :(
Currently, you can install all dom0 updates, but before actual reboot change kernel manually to previous that reboot and all must be fine

[Andrew David Wong]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Thanks, all. I've posted a question for Marek about whether the update
should be pulled:

https://github.com/QubesOS/qubes-issues/issues/4934#issuecomment-496034991

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlzrDXoACgkQ203TvDlQ
MDD/Jg//Qx+rud/Fu0xp3k9/Gw6NI03e5ZOYyQq2yB3bKXSCxiCVF2v7ZKNywRVf
Sq0Wagv6EwLaq6Wz+E9pFwkBZSgKFa1nNskI7AvTf27+FVTlamleRJqEpBNQ2HJV
tCaEzr+mEAdUcBKO1WKcBQnBZI7fkHQRWn+GGgVXrlkNxnIgWkKmNiCjcWr8O30L
uHoH25BvVH+xxrF7DAuV65vdtztA9m6cyAjubss2U92y5DB4PTQM9qqVAyi2pIQw
xXVuwTRo4eDdr1/e8gjgdeHepxP1a2kacBlI3tKOgV7CbHzWm5iz1RvdnILyP3bZ
dkKTIxUzNydG1nGVyM0dvcCeAYnr8Mf0pxv95Pzl1E6V2IphwAHSrZfwePESRFgQ
tfCOlf7pMU3Ll1ZNLZG5Ey2yv7XeOGz0lLTo+eeWBFeNEqKnpZKVekmpTs3tRqL+
c3G6Z0kK+JFIt5jv3ZH+UAXHPXtCOf8ofe6qEYwBOCuZY0OzVnayuOxqNYNGh88b
oXMGxroZdQU/M03sYMLHu6zhgJ+TXGHa3GICvFosoFZXDjxf1KWqQykkF3ubiMsp
MTG9WRa3kjvCchsC6LbNtPXXp2TjKljjYDyQBLWO+RnuHXDs2qsSK1+f9SrSZ20B
UA97yXk7csI59LSMdSL8kX/c4f7zJPC3/MayAycmruh2IRZg16c=
=7rc+
-----END PGP SIGNATURE-----

[Andrew David Wong]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 26/05/2019 5.04 PM, Andrew David Wong wrote:
>
> On 26/05/2019 3.39 PM, Eva Star wrote:
>
>>>> If 4.19 is this problematic, should the update be pulled?
>>>
>>> Yes, please pull 4.19.43-1 kernel update, if possible. Would solve my problem.
>>>
>
>> Yes, problems :(
>> Currently, you can install all dom0 updates, but before actual reboot change kernel manually to previous that reboot and all must be fine
>
>
> Thanks, all. I've posted a question for Marek about whether the update
> should be pulled:
>
> https://github.com/QubesOS/qubes-issues/issues/4934#issuecomment-496034991
>

Kernel 4.19 has been pulled from the "current" repo for now:

https://github.com/QubesOS/qubes-issues/issues/4934#issuecomment-496035377

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlzrDv8ACgkQ203TvDlQ
MDATVg//emqLXvTO/lOnJPT/THNOw82RuH3d2R06ZDaT1VK8iryxvg2ql+sPm3q8
UXkc4y7UskdjlvtsLmI26Drb9sws13fyOwH9O7nTb7XxnOsh7grrKmQ89hLj01Lq
SfCQA3oVb5kaqp57J6EeG2l9ln+pDARmwZLiUHoi8jrz49T1vh752bYVYl+CifwF
/+hYeJZZXk+kEGWnDZOU6ryLDFAXpjoVl7eDkZtd7aUVckBWVD31370ESHS/9nga
2kj36mmKFKz812WfC5HHeJ6zUPNKRzNzHLiptdG4rui1twZx+o6tpPoxkrOIt3Tb
HD3YBpsoME8rqJvsOAvl/3vQFWYo5v+rVj9dP0Sw7/x4zd4NoM8x+KxF7HBJLbN8
Jat/AAeHcVx02XH+h3sWGG8WxojNZQTsxFFE5u1fYhNIWTKFZBv74g1lizULJo6I
t5p08JeZvEEK4R0qiabNGMwfkB3w2ZRtA1GTCjmnHlZa093LA09fdlUH4iyJ94eT
Q6A+2dwxWBdZb5EyhA2+iypFko+kkmDK7vSVzCO21zBlIwUI8//n/V+tFN7X06So
wnrGOcCi0lANiVSQ1F5shVnFxZvSE+/ahqynbEVjkDEROab+bQyG4qd70mUQdoAW
3g0id1qyBc56diqAZnWmcuxJp545kiqGL5ZtPV7/4HnY34/bx3c=
=mUla
-----END PGP SIGNATURE-----

[BM-2cTjsegDfZQNGQW...@bitmessage.ch]

Interestingly, this apparently problematic 4.19.43 kernel did not break
my Dom0 or Fedora-29, but instead, broke sys-whonix: I can connect
through any chain of net-vms to clearnet, including through debian-9
VMs with 4.19.43. However, I could not get out to the internet via
sys-whonix, until selecting an older kernel in sys-whonix itself. I'm
not sure if that issue has been noted yet. A further twist is that
updates via tor to onion repos still worked with the bad kernel in
sys-whonix. It was only non-update traffic that could not make it
through sys-whonix. This all happens with 4.19.43 in Dom0, and with
kernel-latest (5-something) in Dom0, which had no impact on the issue.

[dro...@gmail.com]

Whonix updating/working fine here. Maybe try creating a new sys-whonix2 VM from the template, and switch to it.

[awokd]

dro...@gmail.com wrote on 5/28/19 1:54 AM:

Try 4.19.46-3 (in current-testing right now). I'm running it and tested
debian-9, fedora-29, and whonix-ws through sys-whonix with no problems.

[BM-2cTjsegDfZQNGQW...@bitmessage.ch]

On Tue, 28 May 2019 10:56:30 +0000
"'awokd' via qubes-users" <qubes...@googlegroups.com> wrote:

> dro...@gmail.com wrote on 5/28/19 1:54 AM:
> > On Monday, May 27, 2019 at 6:32:20 PM UTC-7,
> > BM-2cTjsegDfZQNGQW...@bitmessage.ch wrote:
> >> Interestingly, this apparently problematic 4.19.43 kernel did not
> >> break my Dom0 or Fedora-29, but instead, broke sys-whonix: I can
> >> connect through any chain of net-vms to clearnet, including
> >> through debian-9 VMs with 4.19.43. However, I could not get out to
> >> the internet via sys-whonix, until selecting an older kernel in
> >> sys-whonix itself. I'm not sure if that issue has been noted yet.
> >> A further twist is that updates via tor to onion repos still
> >> worked with the bad kernel in sys-whonix. It was only non-update
> >> traffic that could not make it through sys-whonix. This all
> >> happens with 4.19.43 in Dom0, and with kernel-latest (5-something)
> >> in Dom0, which had no impact on the issue.
> >
> > Whonix updating/working fine here. Maybe try creating a new
> > sys-whonix2 VM from the template, and switch to it.

Strange, I could update just fine, and the sys-whonix connected to tor
internally just fine, but VMs connecting through it had issues. The same
was true when I made a new sys-whonix2 on the same kernel (not older
ones).

> Try 4.19.46-3 (in current-testing right now). I'm running it and
> tested debian-9, fedora-29, and whonix-ws through sys-whonix with no
> problems.

Will have to figure out how to grab just this from testing and try,
thanks!

[awokd]

BM-2cTjsegDfZQNGQW...@bitmessage.ch wrote on 5/28/19
7:45 PM:

> Will have to figure out how to grab just this from testing and try,
> thanks!

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing kernel
kernel-qubes-vm --best --allowerasing

(Had it in my history buffer anyways!)