Bug#1013249: virtio_ring: module verification failed: signature and/or required key missing - tainting kernel

[Ryutaroh Matsumoto]

Package: src:linux
Version: 5.18.5-1
Severity: normal
User: debian-ri...@lists.debian.org
Usertags: riscv64
X-Debbugs-Cc: debian-ri...@lists.debian.org

Dear Maintainer,

I do not expect a kernel module in a genuine Debian kernel package
taints a kernel. But I see the following message in dmesg on
QEMU RISCV64 virt machine:

[8.038025] virtio_ring: module verification failed: signature and/or 
required key missing - tainting kernel

The QEMU is running on Debian/testing amd64 with the following version:
$ dpkg-query -W | fgrep qemu-system-misc
qemu-system-misc1:7.0+dfsg-7

The QEMU is started as follows:
qemu-system-riscv64 -machine virt,aclint=on,aia=none -m 4G -smp 4 -bios 
/usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.elf -kernel 
/usr/lib/u-boot/qemu-riscv64_smode/uboot.elf -append "console=ttyS0 rw 
root=/dev/vda1" -netdev user,id=net0 -device virtio-net-pci,netdev=net0  
-object rng-random,filename=/dev/urandom,id=rng0 -device 
virtio-rng-pci,rng=rng0 -drive 
if=virtio,file=debian-sid-riscv64.qcow2,index=0,format=qcow2,discard=unmap,detect-zeroes=unmap

-- Package-specific info:
** Version:
Linux version 5.18.0-2-riscv64 (debian-kernel@lists.debian.org) (gcc-11 (Debian 
11.2.0-20) 11.2.0, GNU ld (GNU Binutils for Debian) 2.38) #1 SMP Debian 
5.18.5-1 (2022-06-16)

** Command line:
root=UUID=031c42a9-74c5-4b38-8e78-87d5f1141c24 rw noquiet root=/dev/vda1 
net.ifnames=0 consoleblank=0 rw

** Tainted: E (8192)
 * unsigned module was loaded

** Kernel log:
[0.00] Linux version 5.18.0-2-riscv64 (debian-kernel@lists.debian.org) 
(gcc-11 (Debian 11.2.0-20) 11.2.0, GNU ld (GNU Binutils for Debian) 2.38) #1 
SMP Debian 5.18.5-1 (2022-06-16)
[0.00] OF: fdt: Ignoring memory range 0x8000 - 0x8020
[0.00] Machine model: riscv-virtio,qemu
[0.00] efi: UEFI not found.
[0.00] NUMA: No NUMA configuration found
[0.00] NUMA: Faking a node at [mem 
0x8020-0x00017fff]
[0.00] NUMA: NODE_DATA [mem 0x17ffedbc0-0x17ffeefff]
[0.00] Zone ranges:
[0.00]   DMA32[mem 0x8020-0x]
[0.00]   Normal   [mem 0x0001-0x00017fff]
[0.00] Movable zone start for each node
[0.00] Early memory node ranges
[0.00]   node   0: [mem 0x8020-0x00017fff]
[0.00] Initmem setup node 0 [mem 0x8020-0x00017fff]
[0.00] On node 0, zone DMA32: 512 pages in unavailable ranges
[0.00] SBI specification v0.3 detected
[0.00] SBI implementation ID=0x1 Version=0x1
[0.00] SBI TIME extension detected
[0.00] SBI IPI extension detected
[0.00] SBI RFENCE extension detected
[0.00] SBI SRST extension detected
[0.00] SBI HSM extension detected
[0.00] riscv: base ISA extensions acdfhim
[0.00] riscv: ELF capabilities acdfim
[0.00] percpu: cpu 0 has no node -1 or node-local memory
[0.00] percpu: Embedded 27 pages/cpu s72744 r8192 d29656 u110592
[0.00] pcpu-alloc: s72744 r8192 d29656 u110592 alloc=27*4096
[0.00] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[0.00] Fallback order for Node 0: 0 
[0.00] Built 1 zonelists, mobility grouping on.  Total pages: 1031688
[0.00] Policy zone: Normal
[0.00] Kernel command line: 
root=UUID=031c42a9-74c5-4b38-8e78-87d5f1141c24 rw noquiet root=/dev/vda1 
net.ifnames=0 consoleblank=0 rw
[0.00] Unknown kernel command line parameters "noquiet", will be passed 
to user space.
[0.00] Dentry cache hash table entries: 524288 (order: 10, 4194304 
bytes, linear)
[0.00] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes, 
linear)
[0.00] mem auto-init: stack:off, heap alloc:on, heap free:off
[0.00] software IO TLB: mapped [mem 
0xfb73a000-0xff73a000] (64MB)
[0.00] Memory: 2079280K/4192256K available (7539K kernel code, 5095K 
rwdata, 4096K rodata, 2456K init, 426K bss, 252764K reserved, 0K cma-reserved)
[0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[0.00] ftrace: allocating 28720 entries in 113 pages
[0.00] ftrace: allocated 113 pages with 4 groups
[0.00] trace event string verifier disabled
[0.00] rcu: Hierarchical RCU implementation.
[0.00] rcu: RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.
[0.00]  Rude variant of Tasks RCU enabled.
[0.00]  Tracing variant of Tasks RCU enabled.
[0.00] rcu: RCU calculated value of scheduler-enlistment delay is 25 
jiffies.
[0.00] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[0.00] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[0.00] riscv-intc: 64 local interrupts mapped
[0.00] plic: plic@c00: mapped 53 interrupts with 4 handlers for 8 
contexts.
[0.00] riscv_timer_init_dt: Registering clocksource cpuid 

Bug#977647: 5.10.4 Debian kernel does not boot on amd64 with btrfs rootfs

[Ryutaroh Matsumoto]

Control: close -1

>> The severity seems now minor.
>> It has still the mysterious dmesg error on tpm as follows.
>> The full dmesg log is attached.
> 
> Do you still have the issues? Otherwise let's close this bug.

No. Let's close this. Ryutaroh

Bug#981586: Bullseye armhf kernel for Raspberry Pi 4b does not boot

[Ryutaroh Matsumoto]

Control: tags -1 + wontfix patch

From: Der_Martin 
Date: Fri, 9 Apr 2021 10:45:13 +0200
> On 16 Mar 2021 someone published a solution to that bug. Obviously nobody 
> cares?

Bug #981586 is a duplicate of #971059.
#981586 is unlikely to get fixed because
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971059#12
So I add "wontfix".

Only
CONFIG_PCIE_BRCMSTB=m
is sufficient for linux-image-armmp-lpae to boot on RPi4B 8GB.
The following script on Debian Bullseye armhf (in a container or a VM)
builds a kernel bootable from USB MSD on RPi4B 8GB. 

#!/bin/sh
set -ex
KVAR=5.10.29
wget https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-${KVAR}.tar.xz
tar Jxf linux-${KVAR}.tar.xz 
apt-get -q -y install linux-config-5.10 build-essential libncurses-dev fakeroot 
dpkg-dev
apt-get -q -y build-dep linux
cd linux-${KVAR}
xzcat /usr/src/linux-config-5.10/config.armhf_none_armmp-lpae.xz >.config
ARCH=arm
export ARCH
echo 'CONFIG_PCIE_BRCMSTB=m' >>.config
make oldconfig
nice -19 make -j 12 bindeb-pkg

Best regards, Ryutaroh Matsumoto

Bug#981616: RPi4B 5GHz WiFi problems #985632 & #981616 completely went away by replacing brcmfmac43455-sdio.bin and brcmfmac43455-sdio.clm_blob

[Ryutaroh Matsumoto]

Control: reassign 981616 firmware-brcm80211 20201218-3

Hi,
two RPi4B 5GHz WiFi problems

#985632
firmware-brcm80211: [REGRESSION] RPi4B 5GHz WiFi stopped working with 
20210208-4, 20201218-3 was fine

and

#981616
5GHz WiFi does not work with vc4.ko on RPi4 and 4K display

completely went away by replacing
/lib/firmware/brcm/brcmfmac43455-sdio.bin and
/lib/firmware/brcm/brcmfmac43455-sdio.clm_blob
by the files at
https://github.com/RPi-Distro/firmware-nonfree/tree/master/brcm

Commit messages at 
https://github.com/RPi-Distro/firmware-nonfree/tree/master/brcm
are interesting:

Use BCM43456 clm_blob on CYW43455
The previous CYW43455 clm_blob provides limited access to the higher
5GHz channels (100+) - the BCM43456 (surprisingly) seems to work and
doesn't have this problem. Huh

Update CYW43455 firmware
This release fixes the error: Firmware trap: type 0x4 @ epc 0x0007a094
The full version string is:
Version 7.45.229 (617f1f5 CY) CRC: 253bd863 Date: Mon 2021-01-04 19:58:58 PST 
Ucode Ver: 1043.2160 FWID 01-2dbd9d2e
See: raspberrypi/linux#3849

Best regards,
Ryutaroh Matsumoto

Bug#978025: Sound issues with the 5.10.x kernel (alsa)

[Ryutaroh Matsumoto]

>> i assume you set this option in the config.txt? This shouldn't have any
>> affect for the mainline kernel / DT.
> I am aware of that...

I include my config.txt on RPi4B for reference...
arm_64bit=1
enable_uart=1
upstream_kernel=1
kernel=vmlinuz-5.10.0-5-rt-arm64
initramfs initrd.img-5.10.0-5-rt-arm64
disable_fw_kms_setup=1
disable_overscan=1
hdmi_enable_4kp60=1

Best regards, Ryutaroh Matsumoto

Bug#985928: Sound issues with the 5.10.x kernel (alsa)

[Ryutaroh Matsumoto]

Hi Stefan, thank you for your response.

> i assume you set this option in the config.txt? This shouldn't have any
> affect for the mainline kernel / DT.

I am aware of that...
I did "snd_bcm2835 enable_hdmi=0" in /etc/modules.
"modinfo snd_bcm2835" shows as below. Doesn't it indicate snd_bcm2835 having
an option enable_hdmi???

It seems that the contention of grabbing HDMI audio output between vc4.ko
and snd_bcm2835.ko can be addressed if snd_bcm2835.ko honors the
option enable_hdmi with its default =0, but currently enable_hdmi seems
having no effect in behavior of snd_bcm2835...

# modinfo snd_bcm2835
filename:   
/lib/modules/5.10.0-5-rt-arm64/kernel/drivers/staging/vc04_services/bcm2835-audio/snd-bcm2835.ko
alias:  platform:bcm2835_audio
license:GPL
description:Alsa driver for BCM2835 chip
author: Dom Cobley
depends:snd-pcm,vchiq,snd
staging:Y
intree: Y
name:   snd_bcm2835
vermagic:   5.10.0-5-rt-arm64 SMP preempt_rt mod_unload modversions aarch64
sig_id: PKCS#7
signer: Debian Secure Boot CA
sig_key:4B:6E:F5:AB:CA:66:98:25:17:8E:05:2C:84:66:7C:CB:C0:53:1F:8C
sig_hashalgo:   sha256
signature:  omitted, too long.
parm:   force_bulk:Force use of vchiq bulk for audio (bool)
parm:   enable_hdmi:Enables HDMI virtual audio device (bool)
parm:   enable_headphones:Enables Headphones virtual audio device (bool)
parm:   enable_compat_alsa:Enables ALSA compatibility virtual audio 
device (bool)
parm:   num_channels:Number of audio channels (default: 8) (int)

Best regards, Ryutaroh

Bug#978025: Sound issues with the 5.10.x kernel (alsa)

[Ryutaroh Matsumoto]

> I think the root cause of this issue is that both vc4.ko and snd_bcm2835.ko
> try to provide ALSA sinks to HDMI audio outputs from RPi.
> Why do the two drivers provide the same functionality for the same device?
> It seems nonsense.
> There must be some coordination between vc4.ko and snd_bcm2835.ko
> on who provides ALSA sinks of RPi HDMI output.

Giving "enable_hdmi=0" to snd_bcm2835.ko does not improve the situation,
while module_blacklisting snd_bcm2835 suppresses all the symptoms reported.
snd_bcm2835.ko in 5.10.24 seems having a bug ignoring "enable_hdmi=0".

Best regards, Ryutaroh

Bug#978025: Sound issues with the 5.10.x kernel (alsa)

[Ryutaroh Matsumoto]

Hi all,

From: Stefan Wahren 
Subject: Re: Sound issues with the 5.10.x kernel (alsa)
Date: Mon, 8 Feb 2021 13:22:56 +0100
>> This is basically me forwarding the bug I reported on Debian's BTS:
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978025
>> TL;DR: I have a RPi 3B+ running pure Debian Bullseye arm64 (~from 
>> raspi.debian.net), named rpi-mpd, connected via HDMI cable to my AV Receiver.
> can you please confirm that the bcm2835-audio driver causing the issues?

I think the root cause of this issue is that both vc4.ko and snd_bcm2835.ko
try to provide ALSA sinks to HDMI audio outputs from RPi.
Why do the two drivers provide the same functionality for the same device?
It seems nonsense.
There must be some coordination between vc4.ko and snd_bcm2835.ko
on who provides ALSA sinks of RPi HDMI output.

The non-coordination that both drivers provide different ALSA sinks of the same
device already causes another symptom as
http://lists.infradead.org/pipermail/linux-rpi-kernel/2021-March/008077.html

Best regards, Ryutaroh Matsumoto

Bug#985928: vc4.ko brings unusable ALSA sinks

[Ryutaroh Matsumoto]

From: Ryutaroh Matsumoto 
Subject: vc4.ko brings unusable ALSA sinks
Date: Fri, 26 Mar 2021 17:15:40 +0900 (JST)
> Touching vc4-hdmi-[01] too many times makes the kernel unstable,
> and shutting down often needs several minutes.
> /usr/bin/pulseaudio in its default setting touches all available  ALSA sinks
> and causes the above inconvenience.
> I mainly use HDMI audio output, and 

In my last email, a pointed reproducing procedure should have been given:

0. Assume an RPi4B and a high resolution HDMI display.
1. Install pulseaudio on a sensible distro with the upstream kernel and systemd,
e.g.  https://raspi.debian.net
2. Make a non-root user and login as that user.
3. Run the following script by the non-root user:
#!/bin/sh
set -x
while true; do
  systemctl --user status pulseaudio
  pacmd list-sinks
  pacmd exit
  systemctl --user restart pulseaudio
done

Then every command in the above script gets stuck or fails.

I also prepared an SD card image that can reproduce the reported symptom
on RPi4B 8GB at http://153.240.174.134:64193/tmp/sdimage8GB.img.xz
(268,112,012 bytes).

Best regards, Ryutaroh

Bug#984844: 984844 was fixed by upgrading firmware-brcm80211

[Ryutaroh Matsumoto]

Control: notfound -1 20210208-4

#984844 is not observed in 20210208-4 in testing/Bullseye.
Ryutaroh

Bug#981616: 981616 remains in 5.10.24-1

[Ryutaroh Matsumoto]

Control: reopen -1
Control: forwarded -1 
http://lists.infradead.org/pipermail/linux-rpi-kernel/2021-March/008065.html
Control: found -1 5.10.24-1
Control: tags -1 + upstream

Sorry, #981616 still persists in 5.10.24-1.
For detail, please refer to
http://lists.infradead.org/pipermail/linux-rpi-kernel/2021-March/008065.html

Best regards, Ryutaroh

Bug#981616: 981616 is fixed in 5.10.24-1

[Ryutaroh Matsumoto]

Control: close -1 5.10.24-1

I recheck the situation with Debian kernel 5.10.24 and
Debian firmware-brcm80211 20201218-3.
5GHz WiFi works fine with vc4 and without vc4.

Debian package of firmware-brcm80211 newer than 20201218-3
has a severe issue with 5GHz WiFi as reported at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984489
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985632
But it is a separate topic.

Best regards, Ryutaroh

Bug#985632: firmware-brcm80211: [REGRESSION] RPi4B 5GHz WiFi stopped working with 20210208-4, 20201218-3 was fine

[Ryutaroh Matsumoto]

Control: found -1 20210315-1

> I will re-check 20210315-1.

The system boots with 20210315-1 and the reported symtom remains in
the same way. Ryutaroh

Bug#985632: firmware-brcm80211: [REGRESSION] RPi4B 5GHz WiFi stopped working with 20210208-4, 20201218-3 was fine

[Ryutaroh Matsumoto]

Hi Maximilian, thank you again for your response.

> but are you sure that these
> bootflags are still adequate for the latest cypress firmware?

What did you mean by "bootflags"??
Did you mean /proc/cmdline (i.e. cmdline.txt in Raspberry Pi)?

> concerning bluetooth unfortunately this seems missing firmware
> in latest upstream firmware git (see #962038 ) or possible wget info
> https://wiki.debian.org/RaspberryPi4#Bluetooth

I know that bluetooth interferes with 2.4GHz WiFi with pure Debian
packages as reported in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984844

I do not see any intererence between bluetooth and 5GHz WiFi.
I doubt the intererence as bluetooth frequency does not overlap with 5GHz WiFi 
at all.
With the firmware 20210208-4, 2.4GHz WiFi works fine provided that
bluetooth is turned off by rfkill etc.

I am running a combination of pure Debian packages and
encountered the reported symptom. What is a Debian way to
use 5GHz WiFi? Do you need additional information?

> this should not be reproducible as 20210315-1 and 20210315-1~exp1 are
> unchanged (just uploaded into experimental before unstable).

I will re-check 20210315-1.

Best regards, Ryutaroh

Bug#985632: firmware-brcm80211: [REGRESSION] RPi4B 5GHz WiFi stopped working with 20210208-4, 20201218-3 was fine

[Ryutaroh Matsumoto]

Control: tags -1 - moreinfo

Hi Maximilian, thank you for your attention!

> please provide info on the affected hardware,

It is Raspberry Pi 4B 8GB model.

> please show affected dmesg output working and non working,
> the difference between 20210208-3 20210208-4 is minimal,
> hence it should be easy to find out what broke?

Not at all, unfortunately.
20210208-3 was completely broken on RPi4B as
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984489
20210208-1 to 20210208-3 were broken...
The last working version was 20201218-3, and I apt-mark-holded 
firmware-brcm80211.
I unhold it in the weekend and found this issue.

I attach dmesg of 20201218-3, 20210208-4, and 20210315-1.
It was also interesting that installation of 20210315-1 causes boot failure
and showed "Give root password for maintainance"...
Should I file a separete report against 20210315-1?
20210315-1~exp1 was booted fine...

Best regards, Ryutaroh


dmesg.tar.xz
Description: Binary data

Bug#985632: firmware-brcm80211: [REGRESSION] RPi4B 5GHz WiFi stopped working with 20210208-4, 20201218-3 was fine

[Ryutaroh Matsumoto]

Package: firmware-brcm80211
Version: 20210315-1~exp1
Followup-For: Bug #985632

Dear Maintainer,

This reported symptom also exists in
20210315-1~exp1.

Best regards, Ryutaroh

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: arm64 (aarch64)

Kernel: Linux 5.10.0-4-rt-arm64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CRAP
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

firmware-brcm80211 depends on no packages.

firmware-brcm80211 recommends no packages.

Versions of packages firmware-brcm80211 suggests:
ii  initramfs-tools  0.140

-- no debconf information

Bug#985632: firmware-brcm80211: [REGRESSION] RPi4B 5GHz WiFi stopped working with 20210208-4, 20201218-3 was fine

[Ryutaroh Matsumoto]

Package: firmware-brcm80211
Version: 20210208-4
Severity: grave
Tags: sid bullseye
Justification: renders package unusable
X-Debbugs-Cc: debian-...@lists.debian.org

Dear Maintainer,

5GHz WiFi stopped working with 20210208-4.
iw wlan0 scan does not show SSID of 5GHz WiFi.
With 20201218-3, 5GHz worked fine,
provided that vc4.ko is blacklisted (see #981616).

I will see if the newer package in the experimental
behaves differently.

Best regards, Ryutaroh Matsumoto5GHz WiFi stopped working with 20210208-4.
iw wlan0 scan does not show SSID of 5GHz WiFi.
With 20201218-3, 5GHz worked fine,
provided that vc4.ko is blacklisted (see #981616).

I will see if the newer package in the experimental
behaves differently.

Best regards, Ryutaroh Matsumoto5GHz WiFi stopped working with 20210208-4.
iw wlan0 scan does not show SSID of 5GHz WiFi.
With 20201218-3, 5GHz worked fine,
provided that vc4.ko is blacklisted (see #981616).

I will see if the newer package in the experimental
behaves differently.

Best regards, Ryutaroh Matsumoto5GHz WiFi stopped working with 20210208-4.
iw wlan0 scan does not show SSID of 5GHz WiFi.
With 20201218-3, 5GHz worked fine,
provided that vc4.ko is blacklisted (see #981616).

I will see if the newer package in the experimental
behaves differently.

Best regards, Ryutaroh Matsumoto5GHz WiFi stopped working with 20210208-4.
iw wlan0 scan does not show SSID of 5GHz WiFi.
With 20201218-3, 5GHz worked fine,
provided that vc4.ko is blacklisted (see #981616).

I will see if the newer package in the experimental
behaves differently.

Best regards, Ryutaroh Matsumoto

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: arm64 (aarch64)

Kernel: Linux 5.10.0-4-rt-arm64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CRAP
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

firmware-brcm80211 depends on no packages.

firmware-brcm80211 recommends no packages.

Versions of packages firmware-brcm80211 suggests:
ii  initramfs-tools  0.139

-- no debconf information

Bug#985630: linux-image-5.10.0-4-rt-arm64: vc4.ko gives a false error messages with empty SD card slot

[Ryutaroh Matsumoto]

Package: src:linux
Version: 5.10.19-1
Severity: minor
Tags: upstream sid bullseye
Control: forwarded -1 
http://lists.infradead.org/pipermail/linux-rpi-kernel/2021-March/008058.html

Dear Maintainer,

I found another mysterious error caused by vc4.ko.
Only when vc4.ko is loaded AND the SD card slot is empty in my RPi4B 8GB,
I observe the following harmless error message at every 10 seconds:

[  255.457584] mmc1: Timeout waiting for hardware cmd interrupt.
[  255.460735] mmc1: sdhci:  SDHCI REGISTER DUMP ===
[  255.464244] mmc1: sdhci: Sys addr:  0x | Version:  0x1002
[  255.467752] mmc1: sdhci: Blk size:  0x | Blk cnt:  0x
[  255.471259] mmc1: sdhci: Argument:  0x | Trn mode: 0x
[  255.474765] mmc1: sdhci: Present:   0x1fff0001 | Host ctl: 0x0001
[  255.478271] mmc1: sdhci: Power: 0x000f | Blk gap:  0x0080
[  255.481777] mmc1: sdhci: Wake-up:   0x | Clock:0xf447
[  255.485282] mmc1: sdhci: Timeout:   0x | Int stat: 0x
[  255.488787] mmc1: sdhci: Int enab:  0x00ff1003 | Sig enab: 0x00ff1003
[  255.492293] mmc1: sdhci: ACmd stat: 0x | Slot int: 0x
[  255.495799] mmc1: sdhci: Caps:  0x45ee6432 | Caps_1:   0xa525
[  255.499305] mmc1: sdhci: Cmd:   0x0502 | Max curr: 0x00080008
[  255.502809] mmc1: sdhci: Resp[0]:   0x | Resp[1]:  0x
[  255.506314] mmc1: sdhci: Resp[2]:   0x | Resp[3]:  0x
[  255.509819] mmc1: sdhci: Host ctl2: 0x
[  255.512239] mmc1: sdhci: ADMA Err:  0x | ADMA Ptr: 0x
[  255.515743] mmc1: sdhci: 
[  265.697585] mmc1: Timeout waiting for hardware cmd interrupt.
[  265.700734] mmc1: sdhci:  SDHCI REGISTER DUMP ===
[  265.704244] mmc1: sdhci: Sys addr:  0x | Version:  0x1002
[  265.707752] mmc1: sdhci: Blk size:  0x | Blk cnt:  0x
[  265.711258] mmc1: sdhci: Argument:  0x | Trn mode: 0x
[  265.714764] mmc1: sdhci: Present:   0x1fff0001 | Host ctl: 0x0001
[  265.718270] mmc1: sdhci: Power: 0x000f | Blk gap:  0x0080
[  265.721775] mmc1: sdhci: Wake-up:   0x | Clock:0xf447
[  265.725279] mmc1: sdhci: Timeout:   0x | Int stat: 0x
[  265.728785] mmc1: sdhci: Int enab:  0x00ff1003 | Sig enab: 0x00ff1003
[  265.732290] mmc1: sdhci: ACmd stat: 0x | Slot int: 0x
[  265.735795] mmc1: sdhci: Caps:  0x45ee6432 | Caps_1:   0xa525
[  265.739300] mmc1: sdhci: Cmd:   0x0502 | Max curr: 0x00080008
[  265.742806] mmc1: sdhci: Resp[0]:   0x | Resp[1]:  0x
[  265.746311] mmc1: sdhci: Resp[2]:   0x | Resp[3]:  0x
[  265.749815] mmc1: sdhci: Host ctl2: 0x
[  265.752234] mmc1: sdhci: ADMA Err:  0x | ADMA Ptr: 0x
[  265.755739] mmc1: sdhci: 

Best regards, Ryutaroh Matsumoto

-- Package-specific info:
** Version:
Linux version 5.10.0-4-rt-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 PREEMPT_RT Debian 5.10.19-1 (2021-03-02)

** Command line:
 dma.dmachans=0x37f5 bcm2709.boardrev=0xd03114 bcm2709.serial=0x488d2af3 
bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=42 
bcm2709.disk_led_active_low=0 smsc95xx.macaddr=DC:A6:32:BB:99:D9 
vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0  console=tty0 
console=ttyS1,115200 root=LABEL=RASPIROOT rw fsck.repair=yes net.ifnames=0 
cma=256M@256M rootwait rootfstype=ext4 module_blacklist=btrfs

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

** Kernel log:

[0.00] Booting Linux on physical CPU 0x00 [0x410fd083]
[0.00] Linux version 5.10.0-4-rt-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 PREEMPT_RT Debian 5.10.19-1 (2021-03-02)
[0.00] Machine model: Raspberry Pi 4 Model B Rev 1.4
[0.00] efi: UEFI not found.
[0.00] Reserved memory: bypass linux,cma node, using cmdline CMA params 
instead
[0.00] OF: reserved mem: node linux,cma compatible matching fail
[0.00] cma: Reserved 256 MiB at 0x1000
[0.00] NUMA: No NUMA configuration found
[0.00] NUMA: Faking a node at [mem 
0x-0x0001]
[0.00] NUMA: NODE_DATA [mem 0x1ff018940-0x1ff01afff]
[0.00] Zone ranges:
[0.00]   DMA  [mem 0x-0x3fff]
[0.00]   DMA32[mem 0x4000-0x]
[0.00]   Normal   [mem 0x0001-0x0001]
[0.00] Movable zone start for each node
[0.00] Early memory node ranges
[0.00]   node   0: [mem 0x-0x3b2f]
[0.00]   node   0: [mem 0x4000-0xfbff]
[0.00

Bug#985121: linux-image-5.10.0-4-rt-arm64: KMS seems broken in vc4.ko

[Ryutaroh Matsumoto]

Hi Lucas,

> According to strace, it fails because /dev/dri does not exist.

When vc4.ko is not loaded, /dev/dri does not exist.
If vc4.ko is loaded, /dev/dri exists. Could you make sure that
vc4.ko is loaded by "lsmod | fgrep vc4"?
vc4.ko was disabled at Debian kernel 5.10.9.
Other Debian 5.10.? kernel packages have vc4.ko.

When vc4.ko is not loaded, kmscube fails as:

Script started on 2021-03-15 09:02:32+09:00 [TERM="linux" TTY="/dev/tty3" 
COLUMNS="480" LINES="135"]
root@raspi4b8gb:/tmp# kmscube
drmGetDevices2 failed: No such file or directory
could not open drm device
failed to initialize legacy DRM
root@raspi4b8gb:/tmp# exit
Script done on 2021-03-15 09:02:40+09:00 [COMMAND_EXIT_CODE="255"]

When vc4.ko is loaded, kmscube fails as:

$ kmscube
Using display 0xe087a150 with EGL version 1.4
===
EGL information:
  version: "1.4"
  vendor: "Mesa Project"
  client extensions: "EGL_EXT_device_base EGL_EXT_device_enumeration 
EGL_EXT_device_query EGL_EXT_platform_base 
EGL_KHR_client_get_all_proc_addresses EGL_EXT_client_extensions EGL_KHR_debug 
EGL_EXT_platform_device EGL_EXT_platform_wayland EGL_KHR_platform_wayland 
EGL_EXT_platform_x11 EGL_KHR_platform_x11 EGL_MESA_platform_gbm 
EGL_KHR_platform_gbm EGL_MESA_platform_surfaceless"
  display extensions: "EGL_ANDROID_blob_cache EGL_EXT_buffer_age 
EGL_EXT_image_dma_buf_import EGL_EXT_image_dma_buf_import_modifiers 
EGL_KHR_cl_event2 EGL_KHR_config_attribs EGL_KHR_create_context 
EGL_KHR_create_context_no_error EGL_KHR_fence_sync 
EGL_KHR_get_all_proc_addresses EGL_KHR_gl_colorspace 
EGL_KHR_gl_renderbuffer_image EGL_KHR_gl_texture_2D_image 
EGL_KHR_gl_texture_3D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_image 
EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_no_config_context 
EGL_KHR_reusable_sync EGL_KHR_surfaceless_context EGL_EXT_pixel_format_float 
EGL_KHR_wait_sync EGL_MESA_configless_context EGL_MESA_image_dma_buf_export 
EGL_MESA_query_driver "
===
OpenGL ES 2.x information:
  version: "OpenGL ES 3.2 Mesa 20.3.4"
  shading language version: "OpenGL ES GLSL ES 3.20"
  vendor: "Mesa/X.org"
  renderer: "llvmpipe (LLVM 11.0.1, 128 bits)"
  extensions: "GL_EXT_blend_minmax GL_EXT_multi_draw_arrays 
GL_EXT_texture_compression_s3tc GL_EXT_texture_compression_dxt1 
GL_EXT_texture_compression_rgtc GL_EXT_texture_format_BGRA 
GL_OES_compressed_ETC1_RGB8_texture GL_OES_depth24 GL_OES_element_index_uint 
GL_OES_fbo_render_mipmap GL_OES_mapbuffer GL_OES_rgb8_rgba8 
GL_OES_standard_derivatives GL_OES_stencil8 GL_OES_texture_3D 
GL_OES_texture_float GL_OES_texture_float_linear GL_OES_texture_half_float 
GL_OES_texture_half_float_linear GL_OES_texture_npot GL_OES_vertex_half_float 
GL_EXT_draw_instanced GL_EXT_texture_sRGB_decode GL_OES_EGL_image 
GL_OES_depth_texture GL_OES_packed_depth_stencil 
GL_EXT_texture_type_2_10_10_10_REV GL_NV_conditional_render 
GL_OES_get_program_binary GL_APPLE_texture_max_level GL_EXT_discard_framebuffer 
GL_EXT_read_format_bgra GL_EXT_frag_depth GL_NV_fbo_color_attachments 
GL_OES_EGL_image_external GL_OES_EGL_sync GL_OES_vertex_array_object 
GL_OES_viewport_array GL_ANGLE_pack_reverse_row_order 
GL_ANGLE_texture_compression_dxt3 GL_ANGLE_texture_compression_dxt5 
GL_EXT_occlusion_query_boolean GL_EXT_robustness GL_EXT_texture_rg 
GL_EXT_unpack_subimage GL_NV_draw_buffers GL_NV_read_buffer GL_NV_read_depth 
GL_NV_read_depth_stencil GL_NV_read_stencil GL_EXT_draw_buffers 
GL_EXT_map_buffer_range GL_KHR_debug GL_KHR_robustness 
GL_KHR_texture_compression_astc_ldr GL_NV_pixel_buffer_object 
GL_OES_depth_texture_cube_map GL_OES_required_internalformat 
GL_OES_surfaceless_context GL_EXT_color_buffer_float GL_EXT_sRGB_write_control 
GL_EXT_separate_shader_objects GL_EXT_shader_group_vote 
GL_EXT_shader_implicit_conversions GL_EXT_shader_integer_mix 
GL_EXT_tessellation_point_size GL_EXT_tessellation_shader 
GL_ANDROID_extension_pack_es31a GL_EXT_base_instance 
GL_EXT_compressed_ETC1_RGB8_sub_texture GL_EXT_copy_image 
GL_EXT_draw_buffers_indexed GL_EXT_draw_elements_base_vertex GL_EXT_gpu_shader5 
GL_EXT_polygon_offset_clamp GL_EXT_primitive_bounding_box GL_EXT_render_snorm 
GL_EXT_shader_io_blocks GL_EXT_texture_border_clamp GL_EXT_texture_buffer 
GL_EXT_texture_cube_map_array GL_EXT_texture_norm16 GL_EXT_texture_view 
GL_KHR_blend_equation_advanced GL_KHR_context_flush_control 
GL_KHR_robust_buffer_access_behavior GL_NV_image_formats GL_OES_copy_image 
GL_OES_draw_buffers_indexed GL_OES_draw_elements_base_vertex GL_OES_gpu_shader5 
GL_OES_primitive_bounding_box GL_OES_sample_shading GL_OES_sample_variables 
GL_OES_shader_io_blocks GL_OES_shader_multisample_interpolation 
GL_OES_tessellation_point_size GL_OES_tessellation_shader 
GL_OES_texture_border_clamp GL_OES_texture_buffer GL_OES_texture_cube_map_array 
GL_OES_texture_stencil8 GL_OES_texture_storage_multisample_2d_array 
GL_OES_texture_view GL_EXT_blend_func_extended GL_EXT_buffer_storage 

Bug#985121: linux-image-5.10.0-4-rt-arm64: KMS seems broken in vc4.ko

[Ryutaroh Matsumoto]

Package: src:linux
Version: 5.10.19-1
Severity: normal
Tags: upstream sid bullseye
X-Debbugs-Cc: debian-...@lists.debian.org
Control: forwarded -1 
http://lists.infradead.org/pipermail/linux-rpi-kernel/2021-March/008049.html

Dear Maintainer,

kmscube 0.0.0~git20210103-1 fails to start with the error message
on Raspberry Pi 4B:

failed to set mode: Invalid argument

kmscube works fine on linux-image-amd64 and Raspberry Pi OS kernel
with vc4.ko and v3d.ko loaded.
Debian kernel without vc4.ko does not have KMS support on RPi4B.

If this is an issue in kmscube, please feel free to reassign.
This has been reported to the upstream maintainer.

Best regards, Ryutaroh Matsumoto


-- Package-specific info:
** Version:
Linux version 5.10.0-4-rt-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 PREEMPT_RT Debian 5.10.19-1 (2021-03-02)

** Command line:
 dma.dmachans=0x37f5 bcm2709.boardrev=0xd03114 bcm2709.serial=0x488d2af3 
bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=42 
bcm2709.disk_led_active_low=0 smsc95xx.macaddr=DC:A6:32:BB:99:D9 
vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0  console=tty0 
root=LABEL=RASPIROOT rw fsck.repair=yes net.ifnames=0 cma=256M@256M rootwait 
rootfstype=ext4 module_blacklist=vc4,btrfs

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

** Kernel log:
[   15.434159] systemd[1]: Listening on udev Kernel Socket.
[   15.469512] systemd[1]: Mounting Huge Pages File System...
[   15.586142] systemd[1]: Mounting POSIX Message Queue File System...
[   15.693933] systemd[1]: Mounting Kernel Debug File System...
[   15.760955] systemd[1]: Mounting Kernel Trace File System...
[   15.824464] systemd[1]: Starting Restore / save the current clock...
[   15.887927] systemd[1]: Starting Set the console keyboard layout...
[   15.948674] systemd[1]: Starting Create list of static device nodes for the 
current kernel...
[   16.009118] systemd[1]: Starting Load Kernel Module configfs...
[   16.072408] systemd[1]: Starting Load Kernel Module drm...
[   16.136954] systemd[1]: Starting Load Kernel Module fuse...
[   16.186350] fuse: init (API version 7.32)
[   16.593944] systemd[1]: Condition check resulted in Set Up Additional Binary 
Formats being skipped.
[   16.594243] systemd[1]: Condition check resulted in File System Check on 
Root Device being skipped.
[   16.606377] systemd[1]: Starting Journal Service...
[   16.697713] systemd[1]: Starting Load Kernel Modules...
[   16.772886] systemd[1]: Starting Remount Root and Kernel File Systems...
[   16.826411] EXT4-fs (sda2): re-mounted. Opts: 
journal_async_commit,nobarrier,data=writeback,commit=3600
[   16.839276] systemd[1]: Starting Coldplug All udev Devices...
[   16.936206] systemd[1]: Mounted Huge Pages File System.
[   16.963282] systemd[1]: Mounted POSIX Message Queue File System.
[   16.991278] systemd[1]: Mounted Kernel Debug File System.
[   17.088051] systemd[1]: Started Journal Service.
[   17.499035] systemd-journald[259]: Received client request to flush runtime 
journal.
[   29.663856] vchiq: module is from the staging directory, the quality is 
unknown, you have been warned.
[   29.838127] iproc-rng200 fe104000.rng: hwrng registered
[   30.005996] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer
[   30.152450] Module vc4 is blacklisted
[   30.528213] alg: No test for fips(ansi_cprng) (fips_ansi_cprng)
[   30.841068] snd_bcm2835: module is from the staging directory, the quality 
is unknown, you have been warned.
[   30.893324] cryptd: max_cpu_qlen set to 1000
[   30.905644] mc: Linux media interface: v0.10
[   30.931090] bcm2835_audio bcm2835_audio: card created with 8 channels
[   30.965046] cfg80211: Loading compiled-in X.509 certificates for regulatory 
database
[   30.965729] cfg80211: Loaded X.509 cert 'b...@debian.org: 
577e021cb980e0e820821ba7b54b4961b8b4fadf'
[   30.966251] cfg80211: Loaded X.509 cert 'romain.per...@gmail.com: 
3abbc6ec146e09d1b6016ab9d6cf71dd233f0328'
[   30.966940] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   30.988506] platform regulatory.0: firmware: direct-loading firmware 
regulatory.db
[   30.993828] platform regulatory.0: firmware: direct-loading firmware 
regulatory.db.p7s
[   31.010109] videodev: Linux video capture interface: v2.00
[   31.089165] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio 
for chip BCM4345/6
[   31.099490] brcmfmac mmc0:0001:1: firmware: direct-loading firmware 
brcm/brcmfmac43455-sdio.bin
[   31.100616] brcmfmac mmc0:0001:1: firmware: direct-loading firmware 
brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt
[   31.106479] usbcore: registered new interface driver brcmfmac
[   31.197366] bcm2835_mmal_vchiq: module is from the staging directory, the 
quality is unknown, you have been warned.
[   31.222017] bcm2835_v4l2: module is from the staging directory, the quality 
is unknown, you have been warned.
[   31.241095] brcmfmac

Bug#977647: 5.10.4 Debian kernel does not boot on amd64 with btrfs rootfs

[Ryutaroh Matsumoto]

  7.198838] RBP: 0002 R08:  R09: 55ee81373ff0
[7.198838] R10: 0011 R11: 0246 R12: 7ff6723a6e2d
[7.198839] R13:  R14: 55ee813330b0 R15: 55ee81379020
[7.198841] ---[ end trace 763ec261f802618a ]---

Best regards, Ryutaroh Matsumoto

-- Package-specific info:
** Version:
Linux version 5.10.0-4-amd64 (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.19-1 (2021-03-02)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.10.0-4-amd64 
root=UUID=676134ca-7200-4cf0-b363-ef93702a7a1c ro i8042.reset=1 intel_iommu=on 
i8042.nopnp

** Tainted: W (512)
 * kernel issued warning

** Kernel log:
[7.697570] usbcore: registered new interface driver uvcvideo
[7.700175] firmware_class: See https://wiki.debian.org/Firmware for 
information about missing firmware
[7.706044] USB Video Class driver (1.1.1)
[7.709730] RAPL PMU: API unit is 2^-32 Joules, 5 fixed counters, 655360 ms 
ovfl timer
[7.713280] RAPL PMU: hw unit of domain pp0-core 2^-14 Joules
[7.713281] RAPL PMU: hw unit of domain package 2^-14 Joules
[7.713282] RAPL PMU: hw unit of domain dram 2^-14 Joules
[7.713282] RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules
[7.713283] RAPL PMU: hw unit of domain psys 2^-14 Joules
[7.799578] alg: No test for fips(ansi_cprng) (fips_ansi_cprng)
[7.813519] audit: type=1400 audit(1614821632.324:2): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="lsb_release" pid=525 
comm="apparmor_parser"
[7.813753] audit: type=1400 audit(1614821632.324:3): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/bin/lxc-start" pid=535 
comm="apparmor_parser"
[7.814648] audit: type=1400 audit(1614821632.324:4): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-oopslash" 
pid=527 comm="apparmor_parser"
[7.818048] audit: type=1400 audit(1614821632.328:5): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=532 
comm="apparmor_parser"
[7.844320] audit: type=1400 audit(1614821632.328:6): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" 
pid=532 comm="apparmor_parser"
[7.844326] audit: type=1400 audit(1614821632.328:7): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-xpdfimport" 
pid=530 comm="apparmor_parser"
[7.844331] audit: type=1400 audit(1614821632.328:8): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=526 
comm="apparmor_parser"
[7.844335] audit: type=1400 audit(1614821632.328:9): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="man_filter" pid=526 
comm="apparmor_parser"
[7.844340] audit: type=1400 audit(1614821632.328:10): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="man_groff" pid=526 
comm="apparmor_parser"
[7.844345] audit: type=1400 audit(1614821632.328:11): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-senddoc" 
pid=528 comm="apparmor_parser"
[8.104937] iwlwifi :00:14.3: Detected Intel(R) Wi-Fi 6 AX201 160MHz, 
REV=0x354
[8.215971] Bluetooth: Core ver 2.22
[8.216006] NET: Registered protocol family 31
[8.216008] Bluetooth: HCI device and connection manager initialized
[8.216014] Bluetooth: HCI socket layer initialized
[8.216019] Bluetooth: L2CAP socket layer initialized
[8.216026] Bluetooth: SCO socket layer initialized
[8.293461] iwlwifi :00:14.3: base HW address: bc:54:2f:bc:8f:9a
[8.306026] thermal thermal_zone10: failed to read out thermal zone (-61)
[8.360383] intel_rapl_common: Found RAPL domain package
[8.360386] intel_rapl_common: Found RAPL domain core
[8.360388] intel_rapl_common: Found RAPL domain uncore
[8.360391] intel_rapl_common: Found RAPL domain dram
[8.360393] intel_rapl_common: Found RAPL domain psys
[8.360399] intel_rapl_common: RAPL package-0 domain package locked by BIOS
[8.360414] intel_rapl_common: RAPL package-0 domain dram locked by BIOS
[8.384742] snd_hda_intel :00:1f.3: DSP detected with PCI 
class/subclass/prog-if info 0x040100
[8.385172] iwlwifi :00:14.3 wlp0s20f3: renamed from wlan0
[8.395871] snd_hda_intel :00:1f.3: Digital mics found on Skylake+ 
platform, 

Bug#982840: linux-image-5.10.0-3-arm64: requesting scsi_debug.ko for arm64/armhf helping systemd autopkgtest

[Ryutaroh Matsumoto]

Control: retitle -1 requesting scsi_debug.ko for arm64 helping 
systemd autopkgtest

Lack of scsi_debug.ko is also observed for ppc64el.
Ryutaroh

Bug#982840: linux-image-5.10.0-3-arm64: requesting scsi_debug.ko for arm64/armhf helping systemd autopkgtest

[Ryutaroh Matsumoto]

The lack of scsci_debug.ko for arm64 also makes the autopkgtest-virt-qemu
testsuite fail with udisks2.
Ryutaroh

Bug#982840: linux-image-5.10.0-3-arm64: requesting scsi_debug.ko for arm64/armhf helping systemd autopkgtest

[Ryutaroh Matsumoto]

Package: src:linux
Version: 5.10.13-1
Severity: wishlist

Dear Maintainer,

Latest autopkgtest Salsa supports arm64 QEMU testbeds.
When we apply autopkgtest-virt-qemu --dpkg-architecture=arm64 or armhf on
systemd, the "storage" test fails because of
modprobe: FATAL: Module scsi_debug not found in directory 
/lib/modules/5.10.0-3-arm64

I talked with Michael Biebl on
https://salsa.debian.org/ci-team/autopkgtest/-/merge_requests/113#note_227958
he wondered if it is possible to enable scsi_debug on arm64

Best regards, Ryutaroh Matsumoto

-- Package-specific info:
** Version:
Linux version 5.10.0-3-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.1) #1 SMP 
Debian 5.10.13-1 (2021-02-06)

** Command line:
 dma.dmachans=0x37f5 bcm2709.boardrev=0xd03114 bcm2709.serial=0x488d2af3 
bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=42 
bcm2709.disk_led_active_low=0 smsc95xx.macaddr=DC:A6:32:BB:99:D9 
vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0  console=tty0 
console=ttyS1,115200 root=LABEL=RASPIROOT rw fsck.repair=yes net.ifnames=0  
rootwait rootfstype=ext4 module_blacklist=vc4

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

** Kernel log:
[   20.631603] systemd[1]: Mounting Huge Pages File System...
[   20.683486] systemd[1]: Mounting POSIX Message Queue File System...
[   20.736492] systemd[1]: Mounting Kernel Debug File System...
[   20.787618] systemd[1]: Mounting Kernel Trace File System...
[   20.836925] systemd[1]: Starting Restore / save the current clock...
[   20.889264] systemd[1]: Starting Set the console keyboard layout...
[   20.940552] systemd[1]: Starting Create list of static device nodes for the 
current kernel...
[   20.992153] systemd[1]: Starting Load Kernel Module configfs...
[   21.044220] systemd[1]: Starting Load Kernel Module drm...
[   21.095387] systemd[1]: Starting Load Kernel Module fuse...
[   21.138735] fuse: init (API version 7.32)
[   21.163989] systemd[1]: Condition check resulted in Set Up Additional Binary 
Formats being skipped.
[   21.164255] systemd[1]: Condition check resulted in File System Check on 
Root Device being skipped.
[   21.227986] systemd[1]: Starting Journal Service...
[   21.464155] systemd[1]: Starting Load Kernel Modules...
[   21.513840] systemd[1]: Starting Remount Root and Kernel File Systems...
[   21.563344] EXT4-fs (sda2): re-mounted. Opts: 
journal_async_commit,nobarrier,data=writeback,commit=3600
[   21.564141] systemd[1]: Starting Coldplug All udev Devices...
[   21.651478] systemd[1]: Mounted Huge Pages File System.
[   21.694010] systemd[1]: Started Journal Service.
[   22.064408] systemd-journald[243]: Received client request to flush runtime 
journal.
[   37.861091] vcc-sd: disabling
[   39.399477] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer
[   39.439887] vchiq: module is from the staging directory, the quality is 
unknown, you have been warned.
[   39.488816] iproc-rng200 fe104000.rng: hwrng registered
[   39.516318] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   39.610584] Module vc4 is blacklisted
[   39.638493] cfg80211: Loading compiled-in X.509 certificates for regulatory 
database
[   39.657619] cfg80211: Loaded X.509 cert 'b...@debian.org: 
577e021cb980e0e820821ba7b54b4961b8b4fadf'
[   39.678583] cfg80211: Loaded X.509 cert 'romain.per...@gmail.com: 
3abbc6ec146e09d1b6016ab9d6cf71dd233f0328'
[   39.700179] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   39.706556] io scheduler kyber registered
[   39.719922] platform regulatory.0: firmware: direct-loading firmware 
regulatory.db
[   39.787993] platform regulatory.0: firmware: direct-loading firmware 
regulatory.db.p7s
[   39.813752] alg: No test for fips(ansi_cprng) (fips_ansi_cprng)
[   39.844975] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio 
for chip BCM4345/6
[   39.863636] usbcore: registered new interface driver brcmfmac
[   39.877152] snd_bcm2835: module is from the staging directory, the quality 
is unknown, you have been warned.
[   39.905384] bcm2835_audio bcm2835_audio: card created with 8 channels
[   39.907090] brcmfmac mmc0:0001:1: firmware: direct-loading firmware 
brcm/brcmfmac43455-sdio.bin
[   39.925440] mc: Linux media interface: v0.10
[   39.956391] brcmfmac mmc0:0001:1: firmware: direct-loading firmware 
brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt
[   40.102108] videodev: Linux video capture interface: v2.00
[   40.107976] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio 
for chip BCM4345/6
[   40.108103] brcmfmac mmc0:0001:1: firmware: failed to load 
brcm/brcmfmac43455-sdio.clm_blob (-2)
[   40.108107] firmware_class: See https://wiki.debian.org/Firmware for 
information about missing firmware
[   40.108113] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available 
(err=-2), device may have limited channels available
[   40.109706] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Mar  1 
201

Bug#982167: linux-image-5.10.0-3-arm64: suspend and hibernation fail to work on raspi

[Ryutaroh Matsumoto]

Package: src:linux
Version: 5.10.12-1
Severity: normal

Dear Maintainer,

I wonder if suspend or hibernation works on any single board computer (SBC)
in a sensible way.

I run the Gnome desktop environment on RPi4 with Debian.
After some idle, it goes to suspend (so called "s2idle" as defined in
https://www.kernel.org/doc/html/latest/admin-guide/pm/sleep-states.html )

On usual x86 PC, touching a keyboard or a mouse make the computer to resume.
But with RPi4, no method seems able to make RPi4 resume from s2idle.

In addition, "systemctl hibernate" often causes kernel panic. Even with no 
panic,
turning off and on the power supply to RPi4 does not restore pre-hibernation
state, i.e., hibernation does not work.

If a distro includes an SBC-specific build of kernel with CONFIG_SUSPEND=n
and CONFIG_HIBERNATION=n, then the above problems probably cannot appear.

But Debian only ships generic kernel build for aarch64 with
CONFIG_SUSPEND=y and CONFIG_HIBERNATION=y.

If this is considered responsible by another package,
e.g. raspi-firmware, please feel free to reassign this.

This symptom can be supressed by

cat >/etc/systemd/sleep.conf.d/nosleep.conf <<'EOF'
[Sleep]
AllowSuspend=no
AllowHibernation=no
AllowSuspendThenHibernate=no
AllowHybridSleep=no
EOF

Best regards, Ryutaroh Matsumoto




-- Package-specific info:
** Version:
Linux version 5.10.0-3-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.1) #1 SMP 
Debian 5.10.12-1 (2021-01-30)

** Command line:
 dma.dmachans=0x37f5 bcm2709.boardrev=0xd03114 bcm2709.serial=0x488d2af3 
bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=42 
bcm2709.disk_led_active_low=0 smsc95xx.macaddr=DC:A6:32:BB:99:D9 
vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0  console=tty0 
console=ttyS1,115200 root=LABEL=RASPIROOT rw fsck.repair=yes net.ifnames=0  
rootwait rootfstype=btrfs module_blacklist=vc4

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

** Kernel log:

[0.00] Booting Linux on physical CPU 0x00 [0x410fd083]
[0.00] Linux version 5.10.0-3-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.1) #1 SMP Debian 5.10.12-1 (2021-01-30)
[0.00] Machine model: Raspberry Pi 4 Model B Rev 1.4
[0.00] efi: UEFI not found.
[0.00] Reserved memory: created CMA memory pool at 0x3700, 
size 64 MiB
[0.00] OF: reserved mem: initialized node linux,cma, compatible id 
shared-dma-pool
[0.00] NUMA: No NUMA configuration found
[0.00] NUMA: Faking a node at [mem 
0x-0x0001]
[0.00] NUMA: NODE_DATA [mem 0x1ff019b00-0x1ff01bfff]
[0.00] Zone ranges:
[0.00]   DMA  [mem 0x-0x3fff]
[0.00]   DMA32[mem 0x4000-0x]
[0.00]   Normal   [mem 0x0001-0x0001]
[0.00] Movable zone start for each node
[0.00] Early memory node ranges
[0.00]   node   0: [mem 0x-0x3b2f]
[0.00]   node   0: [mem 0x4000-0xfbff]
[0.00]   node   0: [mem 0x0001-0x0001]
[0.00] Zeroed struct page in unavailable ranges: 256 pages
[0.00] Initmem setup node 0 [mem 0x-0x0001]
[0.00] On node 0 totalpages: 2061056
[0.00]   DMA zone: 3788 pages used for memmap
[0.00]   DMA zone: 0 pages reserved
[0.00]   DMA zone: 242432 pages, LIFO batch:63
[0.00]   DMA32 zone: 12288 pages used for memmap
[0.00]   DMA32 zone: 770048 pages, LIFO batch:63
[0.00]   Normal zone: 16384 pages used for memmap
[0.00]   Normal zone: 1048576 pages, LIFO batch:63
[0.00] percpu: Embedded 33 pages/cpu s95192 r8192 d31784 u135168
[0.00] pcpu-alloc: s95192 r8192 d31784 u135168 alloc=33*4096
[0.00] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[0.00] Detected PIPT I-cache on CPU0
[0.00] CPU features: detected: EL2 vector hardening
[0.00] CPU features: kernel page table isolation forced ON by KASLR
[0.00] CPU features: detected: Kernel page table isolation (KPTI)
[0.00] CPU features: detected: Spectre-v2
[0.00] CPU features: detected: Spectre-v4
[0.00] CPU features: detected: ARM errata 1165522, 1319367, or 1530923
[0.00] Built 1 zonelists, mobility grouping on.  Total pages: 2028596
[0.00] Policy zone: Normal
[0.00] Kernel command line:  dma.dmachans=0x37f5 
bcm2709.boardrev=0xd03114 bcm2709.serial=0x488d2af3 bcm2709.uart_clock=4800 
bcm2709.disk_led_gpio=42 bcm2709.disk_led_active_low=0 
smsc95xx.macaddr=DC:A6:32:BB:99:D9 vc_mem.mem_base=0x3eb0 
vc_mem.mem_size=0x3ff0  console=tty0 console=ttyS1,115200 
root=LABEL=RASPIROOT rw fsck.repai

Bug#980980: linux-image-5.10.0-3-arm64: flood of false udev messages make udisks2 eat CPU usage on usb-booted raspi4

[Ryutaroh Matsumoto]

Package: src:linux
Version: 5.10.12-1
Followup-For: Bug #980980
Control: reopen -1
Control: found -1 5.10.12-1

Dear Maintainer,

The bug #980980 reappears with genuin Debian kernel 5.10.12,
when RPi4B 8GB model is booted from my USB MSD...
A mojor difference between Debian kernel 5.10.9 on which I do not
observe #980980, and 5.10.12 seems presence of vc4.ko...

Best regards, Ryutaroh Matsumoto

-- Package-specific info:
** Version:
Linux version 5.10.0-3-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.1) #1 SMP 
Debian 5.10.12-1 (2021-01-30)

** Command line:
 dma.dmachans=0x37f5 bcm2709.boardrev=0xd03114 bcm2709.serial=0x488d2af3 
bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=42 
bcm2709.disk_led_active_low=0 smsc95xx.macaddr=DC:A6:32:BB:99:D9 
vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0  root=LABEL=RASPIROOT rw 
fsck.repair=yes net.ifnames=0 cma=256M@256M rootwait rootfstype=ext4 
module_blacklist=vc4

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

** Kernel log:

[0.00] Booting Linux on physical CPU 0x00 [0x410fd083]
[0.00] Linux version 5.10.0-3-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.1) #1 SMP Debian 5.10.12-1 (2021-01-30)
[0.00] Machine model: Raspberry Pi 4 Model B Rev 1.4
[0.00] efi: UEFI not found.
[0.00] Reserved memory: bypass linux,cma node, using cmdline CMA params 
instead
[0.00] OF: reserved mem: node linux,cma compatible matching fail
[0.00] cma: Reserved 256 MiB at 0x1000
[0.00] NUMA: No NUMA configuration found
[0.00] NUMA: Faking a node at [mem 
0x-0x0001]
[0.00] NUMA: NODE_DATA [mem 0x1ff019b00-0x1ff01bfff]
[0.00] Zone ranges:
[0.00]   DMA  [mem 0x-0x3fff]
[0.00]   DMA32[mem 0x4000-0x]
[0.00]   Normal   [mem 0x0001-0x0001]
[0.00] Movable zone start for each node
[0.00] Early memory node ranges
[0.00]   node   0: [mem 0x-0x3b2f]
[0.00]   node   0: [mem 0x4000-0xfbff]
[0.00]   node   0: [mem 0x0001-0x0001]
[0.00] Zeroed struct page in unavailable ranges: 256 pages
[0.00] Initmem setup node 0 [mem 0x-0x0001]
[0.00] On node 0 totalpages: 2061056
[0.00]   DMA zone: 3788 pages used for memmap
[0.00]   DMA zone: 0 pages reserved
[0.00]   DMA zone: 242432 pages, LIFO batch:63
[0.00]   DMA32 zone: 12288 pages used for memmap
[0.00]   DMA32 zone: 770048 pages, LIFO batch:63
[0.00]   Normal zone: 16384 pages used for memmap
[0.00]   Normal zone: 1048576 pages, LIFO batch:63
[0.00] percpu: Embedded 33 pages/cpu s95192 r8192 d31784 u135168
[0.00] pcpu-alloc: s95192 r8192 d31784 u135168 alloc=33*4096
[0.00] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[0.00] Detected PIPT I-cache on CPU0
[0.00] CPU features: detected: EL2 vector hardening
[0.00] CPU features: kernel page table isolation forced ON by KASLR
[0.00] CPU features: detected: Kernel page table isolation (KPTI)
[0.00] CPU features: detected: Spectre-v2
[0.00] CPU features: detected: Spectre-v4
[0.00] CPU features: detected: ARM errata 1165522, 1319367, or 1530923
[0.00] Built 1 zonelists, mobility grouping on.  Total pages: 2028596
[0.00] Policy zone: Normal
[0.00] Kernel command line:  dma.dmachans=0x37f5 
bcm2709.boardrev=0xd03114 bcm2709.serial=0x488d2af3 bcm2709.uart_clock=4800 
bcm2709.disk_led_gpio=42 bcm2709.disk_led_active_low=0 
smsc95xx.macaddr=DC:A6:32:BB:99:D9 vc_mem.mem_base=0x3eb0 
vc_mem.mem_size=0x3ff0  root=LABEL=RASPIROOT rw fsck.repair=yes 
net.ifnames=0 cma=256M@256M rootwait rootfstype=ext4 module_blacklist=vc4
[0.00] Dentry cache hash table entries: 1048576 (order: 11, 8388608 
bytes, linear)
[0.00] Inode-cache hash table entries: 524288 (order: 10, 4194304 
bytes, linear)
[0.00] mem auto-init: stack:off, heap alloc:on, heap free:off
[0.00] software IO TLB: mapped [mem 
0x3730-0x3b30] (64MB)
[0.00] Memory: 4714240K/8244224K available (11648K kernel code, 2420K 
rwdata, 6848K rodata, 5312K init, 588K bss, 282704K reserved, 262144K 
cma-reserved)
[0.00] random: get_random_u64 called from 
__kmem_cache_create+0x3c/0x5c0 with crng_init=0
[0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[0.00] ftrace: allocating 37920 entries in 149 pages
[0.00] ftrace: allocated 149 pages with 4 groups
[0.00] rcu: Hierarchical RCU implementation.
[0.00] rcu: RCU

Bug#981616: Acknowledgement (linux-image-5.10.0-3-arm64-unsigned: WiFi does not work with vc4.ko on RPi4, module_blacklist=vc4 enables WiFi)

[Ryutaroh Matsumoto]

Control: retitle -1 5GHz WiFi does not work with vc4.ko on RPi4 and 4K display
Control: tags -1 + upstream
Control: severity -1 normal

It turns out that the reported symptom happens with 5GHz Wifi
and 4K display resolution at 30 Hz refreshing rate.

Since the condition is rather limited, I lowered severity to normal.
This is an upstream issue.
It is being discussed at "linux-rpi-kernel" mailing list.

Best regards, Ryutaroh Matsumoto

Bug#981616: linux-image-5.10.0-3-arm64-unsigned: WiFi does not work with vc4.ko on RPi4, module_blacklist=vc4 enables WiFi

[Ryutaroh Matsumoto]

Package: src:linux
Version: 5.10.12-1
Severity: important

Dear Maintainer,

With Debian kernel 5.10.12-1, WiFi does not work on my RPi 4B 8GB model.
Disabling vc4.ko by module_blacklist=vc4 in kernel command line
restores WiFi connection...

I have not yet verified if this is an upstream issue.

The network is configured by systemd-networkd and wpa_supplicant,
but I observe the same issue with ifupdown and NetworkManager.

Best regards, Ryutaroh Matsumoto

-- Package-specific info:
** Version:
Linux version 5.10.0-3-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.1) #1 SMP 
Debian 5.10.12-1 (2021-01-30)

** Command line:
 dma.dmachans=0x37f5 bcm2709.boardrev=0xd03114 bcm2709.serial=0x488d2af3 
bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=42 
bcm2709.disk_led_active_low=0 smsc95xx.macaddr=DC:A6:32:BB:99:D9 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  console=tty0 
root=LABEL=RASPIROOT rw fsck.repair=yes net.ifnames=0  rootwait rootfstype=ext4 
module_blacklist=vc4

** Tainted: CE (9216)
 * staging driver was loaded
 * unsigned module was loaded

** Kernel log:

[0.00] Booting Linux on physical CPU 0x00 [0x410fd083]
[0.00] Linux version 5.10.0-3-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.1) #1 SMP Debian 5.10.12-1 (2021-01-30)
[0.00] Machine model: Raspberry Pi 4 Model B Rev 1.4
[0.00] efi: UEFI not found.
[0.00] Reserved memory: created CMA memory pool at 0x3740, 
size 64 MiB
[0.00] OF: reserved mem: initialized node linux,cma, compatible id 
shared-dma-pool
[0.00] NUMA: No NUMA configuration found
[0.00] NUMA: Faking a node at [mem 
0x-0x0001]
[0.00] NUMA: NODE_DATA [mem 0x1ff019b00-0x1ff01bfff]
[0.00] Zone ranges:
[0.00]   DMA  [mem 0x-0x3fff]
[0.00]   DMA32[mem 0x4000-0x]
[0.00]   Normal   [mem 0x0001-0x0001]
[0.00] Movable zone start for each node
[0.00] Early memory node ranges
[0.00]   node   0: [mem 0x-0x3b3f]
[0.00]   node   0: [mem 0x4000-0xfbff]
[0.00]   node   0: [mem 0x0001-0x0001]
[0.00] Initmem setup node 0 [mem 0x-0x0001]
[0.00] On node 0 totalpages: 2061312
[0.00]   DMA zone: 3792 pages used for memmap
[0.00]   DMA zone: 0 pages reserved
[0.00]   DMA zone: 242688 pages, LIFO batch:63
[0.00]   DMA32 zone: 12288 pages used for memmap
[0.00]   DMA32 zone: 770048 pages, LIFO batch:63
[0.00]   Normal zone: 16384 pages used for memmap
[0.00]   Normal zone: 1048576 pages, LIFO batch:63
[0.00] percpu: Embedded 33 pages/cpu s95192 r8192 d31784 u135168
[0.00] pcpu-alloc: s95192 r8192 d31784 u135168 alloc=33*4096
[0.00] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[0.00] Detected PIPT I-cache on CPU0
[0.00] CPU features: detected: EL2 vector hardening
[0.00] CPU features: kernel page table isolation forced ON by KASLR
[0.00] CPU features: detected: Kernel page table isolation (KPTI)
[0.00] CPU features: detected: Spectre-v2
[0.00] CPU features: detected: Spectre-v4
[0.00] CPU features: detected: ARM errata 1165522, 1319367, or 1530923
[0.00] Built 1 zonelists, mobility grouping on.  Total pages: 2028848
[0.00] Policy zone: Normal
[0.00] Kernel command line:  dma.dmachans=0x37f5 
bcm2709.boardrev=0xd03114 bcm2709.serial=0x488d2af3 bcm2709.uart_clock=4800 
bcm2709.disk_led_gpio=42 bcm2709.disk_led_active_low=0 
smsc95xx.macaddr=DC:A6:32:BB:99:D9 vc_mem.mem_base=0x3ec0 
vc_mem.mem_size=0x4000  console=tty0 root=LABEL=RASPIROOT rw 
fsck.repair=yes net.ifnames=0  rootwait rootfstype=ext4 module_blacklist=vc4
[0.00] Dentry cache hash table entries: 1048576 (order: 11, 8388608 
bytes, linear)
[0.00] Inode-cache hash table entries: 524288 (order: 10, 4194304 
bytes, linear)
[0.00] mem auto-init: stack:off, heap alloc:on, heap free:off
[0.00] software IO TLB: mapped [mem 
0x3340-0x3740] (64MB)
[0.00] Memory: 4913088K/8245248K available (11648K kernel code, 2420K 
rwdata, 6848K rodata, 5312K init, 588K bss, 281488K reserved, 65536K 
cma-reserved)
[0.00] random: get_random_u64 called from 
__kmem_cache_create+0x3c/0x5c0 with crng_init=0
[0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[0.00] ftrace: allocating 37920 entries in 149 pages
[0.00] ftrace: allocated 149 pages with 4 groups
[0.00] rcu: Hierarchical RCU implementation.
[0.00] rcu: RCU restricting CPUs

Bug#980785: linux-image-5.10.0-1-arm64: vc4.ko garbles screen ouput on raspi 4B

[Ryutaroh Matsumoto]

Patches are incorporated into the 5.10-stable branch as

https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/diff/queue-5.10/drm-vc4-correct-lbm-size-and-calculation.patch?id=138ad5c64ba368c5e077b8c178c47f12b29b8701

https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/diff/queue-5.10/drm-vc4-correct-pos1_scl-for-hvs5.patch?id=138ad5c64ba368c5e077b8c178c47f12b29b8701

Best regards, Ryutaroh

Bug#979187: 5.9.15 Debian kernel stopped booting on raspi 4 with Elecom USB MSD 056e:6a13

[Ryutaroh Matsumoto]

Control: close -1 5.10.9-1

When "reset-raspberrypi.ko" and "raspberrypi-cpufreq.ko"
are loaded by initramfs, linux-image-arm64/sid can be booted from
my buggy USB MSD 056e:6a13.
It seems mysterious, but anyway I'd like to close #979187.

Best regards, Ryutaroh Matsumoto

Bug#977694: 5.10.4 Debian kernel does not boot on raspi 4 with ext4 rootfs and usb-msd

[Ryutaroh Matsumoto]

Control: reassign -1 raspi-firmware 1.20210111+ds-2

Booting linux kernel 5.10.x from USB MSD needs either
* loading reset-raspberrypi.ko in initramfs,
* or rebuild kernel with CONFIG_RESET_RASPBERRYPI=y in .config

Anyway, the combination of linux-image-arm64/sid and raspi-firmware/sid
does not allow booting RPi4 from USB-MSD.
Boot from USB-MSD was possible in Debian kernel 5.9 series.

I think this boot failure should be fixed by
echo reset-raspberrypi >/usr/share/initramfs-tools/modules.d/raspi-firmware.conf
instead of CONFIG_RESET_RASPBERRYPI=y.

If this is considered an issue in src:linux, please reassign this back.

Best regards, Ryutaroh Matsumoto

Bug#980980: linux-image-5.10.0-2-arm64-unsigned: flood of false udev messages make udisks2 eat CPU usage on usb-booted raspi4

[Ryutaroh Matsumoto]

Control: forwarded -1 
http://lists.infradead.org/pipermail/linux-rpi-kernel/2021-January/007985.html

Forwarded to the linux-rpi-kernel list. Ryutaroh

Bug#979187: 977694 & 979187 fixed-upstream but remain in Debian :-

[Ryutaroh Matsumoto]

I found that
CONFIG_RESET_RASPBERRYPI=y
is enough to fix #979187, while
CONFIG_RESET_RASPBERRYPI=m
is not.

I will submit an MR to salsa. Ryutaroh

Bug#980785: patch applied upstream

[Ryutaroh Matsumoto]

Control: tags -1 + fixed-upstream

The patch attached to this report was merged upstream (drm-misc-fixes branch)
as
https://cgit.freedesktop.org/drm/drm-misc/commit/drivers/gpu/drm/vc4?h=drm-misc-fixes=f6b57101a6b31277a4bde1d8028c46e898bd2ff2
https://cgit.freedesktop.org/drm/drm-misc/commit/drivers/gpu/drm/vc4?h=drm-misc-fixes=78e5330329ee206d6aa4593a90320fd837f7966e

This seems to satisfy the condition for Debian kernel patch
at
https://kernel-team.pages.debian.net/kernel-handbook/ch-bugs.html#s9.1.7

> 9.1.7. Applying patches
> Patches should normally be reviewed and accepted by the relevant upstream 
> maintainer
> (aside from necessary adjustments for an older kernel version) before being 
> applied.

Best regards, Ryutaroh Matsumoto

Bug#980980: linux-image-5.10.0-2-arm64-unsigned: flood of false udev messages make udisks2 eat CPU usage on usb-booted raspi4

[Ryutaroh Matsumoto]

Package: src:linux
Version: 5.10.9-1
Severity: important
Tags: upstream bullseye
Control: block -1 by 977694

Dear Maintainer,

After booting raspi 4b from USB MSDand installation of
udisks2 2.9.1-3 by
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977694#56

udev starts giving flood of false messages like below,
and the udisks2, udev and dbus daemons eat nearly 100% of CPU
in total. The flood of false messages disappears by removing udisks2
package.

This symptom is also observed with the vanilla upstream kernel.

Best regards, Ryutaroh Matsumoto


monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

KERNEL[1532.887313] change   
/devices/platform/emmc2bus/fe34.emmc2/mmc_host/mmc1/mmc1:0007/block/mmcblk1 
(block)
KERNEL[1532.887432] change   
/devices/platform/emmc2bus/fe34.emmc2/mmc_host/mmc1/mmc1:0007/block/mmcblk1/mmcblk1p1
 (block)
KERNEL[1532.887485] change   
/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda
 (block)
KERNEL[1532.887537] change   
/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda1
 (block)
KERNEL[1532.887588] change   
/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda2
 (block)
KERNEL[1532.887640] change   
/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda3
 (block)
UDEV  [1532.929456] change   
/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda
 (block)
UDEV  [1532.938261] change   
/devices/platform/emmc2bus/fe34.emmc2/mmc_host/mmc1/mmc1:0007/block/mmcblk1 
(block)
UDEV  [1532.945960] change   
/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda1
 (block)
UDEV  [1532.961346] change   
/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda2
 (block)
UDEV  [1532.966981] change   
/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda3
 (block)
UDEV  [1532.999693] change   
/devices/platform/emmc2bus/fe34.emmc2/mmc_host/mmc1/mmc1:0007/block/mmcblk1/mmcblk1p1
 (block)
KERNEL[1535.645238] change   
/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda2
 (block)
UDEV  [1535.656113] change   
/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda2
 (block)
KERNEL[1535.667023] change   
/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda2
 (block)
UDEV  [1535.677595] change   
/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda2
 (block)
KERNEL[1535.699075] change   
/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda2
 (block)
UDEV  [1535.711964] change   
/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda2
 (block)
KERNEL[1535.750938] change   
/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda2
 (block)
UDEV  [1535.762856] change   
/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda2
 (block)
KERNEL[1535.807667] change   
/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda2
 (block)
UDEV  [1535.822477] change   
/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda2
 (block)
KERNEL[1535.857299] change   
/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda2
 (block)
UDEV  [1535.871682] change   
/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda2
 (block)
KERNEL[1535.897123] change   
/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda2
 (block)
UDEV  [1535.911569] change   
/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda2
 (block)




-- Package-specific info:
** Version:
Linux version 5.10.0-2-arm64 (debian

Bug#979187: 977694 & 979187 fixed-upstream but remain in Debian :-

[Ryutaroh Matsumoto]

Control: severity -1 minor

The bug #979187 was the boot failure from the USB MSD
ID 056e:6a13 Elecom Co., Ltd ESD-EMN.

With the kernel .config

From: Ryutaroh Matsumoto 
> CONFIG_RESET_RASPBERRYPI=y
> CONFIG_ARM_RASPBERRYPI_CPUFREQ=y
> CONFIG_SENSORS_RASPBERRYPI_HWMON=y

Kernel mounted the root partition, but the USB MSD stopped
responding during the boot. The photo is
https://photos.app.goo.gl/QWMmrhyM9FT2WZ2f9

My impression is that this USB MSD is simply buggy...
But it worked with Debian kernel 5.9...

Since USB MSD looks very buggy, I lowered severity to minor...

Best regards, Ryutaroh Matsumoto

Bug#977694: 977694 & 979187 fixed-upstream but remain in Debian :-

[Ryutaroh Matsumoto]

Control: tags -1 + patch

> linux-config-5.10/sid, and the symptoms 977694 and 979187 are reproduced.
> My impression is that raspi4 USB-MSD boot failure can be fixed by properly
> changing .config. I will investigate what are required changes to the config.

I identified changes in .config enabling boot of raspi 4B from USB MSD.
The following script built a debian kernel package that can boot from
(not buggy) USB MSD. Build was done on raspi 4B.

#!/bin/bash
set -x
apt-get source linux/sid
cd linux-5.10.9
fakeroot make -f debian/rules.gen setup_arm64_none_arm64
cat >>debian/build/build_arm64_none_arm64/.config <<'EOF'
CONFIG_RESET_RASPBERRYPI=y
CONFIG_ARM_RASPBERRYPI_CPUFREQ=y
CONFIG_SENSORS_RASPBERRYPI_HWMON=y
EOF
yes | make -C debian/build/build_arm64_none_arm64 oldconfig
yes | fakeroot /usr/bin/make -j 12 -f debian/rules.gen 
binary-arch_arm64_none_arm64

I believe 
CONFIG_RESET_RASPBERRYPI=y
CONFIG_ARM_RASPBERRYPI_CPUFREQ=y
CONFIG_SENSORS_RASPBERRYPI_HWMON=y
fix 977694. On the other hand, the other issue 979187 remains.
I will report the situation of 979187 in a separete email.

Best regards, Ryutaroh Matsumoto
[0.00] Booting Linux on physical CPU 0x00 [0x410fd083]
[0.00] Linux version 5.10.0-2-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.1) #1 SMP Debian 5.10.9-1 (2021-01-20)
[0.00] Machine model: Raspberry Pi 4 Model B Rev 1.4
[0.00] efi: UEFI not found.
[0.00] Reserved memory: created CMA memory pool at 0x3700, 
size 64 MiB
[0.00] OF: reserved mem: initialized node linux,cma, compatible id 
shared-dma-pool
[0.00] NUMA: No NUMA configuration found
[0.00] NUMA: Faking a node at [mem 
0x-0x0001]
[0.00] NUMA: NODE_DATA [mem 0x1ff019b00-0x1ff01bfff]
[0.00] Zone ranges:
[0.00]   DMA  [mem 0x-0x3fff]
[0.00]   DMA32[mem 0x4000-0x]
[0.00]   Normal   [mem 0x0001-0x0001]
[0.00] Movable zone start for each node
[0.00] Early memory node ranges
[0.00]   node   0: [mem 0x-0x3b2f]
[0.00]   node   0: [mem 0x4000-0xfbff]
[0.00]   node   0: [mem 0x0001-0x0001]
[0.00] Zeroed struct page in unavailable ranges: 256 pages
[0.00] Initmem setup node 0 [mem 0x-0x0001]
[0.00] On node 0 totalpages: 2061056
[0.00]   DMA zone: 3788 pages used for memmap
[0.00]   DMA zone: 0 pages reserved
[0.00]   DMA zone: 242432 pages, LIFO batch:63
[0.00]   DMA32 zone: 12288 pages used for memmap
[0.00]   DMA32 zone: 770048 pages, LIFO batch:63
[0.00]   Normal zone: 16384 pages used for memmap
[0.00]   Normal zone: 1048576 pages, LIFO batch:63
[0.00] percpu: Embedded 33 pages/cpu s95192 r8192 d31784 u135168
[0.00] pcpu-alloc: s95192 r8192 d31784 u135168 alloc=33*4096
[0.00] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[0.00] Detected PIPT I-cache on CPU0
[0.00] CPU features: detected: EL2 vector hardening
[0.00] CPU features: kernel page table isolation forced ON by KASLR
[0.00] CPU features: detected: Kernel page table isolation (KPTI)
[0.00] CPU features: detected: Spectre-v2
[0.00] CPU features: detected: Spectre-v4
[0.00] CPU features: detected: ARM errata 1165522, 1319367, or 1530923
[0.00] Built 1 zonelists, mobility grouping on.  Total pages: 2028596
[0.00] Policy zone: Normal
[0.00] Kernel command line:  dma.dmachans=0x37f5 
bcm2709.boardrev=0xd03114 bcm2709.serial=0x488d2af3 bcm2709.uart_clock=4800 
bcm2709.disk_led_gpio=42 bcm2709.disk_led_active_low=0 
smsc95xx.macaddr=DC:A6:32:BB:99:D9 vc_mem.mem_base=0x3eb0 
vc_mem.mem_size=0x3ff0  root=LABEL=RASPIROOT rw fsck.repair=yes 
net.ifnames=0  rootwait
[0.00] Dentry cache hash table entries: 1048576 (order: 11, 8388608 
bytes, linear)
[0.00] Inode-cache hash table entries: 524288 (order: 10, 4194304 
bytes, linear)
[0.00] mem auto-init: stack:off, heap alloc:on, heap free:off
[0.00] software IO TLB: mapped [mem 
0x3300-0x3700] (64MB)
[0.00] Memory: 4911236K/8244224K available (11648K kernel code, 2420K 
rwdata, 6852K rodata, 5312K init, 588K bss, 282316K reserved, 65536K 
cma-reserved)
[0.00] random: get_random_u64 called from 
__kmem_cache_create+0x3c/0x590 with crng_init=0
[0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[0.00] ftrace: allocating 37908 entries in 149 pages
[0.00] ftrace: allocated 149 pages with 4 groups
[0.00] rcu: Hierarchical RCU implementation.
[0.00] rcu: RCU restricting 

Bug#968181: 968181 and 968188 are fixed in 5.10.5-1,Re: Bug#968181: 968181 and 968188 are fixed in 5.10.5-1

[Ryutaroh Matsumoto]

> Indeed, CONFIG_DRM_VC4=m has been mistakenly removed from the arm64 kernel
> configuration. I’ll propose a merge request to fix this.
> 
> Cheers,
> Vincent

Thank you. I though that the kernel team decided to suspend vc4.ko,
because of the garbled unreadable screen as reported at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980785
originally found by Lucas.

Best regards, Ryutaroh

Bug#968181: 968181 and 968188 are fixed in 5.10.5-1

[Ryutaroh Matsumoto]

Control: reopen 968181
Control: reopen 968188
Control: found 968181 5.10.9-1
Control: found 968188 5.10.9-1

 968181 missing DRI/DRM support on Raspberry Pi
 968188 4K display resolution is not recognized with Raspberry Pi 4B

Since gpu/drm/vc4.ko is disabled in 5.10.9-1 while it was enabled in 5.10.5-1,
the above two issues have come back (I unwelcome them...).

Best regards, Ryutaroh Matsumoto

Bug#977694: 977694 & 979187 fixed-upstream but remain in Debian :-

[Ryutaroh Matsumoto]

>> 5.10.9-1 is awaiting currently in NEW for beeing processed. Once that
>> enters unstable, can you please check with it, and if so then close
>> this bug with the respective version?
> 
> I do not observe 977694 nor 979187 on my self-compiled kernel,
> but 977694 & 979187 remain in 5.10.9-1... Strange...

I compiled the upstream kernel source with .config minimally changed (*) from
linux-config-5.10/sid, and the symptoms 977694 and 979187 are reproduced.
My impression is that raspi4 USB-MSD boot failure can be fixed by properly
changing .config. I will investigate what are required changes to the config.

(*) "minimal change" means the attached diff.

Ryutaroh
--- config.arm64_none_arm64 2021-01-23 03:49:19.579170266 +0900
+++ linux-5.10.9/.config2021-01-23 03:50:31.892570954 +0900
@@ -2,7 +2,7 @@
 # Automatically generated file; DO NOT EDIT.
 # Linux/arm64 5.10.9 Kernel Configuration
 #
-CONFIG_CC_VERSION_TEXT="gcc-10 (Debian 10.2.1-6) 10.2.1 20210110"
+CONFIG_CC_VERSION_TEXT="gcc (Debian 10.2.1-6) 10.2.1 20210110"
 CONFIG_CC_IS_GCC=y
 CONFIG_GCC_VERSION=100201
 CONFIG_LD_VERSION=23501
@@ -23,6 +23,7 @@
 # CONFIG_COMPILE_TEST is not set
 CONFIG_LOCALVERSION=""
 # CONFIG_LOCALVERSION_AUTO is not set
+CONFIG_BUILD_SALT=""
 CONFIG_DEFAULT_INIT=""
 CONFIG_DEFAULT_HOSTNAME="(none)"
 CONFIG_SWAP=y
@@ -416,8 +417,6 @@
 CONFIG_ARM64_TAGGED_ADDR_ABI=y
 CONFIG_COMPAT=y
 CONFIG_KUSER_HELPERS=y
-CONFIG_COMPAT_VDSO=y
-CONFIG_THUMB2_COMPAT_VDSO=y
 CONFIG_ARMV8_DEPRECATED=y
 CONFIG_SWP_EMULATION=y
 CONFIG_CP15_BARRIER_EMULATION=y
@@ -841,6 +840,7 @@
 # CONFIG_MODULE_SRCVERSION_ALL is not set
 CONFIG_MODULE_SIG=y
 # CONFIG_MODULE_SIG_FORCE is not set
+# CONFIG_MODULE_SIG_ALL is not set
 # CONFIG_MODULE_SIG_SHA1 is not set
 # CONFIG_MODULE_SIG_SHA224 is not set
 CONFIG_MODULE_SIG_SHA256=y
@@ -5603,6 +5603,7 @@
 # CONFIG_VIDEO_OV9640 is not set
 # CONFIG_VIDEO_OV9650 is not set
 # CONFIG_VIDEO_OV13858 is not set
+# CONFIG_VIDEO_VS6624 is not set
 # CONFIG_VIDEO_MT9M001 is not set
 # CONFIG_VIDEO_MT9M032 is not set
 # CONFIG_VIDEO_MT9M111 is not set
@@ -6156,6 +6157,8 @@
 CONFIG_FB_EFI=y
 # CONFIG_FB_OPENCORES is not set
 # CONFIG_FB_S1D13XXX is not set
+# CONFIG_FB_NVIDIA is not set
+# CONFIG_FB_RIVA is not set
 # CONFIG_FB_I740 is not set
 # CONFIG_FB_MATROX is not set
 # CONFIG_FB_RADEON is not set
@@ -6842,7 +6845,7 @@
 
 CONFIG_USB_OHCI_LITTLE_ENDIAN=y
 CONFIG_USB_SUPPORT=y
-CONFIG_USB_COMMON=m
+CONFIG_USB_COMMON=y
 CONFIG_USB_LED_TRIG=y
 CONFIG_USB_ULPI_BUS=m
 CONFIG_USB_CONN_GPIO=m
@@ -7772,7 +7775,7 @@
 #
 # Android
 #
-CONFIG_ASHMEM=m
+# CONFIG_ASHMEM is not set
 # CONFIG_ION is not set
 # end of Android
 
@@ -8879,10 +8882,7 @@
 # Android
 #
 CONFIG_ANDROID=y
-CONFIG_ANDROID_BINDER_IPC=m
-# CONFIG_ANDROID_BINDERFS is not set
-CONFIG_ANDROID_BINDER_DEVICES="binder"
-# CONFIG_ANDROID_BINDER_IPC_SELFTEST is not set
+# CONFIG_ANDROID_BINDER_IPC is not set
 # end of Android
 
 CONFIG_LIBNVDIMM=m
@@ -9072,6 +9072,9 @@
 CONFIG_FAT_DEFAULT_UTF8=y
 CONFIG_EXFAT_FS=m
 CONFIG_EXFAT_DEFAULT_IOCHARSET="utf8"
+CONFIG_NTFS_FS=m
+# CONFIG_NTFS_DEBUG is not set
+# CONFIG_NTFS_RW is not set
 # end of DOS/FAT/EXFAT/NT Filesystems
 
 #
@@ -9334,7 +9337,6 @@
 # CONFIG_ENCRYPTED_KEYS is not set
 CONFIG_KEY_DH_OPERATIONS=y
 CONFIG_SECURITY_DMESG_RESTRICT=y
-CONFIG_SECURITY_PERF_EVENTS_RESTRICT=y
 CONFIG_SECURITY=y
 CONFIG_SECURITYFS=y
 CONFIG_SECURITY_NETWORK=y
@@ -9376,7 +9378,6 @@
 CONFIG_LOCK_DOWN_KERNEL_FORCE_NONE=y
 # CONFIG_LOCK_DOWN_KERNEL_FORCE_INTEGRITY is not set
 # CONFIG_LOCK_DOWN_KERNEL_FORCE_CONFIDENTIALITY is not set
-CONFIG_LOCK_DOWN_IN_EFI_SECURE_BOOT=y
 CONFIG_INTEGRITY=y
 CONFIG_INTEGRITY_SIGNATURE=y
 CONFIG_INTEGRITY_ASYMMETRIC_KEYS=y
@@ -9662,7 +9663,9 @@
 #
 # Certificates for signature checking
 #
+CONFIG_MODULE_SIG_KEY="certs/signing_key.pem"
 CONFIG_SYSTEM_TRUSTED_KEYRING=y
+CONFIG_SYSTEM_TRUSTED_KEYS=""
 # CONFIG_SYSTEM_EXTRA_CERTIFICATE is not set
 CONFIG_SECONDARY_TRUSTED_KEYRING=y
 CONFIG_SYSTEM_BLACKLIST_KEYRING=y
@@ -9796,7 +9799,6 @@
 CONFIG_UCS2_STRING=y
 CONFIG_HAVE_GENERIC_VDSO=y
 CONFIG_GENERIC_GETTIMEOFDAY=y
-CONFIG_GENERIC_COMPAT_VDSO=y
 CONFIG_GENERIC_VDSO_TIME_NS=y
 CONFIG_FONT_SUPPORT=y
 CONFIG_FONTS=y

Bug#980785: linux-image-5.10.0-1-arm64: vc4.ko garbles screen ouput on raspi 4B

[Ryutaroh Matsumoto]

The emails related to this symptom and pathces have appeared in the dri-devel
mailing list as below:

https://lists.freedesktop.org/archives/dri-devel/2021-January/295093.html
https://lists.freedesktop.org/archives/dri-devel/2021-January/295094.html
https://lists.freedesktop.org/archives/dri-devel/2021-January/295083.html
https://lists.freedesktop.org/archives/dri-devel/2021-January/295086.html
https://lists.freedesktop.org/archives/dri-devel/2021-January/295111.html
https://lists.freedesktop.org/archives/dri-devel/2021-January/295121.html
https://lists.freedesktop.org/archives/dri-devel/2021-January/295122.html

Ryutaroh

Bug#977694: 977694 & 979187 fixed-upstream but remain in Debian :-

[Ryutaroh Matsumoto]

Control: found -1 5.10.9-1

Hi Salvatore, thank you very much for your attention!

From: Salvatore Bonaccorso 
Subject: Re: Bug#979187: 979187 is fixed-upstream
Date: Thu, 21 Jan 2021 11:34:13 +0100
> 5.10.9-1 is awaiting currently in NEW for beeing processed. Once that
> enters unstable, can you please check with it, and if so then close
> this bug with the respective version?

I do not observe 977694 nor 979187 on my self-compiled kernel,
but 977694 & 979187 remain in 5.10.9-1... Strange...

The photo of booting failure is at
https://photos.app.goo.gl/QFD1ZAept3Ks7wP66

When the booting device is USB-MSD and the kernel tries to mount the
root partition, it has not yet recognized any USB device, and fails to
mount the root partition. As such, my USB keyboard does not work, neither.

On the other hand, my compiled kernel somehow recognize USB devices
even when the booting device is a USB MSD. Its  dmesg is attached
to this email.

Disk images of USB-MSD are made by slightly modified version of
https://github.com/emojifreak/debian-rpi-image-script
Only the kernel package is changed.

My kernel .config is
http://153.240.174.134:64193/kernel-deb-5.9/config-arm64-5.10.9.txt

Best regards, Ryutaroh Matsumoto
[0.00] Booting Linux on physical CPU 0x00 [0x410fd083]
[0.00] Linux version 5.10.9 (root@raspi4b8gb) (gcc (Debian 10.2.1-6) 
10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.1) #1 SMP Fri Jan 22 
10:00:50 JST 2021
[0.00] Machine model: Raspberry Pi 4 Model B Rev 1.4
[0.00] efi: UEFI not found.
[0.00] Reserved memory: created CMA memory pool at 0x3700, 
size 64 MiB
[0.00] OF: reserved mem: initialized node linux,cma, compatible id 
shared-dma-pool
[0.00] NUMA: No NUMA configuration found
[0.00] NUMA: Faking a node at [mem 
0x-0x0001]
[0.00] NUMA: NODE_DATA [mem 0x1ff016b00-0x1ff018fff]
[0.00] Zone ranges:
[0.00]   DMA  [mem 0x-0x3fff]
[0.00]   DMA32[mem 0x4000-0x]
[0.00]   Normal   [mem 0x0001-0x0001]
[0.00] Movable zone start for each node
[0.00] Early memory node ranges
[0.00]   node   0: [mem 0x-0x3b2f]
[0.00]   node   0: [mem 0x4000-0xfbff]
[0.00]   node   0: [mem 0x0001-0x0001]
[0.00] Zeroed struct page in unavailable ranges: 256 pages
[0.00] Initmem setup node 0 [mem 0x-0x0001]
[0.00] On node 0 totalpages: 2061056
[0.00]   DMA zone: 3788 pages used for memmap
[0.00]   DMA zone: 0 pages reserved
[0.00]   DMA zone: 242432 pages, LIFO batch:63
[0.00]   DMA32 zone: 12288 pages used for memmap
[0.00]   DMA32 zone: 770048 pages, LIFO batch:63
[0.00]   Normal zone: 16384 pages used for memmap
[0.00]   Normal zone: 1048576 pages, LIFO batch:63
[0.00] percpu: Embedded 33 pages/cpu s95192 r8192 d31784 u135168
[0.00] pcpu-alloc: s95192 r8192 d31784 u135168 alloc=33*4096
[0.00] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[0.00] Detected PIPT I-cache on CPU0
[0.00] CPU features: detected: EL2 vector hardening
[0.00] CPU features: kernel page table isolation forced ON by KASLR
[0.00] CPU features: detected: Kernel page table isolation (KPTI)
[0.00] CPU features: detected: Spectre-v2
[0.00] CPU features: detected: Spectre-v4
[0.00] CPU features: detected: ARM errata 1165522, 1319367, or 1530923
[0.00] Built 1 zonelists, mobility grouping on.  Total pages: 2028596
[0.00] Policy zone: Normal
[0.00] Kernel command line:  dma.dmachans=0x37f5 
bcm2709.boardrev=0xd03114 bcm2709.serial=0x488d2af3 bcm2709.uart_clock=4800 
bcm2709.disk_led_gpio=42 bcm2709.disk_led_active_low=0 
smsc95xx.macaddr=DC:A6:32:BB:99:D9 vc_mem.mem_base=0x3eb0 
vc_mem.mem_size=0x3ff0  root=LABEL=RASPIROOT rw fsck.repair=yes 
net.ifnames=0 rootwait
[0.00] Dentry cache hash table entries: 1048576 (order: 11, 8388608 
bytes, linear)
[0.00] Inode-cache hash table entries: 524288 (order: 10, 4194304 
bytes, linear)
[0.00] mem auto-init: stack:off, heap alloc:on, heap free:off
[0.00] software IO TLB: mapped [mem 
0x3300-0x3700] (64MB)
[0.00] Memory: 4919276K/8244224K available (9664K kernel code, 2424K 
rwdata, 3528K rodata, 5312K init, 587K bss, 274288K reserved, 65536K 
cma-reserved)
[0.00] random: get_random_u64 called from 
__kmem_cache_create+0x48/0x404 with crng_init=0
[0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[0.00] ftrace: allocating 39727 entries in 156 pages
[0.00] ftrace: allocated 156 pages with 4 groups
[0.00] rcu: Hierarchical RCU i

Bug#968181: 968181 and 968188 are fixed in 5.10.5-1

[Ryutaroh Matsumoto]

Control: close 968181 5.10.5-1
Control: close 968188 5.10.5-1

 968181 missing DRI/DRM support on Raspberry Pi
 968188 4K display resolution is not recognized with Raspberry Pi 4B

I confirm that vc4.ko in 5.10.5-1 can show 4K output and it provides 
/dev/dri/card0.
The gdm3 display manager and the gnome session (both using wayland) work well
with vc4.ko on my raspi 4B 8GB mode.

Some comments:
The default CMA size 64 MB is insufficient for gdm3 with 4K resolution as 
reportet at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980536

"disable_fw_kms_setup=1" is necessary in "config.txt" of raspi, as reported at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977642

The latter is actually a bug in the upstream kernel. Today I was told that
it has been fixed upstream at the dri-devel mailing list from Maxime Ripard.

Best regards, Ryutaroh Matsumoto

Bug#977645: 977642 is fixed in 5.10.5-1

[Ryutaroh Matsumoto]

> On the other hand, vc4.ko gives completely garbled screen to my 4K HDMI
> display, and disable_fw_kms_setup=1 does not help unlike
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977642

I am sorry, with disable_fw_kms_setup=1, vc4.ko works fine.
Without disable_fw_kms_setup=1, vc4.ko gives garbled screen...
Ryutaroh

Bug#979187: 979187 is fixed-upstream

[Ryutaroh Matsumoto]

Control: tags -1 + fixed-upstream

Self-compiled 5.10.9 does not show this reported symptom,
and I assume this is fixed-upstream. Ryutaroh

Bug#977645: 977642 is fixed in 5.10.5-1

[Ryutaroh Matsumoto]

Control: fixed -1 5.10.5-1

I verified that linux-image-arm64 5.10.5-1 at least boots on
my raspi 4B 8GB model.

On the other hand, vc4.ko gives completely garbled screen to my 4K HDMI
display, and disable_fw_kms_setup=1 does not help unlike
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977642

Giving module_blacklist=vc4 to the kernel command line helps.
On the other hand, vc4.ko in the upstream 5.10.9 with disable_fw_kms_setup=1
works well, and I expect it will get better with no extra packaging effort.

Best regards, Ryutaroh Matsumoto

Bug#968181: linux-image-5.7.0-2-arm64: DRM unavailable on Rapsberry Pi 4B

[Ryutaroh Matsumoto]

Control: forwarded -1 https://github.com/raspberrypi/firmware/issues/1247
Control: tags -1 + fixed-upstream

> On the other hand, gdm3 and weston gives the following error in dmesg,
> "kernel: [drm:vc4_bo_create [vc4]] *ERROR* Failed to allocate from CMA:"
> and no graphics come. Rendering by wayland does not work at all with
> vc4.ko in 5.10.9.

The above symptom is "fixed" by adding
CMA=256M@128M
to the kernel command line.

Then the gdm3 display manager starts up well, and I have
# grep -i cma /proc/meminfo 
CmaTotal: 262144 kB
CmaFree:      143008 kB

Best regards, Ryutaroh Matsumoto

Bug#968181: linux-image-5.7.0-2-arm64: DRM unavailable on Rapsberry Pi 4B

[Ryutaroh Matsumoto]

Hi all,

This is an update to
Bug#968181: linux-image-5.7.0-2-arm64: DRM unavailable on Rapsberry Pi 4B

I compiled Linux 5.10.9 by myself, and xinit starts fine without installing
the Debian package xserver-xorg-video-fbdev. When I originally reported this
#968181, the graphics on my raspi can only be used through 
xserver-xorg-video-fbdev.

X server works fine by using
/dev/dri/card0 on my raspi 4B 8GB model.
DRI/DRM on raspi started to partially work.

On the other hand, gdm3 and weston gives the following error in dmesg,
"kernel: [drm:vc4_bo_create [vc4]] *ERROR* Failed to allocate from CMA:"
and no graphics come. Rendering by wayland does not work at all with
vc4.ko in 5.10.9.

Best regards, Ryutaroh

Bug#968188: 968188 seems fixed upstream

[Ryutaroh Matsumoto]

Control: tags -1 + fixed-upstream

I compiled the upstream kernel 5.10.8 and it can use 4K resolution. Ryutaroh

Bug#977694: #977694: seems fixed upstream

[Ryutaroh Matsumoto]

Control: tags -1 + fixed-upstream

I compiled the upstream kernel 5.10.8, and it boots well from a USB MSD.
5.10.6 and older seem unable to find any USB device connected to
Raspberry Pi 4B 8GB, and 5.10.8 seems to have no problem with
USB on Raspberry Pi 4B 8GB.

Ryutaroh Matsumoto

Bug#977647: 5.10.1 Debian kernel does not boot on amd64 with btrfs rootfs

[Ryutaroh Matsumoto]

Control: tags -1 + moreinfo

Hi Nicholas, thanks again for your response.

In my new year holidays, I built the upstream (not Debian)
5.10.6 kernel and saw what happend. The situation got better,
* booting always succeeded (at least I did not observe it)
* tpm error persisted
* I did "systemctl poweroff" immediately after I got "login:".
  The shutdown behavior was very strange, many systemd services cannot be
  stopped cleanly and timeouts occurred many times. I cut the power line
  after waiting 5 minutes or so.

I'd like to see the situation again after the upstream version gets 5.10.10 or
so, because, for I now have very little (or no) trust on the upstream (not 
Debian)
kernel as

* arm64 kernel does not boot at all on raspberry pi 4B on USB MSD
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977694
* arm64 kernel did not boot on raspberry pi 4B on SD card,
  (all usual booting devices did not work). It seems fixed in upstream 5.10.6
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977645
* wireless network does not work on raspberry pi 4B
  (this has not been reported as booting on my raspi has not been confirmed
  on any Debian kernel).

Simply, I am tired of seeing if 5.10.? kernel works normally or not on my 
machines.
I have seen little problem in Debian 5.9.* series.
Since 5.10 is LTS, maybe 5.10.10 or 5.10.20 will gets as good as 5.9.15.
I will stick to Debian 5.9.15 kernel on my amd64 notebook and raspi4b
for a while...

Best regards, Ryutaroh Matsumoto

Bug#979187: 5.9.15 Debian kernel stopped booting on raspi 4 with Elecom USB MSD 056e:6a13

[Ryutaroh Matsumoto]

Hi,

> reportbug linux-image-5.9.0-5-arm64
> while booted with this kernel and select the option to Follow-Up to this 
> bug (you might want to have the bug number handy), so that reportbug can 
> collect more information about your system.

I wanted to do that, but as the kernel does not boot with the
problematic USB MSD, I cannot use reportbug on it.
Did you mean that I should boot linux-image-5.9.0-5-arm64
on an sdcard or another usb msd, and run reportbug on it?

As I wrote in another email, screenshot of failing boot is placed at
https://photos.app.goo.gl/gCHUEXJB74hsWQtTA

Ryutaroh

Bug#977694: 5.10.4 Debian kernel does not boot on raspi 4 with ext4 rootfs and usb-msd

[Ryutaroh Matsumoto]

Control: reassign -1 linux-image-5.10.0-1-arm64 5.10.4-1
Control: retitle -1 5.10.4 Debian kernel does not boot on raspi 4 with ext4 
rootfs and usb-msd

I checked the reported symptom with
linux-image-5.10.0-1-arm64 5.10.4-1

The symptom remains the same, unlike
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977645

I have checked the symptom with two usb msds, one is hdd and the other is ssd.

Ryutaroh

Bug#977645: 5.10.1 Debian kernel does not boot on raspi 4 with ext4 rootfs and sdcard

[Ryutaroh Matsumoto]

Control: reassign -1 linux-image-5.10.0-1-arm64 5.10.4-1
Control: severity -1 important

I checked the reported symptom with
linux-image-5.10.0-1-arm64 5.10.4-1

It booted with completely garbled screen output.
disable_fw_kms_setup=1 in config.txt did not help.
Removing vc4.ko let the screen output normal.
/proc/cmdline looked like
dma.dmachans=0x71f5 bcm2709.boardrev=0xd03114 bcm2709.serial=0x488d2af3 
bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=42 
bcm2709.disk_led_active_low=0 smsc95xx.macaddr=DC:A6:32:BB:99:D9 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  console=tty0 
console=ttyS1,115200 root=LABEL=RASPIROOT rw fsck.repair=yes net.ifnames=0 
cma=64M rootwait

Ryutaroh

Bug#977647: 5.10.4 Debian kernel does not boot on amd64 with btrfs rootfs

[Ryutaroh Matsumoto]

Control: retitle 977647 5.10.4 Debian kernel does not boot on amd64 with btrfs 
rootfs
Control: reassign 977647 linux-image-5.10.0-1-amd64 5.10.4-1

I installed (signed) linux-image-5.10.0-1-amd64 5.10.4-1 on my laptop 
incompatible
with Linux 5.10.2. It still fails to boot.

On the other hand, I re-confirm that
linux-image-5.9.0-5-amd64 5.9.15-1 boots well and there seems no problem with 
it...

Best regards, Ryutaroh Matsumoto

Bug#977647: 5.10.1 Debian kernel does not boot on amd64 with btrfs rootfs

[Ryutaroh Matsumoto]

Hi Nicholas,
Thank you very much for your attention!

> Is it possible to shift+page-up to reveal the backtrace?  The backtrace
> section ends with "---[ end trace 75435… ]---"

My laptop has combined page-up + arrow-up.
Page-up is "Fn" + "arrow-up".
Shift+"Fn"+"arrow-up" doesn't work.

Shift+arrow-up shows mixture of console and gdm starting up screen
as below. Funny!!
https://photos.app.goo.gl/7LdpPCcJxb51RYXA8
In addition, I tried to boot it several times, and almost everytime
I tried today, booting failed at a later point than reported originally
(but I do not have a way to type a username...)
Boot failures themselves are unreliable...

> If that's not possible,
> see if you can get a copy from /var/log after rebooting with a working
> kernel or when using a network disk.

/var/log/kern.log does not have information of 5.10.1...

> If that's not possible, and you
> have good reflexes, you could try ctr+s or scroll-lock to pause the
> kernel output at just the right moment,

I found that once in ten times, booting succeeds and I got dmesg and 
/proc/mounts
of 5.10.1 as attached...

> Finally, what btrfs features (profiles, compression, layers of storage,
> etc) are being used?

Please have a look at attached file. Less usual one is compress-force=lzo.
If I remember it correctly, all files are lzo-compressed.

Best regards, Ryutaroh
[0.00] microcode: microcode updated early to revision 0xe0, date = 
2020-07-08
[0.00] Linux version 5.10.0-trunk-amd64 
(debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-1) 10.2.1 20201207, GNU 
ld (GNU Binutils for Debian) 2.35.1) #1 SMP Debian 5.10.1-1~exp1 (2020-12-17)
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-trunk-amd64 
root=UUID=676134ca-7200-4cf0-b363-ef93702a7a1c ro 
systemd.unified_cgroup_hierarchy=1 i8042.reset=1 intel_iommu=on i8042.nopnp
[0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point 
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
[0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[0.00] x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
[0.00] x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
[0.00] x86/fpu: Enabled xstate features 0x1f, context size is 960 
bytes, using 'compacted' format.
[0.00] BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009dfff] usable
[0.00] BIOS-e820: [mem 0x0009e000-0x0009efff] reserved
[0.00] BIOS-e820: [mem 0x0009f000-0x0009] usable
[0.00] BIOS-e820: [mem 0x000a-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0x7abf1fff] usable
[0.00] BIOS-e820: [mem 0x7abf2000-0x829a3fff] reserved
[0.00] BIOS-e820: [mem 0x829a4000-0x82ad3fff] ACPI data
[0.00] BIOS-e820: [mem 0x82ad4000-0x82bd8fff] ACPI NVS
[0.00] BIOS-e820: [mem 0x82bd9000-0x84894fff] reserved
[0.00] BIOS-e820: [mem 0x84895000-0x84b4efff] type 20
[0.00] BIOS-e820: [mem 0x84b4f000-0x84b4] usable
[0.00] BIOS-e820: [mem 0x84b5-0x897f] reserved
[0.00] BIOS-e820: [mem 0xe000-0xefff] reserved
[0.00] BIOS-e820: [mem 0xfe00-0xfe010fff] reserved
[0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved
[0.00] BIOS-e820: [mem 0xfed0-0xfed03fff] reserved
[0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved
[0.00] BIOS-e820: [mem 0xff00-0x] reserved
[0.00] BIOS-e820: [mem 0x0001-0x0004747f] usable
[0.00] NX (Execute Disable) protection: active
[0.00] efi: EFI v2.70 by American Megatrends
[0.00] efi: ACPI=0x82ad3000 ACPI 2.0=0x82ad3014 TPMFinalLog=0x82b25000 
SMBIOS=0x84614000 SMBIOS 3.0=0x84613000 MEMATTR=0x73826018 ESRT=0x75b99d98 
[0.00] secureboot: Secure boot could not be determined (mode 0)
[0.00] SMBIOS 3.2.0 present.
[0.00] DMI: Panasonic Corporation CFSV9-2/CFSV9-2L, BIOS V2.00L12 
04/20/2020
[0.00] tsc: Detected 1600.000 MHz processor
[0.00] tsc: Detected 1599.960 MHz TSC
[0.000400] e820: update [mem 0x-0x0fff] usable ==> reserved
[0.000405] e820: remove [mem 0x000a-0x000f] usable
[0.000416] last_pfn = 0x474800 max_arch_pfn = 0x4
[0.000423] MTRR default type: write-back
[0.000425] MTRR fixed ranges enabled:
[0.000427]   0-9 write-back
[0.000428]   

Bug#977694: 5.10.1 Debian kernel does not boot on raspi 4 with ext4 rootfs and usb-msd

[Ryutaroh Matsumoto]

Package: linux-image-5.10.0-trunk-arm64-unsigned
Version: 5.10.1-1~exp1
Severity: grave
Justification: renders package unusable

Dear Debian kernel maintainers,

This is somewhat similar to
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977645
but I assume this is a different issue as booting stops at a different point.

Debian kernel 5.10.1 in experimental does not boot on my raspberry pi 4.
I tried to boot it from an usb-msd (not an SD card) with ext4 root partition.
Partitioining is gpt (not msdos). btrfs is blacklisted.
Booting succeeds with Debian kernel 5.9.x.
lsusb -v of the usb bsd is shown at the bottom.

Photo of boot console is found at
https://photos.app.goo.gl/WAY2NgXpFsudNQ5CA

Best regards, Ryutaroh Matsumoto



Bus 002 Device 003: ID 056e:6a13 Elecom Co., Ltd ESD-EMN
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   3.20
  bDeviceClass0 
  bDeviceSubClass 0 
  bDeviceProtocol 0 
  bMaxPacketSize0 9
  idVendor   0x056e Elecom Co., Ltd
  idProduct  0x6a13 
  bcdDevice   11.00
  iManufacturer   1 ELECOM
  iProduct2 ESD-EMN
  iSerial 3 20B10164305600A9
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   0x0079
bNumInterfaces  1
bConfigurationValue 1
iConfiguration  0 
bmAttributes 0x80
  (Bus Powered)
MaxPower  504mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   2
  bInterfaceClass 8 Mass Storage
  bInterfaceSubClass  6 SCSI
  bInterfaceProtocol 80 Bulk-Only
  iInterface  0 
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01  EP 1 OUT
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0400  1x 1024 bytes
bInterval   0
bMaxBurst   8
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82  EP 2 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0400  1x 1024 bytes
bInterval   0
bMaxBurst   8
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   1
  bNumEndpoints   4
  bInterfaceClass 8 Mass Storage
  bInterfaceSubClass  6 SCSI
  bInterfaceProtocol 98 
  iInterface  0 
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01  EP 1 OUT
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0400  1x 1024 bytes
bInterval   0
bMaxBurst   8
MaxStreams  4
Data-out pipe (0x04)
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82  EP 2 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0400  1x 1024 bytes
bInterval   0
bMaxBurst   8
MaxStreams  4
Data-in pipe (0x03)
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03  EP 3 OUT
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0400  1x 1024 bytes
bInterval   0
bMaxBurst   0
Command pipe (0x01)
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84  EP 4 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0400  1x 1024 bytes
bInterval   0
bMaxBurst   8
MaxStreams  4
Status pipe (0x02)
Binary Object Store Descriptor:
  bLength 5
  bDescriptorType15

Bug#977647: 5.10.1 Debian kernel does not boot on amd64 with btrfs rootfs

[Ryutaroh Matsumoto]

Package: linux-image-5.10.0-trunk-amd64-unsigned
Version: 5.10.1-1~exp1
Severity: grave
Justification: renders package unusable

Dear Debian kernel maintainers,

Debian kernel 5.10.1 in experimental does not boot on my x86_64 notebook
with btrfs rootfs.
As I am suspecting btrfs as
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977645

This strengthen my suspicion about 5.10.1 btrfs...

Photo of booting console is found at
https://photos.app.goo.gl/zyCg4ZH8zDgwoiBr8

We observe that systemd accessed some files in btrfs rootfs,
so the situation seems somewhat better than
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977645

Best regards, Ryutaroh Matsumoto

Bug#977645: 5.10.1 Debian kernel does not boot on raspi 4 with ext4 rootfs and sdcard

[Ryutaroh Matsumoto]

Package: linux-image-5.10.0-trunk-arm64-unsigned
Version: 5.10.1-1~exp1
Severity: grave
Justification: renders package unusable

Dear Debian kernel maintainers,

Debian kernel 5.10.1 in experimental does not boot on my raspberry pi 4.
I tried to boot it from an SD card with ext4 root partition.
Partitioining is msdos (not gpt).

I was always able to boot it in the same configuration,
when I used my compiled vanilla 5.10.1 or "git clone"'ning from salsa.debian.

When I use vanilla or salsa.debian.org 5.10.1, booting ALWAYS fails
if rootfs is btrfs.

Photo of boot console is found at
https://photos.app.goo.gl/A755wZKvqneX1WvY6

We observe that booting fails at btrfs.
To me, 5.10.1 btrfs looks very suspicious...

I will see if what will happen with x86_64 with btrfs rootfs...

Best regards, Ryutaroh Matsumoto

Bug#977438: linux: Pls. consider DRM_VC4_HDMI_CEC

[Ryutaroh Matsumoto]

Control: retitle -1 Pls. consider DRM_VC4_HDMI_CEC

I change the issue title following suggestion by Vinent.

From: Ryutaroh Matsumoto 
Subject: Re: Bug#977438: linux: Pls. consider DRM_VC4_HDMI_CEC
Date: Fri, 18 Dec 2020 09:30:49 +0900 (JST)

> Hi Vincent,
> 
> Thank you for your attention and MR.
> 
>> I see that in a follow-up
>> email you're asking for more configuration options to be enabled; It
>> would probably be better to open a new bug report for those.
> 
> I will do so, after a 5.10.x package enters into experimental or unstable,
> I built a Debian kernel pkg with proposed config, and test it.
> 
> Best regards, Ryutaroh

Bug#977438: linux: Pls. consider DRM_VC4_HDMI_CEC

[Ryutaroh Matsumoto]

Hi Vincent,

Thank you for your attention and MR.

> I see that in a follow-up
> email you're asking for more configuration options to be enabled; It
> would probably be better to open a new bug report for those.

I will do so, after a 5.10.x package enters into experimental or unstable,
I built a Debian kernel pkg with proposed config, and test it.

Best regards, Ryutaroh

Bug#968181: v3d.ko for RPi4

[Ryutaroh Matsumoto]

Hi Lucas,

This is in response to your message
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968181#14

>B/ RPI4 support in the kernel v3d driver
>(B) requires less work, so should come next quite quickly.

I tried loading v3d.ko to the vanilla 5.10.1 kernel, but
doing so did not bring /dev/dri/render*, which appears and
enables GPU acceleration on Ubuntu kernel for RPi4.

I reported it to 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977441#27

Bringing GPU acceleration to Debian kernel seems to need some work.

On the other hand, I also have the garbled screen on my 4K HDMI display
as you wrote at
http://lists.infradead.org/pipermail/linux-rpi-kernel/2020-November/007894.html

Best regards, Ryutaroh Matsumoto

Bug#977441: linux: Pls. consider CONFIG_DRM_V3D

[Ryutaroh Matsumoto]

Control: retitle 968181 GPU/DRM acceleration unavailable on Raspberry Pi

I modprobe'ed v3d.ko on vanilla Linux kernel 5.10.1,
but /dev/dri/render* does not appear like

https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880125/comments/14
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876/comments/33

Simply compiling and loading v3d do not seem to enable
DRM/GPU acceleration on RPi4... We may need some work for enabling GPU
acceleration on Raspberry Pi series...
Ryutaroh

Bug#977575: raspberry pi touch screen support

[Ryutaroh Matsumoto]

Source: linux
Version: 5.10.1-1~exp1
Severity: wishlist

Dear Debian kernel maintainers,

debian/config/arm64/config on salsa.debian.org has
CONFIG_DRM_PANEL_RASPBERRYPI_TOUCHSCREEN=m

suggesting intention of supporting the official raspi touch screen...

But the following config items are disabled now, which seems contradicting...

CONFIG_TOUCHSCREEN_RASPBERRYPI_FW=m
CONFIG_REGULATOR_RASPBERRYPI_TOUCHSCREEN_ATTINY=m

may provide better support of raspi touch screnn.

Best regards, Ryutaroh Matsumoto

Bug#977438: Pls. consider raspi-related configs for kernel 5.10

[Ryutaroh Matsumoto]

Control: retitle -1 Pls. consider raspi-related configs for 5.10
Control: tags -1 + patch
Control: block 968181 by 977441

Dear Debian kernel maintainers,
CC: the Debian ARM list,

Could you consider enabling the following kernel compilation
options for Raspberry Pi 3&4 series for kernel 5.10?
The patch is against latest package source at salsa.debian.org.

--- debian/config/arm64/config-orig 2020-12-16 09:46:18.645380333 +0900
+++ debian/config/arm64/config  2020-12-16 10:22:17.998897582 +0900
@@ -424,6 +424,11 @@
 ## file: drivers/gpu/drm/vc4/Kconfig
 ##
 CONFIG_DRM_VC4=m
+CONFIG_DRM_VC4_HDMI_CEC=y
+CONFIG_DRM_V3D=m
+CONFIG_BCM_VIDEOCORE=m
+CONFIG_BCM2835_VCHIQ=m
+CONFIG_BCM2835_VCHIQ_MMAL=m
 
 ##
 ## file: drivers/gpu/host1x/Kconfig
@@ -443,6 +448,7 @@
 CONFIG_SENSORS_PWM_FAN=m
 CONFIG_SENSORS_SL28CPLD=m
 CONFIG_SENSORS_XGENE=m
+CONFIG_SENSORS_RASPBERRYPI_HWMON=m
 
 ##
 ## file: drivers/hwspinlock/Kconfig
@@ -1006,6 +1012,7 @@
 CONFIG_PINCTRL_AMD=y
 CONFIG_PINCTRL_SINGLE=y
 CONFIG_PINCTRL_MAX77620=y
+CONFIG_PINCTRL_BCM2835=y
 
 ##
 ## file: drivers/pinctrl/qcom/Kconfig
@@ -1093,6 +1100,7 @@
 ## file: drivers/reset/Kconfig
 ##
 CONFIG_RESET_CONTROLLER=y
+CONFIG_RESET_RASPBERRYPI=m
 
 ##
 ## file: drivers/rpmsg/Kconfig
@@ -1136,6 +1144,7 @@
 ## file: drivers/soc/bcm/Kconfig
 ##
 CONFIG_RASPBERRYPI_POWER=y
+CONFIG_BCM2835_POWER=y
 
 ##
 ## file: drivers/soc/fsl/Kconfig


I have already built a Debian package with the above options
from the latest master branch source on salsa.debian.org, and observed
the following on RPi4:

(1) CONFIG_DRM_V3D has no effect, as
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977441#18

(2) HDMI display resolution can become 4K and fixing an important bug
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968188

(3) /dev/dri/render* does not appear unlike

https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880125/comments/14
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876/comments/33

GPU/DRM acceleration remains unusable on RPi4, and bug 968181
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968181
remains open. 968181 seems blocked by 977441.

(4) My built Debian kernel 5.10.1 can boot from my usb mass storage device
ID 04bb:0168 I-O Data Device, Inc. I-O DATA HDPH-UT
but cannot access the root filesystem... My USB MSD mergenally worked
with Debian kernel 5.9.* and can compile the Debian kernel package.
My USB MSD  requires periodical reset by the Debian kernel 5.9.*,
which suggests this MSD is buggy... I ordered a faster SSD-based USB MSD.

(5) Raspberry Pi Wireless cannot be used by my built Debian kernel 5.10.1.
The wirelss has worked perfectly with Debian kernel 5.7--5.9.

I will see what will happen with a Debian kernel package 5.10*
both with and without proposed patch, and report it back,
when it arrives in experimental or unstable.

Bes regards, Ryutaroh Matsumoto

Bug#977441: linux: Pls. consider CONFIG_DRM_V3D

[Ryutaroh Matsumoto]

Control: tags -1 + patch

Just adding CONFIG_DRM_V3D=m is not enough,
as reported at
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1876862/comments/5

The following patch seems necessary, which has been introduced in
the Ubuntu kernel.

change
linux/drivers/gpu/drm/v3d/kconfig
- depends on ARCH_BCM || ARCH_BCMSTB || COMPILE_TEST
+ depends on ARCH_BCM || ARCH_BCMSTB || ARCH_BCM2835 || COMPILE_TEST

Best regards, Ryutaroh Matsumoto

Bug#977126: panic log attached Re: linux-image-rpi does not boot by qemu-system-arm -machine raspi0

[Ryutaroh Matsumoto]

Control: retitle -1 linux-image-rpi does not boot by qemu-system-arm -machine 
raspi0 or raspi1ap

Booting a Debian armel kernel by grub-efi-arm:armel seems unnecessary
to everyone (?). So I changed the title.
If linux-image-rpi can boot on qemu-system-arm, then I can modify
autopkgtest-virt-qemu to use linux-image-rpi with no change.
Ryutaroh

Bug#977441: linux: Pls. consider CONFIG_DRM_V3D

[Ryutaroh Matsumoto]

Source: linux
Version: 5.9.11-1
Severity: wishlist

Dear Maintainer,

>From 5.10, Linux vc4 driver starts supporting Raspberry Pi GPU as
https://www.phoronix.com/scan.php?page=news_item=RPi4-Display-Linux-5.10-Coming

>From Ubuntu kernel experience, CONFIG_DRM_V3D seems necessary to
fully use its hardware acceleration, as
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876

Could you consider to enable CONFIG_DRM_V3D for arm64 and possibly
for armhf?

Best regards, Ryutaroh Matsumoto

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: arm64 (aarch64)

Kernel: Linux 5.9.0-4-arm64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#977438: linux: Pls. consider DRM_VC4_HDMI_CEC

[Ryutaroh Matsumoto]

Source: linux
Version: 5.9.11-1
Severity: wishlist

Dear Maintainer,

Could you consider to enable CONFIG_DRM_VC4_HDMI_CEC
for arm64 and possibly armhf?
It should enable cec-client command in Debian cec-util to
control some CEC-capable devices connected via HDMI.

Best regards, Ryutaroh Matsumoto


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: arm64 (aarch64)

Kernel: Linux 5.9.0-4-arm64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#977126: linux: No armel kernel can be booted by grub-efi-arm:armel

[Ryutaroh Matsumoto]

Hi Ben,

> But linux-image-rpi does not have the virtio driver, this option cannot
> be used (at least for now).
> 
> Can you try adding it?  You should be able to cross-build the kernel
> package quite easily if you use the profiles "cross,pkg.linux.notools".
> There are generic instructions at
> .

Thanks. I will. But please give me some time as I am in my working hour... 
I didn't have experience with u-boot'ing a Debian kernel, so maybe I need some
time to correctly build a qemu bootable image by u-boot-rpi:armel package...
Ryutaroh

Bug#977126: linux: No armel kernel can be booted by grub-efi-arm:armel

[Ryutaroh Matsumoto]

Hi Ben, thanks again for your response.

> We used to provide a 'versatile' flavour on armel, for the ARM
> Versatile boards that QEMU has supported for a long time.  I removed
> this flavour back in 2016 after finding that it had been broken for a
> while and no-one had reported it.  Adding that back might be an option,
> if the Raspberry Pi device emulation in QEMU is slow.  What do you
> think?

If nobody uses linux-image-versatile now, I don't want to request the
kernel team to revive it. It may/might increase the maintainance effort...

The minimum requirements by autopkgtest-virt-qemu are
* VM has at least two serial ports,
* the Linux kernel has a driver for them, and
* the Linux kernel has a driver for a storage attached to the VM.

On the other hand, RPi series has only one serial port by PL011.
So we need to attach another serial port to the VM. For armhf, arm64,
and ppc64el, I was advised to use virtconsole by Simon McVittie,
and it has worked fine as far as I see.

But linux-image-rpi does not have the virtio driver, this option cannot
be used (at least for now). Another option is to attach "pci-serial-2x"
to the qemu VM, but linux-image-rpi does not seem to have a PCI driver...
Yet another option is to attach "qemu-xhci" and "usb-serial" to the VM,
but "usb-serial" behaves much differently from isa/pci-serial and virtconsole
and it cannot be used by the current autopkgtest-virt-qemu as reported at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973038#40

> The usual practice is to use u-boot or some other board-specific boot
> loader, which can be configured by the flash-kernel package.  I don't
> think that works in QEMU.

I have not intensively investigated if we can boot linux-image-marvell
by qemu-system-arm and some u-boot Debian package...
I will see it within several days and report it back here.
First I will see u-boot-qemu Debian package and the qemu "virt" machine
can boot linux-image-marvell as suggested at
https://github.com/ARM-software/u-boot/blob/master/doc/README.qemu-arm

linux-image-marvell seems capable of handling PCI serial ports.
Storage options for QEMU VM seems only "ich9-ahci" and "sdhci-pci"...

Best regards, Ryutaroh

Bug#977126: linux: No armel kernel can be booted by grub-efi-arm:armel

[Ryutaroh Matsumoto]

> The rpi flavour doesn't have those constraints, though.  What would be
> the benefit of booting it in UEFI mode?

Thank you for paying your attention!
I considered extending autopkgtest-virt-qemu to armel (and other archs) 
testbeds at
https://salsa.debian.org/ci-team/autopkgtest/-/merge_requests/100#note_205984

To boot a qemu disk image by qemu-system-*, a booting firmware seems
indispensable, as the autopkgtest maintainer does not like giving 
-kernel=something
qemu option as
https://salsa.debian.org/ci-team/autopkgtest/-/merge_requests/97#note_205357

A booting firmware for an armel Debian disk image seems only
the qemu-efi-arm Debian package (is there anything else??).
So I resorted to the UEFI booting.
Currently I proposes to use linux-image-armmp-lpae for armel testbed.

Best regards, Ryutaroh

Bug#977126: linux: No armel kernel can be booted by grub-efi-arm:armel

[Ryutaroh Matsumoto]

Source: linux
Version: 5.9.11-1
Severity: important
X-Debbugs-Cc: pkg-grub-de...@alioth-lists.debian.net

Dear Maintainer,

grub-efi-arm:armel package remains almost unusable for very long time.
To boot a kernel in UEFI mode, it must be compiled with CONFIG_EFI.
But no Debian armel kernel (specifically linux-image-marvell or
linux-image-rpi) is built with CONFIG_EFI.
This leaves armel grub-efi-arm package almost useless.

For example, trying to boot linux-image-marvell by grub-efi-arm:armel
shows the following message:

Welcome to GRUB!

error: no suitable video mode found.
  Booting `Debian GNU/Linux'

Loading Linux 5.9.0-4-marvell ...
error: plain image kernel not supported - rebuild with CONFIG_(U)EFI_STUB
enabled.
Loading initial ramdisk ...
error: you need to load the kernel first.

On the other hand, grub-efi-arm:armel can boot linux-image-armmp:armhf.

This feature/bug leaves grub-efi-arm:armel almost useless,
so I chose "important" priority.

Best regards, Ryutaroh Matsumoto


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: arm64 (aarch64)

Kernel: Linux 5.9.0-4-arm64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#975053: linux-image-5.9.0-2-arm64: qemu's qxl-vga gives Oops Unable to handle kernel paging request

[Ryutaroh Matsumoto]

Package: src:linux
Version: 5.9.6-1
Severity: normal

Dear Maintainer,

I am running Debian Bullseye on qemu-system-aarch64
(host is Raspberry Pi 4B).

When I give -device qxl-vga to qemu-system-aarch64,
guest Linux gives "Unable to handle kernel paging request".
Full dmesg log is given below.

Other display devices of qemu does not give such an error.
qemu-system-aarch64 is started as below:

qemu-system-aarch64 -smp 2 -m 4096 -enable-kvm \
 -device qxl-vga -display vnc=${VNC_LISTEN_ADDR}:1 \
 -device virtio-balloon -device virtio-keyboard -device virtio-mouse \
 -machine 
virt,iommu=smmuv3,acpi=on,gic-version=host,virtualization=off,mem-merge=on \
 -cpu host -net nic,model=virtio -net user,hostfwd=tcp:127.0.0.1:10022-:22 \
 -object rng-random,filename=/dev/urandom,id=rng0 \
 -device virtio-rng-pci,rng=rng0,id=rng-device0 \
 -drive 
if=virtio,file=${IMGFILE},index=0,format=raw,discard=unmap,detect-zeroes=unmap,media=disk
 \
 -drive if=pflash,format=raw,unit=0,file=AAVMF_CODE.fd,readonly=on \
 -drive if=pflash,format=raw,unit=1,file=AAVMF_VARS.fd

qemu-system-aarch64's version is 1:5.1-dfsg-4+b1


Best regards, Ryutaroh Matsumoto

-- Package-specific info:
** Version:
Linux version 5.9.0-2-arm64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 
10.2.0-16) 10.2.0, GNU ld (GNU Binutils for Debian) 2.35.1) #1 SMP Debian 
5.9.6-1 (2020-11-08)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.9.0-2-arm64 
root=UUID=5104f6d3-1a91-4381-a030-080d2b497cb8 ro 
systemd.unified_cgroup_hierarchy=1

** Tainted: D (128)
 * kernel died recently, i.e. there was an OOPS or BUG

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

[0.00] Booting Linux on physical CPU 0x00 [0x410fd083]
[0.00] Linux version 5.9.0-2-arm64 (debian-kernel@lists.debian.org) 
(gcc-10 (Debian 10.2.0-16) 10.2.0, GNU ld (GNU Binutils for Debian) 2.35.1) #1 
SMP Debian 5.9.6-1 (2020-11-08)
[0.00] efi: EFI v2.70 by EDK II
[0.00] efi: SMBIOS 3.0=0x13bef MEMATTR=0x1391ef018 ACPI 
2.0=0x13845 RNG=0x13bffca98 MEMRESERVE=0x13843fe18 
[0.00] efi: seeding entropy pool
[0.00] secureboot: Secure boot disabled
[0.00] cma: Reserved 64 MiB at 0xfc00
[0.00] ACPI: Early table checksum verification disabled
[0.00] ACPI: RSDP 0x00013845 24 (v02 BOCHS )
[0.00] ACPI: XSDT 0x00013844 54 (v01 BOCHS  BXPCFACP 
0001  0113)
[0.00] ACPI: FACP 0x00013840 00010C (v05 BOCHS  BXPCFACP 
0001 BXPC 0001)
[0.00] ACPI: DSDT 0x00013841 001471 (v02 BOCHS  BXPCDSDT 
0001 BXPC 0001)
[0.00] ACPI: APIC 0x0001383F F4 (v03 BOCHS  BXPCAPIC 
0001 BXPC 0001)
[0.00] ACPI: GTDT 0x0001383E 60 (v02 BOCHS  BXPCGTDT 
0001 BXPC 0001)
[0.00] ACPI: MCFG 0x0001383D 3C (v01 BOCHS  BXPCMCFG 
0001 BXPC 0001)
[0.00] ACPI: SPCR 0x0001383C 50 (v02 BOCHS  BXPCSPCR 
0001 BXPC 0001)
[0.00] ACPI: IORT 0x0001383B CC (v00 BOCHS  BXPCIORT 
0001 BXPC 0001)
[0.00] ACPI: SPCR: console: pl011,mmio,0x900,9600
[0.00] ACPI: NUMA: Failed to initialise from firmware
[0.00] NUMA: Faking a node at [mem 
0x4000-0x00013fff]
[0.00] NUMA: NODE_DATA [mem 0x13f7f8100-0x13f7f9fff]
[0.00] Zone ranges:
[0.00]   DMA  [mem 0x4000-0x7fff]
[0.00]   DMA32[mem 0x8000-0x]
[0.00]   Normal   [mem 0x0001-0x00013fff]
[0.00] Movable zone start for each node
[0.00] Early memory node ranges
[0.00]   node   0: [mem 0x4000-0x00013845]
[0.00]   node   0: [mem 0x00013846-0x00013874]
[0.00]   node   0: [mem 0x00013875-0x00013bc1]
[0.00]   node   0: [mem 0x00013bc2-0x00013bff]
[0.00]   node   0: [mem 0x00013c00-0x00013fff]
[0.00] Zeroed struct page in unavailable ranges: 896 pages
[0.00] Initmem setup node 0 [mem 0x4000-0x00013fff]
[0.00] On node 0 totalpages: 1048576
[0.00]   DMA zone: 4096 pages used for memmap
[0.00]   DMA zone: 0 pages reserved
[0.00]   DMA zone: 262144 pages, LIFO batch:63
[0.00]   DMA32 zone: 8192 pages used for memmap
[0.00]   DMA32 zone: 524288 pages, LIFO batch:63
[0.00]   Normal zone: 4096 pages used for memmap
[0.00]   Normal zone: 262144 pages, LIFO batch:63
[0.00] psci: probing for conduit method from ACPI.
[0.00] psci: PSCIv1.0 detected in firmware.
[0.00] psci: Using standard PSCI v0.2 function IDs
[0.00] psci: Trusted OS migration not required
[0.00] psci: SMC Calling Convention v1.1
[0.00] ACPI: SRAT not present
[  

Bug#974921: linux-image-5.9.0-2-arm64: Could you consider CONFIG_VDPA=m and CONFIG_VFIO_MDEV=m ?

[Ryutaroh Matsumoto]

Package: src:linux
Version: 5.9.6-1
Severity: wishlist

Dear Maintainer,

vDPA means virtio data path acceleration, and a faster alternative
to vhost-net. Its advantages over vhost-net is explained at
https://www.redhat.com/ja/blog/introduction-vdpa-kernel-framework

MDEV means mediator devices, and its use cases are explained at
https://www.redhat.com/en/blog/how-deep-does-vdpa-rabbit-hole-go
and can conveniently used with vDPA above.

Both of them are currently disabled at the Debian kernel package.
I would appreciate it if you could consider enabling them as modules.

Best regards, Ryutaroh Matsumoto


-- Package-specific info:
** Version:
Linux version 5.9.0-2-arm64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 
10.2.0-16) 10.2.0, GNU ld (GNU Binutils for Debian) 2.35.1) #1 SMP Debian 
5.9.6-1 (2020-11-08)

** Command line:
video=HDMI-A-1:3840x2160M@30,margin_left=48,margin_right=48,margin_top=48,margin_bottom=48
 dma.dmachans=0x71f5 bcm2709.boardrev=0xd03114 bcm2709.serial=0x488d2af3 
bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=42 
bcm2709.disk_led_active_low=0 smsc95xx.macaddr=DC:A6:32:BB:99:D9 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  console=tty0 
console=ttyS1,115200 root=/dev/mmcblk1p2 rw elevator=deadline fsck.repair=yes 
net.ifnames=0  rootwait

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

** Kernel log:
[   14.382071] platform regulatory.0: firmware: direct-loading firmware 
regulatory.db
[   14.397371] platform regulatory.0: firmware: direct-loading firmware 
regulatory.db.p7s
[   14.407069] alg: No test for fips(ansi_cprng) (fips_ansi_cprng)
[   14.467310] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio 
for chip BCM4345/6
[   14.482828] usbcore: registered new interface driver brcmfmac
[   14.608442] brcmfmac mmc0:0001:1: firmware: direct-loading firmware 
brcm/brcmfmac43455-sdio.bin
[   14.626753] brcmfmac mmc0:0001:1: firmware: direct-loading firmware 
brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt
[   14.757810] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio 
for chip BCM4345/6
[   14.772482] brcmfmac mmc0:0001:1: firmware: failed to load 
brcm/brcmfmac43455-sdio.clm_blob (-2)
[   14.787326] firmware_class: See https://wiki.debian.org/Firmware for 
information about missing firmware
[   14.813962] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available 
(err=-2), device may have limited channels available
[   14.840193] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Mar  1 
2015 07:29:38 version 7.45.18 (r538002) FWID 01-6a2c8ad4
[   14.882902] random: crng init done
[   14.891827] Bluetooth: Core ver 2.22
[   14.892590] random: 3 urandom warning(s) missed due to ratelimiting
[   14.902517] NET: Registered protocol family 31
[   14.925671] Bluetooth: HCI device and connection manager initialized
[   14.938656] Bluetooth: HCI socket layer initialized
[   14.952837] Bluetooth: L2CAP socket layer initialized
[   14.968934] Bluetooth: SCO socket layer initialized
[   15.004369] input: SEM USB Keyboard as 
/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb1/1-1/1-1.3/1-1.3:1.0/0003:1A2C:4324.0001/input/input0
[   15.047674] mc: Linux media interface: v0.10
[   15.086073] hid-generic 0003:1A2C:4324.0001: input,hidraw0: USB HID v1.10 
Keyboard [SEM USB Keyboard] on usb-:01:00.0-1.3/input0
[   15.086465] videodev: Linux video capture interface: v2.00
[   15.115306] input: SEM USB Keyboard Consumer Control as 
/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb1/1-1/1-1.3/1-1.3:1.1/0003:1A2C:4324.0002/input/input1
[   15.165175] snd_bcm2835: module is from the staging directory, the quality 
is unknown, you have been warned.
[   15.179901] Bluetooth: HCI UART driver ver 2.3
[   15.187463] Bluetooth: HCI UART protocol H4 registered
[   15.187665] Bluetooth: HCI UART protocol LL registered
[   15.195137] input: SEM USB Keyboard System Control as 
/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb1/1-1/1-1.3/1-1.3:1.1/0003:1A2C:4324.0002/input/input2
[   15.195289] hid-generic 0003:1A2C:4324.0002: input,hidraw1: USB HID v1.10 
Device [SEM USB Keyboard] on usb-:01:00.0-1.3/input1
[   15.196317] input: USB Optical Mouse as 
/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb1/1-1/1-1.4/1-1.4:1.0/0003:15CA:00C3.0003/input/input3
[   15.203971] Bluetooth: HCI UART protocol ATH3K registered
[   15.204259] Bluetooth: HCI UART protocol Three-wire (H5) registered
[   15.206621] bcm2835_audio bcm2835_audio: card created with 8 channels
[   15.224906] hid-generic 0003:15CA:00C3.0003: input,hidraw2: USB HID v1.10 
Mouse [USB Optical Mouse] on usb-:01:00.0-1.4/input0
[   15.226421] bcm2835_mmal_vchiq: module is from the staging directory, the 
quality is unknown, you have been warned.
[   15.242364] Bluetooth: HCI UART protocol Intel registered
[   15.321838] bcm2835_v4l2: module is from the staging directory, the quality

Bug#974157: linux-image-5.9.0-2-686-pae: prints incorrect highmem if memory >= 4GB

[Ryutaroh Matsumoto]

Package: src:linux
Followup-For: Bug #974157
Control: tags -1 + buster bullseye sid
Control: found -1 4.19.152-1
Control: found -1 4.19+105+deb10u7

Dear Maintainer,

This symptom is also ovserved with Buster's following packages:
linux-image-4.19.0-12-686-pae   4.19.152-1
linux-image-686-pae 4.19+105+deb10u7

Ryutaroh

-- System Information:
Debian Release: 10.6
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.19.0-12-686-pae (SMP w/6 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#974157: linux-image-5.9.0-2-686-pae: prints incorrect highmem if memory >= 4GB

[Ryutaroh Matsumoto]

Package: src:linux
Version: 5.9.6-1
Severity: minor

Dear Maintainer,

This symptom is observed in a qemu-system-i386 guest.
When 4GB or more memory is given by -m option to qemu,
the amounts of highmem are printed as


[0.021084] 5656MB HIGHMEM available.
[0.021085] 487MB LOWMEM available.
[0.260926] Memory: 3968828K/4158180K available (7846K kernel code, 770K 
rwdata, 2372K rodata, 868K init, 480K bss, 189352K reserved, 0K cma-reserved, 
3649456K highmem)

Two inconsistent amounts are printed as above.
I do not observe this when I give 2GB memory to qemu-system-i386.

There seems no actual inconvenience by this, though.

Best regards, Ryutaroh Matsumoto


-- Package-specific info:
** Version:
Linux version 5.9.0-2-686-pae (debian-kernel@lists.debian.org) (gcc-10 (Debian 
10.2.0-16) 10.2.0, GNU ld (GNU Binutils for Debian) 2.35.1) #1 SMP Debian 
5.9.6-1 (2020-11-08)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.9.0-2-686-pae 
root=UUID=70ea2c03-79ae-4c46-a442-0c9d26ebf9c7 ro console=ttyS0 vmalloc=512M 
systemd.unified_cgroup_hierarchy=1

** Not tainted

** Kernel log:

[0.00] Linux version 5.9.0-2-686-pae (debian-kernel@lists.debian.org) 
(gcc-10 (Debian 10.2.0-16) 10.2.0, GNU ld (GNU Binutils for Debian) 2.35.1) #1 
SMP Debian 5.9.6-1 (2020-11-08)
[0.00] x86/fpu: x87 FPU will use FXSAVE
[0.00] BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0002] usable
[0.00] BIOS-e820: [mem 0x0003-0x0004] reserved
[0.00] BIOS-e820: [mem 0x0005-0x0009dfff] usable
[0.00] BIOS-e820: [mem 0x0009e000-0x0009] reserved
[0.00] BIOS-e820: [mem 0x0010-0x00806fff] usable
[0.00] BIOS-e820: [mem 0x00807000-0x00807fff] ACPI NVS
[0.00] BIOS-e820: [mem 0x00808000-0x0080] usable
[0.00] BIOS-e820: [mem 0x0081-0x0170] ACPI NVS
[0.00] BIOS-e820: [mem 0x0171-0x7af6] usable
[0.00] BIOS-e820: [mem 0x7af73000-0x7eba2fff] usable
[0.00] BIOS-e820: [mem 0x7eba3000-0x7ee22fff] reserved
[0.00] BIOS-e820: [mem 0x7ee23000-0x7ee32fff] ACPI data
[0.00] BIOS-e820: [mem 0x7ee33000-0x7eeb2fff] ACPI NVS
[0.00] BIOS-e820: [mem 0x7eeb3000-0x7ef4] usable
[0.00] BIOS-e820: [mem 0x7ef5-0x7eff] ACPI NVS
[0.00] BIOS-e820: [mem 0x7f00-0x7fff] reserved
[0.00] BIOS-e820: [mem 0xb000-0xbfff] reserved
[0.00] BIOS-e820: [mem 0x0001-0x00017fff] usable
[0.00] Notice: NX (Execute Disable) protection missing in CPU!
[0.00] e820: update [mem 0x7d438010-0x7d441a3b] usable ==> usable
[0.00] e820: update [mem 0x7d438010-0x7d441a3b] usable ==> usable
[0.00] e820: update [mem 0x7d3fb010-0x7d437c3b] usable ==> usable
[0.00] e820: update [mem 0x7d3fb010-0x7d437c3b] usable ==> usable
[0.00] extended physical RAM map:
[0.00] reserve setup_data: [mem 0x-0x0002] 
usable
[0.00] reserve setup_data: [mem 0x0003-0x0004] 
reserved
[0.00] reserve setup_data: [mem 0x0005-0x0009dfff] 
usable
[0.00] reserve setup_data: [mem 0x0009e000-0x0009] 
reserved
[0.00] reserve setup_data: [mem 0x0010-0x00806fff] 
usable
[0.00] reserve setup_data: [mem 0x00807000-0x00807fff] 
ACPI NVS
[0.00] reserve setup_data: [mem 0x00808000-0x0080] 
usable
[0.00] reserve setup_data: [mem 0x0081-0x0170] 
ACPI NVS
[0.00] reserve setup_data: [mem 0x0171-0x7af6] 
usable
[0.00] reserve setup_data: [mem 0x7af73000-0x7d3fb00f] 
usable
[0.00] reserve setup_data: [mem 0x7d3fb010-0x7d437c3b] 
usable
[0.00] reserve setup_data: [mem 0x7d437c3c-0x7d43800f] 
usable
[0.00] reserve setup_data: [mem 0x7d438010-0x7d441a3b] 
usable
[0.00] reserve setup_data: [mem 0x7d441a3c-0x7eba2fff] 
usable
[0.00] reserve setup_data: [mem 0x7eba3000-0x7ee22fff] 
reserved
[0.00] reserve setup_data: [mem 0x7ee23000-0x7ee32fff] 
ACPI data
[0.00] reserve setup_data: [mem 0x7ee33000-0x7eeb2fff] 
ACPI NVS
[0.00] reserve setup_data: [mem 0x7eeb3000-0x7ef4] 
usable
[0.00] reserve setup_data: [mem 0x7ef5-0x7eff] 
ACPI NVS
[0.00] reserve setup_data: [mem 0x7f00-0x7fff] 
reserved
[0.00] reserve setu

Bug#920740: Should crda be shipped in buster?

[Ryutaroh Matsumoto]

When ifconfig and wpasupplicant are used for configuring a
wireless interface, crda seems the only way to choose a regulatory domain.

One cannot do "wpa-country JP" in /etc/network/interface

Best regards, Ryutaroh

Bug#972311: crda: Could dpkg-reconfigure crda set a regulatory domain?

[Ryutaroh Matsumoto]

Package: crda
Version: 4.14+git20191112.9856751-1
Severity: wishlist

Dear Maintainer,

It would be more user-friendly if user's regulatory domain can be set
by dpke-reconfigure crda.

Making suitable debian/config and debian/templates should enable the above.

Best regards, Ryutaroh Matsumoto

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: arm64 (aarch64)

Kernel: Linux 5.8.0-2-arm64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages crda depends on:
ii  iw5.8-1
ii  libc6 2.31-3
ii  libnl-3-200   3.4.0-1+b1
ii  libnl-genl-3-200  3.4.0-1+b1
ii  libssl1.1 1.1.1g-1
ii  wireless-regdb2020.04.29-2

crda recommends no packages.

crda suggests no packages.

-- no debconf information

Bug#971059: linux-image-5.8.0-2-armmp-lpae: PCI invisible on Raspberry Pi 4B 8GB

[Ryutaroh Matsumoto]

Package: src:linux
Version: 5.8.10-1
Severity: normal

Dear Maintainer,

I am reporting a similar symptom to
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968109
for a different kernel package (armmp-lpae).

PCI peripherals of Raspberry Pi 4B (8GB model) are completely
invisible. lspci shows nothing.
As a result, USB is unusable.

Best regards, Ryutaroh Matsumoto

-- Package-specific info:
** Version:
Linux version 5.8.0-2-armmp-lpae (debian-kernel@lists.debian.org) (gcc-10 
(Debian 10.2.0-8) 10.2.0, GNU ld (GNU Binutils for Debian) 2.35) #1 SMP Debian 
5.8.10-1 (2020-09-19)

** Command line:
video=HDMI-A-1:3840x2160M@30,margin_left=48,margin_right=48,margin_top=48,margin_bottom=48
 dma.dmachans=0x71f5 bcm2709.boardrev=0xd03114 bcm2709.serial=0x488d2af3 
bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=42 
bcm2709.disk_led_active_low=0 smsc95xx.macaddr=DC:A6:32:BB:99:D9 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  console=tty0 
console=ttyS1,115200 root=/dev/mmcblk1p2 rw elevator=deadline fsck.repair=yes 
net.ifnames=0  rootwait

** Tainted: CE (9216)
 * staging driver was loaded
 * unsigned module was loaded

** Kernel log:

[0.00] Booting Linux on physical CPU 0x0
[0.00] Linux version 5.8.0-2-armmp-lpae 
(debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.0-8) 10.2.0, GNU ld (GNU 
Binutils for Debian) 2.35) #1 SMP Debian 5.8.10-1 (2020-09-19)
[0.00] CPU: ARMv7 Processor [410fd083] revision 3 (ARMv7), cr=30c5383d
[0.00] CPU: div instructions available: patching division code
[0.00] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
[0.00] OF: fdt: Machine model: Raspberry Pi 4 Model B Rev 1.4
[0.00] Memory policy: Data cache writealloc
[0.00] efi: UEFI not found.
[0.00] Reserved memory: created CMA memory pool at 0x3700, 
size 64 MiB
[0.00] OF: reserved mem: initialized node linux,cma, compatible id 
shared-dma-pool
[0.00] Zone ranges:
[0.00]   DMA  [mem 0x-0x2fff]
[0.00]   Normal   empty
[0.00]   HighMem  [mem 0x3000-0x0001]
[0.00] Movable zone start for each node
[0.00] Early memory node ranges
[0.00]   node   0: [mem 0x-0x3b3f]
[0.00]   node   0: [mem 0x4000-0xfbff]
[0.00]   node   0: [mem 0x0001-0x0001]
[0.00] Initmem setup node 0 [mem 0x-0x0001]
[0.00] On node 0 totalpages: 2061312
[0.00]   DMA zone: 2304 pages used for memmap
[0.00]   DMA zone: 0 pages reserved
[0.00]   DMA zone: 196608 pages, LIFO batch:63
[0.00]   HighMem zone: 1864704 pages, LIFO batch:63
[0.00] percpu: Embedded 21 pages/cpu s54220 r8192 d23604 u86016
[0.00] pcpu-alloc: s54220 r8192 d23604 u86016 alloc=21*4096
[0.00] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[0.00] Built 1 zonelists, mobility grouping on.  Total pages: 2059008
[0.00] Kernel command line: 
video=HDMI-A-1:3840x2160M@30,margin_left=48,margin_right=48,margin_top=48,margin_bottom=48
 dma.dmachans=0x71f5 bcm2709.boardrev=0xd03114 bcm2709.serial=0x488d2af3 
bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=42 
bcm2709.disk_led_active_low=0 smsc95xx.macaddr=DC:A6:32:BB:99:D9 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  console=tty0 
console=ttyS1,115200 root=/dev/mmcblk1p2 rw elevator=deadline fsck.repair=yes 
net.ifnames=0  rootwait
[0.00] Kernel parameter elevator= does not have any effect anymore.
   Please use sysfs to set IO scheduler for individual devices.
[0.00] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes, 
linear)
[0.00] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes, 
linear)
[0.00] mem auto-init: stack:off, heap alloc:on, heap free:off
[0.00] software IO TLB: mapped [mem 0x23985000-0x27985000] (64MB)
[0.00] Memory: 7974884K/8245248K available (10240K kernel code, 1263K 
rwdata, 3228K rodata, 2048K init, 336K bss, 204828K reserved, 65536K 
cma-reserved, 7393280K highmem)
[0.00] random: get_random_u32 called from 
__kmem_cache_create+0x48/0x570 with crng_init=0
[0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[0.00] ftrace: allocating 35987 entries in 71 pages
[0.00] ftrace: allocated 71 pages with 4 groups
[0.00] rcu: Hierarchical RCU implementation.
[0.00] rcu: RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.
[0.00]  Rude variant of Tasks RCU enabled.
[0.00] rcu: RCU calculated value of scheduler-enlistment delay is 25 
jiffies.
[0.00] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[0.00] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[0.00] GIC: Using split EOI/Deactivate mode
[0.09

Bug#970634: linux-image-5.8.0-1-arm64: Kernel image misaligned at boot on raspi 4B

[Ryutaroh Matsumoto]

Package: src:linux
Version: 5.8.7-1
Severity: minor

Dear Maintainer,

With a recent SD card image from raspi.debian.net,
running on Raspberry Pi 4B 8GB (board revision 1.4),
I see

Sep 14 15:04:42 rpi4-20200909 kernel: [Firmware Bug]: Kernel image misaligned 
at boot, please fix your bootloader!

I have no functional problem, though.

Best regards, Ryutaroh Matsumoto


-- Package-specific info:
** Version:
Linux version 5.8.0-1-arm64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 
10.2.0-6) 10.2.0, GNU ld (GNU Binutils for Debian) 2.35) #1 SMP Debian 5.8.7-1 
(2020-09-05)

** Command line:
video=HDMI-A-1:3840x2160M@30,margin_left=48,margin_right=48,margin_top=48,margin_bottom=48
 dma.dmachans=0x71f5 bcm2709.boardrev=0xd03114 bcm2709.serial=0x488d2af3 
bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=42 
bcm2709.disk_led_active_low=0 smsc95xx.macaddr=DC:A6:32:BB:99:D9 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  console=tty0 
console=ttyS1,115200 root=/dev/mmcblk1p2 rw elevator=deadline fsck.repair=yes 
net.ifnames=0  rootwait

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

** Kernel log:
[   35.811564] systemd-xdg-autostart-generator[1975]: Not generating service 
for XDG autostart 
app-cinnamon\x2dsettings\x2ddaemon\x2dxsettings-autostart.service, startup 
phases are not supported.
[   35.831413] systemd-xdg-autostart-generator[1975]: 
kde-systemd-start-condition not found: No such file or directory
[   35.844863] systemd-xdg-autostart-generator[1975]: Not generating service 
for XDG autostart 
app-cinnamon\x2dsettings\x2ddaemon\x2dscreensaver\x2dproxy-autostart.service, 
startup phases are not supported.
[   35.865776] systemd-xdg-autostart-generator[1975]: Not generating service 
for XDG autostart 
app-cinnamon\x2dsettings\x2ddaemon\x2dcolor-autostart.service, startup phases 
are not supported.
[   35.885280] systemd-xdg-autostart-generator[1975]: Not generating service 
for XDG autostart 
app-org.gnome.SettingsDaemon.PrintNotifications-autostart.service, startup 
phases are not supported.
[   35.910138] systemd-xdg-autostart-generator[1975]: 
gnome-systemd-autostart-condition not found: No such file or directory
[   35.923850] systemd-xdg-autostart-generator[1975]: Not generating service 
for XDG autostart app-org.gnome.SettingsDaemon.Wwan-autostart.service, startup 
phases are not supported.
[   35.942947] systemd-xdg-autostart-generator[1975]: 
gnome-systemd-autostart-condition not found: No such file or directory
[   35.957811] systemd-xdg-autostart-generator[1975]: Not generating service 
for XDG autostart 
app-org.gnome.SettingsDaemon.ScreensaverProxy-autostart.service, startup phases 
are not supported.
[   35.977740] systemd-xdg-autostart-generator[1975]: Not generating service 
for XDG autostart app-gnome\x2dkeyring\x2dsecrets-autostart.service, startup 
phases are not supported.
[   35.996632] systemd-xdg-autostart-generator[1975]: 
kde-systemd-start-condition not found: No such file or directory
[   36.010080] systemd-xdg-autostart-generator[1975]: Not generating service 
for XDG autostart 
app-xfce4\x2dclipman\x2dplugin\x2dautostart-autostart.service, it is hidden.
[   36.032819] systemd-xdg-autostart-generator[1975]: Not generating service 
for XDG autostart 
app-cinnamon\x2dsettings\x2ddaemon\x2dxrandr-autostart.service, startup phases 
are not supported.
[   36.052914] systemd-xdg-autostart-generator[1975]: Not generating service 
for XDG autostart app-pulseaudio-autostart.service, startup phases are not 
supported.
[   36.070574] systemd-xdg-autostart-generator[1975]: Not generating service 
for XDG autostart 
app-cinnamon\x2dsettings\x2ddaemon\x2dmouse-autostart.service, startup phases 
are not supported.
[   36.090536] systemd-xdg-autostart-generator[1975]: Not generating service 
for XDG autostart app-at\x2dspi\x2ddbus\x2dbus-autostart.service, startup 
phases are not supported.
[   36.109234] systemd-xdg-autostart-generator[1975]: Not generating service 
for XDG autostart app-gnome\x2dkeyring\x2dssh-autostart.service, startup phases 
are not supported.
[   36.127828] systemd-xdg-autostart-generator[1975]: Not generating service 
for XDG autostart app-org.gnome.SettingsDaemon.Color-autostart.service, startup 
phases are not supported.
[   36.151803] systemd-xdg-autostart-generator[1975]: Not generating service 
for XDG autostart app-org.gnome.SettingsDaemon.Keyboard-autostart.service, 
startup phases are not supported.
[   36.171779] systemd-xdg-autostart-generator[1975]: Not generating service 
for XDG autostart 
app-cinnamon\x2dsettings\x2ddaemon\x2da11y\x2dkeyboard-autostart.service, 
startup phases are not supported.
[   36.193418] systemd-xdg-autostart-generator[1975]: Not generating service 
for XDG autostart app-org.gnome.SettingsDaemon.Power-autostart.service, startup 
phases are not supported.
[   36.212906] systemd-xdg-autostart-generator[1975]: Not generating service 
for XDG autostart app-org.gnome.SettingsDaemon.Sound-autostart.service, startup 
phases

Bug#968109: Resolved: USB unusable on Raspberry Pi 4B 8GB

[Ryutaroh Matsumoto]

Package: src:linux
Followup-For: Bug #968109
Control: fixed -1 5.8.7-1

Dear Maintainer,

I verified that Debian kernel package version 5.8.7-1 lets
USB of Raspberry Pi 4B 8GB work! Thanks.

Best regards, Ryutaroh

-- Package-specific info:
** Version:
Linux version 5.8.0-1-arm64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 
10.2.0-6) 10.2.0, GNU ld (GNU Binutils for Debian) 2.35) #1 SMP Debian 5.8.7-1 
(2020-09-05)

** Command line:
video=HDMI-A-1:3840x2160M@30,margin_left=48,margin_right=48,margin_top=48,margin_bottom=48
 dma.dmachans=0x71f5 bcm2709.boardrev=0xd03114 bcm2709.serial=0x488d2af3 
bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=42 
bcm2709.disk_led_active_low=0 smsc95xx.macaddr=DC:A6:32:BB:99:D9 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  console=tty0 
console=ttyS1,115200 root=/dev/mmcblk1p2 rw elevator=deadline fsck.repair=yes 
net.ifnames=0  rootwait

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

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

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

** Loaded modules:
xt_CHECKSUM
nft_chain_nat
xt_MASQUERADE
nf_nat
nf_conntrack
nf_defrag_ipv6
nf_defrag_ipv4
nft_counter
cmac
algif_hash
xt_tcpudp
nft_compat
algif_skcipher
af_alg
bridge
bnep
stp
llc
nf_tables
nfnetlink
nls_ascii
nls_cp437
vfat
fat
hci_uart
btqca
btrtl
btsdio
joydev
evdev
btbcm
brcmfmac
btintel
brcmutil
bluetooth
bcm2835_v4l2(C)
cfg80211
videobuf2_vmalloc
videobuf2_memops
videobuf2_v4l2
hid_generic
jitterentropy_rng
snd_bcm2835(C)
videobuf2_common
drbg
snd_pcm
videodev
ansi_cprng
snd_timer
ecdh_generic
mc
ecc
snd
rfkill
soundcore
cpufreq_dt
iproc_rng200
raspberrypi_cpufreq
vchiq(C)
rng_core
bcm2711_thermal
pwm_bcm2835
bcm2835_wdt
leds_gpio
drm
ip_tables
x_tables
autofs4
usbhid
hid
ext4
crc16
mbcache
jbd2
vhost_net
tun
vhost
vhost_iotlb
tap
btrfs
blake2b_generic
xor
xor_neon
zstd_decompress
zstd_compress
raid6_pq
libcrc32c
crc32c_generic
bfq
broadcom
bcm_phy_lib
xhci_pci
xhci_hcd
dwc2
udc_core
mdio_bcm_unimac
genet
usbcore
of_mdio
sdhci_iproc
i2c_bcm2835
sdhci_pltfm
fixed_phy
gpio_regulator
libphy
fixed
usb_common
sdhci
phy_generic

** Network interface configuration:
*** /etc/network/interfaces:
source-directory /etc/network/interfaces.d

*** /etc/network/interfaces.d/eth0:
auto eth0

iface eth0 inet dhcp

*** /etc/network/interfaces.d/wlan0:
auto wlan0

iface wlan0 inet dhcp

** Network status:
*** IP interfaces and addresses:
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host 
   valid_lft forever preferred_lft forever
2: eth0:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
link/ether dc:a6:32:bb:99:d9 brd ff:ff:ff:ff:ff:ff
3: wlan0:  mtu 1500 qdisc pfifo_fast state UP 
group default qlen 1000
link/ether dc:a6:32:bb:99:da brd ff:ff:ff:ff:ff:ff
inet 192.168.1.9/24 brd 192.168.1.255 scope global wlan0
   valid_lft forever preferred_lft forever
inet6 2400:4050:2ba1:ac00:dea6:32ff:febb:99da/64 scope global dynamic 
mngtmpaddr noprefixroute 
   valid_lft 13873sec preferred_lft 12073sec
inet6 fe80::dea6:32ff:febb:99da/64 scope link 
   valid_lft forever preferred_lft forever
4: lxcbr0:  mtu 1500 qdisc noqueue state 
DOWN group default qlen 1000
link/ether 00:16:3e:00:00:00 brd ff:ff:ff:ff:ff:ff
inet 10.0.3.1/24 brd 10.0.3.255 scope global lxcbr0
   valid_lft forever preferred_lft forever

*** Device statistics:
Inter-|   Receive|  Transmit
 face |bytespackets errs drop fifo frame compressed multicast|bytes
packets errs drop fifo colls carrier compressed
lo: 200   4000 0  0 0  200  
 4000 0   0  0
  eth0:   0   0000 0  0 00  
 0000 0   0  0
 wlan0:  1030781064000 0  0 5   104793 
792000 0   0  0
lxcbr0:   0   0000 0  0 00  
 0000 0   0  0


** PCI devices:
00:00.0 PCI bridge [0604]: Broadcom Inc. and subsidiaries Device [14e4:2711] 
(rev 10) (prog-if 00 [Normal decode])
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [48] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1-,D2-,D3hot+,D3cold-)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [ac] Express (v2) Root Port 

Bug#968188: linux-image-5.7.0-2-arm64: 4K display resolution is not recognized with Raspberry Pi 4B

[Ryutaroh Matsumoto]

Package: src:linux
Version: 5.7.10-1
Severity: important


Dear Maintainer,

My display has 3840x2160 resulution.
The kernel from Raspberry Pi Foundation can use 3840x2160.

But the debian kernel can only use 1920×1280.

By the lack of DRM reported at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968181
I can only use fbdev_backend in weston/wayland and
xserver-xorg-video-fbdev.

They only recognize 1920×1280. Relevant Debian kernel log is

[0.920977] simple-framebuffer 3e267000.framebuffer: framebuffer at 
0x3e267000, 0x96 bytes, mapped to 0x(ptrval)
[0.921003] simple-framebuffer 3e267000.framebuffer: format=a8r8g8b8, 
mode=1920x1280x32, linelength=7680
[0.946638] Console: switching to colour frame buffer device 240x80
[0.971786] simple-framebuffer 3e267000.framebuffer: fb0: simplefb 
registered!

Best regards, Ryutaroh Matsumoto

-- Package-specific info:
** Version:
Linux version 5.7.0-2-arm64 (debian-kernel@lists.debian.org) (gcc version 9.3.0 
(Debian 9.3.0-15), GNU ld (GNU Binutils for Debian) 2.35) #1 SMP Debian 
5.7.10-1 (2020-07-26)

** Command line:
video=HDMI-A-1:3840x2160M@30,margin_left=48,margin_right=48,margin_top=48,margin_bottom=48
 dma.dmachans=0x71f5 bcm2709.boardrev=0xd03114 bcm2709.serial=0x488d2af3 
bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=42 
bcm2709.disk_led_active_low=0 smsc95xx.macaddr=DC:A6:32:BB:99:D9 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  console=tty0 
console=ttyS1,115200 root=/dev/mmcblk1p2 rw elevator=bfq fsck.repair=yes 
net.ifnames=0  rootwait systemd.unified_cgroup_hierarchy=1

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

** Kernel log:
Unable to read kernel log; any relevant messages should be attached
dmesg output is below:

[0.00] Booting Linux on physical CPU 0x00 [0x410fd083]
[0.00] Linux version 5.7.0-2-arm64 (debian-kernel@lists.debian.org) 
(gcc version 9.3.0 (Debian 9.3.0-15), GNU ld (GNU Binutils for Debian) 2.35) #1 
SMP Debian 5.7.10-1 (2020-07-26)
[0.00] Machine model: Raspberry Pi 4 Model B Rev 1.4
[0.00] efi: UEFI not found.
[0.00] Reserved memory: created CMA memory pool at 0x2900, 
size 64 MiB
[0.00] OF: reserved mem: initialized node linux,cma, compatible id 
shared-dma-pool
[0.00] NUMA: No NUMA configuration found
[0.00] NUMA: Faking a node at [mem 
0x-0x0001]
[0.00] NUMA: NODE_DATA [mem 0x1ff0730c0-0x1ff074fff]
[0.00] Zone ranges:
[0.00]   DMA  [mem 0x-0x3fff]
[0.00]   DMA32[mem 0x4000-0x]
[0.00]   Normal   [mem 0x0001-0x0001]
[0.00] Movable zone start for each node
[0.00] Early memory node ranges
[0.00]   node   0: [mem 0x-0x2fff]
[0.00]   node   0: [mem 0x4000-0xfbff]
[0.00]   node   0: [mem 0x0001-0x0001]
[0.00] Initmem setup node 0 [mem 0x-0x0001]
[0.00] On node 0 totalpages: 2015232
[0.00]   DMA zone: 3072 pages used for memmap
[0.00]   DMA zone: 0 pages reserved
[0.00]   DMA zone: 196608 pages, LIFO batch:63
[0.00]   DMA32 zone: 12288 pages used for memmap
[0.00]   DMA32 zone: 770048 pages, LIFO batch:63
[0.00]   Normal zone: 16384 pages used for memmap
[0.00]   Normal zone: 1048576 pages, LIFO batch:63
[0.00] percpu: Embedded 32 pages/cpu s93720 r8192 d29160 u131072
[0.00] pcpu-alloc: s93720 r8192 d29160 u131072 alloc=32*4096
[0.00] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[0.00] Detected PIPT I-cache on CPU0
[0.00] CPU features: detected: EL2 vector hardening
[0.00] CPU features: kernel page table isolation forced ON by KASLR
[0.00] CPU features: detected: Kernel page table isolation (KPTI)
[0.00] ARM_SMCCC_ARCH_WORKAROUND_1 missing from firmware
[0.00] CPU features: detected: ARM erratum 1319367
[0.00] Built 1 zonelists, mobility grouping on.  Total pages: 1983488
[0.00] Policy zone: Normal
[0.00] Kernel command line: 
video=HDMI-A-1:3840x2160M@30,margin_left=48,margin_right=48,margin_top=48,margin_bottom=48
 dma.dmachans=0x71f5 bcm2709.boardrev=0xd03114 bcm2709.serial=0x488d2af3 
bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=42 
bcm2709.disk_led_active_low=0 smsc95xx.macaddr=DC:A6:32:BB:99:D9 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  console=tty0 
console=ttyS1,115200 root=/dev/mmcblk1p2 rw elevator=bfq fsck.repair=yes 
net.ifnames=0  rootwait systemd.unified_cgroup_hierarchy=1
[0.00] Kernel parameter elevator= does not have any effect anymore.
   Please use sysfs to set IO scheduler for individual devices.
[0.00] Dentry cache hash table entries: 1048576 (order: 11, 8388608 
bytes, linear

Bug#968181: linux-image-5.7.0-2-arm64: DRM unavailable on Rapsberry Pi 4B

[Ryutaroh Matsumoto]

Package: src:linux
Version: 5.7.10-1
Severity: normal

Dear Maintainer,

DRM is unavailable on Raspberry Pi 4B (board revision 1.4).
Lack of DRM prevents drm_backend in weston/wayland.
X server does not start without installation of xserver-xorg-video-fbdev.

In contrast to the Debian kernel, the kernel from Raspbian Foundation
allows drm_backend in weston, and it does not need xserver-xorg-video-fbdev.

Best regards, Ryutaroh Matsumoto


-- Package-specific info:
** Version:
Linux version 5.7.0-2-arm64 (debian-kernel@lists.debian.org) (gcc version 9.3.0 
(Debian 9.3.0-15), GNU ld (GNU Binutils for Debian) 2.35) #1 SMP Debian 
5.7.10-1 (2020-07-26)

** Command line:
video=HDMI-A-1:3840x2160M@30,margin_left=48,margin_right=48,margin_top=48,margin_bottom=48
 dma.dmachans=0x71f5 bcm2709.boardrev=0xd03114 bcm2709.serial=0x488d2af3 
bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=42 
bcm2709.disk_led_active_low=0 smsc95xx.macaddr=DC:A6:32:BB:99:D9 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  console=tty0 
console=ttyS1,115200 root=/dev/mmcblk1p2 rw elevator=bfq fsck.repair=yes 
net.ifnames=0  rootwait systemd.unified_cgroup_hierarchy=1

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

** Kernel log:
Unable to read kernel log; any relevant messages should be attached
dmesg out put is included here:


[0.00] Booting Linux on physical CPU 0x00 [0x410fd083]
[0.00] Linux version 5.7.0-2-arm64 (debian-kernel@lists.debian.org) 
(gcc version 9.3.0 (Debian 9.3.0-15), GNU ld (GNU Binutils for Debian) 2.35) #1 
SMP Debian 5.7.10-1 (2020-07-26)
[0.00] Machine model: Raspberry Pi 4 Model B Rev 1.4
[0.00] efi: UEFI not found.
[0.00] Reserved memory: created CMA memory pool at 0x2900, 
size 64 MiB
[0.00] OF: reserved mem: initialized node linux,cma, compatible id 
shared-dma-pool
[0.00] NUMA: No NUMA configuration found
[0.00] NUMA: Faking a node at [mem 
0x-0x0001]
[0.00] NUMA: NODE_DATA [mem 0x1ff0730c0-0x1ff074fff]
[0.00] Zone ranges:
[0.00]   DMA  [mem 0x-0x3fff]
[0.00]   DMA32[mem 0x4000-0x]
[0.00]   Normal   [mem 0x0001-0x0001]
[0.00] Movable zone start for each node
[0.00] Early memory node ranges
[0.00]   node   0: [mem 0x-0x2fff]
[0.00]   node   0: [mem 0x4000-0xfbff]
[0.00]   node   0: [mem 0x0001-0x0001]
[0.00] Initmem setup node 0 [mem 0x-0x0001]
[0.00] On node 0 totalpages: 2015232
[0.00]   DMA zone: 3072 pages used for memmap
[0.00]   DMA zone: 0 pages reserved
[0.00]   DMA zone: 196608 pages, LIFO batch:63
[0.00]   DMA32 zone: 12288 pages used for memmap
[0.00]   DMA32 zone: 770048 pages, LIFO batch:63
[0.00]   Normal zone: 16384 pages used for memmap
[0.00]   Normal zone: 1048576 pages, LIFO batch:63
[0.00] percpu: Embedded 32 pages/cpu s93720 r8192 d29160 u131072
[0.00] pcpu-alloc: s93720 r8192 d29160 u131072 alloc=32*4096
[0.00] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[0.00] Detected PIPT I-cache on CPU0
[0.00] CPU features: detected: EL2 vector hardening
[0.00] CPU features: kernel page table isolation forced ON by KASLR
[0.00] CPU features: detected: Kernel page table isolation (KPTI)
[0.00] ARM_SMCCC_ARCH_WORKAROUND_1 missing from firmware
[0.00] CPU features: detected: ARM erratum 1319367
[0.00] Built 1 zonelists, mobility grouping on.  Total pages: 1983488
[0.00] Policy zone: Normal
[0.00] Kernel command line: 
video=HDMI-A-1:3840x2160M@30,margin_left=48,margin_right=48,margin_top=48,margin_bottom=48
 dma.dmachans=0x71f5 bcm2709.boardrev=0xd03114 bcm2709.serial=0x488d2af3 
bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=42 
bcm2709.disk_led_active_low=0 smsc95xx.macaddr=DC:A6:32:BB:99:D9 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  console=tty0 
console=ttyS1,115200 root=/dev/mmcblk1p2 rw elevator=bfq fsck.repair=yes 
net.ifnames=0  rootwait systemd.unified_cgroup_hierarchy=1
[0.00] Kernel parameter elevator= does not have any effect anymore.
   Please use sysfs to set IO scheduler for individual devices.
[0.00] Dentry cache hash table entries: 1048576 (order: 11, 8388608 
bytes, linear)
[0.00] Inode-cache hash table entries: 524288 (order: 10, 4194304 
bytes, linear)
[0.00] mem auto-init: stack:off, heap alloc:off, heap free:off
[0.00] software IO TLB: mapped [mem 0x2500-0x2900] (64MB)
[0.00] Memory: 4732836K/8060928K available (10684K kernel code, 1848K 
rwdata, 3808K rodata, 5184K init, 561K bss, 277044K reserved, 65536K 
cma-reserved)
[0.00] random

Bug#968109: linux-image-5.7.0-2-arm64: USB unusable on Raspberry Pi 4B 8GB

[Ryutaroh Matsumoto]

Package: src:linux
Version: 5.7.10-1
Severity: normal

Dear Maintainer,

I installed an SD card image from
https://raspi.debian.net/daily/raspi_4.img.xz
to Raspberry Pi 4B 8GB (board revision 1.4).

USB is unusable and "lsusb" shows nothing.
Relevant dmesg is as follows:


[3.198861] pci :01:00.0: enabling device ( -> 0002)
[8.663493] pci :01:00.0: xHCI HW not ready after 5 sec (HC bug?) status 
= 0x801
[8.663690] pci :01:00.0: quirk_usb_early_handoff+0x0/0x890 took 5336734 
usecs

[   12.265387] xhci_hcd :01:00.0: xHCI Host Controller
[   12.268816] mmc0: queuing unknown CIS tuple 0x80 (7 bytes)
[   12.278041] dwc2 fe98.usb: supply vusb_d not found, using dummy regulator
[   12.278134] dwc2 fe98.usb: supply vusb_a not found, using dummy regulator
[   12.282227] xhci_hcd :01:00.0: new USB bus registered, assigned bus 
number 1
[   22.320273] xhci_hcd :01:00.0: can't setup: -110
[   22.336521] xhci_hcd :01:00.0: USB bus 1 deregistered
[   22.353573] xhci_hcd :01:00.0: init :01:00.0 fail, -110


Best regards, Ryutaroh Matsumoto

-- Package-specific info:
** Version:
Linux version 5.7.0-2-arm64 (debian-kernel@lists.debian.org) (gcc version 9.3.0 
(Debian 9.3.0-15), GNU ld (GNU Binutils for Debian) 2.35) #1 SMP Debian 
5.7.10-1 (2020-07-26)

** Command line:
video=HDMI-A-1:3840x2160M@30,margin_left=48,margin_right=48,margin_top=48,margin_bottom=48
 dma.dmachans=0x71f5 bcm2709.boardrev=0xd03114 bcm2709.serial=0x488d2af3 
bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=42 
bcm2709.disk_led_active_low=0 smsc95xx.macaddr=DC:A6:32:BB:99:D9 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  console=tty0 
console=ttyS1,115200 root=/dev/mmcblk1p2 rw elevator=deadline fsck.repair=yes 
net.ifnames=0  rootwait

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

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

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

** Loaded modules:
nls_ascii
nls_cp437
vfat
fat
hci_uart
btqca
btrtl
btbcm
btsdio
btintel
bcm2835_v4l2(C)
bluetooth
brcmfmac
brcmutil
videobuf2_vmalloc
videobuf2_memops
snd_bcm2835(C)
videobuf2_v4l2
jitterentropy_rng
videobuf2_common
snd_pcm
drbg
snd_timer
videodev
snd
ansi_cprng
cpufreq_dt
cfg80211
mc
soundcore
ecdh_generic
ecc
rfkill
raspberrypi_cpufreq
bcm2835_wdt
bcm2711_thermal
pwm_bcm2835
iproc_rng200
vchiq(C)
rng_core
leds_gpio
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
btrfs
blake2b_generic
xor
xor_neon
zstd_decompress
zstd_compress
raid6_pq
libcrc32c
crc32c_generic
bfq
broadcom
bcm_phy_lib
xhci_pci
dwc2
xhci_hcd
udc_core
mdio_bcm_unimac
usbcore
genet
sdhci_iproc
of_mdio
sdhci_pltfm
i2c_bcm2835
fixed_phy
libphy
sdhci
gpio_regulator
usb_common
phy_generic

** Network interface configuration:
*** /etc/network/interfaces:
# interfaces(5) file used by ifup(8) and ifdown(8)
# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d

*** /etc/network/interfaces.d/eth0:
auto eth0

# TODO: switch back to iptables-persistent once it re-enters testing
iface eth0 inet dhcp
# We don't currently support setup of firewalls here.
#   pre-up iptables-restore < /etc/iptables/rules.v4 || true
#   pre-up ip6tables-restore < /etc/iptables/rules.v6 || ture

*** /etc/network/interfaces.d/wlan0:
auto wlan0

# TODO: switch back to iptables-persistent once it re-enters testing
iface wlan0 inet dhcp
# We don't currently support setup of firewalls here.
#   pre-up iptables-restore < /etc/iptables/rules.v4 || true
#   pre-up ip6tables-restore < /etc/iptables/rules.v6 || ture

** Network status:
*** IP interfaces and addresses:
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host 
   valid_lft forever preferred_lft forever
2: eth0:  mtu 1500 qdisc mq state DOWN group 
default qlen 1000
link/ether dc:a6:32:bb:99:d9 brd ff:ff:ff:ff:ff:ff
3: wlan0:  mtu 1500 qdisc pfifo_fast state UP 
group default qlen 1000
link/ether dc:a6:32:bb:99:da brd ff:ff:ff:ff:ff:ff
inet 192.168.1.84/24 brd 192.168.1.255 scope global dynamic wlan0
   valid_lft 42924sec preferred_lft 42924sec
inet6 2400:4050:2ba1:ac00:dea6:32ff:febb:99da/64 scope global dynamic 
mngtmpaddr 
   valid_lft 14071sec preferred_lft 12271sec
inet6 fe80::dea6:32ff:febb:99da/64 scope link 
   valid_lft forever preferred_lft forever

*** Device statistics:
Inter-|   Receive|  Transmit
 face |bytespackets errs drop fifo frame compressed multicast|bytes
packets errs drop fifo colls carrier compressed
lo:   0   0000 0  0 00  
 0000 0   0  0
  eth0:   0   0000  

Bug#946791: io.weight cannot be enabled in recent Debian kernel package

[Ryutaroh Matsumoto]

Source: linux
Followup-For: Bug #946791
Control: tags -1 + patch

Dear Maintainer,

I reported that IOWeight config item in systemd has no effect
on recent Debian kernels. I found the root cause.
io.weight was changed to io.bfq.weight, and recent systemd sets
values of IOWeight to io.bfq.weight as

https://github.com/systemd/systemd/commit/2dbc45aea747f25cc1c3848fded2ec0062f96bcf

For io.bfq.weight to appear in cgroup v2 filesystem, the bfq kernel
module must be loaded. Addition of "bfq" to /etc/initramfs-tools/modules
solved this issue. Since the systemd needs bfq module to be loaded,
changing CONFIG_IOSCHED_BFQ=m to CONFIG_IOSCHED_BFQ=y in kernel config
seems suitable.

If the Debian kernel team considers this issue to be handled by another
package, e.g. initramfs-tools or systemd, please reassign this.
If this issue is considered not being a bug, please close this.

Best regards, Ryutaroh Matsumoto

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.4.0-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8), 
LANGUAGE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#934369: linux-image-5.2.0-1-amd64-unsigned: powertop -i 10 always causes kernel NULL pointer dereference

[Ryutaroh Matsumoto]

Package: src:linux
Version: 5.2.6-1
Severity: normal

Dear Maintainer,

When I run "powertop -i 10" it always triggers "kernel NULL pointer 
dereference".
I observed this issue on two different models on Panasonic notbooks.
I can always reproduce this. dmesg output is pasted below.

Best regards,
Ryutaroh Matsumoto

[ 1653.251287] BUG: kernel NULL pointer dereference, address: 
[ 1653.252724] #PF: supervisor instruction fetch in kernel mode
[ 1653.254161] #PF: error_code(0x0010) - not-present page
[ 1653.255580] PGD 0 P4D 0 
[ 1653.256875] Oops: 0010 [#1] SMP PTI
[ 1653.258313] CPU: 2 PID: 1927 Comm: powertop Tainted: GE 
5.2.0-1-amd64 #1 Debian 5.2.6-1
[ 1653.259375] Hardware name: Panasonic Corporation CF-LX3YEUCU/CFLX3-1L, BIOS 
V1.11L16 10/29/2013
[ 1653.260208] RIP: 0010:0x0
[ 1653.260973] Code: Bad RIP value.
[ 1653.261694] RSP: 0018:b2328376bcd8 EFLAGS: 00010246
[ 1653.262425] RAX:  RBX: 904c161b7400 RCX: 0001
[ 1653.263141] RDX: 904c15e4bc00 RSI: 904c161b7400 RDI: 904c1735e2b0
[ 1653.263854] RBP: 904c1735e2b0 R08:  R09: 
[ 1653.264565] R10: 904c17311840 R11:  R12: 904c161b7410
[ 1653.265276] R13: b591cbf0 R14:  R15: 904c161b7400
[ 1653.265976] FS:  7f8f41cdcfc0() GS:904c1790() 
knlGS:
[ 1653.266708] CS:  0010 DS:  ES:  CR0: 80050033
[ 1653.267420] CR2: ffd6 CR3: 0001a61d6003 CR4: 001606e0
[ 1653.268141] Call Trace:
[ 1653.268861]  do_dentry_open+0x13a/0x370
[ 1653.269588]  path_openat+0x2c6/0x1480
[ 1653.270337]  ? terminate_walk+0xe6/0x100
[ 1653.271059]  ? path_lookupat.isra.48+0xa3/0x220
[ 1653.271791]  ? reuse_swap_page+0x105/0x320
[ 1653.272513]  do_filp_open+0x93/0x100
[ 1653.273226]  ? __check_object_size+0x15d/0x189
[ 1653.273945]  do_sys_open+0x184/0x220
[ 1653.274690]  do_syscall_64+0x53/0x130
[ 1653.275426]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 1653.276170] RIP: 0033:0x7f8f420391ae
[ 1653.276909] Code: 25 00 00 41 00 3d 00 00 41 00 74 48 48 8d 05 59 65 0d 00 
8b 00 85 c0 75 69 89 f2 b8 01 01 00 00 48 89 fe bf 9c ff ff ff 0f 05 <48> 3d 00 
f0 ff ff 0f 87 a6 00 00 00 48 8b 4c 24 28 64 48 33 0c 25
[ 1653.278535] RSP: 002b:7ffc883a15b0 EFLAGS: 0246 ORIG_RAX: 
0101
[ 1653.279348] RAX: ffda RBX: 56490228b8b0 RCX: 7f8f420391ae
[ 1653.280172] RDX:  RSI: 7ffc883a2960 RDI: ff9c
[ 1653.281004] RBP: 0008 R08: 0008 R09: 0001
[ 1653.281834] R10:  R11: 0246 R12: 7f8f42405835
[ 1653.282691] R13: 7f8f42405835 R14: 0001 R15: 5649022971a0
[ 1653.283531] Modules linked in: msr(E) xt_CHECKSUM(E) xt_MASQUERADE(E) 
xt_conntrack(E) ipt_REJECT(E) nf_reject_ipv4(E) xt_tcpudp(E) nft_compat(E) 
tun(E) bridge(E) stp(E) llc(E) nft_counter(E) nft_chain_nat(E) nf_nat(E) 
nf_conntrack(E) nf_defrag_ipv6(E) nf_defrag_ipv4(E) nf_tables(E) nfnetlink(E) 
ctr(E) ccm(E) cmac(E) bnep(E) nls_ascii(E) nls_cp437(E) intel_rapl(E) vfat(E) 
x86_pkg_temp_thermal(E) intel_powerclamp(E) fat(E) coretemp(E) kvm_intel(E) 
kvm(E) irqbypass(E) btusb(E) arc4(E) btrtl(E) btbcm(E) btintel(E) 
crct10dif_pclmul(E) crc32_pclmul(E) ghash_clmulni_intel(E) aesni_intel(E) 
aes_x86_64(E) bluetooth(E) iwlmvm(E) uvcvideo(E) videobuf2_vmalloc(E) 
videobuf2_memops(E) videobuf2_v4l2(E) crypto_simd(E) mac80211(E) cryptd(E) 
drbg(E) videobuf2_common(E) glue_helper(E) videodev(E) ansi_cprng(E) 
acpi_als(E) ecdh_generic(E) ecc(E) kfifo_buf(E) media(E) iwlwifi(E) 
snd_hda_codec_realtek(E) snd_hda_codec_generic(E) ledtrig_audio(E) 
industrialio(E) snd_hda_codec_hdmi(E) efi_pstore(E)
[ 1653.283553]  snd_hda_intel(E) mei_me(E) intel_cstate(E) intel_uncore(E) 
snd_hda_codec(E) snd_hda_core(E) joydev(E) efivars(E) snd_hwdep(E) mei(E) 
pcspkr(E) serio_raw(E) panasonic_laptop(E) rmi_smbus(E) intel_rapl_perf(E) 
sparse_keymap(E) sg(E) rmi_core(E) snd_pcm(E) iTCO_wdt(E) 
iTCO_vendor_support(E) cfg80211(E) snd_timer(E) snd(E) rfkill(E) watchdog(E) 
soundcore(E) intel_pch_thermal(E) processor_thermal_device(E) 
int3402_thermal(E) int3403_thermal(E) int340x_thermal_zone(E) 
int3400_thermal(E) intel_soc_dts_iosf(E) acpi_thermal_rel(E) pcc_cpufreq(E) 
evdev(E) intel_smartconnect(E) battery(E) ac(E) parport_pc(E) ppdev(E) lp(E) 
parport(E) efivarfs(E) ip_tables(E) x_tables(E) autofs4(E) ext4(E) crc16(E) 
mbcache(E) jbd2(E) btrfs(E) xor(E) zstd_decompress(E) zstd_compress(E) 
raid6_pq(E) libcrc32c(E) crc32c_generic(E) sd_mod(E) xhci_pci(E) ehci_pci(E) 
xhci_hcd(E) ehci_hcd(E) ahci(E) sdhci_pci(E) libahci(E) cqhci(E) i915(E) 
i2c_algo_bit(E) crc32c_intel(E) sdhci(E) psmouse(E) libata(E) i2c_i801(E)
[ 1653.288408]  drm_kms_helper(E) scsi_mod(E) usbcore(E) lpc_ich(E) e1000e(E) 
mmc_core(E) mfd_core(E) drm(E) usb_common(E) fan(E) video(E) bu

Bug#934309: linux-image-5.2.0-1-amd64-unsigned: suggesting INTEL_IOMMU_DEFAULT_ON

[Ryutaroh Matsumoto]

Package: src:linux
Version: 5.2.6-1
Severity: wishlist

Dear Maintainer,

Without hardware IOMMU, heavy IO traffic sometimes causes
"swiotlb buffer is full" from kernel/dma/swiotlb.c.
Then an error is returned to a device driver calling dma_map_sg()
or something similar. Some device drivers (e.g. ehci-pci.c) do
not handle failures from dma_map_*() functions, and failures
of assigning DMA memories often lead undesirable behaviors.
Enablement of hardware IOMMU reduces possiblity of "swiotlb buffer is full".

I'd like to request to consider INTEL_IOMMU_DEFAULT_ON.
AMD IOMMU seems to be enabled by default, btw.

Best regards,
Ryutaroh Matsumoto

-- Package-specific info:
** Version:
Linux version 5.2.0-1-amd64 (debian-kernel@lists.debian.org) (gcc
version 8.3.0 (Debian 8.3.0-19)) #1 SMP Debian 5.2.6-1 (2019-08-05)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.2.0-1-amd64
root=UUID=12f1110c-5548-452b-ba7e-b995b8aa7f45 ro i915.fastboot=1
swiotlb=noforce iommu=force,merge,nopanic,nopt intel_iommu=on
cgoup_no_v1=all systemd.unified_cgroup_hierarchy=1
systemd.show_status=1

** Tainted: E (8192)
 * Unsigned module has been loaded.

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: Panasonic Corporation
product_name: CFSZ6-1L
product_version: 001
chassis_vendor: Panasonic Corporation
chassis_version: 001
bios_vendor: American Megatrends Inc.
bios_version: V1.11L10
board_vendor: Panasonic Corporation
board_name: CFSZ6-1L
board_version: 1

** Loaded modules:
ctr(E)
ccm(E)
cmac(E)
cpufreq_powersave(E)
cpufreq_userspace(E)
cpufreq_conservative(E)
bnep(E)
intel_rapl(E)
x86_pkg_temp_thermal(E)
intel_powerclamp(E)
coretemp(E)
kvm_intel(E)
kvm(E)
irqbypass(E)
crct10dif_pclmul(E)
crc32_pclmul(E)
ghash_clmulni_intel(E)
nls_ascii(E)
nls_cp437(E)
vfat(E)
fat(E)
arc4(E)
snd_hda_codec_hdmi(E)
snd_soc_skl(E)
snd_soc_skl_ipc(E)
snd_soc_sst_ipc(E)
cdc_mbim(E)
snd_hda_codec_realtek(E)
btusb(E)
snd_soc_sst_dsp(E)
btrtl(E)
btbcm(E)
snd_hda_codec_generic(E)
cdc_wdm(E)
btintel(E)
snd_hda_ext_core(E)
ledtrig_audio(E)
snd_soc_acpi_intel_match(E)
snd_soc_acpi(E)
snd_soc_core(E)
qcserial(E)
bluetooth(E)
usb_wwan(E)
cdc_ncm(E)
snd_compress(E)
efi_pstore(E)
aesni_intel(E)
usbnet(E)
mii(E)
snd_hda_intel(E)
usbserial(E)
aes_x86_64(E)
crypto_simd(E)
cryptd(E)
glue_helper(E)
intel_cstate(E)
uvcvideo(E)
iwlmvm(E)
snd_hda_codec(E)
videobuf2_vmalloc(E)
videobuf2_memops(E)
intel_uncore(E)
videobuf2_v4l2(E)
mac80211(E)
iTCO_wdt(E)
intel_rapl_perf(E)
videobuf2_common(E)
snd_hda_core(E)
serio_raw(E)
iTCO_vendor_support(E)
snd_hwdep(E)
videodev(E)
watchdog(E)
drbg(E)
iwlwifi(E)
media(E)
snd_pcm(E)
efivars(E)
pcspkr(E)
snd_timer(E)
ansi_cprng(E)
snd(E)
soundcore(E)
cfg80211(E)
tpm_crb(E)
ecdh_generic(E)
ecc(E)
rfkill(E)
sg(E)
mei_me(E)
processor_thermal_device(E)
mei(E)
intel_soc_dts_iosf(E)
intel_pch_thermal(E)
battery(E)
acpi_als(E)
kfifo_buf(E)
industrialio(E)
int3403_thermal(E)
int340x_thermal_zone(E)
tpm_tis(E)
tpm_tis_core(E)
panasonic_laptop(E)
int3406_thermal(E)
tpm(E)
sparse_keymap(E)
rng_core(E)
int3400_thermal(E)
acpi_pad(E)
acpi_thermal_rel(E)
ac(E)
pcc_cpufreq(E)
evdev(E)
joydev(E)
parport_pc(E)
ppdev(E)
lp(E)
parport(E)
efivarfs(E)
ip_tables(E)
x_tables(E)
autofs4(E)
ext4(E)
crc16(E)
mbcache(E)
jbd2(E)
crc32c_generic(E)
sr_mod(E)
cdrom(E)
sd_mod(E)
ahci(E)
libahci(E)
crc32c_intel(E)
i915(E)
psmouse(E)
sdhci_pci(E)
xhci_pci(E)
i2c_algo_bit(E)
cqhci(E)
xhci_hcd(E)
libata(E)
drm_kms_helper(E)
e1000e(E)
scsi_mod(E)
i2c_i801(E)
sdhci(E)
mmc_core(E)
usbcore(E)
drm(E)
usb_common(E)
fan(E)
video(E)
button(E)

** Network interface configuration:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

** Network status:
*** IP interfaces and addresses:
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN
group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: enp0s31f6:  mtu 1500 qdisc
pfifo_fast state DOWN group default qlen 1000
link/ether a8:13:74:97:2f:94 brd ff:ff:ff:ff:ff:ff
3: wwp0s20f0u2i12:  mtu 1500 qdisc noop
state DOWN group default qlen 1000
link/ether ba:d9:fa:0c:cc:18 brd ff:ff:ff:ff:ff:ff
4: wlp2s0:  mtu 1500 qdisc noqueue
state UP group default qlen 1000
link/ether 00:28:f8:4a:37:bf brd ff:ff:ff:ff:ff:ff
inet 192.168.1.4/24 brd 192.168.1.255 scope global dynamic
noprefixroute wlp2s0
   valid_lft 13555sec preferred_lft 13555sec
inet6 2409:251:2c0:1500:fbf1:f1f9:2ab9:f9c7/64 scope global
dynamic noprefixroute
   valid_lft 13558sec preferred_lft 11758sec
inet6 fe80::9b0f:dffc:a216:933/64 scope link noprefixroute
   valid_lft forever preferred_lft forever

*

Bug#931247: linux-image-5.0.0-trunk-amd64-unsigned: could enable pressure stall information?

[Ryutaroh Matsumoto]

Package: src:linux
Version: 5.0.2-1~exp1
Severity: wishlist

Dear Maintainer,

Could you consider to set the kernel config variables as follows?
CONFIG_PSI=y
CONFIG_PSI_DEFAULT_DISABLED=y

PSI stands for "pressure stall information" as described in
https://lwn.net/ml/cgroups/20180712172942.10094-1-han...@cmpxchg.org/

It is enabled only if "psi=1" is given as the boot kernel parameter,
so the only interested users can try and be affected.

Best regards,
Ryutaroh Matsumoto


-- Package-specific info:
** Version:
Linux version 5.0.0-trunk-amd64 (debian-kernel@lists.debian.org) (gcc version 
8.3.0 (Debian 8.3.0-3)) #1 SMP Debian 5.0.2-1~exp1 (2019-03-18)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.0.0-trunk-amd64 
root=UUID=2fac8e46-9da0-4d9c-8b22-79bc7c6e1a8d ro psi=1 i8042.reset=1 
systemd.unified_cgroup_hierarchy=1

** Tainted: E (8192)
 * Unsigned module has been loaded.

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: Panasonic Corporation
product_name: CF-LX3YEUCU
product_version: 001
chassis_vendor: Panasonic Corporation
chassis_version: 001
bios_vendor: American Megatrends Inc.
bios_version: V1.11L16
board_vendor: Panasonic Corporation
board_name: CFLX3-1L
board_version: 1

** Loaded modules:
fuse(E)
ufs(E)
qnx4(E)
hfsplus(E)
hfs(E)
minix(E)
ntfs(E)
msdos(E)
jfs(E)
xfs(E)
dm_mod(E)
nft_chain_route_ipv4(E)
xt_CHECKSUM(E)
nft_chain_nat_ipv4(E)
ipt_MASQUERADE(E)
nf_nat_ipv4(E)
nf_nat(E)
xt_conntrack(E)
nf_conntrack(E)
nf_defrag_ipv6(E)
nf_defrag_ipv4(E)
ipt_REJECT(E)
nf_reject_ipv4(E)
nft_counter(E)
xt_tcpudp(E)
nft_compat(E)
tun(E)
bridge(E)
stp(E)
llc(E)
nf_tables(E)
devlink(E)
nfnetlink(E)
ctr(E)
ccm(E)
cmac(E)
bnep(E)
nls_ascii(E)
nls_cp437(E)
vfat(E)
fat(E)
intel_rapl(E)
x86_pkg_temp_thermal(E)
intel_powerclamp(E)
coretemp(E)
arc4(E)
kvm_intel(E)
btusb(E)
kvm(E)
irqbypass(E)
uvcvideo(E)
btrtl(E)
btbcm(E)
iwlmvm(E)
videobuf2_vmalloc(E)
videobuf2_memops(E)
videobuf2_v4l2(E)
btintel(E)
mac80211(E)
snd_hda_codec_realtek(E)
snd_hda_codec_generic(E)
snd_hda_codec_hdmi(E)
ledtrig_audio(E)
videobuf2_common(E)
snd_hda_intel(E)
videodev(E)
snd_hda_codec(E)
snd_hda_core(E)
iwlwifi(E)
media(E)
snd_hwdep(E)
snd_pcm(E)
snd_timer(E)
snd(E)
bluetooth(E)
drbg(E)
ansi_cprng(E)
ecdh_generic(E)
acpi_als(E)
soundcore(E)
crct10dif_pclmul(E)
cfg80211(E)
crc32_pclmul(E)
mei_me(E)
ghash_clmulni_intel(E)
kfifo_buf(E)
industrialio(E)
sg(E)
mei(E)
joydev(E)
rfkill(E)
iTCO_wdt(E)
iTCO_vendor_support(E)
serio_raw(E)
efi_pstore(E)
efivars(E)
int3400_thermal(E)
processor_thermal_device(E)
panasonic_laptop(E)
intel_smartconnect(E)
acpi_thermal_rel(E)
intel_soc_dts_iosf(E)
int3403_thermal(E)
intel_pch_thermal(E)
int3402_thermal(E)
int340x_thermal_zone(E)
evdev(E)
pcspkr(E)
sparse_keymap(E)
pcc_cpufreq(E)
intel_cstate(E)
intel_uncore(E)
intel_rapl_perf(E)
battery(E)
ac(E)
parport_pc(E)
ppdev(E)
lp(E)
parport(E)
efivarfs(E)
ip_tables(E)
x_tables(E)
autofs4(E)
ext4(E)
crc16(E)
mbcache(E)
jbd2(E)
fscrypto(E)
ecb(E)
btrfs(E)
xor(E)
zstd_decompress(E)
zstd_compress(E)
raid6_pq(E)
libcrc32c(E)
crc32c_generic(E)
sd_mod(E)
crc32c_intel(E)
aesni_intel(E)
i915(E)
ahci(E)
sdhci_pci(E)
ehci_pci(E)
libahci(E)
xhci_pci(E)
i2c_algo_bit(E)
cqhci(E)
aes_x86_64(E)
crypto_simd(E)
xhci_hcd(E)
libata(E)
psmouse(E)
cryptd(E)
ehci_hcd(E)
glue_helper(E)
sdhci(E)
drm_kms_helper(E)
lpc_ich(E)
i2c_i801(E)
scsi_mod(E)
mmc_core(E)
usbcore(E)
e1000e(E)
usb_common(E)
drm(E)
thermal(E)
fan(E)
video(E)
button(E)

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Haswell-ULT DRAM Controller 
[8086:0a04] (rev 09)
Subsystem: Matsushita Electric Industrial Co., Ltd. Haswell-ULT DRAM 
Controller [10f7:8338]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: hsw_uncore

00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT 
Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA 
controller])
Subsystem: Matsushita Electric Industrial Co., Ltd. Haswell-ULT 
Integrated Graphics Controller [10f7:8338]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

00:03.0 Audio device [0403]: Intel Corporation Haswell-ULT HD Audio Controller 
[8086:0a0c] (rev 09)
Subsystem: Matsushita Electric Industrial Co., Ltd. Haswell-ULT HD 
Audio Controller [10f7:8338]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

00:04.0 Signal processing control