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

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

Bug#984873: linux-image-5.10.0-4-arm64: RPi4 8 GB lost USB support (doesn't start with / on USB device)

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

Contents

  Bug#984873: linux-image-5.10.0-4-arm64: RPi4 8 GB lost USB support (doesn't start with / on USB device) Jan Huijsmans <huysmans@trillian.koffie.nu> - 2021-03-09 15:40 +0100
    Bug#984873: linux-image-5.10.0-4-arm64: RPi4 8 GB lost USB support (doesn't start with / on USB device) Diederik de Haas <didi.debian@cknow.org> - 2021-03-09 16:20 +0100
    Bug#984873: marked as done (linux-image-5.10.0-4-arm64: RPi4 8 GB  lost USB support (doesn't start with / on USB device)) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2021-09-24 12:40 +0200

#69767 — Bug#984873: linux-image-5.10.0-4-arm64: RPi4 8 GB lost USB support (doesn't start with / on USB device)

Package: src:linux
Version: 5.10.19-1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

Updating from linux-image-5.9.0-4-arm64 to linux-image-5.10.0-3/4-arm64
resulted in a non-booting system due to missing/incorrect USB support
for the RPi4 8GB. (system has / on USB SSD)

Only method to get the system booting again is to change config.txt to
boot the available 5.9.0-4 kernel. System came up as expected.

With the 5.10 kernels I tested (-3 and -4 packages) the boot halted
after detecting the partitions on mmcblk1 , on 5.9.0-4 it continues
to detect the storange via USB and boots from it.

Regards,

Jan Huijsmans

-- Package-specific info:
** Kernel log: boot messages should be attached

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

** PCI devices:
not available

** USB devices:
Bus 002 Device 002: ID 0578:0578 Intrinsix Corp. KingSpec Z3-128
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 413c:2003 Dell Computer Corp. Keyboard SK-8115
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


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

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

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

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

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

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

-- no debconf information

[toc] | [next] | [standalone]

#69769

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

On dinsdag 9 maart 2021 15:17:01 CET Jan Huijsmans wrote:
> Updating from linux-image-5.9.0-4-arm64 to linux-image-5.10.0-3/4-arm64
> resulted in a non-booting system due to missing/incorrect USB support
> for the RPi4 8GB. (system has / on USB SSD)
> 
> Only method to get the system booting again is to change config.txt to
> boot the available 5.9.0-4 kernel. System came up as expected.
> 
> With the 5.10 kernels I tested (-3 and -4 packages) the boot halted
> after detecting the partitions on mmcblk1 , on 5.9.0-4 it continues
> to detect the storange via USB and boots from it.

This is possibly a duplicate of bug #977694 and a possible solution can be 
found here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977694#67

Could you try whether that fixes it for you too?

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

#73045 — Bug#984873: marked as done (linux-image-5.10.0-4-arm64: RPi4 8 GB lost USB support (doesn't start with / on USB device))

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

Your message dated Fri, 24 Sep 2021 12:29:58 +0200
with message-id <2054802.vA3YWZxDMA@bagend>
and subject line Re: Bug#991714: linux-image-5.10.0-8-arm64: RPi 4 (8 GB) - CPU stuck in highest speed
has caused the Debian Bug report #984873,
regarding linux-image-5.10.0-4-arm64: RPi4 8 GB lost USB support (doesn't start with / on USB device)
to be marked as done.

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

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


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

[toc] | [prev] | [standalone]

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

csiph-web