Processed: bug 925943 is forwarded to https://bugzilla.linux-nfs.org/show_bug.cgi?id=334
Processing commands for cont...@bugs.debian.org: > forwarded 925943 https://bugzilla.linux-nfs.org/show_bug.cgi?id=334 Bug #925943 [nfs-utils] nfs-common: nfsiostat crashes due to using reserved word 'list' as variable name Set Bug forwarded-to-address to 'https://bugzilla.linux-nfs.org/show_bug.cgi?id=334'. > thanks Stopping processing here. Please contact me if you need assistance. -- 925943: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925943 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 925943
Processing commands for cont...@bugs.debian.org: > tags 925943 + upstream fixed-upstream Bug #925943 [nfs-utils] nfs-common: nfsiostat crashes due to using reserved word 'list' as variable name Added tag(s) upstream and fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 925943: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925943 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 923398 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 923398 src:linux 4.9.144-3.1 Bug #923398 [linux-headers-4.9.0-8-amd64] In debian stretch: bind(2) port collision checking is wrong for IPv4 if IPv6 is checked first Bug reassigned from package 'linux-headers-4.9.0-8-amd64' to 'src:linux'. Ignoring request to alter found versions of bug #923398 to the same values previously set Ignoring request to alter fixed versions of bug #923398 to the same values previously set Bug #923398 [src:linux] In debian stretch: bind(2) port collision checking is wrong for IPv4 if IPv6 is checked first Marked as found in versions linux/4.9.144-3.1. > thanks Stopping processing here. Please contact me if you need assistance. -- 923398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923398 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: limit source to linux, tagging 923723
Processing commands for cont...@bugs.debian.org: > limit source linux Limiting to bugs with field 'source' containing at least one of 'linux' Limit currently set to 'source':'linux' > tags 923723 + pending Bug #923723 [src:linux] linux: amdgpu/radeon driver optimization is broken on ARM/arm64 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 923723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923723 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 919227
Processing commands for cont...@bugs.debian.org: > close 919227 5.0.2-1~exp1 Bug #919227 [src:linux] linux-image-4.19.0-1-amd64: acpi lid regression from stable to testing Marked as fixed in versions linux/5.0.2-1~exp1. Bug #919227 [src:linux] linux-image-4.19.0-1-amd64: acpi lid regression from stable to testing Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 919227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919227 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#926794: linux-image-4.19.0.0-bpo.4-amd64: Please enable FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER in kernel config
Hello Ben, as this does not have any direct impact on any other components I think it can be enabled independently. This is because the first write to the console bounds it to the FB and the output behavior works as usual. On other hand, I definitely agree with you that other components has to be updated as well in order to be possible to fully use this feature. At least, the screen must be captured prior the display driver is loaded and the Systemd runs the console initialization in order to be possible to restore the vendor logo displayed by EFI shell after mentioned tasks. Also, components such as Plymouth should be updated in order to be possible to use the “UEFI” theme. Unfortunately, the list of components can be more wide and I can’t even imagine the foll set of them. I asked to enable it independently because it currently prevents us from customization of the boot process while the standard Debian Kernel build is in use. We can do it only in case we recompile the Kernel on our own. It is not optimal for the productional environments. Regards, Frantisek > On 12 Apr 2019, at 22:17, Ben Hutchings wrote: > > On Wed, 10 Apr 2019 15:58:07 +0200 Frantisek Novak < > novak.franti...@atlas.cz> wrote: >> Package: linux-image-4.19.0.0-bpo.4-amd64 >> Version: linux-image-4.19.0-0-bpo.4-amd64 >> Severity: wishlist >> >> Dear Maintainer, >> >> please enable FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER in kernel > configuration to prevent clearing of the framebuffer when the console > starts during the boot. > > I tried it a few months back and I don't think we should do this in the > kernel in isolation. We would also need to make the boot loader silent > by default, and we might need to update themes as well. > > If you want this to happen, please propose those changes in the other > packages after the buster release. > > Ben. > > -- > Ben Hutchings > Hoare's Law of Large Problems: > Inside every large problem is a small problem struggling to get out. > >
Processed: closing 919498
Processing commands for cont...@bugs.debian.org: > close 919498 4.19.16-1 Bug #919498 [src:linux] linux-image-4.19.0-1-amd64: Fails to boot. Inactive (initramfs) prompt.'Gave up waiting for suspend/resume device' Marked as fixed in versions linux/4.19.16-1. Bug #919498 [src:linux] linux-image-4.19.0-1-amd64: Fails to boot. Inactive (initramfs) prompt.'Gave up waiting for suspend/resume device' Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 919498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919498 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 919290
Processing commands for cont...@bugs.debian.org: > tags 919290 + pending Bug #919290 [src:linux] SMB2_close_free: BUG: unable to handle kernel NULL pointer dereference at Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 919290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919290 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 915614
Processing commands for cont...@bugs.debian.org: > close 915614 4.19.12-1 Bug #915614 [src:linux] linux-image-4.18.0-3-amd64: Hard lockup under load on dual EPYC 7501 Supermicro H11DSi-NT Marked as fixed in versions linux/4.19.12-1. Bug #915614 [src:linux] linux-image-4.18.0-3-amd64: Hard lockup under load on dual EPYC 7501 Supermicro H11DSi-NT Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 915614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915614 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 910069, closing 910069
Processing commands for cont...@bugs.debian.org: > tags 910069 - moreinfo Bug #910069 [src:linux] linux-image-4.18.0-1-amd64: NVME quirk needed for Intel 760p + Thinkpad T480 Removed tag(s) moreinfo. > close 910069 Bug #910069 [src:linux] linux-image-4.18.0-1-amd64: NVME quirk needed for Intel 760p + Thinkpad T480 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 910069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910069 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 857912 in 1:1.3.4-2.5
Processing commands for cont...@bugs.debian.org: > found 857912 1:1.3.4-2.5 Bug #857912 [nfs-common] rpc-svcgssd.service: references wrong environment variable Bug #892654 [nfs-common] nfs-kernel-server: Mismatching [RPC]SVCGSSDOPTS defaults Marked as found in versions nfs-utils/1:1.3.4-2.5. Marked as found in versions nfs-utils/1:1.3.4-2.5. > thanks Stopping processing here. Please contact me if you need assistance. -- 857912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857912 892654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892654 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 892654 to nfs-common, forcibly merging 857912 892654, tagging 857912
Processing commands for cont...@bugs.debian.org: > reassign 892654 nfs-common Bug #892654 [nfs-kernel-server] nfs-kernel-server: Mismatching [RPC]SVCGSSDOPTS defaults Bug reassigned from package 'nfs-kernel-server' to 'nfs-common'. No longer marked as found in versions nfs-utils/1:1.3.4-2.1. Ignoring request to alter fixed versions of bug #892654 to the same values previously set > forcemerge 857912 892654 Bug #857912 [nfs-common] rpc-svcgssd.service: references wrong environment variable Bug #892654 [nfs-common] nfs-kernel-server: Mismatching [RPC]SVCGSSDOPTS defaults Marked as found in versions nfs-utils/1:1.3.4-2. Added tag(s) patch. Merged 857912 892654 > tags 857912 + patch Bug #857912 [nfs-common] rpc-svcgssd.service: references wrong environment variable Bug #892654 [nfs-common] nfs-kernel-server: Mismatching [RPC]SVCGSSDOPTS defaults Ignoring request to alter tags of bug #857912 to the same tags previously set Ignoring request to alter tags of bug #892654 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 857912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857912 892654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892654 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: limit source to linux, tagging 785065, tagging 884562
Processing commands for cont...@bugs.debian.org: > limit source linux Limiting to bugs with field 'source' containing at least one of 'linux' Limit currently set to 'source':'linux' > tags 785065 + pending Bug #785065 [src:linux] ppc64el kernel build requires multilib compiler Added tag(s) pending. > tags 884562 + pending Bug #884562 [src:linux] linux-image-4.9.0-4-armmp-lp: Enable CONFIG_SND_SOC_SPDIF for cubietruck spdif Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 785065: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785065 884562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884562 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 886049
Processing commands for cont...@bugs.debian.org: > tags 886049 + moreinfo Bug #886049 [src:linux] [linux-image-4.14.0-2-amd64] Function g_file_copy() from libglib2.0-0 hangs when copying small files from CIFS-Share. This is relevant for Thunar filemanager. Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 886049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886049 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#926967: Don't recommend irqbalance (was: Re: Handling irqbalance in virtual environments)
Package: src:linux Version: 4.19.28-2 Severity: important On Fri, Apr 12, 2019 at 09:10:32PM +0100, Ben Hutchings wrote: > On Fri, 2019-04-12 at 10:53 +0200, Bastian Blank wrote: > > It turns out we got again problems with irqbalance. > > > > It was added as recommends of the main image in 3.16, as it was reported > > that older kernels move all interrupts to CPU 0 without help.[1] > > > > In the meantime the kernel can do balancing on it's own. In 4.9, I've > > seen it working with aacraid, each queue gets hard pinned to it's own > > CPU from 0 to $NRCPUS. In 4.19 I've seen the same working properly with > > virtio-net. > > > > With 4.19, even on real hardware, where interrupts have an affinity for > > all cpus, each interrupt is actually delivered to different cpu. > > > > Random example for this, it even selects only one thread of each core: > > > > > 26:0000 92000 IR-PCI-MSI 3670017-edge > > > eno1-TxRx-0 > > > 27:00000 16700 IR-PCI-MSI 3670018-edge > > > eno1-TxRx-1 > > > 28:000000 4670 IR-PCI-MSI 3670019-edge > > > eno1-TxRx-2 > > > 29:0000000 454 IR-PCI-MSI 3670020-edge > > > eno1-TxRx-3 > > > > Now irqbalance comes to re-do the existing pinning, and the result is not > > longer correct but $RANDOM for the hard queue-to-cpu case of virtio. > > Then let's drop the recommendation. Okay. Regards, Bastian -- I'm a soldier, not a diplomat. I can only tell the truth. -- Kirk, "Errand of Mercy", stardate 3198.9
Processed: reassign 926926 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 926926 src:linux 4.19.28-2~bpo9+1 Bug #926926 [linux-image-4.19.0-0.bpo.4-amd64] thinkpad_acpi: Unable to use VGA port on Lenovo Docking station after boot Bug reassigned from package 'linux-image-4.19.0-0.bpo.4-amd64' to 'src:linux'. No longer marked as found in versions linux-signed-amd64/4.19.28+2~bpo9+1. Ignoring request to alter fixed versions of bug #926926 to the same values previously set Bug #926926 [src:linux] thinkpad_acpi: Unable to use VGA port on Lenovo Docking station after boot Marked as found in versions linux/4.19.28-2~bpo9+1. > thanks Stopping processing here. Please contact me if you need assistance. -- 926926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926926 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Re: question: what will happen to buster when kernel 4.19 goes out of life in Dec2020?
On Fri, 2019-04-12 at 15:51 +, Thierry Vilmart wrote: > question: > > What will happen to buster when kernel 4.19 goes out of life in > Dec2020? > > See EOL for 4.19. > https://www.kernel.org/category/releases.html This is quite likely to be extended to 6 years, as has happened with 4.4 and 4.9. The Civil Infrastructure Platform (CIP) is also maintaining a 4.19 branch and aims to do so for 10 years (but covering a limited feature set). > If buster debian 10 has to change the kernel to 5 in Dec 2020, it will > be untested. And it would be preferable to have kernel 5 before buster > is realeased during the testing phase. > > Or will you do your own patchsets on an out of life 4.19 kernel? If Greg K-H does not maintain 4.19 for long enough, the Debian kernel team would probably work with CIP on backporting important fixes. Ben. -- Ben Hutchings Hoare's Law of Large Problems: Inside every large problem is a small problem struggling to get out. signature.asc Description: This is a digitally signed message part
Re: stable-p-u and P9 security patches
On Fri, 2019-04-12 at 16:56 +0200, Frédéric Bonnard wrote: > Hi, > > several patches have been pushed upstream for next in 4.9.y linux kernel > concerning additional Spectre/Meltdown fixes on P9 for the new DD2.3 > processor revision : > https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/commit/?id=45d80ddf5e0c5fa43507709537559d1ed4583e9d > > I guess they'll be pushed into next 4.9.169 in the coming days : > > http://www.kernel.org/ > http://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/log/ > > When does the team plan to refresh the kernel for stable-p-u ? > Can we have something equal or greater than 4.9.169 to have those P9 security > patches ? This will happen in due course, but probably not until after the next point release (9.9 on 27th April). Ben. -- Ben Hutchings Hoare's Law of Large Problems: Inside every large problem is a small problem struggling to get out. signature.asc Description: This is a digitally signed message part
Bug#926794: linux-image-4.19.0.0-bpo.4-amd64: Please enable FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER in kernel config
On Wed, 10 Apr 2019 15:58:07 +0200 Frantisek Novak < novak.franti...@atlas.cz> wrote: > Package: linux-image-4.19.0.0-bpo.4-amd64 > Version: linux-image-4.19.0-0-bpo.4-amd64 > Severity: wishlist > > Dear Maintainer, > > please enable FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER in kernel configuration to prevent clearing of the framebuffer when the console starts during the boot. I tried it a few months back and I don't think we should do this in the kernel in isolation. We would also need to make the boot loader silent by default, and we might need to update themes as well. If you want this to happen, please propose those changes in the other packages after the buster release. Ben. -- Ben Hutchings Hoare's Law of Large Problems: Inside every large problem is a small problem struggling to get out. signature.asc Description: This is a digitally signed message part
Re: Handling irqbalance in virtual environments
On Fri, 2019-04-12 at 10:53 +0200, Bastian Blank wrote: > Moin > > It turns out we got again problems with irqbalance. > > It was added as recommends of the main image in 3.16, as it was reported > that older kernels move all interrupts to CPU 0 without help.[1] > > In the meantime the kernel can do balancing on it's own. In 4.9, I've > seen it working with aacraid, each queue gets hard pinned to it's own > CPU from 0 to $NRCPUS. In 4.19 I've seen the same working properly with > virtio-net. > > With 4.19, even on real hardware, where interrupts have an affinity for > all cpus, each interrupt is actually delivered to different cpu. > > Random example for this, it even selects only one thread of each core: > > > 26:0000 92000 IR-PCI-MSI 3670017-edge > > eno1-TxRx-0 > > 27:00000 16700 IR-PCI-MSI 3670018-edge > > eno1-TxRx-1 > > 28:000000 4670 IR-PCI-MSI 3670019-edge > > eno1-TxRx-2 > > 29:0000000 454 IR-PCI-MSI 3670020-edge > > eno1-TxRx-3 > > Now irqbalance comes to re-do the existing pinning, and the result is not > longer correct but $RANDOM for the hard queue-to-cpu case of virtio. Then let's drop the recommendation. Ben. > At least Google considers the work irqbalance does to "correct" the existing > balancing a large problem. > > I'm not sure how to go forward. I have a workaround pending for our > cloud images to hard exclude the installation of irqbalance.[2] > > Regards, > Bastian > > [1]: https://bugs.debian.org/577788 > [2]: https://salsa.debian.org/cloud-team/debian-cloud-images/merge_requests/81 -- Ben Hutchings Hoare's Law of Large Problems: Inside every large problem is a small problem struggling to get out. signature.asc Description: This is a digitally signed message part
question: what will happen to buster when kernel 4.19 goes out of life in Dec2020?
question: What will happen to buster when kernel 4.19 goes out of life in Dec2020? See EOL for 4.19. https://www.kernel.org/category/releases.html If buster debian 10 has to change the kernel to 5 in Dec 2020, it will be untested. And it would be preferable to have kernel 5 before buster is realeased during the testing phase. Or will you do your own patchsets on an out of life 4.19 kernel? Regards Thierry
linux_4.9.168-1_source.changes ACCEPTED into proposed-updates->stable-new
Mapping stretch to stable.
Mapping stable to proposed-updates.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 12 Apr 2019 15:52:49 +0200
Source: linux
Architecture: source
Version: 4.9.168-1
Distribution: stretch
Urgency: medium
Maintainer: Debian Kernel Team
Changed-By: Salvatore Bonaccorso
Changes:
linux (4.9.168-1) stretch; urgency=medium
.
* New upstream stable update:
https://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.162
- Revert "loop: Fix double mutex_unlock(&loop_ctl_mutex) in
loop_control_ioctl()"
- Revert "loop: Get rid of loop_index_mutex"
- Revert "loop: Fold __loop_release into loop_release"
- scsi: libsas: Fix rphy phy_identifier for PHYs with end devices attached
- [arm64] drm/msm: Unblock writer if reader closes file
- [x86] ASoC: Intel: Haswell/Broadwell: fix setting for .dynamic field
- [x86] ALSA: compress: prevent potential divide by zero bugs
- [x86] thermal: int340x_thermal: Fix a NULL vs IS_ERR() check
- [arm64,armhf] usb: dwc3: gadget: synchronize_irq dwc irq in suspend
- [arm64,armhf] usb: dwc3: gadget: Fix the uninitialized link_state when
udc starts
- usb: gadget: Potential NULL dereference on allocation error
- ASoC: dapm: change snprintf to scnprintf for possible overflow
- [armhf] ASoC: imx-audmux: change snprintf to scnprintf for possible
overflow
- [x86] drivers: thermal: int340x_thermal: Fix sysfs race condition
- mac80211: fix miscounting of ttl-dropped frames
- locking/rwsem: Fix (possible) missed wakeup
- direct-io: allow direct writes to empty inodes
- scsi: csiostor: fix NULL pointer dereference in csio_vport_set_state()
- net: usb: asix: ax88772_bind return error when hw_reset fail
- [ppc64el] ibmveth: Do not process frames after calling napi_reschedule
- mac80211: don't initiate TDLS connection if station is not associated to
AP
- mac80211: Add attribute aligned(2) to struct 'action'
- cfg80211: extend range deviation for DMG
- [x86] svm: Fix AVIC incomplete IPI emulation
- [x86] KVM: nSVM: clear events pending from svm_complete_interrupts()
when exiting to L1
- [powerpc*] Always initialize input array when calling epapr_hypercall()
- [arm64] mmc: spi: Fix card detection during probe
- mm: enforce min addr even if capable() in expand_downwards()
(CVE-2019-9213)
- [x86] uaccess: Don't leak the AC flag into __put_user() value evaluation
https://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.163
- USB: serial: option: add Telit ME910 ECM composition
- USB: serial: cp210x: add ID for Ingenico 3070
- USB: serial: ftdi_sio: add ID for Hjelmslund Electronics USB485
- cpufreq: Use struct kobj_attribute instead of struct global_attr
- ncpfs: fix build warning of strncpy
- [x86] staging: comedi: ni_660x: fix missing break in switch statement
- ip6mr: Do not call __IP6_INC_STATS() from preemptible context
- net-sysfs: Fix mem leak in netdev_register_kobject
- sky2: Disable MSI on Dell Inspiron 1545 and Gateway P-79
- team: Free BPF filter when unregistering netdev
- bnxt_en: Drop oversize TX packets to prevent errors.
- [x86] hv_netvsc: Fix IP header checksum for coalesced packets
- [armhf] net: dsa: mv88e6xxx: Fix u64 statistics
- net: netem: fix skb length BUG_ON in __skb_to_sgvec
- net: nfc: Fix NULL dereference on nfc_llcp_build_tlv fails
- net: sit: fix memory leak in sit_init_net()
- xen-netback: don't populate the hash cache on XenBus disconnect
- xen-netback: fix occasional leak of grant ref mappings under memory
pressure
- net: Add __icmp_send helper.
- tun: fix blocking read
- tun: remove unnecessary memory barrier
- net: phy: Micrel KSZ8061: link failure after cable connect
- [x86] CPU/AMD: Set the CPB bit unconditionally on F17h
- applicom: Fix potential Spectre v1 vulnerabilities
- [mips*] irq: Allocate accurate order pages for irq stack
- hugetlbfs: fix races and page leaks during migration
- exec: Fix mem leak in kernel_read_file (CVE-2019-8980)
- media: uvcvideo: Fix 'type' check leading to overflow
- vti4: Fix a ipip packet processing bug in 'IPCOMP' virtual tunnel
- perf core: Fix perf_proc_update_handler() bug
- perf tools: Handle TOPOLOGY headers with no CPU
- IB/{hfi1, qib}: Fix WC.byte_len calculation for UD_SEND_WITH_IMM
- [amd64] iommu/amd: Call free_iova_fast with pfn in map_sg
- [amd64] iommu/amd: Unmap all mapped pages in error path of map_sg
- ipvs: Fix signed integer overflow when setsockopt timeout
- [amd64] iommu/amd: Fix IOMMU page flush when detach device from a domain
- [arm64] net: hns: Fix for missing of_node_put() after of_parse_phandle()
- [arm64] net: hns: Fix wrong read accesses via Clause 45 MDI
Processing of linux_4.9.168-1_source.changes
linux_4.9.168-1_source.changes uploaded successfully to localhost along with the files: linux_4.9.168-1.dsc linux_4.9.168.orig.tar.xz linux_4.9.168-1.debian.tar.xz linux_4.9.168-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
stable-p-u and P9 security patches
Hi, several patches have been pushed upstream for next in 4.9.y linux kernel concerning additional Spectre/Meltdown fixes on P9 for the new DD2.3 processor revision : https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/commit/?id=45d80ddf5e0c5fa43507709537559d1ed4583e9d I guess they'll be pushed into next 4.9.169 in the coming days : http://www.kernel.org/ http://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/log/ When does the team plan to refresh the kernel for stable-p-u ? Can we have something equal or greater than 4.9.169 to have those P9 security patches ? Thanks a lot, F. pgp3PK9u9OB6a.pgp Description: PGP signature
Bug#926938: reboot hangs, hung task, ohci_urb_dequeue
Package: src:linux Version: 4.9.144-3.1 I have two machines in the Xen Project CI lab which fail to reboot using the stock stretch kernel. They both hang, printing a message like the one belwo to their serial console. The appearance of a new usb device during kernel reboot is rather odd. Full logs http://logs.test-lab.xenproject.org/osstest/logs/134652/test-amd64-amd64-xl-multivcpu/info.html http://logs.test-lab.xenproject.org/osstest/logs/134652/test-amd64-amd64-xl-multivcpu/serial-joubertin0.log http://logs.test-lab.xenproject.org/osstest/logs/134651/test-xtf-amd64-amd64-1/info.html http://logs.test-lab.xenproject.org/osstest/logs/134651/test-xtf-amd64-amd64-1/serial-merlot1.log Look at or near the end of each serial log. The "client 0x55dcddf30100 connected" messages are a result of my CI system deciding that the host isn't going reboot, and making connections to the serial concentrator to try to collect debug information. BTW, my Citrix email address has an often-malfunctioning spamfilter. Sadly I have not been able to get corporiate IT to fix it. Please CC ijack...@chiark.greenend.org.uk (especially if you get bounces). If ijackson@chiark bounces, talk to postmaster@chiark and I will fix my personal spamfilter so it lets you through. Sorry for any inconvenience. If you would like me to test any workaround or something, please let me know. Thanks, Ian. Apr 12 01:23:40.224056 Unmounting local filesystems...done. Apr 12 01:23:40.224074 [ 523.410355] EXT4-fs (dm-1): re-mounted. Opts: (null) Apr 12 01:23:40.260056 Will now restart. Apr 12 01:23:40.464036 [ 526.126589] kvm: exiting hardware virtualization Apr 12 01:23:42.976057 [ 599.629542] usb 3-2: new full-speed USB device number 2 using ohci-pci Apr 12 01:24:56.488055 [ 741.973018] INFO: task kworker/0:2:370 blocked for more than 120 seconds. Apr 12 01:27:18.840086 [ 741.980517] Not tainted 4.9.0-8-amd64 #1 Debian 4.9.144-3.1 Apr 12 01:27:18.840111 [ 741.988437] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Apr 12 01:27:18.852090 [ 741.997540] kworker/0:2 D0 370 2 0x Apr 12 01:27:18.864081 [ 742.004100] Workqueue: usb_hub_wq hub_event [usbcore] Apr 12 01:27:18.864102 [ 742.009689] 9d7431996580 9d7231d68100 9d7237c18980 Apr 12 01:27:18.876085 [ 742.017972] 9d722ac85080 c2a742443ba0 be2144b9 c03241c2 Apr 12 01:27:18.876110 [ 742.026553] 00ff9d723244d600 9d7237c18980 c02a40b0 9d7231d68100 Apr 12 01:27:18.888092 [ 742.035477] Call Trace: Apr 12 01:27:18.888109 [ 742.038273] [] ? __schedule+0x239/0x6f0 Apr 12 01:27:18.900084 [ 742.044656] [] ? ohci_urb_dequeue+0x72/0xa0 [ohci_hcd] Apr 12 01:27:18.912078 [ 742.052929] [] ? schedule+0x32/0x80 Apr 12 01:27:18.912100 [ 742.058956] [] ? usb_kill_urb+0x86/0xc0 [usbcore] Apr 12 01:27:18.924088 [ 742.066682] [] ? prepare_to_wait_event+0xf0/0xf0 Apr 12 01:27:18.924110 [ 742.074339] [] ? usb_start_wait_urb+0xe2/0x170 [usbcore] Apr 12 01:27:18.936094 [ 742.082688] [] ? usb_control_msg+0xdd/0x140 [usbcore] Apr 12 01:27:18.948080 [ 742.090724] [] ? hub_port_init+0x323/0xbd0 [usbcore] Apr 12 01:27:18.960073 [ 742.098831] [] ? usb_alloc_dev+0x1e2/0x300 [usbcore] Apr 12 01:27:18.960098 [ 742.106802] [] ? hub_event+0xb5d/0x15c0 [usbcore] Apr 12 01:27:18.972083 [ 742.114258] [] ? process_one_work+0x18a/0x430 Apr 12 01:27:18.972106 [ 742.121552] [] ? worker_thread+0x4d/0x490 Apr 12 01:27:18.984084 [ 742.128767] [] ? process_one_work+0x430/0x430 Apr 12 01:27:18.996072 [ 742.136056] [] ? kthread+0xd9/0xf0 Apr 12 01:27:18.996093 [ 742.142505] [] ? kthread_park+0x60/0x60 Apr 12 01:27:19.008069 [ 742.149159] [] ? ret_from_fork+0x44/0x70 Apr 12 01:27:19.008091 [ 864.055852] INFO: task kworker/0:2:370 blocked for more than 120 seconds. Apr 12 01:29:20.920082 [ 864.063321] Not tainted 4.9.0-8-amd64 #1 Debian 4.9.144-3.1 Apr 12 01:29:20.932081 [ 864.071672] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Apr 12 01:29:20.944079 [ 864.080284] kworker/0:2 D0 370 2 0x Apr 12 01:29:20.944100 [ 864.087479] Workqueue: usb_hub_wq hub_event [usbcore] Apr 12 01:29:20.956081 [ 864.093070] 9d7431996580 9d7231d68100 9d7237c18980 Apr 12 01:29:20.968086 [ 864.102238] 9d722ac85080 c2a742443ba0 be2144b9 c03241c2 Apr 12 01:29:20.968110 [ 864.112078] 00ff9d723244d600 9d7237c18980 c02a40b0 9d7231d68100 Apr 12 01:29:20.980083 [ 864.121397] Call Trace: Apr 12 01:29:20.980100 [ 864.124094] [] ? __schedule+0x239/0x6f0 Apr 12 01:29:20.992082 [ 864.131348] [] ? ohci_urb_dequeue+0x72/0xa0 [ohci_hcd] Apr 12 01:29:21.004079 [ 864.139310] [] ? schedule+0x32/0x80 Apr 12 01:29:21.004099 [ 864.145826] [] ? usb_kill_urb+0x86/0xc0 [usbcore] Apr 12 01:29:21.016080 [ 864.153651] [] ? prepare_to_wait_ev
Processed: reassign 926794 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 926794 src:linux Bug #926794 [linux-image-4.19.0.0-bpo.4-amd64] linux-image-4.19.0.0-bpo.4-amd64: Please enable FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER in kernel config Warning: Unknown package 'linux-image-4.19.0.0-bpo.4-amd64' Bug reassigned from package 'linux-image-4.19.0.0-bpo.4-amd64' to 'src:linux'. No longer marked as found in versions linux-image-4.19.0-0-bpo.4-amd64. Ignoring request to alter fixed versions of bug #926794 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 926794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926794 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Re: Handling irqbalance in virtual environments
On Fri, Apr 12, 2019 at 10:53:47AM +0200, Bastian Blank wrote: > With 4.19, even on real hardware, where interrupts have an affinity for > all cpus, each interrupt is actually delivered to different cpu. It seems a lot of this comes from https://lore.kernel.org/patchwork/cover/801590/ Regards, Bastian -- Violence in reality is quite different from theory. -- Spock, "The Cloud Minders", stardate 5818.4
Handling irqbalance in virtual environments
Moin It turns out we got again problems with irqbalance. It was added as recommends of the main image in 3.16, as it was reported that older kernels move all interrupts to CPU 0 without help.[1] In the meantime the kernel can do balancing on it's own. In 4.9, I've seen it working with aacraid, each queue gets hard pinned to it's own CPU from 0 to $NRCPUS. In 4.19 I've seen the same working properly with virtio-net. With 4.19, even on real hardware, where interrupts have an affinity for all cpus, each interrupt is actually delivered to different cpu. Random example for this, it even selects only one thread of each core: | 26:0000 92000 IR-PCI-MSI 3670017-edge eno1-TxRx-0 | 27:00000 16700 IR-PCI-MSI 3670018-edge eno1-TxRx-1 | 28:000000 4670 IR-PCI-MSI 3670019-edge eno1-TxRx-2 | 29:0000000 454 IR-PCI-MSI 3670020-edge eno1-TxRx-3 Now irqbalance comes to re-do the existing pinning, and the result is not longer correct but $RANDOM for the hard queue-to-cpu case of virtio. At least Google considers the work irqbalance does to "correct" the existing balancing a large problem. I'm not sure how to go forward. I have a workaround pending for our cloud images to hard exclude the installation of irqbalance.[2] Regards, Bastian [1]: https://bugs.debian.org/577788 [2]: https://salsa.debian.org/cloud-team/debian-cloud-images/merge_requests/81 -- Youth doesn't excuse everything. -- Dr. Janice Lester (in Kirk's body), "Turnabout Intruder", stardate 5928.5.
Bug#914517: linux-image-4.19.0-4-amd64: System freezes with nomodeset set and boots in a loop without
On Wed, 2019-04-10 at 23:02 +0200, Robert Pommrich wrote: > Am 10.04.19 um 22:32 schrieb Ben Hutchings: > > On Wed, 2019-04-10 at 17:26 +0200, Robert Pommrich wrote: > > > Hi, > > > > > > I really don't understand why the severity of this bug was lowered. > > > Plus, this was the only action taken on this bug beside my actions. > > [...] > > > > The phrase "renders package unusable" means that the package is > > unusable in general, or on a large proportion of Debian systems. > > > > I don't believe that that is the case for this bug. > > Okay, what would be the right phrase for a system, that doesn't start? https://kernel-team.pages.debian.net/kernel-handbook/ch-bugs.html#s9.1.2 has some info on how the kernel team interprets the severity field. Ian.
