Bug#968567: linux-image-4.19.0-10-amd64: kernel failure when writing on a GFS2 partition
Hi Dan, On Fri, Sep 11, 2020 at 11:33:47PM +, Craig, Daniel (CASS, Marsfield) wrote: > Hi Salvatore, > > Thanks for chasing this up, I've just built the 4.19.144 vanilla > kernel with the referenced commit applied and can confirm that this > issue no longer occurs on writing to a mounted gfs2 filesystem. Thanks for confirming! I cherry-picked as well the commit for the packaging (and can disapear once we rebase to the version including the backport as well, I confirmed your result to Greg and asked for inclusion in the stable series). Regards, Salvatore
Bug#968567: linux-image-4.19.0-10-amd64: kernel failure when writing on a GFS2 partition
Hi Salvatore, Thanks for chasing this up, I've just built the 4.19.144 vanilla kernel with the referenced commit applied and can confirm that this issue no longer occurs on writing to a mounted gfs2 filesystem. Cheers, Dan. From: Salvatore Bonaccorso on behalf of Salvatore Bonaccorso Sent: Friday, 11 September 2020 11:15 PM To: Craig, Daniel (CASS, Marsfield) ; 968...@bugs.debian.org <968...@bugs.debian.org> Cc: Nicolas Courtel Subject: Re: Bug#968567: linux-image-4.19.0-10-amd64: kernel failure when writing on a GFS2 partition Hi Daniel, hi Nicolas, On Thu, Sep 10, 2020 at 04:47:20AM +, Craig, Daniel (CASS, Marsfield) wrote: > Hi, > > I can confirm the existence of this CPU soft-lock bug with gfs2. > > I won't worry about reproducing the kernel bug message, but I have > done a bit of digging and if I revert the following commit, added in > the 4.19.130 release then this fixes issue for me. > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-4.19.y&id=c91cffd0fd010c06d67f3a9a528b858ce28c60fb > > Note that the problem is still present in the latest upstream > release in the 4.19 series (4.19.144) > > I've reported this bug in the kernel bugzilla, referenced here: > > https://bugzilla.kernel.org/show_bug.cgi?id=209217 Upstream did had a look at this see (you both were CC'ed on that thread though) the thread starting at https://lore.kernel.org/stable/20200910194319.GA131386@eldamar.local/ and suggested that upstream commit cbcc89b630447ec7836aa2b9242d9bb1725f5a61 is definitely needed. Would it be possible for you to test a build with that commit added on top? (Note the patch would need a slight refresh when applying on top of 4.19.144 for context changes). https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s4.2.2 explains how to test a single patch on top of the packaging, or you can try 4.19.144 with the cherry-picked commit. That would be much appreciated. Regards, Salvatore
initramfs-tools_0.138_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 11 Sep 2020 20:37:29 +0100 Source: initramfs-tools Architecture: source Version: 0.138 Distribution: unstable Urgency: medium Maintainer: Debian kernel team Changed-By: Ben Hutchings Closes: 857054 923400 955469 959768 960355 Changes: initramfs-tools (0.138) unstable; urgency=medium . [ Ben Hutchings ] * [0b034b4] docs/maintainer-notes.md: Delete the horizontal rules * [ba883cb] docs/maintainer-notes.md: Use Gitlab markup for table of contents * [5284a00] docs/maintainer-notes.md: Use Gitlab markup for definition table * [a469b7e] docs/maintainer-notes.md: Use archive.org URL for Daniel Baumann doc * [424260e] debian/control, docs/maintainer-notes.md: Use my @debian.org address * [181a35c] update-initramfs: Remove test for direct invocation from kernel package * [6ebe41b] Remove obsolete update-initramfs state in /var/lib/initramfs-tools * [2f2ad0d] hook-functions: copy_exec: Copy libgcc_s.so with any soversion up to 9 (Closes: #959768) * [0f24cc1] Add CI configuration for salsa.debian.org * [9877542] initramfs.conf: Delete "NFS Section" comment * [4309c3b] Add FSTYPE config parameter to allow overriding filesystem type detection (Closes: #923400) * [6300aa1] Change "panic" parameter handling to work more like the kernel * [90d64bd] debian/tests: Add common test preparation code * [3dd2984] debian/tests: Add basic test for amd64 using klibc and not busybox * [69240b1] debian/tests: Add basic test for amd64 using busybox * [3d834c8] debian/tests: Add basic tests for amd64 with only ata/virtio driver * [c14b760] debian/tests: Add test for separate /usr device * [6b3b361] debian/tests: Add test of the panic shell and parameter handling . [ Vagrant Cascadian ] * [482897b] hook-functions: Add modules needed for Pinebook LCD display. . [ Guilherme G. Piccoli ] * [c3cbf35] scripts/functions: Prevents printf error carry over if wrong console is set (Closes: #960355) . [ Unit 193 ] * [3b82099] When overriding configured compressor, warn the user. . [ Norbert Lange ] * [e94f410] un-,mkinitramfs: add support for zstd (Closes: #955469) . [ Jann Horn ] * [a7718dc] Add firmware for built-in drivers (Closes: #857054) Checksums-Sha1: 34a50d294cf32e46c82e59592b948ef19dc0e8d6 1923 initramfs-tools_0.138.dsc db92434b29dd061ec01ff112c721f02c1b0f1d04 94668 initramfs-tools_0.138.tar.xz df9dfe47a5013cb3d9e001ba9954d7d644221277 5970 initramfs-tools_0.138_source.buildinfo Checksums-Sha256: cdd45f17e853f38b6ff73c42259efce66403b4448b3ed938ad7a31fed8c4330f 1923 initramfs-tools_0.138.dsc 5bb142353d8d4438f213f8dc3bc155884420785553263b2b50008ec30eb2dfb0 94668 initramfs-tools_0.138.tar.xz 82c2e1a752a1f1306f786978da1a8e7ac9973476173a8ca4e15ad5556c8214e2 5970 initramfs-tools_0.138_source.buildinfo Files: 304fb7af1dd552e701dd44470a6e9d94 1923 utils optional initramfs-tools_0.138.dsc 47056fd475d71447dcbc49fb678257ea 94668 utils optional initramfs-tools_0.138.tar.xz e13c7f7fccea38f044016afcbe12a62e 5970 utils optional initramfs-tools_0.138_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEErCspvTSmr92z9o8157/I7JWGEQkFAl9b2O0ACgkQ57/I7JWG EQmzMg//er6SVEJA1MAPY/tX5OoQ94YhMmZL7OROIEmYFjqLomIVUM749DUb0uU1 jyosbywPa8PKa26GvJIH0lRpTjPNWK35FBtpRcaZBpOszYDIrprh1EOxFAK/p0Fz jjllRna7RitvHi4cy+qcF0dwk5u4Ap8vCp23ZQBC1mTJMzRWL0ScxEIgzpYzsxTM xGpfhNTch0ErBXrd3+HEY8jjb2KfsDQTJsZH5BJYpzPnCNvjZ3uKx4d9JPCPw9Bu 5CP4WPiTbDL7Znw68OGY3RtMz3ehnZC+FbKczJeVoC/nk5wBSVzvVIAuEavY0o2P oOSXO5LBNIVCla5VBrQIUhIbttyPxJn165Tz9FzRr9cTTadYRmZ9wx1jnFOOTk6a 9/dCrnymSzcGCB67H13PWL2OjD8Lg02PNBKD4Nu5L8j6UV+Ro/y45bSv9JwKzoBm LE1Face5gZn+hE2rTj0hBr9zlchcLZiC/CW235UFmm6xx94EiX6GzkWwceWpQqh6 /kdzTfnjjvh3iCtK6M05d0L7bIGVOlRhnE/JYstyRiKzLhlESEL8cVbG0aTFhDL1 ZcXPlxu5QMeyUgqsXaa4pFolFB/DASgtgMhdu5WQzwsA13VB29SXw1hYRVnd+zrt uBRDSE+47anirgoY5NDVgYgAiGpVPjCdE/87KhBij5fHRGifLqo= =7UYp -END PGP SIGNATURE- Thank you for your contribution to Debian.
Bug#857054: marked as done (initramfs-tools: Firmware for builtin kernel modules not included in initramfs)
Your message dated Fri, 11 Sep 2020 20:36:03 + with message-id and subject line Bug#857054: fixed in initramfs-tools 0.138 has caused the Debian Bug report #857054, regarding initramfs-tools: Firmware for builtin kernel modules not included in initramfs 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.) -- 857054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857054 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: initramfs-tools Version: 0.120+deb8u3 Severity: normal Hi, I am using MODULES=netboot in combination with a custom kernel. This kernel has its network driver bnx2x built in: $ grep BNX2X= /boot/config-$version CONFIG_BNX2X=y The required firmware blobs are not included in the generated initramfs even when specifying bnx2x in /etc/initramfs-tools/modules, because manual_add_modules() from hook-functions does following: $ modprobe --all --ignore-install --quiet --show-depends bnx2x builtin bnx2x $ $ modinfo -k $version -F firmware bnx2x modinfo: ERROR: Module bnx2x not found. I wrote a hook function as workaround: $ cat /etc/initramfs-tools/hooks/fix-missing-firmware #!/bin/sh PREREQ="" prereqs() { echo "$PREREQ" } case $1 in # get pre-requisites prereqs) prereqs exit 0 ;; esac . /usr/share/initramfs-tools/hook-functions for file in /lib/firmware/bnx2x/*; do if test -e $file; then copy_exec $file fi done -- Benjamin Drung System Developer Debian & Ubuntu Developer ProfitBricks GmbH Greifswalder Str. 207 D - 10405 Berlin Email: benjamin.dr...@profitbricks.com URL: http://www.profitbricks.com Sitz der Gesellschaft: Berlin. Registergericht: Amtsgericht Charlottenburg, HRB 125506B. Geschäftsführer: Andreas Gauger, Achim Weiss. --- End Message --- --- Begin Message --- Source: initramfs-tools Source-Version: 0.138 Done: Ben Hutchings We believe that the bug you reported is fixed in the latest version of initramfs-tools, 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 857...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings (supplier of updated initramfs-tools 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: Fri, 11 Sep 2020 20:37:29 +0100 Source: initramfs-tools Architecture: source Version: 0.138 Distribution: unstable Urgency: medium Maintainer: Debian kernel team Changed-By: Ben Hutchings Closes: 857054 923400 955469 959768 960355 Changes: initramfs-tools (0.138) unstable; urgency=medium . [ Ben Hutchings ] * [0b034b4] docs/maintainer-notes.md: Delete the horizontal rules * [ba883cb] docs/maintainer-notes.md: Use Gitlab markup for table of contents * [5284a00] docs/maintainer-notes.md: Use Gitlab markup for definition table * [a469b7e] docs/maintainer-notes.md: Use archive.org URL for Daniel Baumann doc * [424260e] debian/control, docs/maintainer-notes.md: Use my @debian.org address * [181a35c] update-initramfs: Remove test for direct invocation from kernel package * [6ebe41b] Remove obsolete update-initramfs state in /var/lib/initramfs-tools * [2f2ad0d] hook-functions: copy_exec: Copy libgcc_s.so with any soversion up to 9 (Closes: #959768) * [0f24cc1] Add CI configuration for salsa.debian.org * [9877542] initramfs.conf: Delete "NFS Section" comment * [4309c3b] Add FSTYPE config parameter to allow overriding filesystem type detection (Closes: #923400) * [6300aa1] Change "panic" parameter handling to work more like the kernel * [90d64bd] debian/tests: Add common test preparation code * [3dd2984] debian/tests: Add basic test for amd64 using klibc and not busybox * [69240b1] debian/tests: Add basic test for amd64 using busybox * [3d834c8] debian/tests: Add basic tests for amd64 with only ata/virtio driver * [c14b760] debian/tests: Add test for separate /usr device * [6b3b361] debian/tests: Add test of the panic shell and parameter handling . [ Vagrant Cascadian ] * [482897b] hook-functions: Add modules needed for Pinebook LCD display. . [ Guilherme G. Pic
Bug#923400: marked as done (Add option to override filesystem type detection)
Your message dated Fri, 11 Sep 2020 20:36:04 + with message-id and subject line Bug#923400: fixed in initramfs-tools 0.138 has caused the Debian Bug report #923400, regarding Add option to override filesystem type detection 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.) -- 923400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923400 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: initramfs-tools Version: 0.133 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Building a system image using multistrap, including generating an initial ramdisk, worked fine recently. Now it fails with this error message: W: Couldn't identify type of root file system for fsck hook It seems to me that git commit a8ed874 intended to extend the code operating on "auto" mounted filesystems to cover all _except_ root disk, but that the logic is flipped around so that now it _only_ extends that to include root disk: - - case "$MNT_TYPE" in - - auto) [...] + # Ignore filesystem type for /, as it is not available and + # therefore never used at boot time + if [ "${MNT_DIR}" = "/" ] || [ "${MNT_TYPE}" = "auto" ]; then - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlx2vqoACgkQLHwxRsGg ASF8ohAAjuJLFgguQyXi0Xp+v2YhFWxqiZxnSBav7/f85S3UjaqUNU3DjXdFv/FJ 7SkzZShmdqGIkpjxGyajRBGbFZzDJkR2Xn7p1T+CcYHvOcUNPfcWzHumc120l9mW f74frkEC6J/IZX3tFRRXsEZaZ9ZasA16mvoQyL6lXR6ys22gQa3fEVRpGS95jxm2 hH4OorJSLeaGNYiXUMDmav29Aom1We7sojs/fdkQXiSE7Q0nc9jeuOOsSXLkFgKI EvK88J3YpjuzXGNtwYbVn1QyVAYSAqrDyLyTtjtFwUjQbQc3jy/rYW/DeoTQ8lD2 syKc7e2N0xz02Y3JOQWxMdA+SdlQqeiGkQI7AHL23D0MXLcVkCp9WfWfOAlulpKd tNrf7+Bc+tSBz4uNy04xP5UzhLcOKOPy1Rxz2ItSd6vZF0BL/4fptMZBMlvqxWsX f3soeauNDC9F0584K0Fkuhta8jI3KYAJkNOw1omBzjunf8TpnAEKIvr7IfEk9RJp FnE7TF9fUurxxnZx8crBCzNqFRkwj0oCjno/0HMvNKYbucPaXCD/Oco7aU4/KnbP YVj5i9V/sfS7f68N3q6tZF09Tcd0IKPkItm7i796GtQRcVwvLpa7CPPMz4WK33bE P6lP1/ldcx2+THYbL1i4xGhA3S24g4Nn1DSqNZRaZA90cLtZGKU= =0zMd -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: initramfs-tools Source-Version: 0.138 Done: Ben Hutchings We believe that the bug you reported is fixed in the latest version of initramfs-tools, 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 923...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings (supplier of updated initramfs-tools 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: Fri, 11 Sep 2020 20:37:29 +0100 Source: initramfs-tools Architecture: source Version: 0.138 Distribution: unstable Urgency: medium Maintainer: Debian kernel team Changed-By: Ben Hutchings Closes: 857054 923400 955469 959768 960355 Changes: initramfs-tools (0.138) unstable; urgency=medium . [ Ben Hutchings ] * [0b034b4] docs/maintainer-notes.md: Delete the horizontal rules * [ba883cb] docs/maintainer-notes.md: Use Gitlab markup for table of contents * [5284a00] docs/maintainer-notes.md: Use Gitlab markup for definition table * [a469b7e] docs/maintainer-notes.md: Use archive.org URL for Daniel Baumann doc * [424260e] debian/control, docs/maintainer-notes.md: Use my @debian.org address * [181a35c] update-initramfs: Remove test for direct invocation from kernel package * [6ebe41b] Remove obsolete update-initramfs state in /var/lib/initramfs-tools * [2f2ad0d] hook-functions: copy_exec: Copy libgcc_s.so with any soversion up to 9 (Closes: #959768) * [0f24cc1] Add CI configuration for salsa.debian.org * [9877542] initramfs.conf: Delete "NFS Section" comment * [4309c3b] Add FSTYPE config parameter to allow overriding filesystem type detection (Closes: #923400) * [6300aa1] Change "panic" parameter handling to work more like the kernel * [90d64bd] debian/tests: Add common test preparation code * [3dd2984] debian/tests: Add basic test for amd64 using klibc and not busybox * [69240b1] debian/tests: Add basic test for amd64 using busybox * [3d834c8] debian/tests: Add basic tests for amd64 with only
Bug#962545: marked as done (Invalid serial console blocks system boot)
Your message dated Fri, 11 Sep 2020 20:36:04 + with message-id and subject line Bug#960355: fixed in initramfs-tools 0.138 has caused the Debian Bug report #960355, regarding Invalid serial console blocks system boot 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.) -- 960355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960355 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: initramfs-tools Version: 0.137 Followup-For: Bug #960355 Hi Ben and Jonas, I was reporting a similar bug and found this one, thanks to reportbug! So, I think this is indeed a bug. The problem was vastly debugged in a recent Launchpad issue [0], I'll give a summary here. Currently, _log_msg() is like a void-typed function, with no return. If the parameter "quiet" is not provided, there's a printf and then the function returns, which in shell language means the printf return is carried over to the caller of _log_msg(). Problem is: checkfs() makes use of error log functions, which in the end rely on _log_msg(). If "quiet" is not supplied, and the filesystem is not set to fsck on boot (i.e., fsck is not included in the initrd), when the bad console is provided, an error message on checkfs_once() will eventually reach the printf on _log_msg(), causing checkfs_once() to "inherit" the bad return from printf. The big issue comes now: checkfs() runs a loop, and given in this corner case checkfs_once() returns an error state, the loop goes on forever, effectively preventing the boot. I consider this a bug specially because we had reports of cases in which the serial console was working...but after a (virtual) HW update the serial port changed, hence introducing such boot loop. I've proposed a really simple fix in the following merge request: salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/30 One could argue the problem is on checkfs() and we could fix there. I disagree, I think in no way an error log message should prevent boot or induce such errors by carrying over a bad result due to invalid console. Also, we could rethink printf returning error in case of bad console, but this is/will be a long-term discussion, no quick fix will outcome from there, so I'd rather have it fixed now if possible. Cheers, Guilherme [0] bugs.launchpad.net/bugs/1573095 -- System Information: Debian Release: stretch/sid Architecture: amd64 (x86_64) --- End Message --- --- Begin Message --- Source: initramfs-tools Source-Version: 0.138 Done: Ben Hutchings We believe that the bug you reported is fixed in the latest version of initramfs-tools, 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 960...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings (supplier of updated initramfs-tools 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: Fri, 11 Sep 2020 20:37:29 +0100 Source: initramfs-tools Architecture: source Version: 0.138 Distribution: unstable Urgency: medium Maintainer: Debian kernel team Changed-By: Ben Hutchings Closes: 857054 923400 955469 959768 960355 Changes: initramfs-tools (0.138) unstable; urgency=medium . [ Ben Hutchings ] * [0b034b4] docs/maintainer-notes.md: Delete the horizontal rules * [ba883cb] docs/maintainer-notes.md: Use Gitlab markup for table of contents * [5284a00] docs/maintainer-notes.md: Use Gitlab markup for definition table * [a469b7e] docs/maintainer-notes.md: Use archive.org URL for Daniel Baumann doc * [424260e] debian/control, docs/maintainer-notes.md: Use my @debian.org address * [181a35c] update-initramfs: Remove test for direct invocation from kernel package * [6ebe41b] Remove obsolete update-initramfs state in /var/lib/initramfs-tools * [2f2ad0d] hook-functions: copy_exec: Copy libgcc_s.so with any soversion up to 9 (Closes: #959768) * [0f24cc1] Add CI configuration for salsa.debian.org * [9877542] initramfs.conf: Delete "NFS Section" comment * [4309c3b] Add FSTYPE config parameter to allow overriding filesystem type detection (Closes: #923400) * [6300aa1] Change "panic" parameter handling to wor
Bug#960355: marked as done (Invalid serial console blocks system boot)
Your message dated Fri, 11 Sep 2020 20:36:04 + with message-id and subject line Bug#960355: fixed in initramfs-tools 0.138 has caused the Debian Bug report #960355, regarding Invalid serial console blocks system boot 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.) -- 960355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960355 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: initramfs-tools-core Version: 0.137 Putting a serial console on a non-existent/broken serial port via the last "console=" argument of the kernel command line causes the initrd to hang without completing the boot process. If the problematic serial console argument comes first in the kernel command line, the system boots without issues. ***To reproduce:*** 1. Check for a non-connected/disabled serial port. On the problematic system running [$] stty -a -F /dev/ttyS1 stty: /dev/ttyS1: Input/output error The serial ports are registered by the "serial8250" driver but are probably not wired to anything. 2. Boot with a kernel command line that puts serial console on a non-existent/broken serial port via last "console=" argument: console=tty0 console=ttyS1,115200n8 3. Check if system boots successfully I am using Debian GNU/Linux 11 (bullseye/testing), vanilla kernel 5.7-rc5. This issue was initially reported multiple times for Debian and Ubuntu to the systemd maintainers as: https://github.com/systemd/systemd/issues/15656 (for Ubuntu) https://github.com/systemd/systemd/issues/15783 (for Debian, duplicate) I am not sure if the _exact_ cause of both issues is the same, because I observed the problem on a very minimal system without console-setup or kbd. --- End Message --- --- Begin Message --- Source: initramfs-tools Source-Version: 0.138 Done: Ben Hutchings We believe that the bug you reported is fixed in the latest version of initramfs-tools, 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 960...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings (supplier of updated initramfs-tools 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: Fri, 11 Sep 2020 20:37:29 +0100 Source: initramfs-tools Architecture: source Version: 0.138 Distribution: unstable Urgency: medium Maintainer: Debian kernel team Changed-By: Ben Hutchings Closes: 857054 923400 955469 959768 960355 Changes: initramfs-tools (0.138) unstable; urgency=medium . [ Ben Hutchings ] * [0b034b4] docs/maintainer-notes.md: Delete the horizontal rules * [ba883cb] docs/maintainer-notes.md: Use Gitlab markup for table of contents * [5284a00] docs/maintainer-notes.md: Use Gitlab markup for definition table * [a469b7e] docs/maintainer-notes.md: Use archive.org URL for Daniel Baumann doc * [424260e] debian/control, docs/maintainer-notes.md: Use my @debian.org address * [181a35c] update-initramfs: Remove test for direct invocation from kernel package * [6ebe41b] Remove obsolete update-initramfs state in /var/lib/initramfs-tools * [2f2ad0d] hook-functions: copy_exec: Copy libgcc_s.so with any soversion up to 9 (Closes: #959768) * [0f24cc1] Add CI configuration for salsa.debian.org * [9877542] initramfs.conf: Delete "NFS Section" comment * [4309c3b] Add FSTYPE config parameter to allow overriding filesystem type detection (Closes: #923400) * [6300aa1] Change "panic" parameter handling to work more like the kernel * [90d64bd] debian/tests: Add common test preparation code * [3dd2984] debian/tests: Add basic test for amd64 using klibc and not busybox * [69240b1] debian/tests: Add basic test for amd64 using busybox * [3d834c8] debian/tests: Add basic tests for amd64 with only ata/virtio driver * [c14b760] debian/tests: Add test for separate /usr device * [6b3b361] debian/tests: Add test of the panic shell and parameter handling . [ Vagrant Cascadian ] * [482897b] hook-functions: Add modules needed for Pinebook LCD display. . [ Guilherme G. Piccoli ] * [c3cbf35] scripts/functions: Prevents pri
Bug#959768: marked as done (initramfs-tools: Does not account for different so versions of libgcc_s)
Your message dated Fri, 11 Sep 2020 20:36:04 + with message-id and subject line Bug#959768: fixed in initramfs-tools 0.138 has caused the Debian Bug report #959768, regarding initramfs-tools: Does not account for different so versions of libgcc_s 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.) -- 959768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959768 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: initramfs-tools Severity: important User: debian-h...@lists.debian.org Usertags: hppa,m68k Hello! In #950254 [1], a change was introduced to copy libgcc_s.so.1 into the initrd. Unfortunately, this change has introduced a regression on some architectures as the shared library has a different so version on these targets. amd64: root@z6:~> ls -l /lib/x86_64-linux-gnu/libgcc* -rw-r--r-- 1 root root 100736 May 2 14:09 /lib/x86_64-linux-gnu/libgcc_s.so.1 root@z6:~> hppa: root@phantom:~# ls -l /lib/hppa-linux-gnu/libgcc* -rw-r--r-- 1 root root 84412 Apr 18 09:56 /lib/hppa-linux-gnu/libgcc_s.so.4 root@phantom:~# m68k: root@elgar:~> ls -l /lib/m68k-linux-gnu/libgcc* -rw-r--r-- 1 root root 59116 Apr 18 11:56 /lib/m68k-linux-gnu/libgcc_s.so.2 root@elgar:~> Can you fix the change from #950254 to account for the different so versions of that library? Thanks, Adrian > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950254 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 --- End Message --- --- Begin Message --- Source: initramfs-tools Source-Version: 0.138 Done: Ben Hutchings We believe that the bug you reported is fixed in the latest version of initramfs-tools, 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 959...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings (supplier of updated initramfs-tools 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: Fri, 11 Sep 2020 20:37:29 +0100 Source: initramfs-tools Architecture: source Version: 0.138 Distribution: unstable Urgency: medium Maintainer: Debian kernel team Changed-By: Ben Hutchings Closes: 857054 923400 955469 959768 960355 Changes: initramfs-tools (0.138) unstable; urgency=medium . [ Ben Hutchings ] * [0b034b4] docs/maintainer-notes.md: Delete the horizontal rules * [ba883cb] docs/maintainer-notes.md: Use Gitlab markup for table of contents * [5284a00] docs/maintainer-notes.md: Use Gitlab markup for definition table * [a469b7e] docs/maintainer-notes.md: Use archive.org URL for Daniel Baumann doc * [424260e] debian/control, docs/maintainer-notes.md: Use my @debian.org address * [181a35c] update-initramfs: Remove test for direct invocation from kernel package * [6ebe41b] Remove obsolete update-initramfs state in /var/lib/initramfs-tools * [2f2ad0d] hook-functions: copy_exec: Copy libgcc_s.so with any soversion up to 9 (Closes: #959768) * [0f24cc1] Add CI configuration for salsa.debian.org * [9877542] initramfs.conf: Delete "NFS Section" comment * [4309c3b] Add FSTYPE config parameter to allow overriding filesystem type detection (Closes: #923400) * [6300aa1] Change "panic" parameter handling to work more like the kernel * [90d64bd] debian/tests: Add common test preparation code * [3dd2984] debian/tests: Add basic test for amd64 using klibc and not busybox * [69240b1] debian/tests: Add basic test for amd64 using busybox * [3d834c8] debian/tests: Add basic tests for amd64 with only ata/virtio driver * [c14b760] debian/tests: Add test for separate /usr device * [6b3b361] debian/tests: Add test of the panic shell and parameter handling . [ Vagrant Cascadian ] * [482897b] hook-functions: Add modules needed for Pinebook LCD display. . [ Guilherme G. Piccoli ] * [c3cbf35] scripts/functions: Prevents printf error carry over if wrong console is set (Closes: #960355) . [ Unit 193 ] * [3b82099] When overriding configured compressor, w
Bug#955469: marked as done (initramfs-tools-core: Enable zstandard support)
Your message dated Fri, 11 Sep 2020 20:36:04 + with message-id and subject line Bug#955469: fixed in initramfs-tools 0.138 has caused the Debian Bug report #955469, regarding initramfs-tools-core: Enable zstandard support 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.) -- 955469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955469 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: initramfs-tools-core Version: 0.136 Severity: wishlist Tags: patch Hello, there are Kernelpatches for zstandard initramfs support available for several years, and will hopefully accepted upstream soon. Please enable support for this compression. The patch should be simple enough, I chosen to try zstd as first decompressor because it supports a whole range of formats on debian. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages initramfs-tools-core depends on: ii coreutils8.30-3+b1 ii cpio 2.13+dfsg-2 ii e2fsprogs1.45.6-1 ii klibc-utils 2.0.7-1 ii kmod 27-2 ii logsave 1.45.6-1 ii udev 244.3-1 Versions of packages initramfs-tools-core recommends: ii busybox 1:1.30.1-4 ii pigz 2.4-1+b1 Versions of packages initramfs-tools-core suggests: ii bash-completion 1:2.10-1 -- Configuration Files: /etc/initramfs-tools/initramfs.conf changed [not included] -- no debconf information diff -burN initramfs-tools.org/conf/initramfs.conf initramfs-tools/conf/initramfs.conf --- initramfs-tools.org/conf/initramfs.conf 2019-02-06 00:55:47.0 +0100 +++ initramfs-tools/conf/initramfs.conf 2020-03-31 18:38:48.558687968 +0200 @@ -38,7 +38,7 @@ KEYMAP=n # -# COMPRESS: [ gzip | bzip2 | lz4 | lzma | lzop | xz ] +# COMPRESS: [ gzip | bzip2 | lz4 | lzma | lzop | zstd | xz ] # COMPRESS=gzip diff -burN initramfs-tools.org/mkinitramfs initramfs-tools/mkinitramfs --- initramfs-tools.org/mkinitramfs 2020-01-18 19:36:00.0 +0100 +++ initramfs-tools/mkinitramfs 2020-03-31 18:31:31.046107765 +0200 @@ -185,6 +185,7 @@ fi ;; lz4) compress="lz4 -9 -l" ;; +zstd) compress="zstd -19" ;; xz)compress="xz --check=crc32" # If we're not doing a reproducible build, enable multithreading test -z "${SOURCE_DATE_EPOCH}" && compress="$compress --threads=0" diff -burN initramfs-tools.org/unmkinitramfs initramfs-tools/unmkinitramfs --- initramfs-tools.org/unmkinitramfs 2019-07-31 16:25:58.0 +0200 +++ initramfs-tools/unmkinitramfs 2020-03-31 18:36:36.821308275 +0200 @@ -29,7 +29,9 @@ dir="$2" shift 2 - if gzip -t "$archive" >/dev/null 2>&1 ; then + if zstd -q -c -t "$archive" >/dev/null 2>&1 ; then + zstd -q -c -d "$archive" + elif gzip -t "$archive" >/dev/null 2>&1 ; then gzip -c -d "$archive" elif xzcat -t "$archive" >/dev/null 2>&1 ; then xzcat "$archive" --- End Message --- --- Begin Message --- Source: initramfs-tools Source-Version: 0.138 Done: Ben Hutchings We believe that the bug you reported is fixed in the latest version of initramfs-tools, 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 955...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings (supplier of updated initramfs-tools 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: Fri, 11 Sep 2020 20:37:29 +0100 Source: initramfs-tools Architecture: source Version: 0.138 Distribution: unstable Urgency: medium Maintainer: Debian kernel team Changed-By: Ben Hutchings Closes: 857054 923400 955469 959768 960355 Changes: initramfs-tools (0.138) unstable; urgency=medium . [ Ben Hutchings ] * [0b034b4] docs/maintainer-notes.md: Delete the horizontal rules * [ba883cb] docs/m
Processing of initramfs-tools_0.138_source.changes
initramfs-tools_0.138_source.changes uploaded successfully to localhost along with the files: initramfs-tools_0.138.dsc initramfs-tools_0.138.tar.xz initramfs-tools_0.138_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#857055: marked as done (Kernel installation should include list of firmware for built-in drivers)
Your message dated Fri, 11 Sep 2020 20:35:04 +0100 with message-id <74499be4660a537152fc2358e12bbc2c319f4e98.ca...@decadent.org.uk> and subject line Re: Bug#857054: initramfs-tools: Firmware for builtin kernel modules not included in initramfs has caused the Debian Bug report #857055, regarding Kernel installation should include list of firmware for built-in drivers 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.) -- 857055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857055 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: initramfs-tools Version: 0.120+deb8u3 Severity: normal Hi, I am using MODULES=netboot in combination with a custom kernel. This kernel has its network driver bnx2x built in: $ grep BNX2X= /boot/config-$version CONFIG_BNX2X=y The required firmware blobs are not included in the generated initramfs even when specifying bnx2x in /etc/initramfs-tools/modules, because manual_add_modules() from hook-functions does following: $ modprobe --all --ignore-install --quiet --show-depends bnx2x builtin bnx2x $ $ modinfo -k $version -F firmware bnx2x modinfo: ERROR: Module bnx2x not found. I wrote a hook function as workaround: $ cat /etc/initramfs-tools/hooks/fix-missing-firmware #!/bin/sh PREREQ="" prereqs() { echo "$PREREQ" } case $1 in # get pre-requisites prereqs) prereqs exit 0 ;; esac . /usr/share/initramfs-tools/hook-functions for file in /lib/firmware/bnx2x/*; do if test -e $file; then copy_exec $file fi done -- Benjamin Drung System Developer Debian & Ubuntu Developer ProfitBricks GmbH Greifswalder Str. 207 D - 10405 Berlin Email: benjamin.dr...@profitbricks.com URL: http://www.profitbricks.com Sitz der Gesellschaft: Berlin. Registergericht: Amtsgericht Charlottenburg, HRB 125506B. Geschäftsführer: Andreas Gauger, Achim Weiss. --- End Message --- --- Begin Message --- Version: 5.4.13-1 On Tue, 07 Mar 2017 15:35:56 + Ben Hutchings wrote: > Control: clone -1 -2 > Control: reassign -2 src:linux 4.9.13-1 > Control: retitle -2 Kernel installation should include list of firmware for > built-in drivers > Control: block -1 with -2 > Control: found -1 0.120 > Control: found -1 0.127 > > initramfs-tools will not keep its own lists of driver/firmware > dependencies; that is not maintainable. This information has to be > carried by the drivers themselves. > > In the case of built-in drivers, unfortunately, that information is > currently discarded at kernel build time. This was fixed upstream in 5.2, though our signed kernel packages didn't include the extra file until version 5.4.13-1. Jann Horn contributed a patch for initramfs-tools to use this information, so that bug will be fixed soon. Ben. -- Ben Hutchings Never put off till tomorrow what you can avoid all together. signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#878332: linux > 4.11: Raspberry pi 2 hangs at boot with lpae kernel
On 10.09.20 at 18:34, Gunnar Wolf wrote: > At the time of my bug report, I had not tested it yet. I checked right > now, downloading an image from raspi.debian.net, and installing the > -lpae kernel, I can confirm it boots correctly all the way to: > > root@rpi2-20200910:~# uname -a > Linux rpi2-20200910 4.19.0-10-armmp-lpae #1 SMP Debian 4.19.132-1 > (2020-07-24) armv7l GNU/Linux Thanks again for testing :-) signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#970011: linux: missing build dependency on kernel-wedge in stage1 build
Processing control commands: > tag -1 pending Bug #970011 [src:linux] linux: missing build dependency on kernel-wedge in stage1 build Added tag(s) pending. -- 970011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970011 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#970011: linux: missing build dependency on kernel-wedge in stage1 build
Control: tag -1 pending On Thu, 2020-09-10 at 06:59 +0200, Helmut Grohne wrote: > Source: linux > Version: 5.8.7-1 > Severity: important > User: helm...@debian.org > Usertags: rebootstrap > > Hi, > > I'm run into a bootstrap failure caused by linux: > https://jenkins.debian.net/job/rebootstrap_hppa_gcc10/9/ > > dh_prep > > dh_prep: warning: All requested packages have been excluded (e.g. via a > > Build-Profile or due to architecture restrictions). > > kernel-wedge install-files 5.8.0-1 > > bash: kernel-wedge: command not found > > make[2]: Leaving directory '/tmp/buildd/linux/linux-5.8.7' > > make[2]: *** [debian/rules.real:573: install-udeb_hppa] Error 127 > > make[1]: Leaving directory '/tmp/buildd/linux/linux-5.8.7' > > make[1]: *** [debian/rules.gen:89: binary-arch_hppa] Error 2 > > make: *** [debian/rules:43: binary-arch] Error 2 > > dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit > > status 2 > > What we see here is that kernel-wedge is not found while cross building > linux with the stage1 profile for hppa. This seems to be a recent thing. > It used to work earlier. I'm not sure yet, how many other architectures > are affected. This is specific to hppa. It recently gained transitional metapackages with no build-profiles set, and that made the condition here true: install-udeb_$(ARCH): # Logically we should check for %-di here, but that would break test builds ifneq (,$(filter linux-image-%,$(packages_enabled))) ... endif endif # enabled > A kernel-wedge dependency is there, but it is tagged . That > used to be true. It should still be true; there is no reason to run kernel-wedge, and it would fail if it was installed anyway. [...] > While looking into linux' build profiles I was wondering whether we > still need stage1. linux gained a number of functional profiles > including pkg.linux.nokernel, pkg.linux.notools and pkg.linux.nosource. > Their combination does not exactly reproduce stage1, but it is close. > I'm wondering whether we can simply switch any stage1 user to using the > combination of these three and be done. I haven't tried whether this > actually works yet, but I believe it is feasible and you get the idea. I think that would be more fragile than the clearly defined stage1. Ben. -- Ben Hutchings Never put off till tomorrow what you can avoid all together. signature.asc Description: This is a digitally signed message part
linux_5.9~rc4-1~exp1_source.changes is NEW
binary:acpi-modules-5.9.0-rc4-686-di is NEW. binary:acpi-modules-5.9.0-rc4-686-pae-di is NEW. binary:acpi-modules-5.9.0-rc4-amd64-di is NEW. binary:affs-modules-5.9.0-rc4-4kc-malta-di is NEW. binary:affs-modules-5.9.0-rc4-5kc-malta-di is NEW. binary:affs-modules-5.9.0-rc4-loongson-3-di is NEW. binary:affs-modules-5.9.0-rc4-octeon-di is NEW. binary:ata-modules-5.9.0-rc4-4kc-malta-di is NEW. binary:ata-modules-5.9.0-rc4-5kc-malta-di is NEW. binary:ata-modules-5.9.0-rc4-686-di is NEW. binary:ata-modules-5.9.0-rc4-686-pae-di is NEW. binary:ata-modules-5.9.0-rc4-amd64-di is NEW. binary:ata-modules-5.9.0-rc4-arm64-di is NEW. binary:ata-modules-5.9.0-rc4-armmp-di is NEW. binary:ata-modules-5.9.0-rc4-loongson-3-di is NEW. binary:ata-modules-5.9.0-rc4-powerpc64le-di is NEW. binary:btrfs-modules-5.9.0-rc4-4kc-malta-di is NEW. binary:btrfs-modules-5.9.0-rc4-5kc-malta-di is NEW. binary:btrfs-modules-5.9.0-rc4-686-di is NEW. binary:btrfs-modules-5.9.0-rc4-686-pae-di is NEW. binary:btrfs-modules-5.9.0-rc4-amd64-di is NEW. binary:btrfs-modules-5.9.0-rc4-arm64-di is NEW. binary:btrfs-modules-5.9.0-rc4-armmp-di is NEW. binary:btrfs-modules-5.9.0-rc4-loongson-3-di is NEW. binary:btrfs-modules-5.9.0-rc4-marvell-di is NEW. binary:btrfs-modules-5.9.0-rc4-octeon-di is NEW. binary:btrfs-modules-5.9.0-rc4-powerpc64le-di is NEW. binary:btrfs-modules-5.9.0-rc4-s390x-di is NEW. binary:cdrom-core-modules-5.9.0-rc4-4kc-malta-di is NEW. binary:cdrom-core-modules-5.9.0-rc4-5kc-malta-di is NEW. binary:cdrom-core-modules-5.9.0-rc4-686-di is NEW. binary:cdrom-core-modules-5.9.0-rc4-686-pae-di is NEW. binary:cdrom-core-modules-5.9.0-rc4-amd64-di is NEW. binary:cdrom-core-modules-5.9.0-rc4-arm64-di is NEW. binary:cdrom-core-modules-5.9.0-rc4-armmp-di is NEW. binary:cdrom-core-modules-5.9.0-rc4-loongson-3-di is NEW. binary:cdrom-core-modules-5.9.0-rc4-marvell-di is NEW. binary:cdrom-core-modules-5.9.0-rc4-octeon-di is NEW. binary:cdrom-core-modules-5.9.0-rc4-powerpc64le-di is NEW. binary:cdrom-core-modules-5.9.0-rc4-s390x-di is NEW. binary:crc-modules-5.9.0-rc4-4kc-malta-di is NEW. binary:crc-modules-5.9.0-rc4-5kc-malta-di is NEW. binary:crc-modules-5.9.0-rc4-686-di is NEW. binary:crc-modules-5.9.0-rc4-686-pae-di is NEW. binary:crc-modules-5.9.0-rc4-amd64-di is NEW. binary:crc-modules-5.9.0-rc4-arm64-di is NEW. binary:crc-modules-5.9.0-rc4-armmp-di is NEW. binary:crc-modules-5.9.0-rc4-loongson-3-di is NEW. binary:crc-modules-5.9.0-rc4-marvell-di is NEW. binary:crc-modules-5.9.0-rc4-octeon-di is NEW. binary:crc-modules-5.9.0-rc4-powerpc64le-di is NEW. binary:crc-modules-5.9.0-rc4-s390x-di is NEW. binary:crypto-dm-modules-5.9.0-rc4-4kc-malta-di is NEW. binary:crypto-dm-modules-5.9.0-rc4-5kc-malta-di is NEW. binary:crypto-dm-modules-5.9.0-rc4-686-di is NEW. binary:crypto-dm-modules-5.9.0-rc4-686-pae-di is NEW. binary:crypto-dm-modules-5.9.0-rc4-amd64-di is NEW. binary:crypto-dm-modules-5.9.0-rc4-arm64-di is NEW. binary:crypto-dm-modules-5.9.0-rc4-armmp-di is NEW. binary:crypto-dm-modules-5.9.0-rc4-loongson-3-di is NEW. binary:crypto-dm-modules-5.9.0-rc4-marvell-di is NEW. binary:crypto-dm-modules-5.9.0-rc4-octeon-di is NEW. binary:crypto-dm-modules-5.9.0-rc4-powerpc64le-di is NEW. binary:crypto-dm-modules-5.9.0-rc4-s390x-di is NEW. binary:crypto-modules-5.9.0-rc4-4kc-malta-di is NEW. binary:crypto-modules-5.9.0-rc4-5kc-malta-di is NEW. binary:crypto-modules-5.9.0-rc4-686-di is NEW. binary:crypto-modules-5.9.0-rc4-686-pae-di is NEW. binary:crypto-modules-5.9.0-rc4-amd64-di is NEW. binary:crypto-modules-5.9.0-rc4-arm64-di is NEW. binary:crypto-modules-5.9.0-rc4-armmp-di is NEW. binary:crypto-modules-5.9.0-rc4-loongson-3-di is NEW. binary:crypto-modules-5.9.0-rc4-marvell-di is NEW. binary:crypto-modules-5.9.0-rc4-octeon-di is NEW. binary:crypto-modules-5.9.0-rc4-powerpc64le-di is NEW. binary:crypto-modules-5.9.0-rc4-s390x-di is NEW. binary:dasd-extra-modules-5.9.0-rc4-s390x-di is NEW. binary:dasd-modules-5.9.0-rc4-s390x-di is NEW. binary:efi-modules-5.9.0-rc4-686-di is NEW. binary:efi-modules-5.9.0-rc4-686-pae-di is NEW. binary:efi-modules-5.9.0-rc4-amd64-di is NEW. binary:efi-modules-5.9.0-rc4-arm64-di is NEW. binary:efi-modules-5.9.0-rc4-armmp-di is NEW. binary:event-modules-5.9.0-rc4-4kc-malta-di is NEW. binary:event-modules-5.9.0-rc4-5kc-malta-di is NEW. binary:event-modules-5.9.0-rc4-686-di is NEW. binary:event-modules-5.9.0-rc4-686-pae-di is NEW. binary:event-modules-5.9.0-rc4-amd64-di is NEW. binary:event-modules-5.9.0-rc4-arm64-di is NEW. binary:event-modules-5.9.0-rc4-armmp-di is NEW. binary:event-modules-5.9.0-rc4-loongson-3-di is NEW. binary:event-modules-5.9.0-rc4-marvell-di is NEW. binary:event-modules-5.9.0-rc4-octeon-di is NEW. binary:event-modules-5.9.0-rc4-powerpc64le-di is NEW. binary:ext4-modules-5.9.0-rc4-4kc-malta-di is NEW. binary:ext4-modules-5.9.0-rc4-5kc-malta-di is NEW. binary:ext4-modules-5.9.0-rc4-686-di is NEW. binary:ext4-modules-5.9.0-rc4-686-pae-di is NEW. binary:ext4-modules-5.9.0-rc4-amd64-di is NEW. binary:ext4-mo
Processing of linux_5.9~rc4-1~exp1_source.changes
linux_5.9~rc4-1~exp1_source.changes uploaded successfully to localhost along with the files: linux_5.9~rc4-1~exp1.dsc linux_5.9~rc4.orig.tar.xz linux_5.9~rc4-1~exp1.debian.tar.xz linux_5.9~rc4-1~exp1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#968567: linux-image-4.19.0-10-amd64: kernel failure when writing on a GFS2 partition
Hi Daniel, hi Nicolas, On Thu, Sep 10, 2020 at 04:47:20AM +, Craig, Daniel (CASS, Marsfield) wrote: > Hi, > > I can confirm the existence of this CPU soft-lock bug with gfs2. > > I won't worry about reproducing the kernel bug message, but I have > done a bit of digging and if I revert the following commit, added in > the 4.19.130 release then this fixes issue for me. > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-4.19.y&id=c91cffd0fd010c06d67f3a9a528b858ce28c60fb > > Note that the problem is still present in the latest upstream > release in the 4.19 series (4.19.144) > > I've reported this bug in the kernel bugzilla, referenced here: > > https://bugzilla.kernel.org/show_bug.cgi?id=209217 Upstream did had a look at this see (you both were CC'ed on that thread though) the thread starting at https://lore.kernel.org/stable/20200910194319.GA131386@eldamar.local/ and suggested that upstream commit cbcc89b630447ec7836aa2b9242d9bb1725f5a61 is definitely needed. Would it be possible for you to test a build with that commit added on top? (Note the patch would need a slight refresh when applying on top of 4.19.144 for context changes). https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s4.2.2 explains how to test a single patch on top of the packaging, or you can try 4.19.144 with the cherry-picked commit. That would be much appreciated. Regards, Salvatore
Bug#966846: Kernel panic (4.19.0-10): RIP __cgroup_bpf_run_filter_skb
Hi Sébastien, On Fri, Sep 11, 2020 at 11:41:16AM +0200, Sébastien NOBILI wrote: > Hi, > > More than a week after, no problem with this build, working fine > 24/7. Thanks for confirming that. We are planning to rebase the version for the next point release and so will contain the fix. Regards, Salvatore
Bug#969961: marked as done (firmware-amd-graphics: amdgpu requires firmware installed even it already has been installed)
Your message dated Fri, 11 Sep 2020 13:10:42 +0200 with message-id <2020091042.ga1285...@photino.stro.at> and subject line Re: Bug#969961: firmware-amd-graphics: amdgpu requires firmware installed even it already has been installed has caused the Debian Bug report #969961, regarding firmware-amd-graphics: amdgpu requires firmware installed even it already has been installed 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.) -- 969961: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969961 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: firmware-amd-graphics Version: 20200817-1 Severity: important Dear Maintainer, * What led up to the situation? None, just boot up. * What exactly did you do (or not do) that was effective (or ineffective)? 1. Go to tty2, login. Enter "sudo modprobe -r amdgpu" 2. Then, Enter "sudo modprobe -i amdgpu" * What was the outcome of this action? None graphics shows up..Startx failed too. * What outcome did you expect instead? No error shows and graphics shows up. My inxi -xx -GSC shows: System:Host: XQQY-debian Kernel: 5.7.0-3-amd64 x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: KDE Plasma 5.17.5 tk: Qt 5.14.2 wm: kwin_x11 dm: SDDM Distro: Debian GNU/Linux bullseye/sid CPU: Info: 6-Core model: AMD Ryzen 5 3600 bits: 64 type: MT MCP arch: Zen 2 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 94790 Speed: 3950 MHz min/max: 2200/3950 MHz Core speeds (MHz): 1: 3949 2: 3938 3: 3949 4: 3949 5: 3950 6: 3949 7: 3950 8: 3949 9: 3940 10: 3933 11: 3951 12: 3949 Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] vendor: XFX Pine driver: amdgpu v: kernel bus ID: 08:00.0 chip ID: 1002:731f Display: x11 server: X.Org 1.20.8 compositor: kwin_x11 driver: amdgpu FAILED: ati unloaded: fbdev,modesetting,radeon,vesa resolution: 1920x1080 s-dpi: 96 OpenGL: renderer: AMD Radeon RX 5600 XT (NAVI10 DRM 3.37.0 5.7.0-3-amd64 LLVM 10.0.1) v: 4.6 Mesa 20.1.7 direct render: Yes I have upload my log of this problem to https://pastebin.com/1h1cT4wB Also, I have marked what happen when I type "sudo modprobe -r amdgpu" On line 1592 and "sudo modprobe -i amdgpu" on line 1638 -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.7.0-3-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), LANGUAGE=zh_CN:zh_TW Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled firmware-amd-graphics depends on no packages. firmware-amd-graphics recommends no packages. Versions of packages firmware-amd-graphics suggests: ii initramfs-tools 0.137 -- no debconf information --- End Message --- --- Begin Message --- Version: 5.8.7-1 done > > Yes, as I temply add unstable source and upgraded to Linux-image 5.8.0-1- > amd64. It seems fixed. Thanks a lot. Thank you for your report and information that linux 5.8.7-1 fixes it! Concerning the newer microcode I'll see what I can do in the next weeks. -- maks signature.asc Description: PGP signature --- End Message ---
Bug#966846: Kernel panic (4.19.0-10): RIP __cgroup_bpf_run_filter_skb
Hi, More than a week after, no problem with this build, working fine 24/7. Sébastien
Processed: affects 968567
Processing commands for cont...@bugs.debian.org: > affects 968567 + release.debian.org Bug #968567 [src:linux] linux-image-4.19.0-10-amd64: kernel failure when writing on a GFS2 partition Added indication that 968567 affects release.debian.org > thanks Stopping processing here. Please contact me if you need assistance. -- 968567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968567 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964734: reopened
Reopened until the resolution is clarified upstream.
Processed: Re: tags 964734 reopen
Processing commands for cont...@bugs.debian.org: > reopen 964734 Bug #964734 {Done: Bernhard Turmann } [src:linux] linux-image-4.19.0-9-amd64: [bisected] i2c timeout loading module ddbridge Bug reopened Ignoring request to alter fixed versions of bug #964734 to the same values previously set > End of message, stopping processing here. Please contact me if you need assistance. -- 964734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964734 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems