[Kernel-packages] [Bug 1411535] 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/1411535 Title: [Dell Precision M4800] No Unity 3D support on nVidia GK106GLM [10de:11fc] with open-source driver Status in linux package in Ubuntu: Confirmed Bug description: CID: 201305-13527 Dell Precision M4800 With Enable Switchable Graphics disabled in the BIOS, this system would use software rendering in Unity. ubuntu@201305-13527:~$ /usr/lib/nux/unity_support_test -c -p OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.4, 256 bits) OpenGL version string: 2.1 Mesa 10.1.3 Not software rendered:no Not blacklisted: yes GLX fbconfig: yes GLX texture from pixmap: yes GL npot or rect textures: yes Compiz supported: no But with that aforementioned option enabled, it won't have this issue. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-44-generic 3.13.0-44.73 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1439 F pulseaudio /dev/snd/controlC1: ubuntu 1439 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Fri Jan 16 02:21:07 2015 HibernationDevice: RESUME=UUID=4e3c0183-4d3f-495e-8d6a-57e2b23e6412 InstallationDate: Installed on 2015-01-16 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Dell Inc. Precision M4800 ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic root=UUID=3edd6366-27b1-41af-88d4-ac1abe216d8f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-44-generic N/A linux-backports-modules-3.13.0-44-generic N/A linux-firmware 1.127.11 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 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: 0FVDR2 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd12/03/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn0FVDR2:rvrX02: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/1411535/+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 1378744] Re: nVidia GK106GLM [Quadro K2100M] [10de:11fc] Connect to HDMI / DP port with open-source driver will cause Xorg crash
For bug https://bugs.freedesktop.org/show_bug.cgi?id=76990 I can't reproduce this on this system (with Switchable Graphics enabled or disabled), therefore I think this is not the case. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1378744 Title: nVidia GK106GLM [Quadro K2100M] [10de:11fc] Connect to HDMI / DP port with open-source driver will cause Xorg crash Status in Accelerated Xorg driver for nVidia cards: Confirmed Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: CID: 201305-13527 Dell Precision M4800 Xorg would crash and restart (you will see the login screen again and again) when the HDMI / DP cable is connected to the system. Steps: 1. Install 14.04 + update (3.13.0-36), boot to desktop 2. Connect a HDMI / DP cable Expected result: * The external monitor should work Actual result: * The external monitor screen is black, and the Xorg crashed - black screen on this laptop - login screen shows up - black screen... repeat. WORKAROUND: * Install the proprietary nvidia driver I'm not sure if this should be consider as a blocker. But hey, we need to certified this I+N system with the proprietary driver, I think it's OK to not to call this a blocker. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-36-generic 3.13.0-36.63 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 7071 F pulseaudio ubuntu 7529 F pulseaudio /dev/snd/controlC1: ubuntu 7071 F pulseaudio ubuntu 7529 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Wed Oct 8 06:20:44 2014 HibernationDevice: RESUME=UUID=46ed949d-eff8-48e9-b337-6425f480cf12 InstallationDate: Installed on 2014-10-08 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Precision M4800 ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic.efi.signed root=UUID=e7f55d08-44a4-447e-8fc6-563864d60df4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-36-generic N/A linux-backports-modules-3.13.0-36-generic N/A linux-firmware 1.127.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/02/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0FVDR2 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd01/02/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn0FVDR2:rvrX02: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/nouveau/+bug/1378744/+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 1410909] Re: linux-armadaxp: 3.2.0-1644.63 -proposed tracker
All builds are complete, packages in this bug can be copied to -proposed. ** Changed in: kernel-sru-workflow/prepare-package Status: New = Fix Released ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New = Confirmed ** Changed in: kernel-sru-workflow/package-testing Status: New = In Progress ** Changed in: kernel-sru-workflow/package-testing Status: In Progress = Confirmed ** Description changed: This bug is for tracking the 3.2.0-1644.63 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-stable-Prepare-package-start:Wednesday, 14. January 2015 18:03 UTC - kernel-stable-phase:Prepare - kernel-stable-phase-changed:Wednesday, 14. January 2015 18:03 UTC kernel-stable-master-bug:1410459 kernel-stable-Certification-testing-end:Friday, 16. January 2015 07:01 UTC kernel-stable-Security-signoff-end:Friday, 16. January 2015 07:02 UTC + kernel-stable-phase:PPA Testing + kernel-stable-phase-changed:Friday, 16. January 2015 08:02 UTC + kernel-stable-Prepare-package-end:Friday, 16. January 2015 08:02 UTC + kernel-stable-Promote-to-proposed-start:Friday, 16. January 2015 08:02 UTC + ppa-package-testing-start:Friday, 16. January 2015 08:02 UTC -- 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/1410909 Title: linux-armadaxp: 3.2.0-1644.63 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-armadaxp source package in Precise: In Progress Bug description: This bug is for tracking the 3.2.0-1644.63 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-stable-Prepare-package-start:Wednesday, 14. January 2015 18:03 UTC kernel-stable-master-bug:1410459 kernel-stable-Certification-testing-end:Friday, 16. January 2015 07:01 UTC kernel-stable-Security-signoff-end:Friday, 16. January 2015 07:02 UTC kernel-stable-phase:PPA Testing kernel-stable-phase-changed:Friday, 16. January 2015 08:02 UTC kernel-stable-Prepare-package-end:Friday, 16. January 2015 08:02 UTC kernel-stable-Promote-to-proposed-start:Friday, 16. January 2015 08:02 UTC ppa-package-testing-start:Friday, 16. January 2015 08:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1410909/+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 1411514] Re: [Dell Precision M4800] Brightness can't be controlled on 14.04.1
With the proprietary driver nvidia-331 installed, the brightness control could work as expected. (Switchable Graphic disabled.) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1411514 Title: [Dell Precision M4800] Brightness can't be controlled on 14.04.1 Status in HWE Next Project: Triaged Status in linux package in Ubuntu: Confirmed Bug description: CID: 201305-13527 Dell Precision M4800 The screen brightness The brightness control does not work at all on 14.04.1 Steps: 1. Install 14.04.1 + update 2. Test the brightness control with hotkeys 3. Test the brightness control by using the Brightness and Lock applet. Expected results: * Brightness control should work in step 2 and 3 Actual result: * Brightness level would change with the hotkey, but the backlight level won't, nothing happened when you scroll the scrollbar in the Brightness and Lock applet. Debugging information: ubuntu@201305-13527:~$ sudo showkey -s kb mode was ?UNKNOWN? [ if you are trying this under X, it might not work since the X server is also reading /dev/console ] press any key (program terminates 10s after last keypress)... 0x9c 0xe0 0x54 0xe0 0xd4 0xe0 0x4c 0xe0 0xcc 0x1d ^Ccaught signal 2, cleaning up... ubuntu@201305-13527:~$ ubuntu@201305-13527:~$ sudo showkey -k kb mode was ?UNKNOWN? [ if you are trying this under X, it might not work since the X server is also reading /dev/console ] press any key (program terminates 10s after last keypress)... keycode 28 release keycode 225 press keycode 225 release keycode 224 press keycode 224 release keycode 29 press ^Ccaught signal 2, cleaning up... ubuntu@201305-13527:~$ ubuntu@201305-13527:~$ ls /sys/class/backlight/ acpi_video0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-44-generic 3.13.0-44.73 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1635 F pulseaudio ubuntu 2242 F pulseaudio /dev/snd/controlC0: ubuntu 1635 F pulseaudio ubuntu 2242 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Fri Jan 16 00:56:25 2015 HibernationDevice: RESUME=UUID=4e3c0183-4d3f-495e-8d6a-57e2b23e6412 InstallationDate: Installed on 2015-01-16 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Dell Inc. Precision M4800 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic root=UUID=3edd6366-27b1-41af-88d4-ac1abe216d8f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-44-generic N/A linux-backports-modules-3.13.0-44-generic N/A linux-firmware 1.127.11 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 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: 0FVDR2 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd12/03/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn0FVDR2:rvrX02: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/hwe-next/+bug/1411514/+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 1410908] Re: linux-ti-omap4: 3.2.0-1459.79 -proposed tracker
git://kernel.ubuntu.com/ppisati/ubuntu-precise.git ti-omap4 ** Summary changed: - linux-ti-omap4: version to be filled -proposed tracker + linux-ti-omap4: 3.2.0-1459.79 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1410908 Title: linux-ti-omap4: 3.2.0-1459.79 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-ti-omap4 source package in Precise: New Bug description: This bug is for tracking the version to be filled 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-stable-Prepare-package-start:Wednesday, 14. January 2015 18:01 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Wednesday, 14. January 2015 18:01 UTC kernel-stable-master-bug:1410459 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1410908/+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 1411535] Re: [Dell Precision M4800] No Unity 3D support on nVidia GK106GLM [10de:11fc] with open-source driver
This issue could be fixed by installing the proprietary nvidia-331 driver. Therefore I think we don't need to add the blocker tag to this. ** Package changed: linux (Ubuntu) = xserver-xorg-video-nouveau (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1411535 Title: [Dell Precision M4800] No Unity 3D support on nVidia GK106GLM [10de:11fc] with open-source driver Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: CID: 201305-13527 Dell Precision M4800 With Enable Switchable Graphics disabled in the BIOS, this system would use software rendering in Unity. ubuntu@201305-13527:~$ /usr/lib/nux/unity_support_test -c -p OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.4, 256 bits) OpenGL version string: 2.1 Mesa 10.1.3 Not software rendered:no Not blacklisted: yes GLX fbconfig: yes GLX texture from pixmap: yes GL npot or rect textures: yes Compiz supported: no But with that aforementioned option enabled, it won't have this issue. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-44-generic 3.13.0-44.73 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1439 F pulseaudio /dev/snd/controlC1: ubuntu 1439 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Fri Jan 16 02:21:07 2015 HibernationDevice: RESUME=UUID=4e3c0183-4d3f-495e-8d6a-57e2b23e6412 InstallationDate: Installed on 2015-01-16 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Dell Inc. Precision M4800 ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic root=UUID=3edd6366-27b1-41af-88d4-ac1abe216d8f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-44-generic N/A linux-backports-modules-3.13.0-44-generic N/A linux-firmware 1.127.11 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 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: 0FVDR2 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd12/03/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn0FVDR2:rvrX02: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/xserver-xorg-video-nouveau/+bug/1411535/+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 1410309] Re: [HP EliteBook 725 G2 Notebook PC] mute LED does not work. it always keeps the same color (white).
** Changed in: linux (Ubuntu) Assignee: Hui Wang (hui.wang) = (unassigned) ** Changed in: linux (Ubuntu) Status: Confirmed = Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1410309 Title: [HP EliteBook 725 G2 Notebook PC] mute LED does not work. it always keeps the same color (white). Status in linux package in Ubuntu: Won't Fix Bug description: The way to reproduce this bug and the basic debug information are at LP: #1409721 I separate LP: #1409721 to several bug reports because there are different failed features from the same system. --- ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1516 F pulseaudio /dev/snd/controlC1: ubuntu 1516 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=9864838c-7ba0-41b5-bd85-fe728504b659 InstallationDate: Installed on 2015-01-14 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP 430 G2 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic root=UUID=d4e5a7ff-0bd2-48a7-9d43-2defe1dcd58b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 RelatedPackageVersions: linux-restricted-modules-3.13.0-44-generic N/A linux-backports-modules-3.13.0-44-generic N/A linux-firmware 1.127.11 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.13.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/07/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M74 Ver. 01.03 dmi.board.name: 2246 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 67.22 dmi.chassis.asset.tag: 73612P10CU dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrM74Ver.01.03:bd07/07/2014:svnHewlett-Packard:pnHP430G2:pvrA3009C510002:rvnHewlett-Packard:rn2246:rvrKBCVersion67.22:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP 430 G2 dmi.product.version: A3009C510002 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1410309/+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 1410308] Re: [HP EliteBook 725 G2 Notebook PC] mic mute LED does not work.
** Tags added: 201405-15063 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1410308 Title: [HP EliteBook 725 G2 Notebook PC] mic mute LED does not work. Status in linux package in Ubuntu: Confirmed Bug description: The way to reproduce this bug and the basic debug information are at LP: #1409721 I separate LP: #1409721 to several bug reports because there are different failed features from the same system. --- ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2015-01-08 (5 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) Package: linux (not installed) Tags: trusty Uname: Linux 3.19.0-031900rc4-generic x86_64 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 _MarkForUpload: True --- ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2015-01-08 (5 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) Package: linux (not installed) Tags: trusty Uname: Linux 3.19.0-031900rc4-generic x86_64 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 _MarkForUpload: True --- ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1602 F pulseaudio /dev/snd/controlC0: ubuntu 1602 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=e24b803a-e217-4d6d-a35c-dbe0c033966a InstallationDate: Installed on 2015-01-08 (5 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP Licrice NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic root=UUID=c1e0a265-8c75-4427-ad25-f0c76f003ce7 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 RelatedPackageVersions: linux-restricted-modules-3.13.0-44-generic N/A linux-backports-modules-3.13.0-44-generic N/A linux-firmware 1.127.11 Tags: trusty Uname: Linux 3.13.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/03/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M84 Ver. 97.35 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 221D dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 63.14 dmi.chassis.asset.tag: 73612P10CU dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrM84Ver.97.35:bd09/03/2014:svnHewlett-Packard:pnHPLicrice:pvrA3009CD10002:rvnHewlett-Packard:rn221D:rvrKBCVersion63.14:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Licrice dmi.product.version: A3009CD10002 dmi.sys.vendor: Hewlett-Packard --- ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1516 F pulseaudio /dev/snd/controlC1: ubuntu 1516 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=9864838c-7ba0-41b5-bd85-fe728504b659 InstallationDate: Installed on 2015-01-14 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP 430 G2 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic root=UUID=d4e5a7ff-0bd2-48a7-9d43-2defe1dcd58b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 RelatedPackageVersions: linux-restricted-modules-3.13.0-44-generic N/A linux-backports-modules-3.13.0-44-generic N/A linux-firmware 1.127.11 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.13.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True
[Kernel-packages] [Bug 1410309] Re: [HP EliteBook 725 G2 Notebook PC] mute LED does not work. it always keeps the same color (white).
** Tags added: 201405-15063 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1410309 Title: [HP EliteBook 725 G2 Notebook PC] mute LED does not work. it always keeps the same color (white). Status in linux package in Ubuntu: Won't Fix Bug description: The way to reproduce this bug and the basic debug information are at LP: #1409721 I separate LP: #1409721 to several bug reports because there are different failed features from the same system. --- ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1516 F pulseaudio /dev/snd/controlC1: ubuntu 1516 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=9864838c-7ba0-41b5-bd85-fe728504b659 InstallationDate: Installed on 2015-01-14 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP 430 G2 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic root=UUID=d4e5a7ff-0bd2-48a7-9d43-2defe1dcd58b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 RelatedPackageVersions: linux-restricted-modules-3.13.0-44-generic N/A linux-backports-modules-3.13.0-44-generic N/A linux-firmware 1.127.11 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.13.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/07/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M74 Ver. 01.03 dmi.board.name: 2246 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 67.22 dmi.chassis.asset.tag: 73612P10CU dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrM74Ver.01.03:bd07/07/2014:svnHewlett-Packard:pnHP430G2:pvrA3009C510002:rvnHewlett-Packard:rn2246:rvrKBCVersion67.22:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP 430 G2 dmi.product.version: A3009C510002 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1410309/+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 1409721] Re: [HP EliteBook 725 G2 Notebook PC] mic mute key (Fn+F8) does not work
** Tags added: 201405-15063 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1409721 Title: [HP EliteBook 725 G2 Notebook PC] mic mute key (Fn+F8) does not work Status in HWE Next Project: Triaged Status in linux package in Ubuntu: Confirmed Bug description: HP EliteBook 725 G2 Notebook PC (CID 201405-15214) updated ubuntu 14.04.1 3.13.0-43-generic #72 Steps to reproduce this bug: 1. install 14.04.1 and use the updater to update the system. Reboot. 2. Get into the desktop and ready to use the system. 3. sudo apt-get install sox 4. apply command 'sox -t alsa default tmp.wav' to record the sound. Press Fn F8 at the same time. 5. use 'ctrl+c' to stop recording. use 'play tmp.wav' to playback 6. during the playback, press the mute fhunction key. Expected result: of step 5. : The recorded sound was muted. The LED indicate the mic was muted. of step 6. : The speaker was muted and the mute LED indicate it was muted. Actual result: of step 5. : nothing happened. of step 6 : the sound was muted but the LED did not change color. More information: sudo hda-verb /dev/snd/hwC1D0 0x18 SET_PIN_WIDGET_CONTROL 0x20 could turn off the mic mute LED sudo hda-verb /dev/snd/hwC1D0 0x18 SET_PIN_WIDGET_CONTROL 0x24 could turn on the mic mute LED -- 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 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1404 F pulseaudio /dev/snd/controlC0: ubuntu 1404 F pulseaudio CurrentDesktop: Unity Date: Mon Jan 12 07:36:28 2015 HibernationDevice: RESUME=UUID=e24b803a-e217-4d6d-a35c-dbe0c033966a InstallationDate: Installed on 2015-01-08 (4 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP Licrice ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic root=UUID=c1e0a265-8c75-4427-ad25-f0c76f003ce7 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: 09/03/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M84 Ver. 97.35 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 221D dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 63.14 dmi.chassis.asset.tag: 73612P10CU dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrM84Ver.97.35:bd09/03/2014:svnHewlett-Packard:pnHPLicrice:pvrA3009CD10002:rvnHewlett-Packard:rn221D:rvrKBCVersion63.14:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Licrice dmi.product.version: A3009CD10002 dmi.sys.vendor: Hewlett-Packard --- ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1516 F pulseaudio /dev/snd/controlC1: ubuntu 1516 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=9864838c-7ba0-41b5-bd85-fe728504b659 InstallationDate: Installed on 2015-01-14 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP 430 G2 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic root=UUID=d4e5a7ff-0bd2-48a7-9d43-2defe1dcd58b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 RelatedPackageVersions: linux-restricted-modules-3.13.0-44-generic N/A linux-backports-modules-3.13.0-44-generic N/A linux-firmware 1.127.11 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.13.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/07/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M74 Ver. 01.03 dmi.board.name: 2246 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 67.22 dmi.chassis.asset.tag: 73612P10CU dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias:
[Kernel-packages] [Bug 1411535] [NEW] [Dell Precision M4800] No Unity 3D support on nVidia GK106GLM [10de:11fc] with open-source driver
Public bug reported: CID: 201305-13527 Dell Precision M4800 With Enable Switchable Graphics disabled in the BIOS, this system would use software rendering in Unity. ubuntu@201305-13527:~$ /usr/lib/nux/unity_support_test -c -p OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.4, 256 bits) OpenGL version string: 2.1 Mesa 10.1.3 Not software rendered:no Not blacklisted: yes GLX fbconfig: yes GLX texture from pixmap: yes GL npot or rect textures: yes Compiz supported: no But with that aforementioned option enabled, it won't have this issue. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-44-generic 3.13.0-44.73 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1439 F pulseaudio /dev/snd/controlC1: ubuntu 1439 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Fri Jan 16 02:21:07 2015 HibernationDevice: RESUME=UUID=4e3c0183-4d3f-495e-8d6a-57e2b23e6412 InstallationDate: Installed on 2015-01-16 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Dell Inc. Precision M4800 ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic root=UUID=3edd6366-27b1-41af-88d4-ac1abe216d8f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-44-generic N/A linux-backports-modules-3.13.0-44-generic N/A linux-firmware 1.127.11 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 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: 0FVDR2 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd12/03/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn0FVDR2:rvrX02:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: 201305-13527 amd64 apport-bug taipei-lab 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/1411535 Title: [Dell Precision M4800] No Unity 3D support on nVidia GK106GLM [10de:11fc] with open-source driver Status in linux package in Ubuntu: Confirmed Bug description: CID: 201305-13527 Dell Precision M4800 With Enable Switchable Graphics disabled in the BIOS, this system would use software rendering in Unity. ubuntu@201305-13527:~$ /usr/lib/nux/unity_support_test -c -p OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.4, 256 bits) OpenGL version string: 2.1 Mesa 10.1.3 Not software rendered:no Not blacklisted: yes GLX fbconfig: yes GLX texture from pixmap: yes GL npot or rect textures: yes Compiz supported: no But with that aforementioned option enabled, it won't have this issue. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-44-generic 3.13.0-44.73 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1439 F pulseaudio /dev/snd/controlC1: ubuntu 1439 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Fri Jan 16 02:21:07 2015 HibernationDevice: RESUME=UUID=4e3c0183-4d3f-495e-8d6a-57e2b23e6412 InstallationDate: Installed on 2015-01-16 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Dell Inc. Precision M4800 ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic root=UUID=3edd6366-27b1-41af-88d4-ac1abe216d8f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-44-generic N/A linux-backports-modules-3.13.0-44-generic N/A linux-firmware 1.127.11 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 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
[Kernel-packages] [Bug 1410668] Re: [Dell Latitude E5450] Touchpad is being recognized as ImPS/2 Generic Wheel Mouse
** Changed in: hwe-next Assignee: (unassigned) = Jesse Sung (wenchien) ** Changed in: linux (Ubuntu) Assignee: (unassigned) = Jesse Sung (wenchien) ** Changed in: hwe-next 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/1410668 Title: [Dell Latitude E5450] Touchpad is being recognized as ImPS/2 Generic Wheel Mouse Status in HWE Next Project: New Status in linux package in Ubuntu: Confirmed Bug description: In generally this touchpad works fine, however there is no touchpad related configuration shows in System Settings. And secondly, middle button with Point stick scrolling is not working. This touchpad got five individual buttons, each of them is working, however only scrolling by using point stick with middle button is not working. config like this: upper left | middle | upper right [ touchpad ] buttom left | buttom right There is a temproary workaround can enable the scrolling, with following command: $ xinput set-prop 14 Evdev Wheel Emulation 1 xinput set-prop 14 Evdev Wheel Emulation Button 2 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-44-generic 3.13.0-44.73 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1405 F pulseaudio /dev/snd/controlC1: ubuntu 1405 F pulseaudio CurrentDesktop: Unity Date: Wed Jan 14 02:03:58 2015 HibernationDevice: RESUME=UUID=a4551cd4-67b8-46e7-845a-89a9d9a45dec InstallationDate: Installed on 2015-01-12 (2 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Latitude E5450 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic root=UUID=a0369912-d393-4dc4-a0fa-aa83608a99b6 ro rootdelay=60 quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-44-generic N/A linux-backports-modules-3.13.0-44-generic N/A linux-firmware 1.127.11 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: 013BI5 dmi.board.vendor: Dell Inc. dmi.board.version: X03 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA00:bd08/06/2014:svnDellInc.:pnLatitudeE5450:pvr01:rvnDellInc.:rn013BI5:rvrX03:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5450 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1410668/+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 1409721] Re: [HP EliteBook 725 G2 Notebook PC] mic mute key (Fn+F8) does not work
HP ProBook 440 G2 Notebook PC CID: 201405-15063 could reproduce this issue. The attachment 201405-15063.apport.linux.log shows the log. ** Attachment added: 201405-15063.apport.linux.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1409721/+attachment/4299807/+files/201405-15063.apport.linux.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/1409721 Title: [HP EliteBook 725 G2 Notebook PC] mic mute key (Fn+F8) does not work Status in HWE Next Project: Triaged Status in linux package in Ubuntu: Confirmed Bug description: HP EliteBook 725 G2 Notebook PC (CID 201405-15214) updated ubuntu 14.04.1 3.13.0-43-generic #72 Steps to reproduce this bug: 1. install 14.04.1 and use the updater to update the system. Reboot. 2. Get into the desktop and ready to use the system. 3. sudo apt-get install sox 4. apply command 'sox -t alsa default tmp.wav' to record the sound. Press Fn F8 at the same time. 5. use 'ctrl+c' to stop recording. use 'play tmp.wav' to playback 6. during the playback, press the mute fhunction key. Expected result: of step 5. : The recorded sound was muted. The LED indicate the mic was muted. of step 6. : The speaker was muted and the mute LED indicate it was muted. Actual result: of step 5. : nothing happened. of step 6 : the sound was muted but the LED did not change color. More information: sudo hda-verb /dev/snd/hwC1D0 0x18 SET_PIN_WIDGET_CONTROL 0x20 could turn off the mic mute LED sudo hda-verb /dev/snd/hwC1D0 0x18 SET_PIN_WIDGET_CONTROL 0x24 could turn on the mic mute LED -- 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 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1404 F pulseaudio /dev/snd/controlC0: ubuntu 1404 F pulseaudio CurrentDesktop: Unity Date: Mon Jan 12 07:36:28 2015 HibernationDevice: RESUME=UUID=e24b803a-e217-4d6d-a35c-dbe0c033966a InstallationDate: Installed on 2015-01-08 (4 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP Licrice ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic root=UUID=c1e0a265-8c75-4427-ad25-f0c76f003ce7 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: 09/03/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M84 Ver. 97.35 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 221D dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 63.14 dmi.chassis.asset.tag: 73612P10CU dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrM84Ver.97.35:bd09/03/2014:svnHewlett-Packard:pnHPLicrice:pvrA3009CD10002:rvnHewlett-Packard:rn221D:rvrKBCVersion63.14:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Licrice dmi.product.version: A3009CD10002 dmi.sys.vendor: Hewlett-Packard --- ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1516 F pulseaudio /dev/snd/controlC1: ubuntu 1516 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=9864838c-7ba0-41b5-bd85-fe728504b659 InstallationDate: Installed on 2015-01-14 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP 430 G2 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic root=UUID=d4e5a7ff-0bd2-48a7-9d43-2defe1dcd58b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 RelatedPackageVersions: linux-restricted-modules-3.13.0-44-generic N/A linux-backports-modules-3.13.0-44-generic N/A linux-firmware 1.127.11 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.13.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/07/2014 dmi.bios.vendor: Hewlett-Packard
[Kernel-packages] [Bug 1410308] Re: [HP EliteBook 725 G2 Notebook PC] mic mute LED does not work.
HP ProBook 440 G2 Notebook PC CID: 201405-15063 could reproduce this issue. The attachment 201405-15063.apport.linux.log shows the log. ** Attachment added: 201405-15063.apport.linux.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1410308/+attachment/4299808/+files/201405-15063.apport.linux.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/1410308 Title: [HP EliteBook 725 G2 Notebook PC] mic mute LED does not work. Status in linux package in Ubuntu: Confirmed Bug description: The way to reproduce this bug and the basic debug information are at LP: #1409721 I separate LP: #1409721 to several bug reports because there are different failed features from the same system. --- ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2015-01-08 (5 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) Package: linux (not installed) Tags: trusty Uname: Linux 3.19.0-031900rc4-generic x86_64 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 _MarkForUpload: True --- ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2015-01-08 (5 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) Package: linux (not installed) Tags: trusty Uname: Linux 3.19.0-031900rc4-generic x86_64 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 _MarkForUpload: True --- ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1602 F pulseaudio /dev/snd/controlC0: ubuntu 1602 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=e24b803a-e217-4d6d-a35c-dbe0c033966a InstallationDate: Installed on 2015-01-08 (5 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP Licrice NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic root=UUID=c1e0a265-8c75-4427-ad25-f0c76f003ce7 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 RelatedPackageVersions: linux-restricted-modules-3.13.0-44-generic N/A linux-backports-modules-3.13.0-44-generic N/A linux-firmware 1.127.11 Tags: trusty Uname: Linux 3.13.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/03/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M84 Ver. 97.35 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 221D dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 63.14 dmi.chassis.asset.tag: 73612P10CU dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrM84Ver.97.35:bd09/03/2014:svnHewlett-Packard:pnHPLicrice:pvrA3009CD10002:rvnHewlett-Packard:rn221D:rvrKBCVersion63.14:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Licrice dmi.product.version: A3009CD10002 dmi.sys.vendor: Hewlett-Packard --- ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1516 F pulseaudio /dev/snd/controlC1: ubuntu 1516 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=9864838c-7ba0-41b5-bd85-fe728504b659 InstallationDate: Installed on 2015-01-14 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP 430 G2 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic root=UUID=d4e5a7ff-0bd2-48a7-9d43-2defe1dcd58b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 RelatedPackageVersions: linux-restricted-modules-3.13.0-44-generic N/A linux-backports-modules-3.13.0-44-generic N/A linux-firmware 1.127.11
[Kernel-packages] [Bug 1410309] Re: [HP EliteBook 725 G2 Notebook PC] mute LED does not work. it always keeps the same color (white).
HP ProBook 440 G2 Notebook PC CID: 201405-15063 could reproduce this issue. The attachment 201405-15063.apport.linux.log shows the log. ** Attachment added: 201405-15063.apport.linux.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1410309/+attachment/4299809/+files/201405-15063.apport.linux.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/1410309 Title: [HP EliteBook 725 G2 Notebook PC] mute LED does not work. it always keeps the same color (white). Status in linux package in Ubuntu: Won't Fix Bug description: The way to reproduce this bug and the basic debug information are at LP: #1409721 I separate LP: #1409721 to several bug reports because there are different failed features from the same system. --- ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1516 F pulseaudio /dev/snd/controlC1: ubuntu 1516 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=9864838c-7ba0-41b5-bd85-fe728504b659 InstallationDate: Installed on 2015-01-14 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP 430 G2 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic root=UUID=d4e5a7ff-0bd2-48a7-9d43-2defe1dcd58b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 RelatedPackageVersions: linux-restricted-modules-3.13.0-44-generic N/A linux-backports-modules-3.13.0-44-generic N/A linux-firmware 1.127.11 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.13.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/07/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M74 Ver. 01.03 dmi.board.name: 2246 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 67.22 dmi.chassis.asset.tag: 73612P10CU dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrM74Ver.01.03:bd07/07/2014:svnHewlett-Packard:pnHP430G2:pvrA3009C510002:rvnHewlett-Packard:rn2246:rvrKBCVersion67.22:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP 430 G2 dmi.product.version: A3009C510002 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1410309/+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 1410309] Re: [HP EliteBook 725 G2 Notebook PC] mute LED does not work. it always keeps the same color (white).
@Hui I could understand the pin quirk framework to make it hard to backport to linux-3.13. Is anyway for us to confirm the pin quirk configuration or this is also caused by the pin quirk framework? We have more and more systems have this issue If there is such a way, I may summarize these models of the machines so I could know they are Won't fix in a short time and avoid to duplicate to file bug reports. 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/1410309 Title: [HP EliteBook 725 G2 Notebook PC] mute LED does not work. it always keeps the same color (white). Status in linux package in Ubuntu: Won't Fix Bug description: The way to reproduce this bug and the basic debug information are at LP: #1409721 I separate LP: #1409721 to several bug reports because there are different failed features from the same system. --- ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1516 F pulseaudio /dev/snd/controlC1: ubuntu 1516 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=9864838c-7ba0-41b5-bd85-fe728504b659 InstallationDate: Installed on 2015-01-14 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP 430 G2 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic root=UUID=d4e5a7ff-0bd2-48a7-9d43-2defe1dcd58b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 RelatedPackageVersions: linux-restricted-modules-3.13.0-44-generic N/A linux-backports-modules-3.13.0-44-generic N/A linux-firmware 1.127.11 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.13.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/07/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M74 Ver. 01.03 dmi.board.name: 2246 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 67.22 dmi.chassis.asset.tag: 73612P10CU dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrM74Ver.01.03:bd07/07/2014:svnHewlett-Packard:pnHP430G2:pvrA3009C510002:rvnHewlett-Packard:rn2246:rvrKBCVersion67.22:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP 430 G2 dmi.product.version: A3009C510002 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1410309/+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 1410908] Re: linux-ti-omap4: 3.2.0-1459.79 -proposed tracker
** Changed in: kernel-sru-workflow/upload-to-ppa Status: New = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1410908 Title: linux-ti-omap4: 3.2.0-1459.79 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Confirmed Status in Kernel SRU Workflow verification-testing series: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-ti-omap4 source package in Precise: New Bug description: This bug is for tracking the version to be filled 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-stable-Prepare-package-start:Wednesday, 14. January 2015 18:01 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Wednesday, 14. January 2015 18:01 UTC kernel-stable-master-bug:1410459 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1410908/+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 1317811] Re: Dropped packets on EC2, xen_netfront: xennet: skb rides the rocket: x slots
Not surprising as we held back for Trusty and Utopic after being told that there was a regression. And as the task status show this only became fixed in current development (Vivid). But Now that both parts are there it is time to get back to stable. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1317811 Title: Dropped packets on EC2, xen_netfront: xennet: skb rides the rocket: x slots Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Confirmed Status in linux source package in Utopic: Confirmed Bug description: Running Ubuntu 14.04 LTS on EC2, we see a lot of the following in the kernel log: xen_netfront: xennet: skb rides the rocket: 19 slots Each of these messages corresponds to a dropped TX packet, and eventually causes our application's connections to break and timeout. The problem appears when network load increases. We have Node.js processes doing pubsub with a Redis server, and these are most visibly affected, showing frequent connection loss. The processes talk to each other using the private addresses EC2 allocates to the machines. Notably, the default MTU on the network interface seems to have gone up from 1500 on 13.10, to 9000 in 14.04 LTS. Reducing the MTU back to 1500 seems to drastically reduce dropped packets. (Can't say for certain if it completely eliminates the problem.) The machines we run are started from ami-896c96fe. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: User Name 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 9 09:01 seq crw-rw 1 root audio 116, 33 May 9 09:01 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Fri May 9 09:11:18 2014 Ec2AMI: ami-896c96fe Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1c Ec2InstanceType: c3.large Ec2Kernel: aki-52a34525 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 9 09:54 seq crw-rw 1 root audio 116, 33 May 9 09:54 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 24.724129] init: plymouth-upstart-bridge main process ended, respawning DistroRelease: Ubuntu 14.04 Ec2AMI: ami-896c96fe Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1c Ec2InstanceType: c3.large Ec2Kernel: aki-52a34525 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 ProcVersionSignature: User Name 3.13.0-24.46-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video _MarkForUpload: True break-fix: - 97a6d1bb2b658ac85ed88205ccd1ab809899884d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1317811/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1411438] [NEW] virtualbox-guest-dkms 4.3.10-dfsg-1: virtualbox-guest kernel module failed to build [/bin/sh: 1: scripts/genksyms/genksyms: Permission denied]
You have been subscribed to a public bug: np ProblemType: Package DistroRelease: Ubuntu 14.04 Package: virtualbox-guest-dkms 4.3.10-dfsg-1 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic i686 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 DKMSKernelVersion: 3.13.0-44-generic Date: Thu Jan 15 23:17:33 2015 InstallationDate: Installed on 2015-01-05 (10 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release i386 (20140416.1) PackageArchitecture: all PackageVersion: 4.3.10-dfsg-1 SourcePackage: virtualbox Title: virtualbox-guest-dkms 4.3.10-dfsg-1: virtualbox-guest kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) VirtualBox.ModInfo: ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 trusty -- virtualbox-guest-dkms 4.3.10-dfsg-1: virtualbox-guest kernel module failed to build [/bin/sh: 1: scripts/genksyms/genksyms: Permission denied] https://bugs.launchpad.net/bugs/1411438 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta 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 1407913] Re: In 3840x2160 high resolution mode, display would blink with Chrome / Chromium browser opened, or with certain page in Firefox
Thanks for the testing. I think nothing HWE can do right now. Pending on upstream fix. -- You 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: Confirmed 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 1411438] Re: virtualbox-guest-dkms 4.3.10-dfsg-1: virtualbox-guest kernel module failed to build [/bin/sh: 1: scripts/genksyms/genksyms: Permission denied]
this is a kernel issue, at least that genksyms belongs to linux-headers. Reassigning ** Package changed: virtualbox (Ubuntu) = linux-meta (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1411438 Title: virtualbox-guest-dkms 4.3.10-dfsg-1: virtualbox-guest kernel module failed to build [/bin/sh: 1: scripts/genksyms/genksyms: Permission denied] Status in linux package in Ubuntu: New Bug description: np ProblemType: Package DistroRelease: Ubuntu 14.04 Package: virtualbox-guest-dkms 4.3.10-dfsg-1 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic i686 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 DKMSKernelVersion: 3.13.0-44-generic Date: Thu Jan 15 23:17:33 2015 InstallationDate: Installed on 2015-01-05 (10 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release i386 (20140416.1) PackageArchitecture: all PackageVersion: 4.3.10-dfsg-1 SourcePackage: virtualbox Title: virtualbox-guest-dkms 4.3.10-dfsg-1: virtualbox-guest kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) VirtualBox.ModInfo: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1411438/+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 1411438] Re: virtualbox-guest-dkms 4.3.10-dfsg-1: virtualbox-guest kernel module failed to build [/bin/sh: 1: scripts/genksyms/genksyms: Permission denied]
** Package changed: linux-meta (Ubuntu) = linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1411438 Title: virtualbox-guest-dkms 4.3.10-dfsg-1: virtualbox-guest kernel module failed to build [/bin/sh: 1: scripts/genksyms/genksyms: Permission denied] Status in linux package in Ubuntu: New Bug description: np ProblemType: Package DistroRelease: Ubuntu 14.04 Package: virtualbox-guest-dkms 4.3.10-dfsg-1 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic i686 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 DKMSKernelVersion: 3.13.0-44-generic Date: Thu Jan 15 23:17:33 2015 InstallationDate: Installed on 2015-01-05 (10 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release i386 (20140416.1) PackageArchitecture: all PackageVersion: 4.3.10-dfsg-1 SourcePackage: virtualbox Title: virtualbox-guest-dkms 4.3.10-dfsg-1: virtualbox-guest kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) VirtualBox.ModInfo: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1411438/+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 1410908] Re: linux-ti-omap4: 3.2.0-1459.79 -proposed tracker
** Description changed: This bug is for tracking the version to be filled 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-stable-Prepare-package-start:Wednesday, 14. January 2015 18:01 UTC - kernel-stable-phase:Prepare - kernel-stable-phase-changed:Wednesday, 14. January 2015 18:01 UTC kernel-stable-master-bug:1410459 + kernel-stable-phase:ReadyToBePackaged + kernel-stable-phase-changed:Friday, 16. January 2015 09:01 UTC + kernel-stable-Certification-testing-end:Friday, 16. January 2015 09:01 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1410908 Title: linux-ti-omap4: 3.2.0-1459.79 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Confirmed Status in Kernel SRU Workflow verification-testing series: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-ti-omap4 source package in Precise: New Bug description: This bug is for tracking the version to be filled 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-stable-Prepare-package-start:Wednesday, 14. January 2015 18:01 UTC kernel-stable-master-bug:1410459 kernel-stable-phase:ReadyToBePackaged kernel-stable-phase-changed:Friday, 16. January 2015 09:01 UTC kernel-stable-Certification-testing-end:Friday, 16. January 2015 09:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1410908/+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 1354313] Re: [Dell Inspiron 5721] Brightness control does not work with 12.04.5(with kernel 3.13)
** Changed in: hwe-next Status: Triaged = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1354313 Title: [Dell Inspiron 5721] Brightness control does not work with 12.04.5(with kernel 3.13) Status in HWE Next Project: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-lts-trusty source package in Trusty: Invalid Status in linux source package in Utopic: Invalid Status in linux-lts-trusty source package in Utopic: Invalid Bug description: This is a system installed with latest stable 12.04.5 image. The Brightness key will invoke the osd-notify indicator but the display brightness won't change. Verifying the value changing in backlight interface, system are using acpi_video0 instead: Steps to monitor the backlight interfaces: Press the brightness key until maxium indicator shows: ubuntu@201210-11863:/sys/class/backlight$ cat intel_backlight/brightness ; cat acpi_video0/brightness 3407 99 ubuntu@201210-11863:/sys/class/backlight$ Press the brightness key until to minimum indicator shows: ubuntu@201210-11863:/sys/class/backlight$ cat intel_backlight/brightness ; cat acpi_video0/brightness 3407 0 - The workaround found here could solve this issue: http://itsfoss.com/fix-brightness-ubuntu-1310/ - Verified with other kernels: linux-image-generic 3.2.0.67.79 = brightness control works linux-image-generic-lts-quantal 3.5.0.54.59 = brightness control works There is possible regression in following kernels: linux-image-generic-lts-raring 3.8.0.44.44 = brightness control not work linux-image-generic-lts-saucy 3.11.0.26.23 = brightness control not work - ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Fri Aug 8 03:51:43 2014 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms, 14.07.00, 3.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes, even including gdb or git bisection work if needed GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05ba] Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] [1002:6601] (rev ff) (prog-if ff) InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) MachineType: Dell Inc. Inspiron 5721 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=93a24f68-72a1-4335-938a-75f624f57e68 ro quiet splash initcall_debug vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0KNF68 dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd10/25/2013:svnDellInc.:pnInspiron5721:pvrA12:rvnDellInc.:rn0KNF68:rvrX01:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron 5721 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.7.12-0ubuntu4 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1~precise1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1354313/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1408295] Re: Enable mic mute hotkey and LEDs for an HP machine
** Changed in: hwe-next Status: New = Fix Committed ** Changed in: hwe-next Assignee: (unassigned) = David Henningsson (diwic) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1408295 Title: Enable mic mute hotkey and LEDs for an HP machine Status in HWE Next Project: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: This bug is used for tracking only, please do not triage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1408295/+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 1408222] Re: Intel 7265 8086:5412 isn't listed in the driver
** Also affects: hwe-next/trusty Importance: Undecided Status: New ** Changed in: hwe-next/trusty Status: New = Fix Committed ** Changed in: hwe-next Status: New = Fix Released ** Changed in: hwe-next Assignee: (unassigned) = AceLan Kao (acelankao) ** Changed in: hwe-next/trusty Assignee: (unassigned) = AceLan Kao (acelankao) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1408222 Title: Intel 7265 8086:5412 isn't listed in the driver Status in HWE Next Project: Fix Released Status in HWE Next trusty series: Fix Committed Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: Fix Committed Bug description: The wifi doesn't work if the id is not listed in the iwlwifi driver To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1408222/+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 1401466] Re: [Dell Inspiron 2350] fwts high failure:method: Detected error 'No return value' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS10._UPC'.
** Changed in: hwe-next Importance: Undecided = Low ** Changed in: hwe-next Assignee: (unassigned) = Ivan Hu (ivan.hu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1401466 Title: [Dell Inspiron 2350] fwts high failure:method: Detected error 'No return value' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS10._UPC'. Status in HWE Next Project: New Status in linux package in Ubuntu: Incomplete Bug description: Dell Inspiron 2350 (CID 201305-13669) with Ubuntu 14.04.1 Linux 201305-13669 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux The following fwts high failure was found: method: Detected error 'No return value' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS10._UPC'. method: Detected error 'No return value' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS11._UPC'. method: Detected error 'No return value' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS12._UPC'. method: Detected error 'No return value' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS13._UPC'. method: Detected error 'No return value' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS14._UPC'. method: Detected error 'No return value' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS15._UPC'. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1476 F pulseaudio /dev/snd/controlC1: ubuntu 1476 F pulseaudio CurrentDesktop: Unity CurrentDmesg: [ 15.148179] thinkpad_ec: no ThinkPad embedded controller! [ 17.013792] init: plymouth-upstart-bridge main process ended, respawning [ 17.021574] init: plymouth-upstart-bridge main process ended, respawning [ 17.969005] r8169 :03:00.0 eth0: link up [ 17.969013] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=a6237ffe-4fa9-4ab7-9253-55430263f86f InstallationDate: Installed on 2014-12-08 (2 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Inspiron 2350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=fe7cefb8-002c-4091-9a6e-6cab455727b5 ro rootdelay=60 quiet splash initcall_debug vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/02/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 08NG84 dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 00 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd09/02/2013:svnDellInc.:pnInspiron2350:pvr00:rvnDellInc.:rn08NG84:rvrX01:cvnDellInc.:ct13:cvr00: dmi.product.name: Inspiron 2350 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1401466/+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 1400365] Re: Intel PRO/1000 network driver e1000e doesn't always regain connection
** Changed in: hwe-next Status: Triaged = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1400365 Title: Intel PRO/1000 network driver e1000e doesn't always regain connection Status in HWE Next Project: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Trusty: Fix Committed Bug description: On our Dell E6440 laptops we found that the Wired network connection is sometimes not re-established when going from Wifi back to Ethernet, e.g. when booting without LAN and then putting the laptop back in its dock. The following upstream patch resolved this problem for us in Kubuntu 14.04 LTS kernels 3.13.0-34-generic and 3.13.0-40-generic: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/drivers/net/ethernet/intel/e1000e?id=b20a774495671f037e7160ea2ce8789af6b61533 Please incorporate this patch in the Kubuntu kernel so that the /lib/modules/3.13.0-XX- generic/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko module doesn't have to rebuilt manually every time we follow a kernel update. Thanks. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-40-generic 3.13.0-40.69 [modified: lib/modules/3.13.0-40-generic/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko] ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: homa 2299 F pulseaudio homa 2573 F pulseaudio /dev/snd/controlC0: homa 2299 F pulseaudio homa 2573 F pulseaudio CurrentDesktop: KDE Date: Mon Dec 8 16:22:48 2014 HibernationDevice: RESUME=UUID=df0741f0-a429-48cf-9eaf-0b9a31bb32ea InstallationDate: Installed on 2014-12-05 (3 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.1) MachineType: Dell Inc. Latitude E6440 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic root=UUID=63b4f79f-bbff-4166-9be1-3adf4ea9708b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-40-generic N/A linux-backports-modules-3.13.0-40-generic N/A linux-firmware 1.127.10 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0YX2X3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd02/18/2014:svnDellInc.:pnLatitudeE6440:pvr01:rvnDellInc.:rn0YX2X3:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1400365/+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 1397285] Re: O2 Micron cardreader [1217:8621] could not read mmc cards
** Changed in: hwe-next Assignee: (unassigned) = Adam Lee (adam8157) ** Changed in: hwe-next Importance: Undecided = Medium ** Changed in: linux (Ubuntu) Assignee: (unassigned) = Adam Lee (adam8157) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1397285 Title: O2 Micro cardreader [1217:8621] could not read mmc cards Status in HWE Next Project: New Status in linux package in Ubuntu: Incomplete Bug description: Dell Inspiron 3048 (CID 201401-14493) on Ubuntu 14.04.1 Steps to reproduce the bug: 1. boot the system, login and wait for the desktop ready to use 2. plugin mmc card Expected result: mmc directory will pop up and ready to use it. Actual result: no thing pop up on desktop --- dmesg -- [ 41.180392] mmc0: Got data interrupt 0x0200 even though no data operation was in progress. [ 51.210537] mmc0: Timeout waiting for hardware interrupt. [ 51.212627] mmc0: Got data interrupt 0x0200 even though no data operation was in progress. [ 61.229658] mmc0: Timeout waiting for hardware interrupt. [ 61.231738] mmc0: Got data interrupt 0x0200 even though no data operation was in progress. [ 71.248714] mmc0: Timeout waiting for hardware interrupt. [ 71.250815] mmc0: Got data interrupt 0x0200 even though no data operation was in progress. [ 81.267947] mmc0: Timeout waiting for hardware interrupt. [ 81.270026] mmc0: error -110 whilst initialising MMC card [ 81.377041] mmc0: Got data interrupt 0x0200 even though no data operation was in progress. [ 86.065388] mmc0: Card removed during transfer! [ 86.065398] mmc0: Resetting controller. [ 86.065544] mmc0: error -123 whilst initialising MMC card ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 [modified: boot/vmlinuz-3.13.0-32-generic] ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1447 F pulseaudio /dev/snd/controlC1: ubuntu 1447 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 28 05:20:43 2014 HibernationDevice: RESUME=UUID=265f8dc9-0dff-4a1b-9a3b-08fb662a7daf InstallationDate: Installed on 2014-11-26 (2 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Inspiron 20 Model 3048 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=f35024ba-c412-4316-8474-bd2a586c6c1b ro rootdelay=60 quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: X19 dmi.board.name: 0HD5K4 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrX19:bd12/18/2013:svnDellInc.:pnInspiron20Model3048:pvr01:rvnDellInc.:rn0HD5K4:rvrX02:cvnDellInc.:ct13:cvr: dmi.product.name: Inspiron 20 Model 3048 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1397285/+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 1381906] Re: [Dell Latitude E5550] Atheros Bluetooth [0cf3:e005] gone after suspend
** Changed in: hwe-next Assignee: (unassigned) = Adam Lee (adam8157) ** Changed in: linux (Ubuntu) Assignee: Anthony Wong (anthonywong) = Adam Lee (adam8157) ** Changed in: hwe-next 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/1381906 Title: [Dell Latitude E5550] Atheros Bluetooth [0cf3:e005] gone after suspend Status in HWE Next Project: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: CID: 201406-15271 Dell Latitude E5550 After S3, the Bluetooth indicator will grey out (stays at the OFF state), but rfkill show it's not blocked. Even enable it by changing it to the ON state does not help, can't find any device with it, hciconfig return nothing. Error message could be found in the dmesg output: [ 8996.779551] Bluetooth: Error in firmware loading err = -110,len = 448, size = 1906 [ 8996.779570] Bluetooth: Loading sysconfig file failed More important part is that after reboot, the Bluetooth will disappear as it never exist, won't be listed in lsusb and dmesg. 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.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1726 F pulseaudio /dev/snd/controlC1: ubuntu 1726 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Thu Oct 16 00:41:31 2014 HibernationDevice: RESUME=UUID=02cbc1f1-a261-484c-8fc2-05b68f73446d InstallationDate: Installed on 2014-10-09 (6 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Latitude E5550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=d3b20ae5-9ff8-49b3-b640-1c6a9f264710 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.7 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: T43 dmi.board.name: 0141B2 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrT43:bd07/25/2014:svnDellInc.:pnLatitudeE5550:pvr01:rvnDellInc.:rn0141B2:rvrX02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5550 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1381906/+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 1387128] Re: Need quirk for headphones to work on a few HP machines
** Changed in: hwe-next Status: New = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1387128 Title: Need quirk for headphones to work on a few HP machines Status in HWE Next Project: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: This bug is for tracking purposes only. Please do not triage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1387128/+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 1404173] Re: [Dell Inspiron 7537] HIGH failures found in FWTS klog report
** Changed in: hwe-next Importance: Undecided = Low ** Changed in: hwe-next Assignee: (unassigned) = Ivan Hu (ivan.hu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1404173 Title: [Dell Inspiron 7537] HIGH failures found in FWTS klog report Status in HWE Next Project: New Status in linux package in Ubuntu: Confirmed Bug description: CID: 201306-13868 Dell Inspiron 7537 There are four high failure reported in the klog log: High failures: 4 klog: HIGH Kernel message: [0.00] ACPI Error: Gpe0Block - 32-bit FADT register is too long (32 bytes, 256 bits) to convert to GAS struct - 255 bits max, truncating (20131115/tbfadt-202) I think this one was confirmed not a blocker in bug 1363775 klog: HIGH Kernel message: [0.257172] \_SB_.PCI0:_OSC invalid UUID I think this one was confirmed not a blocker in bug 1279169 klog: HIGH Kernel message: [7.099033] ACPI Exception: AE_NOT_FOUND, Evaluating _DOD (20131115/video-1278) klog: HIGH Kernel message: [ 10.653041] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95) 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 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1750 F pulseaudio /dev/snd/controlC1: ubuntu 1750 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Fri Dec 19 04:52:02 2014 HibernationDevice: RESUME=UUID=1037e06d-3f36-4dbc-a80a-31400fcf4165 InstallationDate: Installed on 2014-12-17 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 7537 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic root=UUID=8ffaa535-6ef2-4aa6-b934-cb06b23881b9 ro quiet splash 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: 12/10/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: C35 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrC35:bd12/10/2013:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Inspiron 7537 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1404173/+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 1397285] Re: O2 Micro cardreader [1217:8621] could not read mmc cards
** Summary changed: - O2 Micron cardreader [1217:8621] could not read mmc cards + O2 Micro cardreader [1217:8621] could not read mmc cards -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1397285 Title: O2 Micro cardreader [1217:8621] could not read mmc cards Status in HWE Next Project: New Status in linux package in Ubuntu: Incomplete Bug description: Dell Inspiron 3048 (CID 201401-14493) on Ubuntu 14.04.1 Steps to reproduce the bug: 1. boot the system, login and wait for the desktop ready to use 2. plugin mmc card Expected result: mmc directory will pop up and ready to use it. Actual result: no thing pop up on desktop --- dmesg -- [ 41.180392] mmc0: Got data interrupt 0x0200 even though no data operation was in progress. [ 51.210537] mmc0: Timeout waiting for hardware interrupt. [ 51.212627] mmc0: Got data interrupt 0x0200 even though no data operation was in progress. [ 61.229658] mmc0: Timeout waiting for hardware interrupt. [ 61.231738] mmc0: Got data interrupt 0x0200 even though no data operation was in progress. [ 71.248714] mmc0: Timeout waiting for hardware interrupt. [ 71.250815] mmc0: Got data interrupt 0x0200 even though no data operation was in progress. [ 81.267947] mmc0: Timeout waiting for hardware interrupt. [ 81.270026] mmc0: error -110 whilst initialising MMC card [ 81.377041] mmc0: Got data interrupt 0x0200 even though no data operation was in progress. [ 86.065388] mmc0: Card removed during transfer! [ 86.065398] mmc0: Resetting controller. [ 86.065544] mmc0: error -123 whilst initialising MMC card ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 [modified: boot/vmlinuz-3.13.0-32-generic] ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1447 F pulseaudio /dev/snd/controlC1: ubuntu 1447 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 28 05:20:43 2014 HibernationDevice: RESUME=UUID=265f8dc9-0dff-4a1b-9a3b-08fb662a7daf InstallationDate: Installed on 2014-11-26 (2 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Inspiron 20 Model 3048 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=f35024ba-c412-4316-8474-bd2a586c6c1b ro rootdelay=60 quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: X19 dmi.board.name: 0HD5K4 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrX19:bd12/18/2013:svnDellInc.:pnInspiron20Model3048:pvr01:rvnDellInc.:rn0HD5K4:rvrX02:cvnDellInc.:ct13:cvr: dmi.product.name: Inspiron 20 Model 3048 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1397285/+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 1369633] Re: 4k laptop eDP display not working on newer laptops
** Changed in: hwe-next Status: New = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1369633 Title: 4k laptop eDP display not working on newer laptops Status in HWE Next Project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Released Bug description: Impact: Some new laptops with 4k screens are starting to use dp 1.2 only feature of supporting 5.4ghz link rates over displayport which was not turned on until 3.15 even though the plumbing for it was (mostly) there. This should only make more devices work since it has to advertise support for the feature in the dpcd. previously dp 1.2 screens which needed 5.4ghz link rates were forced to use 2.7ghz instead, which would not provide enough bandwidth for some high resolution/high bandwidth screens. It only affects haswell for trusty, broadwell is handled through i915_bdw module which already as this fix and the fix was upstream in 3.15-rc1 so utopic is unaffected. Fix: Allow the 5.4ghz link rate over displayport. This has been tested on an affected OEM laptop with a 4K display that requires 5.4ghz link rate to light up (without it the display never turns on) as well as 2 other haswell machines to be sure it doesn't regress. [ 5.297037] [drm:intel_modeset_stage_output_state] [CONNECTOR:16:eDP-1] to [CRTC:5] [ 5.297038] [drm:intel_modeset_affected_pipes] set mode pipe masks: modeset: 1, prepare: 1, disable: 0 [ 5.297040] [drm:connected_sink_compute_bpp] [CONNECTOR:16:eDP-1] checking for sink bpp constrains [ 5.297042] [drm:intel_dp_compute_config] DP link computation with max lane count 4 max bw 14 pixel clock 533250KHz [ 5.297045] [drm:intel_dp_compute_config] DP link bw 14 lane count 4 clock 54 bpp 24 [ 5.297046] [drm:intel_dp_compute_config] DP link bw required 1279800 available 1728000 [ 5.297047] [drm:intel_modeset_pipe_config] plane bpp: 24, pipe bpp: 24, dithering: 0 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1369633/+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 1381851] Re: [Dell Latitude E5550] Brightness control does not work on this system
** Changed in: hwe-next Importance: Undecided = Medium ** Changed in: hwe-next Assignee: (unassigned) = AceLan Kao (acelankao) ** Changed in: linux (Ubuntu) Assignee: (unassigned) = AceLan Kao (acelankao) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1381851 Title: [Dell Latitude E5550] Brightness control does not work on this system Status in HWE Next Project: Triaged Status in linux package in Ubuntu: Triaged Bug description: CID: 201406-15271 Dell Latitude E5550 Brightness control does not work on this system The brightness level indicator would change with hotkey events, but the brightness itself does not. Debugging information: ubuntu@201406-15271:~$ ls /sys/class/backlight acpi_video0 intel_backlight ubuntu@201406-15271:~$ 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: discharging /proc/acpi/battery/BAT0/state:present rate:772 mA /proc/acpi/battery/BAT0/state:remaining capacity: 3170 mAh /proc/acpi/battery/BAT0/state:present voltage: 12493 mV /proc/acpi/battery/BAT0/info:present: yes /proc/acpi/battery/BAT0/info:design capacity: 3540 mAh /proc/acpi/battery/BAT0/info:last full capacity: 3372 mAh /proc/acpi/battery/BAT0/info:battery technology: rechargeable /proc/acpi/battery/BAT0/info:design voltage: 11100 mV /proc/acpi/battery/BAT0/info:design capacity warning: 354 mAh /proc/acpi/battery/BAT0/info:design capacity low: 107 mAh /proc/acpi/battery/BAT0/info:cycle count: 0 /proc/acpi/battery/BAT0/info:capacity granularity 1: 35 mAh /proc/acpi/battery/BAT0/info:capacity granularity 2: 35 mAh /proc/acpi/battery/BAT0/info:model number:DELL 9P4D246 /proc/acpi/battery/BAT0/info:serial number: 226 /proc/acpi/battery/BAT0/info:battery type:LiP /proc/acpi/battery/BAT0/info:OEM info:LGC-LGC3.4 /proc/acpi/button/lid/LID0/state:state: open /proc/acpi/ac_adapter/AC/state:state: off-line /proc/acpi/wakeup:Device S-state Status Sysfs node /proc/acpi/wakeup:PEG0 S4*disabled /proc/acpi/wakeup:PEGP S4*disabled /proc/acpi/wakeup:PEG1 S4*disabled /proc/acpi/wakeup:PEGP S4*disabled /proc/acpi/wakeup:PEG2 S4*disabled /proc/acpi/wakeup:PEGP S4*disabled /proc/acpi/wakeup:RP01 S4*disabled pci::00:1c.0 /proc/acpi/wakeup:PXSX S4*disabled pci::01:00.0 /proc/acpi/wakeup:RP02 S4*disabled /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:RP03 S4*disabled /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:RP04 S4*disabled pci::00:1c.3 /proc/acpi/wakeup:PXSX S4*disabled pci::02:00.0 /proc/acpi/wakeup:RP05 S4*disabled pci::00:1c.4 /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:RP06 S4*disabled /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:RP07 S4*disabled /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:RP08 S4*disabled /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:GLAN S4*disabled pci::00:19.0 /proc/acpi/wakeup:EHC1 S0*enabled pci::00:1d.0 /proc/acpi/wakeup:EHC2 S0*disabled /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 /proc/acpi/wakeup:PBTN S3*enabled ubuntu@201406-15271:~$ dmesg | grep 'ACPI: Video' [ 12.986933] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) ubuntu@201406-15271:~$ 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.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1530 F pulseaudio /dev/snd/controlC1: ubuntu 1530 F pulseaudio CurrentDesktop: Unity Date: Wed Oct 15 23:03:45 2014 HibernationDevice: RESUME=UUID=02cbc1f1-a261-484c-8fc2-05b68f73446d InstallationDate: Installed on 2014-10-09 (6 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Latitude E5550 ProcFB: 0 inteldrmfb ProcKernelCmdLine:
[Kernel-packages] [Bug 1364784] Re: [Lenovo ThinkPad T440p] hybrid sleep didn't sleep
** Changed in: hwe-next Status: New = Incomplete ** Changed in: hwe-next 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/1364784 Title: [Lenovo ThinkPad T440p] hybrid sleep didn't sleep Status in HWE Next Project: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Lenovo ThinkPad T440p ( CID 201309-14169 ) on Ubuntu 14.04 3.13.0-24-generic --- use the command to ask the system to hybrid sleep sudo fwts -q --stdout-summary -r hybrid_sleep_single --s3-hybrid --s3 -sleep-delay 30 --s3-device-check --s3-device-check-delay 45 s3 and the system didn't went to sleep. Only the screen is black and nothing happened. --- More information: this system has an discrete nvidia graphic card [10de:1290] but this issue happened under performance mode and power-saving mode both. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1712 F pulseaudio /dev/snd/controlC1: ubuntu 1712 F pulseaudio CurrentDesktop: Unity Date: Wed Sep 3 02:39:30 2014 HibernationDevice: RESUME=UUID=b437ec5c-4a11-4108-a4b7-900f2ea9f312 InstallationDate: Installed on 2014-08-27 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: LENOVO 20ANZ03CUS ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=cb520008-8859-45fa-b8dd-d66a667b1be2 ro rootdelay=60 quiet splash initcall_debug RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2013 dmi.bios.vendor: LENOVO dmi.bios.version: GLET34WW (1.09.T05 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ANZ03CUS dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET34WW(1.09.T05):bd08/20/2013:svnLENOVO:pn20ANZ03CUS:pvrThinkPadT440p:rvnLENOVO:rn20ANZ03CUS:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20ANZ03CUS dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1364784/+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 1330893] Re: [HP 110 Desktop] Power LED won't blink or change color during suspend
** Changed in: hwe-next Assignee: (unassigned) = Jesse Sung (wenchien) ** Changed in: hwe-next 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/1330893 Title: [HP 110 Desktop] Power LED won't blink or change color during suspend Status in HWE Next Project: New Status in linux package in Ubuntu: Confirmed Bug description: CID: 201301-12636 HP 110 Desktop The power LED on this system won't blink or change color when it's suspended. And it seems that we don't have this kind of test during the pre- install certification stage of it, I am not sure if this will happen to Precise or not, will update the bug report later. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1457 F pulseaudio CurrentDesktop: Unity Date: Tue Jun 17 05:09:10 2014 HibernationDevice: RESUME=UUID=59db6909-073e-4037-a30a-1a573bdff093 InstallationDate: Installed on 2014-06-16 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard TEST ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=2baadb9d-3d7f-4cc2-8448-6bf2a8d52379 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2013 dmi.bios.vendor: AMI dmi.bios.version: 8.17G dmi.board.name: 2B01 dmi.board.vendor: Hewlett-Packard dmi.board.version: 1.02 dmi.chassis.asset.tag: RDW3010022 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr8.17G:bd03/18/2013:svnHewlett-Packard:pnTEST:pvr:rvnHewlett-Packard:rn2B01:rvr1.02:cvnHewlett-Packard:ct3:cvr: dmi.product.name: TEST dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1330893/+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 1411438] 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/1411438 Title: virtualbox-guest-dkms 4.3.10-dfsg-1: virtualbox-guest kernel module failed to build [/bin/sh: 1: scripts/genksyms/genksyms: Permission denied] Status in linux package in Ubuntu: Confirmed Bug description: np ProblemType: Package DistroRelease: Ubuntu 14.04 Package: virtualbox-guest-dkms 4.3.10-dfsg-1 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic i686 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 DKMSKernelVersion: 3.13.0-44-generic Date: Thu Jan 15 23:17:33 2015 InstallationDate: Installed on 2015-01-05 (10 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release i386 (20140416.1) PackageArchitecture: all PackageVersion: 4.3.10-dfsg-1 SourcePackage: virtualbox Title: virtualbox-guest-dkms 4.3.10-dfsg-1: virtualbox-guest kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) VirtualBox.ModInfo: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1411438/+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 1152539] Re: 8086:0162 [HP Envy 23 AIO] HDMI Out does not work
Are we sure the port is HDMI OUT or HDMI IN? Because from
http://h10025.www1.hp.com/ewfrf/wc/document?docname=c04092080cc=usdlc=enlc=en
it mentions only HDMI IN, not sure if it is the same model though.
** Changed in: hwe-next
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/1152539
Title:
8086:0162 [HP Envy 23 AIO] HDMI Out does not work
Status in HWE Next Project:
Incomplete
Status in linux package in Ubuntu:
Confirmed
Bug description:
This system has an HDMI jack and buttons that should switch the jack
from output to input. According to the QA engineers, these keys are
not enabled on Ubuntu, so the jack should just function as an HDMI
output as expected.
With 12.04.2, this does not work, however.
On plugging an HDMI monitor into the jack, the monitor status light
goes from orange (standby) to green (active), but then falls back to
Orange. The display never wakes and on the AIO, you don't see the
desktop flash or re-draw as it often does when adding an external
display and the desktop has to stretch.
I tried several times and could not get the HDMI output to work on
this system.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.5.0-23-generic 3.5.0-23.35~precise1
ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2
Uname: Linux 3.5.0-23-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1708 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xf7c0 irq 51'
Mixer name : 'IDT 92HD91BXX'
Components : 'HDA:111d76e0,103c2adc,00100102'
Controls : 18
Simple ctrls : 9
Date: Fri Mar 8 04:37:22 2013
HibernationDevice: RESUME=UUID=5a0be338-b72f-4759-947d-2c799a9951e2
InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64
(20130213)
MachineType: Hewlett-Packard 520-1299
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic
root=UUID=759df16a-1f46-4f4e-b7b7-bff65b4d6bec ro quiet splash initcall_debug
vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.5.0-23-generic N/A
linux-backports-modules-3.5.0-23-generic N/A
linux-firmware1.79.1
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
StagingDrivers: rts_pstor
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/25/2012
dmi.bios.vendor: AMI
dmi.bios.version: 8.10
dmi.board.asset.tag: 3CR2080BJX
dmi.board.name: 2ADC
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 1.05
dmi.chassis.asset.tag: 3CR2080BJX
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias:
dmi:bvnAMI:bvr8.10:bd09/25/2012:svnHewlett-Packard:pn520-1299:pvr1.00:rvnPEGATRONCORPORATION:rn2ADC:rvr1.05:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: 520-1299
dmi.product.version: 1.00
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1152539/+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 1085751] Re: [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -35!
** No longer affects: hwe-next -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1085751 Title: [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -35! Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-ati package in Ubuntu: Fix Released Status in linux source package in Precise: Incomplete Status in xserver-xorg-video-ati source package in Precise: Confirmed Status in linux source package in Quantal: Won't Fix Status in xserver-xorg-video-ati source package in Quantal: Won't Fix Status in Fedora: Confirmed Bug description: This is on a machine upgraded from Quantal to Raring. I switched between two users, and then switched back under KDE and managed to trigger that Failed to parse relocation. It happened (and the screen went blank) at the moment I clicked the 'activate' button on the screen saver to switch back to my original user. Both users running KDE. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.7.0-4-generic 3.7.0-4.12 ProcVersionSignature: Ubuntu 3.7.0-4.12-generic 3.7.0-rc7 Uname: Linux 3.7.0-4-generic x86_64 ApportVersion: 2.6.3-0ubuntu2 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Sun Dec 2 23:49:46 2012 HibernationDevice: RESUME=UUID=985b0eb1-c149-486d-a66d-3113788778b1 InstallationDate: Installed on 2012-07-17 (138 days ago) InstallationMedia: Kubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120717) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.7.0-4-generic root=UUID=711860b7-f028-46b1-83bb-c2be5dc8044d ro nointremap crashkernel=384M-2G:64M,2G-:128M 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.7.0-4-generic N/A linux-backports-modules-3.7.0-4-generic N/A linux-firmware 1.97 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to raring on 2012-12-02 (0 days ago) dmi.bios.date: 09/10/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: P55M Pro dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd09/10/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnP55MPro:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1085751/+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 1348688] Re: kernel does not support limiting swap usage (memory.memsw.limit_in_bytes missing)
After updating to that kernel (under 14.04), the problem is not fixed. $ uname -a Linux kit1 3.19.0-031900rc4-generic #201501112135 SMP Sun Jan 11 21:36:48 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux * The LXC instance still does not start if the memtuneswap_hard_limit unit='KiB'131072/swap_hard_limit/memtune setting is included. $ virsh -c lxc: start gold-lxc-20140717 error: Failed to start domain gold-lxc-20140717 error: internal error: guest failed to start: Unable to write to '/sys/fs/cgroup/memory/machine/gold-lxc-20140717.libvirt-lxc/memory.memsw.limit_in_bytes': No such file or directory $ ls /sys/fs/cgroup/memory/machine/gold-lxc-20140717.libvirt-lxc/ cgroup.clone_children memory.kmem.tcp.failcnt memory.oom_control cgroup.event_controlmemory.kmem.tcp.limit_in_bytes memory.pressure_level cgroup.procsmemory.kmem.tcp.max_usage_in_bytes memory.soft_limit_in_bytes memory.failcnt memory.kmem.tcp.usage_in_bytes memory.stat memory.force_empty memory.kmem.usage_in_bytes memory.swappiness memory.kmem.failcnt memory.limit_in_bytes memory.usage_in_bytes memory.kmem.limit_in_bytes memory.max_usage_in_bytes memory.use_hierarchy memory.kmem.max_usage_in_bytes memory.move_charge_at_immigrate notify_on_release memory.kmem.slabinfomemory.numa_stattasks (Note it does not include memory.memsw.limit_in_bytes) * After reverting to kernel 3.13.0-43 and doing the same lxc start which fails in the same way: $ ls /sys/fs/cgroup/memory/machine/gold-lxc-20140717.libvirt-lxc/ cgroup.clone_children memory.kmem.tcp.failcnt memory.oom_control cgroup.event_controlmemory.kmem.tcp.limit_in_bytes memory.pressure_level cgroup.procsmemory.kmem.tcp.max_usage_in_bytes memory.soft_limit_in_bytes memory.failcnt memory.kmem.tcp.usage_in_bytes memory.stat memory.force_empty memory.kmem.usage_in_bytes memory.swappiness memory.kmem.failcnt memory.limit_in_bytes memory.usage_in_bytes memory.kmem.limit_in_bytes memory.max_usage_in_bytes memory.use_hierarchy memory.kmem.max_usage_in_bytes memory.move_charge_at_immigrate notify_on_release memory.kmem.slabinfomemory.numa_stattasks Looks identical to me. ** 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/1348688 Title: kernel does not support limiting swap usage (memory.memsw.limit_in_bytes missing) Status in linux package in Ubuntu: Confirmed Bug description: (Sorry I'm not sure exactly what package to report this against - kernel perhaps? libvirt is what I was using to replicate the problem) Host platform: ubuntu 14.04 amd64, Mac Mini, 16GB RAM. Short version: create an LXC domain with memtune swap_hard_limit set in the XML: domain type='lxc' namegold-lxc-20140717/name uuidb2a02d49-bb1e-4aec-81d1-58910892780e/uuid memory unit='KiB'327680/memory currentMemory unit='KiB'327680/currentMemory memtune swap_hard_limit unit='KiB'131072/swap_hard_limit /memtune ... (full version at end of this report) Now try to start it: $ virsh -c lxc: start gold-lxc-20140717error: Failed to start domain gold-lxc-20140717 error: internal error: guest failed to start: Unable to write to '/sys/fs/cgroup/memory/machine/gold-lxc-20140717.libvirt-lxc/memory.memsw.limit_in_bytes': No such file or directory The reason this matters is because otherwise the LXC memory limit applies only to real RAM used. If the guest exceeds this it can still use as much swap space as it likes, and is therefore effectively unlimited (and can happily DoS the swap disk). Long version: I created an ubuntu 14.04 i386 VM image using python-vmbuilder, loopback-mounted it with qemu-nbd, and rsync'd it to create a root filesystem for an LXC guest. Then defined a guest using libvirt XML and started it using virsh -c lxc: start domain (as per XML at end but without the memtune section). It starts successfully, networking is fine, I can get a console etc. Now, the libvirt XML description says the guest's memory limit is 320MB: memory unit='KiB'327680/memory currentMemory unit='KiB'327680/currentMemory and indeed the cgroups setting has been set: $ cat /sys/fs/cgroup/memory/machine/gold-lxc-20140717.libvirt-lxc/memory.limit_in_bytes 335544320 However inside the guest I can happily allocate as much memory as I like, up to just under 4GB, which is the limit for a 32-bit guest. Here's the test program I ran in the guest (usemem.c): #include stdlib.h #include unistd.h #include stdio.h int
[Kernel-packages] [Bug 1410907] Re: linux: 2.6.32-72.139 -proposed tracker
** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed = In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) = tai271828 (taihsiangho) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1410907 Title: linux: 2.6.32-72.139 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-ports-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Lucid: New Bug description: This bug is for tracking the 2.6.32-72.139 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-stable-Prepare-package-start:Wednesday, 14. January 2015 17:57 UTC kernel-stable-Prepare-package-end:Thursday, 15. January 2015 18:05 UTC kernel-stable-Promote-to-proposed-start:Thursday, 15. January 2015 18:05 UTC ppa-package-testing-start:Thursday, 15. January 2015 18:05 UTC kernel-stable-Promote-to-proposed-end:Thursday, 15. January 2015 21:33 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Thursday, 15. January 2015 23:03 UTC kernel-stable-Verification-testing-start:Thursday, 15. January 2015 23:03 UTC kernel-stable-Certification-testing-start:Thursday, 15. January 2015 23:04 UTC kernel-stable-Security-signoff-start:Thursday, 15. January 2015 23:04 UTC kernel-stable-Regression-testing-start:Thursday, 15. January 2015 23:04 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1410907/+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 1409890] Re: linux: 3.16.0-30.40 -proposed tracker
** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed = In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) = tai271828 (taihsiangho) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1409890 Title: linux: 3.16.0-30.40 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Utopic: New Bug description: This bug is for tracking the 3.16.0-30.40 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-stable-Prepare-package-start:Monday, 12. January 2015 20:07 UTC kernel-stable-Prepare-package-end:Tuesday, 13. January 2015 07:03 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 13. January 2015 07:03 UTC ppa-package-testing-start:Tuesday, 13. January 2015 07:03 UTC kernel-stable-Promote-to-proposed-end:Thursday, 15. January 2015 20:41 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Thursday, 15. January 2015 22:00 UTC kernel-stable-Verification-testing-start:Thursday, 15. January 2015 22:00 UTC kernel-stable-Certification-testing-start:Thursday, 15. January 2015 22:00 UTC kernel-stable-Security-signoff-start:Thursday, 15. January 2015 22:01 UTC kernel-stable-Regression-testing-start:Thursday, 15. January 2015 22:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1409890/+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 1410459] Re: linux: 3.2.0-76.111 -proposed tracker
** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed = In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) = tai271828 (taihsiangho) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1410459 Title: linux: 3.2.0-76.111 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: New Bug description: This bug is for tracking the 3.2.0-76.111 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-stable-Prepare-package-start:Tuesday, 13. January 2015 19:46 UTC kernel-stable-Prepare-package-end:Wednesday, 14. January 2015 18:07 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 14. January 2015 18:07 UTC ppa-package-testing-start:Wednesday, 14. January 2015 18:07 UTC kernel-stable-Promote-to-proposed-end:Thursday, 15. January 2015 20:39 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Thursday, 15. January 2015 22:02 UTC kernel-stable-Verification-testing-start:Thursday, 15. January 2015 22:02 UTC kernel-stable-Certification-testing-start:Thursday, 15. January 2015 22:02 UTC kernel-stable-Security-signoff-start:Thursday, 15. January 2015 22:03 UTC kernel-stable-Regression-testing-start:Thursday, 15. January 2015 22:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1410459/+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 1401903] Re: [Hyper-V] FileCopy data loss after fcopy finish (X86 Only) Ubuntu 14.10
** Changed in: linux-lts-utopic (Ubuntu Trusty) Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1401903 Title: [Hyper-V] FileCopy data loss after fcopy finish (X86 Only) Ubuntu 14.10 Status in linux package in Ubuntu: Fix Released 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: Fix Committed Status in linux source package in Utopic: Fix Committed Status in linux-lts-utopic source package in Utopic: Invalid Status in linux source package in Vivid: Fix Released Status in linux-lts-utopic source package in Vivid: Invalid Bug description: Please include this patch for the bug detailed below. https://git.kernel.org/cgit/linux/kernel/git/gregkh/char-misc.git/commit/?h=char-misc-nextid=31d4ea1a093fcf668d5f95af44b8d41488bdb7ec The hv_fcopy_daemon must also be recompiled with this header. Description of problem: after fcopy from the host to guest check it in guest,no data in the file Version-Release number of selected component (if applicable): Host: hyperv server 2012 R2 Guest VM: Ubuntu 14.10 (final release) How reproducible: 100% Steps to Reproduce: 1.input data in Test.txt（host） 2.install hypervfcopyd(guest) 3.service hypervfcopyd start(guest) 4.(host)C:\ Copy-VMFile Test VM -SourcePath C:\Test.txt -DestinationPath /test -CreateFullPath -FileSource Host(host) 5.check data in test.txt what fcopyed from host(guest) Actual results: all the data is lost Expected results: the same with the original file Additional info: - x64 builds are not affected - this bug has been initially found and patched in a RHEL bug thread, details above are from it. === break-fix: bc5a5b02331a3175a5fca20a4beba249e573b672 31d4ea1a093fcf668d5f95af44b8d41488bdb7ec To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1401903/+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 1335478] Re: A new instance of IBM Domino 'bindsock' cannot bind to ports 1024 Kernel 3.13.0-29 and above
** Tags removed: kernel-bug-break-fix -- You 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 Released 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 Released 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 Released Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux source package in Utopic: Fix Released 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 Released 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 1409123] Re: hw csum failure in encapsulated network topolgies
** Also affects: linux (Ubuntu Vivid) Importance: Medium Assignee: Jay Vosburgh (jvosburgh) Status: Triaged ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-utopic (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-lts-utopic (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-lts-utopic (Ubuntu Utopic) Status: New = Invalid ** Description changed: Virtualized network topologies that utilize encapsulation (e.g., VXLAN) and bridging may experience kernel errors of the format: [ 4297.761899] eth0: hw csum failure [ 4297.765210] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G OE 3.18.0-rc4 -nn+ #22 [ 4297.765212] Hardware name: LENOVO 0829F3U/To be filled by O.E.M., BIOS 90KT15 AUS 07/21/2010 [ 4297.765216] 88013fc03ba8 8172f026 0 001 [ 4297.765219] 88013870e000 88013fc03bc8 8162ba52 8161c 1a0 [ 4297.765221] 8800afdf1000 88013fc03c08 8162325c 88013870e 000 [ 4297.765223] Call Trace: [ 4297.765224] IRQ [8172f026] dump_stack+0x46/0x58 [ 4297.765235] [8162ba52] netdev_rx_csum_fault+0x42/0x50 [ 4297.765238] [8161c1a0] ? skb_push+0x40/0x40 [ 4297.765240] [8162325c] __skb_checksum_complete+0xbc/0xd0 [ 4297.765243] [8168c602] tcp_v4_rcv+0x2e2/0x950 [ 4297.765246] [81666ca0] ? ip_rcv_finish+0x360/0x360 [ 4297.765248] [81660224] ? nf_hook_slow+0x74/0x130 [ 4297.765250] [81666ca0] ? ip_rcv_finish+0x360/0x360 [ 4297.765253] [81666d4c] ip_local_deliver_finish+0xac/0x220 [ 4297.765255] [81667058] ip_local_deliver+0x48/0x80 [ 4297.765257] [816669c1] ip_rcv_finish+0x81/0x360 [ 4297.765259] [81667332] ip_rcv+0x2a2/0x3f0 [ 4297.765261] [8162e932] __netif_receive_skb_core+0x562/0x7a0 [ 4297.765263] [8162eb88] __netif_receive_skb+0x18/0x60 [ 4297.765265] [8162f8f6] process_backlog+0xa6/0x150 The backtrace may vary, stacks descending into conntrack have also been observed: Call Trace: - IRQ [8171a324] dump_stack+0x45/0x56 - [8161bfba] netdev_rx_csum_fault+0x3a/0x40 - [81614782] __skb_checksum_complete_head+0x62/0x70 - [816147a1] __skb_checksum_complete+0x11/0x20 - [816a3eac] nf_ip_checksum+0xcc/0x100 - [a04df33b] udp_error+0xdb/0x1f0 [nf_conntrack] - [a04d926e] nf_conntrack_in+0xee/0xb40 [nf_conntrack] - [a0307653] ? do_execute_actions+0x2e3/0xab0 [openvswitch] - [a0307e4b] ? ovs_execute_actions+0x2b/0x30 [openvswitch] - [81654540] ? inet_del_offload+0x40/0x40 - [a03b52e2] ipv4_conntrack_in+0x22/0x30 [nf_conntrack_ipv4] - [8164e0aa] nf_iterate+0x9a/0xb0 - [81654540] ? inet_del_offload+0x40/0x40 - [8164e134] nf_hook_slow+0x74/0x130 - [81654540] ? inet_del_offload+0x40/0x40 - [81654f68] ip_rcv+0x2f8/0x3d0 + IRQ [8171a324] dump_stack+0x45/0x56 + [8161bfba] netdev_rx_csum_fault+0x3a/0x40 + [81614782] __skb_checksum_complete_head+0x62/0x70 + [816147a1] __skb_checksum_complete+0x11/0x20 + [816a3eac] nf_ip_checksum+0xcc/0x100 + [a04df33b] udp_error+0xdb/0x1f0 [nf_conntrack] + [a04d926e] nf_conntrack_in+0xee/0xb40 [nf_conntrack] + [a0307653] ? do_execute_actions+0x2e3/0xab0 [openvswitch] + [a0307e4b] ? ovs_execute_actions+0x2b/0x30 [openvswitch] + [81654540] ? inet_del_offload+0x40/0x40 + [a03b52e2] ipv4_conntrack_in+0x22/0x30 [nf_conntrack_ipv4] + [8164e0aa] nf_iterate+0x9a/0xb0 + [81654540] ? inet_del_offload+0x40/0x40 + [8164e134] nf_hook_slow+0x74/0x130 + [81654540] ? inet_del_offload+0x40/0x40 + [81654f68] ip_rcv+0x2f8/0x3d0 The root cause of this is twofold: First, the kernel handling of forwarded packets that have been encapsulated (e.g., from VXLAN) for devices that support CHECKSUM_COMPLETE checksum offload fails to update the running checksum when decapsulating the packet. Second, for the enic device itself, the hardware is not correctly computing the checksum for some cases. Both of these issues are patched in mainline: - commit 17e96834fd35997ca7cdfbf15413bcd5a36ad448 - Author: Govindarajulu Varadarajan _gov...@gmx.com - Date: Thu Dec 18 15:58:42 2014 +0530 + commit 17e96834fd35997ca7cdfbf15413bcd5a36ad448 + Author: Govindarajulu Varadarajan _gov...@gmx.com + Date: Thu Dec 18 15:58:42 2014 +0530 enic: fix rx skb checksum - commit 2c26d34bbcc0b3f30385d5587aa232289e2eed8e - Author: Jay Vosburgh jay.vosbu...@canonical.com - Date: Fri Dec 19 15:32:00 2014 -0800 + commit
[Kernel-packages] [Bug 1411284] Re: arm64: ubuntu drivers are not built at all for this arch
** Changed in: linux (Ubuntu Utopic) Status: In Progress = Fix Committed ** Changed in: linux (Ubuntu Trusty) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1411284 Title: arm64: ubuntu drivers are not built at all for this arch Status in linux package in Ubuntu: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux source package in Utopic: Fix Committed Status in linux source package in Vivid: Fix Committed Bug description: We are not building the ubuntu drivers on arm64. We are missing the arch Kconfig include to enable them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1411284/+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 1409123] Re: hw csum failure in encapsulated network topolgies
** Changed in: linux (Ubuntu Trusty) Status: New = Confirmed ** Changed in: linux (Ubuntu Utopic) Status: New = Confirmed ** Changed in: linux-lts-utopic (Ubuntu Trusty) Status: New = Confirmed ** Changed in: linux (Ubuntu Vivid) Status: Triaged = 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/1409123 Title: hw csum failure in encapsulated network topolgies Status in linux package in Ubuntu: Confirmed Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Status in linux-lts-utopic source package in Trusty: Confirmed Status in linux source package in Utopic: Confirmed Status in linux-lts-utopic source package in Utopic: Invalid Status in linux source package in Vivid: Confirmed Status in linux-lts-utopic source package in Vivid: Invalid Bug description: Virtualized network topologies that utilize encapsulation (e.g., VXLAN) and bridging may experience kernel errors of the format: [ 4297.761899] eth0: hw csum failure [ 4297.765210] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G OE 3.18.0-rc4 -nn+ #22 [ 4297.765212] Hardware name: LENOVO 0829F3U/To be filled by O.E.M., BIOS 90KT15 AUS 07/21/2010 [ 4297.765216] 88013fc03ba8 8172f026 0 001 [ 4297.765219] 88013870e000 88013fc03bc8 8162ba52 8161c 1a0 [ 4297.765221] 8800afdf1000 88013fc03c08 8162325c 88013870e 000 [ 4297.765223] Call Trace: [ 4297.765224] IRQ [8172f026] dump_stack+0x46/0x58 [ 4297.765235] [8162ba52] netdev_rx_csum_fault+0x42/0x50 [ 4297.765238] [8161c1a0] ? skb_push+0x40/0x40 [ 4297.765240] [8162325c] __skb_checksum_complete+0xbc/0xd0 [ 4297.765243] [8168c602] tcp_v4_rcv+0x2e2/0x950 [ 4297.765246] [81666ca0] ? ip_rcv_finish+0x360/0x360 [ 4297.765248] [81660224] ? nf_hook_slow+0x74/0x130 [ 4297.765250] [81666ca0] ? ip_rcv_finish+0x360/0x360 [ 4297.765253] [81666d4c] ip_local_deliver_finish+0xac/0x220 [ 4297.765255] [81667058] ip_local_deliver+0x48/0x80 [ 4297.765257] [816669c1] ip_rcv_finish+0x81/0x360 [ 4297.765259] [81667332] ip_rcv+0x2a2/0x3f0 [ 4297.765261] [8162e932] __netif_receive_skb_core+0x562/0x7a0 [ 4297.765263] [8162eb88] __netif_receive_skb+0x18/0x60 [ 4297.765265] [8162f8f6] process_backlog+0xa6/0x150 The backtrace may vary, stacks descending into conntrack have also been observed: Call Trace: IRQ [8171a324] dump_stack+0x45/0x56 [8161bfba] netdev_rx_csum_fault+0x3a/0x40 [81614782] __skb_checksum_complete_head+0x62/0x70 [816147a1] __skb_checksum_complete+0x11/0x20 [816a3eac] nf_ip_checksum+0xcc/0x100 [a04df33b] udp_error+0xdb/0x1f0 [nf_conntrack] [a04d926e] nf_conntrack_in+0xee/0xb40 [nf_conntrack] [a0307653] ? do_execute_actions+0x2e3/0xab0 [openvswitch] [a0307e4b] ? ovs_execute_actions+0x2b/0x30 [openvswitch] [81654540] ? inet_del_offload+0x40/0x40 [a03b52e2] ipv4_conntrack_in+0x22/0x30 [nf_conntrack_ipv4] [8164e0aa] nf_iterate+0x9a/0xb0 [81654540] ? inet_del_offload+0x40/0x40 [8164e134] nf_hook_slow+0x74/0x130 [81654540] ? inet_del_offload+0x40/0x40 [81654f68] ip_rcv+0x2f8/0x3d0 The root cause of this is twofold: First, the kernel handling of forwarded packets that have been encapsulated (e.g., from VXLAN) for devices that support CHECKSUM_COMPLETE checksum offload fails to update the running checksum when decapsulating the packet. Second, for the enic device itself, the hardware is not correctly computing the checksum for some cases. Both of these issues are patched in mainline: commit 17e96834fd35997ca7cdfbf15413bcd5a36ad448 Author: Govindarajulu Varadarajan _gov...@gmx.com Date: Thu Dec 18 15:58:42 2014 +0530 enic: fix rx skb checksum commit 2c26d34bbcc0b3f30385d5587aa232289e2eed8e Author: Jay Vosburgh jay.vosbu...@canonical.com Date: Fri Dec 19 15:32:00 2014 -0800 net/core: Handle csum for CHECKSUM_COMPLETE VXLAN forwarding === break-fix: - 17e96834fd35997ca7cdfbf15413bcd5a36ad448 break-fix: - 2c26d34bbcc0b3f30385d5587aa232289e2eed8e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1409123/+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 1383356] Re: CVE-2014-7970
** Changed in: linux (Ubuntu Precise) Status: New = Fix Committed -- 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/1383356 Title: CVE-2014-7970 Status in linux package in Ubuntu: Fix Committed 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: Fix Committed 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: Fix Committed Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Fix Committed Status in linux-lts-trusty source package in Precise: Fix Released 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: Fix Released 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: Fix Released 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: Fix Released 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: Fix Committed 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 in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4
[Kernel-packages] [Bug 1411320] Re: btrfs causes reboot when running xfs btrfs tests 032 and 033 back to back
This fix was applied in v3.14-rcN, so this does not affect anything since trusty. Nominating for trusty and closing out elsewhere. ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Trusty) Assignee: (unassigned) = Colin Ian King (colin-king) ** Changed in: linux (Ubuntu Trusty) Importance: Undecided = Medium ** Changed in: linux (Ubuntu Trusty) Status: New = Confirmed ** Changed in: linux (Ubuntu Trusty) Status: Confirmed = In Progress ** Changed in: linux (Ubuntu) Status: In Progress = Invalid ** Summary changed: - btrfs causes reboot when running xfs btrfs tests 032 and 033 back to back + [trusty] btrfs causes reboot when running xfs btrfs tests 032 and 033 back to back -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1411320 Title: [trusty] btrfs causes reboot when running xfs btrfs tests 032 and 033 back to back Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: In Progress Bug description: Running xfs btrfs specific tests 032 and 033 back-to-back with various mount options with 7 target btrfs devices causes the kernel to reboot when running inside a virtual machine. I've bisected this down and the upstream commit 2c21b4d733d6e50514e30ffd87110364ddda695b Btrfs: fix transaction abortion when remounting btrfs from RW to RO fixes this, allowing me to run the tests through to completion multiple times. Without this fix, the tests always reboot on the first iteration using the autodefrag mount option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1411320/+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 1410519] Re: [PowerVM] Kernel BUG @ kernel/irq_work.c:157! - 24x7 hw counters
** Description changed: [Impact] Using perf with hv_24x7 events can cause a kernel BUG. [Fix] The following upstream commits: - d658972 - 48bee8a - f34b6c7 - ec2aef5 + d658972 + 48bee8a + f34b6c7 + ec2aef5 [Test Case] Steps to recreate the problem: 1. Install Ubuntu 15.04 as a PowerVM guest. 2. Install perf tool 3. Run following scripts to test 24/7 Power8 hardware counter event with perf. tool === Script 1 #!/bin/bash count=0; offset=0x128 PERF_ARGS=-r 10 -C 0 while [ $count -lt 100 ]; do EVENT=hv_24x7/domain=0x2,offset=$offset,starting_index=10/ perf stat $PERF_ARGS -x ' ' perf stat $PERF_ARGS -x ' ' -e $EVENT ls count=) done Script 2 #!/bin/bash offset=0; PERF_ARGS=-r 10 -C 0 while [ $offset -lt 8192 ]; do EVENT=hv_24x7/domain=0x2,offset=$offset,starting_index=10/ perf stat $PERF_ARGS -x ' ' perf stat $PERF_ARGS -x ' ' -e $EVENT ls offset=) done After few iterations I hit the following BUG. tt2.sh tt.sh tt2.sh tt.sh tt2.sh tt.sh 275679187521558 hv_24x7/domain=0x2,offset=6848,starting_index=10/ 0.00% tt2.sh tt.sh [ 4657.314709] softirq: huh, entered softirq 7 SCHED c010abc0 with preem pt_count 0100, exited with bfff? [ 4657.314727] kernel BUG at /build/buildd/linux-3.16.0/kernel/irq_work.c:157! [ 4657.314732] Oops: Exception in kernel mode, sig: 5 [#1] [ 4657.314740] Modules linked in: rtc_generic pseries_rng [ 4657.314749] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.16.0-25-generic #33-U [ 4657.314755] task: c1375e00 ti: c13d task.ti: c13d [ 4657.314759] NIP: c01e8ffc LR: c001fe70 CTR: c0002800ic) [ 4657.314770] MSR: 80029033 SF,EE,ME,IR,DR,RI,LE CR: 28042024 XER: 000a [ 4657.314782] CFAR: c001fe6c SOFTE: 0 GPR04: 0010 009c c1424a98 0002 GPR12: 80009033 ce9a 06a3fcd0 0060 GPR16: 0020 c0e57c00 GPR20: c1595dca c1595478 0001 GPR28: c0e40380 c0e40300 c13d3590 c0e56f08 [ 4657.314832] NIP [c01e8ffc] irq_work_run+0x1c/0x30 [ 4657.314841] Call Trace: 4000 (unreliable) [ 4657.314861] [c13d34f0] [c001ff90] timer_interrupt+0xa0/0xe0 [ 4657.314871] [c13d3520] [c0002914] decrementer_common+0x114/0x180 [ 4657.314884] --- Exception: 901 at arch_local_irq_restore+0x14/0x90 [ 4657.314896] [c13d3810] [c012ed08] vprintk_emit+0x3b8/0x660 (u [ 4657.314908] [c13d38e0] [c0a02650] printk+0x84/0x98 [ 4657.314918] [c13d3910] [c00b51b4] __do_softirq+0x1e4/0x410 [ 4657.314927] [c13d3a00] [c00b57b8] irq_exit+0xf8/0x1400 [ 4657.314948] [c13d3a60] [c0002c14] doorbell_super_common+0x114/0x180 [ 4657.314963] --- Exception: a01 at plpar_hcall_norets+0x8c/0xdc [ 4657.314963] LR = check_and_cede_processor+0x34/0x5020/0x50 (unreliable) [ 4657.314997] [c13d3df0] [c084077c] cpuidle_enter_state+0x6c/0x140c0 [ 4657.315030] [c13d3f00] [c0d63ea8] start_kernel+0x500/0x51c [ 4657.315047] Instruction dump: [ 4657.315052] eba1ffe8 7c0803a6 ebc1fff0 ebe1fff8 4e800020 3c4c011f 3842c110 78290464 [ 4657.315068] 81290014 752a000f 7d380026 55291ffe 0b09 4bfffec8 6000 6000 [ 4657.315090] ---[ end trace ee202cccd2211e5d ]--- [ 4657.320224] [ 4657.362675] Unable to handle kernel paging request for data at address 0xc000 000b35515048 [ 4657.362680] Faulting instruction address: 0xc006a37c [ 4657.362684] Oops: Kernel access of bad area, sig: 11 [#2] [ 4657.362686] SMP NR_CPUS=2048 NUMA pSeries [ 4657.362695] CPU: 12 PID: 7 Comm: rcu_sched Tainted: G D 3.16.0-25- [ 4657.362699] task: c000eb581540 ti: c000eb604000 task.ti: c000eb60 [ 4657.362703] NIP: c006a37c LR: c00865a8 CTR: c006a340 [ 4657.362706] REGS: c000eb607800 TRAP: 0300 Tainted: G D (3.16.0-25-generic) [ 4657.362718] CFAR: c00865a4 DAR: c00b35515048 DSISR: 4000 SOFTE: 0 GPR00: c00865a8 c000eb607a80 c13d50f0 013d30d0 GPR08: 00cc c00b35515000 ce9a GPR12: c006a340 ce9a6c00 0001 GPR20: c1389700 0001 GPR28: c1420a68 013d30d0 0001 [ 4657.362758] NIP [c006a37c] icp_hv_cause_ipi+0x3c/0xc0 [ 4657.362762] LR [c00865a8] pSeries_cause_ipi_mux+0x88/0xc0 [ 4657.362765] Call Trace: 0 (unreliable) [
Re: [Kernel-packages] [Bug 1411193] Re: [Asus F200MA] bluetooth not working
Here is the source of that kernel. The same patch type. But it seems that firmware does not load. https://github.com/hanipouspilot/ubuntu-fixes/tree/bt13d3_3423 2015-01-16 7:16 GMT+03:00 Alessandro Languasco langu...@gmail.com: no changes with echo 'options asus_nb_wmi wapf=4' | sudo tee /etc/modprobe.d/asus.conf after a reboot Jeremy: languasc@languasc-asus:~$ modprobe -c | grep 3423 | grep ath3k alias usb:v13D3p3423d*dc*dsc*dp*ic*isc*ip*in* ath3k -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1411193 Title: [Asus F200MA] bluetooth not working Status in linux package in Ubuntu: Incomplete Bug description: In my opinion, this is a very similar bug to https://bugs.launchpad.net/bugs/1395465 in the sense that the bluetooth indicator works but no external devices are detected. I don't know which information I should provide here so I just insert uname -a and lsusb. lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:3423 IMC Networks Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub uname -a Linux languasc-asus 3.16.0-30-generic #40-Ubuntu SMP Mon Jan 12 22:06:37 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Any help will be greatly appreciated. Alessandro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1411193/+subscriptions -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1411193 Title: [Asus F200MA] bluetooth not working Status in linux package in Ubuntu: Incomplete Bug description: In my opinion, this is a very similar bug to https://bugs.launchpad.net/bugs/1395465 in the sense that the bluetooth indicator works but no external devices are detected. I don't know which information I should provide here so I just insert uname -a and lsusb. lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:3423 IMC Networks Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub uname -a Linux languasc-asus 3.16.0-30-generic #40-Ubuntu SMP Mon Jan 12 22:06:37 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Any help will be greatly appreciated. Alessandro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1411193/+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 1411193] Re: [Asus F200MA] bluetooth not working
But the Windows driver loads same firmware as for 13d3:3408 e.g. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1411193 Title: [Asus F200MA] bluetooth not working Status in linux package in Ubuntu: Incomplete Bug description: In my opinion, this is a very similar bug to https://bugs.launchpad.net/bugs/1395465 in the sense that the bluetooth indicator works but no external devices are detected. I don't know which information I should provide here so I just insert uname -a and lsusb. lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:3423 IMC Networks Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub uname -a Linux languasc-asus 3.16.0-30-generic #40-Ubuntu SMP Mon Jan 12 22:06:37 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Any help will be greatly appreciated. Alessandro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1411193/+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 1411320] Re: [trusty] btrfs causes reboot when running xfs btrfs tests 032 and 033 back to back
** Changed in: linux (Ubuntu Trusty) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1411320 Title: [trusty] btrfs causes reboot when running xfs btrfs tests 032 and 033 back to back Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Fix Committed Bug description: Running xfs btrfs specific tests 032 and 033 back-to-back with various mount options with 7 target btrfs devices causes the kernel to reboot when running inside a virtual machine. I've bisected this down and the upstream commit 2c21b4d733d6e50514e30ffd87110364ddda695b Btrfs: fix transaction abortion when remounting btrfs from RW to RO fixes this, allowing me to run the tests through to completion multiple times. Without this fix, the tests always reboot on the first iteration using the autodefrag mount option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1411320/+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 1401817] Re: memory leak with unknown reason after upgrade to utopic
trusty + mainline kernel works like a charm, worker 2 and 3 are swapping again... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1401817 Title: memory leak with unknown reason after upgrade to utopic Status in linux package in Ubuntu: Confirmed Bug description: I'm not sure if this is the right component/package. We are not able to identify a package/program which could be responsible for this bug, so we assume it is the kernel or at least a kernel configuration. Since the upgrade from trusty to utopic at October 27., our three servers for package building are massively swapping. This leads to by a factor of four slower build times. There were no configuration changes at all. Munin graphs of one of the affected servers are attached. The system has 48GB memory, and we have configured several ramdisks: root@cx1000-02:~# mount | grep -E tmpfs|ramfs none on /sys/fs/cgroup type tmpfs (rw,uid=0,gid=0,mode=0755,size=1024) udev on /dev type devtmpfs (rw,mode=0755) tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755) none on /run/lock type tmpfs (rw,nodev,noexec,nosuid,size=5242880) none on /run/shm type tmpfs (rw,nosuid,nodev) none on /run/user type tmpfs (rw,nodev,noexec,nosuid,size=104857600,mode=0755) tmpfs on /var/tmp/obs type tmpfs (rw,size=36G) tmpfs on /run/obs type tmpfs (rw,relatime,size=1G) ramfs on /var/obscache type ramfs (rw) tmpfs on /run/obs type tmpfs (rw,relatime,size=1048576k) The build service uses several chroot environments to build packages for several distributions (http://openbuildservice.org/). You don't see any process which allocates so much memory with 'top'. Even after stopping the build service and unmounting /var/tmp/obs you are not able to deactivate the swap via swapoff -a: root@cx1000-02:~# swapoff -a swapoff: /dev/sda5: swapoff failed: Cannot allocate memory We also tested the latest kernel (3.16.0-28) and an old trusty kernel (3.13.0-40) without success. Also patching perl to exclude the perl bug https://rt.perl.org/Public/Bug/Display.html?id=123198 as root cause doesn't help. We don't have any idea what's the cause for this problem... We can deploy debug packages or anything else on the system, so please hesitate to ask for any information or help. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-26-generic 3.16.0-26.35 ProcVersionSignature: Ubuntu 3.16.0-26.35-generic 3.16.7-ckt1 Uname: Linux 3.16.0-26-generic x86_64 AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' Date: Fri Dec 12 09:54:36 2014 HibernationDevice: RESUME=UUID=531cb8f2-e194-45a7-a13c-3167aacf89bf InstallationDate: Installed on 2011-09-20 (1178 days ago) InstallationMedia: Ubuntu-Server 11.04 Natty Narwhal - Release amd64 (20110426) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: FUJITSU PRIMERGY CX122 S1 PciMultimedia: ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-26-generic root=UUID=6e5b9bee-ccdf-4e6f-b09d-759312aeb3e0 ro quiet RelatedPackageVersions: linux-restricted-modules-3.16.0-26-generic N/A linux-backports-modules-3.16.0-26-generic N/A linux-firmware 1.138 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2014-10-27 (45 days ago) dmi.bios.date: 05/24/2011 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: 6.00 Rev. 1.10.2899.A1 dmi.board.asset.tag: - dmi.board.name: D2899 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D2899-A11 WGS02 GS01 dmi.chassis.asset.tag: YLAM001377 dmi.chassis.type: 23 dmi.chassis.vendor: FUJITSU dmi.chassis.version: CX122S1R dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvr6.00Rev.1.10.2899.A1:bd05/24/2011:svnFUJITSU:pnPRIMERGYCX122S1:pvrGS01:rvnFUJITSU:rnD2899:rvrS26361-D2899-A11WGS02GS01:cvnFUJITSU:ct23:cvrCX122S1R: dmi.product.name: PRIMERGY CX122 S1 dmi.product.version: GS01 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1401817/+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 1411193] Re: [Asus F200MA] bluetooth not working
Don't know what to say; this is far beyond my skills. Maybe it could be useful to try with another laptop like mine; but I don't know anyone else who owns an asus f200ma. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1411193 Title: [Asus F200MA] bluetooth not working Status in linux package in Ubuntu: Incomplete Bug description: In my opinion, this is a very similar bug to https://bugs.launchpad.net/bugs/1395465 in the sense that the bluetooth indicator works but no external devices are detected. I don't know which information I should provide here so I just insert uname -a and lsusb. lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:3423 IMC Networks Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub uname -a Linux languasc-asus 3.16.0-30-generic #40-Ubuntu SMP Mon Jan 12 22:06:37 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Any help will be greatly appreciated. Alessandro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1411193/+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 1410519] Re: [PowerVM] Kernel BUG @ kernel/irq_work.c:157! - 24x7 hw counters
** Changed in: linux (Ubuntu Utopic) Status: In Progress = Fix Committed ** Changed in: linux (Ubuntu) Status: Triaged = 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/1410519 Title: [PowerVM] Kernel BUG @ kernel/irq_work.c:157! - 24x7 hw counters Status in linux package in Ubuntu: Confirmed Status in linux source package in Utopic: Fix Committed Bug description: [Impact] Using perf with hv_24x7 events can cause a kernel BUG. [Fix] The following upstream commits: d658972 48bee8a f34b6c7 ec2aef5 [Test Case] Steps to recreate the problem: 1. Install Ubuntu 15.04 as a PowerVM guest. 2. Install perf tool 3. Run following scripts to test 24/7 Power8 hardware counter event with perf. tool === Script 1 #!/bin/bash count=0; offset=0x128 PERF_ARGS=-r 10 -C 0 while [ $count -lt 100 ]; do EVENT=hv_24x7/domain=0x2,offset=$offset,starting_index=10/ perf stat $PERF_ARGS -x ' ' perf stat $PERF_ARGS -x ' ' -e $EVENT ls count=) done Script 2 #!/bin/bash offset=0; PERF_ARGS=-r 10 -C 0 while [ $offset -lt 8192 ]; do EVENT=hv_24x7/domain=0x2,offset=$offset,starting_index=10/ perf stat $PERF_ARGS -x ' ' perf stat $PERF_ARGS -x ' ' -e $EVENT ls offset=) done After few iterations I hit the following BUG. tt2.sh tt.sh tt2.sh tt.sh tt2.sh tt.sh 275679187521558 hv_24x7/domain=0x2,offset=6848,starting_index=10/ 0.00% tt2.sh tt.sh [ 4657.314709] softirq: huh, entered softirq 7 SCHED c010abc0 with preem pt_count 0100, exited with bfff? [ 4657.314727] kernel BUG at /build/buildd/linux-3.16.0/kernel/irq_work.c:157! [ 4657.314732] Oops: Exception in kernel mode, sig: 5 [#1] [ 4657.314740] Modules linked in: rtc_generic pseries_rng [ 4657.314749] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.16.0-25-generic #33-U [ 4657.314755] task: c1375e00 ti: c13d task.ti: c13d [ 4657.314759] NIP: c01e8ffc LR: c001fe70 CTR: c0002800ic) [ 4657.314770] MSR: 80029033 SF,EE,ME,IR,DR,RI,LE CR: 28042024 XER: 000a [ 4657.314782] CFAR: c001fe6c SOFTE: 0 GPR04: 0010 009c c1424a98 0002 GPR12: 80009033 ce9a 06a3fcd0 0060 GPR16: 0020 c0e57c00 GPR20: c1595dca c1595478 0001 GPR28: c0e40380 c0e40300 c13d3590 c0e56f08 [ 4657.314832] NIP [c01e8ffc] irq_work_run+0x1c/0x30 [ 4657.314841] Call Trace: 4000 (unreliable) [ 4657.314861] [c13d34f0] [c001ff90] timer_interrupt+0xa0/0xe0 [ 4657.314871] [c13d3520] [c0002914] decrementer_common+0x114/0x180 [ 4657.314884] --- Exception: 901 at arch_local_irq_restore+0x14/0x90 [ 4657.314896] [c13d3810] [c012ed08] vprintk_emit+0x3b8/0x660 (u [ 4657.314908] [c13d38e0] [c0a02650] printk+0x84/0x98 [ 4657.314918] [c13d3910] [c00b51b4] __do_softirq+0x1e4/0x410 [ 4657.314927] [c13d3a00] [c00b57b8] irq_exit+0xf8/0x1400 [ 4657.314948] [c13d3a60] [c0002c14] doorbell_super_common+0x114/0x180 [ 4657.314963] --- Exception: a01 at plpar_hcall_norets+0x8c/0xdc [ 4657.314963] LR = check_and_cede_processor+0x34/0x5020/0x50 (unreliable) [ 4657.314997] [c13d3df0] [c084077c] cpuidle_enter_state+0x6c/0x140c0 [ 4657.315030] [c13d3f00] [c0d63ea8] start_kernel+0x500/0x51c [ 4657.315047] Instruction dump: [ 4657.315052] eba1ffe8 7c0803a6 ebc1fff0 ebe1fff8 4e800020 3c4c011f 3842c110 78290464 [ 4657.315068] 81290014 752a000f 7d380026 55291ffe 0b09 4bfffec8 6000 6000 [ 4657.315090] ---[ end trace ee202cccd2211e5d ]--- [ 4657.320224] [ 4657.362675] Unable to handle kernel paging request for data at address 0xc000 000b35515048 [ 4657.362680] Faulting instruction address: 0xc006a37c [ 4657.362684] Oops: Kernel access of bad area, sig: 11 [#2] [ 4657.362686] SMP NR_CPUS=2048 NUMA pSeries [ 4657.362695] CPU: 12 PID: 7 Comm: rcu_sched Tainted: G D 3.16.0-25- [ 4657.362699] task: c000eb581540 ti: c000eb604000 task.ti: c000eb60 [ 4657.362703] NIP: c006a37c LR: c00865a8 CTR: c006a340 [ 4657.362706] REGS: c000eb607800 TRAP: 0300 Tainted: G D (3.16.0-25-generic) [ 4657.362718] CFAR: c00865a4 DAR: c00b35515048 DSISR: 4000 SOFTE: 0 GPR00: c00865a8 c000eb607a80 c13d50f0 013d30d0 GPR08: 00cc c00b35515000 ce9a GPR12:
[Kernel-packages] [Bug 1401817] Re: memory leak with unknown reason after upgrade to utopic
So it must be some setting within the system that affects this behavior. Any hints from the Ubuntu guys what we should look for? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1401817 Title: memory leak with unknown reason after upgrade to utopic Status in linux package in Ubuntu: Confirmed Bug description: I'm not sure if this is the right component/package. We are not able to identify a package/program which could be responsible for this bug, so we assume it is the kernel or at least a kernel configuration. Since the upgrade from trusty to utopic at October 27., our three servers for package building are massively swapping. This leads to by a factor of four slower build times. There were no configuration changes at all. Munin graphs of one of the affected servers are attached. The system has 48GB memory, and we have configured several ramdisks: root@cx1000-02:~# mount | grep -E tmpfs|ramfs none on /sys/fs/cgroup type tmpfs (rw,uid=0,gid=0,mode=0755,size=1024) udev on /dev type devtmpfs (rw,mode=0755) tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755) none on /run/lock type tmpfs (rw,nodev,noexec,nosuid,size=5242880) none on /run/shm type tmpfs (rw,nosuid,nodev) none on /run/user type tmpfs (rw,nodev,noexec,nosuid,size=104857600,mode=0755) tmpfs on /var/tmp/obs type tmpfs (rw,size=36G) tmpfs on /run/obs type tmpfs (rw,relatime,size=1G) ramfs on /var/obscache type ramfs (rw) tmpfs on /run/obs type tmpfs (rw,relatime,size=1048576k) The build service uses several chroot environments to build packages for several distributions (http://openbuildservice.org/). You don't see any process which allocates so much memory with 'top'. Even after stopping the build service and unmounting /var/tmp/obs you are not able to deactivate the swap via swapoff -a: root@cx1000-02:~# swapoff -a swapoff: /dev/sda5: swapoff failed: Cannot allocate memory We also tested the latest kernel (3.16.0-28) and an old trusty kernel (3.13.0-40) without success. Also patching perl to exclude the perl bug https://rt.perl.org/Public/Bug/Display.html?id=123198 as root cause doesn't help. We don't have any idea what's the cause for this problem... We can deploy debug packages or anything else on the system, so please hesitate to ask for any information or help. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-26-generic 3.16.0-26.35 ProcVersionSignature: Ubuntu 3.16.0-26.35-generic 3.16.7-ckt1 Uname: Linux 3.16.0-26-generic x86_64 AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' Date: Fri Dec 12 09:54:36 2014 HibernationDevice: RESUME=UUID=531cb8f2-e194-45a7-a13c-3167aacf89bf InstallationDate: Installed on 2011-09-20 (1178 days ago) InstallationMedia: Ubuntu-Server 11.04 Natty Narwhal - Release amd64 (20110426) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: FUJITSU PRIMERGY CX122 S1 PciMultimedia: ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-26-generic root=UUID=6e5b9bee-ccdf-4e6f-b09d-759312aeb3e0 ro quiet RelatedPackageVersions: linux-restricted-modules-3.16.0-26-generic N/A linux-backports-modules-3.16.0-26-generic N/A linux-firmware 1.138 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2014-10-27 (45 days ago) dmi.bios.date: 05/24/2011 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: 6.00 Rev. 1.10.2899.A1 dmi.board.asset.tag: - dmi.board.name: D2899 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D2899-A11 WGS02 GS01 dmi.chassis.asset.tag: YLAM001377 dmi.chassis.type: 23 dmi.chassis.vendor: FUJITSU dmi.chassis.version: CX122S1R dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvr6.00Rev.1.10.2899.A1:bd05/24/2011:svnFUJITSU:pnPRIMERGYCX122S1:pvrGS01:rvnFUJITSU:rnD2899:rvrS26361-D2899-A11WGS02GS01:cvnFUJITSU:ct23:cvrCX122S1R: dmi.product.name: PRIMERGY CX122 S1 dmi.product.version: GS01 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1401817/+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
Re: [Kernel-packages] [Bug 1411193] Re: [Asus F200MA] bluetooth not working
What does rfkill list show ? 2015-01-16 14:53 GMT+03:00 Alessandro Languasco langu...@gmail.com: Don't know what to say; this is far beyond my skills. Maybe it could be useful to try with another laptop like mine; but I don't know anyone else who owns an asus f200ma. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1411193 Title: [Asus F200MA] bluetooth not working Status in linux package in Ubuntu: Incomplete Bug description: In my opinion, this is a very similar bug to https://bugs.launchpad.net/bugs/1395465 in the sense that the bluetooth indicator works but no external devices are detected. I don't know which information I should provide here so I just insert uname -a and lsusb. lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:3423 IMC Networks Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub uname -a Linux languasc-asus 3.16.0-30-generic #40-Ubuntu SMP Mon Jan 12 22:06:37 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Any help will be greatly appreciated. Alessandro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1411193/+subscriptions -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1411193 Title: [Asus F200MA] bluetooth not working Status in linux package in Ubuntu: Incomplete Bug description: In my opinion, this is a very similar bug to https://bugs.launchpad.net/bugs/1395465 in the sense that the bluetooth indicator works but no external devices are detected. I don't know which information I should provide here so I just insert uname -a and lsusb. lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:3423 IMC Networks Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub uname -a Linux languasc-asus 3.16.0-30-generic #40-Ubuntu SMP Mon Jan 12 22:06:37 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Any help will be greatly appreciated. Alessandro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1411193/+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 1411496] Re: [HP 15 Notebook PC] failed to render desktop so could not use 14.04.1 liveusb
** 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/1411496 Title: [HP 15 Notebook PC] failed to render desktop so could not use 14.04.1 liveusb Status in linux package in Ubuntu: Confirmed Bug description: HP 15 Notebook PC CID 201406-15266 Steps to reproduce this bug: 1. prepare an 14.04.1 live USB 2. boot the machine by the live USB Expected result: The system boot the live USB desktop and ready to use. Actual: result: The system boot to desktop but failed to render the desktop. It looks like as the attachment 201406-15266-updated-14.04.1-without-fglrx-screenshot.png More information: Please note the desktop launcher and dash rendering are fine. Please refer to 201406-15266-updated-14.04.1-without-fglrx-screenshot.png as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1411496/+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 1410519] Re: [PowerVM] Kernel BUG @ kernel/irq_work.c:157! - 24x7 hw counters
** Changed in: linux (Ubuntu) Assignee: Andy Whitcroft (apw) = (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1410519 Title: [PowerVM] Kernel BUG @ kernel/irq_work.c:157! - 24x7 hw counters Status in linux package in Ubuntu: Confirmed Status in linux source package in Utopic: Fix Committed Bug description: [Impact] Using perf with hv_24x7 events can cause a kernel BUG. [Fix] The following upstream commits: d658972 48bee8a f34b6c7 ec2aef5 [Test Case] Steps to recreate the problem: 1. Install Ubuntu 15.04 as a PowerVM guest. 2. Install perf tool 3. Run following scripts to test 24/7 Power8 hardware counter event with perf. tool === Script 1 #!/bin/bash count=0; offset=0x128 PERF_ARGS=-r 10 -C 0 while [ $count -lt 100 ]; do EVENT=hv_24x7/domain=0x2,offset=$offset,starting_index=10/ perf stat $PERF_ARGS -x ' ' perf stat $PERF_ARGS -x ' ' -e $EVENT ls count=) done Script 2 #!/bin/bash offset=0; PERF_ARGS=-r 10 -C 0 while [ $offset -lt 8192 ]; do EVENT=hv_24x7/domain=0x2,offset=$offset,starting_index=10/ perf stat $PERF_ARGS -x ' ' perf stat $PERF_ARGS -x ' ' -e $EVENT ls offset=) done After few iterations I hit the following BUG. tt2.sh tt.sh tt2.sh tt.sh tt2.sh tt.sh 275679187521558 hv_24x7/domain=0x2,offset=6848,starting_index=10/ 0.00% tt2.sh tt.sh [ 4657.314709] softirq: huh, entered softirq 7 SCHED c010abc0 with preem pt_count 0100, exited with bfff? [ 4657.314727] kernel BUG at /build/buildd/linux-3.16.0/kernel/irq_work.c:157! [ 4657.314732] Oops: Exception in kernel mode, sig: 5 [#1] [ 4657.314740] Modules linked in: rtc_generic pseries_rng [ 4657.314749] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.16.0-25-generic #33-U [ 4657.314755] task: c1375e00 ti: c13d task.ti: c13d [ 4657.314759] NIP: c01e8ffc LR: c001fe70 CTR: c0002800ic) [ 4657.314770] MSR: 80029033 SF,EE,ME,IR,DR,RI,LE CR: 28042024 XER: 000a [ 4657.314782] CFAR: c001fe6c SOFTE: 0 GPR04: 0010 009c c1424a98 0002 GPR12: 80009033 ce9a 06a3fcd0 0060 GPR16: 0020 c0e57c00 GPR20: c1595dca c1595478 0001 GPR28: c0e40380 c0e40300 c13d3590 c0e56f08 [ 4657.314832] NIP [c01e8ffc] irq_work_run+0x1c/0x30 [ 4657.314841] Call Trace: 4000 (unreliable) [ 4657.314861] [c13d34f0] [c001ff90] timer_interrupt+0xa0/0xe0 [ 4657.314871] [c13d3520] [c0002914] decrementer_common+0x114/0x180 [ 4657.314884] --- Exception: 901 at arch_local_irq_restore+0x14/0x90 [ 4657.314896] [c13d3810] [c012ed08] vprintk_emit+0x3b8/0x660 (u [ 4657.314908] [c13d38e0] [c0a02650] printk+0x84/0x98 [ 4657.314918] [c13d3910] [c00b51b4] __do_softirq+0x1e4/0x410 [ 4657.314927] [c13d3a00] [c00b57b8] irq_exit+0xf8/0x1400 [ 4657.314948] [c13d3a60] [c0002c14] doorbell_super_common+0x114/0x180 [ 4657.314963] --- Exception: a01 at plpar_hcall_norets+0x8c/0xdc [ 4657.314963] LR = check_and_cede_processor+0x34/0x5020/0x50 (unreliable) [ 4657.314997] [c13d3df0] [c084077c] cpuidle_enter_state+0x6c/0x140c0 [ 4657.315030] [c13d3f00] [c0d63ea8] start_kernel+0x500/0x51c [ 4657.315047] Instruction dump: [ 4657.315052] eba1ffe8 7c0803a6 ebc1fff0 ebe1fff8 4e800020 3c4c011f 3842c110 78290464 [ 4657.315068] 81290014 752a000f 7d380026 55291ffe 0b09 4bfffec8 6000 6000 [ 4657.315090] ---[ end trace ee202cccd2211e5d ]--- [ 4657.320224] [ 4657.362675] Unable to handle kernel paging request for data at address 0xc000 000b35515048 [ 4657.362680] Faulting instruction address: 0xc006a37c [ 4657.362684] Oops: Kernel access of bad area, sig: 11 [#2] [ 4657.362686] SMP NR_CPUS=2048 NUMA pSeries [ 4657.362695] CPU: 12 PID: 7 Comm: rcu_sched Tainted: G D 3.16.0-25- [ 4657.362699] task: c000eb581540 ti: c000eb604000 task.ti: c000eb60 [ 4657.362703] NIP: c006a37c LR: c00865a8 CTR: c006a340 [ 4657.362706] REGS: c000eb607800 TRAP: 0300 Tainted: G D (3.16.0-25-generic) [ 4657.362718] CFAR: c00865a4 DAR: c00b35515048 DSISR: 4000 SOFTE: 0 GPR00: c00865a8 c000eb607a80 c13d50f0 013d30d0 GPR08: 00cc c00b35515000 ce9a GPR12: c006a340 ce9a6c00 0001
[Kernel-packages] [Bug 1411193] Re: [Asus F200MA] bluetooth not working
Sry, the command is rfkill list -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1411193 Title: [Asus F200MA] bluetooth not working Status in linux package in Ubuntu: Incomplete Bug description: In my opinion, this is a very similar bug to https://bugs.launchpad.net/bugs/1395465 in the sense that the bluetooth indicator works but no external devices are detected. I don't know which information I should provide here so I just insert uname -a and lsusb. lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:3423 IMC Networks Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub uname -a Linux languasc-asus 3.16.0-30-generic #40-Ubuntu SMP Mon Jan 12 22:06:37 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Any help will be greatly appreciated. Alessandro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1411193/+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
@Stephan: Yes, that's totally unrelated, better open a new bug. @Tom: Just to check that the problem is the same as with the other models where the touchpad is not working: Can you post a complete dmesg here? And to all who have a touchpad where the touchpad does not work and dmesg shows lines like [ 0.870915] psmouse serio1: Failed to enable mouse on isa0060/serio1 - can you post dmesg both with the touchpad patch and without (in both cases, with the same kernel parameters)? I'd like to check whether the patch introduces that error, or whether I am looking in the wrong place. Also, I tried to put together a list of devices where the driver works/does not work, from the reports I received, it looks like this atm: Works: - UX303LN - UX303LA - R409LD - X450JN - X553MA - X200MA - K750L - N550JK - X450LD? Does not work (Failed to enable mouse on isa0060/serio1): - X550LN - R510L - X450LC Does not work: - Q501LA What I find particularly weird is that I'd expect X450JN/X450LD and X450LC to share one hardware platform. -- You 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 Released 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
[Kernel-packages] [Bug 1386534] Re: kernel dependent deterministic view crash on X startup
** Description changed: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 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 CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel
[Kernel-packages] [Bug 1411193] Re: [Asus F200MA] bluetooth not working
here I am: rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: asus-wlan: Wireless LAN Soft blocked: no Hard blocked: no 2: asus-bluetooth: Bluetooth Soft blocked: no Hard blocked: no -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1411193 Title: [Asus F200MA] bluetooth not working Status in linux package in Ubuntu: Incomplete Bug description: In my opinion, this is a very similar bug to https://bugs.launchpad.net/bugs/1395465 in the sense that the bluetooth indicator works but no external devices are detected. I don't know which information I should provide here so I just insert uname -a and lsusb. lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:3423 IMC Networks Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub uname -a Linux languasc-asus 3.16.0-30-generic #40-Ubuntu SMP Mon Jan 12 22:06:37 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Any help will be greatly appreciated. Alessandro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1411193/+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 1378744] Re: nVidia GK106GLM [Quadro K2100M] [10de:11fc] Connect to HDMI / DP port with open-source driver will cause Xorg crash
The Problem was solved when the new kernel was installed. Works now again... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1378744 Title: nVidia GK106GLM [Quadro K2100M] [10de:11fc] Connect to HDMI / DP port with open-source driver will cause Xorg crash Status in Accelerated Xorg driver for nVidia cards: Confirmed Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: CID: 201305-13527 Dell Precision M4800 Xorg would crash and restart (you will see the login screen again and again) when the HDMI / DP cable is connected to the system. Steps: 1. Install 14.04 + update (3.13.0-36), boot to desktop 2. Connect a HDMI / DP cable Expected result: * The external monitor should work Actual result: * The external monitor screen is black, and the Xorg crashed - black screen on this laptop - login screen shows up - black screen... repeat. WORKAROUND: * Install the proprietary nvidia driver I'm not sure if this should be consider as a blocker. But hey, we need to certified this I+N system with the proprietary driver, I think it's OK to not to call this a blocker. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-36-generic 3.13.0-36.63 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 7071 F pulseaudio ubuntu 7529 F pulseaudio /dev/snd/controlC1: ubuntu 7071 F pulseaudio ubuntu 7529 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Wed Oct 8 06:20:44 2014 HibernationDevice: RESUME=UUID=46ed949d-eff8-48e9-b337-6425f480cf12 InstallationDate: Installed on 2014-10-08 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Precision M4800 ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic.efi.signed root=UUID=e7f55d08-44a4-447e-8fc6-563864d60df4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-36-generic N/A linux-backports-modules-3.13.0-36-generic N/A linux-firmware 1.127.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/02/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0FVDR2 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd01/02/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn0FVDR2:rvrX02: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/nouveau/+bug/1378744/+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 1317811] Re: Dropped packets on EC2, xen_netfront: xennet: skb rides the rocket: x slots
** Description changed: Running Ubuntu 14.04 LTS on EC2, we see a lot of the following in the kernel log: xen_netfront: xennet: skb rides the rocket: 19 slots Each of these messages corresponds to a dropped TX packet, and eventually causes our application's connections to break and timeout. The problem appears when network load increases. We have Node.js processes doing pubsub with a Redis server, and these are most visibly affected, showing frequent connection loss. The processes talk to each other using the private addresses EC2 allocates to the machines. Notably, the default MTU on the network interface seems to have gone up from 1500 on 13.10, to 9000 in 14.04 LTS. Reducing the MTU back to 1500 seems to drastically reduce dropped packets. (Can't say for certain if it completely eliminates the problem.) The machines we run are started from ami-896c96fe. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: User Name 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 9 09:01 seq crw-rw 1 root audio 116, 33 May 9 09:01 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Fri May 9 09:11:18 2014 Ec2AMI: ami-896c96fe Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1c Ec2InstanceType: c3.large Ec2Kernel: aki-52a34525 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 9 09:54 seq crw-rw 1 root audio 116, 33 May 9 09:54 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 24.724129] init: plymouth-upstart-bridge main process ended, respawning DistroRelease: Ubuntu 14.04 Ec2AMI: ami-896c96fe Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1c Ec2InstanceType: c3.large Ec2Kernel: aki-52a34525 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 ProcVersionSignature: User Name 3.13.0-24.46-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video _MarkForUpload: True break-fix: - 97a6d1bb2b658ac85ed88205ccd1ab809899884d + break-fix: - 11d3d2a16cc1f05c6ece69a4392e99efb85666a6 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1317811 Title: Dropped packets on EC2, xen_netfront: xennet: skb rides the rocket: x slots Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Confirmed Status in linux source package in Utopic: Confirmed Bug description: Running Ubuntu 14.04 LTS on EC2, we see a lot of the following in the kernel log: xen_netfront: xennet: skb rides the rocket: 19 slots Each of these messages corresponds to a dropped TX packet, and eventually causes our application's connections to break and timeout. The problem appears when network load increases. We have Node.js processes doing pubsub with a Redis server, and these are most visibly affected, showing frequent
[Kernel-packages] [Bug 314572] Re: ch341 driver does not work 1a86 7523 kernel 2.6.27
if anyone have problems with ch341 drivers on Ubuntu 14.04 I have a patched driver and it works with 3.13.X kernel: https://www.mediafire.com/?3ph5x6ttc7ddde4 thanks to: http://stackoverflow.com/questions/23040820/driver-ch341-usb-adapter- serial-port-or-qserialport-not-works-in-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/314572 Title: ch341 driver does not work 1a86 7523 kernel 2.6.27 Status in linux package in Ubuntu: Expired Bug description: The modprobe ch341 fails with the following error: [ 1186.582421] usbcore: deregistering interface driver ch341 [ 1186.587506] usbserial: USB Serial deregistering driver ch341-uart [ 2260.948951] usbserial: USB Serial support registered for ch341-uart [ 2260.955430] ch341 1-1:1.0: ch341-uart converter detected [ 2261.960103] ch341: probe of 1-1:1.0 failed with error -5 [ 2261.964376] usbcore: registered new interface driver ch341 The output from lsusb is: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 1a86:7523 Bus 001 Device 003: ID 0e0f:0002 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub The cable worked fine with ubuntu 8.04 and the ch341-dkms as prescribed by: http://ubuntuforums.org/archive/index.php/t-921409.html I am running ubuntu 8.10 in vmware fusion. I also tried ubuntu 8.04 with the ch341-dkms under vmware fusion, and it also appears to have the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/314572/+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 1410909] Re: linux-armadaxp: 3.2.0-1644.63 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) = Chris J Arges (arges) -- 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/1410909 Title: linux-armadaxp: 3.2.0-1644.63 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-armadaxp source package in Precise: In Progress Bug description: This bug is for tracking the 3.2.0-1644.63 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-stable-Prepare-package-start:Wednesday, 14. January 2015 18:03 UTC kernel-stable-master-bug:1410459 kernel-stable-Certification-testing-end:Friday, 16. January 2015 07:01 UTC kernel-stable-Security-signoff-end:Friday, 16. January 2015 07:02 UTC kernel-stable-phase:PPA Testing kernel-stable-phase-changed:Friday, 16. January 2015 08:02 UTC kernel-stable-Prepare-package-end:Friday, 16. January 2015 08:02 UTC kernel-stable-Promote-to-proposed-start:Friday, 16. January 2015 08:02 UTC ppa-package-testing-start:Friday, 16. January 2015 08:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1410909/+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 1301962] Re: package update of bluez 4.98-2ubuntu7 (Precise) to 4.101-0ubuntu10 (Trusty) fails
I encounter the same issue. Is there a workaround? I am running Linux Mint 17.1 Rebecca, which is more or less 'similar' to Trusty. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1301962 Title: package update of bluez 4.98-2ubuntu7 (Precise) to 4.101-0ubuntu10 (Trusty) fails Status in bluez package in Ubuntu: New Bug description: During an upgrade of a vanilla Precise install to Trusty I've encountered already twice this issue: $ sudo dpkg --configure bluez Setting up bluez (4.101-0ubuntu10) ... reload: Method Reload with signature on interface com.ubuntu.Upstart0_6.Instance doesn't exist invoke-rc.d: initscript dbus, action force-reload failed. start: Job failed to start invoke-rc.d: initscript bluetooth, action start failed. dpkg: error processing package bluez (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: bluez To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1301962/+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 1366538] Re: Synchronisation/close /dev/sdX: i/o error on target host
Is this patch going to be incorporated soon? I have 2 USB drive that are useless until this is fixed. 'Importance' is more than medium for me! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1366538 Title: Synchronisation/close /dev/sdX: i/o error on target host Status in linux package in Ubuntu: Triaged Status in linux source package in Trusty: Triaged Status in linux source package in Utopic: Triaged Status in linux source package in Vivid: Triaged Bug description: Ubuntu 14.04.1 x86-64 wanting to unmout a pata drive (usb attached), I get this (title) Warning from libparted when gparted launches. Same issue with another pc x86-64 Errors retries then ignore, shred /dev/sdi fails: shred: /dev/sdi : pass 1/2 (random)… shred: /dev/sdi : pass 1/2 (random)…231MiB/94GiB 0 % shred: /dev/sdi : failure of fdatasync: i/o error on target host I reached to shred the drive from a 12.04.4 i386 pc with no error. Sep 7 15:07:08 nux kernel: [261448.072475] usb 5-1: new high-speed USB device number 10 using xhci_hcd Sep 7 15:07:09 nux kernel: [261448.202999] usb 5-1: New USB device found, idVendor=04cf, idProduct=8818 Sep 7 15:07:09 nux kernel: [261448.203008] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Sep 7 15:07:09 nux kernel: [261448.203013] usb 5-1: Product: USB Mass Storage Device Sep 7 15:07:09 nux kernel: [261448.203018] usb 5-1: Manufacturer: Myson Century, Inc. Sep 7 15:07:09 nux kernel: [261448.205463] usb-storage 5-1:1.0: USB Mass Storage device detected Sep 7 15:07:09 nux kernel: [261448.205673] scsi20 : usb-storage 5-1:1.0 Sep 7 15:07:10 nux kernel: [261449.206849] scsi 20:0:0:0: Direct-Access HTS72101 0G9AT00 MCZO PQ: 0 ANSI: 0 CCS Sep 7 15:07:10 nux kernel: [261449.207763] sd 20:0:0:0: Attached scsi generic sg7 type 0 Sep 7 15:07:10 nux kernel: [261449.207901] sd 20:0:0:0: [sdi] 195371568 512-byte logical blocks: (100 GB/93.1 GiB) Sep 7 15:07:10 nux kernel: [261449.208068] sd 20:0:0:0: [sdi] Write Protect is off Sep 7 15:07:10 nux kernel: [261449.208074] sd 20:0:0:0: [sdi] Mode Sense: 00 14 00 00 Sep 7 15:07:10 nux kernel: [261449.208280] sd 20:0:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Sep 7 15:07:10 nux kernel: [261449.555232] sdi: unknown partition table Sep 7 15:07:10 nux kernel: [261449.555926] sd 20:0:0:0: [sdi] Attached SCSI disk Sep 7 15:07:43 nux kernel: [261482.219026] end_request: critical target error, dev sdi, sector 0 Sep 7 15:07:52 nux kernel: [261492.015180] end_request: critical target error, dev sdi, sector 0 Sep 7 15:07:55 nux kernel: [261494.261159] end_request: critical target error, dev sdi, sector 0 Sep 7 15:16:23 nux kernel: [262003.027005] end_request: critical target error, dev sdi, sector 0 Sep 7 15:16:35 nux kernel: [262014.215352] end_request: critical target error, dev sdi, sector 0 Sep 7 15:16:35 nux kernel: [262014.859651] end_request: critical target error, dev sdi, sector 0 [EDIT: Once shreded, no error on the i386, but still same error on the 2 x86-64] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1366538/+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 1410909] Re: linux-armadaxp: 3.2.0-1644.63 -proposed tracker
Promoted to proposed: linux-armadaxp | 3.2.0-1644.63 | precise-proposed | source linux-meta-armadaxp | 3.2.0.1644.50 | precise-proposed | source ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed = Fix Released -- 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/1410909 Title: linux-armadaxp: 3.2.0-1644.63 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-armadaxp source package in Precise: In Progress Bug description: This bug is for tracking the 3.2.0-1644.63 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-stable-Prepare-package-start:Wednesday, 14. January 2015 18:03 UTC kernel-stable-master-bug:1410459 kernel-stable-Certification-testing-end:Friday, 16. January 2015 07:01 UTC kernel-stable-Security-signoff-end:Friday, 16. January 2015 07:02 UTC kernel-stable-phase:PPA Testing kernel-stable-phase-changed:Friday, 16. January 2015 08:02 UTC kernel-stable-Prepare-package-end:Friday, 16. January 2015 08:02 UTC kernel-stable-Promote-to-proposed-start:Friday, 16. January 2015 08:02 UTC ppa-package-testing-start:Friday, 16. January 2015 08:02 UTC kernel-stable-Promote-to-proposed-end:Friday, 16. January 2015 15:03 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1410909/+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 1410909] Re: linux-armadaxp: 3.2.0-1644.63 -proposed tracker
** Description changed: This bug is for tracking the 3.2.0-1644.63 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-stable-Prepare-package-start:Wednesday, 14. January 2015 18:03 UTC kernel-stable-master-bug:1410459 kernel-stable-Certification-testing-end:Friday, 16. January 2015 07:01 UTC kernel-stable-Security-signoff-end:Friday, 16. January 2015 07:02 UTC kernel-stable-phase:PPA Testing kernel-stable-phase-changed:Friday, 16. January 2015 08:02 UTC kernel-stable-Prepare-package-end:Friday, 16. January 2015 08:02 UTC kernel-stable-Promote-to-proposed-start:Friday, 16. January 2015 08:02 UTC ppa-package-testing-start:Friday, 16. January 2015 08:02 UTC + kernel-stable-Promote-to-proposed-end:Friday, 16. January 2015 15:03 UTC -- 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/1410909 Title: linux-armadaxp: 3.2.0-1644.63 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-armadaxp source package in Precise: In Progress Bug description: This bug is for tracking the 3.2.0-1644.63 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-stable-Prepare-package-start:Wednesday, 14. January 2015 18:03 UTC kernel-stable-master-bug:1410459 kernel-stable-Certification-testing-end:Friday, 16. January 2015 07:01 UTC kernel-stable-Security-signoff-end:Friday, 16. January 2015 07:02 UTC kernel-stable-phase:PPA Testing kernel-stable-phase-changed:Friday, 16. January 2015 08:02 UTC kernel-stable-Prepare-package-end:Friday, 16. January 2015 08:02 UTC kernel-stable-Promote-to-proposed-start:Friday, 16. January 2015 08:02 UTC ppa-package-testing-start:Friday, 16. January 2015 08:02 UTC kernel-stable-Promote-to-proposed-end:Friday, 16. January 2015 15:03 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1410909/+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 1410384] Re: linux: 3.13.0-45.74 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) = Chris J Arges (arges) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1410384 Title: linux: 3.13.0-45.74 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-45.74 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-stable-Prepare-package-start:Tuesday, 13. January 2015 17:34 UTC kernel-stable-phase:PPA Testing kernel-stable-phase-changed:Wednesday, 14. January 2015 02:05 UTC kernel-stable-Prepare-package-end:Wednesday, 14. January 2015 02:05 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 14. January 2015 02:05 UTC ppa-package-testing-start:Wednesday, 14. January 2015 02:05 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1410384/+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 1411193] Re: [Asus F200MA] bluetooth not working
I wonder if ath3k even loaded lsmod | grep ath3k -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1411193 Title: [Asus F200MA] bluetooth not working Status in linux package in Ubuntu: Incomplete Bug description: In my opinion, this is a very similar bug to https://bugs.launchpad.net/bugs/1395465 in the sense that the bluetooth indicator works but no external devices are detected. I don't know which information I should provide here so I just insert uname -a and lsusb. lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:3423 IMC Networks Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub uname -a Linux languasc-asus 3.16.0-30-generic #40-Ubuntu SMP Mon Jan 12 22:06:37 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Any help will be greatly appreciated. Alessandro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1411193/+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 1202998] Re: Only when using kernel parameter init=/sbin/e4rat-preload kernel panics when updating libc6
I had the same problem and managed to solve by following steps: - edit with admin rights /etc/default/grub: remove the init part from GRUB_CMDLINE_LINUX_DEFAULT line - sudo update-grub - reboot - try sudo dpkg --configure -a again, libc6 should be installed without kernel panic With this steps, e4rat is not enabled any more. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1202998 Title: Only when using kernel parameter init=/sbin/e4rat-preload kernel panics when updating libc6 Status in linux package in Ubuntu: Incomplete Bug description: Every time I update ubuntu 13.10 using sudo aptitude update sudo aptitude safe-upgrade, my pc freezes with a kernel panic: trying to kill init. The error code is ff00. So far this has happened 4 or 5 times, always when installing updates. WORKAROUND: Use default kernel parameters (e.g. remove init=/sbin /e4rat-preload ). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.10.0-3-generic 3.10.0-3.12 ProcVersionSignature: Ubuntu 3.10.0-3.12-generic 3.10.1 Uname: Linux 3.10.0-3-generic i686 ApportVersion: 2.11-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trijntje 1699 F pulseaudio Date: Fri Jul 19 11:46:13 2013 InstallationDate: Installed on 2012-11-01 (259 days ago) InstallationMedia: Ubuntu 12.10 Quantal - Build i386 LIVE Binary 20121018-21:07 Lsusb: Bus 001 Device 002: ID 0402:7675 ALi Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Acer AOD257 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.10.0-3-generic root=UUID=f2496972-ed3a-4a43-a55c-4eaa002cf2be ro verbose init=/sbin/e4rat-preload RelatedPackageVersions: linux-restricted-modules-3.10.0-3-generic N/A linux-backports-modules-3.10.0-3-generic N/A linux-firmware1.112 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-06-15 (33 days ago) dmi.bios.date: 10/21/2011 dmi.bios.vendor: INSYDE dmi.bios.version: V1.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JE06_PT dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrV1.15:bd10/21/2011:svnAcer:pnAOD257:pvrV1.15:rvnAcer:rnJE06_PT:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: AOD257 dmi.product.version: V1.15 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1202998/+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 1408495] Re: Ubiquity crashes prior to keyboard configuration in 15.04
It looks like any moving of a file which comes from the read-only
underlying filesystem. It doesn't behave the same when one deletes a
file instead of moving.
It seems like it's probably a bug in overlayfs, so I'm adding a task for
linux so the kernel team can take a look.
** Also 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/1408495
Title:
Ubiquity crashes prior to keyboard configuration in 15.04
Status in linux package in Ubuntu:
New
Status in ubiquity package in Ubuntu:
Confirmed
Status in linux source package in Vivid:
New
Status in ubiquity source package in Vivid:
Confirmed
Bug description:
As best as I can tell, if anything other than a US keyboard layout is
selected from the boot menu, ubi-console-setup will crash prior to the
keyboard configuration. The dialogue displayed says:
ubi-console-setup failed with exit code 2. Further information
maybe found in /var/log/syslog.
There are the relevant lines from /var/log/syslog:
Jan 7 23:30:39 ubuntu ubiquity:
/var/lib/dpkg/info/keyboard-configuration.config: 34160: .: Can't open
/etc/default/keyboard
Jan 7 23:30:39 ubuntu ubiquity[2323]: log-output -t ubiquity setxkbmap
-layout gb -option
Jan 7 23:30:39 ubuntu ubiquity[2323]: debconffilter_done: ubi-console-setup
(current: ubi-console-setup)
Jan 7 23:30:39 ubuntu ubiquity[2323]: dbfilter_handle_status:
('ubi-console-setup', 2)
The dialogue has 3 buttons, Quit, Continue Anyway and Try Again. If
you choose Try Again it is possible to complete the install. If you
choose Continue Anyway the installer will progress and eventually
crash completely as which point apport was able to harvest the
attached logs.
WORKAROUND: After you see the ubi-console-setup crashed dialog, open a
terminal and do
sudo rm /etc/default/keyboard
sudo mv /etc/default/keyboard.pre-ubiquity /etc/default/keyboard
then click Continue anyway in the dialog. This should prevent the
crash at the end of installation.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: ubiquity 2.21.2
ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
Uname: Linux 3.18.0-8-generic x86_64
ApportVersion: 2.15.1-0ubuntu1
Architecture: amd64
CasperVersion: 1.347
Date: Wed Jan 7 23:36:41 2015
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity
initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb
LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150107)
ProcEnviron:
LANGUAGE=en_GB.UTF-8
TERM=linux
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=en_GB.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408495/+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 1335478] Re: A new instance of IBM Domino 'bindsock' cannot bind to ports 1024 Kernel 3.13.0-29 and above
I pushed a little harder with IBM and found out that an SPR (Software Problem Report) has been opened for the issue on SUSE 12, which also exhibits the same behavior: SPR # YXYX9RA56Z Error - Unable to Bind port 443 or 80 on SUSE12. My representative quoted one of the developers as saying: There is a known issue with SLES 12 where bindsock has issues. Before we can support SLES 12 and any other newer kernel with this issue, we will have to identify the issue and get it fixed - bindsock and it's code has never changed in this area so the issue is a change in behavior in the kernel. So, there is hope that there may be a future fixpack(s)(9.0.1 FP3?) where the issue may be addressed on the bindsock side. But, as one of my favorite quotes goes, Hope? Let me tell you something, my friend. Hope is a dangerous thing. Hope can drive a man insane. It's got no use on the inside. You'd better get used to that idea. -Red, Shawshank Redemption -- You 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 Released 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 Released 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 Released Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux source package in Utopic: Fix Released 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 Released 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 1408495] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem.
From a terminal window please run:
apport-collect 1408495
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/1408495
Title:
Ubiquity crashes prior to keyboard configuration in 15.04
Status in linux package in Ubuntu:
Incomplete
Status in ubiquity package in Ubuntu:
Confirmed
Status in linux source package in Vivid:
Incomplete
Status in ubiquity source package in Vivid:
Confirmed
Bug description:
As best as I can tell, if anything other than a US keyboard layout is
selected from the boot menu, ubi-console-setup will crash prior to the
keyboard configuration. The dialogue displayed says:
ubi-console-setup failed with exit code 2. Further information
maybe found in /var/log/syslog.
There are the relevant lines from /var/log/syslog:
Jan 7 23:30:39 ubuntu ubiquity:
/var/lib/dpkg/info/keyboard-configuration.config: 34160: .: Can't open
/etc/default/keyboard
Jan 7 23:30:39 ubuntu ubiquity[2323]: log-output -t ubiquity setxkbmap
-layout gb -option
Jan 7 23:30:39 ubuntu ubiquity[2323]: debconffilter_done: ubi-console-setup
(current: ubi-console-setup)
Jan 7 23:30:39 ubuntu ubiquity[2323]: dbfilter_handle_status:
('ubi-console-setup', 2)
The dialogue has 3 buttons, Quit, Continue Anyway and Try Again. If
you choose Try Again it is possible to complete the install. If you
choose Continue Anyway the installer will progress and eventually
crash completely as which point apport was able to harvest the
attached logs.
WORKAROUND: After you see the ubi-console-setup crashed dialog, open a
terminal and do
sudo rm /etc/default/keyboard
sudo mv /etc/default/keyboard.pre-ubiquity /etc/default/keyboard
then click Continue anyway in the dialog. This should prevent the
crash at the end of installation.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: ubiquity 2.21.2
ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
Uname: Linux 3.18.0-8-generic x86_64
ApportVersion: 2.15.1-0ubuntu1
Architecture: amd64
CasperVersion: 1.347
Date: Wed Jan 7 23:36:41 2015
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity
initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb
LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150107)
ProcEnviron:
LANGUAGE=en_GB.UTF-8
TERM=linux
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=en_GB.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408495/+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 1410909] Re: linux-armadaxp: 3.2.0-1644.63 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: New = In Progress ** Changed in: kernel-sru-workflow/regression-testing Status: New = Confirmed ** Description changed: This bug is for tracking the 3.2.0-1644.63 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-stable-Prepare-package-start:Wednesday, 14. January 2015 18:03 UTC kernel-stable-master-bug:1410459 kernel-stable-Certification-testing-end:Friday, 16. January 2015 07:01 UTC kernel-stable-Security-signoff-end:Friday, 16. January 2015 07:02 UTC - kernel-stable-phase:PPA Testing - kernel-stable-phase-changed:Friday, 16. January 2015 08:02 UTC kernel-stable-Prepare-package-end:Friday, 16. January 2015 08:02 UTC kernel-stable-Promote-to-proposed-start:Friday, 16. January 2015 08:02 UTC ppa-package-testing-start:Friday, 16. January 2015 08:02 UTC kernel-stable-Promote-to-proposed-end:Friday, 16. January 2015 15:03 UTC + kernel-stable-phase:Verification Testing + kernel-stable-phase-changed:Friday, 16. January 2015 16:03 UTC + kernel-stable-Verification-testing-start:Friday, 16. January 2015 16:03 UTC + kernel-stable-Regression-testing-start:Friday, 16. January 2015 16:03 UTC -- 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/1410909 Title: linux-armadaxp: 3.2.0-1644.63 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-armadaxp source package in Precise: In Progress Bug description: This bug is for tracking the 3.2.0-1644.63 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-stable-Prepare-package-start:Wednesday, 14. January 2015 18:03 UTC kernel-stable-master-bug:1410459 kernel-stable-Certification-testing-end:Friday, 16. January 2015 07:01 UTC kernel-stable-Security-signoff-end:Friday, 16. January 2015 07:02 UTC kernel-stable-Prepare-package-end:Friday, 16. January 2015 08:02 UTC kernel-stable-Promote-to-proposed-start:Friday, 16. January 2015 08:02 UTC ppa-package-testing-start:Friday, 16. January 2015 08:02 UTC kernel-stable-Promote-to-proposed-end:Friday, 16. January 2015 15:03 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Friday, 16. January 2015 16:03 UTC kernel-stable-Verification-testing-start:Friday, 16. January 2015 16:03 UTC kernel-stable-Regression-testing-start:Friday, 16. January 2015 16:03 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1410909/+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 1411734] [NEW] bcache crash
Public bug reported: Using bcache with a 512GB SSD as cache, 4TB HDD as backing, doing a backup of the bcache device sometimes results in a kernel crash. Below is an OCR of the crash log. lsb_release -rd Description:Ubuntu 14.04.1 LTS Release:14.04 Linux goliad 3.13.0-44-generic #73-Ubuntu SMP Tue Dec 16 00:22:43 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux I have a picture of the screen as well if needed. [127032.260022] R13: 0002 R14: 8800d5e27ff0 R15: 8800d5e28000 [127032.260952] FS: () GS:88021fc8() knlGS: [127032.261880] CS: 0010 DS: ES: CR0: 8005003b [127032.262813] CR2: 0028 CR3: 00021ec0e000 CR4: 07e0 [127032.263755] Stack: [127032.264683] 8800d724f830 81084f51 BB00d5e28000 8800d724f890 [127032.265629] 81724f39 8800d5e28000 8800d724ffd8 00013480 [127032.266577] 00013480 8800d5e28000 BB00d5e28650 8800d5e27ff0 [127032.267523] Call Trace: [127032.268453] [81084f51] wq_worker_sleeping+0x11/0x90 [127032.269386] [81724f39] __schedule+0x589/0x7d0 [127032.270323] [817251a9] schedule+0x29/0x70 [127032.271260] [8106a15f] do_exit+0x6df/0xa50 [127032.272194] [B172a329] oops_end+0xa9/0x150 [127032.273115] [8171996d] no_context+0x27e/0x28b [127032.274038] [817199ed] __bad_area_nose,aphore+0x73/0x1ca [127032.274960] [81719b57] bad_area_nosemaphore+0x13/0x15 [127032.275878] [8172ccf7] __do_page_fault+0xa7/0x560 [127032.276791] [81197793] ? alloc_pages_current+0xa3/0x160 [127032.277708] [81153Bfe] ? __get_free_pages+0xe/0x50 [127032.278630] [8117083e] ? kmalloc_order_trace+0x2e/0xa0 [127032.279553] [8172d1ca] do_page_fault+0x1a/0x70 [127032.280474] [811a2941] ? __kmalloc+0x211/0x230 [127032.281390] [81729628] page_fault+0xZ8/0x30 [127032.282275] [a009a976] ? bch_htree_node_read+0x176/0x550 [bcache1 [127032.283108] [a009bf45] bch_btree_node_get+0x165/0x290 [bcache] [127032.283933] [a009c108] bch_btree_map_nodes_recurse+0x98/0x140 [bcache] [127032.284760] [a009eb90] ? bch_btree_insert_check_key+0x190/0x190 [bcache] [127032.285593] [81151947] ? mempool_free_slab+0x17/0x20 [127032.286418] [81151bb9] ? mempool_free+0x49/0x90 [127032.287233] [a009f3c9] __bch_btree_map_nodes+0x139/0x1c0 [bcache] [127032.288053] [a009eb90] ? bch_btree_insert_check_key+0x190/0x190 [bcache] [127032.288873] [81151bb9] ? mempool_free+0x49/0x90 [127032.289678] [a009f504] bch_btree_insert+0xb4/0x120 [bcache] [127032.290476] [a00a97ba] bch_data_insert_keys+0x3a/0x160 [bcache] [127032.291258] [81083a52] process_one_work+0x182/0x450 [127032.292029] [81084841] worker_thread+0x121/0x410 [127032.292786] [B1e84720] ? rescuer_thread+0x430/0x430 [127032.293523] [8108b572] kthread+0xd2/0xf0 [127032.294246] [8108b4a0] ? kthread_create_on_node+0x1c0/0x1c0 [127032.294961] [817317bc] ret_from_fork+0x7c/0xb0 [127032.295672] [8108b4a0] ? kthread_create_on_node+0xlc0/0xlc0 [127032.296374] Code: 00 48 89 e5 5d 48 8b 40 c8 48 c1 e8 02 83 e0 01 c3 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 48 8b 87 c0 03 00 00 55 48 89 e5 48 8b 40 d8 5d c3 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 [127032.298061] RIP [8108bc10] kthread_data+0x10/0x20 [127032.298853] RSP 8800d724f818 [127032.299630] CR2: ffd8 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-44-generic 3.13.0-44.73 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D3', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Fri Jan 16 10:04:07 2015 InstallationDate: Installed on 2011-08-25 (1240 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0557:2220 ATEN International Co., Ltd MachineType: Dell Inc. OptiPlex 980 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic
[Kernel-packages] [Bug 1408495] Re: Ubiquity crashes prior to keyboard configuration in 15.04
ApportVersion: 2.15.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 2119 F pulseaudio
CasperVersion: 1.347
DistroRelease: Ubuntu 15.04
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity
initrd=/casper/initrd.lz quiet splash --
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150116)
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
Package: ubiquity
PackageArchitecture: amd64
ProcEnviron:
TERM=linux
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 qxldrmfb
ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper only-ubiquity
initrd=/casper/initrd.lz quiet splash --
ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
PulseList:
Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not
accessible: Permission denied
No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-3.18.0-9-generic N/A
linux-backports-modules-3.18.0-9-generic N/A
linux-firmware1.140
RfKill:
Tags: vivid vivid ubiquity-2.21.4 ubuntu
Uname: Linux 3.18.0-9-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.7.5-20140531_171129-lamiak
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-utopic
dmi.modalias:
dmi:bvnSeaBIOS:bvr1.7.5-20140531_171129-lamiak:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-utopic:cvnQEMU:ct1:cvrpc-i440fx-utopic:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-utopic
dmi.sys.vendor: QEMU
** Tags added: apport-collected ubiquity-2.21.4
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1408495
Title:
Ubiquity crashes prior to keyboard configuration in 15.04
Status in linux package in Ubuntu:
Confirmed
Status in ubiquity package in Ubuntu:
Confirmed
Status in linux source package in Vivid:
Confirmed
Status in ubiquity source package in Vivid:
Confirmed
Bug description:
As best as I can tell, if anything other than a US keyboard layout is
selected from the boot menu, ubi-console-setup will crash prior to the
keyboard configuration. The dialogue displayed says:
ubi-console-setup failed with exit code 2. Further information
maybe found in /var/log/syslog.
There are the relevant lines from /var/log/syslog:
Jan 7 23:30:39 ubuntu ubiquity:
/var/lib/dpkg/info/keyboard-configuration.config: 34160: .: Can't open
/etc/default/keyboard
Jan 7 23:30:39 ubuntu ubiquity[2323]: log-output -t ubiquity setxkbmap
-layout gb -option
Jan 7 23:30:39 ubuntu ubiquity[2323]: debconffilter_done: ubi-console-setup
(current: ubi-console-setup)
Jan 7 23:30:39 ubuntu ubiquity[2323]: dbfilter_handle_status:
('ubi-console-setup', 2)
The dialogue has 3 buttons, Quit, Continue Anyway and Try Again. If
you choose Try Again it is possible to complete the install. If you
choose Continue Anyway the installer will progress and eventually
crash completely as which point apport was able to harvest the
attached logs.
WORKAROUND: After you see the ubi-console-setup crashed dialog, open a
terminal and do
sudo rm /etc/default/keyboard
sudo mv /etc/default/keyboard.pre-ubiquity /etc/default/keyboard
then click Continue anyway in the dialog. This should prevent the
crash at the end of installation.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: ubiquity 2.21.2
ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
Uname: Linux 3.18.0-8-generic x86_64
ApportVersion: 2.15.1-0ubuntu1
Architecture: amd64
CasperVersion: 1.347
Date: Wed Jan 7 23:36:41 2015
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity
initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb
LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150107)
ProcEnviron:
LANGUAGE=en_GB.UTF-8
TERM=linux
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=en_GB.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408495/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1408495] AlsaInfo.txt
apport information
** Attachment added: AlsaInfo.txt
https://bugs.launchpad.net/bugs/1408495/+attachment/4300046/+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/1408495
Title:
Ubiquity crashes prior to keyboard configuration in 15.04
Status in linux package in Ubuntu:
Confirmed
Status in ubiquity package in Ubuntu:
Confirmed
Status in linux source package in Vivid:
Confirmed
Status in ubiquity source package in Vivid:
Confirmed
Bug description:
As best as I can tell, if anything other than a US keyboard layout is
selected from the boot menu, ubi-console-setup will crash prior to the
keyboard configuration. The dialogue displayed says:
ubi-console-setup failed with exit code 2. Further information
maybe found in /var/log/syslog.
There are the relevant lines from /var/log/syslog:
Jan 7 23:30:39 ubuntu ubiquity:
/var/lib/dpkg/info/keyboard-configuration.config: 34160: .: Can't open
/etc/default/keyboard
Jan 7 23:30:39 ubuntu ubiquity[2323]: log-output -t ubiquity setxkbmap
-layout gb -option
Jan 7 23:30:39 ubuntu ubiquity[2323]: debconffilter_done: ubi-console-setup
(current: ubi-console-setup)
Jan 7 23:30:39 ubuntu ubiquity[2323]: dbfilter_handle_status:
('ubi-console-setup', 2)
The dialogue has 3 buttons, Quit, Continue Anyway and Try Again. If
you choose Try Again it is possible to complete the install. If you
choose Continue Anyway the installer will progress and eventually
crash completely as which point apport was able to harvest the
attached logs.
WORKAROUND: After you see the ubi-console-setup crashed dialog, open a
terminal and do
sudo rm /etc/default/keyboard
sudo mv /etc/default/keyboard.pre-ubiquity /etc/default/keyboard
then click Continue anyway in the dialog. This should prevent the
crash at the end of installation.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: ubiquity 2.21.2
ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
Uname: Linux 3.18.0-8-generic x86_64
ApportVersion: 2.15.1-0ubuntu1
Architecture: amd64
CasperVersion: 1.347
Date: Wed Jan 7 23:36:41 2015
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity
initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb
LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150107)
ProcEnviron:
LANGUAGE=en_GB.UTF-8
TERM=linux
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=en_GB.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408495/+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 1408495] CurrentDmesg.txt
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1408495/+attachment/4300050/+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/1408495
Title:
Ubiquity crashes prior to keyboard configuration in 15.04
Status in linux package in Ubuntu:
Confirmed
Status in ubiquity package in Ubuntu:
Confirmed
Status in linux source package in Vivid:
Confirmed
Status in ubiquity source package in Vivid:
Confirmed
Bug description:
As best as I can tell, if anything other than a US keyboard layout is
selected from the boot menu, ubi-console-setup will crash prior to the
keyboard configuration. The dialogue displayed says:
ubi-console-setup failed with exit code 2. Further information
maybe found in /var/log/syslog.
There are the relevant lines from /var/log/syslog:
Jan 7 23:30:39 ubuntu ubiquity:
/var/lib/dpkg/info/keyboard-configuration.config: 34160: .: Can't open
/etc/default/keyboard
Jan 7 23:30:39 ubuntu ubiquity[2323]: log-output -t ubiquity setxkbmap
-layout gb -option
Jan 7 23:30:39 ubuntu ubiquity[2323]: debconffilter_done: ubi-console-setup
(current: ubi-console-setup)
Jan 7 23:30:39 ubuntu ubiquity[2323]: dbfilter_handle_status:
('ubi-console-setup', 2)
The dialogue has 3 buttons, Quit, Continue Anyway and Try Again. If
you choose Try Again it is possible to complete the install. If you
choose Continue Anyway the installer will progress and eventually
crash completely as which point apport was able to harvest the
attached logs.
WORKAROUND: After you see the ubi-console-setup crashed dialog, open a
terminal and do
sudo rm /etc/default/keyboard
sudo mv /etc/default/keyboard.pre-ubiquity /etc/default/keyboard
then click Continue anyway in the dialog. This should prevent the
crash at the end of installation.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: ubiquity 2.21.2
ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
Uname: Linux 3.18.0-8-generic x86_64
ApportVersion: 2.15.1-0ubuntu1
Architecture: amd64
CasperVersion: 1.347
Date: Wed Jan 7 23:36:41 2015
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity
initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb
LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150107)
ProcEnviron:
LANGUAGE=en_GB.UTF-8
TERM=linux
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=en_GB.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408495/+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 1408495] CRDA.txt
apport information
** Attachment added: CRDA.txt
https://bugs.launchpad.net/bugs/1408495/+attachment/4300048/+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/1408495
Title:
Ubiquity crashes prior to keyboard configuration in 15.04
Status in linux package in Ubuntu:
Confirmed
Status in ubiquity package in Ubuntu:
Confirmed
Status in linux source package in Vivid:
Confirmed
Status in ubiquity source package in Vivid:
Confirmed
Bug description:
As best as I can tell, if anything other than a US keyboard layout is
selected from the boot menu, ubi-console-setup will crash prior to the
keyboard configuration. The dialogue displayed says:
ubi-console-setup failed with exit code 2. Further information
maybe found in /var/log/syslog.
There are the relevant lines from /var/log/syslog:
Jan 7 23:30:39 ubuntu ubiquity:
/var/lib/dpkg/info/keyboard-configuration.config: 34160: .: Can't open
/etc/default/keyboard
Jan 7 23:30:39 ubuntu ubiquity[2323]: log-output -t ubiquity setxkbmap
-layout gb -option
Jan 7 23:30:39 ubuntu ubiquity[2323]: debconffilter_done: ubi-console-setup
(current: ubi-console-setup)
Jan 7 23:30:39 ubuntu ubiquity[2323]: dbfilter_handle_status:
('ubi-console-setup', 2)
The dialogue has 3 buttons, Quit, Continue Anyway and Try Again. If
you choose Try Again it is possible to complete the install. If you
choose Continue Anyway the installer will progress and eventually
crash completely as which point apport was able to harvest the
attached logs.
WORKAROUND: After you see the ubi-console-setup crashed dialog, open a
terminal and do
sudo rm /etc/default/keyboard
sudo mv /etc/default/keyboard.pre-ubiquity /etc/default/keyboard
then click Continue anyway in the dialog. This should prevent the
crash at the end of installation.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: ubiquity 2.21.2
ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
Uname: Linux 3.18.0-8-generic x86_64
ApportVersion: 2.15.1-0ubuntu1
Architecture: amd64
CasperVersion: 1.347
Date: Wed Jan 7 23:36:41 2015
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity
initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb
LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150107)
ProcEnviron:
LANGUAGE=en_GB.UTF-8
TERM=linux
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=en_GB.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408495/+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 1408495] Dependencies.txt
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/1408495/+attachment/4300051/+files/Dependencies.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/1408495
Title:
Ubiquity crashes prior to keyboard configuration in 15.04
Status in linux package in Ubuntu:
Confirmed
Status in ubiquity package in Ubuntu:
Confirmed
Status in linux source package in Vivid:
Confirmed
Status in ubiquity source package in Vivid:
Confirmed
Bug description:
As best as I can tell, if anything other than a US keyboard layout is
selected from the boot menu, ubi-console-setup will crash prior to the
keyboard configuration. The dialogue displayed says:
ubi-console-setup failed with exit code 2. Further information
maybe found in /var/log/syslog.
There are the relevant lines from /var/log/syslog:
Jan 7 23:30:39 ubuntu ubiquity:
/var/lib/dpkg/info/keyboard-configuration.config: 34160: .: Can't open
/etc/default/keyboard
Jan 7 23:30:39 ubuntu ubiquity[2323]: log-output -t ubiquity setxkbmap
-layout gb -option
Jan 7 23:30:39 ubuntu ubiquity[2323]: debconffilter_done: ubi-console-setup
(current: ubi-console-setup)
Jan 7 23:30:39 ubuntu ubiquity[2323]: dbfilter_handle_status:
('ubi-console-setup', 2)
The dialogue has 3 buttons, Quit, Continue Anyway and Try Again. If
you choose Try Again it is possible to complete the install. If you
choose Continue Anyway the installer will progress and eventually
crash completely as which point apport was able to harvest the
attached logs.
WORKAROUND: After you see the ubi-console-setup crashed dialog, open a
terminal and do
sudo rm /etc/default/keyboard
sudo mv /etc/default/keyboard.pre-ubiquity /etc/default/keyboard
then click Continue anyway in the dialog. This should prevent the
crash at the end of installation.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: ubiquity 2.21.2
ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
Uname: Linux 3.18.0-8-generic x86_64
ApportVersion: 2.15.1-0ubuntu1
Architecture: amd64
CasperVersion: 1.347
Date: Wed Jan 7 23:36:41 2015
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity
initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb
LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150107)
ProcEnviron:
LANGUAGE=en_GB.UTF-8
TERM=linux
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=en_GB.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408495/+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 1408495] Casper.txt
apport information
** Attachment added: Casper.txt
https://bugs.launchpad.net/bugs/1408495/+attachment/4300049/+files/Casper.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/1408495
Title:
Ubiquity crashes prior to keyboard configuration in 15.04
Status in linux package in Ubuntu:
Confirmed
Status in ubiquity package in Ubuntu:
Confirmed
Status in linux source package in Vivid:
Confirmed
Status in ubiquity source package in Vivid:
Confirmed
Bug description:
As best as I can tell, if anything other than a US keyboard layout is
selected from the boot menu, ubi-console-setup will crash prior to the
keyboard configuration. The dialogue displayed says:
ubi-console-setup failed with exit code 2. Further information
maybe found in /var/log/syslog.
There are the relevant lines from /var/log/syslog:
Jan 7 23:30:39 ubuntu ubiquity:
/var/lib/dpkg/info/keyboard-configuration.config: 34160: .: Can't open
/etc/default/keyboard
Jan 7 23:30:39 ubuntu ubiquity[2323]: log-output -t ubiquity setxkbmap
-layout gb -option
Jan 7 23:30:39 ubuntu ubiquity[2323]: debconffilter_done: ubi-console-setup
(current: ubi-console-setup)
Jan 7 23:30:39 ubuntu ubiquity[2323]: dbfilter_handle_status:
('ubi-console-setup', 2)
The dialogue has 3 buttons, Quit, Continue Anyway and Try Again. If
you choose Try Again it is possible to complete the install. If you
choose Continue Anyway the installer will progress and eventually
crash completely as which point apport was able to harvest the
attached logs.
WORKAROUND: After you see the ubi-console-setup crashed dialog, open a
terminal and do
sudo rm /etc/default/keyboard
sudo mv /etc/default/keyboard.pre-ubiquity /etc/default/keyboard
then click Continue anyway in the dialog. This should prevent the
crash at the end of installation.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: ubiquity 2.21.2
ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
Uname: Linux 3.18.0-8-generic x86_64
ApportVersion: 2.15.1-0ubuntu1
Architecture: amd64
CasperVersion: 1.347
Date: Wed Jan 7 23:36:41 2015
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity
initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb
LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150107)
ProcEnviron:
LANGUAGE=en_GB.UTF-8
TERM=linux
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=en_GB.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408495/+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 1408495] ProcCpuinfo.txt
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1408495/+attachment/4300055/+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/1408495
Title:
Ubiquity crashes prior to keyboard configuration in 15.04
Status in linux package in Ubuntu:
Confirmed
Status in ubiquity package in Ubuntu:
Confirmed
Status in linux source package in Vivid:
Confirmed
Status in ubiquity source package in Vivid:
Confirmed
Bug description:
As best as I can tell, if anything other than a US keyboard layout is
selected from the boot menu, ubi-console-setup will crash prior to the
keyboard configuration. The dialogue displayed says:
ubi-console-setup failed with exit code 2. Further information
maybe found in /var/log/syslog.
There are the relevant lines from /var/log/syslog:
Jan 7 23:30:39 ubuntu ubiquity:
/var/lib/dpkg/info/keyboard-configuration.config: 34160: .: Can't open
/etc/default/keyboard
Jan 7 23:30:39 ubuntu ubiquity[2323]: log-output -t ubiquity setxkbmap
-layout gb -option
Jan 7 23:30:39 ubuntu ubiquity[2323]: debconffilter_done: ubi-console-setup
(current: ubi-console-setup)
Jan 7 23:30:39 ubuntu ubiquity[2323]: dbfilter_handle_status:
('ubi-console-setup', 2)
The dialogue has 3 buttons, Quit, Continue Anyway and Try Again. If
you choose Try Again it is possible to complete the install. If you
choose Continue Anyway the installer will progress and eventually
crash completely as which point apport was able to harvest the
attached logs.
WORKAROUND: After you see the ubi-console-setup crashed dialog, open a
terminal and do
sudo rm /etc/default/keyboard
sudo mv /etc/default/keyboard.pre-ubiquity /etc/default/keyboard
then click Continue anyway in the dialog. This should prevent the
crash at the end of installation.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: ubiquity 2.21.2
ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
Uname: Linux 3.18.0-8-generic x86_64
ApportVersion: 2.15.1-0ubuntu1
Architecture: amd64
CasperVersion: 1.347
Date: Wed Jan 7 23:36:41 2015
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity
initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb
LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150107)
ProcEnviron:
LANGUAGE=en_GB.UTF-8
TERM=linux
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=en_GB.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408495/+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 1408495] BootDmesg.txt
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1408495/+attachment/4300047/+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/1408495
Title:
Ubiquity crashes prior to keyboard configuration in 15.04
Status in linux package in Ubuntu:
Confirmed
Status in ubiquity package in Ubuntu:
Confirmed
Status in linux source package in Vivid:
Confirmed
Status in ubiquity source package in Vivid:
Confirmed
Bug description:
As best as I can tell, if anything other than a US keyboard layout is
selected from the boot menu, ubi-console-setup will crash prior to the
keyboard configuration. The dialogue displayed says:
ubi-console-setup failed with exit code 2. Further information
maybe found in /var/log/syslog.
There are the relevant lines from /var/log/syslog:
Jan 7 23:30:39 ubuntu ubiquity:
/var/lib/dpkg/info/keyboard-configuration.config: 34160: .: Can't open
/etc/default/keyboard
Jan 7 23:30:39 ubuntu ubiquity[2323]: log-output -t ubiquity setxkbmap
-layout gb -option
Jan 7 23:30:39 ubuntu ubiquity[2323]: debconffilter_done: ubi-console-setup
(current: ubi-console-setup)
Jan 7 23:30:39 ubuntu ubiquity[2323]: dbfilter_handle_status:
('ubi-console-setup', 2)
The dialogue has 3 buttons, Quit, Continue Anyway and Try Again. If
you choose Try Again it is possible to complete the install. If you
choose Continue Anyway the installer will progress and eventually
crash completely as which point apport was able to harvest the
attached logs.
WORKAROUND: After you see the ubi-console-setup crashed dialog, open a
terminal and do
sudo rm /etc/default/keyboard
sudo mv /etc/default/keyboard.pre-ubiquity /etc/default/keyboard
then click Continue anyway in the dialog. This should prevent the
crash at the end of installation.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: ubiquity 2.21.2
ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
Uname: Linux 3.18.0-8-generic x86_64
ApportVersion: 2.15.1-0ubuntu1
Architecture: amd64
CasperVersion: 1.347
Date: Wed Jan 7 23:36:41 2015
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity
initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb
LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150107)
ProcEnviron:
LANGUAGE=en_GB.UTF-8
TERM=linux
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=en_GB.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408495/+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 1408495] Lspci.txt
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1408495/+attachment/4300052/+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/1408495
Title:
Ubiquity crashes prior to keyboard configuration in 15.04
Status in linux package in Ubuntu:
Confirmed
Status in ubiquity package in Ubuntu:
Confirmed
Status in linux source package in Vivid:
Confirmed
Status in ubiquity source package in Vivid:
Confirmed
Bug description:
As best as I can tell, if anything other than a US keyboard layout is
selected from the boot menu, ubi-console-setup will crash prior to the
keyboard configuration. The dialogue displayed says:
ubi-console-setup failed with exit code 2. Further information
maybe found in /var/log/syslog.
There are the relevant lines from /var/log/syslog:
Jan 7 23:30:39 ubuntu ubiquity:
/var/lib/dpkg/info/keyboard-configuration.config: 34160: .: Can't open
/etc/default/keyboard
Jan 7 23:30:39 ubuntu ubiquity[2323]: log-output -t ubiquity setxkbmap
-layout gb -option
Jan 7 23:30:39 ubuntu ubiquity[2323]: debconffilter_done: ubi-console-setup
(current: ubi-console-setup)
Jan 7 23:30:39 ubuntu ubiquity[2323]: dbfilter_handle_status:
('ubi-console-setup', 2)
The dialogue has 3 buttons, Quit, Continue Anyway and Try Again. If
you choose Try Again it is possible to complete the install. If you
choose Continue Anyway the installer will progress and eventually
crash completely as which point apport was able to harvest the
attached logs.
WORKAROUND: After you see the ubi-console-setup crashed dialog, open a
terminal and do
sudo rm /etc/default/keyboard
sudo mv /etc/default/keyboard.pre-ubiquity /etc/default/keyboard
then click Continue anyway in the dialog. This should prevent the
crash at the end of installation.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: ubiquity 2.21.2
ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
Uname: Linux 3.18.0-8-generic x86_64
ApportVersion: 2.15.1-0ubuntu1
Architecture: amd64
CasperVersion: 1.347
Date: Wed Jan 7 23:36:41 2015
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity
initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb
LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150107)
ProcEnviron:
LANGUAGE=en_GB.UTF-8
TERM=linux
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=en_GB.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408495/+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 1408495] UbiquityDebug.txt
apport information
** Attachment added: UbiquityDebug.txt
https://bugs.launchpad.net/bugs/1408495/+attachment/4300058/+files/UbiquityDebug.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/1408495
Title:
Ubiquity crashes prior to keyboard configuration in 15.04
Status in linux package in Ubuntu:
Confirmed
Status in ubiquity package in Ubuntu:
Confirmed
Status in linux source package in Vivid:
Confirmed
Status in ubiquity source package in Vivid:
Confirmed
Bug description:
As best as I can tell, if anything other than a US keyboard layout is
selected from the boot menu, ubi-console-setup will crash prior to the
keyboard configuration. The dialogue displayed says:
ubi-console-setup failed with exit code 2. Further information
maybe found in /var/log/syslog.
There are the relevant lines from /var/log/syslog:
Jan 7 23:30:39 ubuntu ubiquity:
/var/lib/dpkg/info/keyboard-configuration.config: 34160: .: Can't open
/etc/default/keyboard
Jan 7 23:30:39 ubuntu ubiquity[2323]: log-output -t ubiquity setxkbmap
-layout gb -option
Jan 7 23:30:39 ubuntu ubiquity[2323]: debconffilter_done: ubi-console-setup
(current: ubi-console-setup)
Jan 7 23:30:39 ubuntu ubiquity[2323]: dbfilter_handle_status:
('ubi-console-setup', 2)
The dialogue has 3 buttons, Quit, Continue Anyway and Try Again. If
you choose Try Again it is possible to complete the install. If you
choose Continue Anyway the installer will progress and eventually
crash completely as which point apport was able to harvest the
attached logs.
WORKAROUND: After you see the ubi-console-setup crashed dialog, open a
terminal and do
sudo rm /etc/default/keyboard
sudo mv /etc/default/keyboard.pre-ubiquity /etc/default/keyboard
then click Continue anyway in the dialog. This should prevent the
crash at the end of installation.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: ubiquity 2.21.2
ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
Uname: Linux 3.18.0-8-generic x86_64
ApportVersion: 2.15.1-0ubuntu1
Architecture: amd64
CasperVersion: 1.347
Date: Wed Jan 7 23:36:41 2015
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity
initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb
LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150107)
ProcEnviron:
LANGUAGE=en_GB.UTF-8
TERM=linux
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=en_GB.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408495/+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 1408495] UbiquityDm.txt
apport information
** Attachment added: UbiquityDm.txt
https://bugs.launchpad.net/bugs/1408495/+attachment/4300059/+files/UbiquityDm.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/1408495
Title:
Ubiquity crashes prior to keyboard configuration in 15.04
Status in linux package in Ubuntu:
Confirmed
Status in ubiquity package in Ubuntu:
Confirmed
Status in linux source package in Vivid:
Confirmed
Status in ubiquity source package in Vivid:
Confirmed
Bug description:
As best as I can tell, if anything other than a US keyboard layout is
selected from the boot menu, ubi-console-setup will crash prior to the
keyboard configuration. The dialogue displayed says:
ubi-console-setup failed with exit code 2. Further information
maybe found in /var/log/syslog.
There are the relevant lines from /var/log/syslog:
Jan 7 23:30:39 ubuntu ubiquity:
/var/lib/dpkg/info/keyboard-configuration.config: 34160: .: Can't open
/etc/default/keyboard
Jan 7 23:30:39 ubuntu ubiquity[2323]: log-output -t ubiquity setxkbmap
-layout gb -option
Jan 7 23:30:39 ubuntu ubiquity[2323]: debconffilter_done: ubi-console-setup
(current: ubi-console-setup)
Jan 7 23:30:39 ubuntu ubiquity[2323]: dbfilter_handle_status:
('ubi-console-setup', 2)
The dialogue has 3 buttons, Quit, Continue Anyway and Try Again. If
you choose Try Again it is possible to complete the install. If you
choose Continue Anyway the installer will progress and eventually
crash completely as which point apport was able to harvest the
attached logs.
WORKAROUND: After you see the ubi-console-setup crashed dialog, open a
terminal and do
sudo rm /etc/default/keyboard
sudo mv /etc/default/keyboard.pre-ubiquity /etc/default/keyboard
then click Continue anyway in the dialog. This should prevent the
crash at the end of installation.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: ubiquity 2.21.2
ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
Uname: Linux 3.18.0-8-generic x86_64
ApportVersion: 2.15.1-0ubuntu1
Architecture: amd64
CasperVersion: 1.347
Date: Wed Jan 7 23:36:41 2015
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity
initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb
LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150107)
ProcEnviron:
LANGUAGE=en_GB.UTF-8
TERM=linux
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=en_GB.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408495/+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 1408495] UdevDb.txt
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1408495/+attachment/4300062/+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/1408495
Title:
Ubiquity crashes prior to keyboard configuration in 15.04
Status in linux package in Ubuntu:
Confirmed
Status in ubiquity package in Ubuntu:
Confirmed
Status in linux source package in Vivid:
Confirmed
Status in ubiquity source package in Vivid:
Confirmed
Bug description:
As best as I can tell, if anything other than a US keyboard layout is
selected from the boot menu, ubi-console-setup will crash prior to the
keyboard configuration. The dialogue displayed says:
ubi-console-setup failed with exit code 2. Further information
maybe found in /var/log/syslog.
There are the relevant lines from /var/log/syslog:
Jan 7 23:30:39 ubuntu ubiquity:
/var/lib/dpkg/info/keyboard-configuration.config: 34160: .: Can't open
/etc/default/keyboard
Jan 7 23:30:39 ubuntu ubiquity[2323]: log-output -t ubiquity setxkbmap
-layout gb -option
Jan 7 23:30:39 ubuntu ubiquity[2323]: debconffilter_done: ubi-console-setup
(current: ubi-console-setup)
Jan 7 23:30:39 ubuntu ubiquity[2323]: dbfilter_handle_status:
('ubi-console-setup', 2)
The dialogue has 3 buttons, Quit, Continue Anyway and Try Again. If
you choose Try Again it is possible to complete the install. If you
choose Continue Anyway the installer will progress and eventually
crash completely as which point apport was able to harvest the
attached logs.
WORKAROUND: After you see the ubi-console-setup crashed dialog, open a
terminal and do
sudo rm /etc/default/keyboard
sudo mv /etc/default/keyboard.pre-ubiquity /etc/default/keyboard
then click Continue anyway in the dialog. This should prevent the
crash at the end of installation.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: ubiquity 2.21.2
ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
Uname: Linux 3.18.0-8-generic x86_64
ApportVersion: 2.15.1-0ubuntu1
Architecture: amd64
CasperVersion: 1.347
Date: Wed Jan 7 23:36:41 2015
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity
initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb
LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150107)
ProcEnviron:
LANGUAGE=en_GB.UTF-8
TERM=linux
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=en_GB.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408495/+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 1408495] ProcInterrupts.txt
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1408495/+attachment/4300056/+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/1408495
Title:
Ubiquity crashes prior to keyboard configuration in 15.04
Status in linux package in Ubuntu:
Confirmed
Status in ubiquity package in Ubuntu:
Confirmed
Status in linux source package in Vivid:
Confirmed
Status in ubiquity source package in Vivid:
Confirmed
Bug description:
As best as I can tell, if anything other than a US keyboard layout is
selected from the boot menu, ubi-console-setup will crash prior to the
keyboard configuration. The dialogue displayed says:
ubi-console-setup failed with exit code 2. Further information
maybe found in /var/log/syslog.
There are the relevant lines from /var/log/syslog:
Jan 7 23:30:39 ubuntu ubiquity:
/var/lib/dpkg/info/keyboard-configuration.config: 34160: .: Can't open
/etc/default/keyboard
Jan 7 23:30:39 ubuntu ubiquity[2323]: log-output -t ubiquity setxkbmap
-layout gb -option
Jan 7 23:30:39 ubuntu ubiquity[2323]: debconffilter_done: ubi-console-setup
(current: ubi-console-setup)
Jan 7 23:30:39 ubuntu ubiquity[2323]: dbfilter_handle_status:
('ubi-console-setup', 2)
The dialogue has 3 buttons, Quit, Continue Anyway and Try Again. If
you choose Try Again it is possible to complete the install. If you
choose Continue Anyway the installer will progress and eventually
crash completely as which point apport was able to harvest the
attached logs.
WORKAROUND: After you see the ubi-console-setup crashed dialog, open a
terminal and do
sudo rm /etc/default/keyboard
sudo mv /etc/default/keyboard.pre-ubiquity /etc/default/keyboard
then click Continue anyway in the dialog. This should prevent the
crash at the end of installation.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: ubiquity 2.21.2
ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
Uname: Linux 3.18.0-8-generic x86_64
ApportVersion: 2.15.1-0ubuntu1
Architecture: amd64
CasperVersion: 1.347
Date: Wed Jan 7 23:36:41 2015
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity
initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb
LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150107)
ProcEnviron:
LANGUAGE=en_GB.UTF-8
TERM=linux
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=en_GB.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408495/+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 1408495] UbiquitySyslog.txt
apport information
** Attachment added: UbiquitySyslog.txt
https://bugs.launchpad.net/bugs/1408495/+attachment/4300061/+files/UbiquitySyslog.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/1408495
Title:
Ubiquity crashes prior to keyboard configuration in 15.04
Status in linux package in Ubuntu:
Confirmed
Status in ubiquity package in Ubuntu:
Confirmed
Status in linux source package in Vivid:
Confirmed
Status in ubiquity source package in Vivid:
Confirmed
Bug description:
As best as I can tell, if anything other than a US keyboard layout is
selected from the boot menu, ubi-console-setup will crash prior to the
keyboard configuration. The dialogue displayed says:
ubi-console-setup failed with exit code 2. Further information
maybe found in /var/log/syslog.
There are the relevant lines from /var/log/syslog:
Jan 7 23:30:39 ubuntu ubiquity:
/var/lib/dpkg/info/keyboard-configuration.config: 34160: .: Can't open
/etc/default/keyboard
Jan 7 23:30:39 ubuntu ubiquity[2323]: log-output -t ubiquity setxkbmap
-layout gb -option
Jan 7 23:30:39 ubuntu ubiquity[2323]: debconffilter_done: ubi-console-setup
(current: ubi-console-setup)
Jan 7 23:30:39 ubuntu ubiquity[2323]: dbfilter_handle_status:
('ubi-console-setup', 2)
The dialogue has 3 buttons, Quit, Continue Anyway and Try Again. If
you choose Try Again it is possible to complete the install. If you
choose Continue Anyway the installer will progress and eventually
crash completely as which point apport was able to harvest the
attached logs.
WORKAROUND: After you see the ubi-console-setup crashed dialog, open a
terminal and do
sudo rm /etc/default/keyboard
sudo mv /etc/default/keyboard.pre-ubiquity /etc/default/keyboard
then click Continue anyway in the dialog. This should prevent the
crash at the end of installation.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: ubiquity 2.21.2
ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
Uname: Linux 3.18.0-8-generic x86_64
ApportVersion: 2.15.1-0ubuntu1
Architecture: amd64
CasperVersion: 1.347
Date: Wed Jan 7 23:36:41 2015
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity
initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb
LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150107)
ProcEnviron:
LANGUAGE=en_GB.UTF-8
TERM=linux
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=en_GB.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408495/+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 1408495] UpstartUbiquity.txt
apport information
** Attachment added: UpstartUbiquity.txt
https://bugs.launchpad.net/bugs/1408495/+attachment/4300064/+files/UpstartUbiquity.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/1408495
Title:
Ubiquity crashes prior to keyboard configuration in 15.04
Status in linux package in Ubuntu:
Confirmed
Status in ubiquity package in Ubuntu:
Confirmed
Status in linux source package in Vivid:
Confirmed
Status in ubiquity source package in Vivid:
Confirmed
Bug description:
As best as I can tell, if anything other than a US keyboard layout is
selected from the boot menu, ubi-console-setup will crash prior to the
keyboard configuration. The dialogue displayed says:
ubi-console-setup failed with exit code 2. Further information
maybe found in /var/log/syslog.
There are the relevant lines from /var/log/syslog:
Jan 7 23:30:39 ubuntu ubiquity:
/var/lib/dpkg/info/keyboard-configuration.config: 34160: .: Can't open
/etc/default/keyboard
Jan 7 23:30:39 ubuntu ubiquity[2323]: log-output -t ubiquity setxkbmap
-layout gb -option
Jan 7 23:30:39 ubuntu ubiquity[2323]: debconffilter_done: ubi-console-setup
(current: ubi-console-setup)
Jan 7 23:30:39 ubuntu ubiquity[2323]: dbfilter_handle_status:
('ubi-console-setup', 2)
The dialogue has 3 buttons, Quit, Continue Anyway and Try Again. If
you choose Try Again it is possible to complete the install. If you
choose Continue Anyway the installer will progress and eventually
crash completely as which point apport was able to harvest the
attached logs.
WORKAROUND: After you see the ubi-console-setup crashed dialog, open a
terminal and do
sudo rm /etc/default/keyboard
sudo mv /etc/default/keyboard.pre-ubiquity /etc/default/keyboard
then click Continue anyway in the dialog. This should prevent the
crash at the end of installation.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: ubiquity 2.21.2
ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
Uname: Linux 3.18.0-8-generic x86_64
ApportVersion: 2.15.1-0ubuntu1
Architecture: amd64
CasperVersion: 1.347
Date: Wed Jan 7 23:36:41 2015
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity
initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb
LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150107)
ProcEnviron:
LANGUAGE=en_GB.UTF-8
TERM=linux
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=en_GB.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408495/+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 1408495] UbiquityPartman.txt
apport information
** Attachment added: UbiquityPartman.txt
https://bugs.launchpad.net/bugs/1408495/+attachment/4300060/+files/UbiquityPartman.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/1408495
Title:
Ubiquity crashes prior to keyboard configuration in 15.04
Status in linux package in Ubuntu:
Confirmed
Status in ubiquity package in Ubuntu:
Confirmed
Status in linux source package in Vivid:
Confirmed
Status in ubiquity source package in Vivid:
Confirmed
Bug description:
As best as I can tell, if anything other than a US keyboard layout is
selected from the boot menu, ubi-console-setup will crash prior to the
keyboard configuration. The dialogue displayed says:
ubi-console-setup failed with exit code 2. Further information
maybe found in /var/log/syslog.
There are the relevant lines from /var/log/syslog:
Jan 7 23:30:39 ubuntu ubiquity:
/var/lib/dpkg/info/keyboard-configuration.config: 34160: .: Can't open
/etc/default/keyboard
Jan 7 23:30:39 ubuntu ubiquity[2323]: log-output -t ubiquity setxkbmap
-layout gb -option
Jan 7 23:30:39 ubuntu ubiquity[2323]: debconffilter_done: ubi-console-setup
(current: ubi-console-setup)
Jan 7 23:30:39 ubuntu ubiquity[2323]: dbfilter_handle_status:
('ubi-console-setup', 2)
The dialogue has 3 buttons, Quit, Continue Anyway and Try Again. If
you choose Try Again it is possible to complete the install. If you
choose Continue Anyway the installer will progress and eventually
crash completely as which point apport was able to harvest the
attached logs.
WORKAROUND: After you see the ubi-console-setup crashed dialog, open a
terminal and do
sudo rm /etc/default/keyboard
sudo mv /etc/default/keyboard.pre-ubiquity /etc/default/keyboard
then click Continue anyway in the dialog. This should prevent the
crash at the end of installation.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: ubiquity 2.21.2
ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
Uname: Linux 3.18.0-8-generic x86_64
ApportVersion: 2.15.1-0ubuntu1
Architecture: amd64
CasperVersion: 1.347
Date: Wed Jan 7 23:36:41 2015
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity
initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb
LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150107)
ProcEnviron:
LANGUAGE=en_GB.UTF-8
TERM=linux
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=en_GB.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408495/+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 1408495] UdevLog.txt
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1408495/+attachment/4300063/+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/1408495
Title:
Ubiquity crashes prior to keyboard configuration in 15.04
Status in linux package in Ubuntu:
Confirmed
Status in ubiquity package in Ubuntu:
Confirmed
Status in linux source package in Vivid:
Confirmed
Status in ubiquity source package in Vivid:
Confirmed
Bug description:
As best as I can tell, if anything other than a US keyboard layout is
selected from the boot menu, ubi-console-setup will crash prior to the
keyboard configuration. The dialogue displayed says:
ubi-console-setup failed with exit code 2. Further information
maybe found in /var/log/syslog.
There are the relevant lines from /var/log/syslog:
Jan 7 23:30:39 ubuntu ubiquity:
/var/lib/dpkg/info/keyboard-configuration.config: 34160: .: Can't open
/etc/default/keyboard
Jan 7 23:30:39 ubuntu ubiquity[2323]: log-output -t ubiquity setxkbmap
-layout gb -option
Jan 7 23:30:39 ubuntu ubiquity[2323]: debconffilter_done: ubi-console-setup
(current: ubi-console-setup)
Jan 7 23:30:39 ubuntu ubiquity[2323]: dbfilter_handle_status:
('ubi-console-setup', 2)
The dialogue has 3 buttons, Quit, Continue Anyway and Try Again. If
you choose Try Again it is possible to complete the install. If you
choose Continue Anyway the installer will progress and eventually
crash completely as which point apport was able to harvest the
attached logs.
WORKAROUND: After you see the ubi-console-setup crashed dialog, open a
terminal and do
sudo rm /etc/default/keyboard
sudo mv /etc/default/keyboard.pre-ubiquity /etc/default/keyboard
then click Continue anyway in the dialog. This should prevent the
crash at the end of installation.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: ubiquity 2.21.2
ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
Uname: Linux 3.18.0-8-generic x86_64
ApportVersion: 2.15.1-0ubuntu1
Architecture: amd64
CasperVersion: 1.347
Date: Wed Jan 7 23:36:41 2015
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity
initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb
LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150107)
ProcEnviron:
LANGUAGE=en_GB.UTF-8
TERM=linux
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=en_GB.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408495/+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 1408495] ProcModules.txt
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1408495/+attachment/4300057/+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/1408495
Title:
Ubiquity crashes prior to keyboard configuration in 15.04
Status in linux package in Ubuntu:
Confirmed
Status in ubiquity package in Ubuntu:
Confirmed
Status in linux source package in Vivid:
Confirmed
Status in ubiquity source package in Vivid:
Confirmed
Bug description:
As best as I can tell, if anything other than a US keyboard layout is
selected from the boot menu, ubi-console-setup will crash prior to the
keyboard configuration. The dialogue displayed says:
ubi-console-setup failed with exit code 2. Further information
maybe found in /var/log/syslog.
There are the relevant lines from /var/log/syslog:
Jan 7 23:30:39 ubuntu ubiquity:
/var/lib/dpkg/info/keyboard-configuration.config: 34160: .: Can't open
/etc/default/keyboard
Jan 7 23:30:39 ubuntu ubiquity[2323]: log-output -t ubiquity setxkbmap
-layout gb -option
Jan 7 23:30:39 ubuntu ubiquity[2323]: debconffilter_done: ubi-console-setup
(current: ubi-console-setup)
Jan 7 23:30:39 ubuntu ubiquity[2323]: dbfilter_handle_status:
('ubi-console-setup', 2)
The dialogue has 3 buttons, Quit, Continue Anyway and Try Again. If
you choose Try Again it is possible to complete the install. If you
choose Continue Anyway the installer will progress and eventually
crash completely as which point apport was able to harvest the
attached logs.
WORKAROUND: After you see the ubi-console-setup crashed dialog, open a
terminal and do
sudo rm /etc/default/keyboard
sudo mv /etc/default/keyboard.pre-ubiquity /etc/default/keyboard
then click Continue anyway in the dialog. This should prevent the
crash at the end of installation.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: ubiquity 2.21.2
ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
Uname: Linux 3.18.0-8-generic x86_64
ApportVersion: 2.15.1-0ubuntu1
Architecture: amd64
CasperVersion: 1.347
Date: Wed Jan 7 23:36:41 2015
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity
initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb
LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150107)
ProcEnviron:
LANGUAGE=en_GB.UTF-8
TERM=linux
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=en_GB.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408495/+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
