[Kernel-packages] [Bug 1604313] Re: Ubuntu 16.04: system freezes instead of suspend after undocking
brandon211, the next step is to fully commit bisect from kernel 4.4.0-22 to 4.4.0-28 in order to identify the last good kernel commit, followed immediately by the first bad one. This will allow for a more expedited analysis of the root cause of your issue. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ? Please note, finding adjacent kernel versions is not fully commit bisecting. Also, the kernel release names are irrelevant for the purposes of bisecting. After the offending commit (not kernel version) has been identified, then please mark this report Status Confirmed. Thank you for your help. ** Tags removed: bios-outdated-1.25 ** Tags added: latest-bios-1.24 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1604313 Title: Ubuntu 16.04: system freezes instead of suspend after undocking Status in linux package in Ubuntu: Incomplete Bug description: I'm using a Lenovo ThinkPad T450s. When the system was docked and then undocked, suspend won't work. Instead, the screen goes black, the system freezes and the fan runs on high speed. This problem persists with the (as of today) most recent kernel 4.4.0-31-generic #50. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: buerger3534 F pulseaudio /dev/snd/pcmC1D0p: buerger3534 F...m pulseaudio /dev/snd/controlC1: buerger3534 F pulseaudio CurrentDesktop: Unity Date: Tue Jul 19 11:13:41 2016 HibernationDevice: RESUME=UUID=21eeaf61-c437-45dc-80e3-e581eb6f795c InstallationDate: Installed on 2015-09-15 (307 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 20BX000XGE ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=93fc15f9-4090-40ff-a3ac-a642833f1da2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-22 (87 days ago) dmi.bios.date: 03/23/2016 dmi.bios.vendor: LENOVO dmi.bios.version: JBET57WW (1.22 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BX000XGE dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET57WW(1.22):bd03/23/2016:svnLENOVO:pn20BX000XGE:pvrThinkPadT450s:rvnLENOVO:rn20BX000XGE:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BX000XGE dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1604313/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1580311] Re: Laptop boots only if external display connected
** Tags removed: kernel-bug-exists-upstream-4.7-rc6 latest-bios-4.0.7 ** Tags added: bios-outdated-4.0.9 kernel-bug-exists-upstream-4.7 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1580311 Title: Laptop boots only if external display connected Status in linux package in Ubuntu: Incomplete Bug description: Hi, Since updating to 16.04 with kernel vmlinuz-4.4.0-22-generic my laptop no longer completes the boot sequence under a normal boot scenario - the "loading initrd..." message is displayed, then, when the VGA modesetting usually kicks the display into a higher resolution, the screen blanks and the startup apparently halts. This is a regression from 4.2 series kernels. I can successfully bring up the system if I revert to 4.2.0-35, and also if I boot 4.4 with the failsafe setting (but then X is painfully slow, as its using software) Matt ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue May 10 20:29:56 2016 DistUpgraded: 2016-05-04 00:10:55,503 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.18, 4.2.0-35-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-22-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:06ac] InstallationDate: Installed on 2015-05-12 (364 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Inspiron 15-3552 PlymouthDebug: Error: [Errno 13] Permission denied: '/var/log/plymouth-debug.log' ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-35-generic.efi.signed root=/dev/mapper/ubuntu--15--vg-root ro plymouth:debug i8042.nopnp=1 vesafb.invalid=1 drm.debug=0xe SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to xenial on 2016-05-03 (6 days ago) dmi.bios.date: 11/17/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.0.3 dmi.board.name: 0CP33T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.0.3:bd11/17/2015:svnDellInc.:pnInspiron15-3552:pvr4.0.3:rvnDellInc.:rn0CP33T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.0.3 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue May 10 12:26:45 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5578 vendor CMN xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1580311/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1607571] Re: No network devices after suspend and resume
** Tags removed: latest-bios-1.2.15 ** Tags added: bios-outdated-1.3.6 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1607571 Title: No network devices after suspend and resume Status in linux package in Ubuntu: Confirmed Bug description: I'm on an Alienware 17R3 on Ubuntu 16.04. The wifi stops working after resume. The problem seems related to https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1422143, but the solutions proposed there doesn't work. Other seems to have a problem related with the network-manager stop working (like http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend- after-16-04-upgrade). However, in my case the network-manager restarts and stops after the resume. However, there is no device, and thus there is no list of available networks to join. For example, doing $ iwconfig lono wireless extensions. while in a normal reboot the wireless card information is printed $ iwconfig wlp60s0 IEEE 802.11abgn ESSID:"Chapinlandia" Mode:Managed Frequency:2.412 GHz Access Point: 8C:04:FF:F6:90:9E Bit Rate=1 Mb/s Tx-Power=20 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:on Link Quality=51/70 Signal level=-59 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:36 Invalid misc:39 Missed beacon:0 lono wireless extensions. enp59s0 no wireless extensions. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adin 3934 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 28 21:05:44 2016 HibernationDevice: RESUME=UUID=c0bba13c-6fa5-4545-a7ee-cd58b1e6e3bd InstallationDate: Installed on 2016-07-03 (25 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Alienware Alienware 17 R3 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=dc6d8cac-eff1-4dce-97fd-949d7268d2d9 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2015 dmi.bios.vendor: Alienware dmi.bios.version: 1.2.3 dmi.board.name: Alienware 17 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.2.3:bd11/11/2015:svnAlienware:pnAlienware17R3:pvr1.2.3:rvnAlienware:rnAlienware17R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.name: Alienware 17 R3 dmi.product.version: 1.2.3 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1607571/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1607571] Re: No network devices after suspend and resume
** 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/1607571 Title: No network devices after suspend and resume Status in linux package in Ubuntu: Confirmed Bug description: I'm on an Alienware 17R3 on Ubuntu 16.04. The wifi stops working after resume. The problem seems related to https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1422143, but the solutions proposed there doesn't work. Other seems to have a problem related with the network-manager stop working (like http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend- after-16-04-upgrade). However, in my case the network-manager restarts and stops after the resume. However, there is no device, and thus there is no list of available networks to join. For example, doing $ iwconfig lono wireless extensions. while in a normal reboot the wireless card information is printed $ iwconfig wlp60s0 IEEE 802.11abgn ESSID:"Chapinlandia" Mode:Managed Frequency:2.412 GHz Access Point: 8C:04:FF:F6:90:9E Bit Rate=1 Mb/s Tx-Power=20 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:on Link Quality=51/70 Signal level=-59 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:36 Invalid misc:39 Missed beacon:0 lono wireless extensions. enp59s0 no wireless extensions. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adin 3934 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 28 21:05:44 2016 HibernationDevice: RESUME=UUID=c0bba13c-6fa5-4545-a7ee-cd58b1e6e3bd InstallationDate: Installed on 2016-07-03 (25 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Alienware Alienware 17 R3 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=dc6d8cac-eff1-4dce-97fd-949d7268d2d9 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2015 dmi.bios.vendor: Alienware dmi.bios.version: 1.2.3 dmi.board.name: Alienware 17 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.2.3:bd11/11/2015:svnAlienware:pnAlienware17R3:pvr1.2.3:rvnAlienware:rnAlienware17R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.name: Alienware 17 R3 dmi.product.version: 1.2.3 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1607571/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1584051] Re: BUG: soft lockup - CPU#0 stuck for 22s! [kswapd0:33]
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1584051 Title: BUG: soft lockup - CPU#0 stuck for 22s! [kswapd0:33] Status in linux package in Ubuntu: Expired Bug description: This is an upgrade of LXLE (lxle.net) from 12.04 to 14.04. The installation has been done by leaving the /home partition intact and installing the 14.04 upon the re-formatted /boot and /root and /swap partitions. The size of all the partitions have been kept the same. I get this error soon after I start up the Notebook pretty much 70% of the times. And it comes up multiple times while the Notebook is on. What follows are random spikes of CPU load with few seconds of freezes. However, when I use Chromium, thing get worst. CPU spikes are longer and it often requires a restart. Chromium details: Chromium 49.0.2623.108 (Developer Build) Ubuntu 14.04 (32-bit) Revision d65a1c2f313b54fb0b90bb8a1082e4f5ecba2dda OSLinux Blink 537.36 (@d65a1c2f313b54fb0b90bb8a1082e4f5ecba2dda) JavaScriptV8 4.9.385.33 Flash 11.2.999.999 User AgentMozilla/5.0 (X11; Linux i686) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/49.0.2623.108 Chrome/49.0.2623.108 Safari/537.36 Command Line /usr/lib/chromium-browser/chromium-browser --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so --ppapi-flash-version --enable-pinch --window-depth=24 --flag-switches-begin --disable-quic --flag-switches-end Executable Path /usr/lib/chromium-browser/chromium-browser Profile Path /home/msal/.config/chromium/Default Variationscf5ed6e1-3f4a17df f1eb96ab-3f4a17df 775ebbd7-3f4a17df f5dd6118-2f5721af 4ea303a6-3f4a17df dbffab5d-f51b51 c8b9b12d-d93a0620 867c4c68-3f4a17df a70306ec-3f4a17df Attached in the Apport .crash report Thanks M. --- ApportVersion: 2.14.1-0ubuntu3.20 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: brucopeloso 2847 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=580edce1-e022-4aec-9123-a50687f0a963 MachineType: Hewlett-Packard HP Mini 5101 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-86-generic root=UUID=7462b3f0-9e8f-4431-9aaa-ace395d4ef91 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-86.131-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-86-generic N/A linux-backports-modules-3.13.0-86-generic N/A linux-firmware 1.127.22 StagingDrivers: zram Tags: trusty staging Uname: Linux 3.13.0-86-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/06/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68DGI Ver. F.01 dmi.board.name: 3632 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 34.0F dmi.chassis.asset.tag: CNU9322GCH dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68DGIVer.F.01:bd07/06/2009:svnHewlett-Packard:pnHPMini5101:pvrF.01:rvnHewlett-Packard:rn3632:rvrKBCVersion34.0F:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Mini 5101 dmi.product.version: F.01 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584051/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1245081] Re: macbook keyboard layout maps the tilde key to something else
Workaround is still needed and works on Xenial 16.04 for my MBA 6,2 (2013). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1245081 Title: macbook keyboard layout maps the tilde key to something else Status in linux package in Ubuntu: Confirmed Bug description: 1. install ubuntu on Macbook Air 6,2 2. press the key with the tilde ('~') written on it. 3. see that is prints '§' instead. This is particularly annoying since the way to switch between windows uses the tilde. --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kms1491 F pulseaudio /dev/snd/controlC1: kms1491 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=9e7b2d0e-6a44-4ad7-9725-f9a3f5f39c33 InstallationDate: Installed on 2013-10-25 (1 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64+mac (20131016.1) MachineType: Apple Inc. MacBookAir6,2 MarkForUpload: True NonfreeKernelModules: wl Package: linux 3.11.0.12.13 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=079cbe6b-6488-4e57-85d3-c3e3e2fcbe40 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 Tags: saucy Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 07/12/2013 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA61.88Z.0099.B01.1307121317 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-7DF21CB3ED6977E5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir6,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-7DF21CB3ED6977E5 dmi.modalias: dmi:bvnAppleInc.:bvrMBA61.88Z.0099.B01.1307121317:bd07/12/2013:svnAppleInc.:pnMacBookAir6,2:pvr1.0:rvnAppleInc.:rnMac-7DF21CB3ED6977E5:rvrMacBookAir6,2:cvnAppleInc.:ct10:cvrMac-7DF21CB3ED6977E5: dmi.product.name: MacBookAir6,2 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/1245081/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1616966] Re: linux: 4.6.0-12.14 -proposed tracker
** Tags added: block-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1616966 Title: linux: 4.6.0-12.14 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Confirmed Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: New Status in linux source package in Yakkety: New Bug description: This bug is for tracking the 4.6.0-12.14 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1616966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1612006] Re: I2C touchpad does not work on AMD platform
This bug was fixed in the package linux - 4.4.0-9136.55 --- linux (4.4.0-9136.55) yakkety; urgency=low [ Adam Conrad ] * Rebuild in yakkety for the binutils transition: - Bump ABI to avoid namespace clash with xenial kernels. - Build-depend on (and use) gcc-5 to match xenial. * Pull patches to allow perf to build against glibc 2.24: - 22a9f41b555673e7499b97acf3ffb07bf0af31ad - 7839b9f32e45075d9eb48da8480faef3dbd019f0 - 9a5f3bf332bbd42625b71553ca9ffdffa9fc4785 - 2515e614834f362eed36fb5ea5d359d94a525263 [ Stefan Bader ] * Release Tracking Bug - LP: #1612305 * I2C touchpad does not work on AMD platform (LP: #1612006) - SAUCE: pinctrl/amd: Remove the default de-bounce time * CVE-2016-5696 - tcp: make challenge acks less predictable -- Adam Conrad Thu, 25 Aug 2016 23:45:12 -0600 ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2016-5696 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1612006 Title: I2C touchpad does not work on AMD platform Status in HWE Next: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: Recent AMD platform has problems with I2C touchpads because its GPIO controller is not configured correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1612006/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1612305] Re: linux: 4.4.0-36.55 -proposed tracker
This bug was fixed in the package linux - 4.4.0-9136.55 --- linux (4.4.0-9136.55) yakkety; urgency=low [ Adam Conrad ] * Rebuild in yakkety for the binutils transition: - Bump ABI to avoid namespace clash with xenial kernels. - Build-depend on (and use) gcc-5 to match xenial. * Pull patches to allow perf to build against glibc 2.24: - 22a9f41b555673e7499b97acf3ffb07bf0af31ad - 7839b9f32e45075d9eb48da8480faef3dbd019f0 - 9a5f3bf332bbd42625b71553ca9ffdffa9fc4785 - 2515e614834f362eed36fb5ea5d359d94a525263 [ Stefan Bader ] * Release Tracking Bug - LP: #1612305 * I2C touchpad does not work on AMD platform (LP: #1612006) - SAUCE: pinctrl/amd: Remove the default de-bounce time * CVE-2016-5696 - tcp: make challenge acks less predictable -- Adam Conrad Thu, 25 Aug 2016 23:45:12 -0600 ** Changed in: linux (Ubuntu) Status: Invalid => Fix Released ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2016-5696 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1612305 Title: linux: 4.4.0-36.55 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-36.55 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1612305/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1616966] Re: linux: 4.6.0-12.14 -proposed tracker
** Tags removed: block-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1616966 Title: linux: 4.6.0-12.14 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Confirmed Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: New Status in linux source package in Yakkety: New Bug description: This bug is for tracking the 4.6.0-12.14 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1616966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1572801] Re: Ubuntu 16.04 Unity desktop uses much more ram than Ubuntu 15.10
I was having the same issue: lots of RAM usage, increasing over time, even with no applications open. I uninstalled the evolution package (just that one, no other evolution-*), and the problem seems to be fixed. Still testing, but I haven't seen excessive ram usage since yesterday. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1572801 Title: Ubuntu 16.04 Unity desktop uses much more ram than Ubuntu 15.10 Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Confirmed Bug description: Ubuntu 16.04 64bit ISO number 20160420.1 unity version 7.4.0+16.04.20160415-0ubuntu1 Ubuntu 16.04 64bit ram usage has increase dramatically over Ubuntu 15.10 Ubuntu 16.04 ram roughly 1 GB Ubuntu15.10 can be tuned to 420, 450 MB Ubuntu 16.04 with unity uses 1GB whereas Kubuntu 16.04 is using 420MB live usb ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160415-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.376 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Apr 21 01:44:22 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] GsettingsChanges: b'org.compiz.core' b'outputs' b"['1920x1080+0+0']" b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 'place', 'regex', 'resize', 'session', 'snap', 'vpswitch', 'wall', 'animation', 'commands', 'compiztoolbox', 'copytex', 'fade', 'grid', 'imgpng', 'mousepoll', 'move', 'scale', 'unitymtgrabhandles', 'workarounds', 'expo', 'ezoom', 'unityshell']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: ASUS All Series ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- cdrom-detect/try-usb=true noprompt SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2004 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2004:bd06/03/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PLUS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Apr 21 01:37:17 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1572801/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1617622] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1617622 Title: no sound only dummy output Status in linux package in Ubuntu: Confirmed Bug description: alsa force reload worke d but now it dont ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-36-generic 4.4.0-36.55 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D1', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: GNOME Date: Sat Aug 27 16:15:15 2016 HibernationDevice: RESUME=UUID=afe10987-bd60-4356-aa71-790cef4f64fb InstallationDate: Installed on 2012-12-22 (1343 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 04e8:6865 Samsung Electronics Co., Ltd GT-I9300 Phone [Galaxy S III] (PTP mode) Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Acer, inc. Aspire 4520 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=776a497e-7cf0-491b-8c63-5a35aaded5dd ro drm.debug=0xe plymouth:debug RelatedPackageVersions: linux-restricted-modules-4.4.0-36-generic N/A linux-backports-modules-4.4.0-36-generic N/A linux-firmware1.157.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2007 dmi.bios.vendor: Acer dmi.bios.version: v1.3620 dmi.board.name: Mono dmi.board.vendor: Acer, Inc. dmi.board.version: Not Applicable dmi.chassis.type: 1 dmi.chassis.vendor: Acer, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrv1.3620:bd09/14/2007:svnAcer,inc.:pnAspire4520:pvrNotApplicable:rvnAcer,Inc.:rnMono:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A: dmi.product.name: Aspire 4520 dmi.product.version: Not Applicable dmi.sys.vendor: Acer, inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1617622/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1617622] [NEW] no sound only dummy output
Public bug reported: alsa force reload worke d but now it dont ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-36-generic 4.4.0-36.55 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D1', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: GNOME Date: Sat Aug 27 16:15:15 2016 HibernationDevice: RESUME=UUID=afe10987-bd60-4356-aa71-790cef4f64fb InstallationDate: Installed on 2012-12-22 (1343 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 04e8:6865 Samsung Electronics Co., Ltd GT-I9300 Phone [Galaxy S III] (PTP mode) Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Acer, inc. Aspire 4520 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=776a497e-7cf0-491b-8c63-5a35aaded5dd ro drm.debug=0xe plymouth:debug RelatedPackageVersions: linux-restricted-modules-4.4.0-36-generic N/A linux-backports-modules-4.4.0-36-generic N/A linux-firmware1.157.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2007 dmi.bios.vendor: Acer dmi.bios.version: v1.3620 dmi.board.name: Mono dmi.board.vendor: Acer, Inc. dmi.board.version: Not Applicable dmi.chassis.type: 1 dmi.chassis.vendor: Acer, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrv1.3620:bd09/14/2007:svnAcer,inc.:pnAspire4520:pvrNotApplicable:rvnAcer,Inc.:rnMono:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A: dmi.product.name: Aspire 4520 dmi.product.version: Not Applicable dmi.sys.vendor: Acer, inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-bug i386 package-from-proposed 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/1617622 Title: no sound only dummy output Status in linux package in Ubuntu: Confirmed Bug description: alsa force reload worke d but now it dont ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-36-generic 4.4.0-36.55 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D1', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: GNOME Date: Sat Aug 27 16:15:15 2016 HibernationDevice: RESUME=UUID=afe10987-bd60-4356-aa71-790cef4f64fb InstallationDate: Installed on 2012-12-22 (1343 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 04e8:6865 Samsung Electronics Co., Ltd GT-I9300 Phone [Galaxy S III] (PTP mode) Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Acer, inc. Aspire 4520 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=776a497e-7cf0-491b-8c63-5a35aaded5dd ro drm.debug=0xe plymouth:debug RelatedPackageVersions: linux-restricted-modules-4.4.0-36-generic N/A linux-backports-modules-4.4.0-36-generic N/A linux-firmware1.157.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2007 dmi.bios.vendor: Acer dmi.bios.version: v1.3620 dmi.board.name: Mono dmi.board.vendor: Acer, Inc. dmi.board.version: Not Applicable dmi.chassis.type: 1 dmi.chassis.vendor: Acer, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrv1.3620:bd09/14/2007:svnAcer,inc.:pnAspire4520:pvrNotApplicable:rvnAcer,Inc.:rnMono:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A: dmi.product.name: Aspire 4520 dmi.product.version: Not Applicable dmi.sys.vendor: Acer, inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1617622/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1617619] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1617619 Title: Problem with Bluetooth USB Host Controller: Connection time-out after connecting to device Status in linux package in Ubuntu: Confirmed Bug description: 1.) Release: Ubuntu 16.04 LTS Kernel: Ubuntu 4.4.0-34.53-generic 4.4.15 CPU: Intel® Core™ i5-2450M CPU @ 2.50GHz × 4 Graphics: Gallium 0.4 on NVC1 OS type: 64-bit 2.)package-version (gnome-bluetooth): 3.18.2-1ubuntu2 3.) I expected a smooth connection of the computer to my speakers via bluetooth. 4.)... but after a short connection it sometimes gets a timeout. I faced this problem several times now, but not after every boot. I always tried to log-out and log-in again, as well as restarting the computer. Sometimes it helped, but this time it didn't work. I tried to fix it like in this report: http://askubuntu.com/questions/804014/stuck-on-a-bluetooth-problem they suggested it may be a kernel problem, therefore I thought it might be a good idea to report this, as it could be a bug. Here are some outputs: tingatinga@Xel:~$ dmesg | grep -i blue [2.461258] usb 1-1.5: Product: Bluetooth USB Host Controller [8.686487] Bluetooth: Core ver 2.21 [8.686504] Bluetooth: HCI device and connection manager initialized [8.686509] Bluetooth: HCI socket layer initialized [8.686512] Bluetooth: L2CAP socket layer initialized [8.686518] Bluetooth: SCO socket layer initialized [ 10.878528] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 10.878533] Bluetooth: BNEP filters: protocol multicast [ 10.878539] Bluetooth: BNEP socket layer initialized [ 24.914041] usb 1-1.5: Product: Bluetooth USB Host Controller [ 25.036498] Bluetooth: RFCOMM TTY layer initialized [ 25.036506] Bluetooth: RFCOMM socket layer initialized [ 25.036512] Bluetooth: RFCOMM ver 1.11 [ 1180.258184] usb 1-1.5: Product: Bluetooth USB Host Controller [ 1182.331574] Bluetooth: hci0 command 0x0c16 tx timeout [ 1184.335420] Bluetooth: hci0 command 0x2002 tx timeout [ 1186.339358] Bluetooth: hci0 command 0x2003 tx timeout [ 1188.343276] Bluetooth: hci0 command 0x201c tx timeout [ 1814.065219] usb 1-1.5: Product: Bluetooth USB Host Controller [ 1833.224835] usb 1-1.5: Product: Bluetooth USB Host Controller [ 1835.345966] Bluetooth: hci0 command 0x0c13 tx timeout [ 1837.353923] Bluetooth: hci0 command 0x2009 tx timeout [ 1839.357812] Bluetooth: hci0 command 0x0c52 tx timeout [ 1919.603466] Bluetooth: hci0 command 0x0405 tx timeout [ 1959.698076] Bluetooth: hci0 command 0x0408 tx timeout [ 2014.352121] Bluetooth: hci0 command 0x0408 tx timeout [ 2104.859182] usb 1-1.5: Product: Bluetooth USB Host Controller [ 2106.932712] Bluetooth: hci0 command 0x2003 tx timeout [ 2108.936570] Bluetooth: hci0 command 0x201c tx timeout [ 2110.940554] Bluetooth: hci0 command 0x1002 tx timeout [ 2112.944538] Bluetooth: hci0 command 0x0c52 tx timeout tingatinga@Xel:~$ lspci -knn | grep Net -A2; lsusb 02:00.0 Network controller [0280]: Qualcomm Atheros AR9485 Wireless Network Adapter [168c:0032] (rev 01) Subsystem: Foxconn International, Inc. Unex DHXA-225 [105b:e044] Kernel driver in use: ath9k Bus 002 Device 003: ID 276d:1160 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 0fce:0192 Sony Ericsson Mobile Communications AB Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 010: ID 0489:e036 Foxconn / Hon Hai Bus 001 Device 003: ID 05ca:18c0 Ricoh Co., Ltd Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub tingatinga@Xel:~$ dmesg | grep ath3k; dkms status [8.777178] usbcore: registered new interface driver ath3k tingatinga@Xel:~$ dmesg | grep ath9k; dkms status [9.105129] ath9k :02:00.0 wlp2s0: renamed from wlan0 [ 68.612969] ath9k :02:00.0 wlp2s0: disabling HT as WMM/QoS is not supported by the AP [ 68.612973] ath9k :02:00.0 wlp2s0: disabling VHT as WMM/QoS is not supported by the AP [ 1295.614238] ath9k :02:00.0 wlp2s0: disabling HT as WMM/QoS is not supported by the AP [ 1295.614242] ath9k :02:00.0 wlp2s0: disabling VHT as WMM/QoS is not supported by the AP [ 1664.599594] ath9k :02:00.0 wlp2s0: disabling HT as WMM/QoS is not supported by the AP [ 1664.599598] ath9k :02:00.0 wlp2s0: disabling VHT as WMM/QoS is not supported by the AP ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-34-generic 4.4.0-34.53 Pr
[Kernel-packages] [Bug 1617619] [NEW] Problem with Bluetooth USB Host Controller: Connection time-out after connecting to device
Public bug reported: 1.) Release: Ubuntu 16.04 LTS Kernel: Ubuntu 4.4.0-34.53-generic 4.4.15 CPU: Intel® Core™ i5-2450M CPU @ 2.50GHz × 4 Graphics: Gallium 0.4 on NVC1 OS type: 64-bit 2.)package-version (gnome-bluetooth): 3.18.2-1ubuntu2 3.) I expected a smooth connection of the computer to my speakers via bluetooth. 4.)... but after a short connection it sometimes gets a timeout. I faced this problem several times now, but not after every boot. I always tried to log-out and log-in again, as well as restarting the computer. Sometimes it helped, but this time it didn't work. I tried to fix it like in this report: http://askubuntu.com/questions/804014/stuck-on-a-bluetooth-problem they suggested it may be a kernel problem, therefore I thought it might be a good idea to report this, as it could be a bug. Here are some outputs: tingatinga@Xel:~$ dmesg | grep -i blue [2.461258] usb 1-1.5: Product: Bluetooth USB Host Controller [8.686487] Bluetooth: Core ver 2.21 [8.686504] Bluetooth: HCI device and connection manager initialized [8.686509] Bluetooth: HCI socket layer initialized [8.686512] Bluetooth: L2CAP socket layer initialized [8.686518] Bluetooth: SCO socket layer initialized [ 10.878528] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 10.878533] Bluetooth: BNEP filters: protocol multicast [ 10.878539] Bluetooth: BNEP socket layer initialized [ 24.914041] usb 1-1.5: Product: Bluetooth USB Host Controller [ 25.036498] Bluetooth: RFCOMM TTY layer initialized [ 25.036506] Bluetooth: RFCOMM socket layer initialized [ 25.036512] Bluetooth: RFCOMM ver 1.11 [ 1180.258184] usb 1-1.5: Product: Bluetooth USB Host Controller [ 1182.331574] Bluetooth: hci0 command 0x0c16 tx timeout [ 1184.335420] Bluetooth: hci0 command 0x2002 tx timeout [ 1186.339358] Bluetooth: hci0 command 0x2003 tx timeout [ 1188.343276] Bluetooth: hci0 command 0x201c tx timeout [ 1814.065219] usb 1-1.5: Product: Bluetooth USB Host Controller [ 1833.224835] usb 1-1.5: Product: Bluetooth USB Host Controller [ 1835.345966] Bluetooth: hci0 command 0x0c13 tx timeout [ 1837.353923] Bluetooth: hci0 command 0x2009 tx timeout [ 1839.357812] Bluetooth: hci0 command 0x0c52 tx timeout [ 1919.603466] Bluetooth: hci0 command 0x0405 tx timeout [ 1959.698076] Bluetooth: hci0 command 0x0408 tx timeout [ 2014.352121] Bluetooth: hci0 command 0x0408 tx timeout [ 2104.859182] usb 1-1.5: Product: Bluetooth USB Host Controller [ 2106.932712] Bluetooth: hci0 command 0x2003 tx timeout [ 2108.936570] Bluetooth: hci0 command 0x201c tx timeout [ 2110.940554] Bluetooth: hci0 command 0x1002 tx timeout [ 2112.944538] Bluetooth: hci0 command 0x0c52 tx timeout tingatinga@Xel:~$ lspci -knn | grep Net -A2; lsusb 02:00.0 Network controller [0280]: Qualcomm Atheros AR9485 Wireless Network Adapter [168c:0032] (rev 01) Subsystem: Foxconn International, Inc. Unex DHXA-225 [105b:e044] Kernel driver in use: ath9k Bus 002 Device 003: ID 276d:1160 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 0fce:0192 Sony Ericsson Mobile Communications AB Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 010: ID 0489:e036 Foxconn / Hon Hai Bus 001 Device 003: ID 05ca:18c0 Ricoh Co., Ltd Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub tingatinga@Xel:~$ dmesg | grep ath3k; dkms status [8.777178] usbcore: registered new interface driver ath3k tingatinga@Xel:~$ dmesg | grep ath9k; dkms status [9.105129] ath9k :02:00.0 wlp2s0: renamed from wlan0 [ 68.612969] ath9k :02:00.0 wlp2s0: disabling HT as WMM/QoS is not supported by the AP [ 68.612973] ath9k :02:00.0 wlp2s0: disabling VHT as WMM/QoS is not supported by the AP [ 1295.614238] ath9k :02:00.0 wlp2s0: disabling HT as WMM/QoS is not supported by the AP [ 1295.614242] ath9k :02:00.0 wlp2s0: disabling VHT as WMM/QoS is not supported by the AP [ 1664.599594] ath9k :02:00.0 wlp2s0: disabling HT as WMM/QoS is not supported by the AP [ 1664.599598] ath9k :02:00.0 wlp2s0: disabling VHT as WMM/QoS is not supported by the AP ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-34-generic 4.4.0-34.53 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tingatinga 3843 F pulseaudio /dev/snd/controlC0: tingatinga 3843 F pulseaudio CurrentDesktop: Unity Date: Sat Aug 27 21:18:54 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=7e8096b7-e5c4-4eec-99dc-065ab5a50e0f InstallationDate: Installed on 2016-08-16 (10 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xer
[Kernel-packages] [Bug 1566302] Re: Ubuntu 16.04: Suspend freezes the system after upgrade to linux image 4.4.0-16
I solved it on my dell 7537 by following this guide https://www.youtube.com/watch?v=l8xa-PkDhhk so I basically just added acpi_osi='!Windows 2013' acpi_osi='!Windows 2012' to my grub configuration. I skipped the acpi_backlight=vendor part because it breaks my backlight shortcut. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1566302 Title: Ubuntu 16.04: Suspend freezes the system after upgrade to linux image 4.4.0-16 Status in linux package in Ubuntu: Won't Fix Bug description: I'm using ubuntu 16.04 on a XPS 15 9550. Suspend/resume worked flawlessly with linux image 4.4.0-15, and after standard upgrade yesterday (5/04/2016) which installed image 4.4.0-16, the system freezes when attempting a suspend. I get no response from the system (nor keyboard, nor screen, nor touchpad), but it gets very hot, so that it must be running something. Booting with 4.4.0-15 makes the suspend to work perfectly. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-16-generic 4.4.0-16.32 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: macias 1770 F pulseaudio CurrentDesktop: X-Cinnamon Date: Tue Apr 5 14:56:17 2016 HibernationDevice: RESUME=UUID=4180adfa-3852-4a96-86b4-f3696448c743 InstallationDate: Installed on 2016-03-07 (28 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcEnviron: LANGUAGE=es_ES PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed root=UUID=673f4658-75f8-4c01-bcd8-0af860269699 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.01.19 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1617599] Re: Resume from suspend causes reboot, except if USB key is plugged in
Sorry but I cannot afford to publicly display the full specifications of my system. Please tell me what you look for in particular. I can provide all the necessary information. Sorry for the inconvenience. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1617599 Title: Resume from suspend causes reboot, except if USB key is plugged in Status in linux package in Ubuntu: Incomplete Bug description: I have been struggling to find out how to get my laptop (Dell M3800) using ubuntu 16.04 to resume from suspend. It goes into suspend (with no errors in /var/log/pm-suspend.log). But when resuming, it immediately reboots, with no errors in /var/log/pm-suspend either. *but* Resume works perfectly when a USB key is plugged in (any key!). PS: I figured that out because suspend/resume works out of the box when using ubuntu 16.04 live CD, but not when using the fresh installed 16.04 afterwards. What's the difference?? There's a key in the USB port in the first case. So I tried suspend/resume with the *installed* version when a USB key is present: it works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1617599/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1531653] Re: Macbook Pro Retina 11, 1 SD Card Reader Doesn't Work
I have a MacBook Pro 13" from 2013, running Debian8 with the backported kernel (4.2). The SD-card reader works randomly: sometimes it is perfectly recognized at boot and works as expected without a glitch as long as you don't suspend/restart the computer. But most of the time (>50% of the boot) the card reader is not recognized. Then inserting a card, nothing in dmesg, not seen in the lsusb, ... and there is a "timeout" message about xhci-hcd (USB3 driver). Are there option to load xhci with longer timeout ? Cheers, Jerome -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1531653 Title: Macbook Pro Retina 11,1 SD Card Reader Doesn't Work Status in linux package in Ubuntu: Incomplete Status in linux package in Debian: New Status in Fedora: Unknown Bug description: I have a Macbook Pro (MBP) Retina 11,1 with an SD card reader that will not work. The SD card reader: * has device code 05ac:8406 * does work in OS X. * does not work in SystemRescueCD running kernel 3.14.56-std461-amd64 - I have a friend with an identical Macbook Pro and his SD card reader does work in SystemRescueCD * Does not show up in lsusb * Does not display any messages in dmesg when an SD card is inserted * Device 05ac:8406 does not show up in dmesg * Does not work in kernel 4.2.0-22.27~14.04.1. All issues reported here seem to be the same regardless if I use 3.13 or 4.2. * Uses the following drivers on my friends MBP: sd, usb-storage, usb, xhci_hcd The last point made me look closer at the xhci_hcd logs: rsyring@loftex:~$ dmesg | grep xhci_hcd [2.681478] xhci_hcd :00:14.0: xHCI Host Controller [2.681498] xhci_hcd :00:14.0: new USB bus registered, assigned bus number 1 [2.681589] xhci_hcd :00:14.0: cache line size of 256 is not supported [2.681607] xhci_hcd :00:14.0: irq 63 for MSI/MSI-X [2.681755] usb usb1: Manufacturer: Linux 3.13.0-57-generic xhci_hcd [2.682098] xhci_hcd :00:14.0: xHCI Host Controller [2.682115] xhci_hcd :00:14.0: new USB bus registered, assigned bus number 2 [2.682219] usb usb2: Manufacturer: Linux 3.13.0-57-generic xhci_hcd [3.980423] usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd [9.352422] xhci_hcd :00:14.0: Timeout while waiting for address device command [ 14.560476] xhci_hcd :00:14.0: Timeout while waiting for address device command [ 20.549170] xhci_hcd :00:14.0: Timeout while waiting for address device command [ 25.757227] xhci_hcd :00:14.0: Timeout while waiting for address device command [ 26.129482] usb 1-1: new high-speed USB device number 2 using xhci_hcd [ 26.321707] usb 1-3: new full-speed USB device number 3 using xhci_hcd [ 26.505802] usb 1-5: new full-speed USB device number 4 using xhci_hcd [ 26.603224] usb 2-1.1: new SuperSpeed USB device number 6 using xhci_hcd [ 26.754245] usb 1-1.2: new low-speed USB device number 5 using xhci_hcd [ 26.954315] usb 1-1.4: new low-speed USB device number 6 using xhci_hcd [ 27.050323] usb 1-3.1: new full-speed USB device number 7 using xhci_hcd [ 27.142383] usb 1-3.2: new full-speed USB device number 8 using xhci_hcd [ 27.234476] usb 1-3.3: new full-speed USB device number 9 using xhci_hcd [ 81.685139] usb 1-1.4: new low-speed USB device number 10 using xhci_hcd The "Timeout while waiting" messages are suspicious to me. dmesg on my friend's MBP does not show those messages. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-57-generic 3.13.0-57.95 ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21 Uname: Linux 3.13.0-57-generic x86_64 NonfreeKernelModules: wl zfs zunicode zcommon znvpair zavl ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rsyring5051 F pulseaudio /dev/snd/controlC0: rsyring5051 F pulseaudio CurrentDesktop: XFCE Date: Wed Jan 6 17:57:28 2016 HibernationDevice: RESUME=UUID=8b8a41c8-2030-4f92-b7d6-1143a081ec85 InstallationDate: Installed on 2014-02-15 (690 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) MachineType: Apple Inc. MacBookPro11,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: \vmlinuz-3.13.0-57-generic.efi.signed root=ZFS=/ROOT ro libata.force=noncq cryptopts=target=cryptdev,source=/dev/disk/by-uuid/6993c5ec-7308-420d-bbe2-1ed18c15e2bc,discard boot=zfs initrd=\initrd.img-3.13.0-57-generic RelatedPackageVersions: linux-restricted-modules-3.13.0-57-generic N/A linux-backports-modules-3.13.0-57-generic N/A linux-firmware 1.127.19 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-07-21 (534 days ago) dmi.bios.date: 09/08/2015 dmi.bios.vendor:
[Kernel-packages] [Bug 1568729] Re: divide error: 0000 [#1] SMP in task_numa_migrate - handle_mm_fault
So jujud exercises the same code path as ceph-osd? curious -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1568729 Title: divide error: [#1] SMP in task_numa_migrate - handle_mm_fault Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Bug description: While running qemu 2.5 on a trusty host running 4.4.0-15.31~14.04.1 the host system has crashed (load > 200) 3 times in the last 3 days. Always with this stack trace: Apr 9 19:01:09 cnode9.0 kernel: [197071.195577] divide error: [#1] SMP Apr 9 19:01:09 cnode9.0 kernel: [197071.195633] Modules linked in: vhost_net vhost macvtap macvlan arc4 md4 nls_utf8 ci fs nfnetlink_queue nfnetlink xt_CHECKSUM xt_nat iptable_nat nf_nat_ipv4 xt_NFQUEUE xt_CLASSIFY ip6table_mangle sch_sfq sch_htb veth dccp_diag dccp tcp_diag udp_diag inet_diag unix_diag af_packet_diag netlink_diag ebtable_filter ebtables nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_fil ter ip6_tables iptable_mangle xt_CT iptable_raw xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack iptable_filter ip_tables x_tables dum my bridge stp llc ipmi_ssif ipmi_devintf intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm dcdbas irqbypass crct10dif_p clmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd joydev input_leds nf_nat_ftp sb_edac nf_conntrack_ftp e dac_core cdc_ether nf_nat_pptp usbnet nf_conntrack_pptp mii nf_nat_proto_gre lpc_ich nf_nat_sip ioatdma nf_nat nf_conntrack_sip nfsd ipmi_si 8250_fintek nf_conntrack_proto_gre ipmi_msghandler acpi_pad wmi shpchp nf_conntrack acpi_power_meter mac_hid auth_rpcgss nfs_acl bonding nfs lp lockd parport grace sunrpc fscache tcp_htcp xfs btrfs hid_generic usbhid hid raid10 raid456 async_raid6_recov async_memcpy async_pq async_ xor async_tx xor ixgbe raid6_pq libcrc32c igb vxlan raid1 i2c_algo_bit ip6_udp_tunnel dca udp_tunnel ahci raid0 ptp libahci megaraid_sas mult ipath pps_core mdio linear fjes Apr 9 19:01:09 cnode9.0 kernel: [197071.197014] CPU: 13 PID: 3147726 Comm: ceph-osd Not tainted 4.4.0-15-generic #31~14 .04.1-Ubuntu Apr 9 19:01:09 cnode9.0 kernel: [197071.197085] Hardware name: Dell Inc. PowerEdge R720/0XH7F2, BIOS 2.5.2 01/28/2015 Apr 9 19:01:09 cnode9.0 kernel: [197071.197154] task: 88252be1ee00 ti: 8824fc0d4000 task.ti: 8824fc0d4000 Apr 9 19:01:09 cnode9.0 kernel: [197071.197221] RIP: 0010:[] [] task_numa_find_cpu+0x238/0x700 Apr 9 19:01:09 cnode9.0 kernel: [197071.197300] RSP: :8824fc0d7ba8 EFLAGS: 00010257 Apr 9 19:01:09 cnode9.0 kernel: [197071.197340] RAX: RBX: 8824fc0d7c48 RCX: Apr 9 19:01:09 cnode9.0 kernel: [197071.197406] RDX: RSI: 88479f18 RDI: 884782a47600 Apr 9 19:01:09 cnode9.0 kernel: [197071.197473] RBP: 8824fc0d7c10 R08: 000102eea157 R09: 01a8 Apr 9 19:01:09 cnode9.0 kernel: [197071.197540] R10: 0002404b R11: 023f R12: 88238093 Apr 9 19:01:09 cnode9.0 kernel: [197071.197606] R13: 0008 R14: 008c R15: 0124 Apr 9 19:01:09 cnode9.0 kernel: [197071.197673] FS: 7f19aab5b700() GS:88479f18() knlGS: Apr 9 19:01:09 cnode9.0 kernel: [197071.197741] CS: 0010 DS: ES: CR0: 80050033 Apr 9 19:01:09 cnode9.0 kernel: [197071.197782] CR2: 25469600 CR3: 0023846bc000 CR4: 000426e0 Apr 9 19:01:09 cnode9.0 kernel: [197071.197848] Stack: Apr 9 19:01:09 cnode9.0 kernel: [197071.197880] 817425fb 8829af3e9e00 00f6 88252be1ee00 Apr 9 19:01:09 cnode9.0 kernel: [197071.197965] 008d 0225 00016d40 008d Apr 9 19:01:09 cnode9.0 kernel: [197071.198047] 88252be1ee00 01ad 8824fc0d7c48 00e1 Apr 9 19:01:09 cnode9.0 kernel: [197071.198132] Call Trace: Apr 9 19:01:09 cnode9.0 kernel: [197071.198172] [] ? tcp_schedule_loss_probe+0x12b/0x1b0 Apr 9 19:01:09 cnode9.0 kernel: [197071.198219] [] task_numa_migrate+0x4a0/0x930 Apr 9 19:01:09 cnode9.0 kernel: [197071.198264] [] ? release_sock+0x117/0x160 Apr 9 19:01:09 cnode9.0 kernel: [197071.198306] [] numa_migrate_preferred+0x79/0x80 Apr 9 19:01:09 cnode9.0 kernel: [197071.198350] [] task_numa_fault+0x91d/0xcc0 Apr 9 19:01:09 cnode9.0 kernel: [197071.198395] [] ? mpol_misplaced+0x14e/0x190 Apr 9 19:01:09 cnode9.0 kernel: [197071.198439] [] handle_pte_fault+0x5a8/0x14c0 Apr 9 19:01:09 cnode9.0 kernel: [197071.198485] [] ? futex_wake+0x81/0x150 Apr 9 19:01:09 cnode9.0 kernel: [197071.198526] [] ? set_next_entity+0xa4/0x700 Apr 9 19:01:09 cnode9.0 kernel: [197071.198569] [] ? do_futex+0xf4/0x4
[Kernel-packages] [Bug 1617599] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1617599 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1617599 Title: Resume from suspend causes reboot, except if USB key is plugged in Status in linux package in Ubuntu: Incomplete Bug description: I have been struggling to find out how to get my laptop (Dell M3800) using ubuntu 16.04 to resume from suspend. It goes into suspend (with no errors in /var/log/pm-suspend.log). But when resuming, it immediately reboots, with no errors in /var/log/pm-suspend either. *but* Resume works perfectly when a USB key is plugged in (any key!). PS: I figured that out because suspend/resume works out of the box when using ubuntu 16.04 live CD, but not when using the fresh installed 16.04 afterwards. What's the difference?? There's a key in the USB port in the first case. So I tried suspend/resume with the *installed* version when a USB key is present: it works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1617599/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1617599] [NEW] Resume from suspend causes reboot, except if USB key is plugged in
Public bug reported: I have been struggling to find out how to get my laptop (Dell M3800) using ubuntu 16.04 to resume from suspend. It goes into suspend (with no errors in /var/log/pm-suspend.log). But when resuming, it immediately reboots, with no errors in /var/log/pm-suspend either. *but* Resume works perfectly when a USB key is plugged in (any key!). PS: I figured that out because suspend/resume works out of the box when using ubuntu 16.04 live CD, but not when using the fresh installed 16.04 afterwards. What's the difference?? There's a key in the USB port in the first case. So I tried suspend/resume with the *installed* version when a USB key is present: it works. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1617599 Title: Resume from suspend causes reboot, except if USB key is plugged in Status in linux package in Ubuntu: Incomplete Bug description: I have been struggling to find out how to get my laptop (Dell M3800) using ubuntu 16.04 to resume from suspend. It goes into suspend (with no errors in /var/log/pm-suspend.log). But when resuming, it immediately reboots, with no errors in /var/log/pm-suspend either. *but* Resume works perfectly when a USB key is plugged in (any key!). PS: I figured that out because suspend/resume works out of the box when using ubuntu 16.04 live CD, but not when using the fresh installed 16.04 afterwards. What's the difference?? There's a key in the USB port in the first case. So I tried suspend/resume with the *installed* version when a USB key is present: it works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1617599/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1531653] Re: Macbook Pro Retina 11, 1 SD Card Reader Doesn't Work
** Also affects: linux (Debian) 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/1531653 Title: Macbook Pro Retina 11,1 SD Card Reader Doesn't Work Status in linux package in Ubuntu: Incomplete Status in linux package in Debian: New Status in Fedora: Unknown Bug description: I have a Macbook Pro (MBP) Retina 11,1 with an SD card reader that will not work. The SD card reader: * has device code 05ac:8406 * does work in OS X. * does not work in SystemRescueCD running kernel 3.14.56-std461-amd64 - I have a friend with an identical Macbook Pro and his SD card reader does work in SystemRescueCD * Does not show up in lsusb * Does not display any messages in dmesg when an SD card is inserted * Device 05ac:8406 does not show up in dmesg * Does not work in kernel 4.2.0-22.27~14.04.1. All issues reported here seem to be the same regardless if I use 3.13 or 4.2. * Uses the following drivers on my friends MBP: sd, usb-storage, usb, xhci_hcd The last point made me look closer at the xhci_hcd logs: rsyring@loftex:~$ dmesg | grep xhci_hcd [2.681478] xhci_hcd :00:14.0: xHCI Host Controller [2.681498] xhci_hcd :00:14.0: new USB bus registered, assigned bus number 1 [2.681589] xhci_hcd :00:14.0: cache line size of 256 is not supported [2.681607] xhci_hcd :00:14.0: irq 63 for MSI/MSI-X [2.681755] usb usb1: Manufacturer: Linux 3.13.0-57-generic xhci_hcd [2.682098] xhci_hcd :00:14.0: xHCI Host Controller [2.682115] xhci_hcd :00:14.0: new USB bus registered, assigned bus number 2 [2.682219] usb usb2: Manufacturer: Linux 3.13.0-57-generic xhci_hcd [3.980423] usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd [9.352422] xhci_hcd :00:14.0: Timeout while waiting for address device command [ 14.560476] xhci_hcd :00:14.0: Timeout while waiting for address device command [ 20.549170] xhci_hcd :00:14.0: Timeout while waiting for address device command [ 25.757227] xhci_hcd :00:14.0: Timeout while waiting for address device command [ 26.129482] usb 1-1: new high-speed USB device number 2 using xhci_hcd [ 26.321707] usb 1-3: new full-speed USB device number 3 using xhci_hcd [ 26.505802] usb 1-5: new full-speed USB device number 4 using xhci_hcd [ 26.603224] usb 2-1.1: new SuperSpeed USB device number 6 using xhci_hcd [ 26.754245] usb 1-1.2: new low-speed USB device number 5 using xhci_hcd [ 26.954315] usb 1-1.4: new low-speed USB device number 6 using xhci_hcd [ 27.050323] usb 1-3.1: new full-speed USB device number 7 using xhci_hcd [ 27.142383] usb 1-3.2: new full-speed USB device number 8 using xhci_hcd [ 27.234476] usb 1-3.3: new full-speed USB device number 9 using xhci_hcd [ 81.685139] usb 1-1.4: new low-speed USB device number 10 using xhci_hcd The "Timeout while waiting" messages are suspicious to me. dmesg on my friend's MBP does not show those messages. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-57-generic 3.13.0-57.95 ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21 Uname: Linux 3.13.0-57-generic x86_64 NonfreeKernelModules: wl zfs zunicode zcommon znvpair zavl ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rsyring5051 F pulseaudio /dev/snd/controlC0: rsyring5051 F pulseaudio CurrentDesktop: XFCE Date: Wed Jan 6 17:57:28 2016 HibernationDevice: RESUME=UUID=8b8a41c8-2030-4f92-b7d6-1143a081ec85 InstallationDate: Installed on 2014-02-15 (690 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) MachineType: Apple Inc. MacBookPro11,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: \vmlinuz-3.13.0-57-generic.efi.signed root=ZFS=/ROOT ro libata.force=noncq cryptopts=target=cryptdev,source=/dev/disk/by-uuid/6993c5ec-7308-420d-bbe2-1ed18c15e2bc,discard boot=zfs initrd=\initrd.img-3.13.0-57-generic RelatedPackageVersions: linux-restricted-modules-3.13.0-57-generic N/A linux-backports-modules-3.13.0-57-generic N/A linux-firmware 1.127.19 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-07-21 (534 days ago) dmi.bios.date: 09/08/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP111.88Z.0138.B16.1509081438 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B16.1509081438:bd09/08/2015:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F9
[Kernel-packages] [Bug 1451246] Re: Intel 7265 Wifi instability workaround
I'm using ASUS UX 305F with Intel Intel Corporation Dual Band Wireless- AC 7265 and having similar issues With Mint 18 (Ubuntu Xenial) I'm with kernel 4.4.0-21-generic (and problems still occurs form 3.x) I did workaround this by disabling N Wireless :( -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1451246 Title: Intel 7265 Wifi instability workaround Status in linux package in Ubuntu: Invalid Bug description: I have a Thinkpad T450s since 5/1/2015 (though linux wants the 7265D ucode though). It was unstable, even when upgrading to the 4.0.1 mainline kernel. Using the latest 7265 firmware improved things, but things like streams, speed tests, and youtube would tank the connection: retrieve the latest linux-firmware from their git: http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git (git clone https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git) sudo rm /lib/firmware/iwlwifi* sudo cp /path/to//iwlwifi-7265*-12.ucode /lib/firmware/. reboot WORKAROUND: Disable 802.11n: echo 'options iwlwifi 11n_disable=1' | sudo tee -a /etc/modprobe.d/iwlwifi.conf ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-15-generic 3.19.0-15.15 [modified: boot/vmlinuz-3.19.0-15-generic] ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: epicstar 1453 F pulseaudio /dev/snd/pcmC1D0p: epicstar 1453 F...m pulseaudio /dev/snd/controlC1: epicstar 1453 F pulseaudio CurrentDesktop: Unity Date: Sun May 3 15:43:35 2015 HibernationDevice: RESUME=UUID=9caf85bf-266f-4356-9a64-031df7edb239 InstallationDate: Installed on 2015-05-02 (1 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 20BXCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic.efi.signed root=UUID=b8187455-26c0-492f-bf45-755286cf5623 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-15-generic N/A linux-backports-modules-3.19.0-15-generic N/A linux-firmware 1.143 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: 03/10/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET47WW (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET47WW(1.12):bd03/10/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451246/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1585081] Re: Switching user freezes system
Hi, I have exactly the same problem with 14.04, with 16.04 it doens't freeze but I have just the icon (and not all) in the windows, without the text below it. Same bug here : https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1247189 ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1585081 Title: Switching user freezes system Status in linux package in Ubuntu: Expired Bug description: Just doing this my system freezes: 1. Click on the top right gear icon. 2. Select a different user account. Login screen appears briefly, then black screen and the system is death: BUG: unable to handle kernel NULL pointer dereference at 0248 IP: [] amdgpu_vm_grab_id+0x122/0x310 [amdgpu] PGD 0 Oops: [#1] SMP Modules linked in: ... (See attached syslog for more) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 2739 F pulseaudio /dev/snd/controlC1: david 2739 F pulseaudio CurrentDesktop: Unity Date: Tue May 24 08:54:13 2016 HibernationDevice: RESUME=UUID=d225720a-fc40-49a3-9182-17d278d40460 InstallationDate: Installed on 2015-06-29 (329 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: TOSHIBA SATELLITE S50-B ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-22 (31 days ago) dmi.bios.date: 12/02/2014 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 2.00 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr2.00:bd12/02/2014:svnTOSHIBA:pnSATELLITES50-B:pvrPSPQEE-00F00JEN:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.name: SATELLITE S50-B dmi.product.version: PSPQEE-00F00JEN dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1585081/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1566302] Re: Ubuntu 16.04: Suspend freezes the system after upgrade to linux image 4.4.0-16
This also affected me, on Lenovo G580, kernel 4.4.0-34-generic. However, I think I fixed it by appending "nomodeset" to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub, then running sudo update-grub as per http://askubuntu.com/a/722653/478436. @ileyka/#112 - I was experiencing similar problems with blank TTYs; you could try the solution I mentioned above. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1566302 Title: Ubuntu 16.04: Suspend freezes the system after upgrade to linux image 4.4.0-16 Status in linux package in Ubuntu: Won't Fix Bug description: I'm using ubuntu 16.04 on a XPS 15 9550. Suspend/resume worked flawlessly with linux image 4.4.0-15, and after standard upgrade yesterday (5/04/2016) which installed image 4.4.0-16, the system freezes when attempting a suspend. I get no response from the system (nor keyboard, nor screen, nor touchpad), but it gets very hot, so that it must be running something. Booting with 4.4.0-15 makes the suspend to work perfectly. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-16-generic 4.4.0-16.32 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: macias 1770 F pulseaudio CurrentDesktop: X-Cinnamon Date: Tue Apr 5 14:56:17 2016 HibernationDevice: RESUME=UUID=4180adfa-3852-4a96-86b4-f3696448c743 InstallationDate: Installed on 2016-03-07 (28 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcEnviron: LANGUAGE=es_ES PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed root=UUID=673f4658-75f8-4c01-bcd8-0af860269699 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.01.19 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1617567] [NEW] unable to use bluetooth on Dell Latitude E6410 with Ubuntu 16
Public bug reported: all settings >> bluetooth = No bluetooth adapters found and Bluetooth switch is greyed out #systemctl start bluetooth.service #/etc/init.d/bluetoothd start after running both the above commands, the service still doesn't start ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Aug 27 18:36:28 2016 InstallationDate: Installed on 2016-08-26 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) InterestingModules: bluetooth Lsusb: Bus 002 Device 003: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude E6410 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic root=UUID=3690b1df-8453-4404-bd9b-6735f9f23658 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to xenial on 2016-08-26 (0 days ago) dmi.bios.date: 12/05/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0667CC dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd12/05/2013:svnDellInc.:pnLatitudeE6410:pvr0001:rvnDellInc.:rn0667CC:rvrA03:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6410 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. hciconfig: mtime.conffile..etc.bluetooth.main.conf: 2016-08-27T16:24:16.848700 ** Affects: bluez (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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1617567 Title: unable to use bluetooth on Dell Latitude E6410 with Ubuntu 16 Status in bluez package in Ubuntu: New Bug description: all settings >> bluetooth = No bluetooth adapters found and Bluetooth switch is greyed out #systemctl start bluetooth.service #/etc/init.d/bluetoothd start after running both the above commands, the service still doesn't start ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Aug 27 18:36:28 2016 InstallationDate: Installed on 2016-08-26 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) InterestingModules: bluetooth Lsusb: Bus 002 Device 003: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude E6410 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic root=UUID=3690b1df-8453-4404-bd9b-6735f9f23658 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to xenial on 2016-08-26 (0 days ago) dmi.bios.date: 12/05/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0667CC dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd12/05/2013:svnDellInc.:pnLatitudeE6410:pvr0001:rvnDellInc.:rn0667CC:rvrA03:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6410 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. hciconfig: mtime.conffile..etc.bluetooth.main.conf: 2016-08-27T16:24:16.848700 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1617567/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1594023] Re: Poweroff or reboot hangs. Laptop won't shutdown. 16.04
Hello, I have exact the same problem with ASUS notebook. Is there any quick fix for it? GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=force" didn't help me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1594023 Title: Poweroff or reboot hangs. Laptop won't shutdown. 16.04 Status in linux package in Ubuntu: Confirmed Bug description: This is about a fresh Ubuntu 16.04 install on a new laptop (asus x540sa). After pressing the shutdown button in the start menu; the shutdown procedure starts and in the final splash screen the system just hangs. Tried a second time by pressing Esc once the splash screen showed up and I saw that it reaches the line "Reached target shutdown" and just stops there, no matter how long I leave it there the machine won't turn off. I also tried a Kubuntu 16.04 fresh install on the same machine and it hanged too at the final splash screen where the pulsating logo stopped. Then I tried with Esc only to see the exact same line in the end. The issue seems to affect lately quite many users as shown by the google results of the past month / week or so. I have also tried shutting down from the console with shutdown -and all the parameters after that suggested online- and sudo poweroff but unfortunately they didn't do the trick. The exact same situation occurred. Unmounting the swap as suggested online doesn't work. Also rebooting the system is not working either due to the same issue. So right now the only way for me to poweroff the machine is to press the power button on the keyboard continuously. Reproducible: Always Steps to Reproduce: 1.Install OS 2.Do something, anything or nothing 3.Try to shutdown or reboot Actual Results: The computer is not shutting down: "Reached target shutdown" and hangs there. Expected Results: Powering off the machine. For what it's worth, closing the lid won't suspend the system, but using the menu buttons for suspension will do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1594023/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1617550] Re: Kernel Build Fails for Fuse Module
I am unable to run this command. ** 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/1617550 Title: Kernel Build Fails for Fuse Module Status in linux package in Ubuntu: Confirmed Bug description: ERROR: "current_in_userns" [fs/fuse/fuse.ko] undefined! /root/linux-4.4.0/scripts/Makefile.modpost:91: recipe for target '__modpost' failed make[3]: *** [__modpost] Error 1 /root/linux-4.4.0/Makefile:1112: recipe for target 'modules' failed make[2]: *** [modules] Error 2 make[2]: Leaving directory '/root/linux-4.4.0/debian/build/build-generic' Makefile:146: recipe for target 'sub-make' failed make[1]: *** [sub-make] Error 2 make[1]: Leaving directory '/root/linux-4.4.0' debian/rules.d/2-binary-arch.mk:70: recipe for target '/root/linux-4.4.0/debian/stamps/stamp-build-generic' failed make: *** [/root/linux-4.4.0/debian/stamps/stamp-build-generic] Error 2 Confirmed working using the following diff: https://www.redhat.com/archives/dm-devel/2016-April/msg00388.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1617550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1172852] Re: USB keyboard and mouse don't work
In the meantime I can confirm, that my modifications as described in comment #39 of 2016-03-27 resulted in a stable Lubuntu 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/1172852 Title: USB keyboard and mouse don't work Status in linux package in Ubuntu: Confirmed Bug description: I am installing Ubuntu 13.04 from a live USB key. I downloaded the stable amd64 iso of Ubuntu 13.04 after it was released today. It runs beautifully from a live USB key. However, after installing the OS to my hard drive and rebooting, the keyboard and mouse both fail to work. They are standard USB input devices (US layout) which have worked for years on other versions of Red Hat and Ubuntu. They work fine with the live USB version of the OS. I can't even log into the computer to collect bug data. I've tried reinstalling several times, changing the install options. Installing fresh on this computer, keeping only my old /home partition, and disallowing the installation of third-party software still produces the error. The same system has run several previous versions of Ubuntu without problems. Thanks for your help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1172852/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1617550] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1617550 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1617550 Title: Kernel Build Fails for Fuse Module Status in linux package in Ubuntu: Incomplete Bug description: ERROR: "current_in_userns" [fs/fuse/fuse.ko] undefined! /root/linux-4.4.0/scripts/Makefile.modpost:91: recipe for target '__modpost' failed make[3]: *** [__modpost] Error 1 /root/linux-4.4.0/Makefile:1112: recipe for target 'modules' failed make[2]: *** [modules] Error 2 make[2]: Leaving directory '/root/linux-4.4.0/debian/build/build-generic' Makefile:146: recipe for target 'sub-make' failed make[1]: *** [sub-make] Error 2 make[1]: Leaving directory '/root/linux-4.4.0' debian/rules.d/2-binary-arch.mk:70: recipe for target '/root/linux-4.4.0/debian/stamps/stamp-build-generic' failed make: *** [/root/linux-4.4.0/debian/stamps/stamp-build-generic] Error 2 Confirmed working using the following diff: https://www.redhat.com/archives/dm-devel/2016-April/msg00388.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1617550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 974090] They kill with wars, alcohol and abortions. Save us!!!
They kill with wars, alcohol and abortions. Save us!!! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/974090 Title: ALSA: HDA: Virtual master gets wrong dB values on some Realtek codecs Status in linux package in Ubuntu: Fix Released Bug description: Please do not triage this bug, it's being used for tracking purposes. What's happening here is that the wrong node is being used as a template when the vmaster ("Master" alsa mixer control) is created. This patch makes the parser use the mixer nid that the auto-parser has detected instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/974090/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1617550] [NEW] Kernel Build Fails for Fuse Module
Public bug reported: ERROR: "current_in_userns" [fs/fuse/fuse.ko] undefined! /root/linux-4.4.0/scripts/Makefile.modpost:91: recipe for target '__modpost' failed make[3]: *** [__modpost] Error 1 /root/linux-4.4.0/Makefile:1112: recipe for target 'modules' failed make[2]: *** [modules] Error 2 make[2]: Leaving directory '/root/linux-4.4.0/debian/build/build-generic' Makefile:146: recipe for target 'sub-make' failed make[1]: *** [sub-make] Error 2 make[1]: Leaving directory '/root/linux-4.4.0' debian/rules.d/2-binary-arch.mk:70: recipe for target '/root/linux-4.4.0/debian/stamps/stamp-build-generic' failed make: *** [/root/linux-4.4.0/debian/stamps/stamp-build-generic] Error 2 Confirmed working using the following diff: https://www.redhat.com/archives/dm-devel/2016-April/msg00388.html ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1617550 Title: Kernel Build Fails for Fuse Module Status in linux package in Ubuntu: New Bug description: ERROR: "current_in_userns" [fs/fuse/fuse.ko] undefined! /root/linux-4.4.0/scripts/Makefile.modpost:91: recipe for target '__modpost' failed make[3]: *** [__modpost] Error 1 /root/linux-4.4.0/Makefile:1112: recipe for target 'modules' failed make[2]: *** [modules] Error 2 make[2]: Leaving directory '/root/linux-4.4.0/debian/build/build-generic' Makefile:146: recipe for target 'sub-make' failed make[1]: *** [sub-make] Error 2 make[1]: Leaving directory '/root/linux-4.4.0' debian/rules.d/2-binary-arch.mk:70: recipe for target '/root/linux-4.4.0/debian/stamps/stamp-build-generic' failed make: *** [/root/linux-4.4.0/debian/stamps/stamp-build-generic] Error 2 Confirmed working using the following diff: https://www.redhat.com/archives/dm-devel/2016-April/msg00388.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1617550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1592442] Re: Ubuntu 16.04 Xenial hard crashing on ACER E3-11-P0D8
I had the same issue on an Acer E3-111. Problem was resolved with an update to the latest BIOS. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1592442 Title: Ubuntu 16.04 Xenial hard crashing on ACER E3-11-P0D8 Status in linux package in Ubuntu: Confirmed Bug description: About a month ago I installed the latest Ubuntu 16.04 Xenial on my ACER E3-11-P0D8 laptop. Since then, it randomly freeze up while I work. It generally takes 10-20 mins to do that. Out of frustration, I started to change the kernel. It seems that every >4.0 kernel is freezing up my system. Now i am stable at 3.19.8 from here: http://kernel.ubuntu.com/~kernel-ppa/mainline/ Please note: When using old kernel ( 3.19.8 ) i have no crash. But when i use the latest one, it freeze up and i can not use anything ( no kernel panic, no terminal, nothing, keyboard mouse doesn't work ). The freeze happens very randomly. It can take 5 mins or hours after working. And it takes me to switch off the laptop and start it again. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-24-generic 4.4.0-24.43 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: saif 1431 F pulseaudio Date: Tue Jun 14 20:39:57 2016 HibernationDevice: RESUME=UUID=f2e69a50-3159-4db7-be6b-10bc5072fc65 InstallationDate: Installed on 2016-05-14 (31 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b48a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire E3-112 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=665e2c47-366b-4bc0-9142-8ae6796d1b72 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: R2 dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd08/20/2014:svnAcer:pnAspireE3-112:pvrV1.10:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire E3-112 dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1592442/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1470091] Re: update for V3 kernel bits and improved multiple fan slice support
** No longer affects: linux-lts-utopic (Ubuntu) ** Changed in: linux (Ubuntu Trusty) Importance: Undecided => High ** No longer affects: linux-lts-utopic (Ubuntu Vivid) ** No longer affects: linux-lts-utopic (Ubuntu Wily) ** No longer affects: linux-lts-vivid (Ubuntu) ** No longer affects: linux-lts-vivid (Ubuntu Vivid) ** No longer affects: linux-lts-vivid (Ubuntu Wily) ** Changed in: linux-lts-utopic (Ubuntu Trusty) Importance: Undecided => High ** Changed in: linux-lts-vivid (Ubuntu Trusty) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1470091 Title: update for V3 kernel bits and improved multiple fan slice support Status in iproute2 package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in ubuntu-fan package in Ubuntu: Fix Released Status in iproute2 source package in Trusty: Fix Released Status in linux source package in Trusty: New Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: Fix Released Status in ubuntu-fan source package in Trusty: Fix Released Status in iproute2 source package in Vivid: Fix Released Status in linux source package in Vivid: Fix Released Status in ubuntu-fan source package in Vivid: Fix Released Status in iproute2 source package in Wily: Fix Released Status in linux source package in Wily: Fix Released Status in ubuntu-fan source package in Wily: Fix Released Bug description: Fan V2 to V3 transition plan Currently we have V2 Fan kernel patches paired with an /etc/defaults/ubuntu-fan based single fan mapping setup. We want to transition to both V3 Fan kernel patches with fanctl based configuration allowing multiple fans to be configured together. The new V3 kernel bits fix a significant limitation wherein we could not have multiple slices of different overlay address ranges on the same local address. This update introduces an incompatible kernel interface against a different device. The new functionality is a full superset of the old. The new V3 kernel bits require updated iproute2 patches to handle the new netlink form carrying the expanded map forms. In order to manage multiple Fan devices we are updating ubuntu-fan to use the new fanctl command line tool and a new fan specific configuration file. This plan assumes we are not wedded to the kernel interface, that the supported API is the /etc/defaults/ubuntu-fan fan configuration. Considerations == We are unable to depend on kernel features, as we have no meaninful dependencies to kernel versions. We need to change the primary configuration file and format for ubuntu-fan package to allow multiple slices of multiple fans to be configured together. We have V2 kernel bits in the wild. We have V2 iproute in the wild. Steps = 1) update fanctl to support both the V2 and V3 kernel interfaces as we cannot depend on a kernel version meaningfully. 2) update iproute2 to support configuring both V2 and V3 kernel interfaces. 3) update ubuntu-fan with the updated fanctl, supporting migration of the /etc/default/fan contents to /etc/network/fan (or directly handling that form), and depending on the updated iproute2 bits. 4) release updated iproute2 bits. 5) release updated ubuntu-fan bits. 6) release updated kernel bits (V3 kernel module). Testing === Need to test old and new kernels with old and new ubuntu-fan levels. We obviously do not expect the old userspace to work with the new kernels, but it should fail obviously. === Discussions on this with the Ubuntu Tech Board are in the thread below: https://lists.ubuntu.com/archives/technical- board/2015-July/002122.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1470091/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1559576] Re: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers on a laptop with Optimus
Indeed, I get the same experience with Yakkety. "Kinda funky" means, running my system, that Nvidia boots fine but Intel can lead to a login loop (not reproduced) and surely to a Xorg crash (but only Apport makes me knowing that there is one, except maybe the deactivation of some Gnome shell's extensions). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1559576 Title: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers on a laptop with Optimus Status in gdm: Confirmed Status in Ubuntu GNOME: Triaged Status in gdm3 package in Ubuntu: Triaged Status in linux package in Ubuntu: Invalid Status in gdm3 source package in Xenial: Triaged Status in linux source package in Xenial: Invalid Bug description: Using latest Ubuntu Gnome x64 daily build with all updates installed. Lenovo Z70-80 laptop with Nvidia 840M, BIOS updated to latest version, secure boot and other potentially problematic BIOS settings disabled. Can only see a black screen instead of a log-in screen after boot completes when proprietary Nvidia drivers are installed. Regular Ubuntu works absolutely fine on the same machine with the same driver version. Attempting to use older drivers on Ubuntu Gnome made no difference. Bug is affecting more than just me. We were talking about workarounds in ubuntuforums. User fthx claims that switching to lightdm fixes the issue http://ubuntuforums.org/showthread.php?t=2317628&p=13457703#post13457703 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-14-generic 4.4.0-14.30 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-14-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Sat Mar 19 23:19:21 2016 HibernationDevice: RESUME=UUID=4f8fb76c-f99d-4c54-8a67-eed0653d8eb6 InstallationDate: Installed on 2016-03-19 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160318) MachineType: LENOVO 80FG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-14-generic.efi.signed root=UUID=572a19f6-7324-4269-ad36-7ffc9919f7a2 ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-14-generic N/A linux-backports-modules-4.4.0-14-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: ABCN96WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo Z70-80 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z70-80 dmi.modalias: dmi:bvnLENOVO:bvrABCN96WW:bd09/22/2015:svnLENOVO:pn80FG:pvrLenovoZ70-80:rvnLENOVO:rnLenovoZ70-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoZ70-80: dmi.product.name: 80FG dmi.product.version: Lenovo Z70-80 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1559576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp