[Kernel-packages] [Bug 1359052] Re: [HP Z1-G2] Realtek card reader [10ec:5249] does not work after suspended on this system
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1366841 looks like the same issue as this, which was fixed by another solution from vendor, I'm contacting vendor for advice. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1359052 Title: [HP Z1-G2] Realtek card reader [10ec:5249] does not work after suspended on this system Status in HWE Next Project: Triaged Status in HWE Next trusty series: Triaged Status in HWE Next utopic series: Triaged Status in “linux” package in Ubuntu: Triaged Status in “linux” source package in Trusty: Triaged Status in “linux” source package in Utopic: Triaged Bug description: Before suspend [ 12.896116] rtsx_pci :03:00.0: irq 47 for MSI/MSI-X [ 12.896128] rtsx_pci :03:00.0: rtsx_pci_acquire_irq: pcr->msi_en = 1, pci->irq = 47 After resume [ 89.354583] rtsx_pci :03:00.0: no hotplug settings from platform rmmod rtsx_pci modprobe rtsx_pci doesn't work Reboot [ 12.358093] rtsx_pci :03:00.0: irq 47 for MSI/MSI-X [ 12.358103] rtsx_pci :03:00.0: rtsx_pci_acquire_irq: pcr->msi_en = 1, pci->irq = 47 [ 12.455971] rtsx_pci: probe of :03:00.0 failed with error -110 Then driver cannot be loaded To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1359052/+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 1366841] Re: mfd: rtsx_pcr: Fix MSI enable error handling
https://bugs.launchpad.net/hwe-next/trusty/+bug/1359052 looks like the same issue as this, which was fixed by another solution from vendor, I'm contacting vendor for advice. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1366841 Title: mfd: rtsx_pcr: Fix MSI enable error handling Status in “linux” package in Ubuntu: In Progress Status in “linux” source package in Trusty: In Progress Status in “linux” source package in Utopic: In Progress Bug description: This patch has been submitted upstream and is queued up for inclusion in mfd-next: https://git.kernel.org/cgit/linux/kernel/git/lee/mfd.git/commit/?h =for-mfd-next&id=eb61b3276e099d937fcdae2c67aec4766bba2dc3 Please include this patch in Trusty and Utopic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1366841/+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 1346067] Re: [Dell Latitude E5440] O2 Card reader [1217:8520] could not be detected after rebooting this system
Will do, any log needed? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1346067 Title: [Dell Latitude E5440] O2 Card reader [1217:8520] could not be detected after rebooting this system Status in HWE Next Project: New Status in “linux” package in Ubuntu: In Progress Bug description: CID: 201307-14017 Dell Latitude E5440 The O2 card reader, O2 Micro, Inc. SD/MMC Card Reader Controller [1217:8520] (rev 01) is not stable on this system, the card reader cannot be detected. It works normally after reboot, but will be gone if you reboot it one more time Steps: 1. Install 14.04 + update (3.13.0-32), boot to desktop 2. Run lspci -nn to see if the card reader is there 3. Insert a SD card 4. Reboot, go through step 2 and 3 again Expected result: * Card reader should be found in lspci output, SD card should be mounted automatically Actual result: * Nothing happened, the card was not detected at all * On step 4, the card reader works, if rebooted again, it will be gone. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 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 1398 F pulseaudio /dev/snd/controlC1: ubuntu 1398 F pulseaudio CurrentDesktop: Unity Date: Mon Jul 21 04:07:31 2014 HibernationDevice: RESUME=UUID=730e0474-ac0b-4fc6-a321-6203c9b07a19 InstallationDate: Installed on 2014-07-21 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Latitude E5440 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed root=UUID=b55056b7-f859-4273-9793-12757a75c5ee ro quiet splash 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.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 01348S dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd06/26/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn01348S:rvrX02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1346067/+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 1367100] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1367100 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/1367100 Title: Right mouse button not responsive after resume from sleep Status in “linux” package in Ubuntu: Incomplete Bug description: My Apple Magic mouse does not accept right mouse button clicks after resuming from suspend. In order to make it work again I have to either - reboot the system - start a VM with Windows, and come back to Ubuntu (weired) Can't use apport-bug to report bug as there is no package associated with this To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1367100/+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 1366468] Re: 046d:0990 cannot set freq 16000 to exp 0x86-: Errors due to logitech Quickcam
/var/log/syslog activity when plugging in Logitech QuickCam® Pro 9000 under linux- image-3.17.0-031700rc4-generic_3.17.0-031700rc4.201409071935_amd64: Sep 9 06:22:50 linux kernel: [ 536.491258] usb 1-2.3: USB disconnect, device number 3 Sep 9 06:22:52 linux kernel: [ 538.480135] usb 1-2.3: new high-speed USB device number 7 using ehci-pci Sep 9 06:22:52 linux kernel: [ 538.715641] usb 1-2.3: New USB device found, idVendor=046d, idProduct=0990 Sep 9 06:22:52 linux kernel: [ 538.715647] usb 1-2.3: New USB device strings: Mfr=0, Product=0, SerialNumber=2 Sep 9 06:22:52 linux kernel: [ 538.715651] usb 1-2.3: SerialNumber: A0192EE8 Sep 9 06:22:52 linux kernel: [ 538.715984] uvcvideo: Found UVC 1.00 device (046d:0990) Sep 9 06:22:52 linux kernel: [ 538.747703] input: UVC Camera (046d:0990) as /devices/pci:00/:00:1a.7/usb1/1-2/1-2.3/1-2.3:1.0/input/input17 Sep 9 06:22:52 linux kernel: [ 539.135057] usb 1-2.3: Warning! Unlikely big volume range (=3072), cval->res is probably wrong. Sep 9 06:22:52 linux kernel: [ 539.135063] usb 1-2.3: [5] FU [Mic Capture Volume] ch = 1, val = 4608/7680/1 Sep 9 06:22:52 linux mtp-probe: checking bus 1, device 7: "/sys/devices/pci:00/:00:1a.7/usb1/1-2/1-2.3" Sep 9 06:22:52 linux mtp-probe: bus: 1, device: 7 was not an MTP device Sep 9 06:22:52 linux pulseaudio[12600]: [pulseaudio] module-alsa-card.c: Failed to find a working profile. Sep 9 06:22:52 linux pulseaudio[12600]: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="1" name="usb-046d_0990_A0192EE8-02-Q9000" card_name="alsa_card.usb-046d_0990_A0192EE8-02-Q9000" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties="module-udev-detect.discovered=1""): initialization failed. Sep 9 06:22:57 linux kernel: [ 544.208275] usb 1-2.3: 3:1: cannot get freq at ep 0x86 ** Tags added: kernel-bug-exists-upstream kernel-bug-exists- upstream-3.17.0-031700rc4 ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1366468 Title: 046d:0990 cannot set freq 16000 to exp 0x86-: Errors due to logitech Quickcam Status in “linux” package in Ubuntu: Confirmed Bug description: Cannot set freq 16000 to exp 0x86-: Errors due to logitech Quickcam. 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 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: msw2598 F pulseaudio /dev/snd/pcmC1D0c: msw2598 F...m pulseaudio /dev/snd/controlC0: msw2598 F pulseaudio CurrentDesktop: Unity Date: Sun Sep 7 06:12:28 2014 HibernationDevice: RESUME=UUID=d7e68cfe-7474-4c58-b1ce-b536dee6f3b1 InstallationDate: Installed on 2014-09-02 (4 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=e1a906cb-ef2b-4f04-8de7-0f94e4d8f0d1 ro quiet splash nomdmonddf nomdmonisw PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. 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 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.70 dmi.board.name: P45XE 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.70:bd09/30/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnP45XE: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/1366468/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More
[Kernel-packages] [Bug 1318026] Re: 05ac:8286 [MacBookPro10, 1] mouse battery indicator shows 0%
This same thing happens on 14.04 as well. Nothing better, it seems that the mouse support gets worse (permanent drop-outs of mouse functionality) The mouse is ok with another machine and other OS -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1318026 Title: 05ac:8286 [MacBookPro10,1] mouse battery indicator shows 0% Status in “linux” package in Ubuntu: Expired Bug description: Ever since the update to kernel 3.13.0-26 (today, 9.5.2014) the mouse battery indicator shows a load of 0% (before the update 57%). This happens on Apple magic mice ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-26-generic 3.13.0-26.48 ProcVersionSignature: Ubuntu 3.13.0-26.48-generic 3.13.11 Uname: Linux 3.13.0-26-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wolf 3956 F pulseaudio /dev/snd/controlC0: wolf 3956 F pulseaudio CurrentDesktop: Unity Date: Fri May 9 21:17:09 2014 HibernationDevice: RESUME=UUID=82dd2ca4-5c1e-43dc-b83e-d93e6166e5c4 InstallationDate: Installed on 2013-05-17 (356 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) MachineType: Apple Inc. MacBookPro10,1 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-26-generic root=UUID=3679e976-6405-4981-aa99-8c79d15e6aa3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-26-generic N/A linux-backports-modules-3.13.0-26-generic N/A linux-firmware 1.127.2 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-20 (19 days ago) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318026/+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 1367100] [NEW] Right mouse button not responsive after resume from sleep
Public bug reported: My Apple Magic mouse does not accept right mouse button clicks after resuming from suspend. In order to make it work again I have to either - reboot the system - start a VM with Windows, and come back to Ubuntu (weired) Can't use apport-bug to report bug as there is no package associated with this ** 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/1367100 Title: Right mouse button not responsive after resume from sleep Status in “linux” package in Ubuntu: New Bug description: My Apple Magic mouse does not accept right mouse button clicks after resuming from suspend. In order to make it work again I have to either - reboot the system - start a VM with Windows, and come back to Ubuntu (weired) Can't use apport-bug to report bug as there is no package associated with this To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1367100/+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 1346067] Re: [Dell Latitude E5440] O2 Card reader [1217:8520] could not be detected after rebooting this system
quote Peter Guo from O2Micro: "Hi Adam, Last patch release to you is our candidate version, which we will update to kernel org. But for this issue, We want to get the root cause of it. Attachment is a test patch, could you generate kernel and ask Po-Hsu Lin to check it?" @Po-Hsu, could you please test http://kernel.ubuntu.com/~adamlee/lp1346067_v3/ ? 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/1346067 Title: [Dell Latitude E5440] O2 Card reader [1217:8520] could not be detected after rebooting this system Status in HWE Next Project: New Status in “linux” package in Ubuntu: In Progress Bug description: CID: 201307-14017 Dell Latitude E5440 The O2 card reader, O2 Micro, Inc. SD/MMC Card Reader Controller [1217:8520] (rev 01) is not stable on this system, the card reader cannot be detected. It works normally after reboot, but will be gone if you reboot it one more time Steps: 1. Install 14.04 + update (3.13.0-32), boot to desktop 2. Run lspci -nn to see if the card reader is there 3. Insert a SD card 4. Reboot, go through step 2 and 3 again Expected result: * Card reader should be found in lspci output, SD card should be mounted automatically Actual result: * Nothing happened, the card was not detected at all * On step 4, the card reader works, if rebooted again, it will be gone. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 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 1398 F pulseaudio /dev/snd/controlC1: ubuntu 1398 F pulseaudio CurrentDesktop: Unity Date: Mon Jul 21 04:07:31 2014 HibernationDevice: RESUME=UUID=730e0474-ac0b-4fc6-a321-6203c9b07a19 InstallationDate: Installed on 2014-07-21 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Latitude E5440 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed root=UUID=b55056b7-f859-4273-9793-12757a75c5ee ro quiet splash 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.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 01348S dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd06/26/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn01348S:rvrX02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1346067/+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 1339340] Re: [HP Pavilion 11-h009tu x2 PC] Touchpad does not work
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1339340 Title: [HP Pavilion 11-h009tu x2 PC] Touchpad does not work Status in “linux” package in Ubuntu: Expired Bug description: Hi, I have an HP h009tux2 laptop. It has synaptic hid touchpad. The touchscreen is working as a mouse (no multitouch). The touchpad doesn't have two finger scroll or any scrolling for that matter, it doesn't even show up in touchpad section in control center. There has been no change in all these updates. Please help I am confined to windows 8 only as of now. xinput: ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ Synaptics Touch Pad V 103u5 id=11 [slave pointer (2)] ⎜ ↳ ELAN Touchscreen id=12 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ Power Button id=6 [slave keyboard (3)] ↳ Video Bus id=7 [slave keyboard (3)] ↳ Power Button id=8 [slave keyboard (3)] ↳ HP TrueVision Full HD id=9 [slave keyboard (3)] ↳ HP TrueVision Full HD Rear id=10 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=13 [slave keyboard (3)] ↳ HP Wireless hotkeys id=14 [slave keyboard (3)] ↳ HP WMI hotkeys id=15 [slave keyboard (3)] lsmod | grep hid -> hid_generic 12548 0 hid_multitouch 17407 0 hid_sensor_als 13123 0 hid_sensor_gyro_3d 13209 0 hid_sensor_accel_3d 13221 0 hid_sensor_magn_3d 13209 0 hid_sensor_trigger 12916 4 hid_sensor_gyro_3d,hid_sensor_accel_3d,hid_sensor_als,hid_sensor_magn_3d industrialio_triggered_buffer 12882 4 hid_sensor_gyro_3d,hid_sensor_accel_3d,hid_sensor_als,hid_sensor_magn_3d industrialio 54069 7 hid_sensor_trigger,hid_sensor_gyro_3d,industrialio_triggered_buffer,hid_sensor_accel_3d,hid_sensor_als,kfifo_buf,hid_sensor_magn_3d hid_sensor_iio_common 13755 4 hid_sensor_gyro_3d,hid_sensor_accel_3d,hid_sensor_als,hid_sensor_magn_3d hid_sensor_hub 19536 6 hid_sensor_trigger,hid_sensor_gyro_3d,hid_sensor_accel_3d,hid_sensor_als,hid_sensor_magn_3d,hid_sensor_iio_common usbhid 52570 0 hid 106148 4 hid_multitouch,hid_generic,hid_sensor_hub,usbhid mac_hid 13205 0 lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 009: ID 04f3:0193 Elan Microelectronics Corp. Bus 001 Device 008: ID 06cb:2239 Synaptics, Inc. Bus 001 Device 007: ID 1bcf:2c5a Sunplus Innovation Technology Inc. Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB Bus 001 Device 006: ID 8087:07dc Intel Corp. Bus 001 Device 005: ID 0483:91d1 STMicroelectronics Bus 001 Device 004: ID 1bcf:2c59 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-30-generic 3.13.0-30.54 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: saurabh2334 F pulseaudio CurrentDesktop: Unity CurrentDmesg: [ 127.814408] init: plymouth-stop pre-start process (3283) terminated with status 1 Date: Wed Jul 9 02:23:11 2014 InstallationDate: Installed on 2014-05-26 (43 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion 11 x2 Notebook PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic.efi.signed root=UUID=075740be-e639-4f27-80f6-f4f4bd42a3da ro quiet splash intel_pstate=enable acpi_backlight=vendor vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-3.13.0-30-generic N/A linux-backports-modules-3.13.0-30-generic N/A linux-firmware 1.127.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2188 dmi.board.vendor: Hewlett-Packard dmi.board.version: 36.29 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.22:bd05/23/2014:svnHewlett-Packard:pnHPPavilion11x2NotebookPC:pvr088310305E00010320100:rvnHewlett-Packard:rn2188:rvr36.29:cvnHewlett-Packard:ct10:cvrChassisVer
[Kernel-packages] [Bug 1339981] Re: [Lenovo ThinkPad T61] suspend/resume failure
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1339981 Title: [Lenovo ThinkPad T61] suspend/resume failure Status in “linux” package in Ubuntu: Expired Bug description: ubuntu 14.10 alpha ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.15.0-6-generic 3.15.0-6.11 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: frank 2262 F pulseaudio Date: Wed Jul 9 20:26:03 2014 DuplicateSignature: suspend/resume:LENOVO 766406U:7LETD0WW (2.30 ) ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=b3c58560-5981-4047-b509-e2fbb241b5b2 InstallationDate: Installed on 2014-07-09 (1 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) InterpreterPath: /usr/bin/python3.4 MachineType: LENOVO 766406U PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.15.0-6-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.15.0-6-generic N/A linux-backports-modules-3.15.0-6-generic N/A linux-firmware1.132 SourcePackage: linux Title: [LENOVO 766406U] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 02/27/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETD0WW (2.30 ) dmi.board.name: 766406U dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7LETD0WW(2.30):bd02/27/2012:svnLENOVO:pn766406U:pvrThinkPadT61:rvnLENOVO:rn766406U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 766406U dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1339981/+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 1340257] Re: brightness keys are not working.
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1340257 Title: brightness keys are not working. Status in “linux” package in Ubuntu: Expired Bug description: I am using Dell xps-l501x and i recently upgraded my ubuntu to 14.04. when i press f5, the brightness increases and when i press f5 to decrease, it reaches maximum. In the touch panel which has 3 buttons, the middle button performs the action which was supposed to be the function of f4 !! please help me debug this problem as i am new to the ubuntu world. Thank you :) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.56 ProcVersionSignature: Ubuntu 3.13.0-32.56-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: pruthvi2464 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 10 20:35:13 2014 InstallationDate: Installed on 2014-02-21 (138 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. XPS L501X ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=0bd76ea8-c534-46c2-b398-603109807bee ro GRUB_CMDLINE_LINUX_DEFAULT=quiet splash acpi_backlight=vendor 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.4 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-07-08 (1 days ago) dmi.bios.date: 03/29/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A07 dmi.modalias: dmi:bvnDellInc.:bvrA07:bd03/29/2011:svnDellInc.:pnXPSL501X:pvrA07:rvnDellInc.:rn:rvrA07:cvnDellInc.:ct8:cvrA07: dmi.product.name: XPS L501X dmi.product.version: A07 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1340257/+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 1362199] Re: [FFe] apparmor abstract, anonymous and netlink socket mediation
This bug was fixed in the package apparmor - 2.8.96~2652-0ubuntu3 --- apparmor (2.8.96~2652-0ubuntu3) utopic; urgency=medium * 08-phpsysinfo-policy-updates.patch: update for new phpsysinfo on Ubuntu 14.10 * 09-apache2-policy-instructions.patch: update for recent Debian/Ubuntu packaging * debian/control: update Breaks for apparmor-easyprof-ubuntu, libvirt-bin, and lightdm. Add Breaks on rsyslog. apparmor (2.8.96~2652-0ubuntu2) utopic; urgency=medium * 07-parser-fix_local_perms.patch: do not output local permissions for rules that have peer_conditionals. Patch from John Johansen apparmor (2.8.96~2652-0ubuntu1) utopic; urgency=medium * Updated to r2652 snapshot of 2.8.96 (LP: #1362199, LP: #1341152) [ Steve Beattie ] * removed upstreamed patches: - dnsmasq-libvirtd-signal-ptrace.patch - update-base-abstraction-for-signals-and-ptrace.patch - update-nameservice-abstraction-for-extrausers.patch - debian/apparmor-profiles.install: dropped program-chunks/postfix-common, moved to abstractions/ and covered by apparmor.install - refreshed libapparmor-layout-deb.patch patch * Add in Tyler Hicks' regression test improvements: - 01-tests-unix_socket_lists.patch, - 02-tests-accept_unix_rules_in_mkprofile.patch, - 03-tests-unix_sockets_v7_pathnames.patch, - 04-tests-migrate_from_poll_to_sockio_timeout.patch, - 05-tests-add_abstract_socket_tests.patch, * 07-parser-fix_local_perms.patch: do not output local permissions for rules that have peer_conditionals [ Jamie Strandboge ] * add-chromium-browser.patch: update for unix socket mediation * drop-peer_addr-with-local-addr-in-base.patch: don't use peer=(addr=none) with getattr, getopt, setopt and shutdown [ Tyler Hicks ] * debian/lib/apparmor/functions, debian/apparmor.init, debian/apparmor.upstart: Ensure system policy cache cannot become stale after image based upgrades that update the system profiles (LP: #1350673) * parser-include-usr-share-apparmor.patch, debian/apparmor.install: Adjust the default parser.conf file, to add /usr/share/apparmor as an additional search path when resolving include directives in profiles, and install the file in /etc/apparmor. Ubuntu places hardware specific access rules in /usr/share/apparmor/hardware. This change allows these files to be included without using an absolute path (e.g., '#include '). -- Jamie StrandbogeMon, 08 Sep 2014 16:13:10 -0500 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1362199 Title: [FFe] apparmor abstract, anonymous and netlink socket mediation Status in “apparmor” package in Ubuntu: Fix Released Status in “apparmor-easyprof-ubuntu” package in Ubuntu: Fix Released Status in “isc-dhcp” package in Ubuntu: Fix Released Status in “libvirt” package in Ubuntu: Fix Released Status in “lightdm” package in Ubuntu: Fix Released Status in “linux” package in Ubuntu: In Progress Status in “rsyslog” package in Ubuntu: Fix Released Status in “tlsdate” package in Ubuntu: In Progress Bug description: Background: kernel and apparmor userspace updates to support abstract, anonymous and fine-grained netlink socket mediation. These packages are listed in one bug because they are related, but the FFes may be granted and the uploads may happen at different times. = apparmor userspace = Summary: This feature freeze exception is requested for abstract, anonymous and fine-grained netlink socket for apparmor userspace. When used with a compatible kernel, 'unix' and 'network netlink' rules are supported. When used without a compatible apparmor userspace (eg, on a trusty system with an utopic backport kernel), abstract, anonymous and fine-grained netlink socket mediation is not enforced (ie, you can use this userspace with an old kernel without any issues). Testing: * 14.10 system with current kernels lacking abstract, anonymous and fine-grained netlink socket mediation (non-Touch): * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: DONE (exploratory manual testing, lxc, libvirt, etc) * 14.10 system kernel capable of supporting abstract, anonymous and fine-grained netlink socket mediation (non-Touch): * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: INPROGRESS (includes test-apparmor.py, exploratory manual testing, lxc, libvirt, etc) * Verify everything in https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/AppArmorProfiles: DONE (except juju since it doesn't have policy itself) Justification: This feature is required to support comprehensive application confinement on Ubuntu Touch. This feature adds a security benefit to libvirt's qemu guest isolation which is fundamental to Ubuntu on Server/Cloud. This feature also adds a welcome improvement to administrators wishing to further protect their
[Kernel-packages] [Bug 1173655] Re: Ubuntu 13.04 - ubiquity crash due to the wifi broadcom driver
** Tags added: ubi-wireless -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1173655 Title: Ubuntu 13.04 - ubiquity crash due to the wifi broadcom driver Status in “bcmwl” package in Ubuntu: Confirmed Status in “ubiquity” package in Ubuntu: Confirmed Status in “bcmwl” source package in Precise: Confirmed Status in “ubiquity” source package in Precise: Confirmed Status in “bcmwl” source package in Trusty: Confirmed Status in “ubiquity” source package in Trusty: Confirmed Bug description: During 13.04 Live installation (I tried UBUNTU, UBUNTU GNOME and LUBUNTU), system crash because the WiFi Broadcom driver. It happen when system try to install and configure bcmwl-kernel- source, so I can't finish to install system successfully. I tried by minimal installation (http://archive.ubuntu.com/ubuntu/dists/raring/main/installer-i386/current/images/netboot/mini.iso): installed ubuntu-desktop and everything ok, but after reboot I tried to install WiFi Broadcom driver and system crash again and it become instable, for example it can't turn off. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ubiquity 2.14.6 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 CasperVersion: 1.331 Date: Sat Apr 27 16:58:06 2013 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- debian-installer/language=it keyboard-configuration/layoutcode?=it LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1173655/+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 1362199] Re: [FFe] apparmor abstract, anonymous and netlink socket mediation
This bug was fixed in the package apparmor-easyprof-ubuntu - 1.2.22
---
apparmor-easyprof-ubuntu (1.2.22) utopic; urgency=medium
* Updates for abstract and anonymous socket mediation (LP: #1362199):
- ubuntu/*/ubuntu-*:
+ use dbus-strict and dbus-session-strict abstractions and remove
duplicated policy
+ allow ubuntu-sdk and ubuntu-webapp connect, receive and send on the
maliit abstract socket
+ allow write access to owner /{,var/}run/user/*/@{APP_PKGNAME}/{,**}
- ubuntu/*/unconfined: allow unix
- ubuntu/webview:
+ allow oxide to talk to sandbox via unix sockets
+ allow sandbox to talk to @{APP_PKGNAME}_@{APP_APPNAME}_@{APP_VERSION}
peer
+ allow various unix perms from base abstract for the sandbox to use
unix sockets
- debian/control: Depends on apparmor >= 2.8.96~2541-0ubuntu4
* ubuntu/webview: use @{APP_PKGNAME}_@{APP_APPNAME}_@{APP_VERSION} for
signal now that we have @{APP_APPNAME} available (LP: #1363112)
* ubuntu/debug: 'audit deny @{HOME}/.local/share/ r' which is used by the
SDK to see if confined
* debian/control: Depends on apparmor >= 2.8.96~2541-0ubuntu4~
-- Jamie StrandbogeFri, 05 Sep 2014 15:17:07 -0500
** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
Status: In Progress => Fix Released
** Changed in: apparmor (Ubuntu)
Status: In Progress => 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/1362199
Title:
[FFe] apparmor abstract, anonymous and netlink socket mediation
Status in “apparmor” package in Ubuntu:
Fix Released
Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
Fix Released
Status in “isc-dhcp” package in Ubuntu:
Fix Released
Status in “libvirt” package in Ubuntu:
Fix Released
Status in “lightdm” package in Ubuntu:
Fix Released
Status in “linux” package in Ubuntu:
In Progress
Status in “rsyslog” package in Ubuntu:
Fix Released
Status in “tlsdate” package in Ubuntu:
In Progress
Bug description:
Background: kernel and apparmor userspace updates to support abstract,
anonymous and fine-grained netlink socket mediation. These packages
are listed in one bug because they are related, but the FFes may be
granted and the uploads may happen at different times.
= apparmor userspace =
Summary:
This feature freeze exception is requested for abstract, anonymous and
fine-grained netlink socket for apparmor userspace. When used with a compatible
kernel, 'unix' and 'network netlink' rules are supported. When used without a
compatible apparmor userspace (eg, on a trusty system with an utopic backport
kernel), abstract, anonymous and fine-grained netlink socket mediation is not
enforced (ie, you can use this userspace with an old kernel without any issues).
Testing:
* 14.10 system with current kernels lacking abstract, anonymous and
fine-grained netlink socket mediation (non-Touch):
* https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: DONE
(exploratory manual testing, lxc, libvirt, etc)
* 14.10 system kernel capable of supporting abstract, anonymous and
fine-grained netlink socket mediation (non-Touch):
* https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: INPROGRESS
(includes test-apparmor.py, exploratory manual testing, lxc, libvirt, etc)
* Verify everything in
https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/AppArmorProfiles: DONE
(except juju since it doesn't have policy itself)
Justification:
This feature is required to support comprehensive application confinement on
Ubuntu Touch. This feature adds a security benefit to libvirt's qemu guest
isolation which is fundamental to Ubuntu on Server/Cloud. This feature also
adds a welcome improvement to administrators wishing to further protect their
systems.
Extra information:
While the apparmor userspace and kernel changes to support abstract,
anonymous and fine-grained netlink socket can happen at different times, the
apparmor userspace upload must correspond with uploads for packages that ship
AppArmor policy that require updates (eg, libvirt, lightdm, etc). The packages
outlined in https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/AppArmorProfiles
have been tested to either work without modification to the policy or updated
and tested to work with updated policy. Common rules will be added to the
apparmor base abstraction such that most packages shipping apparmor policy will
not require updating. These updates will be prepared, tested and published en
masse via a silo ppa.
= linux =
Summary:
This feature freeze exception is requested for abstract, anonymous and
fine-grained netlink socket via apparmor in the kernel. When used with a
compatible apparmor userspace, 'unix' and 'network netlink' rules are
supported. When used without a compatible apparmor userspace (eg, on a trusty
sys
[Kernel-packages] [Bug 1362199] Re: [FFe] apparmor abstract, anonymous and netlink socket mediation
This bug was fixed in the package rsyslog - 7.4.4-1ubuntu9 --- rsyslog (7.4.4-1ubuntu9) utopic; urgency=medium * debian/usr.sbin.rsyslog: update for abstract socket mediation (LP: #1362199) * debian/control: Suggests apparmor >= 2.8.96~2541-0ubuntu4~ -- Jamie StrandbogeThu, 04 Sep 2014 09:45:43 -0500 ** Changed in: rsyslog (Ubuntu) Status: In Progress => 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/1362199 Title: [FFe] apparmor abstract, anonymous and netlink socket mediation Status in “apparmor” package in Ubuntu: In Progress Status in “apparmor-easyprof-ubuntu” package in Ubuntu: In Progress Status in “isc-dhcp” package in Ubuntu: Fix Released Status in “libvirt” package in Ubuntu: Fix Released Status in “lightdm” package in Ubuntu: Fix Released Status in “linux” package in Ubuntu: In Progress Status in “rsyslog” package in Ubuntu: Fix Released Status in “tlsdate” package in Ubuntu: In Progress Bug description: Background: kernel and apparmor userspace updates to support abstract, anonymous and fine-grained netlink socket mediation. These packages are listed in one bug because they are related, but the FFes may be granted and the uploads may happen at different times. = apparmor userspace = Summary: This feature freeze exception is requested for abstract, anonymous and fine-grained netlink socket for apparmor userspace. When used with a compatible kernel, 'unix' and 'network netlink' rules are supported. When used without a compatible apparmor userspace (eg, on a trusty system with an utopic backport kernel), abstract, anonymous and fine-grained netlink socket mediation is not enforced (ie, you can use this userspace with an old kernel without any issues). Testing: * 14.10 system with current kernels lacking abstract, anonymous and fine-grained netlink socket mediation (non-Touch): * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: DONE (exploratory manual testing, lxc, libvirt, etc) * 14.10 system kernel capable of supporting abstract, anonymous and fine-grained netlink socket mediation (non-Touch): * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: INPROGRESS (includes test-apparmor.py, exploratory manual testing, lxc, libvirt, etc) * Verify everything in https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/AppArmorProfiles: DONE (except juju since it doesn't have policy itself) Justification: This feature is required to support comprehensive application confinement on Ubuntu Touch. This feature adds a security benefit to libvirt's qemu guest isolation which is fundamental to Ubuntu on Server/Cloud. This feature also adds a welcome improvement to administrators wishing to further protect their systems. Extra information: While the apparmor userspace and kernel changes to support abstract, anonymous and fine-grained netlink socket can happen at different times, the apparmor userspace upload must correspond with uploads for packages that ship AppArmor policy that require updates (eg, libvirt, lightdm, etc). The packages outlined in https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/AppArmorProfiles have been tested to either work without modification to the policy or updated and tested to work with updated policy. Common rules will be added to the apparmor base abstraction such that most packages shipping apparmor policy will not require updating. These updates will be prepared, tested and published en masse via a silo ppa. = linux = Summary: This feature freeze exception is requested for abstract, anonymous and fine-grained netlink socket via apparmor in the kernel. When used with a compatible apparmor userspace, 'unix' and 'network netlink' rules are supported. When used without a compatible apparmor userspace (eg, on a trusty system with an utopic backport kernel), abstract, anonymous and fine-grained netlink socket mediation is not enforced (ie, you can use this kernel with an old userspace without any issues). Testing: * 14.04 system with backported kernel: TODO * test-apparmor.py: TODO (runs extensive tests (upstream and distro)) * exploratory manual testing: TODO (networking, aa-enforce with firefox, firefox works, apparmor blocks access, etc) * aa-status: TODO * lxc: TODO (containers can be created, started, shutdown) * libvirt: TODO (VMs started via openstack, and test-libvirt.py from QRT passes all tests) * 14.10 system (non-Touch) with updated kernel: * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: INPROGRESS (includes click-apparmor, apparmor-easyprof-ubuntu, exploratory manual testing, etc) * 14.10 system (Touch) with updated kernel: * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: INPROGRESS (includes click-apparmor, apparmor-easyprof-ubuntu, exploratory manua
[Kernel-packages] [Bug 1366432] Re: [Dell Latitude E6400] System crashes after opening laptop from suspend
kernel-fixed-upstream-3.17-rc4-lowlatency (current version installed for testing, confirmed by uname -a) Bug appears to be fixed. Recovery from suspend is working correctly and quickly, whether initiated by the pull-down menu or by closing the lid. Thank you for your patience through this process. Do I retain this kernel on my machine, or do I need to obtain a newer Edubuntu for a reinstall? ** Tags removed: needs-upstream-testing ** Tags added: kernel-fixed-upstream ** Tags added: kernel-fixed-upstream-3.17-rc3-lowlatency ** Tags removed: kernel-fixed-upstream-3.17-rc3-lowlatency ** Tags added: kernel-fixed-upstream-3.17-rc4-lowlatency ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1366432 Title: [Dell Latitude E6400] System crashes after opening laptop from suspend Status in “linux” package in Ubuntu: Confirmed Bug description: Fresh install of edubuntu 14.04 LTS on a laptop Dell latitude E6400; rather than allowing the user to log back in, the laptop crashes after closing and opening the lid. Shows a login screen as if the computer is locked, but the keyboard does not respond. Mouse pad allows movement of the cursor, but clicking on icons to try to shut down properly does not work. Must use power button to perform a hard reboot. Thus far has been a problem on two of these laptops with the same edubuntu install. Used ubuntu-bug linux command to generate this report. 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.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: godric 2003 F pulseaudio CurrentDesktop: Unity Date: Sat Sep 6 19:37:02 2014 HibernationDevice: RESUME=UUID=df6c4b8f-2f59-4284-81cc-48c0eb82db87 InstallationDate: Installed on 2014-08-20 (17 days ago) InstallationMedia: Edubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.1) MachineType: Dell Inc. Latitude E6400 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=1f0591c4-22b7-4e75-bb4f-01762eafcb99 ro quiet splash 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: 05/11/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0U695R dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd05/11/2009:svnDellInc.:pnLatitudeE6400:pvr:rvnDellInc.:rn0U695R:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude E6400 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1366432/+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 1362199] Re: [FFe] apparmor abstract, anonymous and netlink socket mediation
This bug was fixed in the package lightdm - 1.11.8-0ubuntu2 --- lightdm (1.11.8-0ubuntu2) utopic; urgency=medium * debian/patches/06_apparmor-unix.patch: updates for unix socket mediation (LP: #1362199) -- Jamie StrandbogeFri, 05 Sep 2014 17:34:03 -0500 ** Changed in: lightdm (Ubuntu) Status: In Progress => 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/1362199 Title: [FFe] apparmor abstract, anonymous and netlink socket mediation Status in “apparmor” package in Ubuntu: In Progress Status in “apparmor-easyprof-ubuntu” package in Ubuntu: In Progress Status in “isc-dhcp” package in Ubuntu: Fix Released Status in “libvirt” package in Ubuntu: Fix Released Status in “lightdm” package in Ubuntu: Fix Released Status in “linux” package in Ubuntu: In Progress Status in “rsyslog” package in Ubuntu: In Progress Status in “tlsdate” package in Ubuntu: In Progress Bug description: Background: kernel and apparmor userspace updates to support abstract, anonymous and fine-grained netlink socket mediation. These packages are listed in one bug because they are related, but the FFes may be granted and the uploads may happen at different times. = apparmor userspace = Summary: This feature freeze exception is requested for abstract, anonymous and fine-grained netlink socket for apparmor userspace. When used with a compatible kernel, 'unix' and 'network netlink' rules are supported. When used without a compatible apparmor userspace (eg, on a trusty system with an utopic backport kernel), abstract, anonymous and fine-grained netlink socket mediation is not enforced (ie, you can use this userspace with an old kernel without any issues). Testing: * 14.10 system with current kernels lacking abstract, anonymous and fine-grained netlink socket mediation (non-Touch): * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: DONE (exploratory manual testing, lxc, libvirt, etc) * 14.10 system kernel capable of supporting abstract, anonymous and fine-grained netlink socket mediation (non-Touch): * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: INPROGRESS (includes test-apparmor.py, exploratory manual testing, lxc, libvirt, etc) * Verify everything in https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/AppArmorProfiles: DONE (except juju since it doesn't have policy itself) Justification: This feature is required to support comprehensive application confinement on Ubuntu Touch. This feature adds a security benefit to libvirt's qemu guest isolation which is fundamental to Ubuntu on Server/Cloud. This feature also adds a welcome improvement to administrators wishing to further protect their systems. Extra information: While the apparmor userspace and kernel changes to support abstract, anonymous and fine-grained netlink socket can happen at different times, the apparmor userspace upload must correspond with uploads for packages that ship AppArmor policy that require updates (eg, libvirt, lightdm, etc). The packages outlined in https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/AppArmorProfiles have been tested to either work without modification to the policy or updated and tested to work with updated policy. Common rules will be added to the apparmor base abstraction such that most packages shipping apparmor policy will not require updating. These updates will be prepared, tested and published en masse via a silo ppa. = linux = Summary: This feature freeze exception is requested for abstract, anonymous and fine-grained netlink socket via apparmor in the kernel. When used with a compatible apparmor userspace, 'unix' and 'network netlink' rules are supported. When used without a compatible apparmor userspace (eg, on a trusty system with an utopic backport kernel), abstract, anonymous and fine-grained netlink socket mediation is not enforced (ie, you can use this kernel with an old userspace without any issues). Testing: * 14.04 system with backported kernel: TODO * test-apparmor.py: TODO (runs extensive tests (upstream and distro)) * exploratory manual testing: TODO (networking, aa-enforce with firefox, firefox works, apparmor blocks access, etc) * aa-status: TODO * lxc: TODO (containers can be created, started, shutdown) * libvirt: TODO (VMs started via openstack, and test-libvirt.py from QRT passes all tests) * 14.10 system (non-Touch) with updated kernel: * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: INPROGRESS (includes click-apparmor, apparmor-easyprof-ubuntu, exploratory manual testing, etc) * 14.10 system (Touch) with updated kernel: * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: INPROGRESS (includes click-apparmor, apparmor-easyprof-ubuntu, exploratory manual testing, etc) Justification: This feature i
[Kernel-packages] [Bug 1362199] Re: [FFe] apparmor abstract, anonymous and netlink socket mediation
This bug was fixed in the package libvirt - 1.2.6-0ubuntu6
---
libvirt (1.2.6-0ubuntu6) utopic; urgency=medium
* debian/apparmor/usr.sbin.libvirtd: update for abstract socket mediation
(LP: #1362199)
* debian/apparmor/libvirt-qemu: allow 'r' on @{PROC}/sys/kernel/cap_last_cap
* debian/control: Suggests apparmor >= 2.8.96~2541-0ubuntu4~
-- Jamie StrandbogeFri, 05 Sep 2014 17:32:16 -0500
** Changed in: libvirt (Ubuntu)
Status: In Progress => 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/1362199
Title:
[FFe] apparmor abstract, anonymous and netlink socket mediation
Status in “apparmor” package in Ubuntu:
In Progress
Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
In Progress
Status in “isc-dhcp” package in Ubuntu:
Fix Released
Status in “libvirt” package in Ubuntu:
Fix Released
Status in “lightdm” package in Ubuntu:
Fix Released
Status in “linux” package in Ubuntu:
In Progress
Status in “rsyslog” package in Ubuntu:
In Progress
Status in “tlsdate” package in Ubuntu:
In Progress
Bug description:
Background: kernel and apparmor userspace updates to support abstract,
anonymous and fine-grained netlink socket mediation. These packages
are listed in one bug because they are related, but the FFes may be
granted and the uploads may happen at different times.
= apparmor userspace =
Summary:
This feature freeze exception is requested for abstract, anonymous and
fine-grained netlink socket for apparmor userspace. When used with a compatible
kernel, 'unix' and 'network netlink' rules are supported. When used without a
compatible apparmor userspace (eg, on a trusty system with an utopic backport
kernel), abstract, anonymous and fine-grained netlink socket mediation is not
enforced (ie, you can use this userspace with an old kernel without any issues).
Testing:
* 14.10 system with current kernels lacking abstract, anonymous and
fine-grained netlink socket mediation (non-Touch):
* https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: DONE
(exploratory manual testing, lxc, libvirt, etc)
* 14.10 system kernel capable of supporting abstract, anonymous and
fine-grained netlink socket mediation (non-Touch):
* https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: INPROGRESS
(includes test-apparmor.py, exploratory manual testing, lxc, libvirt, etc)
* Verify everything in
https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/AppArmorProfiles: DONE
(except juju since it doesn't have policy itself)
Justification:
This feature is required to support comprehensive application confinement on
Ubuntu Touch. This feature adds a security benefit to libvirt's qemu guest
isolation which is fundamental to Ubuntu on Server/Cloud. This feature also
adds a welcome improvement to administrators wishing to further protect their
systems.
Extra information:
While the apparmor userspace and kernel changes to support abstract,
anonymous and fine-grained netlink socket can happen at different times, the
apparmor userspace upload must correspond with uploads for packages that ship
AppArmor policy that require updates (eg, libvirt, lightdm, etc). The packages
outlined in https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/AppArmorProfiles
have been tested to either work without modification to the policy or updated
and tested to work with updated policy. Common rules will be added to the
apparmor base abstraction such that most packages shipping apparmor policy will
not require updating. These updates will be prepared, tested and published en
masse via a silo ppa.
= linux =
Summary:
This feature freeze exception is requested for abstract, anonymous and
fine-grained netlink socket via apparmor in the kernel. When used with a
compatible apparmor userspace, 'unix' and 'network netlink' rules are
supported. When used without a compatible apparmor userspace (eg, on a trusty
system with an utopic backport kernel), abstract, anonymous and fine-grained
netlink socket mediation is not enforced (ie, you can use this kernel with an
old userspace without any issues).
Testing:
* 14.04 system with backported kernel: TODO
* test-apparmor.py: TODO (runs extensive tests (upstream and distro))
* exploratory manual testing: TODO (networking, aa-enforce with firefox,
firefox works, apparmor blocks access, etc)
* aa-status: TODO
* lxc: TODO (containers can be created, started, shutdown)
* libvirt: TODO (VMs started via openstack, and test-libvirt.py from QRT
passes all tests)
* 14.10 system (non-Touch) with updated kernel:
* https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: INPROGRESS
(includes click-apparmor, apparmor-easyprof-ubuntu, exploratory manual testing,
etc)
* 14.10 system (Touch) with updated kernel:
* https://wiki.ubuntu.com/Process/Merges/TestPlans/App
[Kernel-packages] [Bug 1362199] Re: [FFe] apparmor abstract, anonymous and netlink socket mediation
** Branch linked: lp:ubuntu/utopic-proposed/lightdm ** Branch linked: lp:ubuntu/utopic-proposed/rsyslog -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1362199 Title: [FFe] apparmor abstract, anonymous and netlink socket mediation Status in “apparmor” package in Ubuntu: In Progress Status in “apparmor-easyprof-ubuntu” package in Ubuntu: In Progress Status in “isc-dhcp” package in Ubuntu: Fix Released Status in “libvirt” package in Ubuntu: In Progress Status in “lightdm” package in Ubuntu: In Progress Status in “linux” package in Ubuntu: In Progress Status in “rsyslog” package in Ubuntu: In Progress Status in “tlsdate” package in Ubuntu: In Progress Bug description: Background: kernel and apparmor userspace updates to support abstract, anonymous and fine-grained netlink socket mediation. These packages are listed in one bug because they are related, but the FFes may be granted and the uploads may happen at different times. = apparmor userspace = Summary: This feature freeze exception is requested for abstract, anonymous and fine-grained netlink socket for apparmor userspace. When used with a compatible kernel, 'unix' and 'network netlink' rules are supported. When used without a compatible apparmor userspace (eg, on a trusty system with an utopic backport kernel), abstract, anonymous and fine-grained netlink socket mediation is not enforced (ie, you can use this userspace with an old kernel without any issues). Testing: * 14.10 system with current kernels lacking abstract, anonymous and fine-grained netlink socket mediation (non-Touch): * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: DONE (exploratory manual testing, lxc, libvirt, etc) * 14.10 system kernel capable of supporting abstract, anonymous and fine-grained netlink socket mediation (non-Touch): * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: INPROGRESS (includes test-apparmor.py, exploratory manual testing, lxc, libvirt, etc) * Verify everything in https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/AppArmorProfiles: DONE (except juju since it doesn't have policy itself) Justification: This feature is required to support comprehensive application confinement on Ubuntu Touch. This feature adds a security benefit to libvirt's qemu guest isolation which is fundamental to Ubuntu on Server/Cloud. This feature also adds a welcome improvement to administrators wishing to further protect their systems. Extra information: While the apparmor userspace and kernel changes to support abstract, anonymous and fine-grained netlink socket can happen at different times, the apparmor userspace upload must correspond with uploads for packages that ship AppArmor policy that require updates (eg, libvirt, lightdm, etc). The packages outlined in https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/AppArmorProfiles have been tested to either work without modification to the policy or updated and tested to work with updated policy. Common rules will be added to the apparmor base abstraction such that most packages shipping apparmor policy will not require updating. These updates will be prepared, tested and published en masse via a silo ppa. = linux = Summary: This feature freeze exception is requested for abstract, anonymous and fine-grained netlink socket via apparmor in the kernel. When used with a compatible apparmor userspace, 'unix' and 'network netlink' rules are supported. When used without a compatible apparmor userspace (eg, on a trusty system with an utopic backport kernel), abstract, anonymous and fine-grained netlink socket mediation is not enforced (ie, you can use this kernel with an old userspace without any issues). Testing: * 14.04 system with backported kernel: TODO * test-apparmor.py: TODO (runs extensive tests (upstream and distro)) * exploratory manual testing: TODO (networking, aa-enforce with firefox, firefox works, apparmor blocks access, etc) * aa-status: TODO * lxc: TODO (containers can be created, started, shutdown) * libvirt: TODO (VMs started via openstack, and test-libvirt.py from QRT passes all tests) * 14.10 system (non-Touch) with updated kernel: * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: INPROGRESS (includes click-apparmor, apparmor-easyprof-ubuntu, exploratory manual testing, etc) * 14.10 system (Touch) with updated kernel: * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: INPROGRESS (includes click-apparmor, apparmor-easyprof-ubuntu, exploratory manual testing, etc) Justification: This feature is required to support comprehensive application confinement on Ubuntu Touch. This feature adds a security benefit to libvirt's qemu guest isolation which is fundamental to Ubuntu on Server/Cloud. This feature also adds a welcome improvement to admin
[Kernel-packages] [Bug 1220577] Re: [HP Pavilion 15 Sleekbook] wireless hotkey function loss on 12.04.3 but works on 12.04.2
Wireless key on 201210-11859 (HP ENVY 6 Sleekbook) works with 12.04.5 stock
Ubuntu (The wireless LED works as well).
I will go through other systems that listed in tags to make sure this bug could
be set to 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/1220577
Title:
[HP Pavilion 15 Sleekbook] wireless hotkey function loss on 12.04.3
but works on 12.04.2
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
CID 201209-11789
Hardware: HP Pavilion 15 Sleekbook
image: 12.04.3
Step to reproduce the bug:
1. boot into the system
2. connect to wireless AP (if any) via the indicator on Desktop (upper-right
hand side)
3. if connected, make sure we could surf on internet
4. press the wireless hotkey, in this case, it is F12
Expected result:
1. the wireless will lose connection
2. no AP on the scanning list of the wireless desktop indicator
3. wireless LED will change color (from white to orange)
Actual result:
nothing happened
More information may help:
1. "rfkill list" shows the soft block was still "no" after the wireless
hotkey is pressed
2. "sudo showkey -k" has no response when the wireless hotkey is pressed
3. 12.04.2 will not have this bug on the same machine
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.8.0-29-generic 3.8.0-29.42~precise1 [modified:
boot/vmlinuz-3.8.0-29-generic]
ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5
Uname: Linux 3.8.0-29-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.0.1-0ubuntu17.4
Architecture: amd64
Date: Wed Sep 4 16:06:17 2013
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64
(20130820.1)
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-lts-raring
UpgradeStatus: No upgrade log present (probably fresh install)
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k3.8.0-29-generic.
ApportVersion: 2.0.1-0ubuntu17.4
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 1: Generic [HD-Audio Generic], device 0: STAC92xx Analog [STAC92xx
Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ubuntu 1862 F pulseaudio
/dev/snd/controlC0: ubuntu 1862 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'HDMI'/'HDA ATI HDMI at 0x90344000 irq 46'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,00aa0100,00100300'
Controls : 7
Simple ctrls : 1
Card0.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Card1.Amixer.info:
Card hw:1 'Generic'/'HD-Audio Generic at 0x9034 irq 16'
Mixer name : 'IDT 92HD99BXX'
Components : 'HDA:111d76e5,103c1937,00100303'
Controls : 20
Simple ctrls : 10
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=675c5759-cc72-47fa-8bd7-7ee264d629d9
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64
(20130820.1)
MachineType: Hewlett-Packard HP Pavilion Sleekbook 14 PC
MarkForUpload: True
NonfreeKernelModules: fglrx
Package: linux (not installed)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic
root=UUID=7cd69704-76ab-400e-87fa-ace22dc1d651 ro quiet splash
ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5
RelatedPackageVersions:
linux-restricted-modules-3.8.0-29-generic N/A
linux-backports-modules-3.8.0-29-generic N/A
linux-firmware1.79.6
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: precise running-unity
Uname: Linux 3.8.0-29-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 11/01/2012
dmi.bios.vendor: Insyde
dmi.bios.version: F.13
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1937
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 87.0B
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnInsyde:bvrF.13:bd11/01/2012:svnHewlett-Packard:pnHPPavilionSleekbook14PC:pvr08921100590320100:rvnHewlett-Packard:rn1937:rvr87.0B:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion Sleekbook 14 PC
dmi.product.v
[Kernel-packages] [Bug 1220577] Re: [HP Pavilion 15 Sleekbook] wireless hotkey function loss on 12.04.3 but works on 12.04.2
Wireless key on 201209-11789 works with 12.04.5 stock Ubuntu (The wireless LED
works as well).
I will go through other systems listed in tags to make sure this bug could be
set to 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/1220577
Title:
[HP Pavilion 15 Sleekbook] wireless hotkey function loss on 12.04.3
but works on 12.04.2
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
CID 201209-11789
Hardware: HP Pavilion 15 Sleekbook
image: 12.04.3
Step to reproduce the bug:
1. boot into the system
2. connect to wireless AP (if any) via the indicator on Desktop (upper-right
hand side)
3. if connected, make sure we could surf on internet
4. press the wireless hotkey, in this case, it is F12
Expected result:
1. the wireless will lose connection
2. no AP on the scanning list of the wireless desktop indicator
3. wireless LED will change color (from white to orange)
Actual result:
nothing happened
More information may help:
1. "rfkill list" shows the soft block was still "no" after the wireless
hotkey is pressed
2. "sudo showkey -k" has no response when the wireless hotkey is pressed
3. 12.04.2 will not have this bug on the same machine
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.8.0-29-generic 3.8.0-29.42~precise1 [modified:
boot/vmlinuz-3.8.0-29-generic]
ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5
Uname: Linux 3.8.0-29-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.0.1-0ubuntu17.4
Architecture: amd64
Date: Wed Sep 4 16:06:17 2013
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64
(20130820.1)
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-lts-raring
UpgradeStatus: No upgrade log present (probably fresh install)
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k3.8.0-29-generic.
ApportVersion: 2.0.1-0ubuntu17.4
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 1: Generic [HD-Audio Generic], device 0: STAC92xx Analog [STAC92xx
Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ubuntu 1862 F pulseaudio
/dev/snd/controlC0: ubuntu 1862 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'HDMI'/'HDA ATI HDMI at 0x90344000 irq 46'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,00aa0100,00100300'
Controls : 7
Simple ctrls : 1
Card0.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Card1.Amixer.info:
Card hw:1 'Generic'/'HD-Audio Generic at 0x9034 irq 16'
Mixer name : 'IDT 92HD99BXX'
Components : 'HDA:111d76e5,103c1937,00100303'
Controls : 20
Simple ctrls : 10
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=675c5759-cc72-47fa-8bd7-7ee264d629d9
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64
(20130820.1)
MachineType: Hewlett-Packard HP Pavilion Sleekbook 14 PC
MarkForUpload: True
NonfreeKernelModules: fglrx
Package: linux (not installed)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic
root=UUID=7cd69704-76ab-400e-87fa-ace22dc1d651 ro quiet splash
ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5
RelatedPackageVersions:
linux-restricted-modules-3.8.0-29-generic N/A
linux-backports-modules-3.8.0-29-generic N/A
linux-firmware1.79.6
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: precise running-unity
Uname: Linux 3.8.0-29-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 11/01/2012
dmi.bios.vendor: Insyde
dmi.bios.version: F.13
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1937
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 87.0B
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnInsyde:bvrF.13:bd11/01/2012:svnHewlett-Packard:pnHPPavilionSleekbook14PC:pvr08921100590320100:rvnHewlett-Packard:rn1937:rvr87.0B:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion Sleekbook 14 PC
dmi.product.version: 08921100590
[Kernel-packages] [Bug 1366432] Re: [Dell Latitude E6400] System crashes after opening laptop from suspend
Kristen French, consulting https://wiki.ubuntu.com/Kernel/MainlineBuilds if one is using amd64, which your Bug Description advises you do, one would install all the _amd64.deb files, and the _all.deb. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1366432 Title: [Dell Latitude E6400] System crashes after opening laptop from suspend Status in “linux” package in Ubuntu: Incomplete Bug description: Fresh install of edubuntu 14.04 LTS on a laptop Dell latitude E6400; rather than allowing the user to log back in, the laptop crashes after closing and opening the lid. Shows a login screen as if the computer is locked, but the keyboard does not respond. Mouse pad allows movement of the cursor, but clicking on icons to try to shut down properly does not work. Must use power button to perform a hard reboot. Thus far has been a problem on two of these laptops with the same edubuntu install. Used ubuntu-bug linux command to generate this report. 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.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: godric 2003 F pulseaudio CurrentDesktop: Unity Date: Sat Sep 6 19:37:02 2014 HibernationDevice: RESUME=UUID=df6c4b8f-2f59-4284-81cc-48c0eb82db87 InstallationDate: Installed on 2014-08-20 (17 days ago) InstallationMedia: Edubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.1) MachineType: Dell Inc. Latitude E6400 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=1f0591c4-22b7-4e75-bb4f-01762eafcb99 ro quiet splash 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: 05/11/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0U695R dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd05/11/2009:svnDellInc.:pnLatitudeE6400:pvr:rvnDellInc.:rn0U695R:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude E6400 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1366432/+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 1367064] Re: [MSI A88XM-E45][A4-5300] 'buntu 14.04.1 constant reboot without nomodeset
Yuv, thank you for reporting this and helping make Ubuntu better. Could you please test the latest upstream kernel available from the very top line at the top of the page (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags: kernel-fixed-upstream kernel-fixed-upstream-VERSION-NUMBER where VERSION-NUMBER is the version number of the kernel you tested exactly shown as: kernel-fixed-upstream-3.17-rc4 This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. If the mainline kernel does not fix this bug, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-VERSION-NUMBER Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding. ** Description changed: - * Machine was happy with Xubuntu 13.10, but the software has been discontinued and I was forced to upgrade. - * USB stick with 14.04.1 would reboot continuously. Temporary workaround: press F6 and select NOMODESET - * USB stick with 14.04.1 server installs flawlessly, but then the server itself reboots continuously. + Machine was happy with Xubuntu 13.10, but the software has been + discontinued and I was forced to upgrade. USB stick with 14.04.1 would + reboot continuously. USB stick with 14.04.1 server installs flawlessly, + but then the server itself reboots continuously. - Workaround: - * Boot into recovery mode (hidden grub option) + WORKAROUND: Boot into recovery mode (hidden grub option) * Drop to root shell * Mount disk for read/write * edit /etc/default/grub: find the line starting with 'GRUB_CMDLINE_LINUX_DEFAULT=' and add the word nomodeset inside the quotes * run update-grub and reboot - - Developers: How is it possible that something so obvious has gone into an LTS? You may want to - (1) review your processes and maybe be more conservative in the choice of package versions for an LTS; - (2) have some basic validation process before releasing an LTS (AMD's APUs are mainstream hardware); - (3) prioritize the fix of such bugs (first reports are from half a year ago) or extend the life of previous releases (13.10 was just fine) until they are fixed. 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 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-35-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/pcmC1D2c', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CurrentDmesg: - + Date: Mon Sep 8 21:37:52 2014 HibernationDevice: RESUME=UUID=c347e713-9e24-4ff4-aec8-45cc91763877 InstallationDate: Installed on 2014-09-09 (0 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) IwConfig: - eth0 no wireless extensions. - - eth1 no wireless extensions. - - lono wireless extensions. + eth0 no wireless extensions. + + eth1 no wireless extensions. + + lono wireless extensions. MachineType: MSI MS-7721 ProcFB: - + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=42c89bfe-885c-4c79-bc38-c301f5f9545e ro iommu=soft nomodeset 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.5 + linux-restricted-modules-3.13.0-35-generic N/A + linux-backports-modules-3.13.0-35-generic N/A + linux-firmware 1.127.5 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V25.3
[Kernel-packages] [Bug 1360410] Re: Slow connection on RT3290: ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
Serhiy Zahoriya, could you please provide the missing information following https://wiki.ubuntu.com/Kernel/LinuxWireless ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1360410 Title: Slow connection on RT3290: ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Status in “linux” package in Ubuntu: Incomplete Bug description: Previously I thought it was due to low WiFi signal, but I've just compared speeds with my phone in my room and directly below the router. The notebook doesn't get more then half Mbps while phone gets 6 to 8 and wired desktop - above 50. I've also tried changing channels. Kernel log is filled with ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-34-generic 3.13.0-34.60 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: int2111 F pulseaudio /dev/snd/pcmC0D3p: int2111 F...m pulseaudio CurrentDesktop: KDE Date: Fri Aug 22 21:49:00 2014 HibernationDevice: RESUME=UUID=52f0a457-e6ab-4711-a129-83170285523b MachineType: ASUSTeK COMPUTER INC. X502CA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-34-generic root=/dev/mapper/kubuntu--vg-root ro quiet RelatedPackageVersions: linux-restricted-modules-3.13.0-34-generic N/A linux-backports-modules-3.13.0-34-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X502CA.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X502CA 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.:bvrX502CA.207:bd02/21/2013:svnASUSTeKCOMPUTERINC.:pnX502CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX502CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X502CA 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/1360410/+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 1367064] Re: [MSI A88XM-E45][A4-5300] 'buntu 14.04.1 constant reboot without nomodeset
Been monitoring 3.12/3.14 commit logs and it doesn't seem that the fix is going to land in the kernel without backports. Apparently they are too old. It seems (from bug 1355044) that they won't backport a fix without a full bisection. Here Bib reports a bisection range for the ubuntu kernel linux images: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1355044/comments/15 If you intend to complete the bisection, hopefully this link will save you time: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1355044/comments/16 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1367064 Title: [MSI A88XM-E45][A4-5300] 'buntu 14.04.1 constant reboot without nomodeset Status in “linux” package in Ubuntu: Incomplete Bug description: Machine was happy with Xubuntu 13.10, but the software has been discontinued and I was forced to upgrade. USB stick with 14.04.1 would reboot continuously. USB stick with 14.04.1 server installs flawlessly, but then the server itself reboots continuously. WORKAROUND: Boot into recovery mode (hidden grub option) * Drop to root shell * Mount disk for read/write * edit /etc/default/grub: find the line starting with 'GRUB_CMDLINE_LINUX_DEFAULT=' and add the word nomodeset inside the quotes * run update-grub and reboot 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 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-35-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/pcmC1D2c', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CurrentDmesg: Date: Mon Sep 8 21:37:52 2014 HibernationDevice: RESUME=UUID=c347e713-9e24-4ff4-aec8-45cc91763877 InstallationDate: Installed on 2014-09-09 (0 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7721 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=42c89bfe-885c-4c79-bc38-c301f5f9545e ro iommu=soft nomodeset 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.5 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V25.3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-E45 (MS-7721) dmi.board.vendor: MSI dmi.board.version: 5.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 5.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV25.3:bd03/18/2014:svnMSI:pnMS-7721:pvr5.0:rvnMSI:rnA88XM-E45(MS-7721):rvr5.0:cvnMSI:ct3:cvr5.0: dmi.product.name: MS-7721 dmi.product.version: 5.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1367064/+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 1367064] 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/1367064 Title: [MSI A88XM-E45][A4-5300] 'buntu 14.04.1 constant reboot without nomodeset Status in “linux” package in Ubuntu: Incomplete Bug description: Machine was happy with Xubuntu 13.10, but the software has been discontinued and I was forced to upgrade. USB stick with 14.04.1 would reboot continuously. USB stick with 14.04.1 server installs flawlessly, but then the server itself reboots continuously. WORKAROUND: Boot into recovery mode (hidden grub option) * Drop to root shell * Mount disk for read/write * edit /etc/default/grub: find the line starting with 'GRUB_CMDLINE_LINUX_DEFAULT=' and add the word nomodeset inside the quotes * run update-grub and reboot 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 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-35-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/pcmC1D2c', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CurrentDmesg: Date: Mon Sep 8 21:37:52 2014 HibernationDevice: RESUME=UUID=c347e713-9e24-4ff4-aec8-45cc91763877 InstallationDate: Installed on 2014-09-09 (0 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7721 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=42c89bfe-885c-4c79-bc38-c301f5f9545e ro iommu=soft nomodeset 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.5 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V25.3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-E45 (MS-7721) dmi.board.vendor: MSI dmi.board.version: 5.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 5.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV25.3:bd03/18/2014:svnMSI:pnMS-7721:pvr5.0:rvnMSI:rnA88XM-E45(MS-7721):rvr5.0:cvnMSI:ct3:cvr5.0: dmi.product.name: MS-7721 dmi.product.version: 5.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1367064/+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 1366432] Re: [Dell Latitude E6400] System crashes after opening laptop from suspend
Okay, I found that folder using the URL above, but what file(s) do I use to test the kernel? Kristen French, PhD On Sep 8, 2014 9:36 PM, "Christopher M. Penalver" < christopher.m.penal...@gmail.com> wrote: > Kristen French, the latest mainline kernel is http://kernel.ubuntu.com > /~kernel-ppa/mainline/v3.17-rc4-utopic/ . > > ** Changed in: linux (Ubuntu) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1366432 > > Title: > [Dell Latitude E6400] System crashes after opening laptop from suspend > > Status in “linux” package in Ubuntu: > Incomplete > > Bug description: > Fresh install of > > edubuntu 14.04 LTS on a > laptop Dell latitude E6400; > > rather than allowing the user to log back in, the laptop crashes after > closing and opening the lid. Shows a login screen as if the computer > is locked, but the keyboard does not respond. Mouse pad allows > movement of the cursor, but clicking on icons to try to shut down > properly does not work. Must use power button to perform a hard > reboot. Thus far has been a problem on two of these laptops with the > same edubuntu install. > > Used ubuntu-bug linux command to generate this report. > > 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.3 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: godric 2003 F pulseaudio > CurrentDesktop: Unity > Date: Sat Sep 6 19:37:02 2014 > HibernationDevice: RESUME=UUID=df6c4b8f-2f59-4284-81cc-48c0eb82db87 > InstallationDate: Installed on 2014-08-20 (17 days ago) > InstallationMedia: Edubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 > (20140722.1) > MachineType: Dell Inc. Latitude E6400 > ProcFB: 0 nouveaufb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic > root=UUID=1f0591c4-22b7-4e75-bb4f-01762eafcb99 ro quiet splash 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: 05/11/2009 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: A14 > dmi.board.name: 0U695R > dmi.board.vendor: Dell Inc. > dmi.chassis.type: 8 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: > dmi:bvnDellInc.:bvrA14:bd05/11/2009:svnDellInc.:pnLatitudeE6400:pvr:rvnDellInc.:rn0U695R:rvr:cvnDellInc.:ct8:cvr: > dmi.product.name: Latitude E6400 > dmi.sys.vendor: Dell Inc. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1366432/+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/1366432 Title: [Dell Latitude E6400] System crashes after opening laptop from suspend Status in “linux” package in Ubuntu: Incomplete Bug description: Fresh install of edubuntu 14.04 LTS on a laptop Dell latitude E6400; rather than allowing the user to log back in, the laptop crashes after closing and opening the lid. Shows a login screen as if the computer is locked, but the keyboard does not respond. Mouse pad allows movement of the cursor, but clicking on icons to try to shut down properly does not work. Must use power button to perform a hard reboot. Thus far has been a problem on two of these laptops with the same edubuntu install. Used ubuntu-bug linux command to generate this report. 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.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: godric 2003 F pulseaudio CurrentDesktop: Unity Date: Sat Sep 6 19:37:02 2014 HibernationDevice: RESUME=UUID=df6c4b8f-2f59-4284-81cc-48c0eb82db87 InstallationDate: Installed on 2014-08-20 (17 days ago) InstallationMedia: Edubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.1) MachineType: Dell Inc. Latitude E6400 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=1f0591c4-22b7-4e75-bb4f-01762eafcb99 ro quiet splash 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
[Kernel-packages] [Bug 1362199] Re: [FFe] apparmor abstract, anonymous and netlink socket mediation
FYI, when booting new userspace with old kernel, the parser will output something like this: Warning from profile /usr/lib/telepathy/telepathy-ofono (/etc/apparmor.d/usr.lib.telepathy): downgrading extended network unix socket rule to generic network rule -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1362199 Title: [FFe] apparmor abstract, anonymous and netlink socket mediation Status in “apparmor” package in Ubuntu: In Progress Status in “apparmor-easyprof-ubuntu” package in Ubuntu: In Progress Status in “isc-dhcp” package in Ubuntu: Fix Released Status in “libvirt” package in Ubuntu: In Progress Status in “lightdm” package in Ubuntu: In Progress Status in “linux” package in Ubuntu: In Progress Status in “rsyslog” package in Ubuntu: In Progress Status in “tlsdate” package in Ubuntu: In Progress Bug description: Background: kernel and apparmor userspace updates to support abstract, anonymous and fine-grained netlink socket mediation. These packages are listed in one bug because they are related, but the FFes may be granted and the uploads may happen at different times. = apparmor userspace = Summary: This feature freeze exception is requested for abstract, anonymous and fine-grained netlink socket for apparmor userspace. When used with a compatible kernel, 'unix' and 'network netlink' rules are supported. When used without a compatible apparmor userspace (eg, on a trusty system with an utopic backport kernel), abstract, anonymous and fine-grained netlink socket mediation is not enforced (ie, you can use this userspace with an old kernel without any issues). Testing: * 14.10 system with current kernels lacking abstract, anonymous and fine-grained netlink socket mediation (non-Touch): * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: DONE (exploratory manual testing, lxc, libvirt, etc) * 14.10 system kernel capable of supporting abstract, anonymous and fine-grained netlink socket mediation (non-Touch): * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: INPROGRESS (includes test-apparmor.py, exploratory manual testing, lxc, libvirt, etc) * Verify everything in https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/AppArmorProfiles: DONE (except juju since it doesn't have policy itself) Justification: This feature is required to support comprehensive application confinement on Ubuntu Touch. This feature adds a security benefit to libvirt's qemu guest isolation which is fundamental to Ubuntu on Server/Cloud. This feature also adds a welcome improvement to administrators wishing to further protect their systems. Extra information: While the apparmor userspace and kernel changes to support abstract, anonymous and fine-grained netlink socket can happen at different times, the apparmor userspace upload must correspond with uploads for packages that ship AppArmor policy that require updates (eg, libvirt, lightdm, etc). The packages outlined in https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/AppArmorProfiles have been tested to either work without modification to the policy or updated and tested to work with updated policy. Common rules will be added to the apparmor base abstraction such that most packages shipping apparmor policy will not require updating. These updates will be prepared, tested and published en masse via a silo ppa. = linux = Summary: This feature freeze exception is requested for abstract, anonymous and fine-grained netlink socket via apparmor in the kernel. When used with a compatible apparmor userspace, 'unix' and 'network netlink' rules are supported. When used without a compatible apparmor userspace (eg, on a trusty system with an utopic backport kernel), abstract, anonymous and fine-grained netlink socket mediation is not enforced (ie, you can use this kernel with an old userspace without any issues). Testing: * 14.04 system with backported kernel: TODO * test-apparmor.py: TODO (runs extensive tests (upstream and distro)) * exploratory manual testing: TODO (networking, aa-enforce with firefox, firefox works, apparmor blocks access, etc) * aa-status: TODO * lxc: TODO (containers can be created, started, shutdown) * libvirt: TODO (VMs started via openstack, and test-libvirt.py from QRT passes all tests) * 14.10 system (non-Touch) with updated kernel: * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: INPROGRESS (includes click-apparmor, apparmor-easyprof-ubuntu, exploratory manual testing, etc) * 14.10 system (Touch) with updated kernel: * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: INPROGRESS (includes click-apparmor, apparmor-easyprof-ubuntu, exploratory manual testing, etc) Justification: This feature is required to support comprehensive application confinement on Ubuntu Touch. This feature adds a
[Kernel-packages] [Bug 1309578] Re: Ubuntu 14.04 suddenly reboots when booting from Live USB AMD A8 6600k
and another one: bug 1367064 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1309578 Title: Ubuntu 14.04 suddenly reboots when booting from Live USB AMD A8 6600k Status in “linux” package in Ubuntu: Incomplete Bug description: I have a custom built AMD System with the following hardware currently running on Linux Mint 16 : AMD A8 6600k with Integrated graphics | MSI-FM2-A55M-E33 Motherboard | Kingston Hyperx Blu 4GB RAM | Corsair VS450 PSU Today when I tried to install 14.04 amd64 iso using a bootable USB, then the system rebooted. Any further attempts in installing it resulted in the same bug. As soon as I open the "Ubuntu installer" application and click "Continue" button then the system restarts after 2-3 seconds. I asked the same on AskUbuntu and some more guys reported the same problem with AMD APU, so I believe it to be a genuine bug and not just with me. The BIOS version is the latest one downloaded from MSI official website which is version 11.5. Also an Interesting thing is that this bug is common with the latest iso of Arch Linux too, but when booting older distros like Linux Mint 16 from USB, then everything works like it should, so it might have something to do with the newer 3.13 Kernel version. I am not an expert, but I can surely tell that only the newer distros are affected by this bug as reported by some other guys at AskUbuntu and the fact that Arch which is running the newer Kernel is having the same bug, so it probably has something to do with the newer Kernel, but I could be wrong. This bug is not letting me install Ubuntu 14.04 on my hardware and it is affecting a few more users too. Here is the AskUbuntu thread : http://askubuntu.com/questions/449391/unable-to-install-ubuntu-14-04 -pc-restarts-after-i-click-continue-button-in I hope this gets fixed soon or with the 14.04.1 upcoming July release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309578/+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 1367064] [NEW] [MSI A88XM-E45][A4-5300] 'buntu 14.04.1 constant reboot without nomodeset
Public bug reported: * Machine was happy with Xubuntu 13.10, but the software has been discontinued and I was forced to upgrade. * USB stick with 14.04.1 would reboot continuously. Temporary workaround: press F6 and select NOMODESET * USB stick with 14.04.1 server installs flawlessly, but then the server itself reboots continuously. Workaround: * Boot into recovery mode (hidden grub option) * Drop to root shell * Mount disk for read/write * edit /etc/default/grub: find the line starting with 'GRUB_CMDLINE_LINUX_DEFAULT=' and add the word nomodeset inside the quotes * run update-grub and reboot Developers: How is it possible that something so obvious has gone into an LTS? You may want to (1) review your processes and maybe be more conservative in the choice of package versions for an LTS; (2) have some basic validation process before releasing an LTS (AMD's APUs are mainstream hardware); (3) prioritize the fix of such bugs (first reports are from half a year ago) or extend the life of previous releases (13.10 was just fine) until they are fixed. 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 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-35-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/pcmC1D2c', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CurrentDmesg: Date: Mon Sep 8 21:37:52 2014 HibernationDevice: RESUME=UUID=c347e713-9e24-4ff4-aec8-45cc91763877 InstallationDate: Installed on 2014-09-09 (0 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7721 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=42c89bfe-885c-4c79-bc38-c301f5f9545e ro iommu=soft nomodeset 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.5 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V25.3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-E45 (MS-7721) dmi.board.vendor: MSI dmi.board.version: 5.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 5.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV25.3:bd03/18/2014:svnMSI:pnMS-7721:pvr5.0:rvnMSI:rnA88XM-E45(MS-7721):rvr5.0:cvnMSI:ct3:cvr5.0: dmi.product.name: MS-7721 dmi.product.version: 5.0 dmi.sys.vendor: MSI ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1367064 Title: [MSI A88XM-E45][A4-5300] 'buntu 14.04.1 constant reboot without nomodeset Status in “linux” package in Ubuntu: New Bug description: * Machine was happy with Xubuntu 13.10, but the software has been discontinued and I was forced to upgrade. * USB stick with 14.04.1 would reboot continuously. Temporary workaround: press F6 and select NOMODESET * USB stick with 14.04.1 server installs flawlessly, but then the server itself reboots continuously. Workaround: * Boot into recovery mode (hidden grub option) * Drop to root shell * Mount disk for read/write * edit /etc/default/grub: find the line starting with 'GRUB_CMDLINE_LINUX_DEFAULT=' and add the word nomodeset inside the quotes * run update-grub and reboot Developers: How is it possible that something so obvious has gone into an LTS? You may want to (1) review your processes and maybe be more conservative in the choice of package versions for an LTS; (2) have some basic validation process before releasing an LTS (AMD's APUs are mainstream hardware); (3) prioritize the fix of such bugs (first reports are fr
[Kernel-packages] [Bug 1366432] Re: [Dell Latitude E6400] System crashes after opening laptop from suspend
** Tags removed: kernel-bug-exists-upstream kernel-bug-exists-upstream-3.16.0-031600 ** Tags added: needs-upstream-testing -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1366432 Title: [Dell Latitude E6400] System crashes after opening laptop from suspend Status in “linux” package in Ubuntu: Incomplete Bug description: Fresh install of edubuntu 14.04 LTS on a laptop Dell latitude E6400; rather than allowing the user to log back in, the laptop crashes after closing and opening the lid. Shows a login screen as if the computer is locked, but the keyboard does not respond. Mouse pad allows movement of the cursor, but clicking on icons to try to shut down properly does not work. Must use power button to perform a hard reboot. Thus far has been a problem on two of these laptops with the same edubuntu install. Used ubuntu-bug linux command to generate this report. 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.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: godric 2003 F pulseaudio CurrentDesktop: Unity Date: Sat Sep 6 19:37:02 2014 HibernationDevice: RESUME=UUID=df6c4b8f-2f59-4284-81cc-48c0eb82db87 InstallationDate: Installed on 2014-08-20 (17 days ago) InstallationMedia: Edubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.1) MachineType: Dell Inc. Latitude E6400 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=1f0591c4-22b7-4e75-bb4f-01762eafcb99 ro quiet splash 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: 05/11/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0U695R dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd05/11/2009:svnDellInc.:pnLatitudeE6400:pvr:rvnDellInc.:rn0U695R:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude E6400 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1366432/+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 1360410] Re: Slow connection on RT3290: ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
Just bought the notebook, can't say. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1360410 Title: Slow connection on RT3290: ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Status in “linux” package in Ubuntu: Incomplete Bug description: Previously I thought it was due to low WiFi signal, but I've just compared speeds with my phone in my room and directly below the router. The notebook doesn't get more then half Mbps while phone gets 6 to 8 and wired desktop - above 50. I've also tried changing channels. Kernel log is filled with ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-34-generic 3.13.0-34.60 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: int2111 F pulseaudio /dev/snd/pcmC0D3p: int2111 F...m pulseaudio CurrentDesktop: KDE Date: Fri Aug 22 21:49:00 2014 HibernationDevice: RESUME=UUID=52f0a457-e6ab-4711-a129-83170285523b MachineType: ASUSTeK COMPUTER INC. X502CA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-34-generic root=/dev/mapper/kubuntu--vg-root ro quiet RelatedPackageVersions: linux-restricted-modules-3.13.0-34-generic N/A linux-backports-modules-3.13.0-34-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X502CA.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X502CA 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.:bvrX502CA.207:bd02/21/2013:svnASUSTeKCOMPUTERINC.:pnX502CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX502CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X502CA 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/1360410/+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 1366432] Re: [Dell Latitude E6400] System crashes after opening laptop from suspend
Kristen French, the latest mainline kernel is http://kernel.ubuntu.com /~kernel-ppa/mainline/v3.17-rc4-utopic/ . ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1366432 Title: [Dell Latitude E6400] System crashes after opening laptop from suspend Status in “linux” package in Ubuntu: Incomplete Bug description: Fresh install of edubuntu 14.04 LTS on a laptop Dell latitude E6400; rather than allowing the user to log back in, the laptop crashes after closing and opening the lid. Shows a login screen as if the computer is locked, but the keyboard does not respond. Mouse pad allows movement of the cursor, but clicking on icons to try to shut down properly does not work. Must use power button to perform a hard reboot. Thus far has been a problem on two of these laptops with the same edubuntu install. Used ubuntu-bug linux command to generate this report. 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.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: godric 2003 F pulseaudio CurrentDesktop: Unity Date: Sat Sep 6 19:37:02 2014 HibernationDevice: RESUME=UUID=df6c4b8f-2f59-4284-81cc-48c0eb82db87 InstallationDate: Installed on 2014-08-20 (17 days ago) InstallationMedia: Edubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.1) MachineType: Dell Inc. Latitude E6400 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=1f0591c4-22b7-4e75-bb4f-01762eafcb99 ro quiet splash 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: 05/11/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0U695R dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd05/11/2009:svnDellInc.:pnLatitudeE6400:pvr:rvnDellInc.:rn0U695R:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude E6400 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1366432/+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 1360410] Re: Slow connection on RT3290: ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
Serhiy Zahoriya, did this problem not occur in a release prior to 14.04? ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1360410 Title: Slow connection on RT3290: ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Status in “linux” package in Ubuntu: Incomplete Bug description: Previously I thought it was due to low WiFi signal, but I've just compared speeds with my phone in my room and directly below the router. The notebook doesn't get more then half Mbps while phone gets 6 to 8 and wired desktop - above 50. I've also tried changing channels. Kernel log is filled with ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-34-generic 3.13.0-34.60 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: int2111 F pulseaudio /dev/snd/pcmC0D3p: int2111 F...m pulseaudio CurrentDesktop: KDE Date: Fri Aug 22 21:49:00 2014 HibernationDevice: RESUME=UUID=52f0a457-e6ab-4711-a129-83170285523b MachineType: ASUSTeK COMPUTER INC. X502CA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-34-generic root=/dev/mapper/kubuntu--vg-root ro quiet RelatedPackageVersions: linux-restricted-modules-3.13.0-34-generic N/A linux-backports-modules-3.13.0-34-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X502CA.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X502CA 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.:bvrX502CA.207:bd02/21/2013:svnASUSTeKCOMPUTERINC.:pnX502CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX502CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X502CA 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/1360410/+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 1366248] Re: [Intel D54250WYK] Wireless Dropped Connection Intel 7260.HMWG
** Tags removed: bios-outdated-0028 ** Tags added: latest-bios-0028 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1366248 Title: [Intel D54250WYK] Wireless Dropped Connection Intel 7260.HMWG Status in “linux” package in Ubuntu: Incomplete Bug description: The wireless connection is dropping once again. Everything seemed fine after the last dist-upgrade on or around 8/29. An apt-get update/upgrade between 8/29 and 9/3 seems to have introduced this bug. 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.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: justin 1549 F pulseaudio /dev/snd/controlC0: justin 1549 F pulseaudio CurrentDesktop: Unity Date: Fri Sep 5 19:51:33 2014 HibernationDevice: RESUME=UUID=8048d919-eb4b-45eb-a626-ebd626d468f1 InstallationDate: Installed on 2014-04-25 (133 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic.efi.signed root=UUID=ba994e83-d5aa-4912-825f-c6d10a7d86ae 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.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2014 dmi.bios.vendor: Intel Corp. dmi.bios.version: WYLPT10H.86A.0025.2014.0303.1008 dmi.board.name: D54250WYK dmi.board.vendor: Intel Corporation dmi.board.version: H13922-303 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrWYLPT10H.86A.0025.2014.0303.1008:bd03/03/2014:svn:pn:pvr:rvnIntelCorporation:rnD54250WYK:rvrH13922-303:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1366248/+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 1364092] Re: linux: 2.6.32-66.132 -proposed tracker
** Description changed: This bug is for tracking the 2.6.32-66.132 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, 01. September 2014 17:01 UTC kernel-stable-Prepare-package-end:Tuesday, 02. September 2014 01:04 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 02. September 2014 01:04 UTC ppa-package-testing-start:Tuesday, 02. September 2014 01:04 UTC kernel-stable-Promote-to-proposed-end:Monday, 08. September 2014 20:03 UTC - kernel-stable-phase:Verification & Testing - kernel-stable-phase-changed:Monday, 08. September 2014 22:01 UTC kernel-stable-Verification-testing-start:Monday, 08. September 2014 22:01 UTC kernel-stable-Certification-testing-start:Monday, 08. September 2014 22:01 UTC kernel-stable-Security-signoff-start:Monday, 08. September 2014 22:01 UTC kernel-stable-Regression-testing-start:Monday, 08. September 2014 22:01 UTC + kernel-stable-phase:Testing + kernel-stable-phase-changed:Tuesday, 09. September 2014 00:01 UTC + kernel-stable-Verification-testing-end:Tuesday, 09. September 2014 00:01 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1364092 Title: linux: 2.6.32-66.132 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Fix Released 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: Fix Released 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-66.132 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, 01. September 2014 17:01 UTC kernel-stable-Prepare-package-end:Tuesday, 02. September 2014 01:04 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 02. September 2014 01:04 UTC ppa-package-testing-start:Tuesday, 02. September 2014 01:04 UTC kernel-stable-Promote-to-proposed-end:Monday, 08. September 2014 20:03 UTC kernel-stable-Verification-testing-start:Monday, 08. September 2014 22:01 UTC kernel-stable-Certification-testing-start:Monday, 08. September 2014 22:01 UTC kernel-stable-Security-signoff-start:Monday, 08. September 2014 22:01 UTC kernel-stable-Regression-testing-start:Monday, 08. September 2014 22:01 UTC kernel-stable-phase:Testing kernel-stable-phase-changed:Tuesday, 09. September 2014 00:01 UTC kernel-stable-Verification-testing-end:Tuesday, 09. September 2014 00:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1364092/+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 1364208] Re: linux: 3.2.0-69.103 -proposed tracker
** Description changed: This bug is for tracking the 3.2.0-69.103 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, 02. September 2014 03:28 UTC kernel-stable-Prepare-package-end:Tuesday, 02. September 2014 09:08 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 02. September 2014 09:08 UTC ppa-package-testing-start:Tuesday, 02. September 2014 09:08 UTC kernel-stable-Promote-to-proposed-end:Thursday, 04. September 2014 19:40 UTC - kernel-stable-phase:Verification & Testing - kernel-stable-phase-changed:Thursday, 04. September 2014 21:03 UTC kernel-stable-Verification-testing-start:Thursday, 04. September 2014 21:03 UTC kernel-stable-Certification-testing-start:Thursday, 04. September 2014 21:04 UTC kernel-stable-Security-signoff-start:Thursday, 04. September 2014 21:04 UTC kernel-stable-Regression-testing-start:Thursday, 04. September 2014 21:04 UTC + kernel-stable-phase:Testing + kernel-stable-phase-changed:Tuesday, 09. September 2014 00:01 UTC + kernel-stable-Verification-testing-end:Tuesday, 09. September 2014 00:01 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1364208 Title: linux: 3.2.0-69.103 -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: Fix Released 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released 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-69.103 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, 02. September 2014 03:28 UTC kernel-stable-Prepare-package-end:Tuesday, 02. September 2014 09:08 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 02. September 2014 09:08 UTC ppa-package-testing-start:Tuesday, 02. September 2014 09:08 UTC kernel-stable-Promote-to-proposed-end:Thursday, 04. September 2014 19:40 UTC kernel-stable-Verification-testing-start:Thursday, 04. September 2014 21:03 UTC kernel-stable-Certification-testing-start:Thursday, 04. September 2014 21:04 UTC kernel-stable-Security-signoff-start:Thursday, 04. September 2014 21:04 UTC kernel-stable-Regression-testing-start:Thursday, 04. September 2014 21:04 UTC kernel-stable-phase:Testing kernel-stable-phase-changed:Tuesday, 09. September 2014 00:01 UTC kernel-stable-Verification-testing-end:Tuesday, 09. September 2014 00:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1364208/+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 1366431] Re: linux: 3.16.0-14.20 -proposed tracker
The package has been published and the bug is being set to Fix Released ** Changed in: kernel-development-workflow Status: In Progress => Fix Released ** Description changed: This bug is for tracking the 3.16.0-14.20 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Saturday, 06. September 2014 23:27 UTC - kernel-phase-changed:Sunday, 07. September 2014 13:03 UTC kernel-Prepare-package-end:Sunday, 07. September 2014 13:03 UTC kernel-Package-testing-start:Sunday, 07. September 2014 13:03 UTC - kernel-phase:PPA Testing ppa-package-testing-start:Sunday, 07. September 2014 13:03 UTC kernel-Promote-to-release-end:Monday, 08. September 2014 23:00 UTC + kernel-phase:Released + kernel-phase-changed:Tuesday, 09. September 2014 00:00 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1366431 Title: linux: 3.16.0-14.20 -proposed tracker Status in Kernel Development Workflow: Fix Released Status in Kernel Development Workflow package-testing series: Won't Fix Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-release series: Fix Released Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Utopic: Fix Released Bug description: This bug is for tracking the 3.16.0-14.20 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Saturday, 06. September 2014 23:27 UTC kernel-Prepare-package-end:Sunday, 07. September 2014 13:03 UTC kernel-Package-testing-start:Sunday, 07. September 2014 13:03 UTC ppa-package-testing-start:Sunday, 07. September 2014 13:03 UTC kernel-Promote-to-release-end:Monday, 08. September 2014 23:00 UTC kernel-phase:Released kernel-phase-changed:Tuesday, 09. September 2014 00:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1366431/+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 1366432] Re: [Dell Latitude E6400] System crashes after opening laptop from suspend
** Tags added: kernel-bug-exists-upstream kernel-bug-exists- upstream-3.16.0-031600 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1366432 Title: [Dell Latitude E6400] System crashes after opening laptop from suspend Status in “linux” package in Ubuntu: Confirmed Bug description: Fresh install of edubuntu 14.04 LTS on a laptop Dell latitude E6400; rather than allowing the user to log back in, the laptop crashes after closing and opening the lid. Shows a login screen as if the computer is locked, but the keyboard does not respond. Mouse pad allows movement of the cursor, but clicking on icons to try to shut down properly does not work. Must use power button to perform a hard reboot. Thus far has been a problem on two of these laptops with the same edubuntu install. Used ubuntu-bug linux command to generate this report. 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.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: godric 2003 F pulseaudio CurrentDesktop: Unity Date: Sat Sep 6 19:37:02 2014 HibernationDevice: RESUME=UUID=df6c4b8f-2f59-4284-81cc-48c0eb82db87 InstallationDate: Installed on 2014-08-20 (17 days ago) InstallationMedia: Edubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.1) MachineType: Dell Inc. Latitude E6400 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=1f0591c4-22b7-4e75-bb4f-01762eafcb99 ro quiet splash 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: 05/11/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0U695R dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd05/11/2009:svnDellInc.:pnLatitudeE6400:pvr:rvnDellInc.:rn0U695R:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude E6400 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1366432/+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 1358949] Re: arm64 iperf performance suboptimal
I'm seeing reasonable performance with this.
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1358949
Title:
arm64 iperf performance suboptimal
Status in “linux” package in Ubuntu:
Fix Released
Status in “linux” source package in Trusty:
Fix Committed
Status in “linux” source package in Utopic:
Fix Released
Bug description:
[Impact]
The copy_{to,from}_user implementations in the Ubuntu kernel are suboptimal.
Optimized implementations have been submitted upstream and have shown a
significant improvement in network performance.
Iperf performance increase:
-l (size) 1 core result
Optimized 64B 44-51Mb/s
1500B 4.9Gb/s
3B 16.2Gb/s
Original64B 34-50.7Mb/s
1500B 4.7Gb/s
3B 14.5Gb/s
[Test Case]
Generate traffic from one node to another using iperf (see above for config).
[Regression Risk]
These functions are obviously used heavily throughout the kernel, so a defect
here could have significant impact. This risk is mitigated by using an
implementation heavily based on the linaro string libraries (which are used in
other places already, e.g. glibc), and through active testing of this patch on
real hardware using a trusty-kernel base.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358949/+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 1362199] Re: [FFe] apparmor abstract, anonymous and netlink socket mediation
2) new kernel and old userspace This is currently better tested than 3, but of course needs to be done again with any changes made to the kernel. Also note that the regression tests been improved and expanded for all three cases -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1362199 Title: [FFe] apparmor abstract, anonymous and netlink socket mediation Status in “apparmor” package in Ubuntu: In Progress Status in “apparmor-easyprof-ubuntu” package in Ubuntu: In Progress Status in “isc-dhcp” package in Ubuntu: Fix Released Status in “libvirt” package in Ubuntu: In Progress Status in “lightdm” package in Ubuntu: In Progress Status in “linux” package in Ubuntu: In Progress Status in “rsyslog” package in Ubuntu: In Progress Status in “tlsdate” package in Ubuntu: In Progress Bug description: Background: kernel and apparmor userspace updates to support abstract, anonymous and fine-grained netlink socket mediation. These packages are listed in one bug because they are related, but the FFes may be granted and the uploads may happen at different times. = apparmor userspace = Summary: This feature freeze exception is requested for abstract, anonymous and fine-grained netlink socket for apparmor userspace. When used with a compatible kernel, 'unix' and 'network netlink' rules are supported. When used without a compatible apparmor userspace (eg, on a trusty system with an utopic backport kernel), abstract, anonymous and fine-grained netlink socket mediation is not enforced (ie, you can use this userspace with an old kernel without any issues). Testing: * 14.10 system with current kernels lacking abstract, anonymous and fine-grained netlink socket mediation (non-Touch): * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: DONE (exploratory manual testing, lxc, libvirt, etc) * 14.10 system kernel capable of supporting abstract, anonymous and fine-grained netlink socket mediation (non-Touch): * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: INPROGRESS (includes test-apparmor.py, exploratory manual testing, lxc, libvirt, etc) * Verify everything in https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/AppArmorProfiles: DONE (except juju since it doesn't have policy itself) Justification: This feature is required to support comprehensive application confinement on Ubuntu Touch. This feature adds a security benefit to libvirt's qemu guest isolation which is fundamental to Ubuntu on Server/Cloud. This feature also adds a welcome improvement to administrators wishing to further protect their systems. Extra information: While the apparmor userspace and kernel changes to support abstract, anonymous and fine-grained netlink socket can happen at different times, the apparmor userspace upload must correspond with uploads for packages that ship AppArmor policy that require updates (eg, libvirt, lightdm, etc). The packages outlined in https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/AppArmorProfiles have been tested to either work without modification to the policy or updated and tested to work with updated policy. Common rules will be added to the apparmor base abstraction such that most packages shipping apparmor policy will not require updating. These updates will be prepared, tested and published en masse via a silo ppa. = linux = Summary: This feature freeze exception is requested for abstract, anonymous and fine-grained netlink socket via apparmor in the kernel. When used with a compatible apparmor userspace, 'unix' and 'network netlink' rules are supported. When used without a compatible apparmor userspace (eg, on a trusty system with an utopic backport kernel), abstract, anonymous and fine-grained netlink socket mediation is not enforced (ie, you can use this kernel with an old userspace without any issues). Testing: * 14.04 system with backported kernel: TODO * test-apparmor.py: TODO (runs extensive tests (upstream and distro)) * exploratory manual testing: TODO (networking, aa-enforce with firefox, firefox works, apparmor blocks access, etc) * aa-status: TODO * lxc: TODO (containers can be created, started, shutdown) * libvirt: TODO (VMs started via openstack, and test-libvirt.py from QRT passes all tests) * 14.10 system (non-Touch) with updated kernel: * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: INPROGRESS (includes click-apparmor, apparmor-easyprof-ubuntu, exploratory manual testing, etc) * 14.10 system (Touch) with updated kernel: * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: INPROGRESS (includes click-apparmor, apparmor-easyprof-ubuntu, exploratory manual testing, etc) Justification: This feature is required to support comprehensive application confinement on Ubuntu Touch. This feature adds a security benefit to libvirt'
[Kernel-packages] [Bug 1364092] Re: linux: 2.6.32-66.132 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/verification-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Brad Figg (brad-figg) ** Changed in: kernel-sru-workflow/package-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/package-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Brad Figg (brad-figg) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1364092 Title: linux: 2.6.32-66.132 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Fix Released 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: Fix Released 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-66.132 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, 01. September 2014 17:01 UTC kernel-stable-Prepare-package-end:Tuesday, 02. September 2014 01:04 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 02. September 2014 01:04 UTC ppa-package-testing-start:Tuesday, 02. September 2014 01:04 UTC kernel-stable-Promote-to-proposed-end:Monday, 08. September 2014 20:03 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Monday, 08. September 2014 22:01 UTC kernel-stable-Verification-testing-start:Monday, 08. September 2014 22:01 UTC kernel-stable-Certification-testing-start:Monday, 08. September 2014 22:01 UTC kernel-stable-Security-signoff-start:Monday, 08. September 2014 22:01 UTC kernel-stable-Regression-testing-start:Monday, 08. September 2014 22:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1364092/+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 1364208] Re: linux: 3.2.0-69.103 -proposed tracker
** Changed in: kernel-sru-workflow/package-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/package-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Brad Figg (brad-figg) ** Changed in: kernel-sru-workflow/verification-testing Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/verification-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Brad Figg (brad-figg) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1364208 Title: linux: 3.2.0-69.103 -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: Fix Released 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released 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-69.103 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, 02. September 2014 03:28 UTC kernel-stable-Prepare-package-end:Tuesday, 02. September 2014 09:08 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 02. September 2014 09:08 UTC ppa-package-testing-start:Tuesday, 02. September 2014 09:08 UTC kernel-stable-Promote-to-proposed-end:Thursday, 04. September 2014 19:40 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Thursday, 04. September 2014 21:03 UTC kernel-stable-Verification-testing-start:Thursday, 04. September 2014 21:03 UTC kernel-stable-Certification-testing-start:Thursday, 04. September 2014 21:04 UTC kernel-stable-Security-signoff-start:Thursday, 04. September 2014 21:04 UTC kernel-stable-Regression-testing-start:Thursday, 04. September 2014 21:04 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1364208/+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 1362199] Re: [FFe] apparmor abstract, anonymous and netlink socket mediation
1) old kernel and new userspace - this is well tested and ready to land now 2) new kernel and old userspace 3) new kernel and new userspace - these are tested, but need more testing on the kernel side. We are finalizing the kernel and will have these in place for kernel pull requests Ah, I did not update AppArmor's debian/control for the Breaks like I did for the signal and ptrace mediation, but meant to. Thanks for the reminder, I'll do that now. Here are the apparmor changes: https://code.launchpad.net/~apparmor-dev/apparmor/apparmor-ubuntu-citrain.abstract -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1362199 Title: [FFe] apparmor abstract, anonymous and netlink socket mediation Status in “apparmor” package in Ubuntu: In Progress Status in “apparmor-easyprof-ubuntu” package in Ubuntu: In Progress Status in “isc-dhcp” package in Ubuntu: Fix Released Status in “libvirt” package in Ubuntu: In Progress Status in “lightdm” package in Ubuntu: In Progress Status in “linux” package in Ubuntu: In Progress Status in “rsyslog” package in Ubuntu: In Progress Status in “tlsdate” package in Ubuntu: In Progress Bug description: Background: kernel and apparmor userspace updates to support abstract, anonymous and fine-grained netlink socket mediation. These packages are listed in one bug because they are related, but the FFes may be granted and the uploads may happen at different times. = apparmor userspace = Summary: This feature freeze exception is requested for abstract, anonymous and fine-grained netlink socket for apparmor userspace. When used with a compatible kernel, 'unix' and 'network netlink' rules are supported. When used without a compatible apparmor userspace (eg, on a trusty system with an utopic backport kernel), abstract, anonymous and fine-grained netlink socket mediation is not enforced (ie, you can use this userspace with an old kernel without any issues). Testing: * 14.10 system with current kernels lacking abstract, anonymous and fine-grained netlink socket mediation (non-Touch): * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: DONE (exploratory manual testing, lxc, libvirt, etc) * 14.10 system kernel capable of supporting abstract, anonymous and fine-grained netlink socket mediation (non-Touch): * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: INPROGRESS (includes test-apparmor.py, exploratory manual testing, lxc, libvirt, etc) * Verify everything in https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/AppArmorProfiles: DONE (except juju since it doesn't have policy itself) Justification: This feature is required to support comprehensive application confinement on Ubuntu Touch. This feature adds a security benefit to libvirt's qemu guest isolation which is fundamental to Ubuntu on Server/Cloud. This feature also adds a welcome improvement to administrators wishing to further protect their systems. Extra information: While the apparmor userspace and kernel changes to support abstract, anonymous and fine-grained netlink socket can happen at different times, the apparmor userspace upload must correspond with uploads for packages that ship AppArmor policy that require updates (eg, libvirt, lightdm, etc). The packages outlined in https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/AppArmorProfiles have been tested to either work without modification to the policy or updated and tested to work with updated policy. Common rules will be added to the apparmor base abstraction such that most packages shipping apparmor policy will not require updating. These updates will be prepared, tested and published en masse via a silo ppa. = linux = Summary: This feature freeze exception is requested for abstract, anonymous and fine-grained netlink socket via apparmor in the kernel. When used with a compatible apparmor userspace, 'unix' and 'network netlink' rules are supported. When used without a compatible apparmor userspace (eg, on a trusty system with an utopic backport kernel), abstract, anonymous and fine-grained netlink socket mediation is not enforced (ie, you can use this kernel with an old userspace without any issues). Testing: * 14.04 system with backported kernel: TODO * test-apparmor.py: TODO (runs extensive tests (upstream and distro)) * exploratory manual testing: TODO (networking, aa-enforce with firefox, firefox works, apparmor blocks access, etc) * aa-status: TODO * lxc: TODO (containers can be created, started, shutdown) * libvirt: TODO (VMs started via openstack, and test-libvirt.py from QRT passes all tests) * 14.10 system (non-Touch) with updated kernel: * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: INPROGRESS (includes click-apparmor, apparmor-easyprof-ubuntu, exploratory manual testing, etc) * 14.10 system (Touch) with
[Kernel-packages] [Bug 1366431] Re: linux: 3.16.0-14.20 -proposed tracker
** Changed in: kernel-development-workflow/package-testing Status: Confirmed => Won't Fix ** Description changed: This bug is for tracking the 3.16.0-14.20 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Saturday, 06. September 2014 23:27 UTC kernel-phase-changed:Sunday, 07. September 2014 13:03 UTC kernel-Prepare-package-end:Sunday, 07. September 2014 13:03 UTC kernel-Package-testing-start:Sunday, 07. September 2014 13:03 UTC kernel-phase:PPA Testing ppa-package-testing-start:Sunday, 07. September 2014 13:03 UTC + kernel-Promote-to-release-end:Monday, 08. September 2014 23:00 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1366431 Title: linux: 3.16.0-14.20 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow package-testing series: Won't Fix Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-release series: Fix Released Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Utopic: Fix Released Bug description: This bug is for tracking the 3.16.0-14.20 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Saturday, 06. September 2014 23:27 UTC kernel-phase-changed:Sunday, 07. September 2014 13:03 UTC kernel-Prepare-package-end:Sunday, 07. September 2014 13:03 UTC kernel-Package-testing-start:Sunday, 07. September 2014 13:03 UTC kernel-phase:PPA Testing ppa-package-testing-start:Sunday, 07. September 2014 13:03 UTC kernel-Promote-to-release-end:Monday, 08. September 2014 23:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1366431/+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 1362199] Re: [FFe] apparmor abstract, anonymous and netlink socket mediation
This could use some diffs attached to see how bad the damage is, but as long as the three combinations are tested, I'm fine with this in theory: 1) old kernel and new userspace 2) new kernel and old userspace 3) new kernel and new userspace Also, it's not clear if the "other packages that need updating in lockstep" thing is a hard dependency or just a "so they can make use of the feature". If it's a hard dependency, you'll need that specified in package relationships (new apparmor should probably have a "Breaks: foo (<< ver), bar (<< ver)" rather than making all of those packages depend on versioned apparmor). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1362199 Title: [FFe] apparmor abstract, anonymous and netlink socket mediation Status in “apparmor” package in Ubuntu: In Progress Status in “apparmor-easyprof-ubuntu” package in Ubuntu: In Progress Status in “isc-dhcp” package in Ubuntu: Fix Released Status in “libvirt” package in Ubuntu: In Progress Status in “lightdm” package in Ubuntu: In Progress Status in “linux” package in Ubuntu: In Progress Status in “rsyslog” package in Ubuntu: In Progress Status in “tlsdate” package in Ubuntu: In Progress Bug description: Background: kernel and apparmor userspace updates to support abstract, anonymous and fine-grained netlink socket mediation. These packages are listed in one bug because they are related, but the FFes may be granted and the uploads may happen at different times. = apparmor userspace = Summary: This feature freeze exception is requested for abstract, anonymous and fine-grained netlink socket for apparmor userspace. When used with a compatible kernel, 'unix' and 'network netlink' rules are supported. When used without a compatible apparmor userspace (eg, on a trusty system with an utopic backport kernel), abstract, anonymous and fine-grained netlink socket mediation is not enforced (ie, you can use this userspace with an old kernel without any issues). Testing: * 14.10 system with current kernels lacking abstract, anonymous and fine-grained netlink socket mediation (non-Touch): * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: DONE (exploratory manual testing, lxc, libvirt, etc) * 14.10 system kernel capable of supporting abstract, anonymous and fine-grained netlink socket mediation (non-Touch): * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: INPROGRESS (includes test-apparmor.py, exploratory manual testing, lxc, libvirt, etc) * Verify everything in https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/AppArmorProfiles: DONE (except juju since it doesn't have policy itself) Justification: This feature is required to support comprehensive application confinement on Ubuntu Touch. This feature adds a security benefit to libvirt's qemu guest isolation which is fundamental to Ubuntu on Server/Cloud. This feature also adds a welcome improvement to administrators wishing to further protect their systems. Extra information: While the apparmor userspace and kernel changes to support abstract, anonymous and fine-grained netlink socket can happen at different times, the apparmor userspace upload must correspond with uploads for packages that ship AppArmor policy that require updates (eg, libvirt, lightdm, etc). The packages outlined in https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/AppArmorProfiles have been tested to either work without modification to the policy or updated and tested to work with updated policy. Common rules will be added to the apparmor base abstraction such that most packages shipping apparmor policy will not require updating. These updates will be prepared, tested and published en masse via a silo ppa. = linux = Summary: This feature freeze exception is requested for abstract, anonymous and fine-grained netlink socket via apparmor in the kernel. When used with a compatible apparmor userspace, 'unix' and 'network netlink' rules are supported. When used without a compatible apparmor userspace (eg, on a trusty system with an utopic backport kernel), abstract, anonymous and fine-grained netlink socket mediation is not enforced (ie, you can use this kernel with an old userspace without any issues). Testing: * 14.04 system with backported kernel: TODO * test-apparmor.py: TODO (runs extensive tests (upstream and distro)) * exploratory manual testing: TODO (networking, aa-enforce with firefox, firefox works, apparmor blocks access, etc) * aa-status: TODO * lxc: TODO (containers can be created, started, shutdown) * libvirt: TODO (VMs started via openstack, and test-libvirt.py from QRT passes all tests) * 14.10 system (non-Touch) with updated kernel: * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: INPROGRESS (includes click-apparmor, apparmor-easyprof-ubuntu, exploratory
[Kernel-packages] [Bug 1297522] Re: Since Trusty /proc/diskstats shows weird values
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1297522
Title:
Since Trusty /proc/diskstats shows weird values
Status in “linux” package in Ubuntu:
Fix Released
Status in “linux” source package in Trusty:
Fix Committed
Bug description:
SRU Justification:
Impact: Tools that rely on diskstats may report incorrect data in
certain conditions. In particular diskstats in a VM may report
incorrect statistics.
Fix: 0fec08b4ecfc36fd8a64432343b2964fb86d2675 ( in 3.14-rc1 )
Testcase:
- Install a VM with the affected kernel
- Run cat /proc/diskstats | awk '$3=="vda" { print $7/$4, $11/$8 }'
- If the two values are much larger compared to the v3.14-rc1 kernel in the
same VM, we have failed. For example in a failing case I see: "132.44 5458.34";
in a passing case I see: "0.19334 5.90476".
--
After upgrading some virtual machines (KVM) to Trusty I noticed really
high I/O wait times, e.g. Munin graphs now show up to 200 seconds(!)
read I/O wait time. See attached image. Of course real latency isn't
higher than before, it's only /proc/diskstats that shows totally wrong
numbers...
$ cat /proc/diskstats | awk '$3=="vda" { print $7/$4, $11/$8 }'
1375.44 13825.1
From the documentation for /proc/diskstats field 4 is total number of
reads completed, field 7 is the total time spent reading in
milliseconds, and fields 8 and 11 are the same for writes. So above
numbers are the average read and write latency in milliseconds.
Same weird numbers with iowait. Note the column "await" (average time
in milliseconds for I/O requests):
$ iostat -dx 1 60
Linux 3.13.0-19-generic (munin) 03/25/14_x86_64_(2 CPU)
Device: rrqm/s wrqm/s r/s w/srkB/swkB/s avgrq-sz
avgqu-sz await r_await w_await svctm %util
vda 2.3016.75 72.45 24.52 572.79 778.3727.87
1.57 620.00 450.20 1121.83 1.71 16.54
Device: rrqm/s wrqm/s r/s w/srkB/swkB/s avgrq-sz
avgqu-sz await r_await w_await svctm %util
vda 0.00 0.000.000.00 0.00 0.00 0.00
0.000.000.000.00 0.00 0.00
Device: rrqm/s wrqm/s r/s w/srkB/swkB/s avgrq-sz
avgqu-sz await r_await w_await svctm %util
vda 0.00 0.000.000.00 0.00 0.00 0.00
0.000.000.000.00 0.00 0.00
Device: rrqm/s wrqm/s r/s w/srkB/swkB/s avgrq-sz
avgqu-sz await r_await w_await svctm %util
vda 0.0052.000.00 25.00 0.00 308.0024.64
0.30 27813.920.00 27813.92 0.48 1.20
I upgraded the host system to Trusty too, however there
/proc/diskstats output is normal as before.
$ uname -r
3.13.0-19-generic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1297522/+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 1363032] Re: linux: 3.16.0-12.17 -proposed tracker
** Changed in: kernel-development-workflow/promote-to-release Status: Incomplete => Fix Released ** Changed in: kernel-development-workflow Status: In Progress => 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/1363032 Title: linux: 3.16.0-12.17 -proposed tracker Status in Kernel Development Workflow: Fix Released Status in Kernel Development Workflow package-testing series: Won't Fix Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-release series: Fix Released Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Utopic: Fix Released Bug description: This bug is for tracking the 3.16.0-12.17 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Friday, 29. August 2014 10:53 UTC kernel-phase-changed:Friday, 29. August 2014 20:00 UTC kernel-Prepare-package-end:Friday, 29. August 2014 20:00 UTC kernel-Package-testing-start:Friday, 29. August 2014 20:00 UTC kernel-phase:PPA Testing ppa-package-testing-start:Friday, 29. August 2014 20:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1363032/+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 1366431] Re: linux: 3.16.0-14.20 -proposed tracker
** Changed in: kernel-development-workflow/promote-to-release 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/1366431 Title: linux: 3.16.0-14.20 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow package-testing series: Confirmed Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-release series: Fix Released Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Utopic: Fix Released Bug description: This bug is for tracking the 3.16.0-14.20 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Saturday, 06. September 2014 23:27 UTC kernel-phase-changed:Sunday, 07. September 2014 13:03 UTC kernel-Prepare-package-end:Sunday, 07. September 2014 13:03 UTC kernel-Package-testing-start:Sunday, 07. September 2014 13:03 UTC kernel-phase:PPA Testing ppa-package-testing-start:Sunday, 07. September 2014 13:03 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1366431/+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 1354604] Re: Regression: touchscreen-as-input not recognized in recent kernels (Dell Venue 11 Pro 7130)
Don't know if that helps, but I just tried the i386 version of Ubuntu 14.10. (published on the 5th of September 2014). And to my pleasant surprise video and touchscreen are working at the same time! Cheers, Alex -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1354604 Title: Regression: touchscreen-as-input not recognized in recent kernels (Dell Venue 11 Pro 7130) Status in “linux” package in Ubuntu: Triaged Bug description: Due to bug #1354598, my Dell Venue 11 Pro 7130 tablet is unusable as a tablet with the current Trusty kernel, so I have been attempting to find a more recent kernel for which the screen functions both as a display and a touch input device. No luck so far. (Well, actually, oddly enough, that's not quite true: I installed the 05-Aug-2014 01:21 daily live CD of Kubuntu Active, which is i386 only, and *that* worked just fine, from a kernel/hardware perspective. But I'm hoping to get an amd64 kernel working.) When booting either of the most recent Utopic kernel (3.16.0-6) and the kernel team's latest build of upstream (3.16.0-031600), the touchscreen is unresponsive to touch input, and inspection of the logs confirms that the multitouch device is not recognized as such. Will run apport-collect. Also the udev logs attached to bug #1354598 may be interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1354604/+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 1258675] Re: hardware switch of wireless not working for Centrino Advanced-N 6235
** Also affects: linux 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/1258675 Title: hardware switch of wireless not working for Centrino Advanced-N 6235 Status in The Linux Kernel: New Status in “linux” package in Ubuntu: Confirmed Bug description: I have ubuntu 13.10 64-bit running on a HP ZBook 15. The notebook uses an Intel Corporation Centrino Advanced-N 6235 (rev 24) wireless adapter. The wireless networking principally works. The issue is that it is not possible to enable or disable it using the hardware button. The only way is the software control (clicking on "Enable Wi-Fi"). BTW, when I click on "Enable Wi-Fi", it indicates the changes status of the wifi radio by changing the colour of the light on the hardware button. (This is the correct and expected behaviour. What is wrong is that I can not change the status by pressing the hardware button.) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-firmware 1.116 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Fri Dec 6 23:04:18 2013 Dependencies: InstallationDate: Installed on 2013-12-04 (2 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-01-31 (11 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140130) Package: linux (not installed) Tags: trusty Uname: Linux 3.14.0-031400rc2-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 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1258675/+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 1364092] Re: linux: 2.6.32-66.132 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: New => In Progress ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Description changed: This bug is for tracking the 2.6.32-66.132 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, 01. September 2014 17:01 UTC - kernel-stable-phase:PPA Testing - kernel-stable-phase-changed:Tuesday, 02. September 2014 01:04 UTC kernel-stable-Prepare-package-end:Tuesday, 02. September 2014 01:04 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 02. September 2014 01:04 UTC ppa-package-testing-start:Tuesday, 02. September 2014 01:04 UTC kernel-stable-Promote-to-proposed-end:Monday, 08. September 2014 20:03 UTC + kernel-stable-phase:Verification & Testing + kernel-stable-phase-changed:Monday, 08. September 2014 22:01 UTC + kernel-stable-Verification-testing-start:Monday, 08. September 2014 22:01 UTC + kernel-stable-Certification-testing-start:Monday, 08. September 2014 22:01 UTC + kernel-stable-Security-signoff-start:Monday, 08. September 2014 22:01 UTC + kernel-stable-Regression-testing-start:Monday, 08. September 2014 22:01 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1364092 Title: linux: 2.6.32-66.132 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed 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-66.132 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, 01. September 2014 17:01 UTC kernel-stable-Prepare-package-end:Tuesday, 02. September 2014 01:04 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 02. September 2014 01:04 UTC ppa-package-testing-start:Tuesday, 02. September 2014 01:04 UTC kernel-stable-Promote-to-proposed-end:Monday, 08. September 2014 20:03 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Monday, 08. September 2014 22:01 UTC kernel-stable-Verification-testing-start:Monday, 08. September 2014 22:01 UTC kernel-stable-Certification-testing-start:Monday, 08. September 2014 22:01 UTC kernel-stable-Security-signoff-start:Monday, 08. September 2014 22:01 UTC kernel-stable-Regression-testing-start:Monday, 08. September 2014 22:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1364092/+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 1354710] Re: Backlight control does not work, but there are entries in /sys/class/backlight. Lenovo B570
cannot test latest kernel as my machine requires i386 and only amd64 kernel is avalible 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/1354710 Title: Backlight control does not work, but there are entries in /sys/class/backlight. Lenovo B570 Status in “linux” package in Ubuntu: Confirmed Bug description: Laptop model: Lenovo B570 package version: Ubuntu 3.13.0-32.57-generic 3.13.11.4 I expected the keys for changeing the backlight brightness to work they had no effect on the backlight further details in attatched Tar ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic i686 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: x321x321 1977 F pulseaudio Date: Sat Aug 9 16:11:34 2014 HibernationDevice: RESUME=UUID=61c2c6a6-4b45-4af0-941a-dadf05ad0aba InstallationDate: Installed on 2014-07-31 (8 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140723) MachineType: LENOVO 1068FJG ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 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.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 44CN36WW dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Emerald Lake dmi.board.vendor: LENOVO dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnLENOVO:bvr44CN36WW:bd07/11/2011:svnLENOVO:pn1068FJG:pvrLenovoB570:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1: dmi.product.name: 1068FJG dmi.product.version: Lenovo B570 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1354710/+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 1366995] 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/1366995 Title: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK Status in “linux” package in Ubuntu: Confirmed Bug description: [ 133.559768] usb 3-4: new full-speed USB device number 3 using xhci_hcd [ 133.559818] usb 3-4: Device not responding to set address. [ 133.763858] usb 3-4: Device not responding to set address. [ 133.967861] usb 3-4: device not accepting address 3, error -71 [ 134.264036] usb 3-4: new high-speed USB device number 5 using xhci_hcd [ 134.281285] usb 3-4: New USB device found, idVendor=14cd, idProduct=125c [ 134.281297] usb 3-4: New USB device strings: Mfr=1, Product=3, SerialNumber=2 [ 134.281303] usb 3-4: Product: Mass Storage Device [ 134.281308] usb 3-4: Manufacturer: Generic [ 134.281313] usb 3-4: SerialNumber: 125C20100726 [ 134.308563] usb-storage 3-4:1.0: USB Mass Storage device detected [ 134.308819] scsi6 : usb-storage 3-4:1.0 [ 134.308973] usbcore: registered new interface driver usb-storage [ 135.308750] scsi 6:0:0:0: Direct-Access Mass Storage Device PQ: 0 ANSI: 0 CCS [ 135.309376] sd 6:0:0:0: Attached scsi generic sg2 type 0 [ 135.313573] sd 6:0:0:0: [sdc] 15448064 512-byte logical blocks: (7.90 GB/7.36 GiB) [ 135.316052] sd 6:0:0:0: [sdc] Write Protect is off [ 135.316066] sd 6:0:0:0: [sdc] Mode Sense: 03 00 00 00 [ 135.316235] sd 6:0:0:0: [sdc] No Caching mode page found [ 135.316242] sd 6:0:0:0: [sdc] Assuming drive cache: write through [ 135.317484] sd 6:0:0:0: [sdc] No Caching mode page found [ 135.317491] sd 6:0:0:0: [sdc] Assuming drive cache: write through [ 135.484534] usb 3-4: reset high-speed USB device number 5 using xhci_hcd [ 135.500885] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880096c85900 [ 135.500897] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880096c85940 [ 135.620390] usb 3-4: reset high-speed USB device number 5 using xhci_hcd [ 135.636948] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880096c85900 [ 135.636961] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880096c85940 [ 135.756549] usb 3-4: reset high-speed USB device number 5 using xhci_hcd [ 135.772968] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880096c85900 [ 135.772981] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880096c85940 [ 135.892554] usb 3-4: reset high-speed USB device number 5 using xhci_hcd [ 135.908986] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880096c85900 [ 135.908999] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880096c85940 [ 136.028598] usb 3-4: reset high-speed USB device number 5 using xhci_hcd [ 136.045011] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880096c85900 [ 136.045024] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880096c85940 [ 136.164640] usb 3-4: reset high-speed USB device number 5 using xhci_hcd [ 136.181172] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880096c85900 [ 136.181184] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880096c85940 [ 136.181565] sd 6:0:0:0: [sdc] Unhandled error code [ 136.181575] sd 6:0:0:0: [sdc] [ 136.181580] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 136.181584] sd 6:0:0:0: [sdc] CDB: [ 136.181587] Read(10): 28 00 00 00 00 00 00 00 08 00 [ 136.181606] end_request: I/O error, dev sdc, sector 0 [ 136.181614] Buffer I/O error on device sdc, logical block 0 [ 136.348579] usb 3-4: reset high-speed USB device number 5 using xhci_hcd [ 136.365080] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880096c85900 [ 136.365092] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880096c85940 [ 136.484606] usb 3-4: reset high-speed USB device number 5 using xhci_hcd [ 136.501105] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880096c85900 [ 136.501117] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880096c85940 [ 136.620595] usb 3-4: reset high-speed USB device number 5 using xhci_hcd [ 136.637119] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880096c85900 [ 136.637132] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880096c85940 [ 136.756731] usb 3-4: reset high-speed USB device number 5 using xhci_hcd [ 136.773053] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint
[Kernel-packages] [Bug 1239578] Re: No wireless support for Realtek RTL8192EE [10ec:818b]
Hi Larry. I used the source from mjeanson in #86. I will use your github and report back. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1239578 Title: No wireless support for Realtek RTL8192EE [10ec:818b] Status in HWE Next Project: Confirmed Status in HWE Next trusty series: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: Open this bug to trace device driver RTL8192EE. We have seen this wireless card on some laptops, id is [10ec:818b], driver is RTL8192EE. Status: waiting for this driver being moved out of staging directory. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1239578/+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 1366995] [NEW] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Public bug reported: [ 133.559768] usb 3-4: new full-speed USB device number 3 using xhci_hcd [ 133.559818] usb 3-4: Device not responding to set address. [ 133.763858] usb 3-4: Device not responding to set address. [ 133.967861] usb 3-4: device not accepting address 3, error -71 [ 134.264036] usb 3-4: new high-speed USB device number 5 using xhci_hcd [ 134.281285] usb 3-4: New USB device found, idVendor=14cd, idProduct=125c [ 134.281297] usb 3-4: New USB device strings: Mfr=1, Product=3, SerialNumber=2 [ 134.281303] usb 3-4: Product: Mass Storage Device [ 134.281308] usb 3-4: Manufacturer: Generic [ 134.281313] usb 3-4: SerialNumber: 125C20100726 [ 134.308563] usb-storage 3-4:1.0: USB Mass Storage device detected [ 134.308819] scsi6 : usb-storage 3-4:1.0 [ 134.308973] usbcore: registered new interface driver usb-storage [ 135.308750] scsi 6:0:0:0: Direct-Access Mass Storage Device PQ: 0 ANSI: 0 CCS [ 135.309376] sd 6:0:0:0: Attached scsi generic sg2 type 0 [ 135.313573] sd 6:0:0:0: [sdc] 15448064 512-byte logical blocks: (7.90 GB/7.36 GiB) [ 135.316052] sd 6:0:0:0: [sdc] Write Protect is off [ 135.316066] sd 6:0:0:0: [sdc] Mode Sense: 03 00 00 00 [ 135.316235] sd 6:0:0:0: [sdc] No Caching mode page found [ 135.316242] sd 6:0:0:0: [sdc] Assuming drive cache: write through [ 135.317484] sd 6:0:0:0: [sdc] No Caching mode page found [ 135.317491] sd 6:0:0:0: [sdc] Assuming drive cache: write through [ 135.484534] usb 3-4: reset high-speed USB device number 5 using xhci_hcd [ 135.500885] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880096c85900 [ 135.500897] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880096c85940 [ 135.620390] usb 3-4: reset high-speed USB device number 5 using xhci_hcd [ 135.636948] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880096c85900 [ 135.636961] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880096c85940 [ 135.756549] usb 3-4: reset high-speed USB device number 5 using xhci_hcd [ 135.772968] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880096c85900 [ 135.772981] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880096c85940 [ 135.892554] usb 3-4: reset high-speed USB device number 5 using xhci_hcd [ 135.908986] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880096c85900 [ 135.908999] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880096c85940 [ 136.028598] usb 3-4: reset high-speed USB device number 5 using xhci_hcd [ 136.045011] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880096c85900 [ 136.045024] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880096c85940 [ 136.164640] usb 3-4: reset high-speed USB device number 5 using xhci_hcd [ 136.181172] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880096c85900 [ 136.181184] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880096c85940 [ 136.181565] sd 6:0:0:0: [sdc] Unhandled error code [ 136.181575] sd 6:0:0:0: [sdc] [ 136.181580] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 136.181584] sd 6:0:0:0: [sdc] CDB: [ 136.181587] Read(10): 28 00 00 00 00 00 00 00 08 00 [ 136.181606] end_request: I/O error, dev sdc, sector 0 [ 136.181614] Buffer I/O error on device sdc, logical block 0 [ 136.348579] usb 3-4: reset high-speed USB device number 5 using xhci_hcd [ 136.365080] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880096c85900 [ 136.365092] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880096c85940 [ 136.484606] usb 3-4: reset high-speed USB device number 5 using xhci_hcd [ 136.501105] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880096c85900 [ 136.501117] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880096c85940 [ 136.620595] usb 3-4: reset high-speed USB device number 5 using xhci_hcd [ 136.637119] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880096c85900 [ 136.637132] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880096c85940 [ 136.756731] usb 3-4: reset high-speed USB device number 5 using xhci_hcd [ 136.773053] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880096c85900 [ 136.773066] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880096c85940 [ 136.892727] usb 3-4: reset high-speed USB device number 5 using xhci_hcd [ 136.909310] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880096c85900 [ 136.909322] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880096c85940 [ 137.028692] usb 3-4: reset high-speed USB devi
[Kernel-packages] [Bug 1358498] Re: ahci-xgene falsely advertises NCQ support
ubuntu@am3:~$ dmesg | grep -i ncq [1.309746] xgene-ahci 1a80.sata: controller can't do NCQ, turning off CAP_NCQ [1.725691] ata3.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 0/32) ubuntu@am3:~$ ** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1358498 Title: ahci-xgene falsely advertises NCQ support Status in “linux” package in Ubuntu: In Progress Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: In Progress Bug description: [IMPACT] ahci-xgene doesn't support NCQ but it sets this flag. This causes SATA failures that surface as a filesystem being remounted read-only due to errors when using a disk that supports NCQ. [TEST CASE] Do a network boot install on an X-Gene system with an SSD drive that supports NCQ. The install will fail and dmesg will show the filesystem being remounted read-only. [Regression Potential] Minimal; we're turning off a feature that is known broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358498/+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 1357527] Re: [Trusty] support for X-Gene PMU in perf
perf is working for me ** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1357527 Title: [Trusty] support for X-Gene PMU in perf Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Fix Released Bug description: Trusty doesn't currently support the X-Gene PMU, which prevents perf from making use of hardware counters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1357527/+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 1354710] Re: Backlight control does not work, but there are entries in /sys/class/backlight. Lenovo B570
I built the next test kernel, up to the following commit: 91bc033c4d01656e3d8e45a13fd58924a3099693 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1354710 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results. Thanks in advance -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1354710 Title: Backlight control does not work, but there are entries in /sys/class/backlight. Lenovo B570 Status in “linux” package in Ubuntu: Confirmed Bug description: Laptop model: Lenovo B570 package version: Ubuntu 3.13.0-32.57-generic 3.13.11.4 I expected the keys for changeing the backlight brightness to work they had no effect on the backlight further details in attatched Tar ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic i686 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: x321x321 1977 F pulseaudio Date: Sat Aug 9 16:11:34 2014 HibernationDevice: RESUME=UUID=61c2c6a6-4b45-4af0-941a-dadf05ad0aba InstallationDate: Installed on 2014-07-31 (8 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140723) MachineType: LENOVO 1068FJG ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 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.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 44CN36WW dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Emerald Lake dmi.board.vendor: LENOVO dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnLENOVO:bvr44CN36WW:bd07/11/2011:svnLENOVO:pn1068FJG:pvrLenovoB570:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1: dmi.product.name: 1068FJG dmi.product.version: Lenovo B570 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1354710/+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 1354234] Re: 14.04: PANIC with "dcache shrink list corruption?" problem
** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1354234 Title: 14.04: PANIC with "dcache shrink list corruption?" problem Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Fix Released Bug description: Hello, 14.04 kernel linux_3.13.0-32.57 panicked because of "dcache shrink list corruption?" problem. Please see followings: - details at https://lkml.org/lkml/2014/5/2/555. - argument at https://lkml.org/lkml/2014/4/29/402 - patch set at https://lkml.org/lkml/2014/5/4/7 One of 9 patches has been applied to linux_3.13.0-32.57 already. Could you apply other 8 patches to the next 14.04 kernel ? We will need the kernel at the beginning of August badly. If we will not be able to get it, we will not be able to start tests before service in. Could you release it as soon as possible ? We applied other 8 patches to linux_3.13.0-32.57 and now the panic does not occur. Public Bug URL: https://lkml.org/lkml/2014/5/2/555 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1354234/+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 1353021] Re: USB HIDRAW Feature Report Implementation for HID devices not working correctly in Ubuntu 14.04
I confirm that kernel 3.13.0-36 from -proposed also solves the issues regarding Sixaxis/Dualshock3 controller described in duplicate bug #1326725. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1353021 Title: USB HIDRAW Feature Report Implementation for HID devices not working correctly in Ubuntu 14.04 Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Fix Released Bug description: With the release of Ubuntu 14.04 I've been investigating an issue with a software library I maintain to talk to USB based HID signature pads. I believe I've narrowed the issue down to the HIDRAW implementation released with Ubuntu 14.04. Essentially what seems to be failing is the ioctl to get feature reports (HIDIOCGFEATURE). Any attempt to get a feature report results in a failure with a ENODEV error code. The devices I'm testing with are USB signature pads (http://www.scriptel.com). These signature pads use HID feature reports to communicate capabilities and to set up the device. I can provide further information along with USB/HID descriptors if it would be helpful. I have been testing with Ubuntu 14.04 Desktop (x64) with kernel version: Linux 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux This kernel exhibits the problematic behavior, but when testing with Ubuntu 13.10 Desktop (x64): Linux 3.11.0-23-generic #40-Ubuntu SMP Wed Jun 4 21:05:23 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux The 13.10 kernel's version of HIDRAW seems to work correctly. I've also tested with the vanilla kernel: Linux 3.13.1-hidtest #1 SMP Tue Aug 5 09:14:28 EDT 2014 x86_64 x86_64 x86_64 GNU/Linux The vanilla kernel appears to work correctly as well. Kernel source used was downloaded from: https://www.kernel.org/pub/linux/kernel/v3.x/linux-3.13.1.tar.xz The configuration file used was from config-3.13.0-32-generic provided in linux-image-3.13.0-32-generic I believe the breaking change was made as part of commit aa6c390c4d59c9ff4fffd887e15783b2b793951b as part of ubuntu/ubuntu- trusty.git. I have attached a simple C program to demonstrate the problem. You'll need a USB HID device with known feature reports. Please let me know if I can provide any additional information or be of any assistance. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 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: mpowers2863 F pulseaudio CurrentDesktop: Unity Date: Tue Aug 5 13:51:39 2014 HibernationDevice: RESUME=UUID=3a5a866c-6086-47d6-8080-70715896a719 InstallationDate: Installed on 2014-04-17 (109 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=9b49575f-fb86-45d7-af5e-b3fde82f91ac ro quiet splash 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/07/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1762II1.50U dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: CZ-17 dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1762II1.50U:bd12/07/2012:svn:pnCZ-17:pvrREV1.0:rvn:rnCZ-17:rvrREV1.0:cvnToBeFilledByO.E.M.:ct10:cvrTobefilledbyO.E.M.: dmi.product.name: CZ-17 dmi.product.version: REV:1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1353021/+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 1329434] Re: nested KVM fails on intel hardware - KVM: entry failed, hardware error 0x0
** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1329434 Title: nested KVM fails on intel hardware - KVM: entry failed, hardware error 0x0 Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Bug description: [Impact] Using nested KVM on some hypervisors doesn't work. [Test Case] A script to make this easier is posted here: https://gist.github.com/arges/9d21c6da03a8c10d3980 1) enable nested KVM: sudo modprobe -r kvm_intel sudo modprobe kvm_intel nested=1 cat /sys/module/kvm_intel/parameters/nested # should say Y 2) generate an L1 guest and then generate an L2 guest inside the L1 guest - ensure L1 has enough memory to boot L2 - if using libvirt you may need to edit the default bridge to use a different subnet than the L1 guest 3) boot the L2 guest 4) L2 guest should boot [Fix] These three upstream patches needed to be backported to 3.13: * 533558bcb69ef28aff81b6ae9acda8943575319f - This provides necessary code changes to make backporting easier. However vmx_leave_nested function was not yet added, so that function modification was dropped. * b6b8a1451fc40412c57d10c94b62e22acab28f94 - This patch is necessary in order to ensure that the L1 guest doesn't crash with just 696dfd95 applied. I had to remove mpx mentions from the cherry-pick as that feature hasn't been added yet. * 696dfd95ba9838327a7013e5988ff3ba60dcc8c8 - This patch fixes the issue and was the result of the bisection. The APIC virtualization features need to be disabled as they cause L2 guests to not boot depending on the CPU. -- If the L2 guest doesn't boot you can see the log: sudo cat /var/log/libvirt/qemu/nested-L2.log KVM: entry failed, hardware error 0x0 EAX= EBX= ECX= EDX=0663 ESI= EDI= EBP= ESP= EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=00 66 89 d8 66 e8 02 f7 ff ff 66 83 c4 0c 66 5b 66 5e 66 c3 5b e0 00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 13 18:26 seq crw-rw 1 root audio 116, 33 Jun 13 18:26 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.2 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: DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: Intel Corporation S2600WTT Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=b5d11a1d-c48f-4abf-a622-d1efe52fe97c ro 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 1.127.2 RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-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 libvirtd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 05/06/2014 dmi.bios.vendor: Intel Corporation dmi.bios.version: GRNDSDP1.86B.0030.R03.1405061547 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: S2600WTT dmi.board.vendor: Intel Corporation dmi.board.version: H30334-201 dmi.chassis.asset.tag: dmi.chassis.type: 23 dmi.chassis.vendor: ... dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorporation:bvrGRNDSDP1.86B.0030.R03.1405061547:bd05/06/2014:svnIntelCorporation:pnS2600WTT:pvr:rvnIntelCorporation:rnS2600WTT:rvrH30334-201:cvn...:ct23:cvr..: dmi.product.name: S2600WTT dmi.product.ve
[Kernel-packages] [Bug 1363313] Re: mpt2sas not loaded with LSISAS2008 card in trusty 14.04.1
Hi Joe, With the v1 kernel-- cat /boot/config-$(uname -r) | grep CONFIG_PCI_REALLOC_ENABLE_AUTO # CONFIG_PCI_REALLOC_ENABLE_AUTO is not set with the v2-- cat /boot/config-$(uname -r) | grep CONFIG_PCI_REALLOC_ENABLE_AUTO CONFIG_PCI_REALLOC_ENABLE_AUTO=y And yes, the problem is back with v2. Let me know if there is anything I can do to help. - Paul -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1363313 Title: mpt2sas not loaded with LSISAS2008 card in trusty 14.04.1 Status in “linux” package in Ubuntu: Confirmed Bug description: This card has worked without a problem in 12.04 up through the current kernel. After an upgrade to 14.04.1, mpt2sas tries to load during boot but fails. An apport file from this machine is attached; note the error messages during boot. --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: admsvr 3757 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7192beea-6a28-4c3f-b274-3332e6d007b7 InstallationDate: Installed on 2010-09-14 (1445 days ago) InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 (20100427) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. P55-UD3L NonfreeKernelModules: zfs zunicode zavl zcommon znvpair Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=46ac1ed7-062a-4ae3-b071-52ccee0cc346 ro splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 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.5 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.13.0-35-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-08-23 (6 days ago) UserGroups: adm admin cdrom dialout lpadmin lpadmin mythtv plugdev sambashare vboxusers _MarkForUpload: True dmi.bios.date: 06/23/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7 dmi.board.name: P55-UD3L dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7:bd06/23/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55-UD3L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55-UD3L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P55-UD3L dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1363313/+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 1362199] Re: [FFe] apparmor abstract, anonymous and netlink socket mediation
** Description changed: Background: kernel and apparmor userspace updates to support abstract, anonymous and fine-grained netlink socket mediation. These packages are listed in one bug because they are related, but the FFes may be granted and the uploads may happen at different times. = apparmor userspace = Summary: This feature freeze exception is requested for abstract, anonymous and fine-grained netlink socket for apparmor userspace. When used with a compatible kernel, 'unix' and 'network netlink' rules are supported. When used without a compatible apparmor userspace (eg, on a trusty system with an utopic backport kernel), abstract, anonymous and fine-grained netlink socket mediation is not enforced (ie, you can use this userspace with an old kernel without any issues). Testing: - * 14.10 system with previous kernel lacking abstract, anonymous and fine-grained netlink socket mediation (non-Touch): + * 14.10 system with current kernels lacking abstract, anonymous and fine-grained netlink socket mediation (non-Touch): * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: DONE (exploratory manual testing, lxc, libvirt, etc) * 14.10 system kernel capable of supporting abstract, anonymous and fine-grained netlink socket mediation (non-Touch): * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: INPROGRESS (includes test-apparmor.py, exploratory manual testing, lxc, libvirt, etc) * Verify everything in https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/AppArmorProfiles: DONE (except juju since it doesn't have policy itself) Justification: This feature is required to support comprehensive application confinement on Ubuntu Touch. This feature adds a security benefit to libvirt's qemu guest isolation which is fundamental to Ubuntu on Server/Cloud. This feature also adds a welcome improvement to administrators wishing to further protect their systems. Extra information: While the apparmor userspace and kernel changes to support abstract, anonymous and fine-grained netlink socket can happen at different times, the apparmor userspace upload must correspond with uploads for packages that ship AppArmor policy that require updates (eg, libvirt, lxc, etc). The packages outlined in https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/AppArmorProfiles have been tested to either work without modification to the policy or updated and tested to work with updated policy. Common rules will be added to the apparmor base abstraction such that most packages shipping apparmor policy will not require updating. These updates will be prepared, tested and published en masse via a silo ppa. - = linux = Summary: This feature freeze exception is requested for abstract, anonymous and fine-grained netlink socket via apparmor in the kernel. When used with a compatible apparmor userspace, 'unix' and 'network netlink' rules are supported. When used without a compatible apparmor userspace (eg, on a trusty system with an utopic backport kernel), abstract, anonymous and fine-grained netlink socket mediation is not enforced (ie, you can use this kernel with an old userspace without any issues). Testing: * 14.04 system with backported kernel: TODO - * test-apparmor.py: TODO (runs extensive tests (upstream and distro)) - * exploratory manual testing: TODO (networking, aa-enforce with firefox, firefox works, apparmor blocks access, etc) - * aa-status: TODO - * lxc: TODO (containers can be created, started, shutdown) - * libvirt: TODO (VMs started via openstack, and test-libvirt.py from QRT passes all tests) + * test-apparmor.py: TODO (runs extensive tests (upstream and distro)) + * exploratory manual testing: TODO (networking, aa-enforce with firefox, firefox works, apparmor blocks access, etc) + * aa-status: TODO + * lxc: TODO (containers can be created, started, shutdown) + * libvirt: TODO (VMs started via openstack, and test-libvirt.py from QRT passes all tests) * 14.10 system (non-Touch) with updated kernel: - * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: INPROGRESS (includes click-apparmor, apparmor-easyprof-ubuntu, exploratory manual testing, etc) + * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: INPROGRESS (includes click-apparmor, apparmor-easyprof-ubuntu, exploratory manual testing, etc) * 14.10 system (Touch) with updated kernel: - * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: INPROGRESS (includes click-apparmor, apparmor-easyprof-ubuntu, exploratory manual testing, etc) + * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: INPROGRESS (includes click-apparmor, apparmor-easyprof-ubuntu, exploratory manual testing, etc) Justification: This feature is required to support comprehensive application confinement on Ubuntu Touch. This feature adds a security benefit to libvirt's qemu guest isolation which is fundamental to Ubuntu on Server/Cloud. Thi
[Kernel-packages] [Bug 1356558] Re: BUG: soft lockup - CPU stuck for 22s! [md3_raid1]
c6c1f325adc8a8e0cd06c6ad0ca232a6880a1783: exhibits this bug: Sep 8 22:18:29 box kernel: [ 1940.144024] BUG: soft lockup - CPU#0 stuck for 22s! [md3_raid1:172] Sep 8 22:18:29 box kernel: [ 1940.144024] Modules linked in: xt_multiport iptable_filter ip_tables x_tables gpio_ich snd_hda_codec_realtek coretemp snd_hda_intel snd_hda_codec serio_raw snd_hwdep pl2303 usblp usbserial lpc_ich snd_pcm snd_page_alloc snd_timer i915 drm_kms_helper snd drm soundcore i2c_algo_bit video mac_hid parport_pc ppdev lp parport dm_snapshot raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor ahci psmouse r8169 sata_via libahci raid6_pq mii raid1 raid0 multipath linear Sep 8 22:18:29 box kernel: [ 1940.144024] CPU: 0 PID: 172 Comm: md3_raid1 Not tainted 3.13.0-031300rc1-generic #201409081748 Sep 8 22:18:29 box kernel: [ 1940.144024] Hardware name: /D945GSEJT, BIOS JT94510H.86A.0045.2010.0519.1750 05/19/2010 Sep 8 22:18:29 box kernel: [ 1940.144024] task: f6888cf0 ti: f6b68000 task.ti: f6b68000 Sep 8 22:18:29 box kernel: [ 1940.144024] EIP: 0060:[] EFLAGS: 0297 CPU: 0 Sep 8 22:18:29 box kernel: [ 1940.144024] EIP is at memcmp+0x32/0x60 Sep 8 22:18:29 box kernel: [ 1940.144024] EAX: ecb27000 EBX: 007e ECX: 0962 EDX: ec8de000 Sep 8 22:18:29 box kernel: [ 1940.144024] ESI: 007e EDI: 0fff EBP: f6b69e9c ESP: f6b69e8c Sep 8 22:18:29 box kernel: [ 1940.144024] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 Sep 8 22:18:29 box kernel: [ 1940.144024] CR0: 8005003b CR2: bfc95ef4 CR3: 01ae4000 CR4: 07f0 Sep 8 22:18:29 box kernel: [ 1940.144024] Stack: Sep 8 22:18:29 box kernel: [ 1940.144024] 0006 1000 0048 f6b69ee0 f845d3b3 ec8de000 0001 Sep 8 22:18:29 box kernel: [ 1940.144024] 000f f6847800 0007 ecb9e800 f69d2f80 f50da4e0 000c ecb9ea00 Sep 8 22:18:29 box kernel: [ 1940.144024] 001c ecd53300 0002 ecd53300 f6847800 f6b69f00 f845d667 f6847800 Sep 8 22:18:29 box kernel: [ 1940.144024] Call Trace: Sep 8 22:18:29 box kernel: [ 1940.144024] [] process_checks+0x173/0x300 [raid1] Sep 8 22:18:29 box kernel: [ 1940.144024] [] sync_request_write+0x127/0x160 [raid1] Sep 8 22:18:29 box kernel: [ 1940.144024] [] raid1d+0x102/0x140 [raid1] Sep 8 22:18:29 box kernel: [ 1940.144024] [] md_thread+0xe4/0x110 Sep 8 22:18:29 box kernel: [ 1940.144024] [] ? __wake_up_sync+0x20/0x20 Sep 8 22:18:29 box kernel: [ 1940.144024] [] ? md_rdev_init+0x100/0x100 Sep 8 22:18:29 box kernel: [ 1940.144024] [] kthread+0x9b/0xb0 Sep 8 22:18:29 box kernel: [ 1940.144024] [] ret_from_kernel_thread+0x1b/0x28 Sep 8 22:18:29 box kernel: [ 1940.144024] [] ? flush_kthread_worker+0x90/0x90 Sep 8 22:18:29 box kernel: [ 1940.144024] Code: ec 04 85 c9 c7 45 f0 00 00 00 00 74 29 0f b6 30 0f b6 1a 29 de 89 75 f0 75 1c 8d 79 ff 31 c9 eb 11 0f b6 74 08 01 0f b6 5c 0a 01 <83> c1 01 29 de 75 0f 39 f9 75 eb 8b 45 f0 83 c4 04 5b 5e 5f 5d Sep 8 22:38:36 box mdadm[1615]: Rebuild21 event detected on md device /dev/md/03 Sep 8 22:41:05 box kernel: [ 3296.144025] BUG: soft lockup - CPU#0 stuck for 22s! [md3_raid1:172] Sep 8 22:41:05 box kernel: [ 3296.144025] Modules linked in: xt_multiport iptable_filter ip_tables x_tables gpio_ich snd_hda_codec_realtek coretemp snd_hda_intel snd_hda_codec serio_raw snd_hwdep pl2303 usblp usbserial lpc_ich snd_pcm snd_page_alloc snd_timer i915 drm_kms_helper snd drm soundcore i2c_algo_bit video mac_hid parport_pc ppdev lp parport dm_snapshot raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor ahci psmouse r8169 sata_via libahci raid6_pq mii raid1 raid0 multipath linear Sep 8 22:41:05 box kernel: [ 3296.144025] CPU: 0 PID: 172 Comm: md3_raid1 Not tainted 3.13.0-031300rc1-generic #201409081748 Sep 8 22:41:05 box kernel: [ 3296.144025] Hardware name: /D945GSEJT, BIOS JT94510H.86A.0045.2010.0519.1750 05/19/2010 Sep 8 22:41:05 box kernel: [ 3296.144025] task: f6888cf0 ti: f6b68000 task.ti: f6b68000 Sep 8 22:41:05 box kernel: [ 3296.144025] EIP: 0060:[] EFLAGS: 0293 CPU: 0 Sep 8 22:41:05 box kernel: [ 3296.144025] EIP is at memcmp+0x3b/0x60 Sep 8 22:41:05 box kernel: [ 3296.144025] EAX: ec884000 EBX: 00ed ECX: 0056 EDX: ecddf000 Sep 8 22:41:05 box kernel: [ 3296.144025] ESI: EDI: 0fff EBP: f6b69e9c ESP: f6b69e8c Sep 8 22:41:05 box kernel: [ 3296.144025] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 Sep 8 22:41:05 box kernel: [ 3296.144025] CR0: 8005003b CR2: b88467a4 CR3: 01ae4000 CR4: 07f0 Sep 8 22:41:05 box kernel: [ 3296.144025] Stack: Sep 8 22:41:05 box kernel: [ 3296.144025] 000b 1000 0084 f6b69ee0 f845d3b3 ecddf000 0001 Sep 8 22:41:05 box kernel: [ 3296.144025] 000f f6847800 000c ec8c1400 f69d2f80 f50d5080 000c eccb8000 Sep 8 22:41:05 box kernel: [ 3296.144025] 001c ece7ed20 0002 ece7ed20 f6847800 f6b69f00 f845d667 f6847800 Sep 8 22:41:05
[Kernel-packages] [Bug 1366248] Re: [Intel D54250WYK] Wireless Dropped Connection Intel 7260.HMWG
The kernel I referred to in comment #4 is now available for testing in -proposed. Please try it and see if it resolves your issues. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Thanks! ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1366248 Title: [Intel D54250WYK] Wireless Dropped Connection Intel 7260.HMWG Status in “linux” package in Ubuntu: Incomplete Bug description: The wireless connection is dropping once again. Everything seemed fine after the last dist-upgrade on or around 8/29. An apt-get update/upgrade between 8/29 and 9/3 seems to have introduced this bug. 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.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: justin 1549 F pulseaudio /dev/snd/controlC0: justin 1549 F pulseaudio CurrentDesktop: Unity Date: Fri Sep 5 19:51:33 2014 HibernationDevice: RESUME=UUID=8048d919-eb4b-45eb-a626-ebd626d468f1 InstallationDate: Installed on 2014-04-25 (133 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic.efi.signed root=UUID=ba994e83-d5aa-4912-825f-c6d10a7d86ae 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.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2014 dmi.bios.vendor: Intel Corp. dmi.bios.version: WYLPT10H.86A.0025.2014.0303.1008 dmi.board.name: D54250WYK dmi.board.vendor: Intel Corporation dmi.board.version: H13922-303 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrWYLPT10H.86A.0025.2014.0303.1008:bd03/03/2014:svn:pn:pvr:rvnIntelCorporation:rnD54250WYK:rvrH13922-303:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1366248/+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 1329434] Re: nested KVM fails on intel hardware - KVM: entry failed, hardware error 0x0
I tested and I am currently using the latest patch. It works 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/1329434 Title: nested KVM fails on intel hardware - KVM: entry failed, hardware error 0x0 Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Bug description: [Impact] Using nested KVM on some hypervisors doesn't work. [Test Case] A script to make this easier is posted here: https://gist.github.com/arges/9d21c6da03a8c10d3980 1) enable nested KVM: sudo modprobe -r kvm_intel sudo modprobe kvm_intel nested=1 cat /sys/module/kvm_intel/parameters/nested # should say Y 2) generate an L1 guest and then generate an L2 guest inside the L1 guest - ensure L1 has enough memory to boot L2 - if using libvirt you may need to edit the default bridge to use a different subnet than the L1 guest 3) boot the L2 guest 4) L2 guest should boot [Fix] These three upstream patches needed to be backported to 3.13: * 533558bcb69ef28aff81b6ae9acda8943575319f - This provides necessary code changes to make backporting easier. However vmx_leave_nested function was not yet added, so that function modification was dropped. * b6b8a1451fc40412c57d10c94b62e22acab28f94 - This patch is necessary in order to ensure that the L1 guest doesn't crash with just 696dfd95 applied. I had to remove mpx mentions from the cherry-pick as that feature hasn't been added yet. * 696dfd95ba9838327a7013e5988ff3ba60dcc8c8 - This patch fixes the issue and was the result of the bisection. The APIC virtualization features need to be disabled as they cause L2 guests to not boot depending on the CPU. -- If the L2 guest doesn't boot you can see the log: sudo cat /var/log/libvirt/qemu/nested-L2.log KVM: entry failed, hardware error 0x0 EAX= EBX= ECX= EDX=0663 ESI= EDI= EBP= ESP= EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=00 66 89 d8 66 e8 02 f7 ff ff 66 83 c4 0c 66 5b 66 5e 66 c3 5b e0 00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 13 18:26 seq crw-rw 1 root audio 116, 33 Jun 13 18:26 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.2 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: DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: Intel Corporation S2600WTT Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=b5d11a1d-c48f-4abf-a622-d1efe52fe97c ro 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 1.127.2 RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-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 libvirtd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 05/06/2014 dmi.bios.vendor: Intel Corporation dmi.bios.version: GRNDSDP1.86B.0030.R03.1405061547 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: S2600WTT dmi.board.vendor: Intel Corporation dmi.board.version: H30334-201 dmi.chassis.asset.tag: dmi.chassis.type: 23 dmi.chassis.vendor: ... dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorporation:bvrGRNDSDP1.86B.0030.R03.1405061547:bd05/06/2014:svnIntelCorporation:pnS2600WTT:pvr:rvnIntelCorporation:rnS2600WTT:rvrH30334-201:cvn...:ct23:cvr..: dmi.product.name: S2600WTT dmi.product.version:
[Kernel-packages] [Bug 1353021] Re: USB HIDRAW Feature Report Implementation for HID devices not working correctly in Ubuntu 14.04
Verified today that my test application as well as my library and applications appear to work correctly with the kernel in -proposed with version: Linux 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3 21:30:07 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Please let me know if you'd like me to test anything else. ** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1353021 Title: USB HIDRAW Feature Report Implementation for HID devices not working correctly in Ubuntu 14.04 Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Fix Released Bug description: With the release of Ubuntu 14.04 I've been investigating an issue with a software library I maintain to talk to USB based HID signature pads. I believe I've narrowed the issue down to the HIDRAW implementation released with Ubuntu 14.04. Essentially what seems to be failing is the ioctl to get feature reports (HIDIOCGFEATURE). Any attempt to get a feature report results in a failure with a ENODEV error code. The devices I'm testing with are USB signature pads (http://www.scriptel.com). These signature pads use HID feature reports to communicate capabilities and to set up the device. I can provide further information along with USB/HID descriptors if it would be helpful. I have been testing with Ubuntu 14.04 Desktop (x64) with kernel version: Linux 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux This kernel exhibits the problematic behavior, but when testing with Ubuntu 13.10 Desktop (x64): Linux 3.11.0-23-generic #40-Ubuntu SMP Wed Jun 4 21:05:23 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux The 13.10 kernel's version of HIDRAW seems to work correctly. I've also tested with the vanilla kernel: Linux 3.13.1-hidtest #1 SMP Tue Aug 5 09:14:28 EDT 2014 x86_64 x86_64 x86_64 GNU/Linux The vanilla kernel appears to work correctly as well. Kernel source used was downloaded from: https://www.kernel.org/pub/linux/kernel/v3.x/linux-3.13.1.tar.xz The configuration file used was from config-3.13.0-32-generic provided in linux-image-3.13.0-32-generic I believe the breaking change was made as part of commit aa6c390c4d59c9ff4fffd887e15783b2b793951b as part of ubuntu/ubuntu- trusty.git. I have attached a simple C program to demonstrate the problem. You'll need a USB HID device with known feature reports. Please let me know if I can provide any additional information or be of any assistance. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 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: mpowers2863 F pulseaudio CurrentDesktop: Unity Date: Tue Aug 5 13:51:39 2014 HibernationDevice: RESUME=UUID=3a5a866c-6086-47d6-8080-70715896a719 InstallationDate: Installed on 2014-04-17 (109 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=9b49575f-fb86-45d7-af5e-b3fde82f91ac ro quiet splash 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/07/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1762II1.50U dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: CZ-17 dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1762II1.50U:bd12/07/2012:svn:pnCZ-17:pvrREV1.0:rvn:rnCZ-17:rvrREV1.0:cvnToBeFilledByO.E.M.:ct10:cvrTobefilledbyO.E.M.: dmi.product.name: CZ-17 dmi.product.version: REV:1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1353021/+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 1361086] Re: No card reader support for Realtek RTL8402 [ff00:5286]
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1361086 Title: No card reader support for Realtek RTL8402 [ff00:5286] Status in HWE Next Project: Fix Released Status in HWE Next trusty series: Fix Committed Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Fix Released Bug description: SRU Justification: Impact: Realtek RTL8402 [ff00:5286], which is widely used by PC vendors, won't work without this fix. Fix: two patches below coming from upstream, clean cherry-picks. Testcase: we already tested and delivered the fix by dkms in OEM projects, works well. commit 56cb3cc1872923b69fdeeb00362b7da4d6cf5590 Author: Micky Ching Date: Wed Dec 18 10:03:13 2013 +0800 mfd: rtsx: Add support for card reader rtl8402 rtl8402 is much like rtl8411, so just add it to rtl8411.c Signed-off-by: Micky Ching Reviewed-by: Dan Carpenter Signed-off-by: Lee Jones commit 0da14eeba216932db2e4b8805ab58dae72e44a45 Author: Micky Ching Date: Wed Dec 18 10:03:12 2013 +0800 mfd: rtsx: Add set pull control macro and simplify rtl8411 Add set pull control macro to reduce code for setting pull control, and use a common init function to reduce code for rtl8411.c. So this patch is used to just simplify code. Signed-off-by: Micky Ching Reviewed-by: Dan Carpenter Signed-off-by: Lee Jones To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1361086/+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 1359514] Re: pci-xgene-msi: fixed deadlock in irq_set_affinity
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1359514 Title: pci-xgene-msi: fixed deadlock in irq_set_affinity Status in “linux” package in Ubuntu: In Progress Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: In Progress Bug description: [IMPACT] Issue: CPU affinity is changed while irqbalance is running. + Problem explanation: - Old code + Call xgene_msi_cascade function (CPU x) + raw_spin_lock(&desc->lock); (CPU x) + Goto generic_handle_irq (CPU x) + The CPU x doesn't have a chance to exit the xgene_msi_cascade function to unlock desc->lock before Linux scheduce and call xgene_msi_set_affinity (irqbalance is caller) in the same CPU x + In irq_set_affinity, call raw_spin_lock_irqsave(&desc->lock, flags) which cause deadlock to CPU x because it disables preempt - New code + Use chained_irq_enter and exit as the standard way to cascade interrupt functions. [TEST CASE] Turn off irqbalance Run a single tcp stream Randomly change the affinity of the receiving ring: @ ethtool -S $INTF | grep rx[0-9].*_pac @ - to detect the rx ring @ grep $INTF /proc/interrupts@ - to find it's interrupt @ printf "%x" $(( 2 ** $((RANDOM % 8)) )) > /proc/irq/$IRQ/smp_affinity @ - to change the affinity [Regression Potential] Fix specific to the xgene pci msi code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359514/+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 1349572] Re: Wireless network disconnections on Dell XPS 13
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1349572 Title: Wireless network disconnections on Dell XPS 13 Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Fix Released Bug description: SRU Justification Impact: Many users with Intel 7260 wireless are seeing relatively frequent disconnections as a result of the firmware reporting loss of beacons from the access point. Fix: Two upstream backports, one which waits for several lost beacon reports before reporting beacon loss to mac80211, and another which fixes a bug with mac80211's handling of beacon loss reports from some drivers (in particular iwlwifi). Test Case: Tested on LP#1349572. Regression Potential: These patches were merged upstream in 3.14 and 3.15 without any reported regressions. --- With kernel 3.13.0.30 and 22.1.7.0, there are lots of wireless disconnections. Tested also with kernel 3.13.0.32 and 22.24.8.0 , also lots of wireles disconnections. The AP is an ASL-26555 from Movistar(Spain). Firmware version: v2.0.0.51B_ESv6 Seems that when the computer is working for some time it is more easy to reproduce this beahviour. Added this bug as sugested in #1293569, comment #91. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-30-generic 3.13.0-30.55 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: marcel 2611 F pulseaudio /dev/snd/controlC0: marcel 2611 F pulseaudio CurrentDesktop: Unity Date: Mon Jul 28 22:20:19 2014 HibernationDevice: RESUME=UUID=01981495-0235-4fdf-b7c6-c6191e986cec InstallationDate: Installed on 2014-01-23 (186 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Dell Inc. XPS13 9333 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=9d324637-b4a0-4800-a447-d17e20b708f3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-30-generic N/A linux-backports-modules-3.13.0-30-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-17 (101 days ago) dmi.bios.date: 12/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: marcel 2644 F pulseaudio /dev/snd/controlC0: marcel 2644 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=01981495-0235-4fdf-b7c6-c6191e986cec InstallationDate: Installed on 2014-01-23 (187 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Dell Inc. XPS13 9333 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=9d324637-b4a0-4800-a447-d17e20b708f3 ro quiet splash 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: Upgraded to trusty on 2014-04-17 (103 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 12/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1
[Kernel-packages] [Bug 1359507] Re: ahci_xgene: Fix the link down in first attempt for the APM X-Gene SoC AHCI SATA host controller driver
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1359507 Title: ahci_xgene: Fix the link down in first attempt for the APM X-Gene SoC AHCI SATA host controller driver Status in “linux” package in Ubuntu: In Progress Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: In Progress Bug description: [IMPACT] The link down issue in first attempt happens due to 2 H/W errata below: 1. Due to HW errata, during speed negotiation, sometimes controller is not able to detect ALIGN at GEN3(6Gbps) within 54.6us results in a timeout. This issue can be recovered by issuing a COMRESET again. 2. Due to HW errata, although ALIGH detection is successfull, due to 8b/10b and disparity BERR, sometimes the signature from the drive is not received successfully by the Host controller. Due to this the communication with the host and drive is not established due to locking of CDR(clock and data recovery) circuit. This issue can be recovered by issuing a COMRESET again. This patch fixes the above issues by retrying the COMRESET with a maximum attempts of 3. [TEST CASE] Repeatedly reboot the system. [Regression Potential] Fix specific to the xgene ahci driver hardreset function. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359507/+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 1297522] Re: Since Trusty /proc/diskstats shows weird values
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-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/1297522
Title:
Since Trusty /proc/diskstats shows weird values
Status in “linux” package in Ubuntu:
Fix Released
Status in “linux” source package in Trusty:
Fix Committed
Bug description:
SRU Justification:
Impact: Tools that rely on diskstats may report incorrect data in
certain conditions. In particular diskstats in a VM may report
incorrect statistics.
Fix: 0fec08b4ecfc36fd8a64432343b2964fb86d2675 ( in 3.14-rc1 )
Testcase:
- Install a VM with the affected kernel
- Run cat /proc/diskstats | awk '$3=="vda" { print $7/$4, $11/$8 }'
- If the two values are much larger compared to the v3.14-rc1 kernel in the
same VM, we have failed. For example in a failing case I see: "132.44 5458.34";
in a passing case I see: "0.19334 5.90476".
--
After upgrading some virtual machines (KVM) to Trusty I noticed really
high I/O wait times, e.g. Munin graphs now show up to 200 seconds(!)
read I/O wait time. See attached image. Of course real latency isn't
higher than before, it's only /proc/diskstats that shows totally wrong
numbers...
$ cat /proc/diskstats | awk '$3=="vda" { print $7/$4, $11/$8 }'
1375.44 13825.1
From the documentation for /proc/diskstats field 4 is total number of
reads completed, field 7 is the total time spent reading in
milliseconds, and fields 8 and 11 are the same for writes. So above
numbers are the average read and write latency in milliseconds.
Same weird numbers with iowait. Note the column "await" (average time
in milliseconds for I/O requests):
$ iostat -dx 1 60
Linux 3.13.0-19-generic (munin) 03/25/14_x86_64_(2 CPU)
Device: rrqm/s wrqm/s r/s w/srkB/swkB/s avgrq-sz
avgqu-sz await r_await w_await svctm %util
vda 2.3016.75 72.45 24.52 572.79 778.3727.87
1.57 620.00 450.20 1121.83 1.71 16.54
Device: rrqm/s wrqm/s r/s w/srkB/swkB/s avgrq-sz
avgqu-sz await r_await w_await svctm %util
vda 0.00 0.000.000.00 0.00 0.00 0.00
0.000.000.000.00 0.00 0.00
Device: rrqm/s wrqm/s r/s w/srkB/swkB/s avgrq-sz
avgqu-sz await r_await w_await svctm %util
vda 0.00 0.000.000.00 0.00 0.00 0.00
0.000.000.000.00 0.00 0.00
Device: rrqm/s wrqm/s r/s w/srkB/swkB/s avgrq-sz
avgqu-sz await r_await w_await svctm %util
vda 0.0052.000.00 25.00 0.00 308.0024.64
0.30 27813.920.00 27813.92 0.48 1.20
I upgraded the host system to Trusty too, however there
/proc/diskstats output is normal as before.
$ uname -r
3.13.0-19-generic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1297522/+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 1359489] Re: Fix the csr-mask for APM X-Gene SoC AHCI SATA PHY clock DTS node
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1359489 Title: Fix the csr-mask for APM X-Gene SoC AHCI SATA PHY clock DTS node Status in “linux” package in Ubuntu: In Progress Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: In Progress Bug description: [IMPACT] The value of the csr-mask of the SATA PHY clock DTS node has a wrong value resulting a kernel panic as the clock/reset is not proper for the PHY of the SATA host controller 1. This patch fixes the correct csr-mask value of the SATA PHY clock DTS node for the SATA Host controller 1. [TEST CASE] Attempt to boot from a disk attached to SATA Host controller 1. [Regression Potential] As the 'ok' is the default status of a device tree node, this patch removes the status of the PHY clock node of SATA Host Controller 1. The status of the clock node is handled from the firmware based on the controller enabled/disabled by the user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359489/+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 1359501] Re: ahci_xgene: Skip the PHY and clock initialization if already configured by the firmware
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1359501 Title: ahci_xgene: Skip the PHY and clock initialization if already configured by the firmware Status in “linux” package in Ubuntu: In Progress Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: In Progress Bug description: [IMPACT] Some disk types will never be seen after boot, while others can disappear after a reboot. This patch implements the feature to skip the PHY and clock initialization if it is already configured by the firmware. [TEST CASE] Repeatedly reboot the system. [Regression Potential] Only affects the the xgene ahci driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359501/+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 1283101] Re: CVE-2014-0069: CIFS -- add hardening patch
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-trusty -- 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/1283101 Title: CVE-2014-0069: CIFS -- add hardening patch Status in “linux” package in Ubuntu: Fix Released Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid 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-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Won't Fix Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Won't Fix 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-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Confirmed Status in “linux-armadaxp” source package in Precise: Confirmed Status in “linux-ec2” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Won't Fix Status in “linux-lts-raring” source package in Precise: Won't Fix Status in “linux-lts-saucy” source package in Precise: Won't Fix Status in “linux-ti-omap4” source package in Precise: Confirmed Status in “linux” source package in Quantal: Won't Fix Status in “linux-armadaxp” source package in Quantal: Won't Fix Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Won't Fix Status in “linux” source package in Saucy: Won't Fix Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Won't Fix Status in “linux” source package in Trusty: Fix Committed Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid 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-ti-omap4” source package in Trusty: Invalid Bug description: This CVE was fixed under 5d81de8e8667da7135d3a32a964087c0faf5483f but there is a second fix which will make this much safer going forward against other bugs: http://article.gmane.org/gmane.linux.kernel.cifs/9402 Makes sense to put this into any release which needs it. # As applied to linus' tree Break-fix: - a26054d184763969a411e3939fe243516715ff59 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1283101/+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 1358498] Re: ahci-xgene falsely advertises NCQ support
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1358498 Title: ahci-xgene falsely advertises NCQ support Status in “linux” package in Ubuntu: In Progress Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: In Progress Bug description: [IMPACT] ahci-xgene doesn't support NCQ but it sets this flag. This causes SATA failures that surface as a filesystem being remounted read-only due to errors when using a disk that supports NCQ. [TEST CASE] Do a network boot install on an X-Gene system with an SSD drive that supports NCQ. The install will fail and dmesg will show the filesystem being remounted read-only. [Regression Potential] Minimal; we're turning off a feature that is known broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358498/+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 1358855] Re: tools/testing/selftests/ptrace fails on ppc64
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1358855 Title: tools/testing/selftests/ptrace fails on ppc64 Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Fix Released Bug description: Compilation of linux/tools/testing/selftests/ptrace/peeksiginfo.c fails becasue the variable PAGE_SIZE is not defined. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358855/+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 1354234] Re: 14.04: PANIC with "dcache shrink list corruption?" problem
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1354234 Title: 14.04: PANIC with "dcache shrink list corruption?" problem Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Fix Released Bug description: Hello, 14.04 kernel linux_3.13.0-32.57 panicked because of "dcache shrink list corruption?" problem. Please see followings: - details at https://lkml.org/lkml/2014/5/2/555. - argument at https://lkml.org/lkml/2014/4/29/402 - patch set at https://lkml.org/lkml/2014/5/4/7 One of 9 patches has been applied to linux_3.13.0-32.57 already. Could you apply other 8 patches to the next 14.04 kernel ? We will need the kernel at the beginning of August badly. If we will not be able to get it, we will not be able to start tests before service in. Could you release it as soon as possible ? We applied other 8 patches to linux_3.13.0-32.57 and now the panic does not occur. Public Bug URL: https://lkml.org/lkml/2014/5/2/555 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1354234/+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 1357295] Re: bcache_writebac blocks and goes silent on trusty kernel 3.13.0-24-generic #47-Ubuntu
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1357295 Title: bcache_writebac blocks and goes silent on trusty kernel 3.13.0-24-generic #47-Ubuntu Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Fix Released Bug description: We regularly use bcache to use SSDs as an extra block cache layer for performance on large working sets (archive mirrors, large databases, etc). Until now we have had good success with bcache on precise LTS with HWE kernels up to Saucy's. Unfortunately when we mount a bcache-backed volume on a Trusty server, it immediately loses contact with bcache_writebac: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 501 root 20 0 0 0 0 D 0.0 0.0 0:00.00 bcache_writebac kern.log shows it losing its mind pretty much immediately on startup: Aug 12 02:22:15 somehostname kernel: [ 6483.477618] md: bind Aug 12 02:22:15 somehostname kernel: [ 6483.478599] md: bind Aug 12 02:22:15 somehostname kernel: [ 6483.482016] md/raid0:md0: md_size is 781443072 sectors. Aug 12 02:22:15 somehostname kernel: [ 6483.482024] md: RAID0 configuration for md0 - 1 zone Aug 12 02:22:15 somehostname kernel: [ 6483.482026] md: zone0=[sdc/sdd] Aug 12 02:22:15 somehostname kernel: [ 6483.482033] zone-offset= 0KB, device-offset= 0KB, size= 390721536KB Aug 12 02:22:15 somehostname kernel: [ 6483.482036] Aug 12 02:22:15 somehostname kernel: [ 6483.482055] md0: detected capacity change from 0 to 400098852864 Aug 12 02:22:15 somehostname kernel: [ 6483.487644] md0: unknown partition table Aug 12 02:26:55 somehostname kernel: [ 6763.657249] bio: create slab at 2 Aug 12 02:26:55 somehostname kernel: [ 6763.658018] bcache: run_cache_set() invalidating existing data Aug 12 02:26:55 somehostname kernel: [ 6763.695447] bcache: register_cache() registered cache device md0 Aug 12 02:26:55 somehostname kernel: [ 6763.696262] bcache: register_bdev() registered backing device sdb Aug 12 02:26:55 somehostname kernel: [ 6763.697833] bcache: bch_cached_dev_attach() Caching sdb as bcache0 on set 13dcf71e-73ea-49f7-8cd6-fb8182c3cc17 Aug 12 02:27:24 somehostname kernel: [ 6793.114287] EXT4-fs (bcache0): mounted filesystem with ordered data mode. Opts: (null) Aug 12 02:30:16 somehostname kernel: [ 6964.514425] INFO: task bcache_writebac:29721 blocked for more than 120 seconds. Aug 12 02:30:16 somehostname kernel: [ 6964.608861] Not tainted 3.13.0-24-generic #47-Ubuntu Aug 12 02:30:16 somehostname kernel: [ 6964.679403] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Aug 12 02:30:16 somehostname kernel: [ 6964.779270] bcache_writebac D 8817dfb34440 0 29721 2 0x Aug 12 02:30:16 somehostname kernel: [ 6964.779278] 882fafe57eb8 0002 882fb100afe0 882fafe57fd8 Aug 12 02:30:16 somehostname kernel: [ 6964.779286] 00014440 00014440 882fb100afe0 882fb7bcac80 Aug 12 02:30:16 somehostname kernel: [ 6964.779293] 882fb11c a03f5840 Aug 12 02:30:16 somehostname kernel: [ 6964.779301] Call Trace: Aug 12 02:30:16 somehostname kernel: [ 6964.779335] [] ? read_dirty+0x400/0x400 [bcache] Aug 12 02:30:16 somehostname kernel: [ 6964.779346] [] schedule+0x29/0x70 Aug 12 02:30:16 somehostname kernel: [ 6964.779356] [] kthread+0xad/0xf0 Aug 12 02:30:16 somehostname kernel: [ 6964.779368] [] ? kthread_create_on_node+0x1d0/0x1d0 Aug 12 02:30:16 somehostname kernel: [ 6964.779379] [] ret_from_fork+0x7c/0xb0 Aug 12 02:30:16 somehostname kernel: [ 6964.779385] [] ? kthread_create_on_node+0x1d0/0x1d0 Aug 12 02:32:16 somehostname kernel: [ 7084.828482] INFO: task bcache_writebac:29721 blocked for more than 120 seconds. Aug 12 02:32:16 somehostname kernel: [ 7084.922987] Not tainted 3.13.0-24-generic #47-Ubuntu Aug 12 02:32:16 somehostname kernel: [ 7084.993239] "echo 0 > /proc/sys/kernel/hung_task_ti
[Kernel-packages] [Bug 1358162] Re: skb_get_rxhash prematurely renamed to skb_get_hash
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1358162 Title: skb_get_rxhash prematurely renamed to skb_get_hash Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Fix Released Bug description: "3958afa1b272 net: Change skb_get_rxhash to skb_get_hash" is included in the Trusty kernel like so: commit df4530d690a14dd4b72e4eadc8fe845e3c5ba12c Author: Tom Herbert Date: Sun Dec 15 22:12:06 2013 -0800 net: Change skb_get_rxhash to skb_get_hash BugLink: http://bugs.launchpad.net/bugs/1328037 Changing name of function as part of making the hash in skbuff to be generic property, not just for receive path. Signed-off-by: Tom Herbert Signed-off-by: David S. Miller (cherry picked from commit 3958afa1b272eb07109fd31549e69193b4d7c364) Signed-off-by: Tim Gardner Acked-by: Brad Figg The referenced bug is about pulling in some up-to-date drivers. Kernel module authors who need to work with many different kernel versions deal with renames like this by using the KERNEL_VERSION macros to determine which wrappers/stubs/whatever to include in a particular build. However, because of this above change, which wasn't included in upstream kernels until 3.14 (while Trusty is 3.13(+extra magic)) this won't work. I propose you add a compatibility macro. Luckily, it's a straight rename, so this should be simple enough. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358162/+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 1328088] Re: Kernel network namespace performance regression during rcu development on kernels above 3.8
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-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/1328088
Title:
Kernel network namespace performance regression during rcu development
on kernels above 3.8
Status in The Linux Kernel:
In Progress
Status in “linux” package in Ubuntu:
Fix Released
Status in “linux” source package in Trusty:
Fix Committed
Status in “linux” source package in Utopic:
Fix Released
Bug description:
SRU Justification:
Impact: network namespace creation has performance regression since v3.5.
Fix: my analysis, lklm discussion, upstream patch
Testcase:
http://people.canonical.com/~inaddy/lp1328088/make_fake_routers.sh
http://people.canonical.com/~inaddy/lp1328088/parse.py
http://people.canonical.com/~inaddy/lp1328088/charts/250.html
http://people.canonical.com/~inaddy/lp1328088/charts/250-tag.html
Running make_fake_routers.sh 4000 and using parse.py you can check if
"fake routers" are being created in a good rate /sec (and you can
compare with all generated charts).
Original Description:
Please, follow this in:
http://people.canonical.com/~inaddy/lp1328088/. Same description on
daily-basis updated text.
--
It was brought to my attention that network namespace creation scalability
was affected during kernel development.
The following script was used for all the tests and charts generation:
http://people.canonical.com/~inaddy/lp1328088/make_fake_routers.sh
http://people.canonical.com/~inaddy/lp1328088/parse.py
I measured how many "fake routers" (above script) could be added per
second from 0 to 4000 created routers mark. Using this script and a
git bisect on kernel tree I was led to one specific commit causing
regression: #911af50 "rcu: Provide compile-time control for no-CBs
CPUs". Even Though this change was experimental at that point, it
introduced a performance scalability regression (explained below) that
still last and seems to be the default option for distributions
nowadays.
RCU related code looked like to be responsible for the problem. With
that, every commit from tag v3.8..master that changed any of this
files: "kernel/rcutree.c kernel/rcutree.h kernel/rcutree_plugin.h
include/trace/events/rcu.h include/linux/rcupdate.h" was tested. The
idea was to check performance regression during rcu development. In
the worst case, the regression not being related to rcu, I would still
have data to interpret the performance/scalability regression.
All text below this refer to 2 groups of charts, generated during the
study:
1) Kernel git tags from 3.8 to 3.14.
http://people.canonical.com/~inaddy/lp1328088/charts/250-tag.html
2) Kernel git commits for rcu development (111 commits).
http://people.canonical.com/~inaddy/lp1328088/charts/250.html
Since there was difference in results depending on how many cpus or
how the no-cb cpus were configured, 3 kernel config options were used
on every measure:
- CONFIG_RCU_NOCB_CPU (disabled): nocbno
- CONFIG_RCU_NOCB_CPU_ALL (enabled): nocball
- CONFIG_RCU_NOCB_CPU_NONE (enabled): nocbnone
Obs: For 1 cpu cases: nocbno, nocbnone, nocball behaves the same since
w/ only 1 cpu there is no no-cb cpu
After charts being generated it was clear that NOCB_CPU_ALL (4 cpus)
affected the "fake routers" creation process performance and this
regression continues up to upstream version. It was also clear that,
after commit #911af50, having more than 1 cpu does not improve
performance/scalability for netns, makes it worse.
#911af50
...
+#ifdef CONFIG_RCU_NOCB_CPU_ALL
+ pr_info("\tExperimental no-CBs for all CPUs\n");
+ cpumask_setall(rcu_nocb_mask);
+#endif /* #ifdef CONFIG_RCU_NOCB_CPU_ALL */
...
Comparing standing out points (see charts):
#81e5949 - good
#911af50 - bad
I was able to see that, from the script above, the following lines
causes major impact on netns scalability/performance:
1) ip netns add -> huge performance regression:
1 cpu: no regression
4 cpu: regression for NOCB_CPU_ALL
obs: regression from 250 netns/sec to 50 netns/sec
on 500 netns already created mark
2) ip netns exec -> some performance regression
1 cpu: no regression
4 cpu: regression for NOCB_CPU_ALL
obs: regression from 40 netns (+1 exec per
[Kernel-packages] [Bug 1357014] Re: Add THP fixes in 14.10 kernel
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1357014 Title: Add THP fixes in 14.10 kernel Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Fix Released Bug description: Hi Canonical, We would like to include 8 patches regarding Transparent Huge Page for powerpc. The patches are already upstream on Ben powerpc-next tree and should be sent to Linus' tree today, which mean that they are expected to make 3.17. Here are the patches 9e813308a5c18c58f9ccae1ec72ed4e14eaf9025 powerpc/thp: Add tracepoints to track hugepage invalidate 85c1fafd7262e68ad821ee1808686b1392b1167d powerpc/mm: Use read barrier when creating real_pte 7e467245bf5226db34c4b12d3cbacfa2f7a15a8b powerpc/thp: Use ACCESS_ONCE when loading pmdp 969b7b208f7408712a3526856e4ae60ad13f6928 powerpc/thp: Invalidate with vpn in loop fc0479557572375100ef16c71170b29a98e0d69a powerpc/thp: Handle combo pages in invalidate 629149fae478f0ac6bf705a535708b192e9c6b59 powerpc/thp: Invalidate old 64K based hash page mapping before insert of 4k pte fa1f8ae80f8bb996594167ff4750a0b0a5a5bb5d powerpc/thp: Don't recompute vsid and ssize in loop on invalidate b0aa44a3dfae3d8f45bd1264349aa87f87b7774f powerpc/thp: Add write barrier after updating the valid bit I am also adding the patches here for reference. Thank you, Breno To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1357014/+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 1353021] Re: USB HIDRAW Feature Report Implementation for HID devices not working correctly in Ubuntu 14.04
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1353021 Title: USB HIDRAW Feature Report Implementation for HID devices not working correctly in Ubuntu 14.04 Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Fix Released Bug description: With the release of Ubuntu 14.04 I've been investigating an issue with a software library I maintain to talk to USB based HID signature pads. I believe I've narrowed the issue down to the HIDRAW implementation released with Ubuntu 14.04. Essentially what seems to be failing is the ioctl to get feature reports (HIDIOCGFEATURE). Any attempt to get a feature report results in a failure with a ENODEV error code. The devices I'm testing with are USB signature pads (http://www.scriptel.com). These signature pads use HID feature reports to communicate capabilities and to set up the device. I can provide further information along with USB/HID descriptors if it would be helpful. I have been testing with Ubuntu 14.04 Desktop (x64) with kernel version: Linux 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux This kernel exhibits the problematic behavior, but when testing with Ubuntu 13.10 Desktop (x64): Linux 3.11.0-23-generic #40-Ubuntu SMP Wed Jun 4 21:05:23 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux The 13.10 kernel's version of HIDRAW seems to work correctly. I've also tested with the vanilla kernel: Linux 3.13.1-hidtest #1 SMP Tue Aug 5 09:14:28 EDT 2014 x86_64 x86_64 x86_64 GNU/Linux The vanilla kernel appears to work correctly as well. Kernel source used was downloaded from: https://www.kernel.org/pub/linux/kernel/v3.x/linux-3.13.1.tar.xz The configuration file used was from config-3.13.0-32-generic provided in linux-image-3.13.0-32-generic I believe the breaking change was made as part of commit aa6c390c4d59c9ff4fffd887e15783b2b793951b as part of ubuntu/ubuntu- trusty.git. I have attached a simple C program to demonstrate the problem. You'll need a USB HID device with known feature reports. Please let me know if I can provide any additional information or be of any assistance. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 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: mpowers2863 F pulseaudio CurrentDesktop: Unity Date: Tue Aug 5 13:51:39 2014 HibernationDevice: RESUME=UUID=3a5a866c-6086-47d6-8080-70715896a719 InstallationDate: Installed on 2014-04-17 (109 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=9b49575f-fb86-45d7-af5e-b3fde82f91ac ro quiet splash 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/07/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1762II1.50U dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: CZ-17 dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1762II1.50U:bd12/07/2012:svn:pnCZ-17:pvrREV1.0:rvn:rnCZ-17:rvrREV1.0:cvnToBeFilledByO.E.M.:ct10:cvrTobefilledbyO.E.M.: dmi.product.name: CZ-17 dmi.product.version: REV:1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1353021/+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 1329434] Re: nested KVM fails on intel hardware - KVM: entry failed, hardware error 0x0
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1329434 Title: nested KVM fails on intel hardware - KVM: entry failed, hardware error 0x0 Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Bug description: [Impact] Using nested KVM on some hypervisors doesn't work. [Test Case] A script to make this easier is posted here: https://gist.github.com/arges/9d21c6da03a8c10d3980 1) enable nested KVM: sudo modprobe -r kvm_intel sudo modprobe kvm_intel nested=1 cat /sys/module/kvm_intel/parameters/nested # should say Y 2) generate an L1 guest and then generate an L2 guest inside the L1 guest - ensure L1 has enough memory to boot L2 - if using libvirt you may need to edit the default bridge to use a different subnet than the L1 guest 3) boot the L2 guest 4) L2 guest should boot [Fix] These three upstream patches needed to be backported to 3.13: * 533558bcb69ef28aff81b6ae9acda8943575319f - This provides necessary code changes to make backporting easier. However vmx_leave_nested function was not yet added, so that function modification was dropped. * b6b8a1451fc40412c57d10c94b62e22acab28f94 - This patch is necessary in order to ensure that the L1 guest doesn't crash with just 696dfd95 applied. I had to remove mpx mentions from the cherry-pick as that feature hasn't been added yet. * 696dfd95ba9838327a7013e5988ff3ba60dcc8c8 - This patch fixes the issue and was the result of the bisection. The APIC virtualization features need to be disabled as they cause L2 guests to not boot depending on the CPU. -- If the L2 guest doesn't boot you can see the log: sudo cat /var/log/libvirt/qemu/nested-L2.log KVM: entry failed, hardware error 0x0 EAX= EBX= ECX= EDX=0663 ESI= EDI= EBP= ESP= EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=00 66 89 d8 66 e8 02 f7 ff ff 66 83 c4 0c 66 5b 66 5e 66 c3 5b e0 00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 13 18:26 seq crw-rw 1 root audio 116, 33 Jun 13 18:26 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.2 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: DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: Intel Corporation S2600WTT Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=b5d11a1d-c48f-4abf-a622-d1efe52fe97c ro 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 1.127.2 RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-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 libvirtd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 05/06/2014 dmi.bios.vendor: Intel Corporation dmi.bios.version: GRNDSDP1.86B.0030.R03.1405061547 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: S2600WTT dmi.board.vendor: Intel Corporation dmi.board.version: H30334-201 dmi.ch
[Kernel-packages] [Bug 1357527] Re: [Trusty] support for X-Gene PMU in perf
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1357527 Title: [Trusty] support for X-Gene PMU in perf Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Fix Released Bug description: Trusty doesn't currently support the X-Gene PMU, which prevents perf from making use of hardware counters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1357527/+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 1358949] Re: arm64 iperf performance suboptimal
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-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/1358949
Title:
arm64 iperf performance suboptimal
Status in “linux” package in Ubuntu:
Fix Released
Status in “linux” source package in Trusty:
Fix Committed
Status in “linux” source package in Utopic:
Fix Released
Bug description:
[Impact]
The copy_{to,from}_user implementations in the Ubuntu kernel are suboptimal.
Optimized implementations have been submitted upstream and have shown a
significant improvement in network performance.
Iperf performance increase:
-l (size) 1 core result
Optimized 64B 44-51Mb/s
1500B 4.9Gb/s
3B 16.2Gb/s
Original64B 34-50.7Mb/s
1500B 4.7Gb/s
3B 14.5Gb/s
[Test Case]
Generate traffic from one node to another using iperf (see above for config).
[Regression Risk]
These functions are obviously used heavily throughout the kernel, so a defect
here could have significant impact. This risk is mitigated by using an
implementation heavily based on the linaro string libraries (which are used in
other places already, e.g. glibc), and through active testing of this patch on
real hardware using a trusty-kernel base.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358949/+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 1353105] Re: bnx2x crashes on bxn2x_tpa_start
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1353105 Title: bnx2x crashes on bxn2x_tpa_start Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Fix Released Bug description: [Impact] Random crashes when using the bnx2x driver on power 8 [Test Case] heavy use of the bnx2x driver on power 8 [Regression Potential] introduces a simple memory barrier and is therefore very low risk, any such risk would normally affect performanc e not function. === ---Problem Description--- bnx2x may cause crashes or stop working because of a missing memory barrier. Messages like the following appear on the log: bnx2x: [bnx2x_tpa_start:392(eth7)]start of bin not in stop [0] ---uname output--- Linux ubuntu 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:50:31 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux ---Additional Hardware Info--- 0001:00:03.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM57800 1/10 Gigabit Ethernet (rev 10) 0001:00:03.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM57800 1/10 Gigabit Ethernet (rev 10) 0001:00:03.2 Ethernet controller: Broadcom Corporation NetXtreme II BCM57800 1/10 Gigabit Ethernet (rev 10) 0001:00:03.3 Ethernet controller: Broadcom Corporation NetXtreme II BCM57800 1/10 Gigabit Ethernet (rev 10) Machine Type = model : IBM pSeries (emulated by qemu) ---Steps to Reproduce--- Send lots of traffic on a busy workload. Fix for reported issue upstream commit 9aaae044abe95de182d09004cc3fa181bf22e6e0 Fix for EEH related issue upstream commit 0c0e63410a393aae4b615849625f539db775d586 We would like to get those applied to both Ubuntu 14.04 updates and Ubuntu 14.10, please. Cascardo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1353105/+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 1317697] Re: hyper-v: Unable to dump core for Ubuntu 14.04 virtual machines.
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1317697 Title: hyper-v: Unable to dump core for Ubuntu 14.04 virtual machines. Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Fix Released Bug description: Hi, We need to include two new patches: http://git.kernel.org/cgit/linux/kernel/git/next/linux- next.git/commit/arch/x86/kernel/cpu/mshyperv.c?id=e179f6914152eca9b338e7d8445684062f560c55 http://git.kernel.org/cgit/linux/kernel/git/next/linux- next.git/commit/drivers/hv/connection.c?id=03367ef5ea811475187a0732aada068919e14d61 Without these patches we are unable to dump core for Ubuntu 14.04 virtual machines. Please include. Thanks, Abhishek To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1317697/+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 1360140] Re: trusty still uses APM's out-of-tree xgene-enet patches
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1360140 Title: trusty still uses APM's out-of-tree xgene-enet patches Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Fix Released Bug description: Now all APM's xgene-enet patches are merged to linus tree already, so it is time to replace these out-of-tree patches with upstreamed xgene-enet commits. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1360140/+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 1359670] Re: Unsigned oot modules are wrongly tainted and trace events disabled
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1359670 Title: Unsigned oot modules are wrongly tainted and trace events disabled Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Fix Released Bug description: [Impact] Developers are unable to unable to use kernel tracing functions on kernel modules they have themselves compiled. This makes Ubuntu a poor platform for module developement and debugging. [Test Case] Build an OOT or modified version of a module, insert it and notice that tracing becomes disabled. Apply updated kernel and confirm the same does not occur. [Regression Potential] This only changes the taint infrastructure to introduce a single new flag. Should be very low risk. === The issue is explained in detail at http://lwn.net/Articles/588799/ I am trying to load a backported drm module using dkms. It is not signed so is listed as tainted and trace points are disabled. As explained in the above article this is because the TAINT_FORCED MODULE flag is incorrectly set for unsigned modules. The final patch to fix this and add a TAINT_UNSIGNED_MODULE that does not disable trace points can be found at http://lwn.net/Articles/588803/ (fixed in 3.15) Please consider shipping this patch. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-34-generic 3.13.0-34.60 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: badger 2013 F pulseaudio CurrentDesktop: Unity Date: Thu Aug 21 11:28:15 2014 HibernationDevice: RESUME=UUID=21f8f6b4-495d-4bc6-8dec-1f78435d4b95 InstallationDate: Installed on 2014-06-30 (51 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 0301CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic root=UUID=d56caf05-a203-436f-8497-b8a37294fe8a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-34-generic N/A linux-backports-modules-3.13.0-34-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/14/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 80ET42WW (1.19 ) dmi.board.name: 0301CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr80ET42WW(1.19):bd10/14/2010:svnLENOVO:pn0301CTO:pvrThinkPadEdge:rvnLENOVO:rn0301CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 0301CTO dmi.product.version: ThinkPad Edge dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359670/+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 1365869] Re: After upgrade to 3.13.0-35.62, rpc.gssd complains about missing /run/rpc_pipefs/gssd/clntXX/info
I've built, installed and tested the kernel described in comment #4. It does what I expected it to do: * file /run/rpc_pipefs/gssd/clntXX/info now exists; * rpc.gssd no longer complains. No adverse side effects so far. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1365869 Title: After upgrade to 3.13.0-35.62, rpc.gssd complains about missing /run/rpc_pipefs/gssd/clntXX/info Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: In Progress Bug description: The following changes in 3.13.0-35.62: * sunrpc: create a new dummy pipe for gssd to hold open - LP: #1327563 * sunrpc: replace sunrpc_net->gssd_running flag with a more reliable check - LP: #1327563 * nfs: check if gssd is running before attempting to use krb5i auth in SETCLIENTID call - LP: #1327563 are causing rpc.gssd to fill syslog with messages of the form ERROR: can't open /run/rpc_pipefs/gssd/clntXX/info: No such file or directory The problem was discussed last December in https://bugzilla.redhat.com/show_bug.cgi?id=1037793 where the resolution was to include the following three patches: http://marc.info/?l=linux-nfs&m=138624689302466&w=2 http://marc.info/?l=linux-nfs&m=138624684502447&w=2 http://marc.info/?l=linux-nfs&m=138624684502447&w=2 These patches are already in the upstream kernel (since 3.14). I suggest cherry-picking them for 3.13. Commit hashes from the 3.14 branch: 3396f92f8be606ea485b0a82d4e7749a448b013b e2f0c83a9de331d9352185ca3642616c13127539 23e66ba97127ff3b064d4c6c5138aa34eafc492f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1365869/+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 1364092] Re: linux: 2.6.32-66.132 -proposed tracker
** Description changed: This bug is for tracking the 2.6.32-66.132 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, 01. September 2014 17:01 UTC kernel-stable-phase:PPA Testing kernel-stable-phase-changed:Tuesday, 02. September 2014 01:04 UTC kernel-stable-Prepare-package-end:Tuesday, 02. September 2014 01:04 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 02. September 2014 01:04 UTC ppa-package-testing-start:Tuesday, 02. September 2014 01:04 UTC + kernel-stable-Promote-to-proposed-end:Monday, 08. September 2014 20:03 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1364092 Title: linux: 2.6.32-66.132 -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-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: 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 Lucid: New Bug description: This bug is for tracking the 2.6.32-66.132 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, 01. September 2014 17:01 UTC kernel-stable-phase:PPA Testing kernel-stable-phase-changed:Tuesday, 02. September 2014 01:04 UTC kernel-stable-Prepare-package-end:Tuesday, 02. September 2014 01:04 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 02. September 2014 01:04 UTC ppa-package-testing-start:Tuesday, 02. September 2014 01:04 UTC kernel-stable-Promote-to-proposed-end:Monday, 08. September 2014 20:03 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1364092/+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 1364092] Re: linux: 2.6.32-66.132 -proposed tracker
Copied to -proposed and overrides adjusted. ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Adam Conrad (adconrad) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1364092 Title: linux: 2.6.32-66.132 -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-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: 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 Lucid: New Bug description: This bug is for tracking the 2.6.32-66.132 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, 01. September 2014 17:01 UTC kernel-stable-phase:PPA Testing kernel-stable-phase-changed:Tuesday, 02. September 2014 01:04 UTC kernel-stable-Prepare-package-end:Tuesday, 02. September 2014 01:04 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 02. September 2014 01:04 UTC ppa-package-testing-start:Tuesday, 02. September 2014 01:04 UTC kernel-stable-Promote-to-proposed-end:Monday, 08. September 2014 20:03 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1364092/+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 1362199] Re: [FFe] apparmor abstract, anonymous and netlink socket mediation
** Description changed: Background: kernel and apparmor userspace updates to support abstract, anonymous and fine-grained netlink socket mediation. These packages are listed in one bug because they are related, but the FFes may be granted and the uploads may happen at different times. + + = apparmor userspace = + Summary: + This feature freeze exception is requested for abstract, anonymous and fine-grained netlink socket for apparmor userspace. When used with a compatible kernel, 'unix' and 'network netlink' rules are supported. When used without a compatible apparmor userspace (eg, on a trusty system with an utopic backport kernel), abstract, anonymous and fine-grained netlink socket mediation is not enforced (ie, you can use this userspace with an old kernel without any issues). + + Testing: + * 14.10 system with previous kernel lacking abstract, anonymous and fine-grained netlink socket mediation (non-Touch): + * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: DONE (exploratory manual testing, lxc, libvirt, etc) + * 14.10 system kernel capable of supporting abstract, anonymous and fine-grained netlink socket mediation (non-Touch): + * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: INPROGRESS (includes test-apparmor.py, exploratory manual testing, lxc, libvirt, etc) + * Verify everything in https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/AppArmorProfiles: DONE (except juju since it doesn't have policy itself) + + Justification: + This feature is required to support comprehensive application confinement on Ubuntu Touch. This feature adds a security benefit to libvirt's qemu guest isolation which is fundamental to Ubuntu on Server/Cloud. This feature also adds a welcome improvement to administrators wishing to further protect their systems. + + Extra information: + While the apparmor userspace and kernel changes to support abstract, anonymous and fine-grained netlink socket can happen at different times, the apparmor userspace upload must correspond with uploads for packages that ship AppArmor policy that require updates (eg, libvirt, lxc, etc). The packages outlined in https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/AppArmorProfiles have been tested to either work without modification to the policy or updated and tested to work with updated policy. Common rules will be added to the apparmor base abstraction such that most packages shipping apparmor policy will not require updating. These updates will be prepared, tested and published en masse via a silo ppa. + = linux = Summary: This feature freeze exception is requested for abstract, anonymous and fine-grained netlink socket via apparmor in the kernel. When used with a compatible apparmor userspace, 'unix' and 'network netlink' rules are supported. When used without a compatible apparmor userspace (eg, on a trusty system with an utopic backport kernel), abstract, anonymous and fine-grained netlink socket mediation is not enforced (ie, you can use this kernel with an old userspace without any issues). Testing: * 14.04 system with backported kernel: TODO - * test-apparmor.py: TODO (runs extensive tests (upstream and distro)) - * exploratory manual testing: TODO (networking, aa-enforce with firefox, firefox works, apparmor blocks access, etc) - * aa-status: TODO - * lxc: TODO (containers can be created, started, shutdown) - * libvirt: TODO (VMs started via openstack, and test-libvirt.py from QRT passes all tests) - * 14.10 system (non-Touch) with current apparmor userspace: TODO (relevant parts of https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor) - * test-apparmor.py: TODO (runs extensive tests (upstream and distro)) - * exploratory manual testing: TODO (networking, aa-enforce with firefox, firefox works, apparmor blocks access, etc) - * aa-status: TODO - * lxc: TODO (containers can be created, started, shutdown) - * libvirt: TODO (QRT/script/test-libvirt.py (though there are 3 failures unrelated to apparmor)) - * click-apparmor QRT touch image tests: TODO - * apparmor-easyprof-ubuntu QRT touch image tests: TODO - * 14.10 system (non-Touch) with updated apparmor userspace capable of supporting abstract, anonymous and fine-grained netlink socket: TODO (relevant parts of https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor) - * test-apparmor.py: TODO (runs extensive tests (upstream and distro)) - * exploratory manual testing: TODO (networking, aa-enforce with firefox, firefox works, apparmor blocks access, etc) - * aa-status: TODO - * lxc: TODO (containers can be created, started, shutdown) - * libvirt: TODO (QRT/script/test-libvirt.py (though there are 3 failures unrelated to apparmor)) - * click-apparmor QRT touch image tests: TODO - * apparmor-easyprof-ubuntu QRT touch image tests: TODO + * test-apparmor.py: TODO (runs extensive tests (upstream and distro)) + * exploratory manual testing: TODO (networking, aa-enforce with
[Kernel-packages] [Bug 1366868] Re: kvm: dompmwakeup fails if domain becomes pmsuspended
This is a qemu issue, not a kernel issue. This works with qemu 2.1, and not 2.0. Doing a bisect now. ** Also affects: qemu (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) ** Changed in: qemu (Ubuntu) Status: New => Fix Released ** No longer affects: linux (Ubuntu Trusty) ** Changed in: qemu (Ubuntu Trusty) Assignee: (unassigned) => Chris J Arges (arges) ** Changed in: qemu (Ubuntu Trusty) Status: New => In Progress ** Changed in: qemu (Ubuntu Trusty) 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/1366868 Title: kvm: dompmwakeup fails if domain becomes pmsuspended Status in “qemu” package in Ubuntu: Fix Released Status in “qemu” source package in Trusty: In Progress Bug description: [Impact] When using KVM, if one suspends the VM using actual power suspending code, the guest cannot resume using 'virsh dompmwakeup'. [Test Case] 1) Create a KVM VM and install Trusty using libvirt (although qemu alone will also exhibit this problem) 2) Inside the vm run (as root): 'echo mem > /sys/power/state' 3) From the hypervisor run 'virsh dompmwakeup ' 4) The domain should resume So far I've noticed that on Utopic this works fine, while on Trusty this fails; a bisect is needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1366868/+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 1316689] Re: Radeon VDPAU clients crash at vlVdpDecoderCreate with 1080p videos
This change is also in the 3.14.7 kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1316689 Title: Radeon VDPAU clients crash at vlVdpDecoderCreate with 1080p videos Status in The Linux Kernel: Fix Released Status in “linux” package in Ubuntu: Fix Released Bug description: I've enabled VDPAU support in flash player, and testing it with normal youtube videos (up to 720p) gives good results. However, once I switch to 1080p quality, the flash player crashes, and this happens at the mesa vdpau driver level because a Bus Error triggered by mesa since the CPU can't access properly to gpu VRAM. The same happens loading a 1080p video using VLC or MPlayer (see vlc backtrace http://paste.ubuntu.com/7405255/). Here's the problem as explained by Christian König: > It's not the VDPAU driver that's failing here, it's the kernel. > > When the kernel can't place a buffer into visible VRAM the buffer > should be moved into GART instead for CPU access. But instead we > just return a SIGBUS to the application effectively crashing it. I'm attaching the patch that fixes this problem, provided by Christian and tested successfully on ubuntu Trusty kernel. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.47 ProcVersionSignature: Ubuntu 3.13.0-24.47-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/controlC1: marco 2988 F pulseaudio /dev/snd/pcmC1D3p: marco 2988 F...m pulseaudio /dev/snd/controlC0: marco 2988 F pulseaudio CurrentDesktop: Unity Date: Tue May 6 18:27:23 2014 HibernationDevice: RESUME=UUID=534ddf57-b0f4-4367-ae56-d2878b2f614f InstallationDate: Installed on 2010-07-10 (1396 days ago) InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) MachineType: Acer Aspire 4820TG ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=4811a166-63ca-4702-8e63-0c357cc2e2f7 ro quiet splash radeon.audio=1 radeon.dpm=1 crashkernel=384M-2G:64M,2G-:128M crashkernel=384M-2G:64M,2G-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 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 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2012-10-10 (573 days ago) dmi.bios.date: 03/16/2011 dmi.bios.vendor: INSYDE dmi.bios.version: V1.25 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JM41_CP 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.25:bd03/16/2011:svnAcer:pnAspire4820TG:pvrV1.25:rvnAcer:rnJM41_CP:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire 4820TG dmi.product.version: V1.25 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1316689/+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 1316689] Re: Radeon VDPAU clients crash at vlVdpDecoderCreate with 1080p videos
This patch is in the 3.15 kernel. Ubuntu 14.10 "Utopic Unicorn" is based on the 3.16 kernel. ** Changed in: linux (Ubuntu) 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/1316689 Title: Radeon VDPAU clients crash at vlVdpDecoderCreate with 1080p videos Status in The Linux Kernel: Fix Released Status in “linux” package in Ubuntu: Fix Released Bug description: I've enabled VDPAU support in flash player, and testing it with normal youtube videos (up to 720p) gives good results. However, once I switch to 1080p quality, the flash player crashes, and this happens at the mesa vdpau driver level because a Bus Error triggered by mesa since the CPU can't access properly to gpu VRAM. The same happens loading a 1080p video using VLC or MPlayer (see vlc backtrace http://paste.ubuntu.com/7405255/). Here's the problem as explained by Christian König: > It's not the VDPAU driver that's failing here, it's the kernel. > > When the kernel can't place a buffer into visible VRAM the buffer > should be moved into GART instead for CPU access. But instead we > just return a SIGBUS to the application effectively crashing it. I'm attaching the patch that fixes this problem, provided by Christian and tested successfully on ubuntu Trusty kernel. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.47 ProcVersionSignature: Ubuntu 3.13.0-24.47-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/controlC1: marco 2988 F pulseaudio /dev/snd/pcmC1D3p: marco 2988 F...m pulseaudio /dev/snd/controlC0: marco 2988 F pulseaudio CurrentDesktop: Unity Date: Tue May 6 18:27:23 2014 HibernationDevice: RESUME=UUID=534ddf57-b0f4-4367-ae56-d2878b2f614f InstallationDate: Installed on 2010-07-10 (1396 days ago) InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) MachineType: Acer Aspire 4820TG ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=4811a166-63ca-4702-8e63-0c357cc2e2f7 ro quiet splash radeon.audio=1 radeon.dpm=1 crashkernel=384M-2G:64M,2G-:128M crashkernel=384M-2G:64M,2G-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 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 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2012-10-10 (573 days ago) dmi.bios.date: 03/16/2011 dmi.bios.vendor: INSYDE dmi.bios.version: V1.25 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JM41_CP 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.25:bd03/16/2011:svnAcer:pnAspire4820TG:pvrV1.25:rvnAcer:rnJM41_CP:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire 4820TG dmi.product.version: V1.25 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1316689/+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 1366951] [NEW] Bluetooth doesn't work on Gigabyte f2a88xn motherboard
Public bug reported: Bluetooth doesn't work on Gigabyte f2a88xn motherboard. Generally it's not detected. In order to have it detected, one needs to boot into Windows, then on Ubuntu again. Even when it's detected, it doesn't connect to the peripherals. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluez 4.101-0ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Sep 8 21:32:54 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-05 (3 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140723) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic.efi.signed root=UUID=f64a76a3-71a1-4ce4-9934-626170049b70 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/04/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XN-WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd09/04/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. syslog: ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages 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/1366951 Title: Bluetooth doesn't work on Gigabyte f2a88xn motherboard Status in “bluez” package in Ubuntu: New Bug description: Bluetooth doesn't work on Gigabyte f2a88xn motherboard. Generally it's not detected. In order to have it detected, one needs to boot into Windows, then on Ubuntu again. Even when it's detected, it doesn't connect to the peripherals. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluez 4.101-0ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Sep 8 21:32:54 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-05 (3 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140723) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic.efi.signed root=UUID=f64a76a3-71a1-4ce4-9934-626170049b70 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/04/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XN-WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd09/04/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. syslog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1366951/+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 1356558] Re: BUG: soft lockup - CPU stuck for 22s! [md3_raid1]
I built the next test kernel, up to the following commit: c6c1f325adc8a8e0cd06c6ad0ca232a6880a1783 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1356558 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results. Thanks in advance -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1356558 Title: BUG: soft lockup - CPU stuck for 22s! [md3_raid1] Status in “linux” package in Ubuntu: Confirmed Bug description: Hi, this bug appeared in Ubuntu 14.04, Ubuntu 12.04 didn't show this behavior. I've found a possible predecessor in bug #212684. Switching to a recent mainline kernel didn't fix this issue. Starting $ /usr/share/mdadm/checkarray /dev/md3 will repeat this behavior. /dev/md3 is a LVM PV: --- Physical volume --- PV Name /dev/md3 VG Name local_vg1 PV Size 1.36 TiB / not usable 2.25 MiB Allocatable yes PE Size 4.00 MiB Total PE 355619 Free PE 31011 Allocated PE 324608 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-33-generic 3.13.0-33.58 ProcVersionSignature: Ubuntu 3.13.0-33.58-generic 3.13.11.4 Uname: Linux 3.13.0-33-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-33-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.3 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Date: Wed Aug 13 21:42:12 2014 HibernationDevice: RESUME=UUID=c4a03c5e-f650-4ca8-9dab-f0c4ad12c901 InstallationDate: Installed on 2014-07-06 (37 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2) IwConfig: lono wireless extensions. em1 no wireless extensions. ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-33-generic root=UUID=9c2715cb-dd8a-4687-9537-009e1e4e83d8 ro nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-3.13.0-33-generic N/A linux-backports-modules-3.13.0-33-generic N/A linux-firmware 1.127.5 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2010 dmi.bios.vendor: Intel Corp. dmi.bios.version: JT94510H.86A.0045.2010.0519.1750 dmi.board.name: D945GSEJT dmi.board.vendor: Intel Corporation dmi.board.version: AAE57850-300 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrJT94510H.86A.0045.2010.0519.1750:bd05/19/2010:svn:pn:pvr:rvnIntelCorporation:rnD945GSEJT:rvrAAE57850-300:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1356558/+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
