Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #65060 > unrolled thread

Bug#939633: Rpi3+ hangs with kernel 5.2 device_tree

Back to article view | Back to linux.debian.kernel

Contents

  Bug#939633: Rpi3+ hangs with kernel 5.2 device_tree eHenry Berg <ehenry.berg@gmail.com> - 2019-09-07 09:00 +0200
    Bug#939633: linux: rpi3b+ hangs with kernels 5.2, 5.3 (device tree issue?) Thorsten Glaser <t.glaser@tarent.de> - 2019-11-20 20:00 +0100
      Processed: Re: linux: rpi3b+ hangs with kernels 5.2, 5.3 (device  tree issue?) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2019-11-20 20:00 +0100
    Bug#939633: More severe #939633 for RP4 on 5.8? Elliott Mitchell <ehem+debian@m5p.com> - 2020-11-26 03:00 +0100
      Processed (with 1 error): More severe #939633 for RP4 on 5.8? "Debian Bug Tracking System" <owner@bugs.debian.org> - 2020-11-26 03:00 +0100
      Bug#939633: More severe #939633 for RP4 on 5.8? Elliott Mitchell <ehem+debian@m5p.com> - 2020-11-28 05:50 +0100
        Processed: Re: More severe #939633 for RP4 on 5.8? "Debian Bug Tracking System" <owner@bugs.debian.org> - 2020-11-28 05:50 +0100
        Bug#939633: More severe #939633 for RP4 on 5.8? Ben Hutchings <ben@decadent.org.uk> - 2020-12-13 19:10 +0100

#65060 — Bug#939633: Rpi3+ hangs with kernel 5.2 device_tree

Package: linux-image-armmp
Version: 5.2.0-2

Hello,

I have made a guide for Debian on Rpi here:
https://github.com/evasjo/DebianSbcRaspberry

I have 1 device (Rpi3+) and 2 environments (cards).

            armhfCard	arm64Card
4.19.0-5    Success     Success
5.2.0-2     Failure     Failure

New firmware for armhfCard	2018-08-05 -> 2019-08-17	// It did not help.
New firmware for arm64Card	2018-12-25 -> 2019-08-17	// It did not help.

# cat cmdline.txt
dwc_otg.lpm_enable=0 console=tty0 root=/dev/mmcblk0p3 rootfstype=f2fs
elevator=deadline fsck.repair=yes rootwait cma=416M

# cat config.txt   // armhfCard
device_tree=bcm2837-rpi-3-b-plus.dtb.5.2
kernel=vmlinuz-5.2.0-2-armmp
initramfs initrd.img-5.2.0-2-armmp followkernel

# cat config.txt    // arm64Card
arm_control=0x200
device_tree=bcm2837-rpi-3-b-plus.dtb.5.2
kernel=vmlinuz-5.2.0-2-arm64
initramfs initrd.img-5.2.0-2-arm64 followkernel

# cat /etc/apt/sources.list
deb http://ftp.fi.debian.org/debian sid main contrib non-free

# cat /etc/initramfs-tools/modules
crc32
crc32c
f2fs

# cat /etc/modules
f2fs
vc4

# cat /etc/dphys-swapfile
 CONF_SWAPSIZE=1024     // This row is uncommented

# uname -a      // armhfCard
Linux irena 5.2.0-2-armmp #1 SMP Debian 5.2.9-2 (2019-08-21) armv7l GNU/Linux

# uname -a      // arm64Card
Linux atlas 5.2.0-2-arm64 #1 SMP Debian 5.2.9-2 (2019-08-21) aarch64 GNU/Linux

# less /var/log/syslog.1| grep "bcm2835-power"  // No new errors (ASB)
# zcat /var/log/syslog.2.gz| grep "bcm2835-power"    // No new errors (ASB)
# zcat /var/log/syslog.3.gz| grep "bcm2835-power"    // No new errors (ASB)

Error cases below are with 5.2 kernel and its device_tree.
"Hangs" below means that you cannot do anything more with your mouse
or keyboard. You have to switch off and on the electricity.

Reproducible errors:

ReprodError1 week35:  // armhfCard  // Intermittent error week36
a. Start the computer and wait for the SDDM display manager
b. Give Ctrl + Alt + F2 and wait approximately 5 seconds
c. It writes below the login row: "bcm2835-power bcm2835-power: Failed
to disable ASB master for v3d"    // Hangs.

ReprodErrorAvoid1 week35:  // armhfCard
a. Start the computer and wait for the SDDM display manager
b. Give Ctrl + Alt + F2
c. Login with root
d. # tail -f /var/log/syslog

ReprodError2:  // arm64Card
a. Start the computer and wait for the SDDM display manager
b. Login with the keyboard, but do not touch the mouse.
c. Kde start normally and everything is visible.  // Hangs.

ReprodErrorAvoid2:  // arm64Card.
a. Start the computer and wait for the SDDM display manager
b. Login with the keyboard and move the mouse (little is enough).
c. Kde start normally and works for the time being.

ReprodError3 week36:  // armhfCard
a. Start the computer and wait for the SDDM display manager
b. Wait for the cursor to blink in the input field 40-45 seconds. // Hangs

Intermittent errors:

IntermError1:  // arm64Card and armhfCard
a. Start Kde
b. Push the Window key and write for example fakon
c. Backspace (try correct it to falkon)     // Hangs

IntermError2:  // armhfCard.
a. Start Kde
b. Start Konsole and # tail -f /var/log/syslog  // No additonal
(error) rows after the computer was hanged
c. Start editor Kate and a file and arrow key down  // Hangs. The
mouse cursor was gone.

IntermError3:  // armhfCard.
a. Start Kde
b. Start Konsole and # tail -f /var/log/syslog  // No additonal
(error) rows after the computer was hanged
c. Start browser Falkon  // Hangs. The Falkon window, the mouse cursor
and everything else, were visible.

IntermError4:  // armhfCard.
a. Start the computer and wait for the SDDM display manager
b. Give password and enter  // Hangs

IntermError5:  // ar64fCard.
a. Start Kde
b. Start browser Falkon
c. Give url address and choose arrow down to the right in the window.  // Hangs.


Graphic in kernel 4.19.0-5 works without any problem (maybe locks few
times per month and a break of electricity is needed).
Graphic in kernel 5.2 with its device_tree, locks few times per hour
and a break of electricity is needed.

I have a feeling that the culprit is the error message "bcm2835-power
bcm2835-power: Failed to disable ASB master for v3d" which I got for
"ReprodError1" for armhfCard.

This configuration works (device_tree from kernel 4.19), but then
"bcm2835-power" is not used:
# cat config.txt
device_tree=bcm2837-rpi-3-b-plus.dtb.4.19
kernel=vmlinuz-5.2.0-2-armmp
initramfs initrd.img-5.2.0-2-armmp followkernel

Best Regards,
Evald

[toc] | [next] | [standalone]

#65699 — Bug#939633: linux: rpi3b+ hangs with kernels 5.2, 5.3 (device tree issue?)

retitle 939633 linux: rpi3b+ hangs with kernels 5.2, 5.3 (device tree issue?)
notfound 939633 4.19.67-2+deb10u1
notfound 939633 4.19.67-2+deb10u2
found 939633 5.2.9-2~bpo10+1
found 939633 5.2.17-1~bpo10+1
found 939633 5.3.9-3
thanks

We’re currently suffering from a similar situation.

Debian buster/arm64 installation, straight from this script:
https://evolvis.org/plugins/scmgit/cgi-bin/gitweb.cgi?p=shellsnippets/shellsnippets.git;a=blob;f=posix/mkrpi3b%2Bimg.sh;hb=HEAD

With the buster kernel, the analog audio doesn’t work, and
3D graphics using llvmpipe are really slow, but the system
is, overall, stable.

With the backports kernel and either buster’s raspi3-firmware
or sid’s raspi-firmware (tested both), 3D graphics are accelerated,
poweroff/reboot don’t work, and the system crashes after some
uptime (confirmed it’s not a thermal issue, and the official
PSU is used, so power is enough).

With the sid kernel and sid’s raspi-firmware, the same issue
happens. We managed to get a serial console running, and the
crash message is what led us to this bugreport:

[timestamp] bcm2835-power bcm2835-power: Failed to disable ASB master for v3d

This is a fairly stock setup, with CMA raised to 128M and
consoles fixed (see the outstanding bugreports in the
raspi3-firmware/raspi-firmware package), and video size fixed:

tglase@tglase:/mnt $ grep '^[^#]' etc/default/raspi-firmware
CMA=128M
CONSOLES='ttyS1,115200 tty0'
tglase@tglase:/mnt $ cat etc/default/raspi-firmware-custom 
disable_overscan=1


Incidentally, shortly before, we see this in syslog:

Jan  1 01:00:26 rpi3bplus kernel: [   26.255342] broken atomic modeset userspace detected, disabling atomic

Unsure whether it’s related.


Other things are reports in Fedora with instabilities relating
to the RPi 3B+ and power management…

Please advice as to a fix ☻

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

**********

Mit der tarent Academy bieten wir auch Trainings und Schulungen in den
Bereichen Softwareentwicklung, Agiles Arbeiten und Zukunftstechnologien an.

Besuchen Sie uns auf www.tarent.de/academy. Wir freuen uns auf Ihren Kontakt.

**********

[toc] | [prev] | [next] | [standalone]

#65700 — Processed: Re: linux: rpi3b+ hangs with kernels 5.2, 5.3 (device tree issue?)

Processing commands for control@bugs.debian.org:

> retitle 939633 linux: rpi3b+ hangs with kernels 5.2, 5.3 (device tree issue?)
Bug #939633 [src:linux] Rpi3+ hangs with kernel 5.2 device_tree
Changed Bug title to 'linux: rpi3b+ hangs with kernels 5.2, 5.3 (device tree issue?)' from 'Rpi3+ hangs with kernel 5.2 device_tree'.
> notfound 939633 4.19.67-2+deb10u1
Bug #939633 [src:linux] linux: rpi3b+ hangs with kernels 5.2, 5.3 (device tree issue?)
Ignoring request to alter found versions of bug #939633 to the same values previously set
> notfound 939633 4.19.67-2+deb10u2
Bug #939633 [src:linux] linux: rpi3b+ hangs with kernels 5.2, 5.3 (device tree issue?)
Ignoring request to alter found versions of bug #939633 to the same values previously set
> found 939633 5.2.9-2~bpo10+1
Bug #939633 [src:linux] linux: rpi3b+ hangs with kernels 5.2, 5.3 (device tree issue?)
Marked as found in versions linux/5.2.9-2~bpo10+1.
> found 939633 5.2.17-1~bpo10+1
Bug #939633 [src:linux] linux: rpi3b+ hangs with kernels 5.2, 5.3 (device tree issue?)
Marked as found in versions linux/5.2.17-1~bpo10+1.
> found 939633 5.3.9-3
Bug #939633 [src:linux] linux: rpi3b+ hangs with kernels 5.2, 5.3 (device tree issue?)
Marked as found in versions linux/5.3.9-3.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
939633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939633
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#68672 — Bug#939633: More severe #939633 for RP4 on 5.8?

found 939633 5.8.10-1~bpo10+1
severity 939633 important
merge 935456 939633
quit

I'm left suspecting bugs #935456 and #939633, are in reality a single
bug: Raspberry Pi device trees were garbled during Debian's 5.2 kernel
development.

They appear to remain very garbled, to the point of being pretty well
useless.  I've built a kernel from Debian's 5.8 kernel source and the
device tree binary produced doesn't appear to allow a Raspberry PI 4B
to complete its boot.  Might be USB functionality is operational, but
neither ethernet interface nor display function.

Ironically, the additional ACPI/EFI support DOES function.  This means
the Tianocore image for Raspberry PI 4B works better with the current
source.

I'm unsure whether badly breaking all Raspberry PI variants quite
justifies critical or grave (popular machine, but kernel issues by nature
cause 10x the damage so severities should be somewhat damped).

I certainly hope to see the 5.9 release since that has additional
high-value improvements...


-- 
(\___(\___(\______          --=> 8-) EHM <=--          ______/)___/)___/)
 \BS (    |         ehem+sigmsg@m5p.com  PGP 87145445         |    )   /
  \_CS\   |  _____  -O #include <stddisclaimer.h> O-   _____  |   /  _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445

[toc] | [prev] | [next] | [standalone]

#68673 — Processed (with 1 error): More severe #939633 for RP4 on 5.8?

Processing commands for control@bugs.debian.org:

> found 939633 5.8.10-1~bpo10+1
Bug #939633 [src:linux] linux: rpi3b+ hangs with kernels 5.2, 5.3 (device tree issue?)
Marked as found in versions linux/5.8.10-1~bpo10+1.
> severity 939633 important
Bug #939633 [src:linux] linux: rpi3b+ hangs with kernels 5.2, 5.3 (device tree issue?)
Severity set to 'important' from 'normal'
> merge 935456 939633
Bug #935456 [src:linux] No GPU hardware detected with kernel 5.2 for Rpi2b and Rpi3b
Unable to merge bugs because:
severity of #939633 is 'important' not 'normal'
Failed to merge 935456: Did not alter merged bugs.

> quit
Stopping processing here.

Please contact me if you need assistance.
-- 
935456: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935456
939633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939633
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#68705 — Bug#939633: More severe #939633 for RP4 on 5.8?

found 935456 5.9.6-1~bpo10+1
quit

After having spent several hours on kernel compiles and experimenting
with the situation, I'm fairly sure this also applies to
linux-source-5.9.

Odd thing is, when I booted the device using the Tianocore implementation
it came right up with no problems.  I'm getting this odd suspicion
someone deliberately broke the device-trees in Debian's kernel source.
The goal being to force everyone onto the Tianocore/ACPI implementation
and try to kill device-trees.

Right now I think this is conspiracy theory territory, but I'm left
wondering how such a serious bug could hang around so long...


-- 
(\___(\___(\______          --=> 8-) EHM <=--          ______/)___/)___/)
 \BS (    |         ehem+sigmsg@m5p.com  PGP 87145445         |    )   /
  \_CS\   |  _____  -O #include <stddisclaimer.h> O-   _____  |   /  _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445

[toc] | [prev] | [next] | [standalone]

#68706 — Processed: Re: More severe #939633 for RP4 on 5.8?

Processing commands for control@bugs.debian.org:

> found 935456 5.9.6-1~bpo10+1
Bug #935456 [src:linux] linux: Raspberry PI device-trees corrupt on >=5.2
Bug #939633 [src:linux] linux: Raspberry PI device-trees corrupt on >=5.2
Marked as found in versions linux/5.9.6-1~bpo10+1.
Marked as found in versions linux/5.9.6-1~bpo10+1.
> quit
Stopping processing here.

Please contact me if you need assistance.
-- 
935456: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935456
939633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939633
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#68841 — Bug#939633: More severe #939633 for RP4 on 5.8?

[Multipart message — attachments visible in raw view] — view raw

On Fri, 2020-11-27 at 20:41 -0800, Elliott Mitchell wrote:
> found 935456 5.9.6-1~bpo10+1
> quit
> 
> After having spent several hours on kernel compiles and experimenting
> with the situation, I'm fairly sure this also applies to
> linux-source-5.9.
> 
> Odd thing is, when I booted the device using the Tianocore implementation
> it came right up with no problems.  I'm getting this odd suspicion
> someone deliberately broke the device-trees in Debian's kernel source.
> The goal being to force everyone onto the Tianocore/ACPI implementation
> and try to kill device-trees.
> 
> Right now I think this is conspiracy theory territory, but I'm left
> wondering how such a serious bug could hang around so long...

We don't patch any of this stuff.  Any bugs in the device trees that we
ship come from the upstream kernel, and need to be fixed there.  No-
one's deliberately breaking this in Debian, and you had better stop
making accusations like that.

Ben. 

-- 
Ben Hutchings
The two most common things in the universe are hydrogen and stupidity.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web