Your message dated Sun, 08 Dec 2019 21:47:09 +0000
with message-id <e1ie4ot-0007nj...@fasolo.debian.org>
and subject line Bug#941974: fixed in raspi3-firmware 1.20190215-1+deb10u2
has caused the Debian Bug report #941974,
regarding raspi3-firmware: serial console output sent to bluetooth port with 
kernel 5.x
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 ow...@bugs.debian.org
immediately.)


-- 
941974: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941974
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: raspi3-firmware
Version: 1.20190215-1+deb10u1
Severity: critical
Justification: breaks the whole system

I’ve set the severity high because this MIGHT break hardware,
but it it doesn’t (I don’t know enough to judge) feel free to
classify as less critical.

/etc/kernel/postinst.d/z50-raspi3-firmware contains this gem:

   90   serial="ttyAMA0,115200"
   91   kernelmajor=$(echo "${latest_kernel_basename}" | sed 's,^vmlinuz-,,g' | 
cut -d. -f 1)
   92   kernelminor=$(echo "${latest_kernel_basename}" | cut -d. -f 2)
   93   if [ $kernelmajor -ge 4 ]; then
   94     if [ $kernelminor -ge 14 ]; then
   95       # Since Linux 4.14, /dev/ttyS1 is the UART on the pinheader.
   96       serial="ttyS1,115200"
   97     fi
   98   fi

The intent is to set serial to ttyAMA0 for Linux << 4.14
and to ttyS1 for Linux >= 4.14, but this fails obviously
using the old location for 5.0‥5.13, 6.0‥6.13, …

You’ll wish to use this instead:

        serial="ttyAMA0,115200"
        kernelmajmin=$(($(echo $latest_kernel_basename | sed -n \
            's/^vmlinu.-\([0-9]*\)\.\([0-9]*\)\..*$/\1*1000+\2/p')))
        if test $kernelmajmin -ge 4014; then
                # Since Linux 4.14, /dev/ttyS1 is the UART on the pinheader.
                serial="ttyS1,115200"
        fi

This must be fixed in stable, since the 5.x kernel is in
backports, or at least in unstable and available via backports
and the backports kernel must Breaks the versions prior to this fix.

-- System Information:
Debian Release: 10.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: arm64 (aarch64)

Kernel: Linux 5.2.0-0.bpo.2-arm64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_CRAP
Locale: LANG=C.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages raspi3-firmware depends on:
ii  dosfstools  4.1-2

raspi3-firmware recommends no packages.

raspi3-firmware suggests no packages.

-- Configuration Files:
/etc/default/raspi3-firmware changed:
CMA=128M


-- no debconf information

--- End Message ---
--- Begin Message ---
Source: raspi3-firmware
Source-Version: 1.20190215-1+deb10u2

We believe that the bug you reported is fixed in the latest version of
raspi3-firmware, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 941...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Romain Perier <romain.per...@gmail.com> (supplier of updated raspi3-firmware 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sat, 09 Nov 2019 09:09:08 +0100
Source: raspi3-firmware
Binary: raspi3-firmware
Built-For-Profiles: cross nopython nodoc pkg.linux.notools
Architecture: source armhf
Version: 1.20190215-1+deb10u2
Distribution: buster
Urgency: medium
Maintainer: pkg-raspi <pkg-raspi-maintain...@lists.alioth.debian.org>
Changed-By: Romain Perier <romain.per...@gmail.com>
Description:
 raspi3-firmware - Raspberry Pi 2 and 3 GPU firmware and bootloaders
Closes: 941974
Changes:
 raspi3-firmware (1.20190215-1+deb10u2) buster; urgency=medium
 .
   * Fix serial console output sent to bluetooth port with kernel 5.x.
     Thanks to Thorsten Glaser (Closes: #941974)
Checksums-Sha1:
 48ed45243c4a03d9b8060587ad2190300e29d0ce 2180 
raspi3-firmware_1.20190215-1+deb10u2.dsc
 229e84616a2ddc2341099679968f9d91758a64d8 23368 
raspi3-firmware_1.20190215-1+deb10u2.debian.tar.xz
 117e82a51fb294a5eebe90f9140b100a31b9b8f1 5733 
raspi3-firmware_1.20190215-1+deb10u2_armhf.buildinfo
 34feca507d1b04657e6965396767972e919d7dc4 13144372 
raspi3-firmware_1.20190215-1+deb10u2_armhf.deb
Checksums-Sha256:
 e32b8f888cd03da0be7830575fbd4a82aa2edb8c430939f6ad3ba7c2e54b730b 2180 
raspi3-firmware_1.20190215-1+deb10u2.dsc
 c20259b45bb1ed8bd81e6f2b870226f25b3b2e7fcb423e810a33daeac130a514 23368 
raspi3-firmware_1.20190215-1+deb10u2.debian.tar.xz
 2f1fcd3d67929dada6c2604cc5c0bc94817673b240f46351fb6d620e71f54101 5733 
raspi3-firmware_1.20190215-1+deb10u2_armhf.buildinfo
 305f3dc50cbc9e29227420d0b6e5e775d135a02a47f3929a2a8d61cbf7aa1b1a 13144372 
raspi3-firmware_1.20190215-1+deb10u2_armhf.deb
Files:
 0bedf1566ea6197e96cee484b76c5814 2180 non-free/misc optional 
raspi3-firmware_1.20190215-1+deb10u2.dsc
 caece14972d067e40c681a35cca718b2 23368 non-free/misc optional 
raspi3-firmware_1.20190215-1+deb10u2.debian.tar.xz
 171440ce19f4423fff095658dc3dd633 5733 non-free/misc optional 
raspi3-firmware_1.20190215-1+deb10u2_armhf.buildinfo
 7ea191906be81c2d01a1499ed566bbb4 13144372 non-free/misc optional 
raspi3-firmware_1.20190215-1+deb10u2_armhf.deb

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEbpWHxyX/nlEWTnf8WhIh6CKeimAFAl3r1SYACgkQWhIh6CKe
imCTHg//TXb6e0+WR+dQuD7RXADByZC35MDWvQKD/AJggo19NC3GM3QD9dFTdzWa
ipOmeOZFDYUxHFEF2f2Mutd6njKmsws/jR9zBefTb5Dv7RPEtd1rWcnRDXRSAg3C
uIiDDwnJ0d9+n7E3jrhppffgJDs7hPGcyftto1STp9DeKJnk4apLgXmmR3OBCbzn
go48sn4x6Tr9+HERY36xof5a8Hw424uCTXlGSy+Dn4zZWDPNBGwzPThq0gcoQnor
0TD9YmG6+zwO3Y7CZ36oQWiraxJblaspBdh4FN0NCzgp2sdYNq8m1OoW6splBbRI
4jv8Z8poiFBntKOuqKdSVCmPm+WudPwEMIngTm0l5ToWCjGfCFmEF9bu0kbsw7Q/
9atB/L9HrO72rrkmrsNMMc304W7yBmz/5S5PZKhAYA3UcESNNwInWcF0ac/nmT8O
6ihxGoE8Gn/5qW747C8Gy2+ftzy/N3W2uK0EMXkxlL8cZn+PyiEL6ZOdE4KOidPV
xwFaDYdGe3BsGxA469PVuTUL7uYNzrkgpza7dkWY80HbPg0AGNGbBKFLg2633p58
HCdbwVIrFV4Fhf64EE/Q1XLptbbheVmquYc7+2JD4ouaaYgeau5w7ITwBq9uQR/B
u9/MY6W35EovhH1HIn6qTdjfWAmQ6S5mTuHkxBibFmrFiA0gG+U=
=WUTd
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to