[Kernel-packages] [Bug 1834213] Re: After kernel upgrade, nf_conntrack_ipv4 module unloaded, no IP traffic to instances
Ignore prior comment: $ lsmod | grep conntrack nf_conntrack_ipv6 20480 1 nf_conntrack_ipv4 16384 1 nf_defrag_ipv4 16384 1 nf_conntrack_ipv4 nf_defrag_ipv6 36864 2 nf_conntrack_ipv6,openvswitch nf_conntrack 131072 6 nf_conntrack_ipv6,nf_conntrack_ipv4,nf_nat,nf_nat_ipv6,nf_nat_ipv4,openvswitch libcrc32c 16384 5 nf_conntrack,nf_nat,openvswitch,xfs,raid456 as soon as a loaded the openvswitch kernel module the nf_conntrack_* modules where loaded as well. ** Changed in: charm-neutron-openvswitch Status: New => Incomplete ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834213 Title: After kernel upgrade, nf_conntrack_ipv4 module unloaded, no IP traffic to instances Status in OpenStack neutron-openvswitch charm: Incomplete Status in linux package in Ubuntu: New Bug description: With an environment running Xenial-Queens, and having just upgraded the linux-image-generic kernel for MDS patching, a few of our hypervisor hosts that were rebooted (3 out of 100) ended up dropping IP (tcp/udp) ingress traffic. It turns out that nf_conntrack module was loaded, but nf_conntrack_ipv4 was not loading, and the traffic was being dropped by this rule: table=72, n_packets=214989, priority=50,ct_state=+inv+trk actions=resubmit(,93) The ct_state "inv" means invalid conntrack state, which the manpage describes as: The state is invalid, meaning that the connection tracker couldn’t identify the connection. This flag is a catch- all for problems in the connection or the connection tracker, such as: • L3/L4 protocol handler is not loaded/unavailable. With the Linux kernel datapath, this may mean that the nf_conntrack_ipv4 or nf_conntrack_ipv6 modules are not loaded. • L3/L4 protocol handler determines that the packet is malformed. • Packets are unexpected length for protocol. It appears that there may be an issue when patching the OS of a hypervisor not running instances may fail to update initrd to load nf_conntrack_ipv4 (and/or _ipv6). I couldn't find anywhere in the charm code that this would be loaded unless the charm's "harden" option is used on nova-compute charm (see charmhelpers contrib/host templates). It is unset in our environment, so we are not using any special module probing. Did nf_conntrack_ipv4 get split out from nf_conntrack in recent kernel upgrades or is it possible that the charm should define a modprobe file if we have the OVS firewall driver configured? To manage notifications about this bug go to: https://bugs.launchpad.net/charm-neutron-openvswitch/+bug/1834213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836809] Re: segfault when CCD are present in two different HOG services
Noted! Anyway we already had installed the latest bluez version - 5.50. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1836809 Title: segfault when CCD are present in two different HOG services Status in Bluez Utilities: Unknown Status in bluez package in Ubuntu: New Bug description: Hello everyone, We are currently developing a device that contains two HID services. That device, as it is right now, is properly functioning on Windows & Android. However, when pairing the device on Linux running bluez 5.50 we do get segfaults (see attached files). Our bluetooth device has 4 services : 1 battery service, 2 HID Over Gatt services and 1 device information service. With trial and error, we managed to find that we wouldn't get any crash as long as only 1 HOG service was present. Here's the interesting part. The two HOG services are made as follows: - standard keyboard over gatt: protocole mode / report map / 1 INPUT report / boot INPUT + OUTPUT / HID information / HID Control point - raw HID over gatt : report map / 1 INPUT report / 1 OUTPUT report / HID information / HID control point Looking at the write_ccc in the call stacks we wondered if the callbacks subscribing to notifications for the INPUT reports were causing this issue. We therefore changed the raw HID over gatt (and its report map) to remove the INPUT report and change it into 1 OUTPUT report (leading to 2 OUTPUT reports): no crash. We therefore hypothesize that the segfault occurs when subscribing to notification on a second HOG service... To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1836809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834213] Re: After kernel upgrade, nf_conntrack_ipv4 module unloaded, no IP traffic to instances
Raising a kernel bug task. Note my testing was on Bionic not Xenial. Drew - can you confirm which kernel version and packages you are using. ** Changed in: charm-neutron-openvswitch Importance: Undecided => Low -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834213 Title: After kernel upgrade, nf_conntrack_ipv4 module unloaded, no IP traffic to instances Status in OpenStack neutron-openvswitch charm: Incomplete Status in linux package in Ubuntu: New Bug description: With an environment running Xenial-Queens, and having just upgraded the linux-image-generic kernel for MDS patching, a few of our hypervisor hosts that were rebooted (3 out of 100) ended up dropping IP (tcp/udp) ingress traffic. It turns out that nf_conntrack module was loaded, but nf_conntrack_ipv4 was not loading, and the traffic was being dropped by this rule: table=72, n_packets=214989, priority=50,ct_state=+inv+trk actions=resubmit(,93) The ct_state "inv" means invalid conntrack state, which the manpage describes as: The state is invalid, meaning that the connection tracker couldn’t identify the connection. This flag is a catch- all for problems in the connection or the connection tracker, such as: • L3/L4 protocol handler is not loaded/unavailable. With the Linux kernel datapath, this may mean that the nf_conntrack_ipv4 or nf_conntrack_ipv6 modules are not loaded. • L3/L4 protocol handler determines that the packet is malformed. • Packets are unexpected length for protocol. It appears that there may be an issue when patching the OS of a hypervisor not running instances may fail to update initrd to load nf_conntrack_ipv4 (and/or _ipv6). I couldn't find anywhere in the charm code that this would be loaded unless the charm's "harden" option is used on nova-compute charm (see charmhelpers contrib/host templates). It is unset in our environment, so we are not using any special module probing. Did nf_conntrack_ipv4 get split out from nf_conntrack in recent kernel upgrades or is it possible that the charm should define a modprobe file if we have the OVS firewall driver configured? To manage notifications about this bug go to: https://bugs.launchpad.net/charm-neutron-openvswitch/+bug/1834213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836986] Re: Kernel 5.2.0-8: iwlwifi Microcode SW error detected Wireless-AC 9260
Moving the 46 firmware out of /lib/firmware and copying the 43 firmware to the 46 firmware's filename and rebooting has allowed me to have successful wifi. modinfo shows it wants 46, but lshw show's it actually is running version 43. Please either revert to version 43, or fix 46. Thank you. :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1836986 Title: Kernel 5.2.0-8: iwlwifi Microcode SW error detected Wireless-AC 9260 Status in linux-signed package in Ubuntu: New Bug description: Ubuntu version: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 System type: description: Notebook product: Precision 5530 (087D) vendor: Dell Inc. Hardware having issue: (wireless card info from previous working kernel) *-network description: Wireless interface product: Wireless-AC 9260 vendor: Intel Corporation physical id: 0 bus info: pci@:3b:00.0 logical name: wlp59s0 version: 29 serial: 48:89:e7:d5:ab:b5 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-20-generic firmware=43.95eb4e97.0 ip=10.80.13.232 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:ed40-ed403fff Grub config with settings for Dell laptop hardware set: /etc/default/grub # If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg. # For full documentation of the options in this file, see: # info -f grub -n 'Simple configuration' GRUB_DEFAULT=0 GRUB_TIMEOUT=0 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" #GRUB_CMDLINE_LINUX_DEFAULT="nosplash" GRUB_CMDLINE_LINUX="nouveau.blacklist=1 acpi_rev_override=1 acpi_osi=Linux nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 nouveau.runpm=0 mem_sleep_default=deep" # Uncomment to enable BadRAM filtering, modify to suit your needs # This works with Linux (no patch required) and with any kernel that obtains # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...) #GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef" # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=console # The resolution used on graphical terminal # note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' #GRUB_GFXMODE=640x480 # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux #GRUB_DISABLE_LINUX_UUID=true # Uncomment to disable generation of recovery mode menu entries #GRUB_DISABLE_RECOVERY="true" # Uncomment to get a beep at grub start #GRUB_INIT_TUNE="480 440 1" Iwlwifi config with 11n disabled, 11n wasn't ever stable before, so left it disabled. /etc/modprobe.d/iwlwifi.conf # /etc/modprobe.d/iwlwifi.conf # iwlwifi will dyamically load either iwldvm or iwlmvm depending on the # microcode file installed on the system. When removing iwlwifi, first # remove the iwl?vm module and then iwlwifi. remove iwlwifi \ (/sbin/lsmod | grep -o -e ^iwlmvm -e ^iwldvm -e ^iwlwifi | xargs /sbin/rmmod) \ && /sbin/modprobe -r mac80211 options iwlwifi 11n_disable=1 Linux-Firmware package = 1.180 Nvidia Driver version = 430.34-0ubuntu2 Issue: Problem with kernel 5.2.0-8-generic - Wifi firmware fails to load. Works with 5.0.0.-20-generic kernel. Syslog: Jul 17 15:13:31 Lappy kernel: [ 85.319088] iwlwifi :3b:00.0: Microcode SW error detected. Restarting 0x0. Jul 17 15:13:31 Lappy kernel: [ 85.320158] iwlwifi :3b:00.0: Start IWL Error Log Dump: Jul 17 15:13:31 Lappy kernel: [ 85.320161] iwlwifi :3b:00.0: Status: 0x0080, count: 6 Jul 17 15:13:31 Lappy kernel: [ 85.320162] iwlwifi :3b:00.0: Loaded firmware version: 46.a41adfe7.0 Jul 17 15:13:31 Lappy kernel: [ 85.320164] iwlwifi :3b:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL Jul 17 15:13:31 Lappy kernel: [ 85.320166] iwlwifi :3b:00.0: 0x00A022F0 | trm_hw_status0 Jul 17 15:13:31 Lappy kernel: [ 85.320167] iwlwifi :3b:00.0: 0x | trm_hw_status1 Jul 17 15:13:31 Lappy kernel: [ 85.320168] iwlwifi :3b:00.0: 0x004882F2 | branchlink2 Jul 17 15:13:31 Lappy kernel: [ 85.320169] iwlwifi :3b:00.0: 0x004793A2 | interruptlink1 Jul 17 15:13:31 Lappy kernel: [ 85.320171] iwlwifi :3b:00.0: 0x00480EA2 | interruptlink2 Jul 17 15:13:31 Lappy kernel: [ 85.320172] iwlwifi
[Kernel-packages] [Bug 1828948] Re: OBSOLETE_BY in DKMS.CONF does not work
for #10, also followed the testing environment of #12 and tested passed on bionic as well. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1828948 Title: OBSOLETE_BY in DKMS.CONF does not work Status in DKMS: Fix Released Status in OEM Priority Project: Fix Committed Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Bionic: Fix Committed Status in dkms source package in Disco: Fix Committed Bug description: [Impact] OBSOLETE_BY in DKMS.CONF not work Which also be reported on upstream: https://github.com/dell/dkms/issues/81 [Test case] 1. add OBSOLETE_BY in DKMS.CONF e.g. OBSOLETE_BY="4.15.0-1033" 2. the kernel module should not be built with kernel greater than the version specified by OBSOLETE_BY e.g. - user install kernel 4.15.0-1030 and 4.15.0-10360 - user install kernel oem-wifi-qualcomm-ath10k-lp1803647-4.15-dkms [1] which has OBSOLETE_BY="4.15.0-1033" - the kernel module from dkms [1] should only built for 4.15.0-1030, but not for 4.15.0-10360 [Regression potential] None as it used to work, but somehow regression there. [1] https://code.launchpad.net/~alextu/+recipe/oem-wifi-qualcomm- ath10k-lp1803647-4.15-dkms-daily To manage notifications about this bug go to: https://bugs.launchpad.net/dkms/+bug/1828948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836456] Re: [ThinkPad S1 Yoga] Machine Immediately Wakes Up From Suspend
Ok, please compare "/sys/kernel/debug/wakeup_sources" before and after suspend to see which device wakes the system up. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836456 Title: [ThinkPad S1 Yoga] Machine Immediately Wakes Up From Suspend Status in linux package in Ubuntu: Confirmed Bug description: I am using Ubuntu 18.04.2 on a Lenovo ThinkPad S1 Yoga. Unfortunately when I suspend the machine to throw it into my bag, it immediately wakes up causing an issue where the machine will run hot in 85 - 90 degree weather while I am in town. This is not a firmware issue as I have downgraded the BIOS and I have also observed how it worked fine under Arch Linux. I am not entirely sure which package is responsible to interact with acpi under Debian/Ubuntu $ lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 Here is my version.log output, I will provide them as separate attachments per the guidelines Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lalo 1814 F pulseaudio /dev/snd/controlC1: lalo 1814 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=/dev/sda3 InstallationDate: Installed on 2019-07-01 (11 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 20C00063US Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic root=UUID=c9ed5b87-08bb-441b-9d27-ed5b3f05260e ro quiet splash resume=/dev/sda3 vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-25-generic N/A linux-backports-modules-4.18.0-25-generic N/A linux-firmware 1.173.8 Tags: bionic Uname: Linux 4.18.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/28/2018 dmi.bios.vendor: LENOVO dmi.bios.version: B0ET43WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20C00063US dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrB0ET43WW(1.30):bd09/28/2018:svnLENOVO:pn20C00063US:pvrThinkPadS1Yoga:rvnLENOVO:rn20C00063US:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad S1 Yoga dmi.product.name: 20C00063US dmi.product.sku: LENOVO_MT_20C0_BU_Think_FM_ThinkPad S1 Yoga dmi.product.version: ThinkPad S1 Yoga dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836456/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836630] Re: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend
PCI core saves device's config space during suspend so I think it won't cause any issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in Linux: Unknown Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers package in Ubuntu: New Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: system76 1721 F pulseaudio /dev/snd/controlC0: system76 1721 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 MachineType: System76 Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux-hwe-edge ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: oryp5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOryxPro:rvroryp5:cvnSystem76:ct10:cvroryp5: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1836630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1439872] Re: kernel panic involving drbd
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1439872 Title: kernel panic involving drbd Status in linux package in Ubuntu: Expired Bug description: It was brought to my attention the following kernel panic: SYSTEM MAP: /boot/System.map-3.16.0-31-generic DEBUG KERNEL: /usr/lib/debug/boot/vmlinux-3.16.0-31-generic DUMPFILE: ./dump.201503271156 [PARTIAL DUMP] CPUS: 12 DATE: Fri Mar 27 12:56:49 2015 UPTIME: 13 days, 19:14:00 LOAD AVERAGE: 1.72, 0.67, 0.28 TASKS: 340 NODENAME: bluegrass3 RELEASE: 3.16.0-31-generic VERSION: #41~14.04.1-Ubuntu SMP Wed Feb 11 19:30:13 UTC 2015 MACHINE: x86_64 (2397 Mhz) MEMORY: 63.9 GB PANIC: "Kernel panic - not syncing: hung_task: blocked tasks" [1191751.738854] request: minor=1, resource=vm-appserver; but that minor belongs to resource libvirt [1191759.892350] drbd vm-database: peer( Secondary -> Unknown ) conn( Connected -> Disconnecting ) pdsk( UpToDate -> DUnknown ) [1191759.892359] drbd vm-database: asender terminated [1191759.892362] drbd vm-database: Terminating drbd_a_vm-datab [1191759.892471] drbd vm-database: Connection closed [1191759.892480] drbd vm-database: conn( Disconnecting -> StandAlone ) [1191759.892481] drbd vm-database: receiver terminated [1191759.892485] drbd vm-database: Terminating drbd_r_vm-datab [1191759.892497] block drbd6: disk( UpToDate -> Failed ) [1191759.902311] block drbd6: bitmap WRITE of 0 pages took 0 jiffies [1191759.902315] block drbd6: 0 KB (0 bits) marked out-of-sync by on disk bit-map. [1191759.902322] block drbd6: disk( Failed -> Diskless ) [1191759.902565] block drbd6: drbd_bm_resize called with capacity == 0 [1191759.902585] drbd vm-database: Terminating drbd_w_vm-datab [1191992.802513] INFO: task drbdsetup:20254 blocked for more than 120 seconds. [1191992.834141] Not tainted 3.16.0-31-generic #41~14.04.1-Ubuntu [1191992.862889] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [1191992.900367] drbdsetup D 88085fc53440 0 20254 1 0x0004 [1191992.900371] 880845967ab8 0086 880abe65c750 880845967fd8 [1191992.900374] 00013440 00013440 8808546d65e0 8808b5365800 [1191992.900378] 1e00 0400 000e 8808b5365a30 [1191992.900388] Call Trace: [1191992.900398] [] schedule+0x29/0x70 [1191992.900407] [] _drbd_request_state+0x65/0xb0 [drbd] [1191992.900413] [] ? prepare_to_wait_event+0x100/0x100 [1191992.900418] [] adm_detach.part.52+0x3e/0x100 [drbd] [1191992.900422] [] ? drbd_adm_prepare.isra.48+0xd1/0x4e0 [drbd] [1191992.900426] [] drbd_adm_detach+0x149/0x150 [drbd] [1191992.900431] [] genl_family_rcv_msg+0x199/0x380 [1191992.900432] [] ? genl_family_rcv_msg+0x380/0x380 [1191992.900434] [] genl_rcv_msg+0x91/0xd0 [1191992.900436] [] netlink_rcv_skb+0xa9/0xc0 [1191992.900438] [] genl_rcv+0x28/0x40 [1191992.900439] [] netlink_unicast+0xf3/0x200 [1191992.900441] [] netlink_sendmsg+0x315/0x680 [1191992.900448] [] ? aa_sk_perm.isra.4+0x6d/0x150 [1191992.900452] [] sock_aio_write+0xfe/0x130 [1191992.900456] [] do_sync_write+0x5a/0x90 [1191992.900458] [] vfs_write+0x195/0x1f0 [1191992.900461] [] SyS_write+0x46/0xb0 [1191992.900464] [] system_call_fastpath+0x1a/0x1f [1191992.900465] sending NMI to all CPUs: Dump at: http://telsasoft.com/tmp/varcrash-201503271156.tar.bz2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1439872/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1398497] Re: HP Proliant Serverrs - DL360 and DL380 Gen8 - Precise Kernel Panic - General Protection Fault and X2APIC/XAPIC boot parameters
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1398497 Title: HP Proliant Serverrs - DL360 and DL380 Gen8 - Precise Kernel Panic - General Protection Fault and X2APIC/XAPIC boot parameters Status in linux package in Ubuntu: Expired Status in linux source package in Precise: Expired Bug description: It was brought to my attention the following situation: """ We massively upgraded our Ubuntu 12.04 servers (most of them are HP DL360p Gen8 or DL380 Gen8) to 3.2.0-67 kernel And in the last 2-3 days we already had to reboot 5 of them because they completely hang Some of them had the following messages under syslog : kernel: [384707.675479] general protection fault: [#5666] SMP others had : kernel: [950725.612724] BUG: unable to handle kernel paging request All of them have this also : your BIOS is broken and requested that x2apic be disabled """ Comments bellow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1398497/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1398497] Re: HP Proliant Serverrs - DL360 and DL380 Gen8 - Precise Kernel Panic - General Protection Fault and X2APIC/XAPIC boot parameters
[Expired for linux (Ubuntu Precise) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu Precise) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1398497 Title: HP Proliant Serverrs - DL360 and DL380 Gen8 - Precise Kernel Panic - General Protection Fault and X2APIC/XAPIC boot parameters Status in linux package in Ubuntu: Expired Status in linux source package in Precise: Expired Bug description: It was brought to my attention the following situation: """ We massively upgraded our Ubuntu 12.04 servers (most of them are HP DL360p Gen8 or DL380 Gen8) to 3.2.0-67 kernel And in the last 2-3 days we already had to reboot 5 of them because they completely hang Some of them had the following messages under syslog : kernel: [384707.675479] general protection fault: [#5666] SMP others had : kernel: [950725.612724] BUG: unable to handle kernel paging request All of them have this also : your BIOS is broken and requested that x2apic be disabled """ Comments bellow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1398497/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1447763] Re: HP Proliant Servers suffer from cpufreq initialization failure for some cpu cores
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1447763 Title: HP Proliant Servers suffer from cpufreq initialization failure for some cpu cores Status in linux package in Ubuntu: Expired Bug description: It was brought to my attention the following: Ubuntu Trusty Kernel 3.13 is suffering from cpufreq initialization failure for some cpu cores on Proliant Servers. /sys/devices/system/cpu# for cpu in `ls -1d cpu[0-9]*`; do ls -ld $cpu/cpufreq; done drwxr-xr-x 2 root root 0 Apr 2 16:15 cpu0/cpufreq drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu1/cpufreq drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu10/cpufreq drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu11/cpufreq drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu12/cpufreq drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu13/cpufreq drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu14/cpufreq drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu15/cpufreq drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu16/cpufreq ls: cannot access cpu17/cpufreq: No such file or directory drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu18/cpufreq drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu19/cpufreq drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu2/cpufreq drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu20/cpufreq drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu21/cpufreq drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu22/cpufreq drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu23/cpufreq drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu24/cpufreq drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu25/cpufreq drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu26/cpufreq drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu27/cpufreq drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu28/cpufreq drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu29/cpufreq drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu3/cpufreq drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu30/cpufreq drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu31/cpufreq drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu4/cpufreq drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu5/cpufreq drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu6/cpufreq drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu7/cpufreq drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu8/cpufreq drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu9/cpufreq With the following message: [ 2.465616] pcc-cpufreq: (v1.10.00) driver loaded with frequency limits: 1200 MHz, 2200 MHz [ 2.474810] cpufreq: __cpufreq_add_dev: ->get() failed Disabling Collaborative Power Control into firmware setup mitigates the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1447763/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834549] Re: Wifi won't load
Yes sorry, I was pretty sure I didn't mark it as a security bug. Sorry if I flubbed that part up. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834549 Title: Wifi won't load Status in linux package in Ubuntu: Confirmed Bug description: To me this looks different from: 1. https://lkml.org/lkml/2019/4/11/861 2. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1537183 version.log: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 00:14.3 Network controller: Intel Corporation Wireless-AC 9560 [Jefferson Peak] (rev 10) /var/log/kern.log: ... Jun 27 15:03:41 user-ThinkPad-P52 kernel: [274383.172489] CPU5: Package temperature/speed normal Jun 27 15:10:04 user-ThinkPad-P52 kernel: [274765.973921] thinkpad_acpi: unhandled HKEY event 0x6031 Jun 27 15:10:04 user-ThinkPad-P52 kernel: [274765.973924] thinkpad_acpi: please report the conditions when this event happened to ibm-acpi-de...@lists.sourceforge.net Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.439876] iwlwifi :00:14.3: Error sending STATISTICS_CMD: time out after 2000ms. Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.439892] iwlwifi :00:14.3: Current CMD queue read_ptr 10 write_ptr 11 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440076] iwlwifi :00:14.3: Start IWL Error Log Dump: Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440084] iwlwifi :00:14.3: Status: 0x0100, count: 6 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440090] iwlwifi :00:14.3: Loaded firmware version: 38.c0e03d94.0 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440096] iwlwifi :00:14.3: 0x0034 | NMI_INTERRUPT_WDG Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440102] iwlwifi :00:14.3: 0x22F0 | trm_hw_status0 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440107] iwlwifi :00:14.3: 0x | trm_hw_status1 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440112] iwlwifi :00:14.3: 0x00454EAA | branchlink2 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440118] iwlwifi :00:14.3: 0x0045E8C2 | interruptlink1 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440123] iwlwifi :00:14.3: 0xE630 | interruptlink2 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440128] iwlwifi :00:14.3: 0x | data1 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440133] iwlwifi :00:14.3: 0x03FF | data2 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440138] iwlwifi :00:14.3: 0x03FF | data3 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440144] iwlwifi :00:14.3: 0x6AC0A6B1 | beacon time Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440149] iwlwifi :00:14.3: 0xD15FB958 | tsf low Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440155] iwlwifi :00:14.3: 0x002C | tsf hi Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440160] iwlwifi :00:14.3: 0x | time gp1 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440166] iwlwifi :00:14.3: 0xF36C18D6 | time gp2 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440171] iwlwifi :00:14.3: 0x0001 | uCode revision type Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440176] iwlwifi :00:14.3: 0x0026 | uCode version major Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440181] iwlwifi :00:14.3: 0xC0E03D94 | uCode version minor Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440187] iwlwifi :00:14.3: 0x0312 | hw version Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440192] iwlwifi :00:14.3: 0x00489008 | board version Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440197] iwlwifi :00:14.3: 0x0A69001C | hcmd Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440203] iwlwifi :00:14.3: 0x22822002 | isr0 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440208] iwlwifi :00:14.3: 0x0080 | isr1 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440213] iwlwifi :00:14.3: 0x08005802 | isr2 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440218] iwlwifi :00:14.3: 0x4040BDC3 | isr3 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440223] iwlwifi :00:14.3: 0x | isr4 Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440229] iwlwifi :00:14.3: 0x0A68001C | last cmd Id Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440235] iwlwifi :00:14.3: 0x | wait_event Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440240] iwlwifi :00:14.3: 0x | l2p_control Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440245] iwlwifi :00:14.3: 0x0020 | l2p_duration Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440250] iwlwifi :00:14.3: 0x | l2p_mhvalid Jun 27 16:20:13 user-ThinkPad-P52 kernel: [278975.440256] iwlwifi :00:14.3: 0x | l2p_addr_match Jun 27
[Kernel-packages] [Bug 1836169] Re: cpuhotplug04 in cpuhotplug from ubuntu_ltp failed on C ARM64
On amd64 node naumann with Disco kernel, this test failed with: Name: cpuhotplug04 Date: Mon Jul 8 17:22:01 UTC 2019 Desc: Does it prevent us from offlining the last CPU? /opt/ltp/testcases/bin/cpuhotplug04.sh: 99: echo: echo: I/O error cpuhotplug04 1 TFAIL: Could not offline cpu95 tag=cpuhotplug04 stime=1562606521 dur=59 exit=exited stat=1 core=no cu=44 cs=105 ** Tags added: 5.0 amd64 disco ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836169 Title: cpuhotplug04 in cpuhotplug from ubuntu_ltp failed on C ARM64 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Status in linux source package in Disco: New Bug description: This issue can be found on both ThunderX and Moonshot ARM64 <<>> incrementing stop Name: cpuhotplug04 Date: Thu Jul 11 08:34:50 UTC 2019 Desc: Does it prevent us from offlining the last CPU? sh: echo: I/O error cpuhotplug04 1 TFAIL: Could not offline cpu0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=9 cstime=4 <<>> Steps to run this test: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "cpuhotplug04 cpuhotplug04.sh -l 1" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-25-generic 4.18.0-25.26 ProcVersionSignature: User Name 4.18.0-25.26-generic 4.18.20 Uname: Linux 4.18.0-25-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 11 06:57 seq crw-rw 1 root audio 116, 33 Jul 11 06:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.4 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jul 11 08:28:42 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.18.0-25-generic N/A linux-backports-modules-4.18.0-25-generic N/A linux-firmware 1.175.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1836169/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836167] Re: cpuhotplug03 in cpuhotplug from ubuntu_ltp failed on C Moonshot ARM64
Same failure: TFAIL: No cpuhotplug_do_spin_loop processes found on CPU1 Found on amd64 node naumann with Disco kernel. ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836167 Title: cpuhotplug03 in cpuhotplug from ubuntu_ltp failed on C Moonshot ARM64 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Status in linux source package in Disco: New Bug description: <<>> incrementing stop Name: cpuhotplug03 Date: Thu Jul 11 08:31:48 UTC 2019 Desc: Do tasks get scheduled to a newly on-lined CPU? CPU is 1 sh: echo: I/O error cpuhotplug03 1 TBROK: CPU1 cannot be offlined USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root 4642 0.0 0.0 2020 488 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4643 0.0 0.0 2020 480 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4644 0.0 0.0 2020 468 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4645 0.0 0.0 2020 488 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4646 0.0 0.0 2020 472 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4647 0.0 0.0 2020 480 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4648 0.0 0.0 2020 456 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4649 0.0 0.0 2020 508 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4650 0.0 0.0 2020 488 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4651 0.0 0.0 2020 472 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4652 0.0 0.0 2020 484 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4653 0.0 0.0 2020 496 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4654 0.0 0.0 2020 464 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4655 0.0 0.0 2020 492 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4656 0.0 0.0 2020 448 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4657 0.0 0.0 2020 472 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4661 0.0 0.0 7540 648 pts/0S08:31 0:00 grep cpuhotplug_do_spin_loop cpuhotplug03 1 TINFO: Onlining CPU 1 7 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 1 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 4 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 0 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 3 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 6 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 1 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 5 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 3 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 7 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 6 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 2 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 4 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 2 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 0 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 5 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop cpuhotplug03 1 TPASS: 2 cpuhotplug_do_spin_loop processes found onCPU1 <<>> initiation_status="ok" duration=1 termination_type=exited termination_id=2 corefile=no cutime=1060 cstime=9 <<>> Test passed on ThunderX ARM64, probably a test case issue. Steps to run this test: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "cpuhotplug03 cpuhotplug03.sh -c 1 -l 1" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-25-generic 4.18.0-25.26 ProcVersionSignature: User Name 4.18.0-25.26-generic 4.18.20 Uname: Linux 4.18.0-25-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 11 06:57 seq crw-rw 1 root audio 116, 33 Jul 11 06:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
[Kernel-packages] [Bug 1834006] Re: cpuset_hotplug from controllers in ubuntu_ltp failed on C/D
** Summary changed: - cpuset_hotplug from controllers in ubuntu_ltp failed on Cosmic + cpuset_hotplug from controllers in ubuntu_ltp failed on C/D -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834006 Title: cpuset_hotplug from controllers in ubuntu_ltp failed on C/D Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: New Status in linux source package in Disco: New Bug description: Issue found on node amaura: <<>> tag=cpuset_hotplug stime=1561372131 cmdline="cpuset_hotplug_test.sh" contacts="" analysis=exit <<>> incrementing stop cpuset_hotplug 1 TFAIL: task's allowed list isn't expected.(Result: 0-15, Expect: 0-7) cpuset_hotplug 3 TFAIL: task's allowed list isn't expected.(Result: 0-15, Expect: 0-7) cpuset_hotplug 5 TPASS: Cpuset vs CPU hotplug test succeeded. cpuset_hotplug 7 TFAIL: task's cpu allowed list isn't expected(Result: 0-15, Expect: 0-7). cpuset_hotplug 9 TPASS: Cpuset vs CPU hotplug test succeeded. cpuset_hotplug 11 TPASS: Cpuset vs CPU hotplug test succeeded. <<>> initiation_status="ok" duration=1 termination_type=exited termination_id=1 corefile=no cutime=19 cstime=81 <<>> Test script: https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/controllers/cpuset/cpuset_hotplug_test/cpuset_hotplug_test.sh ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-22-generic 4.18.0-22.23 ProcVersionSignature: User Name 4.18.0-22.23-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 24 10:25 seq crw-rw 1 root audio 116, 33 Jun 24 10:25 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Jun 24 10:30:59 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-4.18.0-22-generic N/A linux-backports-modules-4.18.0-22-generic N/A linux-firmware 1.175.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.family: To be filled by O.E.M. dmi.product.name: S1200RP dmi.product.sku: To be filled by O.E.M. dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1834006/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836971] Re: sched: Prevent CPU lockups when task groups take longer than the period
** Description changed: BugLink: https://bugs.launchpad.net/bugs/1836971 [Impact] On machines with extremely high CPU usage, parent task groups which have a large number of children can make the for loop in sched_cfs_period_timer() run until the watchdog fires when the cfs_period_us setting is too short. In this particular case, it is unlikely that the call to hrtimer_forward_now() will return 0, meaning the for loop is never left, and tasks are never rescheduled. The large number of children makes do_sched_cfs_period_timer() take longer than the period, which impacts calls to hrtimer_forward_now(). The kernel will produce this call trace: CPU: 51 PID: 0 Comm: swapper/51 Tainted: P OELK 4.15.0-50-generic #54-Ubuntu Call Trace: ? sched_clock+0x9/0x10 walk_tg_tree_from+0x61/0xd0 ? task_rq_unlock+0x30/0x30 unthrottle_cfs_rq+0xcb/0x1a0 distribute_cfs_runtime+0xd7/0x100 sched_cfs_period_timer+0xd9/0x1a0 ? sched_cfs_slack_timer+0xe0/0xe0 __hrtimer_run_queues+0xdf/0x230 hrtimer_interrupt+0xa0/0x1d0 smp_apic_timer_interrupt+0x6f/0x130 apic_timer_interrupt+0x84/0x90 This has been hit in production in a particularly highly utilised hadoop cluster which is powering an analytics platform. About 30% of the cluster experiences this issue every week, and the machines need a manual reboot to get back online. [Fix] This was fixed in 5.1 upstream with the below commit: commit 2e8e19226398db8265a8e675fcc0118b9e80c9e8 Author: Phil Auld Date: Tue Mar 19 09:00:05 2019 -0400 subject: sched/fair: Limit sched_cfs_period_timer() loop to avoid hard lockup This commit adds a check to see if the loop has run too many times, and if it has, scales up the period and quota, so the timer can complete before the next period expires, which enables the task to be rescheduled normally. Note, 2e8e19226398db8265a8e675fcc0118b9e80c9e8 was included in upstream stable versions 4.4.179, 4.9.171, 4.14.114, 4.19.37, 5.0.10. - Please cherry pick 2e8e19226398db8265a8e675fcc0118b9e80c9e8 to all bionic - kernels. + This patch requires minor backporting for 4.15, so please cherry pick + d069fe4844f8d799d771659a745fe91870c93fda from upstream stable 4.14.y, where the backport has been done by the original author, to all bionic kernels. [Testcase] Kind of hard to reproduce, so this was tested on a production hadoop cluster with extremely high CPU load. I built a test kernel, which is available here: https://launchpad.net/~mruffell/+archive/ubuntu/sf232784-test For unpatched kernels, expect the machine to lockup and print the call trace in the impact section. For patched kernels, if the machine hits the condition, it will print a warning to the kernel log with the new period and quota which has been used: Example from the same hadoop cluster with a machine running the test kernel: % uname -a 4.15.0-50-generic #54+hf232784v20190626b1-Ubuntu % sudo grep cfs /var/log/kern.log.* cfs_period_timer[cpu40]: period too short, scaling up (new cfs_period_us 67872, cfs_quota_us = 3475091) cfs_period_timer[cpu48]: period too short, scaling up (new cfs_period_us 22430, cfs_quota_us = 1148437) cfs_period_timer[cpu48]: period too short, scaling up (new cfs_period_us 25759, cfs_quota_us = 1318908) cfs_period_timer[cpu68]: period too short, scaling up (new cfs_period_us 29583, cfs_quota_us = 1514684) cfs_period_timer[cpu49]: period too short, scaling up (new cfs_period_us 33974, cfs_quota_us = 1739519) cfs_period_timer[cpu3]: period too short, scaling up (new cfs_period_us 39017, cfs_quota_us = 1997729) cfs_period_timer[cpu10]: period too short, scaling up (new cfs_period_us 44809, cfs_quota_us = 2294267) cfs_period_timer[cpu3]: period too short, scaling up (new cfs_period_us 51460, cfs_quota_us = 2634823) cfs_period_timer[cpu3]: period too short, scaling up (new cfs_period_us 59099, cfs_quota_us = 3025929) cfs_period_timer[cpu3]: period too short, scaling up (new cfs_period_us 67872, cfs_quota_us = 3475091) [Regression Potential] This patch was accepted into upstream stable versions 4.4.179, 4.9.171, 4.14.114, 4.19.37, 5.0.10, and is thus treated as stable and trusted by the community. Xenial received this patch in 4.4.0-150.176, as per LP #1828420 Disco will receive this patch in the next version, as per LP #1830922 Eoan already has the patch, being based on 5.2. While this does effect a core part of the kernel, the scheduler, the patch has been extensively tested, and it has been proven in production environments, so the overall risk is low. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836971 Title: sched: Prevent CPU lockups when task groups take longer than the period Status in linux package in Ubuntu:
[Kernel-packages] [Bug 1834006] Re: cpuset_hotplug from controllers in ubuntu_ltp failed on Cosmic
Found on node "amaura" with Disco kernel. ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Tags added: sru-20190701 ** Tags added: 4.18 5.0 disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834006 Title: cpuset_hotplug from controllers in ubuntu_ltp failed on Cosmic Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: New Status in linux source package in Disco: New Bug description: Issue found on node amaura: <<>> tag=cpuset_hotplug stime=1561372131 cmdline="cpuset_hotplug_test.sh" contacts="" analysis=exit <<>> incrementing stop cpuset_hotplug 1 TFAIL: task's allowed list isn't expected.(Result: 0-15, Expect: 0-7) cpuset_hotplug 3 TFAIL: task's allowed list isn't expected.(Result: 0-15, Expect: 0-7) cpuset_hotplug 5 TPASS: Cpuset vs CPU hotplug test succeeded. cpuset_hotplug 7 TFAIL: task's cpu allowed list isn't expected(Result: 0-15, Expect: 0-7). cpuset_hotplug 9 TPASS: Cpuset vs CPU hotplug test succeeded. cpuset_hotplug 11 TPASS: Cpuset vs CPU hotplug test succeeded. <<>> initiation_status="ok" duration=1 termination_type=exited termination_id=1 corefile=no cutime=19 cstime=81 <<>> Test script: https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/controllers/cpuset/cpuset_hotplug_test/cpuset_hotplug_test.sh ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-22-generic 4.18.0-22.23 ProcVersionSignature: User Name 4.18.0-22.23-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 24 10:25 seq crw-rw 1 root audio 116, 33 Jun 24 10:25 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Jun 24 10:30:59 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-4.18.0-22-generic N/A linux-backports-modules-4.18.0-22-generic N/A linux-firmware 1.175.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.family: To be filled by O.E.M. dmi.product.name: S1200RP dmi.product.sku: To be filled by O.E.M. dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1834006/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836809] Re: segfault when CCD are present in two different HOG services
Thanks. Please note Ubuntu 18.10 reaches end-of-life this month, so please upgrade to 19.04. ** Tags added: cosmic ** Bug watch added: Linux Kernel Bug Tracker #204201 https://bugzilla.kernel.org/show_bug.cgi?id=204201 ** Also affects: bluez via https://bugzilla.kernel.org/show_bug.cgi?id=204201 Importance: Unknown Status: Unknown ** Changed in: bluez (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1836809 Title: segfault when CCD are present in two different HOG services Status in Bluez Utilities: Unknown Status in bluez package in Ubuntu: New Bug description: Hello everyone, We are currently developing a device that contains two HID services. That device, as it is right now, is properly functioning on Windows & Android. However, when pairing the device on Linux running bluez 5.50 we do get segfaults (see attached files). Our bluetooth device has 4 services : 1 battery service, 2 HID Over Gatt services and 1 device information service. With trial and error, we managed to find that we wouldn't get any crash as long as only 1 HOG service was present. Here's the interesting part. The two HOG services are made as follows: - standard keyboard over gatt: protocole mode / report map / 1 INPUT report / boot INPUT + OUTPUT / HID information / HID Control point - raw HID over gatt : report map / 1 INPUT report / 1 OUTPUT report / HID information / HID control point Looking at the write_ccc in the call stacks we wondered if the callbacks subscribing to notifications for the INPUT reports were causing this issue. We therefore changed the raw HID over gatt (and its report map) to remove the INPUT report and change it into 1 OUTPUT report (leading to 2 OUTPUT reports): no crash. We therefore hypothesize that the segfault occurs when subscribing to notification on a second HOG service... To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1836809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836858] Re: i915: Display flickers during "flickerfree" boot
I've now found this occurs on an HP laptop, as well as a Lenovo desktop. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836858 Title: i915: Display flickers during "flickerfree" boot Status in linux package in Ubuntu: Confirmed Bug description: I am trying flickerfree boot in 19.10 [1], but find it actually flickers part way through. The flicker occurs seemingly during kernel startup since my peripherals are lit up before the problem occurs. Suspecting this might be related to FB handover: [2.751028] fb0: switching to inteldrmfb from EFI VGA I tried disabling that with a big hammer: i915.modeset=0 so it stays in efifb, and that works -- no more flickering, providing I don't let i915 take over the framebuffer. [1] https://discourse.ubuntu.com/t/testing-flickerfree-boot/11854 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-8-generic 5.2.0-8.9 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Jul 17 16:34:36 2019 InstallationDate: Installed on 2019-05-02 (76 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190501) MachineType: LENOVO 10M7CTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic root=UUID=9bfb5f01-bdd4-4854-bfce-1c28e2f2f3bc ro quiet splash i915.fastboot=1 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.180 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2018 dmi.bios.vendor: LENOVO dmi.bios.version: M16KT47A dmi.board.name: 3102 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN 3259627060530 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060530:cvnLENOVO:ct3:cvrNone: dmi.product.family: ThinkCentre M710s dmi.product.name: 10M7CTO1WW dmi.product.sku: LENOVO_MT_10M7_BU_Think_FM_ThinkCentre M710s dmi.product.version: ThinkCentre M710s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836858/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836986] [NEW] Kernel 5.2.0-8: iwlwifi Microcode SW error detected Wireless-AC 9260
Public bug reported: Ubuntu version: Description:Ubuntu Eoan Ermine (development branch) Release:19.10 System type: description: Notebook product: Precision 5530 (087D) vendor: Dell Inc. Hardware having issue: (wireless card info from previous working kernel) *-network description: Wireless interface product: Wireless-AC 9260 vendor: Intel Corporation physical id: 0 bus info: pci@:3b:00.0 logical name: wlp59s0 version: 29 serial: 48:89:e7:d5:ab:b5 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-20-generic firmware=43.95eb4e97.0 ip=10.80.13.232 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:ed40-ed403fff Grub config with settings for Dell laptop hardware set: /etc/default/grub # If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg. # For full documentation of the options in this file, see: # info -f grub -n 'Simple configuration' GRUB_DEFAULT=0 GRUB_TIMEOUT=0 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" #GRUB_CMDLINE_LINUX_DEFAULT="nosplash" GRUB_CMDLINE_LINUX="nouveau.blacklist=1 acpi_rev_override=1 acpi_osi=Linux nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 nouveau.runpm=0 mem_sleep_default=deep" # Uncomment to enable BadRAM filtering, modify to suit your needs # This works with Linux (no patch required) and with any kernel that obtains # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...) #GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef" # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=console # The resolution used on graphical terminal # note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' #GRUB_GFXMODE=640x480 # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux #GRUB_DISABLE_LINUX_UUID=true # Uncomment to disable generation of recovery mode menu entries #GRUB_DISABLE_RECOVERY="true" # Uncomment to get a beep at grub start #GRUB_INIT_TUNE="480 440 1" Iwlwifi config with 11n disabled, 11n wasn't ever stable before, so left it disabled. /etc/modprobe.d/iwlwifi.conf # /etc/modprobe.d/iwlwifi.conf # iwlwifi will dyamically load either iwldvm or iwlmvm depending on the # microcode file installed on the system. When removing iwlwifi, first # remove the iwl?vm module and then iwlwifi. remove iwlwifi \ (/sbin/lsmod | grep -o -e ^iwlmvm -e ^iwldvm -e ^iwlwifi | xargs /sbin/rmmod) \ && /sbin/modprobe -r mac80211 options iwlwifi 11n_disable=1 Linux-Firmware package = 1.180 Nvidia Driver version = 430.34-0ubuntu2 Issue: Problem with kernel 5.2.0-8-generic - Wifi firmware fails to load. Works with 5.0.0.-20-generic kernel. Syslog: Jul 17 15:13:31 Lappy kernel: [ 85.319088] iwlwifi :3b:00.0: Microcode SW error detected. Restarting 0x0. Jul 17 15:13:31 Lappy kernel: [ 85.320158] iwlwifi :3b:00.0: Start IWL Error Log Dump: Jul 17 15:13:31 Lappy kernel: [ 85.320161] iwlwifi :3b:00.0: Status: 0x0080, count: 6 Jul 17 15:13:31 Lappy kernel: [ 85.320162] iwlwifi :3b:00.0: Loaded firmware version: 46.a41adfe7.0 Jul 17 15:13:31 Lappy kernel: [ 85.320164] iwlwifi :3b:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL Jul 17 15:13:31 Lappy kernel: [ 85.320166] iwlwifi :3b:00.0: 0x00A022F0 | trm_hw_status0 Jul 17 15:13:31 Lappy kernel: [ 85.320167] iwlwifi :3b:00.0: 0x | trm_hw_status1 Jul 17 15:13:31 Lappy kernel: [ 85.320168] iwlwifi :3b:00.0: 0x004882F2 | branchlink2 Jul 17 15:13:31 Lappy kernel: [ 85.320169] iwlwifi :3b:00.0: 0x004793A2 | interruptlink1 Jul 17 15:13:31 Lappy kernel: [ 85.320171] iwlwifi :3b:00.0: 0x00480EA2 | interruptlink2 Jul 17 15:13:31 Lappy kernel: [ 85.320172] iwlwifi :3b:00.0: 0x0001A7D2 | data1 Jul 17 15:13:31 Lappy kernel: [ 85.320173] iwlwifi :3b:00.0: 0x1000 | data2 Jul 17 15:13:31 Lappy kernel: [ 85.320174] iwlwifi :3b:00.0: 0xE008 | data3 Jul 17 15:13:31 Lappy kernel: [ 85.320176] iwlwifi :3b:00.0: 0x | beacon time Jul 17 15:13:31 Lappy kernel: [ 85.320177] iwlwifi :3b:00.0: 0x0003ED44 | tsf low Jul 17 15:13:31 Lappy kernel: [ 85.320178] iwlwifi :3b:00.0: 0x | tsf hi Jul 17 15:13:31 Lappy kernel: [ 85.320180] iwlwifi :3b:00.0: 0x | time gp1 Jul 17 15:13:31 Lappy kernel: [ 85.320181] iwlwifi :3b:00.0: 0x0003ED44 | time gp2 Jul 17 15:13:31 Lappy kernel: [ 85.320182] iwlwifi :3b:00.0: 0x0001 | uCode revision
[Kernel-packages] [Bug 1836983] Re: [Intel CyclonePeak] Pairing new BT mouse fails sometimes
commit dbcc2fb9a18de0116bd5d92a9435417b6a842cb8 Author: Amit K Bag Date: Wed Jul 10 16:53:17 2019 +0530 linux-firmware: Update firmware file for Intel Bluetooth 22161 This patch updates new firmware file for Intel Bluetooth 22161 Also it is known as Intel CyclonePeak (CcP). FW Build: REL0310 Release Version: 21.30.0.4 Signed-off-by: Amit K Bag Signed-off-by: Josh Boyer -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1836983 Title: [Intel CyclonePeak] Pairing new BT mouse fails sometimes Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Bionic: New Status in linux-firmware source package in Disco: New Bug description: [Impact] After update the BT firmware, it requires to pair twice to pair a new device. There should be a "SMP: Pairing Request" send from hci0, but it doesn't be submitted in the first time. [Fix] The new firmware fix this issue. [Test] Verified on Dell platforms with BT Designer Mouse(DF:29:ED:BD:82:95) [Regression Potential] Low, the firmware is newly added for new Cyclone Peak wifi/bt, and it won't affect the devices on the market currently. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1836983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836983] [NEW] [Intel CyclonePeak] Pairing new BT mouse fails sometimes
Public bug reported: [Impact] After update the BT firmware, it requires to pair twice to pair a new device. There should be a "SMP: Pairing Request" send from hci0, but it doesn't be submitted in the first time. [Fix] The new firmware fix this issue. [Test] Verified on Dell platforms with BT Designer Mouse(DF:29:ED:BD:82:95) [Regression Potential] Low, the firmware is newly added for new Cyclone Peak wifi/bt, and it won't affect the devices on the market currently. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1836983 Title: [Intel CyclonePeak] Pairing new BT mouse fails sometimes Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Bionic: New Status in linux-firmware source package in Disco: New Bug description: [Impact] After update the BT firmware, it requires to pair twice to pair a new device. There should be a "SMP: Pairing Request" send from hci0, but it doesn't be submitted in the first time. [Fix] The new firmware fix this issue. [Test] Verified on Dell platforms with BT Designer Mouse(DF:29:ED:BD:82:95) [Regression Potential] Low, the firmware is newly added for new Cyclone Peak wifi/bt, and it won't affect the devices on the market currently. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1836983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836971] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1836971 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836971 Title: sched: Prevent CPU lockups when task groups take longer than the period Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: In Progress Bug description: BugLink: https://bugs.launchpad.net/bugs/1836971 [Impact] On machines with extremely high CPU usage, parent task groups which have a large number of children can make the for loop in sched_cfs_period_timer() run until the watchdog fires when the cfs_period_us setting is too short. In this particular case, it is unlikely that the call to hrtimer_forward_now() will return 0, meaning the for loop is never left, and tasks are never rescheduled. The large number of children makes do_sched_cfs_period_timer() take longer than the period, which impacts calls to hrtimer_forward_now(). The kernel will produce this call trace: CPU: 51 PID: 0 Comm: swapper/51 Tainted: P OELK 4.15.0-50-generic #54-Ubuntu Call Trace: ? sched_clock+0x9/0x10 walk_tg_tree_from+0x61/0xd0 ? task_rq_unlock+0x30/0x30 unthrottle_cfs_rq+0xcb/0x1a0 distribute_cfs_runtime+0xd7/0x100 sched_cfs_period_timer+0xd9/0x1a0 ? sched_cfs_slack_timer+0xe0/0xe0 __hrtimer_run_queues+0xdf/0x230 hrtimer_interrupt+0xa0/0x1d0 smp_apic_timer_interrupt+0x6f/0x130 apic_timer_interrupt+0x84/0x90 This has been hit in production in a particularly highly utilised hadoop cluster which is powering an analytics platform. About 30% of the cluster experiences this issue every week, and the machines need a manual reboot to get back online. [Fix] This was fixed in 5.1 upstream with the below commit: commit 2e8e19226398db8265a8e675fcc0118b9e80c9e8 Author: Phil Auld Date: Tue Mar 19 09:00:05 2019 -0400 subject: sched/fair: Limit sched_cfs_period_timer() loop to avoid hard lockup This commit adds a check to see if the loop has run too many times, and if it has, scales up the period and quota, so the timer can complete before the next period expires, which enables the task to be rescheduled normally. Note, 2e8e19226398db8265a8e675fcc0118b9e80c9e8 was included in upstream stable versions 4.4.179, 4.9.171, 4.14.114, 4.19.37, 5.0.10. Please cherry pick 2e8e19226398db8265a8e675fcc0118b9e80c9e8 to all bionic kernels. [Testcase] Kind of hard to reproduce, so this was tested on a production hadoop cluster with extremely high CPU load. I built a test kernel, which is available here: https://launchpad.net/~mruffell/+archive/ubuntu/sf232784-test For unpatched kernels, expect the machine to lockup and print the call trace in the impact section. For patched kernels, if the machine hits the condition, it will print a warning to the kernel log with the new period and quota which has been used: Example from the same hadoop cluster with a machine running the test kernel: % uname -a 4.15.0-50-generic #54+hf232784v20190626b1-Ubuntu % sudo grep cfs /var/log/kern.log.* cfs_period_timer[cpu40]: period too short, scaling up (new cfs_period_us 67872, cfs_quota_us = 3475091) cfs_period_timer[cpu48]: period too short, scaling up (new cfs_period_us 22430, cfs_quota_us = 1148437) cfs_period_timer[cpu48]: period too short, scaling up (new cfs_period_us 25759, cfs_quota_us = 1318908) cfs_period_timer[cpu68]: period too short, scaling up (new cfs_period_us 29583, cfs_quota_us = 1514684) cfs_period_timer[cpu49]: period too short, scaling up (new cfs_period_us 33974, cfs_quota_us = 1739519) cfs_period_timer[cpu3]: period too short, scaling up (new cfs_period_us 39017, cfs_quota_us = 1997729) cfs_period_timer[cpu10]: period too short, scaling up (new cfs_period_us 44809, cfs_quota_us = 2294267) cfs_period_timer[cpu3]: period too short, scaling up (new cfs_period_us 51460, cfs_quota_us = 2634823) cfs_period_timer[cpu3]: period too short, scaling up (new cfs_period_us 59099, cfs_quota_us = 3025929) cfs_period_timer[cpu3]: period too short, scaling up (new cfs_period_us 67872, cfs_quota_us = 3475091) [Regression Potential] This patch was accepted into upstream stable versions 4.4.179, 4.9.171, 4.14.114, 4.19.37, 5.0.10, and is thus treated as stable and
[Kernel-packages] [Bug 1836971] [NEW] sched: Prevent CPU lockups when task groups take longer than the period
Public bug reported: BugLink: https://bugs.launchpad.net/bugs/1836971 [Impact] On machines with extremely high CPU usage, parent task groups which have a large number of children can make the for loop in sched_cfs_period_timer() run until the watchdog fires when the cfs_period_us setting is too short. In this particular case, it is unlikely that the call to hrtimer_forward_now() will return 0, meaning the for loop is never left, and tasks are never rescheduled. The large number of children makes do_sched_cfs_period_timer() take longer than the period, which impacts calls to hrtimer_forward_now(). The kernel will produce this call trace: CPU: 51 PID: 0 Comm: swapper/51 Tainted: P OELK 4.15.0-50-generic #54-Ubuntu Call Trace: ? sched_clock+0x9/0x10 walk_tg_tree_from+0x61/0xd0 ? task_rq_unlock+0x30/0x30 unthrottle_cfs_rq+0xcb/0x1a0 distribute_cfs_runtime+0xd7/0x100 sched_cfs_period_timer+0xd9/0x1a0 ? sched_cfs_slack_timer+0xe0/0xe0 __hrtimer_run_queues+0xdf/0x230 hrtimer_interrupt+0xa0/0x1d0 smp_apic_timer_interrupt+0x6f/0x130 apic_timer_interrupt+0x84/0x90 This has been hit in production in a particularly highly utilised hadoop cluster which is powering an analytics platform. About 30% of the cluster experiences this issue every week, and the machines need a manual reboot to get back online. [Fix] This was fixed in 5.1 upstream with the below commit: commit 2e8e19226398db8265a8e675fcc0118b9e80c9e8 Author: Phil Auld Date: Tue Mar 19 09:00:05 2019 -0400 subject: sched/fair: Limit sched_cfs_period_timer() loop to avoid hard lockup This commit adds a check to see if the loop has run too many times, and if it has, scales up the period and quota, so the timer can complete before the next period expires, which enables the task to be rescheduled normally. Note, 2e8e19226398db8265a8e675fcc0118b9e80c9e8 was included in upstream stable versions 4.4.179, 4.9.171, 4.14.114, 4.19.37, 5.0.10. Please cherry pick 2e8e19226398db8265a8e675fcc0118b9e80c9e8 to all bionic kernels. [Testcase] Kind of hard to reproduce, so this was tested on a production hadoop cluster with extremely high CPU load. I built a test kernel, which is available here: https://launchpad.net/~mruffell/+archive/ubuntu/sf232784-test For unpatched kernels, expect the machine to lockup and print the call trace in the impact section. For patched kernels, if the machine hits the condition, it will print a warning to the kernel log with the new period and quota which has been used: Example from the same hadoop cluster with a machine running the test kernel: % uname -a 4.15.0-50-generic #54+hf232784v20190626b1-Ubuntu % sudo grep cfs /var/log/kern.log.* cfs_period_timer[cpu40]: period too short, scaling up (new cfs_period_us 67872, cfs_quota_us = 3475091) cfs_period_timer[cpu48]: period too short, scaling up (new cfs_period_us 22430, cfs_quota_us = 1148437) cfs_period_timer[cpu48]: period too short, scaling up (new cfs_period_us 25759, cfs_quota_us = 1318908) cfs_period_timer[cpu68]: period too short, scaling up (new cfs_period_us 29583, cfs_quota_us = 1514684) cfs_period_timer[cpu49]: period too short, scaling up (new cfs_period_us 33974, cfs_quota_us = 1739519) cfs_period_timer[cpu3]: period too short, scaling up (new cfs_period_us 39017, cfs_quota_us = 1997729) cfs_period_timer[cpu10]: period too short, scaling up (new cfs_period_us 44809, cfs_quota_us = 2294267) cfs_period_timer[cpu3]: period too short, scaling up (new cfs_period_us 51460, cfs_quota_us = 2634823) cfs_period_timer[cpu3]: period too short, scaling up (new cfs_period_us 59099, cfs_quota_us = 3025929) cfs_period_timer[cpu3]: period too short, scaling up (new cfs_period_us 67872, cfs_quota_us = 3475091) [Regression Potential] This patch was accepted into upstream stable versions 4.4.179, 4.9.171, 4.14.114, 4.19.37, 5.0.10, and is thus treated as stable and trusted by the community. Xenial received this patch in 4.4.0-150.176, as per LP #1828420 Disco will receive this patch in the next version, as per LP #1830922 Eoan already has the patch, being based on 5.2. While this does effect a core part of the kernel, the scheduler, the patch has been extensively tested, and it has been proven in production environments, so the overall risk is low. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Bionic) Importance: Medium Assignee: Matthew Ruffell (mruffell) Status: In Progress ** Tags: sts ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: sts ** Description changed: - BugLink: https://bugs.launchpad.net/bugs/ + BugLink: https://bugs.launchpad.net/bugs/1836971 [Impact] - On machines with extremely high CPU usage, parent task groups which have a large - number of children can make the for loop in sched_cfs_period_timer() run until - the watchdog fires when the cfs_period_us setting is too short. + On machines with extremely high CPU
[Kernel-packages] [Bug 1836456] Re: [ThinkPad S1 Yoga] Machine Immediately Wakes Up From Suspend
@kaihengfeng This did not solve the issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836456 Title: [ThinkPad S1 Yoga] Machine Immediately Wakes Up From Suspend Status in linux package in Ubuntu: Confirmed Bug description: I am using Ubuntu 18.04.2 on a Lenovo ThinkPad S1 Yoga. Unfortunately when I suspend the machine to throw it into my bag, it immediately wakes up causing an issue where the machine will run hot in 85 - 90 degree weather while I am in town. This is not a firmware issue as I have downgraded the BIOS and I have also observed how it worked fine under Arch Linux. I am not entirely sure which package is responsible to interact with acpi under Debian/Ubuntu $ lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 Here is my version.log output, I will provide them as separate attachments per the guidelines Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lalo 1814 F pulseaudio /dev/snd/controlC1: lalo 1814 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=/dev/sda3 InstallationDate: Installed on 2019-07-01 (11 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 20C00063US Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic root=UUID=c9ed5b87-08bb-441b-9d27-ed5b3f05260e ro quiet splash resume=/dev/sda3 vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-25-generic N/A linux-backports-modules-4.18.0-25-generic N/A linux-firmware 1.173.8 Tags: bionic Uname: Linux 4.18.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/28/2018 dmi.bios.vendor: LENOVO dmi.bios.version: B0ET43WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20C00063US dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrB0ET43WW(1.30):bd09/28/2018:svnLENOVO:pn20C00063US:pvrThinkPadS1Yoga:rvnLENOVO:rn20C00063US:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad S1 Yoga dmi.product.name: 20C00063US dmi.product.sku: LENOVO_MT_20C0_BU_Think_FM_ThinkPad S1 Yoga dmi.product.version: ThinkPad S1 Yoga dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836456/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836968] Re: Bionic update: upstream stable patchset 2019-07-17
** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + upstream stable patchset 2019-07-17 -upstream stable patchset 2019-07-17 -from git://git.kernel.org/ + Ported from the following upstream stable releases: + v4.14.83, v4.19.4, + v4.14.84, v4.19.5, + v4.14.85, v4.19.6, + v4.14.86, v4.19.7 + + from git://git.kernel.org/ ** Description changed: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2019-07-17 - Ported from the following upstream stable releases: - v4.14.83, v4.19.4, - v4.14.84, v4.19.5, - v4.14.85, v4.19.6, - v4.14.86, v4.19.7 + Ported from the following upstream stable releases: + v4.14.83, v4.19.4, + v4.14.84, v4.19.5, + v4.14.85, v4.19.6, + v4.14.86, v4.19.7 from git://git.kernel.org/ + + flow_dissector: do not dissect l4 ports for fragments + ibmvnic: fix accelerated VLAN handling + ip_tunnel: don't force DF when MTU is locked + ipv6: Fix PMTU updates for UDP/raw sockets in presence of VRF + net-gro: reset skb->pkt_type in napi_reuse_skb() + sctp: not allow to set asoc prsctp_enable by sockopt + tg3: Add PHY reset for 5717/5719/5720 in change ring and flow control paths + tuntap: fix multiqueue rx + net: systemport: Protect stop from timeout + net: qualcomm: rmnet: Fix incorrect assignment of real_dev + net: dsa: microchip: initialize mutex before use + sctp: fix strchange_flags name for Stream Change Event + net: phy: mdio-gpio: Fix working over slow can_sleep GPIOs + sctp: not increase stream's incnt before sending addstrm_in request + mlxsw: spectrum: Fix IP2ME CPU policer configuration + net: smsc95xx: Fix MTU range + usbnet: smsc95xx: disable carrier check while suspending + inet: frags: better deal with smp races + ARM: dts: r8a7791: Correct critical CPU temperature + ARM: dts: r8a7793: Correct critical CPU temperature + net: bcmgenet: protect stop from timeout + tcp: Fix SOF_TIMESTAMPING_RX_HARDWARE to use the latest timestamp during TCP coalescing + tipc: don't assume linear buffer when reading ancillary data + tipc: fix link re-establish failure + net/mlx5e: Claim TC hw offloads support only under a proper build config + net/mlx5e: Adjust to max number of channles when re-attaching + net/mlx5e: Fix selftest for small MTUs + l2tp: fix a sock refcnt leak in l2tp_tunnel_register + net/mlx5e: IPoIB, Reset QP after channels are closed + net: dsa: mv88e6xxx: Fix clearing of stats counters + net: phy: realtek: fix RTL8201F sysfs name + sctp: define SCTP_SS_DEFAULT for Stream schedulers + rxrpc: Fix lockup due to no error backoff after ack transmit error + cifs: don't dereference smb_file_target before null check + cifs: fix return value for cifs_listxattr + arm64: kprobe: make page to RO mode when allocate it + ixgbe: fix MAC anti-spoofing filter after VFLR + reiserfs: propagate errors from fill_with_dentries() properly + hfs: prevent btree data loss on root split + hfsplus: prevent btree data loss on root split + um: Give start_idle_thread() a return code + drm/edid: Add 6 bpc quirk for BOE panel. + platform/x86: intel_telemetry: report debugfs failure + clk: fixed-rate: fix of_node_get-put imbalance + perf symbols: Set PLT entry/header sizes properly on Sparc + fs/exofs: fix potential memory leak in mount option parsing + clk: samsung: exynos5420: Enable PERIS clocks for suspend + apparmor: Fix uninitialized value in aa_split_fqname + x86/earlyprintk: Add a force option for
[Kernel-packages] [Bug 1836211] Re: bcmwl fails to install with recent Eoan (Bad return status for module build on kernel: 5.0.0-20-generic)
** Changed in: bcmwl (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1836211 Title: bcmwl fails to install with recent Eoan (Bad return status for module build on kernel: 5.0.0-20-generic) Status in bcmwl package in Ubuntu: Fix Released Bug description: With recent Eoan builds, bcmwl fails to install completely, . It had worked when I installed Eoan a couple weeks ago, but not when I first tried to clean install on 9 July until today. (I've unfortunately erased the old, working installation so I don't have more details.) $ sudo apt install bcmwl-kernel-source Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: dkms Suggested packages: menu The following NEW packages will be installed: bcmwl-kernel-source dkms 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 1,610 kB of archives. After this operation, 8,359 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 dkms all 2.7.1-1ubuntu1 [66.5 kB] Get:2 http://us.archive.ubuntu.com/ubuntu eoan/restricted amd64 bcmwl-kernel-source amd64 6.30.223.271+bdcom-0ubuntu5 [1,544 kB] Fetched 1,610 kB in 0s (4,097 kB/s) Selecting previously unselected package dkms. (Reading database ... 122315 files and directories currently installed.) Preparing to unpack .../dkms_2.7.1-1ubuntu1_all.deb ... Unpacking dkms (2.7.1-1ubuntu1) ... Selecting previously unselected package bcmwl-kernel-source. Preparing to unpack .../bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu5_amd64.deb ... Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu5) ... Setting up dkms (2.7.1-1ubuntu1) ... Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu5) ... Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.0.0-20-generic Building for architecture x86_64 Building initial module for 5.0.0-20-generic Error! Bad return status for module build on kernel: 5.0.0-20-generic (x86_64) Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more information. dpkg: error processing package bcmwl-kernel-source (--configure): installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 Processing triggers for man-db (2.8.5-2) ... Errors were encountered while processing: bcmwl-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jul 11 09:02:53 2019 InstallationDate: Installed on 2019-07-11 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190711) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1836211/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836968] [NEW] Bionic update: upstream stable patchset 2019-07-17
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2019-07-17 from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836968 Title: Bionic update: upstream stable patchset 2019-07-17 Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2019-07-17 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836968/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836876] Re: linux-raspi2: 4.4.0-1116.125 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-xenial ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1836875 (pi2-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1836880 - phase: Holding before Promote to Proposed - phase-changed: Wednesday, 17. July 2019 13:40 UTC + phase: Ready for Promote to Proposed + phase-changed: Wednesday, 17. July 2019 20:42 UTC reason: - promote-to-proposed: Holding -- master bug not ready for proposed + promote-to-proposed: Pending -- ready for review variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1836876 Title: linux-raspi2: 4.4.0-1116.125 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1836875 (pi2-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1836880 phase: Ready for Promote to Proposed phase-changed: Wednesday, 17. July 2019 20:42 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1836876/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834915] Re: linux-fips: 4.4.0-1014.19 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1836880 phase: Holding before Promote to Proposed phase-changed: Wednesday, 17. July 2019 10:05 UTC reason: - promote-to-proposed: Holding -- master bug not ready for proposed + promote-to-proposed: Holding -- manual kernel-block/kernel-block-ppa present variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834915 Title: linux-fips: 4.4.0-1014.19 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1836880 phase: Holding before Promote to Proposed phase-changed: Wednesday, 17. July 2019 10:05 UTC reason: promote-to-proposed: Holding -- manual kernel-block/kernel-block-ppa present variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834915/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836878] Re: linux-snapdragon: 4.4.0-1120.126 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-xenial ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1836877 (dragonboard-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1836880 - phase: Holding before Promote to Proposed - phase-changed: Wednesday, 17. July 2019 13:23 UTC + phase: Ready for Promote to Proposed + phase-changed: Wednesday, 17. July 2019 20:42 UTC reason: - promote-to-proposed: Holding -- master bug not ready for proposed + promote-to-proposed: Pending -- ready for review variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1836878 Title: linux-snapdragon: 4.4.0-1120.126 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1836877 (dragonboard-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1836880 phase: Ready for Promote to Proposed phase-changed: Wednesday, 17. July 2019 20:42 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1836878/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836925] Re: linux-ibm-gt: 4.15.0-1028.30 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1834954 - phase: Holding before Promote to Proposed - phase-changed: Wednesday, 17. July 2019 16:09 UTC + phase: Ready for Promote to Proposed + phase-changed: Wednesday, 17. July 2019 20:40 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa meta:building + promote-to-proposed: Pending -- ready for review variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836925 Title: linux-ibm-gt: 4.15.0-1028.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Ready for Promote to Proposed phase-changed: Wednesday, 17. July 2019 20:40 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1836925/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836880] Re: linux: 4.4.0-156.183 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-xenial ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1836879 (trusty/linux-lts-xenial) derivatives: bug 1834908 (linux-aws), bug 1834909 (linux-kvm), bug 1834915 (linux-fips), bug 1836874 (pc-kernel), bug 1836876 (linux-raspi2), bug 1836878 (linux-snapdragon) -- swm properties -- - phase: Holding before Promote to Proposed - phase-changed: Wednesday, 17. July 2019 12:03 UTC + boot-testing-requested: true + phase: Ready for Promote to Proposed + phase-changed: Wednesday, 17. July 2019 20:34 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa meta:building + promote-to-proposed: Pending -- ready for review variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836880 Title: linux: 4.4.0-156.183 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1836879 (trusty/linux-lts-xenial) derivatives: bug 1834908 (linux-aws), bug 1834909 (linux-kvm), bug 1834915 (linux-fips), bug 1836874 (pc-kernel), bug 1836876 (linux-raspi2), bug 1836878 (linux-snapdragon) -- swm properties -- boot-testing-requested: true phase: Ready for Promote to Proposed phase-changed: Wednesday, 17. July 2019 20:34 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1836880/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795659] Re: kernel panic using CIFS share in smb2_push_mandatory_locks()
SRU request sent to kernel-team mailing list: https://lists.ubuntu.com/archives/kernel-team/2019-July/102354.html Cheers, Guilherme -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1795659 Title: kernel panic using CIFS share in smb2_push_mandatory_locks() Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Bug description: [Impact] * We got reports of a kernel crash in cifs module with the following signature: BUG: unable to handle kernel NULL pointer dereference at 0038 IP: smb2_push_mandatory_locks+0x10e/0x3b0 [cifs] PGD 0 P4D 0 RIP: 0010:smb2_push_mandatory_locks+0x10e/0x3b0 [cifs] Call Trace: cifs_oplock_break+0x12f/0x3d0 [cifs] process_one_work+0x14d/0x410 worker_thread+0x4b/0x460 kthread+0x105/0x140 [...] * Low-level analysis (decodecode script output and the objdump of the function) revealed that we are crashing in a NULL ptr dereference when trying to access "cfile->tlink"; below, a snippet of the objdump at function smb2_push_mandatory_locks(): [...] mov0x10(%r14),%r15 # %r15 = cifsFileInfo *cfile mov0x18(%r14),%rbx # %rbx = cifsLockInfo *li = (fdlocks->locks) lea0x18(%r14),%r12 mov0x90(%r15),%rax # %rax = struct tcon_link *tlink (cfile->tlink) cmp%r12,%rbx mov0x38(%rax),%rax # <--- TRAP [trying to get cifs_tcon *tl_tcon] [...] * After discussing the issue with CIFS maintainers (Steve French and Pavel Shilovsky) they suggested commit b98749cac4a6 ("CIFS: keep FileInfo handle live during oplock break") [http://git.kernel.org/linus/b98749cac4a6] as a fix for multiple reports of this kind of crash. * The fix was sent to stable kernels and is present in Ubuntu kernels 5.0 and newer. We are requesting the SRU for this patch here in order to fix the crashes, after reports of successful testing with the patch (see below section) and since the patch is restricted to the cifs module scope and accepted on linux stable. * Alternatively the issue is known to be avoided when oplocks are disabled using "cifs.enable_oplocks=N" module parameter. [Test case] * Unfortunately we cannot reproduce the issue. The patch proposed here was validated by us with xfstests (instructions followed from https://wiki.samba.org/index.php/Xfstesting-cifs) and fio. Also, we have a user report of test validation using LISA (https://github.com/LIS/LISAv2). * Using xfstest with the exclusions proposed in the link above we managed to get the same results as a non-patched kernel, i.e., the same tests failed in both kernels, we didn't get worse results with the patch. Fio also didn't show noticeable performance regression with the patch. [Regression potential] * The patch was validated by the cifs filesystem maintainers (in fact they suggested its inclusion in Ubuntu) and by the aforementioned tests; also, the scope is restricted to cifs only so the likelihood of regressions is considered low. * Due to the nature of the code modification (add a new reference of a file handler and manipulate it in different places), I consider that if we have a regression it'll manifest as deadlock/blocked tasks, not something more serious like crashes or data corruption. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795659/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836630] Re: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend
I wonder if removing that line would cause issues on kernels before PCI: PM: Skip devices in D0 for suspend-to-idle, like the bionic kernel? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in Linux: Unknown Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers package in Ubuntu: New Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: system76 1721 F pulseaudio /dev/snd/controlC0: system76 1721 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 MachineType: System76 Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux-hwe-edge ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: oryp5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOryxPro:rvroryp5:cvnSystem76:ct10:cvroryp5: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1836630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824981] Re: cifs set_oplock buffer overflow in strcat
** Description changed: [Impact] * We got reports of a kernel crash in cifs module with the following signature: detected buffer overflow in strcat kernel BUG at <...>/lib/string.c:1052! invalid opcode: [#1] SMP PTI RIP: 0010:fortify_panic+0x13/0x1f Call Trace: - smb21_set_oplock_level+0xde/0x190 [cifs] - smb3_set_oplock_level+0x22/0x90 [cifs] - smb2_set_fid+0x76/0xb0 [cifs] - cifs_new_fileinfo+0x268/0x3c0 [cifs] - ? smb2_get_lease_key+0x40/0x40 [cifs] - ? cifs_new_fileinfo+0x268/0x3c0 [cifs] - cifs_open+0x57c/0x8d0 [cifs] - do_dentry_open+0x1fe/0x320 + smb21_set_oplock_level+0xde/0x190 [cifs] + smb3_set_oplock_level+0x22/0x90 [cifs] + smb2_set_fid+0x76/0xb0 [cifs] + cifs_new_fileinfo+0x268/0x3c0 [cifs] + ? smb2_get_lease_key+0x40/0x40 [cifs] + ? cifs_new_fileinfo+0x268/0x3c0 [cifs] + cifs_open+0x57c/0x8d0 [cifs] + do_dentry_open+0x1fe/0x320 [...] * By analyzing the code of smb21_set_oplock_level(), we've noticed the only way fortify function strcat() would get overflow was if the value of cinode->oplock got corrupted in a another thread leading to a buffer write bigger then buffer size. In this function, the 'message' buffer writes are governed by cinode->oplock, so only a different thread cleaning the oplock value would lead to 'message' overflow. * By the same time we worked this analysis, a fix was proposed upstream for this issue in the form of commit 6a54b2e002c9 ("cifs: fix strcat buffer overflow and reduce raciness in smb21_set_oplock_level()"), by the same reporter of this LP. The fix is simple and directly addresses this problem, so we hereby request its SRU into Bionic kernel - it's - already present in Ubuntu kernel version 5.0 and newer, as well as linux - stable branches. + already present in linux stable branches and will soon be in Ubuntu + kernel version 5.0 (when it gets rebased with 5.0.19). [Test case] * Unfortunately we cannot reproduce the issue. The patch proposed here was - validated by us with xfstests (instructions followed from + validated by us with xfstests (instructions followed from https://wiki.samba.org/index.php/Xfstesting-cifs) and fio. * Using xfstest with the exclusions proposed in the link above we managed to get the same results as a non-patched kernel, i.e., the same tests failed in both kernels, we didn't get worse results with the patch. Fio also didn't show noticeable performance regression with the patch. [Regression potential] * The patch was validated by the cifs filesystem maintainers and by the aforementioned tests; also, the scope is restricted to cifs only so the likelihood of regressions is considered low. The commit introduces no functional changes and the only affected path was just refactored in a way to prevent overflow and reduce race potential. ** Description changed: [Impact] * We got reports of a kernel crash in cifs module with the following signature: detected buffer overflow in strcat kernel BUG at <...>/lib/string.c:1052! invalid opcode: [#1] SMP PTI RIP: 0010:fortify_panic+0x13/0x1f Call Trace: smb21_set_oplock_level+0xde/0x190 [cifs] smb3_set_oplock_level+0x22/0x90 [cifs] smb2_set_fid+0x76/0xb0 [cifs] cifs_new_fileinfo+0x268/0x3c0 [cifs] ? smb2_get_lease_key+0x40/0x40 [cifs] ? cifs_new_fileinfo+0x268/0x3c0 [cifs] cifs_open+0x57c/0x8d0 [cifs] do_dentry_open+0x1fe/0x320 [...] * By analyzing the code of smb21_set_oplock_level(), we've noticed the only way fortify function strcat() would get overflow was if the value of cinode->oplock got corrupted in a another thread leading to a buffer write bigger then buffer size. In this function, the 'message' buffer writes are governed by cinode->oplock, so only a different thread cleaning the oplock value would lead to 'message' overflow. * By the same time we worked this analysis, a fix was proposed upstream for this issue in the form of commit 6a54b2e002c9 ("cifs: fix strcat buffer overflow and reduce raciness in smb21_set_oplock_level()"), by the same reporter of this LP. The fix is simple and directly addresses this problem, so we hereby request its SRU into Bionic kernel - it's - already present in linux stable branches and will soon be in Ubuntu - kernel version 5.0 (when it gets rebased with 5.0.19). + already present in linux stable branches. [Test case] * Unfortunately we cannot reproduce the issue. The patch proposed here was validated by us with xfstests (instructions followed from https://wiki.samba.org/index.php/Xfstesting-cifs) and fio. * Using xfstest with the exclusions proposed in the link above we managed to get the same results as a non-patched kernel, i.e., the same tests failed in both kernels, we didn't get worse results with the patch. Fio also didn't show noticeable performance regression with the patch. [Regression potential] * The patch was
[Kernel-packages] [Bug 1824981] Re: cifs set_oplock buffer overflow in strcat
** Description changed: - Ubuntu 18.04.2 LTS - Linux SRV013 4.15.0-47-generic #50-Ubuntu SMP Wed Mar 13 10:44:52 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux + [Impact] - DELL R740, 2 CPU (40 Cores, 80 Threads), 384 GiB RAM + * We got reports of a kernel crash in cifs module with the following + signature: - top - 12:39:53 up 3:41, 4 users, load average: 66.19, 64.06, 76.90 - Tasks: 1076 total, 1 running, 675 sleeping, 12 stopped, 1 zombie - %Cpu(s): 28.2 us, 0.3 sy, 0.0 ni, 71.5 id, 0.0 wa, 0.0 hi, 0.1 si, 0.0 st - KiB Mem : 39483801+total, 24077185+free, 57428284 used, 96637872 buff/cache - KiB Swap: 999420 total, 999420 free,0 used. 33477683+avail Mem + detected buffer overflow in strcat + kernel BUG at <...>/lib/string.c:1052! + invalid opcode: [#1] SMP PTI + RIP: 0010:fortify_panic+0x13/0x1f + Call Trace: + smb21_set_oplock_level+0xde/0x190 [cifs] + smb3_set_oplock_level+0x22/0x90 [cifs] + smb2_set_fid+0x76/0xb0 [cifs] + cifs_new_fileinfo+0x268/0x3c0 [cifs] + ? smb2_get_lease_key+0x40/0x40 [cifs] + ? cifs_new_fileinfo+0x268/0x3c0 [cifs] + cifs_open+0x57c/0x8d0 [cifs] + do_dentry_open+0x1fe/0x320 + [...] + * By analyzing the code of smb21_set_oplock_level(), we've noticed the + only way fortify function strcat() would get overflow was if the value + of cinode->oplock got corrupted in a another thread leading to a buffer + write bigger then buffer size. In this function, the 'message' buffer + writes are governed by cinode->oplock, so only a different thread + cleaning the oplock value would lead to 'message' overflow. - We've seen the following bug many times since we introduced new machines - running Ubuntu 18. Wasn't an issue older machines running Ubuntu 16. - Three different machines are affected, so it's rather not a hardware - issue. + * By the same time we worked this analysis, a fix was proposed upstream + for this issue in the form of commit 6a54b2e002c9 ("cifs: fix strcat + buffer overflow and reduce raciness in smb21_set_oplock_level()"), by + the same reporter of this LP. The fix is simple and directly addresses + this problem, so we hereby request its SRU into Bionic kernel - it's + already present in Ubuntu kernel version 5.0 and newer, as well as linux + stable branches. + [Test case] - | detected buffer overflow in strcat - | [ cut here ] - | kernel BUG at /build/linux-6ZmFRN/linux-4.15.0/lib/string.c:1052! - | invalid opcode: [#1] SMP PTI - | Modules linked in: [...] - | Hardware name: Dell Inc. PowerEdge R740/0923K0, BIOS 1.6.11 11/20/2018 - | RIP: 0010:fortify_panic+0x13/0x22 - | [...] - | Call Trace: - | smb21_set_oplock_level+0x147/0x1a0 [cifs] - | smb3_set_oplock_level+0x22/0x90 [cifs] - | smb2_set_fid+0x76/0xb0 [cifs] - | cifs_new_fileinfo+0x259/0x390 [cifs] - | ? smb2_get_lease_key+0x40/0x40 [cifs] - | ? cifs_new_fileinfo+0x259/0x390 [cifs] - | cifs_open+0x3db/0x8d0 [cifs] - | [...] + * Unfortunately we cannot reproduce the issue. The patch proposed here was + validated by us with xfstests (instructions followed from + https://wiki.samba.org/index.php/Xfstesting-cifs) and fio. - (Full dmesg output attached) + * Using xfstest with the exclusions proposed in the link above we + managed to get the same results as a non-patched kernel, i.e., the same + tests failed in both kernels, we didn't get worse results with the + patch. Fio also didn't show noticeable performance regression with the + patch. - After hitting this bug there are many cifs related dmesg entries, - processes lock up and eventually the systems freezes. + [Regression potential] - - The share is mounted using: - //server/share /mnt/server/ cifs defaults,auto,iocharset=utf8,noperm,file_mode=0777,dir_mode=0777,credentials=/root/passwords/share,domain=myDomain,uid=myUser,gid=10513,mfsymlinks - - Currently we're testing the cifs mount options "cache=none" as the bug - seems to be oplock related. + * The patch was validated by the cifs filesystem maintainers and by the + aforementioned tests; also, the scope is restricted to cifs only so the + likelihood of regressions is considered low. The commit introduces no + functional changes and the only affected path was just refactored in a + way to prevent overflow and reduce race potential. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824981 Title: cifs set_oplock buffer overflow in strcat Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: Won't Fix Status in linux source package in Disco: In Progress Status in linux source package in Eoan: Fix Released Bug description: [Impact] * We got reports of a kernel crash in cifs module with the following signature: detected buffer overflow in strcat kernel BUG at <...>/lib/string.c:1052! invalid
[Kernel-packages] [Bug 1795659] Re: kernel panic using CIFS share in smb2_push_mandatory_locks()
** Summary changed: - kernel panic using CIFS share smb2_push_mandatory_locks + kernel panic using CIFS share in smb2_push_mandatory_locks() ** Description changed: - Description:Ubuntu 16.04.5 LTS - Release:16.04 + [Impact] - Kernel: 4.15.0-36-generic #39~16.04.1-Ubuntu SMP Tue Sep 25 08:59:23 UTC - 2018 x86_64 x86_64 x86_64 GNU/Linux + * We got reports of a kernel crash in cifs module with the following + signature: - Under load, getting a system crash when accessing files on an SMB3 - share. dmesg from crash attached. I can upload the crash dump if needed. + BUG: unable to handle kernel NULL pointer dereference at 0038 + IP: smb2_push_mandatory_locks+0x10e/0x3b0 [cifs] + PGD 0 P4D 0 + RIP: 0010:smb2_push_mandatory_locks+0x10e/0x3b0 [cifs] + Call Trace: + cifs_oplock_break+0x12f/0x3d0 [cifs] + process_one_work+0x14d/0x410 + worker_thread+0x4b/0x460 + kthread+0x105/0x140 + [...] - Share is mounted with the following options: + Low-level analysis (decodecode script output and the objdump of the + function) revealed that we are crashing in a NULL ptr dereference when + trying to access "cfile->tlink"; below, a snippet of the objdump at + function smb2_push_mandatory_locks(): - "ro,_netdev,username=*,password=*,domain=*,vers=3.02,sec=ntlmsspi,nounix,noserverino,nobrl,cache=none" + [...] + mov0x10(%r14),%r15 # %r15 = cifsFileInfo *cfile + mov0x18(%r14),%rbx # %rbx = cifsLockInfo *li = (fdlocks->locks) + lea0x18(%r14),%r12 + mov0x90(%r15),%rax # %rax = struct tcon_link *tlink (cfile->tlink) + cmp%r12,%rbx + mov0x38(%rax),%rax # <--- TRAP [trying to get cifs_tcon *tl_tcon] + [...] - Dmesg points to the cifs module + * After discussing the issue with CIFS maintainers (Steve French and + Pavel Shilovsky) they suggested commit b98749cac4a6 ("CIFS: keep + FileInfo handle live during oplock break") + [http://git.kernel.org/linus/b98749cac4a6] as a fix for multiple reports + of this kind of crash. - [ 2192.662345] BUG: unable to handle kernel NULL pointer dereference at 0038 - [ 2192.662407] IP: smb2_push_mandatory_locks+0x10e/0x3b0 [cifs] + * The fix was sent to stable kernels and is present in Ubuntu kernels + 5.0 and newer. We are requesting the SRU for this patch here in order to + fix the crashes, after reports of successful testing with the patch (see + below section) and since the patch is restricted to the cifs module + scope and accepted on linux stable. + + * Alternatively the issue is known to be avoided when oplocks are + disabled using "cifs.enable_oplocks=N" module parameter. + + [Test case] + + * Unfortunately we cannot reproduce the issue. The patch proposed here was + validated by us with xfstests (instructions followed from + https://wiki.samba.org/index.php/Xfstesting-cifs) and fio. Also, we + have a user report of test validation using LISA (https://github.com/LIS/LISAv2). + + * Using xfstest with the exclusions proposed in the link above we + managed to get the same results as a non-patched kernel, i.e., the same + tests failed in both kernels, we didn't get worse results with the + patch. Fio also didn't show noticeable performance regression with the + patch. + + [Regression potential] + + * The patch was validated by the cifs filesystem maintainers (in fact + they suggested its inclusion in Ubuntu) and by the aforementioned tests; + also, the scope is restricted to cifs only so the likelihood of + regressions is considered low. + + *Due to the nature of the code modification (add a new reference of a + file handler and manipulate it in different places), I consider that if + we have a regression it'll manifest as deadlock/blocked tasks, not + something more serious like crashes or data corruption. ** Description changed: [Impact] * We got reports of a kernel crash in cifs module with the following signature: BUG: unable to handle kernel NULL pointer dereference at 0038 IP: smb2_push_mandatory_locks+0x10e/0x3b0 [cifs] PGD 0 P4D 0 RIP: 0010:smb2_push_mandatory_locks+0x10e/0x3b0 [cifs] Call Trace: - cifs_oplock_break+0x12f/0x3d0 [cifs] - process_one_work+0x14d/0x410 - worker_thread+0x4b/0x460 - kthread+0x105/0x140 + cifs_oplock_break+0x12f/0x3d0 [cifs] + process_one_work+0x14d/0x410 + worker_thread+0x4b/0x460 + kthread+0x105/0x140 [...] - Low-level analysis (decodecode script output and the objdump of the + * Low-level analysis (decodecode script output and the objdump of the function) revealed that we are crashing in a NULL ptr dereference when trying to access "cfile->tlink"; below, a snippet of the objdump at function smb2_push_mandatory_locks(): [...] mov0x10(%r14),%r15 # %r15 = cifsFileInfo *cfile mov0x18(%r14),%rbx # %rbx = cifsLockInfo *li = (fdlocks->locks) lea0x18(%r14),%r12 mov0x90(%r15),%rax # %rax = struct tcon_link *tlink (cfile->tlink) cmp%r12,%rbx mov0x38(%rax),%rax
[Kernel-packages] [Bug 1831775] Re: ss seems broken when using multiple filters in the same cmdline
According to LP: #1836929 I've done the following merge request: https://code.launchpad.net/~rafaeldtinoco/britney/hints- ubuntu/+merge/370268 requesting tests before eoan to be classified as "bad tests". Thus, those failures are "false positives" and SRU is good. I have also verified the SRU is it is good. ** Tags removed: verification-needed verification-needed-disco ** Tags added: verification-done verification-done-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1831775 Title: ss seems broken when using multiple filters in the same cmdline Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Cosmic: Won't Fix Status in iproute2 source package in Disco: Fix Committed Status in iproute2 source package in Eoan: Fix Released Bug description: [Impact] * ss won't be able to run commands with single filters inside parentheses, like: "( sport == :X )", for example. * A workaround is to remove "( )" from single filters, since it looks the issue does not affect 2 filters being put together in the same parentheses, like: " ( X and Y ) and Y " instead of ( X and Y ) and ( Y )". * CTDB is unable to use ss filter to obtain nodes public IP addresses in order to fail over services (LP: #722201). [Test Case] * Having an Ubuntu Cosmic, Disco or Eoan, try to execute the following command: $ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Independent of the IPs or ports being used. Copying and pasting the command should be enough for you to know if you are affected. Bad Result: ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message ... Expected Result: Recv-QSend-Q Local Address:Port Peer Address:Port ... * test case was discovered during CTDB scripts execution [Regression Potential] * biggest risk would be to affect ss interpreter (worst case scenario). * the proposed patch is based in upstream fix and was tested against the same issue reported as the reproducer (above) and some other generic ss commands. * any problem here is unlikely to change iproute2 most important command interpreter, "ip", since the patch is applied against ss code. [Other Info] ORIGINAL DESCRIPTION: Investigating an issue for CTDB (LP: #722201), after suggesting a fix on ss syntax to CTDB upstream project, we discovered that "ss" seems to be broken in Ubuntu since Ubuntu Cosmic: # Debian Sid inaddy@workstation:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-QSend-Q Local Address:Port Peer Address:Port # Ubuntu Ubuntu 16.04 LTS (Xenial Xerus) (c)inaddy@xenial:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-QLocal Address:Port Peer Address:Port # Ubuntu 18.04 LTS (Bionic Beaver) (c)inaddy@bionic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-Q Local Address:Port Peer Address:Port # Ubuntu 18.10 (Cosmic Cuttlefish) (c)inaddy@cosmic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message # Ubuntu 19.04 (Disco Dingo) (c)inaddy@disco:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] # Ubuntu 19.10 (Eoan Ermine) (c)inaddy@eoan:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] I have generated a pkg using upstream iproute2 source code and it does not suffer the issue. I have generated a package using Ubuntu cosmic source package, without debian/patches/*, and verified the issue still persists (not being introduced by any of our packages, and being present if vanilla upstream version used in Cosmic). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1831775/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1836925] Re: linux-ibm-gt: 4.15.0-1028.30 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1834954 phase: Holding before Promote to Proposed phase-changed: Wednesday, 17. July 2019 16:09 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building + promote-to-proposed: Ongoing -- builds not complete in ppa meta:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836925 Title: linux-ibm-gt: 4.15.0-1028.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1834954 phase: Holding before Promote to Proposed phase-changed: Wednesday, 17. July 2019 16:09 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa meta:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1836925/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836880] Re: linux: 4.4.0-156.183 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1836879 (trusty/linux-lts-xenial) derivatives: bug 1834908 (linux-aws), bug 1834909 (linux-kvm), bug 1834915 (linux-fips), bug 1836874 (pc-kernel), bug 1836876 (linux-raspi2), bug 1836878 (linux-snapdragon) -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Wednesday, 17. July 2019 12:03 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building + promote-to-proposed: Ongoing -- builds not complete in ppa meta:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836880 Title: linux: 4.4.0-156.183 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1836879 (trusty/linux-lts-xenial) derivatives: bug 1834908 (linux-aws), bug 1834909 (linux-kvm), bug 1834915 (linux-fips), bug 1836874 (pc-kernel), bug 1836876 (linux-raspi2), bug 1836878 (linux-snapdragon) -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Wednesday, 17. July 2019 12:03 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa meta:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1836880/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835677] Re: Megal33t bug: touchpad with mousewheel is broken >:]
Hi. I'm marking this as invalid. My problem with flicker/tearing seems lie elsewhere. :) https://bugzilla.redhat.com/show_bug.cgi?id=1730272 https://bugzilla.redhat.com/show_bug.cgi?id=1729666 ** Bug watch added: Red Hat Bugzilla #1730272 https://bugzilla.redhat.com/show_bug.cgi?id=1730272 ** Bug watch added: Red Hat Bugzilla #1729666 https://bugzilla.redhat.com/show_bug.cgi?id=1729666 ** No longer affects: linux (Fedora) ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835677 Title: Megal33t bug: touchpad with mousewheel is broken >:] Status in linux package in Ubuntu: Invalid Bug description: If you don't use mousewheel or touchpad (since reboot) everything will be fast and responsive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835677/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836630] Re: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend
Alberto, I think we should raise the issue to Nvidia. For a short term solution, is it possible to apply the change (comment #23) to all supported nvidia package versions in the interim? ** No longer affects: linux-hwe-edge (Ubuntu) ** Also affects: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in Linux: Unknown Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers package in Ubuntu: New Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: system76 1721 F pulseaudio /dev/snd/controlC0: system76 1721 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 MachineType: System76 Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux-hwe-edge ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: oryp5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOryxPro:rvroryp5:cvnSystem76:ct10:cvroryp5: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1836630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828948] Re: OBSOLETE_BY in DKMS.CONF does not work
I verified the 2.6.1-4ubuntu2.2 dkms in VM by multipass snap with changed dkms [1], it works as expected. system has linux-image-5.0.0-20-generic and linux-image-5.0.0-21-generic be installed. With OBSOLETE_BY="5.0.0-21" , then the DKMS will only be installed for kernel 5.0.0-20. With OBSOLETE_BY="5.0.0-20" , then the DKMS not be installed for both kernel. [1] https://code.launchpad.net/~alextu/+git/acpi-call-dkms-test-obsolete ** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1828948 Title: OBSOLETE_BY in DKMS.CONF does not work Status in DKMS: Fix Released Status in OEM Priority Project: Fix Committed Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Bionic: Fix Committed Status in dkms source package in Disco: Fix Committed Bug description: [Impact] OBSOLETE_BY in DKMS.CONF not work Which also be reported on upstream: https://github.com/dell/dkms/issues/81 [Test case] 1. add OBSOLETE_BY in DKMS.CONF e.g. OBSOLETE_BY="4.15.0-1033" 2. the kernel module should not be built with kernel greater than the version specified by OBSOLETE_BY e.g. - user install kernel 4.15.0-1030 and 4.15.0-10360 - user install kernel oem-wifi-qualcomm-ath10k-lp1803647-4.15-dkms [1] which has OBSOLETE_BY="4.15.0-1033" - the kernel module from dkms [1] should only built for 4.15.0-1030, but not for 4.15.0-10360 [Regression potential] None as it used to work, but somehow regression there. [1] https://code.launchpad.net/~alextu/+recipe/oem-wifi-qualcomm- ath10k-lp1803647-4.15-dkms-daily To manage notifications about this bug go to: https://bugs.launchpad.net/dkms/+bug/1828948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836878] Re: linux-snapdragon: 4.4.0-1120.126 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1836877 (dragonboard-kernel) -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1836880 phase: Holding before Promote to Proposed phase-changed: Wednesday, 17. July 2019 13:23 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa main:queued + promote-to-proposed: Holding -- master bug not ready for proposed variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1836878 Title: linux-snapdragon: 4.4.0-1120.126 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1836877 (dragonboard-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1836880 phase: Holding before Promote to Proposed phase-changed: Wednesday, 17. July 2019 13:23 UTC reason: promote-to-proposed: Holding -- master bug not ready for proposed variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1836878/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836630] Re: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend
Kai-Heng, That patch when applied to the nvidia DKMS module appears to fix the suspend issues. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: system76 1721 F pulseaudio /dev/snd/controlC0: system76 1721 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 MachineType: System76 Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux-hwe-edge ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: oryp5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOryxPro:rvroryp5:cvnSystem76:ct10:cvroryp5: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1836630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831775] Re: ss seems broken when using multiple filters in the same cmdline
This happens because output of clknetsim was modified and the following regex: # Check if only NTP port (123) was used check_packet_port() { local i ret=0 port=123 test_message 2 1 "checking port numbers in packet log:" + set -x + + cp tmp/log.packets /tmp/mine.log.packets + for i in $(seq 1 $(get_chronyd_nodes)); do test_message 3 0 "node $i:" grep -E -q "$port [0-9]+\$" tmp/log.packets && \ ! grep -E "^[0-9e.+-]+ $i " tmp/log.packets | \ grep -E -q -v " $port [0-9]+\$" && \ test_ok || test_bad [ $? -eq 0 ] || ret=1 done + set +x + return $ret } Broke. Example of the output change: # good (old) output (vi :set list) 2.020970e-01>---1>--2>--1.854754e-04>---123>123>1$ 2.022825e-01>---2>--1>--2.935628e-04>---123>123>1$ 2.027594e-01>---2>--1>--1.794174e-04>---123>123>1$ 2.029388e-01>---1>--2>--2.045724e-04>---123>123>1$ # bad (new) output (vi :set list) 2.066646e+03>---2>--1>--1.297676e-04>---123>123>1>--48>-1$ 2.066646e+03>---1>--2>--1.520290e-04>---123>123>1>--48>-1$ 2.191654e+03>---1>--2>--1.690480e-04>---123>123>1>--48>-1$ 2.191654e+03>---2>--1>--4.082407e-04>---123>123>1>--48>-1$ TODO: - make a change to eoan so clknetsim code is compatible (so this wont happen again) - mark this test as faulty for previous chronie versions (since they will always fail) - (could do) fix autopkgtest next time chronie needs a SRU (disco/bionic) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1831775 Title: ss seems broken when using multiple filters in the same cmdline Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Cosmic: Won't Fix Status in iproute2 source package in Disco: Fix Committed Status in iproute2 source package in Eoan: Fix Released Bug description: [Impact] * ss won't be able to run commands with single filters inside parentheses, like: "( sport == :X )", for example. * A workaround is to remove "( )" from single filters, since it looks the issue does not affect 2 filters being put together in the same parentheses, like: " ( X and Y ) and Y " instead of ( X and Y ) and ( Y )". * CTDB is unable to use ss filter to obtain nodes public IP addresses in order to fail over services (LP: #722201). [Test Case] * Having an Ubuntu Cosmic, Disco or Eoan, try to execute the following command: $ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Independent of the IPs or ports being used. Copying and pasting the command should be enough for you to know if you are affected. Bad Result: ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message ... Expected Result: Recv-QSend-Q Local Address:Port Peer Address:Port ... * test case was discovered during CTDB scripts execution [Regression Potential] * biggest risk would be to affect ss interpreter (worst case scenario). * the proposed patch is based in upstream fix and was tested against the same issue reported as the reproducer (above) and some other generic ss commands. * any problem here is unlikely to change iproute2 most important command interpreter, "ip", since the patch is applied against ss code. [Other Info] ORIGINAL DESCRIPTION: Investigating an issue for CTDB (LP: #722201), after suggesting a fix on ss syntax to CTDB upstream project, we discovered that "ss" seems to be broken in Ubuntu since Ubuntu Cosmic: # Debian Sid inaddy@workstation:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-QSend-Q Local Address:Port Peer Address:Port # Ubuntu Ubuntu 16.04 LTS (Xenial Xerus) (c)inaddy@xenial:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-QLocal Address:Port Peer Address:Port # Ubuntu 18.04 LTS (Bionic Beaver) (c)inaddy@bionic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-Q Local Address:Port Peer Address:Port # Ubuntu 18.10 (Cosmic Cuttlefish) (c)inaddy@cosmic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message # Ubuntu 19.04 (Disco Dingo)
[Kernel-packages] [Bug 1830815] Re: Hi1620 driver updates from upstream 5.2 merge window
disco verification - I ran Ubuntu Server cert on a d06 system and there were no unexpected failures. ** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830815 Title: Hi1620 driver updates from upstream 5.2 merge window Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Released Bug description: [Impact] Sync up the hns drivers with the 5.2 merge window. (Cut & paste from bug 1819535) Drivers for the HiSilicon Hi1620 SoC continue to be under active development, including both hardware enablement and bug fix patches. With the amount of flux involved, identifying and cherry-picking individual patches would be more error prone then re-syncing with current upstream. [Test Case] Validated by testing on the Hi1620-based D06 systems. These changes were staged in a PPA kernel that underwent testing w/ the Ubuntu certification test suite (Ubuntu certification is targeted for 18.04.3 HWE kernel). In addition, perftest was used to verify RDMA functionality and iperf was used to verify networking performance. [Regression Risk] Changes are restricted to drivers specific to the Hi1620 SoC, and tested on the same. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831775] Re: ss seems broken when using multiple filters in the same cmdline
Issue happens because of the "upstream" "git cloned" clknetsim test dependencies. The tests clone upstream clknetsim repo. Using an old version of clknetsim I was able to make the test 111 to pass: (c)inaddy@iproute2verification:~/work/sources/ubuntu/chrony/test/simulation$ ./111-knownclient Testing reply to client configured as server: network with 1*1 servers and 1 clients: non-default settings: client_conf=acquisitionport 123 server_conf=server 192.168.123.2 noselect acquisitionport 123 starting node 1:OK starting node 2:OK running simulation: OK checking chronyd exit: node 1: OK node 2: OK checking source selection: node 2: OK checking port numbers in packet log: node 1: OK node 2: OK checking clock sync time, max/rms time/freq error: node 2: 130 1.47e-04 6.19e-07 7.41e-05 8.68e-08 OK PASS Will bisect cause its faster and easier. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1831775 Title: ss seems broken when using multiple filters in the same cmdline Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Cosmic: Won't Fix Status in iproute2 source package in Disco: Fix Committed Status in iproute2 source package in Eoan: Fix Released Bug description: [Impact] * ss won't be able to run commands with single filters inside parentheses, like: "( sport == :X )", for example. * A workaround is to remove "( )" from single filters, since it looks the issue does not affect 2 filters being put together in the same parentheses, like: " ( X and Y ) and Y " instead of ( X and Y ) and ( Y )". * CTDB is unable to use ss filter to obtain nodes public IP addresses in order to fail over services (LP: #722201). [Test Case] * Having an Ubuntu Cosmic, Disco or Eoan, try to execute the following command: $ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Independent of the IPs or ports being used. Copying and pasting the command should be enough for you to know if you are affected. Bad Result: ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message ... Expected Result: Recv-QSend-Q Local Address:Port Peer Address:Port ... * test case was discovered during CTDB scripts execution [Regression Potential] * biggest risk would be to affect ss interpreter (worst case scenario). * the proposed patch is based in upstream fix and was tested against the same issue reported as the reproducer (above) and some other generic ss commands. * any problem here is unlikely to change iproute2 most important command interpreter, "ip", since the patch is applied against ss code. [Other Info] ORIGINAL DESCRIPTION: Investigating an issue for CTDB (LP: #722201), after suggesting a fix on ss syntax to CTDB upstream project, we discovered that "ss" seems to be broken in Ubuntu since Ubuntu Cosmic: # Debian Sid inaddy@workstation:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-QSend-Q Local Address:Port Peer Address:Port # Ubuntu Ubuntu 16.04 LTS (Xenial Xerus) (c)inaddy@xenial:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-QLocal Address:Port Peer Address:Port # Ubuntu 18.04 LTS (Bionic Beaver) (c)inaddy@bionic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-Q Local Address:Port Peer Address:Port # Ubuntu 18.10 (Cosmic Cuttlefish) (c)inaddy@cosmic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message # Ubuntu 19.04 (Disco Dingo) (c)inaddy@disco:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry.
[Kernel-packages] [Bug 1831775] Re: ss seems broken when using multiple filters in the same cmdline
(c)inaddy@iproute2verification:~/work/sources/ubuntu/chrony/test/simulation/clknetsim$ git bisect bad 537cb7161de9ad372437ab0fcbff76e54a3cd97a is the first bad commit commit 537cb7161de9ad372437ab0fcbff76e54a3cd97a Author: Miroslav Lichvar Date: Tue Jun 11 17:05:22 2019 +0200 add message type :100644 100644 2898b26a7b1311647b4419da79000e69b6d89b39 5b6d8917e1dd4667fe124b22a907e42286cb86f4 M client.c :100644 100644 20f052d7583d6051e779fd7318f47a3867595993 5cab1f4e86f95719814657da69a93089d029025e M client_fuzz.c :100644 100644 7b2fcbe0c5d39193946afebbd778a506c3452cb9 eeff3aba6b4bc46dc0ef516257a8ff130549a827 M network.cc :100644 100644 427036573b6da7227c5d7fa169a3d81627330d9c b5fe35b408f2a635455548d2b7dfd0ec7ec6da90 M network.h :100644 100644 be9d6fa5177c49acd3906643fc010576a5d5369d cf94b9e42bdb6a1b33b84afe8b5e19a9a5d00806 M node.cc :100644 100644 36e4e328ce10b062166c101a1d4c74244af558ab da78179483f88c84314c85af8dbfd9843332a33d M protocol.h -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1831775 Title: ss seems broken when using multiple filters in the same cmdline Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Cosmic: Won't Fix Status in iproute2 source package in Disco: Fix Committed Status in iproute2 source package in Eoan: Fix Released Bug description: [Impact] * ss won't be able to run commands with single filters inside parentheses, like: "( sport == :X )", for example. * A workaround is to remove "( )" from single filters, since it looks the issue does not affect 2 filters being put together in the same parentheses, like: " ( X and Y ) and Y " instead of ( X and Y ) and ( Y )". * CTDB is unable to use ss filter to obtain nodes public IP addresses in order to fail over services (LP: #722201). [Test Case] * Having an Ubuntu Cosmic, Disco or Eoan, try to execute the following command: $ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Independent of the IPs or ports being used. Copying and pasting the command should be enough for you to know if you are affected. Bad Result: ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message ... Expected Result: Recv-QSend-Q Local Address:Port Peer Address:Port ... * test case was discovered during CTDB scripts execution [Regression Potential] * biggest risk would be to affect ss interpreter (worst case scenario). * the proposed patch is based in upstream fix and was tested against the same issue reported as the reproducer (above) and some other generic ss commands. * any problem here is unlikely to change iproute2 most important command interpreter, "ip", since the patch is applied against ss code. [Other Info] ORIGINAL DESCRIPTION: Investigating an issue for CTDB (LP: #722201), after suggesting a fix on ss syntax to CTDB upstream project, we discovered that "ss" seems to be broken in Ubuntu since Ubuntu Cosmic: # Debian Sid inaddy@workstation:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-QSend-Q Local Address:Port Peer Address:Port # Ubuntu Ubuntu 16.04 LTS (Xenial Xerus) (c)inaddy@xenial:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-QLocal Address:Port Peer Address:Port # Ubuntu 18.04 LTS (Bionic Beaver) (c)inaddy@bionic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-Q Local Address:Port Peer Address:Port # Ubuntu 18.10 (Cosmic Cuttlefish) (c)inaddy@cosmic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message # Ubuntu 19.04 (Disco Dingo) (c)inaddy@disco:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] # Ubuntu 19.10 (Eoan Ermine) (c)inaddy@eoan:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ]
[Kernel-packages] [Bug 1836878] Re: linux-snapdragon: 4.4.0-1120.126 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1836877 (dragonboard-kernel) -- swm properties -- kernel-stable-master-bug: 1836880 phase: Holding before Promote to Proposed phase-changed: Wednesday, 17. July 2019 13:23 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building + promote-to-proposed: Pending -- builds not complete in ppa main:queued variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1836878 Title: linux-snapdragon: 4.4.0-1120.126 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1836877 (dragonboard-kernel) -- swm properties -- kernel-stable-master-bug: 1836880 phase: Holding before Promote to Proposed phase-changed: Wednesday, 17. July 2019 13:23 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa main:queued variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1836878/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836755] Re: hda/realtek: can't detect external mic on a Dell machine
** Changed in: linux (Ubuntu) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836755 Title: hda/realtek: can't detect external mic on a Dell machine Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: [Impact] The external can't be detected when plugging headset in the front audio jack. [Fix] apply the alc891 fixup to set headset-mic and headpphone-mic pins. [Test Case] apply this patch and boot with the kernel, plug the headset-mic and choose headset-mic from popup dialogue, the headset-mic can record sound very well. [Regression Risk] Low. this patch is specific to a dell machine by pin configuration definition. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1836755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836630] Re: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend
I will build the nvidia DKMS module with this patch and test it out, thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: system76 1721 F pulseaudio /dev/snd/controlC0: system76 1721 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 MachineType: System76 Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux-hwe-edge ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: oryp5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOryxPro:rvroryp5:cvnSystem76:ct10:cvroryp5: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1836630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831775] Re: ss seems broken when using multiple filters in the same cmdline
Chrony issue being investigated here: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1836929 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1831775 Title: ss seems broken when using multiple filters in the same cmdline Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Cosmic: Won't Fix Status in iproute2 source package in Disco: Fix Committed Status in iproute2 source package in Eoan: Fix Released Bug description: [Impact] * ss won't be able to run commands with single filters inside parentheses, like: "( sport == :X )", for example. * A workaround is to remove "( )" from single filters, since it looks the issue does not affect 2 filters being put together in the same parentheses, like: " ( X and Y ) and Y " instead of ( X and Y ) and ( Y )". * CTDB is unable to use ss filter to obtain nodes public IP addresses in order to fail over services (LP: #722201). [Test Case] * Having an Ubuntu Cosmic, Disco or Eoan, try to execute the following command: $ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Independent of the IPs or ports being used. Copying and pasting the command should be enough for you to know if you are affected. Bad Result: ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message ... Expected Result: Recv-QSend-Q Local Address:Port Peer Address:Port ... * test case was discovered during CTDB scripts execution [Regression Potential] * biggest risk would be to affect ss interpreter (worst case scenario). * the proposed patch is based in upstream fix and was tested against the same issue reported as the reproducer (above) and some other generic ss commands. * any problem here is unlikely to change iproute2 most important command interpreter, "ip", since the patch is applied against ss code. [Other Info] ORIGINAL DESCRIPTION: Investigating an issue for CTDB (LP: #722201), after suggesting a fix on ss syntax to CTDB upstream project, we discovered that "ss" seems to be broken in Ubuntu since Ubuntu Cosmic: # Debian Sid inaddy@workstation:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-QSend-Q Local Address:Port Peer Address:Port # Ubuntu Ubuntu 16.04 LTS (Xenial Xerus) (c)inaddy@xenial:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-QLocal Address:Port Peer Address:Port # Ubuntu 18.04 LTS (Bionic Beaver) (c)inaddy@bionic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-Q Local Address:Port Peer Address:Port # Ubuntu 18.10 (Cosmic Cuttlefish) (c)inaddy@cosmic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message # Ubuntu 19.04 (Disco Dingo) (c)inaddy@disco:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] # Ubuntu 19.10 (Eoan Ermine) (c)inaddy@eoan:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] I have generated a pkg using upstream iproute2 source code and it does not suffer the issue. I have generated a package using Ubuntu cosmic source package, without debian/patches/*, and verified the issue still persists (not being introduced by any of our packages, and being present if vanilla upstream version used in Cosmic). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1831775/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836630] Re: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend
Thanks, how should I apply this? To the /usr/src/nvidia-*/nvidia/nv.c file? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: system76 1721 F pulseaudio /dev/snd/controlC0: system76 1721 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 MachineType: System76 Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux-hwe-edge ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: oryp5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOryxPro:rvroryp5:cvnSystem76:ct10:cvroryp5: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1836630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762940] Re: hibmc-drm Causes Unreadable Display for Huawei amd64 Servers
** Changed in: linux (Ubuntu Eoan) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762940 Title: hibmc-drm Causes Unreadable Display for Huawei amd64 Servers Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/1762940 [Impact] amd64 based Huawei servers have problems where the display output of their iBMC chips is broken, resulting in a "blurry" screen when viewed from their in house remote kvm-like console. Example: https://launchpadlibrarian.net/365907668/creen_picture_for_blur.png The issue is caused by the hibmc_drm kernel module being loaded. The PCI ID for the iBMC chips on amd64 hardware is the same as arm64 hardware, but the hibmc_drm driver was developed only for use on arm64 hardware, most notably for the Huawei D05 development board. The impact to Huawei is that their customers cannot use Ubuntu server install media as the screen goes "blurry" when the d-i install media or subuqity installer loads the hibmc_drm kernel module after language selection. The only workaround for their customers is to press the "E" key during the very first installer menu and adding "modprobe.blacklist=hibmc_drm" to the kernel command line in the grub menu. This is not good for customer experience with their servers. Other problems exist for the hibmc_drm driver on amd64, such as working on bios, but not uefi, and not being wayland compatible, making the screen blurry whenever a desktop session is started and gdm loaded. Huawei have asked us to remove hibmc_drm from all architectures except arm64, and this aligns with advice from Hisilicon. [Fix] I modified the config/annotations file to remove all architectures except arm64, and created a patch for Kconfig to set a firm requirement on ARM64 for hibmc_drm. I will send the Kconfig patch upstream in the coming days for a more permanent fix. [Testcase] Apply the patches and run: ubuntu-bionic/CONFIGS$ fakeroot debian/rules genconfigs ubuntu-bionic/CONFIGS$ grep -Rin "hibmc" . ./arm64-config.flavour.generic:5739:CONFIG_DRM_HISI_HIBMC=m You should see that only arm64 has the config option enabled. A test kernel has been built, and is available here: https://launchpad.net/~mruffell/+archive/ubuntu/sf232667-test Huawei requested a test d-i install iso to test server install with, which can be found here and uses the kernel from the ppa above: https://people.canonical.com/~mruffell/sf232667_ubuntu_server_d-i_20190711b1.iso Both the test kernel and the custom d-i install iso have been tested on amd64 Huawei server hardware successfully and video output is functional. [Regression Potential] Regressions will be limited to hardware containing the iBMC chips from Hisilicon, which I believe are exclusive to Huawei servers. I have taken care to ensure that hibmc_drm is enabled for ARM64 so it should not impact kernels built for the Huawei D05 arm64 development board, and d-i will still load the hibmc_drm driver during startup for arm64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834883] Re: linux-aws: 4.18.0-1021.25 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834904 - phase: Testing - phase-changed: Thursday, 04. July 2019 13:35 UTC + phase: Holding before Release + phase-changed: Wednesday, 17. July 2019 16:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED + promote-to-updates: Holding -- cycle not ready to release variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1834883 Title: linux-aws: 4.18.0-1021.25 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Cosmic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834904 phase: Holding before Release phase-changed: Wednesday, 17. July 2019 16:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- cycle not ready to release variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835054] Re: Enable Armada SOCs and MVPP2 NIC driver for disco/generic arm64
** Changed in: linux (Ubuntu Eoan) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835054 Title: Enable Armada SOCs and MVPP2 NIC driver for disco/generic arm64 Status in linux package in Ubuntu: Fix Committed Status in linux source package in Disco: In Progress Status in linux source package in Eoan: Fix Committed Bug description: == SRU Justification == The mvpp2 is a driver for network controllers(s) in Marvell SOCs, particularly Armada 8040. However this driver was neither enabled as a module or a built-in for Disco arm64. == Fix == Just like what we did for armhf, set CONFIG_MVPP2 to "m" for arm64 can solve this problem. We need to enable the Armada SOCs support (CONFIG_ARCH_MVEBU) as well to meet the dependency requirement. Other configs were added by the updateconfigs process. == Test == A test kernel for Disco ARM64 could be found here: https://people.canonical.com/~phlin/kernel/lp-1835054-mvpp2/V2/ User has confirmed that the V1 kernel can fix this missing driver issue (V2 is just with CONFIG_ARCH_MULTI_V7 dropped and some configs added explicitly, I have it tested on an ARM64 node, the mvpp2 module can be loaded without any issue). == Regression Potential == Low, this patch just enable the Armada SOCs and make this mvpp2 driver to be built as a module on ARM64, and we already have those for armhf. == Original Bug Report == At least in Ubuntu 19.04, the arm64 kernel (linux-image-5.0.0) is not building CONFIG_MVPP2 (depends on CONFIG_ARCH_MVEBU) - a driver for network controllers(s) in Marvell SOCs, particularly Armada 8040 - neither as a module or a built-in: $ uname -m aarch64 $ grep MVPP2 /boot/config-5.0.0-20-generic $ It makes very hard (and impossible for non-advanced users) to install and use Ubuntu on the Macchiatobin board (http://macchiatobin.net/) - a reasonably priced and performant server/mini-desktop platform. Could it be added, please, and the installer image re-generated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835054/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836912] Re: ipv4: enable route flushing in network namespaces
** Description changed: - Tools such as vpnc try to flush routes when run inside network - namespaces by writing 1 into /proc/sys/net/ipv4/route/flush. This - currently does not work because flush is not enabled in non-initial - network namespaces. - Since routes are per network namespace it is safe to enable + SRU Justification + + Impact: Tools such as vpnc try to flush routes when run inside network namespaces by writing 1 into /proc/sys/net/ipv4/route/flush. This + currently does not work because flush is not enabled in non-initial network namespaces. Users have complained about this at various times (cf. Link: https://github.com/lxc/lxd/issues/4257). + + Fix: Enable /proc/sys/net/ipv4/route/flush inside non-initial network + namespaces. + + Regression Potential: None, since this didn't use to work before. Since + routes are per network namespace it is safe to enable /proc/sys/net/ipv4/route/flush in there. - This has been reported against LXD a few times before + Test Case: Tested with LXD on a kernel with the patch applied and by + running vpnc successfully. - Link: https://github.com/lxc/lxd/issues/4257 + Target Kernels: All LTS kernels starting from 4.15. Kernel 5.3 has the + patchset upstream. - Please backport this to our LTS kernels. :) + Patches: + https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5cdda5f1d6adde02da591ca2196f20289977dc56 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836912 Title: ipv4: enable route flushing in network namespaces Status in linux package in Ubuntu: Confirmed Bug description: SRU Justification Impact: Tools such as vpnc try to flush routes when run inside network namespaces by writing 1 into /proc/sys/net/ipv4/route/flush. This currently does not work because flush is not enabled in non-initial network namespaces. Users have complained about this at various times (cf. Link: https://github.com/lxc/lxd/issues/4257). Fix: Enable /proc/sys/net/ipv4/route/flush inside non-initial network namespaces. Regression Potential: None, since this didn't use to work before. Since routes are per network namespace it is safe to enable /proc/sys/net/ipv4/route/flush in there. Test Case: Tested with LXD on a kernel with the patch applied and by running vpnc successfully. Target Kernels: All LTS kernels starting from 4.15. Kernel 5.3 has the patchset upstream. Patches: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5cdda5f1d6adde02da591ca2196f20289977dc56 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836912/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836177] Re: Intel ethernet I219 may wrongly detect connection speed as 10Mbps
** Changed in: linux (Ubuntu) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1836177 Title: Intel ethernet I219 may wrongly detect connection speed as 10Mbps Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-oem source package in Bionic: New Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Disco: Incomplete Status in linux-oem source package in Disco: Invalid Status in linux-oem-osp1 source package in Disco: Invalid Bug description: [Impact] Intel I219 ethernet may wrongly detect 1Gbps network as 10Mbps after ethernet cable hotplugging. [Fix] Use delayed work before deciding the network speed. This essentially workarounds unreliable reading on MII_BMSR register. [Test] Before the patch the network operates at 10Mbps after cable gets plugged. With the fix, network always operates in 1Gbps. [Regression Potential] Low. It changes the watchdog task from timer to delayed work, the logic is essentially the same. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1836177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836308] Re: Unhide Nvidia HDA audio controller
** Changed in: linux (Ubuntu) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1836308 Title: Unhide Nvidia HDA audio controller Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-oem source package in Bionic: New Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Disco: New Status in linux-oem source package in Disco: Invalid Status in linux-oem-osp1 source package in Disco: Invalid Bug description: [Impact] Nvidia HDA audio controller comes with Nvidia graphics cannot be found by PCI subsystem. [Fix] Write bit 25 at graphics' config space offset 0x488 to enable the HDA controller. [Test] Nvidia HDA controller is not listed under lspci. After applying the fix lspci can find Nvidia HDA controller. [Regression Potential] Low. This fix doesn't bring any functional change other then exposing HDA controller at hardware level. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1836308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836910] Re: br_netfilter: namespace sysctl operations
** Description changed: - Currently, the /proc/sys/net/bridge folder is only created in the initial - network namespace. This patch ensures that the /proc/sys/net/bridge folder - is available in each network namespace if the module is loaded and - disappears from all network namespaces when the module is unloaded. + SRU Justification + + Impact: Currently, the /proc/sys/net/bridge folder is only created in + the initial network namespace. This blocks use-cases where users would + like to e.g. not do bridge filtering for bridges in a specific network + namespace while doing so for bridges located in another network + namespace. + + Fix: The patches linked below ensure that the /proc/sys/net/bridge + folder is available in each network namespace if the module is loaded + and disappears from all network namespaces when the module is unloaded. In doing so the patch makes the sysctls: bridge-nf-call-arptables bridge-nf-call-ip6tables bridge-nf-call-iptables bridge-nf-filter-pppoe-tagged bridge-nf-filter-vlan-tagged bridge-nf-pass-vlan-input-dev - apply per network namespace. This unblocks some use-cases where users would - like to e.g. not do bridge filtering for bridges in a specific network - namespace while doing so for bridges located in another network namespace. + apply per network namespace. - The netfilter rules are afaict already per network namespace so it should - be safe for users to specify whether bridge devices inside a network - namespace are supposed to go through iptables et al. or not. Also, this can - already be done per-bridge by setting an option for each individual bridge - via Netlink. It should also be possible to do this for all bridges in a - network namespace via sysctls. + Regression Potential: None, since this didn't use to work before. Otherwise limited to the br_netfilter module. + The netfilter rules are afaict already per network namespace so it should be safe for users to specify whether bridge devices inside a network namespace are supposed to go through iptables et al. or not. Also, this can already be done per-bridge by setting an option for each individual bridge via Netlink. It should also be possible to do this for all bridges in a network namespace via sysctls. - I've pushed a small series of patches upstream. - Please backport them to our LTS kernels. :) + Test Case: Tested with LXD on a kernel with the patches applied and per- + network namespace iptables. + + Target Kernels: All LTS kernels starting from 4.15. Kernel 5.3 has the + patchset upstream. + + Patches: + https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ff6d090d0db41425aef0cfe5dc58bb3cc12514a2 + + https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=22567590b2e634247931b3d2351384ba45720ebe + + https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7e6daf50e1f4ea0ecd56406beb64ffc66e1e94db -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836910 Title: br_netfilter: namespace sysctl operations Status in linux package in Ubuntu: Confirmed Bug description: SRU Justification Impact: Currently, the /proc/sys/net/bridge folder is only created in the initial network namespace. This blocks use-cases where users would like to e.g. not do bridge filtering for bridges in a specific network namespace while doing so for bridges located in another network namespace. Fix: The patches linked below ensure that the /proc/sys/net/bridge folder is available in each network namespace if the module is loaded and disappears from all network namespaces when the module is unloaded. In doing so the patch makes the sysctls: bridge-nf-call-arptables bridge-nf-call-ip6tables bridge-nf-call-iptables bridge-nf-filter-pppoe-tagged bridge-nf-filter-vlan-tagged bridge-nf-pass-vlan-input-dev apply per network namespace. Regression Potential: None, since this didn't use to work before. Otherwise limited to the br_netfilter module. The netfilter rules are afaict already per network namespace so it should be safe for users to specify whether bridge devices inside a network namespace are supposed to go through iptables et al. or not. Also, this can already be done per-bridge by setting an option for each individual bridge via Netlink. It should also be possible to do this for all bridges in a network namespace via sysctls. Test Case: Tested with LXD on a kernel with the patches applied and per-network namespace iptables. Target Kernels: All LTS kernels starting from 4.15. Kernel 5.3 has the patchset upstream. Patches: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ff6d090d0db41425aef0cfe5dc58bb3cc12514a2
[Kernel-packages] [Bug 1836152] Re: Intel ethernet I219 has slow RX speed
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1836152 Title: Intel ethernet I219 has slow RX speed Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Confirmed Status in linux-oem source package in Bionic: New Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Disco: Confirmed Status in linux-oem source package in Disco: Invalid Status in linux-oem-osp1 source package in Disco: Invalid Bug description: [Impact] RX speed on Intel ethernet I219 v6 is extremely slow due to multiple RX CRC errors. [Fix] Disable e1000e K1 feature to make I219 and PCH operate at higher speed to avoid the issue. [Test] Before applying the patch, the RX is slower than 150Kbps. After applying the fix the RX speed can achive gigabits. [Regression Potential] Low. This only applies to recent I219 generations. I've also test several other systems with e1000e and I don't see any regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1836152/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836020] Re: Sometimes touchpad(goodix) can't use tap function
** Changed in: linux (Ubuntu) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836020 Title: Sometimes touchpad(goodix) can't use tap function Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-osp1 package in Ubuntu: New Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux-oem-osp1 source package in Disco: New Bug description: [Impact] Wake up from runtime suspend, Goodix doesn't report correct Tap event by tapping it the first time, so if you double tap the touchpad, the system only got one tap. [Fix] Adding the platforms which uses Goodix touchpad IC to the i2c designware quirk list. [Test] Verified on the buggy machines. [Regression Potential] Low, this quirk doesn't hurt anything and do little or none to power consumption. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1836020/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748689] Re: Mounting SMB shares with vers=3.0 in fstab gives "ioctl error in smb2_get_dfs_refer rc=-2"
Sorry I cannot delete my messages above but in case someone else has same scenario as me, you might be able to keep the error from displaying by adding "vers=2.0" in your mount options. At least that is the version I needed to specify for Windows 2008 and I do not see the errors anymore upon mounting. I might also have not seen this issue earlier because my remote Windows machine used to be Windows 2012 but did change to 2008 recently. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1748689 Title: Mounting SMB shares with vers=3.0 in fstab gives "ioctl error in smb2_get_dfs_refer rc=-2" Status in dellserver: New Status in linux package in Ubuntu: Confirmed Bug description: Xubuntu 17.10 artful Kernel: x86_64 Linux 4.13.0-32.35-generic cifs-utils 2:6.7-1 smbclient 2:4.6.7+dfsg-1ubuntu3.1 Mounting an SMB share with sec=ntlmssp,vers=3.0,credentials=/home/.smbcredentials,dir_mode=0777,file_mode=0777 in /etc/fstab gives the error: "CIFS VFS: ioctl error in smb2_get_dfs_refer rc=-2" in dmesg. Shares mounted this way are readable, but writing data to them (or using programs such as EasyTAG to write to them) ultimately fails. This bug did not occur in kernel 4.10. Mounting the share(s) with vers=1.0 does not give the error, but this is a haphazard fix as SMB v3.0 carries many security features with it not avaliable in SMB 1.0. --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=/dev/mapper/DeusVitam--vg-swap_1 JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=/dev/mapper/hostname--vg-root ro splash quiet amdgpu.cik_support=1 vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.169.3 RfKill: Tags: artful Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: Upgraded to artful on 2018-02-05 (7 days ago) UserGroups: libvirt libvirtd sudo wireshark WifiSyslog: _MarkForUpload: True dmi.bios.date: 03/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0701 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-E/USB 3.1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0701:bd03/16/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-E/USB3.1:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1748689/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
** Changed in: linux (Ubuntu Eoan) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829563 Title: bcache: risk of data loss on I/O errors in backing or caching devices Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Won't Fix Status in linux source package in Disco: In Progress Status in linux source package in Eoan: Fix Committed Bug description: [Impact] * The bcache code in Bionic lacks several fixes to handle I/O errors in both backing devices and caching devices. * Partial or permanent errors in backing or caching devices, specially in writeback mode, can lead to data loss and/or the application is not notified about failed I/O requests. * The bcache device might remain available for I/O requests even if backing device is offline, so writes are undefined. [Test Case] * Detailed test cases/steps for the behavior of many patches with code logic changes are provided in bug comments. * The patchset has been tested for regressions on each cache mode (writethrough, writeback, writearound, none) with the xfstests test suite (on ext4) and fio (sequential + random read-write). [Regression Potential] * The patchset is relatively large and touches several areas in bcache code, however, synthetic testing of the patches has been performed, and extensive regression/stress tests were run (as mentioned in Test Case section). * Many patches in the patchset are 'Fixes' patches to other patches, and no further 'Fixes' currently exist upstream. [Other Info] * Canonical Field Eng. deploys bcache+writeback extensively (e.g., BootStack, UA cloud, except rare all-flash cases). [Original Bug Description] This is a request for a backport of the following upstream patch from 4.18: "bcache: stop bcache device when backing device is offline" https://github.com/torvalds/linux/commit/0f0709e6bfc3ce4e8e1c0e8573490c45f76cfeee Field engineering uses bcache quite extensively and it would be good to have this in the GA/bionic kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835279] Re: 4.15.0-54.58-generic 4.15.18: oops/BUG on LUKS open
I've found other upstream fixes that might be interesting to test: https://git.launchpad.net/~arighi/+git/bionic-linux/log/?h=lp-1835279 I've uploaded a new test kernel here (still based of 4.15.0-54 + the backported fixes): https://kernel.ubuntu.com/~arighi/LP-1835279/ It'd be great if you could repeat your test and see if the NULL pointer dereference is still happening. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835279 Title: 4.15.0-54.58-generic 4.15.18: oops/BUG on LUKS open Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Bug description: This is Linux version 4.15.0-54-generic (buildd@lgw01-amd64-014) (gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 (Ubuntu 4.15.0-54.58-generic 4.15.18), from pc- kernel_240.snap Version signature: 4.15.0-54.58-generic 4.15.18 Issue is non-deterministic, and happens in roughly 20% of the attempts. Running on: qemu-kvm, command line: kvm \ -bios /usr/share/ovmf/OVMF.fd \ -smp 2 -m 512 -netdev user,id=mynet0,hostfwd=tcp::8022-:22,hostfwd=tcp::8090-:80 \ -device virtio-net-pci,netdev=mynet0 \ -drive file=pc.img,format=raw Commands that caused the problem: cryptsetup -q --type luks2 --key-file luksFormat /dev/sda4 LD_PRELOAD=/lib/no-udev.so cryptsetup --type luks2 --key-file open /dev/sda4 crypt-data Notes: - See https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1589083 for more information on the no-udev workaround. - The commands are scripted. Also tried to add a 200ms and 1s interval before opening the device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835279/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836925] Re: linux-ibm-gt: 4.15.0-1028.30 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1834954 - phase: Packaging - phase-changed: Wednesday, 17. July 2019 15:25 UTC + phase: Holding before Promote to Proposed + phase-changed: Wednesday, 17. July 2019 16:09 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836925 Title: linux-ibm-gt: 4.15.0-1028.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1834954 phase: Holding before Promote to Proposed phase-changed: Wednesday, 17. July 2019 16:09 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1836925/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831775] Re: ss seems broken when using multiple filters in the same cmdline
I have downgraded iproute2 package (using -updates pocket) and it also gave the same errors: (c)inaddy@iproute2verification:~/work/sources/ubuntu/chrony/test/simulation$ ./111-knownclient Testing reply to client configured as server: network with 1*1 servers and 1 clients: ... checking port numbers in packet log: node 1: BAD node 2: BAD FAIL (c)inaddy@iproute2verification:~/work/sources/ubuntu/chrony/test/simulation$ ./112-port Testing port and acquisitionport directives: network with 1*1 servers and 1 clients: ... checking port numbers in packet log: node 1: BAD node 2: BAD FAIL So its not because of this SRU. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1831775 Title: ss seems broken when using multiple filters in the same cmdline Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Cosmic: Won't Fix Status in iproute2 source package in Disco: Fix Committed Status in iproute2 source package in Eoan: Fix Released Bug description: [Impact] * ss won't be able to run commands with single filters inside parentheses, like: "( sport == :X )", for example. * A workaround is to remove "( )" from single filters, since it looks the issue does not affect 2 filters being put together in the same parentheses, like: " ( X and Y ) and Y " instead of ( X and Y ) and ( Y )". * CTDB is unable to use ss filter to obtain nodes public IP addresses in order to fail over services (LP: #722201). [Test Case] * Having an Ubuntu Cosmic, Disco or Eoan, try to execute the following command: $ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Independent of the IPs or ports being used. Copying and pasting the command should be enough for you to know if you are affected. Bad Result: ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message ... Expected Result: Recv-QSend-Q Local Address:Port Peer Address:Port ... * test case was discovered during CTDB scripts execution [Regression Potential] * biggest risk would be to affect ss interpreter (worst case scenario). * the proposed patch is based in upstream fix and was tested against the same issue reported as the reproducer (above) and some other generic ss commands. * any problem here is unlikely to change iproute2 most important command interpreter, "ip", since the patch is applied against ss code. [Other Info] ORIGINAL DESCRIPTION: Investigating an issue for CTDB (LP: #722201), after suggesting a fix on ss syntax to CTDB upstream project, we discovered that "ss" seems to be broken in Ubuntu since Ubuntu Cosmic: # Debian Sid inaddy@workstation:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-QSend-Q Local Address:Port Peer Address:Port # Ubuntu Ubuntu 16.04 LTS (Xenial Xerus) (c)inaddy@xenial:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-QLocal Address:Port Peer Address:Port # Ubuntu 18.04 LTS (Bionic Beaver) (c)inaddy@bionic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-Q Local Address:Port Peer Address:Port # Ubuntu 18.10 (Cosmic Cuttlefish) (c)inaddy@cosmic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message # Ubuntu 19.04 (Disco Dingo) (c)inaddy@disco:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] # Ubuntu 19.10 (Eoan Ermine) (c)inaddy@eoan:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] I have generated a pkg using upstream iproute2 source code and it does not suffer the issue. I have generated a package
[Kernel-packages] [Bug 1828166] Re: perf top problem on z with Ubuntu 18.04
And afterwards you can get the package that contains perf like this: $ dpkg -S $(which perf) linux-tools-common: /usr/bin/perf $ apt-get source linux-tools-common For the linux-tools source package that fits to your running kernel, do: apt-get source linux-tools-$(uname -r) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828166 Title: perf top problem on z with Ubuntu 18.04 Status in Ubuntu on IBM z Systems: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: Invalid Bug description: SRU Justification: == [Impact] * The perf top tool hangs and shows error messages, like 'Not enough memory for annotating' [Fix] * edeb0c90df3581b821a764052d185df985f8b8dc edeb0c9 "perf tools: Stop fallbacking to kallsyms for vdso symbols lookup" [Test Case] * start a benchmark (mem_alloc, but it doesn't really matter what) * execute perf top in a second terminal * the output of perf top is correct * now stop the benchmark * and perf top shows an error message, like "Not enough memory for annotating '__irf_end' symbol!)" * and perf top can't be exited anymore [Regression Potential] * The regression potential can be considered as low since this happens only while using the perf top tool * and it is known that the commit (above) fixes the problem * and the fix is upstream since 4.19 [Other Info] * current disco and eoan kernels don't show that problem * bisecting result points to above commit * applies cleanly on cosmic, but has a little conflict on bionic (both master-next) _ perf top hangs and shows error messages ---uname output--- Linux weather 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:27 UTC 2019 s390x s390x s390x GNU/Linux ---Steps to Reproduce--- I start a benchmark (mem_alloc, but it really doesn't matter) and then issue perf top in a second terminal, the output from perf top is correct. Now I stop the benchmark: perf top shows a error message (Not enough memory for annotating '__irf_end' symbol!) and I can't quit from perf top anymore Following analyse took place: No problem with current kernel . Bi-Secting of perf tool took place and following commit was found: commit edeb0c90df3581b821a764052d185df985f8b8dc (HEAD, refs/bisect/bad) Author: Arnaldo Carvalho de Melo Date: Tue Oct 16 17:08:29 2018 -0300 perf tools: Stop fallbacking to kallsyms for vdso symbols lookup When you apply this patch the issue is gone, however it is contained in these versions: git tag --contains edeb0c90df3581b821 v4.19 v4.20 The level I was debugging was kernel 4.15 which does not contain this patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1828166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748689] Re: Mounting SMB shares with vers=3.0 in fstab gives "ioctl error in smb2_get_dfs_refer rc=-2"
I am seeing this ioctl error on my console screen (before login). It fills the screen because I have a crontab job running that mounts an SMB share temporarily. However, I can still create/modify/delete files on the SMB share. I do not know which kernel version this started to show up on but this server has been running since the initial release of 18.04 and it updates itself regularly and I just noticed it. The server it is connecting to is a Windows 2008 R2 Server. Version 6.1 Build 7601: SP1 (all WindowsUpdate patches have been applied as of 2019-07-17) [code]#uname -a Linux FrankNBeans 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux[/code] [code]#lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename: bionic [/code] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1748689 Title: Mounting SMB shares with vers=3.0 in fstab gives "ioctl error in smb2_get_dfs_refer rc=-2" Status in dellserver: New Status in linux package in Ubuntu: Confirmed Bug description: Xubuntu 17.10 artful Kernel: x86_64 Linux 4.13.0-32.35-generic cifs-utils 2:6.7-1 smbclient 2:4.6.7+dfsg-1ubuntu3.1 Mounting an SMB share with sec=ntlmssp,vers=3.0,credentials=/home/.smbcredentials,dir_mode=0777,file_mode=0777 in /etc/fstab gives the error: "CIFS VFS: ioctl error in smb2_get_dfs_refer rc=-2" in dmesg. Shares mounted this way are readable, but writing data to them (or using programs such as EasyTAG to write to them) ultimately fails. This bug did not occur in kernel 4.10. Mounting the share(s) with vers=1.0 does not give the error, but this is a haphazard fix as SMB v3.0 carries many security features with it not avaliable in SMB 1.0. --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=/dev/mapper/DeusVitam--vg-swap_1 JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=/dev/mapper/hostname--vg-root ro splash quiet amdgpu.cik_support=1 vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.169.3 RfKill: Tags: artful Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: Upgraded to artful on 2018-02-05 (7 days ago) UserGroups: libvirt libvirtd sudo wireshark WifiSyslog: _MarkForUpload: True dmi.bios.date: 03/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0701 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-E/USB 3.1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0701:bd03/16/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-E/USB3.1:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1748689/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828166] Re: perf top problem on z with Ubuntu 18.04
Sorry, I missed comment #31, just saw now #32. Please have a look here on how to install the build env. and the kernel sources: https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel Just notice that the deb line in the sources.list file is different for non-x86 (like s390x) It must be: deb-src http://us.ports.ubuntu.com/ubuntu-ports/ bionic main deb-src http://us.ports.ubuntu.com/ubuntu-ports/ bionic-updates main instead of: deb-src http://archive.ubuntu.com/ubuntu bionic main deb-src http://archive.ubuntu.com/ubuntu bionic-updates main -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828166 Title: perf top problem on z with Ubuntu 18.04 Status in Ubuntu on IBM z Systems: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: Invalid Bug description: SRU Justification: == [Impact] * The perf top tool hangs and shows error messages, like 'Not enough memory for annotating' [Fix] * edeb0c90df3581b821a764052d185df985f8b8dc edeb0c9 "perf tools: Stop fallbacking to kallsyms for vdso symbols lookup" [Test Case] * start a benchmark (mem_alloc, but it doesn't really matter what) * execute perf top in a second terminal * the output of perf top is correct * now stop the benchmark * and perf top shows an error message, like "Not enough memory for annotating '__irf_end' symbol!)" * and perf top can't be exited anymore [Regression Potential] * The regression potential can be considered as low since this happens only while using the perf top tool * and it is known that the commit (above) fixes the problem * and the fix is upstream since 4.19 [Other Info] * current disco and eoan kernels don't show that problem * bisecting result points to above commit * applies cleanly on cosmic, but has a little conflict on bionic (both master-next) _ perf top hangs and shows error messages ---uname output--- Linux weather 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:27 UTC 2019 s390x s390x s390x GNU/Linux ---Steps to Reproduce--- I start a benchmark (mem_alloc, but it really doesn't matter) and then issue perf top in a second terminal, the output from perf top is correct. Now I stop the benchmark: perf top shows a error message (Not enough memory for annotating '__irf_end' symbol!) and I can't quit from perf top anymore Following analyse took place: No problem with current kernel . Bi-Secting of perf tool took place and following commit was found: commit edeb0c90df3581b821a764052d185df985f8b8dc (HEAD, refs/bisect/bad) Author: Arnaldo Carvalho de Melo Date: Tue Oct 16 17:08:29 2018 -0300 perf tools: Stop fallbacking to kallsyms for vdso symbols lookup When you apply this patch the issue is gone, however it is contained in these versions: git tag --contains edeb0c90df3581b821 v4.19 v4.20 The level I was debugging was kernel 4.15 which does not contain this patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1828166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748689] Re: Mounting SMB shares with vers=3.0 in fstab gives "ioctl error in smb2_get_dfs_refer rc=-2"
Whoops, my bad. The error code I see is slightly different than this one. Sorry. ioctl error in smb2_get_dfs_refer rc=-5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1748689 Title: Mounting SMB shares with vers=3.0 in fstab gives "ioctl error in smb2_get_dfs_refer rc=-2" Status in dellserver: New Status in linux package in Ubuntu: Confirmed Bug description: Xubuntu 17.10 artful Kernel: x86_64 Linux 4.13.0-32.35-generic cifs-utils 2:6.7-1 smbclient 2:4.6.7+dfsg-1ubuntu3.1 Mounting an SMB share with sec=ntlmssp,vers=3.0,credentials=/home/.smbcredentials,dir_mode=0777,file_mode=0777 in /etc/fstab gives the error: "CIFS VFS: ioctl error in smb2_get_dfs_refer rc=-2" in dmesg. Shares mounted this way are readable, but writing data to them (or using programs such as EasyTAG to write to them) ultimately fails. This bug did not occur in kernel 4.10. Mounting the share(s) with vers=1.0 does not give the error, but this is a haphazard fix as SMB v3.0 carries many security features with it not avaliable in SMB 1.0. --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=/dev/mapper/DeusVitam--vg-swap_1 JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=/dev/mapper/hostname--vg-root ro splash quiet amdgpu.cik_support=1 vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.169.3 RfKill: Tags: artful Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: Upgraded to artful on 2018-02-05 (7 days ago) UserGroups: libvirt libvirtd sudo wireshark WifiSyslog: _MarkForUpload: True dmi.bios.date: 03/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0701 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-E/USB 3.1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0701:bd03/16/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-E/USB3.1:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1748689/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831775] Re: ss seems broken when using multiple filters in the same cmdline
(c)inaddy@iproute2verification:~/work/sources/ubuntu/chrony/test/simulation$ ./111-knownclient Testing reply to client configured as server: network with 1*1 servers and 1 clients: non-default settings: client_conf=acquisitionport 123 server_conf=server 192.168.123.2 noselect acquisitionport 123 starting node 1:OK starting node 2:OK running simulation: OK checking chronyd exit: node 1: OK node 2: OK checking source selection: node 2: OK checking port numbers in packet log: node 1: BAD node 2: BAD FAIL AND (c)inaddy@iproute2verification:~/work/sources/ubuntu/chrony/test/simulation$ ./112-port Testing port and acquisitionport directives: network with 1*1 servers and 1 clients: non-default settings: starting node 1:OK starting node 2:OK running simulation: OK checking chronyd exit: node 1: OK node 2: OK checking source selection: node 2: OK checking mean/min incoming/outgoing packet interval: node 1: 2.74e+02 2.74e+02 6.40e+01 6.40e+01 OK node 2: 2.74e+02 2.74e+02 6.40e+01 6.40e+01 OK checking clock sync time, max/rms time/freq error: node 2: 132 9.29e-05 1.21e-06 5.77e-05 1.01e-07 OK checking port numbers in packet log: node 1: BAD node 2: BAD network with 1*1 servers and 1 clients: non-default settings: client_conf=acquisitionport 123 starting node 1:OK starting node 2:OK running simulation: OK checking chronyd exit: node 1: OK node 2: OK checking port numbers in packet log: node 1: BAD node 2: BAD FAIL -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1831775 Title: ss seems broken when using multiple filters in the same cmdline Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Cosmic: Won't Fix Status in iproute2 source package in Disco: Fix Committed Status in iproute2 source package in Eoan: Fix Released Bug description: [Impact] * ss won't be able to run commands with single filters inside parentheses, like: "( sport == :X )", for example. * A workaround is to remove "( )" from single filters, since it looks the issue does not affect 2 filters being put together in the same parentheses, like: " ( X and Y ) and Y " instead of ( X and Y ) and ( Y )". * CTDB is unable to use ss filter to obtain nodes public IP addresses in order to fail over services (LP: #722201). [Test Case] * Having an Ubuntu Cosmic, Disco or Eoan, try to execute the following command: $ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Independent of the IPs or ports being used. Copying and pasting the command should be enough for you to know if you are affected. Bad Result: ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message ... Expected Result: Recv-QSend-Q Local Address:Port Peer Address:Port ... * test case was discovered during CTDB scripts execution [Regression Potential] * biggest risk would be to affect ss interpreter (worst case scenario). * the proposed patch is based in upstream fix and was tested against the same issue reported as the reproducer (above) and some other generic ss commands. * any problem here is unlikely to change iproute2 most important command interpreter, "ip", since the patch is applied against ss code. [Other Info] ORIGINAL DESCRIPTION: Investigating an issue for CTDB (LP: #722201), after suggesting a
[Kernel-packages] [Bug 1831775] Re: ss seems broken when using multiple filters in the same cmdline
# disco verification: (c)inaddy@iproute2verification:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-QLocal Address:Port Peer Address:Port # migration issue (chrony rev dependency autopkgtests): 109-makestep PASS 110-chronyc PASS 111-knownclient FAIL 112-port FAIL 113-leapsecond PASS 114-presend PASS 115-cmdmontime PASS 116-minsources PASS 117-fallbackdrift PASS These are known as intermittent tests (as I reviewed last chrony upstream merge and they were also failing intermittently). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1831775 Title: ss seems broken when using multiple filters in the same cmdline Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Cosmic: Won't Fix Status in iproute2 source package in Disco: Fix Committed Status in iproute2 source package in Eoan: Fix Released Bug description: [Impact] * ss won't be able to run commands with single filters inside parentheses, like: "( sport == :X )", for example. * A workaround is to remove "( )" from single filters, since it looks the issue does not affect 2 filters being put together in the same parentheses, like: " ( X and Y ) and Y " instead of ( X and Y ) and ( Y )". * CTDB is unable to use ss filter to obtain nodes public IP addresses in order to fail over services (LP: #722201). [Test Case] * Having an Ubuntu Cosmic, Disco or Eoan, try to execute the following command: $ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Independent of the IPs or ports being used. Copying and pasting the command should be enough for you to know if you are affected. Bad Result: ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message ... Expected Result: Recv-QSend-Q Local Address:Port Peer Address:Port ... * test case was discovered during CTDB scripts execution [Regression Potential] * biggest risk would be to affect ss interpreter (worst case scenario). * the proposed patch is based in upstream fix and was tested against the same issue reported as the reproducer (above) and some other generic ss commands. * any problem here is unlikely to change iproute2 most important command interpreter, "ip", since the patch is applied against ss code. [Other Info] ORIGINAL DESCRIPTION: Investigating an issue for CTDB (LP: #722201), after suggesting a fix on ss syntax to CTDB upstream project, we discovered that "ss" seems to be broken in Ubuntu since Ubuntu Cosmic: # Debian Sid inaddy@workstation:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-QSend-Q Local Address:Port Peer Address:Port # Ubuntu Ubuntu 16.04 LTS (Xenial Xerus) (c)inaddy@xenial:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-QLocal Address:Port Peer Address:Port # Ubuntu 18.04 LTS (Bionic Beaver) (c)inaddy@bionic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-Q Local Address:Port Peer Address:Port # Ubuntu 18.10 (Cosmic Cuttlefish) (c)inaddy@cosmic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message # Ubuntu 19.04 (Disco Dingo) (c)inaddy@disco:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] # Ubuntu 19.10 (Eoan Ermine) (c)inaddy@eoan:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] I have generated a pkg using upstream
[Kernel-packages] [Bug 1831775] Re: ss seems broken when using multiple filters in the same cmdline
Actually they are not intermittent, they started happening after ... The upstream merge request into eoan I commented about: https://code.launchpad.net/~paelzer/ubuntu/+source/chrony/+git/chrony/+merge/370185 and my comment: https://code.launchpad.net/~paelzer/ubuntu/+source/chrony/+git/chrony/+merge/369588/comments/967625 This occurs since iproute2/4.18.0-1ubuntu3 triggered the tests. I'm investigating... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1831775 Title: ss seems broken when using multiple filters in the same cmdline Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Cosmic: Won't Fix Status in iproute2 source package in Disco: Fix Committed Status in iproute2 source package in Eoan: Fix Released Bug description: [Impact] * ss won't be able to run commands with single filters inside parentheses, like: "( sport == :X )", for example. * A workaround is to remove "( )" from single filters, since it looks the issue does not affect 2 filters being put together in the same parentheses, like: " ( X and Y ) and Y " instead of ( X and Y ) and ( Y )". * CTDB is unable to use ss filter to obtain nodes public IP addresses in order to fail over services (LP: #722201). [Test Case] * Having an Ubuntu Cosmic, Disco or Eoan, try to execute the following command: $ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Independent of the IPs or ports being used. Copying and pasting the command should be enough for you to know if you are affected. Bad Result: ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message ... Expected Result: Recv-QSend-Q Local Address:Port Peer Address:Port ... * test case was discovered during CTDB scripts execution [Regression Potential] * biggest risk would be to affect ss interpreter (worst case scenario). * the proposed patch is based in upstream fix and was tested against the same issue reported as the reproducer (above) and some other generic ss commands. * any problem here is unlikely to change iproute2 most important command interpreter, "ip", since the patch is applied against ss code. [Other Info] ORIGINAL DESCRIPTION: Investigating an issue for CTDB (LP: #722201), after suggesting a fix on ss syntax to CTDB upstream project, we discovered that "ss" seems to be broken in Ubuntu since Ubuntu Cosmic: # Debian Sid inaddy@workstation:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-QSend-Q Local Address:Port Peer Address:Port # Ubuntu Ubuntu 16.04 LTS (Xenial Xerus) (c)inaddy@xenial:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-QLocal Address:Port Peer Address:Port # Ubuntu 18.04 LTS (Bionic Beaver) (c)inaddy@bionic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-Q Local Address:Port Peer Address:Port # Ubuntu 18.10 (Cosmic Cuttlefish) (c)inaddy@cosmic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message # Ubuntu 19.04 (Disco Dingo) (c)inaddy@disco:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] # Ubuntu 19.10 (Eoan Ermine) (c)inaddy@eoan:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] I have generated a pkg using upstream iproute2 source code and it does not suffer the issue. I have generated a package using Ubuntu cosmic source package, without debian/patches/*, and verified the issue still persists (not being introduced by any of our packages, and being present if vanilla upstream version used in Cosmic). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1831775/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net
[Kernel-packages] [Bug 1836876] Re: linux-raspi2: 4.4.0-1116.125 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1836875 (pi2-kernel) -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1836880 phase: Holding before Promote to Proposed phase-changed: Wednesday, 17. July 2019 13:40 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa main:queued + promote-to-proposed: Holding -- master bug not ready for proposed variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1836876 Title: linux-raspi2: 4.4.0-1116.125 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1836875 (pi2-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1836880 phase: Holding before Promote to Proposed phase-changed: Wednesday, 17. July 2019 13:40 UTC reason: promote-to-proposed: Holding -- master bug not ready for proposed variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1836876/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828166] Comment bridged from LTC Bugzilla
--- Comment From mbri...@us.ibm.com 2019-07-17 11:24 EDT--- (In reply to comment #45) > How can I get the source code of the kernel tree iand the perf tool? > > I have tried this command and it did not get the sources: > > root@s8360046:~# uname -r > 4.15.0-55-generic > root@s8360046:~# apt-get source linux-image-$(uname -r) > Reading package lists... Done > E: You must put some 'source' URIs in your sources.list > root@s8360046:~# > > Thanks for your help Check the file /etc/apt/sources.list on your system, and look for lines beginning with 'deb-src' that are commented out. Uncomment them, and try again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828166 Title: perf top problem on z with Ubuntu 18.04 Status in Ubuntu on IBM z Systems: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: Invalid Bug description: SRU Justification: == [Impact] * The perf top tool hangs and shows error messages, like 'Not enough memory for annotating' [Fix] * edeb0c90df3581b821a764052d185df985f8b8dc edeb0c9 "perf tools: Stop fallbacking to kallsyms for vdso symbols lookup" [Test Case] * start a benchmark (mem_alloc, but it doesn't really matter what) * execute perf top in a second terminal * the output of perf top is correct * now stop the benchmark * and perf top shows an error message, like "Not enough memory for annotating '__irf_end' symbol!)" * and perf top can't be exited anymore [Regression Potential] * The regression potential can be considered as low since this happens only while using the perf top tool * and it is known that the commit (above) fixes the problem * and the fix is upstream since 4.19 [Other Info] * current disco and eoan kernels don't show that problem * bisecting result points to above commit * applies cleanly on cosmic, but has a little conflict on bionic (both master-next) _ perf top hangs and shows error messages ---uname output--- Linux weather 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:27 UTC 2019 s390x s390x s390x GNU/Linux ---Steps to Reproduce--- I start a benchmark (mem_alloc, but it really doesn't matter) and then issue perf top in a second terminal, the output from perf top is correct. Now I stop the benchmark: perf top shows a error message (Not enough memory for annotating '__irf_end' symbol!) and I can't quit from perf top anymore Following analyse took place: No problem with current kernel . Bi-Secting of perf tool took place and following commit was found: commit edeb0c90df3581b821a764052d185df985f8b8dc (HEAD, refs/bisect/bad) Author: Arnaldo Carvalho de Melo Date: Tue Oct 16 17:08:29 2018 -0300 perf tools: Stop fallbacking to kallsyms for vdso symbols lookup When you apply this patch the issue is gone, however it is contained in these versions: git tag --contains edeb0c90df3581b821 v4.19 v4.20 The level I was debugging was kernel 4.15 which does not contain this patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1828166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836880] Re: linux: 4.4.0-156.183 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1836879 (trusty/linux-lts-xenial) derivatives: bug 1834908 (linux-aws), bug 1834909 (linux-kvm), bug 1834915 (linux-fips), bug 1836874 (pc-kernel), bug 1836876 (linux-raspi2), bug 1836878 (linux-snapdragon) -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Wednesday, 17. July 2019 12:03 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building,signed:building + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836880 Title: linux: 4.4.0-156.183 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1836879 (trusty/linux-lts-xenial) derivatives: bug 1834908 (linux-aws), bug 1834909 (linux-kvm), bug 1834915 (linux-fips), bug 1836874 (pc-kernel), bug 1836876 (linux-raspi2), bug 1836878 (linux-snapdragon) -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Wednesday, 17. July 2019 12:03 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1836880/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836925] Re: linux-ibm-gt: 4.15.0-1028.30 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1834954 + phase: Packaging + phase-changed: Wednesday, 17. July 2019 15:25 UTC + reason: + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836925 Title: linux-ibm-gt: 4.15.0-1028.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1834954 phase: Packaging phase-changed: Wednesday, 17. July 2019 15:25 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1836925/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832565] Re: linux-ibm-gt: 4.15.0-1024.26 -proposed tracker
*** This bug is a duplicate of bug 1836925 *** https://bugs.launchpad.net/bugs/1836925 ** This bug is no longer a duplicate of bug 1834941 linux-ibm-gt: 4.15.0-1027.29 -proposed tracker ** This bug has been marked a duplicate of bug 1836925 linux-ibm-gt: -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832565 Title: linux-ibm-gt: 4.15.0-1024.26 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1832578 phase: Holding before Promote to Proposed phase-changed: Friday, 21. June 2019 17:09 UTC reason: promote-to-proposed: Holding -- another kernel is currently pending in Proposed variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832565/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836925] Re: linux-ibm-gt: -proposed tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836925 Title: linux-ibm-gt: 4.15.0-1028.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1834954 phase: Packaging phase-changed: Wednesday, 17. July 2019 15:25 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1836925/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836925] Re: linux-ibm-gt: -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + kernel-stable-master-bug: 1834954 variant: debs ** Tags added: kernel-sru-derivative-of-1834954 ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium ** Summary changed: - linux-ibm-gt: -proposed tracker + linux-ibm-gt: 4.15.0-1028.30 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836925 Title: linux-ibm-gt: 4.15.0-1028.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1834954 phase: Packaging phase-changed: Wednesday, 17. July 2019 15:25 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1836925/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833977] Re: linux-ibm-gt: 4.15.0-1025.27 -proposed tracker
*** This bug is a duplicate of bug 1836925 *** https://bugs.launchpad.net/bugs/1836925 ** This bug is no longer a duplicate of bug 1834941 linux-ibm-gt: 4.15.0-1027.29 -proposed tracker ** This bug has been marked a duplicate of bug 1836925 linux-ibm-gt: -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833977 Title: linux-ibm-gt: 4.15.0-1025.27 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true phase: Holding before Release phase-changed: Thursday, 27. June 2019 15:48 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- kernel-block/kernel-block-proposed tag present variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1833977/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834941] Re: linux-ibm-gt: 4.15.0-1027.29 -proposed tracker
*** This bug is a duplicate of bug 1836925 *** https://bugs.launchpad.net/bugs/1836925 ** Tags removed: kernel-sru-derivative-of-1834954 ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true - kernel-stable-master-bug: 1834954 phase: Ready for Testing phase-changed: Thursday, 11. July 2019 00:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs ** This bug has been marked a duplicate of bug 1836925 linux-ibm-gt: -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834941 Title: linux-ibm-gt: 4.15.0-1027.29 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true phase: Ready for Testing phase-changed: Thursday, 11. July 2019 00:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834954] Re: linux: 4.15.0-55.60 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834950 (xenial/linux-azure), bug 1834953 (xenial/linux-hwe) - derivatives: bug 1834919 (pc-kernel), bug 1834921 (pc-lowlatency-kernel), bug 1834923 (linux-raspi2), bug 1834925 (linux-snapdragon), bug 1834930 (linux-aws), bug 1834936 (linux-gcp), bug 1834939 (linux-gke-4.15), bug 1834940 (linux-kvm), bug 1834941 (linux-ibm-gt), bug 1834943 (linux-oracle), bug 1834944 (linux-fips), bug 1836172 (linux-oem) + derivatives: bug 1834919 (pc-kernel), bug 1834921 (pc-lowlatency-kernel), bug 1834923 (linux-raspi2), bug 1834925 (linux-snapdragon), bug 1834930 (linux-aws), bug 1834936 (linux-gcp), bug 1834939 (linux-gke-4.15), bug 1834940 (linux-kvm), bug 1834943 (linux-oracle), bug 1834944 (linux-fips), bug 1836172 (linux-oem) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Friday, 12. July 2019 17:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834950 (xenial/linux-azure), bug 1834953 (xenial/linux-hwe) - derivatives: bug 1834919 (pc-kernel), bug 1834921 (pc-lowlatency-kernel), bug 1834923 (linux-raspi2), bug 1834925 (linux-snapdragon), bug 1834930 (linux-aws), bug 1834936 (linux-gcp), bug 1834939 (linux-gke-4.15), bug 1834940 (linux-kvm), bug 1834943 (linux-oracle), bug 1834944 (linux-fips), bug 1836172 (linux-oem) + derivatives: bug 1834919 (pc-kernel), bug 1834921 (pc-lowlatency-kernel), bug 1834923 (linux-raspi2), bug 1834925 (linux-snapdragon), bug 1834930 (linux-aws), bug 1834936 (linux-gcp), bug 1834939 (linux-gke-4.15), bug 1834940 (linux-kvm), bug 1834943 (linux-oracle), bug 1834944 (linux-fips), bug 1836172 (linux-oem), bug 1836925 (linux-ibm-gt) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Friday, 12. July 2019 17:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834954 Title: linux: 4.15.0-55.60 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834950 (xenial/linux-azure), bug 1834953 (xenial/linux-hwe) derivatives: bug 1834919 (pc-kernel), bug 1834921 (pc-lowlatency-kernel), bug 1834923 (linux-raspi2), bug 1834925 (linux-snapdragon), bug 1834930 (linux-aws), bug 1834936 (linux-gcp), bug 1834939 (linux-gke-4.15), bug 1834940 (linux-kvm), bug 1834943 (linux-oracle), bug 1834944 (linux-fips), bug 1836172 (linux-oem), bug 1836925 (linux-ibm-gt) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Friday, 12. July 2019 17:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress
[Kernel-packages] [Bug 1834528] Re: linux-ibm-gt: 4.15.0-1026.28 -proposed tracker
*** This bug is a duplicate of bug 1836925 *** https://bugs.launchpad.net/bugs/1836925 ** This bug is no longer a duplicate of bug 1834941 linux-ibm-gt: 4.15.0-1027.29 -proposed tracker ** This bug has been marked a duplicate of bug 1836925 linux-ibm-gt: -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834528 Title: linux-ibm-gt: 4.15.0-1026.28 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1833987 phase: Complete phase-changed: Tuesday, 02. July 2019 06:32 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834528/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836925] [NEW] linux-ibm-gt: 4.15.0-1028.30 -proposed tracker
Public bug reported: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1834954 phase: Packaging phase-changed: Wednesday, 17. July 2019 15:25 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded variant: debs ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Kleber Sacilotto de Souza (kleber-souza) Status: In Progress ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Kleber Sacilotto de Souza (kleber-souza) Status: In Progress ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: Invalid ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: Invalid ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Bionic) Importance: Medium Status: Confirmed ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2019.07.01-8 kernel-sru-derivative-of-1834954 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Tags added: bionic kernel-release-tracking-bug ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru) ** Changed in: kernel-sru-workflow/promote-to-security Importance: Undecided => Medium ** Changed in:
[Kernel-packages] [Bug 1828166] Comment bridged from LTC Bugzilla
--- Comment From tmri...@de.ibm.com 2019-07-17 11:06 EDT--- How can I get the source code of the kernel tree iand the perf tool? I have tried this command and it did not get the sources: root@s8360046:~# uname -r 4.15.0-55-generic root@s8360046:~# apt-get source linux-image-$(uname -r) Reading package lists... Done E: You must put some 'source' URIs in your sources.list root@s8360046:~# Thanks for your help -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828166 Title: perf top problem on z with Ubuntu 18.04 Status in Ubuntu on IBM z Systems: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: Invalid Bug description: SRU Justification: == [Impact] * The perf top tool hangs and shows error messages, like 'Not enough memory for annotating' [Fix] * edeb0c90df3581b821a764052d185df985f8b8dc edeb0c9 "perf tools: Stop fallbacking to kallsyms for vdso symbols lookup" [Test Case] * start a benchmark (mem_alloc, but it doesn't really matter what) * execute perf top in a second terminal * the output of perf top is correct * now stop the benchmark * and perf top shows an error message, like "Not enough memory for annotating '__irf_end' symbol!)" * and perf top can't be exited anymore [Regression Potential] * The regression potential can be considered as low since this happens only while using the perf top tool * and it is known that the commit (above) fixes the problem * and the fix is upstream since 4.19 [Other Info] * current disco and eoan kernels don't show that problem * bisecting result points to above commit * applies cleanly on cosmic, but has a little conflict on bionic (both master-next) _ perf top hangs and shows error messages ---uname output--- Linux weather 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:27 UTC 2019 s390x s390x s390x GNU/Linux ---Steps to Reproduce--- I start a benchmark (mem_alloc, but it really doesn't matter) and then issue perf top in a second terminal, the output from perf top is correct. Now I stop the benchmark: perf top shows a error message (Not enough memory for annotating '__irf_end' symbol!) and I can't quit from perf top anymore Following analyse took place: No problem with current kernel . Bi-Secting of perf tool took place and following commit was found: commit edeb0c90df3581b821a764052d185df985f8b8dc (HEAD, refs/bisect/bad) Author: Arnaldo Carvalho de Melo Date: Tue Oct 16 17:08:29 2018 -0300 perf tools: Stop fallbacking to kallsyms for vdso symbols lookup When you apply this patch the issue is gone, however it is contained in these versions: git tag --contains edeb0c90df3581b821 v4.19 v4.20 The level I was debugging was kernel 4.15 which does not contain this patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1828166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801540] Re: Microphone distorted sound on ALC892/1220 on AMD chipsets
May as well join the fun. Believed I tried every suggested work around above, still got crackling. In my case the crackling is present on the line-in 3.5mm jack plug and not a microphone. I run: X470 GAMING PRO (MS-7B79) motherboard with a ALC892, Ryzen 2700, Radeon RX Vega 54. Running Ubuntu 19.04, Kernel 5.0.0-20-generic (was hoping kernel 5 would improve things). I did notice that the crackling reduced a bit when using this setting in /etc/default.pa ### Automatically load driver modules depending on the hardware available .ifexists module-udev-detect.so load-module module-udev-detect use_ucm=0 tsched=0 .else ### Use the static hardware detection module (for systems that lack udev suppor$ load-module module-detect tsched=0 .endif I use a Loopback (# pactl load-module module-loopback latency_msec=1) to pipe some line in audio (chiptune device('s)) into PulseAudio if that's something useful to know. Really annoying problem, makes me feel ashamed using Linux, really nice up to date computer (hardware) and some trivial piece of sillycon working with every other OS refuses to work on Linux. Don't know who to blame, but blaming I do! USB soundcapture isn't really the thing I'm looking for. Unnecessary latency is often a thing I try to avoid. Who wants to trade a X470 GAMING PRO for a X470 board that has working sound on Linux?? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836876] Re: linux-raspi2: 4.4.0-1116.125 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1836875 (pi2-kernel) -- swm properties -- kernel-stable-master-bug: 1836880 phase: Holding before Promote to Proposed phase-changed: Wednesday, 17. July 2019 13:40 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building + promote-to-proposed: Pending -- builds not complete in ppa main:queued variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1836876 Title: linux-raspi2: 4.4.0-1116.125 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1836875 (pi2-kernel) -- swm properties -- kernel-stable-master-bug: 1836880 phase: Holding before Promote to Proposed phase-changed: Wednesday, 17. July 2019 13:40 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa main:queued variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1836876/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799988] Re: Missing wifi and bluetooth after sleep on XPS 9370
** Changed in: linux (Ubuntu) Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799988 Title: Missing wifi and bluetooth after sleep on XPS 9370 Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: I have XPS9370 with self-installed Ubuntu 18.10 (not project sputnik) with Killer 1435 wireless module. And sometimes I find wifi and bluetooth missing after sleep. I cannot exactly define preconditions, but it seems there are following steps to reproduce the issue 1. Connect something via bluetooth (I use bluetooth headset) 2. Send laptop to sleep 3. Wake it and find wifi and bluetooth missing. I have to mention that I have also been experienced bluetooth only missing, but it somehow transformed to the issue with both wireless devices. Dmesg after waking up with the issue attached --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kao2362 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-09-22 (33 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180922) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 012: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=34230cbd-d3d2-4cb8-855a-307883bc35ea ro quiet splash mem_sleep_default=deep video=1920x1080 usbcore.dyndbg=+p vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0VM1FG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0VM1FG:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1799988/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836914] Re: Doing multiple squashfs (and other loop?) mounts in parallel breaks
Test script ** Attachment added: "testcase.lp1836914.sh" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836914/+attachment/5277652/+files/testcase.lp1836914.sh -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836914 Title: Doing multiple squashfs (and other loop?) mounts in parallel breaks Status in linux package in Ubuntu: Confirmed Bug description: On a system running a 5.2 kernel, doing a large number of mounts of squashfs filesystems in parallel results in the mounts getting out of sync with their backing devices. To reproduce, https://paste.ubuntu.com/p/VCpzGxvy6h/ this breaks people with ~40 snaps (easily achievable given snapd leaves up to 3 previous revisions of snaps mounted at any given time, so a person with ~13 snaps that get updated often will hit this number). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-8-generic 5.2.0-8.9 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Wed Jul 17 15:11:15 2019 InstallationDate: Installed on 2019-07-17 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190716) IwConfig: ens3 no wireless extensions. lono wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic root=UUID=9618ebbb-955d-4daf-b29a-37162ec7821a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.180 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)
** Changed in: linux (Ubuntu) Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.13.0-21.24-generic 4.13.13 I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 17.04, which gave me this error after 2 weeks of usage. After that, I installed 16.04 and used it for MONTHS without any problems, until it produced the same error this week. I think it has to do with the ubuntu updates, because I did one recently and one today, just before this problem. Could be a coincidence though. I notice the error when I try to save something on disk and it says me that the disk is in read-only mode: lz@lz:/var/log$ touch something touch: cannot touch 'something': Read-only file system lz@lz:/var/log$ cat syslog Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 lz@lz:/var/log$ dmesg [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.377374] Aborting journal on device nvme0n1p2-8. [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" capability=12 capname="net_admin" Rebooting the ubuntu will give me a black terminal where I can run fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of orphaned inodes. The majority of time it boots back to the Ubuntu working good, but some times it boots to a broken ubuntu (no images, lots of things broken). I have to reinstall ubuntu then. Every time I reinstall my Ubuntu, I have to try lots of times until it installs without an Input/Output error. When it installs, I can use it for some hours without having the problem, but if I run the software updates, it ALWAYS crashes and enters in read-only mode, specifically in the part that is installing kernel updates. I noticed that Ubuntu installs updates automatically when they're for security reasons. Could this be the reason my Ubuntu worked for months without the problem, but then an update was applied and it broke? I thought that this bug was happening: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried different nvme_core.default_ps_max_latency_us= combinations, all them gave errors. I just changed to 0 and I had no error while using ubuntu (however I didn't test for a long time) but I still had the error after trying to update my ubuntu. My Samsung 512gb SSD is: SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q on a Razer Blade Stealth. I also asked this on ask ubuntu, without success: https://askubuntu.com/questions/998471/razer-blade-stealth-disk- corruption-fsck-needed-probably-samsung-ssd-bug-afte Please help me, as I need this computer to work on lots of things :c --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lz 1088 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2018-01-30 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Razer Blade Stealth Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine:
[Kernel-packages] [Bug 1836630] Re: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend
As of now PCI core skips pci_prepare_to_sleep(), which put device to D3, if pci_save_state() was called by the driver's suspend callback. IMO there are two ways to handle this: 1) Don't call pci_save_state(). 2) Manually put device to D3 after pci_save_state(). Let's try 1) first: diff --git a/nv.c b/nv.c index b6dc6f3..ed250c8 100644 --- a/nv.c +++ b/nv.c @@ -4200,8 +4200,6 @@ nv_power_management( nv_kthread_q_stop(>bottom_half_q); nv_disable_pat_support(); - -pci_save_state(nvl->pci_dev); break; } case NV_PM_ACTION_RESUME: -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: system76 1721 F pulseaudio /dev/snd/controlC0: system76 1721 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 MachineType: System76 Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux-hwe-edge ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: oryp5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOryxPro:rvroryp5:cvnSystem76:ct10:cvroryp5: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1836630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836916] Re: alsa/hdmi: add icelake hdmi audio support for a Dell machine
** Description changed: - 1) install dell-bto-bionic-beaver-osp1-loras-X08-20190620-5.iso, boot into OS in Powersaving mode - 2) check sound setting - 3) reboot system via power menu with AC - 4) check sound setting - 5) cold boot via power menu with AC - 6) check sound setting - 7) reboot system via power menu with DC - 8) check sound setting - 9) cold boot via power menu with DC - 10) check sound setting - 11) switch to Performance mode and repeat 2) to 10) + [Impact] + On a Dell icelake platform, the hdmi audio doesn't work at all, when users + plug hdmi cable, they can't find hdmi audio from gnome-sound-setting. - Expected results: audio should work well after reboot + [Fix] + add icl hdmi audio id and related support patch to alsa driver. - Actual results: - unknown built-in Headphones list in sound setting --> audio function can not work (e.g internal speaker/ external headset / HDMI/DP audio) + [Test Case] + after applying the patchset, we plug hdmi cable and the hdmi audio shows up + in the sound-setting and works well, after unplugging the cable, the hdmi + audio disappears as expected. + + [Regression Risk] + Low. this patchset is specific to a icl hdmi audio codec. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836916 Title: alsa/hdmi: add icelake hdmi audio support for a Dell machine Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] On a Dell icelake platform, the hdmi audio doesn't work at all, when users plug hdmi cable, they can't find hdmi audio from gnome-sound-setting. [Fix] add icl hdmi audio id and related support patch to alsa driver. [Test Case] after applying the patchset, we plug hdmi cable and the hdmi audio shows up in the sound-setting and works well, after unplugging the cable, the hdmi audio disappears as expected. [Regression Risk] Low. this patchset is specific to a icl hdmi audio codec. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1836916/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836914] Re: Doing multiple squashfs (and other loop?) mounts in parallel breaks
The mainline builds for i386 and amd64 are failing right now so not sure I can do more. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836914 Title: Doing multiple squashfs (and other loop?) mounts in parallel breaks Status in linux package in Ubuntu: Confirmed Bug description: On a system running a 5.2 kernel, doing a large number of mounts of squashfs filesystems in parallel results in the mounts getting out of sync with their backing devices. To reproduce, https://paste.ubuntu.com/p/VCpzGxvy6h/ this breaks people with ~40 snaps (easily achievable given snapd leaves up to 3 previous revisions of snaps mounted at any given time, so a person with ~13 snaps that get updated often will hit this number). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-8-generic 5.2.0-8.9 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Wed Jul 17 15:11:15 2019 InstallationDate: Installed on 2019-07-17 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190716) IwConfig: ens3 no wireless extensions. lono wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic root=UUID=9618ebbb-955d-4daf-b29a-37162ec7821a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.180 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836916] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1836916 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836916 Title: alsa/hdmi: add icelake hdmi audio support for a Dell machine Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: 1) install dell-bto-bionic-beaver-osp1-loras-X08-20190620-5.iso, boot into OS in Powersaving mode 2) check sound setting 3) reboot system via power menu with AC 4) check sound setting 5) cold boot via power menu with AC 6) check sound setting 7) reboot system via power menu with DC 8) check sound setting 9) cold boot via power menu with DC 10) check sound setting 11) switch to Performance mode and repeat 2) to 10) Expected results: audio should work well after reboot Actual results: unknown built-in Headphones list in sound setting --> audio function can not work (e.g internal speaker/ external headset / HDMI/DP audio) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1836916/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836916] [NEW] alsa/hdmi: add icelake hdmi audio support for a Dell machine
Public bug reported: 1) install dell-bto-bionic-beaver-osp1-loras-X08-20190620-5.iso, boot into OS in Powersaving mode 2) check sound setting 3) reboot system via power menu with AC 4) check sound setting 5) cold boot via power menu with AC 6) check sound setting 7) reboot system via power menu with DC 8) check sound setting 9) cold boot via power menu with DC 10) check sound setting 11) switch to Performance mode and repeat 2) to 10) Expected results: audio should work well after reboot Actual results: unknown built-in Headphones list in sound setting --> audio function can not work (e.g internal speaker/ external headset / HDMI/DP audio) ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Critical Assignee: Hui Wang (hui.wang) Status: Incomplete ** Tags: originate-from-1834277 somerville ** Changed in: linux (Ubuntu) Importance: Undecided => Critical ** Tags added: originate-from-1834277 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836916 Title: alsa/hdmi: add icelake hdmi audio support for a Dell machine Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: 1) install dell-bto-bionic-beaver-osp1-loras-X08-20190620-5.iso, boot into OS in Powersaving mode 2) check sound setting 3) reboot system via power menu with AC 4) check sound setting 5) cold boot via power menu with AC 6) check sound setting 7) reboot system via power menu with DC 8) check sound setting 9) cold boot via power menu with DC 10) check sound setting 11) switch to Performance mode and repeat 2) to 10) Expected results: audio should work well after reboot Actual results: unknown built-in Headphones list in sound setting --> audio function can not work (e.g internal speaker/ external headset / HDMI/DP audio) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1836916/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836914] Re: Doing multiple squashfs (and other loop?) mounts in parallel breaks
I haven't yet tried to reproduce this with an upstream kernel, but given that it's affecting arch users with 5.2 as well, it's fairly likely to be there. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836914 Title: Doing multiple squashfs (and other loop?) mounts in parallel breaks Status in linux package in Ubuntu: Confirmed Bug description: On a system running a 5.2 kernel, doing a large number of mounts of squashfs filesystems in parallel results in the mounts getting out of sync with their backing devices. To reproduce, https://paste.ubuntu.com/p/VCpzGxvy6h/ this breaks people with ~40 snaps (easily achievable given snapd leaves up to 3 previous revisions of snaps mounted at any given time, so a person with ~13 snaps that get updated often will hit this number). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-8-generic 5.2.0-8.9 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Wed Jul 17 15:11:15 2019 InstallationDate: Installed on 2019-07-17 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190716) IwConfig: ens3 no wireless extensions. lono wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic root=UUID=9618ebbb-955d-4daf-b29a-37162ec7821a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.180 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp