[Kernel-packages] [Bug 1814757] Re: linux-aws: 4.18.0-1011.13 -proposed tracker
4.18.0-1011.13 - aws Regression test CMPL, RTB. Issue to note in arm64 (aws): ubuntu_kernel_selftests - msg_zerocopy in net (bug 1812620) test_bpf in net (bug 1812189) RTNETLINK in net (bug 1812194) fib related test in net (bug 1812622) ubuntu_ltp - test disabled ubuntu_ltp_syscalls - fanotify case 2 (bug 1804594) msgstress03 (bug 1783881) sync_file_range02 (bug 1819116) getrandom02 (bug 1797327) Issue to note in x86_64 (aws): ubuntu_kernel_selftests - msg_zerocopy in net (bug 1812620) test_bpf in net (bug 1812189) RTNETLINK in net (bug 1812194) fib related test in net (bug 1812622) ubuntu_ltp - test disabled ubuntu_ltp_syscalls - fanotify case 2 (bug 1804594) sync_file_range02 (bug 1819116) Skipped / blacklisted: * libhugetlbfs * ubuntu_quota_smoke_test * ubuntu_seccomp * ubuntu_zram_smoke_test ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- 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/1814757 Title: linux-aws: 4.18.0-1011.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1814749 phase: Ready for Testing phase-changed: Sunday, 10. March 2019 12:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814757/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817848] Re: i915: Backport watermark fixes for gen9+
** Tags added: originate-from-1810272 somerville -- 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/1817848 Title: i915: Backport watermark fixes for gen9+ Status in HWE Next: New Status in linux-oem package in Ubuntu: Confirmed Status in linux-oem source package in Bionic: Confirmed Bug description: [Impact] 5.0 fixes screen flicker issues with new panel models and on hybrid machines, and Intel has prepared a backport for 4.15 which we can use. It consists of 50+ cherry-picked commits plus a handful of build fixes: git://github.com/vsyrjala/linux.git skl_wm_backport_4.15 [Test case] Various display configurations with an external monitor connected need to be tested, preferably on a wider set of hardware [Regression potential] The backport was done by Intel, and tested with intel-gpu-tools to do the right thing, but there's always a chance of regressing something. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1817848/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782209] 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 1782209 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: disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782209 Title: KVM SnowRidge Split-lock disable Status in linux package in Ubuntu: Incomplete Status in qemu package in Ubuntu: New Bug description: When bit 29 is set in Test Control MSR register 0x33, a #AC execption is generated for split locked accesses at all CPL irrespective of CR0.AM or EFLAGS.AC. This feature can help developers to capture memory accesses that across cachelines with #LOCK assertion. Then developers can reconstruct their program accordingly Upstream target linux 5.2 Target Release: 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782209/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782209] Re: KVM SnowRidge Split-lock disable
My questions in comment #1 where no answered directly yet, but this still is using only kernel patches so far, I think it is time to add at least a kernel task. Furthermore it isn't upstream yet and the target being 5.2 is a bit out still, so I'd think you should target 19.10 ** 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/1782209 Title: KVM SnowRidge Split-lock disable Status in linux package in Ubuntu: Incomplete Status in qemu package in Ubuntu: New Bug description: When bit 29 is set in Test Control MSR register 0x33, a #AC execption is generated for split locked accesses at all CPL irrespective of CR0.AM or EFLAGS.AC. This feature can help developers to capture memory accesses that across cachelines with #LOCK assertion. Then developers can reconstruct their program accordingly Upstream target linux 5.2 Target Release: 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782209/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819486] Re: Crash from :i915 module with 4.15.0-46-generic using multi-display
Please test this kernel: https://people.canonical.com/~khfeng/lp1819486/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819486 Title: Crash from :i915 module with 4.15.0-46-generic using multi-display Status in linux package in Ubuntu: Confirmed Bug description: While previously working using 4.15.0-45-generic, booting my thinkpad T480 on a dock with additional screen connected and "kernel 4.15.0-46-generic" lead to a crash of the system. Laptop is running Ubuntu 18.04.2 LTS. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: user 3449 F...m pulseaudio /dev/snd/controlC1: user 3449 F pulseaudio /dev/snd/pcmC0D0p: user 3449 F...m pulseaudio /dev/snd/controlC0: user 3449 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7 InstallationDate: Installed on 2018-06-28 (256 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20L5000AFR Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin netdev plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET37W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5000AFR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L5000AFR:pvrThinkPadT480:rvnLENOVO:rn20L5000AFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5000AFR dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819486/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805152] Re: touchpad not working on 18.04
[9.435425] cannonlake-pinctrl INT3450:00: pin 208 cannot be used as IRQ [9.435427] genirq: Setting trigger mode 8 for irq 132 failed (intel_gpio_irq_type+0x0/0x140) [9.436232] i2c_hid i2c-UNIW0001:00: Could not register for UNIW0001:00 interrupt, irq = 132, ret = -1 [9.436286] i2c_hid: probe of i2c-UNIW0001:00 failed with error -1 ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1805152 Title: touchpad not working on 18.04 Status in linux package in Ubuntu: Fix Released Bug description: hi, new laptop, new 18.04 installation on dual system touchpad had never worked under ubuntu - works ok under WIN10 debug files attached thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805152/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815957] Re: SynPS/2 Synaptics TouchPad: Read error 19
** Changed in: libinput (Ubuntu) Status: New => Incomplete ** Changed in: xserver-xorg-input-libinput (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/1815957 Title: SynPS/2 Synaptics TouchPad: Read error 19 Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: Incomplete Bug description: Hi Ubuntu 18.04 went into standby mode with the mouse plugged in. Then I've removed the mouse. A few hours later I wanted to continue work (without mouse) and woke up my PC from standby mode. Unfortunately the touchpad did not work. So I put Ubuntu back into standby mode, plugged in a mouse and woke it up again. Both Touchpad and mouse worked perfectly again. Regards, Ettore Atalan --- ProblemType: Bug .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben7239 F pulseaudio CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2018-07-29 21:59:28,715 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: tuxedo-wmi, 1.5.1, 3.13.0-24-generic, x86_64: built tuxedo-wmi, 1.5.1, 4.15.0-44-generic, x86_64: installed tuxedo-wmi, 1.5.1, 4.15.0-45-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6507] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 5986:055c Acer, Inc Bus 001 Device 002: ID 046d:c245 Logitech, Inc. G400 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook W65_W67RZ Package: xserver-xorg-input-libinput 0.27.1-1 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=462560f8-ccdb-4115-a3c9-46fce6a630d2 ro rw quiet splash acpi_os_name=Linux acpi_osi= acpi_backlight=vendor vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic ubuntu ubuntu Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-29 (204 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.09 dmi.board.asset.tag: Tag 12345 dmi.board.name: W65_W67RZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.09:bd05/27/2016:svnNotebook:pnW65_W67RZ:pvrNotApplicable:rvnNotebook:rnW65_W67RZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W65_W67RZ dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Jan 21 20:00:45 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1815957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798615] Re: suspend does not lock in 18.04
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798615 Title: suspend does not lock in 18.04 Status in linux package in Ubuntu: Expired Bug description: To reproduce from the command-line (this is ubuntu 18.04): % gsettings set org.gnome.desktop.screensaver ubuntu-lock-on-suspend true % gsettings get org.gnome.desktop.screensaver ubuntu-lock-on-suspend true % systemctl suspend Now the monitors go black and report "no signal" (good), and it will stay that way for hours (good) ... but if I tap "shift" key a few times, Ubuntu 18.04 comes back without asking my password. (I expected rather that the system would be locked, i.e. I should see a dialog box that would require a password before anything else!) Same thing if I suspend by using the upper-right-of-screen "power" icon (click-and-hold, then click on the suspend icon). Same thing if I let 20 minutes go by. (A msg comes up ~~ "system will suspend soon...", and it does suspend, but doesn't lock). I have left the ubuntu-lock-on-suspend setting at "true" through several re-boots, but it still doesn't take effect. I get the same behavior whether ubuntu-lock-on-suspend is set to "true" or "false". Other info: % wmctrl -m Name: GNOME Shell Class: N/A PID: N/A Window manager's "showing the desktop" mode: N/A % lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.1 LTS Release:18.04 Codename: bionic % uname -a Linux ucbvax 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux I just upgraded from 16.04 a couple of weeks ago. I think (90%) it was locking in 16.04, but now not locking in 18.04. If I click on the upper-right-of-screen padlock icon, then the system does lock (password required). While it's locked in that way, I can click on the upper-right-of- screen "suspend" (from drop-down), and then my system is both suspended and locked. But the question is ... How can I make my system lock (automatically) every time a "suspend" happens? (Or even "every time kbd and mouse are idle for 15 minutes"?) Please advise. thanks --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 7633 F pulseaudio /dev/snd/controlC1: ubuntu 7633 F pulseaudio CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IwConfig: enp2s0no wireless extensions. enp7s5no wireless extensions. lono wireless extensions. LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: To be filled by O.E.M. To be filled by O.E.M. Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.173.1 RfKill: Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/23/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0705 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A99X EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0705:bd08/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A99XEVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798615/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811255] Re: perf archive missing
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811255 Title: perf archive missing Status in linux package in Ubuntu: Expired Bug description: Running perf in 16.04 returns: `` usage: perf [--version] [--help] [OPTIONS] COMMAND [ARGS] The most commonly used perf commands are: annotateRead perf.data (created by perf record) and display annotated code archive Create archive with object files with build-ids found in perf.data file ... ``` ``` perf version 4.15.18 ``` However `perf archive` returns: ``` perf: 'archive' is not a perf-command. See 'perf --help'. ``` It appears that the archive script is somehow missing from the package. Similar reports can be seen here: * https://stackoverflow.com/questions/42150355/how-do-i-use-a-newer-perf-tool-front-end-with-a-record-from-an-older-perf-versio * https://www.spinics.net/lists/linux-perf-users/msg01294.html Description: Ubuntu 16.04.5 LTS Release: 16.04 linux-tools-4.15.0-43-generic: Installed: 4.15.0-43.46~16.04.1 Candidate: 4.15.0-43.46~16.04.1 Version table: *** 4.15.0-43.46~16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811255/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805152] Re: touchpad not working on 18.04
Oh please ignore my comment in #8, seems that you have verified this with 4.20rc4. Do you mind test it again with the latest 5.0 kernel? https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0.1/ And please attach the dmesg output when booting with 5.0.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1805152 Title: touchpad not working on 18.04 Status in linux package in Ubuntu: Incomplete Bug description: hi, new laptop, new 18.04 installation on dual system touchpad had never worked under ubuntu - works ok under WIN10 debug files attached thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805152/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805152] Re: touchpad not working on 18.04
Mark this as Incomplete for the request in comment #7 ** 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/1805152 Title: touchpad not working on 18.04 Status in linux package in Ubuntu: Incomplete Bug description: hi, new laptop, new 18.04 installation on dual system touchpad had never worked under ubuntu - works ok under WIN10 debug files attached thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805152/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810130] Re: ic2-HTIX5288
Mark this Incomplete for the request in #12 ** 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/1810130 Title: ic2-HTIX5288 Status in linux package in Ubuntu: Incomplete Bug description: touchpad not working Ubuntu Disco Dingo (development branch) WINBOOK 13 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: docmint2172 F pulseaudio /dev/snd/controlC1: docmint2172 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Dec 31 00:55:26 2018 InstallationDate: Installed on 2018-12-30 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181230) MachineType: AXDIA International GmbH WINBOOK 13 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=ea66942b-3d65-4c18-a99e-d02e31358a42 ro recovery nomodeset i8042.nomux=1 i8042.reset RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2017 dmi.bios.vendor: WINBOOK 13 dmi.bios.version: 1.6 dmi.board.asset.tag: Default string dmi.board.name: K132 dmi.board.vendor: AXDIA International GmbH dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnWINBOOK13:bvr1.6:bd11/27/2017:svnAXDIAInternationalGmbH:pnWINBOOK13:pvrDefaultstring:rvnAXDIAInternationalGmbH:rnK132:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Notebook dmi.product.name: WINBOOK 13 dmi.product.sku: WINBOOK13-K132-02 dmi.product.version: Default string dmi.sys.vendor: AXDIA International GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810130/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810872] Re: Touchpad and wifi don't
You might need a proprietary driver for your Broadcom wifi card, Please try to install it in the "Additional Drivers" tab in "Software & Updates". Also, for your touchpad issue, can you try to install the HWE enablement stack to see if it helps? https://wiki.ubuntu.com/Kernel/LTSEnablementStack (BTW, it's better to have a bug report for one issue) ** 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/1810872 Title: Touchpad and wifi don't Status in linux package in Ubuntu: Incomplete Bug description: I can't use my touchpad at all and the wifi doesn't work. I tried a lot of tutorials but any of them work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: patricio 1561 F pulseaudio /dev/snd/controlC0: patricio 1561 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jan 7 22:28:14 2019 InstallationDate: Installed on 2019-01-05 (3 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: enp1s0no wireless extensions. lono wireless extensions. MachineType: TOSHIBA Satellite L45D-C ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=4224aaec-f1b1-49b5-ba77-b3fdf73c1608 ro i8042.reset quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.vendor: TOSHIBA dmi.bios.version: 5.00 dmi.board.asset.tag: * dmi.board.name: ACWAE dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: * dmi.modalias: dmi:bvnTOSHIBA:bvr5.00:bd08/12/2015:svnTOSHIBA:pnSatelliteL45D-C:pvrPSKYNU-006NC1:rvnTOSHIBA:rnACWAE:rvr1.00:cvnTOSHIBA:ct10:cvr*: dmi.product.family: * dmi.product.name: Satellite L45D-C dmi.product.version: PSKYNU-006NC1 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810872/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813957] Re: T480: closed lid and touchpad
Mark this as Incomplete for the request in comment #5 ** 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/1813957 Title: T480: closed lid and touchpad Status in linux package in Ubuntu: Incomplete Bug description: After closing the lid and working with externals screens and mouse and keyboard, the mouse cursor jumps. The effect is caused by touchpad: the workaround is to completely disable it in settings. This bug is 4.15.0-44 kernel specific. With the previous version 4.15.0-43 the problem was not observed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-44-generic 4.15.0-44.47 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: afiergol 9976 F pulseaudio /dev/snd/pcmC0D0p: afiergol 9976 F...m pulseaudio /dev/snd/controlC0: afiergol 9976 F pulseaudio CurrentDesktop: GNOME Date: Wed Jan 30 17:29:35 2019 HibernationDevice: RESUME=UUID=7b4a9d17-f6d7-42ed-8f12-34f46c41cc6c InstallationDate: Installed on 2018-04-05 (300 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: LENOVO 20L6S04200 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash nogpumanager intel_iommu=on,igfx_off iommu=pt kvm.ignore_msrs=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-08-22 (161 days ago) dmi.bios.date: 11/07/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET44W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L6S04200 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET44W(1.19):bd11/07/2018:svnLENOVO:pn20L6S04200:pvrThinkPadT480:rvnLENOVO:rn20L6S04200:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L6S04200 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812631] Re: touchpad not working at all
Marked as Incomplete for the request in comment #3 ** 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/1812631 Title: touchpad not working at all Status in linux package in Ubuntu: Incomplete Bug description: I've installed Ubuntu 18.10 on my Toshiba Satellite but doesn't work at all, I've tried to fix it without success ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jacopo 2337 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jan 21 11:10:12 2019 InstallationDate: Installed on 2018-11-14 (67 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: TOSHIBA SATELLITE L50-A-161 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=667b06fb-abbf-4ef1-8656-b3893f3cae89 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.20 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VG10F dmi.board.vendor: Intel dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.20:bd05/15/2013:svnTOSHIBA:pnSATELLITEL50-A-161:pvrPSKJNE-03E00MIT:rvnIntel:rnVG10F:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Type1Family dmi.product.name: SATELLITE L50-A-161 dmi.product.sku: PSKJNE dmi.product.version: PSKJNE-03E00MIT dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812631/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815957] Re: SynPS/2 Synaptics TouchPad: Read error 19
Mark this as Incomplete for the request in #31 ** 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/1815957 Title: SynPS/2 Synaptics TouchPad: Read error 19 Status in libinput package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: Hi Ubuntu 18.04 went into standby mode with the mouse plugged in. Then I've removed the mouse. A few hours later I wanted to continue work (without mouse) and woke up my PC from standby mode. Unfortunately the touchpad did not work. So I put Ubuntu back into standby mode, plugged in a mouse and woke it up again. Both Touchpad and mouse worked perfectly again. Regards, Ettore Atalan --- ProblemType: Bug .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben7239 F pulseaudio CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2018-07-29 21:59:28,715 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: tuxedo-wmi, 1.5.1, 3.13.0-24-generic, x86_64: built tuxedo-wmi, 1.5.1, 4.15.0-44-generic, x86_64: installed tuxedo-wmi, 1.5.1, 4.15.0-45-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6507] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 5986:055c Acer, Inc Bus 001 Device 002: ID 046d:c245 Logitech, Inc. G400 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook W65_W67RZ Package: xserver-xorg-input-libinput 0.27.1-1 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=462560f8-ccdb-4115-a3c9-46fce6a630d2 ro rw quiet splash acpi_os_name=Linux acpi_osi= acpi_backlight=vendor vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic ubuntu ubuntu Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-29 (204 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.09 dmi.board.asset.tag: Tag 12345 dmi.board.name: W65_W67RZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.09:bd05/27/2016:svnNotebook:pnW65_W67RZ:pvrNotApplicable:rvnNotebook:rnW65_W67RZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W65_W67RZ dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Jan 21 20:00:45 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1815957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1816036] Re: Sound Card not detected.
Marked as Incomplete for request in comment #3 ** 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/1816036 Title: Sound Card not detected. Status in linux package in Ubuntu: Incomplete Bug description: sound card doesnt work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-45-generic 4.15.0-45.48 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Fri Feb 15 18:06:17 2019 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1018:1006 Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: I-Life Digital Technologies LLC ZED AIR ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=8e451b7e-1777-4606-a6af-3218b2a90d72 ro quiet splash hid.ignore_special_drivers=1 vt.handoff=1 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.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: ilife.Wi314.NANNEBN09 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: ZED AIR dmi.board.vendor: I-Life Digital Technologies LLC dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrilife.Wi314.NANNEBN09:bd08/20/2016:svnI-LifeDigitalTechnologiesLLC:pnZEDAIR:pvrV1.00.01:rvnI-LifeDigitalTechnologiesLLC:rnZEDAIR:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: 10.1 Tablet PC dmi.product.name: ZED AIR dmi.product.version: V1.00.01 dmi.sys.vendor: I-Life Digital Technologies LLC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816036/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819389] Re: i2c_hid_get_input: incomplete report in v5.0.0
Workaround patch: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1475af255e18f35dc46f8a7acc18354c73d45149 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819389 Title: i2c_hid_get_input: incomplete report in v5.0.0 Status in linux package in Ubuntu: Confirmed Bug description: Similar issue to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784152, however the fix in 4.18 does not seem to work for this one. When using the pen included with the HP Spectre x360 13" and libinput1.10 or libinput 1.12, dmesg is flooded with: ... [ 87.571189] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535) [ 87.577156] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535) [ 87.586621] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535) [ 87.600126] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535) [ 87.645181] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535) [ 87.647241] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535) ... Please see attached details. At first, the pen functions normally, however after approximately 1 minute of use, it will continue to move windows but loses writing and drawing capabilities in applications. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797327] Re: getrandom02 in ubuntu_ltp_syscalls failed with X-kvm
Found on C-AWS ARM64 (AMD64 is fine) as well, need to check if it can work with LTP_TIMEOUT_MUL > 1 And the next question is how to determine when to use that parameter. -- 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/1797327 Title: getrandom02 in ubuntu_ltp_syscalls failed with X-kvm Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Bug description: This test will time out with X-KVM kernel on a KVM node. <<>> tag=getrandom02 stime=1539245024 cmdline="getrandom02" contacts="" analysis=exit <<>> tst_test.c:1072: INFO: Timeout per run is 0h 05m 00s getrandom02.c:72: PASS: getrandom returned 256 getrandom02.c:72: PASS: getrandom returned 6 getrandom02.c:72: PASS: getrandom returned 256 Test timeouted, sending SIGKILL! tst_test.c:1112: INFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tst_test.c:1113: BROK: Test killed! (timeout?) Summary: passed 3 failed 0 skipped 0 warnings 0 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1036-kvm 4.4.0-1036.42 ProcVersionSignature: User Name 4.4.0-1036.42-kvm 4.4.155 Uname: Linux 4.4.0-1036-kvm x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Oct 11 08:05:56 2018 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1797327/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818802] Re: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while
Also, does this bug apply to the laptop's internal speakers? Or are you using headphones? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818802 Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Audio dies after few seconds, returns after few minutes and dies again filip@ux433:~$ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.20.14-042014-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filip 8566 F pulseaudio /dev/snd/pcmC0D0p: filip 8566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 6 10:11:01 2019 InstallationDate: Installed on 2019-01-05 (59 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 comm="/usr/bin/pulseaudio --daemonize=no ") Symptom_Type: Sound works for a while, then breaks Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago) dmi.bios.date: 11/21/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818802/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818802] Re: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while
Next, please wait until the audio has stopped working AND has later come back, then run: dmesg > dmesgafter.txt journalctl -b0 > journalafter.txt and send us the files 'dmesgafter.txt' and 'journalafter.txt'. ** Summary changed: - [ZenBook UX433FN_UX433FN] Audio only works when the laptop is plugged in or the battery % is above 20 - 40% + [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818802 Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Audio dies after few seconds, returns after few minutes and dies again filip@ux433:~$ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.20.14-042014-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filip 8566 F pulseaudio /dev/snd/pcmC0D0p: filip 8566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 6 10:11:01 2019 InstallationDate: Installed on 2019-01-05 (59 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 comm="/usr/bin/pulseaudio --daemonize=no ") Symptom_Type: Sound works for a while, then breaks Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago) dmi.bios.date: 11/21/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818802/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818381] Re: Two finger scroll does not work after hibernate
Okay. I checked the POWER setting. You're correct. It only showed Suspend (no hibernate). Anyway, I commented out "blacklist i2c_i801" and rebooted. After suspend, two finger scroll 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/1818381 Title: Two finger scroll does not work after hibernate Status in linux package in Ubuntu: Incomplete Bug description: Two finger scroll does not work in Chromium browser after HIBERNATION. I restarted Chromium browser and it did not resolve two finger scroll issue. I log out, then log back on. Again, it did not resolve two finger scroll issue. SO, I rebooted and it did resolved two finger scroll issue. It happened often ONLY after HIBERNATION. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jwvehrs2302 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-24 (284 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 138a:0097 Validity Sensors, Inc. Bus 001 Device 003: ID 04ca:7067 Lite-On Technology Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HRCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=92701269-6a7b-4d00-ba3a-23edd5c03359 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 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.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/11/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET51W(1.36) dmi.board.asset.tag: Not Available dmi.board.name: 20HRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1MET51W(1.36):bd01/11/2019:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 5th dmi.product.name: 20HRCTO1WW dmi.product.version: ThinkPad X1 Carbon 5th dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jwvehrs2332 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-24 (289 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 138a:0097 Validity Sensors, Inc. Bus 001 Device 003: ID 04ca:7067 Lite-On Technology Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HRCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=92701269-6a7b-4d00-ba3a-23edd5c03359 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/14/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET52W(1.37) dmi.board.asset.tag: Not Available dmi.board.name: 20HRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dm
[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
@Thorsten Might you explain how to apply patches to, say, the 5.0.1 kernel (which I am using, via the Ubuntu Kernel Update Utility, on Linux Mint)? I can't seem to find the information in this thread and I am unsure of the goodness or at least relevance of other instructions that I've found on the web. I'd be most grateful. .Debs are provided, above, for a patched version of the 4.20 kernel; but you say you managed to run the patches on 4.21 - so perhaps the patches can apply to kernel version 5 as well? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage:
[Kernel-packages] [Bug 1819546] [NEW] Avoid potential memory corruption on HiSilicon SoCs
Public bug reported: [Impact] There is a potential for memory corruption in MSI payloads. For reasons mentioned in the commit message, this happens to not be triggerable today, but is fragile, and could rear it's ugly head if a struct layout changes due to other backports in the future. [Test Case] Regression-only. [Fix] 84a9a75774961 iommu/arm-smmu-v3: Avoid memory corruption from Hisilicon MSI payloads [Regression Risk] The fix is to add some explicit padding into an internal structure. This padding is already implicit today. ** Affects: linux (Ubuntu) Importance: Medium Status: Fix Released ** Affects: linux (Ubuntu Bionic) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Affects: linux (Ubuntu Cosmic) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Affects: linux (Ubuntu Disco) Importance: Medium Status: Fix Released ** Also affects: linux (Ubuntu Disco) Importance: Medium Assignee: dann frazier (dannf) Status: Fix Released ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Cosmic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux (Ubuntu Cosmic) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux (Ubuntu Disco) Assignee: dann frazier (dannf) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819546 Title: Avoid potential memory corruption on HiSilicon SoCs Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Status in linux source package in Disco: Fix Released Bug description: [Impact] There is a potential for memory corruption in MSI payloads. For reasons mentioned in the commit message, this happens to not be triggerable today, but is fragile, and could rear it's ugly head if a struct layout changes due to other backports in the future. [Test Case] Regression-only. [Fix] 84a9a75774961 iommu/arm-smmu-v3: Avoid memory corruption from Hisilicon MSI payloads [Regression Risk] The fix is to add some explicit padding into an internal structure. This padding is already implicit today. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819535] [NEW] [disco] hns driver updates from 5.1 merge window
Public bug reported: Sync up the hns drivers with the 5.1 merge window. (Cut & paste from bug 1810457) Drivers for the HiSilicon Hi1616 and Hi1620 SoCs continue to be under active development, including both hardware enablement and bug fix patches. With the amount of flux involved, identifying and cherry-picking individual patches would be more error prone then re-syncing with current upstream. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819535 Title: [disco] hns driver updates from 5.1 merge window Status in linux package in Ubuntu: In Progress Bug description: Sync up the hns drivers with the 5.1 merge window. (Cut & paste from bug 1810457) Drivers for the HiSilicon Hi1616 and Hi1620 SoCs continue to be under active development, including both hardware enablement and bug fix patches. With the amount of flux involved, identifying and cherry-picking individual patches would be more error prone then re-syncing with current upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819535/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819515] [NEW] Disco update: v5.0.1 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.0.1 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Disco) Importance: Undecided Status: Confirmed ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: 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/1819515 Title: Disco update: v5.0.1 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Confirmed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.0.1 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819515/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818580] Re: [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting.
cmdlive==cmdline -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818580 Title: [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting. Status in linux package in Ubuntu: Triaged Bug description: I cannot boot PC normally, i must use recovery mode. Full dmesg after modprobe'ing amdgpu demonstrating call trace and lead up: https://launchpadlibrarian.net/414079136/complete-dmesg-after-modprobe-amdgpu.txt WORKAROUND: Use kernel parameter: nomodeset OR: modprobe.blacklist=amdgpu ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-video-amdgpu 18.1.99+git20190207-1 ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0 Uname: Linux 5.0.0-7-lowlatency x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Tue Mar 5 00:59:48 2019 DistUpgraded: 2019-02-07 01:41:15,390 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: disco DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev cf) (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [174b:353e] InstallationDate: Installed on 2012-02-27 (2562 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: MEDIONPC MS-7616 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-lowlatency root=UUID=cded073e-f845-4947-970b-f8a4290c4c2b ro quiet splash acpi_osi=Linux nomodeset crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M crashkernel=512M-:192M vt.handoff=1 SourcePackage: xserver-xorg-video-amdgpu UpgradeStatus: Upgraded to disco on 2019-02-07 (25 days ago) dmi.bios.date: 01/15/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A7616MLN.10F dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7616 dmi.board.vendor: MEDIONPC dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: MEDIONPC dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA7616MLN.10F:bd01/15/2010:svnMEDIONPC:pnMS-7616:pvr1.0:rvnMEDIONPC:rnMS-7616:rvr1.0:cvnMEDIONPC:ct3:cvr: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: MS-7616 dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MEDIONPC version.compiz: compiz 1:0.9.14.0+19.04.20190219-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.99+git20190207-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818580/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818580] Re: [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting.
i contacted with a guy with an AMD RX 470 GPU and he says irs working fine on his system i have just tested 18.10 and a daily 19.04 livecd builds with no success. Also i have disabled ACPI in both BIOS and kernel cmdlive (acpi=off) with no success -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818580 Title: [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting. Status in linux package in Ubuntu: Triaged Bug description: I cannot boot PC normally, i must use recovery mode. Full dmesg after modprobe'ing amdgpu demonstrating call trace and lead up: https://launchpadlibrarian.net/414079136/complete-dmesg-after-modprobe-amdgpu.txt WORKAROUND: Use kernel parameter: nomodeset OR: modprobe.blacklist=amdgpu ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-video-amdgpu 18.1.99+git20190207-1 ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0 Uname: Linux 5.0.0-7-lowlatency x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Tue Mar 5 00:59:48 2019 DistUpgraded: 2019-02-07 01:41:15,390 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: disco DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev cf) (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [174b:353e] InstallationDate: Installed on 2012-02-27 (2562 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: MEDIONPC MS-7616 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-lowlatency root=UUID=cded073e-f845-4947-970b-f8a4290c4c2b ro quiet splash acpi_osi=Linux nomodeset crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M crashkernel=512M-:192M vt.handoff=1 SourcePackage: xserver-xorg-video-amdgpu UpgradeStatus: Upgraded to disco on 2019-02-07 (25 days ago) dmi.bios.date: 01/15/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A7616MLN.10F dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7616 dmi.board.vendor: MEDIONPC dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: MEDIONPC dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA7616MLN.10F:bd01/15/2010:svnMEDIONPC:pnMS-7616:pvr1.0:rvnMEDIONPC:rnMS-7616:rvr1.0:cvnMEDIONPC:ct3:cvr: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: MS-7616 dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MEDIONPC version.compiz: compiz 1:0.9.14.0+19.04.20190219-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.99+git20190207-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818580/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817832] Re: qemu crashes with `kvm_init_vcpu failed: Invalid argument` during guest boot cores >256
** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin1904 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1817832 Title: qemu crashes with `kvm_init_vcpu failed: Invalid argument` during guest boot cores >256 Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Invalid Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Bug description: == Comment: #0 - Satheesh Rajendran - 2019-02-14 23:48:15 == ---Problem Description--- qemu crashes with `kvm_init_vcpu failed: Invalid argument` during guest boot cores >256 but the error message is not clearly explains it. Contact Information = sathe...@in.ibm.com ---uname output--- 4.15.0-1016-ibm-gt Machine Type = power9 ppc64le ---Debugger--- A debugger is not configured ---Steps to Reproduce--- # /usr/bin/qemu-system-ppc64 -smp 257 -enable-kvm -monitor stdio qemu-system-ppc64: warning: Number of SMP cpus requested (257) exceeds the recommended cpus supported by KVM (128) qemu-system-ppc64: warning: Number of hotpluggable cpus requested (257) exceeds the recommended cpus supported by KVM (128) QEMU 2.11.1 monitor - type 'help' for more information (qemu) kvm_init_vcpu failed: Invalid argument Expected Result: 1. Guest should boot fine or 2. Proper error message stating cores >256 need to have thread>1 because smp=512 with threads=2 works fine like below # /usr/bin/qemu-system-ppc64 -smp 512,cores=256,threads=2 -enable-kvm -monitor stdio qemu-system-ppc64: warning: Number of SMP cpus requested (512) exceeds the recommended cpus supported by KVM (128) qemu-system-ppc64: warning: Number of hotpluggable cpus requested (512) exceeds the recommended cpus supported by KVM (128) QEMU 2.11.1 monitor - type 'help' for more information (qemu) VNC server running on ::1:5900 (qemu) info status VM status: running Userspace tool common name: ii qemu-system-ppc 1:2.11+dfsg-1ubuntu7.8-1ibm3 ppc64el QEMU full system emulation binaries (ppc) The userspace tool has the following bit modes: both Userspace rpm: ii qemu-system-ppc 1:2.11+dfsg-1ubuntu7.8-1ibm3 ppc64el QEMU full system emulation binaries (ppc) Userspace tool obtained from project website: na *Additional Instructions for sathe...@in.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. -Attach ltrace and strace of userspace application. commit 1e175d2e07c71d9574f5b1c74523abca54e2654f Author: Sam Bobroff Date: Wed Jul 25 16:12:02 2018 +1000 commit b5c6f7607b908b1445f2556c8d2f3b1ec5fc5aa8 Author: Paul Mackerras Date: Thu Jul 26 15:38:41 2018 +1000 commit 1ebe6b81ebdba8faf377d1d7d84ad9368e7a0bae Author: Paul Mackerras Date: Thu Jul 26 14:53:54 2018 +1000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1817832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817832] Re: qemu crashes with `kvm_init_vcpu failed: Invalid argument` during guest boot cores >256
** Tags removed: severity-high ** Tags added: severity-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/1817832 Title: qemu crashes with `kvm_init_vcpu failed: Invalid argument` during guest boot cores >256 Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Invalid Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Bug description: == Comment: #0 - Satheesh Rajendran - 2019-02-14 23:48:15 == ---Problem Description--- qemu crashes with `kvm_init_vcpu failed: Invalid argument` during guest boot cores >256 but the error message is not clearly explains it. Contact Information = sathe...@in.ibm.com ---uname output--- 4.15.0-1016-ibm-gt Machine Type = power9 ppc64le ---Debugger--- A debugger is not configured ---Steps to Reproduce--- # /usr/bin/qemu-system-ppc64 -smp 257 -enable-kvm -monitor stdio qemu-system-ppc64: warning: Number of SMP cpus requested (257) exceeds the recommended cpus supported by KVM (128) qemu-system-ppc64: warning: Number of hotpluggable cpus requested (257) exceeds the recommended cpus supported by KVM (128) QEMU 2.11.1 monitor - type 'help' for more information (qemu) kvm_init_vcpu failed: Invalid argument Expected Result: 1. Guest should boot fine or 2. Proper error message stating cores >256 need to have thread>1 because smp=512 with threads=2 works fine like below # /usr/bin/qemu-system-ppc64 -smp 512,cores=256,threads=2 -enable-kvm -monitor stdio qemu-system-ppc64: warning: Number of SMP cpus requested (512) exceeds the recommended cpus supported by KVM (128) qemu-system-ppc64: warning: Number of hotpluggable cpus requested (512) exceeds the recommended cpus supported by KVM (128) QEMU 2.11.1 monitor - type 'help' for more information (qemu) VNC server running on ::1:5900 (qemu) info status VM status: running Userspace tool common name: ii qemu-system-ppc 1:2.11+dfsg-1ubuntu7.8-1ibm3 ppc64el QEMU full system emulation binaries (ppc) The userspace tool has the following bit modes: both Userspace rpm: ii qemu-system-ppc 1:2.11+dfsg-1ubuntu7.8-1ibm3 ppc64el QEMU full system emulation binaries (ppc) Userspace tool obtained from project website: na *Additional Instructions for sathe...@in.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. -Attach ltrace and strace of userspace application. commit 1e175d2e07c71d9574f5b1c74523abca54e2654f Author: Sam Bobroff Date: Wed Jul 25 16:12:02 2018 +1000 commit b5c6f7607b908b1445f2556c8d2f3b1ec5fc5aa8 Author: Paul Mackerras Date: Thu Jul 26 15:38:41 2018 +1000 commit 1ebe6b81ebdba8faf377d1d7d84ad9368e7a0bae Author: Paul Mackerras Date: Thu Jul 26 14:53:54 2018 +1000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1817832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819500] Re: hisi_sas: add debugfs support
** Description changed: [Impact] Per https://patchwork.kernel.org/cover/10737541/ : "Every controller HW version has had bugs. These bugs have been very painful to debug. One useful tool to debug these is being able to capture and export HW registers and driver control structures at point of failure." [Test Case] - echo "options hisi_sas_main hisi_sas_debugfs_enable=1" | \ - sudo tee /etc/modprobe.d/hisi-sas-debugfs.conf + echo "options hisi_sas_main debugfs_enable=1" | \ + sudo tee /etc/modprobe.d/hisi-sas-debugfs.conf sudo mkinitramfs -o /boot/initrd.img-$(uname -r) $(uname -r) sudo reboot [...] test -d /sys/kernel/debug/hisi_sas [Fix] 5979f33b982dc scsi: hisi_sas: Add debugfs ITCT file and add file operations 5b0eeac4bed4b scsi: hisi_sas: Fix type casting and missing static qualifier in debugfs code c2c7e74057715 scsi: hisi_sas: No need to check return value of debugfs_create functions 1afb4b8524797 scsi: hisi_sas: Add debugfs IOST file and add file operations 148e379f60c5c scsi: hisi_sas: Add debugfs DQ file and add file operations 971afae7cf4f7 scsi: hisi_sas: Add debugfs CQ file and add file operations 61a6ebf3f5842 scsi: hisi_sas: Add debugfs for port registers caefac1996764 scsi: hisi_sas: Debugfs global register create file and add file operations 49159a5e4175f scsi: hisi_sas: Take debugfs snapshot for all regs eb1c2b72b7694 scsi: hisi_sas: Alloc debugfs snapshot buffer memory for all registers ef63464bcf8fe scsi: hisi_sas: Create root and device debugfs directories [Regression Risk] Code changes are restricted to the on-chip SAS controller on hi1620 SoCs. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819500 Title: hisi_sas: add debugfs support Status in linux package in Ubuntu: In Progress Bug description: [Impact] Per https://patchwork.kernel.org/cover/10737541/ : "Every controller HW version has had bugs. These bugs have been very painful to debug. One useful tool to debug these is being able to capture and export HW registers and driver control structures at point of failure." [Test Case] echo "options hisi_sas_main debugfs_enable=1" | \ sudo tee /etc/modprobe.d/hisi-sas-debugfs.conf sudo mkinitramfs -o /boot/initrd.img-$(uname -r) $(uname -r) sudo reboot [...] test -d /sys/kernel/debug/hisi_sas [Fix] 5979f33b982dc scsi: hisi_sas: Add debugfs ITCT file and add file operations 5b0eeac4bed4b scsi: hisi_sas: Fix type casting and missing static qualifier in debugfs code c2c7e74057715 scsi: hisi_sas: No need to check return value of debugfs_create functions 1afb4b8524797 scsi: hisi_sas: Add debugfs IOST file and add file operations 148e379f60c5c scsi: hisi_sas: Add debugfs DQ file and add file operations 971afae7cf4f7 scsi: hisi_sas: Add debugfs CQ file and add file operations 61a6ebf3f5842 scsi: hisi_sas: Add debugfs for port registers caefac1996764 scsi: hisi_sas: Debugfs global register create file and add file operations 49159a5e4175f scsi: hisi_sas: Take debugfs snapshot for all regs eb1c2b72b7694 scsi: hisi_sas: Alloc debugfs snapshot buffer memory for all registers ef63464bcf8fe scsi: hisi_sas: Create root and device debugfs directories [Regression Risk] Code changes are restricted to the on-chip SAS controller on hi1620 SoCs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819500/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818802] Re: [ZenBook UX433FN_UX433FN] Audio only works when the laptop is plugged in or the battery % is above 20 - 40%
Hello, it seems like now audio is not working even when on full battery or plugged in. It's so weird. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818802 Title: [ZenBook UX433FN_UX433FN] Audio only works when the laptop is plugged in or the battery % is above 20 - 40% Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Audio dies after few seconds, returns after few minutes and dies again filip@ux433:~$ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.20.14-042014-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filip 8566 F pulseaudio /dev/snd/pcmC0D0p: filip 8566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 6 10:11:01 2019 InstallationDate: Installed on 2019-01-05 (59 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 comm="/usr/bin/pulseaudio --daemonize=no ") Symptom_Type: Sound works for a while, then breaks Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago) dmi.bios.date: 11/21/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818802/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819504] Re: tcmu user space crash results in kernel module hang.
** Changed in: linux-gcp (Ubuntu) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux-gcp (Ubuntu Bionic) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- 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/1819504 Title: tcmu user space crash results in kernel module hang. Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Bionic: New Bug description: With the 4.15.0 kernel version used in bionic GCP/GKE, if the tcmu user space code crashes while handling a netlink message from the kernel, the kernel module will be stuck waiting for the response. This situation can only be resolved with a server reboot. === SRU Justification === [Impact] With this particular user-space crash in the current Ubuntu image it results in a hang hobbles the entire physical server. [Fix] The request is for Canonical to backport the patch https://patchwork.kernel.org/patch/10319623/ to the bionic 4.15.0 kernel There were a number of mainline upstream commits to apply as part of the backport [Test] unavailable [Regression Potential] Low. it's all mainline commits, and affects only that driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1819504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819500] Re: hisi_sas: add debugfs support
** Description changed: [Impact] Per https://patchwork.kernel.org/cover/10737541/ : "Every controller HW version has had bugs. These bugs have been very painful to debug. One useful tool to debug these is being able to capture and export HW registers and driver control structures at point of failure." [Test Case] + echo "options hisi_sas_main hisi_sas_debugfs_enable=1" | \ + sudo tee /etc/modprobe.d/hisi-sas-debugfs.conf + sudo mkinitramfs -o /boot/initrd.img-$(uname -r) $(uname -r) + sudo reboot + [...] test -d /sys/kernel/debug/hisi_sas [Fix] 5979f33b982dc scsi: hisi_sas: Add debugfs ITCT file and add file operations 5b0eeac4bed4b scsi: hisi_sas: Fix type casting and missing static qualifier in debugfs code c2c7e74057715 scsi: hisi_sas: No need to check return value of debugfs_create functions 1afb4b8524797 scsi: hisi_sas: Add debugfs IOST file and add file operations 148e379f60c5c scsi: hisi_sas: Add debugfs DQ file and add file operations 971afae7cf4f7 scsi: hisi_sas: Add debugfs CQ file and add file operations 61a6ebf3f5842 scsi: hisi_sas: Add debugfs for port registers caefac1996764 scsi: hisi_sas: Debugfs global register create file and add file operations 49159a5e4175f scsi: hisi_sas: Take debugfs snapshot for all regs eb1c2b72b7694 scsi: hisi_sas: Alloc debugfs snapshot buffer memory for all registers ef63464bcf8fe scsi: hisi_sas: Create root and device debugfs directories [Regression Risk] Code changes are restricted to the on-chip SAS controller on hi1620 SoCs. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819500 Title: hisi_sas: add debugfs support Status in linux package in Ubuntu: In Progress Bug description: [Impact] Per https://patchwork.kernel.org/cover/10737541/ : "Every controller HW version has had bugs. These bugs have been very painful to debug. One useful tool to debug these is being able to capture and export HW registers and driver control structures at point of failure." [Test Case] echo "options hisi_sas_main debugfs_enable=1" | \ sudo tee /etc/modprobe.d/hisi-sas-debugfs.conf sudo mkinitramfs -o /boot/initrd.img-$(uname -r) $(uname -r) sudo reboot [...] test -d /sys/kernel/debug/hisi_sas [Fix] 5979f33b982dc scsi: hisi_sas: Add debugfs ITCT file and add file operations 5b0eeac4bed4b scsi: hisi_sas: Fix type casting and missing static qualifier in debugfs code c2c7e74057715 scsi: hisi_sas: No need to check return value of debugfs_create functions 1afb4b8524797 scsi: hisi_sas: Add debugfs IOST file and add file operations 148e379f60c5c scsi: hisi_sas: Add debugfs DQ file and add file operations 971afae7cf4f7 scsi: hisi_sas: Add debugfs CQ file and add file operations 61a6ebf3f5842 scsi: hisi_sas: Add debugfs for port registers caefac1996764 scsi: hisi_sas: Debugfs global register create file and add file operations 49159a5e4175f scsi: hisi_sas: Take debugfs snapshot for all regs eb1c2b72b7694 scsi: hisi_sas: Alloc debugfs snapshot buffer memory for all registers ef63464bcf8fe scsi: hisi_sas: Create root and device debugfs directories [Regression Risk] Code changes are restricted to the on-chip SAS controller on hi1620 SoCs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819500/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819420] Re: Apparent bug: Dell tablet crashes when plugged into docking station with 4.15.0-46 kernel
** Description changed: This appears to be the same bug that was present, two kernels ago: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813795 I switched to the 46 kernel from the 45 today, and noticed my tablet hangs when its plugged into the docking station. Without the docking station it appears fine. As with the previous bug, even when it hangs, I can ssh into the tablet. So it appears to be the user interface that's frozen. The mouse pointer remains mobile. - Note: this run of apport is pre-crash. + Note: this run of apport is pre-crash. + + Note 2: I encountered this bug three boots in a row yesterday. But + today I have been unable to duplicate it. So I'm a little confused. + I'll try to duplicate the bug again tonight. If I can't, I'll close + this thread. + --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rybu 2013 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=35ab6535-9677-4ec9-9b70-33d75778947f InstallationDate: Installed on 2018-11-09 (122 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Latitude 5290 2-in-1 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-46-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/27/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.3 dmi.board.name: 0M27Y3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 32 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.3:bd08/27/2018:svnDellInc.:pnLatitude52902-in-1:pvr:rvnDellInc.:rn0M27Y3:rvrA00:cvnDellInc.:ct32:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5290 2-in-1 dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819420 Title: Apparent bug: Dell tablet crashes when plugged into docking station with 4.15.0-46 kernel Status in linux package in Ubuntu: Incomplete Bug description: This appears to be the same bug that was present, two kernels ago: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813795 I switched to the 46 kernel from the 45 today, and noticed my tablet hangs when its plugged into the docking station. Without the docking station it appears fine. As with the previous bug, even when it hangs, I can ssh into the tablet. So it appears to be the user interface that's frozen. The mouse pointer remains mobile. Note: this run of apport is pre-crash. Note 2: I encountered this bug three boots in a row yesterday. But today I have been unable to duplicate it. So I'm a little confused. I'll try to duplicate the bug again tonight. If I can't, I'll close this thread. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rybu 2013 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=35ab6535-9677-4ec9-9b70-33d75778947f InstallationDate: Installed on 2018-11-09 (122 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Latitude 5290 2-in-1 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-46-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/27/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.3 dmi.board.name: 0M27Y3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 32 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.3:bd08/27/2018:svnDellInc.:pnLatitude52902-in-1:pvr:rvnDellInc.:rn0M27Y3:rvrA00:cvnDellInc.
[Kernel-packages] [Bug 1819504] [NEW] tcmu user space crash results in kernel module hang.
Public bug reported: With the 4.15.0 kernel version used in bionic GCP/GKE, if the tcmu user space code crashes while handling a netlink message from the kernel, the kernel module will be stuck waiting for the response. This situation can only be resolved with a server reboot. === SRU Justification === [Impact] With this particular user-space crash in the current Ubuntu image it results in a hang hobbles the entire physical server. [Fix] The request is for Canonical to backport the patch https://patchwork.kernel.org/patch/10319623/ to the bionic 4.15.0 kernel There were a number of mainline upstream commits to apply as part of the backport [Test] unavailable [Regression Potential] Low. it's all mainline commits, and affects only that driver. ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu Bionic) Importance: Undecided Status: New ** 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/1819504 Title: tcmu user space crash results in kernel module hang. Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Bionic: New Bug description: With the 4.15.0 kernel version used in bionic GCP/GKE, if the tcmu user space code crashes while handling a netlink message from the kernel, the kernel module will be stuck waiting for the response. This situation can only be resolved with a server reboot. === SRU Justification === [Impact] With this particular user-space crash in the current Ubuntu image it results in a hang hobbles the entire physical server. [Fix] The request is for Canonical to backport the patch https://patchwork.kernel.org/patch/10319623/ to the bionic 4.15.0 kernel There were a number of mainline upstream commits to apply as part of the backport [Test] unavailable [Regression Potential] Low. it's all mainline commits, and affects only that driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1819504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814069] Re: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2
Here's a log from a boot using your kernal at https://people.canonical.com/~khfeng/lp1814069/ Kernel parameters are as you requested and a modprobe hv_netvsc after boot. I'm not sure exactly how to retrieve dmesg properly nowadays but I used journalctl -k -b -2 to retrieve the kernel messages for the boot we're interested in. If you need more detailed info give me a hint on how to retrieve it. ** Attachment added: "kernel messages from modprobe in 4.15.0-46" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814069/+attachment/5245537/+files/dmesg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814069 Title: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2 Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu stuck on booting on HyperV Server 2008R2. I saw kernel messages, seems to load ram image the boot is stuck. Seems to be a problem with hyperv drivers propably harddrive. Reverted back to the previous kernel. Description:Ubuntu 18.04.1 LTS Release:18.04Description:Ubuntu 18.04.1 LTS Release:18.04 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 31 08:52 seq crw-rw 1 root audio 116, 33 Jan 31 08:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 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' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=86036ccb-bc11-11e8-93c9-00155dfd7535 ro maybe-ubiquity ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090004 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 8531-7125-9206-2460-7819-2663-90 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090004:bd03/19/2009:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: dmi.product.name: Virtual Machine dmi.product.version: 7.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819486] Re: Crash from :i915 module with 4.15.0-46-generic using multi-display
** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819486/+attachment/5245519/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819486 Title: Crash from :i915 module with 4.15.0-46-generic using multi-display Status in linux package in Ubuntu: Confirmed Bug description: While previously working using 4.15.0-45-generic, booting my thinkpad T480 on a dock with additional screen connected and "kernel 4.15.0-46-generic" lead to a crash of the system. Laptop is running Ubuntu 18.04.2 LTS. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: user 3449 F...m pulseaudio /dev/snd/controlC1: user 3449 F pulseaudio /dev/snd/pcmC0D0p: user 3449 F...m pulseaudio /dev/snd/controlC0: user 3449 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7 InstallationDate: Installed on 2018-06-28 (256 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20L5000AFR Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin netdev plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET37W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5000AFR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L5000AFR:pvrThinkPadT480:rvnLENOVO:rn20L5000AFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5000AFR dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819486/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1646805] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2018-12-12 05:40 EDT--- -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1646805 Title: MAC address needs to be unique and unchanged during entire netboot process Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Currently the MAC address is not solely used to id the machine or system. It is at the moment used to id the interface that the MAC represents. (At a very early state in the process the MAC address is missing or only available from inside the partition.) The minimum PXE boot requirements need to be satisfied in general. The boot loader is part of the firmware and not loaded from the server. So that means the firmware needs to provide the MAC address. But the MAC address is not available at that time, so it's not available upfront. MaaS is using the same MAC address for the initial DHCP request as for the network boot. Hence an initially known MAC address is required that needs to be static and doesn't change (on subsequent boots for that instance). There might be an IBM internal ticket already open for this - please check. Furthermore the firmware needs to requests files like this: pxelinux.cfg/01-88-99-aa-bb-cc-dd pxelinux.cfg/default And BOOTIF support is required: See 'petitboot doesn't handle ipappend in pxelinux.cfg' https://bugs.launchpad.net/tasty-taco/+bug/1322307 for reference. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1646805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1804645] Re: [19.04 FEAT] kernel address sanitizer support
Since Kernel 5.0 just landed in disco's release pocket, I'm changing the status to Fix Released. ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released ** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804645 Title: [19.04 FEAT] kernel address sanitizer support Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: KernelAddressSANitizer (KASAN) is a dynamic memory error detector. It provides a fast and comprehensive solution for finding use-after-free and out-of-bounds bugs. KASAN uses compile-time instrumentation for checking every memory access, therefore you will need a GCC version 4.9.2 or later. GCC 5.0 or later is required for detection of out-of-bounds accesses to stack or global variables. Implement the backend for Linux on Z to be able to use KASAN. Provide an additional RPM autobuild target for a KASAN enabled kernel. kernel 4.20 Git-Commit : will follow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1804645/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805428] Re: [19.04 FEAT] Synthesize perf events/samples from CPU-MF auxtrace data
Since Kernel 5.0 just landed in disco's release pocket, I'm changing the status to Fix Released. ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released ** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1805428 Title: [19.04 FEAT] Synthesize perf events/samples from CPU-MF auxtrace data Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Enable the Intel instruction trace (itrace), evaluate synthesizing perf events and samples from auxtrace buffe for s390x. The auxtrace buffer contains the CPU-MF sampling data blocks that contains basic- and diagnostic sampling data entries. Similar to the cpum_sf PMU, parse the basic-sampling data entries and synthesize perf events/samples for each entry. This can be solely done in the perf tool. kernel 4.20: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1805428/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814537] Re: [19.04 FEAT] Splitting DIF and DIX boot time controls
Since Kernel 5.0 just landed in disco's release pocket, I'm changing the status to Fix Released. ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released ** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814537 Title: [19.04 FEAT] Splitting DIF and DIX boot time controls Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Functions: A Linux on Z user can separately configure DIF and DIF+DIX integrity protection mechanisms. Business Value: Customers can improve data integrity protection for data stored on FCP storage by making use of hardware-based DIF data integrity checking between FCP channel and target LUN. Previously, this feature could only be enabled together with the DIX feature that has proven to be too unstable for production usage. Will be made available with kernel 5.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1814537/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819500] [NEW] hisi_sas: add debugfs support
Public bug reported: [Impact] Per https://patchwork.kernel.org/cover/10737541/ : "Every controller HW version has had bugs. These bugs have been very painful to debug. One useful tool to debug these is being able to capture and export HW registers and driver control structures at point of failure." [Test Case] test -d /sys/kernel/debug/hisi_sas [Fix] 5979f33b982dc scsi: hisi_sas: Add debugfs ITCT file and add file operations 5b0eeac4bed4b scsi: hisi_sas: Fix type casting and missing static qualifier in debugfs code c2c7e74057715 scsi: hisi_sas: No need to check return value of debugfs_create functions 1afb4b8524797 scsi: hisi_sas: Add debugfs IOST file and add file operations 148e379f60c5c scsi: hisi_sas: Add debugfs DQ file and add file operations 971afae7cf4f7 scsi: hisi_sas: Add debugfs CQ file and add file operations 61a6ebf3f5842 scsi: hisi_sas: Add debugfs for port registers caefac1996764 scsi: hisi_sas: Debugfs global register create file and add file operations 49159a5e4175f scsi: hisi_sas: Take debugfs snapshot for all regs eb1c2b72b7694 scsi: hisi_sas: Alloc debugfs snapshot buffer memory for all registers ef63464bcf8fe scsi: hisi_sas: Create root and device debugfs directories [Regression Risk] Code changes are restricted to the on-chip SAS controller on hi1620 SoCs. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819500 Title: hisi_sas: add debugfs support Status in linux package in Ubuntu: In Progress Bug description: [Impact] Per https://patchwork.kernel.org/cover/10737541/ : "Every controller HW version has had bugs. These bugs have been very painful to debug. One useful tool to debug these is being able to capture and export HW registers and driver control structures at point of failure." [Test Case] test -d /sys/kernel/debug/hisi_sas [Fix] 5979f33b982dc scsi: hisi_sas: Add debugfs ITCT file and add file operations 5b0eeac4bed4b scsi: hisi_sas: Fix type casting and missing static qualifier in debugfs code c2c7e74057715 scsi: hisi_sas: No need to check return value of debugfs_create functions 1afb4b8524797 scsi: hisi_sas: Add debugfs IOST file and add file operations 148e379f60c5c scsi: hisi_sas: Add debugfs DQ file and add file operations 971afae7cf4f7 scsi: hisi_sas: Add debugfs CQ file and add file operations 61a6ebf3f5842 scsi: hisi_sas: Add debugfs for port registers caefac1996764 scsi: hisi_sas: Debugfs global register create file and add file operations 49159a5e4175f scsi: hisi_sas: Take debugfs snapshot for all regs eb1c2b72b7694 scsi: hisi_sas: Alloc debugfs snapshot buffer memory for all registers ef63464bcf8fe scsi: hisi_sas: Create root and device debugfs directories [Regression Risk] Code changes are restricted to the on-chip SAS controller on hi1620 SoCs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819500/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805429] Re: [19.04 FEAT] Extended access controls for AP queue - kernel part
Since Kernel 5.0 landed in disco's release pocket today, I'm changing the status to Fix Released. ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1805429 Title: [19.04 FEAT] Extended access controls for AP queue - kernel part Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Update description: Provide a means to control which user/process can access which APQN, or in other words enable to grant users/applications access to different (sets of) crypto adapters and domains. While keeping existing interfaces for compatibility, allow to use both DAC (e.g. Unix file permissions) and MAC (e.g. LSM) methods. Please enable the following kernel config option: * CONFIG_ZCRYPT_MULTIDEVNODES=y will be made available with kernel 4.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1805429/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1646805] Re: MAC address needs to be unique and unchanged during entire netboot process
Kernel 5.0 landed in disco's release pocket today, hence changing status to Fix Released. ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released ** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1646805 Title: MAC address needs to be unique and unchanged during entire netboot process Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Currently the MAC address is not solely used to id the machine or system. It is at the moment used to id the interface that the MAC represents. (At a very early state in the process the MAC address is missing or only available from inside the partition.) The minimum PXE boot requirements need to be satisfied in general. The boot loader is part of the firmware and not loaded from the server. So that means the firmware needs to provide the MAC address. But the MAC address is not available at that time, so it's not available upfront. MaaS is using the same MAC address for the initial DHCP request as for the network boot. Hence an initially known MAC address is required that needs to be static and doesn't change (on subsequent boots for that instance). There might be an IBM internal ticket already open for this - please check. Furthermore the firmware needs to requests files like this: pxelinux.cfg/01-88-99-aa-bb-cc-dd pxelinux.cfg/default And BOOTIF support is required: See 'petitboot doesn't handle ipappend in pxelinux.cfg' https://bugs.launchpad.net/tasty-taco/+bug/1322307 for reference. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1646805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819389] Re: i2c_hid_get_input: incomplete report in v5.0.0
NOTE: The pen also reports a 1% battery all of the time. I'm not sure if this is directly related. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819389 Title: i2c_hid_get_input: incomplete report in v5.0.0 Status in linux package in Ubuntu: Confirmed Bug description: Similar issue to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784152, however the fix in 4.18 does not seem to work for this one. When using the pen included with the HP Spectre x360 13" and libinput1.10 or libinput 1.12, dmesg is flooded with: ... [ 87.571189] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535) [ 87.577156] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535) [ 87.586621] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535) [ 87.600126] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535) [ 87.645181] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535) [ 87.647241] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535) ... Please see attached details. At first, the pen functions normally, however after approximately 1 minute of use, it will continue to move windows but loses writing and drawing capabilities in applications. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819486] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819486 Title: Crash from :i915 module with 4.15.0-46-generic using multi-display Status in linux package in Ubuntu: Confirmed Bug description: While previously working using 4.15.0-45-generic, booting my thinkpad T480 on a dock with additional screen connected and "kernel 4.15.0-46-generic" lead to a crash of the system. Laptop is running Ubuntu 18.04.2 LTS. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: user 3449 F...m pulseaudio /dev/snd/controlC1: user 3449 F pulseaudio /dev/snd/pcmC0D0p: user 3449 F...m pulseaudio /dev/snd/controlC0: user 3449 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7 InstallationDate: Installed on 2018-06-28 (256 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20L5000AFR Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin netdev plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET37W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5000AFR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L5000AFR:pvrThinkPadT480:rvnLENOVO:rn20L5000AFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5000AFR dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819486/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811259] Re: 4.20 kernel on s390x VM crashes
Since Kernel 5.0 landed in disco's release pocket today, I'm changing the status to Fix Released. ** Changed in: linux (Ubuntu Disco) Status: Fix Committed => Fix Released ** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811259 Title: 4.20 kernel on s390x VM crashes Status in Linux: Fix Released Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Released Bug description: Booting with 4.20.0-2-generic on a s390x 2 CPU VM we hit a panic: [0.394835] Linux version 4.20.0-2-generic (buildd@bos02-s390x-015) (gcc version 8.2.0 (Ubuntu 8.2.0-13ubuntu1)) #3-Ubuntu SMP Thu Jan 3 18:43:01 UTC 2019 (Ubuntu 4.20.0-2.3-generic 4.20.0) [0.394838] setup.289988: Linux is running under KVM in 64-bit mode [0.394846] setup.b050d0: The maximum memory size is 2048MB [0.394866] numa.196305: NUMA mode: plain [0.394893] cpu.33a262: 2 configured CPUs, 0 standby CPUs [0.394999] Write protected kernel read-only data: 10464k [0.395034] Zone ranges: [0.395035] DMA [mem 0x-0x7fff] [0.395037] Normal empty [0.395038] Movable zone start for each node [0.395039] Early memory node ranges [0.395041] node 0: [mem 0x-0x7fff] [0.395042] Initmem setup node 0 [mem 0x-0x7fff] [0.413802] percpu: Embedded 25 pages/cpu @(ptrval) s62208 r8192 d32000 u102400 [0.413824] Built 1 zonelists, mobility grouping on. Total pages: 516096 [0.413825] Policy zone: DMA [0.413827] Kernel command line: root=LABEL=cloudimg-rootfs [0.450276] Memory: 2034164K/2097152K available (8116K kernel code, 1079K rwdata, 2344K rodata, 992K init, 772K bss, 62988K reserved, 0K cma-reserved) [0.450283] random: get_random_u64 called from kmem_cache_open+0x4c/0x4f0 with crng_init=0 [0.450432] SLUB: HWalign=256, Order=0-3, MinObjects=0, CPUs=3, Nodes=1 [0.450434] ftrace: allocating 27385 entries in 107 pages [0.473325] rcu: Hierarchical RCU implementation. [0.473327] rcu: RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=3. [0.473328]Tasks RCU enabled. [0.473329] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies. [0.473330] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=3 [0.475371] NR_IRQS: 3, nr_irqs: 3, preallocated irqs: 3 [0.475402] clocksource: tod: mask: 0x max_cycles: 0x3b0a9be803b0a9, max_idle_ns: 1805497147909793 ns [0.475558] printk: console [ttyS1] enabled [0.475623] pid_max: default: 32768 minimum: 301 [0.475658] LSM: Security Framework initializing [0.475660] Yama: becoming mindful. [0.475677] AppArmor: AppArmor initialized [0.476134] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes) [0.476352] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes) [0.476370] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes) [0.476377] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes) [0.476726] rcu: Hierarchical SRCU implementation. [0.476927] smp: Bringing up secondary CPUs ... [0.477181] smp: Brought up 1 node, 2 CPUs [0.477549] devtmpfs: initialized [0.477882] clocksource: jiffies: mask: 0x max_cycles: 0x, max_idle_ns: 1911260446275 ns [0.477902] futex hash table entries: 1024 (order: 6, 262144 bytes) [0.478105] NET: Registered protocol family 16 [0.478134] audit: initializing netlink subsys (disabled) [0.478183] audit: type=2000 audit(1547122707.960:1): state=initialized audit_enabled=0 res=1 [0.478222] Spectre V2 mitigation: execute trampolines [0.479205] HugeTLB registered 1.00 MiB page size, pre-allocated 0 pages [0.479623] SCSI subsystem initialized [0.479856] NetLabel: Initializing [0.479858] NetLabel: domain hash size = 128 [0.479859] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO [0.479871] NetLabel: unlabeled traffic allowed by default [0.507362] VFS: Disk quotas dquot_6.6.0 [0.507378] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [0.507486] AppArmor: AppArmor Filesystem Enabled [0.507847] NET: Registered protocol family 2 [0.507976] tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 16384 bytes) [0.507994] TCP established hash table entries: 16384 (order: 5, 131072 bytes) [0.508126] TCP bind hash table entries: 16384 (order: 6, 262144 bytes) [0.508235] TCP: Hash tables configured (established 16384 bind 16384) [0.508269] UDP hash tab
[Kernel-packages] [Bug 1819486] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1819486/+attachment/5245520/+files/IwConfig.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/1819486 Title: Crash from :i915 module with 4.15.0-46-generic using multi-display Status in linux package in Ubuntu: Confirmed Bug description: While previously working using 4.15.0-45-generic, booting my thinkpad T480 on a dock with additional screen connected and "kernel 4.15.0-46-generic" lead to a crash of the system. Laptop is running Ubuntu 18.04.2 LTS. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: user 3449 F...m pulseaudio /dev/snd/controlC1: user 3449 F pulseaudio /dev/snd/pcmC0D0p: user 3449 F...m pulseaudio /dev/snd/controlC0: user 3449 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7 InstallationDate: Installed on 2018-06-28 (256 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20L5000AFR Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin netdev plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET37W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5000AFR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L5000AFR:pvrThinkPadT480:rvnLENOVO:rn20L5000AFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5000AFR dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819486/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819486] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1819486/+attachment/5245526/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819486 Title: Crash from :i915 module with 4.15.0-46-generic using multi-display Status in linux package in Ubuntu: Confirmed Bug description: While previously working using 4.15.0-45-generic, booting my thinkpad T480 on a dock with additional screen connected and "kernel 4.15.0-46-generic" lead to a crash of the system. Laptop is running Ubuntu 18.04.2 LTS. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: user 3449 F...m pulseaudio /dev/snd/controlC1: user 3449 F pulseaudio /dev/snd/pcmC0D0p: user 3449 F...m pulseaudio /dev/snd/controlC0: user 3449 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7 InstallationDate: Installed on 2018-06-28 (256 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20L5000AFR Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin netdev plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET37W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5000AFR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L5000AFR:pvrThinkPadT480:rvnLENOVO:rn20L5000AFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5000AFR dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819486/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819486] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1819486/+attachment/5245522/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819486 Title: Crash from :i915 module with 4.15.0-46-generic using multi-display Status in linux package in Ubuntu: Confirmed Bug description: While previously working using 4.15.0-45-generic, booting my thinkpad T480 on a dock with additional screen connected and "kernel 4.15.0-46-generic" lead to a crash of the system. Laptop is running Ubuntu 18.04.2 LTS. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: user 3449 F...m pulseaudio /dev/snd/controlC1: user 3449 F pulseaudio /dev/snd/pcmC0D0p: user 3449 F...m pulseaudio /dev/snd/controlC0: user 3449 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7 InstallationDate: Installed on 2018-06-28 (256 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20L5000AFR Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin netdev plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET37W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5000AFR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L5000AFR:pvrThinkPadT480:rvnLENOVO:rn20L5000AFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5000AFR dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819486/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819486] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1819486/+attachment/5245530/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819486 Title: Crash from :i915 module with 4.15.0-46-generic using multi-display Status in linux package in Ubuntu: Confirmed Bug description: While previously working using 4.15.0-45-generic, booting my thinkpad T480 on a dock with additional screen connected and "kernel 4.15.0-46-generic" lead to a crash of the system. Laptop is running Ubuntu 18.04.2 LTS. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: user 3449 F...m pulseaudio /dev/snd/controlC1: user 3449 F pulseaudio /dev/snd/pcmC0D0p: user 3449 F...m pulseaudio /dev/snd/controlC0: user 3449 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7 InstallationDate: Installed on 2018-06-28 (256 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20L5000AFR Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin netdev plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET37W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5000AFR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L5000AFR:pvrThinkPadT480:rvnLENOVO:rn20L5000AFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5000AFR dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819486/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819486] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1819486/+attachment/5245521/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819486 Title: Crash from :i915 module with 4.15.0-46-generic using multi-display Status in linux package in Ubuntu: Confirmed Bug description: While previously working using 4.15.0-45-generic, booting my thinkpad T480 on a dock with additional screen connected and "kernel 4.15.0-46-generic" lead to a crash of the system. Laptop is running Ubuntu 18.04.2 LTS. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: user 3449 F...m pulseaudio /dev/snd/controlC1: user 3449 F pulseaudio /dev/snd/pcmC0D0p: user 3449 F...m pulseaudio /dev/snd/controlC0: user 3449 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7 InstallationDate: Installed on 2018-06-28 (256 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20L5000AFR Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin netdev plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET37W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5000AFR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L5000AFR:pvrThinkPadT480:rvnLENOVO:rn20L5000AFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5000AFR dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819486/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819486] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1819486/+attachment/5245527/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819486 Title: Crash from :i915 module with 4.15.0-46-generic using multi-display Status in linux package in Ubuntu: Confirmed Bug description: While previously working using 4.15.0-45-generic, booting my thinkpad T480 on a dock with additional screen connected and "kernel 4.15.0-46-generic" lead to a crash of the system. Laptop is running Ubuntu 18.04.2 LTS. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: user 3449 F...m pulseaudio /dev/snd/controlC1: user 3449 F pulseaudio /dev/snd/pcmC0D0p: user 3449 F...m pulseaudio /dev/snd/controlC0: user 3449 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7 InstallationDate: Installed on 2018-06-28 (256 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20L5000AFR Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin netdev plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET37W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5000AFR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L5000AFR:pvrThinkPadT480:rvnLENOVO:rn20L5000AFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5000AFR dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819486/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819486] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1819486/+attachment/5245529/+files/RfKill.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/1819486 Title: Crash from :i915 module with 4.15.0-46-generic using multi-display Status in linux package in Ubuntu: Confirmed Bug description: While previously working using 4.15.0-45-generic, booting my thinkpad T480 on a dock with additional screen connected and "kernel 4.15.0-46-generic" lead to a crash of the system. Laptop is running Ubuntu 18.04.2 LTS. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: user 3449 F...m pulseaudio /dev/snd/controlC1: user 3449 F pulseaudio /dev/snd/pcmC0D0p: user 3449 F...m pulseaudio /dev/snd/controlC0: user 3449 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7 InstallationDate: Installed on 2018-06-28 (256 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20L5000AFR Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin netdev plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET37W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5000AFR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L5000AFR:pvrThinkPadT480:rvnLENOVO:rn20L5000AFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5000AFR dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819486/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819486] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1819486/+attachment/5245518/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819486 Title: Crash from :i915 module with 4.15.0-46-generic using multi-display Status in linux package in Ubuntu: Confirmed Bug description: While previously working using 4.15.0-45-generic, booting my thinkpad T480 on a dock with additional screen connected and "kernel 4.15.0-46-generic" lead to a crash of the system. Laptop is running Ubuntu 18.04.2 LTS. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: user 3449 F...m pulseaudio /dev/snd/controlC1: user 3449 F pulseaudio /dev/snd/pcmC0D0p: user 3449 F...m pulseaudio /dev/snd/controlC0: user 3449 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7 InstallationDate: Installed on 2018-06-28 (256 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20L5000AFR Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin netdev plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET37W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5000AFR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L5000AFR:pvrThinkPadT480:rvnLENOVO:rn20L5000AFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5000AFR dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819486/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819486] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1819486/+attachment/5245528/+files/PulseList.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/1819486 Title: Crash from :i915 module with 4.15.0-46-generic using multi-display Status in linux package in Ubuntu: Confirmed Bug description: While previously working using 4.15.0-45-generic, booting my thinkpad T480 on a dock with additional screen connected and "kernel 4.15.0-46-generic" lead to a crash of the system. Laptop is running Ubuntu 18.04.2 LTS. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: user 3449 F...m pulseaudio /dev/snd/controlC1: user 3449 F pulseaudio /dev/snd/pcmC0D0p: user 3449 F...m pulseaudio /dev/snd/controlC0: user 3449 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7 InstallationDate: Installed on 2018-06-28 (256 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20L5000AFR Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin netdev plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET37W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5000AFR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L5000AFR:pvrThinkPadT480:rvnLENOVO:rn20L5000AFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5000AFR dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819486/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819486] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1819486/+attachment/5245519/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819486 Title: Crash from :i915 module with 4.15.0-46-generic using multi-display Status in linux package in Ubuntu: Confirmed Bug description: While previously working using 4.15.0-45-generic, booting my thinkpad T480 on a dock with additional screen connected and "kernel 4.15.0-46-generic" lead to a crash of the system. Laptop is running Ubuntu 18.04.2 LTS. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: user 3449 F...m pulseaudio /dev/snd/controlC1: user 3449 F pulseaudio /dev/snd/pcmC0D0p: user 3449 F...m pulseaudio /dev/snd/controlC0: user 3449 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7 InstallationDate: Installed on 2018-06-28 (256 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20L5000AFR Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin netdev plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET37W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5000AFR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L5000AFR:pvrThinkPadT480:rvnLENOVO:rn20L5000AFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5000AFR dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819486/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819486] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1819486/+attachment/5245525/+files/ProcEnviron.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/1819486 Title: Crash from :i915 module with 4.15.0-46-generic using multi-display Status in linux package in Ubuntu: Confirmed Bug description: While previously working using 4.15.0-45-generic, booting my thinkpad T480 on a dock with additional screen connected and "kernel 4.15.0-46-generic" lead to a crash of the system. Laptop is running Ubuntu 18.04.2 LTS. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: user 3449 F...m pulseaudio /dev/snd/controlC1: user 3449 F pulseaudio /dev/snd/pcmC0D0p: user 3449 F...m pulseaudio /dev/snd/controlC0: user 3449 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7 InstallationDate: Installed on 2018-06-28 (256 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20L5000AFR Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin netdev plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET37W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5000AFR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L5000AFR:pvrThinkPadT480:rvnLENOVO:rn20L5000AFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5000AFR dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819486/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819486] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1819486/+attachment/5245531/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819486 Title: Crash from :i915 module with 4.15.0-46-generic using multi-display Status in linux package in Ubuntu: Confirmed Bug description: While previously working using 4.15.0-45-generic, booting my thinkpad T480 on a dock with additional screen connected and "kernel 4.15.0-46-generic" lead to a crash of the system. Laptop is running Ubuntu 18.04.2 LTS. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: user 3449 F...m pulseaudio /dev/snd/controlC1: user 3449 F pulseaudio /dev/snd/pcmC0D0p: user 3449 F...m pulseaudio /dev/snd/controlC0: user 3449 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7 InstallationDate: Installed on 2018-06-28 (256 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20L5000AFR Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin netdev plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET37W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5000AFR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L5000AFR:pvrThinkPadT480:rvnLENOVO:rn20L5000AFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5000AFR dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819486/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819486] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1819486/+attachment/5245523/+files/ProcCpuinfo.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/1819486 Title: Crash from :i915 module with 4.15.0-46-generic using multi-display Status in linux package in Ubuntu: Confirmed Bug description: While previously working using 4.15.0-45-generic, booting my thinkpad T480 on a dock with additional screen connected and "kernel 4.15.0-46-generic" lead to a crash of the system. Laptop is running Ubuntu 18.04.2 LTS. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: user 3449 F...m pulseaudio /dev/snd/controlC1: user 3449 F pulseaudio /dev/snd/pcmC0D0p: user 3449 F...m pulseaudio /dev/snd/controlC0: user 3449 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7 InstallationDate: Installed on 2018-06-28 (256 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20L5000AFR Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin netdev plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET37W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5000AFR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L5000AFR:pvrThinkPadT480:rvnLENOVO:rn20L5000AFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5000AFR dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819486/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819486] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1819486/+attachment/5245524/+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/1819486 Title: Crash from :i915 module with 4.15.0-46-generic using multi-display Status in linux package in Ubuntu: Confirmed Bug description: While previously working using 4.15.0-45-generic, booting my thinkpad T480 on a dock with additional screen connected and "kernel 4.15.0-46-generic" lead to a crash of the system. Laptop is running Ubuntu 18.04.2 LTS. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: user 3449 F...m pulseaudio /dev/snd/controlC1: user 3449 F pulseaudio /dev/snd/pcmC0D0p: user 3449 F...m pulseaudio /dev/snd/controlC0: user 3449 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7 InstallationDate: Installed on 2018-06-28 (256 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20L5000AFR Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin netdev plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET37W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5000AFR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L5000AFR:pvrThinkPadT480:rvnLENOVO:rn20L5000AFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5000AFR dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819486/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819486] Re: Crash from :i915 module with 4.15.0-46-generic using multi-display
apport information ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Tags added: apport-collected ** Description changed: While previously working using 4.15.0-45-generic, booting my thinkpad T480 on a dock with additional screen connected and "kernel 4.15.0-46-generic" lead to a crash of the system. Laptop is running Ubuntu 18.04.2 LTS. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.5 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/pcmC1D0c: user 3449 F...m pulseaudio + /dev/snd/controlC1: user 3449 F pulseaudio + /dev/snd/pcmC0D0p: user 3449 F...m pulseaudio + /dev/snd/controlC0: user 3449 F pulseaudio + CurrentDesktop: X-Cinnamon + DistroRelease: Ubuntu 18.04 + HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7 + InstallationDate: Installed on 2018-06-28 (256 days ago) + InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) + MachineType: LENOVO 20L5000AFR + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash + ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-45-generic N/A + linux-backports-modules-4.15.0-45-generic N/A + linux-firmware 1.173.3 + Tags: bionic + Uname: Linux 4.15.0-45-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip docker libvirt lpadmin netdev plugdev sambashare sudo vboxusers wireshark + _MarkForUpload: True + dmi.bios.date: 03/14/2018 + dmi.bios.vendor: LENOVO + dmi.bios.version: N24ET37W (1.12 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 20L5000AFR + dmi.board.vendor: LENOVO + dmi.board.version: SDK0J40697 WIN + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: None + dmi.modalias: dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L5000AFR:pvrThinkPadT480:rvnLENOVO:rn20L5000AFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: + dmi.product.family: ThinkPad T480 + dmi.product.name: 20L5000AFR + dmi.product.version: ThinkPad T480 + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1819486/+attachment/5245517/+files/AlsaInfo.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/1819486 Title: Crash from :i915 module with 4.15.0-46-generic using multi-display Status in linux package in Ubuntu: Confirmed Bug description: While previously working using 4.15.0-45-generic, booting my thinkpad T480 on a dock with additional screen connected and "kernel 4.15.0-46-generic" lead to a crash of the system. Laptop is running Ubuntu 18.04.2 LTS. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: user 3449 F...m pulseaudio /dev/snd/controlC1: user 3449 F pulseaudio /dev/snd/pcmC0D0p: user 3449 F...m pulseaudio /dev/snd/controlC0: user 3449 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7 InstallationDate: Installed on 2018-06-28 (256 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20L5000AFR Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin netdev plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET37W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5000AFR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L5000AFR:pvrThinkPadT480:rvnLENOVO:rn20L5000AFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5000AFR dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO To manage notificat
[Kernel-packages] [Bug 1690085]
Try idle=halt! It is the workaround that fixes the random freezes! You don't need anything else (at least not with Ryzen 1*** and 2***U processors, as it works wonders on my desktop with a 1600 and my notebook with a 2700U). IDLE=HALT IS THE WORKAROUND THAT FIXES THIS BULLSHIT! I REPEAT: IDLE=HALT! It will probably work for most of you too! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-041100-generic x86_64 UnreportableReason: The running k
[Kernel-packages] [Bug 1819493] Re: network loss and traffic loss problems with i40e 2.1.14-k in Xenial HWE Kernel 4.15
** Description changed: - network loss and traffic loss problems experienced by customer with i40e 2.1.14-k in Xenial HWE Kernel 4.15 - The traffic issues were reported from our customer deployments and we had Intel helping us with the troubleshooting of the problem. Intel recommends and customer requests application of the following commit.e78d9a39fd06109022d11c8ca444cfcec2abb290 (patch) + [SRU Justification] - Per customer urgent request, kernel team is requested to SRU fix to - enable support of the fixed image deployed by a large telco customer for - several years potentially. + = Impact = + + Network loss and traffic loss problems experienced by customer with i40e 2.1.14-k in Xenial HWE Kernel 4.15 + The traffic issues were reported from our customer deployments and we had Intel helping us with the troubleshooting of the problem. + + = Fix = + + Intel recommends and customer requests application of the following + commit e78d9a39fd06109022d11c8ca444cfcec2abb290 (upstream Linus tree) + + = Testcase = + + The issue could only be seen in customer environment. Regression testing + only would be possible. + + = Regression Potential = + + Change is limited to a specific driver, testing should show if there is + any negative impact. ** Changed in: linux (Ubuntu Xenial) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1819493 Title: network loss and traffic loss problems with i40e 2.1.14-k in Xenial HWE Kernel 4.15 Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Bug description: [SRU Justification] = Impact = Network loss and traffic loss problems experienced by customer with i40e 2.1.14-k in Xenial HWE Kernel 4.15 The traffic issues were reported from our customer deployments and we had Intel helping us with the troubleshooting of the problem. = Fix = Intel recommends and customer requests application of the following commit e78d9a39fd06109022d11c8ca444cfcec2abb290 (upstream Linus tree) = Testcase = The issue could only be seen in customer environment. Regression testing only would be possible. = Regression Potential = Change is limited to a specific driver, testing should show if there is any negative impact. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819493/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1690085]
Here (Asus CrossHair VI, 1600, gentoo with any kernel around), no suggested workaround works. The system freezes when in very light use and I was never able to obtain a single line of debug via serial (I put a small linux mini itx box near this computer just to receive the serial log). It seems like after a workaround is applied (BIOS settings, iddle=halt, rcu_nocbs=0-11 and so on), the BAI (Bug AI) finds a way to freeze the system again and the dances restart. Ryzen is not a CPU to run Linux onto. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, n
[Kernel-packages] [Bug 1690085]
Hi ! I haven’t read all the comments here because there are too many by now, but I’m puzzled that many consider this to be a Linux-only issue, because I can tell you that it definitely happens on Windows (10) too, and I found other people with the same freeze/reboot problem on Windows. For me the crashes are really the same on both Linux and Windows. I have a Ryzen 7 1700X and an Asrock X370 Taichi mainboard, and the "Power Supply Idle Control" > "Typical Current Idle" setting fixes the problem. However, lately I’ve noticed a couple of times, but still rarely, that the computer would crash and reboot when waking up from sleep, then it seems to enter a boot loop for a few times, and then starts normally but it resets the BIOS settings… I haven’t overclocked anything. My CPU also seems to have the "Ryzen segfault bug", which seems to be a different issue from what I’ve understood. I should probably RMA the CPU (and the mainboard ?), but I haven’t because disassembling everything would be difficult for me. In my case those crashes (without "Typical Current Idle") happen fairly rarely, like every two-three weeks, or even more rarely than that. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors
[Kernel-packages] [Bug 1819362] Re: HUAWEI E3531 HSPA+ USB Stick "please report the device ID to the Linux USB developers"
The same happens with 5.0.0 (it is the uppermost folder in the mainline builds, but I think it is older than 5.0.1). Still, I can reproduce the bug with both of them. ** Tags added: kernel-bug-exists-upstream-5.0.0 ** 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/1819362 Title: HUAWEI E3531 HSPA+ USB Stick "please report the device ID to the Linux USB developers" Status in linux package in Ubuntu: Confirmed Bug description: I have a HUAWEI E3531 HSPA+ USB Stick When I plug it in, journalctl shows me Mär 10 19:21:20 pshp usb_modeswitch[3556]: usb_modeswitch: switched to 12d1:14dc on 1/9 Mär 10 19:21:20 pshp kernel: scsi 1:0:0:0: Direct-Access HUAWEI TF CARD Storage 2.31 PQ: 0 ANSI: 2 Mär 10 19:21:20 pshp kernel: sd 1:0:0:0: Attached scsi generic sg0 type 0 Mär 10 19:21:20 pshp kernel: sd 1:0:0:0: [sda] Attached SCSI removable disk Mär 10 19:21:21 pshp usb_modeswitch_dispatcher[3556]: Unable to open bind list file: No such file or directory Mär 10 19:21:21 pshp usb_modeswitch[3556]: usb_modeswitch: add device ID 12d1:14dc to driver option Mär 10 19:21:21 pshp usb_modeswitch[3556]: usb_modeswitch: please report the device ID to the Linux USB developers! Mär 10 19:21:22 pshp ModemManager[860]: Couldn't check support for device at '/sys/devices/pci:00/:00:14.0/usb1/1-1': not supported by any plugin And the modem does not work (no ttyUSBX appears) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.18.0-15-generic 4.18.0-15.16~18.04.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 10 19:17:23 2019 EcryptfsInUse: Yes SourcePackage: linux-signed-hwe UpgradeStatus: Upgraded to bionic on 2018-07-01 (252 days ago) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ps 1825 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=f51203fe-7748-4c6c-b60e-becfac3f8f93 MachineType: HP HP EliteBook 820 G4 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=ef37c096-b516-41e7-89ce-be7432f1677e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 Tags: bionic wayland-session Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-01 (252 days ago) UserGroups: adm cdrom dip gsmsms lpadmin plugdev sambashare scanner sudo _MarkForUpload: True dmi.bios.date: 10/17/2017 dmi.bios.vendor: HP dmi.bios.version: P78 Ver. 01.08 dmi.board.name: 8292 dmi.board.vendor: HP dmi.board.version: KBC Version 45.3C dmi.chassis.asset.tag: 5CG7453N9P dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP78Ver.01.08:bd10/17/2017:svnHP:pnHPEliteBook820G4:pvr:rvnHP:rn8292:rvrKBCVersion45.3C:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 820 G4 dmi.product.sku: X3T22AV dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ps 1825 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=f51203fe-7748-4c6c-b60e-becfac3f8f93 MachineType: HP HP EliteBook 820 G4 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=ef37c096-b516-41e7-89ce-be7432f1677e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 Tags: bionic wayland-session Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-01 (252 days ago) UserGroups: adm cdrom dip gsmsms lpadmin plugdev sambashare scanner sudo _MarkForUpload: True dmi.bios.date: 10/17/2017 dmi.bios.vendor: HP dmi.bios.version: P78 Ver. 01.08 dmi.board.name: 8292 dmi.board.vendor: HP dmi.board.version: KBC Version 45.3C dmi.chassis.asset.tag: 5CG7453N9P dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP78Ver.01.08:bd10/17/2
[Kernel-packages] [Bug 1819493] 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 1819493 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 ** Changed in: linux (Ubuntu Bionic) Status: New => Incomplete ** Changed in: linux (Ubuntu Xenial) Status: New => Incomplete ** Tags added: xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819493 Title: network loss and traffic loss problems with i40e 2.1.14-k in Xenial HWE Kernel 4.15 Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Status in linux source package in Bionic: Incomplete Bug description: network loss and traffic loss problems experienced by customer with i40e 2.1.14-k in Xenial HWE Kernel 4.15 The traffic issues were reported from our customer deployments and we had Intel helping us with the troubleshooting of the problem. Intel recommends and customer requests application of the following commit.e78d9a39fd06109022d11c8ca444cfcec2abb290 (patch) Per customer urgent request, kernel team is requested to SRU fix to enable support of the fixed image deployed by a large telco customer for several years potentially. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819493/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819493] Re: network loss and traffic loss problems with i40e 2.1.14-k in Xenial HWE Kernel 4.15
** Description changed: - network loss and traffic loss problems experienced by customer with i40e 2.1.14-k in Xenial HWE Kernel 4.15 - The traffic issues were reported from our customer deployments and we had Intel helping us with the troubleshooting of the problem. Their conclusion was that this fix https://www.spinics.net/lists/netdev/msg520752.html should solve our reported issue. + network loss and traffic loss problems experienced by customer with i40e 2.1.14-k in Xenial HWE Kernel 4.15 + The traffic issues were reported from our customer deployments and we had Intel helping us with the troubleshooting of the problem. Intel recommends and customer requests application of the following commit.e78d9a39fd06109022d11c8ca444cfcec2abb290 (patch) + + Per customer urgent request, kernel team is requested to SRU fix to + enable support of the fixed image deployed by a large telco customer for + several years potentially. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819493 Title: network loss and traffic loss problems with i40e 2.1.14-k in Xenial HWE Kernel 4.15 Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Status in linux source package in Bionic: Incomplete Bug description: network loss and traffic loss problems experienced by customer with i40e 2.1.14-k in Xenial HWE Kernel 4.15 The traffic issues were reported from our customer deployments and we had Intel helping us with the troubleshooting of the problem. Intel recommends and customer requests application of the following commit.e78d9a39fd06109022d11c8ca444cfcec2abb290 (patch) Per customer urgent request, kernel team is requested to SRU fix to enable support of the fixed image deployed by a large telco customer for several years potentially. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819493/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819362] Re: HUAWEI E3531 HSPA+ USB Stick "please report the device ID to the Linux USB developers"
Dear Christopher Penalver, I also updated the tags and set to confirmed. Thank you for the clear and explicit instructions! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819362 Title: HUAWEI E3531 HSPA+ USB Stick "please report the device ID to the Linux USB developers" Status in linux package in Ubuntu: Confirmed Bug description: I have a HUAWEI E3531 HSPA+ USB Stick When I plug it in, journalctl shows me Mär 10 19:21:20 pshp usb_modeswitch[3556]: usb_modeswitch: switched to 12d1:14dc on 1/9 Mär 10 19:21:20 pshp kernel: scsi 1:0:0:0: Direct-Access HUAWEI TF CARD Storage 2.31 PQ: 0 ANSI: 2 Mär 10 19:21:20 pshp kernel: sd 1:0:0:0: Attached scsi generic sg0 type 0 Mär 10 19:21:20 pshp kernel: sd 1:0:0:0: [sda] Attached SCSI removable disk Mär 10 19:21:21 pshp usb_modeswitch_dispatcher[3556]: Unable to open bind list file: No such file or directory Mär 10 19:21:21 pshp usb_modeswitch[3556]: usb_modeswitch: add device ID 12d1:14dc to driver option Mär 10 19:21:21 pshp usb_modeswitch[3556]: usb_modeswitch: please report the device ID to the Linux USB developers! Mär 10 19:21:22 pshp ModemManager[860]: Couldn't check support for device at '/sys/devices/pci:00/:00:14.0/usb1/1-1': not supported by any plugin And the modem does not work (no ttyUSBX appears) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.18.0-15-generic 4.18.0-15.16~18.04.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 10 19:17:23 2019 EcryptfsInUse: Yes SourcePackage: linux-signed-hwe UpgradeStatus: Upgraded to bionic on 2018-07-01 (252 days ago) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ps 1825 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=f51203fe-7748-4c6c-b60e-becfac3f8f93 MachineType: HP HP EliteBook 820 G4 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=ef37c096-b516-41e7-89ce-be7432f1677e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 Tags: bionic wayland-session Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-01 (252 days ago) UserGroups: adm cdrom dip gsmsms lpadmin plugdev sambashare scanner sudo _MarkForUpload: True dmi.bios.date: 10/17/2017 dmi.bios.vendor: HP dmi.bios.version: P78 Ver. 01.08 dmi.board.name: 8292 dmi.board.vendor: HP dmi.board.version: KBC Version 45.3C dmi.chassis.asset.tag: 5CG7453N9P dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP78Ver.01.08:bd10/17/2017:svnHP:pnHPEliteBook820G4:pvr:rvnHP:rn8292:rvrKBCVersion45.3C:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 820 G4 dmi.product.sku: X3T22AV dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ps 1825 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=f51203fe-7748-4c6c-b60e-becfac3f8f93 MachineType: HP HP EliteBook 820 G4 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=ef37c096-b516-41e7-89ce-be7432f1677e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 Tags: bionic wayland-session Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-01 (252 days ago) UserGroups: adm cdrom dip gsmsms lpadmin plugdev sambashare scanner sudo _MarkForUpload: True dmi.bios.date: 10/17/2017 dmi.bios.vendor: HP dmi.bios.version: P78 Ver. 01.08 dmi.board.name: 8292 dmi.board.vendor: HP dmi.board.version: KBC Version 45.3C dmi.chassis.asset.tag: 5CG7453N9P dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP78Ver.01.08:bd10/17/2017:svnHP:pnHPEliteBook820G4:pvr:rvnHP:rn8292:rvrKBCVersion45.3C:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook
[Kernel-packages] [Bug 1819493] Re: network loss and traffic loss problems with i40e 2.1.14-k in Xenial HWE Kernel 4.15
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819493 Title: network loss and traffic loss problems with i40e 2.1.14-k in Xenial HWE Kernel 4.15 Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Status in linux source package in Bionic: Incomplete Bug description: network loss and traffic loss problems experienced by customer with i40e 2.1.14-k in Xenial HWE Kernel 4.15 The traffic issues were reported from our customer deployments and we had Intel helping us with the troubleshooting of the problem. Intel recommends and customer requests application of the following commit.e78d9a39fd06109022d11c8ca444cfcec2abb290 (patch) Per customer urgent request, kernel team is requested to SRU fix to enable support of the fixed image deployed by a large telco customer for several years potentially. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819493/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819362] Re: HUAWEI E3531 HSPA+ USB Stick "please report the device ID to the Linux USB developers"
I tested with linux-image- unsigned-5.0.1-050001-generic_5.0.1-050001.201903100732_amd64.deb and linux-modules-5.0.1-050001-generic_5.0.1-050001.201903100732_amd64.deb and it still shows the same behavior: Mär 11 18:10:01 pshp usb_modeswitch[2143]: usb_modeswitch: switched to 12d1:14dc on 1/6 Mär 11 18:10:02 pshp kernel: scsi 1:0:0:0: Direct-Access HUAWEI TF CARD Storage 2.31 PQ: 0 ANSI: 2 Mär 11 18:10:02 pshp kernel: sd 1:0:0:0: Attached scsi generic sg0 type 0 Mär 11 18:10:02 pshp kernel: sd 1:0:0:0: [sda] Attached SCSI removable disk Mär 11 18:10:02 pshp usb_modeswitch_dispatcher[2143]: Unable to open bind list file: No such file or directory Mär 11 18:10:02 pshp kernel: usbcore: registered new interface driver usbserial_generic Mär 11 18:10:02 pshp kernel: usbserial: USB Serial support registered for generic Mär 11 18:10:02 pshp usb_modeswitch[2143]: usb_modeswitch: add device ID 12d1:14dc to driver option Mär 11 18:10:02 pshp usb_modeswitch[2143]: usb_modeswitch: please report the device ID to the Linux USB developers! ** Tags added: kernel-bug-exists-upstream kernel-bug-exists- upstream-5.0.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819362 Title: HUAWEI E3531 HSPA+ USB Stick "please report the device ID to the Linux USB developers" Status in linux package in Ubuntu: Confirmed Bug description: I have a HUAWEI E3531 HSPA+ USB Stick When I plug it in, journalctl shows me Mär 10 19:21:20 pshp usb_modeswitch[3556]: usb_modeswitch: switched to 12d1:14dc on 1/9 Mär 10 19:21:20 pshp kernel: scsi 1:0:0:0: Direct-Access HUAWEI TF CARD Storage 2.31 PQ: 0 ANSI: 2 Mär 10 19:21:20 pshp kernel: sd 1:0:0:0: Attached scsi generic sg0 type 0 Mär 10 19:21:20 pshp kernel: sd 1:0:0:0: [sda] Attached SCSI removable disk Mär 10 19:21:21 pshp usb_modeswitch_dispatcher[3556]: Unable to open bind list file: No such file or directory Mär 10 19:21:21 pshp usb_modeswitch[3556]: usb_modeswitch: add device ID 12d1:14dc to driver option Mär 10 19:21:21 pshp usb_modeswitch[3556]: usb_modeswitch: please report the device ID to the Linux USB developers! Mär 10 19:21:22 pshp ModemManager[860]: Couldn't check support for device at '/sys/devices/pci:00/:00:14.0/usb1/1-1': not supported by any plugin And the modem does not work (no ttyUSBX appears) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.18.0-15-generic 4.18.0-15.16~18.04.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 10 19:17:23 2019 EcryptfsInUse: Yes SourcePackage: linux-signed-hwe UpgradeStatus: Upgraded to bionic on 2018-07-01 (252 days ago) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ps 1825 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=f51203fe-7748-4c6c-b60e-becfac3f8f93 MachineType: HP HP EliteBook 820 G4 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=ef37c096-b516-41e7-89ce-be7432f1677e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 Tags: bionic wayland-session Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-01 (252 days ago) UserGroups: adm cdrom dip gsmsms lpadmin plugdev sambashare scanner sudo _MarkForUpload: True dmi.bios.date: 10/17/2017 dmi.bios.vendor: HP dmi.bios.version: P78 Ver. 01.08 dmi.board.name: 8292 dmi.board.vendor: HP dmi.board.version: KBC Version 45.3C dmi.chassis.asset.tag: 5CG7453N9P dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP78Ver.01.08:bd10/17/2017:svnHP:pnHPEliteBook820G4:pvr:rvnHP:rn8292:rvrKBCVersion45.3C:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 820 G4 dmi.prod
[Kernel-packages] [Bug 1819493] [NEW] network loss and traffic loss problems with i40e 2.1.14-k in Xenial HWE Kernel 4.15
Public bug reported: network loss and traffic loss problems experienced by customer with i40e 2.1.14-k in Xenial HWE Kernel 4.15 The traffic issues were reported from our customer deployments and we had Intel helping us with the troubleshooting of the problem. Their conclusion was that this fix https://www.spinics.net/lists/netdev/msg520752.html should solve our reported issue. ** Affects: linux (Ubuntu) Importance: Medium Status: Incomplete ** Affects: linux (Ubuntu Xenial) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Bionic) Importance: Undecided Status: Incomplete ** Tags: xenial ** Package changed: linux-azure (Ubuntu) => linux (Ubuntu) -- 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/1819493 Title: network loss and traffic loss problems with i40e 2.1.14-k in Xenial HWE Kernel 4.15 Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Status in linux source package in Bionic: Incomplete Bug description: network loss and traffic loss problems experienced by customer with i40e 2.1.14-k in Xenial HWE Kernel 4.15 The traffic issues were reported from our customer deployments and we had Intel helping us with the troubleshooting of the problem. Their conclusion was that this fix https://www.spinics.net/lists/netdev/msg520752.html should solve our reported issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819493/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814069] Re: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2
Is it possible to collect dmesg? Boot with latest Ubuntu kernel with kernel parameter "blacklist=hv_netvsc modprobe.blacklist=hv_netvsc", then run `sudo modprobe hv_netvsc`. Attach dmesg afterward. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814069 Title: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2 Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu stuck on booting on HyperV Server 2008R2. I saw kernel messages, seems to load ram image the boot is stuck. Seems to be a problem with hyperv drivers propably harddrive. Reverted back to the previous kernel. Description:Ubuntu 18.04.1 LTS Release:18.04Description:Ubuntu 18.04.1 LTS Release:18.04 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 31 08:52 seq crw-rw 1 root audio 116, 33 Jan 31 08:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 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' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=86036ccb-bc11-11e8-93c9-00155dfd7535 ro maybe-ubiquity ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090004 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 8531-7125-9206-2460-7819-2663-90 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090004:bd03/19/2009:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: dmi.product.name: Virtual Machine dmi.product.version: 7.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814684] Re: [19.04 FEAT] [LS1801] PCI Virtual function enablement
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814684 Title: [19.04 FEAT] [LS1801] PCI Virtual function enablement Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Description: The common code Linux kernel PCI bus driver performs initialization steps of PCI virtual functions (SRIOV) in an order that is incompatible with Z firmware requirements. As a result, virtual functions cannot be used properly. This item is about ensuring that PCI virtual functions can be correctly enabled in Linux. Tentativ target ; kernel 5.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1814684/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818519] Re: linux: 5.0.0-7.8 -proposed tracker
All tasks have been completed and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow/promote-to-release Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: -- swm properties -- boot-testing-requested: true phase: Ready for Release phase-changed: Monday, 11. March 2019 14:31 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-release: Pending -- ready to copy ** Tags removed: kernel-release-tracking-bug-live -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818519 Title: linux: 5.0.0-7.8 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: -- swm properties -- boot-testing-requested: true phase: Ready for Release phase-changed: Monday, 11. March 2019 14:31 UTC proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1818519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819490] [NEW] API mismatch: the client has the version 390.116, but this kernel module has the version 390.77
Public bug reported: After system update Nvidia proprietary driver is not working anymore. Default 18.04 install fully updated. Hardware: GTX 1080 Kernel: 4.15.0-46-generic Xorg.log: [ 5.855] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the [ 5.855] (EE) NVIDIA: system's kernel log for additional error messages and [ 5.855] (EE) NVIDIA: consult the NVIDIA README for details. [ 5.855] (EE) [drm] Failed to open DRM device for (null): -2 [ 5.855] (EE) [drm] Failed to open DRM device for (null): -2 [ 5.855] (EE) [drm] Failed to open DRM device for pci::0a:00.0: -2 [ 5.855] (EE) [drm] Failed to open DRM device for pci::0a:00.0: -2 [ 5.856] (EE) Screen 0 deleted because of no matching config section. [ 5.861] (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found) syslog: Mar 11 17:07:34 mysystem kernel: [ 65.860371] NVRM: API mismatch: the client has the version 390.116, but Mar 11 17:07:34 mysystem kernel: [ 65.860371] NVRM: this kernel module has the version 390.77. Please Mar 11 17:07:34 mysystem kernel: [ 65.860371] NVRM: make sure that this kernel module and all NVIDIA driver Mar 11 17:07:34 mysystem kernel: [ 65.860371] NVRM: components have the same version. nvidia-smi: Failed to initialize NVML: Driver/library version mismatch ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-390 390.116-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: MATE Date: Mon Mar 11 17:24:06 2019 InstallationDate: Installed on 2018-08-09 (213 days ago) InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic nvidia -- 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/1819490 Title: API mismatch: the client has the version 390.116, but this kernel module has the version 390.77 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: After system update Nvidia proprietary driver is not working anymore. Default 18.04 install fully updated. Hardware: GTX 1080 Kernel: 4.15.0-46-generic Xorg.log: [ 5.855] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the [ 5.855] (EE) NVIDIA: system's kernel log for additional error messages and [ 5.855] (EE) NVIDIA: consult the NVIDIA README for details. [ 5.855] (EE) [drm] Failed to open DRM device for (null): -2 [ 5.855] (EE) [drm] Failed to open DRM device for (null): -2 [ 5.855] (EE) [drm] Failed to open DRM device for pci::0a:00.0: -2 [ 5.855] (EE) [drm] Failed to open DRM device for pci::0a:00.0: -2 [ 5.856] (EE) Screen 0 deleted because of no matching config section. [ 5.861] (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found) syslog: Mar 11 17:07:34 mysystem kernel: [ 65.860371] NVRM: API mismatch: the client has the version 390.116, but Mar 11 17:07:34 mysystem kernel: [ 65.860371] NVRM: this kernel module has the version 390.77. Please Mar 11 17:07:34 mysystem kernel: [ 65.860371] NVRM: make sure that this kernel module and all NVIDIA driver Mar 11 17:07:34 mysystem kernel: [ 65.860371] NVRM: components have the same version. nvidia-smi: Failed to initialize NVML: Driver/library version mismatch ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-390 390.116-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: MATE Date: Mon Mar 11 17:24:06 2019 InstallationDate: Installed on 2018-08-09 (213 days ago) InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: nvidia-graphics-drivers-390 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/1819490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815733] Re: unnecessary request_queue freeze
This bug was fixed in the package linux - 5.0.0-7.8 --- linux (5.0.0-7.8) disco; urgency=medium * linux: 5.0.0-7.8 -proposed tracker (LP: #1818519) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * unnecessary request_queue freeze (LP: #1815733) - block: avoid setting nr_requests to current value - block: avoid setting none scheduler if it's already none * Miscellaneous Ubuntu changes - SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on xfail - update dkms package versions [ Upstream Kernel Changes ] * Rebase to v5.0 -- Seth Forshee Mon, 04 Mar 2019 08:46:10 -0600 ** Changed in: linux (Ubuntu Disco) 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/1815733 Title: unnecessary request_queue freeze Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Status in linux source package in Disco: Fix Released Bug description: Hi all, In linux-4.15, which is used as hwe-edge in xenial, there's an unexpected behavior. It results in latency spikes of generic_make_request() function call. How to reproduce: 1. Run fio: fio --name=test --rw=randwrite --direct=1 --filename=/dev/sdt --iodepth=1 --fsync=1 --ioengine=libaio --write_lat_log loglat 2. While fio is writing to the device, change nr_requests setting to the same value as current: echo 256 > /sys/block/sdt/queue/nr_requests or: if scheduler is already none: echo none > /sys/block/sdt/queue/scheduler 3. Stop fio and check slat log: ... 3980, 16, 1, 4096 3999, 17, 1, 4096 4010, 19, 1, 4096 4020, 18, 1, 4096 4045, 10821, 1, 4096 4054, 25, 1, 4096 4070, 12, 1, 4096 4083, 17, 1, 4096 4094, 16, 1, 4096 4111, 17, 1, 4096 ... There're a few patches to fix this behavior: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git/commit/?h=for-5.1/block&id=e5fa81408fb43ebabde65938ef8b20ae879017e7 https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git/commit/?h=for-5.1/block&id=fbd72127c975dc8e532ecc73d52f3b1b00935bec This behavior affects production systems, because every change uevent triggers udev to change settings prior to udev rules. Some software, for example arcconf (tool for managing adaptec HBA adapters) triggers uevents for every block device. So, every call to arcconf utility results in latency spike. Could this be backported to 4.15 kernel for xenial/bionic? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815733/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1803206] Re: Please enable CONFIG_DMA_CMA=y on arm64
This bug was fixed in the package linux - 5.0.0-7.8 --- linux (5.0.0-7.8) disco; urgency=medium * linux: 5.0.0-7.8 -proposed tracker (LP: #1818519) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * unnecessary request_queue freeze (LP: #1815733) - block: avoid setting nr_requests to current value - block: avoid setting none scheduler if it's already none * Miscellaneous Ubuntu changes - SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on xfail - update dkms package versions [ Upstream Kernel Changes ] * Rebase to v5.0 -- Seth Forshee Mon, 04 Mar 2019 08:46:10 -0600 ** Changed in: linux (Ubuntu Disco) 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/1803206 Title: Please enable CONFIG_DMA_CMA=y on arm64 Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Released Bug description: Using the generic arm64 kernel on my raspberry pi 3 it seems impossible to use any apps that require 3D graphics. The X session crashes and a reboot is needed to make it bootable again. Inspecting dmesg, there are a lot of "failed to allocate CMA" messages. Adding cma=256M to the kernel command line has no effect. Dropping resolution allows firefox to start, but 3D apps still fail. I believe the vc4 driver needs CONFIG_DMA_CMA=y, which currently the generic kernel does not set. The raspi2 kernel has this and 3D graphics works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803206/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815831] Re: [ALSA] [PATCH] System76 darp5 and oryp5 fixups
This bug was fixed in the package linux - 5.0.0-7.8 --- linux (5.0.0-7.8) disco; urgency=medium * linux: 5.0.0-7.8 -proposed tracker (LP: #1818519) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * unnecessary request_queue freeze (LP: #1815733) - block: avoid setting nr_requests to current value - block: avoid setting none scheduler if it's already none * Miscellaneous Ubuntu changes - SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on xfail - update dkms package versions [ Upstream Kernel Changes ] * Rebase to v5.0 -- Seth Forshee Mon, 04 Mar 2019 08:46:10 -0600 ** 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/1815831 Title: [ALSA] [PATCH] System76 darp5 and oryp5 fixups Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: SRU Justification Impact: The System76 darp5 and oryp5 platforms need audio driverquirks to fix up the pin configuration. Fix: One backport from upstream, and one cherry pick from the upstream sound tree. Test Case: Backports have been tested on the affected hardware. Regression Potential: These are quirks for specific PCI device ids and thus are not expected to introduce regressions for any other hardware. --- Two fixups are needed to support the headset microphone on the System76 darp5 and oryp5. The darp5 patch is attached here, the oryp5 patch will be attached on the next comment. On the System76 Darter Pro (darp5), there is a headset microphone input attached to 0x1a that does not have a jack detect. In order to get it working, the pin configuration needs to be set correctly, and the ALC269_FIXUP_HEADSET_MODE_NO_HP_MIC fixup needs to be applied. This is similar to the MIC_NO_PRESENCE fixups for some Dell laptops, except we have a separate microphone jack that is already configured correctly. On the System76 Oryx Pro (oryp5), there is a headset microphone input attached to 0x19 that does not have a jack detect. In order to get it working, the pin configuration needs to be set correctly, and the ALC269_FIXUP_HEADSET_MODE_NO_HP_MIC fixup needs to be applied. This is similar to the MIC_NO_PRESENCE fixups for some Dell laptops, except we have a separate microphone jack that is already configured correctly. Since the ALC1220 does not have a fixup similar to ALC269_FIXUP_HEADSET_MODE_NO_HP_MIC, I have exposed the fixup from the ALC269 in a way that it can be accessed from the alc1220_fixup_system76_oryp5 function. In addition, the alc1220_fixup_clevo_p950 needs to be applied to gain speaker output. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815831/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814982] Re: efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted
This bug was fixed in the package linux - 5.0.0-7.8 --- linux (5.0.0-7.8) disco; urgency=medium * linux: 5.0.0-7.8 -proposed tracker (LP: #1818519) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * unnecessary request_queue freeze (LP: #1815733) - block: avoid setting nr_requests to current value - block: avoid setting none scheduler if it's already none * Miscellaneous Ubuntu changes - SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on xfail - update dkms package versions [ Upstream Kernel Changes ] * Rebase to v5.0 -- Seth Forshee Mon, 04 Mar 2019 08:46:10 -0600 ** Changed in: linux (Ubuntu Disco) 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/1814982 Title: efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Released Bug description: [Impact] The Ubuntu kernel is not currently bootable on various arm64 laptops (HP Envy x2, Asus NovaGo, Lenovo Miix 630, Lenovo Yoga C630, Samsung ...) because of EFI memory permissions/restrictions. The reason is explained in the commit supplied below. [Test Case] Install and boot Ubuntu on one of the above arm64 laptops. [Fix] Committed upstream: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=4e46c2a956215482418d7b315749fb1b6c6bc224 [Regression Risk] This commit adds support for an optional kernel command line parameter so there is minimal to no risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813060] Re: glibc 2.28-0ubuntu1 ADT test failure with linux 5.0.0-1.2
This bug was fixed in the package linux - 5.0.0-7.8 --- linux (5.0.0-7.8) disco; urgency=medium * linux: 5.0.0-7.8 -proposed tracker (LP: #1818519) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * unnecessary request_queue freeze (LP: #1815733) - block: avoid setting nr_requests to current value - block: avoid setting none scheduler if it's already none * Miscellaneous Ubuntu changes - SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on xfail - update dkms package versions [ Upstream Kernel Changes ] * Rebase to v5.0 -- Seth Forshee Mon, 04 Mar 2019 08:46:10 -0600 ** 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/1813060 Title: glibc 2.28-0ubuntu1 ADT test failure with linux 5.0.0-1.2 Status in glibc package in Ubuntu: New Status in linux package in Ubuntu: Fix Released Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco-canonical-kernel-team-unstable/disco/amd64/g/glibc/20190123_170427_c175c@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco-canonical-kernel-team-unstable/disco/arm64/g/glibc/20190123_173956_c175c@/log.gz armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco-canonical-kernel-team-unstable/disco/armhf/g/glibc/20190123_185911_c175c@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco-canonical-kernel-team-unstable/disco/i386/g/glibc/20190123_172808_c175c@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco-canonical-kernel-team-unstable/disco/ppc64el/g/glibc/20190123_171355_c175c@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco-canonical-kernel-team-unstable/disco/s390x/g/glibc/20190123_170405_c175c@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1813060/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814684] Re: [19.04 FEAT] [LS1801] PCI Virtual function enablement
This bug was fixed in the package linux - 5.0.0-7.8 --- linux (5.0.0-7.8) disco; urgency=medium * linux: 5.0.0-7.8 -proposed tracker (LP: #1818519) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * unnecessary request_queue freeze (LP: #1815733) - block: avoid setting nr_requests to current value - block: avoid setting none scheduler if it's already none * Miscellaneous Ubuntu changes - SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on xfail - update dkms package versions [ Upstream Kernel Changes ] * Rebase to v5.0 -- Seth Forshee Mon, 04 Mar 2019 08:46:10 -0600 ** 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/1814684 Title: [19.04 FEAT] [LS1801] PCI Virtual function enablement Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Bug description: Description: The common code Linux kernel PCI bus driver performs initialization steps of PCI virtual functions (SRIOV) in an order that is incompatible with Z firmware requirements. As a result, virtual functions cannot be used properly. This item is about ensuring that PCI virtual functions can be correctly enabled in Linux. Tentativ target ; kernel 5.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1814684/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1816716] Re: kernel net tls selftest fails on 5.0
This bug was fixed in the package linux - 5.0.0-7.8 --- linux (5.0.0-7.8) disco; urgency=medium * linux: 5.0.0-7.8 -proposed tracker (LP: #1818519) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * unnecessary request_queue freeze (LP: #1815733) - block: avoid setting nr_requests to current value - block: avoid setting none scheduler if it's already none * Miscellaneous Ubuntu changes - SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on xfail - update dkms package versions [ Upstream Kernel Changes ] * Rebase to v5.0 -- Seth Forshee Mon, 04 Mar 2019 08:46:10 -0600 ** Changed in: linux (Ubuntu Disco) 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/1816716 Title: kernel net tls selftest fails on 5.0 Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Released Bug description: Running the kernel net tls selftests on 5.0 produces: # tools/testing/selftests/net/tls [==] Running 28 tests from 2 test cases. [ RUN ] tls.sendfile [ OK ] tls.sendfile [ RUN ] tls.send_then_sendfile [ OK ] tls.send_then_sendfile [ RUN ] tls.recv_max [ OK ] tls.recv_max [ RUN ] tls.recv_small [ OK ] tls.recv_small [ RUN ] tls.msg_more [ OK ] tls.msg_more [ RUN ] tls.sendmsg_single [ OK ] tls.sendmsg_single [ RUN ] tls.sendmsg_large [ OK ] tls.sendmsg_large [ RUN ] tls.sendmsg_multiple [ OK ] tls.sendmsg_multiple [ RUN ] tls.sendmsg_multiple_stress [ OK ] tls.sendmsg_multiple_stress [ RUN ] tls.splice_from_pipe [ OK ] tls.splice_from_pipe [ RUN ] tls.splice_from_pipe2 [ OK ] tls.splice_from_pipe2 [ RUN ] tls.send_and_splice [ OK ] tls.send_and_splice [ RUN ] tls.splice_to_pipe [ OK ] tls.splice_to_pipe [ RUN ] tls.recvmsg_single [ OK ] tls.recvmsg_single [ RUN ] tls.recvmsg_single_max [ OK ] tls.recvmsg_single_max [ RUN ] tls.recvmsg_multiple [ OK ] tls.recvmsg_multiple [ RUN ] tls.single_send_multiple_recv [ OK ] tls.single_send_multiple_recv [ RUN ] tls.multiple_send_single_recv [ OK ] tls.multiple_send_single_recv [ RUN ] tls.recv_partial [ OK ] tls.recv_partial [ RUN ] tls.recv_nonblock [ OK ] tls.recv_nonblock [ RUN ] tls.recv_peek [ OK ] tls.recv_peek [ RUN ] tls.recv_peek_multiple [ OK ] tls.recv_peek_multiple [ RUN ] tls.recv_peek_large_buf_mult_recs tls.c:524:tls.recv_peek_large_buf_mult_recs:Expected memcmp(test_str, buf, len) (18446744073709551595) == 0 (0) tls.recv_peek_large_buf_mult_recs: Test failed at step #8 [ FAIL ] tls.recv_peek_large_buf_mult_recs [ RUN ] tls.pollin [ OK ] tls.pollin [ RUN ] tls.poll_wait [ OK ] tls.poll_wait [ RUN ] tls.blocking [ OK ] tls.blocking [ RUN ] tls.nonblocking [ OK ] tls.nonblocking [ RUN ] tls.control_msg [ OK ] tls.control_msg [==] 27 / 28 tests passed. [ FAILED ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816716/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817585] Re: linux: 5.0.0-6.7 -proposed tracker
*** This bug is a duplicate of bug 1818519 *** https://bugs.launchpad.net/bugs/1818519 This bug was fixed in the package linux - 5.0.0-7.8 --- linux (5.0.0-7.8) disco; urgency=medium * linux: 5.0.0-7.8 -proposed tracker (LP: #1818519) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * unnecessary request_queue freeze (LP: #1815733) - block: avoid setting nr_requests to current value - block: avoid setting none scheduler if it's already none * Miscellaneous Ubuntu changes - SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on xfail - update dkms package versions [ Upstream Kernel Changes ] * Rebase to v5.0 -- Seth Forshee Mon, 04 Mar 2019 08:46:10 -0600 ** Changed in: linux (Ubuntu Disco) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1817585 Title: linux: 5.0.0-6.7 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: 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-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: -- swm properties -- phase: Packaging phase-changed: Monday, 25. February 2019 16:07 UTC reason: prepare-package: Pending -- package tag not yet published prepare-package-meta: Pending -- package tag not yet published prepare-package-signed: Pending -- package tag not yet published promote-to-proposed: Pending -- source package tags missing To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1817585/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817058] Re: Fix I219 doesn't get woken up after plugging ethernet cable
This bug was fixed in the package linux - 5.0.0-7.8 --- linux (5.0.0-7.8) disco; urgency=medium * linux: 5.0.0-7.8 -proposed tracker (LP: #1818519) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * unnecessary request_queue freeze (LP: #1815733) - block: avoid setting nr_requests to current value - block: avoid setting none scheduler if it's already none * Miscellaneous Ubuntu changes - SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on xfail - update dkms package versions [ Upstream Kernel Changes ] * Rebase to v5.0 -- Seth Forshee Mon, 04 Mar 2019 08:46:10 -0600 ** Changed in: linux (Ubuntu Disco) Status: Fix Committed => 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/1817058 Title: Fix I219 doesn't get woken up after plugging ethernet cable Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-oem source package in Bionic: New Status in linux source package in Cosmic: New Status in linux-oem source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-oem source package in Disco: Won't Fix Bug description: [Impact] Plugging ethernet cable doesn't work on new I219 after it runtime suspends to D3. [Fix] Intel confirms that it only supports D0, so disable runtime power management to prevent it from entering D3. [Test] Once the patch applied, the device always stays at D0, which doesn't have this problem. [Regression Potential] Low. This doesn't introduce any functional change. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1817058/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817321] Re: installer does not support iSCSI iBFT
This bug was fixed in the package linux - 5.0.0-7.8 --- linux (5.0.0-7.8) disco; urgency=medium * linux: 5.0.0-7.8 -proposed tracker (LP: #1818519) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * unnecessary request_queue freeze (LP: #1815733) - block: avoid setting nr_requests to current value - block: avoid setting none scheduler if it's already none * Miscellaneous Ubuntu changes - SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on xfail - update dkms package versions [ Upstream Kernel Changes ] * Rebase to v5.0 -- Seth Forshee Mon, 04 Mar 2019 08:46:10 -0600 ** Changed in: linux (Ubuntu Disco) 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/1817321 Title: installer does not support iSCSI iBFT Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Released Bug description: [Impact] * It's not possible to access iBFT (iSCSI Boot Firmware Table) information (settings for network interface, initiator, and target) in the installer because the 'iscsi_ibft' module is not present in udeb packages. * Even if it was, the installer does not handle iBFT information at all, thus any settings are ignored, and iSCSI-related configuration has to be done manually or with workarounds. * This impacts user-experience and automatic installation on systems and deployments which actually do provide the iBFT feature and information, but cannot use it practically. * With proper iBFT support in the installer (kernel module in udeb package and automatic iSCSI-related configuration) users will be able to rely on iBFT to install/deploy Ubuntu on their servers and datacenters. * These fixes add the 'iscsi_ibft' kernel module in the scsi-modules udeb, and configure network/iSCSI according to iBFT information in disk-detect. This is done in disk-detect so that the iSCSI LUNs are detected as disks (useful in case of no other disks in the system so the installer doesn't complain nor wait too long) and that any partman-related preseed options are not required and may be still available for the user. [Test Case] * linux package / kernel module in udeb: $ dpkg-deb -c scsi-modules_*.udeb | grep iscsi_ibft.ko Check the module loads in the installer environment. See comment with example for disco. * d-i/hw-detect package: (to be done) [Regression Potential] * linux package: low, the kernel module is not loaded by default, and only checks whether iBFT information is present in firmware, then exposes that in sysfs in read-only mode. * d-i/hw-detect: (to be done) [Other Info] * This has been verified both by the developer with a simple iSCSI iBFT environment (2 VMs: iSCSI target & initiator with UEFI+iPXE) and by an user with system/firmware that supports iBFT for iSCSI. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817321/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817063] Re: Silent "Unknown key" message when pressing keyboard backlight hotkey
This bug was fixed in the package linux - 5.0.0-7.8 --- linux (5.0.0-7.8) disco; urgency=medium * linux: 5.0.0-7.8 -proposed tracker (LP: #1818519) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * unnecessary request_queue freeze (LP: #1815733) - block: avoid setting nr_requests to current value - block: avoid setting none scheduler if it's already none * Miscellaneous Ubuntu changes - SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on xfail - update dkms package versions [ Upstream Kernel Changes ] * Rebase to v5.0 -- Seth Forshee Mon, 04 Mar 2019 08:46:10 -0600 ** Changed in: linux (Ubuntu Disco) 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/1817063 Title: Silent "Unknown key" message when pressing keyboard backlight hotkey Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Released Status in linux source package in EE-Series: New Bug description: [Impact] Kernel message shows this once keyboard backlight hotkey gets pressed: [ 3285.474172] dell_wmi: Unknown key with type 0x0010 and code 0x003f pressed It's for notification purpose, doesn't have any function. [Fix] Use KE_IGNORE for this type of event, so the keymap won't parse it. [Test] Once the patch is applied, the annoyance goes away. [Regression Potential] Low. This patch silence the useless message, no functional change. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1817063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818519] Re: linux: 5.0.0-7.8 -proposed tracker
This bug was fixed in the package linux - 5.0.0-7.8 --- linux (5.0.0-7.8) disco; urgency=medium * linux: 5.0.0-7.8 -proposed tracker (LP: #1818519) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * unnecessary request_queue freeze (LP: #1815733) - block: avoid setting nr_requests to current value - block: avoid setting none scheduler if it's already none * Miscellaneous Ubuntu changes - SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on xfail - update dkms package versions [ Upstream Kernel Changes ] * Rebase to v5.0 -- Seth Forshee Mon, 04 Mar 2019 08:46:10 -0600 ** Changed in: linux (Ubuntu Disco) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818519 Title: linux: 5.0.0-7.8 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: -- swm properties -- boot-testing-requested: true phase: Ready for Release phase-changed: Monday, 11. March 2019 14:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-release: Pending -- ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1818519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic
** Description changed: - When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel - 4.15.0-32.35 amd64, wifi via rtl8723be works OK. + === SRU Justification === + [Impact] + Realtek 8723be's ant_sel parameter stops working since 4.15.0-33.36. + + [Fix] + The commit that causes the regression works in mainline, so there are + some functional dependencies are not in 4.15. + + Finding those dependencies can be hard since I don't have the hardware + to test with, also pulling new commits may cause new regression. So the + safest way to deal with this bug is to simply revert the regression + commit. + + [Test] + User confirmed reverting the commit can fix the issue. + + [Regression Potential] + Low. Realtek 8723be works without this commit. + + === Original Bug Report === + When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. - --- + --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: al 1234 F pulseaudio - /dev/snd/controlC0: al 1234 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: al 1234 F pulseaudio + /dev/snd/controlC0: al 1234 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Notebook Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: - linux-restricted-modules-4.15.0-33-generic N/A - linux-backports-modules-4.15.0-33-generic N/A - linux-firmware 1.173.1 + linux-restricted-modules-4.15.0-33-generic N/A + linux-backports-modules-4.15.0-33-generic N/A + linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8137 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.02 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: === SRU Justification === [Impact] Realtek 8723be's ant_sel parameter stops working since 4.15.0-33.36. [Fix] The commit that causes the regression works in mainline, so there are some functional dependencies are not in 4.15. Finding those dependencies can be hard since I don't have the hardware to test with, also pulling new commits may cause new regression. So the safest way to deal with this bug is to simply revert the regression commit. [Test] User confirmed reverting the commit can fix the issue. [Regression Potential] Low. Realtek 8723be works without this commit. === Original Bug Report === When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did
[Kernel-packages] [Bug 1819485] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1819485/+attachment/5245480/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819485 Title: AMD Rome : Additional patches Status in linux package in Ubuntu: Confirmed Bug description: The following patches will bring Rome support into 18.04. The patches are all localized to AMD source code. CCP/PSP: dcbc0c6e4aa1ef269179351ac615fd08ddefc849 crypto: ccp - Add support for new CCP/PSP device ID ad01a984f512c42c9f4fe79d36b9cddbc6156a3f crypto: ccp - Support register differences between PSP devices A few others: 210ba1201ff950b3d05bfd8fa5d47540cea393c0 hwmon/k10temp: Add support for AMD family 17h, model 30h CPUs be3518a16ef270e3b030a6ae96055f83f51bd3dd x86/amd_nb: Add PCI device IDs for family 17h, model 30h 556e4c62baffa71e2045a298379db7e57dd47f3d x86/amd_nb: Add support for newer PCI topologies dedf7dce4cec5c0abe69f4fa6938d5100398220b hwmon/k10temp, x86/amd_nb: Consolidate shared device IDs 60c8144afc287ef09ce8c1230c6aa972659ba1bb x86/MCE/AMD: Fix the thresholding machinery initialization order --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-02-28 (10 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: enp33s0f0 no wireless extensions. lono wireless extensions. enp33s0f1 no wireless extensions. MachineType: AMD Corporation DAYTONA_X Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=6500165b-63c3-4a3e-bbee-ca9f43bb1784 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: RDY0071B dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DAYTONA_X dmi.board.vendor: AMD Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 2 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrRDY0071B:bd01/18/2019:svnAMDCorporation:pnDAYTONA_X:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rnDAYTONA_X:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct2:cvrTobefilledbyO.E.M.: dmi.product.family: Default string dmi.product.name: DAYTONA_X dmi.product.sku: Default string dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: AMD Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819485] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819485 Title: AMD Rome : Additional patches Status in linux package in Ubuntu: Confirmed Bug description: The following patches will bring Rome support into 18.04. The patches are all localized to AMD source code. CCP/PSP: dcbc0c6e4aa1ef269179351ac615fd08ddefc849 crypto: ccp - Add support for new CCP/PSP device ID ad01a984f512c42c9f4fe79d36b9cddbc6156a3f crypto: ccp - Support register differences between PSP devices A few others: 210ba1201ff950b3d05bfd8fa5d47540cea393c0 hwmon/k10temp: Add support for AMD family 17h, model 30h CPUs be3518a16ef270e3b030a6ae96055f83f51bd3dd x86/amd_nb: Add PCI device IDs for family 17h, model 30h 556e4c62baffa71e2045a298379db7e57dd47f3d x86/amd_nb: Add support for newer PCI topologies dedf7dce4cec5c0abe69f4fa6938d5100398220b hwmon/k10temp, x86/amd_nb: Consolidate shared device IDs 60c8144afc287ef09ce8c1230c6aa972659ba1bb x86/MCE/AMD: Fix the thresholding machinery initialization order --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-02-28 (10 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: enp33s0f0 no wireless extensions. lono wireless extensions. enp33s0f1 no wireless extensions. MachineType: AMD Corporation DAYTONA_X Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=6500165b-63c3-4a3e-bbee-ca9f43bb1784 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: RDY0071B dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DAYTONA_X dmi.board.vendor: AMD Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 2 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrRDY0071B:bd01/18/2019:svnAMDCorporation:pnDAYTONA_X:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rnDAYTONA_X:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct2:cvrTobefilledbyO.E.M.: dmi.product.family: Default string dmi.product.name: DAYTONA_X dmi.product.sku: Default string dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: AMD Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819485] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1819485/+attachment/5245471/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819485 Title: AMD Rome : Additional patches Status in linux package in Ubuntu: Confirmed Bug description: The following patches will bring Rome support into 18.04. The patches are all localized to AMD source code. CCP/PSP: dcbc0c6e4aa1ef269179351ac615fd08ddefc849 crypto: ccp - Add support for new CCP/PSP device ID ad01a984f512c42c9f4fe79d36b9cddbc6156a3f crypto: ccp - Support register differences between PSP devices A few others: 210ba1201ff950b3d05bfd8fa5d47540cea393c0 hwmon/k10temp: Add support for AMD family 17h, model 30h CPUs be3518a16ef270e3b030a6ae96055f83f51bd3dd x86/amd_nb: Add PCI device IDs for family 17h, model 30h 556e4c62baffa71e2045a298379db7e57dd47f3d x86/amd_nb: Add support for newer PCI topologies dedf7dce4cec5c0abe69f4fa6938d5100398220b hwmon/k10temp, x86/amd_nb: Consolidate shared device IDs 60c8144afc287ef09ce8c1230c6aa972659ba1bb x86/MCE/AMD: Fix the thresholding machinery initialization order --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-02-28 (10 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: enp33s0f0 no wireless extensions. lono wireless extensions. enp33s0f1 no wireless extensions. MachineType: AMD Corporation DAYTONA_X Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=6500165b-63c3-4a3e-bbee-ca9f43bb1784 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: RDY0071B dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DAYTONA_X dmi.board.vendor: AMD Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 2 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrRDY0071B:bd01/18/2019:svnAMDCorporation:pnDAYTONA_X:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rnDAYTONA_X:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct2:cvrTobefilledbyO.E.M.: dmi.product.family: Default string dmi.product.name: DAYTONA_X dmi.product.sku: Default string dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: AMD Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819485] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1819485/+attachment/5245475/+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/1819485 Title: AMD Rome : Additional patches Status in linux package in Ubuntu: Confirmed Bug description: The following patches will bring Rome support into 18.04. The patches are all localized to AMD source code. CCP/PSP: dcbc0c6e4aa1ef269179351ac615fd08ddefc849 crypto: ccp - Add support for new CCP/PSP device ID ad01a984f512c42c9f4fe79d36b9cddbc6156a3f crypto: ccp - Support register differences between PSP devices A few others: 210ba1201ff950b3d05bfd8fa5d47540cea393c0 hwmon/k10temp: Add support for AMD family 17h, model 30h CPUs be3518a16ef270e3b030a6ae96055f83f51bd3dd x86/amd_nb: Add PCI device IDs for family 17h, model 30h 556e4c62baffa71e2045a298379db7e57dd47f3d x86/amd_nb: Add support for newer PCI topologies dedf7dce4cec5c0abe69f4fa6938d5100398220b hwmon/k10temp, x86/amd_nb: Consolidate shared device IDs 60c8144afc287ef09ce8c1230c6aa972659ba1bb x86/MCE/AMD: Fix the thresholding machinery initialization order --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-02-28 (10 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: enp33s0f0 no wireless extensions. lono wireless extensions. enp33s0f1 no wireless extensions. MachineType: AMD Corporation DAYTONA_X Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=6500165b-63c3-4a3e-bbee-ca9f43bb1784 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: RDY0071B dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DAYTONA_X dmi.board.vendor: AMD Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 2 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrRDY0071B:bd01/18/2019:svnAMDCorporation:pnDAYTONA_X:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rnDAYTONA_X:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct2:cvrTobefilledbyO.E.M.: dmi.product.family: Default string dmi.product.name: DAYTONA_X dmi.product.sku: Default string dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: AMD Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819485] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1819485/+attachment/5245474/+files/ProcCpuinfo.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/1819485 Title: AMD Rome : Additional patches Status in linux package in Ubuntu: Confirmed Bug description: The following patches will bring Rome support into 18.04. The patches are all localized to AMD source code. CCP/PSP: dcbc0c6e4aa1ef269179351ac615fd08ddefc849 crypto: ccp - Add support for new CCP/PSP device ID ad01a984f512c42c9f4fe79d36b9cddbc6156a3f crypto: ccp - Support register differences between PSP devices A few others: 210ba1201ff950b3d05bfd8fa5d47540cea393c0 hwmon/k10temp: Add support for AMD family 17h, model 30h CPUs be3518a16ef270e3b030a6ae96055f83f51bd3dd x86/amd_nb: Add PCI device IDs for family 17h, model 30h 556e4c62baffa71e2045a298379db7e57dd47f3d x86/amd_nb: Add support for newer PCI topologies dedf7dce4cec5c0abe69f4fa6938d5100398220b hwmon/k10temp, x86/amd_nb: Consolidate shared device IDs 60c8144afc287ef09ce8c1230c6aa972659ba1bb x86/MCE/AMD: Fix the thresholding machinery initialization order --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-02-28 (10 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: enp33s0f0 no wireless extensions. lono wireless extensions. enp33s0f1 no wireless extensions. MachineType: AMD Corporation DAYTONA_X Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=6500165b-63c3-4a3e-bbee-ca9f43bb1784 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: RDY0071B dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DAYTONA_X dmi.board.vendor: AMD Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 2 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrRDY0071B:bd01/18/2019:svnAMDCorporation:pnDAYTONA_X:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rnDAYTONA_X:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct2:cvrTobefilledbyO.E.M.: dmi.product.family: Default string dmi.product.name: DAYTONA_X dmi.product.sku: Default string dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: AMD Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819485] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1819485/+attachment/5245470/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819485 Title: AMD Rome : Additional patches Status in linux package in Ubuntu: Confirmed Bug description: The following patches will bring Rome support into 18.04. The patches are all localized to AMD source code. CCP/PSP: dcbc0c6e4aa1ef269179351ac615fd08ddefc849 crypto: ccp - Add support for new CCP/PSP device ID ad01a984f512c42c9f4fe79d36b9cddbc6156a3f crypto: ccp - Support register differences between PSP devices A few others: 210ba1201ff950b3d05bfd8fa5d47540cea393c0 hwmon/k10temp: Add support for AMD family 17h, model 30h CPUs be3518a16ef270e3b030a6ae96055f83f51bd3dd x86/amd_nb: Add PCI device IDs for family 17h, model 30h 556e4c62baffa71e2045a298379db7e57dd47f3d x86/amd_nb: Add support for newer PCI topologies dedf7dce4cec5c0abe69f4fa6938d5100398220b hwmon/k10temp, x86/amd_nb: Consolidate shared device IDs 60c8144afc287ef09ce8c1230c6aa972659ba1bb x86/MCE/AMD: Fix the thresholding machinery initialization order --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-02-28 (10 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: enp33s0f0 no wireless extensions. lono wireless extensions. enp33s0f1 no wireless extensions. MachineType: AMD Corporation DAYTONA_X Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=6500165b-63c3-4a3e-bbee-ca9f43bb1784 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: RDY0071B dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DAYTONA_X dmi.board.vendor: AMD Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 2 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrRDY0071B:bd01/18/2019:svnAMDCorporation:pnDAYTONA_X:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rnDAYTONA_X:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct2:cvrTobefilledbyO.E.M.: dmi.product.family: Default string dmi.product.name: DAYTONA_X dmi.product.sku: Default string dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: AMD Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819485] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1819485/+attachment/5245477/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819485 Title: AMD Rome : Additional patches Status in linux package in Ubuntu: Confirmed Bug description: The following patches will bring Rome support into 18.04. The patches are all localized to AMD source code. CCP/PSP: dcbc0c6e4aa1ef269179351ac615fd08ddefc849 crypto: ccp - Add support for new CCP/PSP device ID ad01a984f512c42c9f4fe79d36b9cddbc6156a3f crypto: ccp - Support register differences between PSP devices A few others: 210ba1201ff950b3d05bfd8fa5d47540cea393c0 hwmon/k10temp: Add support for AMD family 17h, model 30h CPUs be3518a16ef270e3b030a6ae96055f83f51bd3dd x86/amd_nb: Add PCI device IDs for family 17h, model 30h 556e4c62baffa71e2045a298379db7e57dd47f3d x86/amd_nb: Add support for newer PCI topologies dedf7dce4cec5c0abe69f4fa6938d5100398220b hwmon/k10temp, x86/amd_nb: Consolidate shared device IDs 60c8144afc287ef09ce8c1230c6aa972659ba1bb x86/MCE/AMD: Fix the thresholding machinery initialization order --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-02-28 (10 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: enp33s0f0 no wireless extensions. lono wireless extensions. enp33s0f1 no wireless extensions. MachineType: AMD Corporation DAYTONA_X Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=6500165b-63c3-4a3e-bbee-ca9f43bb1784 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: RDY0071B dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DAYTONA_X dmi.board.vendor: AMD Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 2 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrRDY0071B:bd01/18/2019:svnAMDCorporation:pnDAYTONA_X:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rnDAYTONA_X:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct2:cvrTobefilledbyO.E.M.: dmi.product.family: Default string dmi.product.name: DAYTONA_X dmi.product.sku: Default string dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: AMD Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819486] Re: Crash from :i915 module with 4.15.0-46-generic using multi-display
** Attachment added: "version.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819486/+attachment/5245481/+files/version.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/1819486 Title: Crash from :i915 module with 4.15.0-46-generic using multi-display Status in linux package in Ubuntu: Incomplete Bug description: While previously working using 4.15.0-45-generic, booting my thinkpad T480 on a dock with additional screen connected and "kernel 4.15.0-46-generic" lead to a crash of the system. Laptop is running Ubuntu 18.04.2 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819486/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819485] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1819485/+attachment/5245476/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819485 Title: AMD Rome : Additional patches Status in linux package in Ubuntu: Confirmed Bug description: The following patches will bring Rome support into 18.04. The patches are all localized to AMD source code. CCP/PSP: dcbc0c6e4aa1ef269179351ac615fd08ddefc849 crypto: ccp - Add support for new CCP/PSP device ID ad01a984f512c42c9f4fe79d36b9cddbc6156a3f crypto: ccp - Support register differences between PSP devices A few others: 210ba1201ff950b3d05bfd8fa5d47540cea393c0 hwmon/k10temp: Add support for AMD family 17h, model 30h CPUs be3518a16ef270e3b030a6ae96055f83f51bd3dd x86/amd_nb: Add PCI device IDs for family 17h, model 30h 556e4c62baffa71e2045a298379db7e57dd47f3d x86/amd_nb: Add support for newer PCI topologies dedf7dce4cec5c0abe69f4fa6938d5100398220b hwmon/k10temp, x86/amd_nb: Consolidate shared device IDs 60c8144afc287ef09ce8c1230c6aa972659ba1bb x86/MCE/AMD: Fix the thresholding machinery initialization order --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-02-28 (10 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: enp33s0f0 no wireless extensions. lono wireless extensions. enp33s0f1 no wireless extensions. MachineType: AMD Corporation DAYTONA_X Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=6500165b-63c3-4a3e-bbee-ca9f43bb1784 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: RDY0071B dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DAYTONA_X dmi.board.vendor: AMD Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 2 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrRDY0071B:bd01/18/2019:svnAMDCorporation:pnDAYTONA_X:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rnDAYTONA_X:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct2:cvrTobefilledbyO.E.M.: dmi.product.family: Default string dmi.product.name: DAYTONA_X dmi.product.sku: Default string dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: AMD Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp