[Kernel-packages] [Bug 1626371] Re: cdc_ether fills kernel log
The problem does not occur in Linux version 4.8.0-34-generic (buildd@lcy01-21) from yakkety-proposed. I don't understand the "checkbox-gtk" instruction in the page you reference. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1626371 Title: cdc_ether fills kernel log Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Released Bug description: On my Lenovo X1 4th gen with a dock attached: [ 1764.086306] cdc_ether 2-4.1.3:2.0 enx0050b6d331fe: kevent 11 may have been dropped [ 1764.150317] cdc_ether 2-4.1.3:2.0 enx0050b6d331fe: kevent 11 may have been dropped The USB Ethernet device would warn occasionally under the 4.4 kernel. Under the 4.8 kernel, it spams my kernel log so much that I don't get anything else. $ uname -a Linux aurora 4.8.0-11-generic #12-Ubuntu SMP Sat Sep 17 20:00:03 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux joel@aurora ~ $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 Codename: yakkety To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626371/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1626371] Re: cdc_ether fills kernel log
I've been using the 4.9.0 I mentioned in comment #14 with no trouble at all. There is a new 4.9.0 of about the same date in the drm-intel-next branch that knz tried in comment #11. See if that has the problem fixed. Someone can also try building Linus's 4.9.0 to see if it's a general or Ubuntu resolution. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1626371 Title: cdc_ether fills kernel log Status in linux package in Ubuntu: Confirmed Bug description: On my Lenovo X1 4th gen with a dock attached: [ 1764.086306] cdc_ether 2-4.1.3:2.0 enx0050b6d331fe: kevent 11 may have been dropped [ 1764.150317] cdc_ether 2-4.1.3:2.0 enx0050b6d331fe: kevent 11 may have been dropped The USB Ethernet device would warn occasionally under the 4.4 kernel. Under the 4.8 kernel, it spams my kernel log so much that I don't get anything else. $ uname -a Linux aurora 4.8.0-11-generic #12-Ubuntu SMP Sat Sep 17 20:00:03 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux joel@aurora ~ $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 Codename: yakkety To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626371/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1626371] Re: cdc_ether fills kernel log
Ubuntu added a 4.9.0 kernel yesterday (4.9.0-040900-generic_4.9.0-040900.201612111631_amd64.deb) in the mainline kernel ppa. This kernel does not have the problem on my Surface Pro 3. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1626371 Title: cdc_ether fills kernel log Status in linux package in Ubuntu: Confirmed Bug description: On my Lenovo X1 4th gen with a dock attached: [ 1764.086306] cdc_ether 2-4.1.3:2.0 enx0050b6d331fe: kevent 11 may have been dropped [ 1764.150317] cdc_ether 2-4.1.3:2.0 enx0050b6d331fe: kevent 11 may have been dropped The USB Ethernet device would warn occasionally under the 4.4 kernel. Under the 4.8 kernel, it spams my kernel log so much that I don't get anything else. $ uname -a Linux aurora 4.8.0-11-generic #12-Ubuntu SMP Sat Sep 17 20:00:03 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux joel@aurora ~ $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 Codename: yakkety To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626371/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1626371] Re: cdc_ether fills kernel log
I've had the same problem with every 4.8 I tried including the one that is in the brand new Ubuntu 16.10 (4.8.0-22) [via live cd, not installed!]. My computer is a Surface Pro 3 which uses a Marvell chipset in the docking station. I'm pretty sure I have updated to the latest mwifiex in my installed 16.04. The computer does seem to work, but syslog grows by several lines per second (but now and again it skips a few seconds while it's worrying about a limit and then away it goes 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/1626371 Title: cdc_ether fills kernel log Status in linux package in Ubuntu: Confirmed Bug description: On my Lenovo X1 4th gen with a dock attached: [ 1764.086306] cdc_ether 2-4.1.3:2.0 enx0050b6d331fe: kevent 11 may have been dropped [ 1764.150317] cdc_ether 2-4.1.3:2.0 enx0050b6d331fe: kevent 11 may have been dropped The USB Ethernet device would warn occasionally under the 4.4 kernel. Under the 4.8 kernel, it spams my kernel log so much that I don't get anything else. $ uname -a Linux aurora 4.8.0-11-generic #12-Ubuntu SMP Sat Sep 17 20:00:03 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux joel@aurora ~ $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 Codename: yakkety To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626371/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1510570] Re: BLE pairing fail
Bluez 5.40 works for me for both Designer keyboard and mouse. At this time Ubuntu has not packaged it up into a DEB but I was able to build and install it myself (search for bluez 5.40 to find how to download the entire large source). I am using Ubuntu 16.04 but a newer kernel made by Ubuntu (4.6.0-040600-generic). It is also important to install the patches Guilhem mentions in #22. I needed some additional packages to do the build. This is the whole procedure as well as a website that helped me figure this out: ./configure --prefix=/usr --mandir=/usr/share/man --sysconfdir=/etc --localstatedir=/var sudo apt-get install glib2.0 sudo apt-get install libdbus-1-dev sudo apt-get install libudev-dev sudo apt-get install libical-dev sudo apt-get install libreadline-dev sudo make sudo make install (I got help from http://rrbluetoothx.blogspot.com/2016/04/rr-bluetooth- compile-bluez-539.html). They haven't got everything right yet: both devices, though they work fine, are of unknown type, and syslog is still littered with python failures whenever one of these connects or disconnects. -- 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/1510570 Title: BLE pairing fail Status in bluez package in Ubuntu: Confirmed Bug description: On 15.10 we now have bluez 5 so we can pair BLE devices like the Microsoft Arc Touch Bluetooth Mouse. But this pairing doesn't work very well. Mouse is seen but pairing fail. More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5 This is due to udev rule that use "hcitool" to power on device. Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used instead of udev rules. here is a commit with this parameter: http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138 And a ppa to test it: https://code.launchpad.net/~guilhem-fr/+archive/ubuntu/bluez-autoenable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1510570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1510570] Re: BLE pairing fail
The 4.4 Linux Kernel series reconnects even after the 10 minutes or (usually) a reboot. My roll-your-own is 4.4-rc2 which has a building problem but that is known and probably will already be fixed in rc3 -- 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/1510570 Title: BLE pairing fail Status in bluez package in Ubuntu: Confirmed Bug description: On 15.10 we now have bluez 5 so we can pair BLE devices like the Microsoft Arc Touch Bluetooth Mouse. But this pairing doesn't work very well. Mouse is seen but pairing fail. More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5 This is due to udev rule that use "hcitool" to power on device. Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used instead of udev rules. here is a commit with this parameter: http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138 And a ppa to test it: https://code.launchpad.net/~guilhem-fr/+archive/ubuntu/bluez-autoenable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1510570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1510570] Re: BLE pairing fail
A follow-up. My Android Lollipop phone can connect and knows that the Designer Mouse is a mouse (not an unknown). Unfortunately it too loses connection in 10 minutes so the problem is deeper than I had expected. -- 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/1510570 Title: BLE pairing fail Status in bluez package in Ubuntu: Confirmed Bug description: On 15.10 we now have bluez 5 so we can pair BLE devices like the Microsoft Arc Touch Bluetooth Mouse. But this pairing doesn't work very well. Mouse is seen but pairing fail. More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5 This is due to udev rule that use "hcitool" to power on device. Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used instead of udev rules. here is a commit with this parameter: http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138 And a ppa to test it: https://code.launchpad.net/~guilhem-fr/+archive/ubuntu/bluez-autoenable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1510570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1510570] Re: BLE pairing fail
I have been working with a Microsoft Designer Mouse (also a BLA device). I went to AskUbuntu to try to find out why I could not use it with Ubuntu 15.10. [I have a Microsoft Surface Pro3 and am using a home-built kernel but the kernel does not seem to affect this problem.] I have followed the instructions in comment #9 and find that the mouse works...for 10 minutes. Apparently each use of the mouse resets a 10-minute watchdog timer and the mouse is disconnected if ever this timer expires. It won't come back on its own. To reconnect it, you must "remove" the mouse using Blueman or the Gnome Bluetooth Manager (I use the former), search it out again, and set it up again. Usually this works the first time but sometimes you have to go through it again. Despite the fact that the mouse works it is reported as of type "unknown" or "All types." I have attached a chunk of syslog showing the full cycle. I removed the old and reconnected it at 19:19. I used the mouse for about 4 minutes and then turned it upside down at 19:23. It disconnected 10 minutes later at 19:33. This sequence is repeatable and invariant. Is this the right bug for this our should another be started? Thanks, Keith ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1510570/+attachment/4523863/+files/syslog -- 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/1510570 Title: BLE pairing fail Status in bluez package in Ubuntu: Confirmed Bug description: On 15.10 we now have bluez 5 so we can pair BLE devices like the Microsoft Arc Touch Bluetooth Mouse. But this pairing doesn't work very well. Mouse is seen but pairing fail. More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5 This is due to udev rule that use "hcitool" to power on device. Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used instead of udev rules. here is a commit with this parameter: http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138 And a ppa to test it: https://code.launchpad.net/~guilhem-fr/+archive/ubuntu/bluez-autoenable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1510570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1436620] Re: Bluetooth USB interrupt suspended state on Surface Pro 3
Christopher, this assignment doesn't seem possible. When I use Linux 4.0.0-04rc7-genericx86_64, it suspends well and seems to stay suspended indefinitely. But I can't get it to resume at all and have to kill it by holding the power switch for a long time. When it comes back it reports two or three errors, though I'm not sure they are different. It's a proglem type KernelOops, suspend/resume failure with apport version 2.14.7-0ubuntu8.2. The hole suspend thing is highly erratic. Sometimes, using my modified 4.0-rc7 kernel, I actually get both lid open and lid close events. When that happens, I can set it to suspend on lid closed and it actually works pretty well except for not going through a logon on the way back. Maybe suspending by another means wrecks its ability to recognize lid opening but this is getting into speculation. I and some other people are trying to keep a coherent discussion of all surface problems going on https://groups.google.com/forum/#!forum/linux- surface . I will keep trying to understand things there.] Maybe this bug should be closed for being irreproducible. Keith -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1436620 Title: Bluetooth USB interrupt suspended state on Surface Pro 3 Status in linux package in Ubuntu: Incomplete Bug description: [Please note: this information was collected using 3.16.0-33 but actually is talking about behavior under 4.0.0-RC4 with four specific patches described at the end of the note.] 1. When suspending (i.e. freezing in this situation), it is never certain that it will stay suspended. About half the time it simply bounces back in the same way that suspending without the freeze patch does. 2. If Bluetooth is on or if a Gigaware USB hub is connected to a USB port, the freeze never seems to last very long. It doesn't always bounce right back but it usually comes back within a few minutes. (I have the latest version of mwifiex firmware.) Not all USB devices cause this problem; e.g. I have a Microsoft wireless keyboard and mouse with a tiny USB transceiver that does not affect suspension. The patches are: - (not involved) The addition of the two Microsoft cameras in the kernel, drivers/media/usb/uvc/uvc_driver.c. - (not involved) The acpi battery-detecting patch described in kernel bugzilla bug 90161. - Modification of /usr/lib/pm-utils/pm-functions as described in Launchpad bug 1380076 to use the freeze methodology for suspending. Without this modification all attempts at suspending bounce back immediately; thus the behavior described in this bug cannot be observed. - The surface_buttons.c patch described in kernel bugzilla bug 84651; without this it is nearly impossible to get out of a freeze once you've gotten into it. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-33-generic 3.16.0-33.44 ProcVersionSignature: Ubuntu 3.16.0-33.44-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: keith 2741 F pulseaudio /dev/snd/controlC0: keith 2741 F pulseaudio /dev/snd/controlC1: keith 2741 F pulseaudio CurrentDesktop: Unity Date: Wed Mar 25 20:17:17 2015 HibernationDevice: RESUME=UUID=a84237b2-3192-4b08-a535-d5561688b546 InstallationDate: Installed on 2015-01-05 (79 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: Microsoft Corporation Surface Pro 3 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic.efi.signed root=UUID=07a2b8fb-d17a-4e67-a4d5-39ece3561dc4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-33-generic N/A linux-backports-modules-3.16.0-33-generic N/A linux-firmware 1.138.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.11.0450 dmi.board.asset.tag: 0 dmi.board.name: Surface Pro 3 dmi.board.vendor: Microsoft Corporation dmi.board.version: 1 dmi.chassis.asset.tag: 0 dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.11.0450:bd11/19/2014:svnMicrosoftCorporation:pnSurfacePro3:pvr1:rvnMicrosoftCorporation:rnSurfacePro3:rvr1:cvnMicrosoftCorporation:ct9:cvr1: dmi.product.name: Surface Pro 3 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/1436620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1436620] Re: Bluetooth USB interrupt suspended state on Surface Pro 3
Here is my bios information: 3.11.0760 03/16/2015 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1436620 Title: Bluetooth USB interrupt suspended state on Surface Pro 3 Status in linux package in Ubuntu: Confirmed Bug description: [Please note: this information was collected using 3.16.0-33 but actually is talking about behavior under 4.0.0-RC4 with four specific patches described at the end of the note.] 1. When suspending (i.e. freezing in this situation), it is never certain that it will stay suspended. About half the time it simply bounces back in the same way that suspending without the freeze patch does. 2. If Bluetooth is on or if a Gigaware USB hub is connected to a USB port, the freeze never seems to last very long. It doesn't always bounce right back but it usually comes back within a few minutes. (I have the latest version of mwifiex firmware.) Not all USB devices cause this problem; e.g. I have a Microsoft wireless keyboard and mouse with a tiny USB transceiver that does not affect suspension. The patches are: - (not involved) The addition of the two Microsoft cameras in the kernel, drivers/media/usb/uvc/uvc_driver.c. - (not involved) The acpi battery-detecting patch described in kernel bugzilla bug 90161. - Modification of /usr/lib/pm-utils/pm-functions as described in Launchpad bug 1380076 to use the freeze methodology for suspending. Without this modification all attempts at suspending bounce back immediately; thus the behavior described in this bug cannot be observed. - The surface_buttons.c patch described in kernel bugzilla bug 84651; without this it is nearly impossible to get out of a freeze once you've gotten into it. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-33-generic 3.16.0-33.44 ProcVersionSignature: Ubuntu 3.16.0-33.44-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: keith 2741 F pulseaudio /dev/snd/controlC0: keith 2741 F pulseaudio /dev/snd/controlC1: keith 2741 F pulseaudio CurrentDesktop: Unity Date: Wed Mar 25 20:17:17 2015 HibernationDevice: RESUME=UUID=a84237b2-3192-4b08-a535-d5561688b546 InstallationDate: Installed on 2015-01-05 (79 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: Microsoft Corporation Surface Pro 3 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic.efi.signed root=UUID=07a2b8fb-d17a-4e67-a4d5-39ece3561dc4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-33-generic N/A linux-backports-modules-3.16.0-33-generic N/A linux-firmware 1.138.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.11.0450 dmi.board.asset.tag: 0 dmi.board.name: Surface Pro 3 dmi.board.vendor: Microsoft Corporation dmi.board.version: 1 dmi.chassis.asset.tag: 0 dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.11.0450:bd11/19/2014:svnMicrosoftCorporation:pnSurfacePro3:pvr1:rvnMicrosoftCorporation:rnSurfacePro3:rvr1:cvnMicrosoftCorporation:ct9:cvr1: dmi.product.name: Surface Pro 3 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/1436620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1436620] Re: Bluetooth USB interrupt suspended state on Surface Pro 3
Christopher, when I downloaded the 4.0-rc6 kernel earlier in the week it didn't really install right but ran (somehow broken with respect to the headers) so I deleted it after making the report. Tonight I can't repeat the installation, good or bad, so I'll wait until the next one is made, probably until sometime Monday. When doing this should I install just the image and headers for .amd64 or also the headers for .all? I presume from your comment that you want me to do the whole resume- trace procedure even though the problem isn't that it resumes badly but that it resumes too easily. 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/1436620 Title: Bluetooth USB interrupt suspended state on Surface Pro 3 Status in linux package in Ubuntu: Incomplete Bug description: [Please note: this information was collected using 3.16.0-33 but actually is talking about behavior under 4.0.0-RC4 with four specific patches described at the end of the note.] 1. When suspending (i.e. freezing in this situation), it is never certain that it will stay suspended. About half the time it simply bounces back in the same way that suspending without the freeze patch does. 2. If Bluetooth is on or if a Gigaware USB hub is connected to a USB port, the freeze never seems to last very long. It doesn't always bounce right back but it usually comes back within a few minutes. (I have the latest version of mwifiex firmware.) Not all USB devices cause this problem; e.g. I have a Microsoft wireless keyboard and mouse with a tiny USB transceiver that does not affect suspension. The patches are: - (not involved) The addition of the two Microsoft cameras in the kernel, drivers/media/usb/uvc/uvc_driver.c. - (not involved) The acpi battery-detecting patch described in kernel bugzilla bug 90161. - Modification of /usr/lib/pm-utils/pm-functions as described in Launchpad bug 1380076 to use the freeze methodology for suspending. Without this modification all attempts at suspending bounce back immediately; thus the behavior described in this bug cannot be observed. - The surface_buttons.c patch described in kernel bugzilla bug 84651; without this it is nearly impossible to get out of a freeze once you've gotten into it. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-33-generic 3.16.0-33.44 ProcVersionSignature: Ubuntu 3.16.0-33.44-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: keith 2741 F pulseaudio /dev/snd/controlC0: keith 2741 F pulseaudio /dev/snd/controlC1: keith 2741 F pulseaudio CurrentDesktop: Unity Date: Wed Mar 25 20:17:17 2015 HibernationDevice: RESUME=UUID=a84237b2-3192-4b08-a535-d5561688b546 InstallationDate: Installed on 2015-01-05 (79 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: Microsoft Corporation Surface Pro 3 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic.efi.signed root=UUID=07a2b8fb-d17a-4e67-a4d5-39ece3561dc4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-33-generic N/A linux-backports-modules-3.16.0-33-generic N/A linux-firmware 1.138.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.11.0450 dmi.board.asset.tag: 0 dmi.board.name: Surface Pro 3 dmi.board.vendor: Microsoft Corporation dmi.board.version: 1 dmi.chassis.asset.tag: 0 dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.11.0450:bd11/19/2014:svnMicrosoftCorporation:pnSurfacePro3:pvr1:rvnMicrosoftCorporation:rnSurfacePro3:rvr1:cvnMicrosoftCorporation:ct9:cvr1: dmi.product.name: Surface Pro 3 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/1436620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1436620] Re: Bluetooth USB interrupt suspended state on Surface Pro 3
I am using that update; it came March 31 and disconnected me from grub. I figured out how to use boot-repair and got back to Linux. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1436620 Title: Bluetooth USB interrupt suspended state on Surface Pro 3 Status in linux package in Ubuntu: Confirmed Bug description: [Please note: this information was collected using 3.16.0-33 but actually is talking about behavior under 4.0.0-RC4 with four specific patches described at the end of the note.] 1. When suspending (i.e. freezing in this situation), it is never certain that it will stay suspended. About half the time it simply bounces back in the same way that suspending without the freeze patch does. 2. If Bluetooth is on or if a Gigaware USB hub is connected to a USB port, the freeze never seems to last very long. It doesn't always bounce right back but it usually comes back within a few minutes. (I have the latest version of mwifiex firmware.) Not all USB devices cause this problem; e.g. I have a Microsoft wireless keyboard and mouse with a tiny USB transceiver that does not affect suspension. The patches are: - (not involved) The addition of the two Microsoft cameras in the kernel, drivers/media/usb/uvc/uvc_driver.c. - (not involved) The acpi battery-detecting patch described in kernel bugzilla bug 90161. - Modification of /usr/lib/pm-utils/pm-functions as described in Launchpad bug 1380076 to use the freeze methodology for suspending. Without this modification all attempts at suspending bounce back immediately; thus the behavior described in this bug cannot be observed. - The surface_buttons.c patch described in kernel bugzilla bug 84651; without this it is nearly impossible to get out of a freeze once you've gotten into it. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-33-generic 3.16.0-33.44 ProcVersionSignature: Ubuntu 3.16.0-33.44-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: keith 2741 F pulseaudio /dev/snd/controlC0: keith 2741 F pulseaudio /dev/snd/controlC1: keith 2741 F pulseaudio CurrentDesktop: Unity Date: Wed Mar 25 20:17:17 2015 HibernationDevice: RESUME=UUID=a84237b2-3192-4b08-a535-d5561688b546 InstallationDate: Installed on 2015-01-05 (79 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: Microsoft Corporation Surface Pro 3 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic.efi.signed root=UUID=07a2b8fb-d17a-4e67-a4d5-39ece3561dc4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-33-generic N/A linux-backports-modules-3.16.0-33-generic N/A linux-firmware 1.138.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.11.0450 dmi.board.asset.tag: 0 dmi.board.name: Surface Pro 3 dmi.board.vendor: Microsoft Corporation dmi.board.version: 1 dmi.chassis.asset.tag: 0 dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.11.0450:bd11/19/2014:svnMicrosoftCorporation:pnSurfacePro3:pvr1:rvnMicrosoftCorporation:rnSurfacePro3:rvr1:cvnMicrosoftCorporation:ct9:cvr1: dmi.product.name: Surface Pro 3 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/1436620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1436620] Re: Bluetooth USB interrupt suspended state on Surface Pro 3
I should really say that suspend-to-idle never holds forever. With the SP3 disconnected from every plug including docking station, power, type cover, and micro-SD and with both BT and WIFI turned off, it lasts for random periods and then comes back alive. I'm using 4.0-RC6 with the set of patches listed in kernel bug 84651 comment 87. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1436620 Title: Bluetooth USB interrupt suspended state on Surface Pro 3 Status in linux package in Ubuntu: Confirmed Bug description: [Please note: this information was collected using 3.16.0-33 but actually is talking about behavior under 4.0.0-RC4 with four specific patches described at the end of the note.] 1. When suspending (i.e. freezing in this situation), it is never certain that it will stay suspended. About half the time it simply bounces back in the same way that suspending without the freeze patch does. 2. If Bluetooth is on or if a Gigaware USB hub is connected to a USB port, the freeze never seems to last very long. It doesn't always bounce right back but it usually comes back within a few minutes. (I have the latest version of mwifiex firmware.) Not all USB devices cause this problem; e.g. I have a Microsoft wireless keyboard and mouse with a tiny USB transceiver that does not affect suspension. The patches are: - (not involved) The addition of the two Microsoft cameras in the kernel, drivers/media/usb/uvc/uvc_driver.c. - (not involved) The acpi battery-detecting patch described in kernel bugzilla bug 90161. - Modification of /usr/lib/pm-utils/pm-functions as described in Launchpad bug 1380076 to use the freeze methodology for suspending. Without this modification all attempts at suspending bounce back immediately; thus the behavior described in this bug cannot be observed. - The surface_buttons.c patch described in kernel bugzilla bug 84651; without this it is nearly impossible to get out of a freeze once you've gotten into it. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-33-generic 3.16.0-33.44 ProcVersionSignature: Ubuntu 3.16.0-33.44-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: keith 2741 F pulseaudio /dev/snd/controlC0: keith 2741 F pulseaudio /dev/snd/controlC1: keith 2741 F pulseaudio CurrentDesktop: Unity Date: Wed Mar 25 20:17:17 2015 HibernationDevice: RESUME=UUID=a84237b2-3192-4b08-a535-d5561688b546 InstallationDate: Installed on 2015-01-05 (79 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: Microsoft Corporation Surface Pro 3 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic.efi.signed root=UUID=07a2b8fb-d17a-4e67-a4d5-39ece3561dc4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-33-generic N/A linux-backports-modules-3.16.0-33-generic N/A linux-firmware 1.138.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.11.0450 dmi.board.asset.tag: 0 dmi.board.name: Surface Pro 3 dmi.board.vendor: Microsoft Corporation dmi.board.version: 1 dmi.chassis.asset.tag: 0 dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.11.0450:bd11/19/2014:svnMicrosoftCorporation:pnSurfacePro3:pvr1:rvnMicrosoftCorporation:rnSurfacePro3:rvr1:cvnMicrosoftCorporation:ct9:cvr1: dmi.product.name: Surface Pro 3 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/1436620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1436620] Re: Bluetooth USB interrupt suspended state on Surface Pro 3
I tested with Linux version 4.0.0-04rc6-generic using the pm_functions as modified by Launchpad bug 1380076. This is not a perfectly clean bug in that it sometimes bounces back from freeze even without BT being on and it can go a long time with BT on. But definitely BT makes the freeze less reliable. An interesting feature: you cannot break the freeze by use of the type cover's keyboard or touch pad but can by an eternal mouse or keyboard. I've attached DMESG. ** Attachment added: dmesg https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1436620/+attachment/4361491/+files/dmesg.txt ** Tags added: kernel-bug-exists-upstream kernel-bug-exists- upstream-4.0.0-rc6 ** 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/1436620 Title: Bluetooth USB interrupt suspended state on Surface Pro 3 Status in linux package in Ubuntu: Confirmed Bug description: [Please note: this information was collected using 3.16.0-33 but actually is talking about behavior under 4.0.0-RC4 with four specific patches described at the end of the note.] 1. When suspending (i.e. freezing in this situation), it is never certain that it will stay suspended. About half the time it simply bounces back in the same way that suspending without the freeze patch does. 2. If Bluetooth is on or if a Gigaware USB hub is connected to a USB port, the freeze never seems to last very long. It doesn't always bounce right back but it usually comes back within a few minutes. (I have the latest version of mwifiex firmware.) Not all USB devices cause this problem; e.g. I have a Microsoft wireless keyboard and mouse with a tiny USB transceiver that does not affect suspension. The patches are: - (not involved) The addition of the two Microsoft cameras in the kernel, drivers/media/usb/uvc/uvc_driver.c. - (not involved) The acpi battery-detecting patch described in kernel bugzilla bug 90161. - Modification of /usr/lib/pm-utils/pm-functions as described in Launchpad bug 1380076 to use the freeze methodology for suspending. Without this modification all attempts at suspending bounce back immediately; thus the behavior described in this bug cannot be observed. - The surface_buttons.c patch described in kernel bugzilla bug 84651; without this it is nearly impossible to get out of a freeze once you've gotten into it. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-33-generic 3.16.0-33.44 ProcVersionSignature: Ubuntu 3.16.0-33.44-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: keith 2741 F pulseaudio /dev/snd/controlC0: keith 2741 F pulseaudio /dev/snd/controlC1: keith 2741 F pulseaudio CurrentDesktop: Unity Date: Wed Mar 25 20:17:17 2015 HibernationDevice: RESUME=UUID=a84237b2-3192-4b08-a535-d5561688b546 InstallationDate: Installed on 2015-01-05 (79 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: Microsoft Corporation Surface Pro 3 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic.efi.signed root=UUID=07a2b8fb-d17a-4e67-a4d5-39ece3561dc4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-33-generic N/A linux-backports-modules-3.16.0-33-generic N/A linux-firmware 1.138.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.11.0450 dmi.board.asset.tag: 0 dmi.board.name: Surface Pro 3 dmi.board.vendor: Microsoft Corporation dmi.board.version: 1 dmi.chassis.asset.tag: 0 dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.11.0450:bd11/19/2014:svnMicrosoftCorporation:pnSurfacePro3:pvr1:rvnMicrosoftCorporation:rnSurfacePro3:rvr1:cvnMicrosoftCorporation:ct9:cvr1: dmi.product.name: Surface Pro 3 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/1436620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1380076] Re: Can't suspend on Surface Pro 3
I have created bug 1436620. It's a bit of a messy situation but I hope I described it well enough. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1380076 Title: Can't suspend on Surface Pro 3 Status in linux package in Ubuntu: Incomplete Bug description: With my Surface Pro 3 when I suspend from the GUI nothing happens. Doing it manually also fails, and nothing appears in dmesg: #echo mem /sys/power/state Error while writing to stdout write_loop: Invalid argument And, more interestingly: cat /sys/power/state freeze disk Using the not-so-good-and-apparently-unsupported: echo freeze /sys/power/state does seem to successfully suspend, however I cannot resume from this (assumed to be a separate issue). I am using a modified utopic unicorn kernel compiled from git at kernel.ubuntu.com, with the following patch to enable mykeyboard to work: http://www.spinics.net/lists/linux-input/msg34918.html The official kernel behaves identically, as does vanilla 3.17 from the mainline folder of kernel-ppa. WORKAROUND: Use hibernate. --- ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarrad 2491 F pulseaudio /dev/snd/controlC0: jarrad 2491 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=178ac532-25db-4ef3-a587-f1fdd2649bf0 InstallationDate: Installed on 2014-10-10 (57 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140923) MachineType: Microsoft Corporation Surface Pro 3 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.4-surface3 root=UUID=f6c17817-9127-4792-be23-a39a07e7f240 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4 RelatedPackageVersions: linux-restricted-modules-3.16.4-surface3 N/A linux-backports-modules-3.16.4-surface3 N/A linux-firmware 1.135 Tags: utopic Uname: Linux 3.16.4-surface3 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/16/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.11.0350 dmi.board.asset.tag: 0 dmi.board.name: Surface Pro 3 dmi.board.vendor: Microsoft Corporation dmi.board.version: 1 dmi.chassis.asset.tag: 0 dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.11.0350:bd10/16/2014:svnMicrosoftCorporation:pnSurfacePro3:pvr1:rvnMicrosoftCorporation:rnSurfacePro3:rvr1:cvnMicrosoftCorporation:ct9:cvr1: dmi.product.name: Surface Pro 3 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/1380076/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1380076] Re: Can't suspend on Surface Pro 3
I have created bug 1436620. It's a bit of a messy situation but I hope I described it well enough. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1380076 Title: Can't suspend on Surface Pro 3 Status in linux package in Ubuntu: Incomplete Bug description: With my Surface Pro 3 when I suspend from the GUI nothing happens. Doing it manually also fails, and nothing appears in dmesg: #echo mem /sys/power/state Error while writing to stdout write_loop: Invalid argument And, more interestingly: cat /sys/power/state freeze disk Using the not-so-good-and-apparently-unsupported: echo freeze /sys/power/state does seem to successfully suspend, however I cannot resume from this (assumed to be a separate issue). I am using a modified utopic unicorn kernel compiled from git at kernel.ubuntu.com, with the following patch to enable mykeyboard to work: http://www.spinics.net/lists/linux-input/msg34918.html The official kernel behaves identically, as does vanilla 3.17 from the mainline folder of kernel-ppa. WORKAROUND: Use hibernate. --- ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarrad 2491 F pulseaudio /dev/snd/controlC0: jarrad 2491 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=178ac532-25db-4ef3-a587-f1fdd2649bf0 InstallationDate: Installed on 2014-10-10 (57 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140923) MachineType: Microsoft Corporation Surface Pro 3 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.4-surface3 root=UUID=f6c17817-9127-4792-be23-a39a07e7f240 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4 RelatedPackageVersions: linux-restricted-modules-3.16.4-surface3 N/A linux-backports-modules-3.16.4-surface3 N/A linux-firmware 1.135 Tags: utopic Uname: Linux 3.16.4-surface3 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/16/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.11.0350 dmi.board.asset.tag: 0 dmi.board.name: Surface Pro 3 dmi.board.vendor: Microsoft Corporation dmi.board.version: 1 dmi.chassis.asset.tag: 0 dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.11.0350:bd10/16/2014:svnMicrosoftCorporation:pnSurfacePro3:pvr1:rvnMicrosoftCorporation:rnSurfacePro3:rvr1:cvnMicrosoftCorporation:ct9:cvr1: dmi.product.name: Surface Pro 3 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/1380076/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1436620] [NEW] Bluetooth USB interrupt suspended state on Surface Pro 3
Public bug reported: [Please note: this information was collected using 3.16.0-33 but actually is talking about behavior under 4.0.0-RC4 with four specific patches described at the end of the note.] 1. When suspending (i.e. freezing in this situation), it is never certain that it will stay suspended. About half the time it simply bounces back in the same way that suspending without the freeze patch does. 2. If Bluetooth is on or if a Gigaware USB hub is connected to a USB port, the freeze never seems to last very long. It doesn't always bounce right back but it usually comes back within a few minutes. (I have the latest version of mwifiex firmware.) Not all USB devices cause this problem; e.g. I have a Microsoft wireless keyboard and mouse with a tiny USB transceiver that does not affect suspension. The patches are: - (not involved) The addition of the two Microsoft cameras in the kernel, drivers/media/usb/uvc/uvc_driver.c. - (not involved) The acpi battery-detecting patch described in kernel bugzilla bug 90161. - Modification of /usr/lib/pm-utils/pm-functions as described in Launchpad bug 1380076 to use the freeze methodology for suspending. Without this modification all attempts at suspending bounce back immediately; thus the behavior described in this bug cannot be observed. - The surface_buttons.c patch described in kernel bugzilla bug 84651; without this it is nearly impossible to get out of a freeze once you've gotten into it. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-33-generic 3.16.0-33.44 ProcVersionSignature: Ubuntu 3.16.0-33.44-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: keith 2741 F pulseaudio /dev/snd/controlC0: keith 2741 F pulseaudio /dev/snd/controlC1: keith 2741 F pulseaudio CurrentDesktop: Unity Date: Wed Mar 25 20:17:17 2015 HibernationDevice: RESUME=UUID=a84237b2-3192-4b08-a535-d5561688b546 InstallationDate: Installed on 2015-01-05 (79 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: Microsoft Corporation Surface Pro 3 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic.efi.signed root=UUID=07a2b8fb-d17a-4e67-a4d5-39ece3561dc4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-33-generic N/A linux-backports-modules-3.16.0-33-generic N/A linux-firmware 1.138.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.11.0450 dmi.board.asset.tag: 0 dmi.board.name: Surface Pro 3 dmi.board.vendor: Microsoft Corporation dmi.board.version: 1 dmi.chassis.asset.tag: 0 dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.11.0450:bd11/19/2014:svnMicrosoftCorporation:pnSurfacePro3:pvr1:rvnMicrosoftCorporation:rnSurfacePro3:rvr1:cvnMicrosoftCorporation:ct9:cvr1: dmi.product.name: Surface Pro 3 dmi.product.version: 1 dmi.sys.vendor: Microsoft Corporation ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bluetooth suspend utopic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1436620 Title: Bluetooth USB interrupt suspended state on Surface Pro 3 Status in linux package in Ubuntu: New Bug description: [Please note: this information was collected using 3.16.0-33 but actually is talking about behavior under 4.0.0-RC4 with four specific patches described at the end of the note.] 1. When suspending (i.e. freezing in this situation), it is never certain that it will stay suspended. About half the time it simply bounces back in the same way that suspending without the freeze patch does. 2. If Bluetooth is on or if a Gigaware USB hub is connected to a USB port, the freeze never seems to last very long. It doesn't always bounce right back but it usually comes back within a few minutes. (I have the latest version of mwifiex firmware.) Not all USB devices cause this problem; e.g. I have a Microsoft wireless keyboard and mouse with a tiny USB transceiver that does not affect suspension. The patches are: - (not involved) The addition of the two Microsoft cameras in the kernel, drivers/media/usb/uvc/uvc_driver.c. - (not involved) The acpi battery-detecting patch described in kernel bugzilla bug 90161. - Modification of /usr/lib/pm-utils/pm-functions as described in Launchpad bug 1380076 to use the freeze methodology for suspending. Without this modification all attempts at suspending bounce back immediately; thus the behavior described
[Kernel-packages] [Bug 1380076] Re: Can't suspend on Surface Pro 3
With the freeze patch installed and the power button patch in the kernel it can still fail to stay suspended. However I think there are two causes in my system and without them it will stay frozen at least until there is a power glitch: - Bluetooth on, even with nothing paired, is certain to cause return from freeze - Some things on USB can cause return from freeze (I had a USB hub and a card reader dongle and removed them both so I don't know which did it). Note that my Microsoft wireless mouse keyboard (which has a tiny USB transceiver) does not cause any trouble. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1380076 Title: Can't suspend on Surface Pro 3 Status in linux package in Ubuntu: Incomplete Bug description: With my Surface Pro 3 when I suspend from the GUI nothing happens. Doing it manually also fails, and nothing appears in dmesg: #echo mem /sys/power/state Error while writing to stdout write_loop: Invalid argument And, more interestingly: cat /sys/power/state freeze disk Using the not-so-good-and-apparently-unsupported: echo freeze /sys/power/state does seem to successfully suspend, however I cannot resume from this (assumed to be a separate issue). I am using a modified utopic unicorn kernel compiled from git at kernel.ubuntu.com, with the following patch to enable mykeyboard to work: http://www.spinics.net/lists/linux-input/msg34918.html The official kernel behaves identically, as does vanilla 3.17 from the mainline folder of kernel-ppa. WORKAROUND: Use hibernate. --- ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarrad 2491 F pulseaudio /dev/snd/controlC0: jarrad 2491 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=178ac532-25db-4ef3-a587-f1fdd2649bf0 InstallationDate: Installed on 2014-10-10 (57 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140923) MachineType: Microsoft Corporation Surface Pro 3 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.4-surface3 root=UUID=f6c17817-9127-4792-be23-a39a07e7f240 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4 RelatedPackageVersions: linux-restricted-modules-3.16.4-surface3 N/A linux-backports-modules-3.16.4-surface3 N/A linux-firmware 1.135 Tags: utopic Uname: Linux 3.16.4-surface3 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/16/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.11.0350 dmi.board.asset.tag: 0 dmi.board.name: Surface Pro 3 dmi.board.vendor: Microsoft Corporation dmi.board.version: 1 dmi.chassis.asset.tag: 0 dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.11.0350:bd10/16/2014:svnMicrosoftCorporation:pnSurfacePro3:pvr1:rvnMicrosoftCorporation:rnSurfacePro3:rvr1:cvnMicrosoftCorporation:ct9:cvr1: dmi.product.name: Surface Pro 3 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/1380076/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1380076] Re: Can't suspend on Surface Pro 3
Kernel bug 84651 addresses the power button issue. As of today it is still being tested. On my computer (now running 4.0-RC4 with patches but NOT the freeze patch from comment 26) suspending still bounces back, but with their patch it goes to the lock screen mode. I will now try putting that in and see if the it is possible to both suspend and resume. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1380076 Title: Can't suspend on Surface Pro 3 Status in linux package in Ubuntu: Incomplete Bug description: With my Surface Pro 3 when I suspend from the GUI nothing happens. Doing it manually also fails, and nothing appears in dmesg: #echo mem /sys/power/state Error while writing to stdout write_loop: Invalid argument And, more interestingly: cat /sys/power/state freeze disk Using the not-so-good-and-apparently-unsupported: echo freeze /sys/power/state does seem to successfully suspend, however I cannot resume from this (assumed to be a separate issue). I am using a modified utopic unicorn kernel compiled from git at kernel.ubuntu.com, with the following patch to enable mykeyboard to work: http://www.spinics.net/lists/linux-input/msg34918.html The official kernel behaves identically, as does vanilla 3.17 from the mainline folder of kernel-ppa. WORKAROUND: Use hibernate. --- ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarrad 2491 F pulseaudio /dev/snd/controlC0: jarrad 2491 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=178ac532-25db-4ef3-a587-f1fdd2649bf0 InstallationDate: Installed on 2014-10-10 (57 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140923) MachineType: Microsoft Corporation Surface Pro 3 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.4-surface3 root=UUID=f6c17817-9127-4792-be23-a39a07e7f240 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4 RelatedPackageVersions: linux-restricted-modules-3.16.4-surface3 N/A linux-backports-modules-3.16.4-surface3 N/A linux-firmware 1.135 Tags: utopic Uname: Linux 3.16.4-surface3 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/16/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.11.0350 dmi.board.asset.tag: 0 dmi.board.name: Surface Pro 3 dmi.board.vendor: Microsoft Corporation dmi.board.version: 1 dmi.chassis.asset.tag: 0 dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.11.0350:bd10/16/2014:svnMicrosoftCorporation:pnSurfacePro3:pvr1:rvnMicrosoftCorporation:rnSurfacePro3:rvr1:cvnMicrosoftCorporation:ct9:cvr1: dmi.product.name: Surface Pro 3 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/1380076/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1380076] Re: Can't suspend on Surface Pro 3
I got that wrong yesterday, I think. IWhen the freeze patch is installed, it seems to do something akin to suspending, but I haven't figured out how to get it back (not power button or mouse movement). Instead you have to hold the power button long enough to kill it and then start over. Note that this computer bounces back in Windows 8.1 when you try sleep. I understood that a kernel patch had fixed that, but I'm up to date with Windows updates and that's what I see. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1380076 Title: Can't suspend on Surface Pro 3 Status in linux package in Ubuntu: Incomplete Bug description: With my Surface Pro 3 when I suspend from the GUI nothing happens. Doing it manually also fails, and nothing appears in dmesg: #echo mem /sys/power/state Error while writing to stdout write_loop: Invalid argument And, more interestingly: cat /sys/power/state freeze disk Using the not-so-good-and-apparently-unsupported: echo freeze /sys/power/state does seem to successfully suspend, however I cannot resume from this (assumed to be a separate issue). I am using a modified utopic unicorn kernel compiled from git at kernel.ubuntu.com, with the following patch to enable mykeyboard to work: http://www.spinics.net/lists/linux-input/msg34918.html The official kernel behaves identically, as does vanilla 3.17 from the mainline folder of kernel-ppa. WORKAROUND: Use hibernate. --- ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarrad 2491 F pulseaudio /dev/snd/controlC0: jarrad 2491 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=178ac532-25db-4ef3-a587-f1fdd2649bf0 InstallationDate: Installed on 2014-10-10 (57 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140923) MachineType: Microsoft Corporation Surface Pro 3 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.4-surface3 root=UUID=f6c17817-9127-4792-be23-a39a07e7f240 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4 RelatedPackageVersions: linux-restricted-modules-3.16.4-surface3 N/A linux-backports-modules-3.16.4-surface3 N/A linux-firmware 1.135 Tags: utopic Uname: Linux 3.16.4-surface3 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/16/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.11.0350 dmi.board.asset.tag: 0 dmi.board.name: Surface Pro 3 dmi.board.vendor: Microsoft Corporation dmi.board.version: 1 dmi.chassis.asset.tag: 0 dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.11.0350:bd10/16/2014:svnMicrosoftCorporation:pnSurfacePro3:pvr1:rvnMicrosoftCorporation:rnSurfacePro3:rvr1:cvnMicrosoftCorporation:ct9:cvr1: dmi.product.name: Surface Pro 3 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/1380076/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1380076] Re: Can't suspend on Surface Pro 3
I made Akdor's pm-functions patch using 3.19RC3. Suspend did not change at all; it still bounced right back. Note that this kernel is unaware of the battery (I've read that 3.16 kernels don't have that problem) so maybe there is some interaction there. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1380076 Title: Can't suspend on Surface Pro 3 Status in linux package in Ubuntu: Incomplete Bug description: With my Surface Pro 3 when I suspend from the GUI nothing happens. Doing it manually also fails, and nothing appears in dmesg: #echo mem /sys/power/state Error while writing to stdout write_loop: Invalid argument And, more interestingly: cat /sys/power/state freeze disk Using the not-so-good-and-apparently-unsupported: echo freeze /sys/power/state does seem to successfully suspend, however I cannot resume from this (assumed to be a separate issue). I am using a modified utopic unicorn kernel compiled from git at kernel.ubuntu.com, with the following patch to enable mykeyboard to work: http://www.spinics.net/lists/linux-input/msg34918.html The official kernel behaves identically, as does vanilla 3.17 from the mainline folder of kernel-ppa. WORKAROUND: Use hibernate. --- ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarrad 2491 F pulseaudio /dev/snd/controlC0: jarrad 2491 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=178ac532-25db-4ef3-a587-f1fdd2649bf0 InstallationDate: Installed on 2014-10-10 (57 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140923) MachineType: Microsoft Corporation Surface Pro 3 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.4-surface3 root=UUID=f6c17817-9127-4792-be23-a39a07e7f240 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4 RelatedPackageVersions: linux-restricted-modules-3.16.4-surface3 N/A linux-backports-modules-3.16.4-surface3 N/A linux-firmware 1.135 Tags: utopic Uname: Linux 3.16.4-surface3 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/16/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.11.0350 dmi.board.asset.tag: 0 dmi.board.name: Surface Pro 3 dmi.board.vendor: Microsoft Corporation dmi.board.version: 1 dmi.chassis.asset.tag: 0 dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.11.0350:bd10/16/2014:svnMicrosoftCorporation:pnSurfacePro3:pvr1:rvnMicrosoftCorporation:rnSurfacePro3:rvr1:cvnMicrosoftCorporation:ct9:cvr1: dmi.product.name: Surface Pro 3 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/1380076/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1079440] Re: 8086:27a2 [Dell MP061] i945: Random complete freeze using dual monitors
Good question, Chris, Again my hardware is HP mini 110, not Dell. The xorg people fixed my problem seemingly quite completely around 8 months ago (before 13.04). I don't use dual monitors on a regular basis, so I don't know any more than that. Keith On Thu, Nov 21, 2013 at 3:21 AM, cmavr8 1079...@bugs.launchpad.net wrote: Christopher, I guess this is an automated response but I'll ask you anyway: How would I know if this is against the kernel or the graphics driver? Does anyone else have a clue? Keith, why are you suggesting that it's been fixed? Comments 56, 57, 58 and mine suggest otherwise... Thanks :) Chris -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1079440 Title: 8086:27a2 [Dell MP061] i945: Random complete freeze using dual monitors Status in The Linux Kernel: Fix Released Status in “linux” package in Ubuntu: Incomplete Bug description: I can run all day without problems if I boot up using just the laptop screen, but using an external monitor to extend the viewing area I get a crash after about an hour or two of use, 100% guaranteed. It seems completely random. I was getting similar crashes in 12.04 but using 2d fixed that. Now with 12.10 I have to use 3d. By complete freeze I mean no mouse click or key press does anything but I can still see the cursor move with the mouse. When I first installed 12.10 and the system froze I could use ctrl- alt-F1 to restart the display manager, but since a recent system update ctrl-alt-F1 just switches to a black screen (no text). Typing any kind of command seems to have no effect, so it is more than the characters simply not displaying. So this recent system update seems to make the crash more severe when it happens. Description: Ubuntu 12.10 Release: 12.10 compiz: Installed: 1:0.9.8.4+bzr3407-0ubuntu1 Candidate: 1:0.9.8.4+bzr3407-0ubuntu1 Version table: *** 1:0.9.8.4+bzr3407-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ quantal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:0.9.8.4-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: compiz 1:0.9.8.4+bzr3407-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Thu Nov 15 14:13:02 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: vboxhost, 4.2.4, 3.5.0-18-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:01cd] Subsystem: Dell Device [1028:01cd] InstallationDate: Installed on 2012-10-31 (15 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: Dell Inc. MP061 MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-18-generic root=UUID=0650f48a-9821-4f03-aad9-130f0ff78d65 ro quiet splash vt.handoff=7 SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0FF049 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd12/18/2006:svnDellInc.:pnMP061:pvr:rvnDellInc.:rn0FF049:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: MP061 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.8.4+bzr3407-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1079440/+subscriptions -- You received this bug notification because you are a
Re: [Kernel-packages] [Bug 1079440] Re: 8086:27a2 [Dell MP061] i945: Random complete freeze using dual monitors
I don't know why you are sending this. So far as I know the problem has been fixed--but I'm not doing dual monitor stuff now and not inclined to make a new test. Keith On Nov 20, 2013 7:41 PM, Christopher M. Penalver christopher.m.penal...@gmail.com wrote: cmavr8, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via: ubuntu-bug linux For more on this, please read the official Ubuntu documentation: Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette When opening up the new report, please feel free to subscribe me to it. Please note, not filing a new report would delay your problem being addressed as quickly as possible. No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions or comments, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly. Thank you for your understanding. ** Summary changed: - [Dell MP061] i945: Random complete freeze using dual monitors + 8086:27a2 [Dell MP061] i945: Random complete freeze using dual monitors ** Attachment removed: Xorg.0.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1079440/+attachment/3913504/+files/Xorg.0.log -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1079440 Title: 8086:27a2 [Dell MP061] i945: Random complete freeze using dual monitors Status in The Linux Kernel: Fix Released Status in “linux” package in Ubuntu: Incomplete Bug description: I can run all day without problems if I boot up using just the laptop screen, but using an external monitor to extend the viewing area I get a crash after about an hour or two of use, 100% guaranteed. It seems completely random. I was getting similar crashes in 12.04 but using 2d fixed that. Now with 12.10 I have to use 3d. By complete freeze I mean no mouse click or key press does anything but I can still see the cursor move with the mouse. When I first installed 12.10 and the system froze I could use ctrl- alt-F1 to restart the display manager, but since a recent system update ctrl-alt-F1 just switches to a black screen (no text). Typing any kind of command seems to have no effect, so it is more than the characters simply not displaying. So this recent system update seems to make the crash more severe when it happens. Description: Ubuntu 12.10 Release: 12.10 compiz: Installed: 1:0.9.8.4+bzr3407-0ubuntu1 Candidate: 1:0.9.8.4+bzr3407-0ubuntu1 Version table: *** 1:0.9.8.4+bzr3407-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ quantal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:0.9.8.4-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: compiz 1:0.9.8.4+bzr3407-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Thu Nov 15 14:13:02 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: vboxhost, 4.2.4, 3.5.0-18-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:01cd] Subsystem: Dell Device [1028:01cd] InstallationDate: Installed on 2012-10-31 (15 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: Dell Inc. MP061 MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-18-generic root=UUID=0650f48a-9821-4f03-aad9-130f0ff78d65 ro quiet splash vt.handoff=7 SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0FF049 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8
Re: [Kernel-packages] [Bug 1079440] Re: i945: Random complete freeze using dual monitors
Christopher, My problem is (was?) with an HP Mini 110 not a Dell computer. I haven't tried it recently so I can't say if it was fixed or not. Thanks, Keith On Tue, Nov 19, 2013 at 7:09 AM, Christopher M. Penalver christopher.m.penal...@gmail.com wrote: mikesmithv, as per http://www.dell.com/support/drivers/us/en/19/DriverDetails?driverId=R243190fileId=2731117184 an update is available for your BIOS (A10). If you update to this following https://help.ubuntu.com/community/BiosUpdate , does it change anything? If not, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Thank you for your understanding. ** Tags added: bios-outdated-a10 ** Changed in: linux (Ubuntu) Status: Triaged = Incomplete -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1079440 Title: i945: Random complete freeze using dual monitors Status in The Linux Kernel: Fix Released Status in “linux” package in Ubuntu: Incomplete Bug description: I can run all day without problems if I boot up using just the laptop screen, but using an external monitor to extend the viewing area I get a crash after about an hour or two of use, 100% guaranteed. It seems completely random. I was getting similar crashes in 12.04 but using 2d fixed that. Now with 12.10 I have to use 3d. By complete freeze I mean no mouse click or key press does anything but I can still see the cursor move with the mouse. When I first installed 12.10 and the system froze I could use ctrl- alt-F1 to restart the display manager, but since a recent system update ctrl-alt-F1 just switches to a black screen (no text). Typing any kind of command seems to have no effect, so it is more than the characters simply not displaying. So this recent system update seems to make the crash more severe when it happens. Description: Ubuntu 12.10 Release: 12.10 compiz: Installed: 1:0.9.8.4+bzr3407-0ubuntu1 Candidate: 1:0.9.8.4+bzr3407-0ubuntu1 Version table: *** 1:0.9.8.4+bzr3407-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ quantal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:0.9.8.4-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: compiz 1:0.9.8.4+bzr3407-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Thu Nov 15 14:13:02 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: vboxhost, 4.2.4, 3.5.0-18-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:01cd] Subsystem: Dell Device [1028:01cd] InstallationDate: Installed on 2012-10-31 (15 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: Dell Inc. MP061 MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-18-generic root=UUID=0650f48a-9821-4f03-aad9-130f0ff78d65 ro quiet splash vt.handoff=7 SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0FF049 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd12/18/2006:svnDellInc.:pnMP061:pvr:rvnDellInc.:rn0FF049:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: MP061 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.8.4+bzr3407-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
Re: [Kernel-packages] [Bug 1079440] Re: [Dell MP061] i945: Random complete freeze using dual monitors
I don't think I have a new bug. Keith On Nov 19, 2013 7:15 PM, Christopher M. Penalver christopher.m.penal...@gmail.com wrote: Keith McClelland, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via: ubuntu-bug linux For more on this, please read the official Ubuntu documentation: Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette When opening up the new report, please feel free to subscribe me to it. Please note, not filing a new report would delay your problem being addressed as quickly as possible. No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions or comments, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly. Thank you for your understanding. ** Summary changed: - i945: Random complete freeze using dual monitors + [Dell MP061] i945: Random complete freeze using dual monitors -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1079440 Title: [Dell MP061] i945: Random complete freeze using dual monitors Status in The Linux Kernel: Fix Released Status in “linux” package in Ubuntu: Incomplete Bug description: I can run all day without problems if I boot up using just the laptop screen, but using an external monitor to extend the viewing area I get a crash after about an hour or two of use, 100% guaranteed. It seems completely random. I was getting similar crashes in 12.04 but using 2d fixed that. Now with 12.10 I have to use 3d. By complete freeze I mean no mouse click or key press does anything but I can still see the cursor move with the mouse. When I first installed 12.10 and the system froze I could use ctrl- alt-F1 to restart the display manager, but since a recent system update ctrl-alt-F1 just switches to a black screen (no text). Typing any kind of command seems to have no effect, so it is more than the characters simply not displaying. So this recent system update seems to make the crash more severe when it happens. Description: Ubuntu 12.10 Release: 12.10 compiz: Installed: 1:0.9.8.4+bzr3407-0ubuntu1 Candidate: 1:0.9.8.4+bzr3407-0ubuntu1 Version table: *** 1:0.9.8.4+bzr3407-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ quantal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:0.9.8.4-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: compiz 1:0.9.8.4+bzr3407-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Thu Nov 15 14:13:02 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: vboxhost, 4.2.4, 3.5.0-18-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:01cd] Subsystem: Dell Device [1028:01cd] InstallationDate: Installed on 2012-10-31 (15 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: Dell Inc. MP061 MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-18-generic root=UUID=0650f48a-9821-4f03-aad9-130f0ff78d65 ro quiet splash vt.handoff=7 SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0FF049 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd12/18/2006:svnDellInc.:pnMP061:pvr:rvnDellInc.:rn0FF049:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: MP061 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.8.4+bzr3407-0ubuntu1 version.ia32-libs: ia32
