[Kernel-packages] [Bug 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59
If this kernel is not going to hit -updates shortly (i.e. days), can something be done to pull or downgrade the broken kernel? At least revert linux-image-generic to depend back on linux- image-4.4.0-57-generic which doesn't have the issues and will stop more people from upgrading to a broken kernel. Having this sort of break in an LTS kernel is not inspiring at all. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1655842 Title: "Out of memory" errors after upgrade to 4.4.0-59 Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: I recently replaced some Xenial servers, and started experiencing "Out of memory" problems with the default kernel. We bake Amazon AMIs based on an official Ubuntu-provided image (ami- e6b58e85, in ap-southeast-2, from https://cloud- images.ubuntu.com/locator/ec2/). Previous versions of our AMI included "4.4.0-57-generic", but the latest version picked up "4.4.0-59-generic" as part of a "dist-upgrade". Instances booted using the new AMI have been using more memory, and experiencing OOM issues - sometimes during boot, and sometimes a while afterwards. An example from the system log is: [ 130.113411] cloud-init[1560]: Cloud-init v. 0.7.8 running 'modules:final' at Wed, 11 Jan 2017 22:07:53 +. Up 29.28 seconds. [ 130.124219] cloud-init[1560]: Cloud-init v. 0.7.8 finished at Wed, 11 Jan 2017 22:09:35 +. Datasource DataSourceEc2. Up 130.09 seconds [29871.137128] Out of memory: Kill process 2920 (ruby) score 107 or sacrifice child [29871.140816] Killed process 2920 (ruby) total-vm:675048kB, anon-rss:51184kB, file-rss:2164kB [29871.449209] Out of memory: Kill process 3257 (splunkd) score 97 or sacrifice child [29871.453282] Killed process 3258 (splunkd) total-vm:66272kB, anon-rss:6676kB, file-rss:0kB [29871.677910] Out of memory: Kill process 2647 (fluentd) score 51 or sacrifice child [29871.681872] Killed process 2647 (fluentd) total-vm:117944kB, anon-rss:23956kB, file-rss:1356kB I have a hunch that this may be related to the fix for https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647400, introduced in linux (4.4.0-58.79). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: User Name 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 06:29 seq crw-rw 1 root audio 116, 33 Jan 12 06:29 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 12 06:38:45 2017 Ec2AMI: ami-0f93966c Ec2AMIManifest: (unknown) Ec2AvailabilityZone: ap-southeast-2a Ec2InstanceType: t2.nano Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Xen HVM domU PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic root=UUID=fb0fef08-f3c5-40bf-9776-f7ba00fe72be ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2016 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd12/09/2016:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1589397] Re: kernel panic connecting display port to Dell Latitude E7470
Looks like it is not working today with any of the above kernels - I had multiple screens working ok on Friday with the mainline kernel, but today it is not working. I'm not sure what changed, I will attach the dpkg log, but am going to have to go to windows as this is a work laptop and i can't spend more time looking at this. Hopefully I can help debug in future if I get time to repartition again or perhaps with a beta live-usb image -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1589397 Title: kernel panic connecting display port to Dell Latitude E7470 Status in linux package in Ubuntu: Confirmed Bug description: Connecting an external Display Port screen wither via the dell E-Port plus or directly via the miniDP causes a kernel panic. The crash is not always immediate, if the internal screen is disabled when docked, then the external screen may work, though undocking and docking a second time usually crashes it. Kernels crashing for me are 4.4.0-21-generic and 4.4.0-22-generic. Testing with the mainline kernel linux- image-4.4.12-040412-generic=4.4.12-040412.201606011712 has not yet caused the panic ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anton 1885 F pulseaudio CurrentDesktop: Unity Date: Mon Jun 6 08:25:23 2016 InstallationDate: Installed on 2016-06-01 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor Bus 001 Device 002: ID 1bcf:28b8 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude E7470 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=UUID=7bebd315-73de-4106-9fef-07139edd58f2 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.3 dmi.board.name: 0T6HHJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.3:bd04/18/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7470 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589397/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1589397] Re: kernel panic connecting display port to Dell Latitude E7470
** Attachment added: "dpkg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589397/+attachment/4677986/+files/dpkg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1589397 Title: kernel panic connecting display port to Dell Latitude E7470 Status in linux package in Ubuntu: Confirmed Bug description: Connecting an external Display Port screen wither via the dell E-Port plus or directly via the miniDP causes a kernel panic. The crash is not always immediate, if the internal screen is disabled when docked, then the external screen may work, though undocking and docking a second time usually crashes it. Kernels crashing for me are 4.4.0-21-generic and 4.4.0-22-generic. Testing with the mainline kernel linux- image-4.4.12-040412-generic=4.4.12-040412.201606011712 has not yet caused the panic ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anton 1885 F pulseaudio CurrentDesktop: Unity Date: Mon Jun 6 08:25:23 2016 InstallationDate: Installed on 2016-06-01 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor Bus 001 Device 002: ID 1bcf:28b8 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude E7470 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=UUID=7bebd315-73de-4106-9fef-07139edd58f2 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.3 dmi.board.name: 0T6HHJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.3:bd04/18/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7470 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589397/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1589397] [NEW] kernel panic connecting display port to Dell Latitude E7470
Public bug reported: Connecting an external Display Port screen wither via the dell E-Port plus or directly via the miniDP causes a kernel panic. The crash is not always immediate, if the internal screen is disabled when docked, then the external screen may work, though undocking and docking a second time usually crashes it. Kernels crashing for me are 4.4.0-21-generic and 4.4.0-22-generic. Testing with the mainline kernel linux- image-4.4.12-040412-generic=4.4.12-040412.201606011712 has not yet caused the panic ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anton 1885 F pulseaudio CurrentDesktop: Unity Date: Mon Jun 6 08:25:23 2016 InstallationDate: Installed on 2016-06-01 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor Bus 001 Device 002: ID 1bcf:28b8 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude E7470 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=UUID=7bebd315-73de-4106-9fef-07139edd58f2 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.3 dmi.board.name: 0T6HHJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.3:bd04/18/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7470 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1589397 Title: kernel panic connecting display port to Dell Latitude E7470 Status in linux package in Ubuntu: New Bug description: Connecting an external Display Port screen wither via the dell E-Port plus or directly via the miniDP causes a kernel panic. The crash is not always immediate, if the internal screen is disabled when docked, then the external screen may work, though undocking and docking a second time usually crashes it. Kernels crashing for me are 4.4.0-21-generic and 4.4.0-22-generic. Testing with the mainline kernel linux- image-4.4.12-040412-generic=4.4.12-040412.201606011712 has not yet caused the panic ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anton 1885 F pulseaudio CurrentDesktop: Unity Date: Mon Jun 6 08:25:23 2016 InstallationDate: Installed on 2016-06-01 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor Bus 001 Device 002: ID 1bcf:28b8 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude E7470 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=UUID=7bebd315-73de-4106-9fef-07139edd58f2 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.3 dmi.board.name: 0T6HHJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.3:bd04/18/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7470 dmi.sys.vendor: Dell Inc. To
[Kernel-packages] [Bug 1589397] Re: kernel panic connecting display port to Dell Latitude E7470
Possibly related to +1560524 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1589397 Title: kernel panic connecting display port to Dell Latitude E7470 Status in linux package in Ubuntu: New Bug description: Connecting an external Display Port screen wither via the dell E-Port plus or directly via the miniDP causes a kernel panic. The crash is not always immediate, if the internal screen is disabled when docked, then the external screen may work, though undocking and docking a second time usually crashes it. Kernels crashing for me are 4.4.0-21-generic and 4.4.0-22-generic. Testing with the mainline kernel linux- image-4.4.12-040412-generic=4.4.12-040412.201606011712 has not yet caused the panic ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anton 1885 F pulseaudio CurrentDesktop: Unity Date: Mon Jun 6 08:25:23 2016 InstallationDate: Installed on 2016-06-01 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor Bus 001 Device 002: ID 1bcf:28b8 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude E7470 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=UUID=7bebd315-73de-4106-9fef-07139edd58f2 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.3 dmi.board.name: 0T6HHJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.3:bd04/18/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7470 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589397/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1589397] Re: kernel panic connecting display port to Dell Latitude E7470
** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589397/+attachment/4677894/+files/kern.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1589397 Title: kernel panic connecting display port to Dell Latitude E7470 Status in linux package in Ubuntu: New Bug description: Connecting an external Display Port screen wither via the dell E-Port plus or directly via the miniDP causes a kernel panic. The crash is not always immediate, if the internal screen is disabled when docked, then the external screen may work, though undocking and docking a second time usually crashes it. Kernels crashing for me are 4.4.0-21-generic and 4.4.0-22-generic. Testing with the mainline kernel linux- image-4.4.12-040412-generic=4.4.12-040412.201606011712 has not yet caused the panic ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anton 1885 F pulseaudio CurrentDesktop: Unity Date: Mon Jun 6 08:25:23 2016 InstallationDate: Installed on 2016-06-01 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor Bus 001 Device 002: ID 1bcf:28b8 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude E7470 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=UUID=7bebd315-73de-4106-9fef-07139edd58f2 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.3 dmi.board.name: 0T6HHJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.3:bd04/18/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7470 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589397/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1560524] Re: Latitude E7470 crashes in DRM driver after connecting to DELL EPORT docking station
Installing 4.4.12-040412-generic from http://kernel.ubuntu.com/~kernel- ppa/mainline/?C=N;O=D and I am able to run a 4k screen through the dock and DP with the internal screen running, which I couldn't do successfully before. Worth testing if you also have this problem. Also check your BIOS version sudo dmidecode |grep 'BIOS Information' -A5|grep Version Version: 1.5.3 Note that I also applied a dock-specific firmware update while in windows, though it isn't entirely clear if it was a windows driver or if it changes any firmware stored within the dock ( http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=WNV4C ) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1560524 Title: Latitude E7470 crashes in DRM driver after connecting to DELL EPORT docking station Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: After attaching latitude E7470 laptop running Linux sashas-work 4.2.0-30-generic #36-Ubuntu SMP Fri Feb 26 00:58:07 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Distributor ID: Ubuntu Description: Ubuntu 15.10 Release: 15.10 Codename: wily modinfo i915 filename: /lib/modules/4.2.0-30-generic/updates/dkms/i915.ko license:GPL and additional rights description:Intel Graphics author: Intel Corporation author: Tungsten Graphics, Inc. firmware: i915/skl_dmc_ver1.bin srcversion: D8F27CD62AA99DAC898A0F1 alias: pci:v8086d5A84sv*sd*bc03sc*i* alias: pci:v8086d1A84sv*sd*bc03sc*i* alias: pci:v8086d0A84sv*sd*bc03sc*i* alias: pci:v8086d192Asv*sd*bc03sc*i* alias: pci:v8086d192Bsv*sd*bc03sc*i* alias: pci:v8086d1926sv*sd*bc03sc*i* alias: pci:v8086d191Dsv*sd*bc03sc*i* alias: pci:v8086d191Asv*sd*bc03sc*i* alias: pci:v8086d191Bsv*sd*bc03sc*i* alias: pci:v8086d1912sv*sd*bc03sc*i* alias: pci:v8086d191Esv*sd*bc03sc*i* alias: pci:v8086d1921sv*sd*bc03sc*i* alias: pci:v8086d1916sv*sd*bc03sc*i* alias: pci:v8086d190Asv*sd*bc03sc*i* alias: pci:v8086d190Bsv*sd*bc03sc*i* alias: pci:v8086d1902sv*sd*bc03sc*i* alias: pci:v8086d190Esv*sd*bc03sc*i* alias: pci:v8086d1906sv*sd*bc03sc*i* alias: pci:v8086d22B3sv*sd*bc03sc*i* alias: pci:v8086d22B2sv*sd*bc03sc*i* alias: pci:v8086d22B1sv*sd*bc03sc*i* alias: pci:v8086d22B0sv*sd*bc03sc*i* alias: pci:v8086d162Dsv*sd*bc03sc*i* alias: pci:v8086d162Asv*sd*bc03sc*i* alias: pci:v8086d162Esv*sd*bc03sc*i* alias: pci:v8086d162Bsv*sd*bc03sc*i* alias: pci:v8086d1626sv*sd*bc03sc*i* alias: pci:v8086d1622sv*sd*bc03sc*i* alias: pci:v8086d161Dsv*sd*bc03sc*i* alias: pci:v8086d161Asv*sd*bc03sc*i* alias: pci:v8086d160Dsv*sd*bc03sc*i* alias: pci:v8086d160Asv*sd*bc03sc*i* alias: pci:v8086d161Esv*sd*bc03sc*i* alias: pci:v8086d161Bsv*sd*bc03sc*i* alias: pci:v8086d1616sv*sd*bc03sc*i* alias: pci:v8086d1612sv*sd*bc03sc*i* alias: pci:v8086d160Esv*sd*bc03sc*i* alias: pci:v8086d160Bsv*sd*bc03sc*i* alias: pci:v8086d1606sv*sd*bc03sc*i* alias: pci:v8086d1602sv*sd*bc03sc*i* alias: pci:v8086d0155sv*sd*bc03sc*i* alias: pci:v8086d0157sv*sd*bc03sc*i* alias: pci:v8086d0F33sv*sd*bc03sc*i* alias: pci:v8086d0F32sv*sd*bc03sc*i* alias: pci:v8086d0F31sv*sd*bc03sc*i* alias: pci:v8086d0F30sv*sd*bc03sc*i* alias: pci:v8086d0D26sv*sd*bc03sc*i* alias: pci:v8086d0D16sv*sd*bc03sc*i* alias: pci:v8086d0D06sv*sd*bc03sc*i* alias: pci:v8086d0A2Esv*sd*bc03sc*i* alias: pci:v8086d0A1Esv*sd*bc03sc*i* alias: pci:v8086d0A0Esv*sd*bc03sc*i* alias: pci:v8086d0A26sv*sd*bc03sc*i* alias: pci:v8086d0A16sv*sd*bc03sc*i* alias: pci:v8086d0A06sv*sd*bc03sc*i* alias: pci:v8086d0C26sv*sd*bc03sc*i* alias: pci:v8086d0C16sv*sd*bc03sc*i* alias: pci:v8086d0C06sv*sd*bc03sc*i* alias: pci:v8086d0426sv*sd*bc03sc*i* alias:
[Kernel-packages] [Bug 1560524] Re: Latitude E7470 crashes in DRM driver after connecting to DELL EPORT docking station
I've just updated the dell bios to 1.5.3 and the crash still occurs. I noticed that plugging into a 4k tv via the builtin mini display port also causes the crash, though not always. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1560524 Title: Latitude E7470 crashes in DRM driver after connecting to DELL EPORT docking station Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: After attaching latitude E7470 laptop running Linux sashas-work 4.2.0-30-generic #36-Ubuntu SMP Fri Feb 26 00:58:07 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Distributor ID: Ubuntu Description: Ubuntu 15.10 Release: 15.10 Codename: wily modinfo i915 filename: /lib/modules/4.2.0-30-generic/updates/dkms/i915.ko license:GPL and additional rights description:Intel Graphics author: Intel Corporation author: Tungsten Graphics, Inc. firmware: i915/skl_dmc_ver1.bin srcversion: D8F27CD62AA99DAC898A0F1 alias: pci:v8086d5A84sv*sd*bc03sc*i* alias: pci:v8086d1A84sv*sd*bc03sc*i* alias: pci:v8086d0A84sv*sd*bc03sc*i* alias: pci:v8086d192Asv*sd*bc03sc*i* alias: pci:v8086d192Bsv*sd*bc03sc*i* alias: pci:v8086d1926sv*sd*bc03sc*i* alias: pci:v8086d191Dsv*sd*bc03sc*i* alias: pci:v8086d191Asv*sd*bc03sc*i* alias: pci:v8086d191Bsv*sd*bc03sc*i* alias: pci:v8086d1912sv*sd*bc03sc*i* alias: pci:v8086d191Esv*sd*bc03sc*i* alias: pci:v8086d1921sv*sd*bc03sc*i* alias: pci:v8086d1916sv*sd*bc03sc*i* alias: pci:v8086d190Asv*sd*bc03sc*i* alias: pci:v8086d190Bsv*sd*bc03sc*i* alias: pci:v8086d1902sv*sd*bc03sc*i* alias: pci:v8086d190Esv*sd*bc03sc*i* alias: pci:v8086d1906sv*sd*bc03sc*i* alias: pci:v8086d22B3sv*sd*bc03sc*i* alias: pci:v8086d22B2sv*sd*bc03sc*i* alias: pci:v8086d22B1sv*sd*bc03sc*i* alias: pci:v8086d22B0sv*sd*bc03sc*i* alias: pci:v8086d162Dsv*sd*bc03sc*i* alias: pci:v8086d162Asv*sd*bc03sc*i* alias: pci:v8086d162Esv*sd*bc03sc*i* alias: pci:v8086d162Bsv*sd*bc03sc*i* alias: pci:v8086d1626sv*sd*bc03sc*i* alias: pci:v8086d1622sv*sd*bc03sc*i* alias: pci:v8086d161Dsv*sd*bc03sc*i* alias: pci:v8086d161Asv*sd*bc03sc*i* alias: pci:v8086d160Dsv*sd*bc03sc*i* alias: pci:v8086d160Asv*sd*bc03sc*i* alias: pci:v8086d161Esv*sd*bc03sc*i* alias: pci:v8086d161Bsv*sd*bc03sc*i* alias: pci:v8086d1616sv*sd*bc03sc*i* alias: pci:v8086d1612sv*sd*bc03sc*i* alias: pci:v8086d160Esv*sd*bc03sc*i* alias: pci:v8086d160Bsv*sd*bc03sc*i* alias: pci:v8086d1606sv*sd*bc03sc*i* alias: pci:v8086d1602sv*sd*bc03sc*i* alias: pci:v8086d0155sv*sd*bc03sc*i* alias: pci:v8086d0157sv*sd*bc03sc*i* alias: pci:v8086d0F33sv*sd*bc03sc*i* alias: pci:v8086d0F32sv*sd*bc03sc*i* alias: pci:v8086d0F31sv*sd*bc03sc*i* alias: pci:v8086d0F30sv*sd*bc03sc*i* alias: pci:v8086d0D26sv*sd*bc03sc*i* alias: pci:v8086d0D16sv*sd*bc03sc*i* alias: pci:v8086d0D06sv*sd*bc03sc*i* alias: pci:v8086d0A2Esv*sd*bc03sc*i* alias: pci:v8086d0A1Esv*sd*bc03sc*i* alias: pci:v8086d0A0Esv*sd*bc03sc*i* alias: pci:v8086d0A26sv*sd*bc03sc*i* alias: pci:v8086d0A16sv*sd*bc03sc*i* alias: pci:v8086d0A06sv*sd*bc03sc*i* alias: pci:v8086d0C26sv*sd*bc03sc*i* alias: pci:v8086d0C16sv*sd*bc03sc*i* alias: pci:v8086d0C06sv*sd*bc03sc*i* alias: pci:v8086d0426sv*sd*bc03sc*i* alias: pci:v8086d0416sv*sd*bc03sc*i* alias: pci:v8086d0406sv*sd*bc03sc*i* alias: pci:v8086d0D2Esv*sd*bc03sc*i* alias: pci:v8086d0D1Esv*sd*bc03sc*i* alias: pci:v8086d0D0Esv*sd*bc03sc*i* alias: pci:v8086d0D2Bsv*sd*bc03sc*i* alias: pci:v8086d0D1Bsv*sd*bc03sc*i* alias: pci:v8086d0D0Bsv*sd*bc03sc*i* alias: pci:v8086d0D2Asv*sd*bc03sc*i* alias:
[Kernel-packages] [Bug 1560524] Re: Latitude E7470 crashes in DRM driver after connecting to DELL EPORT docking station
@combnin re #11 - where did you get that kernel? I think I also have the same iisue on an E7470 running 16.04. I can make the external screen work through DP of the dock if I disable the internal one, but trying to enable both either crashes instantly or shortly after the mouse focuses on the external display. ** Attachment added: "crash kernel log" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1560524/+attachment/4675190/+files/crash.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/1560524 Title: Latitude E7470 crashes in DRM driver after connecting to DELL EPORT docking station Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: After attaching latitude E7470 laptop running Linux sashas-work 4.2.0-30-generic #36-Ubuntu SMP Fri Feb 26 00:58:07 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Distributor ID: Ubuntu Description: Ubuntu 15.10 Release: 15.10 Codename: wily modinfo i915 filename: /lib/modules/4.2.0-30-generic/updates/dkms/i915.ko license:GPL and additional rights description:Intel Graphics author: Intel Corporation author: Tungsten Graphics, Inc. firmware: i915/skl_dmc_ver1.bin srcversion: D8F27CD62AA99DAC898A0F1 alias: pci:v8086d5A84sv*sd*bc03sc*i* alias: pci:v8086d1A84sv*sd*bc03sc*i* alias: pci:v8086d0A84sv*sd*bc03sc*i* alias: pci:v8086d192Asv*sd*bc03sc*i* alias: pci:v8086d192Bsv*sd*bc03sc*i* alias: pci:v8086d1926sv*sd*bc03sc*i* alias: pci:v8086d191Dsv*sd*bc03sc*i* alias: pci:v8086d191Asv*sd*bc03sc*i* alias: pci:v8086d191Bsv*sd*bc03sc*i* alias: pci:v8086d1912sv*sd*bc03sc*i* alias: pci:v8086d191Esv*sd*bc03sc*i* alias: pci:v8086d1921sv*sd*bc03sc*i* alias: pci:v8086d1916sv*sd*bc03sc*i* alias: pci:v8086d190Asv*sd*bc03sc*i* alias: pci:v8086d190Bsv*sd*bc03sc*i* alias: pci:v8086d1902sv*sd*bc03sc*i* alias: pci:v8086d190Esv*sd*bc03sc*i* alias: pci:v8086d1906sv*sd*bc03sc*i* alias: pci:v8086d22B3sv*sd*bc03sc*i* alias: pci:v8086d22B2sv*sd*bc03sc*i* alias: pci:v8086d22B1sv*sd*bc03sc*i* alias: pci:v8086d22B0sv*sd*bc03sc*i* alias: pci:v8086d162Dsv*sd*bc03sc*i* alias: pci:v8086d162Asv*sd*bc03sc*i* alias: pci:v8086d162Esv*sd*bc03sc*i* alias: pci:v8086d162Bsv*sd*bc03sc*i* alias: pci:v8086d1626sv*sd*bc03sc*i* alias: pci:v8086d1622sv*sd*bc03sc*i* alias: pci:v8086d161Dsv*sd*bc03sc*i* alias: pci:v8086d161Asv*sd*bc03sc*i* alias: pci:v8086d160Dsv*sd*bc03sc*i* alias: pci:v8086d160Asv*sd*bc03sc*i* alias: pci:v8086d161Esv*sd*bc03sc*i* alias: pci:v8086d161Bsv*sd*bc03sc*i* alias: pci:v8086d1616sv*sd*bc03sc*i* alias: pci:v8086d1612sv*sd*bc03sc*i* alias: pci:v8086d160Esv*sd*bc03sc*i* alias: pci:v8086d160Bsv*sd*bc03sc*i* alias: pci:v8086d1606sv*sd*bc03sc*i* alias: pci:v8086d1602sv*sd*bc03sc*i* alias: pci:v8086d0155sv*sd*bc03sc*i* alias: pci:v8086d0157sv*sd*bc03sc*i* alias: pci:v8086d0F33sv*sd*bc03sc*i* alias: pci:v8086d0F32sv*sd*bc03sc*i* alias: pci:v8086d0F31sv*sd*bc03sc*i* alias: pci:v8086d0F30sv*sd*bc03sc*i* alias: pci:v8086d0D26sv*sd*bc03sc*i* alias: pci:v8086d0D16sv*sd*bc03sc*i* alias: pci:v8086d0D06sv*sd*bc03sc*i* alias: pci:v8086d0A2Esv*sd*bc03sc*i* alias: pci:v8086d0A1Esv*sd*bc03sc*i* alias: pci:v8086d0A0Esv*sd*bc03sc*i* alias: pci:v8086d0A26sv*sd*bc03sc*i* alias: pci:v8086d0A16sv*sd*bc03sc*i* alias: pci:v8086d0A06sv*sd*bc03sc*i* alias: pci:v8086d0C26sv*sd*bc03sc*i* alias: pci:v8086d0C16sv*sd*bc03sc*i* alias: pci:v8086d0C06sv*sd*bc03sc*i* alias: pci:v8086d0426sv*sd*bc03sc*i* alias: pci:v8086d0416sv*sd*bc03sc*i* alias: pci:v8086d0406sv*sd*bc03sc*i* alias: pci:v8086d0D2Esv*sd*bc03sc*i* alias: pci:v8086d0D1Esv*sd*bc03sc*i* alias:
[Kernel-packages] [Bug 1213035] Re: 8086:1502 [Lenovo ThinkPad W530] e1000e module sometimes prevents suspend to ram
I am still being affected by this ** Changed in: linux (Ubuntu) Status: Expired = New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1213035 Title: 8086:1502 [Lenovo ThinkPad W530] e1000e module sometimes prevents suspend to ram Status in “linux” package in Ubuntu: Confirmed Bug description: Sometimes, usually towards the end of the day, I find my e100e module does not allow the system to suspend. I do use the ethernet adapter, and it only has occurred after having been connected to ethernet. The following is seen in dmsg: [40697.709402] Freezing user space processes ... (elapsed 0.01 seconds) done. [40697.724258] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done. [40697.740285] Suspending console(s) (use no_console_suspend to debug) [40697.872196] sd 0:0:0:0: [sda] Synchronizing SCSI cache [40698.041526] sd 0:0:0:0: [sda] Stopping disk [40698.714054] pci_pm_suspend(): e1000_suspend+0x0/0x20 [e1000e] returns -2 [40698.714058] dpm_run_callback(): pci_pm_suspend+0x0/0x140 returns -2 [40698.714061] PM: Device :00:19.0 failed to suspend async: error -2 [40698.714100] PM: Some devices failed to suspend WORKAROUND: rmmod e100e and I can suspend again. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-27-generic 3.8.0-27.40 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anton 3094 F pulseaudio /dev/snd/controlC0: anton 3094 F pulseaudio Date: Thu Aug 15 17:22:00 2013 HibernationDevice: RESUME=UUID=471df139-754b-43b4-9979-4d334871c53e InstallationDate: Installed on 2013-07-05 (40 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: LENOVO 24491D1 MarkForUpload: True ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-27-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash nox2apic RelatedPackageVersions: linux-restricted-modules-3.8.0-27-generic N/A linux-backports-modules-3.8.0-27-generic N/A linux-firmware1.106 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G5ET92WW (2.52 ) dmi.board.asset.tag: Not Available dmi.board.name: 24491D1 dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG5ET92WW(2.52):bd02/27/2013:svnLENOVO:pn24491D1:pvrThinkPadW530:rvnLENOVO:rn24491D1:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 24491D1 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213035/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1213035] Re: 8086:1502 [Lenovo ThinkPad W530] e1000e module sometimes prevents suspend to ram
Hi Christopher @penalvch, thanks for the update. Given the intermittent nature of the bug (not every suspend is prevented from succeeding) it is going to be incredibly difficult for me to reproduce on a livecd. Has anything changed in this driver that makes you think it will be better for me? It hasn't changed between raring and saucy. Is there a possibility of trying only a newer kernel from trusty perhaps, then I could use it for a week as normal and see if the issue still presents itself? Perhaps there is some debug output I could gather that might point to a cause? This might help determine if undocking is involved as Tim mentions -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1213035 Title: 8086:1502 [Lenovo ThinkPad W530] e1000e module sometimes prevents suspend to ram Status in “linux” package in Ubuntu: Incomplete Bug description: Sometimes, usually towards the end of the day, I find my e100e module does not allow the system to suspend. I do use the ethernet adapter, and it only has occurred after having been connected to ethernet. The following is seen in dmsg: [40697.709402] Freezing user space processes ... (elapsed 0.01 seconds) done. [40697.724258] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done. [40697.740285] Suspending console(s) (use no_console_suspend to debug) [40697.872196] sd 0:0:0:0: [sda] Synchronizing SCSI cache [40698.041526] sd 0:0:0:0: [sda] Stopping disk [40698.714054] pci_pm_suspend(): e1000_suspend+0x0/0x20 [e1000e] returns -2 [40698.714058] dpm_run_callback(): pci_pm_suspend+0x0/0x140 returns -2 [40698.714061] PM: Device :00:19.0 failed to suspend async: error -2 [40698.714100] PM: Some devices failed to suspend WORKAROUND: rmmod e100e and I can suspend again. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-27-generic 3.8.0-27.40 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anton 3094 F pulseaudio /dev/snd/controlC0: anton 3094 F pulseaudio Date: Thu Aug 15 17:22:00 2013 HibernationDevice: RESUME=UUID=471df139-754b-43b4-9979-4d334871c53e InstallationDate: Installed on 2013-07-05 (40 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: LENOVO 24491D1 MarkForUpload: True ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-27-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash nox2apic RelatedPackageVersions: linux-restricted-modules-3.8.0-27-generic N/A linux-backports-modules-3.8.0-27-generic N/A linux-firmware1.106 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G5ET92WW (2.52 ) dmi.board.asset.tag: Not Available dmi.board.name: 24491D1 dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG5ET92WW(2.52):bd02/27/2013:svnLENOVO:pn24491D1:pvrThinkPadW530:rvnLENOVO:rn24491D1:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 24491D1 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213035/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1213035] Re: 8086:1502 [Lenovo ThinkPad W530] e1000e module sometimes prevents suspend to ram
Bios upgrade didn't help $sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date G5ET96WW (2.56 ) 11/27/2013 ** 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/1213035 Title: 8086:1502 [Lenovo ThinkPad W530] e1000e module sometimes prevents suspend to ram Status in “linux” package in Ubuntu: Confirmed Bug description: Sometimes, usually towards the end of the day, I find my e100e module does not allow the system to suspend. I do use the ethernet adapter, and it only has occurred after having been connected to ethernet. The following is seen in dmsg: [40697.709402] Freezing user space processes ... (elapsed 0.01 seconds) done. [40697.724258] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done. [40697.740285] Suspending console(s) (use no_console_suspend to debug) [40697.872196] sd 0:0:0:0: [sda] Synchronizing SCSI cache [40698.041526] sd 0:0:0:0: [sda] Stopping disk [40698.714054] pci_pm_suspend(): e1000_suspend+0x0/0x20 [e1000e] returns -2 [40698.714058] dpm_run_callback(): pci_pm_suspend+0x0/0x140 returns -2 [40698.714061] PM: Device :00:19.0 failed to suspend async: error -2 [40698.714100] PM: Some devices failed to suspend WORKAROUND: rmmod e100e and I can suspend again. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-27-generic 3.8.0-27.40 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anton 3094 F pulseaudio /dev/snd/controlC0: anton 3094 F pulseaudio Date: Thu Aug 15 17:22:00 2013 HibernationDevice: RESUME=UUID=471df139-754b-43b4-9979-4d334871c53e InstallationDate: Installed on 2013-07-05 (40 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: LENOVO 24491D1 MarkForUpload: True ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-27-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash nox2apic RelatedPackageVersions: linux-restricted-modules-3.8.0-27-generic N/A linux-backports-modules-3.8.0-27-generic N/A linux-firmware1.106 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G5ET92WW (2.52 ) dmi.board.asset.tag: Not Available dmi.board.name: 24491D1 dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG5ET92WW(2.52):bd02/27/2013:svnLENOVO:pn24491D1:pvrThinkPadW530:rvnLENOVO:rn24491D1:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 24491D1 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213035/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1213035] Re: e1000e module sometimes prevents suspend to ram
Just seen this on saucy with kernel 3.11.0-13-generic [32026.365726] PM: Entering mem sleep [32026.365783] Suspending console(s) (use no_console_suspend to debug) [32026.491757] sd 0:0:0:0: [sda] Synchronizing SCSI cache [32026.491946] sd 0:0:0:0: [sda] Stopping disk [32026.724207] mei_me :00:16.0: suspend [32027.346674] pci_pm_suspend(): e1000_suspend+0x0/0x20 [e1000e] returns -2 [32027.346678] dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -2 [32027.346681] PM: Device :00:19.0 failed to suspend async: error -2 [32027.346722] PM: Some devices failed to suspend, or early wake event detected ** 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/1213035 Title: e1000e module sometimes prevents suspend to ram Status in “linux” package in Ubuntu: Confirmed Bug description: Sometimes, usually towards the end of the day, I find my e100e module does not allow the system to suspend. The following is seen in dmsg: [40697.709402] Freezing user space processes ... (elapsed 0.01 seconds) done. [40697.724258] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done. [40697.740285] Suspending console(s) (use no_console_suspend to debug) [40697.872196] sd 0:0:0:0: [sda] Synchronizing SCSI cache [40698.041526] sd 0:0:0:0: [sda] Stopping disk [40698.714054] pci_pm_suspend(): e1000_suspend+0x0/0x20 [e1000e] returns -2 [40698.714058] dpm_run_callback(): pci_pm_suspend+0x0/0x140 returns -2 [40698.714061] PM: Device :00:19.0 failed to suspend async: error -2 [40698.714100] PM: Some devices failed to suspend rmmod e100e and I can suspend again. I do use the ethernet adapter, and it only has occurred after having been connected to ethernet. Seen on 13.04 amd64 with kernel 3.8.0-27-generic ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-27-generic 3.8.0-27.40 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anton 3094 F pulseaudio /dev/snd/controlC0: anton 3094 F pulseaudio Date: Thu Aug 15 17:22:00 2013 HibernationDevice: RESUME=UUID=471df139-754b-43b4-9979-4d334871c53e InstallationDate: Installed on 2013-07-05 (40 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: LENOVO 24491D1 MarkForUpload: True ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-27-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash nox2apic RelatedPackageVersions: linux-restricted-modules-3.8.0-27-generic N/A linux-backports-modules-3.8.0-27-generic N/A linux-firmware1.106 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G5ET92WW (2.52 ) dmi.board.asset.tag: Not Available dmi.board.name: 24491D1 dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG5ET92WW(2.52):bd02/27/2013:svnLENOVO:pn24491D1:pvrThinkPadW530:rvnLENOVO:rn24491D1:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 24491D1 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213035/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 962947] Re: CPU scaled back to very slow speed, cannot increase speed
I am now running saucy and the bug is still seen there current policy: frequency should be within 600 MHz and 700 MHz. The governor ondemand may decide which speed to use within this range. I will try a mainline kernel when I get time, but all the other mainline kernels I have tried in the past have this issue, and the upstream bug nobody seems to care about fixing either, so im pretty sure it will still be there. Linux smeg 3.11.0-11-generic #17-Ubuntu SMP Tue Oct 1 19:42:04 UTC 2013 x86_64 x86_64 x86_64 GNU/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/962947 Title: CPU scaled back to very slow speed, cannot increase speed Status in The Linux Kernel: Incomplete Status in “linux” package in Ubuntu: Incomplete Bug description: It appears that my 1.86GHz Intel Core2 CPU is only running at 700Mhz. The attached files show (in /proc/cpu) that the cpu is actually a 1.86Ghz, but cpufreq only lets me set a maximum of 700mhz. I am running precise amd64 on a 3.2.0-20-generic kernel, though the same was seen linux-image-3.2.0-19-generic as well I believe. The system is a Lenovo ThinkCentre 8810-91G, and the bios is the latest one available. The bios doesn't show any cpu limiting options or restrictions, and shows the cpus as the expected 1.86Mhz (though I think that is just model information rather than the current clock speed). I cannot see any overclocking options in the bios. $cpufreq-info cpufrequtils 007: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpuf...@vger.kernel.org, please. analyzing CPU 0: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 0 1 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 10.0 us. hardware limits: 600 MHz - 700 MHz available frequency steps: 700 MHz, 600 MHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 600 MHz and 700 MHz. The governor ondemand may decide which speed to use within this range. current CPU frequency is 600 MHz. cpufreq stats: 700 MHz:69.61%, 600 MHz:30.39% (3179) analyzing CPU 1: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 0 1 CPUs which need to have their frequency coordinated by software: 1 maximum transition latency: 10.0 us. hardware limits: 600 MHz - 700 MHz available frequency steps: 700 MHz, 600 MHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 600 MHz and 700 MHz. The governor ondemand may decide which speed to use within this range. current CPU frequency is 700 MHz. cpufreq stats: 700 MHz:59.66%, 600 MHz:40.34% (4168) ACPI appears to be reporting a bios limit on the CPU, though I have no idea why. $for i in /sys/devices/system/cpu/cpu0/cpufreq/*; do echo $i; sudo cat $i ; done /sys/devices/system/cpu/cpu0/cpufreq/affected_cpus 0 /sys/devices/system/cpu/cpu0/cpufreq/bios_limit 70 /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq 70 /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq 70 /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq 60 /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_transition_latency 1 /sys/devices/system/cpu/cpu0/cpufreq/related_cpus 0 1 /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies 70 60 /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors conservative ondemand userspace powersave performance /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq 70 /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver acpi-cpufreq /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor ondemand /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq 70 /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 60 /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed unsupported I can't recall if this was an issue on oneiric or not as I never looked at the cpufreq before. It may or may not be a new issue. I'm not entirely sure if this is a kernel bug or something else (like ACPI), but am happy to try various other kernels to see if they help. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-20-generic 3.2.0-20.32 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.95-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0:
[Kernel-packages] [Bug 1213035] Re: e1000e module sometimes prevents suspend to ram
I haven't seen it in saucy yet, but then I haven't been on saucy all that long -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1213035 Title: e1000e module sometimes prevents suspend to ram Status in “linux” package in Ubuntu: Incomplete Bug description: Sometimes, usually towards the end of the day, I find my e100e module does not allow the system to suspend. The following is seen in dmsg: [40697.709402] Freezing user space processes ... (elapsed 0.01 seconds) done. [40697.724258] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done. [40697.740285] Suspending console(s) (use no_console_suspend to debug) [40697.872196] sd 0:0:0:0: [sda] Synchronizing SCSI cache [40698.041526] sd 0:0:0:0: [sda] Stopping disk [40698.714054] pci_pm_suspend(): e1000_suspend+0x0/0x20 [e1000e] returns -2 [40698.714058] dpm_run_callback(): pci_pm_suspend+0x0/0x140 returns -2 [40698.714061] PM: Device :00:19.0 failed to suspend async: error -2 [40698.714100] PM: Some devices failed to suspend rmmod e100e and I can suspend again. I do use the ethernet adapter, and it only has occurred after having been connected to ethernet. Seen on 13.04 amd64 with kernel 3.8.0-27-generic ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-27-generic 3.8.0-27.40 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anton 3094 F pulseaudio /dev/snd/controlC0: anton 3094 F pulseaudio Date: Thu Aug 15 17:22:00 2013 HibernationDevice: RESUME=UUID=471df139-754b-43b4-9979-4d334871c53e InstallationDate: Installed on 2013-07-05 (40 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: LENOVO 24491D1 MarkForUpload: True ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-27-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash nox2apic RelatedPackageVersions: linux-restricted-modules-3.8.0-27-generic N/A linux-backports-modules-3.8.0-27-generic N/A linux-firmware1.106 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G5ET92WW (2.52 ) dmi.board.asset.tag: Not Available dmi.board.name: 24491D1 dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG5ET92WW(2.52):bd02/27/2013:svnLENOVO:pn24491D1:pvrThinkPadW530:rvnLENOVO:rn24491D1:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 24491D1 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213035/+subscriptions -- Mailing list: https://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 1213035] Re: e1000e module sometimes prevents suspend to ram
A duplicate actually counts for heat than reporting it affects me too -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1213035 Title: e1000e module sometimes prevents suspend to ram Status in “linux” package in Ubuntu: Incomplete Bug description: Sometimes, usually towards the end of the day, I find my e100e module does not allow the system to suspend. The following is seen in dmsg: [40697.709402] Freezing user space processes ... (elapsed 0.01 seconds) done. [40697.724258] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done. [40697.740285] Suspending console(s) (use no_console_suspend to debug) [40697.872196] sd 0:0:0:0: [sda] Synchronizing SCSI cache [40698.041526] sd 0:0:0:0: [sda] Stopping disk [40698.714054] pci_pm_suspend(): e1000_suspend+0x0/0x20 [e1000e] returns -2 [40698.714058] dpm_run_callback(): pci_pm_suspend+0x0/0x140 returns -2 [40698.714061] PM: Device :00:19.0 failed to suspend async: error -2 [40698.714100] PM: Some devices failed to suspend rmmod e100e and I can suspend again. I do use the ethernet adapter, and it only has occurred after having been connected to ethernet. Seen on 13.04 amd64 with kernel 3.8.0-27-generic ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-27-generic 3.8.0-27.40 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anton 3094 F pulseaudio /dev/snd/controlC0: anton 3094 F pulseaudio Date: Thu Aug 15 17:22:00 2013 HibernationDevice: RESUME=UUID=471df139-754b-43b4-9979-4d334871c53e InstallationDate: Installed on 2013-07-05 (40 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: LENOVO 24491D1 MarkForUpload: True ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-27-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash nox2apic RelatedPackageVersions: linux-restricted-modules-3.8.0-27-generic N/A linux-backports-modules-3.8.0-27-generic N/A linux-firmware1.106 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G5ET92WW (2.52 ) dmi.board.asset.tag: Not Available dmi.board.name: 24491D1 dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG5ET92WW(2.52):bd02/27/2013:svnLENOVO:pn24491D1:pvrThinkPadW530:rvnLENOVO:rn24491D1:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 24491D1 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213035/+subscriptions -- Mailing list: https://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 1213035] Re: e1000e module sometimes prevents suspend to ram
I don't know. It is a new laptop and raring is the first thing I installed on it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1213035 Title: e1000e module sometimes prevents suspend to ram Status in “linux” package in Ubuntu: Incomplete Bug description: Sometimes, usually towards the end of the day, I find my e100e module does not allow the system to suspend. The following is seen in dmsg: [40697.709402] Freezing user space processes ... (elapsed 0.01 seconds) done. [40697.724258] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done. [40697.740285] Suspending console(s) (use no_console_suspend to debug) [40697.872196] sd 0:0:0:0: [sda] Synchronizing SCSI cache [40698.041526] sd 0:0:0:0: [sda] Stopping disk [40698.714054] pci_pm_suspend(): e1000_suspend+0x0/0x20 [e1000e] returns -2 [40698.714058] dpm_run_callback(): pci_pm_suspend+0x0/0x140 returns -2 [40698.714061] PM: Device :00:19.0 failed to suspend async: error -2 [40698.714100] PM: Some devices failed to suspend rmmod e100e and I can suspend again. I do use the ethernet adapter, and it only has occurred after having been connected to ethernet. Seen on 13.04 amd64 with kernel 3.8.0-27-generic ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-27-generic 3.8.0-27.40 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anton 3094 F pulseaudio /dev/snd/controlC0: anton 3094 F pulseaudio Date: Thu Aug 15 17:22:00 2013 HibernationDevice: RESUME=UUID=471df139-754b-43b4-9979-4d334871c53e InstallationDate: Installed on 2013-07-05 (40 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: LENOVO 24491D1 MarkForUpload: True ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-27-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash nox2apic RelatedPackageVersions: linux-restricted-modules-3.8.0-27-generic N/A linux-backports-modules-3.8.0-27-generic N/A linux-firmware1.106 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G5ET92WW (2.52 ) dmi.board.asset.tag: Not Available dmi.board.name: 24491D1 dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG5ET92WW(2.52):bd02/27/2013:svnLENOVO:pn24491D1:pvrThinkPadW530:rvnLENOVO:rn24491D1:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 24491D1 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213035/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1213035] Re: e1000e module sometimes prevents suspend to ram
For reference I tried booting the latest mainline kernel, and apart from screwing up unity (see bug 1215828) it suspended once, then failed to resume. There was a reason I started using the nvidia driver, and that is because the nouveau one fails to resume. So testing on that won't be possible. I am expecting that a live cd will have a similar problem, so don't know if testing it will be feasible. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1213035 Title: e1000e module sometimes prevents suspend to ram Status in “linux” package in Ubuntu: Incomplete Bug description: Sometimes, usually towards the end of the day, I find my e100e module does not allow the system to suspend. The following is seen in dmsg: [40697.709402] Freezing user space processes ... (elapsed 0.01 seconds) done. [40697.724258] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done. [40697.740285] Suspending console(s) (use no_console_suspend to debug) [40697.872196] sd 0:0:0:0: [sda] Synchronizing SCSI cache [40698.041526] sd 0:0:0:0: [sda] Stopping disk [40698.714054] pci_pm_suspend(): e1000_suspend+0x0/0x20 [e1000e] returns -2 [40698.714058] dpm_run_callback(): pci_pm_suspend+0x0/0x140 returns -2 [40698.714061] PM: Device :00:19.0 failed to suspend async: error -2 [40698.714100] PM: Some devices failed to suspend rmmod e100e and I can suspend again. I do use the ethernet adapter, and it only has occurred after having been connected to ethernet. Seen on 13.04 amd64 with kernel 3.8.0-27-generic ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-27-generic 3.8.0-27.40 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anton 3094 F pulseaudio /dev/snd/controlC0: anton 3094 F pulseaudio Date: Thu Aug 15 17:22:00 2013 HibernationDevice: RESUME=UUID=471df139-754b-43b4-9979-4d334871c53e InstallationDate: Installed on 2013-07-05 (40 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: LENOVO 24491D1 MarkForUpload: True ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-27-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash nox2apic RelatedPackageVersions: linux-restricted-modules-3.8.0-27-generic N/A linux-backports-modules-3.8.0-27-generic N/A linux-firmware1.106 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G5ET92WW (2.52 ) dmi.board.asset.tag: Not Available dmi.board.name: 24491D1 dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG5ET92WW(2.52):bd02/27/2013:svnLENOVO:pn24491D1:pvrThinkPadW530:rvnLENOVO:rn24491D1:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 24491D1 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213035/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1213035] Re: e1000e module sometimes prevents suspend to ram
It is not possible to test this on the latest development image as the nouveau driver does not resume (desktop completely locks up), and the e1000e problem is intermittent, so a full reboot between tests is infeasible. Is there any debug info that I can gather to assist here? Any logs or trace? ** 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/1213035 Title: e1000e module sometimes prevents suspend to ram Status in “linux” package in Ubuntu: Confirmed Bug description: Sometimes, usually towards the end of the day, I find my e100e module does not allow the system to suspend. The following is seen in dmsg: [40697.709402] Freezing user space processes ... (elapsed 0.01 seconds) done. [40697.724258] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done. [40697.740285] Suspending console(s) (use no_console_suspend to debug) [40697.872196] sd 0:0:0:0: [sda] Synchronizing SCSI cache [40698.041526] sd 0:0:0:0: [sda] Stopping disk [40698.714054] pci_pm_suspend(): e1000_suspend+0x0/0x20 [e1000e] returns -2 [40698.714058] dpm_run_callback(): pci_pm_suspend+0x0/0x140 returns -2 [40698.714061] PM: Device :00:19.0 failed to suspend async: error -2 [40698.714100] PM: Some devices failed to suspend rmmod e100e and I can suspend again. I do use the ethernet adapter, and it only has occurred after having been connected to ethernet. Seen on 13.04 amd64 with kernel 3.8.0-27-generic ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-27-generic 3.8.0-27.40 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anton 3094 F pulseaudio /dev/snd/controlC0: anton 3094 F pulseaudio Date: Thu Aug 15 17:22:00 2013 HibernationDevice: RESUME=UUID=471df139-754b-43b4-9979-4d334871c53e InstallationDate: Installed on 2013-07-05 (40 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: LENOVO 24491D1 MarkForUpload: True ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-27-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash nox2apic RelatedPackageVersions: linux-restricted-modules-3.8.0-27-generic N/A linux-backports-modules-3.8.0-27-generic N/A linux-firmware1.106 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G5ET92WW (2.52 ) dmi.board.asset.tag: Not Available dmi.board.name: 24491D1 dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG5ET92WW(2.52):bd02/27/2013:svnLENOVO:pn24491D1:pvrThinkPadW530:rvnLENOVO:rn24491D1:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 24491D1 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213035/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1213035] Re: e1000e module sometimes prevents suspend to ram
Hi, I updated to the new bios but still had the problem earlier today. $ sudo dmidecode -s bios-version sudo dmidecode -s -daterelease G5ET93WW (2.53 ) 05/24/2013 ** 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/1213035 Title: e1000e module sometimes prevents suspend to ram Status in “linux” package in Ubuntu: Confirmed Bug description: Sometimes, usually towards the end of the day, I find my e100e module does not allow the system to suspend. The following is seen in dmsg: [40697.709402] Freezing user space processes ... (elapsed 0.01 seconds) done. [40697.724258] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done. [40697.740285] Suspending console(s) (use no_console_suspend to debug) [40697.872196] sd 0:0:0:0: [sda] Synchronizing SCSI cache [40698.041526] sd 0:0:0:0: [sda] Stopping disk [40698.714054] pci_pm_suspend(): e1000_suspend+0x0/0x20 [e1000e] returns -2 [40698.714058] dpm_run_callback(): pci_pm_suspend+0x0/0x140 returns -2 [40698.714061] PM: Device :00:19.0 failed to suspend async: error -2 [40698.714100] PM: Some devices failed to suspend rmmod e100e and I can suspend again. I do use the ethernet adapter, and it only has occurred after having been connected to ethernet. Seen on 13.04 amd64 with kernel 3.8.0-27-generic ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-27-generic 3.8.0-27.40 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anton 3094 F pulseaudio /dev/snd/controlC0: anton 3094 F pulseaudio Date: Thu Aug 15 17:22:00 2013 HibernationDevice: RESUME=UUID=471df139-754b-43b4-9979-4d334871c53e InstallationDate: Installed on 2013-07-05 (40 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: LENOVO 24491D1 MarkForUpload: True ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-27-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash nox2apic RelatedPackageVersions: linux-restricted-modules-3.8.0-27-generic N/A linux-backports-modules-3.8.0-27-generic N/A linux-firmware1.106 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G5ET92WW (2.52 ) dmi.board.asset.tag: Not Available dmi.board.name: 24491D1 dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG5ET92WW(2.52):bd02/27/2013:svnLENOVO:pn24491D1:pvrThinkPadW530:rvnLENOVO:rn24491D1:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 24491D1 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213035/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1213035] [NEW] e1000e module sometimes prevents suspend to ram
Public bug reported: Sometimes, usually towards the end of the day, I find my e100e module does not allow the system to suspend. The following is seen in dmsg: [40697.709402] Freezing user space processes ... (elapsed 0.01 seconds) done. [40697.724258] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done. [40697.740285] Suspending console(s) (use no_console_suspend to debug) [40697.872196] sd 0:0:0:0: [sda] Synchronizing SCSI cache [40698.041526] sd 0:0:0:0: [sda] Stopping disk [40698.714054] pci_pm_suspend(): e1000_suspend+0x0/0x20 [e1000e] returns -2 [40698.714058] dpm_run_callback(): pci_pm_suspend+0x0/0x140 returns -2 [40698.714061] PM: Device :00:19.0 failed to suspend async: error -2 [40698.714100] PM: Some devices failed to suspend rmmod e100e and I can suspend again. I do use the ethernet adapter, and it only has occurred after having been connected to ethernet. Seen on 13.04 amd64 with kernel 3.8.0-27-generic ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-27-generic 3.8.0-27.40 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anton 3094 F pulseaudio /dev/snd/controlC0: anton 3094 F pulseaudio Date: Thu Aug 15 17:22:00 2013 HibernationDevice: RESUME=UUID=471df139-754b-43b4-9979-4d334871c53e InstallationDate: Installed on 2013-07-05 (40 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: LENOVO 24491D1 MarkForUpload: True ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-27-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash nox2apic RelatedPackageVersions: linux-restricted-modules-3.8.0-27-generic N/A linux-backports-modules-3.8.0-27-generic N/A linux-firmware1.106 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G5ET92WW (2.52 ) dmi.board.asset.tag: Not Available dmi.board.name: 24491D1 dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG5ET92WW(2.52):bd02/27/2013:svnLENOVO:pn24491D1:pvrThinkPadW530:rvnLENOVO:rn24491D1:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 24491D1 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1213035 Title: e1000e module sometimes prevents suspend to ram Status in “linux” package in Ubuntu: New Bug description: Sometimes, usually towards the end of the day, I find my e100e module does not allow the system to suspend. The following is seen in dmsg: [40697.709402] Freezing user space processes ... (elapsed 0.01 seconds) done. [40697.724258] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done. [40697.740285] Suspending console(s) (use no_console_suspend to debug) [40697.872196] sd 0:0:0:0: [sda] Synchronizing SCSI cache [40698.041526] sd 0:0:0:0: [sda] Stopping disk [40698.714054] pci_pm_suspend(): e1000_suspend+0x0/0x20 [e1000e] returns -2 [40698.714058] dpm_run_callback(): pci_pm_suspend+0x0/0x140 returns -2 [40698.714061] PM: Device :00:19.0 failed to suspend async: error -2 [40698.714100] PM: Some devices failed to suspend rmmod e100e and I can suspend again. I do use the ethernet adapter, and it only has occurred after having been connected to ethernet. Seen on 13.04 amd64 with kernel 3.8.0-27-generic ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-27-generic 3.8.0-27.40 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anton 3094 F pulseaudio /dev/snd/controlC0: anton 3094 F pulseaudio Date: Thu Aug 15 17:22:00 2013 HibernationDevice: RESUME=UUID=471df139-754b-43b4-9979-4d334871c53e InstallationDate: Installed on 2013-07-05 (40 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: LENOVO 24491D1 MarkForUpload: True ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-27-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash nox2apic RelatedPackageVersions: linux-restricted-modules-3.8.0-27-generic N/A linux-backports-modules-3.8.0-27-generic N/A
