[Kernel-packages] [Bug 1626689] Re: During boot process, system goes to sleep
I upgraded my machine to 17.10 and the bug is still there. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1626689 Title: During boot process, system goes to sleep Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to 16.04, my computer goes to sleep during the boot process, shortly after I entered the passphrase to unlock my LVM. When I wake it up, I’m at the graphical login prompt. I type my user password, press enter and it goes to sleep again. When I wake it up, I’m in my working Lubuntu desktop. This happens every time I boot. And it’s quite annoying. Please tell me which additional information I can provide to help fix this bug. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-38-generic 4.4.0-38.57 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steffi 2155 F lxpanel CurrentDesktop: LXDE Date: Thu Sep 22 20:24:31 2016 HibernationDevice: RESUME=UUID=9e305c00-cee8-4703-9352-abc5fb755282 InstallationDate: Installed on 2016-09-21 (1 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2) MachineType: Acer Aspire one ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic root=/dev/mapper/lubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-38-generic N/A linux-backports-modules-4.4.0-38-generic N/A linux-firmware1.157.3 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-09-22 (0 days ago) dmi.bios.date: 02/20/2009 dmi.bios.vendor: Acer dmi.bios.version: V1.05 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Aspire one dmi.board.vendor: Acer dmi.board.version: V1.05 dmi.chassis.type: 1 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.modalias: dmi:bvnAcer:bvrV1.05:bd02/20/2009:svnAcer:pnAspireone:pvrV1.05:rvnAcer:rnAspireone:rvrV1.05:cvnAcer:ct1:cvrV1.05: dmi.product.name: Aspire one dmi.product.version: V1.05 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626689/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1751798] Re: linux: 4.13.0-37.42 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-lbm Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-ports-meta Status: In Progress => 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/1751798 Title: linux: 4.13.0-37.42 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-lbm series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-ports-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Artful: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1751799 (linux-azure), bug 1751801 (linux-azure-edge), bug 1751802 (linux-gcp), bug 1751803 (linux-hwe), bug 1751805 (linux-oem) derivatives: bug 1751807 (linux-raspi2) kernel-stable-phase-changed:Tuesday, 27. February 2018 18:31 UTC kernel-stable-phase:Uploaded -- swm properties -- phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1751798/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1751398] Re: Brightness keys do nothing, stuck on full brightness
Still continue with kernel upstream mainline v4.15.7 (28 February) because there isn't v4.16 version stable (all rc) uname -a Linux portatil 4.15.7-041507-generic #201802280530 SMP Wed Feb 28 10:31:47 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Thanks ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1751398 Title: Brightness keys do nothing, stuck on full brightness Status in linux package in Ubuntu: Incomplete Bug description: Brightness keys do nothing, stuck on full brightness ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: forge 1895 F pulseaudio CurrentDesktop: Unity Date: Fri Feb 23 19:47:44 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-02-23 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) MachineType: LENOVO 80R3 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=85451546-daae-4935-b12f-494e677b1dac ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.16 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2018-02-23 (0 days ago) dmi.bios.date: 12/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: D3CN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Flex 3-1480 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Flex 3-1480 dmi.modalias: dmi:bvnLENOVO:bvrD3CN29WW:bd12/23/2015:svnLENOVO:pn80R3:pvrFlex3-1480:rvnLENOVO:rnFlex3-1480:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrFlex3-1480: dmi.product.name: 80R3 dmi.product.version: Flex 3-1480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751398/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1751268] Re: bionic desktop does not boot with external monitor attached - [drm:ironlake_crtc_enable [i915]] *ERROR* mode set failed: pipe A stuck / vblank wait timed out on crt
We can perform a kernel bisect to identify the commit that introduced this regression. We first need to identify the last kernel that did not have this bug and the first that did. Can you next test the following kernels: v4.14-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc1/ v4.14 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14/ v4.15-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc1/ You don't have to test all of them. Just until you hit the first version that exhibits the bug. ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Bionic) Status: Confirmed => 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/1751268 Title: bionic desktop does not boot with external monitor attached - [drm:ironlake_crtc_enable [i915]] *ERROR* mode set failed: pipe A stuck / vblank wait timed out on crtc 1 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: Ubuntu Desktop Bionic up to date System doesn't boot with an external monitor attached. There is this message in the journal (full journal attached for this boot) fbcon: inteldrmfb (fb0) is primary device [drm:ironlake_crtc_enable [i915]] *ERROR* mode set failed: pipe A stuck vblank wait timed out on crtc 1 [ cut here ] WARNING: CPU: 3 PID: 201 at /build/linux-UKCsxy/linux-4.13.0/drivers/gpu/drm/drm_vblank.c:1090 drm_wait_one_vblank+0x19b/0x1b0 [drm] Modules linked in: hid_lenovo uas usb_storage rtsx_usb_sdmmc rtsx_usb hid_generic usbhid hid i915 mxm_wmi i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse ahci libahci drm wmi video CPU: 3 PID: 201 Comm: kworker/u8:6 Tainted: G U 4.13.0-32-generic #35-Ubuntu Hardware name: ASUSTeK COMPUTER INC. UX32VD/UX32VD, BIOS UX32VD.214 01/29/2013 Workqueue: events_unbound async_run_entry_fn task: 9760d81cae80 task.stack: b01dc1fb8000 RIP: 0010:drm_wait_one_vblank+0x19b/0x1b0 [drm] RSP: 0018:b01dc1fbb7c8 EFLAGS: 00010282 RAX: 001f RBX: 9760d708 RCX: RDX: RSI: 0002 RDI: 0246 RBP: b01dc1fbb828 R08: 001f R09: 0002af84 R10: b01dc1fbb7c8 R11: 041b R12: 0001 R13: 0170 R14: 0001 R15: FS: () GS:9760eef8() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f156d6d68f0 CR3: 00024660a002 CR4: 001606e0 Call Trace: ? wait_woken+0x80/0x80 ironlake_crtc_enable+0x477/0xc00 [i915] ? gen6_write8+0x190/0x190 [i915] intel_update_crtc+0x4b/0xe0 [i915] intel_update_crtcs+0x5b/0x80 [i915] intel_atomic_commit_tail+0x254/0xf90 [i915] ? __schedule+0x293/0x880 intel_atomic_commit+0x3d5/0x490 [i915] ? drm_atomic_check_only+0x37b/0x540 [drm] drm_atomic_commit+0x4b/0x50 [drm] restore_fbdev_mode+0x15e/0x270 [drm_kms_helper] drm_fb_helper_restore_fbdev_mode_unlocked+0x2e/0x80 [drm_kms_helper] drm_fb_helper_set_par+0x2d/0x60 [drm_kms_helper] intel_fbdev_set_par+0x1a/0x70 [i915] fbcon_init+0x484/0x650 visual_init+0xd6/0x130 do_bind_con_driver+0x1fc/0x410 do_take_over_console+0x82/0x1a0 do_fbcon_takeover+0x5c/0xb0 fbcon_event_notify+0x587/0x780 notifier_call_chain+0x4a/0x70 blocking_notifier_call_chain+0x43/0x60 fb_notifier_call_chain+0x1b/0x20 register_framebuffer+0x24d/0x360 drm_fb_helper_initial_config+0x249/0x400 [drm_kms_helper] intel_fbdev_initial_config+0x18/0x30 [i915] async_run_entry_fn+0x36/0x150 process_one_work+0x1e7/0x410 worker_thread+0x4b/0x420 kthread+0x125/0x140 ? process_one_work+0x410/0x410 ? kthread_create_on_node+0x70/0x70 ret_from_fork+0x1f/0x30 Code: ff e8 da 3b 4c d6 48 8b 7d a0 48 8d 75 a8 e8 dd 93 50 d6 45 85 ff 0f 85 0c ff ff ff 44 89 e6 48 c7 c7 d8 eb 3d c0 e8 b6 46 52 d6 <0f> ff e9 f6 fe ff ff 0f 1f 40 00 66 2e 0f 1f 84 00 00 00 00 00 ---[ end trace a1db7ccd0b5e4dfc ]--- ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: j-lallement 3671 F pulseaudio /dev/snd/controlC0: j-lallement 3671 F pulseaudio /dev/snd/controlC1: j-lallement 3671 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Feb 23 13:58:39 2018 InstallationDate: Installed on 2013-09-03 (1633 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64
Re: [Kernel-packages] [Bug 1749040] Re: KPTI support for arm64 systems
On Wed, Feb 28, 2018 at 10:12 AM, Paolo Pisati <1749...@bugs.launchpad.net> wrote: > Found && fixed. > > https://git.launchpad.net/~p-pisati/ubuntu/+source/linux/log/?h=artful- > master-next-arm64-kpti-414-backport > > I pushed two fixes on top of it: > > 1) 'syscalls: Use CHECK_DATA_CORRUPTION for addr_limit_user_check' fixes a > FTBFS for armhf > 2) 'arm64: mm: fix thinko in non-global page table attribute check' fixes > this kvm boot race > > We probably need to test it again on all arm64 boards now... OK - I'll get a PPA kernel built and we'll begin another test cycle. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1749040 Title: KPTI support for arm64 systems Status in linux package in Ubuntu: Incomplete Status in linux source package in Artful: In Progress Status in linux source package in Bionic: Incomplete Bug description: While regression testing the current linux-hwe proposed kernel (4.13.0-33.36~16.04.1), I found that it fails to boot on a Cavium ThunderX CRB. I've rebooted twice since upgrading from the current -updates kernel, and it's failed to boot both times, with different failure modes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752182] Re: Update Ubuntu 18.04 lpfc FC driver with 32/64GB HBA support and bug fixes
This is a feature request, logs for debugging are not necessary. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Summary changed: - Update Ubuntu 18.04 lpfc FC driver with 32/64GB HBA support and bug fixes + [Feature]Update Ubuntu 18.04 lpfc FC driver with 32/64GB HBA support and bug fixes -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752182 Title: [Feature]Update Ubuntu 18.04 lpfc FC driver with 32/64GB HBA support and bug fixes Status in linux package in Ubuntu: Confirmed Bug description: This is a placeholder bugzilla that will list all commit ids needed for Broadcom Emulex FC 32/64GB new hardware support and all bug fixes available upstream. Note the lpfc FC driver commit list will include NVMe patches for ease of maintainability vs. upstream but we ask that you not build NVMe FC since we do not intend to support NVMe FC on 18.04 (4.15 kernel) at this time due to all of the unmet upper layer dependencies. Laurie Barry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752182/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1751798] Re: linux: 4.13.0-37.42 -proposed tracker
** Summary changed: - linux: 4.13.0-37.41 -proposed tracker + linux: 4.13.0-37.42 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Released => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lbm Status: Invalid => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released => In Progress ** Changed in: kernel-sru-workflow/prepare-package-ports-meta Status: Invalid => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Released => 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/1751798 Title: linux: 4.13.0-37.42 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-lbm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-ports-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Artful: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1751799 (linux-azure), bug 1751801 (linux-azure-edge), bug 1751802 (linux-gcp), bug 1751803 (linux-hwe), bug 1751805 (linux-oem) derivatives: bug 1751807 (linux-raspi2) kernel-stable-phase-changed:Tuesday, 27. February 2018 18:31 UTC kernel-stable-phase:Uploaded -- swm properties -- phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1751798/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1729010] Re: USB hub stops working after suspend(s?)
in limited testing so far, v4.16-rc2 appears better -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729010 Title: USB hub stops working after suspend(s?) Status in linux package in Ubuntu: Confirmed Bug description: On initial boot, my usb hub works fine, but after a (series of?) suspends, I stop being able to see devices that are plugged into it. journalctl output on plugging it in: Oct 31 07:08:36 spiny kernel: usb 1-1: new high-speed USB device number 21 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device found, idVendor=0409, idProduct=005a Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: USB hub found Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: 4 ports detected Oct 31 07:08:36 spiny kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC=fe80::::a299:9bff:fe17:9047 DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=32325 PROTO=UDP SPT=8612 DPT=8612 LEN=24 Oct 31 07:08:36 spiny kernel: usb 1-1.1: new high-speed USB device number 22 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device found, idVendor=0b95, idProduct=772a Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 31 07:08:36 spiny kernel: usb 1-1.1: Product: AX88x72A Oct 31 07:08:36 spiny kernel: usb 1-1.1: Manufacturer: ASIX Elec. Corp. Oct 31 07:08:36 spiny kernel: usb 1-1.1: SerialNumber: 47EDE2 Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 eth0: register 'asix' at usb-:00:14.0-1.1, ASIX AX88772 USB 2.0 Ethernet, 00:50:b6:47:ed:e2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.0438] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/7) Oct 31 07:08:37 spiny mtp-probe[13207]: checking bus 1, device 22: "/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1" Oct 31 07:08:37 spiny mtp-probe[13207]: bus: 1, device: 22 was not an MTP device Oct 31 07:08:37 spiny systemd-udevd[13206]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 enx0050b647ede2: renamed from eth0 Oct 31 07:08:37 spiny pkexec[13215]: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Oct 31 07:08:37 spiny pkexec[13215]: jbarnett: Executing command [USER=root] [TTY=unknown] [CWD=/home/jbarnett] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 31] Oct 31 07:08:37 spiny pkexec[13214]: gdm: Error executing command as another user: Not authorized [USER=root] [TTY=unknown] [CWD=/var/lib/gdm3] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 48] Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: Error executing command as another user: Not authorized Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: This incident has been reported. Oct 31 07:08:37 spiny systemd-networkd[1119]: eth0: Renamed to enx0050b647ede2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1066] device (eth0): interface index 10 renamed iface from 'eth0' to 'enx0050b647ede2' Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] devices added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2) Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] device added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2): no ifupdown configuration found. Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1217] device (enx0050b647ede2): state change: unmanaged -> unavailable (reason 'managed', internal state 'external') Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1274] keyfile: add connection in-memory (9365f42f-9dd9-3bdc-bbad-e7062efcaf7c,"Wired connection 4") Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1284] settings: (enx0050b647ede2): created default wired connection 'Wired connection 4' Oct 31 07:08:37 spiny systemd[1]: Starting systemd-resolved-update-resolvconf.service... Oct 31 07:08:37 spiny systemd[1]: Started systemd-resolved-update-resolvconf.service. Oct 31 07:08:37 spiny kernel: usb 1-1.2: new full-speed USB device number 23 using xhci_hcd Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device found, idVendor=0d8c, idProduct=0105 Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device strings: Mfr=3, Product=1, SerialNumber=0 Oct 31 07:08:37 spiny kernel: usb 1-1.2: Product:
[Kernel-packages] [Bug 1609601] Re: i2c_hid: probe of i2c-ELAN0732:00 failed with error -61
Yes, filed [1]. [1] https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1752437 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1609601 Title: i2c_hid: probe of i2c-ELAN0732:00 failed with error -61 Status in linux package in Ubuntu: Triaged Bug description: I'm using an HP Envy x360 M6-ar004dx with an AMD 7th-gen FX APU, and the touchscreen will not work. Dmesg shows i2c_hid reporting multiple "failed to reset device" error messages before finally failing to add it as an HID device with error -61. As far as I can tell, it's being detected as an ELAN touchscreen. I've seen reports that this error can be fixed in newer kernels, as the touchscreen uses GPIO interrupts which are fixed in versions 4.6 and later. Most of the information I can find indicates that 4.7 includes improved AMD support, but the mainline kernel build appears to be missing the AMD GPIO drivers, since I get a "failed to get GPIO interrupt" error. I've compiled my own 4.7 kernel from the mainline GIT, including the patches used in kernel-ppa/mainline and setting the right config flags for AMD GPIO, but that just gets me the same errors I'm seeing in 4.4.0-31-generic. For additional info, I'm attaching my dmesg output in its entirety. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 [modified: boot/vmlinuz-4.4.0-31-generic] ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: colin 3591 F pulseaudio /dev/snd/controlC0: colin 3591 F pulseaudio CurrentDesktop: GNOME Date: Wed Aug 3 21:51:47 2016 HibernationDevice: RESUME=UUID=1875834b-d1ff-4b97-a9b8-44afb056c592 InstallationDate: Installed on 2016-08-03 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) MachineType: HP HP ENVY x360 m6 Convertible ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/29/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81AA dmi.board.vendor: HP dmi.board.version: 59.42 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.10:bd06/29/2016:svnHP:pnHPENVYx360m6Convertible:pvrType1ProductConfigId:rvnHP:rn81AA:rvr59.42:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP ENVY x360 m6 Convertible dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1609601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1751202] Re: test_095_kernel_symbols_missing in ubuntu_qrt_kernel_security failed on Bionic
Queued for stable 4.15 branch here: https://www.spinics.net/lists/stable/msg219894.html ** Changed in: qa-regression-testing Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1751202 Title: test_095_kernel_symbols_missing in ubuntu_qrt_kernel_security failed on Bionic Status in QA Regression Testing: Invalid Status in linux package in Ubuntu: Triaged Bug description: This issue could be found on AMD64, ppc64le, ARM64, s390x (not sure about i386, which was not tested because of the deployment issue in the last cycle) Steps: 1. Deploy an AMD64 system with Bionic 2. sudo apt-get install git python-minimal -y 3. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests -b master-next 4. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest 5. rm -fr autotest/client/tests 6. ln -sf ~/autotest-client-tests autotest/client/tests 7. AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_qrt_kernel_security/control ERROR: test_095_kernel_symbols_missing (__main__.KernelSecurityTest) kernel addresses in kallsyms and modules are zeroed out -- Traceback (most recent call last): File "./test-kernel-security.py", line 1508, in test_095_kernel_symbols_missing self._check_pK_files(expected) File "./test-kernel-security.py", line 1440, in _check_pK_files expected) File "./test-kernel-security.py", line 1401, in _read_twice self.assertEqual(expected, 0 == int(address, 16), "%s: user saw %s" % (filename, address)) ValueError: invalid literal for int() with base 16: '(null)' ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: User Name 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 23 04:53 seq crw-rw 1 root audio 116, 33 Feb 23 04:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.8-0ubuntu10 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: CurrentDmesg: Date: Fri Feb 23 06:57:48 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R320 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=0845f9a0-ab8c-4dfa-8385-af21f2f2b9ad ro RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.171 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.4 dmi.board.name: 0DY523 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.4:bd05/11/2012:svnDellInc.:pnPowerEdgeR320:pvr:rvnDellInc.:rn0DY523:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R320 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1751202/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Well, the error happened again, and I wasn't even running any VMs Maybe there's a rare case in which your diff correction didn't get applied? :( -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.13.0-21.24-generic 4.13.13 I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 17.04, which gave me this error after 2 weeks of usage. After that, I installed 16.04 and used it for MONTHS without any problems, until it produced the same error this week. I think it has to do with the ubuntu updates, because I did one recently and one today, just before this problem. Could be a coincidence though. I notice the error when I try to save something on disk and it says me that the disk is in read-only mode: lz@lz:/var/log$ touch something touch: cannot touch 'something': Read-only file system lz@lz:/var/log$ cat syslog Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 lz@lz:/var/log$ dmesg [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.377374] Aborting journal on device nvme0n1p2-8. [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" capability=12 capname="net_admin" Rebooting the ubuntu will give me a black terminal where I can run fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of orphaned inodes. The majority of time it boots back to the Ubuntu working good, but some times it boots to a broken ubuntu (no images, lots of things broken). I have to reinstall ubuntu then. Every time I reinstall my Ubuntu, I have to try lots of times until it installs without an Input/Output error. When it installs, I can use it for some hours without having the problem, but if I run the software updates, it ALWAYS crashes and enters in read-only mode, specifically in the part that is installing kernel updates. I noticed that Ubuntu installs updates automatically when they're for security reasons. Could this be the reason my Ubuntu worked for months without the problem, but then an update was applied and it broke? I thought that this bug was happening: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried different nvme_core.default_ps_max_latency_us= combinations, all them gave errors. I just changed to 0 and I had no error while using ubuntu (however I didn't test for a long time) but I still had the error after trying to update my ubuntu. My Samsung 512gb SSD is: SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q on a Razer Blade Stealth. I also asked this on ask ubuntu, without success: https://askubuntu.com/questions/998471/razer-blade-stealth-disk- corruption-fsck-needed-probably-samsung-ssd-bug-afte Please help me, as I need this computer to work on lots of things :c --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lz 1088 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2018-01-30 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Razer Blade Stealth Package: linux (not installed) ProcFB: 0 inteldrmfb
[Kernel-packages] [Bug 1739300] Re: The header files fcntl.h and linux/fcntl.h are incompatible
** Changed in: linux (Ubuntu) Status: Confirmed => 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/1739300 Title: The header files fcntl.h and linux/fcntl.h are incompatible Status in glibc package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: The program try.c, below, does not compile. Though with HAVE_ARCH_STRUCT_FLOCK and HAVE_ARCH_STRUCT_FLOCK64 defined, it compiles. But then fails again to compile, when _GNU_SOURCE is also defined. I expect this to compile in all three cases. $ cat try.c //#define _GNU_SOURCE //#define HAVE_ARCH_STRUCT_FLOCK //#define HAVE_ARCH_STRUCT_FLOCK64 #include #include int main(int argc, char *argv[]){} $ gcc try.c In file included from /usr/include/x86_64-linux-gnu/asm/fcntl.h:1:0, from /usr/include/linux/fcntl.h:4, from try.c:5: /usr/include/asm-generic/fcntl.h:195:8: error: redefinition of ‘struct flock’ struct flock { ^ In file included from /usr/include/fcntl.h:35:0, from try.c:4: /usr/include/x86_64-linux-gnu/bits/fcntl.h:35:8: note: originally defined here struct flock ^ $ gcc -DHAVE_ARCH_STRUCT_FLOCK -DHAVE_ARCH_STRUCT_FLOCK64 try.c ## this is ok $ gcc -D_GNU_SOURCE -DHAVE_ARCH_STRUCT_FLOCK -DHAVE_ARCH_STRUCT_FLOCK64 try.c In file included from /usr/include/x86_64-linux-gnu/asm/fcntl.h:1:0, from /usr/include/linux/fcntl.h:4, from try.c:5: /usr/include/asm-generic/fcntl.h:155:8: error: redefinition of ‘struct f_owner_ex’ struct f_owner_ex { ^~ In file included from /usr/include/x86_64-linux-gnu/bits/fcntl.h:61:0, from /usr/include/fcntl.h:35, from try.c:4: /usr/include/x86_64-linux-gnu/bits/fcntl-linux.h:267:8: note: originally defined here struct f_owner_ex ^~ $ gcc --version | head -1 gcc (Ubuntu 7.2.0-8ubuntu3) 7.2.0 $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ dpkg -S /usr/include/x86_64-linux-gnu/bits/fcntl.h libc6-dev:amd64: /usr/include/x86_64-linux-gnu/bits/fcntl.h # Package: libc6-dev # Version: 2.26-0ubuntu2 $ dpkg -S /usr/include/x86_64-linux-gnu/asm/fcntl.h linux-libc-dev:amd64: /usr/include/x86_64-linux-gnu/asm/fcntl.h # Package: linux-libc-dev # Version: 4.13.0-19.22 Regards, Mike To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1739300/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1741081] Re: zfs-import-cache.service fails on startup
** Changed in: zfs-linux (Ubuntu) Status: Confirmed => In Progress ** Changed in: zfs-linux (Ubuntu) Importance: Undecided => High ** Changed in: zfs-linux (Ubuntu) Assignee: (unassigned) => Colin Ian King (colin-king) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1741081 Title: zfs-import-cache.service fails on startup Status in zfs-linux package in Ubuntu: In Progress Bug description: I just noticed on my test VM of artful that zfs-import-cache.service does not have a ConditionPathExists=/etc/zfs/zpool.cache. Because of that, it fails on startup, since the cache file does not exist. This line is being deleted by debian/patches/ubuntu-load-zfs-unconditionally.patch. This patch seems to exist per: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1672749 This patch still exists in bionic, so I assume it will be similarly broken. If the goal of the patch is to load the module (and only that), I think it should create a third unit instead: zfs-load-module.service ^^ runs modprobe zfs zfs-import-cache.service & zfs-import-scan.service ^^ per upstream minus modprobe plus Requires=zfs-load-module.service I have tested this manually and it works. I can submit a package patch if this is the desired solution. Interestingly, before this change, zfs-import-scan.service wasn't starting. If started manually, it worked. I had to give it a `systemctl enable zfs-import-scan.service` to create the Wants symlinks. Looking at the zfsutils-linux.postinst, I see the correct boilerplate from dh_systemd, so I'm not sure why this wasn't already done. Can anyone confirm or deny whether zfs-import-scan.service is enabled out-of-the-box on their system? Is the zfs-import-scan.service not starting actually the cause of the original bug? The design is that *either* zfs-import-cache.service or zfs-import-scan.service starts. They both call modprobe zfs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1741081/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1739300] 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 1739300 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1739300 Title: The header files fcntl.h and linux/fcntl.h are incompatible Status in glibc package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: The program try.c, below, does not compile. Though with HAVE_ARCH_STRUCT_FLOCK and HAVE_ARCH_STRUCT_FLOCK64 defined, it compiles. But then fails again to compile, when _GNU_SOURCE is also defined. I expect this to compile in all three cases. $ cat try.c //#define _GNU_SOURCE //#define HAVE_ARCH_STRUCT_FLOCK //#define HAVE_ARCH_STRUCT_FLOCK64 #include #include int main(int argc, char *argv[]){} $ gcc try.c In file included from /usr/include/x86_64-linux-gnu/asm/fcntl.h:1:0, from /usr/include/linux/fcntl.h:4, from try.c:5: /usr/include/asm-generic/fcntl.h:195:8: error: redefinition of ‘struct flock’ struct flock { ^ In file included from /usr/include/fcntl.h:35:0, from try.c:4: /usr/include/x86_64-linux-gnu/bits/fcntl.h:35:8: note: originally defined here struct flock ^ $ gcc -DHAVE_ARCH_STRUCT_FLOCK -DHAVE_ARCH_STRUCT_FLOCK64 try.c ## this is ok $ gcc -D_GNU_SOURCE -DHAVE_ARCH_STRUCT_FLOCK -DHAVE_ARCH_STRUCT_FLOCK64 try.c In file included from /usr/include/x86_64-linux-gnu/asm/fcntl.h:1:0, from /usr/include/linux/fcntl.h:4, from try.c:5: /usr/include/asm-generic/fcntl.h:155:8: error: redefinition of ‘struct f_owner_ex’ struct f_owner_ex { ^~ In file included from /usr/include/x86_64-linux-gnu/bits/fcntl.h:61:0, from /usr/include/fcntl.h:35, from try.c:4: /usr/include/x86_64-linux-gnu/bits/fcntl-linux.h:267:8: note: originally defined here struct f_owner_ex ^~ $ gcc --version | head -1 gcc (Ubuntu 7.2.0-8ubuntu3) 7.2.0 $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ dpkg -S /usr/include/x86_64-linux-gnu/bits/fcntl.h libc6-dev:amd64: /usr/include/x86_64-linux-gnu/bits/fcntl.h # Package: libc6-dev # Version: 2.26-0ubuntu2 $ dpkg -S /usr/include/x86_64-linux-gnu/asm/fcntl.h linux-libc-dev:amd64: /usr/include/x86_64-linux-gnu/asm/fcntl.h # Package: linux-libc-dev # Version: 4.13.0-19.22 Regards, Mike To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1739300/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1729010] Re: USB hub stops working after suspend(s?)
i have not yet experienced it in v4.16-rc2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729010 Title: USB hub stops working after suspend(s?) Status in linux package in Ubuntu: Confirmed Bug description: On initial boot, my usb hub works fine, but after a (series of?) suspends, I stop being able to see devices that are plugged into it. journalctl output on plugging it in: Oct 31 07:08:36 spiny kernel: usb 1-1: new high-speed USB device number 21 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device found, idVendor=0409, idProduct=005a Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: USB hub found Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: 4 ports detected Oct 31 07:08:36 spiny kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC=fe80::::a299:9bff:fe17:9047 DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=32325 PROTO=UDP SPT=8612 DPT=8612 LEN=24 Oct 31 07:08:36 spiny kernel: usb 1-1.1: new high-speed USB device number 22 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device found, idVendor=0b95, idProduct=772a Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 31 07:08:36 spiny kernel: usb 1-1.1: Product: AX88x72A Oct 31 07:08:36 spiny kernel: usb 1-1.1: Manufacturer: ASIX Elec. Corp. Oct 31 07:08:36 spiny kernel: usb 1-1.1: SerialNumber: 47EDE2 Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 eth0: register 'asix' at usb-:00:14.0-1.1, ASIX AX88772 USB 2.0 Ethernet, 00:50:b6:47:ed:e2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.0438] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/7) Oct 31 07:08:37 spiny mtp-probe[13207]: checking bus 1, device 22: "/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1" Oct 31 07:08:37 spiny mtp-probe[13207]: bus: 1, device: 22 was not an MTP device Oct 31 07:08:37 spiny systemd-udevd[13206]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 enx0050b647ede2: renamed from eth0 Oct 31 07:08:37 spiny pkexec[13215]: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Oct 31 07:08:37 spiny pkexec[13215]: jbarnett: Executing command [USER=root] [TTY=unknown] [CWD=/home/jbarnett] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 31] Oct 31 07:08:37 spiny pkexec[13214]: gdm: Error executing command as another user: Not authorized [USER=root] [TTY=unknown] [CWD=/var/lib/gdm3] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 48] Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: Error executing command as another user: Not authorized Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: This incident has been reported. Oct 31 07:08:37 spiny systemd-networkd[1119]: eth0: Renamed to enx0050b647ede2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1066] device (eth0): interface index 10 renamed iface from 'eth0' to 'enx0050b647ede2' Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] devices added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2) Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] device added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2): no ifupdown configuration found. Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1217] device (enx0050b647ede2): state change: unmanaged -> unavailable (reason 'managed', internal state 'external') Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1274] keyfile: add connection in-memory (9365f42f-9dd9-3bdc-bbad-e7062efcaf7c,"Wired connection 4") Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1284] settings: (enx0050b647ede2): created default wired connection 'Wired connection 4' Oct 31 07:08:37 spiny systemd[1]: Starting systemd-resolved-update-resolvconf.service... Oct 31 07:08:37 spiny systemd[1]: Started systemd-resolved-update-resolvconf.service. Oct 31 07:08:37 spiny kernel: usb 1-1.2: new full-speed USB device number 23 using xhci_hcd Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device found, idVendor=0d8c, idProduct=0105 Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device strings: Mfr=3, Product=1, SerialNumber=0 Oct 31 07:08:37 spiny kernel: usb 1-1.2: Product: USB
[Kernel-packages] [Bug 1711283] Comment bridged from LTC Bugzilla
--- Comment From hasri...@in.ibm.com 2018-03-01 00:35 EDT--- When run on a P8 PowerNV, following tests failed. 23:28:59 INFO | Testcase failed. Log from debug: selftests: reg_access_test [FAIL] 23:28:59 INFO | Testcase failed. Log from debug: selftests: event_attributes_test [FAIL] 23:28:59 INFO | Testcase failed. Log from debug: selftests: cycles_with_freeze_test [FAIL] 23:28:59 INFO | Testcase failed. Log from debug: selftests: ebb_on_child_test [FAIL] 23:28:59 INFO | Testcase failed. Log from debug: selftests: ebb_vs_cpu_event_test [FAIL] 23:28:59 INFO | Testcase failed. Log from debug: selftests: cpu_event_vs_ebb_test [FAIL] 23:28:59 INFO | Testcase failed. Log from debug: selftests: cpu_event_pinned_vs_ebb_test [FAIL] 23:28:59 INFO | Testcase failed. Log from debug: selftests: task_event_vs_ebb_test [FAIL] 23:28:59 INFO | Testcase failed. Log from debug: selftests: task_event_pinned_vs_ebb_test [FAIL] 23:28:59 INFO | Testcase failed. Log from debug: selftests: multi_ebb_procs_test [FAIL] 23:28:59 INFO | Testcase failed. Log from debug: selftests: multi_counter_test [FAIL] 23:28:59 INFO | Testcase failed. Log from debug: selftests: pmae_handling_test [FAIL] 23:28:59 INFO | Testcase failed. Log from debug: selftests: cycles_with_mmcr2_test [FAIL] 23:28:59 INFO | Testcase failed. Log from debug: selftests: no_handler_test [FAIL] 23:28:59 INFO | Testcase failed. Log from debug: selftests: ebb_on_willing_child_test [FAIL] 23:28:59 INFO | Testcase failed. Log from debug: selftests: back_to_back_ebbs_test [FAIL] 23:28:59 INFO | Testcase failed. Log from debug: selftests: tm-trap [FAIL] 23:28:59 INFO | Testcase failed. Log from debug: selftests: ptrace-tm-spd-gpr [FAIL] Thanks, Harish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1711283 Title: few kernel selftest failed on Ubuntu 17.10 Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Harish Sriram- 2017-08-01 05:11:09 == Problem Description Few kernel selftest failed on Ubuntu 17.10 Environment -- Kernel Build: 4.11.0-10-generic System Name : ltc-test-ci2 Model : 8247-22L Platform: PowerNV ( P8 ) Uname output --- # uname -a Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Steps to reproduce: 1. Get kernel source using apt source 2. Start powerpc specific tests The following FAILS are observed. selftests: cycles_test [FAIL] selftests: cycles_with_freeze_test [FAIL] selftests: pmc56_overflow_test [FAIL] selftests: ebb_vs_cpu_event_test [FAIL] selftests: cpu_event_vs_ebb_test [FAIL] selftests: task_event_vs_ebb_test [FAIL] selftests: multi_ebb_procs_test [FAIL] selftests: multi_counter_test [FAIL] selftests: pmae_handling_test [FAIL] selftests: close_clears_pmcc_test [FAIL] selftests: instruction_count_test [FAIL] selftests: ebb_on_willing_child_test [FAIL] selftests: back_to_back_ebbs_test [FAIL] selftests: lost_exception_test [FAIL] selftests: cycles_with_mmcr2_test [FAIL] selftests: tm-vmxcopy [FAIL] Full run log is attached. == Comment: #5 - Harish Sriram - 2017-08-08 03:33:36 == With the latest ubuntu mainline kernel 4.13-rc4 from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc4/, I see following additional failures selftests: ptrace-gpr [FAIL] selftests: ptrace-tm-gpr [FAIL] selftests: ptrace-tm-spd-gpr [FAIL] # uname -a Linux ltc-test-ci2 4.13.0-041300rc4-generic #201708062231 SMP Mon Aug 7 03:29:19 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Thanks, Harish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1711283/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752026] Re: Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default machine type(pseries-bionic) complaining "KVM implementation does not support Transactional Memo
Sorry, but to be sure is that a clear "yes please disable HTM by default in qemu on ppc64el for Ubuntu 18.04" ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752026 Title: Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default machine type(pseries-bionic) complaining "KVM implementation does not support Transactional Memory, try cap-htm=off" (kvm) Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: New Status in qemu package in Ubuntu: Incomplete Bug description: == Comment: #0 - Satheesh Rajendran- 2018-02-23 08:31:06 == ---Problem Description--- libvirt unable to start a KVM guest complaining about cap-htm machine property to be off Host Env: # lscpu Architecture:ppc64le Byte Order: Little Endian CPU(s): 160 On-line CPU(s) list: 0-159 Thread(s) per core: 4 Core(s) per socket: 20 Socket(s): 2 NUMA node(s):2 Model: 2.2 (pvr 004e 1202) Model name: POWER9 (raw), altivec supported CPU max MHz: 3800. CPU min MHz: 2166. L1d cache: 32K L1i cache: 32K L2 cache:512K L3 cache:10240K NUMA node0 CPU(s): 0-79 NUMA node8 CPU(s): 80-159 ii qemu-kvm 1:2.11+dfsg-1ubuntu2 ppc64el QEMU Full virtualization on x86 hardware ii libvirt-bin 4.0.0-1ubuntu3 ppc64el programs for the libvirt library # lsmcode Version of System Firmware : Product Name : OpenPOWER Firmware Product Version : open-power-SUPERMICRO-P9DSU-V1.03-20180205-imp Product Extra : occ-577915f Product Extra : skiboot-v5.9-240-g081882690163-pcbedce4 Product Extra : petitboot-v1.6.6-p019c87e Product Extra : sbe-095e608 Product Extra : machine-xml-fb5f933 Product Extra : hostboot-9bfb201 Product Extra : linux-4.14.13-openpower1-p78d7eee Contact Information = sathe...@in.ibm.com ---uname output--- 4.15.0-10-generic Machine Type = power9 boston 2.2 (pvr 004e 1202) ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Boot a guest from libvirt with default pseries machine type or pseries-bionic /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 'virt-tests-vm1' --machine pseries --memory=32768 --vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty --memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole WARNING No operating system detected, VM performance may suffer. Specify an OS with --os-variant for optimal results. Starting install... ERRORinternal error: process exited while connecting to monitor: ,id=scsi0-0-0-0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=26 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:77:78:79,bus=pci.0,addr=0x1 -chardev pty,id=charserial0 -device spapr-vty,chardev=charserial0,id=serial0,reg=0x3000 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 -msg timestamp=on 2018-02-23T14:21:11.081809Z qemu-system-ppc64: KVM implementation does not support Transactional Memory, try cap-htm=off Domain installation does not appear to have been successful. If it was, you can restart your domain by running: virsh --connect qemu:///system start virt-tests-vm1 otherwise, please restart your installation. 2. Fails to boot.. Note: if we specify machine type as pseries=2.12 it boots fine like below /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 'virt-tests-vm1' --machine pseries-2.12 --memory=32768 --vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty --memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole WARNING No operating system detected, VM performance may suffer. Specify an OS with --os-variant for optimal results. qemu-cmd line: libvirt+ 4283 1 99 09:26 ?00:00:38 qemu-system-ppc64 -enable-kvm -name guest=virt-tests-vm1,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-4 -virt-tests-vm1/master-key.aes -machine
[Kernel-packages] [Bug 1750379] Re: Distortion Realtek ALC887
** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: pulseaudio (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/1750379 Title: Distortion Realtek ALC887 Status in linux package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Invalid Bug description: Sounds can distort even when not amplified. Amplification worked well for years before recent PulseAudio update. The audio is Realtek ALC887 under an IntelG41 Chipset with GA-G41M-Combo main board; Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 I am seeking to engage upstream for April LTS release. Windows have abandoned this esoteric hardware! Please Ubuntu! Keep a C2D user going! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu6 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fleamour 1049 F pulseaudio /dev/snd/controlC2: fleamour 1049 F pulseaudio /dev/snd/controlC0: fleamour 1049 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Feb 19 13:54:33 2018 InstallationDate: Installed on 2018-02-19 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FB dmi.board.name: G41M-Combo dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFB:bd10/25/2012:svnGigabyteTechnologyCo.,Ltd.:pnG41M-Combo:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41M-Combo:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G41M-Combo dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750379/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1738334] Re: hisilicon hibmc regression due to ea642c3216cb ("drm/ttm: add io_mem_pfn callback")
** Also affects: linux 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/1738334 Title: hisilicon hibmc regression due to ea642c3216cb ("drm/ttm: add io_mem_pfn callback") Status in Linux: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Fix Released Bug description: [SRU Justification] [Impact] On Artful kernels, X fails to start and a kernel splat is printed. This is cbecause ea642c3216cb ("drm/ttm: add io_mem_pfn callback") is incomplete: the hisilicon hibmc driver does not contain the callback and so the kernel tries to execute code at NULL. [Fix] There is a discussion and potential fix at https://lists.freedesktop.org/archives/dri-devel/2017-November/159002.html The fix hasn't landed yet and it looks like they're going to re-engineer the entire section instead. Rather than wait for that and deal with the massive regression potential, the fix I have picked to submit is very very minimal and touches only hibmc. [Regression Potential] Minimal - fix only touches hibmc driver. Tested on D05 board. [Testcase] Install patched kernel, try to start X. If it succeeds, the fix works. If there's a kernel splat, the fix does not work. [Notes] HiSilicon would really like this fix in Artful in such time so that when the next 16.04 point release ships in February, the HWE kernel will work with Xorg. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1738334/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1577140] Re: Wifi Ralink R3290 disabled by default in ubuntu 16.04
Is is the same one as LP: #1745636? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1577140 Title: Wifi Ralink R3290 disabled by default in ubuntu 16.04 Status in linux package in Ubuntu: Confirmed Bug description: I have my personal laptop and it contains PCI Ralink r3290 wifi adaptor with bluetooth and when i have installed the fresh version of Ubuntu 16.04x64 it doesn’t work at all on boot up. The wifi is disabled by default and the it doesn’t activates even by pressing the key and when i go the network settings airplane mode is also enabled and when i try to disable airplane mode it switches back on. I dont know whats going wrong. Earlier my wifi works on ubuntu 15.04. I have tried almost every solution and none works in the latest LTS release. Please help I am unable to use internet in ubuntu ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: boot/vmlinuz-4.4.0-21-generic] ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shankey1536 F pulseaudio /dev/snd/controlC1: shankey1536 F pulseaudio CurrentDesktop: Unity Date: Sun May 1 17:02:12 2016 HibernationDevice: RESUME=UUID=9fdda691-a6ae-4494-99e3-b76fde1f33a6 InstallationDate: Installed on 2016-04-24 (7 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 001 Device 003: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd (Foxlink) Webcam Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard Compaq 15 Notebook PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=609ae58a-a43f-4f7b-9a61-e21d3caf457a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.39 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2211 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.52 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.39:bd05/26/2015:svnHewlett-Packard:pnCompaq15NotebookPC:pvr0991100600087:rvnHewlett-Packard:rn2211:rvr86.52:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: Compaq 15 Notebook PC dmi.product.version: 0991100600087 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577140/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]
Saleh, please also mention which version of Ubuntu you are using. ** Tags added: a2dp-skip -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/405294 Title: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] Status in PulseAudio: Confirmed Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Invalid Bug description: As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/405294/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
** Description changed: - The AC adapter status is incorrectly reported when the battery is fully - charged. It always shows as if the adapter is not plugged in. If the - battery is drained for a while, the adapter status is shown correctly - (both connects and disconnects are shown). + === SRU Justification === + [Impact] + Some Asus laptops report "discharging" when the battery is full and AC + is plugged + + [Test] + Charge battery to full, the issue appears. + Users report with the patch the behaviour is correct. + + [Fix] + The discharge rate is 0 on those machines. Use that to detect the wrong + status report. + + [Regression Potential] + Low. The quirk uses strict DMI to match affected systems. + + === Original Bug Report === + The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: abarto 1388 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) 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 04f2:b57a Chicony Electronics Co., Ltd - Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + 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 04f2:b57a Chicony Electronics Co., Ltd + Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-4.13.0-31-generic N/A - linux-backports-modules-4.13.0-31-generic N/A - linux-firmware 1.169.2 + linux-restricted-modules-4.13.0-31-generic N/A + linux-backports-modules-4.13.0-31-generic N/A + linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK 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.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER 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/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in linux package in Ubuntu: Triaged Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto
[Kernel-packages] [Bug 1661876] Re: [Asus UX360UA] battery status in unity-panel is not changing when battery is being charged
** Description changed: - I've just installed Ubuntu 16.04.1 in dualboot on top of an Asus - UX360UA, alongside with Windows 10. I've already installed the updates - meanwhile. + === SRU Justification === + [Impact] + Some Asus laptops report "discharging" when the battery is full and AC + is plugged + + [Test] + Charge battery to full, the issue appears. + Users report with the patch the behaviour is correct. + + [Fix] + The discharge rate is 0 on those machines. Use that to detect the wrong + status report. + + [Regression Potential] + Low. The quirk uses strict DMI to match affected systems. + + === Original Bug Report === + I've just installed Ubuntu 16.04.1 in dualboot on top of an Asus UX360UA, alongside with Windows 10. I've already installed the updates meanwhile. When I start charging my computer the battery icon on the unity-panel is not changing (it stays in the 98% complete). This is strange because this is a fresh installation so I didn't change any configuration yet. Also, when I tried this ubuntu in the live pen, I noticed that the icon changed when I started charging the laptop. That's why I think it is a bug. - --- + --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: tjiagom1806 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: tjiagom1806 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0eaf9255-c29a-41b7-8449-1eb52f637933 InstallationDate: Installed on 2017-02-04 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 002: ID 04f2:b56b Chicony Electronics Co., Ltd - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 002: ID 04f2:b56b Chicony Electronics Co., Ltd + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX360UA Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic.efi.signed root=UUID=6ca1f963-632a-401d-80db-610ef37f1f26 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 RelatedPackageVersions: - linux-restricted-modules-4.4.0-62-generic N/A - linux-backports-modules-4.4.0-62-generic N/A - linux-firmware1.157.6 + linux-restricted-modules-4.4.0-62-generic N/A + linux-backports-modules-4.4.0-62-generic N/A + linux-firmware1.157.6 Tags: xenial Uname: Linux 4.4.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/17/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX360UA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX360UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX360UA.300:bd06/17/2016:svnASUSTeKCOMPUTERINC.:pnUX360UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX360UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX360UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER 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/1661876 Title: [Asus UX360UA] battery status in unity-panel is not changing when battery is being charged Status in linux package in Ubuntu: Confirmed Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === I've just installed Ubuntu 16.04.1 in dualboot on top of an Asus UX360UA, alongside with Windows 10. I've already installed the updates meanwhile. When I start charging my computer the battery icon on the unity-panel is not changing (it stays in the 98% complete). This is strange because this is a fresh installation so I didn't change any configuration yet. Also, when I tried this ubuntu in the live pen, I noticed that the icon changed when I started charging the laptop. That's why I think it is a bug. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse:
Re: [Kernel-packages] [Bug 1729010] Re: USB hub stops working after suspend(s?)
> On Mar 1, 2018, at 2:27 AM, Joe Barnettwrote: > > in limited testing so far, v4.16-rc2 appears better Is the issue gone completely in v4.16-rc2? > > -- > You received this bug notification because you are subscribed to linux > in Ubuntu. > https://bugs.launchpad.net/bugs/1729010 > > Title: > USB hub stops working after suspend(s?) > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > On initial boot, my usb hub works fine, but after a (series of?) > suspends, I stop being able to see devices that are plugged into it. > journalctl output on plugging it in: > > Oct 31 07:08:36 spiny kernel: usb 1-1: new high-speed USB device number 21 > using xhci_hcd > Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device found, idVendor=0409, > idProduct=005a > Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device strings: Mfr=0, > Product=0, SerialNumber=0 > Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: USB hub found > Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: 4 ports detected > Oct 31 07:08:36 spiny kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= > SRC=fe80::::a299:9bff:fe17:9047 > DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 > FLOWLBL=32325 PROTO=UDP SPT=8612 DPT=8612 LEN=24 > Oct 31 07:08:36 spiny kernel: usb 1-1.1: new high-speed USB device number > 22 using xhci_hcd > Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device found, > idVendor=0b95, idProduct=772a > Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device strings: Mfr=1, > Product=2, SerialNumber=3 > Oct 31 07:08:36 spiny kernel: usb 1-1.1: Product: AX88x72A > Oct 31 07:08:36 spiny kernel: usb 1-1.1: Manufacturer: ASIX Elec. Corp. > Oct 31 07:08:36 spiny kernel: usb 1-1.1: SerialNumber: 47EDE2 > Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 eth0: register 'asix' at > usb-:00:14.0-1.1, ASIX AX88772 USB 2.0 Ethernet, 00:50:b6:47:ed:e2 > Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.0438] > manager: (eth0): new Ethernet device > (/org/freedesktop/NetworkManager/Devices/7) > Oct 31 07:08:37 spiny mtp-probe[13207]: checking bus 1, device 22: > "/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1" > Oct 31 07:08:37 spiny mtp-probe[13207]: bus: 1, device: 22 was not an MTP > device > Oct 31 07:08:37 spiny systemd-udevd[13206]: link_config: autonegotiation is > unset or enabled, the speed and duplex are not writable. > Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 enx0050b647ede2: renamed from > eth0 > Oct 31 07:08:37 spiny pkexec[13215]: pam_unix(polkit-1:session): session > opened for user root by (uid=1000) > Oct 31 07:08:37 spiny pkexec[13215]: jbarnett: Executing command > [USER=root] [TTY=unknown] [CWD=/home/jbarnett] > [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness > 31] > Oct 31 07:08:37 spiny pkexec[13214]: gdm: Error executing command as > another user: Not authorized [USER=root] [TTY=unknown] [CWD=/var/lib/gdm3] > [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness > 48] > Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: Error > executing command as another user: Not authorized > Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: This > incident has been reported. > Oct 31 07:08:37 spiny systemd-networkd[1119]: eth0: Renamed to > enx0050b647ede2 > Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1066] > device (eth0): interface index 10 renamed iface from 'eth0' to > 'enx0050b647ede2' > Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] > devices added (path: > /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, > iface: enx0050b647ede2) > Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] > device added (path: > /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, > iface: enx0050b647ede2): no ifupdown configuration found. > Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1217] > device (enx0050b647ede2): state change: unmanaged -> unavailable (reason > 'managed', internal state 'external') > Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: > link is not ready > Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: > link is not ready > Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1274] > keyfile: add connection in-memory > (9365f42f-9dd9-3bdc-bbad-e7062efcaf7c,"Wired connection 4") > Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1284] > settings: (enx0050b647ede2): created default wired connection 'Wired > connection 4' > Oct 31 07:08:37 spiny systemd[1]: Starting > systemd-resolved-update-resolvconf.service... > Oct 31 07:08:37 spiny systemd[1]: Started > systemd-resolved-update-resolvconf.service. > Oct 31 07:08:37 spiny kernel: usb 1-1.2: new full-speed USB device number
[Kernel-packages] [Bug 1738334] Re: hisilicon hibmc regression due to ea642c3216cb ("drm/ttm: add io_mem_pfn callback")
** Description changed: [SRU Justification] [Impact] - On Artful kernels, X fails to start and a kernel splat is printed. + On Artful and Bionic kernels, X fails to start and a kernel splat is printed. This is cbecause ea642c3216cb ("drm/ttm: add io_mem_pfn callback") is incomplete: the hisilicon hibmc driver does not contain the callback and so the kernel tries to execute code at NULL. [Fix] - There is a discussion and potential fix at https://lists.freedesktop.org/archives/dri-devel/2017-November/159002.html The fix hasn't landed yet and it looks like they're going to re-engineer the entire section instead. - Rather than wait for that and deal with the massive regression - potential, the fix I have picked to submit is very very minimal and - touches only hibmc. + Bionic: There is a generic fix in 4.16 at + c67fa6edc8b11afe22c88a23963170bf5f151acf. It is part of a series that + applies this generic fix and does a bunch of cleanups; we can safely + just pick up the generic fix. + + Artful: Rather than a generic fix, I have submitted a very very minimal + fix that only touches hibmc. [Regression Potential] - Minimal - fix only touches hibmc driver. Tested on D05 board. + Artful: Minimal - fix only touches hibmc driver. Tested on D05 board. + Bionic: fix is to generic drm code, but is small and easily reviewable. [Testcase] Install patched kernel, try to start X. If it succeeds, the fix works. If there's a kernel splat, the fix does not work. [Notes] - HiSilicon would really like this fix in Artful in such time so that when the next 16.04 point release ships in February, the HWE kernel will work with Xorg. + Artful: HiSilicon would really like this fix in Artful in such time so that when the next 16.04 point release ships, the HWE kernel will work with Xorg. + + Bionic: no extra notes. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1738334 Title: hisilicon hibmc regression due to ea642c3216cb ("drm/ttm: add io_mem_pfn callback") Status in Linux: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Fix Released Bug description: [SRU Justification] [Impact] On Artful and Bionic kernels, X fails to start and a kernel splat is printed. This is cbecause ea642c3216cb ("drm/ttm: add io_mem_pfn callback") is incomplete: the hisilicon hibmc driver does not contain the callback and so the kernel tries to execute code at NULL. [Fix] Bionic: There is a generic fix in 4.16 at c67fa6edc8b11afe22c88a23963170bf5f151acf. It is part of a series that applies this generic fix and does a bunch of cleanups; we can safely just pick up the generic fix. Artful: Rather than a generic fix, I have submitted a very very minimal fix that only touches hibmc. [Regression Potential] Artful: Minimal - fix only touches hibmc driver. Tested on D05 board. Bionic: fix is to generic drm code, but is small and easily reviewable. [Testcase] Install patched kernel, try to start X. If it succeeds, the fix works. If there's a kernel splat, the fix does not work. [Notes] Artful: HiSilicon would really like this fix in Artful in such time so that when the next 16.04 point release ships, the HWE kernel will work with Xorg. Bionic: no extra notes. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1738334/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1750385] Re: Poor wifi signal with RTL8723BE and 4.13.0-32 kernel
Do you enable Bluetooth in Manjaro? This might be yet another WiFi/BT coexist bug... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1750385 Title: Poor wifi signal with RTL8723BE and 4.13.0-32 kernel Status in linux package in Ubuntu: Confirmed Bug description: When using Linux Mint 18.3 alongside with the 4.13.0-32 kernel the wifi signal is really really poor (while almost sitting on the respective router) whereas with the 4.10.0-38 it works like charm. I had to use a configuration file for getting the wifi to work properly (/etc/modprobe.d/rtl8723be.conf: options rtl8723be fwlps=0 ips=0 ant_sel=1) but chaning the antenna from 1 to 0 did not change anything with the 4.13 kernel. I am also running Manjaro Linux with the 4.14 kernel on my machine where the wifi is also working just fine (with antenna 0 though). cat /proc/version_signature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 (I tried using ubuntu-bug linux but it didn't work [The report belongs to a package that is not installed.]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752026] Comment bridged from LTC Bugzilla
--- Comment From sura...@au1.ibm.com 2018-03-01 01:22 EDT--- Seems like the best option in my opinion -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752026 Title: Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default machine type(pseries-bionic) complaining "KVM implementation does not support Transactional Memory, try cap-htm=off" (kvm) Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: New Status in qemu package in Ubuntu: Incomplete Bug description: == Comment: #0 - Satheesh Rajendran- 2018-02-23 08:31:06 == ---Problem Description--- libvirt unable to start a KVM guest complaining about cap-htm machine property to be off Host Env: # lscpu Architecture:ppc64le Byte Order: Little Endian CPU(s): 160 On-line CPU(s) list: 0-159 Thread(s) per core: 4 Core(s) per socket: 20 Socket(s): 2 NUMA node(s):2 Model: 2.2 (pvr 004e 1202) Model name: POWER9 (raw), altivec supported CPU max MHz: 3800. CPU min MHz: 2166. L1d cache: 32K L1i cache: 32K L2 cache:512K L3 cache:10240K NUMA node0 CPU(s): 0-79 NUMA node8 CPU(s): 80-159 ii qemu-kvm 1:2.11+dfsg-1ubuntu2 ppc64el QEMU Full virtualization on x86 hardware ii libvirt-bin 4.0.0-1ubuntu3 ppc64el programs for the libvirt library # lsmcode Version of System Firmware : Product Name : OpenPOWER Firmware Product Version : open-power-SUPERMICRO-P9DSU-V1.03-20180205-imp Product Extra : occ-577915f Product Extra : skiboot-v5.9-240-g081882690163-pcbedce4 Product Extra : petitboot-v1.6.6-p019c87e Product Extra : sbe-095e608 Product Extra : machine-xml-fb5f933 Product Extra : hostboot-9bfb201 Product Extra : linux-4.14.13-openpower1-p78d7eee Contact Information = sathe...@in.ibm.com ---uname output--- 4.15.0-10-generic Machine Type = power9 boston 2.2 (pvr 004e 1202) ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Boot a guest from libvirt with default pseries machine type or pseries-bionic /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 'virt-tests-vm1' --machine pseries --memory=32768 --vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty --memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole WARNING No operating system detected, VM performance may suffer. Specify an OS with --os-variant for optimal results. Starting install... ERRORinternal error: process exited while connecting to monitor: ,id=scsi0-0-0-0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=26 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:77:78:79,bus=pci.0,addr=0x1 -chardev pty,id=charserial0 -device spapr-vty,chardev=charserial0,id=serial0,reg=0x3000 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 -msg timestamp=on 2018-02-23T14:21:11.081809Z qemu-system-ppc64: KVM implementation does not support Transactional Memory, try cap-htm=off Domain installation does not appear to have been successful. If it was, you can restart your domain by running: virsh --connect qemu:///system start virt-tests-vm1 otherwise, please restart your installation. 2. Fails to boot.. Note: if we specify machine type as pseries=2.12 it boots fine like below /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 'virt-tests-vm1' --machine pseries-2.12 --memory=32768 --vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty --memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole WARNING No operating system detected, VM performance may suffer. Specify an OS with --os-variant for optimal results. qemu-cmd line: libvirt+ 4283 1 99 09:26 ?00:00:38 qemu-system-ppc64 -enable-kvm -name guest=virt-tests-vm1,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-4 -virt-tests-vm1/master-key.aes -machine
[Kernel-packages] [Bug 1738334] Re: hisilicon hibmc regression due to ea642c3216cb ("drm/ttm: add io_mem_pfn callback")
Hi Fred, Thanks for the update. I have tried to nominate the bug for Bionic; I think the kernel team normally does this so we will see if that has worked. More importantly, I will test and send a patch for Bionic shortly. Regards, Daniel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1738334 Title: hisilicon hibmc regression due to ea642c3216cb ("drm/ttm: add io_mem_pfn callback") Status in Linux: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Fix Released Bug description: [SRU Justification] [Impact] On Artful kernels, X fails to start and a kernel splat is printed. This is cbecause ea642c3216cb ("drm/ttm: add io_mem_pfn callback") is incomplete: the hisilicon hibmc driver does not contain the callback and so the kernel tries to execute code at NULL. [Fix] There is a discussion and potential fix at https://lists.freedesktop.org/archives/dri-devel/2017-November/159002.html The fix hasn't landed yet and it looks like they're going to re-engineer the entire section instead. Rather than wait for that and deal with the massive regression potential, the fix I have picked to submit is very very minimal and touches only hibmc. [Regression Potential] Minimal - fix only touches hibmc driver. Tested on D05 board. [Testcase] Install patched kernel, try to start X. If it succeeds, the fix works. If there's a kernel splat, the fix does not work. [Notes] HiSilicon would really like this fix in Artful in such time so that when the next 16.04 point release ships in February, the HWE kernel will work with Xorg. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1738334/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Please change the line in the patch from "return NVME_QUIRK_PCI_RESET_RESUME"; to "return (NVME_QUIRK_PCI_RESET_RESUME | NVME_QUIRK_NO_DEEPEST_PS); And see if this still happens. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.13.0-21.24-generic 4.13.13 I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 17.04, which gave me this error after 2 weeks of usage. After that, I installed 16.04 and used it for MONTHS without any problems, until it produced the same error this week. I think it has to do with the ubuntu updates, because I did one recently and one today, just before this problem. Could be a coincidence though. I notice the error when I try to save something on disk and it says me that the disk is in read-only mode: lz@lz:/var/log$ touch something touch: cannot touch 'something': Read-only file system lz@lz:/var/log$ cat syslog Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 lz@lz:/var/log$ dmesg [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.377374] Aborting journal on device nvme0n1p2-8. [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" capability=12 capname="net_admin" Rebooting the ubuntu will give me a black terminal where I can run fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of orphaned inodes. The majority of time it boots back to the Ubuntu working good, but some times it boots to a broken ubuntu (no images, lots of things broken). I have to reinstall ubuntu then. Every time I reinstall my Ubuntu, I have to try lots of times until it installs without an Input/Output error. When it installs, I can use it for some hours without having the problem, but if I run the software updates, it ALWAYS crashes and enters in read-only mode, specifically in the part that is installing kernel updates. I noticed that Ubuntu installs updates automatically when they're for security reasons. Could this be the reason my Ubuntu worked for months without the problem, but then an update was applied and it broke? I thought that this bug was happening: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried different nvme_core.default_ps_max_latency_us= combinations, all them gave errors. I just changed to 0 and I had no error while using ubuntu (however I didn't test for a long time) but I still had the error after trying to update my ubuntu. My Samsung 512gb SSD is: SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q on a Razer Blade Stealth. I also asked this on ask ubuntu, without success: https://askubuntu.com/questions/998471/razer-blade-stealth-disk- corruption-fsck-needed-probably-samsung-ssd-bug-afte Please help me, as I need this computer to work on lots of things :c --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lz 1088 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2018-01-30 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Razer Blade Stealth Package: linux (not installed)
[Kernel-packages] [Bug 1746164] Re: [ath9k] Enable Bluetooth-Wifi coexistence by default (bluetooth audio and network skip on Wifi activity)
** Tags added: a2dp-skip -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1746164 Title: [ath9k] Enable Bluetooth-Wifi coexistence by default (bluetooth audio and network skip on Wifi activity) Status in linux package in Ubuntu: Confirmed Bug description: By default BT audio works fine on Ubuntu - if there is no WiFi active: Both work on the same frequency range, 2 WiFi channel is about 20 Bluetooth Channels wide and every time a WiFi package is sent bluetooth risks a packet loss. Creating a file named /etc/modprobe.d/bluetooth-audio.conf with the following content: options ath9k btcoex_enable=1 bt_ant_diversity=1 resolves the problem and drastically increases bluetooth throughput for all other use cases (bluetooth networking that doesn't drop every time the WiFi probes something, lower latency Bluetooth HIDs. We should ship things in a way that they work out-of-the-box => I am all for providing this file with Ubuntu, possibly with Bluez. In the case of my laptop btcoex_enable=1 would already do the trick. Technical background: - https://wireless.wiki.kernel.org/en/users/drivers/ath9k/btcoex - https://wiki.freebsd.org/dev/ath_hal(4)/AntennaDiversity ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.46-0ubuntu4 Uname: Linux 4.15.0-041500rc9-lowlatency x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jan 30 06:40:12 2018 EcryptfsInUse: Yes InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire S7-391 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-041500rc9-lowlatency root=UUID=6d0fd0ad-9048-4fdb-881a-eba6d6d13c3b ro rootflags=subvol=@ acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable nmi_watchdog=0 quiet splash acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable video=vesafb:ywrap,mtrr=3 nmi_watchdog=0 vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.09 dmi.board.asset.tag: No Asset Tag dmi.board.name: Storm dmi.board.vendor: Acer dmi.board.version: V2.09 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.09 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.09:bd11/16/2012:svnAcer:pnAspireS7-391:pvrV2.09:rvnAcer:rnStorm:rvrV2.09:cvnAcer:ct10:cvrV2.09: dmi.product.family: ChiefRiver System dmi.product.name: Aspire S7-391 dmi.product.version: V2.09 dmi.sys.vendor: Acer hciconfig: hci0:Type: Primary Bus: USB BD Address: 68:94:23:49:1B:BC ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN RX bytes:688 acl:0 sco:0 events:49 errors:0 TX bytes:3167 acl:0 sco:0 commands:49 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746164/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1482390] Re: ASUS UX305LA - Battery state not detected correctly
** Description changed: + === SRU Justification === + [Impact] + Some Asus laptops report "discharging" when the battery is full and AC + is plugged + + [Test] + Charge battery to full, the issue appears. + Users report with the patch the behaviour is correct. + + [Fix] + The discharge rate is 0 on those machines. Use that to detect the wrong + status report. + + [Regression Potential] + Low. The quirk uses strict DMI to match affected systems. + + === Original Bug Report === + Whether the AC adapter is connected or not, the battery is always detected as discharging: When AC adapter is present: $ sudo acpitool -a -b Battery #1 : Discharging, 100.0% AC adapter : online $ sudo acpitool -B Battery #1 : present Remaining capacity : 54027 mWh, 100.0% Design capacity: 56041 mWh Last full capacity : 53507 mWh, 95.48% of design capacity Capacity loss : 4.522% Present rate : 0 mW Charging state : Discharging Battery type : Li-ion Model number : ASUS When AC adapter is not present: $ sudo acpitool -a -b Battery #1 : Discharging, 100.0%, 04:19:49 AC adapter : off-line $ sudo acpitool -B Battery #1 : present Remaining capacity : 54005 mWh, 100.0%, 04:28:31 Design capacity: 56041 mWh Last full capacity : 53507 mWh, 95.48% of design capacity Capacity loss : 4.522% Present rate : 12067 mW Charging state : Discharging Battery type : Li-ion Model number : ASUS System information: $ sudo dmidecode # dmidecode 2.12 # SMBIOS entry point at 0xace2a898 SMBIOS 2.8 present. 27 structures occupying 2154 bytes. Table at 0xAC7C6000. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: American Megatrends Inc. Version: UX305LA.202 Release Date: 04/16/2015 Address: 0xF Runtime Size: 64 kB ROM Size: 6464 kB Characteristics: PCI is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported BIOS ROM is socketed EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported Smart battery is supported BIOS boot specification is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 5.6 Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: ASUSTeK COMPUTER INC. Product Name: UX305LA Version: 1.0 Serial Number: xxx UUID: xxx Wake-up Type: Power Switch SKU Number: ASUS-NotebookSKU Family: UX Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: ASUSTeK COMPUTER INC. Product Name: UX305LA Version: 1.0 Serial Number: xxx Asset Tag: xxx Features: Board is a hosting board Board is replaceable Location In Chassis: MIDDLE Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 Handle 0x0003, DMI type 3, 25 bytes Chassis Information Manufacturer: ASUSTeK COMPUTER INC. Type: Notebook Lock: Not Present Version: 1.0 Serial Number: xxx Asset Tag: xxx Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: None OEM Information: 0x Height: Unspecified Number Of Power Cords: 1 Contained Elements: 1 (0) SKU Number: To be filled by O.E.M. Handle 0x0004, DMI type 10, 26 bytes On Board Device 1 Information Type: Video Status: Enabled Description: VGA On Board Device 2 Information Type: Ethernet Status: Enabled Description: GLAN On Board Device 3 Information Type: Ethernet Status: Enabled Description: WLAN On Board Device 4 Information Type: Sound Status: Enabled Description: Audio CODEC On Board Device 5 Information Type: SATA Controller Status: Enabled Description: SATA Controller On Board Device 6 Information Type: Other Status: Enabled Description: USB 2.0 Controller On Board Device 7 Information Type: Other Status: Enabled Description: USB 3.0 Controller On Board Device 8 Information Type: Other Status: Enabled Description: SMBus Controller On Board Device 9 Information Type: Other Status: Enabled Description: Card Reader On Board Device 10 Information Type: Other Status: Enabled Description: Cmos Camera On Board Device 11 Information Type: Other Status: Enabled Description: Bluetooth Handle 0x0005, DMI type 11, 5 bytes OEM
[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Ok, I'm compiling it now on my other PC. Meanwhile, the error happened twice in the same day. That's odd, it usually took at least 2 days to manifest again. Could it be that something chanded on my PC? Anyways, here's the error: 4609.325351] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1447: inode #26610978: comm updatedb.mlocat: checksumming directory block 0 [ 4609.327443] Aborting journal on device nvme0n1p2-8. [ 4609.329533] EXT4-fs (nvme0n1p2): Remounting filesystem read-only [ 4609.357281] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1447: inode #26739117: comm updatedb.mlocat: checksumming directory block 0 [ 4609.627350] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1447: inode #5901277: comm updatedb.mlocat: checksumming directory block 0 [ 4795.596378] perf: interrupt took too long (2563 > 2500), lowering kernel.perf_event_max_sample_rate to 78000 [ 4911.346846] audit: type=1400 audit(1519876882.781:29): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=4149 comm="cupsd" capability=12 capname="net_admin" I'll test the new compiler kernel in some hours -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.13.0-21.24-generic 4.13.13 I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 17.04, which gave me this error after 2 weeks of usage. After that, I installed 16.04 and used it for MONTHS without any problems, until it produced the same error this week. I think it has to do with the ubuntu updates, because I did one recently and one today, just before this problem. Could be a coincidence though. I notice the error when I try to save something on disk and it says me that the disk is in read-only mode: lz@lz:/var/log$ touch something touch: cannot touch 'something': Read-only file system lz@lz:/var/log$ cat syslog Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 lz@lz:/var/log$ dmesg [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.377374] Aborting journal on device nvme0n1p2-8. [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" capability=12 capname="net_admin" Rebooting the ubuntu will give me a black terminal where I can run fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of orphaned inodes. The majority of time it boots back to the Ubuntu working good, but some times it boots to a broken ubuntu (no images, lots of things broken). I have to reinstall ubuntu then. Every time I reinstall my Ubuntu, I have to try lots of times until it installs without an Input/Output error. When it installs, I can use it for some hours without having the problem, but if I run the software updates, it ALWAYS crashes and enters in read-only mode, specifically in the part that is installing kernel updates. I noticed that Ubuntu installs updates automatically when they're for security reasons. Could this be the reason my Ubuntu worked for months without the problem, but then an update was applied and it broke? I thought that this bug was happening: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried different nvme_core.default_ps_max_latency_us= combinations, all them gave errors. I just changed to
[Kernel-packages] [Bug 1749420] Re: [regression] Colour banding and artefacts appear system-wide on an Asus Zenbook UX303LA with Intel HD 4400 graphics
It's already in the upstream. We only need to backport it to Artful's kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1749420 Title: [regression] Colour banding and artefacts appear system-wide on an Asus Zenbook UX303LA with Intel HD 4400 graphics Status in linux package in Ubuntu: Confirmed Bug description: - Ubuntu 18.04 (with updates as of 14 Feb 2018). - Laptop: Asus Zenbook UX303 - CPU: Intel i5 4210U - Graphics: Intel HD 4400 Problem description: Colour artefacts and banding in all apps. Graphics, photos and videos display as though the colour range is improperly configured. See this photo of a 1080p video taken with a camera (poor quality, but illustrates the issue): https://ubuntucommunity.s3-us- east-2.amazonaws.com/original/2X/c/c8f266715226953c6a77db6367ff9b7895784e35.jpg Look at the sky’s light colours. They display with smooth gradients on Ubuntu 16.04, but as the photo illustrates 18.04 seems to display the video with a smaller range of white colours. This is the most apparent with either very dark or very light colours. Even on window titlebars the banding is visible (displayed as lines with different shades of grey/black). Compared with a PrtSc shot of the same image: https://i.imgur.com/VkOSCaQ.png The artefacts are not present on PrtSc shots that are taken on Ubuntu 18.04 but viewed on a different system (16.04 and Windows). Installing a previous kernel version fixes the issue completely. I used UKUU Update Utility to install kernel 4.4 (the same that I use in Ubuntu 16.04 without issues) and upon a reboot with 4.4 running on 18.04 everything displayed smoothly. So this indicates that the system might be using a sub-optimal colour depth with the newer kernel? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified: boot/vmlinuz-4.13.0-32-generic] ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ystein 1344 F pulseaudio /dev/snd/controlC1: ystein 1344 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Feb 14 11:25:43 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=d0bae648-a4d8-454c-b9fc-4cc04874d6c1 InstallationDate: Installed on 2018-02-12 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX303LA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=25279d7b-cc8a-4fee-9088-cfc69607cbca ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.170 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303LA 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.:bvrUX303LA.204:bd09/01/2014:svnASUSTeKCOMPUTERINC.:pnUX303LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX303LA 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/1749420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1749040] Re: KPTI support for arm64 systems
Refreshed kernel now in ppa:dannf/kpti -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1749040 Title: KPTI support for arm64 systems Status in linux package in Ubuntu: Incomplete Status in linux source package in Artful: In Progress Status in linux source package in Bionic: Incomplete Bug description: While regression testing the current linux-hwe proposed kernel (4.13.0-33.36~16.04.1), I found that it fails to boot on a Cavium ThunderX CRB. I've rebooted twice since upgrading from the current -updates kernel, and it's failed to boot both times, with different failure modes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742316] Re: DVB Card with SAA7146 chipset not working
** Description changed: - After upgrading to 17.10 (from 16.04 with 4.4 kernel) my PCI DVB card - Terratec Cinergy DVB-1200 with SAA7146 chipset is not working anymore. - There is a kernel bug message while booting and no /dev/dvb device is - created. Tried also with newest mainline 4.14 kernel - same error. + === SRU Justification === + [Impact] + Callers vmalloc_32() expect the page is not located in highmem. + All users of vmalloc_32() have this issue, module saa7146 is one of + them. + + [Test] + saa7146 crashes at probing. The issue is fixed with the patch. + + [Fix] + Add GFP_DMA32 to GFP_VMALLOC32 flag for 32bits systems. + The patch is in stable trees, so only Artful needs this patch. + + [Regression Potential] + Low. It's a crucial fix for 32bits systems. + + === Original Bug Report === + After upgrading to 17.10 (from 16.04 with 4.4 kernel) my PCI DVB card Terratec Cinergy DVB-1200 with SAA7146 chipset is not working anymore. There is a kernel bug message while booting and no /dev/dvb device is created. Tried also with newest mainline 4.14 kernel - same error. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.13.0-25-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Date: Wed Jan 10 00:42:24 2018 HibernationDevice: RESUME=UUID=342e30a6-d71f-47c0-b65a-5ba657a80456 InstallationDate: Installed on 2016-02-13 (696 days ago) InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release i386 (20151021) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=de_DE.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=de_DE.UTF-8 + SHELL=/bin/bash ProcFB: 0 psbdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic root=UUID=97ea5186-d18d-4c06-a8b2-2dd1417477be ro splash quiet acpi=force video=LVDS-1:d vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-4.13.0-25-generic N/A - linux-backports-modules-4.13.0-25-generic N/A - linux-firmware 1.169.1 + linux-restricted-modules-4.13.0-25-generic N/A + linux-backports-modules-4.13.0-25-generic N/A + linux-firmware 1.169.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to artful on 2016-07-07 (551 days ago) dmi.bios.date: 04/19/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.60 dmi.board.name: AD2700-ITX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd04/19/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAD2700-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742316 Title: DVB Card with SAA7146 chipset not working Status in linux package in Ubuntu: Confirmed Bug description: === SRU Justification === [Impact] Callers vmalloc_32() expect the page is not located in highmem. All users of vmalloc_32() have this issue, module saa7146 is one of them. [Test] saa7146 crashes at probing. The issue is fixed with the patch. [Fix] Add GFP_DMA32 to GFP_VMALLOC32 flag for 32bits systems. The patch is in stable trees, so only Artful needs this patch. [Regression Potential] Low. It's a crucial fix for 32bits systems. === Original Bug Report === After upgrading to 17.10 (from 16.04 with 4.4 kernel) my PCI DVB card Terratec Cinergy DVB-1200 with SAA7146 chipset is not working anymore. There
[Kernel-packages] [Bug 1749420] Re: [regression] Colour banding and artefacts appear system-wide on an Asus Zenbook UX303LA with Intel HD 4400 graphics
** Description changed: + === SRU Justification === + [Impact] + Color dithering not working correctly because the graphics driver + assumes the panel support 8bpc, but the panel only supports 6bpc. + + [Test] + User reports the issue start appearing from v4.8-rc2. + The issue is fixed with the patch. + + [Fix] + Add a quirk to tell DRM that this panel only supports 6bpc. + + [Regression Potential] + Low. This fix matches a very specific panel. + + === Original Bug Report === - Ubuntu 18.04 (with updates as of 14 Feb 2018). - Laptop: Asus Zenbook UX303 - CPU: Intel i5 4210U - Graphics: Intel HD 4400 Problem description: Colour artefacts and banding in all apps. Graphics, photos and videos display as though the colour range is improperly configured. See this photo of a 1080p video taken with a camera (poor quality, but illustrates the issue): https://ubuntucommunity.s3-us- east-2.amazonaws.com/original/2X/c/c8f266715226953c6a77db6367ff9b7895784e35.jpg Look at the sky’s light colours. They display with smooth gradients on Ubuntu 16.04, but as the photo illustrates 18.04 seems to display the video with a smaller range of white colours. This is the most apparent with either very dark or very light colours. Even on window titlebars the banding is visible (displayed as lines with different shades of grey/black). Compared with a PrtSc shot of the same image: https://i.imgur.com/VkOSCaQ.png The artefacts are not present on PrtSc shots that are taken on Ubuntu 18.04 but viewed on a different system (16.04 and Windows). Installing a previous kernel version fixes the issue completely. I used UKUU Update Utility to install kernel 4.4 (the same that I use in Ubuntu 16.04 without issues) and upon a reboot with 4.4 running on 18.04 everything displayed smoothly. So this indicates that the system might be using a sub-optimal colour depth with the newer kernel? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified: boot/vmlinuz-4.13.0-32-generic] ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: ystein 1344 F pulseaudio - /dev/snd/controlC1: ystein 1344 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: ystein 1344 F pulseaudio + /dev/snd/controlC1: ystein 1344 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Feb 14 11:25:43 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=d0bae648-a4d8-454c-b9fc-4cc04874d6c1 InstallationDate: Installed on 2018-02-12 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180210) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 004: ID 8087:07dc Intel Corp. - Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam - Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 004: ID 8087:07dc Intel Corp. + Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam + Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX303LA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=25279d7b-cc8a-4fee-9088-cfc69607cbca ro quiet splash vt.handoff=1 RelatedPackageVersions: - linux-restricted-modules-4.13.0-32-generic N/A - linux-backports-modules-4.13.0-32-generic N/A - linux-firmware 1.170 + linux-restricted-modules-4.13.0-32-generic N/A + linux-backports-modules-4.13.0-32-generic N/A + linux-firmware 1.170 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303LA 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.:bvrUX303LA.204:bd09/01/2014:svnASUSTeKCOMPUTERINC.:pnUX303LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX303LA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.
[Kernel-packages] [Bug 1738334] Re: hisilicon hibmc regression due to ea642c3216cb ("drm/ttm: add io_mem_pfn callback")
hi daniel this bug also affect this ubuntu 18.04.0 version which using bionic kernel branch(kernel 4.15), because this patchset have merged into mainline linus kernel 4.16rc1 (after kernel 4.15). I want to add this bionic tag, but i fail it. Can you add this bionic tag to merge this patchset into bionic branch. thank you -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1738334 Title: hisilicon hibmc regression due to ea642c3216cb ("drm/ttm: add io_mem_pfn callback") Status in Linux: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Fix Released Bug description: [SRU Justification] [Impact] On Artful kernels, X fails to start and a kernel splat is printed. This is cbecause ea642c3216cb ("drm/ttm: add io_mem_pfn callback") is incomplete: the hisilicon hibmc driver does not contain the callback and so the kernel tries to execute code at NULL. [Fix] There is a discussion and potential fix at https://lists.freedesktop.org/archives/dri-devel/2017-November/159002.html The fix hasn't landed yet and it looks like they're going to re-engineer the entire section instead. Rather than wait for that and deal with the massive regression potential, the fix I have picked to submit is very very minimal and touches only hibmc. [Regression Potential] Minimal - fix only touches hibmc driver. Tested on D05 board. [Testcase] Install patched kernel, try to start X. If it succeeds, the fix works. If there's a kernel splat, the fix does not work. [Notes] HiSilicon would really like this fix in Artful in such time so that when the next 16.04 point release ships in February, the HWE kernel will work with Xorg. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1738334/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1611124] Re: W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module i915
@Robert Focht `4.11.5` is fairly old and won't have Meltdown or Spectre fixes. Do you mean `4.15.5`? Regardless see this link to get Skylake through Kabylake drivers: https://askubuntu.com/questions/832524 /updated-kernel-to-4-8-now-missing-firmware-warnings -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1611124 Title: W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module i915 Status in xen: Unknown Status in linux-firmware package in Ubuntu: Invalid Bug description: $sudo dpkg -i linux-image-4.8.0-040800rc1-lowlatency [...] update-initramfs: Generating /boot/initrd.img-4.8.0-040800rc1-lowlatency W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module i915 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-firmware 1.159 Uname: Linux 4.8.0-040800rc1-lowlatency x86_64 ApportVersion: 2.20.3-0ubuntu5 Architecture: amd64 Date: Mon Aug 8 17:50:38 2016 Dependencies: InstallationDate: Installed on 2015-07-26 (379 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xen/+bug/1611124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1518408] Re: Interrupt audio on bluetooth headset when wifi is on
** Tags added: a2dp-skip ** Also affects: broadcom-sta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1518408 Title: Interrupt audio on bluetooth headset when wifi is on Status in Broadcom 802.11 Linux STA driver: New Status in bcmwl package in Ubuntu: Confirmed Status in broadcom-sta package in Ubuntu: New Bug description: When WiFi and Bluetooth is on, this have conflict! Sound on bluetooth headset is interrupted, ping is high. In syslog: Nov 20 20:28:22 Photonix-Laptop pulseaudio[1250]: [bluetooth] module-bluez5-device.c: Skipping 3939657 us (= 694952 bytes) in audio stream Nov 20 20:28:30 Photonix-Laptop pulseaudio[1250]: [bluetooth] module-bluez5-device.c: Skipping 90008 us (= 15876 bytes) in audio stream Nov 20 20:28:33 Photonix-Laptop pulseaudio[1250]: [bluetooth] module-bluez5-device.c: Skipping 1229297 us (= 216844 bytes) in audio stream Nov 20 20:28:36 Photonix-Laptop pulseaudio[1250]: [bluetooth] module-bluez5-device.c: Skipping 1114638 us (= 196620 bytes) in audio stream Nov 20 20:28:47 Photonix-Laptop pulseaudio[1250]: [bluetooth] module-bluez5-device.c: Skipping 888216 us (= 156680 bytes) in audio stream Nov 20 20:28:51 Photonix-Laptop pulseaudio[1250]: [bluetooth] module-bluez5-device.c: Skipping 1772705 us (= 312704 bytes) in audio stream Chip Broadcom 43142 Combo with Bluetooth (ID 04ca:2009 Lite-On Technology Corp. ) ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu7 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Fri Nov 20 20:55:20 2015 InstallationDate: Installed on 2015-11-20 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/broadcom-sta/+bug/1518408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1733888] Re: iwlwifi Error sending STATISTICS_CMD: time out after 2000ms.
[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/1733888 Title: iwlwifi Error sending STATISTICS_CMD: time out after 2000ms. Status in linux package in Ubuntu: Expired Bug description: This started happening today so probably a new issue caused by a kernel update. Randomly, maybe every 45 minutes wifi disconnects and reconnects. Attached is a log output from dmesg. Looks like issue is in the iwlwifi driver. Disconnect causes TCP connections to drop so it's quite annoying for end user. ThinkPad T460p, up to date kernel on Ubuntu 17.04. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-40-generic 4.10.0-40.44 ProcVersionSignature: Ubuntu 4.10.0-40.44-generic 4.10.17 Uname: Linux 4.10.0-40-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: vranki 2298 F...m pulseaudio /dev/snd/controlC1: vranki 2298 F pulseaudio /dev/snd/controlC0: vranki 2298 F pulseaudio CurrentDesktop: X-Cinnamon Date: Wed Nov 22 16:57:46 2017 HibernationDevice: RESUME=UUID=65d76bf9-e895-4dbb-9424-bfd0d498bd43 InstallationDate: Installed on 2017-03-29 (238 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) MachineType: LENOVO 20FW0042MS ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-40-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-40-generic N/A linux-backports-modules-4.10.0-40-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET71W (2.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW0042MS 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:bvrR07ET71W(2.11):bd09/26/2016:svnLENOVO:pn20FW0042MS:pvrThinkPadT460p:rvnLENOVO:rn20FW0042MS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FW0042MS dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733888/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752026] Comment bridged from LTC Bugzilla
--- Comment From sthou...@in.ibm.com 2018-03-01 00:00 EDT--- *** Bug 165240 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752026 Title: Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default machine type(pseries-bionic) complaining "KVM implementation does not support Transactional Memory, try cap-htm=off" (kvm) Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: New Status in qemu package in Ubuntu: Incomplete Bug description: == Comment: #0 - Satheesh Rajendran- 2018-02-23 08:31:06 == ---Problem Description--- libvirt unable to start a KVM guest complaining about cap-htm machine property to be off Host Env: # lscpu Architecture:ppc64le Byte Order: Little Endian CPU(s): 160 On-line CPU(s) list: 0-159 Thread(s) per core: 4 Core(s) per socket: 20 Socket(s): 2 NUMA node(s):2 Model: 2.2 (pvr 004e 1202) Model name: POWER9 (raw), altivec supported CPU max MHz: 3800. CPU min MHz: 2166. L1d cache: 32K L1i cache: 32K L2 cache:512K L3 cache:10240K NUMA node0 CPU(s): 0-79 NUMA node8 CPU(s): 80-159 ii qemu-kvm 1:2.11+dfsg-1ubuntu2 ppc64el QEMU Full virtualization on x86 hardware ii libvirt-bin 4.0.0-1ubuntu3 ppc64el programs for the libvirt library # lsmcode Version of System Firmware : Product Name : OpenPOWER Firmware Product Version : open-power-SUPERMICRO-P9DSU-V1.03-20180205-imp Product Extra : occ-577915f Product Extra : skiboot-v5.9-240-g081882690163-pcbedce4 Product Extra : petitboot-v1.6.6-p019c87e Product Extra : sbe-095e608 Product Extra : machine-xml-fb5f933 Product Extra : hostboot-9bfb201 Product Extra : linux-4.14.13-openpower1-p78d7eee Contact Information = sathe...@in.ibm.com ---uname output--- 4.15.0-10-generic Machine Type = power9 boston 2.2 (pvr 004e 1202) ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Boot a guest from libvirt with default pseries machine type or pseries-bionic /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 'virt-tests-vm1' --machine pseries --memory=32768 --vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty --memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole WARNING No operating system detected, VM performance may suffer. Specify an OS with --os-variant for optimal results. Starting install... ERRORinternal error: process exited while connecting to monitor: ,id=scsi0-0-0-0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=26 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:77:78:79,bus=pci.0,addr=0x1 -chardev pty,id=charserial0 -device spapr-vty,chardev=charserial0,id=serial0,reg=0x3000 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 -msg timestamp=on 2018-02-23T14:21:11.081809Z qemu-system-ppc64: KVM implementation does not support Transactional Memory, try cap-htm=off Domain installation does not appear to have been successful. If it was, you can restart your domain by running: virsh --connect qemu:///system start virt-tests-vm1 otherwise, please restart your installation. 2. Fails to boot.. Note: if we specify machine type as pseries=2.12 it boots fine like below /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 'virt-tests-vm1' --machine pseries-2.12 --memory=32768 --vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty --memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole WARNING No operating system detected, VM performance may suffer. Specify an OS with --os-variant for optimal results. qemu-cmd line: libvirt+ 4283 1 99 09:26 ?00:00:38 qemu-system-ppc64 -enable-kvm -name guest=virt-tests-vm1,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-4 -virt-tests-vm1/master-key.aes -machine
[Kernel-packages] [Bug 1749040] Re: KPTI support for arm64 systems
** Attachment added: "Updated test results from an HP m400 (X-Gene) system" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+attachment/5065762/+files/submission_2018-03-01T05.58.16.640032.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1749040 Title: KPTI support for arm64 systems Status in linux package in Ubuntu: Incomplete Status in linux source package in Artful: In Progress Status in linux source package in Bionic: Incomplete Bug description: While regression testing the current linux-hwe proposed kernel (4.13.0-33.36~16.04.1), I found that it fails to boot on a Cavium ThunderX CRB. I've rebooted twice since upgrading from the current -updates kernel, and it's failed to boot both times, with different failure modes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752507] [NEW] add i915/glk_dmc_ver1_04.bin
Public bug reported: Intel Gemini Lake needs DMC firmware to fix some S3 issues on xenial. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-firmware (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1752507 Title: add i915/glk_dmc_ver1_04.bin Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Xenial: New Status in linux-firmware source package in Artful: New Bug description: Intel Gemini Lake needs DMC firmware to fix some S3 issues on xenial. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1752507/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752507] Re: add i915/glk_dmc_ver1_04.bin
looks like artful is missing it too -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1752507 Title: add i915/glk_dmc_ver1_04.bin Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Xenial: New Status in linux-firmware source package in Artful: New Bug description: Intel Gemini Lake needs DMC firmware to fix some S3 issues on xenial. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1752507/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1738334] Re: hisilicon hibmc regression due to ea642c3216cb ("drm/ttm: add io_mem_pfn callback")
Call traces for this bug on D05 for kernel 4.15.0-10-generic which tested on 1 March 2018 on 18.04 daily build ** Attachment added: "Call traces for this bug on D05 for kernel 4.15.0-10-generic which tested on 1 March 2018 on 18.04 daily build" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738334/+attachment/5065851/+files/bionic_kernel_oops_on_D05.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1738334 Title: hisilicon hibmc regression due to ea642c3216cb ("drm/ttm: add io_mem_pfn callback") Status in Linux: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Fix Released Bug description: [SRU Justification] [Impact] On Artful and Bionic kernels, X fails to start and a kernel splat is printed. This is cbecause ea642c3216cb ("drm/ttm: add io_mem_pfn callback") is incomplete: the hisilicon hibmc driver does not contain the callback and so the kernel tries to execute code at NULL. [Fix] Bionic: There is a generic fix in 4.16 at c67fa6edc8b11afe22c88a23963170bf5f151acf. It is part of a series that applies this generic fix and does a bunch of cleanups; we can safely just pick up the generic fix. Artful: Rather than a generic fix, I have submitted a very very minimal fix that only touches hibmc. [Regression Potential] Artful: Minimal - fix only touches hibmc driver. Tested on D05 board. Bionic: fix is to generic drm code, but is small and easily reviewable. [Testcase] Install patched kernel, try to start X. If it succeeds, the fix works. If there's a kernel splat, the fix does not work. [Notes] Artful: HiSilicon would really like this fix in Artful in such time so that when the next 16.04 point release ships, the HWE kernel will work with Xorg. Bionic: no extra notes. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1738334/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1738334] Re: hisilicon hibmc regression due to ea642c3216cb ("drm/ttm: add io_mem_pfn callback")
Hawei team just tested and verified this bug on 4.15.0-10-generic kernel on D05 server. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1738334 Title: hisilicon hibmc regression due to ea642c3216cb ("drm/ttm: add io_mem_pfn callback") Status in Linux: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Fix Released Bug description: [SRU Justification] [Impact] On Artful and Bionic kernels, X fails to start and a kernel splat is printed. This is cbecause ea642c3216cb ("drm/ttm: add io_mem_pfn callback") is incomplete: the hisilicon hibmc driver does not contain the callback and so the kernel tries to execute code at NULL. [Fix] Bionic: There is a generic fix in 4.16 at c67fa6edc8b11afe22c88a23963170bf5f151acf. It is part of a series that applies this generic fix and does a bunch of cleanups; we can safely just pick up the generic fix. Artful: Rather than a generic fix, I have submitted a very very minimal fix that only touches hibmc. [Regression Potential] Artful: Minimal - fix only touches hibmc driver. Tested on D05 board. Bionic: fix is to generic drm code, but is small and easily reviewable. [Testcase] Install patched kernel, try to start X. If it succeeds, the fix works. If there's a kernel splat, the fix does not work. [Notes] Artful: HiSilicon would really like this fix in Artful in such time so that when the next 16.04 point release ships, the HWE kernel will work with Xorg. Bionic: no extra notes. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1738334/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1671022] Re: package linux-headers-4.8.0-41 (not installed) failed to install/upgrade: nem sikerült megnyitni: „/usr/src/linux-headers-4.8.0-41/arch/cris/boot/rescue/Makefile.dp
This is an unsupported release now. Please think to install the next LTS 'Bionic 18.04' http://cdimage.ubuntu.com/ubuntu-next/daily-live/current/ https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1671022 Title: package linux-headers-4.8.0-41 (not installed) failed to install/upgrade: nem sikerült megnyitni: „/usr/src/linux- headers-4.8.0-41/arch/cris/boot/rescue/Makefile.dpkg-new”: A művelet nem engedélyezett Status in linux package in Ubuntu: Invalid Bug description: dpkg: Error processing archive: /var/cache/apt/archives/linux-headers-4.8.0-41_4.8.0-41.44_all.deb (--unpack): Can not open: „/usr/src/linux-headers-4.8.0-41/arch/powerpc/include/asm/floppy.h.dpkg-new”: Not permitted Errors while processing: /var/cache/apt/archives/linux-headers-4.8.0-41_4.8.0-41.44_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Nothing special, just unattended upgrades; ProblemType: Package DistroRelease: Ubuntu 16.10 Package: linux-headers-4.8.0-41 (not installed) ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17 Uname: Linux 4.8.0-39-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm2172 F pulseaudio tgortva5919 F pulseaudio /dev/snd/controlC0: gdm2172 F pulseaudio tgortva5919 F pulseaudio Date: Wed Mar 8 08:32:41 2017 ErrorMessage: nem sikerült megnyitni: „/usr/src/linux-headers-4.8.0-41/arch/cris/boot/rescue/Makefile.dpkg-new”: A művelet nem engedélyezett HibernationDevice: RESUME=UUID=d44cff4f-ea6a-47d6-9dc6-270d36dc20f8 InstallationDate: Installed on 2017-03-02 (6 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-39-generic root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu11 RfKill: SourcePackage: linux Title: package linux-headers-4.8.0-41 (not installed) failed to install/upgrade: nem sikerült megnyitni: „/usr/src/linux-headers-4.8.0-41/arch/cris/boot/rescue/Makefile.dpkg-new”: A művelet nem engedélyezett UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F15 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H77-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF15:bd11/14/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH77-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671022/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1670154] Re: package linux-headers-4.8.0-39 (not installed) failed to install/upgrade: impossible d'ouvrir « /usr/src/linux-headers-4.8.0-39/include/uapi/drm/via_drm.h.dpkg-new
This is an unsupported release now. Please think to install the next LTS 'Bionic 18.04' http://cdimage.ubuntu.com/ubuntu-next/daily-live/current/ https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1670154 Title: package linux-headers-4.8.0-39 (not installed) failed to install/upgrade: impossible d'ouvrir « /usr/src/linux- headers-4.8.0-39/include/uapi/drm/via_drm.h.dpkg-new »: Opération non permise Status in linux package in Ubuntu: Invalid Bug description: ubuntu 16.10 ProblemType: Package DistroRelease: Ubuntu 16.10 Package: linux-headers-4.8.0-39 (not installed) ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17 Uname: Linux 4.8.0-39-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: uhuru 2394 F pulseaudio /dev/snd/controlC1: uhuru 2394 F pulseaudio /dev/snd/controlC2: uhuru 2394 F pulseaudio Date: Wed Mar 1 22:32:59 2017 ErrorMessage: impossible d'ouvrir « /usr/src/linux-headers-4.8.0-39/include/uapi/drm/via_drm.h.dpkg-new »: Opération non permise HibernationDevice: RESUME=UUID=96b2f8e3-8186-46c4-8475-124db407e9ba InstallationDate: Installed on 2016-01-27 (402 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp5s8no wireless extensions. MachineType: Dell Inc. Dimension 9100 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-39-generic root=UUID=4c460bad-c68b-438c-aebc-70f7efc5103d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu11 RfKill: SourcePackage: linux Title: package linux-headers-4.8.0-39 (not installed) failed to install/upgrade: impossible d'ouvrir « /usr/src/linux-headers-4.8.0-39/include/uapi/drm/via_drm.h.dpkg-new »: Opération non permise UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0X8582 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd07/07/2006:svnDellInc.:pnDimension9100:pvr:rvnDellInc.:rn0X8582:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Dimension 9100 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752165] Re: TB16 dock freezes X on hotplug when used with external displays
apport information ** Tags added: apport-collected ** Description changed: Precision 5520 with Quadro GPU. Latest Ubuntu 16.04, kernel Linux REDACTED 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux, latest BIOS 1.7.0 released 12/15/2017. If it can be of any help, I can get this tested on an XPS 9560 (GTX 1050) too. Steps to reproduce: 1. Plug in monitors into DP and miniDP on the dock. In my case, DP-to-DVI cables are used, but I doubt that it matters. 2. Ubuntu 16.04 GNOME + nVidia drivers with PRIME. 3. Select nVidia GPU in PRIME settings, reboot if needed. 4. Either boot with the dock connected or connect it after booting into user session. 5. Set up monitors if necessary. At this point everything should be working fine. 6. Disconnect the dock, give it a moment to adjust to the new window layout etc. 7. Re-connect the dock. Within a few seconds laptop screen should freeze and external monitors should remain blank, as if not connected. 8. Disconnect the dock. Within a few seconds laptop screen should unfreeze. There is a small chance that it won't if you repeat this procedure multiple times. Errors in dmesg indicate that i915 driver is somehow involved: [ 328.966128] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 328.967848] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF B idle bit [ 329.048839] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 329.050547] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit The kernel logs are flooded with these between steps 7 and 8 above. This behaviour does not occur when Intel GPU is selected in PRIME settings or when nouveau is used. However, nouveau performance leaves a lot to be desired, particularly with 3D acceleration in Windows 10 VMs. I have tried nvidia_drm.modeset=1 in boot options, but it doesn't make any difference. Other reports that may be related: https://devtalk.nvidia.com/default/topic/989704/linux/plugging-a -docking-station-w-two-monitors-into-a-quadro-m1000m-laptop-crashes- hangs-the-whole-machine/ - same error messages https://www.reddit.com/r/Dell/comments/5nas3t/tb16_dock_with_5510_ubuntulinux/ddzjlu8/?st=je63h7lw=40bf8189 - "Connecting and disconnecting the TB16 sometimes freeze the laptop." - https://www.dell.com/community/Sputnik/TB16-Dock-Linux- - Support/m-p/5109128/highlight/true#M7466 - "Hot-plugging the screen does - not work." + https://www.dell.com/community/Sputnik/TB16-Dock-Linux-Support/m-p/5109128/highlight/true#M7466 - "Hot-plugging the screen does not work." + --- + ApportVersion: 2.20.1-0ubuntu2.15 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: gboiko 2491 F pulseaudio + CurrentDesktop: GNOME + DistroRelease: Ubuntu 16.04 + HibernationDevice: RESUME=UUID=08bba264-8658-442f-995d-6a745925ac6c + InstallationDate: Installed on 2017-10-01 (149 days ago) + InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 04f3:24a1 Elan Microelectronics Corp. + Bus 001 Device 002: ID 8087:0a2b Intel Corp. + Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: Dell Inc. Precision 5520 + NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic root=/dev/mapper/ubuntu--gnome--vg-root ro ipv6.disable=1 net.ifnames=0 biosdevname=0 nvidia_drm.modeset=1 quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 + RelatedPackageVersions: + linux-restricted-modules-4.13.0-36-generic N/A + linux-backports-modules-4.13.0-36-generic N/A + linux-firmware 1.170 + Tags: xenial + Uname: Linux 4.13.0-36-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 12/15/2017 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.7.0 + dmi.board.name: 0R6JFH + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 10 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/15/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr: + dmi.product.family: Precision + dmi.product.name: Precision 5520 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1752165/+attachment/5065220/+files/AlsaInfo.txt -- You received this bug notification
[Kernel-packages] [Bug 1752165] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1752165/+attachment/5065224/+files/JournalErrors.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/1752165 Title: TB16 dock freezes X on hotplug when used with external displays Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: Precision 5520 with Quadro GPU. Latest Ubuntu 16.04, kernel Linux REDACTED 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux, latest BIOS 1.7.0 released 12/15/2017. If it can be of any help, I can get this tested on an XPS 9560 (GTX 1050) too. Steps to reproduce: 1. Plug in monitors into DP and miniDP on the dock. In my case, DP-to-DVI cables are used, but I doubt that it matters. 2. Ubuntu 16.04 GNOME + nVidia drivers with PRIME. 3. Select nVidia GPU in PRIME settings, reboot if needed. 4. Either boot with the dock connected or connect it after booting into user session. 5. Set up monitors if necessary. At this point everything should be working fine. 6. Disconnect the dock, give it a moment to adjust to the new window layout etc. 7. Re-connect the dock. Within a few seconds laptop screen should freeze and external monitors should remain blank, as if not connected. 8. Disconnect the dock. Within a few seconds laptop screen should unfreeze. There is a small chance that it won't if you repeat this procedure multiple times. Errors in dmesg indicate that i915 driver is somehow involved: [ 328.966128] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 328.967848] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF B idle bit [ 329.048839] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 329.050547] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit The kernel logs are flooded with these between steps 7 and 8 above. This behaviour does not occur when Intel GPU is selected in PRIME settings or when nouveau is used. However, nouveau performance leaves a lot to be desired, particularly with 3D acceleration in Windows 10 VMs. I have tried nvidia_drm.modeset=1 in boot options, but it doesn't make any difference. Other reports that may be related: https://devtalk.nvidia.com/default/topic/989704/linux/plugging-a -docking-station-w-two-monitors-into-a-quadro-m1000m-laptop-crashes- hangs-the-whole-machine/ - same error messages https://www.reddit.com/r/Dell/comments/5nas3t/tb16_dock_with_5510_ubuntulinux/ddzjlu8/?st=je63h7lw=40bf8189 - "Connecting and disconnecting the TB16 sometimes freeze the laptop." https://www.dell.com/community/Sputnik/TB16-Dock-Linux-Support/m-p/5109128/highlight/true#M7466 - "Hot-plugging the screen does not work." --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gboiko 2491 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=08bba264-8658-442f-995d-6a745925ac6c InstallationDate: Installed on 2017-10-01 (149 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:24a1 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5520 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic root=/dev/mapper/ubuntu--gnome--vg-root ro ipv6.disable=1 net.ifnames=0 biosdevname=0 nvidia_drm.modeset=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-36-generic N/A linux-backports-modules-4.13.0-36-generic N/A linux-firmware 1.170 Tags: xenial Uname: Linux 4.13.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/15/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0R6JFH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/15/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:
[Kernel-packages] [Bug 1752165] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1752165/+attachment/5065222/+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/1752165 Title: TB16 dock freezes X on hotplug when used with external displays Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: Precision 5520 with Quadro GPU. Latest Ubuntu 16.04, kernel Linux REDACTED 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux, latest BIOS 1.7.0 released 12/15/2017. If it can be of any help, I can get this tested on an XPS 9560 (GTX 1050) too. Steps to reproduce: 1. Plug in monitors into DP and miniDP on the dock. In my case, DP-to-DVI cables are used, but I doubt that it matters. 2. Ubuntu 16.04 GNOME + nVidia drivers with PRIME. 3. Select nVidia GPU in PRIME settings, reboot if needed. 4. Either boot with the dock connected or connect it after booting into user session. 5. Set up monitors if necessary. At this point everything should be working fine. 6. Disconnect the dock, give it a moment to adjust to the new window layout etc. 7. Re-connect the dock. Within a few seconds laptop screen should freeze and external monitors should remain blank, as if not connected. 8. Disconnect the dock. Within a few seconds laptop screen should unfreeze. There is a small chance that it won't if you repeat this procedure multiple times. Errors in dmesg indicate that i915 driver is somehow involved: [ 328.966128] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 328.967848] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF B idle bit [ 329.048839] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 329.050547] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit The kernel logs are flooded with these between steps 7 and 8 above. This behaviour does not occur when Intel GPU is selected in PRIME settings or when nouveau is used. However, nouveau performance leaves a lot to be desired, particularly with 3D acceleration in Windows 10 VMs. I have tried nvidia_drm.modeset=1 in boot options, but it doesn't make any difference. Other reports that may be related: https://devtalk.nvidia.com/default/topic/989704/linux/plugging-a -docking-station-w-two-monitors-into-a-quadro-m1000m-laptop-crashes- hangs-the-whole-machine/ - same error messages https://www.reddit.com/r/Dell/comments/5nas3t/tb16_dock_with_5510_ubuntulinux/ddzjlu8/?st=je63h7lw=40bf8189 - "Connecting and disconnecting the TB16 sometimes freeze the laptop." https://www.dell.com/community/Sputnik/TB16-Dock-Linux-Support/m-p/5109128/highlight/true#M7466 - "Hot-plugging the screen does not work." --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gboiko 2491 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=08bba264-8658-442f-995d-6a745925ac6c InstallationDate: Installed on 2017-10-01 (149 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:24a1 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5520 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic root=/dev/mapper/ubuntu--gnome--vg-root ro ipv6.disable=1 net.ifnames=0 biosdevname=0 nvidia_drm.modeset=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-36-generic N/A linux-backports-modules-4.13.0-36-generic N/A linux-firmware 1.170 Tags: xenial Uname: Linux 4.13.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/15/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0R6JFH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/15/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:
[Kernel-packages] [Bug 1752165] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1752165/+attachment/5065229/+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/1752165 Title: TB16 dock freezes X on hotplug when used with external displays Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: Precision 5520 with Quadro GPU. Latest Ubuntu 16.04, kernel Linux REDACTED 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux, latest BIOS 1.7.0 released 12/15/2017. If it can be of any help, I can get this tested on an XPS 9560 (GTX 1050) too. Steps to reproduce: 1. Plug in monitors into DP and miniDP on the dock. In my case, DP-to-DVI cables are used, but I doubt that it matters. 2. Ubuntu 16.04 GNOME + nVidia drivers with PRIME. 3. Select nVidia GPU in PRIME settings, reboot if needed. 4. Either boot with the dock connected or connect it after booting into user session. 5. Set up monitors if necessary. At this point everything should be working fine. 6. Disconnect the dock, give it a moment to adjust to the new window layout etc. 7. Re-connect the dock. Within a few seconds laptop screen should freeze and external monitors should remain blank, as if not connected. 8. Disconnect the dock. Within a few seconds laptop screen should unfreeze. There is a small chance that it won't if you repeat this procedure multiple times. Errors in dmesg indicate that i915 driver is somehow involved: [ 328.966128] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 328.967848] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF B idle bit [ 329.048839] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 329.050547] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit The kernel logs are flooded with these between steps 7 and 8 above. This behaviour does not occur when Intel GPU is selected in PRIME settings or when nouveau is used. However, nouveau performance leaves a lot to be desired, particularly with 3D acceleration in Windows 10 VMs. I have tried nvidia_drm.modeset=1 in boot options, but it doesn't make any difference. Other reports that may be related: https://devtalk.nvidia.com/default/topic/989704/linux/plugging-a -docking-station-w-two-monitors-into-a-quadro-m1000m-laptop-crashes- hangs-the-whole-machine/ - same error messages https://www.reddit.com/r/Dell/comments/5nas3t/tb16_dock_with_5510_ubuntulinux/ddzjlu8/?st=je63h7lw=40bf8189 - "Connecting and disconnecting the TB16 sometimes freeze the laptop." https://www.dell.com/community/Sputnik/TB16-Dock-Linux-Support/m-p/5109128/highlight/true#M7466 - "Hot-plugging the screen does not work." --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gboiko 2491 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=08bba264-8658-442f-995d-6a745925ac6c InstallationDate: Installed on 2017-10-01 (149 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:24a1 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5520 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic root=/dev/mapper/ubuntu--gnome--vg-root ro ipv6.disable=1 net.ifnames=0 biosdevname=0 nvidia_drm.modeset=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-36-generic N/A linux-backports-modules-4.13.0-36-generic N/A linux-firmware 1.170 Tags: xenial Uname: Linux 4.13.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/15/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0R6JFH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/15/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:
[Kernel-packages] [Bug 1752165] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1752165/+attachment/5065227/+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/1752165 Title: TB16 dock freezes X on hotplug when used with external displays Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: Precision 5520 with Quadro GPU. Latest Ubuntu 16.04, kernel Linux REDACTED 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux, latest BIOS 1.7.0 released 12/15/2017. If it can be of any help, I can get this tested on an XPS 9560 (GTX 1050) too. Steps to reproduce: 1. Plug in monitors into DP and miniDP on the dock. In my case, DP-to-DVI cables are used, but I doubt that it matters. 2. Ubuntu 16.04 GNOME + nVidia drivers with PRIME. 3. Select nVidia GPU in PRIME settings, reboot if needed. 4. Either boot with the dock connected or connect it after booting into user session. 5. Set up monitors if necessary. At this point everything should be working fine. 6. Disconnect the dock, give it a moment to adjust to the new window layout etc. 7. Re-connect the dock. Within a few seconds laptop screen should freeze and external monitors should remain blank, as if not connected. 8. Disconnect the dock. Within a few seconds laptop screen should unfreeze. There is a small chance that it won't if you repeat this procedure multiple times. Errors in dmesg indicate that i915 driver is somehow involved: [ 328.966128] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 328.967848] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF B idle bit [ 329.048839] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 329.050547] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit The kernel logs are flooded with these between steps 7 and 8 above. This behaviour does not occur when Intel GPU is selected in PRIME settings or when nouveau is used. However, nouveau performance leaves a lot to be desired, particularly with 3D acceleration in Windows 10 VMs. I have tried nvidia_drm.modeset=1 in boot options, but it doesn't make any difference. Other reports that may be related: https://devtalk.nvidia.com/default/topic/989704/linux/plugging-a -docking-station-w-two-monitors-into-a-quadro-m1000m-laptop-crashes- hangs-the-whole-machine/ - same error messages https://www.reddit.com/r/Dell/comments/5nas3t/tb16_dock_with_5510_ubuntulinux/ddzjlu8/?st=je63h7lw=40bf8189 - "Connecting and disconnecting the TB16 sometimes freeze the laptop." https://www.dell.com/community/Sputnik/TB16-Dock-Linux-Support/m-p/5109128/highlight/true#M7466 - "Hot-plugging the screen does not work." --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gboiko 2491 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=08bba264-8658-442f-995d-6a745925ac6c InstallationDate: Installed on 2017-10-01 (149 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:24a1 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5520 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic root=/dev/mapper/ubuntu--gnome--vg-root ro ipv6.disable=1 net.ifnames=0 biosdevname=0 nvidia_drm.modeset=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-36-generic N/A linux-backports-modules-4.13.0-36-generic N/A linux-firmware 1.170 Tags: xenial Uname: Linux 4.13.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/15/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0R6JFH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/15/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:
[Kernel-packages] [Bug 1752165] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1752165/+attachment/5065233/+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/1752165 Title: TB16 dock freezes X on hotplug when used with external displays Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: Precision 5520 with Quadro GPU. Latest Ubuntu 16.04, kernel Linux REDACTED 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux, latest BIOS 1.7.0 released 12/15/2017. If it can be of any help, I can get this tested on an XPS 9560 (GTX 1050) too. Steps to reproduce: 1. Plug in monitors into DP and miniDP on the dock. In my case, DP-to-DVI cables are used, but I doubt that it matters. 2. Ubuntu 16.04 GNOME + nVidia drivers with PRIME. 3. Select nVidia GPU in PRIME settings, reboot if needed. 4. Either boot with the dock connected or connect it after booting into user session. 5. Set up monitors if necessary. At this point everything should be working fine. 6. Disconnect the dock, give it a moment to adjust to the new window layout etc. 7. Re-connect the dock. Within a few seconds laptop screen should freeze and external monitors should remain blank, as if not connected. 8. Disconnect the dock. Within a few seconds laptop screen should unfreeze. There is a small chance that it won't if you repeat this procedure multiple times. Errors in dmesg indicate that i915 driver is somehow involved: [ 328.966128] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 328.967848] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF B idle bit [ 329.048839] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 329.050547] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit The kernel logs are flooded with these between steps 7 and 8 above. This behaviour does not occur when Intel GPU is selected in PRIME settings or when nouveau is used. However, nouveau performance leaves a lot to be desired, particularly with 3D acceleration in Windows 10 VMs. I have tried nvidia_drm.modeset=1 in boot options, but it doesn't make any difference. Other reports that may be related: https://devtalk.nvidia.com/default/topic/989704/linux/plugging-a -docking-station-w-two-monitors-into-a-quadro-m1000m-laptop-crashes- hangs-the-whole-machine/ - same error messages https://www.reddit.com/r/Dell/comments/5nas3t/tb16_dock_with_5510_ubuntulinux/ddzjlu8/?st=je63h7lw=40bf8189 - "Connecting and disconnecting the TB16 sometimes freeze the laptop." https://www.dell.com/community/Sputnik/TB16-Dock-Linux-Support/m-p/5109128/highlight/true#M7466 - "Hot-plugging the screen does not work." --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gboiko 2491 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=08bba264-8658-442f-995d-6a745925ac6c InstallationDate: Installed on 2017-10-01 (149 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:24a1 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5520 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic root=/dev/mapper/ubuntu--gnome--vg-root ro ipv6.disable=1 net.ifnames=0 biosdevname=0 nvidia_drm.modeset=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-36-generic N/A linux-backports-modules-4.13.0-36-generic N/A linux-firmware 1.170 Tags: xenial Uname: Linux 4.13.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/15/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0R6JFH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/15/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision
[Kernel-packages] [Bug 1752165] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1752165/+attachment/5065226/+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/1752165 Title: TB16 dock freezes X on hotplug when used with external displays Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: Precision 5520 with Quadro GPU. Latest Ubuntu 16.04, kernel Linux REDACTED 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux, latest BIOS 1.7.0 released 12/15/2017. If it can be of any help, I can get this tested on an XPS 9560 (GTX 1050) too. Steps to reproduce: 1. Plug in monitors into DP and miniDP on the dock. In my case, DP-to-DVI cables are used, but I doubt that it matters. 2. Ubuntu 16.04 GNOME + nVidia drivers with PRIME. 3. Select nVidia GPU in PRIME settings, reboot if needed. 4. Either boot with the dock connected or connect it after booting into user session. 5. Set up monitors if necessary. At this point everything should be working fine. 6. Disconnect the dock, give it a moment to adjust to the new window layout etc. 7. Re-connect the dock. Within a few seconds laptop screen should freeze and external monitors should remain blank, as if not connected. 8. Disconnect the dock. Within a few seconds laptop screen should unfreeze. There is a small chance that it won't if you repeat this procedure multiple times. Errors in dmesg indicate that i915 driver is somehow involved: [ 328.966128] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 328.967848] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF B idle bit [ 329.048839] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 329.050547] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit The kernel logs are flooded with these between steps 7 and 8 above. This behaviour does not occur when Intel GPU is selected in PRIME settings or when nouveau is used. However, nouveau performance leaves a lot to be desired, particularly with 3D acceleration in Windows 10 VMs. I have tried nvidia_drm.modeset=1 in boot options, but it doesn't make any difference. Other reports that may be related: https://devtalk.nvidia.com/default/topic/989704/linux/plugging-a -docking-station-w-two-monitors-into-a-quadro-m1000m-laptop-crashes- hangs-the-whole-machine/ - same error messages https://www.reddit.com/r/Dell/comments/5nas3t/tb16_dock_with_5510_ubuntulinux/ddzjlu8/?st=je63h7lw=40bf8189 - "Connecting and disconnecting the TB16 sometimes freeze the laptop." https://www.dell.com/community/Sputnik/TB16-Dock-Linux-Support/m-p/5109128/highlight/true#M7466 - "Hot-plugging the screen does not work." --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gboiko 2491 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=08bba264-8658-442f-995d-6a745925ac6c InstallationDate: Installed on 2017-10-01 (149 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:24a1 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5520 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic root=/dev/mapper/ubuntu--gnome--vg-root ro ipv6.disable=1 net.ifnames=0 biosdevname=0 nvidia_drm.modeset=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-36-generic N/A linux-backports-modules-4.13.0-36-generic N/A linux-firmware 1.170 Tags: xenial Uname: Linux 4.13.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/15/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0R6JFH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/15/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family:
[Kernel-packages] [Bug 1752165] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1752165/+attachment/5065225/+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/1752165 Title: TB16 dock freezes X on hotplug when used with external displays Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: Precision 5520 with Quadro GPU. Latest Ubuntu 16.04, kernel Linux REDACTED 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux, latest BIOS 1.7.0 released 12/15/2017. If it can be of any help, I can get this tested on an XPS 9560 (GTX 1050) too. Steps to reproduce: 1. Plug in monitors into DP and miniDP on the dock. In my case, DP-to-DVI cables are used, but I doubt that it matters. 2. Ubuntu 16.04 GNOME + nVidia drivers with PRIME. 3. Select nVidia GPU in PRIME settings, reboot if needed. 4. Either boot with the dock connected or connect it after booting into user session. 5. Set up monitors if necessary. At this point everything should be working fine. 6. Disconnect the dock, give it a moment to adjust to the new window layout etc. 7. Re-connect the dock. Within a few seconds laptop screen should freeze and external monitors should remain blank, as if not connected. 8. Disconnect the dock. Within a few seconds laptop screen should unfreeze. There is a small chance that it won't if you repeat this procedure multiple times. Errors in dmesg indicate that i915 driver is somehow involved: [ 328.966128] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 328.967848] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF B idle bit [ 329.048839] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 329.050547] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit The kernel logs are flooded with these between steps 7 and 8 above. This behaviour does not occur when Intel GPU is selected in PRIME settings or when nouveau is used. However, nouveau performance leaves a lot to be desired, particularly with 3D acceleration in Windows 10 VMs. I have tried nvidia_drm.modeset=1 in boot options, but it doesn't make any difference. Other reports that may be related: https://devtalk.nvidia.com/default/topic/989704/linux/plugging-a -docking-station-w-two-monitors-into-a-quadro-m1000m-laptop-crashes- hangs-the-whole-machine/ - same error messages https://www.reddit.com/r/Dell/comments/5nas3t/tb16_dock_with_5510_ubuntulinux/ddzjlu8/?st=je63h7lw=40bf8189 - "Connecting and disconnecting the TB16 sometimes freeze the laptop." https://www.dell.com/community/Sputnik/TB16-Dock-Linux-Support/m-p/5109128/highlight/true#M7466 - "Hot-plugging the screen does not work." --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gboiko 2491 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=08bba264-8658-442f-995d-6a745925ac6c InstallationDate: Installed on 2017-10-01 (149 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:24a1 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5520 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic root=/dev/mapper/ubuntu--gnome--vg-root ro ipv6.disable=1 net.ifnames=0 biosdevname=0 nvidia_drm.modeset=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-36-generic N/A linux-backports-modules-4.13.0-36-generic N/A linux-firmware 1.170 Tags: xenial Uname: Linux 4.13.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/15/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0R6JFH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/15/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision
[Kernel-packages] [Bug 1752165] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1752165/+attachment/5065230/+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/1752165 Title: TB16 dock freezes X on hotplug when used with external displays Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: Precision 5520 with Quadro GPU. Latest Ubuntu 16.04, kernel Linux REDACTED 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux, latest BIOS 1.7.0 released 12/15/2017. If it can be of any help, I can get this tested on an XPS 9560 (GTX 1050) too. Steps to reproduce: 1. Plug in monitors into DP and miniDP on the dock. In my case, DP-to-DVI cables are used, but I doubt that it matters. 2. Ubuntu 16.04 GNOME + nVidia drivers with PRIME. 3. Select nVidia GPU in PRIME settings, reboot if needed. 4. Either boot with the dock connected or connect it after booting into user session. 5. Set up monitors if necessary. At this point everything should be working fine. 6. Disconnect the dock, give it a moment to adjust to the new window layout etc. 7. Re-connect the dock. Within a few seconds laptop screen should freeze and external monitors should remain blank, as if not connected. 8. Disconnect the dock. Within a few seconds laptop screen should unfreeze. There is a small chance that it won't if you repeat this procedure multiple times. Errors in dmesg indicate that i915 driver is somehow involved: [ 328.966128] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 328.967848] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF B idle bit [ 329.048839] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 329.050547] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit The kernel logs are flooded with these between steps 7 and 8 above. This behaviour does not occur when Intel GPU is selected in PRIME settings or when nouveau is used. However, nouveau performance leaves a lot to be desired, particularly with 3D acceleration in Windows 10 VMs. I have tried nvidia_drm.modeset=1 in boot options, but it doesn't make any difference. Other reports that may be related: https://devtalk.nvidia.com/default/topic/989704/linux/plugging-a -docking-station-w-two-monitors-into-a-quadro-m1000m-laptop-crashes- hangs-the-whole-machine/ - same error messages https://www.reddit.com/r/Dell/comments/5nas3t/tb16_dock_with_5510_ubuntulinux/ddzjlu8/?st=je63h7lw=40bf8189 - "Connecting and disconnecting the TB16 sometimes freeze the laptop." https://www.dell.com/community/Sputnik/TB16-Dock-Linux-Support/m-p/5109128/highlight/true#M7466 - "Hot-plugging the screen does not work." --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gboiko 2491 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=08bba264-8658-442f-995d-6a745925ac6c InstallationDate: Installed on 2017-10-01 (149 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:24a1 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5520 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic root=/dev/mapper/ubuntu--gnome--vg-root ro ipv6.disable=1 net.ifnames=0 biosdevname=0 nvidia_drm.modeset=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-36-generic N/A linux-backports-modules-4.13.0-36-generic N/A linux-firmware 1.170 Tags: xenial Uname: Linux 4.13.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/15/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0R6JFH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/15/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family:
[Kernel-packages] [Bug 1752165] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1752165/+attachment/5065223/+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/1752165 Title: TB16 dock freezes X on hotplug when used with external displays Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: Precision 5520 with Quadro GPU. Latest Ubuntu 16.04, kernel Linux REDACTED 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux, latest BIOS 1.7.0 released 12/15/2017. If it can be of any help, I can get this tested on an XPS 9560 (GTX 1050) too. Steps to reproduce: 1. Plug in monitors into DP and miniDP on the dock. In my case, DP-to-DVI cables are used, but I doubt that it matters. 2. Ubuntu 16.04 GNOME + nVidia drivers with PRIME. 3. Select nVidia GPU in PRIME settings, reboot if needed. 4. Either boot with the dock connected or connect it after booting into user session. 5. Set up monitors if necessary. At this point everything should be working fine. 6. Disconnect the dock, give it a moment to adjust to the new window layout etc. 7. Re-connect the dock. Within a few seconds laptop screen should freeze and external monitors should remain blank, as if not connected. 8. Disconnect the dock. Within a few seconds laptop screen should unfreeze. There is a small chance that it won't if you repeat this procedure multiple times. Errors in dmesg indicate that i915 driver is somehow involved: [ 328.966128] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 328.967848] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF B idle bit [ 329.048839] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 329.050547] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit The kernel logs are flooded with these between steps 7 and 8 above. This behaviour does not occur when Intel GPU is selected in PRIME settings or when nouveau is used. However, nouveau performance leaves a lot to be desired, particularly with 3D acceleration in Windows 10 VMs. I have tried nvidia_drm.modeset=1 in boot options, but it doesn't make any difference. Other reports that may be related: https://devtalk.nvidia.com/default/topic/989704/linux/plugging-a -docking-station-w-two-monitors-into-a-quadro-m1000m-laptop-crashes- hangs-the-whole-machine/ - same error messages https://www.reddit.com/r/Dell/comments/5nas3t/tb16_dock_with_5510_ubuntulinux/ddzjlu8/?st=je63h7lw=40bf8189 - "Connecting and disconnecting the TB16 sometimes freeze the laptop." https://www.dell.com/community/Sputnik/TB16-Dock-Linux-Support/m-p/5109128/highlight/true#M7466 - "Hot-plugging the screen does not work." --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gboiko 2491 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=08bba264-8658-442f-995d-6a745925ac6c InstallationDate: Installed on 2017-10-01 (149 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:24a1 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5520 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic root=/dev/mapper/ubuntu--gnome--vg-root ro ipv6.disable=1 net.ifnames=0 biosdevname=0 nvidia_drm.modeset=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-36-generic N/A linux-backports-modules-4.13.0-36-generic N/A linux-firmware 1.170 Tags: xenial Uname: Linux 4.13.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/15/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0R6JFH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/15/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family:
[Kernel-packages] [Bug 1752165] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1752165/+attachment/5065221/+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/1752165 Title: TB16 dock freezes X on hotplug when used with external displays Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: Precision 5520 with Quadro GPU. Latest Ubuntu 16.04, kernel Linux REDACTED 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux, latest BIOS 1.7.0 released 12/15/2017. If it can be of any help, I can get this tested on an XPS 9560 (GTX 1050) too. Steps to reproduce: 1. Plug in monitors into DP and miniDP on the dock. In my case, DP-to-DVI cables are used, but I doubt that it matters. 2. Ubuntu 16.04 GNOME + nVidia drivers with PRIME. 3. Select nVidia GPU in PRIME settings, reboot if needed. 4. Either boot with the dock connected or connect it after booting into user session. 5. Set up monitors if necessary. At this point everything should be working fine. 6. Disconnect the dock, give it a moment to adjust to the new window layout etc. 7. Re-connect the dock. Within a few seconds laptop screen should freeze and external monitors should remain blank, as if not connected. 8. Disconnect the dock. Within a few seconds laptop screen should unfreeze. There is a small chance that it won't if you repeat this procedure multiple times. Errors in dmesg indicate that i915 driver is somehow involved: [ 328.966128] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 328.967848] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF B idle bit [ 329.048839] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 329.050547] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit The kernel logs are flooded with these between steps 7 and 8 above. This behaviour does not occur when Intel GPU is selected in PRIME settings or when nouveau is used. However, nouveau performance leaves a lot to be desired, particularly with 3D acceleration in Windows 10 VMs. I have tried nvidia_drm.modeset=1 in boot options, but it doesn't make any difference. Other reports that may be related: https://devtalk.nvidia.com/default/topic/989704/linux/plugging-a -docking-station-w-two-monitors-into-a-quadro-m1000m-laptop-crashes- hangs-the-whole-machine/ - same error messages https://www.reddit.com/r/Dell/comments/5nas3t/tb16_dock_with_5510_ubuntulinux/ddzjlu8/?st=je63h7lw=40bf8189 - "Connecting and disconnecting the TB16 sometimes freeze the laptop." https://www.dell.com/community/Sputnik/TB16-Dock-Linux-Support/m-p/5109128/highlight/true#M7466 - "Hot-plugging the screen does not work." --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gboiko 2491 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=08bba264-8658-442f-995d-6a745925ac6c InstallationDate: Installed on 2017-10-01 (149 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:24a1 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5520 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic root=/dev/mapper/ubuntu--gnome--vg-root ro ipv6.disable=1 net.ifnames=0 biosdevname=0 nvidia_drm.modeset=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-36-generic N/A linux-backports-modules-4.13.0-36-generic N/A linux-firmware 1.170 Tags: xenial Uname: Linux 4.13.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/15/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0R6JFH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/15/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision
[Kernel-packages] [Bug 1577140] Re: Wifi Ralink R3290 disabled by default in ubuntu 16.04
Hi, Writing here as I've recently faced the same issue with rt3290 on Ubuntu 16.04. May I wonder if there are any information right now as last activity here was more than year ago? Have anyone made some progress? /M -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1577140 Title: Wifi Ralink R3290 disabled by default in ubuntu 16.04 Status in linux package in Ubuntu: Confirmed Bug description: I have my personal laptop and it contains PCI Ralink r3290 wifi adaptor with bluetooth and when i have installed the fresh version of Ubuntu 16.04x64 it doesn’t work at all on boot up. The wifi is disabled by default and the it doesn’t activates even by pressing the key and when i go the network settings airplane mode is also enabled and when i try to disable airplane mode it switches back on. I dont know whats going wrong. Earlier my wifi works on ubuntu 15.04. I have tried almost every solution and none works in the latest LTS release. Please help I am unable to use internet in ubuntu ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: boot/vmlinuz-4.4.0-21-generic] ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shankey1536 F pulseaudio /dev/snd/controlC1: shankey1536 F pulseaudio CurrentDesktop: Unity Date: Sun May 1 17:02:12 2016 HibernationDevice: RESUME=UUID=9fdda691-a6ae-4494-99e3-b76fde1f33a6 InstallationDate: Installed on 2016-04-24 (7 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 001 Device 003: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd (Foxlink) Webcam Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard Compaq 15 Notebook PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=609ae58a-a43f-4f7b-9a61-e21d3caf457a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.39 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2211 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.52 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.39:bd05/26/2015:svnHewlett-Packard:pnCompaq15NotebookPC:pvr0991100600087:rvnHewlett-Packard:rn2211:rvr86.52:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: Compaq 15 Notebook PC dmi.product.version: 0991100600087 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577140/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752165] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1752165/+attachment/5065234/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Attachment removed: "WifiSyslog.txt" https://bugs.launchpad.net/dell-sputnik/+bug/1752165/+attachment/5065234/+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/1752165 Title: TB16 dock freezes X on hotplug when used with external displays Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: Precision 5520 with Quadro GPU. Latest Ubuntu 16.04, kernel Linux REDACTED 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux, latest BIOS 1.7.0 released 12/15/2017. If it can be of any help, I can get this tested on an XPS 9560 (GTX 1050) too. Steps to reproduce: 1. Plug in monitors into DP and miniDP on the dock. In my case, DP-to-DVI cables are used, but I doubt that it matters. 2. Ubuntu 16.04 GNOME + nVidia drivers with PRIME. 3. Select nVidia GPU in PRIME settings, reboot if needed. 4. Either boot with the dock connected or connect it after booting into user session. 5. Set up monitors if necessary. At this point everything should be working fine. 6. Disconnect the dock, give it a moment to adjust to the new window layout etc. 7. Re-connect the dock. Within a few seconds laptop screen should freeze and external monitors should remain blank, as if not connected. 8. Disconnect the dock. Within a few seconds laptop screen should unfreeze. There is a small chance that it won't if you repeat this procedure multiple times. Errors in dmesg indicate that i915 driver is somehow involved: [ 328.966128] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 328.967848] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF B idle bit [ 329.048839] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 329.050547] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit The kernel logs are flooded with these between steps 7 and 8 above. This behaviour does not occur when Intel GPU is selected in PRIME settings or when nouveau is used. However, nouveau performance leaves a lot to be desired, particularly with 3D acceleration in Windows 10 VMs. I have tried nvidia_drm.modeset=1 in boot options, but it doesn't make any difference. Other reports that may be related: https://devtalk.nvidia.com/default/topic/989704/linux/plugging-a -docking-station-w-two-monitors-into-a-quadro-m1000m-laptop-crashes- hangs-the-whole-machine/ - same error messages https://www.reddit.com/r/Dell/comments/5nas3t/tb16_dock_with_5510_ubuntulinux/ddzjlu8/?st=je63h7lw=40bf8189 - "Connecting and disconnecting the TB16 sometimes freeze the laptop." https://www.dell.com/community/Sputnik/TB16-Dock-Linux-Support/m-p/5109128/highlight/true#M7466 - "Hot-plugging the screen does not work." --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gboiko 2491 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=08bba264-8658-442f-995d-6a745925ac6c InstallationDate: Installed on 2017-10-01 (149 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:24a1 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5520 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic root=/dev/mapper/ubuntu--gnome--vg-root ro ipv6.disable=1 net.ifnames=0 biosdevname=0 nvidia_drm.modeset=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-36-generic N/A linux-backports-modules-4.13.0-36-generic N/A linux-firmware 1.170 Tags: xenial Uname: Linux 4.13.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/15/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0R6JFH dmi.board.vendor: Dell Inc. dmi.board.version: A00
[Kernel-packages] [Bug 1752165] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1752165/+attachment/5065231/+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/1752165 Title: TB16 dock freezes X on hotplug when used with external displays Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: Precision 5520 with Quadro GPU. Latest Ubuntu 16.04, kernel Linux REDACTED 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux, latest BIOS 1.7.0 released 12/15/2017. If it can be of any help, I can get this tested on an XPS 9560 (GTX 1050) too. Steps to reproduce: 1. Plug in monitors into DP and miniDP on the dock. In my case, DP-to-DVI cables are used, but I doubt that it matters. 2. Ubuntu 16.04 GNOME + nVidia drivers with PRIME. 3. Select nVidia GPU in PRIME settings, reboot if needed. 4. Either boot with the dock connected or connect it after booting into user session. 5. Set up monitors if necessary. At this point everything should be working fine. 6. Disconnect the dock, give it a moment to adjust to the new window layout etc. 7. Re-connect the dock. Within a few seconds laptop screen should freeze and external monitors should remain blank, as if not connected. 8. Disconnect the dock. Within a few seconds laptop screen should unfreeze. There is a small chance that it won't if you repeat this procedure multiple times. Errors in dmesg indicate that i915 driver is somehow involved: [ 328.966128] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 328.967848] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF B idle bit [ 329.048839] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 329.050547] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit The kernel logs are flooded with these between steps 7 and 8 above. This behaviour does not occur when Intel GPU is selected in PRIME settings or when nouveau is used. However, nouveau performance leaves a lot to be desired, particularly with 3D acceleration in Windows 10 VMs. I have tried nvidia_drm.modeset=1 in boot options, but it doesn't make any difference. Other reports that may be related: https://devtalk.nvidia.com/default/topic/989704/linux/plugging-a -docking-station-w-two-monitors-into-a-quadro-m1000m-laptop-crashes- hangs-the-whole-machine/ - same error messages https://www.reddit.com/r/Dell/comments/5nas3t/tb16_dock_with_5510_ubuntulinux/ddzjlu8/?st=je63h7lw=40bf8189 - "Connecting and disconnecting the TB16 sometimes freeze the laptop." https://www.dell.com/community/Sputnik/TB16-Dock-Linux-Support/m-p/5109128/highlight/true#M7466 - "Hot-plugging the screen does not work." --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gboiko 2491 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=08bba264-8658-442f-995d-6a745925ac6c InstallationDate: Installed on 2017-10-01 (149 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:24a1 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5520 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic root=/dev/mapper/ubuntu--gnome--vg-root ro ipv6.disable=1 net.ifnames=0 biosdevname=0 nvidia_drm.modeset=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-36-generic N/A linux-backports-modules-4.13.0-36-generic N/A linux-firmware 1.170 Tags: xenial Uname: Linux 4.13.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/15/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0R6JFH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/15/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family:
[Kernel-packages] [Bug 1752165] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1752165/+attachment/5065228/+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/1752165 Title: TB16 dock freezes X on hotplug when used with external displays Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: Precision 5520 with Quadro GPU. Latest Ubuntu 16.04, kernel Linux REDACTED 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux, latest BIOS 1.7.0 released 12/15/2017. If it can be of any help, I can get this tested on an XPS 9560 (GTX 1050) too. Steps to reproduce: 1. Plug in monitors into DP and miniDP on the dock. In my case, DP-to-DVI cables are used, but I doubt that it matters. 2. Ubuntu 16.04 GNOME + nVidia drivers with PRIME. 3. Select nVidia GPU in PRIME settings, reboot if needed. 4. Either boot with the dock connected or connect it after booting into user session. 5. Set up monitors if necessary. At this point everything should be working fine. 6. Disconnect the dock, give it a moment to adjust to the new window layout etc. 7. Re-connect the dock. Within a few seconds laptop screen should freeze and external monitors should remain blank, as if not connected. 8. Disconnect the dock. Within a few seconds laptop screen should unfreeze. There is a small chance that it won't if you repeat this procedure multiple times. Errors in dmesg indicate that i915 driver is somehow involved: [ 328.966128] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 328.967848] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF B idle bit [ 329.048839] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 329.050547] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit The kernel logs are flooded with these between steps 7 and 8 above. This behaviour does not occur when Intel GPU is selected in PRIME settings or when nouveau is used. However, nouveau performance leaves a lot to be desired, particularly with 3D acceleration in Windows 10 VMs. I have tried nvidia_drm.modeset=1 in boot options, but it doesn't make any difference. Other reports that may be related: https://devtalk.nvidia.com/default/topic/989704/linux/plugging-a -docking-station-w-two-monitors-into-a-quadro-m1000m-laptop-crashes- hangs-the-whole-machine/ - same error messages https://www.reddit.com/r/Dell/comments/5nas3t/tb16_dock_with_5510_ubuntulinux/ddzjlu8/?st=je63h7lw=40bf8189 - "Connecting and disconnecting the TB16 sometimes freeze the laptop." https://www.dell.com/community/Sputnik/TB16-Dock-Linux-Support/m-p/5109128/highlight/true#M7466 - "Hot-plugging the screen does not work." --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gboiko 2491 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=08bba264-8658-442f-995d-6a745925ac6c InstallationDate: Installed on 2017-10-01 (149 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:24a1 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5520 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic root=/dev/mapper/ubuntu--gnome--vg-root ro ipv6.disable=1 net.ifnames=0 biosdevname=0 nvidia_drm.modeset=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-36-generic N/A linux-backports-modules-4.13.0-36-generic N/A linux-firmware 1.170 Tags: xenial Uname: Linux 4.13.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/15/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0R6JFH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/15/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family:
[Kernel-packages] [Bug 1743856] Re: EDAC, sb_edac: Backport 1 patch to Ubuntu 17.10 (Fix missing DIMM sysfs entries with KNL SNC2/SNC4 mode)
I verfied it with the kernel: Linux [*]4 4.13.0-36-generic #40~lp1743856 SMP Tue Feb 27 19:57:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux and the output of the following command: ls -la /sys/devices/system//edac/mc/mc0/dimm seems to be good: dimm0/ dimm1/ dimm2/ dimm3/ dimm4/ dimm5/ Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1743856 Title: EDAC, sb_edac: Backport 1 patch to Ubuntu 17.10 (Fix missing DIMM sysfs entries with KNL SNC2/SNC4 mode) Status in intel: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: In Progress Status in linux source package in Bionic: Fix Released Bug description: The sb_edac needs additional patch to enable EDAC to know of the existence of some DIMMs attached to channels while figuring out the size of the DIMMs and the cluster mode is SNC2 or SNC4. All the thread connected with this issue is described here https://www.spinics.net/lists/linux-edac/msg08170.html. Please backport the following patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=24281a2f4ca569d44e44e4cbc500cf08e7bb4c36 to solve the sb_edac driver issue on Ubuntu 17.10. Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1743856/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752165] Re: TB16 dock freezes X on hotplug when used with external displays
Tested this on XPS 15 9560 (GTX 1050) and it does not have this problem, hotplugging works fine on it. I was using this very setup - just plugged the thunderbolt cable into a different laptop. Exact same drivers and the same linux-firmware package from upstream (1.170) that I have installed for WiFi and Bluetooth reasons. Added the apport logs as requested. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752165 Title: TB16 dock freezes X on hotplug when used with external displays Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: Precision 5520 with Quadro GPU. Latest Ubuntu 16.04, kernel Linux REDACTED 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux, latest BIOS 1.7.0 released 12/15/2017. If it can be of any help, I can get this tested on an XPS 9560 (GTX 1050) too. Steps to reproduce: 1. Plug in monitors into DP and miniDP on the dock. In my case, DP-to-DVI cables are used, but I doubt that it matters. 2. Ubuntu 16.04 GNOME + nVidia drivers with PRIME. 3. Select nVidia GPU in PRIME settings, reboot if needed. 4. Either boot with the dock connected or connect it after booting into user session. 5. Set up monitors if necessary. At this point everything should be working fine. 6. Disconnect the dock, give it a moment to adjust to the new window layout etc. 7. Re-connect the dock. Within a few seconds laptop screen should freeze and external monitors should remain blank, as if not connected. 8. Disconnect the dock. Within a few seconds laptop screen should unfreeze. There is a small chance that it won't if you repeat this procedure multiple times. Errors in dmesg indicate that i915 driver is somehow involved: [ 328.966128] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 328.967848] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF B idle bit [ 329.048839] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 329.050547] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit The kernel logs are flooded with these between steps 7 and 8 above. This behaviour does not occur when Intel GPU is selected in PRIME settings or when nouveau is used. However, nouveau performance leaves a lot to be desired, particularly with 3D acceleration in Windows 10 VMs. I have tried nvidia_drm.modeset=1 in boot options, but it doesn't make any difference. Other reports that may be related: https://devtalk.nvidia.com/default/topic/989704/linux/plugging-a -docking-station-w-two-monitors-into-a-quadro-m1000m-laptop-crashes- hangs-the-whole-machine/ - same error messages https://www.reddit.com/r/Dell/comments/5nas3t/tb16_dock_with_5510_ubuntulinux/ddzjlu8/?st=je63h7lw=40bf8189 - "Connecting and disconnecting the TB16 sometimes freeze the laptop." https://www.dell.com/community/Sputnik/TB16-Dock-Linux-Support/m-p/5109128/highlight/true#M7466 - "Hot-plugging the screen does not work." --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gboiko 2491 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=08bba264-8658-442f-995d-6a745925ac6c InstallationDate: Installed on 2017-10-01 (149 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:24a1 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5520 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic root=/dev/mapper/ubuntu--gnome--vg-root ro ipv6.disable=1 net.ifnames=0 biosdevname=0 nvidia_drm.modeset=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-36-generic N/A linux-backports-modules-4.13.0-36-generic N/A linux-firmware 1.170 Tags: xenial Uname: Linux 4.13.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/15/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0R6JFH dmi.board.vendor: Dell Inc. dmi.board.version: A00
[Kernel-packages] [Bug 1742293] Re: Kernel Upgrade Error
*** This bug is a duplicate of bug 1705345 *** https://bugs.launchpad.net/bugs/1705345 ** This bug has been marked a duplicate of bug 1705345 Installing new kernel hangs on plymouth --ping -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742293 Title: Kernel Upgrade Error Status in linux package in Ubuntu: Incomplete Bug description: Installation frozen on this and even after a dpkg --configure -a: Setting up linux-image-4.13.0-25-generic (4.13.0-25.29) ... Running depmod. update-initramfs: deferring update (hook will be called later) The link /initrd.img is a dangling linkto /boot/initrd.img-4.13.0-25-generic vmlinuz(/boot/vmlinuz-4.13.0-25-generic ) points to /boot/vmlinuz-4.13.0-25-generic (/boot/vmlinuz-4.13.0-25-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-4.13.0-25-generic.postinst line 491. Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.13.0-25-generic /boot/vmlinuz-4.13.0-25-generic run-parts: executing /etc/kernel/postinst.d/dkms 4.13.0-25-generic /boot/vmlinuz-4.13.0-25-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1747563] Re: Ubuntu18.04[P9, Boston]: while booting system with disable_radix as kernel boot parameter continuous cpu warn on seen in console
** Changed in: linux (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: ubuntu-power-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1747563 Title: Ubuntu18.04[P9, Boston]: while booting system with disable_radix as kernel boot parameter continuous cpu warn on seen in console Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: == Comment: #0 - Praveen K. Pandey- 2018-01-16 02:38:52 == Problem Description : while booting Power9 Boston as ubuntu18.04 system with disable_radix as kernel boot parameter continuous cpu warn on seen in console Steps to reproduce: 1- install P9 system with ubuntu 18.04 2- boot system with disable_radix as kernel boot parameter LOG: 0 [ 47.953357] [c00febc3be30] [c000b4e8] ret_from_kernel_thread+0x5c/0x74 [ 47.953358] Instruction dump: [ 47.953358] eae3 4191fad0 7ed3b378 e9210030 7efbbb78 7c791b78 3b40 e953 [ 47.953360] 7d3f4850 7f7b5214 7fa9d840 409cfbc4 <0fe0> 3ae0 4bfffcd4 7c0004ac [ 47.953363] ---[ end trace 69b8c2ab7570cdbf ]--- [ 47.953561] [ cut here ] [ 47.953562] WARNING: CPU: 23 PID: 995 at /build/linux-268tGw/linux-4.13.0/mm/vmalloc.c:2521 pcpu_get_vm_areas+0x62c/0x660 [ 47.953563] Modules linked in: hid_generic crc32c_vpmsum ast i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm usbhid hid aac raid i40e(+) [ 47.953567] CPU: 23 PID: 995 Comm: kworker/23:1 Tainted: GW 4.13.0-25-generic #29-Ubuntu [ 47.953569] Workqueue: events pcpu_balance_workfn [ 47.953570] task: c00febb97000 task.stack: c00febc38000 [ 47.953570] NIP: c032fedc LR: c02f9c54 CTR: [ 47.953571] REGS: c00febc3b800 TRAP: 0700 Tainted: GW (4.13.0-25-generic) [ 47.953571] MSR: 92029033 [ 47.953574] CR: 24024828 XER: 2004 [ 47.953574] CFAR: c032fa98 SOFTE: 1 [ 47.953574] GPR00: 21e0 c00febc3ba80 c15f6200 c000200fff6da480 [ 47.953574] GPR04: c000200fff356c08 0008 c000200fff6da488 [ 47.953574] GPR08: 21e0 0800 0140 c000200fff6da488 [ 47.953574] GPR12: 0002 cfacf180 c0f7dbe0 c00febc3bbb0 [ 47.953574] GPR16: 0010 c18adff8 c000200fff356c08 [ 47.953574] GPR20: 2320 c000200fff356bf8 c000200fff356c00 [ 47.953574] GPR24: c000200fff6da488 0001 2320 [ 47.953574] GPR28: 0002 000f d800 d000 [ [ 47.960515] GPR00: 21e0 c00febc5ba80 c15f6200 c000200fff6da480 [ 47.960515] GPR04: c000200fff356c08 0008 c000200fff6da488 [ 47.960515] GPR08: 21e0 0800 0140 c000200fff6da488 [ 47.960515] GPR12: 0002 cfacdc80 c0f7dbe0 c00febc5bbb0 [ 47.960515] GPR16: 0010 c18adff8 c000200fff356c08 [ 47.960515] GPR20: 2320 c000200fff356bf8 c000200fff356c00 [ 47.960515] GPR24: c000200fff6da488 0001 2320 [ 47.960515] GPR28: 0002 000f d800 d000 [ 47.960527] NIP [c032fedc] pcpu_get_vm_areas+0x62c/0x660 [ 47.960528] LR [c02f9c54] pcpu_create_chunk+0xb4/0x1b0 [ 47.960528] Call Trace: [ 47.960529] [c00febc5ba80] [c00febc5bac0] 0xc00febc5bac0 (unreliable) [ 47.960531] [c00febc5bb50] [c02f9c54] pcpu_create_chunk+0xb4/0x1b0 [ 47.960532] [c00febc5bb90] [c02fb510] pcpu_balance_workfn+0x600/0x960 [ 47.960534] [c00febc5bc90] [c0124018] process_one_work+0x298/0x5a0 [ 47.960536] [c00febc5bd20] [c01243a8] worker_thread+0x88/0x620 [ 47.960537] [c00febc5bdc0] [c012d21c] kthread+0x1ac/0x1c0 [ 47.960539] [c00febc5be30] [c000b4e8] ret_from_kernel_thread+0x5c/0x74 [ 47.960539] Instruction dump: [ 47.960540] eae3 4191fad0 7ed3b378 e9210030 7efbbb78 7c791b78 3b40 e953 [ 47.960542] 7d3f4850 7f7b5214 7fa9d840 409cfbc4 <0fe0> 3ae0 4bfffcd4 7c0004ac [ 47.960545] ---[ end trace 69b8c2ab7570ce02 ]--- [ 47.960554] [ cut here ] [ 47.960556] WARNING: CPU: 21 PID:
[Kernel-packages] [Bug 1745266] Re: Xenial update to 4.4.112 stable release
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1745266 Title: Xenial update to 4.4.112 stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.112 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.112 stable release shall be applied: * dm bufio: fix shrinker scans when (nr_to_scan < retain_target) * KVM: Fix stack-out-of-bounds read in write_mmio * can: gs_usb: fix return value of the "set_bittiming" callback * IB/srpt: Disable RDMA access by the initiator * MIPS: Validate PR_SET_FP_MODE prctl(2) requests against the ABI of the task * MIPS: Factor out NT_PRFPREG regset access helpers * MIPS: Guard against any partial write attempt with PTRACE_SETREGSET * MIPS: Consistently handle buffer counter with PTRACE_SETREGSET * MIPS: Fix an FCSR access API regression with NT_PRFPREG and MSA * MIPS: Also verify sizeof `elf_fpreg_t' with PTRACE_SETREGSET * MIPS: Disallow outsized PTRACE_SETREGSET NT_PRFPREG regset accesses * net/mac80211/debugfs.c: prevent build failure with CONFIG_UBSAN=y * kvm: vmx: Scrub hardware GPRs at VM-exit * x86/vsdo: Fix build on PARAVIRT_CLOCK=y, KVM_GUEST=n * x86/acpi: Handle SCI interrupts above legacy space gracefully * iommu/arm-smmu-v3: Don't free page table ops twice * ALSA: pcm: Remove incorrect snd_BUG_ON() usages * ALSA: pcm: Add missing error checks in OSS emulation plugin builder * ALSA: pcm: Abort properly at pending signal in OSS read/write loops * ALSA: pcm: Allow aborting mutex lock at OSS read/write loops * ALSA: aloop: Release cable upon open error path * ALSA: aloop: Fix inconsistent format due to incomplete rule * ALSA: aloop: Fix racy hw constraints adjustment * x86/acpi: Reduce code duplication in mp_override_legacy_irq() * mm/compaction: fix invalid free_pfn and compact_cached_free_pfn * mm/compaction: pass only pageblock aligned range to pageblock_pfn_to_page * mm/page-writeback: fix dirty_ratelimit calculation * mm/zswap: use workqueue to destroy pool * zswap: don't param_set_charp while holding spinlock * locks: don't check for race with close when setting OFD lock * futex: Replace barrier() in unqueue_me() with READ_ONCE() * locking/mutex: Allow next waiter lockless wakeup * usbvision fix overflow of interfaces array * usb: musb: ux500: Fix NULL pointer dereference at system PM * r8152: fix the wake event * r8152: use test_and_clear_bit * r8152: adjust ALDPS function * lan78xx: use skb_cow_head() to deal with cloned skbs * sr9700: use skb_cow_head() to deal with cloned skbs * smsc75xx: use skb_cow_head() to deal with cloned skbs * cx82310_eth: use skb_cow_head() to deal with cloned skbs * x86/mm/pat, /dev/mem: Remove superfluous error message * hwrng: core - sleep interruptible in read * sysrq: Fix warning in sysrq generated crash. * xhci: Fix ring leak in failure path of xhci_alloc_virt_device() * Revert "userfaultfd: selftest: vm: allow to build in vm/ directory" * x86/pti/efi: broken conversion from efi to kernel page table * 8021q: fix a memory leak for VLAN 0 device * ip6_tunnel: disable dst caching if tunnel is dual-stack * net: core: fix module type in sock_diag_bind * RDS: Heap OOB write in rds_message_alloc_sgs() * RDS: null pointer dereference in rds_atomic_free_op * sh_eth: fix TSU resource handling * sh_eth: fix SH7757 GEther initialization * net: stmmac: enable EEE in MII, GMII or RGMII only * ipv6: fix possible mem leaks in ipv6_make_skb() * crypto: algapi - fix NULL dereference in crypto_remove_spawns() * rbd: set max_segments to USHRT_MAX * x86/microcode/intel: Extend BDW late-loading with a revision check * KVM: x86: Add memory barrier on vmcs field lookup * drm/vmwgfx: Potential off by one in vmw_view_add() * kaiser: Set _PAGE_NX only if supported * bpf: add bpf_patch_insn_single helper * bpf: don't (ab)use instructions to store state * bpf: move fixup_bpf_calls() function * bpf: refactor fixup_bpf_calls() * bpf: adjust insn_aux_data when patching insns * bpf: prevent out-of-bounds
[Kernel-packages] [Bug 1752336] 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/1752336 Title: BUG: Bad page map in process CompositorTileW pte:94aadfb0 pmd:943ae067 Status in linux package in Ubuntu: Confirmed Bug description: This just happened ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm3937 F pulseaudio fabio 4501 F pulseaudio /dev/snd/controlC0: gdm3937 F pulseaudio fabio 4501 F pulseaudio Date: Wed Feb 28 16:18:53 2018 Failure: oops HibernationDevice: RESUME=UUID=f6770099-4a42-48e3-b4ab-588190b2a701 InstallationDate: Installed on 2017-08-21 (191 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 008: ID 13d3:3408 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=3eab3ace-7b67-4e6a-aea7-d31b73cc4819 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: BUG: Bad page map in process CompositorTileW pte:94aadfb0 pmd:943ae067 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JK 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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X550JK 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/1752336/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752163] Re: computer freeze
So just finished getting in new kernel, might take a while before the bug comes back as I sometime had uptime for almost 24hours, will let you know :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752163 Title: computer freeze Status in linux package in Ubuntu: Incomplete Bug description: Computer randomly freeze, not possible to do anything than reboot the system. Did alot of installs on the same day, not sure what is the cause. Running script to not have gpu installed, should not be a problem? am4 cpu with no apu. Description: Ubuntu 17.10 Release: 17.10 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-36-generic 4.13.0-36.40 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: prozac 2113 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Feb 27 21:22:31 2018 InstallationDate: Installed on 2018-02-16 (11 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) IwConfig: lono wireless extensions. enp38s0 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic.efi.signed root=UUID=779380b7-d22a-4038-a9a4-cdf71b00b881 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-36-generic N/A linux-backports-modules-4.13.0-36-generic N/A linux-firmware 1.169.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0612 dmi.board.asset.tag: Default string dmi.board.name: PRIME X370-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0612:bd05/15/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX370-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752163/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752310] [NEW] What is the zfs support policy wrt. LTS releases?
Public bug reported: If we consider the zfs 0.x releases as being major (0.6, 0.7, 0.8), is the assumption correct that LTS releases will not receive a new major ZFS release ? To be as practical as possible: Bionic will be stuck at zfs 0.7.x, Xenial at zfs 0.6.x ? If my assumption is wrong, when would Xenial see zfs 0.7 ? Has a policy been defined ? ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1752310 Title: What is the zfs support policy wrt. LTS releases? Status in zfs-linux package in Ubuntu: New Bug description: If we consider the zfs 0.x releases as being major (0.6, 0.7, 0.8), is the assumption correct that LTS releases will not receive a new major ZFS release ? To be as practical as possible: Bionic will be stuck at zfs 0.7.x, Xenial at zfs 0.6.x ? If my assumption is wrong, when would Xenial see zfs 0.7 ? Has a policy been defined ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1752310/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1413440] Re: USB stops working after a while (xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command)
I am having the same problem, but only after resume from suspend or hibernate. I first thought it was a bluetooth problem, as my bluetooth mouse stops working after a minute or so after resume. However, both the bluetooth adapter is gone (bluetoothctl says "No Default controller"), but also ordinary USB mice will not work. It seems that HCI dies, and the kernel decides to remove everything else as well. Touchpad works however. I am running 18.04 alpha with 4.16rc3 (4.16.0-041600rc3-generic) mainline kernel. Hardware: Lenovo Thinkpad E580. Full syslog output. BTW: "MX Anywhere 2" is a BT mouse, not a keyboard. Not sure why it is registered as such. Feb 28 14:18:00 miCycle bluetoothd[1040]: Unable to register org.bluez.Battery1 interface for /org/bluez/hci0/dev_E8_02_AE_59_01_F8 Feb 28 14:18:01 miCycle kernel: [13423.017919] input: MX Anywhere 2 as /devices/virtual/misc/uhid/0005:046D:B018.0002/input/input19 Feb 28 14:18:01 miCycle kernel: [13423.018374] hid-generic 0005:046D:B018.0002: input,hidraw0: BLUETOOTH HID v0.09 Keyboard [MX Anywhere 2] on A0:D3:7A:E0:62:A2 Feb 28 14:18:01 miCycle upowerd[1731]: unhandled action 'bind' on /sys/devices/virtual/misc/uhid/0005:046D:B018.0002 Feb 28 14:18:15 miCycle blueman-mechanism: Exiting Feb 28 14:18:42 miCycle kernel: [13464.682662] xhci_hcd :00:14.0: xHC is not running. Feb 28 14:18:42 miCycle kernel: [13464.724396] xhci_hcd :00:14.0: xHCI host controller not responding, assume dead Feb 28 14:18:42 miCycle kernel: [13464.724414] xhci_hcd :00:14.0: HC died; cleaning up Feb 28 14:18:42 miCycle kernel: [13464.746152] usb 1-5: USB disconnect, device number 4 Feb 28 14:18:42 miCycle kernel: [13464.801790] usb 1-6: USB disconnect, device number 3 Feb 28 14:18:42 miCycle systemd[1]: bluetooth.target: Unit not needed anymore. Stopping. Feb 28 14:18:42 miCycle systemd[1]: Stopped target Bluetooth. Feb 28 14:18:42 miCycle upowerd[1731]: unhandled action 'unbind' on /sys/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.1 Feb 28 14:18:42 miCycle upowerd[1731]: unhandled action 'unbind' on /sys/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0 Feb 28 14:18:42 miCycle upowerd[1731]: unhandled action 'unbind' on /sys/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.1 Feb 28 14:18:42 miCycle upowerd[1731]: unhandled action 'unbind' on /sys/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0 Feb 28 14:18:42 miCycle upowerd[1731]: unhandled action 'unbind' on /sys/devices/pci:00/:00:14.0/usb1/1-5 Feb 28 14:18:42 miCycle upowerd[1731]: unhandled action 'unbind' on /sys/devices/pci:00/:00:14.0/usb1/1-6 Feb 28 14:18:42 miCycle acpid: input device has been disconnected, fd 19 Feb 28 14:18:42 miCycle bluetoothd[1040]: Endpoint unregistered: sender=:1.52 path=/MediaEndpoint/A2DPSource Feb 28 14:18:42 miCycle bluetoothd[1040]: Endpoint unregistered: sender=:1.52 path=/MediaEndpoint/A2DPSink Feb 28 14:18:42 miCycle upowerd[1731]: unhandled action 'unbind' on /sys/devices/virtual/misc/uhid/0005:046D:B018.0002 Feb 28 14:18:42 miCycle NetworkManager[879]: [1519823922.9176] bluez5: NAP: removed interface A0:D3:7A:E0:62:A2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1413440 Title: USB stops working after a while (xhci_hcd :00:14.0: Timeout while waiting for setup device command) Status in System76: Triaged Status in linux package in Ubuntu: Triaged Bug description: On my laptop the kernel will sometimes drop the USB hub. After this, the laptop doesn't recognise any device plugged in to the USB ports - plugging and unplugging any device I've tried into any of the USB ports produces no response, not even dmesg entries. Strangely this also applies to bluetooth - it no longer works once USB has dropped (possibly the module is hung of the bus internally). Once this has happened only a reboot fixes it; I've not managed to find any combination of module unload/reload or suspend cycles to reinitialise things correctly. Relevant snippet of dmesg: [48830.625057] xhci_hcd :00:14.0: Timeout while waiting for setup device command [48838.079718] xhci_hcd :00:14.0: Stopped the command ring failed, maybe the host is dead [48838.079742] xhci_hcd :00:14.0: Abort command ring failed [48838.079746] xhci_hcd :00:14.0: HC died; cleaning up [48838.079770] xhci_hcd :00:14.0: Timeout while waiting for setup device command [48838.079806] sched: RT throttling activated [48838.079981] usb 1-1: USB disconnect, device number 16 [48838.079985] usb 1-1.2: USB disconnect, device number 18 [48838.079987] usb 1-1.2.3: USB disconnect, device number 19 [48838.080285] usb 1-1.2.4: USB disconnect, device number 20 [48838.111892] usb 1-1.4: USB disconnect, device number 17 [48838.191292] usb 1-4: USB disconnect, device number 6 [48838.267550] usb 1-10: USB disconnect, device number 8
[Kernel-packages] [Bug 1752317] [NEW] Bionic update to v4.15.7 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 v4.15.7 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the v4.15.7 stable release shall be applied: netfilter: drop outermost socket lock in getsockopt() arm64: mm: don't write garbage into TTBR1_EL1 register kconfig.h: Include compiler types to avoid missed struct attributes MIPS: boot: Define __ASSEMBLY__ for its.S build xtensa: fix high memory/reserved memory collision scsi: ibmvfc: fix misdefined reserved field in ibmvfc_fcp_rsp_info MIPS: Drop spurious __unused in struct compat_flock cfg80211: fix cfg80211_beacon_dup i2c: designware: must wait for enable i2c: bcm2835: Set up the rising/falling edge delays X.509: fix BUG_ON() when hash algorithm is unsupported X.509: fix NULL dereference when restricting key with unsupported_sig PKCS#7: fix certificate chain verification PKCS#7: fix certificate blacklisting extcon: int3496: process id-pin first so that we start with the right status genirq/matrix: Handle CPU offlining proper RDMA/uverbs: Protect from races between lookup and destroy of uobjects RDMA/uverbs: Protect from command mask overflow RDMA/uverbs: Fix bad unlock balance in ib_uverbs_close_xrcd RDMA/uverbs: Fix circular locking dependency RDMA/uverbs: Sanitize user entered port numbers prior to access it iio: adc: stm32: fix stm32h7_adc_enable error handling iio: srf08: fix link error "devm_iio_triggered_buffer_setup" undefined iio: buffer: check if a buffer has been set up when poll is called iio: adis_lib: Initialize trigger before requesting interrupt Kbuild: always define endianess in kconfig.h x86/apic/vector: Handle vector release on CPU unplug correctly x86/oprofile: Fix bogus GCC-8 warning in nmi_setup() mm, swap, frontswap: fix THP swap if frontswap enabled mm: don't defer struct page initialization for Xen pv guests uapi/if_ether.h: move __UAPI_DEF_ETHHDR libc define irqchip/gic-v3: Use wmb() instead of smb_wmb() in gic_raise_softirq() irqchip/mips-gic: Avoid spuriously handling masked interrupts PCI/cxgb4: Extend T3 PCI quirk to T4+ devices net: thunderbolt: Tear down connection properly on suspend net: thunderbolt: Run disconnect flow asynchronously when logout is received ohci-hcd: Fix race condition caused by ohci_urb_enqueue() and io_watchdog_func() usb: ohci: Proper handling of ed_rm_list to handle race condition between usb_kill_urb() and finish_unlinks() arm64: Remove unimplemented syscall log message arm64: Disable unhandled signal log messages by default arm64: cpufeature: Fix CTR_EL0 field definitions Add delay-init quirk for Corsair K70 RGB keyboards drm/edid: Add 6 bpc quirk for CPT panel in Asus UX303LA usb: host: ehci: use correct device pointer for dma ops usb: dwc3: gadget: Set maxpacket size for ep0 IN usb: dwc3: ep0: Reset TRB counter for ep0 IN usb: phy: mxs: Fix NULL pointer dereference on i.MX23/28 usb: ldusb: add PIDs for new CASSY devices supported by this driver Revert "usb: musb: host: don't start next rx urb if current one failed" usb: gadget: f_fs: Process all descriptors during bind usb: gadget: f_fs: Use config_ep_by_speed() usb: renesas_usbhs: missed the "running" flag in usb_dmac with rx path drm/cirrus: Load lut in crtc_commit drm/atomic: Fix memleak on ERESTARTSYS during non-blocking commits drm: Handle unexpected holes in color-eviction drm/amdgpu: disable MMHUB power gating on raven drm/amdgpu: fix VA hole handling on Vega10 v3 drm/amdgpu: Add dpm quirk for Jet PRO (v2) drm/amdgpu: only check mmBIF_IOV_FUNC_IDENTIFIER on tonga/fiji drm/amdgpu: add atpx quirk handling (v2) drm/amdgpu: Avoid leaking PM domain on driver unbind (v2) drm/amdgpu: add new device to use atpx quirk arm64: __show_regs: Only resolve kernel symbols when running at EL1 drm/i915/breadcrumbs: Ignore unsubmitted signalers microblaze: fix endian handling Linux 4.15.7 ** Affects: linux (Ubuntu) Importance: Medium Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Affects: linux (Ubuntu Bionic) Importance: Medium Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Tags added: kernel-stable-tracking-bug ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from
[Kernel-packages] [Bug 1745263] Re: Xenial update to 4.4.111 stable release
Skipped at application time as already applied: * Input: elantech - add new icbody type 15 (bug #1733605) ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1745263 Title: Xenial update to 4.4.111 stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.111 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.111 stable release shall be applied: * x86/kasan: Write protect kasan zero shadow * kernel/acct.c: fix the acct->needcheck check in check_free_space() * crypto: n2 - cure use after free * crypto: chacha20poly1305 - validate the digest size * crypto: pcrypt - fix freeing pcrypt instances * sunxi-rsb: Include OF based modalias in device uevent * fscache: Fix the default for fscache_maybe_release_page() * kernel: make groups_sort calling a responsibility group_info allocators * kernel/signal.c: protect the traced SIGNAL_UNKILLABLE tasks from SIGKILL * kernel/signal.c: protect the SIGNAL_UNKILLABLE tasks from !sig_kernel_only() signals * kernel/signal.c: remove the no longer needed SIGNAL_UNKILLABLE check in complete_signal() * ARC: uaccess: dont use "l" gcc inline asm constraint modifier * Input: elantech - add new icbody type 15 * x86/microcode/AMD: Add support for fam17h microcode loading * parisc: Fix alignment of pa_tlb_lock in assembly on 32-bit SMP kernel * x86/tlb: Drop the _GPL from the cpu_tlbstate export * genksyms: Handle string literals with spaces in reference files * module: keep percpu symbols in module's symtab * module: Issue warnings when tainting kernel * proc: much faster /proc/vmstat * Map the vsyscall page with _PAGE_USER * Fix build error in vma.c * Linux 4.4.111 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745263/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1745364] Re: x86/net/bpf: return statement missing value
** Changed in: linux (Ubuntu Xenial) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1745364 Title: x86/net/bpf: return statement missing value Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification = Coverity reports: *** CID 1464330: Uninitialized variables (MISSING_RETURN) /arch/x86/net/bpf_jit_comp.c: 1088 in bpf_int_jit_compile() 1082int i; 1083 1084 if (!bpf_jit_enable) 1085return prog; 1086 1087 if (!prog || !prog->len) >>> CID 1464330: Uninitialized variables (MISSING_RETURN) >>> Arriving at the end of a function without returning a value. 1088return; 1089 1090 addrs = kmalloc(prog->len * sizeof(*addrs), GFP_KERNEL); 1091if (!addrs) 1092return prog; 1093 This is a result of 3098d8eae421 ("bpf: prepare bpf_int_jit_compile/bpf_prog_select_runtime apis"), which is a cherry- pick of d1c55ab5e41f upstream. In that patch, the return type of bpf_int_jit_compile was changed from void to struct bpf_prog*. That patch changed some of the return statements. It did not, however, change the return statement of the (!prog || !prog->len) check, as in upstream the (!prog || !prog->len) check was dropped in 93a73d442d37 ("bpf, x86/arm64: remove useless checks on prog"): """ There is never such a situation, where bpf_int_jit_compile() is called with either prog as NULL or len as 0, so the tests are unnecessary and confusing as people would just copy them. """ However, we haven't picked up 93a73d442d37, so when we cherry-picked d1c55ab5e41f, that branch remained unmodified, hence the static analysis warning. Impact == If the branch is not dead and someone can hit it, an undefined value can be returned, which could cause issues. Fix === For consistency and in case the branch is not actually dead on Xenial, we should do a fixup to 'return prog;' Regression Potential Limited to the BPF jit which is off by default. Limited to a branch that should be dead code anyway. Limited to an error handling path. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745364/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752336] [NEW] BUG: Bad page map in process CompositorTileW pte:94aadfb0 pmd:943ae067
Public bug reported: This just happened ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm3937 F pulseaudio fabio 4501 F pulseaudio /dev/snd/controlC0: gdm3937 F pulseaudio fabio 4501 F pulseaudio Date: Wed Feb 28 16:18:53 2018 Failure: oops HibernationDevice: RESUME=UUID=f6770099-4a42-48e3-b4ab-588190b2a701 InstallationDate: Installed on 2017-08-21 (191 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 008: ID 13d3:3408 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=3eab3ace-7b67-4e6a-aea7-d31b73cc4819 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: BUG: Bad page map in process CompositorTileW pte:94aadfb0 pmd:943ae067 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JK 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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-kerneloops bionic kernel-oops -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752336 Title: BUG: Bad page map in process CompositorTileW pte:94aadfb0 pmd:943ae067 Status in linux package in Ubuntu: Confirmed Bug description: This just happened ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm3937 F pulseaudio fabio 4501 F pulseaudio /dev/snd/controlC0: gdm3937 F pulseaudio fabio 4501 F pulseaudio Date: Wed Feb 28 16:18:53 2018 Failure: oops HibernationDevice: RESUME=UUID=f6770099-4a42-48e3-b4ab-588190b2a701 InstallationDate: Installed on 2017-08-21 (191 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 008: ID 13d3:3408 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=3eab3ace-7b67-4e6a-aea7-d31b73cc4819 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: BUG: Bad page map in process CompositorTileW pte:94aadfb0 pmd:943ae067 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JK 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:
[Kernel-packages] [Bug 1745263] Re: Xenial update to 4.4.111 stable release
** Changed in: linux (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1745263 Title: Xenial update to 4.4.111 stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.111 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.111 stable release shall be applied: * x86/kasan: Write protect kasan zero shadow * kernel/acct.c: fix the acct->needcheck check in check_free_space() * crypto: n2 - cure use after free * crypto: chacha20poly1305 - validate the digest size * crypto: pcrypt - fix freeing pcrypt instances * sunxi-rsb: Include OF based modalias in device uevent * fscache: Fix the default for fscache_maybe_release_page() * kernel: make groups_sort calling a responsibility group_info allocators * kernel/signal.c: protect the traced SIGNAL_UNKILLABLE tasks from SIGKILL * kernel/signal.c: protect the SIGNAL_UNKILLABLE tasks from !sig_kernel_only() signals * kernel/signal.c: remove the no longer needed SIGNAL_UNKILLABLE check in complete_signal() * ARC: uaccess: dont use "l" gcc inline asm constraint modifier * Input: elantech - add new icbody type 15 * x86/microcode/AMD: Add support for fam17h microcode loading * parisc: Fix alignment of pa_tlb_lock in assembly on 32-bit SMP kernel * x86/tlb: Drop the _GPL from the cpu_tlbstate export * genksyms: Handle string literals with spaces in reference files * module: keep percpu symbols in module's symtab * module: Issue warnings when tainting kernel * proc: much faster /proc/vmstat * Map the vsyscall page with _PAGE_USER * Fix build error in vma.c * Linux 4.4.111 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745263/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1743094] Re: [regression] hibernation (freezes on resume) since 4.13.0-25.29
For ubuntu 17.10 on HP 2000, I can confirm version 4.16rc2 of the linux kernel has this bug fixed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1743094 Title: [regression] hibernation (freezes on resume) since 4.13.0-25.29 Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: After hibernating the system and than resuming it the system reboots notifying that it is resuming and than stops/freezes. The system does not respond to anything (no tty's other notifying textg are available). After booting kernel 4.10-042 the hibernation and hibride hibernation/sleep functions as proposed. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jb 1717 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=00059f88-0cf2-44a0-a23d-f0a995cb1478 InstallationDate: Installed on 2017-12-10 (34 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124 MachineType: Acer Aspire S3-391 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic root=UUID=5397ffb7-8114-45c4-824f-b1da7cce468c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-26-generic N/A linux-backports-modules-4.13.0-26-generic N/A linux-firmware 1.157.14 Tags: sylvia Uname: Linux 4.13.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/31/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Hummingbird2 dmi.board.vendor: Acer dmi.board.version: V2.10 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.10 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.10:bd10/31/2012:svnAcer:pnAspireS3-391:pvrV2.10:rvnAcer:rnHummingbird2:rvrV2.10:cvnAcer:ct10:cvrV2.10: dmi.product.family: ChiefRiver System dmi.product.name: Aspire S3-391 dmi.product.version: V2.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1609143] Re: "lsluns" does not display ds8k lun information and unable to activate ds8k storage luns in host
** Changed in: linux (Ubuntu) Assignee: bugproxy (bugproxy) => (unassigned) ** Changed in: ubuntu-z-systems Assignee: bugproxy (bugproxy) => (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/1609143 Title: "lsluns" does not display ds8k lun information and unable to activate ds8k storage luns in host Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: == Comment: #2 - Steffen Maier - 2016-08-01 09:54:09 == While LTC bug 139096 - LP1567602 : FCP devices are not detected correctly nor deterministically did successfully fix the attachment of "regular" LUNs of (peripheral device) type disk, it seems the attachment of the (report luns) WLUN 0xc101 (49409) still shows issues with the ALUA device handler: [ 105.049479] scsi 0:0:7:49409: Well-known LUNIBM 2107900 .470 PQ: 0 ANSI: 5 [ 105.050109] scsi 0:0:7:49409: alua: disable for non-disk devices [ 105.050112] scsi 0:0:7:49409: alua: Attach failed (-22) [ 105.050114] scsi 0:0:7:49409: failed to add device handler: -22 After this failed attempt to attach such LUN (here triggered by the "lsluns" tool from s390-tools to discover LUNs from out of user space), the corresponding SCSI device is INvisible from user space, but still exists in-kernel in some broken state. In our case here, the attachment should have been successful (or the scsi_device been unregistered completely in maybe other cases). On the next attempt to run lsluns against the same target remote port and thus the same WLUN SCSI device, we get the following kernel warning as a follow-on error: [ 572.079588] scsi 0:0:7:49409: Well-known LUNIBM 2107900 .470 PQ: 0 ANSI: 5 [ 572.080354] sysfs: cannot create duplicate filename '/bus/scsi/devices/0:0:7:49409' [ 572.080380] [ cut here ] [ 572.080381] WARNING: at /build/linux-0ECIDW/linux-4.4.0/fs/sysfs/dir.c:31 [ 572.080381] Modules linked in: qeth_l3 chsc_sch eadm_sch qeth ccwgroup ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsd auth_rpcgss nfs_acl lockd grace sunrpc btrfs zlib_deflate raid10 raid456 async_memcpy async_raid6_recov async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear dm_round_robin ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 sha1_s390 sha_common dasd_eckd_mod dasd_mod zfcp qdio scsi_transport_fc scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath [ 572.080404] CPU: 1 PID: 8494 Comm: sh Not tainted 4.4.0-31-generic #50-Ubuntu [ 572.080405] task: 0001d7740af0 ti: 0001d8144000 task.ti: 0001d8144000 [ 572.080406] Krnl PSW : 0704c0018000 003a35fc (sysfs_warn_dup+0x7c/0x98) [ 572.080415]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 EA:3 Krnl GPRS: 00cf7034 0006 0047 [ 572.080417]003a35f8 02c6 0001da805400 0001d8f2f178 [ 572.080417]00c1d0e0 0001e8cd3ab8 0001 0001e8cd3ab8 [ 572.080418]0001d8cac4b0 7b7c8000 003a35f8 0001d81479b8 [ 572.080425] Krnl Code: 003a35ec: c020002f33f3larl %r2,989dd2 003a35f2: c0e5fff6bf0bbrasl %r14,27b408 #003a35f8: a7f40001brc 15,3a35fa >003a35fc: b904002dlgr %r2,%r13 003a3600: ebbff0a4lmg %r11,%r15,160(%r15) 003a3606: c0f4fffa5999brcl 15,2ee938 003a360c: a739lghi%r3,0 003a3610: a7f4ffecbrc 15,3a35e8 [ 572.080438] Call Trace: [ 572.080440] ([<003a35f8>] sysfs_warn_dup+0x78/0x98) [ 572.080443] [<003a3b10>] sysfs_do_create_link_sd.isra.0+0xf8/0x108 [ 572.080447] [<005c4004>] bus_add_device+0x13c/0x230 [ 572.080448] [<005c1718>] device_add+0x398/0x680 [ 572.080453] [<005f79bc>] scsi_sysfs_add_sdev+0xcc/0x2a8 [ 572.080456] [<005f4198>] scsi_probe_and_add_lun+0xcc0/0xe18 [ 572.080457] [<005f4be2>] __scsi_scan_target+0xba/0x268 [ 572.080458] [<005f4e92>] scsi_scan_target+0x102/0x120 [ 572.080468] [<03ff800765f6>] zfcp_unit_scsi_scan+0x7e/0x90 [zfcp] [ 572.080471] [<03ff80076948>] zfcp_unit_add+0x168/0x1f0 [zfcp] [ 572.080474] [<03ff80075564>] zfcp_sysfs_unit_add_store+0x54/0x70 [zfcp] [ 572.080476] [<003a1d7a>]
[Kernel-packages] [Bug 1745266] Re: Xenial update to 4.4.112 stable release
** Changed in: linux (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1745266 Title: Xenial update to 4.4.112 stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.112 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.112 stable release shall be applied: * dm bufio: fix shrinker scans when (nr_to_scan < retain_target) * KVM: Fix stack-out-of-bounds read in write_mmio * can: gs_usb: fix return value of the "set_bittiming" callback * IB/srpt: Disable RDMA access by the initiator * MIPS: Validate PR_SET_FP_MODE prctl(2) requests against the ABI of the task * MIPS: Factor out NT_PRFPREG regset access helpers * MIPS: Guard against any partial write attempt with PTRACE_SETREGSET * MIPS: Consistently handle buffer counter with PTRACE_SETREGSET * MIPS: Fix an FCSR access API regression with NT_PRFPREG and MSA * MIPS: Also verify sizeof `elf_fpreg_t' with PTRACE_SETREGSET * MIPS: Disallow outsized PTRACE_SETREGSET NT_PRFPREG regset accesses * net/mac80211/debugfs.c: prevent build failure with CONFIG_UBSAN=y * kvm: vmx: Scrub hardware GPRs at VM-exit * x86/vsdo: Fix build on PARAVIRT_CLOCK=y, KVM_GUEST=n * x86/acpi: Handle SCI interrupts above legacy space gracefully * iommu/arm-smmu-v3: Don't free page table ops twice * ALSA: pcm: Remove incorrect snd_BUG_ON() usages * ALSA: pcm: Add missing error checks in OSS emulation plugin builder * ALSA: pcm: Abort properly at pending signal in OSS read/write loops * ALSA: pcm: Allow aborting mutex lock at OSS read/write loops * ALSA: aloop: Release cable upon open error path * ALSA: aloop: Fix inconsistent format due to incomplete rule * ALSA: aloop: Fix racy hw constraints adjustment * x86/acpi: Reduce code duplication in mp_override_legacy_irq() * mm/compaction: fix invalid free_pfn and compact_cached_free_pfn * mm/compaction: pass only pageblock aligned range to pageblock_pfn_to_page * mm/page-writeback: fix dirty_ratelimit calculation * mm/zswap: use workqueue to destroy pool * zswap: don't param_set_charp while holding spinlock * locks: don't check for race with close when setting OFD lock * futex: Replace barrier() in unqueue_me() with READ_ONCE() * locking/mutex: Allow next waiter lockless wakeup * usbvision fix overflow of interfaces array * usb: musb: ux500: Fix NULL pointer dereference at system PM * r8152: fix the wake event * r8152: use test_and_clear_bit * r8152: adjust ALDPS function * lan78xx: use skb_cow_head() to deal with cloned skbs * sr9700: use skb_cow_head() to deal with cloned skbs * smsc75xx: use skb_cow_head() to deal with cloned skbs * cx82310_eth: use skb_cow_head() to deal with cloned skbs * x86/mm/pat, /dev/mem: Remove superfluous error message * hwrng: core - sleep interruptible in read * sysrq: Fix warning in sysrq generated crash. * xhci: Fix ring leak in failure path of xhci_alloc_virt_device() * Revert "userfaultfd: selftest: vm: allow to build in vm/ directory" * x86/pti/efi: broken conversion from efi to kernel page table * 8021q: fix a memory leak for VLAN 0 device * ip6_tunnel: disable dst caching if tunnel is dual-stack * net: core: fix module type in sock_diag_bind * RDS: Heap OOB write in rds_message_alloc_sgs() * RDS: null pointer dereference in rds_atomic_free_op * sh_eth: fix TSU resource handling * sh_eth: fix SH7757 GEther initialization * net: stmmac: enable EEE in MII, GMII or RGMII only * ipv6: fix possible mem leaks in ipv6_make_skb() * crypto: algapi - fix NULL dereference in crypto_remove_spawns() * rbd: set max_segments to USHRT_MAX * x86/microcode/intel: Extend BDW late-loading with a revision check * KVM: x86: Add memory barrier on vmcs field lookup * drm/vmwgfx: Potential off by one in vmw_view_add() * kaiser: Set _PAGE_NX only if supported * bpf: add bpf_patch_insn_single helper * bpf: don't (ab)use instructions to store state * bpf: move fixup_bpf_calls() function * bpf: refactor fixup_bpf_calls() * bpf: adjust insn_aux_data when patching insns * bpf: prevent out-of-bounds speculation * bpf, array: fix overflow in max_entries and undefined behavior in index_mask * iscsi-target: Make TASK_REASSIGN use
[Kernel-packages] [Bug 1732056] Re: Touchpad stops working after a few seconds in Lenovo ideapad 320
** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: linux-oem (Ubuntu Artful) Status: New => Invalid ** Changed in: linux (Ubuntu Artful) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1732056 Title: Touchpad stops working after a few seconds in Lenovo ideapad 320 Status in HWE Next: Triaged Status in linux package in Ubuntu: Triaged Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Committed Status in linux-oem source package in Artful: Invalid Bug description: === SRU Justifications === [Impact] Touchpad freezes after a brief usage. [Fix] Quote from the commit log: "The stale cached value written at the final stage undoes the masking. Fix this by re-reading the register before clearing the interrupt. I also spotted that the interrupt-clearing code can race against amd_gpio_irq_mask() / amd_gpio_irq_unmask(), so add locking there. Presumably this race was leading to the loss of interrupts." [Test Case] Touchpad no longer freezes on ideapad 320-15ABR, a new Dell Latitude and a new Dell Inspiron. [Regression Potential] Low. It limits to AMD laptops === Original Bug Report === I have installed ubuntu bionic on a Lenovo ideapad 320. The touchpad stops working a few seconds after I log in. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rebeca 1440 F pulseaudio /dev/snd/controlC0: rebeca 1440 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Nov 13 20:03:41 2017 InstallationDate: Installed on 2017-09-22 (53 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170918) MachineType: LENOVO 80XS ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=1e55f665-bd98-4113-9ae8-ec766bfc424f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2017-11-14 (0 days ago) dmi.bios.date: 05/22/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 5QCN16WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15ABR dmi.modalias: dmi:bvnLENOVO:bvr5QCN16WW:bd05/22/2017:svnLENOVO:pn80XS:pvrLenovoideapad320-15ABR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15ABR: dmi.product.family: ideapad 320-15ABR dmi.product.name: 80XS dmi.product.version: Lenovo ideapad 320-15ABR dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1732056/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1746806] Re: sssd appears to crash AWS c5 and m5 instances, cause 100% CPU
I'm still experiencing this issue in eu-west-1 using an m5.large - machine will not boot. Kernel is 4.4.0-1052-aws sssd is 1.13.4 apparmor is 2.10.95 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1746806 Title: sssd appears to crash AWS c5 and m5 instances, cause 100% CPU Status in cloud-images: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux-aws source package in Xenial: Fix Released Bug description: After upgrading to the Ubuntu EC2 AMI from 20180126 (specifically ami-79873901 in us-west-2) we have seen sssd hard locking c5 and m5 EC2 instances after starting the service and CPU goes to 100%. We do not experience this issue with t2 or c4 instance types and we do not see this issue on any instance types using Ubuntu Cloud images from 20180109 or before. I have verified that this is kernel related as I booted an image that we created using the Ubuntu cloud image from 20180109 which works fine on a c5. I then did a "apt update && apt install --only-upgrade linux-aws && systemctl disable sssd", rebooted the server, verified I was on the new kernel and started sssd with "systemctl start sssd" and the EC2 instance froze and Cloudwatch CPU usage for that instance went to 100%. I haven't been able to find much in the syslog, kern.log, journalctl logs, etc. The only thing I have been able to find is that when this happens I tend to see "^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@" in the syslog and sssd log files. I have attached several log files and the output of a "apport-bug /usr/sbin/sssd". Let me know if you need anything else to help track this down. Thanks, Paul To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1746806/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1736393] Re: [Artful][Wyse 3040] System hang when trying to enable an offlined CPU core
** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: linux-oem (Ubuntu Artful) Status: New => Invalid ** Changed in: linux (Ubuntu Artful) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1736393 Title: [Artful][Wyse 3040] System hang when trying to enable an offlined CPU core Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Committed Status in linux-oem source package in Artful: Invalid Bug description: 1. disable cpu[1-3] $ echo 0 > /sys/devices/system/cpu/cpu[1-3]/online 2. enable cpu[1-3] $ echo 1 > /sys/devices/system/cpu/cpu[1-3]/online System will hang on step 2. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1736393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1745266] Re: Xenial update to 4.4.112 stable release
Since this update was prepared, the following patches were already applied: * KVM: Fix stack-out-of-bounds read in write_mmio (CVE-2017-17741) * RDS: null pointer dereference in rds_atomic_free_op (CVE-2018-5333) Needed fixup: * bpf: don't (ab)use instructions to store state We added a partial backport of this change when applying "bpf: fix branch pruning logic" (CVE-2017-17862) * bpf: prevent out-of-bounds speculation Because of changes introduced by "bpf: fix branch pruning logic" (CVE-2017-17862) The following patches were all also applied already as part of CVE-2017-5715 (Spectre v2 retpoline): * x86/cpu: Factor out application of forced CPU caps * x86/cpufeatures: Make CPU bugs sticky * x86/cpufeatures: Add X86_BUG_CPU_INSECURE * x86/pti: Rename BUG_CPU_INSECURE to BUG_CPU_MELTDOWN * x86/cpufeatures: Add X86_BUG_SPECTRE_V[12] * x86/cpu: Merge bugs.c and bugs_64.c * sysfs/cpu: Add vulnerability folder * x86/cpu: Implement CPU vulnerabilites sysfs functions * x86/alternatives: Add missing '\n' at end of ALTERNATIVE inline asm ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-17741 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-17862 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-5715 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-5333 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1745266 Title: Xenial update to 4.4.112 stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.112 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.112 stable release shall be applied: * dm bufio: fix shrinker scans when (nr_to_scan < retain_target) * KVM: Fix stack-out-of-bounds read in write_mmio * can: gs_usb: fix return value of the "set_bittiming" callback * IB/srpt: Disable RDMA access by the initiator * MIPS: Validate PR_SET_FP_MODE prctl(2) requests against the ABI of the task * MIPS: Factor out NT_PRFPREG regset access helpers * MIPS: Guard against any partial write attempt with PTRACE_SETREGSET * MIPS: Consistently handle buffer counter with PTRACE_SETREGSET * MIPS: Fix an FCSR access API regression with NT_PRFPREG and MSA * MIPS: Also verify sizeof `elf_fpreg_t' with PTRACE_SETREGSET * MIPS: Disallow outsized PTRACE_SETREGSET NT_PRFPREG regset accesses * net/mac80211/debugfs.c: prevent build failure with CONFIG_UBSAN=y * kvm: vmx: Scrub hardware GPRs at VM-exit * x86/vsdo: Fix build on PARAVIRT_CLOCK=y, KVM_GUEST=n * x86/acpi: Handle SCI interrupts above legacy space gracefully * iommu/arm-smmu-v3: Don't free page table ops twice * ALSA: pcm: Remove incorrect snd_BUG_ON() usages * ALSA: pcm: Add missing error checks in OSS emulation plugin builder * ALSA: pcm: Abort properly at pending signal in OSS read/write loops * ALSA: pcm: Allow aborting mutex lock at OSS read/write loops * ALSA: aloop: Release cable upon open error path * ALSA: aloop: Fix inconsistent format due to incomplete rule * ALSA: aloop: Fix racy hw constraints adjustment * x86/acpi: Reduce code duplication in mp_override_legacy_irq() * mm/compaction: fix invalid free_pfn and compact_cached_free_pfn * mm/compaction: pass only pageblock aligned range to pageblock_pfn_to_page * mm/page-writeback: fix dirty_ratelimit calculation * mm/zswap: use workqueue to destroy pool * zswap: don't param_set_charp while holding spinlock * locks: don't check for race with close when setting OFD lock * futex: Replace barrier() in unqueue_me() with READ_ONCE() * locking/mutex: Allow next waiter lockless wakeup * usbvision fix overflow of interfaces array * usb: musb: ux500: Fix NULL pointer dereference at system PM * r8152: fix the wake event * r8152: use test_and_clear_bit * r8152: adjust ALDPS function * lan78xx: use skb_cow_head() to deal with cloned skbs * sr9700: use skb_cow_head() to deal with cloned skbs * smsc75xx: use skb_cow_head() to deal with cloned skbs * cx82310_eth: use skb_cow_head() to deal with cloned skbs * x86/mm/pat, /dev/mem: Remove superfluous error message * hwrng: core - sleep interruptible in read * sysrq: Fix warning in sysrq generated crash. * xhci: Fix ring leak in failure path of xhci_alloc_virt_device() * Revert "userfaultfd: selftest: vm: allow
[Kernel-packages] [Bug 1747639] Re: [18.04 FEAT] Automatically detect layer2 setting in the qeth device driver
Hi, Julian. I picked it up and pushed to master-next. Thanks. Cascardo. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1747639 Title: [18.04 FEAT] Automatically detect layer2 setting in the qeth device driver Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: Follow-on of https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1541544 Now we have an enhancement as part of kernel 4.16. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1747639/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752350] [NEW] Bionic x86_64 Linux Kernel 4.15 fails to boot on Xen
Public bug reported: The Linux Kernel 4.15 from bionic on x86_64 immediately crashes when booted as a dom0 under Xen. A similar bug was reported by someone else for archlinux (https://bugs.archlinux.org/task/57500). A patch exists for 4.16. I tried this patch on 4.15.0-10-generic, it fixes the problem for me. (https://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git/patch/?id=4f277295e54c5b7340e48efea3fc5cc21a2872b7). Xen output: (XEN) Xen version 4.9.0 (Ubuntu 4.9.0-0ubuntu3) (stefan.ba...@canonical.com) (gcc (Ubuntu 7.2.0-8ubuntu2) 7.2.0) debug=n Fri Oct 13 15:58:41 UTC 2017 (XEN) Bootloader: GRUB 2.02~beta2-36ubuntu3.9 (XEN) Command line: placeholder com1=115200,8N1 console=com1,vga (XEN) Xen image load base address: 0 (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods: none; EDID transfer time: 0 seconds (XEN) EDID info not retrieved because no DDC retrieval method detected (XEN) Disc information: (XEN) Found 1 MBR signatures (XEN) Found 1 EDD information structures (XEN) Xen-e820 RAM map: (XEN) - 0009ec00 (usable) (XEN) 000f - 0010 (reserved) (XEN) 0010 - cb6cfc00 (usable) (XEN) cb6cfc00 - cb723c00 (ACPI NVS) (XEN) cb723c00 - cb725c00 (ACPI data) (XEN) cb725c00 - cc00 (reserved) (XEN) f800 - fc00 (reserved) (XEN) fec0 - fed00400 (reserved) (XEN) fed2 - feda (reserved) (XEN) fee0 - fef0 (reserved) (XEN) ffb0 - 0001 (reserved) (XEN) 0001 - 00013000 (usable) (XEN) New Xen image base address: 0xcb00 (XEN) ACPI: RSDP 000FEC00, 0024 (r2 DELL ) (XEN) ACPI: XSDT 000FC7E7, 006C (r1 DELLB11K 15 ASL61) (XEN) ACPI: FACP 000FC8D7, 00F4 (r3 DELLB11K 15 ASL61) (XEN) ACPI: DSDT FFDC89E4, 47BC (r1 DELLdt_ex 1000 INTL 20050624) (XEN) ACPI: FACS CB6CFC00, 0040 (XEN) ACPI: SSDT FFDCD2C1, 00AC (r1 DELLst_ex 1000 INTL 20050624) (XEN) ACPI: APIC 000FC9CB, 0092 (r1 DELLB11K 15 ASL61) (XEN) ACPI: BOOT 000FCA5D, 0028 (r1 DELLB11K 15 ASL61) (XEN) ACPI: ASF! 000FCA85, 0096 (r32 DELLB11K 15 ASL61) (XEN) ACPI: MCFG 000FCB1B, 003E (r1 DELLB11K 15 ASL61) (XEN) ACPI: HPET 000FCB59, 0038 (r1 DELLB11K 15 ASL61) (XEN) ACPI: TCPA 000FCDB5, 0032 (r1 DELLB11K 15 ASL61) (XEN) ACPI: DMAR 000FCDE7, 0068 (r1 DELLB11K 15 ASL61) (XEN) System RAM: 4022MB (4118964kB) (XEN) Domain heap initialised (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec0, GSI 0-23 (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Platform timer is 14.318MHz HPET (XEN) Detected 2926.007 MHz processor. (XEN) Initing memory sharing. (XEN) Intel VT-d iommu 0 supported page sizes: 4kB. (XEN) Intel VT-d Snoop Control enabled. (XEN) Intel VT-d Dom0 DMA Passthrough not enabled. (XEN) Intel VT-d Queued Invalidation enabled. (XEN) Intel VT-d Interrupt Remapping not enabled. (XEN) Intel VT-d Posted Interrupt not enabled. (XEN) Intel VT-d Shared EPT tables not enabled. (XEN) :04:00.0: unknown type 4 (XEN) I/O virtualisation enabled (XEN) - Dom0 mode: Relaxed (XEN) Interrupt remapping disabled (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) Allocated console ring of 16 KiB. (XEN) VMX: Supported advanced features: (XEN) - APIC MMIO access virtualisation (XEN) - APIC TPR shadow (XEN) - Extended Page Tables (EPT) (XEN) - Virtual-Processor Identifiers (VPID) (XEN) - Virtual NMI (XEN) - MSR direct-access bitmap (XEN) HVM: ASIDs enabled. (XEN) HVM: VMX enabled (XEN) HVM: Hardware Assisted Paging (HAP) detected (XEN) HVM: HAP page sizes: 4kB, 2MB (XEN) Brought up 4 CPUs (XEN) Dom0 has maximum 600 PIRQs (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x100 -> 0x2b69000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 00012000->00012400 (952940 pages to be allocated) (XEN) Init. ramdisk: 00012d251000->00012575 (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: 8100->82b69000 (XEN) Init. ramdisk: -> (XEN) Phys-Mach map: 0080->00800077c0d8 (XEN) Start info:82b69000->82b694b4 (XEN) Page tables: 82b6a000->82b85000 (XEN) Boot stack:82b85000->82b86000 (XEN) TOTAL: 8000->8300 (XEN) ENTRY ADDRESS: 826a3180 (XEN) Dom0 has maximum 4 VCPUs (XEN) setup :04:00.0 for d0 failed (-22) (XEN) Scrubbing Free RAM on 1 nodes using 4 CPUs (XEN) ..done. (XEN) Initial low memory virq threshold set at
[Kernel-packages] [Bug 1752350] Re: Bionic x86_64 Linux Kernel 4.15 fails to boot on Xen
I can not run apport-collect on the affected system, since the kernel crashes immediately. ** 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/1752350 Title: Bionic x86_64 Linux Kernel 4.15 fails to boot on Xen Status in linux package in Ubuntu: Confirmed Bug description: The Linux Kernel 4.15 from bionic on x86_64 immediately crashes when booted as a dom0 under Xen. A similar bug was reported by someone else for archlinux (https://bugs.archlinux.org/task/57500). A patch exists for 4.16. I tried this patch on 4.15.0-10-generic, it fixes the problem for me. (https://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git/patch/?id=4f277295e54c5b7340e48efea3fc5cc21a2872b7). Xen output: (XEN) Xen version 4.9.0 (Ubuntu 4.9.0-0ubuntu3) (stefan.ba...@canonical.com) (gcc (Ubuntu 7.2.0-8ubuntu2) 7.2.0) debug=n Fri Oct 13 15:58:41 UTC 2017 (XEN) Bootloader: GRUB 2.02~beta2-36ubuntu3.9 (XEN) Command line: placeholder com1=115200,8N1 console=com1,vga (XEN) Xen image load base address: 0 (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods: none; EDID transfer time: 0 seconds (XEN) EDID info not retrieved because no DDC retrieval method detected (XEN) Disc information: (XEN) Found 1 MBR signatures (XEN) Found 1 EDD information structures (XEN) Xen-e820 RAM map: (XEN) - 0009ec00 (usable) (XEN) 000f - 0010 (reserved) (XEN) 0010 - cb6cfc00 (usable) (XEN) cb6cfc00 - cb723c00 (ACPI NVS) (XEN) cb723c00 - cb725c00 (ACPI data) (XEN) cb725c00 - cc00 (reserved) (XEN) f800 - fc00 (reserved) (XEN) fec0 - fed00400 (reserved) (XEN) fed2 - feda (reserved) (XEN) fee0 - fef0 (reserved) (XEN) ffb0 - 0001 (reserved) (XEN) 0001 - 00013000 (usable) (XEN) New Xen image base address: 0xcb00 (XEN) ACPI: RSDP 000FEC00, 0024 (r2 DELL ) (XEN) ACPI: XSDT 000FC7E7, 006C (r1 DELLB11K 15 ASL61) (XEN) ACPI: FACP 000FC8D7, 00F4 (r3 DELLB11K 15 ASL61) (XEN) ACPI: DSDT FFDC89E4, 47BC (r1 DELLdt_ex 1000 INTL 20050624) (XEN) ACPI: FACS CB6CFC00, 0040 (XEN) ACPI: SSDT FFDCD2C1, 00AC (r1 DELLst_ex 1000 INTL 20050624) (XEN) ACPI: APIC 000FC9CB, 0092 (r1 DELLB11K 15 ASL61) (XEN) ACPI: BOOT 000FCA5D, 0028 (r1 DELLB11K 15 ASL61) (XEN) ACPI: ASF! 000FCA85, 0096 (r32 DELLB11K 15 ASL61) (XEN) ACPI: MCFG 000FCB1B, 003E (r1 DELLB11K 15 ASL61) (XEN) ACPI: HPET 000FCB59, 0038 (r1 DELLB11K 15 ASL61) (XEN) ACPI: TCPA 000FCDB5, 0032 (r1 DELLB11K 15 ASL61) (XEN) ACPI: DMAR 000FCDE7, 0068 (r1 DELLB11K 15 ASL61) (XEN) System RAM: 4022MB (4118964kB) (XEN) Domain heap initialised (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec0, GSI 0-23 (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Platform timer is 14.318MHz HPET (XEN) Detected 2926.007 MHz processor. (XEN) Initing memory sharing. (XEN) Intel VT-d iommu 0 supported page sizes: 4kB. (XEN) Intel VT-d Snoop Control enabled. (XEN) Intel VT-d Dom0 DMA Passthrough not enabled. (XEN) Intel VT-d Queued Invalidation enabled. (XEN) Intel VT-d Interrupt Remapping not enabled. (XEN) Intel VT-d Posted Interrupt not enabled. (XEN) Intel VT-d Shared EPT tables not enabled. (XEN) :04:00.0: unknown type 4 (XEN) I/O virtualisation enabled (XEN) - Dom0 mode: Relaxed (XEN) Interrupt remapping disabled (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) Allocated console ring of 16 KiB. (XEN) VMX: Supported advanced features: (XEN) - APIC MMIO access virtualisation (XEN) - APIC TPR shadow (XEN) - Extended Page Tables (EPT) (XEN) - Virtual-Processor Identifiers (VPID) (XEN) - Virtual NMI (XEN) - MSR direct-access bitmap (XEN) HVM: ASIDs enabled. (XEN) HVM: VMX enabled (XEN) HVM: Hardware Assisted Paging (HAP) detected (XEN) HVM: HAP page sizes: 4kB, 2MB (XEN) Brought up 4 CPUs (XEN) Dom0 has maximum 600 PIRQs (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x100 -> 0x2b69000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 00012000->00012400 (952940 pages to be allocated) (XEN) Init. ramdisk: 00012d251000->00012575 (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel:
[Kernel-packages] [Bug 1752350] 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 1752350 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752350 Title: Bionic x86_64 Linux Kernel 4.15 fails to boot on Xen Status in linux package in Ubuntu: Confirmed Bug description: The Linux Kernel 4.15 from bionic on x86_64 immediately crashes when booted as a dom0 under Xen. A similar bug was reported by someone else for archlinux (https://bugs.archlinux.org/task/57500). A patch exists for 4.16. I tried this patch on 4.15.0-10-generic, it fixes the problem for me. (https://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git/patch/?id=4f277295e54c5b7340e48efea3fc5cc21a2872b7). Xen output: (XEN) Xen version 4.9.0 (Ubuntu 4.9.0-0ubuntu3) (stefan.ba...@canonical.com) (gcc (Ubuntu 7.2.0-8ubuntu2) 7.2.0) debug=n Fri Oct 13 15:58:41 UTC 2017 (XEN) Bootloader: GRUB 2.02~beta2-36ubuntu3.9 (XEN) Command line: placeholder com1=115200,8N1 console=com1,vga (XEN) Xen image load base address: 0 (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods: none; EDID transfer time: 0 seconds (XEN) EDID info not retrieved because no DDC retrieval method detected (XEN) Disc information: (XEN) Found 1 MBR signatures (XEN) Found 1 EDD information structures (XEN) Xen-e820 RAM map: (XEN) - 0009ec00 (usable) (XEN) 000f - 0010 (reserved) (XEN) 0010 - cb6cfc00 (usable) (XEN) cb6cfc00 - cb723c00 (ACPI NVS) (XEN) cb723c00 - cb725c00 (ACPI data) (XEN) cb725c00 - cc00 (reserved) (XEN) f800 - fc00 (reserved) (XEN) fec0 - fed00400 (reserved) (XEN) fed2 - feda (reserved) (XEN) fee0 - fef0 (reserved) (XEN) ffb0 - 0001 (reserved) (XEN) 0001 - 00013000 (usable) (XEN) New Xen image base address: 0xcb00 (XEN) ACPI: RSDP 000FEC00, 0024 (r2 DELL ) (XEN) ACPI: XSDT 000FC7E7, 006C (r1 DELLB11K 15 ASL61) (XEN) ACPI: FACP 000FC8D7, 00F4 (r3 DELLB11K 15 ASL61) (XEN) ACPI: DSDT FFDC89E4, 47BC (r1 DELLdt_ex 1000 INTL 20050624) (XEN) ACPI: FACS CB6CFC00, 0040 (XEN) ACPI: SSDT FFDCD2C1, 00AC (r1 DELLst_ex 1000 INTL 20050624) (XEN) ACPI: APIC 000FC9CB, 0092 (r1 DELLB11K 15 ASL61) (XEN) ACPI: BOOT 000FCA5D, 0028 (r1 DELLB11K 15 ASL61) (XEN) ACPI: ASF! 000FCA85, 0096 (r32 DELLB11K 15 ASL61) (XEN) ACPI: MCFG 000FCB1B, 003E (r1 DELLB11K 15 ASL61) (XEN) ACPI: HPET 000FCB59, 0038 (r1 DELLB11K 15 ASL61) (XEN) ACPI: TCPA 000FCDB5, 0032 (r1 DELLB11K 15 ASL61) (XEN) ACPI: DMAR 000FCDE7, 0068 (r1 DELLB11K 15 ASL61) (XEN) System RAM: 4022MB (4118964kB) (XEN) Domain heap initialised (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec0, GSI 0-23 (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Platform timer is 14.318MHz HPET (XEN) Detected 2926.007 MHz processor. (XEN) Initing memory sharing. (XEN) Intel VT-d iommu 0 supported page sizes: 4kB. (XEN) Intel VT-d Snoop Control enabled. (XEN) Intel VT-d Dom0 DMA Passthrough not enabled. (XEN) Intel VT-d Queued Invalidation enabled. (XEN) Intel VT-d Interrupt Remapping not enabled. (XEN) Intel VT-d Posted Interrupt not enabled. (XEN) Intel VT-d Shared EPT tables not enabled. (XEN) :04:00.0: unknown type 4 (XEN) I/O virtualisation enabled (XEN) - Dom0 mode: Relaxed (XEN) Interrupt remapping disabled (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) Allocated console ring of 16 KiB. (XEN) VMX: Supported advanced features: (XEN) - APIC MMIO access virtualisation (XEN) - APIC TPR shadow (XEN) - Extended Page Tables (EPT) (XEN) - Virtual-Processor Identifiers (VPID) (XEN) - Virtual NMI (XEN) - MSR direct-access bitmap (XEN) HVM: ASIDs enabled. (XEN) HVM: VMX enabled (XEN) HVM: Hardware Assisted Paging (HAP) detected (XEN) HVM: HAP page
[Kernel-packages] [Bug 1654754] Re: Wifi stopped working; ath10k_pci firmware crash in dmesg log
This is an unsupported release now. Please think to install the next LTS 'Bionic 18.04' http://cdimage.ubuntu.com/ubuntu-next/daily-live/current/ https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1654754 Title: Wifi stopped working; ath10k_pci firmware crash in dmesg log Status in linux-firmware package in Ubuntu: Invalid Bug description: Wifi worked fine for a while then stopped working. dmesg log has a correlated firmware crash for the Wifi adapter's driver. Disabling and reenabling Wifi in the network manager widget seemed to make it work for a while again. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-firmware 1.161.1 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jan 7 15:42:55 2017 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes InstallationDate: Installed on 2016-12-20 (18 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: Upgraded to yakkety on 2017-01-03 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1654754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1736393] Re: [Artful][Wyse 3040] System hang when trying to enable an offlined CPU core
** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Artful) Status: New => Fix Committed ** Changed in: linux-oem (Ubuntu Artful) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1736393 Title: [Artful][Wyse 3040] System hang when trying to enable an offlined CPU core Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Committed Status in linux-oem source package in Artful: Invalid Bug description: 1. disable cpu[1-3] $ echo 0 > /sys/devices/system/cpu/cpu[1-3]/online 2. enable cpu[1-3] $ echo 1 > /sys/devices/system/cpu/cpu[1-3]/online System will hang on step 2. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1736393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752317] Re: Bionic update to v4.15.7 stable release
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752317 Title: Bionic update to v4.15.7 stable release Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The v4.15.7 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the v4.15.7 stable release shall be applied: netfilter: drop outermost socket lock in getsockopt() arm64: mm: don't write garbage into TTBR1_EL1 register kconfig.h: Include compiler types to avoid missed struct attributes MIPS: boot: Define __ASSEMBLY__ for its.S build xtensa: fix high memory/reserved memory collision scsi: ibmvfc: fix misdefined reserved field in ibmvfc_fcp_rsp_info MIPS: Drop spurious __unused in struct compat_flock cfg80211: fix cfg80211_beacon_dup i2c: designware: must wait for enable i2c: bcm2835: Set up the rising/falling edge delays X.509: fix BUG_ON() when hash algorithm is unsupported X.509: fix NULL dereference when restricting key with unsupported_sig PKCS#7: fix certificate chain verification PKCS#7: fix certificate blacklisting extcon: int3496: process id-pin first so that we start with the right status genirq/matrix: Handle CPU offlining proper RDMA/uverbs: Protect from races between lookup and destroy of uobjects RDMA/uverbs: Protect from command mask overflow RDMA/uverbs: Fix bad unlock balance in ib_uverbs_close_xrcd RDMA/uverbs: Fix circular locking dependency RDMA/uverbs: Sanitize user entered port numbers prior to access it iio: adc: stm32: fix stm32h7_adc_enable error handling iio: srf08: fix link error "devm_iio_triggered_buffer_setup" undefined iio: buffer: check if a buffer has been set up when poll is called iio: adis_lib: Initialize trigger before requesting interrupt Kbuild: always define endianess in kconfig.h x86/apic/vector: Handle vector release on CPU unplug correctly x86/oprofile: Fix bogus GCC-8 warning in nmi_setup() mm, swap, frontswap: fix THP swap if frontswap enabled mm: don't defer struct page initialization for Xen pv guests uapi/if_ether.h: move __UAPI_DEF_ETHHDR libc define irqchip/gic-v3: Use wmb() instead of smb_wmb() in gic_raise_softirq() irqchip/mips-gic: Avoid spuriously handling masked interrupts PCI/cxgb4: Extend T3 PCI quirk to T4+ devices net: thunderbolt: Tear down connection properly on suspend net: thunderbolt: Run disconnect flow asynchronously when logout is received ohci-hcd: Fix race condition caused by ohci_urb_enqueue() and io_watchdog_func() usb: ohci: Proper handling of ed_rm_list to handle race condition between usb_kill_urb() and finish_unlinks() arm64: Remove unimplemented syscall log message arm64: Disable unhandled signal log messages by default arm64: cpufeature: Fix CTR_EL0 field definitions Add delay-init quirk for Corsair K70 RGB keyboards drm/edid: Add 6 bpc quirk for CPT panel in Asus UX303LA usb: host: ehci: use correct device pointer for dma ops usb: dwc3: gadget: Set maxpacket size for ep0 IN usb: dwc3: ep0: Reset TRB counter for ep0 IN usb: phy: mxs: Fix NULL pointer dereference on i.MX23/28 usb: ldusb: add PIDs for new CASSY devices supported by this driver Revert "usb: musb: host: don't start next rx urb if current one failed" usb: gadget: f_fs: Process all descriptors during bind usb: gadget: f_fs: Use config_ep_by_speed() usb: renesas_usbhs: missed the "running" flag in usb_dmac with rx path drm/cirrus: Load lut in crtc_commit drm/atomic: Fix memleak on ERESTARTSYS during non-blocking commits drm: Handle unexpected holes in color-eviction drm/amdgpu: disable MMHUB power gating on raven drm/amdgpu: fix VA hole handling on Vega10 v3 drm/amdgpu: Add dpm quirk for Jet PRO (v2) drm/amdgpu: only check mmBIF_IOV_FUNC_IDENTIFIER on tonga/fiji drm/amdgpu: add atpx quirk handling (v2) drm/amdgpu: Avoid leaking PM domain on driver unbind (v2) drm/amdgpu: add new device to use atpx quirk arm64: __show_regs: Only resolve kernel symbols when running at EL1 drm/i915/breadcrumbs: Ignore unsubmitted signalers microblaze: fix endian handling Linux 4.15.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752317/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1736393] Re: [Artful][Wyse 3040] System hang when trying to enable an offlined CPU core
** No longer affects: linux (Ubuntu Artful) ** No longer affects: linux-oem (Ubuntu Artful) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1736393 Title: [Artful][Wyse 3040] System hang when trying to enable an offlined CPU core Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Committed Status in linux-oem source package in Artful: Invalid Bug description: 1. disable cpu[1-3] $ echo 0 > /sys/devices/system/cpu/cpu[1-3]/online 2. enable cpu[1-3] $ echo 1 > /sys/devices/system/cpu/cpu[1-3]/online System will hang on step 2. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1736393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704929] Re: Repeating "can't open /dev/ttyX: No such device or address" messages during installation
** Changed in: ubuntu-z-systems Assignee: bugproxy (bugproxy) => (unassigned) ** No longer affects: linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1704929 Title: Repeating "can't open /dev/ttyX: No such device or address" messages during installation Status in Ubuntu on IBM z Systems: Confirmed Status in console-setup package in Ubuntu: Incomplete Bug description: [Impact] console-setup continuously tries to open /dev/tty[1-6] on s390x, when such consoles do not exist on s390x. This can be seen on boot in the output from the initramfs, and during the installer. [Cause] It seems to me that the postinst of the console-setup is incorrect for s390, since on s390 Linux tty[1-6] do not exist in any modes (LPAR, z/VM, KVM) [Solution] I do not know what ACTIVE_CONSOLES should be set as, my guess is to set it to... "guess". Usually it should be slcp, but that depends on which consoles are configured/activated in the given KVM. [Testcase] On boot, scroll all the messages and makesure there are no error messages about inability to open /dev/tty* [Original Bug Report] During the installation (z/VM guest and KVM virtual machine) of Ubuntu Server 16.04.1 (and 16.04.2) repeating messages of the form: " Select and install software ... 10% can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty3: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address ... 20% can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address ... 30%... 40% can't open /dev/tty3: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address ... 50% can't open /dev/tty3: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address ... 60% can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address ... Finishing the installation ... 13%... 22%... 31% can't open /dev/tty3: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty4: No such device or address ... 40%... 50%... 63%... 72%... 81% can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address ... 90% The system is going down NOW Sent SIGTERM to all processes Sent SIGKILL to all processes Requesting system reboot 01: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop CPU 00. 02: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop CPU 00. 03: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop CPU 00. 00 Storage cleared - system reset. 00 zIPL .. " They start to occur when the software gets installed: "Select and install software ... 10% can't open /dev/tty4: No such device or address" And only stop with the final system reboot at the end of the installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1704929/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1734691] Re: Got disk i/o failure when vary cpu offline via chcpu command (Ubuntu running on LPAR)
** Changed in: linux (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => (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/1734691 Title: Got disk i/o failure when vary cpu offline via chcpu command (Ubuntu running on LPAR) Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Got disk i/o failure when offline CPU via chcpu command ---uname output--- 4.4.0-45-generic #66-Ubuntu Machine Type = z13 - 2964 ---Debugger--- A debugger is not configured Contact Information = y...@cn.ibm.com Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. -Attach sysctl -a output output to the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1734691/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1750385] Re: Poor wifi signal with RTL8723BE and 4.13.0-32 kernel
Yes. Of course a reusable media is preferable... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1750385 Title: Poor wifi signal with RTL8723BE and 4.13.0-32 kernel Status in linux package in Ubuntu: Confirmed Bug description: When using Linux Mint 18.3 alongside with the 4.13.0-32 kernel the wifi signal is really really poor (while almost sitting on the respective router) whereas with the 4.10.0-38 it works like charm. I had to use a configuration file for getting the wifi to work properly (/etc/modprobe.d/rtl8723be.conf: options rtl8723be fwlps=0 ips=0 ant_sel=1) but chaning the antenna from 1 to 0 did not change anything with the 4.13 kernel. I am also running Manjaro Linux with the 4.14 kernel on my machine where the wifi is also working just fine (with antenna 0 though). cat /proc/version_signature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 (I tried using ubuntu-bug linux but it didn't work [The report belongs to a package that is not installed.]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1751839] Re: linux-lts-trusty: 3.13.0-143.192~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1751839 Title: linux-lts-trusty: 3.13.0-143.192~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-ports-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1751838 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1751839/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1747639] Comment bridged from LTC Bugzilla
--- Comment From julian.wiedm...@de.ibm.com 2018-02-28 04:02 EDT--- Hello Seth (long time no see!), I peeked into bionic/master-next - any chance you could cherry-pick the second patch (615dff228368) from comment #3 as well? Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1747639 Title: [18.04 FEAT] Automatically detect layer2 setting in the qeth device driver Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: Follow-on of https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1541544 Now we have an enhancement as part of kernel 4.16. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1747639/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1746019] Re: [Artful SRU] Fix capsule update regression
** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1746019 Title: [Artful SRU] Fix capsule update regression Status in linux package in Ubuntu: Incomplete Status in linux source package in Artful: New Bug description: [IMPACT] Commit 82c3768b8d68 ("efi/capsule-loader: Use a cached copy of the capsule header") refactored the capsule loading code that maps the capsule header, to avoid having to map it several times. However, as it turns out, the vmap() call we ended up removing did not just map the header, but the entire capsule image, and dropping this virtual mapping breaks capsules that are processed by the firmware immediately (i.e., without a reboot). [FIX] The following patch fixes the issue https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/firmware/efi/capsule-loader.c?id=f24c4d478013d82bd1b943df566fff3561d52864 [TEST] Please see comments below for testing information and details. [REGRESSION POTENTIAL] This patch fixes a regression in 4.13 and onward. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746019/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1668062] Re: Black screen after waking from suspend, need to reboot to use the PC
This is an unsupported release now. Please think to install the next LTS 'Bionic 18.04' http://cdimage.ubuntu.com/ubuntu-next/daily-live/current/ https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1668062 Title: Black screen after waking from suspend, need to reboot to use the PC Status in linux package in Ubuntu: Invalid Bug description: Hi, I installed a fresh Ubuntu 16.10. When I try to wake the system from suspend, I only get a black screen. The LCD back-light gets light up, the mouse pointer shows up, and it can be moved, but then I do not get anything else on the screen. I can still use Ctrl+Alt+F1 to switch to text screen. Switching back with Alt+F7 leads back to the black screen. This makes it impossible to use Ubuntu 16.10, please address. I use Fedora 25 now, and does not suffer the same issue. I am happy to provide more details (hardware, logs), please let me know. Best regards, Marton --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D7p: csalad22310 F...m pulseaudio /dev/snd/controlC1: csalad22310 F pulseaudio /dev/snd/controlC0: csalad22310 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=0d7c78b5-bcee-4f78-ac98-35861e943e69 InstallationDate: Installed on 2017-02-22 (10 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-39-generic root=UUID=080d6932-790b-4bd2-84a7-c81995d324cc ro quiet splash ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17 RelatedPackageVersions: linux-restricted-modules-4.8.0-39-generic N/A linux-backports-modules-4.8.0-39-generic N/A linux-firmware1.161.1 RfKill: Tags: yakkety Uname: Linux 4.8.0-39-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/29/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2507 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F1A75-V PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2507:bd01/29/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF1A75-VPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1743638] Re: Missing install-time driver for QLogic QED 25/40/100Gb Ethernet NIC
This bug was fixed in the package linux-firmware - 1.157.17 --- linux-firmware (1.157.17) xenial; urgency=medium * need linux-firmware for rtl bt ( 0bda:b023) (LP: #1747336) - rtl_bt: Add firmware and config file for RTL8822BE - rtl_bt: Update firmware for BT part of rtl8822be * Missing install-time driver for QLogic QED 25/40/100Gb Ethernet NIC (LP: #1743638) - UBUNTU: Add QLogic QED firmware to nic-firmware.lst -- Seth ForsheeWed, 14 Feb 2018 08:19:39 -0600 ** Changed in: linux-firmware (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1743638 Title: Missing install-time driver for QLogic QED 25/40/100Gb Ethernet NIC Status in debian-installer package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-hwe package in Ubuntu: Invalid Status in linux-hwe-edge package in Ubuntu: Invalid Status in debian-installer source package in Xenial: Fix Released Status in linux source package in Xenial: Fix Released Status in linux-firmware source package in Xenial: Fix Released Status in linux-hwe source package in Xenial: Fix Released Status in linux-hwe-edge source package in Xenial: Fix Committed Status in debian-installer source package in Artful: Fix Committed Status in linux source package in Artful: Fix Released Status in linux-firmware source package in Artful: Fix Committed Status in linux-hwe source package in Artful: Invalid Status in linux-hwe-edge source package in Artful: Invalid Status in debian-installer source package in Bionic: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-firmware source package in Bionic: Fix Released Status in linux-hwe source package in Bionic: Invalid Status in linux-hwe-edge source package in Bionic: Invalid Bug description: [Impact] Network installs over a QLogic QED 25/40/100Gb Ethernet NIC will not work. [Test Case] Attempt to use the netinst installer to install a system over this NIC. [Regression Risk] The fix is just add to add additional kernel modules and firmware to the installer to support this NIC. The biggest risk I see there is that it increases the size of the installer, which could potentially grow to bit for some smaller systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1743638/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp