[Kernel-packages] [Bug 1673805] gonzo (amd64) - tests ran: 2, failed: 0
tests ran: 2, failed: 0; http://kernel.ubuntu.com/testing/4.10.0-14.16-generic/gonzo__4.10.0-14.16__2017-03-23_06-44-00/results-index.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/1673805 Title: linux: 4.10.0-14.16 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 4.10.0-14.16 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 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1673805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1673805] modoc (ppc64el) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.10.0-14.16-generic/modoc__4.10.0-14.16__2017-03-23_06-37-00/results-index.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/1673805 Title: linux: 4.10.0-14.16 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 4.10.0-14.16 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 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1673805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1657994] Re: Regression: HDMI audio produces no sound (Skylake NUC)
Do you have any alsa/pulseaudio config? This can be quickly verified by running "vanilla" Ubuntu. 16.04: http://cdimage.ubuntu.com/xenial/daily-live/current/ 17.04: http://cdimage.ubuntu.com/daily-live/current/ If both of them work, then it's probably related to your config setting. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1657994 Title: Regression: HDMI audio produces no sound (Skylake NUC) Status in linux package in Ubuntu: Incomplete Status in linux source package in Yakkety: Incomplete Bug description: After upgrade from Xenial 16.04 to Yakkety 16.10, playing audio over HDMI no longer produces sound. * When booting with old kernel from Xenial (4.4.0-59), HDMI audio works fine * Audio from headphone jack works fine * Userspace seems to be happily playing to HDMI audio device, but no sound produced at HDMI sink (Samsung TV) Any of a wide range of pre-built mainline kernels fail to produce HDMI audio, but with a different failure mode (HDMI audio does not seem to be enumerated in the same way as in the Ubuntu kernels.) ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-34-generic 4.8.0-34.36 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: israel 1973 F pulseaudio /dev/snd/controlC1: israel 1973 F pulseaudio CurrentDesktop: Unity Date: Fri Jan 20 08:58:35 2017 HibernationDevice: RESUME=UUID=ca27f739-071f-4c25-974e-0d0f0614b21c InstallationDate: Installed on 2016-10-03 (108 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic.efi.signed root=UUID=90c3e094-e890-4c35-a0d2-0a358f5d2430 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-34-generic N/A linux-backports-modules-4.8.0-34-generic N/A linux-firmware1.161.1 SourcePackage: linux UpgradeStatus: Upgraded to yakkety on 2017-01-13 (6 days ago) dmi.bios.date: 06/03/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: KYSKLi70.86A.0037.2016.0603.1032 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-405 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrKYSKLi70.86A.0037.2016.0603.1032:bd06/03/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-405:cvnIntelCorporation:ct3:cvr1.0: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1657994/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1673805] archytas (amd64) - tests ran: 21, failed: 0
tests ran: 21, failed: 0; http://kernel.ubuntu.com/testing/4.10.0-14.16-generic/archytas__4.10.0-14.16__2017-03-23_04-40-00/results-index.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/1673805 Title: linux: 4.10.0-14.16 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 4.10.0-14.16 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 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1673805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674938] onibi (i386) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-70.91-lowlatency/onibi__4.4.0-70.91__2017-03-23_05-14-00/results-index.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/1674938 Title: linux: 4.4.0-70.91 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674939 derivatives: 1674940,1674941,1674944,1674945 kernel-stable-phase:Uploaded kernel-stable-phase-changed:Wednesday, 22. March 2017 19:03 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1674938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674938] onibi (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-70.91-lowlatency/onibi__4.4.0-70.91__2017-03-23_04-42-00/results-index.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/1674938 Title: linux: 4.4.0-70.91 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674939 derivatives: 1674940,1674941,1674944,1674945 kernel-stable-phase:Uploaded kernel-stable-phase-changed:Wednesday, 22. March 2017 19:03 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1674938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674938] onibi (i386) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-70.91-generic/onibi__4.4.0-70.91__2017-03-23_04-13-00/results-index.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/1674938 Title: linux: 4.4.0-70.91 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674939 derivatives: 1674940,1674941,1674944,1674945 kernel-stable-phase:Uploaded kernel-stable-phase-changed:Wednesday, 22. March 2017 19:03 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1674938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook
Does your system have a touchscreen? Does it have the same stuttering issue under heavy graphics load? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1590590 Title: Touchpad not recognized on Dell Latitude E7470 Ultrabook Status in linux package in Ubuntu: Triaged Status in systemd package in Ubuntu: New Status in xserver-xorg-input-synaptics package in Ubuntu: Confirmed Bug description: Expected: Touchpad settings available in Mouse & Touchpad Settings dialog Actual result: Touchpad settings missing entirely Details: The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. The settings for the touchpad are not available at all in the Mouse and Touchpad settings (see http://i.imgur.com/YRGiOrj.png). Two-finger scrolling works as expected except it's using "Natural Scrolling" by default and there is no way to change it. xinput list does not display a touchpad at all: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ ELAN Touchscreenid=11 [slave pointer (2)] ⎜ ↳ ImPS/2 Generic Wheel Mouse id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Integrated_Webcam_FHD id=10 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=12 [slave keyboard (3)] ↳ Dell WMI hotkeysid=14 [slave keyboard (3)] ↳ DELL Wireless hotkeys id=15 [slave keyboard (3)] /proc/bus/input/devices lists the device as a "Generic Wheel Mouse" Output of `lsb_release -rd`: Description: Ubuntu 16.04 LTS Release: 16.04 xserver-xorg-input-synaptics version information: xserver-xorg-input-synaptics: Installed: 1.8.2-1ubuntu3 Candidate: 1.8.2-1ubuntu3 Version table: *** 1.8.2-1ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1667160] Re: Kernel panic with 4.8.0-1025, -1026 and -1028 on RasPi 2
I encounter a similar panic w/ a pi2, kernel 4.4.0-1046-raspi2, and an edimax wifi adapter (ID 7392:7811 Edimax Technology Co., Ltd EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS] using module rtl8192cu). See attached panic output. ** Attachment added: "console output from kernel panic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667160/+attachment/4842956/+files/4.4.0-1046-raspi2_rtl8192cu_panic.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1667160 Title: Kernel panic with 4.8.0-1025, -1026 and -1028 on RasPi 2 Status in linux package in Ubuntu: Confirmed Bug description: I have a Raspberry Pi 2 running Ubuntu 16.10 without problems. I use wicd to let it connect to my WiFi with a RTL8188CUS USB dongle. And there's a RTL2838 DVB-T USB stick attached to monitor airplane positions for Flightradar24. After updateing the kernel from 4.8.0-1024, which runs flawlessly, to -1025, there's a kernel panic happening 10-20 seconds after booting up to the login prompt. I thought the -1026 fixed that, but it's still no worky. The trace is scrolling so fast I can't read anything but the last page: [<808c76c8>] (sock_sendmsg) from... [<808c7778>] (sock_write_iter) from... [<802c39c8>] (new_sync_write) from... [<802c3a4c>] (__vfs_write) from... [<802c48d8>] (vfs_write) from... [<802c5ab4>] (SyS_write) from... Code: e5922004 e0033002 e353 0a0a (e5902034) ---[ end trace 0f53d17efe0c6ba ]--- Kernel panic - not syncing: Fatal exception in interrupt CPU2: stopping CPU: 2 PID: 21 Comm: migration/2 Tainted: G D 4.8.0-1026-raspi2 #29-Ubuntu Hardware name: BCM2709 [<801120ac>] (unwind_backtrace) from ... [<8010d2dc>] (show_stack) from ... [<8059c38c>] (handle_IPI) from ... [<80101564>] (bcm2836_arm_irqchip_handle_irq) from [<80a49f3c>] (__irq_svc+0x5c/0x7c) Exception stack(0xbb99de68 to 0xbb99deb0) de60: 0004 0001 bac05de0 0001 de80: bac05dcc a00e0013 bac05d6c bb99dedc bb99dee0 bb99deb8 dea0: 801d367c 801d35f4 600e0013 [<80a49f3c>] (__irq_svc) from ... [<801d35f4>] (multi_cpu_stop) from ... [<801d38ec>] (cpu_stopper_thread) from ... [<8014b71c>] (smpboot_thread_fn) from ... [<80147770>] (kthread) from [<80108e28>] (ret_from_fork+0x14/0x2c) And then this block repeats with CPU3 and CPU0. Going back to 4.8.0-1024 makes everything work again. Affected packages: linux-image-4.8.0-1025-raspi2:armhf (4.8.0-1025.28) linux-image-4.8.0-1026-raspi2:armhf (4.8.0-1026.29) --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 25 2016 seq crw-rw 1 root audio 116, 33 Jul 25 2016 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.8.0-1024-raspi2. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.3-0ubuntu8.2 Architecture: armhf ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 16.10 Lsusb: Bus 001 Device 005: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T Bus 001 Device 004: ID 7392:7811 Edimax Technology Co., Ltd EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS] Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: linux (not installed) PciMultimedia: ProcFB: 0 BCM2708 FB ProcKernelCmdLine: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2709.boardrev=0xa01041 bcm2709.serial=0xecd3f749 smsc95xx.macaddr=B8:27:EB:D3:F7:49 bcm2708_fb.fbdepth=16 bcm2708_fb.fbswap=1 bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=47 bcm2709.disk_led_active_low=0 vc_mem.mem_base=0x3ea0 vc_mem.mem_size=0x3f00 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait ProcVersionSignature: Ubuntu 4.8.0-1024.27-raspi2 4.8.16 RelatedPackageVersions: linux-restricted-modules-4.8.0-1024-raspi2 N/A linux-backports-modules-4.8.0-1024-raspi2 N/A linux-firmware 1.161.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: yakkety Uname: Linux 4.8.0-1024-raspi2 armv7l UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: Upgraded to yakkety on 2016-10-24 (122 days ago) UserGroups: adm audio cdrom dialout floppy fuse netdev plugdev sudo users video www-data _MarkForUpload: False To manage notifications about this bug go to: https://bugs.launch
[Kernel-packages] [Bug 1644919] Re: [fn] plus F2, F3, F4, F5, F6, F10, F11, F12 not responding - Fresh Install
Hi Andrew, You need to boot to 4.4.0-XX kernel instead of mainline kernel. The latest mainline kernel is for testing only - you can safely remove those kernels after testing is done. To remove mainline kernels, you can run something like this: $ sudo apt purge $(dpkg -l | grep 041100rc2 | awk '{print $2}') Do the same for other mainline kernels you installed for testing. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1644919 Title: [fn] plus F2,F3,F4,F5,F6,F10,F11,F12 not responding - Fresh Install Status in linux package in Ubuntu: Confirmed Bug description: Gigabyte P57 laptop Fresh install, 10 days old, updated yesterday so software/kernel should be current. Some function keys work. Function plus F1 puts the machine to sleep Function plus F7, F8, F9 control the volume However, Pressing Function plus F2 does not turn off wireless Pressing Function plus F3,F4 do not change brightness Function plus F5 does not change output to LCD or Monitor Pressing Function plus F6 does not toggle touchpad (a separate bug in this machine, but the Elantech touchpad is recognised at the moment.) Function plus F10 does not turn the display off Function plus F11 does not turn off bluetooth Function plus F12 does not disable the camera Please let me know if you need any further troubleshooting ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-47-generic 4.4.0-47.68 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: horace 1948 F pulseaudio CurrentDesktop: Unity Date: Sat Nov 26 07:44:13 2016 HibernationDevice: RESUME=UUID=fba63969-ab35-4aa7-b2f7-e432edba169e InstallationDate: Installed on 2016-11-13 (12 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 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 05af:1050 Jing-Mold Enterprise Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GIGABYTE P57 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic.efi.signed root=UUID=e9ea66ca-2853-4d85-bc49-74de4c35c442 ro quiet splash i8042.nomux=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-47-generic N/A linux-backports-modules-4.4.0-47-generic N/A linux-firmware1.157.5 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FB0B dmi.board.asset.tag: Default string dmi.board.name: P57 dmi.board.vendor: GIGABYTE dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFB0B:bd05/30/2016:svnGIGABYTE:pnP57:pvrDefaultstring:rvnGIGABYTE:rnP57:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.name: P57 dmi.product.version: Default string dmi.sys.vendor: GIGABYTE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1644919/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1675204] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1675204/+attachment/4842926/+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/1675204 Title: Intel HD graphics crashes when connecting to 3 outputs (DVI+HDMI+DP) Status in linux package in Ubuntu: Confirmed Bug description: I have a very strange issue related to Intel graphics drivers (i915) with 3 connected on-board displays. I have a Xubuntu (14.04 LTS with HWE on 4.4.0-66 kernel) desktop computer running on a i7-6700K processor and on-board graphics (Mobo: AsRock z170 extreme4). I connect it to 3 displays - a 3440x1400 LG display (via onboard DP port), a 1920x1200 Dell display (via on-board HDMI), and a Sony 4k TV (via onboard DVI and a DVI-to-HDMI adapter). If I just connect my desktop to the first two displays (not the TV), everything works fine (except some minor issues). However, if I connect the 4k TV, even the TV is not on, my graphics starts to flicker every 5 min-ish (window theme turns off and then turns quickly back on); after a few flickering, the window theme will disappear, and the screen becomes weird - my chrome window will not fresh, or show blank boxes etc. If I disconnect the DVI connector to the TV (just use the LG+Dell dual-display), flickering and crash will not appear. I want to mention that, when I connect the computer to all 3 displays, I was actually able to get video output to all displays (I used arandr to configure them). I can even get 4k output to the 4k TV at 30Hz. I can't find a useful log entry when the flicking or graphics crash happens. I can only see a "CPU pipe A FIFO underrun" for pipe A/B/F (log attached at the end), but I can see many similar errors in my log and the appearance is not correlated to the flickering/crash. The "pipe A FIFO underrun" issue was previously reported in Bug#1550779. I also see "intel(0): HDMI max TMDS frequency 30KHz" entry in my Xorg.0.log file constantly, I also do not see an consistent mapping between the log entry and the flickering. Can anyone tell me how to properly debug this? what can I do to get a log for what was wrong? --- [ 145.033055] WARNING: CPU: 2 PID: 1804 at /build/linux-lts-xenial-drAJVo/linux-lts-xenial-4.4.0/ubuntu/i915/intel_pm.c:3675 skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo]() [ 145.033058] WARN_ON(!wm_changed) [ 145.033060] Modules linked in: nfsv3 pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) autofs4 rpcsec_gss_krb5 nfsv4 usblp joydev input_leds ti_usb_3410_5052 usbserial hid_generic gspca_ov534 gspca_main v4l2_common videodev media snd_usb_audio snd_usbmidi_lib usbhid snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic nvidia_uvm(POE) uas usb_storage intel_rapl x86_pkg_temp_thermal intel_powerclamp mxm_wmi coretemp kvm_intel bnep kvm rfcomm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_intel snd_hda_codec snd_hda_core nvidia_drm(POE) nvidia_modeset(POE) snd_hwdep aesni_intel snd_pcm aes_x86_64 nvidia(POE) lrw gf128mul snd_seq_midi snd_seq_midi_event glue_helper ablk_helper snd_rawmidi cryptd snd_seq snd_seq_device snd_timer serio_raw snd soundcore nfsd i915_bpo auth_rpcgss nfs_acl nfs binfmt_misc lockd grace 8250_fintek hci_uart sunrpc intel_ips drm_kms_helper btbcm pinctrl_sunrisepoint btqca fscache pinctrl_intel btintel intel_lpss_ac pi bluetooth i2c_hid intel_lpss drm hid video i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt shpchp mei_me mei mac_hid acpi_als wmi kfifo_buf industrialio acpi_pad parport_pc ppdev lp parport e1000e psmouse ptp pps_core ahci nvme libahci fjes [ 145.033284] CPU: 2 PID: 1804 Comm: Xorg Tainted: PW OE 4.4.0-66-generic #87~14.04.1-Ubuntu [ 145.033287] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z170 Extreme4, BIOS P7.00 09/09/2016 [ 145.033290] 88086e5879a0 813dc80c 88086e5879e8 [ 145.033295] c0556700 88086e5879d8 8107e9d6 88086d898000 [ 145.033300] 88086d89b000 0004 880871924b78 88086e587a64 [ 145.033305] Call Trace: [ 145.033311] [] dump_stack+0x63/0x87 [ 145.033317] [] warn_slowpath_common+0x86/0xc0 [ 145.033323] [] warn_slowpath_fmt+0x4c/0x50 [ 145.033358] [] ? ironlake_irq_handler+0x660/0xba0 [i915_bpo] [ 145.033393] [] skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo] [ 145.033435] [] skl_update_wm+0x19a/0x6f0 [i915_bpo] [ 145.033491] [] ? chv_write8+0x390/0x390 [i915_bpo] [ 145.033551] [] ? skl_ddi_pll_disable+0x70/0x80 [i915_bpo] [ 145.033590] [] intel_update_watermarks+0x1e/0x30 [i915_bpo] [ 145.033649] [] intel_atomic_commit+0x432/0x1440 [i915_bpo] [ 145.033688] [] ?
[Kernel-packages] [Bug 1675204] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1675204/+attachment/4842930/+files/UdevLog.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/1675204 Title: Intel HD graphics crashes when connecting to 3 outputs (DVI+HDMI+DP) Status in linux package in Ubuntu: Confirmed Bug description: I have a very strange issue related to Intel graphics drivers (i915) with 3 connected on-board displays. I have a Xubuntu (14.04 LTS with HWE on 4.4.0-66 kernel) desktop computer running on a i7-6700K processor and on-board graphics (Mobo: AsRock z170 extreme4). I connect it to 3 displays - a 3440x1400 LG display (via onboard DP port), a 1920x1200 Dell display (via on-board HDMI), and a Sony 4k TV (via onboard DVI and a DVI-to-HDMI adapter). If I just connect my desktop to the first two displays (not the TV), everything works fine (except some minor issues). However, if I connect the 4k TV, even the TV is not on, my graphics starts to flicker every 5 min-ish (window theme turns off and then turns quickly back on); after a few flickering, the window theme will disappear, and the screen becomes weird - my chrome window will not fresh, or show blank boxes etc. If I disconnect the DVI connector to the TV (just use the LG+Dell dual-display), flickering and crash will not appear. I want to mention that, when I connect the computer to all 3 displays, I was actually able to get video output to all displays (I used arandr to configure them). I can even get 4k output to the 4k TV at 30Hz. I can't find a useful log entry when the flicking or graphics crash happens. I can only see a "CPU pipe A FIFO underrun" for pipe A/B/F (log attached at the end), but I can see many similar errors in my log and the appearance is not correlated to the flickering/crash. The "pipe A FIFO underrun" issue was previously reported in Bug#1550779. I also see "intel(0): HDMI max TMDS frequency 30KHz" entry in my Xorg.0.log file constantly, I also do not see an consistent mapping between the log entry and the flickering. Can anyone tell me how to properly debug this? what can I do to get a log for what was wrong? --- [ 145.033055] WARNING: CPU: 2 PID: 1804 at /build/linux-lts-xenial-drAJVo/linux-lts-xenial-4.4.0/ubuntu/i915/intel_pm.c:3675 skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo]() [ 145.033058] WARN_ON(!wm_changed) [ 145.033060] Modules linked in: nfsv3 pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) autofs4 rpcsec_gss_krb5 nfsv4 usblp joydev input_leds ti_usb_3410_5052 usbserial hid_generic gspca_ov534 gspca_main v4l2_common videodev media snd_usb_audio snd_usbmidi_lib usbhid snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic nvidia_uvm(POE) uas usb_storage intel_rapl x86_pkg_temp_thermal intel_powerclamp mxm_wmi coretemp kvm_intel bnep kvm rfcomm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_intel snd_hda_codec snd_hda_core nvidia_drm(POE) nvidia_modeset(POE) snd_hwdep aesni_intel snd_pcm aes_x86_64 nvidia(POE) lrw gf128mul snd_seq_midi snd_seq_midi_event glue_helper ablk_helper snd_rawmidi cryptd snd_seq snd_seq_device snd_timer serio_raw snd soundcore nfsd i915_bpo auth_rpcgss nfs_acl nfs binfmt_misc lockd grace 8250_fintek hci_uart sunrpc intel_ips drm_kms_helper btbcm pinctrl_sunrisepoint btqca fscache pinctrl_intel btintel intel_lpss_ac pi bluetooth i2c_hid intel_lpss drm hid video i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt shpchp mei_me mei mac_hid acpi_als wmi kfifo_buf industrialio acpi_pad parport_pc ppdev lp parport e1000e psmouse ptp pps_core ahci nvme libahci fjes [ 145.033284] CPU: 2 PID: 1804 Comm: Xorg Tainted: PW OE 4.4.0-66-generic #87~14.04.1-Ubuntu [ 145.033287] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z170 Extreme4, BIOS P7.00 09/09/2016 [ 145.033290] 88086e5879a0 813dc80c 88086e5879e8 [ 145.033295] c0556700 88086e5879d8 8107e9d6 88086d898000 [ 145.033300] 88086d89b000 0004 880871924b78 88086e587a64 [ 145.033305] Call Trace: [ 145.033311] [] dump_stack+0x63/0x87 [ 145.033317] [] warn_slowpath_common+0x86/0xc0 [ 145.033323] [] warn_slowpath_fmt+0x4c/0x50 [ 145.033358] [] ? ironlake_irq_handler+0x660/0xba0 [i915_bpo] [ 145.033393] [] skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo] [ 145.033435] [] skl_update_wm+0x19a/0x6f0 [i915_bpo] [ 145.033491] [] ? chv_write8+0x390/0x390 [i915_bpo] [ 145.033551] [] ? skl_ddi_pll_disable+0x70/0x80 [i915_bpo] [ 145.033590] [] intel_update_watermarks+0x1e/0x30 [i915_bpo] [ 145.033649] [] intel_atomic_commit+0x432/0x1440 [i915_bpo] [ 145.033688] [] ? drm_atomic_s
[Kernel-packages] [Bug 1675204] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1675204/+attachment/4842946/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1675204 Title: Intel HD graphics crashes when connecting to 3 outputs (DVI+HDMI+DP) Status in linux package in Ubuntu: Confirmed Bug description: I have a very strange issue related to Intel graphics drivers (i915) with 3 connected on-board displays. I have a Xubuntu (14.04 LTS with HWE on 4.4.0-66 kernel) desktop computer running on a i7-6700K processor and on-board graphics (Mobo: AsRock z170 extreme4). I connect it to 3 displays - a 3440x1400 LG display (via onboard DP port), a 1920x1200 Dell display (via on-board HDMI), and a Sony 4k TV (via onboard DVI and a DVI-to-HDMI adapter). If I just connect my desktop to the first two displays (not the TV), everything works fine (except some minor issues). However, if I connect the 4k TV, even the TV is not on, my graphics starts to flicker every 5 min-ish (window theme turns off and then turns quickly back on); after a few flickering, the window theme will disappear, and the screen becomes weird - my chrome window will not fresh, or show blank boxes etc. If I disconnect the DVI connector to the TV (just use the LG+Dell dual-display), flickering and crash will not appear. I want to mention that, when I connect the computer to all 3 displays, I was actually able to get video output to all displays (I used arandr to configure them). I can even get 4k output to the 4k TV at 30Hz. I can't find a useful log entry when the flicking or graphics crash happens. I can only see a "CPU pipe A FIFO underrun" for pipe A/B/F (log attached at the end), but I can see many similar errors in my log and the appearance is not correlated to the flickering/crash. The "pipe A FIFO underrun" issue was previously reported in Bug#1550779. I also see "intel(0): HDMI max TMDS frequency 30KHz" entry in my Xorg.0.log file constantly, I also do not see an consistent mapping between the log entry and the flickering. Can anyone tell me how to properly debug this? what can I do to get a log for what was wrong? --- [ 145.033055] WARNING: CPU: 2 PID: 1804 at /build/linux-lts-xenial-drAJVo/linux-lts-xenial-4.4.0/ubuntu/i915/intel_pm.c:3675 skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo]() [ 145.033058] WARN_ON(!wm_changed) [ 145.033060] Modules linked in: nfsv3 pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) autofs4 rpcsec_gss_krb5 nfsv4 usblp joydev input_leds ti_usb_3410_5052 usbserial hid_generic gspca_ov534 gspca_main v4l2_common videodev media snd_usb_audio snd_usbmidi_lib usbhid snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic nvidia_uvm(POE) uas usb_storage intel_rapl x86_pkg_temp_thermal intel_powerclamp mxm_wmi coretemp kvm_intel bnep kvm rfcomm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_intel snd_hda_codec snd_hda_core nvidia_drm(POE) nvidia_modeset(POE) snd_hwdep aesni_intel snd_pcm aes_x86_64 nvidia(POE) lrw gf128mul snd_seq_midi snd_seq_midi_event glue_helper ablk_helper snd_rawmidi cryptd snd_seq snd_seq_device snd_timer serio_raw snd soundcore nfsd i915_bpo auth_rpcgss nfs_acl nfs binfmt_misc lockd grace 8250_fintek hci_uart sunrpc intel_ips drm_kms_helper btbcm pinctrl_sunrisepoint btqca fscache pinctrl_intel btintel intel_lpss_ac pi bluetooth i2c_hid intel_lpss drm hid video i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt shpchp mei_me mei mac_hid acpi_als wmi kfifo_buf industrialio acpi_pad parport_pc ppdev lp parport e1000e psmouse ptp pps_core ahci nvme libahci fjes [ 145.033284] CPU: 2 PID: 1804 Comm: Xorg Tainted: PW OE 4.4.0-66-generic #87~14.04.1-Ubuntu [ 145.033287] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z170 Extreme4, BIOS P7.00 09/09/2016 [ 145.033290] 88086e5879a0 813dc80c 88086e5879e8 [ 145.033295] c0556700 88086e5879d8 8107e9d6 88086d898000 [ 145.033300] 88086d89b000 0004 880871924b78 88086e587a64 [ 145.033305] Call Trace: [ 145.033311] [] dump_stack+0x63/0x87 [ 145.033317] [] warn_slowpath_common+0x86/0xc0 [ 145.033323] [] warn_slowpath_fmt+0x4c/0x50 [ 145.033358] [] ? ironlake_irq_handler+0x660/0xba0 [i915_bpo] [ 145.033393] [] skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo] [ 145.033435] [] skl_update_wm+0x19a/0x6f0 [i915_bpo] [ 145.033491] [] ? chv_write8+0x390/0x390 [i915_bpo] [ 145.033551] [] ? skl_ddi_pll_disable+0x70/0x80 [i915_bpo] [ 145.033590] [] intel_update_watermarks+0x1e/0x30 [i915_bpo] [ 145.033649] [] intel
[Kernel-packages] [Bug 1675204] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1675204/+attachment/4842922/+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/1675204 Title: Intel HD graphics crashes when connecting to 3 outputs (DVI+HDMI+DP) Status in linux package in Ubuntu: Confirmed Bug description: I have a very strange issue related to Intel graphics drivers (i915) with 3 connected on-board displays. I have a Xubuntu (14.04 LTS with HWE on 4.4.0-66 kernel) desktop computer running on a i7-6700K processor and on-board graphics (Mobo: AsRock z170 extreme4). I connect it to 3 displays - a 3440x1400 LG display (via onboard DP port), a 1920x1200 Dell display (via on-board HDMI), and a Sony 4k TV (via onboard DVI and a DVI-to-HDMI adapter). If I just connect my desktop to the first two displays (not the TV), everything works fine (except some minor issues). However, if I connect the 4k TV, even the TV is not on, my graphics starts to flicker every 5 min-ish (window theme turns off and then turns quickly back on); after a few flickering, the window theme will disappear, and the screen becomes weird - my chrome window will not fresh, or show blank boxes etc. If I disconnect the DVI connector to the TV (just use the LG+Dell dual-display), flickering and crash will not appear. I want to mention that, when I connect the computer to all 3 displays, I was actually able to get video output to all displays (I used arandr to configure them). I can even get 4k output to the 4k TV at 30Hz. I can't find a useful log entry when the flicking or graphics crash happens. I can only see a "CPU pipe A FIFO underrun" for pipe A/B/F (log attached at the end), but I can see many similar errors in my log and the appearance is not correlated to the flickering/crash. The "pipe A FIFO underrun" issue was previously reported in Bug#1550779. I also see "intel(0): HDMI max TMDS frequency 30KHz" entry in my Xorg.0.log file constantly, I also do not see an consistent mapping between the log entry and the flickering. Can anyone tell me how to properly debug this? what can I do to get a log for what was wrong? --- [ 145.033055] WARNING: CPU: 2 PID: 1804 at /build/linux-lts-xenial-drAJVo/linux-lts-xenial-4.4.0/ubuntu/i915/intel_pm.c:3675 skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo]() [ 145.033058] WARN_ON(!wm_changed) [ 145.033060] Modules linked in: nfsv3 pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) autofs4 rpcsec_gss_krb5 nfsv4 usblp joydev input_leds ti_usb_3410_5052 usbserial hid_generic gspca_ov534 gspca_main v4l2_common videodev media snd_usb_audio snd_usbmidi_lib usbhid snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic nvidia_uvm(POE) uas usb_storage intel_rapl x86_pkg_temp_thermal intel_powerclamp mxm_wmi coretemp kvm_intel bnep kvm rfcomm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_intel snd_hda_codec snd_hda_core nvidia_drm(POE) nvidia_modeset(POE) snd_hwdep aesni_intel snd_pcm aes_x86_64 nvidia(POE) lrw gf128mul snd_seq_midi snd_seq_midi_event glue_helper ablk_helper snd_rawmidi cryptd snd_seq snd_seq_device snd_timer serio_raw snd soundcore nfsd i915_bpo auth_rpcgss nfs_acl nfs binfmt_misc lockd grace 8250_fintek hci_uart sunrpc intel_ips drm_kms_helper btbcm pinctrl_sunrisepoint btqca fscache pinctrl_intel btintel intel_lpss_ac pi bluetooth i2c_hid intel_lpss drm hid video i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt shpchp mei_me mei mac_hid acpi_als wmi kfifo_buf industrialio acpi_pad parport_pc ppdev lp parport e1000e psmouse ptp pps_core ahci nvme libahci fjes [ 145.033284] CPU: 2 PID: 1804 Comm: Xorg Tainted: PW OE 4.4.0-66-generic #87~14.04.1-Ubuntu [ 145.033287] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z170 Extreme4, BIOS P7.00 09/09/2016 [ 145.033290] 88086e5879a0 813dc80c 88086e5879e8 [ 145.033295] c0556700 88086e5879d8 8107e9d6 88086d898000 [ 145.033300] 88086d89b000 0004 880871924b78 88086e587a64 [ 145.033305] Call Trace: [ 145.033311] [] dump_stack+0x63/0x87 [ 145.033317] [] warn_slowpath_common+0x86/0xc0 [ 145.033323] [] warn_slowpath_fmt+0x4c/0x50 [ 145.033358] [] ? ironlake_irq_handler+0x660/0xba0 [i915_bpo] [ 145.033393] [] skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo] [ 145.033435] [] skl_update_wm+0x19a/0x6f0 [i915_bpo] [ 145.033491] [] ? chv_write8+0x390/0x390 [i915_bpo] [ 145.033551] [] ? skl_ddi_pll_disable+0x70/0x80 [i915_bpo] [ 145.033590] [] intel_update_watermarks+0x1e/0x30 [i915_bpo] [ 145.033649] [] intel_atomic_commit+0x432/0x1440 [i915_bpo] [ 145.033688] [] ? drm_atomic_set_cr
[Kernel-packages] [Bug 1675204] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1675204/+attachment/4842923/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1675204 Title: Intel HD graphics crashes when connecting to 3 outputs (DVI+HDMI+DP) Status in linux package in Ubuntu: Confirmed Bug description: I have a very strange issue related to Intel graphics drivers (i915) with 3 connected on-board displays. I have a Xubuntu (14.04 LTS with HWE on 4.4.0-66 kernel) desktop computer running on a i7-6700K processor and on-board graphics (Mobo: AsRock z170 extreme4). I connect it to 3 displays - a 3440x1400 LG display (via onboard DP port), a 1920x1200 Dell display (via on-board HDMI), and a Sony 4k TV (via onboard DVI and a DVI-to-HDMI adapter). If I just connect my desktop to the first two displays (not the TV), everything works fine (except some minor issues). However, if I connect the 4k TV, even the TV is not on, my graphics starts to flicker every 5 min-ish (window theme turns off and then turns quickly back on); after a few flickering, the window theme will disappear, and the screen becomes weird - my chrome window will not fresh, or show blank boxes etc. If I disconnect the DVI connector to the TV (just use the LG+Dell dual-display), flickering and crash will not appear. I want to mention that, when I connect the computer to all 3 displays, I was actually able to get video output to all displays (I used arandr to configure them). I can even get 4k output to the 4k TV at 30Hz. I can't find a useful log entry when the flicking or graphics crash happens. I can only see a "CPU pipe A FIFO underrun" for pipe A/B/F (log attached at the end), but I can see many similar errors in my log and the appearance is not correlated to the flickering/crash. The "pipe A FIFO underrun" issue was previously reported in Bug#1550779. I also see "intel(0): HDMI max TMDS frequency 30KHz" entry in my Xorg.0.log file constantly, I also do not see an consistent mapping between the log entry and the flickering. Can anyone tell me how to properly debug this? what can I do to get a log for what was wrong? --- [ 145.033055] WARNING: CPU: 2 PID: 1804 at /build/linux-lts-xenial-drAJVo/linux-lts-xenial-4.4.0/ubuntu/i915/intel_pm.c:3675 skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo]() [ 145.033058] WARN_ON(!wm_changed) [ 145.033060] Modules linked in: nfsv3 pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) autofs4 rpcsec_gss_krb5 nfsv4 usblp joydev input_leds ti_usb_3410_5052 usbserial hid_generic gspca_ov534 gspca_main v4l2_common videodev media snd_usb_audio snd_usbmidi_lib usbhid snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic nvidia_uvm(POE) uas usb_storage intel_rapl x86_pkg_temp_thermal intel_powerclamp mxm_wmi coretemp kvm_intel bnep kvm rfcomm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_intel snd_hda_codec snd_hda_core nvidia_drm(POE) nvidia_modeset(POE) snd_hwdep aesni_intel snd_pcm aes_x86_64 nvidia(POE) lrw gf128mul snd_seq_midi snd_seq_midi_event glue_helper ablk_helper snd_rawmidi cryptd snd_seq snd_seq_device snd_timer serio_raw snd soundcore nfsd i915_bpo auth_rpcgss nfs_acl nfs binfmt_misc lockd grace 8250_fintek hci_uart sunrpc intel_ips drm_kms_helper btbcm pinctrl_sunrisepoint btqca fscache pinctrl_intel btintel intel_lpss_ac pi bluetooth i2c_hid intel_lpss drm hid video i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt shpchp mei_me mei mac_hid acpi_als wmi kfifo_buf industrialio acpi_pad parport_pc ppdev lp parport e1000e psmouse ptp pps_core ahci nvme libahci fjes [ 145.033284] CPU: 2 PID: 1804 Comm: Xorg Tainted: PW OE 4.4.0-66-generic #87~14.04.1-Ubuntu [ 145.033287] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z170 Extreme4, BIOS P7.00 09/09/2016 [ 145.033290] 88086e5879a0 813dc80c 88086e5879e8 [ 145.033295] c0556700 88086e5879d8 8107e9d6 88086d898000 [ 145.033300] 88086d89b000 0004 880871924b78 88086e587a64 [ 145.033305] Call Trace: [ 145.033311] [] dump_stack+0x63/0x87 [ 145.033317] [] warn_slowpath_common+0x86/0xc0 [ 145.033323] [] warn_slowpath_fmt+0x4c/0x50 [ 145.033358] [] ? ironlake_irq_handler+0x660/0xba0 [i915_bpo] [ 145.033393] [] skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo] [ 145.033435] [] skl_update_wm+0x19a/0x6f0 [i915_bpo] [ 145.033491] [] ? chv_write8+0x390/0x390 [i915_bpo] [ 145.033551] [] ? skl_ddi_pll_disable+0x70/0x80 [i915_bpo] [ 145.033590] [] intel_update_watermarks+0x1e/0x30 [i915_bpo] [ 145.033649] [] intel_atomic_commit+0x432/0x1440 [i915_bpo] [ 145.033688] [] ? drm_atomic_set_cr
[Kernel-packages] [Bug 1675204] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1675204/+attachment/4842940/+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/1675204 Title: Intel HD graphics crashes when connecting to 3 outputs (DVI+HDMI+DP) Status in linux package in Ubuntu: Confirmed Bug description: I have a very strange issue related to Intel graphics drivers (i915) with 3 connected on-board displays. I have a Xubuntu (14.04 LTS with HWE on 4.4.0-66 kernel) desktop computer running on a i7-6700K processor and on-board graphics (Mobo: AsRock z170 extreme4). I connect it to 3 displays - a 3440x1400 LG display (via onboard DP port), a 1920x1200 Dell display (via on-board HDMI), and a Sony 4k TV (via onboard DVI and a DVI-to-HDMI adapter). If I just connect my desktop to the first two displays (not the TV), everything works fine (except some minor issues). However, if I connect the 4k TV, even the TV is not on, my graphics starts to flicker every 5 min-ish (window theme turns off and then turns quickly back on); after a few flickering, the window theme will disappear, and the screen becomes weird - my chrome window will not fresh, or show blank boxes etc. If I disconnect the DVI connector to the TV (just use the LG+Dell dual-display), flickering and crash will not appear. I want to mention that, when I connect the computer to all 3 displays, I was actually able to get video output to all displays (I used arandr to configure them). I can even get 4k output to the 4k TV at 30Hz. I can't find a useful log entry when the flicking or graphics crash happens. I can only see a "CPU pipe A FIFO underrun" for pipe A/B/F (log attached at the end), but I can see many similar errors in my log and the appearance is not correlated to the flickering/crash. The "pipe A FIFO underrun" issue was previously reported in Bug#1550779. I also see "intel(0): HDMI max TMDS frequency 30KHz" entry in my Xorg.0.log file constantly, I also do not see an consistent mapping between the log entry and the flickering. Can anyone tell me how to properly debug this? what can I do to get a log for what was wrong? --- [ 145.033055] WARNING: CPU: 2 PID: 1804 at /build/linux-lts-xenial-drAJVo/linux-lts-xenial-4.4.0/ubuntu/i915/intel_pm.c:3675 skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo]() [ 145.033058] WARN_ON(!wm_changed) [ 145.033060] Modules linked in: nfsv3 pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) autofs4 rpcsec_gss_krb5 nfsv4 usblp joydev input_leds ti_usb_3410_5052 usbserial hid_generic gspca_ov534 gspca_main v4l2_common videodev media snd_usb_audio snd_usbmidi_lib usbhid snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic nvidia_uvm(POE) uas usb_storage intel_rapl x86_pkg_temp_thermal intel_powerclamp mxm_wmi coretemp kvm_intel bnep kvm rfcomm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_intel snd_hda_codec snd_hda_core nvidia_drm(POE) nvidia_modeset(POE) snd_hwdep aesni_intel snd_pcm aes_x86_64 nvidia(POE) lrw gf128mul snd_seq_midi snd_seq_midi_event glue_helper ablk_helper snd_rawmidi cryptd snd_seq snd_seq_device snd_timer serio_raw snd soundcore nfsd i915_bpo auth_rpcgss nfs_acl nfs binfmt_misc lockd grace 8250_fintek hci_uart sunrpc intel_ips drm_kms_helper btbcm pinctrl_sunrisepoint btqca fscache pinctrl_intel btintel intel_lpss_ac pi bluetooth i2c_hid intel_lpss drm hid video i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt shpchp mei_me mei mac_hid acpi_als wmi kfifo_buf industrialio acpi_pad parport_pc ppdev lp parport e1000e psmouse ptp pps_core ahci nvme libahci fjes [ 145.033284] CPU: 2 PID: 1804 Comm: Xorg Tainted: PW OE 4.4.0-66-generic #87~14.04.1-Ubuntu [ 145.033287] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z170 Extreme4, BIOS P7.00 09/09/2016 [ 145.033290] 88086e5879a0 813dc80c 88086e5879e8 [ 145.033295] c0556700 88086e5879d8 8107e9d6 88086d898000 [ 145.033300] 88086d89b000 0004 880871924b78 88086e587a64 [ 145.033305] Call Trace: [ 145.033311] [] dump_stack+0x63/0x87 [ 145.033317] [] warn_slowpath_common+0x86/0xc0 [ 145.033323] [] warn_slowpath_fmt+0x4c/0x50 [ 145.033358] [] ? ironlake_irq_handler+0x660/0xba0 [i915_bpo] [ 145.033393] [] skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo] [ 145.033435] [] skl_update_wm+0x19a/0x6f0 [i915_bpo] [ 145.033491] [] ? chv_write8+0x390/0x390 [i915_bpo] [ 145.033551] [] ? skl_ddi_pll_disable+0x70/0x80 [i915_bpo] [ 145.033590] [] intel_update_watermarks+0x1e/0x30 [i915_bpo] [ 145.033649] [] intel_atomic_commit+0x432/0x1440 [i915_bpo] [ 145.033688] [] ? drm_
[Kernel-packages] [Bug 1675204] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1675204/+attachment/4842942/+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/1675204 Title: Intel HD graphics crashes when connecting to 3 outputs (DVI+HDMI+DP) Status in linux package in Ubuntu: Confirmed Bug description: I have a very strange issue related to Intel graphics drivers (i915) with 3 connected on-board displays. I have a Xubuntu (14.04 LTS with HWE on 4.4.0-66 kernel) desktop computer running on a i7-6700K processor and on-board graphics (Mobo: AsRock z170 extreme4). I connect it to 3 displays - a 3440x1400 LG display (via onboard DP port), a 1920x1200 Dell display (via on-board HDMI), and a Sony 4k TV (via onboard DVI and a DVI-to-HDMI adapter). If I just connect my desktop to the first two displays (not the TV), everything works fine (except some minor issues). However, if I connect the 4k TV, even the TV is not on, my graphics starts to flicker every 5 min-ish (window theme turns off and then turns quickly back on); after a few flickering, the window theme will disappear, and the screen becomes weird - my chrome window will not fresh, or show blank boxes etc. If I disconnect the DVI connector to the TV (just use the LG+Dell dual-display), flickering and crash will not appear. I want to mention that, when I connect the computer to all 3 displays, I was actually able to get video output to all displays (I used arandr to configure them). I can even get 4k output to the 4k TV at 30Hz. I can't find a useful log entry when the flicking or graphics crash happens. I can only see a "CPU pipe A FIFO underrun" for pipe A/B/F (log attached at the end), but I can see many similar errors in my log and the appearance is not correlated to the flickering/crash. The "pipe A FIFO underrun" issue was previously reported in Bug#1550779. I also see "intel(0): HDMI max TMDS frequency 30KHz" entry in my Xorg.0.log file constantly, I also do not see an consistent mapping between the log entry and the flickering. Can anyone tell me how to properly debug this? what can I do to get a log for what was wrong? --- [ 145.033055] WARNING: CPU: 2 PID: 1804 at /build/linux-lts-xenial-drAJVo/linux-lts-xenial-4.4.0/ubuntu/i915/intel_pm.c:3675 skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo]() [ 145.033058] WARN_ON(!wm_changed) [ 145.033060] Modules linked in: nfsv3 pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) autofs4 rpcsec_gss_krb5 nfsv4 usblp joydev input_leds ti_usb_3410_5052 usbserial hid_generic gspca_ov534 gspca_main v4l2_common videodev media snd_usb_audio snd_usbmidi_lib usbhid snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic nvidia_uvm(POE) uas usb_storage intel_rapl x86_pkg_temp_thermal intel_powerclamp mxm_wmi coretemp kvm_intel bnep kvm rfcomm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_intel snd_hda_codec snd_hda_core nvidia_drm(POE) nvidia_modeset(POE) snd_hwdep aesni_intel snd_pcm aes_x86_64 nvidia(POE) lrw gf128mul snd_seq_midi snd_seq_midi_event glue_helper ablk_helper snd_rawmidi cryptd snd_seq snd_seq_device snd_timer serio_raw snd soundcore nfsd i915_bpo auth_rpcgss nfs_acl nfs binfmt_misc lockd grace 8250_fintek hci_uart sunrpc intel_ips drm_kms_helper btbcm pinctrl_sunrisepoint btqca fscache pinctrl_intel btintel intel_lpss_ac pi bluetooth i2c_hid intel_lpss drm hid video i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt shpchp mei_me mei mac_hid acpi_als wmi kfifo_buf industrialio acpi_pad parport_pc ppdev lp parport e1000e psmouse ptp pps_core ahci nvme libahci fjes [ 145.033284] CPU: 2 PID: 1804 Comm: Xorg Tainted: PW OE 4.4.0-66-generic #87~14.04.1-Ubuntu [ 145.033287] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z170 Extreme4, BIOS P7.00 09/09/2016 [ 145.033290] 88086e5879a0 813dc80c 88086e5879e8 [ 145.033295] c0556700 88086e5879d8 8107e9d6 88086d898000 [ 145.033300] 88086d89b000 0004 880871924b78 88086e587a64 [ 145.033305] Call Trace: [ 145.033311] [] dump_stack+0x63/0x87 [ 145.033317] [] warn_slowpath_common+0x86/0xc0 [ 145.033323] [] warn_slowpath_fmt+0x4c/0x50 [ 145.033358] [] ? ironlake_irq_handler+0x660/0xba0 [i915_bpo] [ 145.033393] [] skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo] [ 145.033435] [] skl_update_wm+0x19a/0x6f0 [i915_bpo] [ 145.033491] [] ? chv_write8+0x390/0x390 [i915_bpo] [ 145.033551] [] ? skl_ddi_pll_disable+0x70/0x80 [i915_bpo] [ 145.033590] [] intel_update_watermarks+0x1e/0x30 [i915_bpo] [ 145.033649] [] intel_atomic_commit+0x432/0x1440 [i915_bpo] [ 145.033688] [] ? drm_
[Kernel-packages] [Bug 1675204] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1675204/+attachment/4842925/+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/1675204 Title: Intel HD graphics crashes when connecting to 3 outputs (DVI+HDMI+DP) Status in linux package in Ubuntu: Confirmed Bug description: I have a very strange issue related to Intel graphics drivers (i915) with 3 connected on-board displays. I have a Xubuntu (14.04 LTS with HWE on 4.4.0-66 kernel) desktop computer running on a i7-6700K processor and on-board graphics (Mobo: AsRock z170 extreme4). I connect it to 3 displays - a 3440x1400 LG display (via onboard DP port), a 1920x1200 Dell display (via on-board HDMI), and a Sony 4k TV (via onboard DVI and a DVI-to-HDMI adapter). If I just connect my desktop to the first two displays (not the TV), everything works fine (except some minor issues). However, if I connect the 4k TV, even the TV is not on, my graphics starts to flicker every 5 min-ish (window theme turns off and then turns quickly back on); after a few flickering, the window theme will disappear, and the screen becomes weird - my chrome window will not fresh, or show blank boxes etc. If I disconnect the DVI connector to the TV (just use the LG+Dell dual-display), flickering and crash will not appear. I want to mention that, when I connect the computer to all 3 displays, I was actually able to get video output to all displays (I used arandr to configure them). I can even get 4k output to the 4k TV at 30Hz. I can't find a useful log entry when the flicking or graphics crash happens. I can only see a "CPU pipe A FIFO underrun" for pipe A/B/F (log attached at the end), but I can see many similar errors in my log and the appearance is not correlated to the flickering/crash. The "pipe A FIFO underrun" issue was previously reported in Bug#1550779. I also see "intel(0): HDMI max TMDS frequency 30KHz" entry in my Xorg.0.log file constantly, I also do not see an consistent mapping between the log entry and the flickering. Can anyone tell me how to properly debug this? what can I do to get a log for what was wrong? --- [ 145.033055] WARNING: CPU: 2 PID: 1804 at /build/linux-lts-xenial-drAJVo/linux-lts-xenial-4.4.0/ubuntu/i915/intel_pm.c:3675 skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo]() [ 145.033058] WARN_ON(!wm_changed) [ 145.033060] Modules linked in: nfsv3 pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) autofs4 rpcsec_gss_krb5 nfsv4 usblp joydev input_leds ti_usb_3410_5052 usbserial hid_generic gspca_ov534 gspca_main v4l2_common videodev media snd_usb_audio snd_usbmidi_lib usbhid snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic nvidia_uvm(POE) uas usb_storage intel_rapl x86_pkg_temp_thermal intel_powerclamp mxm_wmi coretemp kvm_intel bnep kvm rfcomm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_intel snd_hda_codec snd_hda_core nvidia_drm(POE) nvidia_modeset(POE) snd_hwdep aesni_intel snd_pcm aes_x86_64 nvidia(POE) lrw gf128mul snd_seq_midi snd_seq_midi_event glue_helper ablk_helper snd_rawmidi cryptd snd_seq snd_seq_device snd_timer serio_raw snd soundcore nfsd i915_bpo auth_rpcgss nfs_acl nfs binfmt_misc lockd grace 8250_fintek hci_uart sunrpc intel_ips drm_kms_helper btbcm pinctrl_sunrisepoint btqca fscache pinctrl_intel btintel intel_lpss_ac pi bluetooth i2c_hid intel_lpss drm hid video i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt shpchp mei_me mei mac_hid acpi_als wmi kfifo_buf industrialio acpi_pad parport_pc ppdev lp parport e1000e psmouse ptp pps_core ahci nvme libahci fjes [ 145.033284] CPU: 2 PID: 1804 Comm: Xorg Tainted: PW OE 4.4.0-66-generic #87~14.04.1-Ubuntu [ 145.033287] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z170 Extreme4, BIOS P7.00 09/09/2016 [ 145.033290] 88086e5879a0 813dc80c 88086e5879e8 [ 145.033295] c0556700 88086e5879d8 8107e9d6 88086d898000 [ 145.033300] 88086d89b000 0004 880871924b78 88086e587a64 [ 145.033305] Call Trace: [ 145.033311] [] dump_stack+0x63/0x87 [ 145.033317] [] warn_slowpath_common+0x86/0xc0 [ 145.033323] [] warn_slowpath_fmt+0x4c/0x50 [ 145.033358] [] ? ironlake_irq_handler+0x660/0xba0 [i915_bpo] [ 145.033393] [] skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo] [ 145.033435] [] skl_update_wm+0x19a/0x6f0 [i915_bpo] [ 145.033491] [] ? chv_write8+0x390/0x390 [i915_bpo] [ 145.033551] [] ? skl_ddi_pll_disable+0x70/0x80 [i915_bpo] [ 145.033590] [] intel_update_watermarks+0x1e/0x30 [i915_bpo] [ 145.033649] [] intel_atomic_commit+0x432/0x1440 [i915_bpo] [ 145.033688] [] ? drm_
[Kernel-packages] [Bug 1675204] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1675204/+attachment/4842928/+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/1675204 Title: Intel HD graphics crashes when connecting to 3 outputs (DVI+HDMI+DP) Status in linux package in Ubuntu: Confirmed Bug description: I have a very strange issue related to Intel graphics drivers (i915) with 3 connected on-board displays. I have a Xubuntu (14.04 LTS with HWE on 4.4.0-66 kernel) desktop computer running on a i7-6700K processor and on-board graphics (Mobo: AsRock z170 extreme4). I connect it to 3 displays - a 3440x1400 LG display (via onboard DP port), a 1920x1200 Dell display (via on-board HDMI), and a Sony 4k TV (via onboard DVI and a DVI-to-HDMI adapter). If I just connect my desktop to the first two displays (not the TV), everything works fine (except some minor issues). However, if I connect the 4k TV, even the TV is not on, my graphics starts to flicker every 5 min-ish (window theme turns off and then turns quickly back on); after a few flickering, the window theme will disappear, and the screen becomes weird - my chrome window will not fresh, or show blank boxes etc. If I disconnect the DVI connector to the TV (just use the LG+Dell dual-display), flickering and crash will not appear. I want to mention that, when I connect the computer to all 3 displays, I was actually able to get video output to all displays (I used arandr to configure them). I can even get 4k output to the 4k TV at 30Hz. I can't find a useful log entry when the flicking or graphics crash happens. I can only see a "CPU pipe A FIFO underrun" for pipe A/B/F (log attached at the end), but I can see many similar errors in my log and the appearance is not correlated to the flickering/crash. The "pipe A FIFO underrun" issue was previously reported in Bug#1550779. I also see "intel(0): HDMI max TMDS frequency 30KHz" entry in my Xorg.0.log file constantly, I also do not see an consistent mapping between the log entry and the flickering. Can anyone tell me how to properly debug this? what can I do to get a log for what was wrong? --- [ 145.033055] WARNING: CPU: 2 PID: 1804 at /build/linux-lts-xenial-drAJVo/linux-lts-xenial-4.4.0/ubuntu/i915/intel_pm.c:3675 skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo]() [ 145.033058] WARN_ON(!wm_changed) [ 145.033060] Modules linked in: nfsv3 pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) autofs4 rpcsec_gss_krb5 nfsv4 usblp joydev input_leds ti_usb_3410_5052 usbserial hid_generic gspca_ov534 gspca_main v4l2_common videodev media snd_usb_audio snd_usbmidi_lib usbhid snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic nvidia_uvm(POE) uas usb_storage intel_rapl x86_pkg_temp_thermal intel_powerclamp mxm_wmi coretemp kvm_intel bnep kvm rfcomm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_intel snd_hda_codec snd_hda_core nvidia_drm(POE) nvidia_modeset(POE) snd_hwdep aesni_intel snd_pcm aes_x86_64 nvidia(POE) lrw gf128mul snd_seq_midi snd_seq_midi_event glue_helper ablk_helper snd_rawmidi cryptd snd_seq snd_seq_device snd_timer serio_raw snd soundcore nfsd i915_bpo auth_rpcgss nfs_acl nfs binfmt_misc lockd grace 8250_fintek hci_uart sunrpc intel_ips drm_kms_helper btbcm pinctrl_sunrisepoint btqca fscache pinctrl_intel btintel intel_lpss_ac pi bluetooth i2c_hid intel_lpss drm hid video i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt shpchp mei_me mei mac_hid acpi_als wmi kfifo_buf industrialio acpi_pad parport_pc ppdev lp parport e1000e psmouse ptp pps_core ahci nvme libahci fjes [ 145.033284] CPU: 2 PID: 1804 Comm: Xorg Tainted: PW OE 4.4.0-66-generic #87~14.04.1-Ubuntu [ 145.033287] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z170 Extreme4, BIOS P7.00 09/09/2016 [ 145.033290] 88086e5879a0 813dc80c 88086e5879e8 [ 145.033295] c0556700 88086e5879d8 8107e9d6 88086d898000 [ 145.033300] 88086d89b000 0004 880871924b78 88086e587a64 [ 145.033305] Call Trace: [ 145.033311] [] dump_stack+0x63/0x87 [ 145.033317] [] warn_slowpath_common+0x86/0xc0 [ 145.033323] [] warn_slowpath_fmt+0x4c/0x50 [ 145.033358] [] ? ironlake_irq_handler+0x660/0xba0 [i915_bpo] [ 145.033393] [] skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo] [ 145.033435] [] skl_update_wm+0x19a/0x6f0 [i915_bpo] [ 145.033491] [] ? chv_write8+0x390/0x390 [i915_bpo] [ 145.033551] [] ? skl_ddi_pll_disable+0x70/0x80 [i915_bpo] [ 145.033590] [] intel_update_watermarks+0x1e/0x30 [i915_bpo] [ 145.033649] [] intel_atomic_commit+0x432/0x1440 [i915_bpo] [ 145.033688] [] ? drm_atom
[Kernel-packages] [Bug 1675204] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1675204/+attachment/4842936/+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/1675204 Title: Intel HD graphics crashes when connecting to 3 outputs (DVI+HDMI+DP) Status in linux package in Ubuntu: Confirmed Bug description: I have a very strange issue related to Intel graphics drivers (i915) with 3 connected on-board displays. I have a Xubuntu (14.04 LTS with HWE on 4.4.0-66 kernel) desktop computer running on a i7-6700K processor and on-board graphics (Mobo: AsRock z170 extreme4). I connect it to 3 displays - a 3440x1400 LG display (via onboard DP port), a 1920x1200 Dell display (via on-board HDMI), and a Sony 4k TV (via onboard DVI and a DVI-to-HDMI adapter). If I just connect my desktop to the first two displays (not the TV), everything works fine (except some minor issues). However, if I connect the 4k TV, even the TV is not on, my graphics starts to flicker every 5 min-ish (window theme turns off and then turns quickly back on); after a few flickering, the window theme will disappear, and the screen becomes weird - my chrome window will not fresh, or show blank boxes etc. If I disconnect the DVI connector to the TV (just use the LG+Dell dual-display), flickering and crash will not appear. I want to mention that, when I connect the computer to all 3 displays, I was actually able to get video output to all displays (I used arandr to configure them). I can even get 4k output to the 4k TV at 30Hz. I can't find a useful log entry when the flicking or graphics crash happens. I can only see a "CPU pipe A FIFO underrun" for pipe A/B/F (log attached at the end), but I can see many similar errors in my log and the appearance is not correlated to the flickering/crash. The "pipe A FIFO underrun" issue was previously reported in Bug#1550779. I also see "intel(0): HDMI max TMDS frequency 30KHz" entry in my Xorg.0.log file constantly, I also do not see an consistent mapping between the log entry and the flickering. Can anyone tell me how to properly debug this? what can I do to get a log for what was wrong? --- [ 145.033055] WARNING: CPU: 2 PID: 1804 at /build/linux-lts-xenial-drAJVo/linux-lts-xenial-4.4.0/ubuntu/i915/intel_pm.c:3675 skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo]() [ 145.033058] WARN_ON(!wm_changed) [ 145.033060] Modules linked in: nfsv3 pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) autofs4 rpcsec_gss_krb5 nfsv4 usblp joydev input_leds ti_usb_3410_5052 usbserial hid_generic gspca_ov534 gspca_main v4l2_common videodev media snd_usb_audio snd_usbmidi_lib usbhid snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic nvidia_uvm(POE) uas usb_storage intel_rapl x86_pkg_temp_thermal intel_powerclamp mxm_wmi coretemp kvm_intel bnep kvm rfcomm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_intel snd_hda_codec snd_hda_core nvidia_drm(POE) nvidia_modeset(POE) snd_hwdep aesni_intel snd_pcm aes_x86_64 nvidia(POE) lrw gf128mul snd_seq_midi snd_seq_midi_event glue_helper ablk_helper snd_rawmidi cryptd snd_seq snd_seq_device snd_timer serio_raw snd soundcore nfsd i915_bpo auth_rpcgss nfs_acl nfs binfmt_misc lockd grace 8250_fintek hci_uart sunrpc intel_ips drm_kms_helper btbcm pinctrl_sunrisepoint btqca fscache pinctrl_intel btintel intel_lpss_ac pi bluetooth i2c_hid intel_lpss drm hid video i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt shpchp mei_me mei mac_hid acpi_als wmi kfifo_buf industrialio acpi_pad parport_pc ppdev lp parport e1000e psmouse ptp pps_core ahci nvme libahci fjes [ 145.033284] CPU: 2 PID: 1804 Comm: Xorg Tainted: PW OE 4.4.0-66-generic #87~14.04.1-Ubuntu [ 145.033287] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z170 Extreme4, BIOS P7.00 09/09/2016 [ 145.033290] 88086e5879a0 813dc80c 88086e5879e8 [ 145.033295] c0556700 88086e5879d8 8107e9d6 88086d898000 [ 145.033300] 88086d89b000 0004 880871924b78 88086e587a64 [ 145.033305] Call Trace: [ 145.033311] [] dump_stack+0x63/0x87 [ 145.033317] [] warn_slowpath_common+0x86/0xc0 [ 145.033323] [] warn_slowpath_fmt+0x4c/0x50 [ 145.033358] [] ? ironlake_irq_handler+0x660/0xba0 [i915_bpo] [ 145.033393] [] skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo] [ 145.033435] [] skl_update_wm+0x19a/0x6f0 [i915_bpo] [ 145.033491] [] ? chv_write8+0x390/0x390 [i915_bpo] [ 145.033551] [] ? skl_ddi_pll_disable+0x70/0x80 [i915_bpo] [ 145.033590] [] intel_update_watermarks+0x1e/0x30 [i915_bpo] [ 145.033649] [] intel_atomic_commit+0x432/0x1440 [i915_bpo] [ 145.033688] [] ? dr
[Kernel-packages] [Bug 1675204] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1675204/+attachment/4842931/+files/WifiSyslog.txt ** Description changed: I have a very strange issue related to Intel graphics drivers (i915) with 3 connected on-board displays. I have a Xubuntu (14.04 LTS with HWE on 4.4.0-66 kernel) desktop computer running on a i7-6700K processor and on-board graphics (Mobo: AsRock z170 extreme4). I connect it to 3 displays - a 3440x1400 LG display (via onboard DP port), a 1920x1200 Dell display (via on-board HDMI), and a Sony 4k TV (via onboard DVI and a DVI-to-HDMI adapter). If I just connect my desktop to the first two displays (not the TV), everything works fine (except some minor issues). However, if I connect the 4k TV, even the TV is not on, my graphics starts to flicker every 5 min-ish (window theme turns off and then turns quickly back on); after a few flickering, the window theme will disappear, and the screen becomes weird - my chrome window will not fresh, or show blank boxes etc. If I disconnect the DVI connector to the TV (just use the LG+Dell dual- display), flickering and crash will not appear. I want to mention that, when I connect the computer to all 3 displays, I was actually able to get video output to all displays (I used arandr to configure them). I can even get 4k output to the 4k TV at 30Hz. I can't find a useful log entry when the flicking or graphics crash happens. I can only see a "CPU pipe A FIFO underrun" for pipe A/B/F (log attached at the end), but I can see many similar errors in my log and the appearance is not correlated to the flickering/crash. The "pipe A FIFO underrun" issue was previously reported in Bug#1550779. I also see "intel(0): HDMI max TMDS frequency 30KHz" entry in my Xorg.0.log file constantly, I also do not see an consistent mapping between the log entry and the flickering. Can anyone tell me how to properly debug this? what can I do to get a log for what was wrong? --- [ 145.033055] WARNING: CPU: 2 PID: 1804 at /build/linux-lts-xenial-drAJVo/linux-lts-xenial-4.4.0/ubuntu/i915/intel_pm.c:3675 skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo]() [ 145.033058] WARN_ON(!wm_changed) [ 145.033060] Modules linked in: nfsv3 pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) autofs4 rpcsec_gss_krb5 nfsv4 usblp joydev input_leds ti_usb_3410_5052 usbserial hid_generic gspca_ov534 gspca_main v4l2_common videodev media snd_usb_audio snd_usbmidi_lib usbhid snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic nvidia_uvm(POE) uas usb_storage intel_rapl x86_pkg_temp_thermal intel_powerclamp mxm_wmi coretemp kvm_intel bnep kvm rfcomm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_intel snd_hda_codec snd_hda_core nvidia_drm(POE) nvidia_modeset(POE) snd_hwdep aesni_intel snd_pcm aes_x86_64 nvidia(POE) lrw gf128mul snd_seq_midi snd_seq_midi_event glue_helper ablk_helper snd_rawmidi cryptd snd_seq snd_seq_device snd_timer serio_raw snd soundcore nfsd i915_bpo auth_rpcgss nfs_acl nfs binfmt_misc lockd grace 8250_fintek hci_uart sunrpc intel_ips drm_kms_helper btbcm pinctrl_sunrisepoint btqca fscache pinctrl_intel btintel intel_lpss_ac pi bluetooth i2c_hid intel_lpss drm hid video i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt shpchp mei_me mei mac_hid acpi_als wmi kfifo_buf industrialio acpi_pad parport_pc ppdev lp parport e1000e psmouse ptp pps_core ahci nvme libahci fjes [ 145.033284] CPU: 2 PID: 1804 Comm: Xorg Tainted: PW OE 4.4.0-66-generic #87~14.04.1-Ubuntu [ 145.033287] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z170 Extreme4, BIOS P7.00 09/09/2016 [ 145.033290] 88086e5879a0 813dc80c 88086e5879e8 [ 145.033295] c0556700 88086e5879d8 8107e9d6 88086d898000 [ 145.033300] 88086d89b000 0004 880871924b78 88086e587a64 [ 145.033305] Call Trace: [ 145.033311] [] dump_stack+0x63/0x87 [ 145.033317] [] warn_slowpath_common+0x86/0xc0 [ 145.033323] [] warn_slowpath_fmt+0x4c/0x50 [ 145.033358] [] ? ironlake_irq_handler+0x660/0xba0 [i915_bpo] [ 145.033393] [] skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo] [ 145.033435] [] skl_update_wm+0x19a/0x6f0 [i915_bpo] [ 145.033491] [] ? chv_write8+0x390/0x390 [i915_bpo] [ 145.033551] [] ? skl_ddi_pll_disable+0x70/0x80 [i915_bpo] [ 145.033590] [] intel_update_watermarks+0x1e/0x30 [i915_bpo] [ 145.033649] [] intel_atomic_commit+0x432/0x1440 [i915_bpo] [ 145.033688] [] ? drm_atomic_set_crtc_for_connector+0x44/0xf0 [drm] [ 145.033720] [] drm_atomic_commit+0x37/0x60 [drm] [ 145.033743] [] drm_atomic_helper_set_config+0x77/0xb0 [drm_kms_helper] [ 145.033775] [] drm_mode_set_config_internal+0x64/0x100 [drm] [ 145.033805] [] d
[Kernel-packages] [Bug 1675204] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1675204/+attachment/4842924/+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/1675204 Title: Intel HD graphics crashes when connecting to 3 outputs (DVI+HDMI+DP) Status in linux package in Ubuntu: Confirmed Bug description: I have a very strange issue related to Intel graphics drivers (i915) with 3 connected on-board displays. I have a Xubuntu (14.04 LTS with HWE on 4.4.0-66 kernel) desktop computer running on a i7-6700K processor and on-board graphics (Mobo: AsRock z170 extreme4). I connect it to 3 displays - a 3440x1400 LG display (via onboard DP port), a 1920x1200 Dell display (via on-board HDMI), and a Sony 4k TV (via onboard DVI and a DVI-to-HDMI adapter). If I just connect my desktop to the first two displays (not the TV), everything works fine (except some minor issues). However, if I connect the 4k TV, even the TV is not on, my graphics starts to flicker every 5 min-ish (window theme turns off and then turns quickly back on); after a few flickering, the window theme will disappear, and the screen becomes weird - my chrome window will not fresh, or show blank boxes etc. If I disconnect the DVI connector to the TV (just use the LG+Dell dual-display), flickering and crash will not appear. I want to mention that, when I connect the computer to all 3 displays, I was actually able to get video output to all displays (I used arandr to configure them). I can even get 4k output to the 4k TV at 30Hz. I can't find a useful log entry when the flicking or graphics crash happens. I can only see a "CPU pipe A FIFO underrun" for pipe A/B/F (log attached at the end), but I can see many similar errors in my log and the appearance is not correlated to the flickering/crash. The "pipe A FIFO underrun" issue was previously reported in Bug#1550779. I also see "intel(0): HDMI max TMDS frequency 30KHz" entry in my Xorg.0.log file constantly, I also do not see an consistent mapping between the log entry and the flickering. Can anyone tell me how to properly debug this? what can I do to get a log for what was wrong? --- [ 145.033055] WARNING: CPU: 2 PID: 1804 at /build/linux-lts-xenial-drAJVo/linux-lts-xenial-4.4.0/ubuntu/i915/intel_pm.c:3675 skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo]() [ 145.033058] WARN_ON(!wm_changed) [ 145.033060] Modules linked in: nfsv3 pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) autofs4 rpcsec_gss_krb5 nfsv4 usblp joydev input_leds ti_usb_3410_5052 usbserial hid_generic gspca_ov534 gspca_main v4l2_common videodev media snd_usb_audio snd_usbmidi_lib usbhid snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic nvidia_uvm(POE) uas usb_storage intel_rapl x86_pkg_temp_thermal intel_powerclamp mxm_wmi coretemp kvm_intel bnep kvm rfcomm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_intel snd_hda_codec snd_hda_core nvidia_drm(POE) nvidia_modeset(POE) snd_hwdep aesni_intel snd_pcm aes_x86_64 nvidia(POE) lrw gf128mul snd_seq_midi snd_seq_midi_event glue_helper ablk_helper snd_rawmidi cryptd snd_seq snd_seq_device snd_timer serio_raw snd soundcore nfsd i915_bpo auth_rpcgss nfs_acl nfs binfmt_misc lockd grace 8250_fintek hci_uart sunrpc intel_ips drm_kms_helper btbcm pinctrl_sunrisepoint btqca fscache pinctrl_intel btintel intel_lpss_ac pi bluetooth i2c_hid intel_lpss drm hid video i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt shpchp mei_me mei mac_hid acpi_als wmi kfifo_buf industrialio acpi_pad parport_pc ppdev lp parport e1000e psmouse ptp pps_core ahci nvme libahci fjes [ 145.033284] CPU: 2 PID: 1804 Comm: Xorg Tainted: PW OE 4.4.0-66-generic #87~14.04.1-Ubuntu [ 145.033287] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z170 Extreme4, BIOS P7.00 09/09/2016 [ 145.033290] 88086e5879a0 813dc80c 88086e5879e8 [ 145.033295] c0556700 88086e5879d8 8107e9d6 88086d898000 [ 145.033300] 88086d89b000 0004 880871924b78 88086e587a64 [ 145.033305] Call Trace: [ 145.033311] [] dump_stack+0x63/0x87 [ 145.033317] [] warn_slowpath_common+0x86/0xc0 [ 145.033323] [] warn_slowpath_fmt+0x4c/0x50 [ 145.033358] [] ? ironlake_irq_handler+0x660/0xba0 [i915_bpo] [ 145.033393] [] skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo] [ 145.033435] [] skl_update_wm+0x19a/0x6f0 [i915_bpo] [ 145.033491] [] ? chv_write8+0x390/0x390 [i915_bpo] [ 145.033551] [] ? skl_ddi_pll_disable+0x70/0x80 [i915_bpo] [ 145.033590] [] intel_update_watermarks+0x1e/0x30 [i915_bpo] [ 145.033649] [] intel_atomic_commit+0x432/0x1440 [i915_bpo] [ 145.033688] [] ? drm_
[Kernel-packages] [Bug 1675204] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1675204/+attachment/4842933/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1675204 Title: Intel HD graphics crashes when connecting to 3 outputs (DVI+HDMI+DP) Status in linux package in Ubuntu: Confirmed Bug description: I have a very strange issue related to Intel graphics drivers (i915) with 3 connected on-board displays. I have a Xubuntu (14.04 LTS with HWE on 4.4.0-66 kernel) desktop computer running on a i7-6700K processor and on-board graphics (Mobo: AsRock z170 extreme4). I connect it to 3 displays - a 3440x1400 LG display (via onboard DP port), a 1920x1200 Dell display (via on-board HDMI), and a Sony 4k TV (via onboard DVI and a DVI-to-HDMI adapter). If I just connect my desktop to the first two displays (not the TV), everything works fine (except some minor issues). However, if I connect the 4k TV, even the TV is not on, my graphics starts to flicker every 5 min-ish (window theme turns off and then turns quickly back on); after a few flickering, the window theme will disappear, and the screen becomes weird - my chrome window will not fresh, or show blank boxes etc. If I disconnect the DVI connector to the TV (just use the LG+Dell dual-display), flickering and crash will not appear. I want to mention that, when I connect the computer to all 3 displays, I was actually able to get video output to all displays (I used arandr to configure them). I can even get 4k output to the 4k TV at 30Hz. I can't find a useful log entry when the flicking or graphics crash happens. I can only see a "CPU pipe A FIFO underrun" for pipe A/B/F (log attached at the end), but I can see many similar errors in my log and the appearance is not correlated to the flickering/crash. The "pipe A FIFO underrun" issue was previously reported in Bug#1550779. I also see "intel(0): HDMI max TMDS frequency 30KHz" entry in my Xorg.0.log file constantly, I also do not see an consistent mapping between the log entry and the flickering. Can anyone tell me how to properly debug this? what can I do to get a log for what was wrong? --- [ 145.033055] WARNING: CPU: 2 PID: 1804 at /build/linux-lts-xenial-drAJVo/linux-lts-xenial-4.4.0/ubuntu/i915/intel_pm.c:3675 skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo]() [ 145.033058] WARN_ON(!wm_changed) [ 145.033060] Modules linked in: nfsv3 pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) autofs4 rpcsec_gss_krb5 nfsv4 usblp joydev input_leds ti_usb_3410_5052 usbserial hid_generic gspca_ov534 gspca_main v4l2_common videodev media snd_usb_audio snd_usbmidi_lib usbhid snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic nvidia_uvm(POE) uas usb_storage intel_rapl x86_pkg_temp_thermal intel_powerclamp mxm_wmi coretemp kvm_intel bnep kvm rfcomm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_intel snd_hda_codec snd_hda_core nvidia_drm(POE) nvidia_modeset(POE) snd_hwdep aesni_intel snd_pcm aes_x86_64 nvidia(POE) lrw gf128mul snd_seq_midi snd_seq_midi_event glue_helper ablk_helper snd_rawmidi cryptd snd_seq snd_seq_device snd_timer serio_raw snd soundcore nfsd i915_bpo auth_rpcgss nfs_acl nfs binfmt_misc lockd grace 8250_fintek hci_uart sunrpc intel_ips drm_kms_helper btbcm pinctrl_sunrisepoint btqca fscache pinctrl_intel btintel intel_lpss_ac pi bluetooth i2c_hid intel_lpss drm hid video i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt shpchp mei_me mei mac_hid acpi_als wmi kfifo_buf industrialio acpi_pad parport_pc ppdev lp parport e1000e psmouse ptp pps_core ahci nvme libahci fjes [ 145.033284] CPU: 2 PID: 1804 Comm: Xorg Tainted: PW OE 4.4.0-66-generic #87~14.04.1-Ubuntu [ 145.033287] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z170 Extreme4, BIOS P7.00 09/09/2016 [ 145.033290] 88086e5879a0 813dc80c 88086e5879e8 [ 145.033295] c0556700 88086e5879d8 8107e9d6 88086d898000 [ 145.033300] 88086d89b000 0004 880871924b78 88086e587a64 [ 145.033305] Call Trace: [ 145.033311] [] dump_stack+0x63/0x87 [ 145.033317] [] warn_slowpath_common+0x86/0xc0 [ 145.033323] [] warn_slowpath_fmt+0x4c/0x50 [ 145.033358] [] ? ironlake_irq_handler+0x660/0xba0 [i915_bpo] [ 145.033393] [] skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo] [ 145.033435] [] skl_update_wm+0x19a/0x6f0 [i915_bpo] [ 145.033491] [] ? chv_write8+0x390/0x390 [i915_bpo] [ 145.033551] [] ? skl_ddi_pll_disable+0x70/0x80 [i915_bpo] [ 145.033590] [] intel_update_watermarks+0x1e/0x30 [i915_bpo] [ 145.033649] [] intel_atomic_commit+0x432/0x1440 [i915_bpo] [ 145.033688] [] ? drm_atomic
[Kernel-packages] [Bug 1675204] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1675204/+attachment/4842944/+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/1675204 Title: Intel HD graphics crashes when connecting to 3 outputs (DVI+HDMI+DP) Status in linux package in Ubuntu: Confirmed Bug description: I have a very strange issue related to Intel graphics drivers (i915) with 3 connected on-board displays. I have a Xubuntu (14.04 LTS with HWE on 4.4.0-66 kernel) desktop computer running on a i7-6700K processor and on-board graphics (Mobo: AsRock z170 extreme4). I connect it to 3 displays - a 3440x1400 LG display (via onboard DP port), a 1920x1200 Dell display (via on-board HDMI), and a Sony 4k TV (via onboard DVI and a DVI-to-HDMI adapter). If I just connect my desktop to the first two displays (not the TV), everything works fine (except some minor issues). However, if I connect the 4k TV, even the TV is not on, my graphics starts to flicker every 5 min-ish (window theme turns off and then turns quickly back on); after a few flickering, the window theme will disappear, and the screen becomes weird - my chrome window will not fresh, or show blank boxes etc. If I disconnect the DVI connector to the TV (just use the LG+Dell dual-display), flickering and crash will not appear. I want to mention that, when I connect the computer to all 3 displays, I was actually able to get video output to all displays (I used arandr to configure them). I can even get 4k output to the 4k TV at 30Hz. I can't find a useful log entry when the flicking or graphics crash happens. I can only see a "CPU pipe A FIFO underrun" for pipe A/B/F (log attached at the end), but I can see many similar errors in my log and the appearance is not correlated to the flickering/crash. The "pipe A FIFO underrun" issue was previously reported in Bug#1550779. I also see "intel(0): HDMI max TMDS frequency 30KHz" entry in my Xorg.0.log file constantly, I also do not see an consistent mapping between the log entry and the flickering. Can anyone tell me how to properly debug this? what can I do to get a log for what was wrong? --- [ 145.033055] WARNING: CPU: 2 PID: 1804 at /build/linux-lts-xenial-drAJVo/linux-lts-xenial-4.4.0/ubuntu/i915/intel_pm.c:3675 skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo]() [ 145.033058] WARN_ON(!wm_changed) [ 145.033060] Modules linked in: nfsv3 pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) autofs4 rpcsec_gss_krb5 nfsv4 usblp joydev input_leds ti_usb_3410_5052 usbserial hid_generic gspca_ov534 gspca_main v4l2_common videodev media snd_usb_audio snd_usbmidi_lib usbhid snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic nvidia_uvm(POE) uas usb_storage intel_rapl x86_pkg_temp_thermal intel_powerclamp mxm_wmi coretemp kvm_intel bnep kvm rfcomm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_intel snd_hda_codec snd_hda_core nvidia_drm(POE) nvidia_modeset(POE) snd_hwdep aesni_intel snd_pcm aes_x86_64 nvidia(POE) lrw gf128mul snd_seq_midi snd_seq_midi_event glue_helper ablk_helper snd_rawmidi cryptd snd_seq snd_seq_device snd_timer serio_raw snd soundcore nfsd i915_bpo auth_rpcgss nfs_acl nfs binfmt_misc lockd grace 8250_fintek hci_uart sunrpc intel_ips drm_kms_helper btbcm pinctrl_sunrisepoint btqca fscache pinctrl_intel btintel intel_lpss_ac pi bluetooth i2c_hid intel_lpss drm hid video i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt shpchp mei_me mei mac_hid acpi_als wmi kfifo_buf industrialio acpi_pad parport_pc ppdev lp parport e1000e psmouse ptp pps_core ahci nvme libahci fjes [ 145.033284] CPU: 2 PID: 1804 Comm: Xorg Tainted: PW OE 4.4.0-66-generic #87~14.04.1-Ubuntu [ 145.033287] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z170 Extreme4, BIOS P7.00 09/09/2016 [ 145.033290] 88086e5879a0 813dc80c 88086e5879e8 [ 145.033295] c0556700 88086e5879d8 8107e9d6 88086d898000 [ 145.033300] 88086d89b000 0004 880871924b78 88086e587a64 [ 145.033305] Call Trace: [ 145.033311] [] dump_stack+0x63/0x87 [ 145.033317] [] warn_slowpath_common+0x86/0xc0 [ 145.033323] [] warn_slowpath_fmt+0x4c/0x50 [ 145.033358] [] ? ironlake_irq_handler+0x660/0xba0 [i915_bpo] [ 145.033393] [] skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo] [ 145.033435] [] skl_update_wm+0x19a/0x6f0 [i915_bpo] [ 145.033491] [] ? chv_write8+0x390/0x390 [i915_bpo] [ 145.033551] [] ? skl_ddi_pll_disable+0x70/0x80 [i915_bpo] [ 145.033590] [] intel_update_watermarks+0x1e/0x30 [i915_bpo] [ 145.033649] [] intel_atomic_commit+0x432/0x1440 [i915_bpo] [ 145.033688] [] ? drm_atomic_set_
[Kernel-packages] [Bug 1675204] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1675204/+attachment/4842943/+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/1675204 Title: Intel HD graphics crashes when connecting to 3 outputs (DVI+HDMI+DP) Status in linux package in Ubuntu: Confirmed Bug description: I have a very strange issue related to Intel graphics drivers (i915) with 3 connected on-board displays. I have a Xubuntu (14.04 LTS with HWE on 4.4.0-66 kernel) desktop computer running on a i7-6700K processor and on-board graphics (Mobo: AsRock z170 extreme4). I connect it to 3 displays - a 3440x1400 LG display (via onboard DP port), a 1920x1200 Dell display (via on-board HDMI), and a Sony 4k TV (via onboard DVI and a DVI-to-HDMI adapter). If I just connect my desktop to the first two displays (not the TV), everything works fine (except some minor issues). However, if I connect the 4k TV, even the TV is not on, my graphics starts to flicker every 5 min-ish (window theme turns off and then turns quickly back on); after a few flickering, the window theme will disappear, and the screen becomes weird - my chrome window will not fresh, or show blank boxes etc. If I disconnect the DVI connector to the TV (just use the LG+Dell dual-display), flickering and crash will not appear. I want to mention that, when I connect the computer to all 3 displays, I was actually able to get video output to all displays (I used arandr to configure them). I can even get 4k output to the 4k TV at 30Hz. I can't find a useful log entry when the flicking or graphics crash happens. I can only see a "CPU pipe A FIFO underrun" for pipe A/B/F (log attached at the end), but I can see many similar errors in my log and the appearance is not correlated to the flickering/crash. The "pipe A FIFO underrun" issue was previously reported in Bug#1550779. I also see "intel(0): HDMI max TMDS frequency 30KHz" entry in my Xorg.0.log file constantly, I also do not see an consistent mapping between the log entry and the flickering. Can anyone tell me how to properly debug this? what can I do to get a log for what was wrong? --- [ 145.033055] WARNING: CPU: 2 PID: 1804 at /build/linux-lts-xenial-drAJVo/linux-lts-xenial-4.4.0/ubuntu/i915/intel_pm.c:3675 skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo]() [ 145.033058] WARN_ON(!wm_changed) [ 145.033060] Modules linked in: nfsv3 pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) autofs4 rpcsec_gss_krb5 nfsv4 usblp joydev input_leds ti_usb_3410_5052 usbserial hid_generic gspca_ov534 gspca_main v4l2_common videodev media snd_usb_audio snd_usbmidi_lib usbhid snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic nvidia_uvm(POE) uas usb_storage intel_rapl x86_pkg_temp_thermal intel_powerclamp mxm_wmi coretemp kvm_intel bnep kvm rfcomm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_intel snd_hda_codec snd_hda_core nvidia_drm(POE) nvidia_modeset(POE) snd_hwdep aesni_intel snd_pcm aes_x86_64 nvidia(POE) lrw gf128mul snd_seq_midi snd_seq_midi_event glue_helper ablk_helper snd_rawmidi cryptd snd_seq snd_seq_device snd_timer serio_raw snd soundcore nfsd i915_bpo auth_rpcgss nfs_acl nfs binfmt_misc lockd grace 8250_fintek hci_uart sunrpc intel_ips drm_kms_helper btbcm pinctrl_sunrisepoint btqca fscache pinctrl_intel btintel intel_lpss_ac pi bluetooth i2c_hid intel_lpss drm hid video i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt shpchp mei_me mei mac_hid acpi_als wmi kfifo_buf industrialio acpi_pad parport_pc ppdev lp parport e1000e psmouse ptp pps_core ahci nvme libahci fjes [ 145.033284] CPU: 2 PID: 1804 Comm: Xorg Tainted: PW OE 4.4.0-66-generic #87~14.04.1-Ubuntu [ 145.033287] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z170 Extreme4, BIOS P7.00 09/09/2016 [ 145.033290] 88086e5879a0 813dc80c 88086e5879e8 [ 145.033295] c0556700 88086e5879d8 8107e9d6 88086d898000 [ 145.033300] 88086d89b000 0004 880871924b78 88086e587a64 [ 145.033305] Call Trace: [ 145.033311] [] dump_stack+0x63/0x87 [ 145.033317] [] warn_slowpath_common+0x86/0xc0 [ 145.033323] [] warn_slowpath_fmt+0x4c/0x50 [ 145.033358] [] ? ironlake_irq_handler+0x660/0xba0 [i915_bpo] [ 145.033393] [] skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo] [ 145.033435] [] skl_update_wm+0x19a/0x6f0 [i915_bpo] [ 145.033491] [] ? chv_write8+0x390/0x390 [i915_bpo] [ 145.033551] [] ? skl_ddi_pll_disable+0x70/0x80 [i915_bpo] [ 145.033590] [] intel_update_watermarks+0x1e/0x30 [i915_bpo] [ 145.033649] [] intel_atomic_commit+0x432/0x1440 [i915_bpo] [ 145.033688] [] ? drm_atom
[Kernel-packages] [Bug 1675204] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1675204/+attachment/4842945/+files/UdevLog.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/1675204 Title: Intel HD graphics crashes when connecting to 3 outputs (DVI+HDMI+DP) Status in linux package in Ubuntu: Confirmed Bug description: I have a very strange issue related to Intel graphics drivers (i915) with 3 connected on-board displays. I have a Xubuntu (14.04 LTS with HWE on 4.4.0-66 kernel) desktop computer running on a i7-6700K processor and on-board graphics (Mobo: AsRock z170 extreme4). I connect it to 3 displays - a 3440x1400 LG display (via onboard DP port), a 1920x1200 Dell display (via on-board HDMI), and a Sony 4k TV (via onboard DVI and a DVI-to-HDMI adapter). If I just connect my desktop to the first two displays (not the TV), everything works fine (except some minor issues). However, if I connect the 4k TV, even the TV is not on, my graphics starts to flicker every 5 min-ish (window theme turns off and then turns quickly back on); after a few flickering, the window theme will disappear, and the screen becomes weird - my chrome window will not fresh, or show blank boxes etc. If I disconnect the DVI connector to the TV (just use the LG+Dell dual-display), flickering and crash will not appear. I want to mention that, when I connect the computer to all 3 displays, I was actually able to get video output to all displays (I used arandr to configure them). I can even get 4k output to the 4k TV at 30Hz. I can't find a useful log entry when the flicking or graphics crash happens. I can only see a "CPU pipe A FIFO underrun" for pipe A/B/F (log attached at the end), but I can see many similar errors in my log and the appearance is not correlated to the flickering/crash. The "pipe A FIFO underrun" issue was previously reported in Bug#1550779. I also see "intel(0): HDMI max TMDS frequency 30KHz" entry in my Xorg.0.log file constantly, I also do not see an consistent mapping between the log entry and the flickering. Can anyone tell me how to properly debug this? what can I do to get a log for what was wrong? --- [ 145.033055] WARNING: CPU: 2 PID: 1804 at /build/linux-lts-xenial-drAJVo/linux-lts-xenial-4.4.0/ubuntu/i915/intel_pm.c:3675 skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo]() [ 145.033058] WARN_ON(!wm_changed) [ 145.033060] Modules linked in: nfsv3 pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) autofs4 rpcsec_gss_krb5 nfsv4 usblp joydev input_leds ti_usb_3410_5052 usbserial hid_generic gspca_ov534 gspca_main v4l2_common videodev media snd_usb_audio snd_usbmidi_lib usbhid snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic nvidia_uvm(POE) uas usb_storage intel_rapl x86_pkg_temp_thermal intel_powerclamp mxm_wmi coretemp kvm_intel bnep kvm rfcomm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_intel snd_hda_codec snd_hda_core nvidia_drm(POE) nvidia_modeset(POE) snd_hwdep aesni_intel snd_pcm aes_x86_64 nvidia(POE) lrw gf128mul snd_seq_midi snd_seq_midi_event glue_helper ablk_helper snd_rawmidi cryptd snd_seq snd_seq_device snd_timer serio_raw snd soundcore nfsd i915_bpo auth_rpcgss nfs_acl nfs binfmt_misc lockd grace 8250_fintek hci_uart sunrpc intel_ips drm_kms_helper btbcm pinctrl_sunrisepoint btqca fscache pinctrl_intel btintel intel_lpss_ac pi bluetooth i2c_hid intel_lpss drm hid video i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt shpchp mei_me mei mac_hid acpi_als wmi kfifo_buf industrialio acpi_pad parport_pc ppdev lp parport e1000e psmouse ptp pps_core ahci nvme libahci fjes [ 145.033284] CPU: 2 PID: 1804 Comm: Xorg Tainted: PW OE 4.4.0-66-generic #87~14.04.1-Ubuntu [ 145.033287] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z170 Extreme4, BIOS P7.00 09/09/2016 [ 145.033290] 88086e5879a0 813dc80c 88086e5879e8 [ 145.033295] c0556700 88086e5879d8 8107e9d6 88086d898000 [ 145.033300] 88086d89b000 0004 880871924b78 88086e587a64 [ 145.033305] Call Trace: [ 145.033311] [] dump_stack+0x63/0x87 [ 145.033317] [] warn_slowpath_common+0x86/0xc0 [ 145.033323] [] warn_slowpath_fmt+0x4c/0x50 [ 145.033358] [] ? ironlake_irq_handler+0x660/0xba0 [i915_bpo] [ 145.033393] [] skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo] [ 145.033435] [] skl_update_wm+0x19a/0x6f0 [i915_bpo] [ 145.033491] [] ? chv_write8+0x390/0x390 [i915_bpo] [ 145.033551] [] ? skl_ddi_pll_disable+0x70/0x80 [i915_bpo] [ 145.033590] [] intel_update_watermarks+0x1e/0x30 [i915_bpo] [ 145.033649] [] intel_atomic_commit+0x432/0x1440 [i915_bpo] [ 145.033688] [] ? drm_atomic_s
[Kernel-packages] [Bug 1675204] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1675204/+attachment/4842934/+files/BootDmesg.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/1675204 Title: Intel HD graphics crashes when connecting to 3 outputs (DVI+HDMI+DP) Status in linux package in Ubuntu: Confirmed Bug description: I have a very strange issue related to Intel graphics drivers (i915) with 3 connected on-board displays. I have a Xubuntu (14.04 LTS with HWE on 4.4.0-66 kernel) desktop computer running on a i7-6700K processor and on-board graphics (Mobo: AsRock z170 extreme4). I connect it to 3 displays - a 3440x1400 LG display (via onboard DP port), a 1920x1200 Dell display (via on-board HDMI), and a Sony 4k TV (via onboard DVI and a DVI-to-HDMI adapter). If I just connect my desktop to the first two displays (not the TV), everything works fine (except some minor issues). However, if I connect the 4k TV, even the TV is not on, my graphics starts to flicker every 5 min-ish (window theme turns off and then turns quickly back on); after a few flickering, the window theme will disappear, and the screen becomes weird - my chrome window will not fresh, or show blank boxes etc. If I disconnect the DVI connector to the TV (just use the LG+Dell dual-display), flickering and crash will not appear. I want to mention that, when I connect the computer to all 3 displays, I was actually able to get video output to all displays (I used arandr to configure them). I can even get 4k output to the 4k TV at 30Hz. I can't find a useful log entry when the flicking or graphics crash happens. I can only see a "CPU pipe A FIFO underrun" for pipe A/B/F (log attached at the end), but I can see many similar errors in my log and the appearance is not correlated to the flickering/crash. The "pipe A FIFO underrun" issue was previously reported in Bug#1550779. I also see "intel(0): HDMI max TMDS frequency 30KHz" entry in my Xorg.0.log file constantly, I also do not see an consistent mapping between the log entry and the flickering. Can anyone tell me how to properly debug this? what can I do to get a log for what was wrong? --- [ 145.033055] WARNING: CPU: 2 PID: 1804 at /build/linux-lts-xenial-drAJVo/linux-lts-xenial-4.4.0/ubuntu/i915/intel_pm.c:3675 skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo]() [ 145.033058] WARN_ON(!wm_changed) [ 145.033060] Modules linked in: nfsv3 pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) autofs4 rpcsec_gss_krb5 nfsv4 usblp joydev input_leds ti_usb_3410_5052 usbserial hid_generic gspca_ov534 gspca_main v4l2_common videodev media snd_usb_audio snd_usbmidi_lib usbhid snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic nvidia_uvm(POE) uas usb_storage intel_rapl x86_pkg_temp_thermal intel_powerclamp mxm_wmi coretemp kvm_intel bnep kvm rfcomm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_intel snd_hda_codec snd_hda_core nvidia_drm(POE) nvidia_modeset(POE) snd_hwdep aesni_intel snd_pcm aes_x86_64 nvidia(POE) lrw gf128mul snd_seq_midi snd_seq_midi_event glue_helper ablk_helper snd_rawmidi cryptd snd_seq snd_seq_device snd_timer serio_raw snd soundcore nfsd i915_bpo auth_rpcgss nfs_acl nfs binfmt_misc lockd grace 8250_fintek hci_uart sunrpc intel_ips drm_kms_helper btbcm pinctrl_sunrisepoint btqca fscache pinctrl_intel btintel intel_lpss_ac pi bluetooth i2c_hid intel_lpss drm hid video i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt shpchp mei_me mei mac_hid acpi_als wmi kfifo_buf industrialio acpi_pad parport_pc ppdev lp parport e1000e psmouse ptp pps_core ahci nvme libahci fjes [ 145.033284] CPU: 2 PID: 1804 Comm: Xorg Tainted: PW OE 4.4.0-66-generic #87~14.04.1-Ubuntu [ 145.033287] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z170 Extreme4, BIOS P7.00 09/09/2016 [ 145.033290] 88086e5879a0 813dc80c 88086e5879e8 [ 145.033295] c0556700 88086e5879d8 8107e9d6 88086d898000 [ 145.033300] 88086d89b000 0004 880871924b78 88086e587a64 [ 145.033305] Call Trace: [ 145.033311] [] dump_stack+0x63/0x87 [ 145.033317] [] warn_slowpath_common+0x86/0xc0 [ 145.033323] [] warn_slowpath_fmt+0x4c/0x50 [ 145.033358] [] ? ironlake_irq_handler+0x660/0xba0 [i915_bpo] [ 145.033393] [] skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo] [ 145.033435] [] skl_update_wm+0x19a/0x6f0 [i915_bpo] [ 145.033491] [] ? chv_write8+0x390/0x390 [i915_bpo] [ 145.033551] [] ? skl_ddi_pll_disable+0x70/0x80 [i915_bpo] [ 145.033590] [] intel_update_watermarks+0x1e/0x30 [i915_bpo] [ 145.033649] [] intel_atomic_commit+0x432/0x1440 [i915_bpo] [ 145.033688] [] ? drm_atom
[Kernel-packages] [Bug 1675204] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1675204/+attachment/4842941/+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/1675204 Title: Intel HD graphics crashes when connecting to 3 outputs (DVI+HDMI+DP) Status in linux package in Ubuntu: Confirmed Bug description: I have a very strange issue related to Intel graphics drivers (i915) with 3 connected on-board displays. I have a Xubuntu (14.04 LTS with HWE on 4.4.0-66 kernel) desktop computer running on a i7-6700K processor and on-board graphics (Mobo: AsRock z170 extreme4). I connect it to 3 displays - a 3440x1400 LG display (via onboard DP port), a 1920x1200 Dell display (via on-board HDMI), and a Sony 4k TV (via onboard DVI and a DVI-to-HDMI adapter). If I just connect my desktop to the first two displays (not the TV), everything works fine (except some minor issues). However, if I connect the 4k TV, even the TV is not on, my graphics starts to flicker every 5 min-ish (window theme turns off and then turns quickly back on); after a few flickering, the window theme will disappear, and the screen becomes weird - my chrome window will not fresh, or show blank boxes etc. If I disconnect the DVI connector to the TV (just use the LG+Dell dual-display), flickering and crash will not appear. I want to mention that, when I connect the computer to all 3 displays, I was actually able to get video output to all displays (I used arandr to configure them). I can even get 4k output to the 4k TV at 30Hz. I can't find a useful log entry when the flicking or graphics crash happens. I can only see a "CPU pipe A FIFO underrun" for pipe A/B/F (log attached at the end), but I can see many similar errors in my log and the appearance is not correlated to the flickering/crash. The "pipe A FIFO underrun" issue was previously reported in Bug#1550779. I also see "intel(0): HDMI max TMDS frequency 30KHz" entry in my Xorg.0.log file constantly, I also do not see an consistent mapping between the log entry and the flickering. Can anyone tell me how to properly debug this? what can I do to get a log for what was wrong? --- [ 145.033055] WARNING: CPU: 2 PID: 1804 at /build/linux-lts-xenial-drAJVo/linux-lts-xenial-4.4.0/ubuntu/i915/intel_pm.c:3675 skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo]() [ 145.033058] WARN_ON(!wm_changed) [ 145.033060] Modules linked in: nfsv3 pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) autofs4 rpcsec_gss_krb5 nfsv4 usblp joydev input_leds ti_usb_3410_5052 usbserial hid_generic gspca_ov534 gspca_main v4l2_common videodev media snd_usb_audio snd_usbmidi_lib usbhid snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic nvidia_uvm(POE) uas usb_storage intel_rapl x86_pkg_temp_thermal intel_powerclamp mxm_wmi coretemp kvm_intel bnep kvm rfcomm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_intel snd_hda_codec snd_hda_core nvidia_drm(POE) nvidia_modeset(POE) snd_hwdep aesni_intel snd_pcm aes_x86_64 nvidia(POE) lrw gf128mul snd_seq_midi snd_seq_midi_event glue_helper ablk_helper snd_rawmidi cryptd snd_seq snd_seq_device snd_timer serio_raw snd soundcore nfsd i915_bpo auth_rpcgss nfs_acl nfs binfmt_misc lockd grace 8250_fintek hci_uart sunrpc intel_ips drm_kms_helper btbcm pinctrl_sunrisepoint btqca fscache pinctrl_intel btintel intel_lpss_ac pi bluetooth i2c_hid intel_lpss drm hid video i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt shpchp mei_me mei mac_hid acpi_als wmi kfifo_buf industrialio acpi_pad parport_pc ppdev lp parport e1000e psmouse ptp pps_core ahci nvme libahci fjes [ 145.033284] CPU: 2 PID: 1804 Comm: Xorg Tainted: PW OE 4.4.0-66-generic #87~14.04.1-Ubuntu [ 145.033287] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z170 Extreme4, BIOS P7.00 09/09/2016 [ 145.033290] 88086e5879a0 813dc80c 88086e5879e8 [ 145.033295] c0556700 88086e5879d8 8107e9d6 88086d898000 [ 145.033300] 88086d89b000 0004 880871924b78 88086e587a64 [ 145.033305] Call Trace: [ 145.033311] [] dump_stack+0x63/0x87 [ 145.033317] [] warn_slowpath_common+0x86/0xc0 [ 145.033323] [] warn_slowpath_fmt+0x4c/0x50 [ 145.033358] [] ? ironlake_irq_handler+0x660/0xba0 [i915_bpo] [ 145.033393] [] skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo] [ 145.033435] [] skl_update_wm+0x19a/0x6f0 [i915_bpo] [ 145.033491] [] ? chv_write8+0x390/0x390 [i915_bpo] [ 145.033551] [] ? skl_ddi_pll_disable+0x70/0x80 [i915_bpo] [ 145.033590] [] intel_update_watermarks+0x1e/0x30 [i915_bpo] [ 145.033649] [] intel_atomic_commit+0x432/0x1440 [i915_bpo] [ 145.033688] [] ?
[Kernel-packages] [Bug 1675204] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1675204/+attachment/4842927/+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/1675204 Title: Intel HD graphics crashes when connecting to 3 outputs (DVI+HDMI+DP) Status in linux package in Ubuntu: Confirmed Bug description: I have a very strange issue related to Intel graphics drivers (i915) with 3 connected on-board displays. I have a Xubuntu (14.04 LTS with HWE on 4.4.0-66 kernel) desktop computer running on a i7-6700K processor and on-board graphics (Mobo: AsRock z170 extreme4). I connect it to 3 displays - a 3440x1400 LG display (via onboard DP port), a 1920x1200 Dell display (via on-board HDMI), and a Sony 4k TV (via onboard DVI and a DVI-to-HDMI adapter). If I just connect my desktop to the first two displays (not the TV), everything works fine (except some minor issues). However, if I connect the 4k TV, even the TV is not on, my graphics starts to flicker every 5 min-ish (window theme turns off and then turns quickly back on); after a few flickering, the window theme will disappear, and the screen becomes weird - my chrome window will not fresh, or show blank boxes etc. If I disconnect the DVI connector to the TV (just use the LG+Dell dual-display), flickering and crash will not appear. I want to mention that, when I connect the computer to all 3 displays, I was actually able to get video output to all displays (I used arandr to configure them). I can even get 4k output to the 4k TV at 30Hz. I can't find a useful log entry when the flicking or graphics crash happens. I can only see a "CPU pipe A FIFO underrun" for pipe A/B/F (log attached at the end), but I can see many similar errors in my log and the appearance is not correlated to the flickering/crash. The "pipe A FIFO underrun" issue was previously reported in Bug#1550779. I also see "intel(0): HDMI max TMDS frequency 30KHz" entry in my Xorg.0.log file constantly, I also do not see an consistent mapping between the log entry and the flickering. Can anyone tell me how to properly debug this? what can I do to get a log for what was wrong? --- [ 145.033055] WARNING: CPU: 2 PID: 1804 at /build/linux-lts-xenial-drAJVo/linux-lts-xenial-4.4.0/ubuntu/i915/intel_pm.c:3675 skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo]() [ 145.033058] WARN_ON(!wm_changed) [ 145.033060] Modules linked in: nfsv3 pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) autofs4 rpcsec_gss_krb5 nfsv4 usblp joydev input_leds ti_usb_3410_5052 usbserial hid_generic gspca_ov534 gspca_main v4l2_common videodev media snd_usb_audio snd_usbmidi_lib usbhid snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic nvidia_uvm(POE) uas usb_storage intel_rapl x86_pkg_temp_thermal intel_powerclamp mxm_wmi coretemp kvm_intel bnep kvm rfcomm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_intel snd_hda_codec snd_hda_core nvidia_drm(POE) nvidia_modeset(POE) snd_hwdep aesni_intel snd_pcm aes_x86_64 nvidia(POE) lrw gf128mul snd_seq_midi snd_seq_midi_event glue_helper ablk_helper snd_rawmidi cryptd snd_seq snd_seq_device snd_timer serio_raw snd soundcore nfsd i915_bpo auth_rpcgss nfs_acl nfs binfmt_misc lockd grace 8250_fintek hci_uart sunrpc intel_ips drm_kms_helper btbcm pinctrl_sunrisepoint btqca fscache pinctrl_intel btintel intel_lpss_ac pi bluetooth i2c_hid intel_lpss drm hid video i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt shpchp mei_me mei mac_hid acpi_als wmi kfifo_buf industrialio acpi_pad parport_pc ppdev lp parport e1000e psmouse ptp pps_core ahci nvme libahci fjes [ 145.033284] CPU: 2 PID: 1804 Comm: Xorg Tainted: PW OE 4.4.0-66-generic #87~14.04.1-Ubuntu [ 145.033287] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z170 Extreme4, BIOS P7.00 09/09/2016 [ 145.033290] 88086e5879a0 813dc80c 88086e5879e8 [ 145.033295] c0556700 88086e5879d8 8107e9d6 88086d898000 [ 145.033300] 88086d89b000 0004 880871924b78 88086e587a64 [ 145.033305] Call Trace: [ 145.033311] [] dump_stack+0x63/0x87 [ 145.033317] [] warn_slowpath_common+0x86/0xc0 [ 145.033323] [] warn_slowpath_fmt+0x4c/0x50 [ 145.033358] [] ? ironlake_irq_handler+0x660/0xba0 [i915_bpo] [ 145.033393] [] skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo] [ 145.033435] [] skl_update_wm+0x19a/0x6f0 [i915_bpo] [ 145.033491] [] ? chv_write8+0x390/0x390 [i915_bpo] [ 145.033551] [] ? skl_ddi_pll_disable+0x70/0x80 [i915_bpo] [ 145.033590] [] intel_update_watermarks+0x1e/0x30 [i915_bpo] [ 145.033649] [] intel_atomic_commit+0x432/0x1440 [i915_bpo] [ 145.033688] [] ? drm_
[Kernel-packages] [Bug 1675204] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1675204/+attachment/4842937/+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/1675204 Title: Intel HD graphics crashes when connecting to 3 outputs (DVI+HDMI+DP) Status in linux package in Ubuntu: Confirmed Bug description: I have a very strange issue related to Intel graphics drivers (i915) with 3 connected on-board displays. I have a Xubuntu (14.04 LTS with HWE on 4.4.0-66 kernel) desktop computer running on a i7-6700K processor and on-board graphics (Mobo: AsRock z170 extreme4). I connect it to 3 displays - a 3440x1400 LG display (via onboard DP port), a 1920x1200 Dell display (via on-board HDMI), and a Sony 4k TV (via onboard DVI and a DVI-to-HDMI adapter). If I just connect my desktop to the first two displays (not the TV), everything works fine (except some minor issues). However, if I connect the 4k TV, even the TV is not on, my graphics starts to flicker every 5 min-ish (window theme turns off and then turns quickly back on); after a few flickering, the window theme will disappear, and the screen becomes weird - my chrome window will not fresh, or show blank boxes etc. If I disconnect the DVI connector to the TV (just use the LG+Dell dual-display), flickering and crash will not appear. I want to mention that, when I connect the computer to all 3 displays, I was actually able to get video output to all displays (I used arandr to configure them). I can even get 4k output to the 4k TV at 30Hz. I can't find a useful log entry when the flicking or graphics crash happens. I can only see a "CPU pipe A FIFO underrun" for pipe A/B/F (log attached at the end), but I can see many similar errors in my log and the appearance is not correlated to the flickering/crash. The "pipe A FIFO underrun" issue was previously reported in Bug#1550779. I also see "intel(0): HDMI max TMDS frequency 30KHz" entry in my Xorg.0.log file constantly, I also do not see an consistent mapping between the log entry and the flickering. Can anyone tell me how to properly debug this? what can I do to get a log for what was wrong? --- [ 145.033055] WARNING: CPU: 2 PID: 1804 at /build/linux-lts-xenial-drAJVo/linux-lts-xenial-4.4.0/ubuntu/i915/intel_pm.c:3675 skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo]() [ 145.033058] WARN_ON(!wm_changed) [ 145.033060] Modules linked in: nfsv3 pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) autofs4 rpcsec_gss_krb5 nfsv4 usblp joydev input_leds ti_usb_3410_5052 usbserial hid_generic gspca_ov534 gspca_main v4l2_common videodev media snd_usb_audio snd_usbmidi_lib usbhid snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic nvidia_uvm(POE) uas usb_storage intel_rapl x86_pkg_temp_thermal intel_powerclamp mxm_wmi coretemp kvm_intel bnep kvm rfcomm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_intel snd_hda_codec snd_hda_core nvidia_drm(POE) nvidia_modeset(POE) snd_hwdep aesni_intel snd_pcm aes_x86_64 nvidia(POE) lrw gf128mul snd_seq_midi snd_seq_midi_event glue_helper ablk_helper snd_rawmidi cryptd snd_seq snd_seq_device snd_timer serio_raw snd soundcore nfsd i915_bpo auth_rpcgss nfs_acl nfs binfmt_misc lockd grace 8250_fintek hci_uart sunrpc intel_ips drm_kms_helper btbcm pinctrl_sunrisepoint btqca fscache pinctrl_intel btintel intel_lpss_ac pi bluetooth i2c_hid intel_lpss drm hid video i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt shpchp mei_me mei mac_hid acpi_als wmi kfifo_buf industrialio acpi_pad parport_pc ppdev lp parport e1000e psmouse ptp pps_core ahci nvme libahci fjes [ 145.033284] CPU: 2 PID: 1804 Comm: Xorg Tainted: PW OE 4.4.0-66-generic #87~14.04.1-Ubuntu [ 145.033287] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z170 Extreme4, BIOS P7.00 09/09/2016 [ 145.033290] 88086e5879a0 813dc80c 88086e5879e8 [ 145.033295] c0556700 88086e5879d8 8107e9d6 88086d898000 [ 145.033300] 88086d89b000 0004 880871924b78 88086e587a64 [ 145.033305] Call Trace: [ 145.033311] [] dump_stack+0x63/0x87 [ 145.033317] [] warn_slowpath_common+0x86/0xc0 [ 145.033323] [] warn_slowpath_fmt+0x4c/0x50 [ 145.033358] [] ? ironlake_irq_handler+0x660/0xba0 [i915_bpo] [ 145.033393] [] skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo] [ 145.033435] [] skl_update_wm+0x19a/0x6f0 [i915_bpo] [ 145.033491] [] ? chv_write8+0x390/0x390 [i915_bpo] [ 145.033551] [] ? skl_ddi_pll_disable+0x70/0x80 [i915_bpo] [ 145.033590] [] intel_update_watermarks+0x1e/0x30 [i915_bpo] [ 145.033649] [] intel_atomic_commit+0x432/0x1440 [i915_bpo] [ 145.033688] [] ? drm_atomic_set_cr
[Kernel-packages] [Bug 1675204] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1675204/+attachment/4842929/+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/1675204 Title: Intel HD graphics crashes when connecting to 3 outputs (DVI+HDMI+DP) Status in linux package in Ubuntu: Confirmed Bug description: I have a very strange issue related to Intel graphics drivers (i915) with 3 connected on-board displays. I have a Xubuntu (14.04 LTS with HWE on 4.4.0-66 kernel) desktop computer running on a i7-6700K processor and on-board graphics (Mobo: AsRock z170 extreme4). I connect it to 3 displays - a 3440x1400 LG display (via onboard DP port), a 1920x1200 Dell display (via on-board HDMI), and a Sony 4k TV (via onboard DVI and a DVI-to-HDMI adapter). If I just connect my desktop to the first two displays (not the TV), everything works fine (except some minor issues). However, if I connect the 4k TV, even the TV is not on, my graphics starts to flicker every 5 min-ish (window theme turns off and then turns quickly back on); after a few flickering, the window theme will disappear, and the screen becomes weird - my chrome window will not fresh, or show blank boxes etc. If I disconnect the DVI connector to the TV (just use the LG+Dell dual-display), flickering and crash will not appear. I want to mention that, when I connect the computer to all 3 displays, I was actually able to get video output to all displays (I used arandr to configure them). I can even get 4k output to the 4k TV at 30Hz. I can't find a useful log entry when the flicking or graphics crash happens. I can only see a "CPU pipe A FIFO underrun" for pipe A/B/F (log attached at the end), but I can see many similar errors in my log and the appearance is not correlated to the flickering/crash. The "pipe A FIFO underrun" issue was previously reported in Bug#1550779. I also see "intel(0): HDMI max TMDS frequency 30KHz" entry in my Xorg.0.log file constantly, I also do not see an consistent mapping between the log entry and the flickering. Can anyone tell me how to properly debug this? what can I do to get a log for what was wrong? --- [ 145.033055] WARNING: CPU: 2 PID: 1804 at /build/linux-lts-xenial-drAJVo/linux-lts-xenial-4.4.0/ubuntu/i915/intel_pm.c:3675 skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo]() [ 145.033058] WARN_ON(!wm_changed) [ 145.033060] Modules linked in: nfsv3 pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) autofs4 rpcsec_gss_krb5 nfsv4 usblp joydev input_leds ti_usb_3410_5052 usbserial hid_generic gspca_ov534 gspca_main v4l2_common videodev media snd_usb_audio snd_usbmidi_lib usbhid snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic nvidia_uvm(POE) uas usb_storage intel_rapl x86_pkg_temp_thermal intel_powerclamp mxm_wmi coretemp kvm_intel bnep kvm rfcomm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_intel snd_hda_codec snd_hda_core nvidia_drm(POE) nvidia_modeset(POE) snd_hwdep aesni_intel snd_pcm aes_x86_64 nvidia(POE) lrw gf128mul snd_seq_midi snd_seq_midi_event glue_helper ablk_helper snd_rawmidi cryptd snd_seq snd_seq_device snd_timer serio_raw snd soundcore nfsd i915_bpo auth_rpcgss nfs_acl nfs binfmt_misc lockd grace 8250_fintek hci_uart sunrpc intel_ips drm_kms_helper btbcm pinctrl_sunrisepoint btqca fscache pinctrl_intel btintel intel_lpss_ac pi bluetooth i2c_hid intel_lpss drm hid video i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt shpchp mei_me mei mac_hid acpi_als wmi kfifo_buf industrialio acpi_pad parport_pc ppdev lp parport e1000e psmouse ptp pps_core ahci nvme libahci fjes [ 145.033284] CPU: 2 PID: 1804 Comm: Xorg Tainted: PW OE 4.4.0-66-generic #87~14.04.1-Ubuntu [ 145.033287] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z170 Extreme4, BIOS P7.00 09/09/2016 [ 145.033290] 88086e5879a0 813dc80c 88086e5879e8 [ 145.033295] c0556700 88086e5879d8 8107e9d6 88086d898000 [ 145.033300] 88086d89b000 0004 880871924b78 88086e587a64 [ 145.033305] Call Trace: [ 145.033311] [] dump_stack+0x63/0x87 [ 145.033317] [] warn_slowpath_common+0x86/0xc0 [ 145.033323] [] warn_slowpath_fmt+0x4c/0x50 [ 145.033358] [] ? ironlake_irq_handler+0x660/0xba0 [i915_bpo] [ 145.033393] [] skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo] [ 145.033435] [] skl_update_wm+0x19a/0x6f0 [i915_bpo] [ 145.033491] [] ? chv_write8+0x390/0x390 [i915_bpo] [ 145.033551] [] ? skl_ddi_pll_disable+0x70/0x80 [i915_bpo] [ 145.033590] [] intel_update_watermarks+0x1e/0x30 [i915_bpo] [ 145.033649] [] intel_atomic_commit+0x432/0x1440 [i915_bpo] [ 145.033688] [] ? drm_atomic_set_
[Kernel-packages] [Bug 1675204] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1675204/+attachment/4842938/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1675204 Title: Intel HD graphics crashes when connecting to 3 outputs (DVI+HDMI+DP) Status in linux package in Ubuntu: Confirmed Bug description: I have a very strange issue related to Intel graphics drivers (i915) with 3 connected on-board displays. I have a Xubuntu (14.04 LTS with HWE on 4.4.0-66 kernel) desktop computer running on a i7-6700K processor and on-board graphics (Mobo: AsRock z170 extreme4). I connect it to 3 displays - a 3440x1400 LG display (via onboard DP port), a 1920x1200 Dell display (via on-board HDMI), and a Sony 4k TV (via onboard DVI and a DVI-to-HDMI adapter). If I just connect my desktop to the first two displays (not the TV), everything works fine (except some minor issues). However, if I connect the 4k TV, even the TV is not on, my graphics starts to flicker every 5 min-ish (window theme turns off and then turns quickly back on); after a few flickering, the window theme will disappear, and the screen becomes weird - my chrome window will not fresh, or show blank boxes etc. If I disconnect the DVI connector to the TV (just use the LG+Dell dual-display), flickering and crash will not appear. I want to mention that, when I connect the computer to all 3 displays, I was actually able to get video output to all displays (I used arandr to configure them). I can even get 4k output to the 4k TV at 30Hz. I can't find a useful log entry when the flicking or graphics crash happens. I can only see a "CPU pipe A FIFO underrun" for pipe A/B/F (log attached at the end), but I can see many similar errors in my log and the appearance is not correlated to the flickering/crash. The "pipe A FIFO underrun" issue was previously reported in Bug#1550779. I also see "intel(0): HDMI max TMDS frequency 30KHz" entry in my Xorg.0.log file constantly, I also do not see an consistent mapping between the log entry and the flickering. Can anyone tell me how to properly debug this? what can I do to get a log for what was wrong? --- [ 145.033055] WARNING: CPU: 2 PID: 1804 at /build/linux-lts-xenial-drAJVo/linux-lts-xenial-4.4.0/ubuntu/i915/intel_pm.c:3675 skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo]() [ 145.033058] WARN_ON(!wm_changed) [ 145.033060] Modules linked in: nfsv3 pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) autofs4 rpcsec_gss_krb5 nfsv4 usblp joydev input_leds ti_usb_3410_5052 usbserial hid_generic gspca_ov534 gspca_main v4l2_common videodev media snd_usb_audio snd_usbmidi_lib usbhid snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic nvidia_uvm(POE) uas usb_storage intel_rapl x86_pkg_temp_thermal intel_powerclamp mxm_wmi coretemp kvm_intel bnep kvm rfcomm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_intel snd_hda_codec snd_hda_core nvidia_drm(POE) nvidia_modeset(POE) snd_hwdep aesni_intel snd_pcm aes_x86_64 nvidia(POE) lrw gf128mul snd_seq_midi snd_seq_midi_event glue_helper ablk_helper snd_rawmidi cryptd snd_seq snd_seq_device snd_timer serio_raw snd soundcore nfsd i915_bpo auth_rpcgss nfs_acl nfs binfmt_misc lockd grace 8250_fintek hci_uart sunrpc intel_ips drm_kms_helper btbcm pinctrl_sunrisepoint btqca fscache pinctrl_intel btintel intel_lpss_ac pi bluetooth i2c_hid intel_lpss drm hid video i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt shpchp mei_me mei mac_hid acpi_als wmi kfifo_buf industrialio acpi_pad parport_pc ppdev lp parport e1000e psmouse ptp pps_core ahci nvme libahci fjes [ 145.033284] CPU: 2 PID: 1804 Comm: Xorg Tainted: PW OE 4.4.0-66-generic #87~14.04.1-Ubuntu [ 145.033287] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z170 Extreme4, BIOS P7.00 09/09/2016 [ 145.033290] 88086e5879a0 813dc80c 88086e5879e8 [ 145.033295] c0556700 88086e5879d8 8107e9d6 88086d898000 [ 145.033300] 88086d89b000 0004 880871924b78 88086e587a64 [ 145.033305] Call Trace: [ 145.033311] [] dump_stack+0x63/0x87 [ 145.033317] [] warn_slowpath_common+0x86/0xc0 [ 145.033323] [] warn_slowpath_fmt+0x4c/0x50 [ 145.033358] [] ? ironlake_irq_handler+0x660/0xba0 [i915_bpo] [ 145.033393] [] skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo] [ 145.033435] [] skl_update_wm+0x19a/0x6f0 [i915_bpo] [ 145.033491] [] ? chv_write8+0x390/0x390 [i915_bpo] [ 145.033551] [] ? skl_ddi_pll_disable+0x70/0x80 [i915_bpo] [ 145.033590] [] intel_update_watermarks+0x1e/0x30 [i915_bpo] [ 145.033649] [] intel_atomic_commit+0x432/0x1440 [i915_bpo] [ 145.033688] [] ? drm_atomic_set_cr
[Kernel-packages] [Bug 1675204] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1675204/+attachment/4842935/+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/1675204 Title: Intel HD graphics crashes when connecting to 3 outputs (DVI+HDMI+DP) Status in linux package in Ubuntu: Confirmed Bug description: I have a very strange issue related to Intel graphics drivers (i915) with 3 connected on-board displays. I have a Xubuntu (14.04 LTS with HWE on 4.4.0-66 kernel) desktop computer running on a i7-6700K processor and on-board graphics (Mobo: AsRock z170 extreme4). I connect it to 3 displays - a 3440x1400 LG display (via onboard DP port), a 1920x1200 Dell display (via on-board HDMI), and a Sony 4k TV (via onboard DVI and a DVI-to-HDMI adapter). If I just connect my desktop to the first two displays (not the TV), everything works fine (except some minor issues). However, if I connect the 4k TV, even the TV is not on, my graphics starts to flicker every 5 min-ish (window theme turns off and then turns quickly back on); after a few flickering, the window theme will disappear, and the screen becomes weird - my chrome window will not fresh, or show blank boxes etc. If I disconnect the DVI connector to the TV (just use the LG+Dell dual-display), flickering and crash will not appear. I want to mention that, when I connect the computer to all 3 displays, I was actually able to get video output to all displays (I used arandr to configure them). I can even get 4k output to the 4k TV at 30Hz. I can't find a useful log entry when the flicking or graphics crash happens. I can only see a "CPU pipe A FIFO underrun" for pipe A/B/F (log attached at the end), but I can see many similar errors in my log and the appearance is not correlated to the flickering/crash. The "pipe A FIFO underrun" issue was previously reported in Bug#1550779. I also see "intel(0): HDMI max TMDS frequency 30KHz" entry in my Xorg.0.log file constantly, I also do not see an consistent mapping between the log entry and the flickering. Can anyone tell me how to properly debug this? what can I do to get a log for what was wrong? --- [ 145.033055] WARNING: CPU: 2 PID: 1804 at /build/linux-lts-xenial-drAJVo/linux-lts-xenial-4.4.0/ubuntu/i915/intel_pm.c:3675 skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo]() [ 145.033058] WARN_ON(!wm_changed) [ 145.033060] Modules linked in: nfsv3 pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) autofs4 rpcsec_gss_krb5 nfsv4 usblp joydev input_leds ti_usb_3410_5052 usbserial hid_generic gspca_ov534 gspca_main v4l2_common videodev media snd_usb_audio snd_usbmidi_lib usbhid snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic nvidia_uvm(POE) uas usb_storage intel_rapl x86_pkg_temp_thermal intel_powerclamp mxm_wmi coretemp kvm_intel bnep kvm rfcomm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_intel snd_hda_codec snd_hda_core nvidia_drm(POE) nvidia_modeset(POE) snd_hwdep aesni_intel snd_pcm aes_x86_64 nvidia(POE) lrw gf128mul snd_seq_midi snd_seq_midi_event glue_helper ablk_helper snd_rawmidi cryptd snd_seq snd_seq_device snd_timer serio_raw snd soundcore nfsd i915_bpo auth_rpcgss nfs_acl nfs binfmt_misc lockd grace 8250_fintek hci_uart sunrpc intel_ips drm_kms_helper btbcm pinctrl_sunrisepoint btqca fscache pinctrl_intel btintel intel_lpss_ac pi bluetooth i2c_hid intel_lpss drm hid video i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt shpchp mei_me mei mac_hid acpi_als wmi kfifo_buf industrialio acpi_pad parport_pc ppdev lp parport e1000e psmouse ptp pps_core ahci nvme libahci fjes [ 145.033284] CPU: 2 PID: 1804 Comm: Xorg Tainted: PW OE 4.4.0-66-generic #87~14.04.1-Ubuntu [ 145.033287] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z170 Extreme4, BIOS P7.00 09/09/2016 [ 145.033290] 88086e5879a0 813dc80c 88086e5879e8 [ 145.033295] c0556700 88086e5879d8 8107e9d6 88086d898000 [ 145.033300] 88086d89b000 0004 880871924b78 88086e587a64 [ 145.033305] Call Trace: [ 145.033311] [] dump_stack+0x63/0x87 [ 145.033317] [] warn_slowpath_common+0x86/0xc0 [ 145.033323] [] warn_slowpath_fmt+0x4c/0x50 [ 145.033358] [] ? ironlake_irq_handler+0x660/0xba0 [i915_bpo] [ 145.033393] [] skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo] [ 145.033435] [] skl_update_wm+0x19a/0x6f0 [i915_bpo] [ 145.033491] [] ? chv_write8+0x390/0x390 [i915_bpo] [ 145.033551] [] ? skl_ddi_pll_disable+0x70/0x80 [i915_bpo] [ 145.033590] [] intel_update_watermarks+0x1e/0x30 [i915_bpo] [ 145.033649] [] intel_atomic_commit+0x432/0x1440 [i915_bpo] [ 145.033688] [] ? drm_atomic_set_crtc
[Kernel-packages] [Bug 1675204] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1675204/+attachment/4842939/+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/1675204 Title: Intel HD graphics crashes when connecting to 3 outputs (DVI+HDMI+DP) Status in linux package in Ubuntu: Confirmed Bug description: I have a very strange issue related to Intel graphics drivers (i915) with 3 connected on-board displays. I have a Xubuntu (14.04 LTS with HWE on 4.4.0-66 kernel) desktop computer running on a i7-6700K processor and on-board graphics (Mobo: AsRock z170 extreme4). I connect it to 3 displays - a 3440x1400 LG display (via onboard DP port), a 1920x1200 Dell display (via on-board HDMI), and a Sony 4k TV (via onboard DVI and a DVI-to-HDMI adapter). If I just connect my desktop to the first two displays (not the TV), everything works fine (except some minor issues). However, if I connect the 4k TV, even the TV is not on, my graphics starts to flicker every 5 min-ish (window theme turns off and then turns quickly back on); after a few flickering, the window theme will disappear, and the screen becomes weird - my chrome window will not fresh, or show blank boxes etc. If I disconnect the DVI connector to the TV (just use the LG+Dell dual-display), flickering and crash will not appear. I want to mention that, when I connect the computer to all 3 displays, I was actually able to get video output to all displays (I used arandr to configure them). I can even get 4k output to the 4k TV at 30Hz. I can't find a useful log entry when the flicking or graphics crash happens. I can only see a "CPU pipe A FIFO underrun" for pipe A/B/F (log attached at the end), but I can see many similar errors in my log and the appearance is not correlated to the flickering/crash. The "pipe A FIFO underrun" issue was previously reported in Bug#1550779. I also see "intel(0): HDMI max TMDS frequency 30KHz" entry in my Xorg.0.log file constantly, I also do not see an consistent mapping between the log entry and the flickering. Can anyone tell me how to properly debug this? what can I do to get a log for what was wrong? --- [ 145.033055] WARNING: CPU: 2 PID: 1804 at /build/linux-lts-xenial-drAJVo/linux-lts-xenial-4.4.0/ubuntu/i915/intel_pm.c:3675 skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo]() [ 145.033058] WARN_ON(!wm_changed) [ 145.033060] Modules linked in: nfsv3 pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) autofs4 rpcsec_gss_krb5 nfsv4 usblp joydev input_leds ti_usb_3410_5052 usbserial hid_generic gspca_ov534 gspca_main v4l2_common videodev media snd_usb_audio snd_usbmidi_lib usbhid snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic nvidia_uvm(POE) uas usb_storage intel_rapl x86_pkg_temp_thermal intel_powerclamp mxm_wmi coretemp kvm_intel bnep kvm rfcomm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_intel snd_hda_codec snd_hda_core nvidia_drm(POE) nvidia_modeset(POE) snd_hwdep aesni_intel snd_pcm aes_x86_64 nvidia(POE) lrw gf128mul snd_seq_midi snd_seq_midi_event glue_helper ablk_helper snd_rawmidi cryptd snd_seq snd_seq_device snd_timer serio_raw snd soundcore nfsd i915_bpo auth_rpcgss nfs_acl nfs binfmt_misc lockd grace 8250_fintek hci_uart sunrpc intel_ips drm_kms_helper btbcm pinctrl_sunrisepoint btqca fscache pinctrl_intel btintel intel_lpss_ac pi bluetooth i2c_hid intel_lpss drm hid video i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt shpchp mei_me mei mac_hid acpi_als wmi kfifo_buf industrialio acpi_pad parport_pc ppdev lp parport e1000e psmouse ptp pps_core ahci nvme libahci fjes [ 145.033284] CPU: 2 PID: 1804 Comm: Xorg Tainted: PW OE 4.4.0-66-generic #87~14.04.1-Ubuntu [ 145.033287] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z170 Extreme4, BIOS P7.00 09/09/2016 [ 145.033290] 88086e5879a0 813dc80c 88086e5879e8 [ 145.033295] c0556700 88086e5879d8 8107e9d6 88086d898000 [ 145.033300] 88086d89b000 0004 880871924b78 88086e587a64 [ 145.033305] Call Trace: [ 145.033311] [] dump_stack+0x63/0x87 [ 145.033317] [] warn_slowpath_common+0x86/0xc0 [ 145.033323] [] warn_slowpath_fmt+0x4c/0x50 [ 145.033358] [] ? ironlake_irq_handler+0x660/0xba0 [i915_bpo] [ 145.033393] [] skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo] [ 145.033435] [] skl_update_wm+0x19a/0x6f0 [i915_bpo] [ 145.033491] [] ? chv_write8+0x390/0x390 [i915_bpo] [ 145.033551] [] ? skl_ddi_pll_disable+0x70/0x80 [i915_bpo] [ 145.033590] [] intel_update_watermarks+0x1e/0x30 [i915_bpo] [ 145.033649] [] intel_atomic_commit+0x432/0x1440 [i915_bpo] [ 145.033688] [] ? drm_
[Kernel-packages] [Bug 1675204] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1675204/+attachment/4842919/+files/BootDmesg.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/1675204 Title: Intel HD graphics crashes when connecting to 3 outputs (DVI+HDMI+DP) Status in linux package in Ubuntu: Confirmed Bug description: I have a very strange issue related to Intel graphics drivers (i915) with 3 connected on-board displays. I have a Xubuntu (14.04 LTS with HWE on 4.4.0-66 kernel) desktop computer running on a i7-6700K processor and on-board graphics (Mobo: AsRock z170 extreme4). I connect it to 3 displays - a 3440x1400 LG display (via onboard DP port), a 1920x1200 Dell display (via on-board HDMI), and a Sony 4k TV (via onboard DVI and a DVI-to-HDMI adapter). If I just connect my desktop to the first two displays (not the TV), everything works fine (except some minor issues). However, if I connect the 4k TV, even the TV is not on, my graphics starts to flicker every 5 min-ish (window theme turns off and then turns quickly back on); after a few flickering, the window theme will disappear, and the screen becomes weird - my chrome window will not fresh, or show blank boxes etc. If I disconnect the DVI connector to the TV (just use the LG+Dell dual-display), flickering and crash will not appear. I want to mention that, when I connect the computer to all 3 displays, I was actually able to get video output to all displays (I used arandr to configure them). I can even get 4k output to the 4k TV at 30Hz. I can't find a useful log entry when the flicking or graphics crash happens. I can only see a "CPU pipe A FIFO underrun" for pipe A/B/F (log attached at the end), but I can see many similar errors in my log and the appearance is not correlated to the flickering/crash. The "pipe A FIFO underrun" issue was previously reported in Bug#1550779. I also see "intel(0): HDMI max TMDS frequency 30KHz" entry in my Xorg.0.log file constantly, I also do not see an consistent mapping between the log entry and the flickering. Can anyone tell me how to properly debug this? what can I do to get a log for what was wrong? --- [ 145.033055] WARNING: CPU: 2 PID: 1804 at /build/linux-lts-xenial-drAJVo/linux-lts-xenial-4.4.0/ubuntu/i915/intel_pm.c:3675 skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo]() [ 145.033058] WARN_ON(!wm_changed) [ 145.033060] Modules linked in: nfsv3 pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) autofs4 rpcsec_gss_krb5 nfsv4 usblp joydev input_leds ti_usb_3410_5052 usbserial hid_generic gspca_ov534 gspca_main v4l2_common videodev media snd_usb_audio snd_usbmidi_lib usbhid snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic nvidia_uvm(POE) uas usb_storage intel_rapl x86_pkg_temp_thermal intel_powerclamp mxm_wmi coretemp kvm_intel bnep kvm rfcomm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_intel snd_hda_codec snd_hda_core nvidia_drm(POE) nvidia_modeset(POE) snd_hwdep aesni_intel snd_pcm aes_x86_64 nvidia(POE) lrw gf128mul snd_seq_midi snd_seq_midi_event glue_helper ablk_helper snd_rawmidi cryptd snd_seq snd_seq_device snd_timer serio_raw snd soundcore nfsd i915_bpo auth_rpcgss nfs_acl nfs binfmt_misc lockd grace 8250_fintek hci_uart sunrpc intel_ips drm_kms_helper btbcm pinctrl_sunrisepoint btqca fscache pinctrl_intel btintel intel_lpss_ac pi bluetooth i2c_hid intel_lpss drm hid video i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt shpchp mei_me mei mac_hid acpi_als wmi kfifo_buf industrialio acpi_pad parport_pc ppdev lp parport e1000e psmouse ptp pps_core ahci nvme libahci fjes [ 145.033284] CPU: 2 PID: 1804 Comm: Xorg Tainted: PW OE 4.4.0-66-generic #87~14.04.1-Ubuntu [ 145.033287] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z170 Extreme4, BIOS P7.00 09/09/2016 [ 145.033290] 88086e5879a0 813dc80c 88086e5879e8 [ 145.033295] c0556700 88086e5879d8 8107e9d6 88086d898000 [ 145.033300] 88086d89b000 0004 880871924b78 88086e587a64 [ 145.033305] Call Trace: [ 145.033311] [] dump_stack+0x63/0x87 [ 145.033317] [] warn_slowpath_common+0x86/0xc0 [ 145.033323] [] warn_slowpath_fmt+0x4c/0x50 [ 145.033358] [] ? ironlake_irq_handler+0x660/0xba0 [i915_bpo] [ 145.033393] [] skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo] [ 145.033435] [] skl_update_wm+0x19a/0x6f0 [i915_bpo] [ 145.033491] [] ? chv_write8+0x390/0x390 [i915_bpo] [ 145.033551] [] ? skl_ddi_pll_disable+0x70/0x80 [i915_bpo] [ 145.033590] [] intel_update_watermarks+0x1e/0x30 [i915_bpo] [ 145.033649] [] intel_atomic_commit+0x432/0x1440 [i915_bpo] [ 145.033688] [] ? drm_atom
[Kernel-packages] [Bug 1675204] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1675204/+attachment/4842920/+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/1675204 Title: Intel HD graphics crashes when connecting to 3 outputs (DVI+HDMI+DP) Status in linux package in Ubuntu: Confirmed Bug description: I have a very strange issue related to Intel graphics drivers (i915) with 3 connected on-board displays. I have a Xubuntu (14.04 LTS with HWE on 4.4.0-66 kernel) desktop computer running on a i7-6700K processor and on-board graphics (Mobo: AsRock z170 extreme4). I connect it to 3 displays - a 3440x1400 LG display (via onboard DP port), a 1920x1200 Dell display (via on-board HDMI), and a Sony 4k TV (via onboard DVI and a DVI-to-HDMI adapter). If I just connect my desktop to the first two displays (not the TV), everything works fine (except some minor issues). However, if I connect the 4k TV, even the TV is not on, my graphics starts to flicker every 5 min-ish (window theme turns off and then turns quickly back on); after a few flickering, the window theme will disappear, and the screen becomes weird - my chrome window will not fresh, or show blank boxes etc. If I disconnect the DVI connector to the TV (just use the LG+Dell dual-display), flickering and crash will not appear. I want to mention that, when I connect the computer to all 3 displays, I was actually able to get video output to all displays (I used arandr to configure them). I can even get 4k output to the 4k TV at 30Hz. I can't find a useful log entry when the flicking or graphics crash happens. I can only see a "CPU pipe A FIFO underrun" for pipe A/B/F (log attached at the end), but I can see many similar errors in my log and the appearance is not correlated to the flickering/crash. The "pipe A FIFO underrun" issue was previously reported in Bug#1550779. I also see "intel(0): HDMI max TMDS frequency 30KHz" entry in my Xorg.0.log file constantly, I also do not see an consistent mapping between the log entry and the flickering. Can anyone tell me how to properly debug this? what can I do to get a log for what was wrong? --- [ 145.033055] WARNING: CPU: 2 PID: 1804 at /build/linux-lts-xenial-drAJVo/linux-lts-xenial-4.4.0/ubuntu/i915/intel_pm.c:3675 skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo]() [ 145.033058] WARN_ON(!wm_changed) [ 145.033060] Modules linked in: nfsv3 pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) autofs4 rpcsec_gss_krb5 nfsv4 usblp joydev input_leds ti_usb_3410_5052 usbserial hid_generic gspca_ov534 gspca_main v4l2_common videodev media snd_usb_audio snd_usbmidi_lib usbhid snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic nvidia_uvm(POE) uas usb_storage intel_rapl x86_pkg_temp_thermal intel_powerclamp mxm_wmi coretemp kvm_intel bnep kvm rfcomm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_intel snd_hda_codec snd_hda_core nvidia_drm(POE) nvidia_modeset(POE) snd_hwdep aesni_intel snd_pcm aes_x86_64 nvidia(POE) lrw gf128mul snd_seq_midi snd_seq_midi_event glue_helper ablk_helper snd_rawmidi cryptd snd_seq snd_seq_device snd_timer serio_raw snd soundcore nfsd i915_bpo auth_rpcgss nfs_acl nfs binfmt_misc lockd grace 8250_fintek hci_uart sunrpc intel_ips drm_kms_helper btbcm pinctrl_sunrisepoint btqca fscache pinctrl_intel btintel intel_lpss_ac pi bluetooth i2c_hid intel_lpss drm hid video i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt shpchp mei_me mei mac_hid acpi_als wmi kfifo_buf industrialio acpi_pad parport_pc ppdev lp parport e1000e psmouse ptp pps_core ahci nvme libahci fjes [ 145.033284] CPU: 2 PID: 1804 Comm: Xorg Tainted: PW OE 4.4.0-66-generic #87~14.04.1-Ubuntu [ 145.033287] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z170 Extreme4, BIOS P7.00 09/09/2016 [ 145.033290] 88086e5879a0 813dc80c 88086e5879e8 [ 145.033295] c0556700 88086e5879d8 8107e9d6 88086d898000 [ 145.033300] 88086d89b000 0004 880871924b78 88086e587a64 [ 145.033305] Call Trace: [ 145.033311] [] dump_stack+0x63/0x87 [ 145.033317] [] warn_slowpath_common+0x86/0xc0 [ 145.033323] [] warn_slowpath_fmt+0x4c/0x50 [ 145.033358] [] ? ironlake_irq_handler+0x660/0xba0 [i915_bpo] [ 145.033393] [] skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo] [ 145.033435] [] skl_update_wm+0x19a/0x6f0 [i915_bpo] [ 145.033491] [] ? chv_write8+0x390/0x390 [i915_bpo] [ 145.033551] [] ? skl_ddi_pll_disable+0x70/0x80 [i915_bpo] [ 145.033590] [] intel_update_watermarks+0x1e/0x30 [i915_bpo] [ 145.033649] [] intel_atomic_commit+0x432/0x1440 [i915_bpo] [ 145.033688] [] ? drm_atomic_set_crtc
[Kernel-packages] [Bug 1675204] Re: Intel HD graphics crashes when connecting to 3 outputs (DVI+HDMI+DP)
apport information ** Tags added: apport-collected trusty ** Description changed: I have a very strange issue related to Intel graphics drivers (i915) with 3 connected on-board displays. I have a Xubuntu (14.04 LTS with HWE on 4.4.0-66 kernel) desktop computer running on a i7-6700K processor and on-board graphics (Mobo: AsRock z170 extreme4). I connect it to 3 displays - a 3440x1400 LG display (via onboard DP port), a 1920x1200 Dell display (via on-board HDMI), and a Sony 4k TV (via onboard DVI and a DVI-to-HDMI adapter). If I just connect my desktop to the first two displays (not the TV), everything works fine (except some minor issues). However, if I connect the 4k TV, even the TV is not on, my graphics starts to flicker every 5 min-ish (window theme turns off and then turns quickly back on); after a few flickering, the window theme will disappear, and the screen becomes weird - my chrome window will not fresh, or show blank boxes etc. If I disconnect the DVI connector to the TV (just use the LG+Dell dual- display), flickering and crash will not appear. I want to mention that, when I connect the computer to all 3 displays, I was actually able to get video output to all displays (I used arandr to configure them). I can even get 4k output to the 4k TV at 30Hz. I can't find a useful log entry when the flicking or graphics crash happens. I can only see a "CPU pipe A FIFO underrun" for pipe A/B/F (log attached at the end), but I can see many similar errors in my log and the appearance is not correlated to the flickering/crash. The "pipe A FIFO underrun" issue was previously reported in Bug#1550779. I also see "intel(0): HDMI max TMDS frequency 30KHz" entry in my Xorg.0.log file constantly, I also do not see an consistent mapping between the log entry and the flickering. Can anyone tell me how to properly debug this? what can I do to get a log for what was wrong? --- [ 145.033055] WARNING: CPU: 2 PID: 1804 at /build/linux-lts-xenial-drAJVo/linux-lts-xenial-4.4.0/ubuntu/i915/intel_pm.c:3675 skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo]() [ 145.033058] WARN_ON(!wm_changed) [ 145.033060] Modules linked in: nfsv3 pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) autofs4 rpcsec_gss_krb5 nfsv4 usblp joydev input_leds ti_usb_3410_5052 usbserial hid_generic gspca_ov534 gspca_main v4l2_common videodev media snd_usb_audio snd_usbmidi_lib usbhid snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic nvidia_uvm(POE) uas usb_storage intel_rapl x86_pkg_temp_thermal intel_powerclamp mxm_wmi coretemp kvm_intel bnep kvm rfcomm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_intel snd_hda_codec snd_hda_core nvidia_drm(POE) nvidia_modeset(POE) snd_hwdep aesni_intel snd_pcm aes_x86_64 nvidia(POE) lrw gf128mul snd_seq_midi snd_seq_midi_event glue_helper ablk_helper snd_rawmidi cryptd snd_seq snd_seq_device snd_timer serio_raw snd soundcore nfsd i915_bpo auth_rpcgss nfs_acl nfs binfmt_misc lockd grace 8250_fintek hci_uart sunrpc intel_ips drm_kms_helper btbcm pinctrl_sunrisepoint btqca fscache pinctrl_intel btintel intel_lpss_ac pi bluetooth i2c_hid intel_lpss drm hid video i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt shpchp mei_me mei mac_hid acpi_als wmi kfifo_buf industrialio acpi_pad parport_pc ppdev lp parport e1000e psmouse ptp pps_core ahci nvme libahci fjes [ 145.033284] CPU: 2 PID: 1804 Comm: Xorg Tainted: PW OE 4.4.0-66-generic #87~14.04.1-Ubuntu [ 145.033287] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z170 Extreme4, BIOS P7.00 09/09/2016 [ 145.033290] 88086e5879a0 813dc80c 88086e5879e8 [ 145.033295] c0556700 88086e5879d8 8107e9d6 88086d898000 [ 145.033300] 88086d89b000 0004 880871924b78 88086e587a64 [ 145.033305] Call Trace: [ 145.033311] [] dump_stack+0x63/0x87 [ 145.033317] [] warn_slowpath_common+0x86/0xc0 [ 145.033323] [] warn_slowpath_fmt+0x4c/0x50 [ 145.033358] [] ? ironlake_irq_handler+0x660/0xba0 [i915_bpo] [ 145.033393] [] skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo] [ 145.033435] [] skl_update_wm+0x19a/0x6f0 [i915_bpo] [ 145.033491] [] ? chv_write8+0x390/0x390 [i915_bpo] [ 145.033551] [] ? skl_ddi_pll_disable+0x70/0x80 [i915_bpo] [ 145.033590] [] intel_update_watermarks+0x1e/0x30 [i915_bpo] [ 145.033649] [] intel_atomic_commit+0x432/0x1440 [i915_bpo] [ 145.033688] [] ? drm_atomic_set_crtc_for_connector+0x44/0xf0 [drm] [ 145.033720] [] drm_atomic_commit+0x37/0x60 [drm] [ 145.033743] [] drm_atomic_helper_set_config+0x77/0xb0 [drm_kms_helper] [ 145.033775] [] drm_mode_set_config_internal+0x64/0x100 [drm] [ 145.033805] [] drm_mode_setcrtc+0xdd/0x4f0 [drm] [ 145.033828] [] drm_ioctl+0x25d/0x4f0 [drm] [
[Kernel-packages] [Bug 1675204] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1675204/+attachment/4842921/+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/1675204 Title: Intel HD graphics crashes when connecting to 3 outputs (DVI+HDMI+DP) Status in linux package in Ubuntu: Confirmed Bug description: I have a very strange issue related to Intel graphics drivers (i915) with 3 connected on-board displays. I have a Xubuntu (14.04 LTS with HWE on 4.4.0-66 kernel) desktop computer running on a i7-6700K processor and on-board graphics (Mobo: AsRock z170 extreme4). I connect it to 3 displays - a 3440x1400 LG display (via onboard DP port), a 1920x1200 Dell display (via on-board HDMI), and a Sony 4k TV (via onboard DVI and a DVI-to-HDMI adapter). If I just connect my desktop to the first two displays (not the TV), everything works fine (except some minor issues). However, if I connect the 4k TV, even the TV is not on, my graphics starts to flicker every 5 min-ish (window theme turns off and then turns quickly back on); after a few flickering, the window theme will disappear, and the screen becomes weird - my chrome window will not fresh, or show blank boxes etc. If I disconnect the DVI connector to the TV (just use the LG+Dell dual-display), flickering and crash will not appear. I want to mention that, when I connect the computer to all 3 displays, I was actually able to get video output to all displays (I used arandr to configure them). I can even get 4k output to the 4k TV at 30Hz. I can't find a useful log entry when the flicking or graphics crash happens. I can only see a "CPU pipe A FIFO underrun" for pipe A/B/F (log attached at the end), but I can see many similar errors in my log and the appearance is not correlated to the flickering/crash. The "pipe A FIFO underrun" issue was previously reported in Bug#1550779. I also see "intel(0): HDMI max TMDS frequency 30KHz" entry in my Xorg.0.log file constantly, I also do not see an consistent mapping between the log entry and the flickering. Can anyone tell me how to properly debug this? what can I do to get a log for what was wrong? --- [ 145.033055] WARNING: CPU: 2 PID: 1804 at /build/linux-lts-xenial-drAJVo/linux-lts-xenial-4.4.0/ubuntu/i915/intel_pm.c:3675 skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo]() [ 145.033058] WARN_ON(!wm_changed) [ 145.033060] Modules linked in: nfsv3 pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) autofs4 rpcsec_gss_krb5 nfsv4 usblp joydev input_leds ti_usb_3410_5052 usbserial hid_generic gspca_ov534 gspca_main v4l2_common videodev media snd_usb_audio snd_usbmidi_lib usbhid snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic nvidia_uvm(POE) uas usb_storage intel_rapl x86_pkg_temp_thermal intel_powerclamp mxm_wmi coretemp kvm_intel bnep kvm rfcomm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_intel snd_hda_codec snd_hda_core nvidia_drm(POE) nvidia_modeset(POE) snd_hwdep aesni_intel snd_pcm aes_x86_64 nvidia(POE) lrw gf128mul snd_seq_midi snd_seq_midi_event glue_helper ablk_helper snd_rawmidi cryptd snd_seq snd_seq_device snd_timer serio_raw snd soundcore nfsd i915_bpo auth_rpcgss nfs_acl nfs binfmt_misc lockd grace 8250_fintek hci_uart sunrpc intel_ips drm_kms_helper btbcm pinctrl_sunrisepoint btqca fscache pinctrl_intel btintel intel_lpss_ac pi bluetooth i2c_hid intel_lpss drm hid video i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt shpchp mei_me mei mac_hid acpi_als wmi kfifo_buf industrialio acpi_pad parport_pc ppdev lp parport e1000e psmouse ptp pps_core ahci nvme libahci fjes [ 145.033284] CPU: 2 PID: 1804 Comm: Xorg Tainted: PW OE 4.4.0-66-generic #87~14.04.1-Ubuntu [ 145.033287] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z170 Extreme4, BIOS P7.00 09/09/2016 [ 145.033290] 88086e5879a0 813dc80c 88086e5879e8 [ 145.033295] c0556700 88086e5879d8 8107e9d6 88086d898000 [ 145.033300] 88086d89b000 0004 880871924b78 88086e587a64 [ 145.033305] Call Trace: [ 145.033311] [] dump_stack+0x63/0x87 [ 145.033317] [] warn_slowpath_common+0x86/0xc0 [ 145.033323] [] warn_slowpath_fmt+0x4c/0x50 [ 145.033358] [] ? ironlake_irq_handler+0x660/0xba0 [i915_bpo] [ 145.033393] [] skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo] [ 145.033435] [] skl_update_wm+0x19a/0x6f0 [i915_bpo] [ 145.033491] [] ? chv_write8+0x390/0x390 [i915_bpo] [ 145.033551] [] ? skl_ddi_pll_disable+0x70/0x80 [i915_bpo] [ 145.033590] [] intel_update_watermarks+0x1e/0x30 [i915_bpo] [ 145.033649] [] intel_atomic_commit+0x432/0x1440 [i915_bpo] [ 145.033688] [] ? dr
[Kernel-packages] [Bug 1654319] Re: kernel BUG at /build/linux-_qw1uB/linux-4.8.0/drivers/net/vmxnet3/vmxnet3_drv.c:1413
I could not repro this issue locally despite running traffic for several hours. If you hit the issue again, could you please generate vmss file when the VM is in the panic state? It can be obtained by suspending the VM in the panic state and then locating the vmss file in the director of the virtual machine on the ESX host. More details here: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2005831 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1654319 Title: kernel BUG at /build/linux- _qw1uB/linux-4.8.0/drivers/net/vmxnet3/vmxnet3_drv.c:1413 Status in Linux: Unknown Status in linux package in Ubuntu: Incomplete Bug description: Hello everyone, I have jenkins installed with an apache frontend. Sometimes, after making few GET requests whole system crashes and restarts. ESXi host version 6.5, virtual hardware version 13. I've found similar bug report here https://bugzilla.kernel.org/show_bug.cgi?id=191201 [ 6544.559660] [ cut here ] [ 6544.559694] kernel BUG at /build/linux-_qw1uB/linux-4.8.0/drivers/net/vmxnet3/vmxnet3_drv.c:1413! [ 6544.559728] invalid opcode: [#1] SMP [ 6544.559745] Modules linked in: xt_multiport vmw_vsock_vmci_transport vsock ppdev vmw_balloon joydev coretemp input_leds serio_raw nfit shpchp i2c_piix4 vmw_vmci parport_pc parport mac_hid ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns ib_iser rdma_cm nf_conntrack_broadcast iw_cm nf_nat_ftp ib_cm nf_nat ib_core nf_conntrack_ftp nf_conntrack iptable_filter configfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic [ 6544.560172] usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel vmwgfx ttm aesni_intel aes_x86_64 lrw glue_helper ablk_helper cryptd drm_kms_helper syscopyarea sysfillrect psmouse sysimgblt fb_sys_fops vmxnet3 ahci libahci mptspi drm mptscsih mptbase scsi_transport_spi pata_acpi fjes [ 6544.560332] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.8.0-32-generic #34-Ubuntu [ 6544.560360] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 04/05/2016 [ 6544.560399] task: a172f62a0d00 task.stack: a172f62ac000 [ 6544.560422] RIP: 0010:[] [] vmxnet3_rq_rx_complete+0x8d1/0xeb0 [vmxnet3] [ 6544.560465] RSP: 0018:a172ffc83dc8 EFLAGS: 00010297 [ 6544.560487] RAX: RBX: RCX: a172efb8a000 [ 6544.560513] RDX: 0040 RSI: 0001 RDI: 0040 [ 6544.560540] RBP: a172ffc83e40 R08: 0002 R09: 0030 [ 6544.560566] R10: R11: a172ec950880 R12: a172f35cc280 [ 6544.560593] R13: a172ec951400 R14: a172f1c83000 R15: a172f2b1c000 [ 6544.560621] FS: () GS:a172ffc8() knlGS: [ 6544.560650] CS: 0010 DS: ES: CR0: 80050033 [ 6544.560671] CR2: 7f742a78da30 CR3: 00022f962000 CR4: 06e0 [ 6544.560752] Stack: [ 6544.560766] a172ec950880 a172ec950880 a172ec950880 [ 6544.560803] 002d a172ec951420 0002 00010040 [ 6544.560837] a172ec9514e8 a172ec950880 a172ec951420 [ 6544.560872] Call Trace: [ 6544.561677] [ 6544.561689] [] vmxnet3_poll_rx_only+0x3a/0xb0 [vmxnet3] [ 6544.563233] [] net_rx_action+0x238/0x380 [ 6544.564004] [] __do_softirq+0x10d/0x298 [ 6544.564757] [] irq_exit+0xa3/0xb0 [ 6544.565499] [] do_IRQ+0x54/0xd0 [ 6544.566224] [] common_interrupt+0x82/0x82 [ 6544.566928] [ 6544.566940] [] ? native_safe_halt+0x6/0x10 [ 6544.568313] [] default_idle+0x20/0xd0 [ 6544.568978] [] arch_cpu_idle+0xf/0x20 [ 6544.569625] [] default_idle_call+0x2a/0x40 [ 6544.570255] [] cpu_startup_entry+0x2ec/0x350 [ 6544.570871] [] start_secondary+0x151/0x190 [ 6544.571475] Code: 90 88 45 98 4c 89 55 a0 e8 4d 70 e9 d8 0f b6 45 98 4c 8b 5d 90 4c 8b 55 a0 49 c7 85 60 01 00 00 00 00 00 00 89 c6 e9 91 f8 ff ff <0f> 0b 0f 0b 49 83 85 b8 01 00 00 01 49 c7 85 60 01 00 00 00 00 [ 6544.573327] RIP [] vmxnet3_rq_rx_complete+0x8d1/0xeb0 [vmxnet3] [ 6544.573926] RSP BR, Mikolaj Kowalski ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-32-generic 4.8.0-32.34 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 A
[Kernel-packages] [Bug 1616695] Re: Bluetooth signal is unusably poor
Well I found a work around for Manjaro/Arch linux... Hope this helps you guys on Ubuntu. I had rebooted into my original install ISO USB drive to check something unrelated and decided to try the BT Headphones on the live ISO, and it all works perfectly! I can walk between rooms and the A2DP works perfectly! So what I did was downgrade my Bluez & Bluez-libs from 5.44 to 5.41-2 and all is good in the bluetooth world! Note: I believe Ubuntu and Arch use different version numbers... -- 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/1616695 Title: Bluetooth signal is unusably poor Status in bluez package in Ubuntu: Confirmed Bug description: Brand new Macbook Pro 12,1. Brand new Ubuntu 16.04 install (from scratch). In MacOS the machine can connect to my bluetooth speaker from across the room and play A2DP no trouble at all. In Ubuntu 16.04 I have to literally hold up the macbook 1 inch away from the speaker to get it to connect and play, and even then it's a bit choppy. Turning off Wifi seems to help a bit, which leads me to think this is some kind of transmit power issue. Syslog is chock full of warnings about skipping audio: Aug 24 16:22:32 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 206099 us (= 36352 bytes) in audio stream Aug 24 16:22:32 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 382089 us (= 67400 bytes) in audio stream Aug 24 16:22:33 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 394108 us (= 69520 bytes) in audio stream Aug 24 16:22:33 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 328125 us (= 57880 bytes) in audio stream Aug 24 16:22:33 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 59087 us (= 10420 bytes) in audio stream Aug 24 16:22:33 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 14036 us (= 2472 bytes) in audio stream Aug 24 16:22:34 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 247134 us (= 43592 bytes) in audio stream Aug 24 16:22:34 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 342190 us (= 60360 bytes) in audio stream Aug 24 16:22:34 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 172035 us (= 30344 bytes) in audio stream Aug 24 16:22:35 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 803140 us (= 141672 bytes) in audio stream Aug 24 16:22:36 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 651085 us (= 114848 bytes) in audio stream Aug 24 16:22:36 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 202043 us (= 35640 bytes) in audio stream Aug 24 16:22:36 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 265112 us (= 46764 bytes) in audio stream $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04.1 LTS" $ uname -a Linux badassm 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux $ lsusb Bus 002 Device 002: ID 05ac:8406 Apple, Inc. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05ac:0273 Apple, Inc. Bus 001 Device 003: ID 05ac:8290 Apple, Inc. Bus 001 Device 006: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 4000 V1.0 Bus 001 Device 005: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub $ hciconfig hci0: Type: BR/EDR Bus: USB BD Address: 98:01:A7:A8:D4:6A ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:5198 acl:2 sco:0 events:269 errors:0 TX bytes:7021 acl:2 sco:0 commands:218 errors:0 [bluetooth]# show Controller 98:01:A7:A8:D4:6A Name: badassm Alias: badassm Class: 0x1c010c Powered: yes Discoverable: no Pairable: yes UUID: Headset AG(1112--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: OBEX Object Push (1105--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: IrMC Sync (1104--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
[Kernel-packages] [Bug 1674986] gonzo (i386) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-44.47-generic/gonzo__4.8.0-44.47__2017-03-23_00-22-00/results-index.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/1674986 Title: linux: 4.8.0-44.47 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 Yakkety: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674988 derivatives: 1674989 kernel-stable-phase-changed:Wednesday, 22. March 2017 21:31 UTC kernel-stable-phase:Uploaded -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1674986/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674986] fozzie (i386) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-44.47-generic/fozzie__4.8.0-44.47__2017-03-23_00-18-00/results-index.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/1674986 Title: linux: 4.8.0-44.47 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 Yakkety: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674988 derivatives: 1674989 kernel-stable-phase-changed:Wednesday, 22. March 2017 21:31 UTC kernel-stable-phase:Uploaded -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1674986/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581088] Re: Middle mouse (wheel-click) button stopped working after upgrade to 16.04
typo in my previous post. Command is: xinput --set-prop 11 297 1 Apologize for any confusion. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1581088 Title: Middle mouse (wheel-click) button stopped working after upgrade to 16.04 Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to 16.04 clicking the middle mouse button (scroll wheel) on my Logitech M185 stopped working. xev does not even show the event for clicking the wheel, while it shows other button clicks and scroll wheel up/down events. xinput list shows the USB receiver 2 times: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=9[slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=10 [slave pointer (2)] ⎜ ↳ HID 046a:0023 id=13 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=16 [slave pointer (2)] ⎜ ↳ TPPS/2 IBM TrackPoint id=17 [slave pointer (2)] Listing the capabilities looks like this: $ xinput list 9 Logitech USB Receiver id=9[slave pointer (2)] Reporting 7 classes: Class originated from: 9. Type: XIButtonClass Buttons supported: 24 Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" "Button Side" "Button Extra" "Button Forward" "Button Back" "Button Task" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" Button state: Class originated from: 9. Type: XIValuatorClass Detail for Valuator 0: Label: Rel X Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 1: Label: Rel Y Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 2: Label: Rel Horiz Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 3: Label: Rel Vert Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIScrollClass Scroll info for Valuator 2 type: 2 (horizontal) increment: 1.00 flags: 0x0 Class originated from: 9. Type: XIScrollClass Scroll info for Valuator 3 type: 1 (vertical) increment: -1.00 flags: 0x2 ( preferred ) $ xinput list 10 Logitech USB Receiver id=10 [slave pointer (2)] Reporting 6 classes: Class originated from: 10. Type: XIButtonClass Buttons supported: 7 Button labels: "Button 0" "Button Unknown" "Button Unknown" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" Button state: Class originated from: 10. Type: XIKeyClass Keycodes supported: 248 Class originated from: 10. Type: XIValuatorClass Detail for Valuator 0: Label: Rel X Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 10. Type: XIValuatorClass Detail for Valuator 1: Label: Rel Y Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 10. Type: XIValuatorClass Detail for Valuator 2: Label: Rel Horiz Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 10. Type: XIScrollClass Scroll info for Valuator 2 type: 2 (horizontal) increment: 1.00 flags: 0x0 Does anyone have an idea how I can attempt to further debug that issue? Or maybe even a solution? Should I consider this issue a bug? Can I provide more info? --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: toby 11625 F pulseaudio /dev/snd/controlC0: toby 11625 F pulseaudio /dev/snd/pcmC1D0p: toby 11625 F...m pulseaudio /dev/snd/controlC1: toby 11625 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=5e3a6d2e-05f8-4d01-b80c-a9f200e6 InstallationDate: Installed on 2014-04-24 (749 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.
[Kernel-packages] [Bug 1674986] rumford (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-44.47-generic/rumford__4.8.0-44.47__2017-03-23_00-10-00/results-index.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/1674986 Title: linux: 4.8.0-44.47 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 Yakkety: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674988 derivatives: 1674989 kernel-stable-phase-changed:Wednesday, 22. March 2017 21:31 UTC kernel-stable-phase:Uploaded -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1674986/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581088] Re: Middle mouse (wheel-click) button stopped working after upgrade to 16.04
I'm not sure this is a kernel issue. It appears to be something related to the evdev driver or how the files in xorg.conf.d are interpreted when setting up the evdev driver. the "Evdev Wheel Emulation" is "false" even though my config file xorg.conf.d is trying to set it to "true" - when I manually set it to "true" scrolling works fine. I have a precise install (3.13.0-112-generic kernel) where the scrolling works. When I look at the output of "xinput --list-props XX" for my trackball, I see that "Evdev Wheel Emulation" is "true". On a Xenial install (4.8.0-41-generic kernel), using the same file in xorg.conf.d for my trackball, it shows Evdev Wheel Emulation as false. Looking in the syslog, I see a line for: "/usr/lib/gdm3/gdm-x-session[2042]: (**) Option "EmulateWheel" "true"" but the option isn't being set to true. I believe this is where the problem lies. Here is a work around: find the id of the device that won't scroll using "xinput --list", mine is 11 then check whether wheel emulation is true or false usng "xinput --list- props 11" Here is what I see for list-props when I first boot and log in: Evdev Wheel Emulation (297):0 the 0 is false. Change this with the following: xinput --set-property 11 297 1 where 11 - id of the device 297 - property number (shown in parenthesis from above) 1 is the boolean for true After doing this, the output from "xinput --list-props 11" shows: Evdev Wheel Emulation (297):1 And now the scroll works as it did before I experienced this problem. Can others check what they find using "xinput --list-props xx" to see if this is repeatable? 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/1581088 Title: Middle mouse (wheel-click) button stopped working after upgrade to 16.04 Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to 16.04 clicking the middle mouse button (scroll wheel) on my Logitech M185 stopped working. xev does not even show the event for clicking the wheel, while it shows other button clicks and scroll wheel up/down events. xinput list shows the USB receiver 2 times: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=9[slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=10 [slave pointer (2)] ⎜ ↳ HID 046a:0023 id=13 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=16 [slave pointer (2)] ⎜ ↳ TPPS/2 IBM TrackPoint id=17 [slave pointer (2)] Listing the capabilities looks like this: $ xinput list 9 Logitech USB Receiver id=9[slave pointer (2)] Reporting 7 classes: Class originated from: 9. Type: XIButtonClass Buttons supported: 24 Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" "Button Side" "Button Extra" "Button Forward" "Button Back" "Button Task" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" Button state: Class originated from: 9. Type: XIValuatorClass Detail for Valuator 0: Label: Rel X Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 1: Label: Rel Y Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 2: Label: Rel Horiz Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 3: Label: Rel Vert Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIScrollClass Scroll info for Valuator 2 type: 2 (horizontal) increment: 1.00 flags: 0x0 Class originated from: 9. Type: XIScrollClass Scroll info for Valuator 3 type: 1 (vertical) increment: -1.00 flags: 0x2 ( preferred ) $ xinput list 10 Logitech USB Receiver id=10 [slave pointer (2)] Reporting 6 classes: Class originated from: 10. Type: XIButtonClass Buttons supported: 7 Button labels: "Button 0" "Button Unknown" "Button Unknown" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" Button state: Class originated from: 10.
[Kernel-packages] [Bug 1674986] ms10-34-mcdivittB0-kernel (arm64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-44.47-generic/ms10-34-mcdivittB0-kernel__4.8.0-44.47__2017-03-23_00-04-00/results-index.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/1674986 Title: linux: 4.8.0-44.47 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 Yakkety: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674988 derivatives: 1674989 kernel-stable-phase-changed:Wednesday, 22. March 2017 21:31 UTC kernel-stable-phase:Uploaded -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1674986/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674986] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-44.47-generic/ms10-35-mcdivittB0-kernel__4.8.0-44.47__2017-03-23_00-03-00/results-index.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/1674986 Title: linux: 4.8.0-44.47 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 Yakkety: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674988 derivatives: 1674989 kernel-stable-phase-changed:Wednesday, 22. March 2017 21:31 UTC kernel-stable-phase:Uploaded -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1674986/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674986] modoc (ppc64el) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-44.47-generic/modoc__4.8.0-44.47__2017-03-23_00-02-00/results-index.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/1674986 Title: linux: 4.8.0-44.47 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 Yakkety: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674988 derivatives: 1674989 kernel-stable-phase-changed:Wednesday, 22. March 2017 21:31 UTC kernel-stable-phase:Uploaded -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1674986/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674986] gonzo (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-44.47-generic/gonzo__4.8.0-44.47__2017-03-22_23-56-00/results-index.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/1674986 Title: linux: 4.8.0-44.47 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 Yakkety: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674988 derivatives: 1674989 kernel-stable-phase-changed:Wednesday, 22. March 2017 21:31 UTC kernel-stable-phase:Uploaded -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1674986/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674986] hainzel (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-44.47-generic/hainzel__4.8.0-44.47__2017-03-22_23-56-00/results-index.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/1674986 Title: linux: 4.8.0-44.47 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 Yakkety: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674988 derivatives: 1674989 kernel-stable-phase-changed:Wednesday, 22. March 2017 21:31 UTC kernel-stable-phase:Uploaded -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1674986/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674986] archytas (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-44.47-generic/archytas__4.8.0-44.47__2017-03-22_23-56-00/results-index.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/1674986 Title: linux: 4.8.0-44.47 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 Yakkety: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674988 derivatives: 1674989 kernel-stable-phase-changed:Wednesday, 22. March 2017 21:31 UTC kernel-stable-phase:Uploaded -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1674986/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674986] fozzie (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-44.47-generic/fozzie__4.8.0-44.47__2017-03-22_23-55-00/results-index.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/1674986 Title: linux: 4.8.0-44.47 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 Yakkety: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674988 derivatives: 1674989 kernel-stable-phase-changed:Wednesday, 22. March 2017 21:31 UTC kernel-stable-phase:Uploaded -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1674986/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674986] amaura (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-44.47-generic/amaura__4.8.0-44.47__2017-03-22_23-47-00/results-index.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/1674986 Title: linux: 4.8.0-44.47 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 Yakkety: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674988 derivatives: 1674989 kernel-stable-phase-changed:Wednesday, 22. March 2017 21:31 UTC kernel-stable-phase:Uploaded -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1674986/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674986] Re: linux: 4.8.0-44.47 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674988 derivatives: 1674989 kernel-stable-phase-changed:Wednesday, 22. March 2017 21:31 UTC kernel-stable-phase:Uploaded -- swm properties -- + boot-testing-requested: true phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1674986 Title: linux: 4.8.0-44.47 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 Yakkety: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674988 derivatives: 1674989 kernel-stable-phase-changed:Wednesday, 22. March 2017 21:31 UTC kernel-stable-phase:Uploaded -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1674986/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674635] Re: Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft Hyper-v 2012r2 Gen2 VM
same results for me: b06640ee040e347f122d0e885383da3efdb15ccd works fine c7e300f2972c4d9a0dcd2d305556b14abb26be2b does not boot -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1674635 Title: Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft Hyper-v 2012r2 Gen2 VM Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: After updating the kernel inside the virtual machine to the version 4.4.0-67-generic, at the next boot the vm will stuck in a black screen at every try. An hard reset is required. The only workaround is to set the default in grub to the previous version. The virtual machine hardware is a Gen2. We are experiencing this issue on all our vps with the same kernel (around 300-400 vms). --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 20 10:30 seq crw-rw 1 root audio 116, 33 Mar 20 10:30 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=/dev/mapper/vg01--vg-swap_1 InstallationDate: Installed on 2017-03-13 (7 days ago) InstallationMedia: IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-66-generic.efi.signed root=/dev/mapper/vg01--vg-root ro nomodeset ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 RelatedPackageVersions: linux-restricted-modules-4.4.0-66-generic N/A linux-backports-modules-4.4.0-66-generic N/A linux-firmware1.157.8 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-66-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 4898-1213-1192-4801-7611-1594-99 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v1.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0: dmi.product.name: Virtual Machine dmi.product.version: Hyper-V UEFI Release v1.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674635/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1675204] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1675204 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/1675204 Title: Intel HD graphics crashes when connecting to 3 outputs (DVI+HDMI+DP) Status in linux package in Ubuntu: Incomplete Bug description: I have a very strange issue related to Intel graphics drivers (i915) with 3 connected on-board displays. I have a Xubuntu (14.04 LTS with HWE on 4.4.0-66 kernel) desktop computer running on a i7-6700K processor and on-board graphics (Mobo: AsRock z170 extreme4). I connect it to 3 displays - a 3440x1400 LG display (via onboard DP port), a 1920x1200 Dell display (via on-board HDMI), and a Sony 4k TV (via onboard DVI and a DVI-to-HDMI adapter). If I just connect my desktop to the first two displays (not the TV), everything works fine (except some minor issues). However, if I connect the 4k TV, even the TV is not on, my graphics starts to flicker every 5 min-ish (window theme turns off and then turns quickly back on); after a few flickering, the window theme will disappear, and the screen becomes weird - my chrome window will not fresh, or show blank boxes etc. If I disconnect the DVI connector to the TV (just use the LG+Dell dual-display), flickering and crash will not appear. I want to mention that, when I connect the computer to all 3 displays, I was actually able to get video output to all displays (I used arandr to configure them). I can even get 4k output to the 4k TV at 30Hz. I can't find a useful log entry when the flicking or graphics crash happens. I can only see a "CPU pipe A FIFO underrun" for pipe A/B/F (log attached at the end), but I can see many similar errors in my log and the appearance is not correlated to the flickering/crash. The "pipe A FIFO underrun" issue was previously reported in Bug#1550779. I also see "intel(0): HDMI max TMDS frequency 30KHz" entry in my Xorg.0.log file constantly, I also do not see an consistent mapping between the log entry and the flickering. Can anyone tell me how to properly debug this? what can I do to get a log for what was wrong? --- [ 145.033055] WARNING: CPU: 2 PID: 1804 at /build/linux-lts-xenial-drAJVo/linux-lts-xenial-4.4.0/ubuntu/i915/intel_pm.c:3675 skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo]() [ 145.033058] WARN_ON(!wm_changed) [ 145.033060] Modules linked in: nfsv3 pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) autofs4 rpcsec_gss_krb5 nfsv4 usblp joydev input_leds ti_usb_3410_5052 usbserial hid_generic gspca_ov534 gspca_main v4l2_common videodev media snd_usb_audio snd_usbmidi_lib usbhid snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic nvidia_uvm(POE) uas usb_storage intel_rapl x86_pkg_temp_thermal intel_powerclamp mxm_wmi coretemp kvm_intel bnep kvm rfcomm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_intel snd_hda_codec snd_hda_core nvidia_drm(POE) nvidia_modeset(POE) snd_hwdep aesni_intel snd_pcm aes_x86_64 nvidia(POE) lrw gf128mul snd_seq_midi snd_seq_midi_event glue_helper ablk_helper snd_rawmidi cryptd snd_seq snd_seq_device snd_timer serio_raw snd soundcore nfsd i915_bpo auth_rpcgss nfs_acl nfs binfmt_misc lockd grace 8250_fintek hci_uart sunrpc intel_ips drm_kms_helper btbcm pinctrl_sunrisepoint btqca fscache pinctrl_intel btintel intel_lpss_ac pi bluetooth i2c_hid intel_lpss drm hid video i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt shpchp mei_me mei mac_hid acpi_als wmi kfifo_buf industrialio acpi_pad parport_pc ppdev lp parport e1000e psmouse ptp pps_core ahci nvme libahci fjes [ 145.033284] CPU: 2 PID: 1804 Comm: Xorg Tainted: PW OE 4.4.0-66-generic #87~14.04.1-Ubuntu [ 145.033287] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z170 Extreme4, BIOS P7.00 09/09/2016 [ 145.033290] 88086e5879a0 813dc80c 88086e5879e8 [ 145.033295] c0556700 88086e5879d8 8107e9d6 88086d898000 [ 145.033300] 88086d89b000 0004 880871924b78 88086e587a64 [ 145.033305] Call Trace: [ 145.033311] [] dump_stack+0x63/0x87 [ 145.033317] [] warn_slowpath_common+0x86/0xc0 [ 145.033323] [] warn_slowpath_fmt+0x4c/0x50 [ 145.033358] [] ? ironlake_irq_handler+0x660/0xba0 [i915_bpo] [ 145.033393] [] skl_update_other_pipe
[Kernel-packages] [Bug 1673211] Re: linux-lts-trusty: 3.13.0-114.161~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid -- 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/1673211 Title: linux-lts-trusty: 3.13.0-114.161~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1673207 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1673211/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1673211] Re: linux-lts-trusty: 3.13.0-114.161~precise1 -proposed tracker
Does not need to be copied to the security pocket. ** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Invalid -- 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/1673211 Title: linux-lts-trusty: 3.13.0-114.161~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1673207 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1673211/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1675204] [NEW] Intel HD graphics crashes when connecting to 3 outputs (DVI+HDMI+DP)
Public bug reported: I have a very strange issue related to Intel graphics drivers (i915) with 3 connected on-board displays. I have a Xubuntu (14.04 LTS with HWE on 4.4.0-66 kernel) desktop computer running on a i7-6700K processor and on-board graphics (Mobo: AsRock z170 extreme4). I connect it to 3 displays - a 3440x1400 LG display (via onboard DP port), a 1920x1200 Dell display (via on-board HDMI), and a Sony 4k TV (via onboard DVI and a DVI-to-HDMI adapter). If I just connect my desktop to the first two displays (not the TV), everything works fine (except some minor issues). However, if I connect the 4k TV, even the TV is not on, my graphics starts to flicker every 5 min-ish (window theme turns off and then turns quickly back on); after a few flickering, the window theme will disappear, and the screen becomes weird - my chrome window will not fresh, or show blank boxes etc. If I disconnect the DVI connector to the TV (just use the LG+Dell dual- display), flickering and crash will not appear. I want to mention that, when I connect the computer to all 3 displays, I was actually able to get video output to all displays (I used arandr to configure them). I can even get 4k output to the 4k TV at 30Hz. I can't find a useful log entry when the flicking or graphics crash happens. I can only see a "CPU pipe A FIFO underrun" for pipe A/B/F (log attached at the end), but I can see many similar errors in my log and the appearance is not correlated to the flickering/crash. The "pipe A FIFO underrun" issue was previously reported in Bug#1550779. I also see "intel(0): HDMI max TMDS frequency 30KHz" entry in my Xorg.0.log file constantly, I also do not see an consistent mapping between the log entry and the flickering. Can anyone tell me how to properly debug this? what can I do to get a log for what was wrong? --- [ 145.033055] WARNING: CPU: 2 PID: 1804 at /build/linux-lts-xenial-drAJVo/linux-lts-xenial-4.4.0/ubuntu/i915/intel_pm.c:3675 skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo]() [ 145.033058] WARN_ON(!wm_changed) [ 145.033060] Modules linked in: nfsv3 pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) autofs4 rpcsec_gss_krb5 nfsv4 usblp joydev input_leds ti_usb_3410_5052 usbserial hid_generic gspca_ov534 gspca_main v4l2_common videodev media snd_usb_audio snd_usbmidi_lib usbhid snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic nvidia_uvm(POE) uas usb_storage intel_rapl x86_pkg_temp_thermal intel_powerclamp mxm_wmi coretemp kvm_intel bnep kvm rfcomm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_intel snd_hda_codec snd_hda_core nvidia_drm(POE) nvidia_modeset(POE) snd_hwdep aesni_intel snd_pcm aes_x86_64 nvidia(POE) lrw gf128mul snd_seq_midi snd_seq_midi_event glue_helper ablk_helper snd_rawmidi cryptd snd_seq snd_seq_device snd_timer serio_raw snd soundcore nfsd i915_bpo auth_rpcgss nfs_acl nfs binfmt_misc lockd grace 8250_fintek hci_uart sunrpc intel_ips drm_kms_helper btbcm pinctrl_sunrisepoint btqca fscache pinctrl_intel btintel intel_lpss_acpi bluetooth i2c_hid intel_lpss drm hid video i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt shpchp mei_me mei mac_hid acpi_als wmi kfifo_buf industrialio acpi_pad parport_pc ppdev lp parport e1000e psmouse ptp pps_core ahci nvme libahci fjes [ 145.033284] CPU: 2 PID: 1804 Comm: Xorg Tainted: PW OE 4.4.0-66-generic #87~14.04.1-Ubuntu [ 145.033287] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z170 Extreme4, BIOS P7.00 09/09/2016 [ 145.033290] 88086e5879a0 813dc80c 88086e5879e8 [ 145.033295] c0556700 88086e5879d8 8107e9d6 88086d898000 [ 145.033300] 88086d89b000 0004 880871924b78 88086e587a64 [ 145.033305] Call Trace: [ 145.033311] [] dump_stack+0x63/0x87 [ 145.033317] [] warn_slowpath_common+0x86/0xc0 [ 145.033323] [] warn_slowpath_fmt+0x4c/0x50 [ 145.033358] [] ? ironlake_irq_handler+0x660/0xba0 [i915_bpo] [ 145.033393] [] skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo] [ 145.033435] [] skl_update_wm+0x19a/0x6f0 [i915_bpo] [ 145.033491] [] ? chv_write8+0x390/0x390 [i915_bpo] [ 145.033551] [] ? skl_ddi_pll_disable+0x70/0x80 [i915_bpo] [ 145.033590] [] intel_update_watermarks+0x1e/0x30 [i915_bpo] [ 145.033649] [] intel_atomic_commit+0x432/0x1440 [i915_bpo] [ 145.033688] [] ? drm_atomic_set_crtc_for_connector+0x44/0xf0 [drm] [ 145.033720] [] drm_atomic_commit+0x37/0x60 [drm] [ 145.033743] [] drm_atomic_helper_set_config+0x77/0xb0 [drm_kms_helper] [ 145.033775] [] drm_mode_set_config_internal+0x64/0x100 [drm] [ 145.033805] [] drm_mode_setcrtc+0xdd/0x4f0 [drm] [ 145.033828] [] drm_ioctl+0x25d/0x4f0 [drm] [ 145.033853] [] ? drm_mode_setplane+0x1c0/0x1c0 [drm] [ 145.033860] [] ? hrtimer_start_range_ns+0x1d5/0x370 [ 145.033867] [] do_vfs_ioctl+0x2dd/0x4c0 [ 145.033872] [] ? __sys_recvmsg+0x
[Kernel-packages] [Bug 1576816] Re: sky2 Driver RX Error
This happens to me as well on Debian 8 Jessie with kernel 3.16.0-4-amd64 lspci 00:00.0 Host bridge: Intel Corporation 3200/3210 Chipset DRAM Controller (rev 01) 00:01.0 PCI bridge: Intel Corporation 3200/3210 Chipset Host-Primary PCI Express Bridge (rev 01) 00:1c.0 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 1 (rev 01) 00:1c.4 PCI bridge: Intel Corporation 82801GR/GH/GHM (ICH7 Family) PCI Express Port 5 (rev 01) 00:1c.5 PCI bridge: Intel Corporation 82801GR/GH/GHM (ICH7 Family) PCI Express Port 6 (rev 01) 00:1d.0 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #1 (rev 01) 00:1d.1 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #2 (rev 01) 00:1d.7 USB controller: Intel Corporation NM10/ICH7 Family USB2 EHCI Controller (rev 01) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev e1) 00:1f.0 ISA bridge: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge (rev 01) 00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 01) 00:1f.2 RAID bus controller: Intel Corporation 82801GR/GDH (ICH7R/ICH7DH) SATA Controller [RAID mode] (rev 01) 00:1f.3 SMBus: Intel Corporation NM10/ICH7 Family SMBus Controller (rev 01) 01:03.0 VGA compatible controller: XGI Technology Inc. (eXtreme Graphics Innovation) Z7/Z9 (XG20 core) 02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller (rev 14) 03:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller (rev 14) With Intel(R) Xeon(R) CPU X3330 @ 2.66GHz for reference and system age estimate. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1576816 Title: sky2 Driver RX Error Status in linux package in Ubuntu: Confirmed Bug description: Error occurs every time there's either heavy network load, or trying to (for example) connect with SSL in a Docker container (virtual interfaces, bridging, etc) Fills up syslog with: Apr 29 20:21:08 Pixeldust kernel: [ 107.956249] sky2 :04:00.0 eth1: rx error, status 0x5ea0100 length 1510 Apr 29 20:21:09 Pixeldust kernel: [ 107.956471] sky2 :04:00.0 eth1: rx error, status 0x5ea0100 length 1510 Apr 29 20:21:09 Pixeldust kernel: [ 107.968651] sky2 :04:00.0 eth1: rx error, status 0x5ea0100 length 1510 Apr 29 20:21:09 Pixeldust kernel: [ 107.968832] sky2 :04:00.0 eth1: rx error, status 0x5ea0100 length 1510 Apr 29 20:21:09 Pixeldust kernel: [ 108.180812] sky2 :04:00.0 eth1: rx error, status 0x5ea0100 length 1510 Apr 29 20:21:09 Pixeldust kernel: [ 108.604866] sky2 :04:00.0 eth1: rx error, status 0x5ea0100 length 1510 Apr 29 20:21:10 Pixeldust kernel: [ 109.453130] sky2 :04:00.0 eth1: rx error, status 0x5ea0100 length 1510 Apr 29 20:21:12 Pixeldust kernel: [ 111.153079] sky2 :04:00.0 eth1: rx error, status 0x5ea0100 length 1510 This issue has been around since 2007 or even earlier and still isn't fixed. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/227204 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/292445 https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/138611 System info: Description: Ubuntu 15.10 Release: 15.10 lshw output: *-pci:4 description: PCI bridge product: 82801JI (ICH10 Family) PCI Express Root Port 3 vendor: Intel Corporation physical id: 1c.2 bus info: pci@:00:1c.2 version: 00 width: 32 bits clock: 33MHz capabilities: pci normal_decode bus_master cap_list configuration: driver=pcieport resources: irq:25 ioport:d000(size=4096) memory:fbd0-fbdf ioport:c040(size=2097152) *-network description: Ethernet interface product: 88E8056 PCI-E Gigabit Ethernet Controller vendor: Marvell Technology Group Ltd. physical id: 0 bus info: pci@:06:00.0 logical name: eth0 version: 12 serial: 48:5b:39:1b:87:56 capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: bus_master cap_list rom ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=sky2 driverversion=1.30 latency=0 link=no multicast=yes port=twisted pair resources: irq:28 memory:fbdfc000-fbdf ioport:d800(size=256) memory:fbdc-fbdd *-pci:6 description: PCI bridge product: 82801JI (ICH10 Family) PCI Express Root Port 6 vendor: Intel Corporation
[Kernel-packages] [Bug 1578141] Re: Predictable interface names partially broken with igb driver
Dear all, I have a supermicro X9DRI-4LNF and experiencing the same issue. @pdxvoyd mentioned this does not happen on BIOS 3.0 but it does for us. Running latest xenial server with kernel 4.4.0-66. sudo biosdevname -d | grep device BIOS device: em1 BIOS device: em1 BIOS device: em1 BIOS device: em1 So confirming the problem with conflicting info coming from the BIOS. @pdxvoyd any news on your report to SM? been 8 months since your comment. I've open a ticket myself just in case, would love to get this resolved. best, Spike -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1578141 Title: Predictable interface names partially broken with igb driver Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Note: I'm not sure whether this is really a kernel bug or something within systemd/udev, please advise how to further debug. On a system with two GE ports, instead of getting named eno1 and eno2, I am getting eno1 and renameN. Where N starts at 3 and increases by 2 on every iteration of doing "rmmod igb;modprobe igb". The corresponding lines in dmesg look like this: [2.748429] igb :07:00.0: added PHC on eth0 [2.748431] igb :07:00.0: Intel(R) Gigabit Ethernet Network Connection [2.748433] igb :07:00.0: eth0: (PCIe:5.0Gb/s:Width x4) 00:25:90:d7:60:8e [2.748505] igb :07:00.0: eth0: PBA No: 106100-000 [2.748506] igb :07:00.0: Using MSI-X interrupts. 8 rx queue(s), 8 tx queue(s) [2.802555] igb :07:00.1: added PHC on eth1 [2.802557] igb :07:00.1: Intel(R) Gigabit Ethernet Network Connection [2.802559] igb :07:00.1: eth1: (PCIe:5.0Gb/s:Width x4) 00:25:90:d7:60:8f [2.802631] igb :07:00.1: eth1: PBA No: 106100-000 [2.802632] igb :07:00.1: Using MSI-X interrupts. 8 rx queue(s), 8 tx queue(s) [2.803618] igb :07:00.0 eno1: renamed from eth0 [2.833208] igb :07:00.1 rename3: renamed from eth1 What is even worse: Sometimes the naming changes and the second interface ends up as eno1 while the first interface is named renameN with an even N. The bad thing about this version is that when it happens while the installer is running, the installer will setup "rename2" as the primary network interface, which works fine for the installation itself, but after installation is finished and the first boot of the installed system happens, that interface will be gone, leaving the system without network connectivity. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 4 09:48 seq crw-rw 1 root audio 116, 33 May 4 09:48 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed May 4 10:00:39 2016 HibernationDevice: RESUME=/dev/mapper/compute--node37--vg-swap IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro X9DRT-HF+ PciMultimedia: ProcEnviron: LANGUAGE=en_US: TERM=screen PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic root=/dev/mapper/compute--node37--vg-root 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 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.0c dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X9DRT-HF+ dmi.board.vendor: Supermicro dmi.board.version: 0123456789 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.0c:bd05/21/2014:svnSupermicro:pnX9DRT-HF+:pvr0123456789:rvnSupermicro:rnX9DRT-HF+:rvr0123456789:cvnSup
[Kernel-packages] [Bug 1578141] Re: Predictable interface names partially broken with igb driver
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (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/1578141 Title: Predictable interface names partially broken with igb driver Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Note: I'm not sure whether this is really a kernel bug or something within systemd/udev, please advise how to further debug. On a system with two GE ports, instead of getting named eno1 and eno2, I am getting eno1 and renameN. Where N starts at 3 and increases by 2 on every iteration of doing "rmmod igb;modprobe igb". The corresponding lines in dmesg look like this: [2.748429] igb :07:00.0: added PHC on eth0 [2.748431] igb :07:00.0: Intel(R) Gigabit Ethernet Network Connection [2.748433] igb :07:00.0: eth0: (PCIe:5.0Gb/s:Width x4) 00:25:90:d7:60:8e [2.748505] igb :07:00.0: eth0: PBA No: 106100-000 [2.748506] igb :07:00.0: Using MSI-X interrupts. 8 rx queue(s), 8 tx queue(s) [2.802555] igb :07:00.1: added PHC on eth1 [2.802557] igb :07:00.1: Intel(R) Gigabit Ethernet Network Connection [2.802559] igb :07:00.1: eth1: (PCIe:5.0Gb/s:Width x4) 00:25:90:d7:60:8f [2.802631] igb :07:00.1: eth1: PBA No: 106100-000 [2.802632] igb :07:00.1: Using MSI-X interrupts. 8 rx queue(s), 8 tx queue(s) [2.803618] igb :07:00.0 eno1: renamed from eth0 [2.833208] igb :07:00.1 rename3: renamed from eth1 What is even worse: Sometimes the naming changes and the second interface ends up as eno1 while the first interface is named renameN with an even N. The bad thing about this version is that when it happens while the installer is running, the installer will setup "rename2" as the primary network interface, which works fine for the installation itself, but after installation is finished and the first boot of the installed system happens, that interface will be gone, leaving the system without network connectivity. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 4 09:48 seq crw-rw 1 root audio 116, 33 May 4 09:48 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed May 4 10:00:39 2016 HibernationDevice: RESUME=/dev/mapper/compute--node37--vg-swap IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro X9DRT-HF+ PciMultimedia: ProcEnviron: LANGUAGE=en_US: TERM=screen PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic root=/dev/mapper/compute--node37--vg-root 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 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.0c dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X9DRT-HF+ dmi.board.vendor: Supermicro dmi.board.version: 0123456789 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.0c:bd05/21/2014:svnSupermicro:pnX9DRT-HF+:pvr0123456789:rvnSupermicro:rnX9DRT-HF+:rvr0123456789:cvnSupermicro:ct17:cvr0123456789: dmi.product.name: X9DRT-HF+ dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578141/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-pack
[Kernel-packages] [Bug 1674938] fozzie (i386) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-70.91-lowlatency/fozzie__4.4.0-70.91__2017-03-22_21-51-00/results-index.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/1674938 Title: linux: 4.4.0-70.91 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674939 derivatives: 1674940,1674941,1674944,1674945 kernel-stable-phase:Uploaded kernel-stable-phase-changed:Wednesday, 22. March 2017 19:03 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1674938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674938] gonzo (i386) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-70.91-lowlatency/gonzo__4.4.0-70.91__2017-03-22_21-54-00/results-index.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/1674938 Title: linux: 4.4.0-70.91 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674939 derivatives: 1674940,1674941,1674944,1674945 kernel-stable-phase:Uploaded kernel-stable-phase-changed:Wednesday, 22. March 2017 19:03 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1674938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674986] Re: linux: 4.8.0-44.47 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1674986 Title: linux: 4.8.0-44.47 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 Yakkety: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674988 derivatives: 1674989 kernel-stable-phase-changed:Wednesday, 22. March 2017 21: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/1674986/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674635] Re: Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft Hyper-v 2012r2 Gen2 VM
c7e300f2972c4d9a0dcd2d305556b14abb26be2b does not boot -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1674635 Title: Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft Hyper-v 2012r2 Gen2 VM Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: After updating the kernel inside the virtual machine to the version 4.4.0-67-generic, at the next boot the vm will stuck in a black screen at every try. An hard reset is required. The only workaround is to set the default in grub to the previous version. The virtual machine hardware is a Gen2. We are experiencing this issue on all our vps with the same kernel (around 300-400 vms). --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 20 10:30 seq crw-rw 1 root audio 116, 33 Mar 20 10:30 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=/dev/mapper/vg01--vg-swap_1 InstallationDate: Installed on 2017-03-13 (7 days ago) InstallationMedia: IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-66-generic.efi.signed root=/dev/mapper/vg01--vg-root ro nomodeset ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 RelatedPackageVersions: linux-restricted-modules-4.4.0-66-generic N/A linux-backports-modules-4.4.0-66-generic N/A linux-firmware1.157.8 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-66-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 4898-1213-1192-4801-7611-1594-99 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v1.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0: dmi.product.name: Virtual Machine dmi.product.version: Hyper-V UEFI Release v1.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674635/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1609475] Re: Recovery mode won't allow recovery after manually installing the OS incorrectly
Hi Bill, as far as I can see, this is not a systemd but a Ubuntu problem. My Debian machines enter rescue mode just fine with systemd. Youncan circumvent this by talking to systemd directly as described in my blog post http://blog.lazy-evaluation.net/posts/linux/ubuntu-16-04-entering- recovery.html Hope that helps until the real problemmis 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/1609475 Title: Recovery mode won't allow recovery after manually installing the OS incorrectly Status in linux package in Ubuntu: Opinion Bug description: If one manually installs Ubuntu but doesn't install a boot partition, the recovery mode doesn't work. The expectation (perhaps naively) is that the recovery mode is bootable and allows one to fix the situation. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-31-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/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 Card0.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=8c695f64-12a0-4748-a431-7ab97a1e9042 InstallationDate: Installed on 2016-08-04 (33 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub NonfreeKernelModules: zfs zunicode zcommon znvpair zavl Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=a91f753b-69af-4125-a03d-0dcb63d55d38 ro net.ifnames=0 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 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 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/03/2016 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0054.2016.0503.1546 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-407 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0054.2016.0503.1546:bd05/03/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-407:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1609475/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674938] fozzie (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-70.91-lowlatency/fozzie__4.4.0-70.91__2017-03-22_21-23-00/results-index.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/1674938 Title: linux: 4.4.0-70.91 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674939 derivatives: 1674940,1674941,1674944,1674945 kernel-stable-phase:Uploaded kernel-stable-phase-changed:Wednesday, 22. March 2017 19:03 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1674938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674938] rumford (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-70.91-lowlatency/rumford__4.4.0-70.91__2017-03-22_21-28-00/results-index.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/1674938 Title: linux: 4.4.0-70.91 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674939 derivatives: 1674940,1674941,1674944,1674945 kernel-stable-phase:Uploaded kernel-stable-phase-changed:Wednesday, 22. March 2017 19:03 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1674938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674635] Re: Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft Hyper-v 2012r2 Gen2 VM
I built the next test kernel, up to the following commit: c7e300f2972c4d9a0dcd2d305556b14abb26be2b The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1674635/c7e300f2972c4d9a0dcd2d305556b14abb26be2b Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results. Thanks in advance -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1674635 Title: Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft Hyper-v 2012r2 Gen2 VM Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: After updating the kernel inside the virtual machine to the version 4.4.0-67-generic, at the next boot the vm will stuck in a black screen at every try. An hard reset is required. The only workaround is to set the default in grub to the previous version. The virtual machine hardware is a Gen2. We are experiencing this issue on all our vps with the same kernel (around 300-400 vms). --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 20 10:30 seq crw-rw 1 root audio 116, 33 Mar 20 10:30 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=/dev/mapper/vg01--vg-swap_1 InstallationDate: Installed on 2017-03-13 (7 days ago) InstallationMedia: IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-66-generic.efi.signed root=/dev/mapper/vg01--vg-root ro nomodeset ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 RelatedPackageVersions: linux-restricted-modules-4.4.0-66-generic N/A linux-backports-modules-4.4.0-66-generic N/A linux-firmware1.157.8 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-66-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 4898-1213-1192-4801-7611-1594-99 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v1.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0: dmi.product.name: Virtual Machine dmi.product.version: Hyper-V UEFI Release v1.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674635/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674938] gonzo (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-70.91-lowlatency/gonzo__4.4.0-70.91__2017-03-22_21-24-00/results-index.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/1674938 Title: linux: 4.4.0-70.91 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674939 derivatives: 1674940,1674941,1674944,1674945 kernel-stable-phase:Uploaded kernel-stable-phase-changed:Wednesday, 22. March 2017 19:03 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1674938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674986] Re: linux: 4.8.0-44.47 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-signed Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de Souza Cascardo (cascardo) ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674988 derivatives: 1674989 + kernel-stable-phase-changed:Wednesday, 22. March 2017 21:31 UTC + kernel-stable-phase:Uploaded ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674988 derivatives: 1674989 kernel-stable-phase-changed:Wednesday, 22. March 2017 21:31 UTC kernel-stable-phase:Uploaded + + -- swm properties -- + phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1674986 Title: linux: 4.8.0-44.47 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674988 derivatives: 1674989 kernel-stable-phase-changed:Wednesday, 22. March 2017 21: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/1674986/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1675178] [NEW] package linux-firmware (not installed) failed to install/upgrade: próba nadpisania "/lib/firmware/iwlwifi-6000g2b-6.ucode", który istnieje także w pakiecie firmwa
Public bug reported: first installing firmware-iwlwifi than: linux-firmware error occured ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware (not installed) ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook ApportVersion: 2.20.1-0ubuntu2.5 AptOrdering: linux-firmware: Install linux-firmware: Configure NULL: ConfigurePending Architecture: amd64 Date: Wed Mar 22 22:17:46 2017 DpkgTerminalLog: Przygotowywanie do rozpakowania pakietu .../linux-firmware_1.157.8_all.deb ... Rozpakowywanie pakietu linux-firmware (1.157.8) ... dpkg: błąd przetwarzania archiwum /var/cache/apt/archives/linux-firmware_1.157.8_all.deb (--unpack): próba nadpisania "/lib/firmware/iwlwifi-6000g2b-6.ucode", który istnieje także w pakiecie firmware-iwlwifi 0.43 ErrorMessage: próba nadpisania "/lib/firmware/iwlwifi-6000g2b-6.ucode", który istnieje także w pakiecie firmware-iwlwifi 0.43 InstallationDate: Installed on 2016-07-25 (240 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: linux-firmware Title: package linux-firmware (not installed) failed to install/upgrade: próba nadpisania "/lib/firmware/iwlwifi-6000g2b-6.ucode", który istnieje także w pakiecie firmware-iwlwifi 0.43 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1675178 Title: package linux-firmware (not installed) failed to install/upgrade: próba nadpisania "/lib/firmware/iwlwifi-6000g2b-6.ucode", który istnieje także w pakiecie firmware-iwlwifi 0.43 Status in linux-firmware package in Ubuntu: New Bug description: first installing firmware-iwlwifi than: linux-firmware error occured ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware (not installed) ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook ApportVersion: 2.20.1-0ubuntu2.5 AptOrdering: linux-firmware: Install linux-firmware: Configure NULL: ConfigurePending Architecture: amd64 Date: Wed Mar 22 22:17:46 2017 DpkgTerminalLog: Przygotowywanie do rozpakowania pakietu .../linux-firmware_1.157.8_all.deb ... Rozpakowywanie pakietu linux-firmware (1.157.8) ... dpkg: błąd przetwarzania archiwum /var/cache/apt/archives/linux-firmware_1.157.8_all.deb (--unpack): próba nadpisania "/lib/firmware/iwlwifi-6000g2b-6.ucode", który istnieje także w pakiecie firmware-iwlwifi 0.43 ErrorMessage: próba nadpisania "/lib/firmware/iwlwifi-6000g2b-6.ucode", który istnieje także w pakiecie firmware-iwlwifi 0.43 InstallationDate: Installed on 2016-07-25 (240 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: linux-firmware Title: package linux-firmware (not installed) failed to install/upgrade: próba nadpisania "/lib/firmware/iwlwifi-6000g2b-6.ucode", który istnieje także w pakiecie firmware-iwlwifi 0.43 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1675178/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1675046] Re: [ARM64] Support systems where the physical memory footprint exceeds the size of the linear mapping.
These are in the next branch of the maintainer's tree - https://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git/log/?h=next -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1675046 Title: [ARM64] Support systems where the physical memory footprint exceeds the size of the linear mapping. Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Kernel might fail booting on systems where the physical memory footprint exceeds the size of the linear mapping. The following patches addresses this issue: [v2,1/2] efi: arm-stub: Correct FDT and initrd allocation rules for arm64 https://patchwork.kernel.org/patch/9565537/ [v2,2/2] efi: arm-stub: Round up FDT allocation to mapping size https://patchwork.kernel.org/patch/9565539 [Testing] These patches were regression tested. Patches were applied to Zesty latest and boots on a KVM instance and on QDF2400 ARM64 Qualcomm server. At this time do not have systems with high memory to test with. [Regression Potential] Changes are confined to ARM architecture, patches apply cleanly to Ubuntu-4.10.0-13.15. Potential for any regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1675046/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674938] naumann (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-70.91-lowlatency/naumann__4.4.0-70.91__2017-03-22_20-55-00/results-index.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/1674938 Title: linux: 4.4.0-70.91 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674939 derivatives: 1674940,1674941,1674944,1674945 kernel-stable-phase:Uploaded kernel-stable-phase-changed:Wednesday, 22. March 2017 19:03 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1674938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674938] fozzie (i386) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-70.91-generic/fozzie__4.4.0-70.91__2017-03-22_20-54-00/results-index.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/1674938 Title: linux: 4.4.0-70.91 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674939 derivatives: 1674940,1674941,1674944,1674945 kernel-stable-phase:Uploaded kernel-stable-phase-changed:Wednesday, 22. March 2017 19:03 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1674938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674938] hainzel (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-70.91-lowlatency/hainzel__4.4.0-70.91__2017-03-22_21-03-00/results-index.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/1674938 Title: linux: 4.4.0-70.91 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674939 derivatives: 1674940,1674941,1674944,1674945 kernel-stable-phase:Uploaded kernel-stable-phase-changed:Wednesday, 22. March 2017 19:03 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1674938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674938] gonzo (i386) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-70.91-generic/gonzo__4.4.0-70.91__2017-03-22_20-55-00/results-index.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/1674938 Title: linux: 4.4.0-70.91 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674939 derivatives: 1674940,1674941,1674944,1674945 kernel-stable-phase:Uploaded kernel-stable-phase-changed:Wednesday, 22. March 2017 19:03 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1674938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674938] archytas (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-70.91-lowlatency/archytas__4.4.0-70.91__2017-03-22_21-00-00/results-index.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/1674938 Title: linux: 4.4.0-70.91 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674939 derivatives: 1674940,1674941,1674944,1674945 kernel-stable-phase:Uploaded kernel-stable-phase-changed:Wednesday, 22. March 2017 19:03 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1674938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674938] amaura (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-70.91-lowlatency/amaura__4.4.0-70.91__2017-03-22_20-39-00/results-index.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/1674938 Title: linux: 4.4.0-70.91 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674939 derivatives: 1674940,1674941,1674944,1674945 kernel-stable-phase:Uploaded kernel-stable-phase-changed:Wednesday, 22. March 2017 19:03 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1674938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674938] rumford (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-70.91-generic/rumford__4.4.0-70.91__2017-03-22_20-43-00/results-index.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/1674938 Title: linux: 4.4.0-70.91 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674939 derivatives: 1674940,1674941,1674944,1674945 kernel-stable-phase:Uploaded kernel-stable-phase-changed:Wednesday, 22. March 2017 19:03 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1674938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674938] modoc (ppc64el) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-70.91-generic/modoc__4.4.0-70.91__2017-03-22_20-39-00/results-index.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/1674938 Title: linux: 4.4.0-70.91 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674939 derivatives: 1674940,1674941,1674944,1674945 kernel-stable-phase:Uploaded kernel-stable-phase-changed:Wednesday, 22. March 2017 19:03 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1674938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674938] fozzie (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-70.91-generic/fozzie__4.4.0-70.91__2017-03-22_20-29-00/results-index.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/1674938 Title: linux: 4.4.0-70.91 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674939 derivatives: 1674940,1674941,1674944,1674945 kernel-stable-phase:Uploaded kernel-stable-phase-changed:Wednesday, 22. March 2017 19:03 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1674938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674938] hainzel (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-70.91-generic/hainzel__4.4.0-70.91__2017-03-22_20-30-00/results-index.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/1674938 Title: linux: 4.4.0-70.91 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674939 derivatives: 1674940,1674941,1674944,1674945 kernel-stable-phase:Uploaded kernel-stable-phase-changed:Wednesday, 22. March 2017 19:03 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1674938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674938] ms10-34-mcdivittB0-kernel (arm64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-70.91-generic/ms10-34-mcdivittB0-kernel__4.4.0-70.91__2017-03-22_20-33-00/results-index.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/1674938 Title: linux: 4.4.0-70.91 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674939 derivatives: 1674940,1674941,1674944,1674945 kernel-stable-phase:Uploaded kernel-stable-phase-changed:Wednesday, 22. March 2017 19:03 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1674938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674938] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-70.91-generic/ms10-35-mcdivittB0-kernel__4.4.0-70.91__2017-03-22_20-33-00/results-index.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/1674938 Title: linux: 4.4.0-70.91 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674939 derivatives: 1674940,1674941,1674944,1674945 kernel-stable-phase:Uploaded kernel-stable-phase-changed:Wednesday, 22. March 2017 19:03 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1674938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674938] archytas (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-70.91-generic/archytas__4.4.0-70.91__2017-03-22_20-29-00/results-index.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/1674938 Title: linux: 4.4.0-70.91 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674939 derivatives: 1674940,1674941,1674944,1674945 kernel-stable-phase:Uploaded kernel-stable-phase-changed:Wednesday, 22. March 2017 19:03 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1674938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674938] gonzo (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-70.91-generic/gonzo__4.4.0-70.91__2017-03-22_20-29-00/results-index.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/1674938 Title: linux: 4.4.0-70.91 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674939 derivatives: 1674940,1674941,1674944,1674945 kernel-stable-phase:Uploaded kernel-stable-phase-changed:Wednesday, 22. March 2017 19:03 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1674938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674938] naumann (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-70.91-generic/naumann__4.4.0-70.91__2017-03-22_20-28-00/results-index.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/1674938 Title: linux: 4.4.0-70.91 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674939 derivatives: 1674940,1674941,1674944,1674945 kernel-stable-phase:Uploaded kernel-stable-phase-changed:Wednesday, 22. March 2017 19:03 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1674938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1668042] Re: [Xenial - 16.04 ]Bonding driver - stack corruption when trying to copy 20 bytes to a sockaddr
I backported commit 1533e77315220 to Trusty and built a test kernel. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1668042/trusty Can you test this kernel and see if it resolves this bug for Trusty? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1668042 Title: [Xenial - 16.04 ]Bonding driver - stack corruption when trying to copy 20 bytes to a sockaddr Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: Fix Committed Bug description: In Ubuntu Xenial with kernel 4.4.0-65, we get kernel Panic after scenario [1]. patch [2] should fix the issue When using an IPoIB bond currently only active-backup mode is a valid use case and this commit strengthens it. Since commit 2ab82852a270 ("net/bonding: Enable bonding to enslave netdevices not supporting set_mac_address()") was introduced till 4.7-rc1, IPoIB didn't support the set_mac_address ndo, and hence the fail over mac policy always applied to IPoIB bonds. With the introduction of commit 492a7e67ff83 ("IB/IPoIB: Allow setting the device address"), that doesn't hold and practically IPoIB bonds are broken as of that. To fix it, lets go to fail over mac if the device doesn't support the ndo OR this is IPoIB device. As a by-product, this commit also prevents a stack corruption which occurred when trying to copy 20 bytes (IPoIB) device address to a sockaddr struct that has only 16 bytes of storage. [1] Get panic after create bond with down/updelay and restart NIC driver Configure bond with down/updelay cat /etc/network/interfaces auto bond1 iface bond1 inet static address 31.136.42.17 netmask 255.255.0.0 bond-slaves ib0 ib1 bond-miimon 100 bond-updelay 5000 bond-mode active-backup bond-primary ib1 bond-downdelay 5000 auto ib0 iface ib0 inet manual bond-master bond1 auto ib1 iface ib1 inet manual bond-master bond1 modprobe -r [2] 1533e77315220dc1d5ec3bd6d9fe32e2aa0a74c0 net/bonding: Enforce active-backup policy for IPoIB bonds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668042/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674938] amaura (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-70.91-generic/amaura__4.4.0-70.91__2017-03-22_20-20-00/results-index.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/1674938 Title: linux: 4.4.0-70.91 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674939 derivatives: 1674940,1674941,1674944,1674945 kernel-stable-phase:Uploaded kernel-stable-phase-changed:Wednesday, 22. March 2017 19:03 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1674938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674938] Re: linux: 4.4.0-70.91 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader (smb) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader (smb) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674939 derivatives: 1674940,1674941,1674944,1674945 kernel-stable-phase:Uploaded kernel-stable-phase-changed:Wednesday, 22. March 2017 19:03 UTC -- swm properties -- + boot-testing-requested: true phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1674938 Title: linux: 4.4.0-70.91 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674939 derivatives: 1674940,1674941,1674944,1674945 kernel-stable-phase:Uploaded kernel-stable-phase-changed:Wednesday, 22. March 2017 19:03 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1674938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674635] Re: Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft Hyper-v 2012r2 Gen2 VM
b06640ee040e347f122d0e885383da3efdb15ccd works fine -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1674635 Title: Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft Hyper-v 2012r2 Gen2 VM Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: After updating the kernel inside the virtual machine to the version 4.4.0-67-generic, at the next boot the vm will stuck in a black screen at every try. An hard reset is required. The only workaround is to set the default in grub to the previous version. The virtual machine hardware is a Gen2. We are experiencing this issue on all our vps with the same kernel (around 300-400 vms). --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 20 10:30 seq crw-rw 1 root audio 116, 33 Mar 20 10:30 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=/dev/mapper/vg01--vg-swap_1 InstallationDate: Installed on 2017-03-13 (7 days ago) InstallationMedia: IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-66-generic.efi.signed root=/dev/mapper/vg01--vg-root ro nomodeset ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 RelatedPackageVersions: linux-restricted-modules-4.4.0-66-generic N/A linux-backports-modules-4.4.0-66-generic N/A linux-firmware1.157.8 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-66-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 4898-1213-1192-4801-7611-1594-99 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v1.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0: dmi.product.name: Virtual Machine dmi.product.version: Hyper-V UEFI Release v1.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674635/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674635] Re: Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft Hyper-v 2012r2 Gen2 VM
During the bisect, some of the test kernels will be good and not exhibit the bug, while others will be bad. I built the next test kernel, up to the following commit: b06640ee040e347f122d0e885383da3efdb15ccd The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1674635 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results. Thanks in advance -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1674635 Title: Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft Hyper-v 2012r2 Gen2 VM Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: After updating the kernel inside the virtual machine to the version 4.4.0-67-generic, at the next boot the vm will stuck in a black screen at every try. An hard reset is required. The only workaround is to set the default in grub to the previous version. The virtual machine hardware is a Gen2. We are experiencing this issue on all our vps with the same kernel (around 300-400 vms). --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 20 10:30 seq crw-rw 1 root audio 116, 33 Mar 20 10:30 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=/dev/mapper/vg01--vg-swap_1 InstallationDate: Installed on 2017-03-13 (7 days ago) InstallationMedia: IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-66-generic.efi.signed root=/dev/mapper/vg01--vg-root ro nomodeset ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 RelatedPackageVersions: linux-restricted-modules-4.4.0-66-generic N/A linux-backports-modules-4.4.0-66-generic N/A linux-firmware1.157.8 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-66-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 4898-1213-1192-4801-7611-1594-99 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v1.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0: dmi.product.name: Virtual Machine dmi.product.version: Hyper-V UEFI Release v1.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674635/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674635] Re: Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft Hyper-v 2012r2 Gen2 VM
I have the same problem in my homelab: Host: Windows 10 Pro Hyper-V VMs: Ubuntu Server 16.04.2 with latest updates, one vm is clean and rest have only one service installed (perforce server, plex server, etc.). Test kernel df0a1b9cce531e1718dbb966b1e0075b3667598f booted up without errors. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1674635 Title: Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft Hyper-v 2012r2 Gen2 VM Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: After updating the kernel inside the virtual machine to the version 4.4.0-67-generic, at the next boot the vm will stuck in a black screen at every try. An hard reset is required. The only workaround is to set the default in grub to the previous version. The virtual machine hardware is a Gen2. We are experiencing this issue on all our vps with the same kernel (around 300-400 vms). --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 20 10:30 seq crw-rw 1 root audio 116, 33 Mar 20 10:30 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=/dev/mapper/vg01--vg-swap_1 InstallationDate: Installed on 2017-03-13 (7 days ago) InstallationMedia: IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-66-generic.efi.signed root=/dev/mapper/vg01--vg-root ro nomodeset ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 RelatedPackageVersions: linux-restricted-modules-4.4.0-66-generic N/A linux-backports-modules-4.4.0-66-generic N/A linux-firmware1.157.8 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-66-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 4898-1213-1192-4801-7611-1594-99 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v1.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0: dmi.product.name: Virtual Machine dmi.product.version: Hyper-V UEFI Release v1.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674635/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1654073] dev
Default Comment by Bridge ** Attachment added: "dev" https://bugs.launchpad.net/bugs/1654073/+attachment/4842651/+files/dev -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1654073 Title: Ubuntu 17.04: machine crashes with Oops in dccp_v4_ctl_send_reset while running stress-ng. Status in linux package in Ubuntu: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: == Comment: #0 - PAVITHRA R. PRAKASH - 2016-12-28 03:39:50 == ---Problem Description--- Ubuntu 17.04: machine crashes with Oops while running stress-ng. ---Steps followed- 1. Install 17.04 on NV machine. 2. apt-get install stress-ng 3. stress-ng -a 0 Logs dccp af_alg joydev input_leds mac_hid at24 nvmem_core ofpart cmdlinepart powernv_flash mtd opal_prd powernv_rng ipmi_powernv ipmi_msghandler ibmpowernv uio_pdrv_genirq uio vmx_crypto ib_iser rdma_cm iw_cm ib_cm ib_core configfs iscsi_tcp libiscsi_tcp libiscsi scsi_tran[165938083361,3] OPAL: Trying a CPU re-init with flags: 0x1 [166456504189,3] OPAL: CPU 0x29 not in OPAL ! [167510150475,3] OPAL: Trying a CPU re-init with flags: 0x2 [168022446397,3] OPAL: CPU 0x29 not in OPAL ! sport_iscsi ip_tables x_tables autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear ses enclosure scsi_transport_sas hid_generic ast i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt bnx2x fb_sys_fops drm aacraid tg3 usbhid uas hid usb_storage mdio ahci libcrc32c libahci crc32c_vpmsum [ 237.047216] CPU: 33 PID: 34694 Comm: stress-ng-dccp Not tainted 4.9.0-11-generic #12-Ubuntu [ 237.047315] task: c03312a69400 task.stack: c03779698000 [ 237.047402] NIP: d0002e7b0a7c LR: d0002e7b21cc CTR: c0a0dd00 [ 237.047509] REGS: c03fff68f670 TRAP: 0300 Not tainted (4.9.0-11-generic) [ 237.047613] MSR: 90010280b033 [ 237.049028] CR: 24002282 XER: 2000 [ 237.049103] CFAR: c0008a60 DAR: 02f4 DSISR: 4000 SOFTE: 1 GPR00: d0002e7b21cc c03fff68f8f0 d0002e7bb670 0001 GPR04: c02b5dbdc400 c03c74c0a460 0474 c03c74c0a474 GPR08: c03c74c0a000 c0348cd25200 GPR12: 2200 c7b72900 c03fff68c000 GPR16: 0040 0001 2713 GPR20: cc84 017f 017f c13b2f00 GPR24: 0001 0001 0004 GPR28: c13b2f00 c03c74c0a474 c02b5dbdc400 NIP [d0002e7b0a7c] dccp_v4_ctl_send_reset+0xa4/0x2f0 [dccp_ipv4] [ 237.051403] LR [d0002e7b21cc] dccp_v4_rcv+0x5d4/0x850 [dccp_ipv4] [ 237.051486] Call Trace: [ 237.051529] [c03fff68f8f0] [2713cc84] 0x2713cc84 (unreliable) [ 237.051649] [c03fff68f970] [d0002e7b21cc] dccp_v4_rcv+0x5d4/0x850 [dccp_ipv4] [ 237.051779] [c03fff68fa50] [c0a01e40] ip_local_deliver_finish+0x170/0x350 [ 237.051932] [c03fff68faa0] [c0a0276c] ip_local_deliver+0x5c/0x130 [ 237.052038] [c03fff68fb10] [c0a02278] ip_rcv_finish+0x258/0x510 [ 237.052151] [c03fff68fba0] [c0a02b44] ip_rcv+0x304/0x420 [ 237.052263] [c03fff68fc30] [c09a28bc] __netif_receive_skb_core+0x97c/0xda0 [ 237.052388] [c03fff68fd10] [c09a7ab4] process_backlog+0xd4/0x1e0 [ 237.052489] [c03fff68fd80] [c09a6f0c] net_rx_action+0x35c/0x480 [ 237.052603] [c03fff68fe90] [c0b22a6c] __do_softirq+0x18c/0x3fc [ 237.052726] [c03fff68ff90] [c0029fb0] call_do_softirq+0x14/0x24 [ 237.052848] [c0377969b920] [c001765c] do_softirq_own_stack+0x5c/0xa0 [ 237.052992] [c0377969b960] [c00cfd48] do_softirq.part.3+0x68/0x90 [ 237.053112] [c0377969b990] [c00cfe44] __local_bh_enable_ip+0xd4/0x100 [ 237.053240] [c0377969b9b0] [c0a06724] ip_finish_output2+0x244/0x460 [ 237.053372] [c0377969ba50] [c0a0977c] ip_output+0xcc/0x180 [ 237.053485] [c0377969bae0] [c0a08c78] ip_local_out+0x68/0x90 [ 237.053607] [c0377969bb20] [d00021966978] dccp_transmit_skb+0x320/0x550 [dccp] [ 237.053739] [c0377969bb90] [d0002196732c] dccp_connect+0xf4/0x1f0 [dccp] [ 237.053890] [c0377969bc10] [d0002e7b0320] dccp_v4_connect+0x308/0x400 [dccp_ipv4] [ 237.054213] [c0377969bc90] [c0a51678] __inet_stream_connect+0x158/0x400 [ 237.065276] [c0377969bd20] [c0a51978] inet_stream_connect+0x58/0x90 [ 237.074757] [c0377969bd60] [c097eeac] SyS_connect+0x10c/0x130 [ 237.092889] [c0377969be30] [c000bd
[Kernel-packages] [Bug 1654073] net
Default Comment by Bridge ** Attachment added: "net" https://bugs.launchpad.net/bugs/1654073/+attachment/4842650/+files/net -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1654073 Title: Ubuntu 17.04: machine crashes with Oops in dccp_v4_ctl_send_reset while running stress-ng. Status in linux package in Ubuntu: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: == Comment: #0 - PAVITHRA R. PRAKASH - 2016-12-28 03:39:50 == ---Problem Description--- Ubuntu 17.04: machine crashes with Oops while running stress-ng. ---Steps followed- 1. Install 17.04 on NV machine. 2. apt-get install stress-ng 3. stress-ng -a 0 Logs dccp af_alg joydev input_leds mac_hid at24 nvmem_core ofpart cmdlinepart powernv_flash mtd opal_prd powernv_rng ipmi_powernv ipmi_msghandler ibmpowernv uio_pdrv_genirq uio vmx_crypto ib_iser rdma_cm iw_cm ib_cm ib_core configfs iscsi_tcp libiscsi_tcp libiscsi scsi_tran[165938083361,3] OPAL: Trying a CPU re-init with flags: 0x1 [166456504189,3] OPAL: CPU 0x29 not in OPAL ! [167510150475,3] OPAL: Trying a CPU re-init with flags: 0x2 [168022446397,3] OPAL: CPU 0x29 not in OPAL ! sport_iscsi ip_tables x_tables autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear ses enclosure scsi_transport_sas hid_generic ast i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt bnx2x fb_sys_fops drm aacraid tg3 usbhid uas hid usb_storage mdio ahci libcrc32c libahci crc32c_vpmsum [ 237.047216] CPU: 33 PID: 34694 Comm: stress-ng-dccp Not tainted 4.9.0-11-generic #12-Ubuntu [ 237.047315] task: c03312a69400 task.stack: c03779698000 [ 237.047402] NIP: d0002e7b0a7c LR: d0002e7b21cc CTR: c0a0dd00 [ 237.047509] REGS: c03fff68f670 TRAP: 0300 Not tainted (4.9.0-11-generic) [ 237.047613] MSR: 90010280b033 [ 237.049028] CR: 24002282 XER: 2000 [ 237.049103] CFAR: c0008a60 DAR: 02f4 DSISR: 4000 SOFTE: 1 GPR00: d0002e7b21cc c03fff68f8f0 d0002e7bb670 0001 GPR04: c02b5dbdc400 c03c74c0a460 0474 c03c74c0a474 GPR08: c03c74c0a000 c0348cd25200 GPR12: 2200 c7b72900 c03fff68c000 GPR16: 0040 0001 2713 GPR20: cc84 017f 017f c13b2f00 GPR24: 0001 0001 0004 GPR28: c13b2f00 c03c74c0a474 c02b5dbdc400 NIP [d0002e7b0a7c] dccp_v4_ctl_send_reset+0xa4/0x2f0 [dccp_ipv4] [ 237.051403] LR [d0002e7b21cc] dccp_v4_rcv+0x5d4/0x850 [dccp_ipv4] [ 237.051486] Call Trace: [ 237.051529] [c03fff68f8f0] [2713cc84] 0x2713cc84 (unreliable) [ 237.051649] [c03fff68f970] [d0002e7b21cc] dccp_v4_rcv+0x5d4/0x850 [dccp_ipv4] [ 237.051779] [c03fff68fa50] [c0a01e40] ip_local_deliver_finish+0x170/0x350 [ 237.051932] [c03fff68faa0] [c0a0276c] ip_local_deliver+0x5c/0x130 [ 237.052038] [c03fff68fb10] [c0a02278] ip_rcv_finish+0x258/0x510 [ 237.052151] [c03fff68fba0] [c0a02b44] ip_rcv+0x304/0x420 [ 237.052263] [c03fff68fc30] [c09a28bc] __netif_receive_skb_core+0x97c/0xda0 [ 237.052388] [c03fff68fd10] [c09a7ab4] process_backlog+0xd4/0x1e0 [ 237.052489] [c03fff68fd80] [c09a6f0c] net_rx_action+0x35c/0x480 [ 237.052603] [c03fff68fe90] [c0b22a6c] __do_softirq+0x18c/0x3fc [ 237.052726] [c03fff68ff90] [c0029fb0] call_do_softirq+0x14/0x24 [ 237.052848] [c0377969b920] [c001765c] do_softirq_own_stack+0x5c/0xa0 [ 237.052992] [c0377969b960] [c00cfd48] do_softirq.part.3+0x68/0x90 [ 237.053112] [c0377969b990] [c00cfe44] __local_bh_enable_ip+0xd4/0x100 [ 237.053240] [c0377969b9b0] [c0a06724] ip_finish_output2+0x244/0x460 [ 237.053372] [c0377969ba50] [c0a0977c] ip_output+0xcc/0x180 [ 237.053485] [c0377969bae0] [c0a08c78] ip_local_out+0x68/0x90 [ 237.053607] [c0377969bb20] [d00021966978] dccp_transmit_skb+0x320/0x550 [dccp] [ 237.053739] [c0377969bb90] [d0002196732c] dccp_connect+0xf4/0x1f0 [dccp] [ 237.053890] [c0377969bc10] [d0002e7b0320] dccp_v4_connect+0x308/0x400 [dccp_ipv4] [ 237.054213] [c0377969bc90] [c0a51678] __inet_stream_connect+0x158/0x400 [ 237.065276] [c0377969bd20] [c0a51978] inet_stream_connect+0x58/0x90 [ 237.074757] [c0377969bd60] [c097eeac] SyS_connect+0x10c/0x130 [ 237.092889] [c0377969be30] [c000bd
[Kernel-packages] [Bug 1654073] rxskb
Default Comment by Bridge ** Attachment added: "rxskb" https://bugs.launchpad.net/bugs/1654073/+attachment/4842649/+files/dccp_v4_ctl_send_reset.rxskb -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1654073 Title: Ubuntu 17.04: machine crashes with Oops in dccp_v4_ctl_send_reset while running stress-ng. Status in linux package in Ubuntu: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: == Comment: #0 - PAVITHRA R. PRAKASH - 2016-12-28 03:39:50 == ---Problem Description--- Ubuntu 17.04: machine crashes with Oops while running stress-ng. ---Steps followed- 1. Install 17.04 on NV machine. 2. apt-get install stress-ng 3. stress-ng -a 0 Logs dccp af_alg joydev input_leds mac_hid at24 nvmem_core ofpart cmdlinepart powernv_flash mtd opal_prd powernv_rng ipmi_powernv ipmi_msghandler ibmpowernv uio_pdrv_genirq uio vmx_crypto ib_iser rdma_cm iw_cm ib_cm ib_core configfs iscsi_tcp libiscsi_tcp libiscsi scsi_tran[165938083361,3] OPAL: Trying a CPU re-init with flags: 0x1 [166456504189,3] OPAL: CPU 0x29 not in OPAL ! [167510150475,3] OPAL: Trying a CPU re-init with flags: 0x2 [168022446397,3] OPAL: CPU 0x29 not in OPAL ! sport_iscsi ip_tables x_tables autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear ses enclosure scsi_transport_sas hid_generic ast i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt bnx2x fb_sys_fops drm aacraid tg3 usbhid uas hid usb_storage mdio ahci libcrc32c libahci crc32c_vpmsum [ 237.047216] CPU: 33 PID: 34694 Comm: stress-ng-dccp Not tainted 4.9.0-11-generic #12-Ubuntu [ 237.047315] task: c03312a69400 task.stack: c03779698000 [ 237.047402] NIP: d0002e7b0a7c LR: d0002e7b21cc CTR: c0a0dd00 [ 237.047509] REGS: c03fff68f670 TRAP: 0300 Not tainted (4.9.0-11-generic) [ 237.047613] MSR: 90010280b033 [ 237.049028] CR: 24002282 XER: 2000 [ 237.049103] CFAR: c0008a60 DAR: 02f4 DSISR: 4000 SOFTE: 1 GPR00: d0002e7b21cc c03fff68f8f0 d0002e7bb670 0001 GPR04: c02b5dbdc400 c03c74c0a460 0474 c03c74c0a474 GPR08: c03c74c0a000 c0348cd25200 GPR12: 2200 c7b72900 c03fff68c000 GPR16: 0040 0001 2713 GPR20: cc84 017f 017f c13b2f00 GPR24: 0001 0001 0004 GPR28: c13b2f00 c03c74c0a474 c02b5dbdc400 NIP [d0002e7b0a7c] dccp_v4_ctl_send_reset+0xa4/0x2f0 [dccp_ipv4] [ 237.051403] LR [d0002e7b21cc] dccp_v4_rcv+0x5d4/0x850 [dccp_ipv4] [ 237.051486] Call Trace: [ 237.051529] [c03fff68f8f0] [2713cc84] 0x2713cc84 (unreliable) [ 237.051649] [c03fff68f970] [d0002e7b21cc] dccp_v4_rcv+0x5d4/0x850 [dccp_ipv4] [ 237.051779] [c03fff68fa50] [c0a01e40] ip_local_deliver_finish+0x170/0x350 [ 237.051932] [c03fff68faa0] [c0a0276c] ip_local_deliver+0x5c/0x130 [ 237.052038] [c03fff68fb10] [c0a02278] ip_rcv_finish+0x258/0x510 [ 237.052151] [c03fff68fba0] [c0a02b44] ip_rcv+0x304/0x420 [ 237.052263] [c03fff68fc30] [c09a28bc] __netif_receive_skb_core+0x97c/0xda0 [ 237.052388] [c03fff68fd10] [c09a7ab4] process_backlog+0xd4/0x1e0 [ 237.052489] [c03fff68fd80] [c09a6f0c] net_rx_action+0x35c/0x480 [ 237.052603] [c03fff68fe90] [c0b22a6c] __do_softirq+0x18c/0x3fc [ 237.052726] [c03fff68ff90] [c0029fb0] call_do_softirq+0x14/0x24 [ 237.052848] [c0377969b920] [c001765c] do_softirq_own_stack+0x5c/0xa0 [ 237.052992] [c0377969b960] [c00cfd48] do_softirq.part.3+0x68/0x90 [ 237.053112] [c0377969b990] [c00cfe44] __local_bh_enable_ip+0xd4/0x100 [ 237.053240] [c0377969b9b0] [c0a06724] ip_finish_output2+0x244/0x460 [ 237.053372] [c0377969ba50] [c0a0977c] ip_output+0xcc/0x180 [ 237.053485] [c0377969bae0] [c0a08c78] ip_local_out+0x68/0x90 [ 237.053607] [c0377969bb20] [d00021966978] dccp_transmit_skb+0x320/0x550 [dccp] [ 237.053739] [c0377969bb90] [d0002196732c] dccp_connect+0xf4/0x1f0 [dccp] [ 237.053890] [c0377969bc10] [d0002e7b0320] dccp_v4_connect+0x308/0x400 [dccp_ipv4] [ 237.054213] [c0377969bc90] [c0a51678] __inet_stream_connect+0x158/0x400 [ 237.065276] [c0377969bd20] [c0a51978] inet_stream_connect+0x58/0x90 [ 237.074757] [c0377969bd60] [c097eeac] SyS_connect+0x10c/0x130 [ 237.092889] [c
[Kernel-packages] [Bug 1654073] commit 449809a66c1d0b1563dee84493e14bf3104d2d7e
--- Comment on attachment From ru...@us.ibm.com 2017-03-20 11:13 EDT--- Hello Canonical. Applying dccp commit 449809a66c1d0b1563dee84493e14bf3104d2d7e on top of the 4.10.0-13 kernel source appears to have resolved this issue. Please consider including this commit: tcp/dccp: block BH for SYN processing ** Attachment added: "commit 449809a66c1d0b1563dee84493e14bf3104d2d7e" https://bugs.launchpad.net/bugs/1654073/+attachment/4842652/+files/dccp_syn_bh.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1654073 Title: Ubuntu 17.04: machine crashes with Oops in dccp_v4_ctl_send_reset while running stress-ng. Status in linux package in Ubuntu: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: == Comment: #0 - PAVITHRA R. PRAKASH - 2016-12-28 03:39:50 == ---Problem Description--- Ubuntu 17.04: machine crashes with Oops while running stress-ng. ---Steps followed- 1. Install 17.04 on NV machine. 2. apt-get install stress-ng 3. stress-ng -a 0 Logs dccp af_alg joydev input_leds mac_hid at24 nvmem_core ofpart cmdlinepart powernv_flash mtd opal_prd powernv_rng ipmi_powernv ipmi_msghandler ibmpowernv uio_pdrv_genirq uio vmx_crypto ib_iser rdma_cm iw_cm ib_cm ib_core configfs iscsi_tcp libiscsi_tcp libiscsi scsi_tran[165938083361,3] OPAL: Trying a CPU re-init with flags: 0x1 [166456504189,3] OPAL: CPU 0x29 not in OPAL ! [167510150475,3] OPAL: Trying a CPU re-init with flags: 0x2 [168022446397,3] OPAL: CPU 0x29 not in OPAL ! sport_iscsi ip_tables x_tables autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear ses enclosure scsi_transport_sas hid_generic ast i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt bnx2x fb_sys_fops drm aacraid tg3 usbhid uas hid usb_storage mdio ahci libcrc32c libahci crc32c_vpmsum [ 237.047216] CPU: 33 PID: 34694 Comm: stress-ng-dccp Not tainted 4.9.0-11-generic #12-Ubuntu [ 237.047315] task: c03312a69400 task.stack: c03779698000 [ 237.047402] NIP: d0002e7b0a7c LR: d0002e7b21cc CTR: c0a0dd00 [ 237.047509] REGS: c03fff68f670 TRAP: 0300 Not tainted (4.9.0-11-generic) [ 237.047613] MSR: 90010280b033 [ 237.049028] CR: 24002282 XER: 2000 [ 237.049103] CFAR: c0008a60 DAR: 02f4 DSISR: 4000 SOFTE: 1 GPR00: d0002e7b21cc c03fff68f8f0 d0002e7bb670 0001 GPR04: c02b5dbdc400 c03c74c0a460 0474 c03c74c0a474 GPR08: c03c74c0a000 c0348cd25200 GPR12: 2200 c7b72900 c03fff68c000 GPR16: 0040 0001 2713 GPR20: cc84 017f 017f c13b2f00 GPR24: 0001 0001 0004 GPR28: c13b2f00 c03c74c0a474 c02b5dbdc400 NIP [d0002e7b0a7c] dccp_v4_ctl_send_reset+0xa4/0x2f0 [dccp_ipv4] [ 237.051403] LR [d0002e7b21cc] dccp_v4_rcv+0x5d4/0x850 [dccp_ipv4] [ 237.051486] Call Trace: [ 237.051529] [c03fff68f8f0] [2713cc84] 0x2713cc84 (unreliable) [ 237.051649] [c03fff68f970] [d0002e7b21cc] dccp_v4_rcv+0x5d4/0x850 [dccp_ipv4] [ 237.051779] [c03fff68fa50] [c0a01e40] ip_local_deliver_finish+0x170/0x350 [ 237.051932] [c03fff68faa0] [c0a0276c] ip_local_deliver+0x5c/0x130 [ 237.052038] [c03fff68fb10] [c0a02278] ip_rcv_finish+0x258/0x510 [ 237.052151] [c03fff68fba0] [c0a02b44] ip_rcv+0x304/0x420 [ 237.052263] [c03fff68fc30] [c09a28bc] __netif_receive_skb_core+0x97c/0xda0 [ 237.052388] [c03fff68fd10] [c09a7ab4] process_backlog+0xd4/0x1e0 [ 237.052489] [c03fff68fd80] [c09a6f0c] net_rx_action+0x35c/0x480 [ 237.052603] [c03fff68fe90] [c0b22a6c] __do_softirq+0x18c/0x3fc [ 237.052726] [c03fff68ff90] [c0029fb0] call_do_softirq+0x14/0x24 [ 237.052848] [c0377969b920] [c001765c] do_softirq_own_stack+0x5c/0xa0 [ 237.052992] [c0377969b960] [c00cfd48] do_softirq.part.3+0x68/0x90 [ 237.053112] [c0377969b990] [c00cfe44] __local_bh_enable_ip+0xd4/0x100 [ 237.053240] [c0377969b9b0] [c0a06724] ip_finish_output2+0x244/0x460 [ 237.053372] [c0377969ba50] [c0a0977c] ip_output+0xcc/0x180 [ 237.053485] [c0377969bae0] [c0a08c78] ip_local_out+0x68/0x90 [ 237.053607] [c0377969bb20] [d00021966978] dccp_transmit_skb+0x320/0x550 [dccp] [ 237.053739] [c0377969bb90] [d0002196732c] dccp_connect+0xf4/0x1f0 [dccp] [ 237.053890] [c0377969bc10] [d0002e7b0320]
[Kernel-packages] [Bug 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129
Hi, I don't remember encountering this bug with Linux 4.8, happens about every 1-3 hours with Linux 4.10 (although I couldn't figure out a way to reproduce it). I'll try with Linux 4.11 RC3 and tell you how it goes. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1674838 Title: kernel BUG at /build/linux- 7LGLH_/linux-4.10.0/include/linux/swapops.h:129 Status in linux package in Ubuntu: Incomplete Bug description: Randomly, khugepaged process will take 100% CPU, and I can only restart the computer to recover it. Relevant dmesg attached (dmesg_crash.txt). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-14-generic 4.10.0-14.16 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mathieu2221 F pulseaudio /dev/snd/pcmC1D0p: mathieu2221 F...m pulseaudio /dev/snd/controlC1: mathieu2221 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Tue Mar 21 23:03:23 2017 HibernationDevice: RESUME=UUID=67e78e4c-94ee-447c-ae60-4387dae296dd InstallationDate: Installed on 2016-01-31 (415 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131) MachineType: LENOVO 20344 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic root=UUID=b982929e-11d0-4984-885c-6c9daba24836 ro noprompt quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-14-generic N/A linux-backports-modules-4.10.0-14-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-03-02 (19 days ago) dmi.bios.date: 10/16/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 96CN29WW(V1.15) dmi.board.asset.tag: 31900058WIN dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 13 dmi.modalias: dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213: dmi.product.name: 20344 dmi.product.version: Lenovo Yoga 2 13 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp