User avatar
DougieLawson
Posts: 39610
Joined: Sun Jun 16, 2013 11:19 pm
Location: A small cave in deepest darkest Basingstoke, UK
Contact: Website Twitter

Re: Moving Linux Kernel to 5.4

Thu May 07, 2020 8:41 pm

opscrafts wrote:
Thu May 07, 2020 5:11 pm
Hi, after running rpi-update yesterday, my Waveshare 3.5inch RPi LCD stopped working - the screen was white after boot. Fixed it by removing the overlays provided by Waveshare and installing the ones available on https://github.com/swkim01/waveshare-dtoverlays. Just passing it on for the benefit of others.
Which model? Which controller chip?

Is it connected as an SPI device?
Note: Any requirement to use a crystal ball or mind reading will result in me ignoring your question.

Criticising any questions is banned on this forum.

Any DMs sent on Twitter will be answered next month.
All fake doctors are on my foes list.

satadru
Posts: 39
Joined: Thu Apr 18, 2013 5:18 pm

Re: Moving Linux Kernel to 5.4

Fri May 08, 2020 8:24 pm

DougieLawson wrote:
Thu May 07, 2020 8:41 pm
opscrafts wrote:
Thu May 07, 2020 5:11 pm
Hi, after running rpi-update yesterday, my Waveshare 3.5inch RPi LCD stopped working - the screen was white after boot. Fixed it by removing the overlays provided by Waveshare and installing the ones available on https://github.com/swkim01/waveshare-dtoverlays. Just passing it on for the benefit of others.
Which model? Which controller chip?

Is it connected as an SPI device?
I was responsible (with lots of help from people here) for the updated waveshare35a overlays on there, which fix issues with Linux support for overlays after kernel 5.0. They work great with the 5.4 kernel on raspbian. :)

Jo7e4
Posts: 1
Joined: Fri May 08, 2020 6:50 pm

Re: Moving Linux Kernel to 5.4

Sat May 09, 2020 3:37 am

Hardware: Raspberry Pi 3 Model B Plus Rev 1.3
Kernel: Linux 5.4.35-v7+ #1314 SMP Fri May 1 17:41:46 BST 2020 armv7l GNU/Linux
Packages: buster main contrib non-free rpi

Used rpi-update, then built the kernel-headers with rpi-source, then ran dpkg-reconfigure wireguard-dkms to build the kernel module. All fine and dandy for about 12 hours. Then the 3B got unresponsive, hard reset and looking at the logs:

May 9 04:49:00 ns1 kernel: [22126.063311] ------------[ cut here ]------------
May 9 04:49:00 ns1 kernel: [22126.063377] WARNING: CPU: 3 PID: 0 at net/sched/sch_generic.c:448 dev_watchdog+0x310/0x314
May 9 04:49:00 ns1 kernel: [22126.063396] NETDEV WATCHDOG: eth0 (lan78xx): transmit queue 0 timed out
May 9 04:49:00 ns1 kernel: [22126.063411] Modules linked in: 8021q garp stp llc nft_counter nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv4 nft_compat nf_tables nfnetlink bcm2835_codec(C) bcm2835_v4l2(C) bcm2835_isp(C) v4l2_mem2mem bcm2835_mmal_vchiq(C) videobuf2_dma_contig raspberrypi_hwmon videobuf2_vmalloc hwmon videobuf2_memops videobuf2_v4l2 videobuf2_common videodev mc vc_sm_cma(C) uio_pdrv_genirq uio fixed wireguard ip6_udp_tunnel udp_tunnel ip_tables x_tables ipv6 nf_defrag_ipv6
May 9 04:49:00 ns1 kernel: [22126.063595] CPU: 3 PID: 0 Comm: swapper/3 Tainted: G C 5.4.35-v7+ #1314
May 9 04:49:00 ns1 kernel: [22126.063601] Hardware name: BCM2835
May 9 04:49:00 ns1 kernel: [22126.063606] Backtrace:
May 9 04:49:00 ns1 kernel: [22126.063626] [<8010d458>] (dump_backtrace) from [<8010d750>] (show_stack+0x20/0x24)
May 9 04:49:00 ns1 kernel: [22126.063637] r6:b993c000 r5:00000000 r4:80d930b4 r3:e7001423
May 9 04:49:00 ns1 kernel: [22126.063651] [<8010d730>] (show_stack) from [<808a45a4>] (dump_stack+0xe0/0x124)
May 9 04:49:00 ns1 kernel: [22126.063666] [<808a44c4>] (dump_stack) from [<8011fd24>] (__warn+0xec/0x104)
May 9 04:49:00 ns1 kernel: [22126.063679] r8:000001c0 r7:00000009 r6:80b06554 r5:00000000 r4:b993dd4c r3:e7001423
May 9 04:49:00 ns1 kernel: [22126.063693] [<8011fc38>] (__warn) from [<8011fdc0>] (warn_slowpath_fmt+0x84/0xc0)
May 9 04:49:00 ns1 kernel: [22126.063706] r9:80b06554 r8:000001c0 r7:807b23b8 r6:00000009 r5:80b0656c r4:80d04f48
May 9 04:49:00 ns1 kernel: [22126.063720] [<8011fd40>] (warn_slowpath_fmt) from [<807b23b8>] (dev_watchdog+0x310/0x314)
May 9 04:49:00 ns1 kernel: [22126.063734] r9:00214dc0 r8:b9904000 r7:00000003 r6:80d03d00 r5:b99042a8 r4:00000000
May 9 04:49:00 ns1 kernel: [22126.063751] [<807b20a8>] (dev_watchdog) from [<8019b560>] (call_timer_fn+0x40/0x180)
May 9 04:49:00 ns1 kernel: [22126.063763] r8:807b20a8 r7:00000100 r6:b993c000 r5:b99042a8 r4:be5b6440
May 9 04:49:00 ns1 kernel: [22126.063779] [<8019b520>] (call_timer_fn) from [<8019c6b0>] (run_timer_softirq+0x288/0x654)
May 9 04:49:00 ns1 kernel: [22126.063792] r9:00000000 r8:b99042a8 r7:b993c000 r6:00214dc0 r5:b993de24 r4:be5b6440
May 9 04:49:00 ns1 kernel: [22126.063807] [<8019c428>] (run_timer_softirq) from [<8010249c>] (__do_softirq+0x1a4/0x418)
May 9 04:49:00 ns1 kernel: [22126.063821] r10:00000004 r9:00000082 r8:b989d000 r7:00000100 r6:b993c000 r5:00000001
May 9 04:49:00 ns1 kernel: [22126.063826] r4:80d03084
May 9 04:49:00 ns1 kernel: [22126.063841] [<801022f8>] (__do_softirq) from [<80125b78>] (irq_exit+0x100/0x110)
May 9 04:49:00 ns1 kernel: [22126.063854] r10:00000000 r9:b993c000 r8:b989d000 r7:00000001 r6:00000000 r5:00000000
May 9 04:49:00 ns1 kernel: [22126.063859] r4:80c9d2a4
May 9 04:49:00 ns1 kernel: [22126.063875] [<80125a78>] (irq_exit) from [<80180994>] (__handle_domain_irq+0x70/0xc4)
May 9 04:49:00 ns1 kernel: [22126.063889] [<80180924>] (__handle_domain_irq) from [<80102228>] (bcm2836_arm_irqchip_handle_irq+0x60/0xa4)
May 9 04:49:00 ns1 kernel: [22126.063902] r8:80d984b4 r7:b993df6c r6:ffffffff r5:60000013 r4:00000003 r3:b993df38
May 9 04:49:00 ns1 kernel: [22126.063916] [<801021c8>] (bcm2836_arm_irqchip_handle_irq) from [<80101a3c>] (__irq_svc+0x5c/0x7c)
May 9 04:49:00 ns1 kernel: [22126.063923] Exception stack(0xb993df38 to 0xb993df80)
May 9 04:49:00 ns1 kernel: [22126.063931] df20: 80109b94 00000000
May 9 04:49:00 ns1 kernel: [22126.063944] df40: 60000093 8011a2e0 80d04f68 b993c000 80d04fb0 00000008 80d984b4 410fd034
May 9 04:49:00 ns1 kernel: [22126.063956] df60: 00000000 b993df94 80d0535c b993df88 00000000 80109b98 60000013 ffffffff
May 9 04:49:00 ns1 kernel: [22126.063964] r4:80109b98 r3:e7001423
May 9 04:49:00 ns1 kernel: [22126.063981] [<80109b64>] (arch_cpu_idle) from [<808c4edc>] (default_idle_call+0x34/0x48)
May 9 04:49:00 ns1 kernel: [22126.063994] [<808c4ea8>] (default_idle_call) from [<801533e4>] (do_idle+0xec/0x170)
May 9 04:49:00 ns1 kernel: [22126.064006] [<801532f8>] (do_idle) from [<80153744>] (cpu_startup_entry+0x28/0x2c)
May 9 04:49:00 ns1 kernel: [22126.064019] r8:0000406a r7:80da9878 r6:10c0387d r5:00000003 r4:0000008a r3:e7001423
May 9 04:49:00 ns1 kernel: [22126.064033] [<8015371c>] (cpu_startup_entry) from [<8010fd94>] (secondary_start_kernel+0x130/0x13c)
May 9 04:49:00 ns1 kernel: [22126.064047] [<8010fc64>] (secondary_start_kernel) from [<001027ac>] (0x1027ac)
May 9 04:49:00 ns1 kernel: [22126.064054] r5:00000055 r4:3992806a
May 9 04:49:00 ns1 kernel: [22126.064068] ---[ end trace ba7a5eda52d6df92 ]---

Not sure what i can do to trace/get more info, for when this problem occurs again.

FYI :)

pboh
Posts: 13
Joined: Wed Oct 31, 2018 2:26 pm

Re: Moving Linux Kernel to 5.4

Sun May 10, 2020 9:18 pm

Updated the 8822bu driver with new source and it appears to be working OK now. No more kernel panics etc.


MrEngman
Working great now, thank you for your help!

kyli
Posts: 2
Joined: Sun May 10, 2020 11:22 pm

Re: Moving Linux Kernel to 5.4

Mon May 11, 2020 12:00 am

RNDIS USB gadget breaks on my Pi 4 after upgrading to kernel 5.4.

To reproduce the problem, one can follow the instructions here - https://www.factoryforward.com/pi-zero- ... -resolved/ - and observe the difference between kernel 4.19 and 5.4.
Attachments
RNDIS_failed.png
RNDIS_failed.png (116.16 KiB) Viewed 2768 times

kyli
Posts: 2
Joined: Sun May 10, 2020 11:22 pm

Re: Moving Linux Kernel to 5.4

Mon May 11, 2020 9:41 am

kyli wrote:
Mon May 11, 2020 12:00 am
RNDIS USB gadget breaks on my Pi 4 after upgrading to kernel 5.4.

To reproduce the problem, one can follow the instructions here - https://www.factoryforward.com/pi-zero- ... -resolved/ - and observe the difference between kernel 4.19 and 5.4.

Strange.... It's been on and off. However, on OpenWrt, which these kernel patches ported to, this fails consistently will logs like

Code: Select all

[ 2259.991384] rndis_msg_parser: unknown RNDIS message 0x00520328 len 4456526
[ 2259.998275] RNDIS command error -524, 24/24
Will try to run more tests.

LewisCowles1986
Posts: 13
Joined: Fri Mar 18, 2016 9:24 pm

Re: Moving Linux Kernel to 5.4

Mon May 11, 2020 12:05 pm

4.9 user here. Had some issues with RNDIS anyway. Have you tried manally using "update driver" and selecting microsoft RNDIS driver (not RNDIS6)?

I'm very interested in keeping gadget mode.

Covin
Posts: 1
Joined: Mon May 11, 2020 10:01 pm

Re: Moving Linux Kernel to 5.4

Mon May 11, 2020 10:53 pm

On updating the kernel to 5.4 now my tv at 4k60hz start to flicker and after some second disconnects.
The problem seems to arise only when I update the kernel, with the 4.9 it works without any problem.

6by9
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 9324
Joined: Wed Dec 04, 2013 11:27 am
Location: ZZ9 Plural Z Alpha, aka just outside Cambridge.

Re: Moving Linux Kernel to 5.4

Tue May 12, 2020 12:58 pm

Report of issues in Chromium for fullscreen video if the compositor is disabled. viewtopic.php?f=28&t=273509
Software Engineer at Raspberry Pi Trading. Views expressed are still personal views.
I'm not interested in doing contracts for bespoke functionality - please don't ask.

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5572
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Moving Linux Kernel to 5.4

Tue May 12, 2020 2:48 pm

New update. Note this changes the firmware alsa (not the vc4 kms one) to be separate devices for the two hdmi ports and analogue, rather than a single device with an output switch.

This matches upstream behaviour. In theory not much should change, but you may need to reselect the default audio device in desktop audio control.

Apps that support audio device switching outside of X may need to be updated. Report here if there are issues.

User avatar
dickon
Posts: 1660
Joined: Sun Dec 09, 2012 3:54 pm
Location: Home, just outside Reading

Re: Moving Linux Kernel to 5.4

Tue May 12, 2020 3:10 pm

Which branch, sorry? BRANCH=next is reporting that I'm up to date.

trejan
Posts: 2341
Joined: Tue Jul 02, 2019 2:28 pm

Re: Moving Linux Kernel to 5.4

Tue May 12, 2020 3:17 pm

dickon wrote:
Tue May 12, 2020 3:10 pm
Which branch, sorry? BRANCH=next is reporting that I'm up to date.
It is the regular branch now.

User avatar
dickon
Posts: 1660
Joined: Sun Dec 09, 2012 3:54 pm
Location: Home, just outside Reading

Re: Moving Linux Kernel to 5.4

Tue May 12, 2020 3:32 pm

So it is. Ta.

User avatar
dickon
Posts: 1660
Joined: Sun Dec 09, 2012 3:54 pm
Location: Home, just outside Reading

Re: Moving Linux Kernel to 5.4

Tue May 12, 2020 8:03 pm

Not quite sure what's going on here, but:

* 32b kernel crashes with gpu_mem=384 ('memory deadlocked', apparently),
* 64b kernel can't play video, vlc fails to create a dbus interface (no idea why), and fails to start the wifi interface.

So, so-so.

User avatar
DougieLawson
Posts: 39610
Joined: Sun Jun 16, 2013 11:19 pm
Location: A small cave in deepest darkest Basingstoke, UK
Contact: Website Twitter

Re: Moving Linux Kernel to 5.4

Tue May 12, 2020 8:18 pm

dickon wrote:
Tue May 12, 2020 8:03 pm
Not quite sure what's going on here, but:

* 32b kernel crashes with gpu_mem=384 ('memory deadlocked', apparently),
* 64b kernel can't play video, vlc fails to create a dbus interface (no idea why), and fails to start the wifi interface.

So, so-so.
Have you got the latest VLC, there was a broken version from plain DebIan that sneaked out within the last two weeks? There's been two RPi versions since that.

sudo apt update; sudo apt install --reinstall vlc should fix it.
Note: Any requirement to use a crystal ball or mind reading will result in me ignoring your question.

Criticising any questions is banned on this forum.

Any DMs sent on Twitter will be answered next month.
All fake doctors are on my foes list.

User avatar
dickon
Posts: 1660
Joined: Sun Dec 09, 2012 3:54 pm
Location: Home, just outside Reading

Re: Moving Linux Kernel to 5.4

Tue May 12, 2020 8:21 pm

Code: Select all

vlc is already the newest version (3.0.10-0+deb10u1+rpt2).

BuMRK
Posts: 1
Joined: Thu May 14, 2020 11:48 am

Re: Moving Linux Kernel to 5.4

Thu May 14, 2020 11:53 am

[ 17.897708] ------------[ cut here ]------------
[ 17.898301] WARNING: CPU: 2 PID: 153 at net/wireless/sme.c:1088 __cfg80211_disconnected+0x554/0x5a0 [cfg80211]
[ 17.898316] Modules linked in: w1_therm w1_gpio wire cn ip6table_filter ip6_tables xt_MASQUERADE iptable_nat nf_nat nf_conntrack nf_defrag_ipv4 xt_comment xt_tcpudp xt_multiport iptable_filter binfmt_misc joydev spidev 8192cu evdev sha256_generic libsha256 cfg80211 rfkill raspberrypi_ts input_polldev raspberrypi_hwmon hwmon i2c_bcm2835 spi_bcm2835 snd_bcm2835(C) bcm2835_codec(C) bcm2835_isp(C) bcm2835_v4l2(C) v4l2_mem2mem bcm2835_mmal_vchiq(C) videobuf2_vmalloc videobuf2_dma_contig snd_pcm videobuf2_memops videobuf2_v4l2 videobuf2_common snd_timer snd vc_sm_cma(C) videodev mc rpi_backlight backlight uio_pdrv_genirq uio fixed i2c_bcm2708 i2c_dev ip_tables x_tables ipv6 nf_defrag_ipv6
[ 17.898567] CPU: 2 PID: 153 Comm: kworker/u8:2 Tainted: G C 5.4.40-v7+ #1316
[ 17.898573] Hardware name: BCM2835
[ 17.898872] Workqueue: cfg80211 cfg80211_event_work [cfg80211]
[ 17.898882] Backtrace:
[ 17.898906] [<8010d458>] (dump_backtrace) from [<8010d750>] (show_stack+0x20/0x24)
[ 17.898920] r6:a7b66000 r5:00000000 r4:80d930f4 r3:ea6bfd83
[ 17.898937] [<8010d730>] (show_stack) from [<808a4b04>] (dump_stack+0xe0/0x124)
[ 17.898952] [<808a4a24>] (dump_stack) from [<8011fd24>] (__warn+0xec/0x104)
[ 17.898966] r8:00000440 r7:00000009 r6:7f305168 r5:00000000 r4:00000000 r3:ea6bfd83
[ 17.898980] [<8011fc38>] (__warn) from [<8011fdf4>] (warn_slowpath_fmt+0xb8/0xc0)
[ 17.898993] r9:7f305168 r8:00000440 r7:7f2da8c8 r6:00000009 r5:00000000 r4:80d04f48
[ 17.899252] [<8011fd40>] (warn_slowpath_fmt) from [<7f2da8c8>] (__cfg80211_disconnected+0x554/0x5a0 [cfg80211])
[ 17.899267] r9:00000000 r8:00000000 r7:a4bed824 r6:a4bed800 r5:a9b3c000 r4:a896f9c0
[ 17.899736] [<7f2da374>] (__cfg80211_disconnected [cfg80211]) from [<7f2a5b34>] (cfg80211_process_wdev_events+0x13c/0x160 [cfg80211])
[ 17.899751] r10:00000100 r9:00000122 r8:a4bed88c r7:a4bed824 r6:a4bed894 r5:a4bed800
[ 17.899756] r4:a1228b80
[ 17.900224] [<7f2a59f8>] (cfg80211_process_wdev_events [cfg80211]) from [<7f2a5b98>] (cfg80211_process_rdev_events+0x40/0x98 [cfg80211])
[ 17.900239] r10:00000000 r9:00000100 r8:00000000 r7:a884ab00 r6:aa080400 r5:a896fc60
[ 17.900244] r4:a4bed800
[ 17.900712] [<7f2a5b58>] (cfg80211_process_rdev_events [cfg80211]) from [<7f29f1b8>] (cfg80211_event_work+0x24/0x2c [cfg80211])
[ 17.900720] r5:a883e700 r4:a896f8e4
[ 17.900966] [<7f29f194>] (cfg80211_event_work [cfg80211]) from [<8013bcfc>] (process_one_work+0x17c/0x4b4)
[ 17.900974] r4:a896f8e4 r3:7f29f194
[ 17.900990] [<8013bb80>] (process_one_work) from [<8013c564>] (worker_thread+0x54/0x5b4)
[ 17.901003] r10:a883e700 r9:a7b66038 r8:80d03d00 r7:aa080418 r6:00000088 r5:a883e714
[ 17.901009] r4:aa080400
[ 17.901024] [<8013c510>] (worker_thread) from [<80142948>] (kthread+0x13c/0x168)
[ 17.901037] r10:a9b59b5c r9:aa2b7e74 r8:8013c510 r7:a883e700 r6:00000000 r5:a7b83200
[ 17.901042] r4:a9b59b40
[ 17.901055] [<8014280c>] (kthread) from [<801010ac>] (ret_from_fork+0x14/0x28)
[ 17.901061] Exception stack(0xa7b67fb0 to 0xa7b67ff8)
[ 17.901070] 7fa0: 00000000 00000000 00000000 00000000
[ 17.901080] 7fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 17.901088] 7fe0: 00000000 00000000 00000000 00000000 00000013 00000000
[ 17.901099] r10:00000000 r9:00000000 r8:00000000 r7:00000000 r6:00000000 r5:8014280c
[ 17.901105] r4:a7b83200 r3:80104648
[ 17.901112] ---[ end trace c4a46e5cc0330db1 ]---
[ 18.051499] can: controller area network core (rev 20170425 abi 9)
[ 18.051770] NET: Registered protocol family 29
[ 18.077207] can: raw protocol (rev 20170425)
[ 18.502486] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC1E1
[ 25.689761] tun: Universal TUN/TAP device driver, 1.6
[ 363.074935] ------------[ cut here ]------------
[ 363.075596] WARNING: CPU: 0 PID: 153 at net/wireless/sme.c:1088 __cfg80211_disconnected+0x554/0x5a0 [cfg80211]
[ 363.075612] Modules linked in: tun can_raw can w1_therm w1_gpio wire cn ip6table_filter ip6_tables xt_MASQUERADE iptable_nat nf_nat nf_conntrack nf_defrag_ipv4 xt_comment xt_tcpudp xt_multiport iptable_filter binfmt_misc joydev spidev 8192cu evdev sha256_generic libsha256 cfg80211 rfkill raspberrypi_ts input_polldev raspberrypi_hwmon hwmon i2c_bcm2835 spi_bcm2835 snd_bcm2835(C) bcm2835_codec(C) bcm2835_isp(C) bcm2835_v4l2(C) v4l2_mem2mem bcm2835_mmal_vchiq(C) videobuf2_vmalloc videobuf2_dma_contig snd_pcm videobuf2_memops videobuf2_v4l2 videobuf2_common snd_timer snd vc_sm_cma(C) videodev mc rpi_backlight backlight uio_pdrv_genirq uio fixed i2c_bcm2708 i2c_dev ip_tables x_tables ipv6 nf_defrag_ipv6
[ 363.075931] CPU: 0 PID: 153 Comm: kworker/u8:2 Tainted: G WC 5.4.40-v7+ #1316
[ 363.075938] Hardware name: BCM2835
[ 363.076295] Workqueue: cfg80211 cfg80211_event_work [cfg80211]
[ 363.076305] Backtrace:
[ 363.076334] [<8010d458>] (dump_backtrace) from [<8010d750>] (show_stack+0x20/0x24)
[ 363.076350] r6:a7b66000 r5:00000000 r4:80d930f4 r3:ea6bfd83
[ 363.076369] [<8010d730>] (show_stack) from [<808a4b04>] (dump_stack+0xe0/0x124)
[ 363.076388] [<808a4a24>] (dump_stack) from [<8011fd24>] (__warn+0xec/0x104)
[ 363.076405] r8:00000440 r7:00000009 r6:7f305168 r5:00000000 r4:00000000 r3:ea6bfd83
[ 363.076423] [<8011fc38>] (__warn) from [<8011fdf4>] (warn_slowpath_fmt+0xb8/0xc0)
[ 363.076439] r9:7f305168 r8:00000440 r7:7f2da8c8 r6:00000009 r5:00000000 r4:80d04f48
[ 363.076747] [<8011fd40>] (warn_slowpath_fmt) from [<7f2da8c8>] (__cfg80211_disconnected+0x554/0x5a0 [cfg80211])
[ 363.076765] r9:00000000 r8:00000000 r7:a4bed824 r6:a4bed800 r5:a9b3c000 r4:a896f9c0
[ 363.077332] [<7f2da374>] (__cfg80211_disconnected [cfg80211]) from [<7f2a5b34>] (cfg80211_process_wdev_events+0x13c/0x160 [cfg80211])
[ 363.077350] r10:00000100 r9:00000122 r8:a4bed88c r7:a4bed824 r6:a4bed894 r5:a4bed800
[ 363.077357] r4:9e24e280
[ 363.077921] [<7f2a59f8>] (cfg80211_process_wdev_events [cfg80211]) from [<7f2a5b98>] (cfg80211_process_rdev_events+0x40/0x98 [cfg80211])
[ 363.077939] r10:00000000 r9:00000100 r8:00000000 r7:a884ab00 r6:aa080400 r5:a896fc60
[ 363.077946] r4:a4bed800
[ 363.078510] [<7f2a5b58>] (cfg80211_process_rdev_events [cfg80211]) from [<7f29f1b8>] (cfg80211_event_work+0x24/0x2c [cfg80211])
[ 363.078520] r5:a883e700 r4:a896f8e4
[ 363.078815] [<7f29f194>] (cfg80211_event_work [cfg80211]) from [<8013bcfc>] (process_one_work+0x17c/0x4b4)
[ 363.078825] r4:a896f8e4 r3:7f29f194
[ 363.078844] [<8013bb80>] (process_one_work) from [<8013c564>] (worker_thread+0x54/0x5b4)
[ 363.078862] r10:a883e700 r9:a7b66038 r8:80d03d00 r7:aa080418 r6:00000088 r5:a883e714
[ 363.078869] r4:aa080400
[ 363.078887] [<8013c510>] (worker_thread) from [<80142948>] (kthread+0x13c/0x168)
[ 363.078904] r10:a9b59b5c r9:aa2b7e74 r8:8013c510 r7:a883e700 r6:00000000 r5:a7b83200
[ 363.078911] r4:a9b59b40
[ 363.078927] [<8014280c>] (kthread) from [<801010ac>] (ret_from_fork+0x14/0x28)
[ 363.078936] Exception stack(0xa7b67fb0 to 0xa7b67ff8)
[ 363.078949] 7fa0: 00000000 00000000 00000000 00000000
[ 363.078963] 7fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 363.078975] 7fe0: 00000000 00000000 00000000 00000000 00000013 00000000
[ 363.078991] r10:00000000 r9:00000000 r8:00000000 r7:00000000 r6:00000000 r5:8014280c
[ 363.079000] r4:a7b83200 r3:80104648
[ 363.079011] ---[ end trace c4a46e5cc0330db2 ]---

hjimbens
Posts: 86
Joined: Fri May 24, 2013 9:05 am

Re: Moving Linux Kernel to 5.4

Thu May 14, 2020 3:00 pm

I just ran sudo rpi-update to check whether https://github.com/raspberrypi/firmware/issues/1382 was fixed and because 5.4 is now on the master branch I accidentally updated to 5.4. My OpenGLES2 application on X11 stopped working. It showed a garbled screen where the pixels seemed to be transposed in a complicated way. This was with dtoverlay=vc4-fkms-v3d. With dtoverlay=vc4-kms-v3d-pi4 the screen remains blank and in dmesg I get:

Code: Select all

[   29.676617] broken atomic modeset userspace detected, disabling atomic
[   40.793201] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:65:crtc-2] flip_done timed out
[   51.033200] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:65:crtc-2] flip_done timed out
[   61.273175] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CONNECTOR:32:HDMI-A-1] flip_done timed out
[   71.513186] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:65:crtc-2] flip_done timed out
.

ckoryom
Posts: 1
Joined: Thu May 14, 2020 5:14 pm

Re: Moving Linux Kernel to 5.4

Thu May 14, 2020 5:16 pm

Hi I have set the new dtoverlay=vc4-kms-v3d-pi4

But now Im not getting a signal on my monitor.

When I go back to the previous dtoverlay I get a signal again.

User avatar
bleep42
Posts: 186
Joined: Wed Mar 07, 2012 12:43 pm
Location: Sussex

Re: Moving Linux Kernel to 5.4

Thu May 14, 2020 6:22 pm

Hi Dom,
While getting my Mandelbrot program to work using the new kernel and "dtoverlay=vc4-kms-v3d" ie, non fake kms I have come across a problem.
If I use VLC to play a video with the current release kernel "Linux raspberrypi 4.19.97-v7l+ #1294 SMP Thu Jan 30 13:21:14 GMT 2020 armv7l GNU/Linux" with "dtoverlay=vc4-kms-v3d" everything works as expected, both 32 and 64bit.

However if I use the new kernel "Linux raspberrypi 5.4.40-v7l+ #1316 SMP Tue May 12 13:10:42 BST 2020 armv7l GNU/Linux" with "dtoverlay=vc4-kms-v3d", I have found that if I move the mouse, inside the active VLC video display area, the whole screen disappears, as though its disconnected, I think this because, when I stop moving the mouse the display pops up a message saying 'HDMI reconnected' and the screen reappears. Interestingly, if I move the mouse outside the active video display area, everything works just fine, by that I mean within the VLC menu area is fine, as is its blue bar at the top of the window and the player controls at the bottom of the window, or anywhere outside the VLC window; this is true for both 32 and 64bit. However if I use "dtoverlay=vc4-fkms-v3d" with the new kernel the problem does not exist. This is on a Pi4 fully updated.

Hope that all makes sense and is of use. If you need any further info. let me know.
Regards, Kevin.

cjan
Posts: 852
Joined: Sun May 06, 2012 12:00 am

Re: Moving Linux Kernel to 5.4

Tue May 19, 2020 6:00 am

dtoverlay=vc4-kms-v3d on Pi2, no analog audio.
last update to 5.4.40.

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5572
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Moving Linux Kernel to 5.4

Wed May 20, 2020 12:15 pm

bleep42 wrote:
Thu May 14, 2020 6:22 pm
I have found that if I move the mouse, inside the active VLC video display area, the whole screen disappears, as though its disconnected, I think this because, when I stop moving the mouse the display pops up a message saying 'HDMI reconnected' and the screen reappears. Interestingly, if I move the mouse outside the active video display area
Interesting. It does sound similar to this issue. Might be worth commenting there.

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5572
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Moving Linux Kernel to 5.4

Wed May 20, 2020 12:18 pm

ckoryom wrote:
Thu May 14, 2020 5:16 pm
Hi I have set the new dtoverlay=vc4-kms-v3d-pi4

But now Im not getting a signal on my monitor.

When I go back to the previous dtoverlay I get a signal again.
So you get a signal with vc4-fkms-v3d?
What resolution/framerate does it use when working?

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5572
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Moving Linux Kernel to 5.4

Wed May 20, 2020 12:41 pm

cjan wrote:
Tue May 19, 2020 6:00 am
dtoverlay=vc4-kms-v3d on Pi2, no analog audio.
last update to 5.4.40.
There is no arm side analogue driver. You probably want:

Code: Select all

dtparam=audio=on
dtoverlay=vc4-kms-v3d,audio=off
Also note this post about separate alsa devices.

rcfa
Posts: 15
Joined: Sun Feb 25, 2018 5:22 am

Re: Moving Linux Kernel to 5.4

Wed May 20, 2020 7:04 pm

I ran rpi-update, rebooted, and things so far work, BUT more later.

Here the output of uname:

Code: Select all

root@raspberrypi:~ # uname -a
Linux raspberrypi 5.4.42-v7+ #1319 SMP Wed May 20 14:06:11 BST 2020 armv7l GNU/Linux
root@raspberrypi:~ #
So far so good. However, /boot/kernel8.img doesn't exist, and thus I also can't test the 64-bit kernel
I got two machines a 3B and 3B+, both of which should be 64-bit capable, but as can be seen here, rpi-update doesn't download the necessary files:

Code: Select all

root@raspberrypi:~ # rpi-update
 *** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
 *** Performing self-update
 *** Relaunching after update
 *** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
#############################################################
WARNING: This update bumps to rpi-5.4.y linux tree
See: https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=269769

'rpi-update' should only be used if there is a specific
reason to do so - for example, a request by a Raspberry Pi
engineer or if you want to help the testing effort
and are comfortable with restoring if there are regressions.

DO NOT use 'rpi-update' as part of a regular update process.

##############################################################
Would you like to proceed? (y/N)
 *** Downloading specific firmware revision (this will take a few minutes)
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   168  100   168    0     0   1448      0 --:--:-- --:--:-- --:--:--  1435
100  115M  100  115M    0     0  2200k      0  0:00:53  0:00:53 --:--:-- 2586k
 *** Updating firmware
 *** Updating kernel modules
 *** depmod 5.4.42+
 *** depmod 5.4.42-v7+
 *** Updating VideoCore libraries
 *** Using HardFP libraries
 *** Updating SDK
 *** Running ldconfig
 *** Storing current firmware revision
 *** Deleting downloaded files
 *** Syncing changes to disk
 *** If no errors appeared, your firmware was successfully updated to b28e2bc11d7dd1aec923a389bc570eddb9343309
 *** A reboot is needed to activate the new firmware
root@raspberrypi:~ # ls /boot
bcm2708-rpi-b.dtb       bcm2708-rpi-zero-w.dtb    bcm2710-rpi-cm3.dtb  COPYING.linux  issue.txt         overlays
bcm2708-rpi-b-plus.dtb  bcm2709-rpi-2-b.dtb       bcm2711-rpi-4-b.dtb  fixup_cd.dat   kernel7.img       start_cd.elf
bcm2708-rpi-b-rev1.dtb  bcm2710-rpi-2-b.dtb       bootcode.bin         fixup.dat      kernel.img        start_db.elf
bcm2708-rpi-cm.dtb      bcm2710-rpi-3-b.dtb       cmdline.txt          fixup_db.dat   LICENCE.broadcom  start.elf
bcm2708-rpi-zero.dtb    bcm2710-rpi-3-b-plus.dtb  config.txt           fixup_x.dat    LICENSE.oracle    start_x.elf
root@raspberrypi:~ #
What magic thing must I do to convince rpi-update to also install the 64-bit kernel?

Thanks!

Return to “Advanced users”