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
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
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
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
initrd.img-5.10.0-5-rt-arm64
disable_fw_kms_setup=1
disable_overscan=1
hdmi_enable_4kp60=1
Best regards, Ryutaroh Matsumoto
enable_compat_alsa:Enables ALSA compatibility virtual audio
device (bool)
parm: num_channels:Number of audio channels (default: 8) (int)
Best regards, Ryutaroh
ween 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
vide 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
From: Ryutaroh Matsumoto
Subject: vc4.ko brings unusable&unstable 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 settin
Control: notfound -1 20210208-4
#984844 is not observed in 20210208-4 in testing/Bullseye.
Ryutaroh
-kernel/2021-March/008065.html
Best regards, Ryutaroh
://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
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
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
0315-1~exp1 was booted fine...
Best regards, Ryutaroh
dmesg.tar.xz
Description: Binary data
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,
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
[ 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
ebuffer_fetch_non_coherent GL_EXT_texture_sRGB_R8
GL_EXT_texture_shadow_lod GL_MESA_framebuffer_flip_y GL_EXT_depth_clamp
GL_EXT_texture_query_lod "
===
Using modifier ff
failed to set mode: Invalid argument
Best regards, Ryutaroh
.
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
011 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
Control: retitle -1 requesting scsi_debug.ko for arm64&armhf&ppc64el helping
systemd&udisks2 autopkgtest
Lack of scsi_debug.ko is also observed for ppc64el.
Ryutaroh
The lack of scsci_debug.ko for arm64&armhf also makes the autopkgtest-virt-qemu
testsuite fail with udisks2.
Ryutaroh
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&armhf.
Best regards, Ryutaroh Matsumoto
-- Package-specific info:
'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 (
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
lowered severity to normal.
This is an upstream issue.
It is being discussed at "linux-rpi-kernel" mailing list.
Best regards, Ryutaroh Matsumoto
.
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
-queue.git/diff/queue-5.10/drm-vc4-correct-pos1_scl-for-hvs5.patch?id=138ad5c64ba368c5e077b8c178c47f12b29b8701
Best regards, Ryutaroh
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
in src:linux, please reassign this back.
Best regards, 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
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
ccepted by the relevant upstream
> maintainer
> (aside from necessary adjustments for an older kernel version) before being
> applied.
Best regards, Ryutaroh Matsumoto
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
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
rch_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 Lin
ported at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980785
originally found by Lucas.
Best regards, Ryutaroh
5.10.5-1,
the above two issues have come back (I unwelcome them...).
Best regards, Ryutaroh Matsumoto
igate 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;
/2021-January/295122.html
Ryutaroh
0.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]
quot;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
.ko gives garbled screen...
Ryutaroh
Control: tags -1 + fixed-upstream
Self-compiled 5.10.9 does not show this reported symptom,
and I assume this is fixed-upstream. Ryutaroh
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
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: 1
from CMA:"
and no graphics come. Rendering by wayland does not work at all with
vc4.ko in 5.10.9.
Best regards, Ryutaroh
Control: tags -1 + fixed-upstream
I compiled the upstream kernel 5.10.8 and it can use 4K resolution. Ryutaroh
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
, 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
oes 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
/bugreport.cgi?bug=977645
I have checked the symptom with two usb msds, one is hdd and the other is ssd.
Ryutaroh
console=ttyS1,115200 root=LABEL=RASPIROOT rw fsck.repair=yes net.ifnames=0
cma=64M rootwait
Ryutaroh
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
inally, 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 upd
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
://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977645
Best regards, Ryutaroh Matsumoto
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
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 attenti
ble,
I built a Debian kernel pkg with proposed config, and test it.
Best regards, Ryutaroh
K HDMI display
as you wrote at
http://lists.infradead.org/pipermail/linux-rpi-kernel/2020-November/007894.html
Best regards, Ryutaroh Matsumoto
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
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
.
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
- depends on ARCH_BCM || ARCH_BCMSTB || COMPILE_TEST
+ depends on ARCH_BCM || ARCH_BCMSTB || ARCH_BCM2835 || COMPILE_TEST
Best regards, Ryutaroh Matsumoto
to use linux-image-rpi with no change.
Ryutaroh
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
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
ime to correctly build a qemu bootable image by u-boot-rpi:armel package...
Ryutaroh
/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
or 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
eaves 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')
Archite
aw,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:
**
, 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
6-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
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
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
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 Mats
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
!
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
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
] 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
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
[ 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-ar
st 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
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] Oop
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
42.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.debi
Package: linux-image-2.6.18-1-amd64
Version: 2.6.18-2
Severity: normal
"shutdown -h now" reboots my DELL Dimension 9150 instead of
turning it off when automatic wake up is scheduled by BIOS.
Windows XP Home Edition SP2 can turn it off even if automatic
wake up is scheduled by BIOS. So I suspect t
Package: kernel-tree-2.6.8
Version: 2.6.8-12
Severity: important
The description of this package says:
a complete kernel tree with Debian patches applied will be available
after this package is installed.
However, this package only downloads the kernel-source and the
kernel-pache packages, and i
91 matches
Mail list logo
