[Kernel-packages] [Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension
The commits wasn't in kernel -23. Let me check with the kernel team. ** Changed in: linux (Ubuntu Bionic) Status: Fix Released => Confirmed ** Changed in: linux (Ubuntu) Status: Confirmed => 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/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: Confirmed 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) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.80 dmi.board.name: H55M-LE dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias:
[Kernel-packages] [Bug 1774883] Re: GPF using CIFS and ACQ107 under heavy use
Please tell the Aquantia developers about this issue: Igor Russkikh Pavel Belous net...@vger.kernel.org (open list:NETWORKING DRIVERS) linux-ker...@vger.kernel.org (open list) -- 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/1774883 Title: GPF using CIFS and ACQ107 under heavy use Status in linux package in Ubuntu: Confirmed Bug description: using aquanta 10GBE ethernet I get a GPF when scanning CIFS-mounted library, works fine using 1GBE intel nic. GPF follows: Jun 2 12:55:28 klimt kernel: [ 2112.707816] general protection fault: [#1] SMP PTI Jun 2 12:55:28 klimt kernel: [ 2112.709215] Modules linked in: cmac md4 nls_utf8 cifs ccm fscache binfmt_misc snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp ar c4 kvm_intel iwlmvm kvm snd_hda_codec_realtek irqbypass snd_hda_codec_generic mac80211 intel_cstate iwlwifi intel_rapl_perf snd_hda_intel snd_hda_codec snd_hda_core cfg80211 intel_wmi_thunde rbolt mxm_wmi snd_hwdep snd_pcm snd_timer snd soundcore mei_me ioatdma mei shpchp wmi mac_hid nvidia_uvm(POE) sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear r aid1 nvidia_drm(POE) nvidia_modeset(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel Jun 2 12:55:28 klimt kernel: [ 2112.728235] pcbc nvidia(POE) aesni_intel aes_x86_64 crypto_simd glue_helper cryptd drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm ipmi_dev intf ipmi_msghandler igb e1000e nvme dca nvme_core i2c_algo_bit atlantic ptp pps_core ahci libahci Jun 2 12:55:28 klimt kernel: [ 2112.734257] CPU: 8 PID: 1499 Comm: EmbyServer Tainted: P OE4.15.0-22-generic #24-Ubuntu Jun 2 12:55:28 klimt kernel: [ 2112.736705] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X299 Professional Gaming i9 XE, BIOS P1.00 09/28/2017 Jun 2 12:55:28 klimt kernel: [ 2112.739735] RIP: 0010:prefetch_freepointer+0x15/0x30 Jun 2 12:55:28 klimt kernel: [ 2112.741050] RSP: 0018:aa9a0823bd20 EFLAGS: 00010206 Jun 2 12:55:28 klimt kernel: [ 2112.742434] RAX: RBX: 217a77ddff956e69 RCX: 8789 Jun 2 12:55:28 klimt kernel: [ 2112.744329] RDX: 8788 RSI: 217a77ddff956e69 RDI: 9da1d110ab80 Jun 2 12:55:28 klimt kernel: [ 2112.746222] RBP: aa9a0823bd20 R08: ca99fe822eb0 R09: 9da1d31275a0 Jun 2 12:55:28 klimt kernel: [ 2112.748113] R10: 0007fcbd8002 R11: 9da1ca4d9e00 R12: 014000c0 Jun 2 12:55:28 klimt kernel: [ 2112.750006] R13: 9da1ddc04780 R14: 9da1ca4d9000 R15: 9da1d110ab80 Jun 2 12:55:28 klimt kernel: [ 2112.794382] FS: 7fcc33fff700() GS:9da1de40() knlGS: Jun 2 12:55:28 klimt kernel: [ 2112.884578] CS: 0010 DS: ES: CR0: 80050033 Jun 2 12:55:28 klimt kernel: [ 2112.930582] CR2: 7fcc7e5bf000 CR3: 002012cdc006 CR4: 003606e0 Jun 2 12:55:28 klimt kernel: [ 2112.976554] DR0: DR1: DR2: Jun 2 12:55:28 klimt kernel: [ 2113.021459] DR3: DR6: fffe0ff0 DR7: 0400 Jun 2 12:55:28 klimt kernel: [ 2113.064959] Call Trace: Jun 2 12:55:28 klimt kernel: [ 2113.106986] kmem_cache_alloc+0xa2/0x1b0 Jun 2 12:55:28 klimt kernel: [ 2113.148571] ? anon_vma_fork+0x97/0x130 Jun 2 12:55:28 klimt kernel: [ 2113.189139] anon_vma_fork+0x97/0x130 Jun 2 12:55:28 klimt kernel: [ 2113.228632] copy_process.part.35+0xdce/0x1af0 Jun 2 12:55:28 klimt kernel: [ 2113.267459] _do_fork+0xdf/0x400 Jun 2 12:55:28 klimt kernel: [ 2113.305090] ? get_unused_fd_flags+0x30/0x40 Jun 2 12:55:28 klimt kernel: [ 2113.342027] SyS_clone+0x19/0x20 Jun 2 12:55:28 klimt kernel: [ 2113.377704] do_syscall_64+0x73/0x130 Jun 2 12:55:28 klimt kernel: [ 2113.412455] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Jun 2 12:55:28 klimt kernel: [ 2113.446867] RIP: 0033:0x7fcd1de5ab1c Jun 2 12:55:28 klimt kernel: [ 2113.480134] RSP: 002b:7fcc33ffb630 EFLAGS: 0246 ORIG_RAX: 0038 Jun 2 12:55:28 klimt kernel: [ 2113.546601] RAX: ffda RBX: 7fcc33ffb630 RCX: 7fcd1de5ab1c Jun 2 12:55:28 klimt kernel: [ 2113.581224] RDX: RSI: RDI: 01200011 Jun 2 12:55:28 klimt kernel: [ 2113.615346] RBP: 7fcc33ffb6a0 R08: 7fcc33fff700 R09: Jun 2 12:55:28 klimt kernel: [ 2113.648651] R10: 7fcc33fff9d0 R11: 0246 R12: Jun 2 12:55:28 klimt kernel: [ 2113.681308] R13: 0020 R14: 0001 R15: 7fcc281345f0 Jun 2 12:55:28
[Kernel-packages] [Bug 1775230] Re: TP-LINK TL-WN722N causes 100% CPU usage due to trace logging
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 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.17 -- 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/1775230 Title: TP-LINK TL-WN722N causes 100% CPU usage due to trace logging Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: Hello. Running Ubuntu 18.04 (4.15.0-22-generic), after plugging my TP-LINK TL-WN722N into the USB port, the CPU usage goes to 100%, and there are multiple reports of "stack traces" in dmesg. The attached snippet repeats multiple consecutive times in the dmesg output (albeit with a different trace id). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775230/+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 1776407] 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 1776407 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/1776407 Title: intel_do_flush_locked failed:Bad address Status in linux package in Ubuntu: Incomplete Bug description: when my app run on about 3 days, it exits and throws error info: "intel_do_flush_locked failed:bad address". this information is throwed by OpenGL(mesa). relations: app -> SDL -> OpenGL(mesa) -> libdrm -> kernel frequency: often kernel version:Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17GNU/Linux meas version: 17.2.8 libdrm : 2.4.83 I think it is a kernel bug because the bad address is meaning error code "-EFALUT". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776407/+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 1764645] Re: Bluetooth not working
The test kernel from #43 works on my laptop. Thanks. When is that likely to be 'official'? -- 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/1764645 Title: Bluetooth not working Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: I've installed the Ubuntu Bionic Beta 2 and everything works fine but the bluetooth (perfectly working with Xenial). In bluetooth control panel the slider is impossible to move to "on". 1) Ubuntu Release (via 'lsb_release -rd') Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 2) Version of package (apt-cache policy gnome-bluetooth) gnome-bluetooth: Installato: 3.28.0-2 Candidato: 3.28.0-2 Tabella versione: *** 3.28.0-2 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen I expected to switch on the bluetooth. 4) What happened instead Bluetooth won't switch on. 5) Output of rfkill list is: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 6) Output of lspci -knn | grep Net -A3; lsusb; dmesg | grep -i blue is: 03:00.0 Network controller [0280]: Qualcomm Atheros AR9462 Wireless Network Adapter [168c:0034] (rev 01) Subsystem: Bigfoot Networks, Inc. Killer Wireless-N 1202 Half- size Mini PCIe Card [1a56:2003] Kernel driver in use: ath9k Kernel modules: ath9k 04:00.0 Ethernet controller [0200]: Qualcomm Atheros QCA8171 Gigabit Ethernet [1969:10a1] (rev 10) Bus 002 Device 002: ID 8087:8000 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:8008 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 004: ID 04f2:b414 Chicony Electronics Co., Ltd Bus 003 Device 003: ID 0cf3:3004 Atheros Communications, Inc. AR3012 Bluetooth 4.0 Bus 003 Device 002: ID 0b05:17c4 ASUSTek Computer, Inc. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [ 17.715399] Bluetooth: Core ver 2.22 [ 17.715414] Bluetooth: HCI device and connection manager initialized [ 17.715416] Bluetooth: HCI socket layer initialized [ 17.715418] Bluetooth: L2CAP socket layer initialized [ 17.715422] Bluetooth: SCO socket layer initialized [ 17.723207] Bluetooth: hci0: don't support firmware rome 0x1102 [ 18.600648] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 18.600649] Bluetooth: BNEP filters: protocol multicast [ 18.600651] Bluetooth: BNEP socket layer initialized ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-15-generic 4.15.0-15.16 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stormy 1484 F pulseaudio /dev/snd/controlC0: stormy 1484 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Apr 17 08:46:30 2018 HibernationDevice: RESUME=UUID=3f513ca9-6817-4099-9718-fee68d68ec11 InstallationDate: Installed on 2018-04-16 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) MachineType: ASUSTeK COMPUTER INC. G750JH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G750JH.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G750JH dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG750JH.206:bd12/02/2013:svnASUSTeKCOMPUTERINC.:pnG750JH:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG750JH:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: G dmi.product.name: G750JH dmi.product.version: 1.0 dmi.sys.vendor:
[Kernel-packages] [Bug 1776352] Re: linux: 4.4.0-129.155 -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 ** 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 1776353 (linux-aws), bug 1776355 (linux-lts-xenial) derivatives: bug 1776356 (linux-aws), bug 1776357 (linux-euclid), bug 1776358 (linux-kvm), bug 1776359 (linux-raspi2), bug 1776361 (linux-snapdragon) + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Tuesday, 12. June 2018 10:34 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 1776353 (linux-aws), bug 1776355 (linux-lts-xenial) derivatives: bug 1776356 (linux-aws), bug 1776357 (linux-euclid), bug 1776358 (linux-kvm), bug 1776359 (linux-raspi2), bug 1776361 (linux-snapdragon) kernel-stable-phase:Uploaded kernel-stable-phase-changed:Tuesday, 12. June 2018 10:34 UTC + + -- 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/1776352 Title: linux: 4.4.0-129.155 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 1776353 (linux-aws), bug 1776355 (linux-lts-xenial) derivatives: bug 1776356 (linux-aws), bug 1776357 (linux-euclid), bug 1776358 (linux-kvm), bug 1776359 (linux-raspi2), bug 1776361 (linux-snapdragon) kernel-stable-phase:Uploaded kernel-stable-phase-changed:Tuesday, 12. June 2018 10:34 UTC -- swm properties -- phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776352/+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 1776353] Re: linux-aws: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package 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 -- kernel-stable-master-bug: 1776352 + kernel-stable-phase:Packaging + kernel-stable-phase-changed:Tuesday, 12. June 2018 11: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 -- swm properties -- kernel-stable-master-bug: 1776352 - kernel-stable-phase:Packaging - kernel-stable-phase-changed:Tuesday, 12. June 2018 11:03 UTC + phase: Packaging -- 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/1776353 Title: linux-aws: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 Trusty: 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: 1776352 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776353/+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 1776350] Re: linux: 3.13.0-152.202 -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 ** 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 1776351 (linux-lts-trusty) derivatives: + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Tuesday, 12. June 2018 11:02 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 1776351 (linux-lts-trusty) derivatives: kernel-stable-phase:Uploaded kernel-stable-phase-changed:Tuesday, 12. June 2018 11:02 UTC + + -- 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/1776350 Title: linux: 3.13.0-152.202 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 Trusty: 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 1776351 (linux-lts-trusty) derivatives: kernel-stable-phase:Uploaded kernel-stable-phase-changed:Tuesday, 12. June 2018 11:02 UTC -- swm properties -- phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776350/+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 1776449] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1: bcmwl kernel module failed to build
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1776449 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: New Bug description: ndswrapper ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1 ProcVersionSignature: Ubuntu 4.15.0-15.16~16.04.1-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 DKMSKernelVersion: 4.15.0-23-generic Date: Tue Jun 12 14:52:04 2018 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.1:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2: error: implicit declaration of function ‘init_timer’ [-Werror=implicit-function-declaration] InstallationDate: Installed on 2016-09-21 (629 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.1 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1776449/+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 1773905] Re: Support UVC1.5 Camera for Xenial
** Changed in: linux (Ubuntu Xenial) Status: Confirmed => 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/1773905 Title: Support UVC1.5 Camera for Xenial Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Bug description: ===SRU Justification=== [Impact] UVC1.5 USB class is not in UVC driver's device ID, so the driver doesn't get loaded. [Test] See if the uvcvideo module is loaded for UVC1.5 camera. I can confirm with this commit, uvcvideo.ko is loaded. In addition, cheese can use the webcam without issue. [Fix] Add UVC1.5 device id to uvcvideo. [Regression Potential] Low. The short control message is already fixed by another commit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773905/+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 1774336] Re: FS-Cache: Assertion failed: FS-Cache: 6 == 5 is false
** Changed in: linux (Ubuntu Trusty) Status: New => Fix Committed ** Changed in: linux (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: linux (Ubuntu Artful) Status: New => Fix Committed ** Changed in: linux (Ubuntu Bionic) 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/1774336 Title: FS-Cache: Assertion failed: FS-Cache: 6 == 5 is false Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: == SRU Justification == [Impact] Oops during heavy NFS + FSCache use: [81738.886634] FS-Cache: [81738.888281] FS-Cache: Assertion failed [81738.889461] FS-Cache: 6 == 5 is false [81738.890625] [ cut here ] [81738.891706] kernel BUG at /build/linux-hVVhWi/linux-4.4.0/fs/fscache/operation.c:494! 6 == 5 represents an operation being DEAD when it was not expected to be. [Cause] There is a race in fscache and cachefiles. One thread is in cachefiles_read_waiter: 1) object->work_lock is taken. 2) the operation is added to the to_do list. 3) the work lock is dropped. 4) fscache_enqueue_retrieval is called, which takes a reference. Another thread is in cachefiles_read_copier: 1) object->work_lock is taken 2) an item is popped off the to_do list. 3) object->work_lock is dropped. 4) some processing is done on the item, and fscache_put_retrieval() is called, dropping a reference. Now if the this process in cachefiles_read_copier takes place *between* steps 3 and 4 in cachefiles_read_waiter, a reference will be dropped before it is taken, which leads to the objects reference count hitting zero, which leads to lifecycle events for the object happening too soon, leading to the assertion failure later on. (This is simplified and clarified from the original upstream analysis for this patch at https://www.redhat.com/archives/linux- cachefs/2018-February/msg1.html and from a similar patch with a different approach to fixing the bug at https://www.redhat.com/archives/linux-cachefs/2017-June/msg2.html) [Fix] Move fscache_enqueue_retrieval under the lock in cachefiles_read_waiter. This means that the object cannot be popped off the to_do list until it is in a fully consistent state with the reference taken. [Testcase] A user has run ~100 hours of NFS stress tests and not seen this bug recur. [Regression Potential] - Limited to fscache/cachefiles. - The change makes things more conservative (doing more under lock) so that's reassuring. - There may be performance impacts but none have been observed so far. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774336/+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 1775316] Re: add_key04 in LTP syscall test cause kernel oops (NULL pointer dereference) with T kernel
** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Trusty) Status: New => Fix Committed ** 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/1775316 Title: add_key04 in LTP syscall test cause kernel oops (NULL pointer dereference) with T kernel Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Bug description: [SRU Justification] The assoc_array_insert_into_terminal_node function in lib/assoc_array.c in the Linux kernel before 4.13.11 mishandles node splitting, which allows local users to cause a denial of service (NULL pointer dereference and panic) via a crafted application, as demonstrated by the keyring key type, and key addition and link creation operations. The "add_key04" from the LTP syscall tests will cause kernel oops on a testing node with Trusty kernel installed. And it will make incoming ssh connection hang (bug 1775158) [Test Case] This issue can easily be reproduced with the "add_key04" test from the LTP syscall test suite. Steps (with root): 1. sudo apt-get install git -y 2. git clone --depth=1 https://github.com/linux-test-project/ltp.git 3. cd ltp 4. make autotools 5. ./configure 6. make; make install 7. /opt/ltp/testcases/bin/add_key04 Test result before the patch: ubuntu@amaura:/opt/ltp/testcases/bin$ sudo ./add_key04 tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s add_key04.c:82: FAIL: kernel oops while filling keyring Summary: passed 0 failed 1 skipped 0 warnings 0 [52399.298894] BUG: unable to handle kernel NULL pointer dereference at 0010 [52399.298918] IP: [] assoc_array_apply_edit+0x67/0x110 [52399.298938] PGD 800455a3a067 PUD 45725f067 PMD 0 [52399.298952] Oops: 0002 [#1] SMP [52399.298963] Modules linked in: cfg80211 ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi dm_crypt joydev hid_generic x86_pkg_temp_thermal coretemp kvm_intel kvm usbhid hid lpc_ich shpchp mac_hid crct10dif_pclmul crc32_pclmul i915_bdw ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper igb cryptd ahci dca ptp libahci pps_core intel_ips i2c_algo_bit drm_kms_helper video drm [52399.299100] CPU: 7 PID: 9559 Comm: add_key04 Not tainted 3.13.0-149-generic #199-Ubuntu [52399.299118] Hardware name: Intel Corporation S1200RP/S1200RP, BIOS S1200RP.86B.03.02.0003.070120151022 07/01/2015 [52399.299142] task: 880457b43000 ti: 88045a2e2000 task.ti: 88045a2e2000 [52399.299159] RIP: 0010:[] [] assoc_array_apply_edit+0x67/0x110 [52399.299182] RSP: 0018:88045a2e3df0 EFLAGS: 00010202 [52399.299194] RAX: 0010 RBX: 88045a2e3e78 RCX: [52399.299211] RDX: 88045a1d1741 RSI: 880456028880 RDI: 880456028800 [52399.299228] RBP: 88045a2e3df0 R08: 00016880 R09: 812dba97 [52399.299244] R10: 880460803c00 R11: ddf32900 R12: 880456f7f680 [52399.299261] R13: 88045a1d09c0 R14: R15: [52399.299278] FS: 7ff43fc39740() GS:8804704e() knlGS: [52399.299297] CS: 0010 DS: ES: CR0: 80050033 [52399.299311] CR2: 0010 CR3: 00045514c000 CR4: 00360770 [52399.299328] DR0: DR1: DR2: [52399.299344] DR3: DR6: fffe0ff0 DR7: 0400 [52399.299361] Stack: [52399.299366] 88045a2e3e08 812d7a33 88045a2e3e50 [52399.299387] 812d57a7 88045a1d0a30 88045a2e3e78 880456f7f681 [52399.299407] 3f01 880456f7f380 88045a1d09c0 880457b43000 [52399.299427] Call Trace: [52399.299436] [] __key_link+0x33/0x40 [52399.299450] [] __key_instantiate_and_link+0x87/0xf0 [52399.299467] [] key_create_or_update+0x32e/0x420 [52399.299482] [] SyS_add_key+0x110/0x210 [52399.299497] [] ? schedule_tail+0x5c/0xb0 [52399.299512] [] system_call_fastpath+0x1a/0x1f [52399.299526] Code: 48 85 d2 74 0a 48 8b 8f e8 00 00 00 48 89 0a 48 83 c0 08 48 39 f0 75 e4 48 8b 87 00 01 00 00 48 85 c0 74 0a 48 8b 97 08 01 00 00 <48> 89 10 48 8b 87 10 01 00 00 48 85 c0 74 0a 48 8b 97 18 01 00 [52399.299625] RIP [] assoc_array_apply_edit+0x67/0x110 [52399.299642] RSP [52399.299650] CR2: 0010 [52399.302015] ---[ end trace 0f3e00901ea9f056 ]--- Test result after the patch: $ sudo /opt/ltp/testcases/bin/add_key04 tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s add_key04.c:80:
[Kernel-packages] [Bug 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)
@cmeerw - that's great, thanks for confirming that! (I think I made a clean install of 18.04 but hadn't even thought of being able to use the old kernel if you've upgraded :) ) -- 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/1774950 Title: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47) Status in linux package in Ubuntu: Confirmed Bug description: I have installed Kubuntu 18.04 on 3 different machines (my friend's and my own) with no suspend problems but my HP Pavilion 11 x360 does not suspend. It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse, Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu 18.04. I have also tried suspend using a live USB of 18.04 on this machine and it fails in the same way, so does not appear to be caused by any additional programs that I had installed. By installing an older kernel (4.14) on Kubuntu 18.04 the suspend function works as expected. Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the suspend failure that freezes the machine and requires a hard reset. Correct behaviour is - Screen goes blank, fan goes off, power LED flashes to show machine is in suspend. Pressing power button triggers 'resume' function. What happens - Screen goes blank, fan stays on, power LED stays on. Machine stays in this state and does not respond to any keyboard interaction, mouse movement or power button presses. Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response. The only way to use the machine is to shut down by holding down the power button. Checking the logs suggests that the machine believes it is in suspend mode sleep [deep] when it isn't. Having to hard reset to get any response means that the kernel logs say no more than sleep [deep] pm-suspend also results in the same problems with kernels 4.15 and 4.16, but works fine with 4.14. It is curious that a machine that suspends fine on an earlier 4.14 kernel no longer works with 4.15 and above, whilst 3 other machines (including one with pretty similar hardware) do not exhibit this problem. There are only a handful of questions about it on the forums but at least 3 other people have the same problem: https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on- resuming-from-suspend https://askubuntu.com/questions/1041369/after-upgrading- from-17-10-ubuntu-18-04-wont-sleep-suspend I am attempting to round up anyone else with the same issue and point them to this bug report. My laptop is HP Pavilion x360 11-n013na Matalaks is Acer Aspire ES1-511 collisionTwo has XPS 9560 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+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 1766780] Re: test_250_config_security_perf_events_restrict in kernel security test failed with 4.15 KVM kernel
A test kernel could be found here (along with the patch for bug 1766774: http://people.canonical.com/~phlin/kernel/lp-1766774-1766780/ ** Description changed: - test_250_config_security_perf_events_restrict from the kernel security - test suite failed with 4.15.0-1008 KVM kernel. + == Justification == + In the Bionic KVM kernel, the CONFIG_FORTIFY_SOURCE and + CONFIG_SECURITY_PERF_EVENTS_RESTRICT were not set, they need to be enabled to + meet the security team's requirement. - FAIL: test_250_config_security_perf_events_restrict (__main__.KernelSecurityTest) - Ensure CONFIG_SECURITY_PERF_EVENTS_RESTRICT is set - -- - Traceback (most recent call last): - File "./test-kernel-security.py", line 2313, in test_250_config_security_perf_events_restrict - self.assertEqual(expected, self._test_config(config_name)) - AssertionError: True != False + == Test == + Before enabling the config, test case test_190_config_kernel_fortify and + test_250_config_security_perf_events_restrict will fail in the kernel + security testsuite for the kernel SRU regression test. + + It will pass with these two patches applied, tested on a KVM node. + + == Fix == + Set CONFIG_SECURITY_PERF_EVENTS_RESTRICT to "y". + Set CONFIG_FORTIFY_SOURCE to "y". + + == Regression Potential == + Minimal. + No code changes, just two config change without disabling any other configs. + + + test_250_config_security_perf_events_restrict from the kernel security test suite failed with 4.15.0-1008 KVM kernel. + + FAIL: test_250_config_security_perf_events_restrict (__main__.KernelSecurityTest) + Ensure CONFIG_SECURITY_PERF_EVENTS_RESTRICT is set + -- + Traceback (most recent call last): + File "./test-kernel-security.py", line 2313, in test_250_config_security_perf_events_restrict + self.assertEqual(expected, self._test_config(config_name)) + AssertionError: True != False The CONFIG_SECURITY_PERF_EVENTS_RESTRICT is not set. $ cat /boot/config-4.15.0-1008-kvm | grep CONFIG_SECURITY_PERF_EVENTS_RESTRICT # CONFIG_SECURITY_PERF_EVENTS_RESTRICT is not set ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1008-kvm 4.15.0-1008.8 ProcVersionSignature: User Name 4.15.0-1008.8-kvm 4.15.17 Uname: Linux 4.15.0-1008-kvm x86_64 NonfreeKernelModules: signpost ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed Apr 25 04:41:49 2018 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=C.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=C.UTF-8 + SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: == Justification == In the Bionic KVM kernel, the CONFIG_FORTIFY_SOURCE and CONFIG_SECURITY_PERF_EVENTS_RESTRICT were not set, they need to be enabled to meet the security team's requirement. == Test == Before enabling the config, test case test_190_config_kernel_fortify and test_250_config_security_perf_events_restrict will fail in the kernel security testsuite for the kernel SRU regression test. It will pass with these two patches applied, tested on a KVM node. == Fix == Set CONFIG_SECURITY_PERF_EVENTS_RESTRICT to "y". Set CONFIG_FORTIFY_SOURCE to "y". == Regression Potential == Minimal. No code changes, just two config change without disabling any other configs. + -- test_250_config_security_perf_events_restrict from the kernel security test suite failed with 4.15.0-1008 KVM kernel. FAIL: test_250_config_security_perf_events_restrict (__main__.KernelSecurityTest) Ensure CONFIG_SECURITY_PERF_EVENTS_RESTRICT is set -- Traceback (most recent call last): File "./test-kernel-security.py", line 2313, in test_250_config_security_perf_events_restrict self.assertEqual(expected, self._test_config(config_name)) AssertionError: True != False The CONFIG_SECURITY_PERF_EVENTS_RESTRICT is not set. $ cat /boot/config-4.15.0-1008-kvm | grep CONFIG_SECURITY_PERF_EVENTS_RESTRICT # CONFIG_SECURITY_PERF_EVENTS_RESTRICT is not set ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1008-kvm 4.15.0-1008.8 ProcVersionSignature: User Name 4.15.0-1008.8-kvm 4.15.17 Uname: Linux 4.15.0-1008-kvm x86_64 NonfreeKernelModules: signpost ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed Apr 25 04:41:49 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) ** Description
[Kernel-packages] [Bug 1766774] Re: test_190_config_kernel_fortify in kernel security test failed with 4.15 KVM kernel
A test kernel could be found here (along with the patch for bug 1766780: http://people.canonical.com/~phlin/kernel/lp-1766774-1766780/ ** No longer affects: qa-regression-testing ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux-kvm (Ubuntu) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: ubuntu-kernel-tests Status: New => In Progress ** Changed in: linux-kvm (Ubuntu) Status: New => In Progress ** Description changed: + == Justification == + In the Bionic KVM kernel, the CONFIG_FORTIFY_SOURCE and + CONFIG_SECURITY_PERF_EVENTS_RESTRICT were not set, they need to be enabled to + meet the security team's requirement. + + == Test == + Before enabling the config, test case test_190_config_kernel_fortify and + test_250_config_security_perf_events_restrict will fail in the kernel + security testsuite for the kernel SRU regression test. + + It will pass with these two patches applied, tested on a KVM node. + + == Fix == + Set CONFIG_SECURITY_PERF_EVENTS_RESTRICT to "y". + Set CONFIG_FORTIFY_SOURCE to "y". + + == Regression Potential == + Minimal. + No code changes, just two config change without disabling any other configs. + + Test test_190_config_kernel_fortify from the kernel security test suite failed with 4.15.0-1008 KVM kernel. - == - FAIL: test_190_config_kernel_fortify (__main__.KernelSecurityTest) - Ensure CONFIG_FORTIFY_SOURCE is set - -- - Traceback (most recent call last): - File "./test-kernel-security.py", line 2186, in test_190_config_kernel_fortify - self.assertTrue(self._test_config(config_name)) - AssertionError: False is not true - + == + FAIL: test_190_config_kernel_fortify (__main__.KernelSecurityTest) + Ensure CONFIG_FORTIFY_SOURCE is set + -- + Traceback (most recent call last): + File "./test-kernel-security.py", line 2186, in test_190_config_kernel_fortify + self.assertTrue(self._test_config(config_name)) + AssertionError: False is not true The CONFIG_FORTIFY_SOURCE is not set. $ cat /boot/config-4.15.0-1008-kvm | grep CONFIG_FORTIFY_SOURCE # CONFIG_FORTIFY_SOURCE is not set ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1008-kvm 4.15.0-1008.8 ProcVersionSignature: User Name 4.15.0-1008.8-kvm 4.15.17 Uname: Linux 4.15.0-1008-kvm x86_64 NonfreeKernelModules: signpost ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed Apr 25 04:28:13 2018 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=C.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=C.UTF-8 + SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: == Justification == In the Bionic KVM kernel, the CONFIG_FORTIFY_SOURCE and CONFIG_SECURITY_PERF_EVENTS_RESTRICT were not set, they need to be enabled to meet the security team's requirement. == Test == Before enabling the config, test case test_190_config_kernel_fortify and test_250_config_security_perf_events_restrict will fail in the kernel security testsuite for the kernel SRU regression test. It will pass with these two patches applied, tested on a KVM node. == Fix == Set CONFIG_SECURITY_PERF_EVENTS_RESTRICT to "y". Set CONFIG_FORTIFY_SOURCE to "y". == Regression Potential == Minimal. No code changes, just two config change without disabling any other configs. - Test test_190_config_kernel_fortify from the kernel security test suite - failed with 4.15.0-1008 KVM kernel. + -- + Test test_190_config_kernel_fortify from the kernel security test suite failed with 4.15.0-1008 KVM kernel. == FAIL: test_190_config_kernel_fortify (__main__.KernelSecurityTest) Ensure CONFIG_FORTIFY_SOURCE is set -- Traceback (most recent call last): File "./test-kernel-security.py", line 2186, in test_190_config_kernel_fortify self.assertTrue(self._test_config(config_name)) AssertionError: False is not true The CONFIG_FORTIFY_SOURCE is not set. $ cat /boot/config-4.15.0-1008-kvm | grep CONFIG_FORTIFY_SOURCE # CONFIG_FORTIFY_SOURCE is not set ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1008-kvm 4.15.0-1008.8 ProcVersionSignature: User Name 4.15.0-1008.8-kvm 4.15.17 Uname: Linux 4.15.0-1008-kvm x86_64 NonfreeKernelModules:
[Kernel-packages] [Bug 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)
Here's a more succinct update of how things seem to be progressing: - There's a bugzilla.kernel.org bug report that describes this same behaviour: https://bugzilla.kernel.org/show_bug.cgi?id=199025 - A kernel bisection between v4.14 and v4.15 gives this result: git bisect bad a192aa923b66a435aae56983c4912ee150bc9b32 is the first bad commit commit a192aa923b66a435aae56983c4912ee150bc9b32 Author: Rafael J. Wysocki Date: Mon Oct 16 03:29:55 2017 +0200 ACPI / LPSS: Consolidate runtime PM and system sleep handling Move the LPSS-specific code from acpi_lpss_runtime_suspend() and acpi_lpss_runtime_resume() into separate functions, acpi_lpss_suspend() and acpi_lpss_resume(), respectively, and make acpi_lpss_suspend_late() and acpi_lpss_resume_early() use them too in order to unify the runtime PM and system sleep handling in the LPSS driver. Signed-off-by: Rafael J. Wysocki Acked-by: Greg Kroah-Hartman Reviewed-by: Ulf Hansson :04 04 b4ef369c698a10cec8d6224fdc3b8f287eb853b1 20327192ca09ecc0cf0b24b62fdb915ea303b988 M drivers - from an email list I saw that @kaihengfeng has contacted a kernel.org developer who has written a patch to test. - I don't know if I'm supposed to test this patch (i might just be added to the email list because I opened this bug report) or whether Kai-Heng Feng will post here to let others try a kernel with the patch applied and see if it works. -- 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/1774950 Title: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47) Status in linux package in Ubuntu: Confirmed Bug description: I have installed Kubuntu 18.04 on 3 different machines (my friend's and my own) with no suspend problems but my HP Pavilion 11 x360 does not suspend. It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse, Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu 18.04. I have also tried suspend using a live USB of 18.04 on this machine and it fails in the same way, so does not appear to be caused by any additional programs that I had installed. By installing an older kernel (4.14) on Kubuntu 18.04 the suspend function works as expected. Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the suspend failure that freezes the machine and requires a hard reset. Correct behaviour is - Screen goes blank, fan goes off, power LED flashes to show machine is in suspend. Pressing power button triggers 'resume' function. What happens - Screen goes blank, fan stays on, power LED stays on. Machine stays in this state and does not respond to any keyboard interaction, mouse movement or power button presses. Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response. The only way to use the machine is to shut down by holding down the power button. Checking the logs suggests that the machine believes it is in suspend mode sleep [deep] when it isn't. Having to hard reset to get any response means that the kernel logs say no more than sleep [deep] pm-suspend also results in the same problems with kernels 4.15 and 4.16, but works fine with 4.14. It is curious that a machine that suspends fine on an earlier 4.14 kernel no longer works with 4.15 and above, whilst 3 other machines (including one with pretty similar hardware) do not exhibit this problem. There are only a handful of questions about it on the forums but at least 3 other people have the same problem: https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on- resuming-from-suspend https://askubuntu.com/questions/1041369/after-upgrading- from-17-10-ubuntu-18-04-wont-sleep-suspend I am attempting to round up anyone else with the same issue and point them to this bug report. My laptop is HP Pavilion x360 11-n013na Matalaks is Acer Aspire ES1-511 collisionTwo has XPS 9560 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+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 1766780] Re: test_250_config_security_perf_events_restrict in kernel security test failed with 4.15 KVM kernel
** Description changed: == Justification == In the Bionic KVM kernel, the CONFIG_FORTIFY_SOURCE and CONFIG_SECURITY_PERF_EVENTS_RESTRICT were not set, they need to be enabled to meet the security team's requirement. == Test == Before enabling the config, test case test_190_config_kernel_fortify and test_250_config_security_perf_events_restrict will fail in the kernel security testsuite for the kernel SRU regression test. It will pass with these two patches applied, tested on a KVM node. == Fix == Set CONFIG_SECURITY_PERF_EVENTS_RESTRICT to "y". Set CONFIG_FORTIFY_SOURCE to "y". == Regression Potential == Minimal. - No code changes, just two config change without disabling any other configs. + No code changes, just two config changes without disabling any other configs. BugLink: https://bugs.launchpad.net/bugs/1766780 BugLink: https://bugs.launchpad.net/bugs/1766774 -- test_250_config_security_perf_events_restrict from the kernel security test suite failed with 4.15.0-1008 KVM kernel. FAIL: test_250_config_security_perf_events_restrict (__main__.KernelSecurityTest) Ensure CONFIG_SECURITY_PERF_EVENTS_RESTRICT is set -- Traceback (most recent call last): File "./test-kernel-security.py", line 2313, in test_250_config_security_perf_events_restrict self.assertEqual(expected, self._test_config(config_name)) AssertionError: True != False The CONFIG_SECURITY_PERF_EVENTS_RESTRICT is not set. $ cat /boot/config-4.15.0-1008-kvm | grep CONFIG_SECURITY_PERF_EVENTS_RESTRICT # CONFIG_SECURITY_PERF_EVENTS_RESTRICT is not set ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1008-kvm 4.15.0-1008.8 ProcVersionSignature: User Name 4.15.0-1008.8-kvm 4.15.17 Uname: Linux 4.15.0-1008-kvm x86_64 NonfreeKernelModules: signpost ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed Apr 25 04:41:49 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1766780 Title: test_250_config_security_perf_events_restrict in kernel security test failed with 4.15 KVM kernel Status in ubuntu-kernel-tests: In Progress Status in linux-kvm package in Ubuntu: In Progress Bug description: == Justification == In the Bionic KVM kernel, the CONFIG_FORTIFY_SOURCE and CONFIG_SECURITY_PERF_EVENTS_RESTRICT were not set, they need to be enabled to meet the security team's requirement. == Test == Before enabling the config, test case test_190_config_kernel_fortify and test_250_config_security_perf_events_restrict will fail in the kernel security testsuite for the kernel SRU regression test. It will pass with these two patches applied, tested on a KVM node. == Fix == Set CONFIG_SECURITY_PERF_EVENTS_RESTRICT to "y". Set CONFIG_FORTIFY_SOURCE to "y". == Regression Potential == Minimal. No code changes, just two config changes without disabling any other configs. BugLink: https://bugs.launchpad.net/bugs/1766780 BugLink: https://bugs.launchpad.net/bugs/1766774 -- test_250_config_security_perf_events_restrict from the kernel security test suite failed with 4.15.0-1008 KVM kernel. FAIL: test_250_config_security_perf_events_restrict (__main__.KernelSecurityTest) Ensure CONFIG_SECURITY_PERF_EVENTS_RESTRICT is set -- Traceback (most recent call last): File "./test-kernel-security.py", line 2313, in test_250_config_security_perf_events_restrict self.assertEqual(expected, self._test_config(config_name)) AssertionError: True != False The CONFIG_SECURITY_PERF_EVENTS_RESTRICT is not set. $ cat /boot/config-4.15.0-1008-kvm | grep CONFIG_SECURITY_PERF_EVENTS_RESTRICT # CONFIG_SECURITY_PERF_EVENTS_RESTRICT is not set ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1008-kvm 4.15.0-1008.8 ProcVersionSignature: User Name 4.15.0-1008.8-kvm 4.15.17 Uname: Linux 4.15.0-1008-kvm x86_64 NonfreeKernelModules: signpost ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed Apr 25 04:41:49 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1766780/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1766774] Re: test_190_config_kernel_fortify in kernel security test failed with 4.15 KVM kernel
** Description changed: == Justification == In the Bionic KVM kernel, the CONFIG_FORTIFY_SOURCE and CONFIG_SECURITY_PERF_EVENTS_RESTRICT were not set, they need to be enabled to meet the security team's requirement. == Test == Before enabling the config, test case test_190_config_kernel_fortify and test_250_config_security_perf_events_restrict will fail in the kernel security testsuite for the kernel SRU regression test. It will pass with these two patches applied, tested on a KVM node. == Fix == Set CONFIG_SECURITY_PERF_EVENTS_RESTRICT to "y". Set CONFIG_FORTIFY_SOURCE to "y". == Regression Potential == Minimal. - No code changes, just two config change without disabling any other configs. + No code changes, just two config changes without disabling any other configs. BugLink: https://bugs.launchpad.net/bugs/1766780 BugLink: https://bugs.launchpad.net/bugs/1766774 -- Test test_190_config_kernel_fortify from the kernel security test suite failed with 4.15.0-1008 KVM kernel. == FAIL: test_190_config_kernel_fortify (__main__.KernelSecurityTest) Ensure CONFIG_FORTIFY_SOURCE is set -- Traceback (most recent call last): File "./test-kernel-security.py", line 2186, in test_190_config_kernel_fortify self.assertTrue(self._test_config(config_name)) AssertionError: False is not true The CONFIG_FORTIFY_SOURCE is not set. $ cat /boot/config-4.15.0-1008-kvm | grep CONFIG_FORTIFY_SOURCE # CONFIG_FORTIFY_SOURCE is not set ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1008-kvm 4.15.0-1008.8 ProcVersionSignature: User Name 4.15.0-1008.8-kvm 4.15.17 Uname: Linux 4.15.0-1008-kvm x86_64 NonfreeKernelModules: signpost ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed Apr 25 04:28:13 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1766774 Title: test_190_config_kernel_fortify in kernel security test failed with 4.15 KVM kernel Status in ubuntu-kernel-tests: In Progress Status in linux-kvm package in Ubuntu: In Progress Bug description: == Justification == In the Bionic KVM kernel, the CONFIG_FORTIFY_SOURCE and CONFIG_SECURITY_PERF_EVENTS_RESTRICT were not set, they need to be enabled to meet the security team's requirement. == Test == Before enabling the config, test case test_190_config_kernel_fortify and test_250_config_security_perf_events_restrict will fail in the kernel security testsuite for the kernel SRU regression test. It will pass with these two patches applied, tested on a KVM node. == Fix == Set CONFIG_SECURITY_PERF_EVENTS_RESTRICT to "y". Set CONFIG_FORTIFY_SOURCE to "y". == Regression Potential == Minimal. No code changes, just two config changes without disabling any other configs. BugLink: https://bugs.launchpad.net/bugs/1766780 BugLink: https://bugs.launchpad.net/bugs/1766774 -- Test test_190_config_kernel_fortify from the kernel security test suite failed with 4.15.0-1008 KVM kernel. == FAIL: test_190_config_kernel_fortify (__main__.KernelSecurityTest) Ensure CONFIG_FORTIFY_SOURCE is set -- Traceback (most recent call last): File "./test-kernel-security.py", line 2186, in test_190_config_kernel_fortify self.assertTrue(self._test_config(config_name)) AssertionError: False is not true The CONFIG_FORTIFY_SOURCE is not set. $ cat /boot/config-4.15.0-1008-kvm | grep CONFIG_FORTIFY_SOURCE # CONFIG_FORTIFY_SOURCE is not set ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1008-kvm 4.15.0-1008.8 ProcVersionSignature: User Name 4.15.0-1008.8-kvm 4.15.17 Uname: Linux 4.15.0-1008-kvm x86_64 NonfreeKernelModules: signpost ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed Apr 25 04:28:13 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1766774/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1776358] Re: linux-kvm: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package 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 -- kernel-stable-master-bug: 1776352 + kernel-stable-phase:Packaging + kernel-stable-phase-changed:Tuesday, 12. June 2018 11:04 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 -- kernel-stable-master-bug: 1776352 - kernel-stable-phase:Packaging - kernel-stable-phase-changed:Tuesday, 12. June 2018 11:04 UTC + phase: Packaging -- 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/1776358 Title: linux-kvm: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 -- kernel-stable-master-bug: 1776352 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776358/+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 1776351] Re: linux-lts-trusty: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package 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 -- kernel-stable-master-bug: 1776350 + kernel-stable-phase:Packaging + kernel-stable-phase-changed:Tuesday, 12. June 2018 11:02 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 -- kernel-stable-master-bug: 1776350 - kernel-stable-phase:Packaging - kernel-stable-phase-changed:Tuesday, 12. June 2018 11:02 UTC + phase: Packaging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1776351 Title: linux-lts-trusty: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: 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: 1776350 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776351/+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 1776356] Re: linux-aws: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package 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 -- kernel-stable-master-bug: 1776352 + kernel-stable-phase:Packaging + kernel-stable-phase-changed:Tuesday, 12. June 2018 11: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 -- swm properties -- kernel-stable-master-bug: 1776352 - kernel-stable-phase:Packaging - kernel-stable-phase-changed:Tuesday, 12. June 2018 11:03 UTC + phase: Packaging -- 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/1776356 Title: linux-aws: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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-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 -- kernel-stable-master-bug: 1776352 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776356/+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 1722478] Re: Two-finger scrolling no longer works after resuming from suspend
Ubuntu 18.04 kernel 4.15.0-22-generic T440p - same problem with two- finger scrolling. Will wait until this is fixed in an update ... how long will that be? -- 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/1722478 Title: Two-finger scrolling no longer works after resuming from suspend Status in Linux: Unknown Status in linux package in Ubuntu: Incomplete Bug description: I own a Thinkpad T440p onto which I have had Debian 9 running without hardware issues. I have recently installed Ubuntu 17.10 final beta to test it out, but two-finger scrolling does not work at the moment. It used to work out-of-the-box from the final beta iso, but a subsequent update broke it. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghislain 10620 F pulseaudio /dev/snd/controlC0: ghislain 10620 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 10 09:20:01 2017 HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e InstallationDate: Installed on 2017-10-05 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: LENOVO 20AN00C1UK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GLET83WW (2.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AN00C1UK dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AN00C1UK dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1722478/+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 1776349] Re: linux: -proposed tracker
** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776349 Title: linux: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-lbm series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 Precise: New 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: derivatives: To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776349/+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 1776352] Re: linux: 4.4.0-129.155 -proposed tracker
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776352 Title: linux: 4.4.0-129.155 -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: 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-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: New 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 1776353 (linux-aws), bug 1776355 (linux-lts-xenial) derivatives: bug 1776356 (linux-aws), bug 1776357 (linux-euclid), bug 1776358 (linux-kvm), bug 1776359 (linux-raspi2), bug 1776361 (linux-snapdragon) To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776352/+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 1776338] Re: linux: -proposed tracker
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776338 Title: linux: -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: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 Bionic: New 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 1776346 (linux-azure), bug 1776347 (linux-azure-edge), bug 1776348 (linux-hwe-edge) derivatives: bug 1776339 (linux-raspi2), bug 1776340 (linux-oem), bug 1776341 (linux-aws), bug 1776342 (linux-azure), bug 1776344 (linux-gcp), bug 1776345 (linux-kvm) To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776338/+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 1776350] Re: linux: 3.13.0-152.202 -proposed tracker
** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776350 Title: linux: 3.13.0-152.202 -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: 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 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 Trusty: New 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 1776351 (linux-lts-trusty) derivatives: To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776350/+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 1776337] Re: linux-oem: -proposed tracker
** Also affects: linux-oem (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1776337 Title: linux-oem: -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: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Xenial: New 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: 1776333 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776337/+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 1776352] Re: linux: 4.4.0-129.155 -proposed tracker
** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776352 Title: linux: 4.4.0-129.155 -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: 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-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 1776353 (linux-aws), bug 1776355 (linux-lts-xenial) derivatives: bug 1776356 (linux-aws), bug 1776357 (linux-euclid), bug 1776358 (linux-kvm), bug 1776359 (linux-raspi2), bug 1776361 (linux-snapdragon) To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776352/+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 1776353] Re: linux-aws: -proposed tracker
** Also affects: linux-aws (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux-aws (Ubuntu Trusty) Status: New => Confirmed -- 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/1776353 Title: linux-aws: -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: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 Trusty: 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: 1776352 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776353/+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 1776350] Re: linux: 3.13.0-152.202 -proposed tracker
** Changed in: linux (Ubuntu Trusty) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776350 Title: linux: 3.13.0-152.202 -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: 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 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 Trusty: 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 1776351 (linux-lts-trusty) derivatives: To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776350/+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 1776356] Re: linux-aws: -proposed tracker
** Also affects: linux-aws (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux-aws (Ubuntu Xenial) Status: New => Confirmed -- 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/1776356 Title: linux-aws: -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: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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-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 -- kernel-stable-master-bug: 1776352 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776356/+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 1776351] Re: linux-lts-trusty: -proposed tracker
** Also affects: linux-lts-trusty (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: linux-lts-trusty (Ubuntu Precise) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1776351 Title: linux-lts-trusty: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: 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: 1776350 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776351/+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 1776358] Re: linux-kvm: -proposed tracker
** Also affects: linux-kvm (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux-kvm (Ubuntu Xenial) Status: New => Confirmed -- 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/1776358 Title: linux-kvm: -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: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 -- kernel-stable-master-bug: 1776352 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776358/+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 1776349] Re: linux: -proposed tracker
** Changed in: linux (Ubuntu Precise) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776349 Title: linux: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-lbm series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 Precise: 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: derivatives: To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776349/+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 1776445] [NEW] nvidia-dkms-390 390.48-0ubuntu3: nvidia kernel module failed to build
Public bug reported: I am a noob, so a detailed explanation of the problem and steps and procedures of fixing it would be appreciated thanks. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-dkms-390 390.48-0ubuntu3 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 DKMSBuildLog: DKMS make.log for nvidia-390.48 for kernel 4.15.0-23-generic (x86_64) Tue Jun 12 09:56:49 WAT 2018 make: *** No rule to make target 'modules'. Stop. DKMSKernelVersion: 4.15.0-23-generic Date: Tue Jun 12 09:56:50 2018 InstallationDate: Installed on 2018-04-30 (42 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageVersion: 390.48-0ubuntu3 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: nvidia-graphics-drivers-390 Title: nvidia-dkms-390 390.48-0ubuntu3: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- 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/1776445 Title: nvidia-dkms-390 390.48-0ubuntu3: nvidia kernel module failed to build Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: I am a noob, so a detailed explanation of the problem and steps and procedures of fixing it would be appreciated thanks. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-dkms-390 390.48-0ubuntu3 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 DKMSBuildLog: DKMS make.log for nvidia-390.48 for kernel 4.15.0-23-generic (x86_64) Tue Jun 12 09:56:49 WAT 2018 make: *** No rule to make target 'modules'. Stop. DKMSKernelVersion: 4.15.0-23-generic Date: Tue Jun 12 09:56:50 2018 InstallationDate: Installed on 2018-04-30 (42 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageVersion: 390.48-0ubuntu3 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: nvidia-graphics-drivers-390 Title: nvidia-dkms-390 390.48-0ubuntu3: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1776445/+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 1776443] Re: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck
brian@bacchus:~$ uname -a Linux bacchus 4.15.0-22-lowlatency #24-Ubuntu SMP PREEMPT Wed May 16 17:09:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux brian@bacchus:~$ lsb_release -a LSB Version: core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch Distributor ID: Ubuntu Description:Ubuntu 18.04 LTS Release:18.04 Codename: bionic lspci:- 16:00.0 Network controller: Intel Corporation Wireless 3165 (rev 79) ii linux-firmware1.173.1 all Firmware for Linux kernel drivers brian@bacchus:/lib/firmware$ ls -l | grep iwlwifi | grep 7265D lrwxrwxrwx 1 root root 21 Nov 18 2017 iwlwifi-7265D-10.ucode -> iwlwifi-7265-10.ucode -rw-r--r-- 1 root root 1002800 Mar 30 2017 iwlwifi-7265D-12.ucode -rw-r--r-- 1 root root 1008692 Mar 30 2017 iwlwifi-7265D-13.ucode -rw-r--r-- 1 root root 1384500 Mar 30 2017 iwlwifi-7265D-16.ucode -rw-r--r-- 1 root root 1383604 Nov 18 2017 iwlwifi-7265D-17.ucode -rw-r--r-- 1 root root 1385368 Nov 18 2017 iwlwifi-7265D-21.ucode -rw-r--r-- 1 root root 1028376 Apr 25 00:23 iwlwifi-7265D-22.ucode -rw-r--r-- 1 root root 1032740 Dec 6 2017 iwlwifi-7265D-27.ucode -rw-r--r-- 1 root root 1036432 May 19 04:07 iwlwifi-7265D-29.ucode ** Attachment added: "Most recent log with firmware register dump and driver stack trace" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1776443/+attachment/5151672/+files/bacchus-wifi-hang-log-10-telstraAP-2-4g -- 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/1776443 Title: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck Status in linux-firmware package in Ubuntu: New Bug description: dell inspiron 15 3565 and intel 3165. Difficult to report when wifi is down! Happens sometimes after a few minutes, never more than 30 minutes. Easy to capture journalctl when the network connection hangs. Intel fails on 2.4 GHz or 5 GHz, using several different AP's. The same system runs stable and perfect with a USB dongle Realtek RTL8188CUS, but I have to blacklist iwlwifi in /etc/modprobe.d/modprobe.conf to prevent iwlwifi hanging all network activity while simply scanning and not connected to an AP. I've had similar problems with this system under 17.10, but it has become more reproducible under 18.04. I've back-levelled the driver as far as possible, but they all hang the network. Because version 29 firmware is the latest in the bionic repository, and also on the intel support web site, I won't confuse matters by reporting earlier ubuntu kernels or iwlwifi versions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1776443/+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 1776443] Re: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck
I'm pretty sure the same hardware adapter and firmware is supporting bluetooth for my logitech mouse. ** Tags added: wifi ** Tags added: intel -- 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/1776443 Title: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck Status in linux-firmware package in Ubuntu: New Bug description: dell inspiron 15 3565 and intel 3165. Difficult to report when wifi is down! Happens sometimes after a few minutes, never more than 30 minutes. Easy to capture journalctl when the network connection hangs. Intel fails on 2.4 GHz or 5 GHz, using several different AP's. The same system runs stable and perfect with a USB dongle Realtek RTL8188CUS, but I have to blacklist iwlwifi in /etc/modprobe.d/modprobe.conf to prevent iwlwifi hanging all network activity while simply scanning and not connected to an AP. I've had similar problems with this system under 17.10, but it has become more reproducible under 18.04. I've back-levelled the driver as far as possible, but they all hang the network. Because version 29 firmware is the latest in the bionic repository, and also on the intel support web site, I won't confuse matters by reporting earlier ubuntu kernels or iwlwifi versions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1776443/+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 1766780] Re: test_250_config_security_perf_events_restrict in kernel security test failed with 4.15 KVM kernel
** Changed in: linux-kvm (Ubuntu) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** No longer affects: qa-regression-testing ** Changed in: ubuntu-kernel-tests Status: New => In Progress ** Changed in: linux-kvm (Ubuntu) Status: New => In Progress -- 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/1766780 Title: test_250_config_security_perf_events_restrict in kernel security test failed with 4.15 KVM kernel Status in ubuntu-kernel-tests: In Progress Status in linux-kvm package in Ubuntu: In Progress Bug description: test_250_config_security_perf_events_restrict from the kernel security test suite failed with 4.15.0-1008 KVM kernel. FAIL: test_250_config_security_perf_events_restrict (__main__.KernelSecurityTest) Ensure CONFIG_SECURITY_PERF_EVENTS_RESTRICT is set -- Traceback (most recent call last): File "./test-kernel-security.py", line 2313, in test_250_config_security_perf_events_restrict self.assertEqual(expected, self._test_config(config_name)) AssertionError: True != False The CONFIG_SECURITY_PERF_EVENTS_RESTRICT is not set. $ cat /boot/config-4.15.0-1008-kvm | grep CONFIG_SECURITY_PERF_EVENTS_RESTRICT # CONFIG_SECURITY_PERF_EVENTS_RESTRICT is not set ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1008-kvm 4.15.0-1008.8 ProcVersionSignature: User Name 4.15.0-1008.8-kvm 4.15.17 Uname: Linux 4.15.0-1008-kvm x86_64 NonfreeKernelModules: signpost ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed Apr 25 04:41:49 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1766780/+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 1776389] Re: [Ubuntu 1804][boston][ixgbe] EEH causes kernel BUG at /build/linux-jWa1Fv/linux-4.15.0/drivers/pci/msi.c:352 (i2S)
** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Status: New => Triaged ** Changed in: ubuntu-power-systems Importance: Undecided => High ** Changed in: ubuntu-power-systems Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Tags added: triage-g -- 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/1776389 Title: [Ubuntu 1804][boston][ixgbe] EEH causes kernel BUG at /build/linux- jWa1Fv/linux-4.15.0/drivers/pci/msi.c:352 (i2S) Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Bug description: == Comment: #0 - ABDUL HALEEM <> - 2018-02-16 08:26:15 == Problem: Injecting error multiple times causes kernel crash. echo 0x0:1:4:0x60800:0xfff8 > /sys/kernel/debug/powerpc/PCI/err_injct EEH: PHB#0 failure detected, location: N/A EEH: PHB#0-PE#0 has failed 6 times in the last hour and has been permanently disabled. EEH: Unable to recover from failure from PHB#0-PE#0. Please try reseating or replacing it ixgbe :01:00.1: Adapter removed kernel BUG at /build/linux-jWa1Fv/linux-4.15.0/drivers/pci/msi.c:352! Oops: Exception in kernel mode, sig: 5 [#1] LE SMP NR_CPUS=2048 NUMA PowerNV Modules linked in: rpcsec_gss_krb5 nfsv4 nfs fscache joydev input_leds mac_hid idt_89hpesx ofpart ipmi_powernv cmdlinepart ipmi_devintf ipmi_msghandler at24 powernv_flash mtd opal_prd ibmpowernv uio_pdrv_genirq vmx_crypto uio sch_fq_codel nfsd auth_rpcgss nfs_acl lockd grace sunrpc ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure scsi_transport_sas qla2xxx ast hid_generic ttm drm_kms_helper ixgbe syscopyarea usbhid igb sysfillrect sysimgblt nvme_fc fb_sys_fops hid nvme_fabrics crct10dif_vpmsum crc32c_vpmsum drm i40e scsi_transport_fc aacraid i2c_algo_bit mdio CPU: 28 PID: 972 Comm: eehd Not tainted 4.15.0-10-generic #11-Ubuntu NIP: c077f080 LR: c077f070 CTR: c00aac30 REGS: c00ff1deb5a0 TRAP: 0700 Not tainted (4.15.0-10-generic) MSR: 90029033 CR: 24002822 XER: 2004 CFAR: c018bddc SOFTE: 1 GPR00: c077f070 c00ff1deb820 c16ea600 c00fbb5fac00 GPR04: 02c5 GPR08: c00fbb5fac00 0001 c00fec617a00 c00fdfd86488 GPR12: 0040 c7a33400 c0138be8 c00ff90ec1c0 GPR16: GPR20: c0f48d10 GPR24: c0f48ce8 c000200e4fcf4000 c00fc6900b18 c000200e4fcf4000 GPR28: c000200e4fcf4288 c00810624480 c00fbb633ea0 NIP [c077f080] free_msi_irqs+0xa0/0x260 LR [c077f070] free_msi_irqs+0x90/0x260 Call Trace: [c00ff1deb820] [c077f070] free_msi_irqs+0x90/0x260 (unreliable) [c00ff1deb880] [c077fa68] pci_disable_msix+0x128/0x170 [c00ff1deb8c0] [c0081060b5c8] ixgbe_reset_interrupt_capability+0x90/0xd0 [ixgbe] [c00ff1deb8f0] [c008105d52f4] ixgbe_remove+0xec/0x240 [ixgbe] [c00ff1deb990] [c07670ec] pci_device_remove+0x6c/0x110 [c00ff1deb9d0] [c085d194] device_release_driver_internal+0x224/0x310 [c00ff1deba20] [c075b398] pci_stop_bus_device+0x98/0xe0 [c00ff1deba60] [c075b588] pci_stop_and_remove_bus_device+0x28/0x40 [c00ff1deba90] [c005e1d0] pci_hp_remove_devices+0x90/0x130 [c00ff1debb20] [c005e184] pci_hp_remove_devices+0x44/0x130 [c00ff1debbb0] [c003ec04] eeh_handle_normal_event+0x134/0x580 [c00ff1debc60] [c003f160] eeh_handle_event+0x30/0x338 [c00ff1debd10] [c003f830] eeh_event_handler+0x140/0x200 [c00ff1debdc0] [c0138d88] kthread+0x1a8/0x1b0 [c00ff1debe30] [c000b528] ret_from_kernel_thread+0x5c/0xb4 Instruction dump: 419effe0 3bc0 480c 6042 807f0010 7c7e1a14 78630020 4ba0cd3d 6000 e9430158 312a 7d295110 <0b09> 813f0014 395e0001 7d5e07b4 ---[ end trace 23c446a470e60864 ]--- ixgbe :01:00.0: Adapter removed Sending IPI to other CPUs OPAL: Switch to big-endian OS OPAL: Switch to little-endian OS PHB#[0:0]: eeh_freeze_clear on fenced PHB ---uname output--- Linux ltciofvtr-bostonlc1 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:21:52 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = Boston-LC :00:00.0 PCI bridge [0604]: IBM Device [1014:04c1]
[Kernel-packages] [Bug 1776333] Re: linux: 4.13.0-46.51 -proposed tracker
** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776333 Title: linux: 4.13.0-46.51 -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: 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 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 Artful: New 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 1776335 (linux-gcp), bug 1776336 (linux-hwe), bug 1776337 (linux-oem) derivatives: bug 1776334 (linux-raspi2) To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776333/+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 1776443] [NEW] iwlwifi-29 kernel timeout queue active on fifo 2 and stuck
Public bug reported: dell inspiron 15 3565 and intel 3165. Difficult to report when wifi is down! Happens sometimes after a few minutes, never more than 30 minutes. Easy to capture journalctl when the network connection hangs. Intel fails on 2.4 GHz or 5 GHz, using several different AP's. The same system runs stable and perfect with a USB dongle Realtek RTL8188CUS, but I have to blacklist iwlwifi in /etc/modprobe.d/modprobe.conf to prevent iwlwifi hanging all network activity while simply scanning and not connected to an AP. I've had similar problems with this system under 17.10, but it has become more reproducible under 18.04. I've back-levelled the driver as far as possible, but they all hang the network. Because version 29 firmware is the latest in the bionic repository, and also on the intel support web site, I won't confuse matters by reporting earlier ubuntu kernels or iwlwifi versions ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1776443 Title: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck Status in linux-firmware package in Ubuntu: New Bug description: dell inspiron 15 3565 and intel 3165. Difficult to report when wifi is down! Happens sometimes after a few minutes, never more than 30 minutes. Easy to capture journalctl when the network connection hangs. Intel fails on 2.4 GHz or 5 GHz, using several different AP's. The same system runs stable and perfect with a USB dongle Realtek RTL8188CUS, but I have to blacklist iwlwifi in /etc/modprobe.d/modprobe.conf to prevent iwlwifi hanging all network activity while simply scanning and not connected to an AP. I've had similar problems with this system under 17.10, but it has become more reproducible under 18.04. I've back-levelled the driver as far as possible, but they all hang the network. Because version 29 firmware is the latest in the bionic repository, and also on the intel support web site, I won't confuse matters by reporting earlier ubuntu kernels or iwlwifi versions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1776443/+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
Confirming this is still an issue for me after updating my bionic installation to linux-image-4.15.0-23-generic 4.15.0-23.25, while https://people.canonical.com/~khfeng/lp1752772-r8169-intx/ worked fine in recent weeks. -- 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: Confirmed 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) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.80 dmi.board.name: H55M-LE dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias:
[Kernel-packages] [Bug 1776352] Re: linux: 4.4.0-129.155 -proposed tracker
** Summary changed: - linux: -proposed tracker + linux: 4.4.0-129.155 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** 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) => Khaled El Mously (kmously) ** 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) => Khaled El Mously (kmously) -- 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/1776352 Title: linux: 4.4.0-129.155 -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: 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-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: New 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 1776353 (linux-aws), bug 1776355 (linux-lts-xenial) derivatives: bug 1776356 (linux-aws), bug 1776357 (linux-euclid), bug 1776358 (linux-kvm), bug 1776359 (linux-raspi2), bug 1776361 (linux-snapdragon) To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776352/+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 1776350] Re: linux: 3.13.0-152.202 -proposed tracker
** Summary changed: - linux: -proposed tracker + linux: 3.13.0-152.202 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** 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) => Khaled El Mously (kmously) ** 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) => Khaled El Mously (kmously) -- 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/1776350 Title: linux: 3.13.0-152.202 -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: 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 upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid 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 1776351 (linux-lts-trusty) derivatives: To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776350/+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 1776335] Re: linux-gcp: 4.13.0-1020.24 -proposed tracker
** Also affects: linux-gcp (Ubuntu Xenial) Importance: Undecided Status: New -- 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/1776335 Title: linux-gcp: 4.13.0-1020.24 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: 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-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: New 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: 1776333 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776335/+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 1776449] [NEW] bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1: bcmwl kernel module failed to build
Public bug reported: ndswrapper ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1 ProcVersionSignature: Ubuntu 4.15.0-15.16~16.04.1-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 DKMSKernelVersion: 4.15.0-23-generic Date: Tue Jun 12 14:52:04 2018 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.1:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2: error: implicit declaration of function ‘init_timer’ [-Werror=implicit-function-declaration] InstallationDate: Installed on 2016-09-21 (629 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.1 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1776449 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: New Bug description: ndswrapper ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1 ProcVersionSignature: Ubuntu 4.15.0-15.16~16.04.1-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 DKMSKernelVersion: 4.15.0-23-generic Date: Tue Jun 12 14:52:04 2018 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.1:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2: error: implicit declaration of function ‘init_timer’ [-Werror=implicit-function-declaration] InstallationDate: Installed on 2016-09-21 (629 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.1 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1776449/+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 1776335] Re: linux-gcp: 4.13.0-1020.24 -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-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1776335 Title: linux-gcp: 4.13.0-1020.24 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: 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-gcp package in Ubuntu: Invalid 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: 1776333 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776335/+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 1776407] [NEW] intel_do_flush_locked failed:Bad address
Public bug reported: when my app run on about 3 days, it exits and throws error info: "intel_do_flush_locked failed:bad address". this information is throwed by OpenGL(mesa). relations: app -> SDL -> OpenGL(mesa) -> libdrm -> kernel frequency: often kernel version:Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17GNU/Linux meas version: 17.2.8 libdrm : 2.4.83 I think it is a kernel bug because the bad address is meaning error code "-EFALUT". ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776407 Title: intel_do_flush_locked failed:Bad address Status in linux package in Ubuntu: New Bug description: when my app run on about 3 days, it exits and throws error info: "intel_do_flush_locked failed:bad address". this information is throwed by OpenGL(mesa). relations: app -> SDL -> OpenGL(mesa) -> libdrm -> kernel frequency: often kernel version:Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17GNU/Linux meas version: 17.2.8 libdrm : 2.4.83 I think it is a kernel bug because the bad address is meaning error code "-EFALUT". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776407/+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 1776376] Re: Intel 9462 bluetooth and wifi doesn't work
I updated to kernel 4.15.0.23 and upgraded to firmware 1.157.19,but wireless network and bluetooth does still not work,so did the ethernet.I need your help. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776376 Title: Intel 9462 bluetooth and wifi doesn't work Status in linux package in Ubuntu: Confirmed Bug description: Besides the issue mentioned above,the keyboard is not completely suitable. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: boot/vmlinuz-4.4.0-21-generic] ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gjd1940 F pulseaudio CurrentDesktop: Unity Date: Tue Jun 12 10:33:31 2018 HibernationDevice: RESUME=UUID=a93c190f-117c-44c6-8595-37cc0499c28b InstallationDate: Installed on 2018-06-11 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: Dell Inc. G3 3579 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=7b8b7532-3642-4369-bfeb-04208cf72efc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157.19 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.0 dmi.board.name: 0JYXHN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.0:bd05/25/2018:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0JYXHN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: G3 3579 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776376/+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 1776342] Re: linux-azure: -proposed tracker
** Also affects: linux-azure (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Bionic) Status: New => Confirmed -- 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/1776342 Title: linux-azure: -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: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-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-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: 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: 1776338 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776342/+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 1776338] Re: linux: -proposed tracker
** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776338 Title: linux: -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: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 Bionic: 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 1776346 (linux-azure), bug 1776347 (linux-azure-edge), bug 1776348 (linux-hwe-edge) derivatives: bug 1776339 (linux-raspi2), bug 1776340 (linux-oem), bug 1776341 (linux-aws), bug 1776342 (linux-azure), bug 1776344 (linux-gcp), bug 1776345 (linux-kvm) To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776338/+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 1776337] Re: linux-oem: -proposed tracker
** Changed in: linux-oem (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1776337 Title: linux-oem: -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: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem 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: 1776333 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776337/+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 1776340] Re: linux-oem: -proposed tracker
** Also affects: linux-oem (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-oem (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1776340 Title: linux-oem: -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: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: 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: 1776338 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776340/+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 1776335] Re: linux-gcp: 4.13.0-1020.24 -proposed tracker
** Changed in: linux-gcp (Ubuntu Xenial) Status: New => Confirmed -- 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/1776335 Title: linux-gcp: 4.13.0-1020.24 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: 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-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: 1776333 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776335/+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 1776346] Re: linux-azure: -proposed tracker
** Also affects: linux-azure (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Xenial) Status: New => Confirmed -- 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/1776346 Title: linux-azure: -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: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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: New 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: 1776338 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776346/+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 1776344] Re: linux-gcp: -proposed tracker
** Also affects: linux-gcp (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-gcp (Ubuntu Bionic) Status: New => Confirmed -- 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/1776344 Title: linux-gcp: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 Bionic: 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: 1776338 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776344/+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 1776345] Re: linux-kvm: -proposed tracker
** Also affects: linux-kvm (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-kvm (Ubuntu Bionic) Status: New => Confirmed -- 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/1776345 Title: linux-kvm: -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: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 Bionic: 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: 1776338 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776345/+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 1776341] Re: linux-aws: -proposed tracker
** Also affects: linux-aws (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-aws (Ubuntu Bionic) Status: New => Confirmed -- 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/1776341 Title: linux-aws: -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: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 Bionic: 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: 1776338 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776341/+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 1772972] Re: linux: -proposed tracker
** 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/1772972 Title: linux: -proposed tracker Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-lbm series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: Invalid 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: derivatives: To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772972/+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
Ok it will be in the next kernel release. -- 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: Confirmed 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) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.80 dmi.board.name: H55M-LE dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH55M-LE:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M.
[Kernel-packages] [Bug 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)
@perryhelionsemail suspend works fine with the kernel from 17.10, but not with the kernel from 18.04 (everything else is the same, just selected the old kernel in 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/1774950 Title: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47) Status in linux package in Ubuntu: Confirmed Bug description: I have installed Kubuntu 18.04 on 3 different machines (my friend's and my own) with no suspend problems but my HP Pavilion 11 x360 does not suspend. It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse, Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu 18.04. I have also tried suspend using a live USB of 18.04 on this machine and it fails in the same way, so does not appear to be caused by any additional programs that I had installed. By installing an older kernel (4.14) on Kubuntu 18.04 the suspend function works as expected. Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the suspend failure that freezes the machine and requires a hard reset. Correct behaviour is - Screen goes blank, fan goes off, power LED flashes to show machine is in suspend. Pressing power button triggers 'resume' function. What happens - Screen goes blank, fan stays on, power LED stays on. Machine stays in this state and does not respond to any keyboard interaction, mouse movement or power button presses. Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response. The only way to use the machine is to shut down by holding down the power button. Checking the logs suggests that the machine believes it is in suspend mode sleep [deep] when it isn't. Having to hard reset to get any response means that the kernel logs say no more than sleep [deep] pm-suspend also results in the same problems with kernels 4.15 and 4.16, but works fine with 4.14. It is curious that a machine that suspends fine on an earlier 4.14 kernel no longer works with 4.15 and above, whilst 3 other machines (including one with pretty similar hardware) do not exhibit this problem. There are only a handful of questions about it on the forums but at least 3 other people have the same problem: https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on- resuming-from-suspend https://askubuntu.com/questions/1041369/after-upgrading- from-17-10-ubuntu-18-04-wont-sleep-suspend I am attempting to round up anyone else with the same issue and point them to this bug report. My laptop is HP Pavilion x360 11-n013na Matalaks is Acer Aspire ES1-511 collisionTwo has XPS 9560 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+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 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)
@Matalak - took a look at your redhat bugzilla link and the behaviour that todd describes is an exact match! Curiously enough, todd seems to be using a standard PC setup rather than a laptop. At the end of the redhat bugzilla post Laura Abbott suggests that todd files a bug report with the upstream maintainers at bugzilla.kernel.org and when I searched for suspend bugs I found: https://bugzilla.kernel.org/show_bug.cgi?id=199025 (last entry was 10th May) A few thoughts: - kernel bug 199025 'Suspend hangs. Never fully suspends and impossible to return to running state.' has been filed against this issue. The 'Status: NEEDINFO' and the last comment on it being from the 10th of May is not particularly encouraging :( - I'm not entirely sure how all of this works (this is the first bug report that I've filed) but my initial thoughts were to get anyone with suspend issues to add to the bug report and list their hardware, so that there might be a clearer picture of how many people this was affecting and what machines seem to be affected. - I assumed that nobody would pay any attention to this seemingly 'edge- case hardware combination issue' until it was ascertained that it affected a good many more people. - I'm pleased to see that I was incorrect in my assumption and that as far as I can tell from an email (think I got added to a list for starting the bug) a canonical team member, Kai-Heng Feng, has been in touch with a kernel.org developer about the kernel bisection report, who has made a patch to test. So I think what happens is that users report bugs to their specific distro (i.e Ubuntu, Fedora, Debian) and the distro developers/maintainers can then narrow it down and report the problem to the maintainers of the affected part of the project. In this case, what seems to be a kernel-related problem is reported to the kernel maintainers by the Ubuntu developers. Since it only seems to be affecting a few specific hardware combinations, it means any fixes will have to be tried out by someone with the 'problem hardware', who can then report back whether the issue is fixed. (I don't mind testing things out but don't really know what I'm doing, so if there is a patch to try I wouldn't know how to apply it.) I'm very tempted to let the bugzilla.kernel.org folks know that bug #199025 is affecting us too, but the Ubuntu maintainers might be in touch with them already. ** Bug watch added: Linux Kernel Bug Tracker #199025 https://bugzilla.kernel.org/show_bug.cgi?id=199025 -- 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/1774950 Title: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47) Status in linux package in Ubuntu: Confirmed Bug description: I have installed Kubuntu 18.04 on 3 different machines (my friend's and my own) with no suspend problems but my HP Pavilion 11 x360 does not suspend. It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse, Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu 18.04. I have also tried suspend using a live USB of 18.04 on this machine and it fails in the same way, so does not appear to be caused by any additional programs that I had installed. By installing an older kernel (4.14) on Kubuntu 18.04 the suspend function works as expected. Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the suspend failure that freezes the machine and requires a hard reset. Correct behaviour is - Screen goes blank, fan goes off, power LED flashes to show machine is in suspend. Pressing power button triggers 'resume' function. What happens - Screen goes blank, fan stays on, power LED stays on. Machine stays in this state and does not respond to any keyboard interaction, mouse movement or power button presses. Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response. The only way to use the machine is to shut down by holding down the power button. Checking the logs suggests that the machine believes it is in suspend mode sleep [deep] when it isn't. Having to hard reset to get any response means that the kernel logs say no more than sleep [deep] pm-suspend also results in the same problems with kernels 4.15 and 4.16, but works fine with 4.14. It is curious that a machine that suspends fine on an earlier 4.14 kernel no longer works with 4.15 and above, whilst 3 other machines (including one with pretty similar hardware) do not exhibit this problem. There are only a handful of questions about it on the forums but at least 3 other people have the same problem: https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on- resuming-from-suspend https://askubuntu.com/questions/1041369/after-upgrading- from-17-10-ubuntu-18-04-wont-sleep-suspend I am
[Kernel-packages] [Bug 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)
Ah flip! writing "kernel bug 199025" automatically links it to an *Ubuntu* bug with the same number from 2008! The bug with that particular number is this: https://bugzilla.kernel.org/show_bug.cgi?id=199025 -- 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/1774950 Title: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47) Status in linux package in Ubuntu: Confirmed Bug description: I have installed Kubuntu 18.04 on 3 different machines (my friend's and my own) with no suspend problems but my HP Pavilion 11 x360 does not suspend. It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse, Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu 18.04. I have also tried suspend using a live USB of 18.04 on this machine and it fails in the same way, so does not appear to be caused by any additional programs that I had installed. By installing an older kernel (4.14) on Kubuntu 18.04 the suspend function works as expected. Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the suspend failure that freezes the machine and requires a hard reset. Correct behaviour is - Screen goes blank, fan goes off, power LED flashes to show machine is in suspend. Pressing power button triggers 'resume' function. What happens - Screen goes blank, fan stays on, power LED stays on. Machine stays in this state and does not respond to any keyboard interaction, mouse movement or power button presses. Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response. The only way to use the machine is to shut down by holding down the power button. Checking the logs suggests that the machine believes it is in suspend mode sleep [deep] when it isn't. Having to hard reset to get any response means that the kernel logs say no more than sleep [deep] pm-suspend also results in the same problems with kernels 4.15 and 4.16, but works fine with 4.14. It is curious that a machine that suspends fine on an earlier 4.14 kernel no longer works with 4.15 and above, whilst 3 other machines (including one with pretty similar hardware) do not exhibit this problem. There are only a handful of questions about it on the forums but at least 3 other people have the same problem: https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on- resuming-from-suspend https://askubuntu.com/questions/1041369/after-upgrading- from-17-10-ubuntu-18-04-wont-sleep-suspend I am attempting to round up anyone else with the same issue and point them to this bug report. My laptop is HP Pavilion x360 11-n013na Matalaks is Acer Aspire ES1-511 collisionTwo has XPS 9560 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+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 1776005] Re: kernel instability with BTRFS filesystem as rootfs
Hello, It seems that the IO-APIC [1] is the main origin of this instability. So booting the kernel with the option "noapic" seems to be a good workaround for this issue, even if it's difficult to me to spot the commit which is the origin of this problem in reasonable time. Best regards, [1]: https://fr.wikipedia.org/wiki/IO-APIC Sylvain -- 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/1776005 Title: kernel instability with BTRFS filesystem as rootfs Status in linux package in Ubuntu: Incomplete Bug description: Hello, As explained yesterday on #ubuntu-kernel, several laptop won't boot (kernel panic) with the latest kernel 4.4.0-127-generic (x86_64) and upper (proposed 4.4.0-128-generic), on Xenial 16.04 LTS I have made many tests to verify that the bootloader (GRUB) is correctly configured (I have also reinstall it, but same result). I have also verified the BTRFS system is clean and not corrupted (with a livecd). The behavior is unpredictable, because often the kernel fall in "panic" during boot, but not all the time, if i do several consecutive reboot to test stability of the boot "process". I have no search behavior with previous kernels (like 4.4.0-124-generic). I suspect (even if I'm quiet disturbed by this behavior, maybe I wrong) that something I changed on last kernel: - on BTRFS subsystem, I have "aggregate" BTRFS partitions as rootfs (for a long time) - something related with the last mitigation about the recent security processor breach But my skills stop here, and I'm not able to find the origin of this behavior despite my efforts. I can continue my investigation if I have some additional pointers. Thanks for your time, Sylvain To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776005/+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 1772960] Re: linux: 4.4.0-128.154 -proposed tracker
The package has been published and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-stable Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => 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 backports: bug 1772962 (linux-lts-xenial), bug 1772963 (linux-aws) derivatives: bug 1772964 (linux-kvm), bug 1772965 (linux-snapdragon), bug 1772966 (linux-aws), bug 1772968 (linux-raspi2), bug 1772969 (linux-euclid) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to updates proposed-announcement-sent: true proposed-testing-requested: true + kernel-stable-phase:Released + kernel-stable-phase-changed:Tuesday, 12. June 2018 12: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 1772962 (linux-lts-xenial), bug 1772963 (linux-aws) derivatives: bug 1772964 (linux-kvm), bug 1772965 (linux-snapdragon), bug 1772966 (linux-aws), bug 1772968 (linux-raspi2), bug 1772969 (linux-euclid) -- swm properties -- boot-testing-requested: true bugs-spammed: true - phase: Promoted to updates + phase: Released proposed-announcement-sent: true proposed-testing-requested: true - kernel-stable-phase:Released - kernel-stable-phase-changed:Tuesday, 12. June 2018 12:03 UTC ** 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/1772960 Title: linux: 4.4.0-128.154 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-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-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Released 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 1772962 (linux-lts-xenial), bug 1772963 (linux-aws) derivatives: bug 1772964 (linux-kvm), bug 1772965 (linux-snapdragon), bug 1772966 (linux-aws), bug 1772968 (linux-raspi2), bug 1772969 (linux-euclid) -- swm properties -- boot-testing-requested: true bugs-spammed: true 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/1772960/+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 1774583] Re: Resuming does not work with kernel 3.13.0-149-generic
I will close this bug report. If anyone else is still experiencing issues I suggest to open a new bug report. ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1774583 Title: Resuming does not work with kernel 3.13.0-149-generic Status in linux package in Ubuntu: Fix Released Bug description: On my laptop MSI GE40 (MS-1492) with Ubuntu 14.04.5 LTS and kernel 3.13.0-149-generic resuming after a suspend no longer works. It hangs on a blank screen and is unresponsive. The only option is to hold the power button for 6 seconds to shut it down. It worked fine on 3.13.0-147-generic. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-149-generic 3.13.0-149.199 ProcVersionSignature: Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39 Uname: Linux 3.13.0-149-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.28 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: j-p3041 F pulseaudio /dev/snd/controlC1: j-p3041 F pulseaudio CurrentDesktop: Unity Date: Fri Jun 1 09:22:59 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=d0b66801-6479-4dc4-aae2-9bd97799b4a4 InstallationDate: Installed on 2013-11-20 (1653 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Micro-Star International Co., Ltd. CR42 2M/GE40 2OC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic root=UUID=3a8ce5b7-2d9e-441f-a3a6-16627d17cfa0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-149-generic N/A linux-backports-modules-3.13.0-149-generic N/A linux-firmware 1.127.24 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: Upgraded to trusty on 2014-11-17 (1291 days ago) dmi.bios.date: 08/05/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1492IMS.10H dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1492 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: CR42 2M/GE40 2OC dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1492IMS.10H:bd08/05/2013:svnMicro-StarInternationalCo.,Ltd.:pnCR422M/GE402OC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1492:rvrREV1.0:cvnCR422M/GE402OC:ct10:cvrN/A: dmi.product.name: CR42 2M/GE40 2OC dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774583/+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 1774150] Re: 3.13.0-149-generic: suspend/resume issue on 14.04
FYI: after installing the latest updates (containing kernel 3.13.0-151-generic) it all seems to work fine again for 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/1774150 Title: 3.13.0-149-generic: suspend/resume issue on 14.04 Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04.5 LTS, the most recent kernel update to 3.13.0-149-generic means that my laptop (Acer Aspire V5) does not resume once suspended - all I get is a blank screen, unresponsive to keypresses, and I need to reboot. The 144 kernel is OK, and this question: https://askubuntu.com/questions/1040169/experiencing-suspend-resume-problem-after-latest-kernel-update-ubuntu-14-04 suggests that 147 is OK too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774150/+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 1774583] Re: Resuming does not work with kernel 3.13.0-149-generic
I'm also not in the position to try the kernel upgrade. However after installing the latest updates (containing the 3.13.0-151-generic kernel) it seems to work fine again. Thanks for your support! -- 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/1774583 Title: Resuming does not work with kernel 3.13.0-149-generic Status in linux package in Ubuntu: Fix Released Bug description: On my laptop MSI GE40 (MS-1492) with Ubuntu 14.04.5 LTS and kernel 3.13.0-149-generic resuming after a suspend no longer works. It hangs on a blank screen and is unresponsive. The only option is to hold the power button for 6 seconds to shut it down. It worked fine on 3.13.0-147-generic. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-149-generic 3.13.0-149.199 ProcVersionSignature: Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39 Uname: Linux 3.13.0-149-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.28 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: j-p3041 F pulseaudio /dev/snd/controlC1: j-p3041 F pulseaudio CurrentDesktop: Unity Date: Fri Jun 1 09:22:59 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=d0b66801-6479-4dc4-aae2-9bd97799b4a4 InstallationDate: Installed on 2013-11-20 (1653 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Micro-Star International Co., Ltd. CR42 2M/GE40 2OC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic root=UUID=3a8ce5b7-2d9e-441f-a3a6-16627d17cfa0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-149-generic N/A linux-backports-modules-3.13.0-149-generic N/A linux-firmware 1.127.24 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: Upgraded to trusty on 2014-11-17 (1291 days ago) dmi.bios.date: 08/05/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1492IMS.10H dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1492 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: CR42 2M/GE40 2OC dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1492IMS.10H:bd08/05/2013:svnMicro-StarInternationalCo.,Ltd.:pnCR422M/GE402OC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1492:rvrREV1.0:cvnCR422M/GE402OC:ct10:cvrN/A: dmi.product.name: CR42 2M/GE40 2OC dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774583/+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 1773383] Re: iotop crashes on launch
Adding a linux task for the kernel team to consider dropping that empty
line, that was perhaps added by mistake.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1773383
Title:
iotop crashes on launch
Status in pkg-website:
Invalid
Status in iotop package in Ubuntu:
Triaged
Bug description:
~$ sudo iotop
Traceback (most recent call last):
File "/usr/sbin/iotop", line 17, in
main()
File "/usr/lib/python2.7/dist-packages/iotop/ui.py", line 620, in main
main_loop()
File "/usr/lib/python2.7/dist-packages/iotop/ui.py", line 610, in
main_loop = lambda: run_iotop(options)
File "/usr/lib/python2.7/dist-packages/iotop/ui.py", line 508, in run_iotop
return curses.wrapper(run_iotop_window, options)
File "/usr/lib/python2.7/curses/wrapper.py", line 43, in wrapper
return func(stdscr, *args, **kwds)
File "/usr/lib/python2.7/dist-packages/iotop/ui.py", line 501, in
run_iotop_window
ui.run()
File "/usr/lib/python2.7/dist-packages/iotop/ui.py", line 155, in run
self.process_list.duration)
File "/usr/lib/python2.7/dist-packages/iotop/ui.py", line 434, in
refresh_display
lines = self.get_data()
File "/usr/lib/python2.7/dist-packages/iotop/ui.py", line 415, in get_data
return list(map(format, processes))
File "/usr/lib/python2.7/dist-packages/iotop/ui.py", line 388, in format
cmdline = p.get_cmdline()
File "/usr/lib/python2.7/dist-packages/iotop/data.py", line 292, in
get_cmdline
proc_status = parse_proc_pid_status(self.pid)
File "/usr/lib/python2.7/dist-packages/iotop/data.py", line 196, in
parse_proc_pid_status
key, value = line.split(':\t', 1)
ValueError: need more than 1 value to unpack
~$ ls /usr/lib/python2.7/dist-packages/ | grep iotop
iotop
iotop-0.6.egg-info
~$ uname -a
Linux KISE-055 4.4.0-127-generic #153-Ubuntu SMP Sat May 19 10:58:46 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.4 LTS
Release:16.04
Codename: xenial
To manage notifications about this bug go to:
https://bugs.launchpad.net/pkg-website/+bug/1773383/+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 1773964] Comment bridged from LTC Bugzilla
--- Comment From cdead...@us.ibm.com 2018-06-12 10:46 EDT--- State: Working by: yadlapat on 12 June 2018 09:43:39 #=#=# 2018-06-12 09:43:37 (CDT) #=#=# New Priority = [2] #=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=# -- 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/1773964 Title: IPL: ppc64_cpu --frequency hang with INFO: rcu_sched detected stalls on CPUs/tasks on w34 and wsbmc016 with 920.1714.20170330n Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: == Comment: #0 - Application Cdeadmin <> - 2018-05-22 09:36:12 == == Comment: #1 - Application Cdeadmin <> - 2018-05-22 09:36:14 == State: Open by: swanman on 22 May 2018 09:17:33 Both w34 and wsbmc016 are stopped on this failure, where we get hung up on the following FFDC gathering step in the OS: #(CDT) 2018/05/22 05:07:19.398218 - 0.211662 - Issuing: OS Execute Command ppc64_cpu --frequency ignore_err=1 #(CDT) 2018/05/22 05:07:19.437808 - 0.024108 - Issuing: ppc64_cpu --frequency , and the last console output shows: # tail -200 /var/log/obmc-console.log s this GP) idle=82a/140/0 softirq=2689/2689 fqs=241989 [13668.719850] (detected by 3, t=3075620 jiffies, g=30289, c=30288, q=796881) [13732.630691] INFO: rcu_sched detected stalls on CPUs/tasks: [13732.630727] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=242996 [13732.630757] (detected by 3, t=3091597 jiffies, g=30289, c=30288, q=799822) [13795.649568] INFO: rcu_sched detected stalls on CPUs/tasks: [13795.649597] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=243942 [13795.649631] (detected by 7, t=3107351 jiffies, g=30289, c=30288, q=802916) [13860.140483] INFO: rcu_sched detected stalls on CPUs/tasks: [13860.140516] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=244940 [13860.140557] (detected by 3, t=3123473 jiffies, g=30289, c=30288, q=806646) [13924.731404] INFO: rcu_sched detected stalls on CPUs/tasks: [13924.731438] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=245874 [13924.731484] (detected by 3, t=3139620 jiffies, g=30289, c=30288, q=809909) [13988.642290] INFO: rcu_sched detected stalls on CPUs/tasks: [13988.642321] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=246892 [13988.642362] (detected by 3, t=3155596 jiffies, g=30289, c=30288, q=813048) [14052.661176] INFO: rcu_sched detected stalls on CPUs/tasks: [14052.661211] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=247857 [14052.661266] (detected by 3, t=3171600 jiffies, g=30289, c=30288, q=816185) [14115.680024] INFO: rcu_sched detected stalls on CPUs/tasks: [14115.680051] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=248819 [14115.680085] (detected by 4, t=3187355 jiffies, g=30289, c=30288, q=819190) [14180.154911] INFO: rcu_sched detected stalls on CPUs/tasks: [14180.154945] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=249833 [14180.154986] (detected by 132, t=3203473 jiffies, g=30289, c=30288, q=822138) [14244.968067]I F: Ne talls onCPUs/tasks [14244669838] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=2[14244.669944] (detected by 3, t=3219600 jiffies, g=30289, c=30288, q=825384) [14308.748680] Id detected stalls on CPUs/tasks: [14308.748719] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=251755 [14308.748755] (detected by 3, t=3235620 jiffies, g=30289, c=30288, q=828445) [14333.081775] Watchdog CPU:132 Hard LOCKUP [14344.750295] Watchdog CPU:132 became unstuck [14372.735558] INFO: rcu_sched detected stalls on CPUs/tasks: [14372.735587] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=252722 [14372.735611] (detected by 6, t=3251616 jiffies, g=30289, c=30288, q=831375) [14435.910193] INFO: rcu_sched detected stalls on CPUs/tasks: [14435.910219] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=253675 [14435.910253] (detected by 3, t=3267409 jiffies, g=30289, c=30288, q=834375) [14500.167195] INFO: rcu_sched detected stalls on CPUs/tasks: [14500.167230] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=254601 [14500.167273] (detected by 134, t=3283473 jiffies, g=30289, c=30288, q=837600) [14564.664395] INFO: rcu_sched detected stalls on CPUs/tasks: [14564.664427] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=255493 [14564.664470] (detected by 3, t=3299596
[Kernel-packages] [Bug 1773383] Re: iotop crashes on launch
The kernel aspect of this is being tracked in another bug: #1772671
** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1773383
Title:
iotop crashes on launch
Status in pkg-website:
Invalid
Status in iotop package in Ubuntu:
Triaged
Bug description:
~$ sudo iotop
Traceback (most recent call last):
File "/usr/sbin/iotop", line 17, in
main()
File "/usr/lib/python2.7/dist-packages/iotop/ui.py", line 620, in main
main_loop()
File "/usr/lib/python2.7/dist-packages/iotop/ui.py", line 610, in
main_loop = lambda: run_iotop(options)
File "/usr/lib/python2.7/dist-packages/iotop/ui.py", line 508, in run_iotop
return curses.wrapper(run_iotop_window, options)
File "/usr/lib/python2.7/curses/wrapper.py", line 43, in wrapper
return func(stdscr, *args, **kwds)
File "/usr/lib/python2.7/dist-packages/iotop/ui.py", line 501, in
run_iotop_window
ui.run()
File "/usr/lib/python2.7/dist-packages/iotop/ui.py", line 155, in run
self.process_list.duration)
File "/usr/lib/python2.7/dist-packages/iotop/ui.py", line 434, in
refresh_display
lines = self.get_data()
File "/usr/lib/python2.7/dist-packages/iotop/ui.py", line 415, in get_data
return list(map(format, processes))
File "/usr/lib/python2.7/dist-packages/iotop/ui.py", line 388, in format
cmdline = p.get_cmdline()
File "/usr/lib/python2.7/dist-packages/iotop/data.py", line 292, in
get_cmdline
proc_status = parse_proc_pid_status(self.pid)
File "/usr/lib/python2.7/dist-packages/iotop/data.py", line 196, in
parse_proc_pid_status
key, value = line.split(':\t', 1)
ValueError: need more than 1 value to unpack
~$ ls /usr/lib/python2.7/dist-packages/ | grep iotop
iotop
iotop-0.6.egg-info
~$ uname -a
Linux KISE-055 4.4.0-127-generic #153-Ubuntu SMP Sat May 19 10:58:46 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.4 LTS
Release:16.04
Codename: xenial
To manage notifications about this bug go to:
https://bugs.launchpad.net/pkg-website/+bug/1773383/+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 1754053] Re: oops in set_next_entity / ipmi_msghandler
Collected more data points on this issue. 1. Tried offline CPUs. We found that the crash typically was on CPU:40, so offlined CPU40 and repeated the test. The test seemed to make progress but panicked on a different CPU. I tried to offline several more CPU, but the crash seems to move on to other CPUs. 2. Changed the scheduler from CFQ to NOOP. This made no difference either, crash was seen on CPU:44 and offline CPU44 yielded the same results. Panics seem to happen either in the scheduler or in ext4 code (note that we are running stress on SDA). According to Cavium eng this could be a due to a bad L2 cache or memory. Tailing /var/log/syslog and /var/log/kernlog while the tests were running I did see messages like this: Jun 12 14:57:55 seuss ipmievd: Voltage sensor CPU_VTT_DDR02 Upper Non-critical going high Asserted (Reading 0.77 > Threshold 0.77 Volts) Jun 12 14:57:56 seuss ipmievd: Voltage sensor CPU_VTT_DDR02 Upper Non-critical going high Deasserted (Reading 0.76 > Threshold 0.77 Volts) Jun 12 14:57:57 seuss ipmievd: Voltage sensor CPU_VTT_DDR13 Upper Non-critical going high Deasserted (Reading 0.76 > Threshold 0.77 Volts) Jun 12 14:57:58 seuss ipmievd: Voltage sensor CPU_VTT_DDR13 Upper Non-critical going high Asserted (Reading 0.77 > Threshold 0.77 Volts) We have other CRB1S that function as expected and the stress-ng tests do no cause any panics. I am tempted consider this issue to be a hardware issue with this particular CRB1S ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => Won't Fix ** Changed in: linux (Ubuntu Artful) Status: Confirmed => Won't Fix ** Changed in: linux (Ubuntu) Status: Incomplete => Won't Fix -- 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/1754053 Title: oops in set_next_entity / ipmi_msghandler Status in linux package in Ubuntu: Won't Fix Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: Won't Fix Bug description: Seen on a Cavium CRB1S a couple of times while running the com.canonical.certification::disk/disk_stress_ng_sda testcase from the canonical-certification-server test suite: [ 1823.116031] Unable to handle kernel read from unreadable memory at virtual address 0038 [ 1823.124479] user pgtable: 4k pages, 48-bit VAs, pgd = 801f4bf0 [ 1823.131068] [0038] *pgd= [ 1823.136080] Internal error: Oops: 9604 [#1] SMP [ 1823.141002] Modules linked in: nls_iso8859_1 i2c_thunderx thunderx_zip thunderx_edac i2c_smbus shpchp cavium_rng_vf cavi um_rng gpio_keys ipmi_ssif ipmi_devintf ipmi_msghandler uio_pdrv_genirq uio ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp l ibiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor as ync_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear nicvf nicpf ast i2c_algo_bit ttm drm_kms_helper syscopyarea sysf illrect aes_ce_blk sysimgblt aes_ce_cipher fb_sys_fops crc32_ce crct10dif_ce drm ghash_ce sha2_ce sha1_ce ahci libahci thun der_bgx thunder_xcv mdio_thunder thunderx_mmc mdio_cavium aes_neon_bs aes_neon_blk crypto_simd cryptd [ 1823.204136] CPU: 30 PID: 0 Comm: swapper/30 Not tainted 4.13.0-36-generic #40~16.04.1-Ubuntu [ 1823.212655] Hardware name: Cavium ThunderX CRB/To be filled by O.E.M., BIOS 5.11 12/12/2012 [ 1823.221085] task: 801f7320bc00 task.stack: 801f7321 [ 1823.227067] PC is at set_next_entity+0x28/0x5e8 [ 1823.231640] LR is at pick_next_task_fair+0xa0/0x580 [ 1823.236561] pc : [] lr : [] pstate: 604001c5 [ 1823.244026] sp : 801f73213dc0 [ 1823.247368] x29: 801f73213dc0 x28: 801f7ca19800 [ 1823.252731] x27: 08a76aac x26: 801f7ca19868 [ 1823.258093] x25: 801f7320c2c0 x24: 093c8000 [ 1823.263455] x23: x22: 08fe1000 [ 1823.268817] x21: 801f7ca19868 x20: 801f7ca19868 [ 1823.274178] x19: x18: ca622758 [ 1823.279541] x17: 002711a2 x16: [ 1823.284903] x15: 3dc0f68eb41e x14: 0001318c81308142 [ 1823.290266] x13: 0003e800 x12: 00b4 [ 1823.295628] x11: x10: 00b4 [ 1823.300990] x9 : 08aa5c98 x8 : 801f7320c760 [ 1823.306353] x7 : 0020 x6 : 003541e45d3fef78 [ 1823.311715] x5 : 0018 x4 : 08118e88 [ 1823.317077] x3 : 08aa5a70 x2 : 0810cb18 [ 1823.324394] x1 : x0 : 08118f28 [ 1823.331704] Process swapper/30 (pid: 0, stack limit = 0x801f7321) [ 1823.340536] Stack: (0x801f73213dc0 to 0x801f73214000) [ 1823.348292] 3dc0: 801f73213e10 08118f28 801f7ca19868 [ 1823.358135] 3de0: 801f73213f28 08fe1000
[Kernel-packages] [Bug 1771780] Re: [LTCTest][OPAL][OP920] cpupower idle-info is not listing stop4 and stop5 idle states when all CORES are guarded
** Changed in: linux (Ubuntu Bionic) 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/1771780 Title: [LTCTest][OPAL][OP920] cpupower idle-info is not listing stop4 and stop5 idle states when all CORES are guarded Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: == SRU Justification == During testing, IBM found that cpupower idle-info is not listing stop4 and stop5 idle states when all CORES are guarded. A patch has been submitted upstream by IBM. However, the patch has not landed in linux-next or mainline as of yet. For that reason, this SRU request is being sent as a SAUCE patch request. == Fix == UBUNTU: SAUCE: cpuidle/powernv : init all present cpus for deep states == Regression Potential == Low. Limited to powerpc. == 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. == Comment: #0 - PAVAMAN SUBRAMANIYAM - 2018-05-16 04:07:59 == ---Problem Description--- cpupower idle-info is not listing stop4 and stop5 idle states when all CORES are guarded ---uname output--- Linux ltc-wspoon11 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = P9 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Install a P9 Open Power Hardware with Ubuntu 18.04 OS. root@ltc-wspoon11:~# uname -a Linux ltc-wspoon11 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@ltc-wspoon11:~# cat /etc/os-release NAME="Ubuntu" VERSION="18.04 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic Then guard an entire processor and also guard all the CORES in the processor 0 except for 1 single core. root@ltc-wspoon11:~# opal-gard list ID | Error| Type | Path --- 0001 | | Manual | /Sys0/Node0/Proc0/EQ1/EX0/Core0 0002 | | Manual | /Sys0/Node0/Proc0/EQ1/EX0/Core1 0003 | | Manual | /Sys0/Node0/Proc1 0004 | | Manual | /Sys0/Node0/Proc0/EQ2/EX0/Core1 0005 | | Manual | /Sys0/Node0/Proc0/EQ2/EX0/Core0 0006 | | Manual | /Sys0/Node0/Proc0/EQ2/EX1/Core0 0007 | | Manual | /Sys0/Node0/Proc0/EQ2/EX1/Core1 0008 | | Manual | /Sys0/Node0/Proc0/EQ3/EX0/Core0 0009 | | Manual | /Sys0/Node0/Proc0/EQ3/EX0/Core1 000a | | Manual | /Sys0/Node0/Proc0/EQ3/EX1/Core0 000b | | Manual | /Sys0/Node0/Proc0/EQ3/EX1/Core1 000c | | Manual | /Sys0/Node0/Proc0/EQ4/EX0/Core0 000d | | Manual | /Sys0/Node0/Proc0/EQ4/EX0/Core1 000e | | Manual | /Sys0/Node0/Proc0/EQ4/EX1/Core0 000f | | Manual | /Sys0/Node0/Proc0/EQ4/EX1/Core1 0010 | | Manual | /Sys0/Node0/Proc0/EQ5/EX0/Core0 0011 | | Manual | /Sys0/Node0/Proc0/EQ5/EX0/Core1 0012 | | Manual | /Sys0/Node0/Proc0/EQ5/EX1/Core0 0013 | | Manual | /Sys0/Node0/Proc0/EQ5/EX1/Core1 0014 | | Manual | /Sys0/Node0/Proc0/EQ1/EX1/Core0 0015 | | Manual | /Sys0/Node0/Proc0/EQ1/EX1/Core1 0016 | | Manual | /Sys0/Node0/Proc0/EQ0/EX1/Core1 0017 | | Manual | /Sys0/Node0/Proc0/EQ0/EX1/Core0 === Then execute the cpupower idle-info command to check the idle states being shown in the OS. root@ltc-wspoon11:~# cpupower idle-info CPUidle driver: powernv_idle CPUidle governor: menu analyzing CPU 0: Number of idle states: 7 Available idle states: snooze stop0_lite stop0 stop1_lite stop1 stop2_lite stop2 snooze: Flags/Description: snooze Latency: 0 Usage: 774653 Duration: 7698954 stop0_lite: Flags/Description: stop0_lite Latency: 1 Usage: 2751 Duration: 11363825 stop0: Flags/Description: stop0 Latency: 2 Usage: 2343 Duration: 915084 stop1_lite: Flags/Description: stop1_lite Latency: 5 Usage: 20 Duration: 1533 stop1:
[Kernel-packages] [Bug 1761856] Re: kata-containers: netlink protocol not supported
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-kvm (Ubuntu) Status: New => Confirmed -- 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/1761856 Title: kata-containers: netlink protocol not supported Status in linux-kvm package in Ubuntu: Confirmed Bug description: Kata container agent is not able to configure the network inside the container level=error msg="update interface request failed" arch=amd64 error="rpc error: code = Unknown desc = protocol not supported" interface-requested="device:\"eth0\" name:\"eth0\" IPAddresses: mtu:1500 hwAddr:\"02:42:ac:11:00:02\" " name=kata-runtime pid=29665 resulting- interface="" source=virtcontainers subsystem=kata_agent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1761856/+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 1776211] Comment bridged from LTC Bugzilla
--- Comment From vaish...@in.ibm.com 2018-06-12 11:38 EDT--- FYI, We do have this fix included for bionic already with launchpad bug 1758206 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1776211 Title: kdump fails to take dump with smt set to 2, hmc dumpstart Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: New Status in linux source package in Artful: In Progress Status in makedumpfile source package in Artful: New Bug description: --Problem Description--- kdump fails to take dump with smt set to 2, hmc dumpstart ---Issue observed--- [0.004111] Oops: Exception in kernel mode, sig: 4 [#1] [0.004118] SMP NR_CPUS=2048 [0.004120] NUMA [0.004125] pSeries [0.004132] Modules linked in: [0.004142] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.13.0-12-generic #13-Ubuntu [0.004153] task: c00046715900 task.stack: c00046134000 [0.004162] NIP: c0006468 LR: c801764c CTR: 006cdc70 [0.004173] REGS: c00047fe3ce0 TRAP: 0700 Not tainted (4.13.0-12-generic) [0.004181] MSR: 80081031 [0.004193] CR: 8804 XER: 2003 [0.004204] CFAR: c0006454 SOFTE: 0 [0.004204] GPR00: c801764c c00047fe3f60 c95e3000 [0.004204] GPR04: 0001 0002 ffdf [0.004204] GPR08: 2804 0002 0002 [0.004204] GPR12: cfff c00046137f90 0b5452d8 [0.004204] GPR16: fffd 089ffd10 0136 0b55d378 [0.004204] GPR20: 0060 1eca 0a6c 0007 [0.004204] GPR24: c9621ed0 [0.004204] GPR28: c00046134000 c00046137c80 c9105df8 [0.004328] NIP [c0006468] 0xc0006468 [0.004338] LR [c801764c] __do_irq+0x4c/0x1c0 [0.004345] Call Trace: [0.004354] [c00047fe3f60] [c801764c] __do_irq+0x4c/0x1c0 (unreliable) [0.004368] [c00047fe3f90] [c802ab70] call_do_irq+0x14/0x24 [0.004380] [c00046137bc0] [c801785c] do_IRQ+0x9c/0x130 [0.004393] [c00046137c10] [c8008ac4] hardware_interrupt_common+0x114/0x120 [0.004409] --- interrupt: 501 at arch_local_irq_restore+0x5c/0x90 [0.004409] LR = arch_local_irq_restore+0x40/0x90 [0.004423] [c00046137f00] [0005] 0x5 (unreliable) [0.004436] [c00046137f20] [c8049824] start_secondary+0x324/0x350 [0.004450] [c00046137f90] [c800aa6c] start_secondary_prolog+0x10/0x14 [0.004460] Instruction dump: [0.004467] [0.004484] [0.004506] ---[ end trace 3e5a2a9047ef3cd0 ]--- [0.004512] [0.004518] Oops: Exception in kernel mode, sig: 4 [#2] [0.004525] SMP NR_CPUS=2048 [0.004526] NUMA [0.004532] pSeries [0.004540] Modules linked in: [0.004550] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G D 4.13.0-12-generic #13-Ubuntu [0.004561] task: c9579f00 task.stack: c95dc000 [0.004569] NIP: c0006460 LR: c80b6e80 CTR: [0.004580] REGS: c95dfb20 TRAP: 0700 Tainted: G D (4.13.0-12-generic) [0.004589] MSR: 80081031 [0.004599] CR: 22002228 XER: 2004 [0.004611] CFAR: c000493c SOFTE: 0 [0.004611] GPR00: c95dfda0 c95e3000 [0.004611] GPR04: [0.004611] GPR08: 22002228 7fff 0008 [0.004611] GPR12: cfff0a80 c00c7e137f90 09980600 [0.004611] GPR16: 1ec7 0001 [0.004611] GPR20: 0007 [0.004611] GPR24: 0008 c800 0800 [0.004611] GPR28: 0008 c9621ed0 c9622354 [0.004729] NIP [c0006460] 0xc0006460 [0.004739] LR [c80b6e80] pseries_lpar_idle+0x30/0x50 [0.004746] Call Trace: [0.004756] [c95dfda0] [c95dfe90] init_thread_union+0x3e90/0x4000
[Kernel-packages] [Bug 1776338] Re: linux: 4.15.0-24.26 -proposed tracker
** Summary changed: - linux: -proposed tracker + linux: 4.15.0-24.26 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** 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) => Kleber Sacilotto de Souza (kleber-souza) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776338 Title: linux: 4.15.0-24.26 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: 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 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 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 Bionic: 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 1776346 (linux-azure), bug 1776347 (linux-azure-edge), bug 1776348 (linux-hwe-edge) derivatives: bug 1776339 (linux-raspi2), bug 1776340 (linux-oem), bug 1776341 (linux-aws), bug 1776342 (linux-azure), bug 1776344 (linux-gcp), bug 1776345 (linux-kvm) To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776338/+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 1771344] Re: Fix enabling bridge MMIO windows
@Manoj, this patch looks to be in Bionic as
16735b38aeae1ce2ae21983a7a7440922d6941e4 - can you please double check?
--
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/1771344
Title:
Fix enabling bridge MMIO windows
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Artful:
Fix Committed
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
In Progress
Bug description:
== SRU Justification ==
IBM is requesting this patch in Bionic and Artful to fix a regression. The
regression was introduced in v3.11-rc1. The patch fixes enabling bridge
MMIO windows. Commit 13a83eac373c was also cc'd to upstream stable, and
has already landed in Xenial via upstream stable updates.
== Fix ==
13a83eac373c ("powerpc/eeh: Fix enabling bridge MMIO windows")
== Regression Potential ==
Low. Limited to powerpc and fixes a current regression.
== 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.
== Comment: #0 - Breno Leitao
On boot we save the configuration space of PCIe bridges. We do this so
when we get an EEH event and everything gets reset that we can restore
them.
Unfortunately we save this state before we've enabled the MMIO space
on the bridges. Hence if we have to reset the bridge when we come back
MMIO is not enabled and we end up taking an PE freeze when the driver
starts accessing again.
This patch forces the memory/MMIO and bus mastering on when restoring
bridges on EEH. Ideally we'd do this correctly by saving the
configuration space writes later, but that will have to come later in
a larger EEH rewrite. For now we have this simple fix.
The original bug can be triggered on a boston machine by doing:
echo 0x8000 >
/sys/kernel/debug/powerpc/PCI0001/err_injct_outbound
On boston, this PHB has a PCIe switch on it. Without this patch,
you'll see two EEH events, 1 expected and 1 the failure we are fixing
here. The second EEH event causes the anything under the PHB to
disappear (i.e. the i40e eth).
With this patch, only 1 EEH event occurs and devices properly recover.
This is commit id 13a83eac373c49c0a081cbcd137e79210fe78acd and should
be part of Ubuntu 18.04 kernel.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1771344/+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 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)
@redroach - Thanks Matze for adding some more details - it's good to have as much information on how people are affected and on what hardware because this is an odd bug that isn't easy to reproduce, except seemingly with a few specific hardware combinations. - My initial thought that it seems to be a 'Bay Trail Atom coupled with an SSD' problem has not held up. @cmeerw had a machine with the same N3540 processor as mine without an SSD and it had the same problem. I also managed to try a machine with an N2830 processor without an SSD and it had the same problem too using a Live USB. So why it works fine on a machine with an N2840 processor is peculiar. - It might be worth trying the 4.14 kernel again without the intel_idle.max_cstate=1 in the grub configuration file, just to check whether the other odd behaviours might be due to that. Changing the cstate value will likely affect your battery life so it's not an ideal fix. - There is a patch that has been written (by kernel.org developer Rafael) and Hai-Keng Feng has posted a kernel with the patch applied. Details in the next post... :) -- 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/1774950 Title: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47) Status in linux package in Ubuntu: Confirmed Bug description: I have installed Kubuntu 18.04 on 3 different machines (my friend's and my own) with no suspend problems but my HP Pavilion 11 x360 does not suspend. It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse, Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu 18.04. I have also tried suspend using a live USB of 18.04 on this machine and it fails in the same way, so does not appear to be caused by any additional programs that I had installed. By installing an older kernel (4.14) on Kubuntu 18.04 the suspend function works as expected. Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the suspend failure that freezes the machine and requires a hard reset. Correct behaviour is - Screen goes blank, fan goes off, power LED flashes to show machine is in suspend. Pressing power button triggers 'resume' function. What happens - Screen goes blank, fan stays on, power LED stays on. Machine stays in this state and does not respond to any keyboard interaction, mouse movement or power button presses. Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response. The only way to use the machine is to shut down by holding down the power button. Checking the logs suggests that the machine believes it is in suspend mode sleep [deep] when it isn't. Having to hard reset to get any response means that the kernel logs say no more than sleep [deep] pm-suspend also results in the same problems with kernels 4.15 and 4.16, but works fine with 4.14. It is curious that a machine that suspends fine on an earlier 4.14 kernel no longer works with 4.15 and above, whilst 3 other machines (including one with pretty similar hardware) do not exhibit this problem. There are only a handful of questions about it on the forums but at least 3 other people have the same problem: https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on- resuming-from-suspend https://askubuntu.com/questions/1041369/after-upgrading- from-17-10-ubuntu-18-04-wont-sleep-suspend I am attempting to round up anyone else with the same issue and point them to this bug report. My laptop is HP Pavilion x360 11-n013na Matalaks is Acer Aspire ES1-511 collisionTwo has XPS 9560 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+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 1776335] Re: linux-gcp: 4.13.0-1020.24 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-xenial ** Tags added: block-proposed -- 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/1776335 Title: linux-gcp: 4.13.0-1020.24 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: 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-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 -- boot-testing-requested: true kernel-stable-master-bug: 1776333 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776335/+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 1771823] Re: Please include ax88179_178a and r8152 modules in d-i udeb
Thanks, both devices worked with the kernel, I tested them by booting the kernel in qemu VM and redirecting the USB devices to the VM. -- 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/1771823 Title: Please include ax88179_178a and r8152 modules in d-i udeb Status in debian-installer package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: New Status in linux source package in Cosmic: Incomplete Bug description: r8152 is used in a thunderbolt-connected docking station and ax88179_178a by an external USB dongle. Despite having two nics connected i can't install Bionic. :-) This is probably a subset of the modules to be included when fixing LP: #1503218. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1771823/+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 1776325] Re: Error messages during boot - Ubuntu 18.04 & Mint19
This started after buying and installing new cpu, AMD Ryzen 2400g, on new motherboard. So no previous history available. Now reading Kernel Mainline Builds, will have a bash... keep you posted -- 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/1776325 Title: Error messages during boot - Ubuntu 18.04 & Mint19 Status in linux package in Ubuntu: Incomplete Bug description: This came about as I had problems with efi while installing a dual boot of ubuntu and linux mint. As I understand it, during the boot process, the kernel sees a cpu count for the processor chip , AMD Ryzen 2400G, as 8 but 4 of them are graphics compute units. A little later in the process, the graphics processors cause errors. Subsequent to discovering this , I have added a line to grub GRUB_CMDLINE_LINUX_ which appears to have improved the boot process. It is 'ruc_nocbs=0-3'. The alteration in grub seems to help limit the cpu count and gets the boot process over the bump. I searched the interweb for clues and this seems to be a successful experiment. I am reporting this because I could not find any pertinent reference to this sort of problem with this particular chip. This search was not exhaustive so I hope I am not wasting your time :) I am attaching a file of concatenated system info for kernel reports as the options on this page only appear to allow one file to be selected (https://bugs.launchpad.net/ubuntu/+source/linux/+filebug/4aca6a90-6dc0-11e8 -b34a-002481e7f48a. Most of this was my lack of understanding the efi requirements, but the lack of useful information in the Gigabyte motherboard manual about how the UEFI operation was managed by its operating system prolonged my agony.:) I hope this helps, thank you and keep up the fantastic work Bob. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 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.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tpf1528 F pulseaudio /dev/snd/controlC0: tpf1528 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jun 12 09:38:39 2018 HibernationDevice: RESUME=UUID=150c1cd8-2246-4c18-b40e-dc07d8425777 InstallationDate: Installed on 2018-06-10 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. AB350N-Gaming WIFI ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=36d43481-0720-4808-a234-82941b71f750 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23d dmi.board.asset.tag: Default string dmi.board.name: AB350N-Gaming WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF23d:bd04/17/2018:svnGigabyteTechnologyCo.,Ltd.:pnAB350N-GamingWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350N-GamingWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350N-Gaming WIFI dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776325/+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 279999] Re: NaturalPoint SmartNav4 support
** Changed in: hal Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/27 Title: NaturalPoint SmartNav4 support Status in HAL: Invalid Status in hal-info package in Ubuntu: Invalid Status in linux package in Ubuntu: Triaged Bug description: Binary package hint: hal-info Here's a start at an FDI file for the SmartNav4 hands-free mouse: SmartNav 4 evdev true To manage notifications about this bug go to: https://bugs.launchpad.net/hal/+bug/27/+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 279999]
Mass closure: This bug has been untouched for more than six years, and is not obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases. -- 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/27 Title: NaturalPoint SmartNav4 support Status in HAL: Invalid Status in hal-info package in Ubuntu: Invalid Status in linux package in Ubuntu: Triaged Bug description: Binary package hint: hal-info Here's a start at an FDI file for the SmartNav4 hands-free mouse: SmartNav 4 evdev true To manage notifications about this bug go to: https://bugs.launchpad.net/hal/+bug/27/+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 1473200] Re: adaptec starfire fails to initialize with pae kernels
Further information, including a solution for this issue, can be found in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1717259 See also https://bugzilla.kernel.org/show_bug.cgi?id=198035 ** Bug watch added: Linux Kernel Bug Tracker #198035 https://bugzilla.kernel.org/show_bug.cgi?id=198035 -- 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/1473200 Title: adaptec starfire fails to initialize with pae kernels Status in linux package in Ubuntu: Expired Bug description: Adaptec ethernet adapter using starfire driver fails to initialize when a pae-enabled kernel is used. Adapted initializes correctly with a non-pae kernel: From dmesg: [3.154813] FDC 0 is a National Semiconductor PC87306 [3.165051] [ cut here ] [3.169716] WARNING: CPU: 0 PID: 118 at /build/buildd/linux-lts-utopic-3.16.0/arch/x86/mm/ioremap.c:98 __ioremap_caller+0x358/0x380() [3.178686] tsc: Refined TSC clocksource calibration: 2790.998 MHz [3.187928] Modules linked in: starfire(+) mii floppy [3.193114] CPU: 0 PID: 118 Comm: systemd-udevd Not tainted 3.16.0-30-generic #40~14.04.1-Ubuntu [3.201911] Hardware name: Intel/SE7501BR2 , BIOS SBR20.86B.0041.P01.02102211/11/2002 [3.212522] f68a1c14 c168b423 [3.217089] usb 2-1: New USB device found, idVendor=413c, idProduct=2005 [3.217093] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [3.217098] usb 2-1: Product: DELL USB Keyboard [3.217102] usb 2-1: Manufacturer: DELL [3.240047] f68a1c44 c105c2ae c187a884 [3.244147] 0076 c1878950 0062 c104f0b8 c104f0b8 0fff fe4f [3.252032] f68a1c54 c105c372 0009 f68a1cb8 c104f0b8 c1878924 [3.259910] Call Trace: [3.262384] [] dump_stack+0x41/0x52 [3.266838] [] warn_slowpath_common+0x7e/0xa0 [3.272157] [] ? __ioremap_caller+0x358/0x380 [3.277476] [] ? __ioremap_caller+0x358/0x380 [3.282798] [] warn_slowpath_null+0x22/0x30 [3.287944] [] __ioremap_caller+0x358/0x380 [3.293096] [] ? __pci_request_selected_regions+0x3f/0x80 [3.299457] [] ? starfire_init_one+0xc6/0x5b0 [starfire] [3.305734] [] ioremap_nocache+0x1f/0x30 [3.310623] [] ? starfire_init_one+0xc6/0x5b0 [starfire] [3.316899] [] starfire_init_one+0xc6/0x5b0 [starfire] [3.323002] [] ? __pm_runtime_resume+0x51/0x70 [3.328417] [] pci_device_probe+0x6f/0xc0 [3.98] [] ? sysfs_create_link+0x25/0x40 [3.338632] [] driver_probe_device+0x93/0x3a0 [3.343958] [] ? pci_match_device+0xca/0x100 [3.349192] [] __driver_attach+0x71/0x80 [3.354081] [] ? __device_attach+0x40/0x40 [3.359139] [] bus_for_each_dev+0x47/0x80 [3.364114] [] driver_attach+0x1e/0x20 [3.368828] [] ? __device_attach+0x40/0x40 [3.373893] [] bus_add_driver+0x157/0x230 [3.378869] [] ? 0xf8370fff [3.382630] [] ? 0xf8370fff [3.386393] [] driver_register+0x59/0xe0 [3.391278] [] ? printk+0x50/0x52 [3.395557] [] __pci_register_driver+0x32/0x40 [3.400968] [] starfire_init+0x30/0x1000 [starfire] [3.406807] [] do_one_initcall+0xc2/0x1f0 [3.411779] [] ? 0xf8370fff [3.415544] [] ? free_vmap_area_noflush+0x24/0x60 [3.421208] [] ? __vunmap+0x8f/0xe0 [3.425660] [] ? __vunmap+0x8f/0xe0 [3.430117] [] load_module+0x1237/0x1930 [3.435005] [] SyS_finit_module+0x75/0xc0 [3.439978] [] ? vm_mmap_pgoff+0x7b/0xa0 [3.444867] [] sysenter_do_call+0x12/0x12 [3.449839] ---[ end trace 3eef602429cd6b81 ]--- [3.454468] starfire :08:04.0: cannot remap 0x8 @ 0xfe48, aborting [3.461915] ioremap: invalid physical address fe38 [3.467770] starfire :08:05.0: cannot remap 0x8 @ 0xfe38, aborting [3.475139] ioremap: invalid physical address fe30 [3.480984] starfire :08:06.0: cannot remap 0x8 @ 0xfe30, aborting [3.488341] ioremap: invalid physical address fe20 [3.494190] starfire :08:07.0: cannot remap 0x8 @ 0xfe20, aborting [3.501552] ioremap: invalid physical address fea8 [3.507394] starfire :09:04.0: cannot remap 0x8 @ 0xfea8, aborting [3.514741] ioremap: invalid physical address fe98 [3.520585] starfire :09:05.0: cannot remap 0x8 @ 0xfe98, aborting [3.527943] ioremap: invalid physical address fe90 [3.533789] starfire :09:06.0: cannot remap 0x8 @ 0xfe90, aborting [3.541144] ioremap: invalid physical address fe80 [3.546986] starfire :09:07.0: cannot remap 0x8 @ 0xfe80, aborting [
[Kernel-packages] [Bug 1768139] Re: Kernel crash when booting laptop with hdmi monitor connected
bisect result: lp:~ubuntu-kernel/ubuntu/+source/linux/+git/unstable shows this commit. I built using the mainline config-4.15.0-041500rc2-generic file and accepted default options. I also had to apply ff6fa2d396b0476988c749664f600b1e177bcf9b in order to get the neighboring commits to build. it does appear to stop the flicker, but also seems to cause the boot failure. commit 77a113c1ac1458856ca8e82a9046efff8ca87f09 Author: Andy Whitcroft Date: Wed Apr 16 19:40:57 2014 +0100 UBUNTU: SAUCE: vt -- maintain bootloader screen mode and content until vt switch Introduce a new VT mode KD_TRANSPARENT which endevours to leave the current content of the framebuffer untouched. This allows the bootloader to insert a graphical splash and have the kernel maintain it until the OS splash can take over. When we finally switch away (either through programs like plymouth or manually) the content is lost and the VT reverts to text mode. BugLink: http://bugs.launchpad.net/bugs/1308685 Signed-off-by: Andy Whitcroft :04 04 b0f28f7ecaeaf8037832299ee421886dcd9dfc25 3e051b4e05da82a1184bdb45a71d3317e8c74445 M drivers :04 04 22bdb68e3e9757318cf57f010231c1af7db61cc1 ce199b29dcc261c74b4b2cdfd26dc3993ecbd970 M include -- 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/1768139 Title: Kernel crash when booting laptop with hdmi monitor connected Status in linux package in Ubuntu: Triaged Bug description: When I boot a Dell Inspiron 7559 with an external monitor connected to the hdmi port, it usually shows only a blank screen after grub and I have to hard power off the laptop. The issue is present when the bios and grub are in mirror mode to both screens. I can see the following stack trace in journalctl: syslog contains: kernel: Missing switch case (6) in intel_prepare_dp_ddi_buffers This occurs with both a Dell U2515H using an HDMI cord, and a HP Compaq LA2405wg connected via HDMI-to-DVI adapter. WORKAROUND: Keep the monitor unplugged until the Ubuntu loading screen shows up. 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 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 30 17:22:20 2018 InstallationDate: Installed on 2018-04-28 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) This is a fresh install. I have modified grub defaults to include "acpi_osi=!Windows 2015" But I tested without the acpi_osi parameter and see the same issue although the system now randomly crashes later on. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: apatterson 1965 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7b947b8e-de50-4ab6-b7f3-254a5dea924a InstallationDate: Installed on 2018-04-28 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 7559 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=77f1cfec-1fe4-4201-9a91-9f00a5d7782b ro quiet splash "acpi_osi=!Windows 2015" ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic wayland-session Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 09/26/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.5 dmi.board.name: 0H0CC0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.5:bd09/26/2017:svnDellInc.:pnInspiron7559:pvr1.2.5:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 7559 dmi.product.version: 1.2.5 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768139/+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 1776356] Re: linux-aws: 4.4.0-1062.71 -proposed tracker
** Summary changed: - linux-aws: -proposed tracker + linux-aws: 4.4.0-1062.71 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** 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) => Khaled El Mously (kmously) -- 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/1776356 Title: linux-aws: 4.4.0-1062.71 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: 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 -- kernel-stable-master-bug: 1776352 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776356/+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 1776276] Re: linux: 4.17.0-2.3 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Description changed: This bug is for tracking the 4.17.0-2.3 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:Tuesday, 12. June 2018 23:01 UTC + kernel-phase:Uploaded ** Description changed: This bug is for tracking the 4.17.0-2.3 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:Tuesday, 12. June 2018 23:01 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/1776276 Title: linux: 4.17.0-2.3 -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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: Fix Released 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-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-2.3 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:Tuesday, 12. June 2018 23:01 UTC kernel-phase:Uploaded -- swm properties -- phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776276/+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 1776578] Re: Ubuntu installation stuck at "Installing the 'grub2' package..." every time. Kernel reports "invalid opcode: 0000 [#1] SMP NOPTI" every time.
** Attachment added: "bionic dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776578/+attachment/5151911/+files/bionic%20dmesg.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/1776578 Title: Ubuntu installation stuck at "Installing the 'grub2' package..." every time. Kernel crash every time. Status in grub2 package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Ubuntu 18.04 and 18.10 installation never completes on one particular machine (Apollo Lake N4200). It always ends up stuck at "Installing the 'grub2' package..." The kernel log shows a crash each time. The same installation media works perfectly on other machines. The same machine installs Windows 10 perfectly too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1776578/+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 1776578] [NEW] Ubuntu installation stuck at "Installing the 'grub2' package..." every time. Kernel crash every time.
Public bug reported: Ubuntu 18.04 and 18.10 installation never completes on one particular machine (Apollo Lake N4200). It always ends up stuck at "Installing the 'grub2' package..." The kernel log shows a crash each time. The same installation media works perfectly on other machines. The same machine installs Windows 10 perfectly too. ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: High Status: New ** Tags: apollo-lake bionic cosmic -- 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/1776578 Title: Ubuntu installation stuck at "Installing the 'grub2' package..." every time. Kernel crash every time. Status in grub2 package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Ubuntu 18.04 and 18.10 installation never completes on one particular machine (Apollo Lake N4200). It always ends up stuck at "Installing the 'grub2' package..." The kernel log shows a crash each time. The same installation media works perfectly on other machines. The same machine installs Windows 10 perfectly too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1776578/+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 1776578] Re: Ubuntu installation stuck at "Installing the 'grub2' package..." every time. Kernel reports "invalid opcode: 0000 [#1] SMP NOPTI" every time.
** Attachment added: "bionic Screenshot from 2018-06-10 22-08-01.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776578/+attachment/5151910/+files/bionic%20Screenshot%20from%202018-06-10%2022-08-01.png -- 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/1776578 Title: Ubuntu installation stuck at "Installing the 'grub2' package..." every time. Kernel crash every time. Status in grub2 package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Ubuntu 18.04 and 18.10 installation never completes on one particular machine (Apollo Lake N4200). It always ends up stuck at "Installing the 'grub2' package..." The kernel log shows a crash each time. The same installation media works perfectly on other machines. The same machine installs Windows 10 perfectly too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1776578/+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 1717259] Re: adaptec starfire fails to initializewith recent kernels
*** This bug is a duplicate of bug 1473200 *** https://bugs.launchpad.net/bugs/1473200 ** This bug has been marked a duplicate of bug 1473200 adaptec starfire fails to initialize with pae kernels -- 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/1717259 Title: adaptec starfire fails to initializewith recent kernels Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Re-opening https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1473200 (expired) Adaptec ethernet adapter using starfire driver fails to initialize when recent kernels are used. This hardware/driver can be successfully initialized under a 3.2.0-126-generic kernel (from precise) but initialization is known to fail under 3.13.0-129-generic kernel and under -pae kernel builds of many vintages. initialization also fails under current 4.x series kernel. Full kernel bisect is not yet complete. Specific indication from dmesg: [3.536508] starfire.c:v1.03 7/26/2000 Written by Donald Becker (unofficial 2.2/2.4 kernel port, version 2.1, July 6, 2008) [3.536509] starfire: polling (NAPI) enabled [3.536771] ioremap: invalid physical address fe48 [3.536773] [ cut here ] [3.536784] WARNING: CPU: 1 PID: 115 at /build/linux-CK3pdl/linux-4.4.0/arch/x86/mm/ioremap.c:104 __ioremap_caller+0x40f/0x440() [3.536790] Modules linked in: starfire(+) mii fjes floppy(+) [3.536795] CPU: 1 PID: 115 Comm: systemd-udevd Not tainted 4.4.0-93-generic #116-Ubuntu [3.536797] Hardware name: Intel/SE7501BR2S, BIOS SBR20.86B.0082.P23.050407173004/07/2005 [3.536805] c1ae9967 73b5a5ce 0286 c01ddb90 c13add2f c19d0e40 c01ddbc0 [3.536811] c1070387 c19d8dd4 0001 0073 c19d0e40 0068 c105fe2f c105fe2f [3.536818] 0fff fe4f c01ddbd0 c1070492 0009 c01ddc3c [3.536819] Call Trace: [3.536829] [] dump_stack+0x58/0x79 [3.536835] [] warn_slowpath_common+0x87/0xc0 [3.536840] [] ? __ioremap_caller+0x40f/0x440 [3.536843] [] ? __ioremap_caller+0x40f/0x440 [3.536847] [] warn_slowpath_null+0x22/0x30 [3.536850] [] __ioremap_caller+0x40f/0x440 [3.536855] [] ? __pci_request_region+0xb4/0x180 [3.536861] [] ? starfire_init_one+0xc6/0x680 [starfire] [3.536866] [] ? starfire_init_one+0xc6/0x680 [starfire] [3.536869] [] ioremap_nocache+0x1f/0x30 [3.536874] [] ? starfire_init_one+0xc6/0x680 [starfire] [3.536879] [] starfire_init_one+0xc6/0x680 [starfire] [3.536885] [] ? __pm_runtime_resume+0x51/0x80 [3.536889] [] pci_device_probe+0x7b/0xf0 [3.536894] [] ? devices_kset_move_last+0x2d/0xa0 [3.536899] [] driver_probe_device+0x1f9/0x4a0 [3.536904] [] ? sysfs_create_dir_ns+0x37/0x90 [3.536907] [] ? pci_match_device+0xdc/0x100 [3.536911] [] __driver_attach+0x79/0x80 [3.536915] [] ? driver_probe_device+0x4a0/0x4a0 [3.536918] [] bus_for_each_dev+0x57/0xa0 [3.536921] [] driver_attach+0x1e/0x20 [3.536925] [] ? driver_probe_device+0x4a0/0x4a0 [3.536928] [] bus_add_driver+0x1ef/0x290 [3.536931] [] ? 0xf8465000 [3.536933] [] ? 0xf8465000 [3.536936] [] driver_register+0x5d/0xf0 [3.536939] [] __pci_register_driver+0x33/0x40 [3.536944] [] starfire_init+0x2b/0x1000 [starfire] [3.536948] [] do_one_initcall+0xaa/0x200 [3.536951] [] ? 0xf8465000 [3.536955] [] ? kfree+0x120/0x130 [3.536958] [] ? kmem_cache_alloc_trace+0x185/0x1e0 [3.536964] [] ? do_init_module+0x21/0x1a6 [3.536967] [] ? do_init_module+0x21/0x1a6 [3.536970] [] do_init_module+0x50/0x1a6 [3.536975] [] load_module+0x1533/0x1a40 [3.536979] [] ? copy_module_from_fd.isra.53+0xf9/0x190 [3.536984] [] SyS_finit_module+0xa5/0xf0 [3.536988] [] ? vm_mmap_pgoff+0xa3/0xc0 [3.536993] [] do_fast_syscall_32+0x8d/0x150 [3.536998] [] sysenter_past_esp+0x3d/0x61 [3.537001] ---[ end trace 2c05306d6389bc20 ]--- [3.537005] starfire :08:04.0: cannot remap 0x8 @ 0xfe48, aborting [3.537162] ioremap: invalid physical address fe38 [3.537166] starfire :08:05.0: cannot remap 0x8 @ 0xfe38, aborting [3.537308] ioremap: invalid physical address fe30 [3.537313] starfire :08:06.0: cannot remap 0x8 @ 0xfe30, aborting [3.537453] ioremap: invalid physical address fe20 Additional information: ~# lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 # uname -a Linux trafcap4 4.4.0-93-generic #116-Ubuntu SMP Fri Aug 11 21:17:52 UTC 2017 i686 i686 i686 GNU/Linux # cat
[Kernel-packages] [Bug 1771823] Re: Please include ax88179_178a and r8152 modules in d-i udeb
** Changed in: linux (Ubuntu Cosmic) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771823 Title: Please include ax88179_178a and r8152 modules in d-i udeb Status in debian-installer package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: r8152 is used in a thunderbolt-connected docking station and ax88179_178a by an external USB dongle. Despite having two nics connected i can't install Bionic. :-) This is probably a subset of the modules to be included when fixing LP: #1503218. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1771823/+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 1776358] Re: linux-kvm: 4.4.0-1028.33 -proposed tracker
** Summary changed: - linux-kvm: -proposed tracker + linux-kvm: 4.4.0-1028.33 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** 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) => Khaled El Mously (kmously) -- 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/1776358 Title: linux-kvm: 4.4.0-1028.33 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: 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 -- kernel-stable-master-bug: 1776352 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776358/+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 532137]
Mass closure: This bug has been untouched for more than six years, and is not obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases. -- 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/532137 Title: Wacom Intuos2 tablet hotplug only works once after booting Status in X.Org X server: Invalid Status in linux package in Ubuntu: Incomplete Status in xf86-input-wacom package in Ubuntu: Incomplete Bug description: Binary package hint: xserver-xorg-input-wacom The following two tablets do not work out plug-and-play of the box in Lucid: 056a:0041 Wacom Co., Ltd Intuos2 4x5 056a:0044 Wacom Co., Ltd Intuos2 12x12 messages/syslog: Mar 4 14:17:37 cool kernel: [94581.248021] usb 3-2: new full speed USB device using uhci_hcd and address 6 Mar 4 14:17:37 cool kernel: [94581.416147] usb 3-2: configuration #1 chosen from 1 choice Mar 4 14:17:37 cool kernel: [94581.419397] input: Wacom Intuos2 4x5 as /devices/pci:00/:00:1a.0/usb3/3-2/3-2:1.0/input/input18 ProblemType: Bug Architecture: i386 Date: Thu Mar 4 14:36:17 2010 DistroRelease: Ubuntu 10.04 Package: xserver-xorg-input-wacom 1:0.10.3+20100109-1ubuntu1 ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-15-generic root=/dev/mapper/hostname-root ro quiet splash ProcEnviron: PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-15.22-generic SourcePackage: nvidia-graphics-drivers Uname: Linux 2.6.32-15-generic i686 dmi.bios.date: 06/05/2006 dmi.bios.vendor: Intel Corp. dmi.bios.version: MQ96510J.86A.0372.2006.0605.1717 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DG965MQ dmi.board.vendor: Intel Corporation dmi.board.version: AAD37419-102 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrMQ96510J.86A.0372.2006.0605.1717:bd06/05/2006:svn:pn:pvr:rvnIntelCorporation:rnDG965MQ:rvrAAD37419-102:cvn:ct2:cvr: glxinfo: Error: [Errno 2] No such file or directory system: distro: Ubuntu codename: lucidarchitecture: i686kernel: 2.6.32-15-generic To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/532137/+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 1776356] Re: linux-aws: 4.4.0-1062.71 -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-aws in Ubuntu. https://bugs.launchpad.net/bugs/1776356 Title: linux-aws: 4.4.0-1062.71 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: 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 -- kernel-stable-master-bug: 1776352 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776356/+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 1717259] Re: adaptec starfire fails to initializewith recent kernels
Launchpad has imported 1 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=198035. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2017-11-29T14:30:48+00:00 sph0lt0n wrote: In drivers/net/ethernet/adaptec/starfire.c at line 653, ioaddr is declared as a (signed) long. This should instead be declared as an unsigned long, as memory addresses cannot really be negative. This allows ioremap() to correctly remap the address in a >32 bit context. See additional bug details in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1717259 Impact: Adaptec ethernet hardware utilizing the starfire driver fails to initialize with 4.x series kernels and 3.x pae kernels. Steps to reproduce: Attempt to load current starfire module on a system with this hardware installed: modprobe -v starfire Actual Results: Output from dmesg when loading current starfire module on system with this hardware equipped: [ 1109.362648] ioremap: invalid physical address fe48 [ 1109.362657] starfire :08:04.0: cannot Remap 0x8 @ 0xfe48, aborting Proposed patch: Modify line 653 to declare ioaddr as an unsigned long int. 653 unsigned long ioaddr; Expected Results: Output from dmesg when loading modified starfire module on system with this hardware equipped: [ 1237.456827] eth2: Adaptec Starfire 6915 at f8a0, 00:00:d1:ef:f6:d1, IRQ 25. [ 1237.488583] starfire :08:04.0 eth23: renamed from eth2 [ 1237.655434] eth23: MII PHY found at address 1, status 0x7809 advertising 0x01e1. [ 1237.655441] eth23: scatter-gather and hardware TCP cksumming enabled. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1717259/comments/15 ** Changed in: linux Status: Unknown => Confirmed ** Changed in: linux Importance: Unknown => 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/1717259 Title: adaptec starfire fails to initializewith recent kernels Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Re-opening https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1473200 (expired) Adaptec ethernet adapter using starfire driver fails to initialize when recent kernels are used. This hardware/driver can be successfully initialized under a 3.2.0-126-generic kernel (from precise) but initialization is known to fail under 3.13.0-129-generic kernel and under -pae kernel builds of many vintages. initialization also fails under current 4.x series kernel. Full kernel bisect is not yet complete. Specific indication from dmesg: [3.536508] starfire.c:v1.03 7/26/2000 Written by Donald Becker (unofficial 2.2/2.4 kernel port, version 2.1, July 6, 2008) [3.536509] starfire: polling (NAPI) enabled [3.536771] ioremap: invalid physical address fe48 [3.536773] [ cut here ] [3.536784] WARNING: CPU: 1 PID: 115 at /build/linux-CK3pdl/linux-4.4.0/arch/x86/mm/ioremap.c:104 __ioremap_caller+0x40f/0x440() [3.536790] Modules linked in: starfire(+) mii fjes floppy(+) [3.536795] CPU: 1 PID: 115 Comm: systemd-udevd Not tainted 4.4.0-93-generic #116-Ubuntu [3.536797] Hardware name: Intel/SE7501BR2S, BIOS SBR20.86B.0082.P23.050407173004/07/2005 [3.536805] c1ae9967 73b5a5ce 0286 c01ddb90 c13add2f c19d0e40 c01ddbc0 [3.536811] c1070387 c19d8dd4 0001 0073 c19d0e40 0068 c105fe2f c105fe2f [3.536818] 0fff fe4f c01ddbd0 c1070492 0009 c01ddc3c [3.536819] Call Trace: [3.536829] [] dump_stack+0x58/0x79 [3.536835] [] warn_slowpath_common+0x87/0xc0 [3.536840] [] ? __ioremap_caller+0x40f/0x440 [3.536843] [] ? __ioremap_caller+0x40f/0x440 [3.536847] [] warn_slowpath_null+0x22/0x30 [3.536850] [] __ioremap_caller+0x40f/0x440 [3.536855] [] ? __pci_request_region+0xb4/0x180 [3.536861] [] ? starfire_init_one+0xc6/0x680 [starfire] [3.536866] [] ? starfire_init_one+0xc6/0x680 [starfire] [3.536869] [] ioremap_nocache+0x1f/0x30 [3.536874] [] ? starfire_init_one+0xc6/0x680 [starfire] [3.536879] [] starfire_init_one+0xc6/0x680 [starfire] [3.536885] [] ? __pm_runtime_resume+0x51/0x80 [3.536889] [] pci_device_probe+0x7b/0xf0 [3.536894] [] ? devices_kset_move_last+0x2d/0xa0 [3.536899] [] driver_probe_device+0x1f9/0x4a0 [3.536904] [] ? sysfs_create_dir_ns+0x37/0x90 [3.536907] [] ? pci_match_device+0xdc/0x100 [3.536911] [] __driver_attach+0x79/0x80 [
[Kernel-packages] [Bug 1767124] Re: bluetoothd crashed with SIGILL in agent_get() from adapter_register()
Thanks. We call that "Fix Released" if any release contains a fix. In order to get a fix into 16.04 though, we would need to know exactly which code change between versions 5.37 and 5.46 fixed it. ** Changed in: bluez (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1767124 Title: bluetoothd crashed with SIGILL in agent_get() from adapter_register() Status in bluez package in Ubuntu: Fix Released Bug description: systemctl status bluetooth.service ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: failed (Result: core-dump) since Don 2018-04-26 16:16:36 CEST; 2min 25s ago Docs: man:bluetoothd(8) Process: 1458 ExecStart=/usr/lib/bluetooth/bluetoothd (code=dumped, signal=ILL) Main PID: 1458 (code=dumped, signal=ILL) Status: "Running" Apr 26 16:16:35 tiger systemd[1]: Starting Bluetooth service... Apr 26 16:16:35 tiger bluetoothd[1458]: Bluetooth daemon 5.37 Apr 26 16:16:35 tiger systemd[1]: Started Bluetooth service. Apr 26 16:16:35 tiger bluetoothd[1458]: Starting SDP server Apr 26 16:16:35 tiger bluetoothd[1458]: Bluetooth management interface 1.14 initialized Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Main process exited, code=dumped, status=4/ILL Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Unit entered failed state. Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Failed with result 'core-dump'. Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Start request repeated too quickly. Apr 26 16:16:36 tiger systemd[1]: Failed to start Bluetooth service. sudo gdb /usr/lib/bluetooth/bluetoothd ... Program received signal SIGILL, Illegal instruction. agent_get (owner=owner@entry=0x0) at src/agent.c:267 267 src/agent.c: Datei oder Verzeichnis nicht gefunden. (gdb) bt #0 agent_get (owner=owner@entry=0x0) at src/agent.c:267 #1 0x555d861b in adapter_register (adapter=0x5587fed0) at src/adapter.c:7434 #2 read_info_complete (status=, length=, param=, user_data=0x5587fed0) at src/adapter.c:7897 #3 0x55602656 in request_complete (mgmt=mgmt@entry=0x55879ef0, status=, opcode=opcode@entry=4, index=index@entry=0, length=length@entry=280, param=0x55879f79) at src/shared/mgmt.c:261 #4 0x5560311c in can_read_data (io=, user_data=0x55879ef0) at src/shared/mgmt.c:353 #5 0x5560ee25 in watch_callback (channel=, cond=, user_data=) at src/shared/io-glib.c:170 #6 0x77b1004a in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x77b103f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x77b10712 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x5557009d in main (argc=1, argv=0x7fffe658) at src/main.c:687 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1767124/+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 532137] Re: Wacom Intuos2 tablet hotplug only works once after booting
** Changed in: xorg-server Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/532137 Title: Wacom Intuos2 tablet hotplug only works once after booting Status in X.Org X server: Invalid Status in linux package in Ubuntu: Incomplete Status in xf86-input-wacom package in Ubuntu: Incomplete Bug description: Binary package hint: xserver-xorg-input-wacom The following two tablets do not work out plug-and-play of the box in Lucid: 056a:0041 Wacom Co., Ltd Intuos2 4x5 056a:0044 Wacom Co., Ltd Intuos2 12x12 messages/syslog: Mar 4 14:17:37 cool kernel: [94581.248021] usb 3-2: new full speed USB device using uhci_hcd and address 6 Mar 4 14:17:37 cool kernel: [94581.416147] usb 3-2: configuration #1 chosen from 1 choice Mar 4 14:17:37 cool kernel: [94581.419397] input: Wacom Intuos2 4x5 as /devices/pci:00/:00:1a.0/usb3/3-2/3-2:1.0/input/input18 ProblemType: Bug Architecture: i386 Date: Thu Mar 4 14:36:17 2010 DistroRelease: Ubuntu 10.04 Package: xserver-xorg-input-wacom 1:0.10.3+20100109-1ubuntu1 ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-15-generic root=/dev/mapper/hostname-root ro quiet splash ProcEnviron: PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-15.22-generic SourcePackage: nvidia-graphics-drivers Uname: Linux 2.6.32-15-generic i686 dmi.bios.date: 06/05/2006 dmi.bios.vendor: Intel Corp. dmi.bios.version: MQ96510J.86A.0372.2006.0605.1717 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DG965MQ dmi.board.vendor: Intel Corporation dmi.board.version: AAD37419-102 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrMQ96510J.86A.0372.2006.0605.1717:bd06/05/2006:svn:pn:pvr:rvnIntelCorporation:rnDG965MQ:rvrAAD37419-102:cvn:ct2:cvr: glxinfo: Error: [Errno 2] No such file or directory system: distro: Ubuntu codename: lucidarchitecture: i686kernel: 2.6.32-15-generic To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/532137/+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
Re: [Kernel-packages] [Bug 1773704] Re: Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset in Bionic 18.04
No, premature. Bug still exists. I'll try your kernel at the next sitting. -Jeff On Tuesday, May 29, 2018, 1:11:03 PM PDT, Joseph Salisbury wrote: I built a patched test kernel. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1773704 Can you test this kernel and see if it resolves this bug? Note about installing test kernels: • If the test kernel is prior to 4.15(Bionic) you need to install the linux-image and linux-image-extra .deb packages. • If the test kernel is 4.15(Bionic) or newer, you need to install the linux-modules, linux-modules-extra and linux-image-unsigned .deb packages. Thanks in advance! -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1773704 Title: Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset in Bionic 18.04 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: A typo at line 184 in /drivers/usb/host/xhci-pci.c trashes a good fix. 183 if (pdev->vendor == PCI_VENDOR_ID_RENESAS && 184 pdev->device == 0x0014) 185 xhci->quirks |= XHCI_TRUST_TX_LENGTH; 186 if (pdev->vendor == PCI_VENDOR_ID_RENESAS && 187 pdev->device == 0x0015) 188 xhci->quirks |= XHCI_RESET_ON_RESUME; Line 184 should be identical to line 187, ie: should read pdev->device == 0x0015) I've compiled the kernel both with and without the typo. As written, hundreds of messages fill dmesg suggesting XHCI_TRUST_TX_LENGTH may be needed when zoneminder tries to access my USB webcams. With the fix applied as I've suggested the messages disappear. The typo is still present in 4.15.0-22.24 For more background, you may refer to bug ID #1710548 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773704/+subscriptions -- 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/1773704 Title: Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset in Bionic 18.04 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: A typo at line 184 in /drivers/usb/host/xhci-pci.c trashes a good fix. 183 if (pdev->vendor == PCI_VENDOR_ID_RENESAS && 184 pdev->device == 0x0014) 185 xhci->quirks |= XHCI_TRUST_TX_LENGTH; 186 if (pdev->vendor == PCI_VENDOR_ID_RENESAS && 187 pdev->device == 0x0015) 188 xhci->quirks |= XHCI_RESET_ON_RESUME; Line 184 should be identical to line 187, ie: should read pdev->device == 0x0015) I've compiled the kernel both with and without the typo. As written, hundreds of messages fill dmesg suggesting XHCI_TRUST_TX_LENGTH may be needed when zoneminder tries to access my USB webcams. With the fix applied as I've suggested the messages disappear. The typo is still present in 4.15.0-22.24 For more background, you may refer to bug ID #1710548 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773704/+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 1776449] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1: bcmwl kernel module failed to build [error: implicit declaration of function ‘init_timer’]
*** This bug is a duplicate of bug 1757008 *** https://bugs.launchpad.net/bugs/1757008 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1757008, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Summary changed: - bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1: bcmwl kernel module failed to build + bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1: bcmwl kernel module failed to build [error: implicit declaration of function ‘init_timer’] ** This bug has been marked a duplicate of bug 1757008 bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl kernel module failed to build [error: implicit declaration of function ‘init_timer’] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1776449 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1: bcmwl kernel module failed to build [error: implicit declaration of function ‘init_timer’] Status in bcmwl package in Ubuntu: New Bug description: ndswrapper ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1 ProcVersionSignature: Ubuntu 4.15.0-15.16~16.04.1-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 DKMSKernelVersion: 4.15.0-23-generic Date: Tue Jun 12 14:52:04 2018 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.1:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2: error: implicit declaration of function ‘init_timer’ [-Werror=implicit-function-declaration] InstallationDate: Installed on 2016-09-21 (629 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.1 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1776449/+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
