Kernel 5.2RC (Release Candidate) series

[Doug S]

Kernel 5.2-rc1 is available from the Ubuntu Mainline PPA and Kernel.org. (Several builds failed.)
I still only use the TEO (Timer Events Oriented) idle governor, introduced in the 5.1RC kernel cycle.

doug@s15:~$ grep . /sys/devices/system/cpu/cpuidle/* && uname -a
/sys/devices/system/cpu/cpuidle/available_governors:ladder menu teo
/sys/devices/system/cpu/cpuidle/current_driver:intel_idle
/sys/devices/system/cpu/cpuidle/current_governor:teo
Linux s15 5.2.0-rc1-stock #593 SMP PREEMPT Mon May 20 13:33:44 PDT 2019 x86_64 x86_64 x86_64 GNU/Linux

[lonniehenry-gmail]

I have been trying to use the mainline kernel for 5.2 daily on my asus laptop. I always try the new kernels during the testing stage. I had no problem with 5.1, but when I try to boot any of the 5.2 dailies with the logitech mouse receiver plugged in, it stops and does not boot. If I don't plug in the receiver, I get a normal boot. Then I plug in the receiver and after a couple of minutes, the mouse starts working. I have read that the Logitech receivers drivers were going to be added to the kernel. Would that work be stopping the boot sequence. How do I try to figure it out?

Eaon and Disco partitions on an Asus Zenbook

[mrfelker]

What's up with rc3. The directory does not have any compiled code and hasn't for a couple of days. I've never seen anything like this.

[Doug S]

What's up with rc3. The directory does not have any compiled code and hasn't for a couple of days. I've never seen anything like this.

actually, it happens occasionally that the build gets broken. If it doesn't get sorted out after a few days someone usually inquires in the kernel IRC channel (It can help to look back in the IRC logs for a few days, to see if someone mentioned it already. ( https://irclogs.ubuntu.com/2019/06/0...tu-kernel.html , for example. No activity for the past few days.). Note that often the kernel team doesn't seem to know the daily mainline build is broken. Also have a look at the build log for anything obvious.

I am behind an RC at the moment, but will try to catch up in a few days.

EDIT 1: Some of the builds, including AMD64, worked in today's (2019.06.04) daily.
EDIT 2: There is IRC channel activity today (2019.06.05) on the build failures.
EDIT 3: Kernel 5.2-rc3 is available from the mainline PPA. All day (2019.06.05) I have been running one I compiled myself without any issues.

[corradoventu]

Installed kernel 5.2.0-050200rc4-generic

corrado@corrado-p9-ee-0523:~$ inxi -SCx
System:    Host: corrado-p9-ee-0523 Kernel: 5.2.0-050200rc4-generic x86_64 bits: 64 compiler: gcc v: 8.3.0 
           Desktop: Gnome 3.32.2 Distro: Ubuntu 19.10 (Eoan Ermine) 
CPU:       Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31296 
           Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 
corrado@corrado-p9-ee-0523:~$

No errors at install but errors at 1st boot:

.........
giu 09 10:58:43 corrado-p9-ee-0523 gnome-shell[1440]: [AppIndicatorSupport-FATAL] unable to update overlay icon
giu 09 10:58:43 corrado-p9-ee-0523 gnome-shell[1440]: [AppIndicatorSupport-FATAL] unable to update overlay icon
giu 09 10:58:50 corrado-p9-ee-0523 PackageKit[1236]: refresh-cache transaction /210_ccdeaded from uid 1000 finished with success after 8228ms
giu 09 10:58:50 corrado-p9-ee-0523 snapd[825]: snapmgr.go:258: cannot read snap info of snap "gnome-system-monitor" at revision 83: cannot find installed snap "gnome-system-monitor" at revision 83: missing file /snap/gnome-system-monitor/83/meta/snap.yaml
giu 09 10:58:51 corrado-p9-ee-0523 PackageKit[1236]: resolve transaction /211_cbadebbd from uid 1000 finished with success after 1223ms
giu 09 10:58:52 corrado-p9-ee-0523 gnome-software[1941]: Only 8 apps for recent list, hiding
giu 09 10:58:52 corrado-p9-ee-0523 PackageKit[1236]: resolve transaction /212_eaebaead from uid 1000 finished with success after 282ms
giu 09 10:58:52 corrado-p9-ee-0523 PackageKit[1236]: resolve transaction /213_aeccdecb from uid 1000 finished with success after 271ms
giu 09 10:58:52 corrado-p9-ee-0523 gnome-software[1941]: hiding category graphics featured applications: found only 1 to show, need at least 9
giu 09 10:59:05 corrado-p9-ee-0523 PackageKit[1236]: search-file transaction /214_edaeacad from uid 1000 finished with success after 12671ms
giu 09 10:59:05 corrado-p9-ee-0523 PackageKit[1236]: search-file transaction /215_eebebdad from uid 1000 finished with success after 344ms
giu 09 10:59:05 corrado-p9-ee-0523 PackageKit[1236]: search-file transaction /216_adeccede from uid 1000 finished with success after 325ms
giu 09 10:59:06 corrado-p9-ee-0523 PackageKit[1236]: search-file transaction /217_eeaccbdb from uid 1000 finished with success after 339ms
giu 09 10:59:06 corrado-p9-ee-0523 PackageKit[1236]: search-file transaction /218_cecaeeab from uid 1000 finished with success after 325ms
giu 09 10:59:06 corrado-p9-ee-0523 PackageKit[1236]: get-details transaction /219_bdbcacaa from uid 1000 finished with success after 278ms
giu 09 10:59:07 corrado-p9-ee-0523 gnome-software[1941]: Failed to load snap icon: local snap has no icon
giu 09 10:59:07 corrado-p9-ee-0523 snapd[825]: snapmgr.go:258: cannot read snap info of snap "gnome-system-monitor" at revision 83: cannot find installed snap "gnome-system-monitor" at revision 83: missing file /snap/gnome-system-monitor/83/meta/snap.yaml
giu 09 10:59:07 corrado-p9-ee-0523 gnome-software[1941]: Failed to load snap icon: local snap has no icon
giu 09 10:59:16 corrado-p9-ee-0523 systemd-resolved[780]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.

corrado@corrado-p9-ee-0523:~$ snap list
Name                  Version                     Rev   Tracking  Publisher   Notes
core                  16-2.39                     6964  stable    canonical✓  core
core18                20190508                    970   stable    canonical✓  base
gnome-3-28-1804       3.28.0-10-gaa70833.aa70833  51    stable/…  canonical✓  -
gnome-calculator      3.32.1                      406   stable/…  canonical✓  -
gnome-characters      v3.32.1+git2.3367201        280   stable/…  canonical✓  -
gnome-logs            3.32.0-4-ge8f3f37ca8        61    stable/…  canonical✓  -
gnome-system-monitor                              83    stable/…  canonical✓  broken
gtk-common-themes     0.1-16-g2287c87             1198  stable/…  canonical✓  -
corrado@corrado-p9-ee-0523:~$

snap refresh is unsuccessful:

corrado@corrado-p9-ee-0523:~$ snap refresh gnome-system-monitor
snap "gnome-system-monitor" has no updates available
corrado@corrado-p9-ee-0523:~$

After a while now gnome-system-monitor is ok

[Doug S]

I have been trying to use the mainline kernel for 5.2 daily on my asus laptop. I always try the new kernels during the testing stage. I had no problem with 5.1, but when I try to boot any of the 5.2 dailies with the logitech mouse receiver plugged in, it stops and does not boot. If I don't plug in the receiver, I get a normal boot. Then I plug in the receiver and after a couple of minutes, the mouse starts working. I have read that the Logitech receivers drivers were going to be added to the kernel. Would that work be stopping the boot sequence. How do I try to figure it out?

Eaon and Disco partitions on an Asus Zenbook

Have you tried 5.2-rc5? I only know of bisecting the kernel as a way to isolate the exact commit that caused your problem. That being said, I did find an upstream bug report and also see a fix recently added to the kernel:

commit 3ed224e273ac5880eeab4c3043a6b06b0478dd56
Author: Hans de Goede <hdegoede@redhat.com>
Date:   Wed Jun 5 14:44:08 2019 +0200

    HID: logitech-dj: Fix 064d:c52f receiver support

And it seems "recently' means 5.2-rc5:

doug@s15:~/temp-k-git/linux$ git tag --contains 3ed224e273ac5880eeab4c3043a6b06b0478dd56
v5.2-rc5

[lonniehenry-gmail]

Doug S - I tried the newest 5.2-rc5 and the problem was solved. I figured that it would be fixed at some point. I thank you for following up on the issue.

[DougieFresh4U]

Not to be picky but in your sig you list Dapper Duck but it's Dapper Drake.
I go back as far as Breezy Badger and loved getting the free cd's from ship it.

[lonniehenry-gmail]

You are right. I misremebered. I dualed Dapper and continued to try all the newest developement versions as soon as they came out. Dumped windows after a year or so.

[IanW]

Good news - Linus has dubbed 5.2 "Bobtail Squid" & pushed it out of the nest.
Bad news - Today's build has failed for both AMD64 & i386.