[Kernel-packages] [Bug 1481136] Re: Bluetooth mouse fails to reconnect after suspend + resume
I have the same Bluetooth mouse and had the same issue, a script fixed this problem for me (http://ubuntuforums.org/showthread.php?t=1387211). -- 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/1481136 Title: Bluetooth mouse fails to reconnect after suspend + resume Status in canonical-pocket-desktop: In Progress Status in bluez package in Ubuntu: In Progress Bug description: I can connect the bluetooth mouse (Logitech M557) using the GUI and the device works properly. However, after suspend and resume the mouse fails to reconnect. It does attempt to reconnect, in that I see the padlock flashes momentarily onto the bluetooth icon on the toolbar applet. Similarly, if the Bluetooth Settings dialog is open the devices flashes momentarily bold as if connected. Both effects happen whenever the mouse is used (movement or mouse click) but the device does not connect. I have a workaround, which is to remove the device and pair it using the command line as follows: sudo bluez-test-device remove 00:1F:20:EF:B1:00 sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 remove sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 sudo bluez-test-device trusted 00:1F:20:EF:B1:00 yes sudo bluez-test-input connect 00:1F:20:EF:B1:00 Once paired manually in this manner the devices appears in the Bluetooth Settings as normal an successfully reconnects when resuming. I'm submitted a new bug as this is similar but not the same as other bugs reported. In particular the workarounds presented in other bugs do not work for me and the workaround I'm using was not suggested in other cases. Thanks. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: bluez 4.101-0ubuntu25 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 4 09:53:18 2015 InstallationDate: Installed on 2014-01-23 (557 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: TOSHIBA KIRA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic.efi.signed root=UUID=a0fdb0ee-bbeb-4872-8e79-1a785c304e91 ro libata.force=noncq vesafb.invalid=1 splash quiet nopat vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2013 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.30 dmi.board.asset.tag: 00 dmi.board.name: KIRA dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.30:bd02/15/2013:svnTOSHIBA:pnKIRA:pvrPSU7FA-00T00K:rvnTOSHIBA:rnKIRA:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: KIRA dmi.product.version: PSU7FA-00T00K dmi.sys.vendor: TOSHIBA hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: B4:B6:76:C4:A2:88 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:587136 acl:36542 sco:0 events:271 errors:0 TX bytes:2913 acl:109 sco:0 commands:81 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2015-08-01T14:24:23.630880 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1481136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1487525] Re: Dell 1525 wakes up on opening the lid, but keyboard takes ages to react
So, test was succesful, it seems the bug does not exist with latest upstream kernel. ** Tags added: kernel-fixed-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1487525 Title: Dell 1525 wakes up on opening the lid, but keyboard takes ages to react Status in linux package in Ubuntu: Incomplete Bug description: What happens: When the lid is closed, ubuntu gets into a sleep state. When I open the lid, the system recovers from sleep, the display shows the screensaver, but the keyboard does not react on any input. I'll have to wait several minutes, bevore the keyboard accepts input and I can log in again. Mouse works normal. What should happen: When I open the lid, the system should recover normally and the keyboard should accept input to let me log in. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-26-generic 3.19.0-26.28 ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: midnatsol 1566 F pulseaudio Date: Fri Aug 21 17:49:41 2015 HibernationDevice: RESUME=UUID=9b5d1018-92ac-4a6b-bcb4-ce8351e95de7 MachineType: Dell Inc. Inspiron 1525 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic root=UUID=5887be20-c47d-41fc-ac15-d517cb5fc739 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.19.0-26-generic N/A linux-backports-modules-3.19.0-26-generic N/A linux-firmware 1.143.3 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0U990C dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd10/27/2009:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1487525/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485184] cavac (amd64) - tests ran: 71, failed: 67
tests ran: 71, failed: 67; http://kernel.ubuntu.com/testing/cavac__3.19.0-27.29~14.04.1__2015-08-26_17-49-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1485184 Title: linux-lts-vivid: 3.19.0-27.29~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-lts-vivid package in Ubuntu: New Status in linux-lts-vivid source package in Trusty: New Bug description: This bug is for tracking the 3.19.0-27.29~14.04.1 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:Saturday, 15. August 2015 07:02 UTC kernel-stable-master-bug:1485113 kernel-stable-Prepare-package-end:Sunday, 16. August 2015 12:03 UTC kernel-stable-Promote-to-proposed-start:Sunday, 16. August 2015 12:03 UTC kernel-stable-Promote-to-proposed-end:Monday, 17. August 2015 23:01 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 18. August 2015 00:04 UTC kernel-stable-Verification-testing-start:Tuesday, 18. August 2015 00:04 UTC kernel-stable-Certification-testing-start:Tuesday, 18. August 2015 00:04 UTC kernel-stable-Security-signoff-start:Tuesday, 18. August 2015 00:04 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 18. August 2015 00:04 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1485184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485081] rukbah (i386) - tests ran: 4, failed: 0
tests ran: 4, failed: 0; http://kernel.ubuntu.com/testing/rukbah__3.2.0-90.128__2015-08-26_17-36-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1485081 Title: linux: 3.2.0-90.128 -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: Fix Released 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 Precise: New Bug description: This bug is for tracking the 3.2.0-90.128 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:Friday, 14. August 2015 18:50 UTC kernel-stable-Prepare-package-end:Saturday, 15. August 2015 03:04 UTC kernel-stable-Promote-to-proposed-start:Saturday, 15. August 2015 03:04 UTC kernel-stable-Promote-to-proposed-end:Monday, 17. August 2015 23:00 UTC kernel-stable-Verification-testing-start:Tuesday, 18. August 2015 00:00 UTC kernel-stable-Certification-testing-start:Tuesday, 18. August 2015 00:00 UTC kernel-stable-Security-signoff-start:Tuesday, 18. August 2015 00:00 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 18. August 2015 00:00 UTC kernel-stable-phase:Testing kernel-stable-phase-changed:Monday, 24. August 2015 16:00 UTC kernel-stable-Verification-testing-end:Monday, 24. August 2015 16:00 UTC kernel-stable-Regression-testing-end:Monday, 24. August 2015 16:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1485081/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1475608] Re: bluetooth dual sim
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: telepathy-ofono (Ubuntu) Status: New = Confirmed -- 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/1475608 Title: bluetooth dual sim Status in Canonical System Image: New Status in bluez package in Ubuntu: Confirmed Status in telepathy-ofono package in Ubuntu: Confirmed Bug description: Hi, I have a BQ phone with 2 SIM-cards. When connected to my handsfree-set (built-in radio set Opel), it shows the provider of my 2nd SIM. When someone phones me on SIM 1, it doesn't go to the hands-free set. But I when I answer the phone (while still connected with BT), I cannot hear the other person, nor does he hear me. Calls on SIM 2 are working as expected. Regards, Carl To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1475608/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1475608] Re: bluetooth dual sim
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New = Confirmed -- 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/1475608 Title: bluetooth dual sim Status in Canonical System Image: New Status in bluez package in Ubuntu: Confirmed Status in telepathy-ofono package in Ubuntu: Confirmed Bug description: Hi, I have a BQ phone with 2 SIM-cards. When connected to my handsfree-set (built-in radio set Opel), it shows the provider of my 2nd SIM. When someone phones me on SIM 1, it doesn't go to the hands-free set. But I when I answer the phone (while still connected with BT), I cannot hear the other person, nor does he hear me. Calls on SIM 2 are working as expected. Regards, Carl To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1475608/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1473540] Re: Kernels above 3.16.33 have problem with Intel 9C60 controller
I have found that Packard Bell EN TF71BM is direct clone of Acer ES1-511. Both ones use the same BIOS. Here someone wrote about touch pad problems https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1449782 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1473540 Title: Kernels above 3.16.33 have problem with Intel 9C60 controller Status in linux package in Ubuntu: Confirmed Bug description: Kernels above 3.16.33 have problem with Intel 9C60 controller. It look s like some pci/dma controller problem. System hangs durting startup. So, it is not possible to use 14.04.2 release on Intel BayTrail platforms. Here they write about it: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773445 It concerns xhci-pci module --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pwoloszyn 1486 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=f7ca3778-7db8-4d09-9327-9362d4794e77 InstallationDate: Installed on 2015-08-05 (0 days ago) InstallationMedia: Ubuntu MATE 14.04.2 Trusty Tahr - LTS amd64 (20150323) MachineType: Packard Bell Easynote ENTF71BM Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-45-generic root=UUID=49713de4-c44b-42ea-8c90-2b6bfb2315e3 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-45.60~14.04.1-generic 3.16.7-ckt14 RelatedPackageVersions: linux-restricted-modules-3.16.0-45-generic N/A linux-backports-modules-3.16.0-45-generic N/A linux-firmware 1.145-0~131~ubuntu14.04.1 Tags: trusty Uname: Linux 3.16.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/25/2014 dmi.bios.vendor: Packard Bell dmi.bios.version: V1.09 dmi.board.name: Easynote ENTF71BM dmi.board.vendor: Packard Bell dmi.board.version: V1.09 dmi.chassis.type: 10 dmi.chassis.vendor: Packard Bell dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPackardBell:bvrV1.09:bd09/25/2014:svnPackardBell:pnEasynoteENTF71BM:pvrV1.09:rvnPackardBell:rnEasynoteENTF71BM:rvrV1.09:cvnPackardBell:ct10:cvrChassisVersion: dmi.product.name: Easynote ENTF71BM dmi.product.version: V1.09 dmi.sys.vendor: Packard Bell --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pwoloszyn 1485 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=f7ca3778-7db8-4d09-9327-9362d4794e77 InstallationDate: Installed on 2015-08-05 (0 days ago) InstallationMedia: Ubuntu MATE 14.04.2 Trusty Tahr - LTS amd64 (20150323) MachineType: Packard Bell Easynote ENTF71BM Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-33-generic root=UUID=49713de4-c44b-42ea-8c90-2b6bfb2315e3 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 RelatedPackageVersions: linux-restricted-modules-3.16.0-33-generic N/A linux-backports-modules-3.16.0-33-generic N/A linux-firmware 1.145-0~131~ubuntu14.04.1 Tags: trusty Uname: Linux 3.16.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/25/2014 dmi.bios.vendor: Packard Bell dmi.bios.version: V1.09 dmi.board.name: Easynote ENTF71BM dmi.board.vendor: Packard Bell dmi.board.version: V1.09 dmi.chassis.type: 10 dmi.chassis.vendor: Packard Bell dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPackardBell:bvrV1.09:bd09/25/2014:svnPackardBell:pnEasynoteENTF71BM:pvrV1.09:rvnPackardBell:rnEasynoteENTF71BM:rvrV1.09:cvnPackardBell:ct10:cvrChassisVersion: dmi.product.name: Easynote ENTF71BM dmi.product.version: V1.09 dmi.sys.vendor: Packard Bell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1473540/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1489109] [NEW] system freezing with bluetooth sony vaio mouse
Public bug reported: Hello, I am testing Ubuntu-gnome 15.10... For this, I installed Wily in my notebook Sony VAIO SVS151290. I bought this notebook already with a Vaio integrated bluetooth mouse from Sony. While I used the Vivid I could use the mouse normally but after I did a fresh install of Wily, I began to realize that Ubuntu started to freeze completely, so that I am forced to shut down the notebook for it to return to work. Ctrl+Alt+F'n' does not work, 'Caps Lock' does not work,' Num Lock' does not work ... the computer stay completely paralyzed showing the frozen screen with content that was running just before freezing. At first I thought it was some crash that could be linked to the new kernel 4.1.0-3, but then one day, I had to put the mouse to recharge and I noticed that the Ubuntu worked normally throughout all the day. From there I started doing some tests and found that the crash only occurs when I use the Sony VAIO mouse... If I do not to connect the mouse and use only the touchpad, everything works normally without freezing. Every new update of Wily I've been redoing the tests but so far, the freezing is still occurring. Thank you very much! ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: bluetooth 5.33-0ubuntu4 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Aug 26 15:06:12 2015 InstallationDate: Installed on 2015-07-30 (27 days ago) InstallationMedia: Ubuntu-GNOME 15.10 Wily Werewolf - Alpha amd64 (20150728) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Sony Corporation SVS151290X PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-3-generic root=UUID=5b11d9d8-e0cc-462f-a2c0-72e8af1ae050 ro quiet splash vt.handoff=7 SourcePackage: bluez UdevLog: Error: [Errno 2] Arquivo ou diretório não encontrado: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R0081C8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR0081C8:bd09/18/2012:svnSonyCorporation:pnSVS151290X:pvrC60BKPK7:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVS151290X dmi.product.version: C60BKPK7 dmi.sys.vendor: Sony Corporation hciconfig: hci0: Type: BR/EDR Bus: USB BD Address: C8:F7:33:3A:53:C1 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:688 acl:0 sco:0 events:49 errors:0 TX bytes:2707 acl:0 sco:0 commands:48 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- 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/1489109 Title: system freezing with bluetooth sony vaio mouse Status in bluez package in Ubuntu: New Bug description: Hello, I am testing Ubuntu-gnome 15.10... For this, I installed Wily in my notebook Sony VAIO SVS151290. I bought this notebook already with a Vaio integrated bluetooth mouse from Sony. While I used the Vivid I could use the mouse normally but after I did a fresh install of Wily, I began to realize that Ubuntu started to freeze completely, so that I am forced to shut down the notebook for it to return to work. Ctrl+Alt+F'n' does not work, 'Caps Lock' does not work,' Num Lock' does not work ... the computer stay completely paralyzed showing the frozen screen with content that was running just before freezing. At first I thought it was some crash that could be linked to the new kernel 4.1.0-3, but then one day, I had to put the mouse to recharge and I noticed that the Ubuntu worked normally throughout all the day. From there I started doing some tests and found that the crash only occurs when I use the Sony VAIO mouse... If I do not to connect the mouse and use only the touchpad, everything works normally without freezing. Every new update of Wily I've been redoing the tests but so far, the freezing is still occurring. Thank you very much! ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: bluetooth 5.33-0ubuntu4 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Aug 26 15:06:12 2015 InstallationDate: Installed on 2015-07-30 (27 days ago) InstallationMedia: Ubuntu-GNOME 15.10 Wily Werewolf - Alpha amd64 (20150728) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Sony Corporation SVS151290X PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-3-generic
[Kernel-packages] [Bug 1349879] Re: powering off an usb3 device causes kernel to resume immediately after suspend
I've filed a bug report about the same issue (#1486581) and found two other bug reports about this (#1454253 and #1389990). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1349879 Title: powering off an usb3 device causes kernel to resume immediately after suspend Status in linux package in Ubuntu: Confirmed Bug description: After powering off an usb3 disk (e.g. udisksctl power-off -b /dev/sdc) the system immediately resumes after suspend. This does not happen, if I umount the device and disconnect it. Usb devices 3.0 seem not to be affected. How to reproduce: 1) plug an usb3 device to an usb3 port and mount it 2) umount it 3) power it off: udisksctl power-off -b /dev/sdX 4) suspend: (e.g. echo mem /sys/power/state) result: system suspends and immediately resumes Package: udisks2 (2.1.3-1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349879/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1389990] Re: [ASRock H77M] Computer resumes right after going into suspend
I've filed a bug report about the same issue (#1486581) and found two other bug reports about this (#1454253 and #1349879). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1389990 Title: [ASRock H77M] Computer resumes right after going into suspend Status in linux package in Ubuntu: Triaged Bug description: how to reproduce the problem at my computer: 1) plug USB3.0 HDD to USB3.0 port at motherboard(Asrock H77M) backpanel 2) mount USB3.0 HDD 3) use it 4) unmount USB3.0 HDD 5) do suspend from 'xfce4-session-logout' or 'action button' of desktop panel, after then,computer go into suspend state once,but right after into suspend,computer resumes by itself ,without any user interaction. USB 2.0 HDD on USB 2.0 port has no problem. Upstream post: http://www.spinics.net/lists/linux-acpi/msg54918.html ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-39-generic 3.13.0-39.66 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Nov 6 16:57:15 2014 InstallationDate: Installed on 2014-04-19 (201 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic.efi.signed root=UUID=32ad3f6d-6568-4377-81b1-50a0ebbe7b60 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-39-generic N/A linux-backports-modules-3.13.0-39-generic N/A linux-firmware 1.127.7 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.60 dmi.board.name: H77M 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.60:bd08/09/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH77M: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/1389990/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1454253] Re: external usb breaks suspend
Found two other bug reports about this issue: #1349879 and #1389990 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1454253 Title: external usb breaks suspend Status in linux package in Ubuntu: Confirmed Bug description: After booting xubuntu 15.04 it's possible to suspend it the normal way BUT - only until you've plugged external usb hard drive. After that (even if it was unmounted and removed) it becomes impossible: the system goes to suspend briefly (for bout 1 second) but immediately wakes up for no apparent reason. I suspect there's some weird bug in xfce power management - is there a way to disable it alltogether and rely on systemd directly instead? --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 15.04 EcryptfsInUse: Yes Package: linux (not installed) Tags: vivid Uname: Linux 4.1.0-040100rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy fuse kismet libvirtd lpadmin netdev plugdev sambashare scanner sudo tape video wireshark _MarkForUpload: True --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 15.04 EcryptfsInUse: Yes Package: linux (not installed) Tags: vivid Uname: Linux 4.1.0-040100rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy fuse kismet libvirtd lpadmin netdev plugdev sambashare scanner sudo tape video wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1454253/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1397285] Re: O2 Micro cardreader [1217:8621] could not read a specific mmc card
** Summary changed: - O2 Micro cardreader [1217:8621] could not read mmc cards + O2 Micro cardreader [1217:8621] could not read a specific mmc card ** Changed in: hwe-next Status: Triaged = Incomplete ** Changed in: linux (Ubuntu) Status: Triaged = 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/1397285 Title: O2 Micro cardreader [1217:8621] could not read a specific mmc card Status in HWE Next: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Dell Inspiron 3048 (CID 201401-14493) on Ubuntu 14.04.1 Steps to reproduce the bug: 1. boot the system, login and wait for the desktop ready to use 2. plugin mmc card Expected result: mmc directory will pop up and ready to use it. Actual result: no thing pop up on desktop --- dmesg -- [ 41.180392] mmc0: Got data interrupt 0x0200 even though no data operation was in progress. [ 51.210537] mmc0: Timeout waiting for hardware interrupt. [ 51.212627] mmc0: Got data interrupt 0x0200 even though no data operation was in progress. [ 61.229658] mmc0: Timeout waiting for hardware interrupt. [ 61.231738] mmc0: Got data interrupt 0x0200 even though no data operation was in progress. [ 71.248714] mmc0: Timeout waiting for hardware interrupt. [ 71.250815] mmc0: Got data interrupt 0x0200 even though no data operation was in progress. [ 81.267947] mmc0: Timeout waiting for hardware interrupt. [ 81.270026] mmc0: error -110 whilst initialising MMC card [ 81.377041] mmc0: Got data interrupt 0x0200 even though no data operation was in progress. [ 86.065388] mmc0: Card removed during transfer! [ 86.065398] mmc0: Resetting controller. [ 86.065544] mmc0: error -123 whilst initialising MMC card ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 [modified: boot/vmlinuz-3.13.0-32-generic] ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1447 F pulseaudio /dev/snd/controlC1: ubuntu 1447 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 28 05:20:43 2014 HibernationDevice: RESUME=UUID=265f8dc9-0dff-4a1b-9a3b-08fb662a7daf InstallationDate: Installed on 2014-11-26 (2 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Inspiron 20 Model 3048 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=f35024ba-c412-4316-8474-bd2a586c6c1b ro rootdelay=60 quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: X19 dmi.board.name: 0HD5K4 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrX19:bd12/18/2013:svnDellInc.:pnInspiron20Model3048:pvr01:rvnDellInc.:rn0HD5K4:rvrX02:cvnDellInc.:ct13:cvr: dmi.product.name: Inspiron 20 Model 3048 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1397285/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 962082] Re: Profiles that require duplex audio like Head Set (HSP) and Hands Free (HFP) do not work on machines with Broadcom BCM20702A0 Bluetooth chips
After going throughout a lot of foros, the solution given at http://plugable.com/2014/06/23/plugable-usb-bluetooth-adapter-solving- hfphsp-profile-issues-on-linux#comment-41932 solved my problem. -- 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/962082 Title: Profiles that require duplex audio like Head Set (HSP) and Hands Free (HFP) do not work on machines with Broadcom BCM20702A0 Bluetooth chips Status in HWE Next: Fix Released Status in bluez package in Ubuntu: Fix Released Bug description: This problem seems to occur on every device that uses the BCM20702A0 Bluetooth hardware. How to reproduce: (1) Pair a bluetooth headset with a machine equipped with a BCM20702A0. (2) Activate the device. Usually there is a button on the headset you should press to notify the bluetooth stack that you're ready to use the device. This creates SCO link and the plumbs the audio components. (3) Open the sound settings tool and select the bluetooth device under the Input and Output tabs. Under each tab you should see a table with an entry that has a headset icon on the left with the bluetooth device name to the right. This is the item to select. Now, everything should be configured so that you can use your bluetooth device to hear and record audio. Test this by: Testing Input: (1) In the sound settings tool, select the Input tab. (2) Make sure the Input Volume is not muted and the scale widget is not set to zero. (3) Make sounds into the headset mic -- you should see the Input Level bar raise. Testing Output: In the same program: (1) Select the Hardware tab. (2) In the box labeled Choose a device to configure, select your bluetooth device. (3) A combobox should appear at the bottom of the window labeled Settings for the selected device. Choose Telephony Duplex (HSP/HFP). (4) Now click on the Test Speakers button to the right. (5) Run speaker test. You should hear a sound. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/962082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1371233] Re: USB 3.0 connection is unreliable + xHCI xhci_drop_endpoint called with disabled ep
Dell XPS 13 9333, Ubuntu 14.04, 3.19.0-26-generic, USB 3.0 HDD enclosure (ASMedia AS2105). Directly connected to USB3 port - not detected at all. Connected to USB2.0 hub - detected and perfectly worked. Connected to USB 3.0 hub (ASIX AX88179) - determined ~50% times (~50% no any line in syslog after plug in). When it successfully determined in USB3 hub - works after it without any problem (however my test was short - 15 min rsync with a lot of files (my home folder)) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1371233 Title: USB 3.0 connection is unreliable + xHCI xhci_drop_endpoint called with disabled ep Status in linux package in Ubuntu: Incomplete Status in linux source package in Trusty: Incomplete Status in linux source package in Utopic: Incomplete Status in linux source package in Vivid: Incomplete Bug description: based on https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358871/comments/7 I tested with the HDD enclosure IcyBox IB-351 series with USB 3.0 connection with the same result (connection drops after 300 MB reading, error message xHCI xhci_drop_endpoint called with disabled ep occurs sometimes, other devices (e.g. Samsung HD103SI 1 TB HDD connected with 3.0 USB adapter to eSATA of enclosure) read hundreds of GB before failing, but definitely do before reading 1TB). Reading tested with `dd`, `gpart` and `btrfsck`. Also confirmed on Lenovo IdeaPad-Z500 after BIOS update to 71CN51WW(V1.21) (changelog didn't indicate any USB issues anyway). Also confirmed with 3.16.3 and 3.16.0-14 on Ubuntu 14.10-beta1 after updates. The issue seems to cause failure of ASIX AX179 gigabit ethernet chip as well, but is independent from the usage of the ethernet adapter. I'm without any clue and stuck with an unreliable USB and ethernet connection which basically means no I/O out of the machine!! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-35-generic 3.13.0-35.62 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D3', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Thu Sep 18 19:58:24 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-10 (8 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: LENOVO 20221 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-35-generic.efi.signed root=UUID=5e999111-7efe-4818-b9e8-a950ad6d3296 ro rootflags=subvol=@ quiet splash nomdmonddf nomdmonisw 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 StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch: dmi.product.name: 20221 dmi.product.version: Lenovo IdeaPad Z500 Touch dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371233/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1488758] Re: GPU crash on NUC with i915
Maybe relevant: https://bugs.freedesktop.org/show_bug.cgi?id=89901 ** Bug watch added: freedesktop.org Bugzilla #89901 https://bugs.freedesktop.org/show_bug.cgi?id=89901 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1488758 Title: GPU crash on NUC with i915 Status in linux package in Ubuntu: Confirmed Bug description: Setup: Intel NUC, i915 graphics, two monitors, one connected with miniHDMI-HDMI cable, second with miniDP-HDMI cable. Screen goes black, flickers back on, goes black again. Only resolution is to ssh into the machine and reboot. Before rebooting, I got lots of these (about 106k lines) in syslog: kernel: [404964.521324] [drm:hsw_unclaimed_reg_detect.isra.12 [i915]] *ERROR* Unclaimed register detected. Please use the i915.mmio_debug=1 to debug this problem.[drm:hsw_unclaimed_reg_detect.isra.12 [i915]] *ERROR* Unclaimed register detected. Please use the i915.mmio_debug=1 to debug this problem. ...then, kernel: [406333.381029] [drm] stuck on render ring kernel: [406333.381945] [drm] GPU HANG: ecode 8:0:0xf5de, in Xorg [918], reason: Ring hung, action: reset kernel: [406333.381947] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. kernel: [406333.381947] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI - DRM/Intel kernel: [406333.381948] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. kernel: [406333.381949] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. kernel: [406333.381951] [drm] GPU crash dump saved to /sys/class/drm/card0/error kernel: [406333.389006] drm/i915: Resetting chip after gpu hang kernel: [406339.379515] [drm] stuck on render ring kernel: [406339.380430] [drm] GPU HANG: ecode 8:0:0x85db, in webapp-containe [14994], reason: Ring hung, action: reset kernel: [406339.380583] drm/i915: Resetting chip after gpu hang kernel: [406417.336790] [drm] GPU HANG: ecode 8:0:0xf5de, in Xorg [918], reason: Ring hung, action: reset kernel: [406417.343850] drm/i915: Resetting chip after gpu hang kernel: [407944.976072] [drm] GPU HANG: ecode 8:0:0xf5de, in Xorg [918], reason: Ring hung, action: reset kernel: [407944.983106] drm/i915: Resetting chip after gpu hang kernel: [409258.618636] [drm] GPU HANG: ecode 8:0:0xf5de, in Xorg [918], reason: Ring hung, action: reset kernel: [409258.625733] drm/i915: Resetting chip after gpu hang kernel: [409264.604180] [drm] stuck on render ring kernel: [409264.605059] [drm] GPU HANG: ecode 8:0:0xf5de, in Xorg [918], reason: Ring hung, action: reset kernel: [409264.605153] [drm:i915_set_reset_status [i915]] *ERROR* gpu hanging too fast, banning! kernel: [409264.612163] drm/i915: Resetting chip after gpu hang ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-26-generic 3.19.0-26.28 ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 Date: Wed Aug 26 12:31:15 2015 InstallationDate: Installed on 2015-08-01 (24 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-26-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1488758/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1415880] Re: 14e4:4365 bcmwl-kernel source: fix for null pointer crash
Testing the package from the PPA on Kubuntu 14.04.3 64bit, kernel 3.19.0-27-generic. Current status: uptime 23 hours, 12 successful suspend cycles. It was happening for me not every time, but I've tried really hard to reproduce (downloading via wi-fi while attempting to suspend and trying other stuff) and was unable to reproduce kernel panic. Will be monitoring further. -- 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/1415880 Title: 14e4:4365 bcmwl-kernel source: fix for null pointer crash Status in Dell Sputnik: Confirmed Status in bcmwl package in Ubuntu: In Progress Bug description: The bcmwl package as of now misses one patch for a bug that occurs with BCM43142 and possibly other broadcom chipsets that will look like random disconnects, poor wifi signal and kernel warnings, See also #1379524. Adding the patch is a fairly simple process: * put the patch file in /usr/src/bcmwl-6.30.223.248+bdcom/patches * add the following line to /usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf PATCH[7]=0014-null-pointer-crash.patch * run: /usr/lib/dkms/common.postinst bcmwl 6.30.223.248+bdcom /usr/share/bcmwl x86_64 $(uname -r) This has fixed the issue for me. Edit: I just wanted to add that I did not write the patch; I merely downloaded it from a paste that was linked from the respective AUR package. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 [modified: usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf] ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: LXDE Date: Thu Jan 29 13:15:17 2015 InstallationDate: Installed on 2015-01-26 (3 days ago) InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1415880/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1436940] Re: Atheros wifi 168c:0041(QCA6164) is not supported
Hi Diego, Thanks for the fix.I got my WIFI working but I lost my bluetooth. This is what the dmesg showing for bluetooth. dmesg | grep -i blue [7.609957] Bluetooth: Core ver 2.20 [7.609975] Bluetooth: HCI device and connection manager initialized [7.609978] Bluetooth: HCI socket layer initialized [7.609980] Bluetooth: L2CAP socket layer initialized [7.609987] Bluetooth: SCO socket layer initialized [7.616484] Bluetooth: RFCOMM TTY layer initialized [7.616494] Bluetooth: RFCOMM socket layer initialized [7.616499] Bluetooth: RFCOMM ver 1.11 [7.626119] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [7.626121] Bluetooth: BNEP filters: protocol multicast [7.626125] Bluetooth: BNEP socket layer initialized [9.046001] bluetooth hci0: Direct firmware load for qca/rampatch_usb_0200.bin failed with error -2 [9.046005] Bluetooth: hci0: failed to request rampatch file: qca/rampatch_usb_0200.bin (-2) Mine is the same card as yours but only difference is it is showing QCA988X instead of QCA6174.Do I need to change any thing in the git patch to make both WIFI and Bluetooth work? PS : Bluetooth is working initially but after the steps,now WIFI works but bluetooth doesnt :( -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1436940 Title: Atheros wifi 168c:0041(QCA6164) is not supported Status in linux package in Ubuntu: Confirmed Status in linux source package in Vivid: Confirmed Status in linux source package in Wily: Confirmed Bug description: The atheros wireless device (168c:0041) isn't supported by the ath10k_pci kernel driver. Found in several laptop models: Lenovo Z70 Lenovo G50-45 Lenovo G50-80 Lenovo Edge 15 Lenovo Yoga 3 11 Lenovo Flex 3-1470 Samsung ATIV Book 9 NP930X2K ProblemType: BugDistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-9-generic 3.19.0-9.9 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicholas 1695 F pulseaudio /dev/snd/controlC1: nicholas 1695 F pulseaudio CurrentDesktop: Unity Date: Thu Mar 26 09:47:16 2015 HibernationDevice: RESUME=UUID=5b068cd8-e60a-49b9-a88e-1581bb6b3dc1 InstallationDate: Installed on 2015-03-25 (1 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 003: ID 5986:0652 Acer, Inc Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80E5 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=e52867c5-0b50-42fb-8288-f30765f926c5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-9-generic N/A linux-backports-modules-3.19.0-9-generic N/A linux-firmware1.143SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-03-26 (0 days ago) dmi.bios.date: 06/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: B0CN69WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo G50-80 dmi.board.vendor: LENOVO dmi.board.version: 31900058 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-80 dmi.modalias: dmi:bvnLENOVO:bvrB0CN69WW:bd06/20/2014:svnLENOVO:pn80E5:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoG50-80: dmi.product.name: 80E5 dmi.product.version: Lenovo G50-80 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1436940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1472843] Re: [O2Micro 1217:8621] MMC plus card failed to be inited
the fix was applied to -next, still waiting mainline -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1472843 Title: [O2Micro 1217:8621] MMC plus card failed to be inited Status in HWE Next: Triaged Status in linux package in Ubuntu: Triaged Bug description: Actual result: MMC plus card could not be auto-mounted. Expect result: MMC plus card is mounted. Note: there is a way could mount MMC plus card automatically. Power on and log in system - plug in SD card - SD card mounted - eject SD card - plug in MMC plus card, system will mount MMC plus card automatically. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1472843/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1085766] Re: /var/log/upstart/ureadahead.log contains garbage
same problem in 15.04 again -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1085766 Title: /var/log/upstart/ureadahead.log contains garbage Status in linux package in Ubuntu: Fix Released Status in ureadahead package in Ubuntu: Fix Released Bug description: After an upgrade to Raring (as of today) from Quantal I'm seeing tons of these in /var/log/upstart/ureadahead.log: Counted 8 CPUs ureadahead: ��a��w: Ignored relative path ureadahead: : Ignored relative path ureadahead: �=%���n�T9: Ignored relative path ureadahead: �=%v9T9: Ignored relative path ureadahead: �=%���U�Ek�: Ignored relative path ureadahead: �=%���`�a: Ignored relative path (the boot was wonderfully fast - not sure if that's because ureadahead was working well or if it's because it didn't do anything). Dave ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ureadahead 0.100.0-12build1 ProcVersionSignature: Ubuntu 3.7.0-4.12-generic 3.7.0-rc7 Uname: Linux 3.7.0-4-generic x86_64 ApportVersion: 2.6.3-0ubuntu2 Architecture: amd64 Date: Mon Dec 3 02:06:14 2012 InstallationDate: Installed on 2012-07-17 (138 days ago) InstallationMedia: Kubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120717) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: ureadahead UpgradeStatus: Upgraded to raring on 2012-12-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1085766/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1449438] Re: Marvell 88W8797 wifi (module mwifiex) does not work on Surface Pro
Any new results? Same prob here SP1 pro and ubuntu 15.04. Thx -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1449438 Title: Marvell 88W8797 wifi (module mwifiex) does not work on Surface Pro Status in linux package in Ubuntu: Incomplete Bug description: I've been running Ubuntu 14.10 on a Microsoft Surface Pro. After some initial problems (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1165938) (fixed by kernel updates I guess) the wifi was working fine. Since the upgrade to 15.04 the problems are back: I can connect to a wifi network, the connection is working for a few seconds but drops right after. I attached the relevant entries in dmes.log. I tried installing the marvell firmware from git://git.marvell.com /mwifiex-firmware.git, that didn't change anything. I also tried the mainline kernel from http://kernel.ubuntu.com/~kernel- ppa/mainline/v4.1-rc1-vivid/: the connection is again working for a few seconds but the whole system hangs afterwards. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-15-generic 3.19.0-15.15 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wilk 1792 F pulseaudio CurrentDesktop: Unity Date: Tue Apr 28 10:57:42 2015 HibernationDevice: RESUME=UUID=adb12a68-9928-4181-b4e2-487010d3c501 InstallationDate: Installed on 2014-02-19 (432 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Microsoft Corporation Surface with Windows 8 Pro ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic.efi.signed root=UUID=919f00b8-5010-46e1-b2f9-c129e17d5312 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-15-generic N/A linux-backports-modules-3.19.0-15-generic N/A linux-firmware 1.143 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-04-27 (0 days ago) dmi.bios.date: 01/08/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.00.0250 dmi.board.asset.tag: 0 dmi.board.name: Surface with Windows 8 Pro dmi.board.vendor: Microsoft Corporation dmi.board.version: 1 dmi.chassis.asset.tag: 0 dmi.chassis.type: 17 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.00.0250:bd01/08/2013:svnMicrosoftCorporation:pnSurfacewithWindows8Pro:pvr1:rvnMicrosoftCorporation:rnSurfacewithWindows8Pro:rvr1:cvnMicrosoftCorporation:ct17:cvr1: dmi.product.name: Surface with Windows 8 Pro dmi.product.version: 1 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1449438/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1489077] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run: apport-collect 1489077 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/1489077 Title: v4l2 can crash computer with badly written userland code Status in linux package in Ubuntu: Incomplete Bug description: In my simple bit of code to grab a frame from a webcam based on the example code given here: https://gist.github.com/Circuitsoft/1126411 I found a badly crafted version would crash the computer (dead except for flashing keyboard lights). Simply calling ioctl(cam, VIDIOC_STREAMON, buf.type) twice without calling VIDIOC_STREAMOFF inbetween causes the crash. I realise this code is incompetent but it shouldn't require a hard reboot to recover from it. I guess this might be rather system specific however it seemed worth reporting. I can't recall the last time I managed to crash a linux box from userland... Kernel: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24 Camera: Bus 001 Device 002: ID 046d:0990 Logitech, Inc. QuickCam Pro 9000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1489077/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1475166] Re: Ubuntu 15.04 Install Error with Avago Controller
I haven't checked the values after successful install. I can check and let you know. Are you saying that what I tried: adding megaraid_sas.max_sectors=2048 wouldn't sustain on reboot ? and hence forth might have issues rebooting and getting in on 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/1475166 Title: Ubuntu 15.04 Install Error with Avago Controller Status in linux package in Ubuntu: Triaged Bug description: Hello Canonical Team We are running to an issue installing ubuntu PPC64LE 15.04 full blown image on our servers (with RAID controller). Installation hangs around 70% of progress. An important part of our configuration is Avago RAID controller: 9361-8i Firmware version we used is 4.300.00-4429, and the package is 24.10.0-0002. IMPORTANT: It has to be noted that with same hardware configuration 14.10 full blown image installs fine. Dmesg logs are attached: Looking at dmesg logs point out that: LSI (avago) driver loads fine During further interaction with raid volume during the installation process, firmware errors are seen [ 196.991417] megasas: FW status 0x3 [ 196.999376] megasas: FW status 0x3 [ 197.007376] megasas: FW status 0x3 Further down the process I/O errors are thrown [ 217.438664] Buffer I/O error on device sda2, logical block 22052864 [ 217.438671] Buffer I/O error on device sda2, logical block 22052865 [ 217.438678] Buffer I/O error on device sda2, logical block 22052866 [ 217.438686] Buffer I/O error on device sda2, logical block 22052867 Full dmesg log is attached. Snippet is pasted below highlighting: It can be noted that there’s a Mellanox Connectx 3 pro card with some test Firmware on our setup. We can Ignore any diagnostic messages from that card in dmesg logs for the purpose of this bug. Thanks Adi Gangidi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1475166] Re: Ubuntu 15.04 Install Error with Avago Controller
Yes it would only be for one boot, to use that as a workaround you want to add it permanently to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub. Then run sudo update-grub. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1475166 Title: Ubuntu 15.04 Install Error with Avago Controller Status in linux package in Ubuntu: Triaged Bug description: Hello Canonical Team We are running to an issue installing ubuntu PPC64LE 15.04 full blown image on our servers (with RAID controller). Installation hangs around 70% of progress. An important part of our configuration is Avago RAID controller: 9361-8i Firmware version we used is 4.300.00-4429, and the package is 24.10.0-0002. IMPORTANT: It has to be noted that with same hardware configuration 14.10 full blown image installs fine. Dmesg logs are attached: Looking at dmesg logs point out that: LSI (avago) driver loads fine During further interaction with raid volume during the installation process, firmware errors are seen [ 196.991417] megasas: FW status 0x3 [ 196.999376] megasas: FW status 0x3 [ 197.007376] megasas: FW status 0x3 Further down the process I/O errors are thrown [ 217.438664] Buffer I/O error on device sda2, logical block 22052864 [ 217.438671] Buffer I/O error on device sda2, logical block 22052865 [ 217.438678] Buffer I/O error on device sda2, logical block 22052866 [ 217.438686] Buffer I/O error on device sda2, logical block 22052867 Full dmesg log is attached. Snippet is pasted below highlighting: It can be noted that there’s a Mellanox Connectx 3 pro card with some test Firmware on our setup. We can Ignore any diagnostic messages from that card in dmesg logs for the purpose of this bug. Thanks Adi Gangidi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1487085] Comment bridged from LTC Bugzilla
--- Comment From cha...@us.ibm.com 2015-08-26 16:32 EDT--- *** Bug 129458 has been marked as a duplicate of this bug. *** --- Comment From cha...@us.ibm.com 2015-08-26 16:40 EDT--- Hi Chris, This problem is starting to become prevalent among the testers. Any outlook as to when this fix may get released? 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/1487085 Title: Ubuntu 14.04.3 LTS Crash in notifier_call_chain after boot Status in linux package in Ubuntu: New Status in linux source package in Vivid: Fix Committed Bug description: SRU Justification: [Impact] Users of 3.19 kernel with power8 machines get a kernel crash on boot. [Test Case] Boot system. [Fix] commit 792f96e9a769b799a2944e9369e4ea1e467135b2 needed to be backported in addition to d7cf83fcaf1b1668201eae4cdd6e6fe7a2448654. Our 3.19 kernel had a partial backport of the first patch. -- ---Problem Description--- Installed Ubuntu 14.04.3 LTS on Palmetto and its crashing after booting to login. This happens every time I boot Ubuntu 14.04.3 LTS. I've reinstalled Ubuntu and replaced the hard disk as well and re-installed. Still crashing. ---uname output--- Linux paul40 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:10:52 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux Machine Type = Palmetto ---System Hang--- Ubuntu OS crashes and cannot access host. Must reboot system ---Steps to Reproduce--- Boot system Oops output: [ 33.132376] Unable to handle kernel paging request for data at address 0x200 [ 33.132565] Faulting instruction address: 0xc00dbc60 [ 33.133422] Oops: Kernel access of bad area, sig: 11 [#1] [ 33.134410] SMP NR_CPUS=2048 NUMA PowerNV [ 33.134478] Modules linked in: ast ttm drm_kms_helper joydev mac_hid drm hid_generic usbhid hid syscopyarea sysfillrect sysimgblt i2c_algo_bit ofpart cmdlinepart at24 uio_pdrv_genirq powernv_flash mtd ipmi_powernv powernv_rng opal_prd ipmi_msghandler uio uas usb_storage ahci libahci [ 33.139112] CPU: 24 PID: 0 Comm: swapper/24 Not tainted 3.19.0-26-generic #28~14.04.1-Ubuntu [ 33.139943] task: c13cccb0 ti: c00fff70 task.ti: c1448000 [ 33.141642] NIP: c00dbc60 LR: c00dbd94 CTR: [ 33.142605] REGS: c00fff703980 TRAP: 0300 Not tainted (3.19.0-26-generic) [ 33.143417] MSR: 90009033 SF,HV,EE,ME,IR,DR,RI,LE CR: 28002888 XER: [ 33.144244] CFAR: c0008468 DAR: 0200 DSISR: 4000 SOFTE: 0 GPR00: c00dbd94 c00fff703c00 c144cc00 c15f03c0 GPR04: 0007 c15f03b8 GPR08: 0200 c006c394 90001003 GPR12: 2200 cfb8d800 0058 GPR16: c1448000 c1448000 c1448080 c0e9a880 GPR20: c1448080 0001 0002 0012 GPR24: c00f1e432200 c15f03b8 GPR28: 0007 c15f03c0 [ 33.157013] NIP [c00dbc60] notifier_call_chain+0x70/0x100 [ 33.157818] LR [c00dbd94] atomic_notifier_call_chain+0x44/0x60 [ 33.162090] Call Trace: [ 33.162845] [c00fff703c00] [0008] 0x8 (unreliable) [ 33.163644] [c00fff703c50] [c00dbd94] atomic_notifier_call_chain+0x44/0x60 [ 33.164647] [c00fff703c90] [c006f2a8] opal_message_notify+0xa8/0x100 [ 33.165476] [c00fff703d00] [c00dbc88] notifier_call_chain+0x98/0x100 [ 33.167007] [c00fff703d50] [c00dbd94] atomic_notifier_call_chain+0x44/0x60 [ 33.167816] [c00fff703d90] [c006f654] opal_do_notifier.part.5+0x74/0xa0 [ 33.172166] [c00fff703dd0] [c006f6d8] opal_interrupt+0x58/0x70 [ 33.172997] [c00fff703e10] [c01273d0] handle_irq_event_percpu+0x90/0x2b0 [ 33.174507] [c00fff703ed0] [c0127658] handle_irq_event+0x68/0xd0 [ 33.175312] [c00fff703f00] [c012baf4] handle_fasteoi_irq+0xe4/0x240 [ 33.176124] [c00fff703f30] [c01265c8] generic_handle_irq+0x58/0x90 [ 33.176936] [c00fff703f60] [c0010f10] __do_irq+0x80/0x190 [ 33.182406] [c00fff703f90] [c002476c] call_do_irq+0x14/0x24 [ 33.183258] [c144ba30] [c00110c0] do_IRQ+0xa0/0x120 [ 33.184072] [c144ba90] [c00025d8] hardware_interrupt_common+0x158/0x180 [ 33.184907] --- interrupt: 501 at arch_local_irq_restore+0x5c/0x90 [
[Kernel-packages] [Bug 1489077] [NEW] v4l2 can crash computer with badly written userland code
Public bug reported: In my simple bit of code to grab a frame from a webcam based on the example code given here: https://gist.github.com/Circuitsoft/1126411 I found a badly crafted version would crash the computer (dead except for flashing keyboard lights). Simply calling ioctl(cam, VIDIOC_STREAMON, buf.type) twice without calling VIDIOC_STREAMOFF inbetween causes the crash. I realise this code is incompetent but it shouldn't require a hard reboot to recover from it. I guess this might be rather system specific however it seemed worth reporting. I can't recall the last time I managed to crash a linux box from userland... Kernel: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24 Camera: Bus 001 Device 002: ID 046d:0990 Logitech, Inc. QuickCam Pro 9000 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1489077 Title: v4l2 can crash computer with badly written userland code Status in linux package in Ubuntu: Incomplete Bug description: In my simple bit of code to grab a frame from a webcam based on the example code given here: https://gist.github.com/Circuitsoft/1126411 I found a badly crafted version would crash the computer (dead except for flashing keyboard lights). Simply calling ioctl(cam, VIDIOC_STREAMON, buf.type) twice without calling VIDIOC_STREAMOFF inbetween causes the crash. I realise this code is incompetent but it shouldn't require a hard reboot to recover from it. I guess this might be rather system specific however it seemed worth reporting. I can't recall the last time I managed to crash a linux box from userland... Kernel: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24 Camera: Bus 001 Device 002: ID 046d:0990 Logitech, Inc. QuickCam Pro 9000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1489077/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1310800] Re: 056a:0302 Trusty Tahr, kernel 3.13: automatic load of wacom.ko driver cause a hard kernel panic
I've taken a long hard look at this bug and believe I've been able to nail down the cause. The panic is caused by a NULL pointer being passed to the 'input_report_switch' function. It occurs if the kernel has probed the tablet's pen/pad interface and processes a status report from it before the kernel has a chance to probe the tablet's touchpad interface. The suggested workaround of loading the module before connecting the tablet only masks the issue by changing the timing of events enough so that the kernel is able to finish probing both interfaces before processing the status report. This issue was addressed upstream by commit 44b9683 (HID: wacom - make sure touch_input is valid before using it) which is part of the 3.19 kernel. Both the Trusty (3.13) and Vivid (3.16) kernels are missing this patch, however. Commit 44b9683 can be trivially backported; I've attached such a backport for convenience. ** Patch added: Upstream 44b9683 modified to apply against Ubuntu's 3.13 and 3.16 kernels https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310800/+attachment/4452940/+files/make-sure-touch_input-is-valid-before-using.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1310800 Title: 056a:0302 Trusty Tahr, kernel 3.13: automatic load of wacom.ko driver cause a hard kernel panic Status in linux package in Ubuntu: Confirmed Bug description: I have just upgraded to 14.04 from 13.10. I have a wacom cth-480 touch+pen tablet, which was not recognized on 13.10 (kernel 3.11). With the stock kernel from 14.04, I have an immediate kernel panic as soon as I plug in the tablet to the laptop. The system is a asus 1005PE (32 bit install), Xubuntu, up-to date: Linux asus-romano 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:08:14 UTC 2014 i686 i686 i686 GNU/Linux The really strange thing is that if I manually load the driver with `sudo modprobe wacom` *before* pluggin the tablet in, then the tablet is recognized and works ok: SYS: Apr 21 15:15:47 asus-romano kernel: [ 265.664161] usbcore: registered new interface driver wacom SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.088161] usb 2-1: new full-speed USB device number 2 using uhci_hcd SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253626] usb 2-1: New USB device found, idVendor=056a, idProduct=0302 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253641] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253651] usb 2-1: Product: Intuos PTS SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253659] usb 2-1: Manufacturer: Wacom Co.,Ltd. SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.257027] input: Wacom Intuos PT S Pen as /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.0/input/input14 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.260630] input: Wacom Intuos PT S Finger as /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.1/input/input15 SYS: Apr 21 15:15:52 asus-romano mtp-probe: checking bus 2, device 2: /sys/devices/pci:00/:00:1d.0/usb2/2-1 SYS: Apr 21 15:15:52 asus-romano mtp-probe: bus: 2, device: 2 was not an MTP device A screenshot of the kernel panic is added. I can reproduce it at will. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310800/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1442466] Re: [Dell Inspiron 3147] wireless hotkey does not work on 14.04.2
Fixed in Ubuntu-3.19.0-27.29 ** Changed in: hwe-next Status: Triaged = Fix Released ** Changed in: linux-lts-utopic (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1442466 Title: [Dell Inspiron 3147] wireless hotkey does not work on 14.04.2 Status in HWE Next: Fix Released Status in linux-lts-utopic package in Ubuntu: Fix Released Bug description: 201403-14889 Steps to reproduce this bug: fn+printscr button (this is the way to trigger wireless switch) Expected to reproduce this bug: wireless on/off Actual result: 1. wireless applet has no response 2. rfkill list has no reponse. always shows 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no More info: 1. APs could be scanned. 2. could enable/disable wifi via desktop applet. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-34-generic 3.16.0-34.45~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-34.45~14.04.1-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 10 11:53:57 2015 InstallationDate: Installed on 2015-04-09 (0 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1654 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=442dffc7-a562-4b0d-a6d6-cb69d6891c61 InstallationDate: Installed on 2015-04-09 (0 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) MachineType: Dell Inc. Inspiron 11 - 3147 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-34-generic.efi.signed root=UUID=da9b59f7-7780-41c5-9e5f-03acb414b69e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-34.45~14.04.1-generic 3.16.7-ckt8 RelatedPackageVersions: linux-restricted-modules-3.16.0-34-generic N/A linux-backports-modules-3.16.0-34-generic N/A linux-firmware 1.127.11 Tags: trusty Uname: Linux 3.16.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/22/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: X30 dmi.board.name: 00K010 dmi.board.vendor: Dell Inc. dmi.board.version: D02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: X30 dmi.modalias: dmi:bvnDellInc.:bvrX30:bd08/22/2014:svnDellInc.:pnInspiron11-3147:pvr:rvnDellInc.:rn00K010:rvrD02:cvnDellInc.:ct8:cvrX30: dmi.product.name: Inspiron 11 - 3147 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1442466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1407569] Re: [Dell Latitude 3340] Bluetooth cannot be controlled by the wireless key
Fixed in Ubuntu-3.19.0-27.29 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1407569 Title: [Dell Latitude 3340] Bluetooth cannot be controlled by the wireless key Status in linux package in Ubuntu: Confirmed Bug description: CID: 201312-14381 Dell Latitude 3340 The wireless key cannot control the Bluetooth on this system. Steps: 1. Install 14.04.1 + update, boot to desktop 2. Try to disable / enable the Bluetooth by using the wireless key Actual result: * before pressing the wireless key ubuntu@201312-14381:~$ rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-bluetooth: Bluetooth Soft blocked: no Hard blocked: no * After pressing the wireless key, Wifi will be disabled, but the Bluetooth does not. The BT applet won't be disabled. I could still run Set up new devices... from the menu. hcitool scan from console still can find some other devices. ubuntu@201312-14381:~$ rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: yes 2: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: yes 3: dell-bluetooth: Bluetooth Soft blocked: no Hard blocked: yes ubuntu@201312-14381:~$ hcitool scan Scanning ... 20:16:D8:6F:A2:74 chaos-0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-43-generic 3.13.0-43.72 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1540 F pulseaudio /dev/snd/controlC0: ubuntu 1540 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Mon Jan 5 01:47:58 2015 HibernationDevice: RESUME=UUID=8881bf5a-55d6-4314-80db-170ff3d262b6 InstallationDate: Installed on 2015-01-05 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Latitude 3340 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic.efi.signed root=UUID=9f9c408e-d1c2-496c-9fd2-8f9ecb77810b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-43-generic N/A linux-backports-modules-3.13.0-43-generic N/A linux-firmware 1.127.10 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/02/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 4OA010 dmi.board.vendor: Dell Inc. dmi.board.version: D01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd05/02/2014:svnDellInc.:pnLatitude3340:pvr01:rvnDellInc.:rn4OA010:rvrD01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude 3340 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407569/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1439935] Re: [Dell Inspiron 7746] Wireless key does not work on 14.04.2
Fixed in Ubuntu-3.19.0-27.29 ** Changed in: hwe-next Status: Triaged = Fix Released ** Changed in: linux-lts-utopic (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1439935 Title: [Dell Inspiron 7746] Wireless key does not work on 14.04.2 Status in HWE Next: Fix Released Status in linux-lts-utopic package in Ubuntu: Fix Released Bug description: CID: 201408-15456 Dell Inspiron 7746 The wireless key does not work on this system at all with14.04.2 (3.16 kernel) Maybe it's related to the udev - systemd migration (similar to bug 1434442) ubuntu@201408-15456:~$ sudo showkey -k [sudo] password for ubuntu: kb mode was ?UNKNOWN? [ if you are trying this under X, it might not work since the X server is also reading /dev/console ] press any key (program terminates 10s after last keypress)... keycode 240 press keycode 240 release ^Ccaught signal 2, cleaning up... ubuntu@201408-15456:~$ nothing could be detected by sudo showkey -s ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-33-generic 3.16.0-33.44~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 2 23:22:28 2015 InstallationDate: Installed on 2015-04-03 (0 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1439935/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1440949] Re: [Dell Inspiron 3543] Wireless key does not work on 14.04.2
** Changed in: linux (Ubuntu Vivid) Status: Fix Committed = Fix Released ** Changed in: linux-lts-utopic (Ubuntu) Status: Fix Committed = Fix Released ** Changed in: hwe-next Status: In Progress = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1440949 Title: [Dell Inspiron 3543] Wireless key does not work on 14.04.2 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux-lts-utopic package in Ubuntu: Fix Released Status in linux source package in Vivid: Fix Released Status in linux-lts-utopic source package in Vivid: New Bug description: CID: 201408-15437 Dell Inspiron 3543 The wireless key does not work on this system at all with14.04.2 (3.16 kernel) Maybe it's related to the udev - systemd migration (similar to bug 1434442) ubuntu@201408-15437:~$ sudo showkey -k [sudo] password for ubuntu: kb mode was ?UNKNOWN? [ if you are trying this under X, it might not work since the X server is also reading /dev/console ] press any key (program terminates 10s after last keypress)... keycode 28 release keycode 240 press keycode 240 release keycode 29 press ^Ccaught signal 2, cleaning up... ubuntu@201408-15437:~$ nothing could be detected by sudo showkey -s ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-33-generic 3.16.0-33.44~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 6 22:17:20 2015 InstallationDate: Installed on 2015-04-03 (3 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1440949/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485102] Re: linux: 3.13.0-63.103 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed = In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) = Yung Shen (kaxing) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1485102 Title: linux: 3.13.0-63.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-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released 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 Trusty: Confirmed Bug description: This bug is for tracking the 3.13.0-63.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:Friday, 14. August 2015 19:58 UTC kernel-stable-Prepare-package-end:Saturday, 15. August 2015 05:04 UTC kernel-stable-Promote-to-proposed-start:Saturday, 15. August 2015 05:04 UTC kernel-stable-Promote-to-proposed-end:Monday, 17. August 2015 23:00 UTC kernel-stable-Verification-testing-start:Tuesday, 18. August 2015 00:01 UTC kernel-stable-Certification-testing-start:Tuesday, 18. August 2015 00:01 UTC kernel-stable-Security-signoff-start:Tuesday, 18. August 2015 00:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 18. August 2015 00:01 UTC kernel-stable-phase:Testing kernel-stable-phase-changed:Monday, 24. August 2015 16:00 UTC kernel-stable-Verification-testing-end:Monday, 24. August 2015 16:00 UTC kernel-stable-Regression-testing-end:Monday, 24. August 2015 16:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1485102/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485184] Re: linux-lts-vivid: 3.19.0-27.29~14.04.1 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed = In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) = Yung Shen (kaxing) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1485184 Title: linux-lts-vivid: 3.19.0-27.29~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-lts-vivid package in Ubuntu: New Status in linux-lts-vivid source package in Trusty: New Bug description: This bug is for tracking the 3.19.0-27.29~14.04.1 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:Saturday, 15. August 2015 07:02 UTC kernel-stable-master-bug:1485113 kernel-stable-Prepare-package-end:Sunday, 16. August 2015 12:03 UTC kernel-stable-Promote-to-proposed-start:Sunday, 16. August 2015 12:03 UTC kernel-stable-Promote-to-proposed-end:Monday, 17. August 2015 23:01 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 18. August 2015 00:04 UTC kernel-stable-Verification-testing-start:Tuesday, 18. August 2015 00:04 UTC kernel-stable-Certification-testing-start:Tuesday, 18. August 2015 00:04 UTC kernel-stable-Security-signoff-start:Tuesday, 18. August 2015 00:04 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 18. August 2015 00:04 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1485184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1435278] Re: [Dell Vostro 3449] Wireless key does not work on 14.04.2 (3.16 kernel)
The fix is included in Ubuntu-3.19.0-27.29 ** Changed in: hwe-next Status: Triaged = Fix Released ** Changed in: linux-lts-utopic (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1435278 Title: [Dell Vostro 3449] Wireless key does not work on 14.04.2 (3.16 kernel) Status in HWE Next: Fix Released Status in linux-lts-utopic package in Ubuntu: Fix Released Bug description: CID: 201408-15447 Dell Vostro 3449 The wireless key does not work on this system at all. acpi_osi=\!Windows 2012\ parameter can't make it work. And unlike bug 1434442, adding options dell_laptop force_rfkill=1 into /etc/modprobe.d/dell.conf can't make it work as well. ubuntu@201408-15447:~$ sudo showkey -k kb mode was ?UNKNOWN? [ if you are trying this under X, it might not work since the X server is also reading /dev/console ] press any key (program terminates 10s after last keypress)... keycode 28 release keycode 240 press keycode 240 release keycode 29 press ^Ccaught signal 2, cleaning up... ubuntu@201408-15447:~$ nothing could be detected by using sudo showkey -s ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-31-generic 3.16.0-31.43~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 23 07:04:20 2015 InstallationDate: Installed on 2015-03-23 (0 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1435278/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1434442] Re: [Vostro 3549] Wireless key does not work on 14.04.2
Fixed is included in Ubuntu-3.19.0-27.29 ** Changed in: linux-lts-utopic (Ubuntu) Status: Confirmed = Fix Released ** Changed in: hwe-next Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1434442 Title: [Vostro 3549] Wireless key does not work on 14.04.2 Status in HWE Next: Fix Released Status in linux-lts-utopic package in Ubuntu: Fix Released Bug description: CID: 201408-15444 Vostro 3549 The wireless key does not work on this system. Debugging information: ubuntu@201408-15444:~$ sudo showkey -k kb mode was ?UNKNOWN? [ if you are trying this under X, it might not work since the X server is also reading /dev/console ] press any key (program terminates 10s after last keypress)... keycode 28 release keycode 240 press keycode 240 release ^Ccaught signal 2, cleaning up... Nothing could be detected by sudo showkey -s ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-31-generic 3.16.0-31.43~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 20 04:24:01 2015 InstallationDate: Installed on 2015-03-20 (0 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1434442/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1486146] Re: recvfrom SYSCALL infinite loop/deadlock chewing 100% CPU (MSG_PEEK|MSG_WAITALL)
** Tags added: kernel-bug-break-fix ** Description changed: In a multi-threaded pthreads process running on Ubuntu 14.04 AMD64 (with over 1000 threads) which uses real time FIFO scheduling, we occasionally see calls to recv() with flags (MSG_PEEK | MSG_WAITALL) get stuck in an infinte loop or deadlock meaning the threads lock up chewing as much CPU as they can (due to FIFO scheduling) while stuck inside recv(). Here's an example gdb back trace: [Switching to thread 4 (Thread 0x7f6040546700 (LWP 27251))] #0 0x7f6231d2f7eb in __libc_recv (fd=fd@entry=146, buf=buf@entry=0x7f6040543600, n=n@entry=5, flags=-1, flags@entry=258) at ../sysdeps/unix/sysv/linux/x86_64/recv.c:33 33 ../sysdeps/unix/sysv/linux/x86_64/recv.c: No such file or directory. (gdb) bt #0 0x7f6231d2f7eb in __libc_recv (fd=fd@entry=146, buf=buf@entry=0x7f6040543600, n=n@entry=5, flags=-1, flags@entry=258) at ../sysdeps/unix/sysv/linux/x86_64/recv.c:33 #1 0x00421945 in recv (__flags=258, __n=5, __buf=0x7f6040543600, __fd=146) at /usr/include/x86_64-linux-gnu/bits/socket2.h:44 [snip] The socket is a TCP socket in blocking mode, the recv() call is inside an outer loop with a counter, and I've checked the counter with gdb and it's always at 1, meaning that I'm sure that the outer loop isn't the problem, the thread is indeed deadlocked inside the recv() internals. - Other nodes: + Other nodes: * There always seems to be 2 or more threads deadlocked in the same place (same recv() call but with distinct FDs) * The threads calling recv() have cancellation disbaled by previously executing: thread_setcancelstate(PTHREAD_CANCEL_DISABLE, NULL); I've even tried adding a poll() call for POLLRDNORM on the socket before calling recv() with MSG_PEEK | MSG_WAITALL flags to try to make sure there's data available on the socket before calling *recv()*, but it makes no difference. So, I don't know what is wrong here, I've read all the recv() documentation and believe that recv() is being used correctly, the only conclusion I can come to is that there is a bug in libc recv() when using flags MSG_PEEK | MSG_WAITALL with thousands of pthreads running. + + === + break-fix: - dfbafc995304ebb9a9b03f65083e6e9cea143b20 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1486146 Title: recvfrom SYSCALL infinite loop/deadlock chewing 100% CPU (MSG_PEEK|MSG_WAITALL) Status in Linux: Unknown Status in linux package in Ubuntu: Fix Committed Status in linux-lts-utopic package in Ubuntu: New Status in linux source package in Trusty: Fix Committed Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux source package in Vivid: Fix Committed Status in linux source package in Wily: Fix Committed Bug description: In a multi-threaded pthreads process running on Ubuntu 14.04 AMD64 (with over 1000 threads) which uses real time FIFO scheduling, we occasionally see calls to recv() with flags (MSG_PEEK | MSG_WAITALL) get stuck in an infinte loop or deadlock meaning the threads lock up chewing as much CPU as they can (due to FIFO scheduling) while stuck inside recv(). Here's an example gdb back trace: [Switching to thread 4 (Thread 0x7f6040546700 (LWP 27251))] #0 0x7f6231d2f7eb in __libc_recv (fd=fd@entry=146, buf=buf@entry=0x7f6040543600, n=n@entry=5, flags=-1, flags@entry=258) at ../sysdeps/unix/sysv/linux/x86_64/recv.c:33 33 ../sysdeps/unix/sysv/linux/x86_64/recv.c: No such file or directory. (gdb) bt #0 0x7f6231d2f7eb in __libc_recv (fd=fd@entry=146, buf=buf@entry=0x7f6040543600, n=n@entry=5, flags=-1, flags@entry=258) at ../sysdeps/unix/sysv/linux/x86_64/recv.c:33 #1 0x00421945 in recv (__flags=258, __n=5, __buf=0x7f6040543600, __fd=146) at /usr/include/x86_64-linux-gnu/bits/socket2.h:44 [snip] The socket is a TCP socket in blocking mode, the recv() call is inside an outer loop with a counter, and I've checked the counter with gdb and it's always at 1, meaning that I'm sure that the outer loop isn't the problem, the thread is indeed deadlocked inside the recv() internals. Other nodes: * There always seems to be 2 or more threads deadlocked in the same place (same recv() call but with distinct FDs) * The threads calling recv() have cancellation disbaled by previously executing: thread_setcancelstate(PTHREAD_CANCEL_DISABLE, NULL); I've even tried adding a poll() call for POLLRDNORM on the socket before calling recv() with MSG_PEEK | MSG_WAITALL flags to try to make sure there's data available on the socket before calling *recv()*, but it makes no difference. So, I don't know what is wrong here, I've read all the recv() documentation and believe that recv() is being used correctly, the only conclusion I can come to is that there is a bug in
[Kernel-packages] [Bug 1481136] Re: Bluetooth mouse fails to reconnect after suspend + resume
We now have two things mixed in here. 1. Device doesn't connect directly after it got paired in the UI and needs a second user step to get connected 2. A keyboard doesn't reconnect after it turned off or the using device went to sleep First problem needs fixes in ubuntu-system-settings which I have at https://code.launchpad.net/~morphis/ubuntu-system-settings/fix-device- actions Second problem requires to backport fixes from upstream bluez to correctly enable the reconnect mode of HID devices. ** Changed in: bluez (Ubuntu) Assignee: (unassigned) = Simon Fels (morphis) ** Changed in: bluez (Ubuntu) Status: Confirmed = In Progress -- 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/1481136 Title: Bluetooth mouse fails to reconnect after suspend + resume Status in canonical-pocket-desktop: New Status in bluez package in Ubuntu: In Progress Bug description: I can connect the bluetooth mouse (Logitech M557) using the GUI and the device works properly. However, after suspend and resume the mouse fails to reconnect. It does attempt to reconnect, in that I see the padlock flashes momentarily onto the bluetooth icon on the toolbar applet. Similarly, if the Bluetooth Settings dialog is open the devices flashes momentarily bold as if connected. Both effects happen whenever the mouse is used (movement or mouse click) but the device does not connect. I have a workaround, which is to remove the device and pair it using the command line as follows: sudo bluez-test-device remove 00:1F:20:EF:B1:00 sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 remove sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 sudo bluez-test-device trusted 00:1F:20:EF:B1:00 yes sudo bluez-test-input connect 00:1F:20:EF:B1:00 Once paired manually in this manner the devices appears in the Bluetooth Settings as normal an successfully reconnects when resuming. I'm submitted a new bug as this is similar but not the same as other bugs reported. In particular the workarounds presented in other bugs do not work for me and the workaround I'm using was not suggested in other cases. Thanks. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: bluez 4.101-0ubuntu25 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 4 09:53:18 2015 InstallationDate: Installed on 2014-01-23 (557 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: TOSHIBA KIRA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic.efi.signed root=UUID=a0fdb0ee-bbeb-4872-8e79-1a785c304e91 ro libata.force=noncq vesafb.invalid=1 splash quiet nopat vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2013 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.30 dmi.board.asset.tag: 00 dmi.board.name: KIRA dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.30:bd02/15/2013:svnTOSHIBA:pnKIRA:pvrPSU7FA-00T00K:rvnTOSHIBA:rnKIRA:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: KIRA dmi.product.version: PSU7FA-00T00K dmi.sys.vendor: TOSHIBA hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: B4:B6:76:C4:A2:88 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:587136 acl:36542 sco:0 events:271 errors:0 TX bytes:2913 acl:109 sco:0 commands:81 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2015-08-01T14:24:23.630880 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1481136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1466889] Re: [Lenovo ThinkPad X250] SD card is not recognized.
Kernel 3.19.0-27-generic #29-Ubuntu SMP Fri Aug 14 21:43:37 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux [ 1262.959100] mmc0: new high speed SDHC card at address b368 [ 1262.960257] mmcblk0: mmc0:b368 SMI 30.0 GiB [ 1262.961323] mmcblk0: p1 p2 [ 1263.068815] mmcblk0: error -110 transferring data, sector 63075616, nr 8, cmd response 0x900, card status 0xb00 [ 1263.068821] mmcblk0: retrying using single block read [ 1263.153118] mmcblk0: error -110 transferring data, sector 63075616, nr 8, cmd response 0x900, card status 0x0 [ 1263.153125] blk_update_request: 29 callbacks suppressed [ 1263.153128] blk_update_request: I/O error, dev mmcblk0, sector 63075616 [ 1263.237436] mmcblk0: error -110 transferring data, sector 63075617, nr 7, cmd response 0x900, card status 0x0 [ 1263.237445] blk_update_request: I/O error, dev mmcblk0, sector 63075617 Was working a couple of weeks ago with some other 3.19.0-xxx 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/1466889 Title: [Lenovo ThinkPad X250] SD card is not recognized. Status in linux package in Ubuntu: Triaged Bug description: When attempting to use card Gigastone 4GB microSD HC, dmesg(1) shows: [ 37.203529] vboxpci: IOMMU not found (not registered) [ 72.571702] mmc0: new high speed SDHC card at address [ 72.609979] Driver 'mmcblk' needs updating - please use bus_type methods [ 72.610041] mmcblk0: mmc0: SU04G 3.69 GiB [ 72.610832] mmcblk0: p1 [ 72.774560] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. Following GUI popup is displayed (in Japanese): 4.0 GB ボリューム フォルダを書き込みモードで開けません このファイルを扱うアプリケーションが登録されていません This message would be translated to the following in English: 4.0GB volume folder cannot be opened in write-mode. Application to drive this file is not registered. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-21-generic 3.19.0-21.21 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ido1704 F pulseaudio /dev/snd/controlC0: ido1704 F pulseaudio CurrentDesktop: GNOME-Flashback:Unity Date: Fri Jun 19 23:08:49 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=24696e94-8aef-4c8c-bf63-65d01633b6e7 HotplugNewDevices: HotplugNewMounts: /dev/mmcblk0p1 /media/ido/3633-31621 vfat rw,nosuid,nodev,relatime,uid=5356,gid=1000,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,showexec,utf8,flush,errors=remount-ro 0 0 InstallationDate: Installed on 2015-04-25 (55 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) Lsusb: Bus 003 Device 002: ID 8087:8001 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 056e:0078 Elecom Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20CLCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic.efi.signed root=UUID=fc487175-e8cd-42fc-844f-d2175a09a760 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-21-generic N/A linux-backports-modules-3.19.0-21-generic N/A linux-firmware 1.143.1 SourcePackage: linux Symptom: storage UdevLog: Error: [Errno 2] そのようなファイルやディレクトリはありません: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET28W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CLCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN10ET28W(1.05):bd01/23/2015:svnLENOVO:pn20CLCTO1WW:pvrThinkPadX250:rvnLENOVO:rn20CLCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20CLCTO1WW dmi.product.version: ThinkPad X250 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1466889/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1439592] Re: [Dell Inspiron 7347] Wireless key does not work on 3.16 kernel
The fix is included in Ubuntu-3.19.0-27.29 ** Changed in: hwe-next Status: Triaged = Fix Released ** Changed in: linux-lts-utopic (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1439592 Title: [Dell Inspiron 7347] Wireless key does not work on 3.16 kernel Status in HWE Next: Fix Released Status in linux-lts-utopic package in Ubuntu: Fix Released Bug description: CID: 201406-15234 Dell Inspiron 7347 The wireless key does not work on this system at all with 14.04.2 (3.16 kernel) Maybe it's related to the udev - systemd migration (similar to bug 1434442) ubuntu@201406-15234:~$ sudo showkey -k kb mode was ?UNKNOWN? [ if you are trying this under X, it might not work since the X server is also reading /dev/console ] press any key (program terminates 10s after last keypress)... keycode 28 release keycode 240 press keycode 240 release ^Ccaught signal 2, cleaning up... ubuntu@201406-15234:~$ Nothing can be detected by the sudo showkey -s command ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-30-generic 3.16.0-30.40~14.04.1 [modified: boot/vmlinuz-3.16.0-30-generic] ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 2 05:12:56 2015 InstallationDate: Installed on 2015-04-02 (0 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1439592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1488842] [NEW] Can't copy and paste more than 4kB into a terminal
Public bug reported: I am unable to copy and paste more than 4kB of script into a terminal (e.g. gnome-terminal, xterm). I have been encountering this issue for nearly a decade now (across multiple distributions, including Ubuntu 14.04 LTS). I believe it may relate to kernel parameter N_TTY_BUF_SIZE. A similar problem appears to have been reported here; http://comments.gmane.org/gmane.linux.kernel/1253720. Use case; 1. The user has a large semi-automated script (e.g. 2000 line deployment instructions.txt; which do not justify full automation*). 2. The user wishes to copy and paste one or more automated sections of the script into a terminal (e.g. gnome-terminal, xterm, etc) while following the self-contained instructions. 3. Those automated sections of the script may contain more than 4kB worth of data (spread across multiple lines) Actual behaviour; - the script being pasted into the terminal is corrupted, then executed Expected Behaviour; - the script is successfully pasted into the terminal, then executed I have reported this issue because it is not intuitive that the system should behave like this. While now that I know it may be a fundamental limitation of current (/prior) Linux kernels, I will ensure to work around it in future activity. However, it is feasible that someone else may encounter this issue before it is rectified. Every time this issue occurs there is a possibility of system corruption (depending on the precise script being copied to the terminal). Perhaps a patch has already been released? Or if this issue should be reported elsewhere, feel free to recommend an alternative forum. * e.g. because the self-contained instructions only need to be executed ~10 times across the product life cycle, taking into account the fact automation time is a function of a) how busy the user is / spare time they can devote to subsystems, and b) the level of robustness required: automatically editing files which may have been significantly updated between deployments is not necessarily safe. Cheers - Richard ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Attachment added: A text file containing 4.1kB worth of script to be copied and pasted to terminal https://bugs.launchpad.net/bugs/1488842/+attachment/4452624/+files/4.1kB.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1488842 Title: Can't copy and paste more than 4kB into a terminal Status in linux package in Ubuntu: Incomplete Bug description: I am unable to copy and paste more than 4kB of script into a terminal (e.g. gnome-terminal, xterm). I have been encountering this issue for nearly a decade now (across multiple distributions, including Ubuntu 14.04 LTS). I believe it may relate to kernel parameter N_TTY_BUF_SIZE. A similar problem appears to have been reported here; http://comments.gmane.org/gmane.linux.kernel/1253720. Use case; 1. The user has a large semi-automated script (e.g. 2000 line deployment instructions.txt; which do not justify full automation*). 2. The user wishes to copy and paste one or more automated sections of the script into a terminal (e.g. gnome-terminal, xterm, etc) while following the self-contained instructions. 3. Those automated sections of the script may contain more than 4kB worth of data (spread across multiple lines) Actual behaviour; - the script being pasted into the terminal is corrupted, then executed Expected Behaviour; - the script is successfully pasted into the terminal, then executed I have reported this issue because it is not intuitive that the system should behave like this. While now that I know it may be a fundamental limitation of current (/prior) Linux kernels, I will ensure to work around it in future activity. However, it is feasible that someone else may encounter this issue before it is rectified. Every time this issue occurs there is a possibility of system corruption (depending on the precise script being copied to the terminal). Perhaps a patch has already been released? Or if this issue should be reported elsewhere, feel free to recommend an alternative forum. * e.g. because the self-contained instructions only need to be executed ~10 times across the product life cycle, taking into account the fact automation time is a function of a) how busy the user is / spare time they can devote to subsystems, and b) the level of robustness required: automatically editing files which may have been significantly updated between deployments is not necessarily safe. Cheers - Richard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1488842/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1481136] Re: Bluetooth mouse fails to reconnect after suspend + resume
** Also affects: qtmir Importance: Undecided Status: New ** No longer affects: qtmir (Ubuntu) ** No longer affects: qtmir ** Also affects: canonical-pocket-desktop Importance: Undecided Status: New -- 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/1481136 Title: Bluetooth mouse fails to reconnect after suspend + resume Status in canonical-pocket-desktop: New Status in bluez package in Ubuntu: Confirmed Bug description: I can connect the bluetooth mouse (Logitech M557) using the GUI and the device works properly. However, after suspend and resume the mouse fails to reconnect. It does attempt to reconnect, in that I see the padlock flashes momentarily onto the bluetooth icon on the toolbar applet. Similarly, if the Bluetooth Settings dialog is open the devices flashes momentarily bold as if connected. Both effects happen whenever the mouse is used (movement or mouse click) but the device does not connect. I have a workaround, which is to remove the device and pair it using the command line as follows: sudo bluez-test-device remove 00:1F:20:EF:B1:00 sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 remove sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 sudo bluez-test-device trusted 00:1F:20:EF:B1:00 yes sudo bluez-test-input connect 00:1F:20:EF:B1:00 Once paired manually in this manner the devices appears in the Bluetooth Settings as normal an successfully reconnects when resuming. I'm submitted a new bug as this is similar but not the same as other bugs reported. In particular the workarounds presented in other bugs do not work for me and the workaround I'm using was not suggested in other cases. Thanks. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: bluez 4.101-0ubuntu25 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 4 09:53:18 2015 InstallationDate: Installed on 2014-01-23 (557 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: TOSHIBA KIRA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic.efi.signed root=UUID=a0fdb0ee-bbeb-4872-8e79-1a785c304e91 ro libata.force=noncq vesafb.invalid=1 splash quiet nopat vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2013 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.30 dmi.board.asset.tag: 00 dmi.board.name: KIRA dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.30:bd02/15/2013:svnTOSHIBA:pnKIRA:pvrPSU7FA-00T00K:rvnTOSHIBA:rnKIRA:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: KIRA dmi.product.version: PSU7FA-00T00K dmi.sys.vendor: TOSHIBA hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: B4:B6:76:C4:A2:88 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:587136 acl:36542 sco:0 events:271 errors:0 TX bytes:2913 acl:109 sco:0 commands:81 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2015-08-01T14:24:23.630880 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1481136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1284093] Re: Please update regulations to support VHT
I install vivid and tried to download some packages (for an upgrade to wily). After initial successs download slowed and pings to google.com were equally 1000ms. Other computers on my network for pings of 30ms. On installing this package and rebooting the packages all downloaded fine and pings to google.com were 30ms reliably for the 30 minutes it took to download them. I installed 2014.11.18-1ubuntu1~ubuntu15.04.1 from vivid-proposed ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1284093 Title: Please update regulations to support VHT Status in wireless-regdb package in Ubuntu: Fix Released Status in wireless-regdb source package in Vivid: Fix Committed Status in wireless-regdb source package in Wily: Fix Released Bug description: Only very recent versions of wireless-regdb have support for VHT (80mhz channels); in addition, all current kernels have a bug that will cause your card to fail to associate with a VHT ap when your local regdb didn't allow VHT: https://bugzilla.kernel.org/show_bug.cgi?id=70881 I have updated the existing Debian bug requesting this too: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729089 Well, more precisely I have emailed the update but it hasn't gone through yet. :) I would recommend updating to 2013.11.27 (current upstream) as it includes other regulatory fixes. I would also recommend applying this to at least Precise and Trusty, possibly Saucy since it is still supported. Here is the update that should post to the Debian bug soon: I would much appreciate this, especially you make the jump to 2013.11.27. The new regdb will also solve issues with 802.11ac; the referenced version appears to be the first with support for 80mhz channels. Without the new regdb (or a patch the kernel that masks the symptoms, below), when you connect to an AP that supports 80mhz channels, you are disconnected with a nearly useless error. Link to the ticket, with details and the symptom-masking patch that will be in future kernels: https://bugzilla.kernel.org/show_bug.cgi?id=70881 It would be great if we could get the new regdb upstream into Debian asap; in the meantime I will try to get an updated version into a ppa for Ubuntu users at least. ;) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1284093/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1447053] Re: IO_PAGE_FAULT
I am seeing the same issue starting w/kernel version 3.13.0.59. [ 42.022439] AMD-Vi: Event logged [IO_PAGE_FAULT device=04:00.0 domain=0x0018 address=0x0002a000 flags=0x] [ 42.055391] xhci_hcd :04:00.0: WARNING: Host System Error [ 42.087222] xhci_hcd :04:00.0: Host not halted after 16000 microseconds. [ 52.033830] xhci_hcd :04:00.0: xHCI host not responding to stop endpoint command. [ 52.033839] xhci_hcd :04:00.0: Assuming host is dying, halting host. [ 52.065665] xhci_hcd :04:00.0: Host not halted after 16000 microseconds. [ 52.065679] xhci_hcd :04:00.0: Non-responsive xHCI host is not halting. [ 52.065680] xhci_hcd :04:00.0: Completing active URBs anyway. [ 52.065701] xhci_hcd :04:00.0: HC died; cleaning up [ 52.065802] usb 10-1: USB disconnect, device number 2 And then the ethernet connection stops working (eth0). Booting back to 3.13.0.57 solved the problem, but that means no new kernel updates. I tried all updates after that, they are all broken. So something was introduced at that point. Can anybody look at this? 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/1447053 Title: IO_PAGE_FAULT Status in linux package in Ubuntu: Confirmed Bug description: Since a couple of weeks I'm experiencing a problem with my motherboard. For some reason the network goes randomly offline and I get a error messages about AMD-Vi. [ 6462.248434] AMD-Vi: Event logged [IO_PAGE_FAULT device=04:00.0 domain=0x0019 address=0x3000 flags=0x0050] I didn't changed anything except for the internet modem is changed and I installed updates as I always do. When using google I see there are more people with this problem exactly the same motherboard, I find this strange because my pc is almost a year old and I never had this problem. Could it be a problem in the kernel of *ubuntu 14.04? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-49-generic 3.13.0-49.83 ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: allard 2282 F pulseaudio allard 2467 F pulseaudio /dev/snd/controlC0: allard 2282 F pulseaudio allard 2467 F pulseaudio CurrentDesktop: KDE Date: Wed Apr 22 11:34:46 2015 HibernationDevice: RESUME=UUID=96633d31-18c6-4b01-b756-f5f919c43fb4 InstallationDate: Installed on 2015-03-27 (25 days ago) InstallationMedia: Kubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic root=UUID=2c77ade3-e2ea-4d88-94d6-e131053f8ac8 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-49-generic N/A linux-backports-modules-3.13.0-49-generic N/A linux-firmware 1.127.11 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/02/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2204 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2204:bd04/02/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1447053/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1481136] Re: Bluetooth mouse fails to reconnect after suspend + resume
Simon, your two things analysis seems to fit my observations. I'm not seeing the issue Kevin describes. I'm only seeing what I originally reported (your number 2 above). -- 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/1481136 Title: Bluetooth mouse fails to reconnect after suspend + resume Status in canonical-pocket-desktop: In Progress Status in bluez package in Ubuntu: In Progress Bug description: I can connect the bluetooth mouse (Logitech M557) using the GUI and the device works properly. However, after suspend and resume the mouse fails to reconnect. It does attempt to reconnect, in that I see the padlock flashes momentarily onto the bluetooth icon on the toolbar applet. Similarly, if the Bluetooth Settings dialog is open the devices flashes momentarily bold as if connected. Both effects happen whenever the mouse is used (movement or mouse click) but the device does not connect. I have a workaround, which is to remove the device and pair it using the command line as follows: sudo bluez-test-device remove 00:1F:20:EF:B1:00 sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 remove sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 sudo bluez-test-device trusted 00:1F:20:EF:B1:00 yes sudo bluez-test-input connect 00:1F:20:EF:B1:00 Once paired manually in this manner the devices appears in the Bluetooth Settings as normal an successfully reconnects when resuming. I'm submitted a new bug as this is similar but not the same as other bugs reported. In particular the workarounds presented in other bugs do not work for me and the workaround I'm using was not suggested in other cases. Thanks. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: bluez 4.101-0ubuntu25 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 4 09:53:18 2015 InstallationDate: Installed on 2014-01-23 (557 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: TOSHIBA KIRA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic.efi.signed root=UUID=a0fdb0ee-bbeb-4872-8e79-1a785c304e91 ro libata.force=noncq vesafb.invalid=1 splash quiet nopat vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2013 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.30 dmi.board.asset.tag: 00 dmi.board.name: KIRA dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.30:bd02/15/2013:svnTOSHIBA:pnKIRA:pvrPSU7FA-00T00K:rvnTOSHIBA:rnKIRA:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: KIRA dmi.product.version: PSU7FA-00T00K dmi.sys.vendor: TOSHIBA hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: B4:B6:76:C4:A2:88 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:587136 acl:36542 sco:0 events:271 errors:0 TX bytes:2913 acl:109 sco:0 commands:81 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2015-08-01T14:24:23.630880 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1481136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1481136] Re: Bluetooth mouse fails to reconnect after suspend + resume
Fixes for 1. and 2. are in Silo 009 and 059. Wily should be not affected as we already landed bluez5 there. @Daniel: If you want to test get and install packages from silo 059 in your vivid desktop installation. -- 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/1481136 Title: Bluetooth mouse fails to reconnect after suspend + resume Status in canonical-pocket-desktop: In Progress Status in bluez package in Ubuntu: In Progress Bug description: I can connect the bluetooth mouse (Logitech M557) using the GUI and the device works properly. However, after suspend and resume the mouse fails to reconnect. It does attempt to reconnect, in that I see the padlock flashes momentarily onto the bluetooth icon on the toolbar applet. Similarly, if the Bluetooth Settings dialog is open the devices flashes momentarily bold as if connected. Both effects happen whenever the mouse is used (movement or mouse click) but the device does not connect. I have a workaround, which is to remove the device and pair it using the command line as follows: sudo bluez-test-device remove 00:1F:20:EF:B1:00 sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 remove sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 sudo bluez-test-device trusted 00:1F:20:EF:B1:00 yes sudo bluez-test-input connect 00:1F:20:EF:B1:00 Once paired manually in this manner the devices appears in the Bluetooth Settings as normal an successfully reconnects when resuming. I'm submitted a new bug as this is similar but not the same as other bugs reported. In particular the workarounds presented in other bugs do not work for me and the workaround I'm using was not suggested in other cases. Thanks. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: bluez 4.101-0ubuntu25 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 4 09:53:18 2015 InstallationDate: Installed on 2014-01-23 (557 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: TOSHIBA KIRA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic.efi.signed root=UUID=a0fdb0ee-bbeb-4872-8e79-1a785c304e91 ro libata.force=noncq vesafb.invalid=1 splash quiet nopat vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2013 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.30 dmi.board.asset.tag: 00 dmi.board.name: KIRA dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.30:bd02/15/2013:svnTOSHIBA:pnKIRA:pvrPSU7FA-00T00K:rvnTOSHIBA:rnKIRA:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: KIRA dmi.product.version: PSU7FA-00T00K dmi.sys.vendor: TOSHIBA hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: B4:B6:76:C4:A2:88 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:587136 acl:36542 sco:0 events:271 errors:0 TX bytes:2913 acl:109 sco:0 commands:81 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2015-08-01T14:24:23.630880 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1481136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1488842] Re: Can't copy and paste more than 4kB into a terminal
** 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/1488842 Title: Can't copy and paste more than 4kB into a terminal Status in linux package in Ubuntu: Confirmed Bug description: I am unable to copy and paste more than 4kB of script into a terminal (e.g. gnome-terminal, xterm). I have been encountering this issue for nearly a decade now (across multiple distributions, including Ubuntu 14.04 LTS). I believe it may relate to kernel parameter N_TTY_BUF_SIZE. A similar problem appears to have been reported here; http://comments.gmane.org/gmane.linux.kernel/1253720. Use case; 1. The user has a large semi-automated script (e.g. 2000 line deployment instructions.txt; which do not justify full automation*). 2. The user wishes to copy and paste one or more automated sections of the script into a terminal (e.g. gnome-terminal, xterm, etc) while following the self-contained instructions. 3. Those automated sections of the script may contain more than 4kB worth of data (spread across multiple lines) Actual behaviour; - the script being pasted into the terminal is corrupted, then executed Expected Behaviour; - the script is successfully pasted into the terminal, then executed I have reported this issue because it is not intuitive that the system should behave like this. While now that I know it may be a fundamental limitation of current (/prior) Linux kernels, I will ensure to work around it in future activity. However, it is feasible that someone else may encounter this issue before it is rectified. Every time this issue occurs there is a possibility of system corruption (depending on the precise script being copied to the terminal). Perhaps a patch has already been released? Or if this issue should be reported elsewhere, feel free to recommend an alternative forum. * e.g. because the self-contained instructions only need to be executed ~10 times across the product life cycle, taking into account the fact automation time is a function of a) how busy the user is / spare time they can devote to subsystems, and b) the level of robustness required: automatically editing files which may have been significantly updated between deployments is not necessarily safe. Cheers - Richard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1488842/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1481136] Re: Bluetooth mouse fails to reconnect after suspend + resume
** Changed in: canonical-pocket-desktop Importance: Undecided = High ** Changed in: canonical-pocket-desktop Status: New = In Progress -- 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/1481136 Title: Bluetooth mouse fails to reconnect after suspend + resume Status in canonical-pocket-desktop: In Progress Status in bluez package in Ubuntu: In Progress Bug description: I can connect the bluetooth mouse (Logitech M557) using the GUI and the device works properly. However, after suspend and resume the mouse fails to reconnect. It does attempt to reconnect, in that I see the padlock flashes momentarily onto the bluetooth icon on the toolbar applet. Similarly, if the Bluetooth Settings dialog is open the devices flashes momentarily bold as if connected. Both effects happen whenever the mouse is used (movement or mouse click) but the device does not connect. I have a workaround, which is to remove the device and pair it using the command line as follows: sudo bluez-test-device remove 00:1F:20:EF:B1:00 sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 remove sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 sudo bluez-test-device trusted 00:1F:20:EF:B1:00 yes sudo bluez-test-input connect 00:1F:20:EF:B1:00 Once paired manually in this manner the devices appears in the Bluetooth Settings as normal an successfully reconnects when resuming. I'm submitted a new bug as this is similar but not the same as other bugs reported. In particular the workarounds presented in other bugs do not work for me and the workaround I'm using was not suggested in other cases. Thanks. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: bluez 4.101-0ubuntu25 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 4 09:53:18 2015 InstallationDate: Installed on 2014-01-23 (557 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: TOSHIBA KIRA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic.efi.signed root=UUID=a0fdb0ee-bbeb-4872-8e79-1a785c304e91 ro libata.force=noncq vesafb.invalid=1 splash quiet nopat vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2013 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.30 dmi.board.asset.tag: 00 dmi.board.name: KIRA dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.30:bd02/15/2013:svnTOSHIBA:pnKIRA:pvrPSU7FA-00T00K:rvnTOSHIBA:rnKIRA:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: KIRA dmi.product.version: PSU7FA-00T00K dmi.sys.vendor: TOSHIBA hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: B4:B6:76:C4:A2:88 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:587136 acl:36542 sco:0 events:271 errors:0 TX bytes:2913 acl:109 sco:0 commands:81 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2015-08-01T14:24:23.630880 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1481136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1381175] Re: vgaarb module not patched
Based on the original bug description, this issue affects me. $ lspci -nn 00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) ... 04:00.0 3D controller [0302]: NVIDIA Corporation GK208M [GeForce GT 740M] [10de:1292] (rev ff) $ dmesg | fgrep vgaar [0.243143] vgaarb: setting as boot device: PCI::00:02.0 [0.243145] vgaarb: device added: PCI::00:02.0,decodes=io+mem,owns=io+mem,locks=none [0.243150] vgaarb: loaded [0.243152] vgaarb: bridge control possible :00:02.0 [2.766514] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 2336.771620] vgaarb: this pci device is not a vga device [ 2337.170566] vgaarb: this pci device is not a vga device [ 2415.373308] vgaarb: this pci device is not a vga device [ 2415.734668] vgaarb: this pci device is not a vga device $ uname -a Linux flat 3.19.0-26-generic #28-Ubuntu SMP Tue Aug 11 14:16:32 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux ** Changed in: linux (Ubuntu) Status: Expired = 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/1381175 Title: vgaarb module not patched Status in linux package in Ubuntu: Confirmed Bug description: Basically, vga cannot detect NVIDIA cards as VGA compatible controller, this is tested on a Optimus System. dmesg indicates that it's not a valid vga device: :~$ dmesg | grep vgaar [0.202410] vgaarb: device added: PCI::00:02.0,decodes=io+mem,owns=io+mem,locks=none [0.202413] vgaarb: loaded [0.202414] vgaarb: bridge control possible :00:02.0 [0.936062] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 532.414245] vgaarb: this pci device is not a vga device [ 533.778296] vgaarb: this pci device is not a vga device system:~$ uname -a Linux 3.16.0-10-generic #15-Ubuntu SMP Thu Aug 21 16:26:44 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux system:~$ lspci -nn 00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) 01:00.0 3D controller [0302]: NVIDIA Corporation GK208M [GeForce GT 735M] [10de:1291] (rev ff) According to this: https://github.com/Bumblebee-Project/Bumblebee/issues/159 it's look like the patch for vgaarb is not in 14.10 more info: https://bugzilla.kernel.org/show_bug.cgi?id=63641 previous patch is on: http://pastebin.com/wpmFi38k Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1381175/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1415880] Re: 14e4:4365 bcmwl-kernel source: fix for null pointer crash
So, It looks like there are 2 or 3 bugs together in this case (maybe ?). I probably solved just the bug where null pointer was being referenced (based on a a Debian Bug already solved). Martin, I need more information than this. The PPA I provided works with Trusty, Vivid and Wily with 3.13, 3.18 and 4.2 kernels. Can you test other kernels and provide feedback. Also, about the crash you are facing, can you attach the crash log ? Zethan, Are you using the same model (BCM43142) ? How come it is fixed (suspend) and the card does not work ? Please provide better feedback. Igor, Are you using the same model (BCM43142) ? Please keep me updated on status! Unfortunately to follow bcmwl development is not an easy task since they only provide .tar.gz sources (without any kind of versioning system). Hopefully with better feedback (logs ?) I might be able to track fixes in between released versions. Thank you Rafael -- 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/1415880 Title: 14e4:4365 bcmwl-kernel source: fix for null pointer crash Status in Dell Sputnik: Confirmed Status in bcmwl package in Ubuntu: In Progress Bug description: The bcmwl package as of now misses one patch for a bug that occurs with BCM43142 and possibly other broadcom chipsets that will look like random disconnects, poor wifi signal and kernel warnings, See also #1379524. Adding the patch is a fairly simple process: * put the patch file in /usr/src/bcmwl-6.30.223.248+bdcom/patches * add the following line to /usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf PATCH[7]=0014-null-pointer-crash.patch * run: /usr/lib/dkms/common.postinst bcmwl 6.30.223.248+bdcom /usr/share/bcmwl x86_64 $(uname -r) This has fixed the issue for me. Edit: I just wanted to add that I did not write the patch; I merely downloaded it from a paste that was linked from the respective AUR package. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 [modified: usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf] ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: LXDE Date: Thu Jan 29 13:15:17 2015 InstallationDate: Installed on 2015-01-26 (3 days ago) InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1415880/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1469829] Re: ppc64el should use 'deadline' as default io scheduler
** Also affects: linux-lts-utopic (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Utopic) Status: In Progress = Invalid ** Description changed: + [Impact] + Using cfq instead of deadline as the default io scheduler starves certain workloads and causes performance issues. In addition every other arch we build uses deadline as the default scheduler. + + [Fix] + Change the configuration to the following for ppc64el: + CONFIG_DEFAULT_DEADLINE=y + CONFIG_DEFAULT_IOSCHED=deadline + + [Test Case] + Boot and cat /sys/block/*/queue/scheduler to see if deadline is being used. + + -- + -- Problem Description -- Firestone system given to DASD group failed HTX overnight test with miscompare error. HTX mdt.hdbuster was running on secondary drive and failed about 12 hours into test HTX miscompare analysis: -== Device under test: /dev/sdb Stanza running: rule_3 miscompare offset: 0x40 Transfer size: Random Size LBA number: 0x70fc miscompare length: all the blocks in the transfer size *- STANZA 3: Creates number of threads twice the queue depth. Each thread -* *- doing 2 num_oper with RC operation with xfer size between 1 block -* *- to 256K.-* This miscompare shows read operation is unable to get the expected data from the disk. The re-read buffer also shows the same data as the first read operation. Since the first read and next re-read shows same data, there could be a write operation (of previous rule stanza to initialize disk with pattern 007 ) failure on the disk. The same miscompare behavior shows for all the blocks in the transfer size. /dev/sdb Jun 2 02:29:43 2015 err=03b6 sev=2 hxestorage === device name (/dev/sdb) rule_3_13 numopers= 2 loop= 767 blk=0x70fc len=89088 - min_blkno=0 max_blkno=0x74706daf, RANDOM access + min_blkno=0 max_blkno=0x74706daf, RANDOM access Seed Values= 37303, 290, 23235 Data Pattern Seed Values = 37303, 291, 23235 BWRC LBA fencepost Detail: th_nummin_lba max_lba status - 0 01c9be3ffR - 1 1d1c1b6c3a3836d7F - 2 3a3836d857545243F - 3 5754524474706dafF + 0 01c9be3ffR + 1 1d1c1b6c3a3836d7F + 2 3a3836d857545243F + 3 5754524474706dafF Miscompare at buffer offset 64 (0x40) === miscompare offset (0x40) (Flags: badsig=0; cksum=0x6) Maximum LBA = 0x74706daf wbuf (baseaddr 0x3ffe1c0e6600) b0ff rbuf (baseaddr 0x3ffe1c0fc400) 850100fc700200fd700300fe700400ff7005 Write buffer saved in /tmp/htxsdb.wbuf1 Read buffer saved in /tmp/htxsdb.rbuf1 Re-read fails compare at offset64; buffer saved in /tmp/htxsdb.rerd1 errno: 950(Unknown error 950) Asghar reproduced that HTX hang he is seeing. Looking in the kernel logs I see some messages from the kernel that there are user threads blocked on getting reads serviced. So likely HTX is seeing the same thing. I've asked Asghar to try using the deadline I/O scheduler rather than CFQ to see if that makes any difference. If that does not make any difference, the next thing to try is reducing the queue depth of the device. Right now its 31, which I think is pretty high. Step 1: echo deadline /sys/block/sda/queue/scheduler echo deadline /sys/block/sdb/queue/scheduler If that reproduces the issue, go to step 2: echo cfq /sys/block/sda/queue/scheduler echo cfq /sys/block/sdb/queue/scheduler echo 8 /sys/block/sda/device/queue_depth echo 8 /sys/block/sdb/device/queue_depth Breno - it looks like the default I/O scheduler + default queue depth for the SATA disks in Firestone is not optimal, in that when running a heavy I/O workload, we see read starvation occurring, which is making the system nearly unusable. Once we changed the I/O scheduler from cfq to deadline, all the issues went away and the system is able to run the same workload yet still be responsive. Suggest we either encourage Canonical to change the default I/O scheduler to deadline or at the very least provide documentation to encourage our customers to make this change themselves. ** Changed in: linux-lts-utopic (Ubuntu) Status: New = Invalid ** Changed in: linux-lts-utopic (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-utopic (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux (Ubuntu Trusty) Assignee: (unassigned) = Chris J Arges (arges) ** Changed in: linux (Ubuntu Vivid) Assignee: (unassigned) = Chris J Arges (arges) ** Changed in: linux-lts-utopic
[Kernel-packages] [Bug 1475166] Re: Ubuntu 15.04 Install Error with Avago Controller
Hi Adi, Just to confirm my understanding of this bug, did doing so change the value of max_sectors_kb / max_hw_sectors_kb? I don't believe it would have survived the reboot after the install, but you could try adding it to the kernel command line of the installed system and see. Bryan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1475166 Title: Ubuntu 15.04 Install Error with Avago Controller Status in linux package in Ubuntu: Triaged Bug description: Hello Canonical Team We are running to an issue installing ubuntu PPC64LE 15.04 full blown image on our servers (with RAID controller). Installation hangs around 70% of progress. An important part of our configuration is Avago RAID controller: 9361-8i Firmware version we used is 4.300.00-4429, and the package is 24.10.0-0002. IMPORTANT: It has to be noted that with same hardware configuration 14.10 full blown image installs fine. Dmesg logs are attached: Looking at dmesg logs point out that: LSI (avago) driver loads fine During further interaction with raid volume during the installation process, firmware errors are seen [ 196.991417] megasas: FW status 0x3 [ 196.999376] megasas: FW status 0x3 [ 197.007376] megasas: FW status 0x3 Further down the process I/O errors are thrown [ 217.438664] Buffer I/O error on device sda2, logical block 22052864 [ 217.438671] Buffer I/O error on device sda2, logical block 22052865 [ 217.438678] Buffer I/O error on device sda2, logical block 22052866 [ 217.438686] Buffer I/O error on device sda2, logical block 22052867 Full dmesg log is attached. Snippet is pasted below highlighting: It can be noted that there’s a Mellanox Connectx 3 pro card with some test Firmware on our setup. We can Ignore any diagnostic messages from that card in dmesg logs for the purpose of this bug. Thanks Adi Gangidi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1436940] Re: Atheros wifi 168c:0041(QCA6164) is not supported
hey, Thank God I ran into this thread!! I'm having the same issue with my wifi card. please excse my noob-ness. Diego, I tried following the directions you posted above but I'm still getting network unclaimmed :/ . Did I miss anything? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1436940 Title: Atheros wifi 168c:0041(QCA6164) is not supported Status in linux package in Ubuntu: Confirmed Status in linux source package in Vivid: Confirmed Status in linux source package in Wily: Confirmed Bug description: The atheros wireless device (168c:0041) isn't supported by the ath10k_pci kernel driver. Found in several laptop models: Lenovo Z70 Lenovo G50-45 Lenovo G50-80 Lenovo Edge 15 Lenovo Yoga 3 11 Lenovo Flex 3-1470 Samsung ATIV Book 9 NP930X2K ProblemType: BugDistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-9-generic 3.19.0-9.9 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicholas 1695 F pulseaudio /dev/snd/controlC1: nicholas 1695 F pulseaudio CurrentDesktop: Unity Date: Thu Mar 26 09:47:16 2015 HibernationDevice: RESUME=UUID=5b068cd8-e60a-49b9-a88e-1581bb6b3dc1 InstallationDate: Installed on 2015-03-25 (1 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 003: ID 5986:0652 Acer, Inc Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80E5 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=e52867c5-0b50-42fb-8288-f30765f926c5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-9-generic N/A linux-backports-modules-3.19.0-9-generic N/A linux-firmware1.143SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-03-26 (0 days ago) dmi.bios.date: 06/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: B0CN69WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo G50-80 dmi.board.vendor: LENOVO dmi.board.version: 31900058 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-80 dmi.modalias: dmi:bvnLENOVO:bvrB0CN69WW:bd06/20/2014:svnLENOVO:pn80E5:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoG50-80: dmi.product.name: 80E5 dmi.product.version: Lenovo G50-80 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1436940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1488842] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run: apport-collect 1488842 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/1488842 Title: Can't copy and paste more than 4kB into a terminal Status in linux package in Ubuntu: Incomplete Bug description: I am unable to copy and paste more than 4kB of script into a terminal (e.g. gnome-terminal, xterm). I have been encountering this issue for nearly a decade now (across multiple distributions, including Ubuntu 14.04 LTS). I believe it may relate to kernel parameter N_TTY_BUF_SIZE. A similar problem appears to have been reported here; http://comments.gmane.org/gmane.linux.kernel/1253720. Use case; 1. The user has a large semi-automated script (e.g. 2000 line deployment instructions.txt; which do not justify full automation*). 2. The user wishes to copy and paste one or more automated sections of the script into a terminal (e.g. gnome-terminal, xterm, etc) while following the self-contained instructions. 3. Those automated sections of the script may contain more than 4kB worth of data (spread across multiple lines) Actual behaviour; - the script being pasted into the terminal is corrupted, then executed Expected Behaviour; - the script is successfully pasted into the terminal, then executed I have reported this issue because it is not intuitive that the system should behave like this. While now that I know it may be a fundamental limitation of current (/prior) Linux kernels, I will ensure to work around it in future activity. However, it is feasible that someone else may encounter this issue before it is rectified. Every time this issue occurs there is a possibility of system corruption (depending on the precise script being copied to the terminal). Perhaps a patch has already been released? Or if this issue should be reported elsewhere, feel free to recommend an alternative forum. * e.g. because the self-contained instructions only need to be executed ~10 times across the product life cycle, taking into account the fact automation time is a function of a) how busy the user is / spare time they can devote to subsystems, and b) the level of robustness required: automatically editing files which may have been significantly updated between deployments is not necessarily safe. Cheers - Richard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1488842/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1482304] Re: Upgrade i40e and i40evf driver to latest
Antony - issues of this sort are meant to be solved with a backported kernel, e.g., linux-generic-lts-vivid. The next Trusty LTS ISO (14.04.3) will install this kernel by default. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1482304 Title: Upgrade i40e and i40evf driver to latest Status in linux package in Ubuntu: Confirmed Bug description: It appears that the latest i40e driver in Trusty is 0.3.36-k. We've been experiencing some kernel panics with this driver and have found that it looks like bringing the driver up to the latest 1.2.48 has alleviated some of the kernel panics on boot. Is this something we could look at getting upgraded to a more modern revision of the driver? Thanks Output of Panic (Using Intel x710) [3.143088] i40e :05:00.0 p1p1: NIC Link is Up [3.301138] Switched to clocksource tsc [6.216639] random: nonblocking pool is initialized [8.934783] [ cut here ] [8.934805] WARNING: CPU: 0 PID: 0 at /build/buildd/linux-3.13.0/net/sched/sch_generic.c:264 dev_watchdog+0x276/0x280() [8.934808] NETDEV WATCHDOG: p1p1 (i40e): transmit queue 0 timed out [8.934828] Modules linked in: joydev hid_generic gpio_ich x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd serio_raw usbhid hid lpc_ich hpilo ioatdma dca ipmi_si shpchp wmi acpi_power_meter mac_hid lp parport psmouse i40e vxlan ip_tunnel ptp hpsa pps_core [8.934874] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.13.0-57-generic #95-Ubuntu [8.934877] Hardware name: HP ProLiant DL380 Gen9, BIOS P89 05/06/2015 [8.934878] 0009 88103fc03d98 817232f0 88103fc03de0 [8.934891] 88103fc03dd0 8106784d 881028d18000 [8.934895] 881023734f40 0040 88103fc03e30 [8.934904] Call Trace: [8.934905] IRQ [817232f0] dump_stack+0x45/0x56 [8.934921] [8106784d] warn_slowpath_common+0x7d/0xa0 [8.934925] [810678bc] warn_slowpath_fmt+0x4c/0x50 [8.934928] [816479d6] dev_watchdog+0x276/0x280 [8.934935] [81647760] ? dev_graft_qdisc+0x80/0x80 [8.934942] [810744e6] call_timer_fn+0x36/0x100 [8.934946] [81647760] ? dev_graft_qdisc+0x80/0x80 [8.934950] [8107547f] run_timer_softirq+0x1ef/0x2f0 [8.934957] [8106ccbc] __do_softirq+0xec/0x2c0 [8.934961] [8106d205] irq_exit+0x105/0x110 [8.934971] [81736195] smp_apic_timer_interrupt+0x45/0x60 [8.934976] [81734b1d] apic_timer_interrupt+0x6d/0x80 [8.934977] EOI [815d55d2] ? cpuidle_enter_state+0x52/0xc0 [8.934986] [815d56f9] cpuidle_idle_call+0xb9/0x1f0 [8.934994] [8101d3ee] arch_cpu_idle+0xe/0x30 [8.935000] [810bf205] cpu_startup_entry+0xc5/0x290 [8.935008] [817114f7] rest_init+0x77/0x80 [8.935016] [81d34f70] start_kernel+0x438/0x443 [8.935021] [81d34941] ? repair_env_string+0x5c/0x5c [8.935023] [81d34120] ? early_idt_handlers+0x120/0x120 [8.935027] [81d345ee] x86_64_start_reservations+0x2a/0x2c [8.935030] [81d34733] x86_64_start_kernel+0x143/0x152 [8.935034] ---[ end trace fabec2b76d314b12 ]--- [8.935037] i40e :05:00.0 p1p1: tx_timeout recovery level 0 [8.935071] i40e :05:00.0: VSI reinit requested [8.945435] i40e :05:00.0 p1p1: NIC Link is Up [ 14.856689] i40e :05:00.0: Detected Tx Unit Hang [ 14.856689] VSI 518 [ 14.856689] Tx Queue 0 [ 14.856689] next_to_use 1 [ 14.856689] next_to_clean0 [ 14.856697] i40e :05:00.0: tx_bi[next_to_clean] [ 14.856697] time_stamp fffee736 [ 14.856697] jiffies fffee971 [ 14.856699] i40e :05:00.0: tx hang detected on queue 0, resetting adapter [ 14.856701] i40e :05:00.0 p1p1: tx_timeout recovery level 1 [ 14.882582] i40e :05:00.0: i40e_ptp_init: added PHC on p1p1 [ 14.899577] i40e :05:00.0 p1p1: NIC Link is Up [ 14.899623] i40e :05:00.0: reset complete [ 24.928762] i40e :05:00.0 p1p1: tx_timeout recovery level 2 [ 25.876839] i40e :05:00.1: i40e_ptp_init: added PHC on p1p2 [ 25.889067] i40e :05:00.1: reset complete [ 25.917938] i40e :05:00.0: i40e_ptp_init: added PHC on p1p1 [ 25.934578] i40e :05:00.0 p1p1: NIC Link is Up [ 25.934621] i40e :05:00.0: reset complete To manage notifications about this bug go to:
[Kernel-packages] [Bug 1488495] Re: NX842 fixes for Ubuntu 15.10
** Also affects: linux (Ubuntu Wily)
Importance: High
Assignee: Canonical Kernel Team (canonical-kernel-team)
Status: Triaged
** Changed in: linux (Ubuntu Wily)
Status: Triaged = In Progress
** Changed in: linux (Ubuntu Wily)
Assignee: Canonical Kernel Team (canonical-kernel-team) = Tim Gardner
(timg-tpi)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1488495
Title:
NX842 fixes for Ubuntu 15.10
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Wily:
In Progress
Bug description:
---Problem Description---
There are actually some more NX 842 patches that should be in the 4.3 kernel.
They're currently all in Herbert's tree:
git://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git
In the usual descending order:
03952d9 crypto: nx - make platform drivers directly register with crypto
174d66d crypto: nx - rename nx-842-crypto.c to nx-842.c
d31581a crypto: nx - merge nx-compress and nx-compress-crypto
20fc311 crypto: nx - use common code for both NX decompress success cases
ee781b7 crypto: nx - don't register pSeries driver if ENODEV
7f6e3aa crypto: nx - move kzalloc() out of spinlock
90fd73f crypto: nx - remove pSeries NX 'status' field
039af96 crypto: nx - remove __init/__exit from VIO functions
23ad69a crypto: nx/842 - Fix context corruption
2b93f7e crypto: nx - reduce chattiness of platform drivers
7abd75b crypto: nx - do not emit extra output if status is disabled
ec13bcb crypto: nx - rename nx842_{init, exit} to nx842_pseries_{init, exit}
fa9a9a0 crypto: nx - nx842_OF_upd_status should return ENODEV if device is
not 'okay'
---uname output---
Ubuntu 15.10
Machine Type = power 8
I am working on back-port these patches and will be providing them early next
week. These patches fix several bugs in nx842 code.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1488495/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1467561] Re: IPsec VTI functionality broken in 3.16.0-39
Someone on the Strongswan mailing list [1] mentioned that 3.19 was also affected. I quickly skimmed the changelog between 3.16.0-38-generic to 3.16.0-39-generic and a possible culprit could be: * ip_forward: Drop frames with attached skb-sk Clemens, would you be able to just revert the corresponding commit and see it if helps? 1: https://lists.strongswan.org/pipermail/users/2015-August/008644.html ** Changed in: linux (Ubuntu) Status: Expired = 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/1467561 Title: IPsec VTI functionality broken in 3.16.0-39 Status in linux package in Ubuntu: Incomplete Bug description: Gentlepeople - this is my very first bug-report to/about Ubuntu, so please forgive any failings regarding form on my side! After upgrading from 3.16.0-38-generic to 3.16.0-39-generic I noticed a number of my IPsec VTIs were no longer working: All crypto parts appear to work fine (I can run tcpdump on the VTIs and I correct cleartext-packets in both directions), but incoming packets are not being processed further (they are simply ignored). It is like there is no IP stack listening on the inbound end of the VTI. I can ping devices on the other side and do see the packets w/ tcpdump/wireshark all over the place (locally, remote-router, remote-device), the targets respond and I again see the packets all the way, but the ping application pretends it never heard or saw a thing. This is true for all VTIs, except those where I put complicated mangle and nat rules in place in order to overcome address-space collisions (damn RFC1918, damn, damn, damn!!!) - but then again source-NAT (masquerading) no longer works on these VTIs either. I tested around by leaving *everything* (StrongSwan config, etc.) the same and only switching kernels and 3.16.0-38 ist the last one fully working and everything after and including 3.16.0-39 is broken in the way described above. I am willing to test further and dig deeper unless you tell me that it is a known problem with an upcoming fix ... :-) Thanks, Clemens ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-39-generic (not installed) ProcVersionSignature: Ubuntu 3.16.0-38.52-generic 3.16.7-ckt10 Uname: Linux 3.16.0-38-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.7-0ubuntu8.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Mon Jun 22 16:48:33 2015 HibernationDevice: RESUME=UUID=e0eb93cf-68f6-4c6b-b4f1-288db4b33df2 InstallationDate: Installed on 2015-02-15 (126 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.3) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/usr/bin/tcsh ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-38-generic root=UUID=bb995ded-003a-4ae3-aa21-0cf188bdba17 ro RelatedPackageVersions: linux-restricted-modules-3.16.0-38-generic N/A linux-backports-modules-3.16.0-38-generic N/A linux-firmware 1.138.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2015-02-15 (126 days ago) dmi.bios.date: 01/01/2011 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-trusty:cvnBochs:ct1:cvr: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-trusty dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1467561/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1487734] [NEW] Battery Absent On HP Split 13x2 Laptop
You have been subscribed to a public bug: I have an HP Split 13x2 laptop with Ubuntu Mate installed. dmesg shows ACPI: Battery Slot [BAT0] (battery absent). The battery icon shows No battery present. ...I'm only able to run on AC power. --- I have tried: * Default and adjusted settings in BIOS. * Live versions of Ubuntu, Lubuntu and Ubuntu Mate. * Release 15.04 and 14.04 for all flavors above. * Installed ACPI. * Installed batmon. * Installed ibam. * Added to grub default boot line acpi_osi=, then acpi_osi=!Linux then acpi_osi=Linux. I have not tried recompiling the kernel, as several posts state the recompiling didn't work for them if not on a Toshiba. --- I'd really like to get this working...the laptop is needed for work done in areas where AC power won't always be present. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Battery Absent On HP Split 13x2 Laptop https://bugs.launchpad.net/bugs/1487734 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1429250] Re: crash cannot find stack info on ppc64le
This bug was fixed in the package crash - 7.0.3-3ubuntu4.3 --- crash (7.0.3-3ubuntu4.3) trusty; urgency=medium * Fix-for-the-PPC64-bt-command-on-both-big-endian-and-.patch (LP: #1429250) * Remove extraneous patch: 0001-Implemented-support-for-the-ARM64-bt-l-option.patch -- Chris J Arges chris.j.ar...@canonical.com Mon, 10 Aug 2015 16:44:48 -0500 ** Changed in: crash (Ubuntu Trusty) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1429250 Title: crash cannot find stack info on ppc64le Status in crash package in Ubuntu: Fix Released Status in crash source package in Trusty: Fix Released Bug description: SRU Justification [Impact] crash's sub-command cannot show stack frame of active tasks on ppc64le systems. [Test Case] 1. capturing a vmcore by kdump on ppc64le system 2. issuing crash with this vmcore 3. run 'bt' in crash 4. no stack frame displaied [Fix] https://github.com/crash-utility/crash/commit/dc4ea682a21567dd9d093862ec54eb8529199c05 [Regression potential] This is easily testable and only affects ppc64le systems. This has already been backported to vivid without issue. -- Problem Description = crash's sub-command cannot show stack frame of active tasks on ppc64le systems. Please see https://www.redhat.com/archives/crash- utility/2015-January/msg00033.html for details. Contact Information = Ping Tian Han/pt...@cn.ibm.com, Mikhail Afanasiev/afana...@us.ibm.com ---uname output--- Linux thymelp2.isst.aus.stglabs.ibm.com 3.10.0-221.ael7b.ppc64le #1 SMP Wed Jan 7 09:27:09 EST 2015 ppc64le ppc64le ppc64le GNU/Linux Machine Type = CHRP IBM,8247-22L lpar Steps to Reproduce = 1. capturing a vmcore by kdump on ppc64le system 2. issuing crash with this vmcore 3. run 'bt' in crash 4. no stack frame displaied Userspace tool common name: crash The userspace tool has the following bit modes: 64-bit Userspace rpm: crash-7.0.9-2.ael7b.ppc64le == Comment: #5 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-02-06 13:18:18 == For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari == Comment: #6 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-02-20 00:08:46 == (In reply to comment #5) (In reply to comment #4) Any update? For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/ dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari I would suggest, we close this bug as the issue reported is resolved with the below patch https://github.com/crash-utility/crash/commit/dc4ea682a21567dd9d093862ec54eb8529199c05 We could track the problem with first method offline or in a separate bug if needed. Thanks Hari == Comment: #10 - Breno Henrique Leitao bren...@br.ibm.com - 2015-03-02 15:42:05 == Canonical, Can we move Crash to versin 7.1.0 that already contains this fix? Thanks. == Comment: #11 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-03-05 23:18:17 == (In reply to comment #6) (In reply to comment #5) (In reply to comment #4) Any update? For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/ dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari I would suggest, we close this bug as the issue reported is resolved with the below patch
[Kernel-packages] [Bug 1284093] Update Released
The verification of the Stable Release Update for wireless-regdb has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1284093 Title: Please update regulations to support VHT Status in wireless-regdb package in Ubuntu: Fix Released Status in wireless-regdb source package in Vivid: Fix Released Status in wireless-regdb source package in Wily: Fix Released Bug description: Only very recent versions of wireless-regdb have support for VHT (80mhz channels); in addition, all current kernels have a bug that will cause your card to fail to associate with a VHT ap when your local regdb didn't allow VHT: https://bugzilla.kernel.org/show_bug.cgi?id=70881 I have updated the existing Debian bug requesting this too: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729089 Well, more precisely I have emailed the update but it hasn't gone through yet. :) I would recommend updating to 2013.11.27 (current upstream) as it includes other regulatory fixes. I would also recommend applying this to at least Precise and Trusty, possibly Saucy since it is still supported. Here is the update that should post to the Debian bug soon: I would much appreciate this, especially you make the jump to 2013.11.27. The new regdb will also solve issues with 802.11ac; the referenced version appears to be the first with support for 80mhz channels. Without the new regdb (or a patch the kernel that masks the symptoms, below), when you connect to an AP that supports 80mhz channels, you are disconnected with a nearly useless error. Link to the ticket, with details and the symptom-masking patch that will be in future kernels: https://bugzilla.kernel.org/show_bug.cgi?id=70881 It would be great if we could get the new regdb upstream into Debian asap; in the meantime I will try to get an updated version into a ppa for Ubuntu users at least. ;) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1284093/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1487734] Re: Battery Absent On HP Split 13x2 Laptop
** Package changed: ubuntu = linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1487734 Title: Battery Absent On HP Split 13x2 Laptop Status in linux package in Ubuntu: New Bug description: I have an HP Split 13x2 laptop with Ubuntu Mate installed. dmesg shows ACPI: Battery Slot [BAT0] (battery absent). The battery icon shows No battery present. ...I'm only able to run on AC power. --- I have tried: * Default and adjusted settings in BIOS. * Live versions of Ubuntu, Lubuntu and Ubuntu Mate. * Release 15.04 and 14.04 for all flavors above. * Installed ACPI. * Installed batmon. * Installed ibam. * Added to grub default boot line acpi_osi=, then acpi_osi=!Linux then acpi_osi=Linux. I have not tried recompiling the kernel, as several posts state the recompiling didn't work for them if not on a Toshiba. --- I'd really like to get this working...the laptop is needed for work done in areas where AC power won't always be present. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1487734/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1477171] Re: Enable intel_pstate by default on Trusty EC2 AMIs
** Changed in: linux (Ubuntu) Status: Confirmed = In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) = Colin Ian King (colin-king) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1477171 Title: Enable intel_pstate by default on Trusty EC2 AMIs Status in linux package in Ubuntu: In Progress Bug description: Please can the intel_pstate driver be enabled by default on the Ubuntu EC2 AMIs. On instances with support for C-states and P-States [1] there is a notable performance impact and lack of support for higher clock frequencies available due to the use of the acpi-cpufreq driver. For example on a c4.8xlarge the default frequency is limited to 2.9GHz when 3.2GHz is supported by the chip [2]. Some additional analysis is available here [3] and re-enabling it by default has been discussed [4] but this request is specifically for the EC2 AMIs. [1] http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/processor_state_control.html [2] http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/c4-instances.html [3] http://www.deplication.net/2015/07/c-states-and-p-states-with-ubuntu-1404.html [4] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1188647 AMI: ami-47a23a30 (eu-west-1) $ lsb_release -d Description:Ubuntu 14.04.2 LTS $ uname -a Linux ip-172-31-8-218 3.13.0-57-generic #95-Ubuntu SMP Fri Jun 19 09:28:15 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Default configuration (c4.8xl): $ sudo cpupower frequency-info analyzing CPU 0: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 10.0 us. hardware limits: 1.20 GHz - 2.90 GHz available frequency steps: 2.90 GHz, 2.90 GHz, 2.80 GHz, 2.70 GHz, 2.50 GHz, 2.40 GHz, 2.30 GHz, 2.20 GHz, 2.00 GHz, 1.90 GHz, 1.80 GHz, 1.70 GHz, 1.60 GHz, 1.40 GHz, 1.30 GHz, 1.20 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 1.20 GHz and 2.90 GHz. The governor ondemand may decide which speed to use within this range. current CPU frequency is 1.20 GHz (asserted by call to hardware). cpufreq stats: 2.90 GHz:70.40%, 2.90 GHz:0.00%, 2.80 GHz:0.00%, 2.70 GHz:0.00%, 2.50 GHz:0.00%, 2.40 GHz:0.00%, 2.30 GHz:0.00%, 2.20 GHz:0.00%, 2.00 GHz:0.00%, 1.90 GHz:0.00%, 1.80 GHz:0.00%, 1.70 GHz:0.00%, 1.60 GHz:0.09%, 1.40 GHz:0.00%, 1.30 GHz:0.00%, 1.20 GHz:29.51% (5) boost state support: Supported: yes Active: yes With intel_pstate enabled (c4.8xl): $ sudo cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 0.97 ms. hardware limits: 1.20 GHz - 3.50 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 1.20 GHz and 3.50 GHz. The governor performance may decide which speed to use within this range. current CPU frequency is 3.20 GHz (asserted by call to hardware). boost state support: Supported: yes Active: yes --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 12 17:19 seq crw-rw 1 root audio 116, 33 Aug 12 17:19 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [39221.196411] init: plymouth-upstart-bridge main process ended, respawning DistroRelease: Ubuntu 14.04 Ec2AMI: ami-47a23a30 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1b Ec2InstanceType: c4.8xlarge Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Xen HVM domU Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-61-generic root=UUID=877c5daf-9427-49e3-8656-437c3f30fc84 ro console=tty1 console=ttyS0 ProcVersionSignature: User Name 3.13.0-61.100-generic 3.13.11-ckt22 RelatedPackageVersions: linux-restricted-modules-3.13.0-61-generic N/A linux-backports-modules-3.13.0-61-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such
[Kernel-packages] [Bug 1487919] Re: macbookrpro12, 1 fails to suspend
possibly related upstream bugs: https://bugzilla.kernel.org/show_bug.cgi?id=101681 https://bugzilla.kernel.org/show_bug.cgi?id=103211 ** Bug watch added: Linux Kernel Bug Tracker #101681 http://bugzilla.kernel.org/show_bug.cgi?id=101681 ** Bug watch added: Linux Kernel Bug Tracker #103211 http://bugzilla.kernel.org/show_bug.cgi?id=103211 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1487919 Title: macbookrpro12,1 fails to suspend Status in linux package in Ubuntu: Confirmed Bug description: I've installed wily on a new macbookpro12,1 (2015 model), and suspending the system results in the screen going black and the apple light turning off, but the system is not fully asleep -- the 'force touch' pad still makes clicking feedback, and the machine continues to generate heat and spin fans if put into a bag. Once in this state, the machine cannot be woken up from the state its in either. did a journalctl -f | tee sleep.log' while this was happening and got the following output -- let me know if there is a better way to figure out where things are going wrong: Aug 23 15:13:21 spiny NetworkManager[820]: info sleep requested (sleeping: no enabled: yes) Aug 23 15:13:21 spiny NetworkManager[820]: info sleeping... Aug 23 15:13:21 spiny NetworkManager[820]: info (wlp3s0): device state change: activated - unmanaged (reason 'sleeping') [100 10 37] Aug 23 15:13:21 spiny NetworkManager[820]: info (wlp3s0): deactivating device (reason 'sleeping') [37] Aug 23 15:13:21 spiny NetworkManager[820]: info (wlp3s0): canceled DHCP transaction, DHCP client pid 925 Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for 2601:1c0:4d00:39e6:f912:fbb6:aaa6:4429 on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for 2601:1c0:4d00:39e6:290:4cff:fe0d:f43e on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Leaving mDNS multicast group on interface wlp3s0.IPv6 with address 2601:1c0:4d00:39e6:290:4cff:fe0d:f43e. Aug 23 15:13:21 spiny avahi-daemon[826]: Joining mDNS multicast group on interface wlp3s0.IPv6 with address fe80::290:4cff:fe0d:f43e. Aug 23 15:13:21 spiny avahi-daemon[826]: Registering new address record for fe80::290:4cff:fe0d:f43e on wlp3s0.*. Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for fe80::290:4cff:fe0d:f43e on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Leaving mDNS multicast group on interface wlp3s0.IPv6 with address fe80::290:4cff:fe0d:f43e. Aug 23 15:13:21 spiny avahi-daemon[826]: Interface wlp3s0.IPv6 no longer relevant for mDNS. Aug 23 15:13:21 spiny wpa_supplicant[891]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=10:c3:7b:c5:83:d8 reason=3 locally_generated=1 Aug 23 15:13:21 spiny wpa_supplicant[891]: nl80211: Was expecting local disconnect but got another disconnect event first Aug 23 15:13:21 spiny avahi-daemon[826]: Withdrawing address record for 192.168.1.83 on wlp3s0. Aug 23 15:13:21 spiny avahi-daemon[826]: Leaving mDNS multicast group on interface wlp3s0.IPv4 with address 192.168.1.83. Aug 23 15:13:21 spiny avahi-daemon[826]: Interface wlp3s0.IPv4 no longer relevant for mDNS. Aug 23 15:13:21 spiny kernel: cfg80211: Calling CRDA to update world regulatory domain Aug 23 15:13:21 spiny NetworkManager[820]: info Writing DNS information to /sbin/resolvconf Aug 23 15:13:21 spiny dnsmasq[928]: setting upstream servers from DBus Aug 23 15:13:21 spiny dnsmasq[928]: using nameserver 2601:1c0:4d00:39e6::1#53 Aug 23 15:13:21 spiny dbus[806]: [system] Rejected send message, 10 matched rules; type=method_return, sender=:1.22 (uid=0 pid=928 comm=/usr/sbin/dnsmasq --no-resolv --keep-in-foreground) interface=(unset) member=(unset) error name=(unset) requested_reply=0 destination=:1.6 (uid=0 pid=820 comm=/usr/sbin/NetworkManager --no-daemon ) Aug 23 15:13:21 spiny wpa_supplicant[891]: p2p-dev-wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Aug 23 15:13:21 spiny NetworkManager[820]: info Writing DNS information to /sbin/resolvconf Aug 23 15:13:21 spiny kernel: brcmf_cfg80211_reg_notifier: not a ISO3166 code Aug 23 15:13:21 spiny kernel: cfg80211: World regulatory domain updated: Aug 23 15:13:21 spiny kernel: cfg80211: DFS Master region: unset Aug 23 15:13:21 spiny kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) Aug 23 15:13:21 spiny kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21 spiny kernel: cfg80211: (517 KHz - 525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A) Aug 23 15:13:21
[Kernel-packages] [Bug 1429250] Update Released
The verification of the Stable Release Update for crash has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1429250 Title: crash cannot find stack info on ppc64le Status in crash package in Ubuntu: Fix Released Status in crash source package in Trusty: Fix Released Bug description: SRU Justification [Impact] crash's sub-command cannot show stack frame of active tasks on ppc64le systems. [Test Case] 1. capturing a vmcore by kdump on ppc64le system 2. issuing crash with this vmcore 3. run 'bt' in crash 4. no stack frame displaied [Fix] https://github.com/crash-utility/crash/commit/dc4ea682a21567dd9d093862ec54eb8529199c05 [Regression potential] This is easily testable and only affects ppc64le systems. This has already been backported to vivid without issue. -- Problem Description = crash's sub-command cannot show stack frame of active tasks on ppc64le systems. Please see https://www.redhat.com/archives/crash- utility/2015-January/msg00033.html for details. Contact Information = Ping Tian Han/pt...@cn.ibm.com, Mikhail Afanasiev/afana...@us.ibm.com ---uname output--- Linux thymelp2.isst.aus.stglabs.ibm.com 3.10.0-221.ael7b.ppc64le #1 SMP Wed Jan 7 09:27:09 EST 2015 ppc64le ppc64le ppc64le GNU/Linux Machine Type = CHRP IBM,8247-22L lpar Steps to Reproduce = 1. capturing a vmcore by kdump on ppc64le system 2. issuing crash with this vmcore 3. run 'bt' in crash 4. no stack frame displaied Userspace tool common name: crash The userspace tool has the following bit modes: 64-bit Userspace rpm: crash-7.0.9-2.ael7b.ppc64le == Comment: #5 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-02-06 13:18:18 == For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari == Comment: #6 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-02-20 00:08:46 == (In reply to comment #5) (In reply to comment #4) Any update? For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/ dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari I would suggest, we close this bug as the issue reported is resolved with the below patch https://github.com/crash-utility/crash/commit/dc4ea682a21567dd9d093862ec54eb8529199c05 We could track the problem with first method offline or in a separate bug if needed. Thanks Hari == Comment: #10 - Breno Henrique Leitao bren...@br.ibm.com - 2015-03-02 15:42:05 == Canonical, Can we move Crash to versin 7.1.0 that already contains this fix? Thanks. == Comment: #11 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-03-05 23:18:17 == (In reply to comment #6) (In reply to comment #5) (In reply to comment #4) Any update? For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/ dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari I would suggest, we close this bug as the issue reported is resolved with the below patch
[Kernel-packages] [Bug 1284093] Re: Please update regulations to support VHT
This bug was fixed in the package wireless-regdb - 2014.11.18-1ubuntu1~ubuntu15.04.1 --- wireless-regdb (2014.11.18-1ubuntu1~ubuntu15.04.1) vivid; urgency=medium * Vivid SRU LP: #1284093 -- Jonathan Riddell jridd...@ubuntu.com Fri, 12 Jun 2015 07:02:48 +0200 ** Changed in: wireless-regdb (Ubuntu Vivid) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1284093 Title: Please update regulations to support VHT Status in wireless-regdb package in Ubuntu: Fix Released Status in wireless-regdb source package in Vivid: Fix Released Status in wireless-regdb source package in Wily: Fix Released Bug description: Only very recent versions of wireless-regdb have support for VHT (80mhz channels); in addition, all current kernels have a bug that will cause your card to fail to associate with a VHT ap when your local regdb didn't allow VHT: https://bugzilla.kernel.org/show_bug.cgi?id=70881 I have updated the existing Debian bug requesting this too: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729089 Well, more precisely I have emailed the update but it hasn't gone through yet. :) I would recommend updating to 2013.11.27 (current upstream) as it includes other regulatory fixes. I would also recommend applying this to at least Precise and Trusty, possibly Saucy since it is still supported. Here is the update that should post to the Debian bug soon: I would much appreciate this, especially you make the jump to 2013.11.27. The new regdb will also solve issues with 802.11ac; the referenced version appears to be the first with support for 80mhz channels. Without the new regdb (or a patch the kernel that masks the symptoms, below), when you connect to an AP that supports 80mhz channels, you are disconnected with a nearly useless error. Link to the ticket, with details and the symptom-masking patch that will be in future kernels: https://bugzilla.kernel.org/show_bug.cgi?id=70881 It would be great if we could get the new regdb upstream into Debian asap; in the meantime I will try to get an updated version into a ppa for Ubuntu users at least. ;) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1284093/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1310800] Re: 056a:0302 Trusty Tahr, kernel 3.13: automatic load of wacom.ko driver cause a hard kernel panic
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1310800 Title: 056a:0302 Trusty Tahr, kernel 3.13: automatic load of wacom.ko driver cause a hard kernel panic Status in linux package in Ubuntu: Confirmed Bug description: I have just upgraded to 14.04 from 13.10. I have a wacom cth-480 touch+pen tablet, which was not recognized on 13.10 (kernel 3.11). With the stock kernel from 14.04, I have an immediate kernel panic as soon as I plug in the tablet to the laptop. The system is a asus 1005PE (32 bit install), Xubuntu, up-to date: Linux asus-romano 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:08:14 UTC 2014 i686 i686 i686 GNU/Linux The really strange thing is that if I manually load the driver with `sudo modprobe wacom` *before* pluggin the tablet in, then the tablet is recognized and works ok: SYS: Apr 21 15:15:47 asus-romano kernel: [ 265.664161] usbcore: registered new interface driver wacom SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.088161] usb 2-1: new full-speed USB device number 2 using uhci_hcd SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253626] usb 2-1: New USB device found, idVendor=056a, idProduct=0302 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253641] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253651] usb 2-1: Product: Intuos PTS SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253659] usb 2-1: Manufacturer: Wacom Co.,Ltd. SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.257027] input: Wacom Intuos PT S Pen as /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.0/input/input14 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.260630] input: Wacom Intuos PT S Finger as /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.1/input/input15 SYS: Apr 21 15:15:52 asus-romano mtp-probe: checking bus 2, device 2: /sys/devices/pci:00/:00:1d.0/usb2/2-1 SYS: Apr 21 15:15:52 asus-romano mtp-probe: bus: 2, device: 2 was not an MTP device A screenshot of the kernel panic is added. I can reproduce it at will. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310800/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1412602] Re: No live DE in Vivid using nouveau w/GeForce 7025/nForce 630a
** Changed in: linux (Ubuntu) Status: Confirmed = Fix Released ** Changed in: linux (Ubuntu Trusty) Status: Confirmed = Fix Released ** Changed in: linux (Ubuntu Utopic) Status: Confirmed = Fix Released ** Changed in: linux (Ubuntu Vivid) Status: Confirmed = Fix Released ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Status: New = Fix Released ** Changed in: xserver-xorg-video-nouveau (Ubuntu Trusty) Status: New = Fix Released ** Changed in: xserver-xorg-video-nouveau (Ubuntu Utopic) Status: New = Fix Released ** Changed in: xserver-xorg-video-nouveau (Ubuntu Vivid) 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/1412602 Title: No live DE in Vivid using nouveau w/GeForce 7025/nForce 630a Status in Nouveau Xorg driver: Unknown Status in linux package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Released Status in xserver-xorg-video-nouveau source package in Trusty: Fix Released Status in linux source package in Utopic: Fix Released Status in xserver-xorg-video-nouveau source package in Utopic: Fix Released Status in linux source package in Vivid: Fix Released Status in xserver-xorg-video-nouveau source package in Vivid: Fix Released Bug description: I've been testing the Ubuntu GNOME Vivid daily images in anticipation of Alpha 2 and I noticed that with this specific hardware I get no graphics at all other than a blank screen (see attached photo): AMD Sempron Processor LE-1250 @ 2.2 GHz nVidia C61 [GeForce 7025 / nForce 630a] (rev a2) nVidia MCP61 High Definition Audio (rev a2) nVidia MCP61 Ethernet (rev a2) 2GB DDR2 RAM In fact I never even get as far as the screen offering to Try or Install, but I can enter the Advanced Boot Options screen and select either Try or Install from there, but with both options I still get the same blank screen. Further testing reveals the same results with Ubuntu and Ubuntu GNOME but I found that both the Xubuntu and Lubuntu images will boot properly on this box so I installed Lubuntu and then installed the ubuntu-desktop, ubuntu-gnome-desktop, and gnome-session-flashback meta-packages just to try some things. After doing so I found that the Unity, GNOME Shell, Gnome Classic, and Flashback w/Compiz sessions produce broken graphics just as the Ubuntu GNOME and Ubuntu live images do. So basically Compiz and Mutter both fail to display any usable UI. OTOH both the Lubuntu and Flashback w/Metacity sessions work just fine. I next opened the Additional drivers UI and chose nvidia-304.125 (current) and all DE's perform quite well with the proprietary drivers so I deduced that nouveau might be the culprit. The last known working Ubuntu and Ubuntu GNOME live images are 14.04.1. I hadn't tried Utopic on this box yet but it's also a fail. I'll try the proposed 14.04.2 images ASAP (probably after Vivid Alpha 2 is released). But I see no point in trying to fix this for Utopic (or even 14.04.2 if it's effected) because of the 9 month life-cycle for Utopic and the continued availability of the 14.04.1 images. In fact I'd be cool with this not being fixed until 16.04 as long as it's documented so people know what versions will and will not work. I'm probably forgetting something but that's all I can think of ATM. Sorry in advance if I did this totally wrong. ### Additional workaround and debug info ### The focus of this bug report is limited to screen corruption and X-freezes that either prevent the installation of Ubuntu (or other flavors) and/or booting the installed system even long enough to enable the third party nvidia driver. There are almost certainly other instances of screen corruption and hard (or soft) lockups that may also be related to the nouveau driver but those are beyond the scope of this specific bug report. To workaround this bug, or to see if you're affected by it you can boot using this boot parameter: nouveau.config=NvMSI=0 You'll find general instructions for using custom boot parameters at these links: https://help.ubuntu.com/community/BootOptions https://wiki.ubuntu.com/Kernel/KernelBootParameters In addition to what's said at the latter link about temporarily adding a kernel boot parameter to an installed system; after using the arrow keys to navigate to the line beginning with linux /boot you'll notice that line ends with quiet splash $vt_handoff. The boot parameter belongs between the quiet splash and $vt_handoff like this: quiet splash nouveau.config=NvMSI=0 $vt_handoff ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 ProcVersionSignature: Ubuntu
[Kernel-packages] [Bug 1016299] Re: CVE-2012-2372
** Description changed: The rds_ib_xmit function in net/rds/ib_send.c in the Reliable Datagram - Sockets (RDS) protocol implementation in the Linux kernel 3.7.4 and earlier - allows local users to cause a denial of service (BUG_ON and kernel panic) - by establishing an RDS connection with the source IP address equal to the - IPoIB interface's own IP address, as demonstrated by rds-ping. + Sockets (RDS) protocol implementation in the Linux kernel 3.7.4 and + earlier allows local users to cause a denial of service (BUG_ON and + kernel panic) by establishing an RDS connection with the source IP + address equal to the IPoIB interface's own IP address, as demonstrated + by rds-ping. Break-Fix: 639b321b4d8f4e412bfbb2a4a19bfebc1e68ace4 local-2012-2372 -- 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/1016299 Title: CVE-2012-2372 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: Invalid Status in linux-lts-backport-natty package in Ubuntu: Invalid Status in linux-lts-backport-oneiric 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-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Invalid Status in linux-lts-backport-natty source package in Lucid: Fix Released Status in linux-lts-backport-oneiric source package in Lucid: Fix Released Status in linux-lts-backport-maverick source package in Natty: Invalid Status in linux-lts-backport-natty source package in Natty: Invalid Status in linux-lts-backport-oneiric source package in Natty: Invalid Status in linux-lts-backport-maverick source package in Oneiric: Invalid Status in linux-lts-backport-natty source package in Oneiric: Invalid Status in linux-lts-backport-oneiric source package in Oneiric: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: Invalid Status in linux-lts-backport-natty source package in Precise: Invalid Status in linux-lts-backport-oneiric source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux-lts-backport-maverick source package in Quantal: Invalid Status in linux-lts-backport-natty source package in Quantal: Invalid Status in linux-lts-backport-oneiric source package in Quantal: Invalid Status in linux-lts-backport-maverick source package in Saucy: Won't Fix Status in linux-lts-backport-natty source package in Saucy: Won't Fix Status in linux-lts-backport-oneiric source package in Saucy: Won't Fix Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: Won't Fix Status in linux-lts-backport-natty source package in Trusty: Won't Fix Status in linux-lts-backport-oneiric source package in Trusty: Won't Fix Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty:
[Kernel-packages] [Bug 1384297] Re: After system resume, Intel i915 graphics hangs
I'm also having this issue on a new Lenovo X1 Carbon generation 3 (model 20BS CT01 WW). The screen will go black at random intervals and a similar stacktrace is produced on dmesg. Switching to a TTY and back (ctrl+alt+F1 and then back to ctrl+alt+f7, for example) returns to a functional Xorg. This is on Ubuntu trusty 14.04.3 LTS and 3.16.0-46-generic #62~14.04.1-Ubuntu. dmesg output example: [32612.021698] [ cut here ] [32612.021722] WARNING: CPU: 0 PID: 1271 at /build/linux-lts-utopic-ZOOBEH/linux-lts-utopic-3.16.0/drivers/gpu/drm/i915/intel_pm.c:5940 intel_display_power_put+0x11d/0x160 [i915]() [32612.021724] Modules linked in: hid_microsoft usbhid hid uas usb_storage ctr ccm btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core btusb v4l2_common videodev media msr acpi_call(OE) dm_crypt intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel arc4 aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd rfcomm snd_hda_codec_realtek snd_hda_codec_generic iwlmvm bnep mac80211 snd_hda_codec_hdmi bluetooth joydev serio_raw 6lowpan_iphc thinkpad_acpi snd_seq_midi snd_seq_midi_event nvram iwlwifi snd_hda_intel lpc_ich snd_hda_controller snd_hda_codec snd_rawmidi snd_hwdep cfg80211 snd_pcm snd_seq mei_me shpchp mei snd_seq_device snd_timer snd soundcore parport_pc binfmt_misc ppdev mac_hid lp parport nls_iso8859_1 i915 psmouse e1000e ahci libahci i2c_algo_bit ptp drm_kms_helper video drm wmi pps_core [32612.021758] CPU: 0 PID: 1271 Comm: Xorg Tainted: GW OE 3.16.0-46-generic #62~14.04.1-Ubuntu [32612.021759] Hardware name: LENOVO 20BSCTO1WW/20BSCTO1WW, BIOS N14ET31W (1.09 ) 06/26/2015 [32612.021760] 0009 8800c5eebaa8 817663d1 [32612.021762] 8800c5eebae0 8106de3d c0302740 [32612.021764] 0800 88021e468548 88021e46 8800c5eebaf0 [32612.021766] Call Trace: [32612.021770] [817663d1] dump_stack+0x45/0x56 [32612.021773] [8106de3d] warn_slowpath_common+0x7d/0xa0 [32612.021776] [8106df1a] warn_slowpath_null+0x1a/0x20 [32612.021785] [c0256aad] intel_display_power_put+0x11d/0x160 [i915] [32612.021800] [c02bb0ff] intel_edp_panel_off+0x11f/0x1c0 [i915] [32612.021812] [c02b37a4] intel_ddi_post_disable+0xe4/0x150 [i915] [32612.021824] [c029e407] haswell_crtc_disable+0x107/0x2e0 [i915] [32612.021835] [c02a00fa] __intel_set_mode+0x78a/0xa90 [i915] [32612.021847] [c02a3256] intel_set_mode+0x16/0x30 [i915] [32612.021858] [c02a418d] intel_crtc_set_config+0x8ed/0xdb0 [i915] [32612.021869] [c0158401] drm_mode_set_config_internal+0x61/0xe0 [drm] [32612.021878] [c015be49] drm_mode_setcrtc+0xd9/0x590 [drm] [32612.021885] [c014c9ec] drm_ioctl+0x1ec/0x660 [drm] [32612.021889] [811e75e0] do_vfs_ioctl+0x2e0/0x4c0 [32612.021891] [811d6ce1] ? __sb_end_write+0x31/0x60 [32612.021894] [811d4872] ? vfs_write+0x172/0x1f0 [32612.021896] [811e7841] SyS_ioctl+0x81/0xa0 [32612.021899] [8176ea8d] system_call_fastpath+0x1a/0x1f [32612.021900] ---[ end trace 7b1c33a1651deac2 ]--- -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1384297 Title: After system resume, Intel i915 graphics hangs Status in linux package in Ubuntu: Triaged Status in linux source package in Utopic: Triaged Bug description: [ 3871.551684] WARNING: CPU: 2 PID: 2161 at /build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_pm.c:5997 intel_display_power_put+0x14c/0x160 [i915]() [ 3871.551686] Modules linked in: ctr ccm ec_sys dm_crypt intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul arc4 ghash_clmulni_intel rfcomm dm_multipath scsi_dh bnep aesni_intel iwlmvm hid_multitouch aes_x86_64 mac80211 lrw gf128mul glue_helper ablk_helper cryptd snd_hda_codec_hdmi snd_hda_codec_realtek iwlwifi snd_hda_codec_generic nfsd rtsx_pci_ms snd_hda_intel auth_rpcgss snd_hda_controller nfs_acl btusb memstick joydev snd_hda_codec nfs lockd snd_hwdep bluetooth snd_seq_midi snd_seq_midi_event sunrpc snd_rawmidi snd_soc_rt5640 6lowpan_iphc fscache snd_soc_rl6231 cfg80211 snd_seq snd_soc_core snd_compress binfmt_misc snd_pcm_dmaengine snd_pcm snd_seq_device tpm_infineon snd_timer lpc_ich dw_dmac dw_dmac_core i2c_hid 8250_dw i2c_designware_platform [ 3871.551704] i2c_designware_core snd shpchp snd_soc_sst_acpi mei_me mei spi_pxa2xx_platform mac_hid soundcore serio_raw parport_pc ppdev lp parport btrfs xor raid6_pq dm_mirror dm_region_hash dm_log mmc_block usbhid hid rtsx_pci_sdmmc i915 i2c_algo_bit rtsx_pci psmouse ahci drm_kms_helper r8169 libahci mii drm
[Kernel-packages] [Bug 1453892] Re: ISST-LTE: Ubuntu 15.04 need to manually set the bootlist when we do empty bootlist install with Crocodile adapters
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Importance: Undecided = High ** Changed in: linux (Ubuntu) Status: New = Triaged ** Changed in: linux (Ubuntu) Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1453892 Title: ISST-LTE: Ubuntu 15.04 need to manually set the bootlist when we do empty bootlist install with Crocodile adapters Status in debian-installer package in Ubuntu: New Status in linux package in Ubuntu: Triaged Bug description: ---Problem Description--- Base on my understanding, Ubuntu 15.4 has the bootlist setup feature, and the system will set the bootlist by itself after fresh installation, so the user don't need to set the bootlist manually. However, when we do the Ubuntu installation with empty bootlist and Crocodile adapters, such as GTO 57B4, North Rim 2CD2 and Solstice 57D7, the firmware cannot find a bootable disk to boot up after fresh installation. The installation with empty bootlist and FC disk or VSCSI works fine (the lpar can automatically find the bootable disk and boot up, no need to set the bootlist). Before installation: Version FW830.00 (SV830_033) SMS (c) Copyright IBM Corp. 2000,2014 All rights reserved. --- Current Boot Sequence 1.None 2.None 3.None 4.None 5.None After installation: IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM No OS image was detected by firmware. At least one disk in the bootlist was not found yet. Firmware is now retrying the entries in the bootlist. Press ctrl-C to stop retrying. ---uname output--- Linux conelp2 3.19.0-16-generic #16-Ubuntu SMP Thu Apr 30 16:12:49 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8408-E8E ---Steps to Reproduce--- 1.Install Ubuntu 15.04 2.Use PCIe2 4-port 1GbE Adapter ( loc=U78C7.001.RCH0042-P1-C8-T2 ) and use kte (10.33.11.31) as server 3.Enter mirror manually *Server: 10.33.11.31 *Directory: Use default *Proxy: http://10.33.11.31:3128 4.Select disk sda/sdb 5.After installation, let the lpar boot up by itself, and you will see the No OS image was detected by firmware message I do not know the specifics of the installers for the different distros, however, the expectation is that the installation does modify the boot list to add the newly installed device. In the scenario where a valid boot list exists prior to the install, if the installer does not modify the boot list to prepend the newly installed device, it will not be discovered automatically. It would require going to the SMS menu to find the device and add it to the boot list. In the scenario where the boot list is empty, on reboot PFW will attempt to construct a default boot list by scanning all of the available devices. We should be able to find the installed device. Excellent, thanks! I knew it would rescan on an empty list but I wasn't sure about the rest. So I guess the expectation is the installer should set the boot device. If this is not happening, can we get a reproduce starting from a empty boot list, and collect the install logs? I will look at the logs to see if I can find where it is failing and will mirror to Ubuntu. At the very end of install you should be able to go back to the main menu, then select Save debug logs, you will then see a message, A simple web server has been started on this computer to serve log files. Retrieve the files and attach to the bug: $ wget http://node/hardware-summary $ wget http://node/syslog I have reinstalled the lpar and collect logs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1453892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485184] cavac (i386) - tests ran: 71, failed: 68
tests ran: 71, failed: 68; http://kernel.ubuntu.com/testing/cavac__3.19.0-27.29~14.04.1__2015-08-26_20-42-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1485184 Title: linux-lts-vivid: 3.19.0-27.29~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-lts-vivid package in Ubuntu: New Status in linux-lts-vivid source package in Trusty: New Bug description: This bug is for tracking the 3.19.0-27.29~14.04.1 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:Saturday, 15. August 2015 07:02 UTC kernel-stable-master-bug:1485113 kernel-stable-Prepare-package-end:Sunday, 16. August 2015 12:03 UTC kernel-stable-Promote-to-proposed-start:Sunday, 16. August 2015 12:03 UTC kernel-stable-Promote-to-proposed-end:Monday, 17. August 2015 23:01 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 18. August 2015 00:04 UTC kernel-stable-Verification-testing-start:Tuesday, 18. August 2015 00:04 UTC kernel-stable-Certification-testing-start:Tuesday, 18. August 2015 00:04 UTC kernel-stable-Security-signoff-start:Tuesday, 18. August 2015 00:04 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 18. August 2015 00:04 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1485184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1384297] Re: After system resume, Intel i915 graphics hangs
Unfortunately, I've recently found that switching to a TTY doesn't always work, and sometimes the screen remains black no matter what is done and a forced reboot is required. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1384297 Title: After system resume, Intel i915 graphics hangs Status in linux package in Ubuntu: Triaged Status in linux source package in Utopic: Triaged Bug description: [ 3871.551684] WARNING: CPU: 2 PID: 2161 at /build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_pm.c:5997 intel_display_power_put+0x14c/0x160 [i915]() [ 3871.551686] Modules linked in: ctr ccm ec_sys dm_crypt intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul arc4 ghash_clmulni_intel rfcomm dm_multipath scsi_dh bnep aesni_intel iwlmvm hid_multitouch aes_x86_64 mac80211 lrw gf128mul glue_helper ablk_helper cryptd snd_hda_codec_hdmi snd_hda_codec_realtek iwlwifi snd_hda_codec_generic nfsd rtsx_pci_ms snd_hda_intel auth_rpcgss snd_hda_controller nfs_acl btusb memstick joydev snd_hda_codec nfs lockd snd_hwdep bluetooth snd_seq_midi snd_seq_midi_event sunrpc snd_rawmidi snd_soc_rt5640 6lowpan_iphc fscache snd_soc_rl6231 cfg80211 snd_seq snd_soc_core snd_compress binfmt_misc snd_pcm_dmaengine snd_pcm snd_seq_device tpm_infineon snd_timer lpc_ich dw_dmac dw_dmac_core i2c_hid 8250_dw i2c_designware_platform [ 3871.551704] i2c_designware_core snd shpchp snd_soc_sst_acpi mei_me mei spi_pxa2xx_platform mac_hid soundcore serio_raw parport_pc ppdev lp parport btrfs xor raid6_pq dm_mirror dm_region_hash dm_log mmc_block usbhid hid rtsx_pci_sdmmc i915 i2c_algo_bit rtsx_pci psmouse ahci drm_kms_helper r8169 libahci mii drm wmi sdhci_acpi video sdhci [ 3871.551717] CPU: 2 PID: 2161 Comm: unity-system-co Tainted: GW I 3.16.0-23-generic #30-Ubuntu [ 3871.551718] Hardware name: System76, IncDarter UltraThin/Darter UltraThin, BIOS 4.6.5 10/28/2013 [ 3871.551719] 0009 8800d70efae0 8177fcbc [ 3871.551721] 8800d70efb18 8106fd8d 88021008002c 000b [ 3871.551722] 880210088520 8802106c3000 88021008 8800d70efb28 [ 3871.551724] Call Trace: [ 3871.551729] [8177fcbc] dump_stack+0x45/0x56 [ 3871.551732] [8106fd8d] warn_slowpath_common+0x7d/0xa0 [ 3871.551734] [8106fe6a] warn_slowpath_null+0x1a/0x20 [ 3871.551742] [c026525c] intel_display_power_put+0x14c/0x160 [i915] [ 3871.551754] [c02adff4] modeset_update_crtc_power_domains+0x204/0x210 [i915] [ 3871.551765] [c02ae00e] haswell_modeset_global_resources+0xe/0x10 [i915] [ 3871.551775] [c02af70a] __intel_set_mode+0x5fa/0xab0 [i915] [ 3871.551785] [c02b2af6] intel_set_mode+0x16/0x30 [i915] [ 3871.551794] [c02b3bba] intel_crtc_set_config+0xa4a/0xda0 [i915] [ 3871.551804] [c01956d1] drm_mode_set_config_internal+0x61/0xe0 [drm] [ 3871.551813] [c01961e1] drm_framebuffer_remove+0xe1/0x140 [drm] [ 3871.551822] [c019a1ff] drm_mode_rmfb+0xdf/0x110 [drm] [ 3871.551828] [c0189a4f] drm_ioctl+0x1df/0x680 [drm] [ 3871.551831] [811f77e4] ? dentry_free+0x34/0x40 [ 3871.551833] [811f81aa] ? __dentry_kill+0x17a/0x200 [ 3871.551835] [811f83b0] ? dput+0x180/0x1c0 [ 3871.551837] [812016b4] ? mntput+0x24/0x40 [ 3871.551838] [811f4bc8] do_vfs_ioctl+0x2c8/0x4a0 [ 3871.551840] [811e285e] ? fput+0xe/0x10 [ 3871.551842] [810919ac] ? task_work_run+0xbc/0xf0 [ 3871.551843] [811f4e21] SyS_ioctl+0x81/0xa0 [ 3871.551845] [81787ced] system_call_fastpath+0x1a/0x1f [ 3871.551854] WARNING: CPU: 2 PID: 2161 at /build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_pm.c:6001 intel_display_power_put+0xf9/0x160 [i915]() [ 3871.551854] Modules linked in: ctr ccm ec_sys dm_crypt intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul arc4 ghash_clmulni_intel rfcomm dm_multipath scsi_dh bnep aesni_intel iwlmvm hid_multitouch aes_x86_64 mac80211 lrw gf128mul glue_helper ablk_helper cryptd snd_hda_codec_hdmi snd_hda_codec_realtek iwlwifi snd_hda_codec_generic nfsd rtsx_pci_ms snd_hda_intel auth_rpcgss snd_hda_controller nfs_acl btusb memstick joydev snd_hda_codec nfs lockd snd_hwdep bluetooth snd_seq_midi snd_seq_midi_event sunrpc snd_rawmidi snd_soc_rt5640 6lowpan_iphc fscache snd_soc_rl6231 cfg80211 snd_seq snd_soc_core snd_compress binfmt_misc snd_pcm_dmaengine snd_pcm snd_seq_device tpm_infineon snd_timer lpc_ich dw_dmac dw_dmac_core i2c_hid 8250_dw i2c_designware_platform [ 3871.551872] i2c_designware_core snd shpchp snd_soc_sst_acpi mei_me mei spi_pxa2xx_platform mac_hid soundcore serio_raw parport_pc
[Kernel-packages] [Bug 1373116] Re: cdc_acm causes Pantech UML295 reset
Got it working by downgrading modemmanager as described here http://ubuntuforums.org/showthread.php?t=2239564 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1373116 Title: cdc_acm causes Pantech UML295 reset Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 14.04.1 LTS Release: 14.04 When I upgraded to 14.04 (3.13 kernel), the Pantech UML295 4G Modem stopped functioning properly. Expected behavior: The modem starts up with a red LED lit while it initialized. Once a connection is established, linux recognizes a USB ethernet connection (cdc_ether), and the LED on the device goes green and flashing, indicating active connection. This status remains until the device is disconnected. Observed behavior: The modem starts up normally, getting to the point that a cdc_ether device is set up and a working internet connection is established. Shortly after this, the modem's light goes blue (an LED color that the documentation shows no information for), the ethernet connection fails, and the device goes back to the beginning of its initialization. The process will repeat indefinitely. This behavior can be avoided, and a connection maintaned, by blacklisting cdc_acm. However, this breaks many other USB serial devices. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-35-generic 3.13.0-35.62 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: charlie1799 F pulseaudio /dev/snd/controlC0: charlie1799 F pulseaudio /dev/snd/pcmC0D0c: charlie1799 F...m pulseaudio CurrentDesktop: X-Cinnamon Date: Tue Sep 23 16:16:04 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-04 (18 days ago) InstallationMedia: Kubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: LENOVO Lenovo IdeaPad P580 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-35-generic.efi.signed root=/dev/mapper/sysvg-lvroot 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 StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 5ECN96WW(V9.01) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: INVALID dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad P580 dmi.modalias: dmi:bvnLENOVO:bvr5ECN96WW(V9.01):bd03/14/2013:svnLENOVO:pnLenovoIdeaPadP580:pvrLenovoIdeaPadP580:rvnLENOVO:rnINVALID:rvrINVALID:cvnLENOVO:ct10:cvrLenovoIdeaPadP580: dmi.product.name: Lenovo IdeaPad P580 dmi.product.version: Lenovo IdeaPad P580 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1373116/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1489045] [NEW] Backport autopkgtest script to precise/trusty
Public bug reported: The kernel team has requested that we run DKMS tests via autopkgtests for precise and trusty the same way that we now do for vivid and upwards. For this we need to backport debian/scripts/dkms-autopkgtest from https://launchpad.net/ubuntu/+source/dkms/2.2.0.3-2ubuntu1. TEST CASE: Run autopkgtest for a DKMS package: adt-run bcmwl --- qemu adt-trusty-amd64-cloud.img # or use a precise image This currently fails with adt-run [15:18:24]: test command1: /usr/lib/dkms/dkms-autopkgtest adt-run [15:18:24]: test command1: [--- bash: /usr/lib/dkms/dkms-autopkgtest: No such file or directory With the proposed packages this should work and look more like Setting up bcmwl-kernel-source (6.30.223.248+bdcom-0ubuntu4) ... Loading new bcmwl-6.30.223.248+bdcom DKMS files... First Installation: checking all kernels... Building only for 4.1.0-3-generic Building for architecture x86_64 Building initial module for 4.1.0-3-generic Done. wl: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/4.1.0-3-generic/updates/dkms/ depmod DKMS: install completed. update-initramfs: deferring update (trigger activated) Setting up libfakeroot:amd64 (1.20.2-1ubuntu1) ... Setting up fakeroot (1.20.2-1ubuntu1) ... update-alternatives: using /usr/bin/fakeroot-sysv to provide /usr/bin/fakeroot (fakeroot) in auto mode Setting up manpages-dev (3.74-1ubuntu1) ... Processing triggers for initramfs-tools (0.120ubuntu3) ... update-initramfs: Generating /boot/initrd.img-4.1.0-3-generic I: Testing binary package bcmwl-kernel-source I: Testing if bcmwl modules are correctly installed bcmwl, 6.30.223.248+bdcom, 4.1.0-3-generic, x86_64: installed adt-run [17:23:43]: test command1: ---] REGRESSION POTENTIAL: Almost zero. dkms is an arch: all package, thus no miscompilation possible. The new script is not being used in dkms' actual operation, only when being invoked through autopkgtest. As every DKMS package test fails right now, there is no test regression possible either. ** Affects: dkms (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: dkms (Ubuntu Precise) Importance: Wishlist Assignee: Martin Pitt (pitti) Status: Triaged ** Affects: dkms (Ubuntu Trusty) Importance: Wishlist Assignee: Martin Pitt (pitti) Status: Triaged ** Also affects: dkms (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: dkms (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: dkms (Ubuntu) Status: New = Fix Released ** Changed in: dkms (Ubuntu Trusty) Status: New = Triaged ** Changed in: dkms (Ubuntu Trusty) Importance: Undecided = Wishlist ** Changed in: dkms (Ubuntu Trusty) Assignee: (unassigned) = Martin Pitt (pitti) ** Description changed: The kernel team has requested that we run DKMS tests via autopkgtests for precise and trusty the same way that we now do for vivid and upwards. For this we need to backport debian/scripts/dkms-autopkgtest from https://launchpad.net/ubuntu/+source/dkms/2.2.0.3-2ubuntu1. TEST CASE: - Run autopkgtest for a DKMS package: + Run autopkgtest for a DKMS package: -adt-run bcmwl --- qemu /srv/vm/adt-trusty-amd64-cloud.img # or use + adt-run bcmwl --- qemu /srv/vm/adt-trusty-amd64-cloud.img # or use a precise image This currently fails with -adt-run [15:18:24]: test command1: /usr/lib/dkms/dkms-autopkgtest -adt-run [15:18:24]: test command1: [--- -bash: /usr/lib/dkms/dkms-autopkgtest: No such file or directory + adt-run [15:18:24]: test command1: /usr/lib/dkms/dkms-autopkgtest + adt-run [15:18:24]: test command1: [--- + bash: /usr/lib/dkms/dkms-autopkgtest: No such file or directory With the proposed packages this should work and look more like Setting up bcmwl-kernel-source (6.30.223.248+bdcom-0ubuntu4) ... Loading new bcmwl-6.30.223.248+bdcom DKMS files... First Installation: checking all kernels... Building only for 4.1.0-3-generic Building for architecture x86_64 Building initial module for 4.1.0-3-generic Done. wl: Running module version sanity check. - - Original module -- No original module exists within this kernel - - Installation -- Installing to /lib/modules/4.1.0-3-generic/updates/dkms/ + - Original module + - No original module exists within this kernel + - Installation + - Installing to /lib/modules/4.1.0-3-generic/updates/dkms/ depmod DKMS: install completed. update-initramfs: deferring update (trigger activated) Setting up libfakeroot:amd64 (1.20.2-1ubuntu1) ... Setting up fakeroot (1.20.2-1ubuntu1) ... update-alternatives: using /usr/bin/fakeroot-sysv to provide /usr/bin/fakeroot (fakeroot) in auto mode Setting up manpages-dev
[Kernel-packages] [Bug 1487734] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run: apport-collect 1487734 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/1487734 Title: Battery Absent On HP Split 13x2 Laptop Status in linux package in Ubuntu: Incomplete Bug description: I have an HP Split 13x2 laptop with Ubuntu Mate installed. dmesg shows ACPI: Battery Slot [BAT0] (battery absent). The battery icon shows No battery present. ...I'm only able to run on AC power. --- I have tried: * Default and adjusted settings in BIOS. * Live versions of Ubuntu, Lubuntu and Ubuntu Mate. * Release 15.04 and 14.04 for all flavors above. * Installed ACPI. * Installed batmon. * Installed ibam. * Added to grub default boot line acpi_osi=, then acpi_osi=!Linux then acpi_osi=Linux. I have not tried recompiling the kernel, as several posts state the recompiling didn't work for them if not on a Toshiba. --- I'd really like to get this working...the laptop is needed for work done in areas where AC power won't always be present. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1487734/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485173] cavac (amd64) - tests ran: 4, failed: 2
tests ran: 4, failed: 2; http://kernel.ubuntu.com/testing/cavac__3.13.0-63.104~precise1__2015-08-27_01-13-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1485173 Title: linux-lts-trusty: 3.13.0-63.104~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: New Bug description: This bug is for tracking the 3.13.0-63.104~precise1 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:Saturday, 15. August 2015 05:03 UTC kernel-stable-master-bug:1485102 kernel-stable-Prepare-package-end:Sunday, 16. August 2015 12:02 UTC kernel-stable-Promote-to-proposed-start:Sunday, 16. August 2015 12:02 UTC kernel-stable-Promote-to-proposed-end:Thursday, 20. August 2015 00:33 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Thursday, 20. August 2015 02:01 UTC kernel-stable-Verification-testing-start:Thursday, 20. August 2015 02:01 UTC kernel-stable-Certification-testing-start:Thursday, 20. August 2015 02:01 UTC kernel-stable-Security-signoff-start:Thursday, 20. August 2015 02:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Thursday, 20. August 2015 02:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1485173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1476888] Re: No headset mic is detected on a dell machine
** Changed in: hwe-next Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu) Status: Fix Committed = 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/1476888 Title: No headset mic is detected on a dell machine Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: This bug is for tracking purposes. Please do not triage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1476888/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1487225] Re: linux-lts-utopic: 3.16.0-48.64~14.04.1 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed = In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) = Yung Shen (kaxing) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1487225 Title: linux-lts-utopic: 3.16.0-48.64~14.04.1 -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-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-utopic source package in Trusty: Confirmed Bug description: This bug is for tracking the 3.16.0-48.64~14.04.1 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:Thursday, 20. August 2015 22:17 UTC kernel-stable-Prepare-package-end:Friday, 21. August 2015 08:02 UTC kernel-stable-Promote-to-proposed-start:Friday, 21. August 2015 08:02 UTC kernel-stable-Promote-to-proposed-end:Friday, 21. August 2015 21:01 UTC kernel-stable-phase:Testing kernel-stable-phase-changed:Friday, 21. August 2015 23:33 UTC kernel-stable-Verification-testing-end:Friday, 21. August 2015 23:33 UTC kernel-stable-Certification-testing-start:Friday, 21. August 2015 23:33 UTC kernel-stable-Security-signoff-start:Friday, 21. August 2015 23:33 UTC kernel-stable-Regression-testing-start:Friday, 21. August 2015 23:33 UTC kernel-stable-Regression-testing-end:Tuesday, 25. August 2015 15:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1487225/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485113] Re: linux: 3.19.0-27.29 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed = In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) = Yung Shen (kaxing) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1485113 Title: linux: 3.19.0-27.29 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: New Bug description: This bug is for tracking the 3.19.0-27.29 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:Friday, 14. August 2015 20:50 UTC kernel-stable-Prepare-package-end:Saturday, 15. August 2015 07:03 UTC kernel-stable-Promote-to-proposed-start:Saturday, 15. August 2015 07:03 UTC kernel-stable-Promote-to-proposed-end:Monday, 17. August 2015 23:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 18. August 2015 00:02 UTC kernel-stable-Verification-testing-start:Tuesday, 18. August 2015 00:02 UTC kernel-stable-Certification-testing-start:Tuesday, 18. August 2015 00:02 UTC kernel-stable-Security-signoff-start:Tuesday, 18. August 2015 00:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 18. August 2015 00:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1485113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1373116] Re: cdc_acm causes Pantech UML295 reset
bump Anyone get this modem working? Works in 13.10 but getting same behavior as above in 14.04. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1373116 Title: cdc_acm causes Pantech UML295 reset Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 14.04.1 LTS Release: 14.04 When I upgraded to 14.04 (3.13 kernel), the Pantech UML295 4G Modem stopped functioning properly. Expected behavior: The modem starts up with a red LED lit while it initialized. Once a connection is established, linux recognizes a USB ethernet connection (cdc_ether), and the LED on the device goes green and flashing, indicating active connection. This status remains until the device is disconnected. Observed behavior: The modem starts up normally, getting to the point that a cdc_ether device is set up and a working internet connection is established. Shortly after this, the modem's light goes blue (an LED color that the documentation shows no information for), the ethernet connection fails, and the device goes back to the beginning of its initialization. The process will repeat indefinitely. This behavior can be avoided, and a connection maintaned, by blacklisting cdc_acm. However, this breaks many other USB serial devices. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-35-generic 3.13.0-35.62 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: charlie1799 F pulseaudio /dev/snd/controlC0: charlie1799 F pulseaudio /dev/snd/pcmC0D0c: charlie1799 F...m pulseaudio CurrentDesktop: X-Cinnamon Date: Tue Sep 23 16:16:04 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-04 (18 days ago) InstallationMedia: Kubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: LENOVO Lenovo IdeaPad P580 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-35-generic.efi.signed root=/dev/mapper/sysvg-lvroot 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 StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 5ECN96WW(V9.01) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: INVALID dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad P580 dmi.modalias: dmi:bvnLENOVO:bvr5ECN96WW(V9.01):bd03/14/2013:svnLENOVO:pnLenovoIdeaPadP580:pvrLenovoIdeaPadP580:rvnLENOVO:rnINVALID:rvrINVALID:cvnLENOVO:ct10:cvrLenovoIdeaPadP580: dmi.product.name: Lenovo IdeaPad P580 dmi.product.version: Lenovo IdeaPad P580 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1373116/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
