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

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

Bug#979187: 979187 is fixed-upstream

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

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#979187: 979187 is fixed-upstream Ryutaroh Matsumoto <ryutaroh@ict.e.titech.ac.jp> - 2021-01-21 03:20 +0100
    Bug#979187: 979187 is fixed-upstream Salvatore Bonaccorso <carnil@debian.org> - 2021-01-21 11:40 +0100
      Bug#977694: 977694 & 979187 fixed-upstream but remain in Debian :-< Ryutaroh Matsumoto <ryutaroh@ict.e.titech.ac.jp> - 2021-01-22 12:00 +0100
        Bug#977694: 977694 & 979187 fixed-upstream but remain in Debian :-< Ryutaroh Matsumoto <ryutaroh@ict.e.titech.ac.jp> - 2021-01-23 13:10 +0100
          Bug#979187: 977694 & 979187 fixed-upstream but remain in Debian :-< Ryutaroh Matsumoto <ryutaroh@ict.e.titech.ac.jp> - 2021-01-24 07:10 +0100
            Processed: Re: 977694 & 979187 fixed-upstream but remain in  Debian :-< "Debian Bug Tracking System" <owner@bugs.debian.org> - 2021-01-24 07:10 +0100
            Bug#979187: 977694 & 979187 fixed-upstream but remain in Debian :-< Ryutaroh Matsumoto <ryutaroh@ict.e.titech.ac.jp> - 2021-01-26 02:40 +0100
              Bug#977694: 5.10.4 Debian kernel does not boot on raspi 4 with ext4 rootfs and usb-msd Ryutaroh Matsumoto <ryutaroh@ict.e.titech.ac.jp> - 2021-01-28 05:40 +0100
                Processed: Re: 5.10.4 Debian kernel does not boot on raspi 4 with  ext4 rootfs and usb-msd "Debian Bug Tracking System" <owner@bugs.debian.org> - 2021-01-28 05:40 +0100
          Bug#977694: 977694 & 979187 fixed-upstream but remain in Debian :-< Ryutaroh Matsumoto <ryutaroh@ict.e.titech.ac.jp> - 2021-01-24 07:10 +0100

#69222 — Bug#979187: 979187 is fixed-upstream

Control: tags -1 + fixed-upstream

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

[toc] | [next] | [standalone]

#69225

On Thu, Jan 21, 2021 at 11:08:27AM +0900, Ryutaroh Matsumoto wrote:
> Control: tags -1 + fixed-upstream
> 
> Self-compiled 5.10.9 does not show this reported symptom,
> and I assume this is fixed-upstream. Ryutaroh

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?

Regards,
Salvatore

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

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

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

Control: found -1 5.10.9-1

Hi Salvatore, thank you very much for your attention!

From: Salvatore Bonaccorso <carnil@debian.org>
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

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

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

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

>> 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

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

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

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 <ryutaroh@ict.e.titech.ac.jp>
> 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

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

#69314 — Processed: Re: 977694 & 979187 fixed-upstream but remain in Debian :-<

Processing control commands:

> severity -1 minor
Bug #979187 [src:linux] 5.9.15 Debian kernel stopped booting on raspi 4 with Elecom USB MSD 056e:6a13
Severity set to 'minor' from 'normal'

-- 
979187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979187
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

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

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

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

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

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

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

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

#69350 — Processed: Re: 5.10.4 Debian kernel does not boot on raspi 4 with ext4 rootfs and usb-msd

Processing control commands:

> reassign -1 raspi-firmware 1.20210111+ds-2
Bug #977694 [src:linux] 5.10.4 Debian kernel does not boot on raspi 4 with ext4 rootfs and usb-msd
Bug reassigned from package 'src:linux' to 'raspi-firmware'.
No longer marked as found in versions linux/5.10.9-1.
Ignoring request to alter fixed versions of bug #977694 to the same values previously set
Bug #977694 [raspi-firmware] 5.10.4 Debian kernel does not boot on raspi 4 with ext4 rootfs and usb-msd
Marked as found in versions raspi-firmware/1.20210111+ds-2.

-- 
977694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977694
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

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

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

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

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

[toc] | [prev] | [standalone]

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

csiph-web