[Kernel-packages] [Bug 1797670] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) 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/1797670 Title: upgrading to 16.04 bug Status in linux package in Ubuntu: Confirmed Bug description: lsb_release -rd Description: Ubuntu 14.04.2 LTS Release: 14.04 apt-cache policy pkgname N: Unable to locate package pkgname ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-53-generic 3.13.0-53.87 ProcVersionSignature: Ubuntu 3.13.0-53.87-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.10 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: taktak 2369 F pulseaudio CurrentDesktop: Unity Date: Sat Oct 13 05:57:00 2018 HibernationDevice: RESUME=UUID=e21c4184-fae7-45c6-bc5b-b10babb22ea3 InstallationDate: Installed on 2012-12-06 (2136 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) MachineType: Dell Inc. Vostro 1015 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=1f09aafa-4f9a-489b-9b7a-96d0efa55993 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-53-generic N/A linux-backports-modules-3.13.0-53-generic N/A linux-firmware 1.127.11 SourcePackage: linux StagingDrivers: keucr UpgradeStatus: Upgraded to trusty on 2018-10-13 (0 days ago) WifiSyslog: Oct 13 05:52:19 Takostro kernel: [ 657.752075] ERROR @wl_dev_intvar_get : error (-1) Oct 13 05:52:19 Takostro kernel: [ 657.752081] ERROR @wl_cfg80211_get_tx_power : error (-1) dmi.bios.date: 09/17/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 047MWF dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd09/17/2009:svnDellInc.:pnVostro1015:pvr:rvnDellInc.:rn047MWF:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Vostro 1015 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797670/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797670] [NEW] upgrading to 16.04 bug
Public bug reported: lsb_release -rd Description:Ubuntu 14.04.2 LTS Release:14.04 apt-cache policy pkgname N: Unable to locate package pkgname ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-53-generic 3.13.0-53.87 ProcVersionSignature: Ubuntu 3.13.0-53.87-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.10 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: taktak 2369 F pulseaudio CurrentDesktop: Unity Date: Sat Oct 13 05:57:00 2018 HibernationDevice: RESUME=UUID=e21c4184-fae7-45c6-bc5b-b10babb22ea3 InstallationDate: Installed on 2012-12-06 (2136 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) MachineType: Dell Inc. Vostro 1015 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=1f09aafa-4f9a-489b-9b7a-96d0efa55993 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-53-generic N/A linux-backports-modules-3.13.0-53-generic N/A linux-firmware 1.127.11 SourcePackage: linux StagingDrivers: keucr UpgradeStatus: Upgraded to trusty on 2018-10-13 (0 days ago) WifiSyslog: Oct 13 05:52:19 Takostro kernel: [ 657.752075] ERROR @wl_dev_intvar_get : error (-1) Oct 13 05:52:19 Takostro kernel: [ 657.752081] ERROR @wl_cfg80211_get_tx_power : error (-1) dmi.bios.date: 09/17/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 047MWF dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd09/17/2009:svnDellInc.:pnVostro1015:pvr:rvnDellInc.:rn047MWF:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Vostro 1015 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 staging trusty -- 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/1797670 Title: upgrading to 16.04 bug Status in linux package in Ubuntu: New Bug description: lsb_release -rd Description: Ubuntu 14.04.2 LTS Release: 14.04 apt-cache policy pkgname N: Unable to locate package pkgname ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-53-generic 3.13.0-53.87 ProcVersionSignature: Ubuntu 3.13.0-53.87-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.10 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: taktak 2369 F pulseaudio CurrentDesktop: Unity Date: Sat Oct 13 05:57:00 2018 HibernationDevice: RESUME=UUID=e21c4184-fae7-45c6-bc5b-b10babb22ea3 InstallationDate: Installed on 2012-12-06 (2136 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) MachineType: Dell Inc. Vostro 1015 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=1f09aafa-4f9a-489b-9b7a-96d0efa55993 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-53-generic N/A linux-backports-modules-3.13.0-53-generic N/A linux-firmware 1.127.11 SourcePackage: linux StagingDrivers: keucr UpgradeStatus: Upgraded to trusty on 2018-10-13 (0 days ago) WifiSyslog: Oct 13 05:52:19 Takostro kernel: [ 657.752075] ERROR @wl_dev_intvar_get : error (-1) Oct 13 05:52:19 Takostro kernel: [ 657.752081] ERROR @wl_cfg80211_get_tx_power : error (-1) dmi.bios.date: 09/17/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 047MWF dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd09/17/2009:svnDellInc.:pnVostro1015:pvr:rvnDellInc.:rn047MWF:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Vostro 1015 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797670/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1543418] Re: Closing lid causes system hang
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1543418 Title: Closing lid causes system hang Status in linux package in Ubuntu: Expired Bug description: I have been having this problem for a past few weeks. I have been using this system for almost 1 year. I use with the power setting to suspend my system when I close the lid. In the past few weeks sometimes when I close the lid, the system doesn't gets suspended. Instead, it gets stuck. When i reopen the lid screen will be back and nothing can bring the system back. I have to restart the system by pressing the power key. No key is working during this state. I tried pressing num lock and no response. It happened rarely before. But for past few days, my system has been getting stuck like this more. Before this, I used to have system crash suddenly and lose all data without any reasons. I am fairly new to ubuntu I don't know how to diagnose these things. Please help me. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543418/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1687274] Re: Boot fails waiting for /dev/disk/by-uuid
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1687274 Title: Boot fails waiting for /dev/disk/by-uuid Status in linux package in Ubuntu: Expired Bug description: The system is stuck waiting 90 seconds for the /dev/disk/by-uuid/* devices to show up. When dropping me to a shell, they do exist. Forcing the system to fsck (by removing power) makes no difference. After rebooting 1-5 times it suddenly completes booting. So it seems it might be a race condition. = Workaround = If I boot once in recovery mode, then the next boot will mostly complete just fine. OK as a workaround, but a horrible solution. I can even just run `systemctl reboot` from recovery mode - no need to boot fully. Running `reboot`, however, does not work. Attached: working$ cat ls-dev-disk-by-uuid working$ cat journalctl-xb failing$ cat ls-dev-disk-by-uuid failing$ cat journalctl-xb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687274/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786382] Re: Repeated crashes in cifs kernel code
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786382 Title: Repeated crashes in cifs kernel code Status in linux package in Ubuntu: Expired Bug description: While trying to write a bunch of files in quick succession to a CIFS filesystem on my Synology NAS, I start getting kernel oopses and the terminal windows in which I'm doing the file operations -- whose current directories are inside the CIFS filesystem -- suddenly crashing. For some reason apport is not picking up on this so I'm reporting manually. Here's one of the oopses: [ 871.470183] general protection fault: [#4] SMP PTI [ 871.470188] Modules linked in: rfcomm xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 bridge stp llc devlink ebtable_filter ebtables pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) cachefiles md4 nfsv3 nfs_acl rpcsec_gss_krb5 auth_rpcgss nfsv4 nls_utf8 cifs nfs lockd ccm grace fscache xt_multiport cmac bnep binfmt_misc ip6t_REJECT nf_reject_ipv6 nls_iso8859_1 xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 xt_comment xt_limit xt_tcpudp snd_hda_codec_hdmi xt_addrtype intel_rapl sparse_keymap wmi_bmof x86_pkg_temp_thermal intel_powerclamp nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack coretemp kvm_intel kvm snd_hda_codec_realtek arc4 snd_hda_codec_generic snd_hda_intel irqbypass uvcvideo snd_hda_codec btusb snd_usb_audio [ 871.470259] btrtl videobuf2_vmalloc snd_hda_core btbcm videobuf2_memops crct10dif_pclmul btintel snd_usbmidi_lib videobuf2_v4l2 snd_hwdep videobuf2_core bluetooth input_leds snd_seq_midi videodev snd_seq_midi_event snd_pcm crc32_pclmul snd_rawmidi media ghash_clmulni_intel ecdh_generic snd_seq cryptd intel_cstate snd_seq_device intel_rapl_perf iwlmvm mac80211 ip6table_filter ip6_tables snd_timer iwlwifi snd nf_conntrack_netbios_ns nvidia_uvm(POE) cfg80211 soundcore serio_raw nf_conntrack_broadcast shpchp wmi mei_me intel_pch_thermal acpi_pad mei mac_hid tpm_crb nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack libcrc32c sch_fq_codel iptable_filter parport_pc ppdev sunrpc lp parport ip_tables x_tables autofs4 hid_logitech_hidpp hid_generic hid_logitech_dj uas usbhid usb_storage hid dm_mirror dm_region_hash [ 871.470329] dm_log nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse drm r8169 ahci ipmi_devintf mii libahci ipmi_msghandler video [ 871.470351] CPU: 6 PID: 8614 Comm: nautilus Tainted: P DOE 4.15.0-30-generic #32-Ubuntu [ 871.470354] Hardware name: Acer Predator G6-710/Predator G6-710, BIOS R01-A4 05/18/2016 [ 871.470362] RIP: 0010:kmem_cache_alloc+0x81/0x1b0 [ 871.470365] RSP: 0018:bbed47c9f618 EFLAGS: 00010202 [ 871.470369] RAX: 65b1b269c87f4446 RBX: 65b1b269c87f4446 RCX: 0ee9 [ 871.470372] RDX: 0ee8 RSI: 01011200 RDI: 0002b5c0 [ 871.470375] RBP: bbed47c9f648 R08: 9e312edab5c0 R09: [ 871.470378] R10: bbed47c9f870 R11: c1ab4000 R12: 01011200 [ 871.470381] R13: 9e311bdbdb00 R14: 65b1b269c87f4446 R15: 9e311bdbdb00 [ 871.470385] FS: 7f2f11675700() GS:9e312ed8() knlGS: [ 871.470388] CS: 0010 DS: ES: CR0: 80050033 [ 871.470391] CR2: 55ba011c7100 CR3: 000451898004 CR4: 003606e0 [ 871.470395] DR0: DR1: DR2: [ 871.470398] DR3: DR6: fffe0ff0 DR7: 0400 [ 871.470400] Call Trace: [ 871.470408] ? mempool_alloc_slab+0x15/0x20 [ 871.470415] ? wait_woken+0x80/0x80 [ 871.470419] mempool_alloc_slab+0x15/0x20 [ 871.470424] mempool_alloc+0x71/0x190 [ 871.470453] cifs_small_buf_get+0x1a/0x30 [cifs] [ 871.470482] small_smb2_init+0x62/0xb0 [cifs] [ 871.470511] SMB2_open+0xc3/0xb50 [cifs] [ 871.470535] ? cifsConvertToUTF16+0x1e9/0x420 [cifs] [ 871.470558] ? cifs_strndup_to_utf16+0xbd/0x110 [cifs] [ 871.470585] smb2_open_op_close+0xad/0x220 [cifs] [ 871.470609] ? smb2_open_op_close+0xad/0x220 [cifs] [ 871.470616] ? alloc_pages_current+0x6a/0xe0 [ 871.470640] smb2_query_path_info+0x74/0xf0 [cifs] [ 871.470667] cifs_get_inode_info+0x4eb/0xab0 [cifs] [ 871.470692] ? build_path_from_dentry_optional_prefix+0x179/0x3e0 [cifs] [ 871.470715] cifs_revalidate_dentry_attr+0x1d8/0x250 [cifs] [ 871.470739] cifs_revalidate_dentry+0x13/0x30 [cifs] [ 871.470760] cifs_d_revalidate+0x27/0xb0 [cifs] [ 871.470765] d_revalidate.part.18+0x10/0x20 [ 871.470770] lookup_fast+0x307/0x320 [
[Kernel-packages] [Bug 1786619] Re: Cannot able to upgrade from 16.04 to 18.04
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786619 Title: Cannot able to upgrade from 16.04 to 18.04 Status in linux package in Ubuntu: Expired Bug description: package linux-headers-4.4.0-131 4.4.0-131.157 failed to install/upgrade: package linux-headers-4.4.0-131 is not ready for configuration cannot configure (current status 'half-installed') Processing triggers for libc-bin (2.23-0ubuntu10) ... dpkg: error processing package linux-headers-4.4.0-131 (--configure): package linux-headers-4.4.0-131 is not ready for configuration cannot configure (current status 'half-installed') Errors were encountered while processing: linux-headers-4.4.0-131 E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.4.0-131 4.4.0-131.157 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: linux-headers-4.4.0-131: Configure NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: argha 2096 F pulseaudio /dev/snd/controlC0: argha 2096 F pulseaudio Date: Sat Aug 11 19:54:47 2018 DpkgTerminalLog: dpkg: error processing package linux-headers-4.4.0-131 (--configure): package linux-headers-4.4.0-131 is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package linux-headers-4.4.0-131 is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=cc8a-0f65-4d75-bf10-dd906f85e00b InstallationDate: Installed on 2017-08-12 (363 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 001 Device 003: ID 04f2:b40e Chicony Electronics Co., Ltd HP Truevision HD camera Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP 15 Notebook PC PackageArchitecture: all ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-131-generic.efi.signed root=UUID=e95dbb4f-5fb3-4ee3-8ad1-155b711b1a4c ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-headers-4.4.0-131 4.4.0-131.157 failed to install/upgrade: package linux-headers-4.4.0-131 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.18 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2212 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.28 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.18:bd05/21/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr0991100600087:rvnHewlett-Packard:rn2212:rvr86.28:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP 15 Notebook PC dmi.product.version: 0991100600087 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786341] Re: Touchpad doesn't work
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786341 Title: Touchpad doesn't work Status in linux package in Ubuntu: Expired Bug description: Hello! I have Asus of TUF GAMING FX504 series. When I connect external mouse it works. However touchpad doesn't response at all. Output of "cat /proc/bus/input/devices" command doesn't show any kind of touchpad device. I have Ubuntu 18.04.1 LTS installed. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: firefly1445 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-06 (34 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:5666 IMC Networks Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 005: ID 2717:5001 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. TUF GAMING FX504GD_FX80GD Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=fa887fbb-ea9a-48ca-996f-8246577c2af3 ro quiet splash nouveau.modeset=0 acpi_backlight=vendor vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX504GD.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX504GD 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.:bvrFX504GD.310:bd05/11/2018:svnASUSTeKCOMPUTERINC.:pnTUFGAMINGFX504GD_FX80GD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX504GD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF GAMING dmi.product.name: TUF GAMING FX504GD_FX80GD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: firefly1445 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-06 (34 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:5666 IMC Networks Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 005: ID 2717:5001 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. TUF GAMING FX504GD_FX80GD Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=fa887fbb-ea9a-48ca-996f-8246577c2af3 ro quiet splash nouveau.modeset=0 acpi_backlight=vendor vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX504GD.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX504GD 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.:bvrFX504GD.310:bd05/11/2018:svnASUSTeKCOMPUTERINC.:pnTUFGAMINGFX504GD_FX80GD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX504GD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF GAMING dmi.product.name: TUF GAMING FX504GD_FX80GD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about
[Kernel-packages] [Bug 1797669] [NEW] tc filter add after delete get error "No space left on device"
Public bug reported: tc filter seems still leak with ubuntu kernel 4.15.0-36-generic, it can be reproduced with the following steps. ``` tc qdisc add dev eth0 ingress tc filter add dev eth0 ingress protocol ip prio 1 handle 800::1 u32 match ip dst 192.168.5.113/32 police rate 10Mbit burst 10Mbit mtu 64kb drop flowid :1 tc filter add dev eth0 ingress protocol ip prio 1 handle 800::2 u32 match ip dst 192.168.5.46/32 police rate 10Mbit burst 10Mbit mtu 64kb drop flowid :1 tc filter del dev eth0 ingress protocol ip prio 1 handle 800::1 u32 match ip dst 192.168.5.113/32 police rate 10Mbit burst 10Mbit mtu 64kb drop flowid :1 tc filter add dev eth0 ingress protocol ip prio 1 handle 800::1 u32 match ip dst 192.168.5.113/32 police rate 10Mbit burst 10Mbit mtu 64kb drop flowid :1 ``` the last command will get this error ``` RTNETLINK answers: No space left on device We have an error talking to the kernel ``` upstream 4.15(eol) also have this issue, but 4.16.2 fixed, and ubuntu 4.15.0-36 already patched upstream 4.16.2 fix patch. however this issue still exist, I think the difference between 4.15 and 4.16 caused this issue. please kindly help check it. Thanks. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: tc ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Description changed: - tc filter seems still leaks with ubuntu kernel 4.15.0-36-generic, + tc filter seems still leak with ubuntu kernel 4.15.0-36-generic, it can be reproduced with the following steps. ``` tc qdisc add dev eth0 ingress tc filter add dev eth0 ingress protocol ip prio 1 handle 800::1 u32 match ip dst 192.168.5.113/32 police rate 10Mbit burst 10Mbit mtu 64kb drop flowid :1 tc filter add dev eth0 ingress protocol ip prio 1 handle 800::2 u32 match ip dst 192.168.5.46/32 police rate 10Mbit burst 10Mbit mtu 64kb drop flowid :1 tc filter del dev eth0 ingress protocol ip prio 1 handle 800::1 u32 match ip dst 192.168.5.113/32 police rate 10Mbit burst 10Mbit mtu 64kb drop flowid :1 tc filter add dev eth0 ingress protocol ip prio 1 handle 800::1 u32 match ip dst 192.168.5.113/32 police rate 10Mbit burst 10Mbit mtu 64kb drop flowid :1 ``` the last command will get this error ``` RTNETLINK answers: No space left on device We have an error talking to the kernel ``` upstream 4.15(eol) also have this issue, but 4.16.2 fixed, and ubuntu 4.15.0-36 already patched upstream 4.16.2 fix patch. however this issue still exist, I think the difference between 4.15 and 4.16 caused this issue. please kindly help check it. Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797669 Title: tc filter add after delete get error "No space left on device" Status in linux package in Ubuntu: Confirmed Bug description: tc filter seems still leak with ubuntu kernel 4.15.0-36-generic, it can be reproduced with the following steps. ``` tc qdisc add dev eth0 ingress tc filter add dev eth0 ingress protocol ip prio 1 handle 800::1 u32 match ip dst 192.168.5.113/32 police rate 10Mbit burst 10Mbit mtu 64kb drop flowid :1 tc filter add dev eth0 ingress protocol ip prio 1 handle 800::2 u32 match ip dst 192.168.5.46/32 police rate 10Mbit burst 10Mbit mtu 64kb drop flowid :1 tc filter del dev eth0 ingress protocol ip prio 1 handle 800::1 u32 match ip dst 192.168.5.113/32 police rate 10Mbit burst 10Mbit mtu 64kb drop flowid :1 tc filter add dev eth0 ingress protocol ip prio 1 handle 800::1 u32 match ip dst 192.168.5.113/32 police rate 10Mbit burst 10Mbit mtu 64kb drop flowid :1 ``` the last command will get this error ``` RTNETLINK answers: No space left on device We have an error talking to the kernel ``` upstream 4.15(eol) also have this issue, but 4.16.2 fixed, and ubuntu 4.15.0-36 already patched upstream 4.16.2 fix patch. however this issue still exist, I think the difference between 4.15 and 4.16 caused this issue. please kindly help check it. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797669/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797379] Re: linux: 4.18.0-10.11 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-release Status: New => Confirmed ** Tags removed: block-proposed-cosmic ** Tags removed: block-proposed -- 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/1797379 Title: linux: 4.18.0-10.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: 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: -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797379/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
Darksurf (piroisl33t-u) great-great-great work, we are waiting for the good news. I did the same with AMD. They tried to help me with giving advices but they couldn't fix the tables of course. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: New Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797379] Re: linux: 4.18.0-10.11 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing 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/1797379 Title: linux: 4.18.0-10.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: 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: -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797379/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797379] Re: linux: 4.18.0-10.11 -proposed tracker
** Tags added: regression-testing-passed -- 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/1797379 Title: linux: 4.18.0-10.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: 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: -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797379/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1760338] Re: Touchpad hotkey 'functional' but has no effect in 18.04 (Bionic)
No, they started in a fresh new installation (18.04). Sorry, I can't test it anymore cause I changed to Deepin and, last month, I changed back to Ubuntu but I completely removed gnome and installed DDE as my window manager. So sorry. -- 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/1760338 Title: Touchpad hotkey 'functional' but has no effect in 18.04 (Bionic) Status in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in xinput package in Ubuntu: Confirmed Status in xserver-xorg-input-synaptics package in Ubuntu: Confirmed Bug description: All the Fn keys are working (audio, mute, bright, volume and even wifi) except for enable/disable touchpad. No display info and no effect. PS: Fn Bright up/down takes about 3s to work the first time or if not used for about 2 minutes. Volume also have a similar problem but only the first time it is used. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xinput 1.6.2-1build1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.42 Sat Mar 3 04:10:22 PST 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-13ubuntu1) ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Sat Mar 31 15:41:59 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.42, 4.15.0-12-generic, x86_64: installed nvidia, 390.42, 4.15.0-13-generic, x86_64: installed virtualbox, 5.2.8, 4.15.0-12-generic, x86_64: installed virtualbox, 5.2.8, 4.15.0-13-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems HD Graphics 530 [1179:f840] InstallationDate: Installed on 2018-03-09 (21 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 04f2:b446 Chicony Electronics Co., Ltd Bus 001 Device 003: ID 248a:8366 Bus 001 Device 002: ID 04f3:2228 Elan Microelectronics Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TOSHIBA Satellite S55t-C ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=62fa4fcd-f1c6-43f5-a86d-ccaae2565dac ro locale=pt_BR quiet splash vt.handoff=1 SourcePackage: xinput UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.20 dmi.board.name: 06F4 dmi.board.vendor: FF50 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr1.20:bd10/08/2015:svnTOSHIBA:pnSatelliteS55t-C:pvrPSPUGU-00200D:rvnFF50:rn06F4:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Type1Family dmi.product.name: Satellite S55t-C dmi.product.version: PSPUGU-00200D dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1760338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic
Here's a full console log from the failure. https://paste.ubuntu.com/p/zmS7CP7NKr/ -- 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/1797581 Title: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic Status in MAAS: Invalid Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Bug description: Using latest MAAS master, I'm unable to compose a VM over the UI successfully when composed with 2048 MB of RAM. By that I mean that the VM is created, but it fails with a kernel panic. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1797581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795292] Re: ELAN469D touch pad not working
https://bugzilla.kernel.org/show_bug.cgi?id=201393 -- Cristian Aravena Romero (caravena) ** Bug watch added: Linux Kernel Bug Tracker #201393 https://bugzilla.kernel.org/show_bug.cgi?id=201393 ** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=201393 Importance: Unknown Status: Unknown -- 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/1795292 Title: ELAN469D touch pad not working Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: I installed Bionic Beaver and now upgraded to Cosmic Cuttlefish on this Lenovo Ideapad 330S-15ARR laptop. The touch pad doesn't work in either. Some possibly relevant info from dmesg: i2c_hid i2c-ELAN469D:00: i2c-ELAN469D:00 supply vdd not found, using dummy regulator i2c_designware AMDI0010:01: controller timed out ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-7-generic 4.18.0-7.8 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xorbit 2086 F pulseaudio /dev/snd/pcmC1D0p: xorbit 2086 F...m pulseaudio /dev/snd/controlC0: xorbit 2086 F pulseaudio CurrentDesktop: GNOME Date: Sun Sep 30 23:14:26 2018 InstallationDate: Installed on 2018-09-20 (10 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 81FB ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic processor.max_cstate=1 rcu_nocbs=0-7 pcie_aspm=off pci=noaer quiet splash vt.handoff=1 elan_i2c.dyndbg=+p RelatedPackageVersions: linux-restricted-modules-4.18.0-7-generic N/A linux-backports-modules-4.18.0-7-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-09-30 (0 days ago) dmi.bios.date: 06/08/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7WCN22WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330S-15ARR dmi.modalias: dmi:bvnLENOVO:bvr7WCN22WW:bd06/08/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR: dmi.product.family: ideapad 330S-15ARR dmi.product.name: 81FB dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR dmi.product.version: Lenovo ideapad 330S-15ARR dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-09-20 (13 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: cosmic Uname: Linux 4.19.0-041900rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to cosmic on 2018-09-30 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1795292/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795292] Re: ELAN469D touch pad not working
acpidump: 5B10: 39 5F 48 49 44 00 A0 13 93 54 43 50 44 0A 02 A4 9_HIDTCPD... 5B20: 0D 53 59 4E 41 33 32 35 35 00 A0 13 93 54 43 50 .SYNA3255TCP 5B30: 44 0A 03 A4 0D 41 4C 50 53 31 32 31 45 00 A4 0D DALPS121E... 5B40: 45 4C 41 4E 34 36 39 44 00 08 45 49 43 30 11 21 ELAN469D..EIC0.! 5B50: 0A 1E 8E 19 00 01 00 01 02 00 00 01 06 00 80 1A 5B60: 06 00 15 00 5C 5F 53 42 2E 49 32 43 44 00 79 00 \_SB.I2CD.y. 5B70: 08 53 49 43 30 11 21 0A 1E 8E 19 00 01 00 01 02 .SIC0.!. Upon installing libinput, and uninstalling synaptics, all mention of ELAN has disappeared from dmesg, and /dev/input shows nothing related to mouse/ touchpad. Hardware debugging told me nothing useful, other than the device is physically there and receiving power. -- 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/1795292 Title: ELAN469D touch pad not working Status in linux package in Ubuntu: Confirmed Bug description: I installed Bionic Beaver and now upgraded to Cosmic Cuttlefish on this Lenovo Ideapad 330S-15ARR laptop. The touch pad doesn't work in either. Some possibly relevant info from dmesg: i2c_hid i2c-ELAN469D:00: i2c-ELAN469D:00 supply vdd not found, using dummy regulator i2c_designware AMDI0010:01: controller timed out ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-7-generic 4.18.0-7.8 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xorbit 2086 F pulseaudio /dev/snd/pcmC1D0p: xorbit 2086 F...m pulseaudio /dev/snd/controlC0: xorbit 2086 F pulseaudio CurrentDesktop: GNOME Date: Sun Sep 30 23:14:26 2018 InstallationDate: Installed on 2018-09-20 (10 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 81FB ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic processor.max_cstate=1 rcu_nocbs=0-7 pcie_aspm=off pci=noaer quiet splash vt.handoff=1 elan_i2c.dyndbg=+p RelatedPackageVersions: linux-restricted-modules-4.18.0-7-generic N/A linux-backports-modules-4.18.0-7-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-09-30 (0 days ago) dmi.bios.date: 06/08/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7WCN22WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330S-15ARR dmi.modalias: dmi:bvnLENOVO:bvr7WCN22WW:bd06/08/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR: dmi.product.family: ideapad 330S-15ARR dmi.product.name: 81FB dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR dmi.product.version: Lenovo ideapad 330S-15ARR dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-09-20 (13 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: cosmic Uname: Linux 4.19.0-041900rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to cosmic on 2018-09-30 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795292/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796385] Re: watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112]
Hello, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796385/comments/6 This suggests another error -> Bug 1797625 -- Cristian Aravena Romero (caravena) -- 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/1796385 Title: watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112] Status in Linux: Unknown Status in linux package in Ubuntu: Incomplete Bug description: I can use the system for a while, then at random, the screen blinks and freezes. Must reboot. Seems to happen both with Wayland and Xorg. ProblemType: KernelOops DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: greg 2039 F pulseaudio /dev/snd/controlC1: greg 2039 F pulseaudio Date: Tue Oct 2 15:56:23 2018 Failure: oops InstallationDate: Installed on 2018-09-28 (7 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. Default string ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=ce06b10d-2a7f-49db-a15b-85554d9a7e4d ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: X99-UD4-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.:bvrF23:bd06/07/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99-UD4-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1796385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796385] Re: watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112]
Hello, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796385/comments/6 This suggests another error -> Bug 1796385 -- Cristian Aravena Romero (caravena) -- 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/1796385 Title: watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112] Status in Linux: Unknown Status in linux package in Ubuntu: Incomplete Bug description: I can use the system for a while, then at random, the screen blinks and freezes. Must reboot. Seems to happen both with Wayland and Xorg. ProblemType: KernelOops DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: greg 2039 F pulseaudio /dev/snd/controlC1: greg 2039 F pulseaudio Date: Tue Oct 2 15:56:23 2018 Failure: oops InstallationDate: Installed on 2018-09-28 (7 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. Default string ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=ce06b10d-2a7f-49db-a15b-85554d9a7e4d ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: X99-UD4-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.:bvrF23:bd06/07/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99-UD4-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1796385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797654] [NEW] hns3: autoneg settings get lost on down/up
Public bug reported: [Impact] If a user manually disables autonegotiation, that setting will be lost if the link is toggled. [Test Case] sudo ethtool -s enp125s0f2 speed 100 duplex half autoneg off After this, "ethtool enp125s0f2" will show: Advertised auto-negotiation: No If you then run: sudo ifconfig enp125s0f2 down; sudo ifconfig enp125s0f2 up, then ethtool will show: Advertised auto-negotiation: Yes [Fix] b01b7cf19bf4a net: hns3: Fix for information of phydev lost problem when down/up [Regression Risk] Restricted to a single SoC on which the fix was explicitly tested. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Affects: linux (Ubuntu Bionic) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => dann frazier (dannf) -- 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/1797654 Title: hns3: autoneg settings get lost on down/up Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: [Impact] If a user manually disables autonegotiation, that setting will be lost if the link is toggled. [Test Case] sudo ethtool -s enp125s0f2 speed 100 duplex half autoneg off After this, "ethtool enp125s0f2" will show: Advertised auto-negotiation: No If you then run: sudo ifconfig enp125s0f2 down; sudo ifconfig enp125s0f2 up, then ethtool will show: Advertised auto-negotiation: Yes [Fix] b01b7cf19bf4a net: hns3: Fix for information of phydev lost problem when down/up [Regression Risk] Restricted to a single SoC on which the fix was explicitly tested. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797654/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752961] Re: With kernel 4.13 btrfs scans for devices before all devices have been discovered
The packages appear to still be the build from 10/01.
--
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/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Artful:
Won't Fix
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
In Progress
Bug description:
See attached dmesg outputs for booting kernels 4.11.x (working) and
4.13.x (not working).
dmesg-4.11.0-14-good.txt shows the dmesg output when booting kernel 4.11.x.
btrfs scans for devices after all 4 (sda, sdb, sdc, sdd) of the devices have
been discovered by the kernel. The btrfs RAID1 filesystem mounts, and
everything is good.
dmesg-4.13.0-36-fail.txt shows the dmesg output when booting kernel 4.13.x.
btrfs scans for devices after only 2 (sda, sdb) of the devices have been
discovered by the kernel. The btrfs RAID1 filesystem fails to mount ("failed
to read the system array: -5"). The remaining 2 devices (sdc, sdd) are
discovered by the kernel immediately afterward. At the end of the log, I run
`btrfs device scan` and mount the filesystem manually.
Hardware:
HP ProLiant MicroServer Gen8
4x WDC WD20EFRX
---
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code
2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: aplay: device_list:270: no soundcards found...
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
ArecordDevices: arecord: device_list:270: no soundcards found...
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2015-10-15 (933 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
MachineType: HP ProLiant MicroServer Gen8
Package: linux (not installed)
ProcEnviron:
TERM=linux
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-20-generic
root=UUID=d976ab07-8377-46dd-ac6c-f5f7312a8305 ro rootflags=subvol=@
rootdelay=10
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
Tags: bionic apport-hook-error
Uname: Linux 4.15.0-20-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 07/16/2015
dmi.bios.vendor: HP
dmi.bios.version: J06
dmi.chassis.type: 7
dmi.chassis.vendor: HP
dmi.modalias:
dmi:bvnHP:bvrJ06:bd07/16/2015:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:
dmi.product.family: ProLiant
dmi.product.name: ProLiant MicroServer Gen8
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752961/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
I've got some interesting news. I did in fact contact Acer Support and opened a case. Went from Lvl1 to Lvl2 support, was called a couple weeks later with a survey about support, I gave my honest opinion, stating that I don't blame support team as they are limited in what they can do. Today I received a call from LVL3 support! They wanted me to go over my problem in more detail. I let them know of the issues with disassembly and the calling of scopes and functions that do not even exist in the firmware, and that they may be doing something in software with windows drivers to hide it or make it work anyway. He did let me know that they do target the Windows 10 audience and couldn't promise anything, but then I mentioned with the way Windows 10 updates are going I doubt Acer is going to continue to rewrite drivers everytime Microsoft breaks them with their updates, and considering how terrible QA is with windows updates lately having it all just built correctly in firmware to begin with would avoid that. The man agreed and laughed a little. I let him know about iasl and asked if he could have the team look into acpi a little better and that I knew they had dealt with linpus in the past which is effectively just fedora, so I know they have some experience with Linux. I also mentioned my model wasn't the only one affected by these oddities and there were threads in ubuntu, fedora, and the linux kernel's bug system. He agreed to pass on the issues and information to the engineering team in Taiwan. Fingers crossed. So far the customer support has blown away Samsung. I'm not holding my breath for a fix, but I am impressed I got this far. The LVL3 support guy said he'd call me back when he got a response from Taiwan's Engineers. So I'm guessing within a couple weeks. I told him I understood it wouldn't be a quick response, or even a quick fix if they agreed. He was very cordial and the conversation went well at the least. Thumbs up for Acer Customer Support guys. Color me impressed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: New Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797002] Re: all my bluetooth headsets skips terribly after todays update
hi, FINALLY, i was able to localize problem :) all my headsets are skipping only when setting window is open! so basically when you click test left or test right - it is in settings window and thus it sounds terribly. But, if you close setting window - every headset works just fine (on online radio for example). my guess would be that while settings window is open - system constantly looking for available devices and thus interfere with present devices. Sorry guys for all these troubles, meanwhile solution was so simple. Thanks -- 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/1797002 Title: all my bluetooth headsets skips terribly after todays update Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Bug description: all my bluetooth headsets skips terribly after today's system update. it is heavy noticeable even on audio setting test form. it work just fine today before i applied updates. even reinstall ubuntu from scratch - didn't help. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 9 18:40:44 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-10-09 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Hewlett-Packard HP ENVY 17 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=fc44a9dc-e173-43fb-ac3a-fdeadb1066e0 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.66 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1968 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 93.52 dmi.chassis.asset.tag: 5CG32907G7 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.66:bd09/22/2015:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1968:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY 17 Notebook PC dmi.product.version: 088510305B0610100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0:Type: Primary Bus: USB BD Address: 68:17:29:62:BE:6A ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:16831 acl:64 sco:0 events:1798 errors:0 TX bytes:688571 acl:2399 sco:0 commands:125 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1797002/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic
It's an empty image - MAAS PXE boots the VM. Could you give it a try with MAAS? I can help you with the setup if needed - just ping me on IRC. -- 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/1797581 Title: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic Status in MAAS: Invalid Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Bug description: Using latest MAAS master, I'm unable to compose a VM over the UI successfully when composed with 2048 MB of RAM. By that I mean that the VM is created, but it fails with a kernel panic. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1797581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
After upgrading from 18.04 to 18.10 the freezes before login. (nvidia- driver-390) -- 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/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1778717] Re: Ubuntu 18.04 guest hangs during diskio stress
** Changed in: linux (Ubuntu Bionic) Status: Triaged => Incomplete ** Changed in: linux (Ubuntu Cosmic) Status: Triaged => 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/1778717 Title: Ubuntu 18.04 guest hangs during diskio stress Status in dellserver: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Cosmic: Incomplete Bug description: Setup - A Dell EMC 14th Gen AMD server, with ESXi 6.7 as host and Ubuntu 18.04 (latest updates) guest. Guest has 3 data disks apart from the boot disk. All these disks are exposed through "ParaVirtual SCSI controller" from the host ESXi 6.7. Run diskio stress on all the 3 data disks for overnight. Guest goes unresponsive (even ping fails) in between. Only way to recover is to reset the guest. Logs do not indicate much on this error. Rarely we get a crash on the Guest-screen. Attaching 2 screenshots of different hits. We have tried mainline kernel v4.18-rc-2 and have hit the issue there as well. Changing the SCSI controller to "LSI Logic SAS adapter" helps and we have not seen any crash/hang here. To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1778717/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790832] Re: crypto/vmx - Backport of Fix sleep-in-atomic bugs patch for 18.04
Xenial SRU request:
https://lists.ubuntu.com/archives/kernel-team/2018-October/096035.html
Bionic SRU request:
https://lists.ubuntu.com/archives/kernel-team/2018-October/096032.html
--
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/1790832
Title:
crypto/vmx - Backport of Fix sleep-in-atomic bugs patch for 18.04
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
Fix Released
Bug description:
== SRU Justification ==
IBM is requesting this patch in all releases order to fix the sleep-in-atomic
bugs in AES-CBC and AES-XTS VMX implementations.
This patch is a clean cherry pick and has already been applied to
Cosmic. It is also needed in Xenial, but there was a minor context
diff, so the Xenial SRU will be sent separatly.
== Fix ==
0522236d4f9c ("crypto: vmx - Fix sleep-in-atomic bugs")
== Regression Potential ==
Low. This patch has also been cc'd to upstream stable, so it has had
additional upstream review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
== Comment: #0 - Paulo Flabiano Smorigo
Please include the following commit in order to fix the sleep-in-atomic bugs
in AES-CBC and AES-XTS VMX implementations [1]:
0522236 crypto: vmx - Fix sleep-in-atomic bugs
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/commit/?id=0522236d4f9c5ab2e79889cb020d1acbe5da416e
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1790832/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797002] Re: all my bluetooth headsets skips terribly after todays update
Hi, it was a great idea to test by running without installation, and i test it on: ubuntu-16.04.1-desktop-amd64 - don't see my Bluetooth headset ubuntu-17.10.1-desktop-amd64 - same problems with skipping as with current version ubuntu-18.04-desktop-amd64 - same problems with skipping as with current version so basically it doesn't work at all and the biggest mystery as for me is why i was able to use my headset on ubuntu at least for half a day when i installed it first time? and why it works perfect right now on windows... so i guess the fact that bluetooth works under windows - excluded hardware problem. -- 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/1797002 Title: all my bluetooth headsets skips terribly after todays update Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Bug description: all my bluetooth headsets skips terribly after today's system update. it is heavy noticeable even on audio setting test form. it work just fine today before i applied updates. even reinstall ubuntu from scratch - didn't help. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 9 18:40:44 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-10-09 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Hewlett-Packard HP ENVY 17 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=fc44a9dc-e173-43fb-ac3a-fdeadb1066e0 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.66 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1968 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 93.52 dmi.chassis.asset.tag: 5CG32907G7 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.66:bd09/22/2015:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1968:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY 17 Notebook PC dmi.product.version: 088510305B0610100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0:Type: Primary Bus: USB BD Address: 68:17:29:62:BE:6A ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:16831 acl:64 sco:0 events:1798 errors:0 TX bytes:688571 acl:2399 sco:0 commands:125 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1797002/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic
I'm unable to recreate with a daily bionic cloud-image on a bionic host with the same versions. % sudo apt install uvtool libvirt % uvt-simplestreams-libvirt -vv sync --source http://cloud-images.ubuntu.com/daily 'supported=True' arch=amd64 release=bionic % uvt-kvm create --memory 2048 --cpu 1 --disk 10 rharper-b1 label=daily release=bionic % virsh dumpxml rharper-b1 | grep Mem 2097152 -- 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/1797581 Title: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic Status in MAAS: Invalid Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Bug description: Using latest MAAS master, I'm unable to compose a VM over the UI successfully when composed with 2048 MB of RAM. By that I mean that the VM is created, but it fails with a kernel panic. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1797581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic
The backing image: /var/lib/libvirt/maas-images/e5d185a9-8ccb-4ca6-959a-bd8eff0ee184 What boot image is that? Can I get a copy of that from maas-images? or how is it created? On the node with the vm that fails, can you: virsh start --console Assuming it's a normal ubuntu image which has normal console= settings, it should dump the boot console to the terminal so we can capture the full boot to panic. -- 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/1797581 Title: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic Status in MAAS: Invalid Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Bug description: Using latest MAAS master, I'm unable to compose a VM over the UI successfully when composed with 2048 MB of RAM. By that I mean that the VM is created, but it fails with a kernel panic. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1797581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775065] Re: No brightness controls and /sys/class/backlight empty after upgrade to Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter acpi_osi= is a workaround)
Hi! I have an Omen by HP 15-ce004la with NVIDIA GTX1060 Q-MAX and the bug is still present. This is my setup: Ubuntu 18.04 with kernel 4.18.13-041813-generic I'am getting acpi errors like this one below in boot time too: [0.104082] ACPI BIOS Error (bug): Failure creating [\_SB.PCI0.XHC.RHUB.GPLD], AE_ALREADY_EXISTS (20180531/dswload2-316) My /sys/class/backlight folder is empty, but xbacklight works. I am using latest Nvidia propietary driver. Regards and hope you can solve this soon. JM -- 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/1775065 Title: No brightness controls and /sys/class/backlight empty after upgrade to Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter acpi_osi= is a workaround) Status in linux package in Ubuntu: Confirmed Bug description: This is a case of "Backlight control does not work, and there are no entries in /sys/class/backlight" for what lspci reports as "NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] (rev a1)" where the kernel parameter acpi_osi= is a workaround. (The workaround is also recorded on Ask Ubuntu at https://askubuntu.com/questions/1030526 /brightness-on-laptop-msi-gt72vr-in-ubuntu-18-04-with-nvidia-gtx-1060 -mobile-does/1043598#1043598.) The problem is new for me after upgrade to Bionic, although the cause might be the corresponding update to the NVIDIA drivers. I will add attachments following the instructions at https://wiki.ubuntu.com/Kernel/Debugging/Backlight, though most of them seem to be uninteresting. If I can provide further information, please let me know. 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 4 14:20:34 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-06-04 (0 days ago) --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bgarvin2442 F pulseaudio /dev/snd/controlC0: bgarvin2442 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=1b60cccb-eea7-4d0b-a32b-97d236a5177f Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b5a7 Chicony Electronics Co., Ltd Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76, Inc. Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=557ebdfc-3380-4721-a494-65c34cb70b2f ro i8042.nomux i8042.reset acpi_osi= ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-06-04 (1 days ago) UserGroups: adm lpadmin sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 09/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.03RSA dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76, Inc. dmi.board.version: oryp2 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.03RSA:bd09/08/2016:svnSystem76,Inc.:pnOryxPro:pvroryp2:rvnSystem76,Inc.:rnOryxPro:rvroryp2:cvnSystem76,Inc.:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.version: oryp2 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775065/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic
Here's the log from the failing VM. Doesn't look too unusual to me... https://paste.ubuntu.com/p/JpmSxmwjfM/ ** Description changed: Using latest MAAS master, I'm unable to compose a VM over the UI - successfully. BY this it means that the VM is created, but it fails with - a kernel panic. - - If I compose a VM over the API, the issue does *not* exist. So this is a - UI issue. + successfully when composed with 2048 MB of RAM. By that I mean that the + VM is created, but it fails with a kernel panic. -- 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/1797581 Title: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic Status in MAAS: Invalid Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Bug description: Using latest MAAS master, I'm unable to compose a VM over the UI successfully when composed with 2048 MB of RAM. By that I mean that the VM is created, but it fails with a kernel panic. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1797581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797538] Re: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]
This occurred right after I upgraded to 18.10 from 18.04.1. Earlier today I got an apt upgrade to kernel 4.18.0-9-generic. The machine is much more stable now. I can't test further at the moment. -- 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/1797538 Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85] Status in linux package in Ubuntu: Incomplete Bug description: Dell XPS 15 9570 ProblemType: KernelOops DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob2250 F pulseaudio Date: Fri Oct 12 08:54:08 2018 Failure: oops InstallationDate: Installed on 2018-10-12 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=b1c8d7c6-d9ec-495c-9770-18e7120e87d5 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85] UpgradeStatus: Upgraded to cosmic on 2018-10-12 (0 days ago) dmi.bios.date: 09/03/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797538/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795453] Re: IO's are issued with incorrect Scatter Gather Buffer
It will be good if you could provide us the exact commit (Patch) which fixes the issue -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1795453 Title: IO's are issued with incorrect Scatter Gather Buffer Status in linux package in Ubuntu: Incomplete Bug description: We have observed that OS is sending the IO's (SCSI Read/Write) with incorrect Scatter Gather Buffer address . i.e OS is sending the IO with 64 bit Scatter Gather Buffer address , such that if we add the length with buffer address then it causes the roll over . Here is the data we captured in our driver (Printed the SGE details which was sent by OS) sgl_ptr->Address = f000 [14547.313240] sgl_ptr->Length = 1000 [14547.313241] sge_count = 18 [14547.313242] cmd->index = 9d9 Note : This issue is observed only when virtualization is enabled Product : Broadcom (LSI) Megaraid H840 controller To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795453/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797379] Re: linux: 4.18.0-10.11 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** 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: derivatives: - kernel-phase:Uploaded - kernel-phase-changed:Thursday, 11. October 2018 15:33 UTC - -- swm properties -- boot-testing-requested: true phase: Uploaded + kernel-phase-changed:Friday, 12. October 2018 20:03 UTC + kernel-phase:Promoted to proposed ** 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: derivatives: -- swm properties -- boot-testing-requested: true - phase: Uploaded - kernel-phase-changed:Friday, 12. October 2018 20:03 UTC - kernel-phase:Promoted to proposed + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797379 Title: linux: 4.18.0-10.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: 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: -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797379/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715271] Re: Middle button of trackpoint doesn't work
This issue was fixed in the upstream 4.13 kernel, so the devel release (and bionic) of ubuntu are no longer affected, closing. ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1715271 Title: Middle button of trackpoint doesn't work Status in HWE Next: Opinion Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Zesty: Fix Released Status in linux source package in Artful: Won't Fix Bug description: Middle button doesn't work on several Thinkpad laptops like E570, E475, E470, E575 and X1Carbon. When middle button fails to work, logs show: psmouse serio2: trackpoint: failed to get extended button data It fails to read out ext button info via PS2 command. Almost all the Thinkpad have 3 buttons, so set it to 3 button when it fails to read button info. And on Lenovo X1, there is a new version of trackpoint, add this ID for this new device. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1715271/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic
And /var/log/libvirt/qemu/.log ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797581 Title: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic Status in MAAS: Invalid Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Bug description: Using latest MAAS master, I'm unable to compose a VM over the UI successfully. BY this it means that the VM is created, but it fails with a kernel panic. If I compose a VM over the API, the issue does *not* exist. So this is a UI issue. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1797581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic
Here's an example of working XML (with 2047 MB RAM) that MAAS generated: https://paste.ubuntu.com/p/mkF6Kp4hx8/ And here's an example of non-working XML (with 2048 MB RAM) that MAAS generated: https://paste.ubuntu.com/p/27HHDrzwm8/ ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797581 Title: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic Status in MAAS: Invalid Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Bug description: Using latest MAAS master, I'm unable to compose a VM over the UI successfully. BY this it means that the VM is created, but it fails with a kernel panic. If I compose a VM over the API, the issue does *not* exist. So this is a UI issue. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1797581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic
Here's the version information. libvirt-bin: Installed: 4.0.0-1ubuntu8.5 Candidate: 4.0.0-1ubuntu8.5 Version table: *** 4.0.0-1ubuntu8.5 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 4.0.0-1ubuntu8.2 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 4.0.0-1ubuntu8 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages qemu-kvm: Installed: 1:2.11+dfsg-1ubuntu7.6 Candidate: 1:2.11+dfsg-1ubuntu7.6 Version table: *** 1:2.11+dfsg-1ubuntu7.6 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:2.11+dfsg-1ubuntu7.3 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1:2.11+dfsg-1ubuntu7 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages qemu-system-x86: Installed: 1:2.11+dfsg-1ubuntu7.6 Candidate: 1:2.11+dfsg-1ubuntu7.6 Version table: *** 1:2.11+dfsg-1ubuntu7.6 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:2.11+dfsg-1ubuntu7.3 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1:2.11+dfsg-1ubuntu7 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages linux-image-4.15.0-34-generic: Installed: 4.15.0-34.37 Candidate: 4.15.0-34.37 Version table: *** 4.15.0-34.37 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 4.15.0-34.37~16.04.1 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages -- 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/1797581 Title: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic Status in MAAS: Invalid Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Bug description: Using latest MAAS master, I'm unable to compose a VM over the UI successfully. BY this it means that the VM is created, but it fails with a kernel panic. If I compose a VM over the API, the issue does *not* exist. So this is a UI issue. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1797581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797581] 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 1797581 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/1797581 Title: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic Status in MAAS: Invalid Status in linux package in Ubuntu: Incomplete Status in qemu package in Ubuntu: New Bug description: Using latest MAAS master, I'm unable to compose a VM over the UI successfully. BY this it means that the VM is created, but it fails with a kernel panic. If I compose a VM over the API, the issue does *not* exist. So this is a UI issue. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1797581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode
I can't see anything obvious in the sosreport, minus the fact I clearly see the package in "iFR" state. I asked a colleague of mine to test in Azure to double-check but my KVM guest tests look good so far : # apt-get install linux-cloud-tools-common -y Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be upgraded: linux-cloud-tools-common 1 upgraded, 0 newly installed, 0 to remove and 72 not upgraded. Need to get 47.0 kB of archives. After this operation, 7,168 B of additional disk space will be used. Get:1 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 linux-cloud-tools-common all 4.15.0-36.39 [47.0 kB] Fetched 47.0 kB in 0s (227 kB/s) (Reading database ... 67213 files and directories currently installed.) Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ... Unpacking linux-cloud-tools-common (4.15.0-36.39) over (4.15.0-34.37) ... Setting up linux-cloud-tools-common (4.15.0-36.39) ... Processing triggers for ureadahead (0.100.0-20) ... Processing triggers for man-db (2.8.3-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/1796376 Title: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode Status in linux package in Ubuntu: Confirmed Bug description: Since the following linux-cloud-tools-common package versions : Xenial : 4.4.0-135.161 Bionic : 4.15.0-34.37 the Systemd service unit file for hv-kvp-daemon has been modified with new dependencies that make the package unable to be upgraded with unattended-upgrades on shutdown mode. Unattended-upgrades hangs with the linux-cloud-tools-common package during "Preparing to unpack". The server restarts after the unattended-upgrades service timeout expires. - Package state after reboot : iFR linux-cloud-tools-common 4.15.0-34.37 all Linux kernel version specific cloud tools for version 4.15.0 - Unattended-upgrades dpkg logs : Log started: 2018-10-05 17:59:04 (Reading database ... 52043 files and directories currently installed.) Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ... Log ended: 2018-10-05 18:00:54 - Impact : The current impact is very important as all security updates are blocked until you manually fix each server with : dpkg --configure -a apt install --only-upgrade linux-cloud-tools-common - Workaround/Fix : As a simple straightforward fix, replacing : Before=shutdown.target cloud-init-local.service walinuxagent.service with : Before=shutdown.target walinuxagent.service makes the package upgradable during shutdown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic
Can you attach the guest xml and host kernel/qemu/libvirt packages? -- 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/1797581 Title: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic Status in MAAS: Invalid Status in linux package in Ubuntu: Incomplete Status in qemu package in Ubuntu: New Bug description: Using latest MAAS master, I'm unable to compose a VM over the UI successfully. BY this it means that the VM is created, but it fails with a kernel panic. If I compose a VM over the API, the issue does *not* exist. So this is a UI issue. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1797581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic
** Summary changed: - Composing a VM in MAAS with exactly 2048 MB RAM causes kernel panic + Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic -- 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/1797581 Title: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic Status in MAAS: Invalid Status in linux package in Ubuntu: Incomplete Status in qemu package in Ubuntu: New Bug description: Using latest MAAS master, I'm unable to compose a VM over the UI successfully. BY this it means that the VM is created, but it fails with a kernel panic. If I compose a VM over the API, the issue does *not* exist. So this is a UI issue. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1797581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797581] Re: [2.5] Composing a VM with 2048 MB RAM causes kernel panic
We can't run apport-collect since the machine doesn't boot, but this was seen with a non-tainted 4.15.0.36-generic kernel in my environment. ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Summary changed: - [2.5] Composing a VM with 2048 MB RAM causes kernel panic + Composing a VM in MAAS with exactly 2048 MB RAM causes kernel panic ** Tags removed: ui -- 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/1797581 Title: Composing a VM in MAAS with exactly 2048 MB RAM causes kernel panic Status in MAAS: Invalid Status in linux package in Ubuntu: New Status in qemu package in Ubuntu: New Bug description: Using latest MAAS master, I'm unable to compose a VM over the UI successfully. BY this it means that the VM is created, but it fails with a kernel panic. If I compose a VM over the API, the issue does *not* exist. So this is a UI issue. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1797581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797581] Re: [2.5] Composing a VM with 2048 MB RAM causes kernel panic
To be clear, the kernel panic is seen when a VM is composed in MAAS with exactly 2048 MB of RAM. Composing with 2047 or 2049 MB RAM results in a working 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/1797581 Title: Composing a VM in MAAS with exactly 2048 MB RAM causes kernel panic Status in MAAS: Invalid Status in linux package in Ubuntu: New Status in qemu package in Ubuntu: New Bug description: Using latest MAAS master, I'm unable to compose a VM over the UI successfully. BY this it means that the VM is created, but it fails with a kernel panic. If I compose a VM over the API, the issue does *not* exist. So this is a UI issue. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1797581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797581] 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 1797581 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/1797581 Title: Composing a VM in MAAS with exactly 2048 MB RAM causes kernel panic Status in MAAS: Invalid Status in linux package in Ubuntu: New Status in qemu package in Ubuntu: New Bug description: Using latest MAAS master, I'm unable to compose a VM over the UI successfully. BY this it means that the VM is created, but it fails with a kernel panic. If I compose a VM over the API, the issue does *not* exist. So this is a UI issue. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1797581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797581] Re: [2.5] Composing a VM with 2048 MB RAM causes kernel panic
Adding the linux package; we should narrow down the issue to see if it's in kernel space or user space. ** Summary changed: - [2.5, UI] Composing a VM over the UI is broken - VM has kernel panic + [2.5] Composing a VM with 2048 MB RAM causes kernel panic ** Changed in: maas Status: Incomplete => Invalid ** Also affects: qemu (Ubuntu) Importance: Undecided Status: New ** 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/1797581 Title: Composing a VM in MAAS with exactly 2048 MB RAM causes kernel panic Status in MAAS: Invalid Status in linux package in Ubuntu: New Status in qemu package in Ubuntu: New Bug description: Using latest MAAS master, I'm unable to compose a VM over the UI successfully. BY this it means that the VM is created, but it fails with a kernel panic. If I compose a VM over the API, the issue does *not* exist. So this is a UI issue. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1797581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790832] Re: crypto/vmx - Backport of Fix sleep-in-atomic bugs patch for 18.04
** Description changed:
- == Comment: #0 - Paulo Flabiano Smorigo
+
+ == SRU Justification ==
+ IBM is requesting this patch in all releases order to fix the sleep-in-atomic
+ bugs in AES-CBC and AES-XTS VMX implementations.
+
+ This patch is a clean cherry pick and has already been applied to
+ Cosmic. It is also needed in Xenial, but there was a minor context
+ diff, so the Xenial SRU will be sent separatly.
+
+ == Fix ==
+ 0522236d4f9c ("crypto: vmx - Fix sleep-in-atomic bugs")
+
+ == Regression Potential ==
+ Low. This patch has also been cc'd to upstream stable, so it has had
+ additional upstream review.
+
+ == Test Case ==
+ A test kernel was built with this patch and tested by the original bug
reporter.
+ The bug reporter states the test kernel resolved the bug.
+
+
+
+
+ == Comment: #0 - Paulo Flabiano Smorigo
Please include the following commit in order to fix the sleep-in-atomic bugs
in AES-CBC and AES-XTS VMX implementations [1]:
0522236 crypto: vmx - Fix sleep-in-atomic bugs
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/commit/?id=0522236d4f9c5ab2e79889cb020d1acbe5da416e
--
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/1790832
Title:
crypto/vmx - Backport of Fix sleep-in-atomic bugs patch for 18.04
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
Fix Released
Bug description:
== SRU Justification ==
IBM is requesting this patch in all releases order to fix the sleep-in-atomic
bugs in AES-CBC and AES-XTS VMX implementations.
This patch is a clean cherry pick and has already been applied to
Cosmic. It is also needed in Xenial, but there was a minor context
diff, so the Xenial SRU will be sent separatly.
== Fix ==
0522236d4f9c ("crypto: vmx - Fix sleep-in-atomic bugs")
== Regression Potential ==
Low. This patch has also been cc'd to upstream stable, so it has had
additional upstream review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
== Comment: #0 - Paulo Flabiano Smorigo
Please include the following commit in order to fix the sleep-in-atomic bugs
in AES-CBC and AES-XTS VMX implementations [1]:
0522236 crypto: vmx - Fix sleep-in-atomic bugs
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/commit/?id=0522236d4f9c5ab2e79889cb020d1acbe5da416e
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1790832/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790832] Re: crypto/vmx - Backport of Fix sleep-in-atomic bugs patch for 18.04
** Changed in: linux (Ubuntu Cosmic) 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/1790832 Title: crypto/vmx - Backport of Fix sleep-in-atomic bugs patch for 18.04 Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: Fix Released Bug description: == Comment: #0 - Paulo Flabiano Smorigo Please include the following commit in order to fix the sleep-in-atomic bugs in AES-CBC and AES-XTS VMX implementations [1]: 0522236 crypto: vmx - Fix sleep-in-atomic bugs [1] https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/commit/?id=0522236d4f9c5ab2e79889cb020d1acbe5da416e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1790832/+subscriptions -- Mailing list: https://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 1797349] Re: GPU hang, full freeze / lockup
This only happened once so far. One too many. -- 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/1797349 Title: GPU hang, full freeze / lockup Status in linux package in Ubuntu: Incomplete Bug description: Oct 11 10:48:38 L-UXX0MPSM3 kernel: [10459.830646] [drm] GPU HANG: ecode 9:0:0x85db, in Xorg [1101], reason: Hang on rcs0, action: reset Oct 11 10:48:38 L-UXX0MPSM3 kernel: [10459.830652] i915 :00:02.0: Resetting rcs0 after gpu hang Oct 11 10:48:39 L-UXX0MPSM3 kernel: [10460.844423] asynchronous wait on fence i915:kwin_x11[2217]/1:2888a timed out Oct 11 10:48:39 L-UXX0MPSM3 ntpd[2505]: Soliciting pool server 91.121.7.182 Oct 11 10:48:40 L-UXX0MPSM3 ntpd[2505]: Soliciting pool server 129.250.35.251 Oct 11 10:48:46 L-UXX0MPSM3 kernel: [10467.788461] i915 :00:02.0: Resetting rcs0 after gpu hang Oct 11 10:48:54 L-UXX0MPSM3 kernel: [10475.756465] i915 :00:02.0: Resetting rcs0 after gpu hang Oct 11 10:49:02 L-UXX0MPSM3 kernel: [10483.756405] i915 :00:02.0: Resetting rcs0 after gpu hang Oct 11 10:49:02 L-UXX0MPSM3 systemd[1]: Started Getty on tty6. Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Received SIGINT. Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopped target Timers. Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopped target Sound Card. Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopped Daily apt upgrade and clean activities. Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopping Disk Manager... Oct 11 10:49:04 L-UXX0MPSM3 obexd[2425]: Terminating Oct 11 10:49:04 L-UXX0MPSM3 sddm[1036]: Authentication error: "Process crashed" Oct 11 10:49:04 L-UXX0MPSM3 sddm[1036]: Auth: sddm-helper crashed (exit code 15) Oct 11 10:49:04 L-UXX0MPSM3 sddm[1036]: Authentication error: "Process crashed" Oct 11 10:49:04 L-UXX0MPSM3 sddm[1036]: Auth: sddm-helper exited with 15 Oct 11 10:49:04 L-UXX0MPSM3 sddm[1036]: Socket server stopping... Oct 11 10:49:04 L-UXX0MPSM3 sddm[1036]: Socket server stopped. Oct 11 10:49:04 L-UXX0MPSM3 sddm[1036]: Display server stopping... Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopping Session 2 of user manu. Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopped Daily Cleanup of Temporary Directories. Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Closed Load/Save RF Kill Switch Status /dev/rfkill Watch. Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopping Daemon for power management... Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopped Daily apt download activities. Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopping Daemon for generating UUIDs... Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopping User Manager for UID 1002... Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopped Stop ureadahead data collection 45s after completed startup. Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopping Authenticate and Authorize Users to Run Privileged Tasks... Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopping ACPI event daemon... Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopped target Graphical Interface. Oct 11 10:49:04 L-UXX0MPSM3 rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="870" x-info="http://www.rsyslog.com;] exiting on signal 15. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Thu Oct 11 10:52:40 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: kubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake Integrated Graphics [17aa:5062] InstallationDate: Installed on 2018-04-20 (173 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 20K5S0T200 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/02/2017 dmi.bios.vendor: LENOVO dmi.bios.version: R0IET36W (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20K5S0T200 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0IET36W(1.14):bd05/02/2017:svnLENOVO:pn20K5S0T200:pvrThinkPadX270W10DG:rvnLENOVO:rn20K5S0T200:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X270 W10DG
[Kernel-packages] [Bug 1796385] Re: watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112]
@Bounty Could you temporarily change the video card to rule out problems with it? Your current video card is: [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 270/370 OEM] Best regards, -- Cristian Aravena Romero (caravena) ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796385 Title: watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112] Status in Linux: Unknown Status in linux package in Ubuntu: Incomplete Bug description: I can use the system for a while, then at random, the screen blinks and freezes. Must reboot. Seems to happen both with Wayland and Xorg. ProblemType: KernelOops DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: greg 2039 F pulseaudio /dev/snd/controlC1: greg 2039 F pulseaudio Date: Tue Oct 2 15:56:23 2018 Failure: oops InstallationDate: Installed on 2018-09-28 (7 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. Default string ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=ce06b10d-2a7f-49db-a15b-85554d9a7e4d ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: X99-UD4-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.:bvrF23:bd06/07/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99-UD4-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1796385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797379] Re: linux: 4.18.0-10.11 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed 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/1797379 Title: linux: 4.18.0-10.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: This bug is for tracking the 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: kernel-phase:Uploaded kernel-phase-changed:Thursday, 11. October 2018 15:33 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797379/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796385] Re: watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112]
https://bugzilla.kernel.org/show_bug.cgi?id=201379#c6 "Unfortunately we do not have information to determine 'Product' and 'Component'. The only information we have is that the hanging process is gnome-shell (or at least that this was the case in at least one instance), that the screen blinks and freezes when the problem is observed, and that the hanging CPU served most of the graphics card interrupts. If it is persistent, it _might_ suggest that graphics (presumably the Radeon graphics driver and/or the graphics hardware) is involved. This would be even more likely if the observed PCIe errors point to the graphics card (not sure if the information provided shows the PCIe bus tree; if so I have not found it)." -- Cristian Aravena Romero (caravena) -- 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/1796385 Title: watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112] Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: I can use the system for a while, then at random, the screen blinks and freezes. Must reboot. Seems to happen both with Wayland and Xorg. ProblemType: KernelOops DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: greg 2039 F pulseaudio /dev/snd/controlC1: greg 2039 F pulseaudio Date: Tue Oct 2 15:56:23 2018 Failure: oops InstallationDate: Installed on 2018-09-28 (7 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. Default string ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=ce06b10d-2a7f-49db-a15b-85554d9a7e4d ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: X99-UD4-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.:bvrF23:bd06/07/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99-UD4-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1796385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793338] Re: Fix unusable NVIDIA GPU after S3
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1793338 Title: Fix unusable NVIDIA GPU after S3 Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-oem source package in Cosmic: Fix Released Bug description: [Impact] NVIDIA GPU becomes unusable after S3. [Test] The NVIDIA GPU works well after applying this patch. [Fix] Rewrite 0 to Intel PCI bridge 'Prefetchable Base Upper 32 Bits'. This should be done by BIOS S3 code [1], but now the issue reappears, let's do the same via Linux PCI subsystem. [Regression Potential] Low. After applying this patch I haven't noticed any change on already working PCI devices. Also this patch is acked by PCI and ACPI maintainers, so we can be more confident. [1] https://bugzilla.kernel.org/show_bug.cgi?id=116851#c23 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1793338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
After upgrading from 18.04 to 18.10 the freezes before login. (nvidia- driver-390) -- 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/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788035] Re: nvme: avoid cqe corruption
So far the best I could reach is get the kernel call trace but not crashing the node yet. Oct 12 15:33:41 ip-10-16-21-10 kernel: [10919.306845] INFO: task java:1932 blocked for more than 120 seconds. Oct 12 15:33:41 ip-10-16-21-10 kernel: [10919.308573] Not tainted 4.4.0-1069-aws #79-Ubuntu Oct 12 15:33:41 ip-10-16-21-10 kernel: [10919.309944] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Oct 12 15:33:41 ip-10-16-21-10 kernel: [10919.312015] javaD 88032dc57db0 0 1932 1 0x Oct 12 15:33:41 ip-10-16-21-10 kernel: [10919.312019] 88032dc57db0 0246 88041077e900 88032dcae900 Oct 12 15:33:41 ip-10-16-21-10 kernel: [10919.312022] 88032dc58000 00074da7 88040dbdf888 88040dbdf824 Oct 12 15:33:41 ip-10-16-21-10 kernel: [10919.312024] 88032dc57df8 88032dc57dc8 81823825 88040dbdf800 Oct 12 15:33:41 ip-10-16-21-10 kernel: [10919.312027] Call Trace: Oct 12 15:33:41 ip-10-16-21-10 kernel: [10919.312035] [] schedule+0x35/0x80 Oct 12 15:33:41 ip-10-16-21-10 kernel: [10919.312042] [] jbd2_log_wait_commit+0xa9/0x130 Oct 12 15:33:41 ip-10-16-21-10 kernel: [10919.312045] [] ? wake_atomic_t_function+0x60/0x60 Oct 12 15:33:41 ip-10-16-21-10 kernel: [10919.312048] [] __jbd2_journal_force_commit+0x61/0xb0 Oct 12 15:33:41 ip-10-16-21-10 kernel: [10919.312049] [] jbd2_journal_force_commit+0x21/0x30 Oct 12 15:33:41 ip-10-16-21-10 kernel: [10919.312053] [] ext4_force_commit+0x29/0x30 Oct 12 15:33:41 ip-10-16-21-10 kernel: [10919.312057] [] ext4_sync_file+0x1a1/0x350 Oct 12 15:33:41 ip-10-16-21-10 kernel: [10919.312065] [] vfs_fsync_range+0x4e/0xb0 Oct 12 15:33:41 ip-10-16-21-10 kernel: [10919.312072] [] do_fsync+0x3d/0x70 Oct 12 15:33:41 ip-10-16-21-10 kernel: [10919.312074] [] SyS_fsync+0x10/0x20 Oct 12 15:33:41 ip-10-16-21-10 kernel: [10919.312077] [] entry_SYSCALL_64_fastpath+0x22/0xc1 Oct 12 15:35:01 ip-10-16-21-10 CRON[31352]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) using this simple script writing and reading same file in parallel from different process and let it run for while in my case I got the first call trace after 3h. while true do dd iflag=nocache if=/dev/zero of=/tmp/myfilesource$1 bs=1k count=$2 dd iflag=nocache if=/tmp/myfilesource$1 of=/tmp/myfileout$1 bs=1k count=$2 done root@ip-10-16-21-10:~# jobs [1] Running nohup ./mytest1.sh 1 1024000& [2]- Running nohup ./mytest1.sh 1 1024 & [3]+ Running nohup ./mytest1.sh 1 102400 & -- 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/1788035 Title: nvme: avoid cqe corruption Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Released Bug description: To address customer-reported NVMe issue with instance types (notably c5 and m5) that expose EBS volumes as NVMe devices, this commit from mainline v4.6 should be backported to Xenial: d783e0bd02e700e7a893ef4fa71c69438ac1c276 nvme: avoid cqe corruption when update at the same time as read dmesg sample: [Wed Aug 15 01:11:21 2018] nvme :00:1f.0: I/O 8 QID 1 timeout, aborting [Wed Aug 15 01:11:21 2018] nvme :00:1f.0: I/O 9 QID 1 timeout, aborting [Wed Aug 15 01:11:21 2018] nvme :00:1f.0: I/O 21 QID 2 timeout, aborting [Wed Aug 15 01:11:32 2018] nvme :00:1f.0: I/O 10 QID 1 timeout, aborting [Wed Aug 15 01:11:51 2018] nvme :00:1f.0: I/O 8 QID 1 timeout, reset controller [Wed Aug 15 01:11:51 2018] nvme nvme1: Abort status: 0x2 [Wed Aug 15 01:11:51 2018] nvme nvme1: Abort status: 0x2 [Wed Aug 15 01:11:51 2018] nvme nvme1: Abort status: 0x2 [Wed Aug 15 01:11:51 2018] nvme :00:1f.0: Cancelling I/O 21 QID 2 [Wed Aug 15 01:11:51 2018] nvme :00:1f.0: completing aborted command with status: 0007 [Wed Aug 15 01:11:51 2018] blk_update_request: I/O error, dev nvme1n1, sector 83887751 [Wed Aug 15 01:11:51 2018] blk_update_request: I/O error, dev nvme1n1, sector 83887751 [Wed Aug 15 01:11:51 2018] nvme :00:1f.0: Cancelling I/O 22 QID 2 [Wed Aug 15 01:11:51 2018] blk_update_request: I/O error, dev nvme1n1, sector 83887767 [Wed Aug 15 01:11:51 2018] blk_update_request: I/O error, dev nvme1n1, sector 83887767 [Wed Aug 15 01:11:51 2018] nvme :00:1f.0: Cancelling I/O 23 QID 2 [Wed Aug 15 01:11:51 2018] blk_update_request: I/O error, dev nvme1n1, sector 83887769 [Wed Aug 15 01:11:51 2018] blk_update_request: I/O error, dev nvme1n1, sector 83887769 [Wed Aug 15 01:11:51 2018] nvme :00:1f.0: Cancelling I/O 8 QID 1 [Wed Aug 15 01:11:51 2018] nvme :00:1f.0: Cancelling I/O 9 QID 1 [Wed Aug 15 01:11:51 2018] nvme :00:1f.0: completing aborted command with status: 0007 [Wed Aug 15 01:11:51 2018] blk_update_request: I/O error, dev nvme1n1, sector 41943136
[Kernel-packages] [Bug 1788035] Re: nvme: avoid cqe corruption
I have the same.
I have the less loaded instances in my real environment crashing and
the environment where I am trying to reproduce the issue stressing it
not crashing.
I am finding a way to reproduce it.
How did you reproduce it?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1788035
Title:
nvme: avoid cqe corruption
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Released
Bug description:
To address customer-reported NVMe issue with instance types (notably
c5 and m5) that expose EBS volumes as NVMe devices, this commit from
mainline v4.6 should be backported to Xenial:
d783e0bd02e700e7a893ef4fa71c69438ac1c276 nvme: avoid cqe corruption
when update at the same time as read
dmesg sample:
[Wed Aug 15 01:11:21 2018] nvme :00:1f.0: I/O 8 QID 1 timeout, aborting
[Wed Aug 15 01:11:21 2018] nvme :00:1f.0: I/O 9 QID 1 timeout, aborting
[Wed Aug 15 01:11:21 2018] nvme :00:1f.0: I/O 21 QID 2 timeout, aborting
[Wed Aug 15 01:11:32 2018] nvme :00:1f.0: I/O 10 QID 1 timeout, aborting
[Wed Aug 15 01:11:51 2018] nvme :00:1f.0: I/O 8 QID 1 timeout, reset
controller
[Wed Aug 15 01:11:51 2018] nvme nvme1: Abort status: 0x2
[Wed Aug 15 01:11:51 2018] nvme nvme1: Abort status: 0x2
[Wed Aug 15 01:11:51 2018] nvme nvme1: Abort status: 0x2
[Wed Aug 15 01:11:51 2018] nvme :00:1f.0: Cancelling I/O 21 QID 2
[Wed Aug 15 01:11:51 2018] nvme :00:1f.0: completing aborted command with
status: 0007
[Wed Aug 15 01:11:51 2018] blk_update_request: I/O error, dev nvme1n1, sector
83887751
[Wed Aug 15 01:11:51 2018] blk_update_request: I/O error, dev nvme1n1, sector
83887751
[Wed Aug 15 01:11:51 2018] nvme :00:1f.0: Cancelling I/O 22 QID 2
[Wed Aug 15 01:11:51 2018] blk_update_request: I/O error, dev nvme1n1, sector
83887767
[Wed Aug 15 01:11:51 2018] blk_update_request: I/O error, dev nvme1n1, sector
83887767
[Wed Aug 15 01:11:51 2018] nvme :00:1f.0: Cancelling I/O 23 QID 2
[Wed Aug 15 01:11:51 2018] blk_update_request: I/O error, dev nvme1n1, sector
83887769
[Wed Aug 15 01:11:51 2018] blk_update_request: I/O error, dev nvme1n1, sector
83887769
[Wed Aug 15 01:11:51 2018] nvme :00:1f.0: Cancelling I/O 8 QID 1
[Wed Aug 15 01:11:51 2018] nvme :00:1f.0: Cancelling I/O 9 QID 1
[Wed Aug 15 01:11:51 2018] nvme :00:1f.0: completing aborted command with
status: 0007
[Wed Aug 15 01:11:51 2018] blk_update_request: I/O error, dev nvme1n1, sector
41943136
[Wed Aug 15 01:11:51 2018] nvme :00:1f.0: Cancelling I/O 10 QID 1
[Wed Aug 15 01:11:51 2018] nvme :00:1f.0: completing aborted command with
status: 0007
[Wed Aug 15 01:11:51 2018] blk_update_request: I/O error, dev nvme1n1, sector
6976
[Wed Aug 15 01:11:51 2018] nvme :00:1f.0: Cancelling I/O 22 QID 1
[Wed Aug 15 01:11:51 2018] nvme :00:1f.0: Cancelling I/O 23 QID 1
[Wed Aug 15 01:11:51 2018] nvme :00:1f.0: Cancelling I/O 24 QID 1
[Wed Aug 15 01:11:51 2018] nvme :00:1f.0: Cancelling I/O 25 QID 1
[Wed Aug 15 01:11:51 2018] nvme :00:1f.0: Cancelling I/O 2 QID 0
[Wed Aug 15 01:11:51 2018] nvme nvme1: Abort status: 0x7
[Wed Aug 15 01:11:51 2018] nvme :00:1f.0: completing aborted command with
status: fffc
[Wed Aug 15 01:11:51 2018] blk_update_request: I/O error, dev nvme1n1, sector
96
[Wed Aug 15 01:11:51 2018] XFS (nvme1n1): metadata I/O error: block 0x5000687
("xlog_iodone") error 5 numblks 64
[Wed Aug 15 01:11:51 2018] XFS (nvme1n1): xfs_do_force_shutdown(0x2) called
from line 1197 of file /build/linux-c2Z51P/linux-4.4.0/fs/xfs/xfs_log.c. Return
address = 0xc075d428
[Wed Aug 15 01:11:51 2018] XFS (nvme1n1): xfs_log_force: error -5 returned.
[Wed Aug 15 01:11:51 2018] XFS (nvme1n1): Log I/O Error Detected. Shutting
down filesystem
[Wed Aug 15 01:11:51 2018] XFS (nvme1n1): Please umount the filesystem and
rectify the problem(s)
[Wed Aug 15 01:11:51 2018] Buffer I/O error on dev nvme1n1, logical block
872, lost async page write
[Wed Aug 15 01:11:51 2018] XFS (nvme1n1): xfs_imap_to_bp:
xfs_trans_read_buf() returned error -5.
[Wed Aug 15 01:11:51 2018] XFS (nvme1n1): xfs_iunlink_remove: xfs_imap_to_bp
returned error -5.
[Wed Aug 15 01:11:51 2018] Buffer I/O error on dev nvme1n1, logical block
873, lost async page write
[Wed Aug 15 01:11:51 2018] Buffer I/O error on dev nvme1n1, logical block
874, lost async page write
[Wed Aug 15 01:11:51 2018] Buffer I/O error on dev nvme1n1, logical block
875, lost async page write
[Wed Aug 15 01:11:51 2018] Buffer I/O error on dev nvme1n1, logical block
876, lost async page write
[Wed Aug 15 01:11:51 2018] Buffer I/O error on dev nvme1n1, logical block
877, lost async page write
[Wed Aug 15 01:11:51 2018] Buffer I/O error on dev nvme1n1, logical block
878, lost async page write
[Kernel-packages] [Bug 1797587] [NEW] Intel NVMe drives timeout when nvme format is attempted
Private bug reported: Every time you run an nvme format on a Intel NVMe drive (whether specifying the secure/crypto erase options or not), the format apparently works (drive is wiped clean) but the drive's admin queue (queue 0) times out, making the nvme device driver flag an error and reset the controller. Here's an example: nvme-cli-1.5 # ./nvme format -l 0 /dev/nvme1 NVME Admin command error:ABORT_REQ(7) nvme-cli-1.5 # dmesg|tail -1 [79725.404910] nvme nvme1: I/O 151 QID 0 timeout, reset controller Patch required: https://github.com/torvalds/linux/commit/62843c2e4226057c83f520c74fe9c81a1891c331 Request you to include the patch for LTS kernel 4.15 of Ubuntu 18.04 ** Affects: dell-poweredge Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Information type changed from Public to Private ** Also affects: dell-poweredge 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/1797587 Title: Intel NVMe drives timeout when nvme format is attempted Status in The Dell-poweredge project: New Status in linux package in Ubuntu: New Bug description: Every time you run an nvme format on a Intel NVMe drive (whether specifying the secure/crypto erase options or not), the format apparently works (drive is wiped clean) but the drive's admin queue (queue 0) times out, making the nvme device driver flag an error and reset the controller. Here's an example: nvme-cli-1.5 # ./nvme format -l 0 /dev/nvme1 NVME Admin command error:ABORT_REQ(7) nvme-cli-1.5 # dmesg|tail -1 [79725.404910] nvme nvme1: I/O 151 QID 0 timeout, reset controller Patch required: https://github.com/torvalds/linux/commit/62843c2e4226057c83f520c74fe9c81a1891c331 Request you to include the patch for LTS kernel 4.15 of Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/dell-poweredge/+bug/1797587/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795453] Re: IO's are issued with incorrect Scatter Gather Buffer
Also another version (other than default version of Ubuntu 18.04.01) of 4.15 kernel fixes the issue -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1795453 Title: IO's are issued with incorrect Scatter Gather Buffer Status in linux package in Ubuntu: Incomplete Bug description: We have observed that OS is sending the IO's (SCSI Read/Write) with incorrect Scatter Gather Buffer address . i.e OS is sending the IO with 64 bit Scatter Gather Buffer address , such that if we add the length with buffer address then it causes the roll over . Here is the data we captured in our driver (Printed the SGE details which was sent by OS) sgl_ptr->Address = f000 [14547.313240] sgl_ptr->Length = 1000 [14547.313241] sge_count = 18 [14547.313242] cmd->index = 9d9 Note : This issue is observed only when virtualization is enabled Product : Broadcom (LSI) Megaraid H840 controller To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795453/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode
Do you have an non-upgraded machine where you can run the sosreport prior the upgrade ? then run the upgrade (and if the problem occurs) run a second sosreport post upgrade ? - Eric -- 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/1796376 Title: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode Status in linux package in Ubuntu: Confirmed Bug description: Since the following linux-cloud-tools-common package versions : Xenial : 4.4.0-135.161 Bionic : 4.15.0-34.37 the Systemd service unit file for hv-kvp-daemon has been modified with new dependencies that make the package unable to be upgraded with unattended-upgrades on shutdown mode. Unattended-upgrades hangs with the linux-cloud-tools-common package during "Preparing to unpack". The server restarts after the unattended-upgrades service timeout expires. - Package state after reboot : iFR linux-cloud-tools-common 4.15.0-34.37 all Linux kernel version specific cloud tools for version 4.15.0 - Unattended-upgrades dpkg logs : Log started: 2018-10-05 17:59:04 (Reading database ... 52043 files and directories currently installed.) Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ... Log ended: 2018-10-05 18:00:54 - Impact : The current impact is very important as all security updates are blocked until you manually fix each server with : dpkg --configure -a apt install --only-upgrade linux-cloud-tools-common - Workaround/Fix : As a simple straightforward fix, replacing : Before=shutdown.target cloud-init-local.service walinuxagent.service with : Before=shutdown.target walinuxagent.service makes the package upgradable during shutdown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796469] Re: aws s3 cp --recursive hangs on the last file on a large file transfer to instance
Not sure if it's related but I'll leave this here. We have a bunch of EC2 instances running Ubuntu 18.04 LTS and GitLab Runner, with the latter configured to execute build jobs inside Docker containers. Our EC2 instances are of the t2.medium, t2.xlarge and t3.medium sizes and run in the eu-west-1 region (in different AZs). After upgrading from kernel 4.15.0-1021-aws to 4.15.0-1023-aws we've seen a lot of build failures across all of our GitLab Runner instances on Ubuntu 18.04 LTS. The problems happen intermittently. Specifically the build jobs fail during the startup phase where GitLab Runner clones the git repository. The git clone operation fails with: ``` Cloning repository... Cloning into '/builds/my-group/my-project'... error: RPC failed; curl 18 transfer closed with outstanding read data remaining fatal: The remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed ``` According to the documentation at https://curl.haxx.se/libcurl/c /libcurl-errors.html this means: > CURLE_PARTIAL_FILE (18) > > A file transfer was shorter or larger than expected. This happens when the > server first reports an expected transfer size, and then delivers data that > doesn't match the previously given size. When this problem happened it seems that the bandwidth used by the `git clone` operation eventually dropped to a few or zero kByte/s (the reporting wasn't granular enough to determine which). I assume that the GitLab server later closed/timed out the connection before the git client had downloaded all of the data it expected, leaving us with a `CURLE_PARTIAL_FILE` error. We've also seen larger (10s-100s of MBs) file downloads hang indefinitely (e.g. apt install). We've rolled back changes made during the last few weeks one by one and eventually found that downgrading to 4.15.0-1021-aws solved the issue on all of our GitLab Runner instances (ranging from 11.2.0, 11.2.1 and 11.3.1). I couldn't spot anything obvious that seemed to be related to the issue in the changelog here: https://changelogs.ubuntu.com/changelogs/pool/main/l/linux-aws/linux-aws_4.15.0-1023.23/changelog FWIW, this is what `docker version` reports: ``` Client: Version: 18.06.1-ce API version: 1.38 Go version:go1.10.3 Git commit:e68fc7a Built: Tue Aug 21 17:24:56 2018 OS/Arch: linux/amd64 Experimental: false Server: Engine: Version: 18.06.1-ce API version: 1.38 (minimum version 1.12) Go version: go1.10.3 Git commit: e68fc7a Built:Tue Aug 21 17:23:21 2018 OS/Arch: linux/amd64 Experimental: false ``` -- 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/1796469 Title: aws s3 cp --recursive hangs on the last file on a large file transfer to instance Status in linux-aws package in Ubuntu: New Bug description: aws s3 cp --recursive hangs on the last file on a large transfer to an instance I have confirmed that this works on version Linux/4.15.0-1021-aws aws cli version aws-cli/1.16.23 Python/2.7.15rc1 Linux/4.15.0-1023-aws botocore/1.12.13 Ubuntu version Description: Ubuntu 18.04.1 LTS Release: 18.04 eu-west-1 - ubuntu/images/hvm-ssd/ubuntu-bionic-18.04-amd64-server-20180912 - ami-00035f41c82244dab Package version linux-aws: Installed: 4.15.0.1023.23 Candidate: 4.15.0.1023.23 Version table: *** 4.15.0.1023.23 500 500 http://eu-west-1.ec2.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 4.15.0.1007.7 500 500 http://eu-west-1.ec2.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1796469/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789746] Re: getxattr: always handle namespaced attributes
Hi @kleber-souza,
The kernel fixes the issue. I changed the tag to
verification-done. Thanks!
Christian
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1789746
Title:
getxattr: always handle namespaced attributes
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Released
Bug description:
== SRU Justification ==
When running in a container with a user namespace, if you call getxattr
with name = "system.posix_acl_access" and size % 8 != 4, then getxattr
silently skips the user namespace fixup that it normally does resulting in
un-fixed-up data being returned.
This is caused by posix_acl_fix_xattr_to_user() being passed the total
buffer size and not the actual size of the xattr as returned by
vfs_getxattr().
I have pushed a commit upstream that fixes this bug:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=82c9a927bc5df6e06b72d206d24a9d10cced4eb5
This commit passes the actual length of the xattr as returned by
vfs_getxattr() down.
A reproducer for the issue is:
touch acl_posix
setfacl -m user:0:rwx acl_posix
and the compile:
#define _GNU_SOURCE
#include
#include
#include
#include
#include
#include
#include
/* Run in user namespace with nsuid 0 mapped to uid != 0 on the host. */
int main(int argc, void **argv)
{
ssize_t ret1, ret2;
char buf1[128], buf2[132];
int fret = EXIT_SUCCESS;
char *file;
if (argc < 2) {
fprintf(stderr,
"Please specify a file with "
"\"system.posix_acl_access\" permissions set\n");
_exit(EXIT_FAILURE);
}
file = argv[1];
ret1 = getxattr(file, "system.posix_acl_access",
buf1, sizeof(buf1));
if (ret1 < 0) {
fprintf(stderr, "%s - Failed to retrieve "
"\"system.posix_acl_access\" "
"from \"%s\"\n", strerror(errno), file);
_exit(EXIT_FAILURE);
}
ret2 = getxattr(file, "system.posix_acl_access",
buf2, sizeof(buf2));
if (ret2 < 0) {
fprintf(stderr, "%s - Failed to retrieve "
"\"system.posix_acl_access\" "
"from \"%s\"\n", strerror(errno), file);
_exit(EXIT_FAILURE);
}
if (ret1 != ret2) {
fprintf(stderr, "The value of \"system.posix_acl_"
"access\" for file \"%s\" changed "
"between two successive calls\n", file);
_exit(EXIT_FAILURE);
}
for (ssize_t i = 0; i < ret2; i++) {
if (buf1[i] == buf2[i])
continue;
fprintf(stderr,
"Unexpected different in byte %zd: "
"%02x != %02x\n", i, buf1[i], buf2[i]);
fret = EXIT_FAILURE;
}
if (fret == EXIT_SUCCESS)
fprintf(stderr, "Test passed\n");
else
fprintf(stderr, "Test failed\n");
_exit(fret);
}
and run:
./tester acl_posix
On a non-fixed up kernel this should return something like:
root@c1:/# ./t
Unexpected different in byte 16: ffa0 != 00
Unexpected different in byte 17: ff86 != 00
Unexpected different in byte 18: 01 != 00
and on a fixed kernel:
root@c1:~# ./t
Test passed
== Fix ==
82c9a927bc5d ("getxattr: use correct xattr length")
== Regression Potential ==
Low. One liner that passes the actual length of the xattr as returned by
vfs_getxattr() down.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789746/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795453] Re: IO's are issued with incorrect Scatter Gather Buffer
Could you also test the latest upstream 4.15 stable kernel? It is available from: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15.18/ We should be able to perform a reverse bisect to identify the commits in 4.18 that resolve this bug. ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-da-key ** Tags added: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1795453 Title: IO's are issued with incorrect Scatter Gather Buffer Status in linux package in Ubuntu: Incomplete Bug description: We have observed that OS is sending the IO's (SCSI Read/Write) with incorrect Scatter Gather Buffer address . i.e OS is sending the IO with 64 bit Scatter Gather Buffer address , such that if we add the length with buffer address then it causes the roll over . Here is the data we captured in our driver (Printed the SGE details which was sent by OS) sgl_ptr->Address = f000 [14547.313240] sgl_ptr->Length = 1000 [14547.313241] sge_count = 18 [14547.313242] cmd->index = 9d9 Note : This issue is observed only when virtualization is enabled Product : Broadcom (LSI) Megaraid H840 controller To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795453/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797349] Re: GPU hang, full freeze / lockup
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 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.19-rc7 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797349 Title: GPU hang, full freeze / lockup Status in linux package in Ubuntu: Incomplete Bug description: Oct 11 10:48:38 L-UXX0MPSM3 kernel: [10459.830646] [drm] GPU HANG: ecode 9:0:0x85db, in Xorg [1101], reason: Hang on rcs0, action: reset Oct 11 10:48:38 L-UXX0MPSM3 kernel: [10459.830652] i915 :00:02.0: Resetting rcs0 after gpu hang Oct 11 10:48:39 L-UXX0MPSM3 kernel: [10460.844423] asynchronous wait on fence i915:kwin_x11[2217]/1:2888a timed out Oct 11 10:48:39 L-UXX0MPSM3 ntpd[2505]: Soliciting pool server 91.121.7.182 Oct 11 10:48:40 L-UXX0MPSM3 ntpd[2505]: Soliciting pool server 129.250.35.251 Oct 11 10:48:46 L-UXX0MPSM3 kernel: [10467.788461] i915 :00:02.0: Resetting rcs0 after gpu hang Oct 11 10:48:54 L-UXX0MPSM3 kernel: [10475.756465] i915 :00:02.0: Resetting rcs0 after gpu hang Oct 11 10:49:02 L-UXX0MPSM3 kernel: [10483.756405] i915 :00:02.0: Resetting rcs0 after gpu hang Oct 11 10:49:02 L-UXX0MPSM3 systemd[1]: Started Getty on tty6. Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Received SIGINT. Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopped target Timers. Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopped target Sound Card. Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopped Daily apt upgrade and clean activities. Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopping Disk Manager... Oct 11 10:49:04 L-UXX0MPSM3 obexd[2425]: Terminating Oct 11 10:49:04 L-UXX0MPSM3 sddm[1036]: Authentication error: "Process crashed" Oct 11 10:49:04 L-UXX0MPSM3 sddm[1036]: Auth: sddm-helper crashed (exit code 15) Oct 11 10:49:04 L-UXX0MPSM3 sddm[1036]: Authentication error: "Process crashed" Oct 11 10:49:04 L-UXX0MPSM3 sddm[1036]: Auth: sddm-helper exited with 15 Oct 11 10:49:04 L-UXX0MPSM3 sddm[1036]: Socket server stopping... Oct 11 10:49:04 L-UXX0MPSM3 sddm[1036]: Socket server stopped. Oct 11 10:49:04 L-UXX0MPSM3 sddm[1036]: Display server stopping... Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopping Session 2 of user manu. Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopped Daily Cleanup of Temporary Directories. Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Closed Load/Save RF Kill Switch Status /dev/rfkill Watch. Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopping Daemon for power management... Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopped Daily apt download activities. Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopping Daemon for generating UUIDs... Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopping User Manager for UID 1002... Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopped Stop ureadahead data collection 45s after completed startup. Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopping Authenticate and Authorize Users to Run Privileged Tasks... Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopping ACPI event daemon... Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopped target Graphical Interface. Oct 11 10:49:04 L-UXX0MPSM3 rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="870" x-info="http://www.rsyslog.com;] exiting on signal 15. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Thu Oct 11 10:52:40 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: kubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake Integrated Graphics [17aa:5062] InstallationDate: Installed on 2018-04-20 (173 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 20K5S0T200
[Kernel-packages] [Bug 1797176] Re: PC is unbearably slow
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 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.19-rc7 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797176 Title: PC is unbearably slow Status in linux package in Ubuntu: Incomplete Bug description: Everything on my machine is running abnormally, unbearably slow - From opening an application from either my GUI (GNOME) to BASH. Simple tasks like checking for an update to opening a web browser is just god-aweful slow, yet it behaves just fine booting up from the HDD and running benchmarks. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_34_37_generic_44 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jeb1786 F pulseaudio /dev/snd/controlC0: jeb1786 F pulseaudio /dev/snd/controlC2: jeb1786 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Oct 10 12:09:11 2018 InstallationDate: Installed on 2018-08-17 (54 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: BIOSTAR Group A880G+ ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=a967adb1-1600-455b-8704-e2bf5de5081d ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/21/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080016 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: A880G+ dmi.board.vendor: BIOSTAR Group dmi.chassis.asset.tag: None dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/21/2011:svnBIOSTARGroup:pnA880G+:pvr:rvnBIOSTARGroup:rnA880G+:rvr:cvnBIOSTARGroup:ct3:cvr: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: A880G+ dmi.sys.vendor: BIOSTAR Group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797176/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797369] Re: package linux-modules-extra-4.15.0-36-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/4.15.0-36-generic/kernel/net/bluetooth/bluetoo
Actually, instead of testing proposed, you may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package or updates. If that does not resolve your issue, please mark the bug as "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/1797369 Title: package linux-modules-extra-4.15.0-36-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/4.15.0-36-generic/kernel/net/bluetooth/bluetooth_6lowpan.ko .dpkg-new': Operation not permitted Status in linux package in Ubuntu: Incomplete Bug description: happened before with libnvidia and libreoffice as well, packaes manually removed from status helped temporarily ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-modules-extra-4.15.0-36-generic (not installed) ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Thu Oct 11 14:29:03 2018 DuplicateSignature: package:linux-modules-extra-4.15.0-36-generic:(not installed) Unpacking linux-modules-extra-4.15.0-36-generic (4.15.0-36.39) ... dpkg: error processing archive /tmp/apt-dpkg-install-1kn4XQ/2-linux-modules-extra-4.15.0-36-generic_4.15.0-36.39_amd64.deb (--unpack): unable to open '/lib/modules/4.15.0-36-generic/kernel/net/bluetooth/bluetooth_6lowpan.ko.dpkg-new': Operation not permitted ErrorMessage: unable to open '/lib/modules/4.15.0-36-generic/kernel/net/bluetooth/bluetooth_6lowpan.ko.dpkg-new': Operation not permitted InstallationDate: Installed on 2018-09-10 (30 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: enp0s31f6 no wireless extensions. lono wireless extensions. MachineType: FUJITSU ESPRIMO P957 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=04bd5b82-6066-4b72-8f40-b307ecf4391e ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: grub-pc 2.02-2ubuntu8.4 RfKill: SourcePackage: linux Title: package linux-modules-extra-4.15.0-36-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/4.15.0-36-generic/kernel/net/bluetooth/bluetooth_6lowpan.ko.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2018 dmi.bios.vendor: FUJITSU // American Megatrends Inc. dmi.bios.version: V5.0.0.12 R1.18.0 for D3502-A1x dmi.board.name: D3502-A1 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D3502-A1 dmi.chassis.type: 3 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.12R1.18.0forD3502-A1x:bd06/11/2018:svnFUJITSU:pnESPRIMOP957:pvr:rvnFUJITSU:rnD3502-A1:rvrS26361-D3502-A1:cvnFUJITSU:ct3:cvr: dmi.product.family: ESPRIMO-FTS dmi.product.name: ESPRIMO P957 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797369/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797086] Re: Updating kernel from 4.15.0-29 to 4.15.0-36 hard disk encryption key not accpeted
Would it be possible for you to test the proposed kernel and post back if it resolves this bug? See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance! ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797086 Title: Updating kernel from 4.15.0-29 to 4.15.0-36 hard disk encryption key not accpeted Status in linux package in Ubuntu: Incomplete Bug description: I am using Ubuntu 18.04.1 LTS, and have set up hard disk encryption during installation. With new automatic software update that installed linux-image-4.15.0-36-generic kernel my password for disk encryption was rejected. The only way I could log in was through choosing the old kernel (linux-image-4.15.0-29-generic) advanced options. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797086/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797364] Re: Can't suspend X1 Carbon 6th (18.04)
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 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.19-rc7 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797364 Title: Can't suspend X1 Carbon 6th (18.04) Status in linux package in Ubuntu: Incomplete Bug description: Laptop: Lenovo X1 Carbon 6th generation, series 20KH006KPB Release: Ubuntu 18.04.1 Kernel: 4.15.0-36-generic (but also happens with newest 4.18 mainline series) Expected behavior: I can suspend and wake up my laptop by closing ad opening the lid. What actually happens: Lenovo has distributed a BIOS update recently, version 1.31, through LVFS. It installed successfully, but I believe that since the upgrade this started happening: I can suspend the laptop by closing the lid the first time after powering it ON, S3 sleep state activates, available since BIOS 1.30 (dmesg doesn't show anything weird aside from usual trackpoint/trackpad issue with this model). But then when I try to suspend it again, I close the lid and it never suspends. dmesg gives me some concerning output this time (lots of red): [ 748.266146] e1000e: enp0s31f6 NIC Link is Down [ 748.305925] wlp2s0: deauthenticating from 74:b5:7e:14:b3:c9 by local choice (Reason: 3=DEAUTH_LEAVING) [ 748.599000] PM: suspend entry (deep) [ 748.599001] PM: Syncing filesystems ... done. [ 748.607780] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 748.609834] OOM killer disabled. [ 748.609835] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 748.611275] Suspending console(s) (use no_console_suspend to debug) [ 748.613850] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6. [ 748.613851] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6. [ 748.613853] rmi4_physical rmi4-00: Failed to suspend functions: -6 [ 748.613854] rmi4_smbus 0-002c: Failed to suspend device: -6 [ 748.613858] dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6 [ 748.613859] PM: Device 0-002c failed to suspend: error -6 [ 748.631862] PM: Some devices failed to suspend, or early wake event detected [ 748.673399] OOM killer enabled. [ 748.673401] Restarting tasks ... [ 748.676264] rmi4_physical rmi4-00: rmi_driver_set_irq_bits: Failed to change enabled interrupts! [ 748.676284] psmouse: probe of serio2 failed with error -1 [ 748.676297] done. [ 748.679931] thermal thermal_zone6: failed to read out thermal zone (-61) [ 748.694583] PM: suspend exit [ 748.694682] PM: suspend entry (s2idle) [ 748.694684] PM: Syncing filesystems ... done. [ 748.700742] Freezing user space processes ... (elapsed 0.003 seconds) done. [ 748.704303] OOM killer disabled. [ 748.704304] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 748.705954] Suspending console(s) (use no_console_suspend to debug) [ 748.711552] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6. [ 748.711556] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6. [ 748.711559] rmi4_physical rmi4-00: Failed to suspend functions: -6 [ 748.711564] rmi4_smbus 0-002c: Failed to suspend device: -6 [ 748.711576] dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6 [ 748.711579] PM: Device 0-002c failed to suspend: error -6 [ 748.727561] PM: Some devices failed to suspend, or early wake event detected [ 748.769017] OOM killer enabled. [ 748.769018] Restarting tasks ... done. [ 748.772216] rmi4_physical rmi4-00: rmi_driver_set_irq_bits: Failed to change enabled interrupts! [ 748.772237] psmouse: probe of serio2 failed with error -1 [ 748.775189] thermal thermal_zone6: failed to read out thermal zone (-61) [ 748.788429] PM: suspend exit [ 748.804548] IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready [ 748.991327] IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready [ 748.993686] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 749.226795] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 749.299774] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 752.736403] wlp2s0: authenticate with 74:b5:7e:14:b3:c9 [ 752.745545] wlp2s0: send auth to 74:b5:7e:14:b3:c9 (try 1/3)
[Kernel-packages] [Bug 1797369] Re: package linux-modules-extra-4.15.0-36-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/4.15.0-36-generic/kernel/net/bluetooth/bluetoo
Would it be possible for you to test the proposed kernel and post back if it resolves this bug? See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance! ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797369 Title: package linux-modules-extra-4.15.0-36-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/4.15.0-36-generic/kernel/net/bluetooth/bluetooth_6lowpan.ko .dpkg-new': Operation not permitted Status in linux package in Ubuntu: Incomplete Bug description: happened before with libnvidia and libreoffice as well, packaes manually removed from status helped temporarily ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-modules-extra-4.15.0-36-generic (not installed) ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Thu Oct 11 14:29:03 2018 DuplicateSignature: package:linux-modules-extra-4.15.0-36-generic:(not installed) Unpacking linux-modules-extra-4.15.0-36-generic (4.15.0-36.39) ... dpkg: error processing archive /tmp/apt-dpkg-install-1kn4XQ/2-linux-modules-extra-4.15.0-36-generic_4.15.0-36.39_amd64.deb (--unpack): unable to open '/lib/modules/4.15.0-36-generic/kernel/net/bluetooth/bluetooth_6lowpan.ko.dpkg-new': Operation not permitted ErrorMessage: unable to open '/lib/modules/4.15.0-36-generic/kernel/net/bluetooth/bluetooth_6lowpan.ko.dpkg-new': Operation not permitted InstallationDate: Installed on 2018-09-10 (30 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: enp0s31f6 no wireless extensions. lono wireless extensions. MachineType: FUJITSU ESPRIMO P957 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=04bd5b82-6066-4b72-8f40-b307ecf4391e ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: grub-pc 2.02-2ubuntu8.4 RfKill: SourcePackage: linux Title: package linux-modules-extra-4.15.0-36-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/4.15.0-36-generic/kernel/net/bluetooth/bluetooth_6lowpan.ko.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2018 dmi.bios.vendor: FUJITSU // American Megatrends Inc. dmi.bios.version: V5.0.0.12 R1.18.0 for D3502-A1x dmi.board.name: D3502-A1 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D3502-A1 dmi.chassis.type: 3 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.12R1.18.0forD3502-A1x:bd06/11/2018:svnFUJITSU:pnESPRIMOP957:pvr:rvnFUJITSU:rnD3502-A1:rvrS26361-D3502-A1:cvnFUJITSU:ct3:cvr: dmi.product.family: ESPRIMO-FTS dmi.product.name: ESPRIMO P957 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797369/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797492] Re: 18.10 - AMD AGESA 1.0.0.4 bios causes kvm_amd to hang on load
The commit in the description is the the Cosmic Ubuntu-4.18.0-9 kernel. ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Also affects: linux (Ubuntu Cosmic) Importance: Medium Status: Triaged ** Changed in: linux (Ubuntu Cosmic) Status: Triaged => 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/1797492 Title: 18.10 - AMD AGESA 1.0.0.4 bios causes kvm_amd to hang on load Status in linux package in Ubuntu: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: Description: Ubuntu Cosmic Cuttlefish (development branch) Release: 18.10 4.18.0-8-generic #9-Ubuntu SMP Mon Sep 10 16:12:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux https://bugzilla.redhat.com/show_bug.cgi?id=1608242 Looks like's it's fixed in kernel 4.18.10 This is the patch: https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/commit/?id=3702a0585e64d70d5bf73bf3e943b8d6005b72c1 Other issues this causes is the systemd-udevd hanging on reboot. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matt 2179 F pulseaudio /dev/snd/controlC0: matt 2179 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-10-06 (5 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181004) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=643f18e2-2cd4-4eff-8659-4a4bbe9ecb35 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 Tags: cosmic Uname: Linux 4.18.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/03/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: X470 Taichi Ultimate 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.50:bd07/03/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470TaichiUltimate: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. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797492/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1760338] Re: Touchpad hotkey 'functional' but has no effect in 18.04 (Bionic)
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 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.19-rc7 ** Package changed: linux-signed (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1760338 Title: Touchpad hotkey 'functional' but has no effect in 18.04 (Bionic) Status in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in xinput package in Ubuntu: Confirmed Status in xserver-xorg-input-synaptics package in Ubuntu: Confirmed Bug description: All the Fn keys are working (audio, mute, bright, volume and even wifi) except for enable/disable touchpad. No display info and no effect. PS: Fn Bright up/down takes about 3s to work the first time or if not used for about 2 minutes. Volume also have a similar problem but only the first time it is used. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xinput 1.6.2-1build1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.42 Sat Mar 3 04:10:22 PST 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-13ubuntu1) ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Sat Mar 31 15:41:59 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.42, 4.15.0-12-generic, x86_64: installed nvidia, 390.42, 4.15.0-13-generic, x86_64: installed virtualbox, 5.2.8, 4.15.0-12-generic, x86_64: installed virtualbox, 5.2.8, 4.15.0-13-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems HD Graphics 530 [1179:f840] InstallationDate: Installed on 2018-03-09 (21 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 04f2:b446 Chicony Electronics Co., Ltd Bus 001 Device 003: ID 248a:8366 Bus 001 Device 002: ID 04f3:2228 Elan Microelectronics Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TOSHIBA Satellite S55t-C ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=62fa4fcd-f1c6-43f5-a86d-ccaae2565dac ro locale=pt_BR quiet splash vt.handoff=1 SourcePackage: xinput UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.20 dmi.board.name: 06F4 dmi.board.vendor: FF50 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr1.20:bd10/08/2015:svnTOSHIBA:pnSatelliteS55t-C:pvrPSPUGU-00200D:rvnFF50:rn06F4:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Type1Family dmi.product.name: Satellite S55t-C dmi.product.version: PSPUGU-00200D dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1797420] Re: rtl8192cu driver and D-Link DWA-121 USB WiFi dongle LED issues - Ubuntu 18.04
** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797420 Title: rtl8192cu driver and D-Link DWA-121 USB WiFi dongle LED issues - Ubuntu 18.04 Status in linux package in Ubuntu: Incomplete Bug description: In the Linux kernel version 4.15.0-36-generic with the D-Link DWA-121 mini USB WiFi using the rtl8192cu driver on Ubuntu 18.04, it appears that the driver is not controlling the blue LED that blinks when there is download/upload going on, so the LED keeps on. This will cause users of this dongle to open network statistics to see if there is download/upload going on rather than simply looking at the LED. It's time consuming. The driver works fine on Windows, so it's a driver issue. It didn't affect my AP performance. It's just the LED that doesn't blink. - Steps to reproduce: 1. Install Ubuntu 18.04 on a system that has D-Link DWA-121 mini USB WiFi dongle or try it live 2. Look at the statistics light (blue LED) on the dongle. It's not blinking, whether there is download/upload or not. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-36-generic 4.15.0-36.39 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-36-generic. ApportVersion: 2.20.9-0ubuntu7.4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eofla 1001 F pulseaudio Card0.Amixer.info: Card hw:0 'V8235'/'VIA 8235 with ALC650F at 0xe000, irq 22' Mixer name : 'Realtek ALC650F' Components : 'AC97a:414c4723' Controls : 62 Simple ctrls : 36 CurrentDesktop: LXDE Date: Thu Oct 11 19:15:25 2018 InstallationDate: Installed on 2018-09-28 (13 days ago) InstallationMedia: Lubuntu 18.04.1 LTS "Bionic Beaver" - Release i386 (20180725) MachineType: MSI MS-6712 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=e0d9a13c-6776-4241-b61f-164ae076b371 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: irda via_ircc UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6712 dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: 0123ABC dmi.chassis.type: 3 dmi.chassis.vendor: Uknown Chassis Manufacture dmi.chassis.version: Version 1.00 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrVersion07.00T:bd04/02/01:svnMSI:pnMS-6712:pvr1.0:rvnMSI:rnMS-6712:rvr1.0:cvnUknownChassisManufacture:ct3:cvrVersion1.00: dmi.product.name: MS-6712 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797538] Re: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 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.19-rc7 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797538 Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85] Status in linux package in Ubuntu: Incomplete Bug description: Dell XPS 15 9570 ProblemType: KernelOops DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob2250 F pulseaudio Date: Fri Oct 12 08:54:08 2018 Failure: oops InstallationDate: Installed on 2018-10-12 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=b1c8d7c6-d9ec-495c-9770-18e7120e87d5 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85] UpgradeStatus: Upgraded to cosmic on 2018-10-12 (0 days ago) dmi.bios.date: 09/03/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797538/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793086] Re: qeth: use vzalloc for QUERY OAT buffer
** Changed in: ubuntu-z-systems
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/1793086
Title:
qeth: use vzalloc for QUERY OAT buffer
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Released
Bug description:
== SRU Justification ==
IBM reports the qethqoat tool fails. qeth_query_oat_command() currently
allocates the kernel buffer for the SIOC_QETH_QUERY_OAT ioctl with kzalloc.
This commit will cause the use of vzalloc() instead of kzalloc(), backing
the allocation with non-contiguous memory.
Xenial also needs this commit, but requres a slightly different
backport. It's SRU will be sent separate.
== Fix ==
aec45e857c55 ("s390/qeth: use vzalloc for QUERY OAT buffer")
== Regression Potential ==
Low, limited to s390.
== Test Case ==
IBM verified testing of this commit up-front.
Description: qeth: use vzalloc for QUERY OAT buffer
Symptom: qethqoat tool fails.
Problem: qeth_query_oat_command() currently allocates the kernel
buffer for the SIOC_QETH_QUERY_OAT ioctl with kzalloc.
Solution: Using vzalloc() instead of kzalloc(), backing the
allocation with non-contiguous memory.
Commit -ID: aec45e857c5538664edb76a60dd452e3265f37d1
kernel 4.19.
To be fixed for 18.10, 18,04 and 16.04.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1793086/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795583] Re: linux-aws: 4.4.0-1032.35 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1795583 Title: linux-aws: 4.4.0-1032.35 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released 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 -- boot-testing-requested: true kernel-stable-master-bug: 1795582 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1795583/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795585] Re: linux-aws: 4.4.0-1070.80 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1795585 Title: linux-aws: 4.4.0-1070.80 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released 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: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1795582 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1795585/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1794346] Re: check and fix zkey required kernel modules locations in debs, udebs, and initramfs
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1794346
Title:
check and fix zkey required kernel modules locations in debs, udebs,
and initramfs
Status in Ubuntu on IBM z Systems:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in s390-tools package in Ubuntu:
Fix Released
Bug description:
todo: check that these modules are included in the initramfs as well.
=== linux crypto-modules udeb task ==
linux-modules-4.18.0-8-generic has:
./lib/modules/4.18.0-8-generic/kernel/arch/s390/crypto/paes_s390.ko
./lib/modules/4.18.0-8-generic/kernel/drivers/s390/crypto/pkey.ko
./lib/modules/4.18.0-8-generic/kernel/drivers/s390/crypto/zcrypt.ko
./lib/modules/4.18.0-8-generic/kernel/drivers/s390/crypto/zcrypt_cex2a.ko
./lib/modules/4.18.0-8-generic/kernel/drivers/s390/crypto/zcrypt_cex4.ko
./lib/modules/4.18.0-8-generic/kernel/drivers/s390/crypto/zcrypt_pcixcc.ko
All of the above appear to be missing from the crypto-modules-4.18.0-8
-generic-di, please ship them in crypto-modules udeb.
To avoid discrepancies as to what crypto is supported by the installed
system, versus d-i environment, it would be nice to make udebs and
linux-modules packages roughly the same.
Does it at all make sense to ship matching set of
kernel/{arch,drivers}/s390/crypto/*.ko in crypto-modules udeb, as shilled in
linux-modules deb?
===
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1794346/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795453] Re: IO's are issued with incorrect Scatter Gather Buffer
Looks like the issue is not seen with 4.18 kernel , please let me know still Ubuntu requires the log with 4.15 kernel ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1795453 Title: IO's are issued with incorrect Scatter Gather Buffer Status in linux package in Ubuntu: Incomplete Bug description: We have observed that OS is sending the IO's (SCSI Read/Write) with incorrect Scatter Gather Buffer address . i.e OS is sending the IO with 64 bit Scatter Gather Buffer address , such that if we add the length with buffer address then it causes the roll over . Here is the data we captured in our driver (Printed the SGE details which was sent by OS) sgl_ptr->Address = f000 [14547.313240] sgl_ptr->Length = 1000 [14547.313241] sge_count = 18 [14547.313242] cmd->index = 9d9 Note : This issue is observed only when virtualization is enabled Product : Broadcom (LSI) Megaraid H840 controller To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795453/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode
@Eric : The server was installed with a 4.15.0-34.37 kernel from a corporate OS image, and linux-cloud-tools-common package was also in version 4.15.0-34.37. All packages where in state "ii". I dist-upgrade the server with APT (to version 4.15.0-36.39) and only downgrade the linux-cloud-tools-common package in order to only let unattended-upgrades try to upgrade the linux-cloud-tools-common package and have simpler unattended-upgrades logs to analyze. Upgrading the linux-cloud-tools-common simultaneously with the other kernel packages leeds to the same result. Also, all packages where in state "ii" before running unattended- upgrades. Let me know if you want me to delete the server and deploy it once more with another "fresh" test case. -- 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/1796376 Title: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode Status in linux package in Ubuntu: Confirmed Bug description: Since the following linux-cloud-tools-common package versions : Xenial : 4.4.0-135.161 Bionic : 4.15.0-34.37 the Systemd service unit file for hv-kvp-daemon has been modified with new dependencies that make the package unable to be upgraded with unattended-upgrades on shutdown mode. Unattended-upgrades hangs with the linux-cloud-tools-common package during "Preparing to unpack". The server restarts after the unattended-upgrades service timeout expires. - Package state after reboot : iFR linux-cloud-tools-common 4.15.0-34.37 all Linux kernel version specific cloud tools for version 4.15.0 - Unattended-upgrades dpkg logs : Log started: 2018-10-05 17:59:04 (Reading database ... 52043 files and directories currently installed.) Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ... Log ended: 2018-10-05 18:00:54 - Impact : The current impact is very important as all security updates are blocked until you manually fix each server with : dpkg --configure -a apt install --only-upgrade linux-cloud-tools-common - Workaround/Fix : As a simple straightforward fix, replacing : Before=shutdown.target cloud-init-local.service walinuxagent.service with : Before=shutdown.target walinuxagent.service makes the package upgradable during shutdown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797359] Re: Not work 802.11ac WLAN Adapter
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797359 Title: Not work 802.11ac WLAN Adapter Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: Hello, At the moment I have two WiFi adapters: 1) TP-LINK TL-WN722N (working) 2) USB WiFi adapter (not working) Initial report: Bug 1743872 Best regards, - Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-9-generic 4.18.0-9.10 ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12 Uname: Linux 4.18.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2027 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 11 07:57:40 2018 InstallationDate: Installed on 2017-10-13 (362 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-9-generic root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-9-generic N/A linux-backports-modules-4.18.0-9-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 530U3C/530U4C dmi.product.sku: System SKUNumber dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1797359/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795596] Re: linux-lts-trusty: 3.13.0-161.211~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released -- 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/1795596 Title: linux-lts-trusty: 3.13.0-161.211~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released 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 -- boot-testing-requested: true kernel-stable-master-bug: 1795595 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1795596/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796346] Re: linux: 4.18.0-9.10 -proposed tracker
The package has been published and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow/promote-to-release Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Description changed: This bug is for tracking the 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 1796347 (linux-hwe-edge), bug 1796348 (linux-azure-edge) derivatives: bug 1796349 (linux-raspi2), bug 1796350 (linux-azure), bug 1796351 (linux-gcp), bug 1796353 (linux-kvm) -- swm properties -- phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true + kernel-phase:Released + kernel-phase-changed:Friday, 12. October 2018 14:08 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 1796347 (linux-hwe-edge), bug 1796348 (linux-azure-edge) derivatives: bug 1796349 (linux-raspi2), bug 1796350 (linux-azure), bug 1796351 (linux-gcp), bug 1796353 (linux-kvm) -- swm properties -- - phase: Promoted to proposed + phase: Released proposed-announcement-sent: true proposed-testing-requested: true - kernel-phase:Released - kernel-phase-changed:Friday, 12. October 2018 14:08 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/1796346 Title: linux: 4.18.0-9.10 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in debian-installer package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in debian-installer source package in Cosmic: Fix Released Status in linux source package in Cosmic: 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 1796347 (linux-hwe-edge), bug 1796348 (linux-azure-edge) derivatives: bug 1796349 (linux-raspi2), bug 1796350 (linux-azure), bug 1796351 (linux-gcp), bug 1796353 (linux-kvm) -- swm properties -- phase: Released proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1796346/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode
and send me the generated sosreport file : sla...@ubuntu.com (if sensible data) otherwise attach to the lp bug. -- 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/1796376 Title: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode Status in linux package in Ubuntu: Confirmed Bug description: Since the following linux-cloud-tools-common package versions : Xenial : 4.4.0-135.161 Bionic : 4.15.0-34.37 the Systemd service unit file for hv-kvp-daemon has been modified with new dependencies that make the package unable to be upgraded with unattended-upgrades on shutdown mode. Unattended-upgrades hangs with the linux-cloud-tools-common package during "Preparing to unpack". The server restarts after the unattended-upgrades service timeout expires. - Package state after reboot : iFR linux-cloud-tools-common 4.15.0-34.37 all Linux kernel version specific cloud tools for version 4.15.0 - Unattended-upgrades dpkg logs : Log started: 2018-10-05 17:59:04 (Reading database ... 52043 files and directories currently installed.) Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ... Log ended: 2018-10-05 18:00:54 - Impact : The current impact is very important as all security updates are blocked until you manually fix each server with : dpkg --configure -a apt install --only-upgrade linux-cloud-tools-common - Workaround/Fix : As a simple straightforward fix, replacing : Before=shutdown.target cloud-init-local.service walinuxagent.service with : Before=shutdown.target walinuxagent.service makes the package upgradable during shutdown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797563] Re: Xenial update: 4.4.156 upstream stable release
Skipped "x86/speculation/l1tf: Fix up pte->pfn conversion for PAE"
because we already use the proper conversion.
Skipped because we already applied it for CVE-2018-6554
* "irda: Fix memory leak caused by repeated binds of irda socket"
Skipped because we already applied it for CVE-2018-6555
* "irda: Only insert new objects into the global database via
setsockopt"
Adjusted context for "ovl: rename is_merge to is_lowest".
Major rewrite of "ovl: override creds with the ones from the superblock
mounter" because we did apply in the past "SAUCE: overlayfs: Replace
ovl_prepare_creds() with ovl_override_creds()" for bug #1659417. Both
are nearly identical but use different internal names. So the upstream
patch got modified to convert things to the upstream layout.
Skipped "s390/lib: use expoline for all bcr instructions" because we
already applied it for CVE-2017-5715.
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-5715
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-6554
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-6555
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+ by originating either directly from a mainline/stable Linux tree or
+ a minimally backported form of that patch. The following upstream
+ stable patches should be included in the Ubuntu kernel:
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+ 4.4.156 upstream stable release
+ from git://git.kernel.org/
-4.4.156 upstream stable release
-from git://git.kernel.org/
+ The following patches will be applied:
+ * staging: android: ion: fix ION_IOC_{MAP,SHARE} use-after-free
+ * net: bcmgenet: use MAC link status for fixed phy
+ * qlge: Fix netdev features configuration.
+ * tcp: do not restart timewait timer on rst reception
+ * vti6: remove !skb->ignore_df check from vti6_xmit()
+ * cifs: check if SMB2 PDU size has been padded and suppress the warning
+ * hfsplus: don't return 0 when fill_super() failed
+ * hfs: prevent crash on exit from failed search
+ * fork: don't copy inconsistent signal handler state to child
+ * reiserfs: change j_timestamp type to time64_t
+ * hfsplus: fix NULL dereference in hfsplus_lookup()
+ * fat: validate ->i_start before using
+ * scripts: modpost: check memory allocation results
+ * mm/fadvise.c: fix signed overflow UBSAN complaint
+ * fs/dcache.c: fix kmemcheck splat at take_dentry_name_snapshot()
+ * ipvs: fix race between ip_vs_conn_new() and ip_vs_del_dest()
+ * mfd: sm501: Set coherent_dma_mask when creating subdevices
+ * platform/x86: asus-nb-wmi: Add keymap entry for lid flip action on UX360
+ * irqchip/bcm7038-l1: Hide cpu offline callback when building for !SMP
+ * net/9p: fix error path of p9_virtio_probe
+ * powerpc: Fix size calculation using resource_size()
+ * s390/dasd: fix hanging offline processing due to canceled worker
+ * scsi: aic94xx: fix an error code in aic94xx_init()
+ * PCI: mvebu: Fix I/O space end address calculation
+ * dm kcopyd: avoid softlockup in run_complete_job
+ * staging: comedi: ni_mio_common: fix subdevice flags for PFI subdevice
+ * selftests/powerpc: Kill child processes on SIGINT
+ * smb3: fix reset of bytes read and written stats
+ * SMB3: Number of requests sent should be displayed for SMB3 not just CIFS
+ * powerpc/pseries: Avoid using the size greater than RTAS_ERROR_LOG_MAX.
+ * btrfs: replace: Reset on-disk dev stats value after replace
+ * btrfs: relocation: Only remove reloc rb_trees if reloc control has been
+ initialized
+ * btrfs: Don't remove block group that still has pinned down bytes
+ * debugobjects: Make stack check warning more informative
+ * x86/pae: use 64 bit atomic xchg function in native_ptep_get_and_clear
+ * kbuild: make missing $DEPMOD a Warning instead of an Error
+ * Revert "ARM: imx_v6_v7_defconfig: Select ULPI support"
+ * enic: do not call enic_change_mtu in enic_probe
+ * Fixes: Commit cdbf92675fad ("mm: numa: avoid waiting on freed migrated
pages")
+ * genirq: Delay incrementing interrupt count if it's disabled/pending
+ * irqchip/gic-v3-its: Recompute the number of pages on page size change
+ * irqchip/gicv3-its: Fix memory leak in its_free_tables()
+ * irqchip/gicv3-its: Avoid cache flush beyond ITS_BASERn memory size
+ * irqchip/gic-v3: Add missing barrier to 32bit version of
[Kernel-packages] [Bug 1771245] Re: [ICL] Touch support
This bug was fixed in the package linux - 4.18.0-9.10
---
linux (4.18.0-9.10) cosmic; urgency=medium
* linux: 4.18.0-9.10 -proposed tracker (LP: #1796346)
* Cosmic update: v4.18.12 upstream stable release (LP: #1796139)
- crypto: skcipher - Fix -Wstringop-truncation warnings
- iio: adc: ina2xx: avoid kthread_stop() with stale task_struct
- tsl2550: fix lux1_input error in low light
- misc: ibmvmc: Use GFP_ATOMIC under spin lock
- vmci: type promotion bug in qp_host_get_user_memory()
- siox: don't create a thread without starting it
- x86/numa_emulation: Fix emulated-to-physical node mapping
- staging: rts5208: fix missing error check on call to rtsx_write_register
- power: supply: axp288_charger: Fix initial constant_charge_current value
- misc: sram: enable clock before registering regions
- serial: sh-sci: Stop RX FIFO timer during port shutdown
- uwb: hwa-rc: fix memory leak at probe
- power: vexpress: fix corruption in notifier registration
- iommu/amd: make sure TLB to be flushed before IOVA freed
- Bluetooth: Add a new Realtek 8723DE ID 0bda:b009
- USB: serial: kobil_sct: fix modem-status error handling
- 6lowpan: iphc: reset mac_header after decompress to fix panic
- iommu/msm: Don't call iommu_device_{,un}link from atomic context
- s390/mm: correct allocate_pgste proc_handler callback
- power: remove possible deadlock when unregistering power_supply
- drm/amd/display/dc/dce: Fix multiple potential integer overflows
- drm/amd/display: fix use of uninitialized memory
- md-cluster: clear another node's suspend_area after the copy is finished
- cxgb4: Fix the condition to check if the card is T5
- RDMA/bnxt_re: Fix a couple off by one bugs
- RDMA/i40w: Hold read semaphore while looking after VMA
- RDMA/bnxt_re: Fix a bunch of off by one bugs in qplib_fp.c
- IB/core: type promotion bug in rdma_rw_init_one_mr()
- media: exynos4-is: Prevent NULL pointer dereference in
__isp_video_try_fmt()
- IB/mlx4: Test port number before querying type.
- powerpc/kdump: Handle crashkernel memory reservation failure
- media: fsl-viu: fix error handling in viu_of_probe()
- vhost_net: Avoid tx vring kicks during busyloop
- media: staging/imx: fill vb2_v4l2_buffer field entry
- IB/mlx5: Fix GRE flow specification
- include/rdma/opa_addr.h: Fix an endianness issue
- x86/tsc: Add missing header to tsc_msr.c
- ARM: hwmod: RTC: Don't assume lock/unlock will be called with irq enabled
- x86/entry/64: Add two more instruction suffixes
- ARM: dts: ls1021a: Add missing cooling device properties for CPUs
- scsi: target/iscsi: Make iscsit_ta_authentication() respect the output
buffer size
- thermal: i.MX: Allow thermal probe to fail gracefully in case of bad
calibration.
- scsi: klist: Make it safe to use klists in atomic context
- scsi: ibmvscsi: Improve strings handling
- scsi: target: Avoid that EXTENDED COPY commands trigger lock inversion
- usb: wusbcore: security: cast sizeof to int for comparison
- ath10k: sdio: use same endpoint id for all packets in a bundle
- ath10k: sdio: set skb len for all rx packets
- powerpc/powernv/ioda2: Reduce upper limit for DMA window size
- platform/x86: asus-wireless: Fix uninitialized symbol usage
- ACPI / button: increment wakeup count only when notified
- s390/sysinfo: add missing #ifdef CONFIG_PROC_FS
- alarmtimer: Prevent overflow for relative nanosleep
- s390/dasd: correct numa_node in dasd_alloc_queue
- s390/scm_blk: correct numa_node in scm_blk_dev_setup
- s390/extmem: fix gcc 8 stringop-overflow warning
- mtd: rawnand: atmel: add module param to avoid using dma
- iio: accel: adxl345: convert address field usage in iio_chan_spec
- posix-timers: Make forward callback return s64
- posix-timers: Sanitize overrun handling
- ALSA: snd-aoa: add of_node_put() in error path
- selftests: forwarding: Tweak tc filters for mirror-to-gretap tests
- ath10k: use locked skb_dequeue for rx completions
- media: s3c-camif: ignore -ENOIOCTLCMD from v4l2_subdev_call for s_power
- media: soc_camera: ov772x: correct setting of banding filter
- media: omap3isp: zero-initialize the isp cam_xclk{a,b} initial data
- media: ov772x: add checks for register read errors
- staging: android: ashmem: Fix mmap size validation
- media: ov772x: allow i2c controllers without I2C_FUNC_PROTOCOL_MANGLING
- staging: mt7621-eth: Fix memory leak in mtk_add_mac() error path
- drivers/tty: add error handling for pcmcia_loop_config
- arm64: dts: renesas: salvator-common: Fix adv7482 decimal unit addresses
- serial: pxa: Fix an error handling path in 'serial_pxa_probe()'
- staging: mt7621-dts: Fix remaining pcie warnings
- media: tm6000: add error handling for dvb_register_adapter
- ASoC: qdsp6: qdafe:
[Kernel-packages] [Bug 1787089] Re: [AEP-bug] ext4: more rare direct I/O vs unmap failures
This bug was fixed in the package linux - 4.18.0-9.10
---
linux (4.18.0-9.10) cosmic; urgency=medium
* linux: 4.18.0-9.10 -proposed tracker (LP: #1796346)
* Cosmic update: v4.18.12 upstream stable release (LP: #1796139)
- crypto: skcipher - Fix -Wstringop-truncation warnings
- iio: adc: ina2xx: avoid kthread_stop() with stale task_struct
- tsl2550: fix lux1_input error in low light
- misc: ibmvmc: Use GFP_ATOMIC under spin lock
- vmci: type promotion bug in qp_host_get_user_memory()
- siox: don't create a thread without starting it
- x86/numa_emulation: Fix emulated-to-physical node mapping
- staging: rts5208: fix missing error check on call to rtsx_write_register
- power: supply: axp288_charger: Fix initial constant_charge_current value
- misc: sram: enable clock before registering regions
- serial: sh-sci: Stop RX FIFO timer during port shutdown
- uwb: hwa-rc: fix memory leak at probe
- power: vexpress: fix corruption in notifier registration
- iommu/amd: make sure TLB to be flushed before IOVA freed
- Bluetooth: Add a new Realtek 8723DE ID 0bda:b009
- USB: serial: kobil_sct: fix modem-status error handling
- 6lowpan: iphc: reset mac_header after decompress to fix panic
- iommu/msm: Don't call iommu_device_{,un}link from atomic context
- s390/mm: correct allocate_pgste proc_handler callback
- power: remove possible deadlock when unregistering power_supply
- drm/amd/display/dc/dce: Fix multiple potential integer overflows
- drm/amd/display: fix use of uninitialized memory
- md-cluster: clear another node's suspend_area after the copy is finished
- cxgb4: Fix the condition to check if the card is T5
- RDMA/bnxt_re: Fix a couple off by one bugs
- RDMA/i40w: Hold read semaphore while looking after VMA
- RDMA/bnxt_re: Fix a bunch of off by one bugs in qplib_fp.c
- IB/core: type promotion bug in rdma_rw_init_one_mr()
- media: exynos4-is: Prevent NULL pointer dereference in
__isp_video_try_fmt()
- IB/mlx4: Test port number before querying type.
- powerpc/kdump: Handle crashkernel memory reservation failure
- media: fsl-viu: fix error handling in viu_of_probe()
- vhost_net: Avoid tx vring kicks during busyloop
- media: staging/imx: fill vb2_v4l2_buffer field entry
- IB/mlx5: Fix GRE flow specification
- include/rdma/opa_addr.h: Fix an endianness issue
- x86/tsc: Add missing header to tsc_msr.c
- ARM: hwmod: RTC: Don't assume lock/unlock will be called with irq enabled
- x86/entry/64: Add two more instruction suffixes
- ARM: dts: ls1021a: Add missing cooling device properties for CPUs
- scsi: target/iscsi: Make iscsit_ta_authentication() respect the output
buffer size
- thermal: i.MX: Allow thermal probe to fail gracefully in case of bad
calibration.
- scsi: klist: Make it safe to use klists in atomic context
- scsi: ibmvscsi: Improve strings handling
- scsi: target: Avoid that EXTENDED COPY commands trigger lock inversion
- usb: wusbcore: security: cast sizeof to int for comparison
- ath10k: sdio: use same endpoint id for all packets in a bundle
- ath10k: sdio: set skb len for all rx packets
- powerpc/powernv/ioda2: Reduce upper limit for DMA window size
- platform/x86: asus-wireless: Fix uninitialized symbol usage
- ACPI / button: increment wakeup count only when notified
- s390/sysinfo: add missing #ifdef CONFIG_PROC_FS
- alarmtimer: Prevent overflow for relative nanosleep
- s390/dasd: correct numa_node in dasd_alloc_queue
- s390/scm_blk: correct numa_node in scm_blk_dev_setup
- s390/extmem: fix gcc 8 stringop-overflow warning
- mtd: rawnand: atmel: add module param to avoid using dma
- iio: accel: adxl345: convert address field usage in iio_chan_spec
- posix-timers: Make forward callback return s64
- posix-timers: Sanitize overrun handling
- ALSA: snd-aoa: add of_node_put() in error path
- selftests: forwarding: Tweak tc filters for mirror-to-gretap tests
- ath10k: use locked skb_dequeue for rx completions
- media: s3c-camif: ignore -ENOIOCTLCMD from v4l2_subdev_call for s_power
- media: soc_camera: ov772x: correct setting of banding filter
- media: omap3isp: zero-initialize the isp cam_xclk{a,b} initial data
- media: ov772x: add checks for register read errors
- staging: android: ashmem: Fix mmap size validation
- media: ov772x: allow i2c controllers without I2C_FUNC_PROTOCOL_MANGLING
- staging: mt7621-eth: Fix memory leak in mtk_add_mac() error path
- drivers/tty: add error handling for pcmcia_loop_config
- arm64: dts: renesas: salvator-common: Fix adv7482 decimal unit addresses
- serial: pxa: Fix an error handling path in 'serial_pxa_probe()'
- staging: mt7621-dts: Fix remaining pcie warnings
- media: tm6000: add error handling for dvb_register_adapter
- ASoC: qdsp6: qdafe:
[Kernel-packages] [Bug 1795589] Re: linux-kvm: 4.4.0-1036.42 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released -- 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/1795589 Title: linux-kvm: 4.4.0-1036.42 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1795582 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1795589/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783964] Re: Please make CONFIG_PWM_LPSS_PCI and CONFIG_PWM_LPSS_PLATFORM built in to make brightness adjustment working on various BayTrail/CherryTrail-based devices
This bug was fixed in the package linux - 4.18.0-9.10
---
linux (4.18.0-9.10) cosmic; urgency=medium
* linux: 4.18.0-9.10 -proposed tracker (LP: #1796346)
* Cosmic update: v4.18.12 upstream stable release (LP: #1796139)
- crypto: skcipher - Fix -Wstringop-truncation warnings
- iio: adc: ina2xx: avoid kthread_stop() with stale task_struct
- tsl2550: fix lux1_input error in low light
- misc: ibmvmc: Use GFP_ATOMIC under spin lock
- vmci: type promotion bug in qp_host_get_user_memory()
- siox: don't create a thread without starting it
- x86/numa_emulation: Fix emulated-to-physical node mapping
- staging: rts5208: fix missing error check on call to rtsx_write_register
- power: supply: axp288_charger: Fix initial constant_charge_current value
- misc: sram: enable clock before registering regions
- serial: sh-sci: Stop RX FIFO timer during port shutdown
- uwb: hwa-rc: fix memory leak at probe
- power: vexpress: fix corruption in notifier registration
- iommu/amd: make sure TLB to be flushed before IOVA freed
- Bluetooth: Add a new Realtek 8723DE ID 0bda:b009
- USB: serial: kobil_sct: fix modem-status error handling
- 6lowpan: iphc: reset mac_header after decompress to fix panic
- iommu/msm: Don't call iommu_device_{,un}link from atomic context
- s390/mm: correct allocate_pgste proc_handler callback
- power: remove possible deadlock when unregistering power_supply
- drm/amd/display/dc/dce: Fix multiple potential integer overflows
- drm/amd/display: fix use of uninitialized memory
- md-cluster: clear another node's suspend_area after the copy is finished
- cxgb4: Fix the condition to check if the card is T5
- RDMA/bnxt_re: Fix a couple off by one bugs
- RDMA/i40w: Hold read semaphore while looking after VMA
- RDMA/bnxt_re: Fix a bunch of off by one bugs in qplib_fp.c
- IB/core: type promotion bug in rdma_rw_init_one_mr()
- media: exynos4-is: Prevent NULL pointer dereference in
__isp_video_try_fmt()
- IB/mlx4: Test port number before querying type.
- powerpc/kdump: Handle crashkernel memory reservation failure
- media: fsl-viu: fix error handling in viu_of_probe()
- vhost_net: Avoid tx vring kicks during busyloop
- media: staging/imx: fill vb2_v4l2_buffer field entry
- IB/mlx5: Fix GRE flow specification
- include/rdma/opa_addr.h: Fix an endianness issue
- x86/tsc: Add missing header to tsc_msr.c
- ARM: hwmod: RTC: Don't assume lock/unlock will be called with irq enabled
- x86/entry/64: Add two more instruction suffixes
- ARM: dts: ls1021a: Add missing cooling device properties for CPUs
- scsi: target/iscsi: Make iscsit_ta_authentication() respect the output
buffer size
- thermal: i.MX: Allow thermal probe to fail gracefully in case of bad
calibration.
- scsi: klist: Make it safe to use klists in atomic context
- scsi: ibmvscsi: Improve strings handling
- scsi: target: Avoid that EXTENDED COPY commands trigger lock inversion
- usb: wusbcore: security: cast sizeof to int for comparison
- ath10k: sdio: use same endpoint id for all packets in a bundle
- ath10k: sdio: set skb len for all rx packets
- powerpc/powernv/ioda2: Reduce upper limit for DMA window size
- platform/x86: asus-wireless: Fix uninitialized symbol usage
- ACPI / button: increment wakeup count only when notified
- s390/sysinfo: add missing #ifdef CONFIG_PROC_FS
- alarmtimer: Prevent overflow for relative nanosleep
- s390/dasd: correct numa_node in dasd_alloc_queue
- s390/scm_blk: correct numa_node in scm_blk_dev_setup
- s390/extmem: fix gcc 8 stringop-overflow warning
- mtd: rawnand: atmel: add module param to avoid using dma
- iio: accel: adxl345: convert address field usage in iio_chan_spec
- posix-timers: Make forward callback return s64
- posix-timers: Sanitize overrun handling
- ALSA: snd-aoa: add of_node_put() in error path
- selftests: forwarding: Tweak tc filters for mirror-to-gretap tests
- ath10k: use locked skb_dequeue for rx completions
- media: s3c-camif: ignore -ENOIOCTLCMD from v4l2_subdev_call for s_power
- media: soc_camera: ov772x: correct setting of banding filter
- media: omap3isp: zero-initialize the isp cam_xclk{a,b} initial data
- media: ov772x: add checks for register read errors
- staging: android: ashmem: Fix mmap size validation
- media: ov772x: allow i2c controllers without I2C_FUNC_PROTOCOL_MANGLING
- staging: mt7621-eth: Fix memory leak in mtk_add_mac() error path
- drivers/tty: add error handling for pcmcia_loop_config
- arm64: dts: renesas: salvator-common: Fix adv7482 decimal unit addresses
- serial: pxa: Fix an error handling path in 'serial_pxa_probe()'
- staging: mt7621-dts: Fix remaining pcie warnings
- media: tm6000: add error handling for dvb_register_adapter
- ASoC: qdsp6: qdafe:
[Kernel-packages] [Bug 1796385] Re: watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112]
https://bugzilla.kernel.org/show_bug.cgi?id=201379#c3 We lack the 'Call Trace' -- Cristian Aravena Romero (caravena) -- 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/1796385 Title: watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112] Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: I can use the system for a while, then at random, the screen blinks and freezes. Must reboot. Seems to happen both with Wayland and Xorg. ProblemType: KernelOops DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: greg 2039 F pulseaudio /dev/snd/controlC1: greg 2039 F pulseaudio Date: Tue Oct 2 15:56:23 2018 Failure: oops InstallationDate: Installed on 2018-09-28 (7 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. Default string ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=ce06b10d-2a7f-49db-a15b-85554d9a7e4d ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: X99-UD4-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.:bvrF23:bd06/07/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99-UD4-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1796385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796351] Re: linux-gcp: 4.18.0-1002.3 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released -- 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/1796351 Title: linux-gcp: 4.18.0-1002.3 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux-gcp package in Ubuntu: Confirmed Status in linux-gcp source package in Cosmic: 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-master-bug: 1796346 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1796351/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode
Can you confirm the state of the package pre-upgrade ? -- 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/1796376 Title: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode Status in linux package in Ubuntu: Confirmed Bug description: Since the following linux-cloud-tools-common package versions : Xenial : 4.4.0-135.161 Bionic : 4.15.0-34.37 the Systemd service unit file for hv-kvp-daemon has been modified with new dependencies that make the package unable to be upgraded with unattended-upgrades on shutdown mode. Unattended-upgrades hangs with the linux-cloud-tools-common package during "Preparing to unpack". The server restarts after the unattended-upgrades service timeout expires. - Package state after reboot : iFR linux-cloud-tools-common 4.15.0-34.37 all Linux kernel version specific cloud tools for version 4.15.0 - Unattended-upgrades dpkg logs : Log started: 2018-10-05 17:59:04 (Reading database ... 52043 files and directories currently installed.) Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ... Log ended: 2018-10-05 18:00:54 - Impact : The current impact is very important as all security updates are blocked until you manually fix each server with : dpkg --configure -a apt install --only-upgrade linux-cloud-tools-common - Workaround/Fix : As a simple straightforward fix, replacing : Before=shutdown.target cloud-init-local.service walinuxagent.service with : Before=shutdown.target walinuxagent.service makes the package upgradable during shutdown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796351] Re: linux-gcp: 4.18.0-1002.3 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-release Status: New => Confirmed ** Tags removed: block-proposed-cosmic ** Tags removed: 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/1796351 Title: linux-gcp: 4.18.0-1002.3 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux-gcp package in Ubuntu: Confirmed Status in linux-gcp source package in Cosmic: 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-master-bug: 1796346 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1796351/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796350] Re: linux-azure: 4.18.0-1003.3 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1796350 Title: linux-azure: 4.18.0-1003.3 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in linux-azure package in Ubuntu: Confirmed Status in linux-azure source package in Cosmic: 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-master-bug: 1796346 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1796350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode
Seems to me like the package "4.15.0-34.37" was already not in "ii" state : 2018-10-10 10:16:57 status half-configured linux-cloud-tools-4.15.0-34-generic:amd64 4.15.0-34.37 2018-10-10 10:16:57 status half-installed linux-cloud-tools-4.15.0-34-generic:amd64 4.15.0-34.37 2018-10-10 10:16:57 status half-configured linux-cloud-tools-4.15.0-34:amd64 4.15.0-34.37 2018-10-10 10:16:57 status half-installed linux-cloud-tools-4.15.0-34:amd64 4.15.0-34.37 2018-10-10 10:45:05 status half-configured linux-cloud-tools-common:all 4.15.0-36.39 2018-10-10 10:45:05 status half-installed linux-cloud-tools-common:all 4.15.0-36.39 2018-10-10 10:45:05 status half-installed linux-cloud-tools-common:all 4.15.0-36.39 -- 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/1796376 Title: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode Status in linux package in Ubuntu: Confirmed Bug description: Since the following linux-cloud-tools-common package versions : Xenial : 4.4.0-135.161 Bionic : 4.15.0-34.37 the Systemd service unit file for hv-kvp-daemon has been modified with new dependencies that make the package unable to be upgraded with unattended-upgrades on shutdown mode. Unattended-upgrades hangs with the linux-cloud-tools-common package during "Preparing to unpack". The server restarts after the unattended-upgrades service timeout expires. - Package state after reboot : iFR linux-cloud-tools-common 4.15.0-34.37 all Linux kernel version specific cloud tools for version 4.15.0 - Unattended-upgrades dpkg logs : Log started: 2018-10-05 17:59:04 (Reading database ... 52043 files and directories currently installed.) Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ... Log ended: 2018-10-05 18:00:54 - Impact : The current impact is very important as all security updates are blocked until you manually fix each server with : dpkg --configure -a apt install --only-upgrade linux-cloud-tools-common - Workaround/Fix : As a simple straightforward fix, replacing : Before=shutdown.target cloud-init-local.service walinuxagent.service with : Before=shutdown.target walinuxagent.service makes the package upgradable during shutdown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic
I built the next test kernel, up to the following commit: cc2180a5880d0fd8491182cdc65e8df9696a7c9e The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1788997 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results. Thanks in advance -- 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/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1234 F pulseaudio /dev/snd/controlC0: al 1234 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Notebook Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8137 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.02 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode
@Eric : Sosreport sent by email. Did you try the second time (with cloud-init installed) to reproduce with unattended upgrades on shutdown mode ? I did not mention it but upgrading the package outside of unattended upgrades on shutdown mode 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/1796376 Title: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode Status in linux package in Ubuntu: Confirmed Bug description: Since the following linux-cloud-tools-common package versions : Xenial : 4.4.0-135.161 Bionic : 4.15.0-34.37 the Systemd service unit file for hv-kvp-daemon has been modified with new dependencies that make the package unable to be upgraded with unattended-upgrades on shutdown mode. Unattended-upgrades hangs with the linux-cloud-tools-common package during "Preparing to unpack". The server restarts after the unattended-upgrades service timeout expires. - Package state after reboot : iFR linux-cloud-tools-common 4.15.0-34.37 all Linux kernel version specific cloud tools for version 4.15.0 - Unattended-upgrades dpkg logs : Log started: 2018-10-05 17:59:04 (Reading database ... 52043 files and directories currently installed.) Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ... Log ended: 2018-10-05 18:00:54 - Impact : The current impact is very important as all security updates are blocked until you manually fix each server with : dpkg --configure -a apt install --only-upgrade linux-cloud-tools-common - Workaround/Fix : As a simple straightforward fix, replacing : Before=shutdown.target cloud-init-local.service walinuxagent.service with : Before=shutdown.target walinuxagent.service makes the package upgradable during shutdown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730836] Re: [Feature] Optimize huge page clear/copy cache behavior
This bug was fixed in the package linux - 4.18.0-9.10
---
linux (4.18.0-9.10) cosmic; urgency=medium
* linux: 4.18.0-9.10 -proposed tracker (LP: #1796346)
* Cosmic update: v4.18.12 upstream stable release (LP: #1796139)
- crypto: skcipher - Fix -Wstringop-truncation warnings
- iio: adc: ina2xx: avoid kthread_stop() with stale task_struct
- tsl2550: fix lux1_input error in low light
- misc: ibmvmc: Use GFP_ATOMIC under spin lock
- vmci: type promotion bug in qp_host_get_user_memory()
- siox: don't create a thread without starting it
- x86/numa_emulation: Fix emulated-to-physical node mapping
- staging: rts5208: fix missing error check on call to rtsx_write_register
- power: supply: axp288_charger: Fix initial constant_charge_current value
- misc: sram: enable clock before registering regions
- serial: sh-sci: Stop RX FIFO timer during port shutdown
- uwb: hwa-rc: fix memory leak at probe
- power: vexpress: fix corruption in notifier registration
- iommu/amd: make sure TLB to be flushed before IOVA freed
- Bluetooth: Add a new Realtek 8723DE ID 0bda:b009
- USB: serial: kobil_sct: fix modem-status error handling
- 6lowpan: iphc: reset mac_header after decompress to fix panic
- iommu/msm: Don't call iommu_device_{,un}link from atomic context
- s390/mm: correct allocate_pgste proc_handler callback
- power: remove possible deadlock when unregistering power_supply
- drm/amd/display/dc/dce: Fix multiple potential integer overflows
- drm/amd/display: fix use of uninitialized memory
- md-cluster: clear another node's suspend_area after the copy is finished
- cxgb4: Fix the condition to check if the card is T5
- RDMA/bnxt_re: Fix a couple off by one bugs
- RDMA/i40w: Hold read semaphore while looking after VMA
- RDMA/bnxt_re: Fix a bunch of off by one bugs in qplib_fp.c
- IB/core: type promotion bug in rdma_rw_init_one_mr()
- media: exynos4-is: Prevent NULL pointer dereference in
__isp_video_try_fmt()
- IB/mlx4: Test port number before querying type.
- powerpc/kdump: Handle crashkernel memory reservation failure
- media: fsl-viu: fix error handling in viu_of_probe()
- vhost_net: Avoid tx vring kicks during busyloop
- media: staging/imx: fill vb2_v4l2_buffer field entry
- IB/mlx5: Fix GRE flow specification
- include/rdma/opa_addr.h: Fix an endianness issue
- x86/tsc: Add missing header to tsc_msr.c
- ARM: hwmod: RTC: Don't assume lock/unlock will be called with irq enabled
- x86/entry/64: Add two more instruction suffixes
- ARM: dts: ls1021a: Add missing cooling device properties for CPUs
- scsi: target/iscsi: Make iscsit_ta_authentication() respect the output
buffer size
- thermal: i.MX: Allow thermal probe to fail gracefully in case of bad
calibration.
- scsi: klist: Make it safe to use klists in atomic context
- scsi: ibmvscsi: Improve strings handling
- scsi: target: Avoid that EXTENDED COPY commands trigger lock inversion
- usb: wusbcore: security: cast sizeof to int for comparison
- ath10k: sdio: use same endpoint id for all packets in a bundle
- ath10k: sdio: set skb len for all rx packets
- powerpc/powernv/ioda2: Reduce upper limit for DMA window size
- platform/x86: asus-wireless: Fix uninitialized symbol usage
- ACPI / button: increment wakeup count only when notified
- s390/sysinfo: add missing #ifdef CONFIG_PROC_FS
- alarmtimer: Prevent overflow for relative nanosleep
- s390/dasd: correct numa_node in dasd_alloc_queue
- s390/scm_blk: correct numa_node in scm_blk_dev_setup
- s390/extmem: fix gcc 8 stringop-overflow warning
- mtd: rawnand: atmel: add module param to avoid using dma
- iio: accel: adxl345: convert address field usage in iio_chan_spec
- posix-timers: Make forward callback return s64
- posix-timers: Sanitize overrun handling
- ALSA: snd-aoa: add of_node_put() in error path
- selftests: forwarding: Tweak tc filters for mirror-to-gretap tests
- ath10k: use locked skb_dequeue for rx completions
- media: s3c-camif: ignore -ENOIOCTLCMD from v4l2_subdev_call for s_power
- media: soc_camera: ov772x: correct setting of banding filter
- media: omap3isp: zero-initialize the isp cam_xclk{a,b} initial data
- media: ov772x: add checks for register read errors
- staging: android: ashmem: Fix mmap size validation
- media: ov772x: allow i2c controllers without I2C_FUNC_PROTOCOL_MANGLING
- staging: mt7621-eth: Fix memory leak in mtk_add_mac() error path
- drivers/tty: add error handling for pcmcia_loop_config
- arm64: dts: renesas: salvator-common: Fix adv7482 decimal unit addresses
- serial: pxa: Fix an error handling path in 'serial_pxa_probe()'
- staging: mt7621-dts: Fix remaining pcie warnings
- media: tm6000: add error handling for dvb_register_adapter
- ASoC: qdsp6: qdafe:
[Kernel-packages] [Bug 1797062] Re: linux-gcp: 4.15.0-1023.24 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1797062 Title: linux-gcp: 4.15.0-1023.24 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-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 -- boot-testing-requested: true kernel-stable-master-bug: 1797061 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797061] Re: linux: 4.15.0-38.41 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797061 Title: linux: 4.15.0-38.41 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in 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 1797074 (linux-azure), bug 1797076 (linux-hwe), bug 1797078 (linux-azure-edge), bug 1797080 (linux-gcp), bug 1797081 (linux-hwe-edge), bug 1797082 (linux-azure) derivatives: bug 1797062 (linux-gcp), bug 1797065 (linux-kvm), bug 1797066 (linux-aws), bug 1797067 (linux-azure), bug 1797069 (linux-oem), bug 1797073 (linux-raspi2) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797061/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode
Can you run sosreport from an impacted system ? It may provide more context. -- 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/1796376 Title: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode Status in linux package in Ubuntu: Confirmed Bug description: Since the following linux-cloud-tools-common package versions : Xenial : 4.4.0-135.161 Bionic : 4.15.0-34.37 the Systemd service unit file for hv-kvp-daemon has been modified with new dependencies that make the package unable to be upgraded with unattended-upgrades on shutdown mode. Unattended-upgrades hangs with the linux-cloud-tools-common package during "Preparing to unpack". The server restarts after the unattended-upgrades service timeout expires. - Package state after reboot : iFR linux-cloud-tools-common 4.15.0-34.37 all Linux kernel version specific cloud tools for version 4.15.0 - Unattended-upgrades dpkg logs : Log started: 2018-10-05 17:59:04 (Reading database ... 52043 files and directories currently installed.) Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ... Log ended: 2018-10-05 18:00:54 - Impact : The current impact is very important as all security updates are blocked until you manually fix each server with : dpkg --configure -a apt install --only-upgrade linux-cloud-tools-common - Workaround/Fix : As a simple straightforward fix, replacing : Before=shutdown.target cloud-init-local.service walinuxagent.service with : Before=shutdown.target walinuxagent.service makes the package upgradable during shutdown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797066] Re: linux-aws: 4.15.0-1025.25 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1797066 Title: linux-aws: 4.15.0-1025.25 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in 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 -- boot-testing-requested: true kernel-stable-master-bug: 1797061 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797066/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
