[Kernel-packages] [Bug 1827428] Re: Mouse cursor left frozen copy of itself
A bit more detail to reproduce this that I think was missed out before: It happens when the configured desktop mode/scaling is set to a fractional value. You can have that experimental xrandr setting set, but be configured to scaling of 100% or 200% (but see below on latter) and you won't see this problem. Set it to 150%, log out, log in again, you should see it. That applies to my experience anyway on the AMD graphics system. NB: Today when I tried to confirm this, I found that it would ignore my setting scaling to 200% on login, and would instead go in as if it was 100%, which would also be what it showed in the display settings dialogue itself. I'm pretty sure that wasn't the case earlier. I am able to select and use 200% in the session, it just won't be remembered. This sounds like a separate problem though. The problem *here* is what happens when scaling is set to a fractional value like 150% (which it does seem to have no problem remembering). It also means that a kind of workaround is to set scaling to 200% or 100% before logging out, then set it back to the 150% you want after logging in again. The problem is only when you're logging in and the setting is already fractional, so the switch in resolution happens during login. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1827428 Title: Mouse cursor left frozen copy of itself Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Mouse cursor left freezed copy of itself over all the windows after login after lock screen. Functionality is not broken. It's just not aesthetic. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 2 16:10:09 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 630 [103c:8392] NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Mobile] [103c:8392] InstallationDate: Installed on 2019-04-29 (2 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 04f2:b593 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP OMEN by HP Laptop 17-an0xx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=08661a81-0386-4b44-9d3e-17ad6fa2de96 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/21/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.05 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8392 dmi.board.vendor: HP dmi.board.version: 40.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.05:bd06/21/2017:svnHP:pnOMENbyHPLaptop17-an0xx:pvr:rvnHP:rn8392:rvr40.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-an0xx dmi.product.sku: 2FP35EA#ACB dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 versio
[Kernel-packages] [Bug 1827428] Re: [nvidia] Mouse cursor left frozen copy of itself
My bug got marked a duplicate of this one but with the latest change that might be wrong: It affected me on a machine with AMD graphics, not nVidia. BTW I recently tried it again on the offchance it had been fixed since (by re-enabling the xrandr scaling setting), and it had not. Also not fixed on 19.10 (which tbh is barely advanced from 19.04 at this stage). On the flipside, a different machine with only Intel graphics (Dell XPS 9370) did *not* show this problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1827428 Title: [nvidia] Mouse cursor left frozen copy of itself Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Mouse cursor left freezed copy of itself over all the windows after login after lock screen. Functionality is not broken. It's just not aesthetic. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 2 16:10:09 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 630 [103c:8392] NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Mobile] [103c:8392] InstallationDate: Installed on 2019-04-29 (2 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 04f2:b593 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP OMEN by HP Laptop 17-an0xx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=08661a81-0386-4b44-9d3e-17ad6fa2de96 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/21/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.05 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8392 dmi.board.vendor: HP dmi.board.version: 40.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.05:bd06/21/2017:svnHP:pnOMENbyHPLaptop17-an0xx:pvr:rvnHP:rn8392:rvr40.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-an0xx dmi.product.sku: 2FP35EA#ACB dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831070] Re: package nvidia-dkms-390 390.116-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status
NB: Post-upgrade upgraded to nvidia-driver-418 from restricted (didn't re-enable graphics-drivers ppa) and all so far seems well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1831070 Title: package nvidia-dkms-390 390.116-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 1 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: Just happened trying to upgrade a machine in two immediate steps bionic->cosmic->disco. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: nvidia-dkms-390 390.116-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-20.21-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Thu May 30 12:58:24 2019 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-02-20 (463 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.6ubuntu1 apt 1.8.1 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.116-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to disco on 2019-05-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1831070/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831070] [NEW] package nvidia-dkms-390 390.116-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit stat
Public bug reported: Just happened trying to upgrade a machine in two immediate steps bionic->cosmic->disco. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: nvidia-dkms-390 390.116-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-20.21-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Thu May 30 12:58:24 2019 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-02-20 (463 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.6ubuntu1 apt 1.8.1 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.116-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to disco on 2019-05-30 (0 days ago) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1831070 Title: package nvidia-dkms-390 390.116-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 1 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: Just happened trying to upgrade a machine in two immediate steps bionic->cosmic->disco. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: nvidia-dkms-390 390.116-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-20.21-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Thu May 30 12:58:24 2019 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-02-20 (463 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.6ubuntu1 apt 1.8.1 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.116-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to disco on 2019-05-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1831070/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)
I hid my earlier posts because I reckoned they were noise, tbh. This one less so. :-) I have replaced the firmware files with those from the windows driver as described above and in the linked-to askubuntu. It worked brilliantly for a few days, no problems at all, but just now failed: Similar to what I found with btusb.enable_autosuspend=n, after one more sleep/wake cycle it came up with both bluetooth *and* wifi interfaces absent. It does at least replicate my earlier findings, that now when it fails, it kills *both* interfaces, not just bluetooth. Maybe that points to a slightly different cause. And at least it does happen far less frequently. Still, the recovery remains to reboot into bios and switch both interfaces off and on again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766825 Title: Bluetooth issues with Dell XPS 13 (9370) Status in Dell Sputnik: Triaged Status in linux package in Ubuntu: Confirmed Bug description: I have the following problem with my Bluetooth module on my new Dell XPS 13 (9370) with Ubuntu preinstalled. The bluetooth module gets disabled for some reason. The bluetooth devices (keyboard and mouse) just stop working in the middle of the work, the Bluetooth indicator goes away and the module is also gone in the rfkill list. To get it back working I need to reboot the machine, start the BIOS, disable the Bluetooth module and re-enable it or I have to turn the machine completely off and on again. After that, the bluetooth module is available again. That's pretty annoying. My syslog when this happens: Apr 11 12:25:45 visyu-albatross kernel: [ 2513.913725] usb 1-7: USB disconnect, device number 3 Apr 11 12:25:45 visyu-albatross acpid: input device has been disconnected, fd 22 Apr 11 12:25:46 visyu-albatross systemd[1]: Starting Load/Save RF Kill Switch Status... Apr 11 12:25:46 visyu-albatross systemd[1]: Started Load/Save RF Kill Switch Status. Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c9 of user root. Apr 11 12:25:46 visyu-albatross acpid: input device has been disconnected, fd 21 Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Timers. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Paths. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Default. Apr 11 12:25:46 visyu-albatross systemd[12109]: Startup finished in 15ms. Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0. Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSource Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSink Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Default. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Shutdown. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Paths. Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[12109]: Starting Exit the Session... Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Timers. Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c10 of user root. Apr 11 12:25:46 visyu-albatross systemd[12109]: Received SIGRTMIN+24 from PID 12120 (kill). Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Timers. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Paths. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Default. Apr 11 12:25:46 visyu-albatross systemd[12123]: Startup finished in 14ms. Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0. Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Shutdown. Apr 11 12:25:46 visyu-albatross systemd[12123]: Starting Exit the Session... Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Default. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Basi
[Kernel-packages] [Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)
typically it waited for me to report that it worked before failing. Proving a negative blah indeed. This time my wifi adapter also didn't come back. I suspect this isn't entirely unrelated as aren't they actually the same physical device? In fact that almost makes it weird that usually *only* bluetooth fails to resume. Also, I had that happen exactly once before, on the stock Ubuntu kernel, so I don't think that's a 4.16 mainline 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/1766825 Title: Bluetooth issues with Dell XPS 13 (9370) Status in Dell Sputnik: Triaged Status in linux package in Ubuntu: Confirmed Bug description: I have the following problem with my Bluetooth module on my new Dell XPS 13 (9370) with Ubuntu preinstalled. The bluetooth module gets disabled for some reason. The bluetooth devices (keyboard and mouse) just stop working in the middle of the work, the Bluetooth indicator goes away and the module is also gone in the rfkill list. To get it back working I need to reboot the machine, start the BIOS, disable the Bluetooth module and re-enable it or I have to turn the machine completely off and on again. After that, the bluetooth module is available again. That's pretty annoying. My syslog when this happens: Apr 11 12:25:45 visyu-albatross kernel: [ 2513.913725] usb 1-7: USB disconnect, device number 3 Apr 11 12:25:45 visyu-albatross acpid: input device has been disconnected, fd 22 Apr 11 12:25:46 visyu-albatross systemd[1]: Starting Load/Save RF Kill Switch Status... Apr 11 12:25:46 visyu-albatross systemd[1]: Started Load/Save RF Kill Switch Status. Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c9 of user root. Apr 11 12:25:46 visyu-albatross acpid: input device has been disconnected, fd 21 Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Timers. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Paths. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Default. Apr 11 12:25:46 visyu-albatross systemd[12109]: Startup finished in 15ms. Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0. Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSource Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSink Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Default. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Shutdown. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Paths. Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[12109]: Starting Exit the Session... Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Timers. Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c10 of user root. Apr 11 12:25:46 visyu-albatross systemd[12109]: Received SIGRTMIN+24 from PID 12120 (kill). Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Timers. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Paths. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Default. Apr 11 12:25:46 visyu-albatross systemd[12123]: Startup finished in 14ms. Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0. Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Shutdown. Apr 11 12:25:46 visyu-albatross systemd[12123]: Starting Exit the Session... Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Default. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Timers. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Paths. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12123]: Received SIGRTMIN+24 from PI
[Kernel-packages] [Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)
Catching up as I came at this from another direction. Having got a Windows-installed XPS 13 9370 and installed 18.04 freshly on it itself, its default suspend mode is s2idle, which means lots of battery life gets lost while suspended. But no bluetooth problems. See askubuntu: https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no- longer-suspends-on-lid-close?newreg=c37c6aa8b9c94d578157bc0835fe0286 for more about that. But when I applied the working fix for that I encountered the problem described here. I've done some different looking around and found this, a Fedora bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1514836 wherein it looks like they may have fixed it for the XPS 13 9360, and that fix is upstream and I guess will appear in 4.17. However that would need to be amended to take in the 9370 too, as it looks like being the same issue. Currently I'm running the workaround described earlier in that bug report, to use the kernel parameter btusb.enable_autosuspend=n (actually I'm doing it with "options btusb enable_autosuspend=n" in a file in /etc/modprobe.d); but that kernel option only arrived in 4.16 so I'm running the 4.16 mainline kernel to get it. It *appears* to be working, with bluetooth having survived a couple of deep sleeps so far this morning, but I haven't been running it very long to be sure. (Proving a negative blah.) But this is a lesser workaround, as I understand it, telling the bt adapter not to go to sleep during deep sleep, rather than, presumably preferably, letting it sleep but waking it up thoroughly afterwards, which is the suspend-resume fix. I think what we probably want is that fix from Redhat that's in btusb.c in kernel head now, to also be applied to 9370. And then for us to get that kernel! Either presumably when the -hwe kernels start, or Dell can push one out, or anyway in 18.10. ** Bug watch added: Red Hat Bugzilla #1514836 https://bugzilla.redhat.com/show_bug.cgi?id=1514836 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766825 Title: Bluetooth issues with Dell XPS 13 (9370) Status in Dell Sputnik: Triaged Status in linux package in Ubuntu: Confirmed Bug description: I have the following problem with my Bluetooth module on my new Dell XPS 13 (9370) with Ubuntu preinstalled. The bluetooth module gets disabled for some reason. The bluetooth devices (keyboard and mouse) just stop working in the middle of the work, the Bluetooth indicator goes away and the module is also gone in the rfkill list. To get it back working I need to reboot the machine, start the BIOS, disable the Bluetooth module and re-enable it or I have to turn the machine completely off and on again. After that, the bluetooth module is available again. That's pretty annoying. My syslog when this happens: Apr 11 12:25:45 visyu-albatross kernel: [ 2513.913725] usb 1-7: USB disconnect, device number 3 Apr 11 12:25:45 visyu-albatross acpid: input device has been disconnected, fd 22 Apr 11 12:25:46 visyu-albatross systemd[1]: Starting Load/Save RF Kill Switch Status... Apr 11 12:25:46 visyu-albatross systemd[1]: Started Load/Save RF Kill Switch Status. Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c9 of user root. Apr 11 12:25:46 visyu-albatross acpid: input device has been disconnected, fd 21 Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Timers. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Paths. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Default. Apr 11 12:25:46 visyu-albatross systemd[12109]: Startup finished in 15ms. Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0. Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSource Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSink Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Default. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Shutdown. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Paths. Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[12109]: Starting Exit the Session... A
[Kernel-packages] [Bug 1299790] Re: [Apple Inc. MacBookAir4, 1] suspend/resume failure [non-free: wl]
My problem definitely was rEFInd; and i resolved it by using the new --ownhfs install option as discussed on their discussion forum. However I don't have hibernate working at all on the linux side, so it may be that for you too. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1299790 Title: [Apple Inc. MacBookAir4,1] suspend/resume failure [non-free: wl] Status in “linux” package in Ubuntu: Incomplete Bug description: I had shut the lid to suspend the system last night. *After that* I plugged in the mains lead. Today I unplugged the mains lead and *then* opened the lid, and tried to wake it, only to find it wouldn't do so. Had to force-reboot it. On logging into desktop, this bug report got triggered. It had been through some suspend/resume cycles already (not many; i only installed it on Friday), so the mains-plug behaviour is where I suspect the problem is. (Until now Trusty has been behaving impeccably on this laptop. :-) ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-20-generic 3.13.0-20.42 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: wl Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm1226 F pulseaudio rachel 1832 F pulseaudio CRDA: country EU: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5710 @ 40), (N/A, 27), DFS Date: Sun Mar 30 15:54:36 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2014-03-28 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64+mac (20140326) InterpreterPath: /usr/bin/python3.4 MachineType: Apple Inc. MacBookAir4,1 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: \boot\vmlinuz-3.13.0-20-generic root=UUID=c2167b45-d81a-4d7f-9017-36858344eef8 ro quiet splash vt.handoff=7 initrd=boot\initrd.img-3.13.0-20-generic PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-20-generic N/A linux-backports-modules-3.13.0-20-generic N/A linux-firmware 1.126 SourcePackage: linux Title: [Apple Inc. MacBookAir4,1] suspend/resume failure [non-free: wl] UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/24/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B0F.1201241549 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C08A6BB70A942AC2 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C08A6BB70A942AC2 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B0F.1201241549:bd01/24/2012:svnAppleInc.:pnMacBookAir4,1:pvr1.0:rvnAppleInc.:rnMac-C08A6BB70A942AC2:rvrMacBookAir4,1:cvnAppleInc.:ct10:cvrMac-C08A6BB70A942AC2: dmi.product.name: MacBookAir4,1 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/1299790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1299790] Re: [Apple Inc. MacBookAir4, 1] suspend/resume failure [non-free: wl]
On further googling the problem may lie with rEFInd. It looks like the problem discussed here: http://askubuntu.com/questions/295105/refind- breaks-standby-mode-on-macbook-air-5-2 Am currently running without rEFInd (though it does mean having to select "Windows" to boot Linux, which isn't pretty!) to confirm the problem disappears with rEFInd not in the mix. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1299790 Title: [Apple Inc. MacBookAir4,1] suspend/resume failure [non-free: wl] Status in “linux” package in Ubuntu: Incomplete Bug description: I had shut the lid to suspend the system last night. *After that* I plugged in the mains lead. Today I unplugged the mains lead and *then* opened the lid, and tried to wake it, only to find it wouldn't do so. Had to force-reboot it. On logging into desktop, this bug report got triggered. It had been through some suspend/resume cycles already (not many; i only installed it on Friday), so the mains-plug behaviour is where I suspect the problem is. (Until now Trusty has been behaving impeccably on this laptop. :-) ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-20-generic 3.13.0-20.42 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: wl Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm1226 F pulseaudio rachel 1832 F pulseaudio CRDA: country EU: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5710 @ 40), (N/A, 27), DFS Date: Sun Mar 30 15:54:36 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2014-03-28 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64+mac (20140326) InterpreterPath: /usr/bin/python3.4 MachineType: Apple Inc. MacBookAir4,1 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: \boot\vmlinuz-3.13.0-20-generic root=UUID=c2167b45-d81a-4d7f-9017-36858344eef8 ro quiet splash vt.handoff=7 initrd=boot\initrd.img-3.13.0-20-generic PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-20-generic N/A linux-backports-modules-3.13.0-20-generic N/A linux-firmware 1.126 SourcePackage: linux Title: [Apple Inc. MacBookAir4,1] suspend/resume failure [non-free: wl] UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/24/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B0F.1201241549 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C08A6BB70A942AC2 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C08A6BB70A942AC2 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B0F.1201241549:bd01/24/2012:svnAppleInc.:pnMacBookAir4,1:pvr1.0:rvnAppleInc.:rnMac-C08A6BB70A942AC2:rvrMacBookAir4,1:cvnAppleInc.:ct10:cvrMac-C08A6BB70A942AC2: dmi.product.name: MacBookAir4,1 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/1299790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1299790] Re: [Apple Inc. MacBookAir4, 1] suspend/resume failure [non-free: wl]
odd coda to add here: Today I've been back using the Mac side of this computer. So far two out of two times, I've seen the same problem resuming from suspend in Mac OS X; requiring the same power cycle to continue. I don't know what to make of this. It never did this before I made this machine dual-boot, but given we're talking about *suspend* as opposed to say, hibernate, I have no idea why this should be related at all. Maybe just a complete coincidence of an unrelated but similar *looking* issue. But I reckoned I'd record the observation here, in case it means something to someone. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1299790 Title: [Apple Inc. MacBookAir4,1] suspend/resume failure [non-free: wl] Status in “linux” package in Ubuntu: Incomplete Bug description: I had shut the lid to suspend the system last night. *After that* I plugged in the mains lead. Today I unplugged the mains lead and *then* opened the lid, and tried to wake it, only to find it wouldn't do so. Had to force-reboot it. On logging into desktop, this bug report got triggered. It had been through some suspend/resume cycles already (not many; i only installed it on Friday), so the mains-plug behaviour is where I suspect the problem is. (Until now Trusty has been behaving impeccably on this laptop. :-) ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-20-generic 3.13.0-20.42 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: wl Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm1226 F pulseaudio rachel 1832 F pulseaudio CRDA: country EU: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5710 @ 40), (N/A, 27), DFS Date: Sun Mar 30 15:54:36 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2014-03-28 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64+mac (20140326) InterpreterPath: /usr/bin/python3.4 MachineType: Apple Inc. MacBookAir4,1 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: \boot\vmlinuz-3.13.0-20-generic root=UUID=c2167b45-d81a-4d7f-9017-36858344eef8 ro quiet splash vt.handoff=7 initrd=boot\initrd.img-3.13.0-20-generic PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-20-generic N/A linux-backports-modules-3.13.0-20-generic N/A linux-firmware 1.126 SourcePackage: linux Title: [Apple Inc. MacBookAir4,1] suspend/resume failure [non-free: wl] UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/24/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B0F.1201241549 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C08A6BB70A942AC2 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C08A6BB70A942AC2 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B0F.1201241549:bd01/24/2012:svnAppleInc.:pnMacBookAir4,1:pvr1.0:rvnAppleInc.:rnMac-C08A6BB70A942AC2:rvrMacBookAir4,1:cvnAppleInc.:ct10:cvrMac-C08A6BB70A942AC2: dmi.product.name: MacBookAir4,1 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/1299790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1301524] Re: Missing EFI Stub Loader support in 3.13.0-21?
3.13.0-22 boots fine with stubloader. So the main interest in wanting to understand why 3.13.0.21 didn't, is to stop it happening again, otherwise it's history... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1301524 Title: Missing EFI Stub Loader support in 3.13.0-21? Status in “linux” package in Ubuntu: Incomplete Bug description: I think that might be the problem: Installed on a Mac (Macbook Air 4,1) using rEFInd boot manager, 3.13.0-19 and 3.13.0-20 as well as 3.14 (mainline, installed to test something else) all happily booted directly using the stubloader. But 3.13.0-21 just hangs instantly on load. Googling around found an older Arch thread where apparently something similar happened to a 3.7 kernel build and that was what it turned out to be: https://bbs.archlinux.org/viewtopic.php?id=156670&p=1 so guessing it might just be a build or build-script error? Kernel boots fine via grub (though this takes longer). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-generic 3.13.0.21.25 ProcVersionSignature: Ubuntu 3.13.0-21.43-generic 3.13.8 Uname: Linux 3.13.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rachel 1869 F pulseaudio CRDA: country EU: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5710 @ 40), (N/A, 27), DFS CurrentDesktop: Unity Date: Wed Apr 2 18:36:49 2014 InstallationDate: Installed on 2014-03-28 (4 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64+mac (20140326) MachineType: Apple Inc. MacBookAir4,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-21-generic root=UUID=c2167b45-d81a-4d7f-9017-36858344eef8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-21-generic N/A linux-backports-modules-3.13.0-21-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/24/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B0F.1201241549 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C08A6BB70A942AC2 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C08A6BB70A942AC2 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B0F.1201241549:bd01/24/2012:svnAppleInc.:pnMacBookAir4,1:pvr1.0:rvnAppleInc.:rnMac-C08A6BB70A942AC2:rvrMacBookAir4,1:cvnAppleInc.:ct10:cvrMac-C08A6BB70A942AC2: dmi.product.name: MacBookAir4,1 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/1301524/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1301524] Re: Missing EFI Stub Loader support in 3.13.0-21?
I just installed rEFInd on a UEFI PC also running Ubuntu Trusty. (built around Asus Z87I-PRO mobo). rEFInd had no trouble booting the same kernel (3.13.0-21) that I reported this problem for on the Mac. Entirely default configuration. (The Mac's rEFInd has an almost entirely default configuration too - just the line to enable scanning for linux kernels uncommented, which is uncommented on Linux by default.) So it looks like this may be Mac specific. Unfortunately (as it'll be harder to test). But Mac specific *and* specific to that one 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/1301524 Title: Missing EFI Stub Loader support in 3.13.0-21? Status in “linux” package in Ubuntu: Incomplete Bug description: I think that might be the problem: Installed on a Mac (Macbook Air 4,1) using rEFInd boot manager, 3.13.0-19 and 3.13.0-20 as well as 3.14 (mainline, installed to test something else) all happily booted directly using the stubloader. But 3.13.0-21 just hangs instantly on load. Googling around found an older Arch thread where apparently something similar happened to a 3.7 kernel build and that was what it turned out to be: https://bbs.archlinux.org/viewtopic.php?id=156670&p=1 so guessing it might just be a build or build-script error? Kernel boots fine via grub (though this takes longer). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-generic 3.13.0.21.25 ProcVersionSignature: Ubuntu 3.13.0-21.43-generic 3.13.8 Uname: Linux 3.13.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rachel 1869 F pulseaudio CRDA: country EU: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5710 @ 40), (N/A, 27), DFS CurrentDesktop: Unity Date: Wed Apr 2 18:36:49 2014 InstallationDate: Installed on 2014-03-28 (4 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64+mac (20140326) MachineType: Apple Inc. MacBookAir4,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-21-generic root=UUID=c2167b45-d81a-4d7f-9017-36858344eef8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-21-generic N/A linux-backports-modules-3.13.0-21-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/24/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B0F.1201241549 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C08A6BB70A942AC2 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C08A6BB70A942AC2 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B0F.1201241549:bd01/24/2012:svnAppleInc.:pnMacBookAir4,1:pvr1.0:rvnAppleInc.:rnMac-C08A6BB70A942AC2:rvrMacBookAir4,1:cvnAppleInc.:ct10:cvrMac-C08A6BB70A942AC2: dmi.product.name: MacBookAir4,1 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/1301524/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1301524] Re: Missing EFI Stub Loader support in 3.13.0-21?
Tested both. *Both* of them boot fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1301524 Title: Missing EFI Stub Loader support in 3.13.0-21? Status in “linux” package in Ubuntu: Incomplete Bug description: I think that might be the problem: Installed on a Mac (Macbook Air 4,1) using rEFInd boot manager, 3.13.0-19 and 3.13.0-20 as well as 3.14 (mainline, installed to test something else) all happily booted directly using the stubloader. But 3.13.0-21 just hangs instantly on load. Googling around found an older Arch thread where apparently something similar happened to a 3.7 kernel build and that was what it turned out to be: https://bbs.archlinux.org/viewtopic.php?id=156670&p=1 so guessing it might just be a build or build-script error? Kernel boots fine via grub (though this takes longer). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-generic 3.13.0.21.25 ProcVersionSignature: Ubuntu 3.13.0-21.43-generic 3.13.8 Uname: Linux 3.13.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rachel 1869 F pulseaudio CRDA: country EU: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5710 @ 40), (N/A, 27), DFS CurrentDesktop: Unity Date: Wed Apr 2 18:36:49 2014 InstallationDate: Installed on 2014-03-28 (4 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64+mac (20140326) MachineType: Apple Inc. MacBookAir4,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-21-generic root=UUID=c2167b45-d81a-4d7f-9017-36858344eef8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-21-generic N/A linux-backports-modules-3.13.0-21-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/24/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B0F.1201241549 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C08A6BB70A942AC2 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C08A6BB70A942AC2 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B0F.1201241549:bd01/24/2012:svnAppleInc.:pnMacBookAir4,1:pvr1.0:rvnAppleInc.:rnMac-C08A6BB70A942AC2:rvrMacBookAir4,1:cvnAppleInc.:ct10:cvrMac-C08A6BB70A942AC2: dmi.product.name: MacBookAir4,1 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/1301524/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1301524] [NEW] Missing EFI Stub Loader support in 3.13.0-21?
Public bug reported: I think that might be the problem: Installed on a Mac (Macbook Air 4,1) using rEFInd boot manager, 3.13.0-19 and 3.13.0-20 as well as 3.14 (mainline, installed to test something else) all happily booted directly using the stubloader. But 3.13.0-21 just hangs instantly on load. Googling around found an older Arch thread where apparently something similar happened to a 3.7 kernel build and that was what it turned out to be: https://bbs.archlinux.org/viewtopic.php?id=156670&p=1 so guessing it might just be a build or build-script error? Kernel boots fine via grub (though this takes longer). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-generic 3.13.0.21.25 ProcVersionSignature: Ubuntu 3.13.0-21.43-generic 3.13.8 Uname: Linux 3.13.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rachel 1869 F pulseaudio CRDA: country EU: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5710 @ 40), (N/A, 27), DFS CurrentDesktop: Unity Date: Wed Apr 2 18:36:49 2014 InstallationDate: Installed on 2014-03-28 (4 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64+mac (20140326) MachineType: Apple Inc. MacBookAir4,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-21-generic root=UUID=c2167b45-d81a-4d7f-9017-36858344eef8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-21-generic N/A linux-backports-modules-3.13.0-21-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/24/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B0F.1201241549 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C08A6BB70A942AC2 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C08A6BB70A942AC2 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B0F.1201241549:bd01/24/2012:svnAppleInc.:pnMacBookAir4,1:pvr1.0:rvnAppleInc.:rnMac-C08A6BB70A942AC2:rvrMacBookAir4,1:cvnAppleInc.:ct10:cvrMac-C08A6BB70A942AC2: dmi.product.name: MacBookAir4,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1301524 Title: Missing EFI Stub Loader support in 3.13.0-21? Status in “linux” package in Ubuntu: New Bug description: I think that might be the problem: Installed on a Mac (Macbook Air 4,1) using rEFInd boot manager, 3.13.0-19 and 3.13.0-20 as well as 3.14 (mainline, installed to test something else) all happily booted directly using the stubloader. But 3.13.0-21 just hangs instantly on load. Googling around found an older Arch thread where apparently something similar happened to a 3.7 kernel build and that was what it turned out to be: https://bbs.archlinux.org/viewtopic.php?id=156670&p=1 so guessing it might just be a build or build-script error? Kernel boots fine via grub (though this takes longer). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-generic 3.13.0.21.25 ProcVersionSignature: Ubuntu 3.13.0-21.43-generic 3.13.8 Uname: Linux 3.13.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rachel 1869 F pulseaudio CRDA: country EU: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5710 @ 40), (N/A, 27), DFS CurrentDesktop: Unity Date: Wed Apr 2 18:36:49 2014 InstallationDate: Installed on 2014-03-28 (4 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64+mac (20140326) MachineType: Apple Inc. MacBookAir4,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-21-generic root=UUID=c2167b45-d81a-4d7f-9017-36858344eef8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-21-generic N/A linux-backports-modules-3.13.0-21-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/24/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B0F.1201241549 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C08A6BB70A942AC2 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi
[Kernel-packages] [Bug 1299790] Re: [Apple Inc. MacBookAir4, 1] suspend/resume failure [non-free: wl]
OK, it happened on 3.14. Confirmed that, as with the first time, the pattern was close lid (observe backlight goes off, then momentarily flashes on again) *then* plug in power; the next morning, unplug power, open lid. *Keyboard* backlight is on, screen does not wake. ** 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/1299790 Title: [Apple Inc. MacBookAir4,1] suspend/resume failure [non-free: wl] Status in “linux” package in Ubuntu: Incomplete Bug description: I had shut the lid to suspend the system last night. *After that* I plugged in the mains lead. Today I unplugged the mains lead and *then* opened the lid, and tried to wake it, only to find it wouldn't do so. Had to force-reboot it. On logging into desktop, this bug report got triggered. It had been through some suspend/resume cycles already (not many; i only installed it on Friday), so the mains-plug behaviour is where I suspect the problem is. (Until now Trusty has been behaving impeccably on this laptop. :-) ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-20-generic 3.13.0-20.42 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: wl Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm1226 F pulseaudio rachel 1832 F pulseaudio CRDA: country EU: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5710 @ 40), (N/A, 27), DFS Date: Sun Mar 30 15:54:36 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2014-03-28 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64+mac (20140326) InterpreterPath: /usr/bin/python3.4 MachineType: Apple Inc. MacBookAir4,1 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: \boot\vmlinuz-3.13.0-20-generic root=UUID=c2167b45-d81a-4d7f-9017-36858344eef8 ro quiet splash vt.handoff=7 initrd=boot\initrd.img-3.13.0-20-generic PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-20-generic N/A linux-backports-modules-3.13.0-20-generic N/A linux-firmware 1.126 SourcePackage: linux Title: [Apple Inc. MacBookAir4,1] suspend/resume failure [non-free: wl] UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/24/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B0F.1201241549 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C08A6BB70A942AC2 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C08A6BB70A942AC2 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B0F.1201241549:bd01/24/2012:svnAppleInc.:pnMacBookAir4,1:pvr1.0:rvnAppleInc.:rnMac-C08A6BB70A942AC2:rvrMacBookAir4,1:cvnAppleInc.:ct10:cvrMac-C08A6BB70A942AC2: dmi.product.name: MacBookAir4,1 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/1299790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1299790] Re: [Apple Inc. MacBookAir4, 1] suspend/resume failure [non-free: wl]
3.14 installed. in case it means something, i *did* manage, twice, to get the timing right to cause that backlight flash that, before, signalled^Wcoincided with the crash, but both times the machine resumed normally afterwards. But hesitant to mark it fixed upstream as I couldn't reproduce the error on demand on the original 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/1299790 Title: [Apple Inc. MacBookAir4,1] suspend/resume failure [non-free: wl] Status in “linux” package in Ubuntu: Incomplete Bug description: I had shut the lid to suspend the system last night. *After that* I plugged in the mains lead. Today I unplugged the mains lead and *then* opened the lid, and tried to wake it, only to find it wouldn't do so. Had to force-reboot it. On logging into desktop, this bug report got triggered. It had been through some suspend/resume cycles already (not many; i only installed it on Friday), so the mains-plug behaviour is where I suspect the problem is. (Until now Trusty has been behaving impeccably on this laptop. :-) ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-20-generic 3.13.0-20.42 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: wl Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm1226 F pulseaudio rachel 1832 F pulseaudio CRDA: country EU: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5710 @ 40), (N/A, 27), DFS Date: Sun Mar 30 15:54:36 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2014-03-28 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64+mac (20140326) InterpreterPath: /usr/bin/python3.4 MachineType: Apple Inc. MacBookAir4,1 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: \boot\vmlinuz-3.13.0-20-generic root=UUID=c2167b45-d81a-4d7f-9017-36858344eef8 ro quiet splash vt.handoff=7 initrd=boot\initrd.img-3.13.0-20-generic PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-20-generic N/A linux-backports-modules-3.13.0-20-generic N/A linux-firmware 1.126 SourcePackage: linux Title: [Apple Inc. MacBookAir4,1] suspend/resume failure [non-free: wl] UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/24/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B0F.1201241549 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C08A6BB70A942AC2 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C08A6BB70A942AC2 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B0F.1201241549:bd01/24/2012:svnAppleInc.:pnMacBookAir4,1:pvr1.0:rvnAppleInc.:rnMac-C08A6BB70A942AC2:rvrMacBookAir4,1:cvnAppleInc.:ct10:cvrMac-C08A6BB70A942AC2: dmi.product.name: MacBookAir4,1 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/1299790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1300493] Re: [Apple Inc. MacBookAir4, 1] suspend/resume failure [non-free: wl]
Would like to mark as dupe of #1299790 (also raised by me - this bug is just from me trying to repeat it) but that appears not to be in my gift. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1300493 Title: [Apple Inc. MacBookAir4,1] suspend/resume failure [non-free: wl] Status in “linux” package in Ubuntu: Confirmed Bug description: got it to happen again once (ref: #1299790) ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-20-generic 3.13.0-20.42 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: wl Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm1211 F pulseaudio rachel 1830 F pulseaudio CRDA: country EU: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5710 @ 40), (N/A, 27), DFS Date: Mon Mar 31 23:41:12 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2014-03-28 (3 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64+mac (20140326) InterpreterPath: /usr/bin/python3.4 MachineType: Apple Inc. MacBookAir4,1 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: \boot\vmlinuz-3.13.0-20-generic root=UUID=c2167b45-d81a-4d7f-9017-36858344eef8 ro quiet splash vt.handoff=7 initrd=boot\initrd.img-3.13.0-20-generic PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-20-generic N/A linux-backports-modules-3.13.0-20-generic N/A linux-firmware 1.126 SourcePackage: linux Title: [Apple Inc. MacBookAir4,1] suspend/resume failure [non-free: wl] UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/24/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B0F.1201241549 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C08A6BB70A942AC2 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C08A6BB70A942AC2 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B0F.1201241549:bd01/24/2012:svnAppleInc.:pnMacBookAir4,1:pvr1.0:rvnAppleInc.:rnMac-C08A6BB70A942AC2:rvrMacBookAir4,1:cvnAppleInc.:ct10:cvrMac-C08A6BB70A942AC2: dmi.product.name: MacBookAir4,1 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/1300493/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1299790] Re: [Apple Inc. MacBookAir4, 1] suspend/resume failure [non-free: wl]
After a number of attempts I only managed to repeat it once, and that was with plugging in mains immediately after (practically simultaneously) closing the lid; so possibly while suspend mode is being entered. The time it happened, the backlight had gone off, then it came on again briefly, then off. Then when I opened the lid it was dead. But i couldn't make it happen again, so it may be *extremely* timing- sensitive and rare. Anyway I'll install the 3.14 kernel, but it's going to be hard to prove the negative given the positive is so chancy... But I suppose if it *does* happen, that tells us something and I could at least tag it 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/1299790 Title: [Apple Inc. MacBookAir4,1] suspend/resume failure [non-free: wl] Status in “linux” package in Ubuntu: Incomplete Bug description: I had shut the lid to suspend the system last night. *After that* I plugged in the mains lead. Today I unplugged the mains lead and *then* opened the lid, and tried to wake it, only to find it wouldn't do so. Had to force-reboot it. On logging into desktop, this bug report got triggered. It had been through some suspend/resume cycles already (not many; i only installed it on Friday), so the mains-plug behaviour is where I suspect the problem is. (Until now Trusty has been behaving impeccably on this laptop. :-) ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-20-generic 3.13.0-20.42 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: wl Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm1226 F pulseaudio rachel 1832 F pulseaudio CRDA: country EU: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5710 @ 40), (N/A, 27), DFS Date: Sun Mar 30 15:54:36 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2014-03-28 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64+mac (20140326) InterpreterPath: /usr/bin/python3.4 MachineType: Apple Inc. MacBookAir4,1 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: \boot\vmlinuz-3.13.0-20-generic root=UUID=c2167b45-d81a-4d7f-9017-36858344eef8 ro quiet splash vt.handoff=7 initrd=boot\initrd.img-3.13.0-20-generic PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-20-generic N/A linux-backports-modules-3.13.0-20-generic N/A linux-firmware 1.126 SourcePackage: linux Title: [Apple Inc. MacBookAir4,1] suspend/resume failure [non-free: wl] UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/24/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B0F.1201241549 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C08A6BB70A942AC2 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C08A6BB70A942AC2 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B0F.1201241549:bd01/24/2012:svnAppleInc.:pnMacBookAir4,1:pvr1.0:rvnAppleInc.:rnMac-C08A6BB70A942AC2:rvrMacBookAir4,1:cvnAppleInc.:ct10:cvrMac-C08A6BB70A942AC2: dmi.product.name: MacBookAir4,1 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/1299790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1300493] [NEW] [Apple Inc. MacBookAir4, 1] suspend/resume failure [non-free: wl]
Public bug reported: got it to happen again once (ref: #1299790) ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-20-generic 3.13.0-20.42 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: wl Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm1211 F pulseaudio rachel 1830 F pulseaudio CRDA: country EU: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5710 @ 40), (N/A, 27), DFS Date: Mon Mar 31 23:41:12 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2014-03-28 (3 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64+mac (20140326) InterpreterPath: /usr/bin/python3.4 MachineType: Apple Inc. MacBookAir4,1 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: \boot\vmlinuz-3.13.0-20-generic root=UUID=c2167b45-d81a-4d7f-9017-36858344eef8 ro quiet splash vt.handoff=7 initrd=boot\initrd.img-3.13.0-20-generic PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-20-generic N/A linux-backports-modules-3.13.0-20-generic N/A linux-firmware 1.126 SourcePackage: linux Title: [Apple Inc. MacBookAir4,1] suspend/resume failure [non-free: wl] UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/24/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B0F.1201241549 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C08A6BB70A942AC2 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C08A6BB70A942AC2 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B0F.1201241549:bd01/24/2012:svnAppleInc.:pnMacBookAir4,1:pvr1.0:rvnAppleInc.:rnMac-C08A6BB70A942AC2:rvrMacBookAir4,1:cvnAppleInc.:ct10:cvrMac-C08A6BB70A942AC2: dmi.product.name: MacBookAir4,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops resume suspend 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/1300493 Title: [Apple Inc. MacBookAir4,1] suspend/resume failure [non-free: wl] Status in “linux” package in Ubuntu: New Bug description: got it to happen again once (ref: #1299790) ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-20-generic 3.13.0-20.42 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: wl Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm1211 F pulseaudio rachel 1830 F pulseaudio CRDA: country EU: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5710 @ 40), (N/A, 27), DFS Date: Mon Mar 31 23:41:12 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2014-03-28 (3 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64+mac (20140326) InterpreterPath: /usr/bin/python3.4 MachineType: Apple Inc. MacBookAir4,1 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: \boot\vmlinuz-3.13.0-20-generic root=UUID=c2167b45-d81a-4d7f-9017-36858344eef8 ro quiet splash vt.handoff=7 initrd=boot\initrd.img-3.13.0-20-generic PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-20-generic N/A linux-backports-modules-3.13.0-20-generic N/A linux-firmware 1.126 SourcePackage: linux Title: [Apple Inc. MacBookAir4,1] suspend/resume failure [non-free: wl] UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/24/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B0F.1201241549 dmi.board.asset.tag: Bas
[Kernel-packages] [Bug 1299790] Re: [Apple Inc. MacBookAir4, 1] suspend/resume failure [non-free: wl]
No objection in principle to trying. Our main problem here is that the bug may not even be reliably repeatable with the current kernel *anyway*, though before doing that upgrade I'll give it a go (having been avoiding the sequence of events that I *think* triggered it the one time it did happen). So I'll just try to reliably repeat the problem first. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1299790 Title: [Apple Inc. MacBookAir4,1] suspend/resume failure [non-free: wl] Status in “linux” package in Ubuntu: Incomplete Bug description: I had shut the lid to suspend the system last night. *After that* I plugged in the mains lead. Today I unplugged the mains lead and *then* opened the lid, and tried to wake it, only to find it wouldn't do so. Had to force-reboot it. On logging into desktop, this bug report got triggered. It had been through some suspend/resume cycles already (not many; i only installed it on Friday), so the mains-plug behaviour is where I suspect the problem is. (Until now Trusty has been behaving impeccably on this laptop. :-) ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-20-generic 3.13.0-20.42 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: wl Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm1226 F pulseaudio rachel 1832 F pulseaudio CRDA: country EU: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5710 @ 40), (N/A, 27), DFS Date: Sun Mar 30 15:54:36 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2014-03-28 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64+mac (20140326) InterpreterPath: /usr/bin/python3.4 MachineType: Apple Inc. MacBookAir4,1 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: \boot\vmlinuz-3.13.0-20-generic root=UUID=c2167b45-d81a-4d7f-9017-36858344eef8 ro quiet splash vt.handoff=7 initrd=boot\initrd.img-3.13.0-20-generic PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-20-generic N/A linux-backports-modules-3.13.0-20-generic N/A linux-firmware 1.126 SourcePackage: linux Title: [Apple Inc. MacBookAir4,1] suspend/resume failure [non-free: wl] UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/24/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B0F.1201241549 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C08A6BB70A942AC2 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C08A6BB70A942AC2 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B0F.1201241549:bd01/24/2012:svnAppleInc.:pnMacBookAir4,1:pvr1.0:rvnAppleInc.:rnMac-C08A6BB70A942AC2:rvrMacBookAir4,1:cvnAppleInc.:ct10:cvrMac-C08A6BB70A942AC2: dmi.product.name: MacBookAir4,1 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/1299790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1299790] [NEW] [Apple Inc. MacBookAir4, 1] suspend/resume failure [non-free: wl]
Public bug reported: I had shut the lid to suspend the system last night. *After that* I plugged in the mains lead. Today I unplugged the mains lead and *then* opened the lid, and tried to wake it, only to find it wouldn't do so. Had to force-reboot it. On logging into desktop, this bug report got triggered. It had been through some suspend/resume cycles already (not many; i only installed it on Friday), so the mains-plug behaviour is where I suspect the problem is. (Until now Trusty has been behaving impeccably on this laptop. :-) ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-20-generic 3.13.0-20.42 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: wl Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm1226 F pulseaudio rachel 1832 F pulseaudio CRDA: country EU: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5710 @ 40), (N/A, 27), DFS Date: Sun Mar 30 15:54:36 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2014-03-28 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64+mac (20140326) InterpreterPath: /usr/bin/python3.4 MachineType: Apple Inc. MacBookAir4,1 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: \boot\vmlinuz-3.13.0-20-generic root=UUID=c2167b45-d81a-4d7f-9017-36858344eef8 ro quiet splash vt.handoff=7 initrd=boot\initrd.img-3.13.0-20-generic PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-20-generic N/A linux-backports-modules-3.13.0-20-generic N/A linux-firmware 1.126 SourcePackage: linux Title: [Apple Inc. MacBookAir4,1] suspend/resume failure [non-free: wl] UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/24/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B0F.1201241549 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C08A6BB70A942AC2 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C08A6BB70A942AC2 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B0F.1201241549:bd01/24/2012:svnAppleInc.:pnMacBookAir4,1:pvr1.0:rvnAppleInc.:rnMac-C08A6BB70A942AC2:rvrMacBookAir4,1:cvnAppleInc.:ct10:cvrMac-C08A6BB70A942AC2: dmi.product.name: MacBookAir4,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops resume suspend 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/1299790 Title: [Apple Inc. MacBookAir4,1] suspend/resume failure [non-free: wl] Status in “linux” package in Ubuntu: New Bug description: I had shut the lid to suspend the system last night. *After that* I plugged in the mains lead. Today I unplugged the mains lead and *then* opened the lid, and tried to wake it, only to find it wouldn't do so. Had to force-reboot it. On logging into desktop, this bug report got triggered. It had been through some suspend/resume cycles already (not many; i only installed it on Friday), so the mains-plug behaviour is where I suspect the problem is. (Until now Trusty has been behaving impeccably on this laptop. :-) ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-20-generic 3.13.0-20.42 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: wl Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm1226 F pulseaudio rachel 1832 F pulseaudio CRDA: country EU: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5710 @ 40), (N/A, 27), DFS Date: Sun Mar 30 15:54:36 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2014-03-28 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64+mac (20140326) InterpreterPath: /usr/bin/python3.4 MachineType: App
[Kernel-packages] [Bug 1293361] Re: xHCI regression(mass storage devices fail) in stable 3.13.5(14.04)
FYI this also seems to have fixed a problem I was having with a USB DVB-S2 receiver, which apparently caused the drivers to hang on load *only* on xHCI; on EHCI, same kernel, all was fine. So this may not have been purely a mass storage device 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/1293361 Title: xHCI regression(mass storage devices fail) in stable 3.13.5(14.04) Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Released Bug description: Mar 11 02:00:25 u-ThinkPad-X240s kernel: [ 299.252465] usb 3-2: reset SuperSpeed USB device number 2 using xhci_hcd Mar 11 02:00:25 u-ThinkPad-X240s kernel: [ 299.268395] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880046f75980 Mar 11 02:00:25 u-ThinkPad-X240s kernel: [ 299.268400] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880046f759c0 Mar 11 02:00:25 u-ThinkPad-X240s kernel: [ 299.540388] usb 3-2: reset SuperSpeed USB device number 2 using xhci_hcd Mar 11 02:00:25 u-ThinkPad-X240s kernel: [ 299.556687] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880046f75980 Mar 11 02:00:25 u-ThinkPad-X240s kernel: [ 299.556693] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880046f759c0 Mar 11 02:00:25 u-ThinkPad-X240s kernel: [ 299.557393] sd 3:0:0:0: [sdb] Unhandled error code Mar 11 02:00:25 u-ThinkPad-X240s kernel: [ 299.557399] sd 3:0:0:0: [sdb] Mar 11 02:00:25 u-ThinkPad-X240s kernel: [ 299.557401] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK Mar 11 02:00:25 u-ThinkPad-X240s kernel: [ 299.557403] sd 3:0:0:0: [sdb] CDB: Mar 11 02:00:25 u-ThinkPad-X240s kernel: [ 299.557405] Read(10): 28 00 00 00 35 a1 00 00 66 00 Mar 11 02:00:25 u-ThinkPad-X240s kernel: [ 299.557415] end_request: I/O error, dev sdb, sector 13729 http://www.spinics.net/lists/linux-usb/msg103757.html should backport: e2ed511400d41e0d136089d5a55ceab57c6a2426 469d417b68958a064c09e7875646c97c6e783dfc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1293361/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
