[Kernel-packages] [Bug 1407913] [NEW] In 3840x2160 high resolution mode, display would blink with Chrome / Chromium browser opened, or with certain page in Firefox
Public bug reported: CID: 201410-15952 Dell Inspiron 7548 I'm not sure which package to blame with, I guess maybe it has something to do with X, thing is: when the system is running in 3840*2160 resolution, the display will blink with these browsers under certain conditions. Steps: 1. Install 14.04.1 + update + Chromium + Chrome 2. Make sure it's running with the highest resolution and open Chrome (39.0.2171.95-1) 3. Make sure it's running with the highest resolution and open Chromium (39.0.2171.65-0ubuntu0.14.04.1.1064) 4. Make sure it's running with the highest resolution and open Firefox (34.0+build2-0ubuntu0.14.04.1) 5. Switch to the second-highest resolution mode and repeat 2-4 Expected result: * Every browser should not intefere the display on this system. Actual result: * On step 2, display blinks right after Chrome opened, back to normal when you close the browser * On step 3, display blinks right after Chromium opened, back to normal when you close the browser * On step 4, it won't blink, but if you visit https://bugzilla.mozilla.org/show_bug.cgi?id=1118140 with 100% zoom scale in Firefox, it will blink. If you zoom in or out with ctrl +/- or close it, the display will back to normal. * On step 5, non of them will make the display blink Note that when it's blinking, you can switch to console with Ctrl + Alt + F1 without any problem. And this happen to Firefox on some other pages as well. Verified with: 3.16.0-28 + open source video driver the latest mainline kernel 3.19.0-rc3 + open source video driver 3.13.0-43 + open source video driver 3.13.0-43 + the latest AMD video driver (14.501.1003) in both power-saving and performance mode they all have the same behaviour. Please find the attachment for screencast from step 2 to 4. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-43-generic 3.13.0-43.72 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1766 F pulseaudio /dev/snd/controlC0: ubuntu 1766 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Tue Jan 6 03:43:19 2015 HibernationDevice: RESUME=UUID=3121f09d-4ad7-4946-b905-ee8e56a6d914 InstallationDate: Installed on 2015-01-05 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Inspiron 7548 ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic.efi.signed root=UUID=57666a30-96f3-478b-b3c1-3879ce81c53f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-43-generic N/A linux-backports-modules-3.13.0-43-generic N/A linux-firmware 1.127.11 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: BBE4C1 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.:bvrA00:bd11/19/2014:svnDellInc.:pnInspiron7548:pvrA00:rvnDellInc.:rnBBE4C1:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 7548 dmi.product.version: A00 dmi.sys.vendor: Dell Inc. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Medium Assignee: Anthony Wong (anthonywong) Status: Confirmed ** Tags: 201410-15952 amd64 apport-bug blocks-hwcert taipei-lab trusty ** Attachment added: Screencast.webm https://bugs.launchpad.net/bugs/1407913/+attachment/4292785/+files/Screencast.webm ** Also affects: hwe-next 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/1407913 Title: In 3840x2160 high resolution mode, display would blink with Chrome / Chromium browser opened, or with certain page in Firefox Status in HWE Next Project: New Status in linux package in Ubuntu: Confirmed Bug description: CID: 201410-15952 Dell Inspiron 7548 I'm not sure which package to blame with, I guess maybe it has something to do with X, thing is: when the system is running in 3840*2160 resolution, the display will blink with these browsers under certain conditions. Steps: 1. Install 14.04.1 + update + Chromium + Chrome 2. Make sure it's running with the highest resolution and open Chrome (39.0.2171.95-1) 3. Make sure it's running with the highest resolution and open Chromium (39.0.2171.65-0ubuntu0.14.04.1.1064) 4. Make sure it's running with the highest resolution and open Firefox
[Kernel-packages] [Bug 1407913] Re: In 3840x2160 high resolution mode, display would blink with Chrome / Chromium browser opened, or with certain page in Firefox
Some error message could be found in dmesg output, but they won't be generated when this happens ** Attachment added: dmesg.log https://bugs.launchpad.net/hwe-next/+bug/1407913/+attachment/4292806/+files/dmesg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1407913 Title: In 3840x2160 high resolution mode, display would blink with Chrome / Chromium browser opened, or with certain page in Firefox Status in HWE Next Project: New Status in linux package in Ubuntu: Confirmed Bug description: CID: 201410-15952 Dell Inspiron 7548 I'm not sure which package to blame with, I guess maybe it has something to do with X, thing is: when the system is running in 3840*2160 resolution, the display will blink with these browsers under certain conditions. Steps: 1. Install 14.04.1 + update + Chromium + Chrome 2. Make sure it's running with the highest resolution and open Chrome (39.0.2171.95-1) 3. Make sure it's running with the highest resolution and open Chromium (39.0.2171.65-0ubuntu0.14.04.1.1064) 4. Make sure it's running with the highest resolution and open Firefox (34.0+build2-0ubuntu0.14.04.1) 5. Switch to the second-highest resolution mode and repeat 2-4 Expected result: * Every browser should not intefere the display on this system. Actual result: * On step 2, display blinks right after Chrome opened, back to normal when you close the browser * On step 3, display blinks right after Chromium opened, back to normal when you close the browser * On step 4, it won't blink, but if you visit https://bugzilla.mozilla.org/show_bug.cgi?id=1118140 with 100% zoom scale in Firefox, it will blink. If you zoom in or out with ctrl +/- or close it, the display will back to normal. * On step 5, non of them will make the display blink Note that when it's blinking, you can switch to console with Ctrl + Alt + F1 without any problem. And this happen to Firefox on some other pages as well. Verified with: 3.16.0-28 + open source video driver the latest mainline kernel 3.19.0-rc3 + open source video driver 3.13.0-43 + open source video driver 3.13.0-43 + the latest AMD video driver (14.501.1003) in both power-saving and performance mode they all have the same behaviour. Please find the attachment for screencast from step 2 to 4. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-43-generic 3.13.0-43.72 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1766 F pulseaudio /dev/snd/controlC0: ubuntu 1766 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Tue Jan 6 03:43:19 2015 HibernationDevice: RESUME=UUID=3121f09d-4ad7-4946-b905-ee8e56a6d914 InstallationDate: Installed on 2015-01-05 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Inspiron 7548 ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic.efi.signed root=UUID=57666a30-96f3-478b-b3c1-3879ce81c53f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-43-generic N/A linux-backports-modules-3.13.0-43-generic N/A linux-firmware 1.127.11 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: BBE4C1 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.:bvrA00:bd11/19/2014:svnDellInc.:pnInspiron7548:pvrA00:rvnDellInc.:rnBBE4C1:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 7548 dmi.product.version: A00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1407913/+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 1407913] Re: In 3840x2160 high resolution mode, display would blink with Chrome / Chromium browser opened, or with certain page in Firefox
** Attachment added: Xorg.0.log https://bugs.launchpad.net/hwe-next/+bug/1407913/+attachment/4292805/+files/Xorg.0.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1407913 Title: In 3840x2160 high resolution mode, display would blink with Chrome / Chromium browser opened, or with certain page in Firefox Status in HWE Next Project: New Status in linux package in Ubuntu: Confirmed Bug description: CID: 201410-15952 Dell Inspiron 7548 I'm not sure which package to blame with, I guess maybe it has something to do with X, thing is: when the system is running in 3840*2160 resolution, the display will blink with these browsers under certain conditions. Steps: 1. Install 14.04.1 + update + Chromium + Chrome 2. Make sure it's running with the highest resolution and open Chrome (39.0.2171.95-1) 3. Make sure it's running with the highest resolution and open Chromium (39.0.2171.65-0ubuntu0.14.04.1.1064) 4. Make sure it's running with the highest resolution and open Firefox (34.0+build2-0ubuntu0.14.04.1) 5. Switch to the second-highest resolution mode and repeat 2-4 Expected result: * Every browser should not intefere the display on this system. Actual result: * On step 2, display blinks right after Chrome opened, back to normal when you close the browser * On step 3, display blinks right after Chromium opened, back to normal when you close the browser * On step 4, it won't blink, but if you visit https://bugzilla.mozilla.org/show_bug.cgi?id=1118140 with 100% zoom scale in Firefox, it will blink. If you zoom in or out with ctrl +/- or close it, the display will back to normal. * On step 5, non of them will make the display blink Note that when it's blinking, you can switch to console with Ctrl + Alt + F1 without any problem. And this happen to Firefox on some other pages as well. Verified with: 3.16.0-28 + open source video driver the latest mainline kernel 3.19.0-rc3 + open source video driver 3.13.0-43 + open source video driver 3.13.0-43 + the latest AMD video driver (14.501.1003) in both power-saving and performance mode they all have the same behaviour. Please find the attachment for screencast from step 2 to 4. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-43-generic 3.13.0-43.72 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1766 F pulseaudio /dev/snd/controlC0: ubuntu 1766 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Tue Jan 6 03:43:19 2015 HibernationDevice: RESUME=UUID=3121f09d-4ad7-4946-b905-ee8e56a6d914 InstallationDate: Installed on 2015-01-05 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Inspiron 7548 ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic.efi.signed root=UUID=57666a30-96f3-478b-b3c1-3879ce81c53f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-43-generic N/A linux-backports-modules-3.13.0-43-generic N/A linux-firmware 1.127.11 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: BBE4C1 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.:bvrA00:bd11/19/2014:svnDellInc.:pnInspiron7548:pvrA00:rvnDellInc.:rnBBE4C1:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 7548 dmi.product.version: A00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1407913/+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 1407913] Re: In 3840x2160 high resolution mode, display would blink with Chrome / Chromium browser opened, or with certain page in Firefox
For the error message in dmesg, I think it's the external webcam, it could be reproduced when removing the external USB webcam. Therefore I think they are not related. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1407913 Title: In 3840x2160 high resolution mode, display would blink with Chrome / Chromium browser opened, or with certain page in Firefox Status in HWE Next Project: New Status in linux package in Ubuntu: Confirmed Bug description: CID: 201410-15952 Dell Inspiron 7548 I'm not sure which package to blame with, I guess maybe it has something to do with X, thing is: when the system is running in 3840*2160 resolution, the display will blink with these browsers under certain conditions. Steps: 1. Install 14.04.1 + update + Chromium + Chrome 2. Make sure it's running with the highest resolution and open Chrome (39.0.2171.95-1) 3. Make sure it's running with the highest resolution and open Chromium (39.0.2171.65-0ubuntu0.14.04.1.1064) 4. Make sure it's running with the highest resolution and open Firefox (34.0+build2-0ubuntu0.14.04.1) 5. Switch to the second-highest resolution mode and repeat 2-4 Expected result: * Every browser should not intefere the display on this system. Actual result: * On step 2, display blinks right after Chrome opened, back to normal when you close the browser * On step 3, display blinks right after Chromium opened, back to normal when you close the browser * On step 4, it won't blink, but if you visit https://bugzilla.mozilla.org/show_bug.cgi?id=1118140 with 100% zoom scale in Firefox, it will blink. If you zoom in or out with ctrl +/- or close it, the display will back to normal. * On step 5, non of them will make the display blink Note that when it's blinking, you can switch to console with Ctrl + Alt + F1 without any problem. And this happen to Firefox on some other pages as well. Verified with: 3.16.0-28 + open source video driver the latest mainline kernel 3.19.0-rc3 + open source video driver 3.13.0-43 + open source video driver 3.13.0-43 + the latest AMD video driver (14.501.1003) in both power-saving and performance mode they all have the same behaviour. Please find the attachment for screencast from step 2 to 4. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-43-generic 3.13.0-43.72 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1766 F pulseaudio /dev/snd/controlC0: ubuntu 1766 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Tue Jan 6 03:43:19 2015 HibernationDevice: RESUME=UUID=3121f09d-4ad7-4946-b905-ee8e56a6d914 InstallationDate: Installed on 2015-01-05 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Inspiron 7548 ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic.efi.signed root=UUID=57666a30-96f3-478b-b3c1-3879ce81c53f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-43-generic N/A linux-backports-modules-3.13.0-43-generic N/A linux-firmware 1.127.11 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: BBE4C1 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.:bvrA00:bd11/19/2014:svnDellInc.:pnInspiron7548:pvrA00:rvnDellInc.:rnBBE4C1:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 7548 dmi.product.version: A00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1407913/+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 1407913] 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/1407913 Title: In 3840x2160 high resolution mode, display would blink with Chrome / Chromium browser opened, or with certain page in Firefox Status in HWE Next Project: New Status in linux package in Ubuntu: Confirmed Bug description: CID: 201410-15952 Dell Inspiron 7548 I'm not sure which package to blame with, I guess maybe it has something to do with X, thing is: when the system is running in 3840*2160 resolution, the display will blink with these browsers under certain conditions. Steps: 1. Install 14.04.1 + update + Chromium + Chrome 2. Make sure it's running with the highest resolution and open Chrome (39.0.2171.95-1) 3. Make sure it's running with the highest resolution and open Chromium (39.0.2171.65-0ubuntu0.14.04.1.1064) 4. Make sure it's running with the highest resolution and open Firefox (34.0+build2-0ubuntu0.14.04.1) 5. Switch to the second-highest resolution mode and repeat 2-4 Expected result: * Every browser should not intefere the display on this system. Actual result: * On step 2, display blinks right after Chrome opened, back to normal when you close the browser * On step 3, display blinks right after Chromium opened, back to normal when you close the browser * On step 4, it won't blink, but if you visit https://bugzilla.mozilla.org/show_bug.cgi?id=1118140 with 100% zoom scale in Firefox, it will blink. If you zoom in or out with ctrl +/- or close it, the display will back to normal. * On step 5, non of them will make the display blink Note that when it's blinking, you can switch to console with Ctrl + Alt + F1 without any problem. And this happen to Firefox on some other pages as well. Verified with: 3.16.0-28 + open source video driver the latest mainline kernel 3.19.0-rc3 + open source video driver 3.13.0-43 + open source video driver 3.13.0-43 + the latest AMD video driver (14.501.1003) in both power-saving and performance mode they all have the same behaviour. Please find the attachment for screencast from step 2 to 4. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-43-generic 3.13.0-43.72 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1766 F pulseaudio /dev/snd/controlC0: ubuntu 1766 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Tue Jan 6 03:43:19 2015 HibernationDevice: RESUME=UUID=3121f09d-4ad7-4946-b905-ee8e56a6d914 InstallationDate: Installed on 2015-01-05 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Inspiron 7548 ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic.efi.signed root=UUID=57666a30-96f3-478b-b3c1-3879ce81c53f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-43-generic N/A linux-backports-modules-3.13.0-43-generic N/A linux-firmware 1.127.11 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: BBE4C1 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.:bvrA00:bd11/19/2014:svnDellInc.:pnInspiron7548:pvrA00:rvnDellInc.:rnBBE4C1:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 7548 dmi.product.version: A00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1407913/+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 1283938] Re: [Samsung NP535U4X-S01TH] Ubuntu 14.04 blank screen after wakeup from sleep
And we're going into the new year with the problem is still not fixed. The bug manifests for me on ThinkPad Edge 02213BG, Radeon graphics, freshly installed Xubuntu 14.04. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1283938 Title: [Samsung NP535U4X-S01TH] Ubuntu 14.04 blank screen after wakeup from sleep Status in The Linux Kernel: Unknown Status in linux package in Ubuntu: Incomplete Bug description: *** ISSUE *** HOW TO REPRODUCE 1. Suspend the device 2. Wake it up EXPECTED BEHAVIOUR - The device to resume normally REAL BEHAVIOUR - The screen goes blank RELEVANT DETAILS - In the /etc/default/grub file; changing quiet splash option to nomodeset allows the wakeup, but the computer gets so slow it is unusable. ** SOLUTION ** WORK-AROUND - Installing the fglrx proprietary package. FIX - https://bugzilla.kernel.org/show_bug.cgi?id=76761#c3 REGRESSION POTENTIAL - Since this affects an essential hardware component, the regression potential is high. TECHNICAL INFO ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-ati 1:7.3.0-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 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: Mon Feb 24 12:58:07 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.6, 3.13.0-11-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7500G] [1002:990a] (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c660] Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7550M/7570M/7650M] [1002:6841] (rev ff) (prog-if ff) InstallationDate: Installed on 2014-02-22 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140218) MachineType: SAMSUNG ELECTRONICS CO., LTD. 535U4C ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic root=UUID=9f8c7e92-a6ea-41fd-9489-a256c8b9f5d5 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P06RAF.N93.130403.LEO dmi.board.asset.tag: No Asset Tag dmi.board.name: NP535U4X-S01TH dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SEC_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP06RAF.N93.130403.LEO:bd04/03/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn535U4C:pvrP06RAF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP535U4X-S01TH:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 535U4C dmi.product.version: P06RAF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Feb 24 12:54:54 2014 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.0-1ubuntu6 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1283938/+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 1407785] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1407785/+attachment/4292734/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1407785 Title: Can't enable both Right click and Multi-Touch in ElanTech touchpad. Status in linux package in Ubuntu: Confirmed Bug description: I tried everything i found in askubuntu and google search but the problem was the same. I would have only right click and not two fingers scroll OR only 2 fingers scroll and no right click of the Elantech touchpad. Exactly as described here by another person: http://askubuntu.com/questions/547410/14-04-how-to-enable-both-right-click-and-multi-touch-in-elantech-touchpad --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tina 1972 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9928b9e7-93e7-424f-8ffa-8fa819f5bec1 InstallationDate: Installed on 2015-01-03 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: LENOVO 80G0 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed root=UUID=d38ce6b9-a2f8-4c69-a375-9546350431db ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.138 Tags: utopic Uname: Linux 3.16.0-28-generic x86_64 UpgradeStatus: Upgraded to utopic on 2015-01-05 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN43WW:bd10/21/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.name: 80G0 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407785/+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 1407785] PulseList.txt
apport information ** Attachment added: PulseList.txt https://bugs.launchpad.net/bugs/1407785/+attachment/4292735/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1407785 Title: Can't enable both Right click and Multi-Touch in ElanTech touchpad. Status in linux package in Ubuntu: Confirmed Bug description: I tried everything i found in askubuntu and google search but the problem was the same. I would have only right click and not two fingers scroll OR only 2 fingers scroll and no right click of the Elantech touchpad. Exactly as described here by another person: http://askubuntu.com/questions/547410/14-04-how-to-enable-both-right-click-and-multi-touch-in-elantech-touchpad --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tina 1972 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9928b9e7-93e7-424f-8ffa-8fa819f5bec1 InstallationDate: Installed on 2015-01-03 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: LENOVO 80G0 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed root=UUID=d38ce6b9-a2f8-4c69-a375-9546350431db ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.138 Tags: utopic Uname: Linux 3.16.0-28-generic x86_64 UpgradeStatus: Upgraded to utopic on 2015-01-05 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN43WW:bd10/21/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.name: 80G0 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407785/+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 1407785] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1407785/+attachment/4292732/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1407785 Title: Can't enable both Right click and Multi-Touch in ElanTech touchpad. Status in linux package in Ubuntu: Confirmed Bug description: I tried everything i found in askubuntu and google search but the problem was the same. I would have only right click and not two fingers scroll OR only 2 fingers scroll and no right click of the Elantech touchpad. Exactly as described here by another person: http://askubuntu.com/questions/547410/14-04-how-to-enable-both-right-click-and-multi-touch-in-elantech-touchpad --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tina 1972 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9928b9e7-93e7-424f-8ffa-8fa819f5bec1 InstallationDate: Installed on 2015-01-03 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: LENOVO 80G0 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed root=UUID=d38ce6b9-a2f8-4c69-a375-9546350431db ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.138 Tags: utopic Uname: Linux 3.16.0-28-generic x86_64 UpgradeStatus: Upgraded to utopic on 2015-01-05 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN43WW:bd10/21/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.name: 80G0 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407785/+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 1407785] CRDA.txt
apport information ** Attachment added: CRDA.txt https://bugs.launchpad.net/bugs/1407785/+attachment/4292726/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1407785 Title: Can't enable both Right click and Multi-Touch in ElanTech touchpad. Status in linux package in Ubuntu: Confirmed Bug description: I tried everything i found in askubuntu and google search but the problem was the same. I would have only right click and not two fingers scroll OR only 2 fingers scroll and no right click of the Elantech touchpad. Exactly as described here by another person: http://askubuntu.com/questions/547410/14-04-how-to-enable-both-right-click-and-multi-touch-in-elantech-touchpad --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tina 1972 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9928b9e7-93e7-424f-8ffa-8fa819f5bec1 InstallationDate: Installed on 2015-01-03 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: LENOVO 80G0 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed root=UUID=d38ce6b9-a2f8-4c69-a375-9546350431db ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.138 Tags: utopic Uname: Linux 3.16.0-28-generic x86_64 UpgradeStatus: Upgraded to utopic on 2015-01-05 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN43WW:bd10/21/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.name: 80G0 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407785/+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 1407785] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1407785/+attachment/4292731/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1407785 Title: Can't enable both Right click and Multi-Touch in ElanTech touchpad. Status in linux package in Ubuntu: Confirmed Bug description: I tried everything i found in askubuntu and google search but the problem was the same. I would have only right click and not two fingers scroll OR only 2 fingers scroll and no right click of the Elantech touchpad. Exactly as described here by another person: http://askubuntu.com/questions/547410/14-04-how-to-enable-both-right-click-and-multi-touch-in-elantech-touchpad --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tina 1972 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9928b9e7-93e7-424f-8ffa-8fa819f5bec1 InstallationDate: Installed on 2015-01-03 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: LENOVO 80G0 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed root=UUID=d38ce6b9-a2f8-4c69-a375-9546350431db ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.138 Tags: utopic Uname: Linux 3.16.0-28-generic x86_64 UpgradeStatus: Upgraded to utopic on 2015-01-05 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN43WW:bd10/21/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.name: 80G0 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407785/+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 1407785] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1407785/+attachment/4292730/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1407785 Title: Can't enable both Right click and Multi-Touch in ElanTech touchpad. Status in linux package in Ubuntu: Confirmed Bug description: I tried everything i found in askubuntu and google search but the problem was the same. I would have only right click and not two fingers scroll OR only 2 fingers scroll and no right click of the Elantech touchpad. Exactly as described here by another person: http://askubuntu.com/questions/547410/14-04-how-to-enable-both-right-click-and-multi-touch-in-elantech-touchpad --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tina 1972 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9928b9e7-93e7-424f-8ffa-8fa819f5bec1 InstallationDate: Installed on 2015-01-03 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: LENOVO 80G0 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed root=UUID=d38ce6b9-a2f8-4c69-a375-9546350431db ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.138 Tags: utopic Uname: Linux 3.16.0-28-generic x86_64 UpgradeStatus: Upgraded to utopic on 2015-01-05 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN43WW:bd10/21/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.name: 80G0 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407785/+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 1407785] IwConfig.txt
apport information ** Attachment added: IwConfig.txt https://bugs.launchpad.net/bugs/1407785/+attachment/4292728/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1407785 Title: Can't enable both Right click and Multi-Touch in ElanTech touchpad. Status in linux package in Ubuntu: Confirmed Bug description: I tried everything i found in askubuntu and google search but the problem was the same. I would have only right click and not two fingers scroll OR only 2 fingers scroll and no right click of the Elantech touchpad. Exactly as described here by another person: http://askubuntu.com/questions/547410/14-04-how-to-enable-both-right-click-and-multi-touch-in-elantech-touchpad --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tina 1972 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9928b9e7-93e7-424f-8ffa-8fa819f5bec1 InstallationDate: Installed on 2015-01-03 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: LENOVO 80G0 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed root=UUID=d38ce6b9-a2f8-4c69-a375-9546350431db ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.138 Tags: utopic Uname: Linux 3.16.0-28-generic x86_64 UpgradeStatus: Upgraded to utopic on 2015-01-05 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN43WW:bd10/21/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.name: 80G0 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407785/+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 1407785] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1407785/+attachment/4292727/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1407785 Title: Can't enable both Right click and Multi-Touch in ElanTech touchpad. Status in linux package in Ubuntu: Confirmed Bug description: I tried everything i found in askubuntu and google search but the problem was the same. I would have only right click and not two fingers scroll OR only 2 fingers scroll and no right click of the Elantech touchpad. Exactly as described here by another person: http://askubuntu.com/questions/547410/14-04-how-to-enable-both-right-click-and-multi-touch-in-elantech-touchpad --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tina 1972 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9928b9e7-93e7-424f-8ffa-8fa819f5bec1 InstallationDate: Installed on 2015-01-03 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: LENOVO 80G0 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed root=UUID=d38ce6b9-a2f8-4c69-a375-9546350431db ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.138 Tags: utopic Uname: Linux 3.16.0-28-generic x86_64 UpgradeStatus: Upgraded to utopic on 2015-01-05 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN43WW:bd10/21/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.name: 80G0 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407785/+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 1407785] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1407785/+attachment/4292729/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1407785 Title: Can't enable both Right click and Multi-Touch in ElanTech touchpad. Status in linux package in Ubuntu: Confirmed Bug description: I tried everything i found in askubuntu and google search but the problem was the same. I would have only right click and not two fingers scroll OR only 2 fingers scroll and no right click of the Elantech touchpad. Exactly as described here by another person: http://askubuntu.com/questions/547410/14-04-how-to-enable-both-right-click-and-multi-touch-in-elantech-touchpad --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tina 1972 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9928b9e7-93e7-424f-8ffa-8fa819f5bec1 InstallationDate: Installed on 2015-01-03 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: LENOVO 80G0 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed root=UUID=d38ce6b9-a2f8-4c69-a375-9546350431db ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.138 Tags: utopic Uname: Linux 3.16.0-28-generic x86_64 UpgradeStatus: Upgraded to utopic on 2015-01-05 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN43WW:bd10/21/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.name: 80G0 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407785/+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 1407785] Re: Can't enable both Right click and Multi-Touch in ElanTech touchpad.
apport information ** Tags added: apport-collected utopic ** Description changed: I tried everything i found in askubuntu and google search but the problem was the same. I would have only right click and not two fingers scroll OR only 2 fingers scroll and no right click of the Elantech touchpad. - Exactly as described here by another person: - http://askubuntu.com/questions/547410/14-04-how-to-enable-both-right- - click-and-multi-touch-in-elantech-touchpad + Exactly as described here by another person: http://askubuntu.com/questions/547410/14-04-how-to-enable-both-right-click-and-multi-touch-in-elantech-touchpad + --- + ApportVersion: 2.14.7-0ubuntu8 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: tina 1972 F pulseaudio + CurrentDesktop: Unity + DistroRelease: Ubuntu 14.10 + HibernationDevice: RESUME=UUID=9928b9e7-93e7-424f-8ffa-8fa819f5bec1 + InstallationDate: Installed on 2015-01-03 (2 days ago) + InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) + MachineType: LENOVO 80G0 + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed root=UUID=d38ce6b9-a2f8-4c69-a375-9546350431db ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 + RelatedPackageVersions: + linux-restricted-modules-3.16.0-28-generic N/A + linux-backports-modules-3.16.0-28-generic N/A + linux-firmware 1.138 + Tags: utopic + Uname: Linux 3.16.0-28-generic x86_64 + UpgradeStatus: Upgraded to utopic on 2015-01-05 (0 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 10/21/2014 + dmi.bios.vendor: LENOVO + dmi.bios.version: A7CN43WW + dmi.board.asset.tag: NO Asset Tag + dmi.board.name: Lancer 5A6 + dmi.board.vendor: LENOVO + dmi.board.version: NANANANANO DPK + dmi.chassis.asset.tag: NO Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: Lenovo G50-30 + dmi.modalias: dmi:bvnLENOVO:bvrA7CN43WW:bd10/21/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-30: + dmi.product.name: 80G0 + dmi.product.version: Lenovo G50-30 + dmi.sys.vendor: LENOVO ** Attachment added: AlsaInfo.txt https://bugs.launchpad.net/bugs/1407785/+attachment/4292724/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1407785 Title: Can't enable both Right click and Multi-Touch in ElanTech touchpad. Status in linux package in Ubuntu: Confirmed Bug description: I tried everything i found in askubuntu and google search but the problem was the same. I would have only right click and not two fingers scroll OR only 2 fingers scroll and no right click of the Elantech touchpad. Exactly as described here by another person: http://askubuntu.com/questions/547410/14-04-how-to-enable-both-right-click-and-multi-touch-in-elantech-touchpad --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tina 1972 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9928b9e7-93e7-424f-8ffa-8fa819f5bec1 InstallationDate: Installed on 2015-01-03 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: LENOVO 80G0 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed root=UUID=d38ce6b9-a2f8-4c69-a375-9546350431db ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.138 Tags: utopic Uname: Linux 3.16.0-28-generic x86_64 UpgradeStatus: Upgraded to utopic on 2015-01-05 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN43WW:bd10/21/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.name: 80G0 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407785/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1407785] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/1407785/+attachment/4292725/+files/BootDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1407785 Title: Can't enable both Right click and Multi-Touch in ElanTech touchpad. Status in linux package in Ubuntu: Confirmed Bug description: I tried everything i found in askubuntu and google search but the problem was the same. I would have only right click and not two fingers scroll OR only 2 fingers scroll and no right click of the Elantech touchpad. Exactly as described here by another person: http://askubuntu.com/questions/547410/14-04-how-to-enable-both-right-click-and-multi-touch-in-elantech-touchpad --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tina 1972 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9928b9e7-93e7-424f-8ffa-8fa819f5bec1 InstallationDate: Installed on 2015-01-03 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: LENOVO 80G0 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed root=UUID=d38ce6b9-a2f8-4c69-a375-9546350431db ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.138 Tags: utopic Uname: Linux 3.16.0-28-generic x86_64 UpgradeStatus: Upgraded to utopic on 2015-01-05 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN43WW:bd10/21/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.name: 80G0 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407785/+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 1407785] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1407785/+attachment/4292733/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1407785 Title: Can't enable both Right click and Multi-Touch in ElanTech touchpad. Status in linux package in Ubuntu: Confirmed Bug description: I tried everything i found in askubuntu and google search but the problem was the same. I would have only right click and not two fingers scroll OR only 2 fingers scroll and no right click of the Elantech touchpad. Exactly as described here by another person: http://askubuntu.com/questions/547410/14-04-how-to-enable-both-right-click-and-multi-touch-in-elantech-touchpad --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tina 1972 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9928b9e7-93e7-424f-8ffa-8fa819f5bec1 InstallationDate: Installed on 2015-01-03 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: LENOVO 80G0 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed root=UUID=d38ce6b9-a2f8-4c69-a375-9546350431db ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.138 Tags: utopic Uname: Linux 3.16.0-28-generic x86_64 UpgradeStatus: Upgraded to utopic on 2015-01-05 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN43WW:bd10/21/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.name: 80G0 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407785/+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 1404560] Re: Trusty kernel is unable to page Evergreen Radeon GPU; blank screen and high load after boot
Kernel bug report: https://bugzilla.kernel.org/show_bug.cgi?id=88481 The fix is here: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=83d04c39f9048807a8500e575ae3f1718a3f45bb ** Bug watch added: Linux Kernel Bug Tracker #88481 http://bugzilla.kernel.org/show_bug.cgi?id=88481 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1404560 Title: Trusty kernel is unable to page Evergreen Radeon GPU; blank screen and high load after boot Status in linux package in Ubuntu: Incomplete Bug description: lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 apt-cache policy linux-signed-generic linux-signed-generic: Installed: 3.13.0.43.50 Candidate: 3.13.0.43.50 Version table: *** 3.13.0.43.50 0 500 http://ro.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 3.13.0.24.28 0 500 http://ro.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages Expected behavior: see lightdm login screen after boot Actual behavior: After a kernel update to 3.13.0-43, a machine with an Evergreen Radeon GPU is no longer usable. After showing the splash screen, the monitor doesn't detect any signal and goes blank. Furthermore, the system load increases above 2.5 without any CPU or IO activity. This bug is similar to bug #1397553 for Utopic. EDIT: The bug only surfaces when a monitor is connected via HDMI. If the HDMI connector is unplugged, the system boots fine. Relevant syslog: [0.00] Linux version 3.13.0-43-generic (buildd@tipua) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014 (Ubuntu 3.13.0-43.72-generic 3.13.11.11) [ 32.934494] BUG: unable to handle kernel paging request at ec200900 [ 32.934592] IP: [811a2046] kfree+0x56/0x140 [ 32.934655] PGD 0 [ 32.934683] Oops: [#1] SMP [ 32.934726] Modules linked in: bnep rfcomm snd_hda_codec_realtek snd_hda_codec_hdmi hid_generic snd_hda_intel usbhid kvm_amd hid snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi kvm snd_seq snd_seq_device snd_timer radeon serio_raw snd btusb soundcore ttm drm_kms_helper k10temp bluetooth sp5100_tco drm i2c_algo_bit i2c_piix4 mac_hid parport_pc ppdev f71882fg lp parport nls_iso8859_1 pata_acpi psmouse r8169 mii pata_atiixp ahci libahci [ 32.935304] CPU: 0 PID: 1523 Comm: Xorg Not tainted 3.13.0-43-generic #72-Ubuntu [ 32.935384] Hardware name: MSI MS-7698/E350IA-E44 (MS-7698), BIOS V1.5 04/22/2011 [ 32.935458] task: 880232b3c800 ti: 880232b34000 task.ti: 880232b34000 [ 32.935532] RIP: 0010:[811a2046] [811a2046] kfree+0x56/0x140 [ 32.935612] RSP: 0018:880232b35a68 EFLAGS: 00010286 [ 32.935669] RAX: ec200900 RBX: 10024414 RCX: [ 32.935739] RDX: ea00 RSI: 5f78 RDI: 10024414 [ 32.935809] RBP: 880232b35a80 R08: 0022 R09: 0021 [ 32.935879] R10: ea0008ca1dc0 R11: a0292bc1 R12: [ 32.935949] R13: a02ef3b6 R14: R15: 880231c95e00 [ 32.936021] FS: 7f47050109c0() GS:88023ec0() knlGS: [ 32.936106] CS: 0010 DS: ES: CR0: 80050033 [ 32.936163] CR2: ec200900 CR3: 000231123000 CR4: 07f0 [ 32.936234] Stack: [ 32.936257] 880036784000 880036784000 880232b35b38 [ 32.936345] a02ef3b6 880232b35ab0 88027048 7044712c [ 32.936431] 880001f7d000 10024414 18824414 18028488 [ 32.936518] Call Trace: [ 32.936605] [a02ef3b6] evergreen_hdmi_setmode+0x776/0x960 [radeon] [ 32.936707] [a00bb55e] ? drm_detect_hdmi_monitor+0x6e/0xb0 [drm] [ 32.936814] [a02f6788] radeon_atom_encoder_mode_set+0x158/0x2d0 [radeon] [ 32.936897] [a0150a98] drm_crtc_helper_set_mode+0x498/0x500 [drm_kms_helper] [ 32.937004] [a02a0d35] radeon_property_change_mode.isra.1+0x35/0x40 [radeon] [ 32.937109] [a02a0ece] radeon_connector_set_property+0x18e/0x300 [radeon] [ 32.937209] [a00b8732] drm_mode_obj_set_property_ioctl+0x142/0x340 [drm] [ 32.937300] [a00b8960] drm_mode_connector_property_set_ioctl+0x30/0x40 [drm] [ 32.937391] [a00a7c22] drm_ioctl+0x502/0x630 [drm] [ 32.937456] [8172cc94] ? __do_page_fault+0x204/0x560 [ 32.937534] [a02620fe] radeon_drm_ioctl+0x4e/0x90 [radeon] [ 32.937602] [811d0e90] do_vfs_ioctl+0x2e0/0x4c0 [ 32.937664]
[Kernel-packages] [Bug 1404409] Re: [regression] Intel 10Gb NIC Crashes
Unfortunately, my test case isn't 100% reproducible. I haven't changed anything, but I have been unable to reproduce the problem tonight, even on the stock Trusty kernel. On the mainline kernel, I can't get the VM to start at all unless I unmount the cgroups filesystem to force libvirt to not use cgroups. libvirt version 1.2.8 throws errors like this: libvirtd: 7815: error : cgm_enter:318 : cgmanager: cgm_enter for controller=cpuset, cgroup_path=machine/VM_NAME.libvirt-qemu/vcpu0, pid=8134 failed: invalid request libvirtd: 7815: error : virCgroupAddTask:1304 : Failed to move 8134 to cpuset:/machine/VM_NAME.libvirt-qemu/vcpu0 libvirtd: 7815: error : cgm_remove:126 : cgmanager: cgm_remove for controller=cpu, cgroup_path=machine/VM_NAME.libvirt-qemu/vcpu0, recursive=1 failed: invalid request libvirtd: 7815: warning : virCgroupRemove:3569 : Error removing cpu:/machine/VM_NAME.libvirt-qemu/vcpu0 libvirtd: 7815: error : cgm_remove:126 : cgmanager: cgm_remove for controller=cpuacct, cgroup_path=machine/VM_NAME.libvirt-qemu/vcpu0, recursive=1 failed: invalid request libvirtd: 7815: warning : virCgroupRemove:3569 : Error removing cpuacct:/machine/VM_NAME.libvirt-qemu/vcpu0 libvirtd: 7819: warning : qemuDomainObjTaint:1672 : Domain id=3 name='VM_NAME' uuid=0f2de0e7-1b11-489f-937d-d83febad0918 is tainted: custom-argv libvirtd: 7819: error : cgm_enter:318 : cgmanager: cgm_enter for controller=cpuset, cgroup_path=machine/VM_NAME.libvirt-qemu/vcpu0, pid=8267 failed: invalid request libvirtd: 7819: error : virCgroupAddTask:1304 : Failed to move 8267 to cpuset:/machine/VM_NAME.libvirt-qemu/vcpu0 libvirtd: 7819: error : cgm_remove:126 : cgmanager: cgm_remove for controller=cpu, cgroup_path=machine/VM_NAME.libvirt-qemu/vcpu0, recursive=1 failed: invalid request libvirtd: 7819: warning : virCgroupRemove:3569 : Error removing cpu:/machine/VM_NAME.libvirt-qemu/vcpu0 libvirtd: 7819: error : cgm_remove:126 : cgmanager: cgm_remove for controller=cpuacct, cgroup_path=machine/VM_NAME.libvirt-qemu/vcpu0, recursive=1 failed: invalid request -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1404409 Title: [regression] Intel 10Gb NIC Crashes Status in linux package in Ubuntu: Confirmed Bug description: I posted this to net...@vger.kernel.org as well: http://www.spinics.net/lists/netdev/msg309110.html I think the next step is to try to bisect this down to a specific commit. I'm starting to look at the instructions here: https://wiki.ubuntu.com/Kernel/KernelBisection - Previous history of this thread: http://thread.gmane.org/gmane.linux.network/326672 On 2014-11-04 22:57:19, Tom Herbert wrote: Using vlan and bonding? vlan_dev_hard_start_xmit called. A possible cause is that bonding interface is out of sync with slave interface w.r.t. GSO features. Do we know if this worked in 3.14, 3.15? I'm seeing the same sort of crash/warning (skb_war_bad_offload). It's happening on Intel 10 Gig NICs using the ixgbe driver. I'm using bridges (for virtual machines) on top of VLANs on top of 802.3ad bonding. I'm using an MTU of 9000 on the bond0 interface, but 1500 everywhere else. I'm always bonding two ports: one one system, I'm bonding two ports on identical one-port NICs; on another system, I'm bonding two ports on a single two-port NIC. Both systems exhibit the same behavior. Everything has worked fine for a couple years on Ubuntu 12.04 Precise (Linux 3.2.0). It immediately broke when I upgraded to Ubuntu 14.04 Trusty (Linux 3.13.0). I can also reproduce this using the packaged version of Linux 3.16.0 on Trusty. In contrast to other reports of this bug, disabling scatter gather on the physical interfaces (e.g. eth0) does *not* stop the crashes (assuming I disabled it correctly). I currently have two systems (one with Precise, one with Trusty) available to do any testing that you'd find helpful. Here's a first pass at getting some debugging data. The broken system (Ubuntu 14.04 Trusty): rlaager@BROKEN:~$ uname -a Linux BROKEN 3.13.0-43-generic #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux rlaager@BROKEN:~$ ethtool -k p6p1 Features for p6p1: rx-checksumming: on tx-checksumming: on tx-checksum-ipv4: on tx-checksum-ip-generic: off [fixed] tx-checksum-ipv6: on tx-checksum-fcoe-crc: on [fixed] tx-checksum-sctp: on scatter-gather: on tx-scatter-gather: on tx-scatter-gather-fraglist: off [fixed] tcp-segmentation-offload: on tx-tcp-segmentation: on tx-tcp-ecn-segmentation: off [fixed] tx-tcp6-segmentation: on udp-fragmentation-offload: off [fixed] generic-segmentation-offload: on generic-receive-offload: on large-receive-offload: off rx-vlan-offload: on tx-vlan-offload: on ntuple-filters:
[Kernel-packages] [Bug 1407785] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/1407785/+attachment/4292739/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1407785 Title: Can't enable both Right click and Multi-Touch in ElanTech touchpad. Status in linux package in Ubuntu: Confirmed Bug description: I tried everything i found in askubuntu and google search but the problem was the same. I would have only right click and not two fingers scroll OR only 2 fingers scroll and no right click of the Elantech touchpad. Exactly as described here by another person: http://askubuntu.com/questions/547410/14-04-how-to-enable-both-right-click-and-multi-touch-in-elantech-touchpad --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tina 1972 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9928b9e7-93e7-424f-8ffa-8fa819f5bec1 InstallationDate: Installed on 2015-01-03 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: LENOVO 80G0 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed root=UUID=d38ce6b9-a2f8-4c69-a375-9546350431db ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.138 Tags: utopic Uname: Linux 3.16.0-28-generic x86_64 UpgradeStatus: Upgraded to utopic on 2015-01-05 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN43WW:bd10/21/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.name: 80G0 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407785/+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 1407785] Re: Can't enable both Right click and Multi-Touch in ElanTech touchpad.
Also i updated to kernel 3.19 but still the problem exists. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1407785 Title: Can't enable both Right click and Multi-Touch in ElanTech touchpad. Status in linux package in Ubuntu: Confirmed Bug description: I tried everything i found in askubuntu and google search but the problem was the same. I would have only right click and not two fingers scroll OR only 2 fingers scroll and no right click of the Elantech touchpad. Exactly as described here by another person: http://askubuntu.com/questions/547410/14-04-how-to-enable-both-right-click-and-multi-touch-in-elantech-touchpad --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tina 1972 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9928b9e7-93e7-424f-8ffa-8fa819f5bec1 InstallationDate: Installed on 2015-01-03 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: LENOVO 80G0 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed root=UUID=d38ce6b9-a2f8-4c69-a375-9546350431db ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.138 Tags: utopic Uname: Linux 3.16.0-28-generic x86_64 UpgradeStatus: Upgraded to utopic on 2015-01-05 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN43WW:bd10/21/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.name: 80G0 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407785/+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 1407785] RfKill.txt
apport information ** Attachment added: RfKill.txt https://bugs.launchpad.net/bugs/1407785/+attachment/4292736/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1407785 Title: Can't enable both Right click and Multi-Touch in ElanTech touchpad. Status in linux package in Ubuntu: Confirmed Bug description: I tried everything i found in askubuntu and google search but the problem was the same. I would have only right click and not two fingers scroll OR only 2 fingers scroll and no right click of the Elantech touchpad. Exactly as described here by another person: http://askubuntu.com/questions/547410/14-04-how-to-enable-both-right-click-and-multi-touch-in-elantech-touchpad --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tina 1972 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9928b9e7-93e7-424f-8ffa-8fa819f5bec1 InstallationDate: Installed on 2015-01-03 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: LENOVO 80G0 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed root=UUID=d38ce6b9-a2f8-4c69-a375-9546350431db ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.138 Tags: utopic Uname: Linux 3.16.0-28-generic x86_64 UpgradeStatus: Upgraded to utopic on 2015-01-05 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN43WW:bd10/21/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.name: 80G0 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407785/+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 1407785] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1407785/+attachment/4292738/+files/UdevLog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1407785 Title: Can't enable both Right click and Multi-Touch in ElanTech touchpad. Status in linux package in Ubuntu: Confirmed Bug description: I tried everything i found in askubuntu and google search but the problem was the same. I would have only right click and not two fingers scroll OR only 2 fingers scroll and no right click of the Elantech touchpad. Exactly as described here by another person: http://askubuntu.com/questions/547410/14-04-how-to-enable-both-right-click-and-multi-touch-in-elantech-touchpad --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tina 1972 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9928b9e7-93e7-424f-8ffa-8fa819f5bec1 InstallationDate: Installed on 2015-01-03 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: LENOVO 80G0 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed root=UUID=d38ce6b9-a2f8-4c69-a375-9546350431db ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.138 Tags: utopic Uname: Linux 3.16.0-28-generic x86_64 UpgradeStatus: Upgraded to utopic on 2015-01-05 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN43WW:bd10/21/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.name: 80G0 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407785/+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 1407785] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1407785/+attachment/4292737/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1407785 Title: Can't enable both Right click and Multi-Touch in ElanTech touchpad. Status in linux package in Ubuntu: Confirmed Bug description: I tried everything i found in askubuntu and google search but the problem was the same. I would have only right click and not two fingers scroll OR only 2 fingers scroll and no right click of the Elantech touchpad. Exactly as described here by another person: http://askubuntu.com/questions/547410/14-04-how-to-enable-both-right-click-and-multi-touch-in-elantech-touchpad --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tina 1972 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9928b9e7-93e7-424f-8ffa-8fa819f5bec1 InstallationDate: Installed on 2015-01-03 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: LENOVO 80G0 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed root=UUID=d38ce6b9-a2f8-4c69-a375-9546350431db ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.138 Tags: utopic Uname: Linux 3.16.0-28-generic x86_64 UpgradeStatus: Upgraded to utopic on 2015-01-05 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN43WW:bd10/21/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.name: 80G0 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407785/+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 1161962] Re: XPS 13 wakes up from suspend spontaneously
Here one possible solution to the problem I described: http://patchwork.ozlabs.org/patch/423494/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1161962 Title: XPS 13 wakes up from suspend spontaneously Status in Dell Sputnik: In Progress Status in linux package in Ubuntu: Incomplete Bug description: My XPS 13 wakes up from suspend by itself. This is very annoying and potentially dangerous since it happens while the computer is its sleeve/bag. Can't tell from the pm-suspend and dmesg what causes the behavior so please let me know what logs you need to investigate it and I will provide them. Further note: It seems like the spontaneous wake up is happening around 40 minutes after suspend every time it occurs. However, the spontaneous wake up does not occur every time. Running Xubuntu 12.10 with the following Sputnik Kernel: 3.5.0-26-generic #42+kamal15~DellXPS-Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1161962/+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 1385137] Re: [ASUS N550JK] Touchpad recognized wrongly as PS/2 mouse
Regarding bugzilla vs mailing list. It looks like in bugzilla issues are addressed better. Mailing lists are mostly used for sending patches. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1385137 Title: [ASUS N550JK] Touchpad recognized wrongly as PS/2 mouse Status in The Linux Kernel: Unknown Status in linux package in Ubuntu: Triaged Bug description: The touchpad on my ASUS N550JK laptop is being recognized as a PS/2 Logitech Wheel Mouse, rather than as a touchpad. In this configuration it only works to move the pointer or clicking, all the advanced features (multi-touch, pinch, zoom, scroll...) can't be properly configured. This is the output of xinput: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ PS/2 Logitech Wheel Mouse id=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ USB2.0 UVC HD Webcamid=11 [slave keyboard (3)] ↳ Asus WMI hotkeysid=12 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-23-generic 3.16.0-23.31 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2857 F pulseaudio /dev/snd/controlC0: ubuntu 2857 F pulseaudio CasperVersion: 1.345 CurrentDesktop: Unity Date: Fri Oct 24 09:09:20 2014 LiveMediaBuild: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: ASUSTeK COMPUTER INC. N550JK ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz.efi boot=casper iso-scan/filename=/home/fil/Downloads/username-14.10-desktop-amd64.iso locale=en_US.UTF-8 RelatedPackageVersions: linux-restricted-modules-3.16.0-23-generic N/A linux-backports-modules-3.16.0-23-generic N/A linux-firmware 1.138 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N550JK.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N550JK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN550JK.207:bd08/11/2014:svnASUSTeKCOMPUTERINC.:pnN550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1385137/+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 1385137] Re: [ASUS N550JK] Touchpad recognized wrongly as PS/2 mouse
Christopher, I was not correct, looked to another tree. It was not merged in rc3 yet. It is in linux-next. Here is the URL. https://git.kernel.org/cgit/linux/kernel/git/next/linux- next.git/commit/drivers/input/mouse/focaltech.c?id=05be1d079ec0b3691783e4384b1ada82149ff7d2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1385137 Title: [ASUS N550JK] Touchpad recognized wrongly as PS/2 mouse Status in The Linux Kernel: Unknown Status in linux package in Ubuntu: Triaged Bug description: The touchpad on my ASUS N550JK laptop is being recognized as a PS/2 Logitech Wheel Mouse, rather than as a touchpad. In this configuration it only works to move the pointer or clicking, all the advanced features (multi-touch, pinch, zoom, scroll...) can't be properly configured. This is the output of xinput: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ PS/2 Logitech Wheel Mouse id=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ USB2.0 UVC HD Webcamid=11 [slave keyboard (3)] ↳ Asus WMI hotkeysid=12 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-23-generic 3.16.0-23.31 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2857 F pulseaudio /dev/snd/controlC0: ubuntu 2857 F pulseaudio CasperVersion: 1.345 CurrentDesktop: Unity Date: Fri Oct 24 09:09:20 2014 LiveMediaBuild: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: ASUSTeK COMPUTER INC. N550JK ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz.efi boot=casper iso-scan/filename=/home/fil/Downloads/username-14.10-desktop-amd64.iso locale=en_US.UTF-8 RelatedPackageVersions: linux-restricted-modules-3.16.0-23-generic N/A linux-backports-modules-3.16.0-23-generic N/A linux-firmware 1.138 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N550JK.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N550JK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN550JK.207:bd08/11/2014:svnASUSTeKCOMPUTERINC.:pnN550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1385137/+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 1283938] Re: [Samsung NP535U4X-S01TH] Ubuntu 14.04 blank screen after wakeup from sleep
** Tags removed: patch ** Tags added: needs-upstream-testing ** Description changed: - *** - ISSUE - *** - HOW TO REPRODUCE 1. Suspend the device 2. Wake it up EXPECTED BEHAVIOUR - The device to resume normally REAL BEHAVIOUR - The screen goes blank RELEVANT DETAILS - In the /etc/default/grub file; changing quiet splash option to nomodeset allows the wakeup, but the computer gets so slow it is unusable. - ** - SOLUTION - ** + WORKAROUND: Install fglrx. - WORK-AROUND - - - Installing the fglrx proprietary package. - - FIX - - - https://bugzilla.kernel.org/show_bug.cgi?id=76761#c3 - - REGRESSION POTENTIAL - - - Since this affects an essential hardware component, the regression - potential is high. - - - TECHNICAL INFO - + Unverified WORKAROUND: Revert commit + 6c7bccea390853bdec5b76fe31fc50f3b36f75d5 as per + https://bugzilla.kernel.org/show_bug.cgi?id=76761#c3 . ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-ati 1:7.3.0-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 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: Mon Feb 24 12:58:07 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.6, 3.13.0-11-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7500G] [1002:990a] (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c660] Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7550M/7570M/7650M] [1002:6841] (rev ff) (prog-if ff) InstallationDate: Installed on 2014-02-22 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140218) MachineType: SAMSUNG ELECTRONICS CO., LTD. 535U4C ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic root=UUID=9f8c7e92-a6ea-41fd-9489-a256c8b9f5d5 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P06RAF.N93.130403.LEO dmi.board.asset.tag: No Asset Tag dmi.board.name: NP535U4X-S01TH dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SEC_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP06RAF.N93.130403.LEO:bd04/03/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn535U4C:pvrP06RAF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP535U4X-S01TH:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 535U4C dmi.product.version: P06RAF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Feb 24 12:54:54 2014 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.0-1ubuntu6 xserver.video_driver: radeon ** Tags added: resume suspend -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1283938 Title: [Samsung NP535U4X-S01TH] Ubuntu 14.04 blank screen after wakeup from sleep Status in The Linux Kernel: Unknown Status in linux package in Ubuntu: Incomplete Bug description: HOW TO REPRODUCE 1. Suspend the device 2. Wake it up EXPECTED BEHAVIOUR - The device to resume normally REAL BEHAVIOUR - The screen goes blank RELEVANT DETAILS - In the /etc/default/grub file; changing quiet splash option to nomodeset allows the wakeup, but the computer gets so slow it is unusable. WORKAROUND: Install fglrx. Unverified WORKAROUND: Revert commit
[Kernel-packages] [Bug 1407755] Re: linux-lts-utopic uname -v value inconsistant with existing lts releases
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New = In Progress ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-utopic (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-utopic (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-utopic (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-utopic (Ubuntu) Status: In Progress = Invalid ** Changed in: linux-lts-utopic (Ubuntu) Milestone: ubuntu-15.01 = None ** Changed in: linux (Ubuntu) Milestone: None = ubuntu-15.01 ** Changed in: linux (Ubuntu) Assignee: (unassigned) = Andy Whitcroft (apw) ** Changed in: linux (Ubuntu Utopic) Assignee: (unassigned) = Andy Whitcroft (apw) ** Changed in: linux-lts-utopic (Ubuntu Trusty) Assignee: (unassigned) = Andy Whitcroft (apw) ** Changed in: linux-lts-utopic (Ubuntu) Assignee: Andy Whitcroft (apw) = (unassigned) ** Changed in: linux-lts-utopic (Ubuntu) Importance: Medium = Undecided ** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** Changed in: linux (Ubuntu Utopic) Importance: Undecided = Medium ** Changed in: linux (Ubuntu Utopic) Status: New = In Progress ** Changed in: linux-lts-utopic (Ubuntu Trusty) Status: New = In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1407755 Title: linux-lts-utopic uname -v value inconsistant with existing lts releases Status in linux package in Ubuntu: In Progress Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: In Progress Status in linux source package in Utopic: In Progress Status in linux-lts-utopic source package in Utopic: Invalid Bug description: The ~14.04.1 version should be reflected in the uname -v output as it is in older LTS backports. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-28-generic 3.16.0-28.38~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-28.38~14.04.1-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jan 5 18:02:37 2015 InstallationDate: Installed on 2015-01-05 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407755/+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 1407313] Re: Physical buttons of touchpad do not work on Asus N53S (ETPS/2 Elantech Touchpad)
Hi Joseph, thank you for your reply. No, this is not a new issue. I had it also on Linux Mint 16, and previously Ubuntu 13.04 and, I believe, 12.10. I installed the latest upstream kernel (uname -r gives: 3.19.0-031900rc3-generic), and the issue is still there. Click either of the touchpad buttona and nothing happens (touchpad and tapping on tapping work fine, same as with previous kernel). Any workaround or other suggestions? thanks! ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1407313 Title: Physical buttons of touchpad do not work on Asus N53S (ETPS/2 Elantech Touchpad) Status in linux package in Ubuntu: Confirmed Bug description: Physical buttons for left and right button do not work at all on the touchpad of Asus N53S. I'm now on Linux Mint 17.1, but had the same issue previously on Ubuntu 13-10 (http://ubuntuforums.org/showthread.php?t=2196970). I have not found any real workaround. Plugging in a mouse all works just fine. Find attached relevant log files. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-37-generic 3.13.0-37.64 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ros1994 F pulseaudio CurrentDesktop: X-Cinnamon CurrentDmesg: [ 32.256027] nouveau E[ PDISP][:01:00.0] chid 0 mthd 0x0080 data 0x 0x00085080 Date: Sat Jan 3 18:24:37 2015 HibernationDevice: RESUME=UUID=b9874704-5718-4a69-88a4-d6d5d08715d7 InstallationDate: Installed on 2015-01-03 (0 days ago) InstallationMedia: Linux Mint 17.1 Rebecca - Release amd64 20141126 MachineType: ASUSTeK Computer Inc. N53SV ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=eef70fc7-ad88-4dee-abec-96153d2eb0ed ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.10 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N53SV.215 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N53SV dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN53SV.215:bd01/09/2012:svnASUSTeKComputerInc.:pnN53SV:pvr1.0:rvnASUSTeKComputerInc.:rnN53SV:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: N53SV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407313/+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 1384515] [NEW] Laptop screen dims on logout
You have been subscribed to a public bug: After upgrading my laptop from Trusty to the Utopic final image, I noticed that when I logged out or switched users, the screen would dim. After logging back in, the brightness would not get restored. The Display Brightness slider in the Power Manager Plugin still showed full brightness, but it obviously was not. I had to click twice on the slider to restore the screen to full brightness. I then did a clean install and had the same issue. Similar to bug #1302025, but this is not due to inactivity. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xfce4-power-manager 1.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Oct 22 21:09:36 2014 InstallationDate: Installed on 2014-10-23 (0 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: xfce4-power-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Medium Status: Confirmed ** Tags: amd64 apport-bug iso-testing utopic -- Laptop screen dims on logout https://bugs.launchpad.net/bugs/1384515 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 1384515] Re: Laptop screen dims on logout
Thank you for testing this. ** Package changed: xserver-xorg-video-intel (Ubuntu) = linux (Ubuntu) ** Tags added: kernel-fixed-upstream-3.17 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1384515 Title: Laptop screen dims on logout Status in linux package in Ubuntu: Confirmed Bug description: After upgrading my laptop from Trusty to the Utopic final image, I noticed that when I logged out or switched users, the screen would dim. After logging back in, the brightness would not get restored. The Display Brightness slider in the Power Manager Plugin still showed full brightness, but it obviously was not. I had to click twice on the slider to restore the screen to full brightness. I then did a clean install and had the same issue. Similar to bug #1302025, but this is not due to inactivity. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xfce4-power-manager 1.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Oct 22 21:09:36 2014 InstallationDate: Installed on 2014-10-23 (0 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: xfce4-power-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1384515/+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 1407942] Re: CVE-2014-4322
CVE-2014-4322 ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Changed in: linux-lts-trusty (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-trusty (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-trusty (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-lts-trusty (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-utopic (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-lts-utopic (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-utopic (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-lts-utopic (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Trusty) Status: New = Invalid ** Changed
[Kernel-packages] [Bug 1407942] [NEW] CVE-2014-4322
*** This bug is a security vulnerability *** Public security bug reported: drivers/misc/qseecom.c in the QSEECOM driver for the Linux kernel 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, does not validate certain offset, length, and base values within an ioctl call, which allows attackers to gain privileges or cause a denial of service (memory corruption) via a crafted application. ** Affects: linux (Ubuntu) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Lucid) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Lucid) Importance: Medium Status: New ** Affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-trusty (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-utopic (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu Trusty)
[Kernel-packages] [Bug 1407947] Re: CVE-2014-9420
CVE-2014-9420 ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Changed in: linux-lts-trusty (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-trusty (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-trusty (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-lts-trusty (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-utopic (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-lts-utopic (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-utopic (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-lts-utopic (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Trusty) Status: New = Invalid ** Changed
[Kernel-packages] [Bug 1407952] [NEW] CVE-2014-9428
*** This bug is a security vulnerability *** Public security bug reported: The batadv_frag_merge_packets function in net/batman-adv/fragmentation.c in the B.A.T.M.A.N. implementation in the Linux kernel through 3.18.1 uses an incorrect length field during a calculation of an amount of memory, which allows remote attackers to cause a denial of service (mesh-node system crash) via fragmented packets. Break-Fix: - 5b6698b0e4a37053de35cc24ee695b98a7eb712b ** Affects: linux (Ubuntu) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Lucid) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Lucid) Importance: Medium Status: New ** Affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-trusty (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-utopic (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu Trusty)
[Kernel-packages] [Bug 1407722] Re: wifi connection does not associate using Dell XPS 13
Omer: New firmware has just been released for this hardware. Can you ensure your system is up to date, reboot, and see if this helps at all? Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1407722 Title: wifi connection does not associate using Dell XPS 13 Status in linux package in Ubuntu: Incomplete Bug description: Adding to this: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1315221 Having issues associating to networks within 5-6 meters length. Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 6b) Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:c470] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-43-generic 3.13.0-43.72 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: omerk 1983 F pulseaudio omerk 2742 F pulseaudio /dev/snd/controlC0: omerk 1983 F pulseaudio omerk 2742 F pulseaudio CurrentDesktop: Unity Date: Mon Jan 5 17:59:30 2015 HibernationDevice: RESUME=UUID=b74a5c36-aee6-4df3-99b5-f2b4752d9e64 InstallationDate: Installed on 2015-01-05 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. XPS13 9333 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic.efi.signed root=UUID=853548c8-96ec-4eec-a5fe-516f656daff9 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-43-generic N/A linux-backports-modules-3.13.0-43-generic N/A linux-firmware 1.127.10 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0D13CR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd09/11/2014:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0D13CR:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407722/+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 1407857] Re: Touchpad doesn't work after resume
*** This bug is a duplicate of bug 1393079 *** https://bugs.launchpad.net/bugs/1393079 ** This bug has been marked a duplicate of bug 1393079 Touchpad not working after suspend/resume -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1407857 Title: Touchpad doesn't work after resume Status in linux package in Ubuntu: Confirmed Bug description: Hi, I was asked to file a new bug after commenting on this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1393079?comments=all It seems to be a similar problem and I'm able to work around by doing a rmmod of hid_multitouch and modprobe using a script on resume. Thanks, Mike ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-28-generic 3.16.0-28.38 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nule 2229 F pulseaudio /dev/snd/controlC1: nule 2229 F pulseaudio CurrentDesktop: Unity Date: Mon Jan 5 22:55:49 2015 HibernationDevice: RESUME=UUID=d856beab-6ee1-4ca7-96bb-55d28630e61f InstallationDate: Installed on 2015-01-02 (3 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: Dell Inc. Inspiron 7347 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed root=UUID=d6ace3b7-b976-4a52-b3b8-0da281987fae ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.138 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0G1P68 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A02 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd09/18/2014:svnDellInc.:pnInspiron7347:pvr00h:rvnDellInc.:rn0G1P68:rvrA00:cvnDellInc.:ct8:cvrA02: dmi.product.name: Inspiron 7347 dmi.product.version: 00h dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407857/+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 1407945] [NEW] CVE-2014-9419
*** This bug is a security vulnerability *** Public security bug reported: The __switch_to function in arch/x86/kernel/process_64.c in the Linux kernel through 3.18.1 does not ensure that Thread Local Storage (TLS) descriptors are loaded before proceeding with other steps, which makes it easier for local users to bypass the ASLR protection mechanism via a crafted application that reads a TLS base address. Break-Fix: - f647d7c155f069c1a068030255c300663516420e ** Affects: linux (Ubuntu) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Lucid) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Lucid) Importance: Medium Status: New ** Affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-trusty (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-utopic (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu
[Kernel-packages] [Bug 1407947] [NEW] CVE-2014-9420
*** This bug is a security vulnerability *** Public security bug reported: The rock_continue function in fs/isofs/rock.c in the Linux kernel through 3.18.1 does not restrict the number of Rock Ridge continuation entries, which allows local users to cause a denial of service (infinite loop, and system crash or hang) via a crafted iso9660 image. Break-Fix: - f54e18f1b831c92f6512d2eedb224cd63d607d3d ** Affects: linux (Ubuntu) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Lucid) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Lucid) Importance: Medium Status: New ** Affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-trusty (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-utopic (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu Trusty) Importance: Medium Status: New ** Affects:
[Kernel-packages] [Bug 1407952] Re: CVE-2014-9428
CVE-2014-9428 ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Changed in: linux-lts-trusty (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-trusty (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-trusty (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-lts-trusty (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-raring (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-raring (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-raring (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-lts-raring (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Trusty) Status: New =
[Kernel-packages] [Bug 1407857] Re: Touchpad doesn't work after resume
Michael Litherland, thank you for reporting this and helping make Ubuntu better. As per http://www.dell.com/support/home/us/en/04/product-support/product/inspiron-13-7347-laptop/drivers an update to your computer's buggy and outdated BIOS is available (A03). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report. Once the BIOS is updated, and the information above is provided, then please mark this report Status Confirmed. Thank you for your understanding. ** This bug is no longer a duplicate of bug 1393079 Touchpad not working after suspend/resume ** Description changed: - Hi, + My touchpad doesn't work after resume. - I was asked to file a new bug after commenting on this bug: - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1393079?comments=all - It seems to be a similar problem and I'm able to work around by doing a - rmmod of hid_multitouch and modprobe using a script on resume. - - Thanks, - Mike + WORKAROUND: I'm able to work around by doing a rmmod of hid_multitouch + and modprobe using a script on resume. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-28-generic 3.16.0-28.38 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: nule 2229 F pulseaudio - /dev/snd/controlC1: nule 2229 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: nule 2229 F pulseaudio + /dev/snd/controlC1: nule 2229 F pulseaudio CurrentDesktop: Unity Date: Mon Jan 5 22:55:49 2015 HibernationDevice: RESUME=UUID=d856beab-6ee1-4ca7-96bb-55d28630e61f InstallationDate: Installed on 2015-01-02 (3 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: Dell Inc. Inspiron 7347 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed root=UUID=d6ace3b7-b976-4a52-b3b8-0da281987fae ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-3.16.0-28-generic N/A - linux-backports-modules-3.16.0-28-generic N/A - linux-firmware 1.138 + linux-restricted-modules-3.16.0-28-generic N/A + linux-backports-modules-3.16.0-28-generic N/A + linux-firmware 1.138 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0G1P68 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A02 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd09/18/2014:svnDellInc.:pnInspiron7347:pvr00h:rvnDellInc.:rn0G1P68:rvrA00:cvnDellInc.:ct8:cvrA02: dmi.product.name: Inspiron 7347 dmi.product.version: 00h dmi.sys.vendor: Dell Inc. ** Tags added: bios-outdated-a03 ** Changed in: linux (Ubuntu) Importance: Undecided = Low ** Changed in: linux (Ubuntu) Status: Confirmed = 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/1407857 Title: Touchpad doesn't work after resume Status in linux package in Ubuntu: Incomplete Bug description: My touchpad doesn't work after resume. WORKAROUND: I'm able to work around by doing a rmmod of hid_multitouch and modprobe using a script on resume. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-28-generic 3.16.0-28.38 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nule 2229 F pulseaudio /dev/snd/controlC1: nule 2229 F pulseaudio CurrentDesktop: Unity Date: Mon Jan 5 22:55:49 2015 HibernationDevice: RESUME=UUID=d856beab-6ee1-4ca7-96bb-55d28630e61f InstallationDate: Installed on 2015-01-02 (3 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: Dell Inc. Inspiron 7347 ProcFB: 0 inteldrmfb ProcKernelCmdLine:
[Kernel-packages] [Bug 1406982] Re: WARNING: CPU: 1 PID: 1253 at /build/buildd/linux-3.13.0/drivers/gpu/drm/i915/intel_display.c:9237 intel_modeset_check_state+0x62d/0x780 [i915]
** Tags removed: needs-bisect ** Tags added: needs-reverse-bisect -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1406982 Title: WARNING: CPU: 1 PID: 1253 at /build/buildd/linux-3.13.0/drivers/gpu/drm/i915/intel_display.c:9237 intel_modeset_check_state+0x62d/0x780 [i915] Status in linux package in Ubuntu: Incomplete Bug description: Hi there, I am also facing the same issue. I have Dell Inspiron 1525 running 14.04.1 LTS and kernel version 3.13.0-43-generic. System becomes unusable completly and screen goes off as well. Following is what i have found in dmesg [ 144.446687] WARNING: CPU: 1 PID: 1253 at /build/buildd/linux-3.13.0/drivers/gpu/drm/i915/intel_display.c:9237 intel_modeset_check_state+0x62d/0x780 [i915]() [ 144.446690] encoder's hw state doesn't match sw tracking (expected 0, found 1) [ 144.446691] Modules linked in: cdc_ether usbnet mii usb_storage ctr ccm bnep rfcomm bluetooth snd_hda_codec_idt snd_hda_codec_hdmi uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev gpio_ich dell_wmi sparse_keymap dell_laptop dcdbas snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event dm_multipath scsi_dh snd_rawmidi coretemp snd_seq joydev serio_raw arc4 r852 sm_common nand nand_ecc nand_bch bch r592 nand_ids mtd memstick iwl3945 snd_seq_device iwlegacy mac80211 snd_timer snd cfg80211 lpc_ich i915 drm_kms_helper soundcore drm i2c_algo_bit mac_hid wmi video parport_pc ppdev lp parport hid_generic usbhid hid firewire_ohci psmouse sdhci_pci sdhci ahci firewire_core libahci crc_itu_t sky2 [ 144.446750] CPU: 1 PID: 1253 Comm: Xorg Tainted: GW 3.13.0-43-generic #72-Ubuntu [ 144.446753] Hardware name: Dell Inc. Inspiron 1525 /0WP007, BIOS A17 10/27/2009 [ 144.446755] 0009 8800aaaf99f8 81720bf6 8800aaaf9a40 [ 144.446759] 8800aaaf9a30 810677cd 8800aaaf9ab0 0001 [ 144.446763] 880036621800 880036621af8 8800b6cc4800 8800aaaf9a90 [ 144.446767] Call Trace: [ 144.446770] [81720bf6] dump_stack+0x45/0x56 [ 144.446774] [810677cd] warn_slowpath_common+0x7d/0xa0 [ 144.446778] [8106783c] warn_slowpath_fmt+0x4c/0x50 [ 144.446802] [a01ad285] ? intel_sdvo_get_hw_state+0x55/0xc0 [i915] [ 144.446823] [a019751d] intel_modeset_check_state+0x62d/0x780 [i915] [ 144.446846] [a0197705] intel_set_mode+0x25/0x30 [i915] [ 144.446867] [a01977d6] intel_release_load_detect_pipe+0xc6/0xf0 [i915] [ 144.446892] [a01bf8e9] intel_tv_detect+0x359/0x500 [i915] [ 144.446901] [a00dc25b] drm_helper_probe_single_connector_modes+0x1eb/0x380 [drm_kms_helper] [ 144.446918] [a011e617] drm_mode_getconnector+0x417/0x480 [drm] [ 144.446923] [8108eb62] ? __hrtimer_start_range_ns+0x1a2/0x3a0 [ 144.446936] [a010fc22] drm_ioctl+0x502/0x630 [drm] [ 144.446942] [81077f42] ? __set_task_blocked+0x32/0x70 [ 144.446948] [811d0e90] do_vfs_ioctl+0x2e0/0x4c0 [ 144.446952] [811d10f1] SyS_ioctl+0x81/0xa0 [ 144.446956] [817316ad] system_call_fastpath+0x1a/0x1f [ 144.446958] ---[ end trace ccc7cdf9d70214e2 ]--- [ 402.128351] perf samples too long (2503 2500), lowering kernel.perf_event_max_sample_rate to 5 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-43-generic 3.13.0-43.72 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gurvinder 2023 F pulseaudio gurvinder 3161 F pulseaudio CurrentDesktop: Unity Date: Fri Jan 2 01:27:54 2015 HibernationDevice: RESUME=UUID=398088de-7b7e-4d91-adb0-4d5b4cb8d963 InstallationDate: Installed on 2014-11-22 (40 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Inspiron 1525 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic root=UUID=6dc40c4b-5124-4216-a79f-44b870f54651 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-43-generic N/A linux-backports-modules-3.13.0-43-generic N/A linux-firmware 1.127.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0WP007 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Kernel-packages] [Bug 1403855] Re: CVE-2014-9322
** Description changed: - [x86: local privesc due to bad_iret and paranoid entry incompatibility] + arch/x86/kernel/entry_64.S in the Linux kernel before 3.17.5 does not + properly handle faults associated with the Stack Segment (SS) segment + register, which allows local users to gain privileges by triggering an + IRET instruction that leads to access to a GS Base address from the + wrong space. Break-Fix: - 6f442be2fb22be02cafa606f1769fa1e6f894441 Break-Fix: - b645af2d5905c4e32399005b867987919cbfc3ae -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1403855 Title: CVE-2014-9322 Status in linux package in Ubuntu: New Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Lucid: New Status in linux-armadaxp source package in Lucid: Invalid Status in linux-ec2 source package in Lucid: New Status in linux-fsl-imx51 source package in Lucid: Invalid Status in linux-lts-backport-maverick source package in Lucid: New Status in linux-lts-backport-natty source package in Lucid: New Status in linux-lts-quantal source package in Lucid: Invalid Status in linux-lts-raring source package in Lucid: Invalid Status in linux-lts-saucy source package in Lucid: Invalid Status in linux-lts-trusty source package in Lucid: Invalid Status in linux-lts-utopic source package in Lucid: Invalid Status in linux-mvl-dove source package in Lucid: Invalid Status in linux-ti-omap4 source package in Lucid: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: New Status in linux-lts-raring source package in Precise: New Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: New Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Utopic: New Status in linux-armadaxp source package in Utopic: Invalid Status in linux-ec2 source package in Utopic: Invalid Status in linux-fsl-imx51 source package in Utopic: Invalid Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux-lts-quantal source package in Utopic: Invalid Status in linux-lts-raring source package in Utopic: Invalid Status in linux-lts-saucy source package in Utopic: Invalid Status in linux-lts-trusty source package in Utopic: Invalid Status in linux-lts-utopic source package in Utopic: Invalid Status in linux-mvl-dove source package in Utopic: Invalid Status in linux-ti-omap4 source package in Utopic: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package
[Kernel-packages] [Bug 1407569] Re: [Dell Latitude 3340] Bluetooth cannot be controlled by the wilreless key
** Changed in: linux (Ubuntu) Importance: Undecided = Low -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1407569 Title: [Dell Latitude 3340] Bluetooth cannot be controlled by the wilreless key Status in linux package in Ubuntu: Confirmed Bug description: CID: 201312-14381 Dell Latitude 3340 The wireless key cannot control the Bluetooth on this system. Steps: 1. Install 14.04.1 + update, boot to desktop 2. Try to disable / enable the Bluetooth by using the wireless key Actual result: * before pressing the wireless key ubuntu@201312-14381:~$ rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-bluetooth: Bluetooth Soft blocked: no Hard blocked: no * After pressing the wireless key, Wifi will be disabled, but the Bluetooth does not. The BT applet won't be disabled. I could still run Set up new devices... from the menu. hcitool scan from console still can find some other devices. ubuntu@201312-14381:~$ rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: yes 2: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: yes 3: dell-bluetooth: Bluetooth Soft blocked: no Hard blocked: yes ubuntu@201312-14381:~$ hcitool scan Scanning ... 20:16:D8:6F:A2:74 chaos-0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-43-generic 3.13.0-43.72 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1540 F pulseaudio /dev/snd/controlC0: ubuntu 1540 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Mon Jan 5 01:47:58 2015 HibernationDevice: RESUME=UUID=8881bf5a-55d6-4314-80db-170ff3d262b6 InstallationDate: Installed on 2015-01-05 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Latitude 3340 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic.efi.signed root=UUID=9f9c408e-d1c2-496c-9fd2-8f9ecb77810b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-43-generic N/A linux-backports-modules-3.13.0-43-generic N/A linux-firmware 1.127.10 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/02/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 4OA010 dmi.board.vendor: Dell Inc. dmi.board.version: D01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd05/02/2014:svnDellInc.:pnLatitude3340:pvr01:rvnDellInc.:rn4OA010:rvrD01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude 3340 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407569/+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 1407945] Re: CVE-2014-9419
CVE-2014-9419 ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Changed in: linux-lts-trusty (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-trusty (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-trusty (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-lts-trusty (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-raring (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-raring (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-raring (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-lts-raring (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Trusty) Status: New =
[Kernel-packages] [Bug 1393079] Re: Touchpad not working after suspend/resume
@ Christopher M. Penalver: It is pretty clear this bug isn't of a low importance. ** Changed in: linux (Ubuntu) Importance: Low = Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1393079 Title: Touchpad not working after suspend/resume Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 14.10 on an Acer Laptop, model: Aspire E5-571G-941Y $ uname -a Linux Acer-Aspire-E5-571G 3.16.0-24-generic #32-Ubuntu SMP Tue Oct 28 13:07:32 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Every time I suspend, the trackpad no longer works when resuming. I see several other people have the same issue with the same laptop here: http://ubuntuforums.org/showthread.php?t=2250002 (some people say it's a 14.10 specific problem) I realize this report is very poor but please don't hesitate to request data / clarifications from me, I'll be happy to help. --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bod3942 F pulseaudio /dev/snd/controlC1: bod3942 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=2e6e7d72-637c-4b16-8cda-0471dfb711d4 InstallationDate: Installed on 2014-11-14 (15 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Acer Aspire E5-571G Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed root=UUID=94aa9203-873c-4dff-8207-4e6b33a6a3e7 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 RelatedPackageVersions: linux-restricted-modules-3.16.0-25-generic N/A linux-backports-modules-3.16.0-25-generic N/A linux-firmware 1.138 Tags: utopic Uname: Linux 3.16.0-25-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-11-14 (15 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/06/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HB dmi.board.vendor: Acer dmi.board.version: V1.04 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd05/06/2014:svnAcer:pnAspireE5-571G:pvrV1.04:rvnAcer:rnEA50_HB:rvrV1.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.name: Aspire E5-571G dmi.product.version: V1.04 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1393079/+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 1407522] Re: bcmwl package was sugested by KDE driver manager but broke the system
Done. Same problem. After installing bcmwl-kernel-source in practice laptop is without any internet connection for not a-bit-more experienced user as modprobe wl will try to remove the NIC driver b44 and then trough modprobe ignore install b44 wich due to the broken module/kernel state cannot be undone, process hangs. After reboot if wl is not explicitly blacklisted it will trigger the same events and prevent WIFI or LAN driver to work at all on the machine... really annoing... Good that Unity did not suggest me to install bcmwl as KDE did on 14.10 and 14.04 :)... Some technical information daily build of 15.04 from 06.01.2015 lsb_release -rd Description:Ubuntu Vivid Vervet (development branch) Release:15.04 uname -a Linux ubuntu 3.16.0-28-generic #38-Ubuntu SMP Fri Dec 12 17:37:40 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux apt-cache policy bcmwl-kernel-source bcmwl-kernel-source: Installed: 6.30.223.248+bdcom-0ubuntu2 Candidate: 6.30.223.248+bdcom-0ubuntu2 Version table: *** 6.30.223.248+bdcom-0ubuntu2 0 500 cdrom://Ubuntu 15.04 _Vivid Vervet_ - Alpha amd64 (20150106)/ vivid/restricted amd64 Packages 500 http://archive.ubuntu.com/ubuntu/ vivid/restricted amd64 Packages 100 /var/lib/dpkg/status Jan 6 10:44:58 ubuntu kernel: [ 3042.972927] malloc in abgphy done Jan 6 10:44:58 ubuntu kernel: [ 3042.973350] wl driver 6.30.223.248 (r487574) failed with code 21 Jan 6 10:44:58 ubuntu kernel: [ 3042.973384] [ cut here ] Jan 6 10:44:58 ubuntu kernel: [ 3042.974356] kernel BUG at include/net/cfg80211.h:3343! Jan 6 10:44:58 ubuntu kernel: [ 3042.975276] invalid opcode: [#1] SMP ** Attachment added: syslog output https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1407522/+attachment/4292893/+files/syslog -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1407522 Title: bcmwl package was sugested by KDE driver manager but broke the system Status in bcmwl package in Ubuntu: Incomplete Bug description: On fresh 14.10 install on the first GUI run in KDE the KDE Driver Manager suggested installation of bcmwl-kernel-source (see attached screenshot)for my Broadcom Corporation BCM4311. After successful installation of the package and restart, my system got Jan 4 23:32:13 Beatles kernel: [ 19.485177] wl driver 6.30.223.248 (r487574) failed with code 21 Jan 4 23:32:13 Beatles kernel: [ 19.485208] [ cut here ] Jan 4 23:32:13 Beatles kernel: [ 19.485242] kernel BUG at include/net/cfg80211.h:3343! full description of the message in attached file (syslog_extracted.log). For some reason this also affects the driver for my NIC and my laptop got out of any possible network connection. So instead of configuring the wireless card it left me with only lo interface :(. I would expect properly configured modules for WAN and LAN Luckily apt-get remove --purge bcmwl-kernel-source restores the previous state so I can submit this bug via LAN. Now I'm running Ubuntu 14.10 but the same happened half an year ago when I tried to install 14.04 on this laptop. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: bcmwl-kernel-source (not installed) ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jan 5 01:00:26 2015 SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1407522/+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 1407604] Re: [Dell Inspiron 7548] Brightness control does not work on 14.04.1
How about passing video.use_native_backlight=1 to kernel, or try Utopic's 3.16 kernel? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1407604 Title: [Dell Inspiron 7548] Brightness control does not work on 14.04.1 Status in HWE Next Project: New Status in linux package in Ubuntu: Confirmed Bug description: CID: 201408-15450 Inspiron 7548 Brightness control does not work on this system with 14.04.1 The brightness level indicator would change with hotkey events, but the brightness itself does not. Debugging information: root@201408-15450:~$ ls /sys/class/backlight acpi_video0 intel_backlight root@201408-15450:~$ grep -r . /proc/acpi /proc/acpi/battery/BAT0/alarm:alarm: unsupported /proc/acpi/battery/BAT0/state:present: yes /proc/acpi/battery/BAT0/state:capacity state: ok /proc/acpi/battery/BAT0/state:charging state: charging /proc/acpi/battery/BAT0/state:present rate:474 mA /proc/acpi/battery/BAT0/state:remaining capacity: 3811 mAh /proc/acpi/battery/BAT0/state:present voltage: 13006 mV /proc/acpi/battery/BAT0/info:present: yes /proc/acpi/battery/BAT0/info:design capacity: 3900 mAh /proc/acpi/battery/BAT0/info:last full capacity: 3900 mAh /proc/acpi/battery/BAT0/info:battery technology: non-rechargeable /proc/acpi/battery/BAT0/info:design voltage: 11400 mV /proc/acpi/battery/BAT0/info:design capacity warning: 390 mAh /proc/acpi/battery/BAT0/info:design capacity low: 0 mAh /proc/acpi/battery/BAT0/info:cycle count: 0 /proc/acpi/battery/BAT0/info:capacity granularity 1: 100 mAh /proc/acpi/battery/BAT0/info:capacity granularity 2: 0 mAh /proc/acpi/battery/BAT0/info:model number:Dell /proc/acpi/battery/BAT0/info:serial number: 480 /proc/acpi/battery/BAT0/info:battery type:LION /proc/acpi/battery/BAT0/info:OEM info:SIMPLO /proc/acpi/button/lid/LID0/state:state: open /proc/acpi/ac_adapter/ADP1/state:state: on-line /proc/acpi/wakeup:Device S-state Status Sysfs node /proc/acpi/wakeup:RP01 S4*disabled pci::00:1c.0 /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:RP04 S4*disabled pci::00:1c.3 /proc/acpi/wakeup:PXSX S4*disabled pci::07:00.0 /proc/acpi/wakeup:RP05 S4*disabled pci::00:1c.4 /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:EHC1 S0*enabled pci::00:1d.0 /proc/acpi/wakeup:XHC S0*enabled pci::00:14.0 /proc/acpi/wakeup:HDEF S4*disabled pci::00:1b.0 /proc/acpi/wakeup:LID0 S3*enabled root@201408-15450:~$ dmesg | grep 'ACPI: Video' [2.843516] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) root@201408-15450:~$ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-43-generic 3.13.0-43.72 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1512 F pulseaudio /dev/snd/controlC0: ubuntu 1512 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Mon Jan 5 04:10:59 2015 HibernationDevice: RESUME=UUID=87828d2c-0d30-454b-90f1-ed89c2790e76 InstallationDate: Installed on 2015-01-05 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Inspiron 7548 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic.efi.signed root=UUID=4cf32401-def5-4cf9-a237-f0bfb729a6cc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-43-generic N/A linux-backports-modules-3.13.0-43-generic N/A linux-firmware 1.127.10 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA00:bd11/19/2014:svnDellInc.:pnInspiron7548:pvrA00:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 7548 dmi.product.version: A00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1407604/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to
[Kernel-packages] [Bug 1391496] Re: [Intel DQ67SW] Can not enter password to decrypt disk at boot
It appears that 3.16.0-28-generic fixes this problem so I will not do a full bisect. After successfully booting and decrypting my disks with 3.16.0-28-generic, I have just rebooted to 3.16.0-26-generic to confirm that the issue is still present there. I assume that this issue should now be closed. Thanks for your help! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1391496 Title: [Intel DQ67SW] Can not enter password to decrypt disk at boot Status in linux package in Ubuntu: Incomplete Bug description: I have upgraded from Ubuntu 14.04 to 14.10. My whole disk is encrypted with luks and since the upgrade I have found I can no longer unlock my disk at boot. The enter password screen appears, but typing does not cause any characters to appear in the password box. However, if I hit ctrl-alt f7 (not sure of the precise function key) I get a black screen with a flashing white cursor and I can see the password that I entered. This would seem to imply that this is not a problem with the usb drivers, as has been reported in other similar bugs. It's as if the focus is simply in the wrong place at the time when I need to enter my password. Entering the password anyway and pressing enter has no effect. By using Grub to select the previous kernel, I can then decrypt my disk and use the system as normal. The working kernel version is 3.13.0-39-generic. The problematic kernel is 3.16.0-24-generic. --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: mjs510 3162 F pulseaudio /dev/snd/controlC2: mjs510 3162 F pulseaudio /dev/snd/controlC1: mjs510 3162 F pulseaudio /dev/snd/controlC0: mjs510 3162 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=66fe5f6c-9937-43f3-90ed-9764c8a9a263 IwConfig: eth0 no wireless extensions. lono wireless extensions. Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=/dev/mapper/ubuntu-root ro quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 RelatedPackageVersions: linux-restricted-modules-3.13.0-39-generic N/A linux-backports-modules-3.13.0-39-generic N/A linux-firmware 1.138 RfKill: Tags: utopic Uname: Linux 3.13.0-39-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-31 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: SWQ6710H.86A.0049.2011.0314.1053 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DQ67SW dmi.board.vendor: Intel Corporation dmi.board.version: AAG12527-308 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrSWQ6710H.86A.0049.2011.0314.1053:bd03/14/2011:svnViglen:pn:pvr:rvnIntelCorporation:rnDQ67SW:rvrAAG12527-308:cvn:ct3:cvr: dmi.sys.vendor: Viglen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1391496/+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 1407986] [NEW] Kernel hard freeze at random time (very often)
Public bug reported: The hardware is Dell Vostro V131 notebook. While using the system at random moments kernel hardfeezes. Ther are no inforamtions logged nowhere. The view on the screen is just freezing, nothing works except hard power off. I was trying REISUB etc. I was thingking this is SSD/RAM failure but after replacing them the bug still exists. Tried mainline kernel 3.17 from PPA the bug still exists. I haven't found what causes excalcy this bug ie. software/hardware. Sometimes it is working many hours and nothing happends and sometimes just after few seconds after boot the system is hardfreezed. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-28-generic 3.16.0-28.38 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bzyx 2832 F pulseaudio CurrentDesktop: KDE Date: Tue Jan 6 15:11:11 2015 InstallationDate: Installed on 2013-11-22 (410 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Dell Inc. Vostro V131 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic root=UUID=5568a9a0-d6f3-41d5-bde8-5a5f709fc110 ro quiet splash intel_pstate=enable vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.140-0~127~ubuntu14.10.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2014-11-02 (65 days ago) dmi.bios.date: 05/03/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0P0TH6 dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA06:bd05/03/2013:svnDellInc.:pnVostroV131:pvrNotSpecified:rvnDellInc.:rn0P0TH6:rvrA06:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro V131 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1407986 Title: Kernel hard freeze at random time (very often) Status in linux package in Ubuntu: Confirmed Bug description: The hardware is Dell Vostro V131 notebook. While using the system at random moments kernel hardfeezes. Ther are no inforamtions logged nowhere. The view on the screen is just freezing, nothing works except hard power off. I was trying REISUB etc. I was thingking this is SSD/RAM failure but after replacing them the bug still exists. Tried mainline kernel 3.17 from PPA the bug still exists. I haven't found what causes excalcy this bug ie. software/hardware. Sometimes it is working many hours and nothing happends and sometimes just after few seconds after boot the system is hardfreezed. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-28-generic 3.16.0-28.38 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bzyx 2832 F pulseaudio CurrentDesktop: KDE Date: Tue Jan 6 15:11:11 2015 InstallationDate: Installed on 2013-11-22 (410 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Dell Inc. Vostro V131 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic root=UUID=5568a9a0-d6f3-41d5-bde8-5a5f709fc110 ro quiet splash intel_pstate=enable vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.140-0~127~ubuntu14.10.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2014-11-02 (65 days ago) dmi.bios.date: 05/03/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0P0TH6 dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA06:bd05/03/2013:svnDellInc.:pnVostroV131:pvrNotSpecified:rvnDellInc.:rn0P0TH6:rvrA06:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro V131 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1391496] Re: [Intel DQ67SW] Can not enter password to decrypt disk at boot
Max Spicer, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1391496/comments/25 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find. ** Changed in: linux (Ubuntu) Status: Incomplete = Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1391496 Title: [Intel DQ67SW] Can not enter password to decrypt disk at boot Status in linux package in Ubuntu: Invalid Bug description: I have upgraded from Ubuntu 14.04 to 14.10. My whole disk is encrypted with luks and since the upgrade I have found I can no longer unlock my disk at boot. The enter password screen appears, but typing does not cause any characters to appear in the password box. However, if I hit ctrl-alt f7 (not sure of the precise function key) I get a black screen with a flashing white cursor and I can see the password that I entered. This would seem to imply that this is not a problem with the usb drivers, as has been reported in other similar bugs. It's as if the focus is simply in the wrong place at the time when I need to enter my password. Entering the password anyway and pressing enter has no effect. By using Grub to select the previous kernel, I can then decrypt my disk and use the system as normal. The working kernel version is 3.13.0-39-generic. The problematic kernel is 3.16.0-24-generic. --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: mjs510 3162 F pulseaudio /dev/snd/controlC2: mjs510 3162 F pulseaudio /dev/snd/controlC1: mjs510 3162 F pulseaudio /dev/snd/controlC0: mjs510 3162 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=66fe5f6c-9937-43f3-90ed-9764c8a9a263 IwConfig: eth0 no wireless extensions. lono wireless extensions. Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=/dev/mapper/ubuntu-root ro quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 RelatedPackageVersions: linux-restricted-modules-3.13.0-39-generic N/A linux-backports-modules-3.13.0-39-generic N/A linux-firmware 1.138 RfKill: Tags: utopic Uname: Linux 3.13.0-39-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-31 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: SWQ6710H.86A.0049.2011.0314.1053 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DQ67SW dmi.board.vendor: Intel Corporation dmi.board.version: AAG12527-308 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrSWQ6710H.86A.0049.2011.0314.1053:bd03/14/2011:svnViglen:pn:pvr:rvnIntelCorporation:rnDQ67SW:rvrAAG12527-308:cvn:ct3:cvr: dmi.sys.vendor: Viglen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1391496/+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 1407760] Re: Kernel crash when setting vxlan tunnel over the mlx4_en when acting as PF
** Also affects: linux (Ubuntu Utopic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu Trusty)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1407760
Title:
Kernel crash when setting vxlan tunnel over the mlx4_en when acting as
PF
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Utopic:
New
Bug description:
Eyal Perry (~eyalpe) writes:
When enabling SR-IOV on Mellanox devices and setting vxlan tunnel over the PF
device (adding vxlan port to an OVS bridge),
the kernel is crushing as result of the unimplemented ndos:
.ndo_{add,del}_vxlan_port
This issue was fixed in upstream kernel:
9737c6a net/mlx4_en: Add VXLAN ndo calls to the PF net device ops too
I've backported it to 3.16 (by removing the yet to be introduced
ndo_gso_check) and attached the backported version here.
The patch was built and tested on top of ubuntu-trusty: abb1293
(UBUNTU: Ubuntu-lts-3.16.0-29.39~14.04.1)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407760/+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 1407986] Re: Kernel hard freeze at random time (very often)
Marcin Jabrzyk, thank you for reporting this and helping make Ubuntu better. Could you please capture the crash via https://help.ubuntu.com/community/DebuggingSystemCrash ? Also, could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. If the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags: kernel-fixed-upstream kernel-fixed-upstream-VERSION-NUMBER where VERSION-NUMBER is the version number of the kernel you tested exactly shown as: kernel-fixed-upstream-3.19-rc2 This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. If the mainline kernel does not fix this bug, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-VERSION-NUMBER Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding. ** Tags added: kernel-bug-exists-upstream-3.17 needs-upstream-testing ** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** Changed in: linux (Ubuntu) Status: Confirmed = 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/1407986 Title: Kernel hard freeze at random time (very often) Status in linux package in Ubuntu: Incomplete Bug description: The hardware is Dell Vostro V131 notebook. While using the system at random moments kernel hardfeezes. Ther are no inforamtions logged nowhere. The view on the screen is just freezing, nothing works except hard power off. I was trying REISUB etc. I was thingking this is SSD/RAM failure but after replacing them the bug still exists. Tried mainline kernel 3.17 from PPA the bug still exists. I haven't found what causes excalcy this bug ie. software/hardware. Sometimes it is working many hours and nothing happends and sometimes just after few seconds after boot the system is hardfreezed. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-28-generic 3.16.0-28.38 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bzyx 2832 F pulseaudio CurrentDesktop: KDE Date: Tue Jan 6 15:11:11 2015 InstallationDate: Installed on 2013-11-22 (410 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Dell Inc. Vostro V131 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic root=UUID=5568a9a0-d6f3-41d5-bde8-5a5f709fc110 ro quiet splash intel_pstate=enable vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.140-0~127~ubuntu14.10.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2014-11-02 (65 days ago) dmi.bios.date: 05/03/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0P0TH6 dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA06:bd05/03/2013:svnDellInc.:pnVostroV131:pvrNotSpecified:rvnDellInc.:rn0P0TH6:rvrA06:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro V131 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407986/+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 1407522] Re: bcmwl package was sugested by KDE driver manager but broke the system
Rostislav Kandilarov, did this problem not occur in a release prior to Utopic? As well, does this occur using https://launchpad.net/ubuntu/+source /broadcom-sta instead of bcmwl? ** Tags added: vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1407522 Title: bcmwl package was sugested by KDE driver manager but broke the system Status in bcmwl package in Ubuntu: Incomplete Bug description: On fresh 14.10 install on the first GUI run in KDE the KDE Driver Manager suggested installation of bcmwl-kernel-source (see attached screenshot)for my Broadcom Corporation BCM4311. After successful installation of the package and restart, my system got Jan 4 23:32:13 Beatles kernel: [ 19.485177] wl driver 6.30.223.248 (r487574) failed with code 21 Jan 4 23:32:13 Beatles kernel: [ 19.485208] [ cut here ] Jan 4 23:32:13 Beatles kernel: [ 19.485242] kernel BUG at include/net/cfg80211.h:3343! full description of the message in attached file (syslog_extracted.log). For some reason this also affects the driver for my NIC and my laptop got out of any possible network connection. So instead of configuring the wireless card it left me with only lo interface :(. I would expect properly configured modules for WAN and LAN Luckily apt-get remove --purge bcmwl-kernel-source restores the previous state so I can submit this bug via LAN. Now I'm running Ubuntu 14.10 but the same happened half an year ago when I tried to install 14.04 on this laptop. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: bcmwl-kernel-source (not installed) ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jan 5 01:00:26 2015 SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1407522/+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 1405437] Re: [Dell Precision M4800] iwlwifi regularly loses connection on Intel 7260
arty: linux-firmware 1.138.1 has just been released with the latest firmware for your hardware. Please ensure your system is fully up to date, reboot, and see if this helps at all. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1405437 Title: [Dell Precision M4800] iwlwifi regularly loses connection on Intel 7260 Status in linux package in Ubuntu: Incomplete Bug description: About every 10 minutes my WiFi disconnects and a line like this appears in syslog: Dec 24 11:31:31 work kernel: [ 2721.017478] wlan0: deauthenticated from 10:c6:1f:2c:49:56 (Reason: 7=CLASS3_FRAME_FROM_NONASSOC_STA) It is accompanied later by such line: Dec 24 11:31:46 work NetworkManager[902]: info (wlan0): device state change: activated - failed (reason 'SSID not found') [100 120 53] The network disappears from the list and only becomes visible after I disable and re-enable networking via the network applet. I don't remember seeing this problem at work where they use Cisco routers. I see the problem at home with my Speedport 723V Typ A router (a+b+n mode, WPA2). This may be affected by number of other wifi networks which are visible here: at least 17 at the moment. 03:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 73) Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:4470] WORKAROUND: /etc/modprobe.d/iwlwifi.conf : options iwlwifi 11n_disable=1 Drops did not cause loss of my network, and reconnects happened mostly in the same second. However at some moments there were just too many drops. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-28-generic 3.16.0-28.38 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: treguben 2520 F pulseaudio /dev/snd/controlC0: treguben 2520 F pulseaudio CurrentDesktop: Unity Date: Wed Dec 24 15:06:25 2014 HibernationDevice: RESUME=UUID=82445dd2-3bcf-42f7-ae59-4fba694e25de InstallationDate: Installed on 2014-12-11 (12 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: Dell Inc. Precision M4800 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed root=UUID=9a116abe-59b9-48b8-abe4-5064a191ac51 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.138 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/03/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0T3YTY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd12/03/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn0T3YTY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1405437/+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 1407760] Re: Kernel crash when setting vxlan tunnel over the mlx4_en when acting as PF
** Description changed:
Eyal Perry (~eyalpe) writes:
+ [Impact]
When enabling SR-IOV on Mellanox devices and setting vxlan tunnel over the PF
device (adding vxlan port to an OVS bridge),
- the kernel is crushing as result of the unimplemented ndos:
.ndo_{add,del}_vxlan_port
+ the kernel is crashing as result of the unimplemented ndos:
.ndo_{add,del}_vxlan_port
+ [Fix]
This issue was fixed in upstream kernel:
9737c6a net/mlx4_en: Add VXLAN ndo calls to the PF net device ops too
I've backported it to 3.16 (by removing the yet to be introduced
ndo_gso_check) and attached the backported version here.
The patch was built and tested on top of ubuntu-trusty: abb1293
(UBUNTU: Ubuntu-lts-3.16.0-29.39~14.04.1)
+
+ This only affect 3.16 since it has the VLAN features.
+
+ [Test Case]
+ Use the affected Mellanox device w/ an Ubuntu 3.16 kernel. Setup vxlan tunnel
over PF device. This should succeed.
** Changed in: linux (Ubuntu)
Status: Triaged = Fix Released
** Changed in: linux (Ubuntu Utopic)
Status: New = In Progress
** Changed in: linux (Ubuntu Utopic)
Importance: Undecided = Medium
** Description changed:
Eyal Perry (~eyalpe) writes:
[Impact]
When enabling SR-IOV on Mellanox devices and setting vxlan tunnel over the PF
device (adding vxlan port to an OVS bridge),
the kernel is crashing as result of the unimplemented ndos:
.ndo_{add,del}_vxlan_port
[Fix]
This issue was fixed in upstream kernel:
9737c6a net/mlx4_en: Add VXLAN ndo calls to the PF net device ops too
- I've backported it to 3.16 (by removing the yet to be introduced
ndo_gso_check) and attached the backported version here.
+
+ ~/linux$ git describe --contains 9737c6ab7afbc950e997ef80cba2c40dbbd16ea4
+ v3.18-rc6~9^2~12
+
+ I've backported it to 3.16 (by removing the yet to be introduced
+ ndo_gso_check) and attached the backported version here.
The patch was built and tested on top of ubuntu-trusty: abb1293
(UBUNTU: Ubuntu-lts-3.16.0-29.39~14.04.1)
This only affect 3.16 since it has the VLAN features.
[Test Case]
Use the affected Mellanox device w/ an Ubuntu 3.16 kernel. Setup vxlan tunnel
over PF device. This should succeed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1407760
Title:
Kernel crash when setting vxlan tunnel over the mlx4_en when acting as
PF
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Utopic:
In Progress
Bug description:
Eyal Perry (~eyalpe) writes:
[Impact]
When enabling SR-IOV on Mellanox devices and setting vxlan tunnel over the PF
device (adding vxlan port to an OVS bridge),
the kernel is crashing as result of the unimplemented ndos:
.ndo_{add,del}_vxlan_port
[Fix]
This issue was fixed in upstream kernel:
9737c6a net/mlx4_en: Add VXLAN ndo calls to the PF net device ops too
~/linux$ git describe --contains 9737c6ab7afbc950e997ef80cba2c40dbbd16ea4
v3.18-rc6~9^2~12
I've backported it to 3.16 (by removing the yet to be introduced
ndo_gso_check) and attached the backported version here.
The patch was built and tested on top of ubuntu-trusty: abb1293
(UBUNTU: Ubuntu-lts-3.16.0-29.39~14.04.1)
This only affect 3.16 since it has the VLAN features.
[Test Case]
Use the affected Mellanox device w/ an Ubuntu 3.16 kernel. Setup vxlan tunnel
over PF device. This should succeed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407760/+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 1402141] Re: Ubuntu 14.10 freezes when use smt-enabled=off as kernel argument
Now in Linus' tree:
git describe --contains d70a54e2d08510a99b1f10eceeae6f2f7086e226
v3.19-rc1~22^2
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1402141
Title:
Ubuntu 14.10 freezes when use smt-enabled=off as kernel argument
Status in linux package in Ubuntu:
Triaged
Bug description:
== Comment: #0 - Paulo Flabiano Smorigo pfsmor...@br.ibm.com - 2014-11-18
12:28:42 ==
Using Ubuntu as the host, if you add smt-enabled=off as kernel argument, the
system will boot until the Freeing initrd memory line:
...
[1.371729] vgaarb: loaded
[1.372989] SCSI subsystem initialized
[1.373977] libata version 3.00 loaded.
[1.374158] usbcore: registered new interface driver usbfs
[1.374246] usbcore: registered new interface driver hub
[1.374382] usbcore: registered new device driver usb
[1.374505] pps_core: LinuxPPS API ver. 1 registered
[1.374563] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo
Giometti giome...@linux.it
[1.374671] PTP clock support registered
[1.377135] NetLabel: Initializing
[1.377218] NetLabel: domain hash size = 128
[1.377328] NetLabel: protocols = UNLABELED CIPSOv4
[1.377472] NetLabel: unlabeled traffic allowed by default
[1.377983] Switched to clocksource timebase
[1.395029] AppArmor: AppArmor Filesystem Enabled
[1.402044] NET: Registered protocol family 2
[1.403795] TCP established hash table entries: 524288 (order: 6, 4194304
bytes)
[1.408343] TCP bind hash table entries: 65536 (order: 4, 1048576 bytes)
[1.409301] TCP: Hash tables configured (established 524288 bind 65536)
[1.409490] TCP: reno registered
[1.409645] UDP hash table entries: 65536 (order: 5, 2097152 bytes)
[1.411943] UDP-Lite hash table entries: 65536 (order: 5, 2097152 bytes)
[1.415409] NET: Registered protocol family 1
[1.415753] PCI: CLS 128 bytes, default 128
[1.415962] Trying to unpack rootfs image as initramfs...
[2.250464] Freeing initrd memory: 21952K (c382 -
c4d9)
Machine Type = Power 8 (S822L)
== Comment: #1 - Thadeu Lima De Souza Cascardo thad...@br.ibm.com -
2014-11-18 13:42:37 ==
What is the firmware version?
Cascardo.
== Comment: #2 - Paulo Flabiano Smorigo pfsmor...@br.ibm.com - 2014-11-19
07:13:35 ==
Currently is FW810.02 (SV810_061). Will update it today.
Smorigo.
== Comment: #3 - Paulo Flabiano Smorigo pfsmor...@br.ibm.com - 2014-11-19
12:47:24 ==
Updated to FW810.20 (SV810_101). Nothing changed.
== Comment: #4 - Greg Kurz kurzg...@fr.ibm.com - 2014-11-20 05:47:45 ==
I reproduce it on a s824 with the FW810.20 (TV810_101) firmware, running
14.04.2 alpha (kernel 3.16.0-25). The issue doesn't show up with kernel
3.13.0-39. I shall try mainline and do some bisect.
== Comment: #5 - Greg Kurz kurzg...@fr.ibm.com - 2014-11-20 13:31:03 ==
FYI issue is upstream.
== Comment: #6 - Breno Henrique Leitao bren...@br.ibm.com - 2014-11-24
11:23:04 ==
(In reply to comment #5)
FYI issue is upstream.
Greg, are you working to solve this issue?
== Comment: #7 - Greg Kurz kurzg...@fr.ibm.com - 2014-11-24 12:08:33 ==
(In reply to comment #6)
(In reply to comment #5)
FYI issue is upstream.
Greg, are you working to solve this issue?
Yes I am.
== Comment: #8 - Greg Kurz kurzg...@fr.ibm.com - 2014-12-01 04:56:07 ==
The hang occurs because all running threads are looping in the split core
code:
static void wait_for_sync_step(int step)
{
int i, cpu = smp_processor_id();
for (i = cpu + 1; i cpu + threads_per_core; i++)
while(per_cpu(split_state, i).step step)
barrier();
The problem is that the split core code needs all possible threads to
participate... if the kernel is booted with smt-enabled set to something
different than the maximum value, some threads are missing and this ruins the
sync.
== Comment: #9 - Greg Kurz kurzg...@fr.ibm.com - 2014-12-01 05:24:28 ==
The current implementaqtion for smt-enabled= is a hack: it simply leaves hw
threads looping where they happen to be (firmware probably)... This isn't
acceptable in a production environment.
An acceptable fix would be to start all threads anyway and offline
the ones that need to be to honour the requested SMT mode AFTER
subcores init. This requires a non-trivial patch.
Since changing SMT mode from userspace when the system is booted is
really straightforward, Michael Ellerman suggests we simply drop that
smt-enabled= feature.
Smorigo,
Why were you using smt-enabled= ? Is there a reason not to do it after the
system is booted with
ppc64_cpu --smt or writing directly to /sys/devices/system/cpu/cpu*/online ?
== Comment: #10 - Paulo Flabiano Smorigo pfsmor...@br.ibm.com - 2014-12-01
06:23:34
[Kernel-packages] [Bug 1407875] Re: [HP 14 Notebook PC][8086:1e20] mute LED does not work
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.19 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as Confirmed. Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19-rc3-vivid/ ** Changed in: linux (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1407875 Title: [HP 14 Notebook PC][8086:1e20] mute LED does not work Status in HWE Next Project: New Status in linux package in Ubuntu: Confirmed Bug description: HP 14 Notebook PC (CID 201404-14936) on 14.04.1 3.13.0-43-generic #72 Audio Controller [8086:1e20] Steps to reproduce this bug: 1. install 14.04.1 on HP 14 Notebook PC (CID 201404-14936) and boot to the desktop. Ready to use Ubuntu 2. press mute key. The playback is muted. Expected result: The mute LED became amber. Actual result: The mute LED has no response. More information: sudo hda-verb /dev/snd/hwC0D0 0x18 SET_PIN_WIDGET_CONTROL 0x24 sudo hda-verb /dev/snd/hwC0D0 0x18 SET_PIN_WIDGET_CONTROL 0x20 could turn on/off the mute LED seperately. - ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-43-generic 3.13.0-43.72 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1521 F pulseaudio CurrentDesktop: Unity Date: Tue Jan 6 14:05:21 2015 HibernationDevice: RESUME=UUID=2121b5cf-c83b-4a11-ae45-a7fcc3a70048 InstallationDate: Installed on 2014-12-18 (18 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP 15 Notebook PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic.efi.signed root=UUID=31c5f412-f969-4705-81f7-2e85fbf53b4d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-43-generic N/A linux-backports-modules-3.13.0-43-generic N/A linux-firmware 1.127.10 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/17/2014 dmi.bios.vendor: Insyde dmi.bios.version: B.34 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 226C dmi.board.vendor: Hewlett-Packard dmi.board.version: 74.20 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrB.34:bd06/17/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr098F11000E100:rvnHewlett-Packard:rn226C:rvr74.20:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP 15 Notebook PC dmi.product.version: 098F11000E100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1407875/+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 1404558] Re: IPv6 related kernel panic following upgrade to 3.13.0-43
** Tags removed: kernel-key ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1404558 Title: IPv6 related kernel panic following upgrade to 3.13.0-43 Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: In Progress Bug description: After updating a dozen machines from 3.13.0-40 to 3.13.0-43, they all kernel panic within the next 24 hours. I managed to pull the console from one over an IP KVM and it shows a panic related to IPv6 networking: https://dl.stgraber.org/panic-3.13-43.png All affected machines had native IPv6 connectivity to the Internet. Downgrading to 3.13.0-40 resolved the issue (so it's clearly a regression) and upgrading to lts-utopic 3.16.0-28-generic also appeared to do the trick. A friend also just reported seeing the exact same problem on his server which also has native IPv6 connectivity so the issue appears pretty widespread. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1404558/+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 1407692] Re: linux: 3.18.0-8.9 -proposed tracker
All builds are complete, packages in this bug are available in -proposed. ** Changed in: kernel-development-workflow/prepare-package-signed Status: New = Fix Released ** Changed in: kernel-development-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) = Leann Ogasawara (leannogasawara) ** Changed in: kernel-development-workflow/package-testing Status: New = Confirmed ** Changed in: kernel-development-workflow/package-testing Status: Confirmed = In Progress ** Changed in: kernel-development-workflow/package-testing Status: In Progress = Confirmed ** Description changed: This bug is for tracking the 3.18.0-8.9 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 kernel-Prepare-package-start:Monday, 05. January 2015 14:24 UTC - kernel-phase-changed:Monday, 05. January 2015 14:24 UTC - kernel-phase:Prepare + kernel-phase-changed:Tuesday, 06. January 2015 19:00 UTC + kernel-Prepare-package-end:Tuesday, 06. January 2015 19:00 UTC + kernel-Package-testing-start:Tuesday, 06. January 2015 19:00 UTC + kernel-phase:PPA Testing + ppa-package-testing-start:Tuesday, 06. January 2015 19:00 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1407692 Title: linux: 3.18.0-8.9 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow package-testing series: Confirmed 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-release series: New Status in linux package in Ubuntu: New Status in linux source package in Vivid: New Bug description: This bug is for tracking the 3.18.0-8.9 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 kernel-Prepare-package-start:Monday, 05. January 2015 14:24 UTC kernel-phase-changed:Tuesday, 06. January 2015 19:00 UTC kernel-Prepare-package-end:Tuesday, 06. January 2015 19:00 UTC kernel-Package-testing-start:Tuesday, 06. January 2015 19:00 UTC kernel-phase:PPA Testing ppa-package-testing-start:Tuesday, 06. January 2015 19:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1407692/+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 1407505] Re: No UMS support in radeon module
I'd like to perform a bisect to figure out what commit caused this regression. We need to identify the earliest kernel where the issue started happening as well as the latest kernel that did not have this issue. Can you test the following kernels and post back? We are looking for the first kernel version that exhibits this bug: v3.16.3: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16.3-utopic/ v3.16.4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16.4-utopic/ v3.16.5: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16.5-utopic/ You don't have to test every kernel, just up until the kernel that first has this bug. Thanks in advance! ** Tags added: performing-bisect -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1407505 Title: No UMS support in radeon module Status in linux package in Ubuntu: Incomplete Bug description: System: Kubuntu (adm64) 14.10. Last update: 4-Jan-2015 No proprietary drivers. No 3rd party software. The last kernel I was able to run on my Utopic system is 3.16.0-17-generic. Every update thereafter failed. The last one I tried is -28. From syslog for -28 kernel: Jan 4 14:22:41 aldebaran kernel: [1.712424] [drm] Initialized drm 1.1.0 20060810 Jan 4 14:22:41 aldebaran kernel: [1.736322] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [1.736375] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 10.340446] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 10.340448] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 101.573768] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 101.573771] [drm:radeon_init] *ERROR* No UMS support in radeon module! From syslog for -17 kernel: Jan 4 14:27:56 aldebaran kernel: [1.676277] [drm] Initialized drm 1.1.0 20060810 Jan 4 14:27:56 aldebaran kernel: [1.698850] [drm] radeon kernel modesetting enabled. Jan 4 14:27:56 aldebaran kernel: [1.698924] fb: switching to radeondrmfb from VESA VGA Jan 4 14:27:56 aldebaran kernel: [1.699341] [drm] initializing kernel modesetting (TURKS 0x1002:0x6758 0x1043:0x03EA). Jan 4 14:27:56 aldebaran kernel: [1.699351] [drm] register mmio base: 0xFDDC Jan 4 14:27:56 aldebaran kernel: [1.699352] [drm]
[Kernel-packages] [Bug 1407505] Re: No UMS support in radeon module
Looks like 3.16.4 is your baby. Thanks for the speed! :-) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1407505 Title: No UMS support in radeon module Status in linux package in Ubuntu: Incomplete Bug description: System: Kubuntu (adm64) 14.10. Last update: 4-Jan-2015 No proprietary drivers. No 3rd party software. The last kernel I was able to run on my Utopic system is 3.16.0-17-generic. Every update thereafter failed. The last one I tried is -28. From syslog for -28 kernel: Jan 4 14:22:41 aldebaran kernel: [1.712424] [drm] Initialized drm 1.1.0 20060810 Jan 4 14:22:41 aldebaran kernel: [1.736322] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [1.736375] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 10.340446] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 10.340448] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 101.573768] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 101.573771] [drm:radeon_init] *ERROR* No UMS support in radeon module! From syslog for -17 kernel: Jan 4 14:27:56 aldebaran kernel: [1.676277] [drm] Initialized drm 1.1.0 20060810 Jan 4 14:27:56 aldebaran kernel: [1.698850] [drm] radeon kernel modesetting enabled. Jan 4 14:27:56 aldebaran kernel: [1.698924] fb: switching to radeondrmfb from VESA VGA Jan 4 14:27:56 aldebaran kernel: [1.699341] [drm] initializing kernel modesetting (TURKS 0x1002:0x6758 0x1043:0x03EA). Jan 4 14:27:56 aldebaran kernel: [1.699351] [drm] register mmio base: 0xFDDC Jan 4 14:27:56 aldebaran kernel: [1.699352] [drm] register mmio size: 131072 Jan 4 14:27:56 aldebaran kernel: [1.699877] [drm] Detected VRAM RAM=1024M, BAR=256M Jan 4 14:27:56 aldebaran kernel: [
[Kernel-packages] [Bug 1400411] Re: Feature: cpuidle: Enable fastsleep and winkle in ubuntu 14.04.02 kernel
** Description changed: + SRU Justification: + Impact: Users would like to be able to use fastsleep and winkle cpuidle states in the 3.16 Ubuntu kernel when using powernv. + Fix: + commits + 56548fc0e86cb9156af7a7e1f15ba78f251dafaf + 8117ac6a6c2fa0f847ff6a21a1f32c8d2c8501d0 + 8eb8ac89a364305d05ad16be983b7890eb462cc3 + 7cba160ad789a3ad7e68b92bf20eaad6ed171f80 + 77b54e9f213f76a23736940cf94bcd765fc00f40 + upstream + Test Case: + cat /sys/devices/system/cpu/cpu0/cpuidle/state*/name + + -- + This is a feature request to enable power management features fastsleep and winkle cpuidle states in ubuntu -14.04.02 kernel. The cpuidle state management patches have been posted to Linux Kernel Community. Mailing list: [PATCH 0/4] powernv: cpuidle: Redesign idle states management https://lists.ozlabs.org/pipermail/linuxppc-dev/2014-November/122433.html Patchset: [1/4] powerpc: powernv: Switch off MMU before entering nap/sleep/rvwinkle mode https://patchwork.ozlabs.org/patch/406249/ [2/4] powerpc/powernv: Enable Offline CPUs to enter deep idle states https://patchwork.ozlabs.org/patch/406250/ [3/4] powernv: cpuidle: Redesign idle states management https://patchwork.ozlabs.org/patch/406256/ [4/4] powernv: powerpc: Add winkle support for offline cpus https://patchwork.ozlabs.org/patch/406251/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1400411 Title: Feature: cpuidle: Enable fastsleep and winkle in ubuntu 14.04.02 kernel Status in linux package in Ubuntu: New Status in linux source package in Utopic: In Progress Bug description: SRU Justification: Impact: Users would like to be able to use fastsleep and winkle cpuidle states in the 3.16 Ubuntu kernel when using powernv. Fix: commits 56548fc0e86cb9156af7a7e1f15ba78f251dafaf 8117ac6a6c2fa0f847ff6a21a1f32c8d2c8501d0 8eb8ac89a364305d05ad16be983b7890eb462cc3 7cba160ad789a3ad7e68b92bf20eaad6ed171f80 77b54e9f213f76a23736940cf94bcd765fc00f40 upstream Test Case: cat /sys/devices/system/cpu/cpu0/cpuidle/state*/name -- This is a feature request to enable power management features fastsleep and winkle cpuidle states in ubuntu -14.04.02 kernel. The cpuidle state management patches have been posted to Linux Kernel Community. Mailing list: [PATCH 0/4] powernv: cpuidle: Redesign idle states management https://lists.ozlabs.org/pipermail/linuxppc-dev/2014-November/122433.html Patchset: [1/4] powerpc: powernv: Switch off MMU before entering nap/sleep/rvwinkle mode https://patchwork.ozlabs.org/patch/406249/ [2/4] powerpc/powernv: Enable Offline CPUs to enter deep idle states https://patchwork.ozlabs.org/patch/406250/ [3/4] powernv: cpuidle: Redesign idle states management https://patchwork.ozlabs.org/patch/406256/ [4/4] powernv: powerpc: Add winkle support for offline cpus https://patchwork.ozlabs.org/patch/406251/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1400411/+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 1402141] Re: Ubuntu 14.10 freezes when use smt-enabled=off as kernel argument
** Description changed:
SRU Justification:
- Impact: Booting a POWER8 machine with smt-enabled=off will cause a system to
hang at Freeing initrd memory
+ Impact: Booting a POWER8 machine with smt-enabled=off will cause a system to
hang at Freeing initrd memory, note is only affects kernel with powernv
split-core support.
Fix: commit d70a54e2d08510a99b1f10eceeae6f2f7086e226 upstream
Testcase: Boot with smt-enabled=off on a POWER8 machine
--
== Comment: #0 - Paulo Flabiano Smorigo pfsmor...@br.ibm.com - 2014-11-18
12:28:42 ==
Using Ubuntu as the host, if you add smt-enabled=off as kernel argument, the
system will boot until the Freeing initrd memory line:
...
[1.371729] vgaarb: loaded
[1.372989] SCSI subsystem initialized
[1.373977] libata version 3.00 loaded.
[1.374158] usbcore: registered new interface driver usbfs
[1.374246] usbcore: registered new interface driver hub
[1.374382] usbcore: registered new device driver usb
[1.374505] pps_core: LinuxPPS API ver. 1 registered
[1.374563] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo
Giometti giome...@linux.it
[1.374671] PTP clock support registered
[1.377135] NetLabel: Initializing
[1.377218] NetLabel: domain hash size = 128
[1.377328] NetLabel: protocols = UNLABELED CIPSOv4
[1.377472] NetLabel: unlabeled traffic allowed by default
[1.377983] Switched to clocksource timebase
[1.395029] AppArmor: AppArmor Filesystem Enabled
[1.402044] NET: Registered protocol family 2
[1.403795] TCP established hash table entries: 524288 (order: 6, 4194304
bytes)
[1.408343] TCP bind hash table entries: 65536 (order: 4, 1048576 bytes)
[1.409301] TCP: Hash tables configured (established 524288 bind 65536)
[1.409490] TCP: reno registered
[1.409645] UDP hash table entries: 65536 (order: 5, 2097152 bytes)
[1.411943] UDP-Lite hash table entries: 65536 (order: 5, 2097152 bytes)
[1.415409] NET: Registered protocol family 1
[1.415753] PCI: CLS 128 bytes, default 128
[1.415962] Trying to unpack rootfs image as initramfs...
[2.250464] Freeing initrd memory: 21952K (c382 -
c4d9)
Machine Type = Power 8 (S822L)
== Comment: #1 - Thadeu Lima De Souza Cascardo thad...@br.ibm.com -
2014-11-18 13:42:37 ==
What is the firmware version?
Cascardo.
== Comment: #2 - Paulo Flabiano Smorigo pfsmor...@br.ibm.com - 2014-11-19
07:13:35 ==
Currently is FW810.02 (SV810_061). Will update it today.
Smorigo.
== Comment: #3 - Paulo Flabiano Smorigo pfsmor...@br.ibm.com - 2014-11-19
12:47:24 ==
Updated to FW810.20 (SV810_101). Nothing changed.
== Comment: #4 - Greg Kurz kurzg...@fr.ibm.com - 2014-11-20 05:47:45 ==
I reproduce it on a s824 with the FW810.20 (TV810_101) firmware, running
14.04.2 alpha (kernel 3.16.0-25). The issue doesn't show up with kernel
3.13.0-39. I shall try mainline and do some bisect.
== Comment: #5 - Greg Kurz kurzg...@fr.ibm.com - 2014-11-20 13:31:03 ==
FYI issue is upstream.
== Comment: #6 - Breno Henrique Leitao bren...@br.ibm.com - 2014-11-24
11:23:04 ==
(In reply to comment #5)
FYI issue is upstream.
Greg, are you working to solve this issue?
== Comment: #7 - Greg Kurz kurzg...@fr.ibm.com - 2014-11-24 12:08:33 ==
(In reply to comment #6)
(In reply to comment #5)
FYI issue is upstream.
Greg, are you working to solve this issue?
Yes I am.
== Comment: #8 - Greg Kurz kurzg...@fr.ibm.com - 2014-12-01 04:56:07 ==
The hang occurs because all running threads are looping in the split core
code:
static void wait_for_sync_step(int step)
{
int i, cpu = smp_processor_id();
for (i = cpu + 1; i cpu + threads_per_core; i++)
while(per_cpu(split_state, i).step step)
barrier();
The problem is that the split core code needs all possible threads to
participate... if the kernel is booted with smt-enabled set to something
different than the maximum value, some threads are missing and this
ruins the sync.
== Comment: #9 - Greg Kurz kurzg...@fr.ibm.com - 2014-12-01 05:24:28 ==
The current implementaqtion for smt-enabled= is a hack: it simply leaves hw
threads looping where they happen to be (firmware probably)... This isn't
acceptable in a production environment.
An acceptable fix would be to start all threads anyway and offline the
ones that need to be to honour the requested SMT mode AFTER subcores
init. This requires a non-trivial patch.
Since changing SMT mode from userspace when the system is booted is
really straightforward, Michael Ellerman suggests we simply drop that
smt-enabled= feature.
Smorigo,
Why were you using smt-enabled= ? Is there a reason not to do it after the
system is booted with
ppc64_cpu --smt or writing directly to /sys/devices/system/cpu/cpu*/online ?
[Kernel-packages] [Bug 1402141] Re: Ubuntu 14.10 freezes when use smt-enabled=off as kernel argument
** Changed in: linux (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1402141
Title:
Ubuntu 14.10 freezes when use smt-enabled=off as kernel argument
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Utopic:
In Progress
Bug description:
SRU Justification:
Impact: Booting a POWER8 machine with smt-enabled=off will cause a system to
hang at Freeing initrd memory, note is only affects kernel with powernv
split-core support.
Fix: commit d70a54e2d08510a99b1f10eceeae6f2f7086e226 upstream
Testcase: Boot with smt-enabled=off on a POWER8 machine
--
== Comment: #0 - Paulo Flabiano Smorigo pfsmor...@br.ibm.com - 2014-11-18
12:28:42 ==
Using Ubuntu as the host, if you add smt-enabled=off as kernel argument, the
system will boot until the Freeing initrd memory line:
...
[1.371729] vgaarb: loaded
[1.372989] SCSI subsystem initialized
[1.373977] libata version 3.00 loaded.
[1.374158] usbcore: registered new interface driver usbfs
[1.374246] usbcore: registered new interface driver hub
[1.374382] usbcore: registered new device driver usb
[1.374505] pps_core: LinuxPPS API ver. 1 registered
[1.374563] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo
Giometti giome...@linux.it
[1.374671] PTP clock support registered
[1.377135] NetLabel: Initializing
[1.377218] NetLabel: domain hash size = 128
[1.377328] NetLabel: protocols = UNLABELED CIPSOv4
[1.377472] NetLabel: unlabeled traffic allowed by default
[1.377983] Switched to clocksource timebase
[1.395029] AppArmor: AppArmor Filesystem Enabled
[1.402044] NET: Registered protocol family 2
[1.403795] TCP established hash table entries: 524288 (order: 6, 4194304
bytes)
[1.408343] TCP bind hash table entries: 65536 (order: 4, 1048576 bytes)
[1.409301] TCP: Hash tables configured (established 524288 bind 65536)
[1.409490] TCP: reno registered
[1.409645] UDP hash table entries: 65536 (order: 5, 2097152 bytes)
[1.411943] UDP-Lite hash table entries: 65536 (order: 5, 2097152 bytes)
[1.415409] NET: Registered protocol family 1
[1.415753] PCI: CLS 128 bytes, default 128
[1.415962] Trying to unpack rootfs image as initramfs...
[2.250464] Freeing initrd memory: 21952K (c382 -
c4d9)
Machine Type = Power 8 (S822L)
== Comment: #1 - Thadeu Lima De Souza Cascardo thad...@br.ibm.com -
2014-11-18 13:42:37 ==
What is the firmware version?
Cascardo.
== Comment: #2 - Paulo Flabiano Smorigo pfsmor...@br.ibm.com - 2014-11-19
07:13:35 ==
Currently is FW810.02 (SV810_061). Will update it today.
Smorigo.
== Comment: #3 - Paulo Flabiano Smorigo pfsmor...@br.ibm.com - 2014-11-19
12:47:24 ==
Updated to FW810.20 (SV810_101). Nothing changed.
== Comment: #4 - Greg Kurz kurzg...@fr.ibm.com - 2014-11-20 05:47:45 ==
I reproduce it on a s824 with the FW810.20 (TV810_101) firmware, running
14.04.2 alpha (kernel 3.16.0-25). The issue doesn't show up with kernel
3.13.0-39. I shall try mainline and do some bisect.
== Comment: #5 - Greg Kurz kurzg...@fr.ibm.com - 2014-11-20 13:31:03 ==
FYI issue is upstream.
== Comment: #6 - Breno Henrique Leitao bren...@br.ibm.com - 2014-11-24
11:23:04 ==
(In reply to comment #5)
FYI issue is upstream.
Greg, are you working to solve this issue?
== Comment: #7 - Greg Kurz kurzg...@fr.ibm.com - 2014-11-24 12:08:33 ==
(In reply to comment #6)
(In reply to comment #5)
FYI issue is upstream.
Greg, are you working to solve this issue?
Yes I am.
== Comment: #8 - Greg Kurz kurzg...@fr.ibm.com - 2014-12-01 04:56:07 ==
The hang occurs because all running threads are looping in the split core
code:
static void wait_for_sync_step(int step)
{
int i, cpu = smp_processor_id();
for (i = cpu + 1; i cpu + threads_per_core; i++)
while(per_cpu(split_state, i).step step)
barrier();
The problem is that the split core code needs all possible threads to
participate... if the kernel is booted with smt-enabled set to
something different than the maximum value, some threads are missing
and this ruins the sync.
== Comment: #9 - Greg Kurz kurzg...@fr.ibm.com - 2014-12-01 05:24:28 ==
The current implementaqtion for smt-enabled= is a hack: it simply leaves hw
threads looping where they happen to be (firmware probably)... This isn't
acceptable in a production environment.
An acceptable fix would be to start all threads anyway and offline
the ones that need to be to honour the requested SMT mode AFTER
subcores init. This requires a non-trivial patch.
Since changing SMT mode from userspace when the system is booted is
really straightforward, Michael
[Kernel-packages] [Bug 1400411] Re: Feature: cpuidle: Enable fastsleep and winkle in ubuntu 14.04.02 kernel
All commits are present in 3.19-rc1 ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Utopic) Assignee: (unassigned) = Chris J Arges (arges) ** Changed in: linux (Ubuntu Utopic) Importance: Undecided = Medium ** Changed in: linux (Ubuntu Utopic) Status: New = In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1400411 Title: Feature: cpuidle: Enable fastsleep and winkle in ubuntu 14.04.02 kernel Status in linux package in Ubuntu: New Status in linux source package in Utopic: In Progress Bug description: SRU Justification: Impact: Users would like to be able to use fastsleep and winkle cpuidle states in the 3.16 Ubuntu kernel when using powernv. Fix: commits 56548fc0e86cb9156af7a7e1f15ba78f251dafaf 8117ac6a6c2fa0f847ff6a21a1f32c8d2c8501d0 8eb8ac89a364305d05ad16be983b7890eb462cc3 7cba160ad789a3ad7e68b92bf20eaad6ed171f80 77b54e9f213f76a23736940cf94bcd765fc00f40 upstream Test Case: cat /sys/devices/system/cpu/cpu0/cpuidle/state*/name -- This is a feature request to enable power management features fastsleep and winkle cpuidle states in ubuntu -14.04.02 kernel. The cpuidle state management patches have been posted to Linux Kernel Community. Mailing list: [PATCH 0/4] powernv: cpuidle: Redesign idle states management https://lists.ozlabs.org/pipermail/linuxppc-dev/2014-November/122433.html Patchset: [1/4] powerpc: powernv: Switch off MMU before entering nap/sleep/rvwinkle mode https://patchwork.ozlabs.org/patch/406249/ [2/4] powerpc/powernv: Enable Offline CPUs to enter deep idle states https://patchwork.ozlabs.org/patch/406250/ [3/4] powernv: cpuidle: Redesign idle states management https://patchwork.ozlabs.org/patch/406256/ [4/4] powernv: powerpc: Add winkle support for offline cpus https://patchwork.ozlabs.org/patch/406251/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1400411/+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 1402141] Comment bridged from LTC Bugzilla
--- Comment From kurzg...@fr.ibm.com 2015-01-06 18:39 EDT---
(In reply to comment #20)
We should also check if this affects 3.13.
It doesn't because powernv split-core isn't available in 3.13.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1402141
Title:
Ubuntu 14.10 freezes when use smt-enabled=off as kernel argument
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Utopic:
In Progress
Bug description:
SRU Justification:
Impact: Booting a POWER8 machine with smt-enabled=off will cause a system to
hang at Freeing initrd memory
Fix: commit d70a54e2d08510a99b1f10eceeae6f2f7086e226 upstream
Testcase: Boot with smt-enabled=off on a POWER8 machine
--
== Comment: #0 - Paulo Flabiano Smorigo pfsmor...@br.ibm.com - 2014-11-18
12:28:42 ==
Using Ubuntu as the host, if you add smt-enabled=off as kernel argument, the
system will boot until the Freeing initrd memory line:
...
[1.371729] vgaarb: loaded
[1.372989] SCSI subsystem initialized
[1.373977] libata version 3.00 loaded.
[1.374158] usbcore: registered new interface driver usbfs
[1.374246] usbcore: registered new interface driver hub
[1.374382] usbcore: registered new device driver usb
[1.374505] pps_core: LinuxPPS API ver. 1 registered
[1.374563] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo
Giometti giome...@linux.it
[1.374671] PTP clock support registered
[1.377135] NetLabel: Initializing
[1.377218] NetLabel: domain hash size = 128
[1.377328] NetLabel: protocols = UNLABELED CIPSOv4
[1.377472] NetLabel: unlabeled traffic allowed by default
[1.377983] Switched to clocksource timebase
[1.395029] AppArmor: AppArmor Filesystem Enabled
[1.402044] NET: Registered protocol family 2
[1.403795] TCP established hash table entries: 524288 (order: 6, 4194304
bytes)
[1.408343] TCP bind hash table entries: 65536 (order: 4, 1048576 bytes)
[1.409301] TCP: Hash tables configured (established 524288 bind 65536)
[1.409490] TCP: reno registered
[1.409645] UDP hash table entries: 65536 (order: 5, 2097152 bytes)
[1.411943] UDP-Lite hash table entries: 65536 (order: 5, 2097152 bytes)
[1.415409] NET: Registered protocol family 1
[1.415753] PCI: CLS 128 bytes, default 128
[1.415962] Trying to unpack rootfs image as initramfs...
[2.250464] Freeing initrd memory: 21952K (c382 -
c4d9)
Machine Type = Power 8 (S822L)
== Comment: #1 - Thadeu Lima De Souza Cascardo thad...@br.ibm.com -
2014-11-18 13:42:37 ==
What is the firmware version?
Cascardo.
== Comment: #2 - Paulo Flabiano Smorigo pfsmor...@br.ibm.com - 2014-11-19
07:13:35 ==
Currently is FW810.02 (SV810_061). Will update it today.
Smorigo.
== Comment: #3 - Paulo Flabiano Smorigo pfsmor...@br.ibm.com - 2014-11-19
12:47:24 ==
Updated to FW810.20 (SV810_101). Nothing changed.
== Comment: #4 - Greg Kurz kurzg...@fr.ibm.com - 2014-11-20 05:47:45 ==
I reproduce it on a s824 with the FW810.20 (TV810_101) firmware, running
14.04.2 alpha (kernel 3.16.0-25). The issue doesn't show up with kernel
3.13.0-39. I shall try mainline and do some bisect.
== Comment: #5 - Greg Kurz kurzg...@fr.ibm.com - 2014-11-20 13:31:03 ==
FYI issue is upstream.
== Comment: #6 - Breno Henrique Leitao bren...@br.ibm.com - 2014-11-24
11:23:04 ==
(In reply to comment #5)
FYI issue is upstream.
Greg, are you working to solve this issue?
== Comment: #7 - Greg Kurz kurzg...@fr.ibm.com - 2014-11-24 12:08:33 ==
(In reply to comment #6)
(In reply to comment #5)
FYI issue is upstream.
Greg, are you working to solve this issue?
Yes I am.
== Comment: #8 - Greg Kurz kurzg...@fr.ibm.com - 2014-12-01 04:56:07 ==
The hang occurs because all running threads are looping in the split core
code:
static void wait_for_sync_step(int step)
{
int i, cpu = smp_processor_id();
for (i = cpu + 1; i cpu + threads_per_core; i++)
while(per_cpu(split_state, i).step step)
barrier();
The problem is that the split core code needs all possible threads to
participate... if the kernel is booted with smt-enabled set to
something different than the maximum value, some threads are missing
and this ruins the sync.
== Comment: #9 - Greg Kurz kurzg...@fr.ibm.com - 2014-12-01 05:24:28 ==
The current implementaqtion for smt-enabled= is a hack: it simply leaves hw
threads looping where they happen to be (firmware probably)... This isn't
acceptable in a production environment.
An acceptable fix would be to start all threads anyway and offline
the ones that need to be to honour the requested SMT mode AFTER
subcores init. This requires a non-trivial patch.
Since changing SMT mode from userspace
[Kernel-packages] [Bug 1408025] Re: Lenovo Thinkpad Edge E540 suspend/resume failure
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.19 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as Confirmed. Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19-rc3-vivid/ ** Changed in: linux (Ubuntu) Importance: Undecided = Low ** Changed in: linux (Ubuntu) Status: Confirmed = 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/1408025 Title: Lenovo Thinkpad Edge E540 suspend/resume failure Status in linux package in Ubuntu: Incomplete Bug description: After an update of the Thinkpad Edge E540 BIOS to version v2.16 (J9ET96WW ) the suspend to RAM failes: - general ThinkPad LED (the i's dot) behaved like normal: slowly blinking, which normally means I'm suspended to RAM. - resume was impossible: wakeup failed through mouse clicks, various keyboard keys and combinations and also the power key, only a hard reset (5s or so holding down the power key) could bring it back to life Ubuntu 14.04.1 LTS Linux Lenovo-E540 3.13.0-43-generic #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-43-generic 3.13.0-43.72 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1501 F pulseaudio /dev/snd/controlC1: peter 1501 F pulseaudio CurrentDesktop: Unity Date: Tue Jan 6 17:21:03 2015 HibernationDevice: RESUME=UUID=9141fa35-dc66-4dcc-8a9f-c3b13be1bded InstallationDate: Installed on 2014-04-18 (262 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: LENOVO 20C60043GE ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic.efi.signed root=UUID=c79d162d-01c6-4fda-ba6b-a5884fc5f16d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-43-generic N/A linux-backports-modules-3.13.0-43-generic N/A linux-firmware 1.127.10 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/14/2014 dmi.bios.vendor: LENOVO dmi.bios.version: J9ET96WW (2.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20C60043GE dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrJ9ET96WW(2.16):bd10/14/2014:svnLENOVO:pn20C60043GE:pvrThinkPadEdgeE540:rvnLENOVO:rn20C60043GE:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20C60043GE dmi.product.version: ThinkPad Edge E540 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408025/+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 1404558] Re: IPv6 related kernel panic following upgrade to 3.13.0-43
** Changed in: linux (Ubuntu Trusty) Status: New = In Progress ** Changed in: linux (Ubuntu Trusty) Importance: Undecided = Critical ** Changed in: linux (Ubuntu Trusty) Assignee: (unassigned) = Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1404558 Title: IPv6 related kernel panic following upgrade to 3.13.0-43 Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: In Progress Bug description: After updating a dozen machines from 3.13.0-40 to 3.13.0-43, they all kernel panic within the next 24 hours. I managed to pull the console from one over an IP KVM and it shows a panic related to IPv6 networking: https://dl.stgraber.org/panic-3.13-43.png All affected machines had native IPv6 connectivity to the Internet. Downgrading to 3.13.0-40 resolved the issue (so it's clearly a regression) and upgrading to lts-utopic 3.16.0-28-generic also appeared to do the trick. A friend also just reported seeing the exact same problem on his server which also has native IPv6 connectivity so the issue appears pretty widespread. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1404558/+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 1283938] Re: [Samsung NP535U4X-S01TH] Ubuntu 14.04 blank screen after wakeup from sleep
This is just so annoying! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1283938 Title: [Samsung NP535U4X-S01TH] Ubuntu 14.04 blank screen after wakeup from sleep Status in The Linux Kernel: Unknown Status in linux package in Ubuntu: Incomplete Bug description: HOW TO REPRODUCE 1. Suspend the device 2. Wake it up EXPECTED BEHAVIOUR - The device to resume normally REAL BEHAVIOUR - The screen goes blank RELEVANT DETAILS - In the /etc/default/grub file; changing quiet splash option to nomodeset allows the wakeup, but the computer gets so slow it is unusable. WORKAROUND: Install fglrx. Unverified WORKAROUND: Revert commit 6c7bccea390853bdec5b76fe31fc50f3b36f75d5 as per https://bugzilla.kernel.org/show_bug.cgi?id=76761#c3 . ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-ati 1:7.3.0-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 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: Mon Feb 24 12:58:07 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.6, 3.13.0-11-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7500G] [1002:990a] (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c660] Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7550M/7570M/7650M] [1002:6841] (rev ff) (prog-if ff) InstallationDate: Installed on 2014-02-22 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140218) MachineType: SAMSUNG ELECTRONICS CO., LTD. 535U4C ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic root=UUID=9f8c7e92-a6ea-41fd-9489-a256c8b9f5d5 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P06RAF.N93.130403.LEO dmi.board.asset.tag: No Asset Tag dmi.board.name: NP535U4X-S01TH dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SEC_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP06RAF.N93.130403.LEO:bd04/03/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn535U4C:pvrP06RAF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP535U4X-S01TH:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 535U4C dmi.product.version: P06RAF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Feb 24 12:54:54 2014 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.0-1ubuntu6 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1283938/+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 1407522] Re: bcmwl package was sugested by KDE driver manager but broke the system
Christopher, I did not remember what I've done with 12.04/10 , so I made a kubuntu usb stick with 12.04.5 and run in on the laptop. Problem is the same (3.2.0-7-generic x86, with bcmwl 6.20.155.1+bdcom-0ubuntu0.0.2 ), so for sure it happened before precise(12.04) . What is more, looking at the syslog I remind myself what I've done to make my wifi working then - to simplify - installed proper b43 driver At that time kde device manager did not pop up with sugestion so I did my driver choise by syslog warning suggestions for b43. Not only did b43 not conflict with b44( the LAN driver) but it serve me for a long time ;). When it comes to broadcom-sta, good guide for me was https://help.ubuntu.com/community/BroadcomSTA%28Wireless%29 where is said that my card [14e4:4311] works with b43 but not with broadcom-sta, so after installing I do not get an offer for the card to use the driver. Should I report the bug on http://www.broadcom.com/support/802.11/linux_sta.php directly ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1407522 Title: bcmwl package was sugested by KDE driver manager but broke the system Status in bcmwl package in Ubuntu: Incomplete Bug description: On fresh 14.10 install on the first GUI run in KDE the KDE Driver Manager suggested installation of bcmwl-kernel-source (see attached screenshot)for my Broadcom Corporation BCM4311. After successful installation of the package and restart, my system got Jan 4 23:32:13 Beatles kernel: [ 19.485177] wl driver 6.30.223.248 (r487574) failed with code 21 Jan 4 23:32:13 Beatles kernel: [ 19.485208] [ cut here ] Jan 4 23:32:13 Beatles kernel: [ 19.485242] kernel BUG at include/net/cfg80211.h:3343! full description of the message in attached file (syslog_extracted.log). For some reason this also affects the driver for my NIC and my laptop got out of any possible network connection. So instead of configuring the wireless card it left me with only lo interface :(. I would expect properly configured modules for WAN and LAN Luckily apt-get remove --purge bcmwl-kernel-source restores the previous state so I can submit this bug via LAN. Now I'm running Ubuntu 14.10 but the same happened half an year ago when I tried to install 14.04 on this laptop. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: bcmwl-kernel-source (not installed) ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jan 5 01:00:26 2015 SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1407522/+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 1381084] Re: xgene-enet: add 10GbE support
** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1381084 Title: xgene-enet: add 10GbE support Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Utopic: Fix Released Bug description: [Impact] APM's Mustang boards have a 10GbE interface that is currently unsupported by Ubuntu. [Test Case] Verify that the previously non-working 10GbE interface now works. [Regression Risk] Since the changes touch the driver that supports the existing GbE support, it is possible that that support has become impacted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1381084/+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 1407505] Re: No UMS support in radeon module
** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Vivid) Importance: Medium Status: Incomplete ** Changed in: linux (Ubuntu Utopic) Status: New = Confirmed ** Changed in: linux (Ubuntu Vivid) Status: Incomplete = Confirmed ** Changed in: linux (Ubuntu Utopic) Importance: Undecided = Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1407505 Title: No UMS support in radeon module Status in linux package in Ubuntu: Confirmed Status in linux source package in Utopic: Confirmed Status in linux source package in Vivid: Confirmed Bug description: System: Kubuntu (adm64) 14.10. Last update: 4-Jan-2015 No proprietary drivers. No 3rd party software. The last kernel I was able to run on my Utopic system is 3.16.0-17-generic. Every update thereafter failed. The last one I tried is -28. From syslog for -28 kernel: Jan 4 14:22:41 aldebaran kernel: [1.712424] [drm] Initialized drm 1.1.0 20060810 Jan 4 14:22:41 aldebaran kernel: [1.736322] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [1.736375] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 10.340446] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 10.340448] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 101.573768] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 101.573771] [drm:radeon_init] *ERROR* No UMS support in radeon module! From syslog for -17 kernel: Jan 4 14:27:56 aldebaran kernel: [1.676277] [drm] Initialized drm 1.1.0 20060810 Jan 4 14:27:56 aldebaran kernel: [1.698850] [drm] radeon kernel modesetting enabled. Jan 4 14:27:56 aldebaran kernel: [1.698924] fb: switching to radeondrmfb from VESA VGA Jan 4 14:27:56 aldebaran kernel: [1.699341] [drm] initializing kernel modesetting (TURKS 0x1002:0x6758 0x1043:0x03EA). Jan 4 14:27:56 aldebaran kernel: [1.699351] [drm] register mmio base: 0xFDDC Jan 4 14:27:56 aldebaran kernel: [1.699352] [drm] register mmio size: 131072
[Kernel-packages] [Bug 1408105] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run: apport-collect 1408105 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/1408105 Title: Haswell-based Chromebook touchpads and touchscreen are not enabled Status in linux package in Ubuntu: Incomplete Bug description: SRU Justification: Impact: The Haswell-based Chromebooks have touchpads and a touchscreen unsupported in the 3.16 kernels Fix: Upstream in 3.17 Testcase: I've tested fixes by compiling and using upstream 3.17+ da3b0ab75aadab63d1ffd5563100c9386e444dad Acer C720 5ea9567f6126846f5dcfa8515d7ef2c238133c0d HP Chromebook 14 0e1e5e590a457063c94d55c219b349bcf0d1f93a Dell Chromebook 11 963cb6fa0f5f115986e970b9d97440e4906524fa Toshiba CB35 b90b3c4ae06af135e279c9a5aa1c640d22787fc4 Acer C720P To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408105/+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 1408105] Re: Haswell-based Chromebook touchpads and touchscreen are not enabled
** Description changed: - The Haswell-based Chromebooks have touchpads and a touchscreen - unsupported in the 3.16 kernels. Will you please add the linux 3.17 - patches to enable these devices? They have been widely tested by those - who install stock linux on these Chromebooks. + SRU Justification: + + Impact: The Haswell-based Chromebooks have touchpads and a touchscreen unsupported in the 3.16 kernels + Fix: Upstream in 3.17 + Testcase: I've tested fixes by compiling and using upstream 3.17+ da3b0ab75aadab63d1ffd5563100c9386e444dad Acer C720 5ea9567f6126846f5dcfa8515d7ef2c238133c0d HP Chromebook 14 0e1e5e590a457063c94d55c219b349bcf0d1f93a Dell Chromebook 11 963cb6fa0f5f115986e970b9d97440e4906524fa Toshiba CB35 b90b3c4ae06af135e279c9a5aa1c640d22787fc4 Acer C720P -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1408105 Title: Haswell-based Chromebook touchpads and touchscreen are not enabled Status in linux package in Ubuntu: Incomplete Bug description: SRU Justification: Impact: The Haswell-based Chromebooks have touchpads and a touchscreen unsupported in the 3.16 kernels Fix: Upstream in 3.17 Testcase: I've tested fixes by compiling and using upstream 3.17+ da3b0ab75aadab63d1ffd5563100c9386e444dad Acer C720 5ea9567f6126846f5dcfa8515d7ef2c238133c0d HP Chromebook 14 0e1e5e590a457063c94d55c219b349bcf0d1f93a Dell Chromebook 11 963cb6fa0f5f115986e970b9d97440e4906524fa Toshiba CB35 b90b3c4ae06af135e279c9a5aa1c640d22787fc4 Acer C720P To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408105/+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 1408106] [NEW] allow defining the attach root for attach_disconnected
Public bug reported:
With the following use of overlayfs, we get a disconnected path:
$ cat ./profile
#include tunables/global
profile foo {
#include abstractions/base
capability sys_admin,
capability sys_chroot,
mount,
pivot_root,
}
$ cat ./overlay.c
#include alloca.h
#include linux/sched.h
#include stdio.h
#include string.h
#include sys/mount.h
#include fcntl.h
#include unistd.h
int main(int argc, char* argv[]) {
int i = 0;
int len = 0;
int ret = 0;
char* options;
if (geteuid())
unshare(CLONE_NEWUSER);
unshare(CLONE_NEWNS);
for (i = 1; i argc; i++) {
if (i == 1) {
len = strlen(argv[i]) + strlen(upperdir=,lowerdir=/) + 2;
options = alloca(len);
ret = snprintf(options, len, upperdir=%s,lowerdir=/, argv[i]);
}
else {
len = strlen(argv[i]) + strlen(upperdir=,lowerdir=/mnt) + 2;
options = alloca(len);
ret = snprintf(options, len, upperdir=%s,lowerdir=/mnt, argv[i]);
}
mount(overlayfs, /mnt, overlayfs, MS_MGC_VAL, options);
}
chdir(/mnt);
pivot_root(., .);
chroot(.);
chdir(/);
execl(/bin/bash, /bin/bash, NULL);
}
$ sudo apparmor_parser -r ./profile aa-exec -p foo -- ./a.out /tmp
[255]
...
Dec 12 14:31:38 localhost kernel: [57278.040216] audit: type=1400
audit(1418387498.613:712): apparmor=DENIED operation=exec info=Failed name
lookup - disconnected path error=-13 profile=foo name=/bin/bash pid=18255
comm=a.out requested_mask=x denied_mask=x fsuid=1000 ouid=0
With the above, the expectation was for the denial to be /mnt/bin/bash. There
are three ways forward:
1. the correct solution is to patch overlayfs to properly track the loopback,
but this will take a while, may ultimately be unachievable (investigation is
needed) and is likely non-upstreamable
2. we could rely on the fact that overlayfs creates a private unshared
submount, and provide a way to not mediate the path when that is present, and
tagged. This would take a bit of time, and might be the preferred method over 1
longer term
3. we could extend attach_disconnected so that we can define the attach root.
Eg, we can use profile foo (attach_disconnected=/mnt) {} such that '/bin/bash'
maps to '/mnt/bin/bash'.
While attach_disconnected should in general be discouraged, this method:
* is doable in a short time frame,
* is generally useful even when the proper fix is in place
* would help lxc in a few cases
* would be sufficient for snappy
** Affects: apparmor
Importance: Critical
Assignee: John Johansen (jjohansen)
Status: In Progress
** Affects: apparmor (Ubuntu)
Importance: Critical
Assignee: Steve Beattie (sbeattie)
Status: Confirmed
** Affects: linux (Ubuntu)
Importance: Critical
Assignee: John Johansen (jjohansen)
Status: Confirmed
** Tags: aa-kernel aa-parser aa-tools
** Description changed:
With the following use of overlayfs, we get a disconnected path:
- $ cat ./profile
+ $ cat ./profile
#include tunables/global
profile foo {
- #include abstractions/base
+ #include abstractions/base
- capability sys_admin,
- capability sys_chroot,
- mount,
- pivot_root,
+ capability sys_admin,
+ capability sys_chroot,
+ mount,
+ pivot_root,
}
-
- $ cat ./overlay.c
+ $ cat ./overlay.c
#include alloca.h
#include linux/sched.h
#include stdio.h
#include string.h
#include sys/mount.h
#include fcntl.h
#include unistd.h
int main(int argc, char* argv[]) {
- int i = 0;
- int len = 0;
- int ret = 0;
- char* options;
+ int i = 0;
+ int len = 0;
+ int ret = 0;
+ char* options;
- if (geteuid())
- unshare(CLONE_NEWUSER);
- unshare(CLONE_NEWNS);
+ if (geteuid())
+ unshare(CLONE_NEWUSER);
+ unshare(CLONE_NEWNS);
- for (i = 1; i argc; i++) {
- if (i == 1) {
- len = strlen(argv[i]) + strlen(upperdir=,lowerdir=/) + 2;
- options = alloca(len);
- ret = snprintf(options, len, upperdir=%s,lowerdir=/, argv[i]);
- }
- else {
- len = strlen(argv[i]) + strlen(upperdir=,lowerdir=/mnt) + 2;
- options = alloca(len);
- ret = snprintf(options, len, upperdir=%s,lowerdir=/mnt,
argv[i]);
- }
+ for (i = 1; i argc; i++) {
+ if (i == 1) {
+ len = strlen(argv[i]) + strlen(upperdir=,lowerdir=/) + 2;
+ options = alloca(len);
+ ret = snprintf(options, len, upperdir=%s,lowerdir=/, argv[i]);
+ }
+ else {
+ len = strlen(argv[i]) + strlen(upperdir=,lowerdir=/mnt) + 2;
+ options = alloca(len);
+ ret = snprintf(options, len, upperdir=%s,lowerdir=/mnt,
argv[i]);
+ }
- mount(overlayfs, /mnt, overlayfs, MS_MGC_VAL, options);
- }
+ mount(overlayfs, /mnt, overlayfs, MS_MGC_VAL,
[Kernel-packages] [Bug 1335478] Re: A new instance of IBM Domino 'bindsock' cannot bind to ports 1024 Kernel 3.13.0-29 and above
Ok, the PMR with IBM went about as expected. Unfortunately our level 3 support team will not pursue this issue seeing how it is not seen on current supported platforms of Unix. So much for bindsock itself getting fixed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1335478 Title: A new instance of IBM Domino 'bindsock' cannot bind to ports 1024 Kernel 3.13.0-29 and above Status in linux package in Ubuntu: Fix Committed Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux source package in Lucid: Fix Committed Status in linux-lts-trusty source package in Lucid: Invalid Status in linux-lts-utopic source package in Lucid: Invalid Status in linux source package in Precise: Fix Committed Status in linux-lts-trusty source package in Precise: Fix Committed Status in linux-lts-utopic source package in Precise: Invalid Status in linux source package in Trusty: Fix Committed Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux source package in Utopic: Fix Committed Status in linux-lts-trusty source package in Utopic: Invalid Status in linux-lts-utopic source package in Utopic: Invalid Status in linux source package in Vivid: Fix Committed Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Bug description: Starting with kernels 3.2.0-64 and 3.13.0-29 Something has changed to once again that prevents IBM Domino's /opt/ibm/domino/notes/latest/linux/bindsock binary that runs as root (setuid) to get ports lower than 1024 for it's LDAP, SMTP, IMAP, POP3, and HTTP processes. The Domino server reports the following: : Listener failure: 'bindsock' is missing, not executable, not owned by root, not setuid root or user needs net_privaddr privilege. This is the same behaviour that was reported and subsequently corrected in Bug # 1269053 === break-fix: dbb490b96584d4e958533fb637f08b557f505657 6a2a2b3ae0759843b22c929881cc184b00cc63ff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1335478/+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 1357090] Re: Black screen on resume in Xubuntu 14.04.1
After trying unsuccessfully to use all the fixes I found online, I finally managed it to fix this problem myself today: 1. Install Gnome Screensaver sudo apt-get install gnome-screensaver 2. Replace Light Locker with Gnome Screen Saver Do it first for all new users sudo vi /etc/xdg/autostart/light-locker.desktop Change the line from: Exec=light-locker to: Exec=gnome-screensaver and then do the same for every existing user su username vi ~/.config/autostart/light-locker.desktop 3. Hide light-locker-settings from menu for all users sudo vi /usr/share/applications/light-locker-settings.desktop Add the line: Hidden=true Hope that helps everyone affected by his bug until Light Locker is actually production ready enough to warrant it's place in a LTS release. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1357090 Title: Black screen on resume in Xubuntu 14.04.1 Status in linux package in Ubuntu: Incomplete Bug description: It seems #1303736 is Not fixed. Black screen on resume when using standby on close lid is confirmed on Dell Latitude D400 on completely new install of Xubuntu 14.04.1 32 bit. downloaded 14 Aug from repository as a .ISO image. This despite claims to the contrary on the website. http://xubuntu.org/news/xubuntu-14-04-1-released/ pointing to https://bugs.launchpad.net/ubuntu/+source/xubuntu-default- settings/+bug/1303736 Using the Suspend key results in correct operation, i.e. the laptop suspends and resumes correctly on lid open. Suspending by closing the laptop lid results in the black screen when re-opening. Once in black screen mode, the only recourse is power off re-boot. Although power manager is set correctly to Suspend in the power manager , on closing the lid the system does NOT appear to suspend as it does when the Log-off Suspend button is clicked or the hardware Suspend key is pressed i.e. the problem APPEARS to be on lid close. Power manager and light-locker set NOT to lock on suspend or shutdown makes no difference to behaviour. Xubuntu up to 12.04.4 (plus latest updates) worked absolutely correctly before new install of 14.04.1 This is a MAJOR inconvenience for an upgrade of an LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1357090/+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 1284936] Re: BUG: unable to handle kernel paging request at ffffc900051f5000
The following commit is in 3.13 upstream as of 3.13.9: fa82051 make prepend_name() work correctly when called with negative *buflen Trusty has the 3.13.9 updates as of: 3.13.0-24.46 Can folks apply the latest Trusty updates and confirm if this bug still exists or not? If it does still exists, then commit fa82051 is not the fix and further investigation is needed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1284936 Title: BUG: unable to handle kernel paging request at c900051f5000 Status in linux package in Ubuntu: Triaged Bug description: Desktop was unresponsive on startup. ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-12-generic 3.13.0-12.32 ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4 Uname: Linux 3.13.0-12-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: biswass3257 F pulseaudio Date: Tue Feb 25 21:25:44 2014 DuplicateSignature: BUG: unable to handle kernel paging request at location RIP: 0010:location location memmove+0x4a/0x1a0 Failure: oops HibernationDevice: RESUME=UUID=15a6635a-ae68-4d9e-af22-9aad2088dad6 MachineType: Dell Inc. Dell System XPS L502X ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-12-generic root=UUID=46ffe02e-a8fb-466b-8b2e-35926951a1eb 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: kerneloops-daemon 0.12+git20090217-3ubuntu4 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: BUG: unable to handle kernel paging request at c900051f5000 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0NJT03 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284936/+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 1251065]
Are the latest logs I posted helpful? Let me know if you think I messed up somehow or need any other info. Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1251065 Title: HP Mini 1000 fails to resume from suspend Status in The Linux Kernel: Confirmed Status in linux package in Ubuntu: In Progress Bug description: Booting various kernels including the mainline 3.12 kernel, HP Mini 1000 does not resume from suspend. Problem seems to have begun following update to 13.10, including kernels 3.9, 3.10, 3.11. Ran steps on DebuggingKernelSuspend wiki page at https://wiki.ubuntu.com/DebugginKernelSuspend#A.22resume- trace.22_debugging_procedure_for_finding_buggy_drivers. Attached: dmesg.txt --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 DistroRelease: Ubuntu 13.10 EcryptfsInUse: Yes InstallationDate: Installed on 2013-11-12 (1 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MarkForUpload: True NonfreeKernelModules: wl Package: linux (not installed) Tags: saucy Uname: Linux 3.12.0-031200-generic i686 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1251065/+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 1408118] [NEW] hama uzzano keyboard do not work properly
Public bug reported: Hello I recently tried to use a hama uzzano keyboard on ubuntu 14.10. This is a wireless keyboard. Some times starts working and then suddenly stops, but mostly it does not work. i looked if it was recognized and it is: lsusb: pau@traveller:~$ lsusb Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 04ca:7012 Lite-On Technology Corp. 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 Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 003: ID 0930:021d Toshiba Corp. Bus 003 Device 008: ID 04d9:a01c Holtek Semiconductor, Inc. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub and dmesg | grep usb (partial) [ 8974.179356] input: HOLTEK Wireless USB Device as /devices/pci:00/:00:14.0/usb3/3-1/3-1:1.0/0003:04D9:A01C.000D/input/input29 [ 8974.179587] hid-generic 0003:04D9:A01C.000D: input,hidraw0: USB HID v1.10 Keyboard [HOLTEK Wireless USB Device] on usb-:00:14.0-1/input0 [ 8974.191755] input: HOLTEK Wireless USB Device as /devices/pci:00/:00:14.0/usb3/3-1/3-1:1.1/0003:04D9:A01C.000E/input/input30 [ 8974.192062] hid-generic 0003:04D9:A01C.000E: input,hidraw1: USB HID v1.10 Mouse [HOLTEK Wireless USB Device] on usb-:00:14.0-1/input1 i tried to solve the problem as it is explained here http://askubuntu.com/questions/160329/usb-keyboard-works-occasionally but it did not works. What can i do, i suppose this is a bug, do you need extra information? (it works with windows) thanks ** 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/1408118 Title: hama uzzano keyboard do not work properly Status in linux package in Ubuntu: New Bug description: Hello I recently tried to use a hama uzzano keyboard on ubuntu 14.10. This is a wireless keyboard. Some times starts working and then suddenly stops, but mostly it does not work. i looked if it was recognized and it is: lsusb: pau@traveller:~$ lsusb Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 04ca:7012 Lite-On Technology Corp. 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 Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 003: ID 0930:021d Toshiba Corp. Bus 003 Device 008: ID 04d9:a01c Holtek Semiconductor, Inc. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub and dmesg | grep usb (partial) [ 8974.179356] input: HOLTEK Wireless USB Device as /devices/pci:00/:00:14.0/usb3/3-1/3-1:1.0/0003:04D9:A01C.000D/input/input29 [ 8974.179587] hid-generic 0003:04D9:A01C.000D: input,hidraw0: USB HID v1.10 Keyboard [HOLTEK Wireless USB Device] on usb-:00:14.0-1/input0 [ 8974.191755] input: HOLTEK Wireless USB Device as /devices/pci:00/:00:14.0/usb3/3-1/3-1:1.1/0003:04D9:A01C.000E/input/input30 [ 8974.192062] hid-generic 0003:04D9:A01C.000E: input,hidraw1: USB HID v1.10 Mouse [HOLTEK Wireless USB Device] on usb-:00:14.0-1/input1 i tried to solve the problem as it is explained here http://askubuntu.com/questions/160329/usb-keyboard-works-occasionally but it did not works. What can i do, i suppose this is a bug, do you need extra information? (it works with windows) thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408118/+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 1407505] Re: No UMS support in radeon module
The only thing I hate more than bugs is reporting them. :-) OK! You build, I test. But give me more than one kernel at a time. -- Philippe -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1407505 Title: No UMS support in radeon module Status in linux package in Ubuntu: Confirmed Status in linux source package in Utopic: Confirmed Status in linux source package in Vivid: Confirmed Bug description: System: Kubuntu (adm64) 14.10. Last update: 4-Jan-2015 No proprietary drivers. No 3rd party software. The last kernel I was able to run on my Utopic system is 3.16.0-17-generic. Every update thereafter failed. The last one I tried is -28. From syslog for -28 kernel: Jan 4 14:22:41 aldebaran kernel: [1.712424] [drm] Initialized drm 1.1.0 20060810 Jan 4 14:22:41 aldebaran kernel: [1.736322] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [1.736375] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 10.340446] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 10.340448] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 101.573768] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 101.573771] [drm:radeon_init] *ERROR* No UMS support in radeon module! From syslog for -17 kernel: Jan 4 14:27:56 aldebaran kernel: [1.676277] [drm] Initialized drm 1.1.0 20060810 Jan 4 14:27:56 aldebaran kernel: [1.698850] [drm] radeon kernel modesetting enabled. Jan 4 14:27:56 aldebaran kernel: [1.698924] fb: switching to radeondrmfb from VESA VGA Jan 4 14:27:56 aldebaran kernel: [1.699341] [drm] initializing kernel modesetting (TURKS 0x1002:0x6758 0x1043:0x03EA). Jan 4 14:27:56 aldebaran kernel: [1.699351] [drm] register mmio base: 0xFDDC Jan 4 14:27:56 aldebaran kernel: [1.699352] [drm] register mmio size: 131072 Jan 4 14:27:56 aldebaran kernel: [1.699877] [drm] Detected VRAM RAM=1024M, BAR=256M
[Kernel-packages] [Bug 1400127] Re: Mellanox updates for Trusty
Sent v2 pull-request to ML with upstream only patches.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1400127
Title:
Mellanox updates for Trusty
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Trusty:
In Progress
Status in linux source package in Utopic:
In Progress
Bug description:
SRU Justification:
[Impact]
Users of Mellanox mlx4_{core,en} drivers may be missing hardware enablement
features.
[Test Case]
Test Mellanox hardware and ensure functionality with mlx4_{core,en} drivers.
[Fix]
As described below, and summarized in Comment #5.
--
The following changes since commit
b87885d70c29324b66ee7d4f979a9f95cc46564b:
UBUNTU: Ubuntu-3.13.0-42.71 (2014-12-05 14:35:11 +)
are attached to this tracker as patch files.
The main goal for this is patch-set is to add functionality to:
1. reduce cache misses by aligning CQE/EQE writes to the actual cache line
size
2. set/get link speed using ethtool [-s].
3. set rx/tx vlan offload
4. bug fixes
all of the patches are upsream (net-next), except for the last one which is
a bug fix waiting for review:
https://patchwork.ozlabs.org/patch/418451/
Ido Shamay (3):
net/mlx4_core: Enable CQE/EQE stride support
net/mlx4_core: Cache line EQE size support
net/mlx4_en: Add mlx4_en_get_cqe helper
Saeed Mahameed (12):
net/mlx4_core: Introduce mlx4_get_module_info for cable module info
reading
ethtool, net/mlx4_en: Cable info, get_module_info/eeprom ethtool support
net/mlx4_core: Introduce ACCESS_REG CMD and eth_prot_ctrl dev cap
net/mlx4_core: Add ethernet backplane autoneg device capability
ethtool, net/mlx4_en: Add 100M, 20G, 56G speeds ethtool reporting
support
net/mlx4_en: Use PTYS register to query ethtool settings
net/mlx4_en: Use PTYS register to set ethtool settings (Speed)
net/mlx4_en: Add support for setting rxvlan offload OFF/ON
net/mlx4_en: Add ethtool support for [rx|tx]vlan offload set to OFF/ON
net/mlx4_core: Prevent VF from changing port configuration
net/mlx4_en: mlx4_en_set_settings() always fails when autoneg is set
net/mlx4_en: ethtool force speed when asking for autoneg=off
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1400127/+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 1372609] Re: Touchpad detected as mouse on Asus ux303ln laptop
Actually. I'm trying to reproduce this bug using the former of the two drivers and it seems to have remidied it to some degree. With the latter driver upon suspend resume the backlight for the keyboard always breaks, whereas with the former driver it is itermittent. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1372609 Title: Touchpad detected as mouse on Asus ux303ln laptop Status in linux package in Ubuntu: Fix Committed Status in linux package in Arch Linux: New Bug description: Hi! I'm following the bug reporting documentation here: https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_Touchpad_features_like_scrolling.2C_tapping.2C_etc._do_not_work_at_all. The touchpad on my new Asus ux303ln laptop is detected as a mouse, so I can't access touchpad features such as two-finger scrolling. The laptop was very recently released and I couldn't find any outstanding firmware updates for it through Asus's Windows-based tools. % lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 Per the instructions on the wiki, I'm attaching output from /proc/bus/input/devices,` xinput --list`, and /var/log/Xorg.0.log. This machine also has a touchscreen, which I'm fairly certain is the maXtouch digitizer visible in the logs. I haven't yet restarted in Windows to see if it says anything useful about the touchpad, but I can do so if that's helpful. This is a fresh install of 14.04 and I haven't done much customization of it apart from installing some applications and changing the default resolution. The only relevant bit I noticed in /var/log/dmesg is this: [3.967547] input: PS/2 Logitech Wheel Mouse as /devices/platform/i8042/serio4/input/input11 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-35-generic 3.13.0-35.62 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tim2234 F pulseaudio /dev/snd/controlC1: tim2234 F pulseaudio CurrentDesktop: Unity Date: Mon Sep 22 14:30:33 2014 HibernationDevice: RESUME=UUID=e6052f15-271a-4424-aac2-9b0ee1e490ed InstallationDate: Installed on 2014-09-22 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 03eb:8a32 Atmel Corp. Bus 001 Device 002: ID 064e:9700 Suyin Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX303LN ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic.efi.signed root=UUID=4f908b1b-e06f-4dc9-9642-e952d2598e42 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/23/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LN.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LN.203:bd06/23/2014:svnASUSTeKCOMPUTERINC.:pnUX303LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX303LN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1372609/+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 1408105] Re: Haswell-based Chromebook touchpads and touchscreen are not enabled
I built a Utopic test kernel with a cherry-pick of the five commits listed in the description. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1408105/ Can you test this kernel on the appropriate systems and confirm it resolves the bug for each? Thanks in advance! ** Changed in: linux (Ubuntu) Assignee: (unassigned) = Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Utopic) Assignee: (unassigned) = Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu) Status: Triaged = In Progress ** Changed in: linux (Ubuntu Utopic) Status: Triaged = In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1408105 Title: Haswell-based Chromebook touchpads and touchscreen are not enabled Status in linux package in Ubuntu: In Progress Status in linux source package in Utopic: In Progress Bug description: SRU Justification: Impact: The Haswell-based Chromebooks have touchpads and a touchscreen unsupported in the 3.16 kernels Fix: Upstream in 3.17 Testcase: I've tested fixes by compiling and using upstream 3.17+ da3b0ab75aadab63d1ffd5563100c9386e444dad Acer C720 5ea9567f6126846f5dcfa8515d7ef2c238133c0d HP Chromebook 14 0e1e5e590a457063c94d55c219b349bcf0d1f93a Dell Chromebook 11 963cb6fa0f5f115986e970b9d97440e4906524fa Toshiba CB35 b90b3c4ae06af135e279c9a5aa1c640d22787fc4 Acer C720P To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408105/+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 453335] Re: apparmor complains about write access to a readonly file
Correction the bug number for the other bug is #1004606 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/453335 Title: apparmor complains about write access to a readonly file Status in libvirt package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in libvirt source package in Lucid: Fix Released Status in linux source package in Lucid: Fix Released Status in libvirt source package in Karmic: Fix Released Status in linux source package in Karmic: Fix Released Bug description: When doing libvirt/apparmor ISO testing, I noticed that if I try to create a VM via an ISO image, I get the following apparmor denied message: type=APPARMOR_DENIED msg=audit(1255714703.311:56): operation=open pid=31330 parent=1 profile=libvirt-7e7f916e-ff5a-c997-e9f6-c379793fd5be requested_mask=::rw denied_mask=::w fsuid=0 ouid=1000 name=/home/jamie/vms/isos/karmic/karmic-desktop-i386.iso What is happening is that libvirt is for some reason trying to write to this file, but it shouldn't. virt-manager shows this device as readonly and the XML for the VM shows it too: disk type='file' device='cdrom' source file='/home/jamie/vms/isos/karmic/karmic-desktop-i386.iso'/ target dev='hdc' bus='ide'/ readonly/ /disk The installation proceeds just fine and this isn't a regression, but libvirt should not try to write to installation media like this. I encountered this when installing via virt-manager using the following: local ISO, os type: generic/generic, kvm/i686, 512, 1 vcpu, 8GB disk, don't allocate now ProblemType: Bug Architecture: amd64 Date: Fri Oct 16 12:47:32 2009 DistroRelease: Ubuntu 9.10 Package: libvirt-bin 0.7.0-1ubuntu11 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.47-generic SourcePackage: libvirt Uname: Linux 2.6.31-14-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/453335/+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 1289746] [NEW] 14e4:4727 [Asus 1225B] BCM4313 not working with D-Link DIR-645 AP
You have been subscribed to a public bug: 1) lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 2) apt-cache policy broadcom-sta-source broadcom-sta-source: Installed: 6.30.223.141-1 Candidate: 6.30.223.141-1 Version table: *** 6.30.223.141-1 0 500 http://se.archive.ubuntu.com/ubuntu/ trusty/multiverse amd64 Packages 100 /var/lib/dpkg/status 3) What is expected to happen with my Asus 1225B-SIV047M laptop and DLINK DIR-645 AP is the WiFi works via the broadcom-sta-source driver. 4) What happened instead: Almost nothing. There is a valid ARP entry for the AP in the ARP cache, but there are no replies from ping. The same problem existed in 13.10 with this computer about a month ago. However, this computer has been able to use the AP w/o problems running 12.04 until about six months ago, when no longer connect to it. I tried upgrading the AP firmware to 1.04 B12 but this didn't change anything. I have two Android devices of different versions using the AP without problems. However, the wifi works with an AP from Huawei. uname -a Linux slim2a 3.13.0-39-generic #66-Ubuntu SMP Tue Oct 28 13:30:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux lspci -vvnn | grep -A 9 Network 04:00.0 Network controller [0280]: Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter [14e4:4727] (rev 01) Subsystem: AzureWave Device [1a3b:2047] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 17 Region 0: Memory at fea0 (64-bit, non-prefetchable) [size=16K] Capabilities: access denied Kernel driver in use: wl sudo dmidecode -s bios-version 209 sudo dmidecode -s bios-release-date 06/05/2012 ** Affects: bcmwl (Ubuntu) Importance: Medium Status: Fix Released ** Tags: amd64 latest-bios-209 saucy trusty -- 14e4:4727 [Asus 1225B] BCM4313 not working with D-Link DIR-645 AP https://bugs.launchpad.net/bugs/1289746 You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. -- 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 1408105] Re: Haswell-based Chromebook touchpads and touchscreen are not enabled
Or a source package / tarball? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1408105 Title: Haswell-based Chromebook touchpads and touchscreen are not enabled Status in linux package in Ubuntu: In Progress Status in linux source package in Utopic: In Progress Bug description: SRU Justification: Impact: The Haswell-based Chromebooks have touchpads and a touchscreen unsupported in the 3.16 kernels Fix: Upstream in 3.17 Testcase: I've tested fixes by compiling and using upstream 3.17+ da3b0ab75aadab63d1ffd5563100c9386e444dad Acer C720 5ea9567f6126846f5dcfa8515d7ef2c238133c0d HP Chromebook 14 0e1e5e590a457063c94d55c219b349bcf0d1f93a Dell Chromebook 11 963cb6fa0f5f115986e970b9d97440e4906524fa Toshiba CB35 b90b3c4ae06af135e279c9a5aa1c640d22787fc4 Acer C720P To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408105/+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 1404530] Re: Installing print Epsso Stylus SX235w
Thank you for taking the time to report this bug and helping to make Ubuntu better. You appear to be running a release of Ubuntu that is no longer supported. Please see https://wiki.ubuntu.com/Releases for information on our currently supported releases; consider using one of the LTS releases, as they will be supported for the longest amount of time. Some additional information on upgrading can be found in our community wiki, https://help.ubuntu.com/community/UpgradeNotes Thanks ** Information type changed from Private Security to Public ** Changed in: linux (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1404530 Title: Installing print Epsso Stylus SX235w Status in linux package in Ubuntu: Invalid Bug description: Have very dificult in resolv this problem i need you help other problem is mode low graphics i need soultion i love linux ubuntu but is problem stay very bad ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-26-generic 3.11.0-26.45 ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12 Uname: Linux 3.11.0-26-generic i686 NonfreeKernelModules: openafs ApportVersion: 2.12.5-0ubuntu2.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luisfortunato 1715 F pulseaudio Date: Sat Dec 20 17:49:41 2014 HibernationDevice: RESUME=UUID=9fcde59a-726a-40b4-af24-580b6b36c8b8 InstallationDate: Installed on 2014-09-01 (110 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MachineType: CLEVO CO. W240EU/W250EUQ/W270EUQ MarkForUpload: True ProcEnviron: LANGUAGE=pt:pt_BR:en TERM=xterm PATH=(custom, no user) LANG=pt_PT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-26-generic root=UUID=28a531d0-7bc8-4435-857a-48302434064c 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-3.11.0-26-generic N/A linux-backports-modules-3.11.0-26-generic N/A linux-firmware 1.116.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W240EU/W250EUQ/W270EUQ dmi.board.vendor: CLEVO CO. dmi.board.version: V3.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd02/26/2013:svnCLEVOCO.:pnW240EU/W250EUQ/W270EUQ:pvrNotApplicable:rvnCLEVOCO.:rnW240EU/W250EUQ/W270EUQ:rvrV3.0:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: W240EU/W250EUQ/W270EUQ dmi.product.version: Not Applicable dmi.sys.vendor: CLEVO CO. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1404530/+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 1408118] Re: hama uzzano keyboard do not work properly
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.19 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as Confirmed. Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19-rc3-vivid/ ** Changed in: linux (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1408118 Title: hama uzzano keyboard do not work properly Status in linux package in Ubuntu: Incomplete Bug description: Hello I recently tried to use a hama uzzano keyboard on ubuntu 14.10. This is a wireless keyboard. Some times starts working and then suddenly stops, but mostly it does not work. i looked if it was recognized and it is: lsusb: pau@traveller:~$ lsusb Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 04ca:7012 Lite-On Technology Corp. 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 Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 003: ID 0930:021d Toshiba Corp. Bus 003 Device 008: ID 04d9:a01c Holtek Semiconductor, Inc. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub and dmesg | grep usb (partial) [ 8974.179356] input: HOLTEK Wireless USB Device as /devices/pci:00/:00:14.0/usb3/3-1/3-1:1.0/0003:04D9:A01C.000D/input/input29 [ 8974.179587] hid-generic 0003:04D9:A01C.000D: input,hidraw0: USB HID v1.10 Keyboard [HOLTEK Wireless USB Device] on usb-:00:14.0-1/input0 [ 8974.191755] input: HOLTEK Wireless USB Device as /devices/pci:00/:00:14.0/usb3/3-1/3-1:1.1/0003:04D9:A01C.000E/input/input30 [ 8974.192062] hid-generic 0003:04D9:A01C.000E: input,hidraw1: USB HID v1.10 Mouse [HOLTEK Wireless USB Device] on usb-:00:14.0-1/input1 i tried to solve the problem as it is explained here http://askubuntu.com/questions/160329/usb-keyboard-works-occasionally but it did not works. What can i do, i suppose this is a bug, do you need extra information? (it works with windows) thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408118/+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 453335] Re: apparmor complains about write access to a readonly file
I think this is actually causing a moderately serious regression with snapshots. If you look at the contents of an apparmor define for an example VM the deny that silences the error here also prevents snapshot commits from working and because the error is hidden makes this extra difficult to debug. /var/log/libvirt/**/OpenWRT.log w, /var/lib/libvirt/**/OpenWRT.monitor rw, /var/run/libvirt/**/OpenWRT.pid rwk, /run/libvirt/**/OpenWRT.pid rwk, /var/run/libvirt/**/*.tunnelmigrate.dest.OpenWRT rw, /run/libvirt/**/*.tunnelmigrate.dest.OpenWRT rw, /var/lib/libvirt/images/openwrt-x86-kvm_guest-combined-ext4-zfs-1.qcow2 rw, /var/lib/libvirt/images/openwrt-x86-kvm_guest-combined-ext4.img r, # don't audit writes to readonly files deny /var/lib/libvirt/images/openwrt-x86-kvm_guest-combined-ext4.img w, /dev/vhost-net rw, /var/lib/libvirt/images/openwrt-x86-kvm_guest-combined-ext4.img rw, The bug number for the snapshot bug is #453335 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/453335 Title: apparmor complains about write access to a readonly file Status in libvirt package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in libvirt source package in Lucid: Fix Released Status in linux source package in Lucid: Fix Released Status in libvirt source package in Karmic: Fix Released Status in linux source package in Karmic: Fix Released Bug description: When doing libvirt/apparmor ISO testing, I noticed that if I try to create a VM via an ISO image, I get the following apparmor denied message: type=APPARMOR_DENIED msg=audit(1255714703.311:56): operation=open pid=31330 parent=1 profile=libvirt-7e7f916e-ff5a-c997-e9f6-c379793fd5be requested_mask=::rw denied_mask=::w fsuid=0 ouid=1000 name=/home/jamie/vms/isos/karmic/karmic-desktop-i386.iso What is happening is that libvirt is for some reason trying to write to this file, but it shouldn't. virt-manager shows this device as readonly and the XML for the VM shows it too: disk type='file' device='cdrom' source file='/home/jamie/vms/isos/karmic/karmic-desktop-i386.iso'/ target dev='hdc' bus='ide'/ readonly/ /disk The installation proceeds just fine and this isn't a regression, but libvirt should not try to write to installation media like this. I encountered this when installing via virt-manager using the following: local ISO, os type: generic/generic, kvm/i686, 512, 1 vcpu, 8GB disk, don't allocate now ProblemType: Bug Architecture: amd64 Date: Fri Oct 16 12:47:32 2009 DistroRelease: Ubuntu 9.10 Package: libvirt-bin 0.7.0-1ubuntu11 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.47-generic SourcePackage: libvirt Uname: Linux 2.6.31-14-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/453335/+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 1289746] Re: 14e4:4727 [Asus 1225B] BCM4313 not working with D-Link DIR-645 AP
LennartP, thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because as per https://bugs.launchpad.net/ubuntu/+source/broadcom- sta/+bug/1289746/comments/14 the bug has been fixed in the latest development version of Ubuntu - Vivid Vervet. This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please perform as much as possible of the SRU Procedure [1] to bring the need to a developer's attention. [1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure ** Package changed: broadcom-sta (Ubuntu) = bcmwl (Ubuntu) ** Changed in: bcmwl (Ubuntu) Status: Incomplete = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1289746 Title: 14e4:4727 [Asus 1225B] BCM4313 not working with D-Link DIR-645 AP Status in bcmwl package in Ubuntu: Fix Released Bug description: 1) lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 2) apt-cache policy broadcom-sta-source broadcom-sta-source: Installed: 6.30.223.141-1 Candidate: 6.30.223.141-1 Version table: *** 6.30.223.141-1 0 500 http://se.archive.ubuntu.com/ubuntu/ trusty/multiverse amd64 Packages 100 /var/lib/dpkg/status 3) What is expected to happen with my Asus 1225B-SIV047M laptop and DLINK DIR-645 AP is the WiFi works via the broadcom-sta-source driver. 4) What happened instead: Almost nothing. There is a valid ARP entry for the AP in the ARP cache, but there are no replies from ping. The same problem existed in 13.10 with this computer about a month ago. However, this computer has been able to use the AP w/o problems running 12.04 until about six months ago, when no longer connect to it. I tried upgrading the AP firmware to 1.04 B12 but this didn't change anything. I have two Android devices of different versions using the AP without problems. However, the wifi works with an AP from Huawei. uname -a Linux slim2a 3.13.0-39-generic #66-Ubuntu SMP Tue Oct 28 13:30:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux lspci -vvnn | grep -A 9 Network 04:00.0 Network controller [0280]: Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter [14e4:4727] (rev 01) Subsystem: AzureWave Device [1a3b:2047] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 17 Region 0: Memory at fea0 (64-bit, non-prefetchable) [size=16K] Capabilities: access denied Kernel driver in use: wl sudo dmidecode -s bios-version 209 sudo dmidecode -s bios-release-date 06/05/2012 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1289746/+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 1408105] Re: Haswell-based Chromebook touchpads and touchscreen are not enabled
Thanks! These deb's are for armhf, but the machines are amd64. I cannot test all hardware, as I only have one of the machines, but they are nearly identical except for hardware id's. Will this be acceptable? Would it be possible to publish these changes to a git tree for me to pull and build? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1408105 Title: Haswell-based Chromebook touchpads and touchscreen are not enabled Status in linux package in Ubuntu: In Progress Status in linux source package in Utopic: In Progress Bug description: SRU Justification: Impact: The Haswell-based Chromebooks have touchpads and a touchscreen unsupported in the 3.16 kernels Fix: Upstream in 3.17 Testcase: I've tested fixes by compiling and using upstream 3.17+ da3b0ab75aadab63d1ffd5563100c9386e444dad Acer C720 5ea9567f6126846f5dcfa8515d7ef2c238133c0d HP Chromebook 14 0e1e5e590a457063c94d55c219b349bcf0d1f93a Dell Chromebook 11 963cb6fa0f5f115986e970b9d97440e4906524fa Toshiba CB35 b90b3c4ae06af135e279c9a5aa1c640d22787fc4 Acer C720P To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408105/+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 1407522] Re: bcmwl package was sugested by KDE driver manager but broke the system
Rostislav Kandilarov, it wouldn't hurt to e-mail them given you are testing the latest version of the driver in Vivid. ** Tags added: precise ** Summary changed: - bcmwl package was sugested by KDE driver manager but broke the system + 14e4:4311 [HP Compaq nx7400 Notebook PC] bcmwl package was sugested by KDE driver manager but broke the system ** Summary changed: - 14e4:4311 [HP Compaq nx7400 Notebook PC] bcmwl package was sugested by KDE driver manager but broke the system + 14e4:4311 [HP Compaq nx7400 Notebook PC] bcmwl package was suggested by KDE driver manager but broke the system ** Changed in: bcmwl (Ubuntu) Status: Incomplete = Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1407522 Title: 14e4:4311 [HP Compaq nx7400 Notebook PC] bcmwl package was suggested by KDE driver manager but broke the system Status in bcmwl package in Ubuntu: Triaged Bug description: On fresh 14.10 install on the first GUI run in KDE the KDE Driver Manager suggested installation of bcmwl-kernel-source (see attached screenshot)for my Broadcom Corporation BCM4311. After successful installation of the package and restart, my system got Jan 4 23:32:13 Beatles kernel: [ 19.485177] wl driver 6.30.223.248 (r487574) failed with code 21 Jan 4 23:32:13 Beatles kernel: [ 19.485208] [ cut here ] Jan 4 23:32:13 Beatles kernel: [ 19.485242] kernel BUG at include/net/cfg80211.h:3343! full description of the message in attached file (syslog_extracted.log). For some reason this also affects the driver for my NIC and my laptop got out of any possible network connection. So instead of configuring the wireless card it left me with only lo interface :(. I would expect properly configured modules for WAN and LAN Luckily apt-get remove --purge bcmwl-kernel-source restores the previous state so I can submit this bug via LAN. Now I'm running Ubuntu 14.10 but the same happened half an year ago when I tried to install 14.04 on this laptop. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: bcmwl-kernel-source (not installed) ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jan 5 01:00:26 2015 SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1407522/+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 1407505] Re: No UMS support in radeon module
OK! I'll check that one out this evening. I don't know what the constraints are, but if you must build kernels based on my tests, then this is going to take a few days. On the other hand, if I have a bunch of kernels, I can install them all at once, boot one then boot the next until we find the culprit. That's at most one hour, not counting download time, which for me would be around 15-30 min per kernel, but that can be automated. Whatever the method, as I said, you build them, I test them. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1407505 Title: No UMS support in radeon module Status in linux package in Ubuntu: Confirmed Status in linux source package in Utopic: Confirmed Status in linux source package in Vivid: Confirmed Bug description: System: Kubuntu (adm64) 14.10. Last update: 4-Jan-2015 No proprietary drivers. No 3rd party software. The last kernel I was able to run on my Utopic system is 3.16.0-17-generic. Every update thereafter failed. The last one I tried is -28. From syslog for -28 kernel: Jan 4 14:22:41 aldebaran kernel: [1.712424] [drm] Initialized drm 1.1.0 20060810 Jan 4 14:22:41 aldebaran kernel: [1.736322] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [1.736375] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 10.340446] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 10.340448] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 101.573768] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 101.573771] [drm:radeon_init] *ERROR* No UMS support in radeon module! From syslog for -17 kernel: Jan 4 14:27:56 aldebaran kernel: [1.676277] [drm] Initialized drm 1.1.0 20060810 Jan 4 14:27:56 aldebaran kernel: [1.698850] [drm] radeon kernel modesetting enabled. Jan 4 14:27:56 aldebaran kernel: [1.698924] fb: switching to radeondrmfb from VESA VGA Jan 4 14:27:56 aldebaran kernel: [1.699341] [drm] initializing kernel modesetting (TURKS 0x1002:0x6758 0x1043:0x03EA). Jan 4 14:27:56 aldebaran kernel: [1.699351] [drm] register mmio base: 0xFDDC Jan 4 14:27:56 aldebaran kernel: [1.699352] [drm] register mmio size: 131072
[Kernel-packages] [Bug 1372609] Re: Touchpad detected as mouse on Asus ux303ln laptop
I have a UX303LA and the drivers work great until I suspend and resume. Then the backlight for the keys no longer work. The screen brightness does still work but the OSD Notification does not show when I change the brightness. How should I go about tracking down the error? dmesg? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1372609 Title: Touchpad detected as mouse on Asus ux303ln laptop Status in linux package in Ubuntu: Fix Committed Status in linux package in Arch Linux: New Bug description: Hi! I'm following the bug reporting documentation here: https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_Touchpad_features_like_scrolling.2C_tapping.2C_etc._do_not_work_at_all. The touchpad on my new Asus ux303ln laptop is detected as a mouse, so I can't access touchpad features such as two-finger scrolling. The laptop was very recently released and I couldn't find any outstanding firmware updates for it through Asus's Windows-based tools. % lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 Per the instructions on the wiki, I'm attaching output from /proc/bus/input/devices,` xinput --list`, and /var/log/Xorg.0.log. This machine also has a touchscreen, which I'm fairly certain is the maXtouch digitizer visible in the logs. I haven't yet restarted in Windows to see if it says anything useful about the touchpad, but I can do so if that's helpful. This is a fresh install of 14.04 and I haven't done much customization of it apart from installing some applications and changing the default resolution. The only relevant bit I noticed in /var/log/dmesg is this: [3.967547] input: PS/2 Logitech Wheel Mouse as /devices/platform/i8042/serio4/input/input11 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-35-generic 3.13.0-35.62 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tim2234 F pulseaudio /dev/snd/controlC1: tim2234 F pulseaudio CurrentDesktop: Unity Date: Mon Sep 22 14:30:33 2014 HibernationDevice: RESUME=UUID=e6052f15-271a-4424-aac2-9b0ee1e490ed InstallationDate: Installed on 2014-09-22 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 03eb:8a32 Atmel Corp. Bus 001 Device 002: ID 064e:9700 Suyin Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX303LN ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic.efi.signed root=UUID=4f908b1b-e06f-4dc9-9642-e952d2598e42 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/23/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LN.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LN.203:bd06/23/2014:svnASUSTeKCOMPUTERINC.:pnUX303LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX303LN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1372609/+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 1408105] Re: Haswell-based Chromebook touchpads and touchscreen are not enabled
** Changed in: linux (Ubuntu) Status: Incomplete = Triaged ** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Utopic) Status: New = Triaged ** Changed in: linux (Ubuntu Utopic) Importance: Undecided = Medium ** Tags added: kernel-da-key utopic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1408105 Title: Haswell-based Chromebook touchpads and touchscreen are not enabled Status in linux package in Ubuntu: Triaged Status in linux source package in Utopic: Triaged Bug description: SRU Justification: Impact: The Haswell-based Chromebooks have touchpads and a touchscreen unsupported in the 3.16 kernels Fix: Upstream in 3.17 Testcase: I've tested fixes by compiling and using upstream 3.17+ da3b0ab75aadab63d1ffd5563100c9386e444dad Acer C720 5ea9567f6126846f5dcfa8515d7ef2c238133c0d HP Chromebook 14 0e1e5e590a457063c94d55c219b349bcf0d1f93a Dell Chromebook 11 963cb6fa0f5f115986e970b9d97440e4906524fa Toshiba CB35 b90b3c4ae06af135e279c9a5aa1c640d22787fc4 Acer C720P To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408105/+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 1372609] Re: Touchpad detected as mouse on Asus ux303ln laptop
@Timo Mathias Gottschlag worte the driver. I backported it ti Ubuntu kernel. You can download a kernel image here. https://www.dropbox.com/sh/07642x3lziqgmz9/AACGWNO5_lNnX7x7tYMoH9gka?dl=0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1372609 Title: Touchpad detected as mouse on Asus ux303ln laptop Status in linux package in Ubuntu: Fix Committed Status in linux package in Arch Linux: New Bug description: Hi! I'm following the bug reporting documentation here: https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_Touchpad_features_like_scrolling.2C_tapping.2C_etc._do_not_work_at_all. The touchpad on my new Asus ux303ln laptop is detected as a mouse, so I can't access touchpad features such as two-finger scrolling. The laptop was very recently released and I couldn't find any outstanding firmware updates for it through Asus's Windows-based tools. % lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 Per the instructions on the wiki, I'm attaching output from /proc/bus/input/devices,` xinput --list`, and /var/log/Xorg.0.log. This machine also has a touchscreen, which I'm fairly certain is the maXtouch digitizer visible in the logs. I haven't yet restarted in Windows to see if it says anything useful about the touchpad, but I can do so if that's helpful. This is a fresh install of 14.04 and I haven't done much customization of it apart from installing some applications and changing the default resolution. The only relevant bit I noticed in /var/log/dmesg is this: [3.967547] input: PS/2 Logitech Wheel Mouse as /devices/platform/i8042/serio4/input/input11 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-35-generic 3.13.0-35.62 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tim2234 F pulseaudio /dev/snd/controlC1: tim2234 F pulseaudio CurrentDesktop: Unity Date: Mon Sep 22 14:30:33 2014 HibernationDevice: RESUME=UUID=e6052f15-271a-4424-aac2-9b0ee1e490ed InstallationDate: Installed on 2014-09-22 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 03eb:8a32 Atmel Corp. Bus 001 Device 002: ID 064e:9700 Suyin Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX303LN ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic.efi.signed root=UUID=4f908b1b-e06f-4dc9-9642-e952d2598e42 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/23/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LN.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LN.203:bd06/23/2014:svnASUSTeKCOMPUTERINC.:pnUX303LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX303LN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1372609/+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
