[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#991714: marked as done (linux-image-5.10.0-8-arm64: RPi 4 (8 GB) - CPU stuck in highest speed)



Your message dated Fri, 24 Sep 2021 12:30:14 +0200
with message-id <6261232.o1o50VpPJW@bagend>
and subject line Re: Bug#991714: linux-image-5.10.0-8-arm64: RPi 4 (8 GB) - CPU stuck in highest speed
has caused the Debian Bug report #991714,
regarding linux-image-5.10.0-8-arm64: RPi 4 (8 GB) - CPU stuck in highest speed
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
991714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991714
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 5.10.46-3
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

Looking into the instability of my RPi 4 (8GB) showed the CPU constantly
in the highest clock setting with a load of 0 and 99.5%+ idle state.

The instability was 1st discovered after updates in januari, but unable
to get researched until now. (so no clue which kernel version triggered
it, I expect a 5.x kernel, as on 4.9 it was stable)

I tried setting the default govenour (performance, tad optimistic for an arm)
to ondemand, powersave and schedutil and install cpufreqd, but cpufreqd
reports no cpufreq support.

The CPU reports to be full-time in the highest speed. Only way to limit
the highest speed is to set arm_freq in /boot/firmware/config.txt to a
lower max cpu freq. (testing with 1000 now)

Running fulltime at 1500 MHz causes the device to crash several times a
day. (housing is very hot)

I expected the CPU to run in the lowest speed most of the time, as it's
almost fulltime idle. Somehow the kernel doesn't use the governor setting.

The issue is not seen on my RPi3 systems (same kernel, same config, gouvenour
defaults to schedutil there), so I'd guess it's either an RPi4 or specifically
a specific RPi 4 8 GB issue.


-- Package-specific info:
** Version:
Linux version 5.10.0-8-arm64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.46-3 (2021-07-28)

** Command line:
video=HDMI-A-1:1280x1024M@60 dma.dmachans=0x37f5 bcm2709.boardrev=0xd03114 bcm2709.serial=0x5e78c29f bcm2709.uart_clock=48000000 bcm2709.disk_led_gpio=42 bcm2709.disk_led_active_low=0 smsc95xx.macaddr=DC:A6:32:B8:7F:26 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  console=tty0 console=ttyS1,115200 root=/dev/sda1 rw fsck.repair=yes net.ifnames=0  rootwait

** Tainted: C (1024)
 * staging driver was loaded

** Kernel log:
[   22.247985] mc: Linux media interface: v0.10
[   22.260008] bcm2835_audio bcm2835_audio: card created with 8 channels
[   22.313119] videodev: Linux video capture interface: v2.00
[   22.328566] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[   22.330090] usbcore: registered new interface driver brcmfmac
[   22.357834] debugfs: Directory 'fef00700.hdmi' with parent 'vc4-hdmi-0' already present!
[   22.359215] brcmfmac mmc0:0001:1: firmware: direct-loading firmware brcm/brcmfmac43455-sdio.bin
[   22.362740] cryptd: max_cpu_qlen set to 1000
[   22.364355] brcmfmac mmc0:0001:1: firmware: direct-loading firmware brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt
[   22.368338] vc4-drm gpu: bound fef00700.hdmi (ops vc4_hdmi_ops [vc4])
[   22.368822] debugfs: Directory 'fef05700.hdmi' with parent 'vc4-hdmi-1' already present!
[   22.373047] vc4-drm gpu: bound fef05700.hdmi (ops vc4_hdmi_ops [vc4])
[   22.373234] vc4-drm gpu: bound fe400000.hvs (ops vc4_hvs_ops [vc4])
[   22.373552] vc4-drm gpu: bound fe004000.txp (ops vc4_txp_ops [vc4])
[   22.373680] vc4-drm gpu: bound fe206000.pixelvalve (ops vc4_crtc_ops [vc4])
[   22.373784] vc4-drm gpu: bound fe207000.pixelvalve (ops vc4_crtc_ops [vc4])
[   22.373889] vc4-drm gpu: bound fe20a000.pixelvalve (ops vc4_crtc_ops [vc4])
[   22.373962] vc4-drm gpu: bound fe216000.pixelvalve (ops vc4_crtc_ops [vc4])
[   22.374258] checking generic (3e6c7000 500000) vs hw (0 ffffffffffffffff)
[   22.374264] fb0: switching to vc4drmfb from simple
[   22.375966] Console: switching to colour dummy device 80x25
[   22.380163] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[   22.405236] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned.
[   22.411921] [drm] Initialized vc4 0.0.0 20140616 for gpu on minor 0
[   22.498091] Adding 8388948k swap on /dev/sda2.  Priority:-2 extents:1 across:8388948k FS
[   22.498288] Console: switching to colour frame buffer device 160x64
[   22.530659] vc4-drm gpu: [drm] fb0: vc4drmfb frame buffer device
[   22.533470] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[   22.534245] brcmfmac mmc0:0001:1: firmware: direct-loading firmware brcm/brcmfmac43455-sdio.clm_blob
[   22.539177] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Sep 18 2020 02:27:58 version 7.45.221 (3a6d3a0 CY) FWID 01-bbd9282b
[   22.756347] Bluetooth: Core ver 2.22
[   22.756479] NET: Registered protocol family 31
[   22.756484] Bluetooth: HCI device and connection manager initialized
[   22.756799] Bluetooth: HCI socket layer initialized
[   22.756811] Bluetooth: L2CAP socket layer initialized
[   22.756839] Bluetooth: SCO socket layer initialized
[   22.796142] Bluetooth: HCI UART driver ver 2.3
[   22.796159] Bluetooth: HCI UART protocol H4 registered
[   22.796255] Bluetooth: HCI UART protocol LL registered
[   22.796259] Bluetooth: HCI UART protocol ATH3K registered
[   22.796309] Bluetooth: HCI UART protocol Three-wire (H5) registered
[   22.796491] Bluetooth: HCI UART protocol Intel registered
[   22.796614] Bluetooth: HCI UART protocol Broadcom registered
[   22.796645] Bluetooth: HCI UART protocol QCA registered
[   22.796649] Bluetooth: HCI UART protocol AG6XX registered
[   22.796685] Bluetooth: HCI UART protocol Marvell registered
[   22.807722] hci_uart_bcm serial0-0: supply vbat not found, using dummy regulator
[   22.807947] hci_uart_bcm serial0-0: supply vddio not found, using dummy regulator
[   22.850263] audit: type=1400 audit(1627656711.643:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=414 comm="apparmor_parser"
[   22.850286] audit: type=1400 audit(1627656711.643:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=414 comm="apparmor_parser"
[   22.850297] audit: type=1400 audit(1627656711.643:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=416 comm="apparmor_parser"
[   22.850308] audit: type=1400 audit(1627656711.643:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=416 comm="apparmor_parser"
[   22.850318] audit: type=1400 audit(1627656711.643:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=416 comm="apparmor_parser"
[   22.852102] audit: type=1400 audit(1627656711.647:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/ntpd" pid=413 comm="apparmor_parser"
[   22.854562] audit: type=1400 audit(1627656711.651:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="named" pid=415 comm="apparmor_parser"
[   22.859952] audit: type=1400 audit(1627656711.655:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/haveged" pid=417 comm="apparmor_parser"
[   22.863132] audit: type=1400 audit(1627656711.659:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lsb_release" pid=419 comm="apparmor_parser"
[   22.931070] uart-pl011 fe201000.serial: no DMA platform data
[   23.170669] Bluetooth: hci0: BCM: chip id 107
[   23.170962] Bluetooth: hci0: BCM: features 0x2f
[   23.172456] Bluetooth: hci0: BCM4345C0
[   23.172469] Bluetooth: hci0: BCM4345C0 (003.001.025) build 0000
[   23.172580] bluetooth hci0: firmware: failed to load brcm/BCM4345C0.hcd (-2)
[   23.172624] bluetooth hci0: firmware: failed to load brcm/BCM.hcd (-2)
[   23.172631] Bluetooth: hci0: BCM: firmware Patch file not found, tried:
[   23.172634] Bluetooth: hci0: BCM: 'brcm/BCM4345C0.hcd'
[   23.172637] Bluetooth: hci0: BCM: 'brcm/BCM.hcd'
[   23.723829] bcmgenet fd580000.ethernet: configuring instance for external RGMII (RX delay)
[   23.724307] bcmgenet fd580000.ethernet lan0: Link is Down
[   23.874372] 8021q: 802.1Q VLAN Support v1.8
[   23.996819] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[   24.024033] vlan142: port 1(lan0.142) entered blocking state
[   24.024046] vlan142: port 1(lan0.142) entered disabled state
[   24.024284] device lan0.142 entered promiscuous mode
[   24.024289] device lan0 entered promiscuous mode
[   27.806305] bcmgenet fd580000.ethernet lan0: Link is Up - 1Gbps/Full - flow control rx/tx
[   27.806340] IPv6: ADDRCONF(NETDEV_CHANGE): lan0: link becomes ready
[   27.806586] vlan142: port 1(lan0.142) entered blocking state
[   27.806593] vlan142: port 1(lan0.142) entered forwarding state
[   27.806654] IPv6: ADDRCONF(NETDEV_CHANGE): vlan142: link becomes ready
[   29.754940] vlan636: port 1(lan0.636) entered blocking state
[   29.754954] vlan636: port 1(lan0.636) entered disabled state
[   29.755211] device lan0.636 entered promiscuous mode
[   29.769539] vlan636: port 1(lan0.636) entered blocking state
[   29.769553] vlan636: port 1(lan0.636) entered forwarding state
[   32.859998] FS-Cache: Loaded
[   33.027400] FS-Cache: Netfs 'nfs' registered for caching
[   33.054593] Key type dns_resolver registered
[   33.630462] NFS: Registering the id_resolver key type
[   33.630548] Key type id_resolver registered
[   33.630555] Key type id_legacy registered
[   33.704667] FS-Cache: Duplicate cookie detected
[   33.704688] FS-Cache: O-cookie c=000000007d88a875 [p=0000000094ddd261 fl=222 nc=0 na=1]
[   33.704692] FS-Cache: O-cookie d=00000000b8e818af n=0000000062bd0305
[   33.704697] FS-Cache: O-key=[16] '0400000002000000020008010a0d8e06'
[   33.704743] FS-Cache: N-cookie c=00000000e7e20181 [p=0000000094ddd261 fl=2 nc=0 na=1]
[   33.704747] FS-Cache: N-cookie d=00000000b8e818af n=00000000dc8cb286
[   33.704751] FS-Cache: N-key=[16] '0400000002000000020008010a0d8e06'
[   35.261468] capability: warning: `jsvc' uses 32-bit capabilities (legacy support in use)
[   57.636336] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).

** Model information
Device Tree model: Raspberry Pi 4 Model B Rev 1.4

** Loaded modules:
nfsd
binfmt_misc
nfsv3
nfs_acl
rpcsec_gss_krb5
auth_rpcgss
nfsv4
dns_resolver
nfs
lockd
grace
nfs_ssc
fscache
bridge
8021q
garp
mrp
stp
llc
cpufreq_powersave
hci_uart
btqca
btrtl
btbcm
btintel
btsdio
bluetooth
nls_ascii
nls_cp437
vfat
fat
jitterentropy_rng
aes_neon_bs
bcm2835_v4l2(C)
bcm2835_mmal_vchiq(C)
aes_neon_blk
videobuf2_vmalloc
crypto_simd
videobuf2_memops
videobuf2_v4l2
cryptd
videobuf2_common
vc4
videodev
brcmfmac
snd_soc_core
mc
cpufreq_dt
drbg
snd_bcm2835(C)
sg
evdev
brcmutil
aes_arm64
cfg80211
snd_pcm_dmaengine
aes_generic
snd_pcm
ansi_cprng
snd_timer
ecdh_generic
raspberrypi_cpufreq
snd
rfkill
ecc
libaes
soundcore
cec
iproc_rng200
rng_core
pwm_bcm2835
drm_kms_helper
vchiq(C)
bcm2835_wdt
bcm2711_thermal
leds_gpio
cpufreq_ondemand
drm
fuse
configfs
sunrpc
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
hid_generic
usbhid
hid
sd_mod
t10_pi
crc_t10dif
crct10dif_generic
uas
usb_storage
scsi_mod
broadcom
bcm_phy_lib
mdio_bcm_unimac
dwc2
xhci_pci
xhci_hcd
udc_core
roles
crct10dif_ce
crct10dif_common
reset_raspberrypi
usbcore
sdhci_iproc
genet
of_mdio
sdhci_pltfm
fixed_phy
libphy
i2c_bcm2835
usb_common
sdhci
phy_generic
gpio_regulator
fixed

*** Device statistics:
Inter-|   Receive                                                |  Transmit
 face |bytes    packets errs drop fifo frame compressed multicast|bytes    packets errs drop fifo colls carrier compressed
    lo: 1737219    6962    0    0    0     0          0         0  1737219    6962    0    0    0     0       0          0
  lan0: 85064279   84500    0    0    0     0          0        21 28305719   61521    0    0    0     0       0          0
 wlan0:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
lan0.142: 82083117   56429    0    0    0     0          0        20 27359919   51109    0    0    0     0       0          0
vlan142: 82083117   56429    0    0    0     0          0        20 27359919   51109    0    0    0     0       0          0
lan0.636:     186       3    0    0    0     0          0         1     2366      25    0    0    0     0       0          0
vlan636:     186       3    0    0    0     0          0         1     2276      24    0    0    0     0       0          0

*** Protocol statistics:
Ip:
    Forwarding: 2
    56846 total packets received
    0 forwarded
    0 incoming packets discarded
    56846 incoming packets delivered
    52121 requests sent out
    6 outgoing packets dropped
    4 dropped because of missing route
Icmp:
    839 ICMP messages received
    0 input ICMP message failed
    ICMP input histogram:
        destination unreachable: 15
        echo requests: 2
        echo replies: 822
    850 ICMP messages sent
    0 ICMP messages failed
    ICMP output histogram:
        destination unreachable: 26
        echo requests: 822
        echo replies: 2
IcmpMsg:
        InType0: 822
        InType3: 15
        InType8: 2
        OutType0: 2
        OutType3: 26
        OutType8: 822
Tcp:
    351 active connection openings
    206 passive connection openings
    81 failed connection attempts
    15 connection resets received
    32 connections established
    58045 segments received
    63792 segments sent out
    2 segments retransmitted
    0 bad segments received
    243 resets sent
Udp:
    2071 packets received
    26 packets to unknown port received
    0 packet receive errors
    2086 packets sent
    0 receive buffer errors
    0 send buffer errors
    IgnoredMulti: 688
UdpLite:
TcpExt:
    1 resets received for embryonic SYN_RECV sockets
    302 TCP sockets finished time wait in fast timer
    175 delayed acks sent
    Quick ack mode was activated 9 times
    38082 packet headers predicted
    3026 acknowledgments not containing data payload received
    23653 predicted acknowledgments
    TCPLossProbes: 2
    TCPBacklogCoalesce: 1117
    TCPDSACKOldSent: 12
    TCPDSACKRecv: 2
    46 connections reset due to unexpected data
    4 connections reset due to early user close
    TCPDSACKIgnoredNoUndo: 1
    TCPDeferAcceptDrop: 31
    TCPRcvCoalesce: 3400
    TCPOFOQueue: 6
    TCPAutoCorking: 1492
    TCPOrigDataSent: 41478
    TCPHystartTrainDetect: 3
    TCPHystartTrainCwnd: 80
    TCPKeepAlive: 205
    TCPDelivered: 41717
    TCPDSACKRecvSegs: 2
IpExt:
    OutMcastPkts: 6
    InBcastPkts: 696
    InOctets: 81840226
    OutOctets: 25246868
    OutMcastOctets: 240
    InBcastOctets: 36705
    InNoECTPkts: 84889
    InECT0Pkts: 3


** PCI devices:
not available

** USB devices:
Bus 002 Device 002: ID 0578:0578 Intrinsix Corp. KingSpec Z3-128
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0430:0005 Sun Microsystems, Inc. Type 6 Keyboard
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


-- System Information:
Debian Release: 11.0
  APT prefers testing
  APT policy: (500, 'testing'), (100, 'stable'), (50, 'unstable')
Architecture: arm64 (aarch64)

Kernel: Linux 5.10.0-8-arm64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_US.ISO8859-15, LC_CTYPE=en_US.ISO8859-15 (charmap=ISO-8859-15) (ignored: LC_ALL set to en_US.ISO8859-15), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-image-5.10.0-8-arm64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.140
ii  kmod                                    28-1
ii  linux-base                              4.6

Versions of packages linux-image-5.10.0-8-arm64 recommends:
ii  apparmor             2.13.6-10
ii  firmware-linux-free  20200122-1

Versions of packages linux-image-5.10.0-8-arm64 suggests:
pn  debian-kernel-handbook  <none>
pn  linux-doc-5.10          <none>

Versions of packages linux-image-5.10.0-8-arm64 is related to:
pn  firmware-amd-graphics     <none>
pn  firmware-atheros          <none>
pn  firmware-bnx2             <none>
pn  firmware-bnx2x            <none>
ii  firmware-brcm80211        20210315-3
pn  firmware-cavium           <none>
pn  firmware-intel-sound      <none>
pn  firmware-intelwimax       <none>
pn  firmware-ipw2x00          <none>
pn  firmware-ivtv             <none>
pn  firmware-iwlwifi          <none>
pn  firmware-libertas         <none>
pn  firmware-linux-nonfree    <none>
pn  firmware-misc-nonfree     <none>
pn  firmware-myricom          <none>
pn  firmware-netxen           <none>
pn  firmware-qlogic           <none>
pn  firmware-realtek          <none>
pn  firmware-samsung          <none>
pn  firmware-siano            <none>
pn  firmware-ti-connectivity  <none>
pn  xen-hypervisor            <none>

-- no debconf information

--- End Message ---
--- Begin Message ---
On Fri, 30 Jul 2021 22:27:40 +0200 Diederik de Haas <didi.debian@cknow.org> 
wrote:
> On vrijdag 30 juli 2021 21:28:54 CEST Diederik de Haas wrote:
> > On vrijdag 30 juli 2021 17:22:06 CEST Jan Huijsmans wrote:
> > I'm assuming you're the same person as in #984873, but iirc my mail to you
> > wrt that bug report bounced and hasn't received an answer.
> 
> And that mail bounced as well.
> So, I'm giving you a week to respond and if that doesn't happen, both bugs 
> will closed.
> If you're using random email addresses and not interested in a dialog, why 
> should we care?

Eight weeks later and still no response, thus closing.
Feel free to reopen the bug with the requested information.

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---

Reply to: