[Kernel-packages] [Bug 1625912] Re: Kernel option usbhid.mousepoll=1 is now ignored
Looks like this may be related: https://bugzilla.kernel.org/show_bug.cgi?id=60586 ** Bug watch added: Linux Kernel Bug Tracker #60586 https://bugzilla.kernel.org/show_bug.cgi?id=60586 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1625912 Title: Kernel option usbhid.mousepoll=1 is now ignored Status in linux package in Ubuntu: Confirmed Bug description: Kernel option usbhid.mousepoll=1 is now ignored. I can see in /proc/cmdline that I still have usbhid.mousepoll=1 but in real testing with Mir clients I'm only getting 125Hz input instead of the expected 1000Hz. Just a few months ago at least it was working (with the same mouse but different PC). ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.4.0-9136-generic 4.4.0-9136.55 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC1D2', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Sep 21 11:59:24 2016 HibernationDevice: RESUME=UUID=14362a37-9d65-44cb-af81-5694ee7c17c1 InstallationDate: Installed on 2016-07-11 (72 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160710) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: LENOVO 30AJS05700 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic.efi.signed root=UUID=81044886-888d-4a06-893c-d740f91759e0 ro quiet splash usbhid.mousepoll=1 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-9136-generic N/A linux-backports-modules-4.4.0-9136-generic N/A linux-firmware 1.161 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2015 dmi.bios.vendor: LENOVO dmi.bios.version: FBKTB6AUS dmi.board.name: SHARKBAY dmi.board.vendor: LENOVO dmi.board.version: SDK0E50519 PRO dmi.chassis.type: 7 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvrFBKTB6AUS:bd08/02/2015:svnLENOVO:pn30AJS05700:pvrThinkStationP300:rvnLENOVO:rnSHARKBAY:rvrSDK0E50519PRO:cvnToBeFilledByO.E.M.:ct7:cvrToBeFilledByO.E.M.: dmi.product.name: 30AJS05700 dmi.product.version: ThinkStation P300 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625912/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782478] Re: linux: 4.15.0-30.32 -proposed tracker
** Summary changed: - linux: 4.15.0-29.31 -proposed tracker + linux: 4.15.0-30.32 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Released => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Stefan Bader (smb) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Stefan Bader (smb) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Released => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Stefan Bader (smb) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782478 Title: linux: 4.15.0-30.32 -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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: 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: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in 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 1782487 (linux-azure), bug 1782488 (linux-azure-edge), bug 1782490 (linux-gcp), bug 1782492 (linux-hwe), bug 1782493 (linux-hwe-edge) derivatives: bug 1782480 (linux-raspi2), bug 1782482 (linux-oem), bug 1782483 (linux-aws), bug 1782484 (linux-azure), bug 1782485 (linux-gcp), bug 1782486 (linux-kvm) kernel-stable-phase-changed:Thursday, 19. July 2018 23:34 UTC kernel-stable-phase:Promoted to proposed -- swm properties -- 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/1782478/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1777194] Comment bridged from LTC Bugzilla
--- Comment From hasri...@in.ibm.com 2018-07-20 01:38 EDT--- (In reply to comment #42) > I built a .deb version of the kernel that is currently in -proposed. > The test kernel can be downloaded from: > http://kernel.ubuntu.com/~jsalisbury/lp1777194 > > Can you test this kernel and see if it resolves this bug? I am seeing the following LOCKUP on the above kernel. # uname -a Linux lep8d 4.15.0-29-generic #32~lp1777194 SMP Thu Jul 19 16:21:31 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux [ 349.854120] Watchdog CPU:16 Hard LOCKUP [ 349.854129] Modules linked in: userio(E) serpent_generic(E) hci_vhci(E) bluetooth(E) ecdh_generic(E) twofish_generic(E) twofish_common(E) cuse(E) vhost_vsock(E) vmw_vsock_virtio_transport_common(E) vsock(E) lrw(E) uhid(E) hid(E) algif_skcipher(E) tgr192(E) wp512(E) rmd320(E) snd_seq(E) snd_seq_device(E) unix_diag(E) snd_timer(E) sctp(E) rmd256(E) snd(E) soundcore(E) rmd160(E) rmd128(E) md4(E) vhost_net(E) vhost(E) tap(E) algif_hash(E) dccp_ipv4(E) dccp(E) af_alg(E) xt_CHECKSUM(E) iptable_mangle(E) ipt_MASQUERADE(E) nf_nat_masquerade_ipv4(E) iptable_nat(E) nf_nat_ipv4(E) nf_nat(E) nf_conntrack_ipv4(E) nf_defrag_ipv4(E) xt_conntrack(E) nf_conntrack(E) libcrc32c(E) ipt_REJECT(E) nf_reject_ipv4(E) xt_tcpudp(E) bridge(E) stp(E) llc(E) ebtable_filter(E) ebtables(E) devlink(E) ip6table_filter(E) ip6_tables(E) [ 349.854595] iptable_filter(E) kvm_hv(E) kvm(E) binfmt_misc(E) dm_multipath(E) scsi_dh_rdac(E) scsi_dh_emc(E) scsi_dh_alua(E) uio_pdrv_genirq(E) uio(E) ipmi_powernv(E) ipmi_devintf(E) ipmi_msghandler(E) vmx_crypto(E) powernv_rng(E) powernv_op_panel(E) ibmpowernv(E) leds_powernv(E) crct10dif_vpmsum(E) nfsd(E) sch_fq_codel(E) auth_rpcgss(E) nfs_acl(E) lockd(E) grace(E) sunrpc(E) ip_tables(E) x_tables(E) autofs4(E) ses(E) enclosure(E) scsi_transport_sas(E) btrfs(E) xor(E) zstd_compress(E) raid6_pq(E) uas(E) usb_storage(E) crc32c_vpmsum(E) tg3(E) ipr(E) [ 349.854940] CPU: 16 PID: 1634 Comm: ureadahead Tainted: GE 4.15.0-29-generic #32~lp1777194 [ 349.854949] NIP: c029738c LR: c0297430 CTR: c00aa8a0 [ 349.854961] REGS: c7ee3d80 TRAP: 0900 Tainted: GE (4.15.0-29-generic) [ 349.854993] MSR: 90009033 CR: 28002848 XER: [ 349.855081] CFAR: c029742c SOFTE: 0 GPR00: c0297430 c0213cc0 c16eaf00 c00fff924360 GPR04: 0010 c00fff924360 c171dd78 b000 GPR08: c1721ee0 0003 c00ff9004928 GPR12: c00aa8a0 c7a2b000 0001 GPR16: 0024 0e8aa6080160 0014 GPR20: 0040 c00fa02a c00fa02a01d0 0001 GPR24: 0002 0010 c02ff3171800 c0213ef0 GPR28: fff8 0002 0003 c00ffa110450 [ 349.855354] NIP [c029738c] irq_work_run_list+0x8c/0x100 [ 349.855373] LR [c0297430] irq_work_run+0x30/0x60 [ 349.855384] Call Trace: [ 349.855400] [c0213cc0] [c02973b0] irq_work_run_list+0xb0/0x100 (unreliable) [ 349.855415] [c0213d00] [c0297430] irq_work_run+0x30/0x60 [ 349.855432] [c0213d30] [c01d7268] flush_smp_call_function_queue+0xd8/0x1d0 [ 349.855439] [c0213db0] [c004923c] smp_ipi_demux_relaxed+0x9c/0x110 [ 349.855445] [c0213df0] [c0098be4] icp_native_ipi_action+0x64/0x80 [ 349.855468] [c0213e10] [c0192440] __handle_irq_event_percpu+0x90/0x300 [ 349.855487] [c0213ed0] [c01926e8] handle_irq_event_percpu+0x38/0x90 [ 349.855510] [c0213f10] [c0198f74] handle_percpu_irq+0x84/0xd0 [ 349.855527] [c0213f40] [c0190b0c] generic_handle_irq+0x4c/0x70 [ 349.855549] [c0213f60] [c001787c] __do_irq+0x7c/0x1c0 [ 349.855569] [c0213f90] [c002a090] call_do_irq+0x14/0x24 [ 349.855575] [c4e4b7a0] [c0017a5c] do_IRQ+0x9c/0x130 [ 349.855582] [c4e4b7f0] [c0008c24] hardware_interrupt_common+0x114/0x120 [ 349.855588] --- interrupt: 501 at replay_interrupt_return+0x0/0x4 LR = arch_local_irq_restore+0x74/0x90 [ 349.855593] [c4e4bae0] [c00fa028] 0xc00fa028 (unreliable) [ 349.855599] [c4e4bb00] [c024b158] ring_buffer_empty_cpu+0xa8/0x150 [ 349.855612] [c4e4bb40] [c024e560] __find_next_entry+0xe0/0x260 [ 349.855617] [c4e4bbe0] [c0257704] trace_find_next_entry_inc+0x34/0xd0 [ 349.855622] [c4e4bc10] [c0257818] s_next+0x78/0x100 [ 349.855626] [c4e4bc50] [c02582c0] s_start+0x180/0x350 [ 349.855643] [c4e4bcd0] [c040ef1c] seq_read+0xfc/0x610 [ 349.855654] [c4e4bd70] [c03d509c] __vfs_read+0x3c/0x70 [ 349.855657] [c4e4bd90] [c03d518c]
[Kernel-packages] [Bug 1771733] Re: bluetooth device disappears after several minutes of use
[Expired for Ubuntu Budgie because there has been no activity for 60 days.] ** Changed in: ubuntubudgie Status: Incomplete => Expired -- 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/1771733 Title: bluetooth device disappears after several minutes of use Status in Ubuntu Budgie: Expired Status in bluez package in Ubuntu: Expired Bug description: I am using budgie-desktop 10.4 on ubuntu budgie 18.04, fully up-to- date. When I open bluetooth settings, I am able to see many different bluetooth devices detected by my computer, and I can connect to my bluetooth mouse (Microsoft sculpt comfort mouse). However, after several minutes of use, I find that my mouse has disconnected, and I no longer have a bluetooth icon in the top right status indicator. Then, when I open bluetooth settings, the window reads "No bluetooth found: Plug in a dongle to use bluetooth." My laptop has bluetooth built in. It's an Asus UX305CA. This is my first bug report so please let me know if I've left out any important details and I will provide them as soon as possible. Thanks for all your hard work with Ubuntu Budgie! --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-15 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 064e:9700 Suyin Corp. Asus Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX305CA Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX305CA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX305CA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX305CA.300:bd06/08/2016:svnASUSTeKCOMPUTERINC.:pnUX305CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX305CA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0:Type: Primary Bus: USB BD Address: 4C:34:88:A3:4C:6E ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:1186983 acl:12228 sco:0 events:120531 errors:0 TX bytes:99607321 acl:116734 sco:0 commands:1078 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntubudgie/+bug/1771733/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771733] Re: bluetooth device disappears after several minutes of use
[Expired for bluez (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bluez (Ubuntu) Status: Incomplete => Expired -- 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/1771733 Title: bluetooth device disappears after several minutes of use Status in Ubuntu Budgie: Expired Status in bluez package in Ubuntu: Expired Bug description: I am using budgie-desktop 10.4 on ubuntu budgie 18.04, fully up-to- date. When I open bluetooth settings, I am able to see many different bluetooth devices detected by my computer, and I can connect to my bluetooth mouse (Microsoft sculpt comfort mouse). However, after several minutes of use, I find that my mouse has disconnected, and I no longer have a bluetooth icon in the top right status indicator. Then, when I open bluetooth settings, the window reads "No bluetooth found: Plug in a dongle to use bluetooth." My laptop has bluetooth built in. It's an Asus UX305CA. This is my first bug report so please let me know if I've left out any important details and I will provide them as soon as possible. Thanks for all your hard work with Ubuntu Budgie! --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-15 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 064e:9700 Suyin Corp. Asus Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX305CA Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX305CA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX305CA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX305CA.300:bd06/08/2016:svnASUSTeKCOMPUTERINC.:pnUX305CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX305CA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0:Type: Primary Bus: USB BD Address: 4C:34:88:A3:4C:6E ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:1186983 acl:12228 sco:0 events:120531 errors:0 TX bytes:99607321 acl:116734 sco:0 commands:1078 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntubudgie/+bug/1771733/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782689] 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 1782689 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/1782689 Title: HDMI/DP audio can't work on the laptop of Dell Latitude 5495 Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: Steps: 1. Install manifest and boot into OS 2. Connect an external monitor via HDMI port 3. Check sound setting Expected results: System should able to detect HDMI audio output Actual results: System can't detect HDMI audio output Failure rate: 2/2 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1782689/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782689] [NEW] HDMI/DP audio can't work on the laptop of Dell Latitude 5495
Public bug reported: Steps: 1. Install manifest and boot into OS 2. Connect an external monitor via HDMI port 3. Check sound setting Expected results: System should able to detect HDMI audio output Actual results: System can't detect HDMI audio output Failure rate: 2/2 ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Critical Assignee: Hui Wang (hui.wang) Status: New ** Tags: originate-from-1775331 somerville ** Tags added: originate-from-1775331 somerville ** Changed in: linux (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782689 Title: HDMI/DP audio can't work on the laptop of Dell Latitude 5495 Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: Steps: 1. Install manifest and boot into OS 2. Connect an external monitor via HDMI port 3. Check sound setting Expected results: System should able to detect HDMI audio output Actual results: System can't detect HDMI audio output Failure rate: 2/2 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1782689/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781328] Re: package linux-image-4.15.0-24-generic (not installed) failed to install/upgrade: installed linux-image-4.15.0-24-generic package pre-removal script subprocess retur
Just ran the commands, then updated and rebooted and have not seen the error again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781328 Title: package linux-image-4.15.0-24-generic (not installed) failed to install/upgrade: installed linux-image-4.15.0-24-generic package pre- removal script subprocess returned error exit status 1 Status in linux package in Ubuntu: Incomplete Bug description: It happens after boot when I open terminal. Not sure if that's related. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-24-generic (not installed) ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_23_25_generic_40 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1251 F pulseaudio jed1802 F pulseaudio /dev/snd/controlC0: gdm1251 F pulseaudio jed1802 F pulseaudio Date: Wed Jul 11 22:50:18 2018 ErrorMessage: installed linux-image-4.15.0-24-generic package pre-removal script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=b9e3143f-9a78-4568-9795-e29691c48cdd InstallationDate: Installed on 2018-04-26 (77 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. Dell Precision M3800 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=/dev/mapper/ubuntu--vg-root 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.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: grub-pc 2.02-2ubuntu8.1 SourcePackage: linux Title: package linux-image-4.15.0-24-generic (not installed) failed to install/upgrade: installed linux-image-4.15.0-24-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: Dell Precision M3800 dmi.board.vendor: Dell Inc. dmi.board.version: A10 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/17/2015:svnDellInc.:pnDellPrecisionM3800:pvrA10:rvnDellInc.:rnDellPrecisionM3800:rvrA10:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Dell Precision M3800 dmi.product.version: A10 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781328/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781533] Re: SATA device is not going to DEVSLP
The third patch split into 2 new commits https://patchwork.kernel.org/patch/10535781/ https://patchwork.kernel.org/patch/10535783/ -- 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/1781533 Title: SATA device is not going to DEVSLP Status in HWE Next: In Progress Status in OEM Priority Project: Triaged Status in linux-oem package in Ubuntu: In Progress Bug description: [Impact] Any of the platforms we’ve been seeing SATA problems not going to deepest state leading to other devices not getting there during long idle or s2idle. And it also prevents the system from entering deeper PC state other than PC3. [Test] Verified the power consumption on some new platforms, it doesn't do too much difference to the numbers, but it improves. [Fix] Suggested from Intel and Dell to contains the 2 commits https://patchwork.kernel.org/patch/10502285/ https://patchwork.kernel.org/patch/10502287/ [Regression Potential] Low, the production machines with suspend-to-idle enabled should have the DEVSLP function been validated. [Misc] Those commits do not show up in any public git tree yet, so let's verify them in oem kernel first, and then will submit to bionic kernel later. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1781533/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1745492] Re: Backport of Debian bug #785714 for Xenial to avoid unclean reboots
I believe this is solved by bug #1743529 backporting kexec-tools from bionic. What's the right way to close this? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1745492 Title: Backport of Debian bug #785714 for Xenial to avoid unclean reboots Status in kexec-tools package in Ubuntu: New Status in kexec-tools source package in Xenial: New Status in kexec-tools package in Debian: Fix Released Bug description: Debian bug #785714 is a fairly substantial one, as it causes unclean shutdowns. In our case, KVM hosts with many guests will begin to partially shutdown a couple before kexec jumps the gun and reboots the machine. Without this fix, kexec is of only minimal use on Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1745492/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781016] Re: Slow flood of do_IRQ: No irq for vector
Still happening: doug@doug-dt:~$ uname -a Linux doug-dt 4.18.0-041800rc5-generic #201807152130 SMP Sun Jul 15 21:32:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux doug@doug-dt:~$ dmesg | tail [ 169.701341] usb 1-4: Warning! Unlikely big volume range (=4096), cval->res is probably wrong. [ 169.701344] usb 1-4: [11] FU [Headset Playback Volume] ch = 1, val = 0/4096/1 [ 169.755604] usbcore: registered new interface driver snd-usb-audio [ 2603.508893] do_IRQ: 15.38 No irq handler for vector [ 2611.510716] do_IRQ: 15.38 No irq handler for vector [ 2624.514513] do_IRQ: 15.38 No irq handler for vector [ 2627.515471] do_IRQ: 15.38 No irq handler for vector [ 2642.520161] do_IRQ: 15.38 No irq handler for vector [ 2644.520907] do_IRQ: 15.38 No irq handler for vector [ 2647.522088] do_IRQ: 15.38 No irq handler for vector doug@doug-dt:~$ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781016 Title: Slow flood of do_IRQ: No irq for vector Status in linux package in Ubuntu: Incomplete Bug description: Every few seconds I get something like this in my dmesg: [44984.933221] do_IRQ: 1.34 No irq handler for vector [44986.933976] do_IRQ: 1.34 No irq handler for vector [44991.935614] do_IRQ: 1.34 No irq handler for vector [45004.938590] do_IRQ: 1.34 No irq handler for vector [45005.939002] do_IRQ: 4.34 No irq handler for vector [45034.949161] do_IRQ: 4.34 No irq handler for vector [45051.954569] do_IRQ: 4.34 No irq handler for vector [45058.956019] do_IRQ: 4.34 No irq handler for vector [45062.957727] do_IRQ: 4.34 No irq handler for vector [45063.958204] do_IRQ: 4.34 No irq handler for vector [45073.961103] do_IRQ: 4.34 No irq handler for vector The numbers vary. Some examples are 4.34, 4.36, 1.34, 0.33, 6.34, 7.33, 5.37. Eventually dmesg's ring buffer is full and my entire log is just messages like above with varying #.## numbers. I researched it and tried disabling irqbalance. It had no effect, the messages continued. The system is a Ryzen 2700X with B350 chipset on Asus Prime B350-PLUS. I have 64GB of Kingston DDR4-2400 ECC memory and Samsung 960 PRO M.2 NVMe SSD, and an Intel I350-T4 quad port gigabit NIC. This issue never occurred before installing 18.03 on the same hardware. No overclocking whatsoever has ever been done to this machine. Also, I had to disable selective suspend on USB in this version to prevent major USB issues, which was not required in 17.10, that might be related. My system seems stable, but spurious IRQs can't be good. I'd like to resolve this if possible. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-26-generic 4.15.0-26.28 ProcVersionSignature: Ubuntu 4.15.0-26.28-generic 4.15.18 Uname: Linux 4.15.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2145 F pulseaudio doug 3736 F pulseaudio /dev/snd/controlC1: gdm2145 F pulseaudio doug 3736 F pulseaudio Date: Tue Jul 10 12:49:00 2018 HibernationDevice: InstallationDate: Installed on 2017-06-26 (379 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-26-generic root=UUID=53446747-0814-48f7-b7c4-7fd7d7234d83 ro video=vesa:off vga=normal video=efifb:off usbcore.autosuspend=-1 usbhid.quirks=0x1e71:0x170e:0x4 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-26-generic N/A linux-backports-modules-4.15.0-26-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4011 dmi.board.asset.tag: Default string dmi.board.name: PRIME B350-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4011:bd04/19/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M.
[Kernel-packages] [Bug 1782645] Re: nvidia-384 384.130-0ubuntu0.14.04.1: nvidia-384 kernel module failed to build [cc: error: unrecognized command line option ‘-fstack-protector-strong’]
*** This bug is a duplicate of bug 1526155 *** https://bugs.launchpad.net/bugs/1526155 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1526155, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Summary changed: - nvidia-384 384.130-0ubuntu0.14.04.1: nvidia-384 kernel module failed to build + nvidia-384 384.130-0ubuntu0.14.04.1: nvidia-384 kernel module failed to build [cc: error: unrecognized command line option ‘-fstack-protector-strong’] ** This bug has been marked a duplicate of bug 1526155 nvidia-* kernel module failed to build [cc: error: unrecognized command line option ‘-fstack-protector-strong’] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-384 in Ubuntu. https://bugs.launchpad.net/bugs/1782645 Title: nvidia-384 384.130-0ubuntu0.14.04.1: nvidia-384 kernel module failed to build [cc: error: unrecognized command line option ‘-fstack- protector-strong’] Status in nvidia-graphics-drivers-384 package in Ubuntu: New Bug description: I get system error screen on booting. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-384 384.130-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 DKMSKernelVersion: 4.4.0-108-generic Date: Thu Jul 19 23:54:45 2018 DuplicateSignature: dkms:nvidia-384:384.130-0ubuntu0.14.04.1:cc: error: unrecognized command line option ‘-fstack-protector-strong’ InstallationDate: Installed on 2018-01-04 (196 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) PackageVersion: 384.130-0ubuntu0.14.04.1 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: nvidia-graphics-drivers-384 Title: nvidia-384 384.130-0ubuntu0.14.04.1: nvidia-384 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-384/+bug/1782645/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779817] Re: no internet after suspending
I'm in the same situation as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817/comments/12 Same Ethernet model, using kubuntu 18.04 after the kernel update 4.15.0-24, If I boot into 4.15.0-23 it works. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1779817 Title: no internet after suspending Status in linux package in Ubuntu: Confirmed Bug description: When my computer wakes up from suspending, there's no internet. Unplugging and replugging cable doesn't work, restarting network service doesn't work also. Only after restarting the computer, internet comes back. It only started happening after I freshly installed Ubuntu Budgie (18.04) and did all the system updates. Before I was using Ubuntu with Unity (16.04) and there was no problems with my internet. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-24-generic 4.15.0-24.26 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: minihydra 2085 F pulseaudio /dev/snd/controlC0: minihydra 2085 F pulseaudio /dev/snd/controlC1: minihydra 2085 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Jul 3 10:13:19 2018 HibernationDevice: RESUME=UUID=3747bab8-c258-4600-bc24-5d1f56a642dd InstallationDate: Installed on 2018-07-02 (1 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=a5ceb36e-76f7-4bd4-a37b-0b91b995c635 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A77T dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd06/28/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A77T:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted
The 100+ just means a lot of people made the same mistake, which is understandable. See comment #48. I asked over a year ago for someone to open a new bug if they want to discuss "Not enough free handles to register service". If it was important to anyone then I'm sure someone would have done it by now. -- 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/1490349 Title: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted Status in bluez package in Ubuntu: Invalid Bug description: On 15:10 after the bluetooth service has been stopped and restarted it is not possible to scan or connect to devices: $ sudo systemctl restart bluetooth $ bluetoothctl [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default] [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782347] Re: [radeon] GDM3 fails to load without nomodeset
Please edit your /etc/gdm3/custom.conf and comment out: WaylandEnable=false Now you should be able to boot without 'nomodeset'...? ** Changed in: gdm3 (Ubuntu) Status: Confirmed => Incomplete ** 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/1782347 Title: [radeon] GDM3 fails to load without nomodeset Status in gdm3 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Both with the livecd (usb drive) and the installed version, I must boot with the 'nomodeset' kernel parameter at GRUB; otherwise GDM3 will not boot (the screen will keep on flashing in semi-textual mode, with a white mouse arrow stuck). This, however, prevents me from using the 'radeon' video driver, dropping me to a very basic 1024x768 vesa mode. The bug did NOT occur on Ubuntu 12.04, so it is a regression. Also, the bug does NOT occur on XUbuntu/XFCE 18.04, so it is a GDM3-Gnome related thing. Thanks, MZ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 18 12:18:06 2018 LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2018-07-18T12:14:53.871895 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: linux PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2018-07-19T11:39:06.027905 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782347/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782478] Re: linux: 4.15.0-29.31 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff 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/1782478 Title: linux: 4.15.0-29.31 -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: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in 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 1782487 (linux-azure), bug 1782488 (linux-azure-edge), bug 1782490 (linux-gcp), bug 1782492 (linux-hwe), bug 1782493 (linux-hwe-edge) derivatives: bug 1782480 (linux-raspi2), bug 1782482 (linux-oem), bug 1782483 (linux-aws), bug 1782484 (linux-azure), bug 1782485 (linux-gcp), bug 1782486 (linux-kvm) kernel-stable-phase-changed:Thursday, 19. July 2018 23:34 UTC kernel-stable-phase:Promoted to proposed -- swm properties -- 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/1782478/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782478] Re: linux: 4.15.0-29.31 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782478 Title: linux: 4.15.0-29.31 -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-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in 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 1782487 (linux-azure), bug 1782488 (linux-azure-edge), bug 1782490 (linux-gcp), bug 1782492 (linux-hwe), bug 1782493 (linux-hwe-edge) derivatives: bug 1782480 (linux-raspi2), bug 1782482 (linux-oem), bug 1782483 (linux-aws), bug 1782484 (linux-azure), bug 1782485 (linux-gcp), bug 1782486 (linux-kvm) kernel-stable-phase-changed:Thursday, 19. July 2018 23:34 UTC kernel-stable-phase:Promoted to proposed -- swm properties -- 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/1782478/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782478] Re: linux: 4.15.0-29.31 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package Assignee: Khaled El Mously (kmously) => Stefan Bader (smb) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Khaled El Mously (kmously) => Stefan Bader (smb) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Khaled El Mously (kmously) => Stefan Bader (smb) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Fix Committed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1782487 (linux-azure), bug 1782488 (linux-azure-edge), bug 1782490 (linux-gcp), bug 1782492 (linux-hwe), bug 1782493 (linux-hwe-edge) derivatives: bug 1782480 (linux-raspi2), bug 1782482 (linux-oem), bug 1782483 (linux-aws), bug 1782484 (linux-azure), bug 1782485 (linux-gcp), bug 1782486 (linux-kvm) + kernel-stable-phase-changed:Thursday, 19. July 2018 23:34 UTC + kernel-stable-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: bug 1782487 (linux-azure), bug 1782488 (linux-azure-edge), bug 1782490 (linux-gcp), bug 1782492 (linux-hwe), bug 1782493 (linux-hwe-edge) derivatives: bug 1782480 (linux-raspi2), bug 1782482 (linux-oem), bug 1782483 (linux-aws), bug 1782484 (linux-azure), bug 1782485 (linux-gcp), bug 1782486 (linux-kvm) kernel-stable-phase-changed:Thursday, 19. July 2018 23:34 UTC kernel-stable-phase:Promoted to proposed + + -- swm properties -- + bugs-spammed: true + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782478 Title: linux: 4.15.0-29.31 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in 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:
[Kernel-packages] [Bug 1782482] Re: linux-oem: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1782478 + kernel-stable-phase-changed:Thursday, 19. July 2018 23:34 UTC + kernel-stable-phase:Packaging ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1782478 - kernel-stable-phase-changed:Thursday, 19. July 2018 23:34 UTC - kernel-stable-phase:Packaging + phase: Packaging -- 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/1782482 Title: linux-oem: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1782478 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1782482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782478] Re: linux: 4.15.0-29.31 -proposed tracker
** Summary changed: - linux: 4.15.0-30.32 -proposed tracker + linux: 4.15.0-29.31 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782478 Title: linux: 4.15.0-29.31 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in 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 1782487 (linux-azure), bug 1782488 (linux-azure-edge), bug 1782490 (linux-gcp), bug 1782492 (linux-hwe), bug 1782493 (linux-hwe-edge) derivatives: bug 1782480 (linux-raspi2), bug 1782482 (linux-oem), bug 1782483 (linux-aws), bug 1782484 (linux-azure), bug 1782485 (linux-gcp), bug 1782486 (linux-kvm) To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1782478/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782186] Re: linux-azure: 4.15.0-1018.18~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1782173 phase: Uploaded + kernel-stable-phase-changed:Thursday, 19. July 2018 23:02 UTC + kernel-stable-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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1782173 - phase: Uploaded - kernel-stable-phase-changed:Thursday, 19. July 2018 23:02 UTC - kernel-stable-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-azure in Ubuntu. https://bugs.launchpad.net/bugs/1782186 Title: linux-azure: 4.15.0-1018.18~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug 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: 1782173 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/1782186/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782178] Re: linux-azure: 4.15.0-1018.18 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1782178 Title: linux-azure: 4.15.0-1018.18 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1782173 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1782178/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782653] Re: ELAN1200 touchpad not working at all with kernel 4.15+; Recognized as ITE 8910 keyboard
** Attachment added: "xinput.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782653/+attachment/5165421/+files/xinput.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782653 Title: ELAN1200 touchpad not working at all with kernel 4.15+; Recognized as ITE 8910 keyboard Status in linux package in Ubuntu: Confirmed Bug description: Laptop is an Asus-GL703GE Touchpad is an ELAN touchpad model 1200. (rev ?) This bug is relative to the Asus-GL703GE and any Asus laptop using the ELAN1200 touchpad that semms to be different from that Bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777679 (ASUS- GL503VD) cat /sys/bus/i2c/devices/i2c-ELAN1200\:00/modalias acpi:ELAN1200:PNP0C50: dmesg: [ 12.721751] i2c_hid i2c-ELAN1200:00: i2c-ELAN1200:00 supply vdd not found, using dummy regulator [ 12.723089] i2c_hid i2c-ELAN1200:00: Could not register for ELAN1200:00 interrupt, irq = 138, ret = -1 [ 12.723113] i2c_hid: probe of i2c-ELAN1200:00 failed with error -1 I tried Kernels 4.15.0-20-generic (Ubuntu 18.04), 4.17.2, 4.17.8, 4.18, all do not work I tried with additional libinput from xorg, did not work. the Kernel-Module hid-multitouch is loaded but touchpad does not work. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-19 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: linux (not installed) Tags: bionic Uname: Linux 4.17.2 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: 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/1782653/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782653] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1782653/+attachment/5165420/+files/ProcEnviron.txt ** 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/1782653 Title: ELAN1200 touchpad not working at all with kernel 4.15+; Recognized as ITE 8910 keyboard Status in linux package in Ubuntu: Confirmed Bug description: Laptop is an Asus-GL703GE Touchpad is an ELAN touchpad model 1200. (rev ?) This bug is relative to the Asus-GL703GE and any Asus laptop using the ELAN1200 touchpad that semms to be different from that Bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777679 (ASUS- GL503VD) cat /sys/bus/i2c/devices/i2c-ELAN1200\:00/modalias acpi:ELAN1200:PNP0C50: dmesg: [ 12.721751] i2c_hid i2c-ELAN1200:00: i2c-ELAN1200:00 supply vdd not found, using dummy regulator [ 12.723089] i2c_hid i2c-ELAN1200:00: Could not register for ELAN1200:00 interrupt, irq = 138, ret = -1 [ 12.723113] i2c_hid: probe of i2c-ELAN1200:00 failed with error -1 I tried Kernels 4.15.0-20-generic (Ubuntu 18.04), 4.17.2, 4.17.8, 4.18, all do not work I tried with additional libinput from xorg, did not work. the Kernel-Module hid-multitouch is loaded but touchpad does not work. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-19 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: linux (not installed) Tags: bionic Uname: Linux 4.17.2 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: 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/1782653/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782653] Re: ELAN1200 touchpad not working at all with kernel 4.15+; Recognized as ITE 8910 keyboard
apport information ** Tags added: apport-collected ** Description changed: Laptop is an Asus-GL703GE Touchpad is an ELAN touchpad model 1200. (rev ?) This bug is relative to the Asus-GL703GE and any Asus laptop using the ELAN1200 touchpad that semms to be different from that Bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777679 (ASUS- GL503VD) cat /sys/bus/i2c/devices/i2c-ELAN1200\:00/modalias acpi:ELAN1200:PNP0C50: dmesg: [ 12.721751] i2c_hid i2c-ELAN1200:00: i2c-ELAN1200:00 supply vdd not found, using dummy regulator [ 12.723089] i2c_hid i2c-ELAN1200:00: Could not register for ELAN1200:00 interrupt, irq = 138, ret = -1 [ 12.723113] i2c_hid: probe of i2c-ELAN1200:00 failed with error -1 I tried Kernels 4.15.0-20-generic (Ubuntu 18.04), 4.17.2, 4.17.8, 4.18, all do not work I tried with additional libinput from xorg, did not work. the Kernel-Module hid-multitouch is loaded but touchpad does not work. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.2 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2018-07-19 (0 days ago) + InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) + Package: linux (not installed) + Tags: bionic + Uname: Linux 4.17.2 x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1782653/+attachment/5165419/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782653 Title: ELAN1200 touchpad not working at all with kernel 4.15+; Recognized as ITE 8910 keyboard Status in linux package in Ubuntu: Confirmed Bug description: Laptop is an Asus-GL703GE Touchpad is an ELAN touchpad model 1200. (rev ?) This bug is relative to the Asus-GL703GE and any Asus laptop using the ELAN1200 touchpad that semms to be different from that Bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777679 (ASUS- GL503VD) cat /sys/bus/i2c/devices/i2c-ELAN1200\:00/modalias acpi:ELAN1200:PNP0C50: dmesg: [ 12.721751] i2c_hid i2c-ELAN1200:00: i2c-ELAN1200:00 supply vdd not found, using dummy regulator [ 12.723089] i2c_hid i2c-ELAN1200:00: Could not register for ELAN1200:00 interrupt, irq = 138, ret = -1 [ 12.723113] i2c_hid: probe of i2c-ELAN1200:00 failed with error -1 I tried Kernels 4.15.0-20-generic (Ubuntu 18.04), 4.17.2, 4.17.8, 4.18, all do not work I tried with additional libinput from xorg, did not work. the Kernel-Module hid-multitouch is loaded but touchpad does not work. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-19 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: linux (not installed) Tags: bionic Uname: Linux 4.17.2 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: 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/1782653/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782653] 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 1782653 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782653 Title: ELAN1200 touchpad not working at all with kernel 4.15+; Recognized as ITE 8910 keyboard Status in linux package in Ubuntu: Incomplete Bug description: Laptop is an Asus-GL703GE Touchpad is an ELAN touchpad model 1200. (rev ?) This bug is relative to the Asus-GL703GE and any Asus laptop using the ELAN1200 touchpad that semms to be different from that Bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777679 (ASUS- GL503VD) cat /sys/bus/i2c/devices/i2c-ELAN1200\:00/modalias acpi:ELAN1200:PNP0C50: dmesg: [ 12.721751] i2c_hid i2c-ELAN1200:00: i2c-ELAN1200:00 supply vdd not found, using dummy regulator [ 12.723089] i2c_hid i2c-ELAN1200:00: Could not register for ELAN1200:00 interrupt, irq = 138, ret = -1 [ 12.723113] i2c_hid: probe of i2c-ELAN1200:00 failed with error -1 I tried Kernels 4.15.0-20-generic (Ubuntu 18.04), 4.17.2, 4.17.8, 4.18, all do not work I tried with additional libinput from xorg, did not work. the Kernel-Module hid-multitouch is loaded but touchpad does not work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782653/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782653] [NEW] ELAN1200 touchpad not working at all with kernel 4.15+; Recognized as ITE 8910 keyboard
Public bug reported: Laptop is an Asus-GL703GE Touchpad is an ELAN touchpad model 1200. (rev ?) This bug is relative to the Asus-GL703GE and any Asus laptop using the ELAN1200 touchpad that semms to be different from that Bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777679 (ASUS- GL503VD) cat /sys/bus/i2c/devices/i2c-ELAN1200\:00/modalias acpi:ELAN1200:PNP0C50: dmesg: [ 12.721751] i2c_hid i2c-ELAN1200:00: i2c-ELAN1200:00 supply vdd not found, using dummy regulator [ 12.723089] i2c_hid i2c-ELAN1200:00: Could not register for ELAN1200:00 interrupt, irq = 138, ret = -1 [ 12.723113] i2c_hid: probe of i2c-ELAN1200:00 failed with error -1 I tried Kernels 4.15.0-20-generic (Ubuntu 18.04), 4.17.2, 4.17.8, 4.18, all do not work I tried with additional libinput from xorg, did not work. the Kernel-Module hid-multitouch is loaded but touchpad does not work. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: asus gl703ge touchpad ** Description changed: Laptop is an Asus-GL703GE Touchpad is an ELAN touchpad model 1200. (rev ?) This bug is relative to the Asus-GL703GE and any Asus laptop using the ELAN1200 touchpad that semms to be different from that Bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777679 (ASUS- GL503VD) - cat /sys/bus/i2c/devices/i2c-ELAN1200\:00/modalias + cat /sys/bus/i2c/devices/i2c-ELAN1200\:00/modalias acpi:ELAN1200:PNP0C50: dmesg: [ 12.721751] i2c_hid i2c-ELAN1200:00: i2c-ELAN1200:00 supply vdd not found, using dummy regulator [ 12.723089] i2c_hid i2c-ELAN1200:00: Could not register for ELAN1200:00 interrupt, irq = 138, ret = -1 [ 12.723113] i2c_hid: probe of i2c-ELAN1200:00 failed with error -1 I tried Kernels 4.15.0-20-generic (Ubuntu 18.04), 4.17.2, 4.17.8, 4.18, all do not work I tried with additional libinput from xorg, did not work. - the Kernel-Module hdm-multitouch is loaded but touchpad does not work. + the Kernel-Module hid-multitouch is loaded but touchpad does not work. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782653 Title: ELAN1200 touchpad not working at all with kernel 4.15+; Recognized as ITE 8910 keyboard Status in linux package in Ubuntu: New Bug description: Laptop is an Asus-GL703GE Touchpad is an ELAN touchpad model 1200. (rev ?) This bug is relative to the Asus-GL703GE and any Asus laptop using the ELAN1200 touchpad that semms to be different from that Bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777679 (ASUS- GL503VD) cat /sys/bus/i2c/devices/i2c-ELAN1200\:00/modalias acpi:ELAN1200:PNP0C50: dmesg: [ 12.721751] i2c_hid i2c-ELAN1200:00: i2c-ELAN1200:00 supply vdd not found, using dummy regulator [ 12.723089] i2c_hid i2c-ELAN1200:00: Could not register for ELAN1200:00 interrupt, irq = 138, ret = -1 [ 12.723113] i2c_hid: probe of i2c-ELAN1200:00 failed with error -1 I tried Kernels 4.15.0-20-generic (Ubuntu 18.04), 4.17.2, 4.17.8, 4.18, all do not work I tried with additional libinput from xorg, did not work. the Kernel-Module hid-multitouch is loaded but touchpad does not work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782653/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782174] Re: linux-gcp: 4.15.0-1014.14 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1782173 phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Thursday, 19. July 2018 21:00 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1782173 - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Thursday, 19. July 2018 21:00 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1782174 Title: linux-gcp: 4.15.0-1014.14 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff 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: 1782173 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/1782174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782645] Re: nvidia-384 384.130-0ubuntu0.14.04.1: nvidia-384 kernel module failed to build
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-384 in Ubuntu. https://bugs.launchpad.net/bugs/1782645 Title: nvidia-384 384.130-0ubuntu0.14.04.1: nvidia-384 kernel module failed to build Status in nvidia-graphics-drivers-384 package in Ubuntu: New Bug description: I get system error screen on booting. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-384 384.130-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 DKMSKernelVersion: 4.4.0-108-generic Date: Thu Jul 19 23:54:45 2018 DuplicateSignature: dkms:nvidia-384:384.130-0ubuntu0.14.04.1:cc: error: unrecognized command line option ‘-fstack-protector-strong’ InstallationDate: Installed on 2018-01-04 (196 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) PackageVersion: 384.130-0ubuntu0.14.04.1 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: nvidia-graphics-drivers-384 Title: nvidia-384 384.130-0ubuntu0.14.04.1: nvidia-384 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-384/+bug/1782645/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782645] Re: nvidia-384 384.130-0ubuntu0.14.04.1: nvidia-384 kernel module failed to build
Hi, Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. Seems this issue is caused by the version of your compiler (gcc/g++). See this line in DKMSBuildlog: "Makefile:702: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler". Check your gcc version, if it's not major than 4.8 that can be the root cause. This flag was added in version >= 4.9. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-384 in Ubuntu. https://bugs.launchpad.net/bugs/1782645 Title: nvidia-384 384.130-0ubuntu0.14.04.1: nvidia-384 kernel module failed to build Status in nvidia-graphics-drivers-384 package in Ubuntu: New Bug description: I get system error screen on booting. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-384 384.130-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 DKMSKernelVersion: 4.4.0-108-generic Date: Thu Jul 19 23:54:45 2018 DuplicateSignature: dkms:nvidia-384:384.130-0ubuntu0.14.04.1:cc: error: unrecognized command line option ‘-fstack-protector-strong’ InstallationDate: Installed on 2018-01-04 (196 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) PackageVersion: 384.130-0ubuntu0.14.04.1 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: nvidia-graphics-drivers-384 Title: nvidia-384 384.130-0ubuntu0.14.04.1: nvidia-384 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-384/+bug/1782645/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782499] Re: linux-aws: 4.4.0-1026.27 -proposed tracker
** Summary changed: - linux-aws: -proposed tracker + linux-aws: 4.4.0-1026.27 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1782499 Title: linux-aws: 4.4.0-1026.27 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1782497 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1782499/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1655280] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore': Bad address when trying to dump vmcore
Can you try the package in ppa:cascardo/ppa? Thanks. Cascardo. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1655280 Title: ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore': Bad address when trying to dump vmcore Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Bug description: == Comment: #0 - Ping Tian Han - 2017-01-09 02:51:00 == ---Problem Description--- Vmcore cannot be saved when triggering bug 150353 on roselp4: Copying data : [ 2.0 %] \/usr/sbin/kdump-config: line 591: 5502 Bus error makedumpfile $MAKEDUMP_ARGS $vmcore_file $KDUMP_CORETEMP [ 512.833872] kdump-tools[5450]: * kdump-tools: makedumpfile failed, falling back to 'cp' [ 573.595449] kdump-tools[5450]: cp: error reading '/proc/vmcore': Bad address [ 573.605717] kdump-tools[5450]: * kdump-tools: failed to save vmcore in /var/crash/201701090223 [ 573.765417] kdump-tools[5450]: * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/201701090223/dmesg.201701090223 [ 574.285506] kdump-tools[5450]: The kernel version is not supported. [ 574.285672] kdump-tools[5450]: The makedumpfile operation may be incomplete. [ 574.285767] kdump-tools[5450]: The dmesg log is saved to /var/crash/201701090223/dmesg.201701090223. [ 574.305422] kdump-tools[5450]: makedumpfile Completed. [ 574.315363] kdump-tools[5450]: * kdump-tools: saved dmesg content in /var/crash/201701090223 [ 574.615688] kdump-tools[5450]: Mon, 09 Jan 2017 02:24:26 -0600 [ 574.705384] kdump-tools[5450]: Rebooting. Stopping ifup for ib0... [ OK ] Stopped ifup for ib0. [ 1008.579897] reboot: Restarting system Contact Information = Ping Tian Han/pt...@cn.ibm.com Carrie Mitsuyoshi/carri...@us.ibm.com ---uname output--- Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = lpar ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. config kdump on roselp4 2. try to trigger bug 150353 *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com Carrie Mitsuyoshi/carri...@us.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. == Comment: #3 - Brahadambal Srinivasan - 2017-01-10 02:42:25 == root@roselp4:~# cat /proc/cmdline BOOT_IMAGE=/boot/vmlinux-4.8.0-34-generic root=UUID=0bcf3431-df8b-499c-9a13-33070f242e0c ro splash quiet crashkernel=384M-:512M root@roselp4:~# dmesg | grep Reser [0.00] Reserving 512MB of memory at 128MB for crashkernel (System RAM: 21760MB) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1655280/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782501] Re: linux-aws: 4.4.0-1064.73 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1782501 Title: linux-aws: 4.4.0-1064.73 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1782497 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1782501/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted
Look, obviously you can't solve all bugs in a single ticket, or you'd never get anything done. However, if you've got more than a hundred people who will still have a problem after a bug is closed, that means there needs to be a new bug created for it, *by the maintainers*! Otherwise you're doing the digital equivalent of sweeping the problem under the rug. This is how it works on every other ticket system. No one else closes a bug and says "hey 100+ users whose problem is not actually fixed ... your problem is fixed! And as a result no other fixes ... like the kind that might actually fix your problem ... will be coming." You can't just screw over 100+ *reporters* (and who knows how many other affected people) by guaranteeing they'll never get a fix, or at best by delaying their fix while you wait for someone to file a new ticket, all so that you can get one more "fixed bug" on your belt notch. You clearly understand the issue, you know the technical details, and you can create a new ticket in all of two minutes. Doing so would get the ball rolling on an actual fix for those 100+ users, instead of throwing them under the bus. -- 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/1490349 Title: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted Status in bluez package in Ubuntu: Invalid Bug description: On 15:10 after the bluetooth service has been stopped and restarted it is not possible to scan or connect to devices: $ sudo systemctl restart bluetooth $ bluetoothctl [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default] [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782184] Re: linux-gcp: 4.15.0-1014.14~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => 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/1782184 Title: linux-gcp: 4.15.0-1014.14~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1782173 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/1782184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782501] Re: linux-aws: 4.4.0-1064.73 -proposed tracker
** Summary changed: - linux-aws: -proposed tracker + linux-aws: 4.4.0-1064.73 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1782501 Title: linux-aws: 4.4.0-1064.73 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1782497 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1782501/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782642] [NEW] package libnvidia-gl-390 (not installed) failed to install/upgrade: new libnvidia-gl-390:i386 package pre-installation script subprocess returned error exit statu
Public bug reported: I was trying to reinstall my nvidia drivers because my computer was overheating and they weren't working correctly. After I purged the old ones then attempted to reinstall I got this error. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libnvidia-gl-390 (not installed) ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Jul 19 12:01:01 2018 ErrorMessage: new libnvidia-gl-390:i386 package pre-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2018-07-03 (15 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.2 SourcePackage: nvidia-graphics-drivers-390 Title: package libnvidia-gl-390 (not installed) failed to install/upgrade: new libnvidia-gl-390:i386 package pre-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1782642 Title: package libnvidia-gl-390 (not installed) failed to install/upgrade: new libnvidia-gl-390:i386 package pre-installation script subprocess returned error exit status 2 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: I was trying to reinstall my nvidia drivers because my computer was overheating and they weren't working correctly. After I purged the old ones then attempted to reinstall I got this error. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libnvidia-gl-390 (not installed) ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Jul 19 12:01:01 2018 ErrorMessage: new libnvidia-gl-390:i386 package pre-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2018-07-03 (15 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.2 SourcePackage: nvidia-graphics-drivers-390 Title: package libnvidia-gl-390 (not installed) failed to install/upgrade: new libnvidia-gl-390:i386 package pre-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1782642/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772991] Re: [Ubuntu 18.04.1] POWER9 - Nvidia Volta - Kernel changes to enable Nvidia driver on bare metal
** Changed in: ubuntu-power-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/1772991 Title: [Ubuntu 18.04.1] POWER9 - Nvidia Volta - Kernel changes to enable Nvidia driver on bare metal Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: == SRU Justification == 12 kernel patches have been identified as needed to support Nvidia Volta on bare metal. All are accepted upstream in 4.17. Three of those are already in bionic, leaving a total of 9 remaining commits needed in bionic. This pull request is for those other 9 commits. == Regression Potential == All of the commits are specific to powerpc. == Test Case == A test kernel was built with these patches and tested by IBM. == Comment: #0 - Barry B. Arndt - 2018-05-23 13:40:33 == 12 kernel patches have been identified as needed to support Nvidia Volta on bare metal. All are accepted upstream in 4.17. Three of those are already in bionic, leaving a total of 9 remaining commits needed in bionic. Those 9 commits are: 720c84046c26 powerpc/npu-dma.c: Fix crash after __mmu_notifier_register failure 2b74e2a9b39d powerpc/powernv/npu: Fix deadlock in mmio_invalidate() 5ee573e8ef03 powerpc/powernv/mce: Don't silently restart the machine fb5924fddf9e powerpc/mm: Flush cache on memory hot(un)plug 7fd6641de28f powerpc/powernv/memtrace: Let the arch hotunplug code flush cache 28a5933e8d36 powerpc/powernv/npu: Add lock to prevent race in concurrent context init/destroy a1409adac748 powerpc/powernv/npu: Prevent overwriting of pnv_npu2_init_contex() callback parameters d0cf9b561ca9 powerpc/powernv/npu: Do a PID GPU TLB flush when invalidating a large address range 75ecfb49516c powerpc/mce: Fix a bug where mce loops on memory UE. We cherry-picked the commits, and all applied cleanly. The resultant kernel built successfully and loaded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1772991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782181] Re: linux-oem: 4.15.0-1012.15 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released -- 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/1782181 Title: linux-oem: 4.15.0-1012.15 -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: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1782173 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/1782181/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782180] Re: linux-kvm: 4.15.0-1016.16 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => 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/1782180 Title: linux-kvm: 4.15.0-1016.16 -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: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in 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: 1782173 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/1782180/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771780] Re: [LTCTest][OPAL][OP920] cpupower idle-info is not listing stop4 and stop5 idle states when all CORES are guarded
** Changed in: ubuntu-power-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/1771780 Title: [LTCTest][OPAL][OP920] cpupower idle-info is not listing stop4 and stop5 idle states when all CORES are guarded Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Bug description: == SRU Justification == During testing, IBM found that cpupower idle-info is not listing stop4 and stop5 idle states when all CORES are guarded. A patch has been submitted upstream by IBM. However, the patch has not landed in linux-next or mainline as of yet. For that reason, this SRU request is being sent as a SAUCE patch request. == Fix == UBUNTU: SAUCE: cpuidle/powernv : init all present cpus for deep states == Regression Potential == Low. Limited to powerpc. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. == Comment: #0 - PAVAMAN SUBRAMANIYAM - 2018-05-16 04:07:59 == ---Problem Description--- cpupower idle-info is not listing stop4 and stop5 idle states when all CORES are guarded ---uname output--- Linux ltc-wspoon11 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = P9 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Install a P9 Open Power Hardware with Ubuntu 18.04 OS. root@ltc-wspoon11:~# uname -a Linux ltc-wspoon11 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@ltc-wspoon11:~# cat /etc/os-release NAME="Ubuntu" VERSION="18.04 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic Then guard an entire processor and also guard all the CORES in the processor 0 except for 1 single core. root@ltc-wspoon11:~# opal-gard list ID | Error| Type | Path --- 0001 | | Manual | /Sys0/Node0/Proc0/EQ1/EX0/Core0 0002 | | Manual | /Sys0/Node0/Proc0/EQ1/EX0/Core1 0003 | | Manual | /Sys0/Node0/Proc1 0004 | | Manual | /Sys0/Node0/Proc0/EQ2/EX0/Core1 0005 | | Manual | /Sys0/Node0/Proc0/EQ2/EX0/Core0 0006 | | Manual | /Sys0/Node0/Proc0/EQ2/EX1/Core0 0007 | | Manual | /Sys0/Node0/Proc0/EQ2/EX1/Core1 0008 | | Manual | /Sys0/Node0/Proc0/EQ3/EX0/Core0 0009 | | Manual | /Sys0/Node0/Proc0/EQ3/EX0/Core1 000a | | Manual | /Sys0/Node0/Proc0/EQ3/EX1/Core0 000b | | Manual | /Sys0/Node0/Proc0/EQ3/EX1/Core1 000c | | Manual | /Sys0/Node0/Proc0/EQ4/EX0/Core0 000d | | Manual | /Sys0/Node0/Proc0/EQ4/EX0/Core1 000e | | Manual | /Sys0/Node0/Proc0/EQ4/EX1/Core0 000f | | Manual | /Sys0/Node0/Proc0/EQ4/EX1/Core1 0010 | | Manual | /Sys0/Node0/Proc0/EQ5/EX0/Core0 0011 | | Manual | /Sys0/Node0/Proc0/EQ5/EX0/Core1 0012 | | Manual | /Sys0/Node0/Proc0/EQ5/EX1/Core0 0013 | | Manual | /Sys0/Node0/Proc0/EQ5/EX1/Core1 0014 | | Manual | /Sys0/Node0/Proc0/EQ1/EX1/Core0 0015 | | Manual | /Sys0/Node0/Proc0/EQ1/EX1/Core1 0016 | | Manual | /Sys0/Node0/Proc0/EQ0/EX1/Core1 0017 | | Manual | /Sys0/Node0/Proc0/EQ0/EX1/Core0 === Then execute the cpupower idle-info command to check the idle states being shown in the OS. root@ltc-wspoon11:~# cpupower idle-info CPUidle driver: powernv_idle CPUidle governor: menu analyzing CPU 0: Number of idle states: 7 Available idle states: snooze stop0_lite stop0 stop1_lite stop1 stop2_lite stop2 snooze: Flags/Description: snooze Latency: 0 Usage: 774653 Duration: 7698954 stop0_lite: Flags/Description: stop0_lite Latency: 1 Usage: 2751 Duration: 11363825 stop0: Flags/Description: stop0 Latency: 2 Usage: 2343 Duration: 915084 stop1_lite: Flags/Description: stop1_lite Latency: 5 Usage: 20 Duration: 1533 stop1:
[Kernel-packages] [Bug 1782176] Re: linux-aws: 4.15.0-1016.16 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => 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/1782176 Title: linux-aws: 4.15.0-1016.16 -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: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in 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: 1782173 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/1782176/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771344] Re: Fix enabling bridge MMIO windows
** Changed in: ubuntu-power-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/1771344
Title:
Fix enabling bridge MMIO windows
Status in The Ubuntu-power-systems project:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Artful:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Bug description:
== SRU Justification ==
IBM is requesting this patch in Bionic and Artful to fix a regression. The
regression was introduced in v3.11-rc1. The patch fixes enabling bridge
MMIO windows. Commit 13a83eac373c was also cc'd to upstream stable, and
has already landed in Xenial via upstream stable updates.
== Fix ==
13a83eac373c ("powerpc/eeh: Fix enabling bridge MMIO windows")
== Regression Potential ==
Low. Limited to powerpc and fixes a current regression.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
== Comment: #0 - Breno Leitao
On boot we save the configuration space of PCIe bridges. We do this so
when we get an EEH event and everything gets reset that we can restore
them.
Unfortunately we save this state before we've enabled the MMIO space
on the bridges. Hence if we have to reset the bridge when we come back
MMIO is not enabled and we end up taking an PE freeze when the driver
starts accessing again.
This patch forces the memory/MMIO and bus mastering on when restoring
bridges on EEH. Ideally we'd do this correctly by saving the
configuration space writes later, but that will have to come later in
a larger EEH rewrite. For now we have this simple fix.
The original bug can be triggered on a boston machine by doing:
echo 0x8000 >
/sys/kernel/debug/powerpc/PCI0001/err_injct_outbound
On boston, this PHB has a PCIe switch on it. Without this patch,
you'll see two EEH events, 1 expected and 1 the failure we are fixing
here. The second EEH event causes the anything under the PHB to
disappear (i.e. the i40e eth).
With this patch, only 1 EEH event occurs and devices properly recover.
This is commit id 13a83eac373c49c0a081cbcd137e79210fe78acd and should
be part of Ubuntu 18.04 kernel.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1771344/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771844] Re: powerpc/livepatch: Implement reliable stack tracing for the consistency model
** Changed in: ubuntu-power-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/1771844
Title:
powerpc/livepatch: Implement reliable stack tracing for the
consistency model
Status in The Ubuntu-power-systems project:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Bug description:
== SRU Justification ==
Livepatch has a consistency model which is a hybrid of kGraft and kpatch:
it uses kGraft's per-task consistency and syscall barrier switching
combined with kpatch's stack trace switching. The current approach is
stack checking of sleeping tasks. If no affected functions are on the
stack of a given task, the task is patched. In most cases this will patch
most or all of the tasks on the first try. Otherwise, it'll keep trying
periodically. This patch implements the reliable stack tracing for
consistency model a.k.a HAVE_RELIABLE_STACKTRACE.
This will help in switching livepatching implementation to basic per-task
consistency model. It is the foundation, which will help us enable
security patches changing function or data semantics. This is the biggest
remaining piece needed on ppc64le to make livepatch more generally useful.
== Fix ==
df78d3f61480 ("powerpc/livepatch: Implement reliable stack tracing for the
consistency model")
== Regression Potential ==
Low. Limited to powerpc.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=df78d3f6148092d33a9a24c7a9cfac
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1771844/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782178] Re: linux-azure: 4.15.0-1018.18 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug 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: 1782173 phase: Uploaded -- 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/1782178 Title: linux-azure: 4.15.0-1018.18 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1782173 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1782178/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1747507] Re: starting VMs causing retpoline4 to reboot
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1747507 Title: starting VMs causing retpoline4 to reboot Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Fix Released Bug description: Using 4.13.0-33.36~retpoline4 kernel test kernel from ppa https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/spectre/. CPU: AMD Ryzen 7 1700 Eight-Core Processor Ubuntu: 17.10. Steps to reproduce (has occurred both times I tried it): 1. Just run kvm with no options (or virsh start <> or start VM from GUI) Machine reboots Going back to 4.13.0-32 has virsh working again. qemu-system-x86_64 command works fine unless you use the enable kvm command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747507/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768431] Re: Request to revert SAUCE patches in the 18.04 SRU and update with upstream version
** Changed in: linux (Ubuntu Cosmic)
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/1768431
Title:
Request to revert SAUCE patches in the 18.04 SRU and update with
upstream version
Status in The Ubuntu-power-systems project:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Bug description:
== SRU Justification ==
This SRU was requested by IBM. It contains one SAUCE patch and three
commits from linux.next.
IBM requested that we revert a set of SAUCE patches from 18.04 and
replace them with patches from linux-next. Based on review comments,
there has been minor changes from the original SAUCE patches and the
versions in linux-next.
The first SAUCE patch contains all the changes between the current version
of SAUCE patches for latest cxlflash patches in bionic and the latest
version accepted by the community. This only has the needed changes and
makes it so we don't have to revert and re-apply a high number of patches.
In addition to the SAUCE patch, IBM requested the 3 additional new patches
from the linux-next tree.
== Fixes ==
UBUNTU: SAUCE: (no-up) cxlflash: OCXL diff between v2 and v3
a3feb6ef50de ("scsi: cxlflash: Synchronize reset and remove ops")
9a597cd4c0ce ("scsi: cxlflash: Remove commmands from pending list on timeout)"
d2d354a606d5 ("scsi: cxlflash: Handle spurious interrupts")
== Regression Potential ==
Medium. All the patches are specific to the cxlflash driver, but there
are four of them and one is a SAUCE patch.
== Test Case ==
A test kernel was built with these patches and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
== Comment: #0 - UMA KRISHNAN - 2018-04-30 14:41:30 ==
---Problem Description---
Request to revert SAUCE patches from 18.04 and apply the patches from
next/master.
Below set of cxlflash patches were submitted to Canonical after they
were sent to the community. Based on review comments, there has been
minor changes from that version. This BZ is to request reverting those
SAUCE patches with the ones that are queued in next/master tree for
4.18.
- SAUCE: cxlflash: Preserve number of interrupts for master contexts
- SAUCE: cxlflash: Avoid clobbering context control register value
- SAUCE: cxlflash: Add argument identifier names
- SAUCE: cxlflash: Introduce OCXL backend
- SAUCE: cxlflash: Hardware AFU for OCXL
- SAUCE: cxlflash: Read host function configuration
- SAUCE: cxlflash: Setup function acTag range
- SAUCE: cxlflash: Read host AFU configuration
- SAUCE: cxlflash: Setup AFU acTag range
- SAUCE: cxlflash: Setup AFU PASID
- SAUCE: cxlflash: Adapter context support for OCXL
- SAUCE: cxlflash: Use IDR to manage adapter contexts
- SAUCE: cxlflash: Support adapter file descriptors for OCXL
- SAUCE: cxlflash: Support adapter context discovery
- SAUCE: cxlflash: Support image reload policy modification
- SAUCE: cxlflash: MMIO map the AFU
- SAUCE: cxlflash: Support starting an adapter context
- SAUCE: cxlflash: Support process specific mappings
- SAUCE: cxlflash: Support AFU state toggling
- SAUCE: cxlflash: Support reading adapter VPD data
- SAUCE: cxlflash: Setup function OCXL link
- SAUCE: cxlflash: Setup OCXL transaction layer
- SAUCE: cxlflash: Support process element lifecycle
- SAUCE: cxlflash: Support AFU interrupt management
- SAUCE: cxlflash: Support AFU interrupt mapping and registration
- SAUCE: cxlflash: Support starting user contexts
- SAUCE: cxlflash: Support adapter context polling
- SAUCE: cxlflash: Support adapter context reading
- SAUCE: cxlflash: Support adapter context mmap and release
- SAUCE: cxlflash: Support file descriptor mapping
- SAUCE: cxlflash: Introduce object handle fop
- SAUCE: cxlflash: Setup LISNs for user contexts
- SAUCE: cxlflash: Setup LISNs for master contexts
- SAUCE: cxlflash: Update synchronous interrupt status bits
- SAUCE: cxlflash: Introduce OCXL context state machine
- SAUCE: cxlflash: Register for translation errors
- SAUCE: cxlflash: Support AFU reset
- SAUCE: cxlflash: Enable OCXL operations
Also, there are 3 additional patches added to end of this series that we
would like to request being pulled into the SRU stream. These 3 patches address
bug fixes.
The commit ids for the patches queued in next/master tree are,
768999d6b1eadc6a13b1fba1886f1708f433d82b scsi: cxlflash: Preserve number of
interrupts for master contexts
6c2b116dd38e3fbda10c3e3d5ac80ea7442e4f4d scsi: cxlflash: Avoid clobbering
context control register value
fcace1d5e11f518c6f91dd245fa1ac37393b47d3 scsi: cxlflash: Add argument
identifier names
[Kernel-packages] [Bug 1774964] Re: [LTCTest][OPAL][OP910.20] WARNING: CPU: 97 PID: 11965 at /build/linux-0zaMZw/linux-4.15.0/kernel/sched/core.c:1189 set_task_cpu+0x240/0x250
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1774964
Title:
[LTCTest][OPAL][OP910.20] WARNING: CPU: 97 PID: 11965 at /build/linux-
0zaMZw/linux-4.15.0/kernel/sched/core.c:1189 set_task_cpu+0x240/0x250
Status in The Ubuntu-power-systems project:
Fix Committed
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
IBM reports seeing the following during their testing:
WARNING: CPU: 97 PID: 11965 at
/build/linux-0zaMZw/linux-4.15.0/kernel/sched/core.c:1189
set_task_cpu+0x240/0x250
This is a regression and was introduced by the following two commits in
v4.15-rc1:
01eaac2b0591 ("powerpc/mce: Hookup ierror (instruction) UE errors")
ba41e1e1ccb9 ("powerpc/mce: Hookup derror (load/store) UE errors")
This regression is fixed by commit 75ecfb49516c in v4.17-rc3. The
commit was also cc'd to upstream stable, but it is being SRU'd to get
the fix into Ubuntu without waiting for it to come down via stable
updates.
== Fix ==
75ecfb49516c ("powerpc/mce: Fix a bug where mce loops on memory UE.")
== Regression Potential ==
Low. Limited to powerpc. The commit was also cc'd to upstream stable
so it will recieve additional upstream stable 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.
== Original Bug Descriptions ==
== Comment: #0 - PAVAMAN SUBRAMANIYAM <> - 2018-04-25 01:59:10 ==
---Problem Description---
WARNING: CPU: 97 PID: 11965 at
/build/linux-0zaMZw/linux-4.15.0/kernel/sched/core.c:1189
set_task_cpu+0x240/0x250
---uname output---
Linux ltc-wspoon8 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC
2018 ppc64le ppc64le ppc64le GNU/Linux
Machine Type = P9
---Debugger---
A debugger is not configured
---Steps to Reproduce---
Install a P9 Open Power Hardware with the latest OP910.20 Firmware images.
root@witherspoon:~# cat /etc/os-release
ID="openbmc-phosphor"
NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)"
VERSION="ibm-v2.0"
VERSION_ID="ibm-v2.0-0-r46-0-gbed584c"
PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)
ibm-v2.0"
BUILD_ID="ibm-v2.0-0-r46"
root@witherspoon:~# cat /var/lib/phosphor-software-manager/pnor/ro/VERSION
open-power-witherspoon-v1.21.2-251-ge2e9363-dirty
buildroot-2017.11-5-g65679be
skiboot-v5.10.3-op910-1-p240231e
hostboot-0aa5bed
linux-4.14.24-openpower1-p3e84190
petitboot-v1.6.6-pd7224b4
machine-xml-4af
occ-8c5b727
hostboot-binaries-9bd4056
capp-ucode-p9-dd2-v3
sbe-7e02c23
Then we have installed the Ubuntu 18.04 OS on the machine.
root@ltc-wspoon8:~# uname -a
Linux ltc-wspoon8 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC
2018 ppc64le ppc64le ppc64le GNU/Linux
root@ltc-wspoon8:~# cat /etc/os-release
NAME="Ubuntu"
VERSION="18.04 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/;
SUPPORT_URL="https://help.ubuntu.com/;
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic
root@ltc-wspoon8:~# cat /proc/cpuinfo | tail
cpu : POWER9, altivec supported
clock : 2300.00MHz
revision: 2.1 (pvr 004e 1201)
timebase: 51200
platform: PowerNV
model : 8335-GTC
machine : PowerNV 8335-GTC
firmware: OPAL
MMU : Radix
root@ltc-wspoon8:~# kdump-config show
DUMP_MODE:kdump
USE_KDUMP:1
KDUMP_SYSCTL: kernel.panic_on_oops=1
KDUMP_COREDIR:/var/crash
crashkernel addr:
/var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-20-generic
kdump initrd:
/var/lib/kdump/initrd.img: symbolic link to
/var/lib/kdump/initrd.img-4.15.0-20-generic
current state:ready to kdump
kexec command:
/sbin/kexec -p
--command-line="root=UUID=a2cd572c-9047-4f0a-843b-6996fae3e999 ro quiet splash
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb"
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
root@ltc-wspoon8:~# ps -ef | grep opal
root880 2 0 01:25 ?00:00:00 [kopald]
root 3604 1 2 01:25 ?00:00:03 /usr/sbin/opal-prd
root 4858 4278 0 01:28 pts/000:00:00 grep --color=auto opal
root@ltc-wspoon8:~# service opal-prd status
? opal-prd.service - OPAL PRD daemon
[Kernel-packages] [Bug 1768103] Re: Lancer A0 Asic HBA's won't boot with 18.04
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1768103
Title:
Lancer A0 Asic HBA's won't boot with 18.04
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Bug description:
== SRU Justification ==
It was reported by Broadcom that an early asic model (A0) of their 16/32GB
HBA's doesn't boot with the lpfc driver in Ubuntu 18.04.
Bionic with the lpfc driver 12.0.0.0 can't see LPe16002-M6 but can see
LPe16002B-M6.
This bug is fixed by commits bf316c78517d and c221768bd49a, which are
both still in linux-next. Broadcom tested with this two commits and
confirmed they resolve the bug and allow the system to boot.
== Fixes ==
Currently in linux-next:
bf316c78517d ("scsi: lpfc: Fix WQ/CQ creation for older asic's.")
c221768bd49a ("scsi: lpfc: Fix 16gb hbas failing cq create.")
== Regression Potential ==
Low. Patches fix a current regression and are limited to lpfc.
== Test Case ==
A test kernel was built with these patches and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
We have discovered that an early asic model (A0) of our 16/32GB HBA's doesn't
boot with the lpfc driver in Ubuntu 18.04.
After further review and discussion, this has been deemed a low risk
issue since early A0 HBA's were only ever shipped to OEMs for test
purposes. These cards were never shipped to end customers. We have
been working to replace those cards whenever we discover them.
We'll leave it up to Canonical to decide whether they want to pull
this in this single patch to an 18.04 subsequent update.
Symptom: Ubuntu 18.04 with lpfc driver 12.0.0.0 they can't see LPe16002-M6
but can see LPe16002B-M6
Resolution: new lpfc driver patch update.
scsi: lpfc: Fix WQ/CQ creation for older asic's.
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=4.18/scsi-queue=83fae8ca4ae09403bfb99542f1aaa292c06cb111
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768103/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771344] Re: Fix enabling bridge MMIO windows
** Changed in: linux (Ubuntu Cosmic)
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/1771344
Title:
Fix enabling bridge MMIO windows
Status in The Ubuntu-power-systems project:
Fix Committed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Artful:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Bug description:
== SRU Justification ==
IBM is requesting this patch in Bionic and Artful to fix a regression. The
regression was introduced in v3.11-rc1. The patch fixes enabling bridge
MMIO windows. Commit 13a83eac373c was also cc'd to upstream stable, and
has already landed in Xenial via upstream stable updates.
== Fix ==
13a83eac373c ("powerpc/eeh: Fix enabling bridge MMIO windows")
== Regression Potential ==
Low. Limited to powerpc and fixes a current regression.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
== Comment: #0 - Breno Leitao
On boot we save the configuration space of PCIe bridges. We do this so
when we get an EEH event and everything gets reset that we can restore
them.
Unfortunately we save this state before we've enabled the MMIO space
on the bridges. Hence if we have to reset the bridge when we come back
MMIO is not enabled and we end up taking an PE freeze when the driver
starts accessing again.
This patch forces the memory/MMIO and bus mastering on when restoring
bridges on EEH. Ideally we'd do this correctly by saving the
configuration space writes later, but that will have to come later in
a larger EEH rewrite. For now we have this simple fix.
The original bug can be triggered on a boston machine by doing:
echo 0x8000 >
/sys/kernel/debug/powerpc/PCI0001/err_injct_outbound
On boston, this PHB has a PCIe switch on it. Without this patch,
you'll see two EEH events, 1 expected and 1 the failure we are fixing
here. The second EEH event causes the anything under the PHB to
disappear (i.e. the i40e eth).
With this patch, only 1 EEH event occurs and devices properly recover.
This is commit id 13a83eac373c49c0a081cbcd137e79210fe78acd and should
be part of Ubuntu 18.04 kernel.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1771344/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772991] Re: [Ubuntu 18.04.1] POWER9 - Nvidia Volta - Kernel changes to enable Nvidia driver on bare metal
** 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/1772991 Title: [Ubuntu 18.04.1] POWER9 - Nvidia Volta - Kernel changes to enable Nvidia driver on bare metal Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: == SRU Justification == 12 kernel patches have been identified as needed to support Nvidia Volta on bare metal. All are accepted upstream in 4.17. Three of those are already in bionic, leaving a total of 9 remaining commits needed in bionic. This pull request is for those other 9 commits. == Regression Potential == All of the commits are specific to powerpc. == Test Case == A test kernel was built with these patches and tested by IBM. == Comment: #0 - Barry B. Arndt - 2018-05-23 13:40:33 == 12 kernel patches have been identified as needed to support Nvidia Volta on bare metal. All are accepted upstream in 4.17. Three of those are already in bionic, leaving a total of 9 remaining commits needed in bionic. Those 9 commits are: 720c84046c26 powerpc/npu-dma.c: Fix crash after __mmu_notifier_register failure 2b74e2a9b39d powerpc/powernv/npu: Fix deadlock in mmio_invalidate() 5ee573e8ef03 powerpc/powernv/mce: Don't silently restart the machine fb5924fddf9e powerpc/mm: Flush cache on memory hot(un)plug 7fd6641de28f powerpc/powernv/memtrace: Let the arch hotunplug code flush cache 28a5933e8d36 powerpc/powernv/npu: Add lock to prevent race in concurrent context init/destroy a1409adac748 powerpc/powernv/npu: Prevent overwriting of pnv_npu2_init_contex() callback parameters d0cf9b561ca9 powerpc/powernv/npu: Do a PID GPU TLB flush when invalidating a large address range 75ecfb49516c powerpc/mce: Fix a bug where mce loops on memory UE. We cherry-picked the commits, and all applied cleanly. The resultant kernel built successfully and loaded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1772991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771780] Re: [LTCTest][OPAL][OP920] cpupower idle-info is not listing stop4 and stop5 idle states when all CORES are guarded
** Changed in: linux (Ubuntu Cosmic) 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/1771780 Title: [LTCTest][OPAL][OP920] cpupower idle-info is not listing stop4 and stop5 idle states when all CORES are guarded Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Bug description: == SRU Justification == During testing, IBM found that cpupower idle-info is not listing stop4 and stop5 idle states when all CORES are guarded. A patch has been submitted upstream by IBM. However, the patch has not landed in linux-next or mainline as of yet. For that reason, this SRU request is being sent as a SAUCE patch request. == Fix == UBUNTU: SAUCE: cpuidle/powernv : init all present cpus for deep states == Regression Potential == Low. Limited to powerpc. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. == Comment: #0 - PAVAMAN SUBRAMANIYAM - 2018-05-16 04:07:59 == ---Problem Description--- cpupower idle-info is not listing stop4 and stop5 idle states when all CORES are guarded ---uname output--- Linux ltc-wspoon11 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = P9 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Install a P9 Open Power Hardware with Ubuntu 18.04 OS. root@ltc-wspoon11:~# uname -a Linux ltc-wspoon11 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@ltc-wspoon11:~# cat /etc/os-release NAME="Ubuntu" VERSION="18.04 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic Then guard an entire processor and also guard all the CORES in the processor 0 except for 1 single core. root@ltc-wspoon11:~# opal-gard list ID | Error| Type | Path --- 0001 | | Manual | /Sys0/Node0/Proc0/EQ1/EX0/Core0 0002 | | Manual | /Sys0/Node0/Proc0/EQ1/EX0/Core1 0003 | | Manual | /Sys0/Node0/Proc1 0004 | | Manual | /Sys0/Node0/Proc0/EQ2/EX0/Core1 0005 | | Manual | /Sys0/Node0/Proc0/EQ2/EX0/Core0 0006 | | Manual | /Sys0/Node0/Proc0/EQ2/EX1/Core0 0007 | | Manual | /Sys0/Node0/Proc0/EQ2/EX1/Core1 0008 | | Manual | /Sys0/Node0/Proc0/EQ3/EX0/Core0 0009 | | Manual | /Sys0/Node0/Proc0/EQ3/EX0/Core1 000a | | Manual | /Sys0/Node0/Proc0/EQ3/EX1/Core0 000b | | Manual | /Sys0/Node0/Proc0/EQ3/EX1/Core1 000c | | Manual | /Sys0/Node0/Proc0/EQ4/EX0/Core0 000d | | Manual | /Sys0/Node0/Proc0/EQ4/EX0/Core1 000e | | Manual | /Sys0/Node0/Proc0/EQ4/EX1/Core0 000f | | Manual | /Sys0/Node0/Proc0/EQ4/EX1/Core1 0010 | | Manual | /Sys0/Node0/Proc0/EQ5/EX0/Core0 0011 | | Manual | /Sys0/Node0/Proc0/EQ5/EX0/Core1 0012 | | Manual | /Sys0/Node0/Proc0/EQ5/EX1/Core0 0013 | | Manual | /Sys0/Node0/Proc0/EQ5/EX1/Core1 0014 | | Manual | /Sys0/Node0/Proc0/EQ1/EX1/Core0 0015 | | Manual | /Sys0/Node0/Proc0/EQ1/EX1/Core1 0016 | | Manual | /Sys0/Node0/Proc0/EQ0/EX1/Core1 0017 | | Manual | /Sys0/Node0/Proc0/EQ0/EX1/Core0 === Then execute the cpupower idle-info command to check the idle states being shown in the OS. root@ltc-wspoon11:~# cpupower idle-info CPUidle driver: powernv_idle CPUidle governor: menu analyzing CPU 0: Number of idle states: 7 Available idle states: snooze stop0_lite stop0 stop1_lite stop1 stop2_lite stop2 snooze: Flags/Description: snooze Latency: 0 Usage: 774653 Duration: 7698954 stop0_lite: Flags/Description: stop0_lite Latency: 1 Usage: 2751 Duration: 11363825 stop0: Flags/Description: stop0 Latency: 2 Usage: 2343 Duration: 915084 stop1_lite: Flags/Description: stop1_lite Latency: 5 Usage: 20 Duration: 1533 stop1:
[Kernel-packages] [Bug 1771844] Re: powerpc/livepatch: Implement reliable stack tracing for the consistency model
** Changed in: linux (Ubuntu Cosmic)
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/1771844
Title:
powerpc/livepatch: Implement reliable stack tracing for the
consistency model
Status in The Ubuntu-power-systems project:
Fix Committed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Bug description:
== SRU Justification ==
Livepatch has a consistency model which is a hybrid of kGraft and kpatch:
it uses kGraft's per-task consistency and syscall barrier switching
combined with kpatch's stack trace switching. The current approach is
stack checking of sleeping tasks. If no affected functions are on the
stack of a given task, the task is patched. In most cases this will patch
most or all of the tasks on the first try. Otherwise, it'll keep trying
periodically. This patch implements the reliable stack tracing for
consistency model a.k.a HAVE_RELIABLE_STACKTRACE.
This will help in switching livepatching implementation to basic per-task
consistency model. It is the foundation, which will help us enable
security patches changing function or data semantics. This is the biggest
remaining piece needed on ppc64le to make livepatch more generally useful.
== Fix ==
df78d3f61480 ("powerpc/livepatch: Implement reliable stack tracing for the
consistency model")
== Regression Potential ==
Low. Limited to powerpc.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=df78d3f6148092d33a9a24c7a9cfac
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1771844/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782173] Re: linux: 4.15.0-29.31 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff 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/1782173 Title: linux: 4.15.0-29.31 -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: In Progress 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: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in 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 1782182 (linux-hwe-edge), bug 1782183 (linux-hwe), bug 1782184 (linux-gcp), bug 1782185 (linux-azure-edge), bug 1782186 (linux-azure) derivatives: bug 1782174 (linux-gcp), bug 1782175 (linux-raspi2), bug 1782176 (linux-aws), bug 1782178 (linux-azure), bug 1782180 (linux-kvm), bug 1782181 (linux-oem) -- 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/1782173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771439] Re: [LTC Test] Ubuntu 18.04: tm_sigreturn failed on P8 compat mode 16.04.04 guest
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1771439
Title:
[LTC Test] Ubuntu 18.04: tm_sigreturn failed on P8 compat mode
16.04.04 guest
Status in The Ubuntu-power-systems project:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Bug description:
== SRU Justification ==
IBM is seeing tm_sigreturn test failures on P8 and P9 hosts. The bad thing
exception is being raised when executing the following line:
c004fcfc: b0 04 03 e8 ld r0,1200(r3)
-> c004fd00: a6 23 02 7c mtspr 130,r0
Which is basically restoring TEXASR in the thread.
ISA says "These registers can be written only when in Non-transactional
state" and the MSR is set to be transactional (suspended):
MSR: 800300201033 [ME][RI][IR][DR][LE][SF][HTM][TSU]
That explains why they are getting the "bad thing exception". A mtspr is
being called with a transaction suspended.
This test failure is fixed by upstream commit 78a3e8889b4b.
Upstream commit 78a3e8889b4b is in mainline as of 4.8-rc5.
== Fix ==
78a3e8889b4b ("powerpc: signals: Discard transaction state from signal
frames")
== Regression Potential ==
Low. Specific to powerpc.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
This test fails in the same way on a P8 host, so it is nothing to do with P9.
There have been many TM bugs fixed upstream since 4.4. I would suggest
starting with commit 044215d145a7 ("powerpc/tm: Fix illegal TM state
in signal handler", 2017-08-22) and see if that helps.
The bad thing exception is being raised when executing the following
line:
c004fcfc: b0 04 03 e8 ld r0,1200(r3)
-> c004fd00: a6 23 02 7c mtspr 130,r0
Which is basically restoring TEXASR in the thread.
ISA says "These registers can be written only when in Non-
transactional state" and the MSR is set to be transactional
(suspended):
MSR: 800300201033 [ME][RI][IR][DR][LE][SF][HTM][TSU]
That explains why we are getting the "bad thing exception". A mtspr is
being called with a transaction suspended.
I think we need the following commit to have this fixed:
commit 78a3e8889b4b6b99775ed954696ff3e017f5d19b
Author: Cyril Bur
Date: Tue Aug 23 10:46:17 2016 +1000
powerpc: signals: Discard transaction state from signal frames
Userspace can begin and suspend a transaction within the signal
handler which means they might enter sys_rt_sigreturn() with the
processor in suspended state.
sys_rt_sigreturn() wants to restore process context (which may have
been in a transaction before signal delivery). To do this it must
restore TM SPRS. To achieve this, any transaction initiated within the
signal frame must be discarded in order to be able to restore TM SPRs
as TM SPRs can only be manipulated non-transactionally..
>From the PowerPC ISA:
TM Bad Thing Exception [Category: Transactional Memory]
An attempt is made to execute a mtspr targeting a TM register in
other than Non-transactional state.
Not doing so results in a TM Bad Thing:
[12045.221359] Kernel BUG at c0050a40 [verbose debug info
unavailable]
[12045.221470] Unexpected TM Bad Thing exception at c0050a40 (msr
0x201033)
[12045.221540] Oops: Unrecoverable exception, sig: 6 [#1]
[12045.221586] SMP NR_CPUS=2048 NUMA PowerNV
[12045.221634] Modules linked in: xt_CHECKSUM iptable_mangle
ipt_MASQUERADE
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4
nf_defrag_ipv4
xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp
llc ebtable_filter
ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables
kvm_hv kvm
uio_pdrv_genirq ipmi_powernv uio powernv_rng ipmi_msghandler autofs4 ses
enclosure
scsi_transport_sas bnx2x ipr mdio libcrc32c
[12045.222167] CPU: 68 PID: 6178 Comm: sigreturnpanic Not tainted 4.7.0
#34
[12045.24] task: c000fce38600 ti: c000fceb4000 task.ti:
c000fceb4000
[12045.93] NIP: c0050a40 LR: c00163bc CTR:
[12045.222361] REGS: c000fceb7ac0 TRAP: 0700 Not tainted (4.7.0)
[12045.222418] MSR: 900300201033 CR:
28444280 XER: 2000
[12045.222625] CFAR: c00163b8 SOFTE: 0 PACATMSCRATCH:
90014280f033
GPR00: 0110b801 c000fceb7d40 c139c100 c000fce390d0
GPR04: 90034280f033
GPR08:
[Kernel-packages] [Bug 1776211] Re: kdump fails to take dump with smt set to 2, hmc dumpstart
** Changed in: linux (Ubuntu Artful)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1776211
Title:
kdump fails to take dump with smt set to 2, hmc dumpstart
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
Invalid
Status in makedumpfile package in Ubuntu:
Incomplete
Status in linux source package in Artful:
Invalid
Status in makedumpfile source package in Artful:
Incomplete
Bug description:
== SRU Justification ==
IBM has requested these three commits in Artful. In Artful, kdump fails to
capture dump when smt=2 or off.
Including these three commits allows kdump to work properly.
== Fixes ==
4388c9b3a6ee ("powerpc: Do not send system reset request through the oops
path")
04b9c96eae72 ("powerpc/crash: Remove the test for cpu_online in the IPI
callback")
4552d128c26e ("powerpc: System reset avoid interleaving oops using die
synchronisation")
== Regression Potential ==
Low. Fixes are limited to powerpc.
== Test Case ==
A test kernel was built with these patches and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
--Problem Description---
kdump fails to take dump with smt set to 2, hmc dumpstart
---Issue observed---
[0.004111] Oops: Exception in kernel mode, sig: 4 [#1]
[0.004118] SMP NR_CPUS=2048
[0.004120] NUMA
[0.004125] pSeries
[0.004132] Modules linked in:
[0.004142] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.13.0-12-generic
#13-Ubuntu
[0.004153] task: c00046715900 task.stack: c00046134000
[0.004162] NIP: c0006468 LR: c801764c CTR:
006cdc70
[0.004173] REGS: c00047fe3ce0 TRAP: 0700 Not tainted
(4.13.0-12-generic)
[0.004181] MSR: 80081031
[0.004193] CR: 8804 XER: 2003
[0.004204] CFAR: c0006454 SOFTE: 0
[0.004204] GPR00: c801764c c00047fe3f60 c95e3000
[0.004204] GPR04: 0001 0002
ffdf
[0.004204] GPR08: 2804 0002
0002
[0.004204] GPR12: cfff c00046137f90
0b5452d8
[0.004204] GPR16: fffd 089ffd10 0136
0b55d378
[0.004204] GPR20: 0060 1eca 0a6c
0007
[0.004204] GPR24: c9621ed0
[0.004204] GPR28: c00046134000 c00046137c80
c9105df8
[0.004328] NIP [c0006468] 0xc0006468
[0.004338] LR [c801764c] __do_irq+0x4c/0x1c0
[0.004345] Call Trace:
[0.004354] [c00047fe3f60] [c801764c] __do_irq+0x4c/0x1c0
(unreliable)
[0.004368] [c00047fe3f90] [c802ab70] call_do_irq+0x14/0x24
[0.004380] [c00046137bc0] [c801785c] do_IRQ+0x9c/0x130
[0.004393] [c00046137c10] [c8008ac4]
hardware_interrupt_common+0x114/0x120
[0.004409] --- interrupt: 501 at arch_local_irq_restore+0x5c/0x90
[0.004409] LR = arch_local_irq_restore+0x40/0x90
[0.004423] [c00046137f00] [0005] 0x5 (unreliable)
[0.004436] [c00046137f20] [c8049824]
start_secondary+0x324/0x350
[0.004450] [c00046137f90] [c800aa6c]
start_secondary_prolog+0x10/0x14
[0.004460] Instruction dump:
[0.004467]
[0.004484]
[0.004506] ---[ end trace 3e5a2a9047ef3cd0 ]---
[0.004512]
[0.004518] Oops: Exception in kernel mode, sig: 4 [#2]
[0.004525] SMP NR_CPUS=2048
[0.004526] NUMA
[0.004532] pSeries
[0.004540] Modules linked in:
[0.004550] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G D
4.13.0-12-generic #13-Ubuntu
[0.004561] task: c9579f00 task.stack: c95dc000
[0.004569] NIP: c0006460 LR: c80b6e80 CTR:
[0.004580] REGS: c95dfb20 TRAP: 0700 Tainted: G D
(4.13.0-12-generic)
[0.004589] MSR: 80081031
[0.004599] CR: 22002228 XER: 2004
[0.004611] CFAR: c000493c SOFTE: 0
[0.004611] GPR00: c95dfda0 c95e3000
[0.004611] GPR04:
[0.004611] GPR08: 22002228 7fff
0008
[0.004611] GPR12: cfff0a80 c00c7e137f90
[Kernel-packages] [Bug 1765105] Re: HP Smart Array driver fails to load, kernel panics boot process
*** This bug is a duplicate of bug 1765232 *** https://bugs.launchpad.net/bugs/1765232 Bug can be closed, it's a problem about fw card and hpsa, please update fw of your p400 card and it will works at 100% -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1765105 Title: HP Smart Array driver fails to load, kernel panics boot process Status in linux package in Ubuntu: Confirmed Bug description: Hi I have an HP ProLiant G6 with a Smart Array controller on Bionic, Kernel 4.15.0-15, that fails to load the hpsa driver for the Smart Array, (occasionally) drops to the initramfs shell, as it cannot find a root device in a reasonable amount of time, and then finally kernel panics with the stack trace leading to the hpsa driver. Occasionally it will complain about resetting the logical volume scsi bus. Downgrading to the previous kernel 4.15.0-13 works just fine. Attached is a screenshot showing the kernel panic, and below is a link to a YouTube video of the whole boot process, a video recording from ILO. To save you the time of watching the whole thing, 39 seconds is the bus reset error, then it hangs around waiting for a root device, and the kernel panics at 4:16. The relevant information are separate below Video: https://youtu.be/45ka2Btgiqk lsb_release: Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1777194] Re: Hard LOCKUP observed on stressing Ubuntu 18 04
I built a .deb version of the kernel that is currently in -proposed.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1777194
Can you test this kernel and see if it resolves this 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/1777194
Title:
Hard LOCKUP observed on stressing Ubuntu 18 04
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
IBM has seen hard lockups when running stress tests against Bionic.
These test sometimes lead to rcu_stalls. IBM found that this bug is
resolved with commits 6bed3237624e and ac61c1156623.
== Fixes ==
6bed3237624e ("powerpc: use NMI IPI for smp_send_stop")
ac61c1156623 ("powerpc: Fix smp_send_stop NMI IPI handling")
== Regression Potential ==
Low. Limited to powerpc.
== Test Case ==
A test kernel was built with these patches and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
--Problem Description--
Hard LOCKUP on stressing Ubuntu 18 04
---Issue observed---
Hard LOCKUP on stressing Ubuntu 18 04 using Ubuntu 18 04, sometimes leads to
rcu_stalls.
Apr 17 00:00:23 lep8d kernel: [ 4309.786755] Watchdog CPU:3 Hard LOCKUP
Apr 17 00:00:23 lep8d kernel: [ 4309.786759] Modules linked in: algif_rng
salsa20_generic userio camellia_generic cast6_generic cast_common snd_seq
snd_seq_device snd_timer snd soundcore vhost_net serpent_generic tap
twofish_generic twofish_common vhost_vsock vmw_vsock_virtio_transport_common
vhost vsock lrw unix_diag algif_skcipher cuse sctp tgr192 wp512 rmd320 rmd256
rmd160 hci_vhci rmd128 bluetooth ecdh_generic dccp_ipv4 md4 uhid hid algif_hash
dccp af_alg xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4
iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack
nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc
ebtable_filter ebtables devlink ip6table_filter ip6_tables iptable_filter
kvm_hv kvm binfmt_misc uio_pdrv_genirq uio vmx_crypto ibmpowernv
powernv_op_panel ipmi_powernv
Apr 17 00:00:23 lep8d kernel: [ 4309.786899] ipmi_devintf ipmi_msghandler
powernv_rng leds_powernv crct10dif_vpmsum sch_fq_codel ip_tables x_tables
autofs4 ses enclosure scsi_transport_sas btrfs xor zstd_compress raid6_pq uas
usb_storage crc32c_vpmsum tg3 ipr
Apr 17 00:00:23 lep8d kernel: [ 4309.786944] CPU: 3 PID: 28361 Comm:
stress-ng-hrtim Not tainted 4.15.0-15-generic #16-Ubuntu
Apr 17 00:00:23 lep8d kernel: [ 4309.786950] NIP: c0d0c8b8 LR:
c0120dbc CTR: c0024480
Apr 17 00:00:23 lep8d kernel: [ 4309.786956] REGS: c7f7fd80 TRAP:
0900 Not tainted (4.15.0-15-generic)
Apr 17 00:00:23 lep8d kernel: [ 4309.786957] MSR: 90009033
CR: 28000442 XER: 2000
Apr 17 00:00:23 lep8d kernel: [ 4309.786972] CFAR: c0120db8 SOFTE: 0
Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR00: c0120dbc
c02d51377ba0 c16eb400 c02d512b0f88
Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR04:
0001 01f40668 0001
Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR08: 0001
8003
Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR12: c0024480
c7a22100 000186a0
Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR16: 7fffed3687e0
0abda98e5db8 8005 00040100
Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR20:
418004fc 003c 0843
Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR24: c02d512b0f88
c02d51377d30 c02d52d47c00
Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR28: c02d51377d50
c02d51377d50 c02d52f04500 c02d512b0f88
Apr 17 00:00:23 lep8d kernel: [ 4309.787035] NIP [c0d0c8b8]
_raw_spin_lock+0x38/0xe0
Apr 17 00:00:23 lep8d kernel: [ 4309.787045] LR [c0120dbc]
dequeue_signal+0xcc/0x260
Apr 17 00:00:23 lep8d kernel: [ 4309.787046] Call Trace:
Apr 17 00:00:23 lep8d kernel: [ 4309.787052] [c02d51377bd0]
[c0120dac] dequeue_signal+0xbc/0x260
Apr 17 00:00:23 lep8d kernel: [ 4309.787059] [c02d51377c20]
[c012459c] get_signal+0x13c/0x7a0
Apr 17 00:00:23 lep8d kernel: [ 4309.787066] [c02d51377d10]
[c001dacc] do_signal+0x7c/0x2c0
Apr 17 00:00:23 lep8d kernel: [ 4309.787072] [c02d51377e00]
[c001deb0] do_notify_resume+0xd0/0x100
Apr 17 00:00:23 lep8d kernel: [ 4309.787083] [c02d51377e30]
[c000b7c4] ret_from_except_lite+0x70/0x74
Apr 17 00:00:23 lep8d kernel: [ 4309.787085] Instruction dump:
[Kernel-packages] [Bug 1782174] Re: linux-gcp: 4.15.0-1014.14 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1782174 Title: linux-gcp: 4.15.0-1014.14 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in 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: 1782173 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1782174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781533] Re: SATA device is not going to DEVSLP
** Changed in: hwe-next Status: New => In Progress -- 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/1781533 Title: SATA device is not going to DEVSLP Status in HWE Next: In Progress Status in OEM Priority Project: Triaged Status in linux-oem package in Ubuntu: In Progress Bug description: [Impact] Any of the platforms we’ve been seeing SATA problems not going to deepest state leading to other devices not getting there during long idle or s2idle. And it also prevents the system from entering deeper PC state other than PC3. [Test] Verified the power consumption on some new platforms, it doesn't do too much difference to the numbers, but it improves. [Fix] Suggested from Intel and Dell to contains the 2 commits https://patchwork.kernel.org/patch/10502285/ https://patchwork.kernel.org/patch/10502287/ [Regression Potential] Low, the production machines with suspend-to-idle enabled should have the DEVSLP function been validated. [Misc] Those commits do not show up in any public git tree yet, so let's verify them in oem kernel first, and then will submit to bionic kernel later. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1781533/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782174] Re: linux-gcp: 4.15.0-1014.14 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1782174 Title: linux-gcp: 4.15.0-1014.14 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in 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: 1782173 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1782174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782186] Re: linux-azure: 4.15.0-1018.18~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1782186 Title: linux-azure: 4.15.0-1018.18~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1782173 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1782186/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782186] Re: linux-azure: 4.15.0-1018.18~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1782186 Title: linux-azure: 4.15.0-1018.18~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1782173 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1782186/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782503] Re: linux-kvm: 4.4.0-1030.35 -proposed tracker
** Summary changed: - linux-kvm: -proposed tracker + linux-kvm: 4.4.0-1030.35 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1782503 Title: linux-kvm: 4.4.0-1030.35 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1782497 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1782503/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782174] Re: linux-gcp: 4.15.0-1014.14 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug 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: 1782173 phase: Uploaded -- 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/1782174 Title: linux-gcp: 4.15.0-1014.14 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in 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: 1782173 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1782174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782186] Re: linux-azure: 4.15.0-1018.18~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-xenial ** Tags added: block-proposed ** Description changed: This bug 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: 1782173 phase: Uploaded -- 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/1782186 Title: linux-azure: 4.15.0-1018.18~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1782173 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1782186/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1778642] Re: ubuntu_lttng_smoke_test failed on Azure 4.15
** Description changed: - ***THIS IS A POTENTIAL REGRESSION*** + SRU Request: + + [Impact] This test will pass with the older kernel, 4.15.0-1013-azure, but not the 4.15.0-1014-azure in -proposed. It looks like the kernel module can be installed, but four tests have failed: == lttng smoke test of session create/destroy == Session test-kernel-session created. Traces will be written in /tmp/lttng-kernel-trace-14716-session PASSED (lttng create) Session test-kernel-session destroyed PASSED (lttng destroy) == lttng smoke test list kernel events == FAILED (lttng list --kernel) FAILED (lttng list --kernel more output expected) == lttng smoke test trace open/close system calls == Session test-kernel-session created. Traces will be written in /tmp/lttng-kernel-trace-14716-session PASSED (lttng create) FAILED (lttng enable-event) Session test-kernel-session destroyed == lttng smoke test trace context switches == Session test-kernel-session created. Traces will be written in /tmp/lttng-kernel-trace-14716-session PASSED (lttng create) FAILED (lttng enable-event) Session test-kernel-session destroyed Summary: 4 passed, 4 failed http://10.246.72.46/4.15.0-1014.14-azure/bionic-linux-azure- azure-4.15.0-Standard_D12-ubuntu_lttng_smoke_test/ubuntu_lttng_smoke_test/results/ubuntu_lttng_smoke_test .lttng-smoke-test/debug/ubuntu_lttng_smoke_test.lttng-smoke- test.DEBUG.html Error message from /var/log/syslog: - kernel: [ 639.531889] PKCS#7 signature not signed with a trusted key - kernel: [ 639.538251] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0) - kernel: [ 639.538280] lttng_tracer: Unknown symbol lttng_hp_online (err 0) - lttng-sessiond[1097]: Error: Unable to load required module lttng-ring-buffer-client-discard - lttng-sessiond[1097]: Warning: No kernel tracer available - kernel: [ 639.606845] PKCS#7 signature not signed with a trusted key - kernel: [ 639.613331] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0) - kernel: [ 639.613360] lttng_tracer: Unknown symbol lttng_hp_online (err 0) - lttng-sessiond[1097]: Error: Unable to load required module lttng-ring-buffer-client-discard - lttng-sessiond[1097]: Warning: No kernel tracer available - kernel: [ 639.677124] PKCS#7 signature not signed with a trusted key - kernel: [ 639.680857] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0) - kernel: [ 639.680886] lttng_tracer: Unknown symbol lttng_hp_online (err 0) - lttng-sessiond[1097]: Error: Unable to load required module lttng-ring-buffer-client-discard - lttng-sessiond[1097]: Warning: No kernel tracer available - kernel: [ 639.737914] PKCS#7 signature not signed with a trusted key - kernel: [ 639.753366] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0) - kernel: [ 639.753394] lttng_tracer: Unknown symbol lttng_hp_online (err 0) - lttng-sessiond[1097]: Error: Unable to load required module lttng-ring-buffer-client-discard - lttng-sessiond[1097]: Warning: No kernel tracer available - kernel: [ 639.829710] PKCS#7 signature not signed with a trusted key - kernel: [ 639.843736] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0) - kernel: [ 639.843765] lttng_tracer: Unknown symbol lttng_hp_online (err 0) - lttng-sessiond[1097]: Error: Unable to load required module lttng-ring-buffer-client-discard - lttng-sessiond[1097]: Warning: No kernel tracer available + kernel: [ 639.531889] PKCS#7 signature not signed with a trusted key + kernel: [ 639.538251] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0) + kernel: [ 639.538280] lttng_tracer: Unknown symbol lttng_hp_online (err 0) + lttng-sessiond[1097]: Error: Unable to load required module lttng-ring-buffer-client-discard + lttng-sessiond[1097]: Warning: No kernel tracer available + kernel: [ 639.606845] PKCS#7 signature not signed with a trusted key + kernel: [ 639.613331] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0) + kernel: [ 639.613360] lttng_tracer: Unknown symbol lttng_hp_online (err 0) + lttng-sessiond[1097]: Error: Unable to load required module lttng-ring-buffer-client-discard + lttng-sessiond[1097]: Warning: No kernel tracer available + kernel: [ 639.677124] PKCS#7 signature not signed with a trusted key + kernel: [ 639.680857] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0) + kernel: [ 639.680886] lttng_tracer: Unknown symbol lttng_hp_online (err 0) + lttng-sessiond[1097]: Error: Unable to load required module lttng-ring-buffer-client-discard + lttng-sessiond[1097]: Warning: No kernel tracer available + kernel: [ 639.737914] PKCS#7 signature not signed with a trusted key + kernel: [ 639.753366] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0) + kernel: [ 639.753394] lttng_tracer: Unknown symbol lttng_hp_online (err 0) + lttng-sessiond[1097]: Error: Unable to load required module lttng-ring-buffer-client-discard + lttng-sessiond[1097]: Warning: No
[Kernel-packages] [Bug 1778642] Re: ubuntu_lttng_smoke_test failed on Azure 4.15
** Patch added: "debdiff for Xenial" https://bugs.launchpad.net/ubuntu/xenial/+source/lttng-modules/+bug/1778642/+attachment/5165340/+files/lttng-modules_2.8.0-1ubuntu1~16.04.7.debdiff -- 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/1778642 Title: ubuntu_lttng_smoke_test failed on Azure 4.15 Status in lttng-modules: New Status in ubuntu-kernel-tests: Invalid Status in linux-azure package in Ubuntu: Invalid Status in lttng-modules package in Ubuntu: In Progress Status in linux-azure source package in Xenial: Invalid Status in lttng-modules source package in Xenial: In Progress Status in linux-azure source package in Bionic: Invalid Status in lttng-modules source package in Bionic: In Progress Status in linux-azure source package in Cosmic: Invalid Status in lttng-modules source package in Cosmic: In Progress Bug description: ***THIS IS A POTENTIAL REGRESSION*** This test will pass with the older kernel, 4.15.0-1013-azure, but not the 4.15.0-1014-azure in -proposed. It looks like the kernel module can be installed, but four tests have failed: == lttng smoke test of session create/destroy == Session test-kernel-session created. Traces will be written in /tmp/lttng-kernel-trace-14716-session PASSED (lttng create) Session test-kernel-session destroyed PASSED (lttng destroy) == lttng smoke test list kernel events == FAILED (lttng list --kernel) FAILED (lttng list --kernel more output expected) == lttng smoke test trace open/close system calls == Session test-kernel-session created. Traces will be written in /tmp/lttng-kernel-trace-14716-session PASSED (lttng create) FAILED (lttng enable-event) Session test-kernel-session destroyed == lttng smoke test trace context switches == Session test-kernel-session created. Traces will be written in /tmp/lttng-kernel-trace-14716-session PASSED (lttng create) FAILED (lttng enable-event) Session test-kernel-session destroyed Summary: 4 passed, 4 failed http://10.246.72.46/4.15.0-1014.14-azure/bionic-linux-azure- azure-4.15.0-Standard_D12-ubuntu_lttng_smoke_test/ubuntu_lttng_smoke_test/results/ubuntu_lttng_smoke_test .lttng-smoke-test/debug/ubuntu_lttng_smoke_test.lttng-smoke- test.DEBUG.html Error message from /var/log/syslog: kernel: [ 639.531889] PKCS#7 signature not signed with a trusted key kernel: [ 639.538251] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0) kernel: [ 639.538280] lttng_tracer: Unknown symbol lttng_hp_online (err 0) lttng-sessiond[1097]: Error: Unable to load required module lttng-ring-buffer-client-discard lttng-sessiond[1097]: Warning: No kernel tracer available kernel: [ 639.606845] PKCS#7 signature not signed with a trusted key kernel: [ 639.613331] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0) kernel: [ 639.613360] lttng_tracer: Unknown symbol lttng_hp_online (err 0) lttng-sessiond[1097]: Error: Unable to load required module lttng-ring-buffer-client-discard lttng-sessiond[1097]: Warning: No kernel tracer available kernel: [ 639.677124] PKCS#7 signature not signed with a trusted key kernel: [ 639.680857] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0) kernel: [ 639.680886] lttng_tracer: Unknown symbol lttng_hp_online (err 0) lttng-sessiond[1097]: Error: Unable to load required module lttng-ring-buffer-client-discard lttng-sessiond[1097]: Warning: No kernel tracer available kernel: [ 639.737914] PKCS#7 signature not signed with a trusted key kernel: [ 639.753366] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0) kernel: [ 639.753394] lttng_tracer: Unknown symbol lttng_hp_online (err 0) lttng-sessiond[1097]: Error: Unable to load required module lttng-ring-buffer-client-discard lttng-sessiond[1097]: Warning: No kernel tracer available kernel: [ 639.829710] PKCS#7 signature not signed with a trusted key kernel: [ 639.843736] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0) kernel: [ 639.843765] lttng_tracer: Unknown symbol lttng_hp_online (err 0) lttng-sessiond[1097]: Error: Unable to load required module lttng-ring-buffer-client-discard lttng-sessiond[1097]: Warning: No kernel tracer available To manage notifications about this bug go to: https://bugs.launchpad.net/lttng-modules/+bug/1778642/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782544] Re: tcpreplay and veth device; extra transmit bytes on 4.4.0-130-generic kernel
Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 stable kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.141 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: linux (Ubuntu Xenial) 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/1782544 Title: tcpreplay and veth device; extra transmit bytes on 4.4.0-130-generic kernel Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: Issue found in a test harness for some code running on Ubuntu 16.04.4 LTS where we use a veth device to play in packets to the code under test. Essentially we see an extra 14 bytes being transmitted at the end of every packet that is just random garbage. Problem came in with the 4.4.0-130 kernel; if I revert to the 4.4.0-128 kernel the issue goes away. I have verified the issue on several different boxes running 16.04 The following steps reproduce the problem: 1) Veth setup sudo ip link add name nic1 type veth peer name nic2 sudo sysctl -q -w net.ipv6.conf.nic1.disable_ipv6=1 sudo sysctl -q -w net.ipv6.conf.nic2.disable_ipv6=1 sudo ip link set nic1 up sudo ip link set nic2 up 2) Configure tcpdump to collect packets on one interface: sudo tcpdump -i nic1 -w outPkts.pcap 3) Play in packets on the other (Any pcap will do): sudo tcpreplay -q -i nic2 inPkts.pcap When I check ifconfig I can see nic2/nic1 transmitting/receiving more bytes than expected. Opening the capture seen by tcpdump shows an extra 14 bytes received for every packet when compared to the input. tcpreplay version info: tcpreplay version: 3.4.4 (build 2450) (debug) Copyright 2000-2010 by Aaron Turner Cache file supported: 04 Not compiled with libdnet. Compiled against libpcap: 1.7.4 64 bit packet counters: enabled Verbose printing via tcpdump: enabled Packet editing: disabled Fragroute engine: disabled Injection method: PF_PACKET send() tcpdump version info tcpdump version 4.9.2 libpcap version 1.7.4 OpenSSL 1.0.2g 1 Mar 2016 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-130-generic 4.4.0-130.156 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: spw3336 F pulseaudio /dev/snd/controlC0: spw3336 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 19 10:30:07 2018 HibernationDevice: RESUME=UUID=032369ab-18b8-41c3-a386-4ed08706f461 InstallationDate: Installed on 2016-11-03 (622 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. OptiPlex 7010 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic root=UUID=7b20f97c-4edc-4af1-bdbb-72ccb26cfbec ro quiet splash intel_iommu=on RelatedPackageVersions: linux-restricted-modules-4.4.0-130-generic N/A linux-backports-modules-4.4.0-130-generic N/A linux-firmware 1.157.20 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0KRC95 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd08/12/2013:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0KRC95:rvrA02:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 7010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782544/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1782608] [NEW] Fresh Ubuntu 18.04 install uses wrong Realtek wired network driver.
Public bug reported: Hi there, Installing Ubuntu 18.04 on my newish laptop which contains a Realtek 8168 NIC seems to use the r8169 driver by default, and should use the r8168 in order to work properly. To fix, I removed or blocked the 8169 driver, installed the 8168 driver and then reconfigured NetworkManager - which was quite difficult for a new user like me. I've included details from my system since I addressed the issue yesterday. Please let me know if there's anything I can do to help more. ~$ lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 ~$ apt-cache policy r8168-dkms r8168-dkms: Installed: 8.045.08-2 Candidate: 8.045.08-2 Version table: *** 8.045.08-2 500 500 http://ca.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 500 http://ca.archive.ubuntu.com/ubuntu bionic/universe i386 Packages 100 /var/lib/dpkg/status ~$ neofetch OS: Ubuntu 18.04 LTS x86_64 Host: Aspire A515-51G V1.10 Kernel: 4.15.0-23-generic Uptime: 30 mins Packages: 2124 Shell: bash 4.4.19 Resolution: 1920x1080 Terminal: gnome-terminal CPU: Intel i5-8250U (8) @ 3.400GHz GPU: Intel UHD Graphics 620 GPU: NVIDIA GeForce MX150 Memory: 3457MiB / 7725MiB ~$ sudo lshw -c network *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0.1 bus info: pci@:02:00.1 logical name: enp2s0f1 version: 12 serial: 98:29:a6:40:b5:f1 size: 10Mbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8168 driverversion=8.045.08-NAPI duplex=half latency=0 link=no multicast=yes port=twisted pair speed=10Mbit/s resources: irq:128 ioport:3000(size=256) memory:a4204000-a4204fff memory:a420-a4203fff ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_23_25_generic_40 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Thu Jul 19 09:56:08 2018 Dependencies: InstallationDate: Installed on 2018-07-16 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1782608 Title: Fresh Ubuntu 18.04 install uses wrong Realtek wired network driver. Status in linux-firmware package in Ubuntu: New Bug description: Hi there, Installing Ubuntu 18.04 on my newish laptop which contains a Realtek 8168 NIC seems to use the r8169 driver by default, and should use the r8168 in order to work properly. To fix, I removed or blocked the 8169 driver, installed the 8168 driver and then reconfigured NetworkManager - which was quite difficult for a new user like me. I've included details from my system since I addressed the issue yesterday. Please let me know if there's anything I can do to help more. ~$ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 ~$ apt-cache policy r8168-dkms r8168-dkms: Installed: 8.045.08-2 Candidate: 8.045.08-2 Version table: *** 8.045.08-2 500 500 http://ca.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 500 http://ca.archive.ubuntu.com/ubuntu bionic/universe i386 Packages 100 /var/lib/dpkg/status ~$ neofetch OS: Ubuntu 18.04 LTS x86_64 Host: Aspire A515-51G V1.10 Kernel: 4.15.0-23-generic Uptime: 30 mins Packages: 2124 Shell: bash 4.4.19 Resolution: 1920x1080 Terminal: gnome-terminal CPU: Intel i5-8250U (8) @ 3.400GHz GPU: Intel UHD Graphics 620 GPU: NVIDIA GeForce MX150 Memory: 3457MiB / 7725MiB ~$ sudo lshw -c network *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0.1 bus info: pci@:02:00.1 logical name: enp2s0f1 version: 12 serial: 98:29:a6:40:b5:f1 size: 10Mbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp 10bt 10bt-fd
[Kernel-packages] [Bug 1780550] Re: No WiFi connection!!!
Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 stable kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15.18/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1780550 Title: No WiFi connection!!! Status in linux package in Ubuntu: Incomplete Bug description: After an update to linux-image-4.15.0-24-generic kernel, my dell laptop lost it's wifi! The wifi does not show up in the settings menu. Although lspci command shows "02:00.0 Network controller: Intel Corporation Wireless 3160 (rev 83)". I am currently booted to old previous kernel linux-image-4.15.0-23-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1778642] Re: ubuntu_lttng_smoke_test failed on Azure 4.15
** Tags added: patch -- 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/1778642 Title: ubuntu_lttng_smoke_test failed on Azure 4.15 Status in lttng-modules: New Status in ubuntu-kernel-tests: Invalid Status in linux-azure package in Ubuntu: Invalid Status in lttng-modules package in Ubuntu: In Progress Status in linux-azure source package in Xenial: Invalid Status in lttng-modules source package in Xenial: In Progress Status in linux-azure source package in Bionic: Invalid Status in lttng-modules source package in Bionic: In Progress Status in linux-azure source package in Cosmic: Invalid Status in lttng-modules source package in Cosmic: In Progress Bug description: ***THIS IS A POTENTIAL REGRESSION*** This test will pass with the older kernel, 4.15.0-1013-azure, but not the 4.15.0-1014-azure in -proposed. It looks like the kernel module can be installed, but four tests have failed: == lttng smoke test of session create/destroy == Session test-kernel-session created. Traces will be written in /tmp/lttng-kernel-trace-14716-session PASSED (lttng create) Session test-kernel-session destroyed PASSED (lttng destroy) == lttng smoke test list kernel events == FAILED (lttng list --kernel) FAILED (lttng list --kernel more output expected) == lttng smoke test trace open/close system calls == Session test-kernel-session created. Traces will be written in /tmp/lttng-kernel-trace-14716-session PASSED (lttng create) FAILED (lttng enable-event) Session test-kernel-session destroyed == lttng smoke test trace context switches == Session test-kernel-session created. Traces will be written in /tmp/lttng-kernel-trace-14716-session PASSED (lttng create) FAILED (lttng enable-event) Session test-kernel-session destroyed Summary: 4 passed, 4 failed http://10.246.72.46/4.15.0-1014.14-azure/bionic-linux-azure- azure-4.15.0-Standard_D12-ubuntu_lttng_smoke_test/ubuntu_lttng_smoke_test/results/ubuntu_lttng_smoke_test .lttng-smoke-test/debug/ubuntu_lttng_smoke_test.lttng-smoke- test.DEBUG.html Error message from /var/log/syslog: kernel: [ 639.531889] PKCS#7 signature not signed with a trusted key kernel: [ 639.538251] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0) kernel: [ 639.538280] lttng_tracer: Unknown symbol lttng_hp_online (err 0) lttng-sessiond[1097]: Error: Unable to load required module lttng-ring-buffer-client-discard lttng-sessiond[1097]: Warning: No kernel tracer available kernel: [ 639.606845] PKCS#7 signature not signed with a trusted key kernel: [ 639.613331] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0) kernel: [ 639.613360] lttng_tracer: Unknown symbol lttng_hp_online (err 0) lttng-sessiond[1097]: Error: Unable to load required module lttng-ring-buffer-client-discard lttng-sessiond[1097]: Warning: No kernel tracer available kernel: [ 639.677124] PKCS#7 signature not signed with a trusted key kernel: [ 639.680857] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0) kernel: [ 639.680886] lttng_tracer: Unknown symbol lttng_hp_online (err 0) lttng-sessiond[1097]: Error: Unable to load required module lttng-ring-buffer-client-discard lttng-sessiond[1097]: Warning: No kernel tracer available kernel: [ 639.737914] PKCS#7 signature not signed with a trusted key kernel: [ 639.753366] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0) kernel: [ 639.753394] lttng_tracer: Unknown symbol lttng_hp_online (err 0) lttng-sessiond[1097]: Error: Unable to load required module lttng-ring-buffer-client-discard lttng-sessiond[1097]: Warning: No kernel tracer available kernel: [ 639.829710] PKCS#7 signature not signed with a trusted key kernel: [ 639.843736] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0) kernel: [ 639.843765] lttng_tracer: Unknown symbol lttng_hp_online (err 0) lttng-sessiond[1097]: Error: Unable to load required module lttng-ring-buffer-client-discard lttng-sessiond[1097]: Warning: No kernel tracer available To manage notifications about this bug go to: https://bugs.launchpad.net/lttng-modules/+bug/1778642/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1778642] Re: ubuntu_lttng_smoke_test failed on Azure 4.15
** Also affects: lttng-modules (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Xenial) Status: New => Invalid ** Changed in: lttng-modules (Ubuntu Xenial) Status: New => In Progress -- 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/1778642 Title: ubuntu_lttng_smoke_test failed on Azure 4.15 Status in lttng-modules: New Status in ubuntu-kernel-tests: Invalid Status in linux-azure package in Ubuntu: Invalid Status in lttng-modules package in Ubuntu: In Progress Status in linux-azure source package in Xenial: Invalid Status in lttng-modules source package in Xenial: In Progress Status in linux-azure source package in Bionic: Invalid Status in lttng-modules source package in Bionic: In Progress Status in linux-azure source package in Cosmic: Invalid Status in lttng-modules source package in Cosmic: In Progress Bug description: ***THIS IS A POTENTIAL REGRESSION*** This test will pass with the older kernel, 4.15.0-1013-azure, but not the 4.15.0-1014-azure in -proposed. It looks like the kernel module can be installed, but four tests have failed: == lttng smoke test of session create/destroy == Session test-kernel-session created. Traces will be written in /tmp/lttng-kernel-trace-14716-session PASSED (lttng create) Session test-kernel-session destroyed PASSED (lttng destroy) == lttng smoke test list kernel events == FAILED (lttng list --kernel) FAILED (lttng list --kernel more output expected) == lttng smoke test trace open/close system calls == Session test-kernel-session created. Traces will be written in /tmp/lttng-kernel-trace-14716-session PASSED (lttng create) FAILED (lttng enable-event) Session test-kernel-session destroyed == lttng smoke test trace context switches == Session test-kernel-session created. Traces will be written in /tmp/lttng-kernel-trace-14716-session PASSED (lttng create) FAILED (lttng enable-event) Session test-kernel-session destroyed Summary: 4 passed, 4 failed http://10.246.72.46/4.15.0-1014.14-azure/bionic-linux-azure- azure-4.15.0-Standard_D12-ubuntu_lttng_smoke_test/ubuntu_lttng_smoke_test/results/ubuntu_lttng_smoke_test .lttng-smoke-test/debug/ubuntu_lttng_smoke_test.lttng-smoke- test.DEBUG.html Error message from /var/log/syslog: kernel: [ 639.531889] PKCS#7 signature not signed with a trusted key kernel: [ 639.538251] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0) kernel: [ 639.538280] lttng_tracer: Unknown symbol lttng_hp_online (err 0) lttng-sessiond[1097]: Error: Unable to load required module lttng-ring-buffer-client-discard lttng-sessiond[1097]: Warning: No kernel tracer available kernel: [ 639.606845] PKCS#7 signature not signed with a trusted key kernel: [ 639.613331] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0) kernel: [ 639.613360] lttng_tracer: Unknown symbol lttng_hp_online (err 0) lttng-sessiond[1097]: Error: Unable to load required module lttng-ring-buffer-client-discard lttng-sessiond[1097]: Warning: No kernel tracer available kernel: [ 639.677124] PKCS#7 signature not signed with a trusted key kernel: [ 639.680857] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0) kernel: [ 639.680886] lttng_tracer: Unknown symbol lttng_hp_online (err 0) lttng-sessiond[1097]: Error: Unable to load required module lttng-ring-buffer-client-discard lttng-sessiond[1097]: Warning: No kernel tracer available kernel: [ 639.737914] PKCS#7 signature not signed with a trusted key kernel: [ 639.753366] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0) kernel: [ 639.753394] lttng_tracer: Unknown symbol lttng_hp_online (err 0) lttng-sessiond[1097]: Error: Unable to load required module lttng-ring-buffer-client-discard lttng-sessiond[1097]: Warning: No kernel tracer available kernel: [ 639.829710] PKCS#7 signature not signed with a trusted key kernel: [ 639.843736] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0) kernel: [ 639.843765] lttng_tracer: Unknown symbol lttng_hp_online (err 0) lttng-sessiond[1097]: Error: Unable to load required module lttng-ring-buffer-client-discard lttng-sessiond[1097]: Warning: No kernel tracer available To manage notifications about this bug go to: https://bugs.launchpad.net/lttng-modules/+bug/1778642/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782184] Re: linux-gcp: 4.15.0-1014.14~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Confirmed ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1782173 phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Thursday, 19. July 2018 16:02 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1782173 - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Thursday, 19. July 2018 16:02 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1782184 Title: linux-gcp: 4.15.0-1014.14~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1782173 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/1782184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782497] Re: linux: 4.4.0-132.158 -proposed tracker
** Summary changed: - linux: -proposed tracker + linux: 4.4.0-132.158 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782497 Title: linux: 4.4.0-132.158 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1782499 (linux-aws), bug 1782500 (linux-lts-xenial) derivatives: bug 1782501 (linux-aws), bug 1782502 (linux-euclid), bug 1782503 (linux-kvm), bug 1782504 (linux-raspi2), bug 1782505 (linux-snapdragon) To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1782497/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773162] Re: 4.15.0-22-generic fails to boot on IBM S822LC (POWER8 (raw), altivec supported)
** Changed in: ubuntu-power-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/1773162 Title: 4.15.0-22-generic fails to boot on IBM S822LC (POWER8 (raw), altivec supported) Status in The Ubuntu-power-systems project: Fix Released Status in debian-installer package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in debian-installer source package in Bionic: Invalid Status in linux source package in Bionic: Fix Released Bug description: Upgrading from 16.04 to 18.04 on a IBM S822LC the system does not boot with 4.15.0-22-generic and is in a reboot cycle. ``` Exiting petitboot. Type 'exit' to return. The system is going down NOW! Sent SIGTERM to all processes Sent SIGKILL to all processes [31775213631,3] OPAL: Trying a CPU re-init with flags: 0x1 [32097001879,3] OPAL: Trying a CPU re-init with flags: 0x2 [2.660186] Bad kernel stack pointer 7fffcd511100 at c000b9ec [2.660382] Oops: Bad kernel stack pointer, sig: 6 [#1] [2.660422] LE SMP NR_CPUS=2048 NUMA PowerNV [2.660462] Modules linked in: [2.660494] CPU: 63 PID: 1201 Comm: modprobe Not tainted 4.15.0-22-generic #24-Ubuntu [2.660549] NIP: c000b9ec LR: CTR: [2.660603] REGS: c0003fd0bd40 TRAP: 0300 Not tainted (4.15.0-22-generic) [2.660657] MSR: 90001031 CR: XER: [2.660713] CFAR: c000b934 DAR: 000200f0 DSISR: 4000 SOFTE: -4611686018408771536 [2.660713] GPR00: 7fffcd511100 [2.660713] GPR04: [2.660713] GPR08: [2.660713] GPR12: 75501b231700 000200f0 [2.660713] GPR16: [2.660713] GPR20: [2.660713] GPR24: [2.660713] GPR28: [2.661203] NIP [c000b9ec] fast_exception_return+0x9c/0x184 [2.661249] LR [] (null) [2.661285] Call Trace: [2.661303] Instruction dump: [2.661331] e84101a0 7c4ff120 e8410170 7c5a03a6 e8010070 e8410080 e8610088 e8810090 [2.661387] e8210078 7db243a6 7db142a6 7c0004ac 63ff 7db242a6 4810 [2.661445] ---[ end trace b607b09fe6490607 ]--- […] ``` Please find the full log attached. Selecting Linux 4.4.0-124-generic works. ``` $ uname -a Linux flughafenberlinbrandenburgwillybrandt 4.4.0-124-generic #148-Ubuntu SMP Wed May 2 13:02:22 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux $ dpkg -l linux-image-4.15.0-22-generic Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-==-==-= ii linux-image-4.15.0-22-generic 4.15.0-22.24 ppc64elSigned kernel image generic $ more /etc/os-release NAME="Ubuntu" VERSION="18.04 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic ``` --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 23 16:40 seq crw-rw 1 root audio 116, 33 May 23 16:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Package: linux (not installed) PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine:
[Kernel-packages] [Bug 1782582] Re: linux-image-generic depends on the proprietary amd64-microcode and intel-microcode
** 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/1782582 Title: linux-image-generic depends on the proprietary amd64-microcode and intel-microcode Status in linux package in Ubuntu: Confirmed Bug description: I'm using Ubuntu 18.10 dev with linux-image-generic 4.17.0.5.8 and the package depends on amd64-microcode and intel-microcode which are proprietary if I'm not wrong. Normally the kernel should run without any microcode updates so it might make sense to move amd64-microcode and intel-microcode from Depends to Recommends to allow users staying on the linux-image-generic metapackage without being required to install proprietary software. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782070] 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 1782070 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-oem in Ubuntu. https://bugs.launchpad.net/bugs/1782070 Title: [Redpine] Upgrades to improve throughput and stability Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: Confirmed Bug description: This is a tracking bug for several improvements for the Redpine RS9113 Wifi+BT combo-device on Dell Edge 300X gateways using Ubuntu 18.04 Server based image. Some of these upgrades are: 1. WoWLAN support from S3/S4 and S5. 2. Better radio throughput 3. Stable operation - fixes to mitigate issues during driver module loading/un-loading - panics when resuming from hibernation These changes have been verified by QA and Dell/ODM. This bug is of tracking purposes only, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782070/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782070] Re: [Redpine] Upgrades to improve throughput and stability
** 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/1782070 Title: [Redpine] Upgrades to improve throughput and stability Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: Confirmed Bug description: This is a tracking bug for several improvements for the Redpine RS9113 Wifi+BT combo-device on Dell Edge 300X gateways using Ubuntu 18.04 Server based image. Some of these upgrades are: 1. WoWLAN support from S3/S4 and S5. 2. Better radio throughput 3. Stable operation - fixes to mitigate issues during driver module loading/un-loading - panics when resuming from hibernation These changes have been verified by QA and Dell/ODM. This bug is of tracking purposes only, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782070/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782582] 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 1782582 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/1782582 Title: linux-image-generic depends on the proprietary amd64-microcode and intel-microcode Status in linux package in Ubuntu: Incomplete Bug description: I'm using Ubuntu 18.10 dev with linux-image-generic 4.17.0.5.8 and the package depends on amd64-microcode and intel-microcode which are proprietary if I'm not wrong. Normally the kernel should run without any microcode updates so it might make sense to move amd64-microcode and intel-microcode from Depends to Recommends to allow users staying on the linux-image-generic metapackage without being required to install proprietary software. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773162] Re: 4.15.0-22-generic fails to boot on IBM S822LC (POWER8 (raw), altivec supported)
** 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/1773162 Title: 4.15.0-22-generic fails to boot on IBM S822LC (POWER8 (raw), altivec supported) Status in The Ubuntu-power-systems project: Fix Committed Status in debian-installer package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in debian-installer source package in Bionic: Invalid Status in linux source package in Bionic: Fix Released Bug description: Upgrading from 16.04 to 18.04 on a IBM S822LC the system does not boot with 4.15.0-22-generic and is in a reboot cycle. ``` Exiting petitboot. Type 'exit' to return. The system is going down NOW! Sent SIGTERM to all processes Sent SIGKILL to all processes [31775213631,3] OPAL: Trying a CPU re-init with flags: 0x1 [32097001879,3] OPAL: Trying a CPU re-init with flags: 0x2 [2.660186] Bad kernel stack pointer 7fffcd511100 at c000b9ec [2.660382] Oops: Bad kernel stack pointer, sig: 6 [#1] [2.660422] LE SMP NR_CPUS=2048 NUMA PowerNV [2.660462] Modules linked in: [2.660494] CPU: 63 PID: 1201 Comm: modprobe Not tainted 4.15.0-22-generic #24-Ubuntu [2.660549] NIP: c000b9ec LR: CTR: [2.660603] REGS: c0003fd0bd40 TRAP: 0300 Not tainted (4.15.0-22-generic) [2.660657] MSR: 90001031 CR: XER: [2.660713] CFAR: c000b934 DAR: 000200f0 DSISR: 4000 SOFTE: -4611686018408771536 [2.660713] GPR00: 7fffcd511100 [2.660713] GPR04: [2.660713] GPR08: [2.660713] GPR12: 75501b231700 000200f0 [2.660713] GPR16: [2.660713] GPR20: [2.660713] GPR24: [2.660713] GPR28: [2.661203] NIP [c000b9ec] fast_exception_return+0x9c/0x184 [2.661249] LR [] (null) [2.661285] Call Trace: [2.661303] Instruction dump: [2.661331] e84101a0 7c4ff120 e8410170 7c5a03a6 e8010070 e8410080 e8610088 e8810090 [2.661387] e8210078 7db243a6 7db142a6 7c0004ac 63ff 7db242a6 4810 [2.661445] ---[ end trace b607b09fe6490607 ]--- […] ``` Please find the full log attached. Selecting Linux 4.4.0-124-generic works. ``` $ uname -a Linux flughafenberlinbrandenburgwillybrandt 4.4.0-124-generic #148-Ubuntu SMP Wed May 2 13:02:22 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux $ dpkg -l linux-image-4.15.0-22-generic Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-==-==-= ii linux-image-4.15.0-22-generic 4.15.0-22.24 ppc64elSigned kernel image generic $ more /etc/os-release NAME="Ubuntu" VERSION="18.04 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic ``` --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 23 16:40 seq crw-rw 1 root audio 116, 33 May 23 16:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Package: linux (not installed) PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine:
[Kernel-packages] [Bug 1782583] Re: package linux-kvm-tools-4.15.0-1008 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.4.15.0-1008', which is also in package l
** Tags removed: need-duplicate-check -- 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/1782583 Title: package linux-kvm-tools-4.15.0-1008 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.4.15.0-1008', which is also in package linux- gcp-tools-4.15.0-1008 4.15.0-1008.8 Status in linux-kvm package in Ubuntu: New Bug description: it just crashed ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-kvm-tools-4.15.0-1008 (not installed) ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_23_25_generic_40 zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Jul 19 09:11:44 2018 DuplicateSignature: package:linux-kvm-tools-4.15.0-1008:(not installed) Unpacking linux-oem-tools-4.15.0-1006 (4.15.0-1006.9) ... dpkg: error processing archive /tmp/apt-dpkg-install-HMrPdr/00-linux-oem-tools-4.15.0-1006_4.15.0-1006.9_amd64.deb (--unpack): trying to overwrite '/usr/lib/libcpupower.so.4.15.0-1006', which is also in package linux-gcp-tools-4.15.0-1006 4.15.0-1006.6 ErrorMessage: trying to overwrite '/usr/lib/libcpupower.so.4.15.0-1008', which is also in package linux-gcp-tools-4.15.0-1008 4.15.0-1008.8 InstallationDate: Installed on 2018-07-18 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.2 SourcePackage: linux-kvm Title: package linux-kvm-tools-4.15.0-1008 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.4.15.0-1008', which is also in package linux-gcp-tools-4.15.0-1008 4.15.0-1008.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1782583/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782583] [NEW] package linux-kvm-tools-4.15.0-1008 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.4.15.0-1008', which is also in package
Public bug reported: it just crashed ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-kvm-tools-4.15.0-1008 (not installed) ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_23_25_generic_40 zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Jul 19 09:11:44 2018 DuplicateSignature: package:linux-kvm-tools-4.15.0-1008:(not installed) Unpacking linux-oem-tools-4.15.0-1006 (4.15.0-1006.9) ... dpkg: error processing archive /tmp/apt-dpkg-install-HMrPdr/00-linux-oem-tools-4.15.0-1006_4.15.0-1006.9_amd64.deb (--unpack): trying to overwrite '/usr/lib/libcpupower.so.4.15.0-1006', which is also in package linux-gcp-tools-4.15.0-1006 4.15.0-1006.6 ErrorMessage: trying to overwrite '/usr/lib/libcpupower.so.4.15.0-1008', which is also in package linux-gcp-tools-4.15.0-1008 4.15.0-1008.8 InstallationDate: Installed on 2018-07-18 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.2 SourcePackage: linux-kvm Title: package linux-kvm-tools-4.15.0-1008 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.4.15.0-1008', which is also in package linux-gcp-tools-4.15.0-1008 4.15.0-1008.8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic package-conflict -- 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/1782583 Title: package linux-kvm-tools-4.15.0-1008 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.4.15.0-1008', which is also in package linux- gcp-tools-4.15.0-1008 4.15.0-1008.8 Status in linux-kvm package in Ubuntu: New Bug description: it just crashed ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-kvm-tools-4.15.0-1008 (not installed) ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_23_25_generic_40 zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Jul 19 09:11:44 2018 DuplicateSignature: package:linux-kvm-tools-4.15.0-1008:(not installed) Unpacking linux-oem-tools-4.15.0-1006 (4.15.0-1006.9) ... dpkg: error processing archive /tmp/apt-dpkg-install-HMrPdr/00-linux-oem-tools-4.15.0-1006_4.15.0-1006.9_amd64.deb (--unpack): trying to overwrite '/usr/lib/libcpupower.so.4.15.0-1006', which is also in package linux-gcp-tools-4.15.0-1006 4.15.0-1006.6 ErrorMessage: trying to overwrite '/usr/lib/libcpupower.so.4.15.0-1008', which is also in package linux-gcp-tools-4.15.0-1008 4.15.0-1008.8 InstallationDate: Installed on 2018-07-18 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.2 SourcePackage: linux-kvm Title: package linux-kvm-tools-4.15.0-1008 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.4.15.0-1008', which is also in package linux-gcp-tools-4.15.0-1008 4.15.0-1008.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1782583/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782582] Re: linux-image-generic depends on the proprietary amd64-microcode and intel-microcode
** Package changed: linux-meta (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782582 Title: linux-image-generic depends on the proprietary amd64-microcode and intel-microcode Status in linux package in Ubuntu: New Bug description: I'm using Ubuntu 18.10 dev with linux-image-generic 4.17.0.5.8 and the package depends on amd64-microcode and intel-microcode which are proprietary if I'm not wrong. Normally the kernel should run without any microcode updates so it might make sense to move amd64-microcode and intel-microcode from Depends to Recommends to allow users staying on the linux-image-generic metapackage without being required to install proprietary software. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767180] Re: Bluetooth of the Asus Maximus X Hero Wifi AC motherboard doesnt work using the Realtek 8822BE driver
Ok so I tried looking back until I found the last working update. It was kernel version 4.16.12. When I installed 4.16.11 bluetooth appears as disabled and doesn't work. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767180 Title: Bluetooth of the Asus Maximus X Hero Wifi AC motherboard doesnt work using the Realtek 8822BE driver Status in linux package in Ubuntu: Incomplete Bug description: What you expected to happen For the Asus Maximus X Hero Wifi AC motherboards' bluetooth to work What happened instead Bluetooth does not work lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 My custom computer uses an Asus Maximus X Hero Wifi AC motherboard, which uses the Realtek 8822BE driver to cotrol wifi and bluetooth. Support for this driver was added on kernel 4.14, however only wifi works. Bluetooth appears as disabled on the Bluetooth adapters program, but on rfkill it is not blocked, and it is not disabled on the motherboards' settings. This was tested on an Ubuntu-Mate 18.04 Beta 2, Ubuntu 16.04LTS and Ubuntu 17.10 using kernel 4.15. Tried 4.16 just in case, but it didn't work. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: azul 1431 F pulseaudio /dev/snd/controlC0: azul 1431 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-08 (18 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=d3f1f2d4-b9ff-4e28-b840-fe563d5df18d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 StagingDrivers: r8822be Tags: bionic staging Uname: Linux 4.15.0-20-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/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: Default string dmi.board.name: ROG MAXIMUS X HERO (WI-FI AC) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/09/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGMAXIMUSXHERO(WI-FIAC):rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767180/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782186] Re: linux-azure: 4.15.0-1018.18~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => 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/1782186 Title: linux-azure: 4.15.0-1018.18~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1782173 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1782186/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782582] [NEW] linux-image-generic depends on the proprietary amd64-microcode and intel-microcode
Public bug reported: I'm using Ubuntu 18.10 dev with linux-image-generic 4.17.0.5.8 and the package depends on amd64-microcode and intel-microcode which are proprietary if I'm not wrong. Normally the kernel should run without any microcode updates so it might make sense to move amd64-microcode and intel-microcode from Depends to Recommends to allow users staying on the linux-image-generic metapackage without being required to install proprietary software. ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New ** Summary changed: - * + linux-image-generic depends on the proprietary amd64-microcode and intel-microcode ** Description changed: - * + I'm using Ubuntu 18.10 dev with linux-image-generic 4.17.0.5.8 and the + package depends on amd64-microcode and intel-microcode which are + proprietary if I'm not wrong. Normally the kernel should run without any + microcode updates so it might make sense to move amd64-microcode and + intel-microcode from Depends to Recommends to allow users staying on the + linux-image-generic metapackage without being required to install + proprietary software. ** Package changed: ubuntu => linux-meta (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1782582 Title: linux-image-generic depends on the proprietary amd64-microcode and intel-microcode Status in linux-meta package in Ubuntu: New Bug description: I'm using Ubuntu 18.10 dev with linux-image-generic 4.17.0.5.8 and the package depends on amd64-microcode and intel-microcode which are proprietary if I'm not wrong. Normally the kernel should run without any microcode updates so it might make sense to move amd64-microcode and intel-microcode from Depends to Recommends to allow users staying on the linux-image-generic metapackage without being required to install proprietary software. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1782582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782582] [NEW] linux-image-generic depends on the proprietary amd64-microcode and intel-microcode
You have been subscribed to a public bug: I'm using Ubuntu 18.10 dev with linux-image-generic 4.17.0.5.8 and the package depends on amd64-microcode and intel-microcode which are proprietary if I'm not wrong. Normally the kernel should run without any microcode updates so it might make sense to move amd64-microcode and intel-microcode from Depends to Recommends to allow users staying on the linux-image-generic metapackage without being required to install proprietary software. ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New -- linux-image-generic depends on the proprietary amd64-microcode and intel-microcode https://bugs.launchpad.net/bugs/1782582 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1777194] Comment bridged from LTC Bugzilla
--- Comment From hasri...@in.ibm.com 2018-07-19 09:54 EDT---
(In reply to comment #40)
> I just confirmed the two requested patches are in the Ubuntu-4.15.0-29
> kernel:
> eeada334156f powerpc: use NMI IPI for smp_send_stop
> 4190e27bf0ee powerpc: Fix smp_send_stop NMI IPI handling
>
> Can you confirm the kernel posted in comment #5 fixes this bug on the same
> machine?
As this is observed on Tuleta, i am not able to boot this kernel even
after I used "apt-setup/proposed=true" while booting. Can you build a
deb with the same?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1777194
Title:
Hard LOCKUP observed on stressing Ubuntu 18 04
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
IBM has seen hard lockups when running stress tests against Bionic.
These test sometimes lead to rcu_stalls. IBM found that this bug is
resolved with commits 6bed3237624e and ac61c1156623.
== Fixes ==
6bed3237624e ("powerpc: use NMI IPI for smp_send_stop")
ac61c1156623 ("powerpc: Fix smp_send_stop NMI IPI handling")
== Regression Potential ==
Low. Limited to powerpc.
== Test Case ==
A test kernel was built with these patches and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
--Problem Description--
Hard LOCKUP on stressing Ubuntu 18 04
---Issue observed---
Hard LOCKUP on stressing Ubuntu 18 04 using Ubuntu 18 04, sometimes leads to
rcu_stalls.
Apr 17 00:00:23 lep8d kernel: [ 4309.786755] Watchdog CPU:3 Hard LOCKUP
Apr 17 00:00:23 lep8d kernel: [ 4309.786759] Modules linked in: algif_rng
salsa20_generic userio camellia_generic cast6_generic cast_common snd_seq
snd_seq_device snd_timer snd soundcore vhost_net serpent_generic tap
twofish_generic twofish_common vhost_vsock vmw_vsock_virtio_transport_common
vhost vsock lrw unix_diag algif_skcipher cuse sctp tgr192 wp512 rmd320 rmd256
rmd160 hci_vhci rmd128 bluetooth ecdh_generic dccp_ipv4 md4 uhid hid algif_hash
dccp af_alg xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4
iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack
nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc
ebtable_filter ebtables devlink ip6table_filter ip6_tables iptable_filter
kvm_hv kvm binfmt_misc uio_pdrv_genirq uio vmx_crypto ibmpowernv
powernv_op_panel ipmi_powernv
Apr 17 00:00:23 lep8d kernel: [ 4309.786899] ipmi_devintf ipmi_msghandler
powernv_rng leds_powernv crct10dif_vpmsum sch_fq_codel ip_tables x_tables
autofs4 ses enclosure scsi_transport_sas btrfs xor zstd_compress raid6_pq uas
usb_storage crc32c_vpmsum tg3 ipr
Apr 17 00:00:23 lep8d kernel: [ 4309.786944] CPU: 3 PID: 28361 Comm:
stress-ng-hrtim Not tainted 4.15.0-15-generic #16-Ubuntu
Apr 17 00:00:23 lep8d kernel: [ 4309.786950] NIP: c0d0c8b8 LR:
c0120dbc CTR: c0024480
Apr 17 00:00:23 lep8d kernel: [ 4309.786956] REGS: c7f7fd80 TRAP:
0900 Not tainted (4.15.0-15-generic)
Apr 17 00:00:23 lep8d kernel: [ 4309.786957] MSR: 90009033
CR: 28000442 XER: 2000
Apr 17 00:00:23 lep8d kernel: [ 4309.786972] CFAR: c0120db8 SOFTE: 0
Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR00: c0120dbc
c02d51377ba0 c16eb400 c02d512b0f88
Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR04:
0001 01f40668 0001
Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR08: 0001
8003
Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR12: c0024480
c7a22100 000186a0
Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR16: 7fffed3687e0
0abda98e5db8 8005 00040100
Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR20:
418004fc 003c 0843
Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR24: c02d512b0f88
c02d51377d30 c02d52d47c00
Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR28: c02d51377d50
c02d51377d50 c02d52f04500 c02d512b0f88
Apr 17 00:00:23 lep8d kernel: [ 4309.787035] NIP [c0d0c8b8]
_raw_spin_lock+0x38/0xe0
Apr 17 00:00:23 lep8d kernel: [ 4309.787045] LR [c0120dbc]
dequeue_signal+0xcc/0x260
Apr 17 00:00:23 lep8d kernel: [ 4309.787046] Call Trace:
Apr 17 00:00:23 lep8d kernel: [ 4309.787052] [c02d51377bd0]
[c0120dac] dequeue_signal+0xbc/0x260
Apr 17 00:00:23 lep8d kernel: [ 4309.787059] [c02d51377c20]
[c012459c] get_signal+0x13c/0x7a0
Apr 17 00:00:23 lep8d kernel: [ 4309.787066] [c02d51377d10]
[Kernel-packages] [Bug 1745899] Re: [Bug][KVM][Crystal Ridge] Terrible performance of vNVDIMM on QEMU with device DAX backend
** Changed in: intel Status: New => 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/1745899 Title: [Bug][KVM][Crystal Ridge] Terrible performance of vNVDIMM on QEMU with device DAX backend Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Description: When device DAX (e.g., /dev/daxX.Y) is used as QEMU vNVDIMM backend, its performance in guest is far behind the performance on bare metal. Commit Ids: aa2e063aea79 b8d7044bcff7 (which is in KVM branch instead of mainline kernel) Target kernel:4.16 Target Release:18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1745899/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1778891] 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 1778891 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: 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/1778891 Title: KVM Instance booting from volume stacktraces Status in cloud-init: Invalid Status in cloud-init package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Bug description: I've booted two instances from the same backing image (http://cloud- images.ubuntu.com/trusty/current/trusty-server-cloudimg- amd64-disk1.img), one using locally attached storage for the boot volume, one using a Cinder volume. The instance booted from cinder volume shows a cloud-init trace in the console log, while the local instance works correctly. Instance booted from volume: Cloud-init v. 0.7.5 running 'init' at Wed, 27 Jun 2018 09:43:10 +. Up 15.61 seconds. ci-info: ++Net device info+++ ci-info: ++--+--+---+---+ ci-info: | Device | Up | Address| Mask | Hw-Address| ci-info: ++--+--+---+---+ ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | . | ci-info: | eth0 | True | 192.168.21.8 | 255.255.255.0 | fa:16:3e:aa:c3:54 | ci-info: ++--+--+---+---+ ci-info: +++Route info+++ ci-info: +---+-+--+-+---+---+ ci-info: | Route | Destination | Gateway| Genmask | Interface | Flags | ci-info: +---+-+--+-+---+---+ ci-info: | 0 | 0.0.0.0 | 192.168.21.1 | 0.0.0.0 |eth0 | UG | ci-info: | 1 | 169.254.169.254 | 192.168.21.1 | 255.255.255.255 |eth0 | UGH | ci-info: | 2 | 192.168.21.0 | 0.0.0.0| 255.255.255.0 |eth0 | U | ci-info: +---+-+--+-+---+---+ dmesg: write failed: Broken pipe Generating public/private rsa key pair. Your identification has been saved in /etc/ssh/ssh_host_rsa_key. Your public key has been saved in /etc/ssh/ssh_host_rsa_key.pub. The key fingerprint is: c7:fb:76:96:ae:aa:6e:73:b1:28:ea:38:40:fa:34:75 root@20180627093956 The key's randomart image is: +--[ RSA 2048]+ | | | | | | | . . E . | |o . . S o | |o o ... | | + . ..o . |[ 36.260523] general protection fault: [#1] SMP [ 36.260523] Modules linked in: dm_crypt kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel serio_raw aesni_intel aes_x86_64 glue_helper lrw gf128mul ablk_helper cryptd psmouse floppy [ 36.260523] CPU: 0 PID: 1 Comm: init Not tainted 3.13.0-151-generic #201-Ubuntu [ 36.260523] Hardware name: OpenStack Foundation OpenStack Nova, BIOS 1.10.2-1ubuntu1~cloud0 04/01/2014 [ 36.260523] task: 88007c088000 ti: 88007c086000 task.ti: 88007c086000 [ 36.260523] RIP: 0010:[] [] switch_mm_irqs_off+0xbb/0x120 [ 36.260523] RSP: 0018:88007c087ee0 EFLAGS: 00010046 [ 36.260523] RAX: 0001 RBX: 880037a54700 RCX: 0049 [ 36.260523] RDX: RSI: 880037a54700 RDI: 880037a54700 [ 36.260523] RBP: 88007c087f00 R08: R09: [ 36.260523] R10: 0001 R11: 88007b666780 R12: 8800378d6700 [ 36.260523] R13: R14: 880037653000 R15: 880037653000 [ 36.260523] FS: 7f81d6e9a840() GS:88007fc0() knlGS: [ 36.260523] CS: 0010 DS: ES: CR0: 80050033 [ 36.260523] CR2: 7ffcc8f0fec0 CR3: 37924000 CR4: 00360670 [ 36.260523] DR0: DR1: DR2: [ 36.260523] DR3: DR6: fffe0ff0 DR7: 0400 [ 36.260523] Stack: [ 36.260523] 8800378d6700 88007fc13b40 880037a54700 [ 36.260523] 88007c087f60 8173c613 88007c088000
[Kernel-packages] [Bug 1778891] Re: KVM Instance booting from volume stacktraces
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-init Status: New => Invalid ** Changed in: cloud-init (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1778891 Title: KVM Instance booting from volume stacktraces Status in cloud-init: Invalid Status in cloud-init package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Bug description: I've booted two instances from the same backing image (http://cloud- images.ubuntu.com/trusty/current/trusty-server-cloudimg- amd64-disk1.img), one using locally attached storage for the boot volume, one using a Cinder volume. The instance booted from cinder volume shows a cloud-init trace in the console log, while the local instance works correctly. Instance booted from volume: Cloud-init v. 0.7.5 running 'init' at Wed, 27 Jun 2018 09:43:10 +. Up 15.61 seconds. ci-info: ++Net device info+++ ci-info: ++--+--+---+---+ ci-info: | Device | Up | Address| Mask | Hw-Address| ci-info: ++--+--+---+---+ ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | . | ci-info: | eth0 | True | 192.168.21.8 | 255.255.255.0 | fa:16:3e:aa:c3:54 | ci-info: ++--+--+---+---+ ci-info: +++Route info+++ ci-info: +---+-+--+-+---+---+ ci-info: | Route | Destination | Gateway| Genmask | Interface | Flags | ci-info: +---+-+--+-+---+---+ ci-info: | 0 | 0.0.0.0 | 192.168.21.1 | 0.0.0.0 |eth0 | UG | ci-info: | 1 | 169.254.169.254 | 192.168.21.1 | 255.255.255.255 |eth0 | UGH | ci-info: | 2 | 192.168.21.0 | 0.0.0.0| 255.255.255.0 |eth0 | U | ci-info: +---+-+--+-+---+---+ dmesg: write failed: Broken pipe Generating public/private rsa key pair. Your identification has been saved in /etc/ssh/ssh_host_rsa_key. Your public key has been saved in /etc/ssh/ssh_host_rsa_key.pub. The key fingerprint is: c7:fb:76:96:ae:aa:6e:73:b1:28:ea:38:40:fa:34:75 root@20180627093956 The key's randomart image is: +--[ RSA 2048]+ | | | | | | | . . E . | |o . . S o | |o o ... | | + . ..o . |[ 36.260523] general protection fault: [#1] SMP [ 36.260523] Modules linked in: dm_crypt kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel serio_raw aesni_intel aes_x86_64 glue_helper lrw gf128mul ablk_helper cryptd psmouse floppy [ 36.260523] CPU: 0 PID: 1 Comm: init Not tainted 3.13.0-151-generic #201-Ubuntu [ 36.260523] Hardware name: OpenStack Foundation OpenStack Nova, BIOS 1.10.2-1ubuntu1~cloud0 04/01/2014 [ 36.260523] task: 88007c088000 ti: 88007c086000 task.ti: 88007c086000 [ 36.260523] RIP: 0010:[] [] switch_mm_irqs_off+0xbb/0x120 [ 36.260523] RSP: 0018:88007c087ee0 EFLAGS: 00010046 [ 36.260523] RAX: 0001 RBX: 880037a54700 RCX: 0049 [ 36.260523] RDX: RSI: 880037a54700 RDI: 880037a54700 [ 36.260523] RBP: 88007c087f00 R08: R09: [ 36.260523] R10: 0001 R11: 88007b666780 R12: 8800378d6700 [ 36.260523] R13: R14: 880037653000 R15: 880037653000 [ 36.260523] FS: 7f81d6e9a840() GS:88007fc0() knlGS: [ 36.260523] CS: 0010 DS: ES: CR0: 80050033 [ 36.260523] CR2: 7ffcc8f0fec0 CR3: 37924000 CR4: 00360670 [ 36.260523] DR0: DR1: DR2: [ 36.260523] DR3: DR6: fffe0ff0 DR7: 0400 [ 36.260523] Stack: [ 36.260523] 8800378d6700 88007fc13b40 880037a54700 [ 36.260523] 88007c087f60 8173c613 88007c088000 00013b40 [ 36.260523] 88007c087fd8 00013b40 88007c088000 7ffcc8f10ae0 [ 36.260523] Call Trace: [ 36.260523] [] __schedule+0x2b3/0x750 [ 36.260523] [] schedule_user+0x2e/0xa0 [ 36.260523] [] sysret_careful+0x14/0x1a [ 36.260523] Code: 24 e0 02 00 00 75 28 5b 41 5c 41 5d 41 5e 5d c3 48 8b 05 a5 58 cb 00 48 c1 e8 33 a8 01 74 d7 31 d2 b8 01 00 00 00 b9 49 00 00 00 <0f> 30 eb c7
[Kernel-packages] [Bug 1577140] Re: Wifi Ralink R3290 disabled by default in ubuntu 16.04
Vipan - If you are live booting Ubuntu 18.04 please boot the live USB after you have turned off your machine completely. If you boot Live ubuntu 18.04 after restarting your machine from the previous Ubuntu version (where WIFI doesn't work) release then the WIFI will not work in Live mode. It's kind of weird but that's how it works in my case. In short, To test your WIFI do not boot into Previous ubuntu release (which is installed on your computer). If somehow you have logged in Previous Ubuntu then shut down the Ubuntu and then boot into LIVE USB directly. It would show up your WIFI device. If it doesn't show up then there could be something messing up with your kernel module. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1577140 Title: Wifi Ralink R3290 disabled by default in ubuntu 16.04 Status in linux package in Ubuntu: Fix Released Bug description: I have my personal laptop and it contains PCI Ralink r3290 wifi adaptor with bluetooth and when i have installed the fresh version of Ubuntu 16.04x64 it doesn’t work at all on boot up. The wifi is disabled by default and the it doesn’t activates even by pressing the key and when i go the network settings airplane mode is also enabled and when i try to disable airplane mode it switches back on. I dont know whats going wrong. Earlier my wifi works on ubuntu 15.04. I have tried almost every solution and none works in the latest LTS release. Please help I am unable to use internet in ubuntu ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: boot/vmlinuz-4.4.0-21-generic] ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shankey1536 F pulseaudio /dev/snd/controlC1: shankey1536 F pulseaudio CurrentDesktop: Unity Date: Sun May 1 17:02:12 2016 HibernationDevice: RESUME=UUID=9fdda691-a6ae-4494-99e3-b76fde1f33a6 InstallationDate: Installed on 2016-04-24 (7 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 001 Device 003: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd (Foxlink) Webcam 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 Compaq 15 Notebook PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=609ae58a-a43f-4f7b-9a61-e21d3caf457a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.39 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2211 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.52 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.39:bd05/26/2015:svnHewlett-Packard:pnCompaq15NotebookPC:pvr0991100600087:rvnHewlett-Packard:rn2211:rvr86.52:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: Compaq 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/1577140/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782184] Re: linux-gcp: 4.15.0-1014.14~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1782184 Title: linux-gcp: 4.15.0-1014.14~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1782173 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1782184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782181] Re: linux-oem: 4.15.0-1012.15 -proposed tracker
** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => Invalid -- 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/1782181 Title: linux-oem: 4.15.0-1012.15 -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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1782173 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/1782181/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782186] Re: linux-azure: 4.15.0-1018.18~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1782173 phase: Packaging + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Thursday, 19. July 2018 13:32 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1782173 - phase: Packaging - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Thursday, 19. July 2018 13:32 UTC + phase: Uploaded -- 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/1782186 Title: linux-azure: 4.15.0-1018.18~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1782173 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1782186/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782557] Re: linux-gcp: add a signed kernel
** Also affects: linux-gcp (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1782557 Title: linux-gcp: add a signed kernel Status in linux-gcp package in Ubuntu: Confirmed Status in linux-gcp source package in Bionic: New Bug description: We need the kernel binaries to be signed. Switch this on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1782557/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782178] Re: linux-azure: 4.15.0-1018.18 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1782173 phase: Packaging + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Thursday, 19. July 2018 13:01 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1782173 - phase: Packaging - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Thursday, 19. July 2018 13:01 UTC + phase: Uploaded -- 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/1782178 Title: linux-azure: 4.15.0-1018.18 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1782173 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1782178/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782184] Re: linux-gcp: 4.15.0-1014.14~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-xenial ** Tags added: block-proposed ** Description changed: This bug 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: 1782173 phase: Uploaded -- 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/1782184 Title: linux-gcp: 4.15.0-1014.14~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1782173 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1782184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782186] Re: linux-azure: 4.15.0-1018.18~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1782186 Title: linux-azure: 4.15.0-1018.18~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1782173 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1782186/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
