Bug#969140: linux-image-5.7.0-0.bpo.2-amd64: Please enable CONFIG_F2FS_FS in the cloud image kernel
On 29/8/20 1:01 pm, Noah Meyerhans wrote: On Sat, Aug 29, 2020 at 11:43:21AM +1000, Hamish Moffatt wrote: Could you please enable CONFIG_F2FS_FS in the cloud kernel? [...] What makes you think f2fs will be commonly used in cloud deployments? I don't know that it will be, but as it supports encryption and compression and benchmarks shows it performs at least as well as ext4, I don't see why it couldn't be a good choice for virtual machines. It seems at least as useful in a cloud deployment as minix and hpfs which are included in this flavour. This sounds like a good argument for turning off minix and hpfs to me. ;) I thought you might say that :) Is F2FS usable as a Debian root filesystem? Does it support all the features (file capabilities and POSIX ACLs, for example) that are commonly used on Debian systems? The cloud team, for what it's worth, does not have any plans to switch from ext4 in the forseeable future. (We probably would not do so unless Debian made the change distro-wide.) That doesn't mean we shouldn't consider enabling it, but I'd like to see a clearer use case. My small amount of research into it (mostly reading wikipedia and a couple of the reference sources) suggests that it's most popular on phones and similar devices, not cloud instances. Do you see use cases involving manipulating filesystems for those type of devices in cloud VMs? Or something else? How are crypto keys handled for its encryption functionality? The cloud kernel is not expected to be useful for 100% of people, even in cloud environments. In cases where specific functionality is needed that isn't available in the cloud kernel, the generic kernel is available and I'd probably recommend that. I envisage using f2fs on cloud instances for their own storage, with the benefit of encryption and compression (without the performance penalty of eg ZFS). f2fs appears to be available in Clear Linux as the root file system since March (https://github.com/clearlinux/distribution/issues/1522, https://www.phoronix.com/scan.php?page=news_item=Clear-Linux-F2FS-Root-Option ). Debian is working on this too according to https://www.phoronix.com/scan.php?page=news_item=Debian-F2FS-Root-File-System . Crypto setup is handled with fscrypt just as per ext4. thanks Hamish
Bug#969140: linux-image-5.7.0-0.bpo.2-amd64: Please enable CONFIG_F2FS_FS in the cloud image kernel
On Fri, 2020-08-28 at 20:01 -0700, Noah Meyerhans wrote: > On Sat, Aug 29, 2020 at 11:43:21AM +1000, Hamish Moffatt wrote: > > > > Could you please enable CONFIG_F2FS_FS in the cloud kernel? > > > [...] > > > > > > What makes you think f2fs will be commonly used in cloud deployments? > > > > > I don't know that it will be, but as it supports encryption and compression > > and benchmarks shows it performs at least as well as ext4, I don't see why > > it couldn't be a good choice for virtual machines. It seems at least as > > useful in a cloud deployment as minix and hpfs which are included in this > > flavour. > > This sounds like a good argument for turning off minix and hpfs to me. > ;) [...] I agree with that; I didn't realise they were enabled. Ben. -- Ben Hutchings Experience is what causes a person to make new mistakes instead of old ones. signature.asc Description: This is a digitally signed message part
Bug#969140: linux-image-5.7.0-0.bpo.2-amd64: Please enable CONFIG_F2FS_FS in the cloud image kernel
On Sat, Aug 29, 2020 at 11:43:21AM +1000, Hamish Moffatt wrote: > > > Could you please enable CONFIG_F2FS_FS in the cloud kernel? > > [...] > > > > What makes you think f2fs will be commonly used in cloud deployments? > > > I don't know that it will be, but as it supports encryption and compression > and benchmarks shows it performs at least as well as ext4, I don't see why > it couldn't be a good choice for virtual machines. It seems at least as > useful in a cloud deployment as minix and hpfs which are included in this > flavour. This sounds like a good argument for turning off minix and hpfs to me. ;) Is F2FS usable as a Debian root filesystem? Does it support all the features (file capabilities and POSIX ACLs, for example) that are commonly used on Debian systems? The cloud team, for what it's worth, does not have any plans to switch from ext4 in the forseeable future. (We probably would not do so unless Debian made the change distro-wide.) That doesn't mean we shouldn't consider enabling it, but I'd like to see a clearer use case. My small amount of research into it (mostly reading wikipedia and a couple of the reference sources) suggests that it's most popular on phones and similar devices, not cloud instances. Do you see use cases involving manipulating filesystems for those type of devices in cloud VMs? Or something else? How are crypto keys handled for its encryption functionality? The cloud kernel is not expected to be useful for 100% of people, even in cloud environments. In cases where specific functionality is needed that isn't available in the cloud kernel, the generic kernel is available and I'd probably recommend that. noah
Bug#969140: linux-image-5.7.0-0.bpo.2-amd64: Please enable CONFIG_F2FS_FS in the cloud image kernel
On 29/8/20 7:41 am, Ben Hutchings wrote: Control: tag -1 moreinfo On Fri, 2020-08-28 at 14:43 +0800, Hamish Moffatt wrote: Package: src:linux Version: 5.7.10-1~bpo10+1 Severity: wishlist Hi, Could you please enable CONFIG_F2FS_FS in the cloud kernel? [...] What makes you think f2fs will be commonly used in cloud deployments? I don't know that it will be, but as it supports encryption and compression and benchmarks shows it performs at least as well as ext4, I don't see why it couldn't be a good choice for virtual machines. It seems at least as useful in a cloud deployment as minix and hpfs which are included in this flavour. thanks Hamish
Bug#969140: linux-image-5.7.0-0.bpo.2-amd64: Please enable CONFIG_F2FS_FS in the cloud image kernel
Control: tag -1 moreinfo On Fri, 2020-08-28 at 14:43 +0800, Hamish Moffatt wrote: > Package: src:linux > Version: 5.7.10-1~bpo10+1 > Severity: wishlist > > Hi, > Could you please enable CONFIG_F2FS_FS in the cloud kernel? [...] What makes you think f2fs will be commonly used in cloud deployments? Ben. -- Ben Hutchings It is impossible to make anything foolproof because fools are so ingenious. signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#969140: linux-image-5.7.0-0.bpo.2-amd64: Please enable CONFIG_F2FS_FS in the cloud image kernel
Processing control commands: > tag -1 moreinfo Bug #969140 [src:linux] linux-image-5.7.0-0.bpo.2-amd64: Please enable CONFIG_F2FS_FS in the cloud image kernel Added tag(s) moreinfo. -- 969140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969140 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#885846: Recurring Atheros Driver Crash
Hi, how are you? Have you tested the firmware-ath9k-htc? And with this firmware it is quite possible that the problem you reported does not occur and I use and in stable version work fine and this one here is open source. I use TP Link board also and it is interesting to report this, although firmware is not a driver. Log here [ 18.124396] usb 1-1.4: ath9k_htc: Firmware ath9k_htc/htc_9271-1.dev.0.fw requested [ 18.124508] usbcore: registered new interface driver ath9k_htc [ 18.326598] usb 1-1.4: firmware: direct-loading firmware ath9k_htc/htc_9271-1.dev.0.fw [ 18.614208] usb 1-1.4: ath9k_htc: Transferred FW: ath9k_htc/htc_9271-1.dev.0.fw, size: 51008 [ 18.865805] ath9k_htc 1-1.4:1.0: ath9k_htc: HTC initialized with 33 credits [ 19.117742] ath9k_htc 1-1.4:1.0: ath9k_htc: FW Version: 1.4 [ 19.117746] ath9k_htc 1-1.4:1.0: FW RMW support: On [ 19.480962] ath9k_htc 1-1.4:1.0 wlxe894f6285298: renamed from wlan0 [ 6074.286308] Modules linked in: ctr ccm aufs(OE) devlink overlay uvcvideo arc4 videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev ath9k_htc ath9k_common snd_hda_codec_hdmi ath9k_hw snd_hda_codec_realtek ath mac80211 snd_hda_codec_generic cfg80211 media snd_hda_intel rfkill snd_hda_codec snd_hda_core snd_hwdep snd_pcm intel_powerclamp snd_timer coretemp snd intel_ips kvm_intel soundcore wmi_bmof mei_me iTCO_wdt kvm mei sg irqbypass iTCO_vendor_support intel_cstate intel_uncore joydev serio_raw evdev pcspkr pcc_cpufreq nf_log_ipv6 battery ac acpi_cpufreq ip6t_REJECT nf_reject_ipv6 xt_hl ip6_tables ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4 xt_LOG squashfs nft_limit xt_limit xt_addrtype xt_tcpudp loop xt_conntrack nft_compat nft_counter nf_conntrack_netbios_ns [ 6074.287109] Modules linked in: ctr ccm aufs(OE) devlink overlay uvcvideo arc4 videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev ath9k_htc ath9k_common snd_hda_codec_hdmi ath9k_hw snd_hda_codec_realtek ath mac80211 snd_hda_codec_generic cfg80211 media snd_hda_intel rfkill snd_hda_codec snd_hda_core snd_hwdep snd_pcm intel_powerclamp snd_timer coretemp snd intel_ips kvm_intel soundcore wmi_bmof mei_me iTCO_wdt kvm mei sg irqbypass iTCO_vendor_support intel_cstate intel_uncore joydev serio_raw evdev pcspkr pcc_cpufreq nf_log_ipv6 battery ac acpi_cpufreq ip6t_REJECT nf_reject_ipv6 xt_hl ip6_tables ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4 xt_LOG squashfs nft_limit xt_limit xt_addrtype xt_tcpudp loop xt_conntrack nft_compat nft_counter nf_conntrack_netbios_ns [ 6078.718836] Modules linked in: ctr ccm aufs(OE) devlink overlay uvcvideo arc4 videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev ath9k_htc ath9k_common snd_hda_codec_hdmi ath9k_hw snd_hda_codec_realtek ath mac80211 snd_hda_codec_generic cfg80211 media snd_hda_intel rfkill snd_hda_codec snd_hda_core snd_hwdep snd_pcm intel_powerclamp snd_timer coretemp snd intel_ips kvm_intel soundcore wmi_bmof mei_me iTCO_wdt kvm mei sg irqbypass iTCO_vendor_support intel_cstate intel_uncore joydev serio_raw evdev pcspkr pcc_cpufreq nf_log_ipv6 battery ac acpi_cpufreq ip6t_REJECT nf_reject_ipv6 xt_hl ip6_tables ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4 xt_LOG squashfs nft_limit xt_limit xt_addrtype xt_tcpudp loop xt_conntrack nft_compat nft_counter nf_conntrack_netbios_ns [10482.893784] Modules linked in: ctr ccm aufs(OE) devlink overlay uvcvideo arc4 videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev ath9k_htc ath9k_common snd_hda_codec_hdmi ath9k_hw snd_hda_codec_realtek ath mac80211 snd_hda_codec_generic cfg80211 media snd_hda_intel rfkill snd_hda_codec snd_hda_core snd_hwdep snd_pcm intel_powerclamp snd_timer coretemp snd intel_ips kvm_intel soundcore wmi_bmof mei_me iTCO_wdt kvm mei sg irqbypass iTCO_vendor_support intel_cstate intel_uncore joydev serio_raw evdev pcspkr pcc_cpufreq nf_log_ipv6 battery ac acpi_cpufreq ip6t_REJECT nf_reject_ipv6 xt_hl ip6_tables ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4 xt_LOG squashfs nft_limit xt_limit xt_addrtype xt_tcpudp loop xt_conntrack nft_compat nft_counter nf_conntrack_netbios_ns [11277.515444] Modules linked in: ctr ccm aufs(OE) devlink overlay uvcvideo arc4 videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev ath9k_htc ath9k_common snd_hda_codec_hdmi ath9k_hw snd_hda_codec_realtek ath mac80211 snd_hda_codec_generic cfg80211 media snd_hda_intel rfkill snd_hda_codec snd_hda_core snd_hwdep snd_pcm intel_powerclamp snd_timer coretemp snd intel_ips kvm_intel soundcore wmi_bmof mei_me iTCO_wdt kvm mei sg irqbypass iTCO_vendor_support intel_cstate intel_uncore joydev serio_raw evdev pcspkr pcc_cpufreq nf_log_ipv6 battery ac acpi_cpufreq ip6t_REJECT nf_reject_ipv6 xt_hl ip6_tables ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4 xt_LOG squashfs nft_limit xt_limit xt_addrtype xt_tcpudp loop xt_conntrack nft_compat nft_counter nf_conntrack_netbios_ns
Bug#885846: Recurring Atheros Driver Crash
Package: firmware-atheros
Version: 20190114-2
Followup-For: Bug #885846
Dear Maintainer,
I am seeing a similar crash as reported in bug 885846, using wireless driver
ATH9k with a TP-Link TL-WN851ND. The system freezes during moderate to high
wifi activity, such as streaming or running speedtest utilities, and is very
repeatable. At best, the system requires a hard reset. At worst, the crash
corrupts the BIOS, forcing BIOS reconfiguration. This issue affects distros
that use kernels common to Ubuntu 20.04, Mint 20/LMDE, etc. It does not occur
with older distros (e.g. Mint 17, Ubuntu 18.04 and its derivatives), or with
Windows.
Using modprobe I attempted to replace the ATH driver package provided with Mint
LMDE/Ubuntu 20 with that from Mint 17, however the older driver package is
apparently incompatible with the new kernel(s) and failed to load. I also
attempted to replace the ATH9k driver with ndiswrapper and the 64 bit driver
provided in Windows XP, but modprobe would hang when attempting to load
ndiswrapper. I also disabled wireless N in both the adapter settings, and the
router itself, to slow the data rate (i.e. I ran the adapter in "Legacy" mode).
The system still crashes; it just takes a while longer. Likewise, the crash
occurs whether security is enabled or disabled, and does not appear related to
any other hardware conflicts (the crash occurs whether using Nouveau or Nvidia
drivers, plus the wireless adapter is only device installed in a PCI slot).
-- System Information:
Debian Release: 10.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-10-amd64 (SMP w/6 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
firmware-atheros depends on no packages.
firmware-atheros recommends no packages.
Versions of packages firmware-atheros suggests:
ii initramfs-tools 0.133+deb10u1
-- no debconf information
*** /mnt/Storage/common files/ath9k/ath9k wireless driver crashing Mint 20 et
al.txt
Problem:
The ath9k wireless adapter driver appears to be "broken". Affects Mint 20
Cinnamon & LMDE, Ubuntu & Xubuntu 20.04.0 &.1 (I believe they all use the
latest kernels). It is NOT "broken" when using Mint 17.3 or Windows 7. (Adapter
make and model: TP-Link TL-WN851nd)
The symptoms:
When running speedtest utils (speedtest.net, xfinityspeedtest.org, etc) OR
streaming audio OR video (YouTubeTV) in Chrome OR Firefox while connected to
wifi, the mouse and keyboard will freeze, plus an audible static ("white
noise") will often come from the speakers. Sometimes speedtest or whatever was
being streamed at the time will continue to run for several seconds, even
though the keyboard and mouse are frozen. Othertimes, everything freezes at the
same time. At best it is necessary to perform a hard shutdown and reboot. At
worst, the crash corrupts the BIOS (about 50% of the time...) and I have to
reconfigure the BIOS before I can use the PC, and/or the OS/boot configuration
will be corrupted and I have to use "Boot Repair" and/or restore a previously
saved backup image before the PC can be used. This problem has been 100%
repeatable.
What I have tried:
1) Updated the firmware-atheros to the newest version (20200619-1). The
wireless still froze.
2) Using "Network Settings" I disabled wireless N on the adapter PLUS I
disabled wireless N on my ASUS RT-AC66U_B1 router (i.e. I used 802.11b or
802.11g Legacy mode only), and re-ran speedtest, but the system still crashed.
The only difference was that it took longer; I presume due to the slower
download and upload speeds.
3) Booting from a live USB (both Mint 20 and LMDE), I connected to wifi and ran
speedtest. The system still crashed. (Booting the live USB in UEFI or Legacy
BIOS mode made no difference.)
4) I attempted to replace the ath9k driver that comes with Mint 20 with the
ath9k driver in Mint 17.3, but it appears that the drivers are signed in some
fashion, preventing older drivers from being used with the newer kernels.
5) Tweeking the wifi, proxy, IPv4, and IPv6 settings from their defaults made
no difference.
6) The system does not crash when both wired and wifi connections are enabled.
I presume this is because the wired connection is preferred (has "priority").
7) The output from "lspci -b -vvv" shows that mint 17.3 is using the same
driver name (ath9k) and interrupt as mint 20.04.
8) Although I have tested this issue many times, only once was a crash log
generated, and it was lost after a subsequent crash. Sorry...
9) Thinking the crash may be related to downloads only, I ran "testmy.net
/upload" to skip the download part of the speedtest, and the system still
crashed. (The problem ***may be*** related to
Processed: bug 966846 is forwarded to https://bugzilla.kernel.org/show_bug.cgi?id=208003
Processing commands for cont...@bugs.debian.org: > forwarded 966846 https://bugzilla.kernel.org/show_bug.cgi?id=208003 Bug #966846 [src:linux] Kernel panic (4.19.0-10): RIP __cgroup_bpf_run_filter_skb Bug #968625 [src:linux] Kernel null pointer deref in the TCP stack Changed Bug forwarded-to-address to 'https://bugzilla.kernel.org/show_bug.cgi?id=208003' from 'https://lore.kernel.org/netdev/20200702185256.17917-1-xiyou.wangc...@gmail.com/'. Changed Bug forwarded-to-address to 'https://bugzilla.kernel.org/show_bug.cgi?id=208003' from 'https://lore.kernel.org/netdev/20200702185256.17917-1-xiyou.wangc...@gmail.com/'. > thanks Stopping processing here. Please contact me if you need assistance. -- 966846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966846 968625: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968625 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
klibc_2.0.8-5_source.changes ACCEPTED into experimental
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 28 Aug 2020 17:41:47 +0100 Source: klibc Architecture: source Version: 2.0.8-5 Distribution: experimental Urgency: medium Maintainer: Debian Kernel Team Changed-By: Ben Hutchings Changes: klibc (2.0.8-5) experimental; urgency=medium . * alpha: Fix definitions of _NSIG and struct sigaction * ia64: Fix definition of struct sigaction Checksums-Sha1: 737d3b3f43abb2eb8f23fdd9fdd2354c0a90f3d1 2107 klibc_2.0.8-5.dsc 27d5824afbd4f434c05ce28e7a204662d581be87 21968 klibc_2.0.8-5.debian.tar.xz d6d5a602b3ac069549535d33bab2a4ca510db243 5914 klibc_2.0.8-5_source.buildinfo Checksums-Sha256: 9989a15891f52c215e7a0740e721b0c27316164b9201f1f497a572e1d36a6bce 2107 klibc_2.0.8-5.dsc 7d7d9659a51717e8f283872c6e57b2db3fd23440ef2f2fed106c0da1d752427f 21968 klibc_2.0.8-5.debian.tar.xz 52c187ceec4db1e6b335975f34a3738c4ffac20afe22dfa22028accf6a9e3f1b 5914 klibc_2.0.8-5_source.buildinfo Files: 3e0c0a76abb6917534e5be25918b8ab4 2107 libs optional klibc_2.0.8-5.dsc 834264adcd7a6d6d67d879745b0695c9 21968 libs optional klibc_2.0.8-5.debian.tar.xz d075209ffe47b0c913877a791bb011ca 5914 libs optional klibc_2.0.8-5_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEErCspvTSmr92z9o8157/I7JWGEQkFAl9JNnkACgkQ57/I7JWG EQlqWBAAxh96cjXITisUvGctDMkiHkmBulJzNzT+D91t6yBD0VRrB7F0K7YcRPqH 1iogCoanXJ86/oTx8DLMRw81SRkBSGZ9vVZ7Usc7fiJXtJHBPdsL1OCcbNQAXMpE +QQWui/P5UT+W8TeHgSvRv+iO/75L3EnGgUWRRKfO6pKEPxPIsu9nNZ+4Pt4dIlb jW+P5Q1pUwtcuIGE9BXSPG43ccCMiK3ERjhSQqyjMYZUB1+5Q7CbMav65H3C6AvR ZVpuMGTE/AaI9kkm37zlVMX0UTukAnDDz/wYGUwVo3V3FXZCB0mZx4lDTaFurJdY 0HlB4otPU4rjNeaginYOCVaOe62R2DjI6pVzV3SJa8Xb+QnMZfz0yH4D3k7yZoTl CHW6PIMUvjDo3/sV0ZnuI7NyWPA8tvdeP1lINVyJ6nCtmkRa6l/Rx1SlfbrCajY9 GuuAm17PvtJjrOq/6gEOgEpC09PMIWw0Of3xDgjwtpy8GzU5OM591Xm+lx4bPWpT zf70SOE3ZAQES9/eRbr3PIut7KuH12+8w/lWjAKp6c3NRiSK4/zeMjO7+qkTF3Du j1oxYFHeY6ay5xR9RY3TVut3F99T9PcODT8WVvlvzhXKekV5qJBJLB4e1pCe98cn qRTS+Aes60kvL1OTGuqwAZ0gUrR16cISsm1/rYPvY56bgfBcSDI= =4k8k -END PGP SIGNATURE- Thank you for your contribution to Debian.
Bug#969179: iwlwifi: firmware error results in extremely poor connection until reboot
Source: linux Version: 5.7.17-1 Severity: normal X-Debbugs-Cc: j...@joshtriplett.org I get errors like the following regularly, particularly when on video calls; as soon as the error happens, most or all packets stop going through, and the connection becomes extremely unreliable. Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: Queue 11 is active on fifo 1 and stuck for 1 ms. SW [126, 95] HW [126, 95] FH TRB=0x0c010b08d Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: Microcode SW error detected. Restarting 0x200. Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: Start IWL Error Log Dump: Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: Status: 0x0040, count: 6 Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: Loaded firmware version: 36.79ff3ccf.0 8265-36.ucode Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x0084 | NMI_INTERRUPT_UNKNOWN Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x22E0 | trm_hw_status0 Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x | trm_hw_status1 Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x000248FC | branchlink2 Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x0003A872 | interruptlink1 Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x083E | interruptlink2 Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x | data1 Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x0080 | data2 Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x0783 | data3 Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x2D800D81 | beacon time Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0xA808AA7D | tsf low Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x0078 | tsf hi Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x | time gp1 Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x346CA182 | time gp2 Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x0001 | uCode revision type Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x0024 | uCode version major Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x79FF3CCF | uCode version minor Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x0230 | hw version Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x00C89000 | board version Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x0A15001C | hcmd Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x000A | isr0 Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x0080 | isr1 Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x0800180A | isr2 Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x00401480 | isr3 Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x | isr4 Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x0B7E001C | last cmd Id Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x | wait_event Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0xCF5A | l2p_control Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x8020 | l2p_duration Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x0003 | l2p_mhvalid Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x00F7 | l2p_addr_match Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x000D | lmpm_pmg_sel Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x02052035 | timestamp Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x00341828 | flow_handler Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x | ADVANCED_SYSASSERT Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x | umac branchlink1 Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x | umac branchlink2 Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x | umac interruptlink1 Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x | umac interruptlink2 Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x | umac data1 Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x | umac data2 Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x | umac data3 Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x | umac major Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x | umac minor Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x | frame pointer Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x | stack pointer Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x | last host cmd Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x | isr status reg Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: Fseq Registers: Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x22BC1126 | FSEQ_ERROR_CODE Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x9E626500 | FSEQ_TOP_INIT_VERSION Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x118C2230 | FSEQ_CNVIO_INIT_VERSION Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0xA10B | FSEQ_OTP_VERSION Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x57DD1850 | FSEQ_TOP_CONTENT_VERSION Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0xC66901A4 | FSEQ_ALIVE_TOKEN Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0xEAC96D6C | FSEQ_CNVI_ID Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0xE4E57887 |
Processing of klibc_2.0.8-5_source.changes
klibc_2.0.8-5_source.changes uploaded successfully to localhost along with the files: klibc_2.0.8-5.dsc klibc_2.0.8-5.debian.tar.xz klibc_2.0.8-5_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Processed (with 2 errors): retitle
Processing commands for cont...@bugs.debian.org: > retitle 963689 Stuck at "pmac32_cpufreq" when booting on PMU based machines > (Apple powerbooks) Bug #963689 [src:linux] linux-image-5.6.0-2-powerpc: stuck at 'pmac32_cpufreq' when booting Changed Bug title to 'Stuck at "pmac32_cpufreq" when booting on PMU based machines (Apple powerbooks)' from 'linux-image-5.6.0-2-powerpc: stuck at 'pmac32_cpufreq' when booting'. > Thanks, Unknown command or malformed arguments to command. > Giuseppe Unknown command or malformed arguments to command. > End of message, stopping processing here. Please contact me if you need assistance. -- 963689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963689 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963689: Acknowledgement (linux-image-5.6.0-2-powerpc: stuck at 'pmac32_cpufreq' when booting)
Hello, it seems I found the problem as explained in the upstream bug I opened[1]. Waiting for a fix, a possibile workaround proposed by kernel developers is to unset CONFIG_VMAP_STACK. Is it possible to change this configuration option for powerpc (32bit) architecture? Thank you, Giuseppe [1]https://github.com/linuxppc/issues/issues/326
Processed: tagging 966846
Processing commands for cont...@bugs.debian.org: > tags 966846 + pending confirmed Bug #966846 [src:linux] Kernel panic (4.19.0-10): RIP __cgroup_bpf_run_filter_skb Bug #968625 [src:linux] Kernel null pointer deref in the TCP stack Added tag(s) confirmed and pending. Added tag(s) confirmed and pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 966846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966846 968625: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968625 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: forcibly merging 966846 968625
Processing commands for cont...@bugs.debian.org: > forcemerge 966846 968625 Bug #966846 [src:linux] Kernel panic (4.19.0-10): RIP __cgroup_bpf_run_filter_skb Bug #968625 [src:linux] Kernel null pointer deref in the TCP stack Set Bug forwarded-to-address to 'https://lore.kernel.org/netdev/20200702185256.17917-1-xiyou.wangc...@gmail.com/'. Severity set to 'important' from 'normal' Added indication that 968625 affects release.debian.org Marked as found in versions linux/4.19.131-1. Added tag(s) upstream and fixed-upstream. Bug #966846 [src:linux] Kernel panic (4.19.0-10): RIP __cgroup_bpf_run_filter_skb Marked as found in versions linux/4.19.132-1. Merged 966846 968625 > thanks Stopping processing here. Please contact me if you need assistance. -- 966846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966846 968625: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968625 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966703: linux-image-4.19.0-10-amd64: kworker process with permanent high CPU load
hi Dirk,
On Wed, Aug 12, 2020 at 05:53:57PM +0200, Dirk Kostrewa wrote:
> Hi Salvatore,
>
> I just found out, that if none of the two USB ports is connected, there are
> two kworker processes with permanently high CPU load, if one USB port is
> connected and the other not, there is one such kworker process, and if both
> USB ports are connected, there is no kworker process with high CPU load.
> I think, this supports your suspicion that these kworker processes are
> connected with the overcurrent condition for both USB ports that I also see
> in the dmesg output.
> What puzzles me, is that I've observed these oddly behaving kworker
> processes also with the 5.6 kernel that I've tried from the Buster Backports
> repository.
The kernel parameter variant did not work correctly as there are no
dynamic debug output afaics (the double quotes seem to placed in the
wrong place), please just try the setting at runtime instead:
# echo 'file drivers/usb/* +p;' > /sys/kernel/debug/dynamic_debug/control
What I was meaning is (and this is confirmed if you see the issue
issue as well with the more recent kernels), that the specified commit
actually uncovers the issue present possibly with the HW.
Similarly to you someone else, where in known case with faulty HW,
reported the following issue upstream:
https://lore.kernel.org/lkml/20200720083956.ga4...@dhcp22.suse.cz/
I would like to see if we can collect as much information as possible
and possibly crosscheck with upstream.
If build the kernel with the attached patch (that is with the commit
wich is supsected to uncover the issue), does then the issue goes
away?
You can folllow the quide in
https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s4.2.2
for the "simple patching and building" and quickly chekcing a patch.
Regards,
Salvatore
>From 61ca5460d93d1a60a9aee0e46d51ae126593fda2 Mon Sep 17 00:00:00 2001
From: Salvatore Bonaccorso
Date: Fri, 28 Aug 2020 16:31:04 +0200
Subject: [PATCH] Revert "xhci: prevent bus suspend if a roothub port detected
a over-current condition"
This reverts commit d3ee95dedd88ed3fcd4647e4a8e265acaf27b2f0.
---
drivers/usb/host/xhci-hub.c | 9 -
1 file changed, 9 deletions(-)
diff --git a/drivers/usb/host/xhci-hub.c b/drivers/usb/host/xhci-hub.c
index a58ef53e4ae1..eb4284696f25 100644
--- a/drivers/usb/host/xhci-hub.c
+++ b/drivers/usb/host/xhci-hub.c
@@ -1481,8 +1481,6 @@ int xhci_hub_status_data(struct usb_hcd *hcd, char *buf)
}
if ((temp & PORT_RC))
reset_change = true;
- if (temp & PORT_OC)
- status = 1;
}
if (!status && !reset_change) {
xhci_dbg(xhci, "%s: stopping port polling.\n", __func__);
@@ -1548,13 +1546,6 @@ int xhci_bus_suspend(struct usb_hcd *hcd)
port_index);
goto retry;
}
- /* bail out if port detected a over-current condition */
- if (t1 & PORT_OC) {
- bus_state->bus_suspended = 0;
- spin_unlock_irqrestore(>lock, flags);
- xhci_dbg(xhci, "Bus suspend bailout, port over-current detected\n");
- return -EBUSY;
- }
/* suspend ports in U0, or bail out for new connect changes */
if ((t1 & PORT_PE) && (t1 & PORT_PLS_MASK) == XDEV_U0) {
if ((t1 & PORT_CSC) && wake_enabled) {
--
2.28.0
Processed: forcibly merging 963868 969160
Processing commands for cont...@bugs.debian.org:
> forcemerge 963868 969160
Bug #963868 {Done: Salvatore Bonaccorso } [src:linux]
linux-image-amd64: 5.7.6 crash (maybe amdgpu and temperature related)
Bug #969160 {Done: Salvatore Bonaccorso } [src:linux]
linux-image-5.7.0-2-amd64: amdgpu_dm_atomic_commit_tail issue freezes X
Marked as found in versions linux/5.7.6-1.
Added tag(s) fixed-upstream.
Bug #963868 {Done: Salvatore Bonaccorso } [src:linux]
linux-image-amd64: 5.7.6 crash (maybe amdgpu and temperature related)
Marked as found in versions linux/5.7.10-1.
Merged 963868 969160
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
963868: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963868
969160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969160
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: closing 969160
Processing commands for cont...@bugs.debian.org: > close 969160 5.7.17-1 Bug #969160 [src:linux] linux-image-5.7.0-2-amd64: amdgpu_dm_atomic_commit_tail issue freezes X Marked as fixed in versions linux/5.7.17-1. Bug #969160 [src:linux] linux-image-5.7.0-2-amd64: amdgpu_dm_atomic_commit_tail issue freezes X Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 969160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969160 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#969160: linux-image-5.7.0-2-amd64: amdgpu_dm_atomic_commit_tail issue freezes X
Package: src:linux Version: 5.7.10-1 Severity: important amdgpu crashes leaving X unressponsible. This seems to be a race condition and is already fixed upstream for kernels 5.8.0, 5.7.13, 5.4.56 https://bugzilla.kernel.org/show_bug.cgi?id=207383 It is quite often reproducible by waking up the monitors after they have been switched off by the screensaver. I'm using a multi monitor setup with a 0a:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] (rev c4) -- Package-specific info: ** Version: Linux version 5.7.0-2-amd64 (debian-kernel@lists.debian.org) (gcc version 9.3.0 (Debian 9.3.0-16), GNU ld (GNU Binutils for Debian) 2.35) #1 SMP Debian 5.7.10-1 (2020-07-26) ** Command line: BOOT_IMAGE=/vmlinuz-5.7.0-2-amd64 root=UUID=70f13b00-5a54-4309-887a-333da8417dd7 ro acpi_enforce_resources=lax splash ** Tainted: W (512) * kernel issued warning ** Kernel log: Aug 26 17:26:38 localhost kernel: [12803.982534] show_signal_msg: 17 callbacks suppressed Aug 26 17:26:38 localhost kernel: [12803.982537] kscreenlocker_g[27883]: segfault at 58 ip 7fddb372a9e9 sp 7ffc4b806000 error 4 in libQt5Core.so.5.14.2[7fddb34e8000+2ef000] Aug 26 17:26:38 localhost kernel: [12803.982545] Code: 58 48 39 d0 0f 85 57 02 00 00 b8 01 00 00 00 e9 34 fd ff ff 48 8b 74 24 38 48 8b 46 08 48 85 c0 74 0d 48 8b 46 08 8b 74 24 40 <3b> 70 08 7c 32 48 8d 7c 24 60 e8 48 71 00 00 48 8b 7c 24 08 b8 01 Aug 26 17:26:39 localhost kernel: [12804.947817] [ cut here ] Aug 26 17:26:39 localhost kernel: [12804.947921] WARNING: CPU: 4 PID: 29465 at drivers/gpu/drm/amd/amdgpu/../display/dc/dcn20/dcn20_hwseq.c:109 dcn20_setup_gsl_group_as_lock+0x7f/0x200 [amdgpu] Aug 26 17:26:39 localhost kernel: [12804.947923] Modules linked in: fuse xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_counter nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink tun bridge stp llc binfmt_misc snd_hda_codec_realtek snd_hda_codec_generic amd64_edac_mod edac_mce_amd ledtrig_audio kvm_amd snd_hda_codec_hdmi kvm eeepc_wmi snd_hda_intel ax88179_178a asus_wmi snd_intel_dspcfg usbnet battery sparse_keymap irqbypass sg mii joydev snd_hda_codec rfkill snd_hda_core video pcspkr wmi_bmof snd_hwdep sp5100_tco snd_pcm k10temp watchdog snd_timer ccp snd rng_core soundcore evdev acpi_cpufreq ib_iser rdma_cm iw_cm ib_cm ib_core configfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nct6775 hwmon_vid r8169 realtek libphy parport_pc ppdev lp parport ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 dm_crypt dm_mod raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c crc32c_generic raid0 multipath Aug 26 17:26:39 localhost kernel: [12804.947953] linear radeon raid1 md_mod sr_mod cdrom hid_generic usbhid hid sd_mod amdgpu gpu_sched i2c_algo_bit ttm crc32_pclmul crc32c_intel drm_kms_helper ghash_clmulni_intel cec xhci_pci drm xhci_hcd ahci aesni_intel libahci libata libaes crypto_simd cryptd glue_helper usbcore nvme scsi_mod nvme_core i2c_piix4 t10_pi crc_t10dif crct10dif_generic mfd_core crct10dif_pclmul usb_common crct10dif_common wmi button Aug 26 17:26:39 localhost kernel: [12804.947972] CPU: 4 PID: 29465 Comm: kworker/u64:5 Not tainted 5.7.0-2-amd64 #1 Debian 5.7.10-1 Aug 26 17:26:39 localhost kernel: [12804.947974] Hardware name: System manufacturer System Product Name/TUF GAMING X570-PLUS, BIOS 1407 04/01/2020 Aug 26 17:26:39 localhost kernel: [12804.947984] Workqueue: events_unbound commit_work [drm_kms_helper] Aug 26 17:26:39 localhost kernel: [12804.948076] RIP: 0010:dcn20_setup_gsl_group_as_lock+0x7f/0x200 [amdgpu] Aug 26 17:26:39 localhost kernel: [12804.948078] Code: 84 d2 74 47 84 c0 75 26 48 8b 87 30 03 00 00 0f b6 80 70 02 00 00 a8 01 0f 84 dc 00 00 00 a8 02 74 55 a8 04 0f 84 f7 00 00 00 <0f> 0b 0f 0b 48 8b 44 24 28 65 48 33 04 25 28 00 00 00 0f 85 59 01 Aug 26 17:26:39 localhost kernel: [12804.948079] RSP: 0018:a67a4828fa48 EFLAGS: 00010202 Aug 26 17:26:39 localhost kernel: [12804.948081] RAX: 0007 RBX: 964871ce0b08 RCX: Aug 26 17:26:39 localhost kernel: [12804.948082] RDX: 0001 RSI: 964871ce0b08 RDI: 9649a8d7 Aug 26 17:26:39 localhost kernel: [12804.948083] RBP: 0001 R08: a67a4828fa44 R09: Aug 26 17:26:39 localhost kernel: [12804.948084] R10: R11: a67a4828fab4 R12: 0001 Aug 26 17:26:39 localhost kernel: [12804.948085] R13: 9649a8d7 R14: 9648b798 R15: 964927614400 Aug 26 17:26:39 localhost kernel: [12804.948087] FS: () GS:9649beb0() knlGS: Aug 26 17:26:39 localhost kernel: [12804.948088] CS: 0010 DS: ES: CR0: 80050033 Aug 26 17:26:39 localhost kernel: [12804.948089] CR2: 7fa2dc0289e0 CR3:
Bug#969139: linux-image-5.7.0-0.bpo.2-amd64: Please enable CONFIG_F2FS_FS_COMPRESSION
Package: src:linux Version: 5.7.10-1~bpo10+1 Severity: wishlist Hi, Could you please enable CONFIG_F2FS_FS_COMPRESSION in all builds? It is a new feature in 5.6 I believe. Hamish -- Package-specific info: ** Version: Linux version 5.7.0-0.bpo.2-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6), GNU ld (GNU Binutils for Debian) 2.31.1) #1 SMP Debian 5.7.10-1~bpo10+1 (2020-07-30) ** Command line: BOOT_IMAGE=/boot/vmlinuz-5.7.0-0.bpo.2-amd64 root=/dev/sda ro quiet nosplash console=tty1 console=ttyS0 ** Not tainted ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information sys_vendor: QEMU product_name: Standard PC (Q35 + ICH9, 2009) product_version: pc-q35-4.1 chassis_vendor: QEMU chassis_version: pc-q35-4.1 bios_vendor: SeaBIOS bios_version: rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org ** Loaded modules: f2fs crc32_generic cts sha512_ssse3 sha512_generic tun nf_log_ipv6 ip6t_REJECT nf_reject_ipv6 xt_hl ip6_tables ip6t_rt nf_log_ipv4 nf_log_common xt_LOG ipt_REJECT nf_reject_ipv4 nft_limit xt_limit bochs_drm crc32_pclmul drm_vram_helper xt_addrtype drm_ttm_helper ghash_clmulni_intel xt_tcpudp ttm drm_kms_helper xt_conntrack nft_compat cec aesni_intel nft_counter joydev drm libaes evdev crypto_simd cryptd iTCO_wdt glue_helper serio_raw iTCO_vendor_support watchdog sg qemu_fw_cfg button nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c nf_tables nfnetlink ecryptfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic sd_mod t10_pi crc_t10dif crct10dif_generic virtio_net net_failover failover ahci virtio_scsi libahci libata psmouse crct10dif_pclmul crct10dif_common scsi_mod crc32c_intel i2c_i801 lpc_ich virtio_pci mfd_core virtio_ring virtio ** PCI devices: not available ** USB devices: not available -- System Information: Debian Release: 10.5 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-0.bpo.2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-5.7.0-0.bpo.2-amd64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.133+deb10u1 ii kmod26-1 ii linux-base 4.6 Versions of packages linux-image-5.7.0-0.bpo.2-amd64 recommends: ii apparmor 2.13.2-10 ii firmware-linux-free 3.4 Versions of packages linux-image-5.7.0-0.bpo.2-amd64 suggests: pn debian-kernel-handbook ii grub-pc 2.02+dfsg1-20+deb10u2 pn linux-doc-5.7 Versions of packages linux-image-5.7.0-0.bpo.2-amd64 is related to: pn firmware-amd-graphics pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x pn firmware-brcm80211 pn firmware-cavium pn firmware-intel-sound pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv pn firmware-iwlwifi pn firmware-libertas pn firmware-linux-nonfree pn firmware-misc-nonfree pn firmware-myricom pn firmware-netxen pn firmware-qlogic pn firmware-realtek pn firmware-samsung pn firmware-siano pn firmware-ti-connectivity pn xen-hypervisor -- no debconf information -- debsums errors found: debsums: missing file /usr/share/doc/linux-image-5.7.0-0.bpo.2-amd64/changelog.gz (from linux-image-5.7.0-0.bpo.2-amd64 package) debsums: missing file /usr/share/doc/linux-image-5.7.0-0.bpo.2-amd64/copyright (from linux-image-5.7.0-0.bpo.2-amd64 package)
Bug#969140: linux-image-5.7.0-0.bpo.2-amd64: Please enable CONFIG_F2FS_FS in the cloud image kernel
Package: src:linux Version: 5.7.10-1~bpo10+1 Severity: wishlist Hi, Could you please enable CONFIG_F2FS_FS in the cloud kernel? thanks, Hamish -- Package-specific info: ** Version: Linux version 5.7.0-0.bpo.2-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6), GNU ld (GNU Binutils for Debian) 2.31.1) #1 SMP Debian 5.7.10-1~bpo10+1 (2020-07-30) ** Command line: BOOT_IMAGE=/boot/vmlinuz-5.7.0-0.bpo.2-amd64 root=/dev/sda ro quiet nosplash console=tty1 console=ttyS0 ** Not tainted ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information sys_vendor: QEMU product_name: Standard PC (Q35 + ICH9, 2009) product_version: pc-q35-4.1 chassis_vendor: QEMU chassis_version: pc-q35-4.1 bios_vendor: SeaBIOS bios_version: rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org ** Loaded modules: f2fs crc32_generic cts sha512_ssse3 sha512_generic tun nf_log_ipv6 ip6t_REJECT nf_reject_ipv6 xt_hl ip6_tables ip6t_rt nf_log_ipv4 nf_log_common xt_LOG ipt_REJECT nf_reject_ipv4 nft_limit xt_limit bochs_drm crc32_pclmul drm_vram_helper xt_addrtype drm_ttm_helper ghash_clmulni_intel xt_tcpudp ttm drm_kms_helper xt_conntrack nft_compat cec aesni_intel nft_counter joydev drm libaes evdev crypto_simd cryptd iTCO_wdt glue_helper serio_raw iTCO_vendor_support watchdog sg qemu_fw_cfg button nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c nf_tables nfnetlink ecryptfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic sd_mod t10_pi crc_t10dif crct10dif_generic virtio_net net_failover failover ahci virtio_scsi libahci libata psmouse crct10dif_pclmul crct10dif_common scsi_mod crc32c_intel i2c_i801 lpc_ich virtio_pci mfd_core virtio_ring virtio ** PCI devices: not available ** USB devices: not available -- System Information: Debian Release: 10.5 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-0.bpo.2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-5.7.0-0.bpo.2-amd64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.133+deb10u1 ii kmod26-1 ii linux-base 4.6 Versions of packages linux-image-5.7.0-0.bpo.2-amd64 recommends: ii apparmor 2.13.2-10 ii firmware-linux-free 3.4 Versions of packages linux-image-5.7.0-0.bpo.2-amd64 suggests: pn debian-kernel-handbook ii grub-pc 2.02+dfsg1-20+deb10u2 pn linux-doc-5.7 Versions of packages linux-image-5.7.0-0.bpo.2-amd64 is related to: pn firmware-amd-graphics pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x pn firmware-brcm80211 pn firmware-cavium pn firmware-intel-sound pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv pn firmware-iwlwifi pn firmware-libertas pn firmware-linux-nonfree pn firmware-misc-nonfree pn firmware-myricom pn firmware-netxen pn firmware-qlogic pn firmware-realtek pn firmware-samsung pn firmware-siano pn firmware-ti-connectivity pn xen-hypervisor -- no debconf information -- debsums errors found: debsums: missing file /usr/share/doc/linux-image-5.7.0-0.bpo.2-amd64/changelog.gz (from linux-image-5.7.0-0.bpo.2-amd64 package) debsums: missing file /usr/share/doc/linux-image-5.7.0-0.bpo.2-amd64/copyright (from linux-image-5.7.0-0.bpo.2-amd64 package)
