[Kernel-packages] [Bug 1792813] Re: iio-sensor-proxy says: "Could not find any supported sensors" on Dell XPS 15 9575 2-in-1 on Cosmic 18.10
fwiw, bug 1797174 captures the behavior from @mario-vukelic's comment -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792813 Title: iio-sensor-proxy says: "Could not find any supported sensors" on Dell XPS 15 9575 2-in-1 on Cosmic 18.10 Status in linux package in Ubuntu: Triaged Status in linux source package in Cosmic: Triaged Bug description: On Cosmic, iio-sensor-proxy 2.4, with default 4.18 kernel as well as latest mainline 4.19.0-041900rc3-generic. There is no rotation lock button in the gnome-shell panel menu. Gnome Settings > Device Display shows rotation buttons There is no directory /sys/bus/iio Reproduction: 1. Rotate device, fold display back to tent and tablet modes: -> Rotation is not detected. When folding to tablet mode, device goes to suspend as if display had been closed normally. iio-sensor-proxy finds no sensors: ~$ systemctl status iio-sensor-proxy.service ● iio-sensor-proxy.service - IIO Sensor Proxy service Loaded: loaded (/lib/systemd/system/iio-sensor-proxy.service; static; vendor preset: enabled) Active: inactive (dead) I reported issue as https://github.com/hadess/iio-sensor- proxy/issues/236 and was advised: "Looks like there's no supported sensors, or just no sensors inside this machine. Nothing that we can do about it, except asking your vendor for support (eg. is there one or multiple sensors, and if so, why aren't they supported in the kernel)" I posted the issue in Dell's Project Sputnik's Google+ community ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-7-generic 4.18.0-7.8 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mario 2139 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Sep 16 20:20:48 2018 InstallationDate: Installed on 2018-09-13 (2 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 004: ID 27c6:5395 Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic root=UUID=26ff4c95-5f68-4121-b7d0-989fa705fcc8 ro quiet splash pcie_aspm=force drm.vblankoffdelay=1 i915.fastboot=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-7-generic N/A linux-backports-modules-4.18.0-7-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.9 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.9:bd08/08/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792813/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead
linux-modules-extra package looks corrupt: (Reading database ... 367458 files and directories currently installed.) Preparing to unpack linux-modules-extra-5.0.0-11-generic_5.0.0-11.12~lp1823029_amd64.deb ... Unpacking linux-modules-extra-5.0.0-11-generic (5.0.0-11.12~lp1823029) ... dpkg-deb (subprocess): cannot copy archive member from 'linux-modules-extra-5.0.0-11-generic_5.0.0-11.12~lp1823029_amd64.deb' to decompressor pipe: unexpected end of file or stream dpkg-deb (subprocess): decompressing archive member: lzma error: unexpected end of input dpkg-deb: error: subprocess returned error exit status 2 dpkg: error processing archive linux-modules-extra-5.0.0-11-generic_5.0.0-11.12~lp1823029_amd64.deb (--install): cannot copy extracted data for './lib/modules/5.0.0-11-generic/kernel/drivers/net/wireless/marvell/mwifiex/mwifiex.ko' to '/lib/modules/5.0.0-11-generic/kernel/drivers/net/wireless/marvell/mwifiex/mwifiex.ko.dpkg-new': unexpected end of file or stream Errors were encountered while processing: linux-modules-extra-5.0.0-11-generic_5.0.0-11.12~lp1823029_amd64.deb -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823029 Title: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead Status in linux package in Ubuntu: Confirmed Bug description: Sometimes when suspending, the suspend process fails, and the machine becomes unresponsive to any input, has nothing but a black/off display, and fans kick in and run high (which is actually 'good' for detecting the issue has happened). journalctl output from an unsuccessful suspend: Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending... Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5332] manager: sleep: sleep requested (sleeping: no en Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5333] device (40:4E:36:47:ED:D1): state change: disconn Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5358] manager: NetworkManager state is now ASLEEP Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully. Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume... Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume. Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep. Apr 02 13:39:57 taplop systemd[1]: Starting Suspend... Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9078] caught SIGTERM, shutting down normally. Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager... Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was not added Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9485] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP c Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] dhcp4 (wlp2s0): state changed bound -> done Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] device (wlp2s0): DHCPv4: 480 seconds grace period Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9570] exiting (success) Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: [resource:///org/gnome/shell/ui/status/network.js 1187]: reference Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded. Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager. Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection (0x55d340e8f5a0), has been already deallocated — im Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for context 0x55d34160e1e0 == Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0 55d345364700 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1 55d345364680 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2 7ffe97451d00 b self-hosted:979 (7fc3d4350a60 @ 440) Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::1c45 Apr 02 13:39:58
[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead
initial tests are looking good (4 successful suspends & resumes during this boot so far). Will keep testing and report back. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823029 Title: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead Status in linux package in Ubuntu: Confirmed Bug description: Sometimes when suspending, the suspend process fails, and the machine becomes unresponsive to any input, has nothing but a black/off display, and fans kick in and run high (which is actually 'good' for detecting the issue has happened). journalctl output from an unsuccessful suspend: Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending... Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5332] manager: sleep: sleep requested (sleeping: no en Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5333] device (40:4E:36:47:ED:D1): state change: disconn Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5358] manager: NetworkManager state is now ASLEEP Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully. Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume... Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume. Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep. Apr 02 13:39:57 taplop systemd[1]: Starting Suspend... Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9078] caught SIGTERM, shutting down normally. Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager... Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was not added Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9485] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP c Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] dhcp4 (wlp2s0): state changed bound -> done Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] device (wlp2s0): DHCPv4: 480 seconds grace period Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9570] exiting (success) Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: [resource:///org/gnome/shell/ui/status/network.js 1187]: reference Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded. Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager. Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection (0x55d340e8f5a0), has been already deallocated — im Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for context 0x55d34160e1e0 == Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0 55d345364700 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1 55d345364680 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2 7ffe97451d00 b self-hosted:979 (7fc3d4350a60 @ 440) Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::1c45 Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 10.30.2.26 Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for fe80::1c45:b634:dc94:8f5f on wlp2s0. Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 10.30.2.26 on wlp2s0. Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0 Apr 02 13:39:58 taplop wpa_supplicant[1069]: Could not read interface p2p-dev-wlp2s0 flags: No such device Apr 02 13:39:58 taplop systemd-sleep[9790]: Suspending system... Apr 02 13:39:58 taplop kernel: PM: suspend entry (deep) Apr 02 13:39:59 taplop kernel:
[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead
still looking good after several more sleep cycles today -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823029 Title: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead Status in linux package in Ubuntu: Confirmed Bug description: Sometimes when suspending, the suspend process fails, and the machine becomes unresponsive to any input, has nothing but a black/off display, and fans kick in and run high (which is actually 'good' for detecting the issue has happened). journalctl output from an unsuccessful suspend: Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending... Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5332] manager: sleep: sleep requested (sleeping: no en Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5333] device (40:4E:36:47:ED:D1): state change: disconn Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5358] manager: NetworkManager state is now ASLEEP Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully. Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume... Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume. Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep. Apr 02 13:39:57 taplop systemd[1]: Starting Suspend... Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9078] caught SIGTERM, shutting down normally. Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager... Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was not added Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9485] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP c Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] dhcp4 (wlp2s0): state changed bound -> done Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] device (wlp2s0): DHCPv4: 480 seconds grace period Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9570] exiting (success) Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: [resource:///org/gnome/shell/ui/status/network.js 1187]: reference Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded. Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager. Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection (0x55d340e8f5a0), has been already deallocated — im Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for context 0x55d34160e1e0 == Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0 55d345364700 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1 55d345364680 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2 7ffe97451d00 b self-hosted:979 (7fc3d4350a60 @ 440) Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::1c45 Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 10.30.2.26 Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for fe80::1c45:b634:dc94:8f5f on wlp2s0. Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 10.30.2.26 on wlp2s0. Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0 Apr 02 13:39:58 taplop wpa_supplicant[1069]: Could not read interface p2p-dev-wlp2s0 flags: No such device Apr 02 13:39:58 taplop systemd-sleep[9790]: Suspending system... Apr 02 13:39:58 taplop kernel: PM: suspend entry (deep) Apr 02 13:39:59 taplop kernel: PM: Syncing filesystems ... done. Apr 02 13:39:59 taplop kernel: F
[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead
Had another failure with similar symptoms (fan on, screen black once laptop lid opened), but logs look different this time. ** Attachment added: "differentfailure.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823029/+attachment/5256275/+files/differentfailure.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/1823029 Title: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead Status in linux package in Ubuntu: Confirmed Bug description: Sometimes when suspending, the suspend process fails, and the machine becomes unresponsive to any input, has nothing but a black/off display, and fans kick in and run high (which is actually 'good' for detecting the issue has happened). journalctl output from an unsuccessful suspend: Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending... Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5332] manager: sleep: sleep requested (sleeping: no en Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5333] device (40:4E:36:47:ED:D1): state change: disconn Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5358] manager: NetworkManager state is now ASLEEP Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully. Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume... Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume. Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep. Apr 02 13:39:57 taplop systemd[1]: Starting Suspend... Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9078] caught SIGTERM, shutting down normally. Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager... Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was not added Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9485] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP c Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] dhcp4 (wlp2s0): state changed bound -> done Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] device (wlp2s0): DHCPv4: 480 seconds grace period Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9570] exiting (success) Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: [resource:///org/gnome/shell/ui/status/network.js 1187]: reference Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded. Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager. Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection (0x55d340e8f5a0), has been already deallocated — im Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for context 0x55d34160e1e0 == Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0 55d345364700 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1 55d345364680 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2 7ffe97451d00 b self-hosted:979 (7fc3d4350a60 @ 440) Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::1c45 Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 10.30.2.26 Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for fe80::1c45:b634:dc94:8f5f on wlp2s0. Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 10.30.2.26 on wlp2s0. Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0 Apr 02 13:39:58 taplop wpa_supplicant[1069]: Could not read interface p2p-dev-wlp2s0 flags: No such device
[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead
(but unlike the on-suspend lockup, the journal continues to accumulate some entries -- possible the system wasn't fully locked up but the display was?) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823029 Title: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead Status in linux package in Ubuntu: Confirmed Bug description: Sometimes when suspending, the suspend process fails, and the machine becomes unresponsive to any input, has nothing but a black/off display, and fans kick in and run high (which is actually 'good' for detecting the issue has happened). journalctl output from an unsuccessful suspend: Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending... Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5332] manager: sleep: sleep requested (sleeping: no en Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5333] device (40:4E:36:47:ED:D1): state change: disconn Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5358] manager: NetworkManager state is now ASLEEP Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully. Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume... Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume. Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep. Apr 02 13:39:57 taplop systemd[1]: Starting Suspend... Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9078] caught SIGTERM, shutting down normally. Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager... Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was not added Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9485] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP c Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] dhcp4 (wlp2s0): state changed bound -> done Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] device (wlp2s0): DHCPv4: 480 seconds grace period Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9570] exiting (success) Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: [resource:///org/gnome/shell/ui/status/network.js 1187]: reference Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded. Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager. Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection (0x55d340e8f5a0), has been already deallocated — im Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for context 0x55d34160e1e0 == Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0 55d345364700 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1 55d345364680 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2 7ffe97451d00 b self-hosted:979 (7fc3d4350a60 @ 440) Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::1c45 Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 10.30.2.26 Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for fe80::1c45:b634:dc94:8f5f on wlp2s0. Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 10.30.2.26 on wlp2s0. Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0 Apr 02 13:39:58 taplop wpa_supplicant[1069]: Could not read interface p2p-dev-wlp2s0 flags: No such device Apr 02 13:39:58 taplop systemd-sleep[9790]: Suspending system... Apr 02 13:39:58 taplop kernel: PM: suspend entry (deep) Apr
[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead
>From reading the logs that's what it looks like -- it appears the lid was closed at 21:48:40 and then suspend was successful at 21:49:10 or 21:49:25, but then the system immediately resumes at 21:49:25, and doesn't fully recover -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823029 Title: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead Status in linux package in Ubuntu: Confirmed Bug description: Sometimes when suspending, the suspend process fails, and the machine becomes unresponsive to any input, has nothing but a black/off display, and fans kick in and run high (which is actually 'good' for detecting the issue has happened). journalctl output from an unsuccessful suspend: Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending... Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5332] manager: sleep: sleep requested (sleeping: no en Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5333] device (40:4E:36:47:ED:D1): state change: disconn Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5358] manager: NetworkManager state is now ASLEEP Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully. Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume... Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume. Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep. Apr 02 13:39:57 taplop systemd[1]: Starting Suspend... Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9078] caught SIGTERM, shutting down normally. Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager... Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was not added Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9485] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP c Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] dhcp4 (wlp2s0): state changed bound -> done Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] device (wlp2s0): DHCPv4: 480 seconds grace period Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9570] exiting (success) Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: [resource:///org/gnome/shell/ui/status/network.js 1187]: reference Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded. Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager. Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection (0x55d340e8f5a0), has been already deallocated — im Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for context 0x55d34160e1e0 == Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0 55d345364700 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1 55d345364680 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2 7ffe97451d00 b self-hosted:979 (7fc3d4350a60 @ 440) Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::1c45 Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 10.30.2.26 Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for fe80::1c45:b634:dc94:8f5f on wlp2s0. Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 10.30.2.26 on wlp2s0. Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0 Apr 02 13:39:58 taplop wpa_supplicant[1069]: Could not read interface p2p-dev-wlp2s0 flags: No such device Apr 02 13:39:58 taplop systemd-sleep[9790]: Suspen
[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead
Either way, whatever fix is in the https://people.canonical.com/~khfeng/lp1823029/ kernel is very effective if not perfect -- can it be put into the main repo kernels or will I need to keep kernel packages held for a while? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823029 Title: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead Status in linux package in Ubuntu: Confirmed Bug description: Sometimes when suspending, the suspend process fails, and the machine becomes unresponsive to any input, has nothing but a black/off display, and fans kick in and run high (which is actually 'good' for detecting the issue has happened). journalctl output from an unsuccessful suspend: Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending... Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5332] manager: sleep: sleep requested (sleeping: no en Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5333] device (40:4E:36:47:ED:D1): state change: disconn Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5358] manager: NetworkManager state is now ASLEEP Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully. Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume... Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume. Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep. Apr 02 13:39:57 taplop systemd[1]: Starting Suspend... Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9078] caught SIGTERM, shutting down normally. Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager... Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was not added Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9485] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP c Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] dhcp4 (wlp2s0): state changed bound -> done Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] device (wlp2s0): DHCPv4: 480 seconds grace period Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9570] exiting (success) Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: [resource:///org/gnome/shell/ui/status/network.js 1187]: reference Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded. Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager. Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection (0x55d340e8f5a0), has been already deallocated — im Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for context 0x55d34160e1e0 == Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0 55d345364700 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1 55d345364680 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2 7ffe97451d00 b self-hosted:979 (7fc3d4350a60 @ 440) Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::1c45 Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 10.30.2.26 Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for fe80::1c45:b634:dc94:8f5f on wlp2s0. Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 10.30.2.26 on wlp2s0. Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0 Apr 02 13:39:58 taplop wpa_supplicant[1069]: Could not read interface p2p-dev-wlp2s0 flags: No such device Apr 02 13:39:58 taplop systemd-sleep[9790]: Suspending sy
[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead
looks like no responses to v2, anything I can do to help move this along? could it at least make it into an updated kernel build with security patches, if not the ubuntu patch set? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823029 Title: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead Status in linux package in Ubuntu: Confirmed Bug description: Sometimes when suspending, the suspend process fails, and the machine becomes unresponsive to any input, has nothing but a black/off display, and fans kick in and run high (which is actually 'good' for detecting the issue has happened). journalctl output from an unsuccessful suspend: Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending... Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5332] manager: sleep: sleep requested (sleeping: no en Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5333] device (40:4E:36:47:ED:D1): state change: disconn Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5358] manager: NetworkManager state is now ASLEEP Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully. Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume... Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume. Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep. Apr 02 13:39:57 taplop systemd[1]: Starting Suspend... Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9078] caught SIGTERM, shutting down normally. Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager... Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was not added Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9485] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP c Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] dhcp4 (wlp2s0): state changed bound -> done Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] device (wlp2s0): DHCPv4: 480 seconds grace period Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9570] exiting (success) Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: [resource:///org/gnome/shell/ui/status/network.js 1187]: reference Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded. Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager. Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection (0x55d340e8f5a0), has been already deallocated — im Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for context 0x55d34160e1e0 == Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0 55d345364700 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1 55d345364680 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2 7ffe97451d00 b self-hosted:979 (7fc3d4350a60 @ 440) Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::1c45 Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 10.30.2.26 Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for fe80::1c45:b634:dc94:8f5f on wlp2s0. Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 10.30.2.26 on wlp2s0. Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0 Apr 02 13:39:58 taplop wpa_supplicant[1069]: Could not read interface p2p-dev-wlp2s0 flags: No such device Apr 02 13:39:58 taplop systemd-sleep[9790]: Suspending system... Apr 02 13:39:58 taplop kernel: P
[Kernel-packages] [Bug 1729010] Re: USB hub stops working after suspend(s?)
Reproduced on mainline as well. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729010 Title: USB hub stops working after suspend(s?) Status in linux package in Ubuntu: Confirmed Bug description: On initial boot, my usb hub works fine, but after a (series of?) suspends, I stop being able to see devices that are plugged into it. journalctl output on plugging it in: Oct 31 07:08:36 spiny kernel: usb 1-1: new high-speed USB device number 21 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device found, idVendor=0409, idProduct=005a Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: USB hub found Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: 4 ports detected Oct 31 07:08:36 spiny kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC=fe80::::a299:9bff:fe17:9047 DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=32325 PROTO=UDP SPT=8612 DPT=8612 LEN=24 Oct 31 07:08:36 spiny kernel: usb 1-1.1: new high-speed USB device number 22 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device found, idVendor=0b95, idProduct=772a Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 31 07:08:36 spiny kernel: usb 1-1.1: Product: AX88x72A Oct 31 07:08:36 spiny kernel: usb 1-1.1: Manufacturer: ASIX Elec. Corp. Oct 31 07:08:36 spiny kernel: usb 1-1.1: SerialNumber: 47EDE2 Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 eth0: register 'asix' at usb-:00:14.0-1.1, ASIX AX88772 USB 2.0 Ethernet, 00:50:b6:47:ed:e2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.0438] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/7) Oct 31 07:08:37 spiny mtp-probe[13207]: checking bus 1, device 22: "/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1" Oct 31 07:08:37 spiny mtp-probe[13207]: bus: 1, device: 22 was not an MTP device Oct 31 07:08:37 spiny systemd-udevd[13206]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 enx0050b647ede2: renamed from eth0 Oct 31 07:08:37 spiny pkexec[13215]: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Oct 31 07:08:37 spiny pkexec[13215]: jbarnett: Executing command [USER=root] [TTY=unknown] [CWD=/home/jbarnett] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 31] Oct 31 07:08:37 spiny pkexec[13214]: gdm: Error executing command as another user: Not authorized [USER=root] [TTY=unknown] [CWD=/var/lib/gdm3] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 48] Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: Error executing command as another user: Not authorized Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: This incident has been reported. Oct 31 07:08:37 spiny systemd-networkd[1119]: eth0: Renamed to enx0050b647ede2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1066] device (eth0): interface index 10 renamed iface from 'eth0' to 'enx0050b647ede2' Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] devices added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2) Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] device added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2): no ifupdown configuration found. Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1217] device (enx0050b647ede2): state change: unmanaged -> unavailable (reason 'managed', internal state 'external') Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1274] keyfile: add connection in-memory (9365f42f-9dd9-3bdc-bbad-e7062efcaf7c,"Wired connection 4") Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1284] settings: (enx0050b647ede2): created default wired connection 'Wired connection 4' Oct 31 07:08:37 spiny systemd[1]: Starting systemd-resolved-update-resolvconf.service... Oct 31 07:08:37 spiny systemd[1]: Started systemd-resolved-update-resolvconf.service. Oct 31 07:08:37 spiny kernel: usb 1-1.2: new full-speed USB device number 23 using xhci_hcd Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device found, idVendor=0d8c, idProduct=0105 Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device str
[Kernel-packages] [Bug 1729010] Re: USB hub stops working after suspend(s?)
It did not occur on previous ubuntu releases, and didn't occur during the artful dev cycle either. It seems to be on a suspend-by-suspend basis: after reproducing, another suspend cycle seems to "fix" it at least some of the time. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729010 Title: USB hub stops working after suspend(s?) Status in linux package in Ubuntu: Confirmed Bug description: On initial boot, my usb hub works fine, but after a (series of?) suspends, I stop being able to see devices that are plugged into it. journalctl output on plugging it in: Oct 31 07:08:36 spiny kernel: usb 1-1: new high-speed USB device number 21 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device found, idVendor=0409, idProduct=005a Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: USB hub found Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: 4 ports detected Oct 31 07:08:36 spiny kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC=fe80::::a299:9bff:fe17:9047 DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=32325 PROTO=UDP SPT=8612 DPT=8612 LEN=24 Oct 31 07:08:36 spiny kernel: usb 1-1.1: new high-speed USB device number 22 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device found, idVendor=0b95, idProduct=772a Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 31 07:08:36 spiny kernel: usb 1-1.1: Product: AX88x72A Oct 31 07:08:36 spiny kernel: usb 1-1.1: Manufacturer: ASIX Elec. Corp. Oct 31 07:08:36 spiny kernel: usb 1-1.1: SerialNumber: 47EDE2 Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 eth0: register 'asix' at usb-:00:14.0-1.1, ASIX AX88772 USB 2.0 Ethernet, 00:50:b6:47:ed:e2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.0438] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/7) Oct 31 07:08:37 spiny mtp-probe[13207]: checking bus 1, device 22: "/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1" Oct 31 07:08:37 spiny mtp-probe[13207]: bus: 1, device: 22 was not an MTP device Oct 31 07:08:37 spiny systemd-udevd[13206]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 enx0050b647ede2: renamed from eth0 Oct 31 07:08:37 spiny pkexec[13215]: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Oct 31 07:08:37 spiny pkexec[13215]: jbarnett: Executing command [USER=root] [TTY=unknown] [CWD=/home/jbarnett] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 31] Oct 31 07:08:37 spiny pkexec[13214]: gdm: Error executing command as another user: Not authorized [USER=root] [TTY=unknown] [CWD=/var/lib/gdm3] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 48] Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: Error executing command as another user: Not authorized Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: This incident has been reported. Oct 31 07:08:37 spiny systemd-networkd[1119]: eth0: Renamed to enx0050b647ede2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1066] device (eth0): interface index 10 renamed iface from 'eth0' to 'enx0050b647ede2' Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] devices added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2) Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] device added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2): no ifupdown configuration found. Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1217] device (enx0050b647ede2): state change: unmanaged -> unavailable (reason 'managed', internal state 'external') Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1274] keyfile: add connection in-memory (9365f42f-9dd9-3bdc-bbad-e7062efcaf7c,"Wired connection 4") Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1284] settings: (enx0050b647ede2): created default wired connection 'Wired connection 4' Oct 31 07:08:37 spiny systemd[1]: Starting systemd-resolved-update-resolvconf.service... Oct 31 07:08:37 spiny systemd[1]: Started systemd-resolved-update-resolvconf.service. Oct 31 07:08:37 spiny kernel: usb 1-1.2: new full-speed USB device number 23 using xhci_hcd Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device found, idVen
[Kernel-packages] [Bug 1729010] Re: USB hub stops working after suspend(s?)
I should probably test a few more suspend cycles, but so far on 4.12.0-11-generic I'm not seeing the issue -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729010 Title: USB hub stops working after suspend(s?) Status in linux package in Ubuntu: Confirmed Bug description: On initial boot, my usb hub works fine, but after a (series of?) suspends, I stop being able to see devices that are plugged into it. journalctl output on plugging it in: Oct 31 07:08:36 spiny kernel: usb 1-1: new high-speed USB device number 21 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device found, idVendor=0409, idProduct=005a Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: USB hub found Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: 4 ports detected Oct 31 07:08:36 spiny kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC=fe80::::a299:9bff:fe17:9047 DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=32325 PROTO=UDP SPT=8612 DPT=8612 LEN=24 Oct 31 07:08:36 spiny kernel: usb 1-1.1: new high-speed USB device number 22 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device found, idVendor=0b95, idProduct=772a Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 31 07:08:36 spiny kernel: usb 1-1.1: Product: AX88x72A Oct 31 07:08:36 spiny kernel: usb 1-1.1: Manufacturer: ASIX Elec. Corp. Oct 31 07:08:36 spiny kernel: usb 1-1.1: SerialNumber: 47EDE2 Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 eth0: register 'asix' at usb-:00:14.0-1.1, ASIX AX88772 USB 2.0 Ethernet, 00:50:b6:47:ed:e2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.0438] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/7) Oct 31 07:08:37 spiny mtp-probe[13207]: checking bus 1, device 22: "/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1" Oct 31 07:08:37 spiny mtp-probe[13207]: bus: 1, device: 22 was not an MTP device Oct 31 07:08:37 spiny systemd-udevd[13206]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 enx0050b647ede2: renamed from eth0 Oct 31 07:08:37 spiny pkexec[13215]: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Oct 31 07:08:37 spiny pkexec[13215]: jbarnett: Executing command [USER=root] [TTY=unknown] [CWD=/home/jbarnett] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 31] Oct 31 07:08:37 spiny pkexec[13214]: gdm: Error executing command as another user: Not authorized [USER=root] [TTY=unknown] [CWD=/var/lib/gdm3] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 48] Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: Error executing command as another user: Not authorized Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: This incident has been reported. Oct 31 07:08:37 spiny systemd-networkd[1119]: eth0: Renamed to enx0050b647ede2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1066] device (eth0): interface index 10 renamed iface from 'eth0' to 'enx0050b647ede2' Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] devices added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2) Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] device added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2): no ifupdown configuration found. Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1217] device (enx0050b647ede2): state change: unmanaged -> unavailable (reason 'managed', internal state 'external') Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1274] keyfile: add connection in-memory (9365f42f-9dd9-3bdc-bbad-e7062efcaf7c,"Wired connection 4") Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1284] settings: (enx0050b647ede2): created default wired connection 'Wired connection 4' Oct 31 07:08:37 spiny systemd[1]: Starting systemd-resolved-update-resolvconf.service... Oct 31 07:08:37 spiny systemd[1]: Started systemd-resolved-update-resolvconf.service. Oct 31 07:08:37 spiny kernel: usb 1-1.2: new full-speed USB device number 23 using xhci_hcd Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device found, idVendor=0d8c, idProduct=0105 Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device strings: Mfr=3, Product=1, SerialNumber=
[Kernel-packages] [Bug 1729010] Re: USB hub stops working after suspend(s?)
ok, i'm going to go with bionic's kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729010 Title: USB hub stops working after suspend(s?) Status in linux package in Ubuntu: Confirmed Bug description: On initial boot, my usb hub works fine, but after a (series of?) suspends, I stop being able to see devices that are plugged into it. journalctl output on plugging it in: Oct 31 07:08:36 spiny kernel: usb 1-1: new high-speed USB device number 21 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device found, idVendor=0409, idProduct=005a Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: USB hub found Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: 4 ports detected Oct 31 07:08:36 spiny kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC=fe80::::a299:9bff:fe17:9047 DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=32325 PROTO=UDP SPT=8612 DPT=8612 LEN=24 Oct 31 07:08:36 spiny kernel: usb 1-1.1: new high-speed USB device number 22 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device found, idVendor=0b95, idProduct=772a Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 31 07:08:36 spiny kernel: usb 1-1.1: Product: AX88x72A Oct 31 07:08:36 spiny kernel: usb 1-1.1: Manufacturer: ASIX Elec. Corp. Oct 31 07:08:36 spiny kernel: usb 1-1.1: SerialNumber: 47EDE2 Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 eth0: register 'asix' at usb-:00:14.0-1.1, ASIX AX88772 USB 2.0 Ethernet, 00:50:b6:47:ed:e2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.0438] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/7) Oct 31 07:08:37 spiny mtp-probe[13207]: checking bus 1, device 22: "/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1" Oct 31 07:08:37 spiny mtp-probe[13207]: bus: 1, device: 22 was not an MTP device Oct 31 07:08:37 spiny systemd-udevd[13206]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 enx0050b647ede2: renamed from eth0 Oct 31 07:08:37 spiny pkexec[13215]: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Oct 31 07:08:37 spiny pkexec[13215]: jbarnett: Executing command [USER=root] [TTY=unknown] [CWD=/home/jbarnett] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 31] Oct 31 07:08:37 spiny pkexec[13214]: gdm: Error executing command as another user: Not authorized [USER=root] [TTY=unknown] [CWD=/var/lib/gdm3] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 48] Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: Error executing command as another user: Not authorized Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: This incident has been reported. Oct 31 07:08:37 spiny systemd-networkd[1119]: eth0: Renamed to enx0050b647ede2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1066] device (eth0): interface index 10 renamed iface from 'eth0' to 'enx0050b647ede2' Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] devices added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2) Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] device added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2): no ifupdown configuration found. Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1217] device (enx0050b647ede2): state change: unmanaged -> unavailable (reason 'managed', internal state 'external') Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1274] keyfile: add connection in-memory (9365f42f-9dd9-3bdc-bbad-e7062efcaf7c,"Wired connection 4") Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1284] settings: (enx0050b647ede2): created default wired connection 'Wired connection 4' Oct 31 07:08:37 spiny systemd[1]: Starting systemd-resolved-update-resolvconf.service... Oct 31 07:08:37 spiny systemd[1]: Started systemd-resolved-update-resolvconf.service. Oct 31 07:08:37 spiny kernel: usb 1-1.2: new full-speed USB device number 23 using xhci_hcd Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device found, idVendor=0d8c, idProduct=0105 Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device strings: Mfr=3, Product=1, SerialNumber=0 Oct 31 07:08:37 spiny kernel: usb 1-1.2: Product: USB Multime
[Kernel-packages] [Bug 1844962] Re: apparent memory usage regression - not getting freed?
patch update: https://lists.freedesktop.org/archives/amd- gfx/2019-October/041187.html (also see review in https://lists.freedesktop.org/archives/amd-gfx/2019-October/041194.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/1844962 Title: apparent memory usage regression - not getting freed? Status in linux package in Ubuntu: Confirmed Bug description: In eoan on a 5.3 kernel, have noticed a few incidents of the system becoming sluggish/unresponsive, which appears to be caused by low available memory. top is reporting 13 of 16G are "used", but adding up the memory reported by top sorted by memory usage appears like it should be closer to 3-4G "used". Attaching two top screenshots, one shows 3.3G used and system behaving well, the other shows 14G used and system lagging. In both cases, approximately the same programs are being run taking up approximately the same amount of resident memory, so not sure where all the memory usage is coming from. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-10-generic 5.3.0-10.11 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 5046 F pulseaudio CurrentDesktop: GNOME Date: Sun Sep 22 21:26:02 2019 InstallationDate: Installed on 2019-08-17 (37 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 004: ID 27c6:5395 HTMicroelectronics Goodix Fingerprint Device Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-10-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash usbcore.dyndbg=+p vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-10-generic N/A linux-backports-modules-5.3.0-10-generic N/A linux-firmware1.182 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-18 (4 days ago) dmi.bios.date: 10/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd10/10/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844962/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844962] Re: apparent memory usage regression - not getting freed?
in drm-next: https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm- next&id=06f7f57e87d09900a7c3109a357b73521ab40771 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844962 Title: apparent memory usage regression - not getting freed? Status in linux package in Ubuntu: Confirmed Bug description: In eoan on a 5.3 kernel, have noticed a few incidents of the system becoming sluggish/unresponsive, which appears to be caused by low available memory. top is reporting 13 of 16G are "used", but adding up the memory reported by top sorted by memory usage appears like it should be closer to 3-4G "used". Attaching two top screenshots, one shows 3.3G used and system behaving well, the other shows 14G used and system lagging. In both cases, approximately the same programs are being run taking up approximately the same amount of resident memory, so not sure where all the memory usage is coming from. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-10-generic 5.3.0-10.11 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 5046 F pulseaudio CurrentDesktop: GNOME Date: Sun Sep 22 21:26:02 2019 InstallationDate: Installed on 2019-08-17 (37 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 004: ID 27c6:5395 HTMicroelectronics Goodix Fingerprint Device Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-10-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash usbcore.dyndbg=+p vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-10-generic N/A linux-backports-modules-5.3.0-10-generic N/A linux-firmware1.182 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-18 (4 days ago) dmi.bios.date: 10/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd10/10/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844962/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844962] Re: apparent memory usage regression - not getting freed?
** Tags added: patch-accepted-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844962 Title: apparent memory usage regression - not getting freed? Status in linux package in Ubuntu: Confirmed Bug description: In eoan on a 5.3 kernel, have noticed a few incidents of the system becoming sluggish/unresponsive, which appears to be caused by low available memory. top is reporting 13 of 16G are "used", but adding up the memory reported by top sorted by memory usage appears like it should be closer to 3-4G "used". Attaching two top screenshots, one shows 3.3G used and system behaving well, the other shows 14G used and system lagging. In both cases, approximately the same programs are being run taking up approximately the same amount of resident memory, so not sure where all the memory usage is coming from. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-10-generic 5.3.0-10.11 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 5046 F pulseaudio CurrentDesktop: GNOME Date: Sun Sep 22 21:26:02 2019 InstallationDate: Installed on 2019-08-17 (37 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 004: ID 27c6:5395 HTMicroelectronics Goodix Fingerprint Device Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-10-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash usbcore.dyndbg=+p vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-10-generic N/A linux-backports-modules-5.3.0-10-generic N/A linux-firmware1.182 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-18 (4 days ago) dmi.bios.date: 10/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd10/10/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844962/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead
fwiw, with a 5.3 kernel on eoan and a system-sleep script that does `btmgmt power off` pre sleep, and `btmgmt power on` post sleep, I haven't been seeing the lock up issue. just an occasional instant wake from suspend with the system usable after that, and able to successfully suspend with another attempt. `PM: Some devices failed to suspend, or early wake event detected` in the logs when the instant wake happens. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823029 Title: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead Status in linux package in Ubuntu: Confirmed Bug description: Sometimes when suspending, the suspend process fails, and the machine becomes unresponsive to any input, has nothing but a black/off display, and fans kick in and run high (which is actually 'good' for detecting the issue has happened). journalctl output from an unsuccessful suspend: Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending... Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5332] manager: sleep: sleep requested (sleeping: no en Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5333] device (40:4E:36:47:ED:D1): state change: disconn Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5358] manager: NetworkManager state is now ASLEEP Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully. Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume... Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume. Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep. Apr 02 13:39:57 taplop systemd[1]: Starting Suspend... Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9078] caught SIGTERM, shutting down normally. Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager... Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was not added Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9485] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP c Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] dhcp4 (wlp2s0): state changed bound -> done Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] device (wlp2s0): DHCPv4: 480 seconds grace period Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9570] exiting (success) Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: [resource:///org/gnome/shell/ui/status/network.js 1187]: reference Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded. Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager. Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection (0x55d340e8f5a0), has been already deallocated — im Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for context 0x55d34160e1e0 == Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0 55d345364700 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1 55d345364680 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2 7ffe97451d00 b self-hosted:979 (7fc3d4350a60 @ 440) Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::1c45 Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 10.30.2.26 Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for fe80::1c45:b634:dc94:8f5f on wlp2s0. Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 10.30.2.26 on wlp2s0. Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit ifname=p2p-dev-w
[Kernel-packages] [Bug 1844962] Re: apparent memory usage regression - not getting freed?
added to the 5.3-stable tree: https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable- queue.git/tree/queue-5.3/drm-amdgpu-user-pages-array-memory-leak- fix.patch can this get into the next ubuntu kernel as well? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844962 Title: apparent memory usage regression - not getting freed? Status in linux package in Ubuntu: Confirmed Bug description: In eoan on a 5.3 kernel, have noticed a few incidents of the system becoming sluggish/unresponsive, which appears to be caused by low available memory. top is reporting 13 of 16G are "used", but adding up the memory reported by top sorted by memory usage appears like it should be closer to 3-4G "used". Attaching two top screenshots, one shows 3.3G used and system behaving well, the other shows 14G used and system lagging. In both cases, approximately the same programs are being run taking up approximately the same amount of resident memory, so not sure where all the memory usage is coming from. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-10-generic 5.3.0-10.11 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 5046 F pulseaudio CurrentDesktop: GNOME Date: Sun Sep 22 21:26:02 2019 InstallationDate: Installed on 2019-08-17 (37 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 004: ID 27c6:5395 HTMicroelectronics Goodix Fingerprint Device Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-10-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash usbcore.dyndbg=+p vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-10-generic N/A linux-backports-modules-5.3.0-10-generic N/A linux-firmware1.182 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-18 (4 days ago) dmi.bios.date: 10/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd10/10/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844962/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead
any chance we can see this in an ubuntu kernel despite the lack of response on lkml? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823029 Title: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead Status in linux package in Ubuntu: Confirmed Bug description: Sometimes when suspending, the suspend process fails, and the machine becomes unresponsive to any input, has nothing but a black/off display, and fans kick in and run high (which is actually 'good' for detecting the issue has happened). journalctl output from an unsuccessful suspend: Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending... Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5332] manager: sleep: sleep requested (sleeping: no en Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5333] device (40:4E:36:47:ED:D1): state change: disconn Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5358] manager: NetworkManager state is now ASLEEP Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully. Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume... Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume. Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep. Apr 02 13:39:57 taplop systemd[1]: Starting Suspend... Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9078] caught SIGTERM, shutting down normally. Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager... Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was not added Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9485] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP c Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] dhcp4 (wlp2s0): state changed bound -> done Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] device (wlp2s0): DHCPv4: 480 seconds grace period Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9570] exiting (success) Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: [resource:///org/gnome/shell/ui/status/network.js 1187]: reference Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded. Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager. Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection (0x55d340e8f5a0), has been already deallocated — im Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for context 0x55d34160e1e0 == Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0 55d345364700 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1 55d345364680 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2 7ffe97451d00 b self-hosted:979 (7fc3d4350a60 @ 440) Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::1c45 Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 10.30.2.26 Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for fe80::1c45:b634:dc94:8f5f on wlp2s0. Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 10.30.2.26 on wlp2s0. Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0 Apr 02 13:39:58 taplop wpa_supplicant[1069]: Could not read interface p2p-dev-wlp2s0 flags: No such device Apr 02 13:39:58 taplop systemd-sleep[9790]: Suspending system... Apr 02 13:39:58 taplop kernel: PM: suspend entry (deep) Apr 02 13:39:59 taplop kernel: PM: Syncing filesystems ... done. Apr
[Kernel-packages] [Bug 1844962] Re: apparent memory usage regression - not getting freed?
https://lists.freedesktop.org/archives/amd-gfx/2019-October/040688.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/1844962 Title: apparent memory usage regression - not getting freed? Status in linux package in Ubuntu: Confirmed Bug description: In eoan on a 5.3 kernel, have noticed a few incidents of the system becoming sluggish/unresponsive, which appears to be caused by low available memory. top is reporting 13 of 16G are "used", but adding up the memory reported by top sorted by memory usage appears like it should be closer to 3-4G "used". Attaching two top screenshots, one shows 3.3G used and system behaving well, the other shows 14G used and system lagging. In both cases, approximately the same programs are being run taking up approximately the same amount of resident memory, so not sure where all the memory usage is coming from. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-10-generic 5.3.0-10.11 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 5046 F pulseaudio CurrentDesktop: GNOME Date: Sun Sep 22 21:26:02 2019 InstallationDate: Installed on 2019-08-17 (37 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 004: ID 27c6:5395 HTMicroelectronics Goodix Fingerprint Device Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-10-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash usbcore.dyndbg=+p vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-10-generic N/A linux-backports-modules-5.3.0-10-generic N/A linux-firmware1.182 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-18 (4 days ago) dmi.bios.date: 10/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd10/10/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844962/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844962] Re: apparent memory usage regression - not getting freed?
The patch in https://lists.freedesktop.org/archives/amd- gfx/2019-October/040850.html appears to fix the issue -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844962 Title: apparent memory usage regression - not getting freed? Status in linux package in Ubuntu: Confirmed Bug description: In eoan on a 5.3 kernel, have noticed a few incidents of the system becoming sluggish/unresponsive, which appears to be caused by low available memory. top is reporting 13 of 16G are "used", but adding up the memory reported by top sorted by memory usage appears like it should be closer to 3-4G "used". Attaching two top screenshots, one shows 3.3G used and system behaving well, the other shows 14G used and system lagging. In both cases, approximately the same programs are being run taking up approximately the same amount of resident memory, so not sure where all the memory usage is coming from. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-10-generic 5.3.0-10.11 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 5046 F pulseaudio CurrentDesktop: GNOME Date: Sun Sep 22 21:26:02 2019 InstallationDate: Installed on 2019-08-17 (37 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 004: ID 27c6:5395 HTMicroelectronics Goodix Fingerprint Device Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-10-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash usbcore.dyndbg=+p vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-10-generic N/A linux-backports-modules-5.3.0-10-generic N/A linux-firmware1.182 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-18 (4 days ago) dmi.bios.date: 10/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd10/10/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844962/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844962] Re: apparent memory usage regression - not getting freed?
** Attachment added: ""bad" memory usage" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844962/+attachment/5290532/+files/Screenshot%20from%202019-09-22%2021-24-40.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844962 Title: apparent memory usage regression - not getting freed? Status in linux package in Ubuntu: New Bug description: In eoan on a 5.3 kernel, have noticed a few incidents of the system becoming sluggish/unresponsive, which appears to be caused by low available memory. top is reporting 13 of 16G are "used", but adding up the memory reported by top sorted by memory usage appears like it should be closer to 3-4G "used". Attaching two top screenshots, one shows 3.3G used and system behaving well, the other shows 14G used and system lagging. In both cases, approximately the same programs are being run taking up approximately the same amount of resident memory, so not sure where all the memory usage is coming from. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-10-generic 5.3.0-10.11 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 5046 F pulseaudio CurrentDesktop: GNOME Date: Sun Sep 22 21:26:02 2019 InstallationDate: Installed on 2019-08-17 (37 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 004: ID 27c6:5395 HTMicroelectronics Goodix Fingerprint Device Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-10-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash usbcore.dyndbg=+p vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-10-generic N/A linux-backports-modules-5.3.0-10-generic N/A linux-firmware1.182 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-18 (4 days ago) dmi.bios.date: 10/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd10/10/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844962/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844962] [NEW] apparent memory usage regression - not getting freed?
Public bug reported: In eoan on a 5.3 kernel, have noticed a few incidents of the system becoming sluggish/unresponsive, which appears to be caused by low available memory. top is reporting 13 of 16G are "used", but adding up the memory reported by top sorted by memory usage appears like it should be closer to 3-4G "used". Attaching two top screenshots, one shows 3.3G used and system behaving well, the other shows 14G used and system lagging. In both cases, approximately the same programs are being run taking up approximately the same amount of resident memory, so not sure where all the memory usage is coming from. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-10-generic 5.3.0-10.11 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 5046 F pulseaudio CurrentDesktop: GNOME Date: Sun Sep 22 21:26:02 2019 InstallationDate: Installed on 2019-08-17 (37 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 004: ID 27c6:5395 HTMicroelectronics Goodix Fingerprint Device Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-10-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash usbcore.dyndbg=+p vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-10-generic N/A linux-backports-modules-5.3.0-10-generic N/A linux-firmware1.182 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-18 (4 days ago) dmi.bios.date: 10/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd10/10/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wayland-session ** Attachment added: ""good" memory usage" https://bugs.launchpad.net/bugs/1844962/+attachment/5290516/+files/Screenshot%20from%202019-09-20%2007-01-42.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844962 Title: apparent memory usage regression - not getting freed? Status in linux package in Ubuntu: New Bug description: In eoan on a 5.3 kernel, have noticed a few incidents of the system becoming sluggish/unresponsive, which appears to be caused by low available memory. top is reporting 13 of 16G are "used", but adding up the memory reported by top sorted by memory usage appears like it should be closer to 3-4G "used". Attaching two top screenshots, one shows 3.3G used and system behaving well, the other shows 14G used and system lagging. In both cases, approximately the same programs are being run taking up approximately the same amount of resident memory, so not sure where all the memory usage is coming from. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-10-generic 5.3.0-10.11 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 5046 F pulseaudio CurrentDesktop: GNOME Date: Sun Sep 22 21:26:02 2019 InstallationDate: Installed on 2019-08-17 (37 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 004: ID 27c6:5395 HTMicroelectronics Goodix Fingerprint Device Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-10-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash usbcore.dyndbg=+p vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-10-generic N/A linux-backports-modules-5.3.0-10-generic N/A linux-firmware1.182 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-18 (4 days ago)
[Kernel-packages] [Bug 1844962] Re: apparent memory usage regression - not getting freed?
seems this gets triggered by the dolphin emulator, but not under disco kernel 5.0.0-25 with an otherwise eoan system. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844962 Title: apparent memory usage regression - not getting freed? Status in linux package in Ubuntu: Confirmed Bug description: In eoan on a 5.3 kernel, have noticed a few incidents of the system becoming sluggish/unresponsive, which appears to be caused by low available memory. top is reporting 13 of 16G are "used", but adding up the memory reported by top sorted by memory usage appears like it should be closer to 3-4G "used". Attaching two top screenshots, one shows 3.3G used and system behaving well, the other shows 14G used and system lagging. In both cases, approximately the same programs are being run taking up approximately the same amount of resident memory, so not sure where all the memory usage is coming from. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-10-generic 5.3.0-10.11 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 5046 F pulseaudio CurrentDesktop: GNOME Date: Sun Sep 22 21:26:02 2019 InstallationDate: Installed on 2019-08-17 (37 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 004: ID 27c6:5395 HTMicroelectronics Goodix Fingerprint Device Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-10-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash usbcore.dyndbg=+p vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-10-generic N/A linux-backports-modules-5.3.0-10-generic N/A linux-firmware1.182 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-18 (4 days ago) dmi.bios.date: 10/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd10/10/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844962/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844962] Re: apparent memory usage regression - not getting freed?
899fbde1464639e3d12eaffdad8481a59b367fcb is the first bad commit commit 899fbde1464639e3d12eaffdad8481a59b367fcb Author: Philip Yang Date: Thu Dec 13 15:35:28 2018 -0500 drm/amdgpu: replace get_user_pages with HMM mirror helpers Use HMM helper function hmm_vma_fault() to get physical pages backing userptr and start CPU page table update track of those pages. Then use hmm_vma_range_done() to check if those pages are updated before amdgpu_cs_submit for gfx or before user queues are resumed for kfd. If userptr pages are updated, for gfx, amdgpu_cs_ioctl will restart from scratch, for kfd, restore worker is rescheduled to retry. HMM simplify the CPU page table concurrent update check, so remove guptasklock, mmu_invalidations, last_set_pages fields from amdgpu_ttm_tt struct. HMM does not pin the page (increase page ref count), so remove related operations like release_pages(), put_page(), mark_page_dirty(). Signed-off-by: Philip Yang Reviewed-by: Felix Kuehling Reviewed-by: Christian König Signed-off-by: Alex Deucher :04 04 0c9f0e2e82e5e4d2d3a4c0daea22eb911244b771 fdcdc7c80f5383486962edf4561e205b55bd8c21 M drivers $ git bisect log # bad: [f74c2bb98776e2de508f4d607cd519873065118e] Linux 5.3-rc8 # good: [1c163f4c7b3f621efff9b28a47abb36f7378d783] Linux 5.0 git bisect start 'v5.3-rc8' 'v5.0' # good: [a2d635decbfa9c1e4ae15cb05b68b2559f7f827c] Merge tag 'drm-next-2019-05-09' of git://anongit.freedesktop.org/drm/drm git bisect good a2d635decbfa9c1e4ae15cb05b68b2559f7f827c # good: [a2d635decbfa9c1e4ae15cb05b68b2559f7f827c] Merge tag 'drm-next-2019-05-09' of git://anongit.freedesktop.org/drm/drm git bisect good a2d635decbfa9c1e4ae15cb05b68b2559f7f827c # good: [8f6ccf6159aed1f04c6d179f61f6fb2691261e84] Merge tag 'clone3-v5.3' of git://git.kernel.org/pub/scm/linux/kernel/git/brauner/linux git bisect good 8f6ccf6159aed1f04c6d179f61f6fb2691261e84 # good: [8f6ccf6159aed1f04c6d179f61f6fb2691261e84] Merge tag 'clone3-v5.3' of git://git.kernel.org/pub/scm/linux/kernel/git/brauner/linux git bisect good 8f6ccf6159aed1f04c6d179f61f6fb2691261e84 # bad: [be8454afc50f43016ca8b6130d9673bdd0bd56ec] Merge tag 'drm-next-2019-07-16' of git://anongit.freedesktop.org/drm/drm git bisect bad be8454afc50f43016ca8b6130d9673bdd0bd56ec # bad: [be8454afc50f43016ca8b6130d9673bdd0bd56ec] Merge tag 'drm-next-2019-07-16' of git://anongit.freedesktop.org/drm/drm git bisect bad be8454afc50f43016ca8b6130d9673bdd0bd56ec # good: [d72619706abc4aa7e540ea882dae883cee7cc3b3] Merge tag 'tty-5.3-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty git bisect good d72619706abc4aa7e540ea882dae883cee7cc3b3 # bad: [83145f110eb2ada9d54fcbcf416c02de126381c1] drm/amdgpu: don't invalidate caches in RELEASE_MEM, only do the writeback git bisect bad 83145f110eb2ada9d54fcbcf416c02de126381c1 # bad: [b239c01727459ba08c44b79e6225d3c58723f282] drm/amdgpu: add mcbp driver parameter git bisect bad b239c01727459ba08c44b79e6225d3c58723f282 # good: [e1dc68a4b149d47536cd001d0d0abadbb62d37bd] drm: atmel-hlcdc: avoid initializing cfg with zero git bisect good e1dc68a4b149d47536cd001d0d0abadbb62d37bd # bad: [c53e4db71276bf257b09010935a04bdafddd458e] drm/amdgpu: cancel late_init_work before gpu reset git bisect bad c53e4db71276bf257b09010935a04bdafddd458e # good: [2da4605dce38b84cd2e5b86686f43adae1b2cacb] drm/amd/display: Use DCN functions instead of DCE git bisect good 2da4605dce38b84cd2e5b86686f43adae1b2cacb # bad: [1c1e53f7f2ce191e6787d3d0648fe8ce7088ceaa] drm/amd/doc: Add XGMI sysfs documentation git bisect bad 1c1e53f7f2ce191e6787d3d0648fe8ce7088ceaa # good: [89cd9d23e9a74d94f0db5bbbaf2ef1f6ede36ae5] drm/amdkfd: avoid HMM change cause circular lock git bisect good 89cd9d23e9a74d94f0db5bbbaf2ef1f6ede36ae5 # bad: [0803e7a9e850f9d6397c594d6c6deac9b2b6d696] drm/amdkfd: Allocate hiq and sdma mqd from mqd trunk git bisect bad 0803e7a9e850f9d6397c594d6c6deac9b2b6d696 # bad: [972fcdb52fe865a2f639e3200b97e648f34a0f41] drm/amdkfd: Introduce asic-specific mqd_manager_init function git bisect bad 972fcdb52fe865a2f639e3200b97e648f34a0f41 # bad: [6c55d6e90e68a4789cbd72a0287026d4dfb4a9f9] drm/amdkfd: support concurrent userptr update for HMM git bisect bad 6c55d6e90e68a4789cbd72a0287026d4dfb4a9f9 # bad: [ad595b8634f36f04bf69bef4eff854091d94f8b3] drm/amdgpu: fix HMM config dependency issue git bisect bad ad595b8634f36f04bf69bef4eff854091d94f8b3 # bad: [899fbde1464639e3d12eaffdad8481a59b367fcb] drm/amdgpu: replace get_user_pages with HMM mirror helpers git bisect bad 899fbde1464639e3d12eaffdad8481a59b367fcb # first bad commit: [899fbde1464639e3d12eaffdad8481a59b367fcb] drm/amdgpu: replace get_user_pages with HMM mirror helpers -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844962 Title: apparent memory usage regression - not getting freed? St
[Kernel-packages] [Bug 1844962] Re: apparent memory usage regression - not getting freed?
(also, still an issue with 5.3.0-13) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844962 Title: apparent memory usage regression - not getting freed? Status in linux package in Ubuntu: Confirmed Bug description: In eoan on a 5.3 kernel, have noticed a few incidents of the system becoming sluggish/unresponsive, which appears to be caused by low available memory. top is reporting 13 of 16G are "used", but adding up the memory reported by top sorted by memory usage appears like it should be closer to 3-4G "used". Attaching two top screenshots, one shows 3.3G used and system behaving well, the other shows 14G used and system lagging. In both cases, approximately the same programs are being run taking up approximately the same amount of resident memory, so not sure where all the memory usage is coming from. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-10-generic 5.3.0-10.11 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 5046 F pulseaudio CurrentDesktop: GNOME Date: Sun Sep 22 21:26:02 2019 InstallationDate: Installed on 2019-08-17 (37 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 004: ID 27c6:5395 HTMicroelectronics Goodix Fingerprint Device Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-10-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash usbcore.dyndbg=+p vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-10-generic N/A linux-backports-modules-5.3.0-10-generic N/A linux-firmware1.182 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-18 (4 days ago) dmi.bios.date: 10/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd10/10/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844962/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965968] Re: post jammy update, black/flickering screen on boot
i915.enable_psr=0 did not fix the black screen issue, but did appear to remove the flickering purple streaks, fwiw. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1965968 Title: post jammy update, black/flickering screen on boot Status in linux package in Ubuntu: Confirmed Bug description: After initial jammy upgrade things were working fine, but after a recent update the machine boots to a blank screen. There are occasional purplish flickers that seem to correspond with keypresses, but even blindly typing the encrypted disk password doesn't appear to advance the boot process to gdm. Plugging in an external monitor does fix the issue and allow boot to proceed, but obviously doesn't help if not near an external monitor. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: plymouth 0.9.5+git20211018-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Mar 22 09:22:26 2022 DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth InstallationDate: Installed on 2019-08-17 (948 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) MachineType: Dell Inc. XPS 15 9575 ProcCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/ubuntu-gnome-text/ubuntu-gnome-text.plymouth UpgradeStatus: Upgraded to jammy on 2022-03-18 (3 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965968/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965968] Re: post jammy update, black/flickering screen on boot
both of those exhibit the bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1965968 Title: post jammy update, black/flickering screen on boot Status in linux package in Ubuntu: Confirmed Bug description: After initial jammy upgrade things were working fine, but after a recent update the machine boots to a blank screen. There are occasional purplish flickers that seem to correspond with keypresses, but even blindly typing the encrypted disk password doesn't appear to advance the boot process to gdm. Plugging in an external monitor does fix the issue and allow boot to proceed, but obviously doesn't help if not near an external monitor. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: plymouth 0.9.5+git20211018-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Mar 22 09:22:26 2022 DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth InstallationDate: Installed on 2019-08-17 (948 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) MachineType: Dell Inc. XPS 15 9575 ProcCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/ubuntu-gnome-text/ubuntu-gnome-text.plymouth UpgradeStatus: Upgraded to jammy on 2022-03-18 (3 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965968/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965968] Re: post jammy update, black/flickering screen on boot
v5.14: black screen v5.13: black screen with i915.enable_psr=0, works without went back and tried the initial 5.13.0-35 as well, and it also does the black screen with i915.enable_psr=0 will try to find the first mainline 5.13 that doesn't work today (or if they all work). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1965968 Title: post jammy update, black/flickering screen on boot Status in linux package in Ubuntu: Confirmed Bug description: After initial jammy upgrade things were working fine, but after a recent update the machine boots to a blank screen. There are occasional purplish flickers that seem to correspond with keypresses, but even blindly typing the encrypted disk password doesn't appear to advance the boot process to gdm. Plugging in an external monitor does fix the issue and allow boot to proceed, but obviously doesn't help if not near an external monitor. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: plymouth 0.9.5+git20211018-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Mar 22 09:22:26 2022 DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth InstallationDate: Installed on 2019-08-17 (948 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) MachineType: Dell Inc. XPS 15 9575 ProcCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/ubuntu-gnome-text/ubuntu-gnome-text.plymouth UpgradeStatus: Upgraded to jammy on 2022-03-18 (3 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965968/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965968] Re: post jammy update, black/flickering screen on boot
based on previous comment no longer testing with i915.enable_psr=0, but here's what i've narrowed it down to: v5.13.19: works v5.14.0rc2: black screen looks like the v5.14.0rc1 build failed so can't test that? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1965968 Title: post jammy update, black/flickering screen on boot Status in linux package in Ubuntu: Confirmed Bug description: After initial jammy upgrade things were working fine, but after a recent update the machine boots to a blank screen. There are occasional purplish flickers that seem to correspond with keypresses, but even blindly typing the encrypted disk password doesn't appear to advance the boot process to gdm. Plugging in an external monitor does fix the issue and allow boot to proceed, but obviously doesn't help if not near an external monitor. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: plymouth 0.9.5+git20211018-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Mar 22 09:22:26 2022 DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth InstallationDate: Installed on 2019-08-17 (948 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) MachineType: Dell Inc. XPS 15 9575 ProcCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/ubuntu-gnome-text/ubuntu-gnome-text.plymouth UpgradeStatus: Upgraded to jammy on 2022-03-18 (3 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965968/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958620] Re: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up
Was the Precision 5530 2-in-1 version of this machine ever certified? don't know if it would have the exact same issue but its the same chipset. In the meantime I'm attempting to bisect the mainline kernel to find the commit that broke this. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1958620 Title: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up Status in linux package in Ubuntu: Confirmed Bug description: This looks like a regression from the 5.13.0-20-generic kernel to the 5.15.0-17-generic kernel. The display works fine under efifb, but as soon as the DRM drivers are loaded and KMS kicks in the display is replaced by black with flickering white (apparently when what would be on the output changes). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7134 F pipewire-media- /dev/snd/seq:chris 7133 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 21 17:07:08 2022 InstallationDate: Installed on 2021-06-26 (208 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago) dmi.bios.date: 07/07/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958620] Re: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up
after bisection:
6d7a793aabf31d7ba2b16fc13a94ccf0b90e4be0 is the first bad commit
commit 6d7a793aabf31d7ba2b16fc13a94ccf0b90e4be0
Author: José Roberto de Souza
Date: Fri May 14 16:22:45 2021 -0700
drm/i915/display: Allow fastsets when DP_SDP_VSC infoframe do not match
with PSR enabled
When PSR is enabled it handles DP_SDP_VSC, changing revision and all
the other fields as necessary.
It can also enabled and disable this SDP as needed without a full
modeset.
So here masking DP_SDP_VSC bit when previous and future state PSR
enabled, it will still be checked when comparing the asked state
to what was programmed to hardware.
Cc: Gwan-gyeong Mun
Cc: Radhakrishna Sripada
Reported-by: Ville Syrjälä
Fixes: 78b772e1a01f ("drm/i915/display: Fill PSR state during hardware
configuration read out")
Signed-off-by: José Roberto de Souza
Reviewed-by: Gwan-gyeong Mun
Link:
https://patchwork.freedesktop.org/patch/msgid/20210514232247.144542-2-jose.so...@intel.com
drivers/gpu/drm/i915/display/intel_display.c | 17 -
1 file changed, 16 insertions(+), 1 deletion(-)
** Attachment added: "bisect log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958620/+attachment/5573585/+files/bisect
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1958620
Title:
[Dell XPS 15 9575] Flickering white/black screen once KMS comes up
Status in linux package in Ubuntu:
Confirmed
Bug description:
This looks like a regression from the 5.13.0-20-generic kernel to the
5.15.0-17-generic kernel. The display works fine under efifb, but as
soon as the DRM drivers are loaded and KMS kicks in the display is
replaced by black with flickering white (apparently when what would be
on the output changes).
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-17-generic 5.15.0-17.17
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
Uname: Linux 5.13.0-20-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu75
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: chris 7134 F pipewire-media-
/dev/snd/seq:chris 7133 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 21 17:07:08 2022
InstallationDate: Installed on 2021-06-26 (208 days ago)
InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622)
MachineType: Dell Inc. XPS 15 9575
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic
root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-20-generic N/A
linux-backports-modules-5.13.0-20-generic N/A
linux-firmware 1.204
SourcePackage: linux
UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago)
dmi.bios.date: 07/07/2019
dmi.bios.release: 1.7
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.7.1
dmi.board.name: 0C32VW
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 31
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9575
dmi.product.sku: 080D
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958620/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958620] Re: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up
Yeah I was confused that the built kernel versions were in the v5.13-rc range, but according to `git tag --contains 6d7a793aabf31d7ba2b16fc13a94ccf0b90e4be0` (and the list of tags in https://github.com/torvalds/linux/commit/6d7a793aabf31d7ba2b16fc13a94ccf0b90e4be0) v5.14-rc1 is the first tag that has this commit in it? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1958620 Title: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up Status in linux package in Ubuntu: Confirmed Bug description: This looks like a regression from the 5.13.0-20-generic kernel to the 5.15.0-17-generic kernel. The display works fine under efifb, but as soon as the DRM drivers are loaded and KMS kicks in the display is replaced by black with flickering white (apparently when what would be on the output changes). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7134 F pipewire-media- /dev/snd/seq:chris 7133 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 21 17:07:08 2022 InstallationDate: Installed on 2021-06-26 (208 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago) dmi.bios.date: 07/07/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958620] Re: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up
appears to be fixed in drm-tip 2022-03-29 packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1958620 Title: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up Status in linux package in Ubuntu: Triaged Bug description: This looks like a regression from the 5.13.0-20-generic kernel to the 5.15.0-17-generic kernel. The display works fine under efifb, but as soon as the DRM drivers are loaded and KMS kicks in the display is replaced by black with flickering white (apparently when what would be on the output changes). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7134 F pipewire-media- /dev/snd/seq:chris 7133 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 21 17:07:08 2022 InstallationDate: Installed on 2021-06-26 (208 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago) dmi.bios.date: 07/07/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958620] Re: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up
If I didn't get my good/bad confused on the reverse bisection, this appears to be the commit that fixes it: 5ac860cc52540df8bca27e0bb25b6744df67e8f0 is the first bad commit commit 5ac860cc52540df8bca27e0bb25b6744df67e8f0 Author: Ville Syrjälä Date: Thu Mar 3 21:12:06 2022 +0200 drm/i915: Fix DBUF bandwidth vs. cdclk handling Make the dbuf bandwidth min cdclk calculations match the spec more closely. Supposedly the arbiter can only guarantee an equal share of the total bandwidth of the slice to each active plane on that slice. So we take the max bandwidth of any of the planes on each slice and multiply that by the number of active planes on the slice to get a worst case estimate on how much bandwidth we require. Signed-off-by: Ville Syrjälä Link: https://patchwork.freedesktop.org/patch/msgid/20220303191207.27931-9-ville.syrj...@linux.intel.com Reviewed-by: Stanislav Lisovskiy drivers/gpu/drm/i915/display/intel_bw.c| 157 - drivers/gpu/drm/i915/display/intel_bw.h| 10 +- drivers/gpu/drm/i915/display/intel_cdclk.c | 67 +--- drivers/gpu/drm/i915/display/intel_cdclk.h | 2 + 4 files changed, 147 insertions(+), 89 deletions(-) ** Attachment added: "bisect log 2" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958620/+attachment/5574955/+files/bisect -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1958620 Title: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up Status in linux package in Ubuntu: Triaged Bug description: This looks like a regression from the 5.13.0-20-generic kernel to the 5.15.0-17-generic kernel. The display works fine under efifb, but as soon as the DRM drivers are loaded and KMS kicks in the display is replaced by black with flickering white (apparently when what would be on the output changes). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7134 F pipewire-media- /dev/snd/seq:chris 7133 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 21 17:07:08 2022 InstallationDate: Installed on 2021-06-26 (208 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago) dmi.bios.date: 07/07/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958620] Re: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up
** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #5534 https://gitlab.freedesktop.org/drm/intel/-/issues/5534 ** Also affects: linux via https://gitlab.freedesktop.org/drm/intel/-/issues/5534 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1958620 Title: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: This looks like a regression from the 5.13.0-20-generic kernel to the 5.15.0-17-generic kernel. The display works fine under efifb, but as soon as the DRM drivers are loaded and KMS kicks in the display is replaced by black with flickering white (apparently when what would be on the output changes). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7134 F pipewire-media- /dev/snd/seq:chris 7133 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 21 17:07:08 2022 InstallationDate: Installed on 2021-06-26 (208 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago) dmi.bios.date: 07/07/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1958620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958620] Re: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up
found some other reports that claim i915.fastboot=0 is a workaround, and can confirm it does work around the issue on jammy's current 5.15 kernel. https://www.reddit.com/r/pop_os/comments/scqr4n/dell_xps_15_9575_screen_flickering_upon_boot/ https://bugs.archlinux.org/task/72134 https://gitlab.freedesktop.org/drm/intel/-/issues/4952 ** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #4952 https://gitlab.freedesktop.org/drm/intel/-/issues/4952 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1958620 Title: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: This looks like a regression from the 5.13.0-20-generic kernel to the 5.15.0-17-generic kernel. The display works fine under efifb, but as soon as the DRM drivers are loaded and KMS kicks in the display is replaced by black with flickering white (apparently when what would be on the output changes). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7134 F pipewire-media- /dev/snd/seq:chris 7133 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 21 17:07:08 2022 InstallationDate: Installed on 2021-06-26 (208 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago) dmi.bios.date: 07/07/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1958620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958620] Re: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up
This bug is not fixed by 5.15.0-40-generic, and still occurs with that kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1958620 Title: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up Status in Linux: New Status in linux package in Ubuntu: Triaged Bug description: This looks like a regression from the 5.13.0-20-generic kernel to the 5.15.0-17-generic kernel. The display works fine under efifb, but as soon as the DRM drivers are loaded and KMS kicks in the display is replaced by black with flickering white (apparently when what would be on the output changes). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7134 F pipewire-media- /dev/snd/seq:chris 7133 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 21 17:07:08 2022 InstallationDate: Installed on 2021-06-26 (208 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago) dmi.bios.date: 07/07/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1958620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958620] Re: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up
also fwiw, confirmed that starting from tag Ubuntu-5.15.0-25.25 (commit f4a9abe17854fc753c84a0ba4ac275e715a008f3), reverting commit 6d7a793aabf31d7ba2b16fc13a94ccf0b90e4be0 applies cleanly and fixes the bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1958620 Title: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: This looks like a regression from the 5.13.0-20-generic kernel to the 5.15.0-17-generic kernel. The display works fine under efifb, but as soon as the DRM drivers are loaded and KMS kicks in the display is replaced by black with flickering white (apparently when what would be on the output changes). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7134 F pipewire-media- /dev/snd/seq:chris 7133 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 21 17:07:08 2022 InstallationDate: Installed on 2021-06-26 (208 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago) dmi.bios.date: 07/07/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1958620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958620] Re: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up
any plans to address this in jammy? haven't had any movement on the upstream bug so I assume reverting that one commit is probably the best option? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1958620 Title: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: This looks like a regression from the 5.13.0-20-generic kernel to the 5.15.0-17-generic kernel. The display works fine under efifb, but as soon as the DRM drivers are loaded and KMS kicks in the display is replaced by black with flickering white (apparently when what would be on the output changes). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7134 F pipewire-media- /dev/snd/seq:chris 7133 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 21 17:07:08 2022 InstallationDate: Installed on 2021-06-26 (208 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago) dmi.bios.date: 07/07/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1958620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958620] Re: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up
fwiw, this is fixed in kinetic with its 5.19 kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1958620 Title: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up Status in Linux: New Status in linux package in Ubuntu: Triaged Bug description: This looks like a regression from the 5.13.0-20-generic kernel to the 5.15.0-17-generic kernel. The display works fine under efifb, but as soon as the DRM drivers are loaded and KMS kicks in the display is replaced by black with flickering white (apparently when what would be on the output changes). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7134 F pipewire-media- /dev/snd/seq:chris 7133 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 21 17:07:08 2022 InstallationDate: Installed on 2021-06-26 (208 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago) dmi.bios.date: 07/07/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1958620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1729010] Re: USB hub stops working after suspend(s?)
in limited testing so far, v4.16-rc2 appears better -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729010 Title: USB hub stops working after suspend(s?) Status in linux package in Ubuntu: Confirmed Bug description: On initial boot, my usb hub works fine, but after a (series of?) suspends, I stop being able to see devices that are plugged into it. journalctl output on plugging it in: Oct 31 07:08:36 spiny kernel: usb 1-1: new high-speed USB device number 21 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device found, idVendor=0409, idProduct=005a Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: USB hub found Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: 4 ports detected Oct 31 07:08:36 spiny kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC=fe80::::a299:9bff:fe17:9047 DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=32325 PROTO=UDP SPT=8612 DPT=8612 LEN=24 Oct 31 07:08:36 spiny kernel: usb 1-1.1: new high-speed USB device number 22 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device found, idVendor=0b95, idProduct=772a Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 31 07:08:36 spiny kernel: usb 1-1.1: Product: AX88x72A Oct 31 07:08:36 spiny kernel: usb 1-1.1: Manufacturer: ASIX Elec. Corp. Oct 31 07:08:36 spiny kernel: usb 1-1.1: SerialNumber: 47EDE2 Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 eth0: register 'asix' at usb-:00:14.0-1.1, ASIX AX88772 USB 2.0 Ethernet, 00:50:b6:47:ed:e2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.0438] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/7) Oct 31 07:08:37 spiny mtp-probe[13207]: checking bus 1, device 22: "/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1" Oct 31 07:08:37 spiny mtp-probe[13207]: bus: 1, device: 22 was not an MTP device Oct 31 07:08:37 spiny systemd-udevd[13206]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 enx0050b647ede2: renamed from eth0 Oct 31 07:08:37 spiny pkexec[13215]: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Oct 31 07:08:37 spiny pkexec[13215]: jbarnett: Executing command [USER=root] [TTY=unknown] [CWD=/home/jbarnett] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 31] Oct 31 07:08:37 spiny pkexec[13214]: gdm: Error executing command as another user: Not authorized [USER=root] [TTY=unknown] [CWD=/var/lib/gdm3] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 48] Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: Error executing command as another user: Not authorized Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: This incident has been reported. Oct 31 07:08:37 spiny systemd-networkd[1119]: eth0: Renamed to enx0050b647ede2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1066] device (eth0): interface index 10 renamed iface from 'eth0' to 'enx0050b647ede2' Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] devices added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2) Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] device added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2): no ifupdown configuration found. Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1217] device (enx0050b647ede2): state change: unmanaged -> unavailable (reason 'managed', internal state 'external') Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1274] keyfile: add connection in-memory (9365f42f-9dd9-3bdc-bbad-e7062efcaf7c,"Wired connection 4") Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1284] settings: (enx0050b647ede2): created default wired connection 'Wired connection 4' Oct 31 07:08:37 spiny systemd[1]: Starting systemd-resolved-update-resolvconf.service... Oct 31 07:08:37 spiny systemd[1]: Started systemd-resolved-update-resolvconf.service. Oct 31 07:08:37 spiny kernel: usb 1-1.2: new full-speed USB device number 23 using xhci_hcd Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device found, idVendor=0d8c, idProduct=0105 Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device strings: Mfr=3, Product=1, SerialNumber=0 Oct 31 07:08:37 spiny kernel: usb 1-1.2: Product: U
[Kernel-packages] [Bug 1729010] Re: USB hub stops working after suspend(s?)
i have not yet experienced it in v4.16-rc2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729010 Title: USB hub stops working after suspend(s?) Status in linux package in Ubuntu: Confirmed Bug description: On initial boot, my usb hub works fine, but after a (series of?) suspends, I stop being able to see devices that are plugged into it. journalctl output on plugging it in: Oct 31 07:08:36 spiny kernel: usb 1-1: new high-speed USB device number 21 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device found, idVendor=0409, idProduct=005a Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: USB hub found Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: 4 ports detected Oct 31 07:08:36 spiny kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC=fe80::::a299:9bff:fe17:9047 DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=32325 PROTO=UDP SPT=8612 DPT=8612 LEN=24 Oct 31 07:08:36 spiny kernel: usb 1-1.1: new high-speed USB device number 22 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device found, idVendor=0b95, idProduct=772a Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 31 07:08:36 spiny kernel: usb 1-1.1: Product: AX88x72A Oct 31 07:08:36 spiny kernel: usb 1-1.1: Manufacturer: ASIX Elec. Corp. Oct 31 07:08:36 spiny kernel: usb 1-1.1: SerialNumber: 47EDE2 Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 eth0: register 'asix' at usb-:00:14.0-1.1, ASIX AX88772 USB 2.0 Ethernet, 00:50:b6:47:ed:e2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.0438] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/7) Oct 31 07:08:37 spiny mtp-probe[13207]: checking bus 1, device 22: "/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1" Oct 31 07:08:37 spiny mtp-probe[13207]: bus: 1, device: 22 was not an MTP device Oct 31 07:08:37 spiny systemd-udevd[13206]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 enx0050b647ede2: renamed from eth0 Oct 31 07:08:37 spiny pkexec[13215]: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Oct 31 07:08:37 spiny pkexec[13215]: jbarnett: Executing command [USER=root] [TTY=unknown] [CWD=/home/jbarnett] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 31] Oct 31 07:08:37 spiny pkexec[13214]: gdm: Error executing command as another user: Not authorized [USER=root] [TTY=unknown] [CWD=/var/lib/gdm3] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 48] Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: Error executing command as another user: Not authorized Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: This incident has been reported. Oct 31 07:08:37 spiny systemd-networkd[1119]: eth0: Renamed to enx0050b647ede2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1066] device (eth0): interface index 10 renamed iface from 'eth0' to 'enx0050b647ede2' Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] devices added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2) Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] device added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2): no ifupdown configuration found. Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1217] device (enx0050b647ede2): state change: unmanaged -> unavailable (reason 'managed', internal state 'external') Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1274] keyfile: add connection in-memory (9365f42f-9dd9-3bdc-bbad-e7062efcaf7c,"Wired connection 4") Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1284] settings: (enx0050b647ede2): created default wired connection 'Wired connection 4' Oct 31 07:08:37 spiny systemd[1]: Starting systemd-resolved-update-resolvconf.service... Oct 31 07:08:37 spiny systemd[1]: Started systemd-resolved-update-resolvconf.service. Oct 31 07:08:37 spiny kernel: usb 1-1.2: new full-speed USB device number 23 using xhci_hcd Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device found, idVendor=0d8c, idProduct=0105 Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device strings: Mfr=3, Product=1, SerialNumber=0 Oct 31 07:08:37 spiny kernel: usb 1-1.2: Product: USB Multim
[Kernel-packages] [Bug 1729010] Re: USB hub stops working after suspend(s?)
appears to be gone in 4.15.0-11 as well -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729010 Title: USB hub stops working after suspend(s?) Status in linux package in Ubuntu: Confirmed Bug description: On initial boot, my usb hub works fine, but after a (series of?) suspends, I stop being able to see devices that are plugged into it. journalctl output on plugging it in: Oct 31 07:08:36 spiny kernel: usb 1-1: new high-speed USB device number 21 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device found, idVendor=0409, idProduct=005a Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: USB hub found Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: 4 ports detected Oct 31 07:08:36 spiny kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC=fe80::::a299:9bff:fe17:9047 DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=32325 PROTO=UDP SPT=8612 DPT=8612 LEN=24 Oct 31 07:08:36 spiny kernel: usb 1-1.1: new high-speed USB device number 22 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device found, idVendor=0b95, idProduct=772a Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 31 07:08:36 spiny kernel: usb 1-1.1: Product: AX88x72A Oct 31 07:08:36 spiny kernel: usb 1-1.1: Manufacturer: ASIX Elec. Corp. Oct 31 07:08:36 spiny kernel: usb 1-1.1: SerialNumber: 47EDE2 Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 eth0: register 'asix' at usb-:00:14.0-1.1, ASIX AX88772 USB 2.0 Ethernet, 00:50:b6:47:ed:e2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.0438] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/7) Oct 31 07:08:37 spiny mtp-probe[13207]: checking bus 1, device 22: "/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1" Oct 31 07:08:37 spiny mtp-probe[13207]: bus: 1, device: 22 was not an MTP device Oct 31 07:08:37 spiny systemd-udevd[13206]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 enx0050b647ede2: renamed from eth0 Oct 31 07:08:37 spiny pkexec[13215]: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Oct 31 07:08:37 spiny pkexec[13215]: jbarnett: Executing command [USER=root] [TTY=unknown] [CWD=/home/jbarnett] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 31] Oct 31 07:08:37 spiny pkexec[13214]: gdm: Error executing command as another user: Not authorized [USER=root] [TTY=unknown] [CWD=/var/lib/gdm3] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 48] Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: Error executing command as another user: Not authorized Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: This incident has been reported. Oct 31 07:08:37 spiny systemd-networkd[1119]: eth0: Renamed to enx0050b647ede2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1066] device (eth0): interface index 10 renamed iface from 'eth0' to 'enx0050b647ede2' Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] devices added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2) Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] device added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2): no ifupdown configuration found. Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1217] device (enx0050b647ede2): state change: unmanaged -> unavailable (reason 'managed', internal state 'external') Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1274] keyfile: add connection in-memory (9365f42f-9dd9-3bdc-bbad-e7062efcaf7c,"Wired connection 4") Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1284] settings: (enx0050b647ede2): created default wired connection 'Wired connection 4' Oct 31 07:08:37 spiny systemd[1]: Starting systemd-resolved-update-resolvconf.service... Oct 31 07:08:37 spiny systemd[1]: Started systemd-resolved-update-resolvconf.service. Oct 31 07:08:37 spiny kernel: usb 1-1.2: new full-speed USB device number 23 using xhci_hcd Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device found, idVendor=0d8c, idProduct=0105 Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device strings: Mfr=3, Product=1, SerialNumber=0 Oct 31 07:08:37 spiny kernel: usb 1-1.2: Product: USB Multimedi
[Kernel-packages] [Bug 1729010] Re: USB hub stops working after suspend(s?)
I can, but can't promise an SLA ;) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729010 Title: USB hub stops working after suspend(s?) Status in linux package in Ubuntu: Confirmed Bug description: On initial boot, my usb hub works fine, but after a (series of?) suspends, I stop being able to see devices that are plugged into it. journalctl output on plugging it in: Oct 31 07:08:36 spiny kernel: usb 1-1: new high-speed USB device number 21 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device found, idVendor=0409, idProduct=005a Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: USB hub found Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: 4 ports detected Oct 31 07:08:36 spiny kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC=fe80::::a299:9bff:fe17:9047 DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=32325 PROTO=UDP SPT=8612 DPT=8612 LEN=24 Oct 31 07:08:36 spiny kernel: usb 1-1.1: new high-speed USB device number 22 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device found, idVendor=0b95, idProduct=772a Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 31 07:08:36 spiny kernel: usb 1-1.1: Product: AX88x72A Oct 31 07:08:36 spiny kernel: usb 1-1.1: Manufacturer: ASIX Elec. Corp. Oct 31 07:08:36 spiny kernel: usb 1-1.1: SerialNumber: 47EDE2 Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 eth0: register 'asix' at usb-:00:14.0-1.1, ASIX AX88772 USB 2.0 Ethernet, 00:50:b6:47:ed:e2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.0438] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/7) Oct 31 07:08:37 spiny mtp-probe[13207]: checking bus 1, device 22: "/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1" Oct 31 07:08:37 spiny mtp-probe[13207]: bus: 1, device: 22 was not an MTP device Oct 31 07:08:37 spiny systemd-udevd[13206]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 enx0050b647ede2: renamed from eth0 Oct 31 07:08:37 spiny pkexec[13215]: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Oct 31 07:08:37 spiny pkexec[13215]: jbarnett: Executing command [USER=root] [TTY=unknown] [CWD=/home/jbarnett] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 31] Oct 31 07:08:37 spiny pkexec[13214]: gdm: Error executing command as another user: Not authorized [USER=root] [TTY=unknown] [CWD=/var/lib/gdm3] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 48] Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: Error executing command as another user: Not authorized Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: This incident has been reported. Oct 31 07:08:37 spiny systemd-networkd[1119]: eth0: Renamed to enx0050b647ede2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1066] device (eth0): interface index 10 renamed iface from 'eth0' to 'enx0050b647ede2' Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] devices added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2) Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] device added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2): no ifupdown configuration found. Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1217] device (enx0050b647ede2): state change: unmanaged -> unavailable (reason 'managed', internal state 'external') Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1274] keyfile: add connection in-memory (9365f42f-9dd9-3bdc-bbad-e7062efcaf7c,"Wired connection 4") Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1284] settings: (enx0050b647ede2): created default wired connection 'Wired connection 4' Oct 31 07:08:37 spiny systemd[1]: Starting systemd-resolved-update-resolvconf.service... Oct 31 07:08:37 spiny systemd[1]: Started systemd-resolved-update-resolvconf.service. Oct 31 07:08:37 spiny kernel: usb 1-1.2: new full-speed USB device number 23 using xhci_hcd Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device found, idVendor=0d8c, idProduct=0105 Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device strings: Mfr=3, Product=1, SerialNumber=0 Oct 31 07:08:37 spiny kernel: usb 1-1.2: Product: USB Multimedia Aud
[Kernel-packages] [Bug 1729010] Re: USB hub stops working after suspend(s?)
(I have confirmed that building at 13cfc732160f7bc7e596128ce34cda361c556966 does not exhibit the bug, fwiw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729010 Title: USB hub stops working after suspend(s?) Status in linux package in Ubuntu: Confirmed Bug description: On initial boot, my usb hub works fine, but after a (series of?) suspends, I stop being able to see devices that are plugged into it. journalctl output on plugging it in: Oct 31 07:08:36 spiny kernel: usb 1-1: new high-speed USB device number 21 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device found, idVendor=0409, idProduct=005a Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: USB hub found Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: 4 ports detected Oct 31 07:08:36 spiny kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC=fe80::::a299:9bff:fe17:9047 DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=32325 PROTO=UDP SPT=8612 DPT=8612 LEN=24 Oct 31 07:08:36 spiny kernel: usb 1-1.1: new high-speed USB device number 22 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device found, idVendor=0b95, idProduct=772a Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 31 07:08:36 spiny kernel: usb 1-1.1: Product: AX88x72A Oct 31 07:08:36 spiny kernel: usb 1-1.1: Manufacturer: ASIX Elec. Corp. Oct 31 07:08:36 spiny kernel: usb 1-1.1: SerialNumber: 47EDE2 Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 eth0: register 'asix' at usb-:00:14.0-1.1, ASIX AX88772 USB 2.0 Ethernet, 00:50:b6:47:ed:e2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.0438] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/7) Oct 31 07:08:37 spiny mtp-probe[13207]: checking bus 1, device 22: "/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1" Oct 31 07:08:37 spiny mtp-probe[13207]: bus: 1, device: 22 was not an MTP device Oct 31 07:08:37 spiny systemd-udevd[13206]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 enx0050b647ede2: renamed from eth0 Oct 31 07:08:37 spiny pkexec[13215]: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Oct 31 07:08:37 spiny pkexec[13215]: jbarnett: Executing command [USER=root] [TTY=unknown] [CWD=/home/jbarnett] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 31] Oct 31 07:08:37 spiny pkexec[13214]: gdm: Error executing command as another user: Not authorized [USER=root] [TTY=unknown] [CWD=/var/lib/gdm3] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 48] Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: Error executing command as another user: Not authorized Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: This incident has been reported. Oct 31 07:08:37 spiny systemd-networkd[1119]: eth0: Renamed to enx0050b647ede2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1066] device (eth0): interface index 10 renamed iface from 'eth0' to 'enx0050b647ede2' Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] devices added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2) Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] device added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2): no ifupdown configuration found. Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1217] device (enx0050b647ede2): state change: unmanaged -> unavailable (reason 'managed', internal state 'external') Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1274] keyfile: add connection in-memory (9365f42f-9dd9-3bdc-bbad-e7062efcaf7c,"Wired connection 4") Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1284] settings: (enx0050b647ede2): created default wired connection 'Wired connection 4' Oct 31 07:08:37 spiny systemd[1]: Starting systemd-resolved-update-resolvconf.service... Oct 31 07:08:37 spiny systemd[1]: Started systemd-resolved-update-resolvconf.service. Oct 31 07:08:37 spiny kernel: usb 1-1.2: new full-speed USB device number 23 using xhci_hcd Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device found, idVendor=0d8c, idProduct=0105 Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device strings: Mfr=3, Product=1, SerialNumber
[Kernel-packages] [Bug 1729010] Re: USB hub stops working after suspend(s?)
having some trouble with the bisect: -in order to be able to test this, the built kernel needs to include commit 13cfc732160f7bc7e596128ce34cda361c556966 which allows suspend on this machine to work -the bisect is picking commits like 6afafa7799cf6fa3c0efb6887704506d21965ad6 that don't descend from the suspend fix commit -I've tried starting the bisect from 13cfc732160f7bc7e596128ce34cda361c556966 as 'good', but am still getting commits picked by the bisect that don't include that change. any pointers on bisecting bewteen 13cfc732160f7bc7e596128ce34cda361c556966 and v4.13-rc3 ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729010 Title: USB hub stops working after suspend(s?) Status in linux package in Ubuntu: Confirmed Bug description: On initial boot, my usb hub works fine, but after a (series of?) suspends, I stop being able to see devices that are plugged into it. journalctl output on plugging it in: Oct 31 07:08:36 spiny kernel: usb 1-1: new high-speed USB device number 21 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device found, idVendor=0409, idProduct=005a Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: USB hub found Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: 4 ports detected Oct 31 07:08:36 spiny kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC=fe80::::a299:9bff:fe17:9047 DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=32325 PROTO=UDP SPT=8612 DPT=8612 LEN=24 Oct 31 07:08:36 spiny kernel: usb 1-1.1: new high-speed USB device number 22 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device found, idVendor=0b95, idProduct=772a Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 31 07:08:36 spiny kernel: usb 1-1.1: Product: AX88x72A Oct 31 07:08:36 spiny kernel: usb 1-1.1: Manufacturer: ASIX Elec. Corp. Oct 31 07:08:36 spiny kernel: usb 1-1.1: SerialNumber: 47EDE2 Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 eth0: register 'asix' at usb-:00:14.0-1.1, ASIX AX88772 USB 2.0 Ethernet, 00:50:b6:47:ed:e2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.0438] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/7) Oct 31 07:08:37 spiny mtp-probe[13207]: checking bus 1, device 22: "/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1" Oct 31 07:08:37 spiny mtp-probe[13207]: bus: 1, device: 22 was not an MTP device Oct 31 07:08:37 spiny systemd-udevd[13206]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 enx0050b647ede2: renamed from eth0 Oct 31 07:08:37 spiny pkexec[13215]: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Oct 31 07:08:37 spiny pkexec[13215]: jbarnett: Executing command [USER=root] [TTY=unknown] [CWD=/home/jbarnett] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 31] Oct 31 07:08:37 spiny pkexec[13214]: gdm: Error executing command as another user: Not authorized [USER=root] [TTY=unknown] [CWD=/var/lib/gdm3] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 48] Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: Error executing command as another user: Not authorized Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: This incident has been reported. Oct 31 07:08:37 spiny systemd-networkd[1119]: eth0: Renamed to enx0050b647ede2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1066] device (eth0): interface index 10 renamed iface from 'eth0' to 'enx0050b647ede2' Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] devices added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2) Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] device added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2): no ifupdown configuration found. Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1217] device (enx0050b647ede2): state change: unmanaged -> unavailable (reason 'managed', internal state 'external') Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1274] keyfile: add connection in-memory (9365f42f-9dd9-3bdc-bbad-e7062efcaf7c,"Wired connection 4") Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1284] settings: (enx0050b647ede2): created default wired connection 'Wired c
[Kernel-packages] [Bug 1729010] Re: USB hub stops working after suspend(s?)
reproduced the issue on v4.13rc3. both rc1 and rc2 appear to be very unstable resulting in full graphical lockups. believe I reproduced the issue on rc2 as well, but hard to tell with the general instability. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729010 Title: USB hub stops working after suspend(s?) Status in linux package in Ubuntu: Confirmed Bug description: On initial boot, my usb hub works fine, but after a (series of?) suspends, I stop being able to see devices that are plugged into it. journalctl output on plugging it in: Oct 31 07:08:36 spiny kernel: usb 1-1: new high-speed USB device number 21 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device found, idVendor=0409, idProduct=005a Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: USB hub found Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: 4 ports detected Oct 31 07:08:36 spiny kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC=fe80::::a299:9bff:fe17:9047 DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=32325 PROTO=UDP SPT=8612 DPT=8612 LEN=24 Oct 31 07:08:36 spiny kernel: usb 1-1.1: new high-speed USB device number 22 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device found, idVendor=0b95, idProduct=772a Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 31 07:08:36 spiny kernel: usb 1-1.1: Product: AX88x72A Oct 31 07:08:36 spiny kernel: usb 1-1.1: Manufacturer: ASIX Elec. Corp. Oct 31 07:08:36 spiny kernel: usb 1-1.1: SerialNumber: 47EDE2 Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 eth0: register 'asix' at usb-:00:14.0-1.1, ASIX AX88772 USB 2.0 Ethernet, 00:50:b6:47:ed:e2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.0438] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/7) Oct 31 07:08:37 spiny mtp-probe[13207]: checking bus 1, device 22: "/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1" Oct 31 07:08:37 spiny mtp-probe[13207]: bus: 1, device: 22 was not an MTP device Oct 31 07:08:37 spiny systemd-udevd[13206]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 enx0050b647ede2: renamed from eth0 Oct 31 07:08:37 spiny pkexec[13215]: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Oct 31 07:08:37 spiny pkexec[13215]: jbarnett: Executing command [USER=root] [TTY=unknown] [CWD=/home/jbarnett] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 31] Oct 31 07:08:37 spiny pkexec[13214]: gdm: Error executing command as another user: Not authorized [USER=root] [TTY=unknown] [CWD=/var/lib/gdm3] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 48] Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: Error executing command as another user: Not authorized Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: This incident has been reported. Oct 31 07:08:37 spiny systemd-networkd[1119]: eth0: Renamed to enx0050b647ede2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1066] device (eth0): interface index 10 renamed iface from 'eth0' to 'enx0050b647ede2' Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] devices added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2) Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] device added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2): no ifupdown configuration found. Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1217] device (enx0050b647ede2): state change: unmanaged -> unavailable (reason 'managed', internal state 'external') Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1274] keyfile: add connection in-memory (9365f42f-9dd9-3bdc-bbad-e7062efcaf7c,"Wired connection 4") Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1284] settings: (enx0050b647ede2): created default wired connection 'Wired connection 4' Oct 31 07:08:37 spiny systemd[1]: Starting systemd-resolved-update-resolvconf.service... Oct 31 07:08:37 spiny systemd[1]: Started systemd-resolved-update-resolvconf.service. Oct 31 07:08:37 spiny kernel: usb 1-1.2: new full-speed USB device number 23 using xhci_hcd Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device found, idVendor=0d8c, idProduct=
[Kernel-packages] [Bug 1729010] Re: USB hub stops working after suspend(s?)
USB mass storage devices appear to have the same problem as the hub i was using, while usb keyboards continue to work ok even when the hub & mass storage devices fail. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729010 Title: USB hub stops working after suspend(s?) Status in linux package in Ubuntu: Confirmed Bug description: On initial boot, my usb hub works fine, but after a (series of?) suspends, I stop being able to see devices that are plugged into it. journalctl output on plugging it in: Oct 31 07:08:36 spiny kernel: usb 1-1: new high-speed USB device number 21 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device found, idVendor=0409, idProduct=005a Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: USB hub found Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: 4 ports detected Oct 31 07:08:36 spiny kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC=fe80::::a299:9bff:fe17:9047 DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=32325 PROTO=UDP SPT=8612 DPT=8612 LEN=24 Oct 31 07:08:36 spiny kernel: usb 1-1.1: new high-speed USB device number 22 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device found, idVendor=0b95, idProduct=772a Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 31 07:08:36 spiny kernel: usb 1-1.1: Product: AX88x72A Oct 31 07:08:36 spiny kernel: usb 1-1.1: Manufacturer: ASIX Elec. Corp. Oct 31 07:08:36 spiny kernel: usb 1-1.1: SerialNumber: 47EDE2 Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 eth0: register 'asix' at usb-:00:14.0-1.1, ASIX AX88772 USB 2.0 Ethernet, 00:50:b6:47:ed:e2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.0438] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/7) Oct 31 07:08:37 spiny mtp-probe[13207]: checking bus 1, device 22: "/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1" Oct 31 07:08:37 spiny mtp-probe[13207]: bus: 1, device: 22 was not an MTP device Oct 31 07:08:37 spiny systemd-udevd[13206]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 enx0050b647ede2: renamed from eth0 Oct 31 07:08:37 spiny pkexec[13215]: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Oct 31 07:08:37 spiny pkexec[13215]: jbarnett: Executing command [USER=root] [TTY=unknown] [CWD=/home/jbarnett] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 31] Oct 31 07:08:37 spiny pkexec[13214]: gdm: Error executing command as another user: Not authorized [USER=root] [TTY=unknown] [CWD=/var/lib/gdm3] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 48] Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: Error executing command as another user: Not authorized Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: This incident has been reported. Oct 31 07:08:37 spiny systemd-networkd[1119]: eth0: Renamed to enx0050b647ede2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1066] device (eth0): interface index 10 renamed iface from 'eth0' to 'enx0050b647ede2' Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] devices added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2) Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] device added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2): no ifupdown configuration found. Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1217] device (enx0050b647ede2): state change: unmanaged -> unavailable (reason 'managed', internal state 'external') Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1274] keyfile: add connection in-memory (9365f42f-9dd9-3bdc-bbad-e7062efcaf7c,"Wired connection 4") Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1284] settings: (enx0050b647ede2): created default wired connection 'Wired connection 4' Oct 31 07:08:37 spiny systemd[1]: Starting systemd-resolved-update-resolvconf.service... Oct 31 07:08:37 spiny systemd[1]: Started systemd-resolved-update-resolvconf.service. Oct 31 07:08:37 spiny kernel: usb 1-1.2: new full-speed USB device number 23 using xhci_hcd Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device found, idVendor=0d8c, idProduct=0105 Oct 31 07:08:37 spiny kernel: usb 1-
[Kernel-packages] [Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot
1.2.0 firmware acpidump attached ** Attachment added: "1.2.0.acpidump" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822394/+attachment/5415318/+files/1.2.0.acpidump -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822394 Title: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot Status in libinput package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard are unresponsive at the gdm login screen. Keyboard works to unlock encrypted harddrive before that though. If I plug in a USB keyboard or activate my bluetooth mouse, I can use those to log in, and then after logging in the laptop touchpad and keyboard work again. Logging out of the desktop results in the laptop touchpad and keyboard working on the gdm screen. Did not see this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had not rebooted in a while, so not sure if bios or package upgrades triggered this behavior. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 29 17:51:00 2019 InstallationDate: Installed on 2018-09-26 (184 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gdm3 UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot
acpidump on latest (1.13.0) firmware. ** Attachment added: "1.13.0.acpidump" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822394/+attachment/5415405/+files/1.13.0.acpidump -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822394 Title: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot Status in libinput package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard are unresponsive at the gdm login screen. Keyboard works to unlock encrypted harddrive before that though. If I plug in a USB keyboard or activate my bluetooth mouse, I can use those to log in, and then after logging in the laptop touchpad and keyboard work again. Logging out of the desktop results in the laptop touchpad and keyboard working on the gdm screen. Did not see this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had not rebooted in a while, so not sure if bios or package upgrades triggered this behavior. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 29 17:51:00 2019 InstallationDate: Installed on 2018-09-26 (184 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gdm3 UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861521] Re: [FOCAL][REGRESSION] Intel Gen 9 brightness cannot be controlled
verified fixed with proposed kernel on dell xps15 2-in-1. Device: Mesa Intel(R) HD Graphics 630 (KBL GT2) (0x591b) ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1861521 Title: [FOCAL][REGRESSION] Intel Gen 9 brightness cannot be controlled Status in linux-5.4 package in Ubuntu: In Progress Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux-5.4 source package in Focal: In Progress Bug description: [Impact] After Ubuntu-5.4.0-9.12 which introduce DPCD backlight patches, the backlight control on some platforms fail to work. It seems using OUI string to map the panels which support DPCD backlight doesn't work well, it mis-mapped those panel that doesn't support DPCD backlight, and breaks the backlight control. [Fix] The author of the origin DPCD backlight patches recently provides a DP quirks based on EDID identification. [Fix] Verified on the machine with DPCD backlight and also on the machine which has regression with the OUI quirks, both of them work now. [Regression Potential] Low, it introduce a new quirks to list the panels which support DPCD backlight. === After upgrading from Eoan (5.3.0-29.31) to Focal (5.4.0-12.15), I no longer have the ability to control the backlight brightness on my HP EliteBook 840 G5. When pressing the brightness hotkeys, the on-screen indicator pops up and shows that the brightness setting is being changed but the actual screen brightness is stuck on the lowest setting. This laptop has a built-in privacy screen. If I activate the privacy screen (fn-f2), then the actual screen brightness goes to the maximum setting and then I am able to dim and brighten the backlight as long as the privacy screen functionality is turned on. This is a regression from Eoan's 5.3.0-29.31 kernel where I was able to control the brightness with and without the privacy screen functionality being turned on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 31 11:42:16 2020 InstallationDate: Installed on 2019-06-24 (221 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: Upgraded to focal on 2020-01-28 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-5.4/+bug/1861521/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead
fwiw, i tried to build 5.0.0.20.21 with v2 applied, and was able to reproduce the bug (I may have built it incorrectly though? I git applied the two patches from a clone of git://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/disco and then did `fakeroot debian/rules clean` ; `AUTOBUILD=1 fakeroot debian/rules binary-debs` and installed the resulting packages) tail of journalctl during reproduction: Jul 04 21:48:54 taplop systemd-sleep[11530]: Suspending system... Jul 04 21:48:54 taplop kernel: PM: suspend entry (deep) Jul 04 21:48:58 taplop kernel: PM: Syncing filesystems ... done. Jul 04 21:48:58 taplop kernel: Freezing user space processes ... (elapsed 0.003 seconds) done. Jul 04 21:48:58 taplop kernel: OOM killer disabled. Jul 04 21:48:58 taplop kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Jul 04 21:48:58 taplop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Jul 04 21:48:58 taplop kernel: usb usb2: usb auto-resume Jul 04 21:48:58 taplop kernel: hub 2-0:1.0: hub_resume Jul 04 21:48:58 taplop kernel: usb usb1: usb auto-resume Jul 04 21:48:58 taplop kernel: hub 1-0:1.0: hub_resume Jul 04 21:48:58 taplop kernel: usb usb1-port1: status 0507 change Jul 04 21:48:58 taplop kernel: usb usb1-port6: status 0107 change Jul 04 21:48:58 taplop kernel: usb usb1-port10: status 0107 change Jul 04 21:48:58 taplop kernel: hub 1-0:1.0: hub_suspend Jul 04 21:48:58 taplop kernel: usb usb1: bus suspend, wakeup 0 Jul 04 21:48:58 taplop kernel: hub 2-0:1.0: hub_suspend Jul 04 21:48:58 taplop kernel: usb usb2: bus suspend, wakeup 0 Jul 04 21:48:58 taplop kernel: PM: Some devices failed to suspend, or early wake event detected Jul 04 21:48:58 taplop kernel: usb usb1: usb resume Jul 04 21:48:58 taplop kernel: hub 1-0:1.0: hub_resume Jul 04 21:48:58 taplop kernel: usb usb1-port1: status 0507 change Jul 04 21:48:58 taplop kernel: usb usb1-port6: status 0107 change Jul 04 21:48:58 taplop kernel: usb usb1-port10: status 0107 change Jul 04 21:48:58 taplop kernel: usb usb2: usb resume Jul 04 21:48:58 taplop kernel: hub 2-0:1.0: hub_resume Jul 04 21:48:58 taplop kernel: ACPI: button: The lid device is not compliant to SW_LID. Jul 04 21:48:58 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Jul 04 21:48:58 taplop kernel: usb 1-1: usb resume Jul 04 21:48:58 taplop kernel: usb 1-10: usb resume Jul 04 21:48:58 taplop kernel: usb 1-6: usb resume Jul 04 21:48:58 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Jul 04 21:48:58 taplop kernel: usb 1-10: Waited 0ms for CONNECT Jul 04 21:48:58 taplop kernel: usb 1-10: finish resume Jul 04 21:48:58 taplop kernel: usb 1-6: Waited 0ms for CONNECT Jul 04 21:48:58 taplop kernel: usb 1-6: finish resume Jul 04 21:48:58 taplop kernel: usb 1-1: Waited 0ms for CONNECT Jul 04 21:48:58 taplop kernel: usb 1-1: finish resume Jul 04 21:48:58 taplop kernel: [drm] VCE initialized successfully. Jul 04 21:48:58 taplop kernel: nvme nvme0: 8/0/0 default/read/poll queues Jul 04 21:48:58 taplop kernel: amdgpu :01:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test f Jul 04 21:48:58 taplop kernel: amdgpu :01:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test f Jul 04 21:48:58 taplop kernel: amdgpu :01:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test f Jul 04 21:48:58 taplop kernel: [drm:amdgpu_device_ip_late_init_func_handler [amdgpu]] *ERROR* ib ring tes Jul 04 21:48:58 taplop kernel: OOM killer enabled. Jul 04 21:48:58 taplop kernel: Restarting tasks ... Jul 04 21:48:58 taplop kernel: hub 2-0:1.0: state 7 ports 8 chg evt Jul 04 21:48:58 taplop kernel: done. Jul 04 21:48:58 taplop kernel: hub 2-0:1.0: hub_suspend Jul 04 21:48:58 taplop kernel: usb usb2: bus auto-suspend, wakeup 1 Jul 04 21:48:58 taplop kernel: hub 1-0:1.0: state 7 ports 16 chg evt 0442 Jul 04 21:48:58 taplop kernel: usb 1-10: usb auto-suspend, wakeup 0 Jul 04 21:48:58 taplop kernel: usb 1-6: usb auto-suspend, wakeup 1 Jul 04 21:48:58 taplop kernel: usb 1-1: usb auto-suspend, wakeup 0 Jul 04 21:48:58 taplop kernel: hub 1-0:1.0: hub_suspend Jul 04 21:48:58 taplop kernel: usb usb1: bus auto-suspend, wakeup 1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823029 Title: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead Status in linux package in Ubuntu: Confirmed Bug description: Sometimes when suspending, the suspend process fails, and the machine becomes unresponsive to any input, has nothing but a black/off display, and fans kick in and run high (which is actually 'good' for detecting the issue has happened). journalctl output from an unsuccessful suspend: Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending... Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5332] manager: sleep: sleep re
[Kernel-packages] [Bug 1729010] [NEW] USB hub stops working after suspend(s?)
Public bug reported: On initial boot, my usb hub works fine, but after a (series of?) suspends, I stop being able to see devices that are plugged into it. journalctl output on plugging it in: Oct 31 07:08:36 spiny kernel: usb 1-1: new high-speed USB device number 21 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device found, idVendor=0409, idProduct=005a Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: USB hub found Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: 4 ports detected Oct 31 07:08:36 spiny kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC=fe80::::a299:9bff:fe17:9047 DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=32325 PROTO=UDP SPT=8612 DPT=8612 LEN=24 Oct 31 07:08:36 spiny kernel: usb 1-1.1: new high-speed USB device number 22 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device found, idVendor=0b95, idProduct=772a Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 31 07:08:36 spiny kernel: usb 1-1.1: Product: AX88x72A Oct 31 07:08:36 spiny kernel: usb 1-1.1: Manufacturer: ASIX Elec. Corp. Oct 31 07:08:36 spiny kernel: usb 1-1.1: SerialNumber: 47EDE2 Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 eth0: register 'asix' at usb-:00:14.0-1.1, ASIX AX88772 USB 2.0 Ethernet, 00:50:b6:47:ed:e2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.0438] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/7) Oct 31 07:08:37 spiny mtp-probe[13207]: checking bus 1, device 22: "/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1" Oct 31 07:08:37 spiny mtp-probe[13207]: bus: 1, device: 22 was not an MTP device Oct 31 07:08:37 spiny systemd-udevd[13206]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 enx0050b647ede2: renamed from eth0 Oct 31 07:08:37 spiny pkexec[13215]: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Oct 31 07:08:37 spiny pkexec[13215]: jbarnett: Executing command [USER=root] [TTY=unknown] [CWD=/home/jbarnett] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 31] Oct 31 07:08:37 spiny pkexec[13214]: gdm: Error executing command as another user: Not authorized [USER=root] [TTY=unknown] [CWD=/var/lib/gdm3] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 48] Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: Error executing command as another user: Not authorized Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: This incident has been reported. Oct 31 07:08:37 spiny systemd-networkd[1119]: eth0: Renamed to enx0050b647ede2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1066] device (eth0): interface index 10 renamed iface from 'eth0' to 'enx0050b647ede2' Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] devices added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2) Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] device added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2): no ifupdown configuration found. Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1217] device (enx0050b647ede2): state change: unmanaged -> unavailable (reason 'managed', internal state 'external') Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1274] keyfile: add connection in-memory (9365f42f-9dd9-3bdc-bbad-e7062efcaf7c,"Wired connection 4") Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1284] settings: (enx0050b647ede2): created default wired connection 'Wired connection 4' Oct 31 07:08:37 spiny systemd[1]: Starting systemd-resolved-update-resolvconf.service... Oct 31 07:08:37 spiny systemd[1]: Started systemd-resolved-update-resolvconf.service. Oct 31 07:08:37 spiny kernel: usb 1-1.2: new full-speed USB device number 23 using xhci_hcd Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device found, idVendor=0d8c, idProduct=0105 Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device strings: Mfr=3, Product=1, SerialNumber=0 Oct 31 07:08:37 spiny kernel: usb 1-1.2: Product: USB Multimedia Audio Device Oct 31 07:08:37 spiny kernel: usb 1-1.2: Manufacturer: C-Media Electronics Inc. Oct 31 07:08:37 spiny kernel: xhci_hcd :00:14.0: WARN: Success on ctrl setup TRB without IOC set? Oct 31 07:08:37 spiny kernel: xhci_hcd :00:14.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 0 comp_code 6 Oct 31 07:08:37 spiny kernel: xhci_hcd :00:14.0:
[Kernel-packages] [Bug 1729010] Re: USB hub stops working after suspend(s?)
its not instantly reproducible so it'll take a while to ensure it's really gone, but i'll run with my last installed kernel (4.13.0-12) for a while and see, and then also try the latest mainline 4.14 and report back -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729010 Title: USB hub stops working after suspend(s?) Status in linux package in Ubuntu: Incomplete Bug description: On initial boot, my usb hub works fine, but after a (series of?) suspends, I stop being able to see devices that are plugged into it. journalctl output on plugging it in: Oct 31 07:08:36 spiny kernel: usb 1-1: new high-speed USB device number 21 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device found, idVendor=0409, idProduct=005a Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: USB hub found Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: 4 ports detected Oct 31 07:08:36 spiny kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC=fe80::::a299:9bff:fe17:9047 DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=32325 PROTO=UDP SPT=8612 DPT=8612 LEN=24 Oct 31 07:08:36 spiny kernel: usb 1-1.1: new high-speed USB device number 22 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device found, idVendor=0b95, idProduct=772a Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 31 07:08:36 spiny kernel: usb 1-1.1: Product: AX88x72A Oct 31 07:08:36 spiny kernel: usb 1-1.1: Manufacturer: ASIX Elec. Corp. Oct 31 07:08:36 spiny kernel: usb 1-1.1: SerialNumber: 47EDE2 Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 eth0: register 'asix' at usb-:00:14.0-1.1, ASIX AX88772 USB 2.0 Ethernet, 00:50:b6:47:ed:e2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.0438] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/7) Oct 31 07:08:37 spiny mtp-probe[13207]: checking bus 1, device 22: "/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1" Oct 31 07:08:37 spiny mtp-probe[13207]: bus: 1, device: 22 was not an MTP device Oct 31 07:08:37 spiny systemd-udevd[13206]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 enx0050b647ede2: renamed from eth0 Oct 31 07:08:37 spiny pkexec[13215]: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Oct 31 07:08:37 spiny pkexec[13215]: jbarnett: Executing command [USER=root] [TTY=unknown] [CWD=/home/jbarnett] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 31] Oct 31 07:08:37 spiny pkexec[13214]: gdm: Error executing command as another user: Not authorized [USER=root] [TTY=unknown] [CWD=/var/lib/gdm3] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 48] Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: Error executing command as another user: Not authorized Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: This incident has been reported. Oct 31 07:08:37 spiny systemd-networkd[1119]: eth0: Renamed to enx0050b647ede2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1066] device (eth0): interface index 10 renamed iface from 'eth0' to 'enx0050b647ede2' Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] devices added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2) Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] device added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2): no ifupdown configuration found. Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1217] device (enx0050b647ede2): state change: unmanaged -> unavailable (reason 'managed', internal state 'external') Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1274] keyfile: add connection in-memory (9365f42f-9dd9-3bdc-bbad-e7062efcaf7c,"Wired connection 4") Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1284] settings: (enx0050b647ede2): created default wired connection 'Wired connection 4' Oct 31 07:08:37 spiny systemd[1]: Starting systemd-resolved-update-resolvconf.service... Oct 31 07:08:37 spiny systemd[1]: Started systemd-resolved-update-resolvconf.service. Oct 31 07:08:37 spiny kernel: usb 1-1.2: new full-speed USB device number 23 using xhci_hcd Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device found, idVendor=0d8c, idPr
[Kernel-packages] [Bug 1729010] Re: USB hub stops working after suspend(s?)
Reproduced on 4.13.0-12, trying mainline now -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729010 Title: USB hub stops working after suspend(s?) Status in linux package in Ubuntu: Incomplete Bug description: On initial boot, my usb hub works fine, but after a (series of?) suspends, I stop being able to see devices that are plugged into it. journalctl output on plugging it in: Oct 31 07:08:36 spiny kernel: usb 1-1: new high-speed USB device number 21 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device found, idVendor=0409, idProduct=005a Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: USB hub found Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: 4 ports detected Oct 31 07:08:36 spiny kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC=fe80::::a299:9bff:fe17:9047 DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=32325 PROTO=UDP SPT=8612 DPT=8612 LEN=24 Oct 31 07:08:36 spiny kernel: usb 1-1.1: new high-speed USB device number 22 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device found, idVendor=0b95, idProduct=772a Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 31 07:08:36 spiny kernel: usb 1-1.1: Product: AX88x72A Oct 31 07:08:36 spiny kernel: usb 1-1.1: Manufacturer: ASIX Elec. Corp. Oct 31 07:08:36 spiny kernel: usb 1-1.1: SerialNumber: 47EDE2 Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 eth0: register 'asix' at usb-:00:14.0-1.1, ASIX AX88772 USB 2.0 Ethernet, 00:50:b6:47:ed:e2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.0438] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/7) Oct 31 07:08:37 spiny mtp-probe[13207]: checking bus 1, device 22: "/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1" Oct 31 07:08:37 spiny mtp-probe[13207]: bus: 1, device: 22 was not an MTP device Oct 31 07:08:37 spiny systemd-udevd[13206]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 enx0050b647ede2: renamed from eth0 Oct 31 07:08:37 spiny pkexec[13215]: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Oct 31 07:08:37 spiny pkexec[13215]: jbarnett: Executing command [USER=root] [TTY=unknown] [CWD=/home/jbarnett] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 31] Oct 31 07:08:37 spiny pkexec[13214]: gdm: Error executing command as another user: Not authorized [USER=root] [TTY=unknown] [CWD=/var/lib/gdm3] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 48] Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: Error executing command as another user: Not authorized Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: This incident has been reported. Oct 31 07:08:37 spiny systemd-networkd[1119]: eth0: Renamed to enx0050b647ede2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1066] device (eth0): interface index 10 renamed iface from 'eth0' to 'enx0050b647ede2' Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] devices added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2) Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] device added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2): no ifupdown configuration found. Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1217] device (enx0050b647ede2): state change: unmanaged -> unavailable (reason 'managed', internal state 'external') Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1274] keyfile: add connection in-memory (9365f42f-9dd9-3bdc-bbad-e7062efcaf7c,"Wired connection 4") Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1284] settings: (enx0050b647ede2): created default wired connection 'Wired connection 4' Oct 31 07:08:37 spiny systemd[1]: Starting systemd-resolved-update-resolvconf.service... Oct 31 07:08:37 spiny systemd[1]: Started systemd-resolved-update-resolvconf.service. Oct 31 07:08:37 spiny kernel: usb 1-1.2: new full-speed USB device number 23 using xhci_hcd Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device found, idVendor=0d8c, idProduct=0105 Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device strings: Mfr=3, Product=1, SerialNumber=0 Oct 31 07:08:37 spiny kernel: usb 1-1.2: Product: USB Mul
[Kernel-packages] [Bug 1721400] Re: Screen dim during encryption unlock prompt
Reproduced on v4.14-rc7 ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu Artful) Status: Incomplete => Confirmed ** 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/1721400 Title: Screen dim during encryption unlock prompt Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: In Artful, since 4.13 kernel, the screen gets super dim after the grub prompt while displaying the hard drive encryption unlock screen. Soon after unlocking the hard drive, the screen returns to normal brightness, but it's hard to even see that the unlock screen is being displayed. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jbarnett 2842 F pulseaudio /dev/snd/controlC3: jbarnett 2842 F pulseaudio /dev/snd/controlC0: jbarnett 2842 F pulseaudio /dev/snd/controlC1: jbarnett 2842 F pulseaudio CurrentDesktop: GNOME Date: Wed Oct 4 14:36:01 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=dd225ec0-47f4-49d8-a51c-a2547f8eb945 InstallationDate: Installed on 2015-08-21 (775 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) MachineType: Apple Inc. MacBookPro11,4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.168 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B04.1506051511 dmi.board.name: Mac-06F11FD93F0323C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,4 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11FD93F0323C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro11,4 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1721400] Re: Screen dim during encryption unlock prompt
it does reproduce on 4.12.0-13. Not sure exactly what kernel I was running when it was last working, but will try a few more and report back after finishing testing mainline for a separate bug -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1721400 Title: Screen dim during encryption unlock prompt Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: In Artful, since 4.13 kernel, the screen gets super dim after the grub prompt while displaying the hard drive encryption unlock screen. Soon after unlocking the hard drive, the screen returns to normal brightness, but it's hard to even see that the unlock screen is being displayed. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jbarnett 2842 F pulseaudio /dev/snd/controlC3: jbarnett 2842 F pulseaudio /dev/snd/controlC0: jbarnett 2842 F pulseaudio /dev/snd/controlC1: jbarnett 2842 F pulseaudio CurrentDesktop: GNOME Date: Wed Oct 4 14:36:01 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=dd225ec0-47f4-49d8-a51c-a2547f8eb945 InstallationDate: Installed on 2015-08-21 (775 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) MachineType: Apple Inc. MacBookPro11,4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.168 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B04.1506051511 dmi.board.name: Mac-06F11FD93F0323C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,4 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11FD93F0323C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro11,4 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1167586] Re: 8086:4239 Wireless bandwidth throttled
sticker has the following info : HP Envy 15 product: nx346AV model: 15t-1100 rev: 1522-110 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1167586 Title: 8086:4239 Wireless bandwidth throttled Status in “linux” package in Ubuntu: Incomplete Bug description: I'm at a location with a 50Mbit connection. If I connect via an ethernet cable, I get approx 50Mbit downstream at speedtest.net / similar services. If I connect via wireless in windows, I get approx 20Mbit downstream (other users macs get ~20Mbit as well). If I connect via wireless in ubuntu (iwlwifi driver), I get approx 5 Mbit downstream. Would expect to get ~20Mbit. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-28-generic 3.5.0-28.47 ProcVersionSignature: Ubuntu 3.5.0-28.47-generic 3.5.7.9 Uname: Linux 3.5.0-28-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jbarnett 3048 F pulseaudio /dev/snd/controlC0: jbarnett 3048 F pulseaudio /dev/snd/pcmC0D0c: jbarnett 3048 F...m pulseaudio /dev/snd/pcmC0D0p: jbarnett 3048 F...m pulseaudio Date: Wed Apr 10 14:33:16 2013 HibernationDevice: RESUME=UUID=6a792c43-ea80-4425-961e-ccde894552ed InstallationDate: Installed on 2010-04-19 (1087 days ago) InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate amd64 (20100419.1) MachineType: Hewlett-Packard HP ENVY 15 Notebook PC MarkForUpload: True ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-28-generic root=UUID=639dc488-e095-42a4-8c1f-ffb1a9299e1c ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-28-generic N/A linux-backports-modules-3.5.0-28-generic N/A linux-firmware1.95.1 SourcePackage: linux UpgradeStatus: Upgraded to quantal on 2012-10-05 (187 days ago) dmi.bios.date: 10/12/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.2B dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1522 dmi.board.vendor: Hewlett-Packard dmi.board.version: 36.35 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.2B:bd10/12/2010:svnHewlett-Packard:pnHPENVY15NotebookPC:pvr048F1124192000153:rvnHewlett-Packard:rn1522:rvr36.35:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP ENVY 15 Notebook PC dmi.product.version: 048F1124192000153 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1167586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1167586] Re: 8086:4239 [HP Envy 15t-1100] Wireless bandwidth throttled
i couldn't get that kernel to boot to anything other than a blank/black screen, not sure if fglrx related, but tried to point to ati driver in xorg.conf and still had the same problem? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1167586 Title: 8086:4239 [HP Envy 15t-1100] Wireless bandwidth throttled Status in “linux” package in Ubuntu: Incomplete Bug description: I'm at a location with a 50Mbit connection. If I connect via an ethernet cable, I get approx 50Mbit downstream at speedtest.net / similar services. If I connect via wireless in windows, I get approx 20Mbit downstream (other users macs get ~20Mbit as well). If I connect via wireless in ubuntu (iwlwifi driver), I get approx 5 Mbit downstream. Would expect to get ~20Mbit. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-28-generic 3.5.0-28.47 ProcVersionSignature: Ubuntu 3.5.0-28.47-generic 3.5.7.9 Uname: Linux 3.5.0-28-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jbarnett 3048 F pulseaudio /dev/snd/controlC0: jbarnett 3048 F pulseaudio /dev/snd/pcmC0D0c: jbarnett 3048 F...m pulseaudio /dev/snd/pcmC0D0p: jbarnett 3048 F...m pulseaudio Date: Wed Apr 10 14:33:16 2013 HibernationDevice: RESUME=UUID=6a792c43-ea80-4425-961e-ccde894552ed InstallationDate: Installed on 2010-04-19 (1087 days ago) InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate amd64 (20100419.1) MachineType: Hewlett-Packard HP ENVY 15 Notebook PC MarkForUpload: True ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-28-generic root=UUID=639dc488-e095-42a4-8c1f-ffb1a9299e1c ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-28-generic N/A linux-backports-modules-3.5.0-28-generic N/A linux-firmware1.95.1 SourcePackage: linux UpgradeStatus: Upgraded to quantal on 2012-10-05 (187 days ago) dmi.bios.date: 10/12/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.2B dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1522 dmi.board.vendor: Hewlett-Packard dmi.board.version: 36.35 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.2B:bd10/12/2010:svnHewlett-Packard:pnHPENVY15NotebookPC:pvr048F1124192000153:rvnHewlett-Packard:rn1522:rvr36.35:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP ENVY 15 Notebook PC dmi.product.version: 048F1124192000153 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1167586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1555434] Re: Black screen/system lockup on 4.4.0-11
** Attachment added: "journalctrl when plugging in monitor" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555434/+attachment/4598800/+files/pluginfail -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1555434 Title: Black screen/system lockup on 4.4.0-11 Status in linux package in Ubuntu: Incomplete Bug description: https://lists.ubuntu.com/archives/ubuntu-devel- discuss/2016-March/016281.html references xenial freezing when plugging in a 2nd monitor on a 2015 macbook pro. I'm seeing similar freezes when _unplugging_ the 2nd monitor -- the screen turns black and everything is unresponsive. Not sure that it happens every time, but have noticed it multiple times today (first time booting with 4.4.0-11), and have not seen it before today (yesterday was booting 4.4.0-10 and the freeze did not occur). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-11-generic 4.4.0-11.26 ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 Uname: Linux 4.4.0-11-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 2270 F pulseaudio /dev/snd/controlC1: jbarnett 2270 F pulseaudio CurrentDesktop: GNOME Date: Wed Mar 9 20:31:07 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=dd225ec0-47f4-49d8-a51c-a2547f8eb945 InstallationDate: Installed on 2015-08-21 (201 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) MachineType: Apple Inc. MacBookPro11,4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-11-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-11-generic N/A linux-backports-modules-4.4.0-11-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-16 (22 days ago) dmi.bios.date: 06/05/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B04.1506051511 dmi.board.name: Mac-06F11FD93F0323C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,4 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11FD93F0323C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5: dmi.product.name: MacBookPro11,4 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1555434] Re: Black screen/system lockup on 4.4.0-11
Still seeing this on 4.4.0-12, will test the latest v4.5 kernel next. attaching journalctl from 2 tests: one unplugging the external monitor, and one plugging it in. both failed in the same apparent way -- unrecoverable black screen (although when holding the power button down, the plymouth splash showed up until the system powered off) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1555434 Title: Black screen/system lockup on 4.4.0-11 Status in linux package in Ubuntu: Incomplete Bug description: https://lists.ubuntu.com/archives/ubuntu-devel- discuss/2016-March/016281.html references xenial freezing when plugging in a 2nd monitor on a 2015 macbook pro. I'm seeing similar freezes when _unplugging_ the 2nd monitor -- the screen turns black and everything is unresponsive. Not sure that it happens every time, but have noticed it multiple times today (first time booting with 4.4.0-11), and have not seen it before today (yesterday was booting 4.4.0-10 and the freeze did not occur). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-11-generic 4.4.0-11.26 ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 Uname: Linux 4.4.0-11-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 2270 F pulseaudio /dev/snd/controlC1: jbarnett 2270 F pulseaudio CurrentDesktop: GNOME Date: Wed Mar 9 20:31:07 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=dd225ec0-47f4-49d8-a51c-a2547f8eb945 InstallationDate: Installed on 2015-08-21 (201 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) MachineType: Apple Inc. MacBookPro11,4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-11-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-11-generic N/A linux-backports-modules-4.4.0-11-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-16 (22 days ago) dmi.bios.date: 06/05/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B04.1506051511 dmi.board.name: Mac-06F11FD93F0323C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,4 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11FD93F0323C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5: dmi.product.name: MacBookPro11,4 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1555434] Re: Black screen/system lockup on 4.4.0-11
** Attachment added: "journalctrl when unplugging monitor" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555434/+attachment/4598801/+files/unplugfail -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1555434 Title: Black screen/system lockup on 4.4.0-11 Status in linux package in Ubuntu: Incomplete Bug description: https://lists.ubuntu.com/archives/ubuntu-devel- discuss/2016-March/016281.html references xenial freezing when plugging in a 2nd monitor on a 2015 macbook pro. I'm seeing similar freezes when _unplugging_ the 2nd monitor -- the screen turns black and everything is unresponsive. Not sure that it happens every time, but have noticed it multiple times today (first time booting with 4.4.0-11), and have not seen it before today (yesterday was booting 4.4.0-10 and the freeze did not occur). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-11-generic 4.4.0-11.26 ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 Uname: Linux 4.4.0-11-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 2270 F pulseaudio /dev/snd/controlC1: jbarnett 2270 F pulseaudio CurrentDesktop: GNOME Date: Wed Mar 9 20:31:07 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=dd225ec0-47f4-49d8-a51c-a2547f8eb945 InstallationDate: Installed on 2015-08-21 (201 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) MachineType: Apple Inc. MacBookPro11,4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-11-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-11-generic N/A linux-backports-modules-4.4.0-11-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-16 (22 days ago) dmi.bios.date: 06/05/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B04.1506051511 dmi.board.name: Mac-06F11FD93F0323C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,4 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11FD93F0323C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5: dmi.product.name: MacBookPro11,4 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1555434] Re: Black screen/system lockup on 4.4.0-11
** Attachment added: "journalctrl plugging in on v4.5" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555434/+attachment/4598822/+files/4.5plug -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1555434 Title: Black screen/system lockup on 4.4.0-11 Status in linux package in Ubuntu: Confirmed Bug description: https://lists.ubuntu.com/archives/ubuntu-devel- discuss/2016-March/016281.html references xenial freezing when plugging in a 2nd monitor on a 2015 macbook pro. I'm seeing similar freezes when _unplugging_ the 2nd monitor -- the screen turns black and everything is unresponsive. Not sure that it happens every time, but have noticed it multiple times today (first time booting with 4.4.0-11), and have not seen it before today (yesterday was booting 4.4.0-10 and the freeze did not occur). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-11-generic 4.4.0-11.26 ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 Uname: Linux 4.4.0-11-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 2270 F pulseaudio /dev/snd/controlC1: jbarnett 2270 F pulseaudio CurrentDesktop: GNOME Date: Wed Mar 9 20:31:07 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=dd225ec0-47f4-49d8-a51c-a2547f8eb945 InstallationDate: Installed on 2015-08-21 (201 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) MachineType: Apple Inc. MacBookPro11,4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-11-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-11-generic N/A linux-backports-modules-4.4.0-11-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-16 (22 days ago) dmi.bios.date: 06/05/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B04.1506051511 dmi.board.name: Mac-06F11FD93F0323C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,4 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11FD93F0323C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5: dmi.product.name: MacBookPro11,4 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1555434] Re: Black screen/system lockup on 4.4.0-11
Same thing on v4.5-wily, although when X died it spit me into a text login console instead of a completely unrecoverable blank screen ** Tags added: kernel-bug-exists-upstream ** 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/1555434 Title: Black screen/system lockup on 4.4.0-11 Status in linux package in Ubuntu: Confirmed Bug description: https://lists.ubuntu.com/archives/ubuntu-devel- discuss/2016-March/016281.html references xenial freezing when plugging in a 2nd monitor on a 2015 macbook pro. I'm seeing similar freezes when _unplugging_ the 2nd monitor -- the screen turns black and everything is unresponsive. Not sure that it happens every time, but have noticed it multiple times today (first time booting with 4.4.0-11), and have not seen it before today (yesterday was booting 4.4.0-10 and the freeze did not occur). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-11-generic 4.4.0-11.26 ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 Uname: Linux 4.4.0-11-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 2270 F pulseaudio /dev/snd/controlC1: jbarnett 2270 F pulseaudio CurrentDesktop: GNOME Date: Wed Mar 9 20:31:07 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=dd225ec0-47f4-49d8-a51c-a2547f8eb945 InstallationDate: Installed on 2015-08-21 (201 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) MachineType: Apple Inc. MacBookPro11,4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-11-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-11-generic N/A linux-backports-modules-4.4.0-11-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-16 (22 days ago) dmi.bios.date: 06/05/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B04.1506051511 dmi.board.name: Mac-06F11FD93F0323C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,4 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11FD93F0323C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5: dmi.product.name: MacBookPro11,4 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1555434] Re: Black screen/system lockup on 4.4.0-11
I've just tested again with 4.4.0-10-generic and 4.4.0-9-generic, and those kernels are seeing the same issue. Perhaps this is a bug in X, not the kernel? Let me know if you still want me to test 4.4.3/4.4.4. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1555434 Title: Black screen/system lockup on 4.4.0-11 Status in linux package in Ubuntu: Confirmed Bug description: https://lists.ubuntu.com/archives/ubuntu-devel- discuss/2016-March/016281.html references xenial freezing when plugging in a 2nd monitor on a 2015 macbook pro. I'm seeing similar freezes when _unplugging_ the 2nd monitor -- the screen turns black and everything is unresponsive. Not sure that it happens every time, but have noticed it multiple times today (first time booting with 4.4.0-11), and have not seen it before today (yesterday was booting 4.4.0-10 and the freeze did not occur). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-11-generic 4.4.0-11.26 ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 Uname: Linux 4.4.0-11-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 2270 F pulseaudio /dev/snd/controlC1: jbarnett 2270 F pulseaudio CurrentDesktop: GNOME Date: Wed Mar 9 20:31:07 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=dd225ec0-47f4-49d8-a51c-a2547f8eb945 InstallationDate: Installed on 2015-08-21 (201 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) MachineType: Apple Inc. MacBookPro11,4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-11-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-11-generic N/A linux-backports-modules-4.4.0-11-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-16 (22 days ago) dmi.bios.date: 06/05/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B04.1506051511 dmi.board.name: Mac-06F11FD93F0323C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,4 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11FD93F0323C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5: dmi.product.name: MacBookPro11,4 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1555434] Re: Black screen/system lockup on 4.4.0-11
Confirmed still occuring on both 4.4.3 and 4.4.4 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1555434 Title: Black screen/system lockup on 4.4.0-11 Status in linux package in Ubuntu: Confirmed Bug description: https://lists.ubuntu.com/archives/ubuntu-devel- discuss/2016-March/016281.html references xenial freezing when plugging in a 2nd monitor on a 2015 macbook pro. I'm seeing similar freezes when _unplugging_ the 2nd monitor -- the screen turns black and everything is unresponsive. Not sure that it happens every time, but have noticed it multiple times today (first time booting with 4.4.0-11), and have not seen it before today (yesterday was booting 4.4.0-10 and the freeze did not occur). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-11-generic 4.4.0-11.26 ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 Uname: Linux 4.4.0-11-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 2270 F pulseaudio /dev/snd/controlC1: jbarnett 2270 F pulseaudio CurrentDesktop: GNOME Date: Wed Mar 9 20:31:07 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=dd225ec0-47f4-49d8-a51c-a2547f8eb945 InstallationDate: Installed on 2015-08-21 (201 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) MachineType: Apple Inc. MacBookPro11,4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-11-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-11-generic N/A linux-backports-modules-4.4.0-11-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-16 (22 days ago) dmi.bios.date: 06/05/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B04.1506051511 dmi.board.name: Mac-06F11FD93F0323C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,4 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11FD93F0323C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5: dmi.product.name: MacBookPro11,4 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1555434] Re: Black screen/system lockup on 4.4.0-11
I've just downgrade xserver back to 2:1.17.3-2ubuntu4 (and the input/video drivers to compatible previous versions) and no longer see this bug on kernel 4.4.0-13-generic ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1555434 Title: Black screen/system lockup on 4.4.0-11 Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: New Bug description: https://lists.ubuntu.com/archives/ubuntu-devel- discuss/2016-March/016281.html references xenial freezing when plugging in a 2nd monitor on a 2015 macbook pro. I'm seeing similar freezes when _unplugging_ the 2nd monitor -- the screen turns black and everything is unresponsive. Not sure that it happens every time, but have noticed it multiple times today (first time booting with 4.4.0-11), and have not seen it before today (yesterday was booting 4.4.0-10 and the freeze did not occur). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-11-generic 4.4.0-11.26 ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 Uname: Linux 4.4.0-11-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 2270 F pulseaudio /dev/snd/controlC1: jbarnett 2270 F pulseaudio CurrentDesktop: GNOME Date: Wed Mar 9 20:31:07 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=dd225ec0-47f4-49d8-a51c-a2547f8eb945 InstallationDate: Installed on 2015-08-21 (201 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) MachineType: Apple Inc. MacBookPro11,4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-11-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-11-generic N/A linux-backports-modules-4.4.0-11-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-16 (22 days ago) dmi.bios.date: 06/05/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B04.1506051511 dmi.board.name: Mac-06F11FD93F0323C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,4 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11FD93F0323C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5: dmi.product.name: MacBookPro11,4 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1555434] Re: Black screen/system lockup on 4.4.0-11
1.18.2 from the x-staging ppa works, thanks Timo! ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: xorg-server (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1555434 Title: Black screen/system lockup on 4.4.0-11 Status in linux package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Fix Committed Bug description: https://lists.ubuntu.com/archives/ubuntu-devel- discuss/2016-March/016281.html references xenial freezing when plugging in a 2nd monitor on a 2015 macbook pro. I'm seeing similar freezes when _unplugging_ the 2nd monitor -- the screen turns black and everything is unresponsive. Not sure that it happens every time, but have noticed it multiple times today (first time booting with 4.4.0-11), and have not seen it before today (yesterday was booting 4.4.0-10 and the freeze did not occur). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-11-generic 4.4.0-11.26 ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 Uname: Linux 4.4.0-11-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 2270 F pulseaudio /dev/snd/controlC1: jbarnett 2270 F pulseaudio CurrentDesktop: GNOME Date: Wed Mar 9 20:31:07 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=dd225ec0-47f4-49d8-a51c-a2547f8eb945 InstallationDate: Installed on 2015-08-21 (201 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) MachineType: Apple Inc. MacBookPro11,4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-11-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-11-generic N/A linux-backports-modules-4.4.0-11-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-16 (22 days ago) dmi.bios.date: 06/05/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B04.1506051511 dmi.board.name: Mac-06F11FD93F0323C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,4 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11FD93F0323C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5: dmi.product.name: MacBookPro11,4 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1555434] [NEW] Black screen/system lockup on 4.4.0-11
Public bug reported: https://lists.ubuntu.com/archives/ubuntu-devel- discuss/2016-March/016281.html references xenial freezing when plugging in a 2nd monitor on a 2015 macbook pro. I'm seeing similar freezes when _unplugging_ the 2nd monitor -- the screen turns black and everything is unresponsive. Not sure that it happens every time, but have noticed it multiple times today (first time booting with 4.4.0-11), and have not seen it before today (yesterday was booting 4.4.0-10 and the freeze did not occur). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-11-generic 4.4.0-11.26 ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 Uname: Linux 4.4.0-11-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 2270 F pulseaudio /dev/snd/controlC1: jbarnett 2270 F pulseaudio CurrentDesktop: GNOME Date: Wed Mar 9 20:31:07 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=dd225ec0-47f4-49d8-a51c-a2547f8eb945 InstallationDate: Installed on 2015-08-21 (201 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) MachineType: Apple Inc. MacBookPro11,4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-11-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-11-generic N/A linux-backports-modules-4.4.0-11-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-16 (22 days ago) dmi.bios.date: 06/05/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B04.1506051511 dmi.board.name: Mac-06F11FD93F0323C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,4 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11FD93F0323C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5: dmi.product.name: MacBookPro11,4 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1555434 Title: Black screen/system lockup on 4.4.0-11 Status in linux package in Ubuntu: New Bug description: https://lists.ubuntu.com/archives/ubuntu-devel- discuss/2016-March/016281.html references xenial freezing when plugging in a 2nd monitor on a 2015 macbook pro. I'm seeing similar freezes when _unplugging_ the 2nd monitor -- the screen turns black and everything is unresponsive. Not sure that it happens every time, but have noticed it multiple times today (first time booting with 4.4.0-11), and have not seen it before today (yesterday was booting 4.4.0-10 and the freeze did not occur). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-11-generic 4.4.0-11.26 ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 Uname: Linux 4.4.0-11-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 2270 F pulseaudio /dev/snd/controlC1: jbarnett 2270 F pulseaudio CurrentDesktop: GNOME Date: Wed Mar 9 20:31:07 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=dd225ec0-47f4-49d8-a51c-a2547f8eb945 InstallationDate: Installed on 2015-08-21 (201 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) MachineType: Apple Inc. MacBookPro11,4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-11-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-11-generic N/A linux-backports-modules-4.4.0-11-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-16 (22 days ago) dmi.bios.date: 06/05/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B04.1506051511 dmi.board.name: Mac-06F11FD93F0323C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,4 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11FD93F0323C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvr
[Kernel-packages] [Bug 1546603] [NEW] Bluetooth mouse connects but doesn't work
Public bug reported: I have a bluetooth mouse that I can get to connect via the gnome bluetooth settings panel, but even after it's connected it doesn't move the pointer or register any clicks. the following shows up in the journal : $ $ journalctl -b 0 |grep bluetooth Feb 17 07:18:22 spiny bluetoothd[1009]: Bluetooth daemon 5.36 Feb 17 07:18:22 spiny bluetoothd[1009]: Starting SDP server Feb 17 07:18:22 spiny bluetoothd[1009]: Bluetooth management interface 1.10 initialized Feb 17 07:18:22 spiny bluetoothd[1009]: Failed to obtain handles for "Service Changed" characteristic Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register service Feb 17 07:18:22 spiny bluetoothd[1009]: Error adding Link Loss service Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register service Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register service Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register service Feb 17 07:18:22 spiny bluetoothd[1009]: Current Time Service could not be registered Feb 17 07:18:22 spiny bluetoothd[1009]: gatt-time-server: Input/output error (5) Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register service Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register service Feb 17 07:18:22 spiny bluetoothd[1009]: Sap driver initialization failed. Feb 17 07:18:22 spiny bluetoothd[1009]: sap-server: Operation not permitted (1) Feb 17 07:18:22 spiny NetworkManager[1062]: Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so) Feb 17 07:18:24 spiny bluetoothd[1009]: Endpoint registered: sender=:1.42 path=/MediaEndpoint/A2DPSource Feb 17 07:18:24 spiny bluetoothd[1009]: Endpoint registered: sender=:1.42 path=/MediaEndpoint/A2DPSink Feb 17 07:18:42 spiny bluetoothd[1009]: Endpoint registered: sender=:1.71 path=/MediaEndpoint/A2DPSource Feb 17 07:18:42 spiny bluetoothd[1009]: Endpoint registered: sender=:1.71 path=/MediaEndpoint/A2DPSink Feb 17 07:18:42 spiny bluetoothd[1009]: RFCOMM server failed for Headset Voice gateway: rfcomm_bind: Address already in use (98) Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** (gnome-control-center.real:2717): WARNING **: Ignoring launcher gufw (missing desktop file) Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** (gnome-control-center.real:2717): WARNING **: Ignoring launcher landscape-client-settings (missing desktop file) Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** (gnome-control-center.real:2717): WARNING **: Ignoring launcher language-selector (missing desktop file) Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** (gnome-control-center.real:2717): WARNING **: Ignoring launcher ubuntuone-installer (missing desktop file) Feb 17 07:19:00 spiny gnome-bluetooth-panel.desktop[2717]: (gnome-control-center.real:2717): GLib-CRITICAL **: g_ascii_strdown: assertion 'str != NULL' failed Feb 17 07:19:01 spiny bluetoothd[1009]: No cache for F2:3F:5C:A1:F9:F7 Feb 17 07:19:06 spiny bluetoothd[1009]: Unable to register GATT service with handle 0x000c for device F2:3F:5C:A1:F9:F7 Feb 17 07:19:06 spiny bluetoothd[1009]: Unable to register GATT service with handle 0x001b for device F2:3F:5C:A1:F9:F7 Feb 17 07:19:06 spiny bluetoothd[1009]: Unable to register GATT service with handle 0x003f for device F2:3F:5C:A1:F9:F7 Feb 17 07:19:06 spiny bluetoothd[1009]: Report Map read failed: Attribute requires authentication before read/write Feb 17 07:19:06 spiny bluetoothd[1009]: Protocol Mode characteristic read failed: Attribute requires authentication before read/write Feb 17 07:19:06 spiny bluetoothd[1009]: HID Information read failed: Attribute requires authentication before read/write Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor failed: Attribute requires authentication before read/write Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor failed: Attribute requires authentication before read/write Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor failed: Attribute requires authentication before read/write Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor failed: Attribute requires authentication before read/write Feb 17 07:19:08 spiny gnome-bluetooth-panel.desktop[2717]: (gnome-control-center.real:2717): GLib-CRITICAL **: g_ascii_strdown: assertion 'str != NULL' failed Feb 17 07:19:08 spiny gnome-bluetooth-panel.desktop[2717]: (gnome-control-center.real:2717): Bluetooth-WARNING **: Setting up /org/bluez/hci0/dev_F2_3F_5C_A1_F9_F7 failed: GDBus.Error:org.bluez.Error.InProgress: In Progress Feb 17 07:19:08 spiny gnome-bluetooth-panel.desktop[2717]: (gnome-control-center.real:2717): GLib-CRITICAL **: g_ascii_strdown: assertion 'str != NULL' failed Feb 17 07:19:08 spiny gnome-bluetooth-panel.desktop[2717]: (gnome-contr
[Kernel-packages] [Bug 1587714] [NEW] MacBookPro11, 4 fails to poweroff or suspend
Public bug reported: Since the release of the 2015 MacBookPro11,4 (15" retina), it has been unable to suspend or poweroff on linux. Recently, https://bugzilla.kernel.org/show_bug.cgi?id=103211 has received a patch that works to fix these issues. The patch is in comment #172, and is also attached to this bugreport, and reported to work very well by users of other distributions. In addition, I can confirm that building the latest xenial 4.4.0-22-generic kernel with this patch applied fixes the issue. Can this be added to the official xenial kernel? Thanks! ** Affects: linux Importance: Unknown Status: Unknown ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Patch added: "macbookpro114suspend.patch" https://bugs.launchpad.net/bugs/1587714/+attachment/4674007/+files/macbookpro114suspend.patch ** Bug watch added: Linux Kernel Bug Tracker #103211 http://bugzilla.kernel.org/show_bug.cgi?id=103211 ** Also affects: linux via http://bugzilla.kernel.org/show_bug.cgi?id=103211 Importance: Unknown Status: Unknown ** Description changed: Since the release of the 2015 MacBookPro11,4 (15" retina), it has been unable to suspend or poweroff on linux. Recently, https://bugzilla.kernel.org/show_bug.cgi?id=103211 has received a patch that works to fix these issues. The patch is in comment #172, and is also attached to this bugreport, and reported to work very well by users of other distributions. In addition, I can confirm that building the latest xenial 4.4.0-22-generic kernel with this patch applied fixes the - issue. Can this be added to the xenial kernel? + issue. Can this be added to the official xenial kernel? 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/1587714 Title: MacBookPro11,4 fails to poweroff or suspend Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: Since the release of the 2015 MacBookPro11,4 (15" retina), it has been unable to suspend or poweroff on linux. Recently, https://bugzilla.kernel.org/show_bug.cgi?id=103211 has received a patch that works to fix these issues. The patch is in comment #172, and is also attached to this bugreport, and reported to work very well by users of other distributions. In addition, I can confirm that building the latest xenial 4.4.0-22-generic kernel with this patch applied fixes the issue. Can this be added to the official xenial kernel? Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1587714/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1497321] Re: thunderbolt ethernet adapter not hotpluggable on MacbookPro12, 1
still the same problem in 4.3-rc2 but looks like it will make it in 4.3-rc3 as per http://git.kernel.org/cgit/linux/kernel/git/gregkh/char- misc.git/commit/?h=char-misc- linus&id=a42fb351ca1f340f8307468be765e3f77ddedda9 from http://git.kernel.org/cgit/linux/kernel/git/gregkh/char-misc.git/log/?h =char-misc-linus -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1497321 Title: thunderbolt ethernet adapter not hotpluggable on MacbookPro12,1 Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: It works if plugged in while booted, but not after removing / replugging, or if plugging in after booted. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-10-generic 4.2.0-10.11 ProcVersionSignature: Ubuntu 4.2.0-10.11-generic 4.2.0 Uname: Linux 4.2.0-10-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Sep 18 07:49:45 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=dd225ec0-47f4-49d8-a51c-a2547f8eb945 InstallationDate: Installed on 2015-08-21 (28 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) MachineType: Apple Inc. MacBookPro11,4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-10-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-10-generic N/A linux-backports-modules-4.2.0-10-generic N/A linux-firmware1.147 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B04.1506051511 dmi.board.name: Mac-06F11FD93F0323C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,4 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11FD93F0323C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5: dmi.product.name: MacBookPro11,4 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1497321/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1487919] Re: macbookrpro12, 1 fails to suspend
attaching wakeup as per https://wiki.ubuntu.com/DebuggingKernelSuspend ** Attachment added: "wakeup" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1487919/+attachment/4501268/+files/wakeup -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1487919 Title: macbookrpro12,1 fails to suspend Status in linux package in Ubuntu: Confirmed Bug description: I've installed wily on a new macbookpro12,1 (2015 model), and suspending the system results in the screen going black and the apple light turning off, but the system is not fully asleep -- the 'force touch' pad still makes clicking feedback, and the machine continues to generate heat and spin fans if put into a bag. Once in this state, the machine cannot be woken up from the state its in either. did a "journalctl -f | tee sleep.log' while this was happening and got the following output -- let me know if there is a better way to figure out where things are going wrong: Aug 23 15:13:21 spiny NetworkManager[820]: sleep requested (sleeping: no enabled: yes) Aug 23 15:13:21 spiny NetworkManager[820]: sleeping... Aug 23 15:13:21 spiny NetworkManager[820]: (wlp3s0): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37] Aug 23 15:13:21 spiny NetworkManager[820]: (wlp3s0): deactivating device (reason 'sleeping') [37] Aug 23 15:13:21 spiny NetworkManager[820]: (wlp3s0): canceled DHCP transaction, DHCP client pid 925 Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for 2601:1c0:4d00:39e6:f912:fbb6:aaa6:4429 on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for 2601:1c0:4d00:39e6:290:4cff:fe0d:f43e on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Leaving mDNS multicast group on interface wlp3s0.IPv6 with address 2601:1c0:4d00:39e6:290:4cff:fe0d:f43e. Aug 23 15:13:21 spiny avahi-daemon[826]: Joining mDNS multicast group on interface wlp3s0.IPv6 with address fe80::290:4cff:fe0d:f43e. Aug 23 15:13:21 spiny avahi-daemon[826]: Registering new address record for fe80::290:4cff:fe0d:f43e on wlp3s0.*. Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for fe80::290:4cff:fe0d:f43e on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Leaving mDNS multicast group on interface wlp3s0.IPv6 with address fe80::290:4cff:fe0d:f43e. Aug 23 15:13:21 spiny avahi-daemon[826]: Interface wlp3s0.IPv6 no longer relevant for mDNS. Aug 23 15:13:21 spiny wpa_supplicant[891]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=10:c3:7b:c5:83:d8 reason=3 locally_generated=1 Aug 23 15:13:21 spiny wpa_supplicant[891]: nl80211: Was expecting local disconnect but got another disconnect event first Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for 192.168.1.83 on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Leaving mDNS multicast group on interface wlp3s0.IPv4 with address 192.168.1.83. Aug 23 15:13:21 spiny avahi-daemon[826]: Interface wlp3s0.IPv4 no longer relevant for mDNS. Aug 23 15:13:21 spiny kernel: cfg80211: Calling CRDA to update world regulatory domain Aug 23 15:13:21 spiny NetworkManager[820]: Writing DNS information to /sbin/resolvconf Aug 23 15:13:21 spiny dnsmasq[928]: setting upstream servers from DBus Aug 23 15:13:21 spiny dnsmasq[928]: using nameserver 2601:1c0:4d00:39e6::1#53 Aug 23 15:13:21 spiny dbus[806]: [system] Rejected send message, 10 matched rules; type="method_return", sender=":1.22" (uid=0 pid=928 comm="/usr/sbin/dnsmasq --no-resolv --keep-in-foreground") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.6" (uid=0 pid=820 comm="/usr/sbin/NetworkManager --no-daemon ") Aug 23 15:13:21 spiny wpa_supplicant[891]: p2p-dev-wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Aug 23 15:13:21 spiny NetworkManager[820]: Writing DNS information to /sbin/resolvconf Aug 23 15:13:21 spiny kernel: brcmf_cfg80211_reg_notifier: not a ISO3166 code Aug 23 15:13:21 spiny kernel: cfg80211: World regulatory domain updated: Aug 23 15:13:21 spiny kernel: cfg80211: DFS Master region: unset Aug 23 15:13:21 spiny kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) Aug 23 15:13:21 spiny kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (517 KHz - 525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (525 KHz - 533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s) Aug 23 15:13:21 spiny kernel: cfg80211: (54
[Kernel-packages] [Bug 1487919] Re: macbookrpro12, 1 fails to suspend
[2.086936] evm: HMAC attrs: 0x1 [2.087564] Magic number: 0:832:178 [2.087566] hash matches /build/linux-AxjFAn/linux-4.2.0/drivers/base/power/main.c:1065 [2.087618] acpi device:0e: hash matches [2.087634] platform: hash matches ^--- the part of dmesg referenced in https://wiki.ubuntu.com/DebuggingKernelSuspend i had rmmod'ed brcmfmac, then suspended via sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend" ** 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/1487919 Title: macbookrpro12,1 fails to suspend Status in linux package in Ubuntu: Confirmed Bug description: I've installed wily on a new macbookpro12,1 (2015 model), and suspending the system results in the screen going black and the apple light turning off, but the system is not fully asleep -- the 'force touch' pad still makes clicking feedback, and the machine continues to generate heat and spin fans if put into a bag. Once in this state, the machine cannot be woken up from the state its in either. did a "journalctl -f | tee sleep.log' while this was happening and got the following output -- let me know if there is a better way to figure out where things are going wrong: Aug 23 15:13:21 spiny NetworkManager[820]: sleep requested (sleeping: no enabled: yes) Aug 23 15:13:21 spiny NetworkManager[820]: sleeping... Aug 23 15:13:21 spiny NetworkManager[820]: (wlp3s0): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37] Aug 23 15:13:21 spiny NetworkManager[820]: (wlp3s0): deactivating device (reason 'sleeping') [37] Aug 23 15:13:21 spiny NetworkManager[820]: (wlp3s0): canceled DHCP transaction, DHCP client pid 925 Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for 2601:1c0:4d00:39e6:f912:fbb6:aaa6:4429 on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for 2601:1c0:4d00:39e6:290:4cff:fe0d:f43e on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Leaving mDNS multicast group on interface wlp3s0.IPv6 with address 2601:1c0:4d00:39e6:290:4cff:fe0d:f43e. Aug 23 15:13:21 spiny avahi-daemon[826]: Joining mDNS multicast group on interface wlp3s0.IPv6 with address fe80::290:4cff:fe0d:f43e. Aug 23 15:13:21 spiny avahi-daemon[826]: Registering new address record for fe80::290:4cff:fe0d:f43e on wlp3s0.*. Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for fe80::290:4cff:fe0d:f43e on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Leaving mDNS multicast group on interface wlp3s0.IPv6 with address fe80::290:4cff:fe0d:f43e. Aug 23 15:13:21 spiny avahi-daemon[826]: Interface wlp3s0.IPv6 no longer relevant for mDNS. Aug 23 15:13:21 spiny wpa_supplicant[891]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=10:c3:7b:c5:83:d8 reason=3 locally_generated=1 Aug 23 15:13:21 spiny wpa_supplicant[891]: nl80211: Was expecting local disconnect but got another disconnect event first Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for 192.168.1.83 on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Leaving mDNS multicast group on interface wlp3s0.IPv4 with address 192.168.1.83. Aug 23 15:13:21 spiny avahi-daemon[826]: Interface wlp3s0.IPv4 no longer relevant for mDNS. Aug 23 15:13:21 spiny kernel: cfg80211: Calling CRDA to update world regulatory domain Aug 23 15:13:21 spiny NetworkManager[820]: Writing DNS information to /sbin/resolvconf Aug 23 15:13:21 spiny dnsmasq[928]: setting upstream servers from DBus Aug 23 15:13:21 spiny dnsmasq[928]: using nameserver 2601:1c0:4d00:39e6::1#53 Aug 23 15:13:21 spiny dbus[806]: [system] Rejected send message, 10 matched rules; type="method_return", sender=":1.22" (uid=0 pid=928 comm="/usr/sbin/dnsmasq --no-resolv --keep-in-foreground") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.6" (uid=0 pid=820 comm="/usr/sbin/NetworkManager --no-daemon ") Aug 23 15:13:21 spiny wpa_supplicant[891]: p2p-dev-wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Aug 23 15:13:21 spiny NetworkManager[820]: Writing DNS information to /sbin/resolvconf Aug 23 15:13:21 spiny kernel: brcmf_cfg80211_reg_notifier: not a ISO3166 code Aug 23 15:13:21 spiny kernel: cfg80211: World regulatory domain updated: Aug 23 15:13:21 spiny kernel: cfg80211: DFS Master region: unset Aug 23 15:13:21 spiny kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) Aug 23 15:13:21 spiny kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (N
[Kernel-packages] [Bug 1487919] Re: macbookrpro12, 1 fails to suspend
attaching dmesg as per https://wiki.ubuntu.com/DebuggingKernelSuspend ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1487919/+attachment/4501267/+files/dmesg.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/1487919 Title: macbookrpro12,1 fails to suspend Status in linux package in Ubuntu: Confirmed Bug description: I've installed wily on a new macbookpro12,1 (2015 model), and suspending the system results in the screen going black and the apple light turning off, but the system is not fully asleep -- the 'force touch' pad still makes clicking feedback, and the machine continues to generate heat and spin fans if put into a bag. Once in this state, the machine cannot be woken up from the state its in either. did a "journalctl -f | tee sleep.log' while this was happening and got the following output -- let me know if there is a better way to figure out where things are going wrong: Aug 23 15:13:21 spiny NetworkManager[820]: sleep requested (sleeping: no enabled: yes) Aug 23 15:13:21 spiny NetworkManager[820]: sleeping... Aug 23 15:13:21 spiny NetworkManager[820]: (wlp3s0): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37] Aug 23 15:13:21 spiny NetworkManager[820]: (wlp3s0): deactivating device (reason 'sleeping') [37] Aug 23 15:13:21 spiny NetworkManager[820]: (wlp3s0): canceled DHCP transaction, DHCP client pid 925 Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for 2601:1c0:4d00:39e6:f912:fbb6:aaa6:4429 on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for 2601:1c0:4d00:39e6:290:4cff:fe0d:f43e on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Leaving mDNS multicast group on interface wlp3s0.IPv6 with address 2601:1c0:4d00:39e6:290:4cff:fe0d:f43e. Aug 23 15:13:21 spiny avahi-daemon[826]: Joining mDNS multicast group on interface wlp3s0.IPv6 with address fe80::290:4cff:fe0d:f43e. Aug 23 15:13:21 spiny avahi-daemon[826]: Registering new address record for fe80::290:4cff:fe0d:f43e on wlp3s0.*. Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for fe80::290:4cff:fe0d:f43e on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Leaving mDNS multicast group on interface wlp3s0.IPv6 with address fe80::290:4cff:fe0d:f43e. Aug 23 15:13:21 spiny avahi-daemon[826]: Interface wlp3s0.IPv6 no longer relevant for mDNS. Aug 23 15:13:21 spiny wpa_supplicant[891]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=10:c3:7b:c5:83:d8 reason=3 locally_generated=1 Aug 23 15:13:21 spiny wpa_supplicant[891]: nl80211: Was expecting local disconnect but got another disconnect event first Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for 192.168.1.83 on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Leaving mDNS multicast group on interface wlp3s0.IPv4 with address 192.168.1.83. Aug 23 15:13:21 spiny avahi-daemon[826]: Interface wlp3s0.IPv4 no longer relevant for mDNS. Aug 23 15:13:21 spiny kernel: cfg80211: Calling CRDA to update world regulatory domain Aug 23 15:13:21 spiny NetworkManager[820]: Writing DNS information to /sbin/resolvconf Aug 23 15:13:21 spiny dnsmasq[928]: setting upstream servers from DBus Aug 23 15:13:21 spiny dnsmasq[928]: using nameserver 2601:1c0:4d00:39e6::1#53 Aug 23 15:13:21 spiny dbus[806]: [system] Rejected send message, 10 matched rules; type="method_return", sender=":1.22" (uid=0 pid=928 comm="/usr/sbin/dnsmasq --no-resolv --keep-in-foreground") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.6" (uid=0 pid=820 comm="/usr/sbin/NetworkManager --no-daemon ") Aug 23 15:13:21 spiny wpa_supplicant[891]: p2p-dev-wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Aug 23 15:13:21 spiny NetworkManager[820]: Writing DNS information to /sbin/resolvconf Aug 23 15:13:21 spiny kernel: brcmf_cfg80211_reg_notifier: not a ISO3166 code Aug 23 15:13:21 spiny kernel: cfg80211: World regulatory domain updated: Aug 23 15:13:21 spiny kernel: cfg80211: DFS Master region: unset Aug 23 15:13:21 spiny kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) Aug 23 15:13:21 spiny kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (517 KHz - 525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (525 KHz - 533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s) Aug 23 15:13:21 spiny kernel: cfg80211:
[Kernel-packages] [Bug 1487919] Re: macbookrpro12, 1 fails to suspend
same thing on latest mainline kernel, hope this is helpful. ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1487919/+attachment/4501841/+files/dmesg.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/1487919 Title: macbookrpro12,1 fails to suspend Status in linux package in Ubuntu: Confirmed Bug description: I've installed wily on a new macbookpro12,1 (2015 model), and suspending the system results in the screen going black and the apple light turning off, but the system is not fully asleep -- the 'force touch' pad still makes clicking feedback, and the machine continues to generate heat and spin fans if put into a bag. Once in this state, the machine cannot be woken up from the state its in either. did a "journalctl -f | tee sleep.log' while this was happening and got the following output -- let me know if there is a better way to figure out where things are going wrong: Aug 23 15:13:21 spiny NetworkManager[820]: sleep requested (sleeping: no enabled: yes) Aug 23 15:13:21 spiny NetworkManager[820]: sleeping... Aug 23 15:13:21 spiny NetworkManager[820]: (wlp3s0): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37] Aug 23 15:13:21 spiny NetworkManager[820]: (wlp3s0): deactivating device (reason 'sleeping') [37] Aug 23 15:13:21 spiny NetworkManager[820]: (wlp3s0): canceled DHCP transaction, DHCP client pid 925 Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for 2601:1c0:4d00:39e6:f912:fbb6:aaa6:4429 on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for 2601:1c0:4d00:39e6:290:4cff:fe0d:f43e on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Leaving mDNS multicast group on interface wlp3s0.IPv6 with address 2601:1c0:4d00:39e6:290:4cff:fe0d:f43e. Aug 23 15:13:21 spiny avahi-daemon[826]: Joining mDNS multicast group on interface wlp3s0.IPv6 with address fe80::290:4cff:fe0d:f43e. Aug 23 15:13:21 spiny avahi-daemon[826]: Registering new address record for fe80::290:4cff:fe0d:f43e on wlp3s0.*. Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for fe80::290:4cff:fe0d:f43e on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Leaving mDNS multicast group on interface wlp3s0.IPv6 with address fe80::290:4cff:fe0d:f43e. Aug 23 15:13:21 spiny avahi-daemon[826]: Interface wlp3s0.IPv6 no longer relevant for mDNS. Aug 23 15:13:21 spiny wpa_supplicant[891]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=10:c3:7b:c5:83:d8 reason=3 locally_generated=1 Aug 23 15:13:21 spiny wpa_supplicant[891]: nl80211: Was expecting local disconnect but got another disconnect event first Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for 192.168.1.83 on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Leaving mDNS multicast group on interface wlp3s0.IPv4 with address 192.168.1.83. Aug 23 15:13:21 spiny avahi-daemon[826]: Interface wlp3s0.IPv4 no longer relevant for mDNS. Aug 23 15:13:21 spiny kernel: cfg80211: Calling CRDA to update world regulatory domain Aug 23 15:13:21 spiny NetworkManager[820]: Writing DNS information to /sbin/resolvconf Aug 23 15:13:21 spiny dnsmasq[928]: setting upstream servers from DBus Aug 23 15:13:21 spiny dnsmasq[928]: using nameserver 2601:1c0:4d00:39e6::1#53 Aug 23 15:13:21 spiny dbus[806]: [system] Rejected send message, 10 matched rules; type="method_return", sender=":1.22" (uid=0 pid=928 comm="/usr/sbin/dnsmasq --no-resolv --keep-in-foreground") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.6" (uid=0 pid=820 comm="/usr/sbin/NetworkManager --no-daemon ") Aug 23 15:13:21 spiny wpa_supplicant[891]: p2p-dev-wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Aug 23 15:13:21 spiny NetworkManager[820]: Writing DNS information to /sbin/resolvconf Aug 23 15:13:21 spiny kernel: brcmf_cfg80211_reg_notifier: not a ISO3166 code Aug 23 15:13:21 spiny kernel: cfg80211: World regulatory domain updated: Aug 23 15:13:21 spiny kernel: cfg80211: DFS Master region: unset Aug 23 15:13:21 spiny kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) Aug 23 15:13:21 spiny kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (517 KHz - 525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (525 KHz - 533 KHz @ 8 KHz, 16 KHz AUTO), (N/A,
[Kernel-packages] [Bug 1487919] Re: macbookrpro12, 1 fails to suspend
there are not ** 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/1487919 Title: macbookrpro12,1 fails to suspend Status in linux package in Ubuntu: Confirmed Bug description: I've installed wily on a new macbookpro12,1 (2015 model), and suspending the system results in the screen going black and the apple light turning off, but the system is not fully asleep -- the 'force touch' pad still makes clicking feedback, and the machine continues to generate heat and spin fans if put into a bag. Once in this state, the machine cannot be woken up from the state its in either. did a "journalctl -f | tee sleep.log' while this was happening and got the following output -- let me know if there is a better way to figure out where things are going wrong: Aug 23 15:13:21 spiny NetworkManager[820]: sleep requested (sleeping: no enabled: yes) Aug 23 15:13:21 spiny NetworkManager[820]: sleeping... Aug 23 15:13:21 spiny NetworkManager[820]: (wlp3s0): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37] Aug 23 15:13:21 spiny NetworkManager[820]: (wlp3s0): deactivating device (reason 'sleeping') [37] Aug 23 15:13:21 spiny NetworkManager[820]: (wlp3s0): canceled DHCP transaction, DHCP client pid 925 Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for 2601:1c0:4d00:39e6:f912:fbb6:aaa6:4429 on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for 2601:1c0:4d00:39e6:290:4cff:fe0d:f43e on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Leaving mDNS multicast group on interface wlp3s0.IPv6 with address 2601:1c0:4d00:39e6:290:4cff:fe0d:f43e. Aug 23 15:13:21 spiny avahi-daemon[826]: Joining mDNS multicast group on interface wlp3s0.IPv6 with address fe80::290:4cff:fe0d:f43e. Aug 23 15:13:21 spiny avahi-daemon[826]: Registering new address record for fe80::290:4cff:fe0d:f43e on wlp3s0.*. Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for fe80::290:4cff:fe0d:f43e on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Leaving mDNS multicast group on interface wlp3s0.IPv6 with address fe80::290:4cff:fe0d:f43e. Aug 23 15:13:21 spiny avahi-daemon[826]: Interface wlp3s0.IPv6 no longer relevant for mDNS. Aug 23 15:13:21 spiny wpa_supplicant[891]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=10:c3:7b:c5:83:d8 reason=3 locally_generated=1 Aug 23 15:13:21 spiny wpa_supplicant[891]: nl80211: Was expecting local disconnect but got another disconnect event first Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for 192.168.1.83 on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Leaving mDNS multicast group on interface wlp3s0.IPv4 with address 192.168.1.83. Aug 23 15:13:21 spiny avahi-daemon[826]: Interface wlp3s0.IPv4 no longer relevant for mDNS. Aug 23 15:13:21 spiny kernel: cfg80211: Calling CRDA to update world regulatory domain Aug 23 15:13:21 spiny NetworkManager[820]: Writing DNS information to /sbin/resolvconf Aug 23 15:13:21 spiny dnsmasq[928]: setting upstream servers from DBus Aug 23 15:13:21 spiny dnsmasq[928]: using nameserver 2601:1c0:4d00:39e6::1#53 Aug 23 15:13:21 spiny dbus[806]: [system] Rejected send message, 10 matched rules; type="method_return", sender=":1.22" (uid=0 pid=928 comm="/usr/sbin/dnsmasq --no-resolv --keep-in-foreground") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.6" (uid=0 pid=820 comm="/usr/sbin/NetworkManager --no-daemon ") Aug 23 15:13:21 spiny wpa_supplicant[891]: p2p-dev-wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Aug 23 15:13:21 spiny NetworkManager[820]: Writing DNS information to /sbin/resolvconf Aug 23 15:13:21 spiny kernel: brcmf_cfg80211_reg_notifier: not a ISO3166 code Aug 23 15:13:21 spiny kernel: cfg80211: World regulatory domain updated: Aug 23 15:13:21 spiny kernel: cfg80211: DFS Master region: unset Aug 23 15:13:21 spiny kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) Aug 23 15:13:21 spiny kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (517 KHz - 525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (525 KHz - 533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s) Aug 23 15:13:21 spiny kernel: cfg80211: (549 KHz - 573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s) Aug 23 15:13:21 spiny kernel: cfg80211: (5735000 K
[Kernel-packages] [Bug 1487919] Re: macbookrpro12, 1 fails to suspend
there are not -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1487919 Title: macbookrpro12,1 fails to suspend Status in linux package in Ubuntu: Confirmed Bug description: I've installed wily on a new macbookpro12,1 (2015 model), and suspending the system results in the screen going black and the apple light turning off, but the system is not fully asleep -- the 'force touch' pad still makes clicking feedback, and the machine continues to generate heat and spin fans if put into a bag. Once in this state, the machine cannot be woken up from the state its in either. did a "journalctl -f | tee sleep.log' while this was happening and got the following output -- let me know if there is a better way to figure out where things are going wrong: Aug 23 15:13:21 spiny NetworkManager[820]: sleep requested (sleeping: no enabled: yes) Aug 23 15:13:21 spiny NetworkManager[820]: sleeping... Aug 23 15:13:21 spiny NetworkManager[820]: (wlp3s0): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37] Aug 23 15:13:21 spiny NetworkManager[820]: (wlp3s0): deactivating device (reason 'sleeping') [37] Aug 23 15:13:21 spiny NetworkManager[820]: (wlp3s0): canceled DHCP transaction, DHCP client pid 925 Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for 2601:1c0:4d00:39e6:f912:fbb6:aaa6:4429 on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for 2601:1c0:4d00:39e6:290:4cff:fe0d:f43e on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Leaving mDNS multicast group on interface wlp3s0.IPv6 with address 2601:1c0:4d00:39e6:290:4cff:fe0d:f43e. Aug 23 15:13:21 spiny avahi-daemon[826]: Joining mDNS multicast group on interface wlp3s0.IPv6 with address fe80::290:4cff:fe0d:f43e. Aug 23 15:13:21 spiny avahi-daemon[826]: Registering new address record for fe80::290:4cff:fe0d:f43e on wlp3s0.*. Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for fe80::290:4cff:fe0d:f43e on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Leaving mDNS multicast group on interface wlp3s0.IPv6 with address fe80::290:4cff:fe0d:f43e. Aug 23 15:13:21 spiny avahi-daemon[826]: Interface wlp3s0.IPv6 no longer relevant for mDNS. Aug 23 15:13:21 spiny wpa_supplicant[891]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=10:c3:7b:c5:83:d8 reason=3 locally_generated=1 Aug 23 15:13:21 spiny wpa_supplicant[891]: nl80211: Was expecting local disconnect but got another disconnect event first Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for 192.168.1.83 on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Leaving mDNS multicast group on interface wlp3s0.IPv4 with address 192.168.1.83. Aug 23 15:13:21 spiny avahi-daemon[826]: Interface wlp3s0.IPv4 no longer relevant for mDNS. Aug 23 15:13:21 spiny kernel: cfg80211: Calling CRDA to update world regulatory domain Aug 23 15:13:21 spiny NetworkManager[820]: Writing DNS information to /sbin/resolvconf Aug 23 15:13:21 spiny dnsmasq[928]: setting upstream servers from DBus Aug 23 15:13:21 spiny dnsmasq[928]: using nameserver 2601:1c0:4d00:39e6::1#53 Aug 23 15:13:21 spiny dbus[806]: [system] Rejected send message, 10 matched rules; type="method_return", sender=":1.22" (uid=0 pid=928 comm="/usr/sbin/dnsmasq --no-resolv --keep-in-foreground") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.6" (uid=0 pid=820 comm="/usr/sbin/NetworkManager --no-daemon ") Aug 23 15:13:21 spiny wpa_supplicant[891]: p2p-dev-wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Aug 23 15:13:21 spiny NetworkManager[820]: Writing DNS information to /sbin/resolvconf Aug 23 15:13:21 spiny kernel: brcmf_cfg80211_reg_notifier: not a ISO3166 code Aug 23 15:13:21 spiny kernel: cfg80211: World regulatory domain updated: Aug 23 15:13:21 spiny kernel: cfg80211: DFS Master region: unset Aug 23 15:13:21 spiny kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) Aug 23 15:13:21 spiny kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (517 KHz - 525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (525 KHz - 533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s) Aug 23 15:13:21 spiny kernel: cfg80211: (549 KHz - 573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s) Aug 23 15:13:21 spiny kernel: cfg80211: (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A) Aug 23 15:13:
[Kernel-packages] [Bug 1487919] Re: macbookrpro12, 1 fails to suspend
sudo wpa_cli suspend before suspend still leaves me unable to resume. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1487919 Title: macbookrpro12,1 fails to suspend Status in linux package in Ubuntu: Confirmed Bug description: I've installed wily on a new macbookpro12,1 (2015 model), and suspending the system results in the screen going black and the apple light turning off, but the system is not fully asleep -- the 'force touch' pad still makes clicking feedback, and the machine continues to generate heat and spin fans if put into a bag. Once in this state, the machine cannot be woken up from the state its in either. did a "journalctl -f | tee sleep.log' while this was happening and got the following output -- let me know if there is a better way to figure out where things are going wrong: Aug 23 15:13:21 spiny NetworkManager[820]: sleep requested (sleeping: no enabled: yes) Aug 23 15:13:21 spiny NetworkManager[820]: sleeping... Aug 23 15:13:21 spiny NetworkManager[820]: (wlp3s0): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37] Aug 23 15:13:21 spiny NetworkManager[820]: (wlp3s0): deactivating device (reason 'sleeping') [37] Aug 23 15:13:21 spiny NetworkManager[820]: (wlp3s0): canceled DHCP transaction, DHCP client pid 925 Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for 2601:1c0:4d00:39e6:f912:fbb6:aaa6:4429 on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for 2601:1c0:4d00:39e6:290:4cff:fe0d:f43e on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Leaving mDNS multicast group on interface wlp3s0.IPv6 with address 2601:1c0:4d00:39e6:290:4cff:fe0d:f43e. Aug 23 15:13:21 spiny avahi-daemon[826]: Joining mDNS multicast group on interface wlp3s0.IPv6 with address fe80::290:4cff:fe0d:f43e. Aug 23 15:13:21 spiny avahi-daemon[826]: Registering new address record for fe80::290:4cff:fe0d:f43e on wlp3s0.*. Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for fe80::290:4cff:fe0d:f43e on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Leaving mDNS multicast group on interface wlp3s0.IPv6 with address fe80::290:4cff:fe0d:f43e. Aug 23 15:13:21 spiny avahi-daemon[826]: Interface wlp3s0.IPv6 no longer relevant for mDNS. Aug 23 15:13:21 spiny wpa_supplicant[891]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=10:c3:7b:c5:83:d8 reason=3 locally_generated=1 Aug 23 15:13:21 spiny wpa_supplicant[891]: nl80211: Was expecting local disconnect but got another disconnect event first Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for 192.168.1.83 on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Leaving mDNS multicast group on interface wlp3s0.IPv4 with address 192.168.1.83. Aug 23 15:13:21 spiny avahi-daemon[826]: Interface wlp3s0.IPv4 no longer relevant for mDNS. Aug 23 15:13:21 spiny kernel: cfg80211: Calling CRDA to update world regulatory domain Aug 23 15:13:21 spiny NetworkManager[820]: Writing DNS information to /sbin/resolvconf Aug 23 15:13:21 spiny dnsmasq[928]: setting upstream servers from DBus Aug 23 15:13:21 spiny dnsmasq[928]: using nameserver 2601:1c0:4d00:39e6::1#53 Aug 23 15:13:21 spiny dbus[806]: [system] Rejected send message, 10 matched rules; type="method_return", sender=":1.22" (uid=0 pid=928 comm="/usr/sbin/dnsmasq --no-resolv --keep-in-foreground") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.6" (uid=0 pid=820 comm="/usr/sbin/NetworkManager --no-daemon ") Aug 23 15:13:21 spiny wpa_supplicant[891]: p2p-dev-wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Aug 23 15:13:21 spiny NetworkManager[820]: Writing DNS information to /sbin/resolvconf Aug 23 15:13:21 spiny kernel: brcmf_cfg80211_reg_notifier: not a ISO3166 code Aug 23 15:13:21 spiny kernel: cfg80211: World regulatory domain updated: Aug 23 15:13:21 spiny kernel: cfg80211: DFS Master region: unset Aug 23 15:13:21 spiny kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) Aug 23 15:13:21 spiny kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (517 KHz - 525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (525 KHz - 533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s) Aug 23 15:13:21 spiny kernel: cfg80211: (549 KHz - 573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s) Aug 23 15:13:21 spiny kernel: cfg80211: (5735000 KHz - 5835000 K
[Kernel-packages] [Bug 1510125] [NEW] occasionally loses external monitor
Public bug reported: Occasionally the screen will blank and all windows move from the external monitor to the laptop monitor. Relatively immediately afterward both screens re-enable, but the windows don't move back to the external monitor. This usually appears to be triggered by a specific application, eg, "ScudCloud" (a slack client that embeds an HTML webkit view), or enabling the flash plugin in an existing firefox window. dmesg shows: [ 174.404713] [ cut here ] [ 174.404736] WARNING: CPU: 0 PID: 1699 at /build/linux-AxjFAn/linux-4.2.0/drivers/gpu/drm/i915/i915_gem.c:5269 i915_gem_track_fb+0x129/0x140 [i915]() [ 174.404738] WARN_ON(!(old->frontbuffer_bits & frontbuffer_bits)) [ 174.404739] Modules linked in: [ 174.404741] bnep pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) asix usbnet mii xt_addrtype xt_conntrack ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 iptable_filter ip_tables x_tables nf_nat nf_conntrack bridge stp llc aufs nls_iso8859_1 applesmc input_polldev uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev media btusb btrtl btbcm btintel bluetooth snd_usb_audio snd_usbmidi_lib joydev input_leds bcm5974 snd_hda_codec_hdmi x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_cirrus kvm_intel snd_hda_codec_generic kvm snd_seq_midi snd_seq_midi_event brcmfmac snd_hda_intel brcmutil snd_hda_codec snd_hda_core cfg80211 snd_hwdep snd_rawmidi bdc_pci lpc_ich snd_pcm mei_me snd_seq mei snd_seq_device [ 174.404776] snd_timer thunderbolt snd sbs soundcore acpi_als kfifo_buf shpchp sbshc industrialio apple_gmux mac_hid apple_bl parport_pc ppdev lp parport autofs4 jitterentropy_rng drbg ansi_cprng algif_skcipher af_alg dm_crypt hid_plantronics hid_microsoft hid_logitech_hidpp hid_generic hid_logitech_dj hid_apple usbhid hid crct10dif_pclmul crc32_pclmul i915 ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper i2c_algo_bit uas cryptd drm_kms_helper usb_storage drm ahci libahci video [ 174.404803] CPU: 0 PID: 1699 Comm: gnome-shell Tainted: G OE 4.2.0-16-generic #19-Ubuntu [ 174.404804] Hardware name: Apple Inc. MacBookPro11,4/Mac-06F11FD93F0323C5, BIOS MBP114.88Z.0172.B04.1506051511 06/05/2015 [ 174.404806] 5f8a407a 8804613eba28 817e8c09 [ 174.404808] 8804613eba80 8804613eba68 8107b3c6 [ 174.404811] 880465a3 0001 88046756e640 8804658558c0 [ 174.404813] Call Trace: [ 174.404818] [] dump_stack+0x45/0x57 [ 174.404823] [] warn_slowpath_common+0x86/0xc0 [ 174.404825] [] warn_slowpath_fmt+0x55/0x70 [ 174.404836] [] i915_gem_track_fb+0x129/0x140 [i915] [ 174.404852] [] intel_prepare_plane_fb+0xe7/0x1a0 [i915] [ 174.404859] [] drm_atomic_helper_prepare_planes+0x59/0xe0 [drm_kms_helper] [ 174.404872] [] __intel_set_mode+0x1ae/0xb60 [i915] [ 174.404886] [] intel_crtc_set_config+0x2b6/0x580 [i915] [ 174.404899] [] ? drm_mode_create+0x25/0x60 [drm] [ 174.404908] [] drm_mode_set_config_internal+0x66/0x100 [drm] [ 174.404917] [] drm_mode_setcrtc+0x3e9/0x500 [drm] [ 174.404923] [] drm_ioctl+0x125/0x610 [drm] [ 174.404930] [] ? drm_mode_setplane+0x1b0/0x1b0 [drm] [ 174.404934] [] do_vfs_ioctl+0x295/0x480 [ 174.404936] [] SyS_ioctl+0x79/0x90 [ 174.404939] [] entry_SYSCALL_64_fastpath+0x16/0x75 [ 174.404941] ---[ end trace fc649a1af1173285 ]--- [ 175.018549] snd_hda_codec_hdmi hdaudioC0D0: HDMI: ELD buf size is 0, force 128 [ 175.018587] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 0 [ 175.184359] thunderbolt :07:00.0: resetting error on 0:c. [ 175.184396] thunderbolt :07:00.0: 0:c: hotplug: scanning [ 175.184400] thunderbolt :07:00.0: 0:c: hotplug: no switch found [ 176.225350] thunderbolt :07:00.0: resetting error on 0:c. [ 176.225389] thunderbolt :07:00.0: 0:c: got unplug event for disconnected port, ignoring [ 181.480150] usb 1-1.3.1: reset high-speed USB device number 10 using xhci_hcd [ 581.943528] usb 1-1.3.1: reset high-speed USB device number 10 using xhci_hcd ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 26 07:38:02 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=dd225ec0-47f4-49d8-a51c-a2547f8eb945 InstallationDate: Installed on 2015-08-21 (66 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) MachineType: Apple Inc. MacBookPro11,4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg
[Kernel-packages] [Bug 1444094] Re: Often have to reload wl module to connect to WPA2/Enterprise network
** Package changed: ubuntu => bcmwl (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1444094 Title: Often have to reload wl module to connect to WPA2/Enterprise network Status in bcmwl package in Ubuntu: New Bug description: I have a WPA2 Enterprise network at work using PEAP authentication with a CA cert that I have on disk and MSCHAPv2 inner authentication. I can connect to it fine via gnome's network-manager integration, but often (1-3 times per day) need to rmmod wl; modprobe wl; in order to successfully associate with the AP. The only related log message I see in syslog when this happens is: NetworkManager[9871]: Activation (wlan0/wireless): association took too long, failing activation. NetworkManager[9871]: (wlan0): device state change: config -> failed (reason 'ssid-not-found') [50 120 53] I do not have this issue with my WPA2 Personal AP at home. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: wl (not installed) ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.17-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Apr 14 11:03:10 2015 InstallationDate: Installed on 2014-02-24 (414 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140218) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wl UpgradeStatus: Upgraded to vivid on 2015-02-04 (68 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1444094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1487919] Re: macbookrpro12, 1 fails to suspend
possibly related upstream bugs: https://bugzilla.kernel.org/show_bug.cgi?id=101681 https://bugzilla.kernel.org/show_bug.cgi?id=103211 ** Bug watch added: Linux Kernel Bug Tracker #101681 http://bugzilla.kernel.org/show_bug.cgi?id=101681 ** Bug watch added: Linux Kernel Bug Tracker #103211 http://bugzilla.kernel.org/show_bug.cgi?id=103211 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1487919 Title: macbookrpro12,1 fails to suspend Status in linux package in Ubuntu: Confirmed Bug description: I've installed wily on a new macbookpro12,1 (2015 model), and suspending the system results in the screen going black and the apple light turning off, but the system is not fully asleep -- the 'force touch' pad still makes clicking feedback, and the machine continues to generate heat and spin fans if put into a bag. Once in this state, the machine cannot be woken up from the state its in either. did a "journalctl -f | tee sleep.log' while this was happening and got the following output -- let me know if there is a better way to figure out where things are going wrong: Aug 23 15:13:21 spiny NetworkManager[820]: sleep requested (sleeping: no enabled: yes) Aug 23 15:13:21 spiny NetworkManager[820]: sleeping... Aug 23 15:13:21 spiny NetworkManager[820]: (wlp3s0): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37] Aug 23 15:13:21 spiny NetworkManager[820]: (wlp3s0): deactivating device (reason 'sleeping') [37] Aug 23 15:13:21 spiny NetworkManager[820]: (wlp3s0): canceled DHCP transaction, DHCP client pid 925 Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for 2601:1c0:4d00:39e6:f912:fbb6:aaa6:4429 on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for 2601:1c0:4d00:39e6:290:4cff:fe0d:f43e on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Leaving mDNS multicast group on interface wlp3s0.IPv6 with address 2601:1c0:4d00:39e6:290:4cff:fe0d:f43e. Aug 23 15:13:21 spiny avahi-daemon[826]: Joining mDNS multicast group on interface wlp3s0.IPv6 with address fe80::290:4cff:fe0d:f43e. Aug 23 15:13:21 spiny avahi-daemon[826]: Registering new address record for fe80::290:4cff:fe0d:f43e on wlp3s0.*. Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for fe80::290:4cff:fe0d:f43e on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Leaving mDNS multicast group on interface wlp3s0.IPv6 with address fe80::290:4cff:fe0d:f43e. Aug 23 15:13:21 spiny avahi-daemon[826]: Interface wlp3s0.IPv6 no longer relevant for mDNS. Aug 23 15:13:21 spiny wpa_supplicant[891]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=10:c3:7b:c5:83:d8 reason=3 locally_generated=1 Aug 23 15:13:21 spiny wpa_supplicant[891]: nl80211: Was expecting local disconnect but got another disconnect event first Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for 192.168.1.83 on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Leaving mDNS multicast group on interface wlp3s0.IPv4 with address 192.168.1.83. Aug 23 15:13:21 spiny avahi-daemon[826]: Interface wlp3s0.IPv4 no longer relevant for mDNS. Aug 23 15:13:21 spiny kernel: cfg80211: Calling CRDA to update world regulatory domain Aug 23 15:13:21 spiny NetworkManager[820]: Writing DNS information to /sbin/resolvconf Aug 23 15:13:21 spiny dnsmasq[928]: setting upstream servers from DBus Aug 23 15:13:21 spiny dnsmasq[928]: using nameserver 2601:1c0:4d00:39e6::1#53 Aug 23 15:13:21 spiny dbus[806]: [system] Rejected send message, 10 matched rules; type="method_return", sender=":1.22" (uid=0 pid=928 comm="/usr/sbin/dnsmasq --no-resolv --keep-in-foreground") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.6" (uid=0 pid=820 comm="/usr/sbin/NetworkManager --no-daemon ") Aug 23 15:13:21 spiny wpa_supplicant[891]: p2p-dev-wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Aug 23 15:13:21 spiny NetworkManager[820]: Writing DNS information to /sbin/resolvconf Aug 23 15:13:21 spiny kernel: brcmf_cfg80211_reg_notifier: not a ISO3166 code Aug 23 15:13:21 spiny kernel: cfg80211: World regulatory domain updated: Aug 23 15:13:21 spiny kernel: cfg80211: DFS Master region: unset Aug 23 15:13:21 spiny kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) Aug 23 15:13:21 spiny kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (517 KHz - 525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny ke
[Kernel-packages] [Bug 1487524] Re: Broadcom BCM43602 not seeing 5Ghz range
this looks to be mentioned in existing bug https://bugzilla.kernel.org/show_bug.cgi?id=100201 ** Bug watch added: Linux Kernel Bug Tracker #100201 http://bugzilla.kernel.org/show_bug.cgi?id=100201 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1487524 Title: Broadcom BCM43602 not seeing 5Ghz range Status in linux package in Ubuntu: Triaged Bug description: On a MacbookPro12,1 (2015 model), the wireless works with the brcmfmac on a wily install out of the box, but can't see any APs on the 5GHz range even though there are APs broadcasting on 5Ghz. 03:00.0 Network controller: Broadcom Corporation BCM43602 802.11ac Wireless LAN SoC (rev 01) Subsystem: Apple Inc. Device 0152 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: brcmfmac $ sudo iwlist wlp3s0 scan|grep Freq Frequency:2.412 GHz (Channel 1) Frequency:2.422 GHz (Channel 3) ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.1.0-3-generic 4.1.0-3.3 [modified: boot/vmlinuz-4.1.0-3-generic] ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: jbarnett 1545 F pulseaudio /dev/snd/controlC2: jbarnett 1545 F pulseaudio /dev/snd/controlC1: jbarnett 1545 F pulseaudio /dev/snd/controlC0: jbarnett 1545 F pulseaudio CurrentDesktop: GNOME Date: Fri Aug 21 08:46:15 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=dd225ec0-47f4-49d8-a51c-a2547f8eb945 InstallationDate: Installed on 2015-08-21 (0 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) MachineType: Apple Inc. MacBookPro11,4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-3-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.1.0-3-generic N/A linux-backports-modules-4.1.0-3-generic N/A linux-firmware 1.146 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B04.1506051511 dmi.board.name: Mac-06F11FD93F0323C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,4 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11FD93F0323C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5: dmi.product.name: MacBookPro11,4 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1487524/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1487919] Re: macbookrpro12, 1 fails to suspend
looks like http://kernel.ubuntu.com/~kernel- ppa/mainline/v4.3-rc1-unstable/ failed to build and/or is missing .debs to install? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1487919 Title: macbookrpro12,1 fails to suspend Status in linux package in Ubuntu: Incomplete Bug description: I've installed wily on a new macbookpro12,1 (2015 model), and suspending the system results in the screen going black and the apple light turning off, but the system is not fully asleep -- the 'force touch' pad still makes clicking feedback, and the machine continues to generate heat and spin fans if put into a bag. Once in this state, the machine cannot be woken up from the state its in either. did a "journalctl -f | tee sleep.log' while this was happening and got the following output -- let me know if there is a better way to figure out where things are going wrong: Aug 23 15:13:21 spiny NetworkManager[820]: sleep requested (sleeping: no enabled: yes) Aug 23 15:13:21 spiny NetworkManager[820]: sleeping... Aug 23 15:13:21 spiny NetworkManager[820]: (wlp3s0): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37] Aug 23 15:13:21 spiny NetworkManager[820]: (wlp3s0): deactivating device (reason 'sleeping') [37] Aug 23 15:13:21 spiny NetworkManager[820]: (wlp3s0): canceled DHCP transaction, DHCP client pid 925 Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for 2601:1c0:4d00:39e6:f912:fbb6:aaa6:4429 on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for 2601:1c0:4d00:39e6:290:4cff:fe0d:f43e on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Leaving mDNS multicast group on interface wlp3s0.IPv6 with address 2601:1c0:4d00:39e6:290:4cff:fe0d:f43e. Aug 23 15:13:21 spiny avahi-daemon[826]: Joining mDNS multicast group on interface wlp3s0.IPv6 with address fe80::290:4cff:fe0d:f43e. Aug 23 15:13:21 spiny avahi-daemon[826]: Registering new address record for fe80::290:4cff:fe0d:f43e on wlp3s0.*. Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for fe80::290:4cff:fe0d:f43e on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Leaving mDNS multicast group on interface wlp3s0.IPv6 with address fe80::290:4cff:fe0d:f43e. Aug 23 15:13:21 spiny avahi-daemon[826]: Interface wlp3s0.IPv6 no longer relevant for mDNS. Aug 23 15:13:21 spiny wpa_supplicant[891]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=10:c3:7b:c5:83:d8 reason=3 locally_generated=1 Aug 23 15:13:21 spiny wpa_supplicant[891]: nl80211: Was expecting local disconnect but got another disconnect event first Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for 192.168.1.83 on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Leaving mDNS multicast group on interface wlp3s0.IPv4 with address 192.168.1.83. Aug 23 15:13:21 spiny avahi-daemon[826]: Interface wlp3s0.IPv4 no longer relevant for mDNS. Aug 23 15:13:21 spiny kernel: cfg80211: Calling CRDA to update world regulatory domain Aug 23 15:13:21 spiny NetworkManager[820]: Writing DNS information to /sbin/resolvconf Aug 23 15:13:21 spiny dnsmasq[928]: setting upstream servers from DBus Aug 23 15:13:21 spiny dnsmasq[928]: using nameserver 2601:1c0:4d00:39e6::1#53 Aug 23 15:13:21 spiny dbus[806]: [system] Rejected send message, 10 matched rules; type="method_return", sender=":1.22" (uid=0 pid=928 comm="/usr/sbin/dnsmasq --no-resolv --keep-in-foreground") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.6" (uid=0 pid=820 comm="/usr/sbin/NetworkManager --no-daemon ") Aug 23 15:13:21 spiny wpa_supplicant[891]: p2p-dev-wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Aug 23 15:13:21 spiny NetworkManager[820]: Writing DNS information to /sbin/resolvconf Aug 23 15:13:21 spiny kernel: brcmf_cfg80211_reg_notifier: not a ISO3166 code Aug 23 15:13:21 spiny kernel: cfg80211: World regulatory domain updated: Aug 23 15:13:21 spiny kernel: cfg80211: DFS Master region: unset Aug 23 15:13:21 spiny kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) Aug 23 15:13:21 spiny kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (517 KHz - 525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (525 KHz - 533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s) Aug 23 15:13:21 spiny kernel: cfg80211: (549 KHz - 573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s) Aug 23
[Kernel-packages] [Bug 1487919] Re: macbookrpro12, 1 fails to suspend
yes still happens with 4.2 ** 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/1487919 Title: macbookrpro12,1 fails to suspend Status in linux package in Ubuntu: Confirmed Bug description: I've installed wily on a new macbookpro12,1 (2015 model), and suspending the system results in the screen going black and the apple light turning off, but the system is not fully asleep -- the 'force touch' pad still makes clicking feedback, and the machine continues to generate heat and spin fans if put into a bag. Once in this state, the machine cannot be woken up from the state its in either. did a "journalctl -f | tee sleep.log' while this was happening and got the following output -- let me know if there is a better way to figure out where things are going wrong: Aug 23 15:13:21 spiny NetworkManager[820]: sleep requested (sleeping: no enabled: yes) Aug 23 15:13:21 spiny NetworkManager[820]: sleeping... Aug 23 15:13:21 spiny NetworkManager[820]: (wlp3s0): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37] Aug 23 15:13:21 spiny NetworkManager[820]: (wlp3s0): deactivating device (reason 'sleeping') [37] Aug 23 15:13:21 spiny NetworkManager[820]: (wlp3s0): canceled DHCP transaction, DHCP client pid 925 Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for 2601:1c0:4d00:39e6:f912:fbb6:aaa6:4429 on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for 2601:1c0:4d00:39e6:290:4cff:fe0d:f43e on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Leaving mDNS multicast group on interface wlp3s0.IPv6 with address 2601:1c0:4d00:39e6:290:4cff:fe0d:f43e. Aug 23 15:13:21 spiny avahi-daemon[826]: Joining mDNS multicast group on interface wlp3s0.IPv6 with address fe80::290:4cff:fe0d:f43e. Aug 23 15:13:21 spiny avahi-daemon[826]: Registering new address record for fe80::290:4cff:fe0d:f43e on wlp3s0.*. Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for fe80::290:4cff:fe0d:f43e on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Leaving mDNS multicast group on interface wlp3s0.IPv6 with address fe80::290:4cff:fe0d:f43e. Aug 23 15:13:21 spiny avahi-daemon[826]: Interface wlp3s0.IPv6 no longer relevant for mDNS. Aug 23 15:13:21 spiny wpa_supplicant[891]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=10:c3:7b:c5:83:d8 reason=3 locally_generated=1 Aug 23 15:13:21 spiny wpa_supplicant[891]: nl80211: Was expecting local disconnect but got another disconnect event first Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for 192.168.1.83 on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Leaving mDNS multicast group on interface wlp3s0.IPv4 with address 192.168.1.83. Aug 23 15:13:21 spiny avahi-daemon[826]: Interface wlp3s0.IPv4 no longer relevant for mDNS. Aug 23 15:13:21 spiny kernel: cfg80211: Calling CRDA to update world regulatory domain Aug 23 15:13:21 spiny NetworkManager[820]: Writing DNS information to /sbin/resolvconf Aug 23 15:13:21 spiny dnsmasq[928]: setting upstream servers from DBus Aug 23 15:13:21 spiny dnsmasq[928]: using nameserver 2601:1c0:4d00:39e6::1#53 Aug 23 15:13:21 spiny dbus[806]: [system] Rejected send message, 10 matched rules; type="method_return", sender=":1.22" (uid=0 pid=928 comm="/usr/sbin/dnsmasq --no-resolv --keep-in-foreground") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.6" (uid=0 pid=820 comm="/usr/sbin/NetworkManager --no-daemon ") Aug 23 15:13:21 spiny wpa_supplicant[891]: p2p-dev-wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Aug 23 15:13:21 spiny NetworkManager[820]: Writing DNS information to /sbin/resolvconf Aug 23 15:13:21 spiny kernel: brcmf_cfg80211_reg_notifier: not a ISO3166 code Aug 23 15:13:21 spiny kernel: cfg80211: World regulatory domain updated: Aug 23 15:13:21 spiny kernel: cfg80211: DFS Master region: unset Aug 23 15:13:21 spiny kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) Aug 23 15:13:21 spiny kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (517 KHz - 525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (525 KHz - 533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s) Aug 23 15:13:21 spiny kernel: cfg80211: (549 KHz - 573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s) Aug 23 15:13:21 spiny kernel: cfg80211:
[Kernel-packages] [Bug 1497321] [NEW] thunderbolt ethernet adapter not hotpluggable on MacbookPro12, 1
Public bug reported: It works if plugged in while booted, but not after removing / replugging, or if plugging in after booted. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-10-generic 4.2.0-10.11 ProcVersionSignature: Ubuntu 4.2.0-10.11-generic 4.2.0 Uname: Linux 4.2.0-10-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Sep 18 07:49:45 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=dd225ec0-47f4-49d8-a51c-a2547f8eb945 InstallationDate: Installed on 2015-08-21 (28 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) MachineType: Apple Inc. MacBookPro11,4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-10-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-10-generic N/A linux-backports-modules-4.2.0-10-generic N/A linux-firmware1.147 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B04.1506051511 dmi.board.name: Mac-06F11FD93F0323C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,4 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11FD93F0323C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5: dmi.product.name: MacBookPro11,4 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: linux Importance: Unknown Status: Unknown ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily ** Bug watch added: Linux Kernel Bug Tracker #100191 http://bugzilla.kernel.org/show_bug.cgi?id=100191 ** Also affects: linux via http://bugzilla.kernel.org/show_bug.cgi?id=100191 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1497321 Title: thunderbolt ethernet adapter not hotpluggable on MacbookPro12,1 Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: It works if plugged in while booted, but not after removing / replugging, or if plugging in after booted. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-10-generic 4.2.0-10.11 ProcVersionSignature: Ubuntu 4.2.0-10.11-generic 4.2.0 Uname: Linux 4.2.0-10-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Sep 18 07:49:45 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=dd225ec0-47f4-49d8-a51c-a2547f8eb945 InstallationDate: Installed on 2015-08-21 (28 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) MachineType: Apple Inc. MacBookPro11,4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-10-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-10-generic N/A linux-backports-modules-4.2.0-10-generic N/A linux-firmware1.147 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B04.1506051511 dmi.board.name: Mac-06F11FD93F0323C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,4 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11FD93F0323C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5: dmi.product.name: MacBookPro11,4 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1497321/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchp
[Kernel-packages] [Bug 1497321] Re: thunderbolt ethernet adapter not hotpluggable on MacbookPro12, 1
looks like the patch attached to this upstream bug should fix it. would it be possible to get that into ubuntu kernels? 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/1497321 Title: thunderbolt ethernet adapter not hotpluggable on MacbookPro12,1 Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: It works if plugged in while booted, but not after removing / replugging, or if plugging in after booted. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-10-generic 4.2.0-10.11 ProcVersionSignature: Ubuntu 4.2.0-10.11-generic 4.2.0 Uname: Linux 4.2.0-10-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Sep 18 07:49:45 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=dd225ec0-47f4-49d8-a51c-a2547f8eb945 InstallationDate: Installed on 2015-08-21 (28 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) MachineType: Apple Inc. MacBookPro11,4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-10-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-10-generic N/A linux-backports-modules-4.2.0-10-generic N/A linux-firmware1.147 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B04.1506051511 dmi.board.name: Mac-06F11FD93F0323C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,4 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11FD93F0323C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5: dmi.product.name: MacBookPro11,4 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1497321/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1510125] Re: occasionally loses external monitor
Still happens on 4.3 mainline. It's happened on every kernel I've used on this machine, and feels related to bug #1493989 , though may not be. ** Tags added: kernel-bug-exists-upstream ** 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/1510125 Title: occasionally loses external monitor Status in linux package in Ubuntu: Confirmed Bug description: Occasionally the screen will blank and all windows move from the external monitor to the laptop monitor. Relatively immediately afterward both screens re-enable, but the windows don't move back to the external monitor. This usually appears to be triggered by a specific application, eg, "ScudCloud" (a slack client that embeds an HTML webkit view), or enabling the flash plugin in an existing firefox window. dmesg shows: [ 174.404713] [ cut here ] [ 174.404736] WARNING: CPU: 0 PID: 1699 at /build/linux-AxjFAn/linux-4.2.0/drivers/gpu/drm/i915/i915_gem.c:5269 i915_gem_track_fb+0x129/0x140 [i915]() [ 174.404738] WARN_ON(!(old->frontbuffer_bits & frontbuffer_bits)) [ 174.404739] Modules linked in: [ 174.404741] bnep pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) asix usbnet mii xt_addrtype xt_conntrack ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 iptable_filter ip_tables x_tables nf_nat nf_conntrack bridge stp llc aufs nls_iso8859_1 applesmc input_polldev uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev media btusb btrtl btbcm btintel bluetooth snd_usb_audio snd_usbmidi_lib joydev input_leds bcm5974 snd_hda_codec_hdmi x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_cirrus kvm_intel snd_hda_codec_generic kvm snd_seq_midi snd_seq_midi_event brcmfmac snd_hda_intel brcmutil snd_hda_codec snd_hda_core cfg80211 snd_hwdep snd_rawmidi bdc_pci lpc_ich snd_pcm mei_me snd_seq mei snd_seq_device [ 174.404776] snd_timer thunderbolt snd sbs soundcore acpi_als kfifo_buf shpchp sbshc industrialio apple_gmux mac_hid apple_bl parport_pc ppdev lp parport autofs4 jitterentropy_rng drbg ansi_cprng algif_skcipher af_alg dm_crypt hid_plantronics hid_microsoft hid_logitech_hidpp hid_generic hid_logitech_dj hid_apple usbhid hid crct10dif_pclmul crc32_pclmul i915 ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper i2c_algo_bit uas cryptd drm_kms_helper usb_storage drm ahci libahci video [ 174.404803] CPU: 0 PID: 1699 Comm: gnome-shell Tainted: G OE 4.2.0-16-generic #19-Ubuntu [ 174.404804] Hardware name: Apple Inc. MacBookPro11,4/Mac-06F11FD93F0323C5, BIOS MBP114.88Z.0172.B04.1506051511 06/05/2015 [ 174.404806] 5f8a407a 8804613eba28 817e8c09 [ 174.404808] 8804613eba80 8804613eba68 8107b3c6 [ 174.404811] 880465a3 0001 88046756e640 8804658558c0 [ 174.404813] Call Trace: [ 174.404818] [] dump_stack+0x45/0x57 [ 174.404823] [] warn_slowpath_common+0x86/0xc0 [ 174.404825] [] warn_slowpath_fmt+0x55/0x70 [ 174.404836] [] i915_gem_track_fb+0x129/0x140 [i915] [ 174.404852] [] intel_prepare_plane_fb+0xe7/0x1a0 [i915] [ 174.404859] [] drm_atomic_helper_prepare_planes+0x59/0xe0 [drm_kms_helper] [ 174.404872] [] __intel_set_mode+0x1ae/0xb60 [i915] [ 174.404886] [] intel_crtc_set_config+0x2b6/0x580 [i915] [ 174.404899] [] ? drm_mode_create+0x25/0x60 [drm] [ 174.404908] [] drm_mode_set_config_internal+0x66/0x100 [drm] [ 174.404917] [] drm_mode_setcrtc+0x3e9/0x500 [drm] [ 174.404923] [] drm_ioctl+0x125/0x610 [drm] [ 174.404930] [] ? drm_mode_setplane+0x1b0/0x1b0 [drm] [ 174.404934] [] do_vfs_ioctl+0x295/0x480 [ 174.404936] [] SyS_ioctl+0x79/0x90 [ 174.404939] [] entry_SYSCALL_64_fastpath+0x16/0x75 [ 174.404941] ---[ end trace fc649a1af1173285 ]--- [ 175.018549] snd_hda_codec_hdmi hdaudioC0D0: HDMI: ELD buf size is 0, force 128 [ 175.018587] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 0 [ 175.184359] thunderbolt :07:00.0: resetting error on 0:c. [ 175.184396] thunderbolt :07:00.0: 0:c: hotplug: scanning [ 175.184400] thunderbolt :07:00.0: 0:c: hotplug: no switch found [ 176.225350] thunderbolt :07:00.0: resetting error on 0:c. [ 176.225389] thunderbolt :07:00.0: 0:c: got unplug event for disconnected port, ignoring [ 181.480150] usb 1-1.3.1: reset high-speed USB device number 10 using xhci_hcd [ 581.943528] usb 1-1.3.1: reset high-speed USB device number 10 using xhci_hcd ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-1
[Kernel-packages] [Bug 1448566] Re: Ubuntu 15.04 - Macbook Pro Early 2015 (12, 1) Bluetooth disabled
this is also in the bluetooth (not bluetooth-next) repo: https://git.kernel.org/cgit/linux/kernel/git/bluetooth/bluetooth.git/commit/?id=22f8e9dbf671a2f36d90d3d8723a2a0c5227fa4b , would it be possible to include in the wily kernel as a SAUCE patch at this point? -- 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/1448566 Title: Ubuntu 15.04 - Macbook Pro Early 2015 (12,1) Bluetooth disabled Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: Fresh install of 15.04 on a Macbook Pro 12,1. I get no Bluetooth icon in the status bar, and in System Settings > Bluetooth, everything is greyed out (i.e., can't turn it on). $lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; rfkill list all; lsmod | grep bluetooth; hciconfig -a; uname -a 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 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 004: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [ 32.369395] usb 1-3: Product: Bluetooth USB Host Controller [ 32.435743] input: Broadcom Corp. Bluetooth USB Host Controller as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/0003:05AC:8290.0006/input/input7 [ 32.490662] hid-generic 0003:05AC:8290.0006: input,hidraw5: USB HID v1.11 Keyboard [Broadcom Corp. Bluetooth USB Host Controller] on usb-:00:14.0-3/input0 [ 32.490750] input: Broadcom Corp. Bluetooth USB Host Controller as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.1/0003:05AC:8290.0007/input/input8 [ 32.490995] hid-generic 0003:05AC:8290.0007: input,hidraw6: USB HID v1.11 Mouse [Broadcom Corp. Bluetooth USB Host Controller] on usb-:00:14.0-3/input1 [ 34.866186] Bluetooth: Core ver 2.20 [ 34.866205] Bluetooth: HCI device and connection manager initialized [ 34.866751] Bluetooth: HCI socket layer initialized [ 34.866754] Bluetooth: L2CAP socket layer initialized [ 34.866759] Bluetooth: SCO socket layer initialized [ 0.158493] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored [ 0.168342] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain [bus 00-9b] only partially covers this bridge [ 35.003383] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt failed with error -2 [ 35.290656] brcmf_c_preinit_dcmds: Firmware version = wl0: Mar 13 2015 08:11:08 version 7.35.177.36 (r540934) FWID 01-e4dc15b 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no bluetooth 491520 1 btusb Linux hxn-laptop-linux 3.19.0-15-generic #15-Ubuntu SMP Thu Apr 16 23:32:37 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1448566/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1443370] Re: fn key not working on Macbook Pro 12, 1
looks like the patch in the upstream bug made it into 4.2-rc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1443370 Title: fn key not working on Macbook Pro 12,1 Status in linux package in Ubuntu: Triaged Bug description: The 'fn' key on the Macbook Pro 12,1 (Early 2015) is not working. The modifier is not captured by xev and the combination with any key reports the original key. More users are reporting the same issue on the forums: http://ubuntuforums.org/showthread.php?t=2270831&p=13252628#post13252628 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1443370/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1487524] [NEW] Broadcom BCM43602 not seeing 5Ghz range
Public bug reported: On a MacbookPro12,1 (2015 model), the wireless works with the brcmfmac on a wily install out of the box, but can't see any APs on the 5GHz range even though there are APs broadcasting on 5Ghz. 03:00.0 Network controller: Broadcom Corporation BCM43602 802.11ac Wireless LAN SoC (rev 01) Subsystem: Apple Inc. Device 0152 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: brcmfmac $ sudo iwlist wlp3s0 scan|grep Freq Frequency:2.412 GHz (Channel 1) Frequency:2.422 GHz (Channel 3) ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.1.0-3-generic 4.1.0-3.3 [modified: boot/vmlinuz-4.1.0-3-generic] ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: jbarnett 1545 F pulseaudio /dev/snd/controlC2: jbarnett 1545 F pulseaudio /dev/snd/controlC1: jbarnett 1545 F pulseaudio /dev/snd/controlC0: jbarnett 1545 F pulseaudio CurrentDesktop: GNOME Date: Fri Aug 21 08:46:15 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=dd225ec0-47f4-49d8-a51c-a2547f8eb945 InstallationDate: Installed on 2015-08-21 (0 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) MachineType: Apple Inc. MacBookPro11,4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-3-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.1.0-3-generic N/A linux-backports-modules-4.1.0-3-generic N/A linux-firmware 1.146 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B04.1506051511 dmi.board.name: Mac-06F11FD93F0323C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,4 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11FD93F0323C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5: dmi.product.name: MacBookPro11,4 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1487524 Title: Broadcom BCM43602 not seeing 5Ghz range Status in linux package in Ubuntu: Confirmed Bug description: On a MacbookPro12,1 (2015 model), the wireless works with the brcmfmac on a wily install out of the box, but can't see any APs on the 5GHz range even though there are APs broadcasting on 5Ghz. 03:00.0 Network controller: Broadcom Corporation BCM43602 802.11ac Wireless LAN SoC (rev 01) Subsystem: Apple Inc. Device 0152 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: brcmfmac $ sudo iwlist wlp3s0 scan|grep Freq Frequency:2.412 GHz (Channel 1) Frequency:2.422 GHz (Channel 3) ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.1.0-3-generic 4.1.0-3.3 [modified: boot/vmlinuz-4.1.0-3-generic] ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: jbarnett 1545 F pulseaudio /dev/snd/controlC2: jbarnett 1545 F pulseaudio /dev/snd/controlC1: jbarnett 1545 F pulseaudio /dev/snd/controlC0: jbarnett 1545 F pulseaudio CurrentDesktop: GNOME Date: Fri Aug 21 08:46:15 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=dd225ec0-47f4-49d8-a51c-a2547f8eb945 InstallationDate: Installed on 2015-08-21 (0 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) MachineType: Apple Inc. MacBookPro11,4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKern
[Kernel-packages] [Bug 1487919] [NEW] macbookrpro12, 1 fails to suspend
Public bug reported: I've installed wily on a new macbookpro12,1 (2015 model), and suspending the system results in the screen going black and the apple light turning off, but the system is not fully asleep -- the 'force touch' pad still makes clicking feedback, and the machine continues to generate heat and spin fans if put into a bag. Once in this state, the machine cannot be woken up from the state its in either. did a "journalctl -f | tee sleep.log' while this was happening and got the following output -- let me know if there is a better way to figure out where things are going wrong: Aug 23 15:13:21 spiny NetworkManager[820]: sleep requested (sleeping: no enabled: yes) Aug 23 15:13:21 spiny NetworkManager[820]: sleeping... Aug 23 15:13:21 spiny NetworkManager[820]: (wlp3s0): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37] Aug 23 15:13:21 spiny NetworkManager[820]: (wlp3s0): deactivating device (reason 'sleeping') [37] Aug 23 15:13:21 spiny NetworkManager[820]: (wlp3s0): canceled DHCP transaction, DHCP client pid 925 Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for 2601:1c0:4d00:39e6:f912:fbb6:aaa6:4429 on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for 2601:1c0:4d00:39e6:290:4cff:fe0d:f43e on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Leaving mDNS multicast group on interface wlp3s0.IPv6 with address 2601:1c0:4d00:39e6:290:4cff:fe0d:f43e. Aug 23 15:13:21 spiny avahi-daemon[826]: Joining mDNS multicast group on interface wlp3s0.IPv6 with address fe80::290:4cff:fe0d:f43e. Aug 23 15:13:21 spiny avahi-daemon[826]: Registering new address record for fe80::290:4cff:fe0d:f43e on wlp3s0.*. Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for fe80::290:4cff:fe0d:f43e on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Leaving mDNS multicast group on interface wlp3s0.IPv6 with address fe80::290:4cff:fe0d:f43e. Aug 23 15:13:21 spiny avahi-daemon[826]: Interface wlp3s0.IPv6 no longer relevant for mDNS. Aug 23 15:13:21 spiny wpa_supplicant[891]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=10:c3:7b:c5:83:d8 reason=3 locally_generated=1 Aug 23 15:13:21 spiny wpa_supplicant[891]: nl80211: Was expecting local disconnect but got another disconnect event first Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for 192.168.1.83 on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Leaving mDNS multicast group on interface wlp3s0.IPv4 with address 192.168.1.83. Aug 23 15:13:21 spiny avahi-daemon[826]: Interface wlp3s0.IPv4 no longer relevant for mDNS. Aug 23 15:13:21 spiny kernel: cfg80211: Calling CRDA to update world regulatory domain Aug 23 15:13:21 spiny NetworkManager[820]: Writing DNS information to /sbin/resolvconf Aug 23 15:13:21 spiny dnsmasq[928]: setting upstream servers from DBus Aug 23 15:13:21 spiny dnsmasq[928]: using nameserver 2601:1c0:4d00:39e6::1#53 Aug 23 15:13:21 spiny dbus[806]: [system] Rejected send message, 10 matched rules; type="method_return", sender=":1.22" (uid=0 pid=928 comm="/usr/sbin/dnsmasq --no-resolv --keep-in-foreground") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.6" (uid=0 pid=820 comm="/usr/sbin/NetworkManager --no-daemon ") Aug 23 15:13:21 spiny wpa_supplicant[891]: p2p-dev-wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Aug 23 15:13:21 spiny NetworkManager[820]: Writing DNS information to /sbin/resolvconf Aug 23 15:13:21 spiny kernel: brcmf_cfg80211_reg_notifier: not a ISO3166 code Aug 23 15:13:21 spiny kernel: cfg80211: World regulatory domain updated: Aug 23 15:13:21 spiny kernel: cfg80211: DFS Master region: unset Aug 23 15:13:21 spiny kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) Aug 23 15:13:21 spiny kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (517 KHz - 525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (525 KHz - 533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s) Aug 23 15:13:21 spiny kernel: cfg80211: (549 KHz - 573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s) Aug 23 15:13:21 spiny kernel: cfg80211: (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (5724 KHz - 6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A) Aug 23 15:13:21 spiny dnsmasq[928]: setting upstream servers from DBus Aug 23 15:13:21 spiny dbus[806]: [system] Rejected send message, 10 matched rules; type="method_return", sender=":1.22" (uid=0 pid=928 comm="/usr/sbin/dnsmasq --no-resolv --keep-in-foregroun
[Kernel-packages] [Bug 1487524] Re: Broadcom BCM43602 not seeing 5Ghz range
its a brand new machine, so haven't tried previous kernel, but the vivid install image didn't even have the firmware for this particular chipset, so brcmfmac didn't work out of the box. will test with mainline kernel and see what happens. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1487524 Title: Broadcom BCM43602 not seeing 5Ghz range Status in linux package in Ubuntu: Incomplete Bug description: On a MacbookPro12,1 (2015 model), the wireless works with the brcmfmac on a wily install out of the box, but can't see any APs on the 5GHz range even though there are APs broadcasting on 5Ghz. 03:00.0 Network controller: Broadcom Corporation BCM43602 802.11ac Wireless LAN SoC (rev 01) Subsystem: Apple Inc. Device 0152 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: brcmfmac $ sudo iwlist wlp3s0 scan|grep Freq Frequency:2.412 GHz (Channel 1) Frequency:2.422 GHz (Channel 3) ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.1.0-3-generic 4.1.0-3.3 [modified: boot/vmlinuz-4.1.0-3-generic] ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: jbarnett 1545 F pulseaudio /dev/snd/controlC2: jbarnett 1545 F pulseaudio /dev/snd/controlC1: jbarnett 1545 F pulseaudio /dev/snd/controlC0: jbarnett 1545 F pulseaudio CurrentDesktop: GNOME Date: Fri Aug 21 08:46:15 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=dd225ec0-47f4-49d8-a51c-a2547f8eb945 InstallationDate: Installed on 2015-08-21 (0 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) MachineType: Apple Inc. MacBookPro11,4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-3-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.1.0-3-generic N/A linux-backports-modules-4.1.0-3-generic N/A linux-firmware 1.146 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B04.1506051511 dmi.board.name: Mac-06F11FD93F0323C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,4 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11FD93F0323C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5: dmi.product.name: MacBookPro11,4 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1487524/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1487919] Re: macbookrpro12, 1 fails to suspend
Confirmed still happens on the upstream kernel. In addition, a "shutdown" doesn't power down the machine -- the screen blacks, but the apple light stays on and need to force power off by holding down the power button for 5-10 seconds. ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1487919 Title: macbookrpro12,1 fails to suspend Status in linux package in Ubuntu: Confirmed Bug description: I've installed wily on a new macbookpro12,1 (2015 model), and suspending the system results in the screen going black and the apple light turning off, but the system is not fully asleep -- the 'force touch' pad still makes clicking feedback, and the machine continues to generate heat and spin fans if put into a bag. Once in this state, the machine cannot be woken up from the state its in either. did a "journalctl -f | tee sleep.log' while this was happening and got the following output -- let me know if there is a better way to figure out where things are going wrong: Aug 23 15:13:21 spiny NetworkManager[820]: sleep requested (sleeping: no enabled: yes) Aug 23 15:13:21 spiny NetworkManager[820]: sleeping... Aug 23 15:13:21 spiny NetworkManager[820]: (wlp3s0): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37] Aug 23 15:13:21 spiny NetworkManager[820]: (wlp3s0): deactivating device (reason 'sleeping') [37] Aug 23 15:13:21 spiny NetworkManager[820]: (wlp3s0): canceled DHCP transaction, DHCP client pid 925 Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for 2601:1c0:4d00:39e6:f912:fbb6:aaa6:4429 on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for 2601:1c0:4d00:39e6:290:4cff:fe0d:f43e on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Leaving mDNS multicast group on interface wlp3s0.IPv6 with address 2601:1c0:4d00:39e6:290:4cff:fe0d:f43e. Aug 23 15:13:21 spiny avahi-daemon[826]: Joining mDNS multicast group on interface wlp3s0.IPv6 with address fe80::290:4cff:fe0d:f43e. Aug 23 15:13:21 spiny avahi-daemon[826]: Registering new address record for fe80::290:4cff:fe0d:f43e on wlp3s0.*. Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for fe80::290:4cff:fe0d:f43e on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Leaving mDNS multicast group on interface wlp3s0.IPv6 with address fe80::290:4cff:fe0d:f43e. Aug 23 15:13:21 spiny avahi-daemon[826]: Interface wlp3s0.IPv6 no longer relevant for mDNS. Aug 23 15:13:21 spiny wpa_supplicant[891]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=10:c3:7b:c5:83:d8 reason=3 locally_generated=1 Aug 23 15:13:21 spiny wpa_supplicant[891]: nl80211: Was expecting local disconnect but got another disconnect event first Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for 192.168.1.83 on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Leaving mDNS multicast group on interface wlp3s0.IPv4 with address 192.168.1.83. Aug 23 15:13:21 spiny avahi-daemon[826]: Interface wlp3s0.IPv4 no longer relevant for mDNS. Aug 23 15:13:21 spiny kernel: cfg80211: Calling CRDA to update world regulatory domain Aug 23 15:13:21 spiny NetworkManager[820]: Writing DNS information to /sbin/resolvconf Aug 23 15:13:21 spiny dnsmasq[928]: setting upstream servers from DBus Aug 23 15:13:21 spiny dnsmasq[928]: using nameserver 2601:1c0:4d00:39e6::1#53 Aug 23 15:13:21 spiny dbus[806]: [system] Rejected send message, 10 matched rules; type="method_return", sender=":1.22" (uid=0 pid=928 comm="/usr/sbin/dnsmasq --no-resolv --keep-in-foreground") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.6" (uid=0 pid=820 comm="/usr/sbin/NetworkManager --no-daemon ") Aug 23 15:13:21 spiny wpa_supplicant[891]: p2p-dev-wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Aug 23 15:13:21 spiny NetworkManager[820]: Writing DNS information to /sbin/resolvconf Aug 23 15:13:21 spiny kernel: brcmf_cfg80211_reg_notifier: not a ISO3166 code Aug 23 15:13:21 spiny kernel: cfg80211: World regulatory domain updated: Aug 23 15:13:21 spiny kernel: cfg80211: DFS Master region: unset Aug 23 15:13:21 spiny kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) Aug 23 15:13:21 spiny kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (517 KHz - 525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (525 KHz - 533 KHz @ 8 KHz, 16 KHz
[Kernel-packages] [Bug 1487524] Re: Broadcom BCM43602 not seeing 5Ghz range
Still same issue on latest upstream kernel. ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1487524 Title: Broadcom BCM43602 not seeing 5Ghz range Status in linux package in Ubuntu: Incomplete Bug description: On a MacbookPro12,1 (2015 model), the wireless works with the brcmfmac on a wily install out of the box, but can't see any APs on the 5GHz range even though there are APs broadcasting on 5Ghz. 03:00.0 Network controller: Broadcom Corporation BCM43602 802.11ac Wireless LAN SoC (rev 01) Subsystem: Apple Inc. Device 0152 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: brcmfmac $ sudo iwlist wlp3s0 scan|grep Freq Frequency:2.412 GHz (Channel 1) Frequency:2.422 GHz (Channel 3) ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.1.0-3-generic 4.1.0-3.3 [modified: boot/vmlinuz-4.1.0-3-generic] ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: jbarnett 1545 F pulseaudio /dev/snd/controlC2: jbarnett 1545 F pulseaudio /dev/snd/controlC1: jbarnett 1545 F pulseaudio /dev/snd/controlC0: jbarnett 1545 F pulseaudio CurrentDesktop: GNOME Date: Fri Aug 21 08:46:15 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=dd225ec0-47f4-49d8-a51c-a2547f8eb945 InstallationDate: Installed on 2015-08-21 (0 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) MachineType: Apple Inc. MacBookPro11,4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-3-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.1.0-3-generic N/A linux-backports-modules-4.1.0-3-generic N/A linux-firmware 1.146 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B04.1506051511 dmi.board.name: Mac-06F11FD93F0323C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,4 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11FD93F0323C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5: dmi.product.name: MacBookPro11,4 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1487524/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1487524] Re: Broadcom BCM43602 not seeing 5Ghz range
** 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/1487524 Title: Broadcom BCM43602 not seeing 5Ghz range Status in linux package in Ubuntu: Confirmed Bug description: On a MacbookPro12,1 (2015 model), the wireless works with the brcmfmac on a wily install out of the box, but can't see any APs on the 5GHz range even though there are APs broadcasting on 5Ghz. 03:00.0 Network controller: Broadcom Corporation BCM43602 802.11ac Wireless LAN SoC (rev 01) Subsystem: Apple Inc. Device 0152 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: brcmfmac $ sudo iwlist wlp3s0 scan|grep Freq Frequency:2.412 GHz (Channel 1) Frequency:2.422 GHz (Channel 3) ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.1.0-3-generic 4.1.0-3.3 [modified: boot/vmlinuz-4.1.0-3-generic] ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: jbarnett 1545 F pulseaudio /dev/snd/controlC2: jbarnett 1545 F pulseaudio /dev/snd/controlC1: jbarnett 1545 F pulseaudio /dev/snd/controlC0: jbarnett 1545 F pulseaudio CurrentDesktop: GNOME Date: Fri Aug 21 08:46:15 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=dd225ec0-47f4-49d8-a51c-a2547f8eb945 InstallationDate: Installed on 2015-08-21 (0 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) MachineType: Apple Inc. MacBookPro11,4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-3-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.1.0-3-generic N/A linux-backports-modules-4.1.0-3-generic N/A linux-firmware 1.146 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B04.1506051511 dmi.board.name: Mac-06F11FD93F0323C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,4 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11FD93F0323C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5: dmi.product.name: MacBookPro11,4 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1487524/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1321824] [NEW] gpe16 interrupt using > 90% cpu in gmux_index_wait_ready.isra
Public bug reported: on a retina macbook pro (MacBookPro11,3), I recently* noticed >90% of cpu being used in kworker thread, similar to http://askubuntu.com/questions/444005/what-is-causing-ubuntu-on-macbook- pro-to-have-high-cpu-usage disabling the gpe16 interrupt restores cpu idleness, and the stack trace shows: # cat /proc/4/stack [] gmux_index_wait_ready.isra.7+0x47/0x70 [apple_gmux] [] gmux_index_write8+0x39/0x60 [apple_gmux] [] gmux_notify_handler+0xd5/0x119 [apple_gmux] [] acpi_ev_notify_dispatch+0x44/0x5c [] acpi_os_execute_deferred+0x14/0x20 [] process_one_work+0x182/0x450 [] worker_thread+0x121/0x410 [] kthread+0xd2/0xf0 [] ret_from_fork+0x7c/0xb0 [] 0x *"recently" being yesterday, when I started plugging in an external monitor via mindisplayport/thunderbolt port, and also started using the 3.13.0-27-generic kernel image ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-27-generic 3.13.0-27.50 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jbarnett 2982 F pulseaudio /dev/snd/controlC0: jbarnett 2982 F pulseaudio /dev/snd/controlC1: jbarnett 2982 F pulseaudio CurrentDesktop: GNOME Date: Wed May 21 09:25:40 2014 HibernationDevice: RESUME=UUID=948280a0-a059-468d-8484-f0d317f46e6d InstallationDate: Installed on 2014-02-24 (85 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140218) MachineType: Apple Inc. MacBookPro11,3 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic.efi.signed root=UUID=135fd833-3282-4f3b-8802-0a27ec2765b9 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-27-generic N/A linux-backports-modules-3.13.0-27-generic N/A linux-firmware 1.127.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/18/2013 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP112.88Z.0138.B02.1310181745 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-2BD1B31983FE1663 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,3 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-2BD1B31983FE1663 dmi.modalias: dmi:bvnAppleInc.:bvrMBP112.88Z.0138.B02.1310181745:bd10/18/2013:svnAppleInc.:pnMacBookPro11,3:pvr1.0:rvnAppleInc.:rnMac-2BD1B31983FE1663:rvrMacBookPro11,3:cvnAppleInc.:ct10:cvrMac-2BD1B31983FE1663: dmi.product.name: MacBookPro11,3 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug package-from-proposed 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/1321824 Title: gpe16 interrupt using > 90% cpu in gmux_index_wait_ready.isra Status in “linux” package in Ubuntu: New Bug description: on a retina macbook pro (MacBookPro11,3), I recently* noticed >90% of cpu being used in kworker thread, similar to http://askubuntu.com/questions/444005/what-is-causing-ubuntu-on- macbook-pro-to-have-high-cpu-usage disabling the gpe16 interrupt restores cpu idleness, and the stack trace shows: # cat /proc/4/stack [] gmux_index_wait_ready.isra.7+0x47/0x70 [apple_gmux] [] gmux_index_write8+0x39/0x60 [apple_gmux] [] gmux_notify_handler+0xd5/0x119 [apple_gmux] [] acpi_ev_notify_dispatch+0x44/0x5c [] acpi_os_execute_deferred+0x14/0x20 [] process_one_work+0x182/0x450 [] worker_thread+0x121/0x410 [] kthread+0xd2/0xf0 [] ret_from_fork+0x7c/0xb0 [] 0x *"recently" being yesterday, when I started plugging in an external monitor via mindisplayport/thunderbolt port, and also started using the 3.13.0-27-generic kernel image ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-27-generic 3.13.0-27.50 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jbarnett 2982 F pulseaudio /dev/snd/controlC0: jbarnett 2982 F pulseaudio /dev/snd/controlC1: jbarnett 2982 F pulseaudio CurrentDesktop: GNOME Date: Wed May 21 09:25:40 2014 HibernationDevice: RESUME=UUID=948280a0-a059-468d-8484-f0d317f46e6d InstallationDate: Installed on 2014-02-24 (85 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140218) MachineType: Apple Inc. MacBookPro11,3 ProcEnviron: TERM=xterm PATH=(cus
[Kernel-packages] [Bug 1287984] [NEW] unable to use macbook pro retina webcam
Public bug reported: cheese, google hangouts plugin, etc can't find a camera. according to http://mactaris.blogspot.co.uk/2013/07/webcam-settings-20-will-support.html , the camera is no longer a UVC device, but on the PCIe bus instead. lspci -vvv shows: 04:00.0 Multimedia controller: Broadcom Corporation Device 1570 Subsystem: Broadcom Corporation Device 1570 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [ac] Express (v2) Endpoint, MSI 00 DevCap: MaxPayload 512 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag- PhantFunc- AuxPwr+ NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- TransPend- LnkCap: Port #0, Speed 5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <2us, L1 <32us ClockPM+ Surprise- LLActRep- BwNot- LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Range ABCD, TimeoutDis+, LTR+, OBFF Via WAKE# DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Disabled LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [100 v1] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn- Capabilities: [13c v1] Device Serial Number 00-00-00-ff-ff-00-00-00 Capabilities: [150 v1] Power Budgeting Capabilities: [160 v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb:Fixed- WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0:Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb:Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=ff Status: NegoPending- InProgress- Capabilities: [1b0 v1] Latency Tolerance Reporting Max snoop latency: 71680ns Max no snoop latency: 71680ns Capabilities: [220 v1] #15 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-15-generic 3.13.0-15.35 ProcVersionSignature: Ubuntu 3.13.0-15.35-generic 3.13.5 Uname: Linux 3.13.0-15-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jbarnett 2348 F pulseaudio /dev/snd/controlC0: jbarnett 2348 F pulseaudio /dev/snd/pcmC0D0c: jbarnett 2348 F...m pulseaudio /dev/snd/pcmC0D0p: jbarnett 2348 F...m pulseaudio CurrentDesktop: GNOME Date: Tue Mar 4 16:25:48 2014 HibernationDevice: RESUME=UUID=948280a0-a059-468d-8484-f0d317f46e6d InstallationDate: Installed on 2014-02-24 (8 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140218) MachineType: Apple Inc. MacBookPro11,3 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-15-generic.efi.signed root=UUID=135fd833-3282-4f3b-8802-0a27ec2765b9 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-15-generic N/A linux-backports-modules-3.13.0-15-generic N/A linux-firmware 1.125 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/18/2013 dmi.bios.vendor: Apple Inc. dm
[Kernel-packages] [Bug 1289884] [NEW] wireless doesn't associate after waking from suspend
Public bug reported: on a macbook pro retina, the wireless often doesn't work after waking from suspend. sometimes combinations of unloading and reloading kernel modules and restarting network-manager works; other times i need to reboot before I can reconnect to the wireless. here's syslog after a network-manager restart during one of the times i needed to reboot. Mar 8 13:38:42 leafy ModemManager[833]: Caught signal, shutting down... Mar 8 13:38:42 leafy ModemManager[833]: ModemManager is shut down Mar 8 13:38:42 leafy ModemManager[4223]: ModemManager (version 1.0.0) starting... Mar 8 13:38:42 leafy NetworkManager[4230]: NetworkManager (version 0.9.8.8) is starting... Mar 8 13:38:42 leafy NetworkManager[4230]: Read config file /etc/NetworkManager/NetworkManager.conf Mar 8 13:38:42 leafy NetworkManager[4230]: WEXT support is enabled Mar 8 13:38:42 leafy NetworkManager[4230]: VPN: loaded org.freedesktop.NetworkManager.pptp Mar 8 13:38:42 leafy NetworkManager[4230]: DNS: loaded plugin dnsmasq Mar 8 13:38:42 leafy NetworkManager[4230]:SCPlugin-Ifupdown: init! Mar 8 13:38:42 leafy NetworkManager[4230]:SCPlugin-Ifupdown: update_system_hostname Mar 8 13:38:42 leafy NetworkManager[4230]: interface-parser: parsing file /etc/network/interfaces Mar 8 13:38:42 leafy NetworkManager[4230]: interface-parser: finished parsing file /etc/network/interf aces Mar 8 13:38:42 leafy NetworkManager[4230]:SCPluginIfupdown: management mode: unmanaged Mar 8 13:38:42 leafy NetworkManager[4230]:SCPlugin-Ifupdown: devices added (path: /sys/devices/pci:0 0/:00:1c.2/:03:00.0/net/wlan0, iface: wlan0) Mar 8 13:38:42 leafy NetworkManager[4230]:SCPlugin-Ifupdown: device added (path: /sys/devices/pci:00 /:00:1c.2/:03:00.0/net/wlan0, iface: wlan0): no ifupdown configuration found. Mar 8 13:38:42 leafy NetworkManager[4230]:SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/n et/lo, iface: lo) Mar 8 13:38:42 leafy NetworkManager[4230]:SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/ne t/lo, iface: lo): no ifupdown configuration found. Mar 8 13:38:42 leafy NetworkManager[4230]:SCPlugin-Ifupdown: end _init. Mar 8 13:38:42 leafy NetworkManager[4230]: Loaded plugin ifupdown: (C) 2008 Canonical Ltd. To report bugs please use the NetworkManager mailing list. Mar 8 13:38:42 leafy NetworkManager[4230]: Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc. To r eport bugs please use the NetworkManager mailing list. Mar 8 13:38:42 leafy NetworkManager[4230]:SCPlugin-Ofono: Acquired D-Bus service com.canonical.NMOfono Mar 8 13:38:42 leafy NetworkManager[4230]:SCPlugin-Ofono: init! Mar 8 13:38:42 leafy NetworkManager[4230]:SCPlugin-Ofono: end _init. Mar 8 13:38:42 leafy NetworkManager[4230]: Loaded plugin (null): (null) Mar 8 13:38:42 leafy NetworkManager[4230]:Ifupdown: get unmanaged devices count: 0 Mar 8 13:38:42 leafy NetworkManager[4230]:SCPlugin-Ifupdown: (13606448) ... get_connections. Mar 8 13:38:42 leafy NetworkManager[4230]:SCPlugin-Ifupdown: (13606448) ... get_connections (managed=fal se): return empty list. Mar 8 13:38:42 leafy NetworkManager[4230]:keyfile: parsing HKGJ3 ... Mar 8 13:38:42 leafy NetworkManager[4230]:keyfile: read connection 'HKGJ3' Mar 8 13:38:42 leafy NetworkManager[4230]:keyfile: parsing Marin Secure ... Mar 8 13:38:42 leafy NetworkManager[4230]:keyfile: read connection 'Marin Secure' Mar 8 13:38:42 leafy NetworkManager[4230]:SCPlugin-Ofono: (67124512) ... get_connections. Mar 8 13:38:42 leafy NetworkManager[4230]:SCPlugin-Ofono: (67124512) connections count: 0 Mar 8 13:38:42 leafy NetworkManager[4230]:Ifupdown: get unmanaged devices count: 0 Mar 8 13:38:42 leafy NetworkManager[4230]: monitoring kernel firmware directory '/lib/firmware'. Mar 8 13:38:42 leafy NetworkManager[4230]: rfkill3: found WiFi radio killswitch (at /sys/devices/pci0 000:00/:00:1c.2/:03:00.0/ieee80211/phy0/rfkill3) (driver wl) Mar 8 13:38:42 leafy NetworkManager[4230]: rfkill4: found WiFi radio killswitch (at /sys/devices/pci0 000:00/:00:1c.2/:03:00.0/net/wlan0/rfkill4) (driver wl) Mar 8 13:38:42 leafy NetworkManager[4230]: WiFi enabled by radio killswitch; enabled by state file Mar 8 13:38:42 leafy NetworkManager[4230]: WWAN enabled by radio killswitch; enabled by state file Mar 8 13:38:42 leafy NetworkManager[4230]: WiMAX enabled by radio killswitch; enabled by state file Mar 8 13:38:42 leafy NetworkManager[4230]: Networking is enabled by state file Mar 8 13:38:42 leafy NetworkManager[4230]: (wlan0): using nl80211 for WiFi device control Mar 8 13:38:42 leafy NetworkManager[4230]: (wlan0): new 802.11 WiFi device (driver: 'wl' ifindex: 3) Mar 8 13:38:42 leafy NetworkManager[4230]: (wlan0): exported as /org/freedesktop/NetworkManager/Devic es/0 Mar 8 13:38:42 leafy NetworkManager[423
