[Kernel-packages] [Bug 1842590] Re: xenial/linux-gcp: 4.15.0-1043.45 -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: 1842828 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Promote to Proposed phase-changed: Monday, 09. September 2019 04:51 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa main:failed,meta:queued,signed:depwait + promote-to-proposed: Pending -- builds not complete in ppa main:failed,signed:depwait trackers: bionic/linux-gcp: bug 1842838 bionic/linux-gke-5.0: bug 1842840 xenial/linux-gcp/gcp-kernel: bug 1842588 xenial/linux-gcp/gke-kernel: bug 1842589 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1842590 Title: xenial/linux-gcp: 4.15.0-1043.45 -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-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-gcp package in Ubuntu: Invalid Status in linux-gcp 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 -- kernel-stable-master-bug: 1842828 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Promote to Proposed phase-changed: Monday, 09. September 2019 04:51 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa main:failed,signed:depwait trackers: bionic/linux-gcp: bug 1842838 bionic/linux-gke-5.0: bug 1842840 xenial/linux-gcp/gcp-kernel: bug 1842588 xenial/linux-gcp/gke-kernel: bug 1842589 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842590/+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 1842838] Re: bionic/linux-gcp: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** 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: 1842590 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Holding before Packaging - phase-changed: Thursday, 05. September 2019 05:06 UTC + phase: Ready for Packaging + phase-changed: Monday, 09. September 2019 04:51 UTC reason: - prepare-package: Holding -- waiting for master bug + prepare-package: Pending -- version not specified replaces: bug 1842549 trackers: bionic/linux-gcp-edge: bug 1842837 bionic/linux-gcp/gcp-kernel: bug 1842836 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1842838 Title: bionic/linux-gcp: -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: Confirmed Status in Kernel SRU Workflow prepare-package-lrm series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New 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-gcp package in Ubuntu: Invalid Status in linux-gcp 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: 1842590 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Ready for Packaging phase-changed: Monday, 09. September 2019 04:51 UTC reason: prepare-package: Pending -- version not specified replaces: bug 1842549 trackers: bionic/linux-gcp-edge: bug 1842837 bionic/linux-gcp/gcp-kernel: bug 1842836 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842838/+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 1842590] Re: xenial/linux-gcp: 4.15.0-1043.45 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Committed => 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: 1842828 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Packaging - phase-changed: Friday, 06. September 2019 18:20 UTC + phase: Holding before Promote to Proposed + phase-changed: Monday, 09. September 2019 04:51 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Pending -- builds not complete in ppa main:failed,meta:queued,signed:depwait trackers: bionic/linux-gcp: bug 1842838 bionic/linux-gke-5.0: bug 1842840 xenial/linux-gcp/gcp-kernel: bug 1842588 xenial/linux-gcp/gke-kernel: bug 1842589 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1842590 Title: xenial/linux-gcp: 4.15.0-1043.45 -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-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-gcp package in Ubuntu: Invalid Status in linux-gcp 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 -- kernel-stable-master-bug: 1842828 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Promote to Proposed phase-changed: Monday, 09. September 2019 04:51 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa main:failed,meta:queued,signed:depwait trackers: bionic/linux-gcp: bug 1842838 bionic/linux-gke-5.0: bug 1842840 xenial/linux-gcp/gcp-kernel: bug 1842588 xenial/linux-gcp/gke-kernel: bug 1842589 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842590/+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 1842557] Re: disco/linux-snapdragon: 5.0.0-1020.21 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => 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: 1842561 packages: main: linux-snapdragon meta: linux-meta-snapdragon - phase: Packaging - phase-changed: Friday, 06. September 2019 10:50 UTC + phase: Holding before Promote to Proposed + phase-changed: Monday, 09. September 2019 04:30 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 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/1842557 Title: disco/linux-snapdragon: 5.0.0-1020.21 -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 Disco: 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: 1842561 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Holding before Promote to Proposed phase-changed: Monday, 09. September 2019 04:30 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842557/+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 1835614] Re: Touchpad not recognized
[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/1835614 Title: Touchpad not recognized Status in linux package in Ubuntu: Expired Bug description: I have an Ubuntu 19.04 installed on HP Omen 15ce-006nk I can not use the touchpad, it seems unrecognized by the OS I attached the output of cat /proc/bus/input/devices > devices ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-20-generic 5.0.0-20.21 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: exo1549 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 6 16:40:01 2019 InstallationDate: Installed on 2019-07-02 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 0bda:58e6 Realtek Semiconductor Corp. Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP OMEN by HP Laptop 15-ce0xx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=UUID=5c61d159-7664-4d88-86c0-b3884c70e5df ro acpi=off i18042.reset quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-20-generic N/A linux-backports-modules-5.0.0-20-generic N/A linux-firmware1.178.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/29/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.08 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 838F dmi.board.vendor: HP dmi.board.version: 40.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.08:bd09/29/2017:svnHP:pnOMENbyHPLaptop15-ce0xx:pvr:rvnHP:rn838F:rvr40.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 15-ce0xx dmi.product.sku: 2HQ17EA#BH4 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835614/+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 1836026] Re: There is no the screen rotation option in Settings with sensor LNG2DM
[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/1836026 Title: There is no the screen rotation option in Settings with sensor LNG2DM Status in linux package in Ubuntu: Expired Bug description: If a machine has a accelerometer, the screen rotation option won't be drawn in Settings. But, we cannot read the accelerometer raw data from the sensor LNG2DM. The value always is 0 in in_accel_x_raw, in_accel_y_raw and in_accel_y_raw. Upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=200775 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836026/+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 1842447] Re: Kernel Panic with linux-image-4.15.0-60-generic when specifying nameserver in docker-compose
FTR, 4.15.0-62 seems *much* better than 4.15.0-60. With 4.15.0-60 this system was kernel panic restarting every 75-90 minutes; now it's been up since I installed 4.15.0-62, over 5 hours ago: -=- cut here -=- ewen@naosr620:~$ uname -r 4.15.0-62-generic ewen@naosr620:~$ uptime 16:09:54 up 5:26, 1 user, load average: 0.24, 0.25, 0.24 ewen@naosr620:~$ -=- cut here -=- That one line fix seems important :-) Ewen -- 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/1842447 Title: Kernel Panic with linux-image-4.15.0-60-generic when specifying nameserver in docker-compose Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] Some fragmentation+NAT workloads will cause kernel BUG/Ooops. [Test case] sudo iptables -t nat -I POSTROUTING -j MASQUERADE sudo hping3 192.168.122.1 -s 1000 -p 2000 -d 6 [Regression potential] This could make fragmented packets stop flowing. So, make sure fragmented pings still work. ping 192.168.122.1 -s 6 still works, even with the above nat rule. Hello, there are multiple inquries in the mailcow GitHub issues over at https://github.com/mailcow/mailcow-dockerized/issues/2904 that the latest kernel linux-image-4.15.0-60-generic causes kernel panics when "- dns" setting is used within the docker-compose.yml file, for yet some unclear reasons. Multiple users on different systems (e.g. virtualized ones on VMware ESXi and KVM) were able to reproduce the same issue. I was also able to reproduce this constantly on a completely new deployed Ubuntu 18.04 VM (KVM) with a fresh mailcow installation. Steps to reproduce: 1. Install a clean Ubuntu 18.04(.03) machine 2. Upgrade the installation to linux-image-4.15.0-60-generic 3. Setup mailcow as instructed at https://mailcow.github.io/mailcow-dockerized-docs/i_u_m_install/ (just takes less than a minute, easy to reproduce) 4. Start mailcow with "dns"-settings specified in docker-compose file (Make sure using the older docker-compose version with dns settings: https://raw.githubusercontent.com/mailcow/mailcow-dockerized/a1403b7a5969637df23001d05c59c2a20774fbb5/docker-compose.yml) 5. Wait a few minutes, then kernel crash appears Using this workaround it appears to be stable again: https://github.com/mailcow/mailcow- dockerized/commit/dc6eea5142c063e26408a685b66fbb7754408ec2 I've attached the apport file to this bug. Please let me know if you need any kind of further information. (As this is my first bug report here, I hope I have included all required information helping you finding the cause.) Kind regards, Patrik To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842447/+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 1842587] Re: xenial/linux-azure: 4.15.0-1057.62 -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: 1842828 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Testing phase-changed: Friday, 06. September 2019 05:48 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: - trusty/linux-azure: bug 1842819, bug 1842585 + trusty/linux-azure: bug 1842585, bug 1842819 xenial/linux-azure-edge: bug 1842584 xenial/linux-azure/azure-kernel: bug 1842583 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1842587 Title: xenial/linux-azure: 4.15.0-1057.62 -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 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: Confirmed Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure 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: 1842828 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Testing phase-changed: Friday, 06. September 2019 05:48 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1842585, bug 1842819 xenial/linux-azure-edge: bug 1842584 xenial/linux-azure/azure-kernel: bug 1842583 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842587/+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 1842773] Re: bionic/linux-oracle: 4.15.0-1023.26 -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: 1842746 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Friday, 06. September 2019 07:00 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: - xenial/linux-oracle: bug 1842772, bug 1842724 + xenial/linux-oracle: bug 1842724, bug 1842772 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1842773 Title: bionic/linux-oracle: 4.15.0-1023.26 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress 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-lrm 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: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle 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: 1842746 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Friday, 06. September 2019 07:00 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-oracle: bug 1842724, bug 1842772 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842773/+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 1843207] [NEW] Doesn't boot on Raspberry Pi 4
Public bug reported: linux-raspi2 from Eoan (19.10) doesn't boot on Raspberry Pi 4 due to missing kernel modules for the new hardware components. It would be nice if these got included. Also it only boots the kernel when the Pi is configured for 1GB RAM or less. (Then gets stuck on missing root FS because the microSD isn't detected.) ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New -- 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/1843207 Title: Doesn't boot on Raspberry Pi 4 Status in linux-raspi2 package in Ubuntu: New Bug description: linux-raspi2 from Eoan (19.10) doesn't boot on Raspberry Pi 4 due to missing kernel modules for the new hardware components. It would be nice if these got included. Also it only boots the kernel when the Pi is configured for 1GB RAM or less. (Then gets stuck on missing root FS because the microSD isn't detected.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1843207/+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 1842587] Re: xenial/linux-azure: 4.15.0-1057.62 -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: 1842828 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Testing phase-changed: Friday, 06. September 2019 05:48 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: - trusty/linux-azure: bug 1842585, bug 1842819 + trusty/linux-azure: bug 1842819, bug 1842585 xenial/linux-azure-edge: bug 1842584 xenial/linux-azure/azure-kernel: bug 1842583 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1842587 Title: xenial/linux-azure: 4.15.0-1057.62 -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 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: Confirmed Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure 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: 1842828 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Testing phase-changed: Friday, 06. September 2019 05:48 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1842819, bug 1842585 xenial/linux-azure-edge: bug 1842584 xenial/linux-azure/azure-kernel: bug 1842583 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842587/+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 1842608] Re: xenial/linux: 4.4.0-162.190 -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 -- packages: main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Wednesday, 04. September 2019 07:52 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa main:failed,meta:depwait trackers: trusty/linux-aws: bug 1842793, bug 1842606 - trusty/linux-lts-xenial: bug 1842607, bug 1842794 + trusty/linux-lts-xenial: bug 1842794, bug 1842607 xenial/linux-aws: bug 1842597 xenial/linux-fips: bug 1842605 xenial/linux-kvm: bug 1842598 xenial/linux-raspi2: bug 1842600 xenial/linux-snapdragon: bug 1842603 xenial/linux/pc-kernel: bug 1842595 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/1842608 Title: xenial/linux: 4.4.0-162.190 -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 -- swm properties -- packages: main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Wednesday, 04. September 2019 07:52 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa main:failed,meta:depwait trackers: trusty/linux-aws: bug 1842793, bug 1842606 trusty/linux-lts-xenial: bug 1842794, bug 1842607 xenial/linux-aws: bug 1842597 xenial/linux-fips: bug 1842605 xenial/linux-kvm: bug 1842598 xenial/linux-raspi2: bug 1842600 xenial/linux-snapdragon: bug 1842603 xenial/linux/pc-kernel: bug 1842595 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842608/+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 1843152] Re: Kernel Panic with linux kernel 4.15.0-60 possibly related to network subsystem
These symptoms sound very much like https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842447 (I found the bug I'm commenting on while searching for additional links about the issue in 1842447). There's a -62 kernel in proposed updates which hopefully contains the fix for this bug. See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842447 for hints on how to install the proposed update kernel. So far the trigger is sounding like NAT + 4.15.0-60 kernel + sufficient time that the relevant uninitialised variable is not clean from boot. I think this is the fix in -62: https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/?h=master- next=b502cfeffec81be8564189e5498fd3f252b27900 Ewen -- 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/1843152 Title: Kernel Panic with linux kernel 4.15.0-60 possibly related to network subsystem Status in linux package in Ubuntu: Confirmed Bug description: 1. Releases: Ubuntu Server 16.04 and Ubuntu Server 18.04 2. Package: Linux Kernel 4.15.0-60 amd64 3. What I expected to happen: Not a recurrent kernel panic. 4. What happened instead: Recurrent kernel panic. While running Ubuntu 16.04 server on an internet appliance that was serving as my router, after the system was updated from kernel 4.15.0-58 to 4.15.0-60, I began getting frequent kernel panics (system seldom remained up for more than an hour after a reboot). I have included example stack traces below. After memtest revealed no problems, and fsck revealed no problems, I opted to rebuild from a fresh install, this time of Ubuntu 18.04, server. Upon completing the rebuilt, and put it back in service. It crashed with the same kernel panic within 30 minutes. I have since updated to kernel 5.0.0-27 and the kernel panics have completely stopped. [10170.296117] kernel BUG at /build/linux-5mCauq/linux-4.15.0/net/ipv4/ip_output.c:636! [10170.304214] invalid opcode: [#1] SMP PTI [10170.308692] Modules linked in: st lp parport_pc ppdev parport ipt_REJECT nf_reject_ipv4 xt_condition(OE) xt_time xt_comment xt_iface(OE) xt_multiport xt_conntrack xt_set xt_recent xt_hashlimit xt_addrtype xt_mark iptable_mangle xt_nat xt_REDIRECT nf_nat_redirect ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_iprange iptable_nat nf_nat_ipv4 nf_conntrack_ipv4 nf_defrag_ipv4 xt_tcpudp xt_CT iptable_raw ip_set_list_set ip_set_hash_ip ip_set_hash_net ip_set_hash_mac ip_set xt_NFLOG nfnetlink_log nf_log_ipv4 nf_log_common xt_LOG nf_conntrack_sane nf_conntrack_netlink nfnetlink nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda nf_nat nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_netbios_ns [10170.381810] nf_conntrack_broadcast nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp ts_kmp nf_conntrack_amanda nf_conntrack iptable_filter bridge intel_rapl intel_soc_dts_thermal intel_soc_dts_iosf intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm irqbypass punit_atom_debug intel_cstate snd_hda_intel snd_hda_codec snd_hda_core joydev snd_hwdep snd_pcm snd_timer serio_raw input_leds snd lpc_ich soundcore shpchp mac_hid mei_txe mei sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 8021q garp mrp stp llc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear i915 crct10dif_pclmul crc32_pclmul i2c_algo_bit drm_kms_helper [10170.454089] ghash_clmulni_intel e1000e syscopyarea sysfillrect sysimgblt fb_sys_fops ptp ahci psmouse cryptd drm pps_core libahci video hid_generic usbhid hid [last unloaded: parport_pc] [10170.471175] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G OE 4.15.0-60-generic #67-Ubuntu [10170.480269] Hardware name: Protectli FW1/FW1, BIOS 5.6.5 05/14/2019 [10170.486704] RIP: 0010:ip_do_fragment+0x482/0x820 [10170.491462] RSP: 0018:92533fc83a18 EFLAGS: 00010202 [10170.496824] RAX: 0001 RBX: 92532b43ed00 RCX: 8d64cdf0 [10170.504158] RDX: 0024 RSI: 05c8 RDI: 925329f06300 [10170.511485] RBP: 92533fc83a80 R08: 925330be9700 R09: 05dc [10170.518777] R10: R11: 92533fc839d0 R12: 0014 [10170.526096] R13: 92532dea4300 R14: 2328 R15: 925330be974e [10170.533430] FS: () GS:92533fc8() knlGS: [10170.541729] CS: 0010 DS: ES: CR0: 80050033 [10170.547631] CR2: 7f3a9dd13b80 CR3: 9640a000 CR4: 001006e0 [10170.554957] Call Trace: [10170.557452] [10170.559541] ? ip_copy_metadata+0x220/0x220 [10170.563849]
[Kernel-packages] [Bug 1842447] Re: Kernel Panic with linux-image-4.15.0-60-generic when specifying nameserver in docker-compose
FTR, I think this is the fix in -62: https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/?h=master- next=b502cfeffec81be8564189e5498fd3f252b27900 and it appears to be the only change from -60 to -62: -=- cut here -=- ewen@naosr620:~$ zcat /usr/share/doc/linux-headers-4.15.0-62-generic/changelog.Debian.gz | head -9 linux (4.15.0-62.69) bionic; urgency=medium * bionic/linux: 4.15.0-62.69 -proposed tracker (LP: #1842746) * Kernel Panic with linux-image-4.15.0-60-generic when specifying nameserver in docker-compose (LP: #1842447) - ip: frags: fix crash in ip_do_fragment() -- Khalid Elmously Wed, 04 Sep 2019 16:11:43 -0400 ewen@naosr620:~$ -=- cut here -=- It's a one line fix. Ewen -- 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/1842447 Title: Kernel Panic with linux-image-4.15.0-60-generic when specifying nameserver in docker-compose Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] Some fragmentation+NAT workloads will cause kernel BUG/Ooops. [Test case] sudo iptables -t nat -I POSTROUTING -j MASQUERADE sudo hping3 192.168.122.1 -s 1000 -p 2000 -d 6 [Regression potential] This could make fragmented packets stop flowing. So, make sure fragmented pings still work. ping 192.168.122.1 -s 6 still works, even with the above nat rule. Hello, there are multiple inquries in the mailcow GitHub issues over at https://github.com/mailcow/mailcow-dockerized/issues/2904 that the latest kernel linux-image-4.15.0-60-generic causes kernel panics when "- dns" setting is used within the docker-compose.yml file, for yet some unclear reasons. Multiple users on different systems (e.g. virtualized ones on VMware ESXi and KVM) were able to reproduce the same issue. I was also able to reproduce this constantly on a completely new deployed Ubuntu 18.04 VM (KVM) with a fresh mailcow installation. Steps to reproduce: 1. Install a clean Ubuntu 18.04(.03) machine 2. Upgrade the installation to linux-image-4.15.0-60-generic 3. Setup mailcow as instructed at https://mailcow.github.io/mailcow-dockerized-docs/i_u_m_install/ (just takes less than a minute, easy to reproduce) 4. Start mailcow with "dns"-settings specified in docker-compose file (Make sure using the older docker-compose version with dns settings: https://raw.githubusercontent.com/mailcow/mailcow-dockerized/a1403b7a5969637df23001d05c59c2a20774fbb5/docker-compose.yml) 5. Wait a few minutes, then kernel crash appears Using this workaround it appears to be stable again: https://github.com/mailcow/mailcow- dockerized/commit/dc6eea5142c063e26408a685b66fbb7754408ec2 I've attached the apport file to this bug. Please let me know if you need any kind of further information. (As this is my first bug report here, I hope I have included all required information helping you finding the cause.) Kind regards, Patrik To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842447/+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 1842271] Re: Infinite loop in __blkdev_issue_discard() consumes the entire system memory when formatting a raid array
This was released in 4.15.0-59-generic and works as intended. Marking
Fix Released. Note, this still needs to land in linux-gcp for Bionic due
to some technical reasons.
** Changed in: linux (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
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/1842271
Title:
Infinite loop in __blkdev_issue_discard() consumes the entire system
memory when formatting a raid array
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Bionic:
Fix Released
Bug description:
BugLink: https://bugs.launchpad.net/bugs/1842271
[Impact]
There is a regression present in block in 4.15.0-56, which causes the
machine to consume all system memory and cause the OOM reaper to come
out, when attempting to format a newly created raid array on a series
of NVMe cluster with an xfs filesystem.
The symptoms can be found with all system memory ending up in
kmalloc-256 slab, with a nondescript call trace being printed.
The problem is caused by the below two commits:
commit 3c2f83d8bcbedeb89efcaf55ae64a99dce9d7e34
Author: Ming Lei
Date: Fri Oct 12 15:53:10 2018 +0800
Subject: block: don't deal with discard limit in blkdev_issue_discard()
BugLink: https://bugs.launchpad.net/bugs/1836802
Upstream-commit: 744889b7cbb56a64f957e65ade7cb65fe3f35714
Pastebin: https://paste.ubuntu.com/p/WKsmwKgCMc/
commit b515257f186e532e0668f7deabcb04b5d27505cf
Author: Ming Lei
Date: Mon Oct 29 20:57:17 2018 +0800
Subject: block: make sure discard bio is aligned with logical block size
BugLink: https://bugs.launchpad.net/bugs/1836802
Upstream-commit: 1adfc5e4136f5967d591c399aff95b3b035f16b7
Pastebin: https://paste.ubuntu.com/p/TcnTck64PJ/
Now, the fault was triggered in two stages. Firstly, in "block: don't
deal with discard limit in blkdev_issue_discard()" a while loop was
changed such that there is a possibility of an infinite loop if
__blkdev_issue_discard() is called with nr_sects > 0 and req_sects
somehow becomes 0:
int __blkdev_issue_discard(..., sector_t nr_sects, ...)
{
...
while (nr_sects) {
unsigned int req_sects = nr_sects;
sector_t end_sect;
end_sect = sector + req_sects;
...
nr_sects -= req_sects;
sector = end_sect;
...
}
if req_sects is 0, then end_sect is always equal to sector, and the
most important part, nr_sects is only decremented in one place, by
req_sects, which if 0, would lead to the infinite loop condition.
Now, since req_sects is initially equal to nr_sects, the loop would
never be entered in the first place if nr_sects is 0.
This is where the second commit, "block: make sure discard bio is
aligned with logical block size" comes in.
This commit adds a line to the above loop, to allow req_sects to be
set to a new value:
int __blkdev_issue_discard(..., sector_t nr_sects, ...)
{
...
while (nr_sects) {
unsigned int req_sects = nr_sects;
sector_t end_sect;
req_sects = min(req_sects, bio_allowed_max_sectors(q));
end_sect = sector + req_sects;
...
nr_sects -= req_sects;
sector = end_sect;
...
}
We see that req_sects will now be the minimum of itself and
bio_allowed_max_sectors(q), a new function introduced by the same
commit.
static inline unsigned int bio_allowed_max_sectors(struct request_queue *q)
{
return round_down(UINT_MAX, queue_logical_block_size(q)) >> 9;
}
queue_logical_block_size(q) queries the hardware for the logical block
size of the underlying device.
static inline unsigned short queue_logical_block_size(struct request_queue *q)
{
int retval = 512;
if (q && q->limits.logical_block_size)
retval = q->limits.logical_block_size;
return retval;
}
if q->limits.logical_block_size is 512 or smaller, then bit shifted
right by 9 yields 0.
bio_allowed_max_sectors will return 0, and the min with req_sects ==
nr_sects will favour the new 0.
This causes nr_sects to never be decremented since req_sects is 0, and
req_sects will never change since the min() that takes in itself will
always favour the 0.
From there the infinite loop iterates and fills up the kmalloc-256
slab with newly created bio entries, until all memory is exhausted and
the OOM reaper comes out and starts killing processes, which is
ineffective since this is a kernel memory leak.
[Fix]
The fix comes in the form of:
commit a55264933f12c2fdc28a66841c4724021e8c1caf
Author: Mikulas Patocka
Date: Tue Jul 3 13:34:22 2018 -0400
Subject: block: fix infinite loop if the device loses discard capability
BugLink: https://bugs.launchpad.net/bugs/1837257
Upstream-commit: b88aef36b87c9787a4db724923ec4f57dfd513f3
Pastebin: https://paste.ubuntu.com/p/bgC9vQnB8x/
This adds a check right after the
[Kernel-packages] [Bug 1842447] Re: Kernel Panic with linux-image-4.15.0-60-generic when specifying nameserver in docker-compose
I agree with Taher (in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842447/comments/15), this bug seems to impact a lot of systems (my colo host was kernel panic restarting about every 75-90 minutes, all weekend). It has a NAT firewall on it (for the hosted VMs), but no Docker/Wireguard, etc. My guess for the 75-90 minutes is that is how long it took to dirty enough memory that the relevant value just happened not to already be 0 (NULL). (Curiously I installed -60 on Thursday last week, and the first issue didn't happen until Friday, so it's been worse over the weekend than the first 24 hours. I enabled kernel.panic=15 after the first issue, to automate recovery, and was *extremely* glad I did so.) Honestly I'd suggest withdrawing -60 as it's very unstable in a lot of common configurations. And also suggest expediting the release of -62, which AFAICT just contains the one line fix for the bug in -60. Now it's Monday morning (and thus I can get into the colo if needed), I've upgraded the colo system to the proposed -62 version, and crossing my fingers the system is more stable as a result. In case it helps others, I found I needed to: (a) https://wiki.ubuntu.com/Testing/EnableProposed (changing "xenial" to "bionic", for 18.04 LTS, including enabling the low priority pin of bionic-proposed); and (b) sudo apt-get install linux-generic/bionic-proposed linux-signed- generic/bionic-proposed linux-headers-generic/bionic-proposed (without at least two of those three, the proposed update metapackages wouldn't install due to conflicts; I'm not sure if linux-signed-generic is needed, but it's still installed, so I chose to keep it in sync.) That list of packages found by looking for 4.15.0-60 versioned packages that didn't have that version in their package name (ie, to find the generic metapackages). Ewen PS: Reboots (due to kernel panic, and kernel.panic=15 sysctl) over the weekend: -=- cut here -=- ewen@naosr620:~$ last | grep reboot reboot system boot 4.15.0-62-generi Mon Sep 9 10:43 still running reboot system boot 4.15.0-60-generi Mon Sep 9 10:14 - 10:39 (00:25) reboot system boot 4.15.0-60-generi Mon Sep 9 08:48 - 10:09 (01:21) reboot system boot 4.15.0-60-generi Mon Sep 9 07:33 - 10:09 (02:36) reboot system boot 4.15.0-60-generi Mon Sep 9 06:18 - 10:09 (03:51) reboot system boot 4.15.0-60-generi Mon Sep 9 05:03 - 10:09 (05:06) reboot system boot 4.15.0-60-generi Mon Sep 9 03:48 - 10:09 (06:21) reboot system boot 4.15.0-60-generi Mon Sep 9 02:33 - 10:09 (07:36) reboot system boot 4.15.0-60-generi Mon Sep 9 01:13 - 10:09 (08:56) reboot system boot 4.15.0-60-generi Sun Sep 8 23:58 - 10:09 (10:11) reboot system boot 4.15.0-60-generi Sun Sep 8 22:43 - 10:09 (11:26) reboot system boot 4.15.0-60-generi Sun Sep 8 21:28 - 10:09 (12:41) reboot system boot 4.15.0-60-generi Sun Sep 8 20:08 - 10:09 (14:01) reboot system boot 4.15.0-60-generi Sun Sep 8 18:53 - 10:09 (15:16) reboot system boot 4.15.0-60-generi Sun Sep 8 17:38 - 10:09 (16:31) reboot system boot 4.15.0-60-generi Sun Sep 8 16:23 - 10:09 (17:46) reboot system boot 4.15.0-60-generi Sun Sep 8 15:08 - 10:09 (19:01) reboot system boot 4.15.0-60-generi Sun Sep 8 13:53 - 10:09 (20:16) reboot system boot 4.15.0-60-generi Sun Sep 8 12:29 - 10:09 (21:40) reboot system boot 4.15.0-60-generi Sun Sep 8 11:14 - 10:09 (22:55) reboot system boot 4.15.0-60-generi Sun Sep 8 09:57 - 10:09 (1+00:12) reboot system boot 4.15.0-60-generi Sun Sep 8 08:43 - 10:09 (1+01:26) reboot system boot 4.15.0-60-generi Sun Sep 8 07:28 - 10:09 (1+02:41) reboot system boot 4.15.0-60-generi Sun Sep 8 06:13 - 10:09 (1+03:56) reboot system boot 4.15.0-60-generi Sun Sep 8 04:54 - 10:09 (1+05:15) reboot system boot 4.15.0-60-generi Sun Sep 8 03:34 - 10:09 (1+06:35) reboot system boot 4.15.0-60-generi Sun Sep 8 02:18 - 10:09 (1+07:51) reboot system boot 4.15.0-60-generi Sun Sep 8 01:03 - 10:09 (1+09:06) reboot system boot 4.15.0-60-generi Sat Sep 7 23:48 - 10:09 (1+10:21) reboot system boot 4.15.0-60-generi Sat Sep 7 22:55 - 10:09 (1+11:14) reboot system boot 4.15.0-60-generi Sat Sep 7 22:34 - 10:09 (1+11:35) reboot system boot 4.15.0-60-generi Sat Sep 7 21:19 - 10:09 (1+12:50) reboot system boot 4.15.0-60-generi Sat Sep 7 20:03 - 10:09 (1+14:06) reboot system boot 4.15.0-60-generi Sat Sep 7 18:48 - 10:09 (1+15:21) reboot system boot 4.15.0-60-generi Sat Sep 7 17:33 - 10:09 (1+16:36) reboot system boot 4.15.0-60-generi Sat Sep 7 16:18 - 10:09 (1+17:51) reboot system boot 4.15.0-60-generi Sat Sep 7 15:03 - 10:09 (1+19:06) reboot system boot 4.15.0-60-generi Sat Sep 7 13:42 - 10:09 (1+20:27) reboot system boot 4.15.0-60-generi Sat Sep 7 12:27 - 10:09 (1+21:42) reboot system boot 4.15.0-60-generi Sat Sep 7 11:12 - 10:09 (1+22:57) reboot system boot 4.15.0-60-generi Sat Sep 7 10:57 - 10:09 (1+23:12)
[Kernel-packages] [Bug 1842713] Re: bionic/linux-snapdragon: 4.15.0-1062.69 -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: 1842746 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Thursday, 05. September 2019 22:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: - bionic/linux-snapdragon/dragonboard-kernel: bug 1842712, bug 1839978 + bionic/linux-snapdragon/dragonboard-kernel: bug 1839978, bug 1842712 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/1842713 Title: bionic/linux-snapdragon: 4.15.0-1062.69 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress 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 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: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon 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: 1842746 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Thursday, 05. September 2019 22:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1839978, bug 1842712 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842713/+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 1842608] Re: xenial/linux: 4.4.0-162.190 -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 -- packages: main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Wednesday, 04. September 2019 07:52 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa main:failed,meta:depwait trackers: - trusty/linux-aws: bug 1842606, bug 1842793 - trusty/linux-lts-xenial: bug 1842794, bug 1842607 + trusty/linux-aws: bug 1842793, bug 1842606 + trusty/linux-lts-xenial: bug 1842607, bug 1842794 xenial/linux-aws: bug 1842597 xenial/linux-fips: bug 1842605 xenial/linux-kvm: bug 1842598 xenial/linux-raspi2: bug 1842600 xenial/linux-snapdragon: bug 1842603 xenial/linux/pc-kernel: bug 1842595 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/1842608 Title: xenial/linux: 4.4.0-162.190 -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 -- swm properties -- packages: main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Wednesday, 04. September 2019 07:52 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa main:failed,meta:depwait trackers: trusty/linux-aws: bug 1842793, bug 1842606 trusty/linux-lts-xenial: bug 1842607, bug 1842794 xenial/linux-aws: bug 1842597 xenial/linux-fips: bug 1842605 xenial/linux-kvm: bug 1842598 xenial/linux-raspi2: bug 1842600 xenial/linux-snapdragon: bug 1842603 xenial/linux/pc-kernel: bug 1842595 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842608/+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 1654448] Re: Dell XPS 13 9350/9360 headphone audio hiss
Weird. I've had an XPS 9360 running ubuntu since November 2017. Last week I picked up all the updates from August, rebooted and ran straight into this bug with headphones that had previously been fine. I dual boot into Windows and that is fine so it isn't a hardware problem. -- 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/1654448 Title: Dell XPS 13 9350/9360 headphone audio hiss Status in Dell Sputnik: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Confirmed Bug description: Pertaining to 16.04 on a dell XPS 13 9360 ii alsa-base 1.0.25+dfsg-0ubuntu5 Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic. When headphones are plugged in, there is a clearly audible hiss (white noise). This is present as soon as the headphones are plugged in, whether 'headphones' or 'headset' are selected from the pop-up box. Using alsamixer to debug the issue reveals that it is related to "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If this is changed to: 10.00, 10.00 (one notch up) the hiss disappears. 20.00, 20.00 cause a louder hiss and 30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. When the headphones are removed and plugged back in the Headphone Mic Boost setting returns to dB gain 0 and the problem also returns. This (problem and workaround) has been reported in the wild: https://news.ycombinator.com/item?id=13050843 and https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/ for example To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1654448/+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 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04
Same problem. XPS 15 9570, freshly installed Ubuntu 18.04.3. 70-99 degrees while using browser + IDE. Disabling turbo boost keeps it under 80 degrees, but that's not a solution. intel_pstate is enabled, disabling it does not 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/1768976 Title: Ubuntu 18.04 is overheating after upgrade from 16.04 Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: Ubuntu is overheating at my laptop. Opening youtube on firefox is enough for critical temperature shutdown. Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C with only firefox or chrome open and doing nothing. On my old 16.04 with same using, the temp varies between 55 and 70°C. First thought was the driver nouveau is the problem, and finally I was able to install by add "nouveau.modeset=0" at livecd boot options, without temp shutdown. After install I disable the nouveau at modprobe blacklist, but the system continues overheating and shutdown with basic usage. I have no idea what's happening with the bionic at my laptop. My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.17 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu May 3 16:22:40 2018 InstallationDate: Installed on 2018-04-27 (6 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptHistorylog: Start-Date: 2018-04-27 15:46:02 End-Date: 2018-04-27 15:46:02 VarLogDistupgradeAptlog: Log time: 2018-04-27 15:45:39.753331 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done Log time: 2018-04-27 15:46:04.859979 VarLogDistupgradeApttermlog: Log started: 2018-04-27 15:46:02 Log ended: 2018-04-27 15:46:02 --- .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: edir 2354 F pulseaudio CompositorRunning: None DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family Integrated Graphics Controller [144d:c0a5] Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5] HibernationDevice: RESUME=UUID=e7a61aee-64c2-4c88-b4e1-4de481d0f88d InstallationDate: Installed on 2018-04-27 (36 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711 NonfreeKernelModules: wl Package: xserver-xorg-video-nouveau 1:1.0.15-2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=db38a22c-0e9f-4e1a-b9f7-f7aac2544394 ro quiet splash nouveau.runpm=0 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 Tags: bionic ubuntu Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 10HX.M034.20110426.SSH dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: RF511/RF411/RF711 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: 10HX dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias:
[Kernel-packages] [Bug 1842587] Re: xenial/linux-azure: 4.15.0-1057.62 -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: 1842828 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Testing phase-changed: Friday, 06. September 2019 05:48 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: - trusty/linux-azure: bug 1842819, bug 1842585 + trusty/linux-azure: bug 1842585, bug 1842819 xenial/linux-azure-edge: bug 1842584 xenial/linux-azure/azure-kernel: bug 1842583 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1842587 Title: xenial/linux-azure: 4.15.0-1057.62 -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 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: Confirmed Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure 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: 1842828 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Testing phase-changed: Friday, 06. September 2019 05:48 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1842585, bug 1842819 xenial/linux-azure-edge: bug 1842584 xenial/linux-azure/azure-kernel: bug 1842583 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842587/+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 1842713] Re: bionic/linux-snapdragon: 4.15.0-1062.69 -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: 1842746 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Thursday, 05. September 2019 22:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: - bionic/linux-snapdragon/dragonboard-kernel: bug 1839978, bug 1842712 + bionic/linux-snapdragon/dragonboard-kernel: bug 1842712, bug 1839978 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/1842713 Title: bionic/linux-snapdragon: 4.15.0-1062.69 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress 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 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: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon 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: 1842746 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Thursday, 05. September 2019 22:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1842712, bug 1839978 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842713/+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 1842608] Re: xenial/linux: 4.4.0-162.190 -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 -- packages: main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Wednesday, 04. September 2019 07:52 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa main:failed,meta:depwait trackers: - trusty/linux-aws: bug 1842793, bug 1842606 + trusty/linux-aws: bug 1842606, bug 1842793 trusty/linux-lts-xenial: bug 1842794, bug 1842607 xenial/linux-aws: bug 1842597 xenial/linux-fips: bug 1842605 xenial/linux-kvm: bug 1842598 xenial/linux-raspi2: bug 1842600 xenial/linux-snapdragon: bug 1842603 xenial/linux/pc-kernel: bug 1842595 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/1842608 Title: xenial/linux: 4.4.0-162.190 -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 -- swm properties -- packages: main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Wednesday, 04. September 2019 07:52 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa main:failed,meta:depwait trackers: trusty/linux-aws: bug 1842606, bug 1842793 trusty/linux-lts-xenial: bug 1842794, bug 1842607 xenial/linux-aws: bug 1842597 xenial/linux-fips: bug 1842605 xenial/linux-kvm: bug 1842598 xenial/linux-raspi2: bug 1842600 xenial/linux-snapdragon: bug 1842603 xenial/linux/pc-kernel: bug 1842595 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842608/+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 1842447] Re: Kernel Panic with linux-image-4.15.0-60-generic when specifying nameserver in docker-compose
This bug has to be dealt with a higher degree of urgency. It impacts any machine that performs any type of NAT. Is not application specific though. -- 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/1842447 Title: Kernel Panic with linux-image-4.15.0-60-generic when specifying nameserver in docker-compose Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] Some fragmentation+NAT workloads will cause kernel BUG/Ooops. [Test case] sudo iptables -t nat -I POSTROUTING -j MASQUERADE sudo hping3 192.168.122.1 -s 1000 -p 2000 -d 6 [Regression potential] This could make fragmented packets stop flowing. So, make sure fragmented pings still work. ping 192.168.122.1 -s 6 still works, even with the above nat rule. Hello, there are multiple inquries in the mailcow GitHub issues over at https://github.com/mailcow/mailcow-dockerized/issues/2904 that the latest kernel linux-image-4.15.0-60-generic causes kernel panics when "- dns" setting is used within the docker-compose.yml file, for yet some unclear reasons. Multiple users on different systems (e.g. virtualized ones on VMware ESXi and KVM) were able to reproduce the same issue. I was also able to reproduce this constantly on a completely new deployed Ubuntu 18.04 VM (KVM) with a fresh mailcow installation. Steps to reproduce: 1. Install a clean Ubuntu 18.04(.03) machine 2. Upgrade the installation to linux-image-4.15.0-60-generic 3. Setup mailcow as instructed at https://mailcow.github.io/mailcow-dockerized-docs/i_u_m_install/ (just takes less than a minute, easy to reproduce) 4. Start mailcow with "dns"-settings specified in docker-compose file (Make sure using the older docker-compose version with dns settings: https://raw.githubusercontent.com/mailcow/mailcow-dockerized/a1403b7a5969637df23001d05c59c2a20774fbb5/docker-compose.yml) 5. Wait a few minutes, then kernel crash appears Using this workaround it appears to be stable again: https://github.com/mailcow/mailcow- dockerized/commit/dc6eea5142c063e26408a685b66fbb7754408ec2 I've attached the apport file to this bug. Please let me know if you need any kind of further information. (As this is my first bug report here, I hope I have included all required information helping you finding the cause.) Kind regards, Patrik To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842447/+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 1842561] Re: disco/linux: 5.0.0-28.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 -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Friday, 06. September 2019 13:02 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe: bug 1842847 bionic/linux-oem-osp1: bug 1842848 disco/linux-aws: bug 1842542 disco/linux-azure: bug 1842546 disco/linux-gcp: bug 1842553 disco/linux-kvm: bug 1842554 disco/linux-oracle: bug 1842556 disco/linux-raspi2: bug 1842540 disco/linux-snapdragon: bug 1842557 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/1842561 Title: disco/linux: 5.0.0-28.30 -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-lrm 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: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: 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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Friday, 06. September 2019 13:02 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe: bug 1842847 bionic/linux-oem-osp1: bug 1842848 disco/linux-aws: bug 1842542 disco/linux-azure: bug 1842546 disco/linux-gcp: bug 1842553 disco/linux-kvm: bug 1842554 disco/linux-oracle: bug 1842556 disco/linux-raspi2: bug 1842540 disco/linux-snapdragon: bug 1842557 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842561/+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 1811730] Re: Thermald does not set max CPU after reseting the voltage using RAPL
Alex, 18.10 is EOL as of the end of July so no fix is planned -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1811730 Title: Thermald does not set max CPU after reseting the voltage using RAPL Status in thermald package in Ubuntu: Confirmed Status in thermald source package in Bionic: Fix Committed Bug description: Hi, I was using Ubuntu 18.10 thermald package, but I noted that, after few seconds at max CPU usage (max temp), thermald send the signal to RALP to reduce the voltage of the CPU. It set the freq to minimum (800MHz in my case). But when the CPU is idle and temp is lowered (35-40ºC) it did not send the signal to resume normal operation of the CPU. I compiled the latest version of thermald from git (https://github.com/intel/thermal_daemon) and now everything works fine. I started to thought that the problem was the hardware or BIOS problem, as I disabled the CPU scaling on the BIOS, but intel_pstate continued doing freq scaling (I think for Turbo mode). But the real problem was Thermald. The latest version from git works really fine and it automatically disables and enable the Intel Turbo state and balance the freqs and fan control fine. My hardware is a Lenovo Thinkpad P52 with i7-8850H. I tested it using Ubuntu kernel and Kernel 4.20 optimized for i7 processor but with Ubuntu default config (except processor family="Core2/newer Xeon", Preemption Model="Preemptible Kernel (Low- Latency Desktop)" and Timer frequency="1000HZ". (Only changed those settings from make oldconfig and make deb-pkg). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: thermald (not installed) ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 14 23:45:01 2019 InstallationDate: Installed on 2018-12-11 (34 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: thermald UpgradeStatus: No upgrade log present (probably fresh install) - SRU Justification == [Impact] * As described by the original bug reporter, CPU usage of Lenovo P52 is sub-optimal under heavy load. * My observation is the machine exhibits a sharp drop of power usage and CPU frequency and takes time to slowly ramp up again (refer to the chart at https://bit.ly/2OJphB8) * Fixed by bisecting and backporting fixes from thermald project. [Test Case] * One can stress the CPU load of the machine and collect the CPU frequency and power usage over time to check for any anamoly. The script at https://people.canonical.com/~ypwong/p52_test_cpu.sh can help with this. * With the fix, the behaviour should be like this: https://bit.ly/2KA9EXB, a consistent power usage can be maintained. [Regression Potential] * Medium. The fix consists of 7 commits cherry-picked from upstream, these changes will affect any machines using RAPL cooling device. The impact may not be obvious in normal daily usage but will be manifested during heavy load, suggest a longer verification period so that more people can discover any adverse effect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1811730/+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 1842587] Re: xenial/linux-azure: 4.15.0-1057.62 -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: 1842828 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Testing phase-changed: Friday, 06. September 2019 05:48 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: - trusty/linux-azure: bug 1842585, bug 1842819 + trusty/linux-azure: bug 1842819, bug 1842585 xenial/linux-azure-edge: bug 1842584 xenial/linux-azure/azure-kernel: bug 1842583 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1842587 Title: xenial/linux-azure: 4.15.0-1057.62 -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 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: Confirmed Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure 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: 1842828 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Testing phase-changed: Friday, 06. September 2019 05:48 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1842819, bug 1842585 xenial/linux-azure-edge: bug 1842584 xenial/linux-azure/azure-kernel: bug 1842583 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842587/+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 1842608] Re: xenial/linux: 4.4.0-162.190 -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 -- packages: main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Wednesday, 04. September 2019 07:52 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa main:failed,meta:depwait trackers: - trusty/linux-aws: bug 1842606, bug 1842793 - trusty/linux-lts-xenial: bug 1842607, bug 1842794 + trusty/linux-aws: bug 1842793, bug 1842606 + trusty/linux-lts-xenial: bug 1842794, bug 1842607 xenial/linux-aws: bug 1842597 xenial/linux-fips: bug 1842605 xenial/linux-kvm: bug 1842598 xenial/linux-raspi2: bug 1842600 xenial/linux-snapdragon: bug 1842603 xenial/linux/pc-kernel: bug 1842595 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/1842608 Title: xenial/linux: 4.4.0-162.190 -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 -- swm properties -- packages: main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Wednesday, 04. September 2019 07:52 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa main:failed,meta:depwait trackers: trusty/linux-aws: bug 1842793, bug 1842606 trusty/linux-lts-xenial: bug 1842794, bug 1842607 xenial/linux-aws: bug 1842597 xenial/linux-fips: bug 1842605 xenial/linux-kvm: bug 1842598 xenial/linux-raspi2: bug 1842600 xenial/linux-snapdragon: bug 1842603 xenial/linux/pc-kernel: bug 1842595 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842608/+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 1842713] Re: bionic/linux-snapdragon: 4.15.0-1062.69 -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: 1842746 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Thursday, 05. September 2019 22:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: - bionic/linux-snapdragon/dragonboard-kernel: bug 1842712, bug 1839978 + bionic/linux-snapdragon/dragonboard-kernel: bug 1839978, bug 1842712 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/1842713 Title: bionic/linux-snapdragon: 4.15.0-1062.69 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress 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 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: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon 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: 1842746 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Thursday, 05. September 2019 22:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1839978, bug 1842712 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842713/+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 1842447] Re: Kernel Panic with linux-image-4.15.0-60-generic when specifying nameserver in docker-compose
** Changed in: linux (Ubuntu Bionic) Status: Fix Released => 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/1842447 Title: Kernel Panic with linux-image-4.15.0-60-generic when specifying nameserver in docker-compose Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] Some fragmentation+NAT workloads will cause kernel BUG/Ooops. [Test case] sudo iptables -t nat -I POSTROUTING -j MASQUERADE sudo hping3 192.168.122.1 -s 1000 -p 2000 -d 6 [Regression potential] This could make fragmented packets stop flowing. So, make sure fragmented pings still work. ping 192.168.122.1 -s 6 still works, even with the above nat rule. Hello, there are multiple inquries in the mailcow GitHub issues over at https://github.com/mailcow/mailcow-dockerized/issues/2904 that the latest kernel linux-image-4.15.0-60-generic causes kernel panics when "- dns" setting is used within the docker-compose.yml file, for yet some unclear reasons. Multiple users on different systems (e.g. virtualized ones on VMware ESXi and KVM) were able to reproduce the same issue. I was also able to reproduce this constantly on a completely new deployed Ubuntu 18.04 VM (KVM) with a fresh mailcow installation. Steps to reproduce: 1. Install a clean Ubuntu 18.04(.03) machine 2. Upgrade the installation to linux-image-4.15.0-60-generic 3. Setup mailcow as instructed at https://mailcow.github.io/mailcow-dockerized-docs/i_u_m_install/ (just takes less than a minute, easy to reproduce) 4. Start mailcow with "dns"-settings specified in docker-compose file (Make sure using the older docker-compose version with dns settings: https://raw.githubusercontent.com/mailcow/mailcow-dockerized/a1403b7a5969637df23001d05c59c2a20774fbb5/docker-compose.yml) 5. Wait a few minutes, then kernel crash appears Using this workaround it appears to be stable again: https://github.com/mailcow/mailcow- dockerized/commit/dc6eea5142c063e26408a685b66fbb7754408ec2 I've attached the apport file to this bug. Please let me know if you need any kind of further information. (As this is my first bug report here, I hope I have included all required information helping you finding the cause.) Kind regards, Patrik To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842447/+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 1840484] Re: linux-oem 4.15 can not suspend to idle XPS-13-9380
I just found that s2i back to work after I removed multipass snap package. BTW, the multipass version is multipass (beta) 0.8.0. This issue looks not impact users who not installed multipass, so I'll lower the priority. ** Changed in: oem-priority Importance: Critical => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem in Ubuntu. https://bugs.launchpad.net/bugs/1840484 Title: linux-oem 4.15 can not suspend to idle XPS-13-9380 Status in OEM Priority Project: New Status in linux-signed-oem package in Ubuntu: New Bug description: it somehow s2i failed, from message , it seems the s2i process be blocked by thunderbolt device. dmesg: [193139.391652] pciehp :04:04.0:pcie204: pcie_do_write_cmd: no response from device [193139.391703] pciehp :04:01.0:pcie204: pcie_do_write_cmd: no response from device [193141.012736] PM: noirq suspend of devices failed [193141.772467] ath10k_pci :02:00.0: Unknown eventid: 118809 [193141.775359] ath10k_pci :02:00.0: Unknown eventid: 90118 [193141.872317] thunderbolt :05:00.0: control channel starting... Not sure is it relative that I hot plug out WD19 docking before suspend. reproduce rate: random ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1045-oem 4.15.0-1045.50 ProcVersionSignature: Ubuntu 4.15.0-1045.50-oem 4.15.18 Uname: Linux 4.15.0-1045-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 17 00:02:08 2019 InstallationDate: Installed on 2019-08-11 (5 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed-oem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1840484/+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 1842447] Re: Kernel Panic with linux-image-4.15.0-60-generic when specifying nameserver in docker-compose
The last status change happened on accident. The fix has not been released, yet. I cannot change the status back to "Fix Committed" though. Can anyone help with this? -- 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/1842447 Title: Kernel Panic with linux-image-4.15.0-60-generic when specifying nameserver in docker-compose Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Released Bug description: [Impact] Some fragmentation+NAT workloads will cause kernel BUG/Ooops. [Test case] sudo iptables -t nat -I POSTROUTING -j MASQUERADE sudo hping3 192.168.122.1 -s 1000 -p 2000 -d 6 [Regression potential] This could make fragmented packets stop flowing. So, make sure fragmented pings still work. ping 192.168.122.1 -s 6 still works, even with the above nat rule. Hello, there are multiple inquries in the mailcow GitHub issues over at https://github.com/mailcow/mailcow-dockerized/issues/2904 that the latest kernel linux-image-4.15.0-60-generic causes kernel panics when "- dns" setting is used within the docker-compose.yml file, for yet some unclear reasons. Multiple users on different systems (e.g. virtualized ones on VMware ESXi and KVM) were able to reproduce the same issue. I was also able to reproduce this constantly on a completely new deployed Ubuntu 18.04 VM (KVM) with a fresh mailcow installation. Steps to reproduce: 1. Install a clean Ubuntu 18.04(.03) machine 2. Upgrade the installation to linux-image-4.15.0-60-generic 3. Setup mailcow as instructed at https://mailcow.github.io/mailcow-dockerized-docs/i_u_m_install/ (just takes less than a minute, easy to reproduce) 4. Start mailcow with "dns"-settings specified in docker-compose file (Make sure using the older docker-compose version with dns settings: https://raw.githubusercontent.com/mailcow/mailcow-dockerized/a1403b7a5969637df23001d05c59c2a20774fbb5/docker-compose.yml) 5. Wait a few minutes, then kernel crash appears Using this workaround it appears to be stable again: https://github.com/mailcow/mailcow- dockerized/commit/dc6eea5142c063e26408a685b66fbb7754408ec2 I've attached the apport file to this bug. Please let me know if you need any kind of further information. (As this is my first bug report here, I hope I have included all required information helping you finding the cause.) Kind regards, Patrik To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842447/+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 1842447] Re: Kernel Panic with linux-image-4.15.0-60-generic when specifying nameserver in docker-compose
** Changed in: linux (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1842447 Title: Kernel Panic with linux-image-4.15.0-60-generic when specifying nameserver in docker-compose Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Released Bug description: [Impact] Some fragmentation+NAT workloads will cause kernel BUG/Ooops. [Test case] sudo iptables -t nat -I POSTROUTING -j MASQUERADE sudo hping3 192.168.122.1 -s 1000 -p 2000 -d 6 [Regression potential] This could make fragmented packets stop flowing. So, make sure fragmented pings still work. ping 192.168.122.1 -s 6 still works, even with the above nat rule. Hello, there are multiple inquries in the mailcow GitHub issues over at https://github.com/mailcow/mailcow-dockerized/issues/2904 that the latest kernel linux-image-4.15.0-60-generic causes kernel panics when "- dns" setting is used within the docker-compose.yml file, for yet some unclear reasons. Multiple users on different systems (e.g. virtualized ones on VMware ESXi and KVM) were able to reproduce the same issue. I was also able to reproduce this constantly on a completely new deployed Ubuntu 18.04 VM (KVM) with a fresh mailcow installation. Steps to reproduce: 1. Install a clean Ubuntu 18.04(.03) machine 2. Upgrade the installation to linux-image-4.15.0-60-generic 3. Setup mailcow as instructed at https://mailcow.github.io/mailcow-dockerized-docs/i_u_m_install/ (just takes less than a minute, easy to reproduce) 4. Start mailcow with "dns"-settings specified in docker-compose file (Make sure using the older docker-compose version with dns settings: https://raw.githubusercontent.com/mailcow/mailcow-dockerized/a1403b7a5969637df23001d05c59c2a20774fbb5/docker-compose.yml) 5. Wait a few minutes, then kernel crash appears Using this workaround it appears to be stable again: https://github.com/mailcow/mailcow- dockerized/commit/dc6eea5142c063e26408a685b66fbb7754408ec2 I've attached the apport file to this bug. Please let me know if you need any kind of further information. (As this is my first bug report here, I hope I have included all required information helping you finding the cause.) Kind regards, Patrik To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842447/+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 1843152] Re: Kernel Panic with linux kernel 4.15.0-60 possibly related to network subsystem
kernel log ** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1843152/+attachment/5287296/+files/kern.log ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1843152 Title: Kernel Panic with linux kernel 4.15.0-60 possibly related to network subsystem Status in linux package in Ubuntu: Confirmed Bug description: 1. Releases: Ubuntu Server 16.04 and Ubuntu Server 18.04 2. Package: Linux Kernel 4.15.0-60 amd64 3. What I expected to happen: Not a recurrent kernel panic. 4. What happened instead: Recurrent kernel panic. While running Ubuntu 16.04 server on an internet appliance that was serving as my router, after the system was updated from kernel 4.15.0-58 to 4.15.0-60, I began getting frequent kernel panics (system seldom remained up for more than an hour after a reboot). I have included example stack traces below. After memtest revealed no problems, and fsck revealed no problems, I opted to rebuild from a fresh install, this time of Ubuntu 18.04, server. Upon completing the rebuilt, and put it back in service. It crashed with the same kernel panic within 30 minutes. I have since updated to kernel 5.0.0-27 and the kernel panics have completely stopped. [10170.296117] kernel BUG at /build/linux-5mCauq/linux-4.15.0/net/ipv4/ip_output.c:636! [10170.304214] invalid opcode: [#1] SMP PTI [10170.308692] Modules linked in: st lp parport_pc ppdev parport ipt_REJECT nf_reject_ipv4 xt_condition(OE) xt_time xt_comment xt_iface(OE) xt_multiport xt_conntrack xt_set xt_recent xt_hashlimit xt_addrtype xt_mark iptable_mangle xt_nat xt_REDIRECT nf_nat_redirect ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_iprange iptable_nat nf_nat_ipv4 nf_conntrack_ipv4 nf_defrag_ipv4 xt_tcpudp xt_CT iptable_raw ip_set_list_set ip_set_hash_ip ip_set_hash_net ip_set_hash_mac ip_set xt_NFLOG nfnetlink_log nf_log_ipv4 nf_log_common xt_LOG nf_conntrack_sane nf_conntrack_netlink nfnetlink nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda nf_nat nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_netbios_ns [10170.381810] nf_conntrack_broadcast nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp ts_kmp nf_conntrack_amanda nf_conntrack iptable_filter bridge intel_rapl intel_soc_dts_thermal intel_soc_dts_iosf intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm irqbypass punit_atom_debug intel_cstate snd_hda_intel snd_hda_codec snd_hda_core joydev snd_hwdep snd_pcm snd_timer serio_raw input_leds snd lpc_ich soundcore shpchp mac_hid mei_txe mei sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 8021q garp mrp stp llc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear i915 crct10dif_pclmul crc32_pclmul i2c_algo_bit drm_kms_helper [10170.454089] ghash_clmulni_intel e1000e syscopyarea sysfillrect sysimgblt fb_sys_fops ptp ahci psmouse cryptd drm pps_core libahci video hid_generic usbhid hid [last unloaded: parport_pc] [10170.471175] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G OE 4.15.0-60-generic #67-Ubuntu [10170.480269] Hardware name: Protectli FW1/FW1, BIOS 5.6.5 05/14/2019 [10170.486704] RIP: 0010:ip_do_fragment+0x482/0x820 [10170.491462] RSP: 0018:92533fc83a18 EFLAGS: 00010202 [10170.496824] RAX: 0001 RBX: 92532b43ed00 RCX: 8d64cdf0 [10170.504158] RDX: 0024 RSI: 05c8 RDI: 925329f06300 [10170.511485] RBP: 92533fc83a80 R08: 925330be9700 R09: 05dc [10170.518777] R10: R11: 92533fc839d0 R12: 0014 [10170.526096] R13: 92532dea4300 R14: 2328 R15: 925330be974e [10170.533430] FS: () GS:92533fc8() knlGS: [10170.541729] CS: 0010 DS: ES: CR0: 80050033 [10170.547631] CR2: 7f3a9dd13b80 CR3: 9640a000 CR4: 001006e0 [10170.554957] Call Trace: [10170.557452] [10170.559541] ? ip_copy_metadata+0x220/0x220 [10170.563849] ip_fragment.constprop.45+0x43/0x80 [10170.568499] ip_finish_output+0x182/0x270 [10170.572604] ? nf_hook_slow+0x48/0xc0 [10170.576354] ip_output+0x70/0xe0 [10170.579664] ? ip_fragment.constprop.45+0x80/0x80 [10170.584496] ip_forward_finish+0x51/0x80 [10170.588540] ip_forward+0x376/0x470 [10170.592108] ? ip4_key_hashfn+0xc0/0xc0 [10170.596056] ip_rcv_finish+0x129/0x430 [10170.599911] ip_rcv+0x296/0x360 [10170.603125] ? inet_del_offload+0x40/0x40 [10170.607242]
[Kernel-packages] [Bug 1843152] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1843152/+attachment/5287295/+files/WifiSyslog.txt -- 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/1843152 Title: Kernel Panic with linux kernel 4.15.0-60 possibly related to network subsystem Status in linux package in Ubuntu: Confirmed Bug description: 1. Releases: Ubuntu Server 16.04 and Ubuntu Server 18.04 2. Package: Linux Kernel 4.15.0-60 amd64 3. What I expected to happen: Not a recurrent kernel panic. 4. What happened instead: Recurrent kernel panic. While running Ubuntu 16.04 server on an internet appliance that was serving as my router, after the system was updated from kernel 4.15.0-58 to 4.15.0-60, I began getting frequent kernel panics (system seldom remained up for more than an hour after a reboot). I have included example stack traces below. After memtest revealed no problems, and fsck revealed no problems, I opted to rebuild from a fresh install, this time of Ubuntu 18.04, server. Upon completing the rebuilt, and put it back in service. It crashed with the same kernel panic within 30 minutes. I have since updated to kernel 5.0.0-27 and the kernel panics have completely stopped. [10170.296117] kernel BUG at /build/linux-5mCauq/linux-4.15.0/net/ipv4/ip_output.c:636! [10170.304214] invalid opcode: [#1] SMP PTI [10170.308692] Modules linked in: st lp parport_pc ppdev parport ipt_REJECT nf_reject_ipv4 xt_condition(OE) xt_time xt_comment xt_iface(OE) xt_multiport xt_conntrack xt_set xt_recent xt_hashlimit xt_addrtype xt_mark iptable_mangle xt_nat xt_REDIRECT nf_nat_redirect ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_iprange iptable_nat nf_nat_ipv4 nf_conntrack_ipv4 nf_defrag_ipv4 xt_tcpudp xt_CT iptable_raw ip_set_list_set ip_set_hash_ip ip_set_hash_net ip_set_hash_mac ip_set xt_NFLOG nfnetlink_log nf_log_ipv4 nf_log_common xt_LOG nf_conntrack_sane nf_conntrack_netlink nfnetlink nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda nf_nat nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_netbios_ns [10170.381810] nf_conntrack_broadcast nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp ts_kmp nf_conntrack_amanda nf_conntrack iptable_filter bridge intel_rapl intel_soc_dts_thermal intel_soc_dts_iosf intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm irqbypass punit_atom_debug intel_cstate snd_hda_intel snd_hda_codec snd_hda_core joydev snd_hwdep snd_pcm snd_timer serio_raw input_leds snd lpc_ich soundcore shpchp mac_hid mei_txe mei sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 8021q garp mrp stp llc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear i915 crct10dif_pclmul crc32_pclmul i2c_algo_bit drm_kms_helper [10170.454089] ghash_clmulni_intel e1000e syscopyarea sysfillrect sysimgblt fb_sys_fops ptp ahci psmouse cryptd drm pps_core libahci video hid_generic usbhid hid [last unloaded: parport_pc] [10170.471175] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G OE 4.15.0-60-generic #67-Ubuntu [10170.480269] Hardware name: Protectli FW1/FW1, BIOS 5.6.5 05/14/2019 [10170.486704] RIP: 0010:ip_do_fragment+0x482/0x820 [10170.491462] RSP: 0018:92533fc83a18 EFLAGS: 00010202 [10170.496824] RAX: 0001 RBX: 92532b43ed00 RCX: 8d64cdf0 [10170.504158] RDX: 0024 RSI: 05c8 RDI: 925329f06300 [10170.511485] RBP: 92533fc83a80 R08: 925330be9700 R09: 05dc [10170.518777] R10: R11: 92533fc839d0 R12: 0014 [10170.526096] R13: 92532dea4300 R14: 2328 R15: 925330be974e [10170.533430] FS: () GS:92533fc8() knlGS: [10170.541729] CS: 0010 DS: ES: CR0: 80050033 [10170.547631] CR2: 7f3a9dd13b80 CR3: 9640a000 CR4: 001006e0 [10170.554957] Call Trace: [10170.557452] [10170.559541] ? ip_copy_metadata+0x220/0x220 [10170.563849] ip_fragment.constprop.45+0x43/0x80 [10170.568499] ip_finish_output+0x182/0x270 [10170.572604] ? nf_hook_slow+0x48/0xc0 [10170.576354] ip_output+0x70/0xe0 [10170.579664] ? ip_fragment.constprop.45+0x80/0x80 [10170.584496] ip_forward_finish+0x51/0x80 [10170.588540] ip_forward+0x376/0x470 [10170.592108] ? ip4_key_hashfn+0xc0/0xc0 [10170.596056] ip_rcv_finish+0x129/0x430 [10170.599911] ip_rcv+0x296/0x360 [10170.603125] ? inet_del_offload+0x40/0x40 [10170.607242] __netif_receive_skb_core+0x432/0xb80 [10170.612070] ? __slab_free+0x14d/0x2c0
[Kernel-packages] [Bug 1843152] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1843152/+attachment/5287293/+files/ProcModules.txt -- 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/1843152 Title: Kernel Panic with linux kernel 4.15.0-60 possibly related to network subsystem Status in linux package in Ubuntu: Confirmed Bug description: 1. Releases: Ubuntu Server 16.04 and Ubuntu Server 18.04 2. Package: Linux Kernel 4.15.0-60 amd64 3. What I expected to happen: Not a recurrent kernel panic. 4. What happened instead: Recurrent kernel panic. While running Ubuntu 16.04 server on an internet appliance that was serving as my router, after the system was updated from kernel 4.15.0-58 to 4.15.0-60, I began getting frequent kernel panics (system seldom remained up for more than an hour after a reboot). I have included example stack traces below. After memtest revealed no problems, and fsck revealed no problems, I opted to rebuild from a fresh install, this time of Ubuntu 18.04, server. Upon completing the rebuilt, and put it back in service. It crashed with the same kernel panic within 30 minutes. I have since updated to kernel 5.0.0-27 and the kernel panics have completely stopped. [10170.296117] kernel BUG at /build/linux-5mCauq/linux-4.15.0/net/ipv4/ip_output.c:636! [10170.304214] invalid opcode: [#1] SMP PTI [10170.308692] Modules linked in: st lp parport_pc ppdev parport ipt_REJECT nf_reject_ipv4 xt_condition(OE) xt_time xt_comment xt_iface(OE) xt_multiport xt_conntrack xt_set xt_recent xt_hashlimit xt_addrtype xt_mark iptable_mangle xt_nat xt_REDIRECT nf_nat_redirect ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_iprange iptable_nat nf_nat_ipv4 nf_conntrack_ipv4 nf_defrag_ipv4 xt_tcpudp xt_CT iptable_raw ip_set_list_set ip_set_hash_ip ip_set_hash_net ip_set_hash_mac ip_set xt_NFLOG nfnetlink_log nf_log_ipv4 nf_log_common xt_LOG nf_conntrack_sane nf_conntrack_netlink nfnetlink nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda nf_nat nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_netbios_ns [10170.381810] nf_conntrack_broadcast nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp ts_kmp nf_conntrack_amanda nf_conntrack iptable_filter bridge intel_rapl intel_soc_dts_thermal intel_soc_dts_iosf intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm irqbypass punit_atom_debug intel_cstate snd_hda_intel snd_hda_codec snd_hda_core joydev snd_hwdep snd_pcm snd_timer serio_raw input_leds snd lpc_ich soundcore shpchp mac_hid mei_txe mei sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 8021q garp mrp stp llc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear i915 crct10dif_pclmul crc32_pclmul i2c_algo_bit drm_kms_helper [10170.454089] ghash_clmulni_intel e1000e syscopyarea sysfillrect sysimgblt fb_sys_fops ptp ahci psmouse cryptd drm pps_core libahci video hid_generic usbhid hid [last unloaded: parport_pc] [10170.471175] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G OE 4.15.0-60-generic #67-Ubuntu [10170.480269] Hardware name: Protectli FW1/FW1, BIOS 5.6.5 05/14/2019 [10170.486704] RIP: 0010:ip_do_fragment+0x482/0x820 [10170.491462] RSP: 0018:92533fc83a18 EFLAGS: 00010202 [10170.496824] RAX: 0001 RBX: 92532b43ed00 RCX: 8d64cdf0 [10170.504158] RDX: 0024 RSI: 05c8 RDI: 925329f06300 [10170.511485] RBP: 92533fc83a80 R08: 925330be9700 R09: 05dc [10170.518777] R10: R11: 92533fc839d0 R12: 0014 [10170.526096] R13: 92532dea4300 R14: 2328 R15: 925330be974e [10170.533430] FS: () GS:92533fc8() knlGS: [10170.541729] CS: 0010 DS: ES: CR0: 80050033 [10170.547631] CR2: 7f3a9dd13b80 CR3: 9640a000 CR4: 001006e0 [10170.554957] Call Trace: [10170.557452] [10170.559541] ? ip_copy_metadata+0x220/0x220 [10170.563849] ip_fragment.constprop.45+0x43/0x80 [10170.568499] ip_finish_output+0x182/0x270 [10170.572604] ? nf_hook_slow+0x48/0xc0 [10170.576354] ip_output+0x70/0xe0 [10170.579664] ? ip_fragment.constprop.45+0x80/0x80 [10170.584496] ip_forward_finish+0x51/0x80 [10170.588540] ip_forward+0x376/0x470 [10170.592108] ? ip4_key_hashfn+0xc0/0xc0 [10170.596056] ip_rcv_finish+0x129/0x430 [10170.599911] ip_rcv+0x296/0x360 [10170.603125] ? inet_del_offload+0x40/0x40 [10170.607242] __netif_receive_skb_core+0x432/0xb80 [10170.612070] ? __slab_free+0x14d/0x2c0
[Kernel-packages] [Bug 1843152] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1843152/+attachment/5287294/+files/UdevDb.txt -- 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/1843152 Title: Kernel Panic with linux kernel 4.15.0-60 possibly related to network subsystem Status in linux package in Ubuntu: Confirmed Bug description: 1. Releases: Ubuntu Server 16.04 and Ubuntu Server 18.04 2. Package: Linux Kernel 4.15.0-60 amd64 3. What I expected to happen: Not a recurrent kernel panic. 4. What happened instead: Recurrent kernel panic. While running Ubuntu 16.04 server on an internet appliance that was serving as my router, after the system was updated from kernel 4.15.0-58 to 4.15.0-60, I began getting frequent kernel panics (system seldom remained up for more than an hour after a reboot). I have included example stack traces below. After memtest revealed no problems, and fsck revealed no problems, I opted to rebuild from a fresh install, this time of Ubuntu 18.04, server. Upon completing the rebuilt, and put it back in service. It crashed with the same kernel panic within 30 minutes. I have since updated to kernel 5.0.0-27 and the kernel panics have completely stopped. [10170.296117] kernel BUG at /build/linux-5mCauq/linux-4.15.0/net/ipv4/ip_output.c:636! [10170.304214] invalid opcode: [#1] SMP PTI [10170.308692] Modules linked in: st lp parport_pc ppdev parport ipt_REJECT nf_reject_ipv4 xt_condition(OE) xt_time xt_comment xt_iface(OE) xt_multiport xt_conntrack xt_set xt_recent xt_hashlimit xt_addrtype xt_mark iptable_mangle xt_nat xt_REDIRECT nf_nat_redirect ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_iprange iptable_nat nf_nat_ipv4 nf_conntrack_ipv4 nf_defrag_ipv4 xt_tcpudp xt_CT iptable_raw ip_set_list_set ip_set_hash_ip ip_set_hash_net ip_set_hash_mac ip_set xt_NFLOG nfnetlink_log nf_log_ipv4 nf_log_common xt_LOG nf_conntrack_sane nf_conntrack_netlink nfnetlink nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda nf_nat nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_netbios_ns [10170.381810] nf_conntrack_broadcast nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp ts_kmp nf_conntrack_amanda nf_conntrack iptable_filter bridge intel_rapl intel_soc_dts_thermal intel_soc_dts_iosf intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm irqbypass punit_atom_debug intel_cstate snd_hda_intel snd_hda_codec snd_hda_core joydev snd_hwdep snd_pcm snd_timer serio_raw input_leds snd lpc_ich soundcore shpchp mac_hid mei_txe mei sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 8021q garp mrp stp llc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear i915 crct10dif_pclmul crc32_pclmul i2c_algo_bit drm_kms_helper [10170.454089] ghash_clmulni_intel e1000e syscopyarea sysfillrect sysimgblt fb_sys_fops ptp ahci psmouse cryptd drm pps_core libahci video hid_generic usbhid hid [last unloaded: parport_pc] [10170.471175] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G OE 4.15.0-60-generic #67-Ubuntu [10170.480269] Hardware name: Protectli FW1/FW1, BIOS 5.6.5 05/14/2019 [10170.486704] RIP: 0010:ip_do_fragment+0x482/0x820 [10170.491462] RSP: 0018:92533fc83a18 EFLAGS: 00010202 [10170.496824] RAX: 0001 RBX: 92532b43ed00 RCX: 8d64cdf0 [10170.504158] RDX: 0024 RSI: 05c8 RDI: 925329f06300 [10170.511485] RBP: 92533fc83a80 R08: 925330be9700 R09: 05dc [10170.518777] R10: R11: 92533fc839d0 R12: 0014 [10170.526096] R13: 92532dea4300 R14: 2328 R15: 925330be974e [10170.533430] FS: () GS:92533fc8() knlGS: [10170.541729] CS: 0010 DS: ES: CR0: 80050033 [10170.547631] CR2: 7f3a9dd13b80 CR3: 9640a000 CR4: 001006e0 [10170.554957] Call Trace: [10170.557452] [10170.559541] ? ip_copy_metadata+0x220/0x220 [10170.563849] ip_fragment.constprop.45+0x43/0x80 [10170.568499] ip_finish_output+0x182/0x270 [10170.572604] ? nf_hook_slow+0x48/0xc0 [10170.576354] ip_output+0x70/0xe0 [10170.579664] ? ip_fragment.constprop.45+0x80/0x80 [10170.584496] ip_forward_finish+0x51/0x80 [10170.588540] ip_forward+0x376/0x470 [10170.592108] ? ip4_key_hashfn+0xc0/0xc0 [10170.596056] ip_rcv_finish+0x129/0x430 [10170.599911] ip_rcv+0x296/0x360 [10170.603125] ? inet_del_offload+0x40/0x40 [10170.607242] __netif_receive_skb_core+0x432/0xb80 [10170.612070] ? __slab_free+0x14d/0x2c0
[Kernel-packages] [Bug 1843152] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1843152/+attachment/5287286/+files/CRDA.txt -- 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/1843152 Title: Kernel Panic with linux kernel 4.15.0-60 possibly related to network subsystem Status in linux package in Ubuntu: Incomplete Bug description: 1. Releases: Ubuntu Server 16.04 and Ubuntu Server 18.04 2. Package: Linux Kernel 4.15.0-60 amd64 3. What I expected to happen: Not a recurrent kernel panic. 4. What happened instead: Recurrent kernel panic. While running Ubuntu 16.04 server on an internet appliance that was serving as my router, after the system was updated from kernel 4.15.0-58 to 4.15.0-60, I began getting frequent kernel panics (system seldom remained up for more than an hour after a reboot). I have included example stack traces below. After memtest revealed no problems, and fsck revealed no problems, I opted to rebuild from a fresh install, this time of Ubuntu 18.04, server. Upon completing the rebuilt, and put it back in service. It crashed with the same kernel panic within 30 minutes. I have since updated to kernel 5.0.0-27 and the kernel panics have completely stopped. [10170.296117] kernel BUG at /build/linux-5mCauq/linux-4.15.0/net/ipv4/ip_output.c:636! [10170.304214] invalid opcode: [#1] SMP PTI [10170.308692] Modules linked in: st lp parport_pc ppdev parport ipt_REJECT nf_reject_ipv4 xt_condition(OE) xt_time xt_comment xt_iface(OE) xt_multiport xt_conntrack xt_set xt_recent xt_hashlimit xt_addrtype xt_mark iptable_mangle xt_nat xt_REDIRECT nf_nat_redirect ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_iprange iptable_nat nf_nat_ipv4 nf_conntrack_ipv4 nf_defrag_ipv4 xt_tcpudp xt_CT iptable_raw ip_set_list_set ip_set_hash_ip ip_set_hash_net ip_set_hash_mac ip_set xt_NFLOG nfnetlink_log nf_log_ipv4 nf_log_common xt_LOG nf_conntrack_sane nf_conntrack_netlink nfnetlink nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda nf_nat nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_netbios_ns [10170.381810] nf_conntrack_broadcast nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp ts_kmp nf_conntrack_amanda nf_conntrack iptable_filter bridge intel_rapl intel_soc_dts_thermal intel_soc_dts_iosf intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm irqbypass punit_atom_debug intel_cstate snd_hda_intel snd_hda_codec snd_hda_core joydev snd_hwdep snd_pcm snd_timer serio_raw input_leds snd lpc_ich soundcore shpchp mac_hid mei_txe mei sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 8021q garp mrp stp llc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear i915 crct10dif_pclmul crc32_pclmul i2c_algo_bit drm_kms_helper [10170.454089] ghash_clmulni_intel e1000e syscopyarea sysfillrect sysimgblt fb_sys_fops ptp ahci psmouse cryptd drm pps_core libahci video hid_generic usbhid hid [last unloaded: parport_pc] [10170.471175] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G OE 4.15.0-60-generic #67-Ubuntu [10170.480269] Hardware name: Protectli FW1/FW1, BIOS 5.6.5 05/14/2019 [10170.486704] RIP: 0010:ip_do_fragment+0x482/0x820 [10170.491462] RSP: 0018:92533fc83a18 EFLAGS: 00010202 [10170.496824] RAX: 0001 RBX: 92532b43ed00 RCX: 8d64cdf0 [10170.504158] RDX: 0024 RSI: 05c8 RDI: 925329f06300 [10170.511485] RBP: 92533fc83a80 R08: 925330be9700 R09: 05dc [10170.518777] R10: R11: 92533fc839d0 R12: 0014 [10170.526096] R13: 92532dea4300 R14: 2328 R15: 925330be974e [10170.533430] FS: () GS:92533fc8() knlGS: [10170.541729] CS: 0010 DS: ES: CR0: 80050033 [10170.547631] CR2: 7f3a9dd13b80 CR3: 9640a000 CR4: 001006e0 [10170.554957] Call Trace: [10170.557452] [10170.559541] ? ip_copy_metadata+0x220/0x220 [10170.563849] ip_fragment.constprop.45+0x43/0x80 [10170.568499] ip_finish_output+0x182/0x270 [10170.572604] ? nf_hook_slow+0x48/0xc0 [10170.576354] ip_output+0x70/0xe0 [10170.579664] ? ip_fragment.constprop.45+0x80/0x80 [10170.584496] ip_forward_finish+0x51/0x80 [10170.588540] ip_forward+0x376/0x470 [10170.592108] ? ip4_key_hashfn+0xc0/0xc0 [10170.596056] ip_rcv_finish+0x129/0x430 [10170.599911] ip_rcv+0x296/0x360 [10170.603125] ? inet_del_offload+0x40/0x40 [10170.607242] __netif_receive_skb_core+0x432/0xb80 [10170.612070] ? __slab_free+0x14d/0x2c0
[Kernel-packages] [Bug 1843152] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1843152/+attachment/5287289/+files/Lspci.txt -- 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/1843152 Title: Kernel Panic with linux kernel 4.15.0-60 possibly related to network subsystem Status in linux package in Ubuntu: Incomplete Bug description: 1. Releases: Ubuntu Server 16.04 and Ubuntu Server 18.04 2. Package: Linux Kernel 4.15.0-60 amd64 3. What I expected to happen: Not a recurrent kernel panic. 4. What happened instead: Recurrent kernel panic. While running Ubuntu 16.04 server on an internet appliance that was serving as my router, after the system was updated from kernel 4.15.0-58 to 4.15.0-60, I began getting frequent kernel panics (system seldom remained up for more than an hour after a reboot). I have included example stack traces below. After memtest revealed no problems, and fsck revealed no problems, I opted to rebuild from a fresh install, this time of Ubuntu 18.04, server. Upon completing the rebuilt, and put it back in service. It crashed with the same kernel panic within 30 minutes. I have since updated to kernel 5.0.0-27 and the kernel panics have completely stopped. [10170.296117] kernel BUG at /build/linux-5mCauq/linux-4.15.0/net/ipv4/ip_output.c:636! [10170.304214] invalid opcode: [#1] SMP PTI [10170.308692] Modules linked in: st lp parport_pc ppdev parport ipt_REJECT nf_reject_ipv4 xt_condition(OE) xt_time xt_comment xt_iface(OE) xt_multiport xt_conntrack xt_set xt_recent xt_hashlimit xt_addrtype xt_mark iptable_mangle xt_nat xt_REDIRECT nf_nat_redirect ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_iprange iptable_nat nf_nat_ipv4 nf_conntrack_ipv4 nf_defrag_ipv4 xt_tcpudp xt_CT iptable_raw ip_set_list_set ip_set_hash_ip ip_set_hash_net ip_set_hash_mac ip_set xt_NFLOG nfnetlink_log nf_log_ipv4 nf_log_common xt_LOG nf_conntrack_sane nf_conntrack_netlink nfnetlink nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda nf_nat nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_netbios_ns [10170.381810] nf_conntrack_broadcast nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp ts_kmp nf_conntrack_amanda nf_conntrack iptable_filter bridge intel_rapl intel_soc_dts_thermal intel_soc_dts_iosf intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm irqbypass punit_atom_debug intel_cstate snd_hda_intel snd_hda_codec snd_hda_core joydev snd_hwdep snd_pcm snd_timer serio_raw input_leds snd lpc_ich soundcore shpchp mac_hid mei_txe mei sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 8021q garp mrp stp llc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear i915 crct10dif_pclmul crc32_pclmul i2c_algo_bit drm_kms_helper [10170.454089] ghash_clmulni_intel e1000e syscopyarea sysfillrect sysimgblt fb_sys_fops ptp ahci psmouse cryptd drm pps_core libahci video hid_generic usbhid hid [last unloaded: parport_pc] [10170.471175] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G OE 4.15.0-60-generic #67-Ubuntu [10170.480269] Hardware name: Protectli FW1/FW1, BIOS 5.6.5 05/14/2019 [10170.486704] RIP: 0010:ip_do_fragment+0x482/0x820 [10170.491462] RSP: 0018:92533fc83a18 EFLAGS: 00010202 [10170.496824] RAX: 0001 RBX: 92532b43ed00 RCX: 8d64cdf0 [10170.504158] RDX: 0024 RSI: 05c8 RDI: 925329f06300 [10170.511485] RBP: 92533fc83a80 R08: 925330be9700 R09: 05dc [10170.518777] R10: R11: 92533fc839d0 R12: 0014 [10170.526096] R13: 92532dea4300 R14: 2328 R15: 925330be974e [10170.533430] FS: () GS:92533fc8() knlGS: [10170.541729] CS: 0010 DS: ES: CR0: 80050033 [10170.547631] CR2: 7f3a9dd13b80 CR3: 9640a000 CR4: 001006e0 [10170.554957] Call Trace: [10170.557452] [10170.559541] ? ip_copy_metadata+0x220/0x220 [10170.563849] ip_fragment.constprop.45+0x43/0x80 [10170.568499] ip_finish_output+0x182/0x270 [10170.572604] ? nf_hook_slow+0x48/0xc0 [10170.576354] ip_output+0x70/0xe0 [10170.579664] ? ip_fragment.constprop.45+0x80/0x80 [10170.584496] ip_forward_finish+0x51/0x80 [10170.588540] ip_forward+0x376/0x470 [10170.592108] ? ip4_key_hashfn+0xc0/0xc0 [10170.596056] ip_rcv_finish+0x129/0x430 [10170.599911] ip_rcv+0x296/0x360 [10170.603125] ? inet_del_offload+0x40/0x40 [10170.607242] __netif_receive_skb_core+0x432/0xb80 [10170.612070] ? __slab_free+0x14d/0x2c0
[Kernel-packages] [Bug 1843152] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1843152/+attachment/5287290/+files/Lsusb.txt -- 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/1843152 Title: Kernel Panic with linux kernel 4.15.0-60 possibly related to network subsystem Status in linux package in Ubuntu: Incomplete Bug description: 1. Releases: Ubuntu Server 16.04 and Ubuntu Server 18.04 2. Package: Linux Kernel 4.15.0-60 amd64 3. What I expected to happen: Not a recurrent kernel panic. 4. What happened instead: Recurrent kernel panic. While running Ubuntu 16.04 server on an internet appliance that was serving as my router, after the system was updated from kernel 4.15.0-58 to 4.15.0-60, I began getting frequent kernel panics (system seldom remained up for more than an hour after a reboot). I have included example stack traces below. After memtest revealed no problems, and fsck revealed no problems, I opted to rebuild from a fresh install, this time of Ubuntu 18.04, server. Upon completing the rebuilt, and put it back in service. It crashed with the same kernel panic within 30 minutes. I have since updated to kernel 5.0.0-27 and the kernel panics have completely stopped. [10170.296117] kernel BUG at /build/linux-5mCauq/linux-4.15.0/net/ipv4/ip_output.c:636! [10170.304214] invalid opcode: [#1] SMP PTI [10170.308692] Modules linked in: st lp parport_pc ppdev parport ipt_REJECT nf_reject_ipv4 xt_condition(OE) xt_time xt_comment xt_iface(OE) xt_multiport xt_conntrack xt_set xt_recent xt_hashlimit xt_addrtype xt_mark iptable_mangle xt_nat xt_REDIRECT nf_nat_redirect ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_iprange iptable_nat nf_nat_ipv4 nf_conntrack_ipv4 nf_defrag_ipv4 xt_tcpudp xt_CT iptable_raw ip_set_list_set ip_set_hash_ip ip_set_hash_net ip_set_hash_mac ip_set xt_NFLOG nfnetlink_log nf_log_ipv4 nf_log_common xt_LOG nf_conntrack_sane nf_conntrack_netlink nfnetlink nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda nf_nat nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_netbios_ns [10170.381810] nf_conntrack_broadcast nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp ts_kmp nf_conntrack_amanda nf_conntrack iptable_filter bridge intel_rapl intel_soc_dts_thermal intel_soc_dts_iosf intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm irqbypass punit_atom_debug intel_cstate snd_hda_intel snd_hda_codec snd_hda_core joydev snd_hwdep snd_pcm snd_timer serio_raw input_leds snd lpc_ich soundcore shpchp mac_hid mei_txe mei sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 8021q garp mrp stp llc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear i915 crct10dif_pclmul crc32_pclmul i2c_algo_bit drm_kms_helper [10170.454089] ghash_clmulni_intel e1000e syscopyarea sysfillrect sysimgblt fb_sys_fops ptp ahci psmouse cryptd drm pps_core libahci video hid_generic usbhid hid [last unloaded: parport_pc] [10170.471175] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G OE 4.15.0-60-generic #67-Ubuntu [10170.480269] Hardware name: Protectli FW1/FW1, BIOS 5.6.5 05/14/2019 [10170.486704] RIP: 0010:ip_do_fragment+0x482/0x820 [10170.491462] RSP: 0018:92533fc83a18 EFLAGS: 00010202 [10170.496824] RAX: 0001 RBX: 92532b43ed00 RCX: 8d64cdf0 [10170.504158] RDX: 0024 RSI: 05c8 RDI: 925329f06300 [10170.511485] RBP: 92533fc83a80 R08: 925330be9700 R09: 05dc [10170.518777] R10: R11: 92533fc839d0 R12: 0014 [10170.526096] R13: 92532dea4300 R14: 2328 R15: 925330be974e [10170.533430] FS: () GS:92533fc8() knlGS: [10170.541729] CS: 0010 DS: ES: CR0: 80050033 [10170.547631] CR2: 7f3a9dd13b80 CR3: 9640a000 CR4: 001006e0 [10170.554957] Call Trace: [10170.557452] [10170.559541] ? ip_copy_metadata+0x220/0x220 [10170.563849] ip_fragment.constprop.45+0x43/0x80 [10170.568499] ip_finish_output+0x182/0x270 [10170.572604] ? nf_hook_slow+0x48/0xc0 [10170.576354] ip_output+0x70/0xe0 [10170.579664] ? ip_fragment.constprop.45+0x80/0x80 [10170.584496] ip_forward_finish+0x51/0x80 [10170.588540] ip_forward+0x376/0x470 [10170.592108] ? ip4_key_hashfn+0xc0/0xc0 [10170.596056] ip_rcv_finish+0x129/0x430 [10170.599911] ip_rcv+0x296/0x360 [10170.603125] ? inet_del_offload+0x40/0x40 [10170.607242] __netif_receive_skb_core+0x432/0xb80 [10170.612070] ? __slab_free+0x14d/0x2c0
[Kernel-packages] [Bug 1843152] HookError_generic.txt
apport information ** Attachment added: "HookError_generic.txt" https://bugs.launchpad.net/bugs/1843152/+attachment/5287288/+files/HookError_generic.txt -- 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/1843152 Title: Kernel Panic with linux kernel 4.15.0-60 possibly related to network subsystem Status in linux package in Ubuntu: Incomplete Bug description: 1. Releases: Ubuntu Server 16.04 and Ubuntu Server 18.04 2. Package: Linux Kernel 4.15.0-60 amd64 3. What I expected to happen: Not a recurrent kernel panic. 4. What happened instead: Recurrent kernel panic. While running Ubuntu 16.04 server on an internet appliance that was serving as my router, after the system was updated from kernel 4.15.0-58 to 4.15.0-60, I began getting frequent kernel panics (system seldom remained up for more than an hour after a reboot). I have included example stack traces below. After memtest revealed no problems, and fsck revealed no problems, I opted to rebuild from a fresh install, this time of Ubuntu 18.04, server. Upon completing the rebuilt, and put it back in service. It crashed with the same kernel panic within 30 minutes. I have since updated to kernel 5.0.0-27 and the kernel panics have completely stopped. [10170.296117] kernel BUG at /build/linux-5mCauq/linux-4.15.0/net/ipv4/ip_output.c:636! [10170.304214] invalid opcode: [#1] SMP PTI [10170.308692] Modules linked in: st lp parport_pc ppdev parport ipt_REJECT nf_reject_ipv4 xt_condition(OE) xt_time xt_comment xt_iface(OE) xt_multiport xt_conntrack xt_set xt_recent xt_hashlimit xt_addrtype xt_mark iptable_mangle xt_nat xt_REDIRECT nf_nat_redirect ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_iprange iptable_nat nf_nat_ipv4 nf_conntrack_ipv4 nf_defrag_ipv4 xt_tcpudp xt_CT iptable_raw ip_set_list_set ip_set_hash_ip ip_set_hash_net ip_set_hash_mac ip_set xt_NFLOG nfnetlink_log nf_log_ipv4 nf_log_common xt_LOG nf_conntrack_sane nf_conntrack_netlink nfnetlink nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda nf_nat nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_netbios_ns [10170.381810] nf_conntrack_broadcast nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp ts_kmp nf_conntrack_amanda nf_conntrack iptable_filter bridge intel_rapl intel_soc_dts_thermal intel_soc_dts_iosf intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm irqbypass punit_atom_debug intel_cstate snd_hda_intel snd_hda_codec snd_hda_core joydev snd_hwdep snd_pcm snd_timer serio_raw input_leds snd lpc_ich soundcore shpchp mac_hid mei_txe mei sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 8021q garp mrp stp llc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear i915 crct10dif_pclmul crc32_pclmul i2c_algo_bit drm_kms_helper [10170.454089] ghash_clmulni_intel e1000e syscopyarea sysfillrect sysimgblt fb_sys_fops ptp ahci psmouse cryptd drm pps_core libahci video hid_generic usbhid hid [last unloaded: parport_pc] [10170.471175] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G OE 4.15.0-60-generic #67-Ubuntu [10170.480269] Hardware name: Protectli FW1/FW1, BIOS 5.6.5 05/14/2019 [10170.486704] RIP: 0010:ip_do_fragment+0x482/0x820 [10170.491462] RSP: 0018:92533fc83a18 EFLAGS: 00010202 [10170.496824] RAX: 0001 RBX: 92532b43ed00 RCX: 8d64cdf0 [10170.504158] RDX: 0024 RSI: 05c8 RDI: 925329f06300 [10170.511485] RBP: 92533fc83a80 R08: 925330be9700 R09: 05dc [10170.518777] R10: R11: 92533fc839d0 R12: 0014 [10170.526096] R13: 92532dea4300 R14: 2328 R15: 925330be974e [10170.533430] FS: () GS:92533fc8() knlGS: [10170.541729] CS: 0010 DS: ES: CR0: 80050033 [10170.547631] CR2: 7f3a9dd13b80 CR3: 9640a000 CR4: 001006e0 [10170.554957] Call Trace: [10170.557452] [10170.559541] ? ip_copy_metadata+0x220/0x220 [10170.563849] ip_fragment.constprop.45+0x43/0x80 [10170.568499] ip_finish_output+0x182/0x270 [10170.572604] ? nf_hook_slow+0x48/0xc0 [10170.576354] ip_output+0x70/0xe0 [10170.579664] ? ip_fragment.constprop.45+0x80/0x80 [10170.584496] ip_forward_finish+0x51/0x80 [10170.588540] ip_forward+0x376/0x470 [10170.592108] ? ip4_key_hashfn+0xc0/0xc0 [10170.596056] ip_rcv_finish+0x129/0x430 [10170.599911] ip_rcv+0x296/0x360 [10170.603125] ? inet_del_offload+0x40/0x40 [10170.607242] __netif_receive_skb_core+0x432/0xb80 [10170.612070] ?
[Kernel-packages] [Bug 1843152] apport information
AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 8 11:07 seq crw-rw 1 root audio 116, 33 Sep 8 11:07 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=f0a1910d-2e27-4679-bf5c-e3b30f2fe8a1 InstallationDate: Installed on 2017-06-06 (823 days ago) InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.8) IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant DL380 G5 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-58-generic root=UUID=9bcdbf2d-a0e7-4d04-af89-8c452d46607a ro apparmor=0 security= ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.157.21 RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial Uname: Linux 4.15.0-58-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 05/02/2011 dmi.bios.vendor: HP dmi.bios.version: P56 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP56:bd05/02/2011:svnHP:pnProLiantDL380G5:pvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL380 G5 dmi.sys.vendor: HP -- 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/1843152 Title: Kernel Panic with linux kernel 4.15.0-60 possibly related to network subsystem Status in linux package in Ubuntu: Incomplete Bug description: 1. Releases: Ubuntu Server 16.04 and Ubuntu Server 18.04 2. Package: Linux Kernel 4.15.0-60 amd64 3. What I expected to happen: Not a recurrent kernel panic. 4. What happened instead: Recurrent kernel panic. While running Ubuntu 16.04 server on an internet appliance that was serving as my router, after the system was updated from kernel 4.15.0-58 to 4.15.0-60, I began getting frequent kernel panics (system seldom remained up for more than an hour after a reboot). I have included example stack traces below. After memtest revealed no problems, and fsck revealed no problems, I opted to rebuild from a fresh install, this time of Ubuntu 18.04, server. Upon completing the rebuilt, and put it back in service. It crashed with the same kernel panic within 30 minutes. I have since updated to kernel 5.0.0-27 and the kernel panics have completely stopped. [10170.296117] kernel BUG at /build/linux-5mCauq/linux-4.15.0/net/ipv4/ip_output.c:636! [10170.304214] invalid opcode: [#1] SMP PTI [10170.308692] Modules linked in: st lp parport_pc ppdev parport ipt_REJECT nf_reject_ipv4 xt_condition(OE) xt_time xt_comment xt_iface(OE) xt_multiport xt_conntrack xt_set xt_recent xt_hashlimit xt_addrtype xt_mark iptable_mangle xt_nat xt_REDIRECT nf_nat_redirect ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_iprange iptable_nat nf_nat_ipv4 nf_conntrack_ipv4 nf_defrag_ipv4 xt_tcpudp xt_CT iptable_raw ip_set_list_set ip_set_hash_ip ip_set_hash_net ip_set_hash_mac ip_set xt_NFLOG nfnetlink_log nf_log_ipv4 nf_log_common xt_LOG nf_conntrack_sane nf_conntrack_netlink nfnetlink nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda nf_nat nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_netbios_ns [10170.381810] nf_conntrack_broadcast nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp ts_kmp nf_conntrack_amanda nf_conntrack iptable_filter bridge intel_rapl intel_soc_dts_thermal intel_soc_dts_iosf intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm irqbypass punit_atom_debug intel_cstate snd_hda_intel snd_hda_codec snd_hda_core joydev snd_hwdep snd_pcm snd_timer serio_raw input_leds snd lpc_ich soundcore shpchp mac_hid mei_txe mei sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 8021q garp mrp stp llc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear i915 crct10dif_pclmul crc32_pclmul i2c_algo_bit drm_kms_helper [10170.454089] ghash_clmulni_intel e1000e syscopyarea sysfillrect sysimgblt
[Kernel-packages] [Bug 1843152] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1843152/+attachment/5287287/+files/CurrentDmesg.txt -- 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/1843152 Title: Kernel Panic with linux kernel 4.15.0-60 possibly related to network subsystem Status in linux package in Ubuntu: Incomplete Bug description: 1. Releases: Ubuntu Server 16.04 and Ubuntu Server 18.04 2. Package: Linux Kernel 4.15.0-60 amd64 3. What I expected to happen: Not a recurrent kernel panic. 4. What happened instead: Recurrent kernel panic. While running Ubuntu 16.04 server on an internet appliance that was serving as my router, after the system was updated from kernel 4.15.0-58 to 4.15.0-60, I began getting frequent kernel panics (system seldom remained up for more than an hour after a reboot). I have included example stack traces below. After memtest revealed no problems, and fsck revealed no problems, I opted to rebuild from a fresh install, this time of Ubuntu 18.04, server. Upon completing the rebuilt, and put it back in service. It crashed with the same kernel panic within 30 minutes. I have since updated to kernel 5.0.0-27 and the kernel panics have completely stopped. [10170.296117] kernel BUG at /build/linux-5mCauq/linux-4.15.0/net/ipv4/ip_output.c:636! [10170.304214] invalid opcode: [#1] SMP PTI [10170.308692] Modules linked in: st lp parport_pc ppdev parport ipt_REJECT nf_reject_ipv4 xt_condition(OE) xt_time xt_comment xt_iface(OE) xt_multiport xt_conntrack xt_set xt_recent xt_hashlimit xt_addrtype xt_mark iptable_mangle xt_nat xt_REDIRECT nf_nat_redirect ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_iprange iptable_nat nf_nat_ipv4 nf_conntrack_ipv4 nf_defrag_ipv4 xt_tcpudp xt_CT iptable_raw ip_set_list_set ip_set_hash_ip ip_set_hash_net ip_set_hash_mac ip_set xt_NFLOG nfnetlink_log nf_log_ipv4 nf_log_common xt_LOG nf_conntrack_sane nf_conntrack_netlink nfnetlink nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda nf_nat nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_netbios_ns [10170.381810] nf_conntrack_broadcast nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp ts_kmp nf_conntrack_amanda nf_conntrack iptable_filter bridge intel_rapl intel_soc_dts_thermal intel_soc_dts_iosf intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm irqbypass punit_atom_debug intel_cstate snd_hda_intel snd_hda_codec snd_hda_core joydev snd_hwdep snd_pcm snd_timer serio_raw input_leds snd lpc_ich soundcore shpchp mac_hid mei_txe mei sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 8021q garp mrp stp llc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear i915 crct10dif_pclmul crc32_pclmul i2c_algo_bit drm_kms_helper [10170.454089] ghash_clmulni_intel e1000e syscopyarea sysfillrect sysimgblt fb_sys_fops ptp ahci psmouse cryptd drm pps_core libahci video hid_generic usbhid hid [last unloaded: parport_pc] [10170.471175] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G OE 4.15.0-60-generic #67-Ubuntu [10170.480269] Hardware name: Protectli FW1/FW1, BIOS 5.6.5 05/14/2019 [10170.486704] RIP: 0010:ip_do_fragment+0x482/0x820 [10170.491462] RSP: 0018:92533fc83a18 EFLAGS: 00010202 [10170.496824] RAX: 0001 RBX: 92532b43ed00 RCX: 8d64cdf0 [10170.504158] RDX: 0024 RSI: 05c8 RDI: 925329f06300 [10170.511485] RBP: 92533fc83a80 R08: 925330be9700 R09: 05dc [10170.518777] R10: R11: 92533fc839d0 R12: 0014 [10170.526096] R13: 92532dea4300 R14: 2328 R15: 925330be974e [10170.533430] FS: () GS:92533fc8() knlGS: [10170.541729] CS: 0010 DS: ES: CR0: 80050033 [10170.547631] CR2: 7f3a9dd13b80 CR3: 9640a000 CR4: 001006e0 [10170.554957] Call Trace: [10170.557452] [10170.559541] ? ip_copy_metadata+0x220/0x220 [10170.563849] ip_fragment.constprop.45+0x43/0x80 [10170.568499] ip_finish_output+0x182/0x270 [10170.572604] ? nf_hook_slow+0x48/0xc0 [10170.576354] ip_output+0x70/0xe0 [10170.579664] ? ip_fragment.constprop.45+0x80/0x80 [10170.584496] ip_forward_finish+0x51/0x80 [10170.588540] ip_forward+0x376/0x470 [10170.592108] ? ip4_key_hashfn+0xc0/0xc0 [10170.596056] ip_rcv_finish+0x129/0x430 [10170.599911] ip_rcv+0x296/0x360 [10170.603125] ? inet_del_offload+0x40/0x40 [10170.607242] __netif_receive_skb_core+0x432/0xb80 [10170.612070] ?
[Kernel-packages] [Bug 1843152] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1843152/+attachment/5287291/+files/ProcCpuinfoMinimal.txt -- 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/1843152 Title: Kernel Panic with linux kernel 4.15.0-60 possibly related to network subsystem Status in linux package in Ubuntu: Incomplete Bug description: 1. Releases: Ubuntu Server 16.04 and Ubuntu Server 18.04 2. Package: Linux Kernel 4.15.0-60 amd64 3. What I expected to happen: Not a recurrent kernel panic. 4. What happened instead: Recurrent kernel panic. While running Ubuntu 16.04 server on an internet appliance that was serving as my router, after the system was updated from kernel 4.15.0-58 to 4.15.0-60, I began getting frequent kernel panics (system seldom remained up for more than an hour after a reboot). I have included example stack traces below. After memtest revealed no problems, and fsck revealed no problems, I opted to rebuild from a fresh install, this time of Ubuntu 18.04, server. Upon completing the rebuilt, and put it back in service. It crashed with the same kernel panic within 30 minutes. I have since updated to kernel 5.0.0-27 and the kernel panics have completely stopped. [10170.296117] kernel BUG at /build/linux-5mCauq/linux-4.15.0/net/ipv4/ip_output.c:636! [10170.304214] invalid opcode: [#1] SMP PTI [10170.308692] Modules linked in: st lp parport_pc ppdev parport ipt_REJECT nf_reject_ipv4 xt_condition(OE) xt_time xt_comment xt_iface(OE) xt_multiport xt_conntrack xt_set xt_recent xt_hashlimit xt_addrtype xt_mark iptable_mangle xt_nat xt_REDIRECT nf_nat_redirect ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_iprange iptable_nat nf_nat_ipv4 nf_conntrack_ipv4 nf_defrag_ipv4 xt_tcpudp xt_CT iptable_raw ip_set_list_set ip_set_hash_ip ip_set_hash_net ip_set_hash_mac ip_set xt_NFLOG nfnetlink_log nf_log_ipv4 nf_log_common xt_LOG nf_conntrack_sane nf_conntrack_netlink nfnetlink nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda nf_nat nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_netbios_ns [10170.381810] nf_conntrack_broadcast nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp ts_kmp nf_conntrack_amanda nf_conntrack iptable_filter bridge intel_rapl intel_soc_dts_thermal intel_soc_dts_iosf intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm irqbypass punit_atom_debug intel_cstate snd_hda_intel snd_hda_codec snd_hda_core joydev snd_hwdep snd_pcm snd_timer serio_raw input_leds snd lpc_ich soundcore shpchp mac_hid mei_txe mei sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 8021q garp mrp stp llc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear i915 crct10dif_pclmul crc32_pclmul i2c_algo_bit drm_kms_helper [10170.454089] ghash_clmulni_intel e1000e syscopyarea sysfillrect sysimgblt fb_sys_fops ptp ahci psmouse cryptd drm pps_core libahci video hid_generic usbhid hid [last unloaded: parport_pc] [10170.471175] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G OE 4.15.0-60-generic #67-Ubuntu [10170.480269] Hardware name: Protectli FW1/FW1, BIOS 5.6.5 05/14/2019 [10170.486704] RIP: 0010:ip_do_fragment+0x482/0x820 [10170.491462] RSP: 0018:92533fc83a18 EFLAGS: 00010202 [10170.496824] RAX: 0001 RBX: 92532b43ed00 RCX: 8d64cdf0 [10170.504158] RDX: 0024 RSI: 05c8 RDI: 925329f06300 [10170.511485] RBP: 92533fc83a80 R08: 925330be9700 R09: 05dc [10170.518777] R10: R11: 92533fc839d0 R12: 0014 [10170.526096] R13: 92532dea4300 R14: 2328 R15: 925330be974e [10170.533430] FS: () GS:92533fc8() knlGS: [10170.541729] CS: 0010 DS: ES: CR0: 80050033 [10170.547631] CR2: 7f3a9dd13b80 CR3: 9640a000 CR4: 001006e0 [10170.554957] Call Trace: [10170.557452] [10170.559541] ? ip_copy_metadata+0x220/0x220 [10170.563849] ip_fragment.constprop.45+0x43/0x80 [10170.568499] ip_finish_output+0x182/0x270 [10170.572604] ? nf_hook_slow+0x48/0xc0 [10170.576354] ip_output+0x70/0xe0 [10170.579664] ? ip_fragment.constprop.45+0x80/0x80 [10170.584496] ip_forward_finish+0x51/0x80 [10170.588540] ip_forward+0x376/0x470 [10170.592108] ? ip4_key_hashfn+0xc0/0xc0 [10170.596056] ip_rcv_finish+0x129/0x430 [10170.599911] ip_rcv+0x296/0x360 [10170.603125] ? inet_del_offload+0x40/0x40 [10170.607242] __netif_receive_skb_core+0x432/0xb80 [10170.612070] ?
[Kernel-packages] [Bug 1843152] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1843152/+attachment/5287292/+files/ProcInterrupts.txt -- 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/1843152 Title: Kernel Panic with linux kernel 4.15.0-60 possibly related to network subsystem Status in linux package in Ubuntu: Incomplete Bug description: 1. Releases: Ubuntu Server 16.04 and Ubuntu Server 18.04 2. Package: Linux Kernel 4.15.0-60 amd64 3. What I expected to happen: Not a recurrent kernel panic. 4. What happened instead: Recurrent kernel panic. While running Ubuntu 16.04 server on an internet appliance that was serving as my router, after the system was updated from kernel 4.15.0-58 to 4.15.0-60, I began getting frequent kernel panics (system seldom remained up for more than an hour after a reboot). I have included example stack traces below. After memtest revealed no problems, and fsck revealed no problems, I opted to rebuild from a fresh install, this time of Ubuntu 18.04, server. Upon completing the rebuilt, and put it back in service. It crashed with the same kernel panic within 30 minutes. I have since updated to kernel 5.0.0-27 and the kernel panics have completely stopped. [10170.296117] kernel BUG at /build/linux-5mCauq/linux-4.15.0/net/ipv4/ip_output.c:636! [10170.304214] invalid opcode: [#1] SMP PTI [10170.308692] Modules linked in: st lp parport_pc ppdev parport ipt_REJECT nf_reject_ipv4 xt_condition(OE) xt_time xt_comment xt_iface(OE) xt_multiport xt_conntrack xt_set xt_recent xt_hashlimit xt_addrtype xt_mark iptable_mangle xt_nat xt_REDIRECT nf_nat_redirect ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_iprange iptable_nat nf_nat_ipv4 nf_conntrack_ipv4 nf_defrag_ipv4 xt_tcpudp xt_CT iptable_raw ip_set_list_set ip_set_hash_ip ip_set_hash_net ip_set_hash_mac ip_set xt_NFLOG nfnetlink_log nf_log_ipv4 nf_log_common xt_LOG nf_conntrack_sane nf_conntrack_netlink nfnetlink nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda nf_nat nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_netbios_ns [10170.381810] nf_conntrack_broadcast nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp ts_kmp nf_conntrack_amanda nf_conntrack iptable_filter bridge intel_rapl intel_soc_dts_thermal intel_soc_dts_iosf intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm irqbypass punit_atom_debug intel_cstate snd_hda_intel snd_hda_codec snd_hda_core joydev snd_hwdep snd_pcm snd_timer serio_raw input_leds snd lpc_ich soundcore shpchp mac_hid mei_txe mei sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 8021q garp mrp stp llc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear i915 crct10dif_pclmul crc32_pclmul i2c_algo_bit drm_kms_helper [10170.454089] ghash_clmulni_intel e1000e syscopyarea sysfillrect sysimgblt fb_sys_fops ptp ahci psmouse cryptd drm pps_core libahci video hid_generic usbhid hid [last unloaded: parport_pc] [10170.471175] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G OE 4.15.0-60-generic #67-Ubuntu [10170.480269] Hardware name: Protectli FW1/FW1, BIOS 5.6.5 05/14/2019 [10170.486704] RIP: 0010:ip_do_fragment+0x482/0x820 [10170.491462] RSP: 0018:92533fc83a18 EFLAGS: 00010202 [10170.496824] RAX: 0001 RBX: 92532b43ed00 RCX: 8d64cdf0 [10170.504158] RDX: 0024 RSI: 05c8 RDI: 925329f06300 [10170.511485] RBP: 92533fc83a80 R08: 925330be9700 R09: 05dc [10170.518777] R10: R11: 92533fc839d0 R12: 0014 [10170.526096] R13: 92532dea4300 R14: 2328 R15: 925330be974e [10170.533430] FS: () GS:92533fc8() knlGS: [10170.541729] CS: 0010 DS: ES: CR0: 80050033 [10170.547631] CR2: 7f3a9dd13b80 CR3: 9640a000 CR4: 001006e0 [10170.554957] Call Trace: [10170.557452] [10170.559541] ? ip_copy_metadata+0x220/0x220 [10170.563849] ip_fragment.constprop.45+0x43/0x80 [10170.568499] ip_finish_output+0x182/0x270 [10170.572604] ? nf_hook_slow+0x48/0xc0 [10170.576354] ip_output+0x70/0xe0 [10170.579664] ? ip_fragment.constprop.45+0x80/0x80 [10170.584496] ip_forward_finish+0x51/0x80 [10170.588540] ip_forward+0x376/0x470 [10170.592108] ? ip4_key_hashfn+0xc0/0xc0 [10170.596056] ip_rcv_finish+0x129/0x430 [10170.599911] ip_rcv+0x296/0x360 [10170.603125] ? inet_del_offload+0x40/0x40 [10170.607242] __netif_receive_skb_core+0x432/0xb80 [10170.612070] ?
[Kernel-packages] [Bug 1843152] Re: Kernel Panic with linux kernel 4.15.0-60 possibly related to network subsystem
I have same error (kernel panik message [ 365.536168] kernel BUG at /build/linux-hwe-L8V6Q3/linux-hwe-4.15.0/net/ipv4/ip_output.c:636! ) How I can provide `apport-collect` ? ** Tags added: apport-collected xenial -- 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/1843152 Title: Kernel Panic with linux kernel 4.15.0-60 possibly related to network subsystem Status in linux package in Ubuntu: Incomplete Bug description: 1. Releases: Ubuntu Server 16.04 and Ubuntu Server 18.04 2. Package: Linux Kernel 4.15.0-60 amd64 3. What I expected to happen: Not a recurrent kernel panic. 4. What happened instead: Recurrent kernel panic. While running Ubuntu 16.04 server on an internet appliance that was serving as my router, after the system was updated from kernel 4.15.0-58 to 4.15.0-60, I began getting frequent kernel panics (system seldom remained up for more than an hour after a reboot). I have included example stack traces below. After memtest revealed no problems, and fsck revealed no problems, I opted to rebuild from a fresh install, this time of Ubuntu 18.04, server. Upon completing the rebuilt, and put it back in service. It crashed with the same kernel panic within 30 minutes. I have since updated to kernel 5.0.0-27 and the kernel panics have completely stopped. [10170.296117] kernel BUG at /build/linux-5mCauq/linux-4.15.0/net/ipv4/ip_output.c:636! [10170.304214] invalid opcode: [#1] SMP PTI [10170.308692] Modules linked in: st lp parport_pc ppdev parport ipt_REJECT nf_reject_ipv4 xt_condition(OE) xt_time xt_comment xt_iface(OE) xt_multiport xt_conntrack xt_set xt_recent xt_hashlimit xt_addrtype xt_mark iptable_mangle xt_nat xt_REDIRECT nf_nat_redirect ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_iprange iptable_nat nf_nat_ipv4 nf_conntrack_ipv4 nf_defrag_ipv4 xt_tcpudp xt_CT iptable_raw ip_set_list_set ip_set_hash_ip ip_set_hash_net ip_set_hash_mac ip_set xt_NFLOG nfnetlink_log nf_log_ipv4 nf_log_common xt_LOG nf_conntrack_sane nf_conntrack_netlink nfnetlink nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda nf_nat nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_netbios_ns [10170.381810] nf_conntrack_broadcast nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp ts_kmp nf_conntrack_amanda nf_conntrack iptable_filter bridge intel_rapl intel_soc_dts_thermal intel_soc_dts_iosf intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm irqbypass punit_atom_debug intel_cstate snd_hda_intel snd_hda_codec snd_hda_core joydev snd_hwdep snd_pcm snd_timer serio_raw input_leds snd lpc_ich soundcore shpchp mac_hid mei_txe mei sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 8021q garp mrp stp llc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear i915 crct10dif_pclmul crc32_pclmul i2c_algo_bit drm_kms_helper [10170.454089] ghash_clmulni_intel e1000e syscopyarea sysfillrect sysimgblt fb_sys_fops ptp ahci psmouse cryptd drm pps_core libahci video hid_generic usbhid hid [last unloaded: parport_pc] [10170.471175] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G OE 4.15.0-60-generic #67-Ubuntu [10170.480269] Hardware name: Protectli FW1/FW1, BIOS 5.6.5 05/14/2019 [10170.486704] RIP: 0010:ip_do_fragment+0x482/0x820 [10170.491462] RSP: 0018:92533fc83a18 EFLAGS: 00010202 [10170.496824] RAX: 0001 RBX: 92532b43ed00 RCX: 8d64cdf0 [10170.504158] RDX: 0024 RSI: 05c8 RDI: 925329f06300 [10170.511485] RBP: 92533fc83a80 R08: 925330be9700 R09: 05dc [10170.518777] R10: R11: 92533fc839d0 R12: 0014 [10170.526096] R13: 92532dea4300 R14: 2328 R15: 925330be974e [10170.533430] FS: () GS:92533fc8() knlGS: [10170.541729] CS: 0010 DS: ES: CR0: 80050033 [10170.547631] CR2: 7f3a9dd13b80 CR3: 9640a000 CR4: 001006e0 [10170.554957] Call Trace: [10170.557452] [10170.559541] ? ip_copy_metadata+0x220/0x220 [10170.563849] ip_fragment.constprop.45+0x43/0x80 [10170.568499] ip_finish_output+0x182/0x270 [10170.572604] ? nf_hook_slow+0x48/0xc0 [10170.576354] ip_output+0x70/0xe0 [10170.579664] ? ip_fragment.constprop.45+0x80/0x80 [10170.584496] ip_forward_finish+0x51/0x80 [10170.588540] ip_forward+0x376/0x470 [10170.592108] ? ip4_key_hashfn+0xc0/0xc0 [10170.596056] ip_rcv_finish+0x129/0x430 [10170.599911] ip_rcv+0x296/0x360 [10170.603125] ? inet_del_offload+0x40/0x40 [10170.607242]
[Kernel-packages] [Bug 1842608] Re: xenial/linux: 4.4.0-162.190 -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 -- packages: main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Wednesday, 04. September 2019 07:52 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa main:failed,meta:depwait trackers: - trusty/linux-aws: bug 1842793, bug 1842606 + trusty/linux-aws: bug 1842606, bug 1842793 trusty/linux-lts-xenial: bug 1842607, bug 1842794 xenial/linux-aws: bug 1842597 xenial/linux-fips: bug 1842605 xenial/linux-kvm: bug 1842598 xenial/linux-raspi2: bug 1842600 xenial/linux-snapdragon: bug 1842603 xenial/linux/pc-kernel: bug 1842595 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/1842608 Title: xenial/linux: 4.4.0-162.190 -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 -- swm properties -- packages: main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Wednesday, 04. September 2019 07:52 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa main:failed,meta:depwait trackers: trusty/linux-aws: bug 1842606, bug 1842793 trusty/linux-lts-xenial: bug 1842607, bug 1842794 xenial/linux-aws: bug 1842597 xenial/linux-fips: bug 1842605 xenial/linux-kvm: bug 1842598 xenial/linux-raspi2: bug 1842600 xenial/linux-snapdragon: bug 1842603 xenial/linux/pc-kernel: bug 1842595 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842608/+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 1842713] Re: bionic/linux-snapdragon: 4.15.0-1062.69 -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: 1842746 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Thursday, 05. September 2019 22:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: - bionic/linux-snapdragon/dragonboard-kernel: bug 1839978, bug 1842712 + bionic/linux-snapdragon/dragonboard-kernel: bug 1842712, bug 1839978 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/1842713 Title: bionic/linux-snapdragon: 4.15.0-1062.69 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress 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 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: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon 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: 1842746 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Thursday, 05. September 2019 22:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1842712, bug 1839978 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842713/+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 1842772] Re: xenial/linux-oracle: 4.15.0-1023.26~16.04.1 -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: 1842773 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Signoff phase-changed: Friday, 06. September 2019 07:07 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress replaces: bug 1842724 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1842772 Title: xenial/linux-oracle: 4.15.0-1023.26~16.04.1 -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 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: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle 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: 1842773 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Signoff phase-changed: Friday, 06. September 2019 07:07 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress replaces: bug 1842724 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842772/+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 1842773] Re: bionic/linux-oracle: 4.15.0-1023.26 -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: 1842746 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Friday, 06. September 2019 07:00 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: - xenial/linux-oracle: bug 1842724, bug 1842772 + xenial/linux-oracle: bug 1842772, bug 1842724 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1842773 Title: bionic/linux-oracle: 4.15.0-1023.26 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress 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-lrm 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: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle 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: 1842746 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Friday, 06. September 2019 07:00 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-oracle: bug 1842772, bug 1842724 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842773/+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 1840484] Re: linux-oem 4.15 can not suspend to idle XPS-13-9380
this issue can not be reproduced on linux-oem-osp1 5.0.0.1020.21. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem in Ubuntu. https://bugs.launchpad.net/bugs/1840484 Title: linux-oem 4.15 can not suspend to idle XPS-13-9380 Status in OEM Priority Project: New Status in linux-signed-oem package in Ubuntu: New Bug description: it somehow s2i failed, from message , it seems the s2i process be blocked by thunderbolt device. dmesg: [193139.391652] pciehp :04:04.0:pcie204: pcie_do_write_cmd: no response from device [193139.391703] pciehp :04:01.0:pcie204: pcie_do_write_cmd: no response from device [193141.012736] PM: noirq suspend of devices failed [193141.772467] ath10k_pci :02:00.0: Unknown eventid: 118809 [193141.775359] ath10k_pci :02:00.0: Unknown eventid: 90118 [193141.872317] thunderbolt :05:00.0: control channel starting... Not sure is it relative that I hot plug out WD19 docking before suspend. reproduce rate: random ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1045-oem 4.15.0-1045.50 ProcVersionSignature: Ubuntu 4.15.0-1045.50-oem 4.15.18 Uname: Linux 4.15.0-1045-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 17 00:02:08 2019 InstallationDate: Installed on 2019-08-11 (5 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed-oem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1840484/+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 1840394] Re: Intel HDMI audio print "Unable to sync register" errors
** 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-oem in Ubuntu. https://bugs.launchpad.net/bugs/1840394 Title: Intel HDMI audio print "Unable to sync register" errors Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux-oem source package in Disco: Invalid Bug description: This fix is in the v5.3-rc3, and EAON already has this patch by backporting stable, so this patch is only for B/D. [Impact] After S3, the intel hdmi audio on a dell laptop print the error like below: [ 2052.030247] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f0d00. -5 And the hdmi audio can't work anymore after this. [Fix] For Intel hdmi audio codec, it doesn't need to resume forcibly, because the i915 side probably is not ready to let hdmi codec work, since the intel hdmi audio uses component framework, let i915 control the hdmi codec. [Test Case] Tested on that dell laptops, the hdmi audio doesn't have any issues anymore after applying this patch. [Regression Risk] Low. We tested this patch on a couple of machines (dell and lenovo). To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1840394/+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 1811730] Re: Thermald does not set max CPU after reseting the voltage using RAPL
Is there any chance this fix will be available for 18.10 as well? Thanks, Alex -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1811730 Title: Thermald does not set max CPU after reseting the voltage using RAPL Status in thermald package in Ubuntu: Confirmed Status in thermald source package in Bionic: Fix Committed Bug description: Hi, I was using Ubuntu 18.10 thermald package, but I noted that, after few seconds at max CPU usage (max temp), thermald send the signal to RALP to reduce the voltage of the CPU. It set the freq to minimum (800MHz in my case). But when the CPU is idle and temp is lowered (35-40ºC) it did not send the signal to resume normal operation of the CPU. I compiled the latest version of thermald from git (https://github.com/intel/thermal_daemon) and now everything works fine. I started to thought that the problem was the hardware or BIOS problem, as I disabled the CPU scaling on the BIOS, but intel_pstate continued doing freq scaling (I think for Turbo mode). But the real problem was Thermald. The latest version from git works really fine and it automatically disables and enable the Intel Turbo state and balance the freqs and fan control fine. My hardware is a Lenovo Thinkpad P52 with i7-8850H. I tested it using Ubuntu kernel and Kernel 4.20 optimized for i7 processor but with Ubuntu default config (except processor family="Core2/newer Xeon", Preemption Model="Preemptible Kernel (Low- Latency Desktop)" and Timer frequency="1000HZ". (Only changed those settings from make oldconfig and make deb-pkg). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: thermald (not installed) ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 14 23:45:01 2019 InstallationDate: Installed on 2018-12-11 (34 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: thermald UpgradeStatus: No upgrade log present (probably fresh install) - SRU Justification == [Impact] * As described by the original bug reporter, CPU usage of Lenovo P52 is sub-optimal under heavy load. * My observation is the machine exhibits a sharp drop of power usage and CPU frequency and takes time to slowly ramp up again (refer to the chart at https://bit.ly/2OJphB8) * Fixed by bisecting and backporting fixes from thermald project. [Test Case] * One can stress the CPU load of the machine and collect the CPU frequency and power usage over time to check for any anamoly. The script at https://people.canonical.com/~ypwong/p52_test_cpu.sh can help with this. * With the fix, the behaviour should be like this: https://bit.ly/2KA9EXB, a consistent power usage can be maintained. [Regression Potential] * Medium. The fix consists of 7 commits cherry-picked from upstream, these changes will affect any machines using RAPL cooling device. The impact may not be obvious in normal daily usage but will be manifested during heavy load, suggest a longer verification period so that more people can discover any adverse effect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1811730/+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 1840847] Re: cpuinfo_linux_get_max_processors_count always warns Ubuntu default MAX cpu values (stderr)
** No longer affects: linux (Ubuntu) -- 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/1840847 Title: cpuinfo_linux_get_max_processors_count always warns Ubuntu default MAX cpu values (stderr) Status in cpuinfo package in Ubuntu: Fix Released Bug description: From bug: https://bugs.launchpad.net/bugs/1840511 clickhouse builds test started failing because of the presence of stderr whenever using the function: cpuinfo_linux_get_max_processors_count(void) From cpuid library. This happens because: #if defined(__ANDROID__) && !defined(CPU_SETSIZE) /* * Android NDK headers before platform 21 do not define CPU_SETSIZE, * so we hard-code its value, as defined in platform 21 headers */ #if defined(__LP64__) static const uint32_t default_max_processors_count = 1024; #else static const uint32_t default_max_processors_count = 32; #endif #else static const uint32_t default_max_processors_count = CPU_SETSIZE; #endif #if !defined(__ANDROID__) /* * sched.h is only used for CPU_SETSIZE constant. * Android NDK headers before platform 21 do have this constant in sched.h */ #include #endif and resolving includes: x86_64-linux-gnu/bits/cpu-set.h: /* Size definition for CPU sets. */ #define __CPU_SETSIZE 1024 And the warning: Warning in cpuinfo: kernel_max value of 8191 parsed from /sys/devices/system/cpu/kernel_max exceeds platform-default limit 1023 Will always be displayed in Ubuntu OS, when it should NOT (does not make any sense to trigger a warning for something that can't be changed). FOR THE KERNEL TEAM: Should ubuntu update sched.h and/or cpu-set.h to reflect its decision in using 8192 max CPUs ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpuinfo/+bug/1840847/+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
