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

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

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

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

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

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


--- End Message ---
Reply to: