[Kernel-packages] [Bug 1429756] Re: FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at end of file
Hi Andy - any progress on this? Although the buildd's are running older kernels, it seems that the DEP-8 Jenkins environment is running 3.19 and is thus causing upstart tests to fail. For example: https://jenkins.qa.ubuntu.com/view/Wily/view/AutoPkgTest/job/wily-adt- upstart/ARCH=amd64,label=adt/lastBuild/ If it will take a while to resolve this, I guess we'll have to consider disabling the test for now. However, doing so is going to change the behaviour of the upstart logger. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1429756 Title: FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at end of file Status in linux package in Ubuntu: In Progress Status in upstart package in Ubuntu: Invalid Status in linux source package in Vivid: In Progress Status in upstart source package in Vivid: Invalid Bug description: As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid- adt-upstart/?, upstart's test fail almost all the time, on ok 53 - with single line command writing fast and exiting not ok 54 - with single line command writing lots of data fast and exiting wrong value for bytes, expected 3145728 got 3018027 at tests/test_job_process.c:3886 (test_start). 1..153 FAIL: test_job_process Sometimes they succeed on one architecture, and with lots of luck on both, but this is way too flaky to be an useful test. This keeps blocking the propagation of other packages from -proposed. This was most likely triggered by the kernel update from 3.18 to 3.19. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1429756/+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 1429756] Re: FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at near of file
Running with a 3.19.0-8-generic kernel I see: - The Upstart test_job_process test fail within a few seconds when run in a loop looking for the errror. - My test program in #13 also finds the bug within ~30 seconds on my test system. Using the kernel in #11, I have run both tests simultaneously for ~1 hour with no errors observed. ** Changed in: upstart (Ubuntu Vivid) Status: New = Invalid ** Summary changed: - FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at near of file + FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at end of file -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1429756 Title: FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at end of file Status in linux package in Ubuntu: In Progress Status in upstart package in Ubuntu: Invalid Status in linux source package in Vivid: In Progress Status in upstart source package in Vivid: Invalid Bug description: As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid- adt-upstart/?, upstart's test fail almost all the time, on ok 53 - with single line command writing fast and exiting not ok 54 - with single line command writing lots of data fast and exiting wrong value for bytes, expected 3145728 got 3018027 at tests/test_job_process.c:3886 (test_start). 1..153 FAIL: test_job_process Sometimes they succeed on one architecture, and with lots of luck on both, but this is way too flaky to be an useful test. This keeps blocking the propagation of other packages from -proposed. This was most likely triggered by the kernel update from 3.18 to 3.19. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1429756/+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 1429756] Re: FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at near of file
I've written a basic program that surfaces this bug. To recreate: $ cd /tmp $ tar xvf bug-1429756.tgz $ cd bug-1429756 $ make $ ./bug-1429756.sh loop 1 loop 2 ERROR: got failure scenario after 2 loops (got=16, count=17, log=/tmp/tmp.uwZHkHh0mc) $ ** Attachment added: bug-1429756.tgz https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1429756/+attachment/4343995/+files/bug-1429756.tgz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1429756 Title: FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at near of file Status in linux package in Ubuntu: In Progress Status in upstart package in Ubuntu: New Status in linux source package in Vivid: In Progress Status in upstart source package in Vivid: New Bug description: As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid- adt-upstart/?, upstart's test fail almost all the time, on ok 53 - with single line command writing fast and exiting not ok 54 - with single line command writing lots of data fast and exiting wrong value for bytes, expected 3145728 got 3018027 at tests/test_job_process.c:3886 (test_start). 1..153 FAIL: test_job_process Sometimes they succeed on one architecture, and with lots of luck on both, but this is way too flaky to be an useful test. This keeps blocking the propagation of other packages from -proposed. This was most likely triggered by the kernel update from 3.18 to 3.19. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1429756/+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 1371651] Re: Daily does not boot into graphical interface after installation
@elfy - is plymouth is still crashing for you? $ sudo grep SEGV /var/log/syslog -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1371651 Title: Daily does not boot into graphical interface after installation Status in Light Display Manager: Invalid Status in “lightdm” package in Ubuntu: Invalid Status in “linux” package in Ubuntu: Invalid Status in “plymouth” package in Ubuntu: Fix Released Bug description: used the daily iso 2015-09-19 i386 ran installation on virtualbox 4.3.16 after installation, the system won't boot into the graphical interface. instead, switching to vt1 and back to vt7 reveals the attached errors. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2 Uname: Linux 3.16.0-16-generic i686 ApportVersion: 2.14.7-0ubuntu2 Architecture: i386 Date: Fri Sep 19 17:09:17 2014 InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- debian-installer/language=de keyboard-configuration/layoutcode?=de InstallationDate: Installed on 2014-09-19 (0 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha i386 (20140919) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1371651/+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 1371651] Re: Daily does not boot into graphical interface after installation
As discussed on irc, the problem seemed to be that the plymouth-ready event was not being emitted since udev was not tagging a graphics device with PRIMARY_DEVICE_FOR_DISPLAY, so it looked like the problem was udev/kernel related. According to jibel, if he enters the grub boot menu lightdm will reliably start suggesting that grub is possibly setting up the framebuffer which for some reason is not happening normally. Looking at the log in #22, we can also see that plymouth itself is crashing (SEGV). This may also suggest a problem with the graphics setup. I've just tried utopic-desktop-amd64.iso (20140923) under kvm and do not see the issue reported. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1371651 Title: Daily does not boot into graphical interface after installation Status in Light Display Manager: Confirmed Status in “lightdm” package in Ubuntu: Triaged Status in “linux” package in Ubuntu: New Bug description: used the daily iso 2015-09-19 i386 ran installation on virtualbox 4.3.16 after installation, the system won't boot into the graphical interface. instead, switching to vt1 and back to vt7 reveals the attached errors. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2 Uname: Linux 3.16.0-16-generic i686 ApportVersion: 2.14.7-0ubuntu2 Architecture: i386 Date: Fri Sep 19 17:09:17 2014 InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- debian-installer/language=de keyboard-configuration/layoutcode?=de InstallationDate: Installed on 2014-09-19 (0 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha i386 (20140919) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1371651/+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 1371651] Re: Daily does not boot into graphical interface after installation
Note also that I do have PRIMARY_DEVICE_FOR_DISPLAY=1 in /var/log/udev. Recreation is under kvm. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1371651 Title: Daily does not boot into graphical interface after installation Status in Light Display Manager: Confirmed Status in “lightdm” package in Ubuntu: Triaged Status in “linux” package in Ubuntu: Incomplete Bug description: used the daily iso 2015-09-19 i386 ran installation on virtualbox 4.3.16 after installation, the system won't boot into the graphical interface. instead, switching to vt1 and back to vt7 reveals the attached errors. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2 Uname: Linux 3.16.0-16-generic i686 ApportVersion: 2.14.7-0ubuntu2 Architecture: i386 Date: Fri Sep 19 17:09:17 2014 InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- debian-installer/language=de keyboard-configuration/layoutcode?=de InstallationDate: Installed on 2014-09-19 (0 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha i386 (20140919) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1371651/+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 1371651] Re: Daily does not boot into graphical interface after installation
I have now recreated using utopic-desktop-amd64.iso (20140923) and http://people.canonical.com/~jhunt/upstart/conf/rebooter.conf to force continuous reboots. It appears that the problem only occurs if quiet splash is specified since I ran 25 boots without those options and was unable to recreate the issue. [1] - http://people.canonical.com/~jhunt/upstart/conf/rebooter.conf -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1371651 Title: Daily does not boot into graphical interface after installation Status in Light Display Manager: Confirmed Status in “lightdm” package in Ubuntu: Triaged Status in “linux” package in Ubuntu: Incomplete Bug description: used the daily iso 2015-09-19 i386 ran installation on virtualbox 4.3.16 after installation, the system won't boot into the graphical interface. instead, switching to vt1 and back to vt7 reveals the attached errors. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2 Uname: Linux 3.16.0-16-generic i686 ApportVersion: 2.14.7-0ubuntu2 Architecture: i386 Date: Fri Sep 19 17:09:17 2014 InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- debian-installer/language=de keyboard-configuration/layoutcode?=de InstallationDate: Installed on 2014-09-19 (0 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha i386 (20140919) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1371651/+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 1371651] Re: Daily does not boot into graphical interface after installation
It's looking like either quiet or more likely splash is the triggering factor here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1371651 Title: Daily does not boot into graphical interface after installation Status in Light Display Manager: Confirmed Status in “lightdm” package in Ubuntu: Triaged Status in “linux” package in Ubuntu: Incomplete Bug description: used the daily iso 2015-09-19 i386 ran installation on virtualbox 4.3.16 after installation, the system won't boot into the graphical interface. instead, switching to vt1 and back to vt7 reveals the attached errors. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2 Uname: Linux 3.16.0-16-generic i686 ApportVersion: 2.14.7-0ubuntu2 Architecture: i386 Date: Fri Sep 19 17:09:17 2014 InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- debian-installer/language=de keyboard-configuration/layoutcode?=de InstallationDate: Installed on 2014-09-19 (0 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha i386 (20140919) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1371651/+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 1371651] Re: Daily does not boot into graphical interface after installation
After removing both 'quiet' and 'splash' options from GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub, and running 'sudo update-grub', I am no longer able to recreate the bug (over 100 boots on a 64-bit kvm instance using utopic-desktop-amd64.iso (20140923)). @elfy: can you provide details on how reliable this failure is for you? Do you see it on every boot? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1371651 Title: Daily does not boot into graphical interface after installation Status in Light Display Manager: Invalid Status in “lightdm” package in Ubuntu: Confirmed Status in “linux” package in Ubuntu: Incomplete Bug description: used the daily iso 2015-09-19 i386 ran installation on virtualbox 4.3.16 after installation, the system won't boot into the graphical interface. instead, switching to vt1 and back to vt7 reveals the attached errors. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2 Uname: Linux 3.16.0-16-generic i686 ApportVersion: 2.14.7-0ubuntu2 Architecture: i386 Date: Fri Sep 19 17:09:17 2014 InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- debian-installer/language=de keyboard-configuration/layoutcode?=de InstallationDate: Installed on 2014-09-19 (0 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha i386 (20140919) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1371651/+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 1371651] Re: Daily does not boot into graphical interface after installation
205 boots and no problem with the 2 options removed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1371651 Title: Daily does not boot into graphical interface after installation Status in Light Display Manager: Invalid Status in “lightdm” package in Ubuntu: Confirmed Status in “linux” package in Ubuntu: Incomplete Bug description: used the daily iso 2015-09-19 i386 ran installation on virtualbox 4.3.16 after installation, the system won't boot into the graphical interface. instead, switching to vt1 and back to vt7 reveals the attached errors. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2 Uname: Linux 3.16.0-16-generic i686 ApportVersion: 2.14.7-0ubuntu2 Architecture: i386 Date: Fri Sep 19 17:09:17 2014 InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- debian-installer/language=de keyboard-configuration/layoutcode?=de InstallationDate: Installed on 2014-09-19 (0 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha i386 (20140919) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1371651/+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 1371651] Re: Daily does not boot into graphical interface after installation
@arges: can you try reproducing without quiet splash as that seems to be the best lead we have so far. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1371651 Title: Daily does not boot into graphical interface after installation Status in Light Display Manager: Invalid Status in “lightdm” package in Ubuntu: Confirmed Status in “linux” package in Ubuntu: Incomplete Bug description: used the daily iso 2015-09-19 i386 ran installation on virtualbox 4.3.16 after installation, the system won't boot into the graphical interface. instead, switching to vt1 and back to vt7 reveals the attached errors. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2 Uname: Linux 3.16.0-16-generic i686 ApportVersion: 2.14.7-0ubuntu2 Architecture: i386 Date: Fri Sep 19 17:09:17 2014 InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- debian-installer/language=de keyboard-configuration/layoutcode?=de InstallationDate: Installed on 2014-09-19 (0 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha i386 (20140919) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1371651/+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 1362742] [NEW] kernel panic attempting to unmount device with errors
Public bug reported: /var/log/kern.log shows: Aug 28 17:32:20 faire kernel: [37077.847109] EXT4-fs (sde1): warning: maximal mount count reached, running e2fsck is recommended Aug 28 17:32:20 faire kernel: [37077.848127] EXT4-fs (sde1): recovery complete Aug 28 17:32:20 faire kernel: [37077.848915] EXT4-fs (sde1): mounted filesystem with ordered data mode. Opts: (null) Aug 28 17:37:17 faire kernel: [37374.626258] EXT4-fs (sdd1): error count since last fsck: 8 Aug 28 17:37:17 faire kernel: [37374.626262] EXT4-fs (sdd1): initial error at time 1389635241: ext4_mb_generate_buddy:756 Aug 28 17:37:17 faire kernel: [37374.626264] EXT4-fs (sdd1): last error at time 1391881607: ext4_mb_generate_buddy:756 Aug 28 19:03:10 faire kernel: [0.00] Initializing cgroup subsys cpuset Aug 28 19:03:10 faire kernel: [0.00] Initializing cgroup subsys cpu Aug 28 19:03:10 faire kernel: [0.00] Initializing cgroup subsys cpuacct Aug 28 19:03:10 faire kernel: [0.00] Linux version 3.16.0-10-generic (buildd@aatxe) (gcc version 4.9.1 (Ubuntu/Linaro 4.9.1-8ubuntu1) ) #15-Ubuntu SMP Thu Aug 21 16:26:44 UTC 2014 (Ubuntu 3.16.0-10.15-generic 3.16.1) Aug 28 19:03:10 faire kernel: [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.16.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Aug 28 19:03:10 faire kernel: [0.00] KERNEL supported cpus: It seems that I have a USB stick which has errors. When I attempted to unmount it, my system froze and had to be alt-sysreq s-u-b'd. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-generic 3.16.0.10.11 ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1 Uname: Linux 3.16.0-10-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 3770 F pulseaudio /dev/snd/controlC0: james 3770 F pulseaudio CurrentDesktop: Unity Date: Thu Aug 28 19:07:46 2014 HibernationDevice: RESUME=UUID=db600bbe-faca-41f4-9338-c3e8e227599a InstallationDate: Installed on 2014-04-11 (138 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409) MachineType: LENOVO 20AQCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-10-generic N/A linux-backports-modules-3.16.0-10-generic N/A linux-firmware 1.132 SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2014-05-08 (112 days ago) dmi.bios.date: 02/10/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET71WW (2.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98405 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AQCTO1WW dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1362742 Title: kernel panic attempting to unmount device with errors Status in “linux” package in Ubuntu: New Bug description: /var/log/kern.log shows: Aug 28 17:32:20 faire kernel: [37077.847109] EXT4-fs (sde1): warning: maximal mount count reached, running e2fsck is recommended Aug 28 17:32:20 faire kernel: [37077.848127] EXT4-fs (sde1): recovery complete Aug 28 17:32:20 faire kernel: [37077.848915] EXT4-fs (sde1): mounted filesystem with ordered data mode. Opts: (null) Aug 28 17:37:17 faire kernel: [37374.626258] EXT4-fs (sdd1): error count since last fsck: 8 Aug 28 17:37:17 faire kernel: [37374.626262] EXT4-fs (sdd1): initial error at time 1389635241: ext4_mb_generate_buddy:756 Aug 28 17:37:17 faire kernel: [37374.626264] EXT4-fs (sdd1): last error at time 1391881607: ext4_mb_generate_buddy:756 Aug 28 19:03:10 faire kernel: [0.00] Initializing cgroup subsys cpuset Aug 28 19:03:10 faire kernel: [0.00] Initializing cgroup subsys cpu Aug 28 19:03:10 faire kernel: [0.00] Initializing cgroup subsys cpuacct Aug 28 19:03:10 faire kernel: [0.00] Linux version 3.16.0-10-generic (buildd@aatxe) (gcc version 4.9.1 (Ubuntu/Linaro 4.9.1-8ubuntu1) ) #15-Ubuntu SMP Thu Aug 21 16:26:44 UTC 2014 (Ubuntu 3.16.0-10.15-generic 3.16.1) Aug 28 19:03:10 faire kernel: [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.16.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Aug 28 19:03:10 faire kernel: [0.00] KERNEL
[Kernel-packages] [Bug 1357252] Re: Upstart jobs specifying cgroup fail to start occasionally
** Changed in: upstart Status: New = In Progress ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1357252 Title: Upstart jobs specifying cgroup fail to start occasionally Status in Ubuntu Application Launcher: Incomplete Status in Upstart: In Progress Status in “cgmanager” package in Ubuntu: Confirmed Status in “linux” package in Ubuntu: New Bug description: After the ubuntu-app-launch landing in #188 (http://people.canonical.com/~ogra/touch-image-stats/188.changes), UI Toolkit autopilot tests have started failing, see http://ci.ubuntu.com/smokeng/utopic/touch/mako/190:20140815:20140811.1/9676/ubuntuuitoolkit/ and the #188 results too. It's different tests each time, but a bit above 10 of them tend to fail on each full run. Reproducable locally, where I got 11 such failures. To reproduce: [terminal 1] 1. flash/update device if needed 2. adb shell 3. apt install ubuntu-ui-toolkit-autopilot 4. powerd-cli display on bright # leave running, also unlock the screen so that lenses are shown [terminal 2] 5. phablet-config autopilot --dbus-probe enable # wait until finishes 6. phablet-test-run ubuntuuitoolkit A full test suite run will take around 0.5h and should produce a bunch of 'Application failed to start.':s. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-app-launch/+bug/1357252/+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 1357252] Re: Upstart jobs specifying cgroup fail to start occasionally
** No longer affects: linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1357252 Title: Upstart jobs specifying cgroup fail to start occasionally Status in Ubuntu Application Launcher: Incomplete Status in Upstart: In Progress Status in “cgmanager” package in Ubuntu: Confirmed Bug description: After the ubuntu-app-launch landing in #188 (http://people.canonical.com/~ogra/touch-image-stats/188.changes), UI Toolkit autopilot tests have started failing, see http://ci.ubuntu.com/smokeng/utopic/touch/mako/190:20140815:20140811.1/9676/ubuntuuitoolkit/ and the #188 results too. It's different tests each time, but a bit above 10 of them tend to fail on each full run. Reproducable locally, where I got 11 such failures. To reproduce: [terminal 1] 1. flash/update device if needed 2. adb shell 3. apt install ubuntu-ui-toolkit-autopilot 4. powerd-cli display on bright # leave running, also unlock the screen so that lenses are shown [terminal 2] 5. phablet-config autopilot --dbus-probe enable # wait until finishes 6. phablet-test-run ubuntuuitoolkit A full test suite run will take around 0.5h and should produce a bunch of 'Application failed to start.':s. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-app-launch/+bug/1357252/+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 1351353] Re: Kernel oops
@Chris - I'm not an expert at reading kernel stack traces, but I don't think the oops stacktrace looks related to kvm. I just mentioned that I was using kvm when the oops occurred (*). I've edited the title accordingly. (*) - I know this since I have a script which warns me as soon as an oops is generated. ** Summary changed: - Kernel oops related to running kvm (?) + Kernel oops -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1351353 Title: Kernel oops Status in “linux” package in Ubuntu: Confirmed Bug description: My system suddently became unresponsive so I tried to SysRq s/u/b and I think that's what caused another problem. Either way, my system hard-locked. Aug 1 16:15:59 faire kernel: [31778.831601] [ cut here ] Aug 1 16:15:59 faire kernel: [31778.831644] WARNING: CPU: 2 PID: 1834 at /build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_display.c:3313 intel_crtc_wait_for_pending_flips+0x171/0x180 [i915]() Aug 1 16:15:59 faire kernel: [31778.831646] Modules linked in: cdc_acm ums_cypress btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c veth ccm overlayfs xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables deflate ctr twofish_generic twofish_avx_x86_64 twofish_x86_64_3way twofish_x86_64 twofish_common camellia_generic camellia_aesni_avx2 camellia_aesni_avx_x86_64 camellia_x86_64 serpent_avx2 serpent_avx_x86_64 serpent_sse2_x86_64 xts serpent_generic blowfish_generic blowfish_x86_64 blowfish_common cast5_avx_x86_64 cast5_generic cast_common des_generic cmac xcbc rmd160 crypto_null af_key xfrm_algo arc4 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm microcode snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi joydev binfmt_misc serio_raw iwlmvm mac80211 snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep lpc_ich rtsx_pci_ms iwlwifi memstick snd_pcm cfg80211 uvcvideo videobuf2_vmalloc videobuf2_memops shpchp videobuf2_core v4l2_common mei_me videodev mei media thinkpad_acpi nvram btusb snd_seq_midi snd_seq_midi_event bluetooth snd_rawmidi 6lowpan_iphc snd_seq snd_seq_device snd_timer snd intel_smartconnect soundcore cuse parport_pc mac_hid ppdev lp parport nls_iso8859_1 uas usb_storage hid_generic usbhid hid dm_crypt mmc_block rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd psmouse i915 ahci e1000e libahci rtsx_pci ptp pps_core i2c_algo_bit drm_kms_helper wmi drm video Aug 1 16:15:59 faire kernel: [31778.831718] CPU: 2 PID: 1834 Comm: Xorg Not tainted 3.16.0-6-generic #11-Ubuntu Aug 1 16:15:59 faire kernel: [31778.831720] Hardware name: LENOVO 20AQCTO1WW/20AQCTO1WW, BIOS GJET71WW (2.21 ) 02/10/2014 Aug 1 16:15:59 faire kernel: [31778.831721] 0009 8800d6233c10 82755538 Aug 1 16:15:59 faire kernel: [31778.831724] 8800d6233c48 8206bb0d 880308eed000 Aug 1 16:15:59 faire kernel: [31778.831726] 880304108240 8800da1e1000 8800da1e1000 8800d6233c58 Aug 1 16:15:59 faire kernel: [31778.831729] Call Trace: Aug 1 16:15:59 faire kernel: [31778.831735] [82755538] dump_stack+0x45/0x56 Aug 1 16:15:59 faire kernel: [31778.831739] [8206bb0d] warn_slowpath_common+0x7d/0xa0 Aug 1 16:15:59 faire kernel: [31778.831742] [8206bbea] warn_slowpath_null+0x1a/0x20 Aug 1 16:15:59 faire kernel: [31778.831765] [c04c6951] intel_crtc_wait_for_pending_flips+0x171/0x180 [i915] Aug 1 16:15:59 faire kernel: [31778.831769] [820b2960] ? prepare_to_wait_event+0x100/0x100 Aug 1 16:15:59 faire kernel: [31778.831787] [c04c9403] intel_crtc_disable_planes+0x33/0x1c0 [i915] Aug 1 16:15:59 faire kernel: [31778.831790] [8275bb2b] ? __ww_mutex_lock+0x1b/0x97 Aug 1 16:15:59 faire kernel: [31778.831807] [c04ca305] haswell_crtc_disable+0x55/0x2f0 [i915] Aug 1 16:15:59 faire kernel: [31778.831809] [8275c062] ? mutex_lock+0x12/0x2f Aug 1 16:15:59 faire kernel: [31778.831823] [c04cad27] intel_crtc_update_dpms+0x67/0xa0 [i915] Aug 1 16:15:59 faire kernel: [31778.831835] [c04cf1e9] intel_connector_dpms+0x59/0x70 [i915] Aug 1 16:15:59 faire kernel: [31778.831848] [c039ea1f] drm_mode_obj_set_property_ioctl+0x39f/0x3b0 [drm] Aug 1 16:15:59 faire kernel: [31778.831858] [c039ea60] drm_mode_connector_property_set_ioctl+0x30/0x40 [drm] Aug 1 16:15:59 faire kernel: [31778.831860] [c0c0c0c0] ? ipv4_conntrack_defrag+0xb0/0x163 [nf_defrag_ipv4] Aug 1 16:15:59 faire kernel: [31778.831868] [c038da3c]
[Kernel-packages] [Bug 1351353] Re: Kernel oops related to running kvm (?)
** Attachment added: kern.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1351353/+attachment/4167467/+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/1351353 Title: Kernel oops related to running kvm (?) Status in “linux” package in Ubuntu: Confirmed Bug description: My system suddently became unresponsive so I tried to SysRq s/u/b and I think that's what caused another problem. Either way, my system hard-locked. Aug 1 16:15:59 faire kernel: [31778.831601] [ cut here ] Aug 1 16:15:59 faire kernel: [31778.831644] WARNING: CPU: 2 PID: 1834 at /build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_display.c:3313 intel_crtc_wait_for_pending_flips+0x171/0x180 [i915]() Aug 1 16:15:59 faire kernel: [31778.831646] Modules linked in: cdc_acm ums_cypress btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c veth ccm overlayfs xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables deflate ctr twofish_generic twofish_avx_x86_64 twofish_x86_64_3way twofish_x86_64 twofish_common camellia_generic camellia_aesni_avx2 camellia_aesni_avx_x86_64 camellia_x86_64 serpent_avx2 serpent_avx_x86_64 serpent_sse2_x86_64 xts serpent_generic blowfish_generic blowfish_x86_64 blowfish_common cast5_avx_x86_64 cast5_generic cast_common des_generic cmac xcbc rmd160 crypto_null af_key xfrm_algo arc4 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm microcode snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi joydev binfmt_misc serio_raw iwlmvm mac80211 snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep lpc_ich rtsx_pci_ms iwlwifi memstick snd_pcm cfg80211 uvcvideo videobuf2_vmalloc videobuf2_memops shpchp videobuf2_core v4l2_common mei_me videodev mei media thinkpad_acpi nvram btusb snd_seq_midi snd_seq_midi_event bluetooth snd_rawmidi 6lowpan_iphc snd_seq snd_seq_device snd_timer snd intel_smartconnect soundcore cuse parport_pc mac_hid ppdev lp parport nls_iso8859_1 uas usb_storage hid_generic usbhid hid dm_crypt mmc_block rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd psmouse i915 ahci e1000e libahci rtsx_pci ptp pps_core i2c_algo_bit drm_kms_helper wmi drm video Aug 1 16:15:59 faire kernel: [31778.831718] CPU: 2 PID: 1834 Comm: Xorg Not tainted 3.16.0-6-generic #11-Ubuntu Aug 1 16:15:59 faire kernel: [31778.831720] Hardware name: LENOVO 20AQCTO1WW/20AQCTO1WW, BIOS GJET71WW (2.21 ) 02/10/2014 Aug 1 16:15:59 faire kernel: [31778.831721] 0009 8800d6233c10 82755538 Aug 1 16:15:59 faire kernel: [31778.831724] 8800d6233c48 8206bb0d 880308eed000 Aug 1 16:15:59 faire kernel: [31778.831726] 880304108240 8800da1e1000 8800da1e1000 8800d6233c58 Aug 1 16:15:59 faire kernel: [31778.831729] Call Trace: Aug 1 16:15:59 faire kernel: [31778.831735] [82755538] dump_stack+0x45/0x56 Aug 1 16:15:59 faire kernel: [31778.831739] [8206bb0d] warn_slowpath_common+0x7d/0xa0 Aug 1 16:15:59 faire kernel: [31778.831742] [8206bbea] warn_slowpath_null+0x1a/0x20 Aug 1 16:15:59 faire kernel: [31778.831765] [c04c6951] intel_crtc_wait_for_pending_flips+0x171/0x180 [i915] Aug 1 16:15:59 faire kernel: [31778.831769] [820b2960] ? prepare_to_wait_event+0x100/0x100 Aug 1 16:15:59 faire kernel: [31778.831787] [c04c9403] intel_crtc_disable_planes+0x33/0x1c0 [i915] Aug 1 16:15:59 faire kernel: [31778.831790] [8275bb2b] ? __ww_mutex_lock+0x1b/0x97 Aug 1 16:15:59 faire kernel: [31778.831807] [c04ca305] haswell_crtc_disable+0x55/0x2f0 [i915] Aug 1 16:15:59 faire kernel: [31778.831809] [8275c062] ? mutex_lock+0x12/0x2f Aug 1 16:15:59 faire kernel: [31778.831823] [c04cad27] intel_crtc_update_dpms+0x67/0xa0 [i915] Aug 1 16:15:59 faire kernel: [31778.831835] [c04cf1e9] intel_connector_dpms+0x59/0x70 [i915] Aug 1 16:15:59 faire kernel: [31778.831848] [c039ea1f] drm_mode_obj_set_property_ioctl+0x39f/0x3b0 [drm] Aug 1 16:15:59 faire kernel: [31778.831858] [c039ea60] drm_mode_connector_property_set_ioctl+0x30/0x40 [drm] Aug 1 16:15:59 faire kernel: [31778.831860] [c0c0c0c0] ? ipv4_conntrack_defrag+0xb0/0x163 [nf_defrag_ipv4] Aug 1 16:15:59 faire kernel: [31778.831868] [c038da3c] drm_ioctl+0x1ec/0x660 [drm] Aug 1 16:15:59 faire kernel: [31778.831873] [821e2d20] do_vfs_ioctl+0x2e0/0x4c0 Aug 1 16:15:59 faire kernel: [31778.831876] [820a2de4] ? vtime_account_user+0x54/0x60 Aug 1 16:15:59
[Kernel-packages] [Bug 1351353] Re: Kernel oops related to running kvm (?)
** Attachment added: kern.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1351353/+attachment/4167466/+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/1351353 Title: Kernel oops related to running kvm (?) Status in “linux” package in Ubuntu: Confirmed Bug description: My system suddently became unresponsive so I tried to SysRq s/u/b and I think that's what caused another problem. Either way, my system hard-locked. Aug 1 16:15:59 faire kernel: [31778.831601] [ cut here ] Aug 1 16:15:59 faire kernel: [31778.831644] WARNING: CPU: 2 PID: 1834 at /build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_display.c:3313 intel_crtc_wait_for_pending_flips+0x171/0x180 [i915]() Aug 1 16:15:59 faire kernel: [31778.831646] Modules linked in: cdc_acm ums_cypress btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c veth ccm overlayfs xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables deflate ctr twofish_generic twofish_avx_x86_64 twofish_x86_64_3way twofish_x86_64 twofish_common camellia_generic camellia_aesni_avx2 camellia_aesni_avx_x86_64 camellia_x86_64 serpent_avx2 serpent_avx_x86_64 serpent_sse2_x86_64 xts serpent_generic blowfish_generic blowfish_x86_64 blowfish_common cast5_avx_x86_64 cast5_generic cast_common des_generic cmac xcbc rmd160 crypto_null af_key xfrm_algo arc4 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm microcode snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi joydev binfmt_misc serio_raw iwlmvm mac80211 snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep lpc_ich rtsx_pci_ms iwlwifi memstick snd_pcm cfg80211 uvcvideo videobuf2_vmalloc videobuf2_memops shpchp videobuf2_core v4l2_common mei_me videodev mei media thinkpad_acpi nvram btusb snd_seq_midi snd_seq_midi_event bluetooth snd_rawmidi 6lowpan_iphc snd_seq snd_seq_device snd_timer snd intel_smartconnect soundcore cuse parport_pc mac_hid ppdev lp parport nls_iso8859_1 uas usb_storage hid_generic usbhid hid dm_crypt mmc_block rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd psmouse i915 ahci e1000e libahci rtsx_pci ptp pps_core i2c_algo_bit drm_kms_helper wmi drm video Aug 1 16:15:59 faire kernel: [31778.831718] CPU: 2 PID: 1834 Comm: Xorg Not tainted 3.16.0-6-generic #11-Ubuntu Aug 1 16:15:59 faire kernel: [31778.831720] Hardware name: LENOVO 20AQCTO1WW/20AQCTO1WW, BIOS GJET71WW (2.21 ) 02/10/2014 Aug 1 16:15:59 faire kernel: [31778.831721] 0009 8800d6233c10 82755538 Aug 1 16:15:59 faire kernel: [31778.831724] 8800d6233c48 8206bb0d 880308eed000 Aug 1 16:15:59 faire kernel: [31778.831726] 880304108240 8800da1e1000 8800da1e1000 8800d6233c58 Aug 1 16:15:59 faire kernel: [31778.831729] Call Trace: Aug 1 16:15:59 faire kernel: [31778.831735] [82755538] dump_stack+0x45/0x56 Aug 1 16:15:59 faire kernel: [31778.831739] [8206bb0d] warn_slowpath_common+0x7d/0xa0 Aug 1 16:15:59 faire kernel: [31778.831742] [8206bbea] warn_slowpath_null+0x1a/0x20 Aug 1 16:15:59 faire kernel: [31778.831765] [c04c6951] intel_crtc_wait_for_pending_flips+0x171/0x180 [i915] Aug 1 16:15:59 faire kernel: [31778.831769] [820b2960] ? prepare_to_wait_event+0x100/0x100 Aug 1 16:15:59 faire kernel: [31778.831787] [c04c9403] intel_crtc_disable_planes+0x33/0x1c0 [i915] Aug 1 16:15:59 faire kernel: [31778.831790] [8275bb2b] ? __ww_mutex_lock+0x1b/0x97 Aug 1 16:15:59 faire kernel: [31778.831807] [c04ca305] haswell_crtc_disable+0x55/0x2f0 [i915] Aug 1 16:15:59 faire kernel: [31778.831809] [8275c062] ? mutex_lock+0x12/0x2f Aug 1 16:15:59 faire kernel: [31778.831823] [c04cad27] intel_crtc_update_dpms+0x67/0xa0 [i915] Aug 1 16:15:59 faire kernel: [31778.831835] [c04cf1e9] intel_connector_dpms+0x59/0x70 [i915] Aug 1 16:15:59 faire kernel: [31778.831848] [c039ea1f] drm_mode_obj_set_property_ioctl+0x39f/0x3b0 [drm] Aug 1 16:15:59 faire kernel: [31778.831858] [c039ea60] drm_mode_connector_property_set_ioctl+0x30/0x40 [drm] Aug 1 16:15:59 faire kernel: [31778.831860] [c0c0c0c0] ? ipv4_conntrack_defrag+0xb0/0x163 [nf_defrag_ipv4] Aug 1 16:15:59 faire kernel: [31778.831868] [c038da3c] drm_ioctl+0x1ec/0x660 [drm] Aug 1 16:15:59 faire kernel: [31778.831873] [821e2d20] do_vfs_ioctl+0x2e0/0x4c0 Aug 1 16:15:59 faire kernel: [31778.831876] [820a2de4] ? vtime_account_user+0x54/0x60 Aug 1 16:15:59
[Kernel-packages] [Bug 1351353] [NEW] Kernel oops related to running kvm (?)
Public bug reported: My system suddently became unresponsive so I tried to SysRq s/u/b and I think that's what caused another problem. Either way, my system hard-locked. Aug 1 16:15:59 faire kernel: [31778.831601] [ cut here ] Aug 1 16:15:59 faire kernel: [31778.831644] WARNING: CPU: 2 PID: 1834 at /build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_display.c:3313 intel_crtc_wait_for_pending_flips+0x171/0x180 [i915]() Aug 1 16:15:59 faire kernel: [31778.831646] Modules linked in: cdc_acm ums_cypress btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c veth ccm overlayfs xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables deflate ctr twofish_generic twofish_avx_x86_64 twofish_x86_64_3way twofish_x86_64 twofish_common camellia_generic camellia_aesni_avx2 camellia_aesni_avx_x86_64 camellia_x86_64 serpent_avx2 serpent_avx_x86_64 serpent_sse2_x86_64 xts serpent_generic blowfish_generic blowfish_x86_64 blowfish_common cast5_avx_x86_64 cast5_generic cast_common des_generic cmac xcbc rmd160 crypto_null af_key xfrm_algo arc4 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm microcode snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi joydev binfmt_misc serio_raw iwlmvm mac80211 snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep lpc_ich rtsx_pci_ms iwlwifi memstick snd_pcm cfg80211 uvcvideo videobuf2_vmalloc videobuf2_memops shpchp videobuf2_core v4l2_common mei_me videodev mei media thinkpad_acpi nvram btusb snd_seq_midi snd_seq_midi_event bluetooth snd_rawmidi 6lowpan_iphc snd_seq snd_seq_device snd_timer snd intel_smartconnect soundcore cuse parport_pc mac_hid ppdev lp parport nls_iso8859_1 uas usb_storage hid_generic usbhid hid dm_crypt mmc_block rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd psmouse i915 ahci e1000e libahci rtsx_pci ptp pps_core i2c_algo_bit drm_kms_helper wmi drm video Aug 1 16:15:59 faire kernel: [31778.831718] CPU: 2 PID: 1834 Comm: Xorg Not tainted 3.16.0-6-generic #11-Ubuntu Aug 1 16:15:59 faire kernel: [31778.831720] Hardware name: LENOVO 20AQCTO1WW/20AQCTO1WW, BIOS GJET71WW (2.21 ) 02/10/2014 Aug 1 16:15:59 faire kernel: [31778.831721] 0009 8800d6233c10 82755538 Aug 1 16:15:59 faire kernel: [31778.831724] 8800d6233c48 8206bb0d 880308eed000 Aug 1 16:15:59 faire kernel: [31778.831726] 880304108240 8800da1e1000 8800da1e1000 8800d6233c58 Aug 1 16:15:59 faire kernel: [31778.831729] Call Trace: Aug 1 16:15:59 faire kernel: [31778.831735] [82755538] dump_stack+0x45/0x56 Aug 1 16:15:59 faire kernel: [31778.831739] [8206bb0d] warn_slowpath_common+0x7d/0xa0 Aug 1 16:15:59 faire kernel: [31778.831742] [8206bbea] warn_slowpath_null+0x1a/0x20 Aug 1 16:15:59 faire kernel: [31778.831765] [c04c6951] intel_crtc_wait_for_pending_flips+0x171/0x180 [i915] Aug 1 16:15:59 faire kernel: [31778.831769] [820b2960] ? prepare_to_wait_event+0x100/0x100 Aug 1 16:15:59 faire kernel: [31778.831787] [c04c9403] intel_crtc_disable_planes+0x33/0x1c0 [i915] Aug 1 16:15:59 faire kernel: [31778.831790] [8275bb2b] ? __ww_mutex_lock+0x1b/0x97 Aug 1 16:15:59 faire kernel: [31778.831807] [c04ca305] haswell_crtc_disable+0x55/0x2f0 [i915] Aug 1 16:15:59 faire kernel: [31778.831809] [8275c062] ? mutex_lock+0x12/0x2f Aug 1 16:15:59 faire kernel: [31778.831823] [c04cad27] intel_crtc_update_dpms+0x67/0xa0 [i915] Aug 1 16:15:59 faire kernel: [31778.831835] [c04cf1e9] intel_connector_dpms+0x59/0x70 [i915] Aug 1 16:15:59 faire kernel: [31778.831848] [c039ea1f] drm_mode_obj_set_property_ioctl+0x39f/0x3b0 [drm] Aug 1 16:15:59 faire kernel: [31778.831858] [c039ea60] drm_mode_connector_property_set_ioctl+0x30/0x40 [drm] Aug 1 16:15:59 faire kernel: [31778.831860] [c0c0c0c0] ? ipv4_conntrack_defrag+0xb0/0x163 [nf_defrag_ipv4] Aug 1 16:15:59 faire kernel: [31778.831868] [c038da3c] drm_ioctl+0x1ec/0x660 [drm] Aug 1 16:15:59 faire kernel: [31778.831873] [821e2d20] do_vfs_ioctl+0x2e0/0x4c0 Aug 1 16:15:59 faire kernel: [31778.831876] [820a2de4] ? vtime_account_user+0x54/0x60 Aug 1 16:15:59 faire kernel: [31778.831878] [821e2f81] SyS_ioctl+0x81/0xa0 Aug 1 16:15:59 faire kernel: [31778.831880] [8275de7f] tracesys+0xe1/0xe6 Aug 1 16:15:59 faire kernel: [31778.831881] ---[ end trace bb931f1719ba6be2 ]--- ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-generic 3.16.0.6.7 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 ApportVersion: 2.14.5-0ubuntu2
[Kernel-packages] [Bug 1348716] Re: kernel oops writing image to sd card
@jsalisbury - I am only using ubuntu-packaged kernels. When I get a chance I'll try to identify the last working kernel. However, can you tell from the stacktrace if this is a generic kernel issue? If so, can the kernel team recreate? @penalvch - my bios may not be at the latest version, but we cannot expect users to go through the hassle of flashing their bios just to write data to an SD card. ** Changed in: linux (Ubuntu) Status: Incomplete = New ** Changed in: linux (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1348716 Title: kernel oops writing image to sd card Status in “linux” package in Ubuntu: Confirmed Bug description: Writing a 3G image to an SD card led to an oops (on both occasions I tried it): $ cat foo.img | sudo dd bs=16M of=/dev/mmcblk0 [36467.181234] Call Trace: [36467.181245] [827596d9] schedule_preempt_disabled+0x29/0x70 [36467.181251] [8275b525] __mutex_lock_slowpath+0xd5/0x1d0 [36467.181278] [8275b63f] mutex_lock+0x1f/0x2f [36467.181283] [822066d3] __blkdev_get+0x63/0x4c0 [36467.181287] [82206cf5] blkdev_get+0x1c5/0x340 [36467.181291] [82206f1b] blkdev_open+0x5b/0x80 [36467.181296] [821cd32f] do_dentry_open+0x1ff/0x350 [36467.181300] [82206ec0] ? blkdev_get_by_dev+0x50/0x50 [36467.181303] [821cd5c9] vfs_open+0x49/0x50 [36467.181309] [821dca94] do_last+0x554/0x1210 [36467.181317] [823226bb] ? apparmor_file_alloc_security+0x5b/0x180 [36467.181322] [821dea1b] path_openat+0xbb/0x620 [36467.181328] [82384d66] ? sprintf+0x46/0x50 [36467.181333] [821e048a] do_filp_open+0x3a/0x90 [36467.181340] [821ecff7] ? __alloc_fd+0xa7/0x130 [36467.181345] [821ceea9] do_sys_open+0x129/0x280 [36467.181349] [82021b55] ? syscall_trace_enter+0x145/0x250 [36467.181353] [821cf01e] SyS_open+0x1e/0x20 [36467.181359] [8275d43f] tracesys+0xe1/0xe6 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-generic 3.16.0.5.6 ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6 Uname: Linux 3.16.0-5-generic x86_64 ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: james 3817 F pulseaudio /dev/snd/controlC1: james 3817 F pulseaudio CurrentDesktop: Unity Date: Fri Jul 25 17:23:47 2014 HibernationDevice: RESUME=UUID=db600bbe-faca-41f4-9338-c3e8e227599a InstallationDate: Installed on 2014-04-11 (104 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409) MachineType: LENOVO 20AQCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-5-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-5-generic N/A linux-backports-modules-3.16.0-5-generic N/A linux-firmware1.132 SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2014-05-08 (78 days ago) dmi.bios.date: 02/10/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET71WW (2.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98405 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AQCTO1WW dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1348716/+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 1348716] [NEW] kernel oops writing image to sd card
Public bug reported: Writing a 3G image to an SD card led to an oops (on both occasions I tried it): $ cat foo.img | sudo dd bs=16M of=/dev/mmcblk0 [36467.181234] Call Trace: [36467.181245] [827596d9] schedule_preempt_disabled+0x29/0x70 [36467.181251] [8275b525] __mutex_lock_slowpath+0xd5/0x1d0 [36467.181278] [8275b63f] mutex_lock+0x1f/0x2f [36467.181283] [822066d3] __blkdev_get+0x63/0x4c0 [36467.181287] [82206cf5] blkdev_get+0x1c5/0x340 [36467.181291] [82206f1b] blkdev_open+0x5b/0x80 [36467.181296] [821cd32f] do_dentry_open+0x1ff/0x350 [36467.181300] [82206ec0] ? blkdev_get_by_dev+0x50/0x50 [36467.181303] [821cd5c9] vfs_open+0x49/0x50 [36467.181309] [821dca94] do_last+0x554/0x1210 [36467.181317] [823226bb] ? apparmor_file_alloc_security+0x5b/0x180 [36467.181322] [821dea1b] path_openat+0xbb/0x620 [36467.181328] [82384d66] ? sprintf+0x46/0x50 [36467.181333] [821e048a] do_filp_open+0x3a/0x90 [36467.181340] [821ecff7] ? __alloc_fd+0xa7/0x130 [36467.181345] [821ceea9] do_sys_open+0x129/0x280 [36467.181349] [82021b55] ? syscall_trace_enter+0x145/0x250 [36467.181353] [821cf01e] SyS_open+0x1e/0x20 [36467.181359] [8275d43f] tracesys+0xe1/0xe6 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-generic 3.16.0.5.6 ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6 Uname: Linux 3.16.0-5-generic x86_64 ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: james 3817 F pulseaudio /dev/snd/controlC1: james 3817 F pulseaudio CurrentDesktop: Unity Date: Fri Jul 25 17:23:47 2014 HibernationDevice: RESUME=UUID=db600bbe-faca-41f4-9338-c3e8e227599a InstallationDate: Installed on 2014-04-11 (104 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409) MachineType: LENOVO 20AQCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-5-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-5-generic N/A linux-backports-modules-3.16.0-5-generic N/A linux-firmware1.132 SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2014-05-08 (78 days ago) dmi.bios.date: 02/10/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET71WW (2.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98405 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AQCTO1WW dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug 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/1348716 Title: kernel oops writing image to sd card Status in “linux” package in Ubuntu: Confirmed Bug description: Writing a 3G image to an SD card led to an oops (on both occasions I tried it): $ cat foo.img | sudo dd bs=16M of=/dev/mmcblk0 [36467.181234] Call Trace: [36467.181245] [827596d9] schedule_preempt_disabled+0x29/0x70 [36467.181251] [8275b525] __mutex_lock_slowpath+0xd5/0x1d0 [36467.181278] [8275b63f] mutex_lock+0x1f/0x2f [36467.181283] [822066d3] __blkdev_get+0x63/0x4c0 [36467.181287] [82206cf5] blkdev_get+0x1c5/0x340 [36467.181291] [82206f1b] blkdev_open+0x5b/0x80 [36467.181296] [821cd32f] do_dentry_open+0x1ff/0x350 [36467.181300] [82206ec0] ? blkdev_get_by_dev+0x50/0x50 [36467.181303] [821cd5c9] vfs_open+0x49/0x50 [36467.181309] [821dca94] do_last+0x554/0x1210 [36467.181317] [823226bb] ? apparmor_file_alloc_security+0x5b/0x180 [36467.181322] [821dea1b] path_openat+0xbb/0x620 [36467.181328] [82384d66] ? sprintf+0x46/0x50 [36467.181333] [821e048a] do_filp_open+0x3a/0x90 [36467.181340] [821ecff7] ? __alloc_fd+0xa7/0x130 [36467.181345] [821ceea9] do_sys_open+0x129/0x280 [36467.181349] [82021b55] ? syscall_trace_enter+0x145/0x250 [36467.181353] [821cf01e] SyS_open+0x1e/0x20 [36467.181359] [8275d43f] tracesys+0xe1/0xe6 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-generic 3.16.0.5.6 ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6 Uname: Linux 3.16.0-5-generic x86_64 ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse:
[Kernel-packages] [Bug 1235649] Re: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch
** Changed in: upstart Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch Status in Touch Landing Plan: Fix Released Status in Unity: Confirmed Status in Upstart: Fix Released Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: Confirmed Status in “upstart” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: Invalid Status in “unity” source package in Saucy: Confirmed Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/landing-plan/+bug/1235649/+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 1340798] [NEW] ubuntu touch kernel oops / BUG on armhf image r126
Public bug reported: [0.70] BUG: Bad page state in process modprobe pfn:0 [0.70] page:81041000 count:0 mapcount:-127 mapping: (null) index:0x0 [0.70] page flags: 0x0() [0.70] Modules linked in: [0.70] [80012bb8] (unwind_backtrace+0x0/0x11c) from [800a30a4] (bad_page+0xd4/0x100) [0.70] [800a30a4] (bad_page+0xd4/0x100) from [800a3194] (free_pages_prepare+0xc4/0x184) [0.70] [800a3194] (free_pages_prepare+0xc4/0x184) from [800a47d0] (free_hot_cold_page+0x20/0x180) [0.70] [800a47d0] (free_hot_cold_page+0x20/0x180) from [800ba568] (do_wp_page.isra.71+0x730/0x780) [0.70] [800ba568] (do_wp_page.isra.71+0x730/0x780) from [800bc388] (handle_mm_fault+0xac/0xd8) [0.70] [800bc388] (handle_mm_fault+0xac/0xd8) from [80414eb4] (do_page_fault+0x168/0x398) [0.70] [80414eb4] (do_page_fault+0x168/0x398) from [80008390] (do_DataAbort+0x34/0x98) [0.70] [80008390] (do_DataAbort+0x34/0x98) from [80413898] (__dabt_svc+0x38/0x60) [0.70] Exception stack(0xeeb7de00 to 0xeeb7de48) [0.70] de00: 76fa722c 0dcc ee8391c0 eeba4d80 76fa7270 [0.70] de20: 76f8e000 76fa722c ef107f00 76fa722c eeb7de48 80113dc4 80235e70 [0.70] de40: 2013 [0.70] [80413898] (__dabt_svc+0x38/0x60) from [80235e70] (__clear_user_std+0x34/0x64) [0.71] Disabling lock debugging due to kernel taint $ ps -ef|grep emulator james 3604 29836 0 16:16 pts/400:00:00 ubuntu-emulator run 11july2014-armhf --memory=2048 james 3609 3604 99 16:16 pts/400:07:49 /usr/share/android/emulator/out/host/linux-x86/bin/emulator-arm -memory 2048 -skindir /usr/share/ubuntu-emulator/skins -skin EDGE -sysdir /home/james/.local/share/ubuntu-emulator/11july2014-armhf -kernel /home/james/.local/share/ubuntu-emulator/11july2014-armhf/ubuntu-kernel -ramdisk /home/james/.local/share/ubuntu-emulator/11july2014-armhf/ramdisk.img -data /home/james/.local/share/ubuntu-emulator/11july2014-armhf/userdata.img -system /home/james/.local/share/ubuntu-emulator/11july2014-armhf/system.img -sdcard /home/james/.local/share/ubuntu-emulator/11july2014-armhf/sdcard.img -cache /home/james/.local/share/ubuntu-emulator/11july2014-armhf/cache.img -force-32bit -no-snapstorage -gpu on -scale 1.0 -shell -no-jni -show-kernel -verbose -qemu -cpu cortex-a9 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Attachment added: ubuntu-emulator log https://bugs.launchpad.net/bugs/1340798/+attachment/4150482/+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/1340798 Title: ubuntu touch kernel oops / BUG on armhf image r126 Status in “linux” package in Ubuntu: Incomplete Bug description: [0.70] BUG: Bad page state in process modprobe pfn:0 [0.70] page:81041000 count:0 mapcount:-127 mapping: (null) index:0x0 [0.70] page flags: 0x0() [0.70] Modules linked in: [0.70] [80012bb8] (unwind_backtrace+0x0/0x11c) from [800a30a4] (bad_page+0xd4/0x100) [0.70] [800a30a4] (bad_page+0xd4/0x100) from [800a3194] (free_pages_prepare+0xc4/0x184) [0.70] [800a3194] (free_pages_prepare+0xc4/0x184) from [800a47d0] (free_hot_cold_page+0x20/0x180) [0.70] [800a47d0] (free_hot_cold_page+0x20/0x180) from [800ba568] (do_wp_page.isra.71+0x730/0x780) [0.70] [800ba568] (do_wp_page.isra.71+0x730/0x780) from [800bc388] (handle_mm_fault+0xac/0xd8) [0.70] [800bc388] (handle_mm_fault+0xac/0xd8) from [80414eb4] (do_page_fault+0x168/0x398) [0.70] [80414eb4] (do_page_fault+0x168/0x398) from [80008390] (do_DataAbort+0x34/0x98) [0.70] [80008390] (do_DataAbort+0x34/0x98) from [80413898] (__dabt_svc+0x38/0x60) [0.70] Exception stack(0xeeb7de00 to 0xeeb7de48) [0.70] de00: 76fa722c 0dcc ee8391c0 eeba4d80 76fa7270 [0.70] de20: 76f8e000 76fa722c ef107f00 76fa722c eeb7de48 80113dc4 80235e70 [0.70] de40: 2013 [0.70] [80413898] (__dabt_svc+0x38/0x60) from [80235e70] (__clear_user_std+0x34/0x64) [0.71] Disabling lock debugging due to kernel taint $ ps -ef|grep emulator james 3604 29836 0 16:16 pts/400:00:00 ubuntu-emulator run 11july2014-armhf --memory=2048 james 3609 3604 99 16:16 pts/400:07:49 /usr/share/android/emulator/out/host/linux-x86/bin/emulator-arm -memory 2048 -skindir /usr/share/ubuntu-emulator/skins -skin EDGE -sysdir /home/james/.local/share/ubuntu-emulator/11july2014-armhf -kernel /home/james/.local/share/ubuntu-emulator/11july2014-armhf/ubuntu-kernel -ramdisk /home/james/.local/share/ubuntu-emulator/11july2014-armhf/ramdisk.img -data
[Kernel-packages] [Bug 1326861] [NEW] kerneloops ignores WARNING: oops messages
Public bug reported: The kerneloops daemon ignores WARNING-type oops's. This seems to be due to bug 346303 (2009). Is this behaviour still in line with our processes? I'm guessing not since the kernel team don't seem to be aware of this silent filtering and it means that we would miss crash reports such as bug 1326300. The fix is to remove the filter on WARNING: in pipe_oopses() - updated patch attached. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: kerneloops-daemon 0.12+git20090217-3ubuntu8 ProcVersionSignature: Ubuntu 3.15.0-5.10-generic 3.15.0-rc8 Uname: Linux 3.15.0-5-generic x86_64 ApportVersion: 2.14.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 5 14:09:04 2014 InstallationDate: Installed on 2014-04-11 (54 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409) SourcePackage: kerneloops UpgradeStatus: Upgraded to utopic on 2014-05-08 (28 days ago) modified.conffile..etc.kerneloops.conf: [modified] mtime.conffile..etc.kerneloops.conf: 2014-06-05T14:00:14.231359 ** Affects: kerneloops (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic ** Patch added: ubuntu-add-submit-pipe.patch https://bugs.launchpad.net/bugs/1326861/+attachment/4125949/+files/ubuntu-add-submit-pipe.patch ** Summary changed: - kerneloops ignored some oops messages + kerneloops ignores WARNING: oops messages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kerneloops in Ubuntu. https://bugs.launchpad.net/bugs/1326861 Title: kerneloops ignores WARNING: oops messages Status in “kerneloops” package in Ubuntu: New Bug description: The kerneloops daemon ignores WARNING-type oops's. This seems to be due to bug 346303 (2009). Is this behaviour still in line with our processes? I'm guessing not since the kernel team don't seem to be aware of this silent filtering and it means that we would miss crash reports such as bug 1326300. The fix is to remove the filter on WARNING: in pipe_oopses() - updated patch attached. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: kerneloops-daemon 0.12+git20090217-3ubuntu8 ProcVersionSignature: Ubuntu 3.15.0-5.10-generic 3.15.0-rc8 Uname: Linux 3.15.0-5-generic x86_64 ApportVersion: 2.14.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 5 14:09:04 2014 InstallationDate: Installed on 2014-04-11 (54 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409) SourcePackage: kerneloops UpgradeStatus: Upgraded to utopic on 2014-05-08 (28 days ago) modified.conffile..etc.kerneloops.conf: [modified] mtime.conffile..etc.kerneloops.conf: 2014-06-05T14:00:14.231359 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kerneloops/+bug/1326861/+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 1326300] [NEW] Logitech QuickCam 4000 Pro causes kernel oops when video switched off
Public bug reported: To reproduce: 1) Plug in Logitech QuickCam 4000 Pro via USB 2) Run 'mplayer -tv device=/dev/video1 tv://' 3) Quit mplayer 4) Run, 'dmesg|grep -q 'Call Trace:' echo found bug' 5) Observe that 'found bug' is displayed. [ 9477.565079] usb 2-1: new full-speed USB device number 10 using xhci_hcd [ 9477.820828] usb 2-1: New USB device found, idVendor=046d, idProduct=08b2 [ 9477.820835] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 9477.821394] usb 2-1: ep 0x82 - rounding interval to 512 microframes, ep desc says 800 microframes [ 9477.839316] pwc: Logitech QuickCam 4000 Pro USB webcam detected. [ 9478.277667] pwc: Registered as video1. [ 9478.277850] input: PWC snapshot button as /devices/pci:00/:00:14.0/usb2/2-1/input/input17 [ 9478.278188] usbcore: registered new interface driver Philips webcam [ 9478.317402] usbcore: registered new interface driver snd-usb-audio [ 9484.954720] usb 2-1: ep 0x82 - rounding interval to 512 microframes, ep desc says 800 microframes [ 9665.533822] usb 2-1: USB disconnect, device number 10 [ 9677.033044] usb 2-3: new full-speed USB device number 11 using xhci_hcd [ 9679.218500] usb 2-3: New USB device found, idVendor=046d, idProduct=08b2 [ 9679.218512] usb 2-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 9679.218820] usb 2-3: ep 0x82 - rounding interval to 512 microframes, ep desc says 800 microframes [ 9679.220197] pwc: Logitech QuickCam 4000 Pro USB webcam detected. [ 9679.674614] pwc: Registered as video2. [ 9679.674713] input: PWC snapshot button as /devices/pci:00/:00:14.0/usb2/2-3/input/input18 [ 9681.296102] [ cut here ] [ 9681.296132] WARNING: CPU: 0 PID: 6039 at /build/buildd/linux-3.15.0/drivers/media/v4l2-core/videobuf2-core.c:2011 __vb2_queue_cancel+0x116/0x180 [videobuf2_core]() [ 9681.296135] Modules linked in: snd_usb_audio snd_usbmidi_lib pwc v4l2_common veth ccm overlayfs xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables deflate ctr twofish_generic twofish_avx_x86_64 twofish_x86_64_3way twofish_x86_64 twofish_common camellia_generic camellia_aesni_avx2 camellia_aesni_avx_x86_64 camellia_x86_64 serpent_avx2 serpent_avx_x86_64 serpent_sse2_x86_64 xts serpent_generic blowfish_generic blowfish_x86_64 blowfish_common cast5_avx_x86_64 cast5_generic cast_common des_generic cmac xcbc rmd160 crypto_null af_key xfrm_algo arc4 snd_hda_codec_hdmi snd_hda_codec_realtek intel_rapl snd_hda_codec_generic x86_pkg_temp_thermal intel_powerclamp coretemp thinkpad_acpi kvm_intel nvram snd_hda_intel iwlmvm snd_hda_controller kvm snd_hda_codec uvcvideo mac80211 snd_hwdep videobuf2_vmalloc videobuf2_memops snd_pcm videobuf2_core snd_seq_midi snd_seq_midi_event microcode snd_rawmidi videodev snd_seq snd_seq_device iwlwifi joydev snd_timer serio_raw btusb rtsx_pci_ms bluetooth memstick 6lowpan_iphc cfg80211 snd mei_me mei mac_hid shpchp intel_smartconnect lpc_ich soundcore cuse parport_pc ppdev lp binfmt_misc parport nls_iso8859_1 uas usb_storage hid_generic usbhid hid dm_crypt mmc_block rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd psmouse i915 ahci e1000e libahci rtsx_pci ptp pps_core wmi i2c_algo_bit drm_kms_helper drm video [ 9681.296240] CPU: 0 PID: 6039 Comm: mplayer Not tainted 3.15.0-5-generic #10-Ubuntu [ 9681.296243] Hardware name: LENOVO 20AQCTO1WW/20AQCTO1WW, BIOS GJET71WW (2.21 ) 02/10/2014 [ 9681.296245] 0009 88028db5fdb0 81733bb4 [ 9681.296249] 88028db5fde8 81066a6d 8801dc2b0670 [ 9681.296252] 8803097f7a18 8801dc2b0420 88007a0f9780 88028db5fdf8 [ 9681.296256] Call Trace: [ 9681.296266] [81733bb4] dump_stack+0x45/0x56 [ 9681.296273] [81066a6d] warn_slowpath_common+0x7d/0xa0 [ 9681.296277] [81066b4a] warn_slowpath_null+0x1a/0x20 [ 9681.296285] [a04d74b6] __vb2_queue_cancel+0x116/0x180 [videobuf2_core] [ 9681.296293] [a04d9c9a] vb2_queue_release+0x1a/0x30 [videobuf2_core] [ 9681.296301] [a04d9d11] _vb2_fop_release+0x61/0xa0 [videobuf2_core] [ 9681.296308] [a04d9d7a] vb2_fop_release+0x2a/0x50 [videobuf2_core] [ 9681.296320] [a04ab434] v4l2_release+0x34/0x80 [videodev] [ 9681.296326] [811c4114] __fput+0xe4/0x220 [ 9681.296331] [811c429e] fput+0xe/0x10 [ 9681.296335] [81086f37] task_work_run+0xa7/0xe0 [ 9681.296342] [81012db7] do_notify_resume+0x97/0xb0 [ 9681.296349] [81744f6a] int_signal+0x12/0x17 [ 9681.296352] ---[ end trace 06de6c117115a86a ]--- [ 9681.296354] [ cut here ] [ 9681.296360] WARNING: CPU: 0 PID: 6039 at /build/buildd/linux-3.15.0/drivers/media/v4l2-core/videobuf2-core.c:1095
[Kernel-packages] [Bug 1326300] Re: Logitech QuickCam 4000 Pro causes kernel oops when video switched off
Note that usb camera is still plugged when oops occurs. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1326300 Title: Logitech QuickCam 4000 Pro causes kernel oops when video switched off Status in “linux” package in Ubuntu: New Bug description: To reproduce: 1) Plug in Logitech QuickCam 4000 Pro via USB 2) Run 'mplayer -tv device=/dev/video1 tv://' 3) Quit mplayer 4) Run, 'dmesg|grep -q 'Call Trace:' echo found bug' 5) Observe that 'found bug' is displayed. [ 9477.565079] usb 2-1: new full-speed USB device number 10 using xhci_hcd [ 9477.820828] usb 2-1: New USB device found, idVendor=046d, idProduct=08b2 [ 9477.820835] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 9477.821394] usb 2-1: ep 0x82 - rounding interval to 512 microframes, ep desc says 800 microframes [ 9477.839316] pwc: Logitech QuickCam 4000 Pro USB webcam detected. [ 9478.277667] pwc: Registered as video1. [ 9478.277850] input: PWC snapshot button as /devices/pci:00/:00:14.0/usb2/2-1/input/input17 [ 9478.278188] usbcore: registered new interface driver Philips webcam [ 9478.317402] usbcore: registered new interface driver snd-usb-audio [ 9484.954720] usb 2-1: ep 0x82 - rounding interval to 512 microframes, ep desc says 800 microframes [ 9665.533822] usb 2-1: USB disconnect, device number 10 [ 9677.033044] usb 2-3: new full-speed USB device number 11 using xhci_hcd [ 9679.218500] usb 2-3: New USB device found, idVendor=046d, idProduct=08b2 [ 9679.218512] usb 2-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 9679.218820] usb 2-3: ep 0x82 - rounding interval to 512 microframes, ep desc says 800 microframes [ 9679.220197] pwc: Logitech QuickCam 4000 Pro USB webcam detected. [ 9679.674614] pwc: Registered as video2. [ 9679.674713] input: PWC snapshot button as /devices/pci:00/:00:14.0/usb2/2-3/input/input18 [ 9681.296102] [ cut here ] [ 9681.296132] WARNING: CPU: 0 PID: 6039 at /build/buildd/linux-3.15.0/drivers/media/v4l2-core/videobuf2-core.c:2011 __vb2_queue_cancel+0x116/0x180 [videobuf2_core]() [ 9681.296135] Modules linked in: snd_usb_audio snd_usbmidi_lib pwc v4l2_common veth ccm overlayfs xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables deflate ctr twofish_generic twofish_avx_x86_64 twofish_x86_64_3way twofish_x86_64 twofish_common camellia_generic camellia_aesni_avx2 camellia_aesni_avx_x86_64 camellia_x86_64 serpent_avx2 serpent_avx_x86_64 serpent_sse2_x86_64 xts serpent_generic blowfish_generic blowfish_x86_64 blowfish_common cast5_avx_x86_64 cast5_generic cast_common des_generic cmac xcbc rmd160 crypto_null af_key xfrm_algo arc4 snd_hda_codec_hdmi snd_hda_codec_realtek intel_rapl snd_hda_codec_generic x86_pkg_temp_thermal intel_powerclamp coretemp thinkpad_acpi kvm_intel nvram snd_hda_intel iwlmvm snd_hda_controller kvm snd_hda_codec uvcvideo mac80211 snd_hwdep videobuf2_vmalloc videobuf2_memops snd_pcm videobuf2_core snd_seq_midi snd_seq_midi_event microcode snd_rawmidi videodev snd_seq snd_seq_device iwlwifi joydev snd_timer serio_raw btusb rtsx_pci_ms bluetooth memstick 6lowpan_iphc cfg80211 snd mei_me mei mac_hid shpchp intel_smartconnect lpc_ich soundcore cuse parport_pc ppdev lp binfmt_misc parport nls_iso8859_1 uas usb_storage hid_generic usbhid hid dm_crypt mmc_block rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd psmouse i915 ahci e1000e libahci rtsx_pci ptp pps_core wmi i2c_algo_bit drm_kms_helper drm video [ 9681.296240] CPU: 0 PID: 6039 Comm: mplayer Not tainted 3.15.0-5-generic #10-Ubuntu [ 9681.296243] Hardware name: LENOVO 20AQCTO1WW/20AQCTO1WW, BIOS GJET71WW (2.21 ) 02/10/2014 [ 9681.296245] 0009 88028db5fdb0 81733bb4 [ 9681.296249] 88028db5fde8 81066a6d 8801dc2b0670 [ 9681.296252] 8803097f7a18 8801dc2b0420 88007a0f9780 88028db5fdf8 [ 9681.296256] Call Trace: [ 9681.296266] [81733bb4] dump_stack+0x45/0x56 [ 9681.296273] [81066a6d] warn_slowpath_common+0x7d/0xa0 [ 9681.296277] [81066b4a] warn_slowpath_null+0x1a/0x20 [ 9681.296285] [a04d74b6] __vb2_queue_cancel+0x116/0x180 [videobuf2_core] [ 9681.296293] [a04d9c9a] vb2_queue_release+0x1a/0x30 [videobuf2_core] [ 9681.296301] [a04d9d11] _vb2_fop_release+0x61/0xa0 [videobuf2_core] [ 9681.296308] [a04d9d7a] vb2_fop_release+0x2a/0x50 [videobuf2_core] [ 9681.296320] [a04ab434] v4l2_release+0x34/0x80 [videodev] [ 9681.296326] [811c4114] __fput+0xe4/0x220 [ 9681.296331]
[Kernel-packages] [Bug 1326300] Re: Logitech QuickCam 4000 Pro causes kernel oops when video switched off
Works fine with trusty using 3.13.0-24-generic and 3.13.0-27-generic (different laptop - Lenovo T410). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1326300 Title: Logitech QuickCam 4000 Pro causes kernel oops when video switched off Status in “linux” package in Ubuntu: Confirmed Bug description: To reproduce: 1) Plug in Logitech QuickCam 4000 Pro via USB 2) Run 'mplayer -tv device=/dev/video1 tv://' 3) Quit mplayer 4) Run, 'dmesg|grep -q 'Call Trace:' echo found bug' 5) Observe that 'found bug' is displayed. [ 9477.565079] usb 2-1: new full-speed USB device number 10 using xhci_hcd [ 9477.820828] usb 2-1: New USB device found, idVendor=046d, idProduct=08b2 [ 9477.820835] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 9477.821394] usb 2-1: ep 0x82 - rounding interval to 512 microframes, ep desc says 800 microframes [ 9477.839316] pwc: Logitech QuickCam 4000 Pro USB webcam detected. [ 9478.277667] pwc: Registered as video1. [ 9478.277850] input: PWC snapshot button as /devices/pci:00/:00:14.0/usb2/2-1/input/input17 [ 9478.278188] usbcore: registered new interface driver Philips webcam [ 9478.317402] usbcore: registered new interface driver snd-usb-audio [ 9484.954720] usb 2-1: ep 0x82 - rounding interval to 512 microframes, ep desc says 800 microframes [ 9665.533822] usb 2-1: USB disconnect, device number 10 [ 9677.033044] usb 2-3: new full-speed USB device number 11 using xhci_hcd [ 9679.218500] usb 2-3: New USB device found, idVendor=046d, idProduct=08b2 [ 9679.218512] usb 2-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 9679.218820] usb 2-3: ep 0x82 - rounding interval to 512 microframes, ep desc says 800 microframes [ 9679.220197] pwc: Logitech QuickCam 4000 Pro USB webcam detected. [ 9679.674614] pwc: Registered as video2. [ 9679.674713] input: PWC snapshot button as /devices/pci:00/:00:14.0/usb2/2-3/input/input18 [ 9681.296102] [ cut here ] [ 9681.296132] WARNING: CPU: 0 PID: 6039 at /build/buildd/linux-3.15.0/drivers/media/v4l2-core/videobuf2-core.c:2011 __vb2_queue_cancel+0x116/0x180 [videobuf2_core]() [ 9681.296135] Modules linked in: snd_usb_audio snd_usbmidi_lib pwc v4l2_common veth ccm overlayfs xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables deflate ctr twofish_generic twofish_avx_x86_64 twofish_x86_64_3way twofish_x86_64 twofish_common camellia_generic camellia_aesni_avx2 camellia_aesni_avx_x86_64 camellia_x86_64 serpent_avx2 serpent_avx_x86_64 serpent_sse2_x86_64 xts serpent_generic blowfish_generic blowfish_x86_64 blowfish_common cast5_avx_x86_64 cast5_generic cast_common des_generic cmac xcbc rmd160 crypto_null af_key xfrm_algo arc4 snd_hda_codec_hdmi snd_hda_codec_realtek intel_rapl snd_hda_codec_generic x86_pkg_temp_thermal intel_powerclamp coretemp thinkpad_acpi kvm_intel nvram snd_hda_intel iwlmvm snd_hda_controller kvm snd_hda_codec uvcvideo mac80211 snd_hwdep videobuf2_vmalloc videobuf2_memops snd_pcm videobuf2_core snd_seq_midi snd_seq_midi_event microcode snd_rawmidi videodev snd_seq snd_seq_device iwlwifi joydev snd_timer serio_raw btusb rtsx_pci_ms bluetooth memstick 6lowpan_iphc cfg80211 snd mei_me mei mac_hid shpchp intel_smartconnect lpc_ich soundcore cuse parport_pc ppdev lp binfmt_misc parport nls_iso8859_1 uas usb_storage hid_generic usbhid hid dm_crypt mmc_block rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd psmouse i915 ahci e1000e libahci rtsx_pci ptp pps_core wmi i2c_algo_bit drm_kms_helper drm video [ 9681.296240] CPU: 0 PID: 6039 Comm: mplayer Not tainted 3.15.0-5-generic #10-Ubuntu [ 9681.296243] Hardware name: LENOVO 20AQCTO1WW/20AQCTO1WW, BIOS GJET71WW (2.21 ) 02/10/2014 [ 9681.296245] 0009 88028db5fdb0 81733bb4 [ 9681.296249] 88028db5fde8 81066a6d 8801dc2b0670 [ 9681.296252] 8803097f7a18 8801dc2b0420 88007a0f9780 88028db5fdf8 [ 9681.296256] Call Trace: [ 9681.296266] [81733bb4] dump_stack+0x45/0x56 [ 9681.296273] [81066a6d] warn_slowpath_common+0x7d/0xa0 [ 9681.296277] [81066b4a] warn_slowpath_null+0x1a/0x20 [ 9681.296285] [a04d74b6] __vb2_queue_cancel+0x116/0x180 [videobuf2_core] [ 9681.296293] [a04d9c9a] vb2_queue_release+0x1a/0x30 [videobuf2_core] [ 9681.296301] [a04d9d11] _vb2_fop_release+0x61/0xa0 [videobuf2_core] [ 9681.296308] [a04d9d7a] vb2_fop_release+0x2a/0x50 [videobuf2_core] [ 9681.296320] [a04ab434] v4l2_release+0x34/0x80 [videodev] [ 9681.296326]
[Kernel-packages] [Bug 1322067] [NEW] 3.15.0.1.2 breaks lxc-attach for unprivileged containers
Public bug reported: An unprivileged call to lxc-attach fails with kernel 3.15.0.1.2, but works fine using 3.13.0-24-generic. Under 3.15.0.1.2, attempting to connect to a running unprivileged container: $ lxc-attach --clear-env -n trusty -- /bin/true lxc-attach: Permission denied - Could not open /proc/3805/personality lxc-attach: failed to get context of the init process, pid = 3805 Note that lxc-start and lxc-console are not affected. To recreate: 1) Create an unpriv container: $ lxc-create -n utopic -t download -- -d ubuntu -r utopic -a amd64 2) Boot with 3.13.0-24-generic 3) Start the container: $ lxc-start -n utopic 4) Run a command in the container: $ lxc-attach -n utopic --clear-env -n trusty -- /bin/true 5) Reboot into 3.15.0.1.2 and re-run the lxc-start and lxc-attach. 6) Observe the EPERM error. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-generic 3.15.0.1.2 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.2-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 2827 F pulseaudio /dev/snd/pcmC1D0p: james 2827 F...m pulseaudio /dev/snd/controlC0: james 2827 F pulseaudio CurrentDesktop: Unity Date: Thu May 22 07:21:55 2014 HibernationDevice: RESUME=UUID=db600bbe-faca-41f4-9338-c3e8e227599a InstallationDate: Installed on 2014-04-11 (40 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409) MachineType: LENOVO 20AQCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.129 SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2014-05-08 (13 days ago) dmi.bios.date: 02/10/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET71WW (2.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98405 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AQCTO1WW dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1322067 Title: 3.15.0.1.2 breaks lxc-attach for unprivileged containers Status in “linux” package in Ubuntu: New Bug description: An unprivileged call to lxc-attach fails with kernel 3.15.0.1.2, but works fine using 3.13.0-24-generic. Under 3.15.0.1.2, attempting to connect to a running unprivileged container: $ lxc-attach --clear-env -n trusty -- /bin/true lxc-attach: Permission denied - Could not open /proc/3805/personality lxc-attach: failed to get context of the init process, pid = 3805 Note that lxc-start and lxc-console are not affected. To recreate: 1) Create an unpriv container: $ lxc-create -n utopic -t download -- -d ubuntu -r utopic -a amd64 2) Boot with 3.13.0-24-generic 3) Start the container: $ lxc-start -n utopic 4) Run a command in the container: $ lxc-attach -n utopic --clear-env -n trusty -- /bin/true 5) Reboot into 3.15.0.1.2 and re-run the lxc-start and lxc-attach. 6) Observe the EPERM error. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-generic 3.15.0.1.2 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.2-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 2827 F pulseaudio /dev/snd/pcmC1D0p: james 2827 F...m pulseaudio /dev/snd/controlC0: james 2827 F pulseaudio CurrentDesktop: Unity Date: Thu May 22 07:21:55 2014 HibernationDevice: RESUME=UUID=db600bbe-faca-41f4-9338-c3e8e227599a InstallationDate: Installed on 2014-04-11 (40 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409) MachineType: LENOVO 20AQCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.129 SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2014-05-08 (13 days ago) dmi.bios.date: 02/10/2014 dmi.bios.vendor:
[Kernel-packages] [Bug 1319141] Re: [Lenovo ThinkPad T440s] Kernel oops before suspend
Problem no longer occurs running kernel 3.15.0-1-generic. ** Changed in: linux (Ubuntu) Status: Incomplete = Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1319141 Title: [Lenovo ThinkPad T440s] Kernel oops before suspend Status in “linux” package in Ubuntu: Invalid Bug description: May 13 18:22:10 faire kernel: [35947.754796] PM: Syncing filesystems ... done. May 13 18:22:10 faire kernel: [35947.782070] PM: Preparing system for mem sleep May 13 19:17:45 faire kernel: [35947.782396] mmc0: card b368 removed May 13 19:17:45 faire kernel: [35947.784816] Freezing user space processes ... (elapsed 0.002 seconds) done. May 13 19:17:45 faire kernel: [35947.787286] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. May 13 19:17:45 faire kernel: [35947.788760] PM: Entering mem sleep May 13 19:17:45 faire kernel: [35947.788841] Suspending console(s) (use no_console_suspend to debug) May 13 19:17:45 faire kernel: [35947.935975] sd 1:0:0:0: [sdb] Synchronizing SCSI cache May 13 19:17:45 faire kernel: [35947.936044] sd 1:0:0:0: [sdb] Stopping disk May 13 19:17:45 faire kernel: [35947.936099] sd 0:0:0:0: [sda] Synchronizing SCSI cache May 13 19:17:45 faire kernel: [35947.938056] sd 0:0:0:0: [sda] Stopping disk May 13 19:17:45 faire kernel: [35948.162233] [ cut here ] May 13 19:17:45 faire kernel: [35948.162268] WARNING: CPU: 0 PID: 32245 at /build/buildd/linux-3.13.0/drivers/gpu/drm/i915/intel_uncore.c:125 gen6_gt_check_fifodbg.isra.9+0x38/0x50 [i915]() May 13 19:17:45 faire kernel: [35948.162268] MMIO read or write has been dropped May 13 19:17:45 faire kernel: [35948.162292] Modules linked in: ums_cypress usb_storage veth ccm hid_generic usbhid hid xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables deflate ctr twofish_generic twofish_avx_x86_64 twofish_x86_64_3way twofish_x86_64 twofish_common camellia_generic camellia_aesni_avx2 camellia_aesni_avx_x86_64 camellia_x86_64 serpent_avx2 serpent_avx_x86_64 serpent_sse2_x86_64 xts serpent_generic blowfish_generic blowfish_x86_64 blowfish_common cast5_avx_x86_64 cast5_generic cast_common des_generic cmac xcbc rmd160 crypto_null af_key xfrm_algo arc4 uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp iwlmvm kvm_intel mac80211 kvm joydev snd_hda_codec_hdmi serio_raw snd_hda_codec_realtek rtsx_pci_ms memstick iwlwifi btusb bluetooth thinkpad_acpi snd_hda_intel nvram snd_hda_codec cfg80211 snd_seq_midi snd_seq_midi_event snd_hwdep snd_pcm snd_rawmidi lpc_ich snd_seq mei_me snd_page_alloc snd_seq_device mei snd_timer snd soundcore binfmt_misc mac_hid intel_smartconnect cuse parport_pc ppdev lp parport nls_iso8859_1 dm_crypt mmc_block rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd i915 psmouse ahci e1000e libahci rtsx_pci i2c_algo_bit ptp drm_kms_helper pps_core drm wmi video May 13 19:17:45 faire kernel: [35948.162318] CPU: 0 PID: 32245 Comm: kworker/u16:0 Not tainted 3.13.0-24-generic #47-Ubuntu May 13 19:17:45 faire kernel: [35948.162319] Hardware name: LENOVO 20AQCTO1WW/20AQCTO1WW, BIOS GJET71WW (2.21 ) 02/10/2014 May 13 19:17:45 faire kernel: [35948.162330] Workqueue: i915 gen6_force_wake_work [i915] May 13 19:17:45 faire kernel: [35948.162332] 0009 880236459d38 81715ac4 880236459d80 May 13 19:17:45 faire kernel: [35948.162333] 880236459d70 810676bd 880306fb0020 880306fb0028 May 13 19:17:45 faire kernel: [35948.162335] 0246 0200 880236459dd0 May 13 19:17:45 faire kernel: [35948.162335] Call Trace: May 13 19:17:45 faire kernel: [35948.162339] [81715ac4] dump_stack+0x45/0x56 May 13 19:17:45 faire kernel: [35948.162341] [810676bd] warn_slowpath_common+0x7d/0xa0 May 13 19:17:45 faire kernel: [35948.162342] [8106772c] warn_slowpath_fmt+0x4c/0x50 May 13 19:17:45 faire kernel: [35948.162353] [a018ede8] gen6_gt_check_fifodbg.isra.9+0x38/0x50 [i915] May 13 19:17:45 faire kernel: [35948.162363] [a018ee8b] __gen6_gt_force_wake_mt_put+0x2b/0x30 [i915] May 13 19:17:45 faire kernel: [35948.162371] [a018ebb7] gen6_force_wake_work+0x37/0x50 [i915] May 13 19:17:45 faire kernel: [35948.162374] [810838a2] process_one_work+0x182/0x450 May 13 19:17:45 faire kernel: [35948.162376] [81084641] worker_thread+0x121/0x410 May 13 19:17:45 faire kernel: [35948.162377] [81084520] ? rescuer_thread+0x3e0/0x3e0 May 13 19:17:45 faire kernel: [35948.162379]
[Kernel-packages] [Bug 1319141] Re: [Lenovo ThinkPad T440s] Kernel oops before suspend
Hi Joseph - in the past few days created a script to show a pop up when I get any kernel oopses and that is what caused me to raise the bug. However, checking my logs the earliest occurrence I have is from April 21 with same kernel version (3.13.0-24-generic): Apr 21 18:10:09 faire kernel: [ 5637.053582] PM: Syncing filesystems ... done. Apr 21 18:10:09 faire kernel: [ 5637.058987] PM: Preparing system for mem sleep Apr 21 18:10:09 faire kernel: [ 5637.059271] mmc0: card b368 removed Apr 21 18:25:39 faire kernel: [ 5637.061398] Freezing user space processes ... (elapsed 0.001 seconds) done. Apr 21 18:25:39 faire kernel: [ 5637.063221] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Apr 21 18:25:39 faire kernel: [ 5637.064492] PM: Entering mem sleep Apr 21 18:25:39 faire kernel: [ 5637.064569] Suspending console(s) (use no_console_suspend to debug) Apr 21 18:25:39 faire kernel: [ 5637.205560] sd 1:0:0:0: [sdb] Synchronizing SCSI cache Apr 21 18:25:39 faire kernel: [ 5637.205608] sd 1:0:0:0: [sdb] Stopping disk Apr 21 18:25:39 faire kernel: [ 5637.205617] sd 0:0:0:0: [sda] Synchronizing SCSI cache Apr 21 18:25:39 faire kernel: [ 5637.207564] sd 0:0:0:0: [sda] Stopping disk Apr 21 18:25:39 faire kernel: [ 5637.431859] [ cut here ] Apr 21 18:25:39 faire kernel: [ 5637.431894] WARNING: CPU: 1 PID: 11523 at /build/buildd/linux-3.13.0/drivers/gpu/drm/i915/intel_uncore.c:125 gen6_gt_check_fifodbg.isra.9+0x38/0x50 [i915]() Apr 21 18:25:39 faire kernel: [ 5637.431895] MMIO read or write has been dropped Apr 21 18:25:39 faire kernel: [ 5637.431918] Modules linked in: snd_seq_dummy snd_hrtimer ccm xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 cuse nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables deflate ctr twofish_generic twofish_avx_x86_64 twofish_x86_64_3way twofish_x86_64 twofish_common camellia_generic camellia_aesni_avx2 camellia_aesni_avx_x86_64 camellia_x86_64 serpent_avx2 serpent_avx_x86_64 serpent_sse2_x86_64 xts serpent_generic blowfish_generic blowfish_x86_64 blowfish_common joydev cast5_avx_x86_64 cast5_generic cast_common des_generic cmac xcbc rmd160 crypto_null af_key xfrm_algo arc4 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp uvcvideo videobuf2_vmalloc kvm_intel videobuf2_memops videobuf2_core videodev iwlmvm kvm mac80211 thinkpad_acpi nvram snd_seq_midi psmouse snd_seq_midi_event snd_rawmidi serio_raw snd_hda_codec_hdmi snd_hda_codec_realtek iwlwifi snd_hda_intel snd_hda_codec snd_seq snd_hwdep lpc_ich rtsx_pci_ms memstick cfg80211 btusb bluetooth mei_me mei snd_pcm snd_seq_device snd_page_alloc snd_timer snd parport_pc soundcore mac_hid ppdev intel_smartconnect lp parport binfmt_misc nls_iso8859_1 dm_crypt hid_generic usbhid hid mmc_block rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd e1000e ahci libahci ptp rtsx_pci i915 pps_core wmi i2c_algo_bit video drm_kms_helper drm Apr 21 18:25:39 faire kernel: [ 5637.431943] CPU: 1 PID: 11523 Comm: kworker/u16:8 Not tainted 3.13.0-24-generic #46-Ubuntu Apr 21 18:25:39 faire kernel: [ 5637.431944] Hardware name: LENOVO 20AQCTO1WW/20AQCTO1WW, BIOS GJET71WW (2.21 ) 02/10/2014 Apr 21 18:25:39 faire kernel: [ 5637.431956] Workqueue: i915 gen6_force_wake_work [i915] Apr 21 18:25:39 faire kernel: [ 5637.431958] 0009 8802cccf9d38 81715a64 8802cccf9d80 Apr 21 18:25:39 faire kernel: [ 5637.431959] 8802cccf9d70 810676bd 88003fba0020 88003fba0028 Apr 21 18:25:39 faire kernel: [ 5637.431960] 0246 0200 8802cccf9dd0 Apr 21 18:25:39 faire kernel: [ 5637.431961] Call Trace: Apr 21 18:25:39 faire kernel: [ 5637.431964] [81715a64] dump_stack+0x45/0x56 Apr 21 18:25:39 faire kernel: [ 5637.431966] [810676bd] warn_slowpath_common+0x7d/0xa0 Apr 21 18:25:39 faire kernel: [ 5637.431968] [8106772c] warn_slowpath_fmt+0x4c/0x50 Apr 21 18:25:39 faire kernel: [ 5637.431979] [a00fade8] gen6_gt_check_fifodbg.isra.9+0x38/0x50 [i915] Apr 21 18:25:39 faire kernel: [ 5637.431988] [a00fae8b] __gen6_gt_force_wake_mt_put+0x2b/0x30 [i915] Apr 21 18:25:39 faire kernel: [ 5637.431996] [a00fabb7] gen6_force_wake_work+0x37/0x50 [i915] Apr 21 18:25:39 faire kernel: [ 5637.431998] [810838a2] process_one_work+0x182/0x450 Apr 21 18:25:39 faire kernel: [ 5637.432000] [81084641] worker_thread+0x121/0x410 Apr 21 18:25:39 faire kernel: [ 5637.432002] [81084520] ? rescuer_thread+0x3e0/0x3e0 Apr 21 18:25:39 faire kernel: [ 5637.432003] [8108b312] kthread+0xd2/0xf0 Apr 21 18:25:39 faire kernel: [ 5637.432005] [8108b240] ? kthread_create_on_node+0x1d0/0x1d0 Apr 21 18:25:39 faire kernel: [ 5637.432006] [8172637c] ret_from_fork+0x7c/0xb0
[Kernel-packages] [Bug 1319141] [NEW] kernel oops before suspend
Public bug reported: May 13 18:22:10 faire kernel: [35947.754796] PM: Syncing filesystems ... done. May 13 18:22:10 faire kernel: [35947.782070] PM: Preparing system for mem sleep May 13 19:17:45 faire kernel: [35947.782396] mmc0: card b368 removed May 13 19:17:45 faire kernel: [35947.784816] Freezing user space processes ... (elapsed 0.002 seconds) done. May 13 19:17:45 faire kernel: [35947.787286] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. May 13 19:17:45 faire kernel: [35947.788760] PM: Entering mem sleep May 13 19:17:45 faire kernel: [35947.788841] Suspending console(s) (use no_console_suspend to debug) May 13 19:17:45 faire kernel: [35947.935975] sd 1:0:0:0: [sdb] Synchronizing SCSI cache May 13 19:17:45 faire kernel: [35947.936044] sd 1:0:0:0: [sdb] Stopping disk May 13 19:17:45 faire kernel: [35947.936099] sd 0:0:0:0: [sda] Synchronizing SCSI cache May 13 19:17:45 faire kernel: [35947.938056] sd 0:0:0:0: [sda] Stopping disk May 13 19:17:45 faire kernel: [35948.162233] [ cut here ] May 13 19:17:45 faire kernel: [35948.162268] WARNING: CPU: 0 PID: 32245 at /build/buildd/linux-3.13.0/drivers/gpu/drm/i915/intel_uncore.c:125 gen6_gt_check_fifodbg.isra.9+0x38/0x50 [i915]() May 13 19:17:45 faire kernel: [35948.162268] MMIO read or write has been dropped May 13 19:17:45 faire kernel: [35948.162292] Modules linked in: ums_cypress usb_storage veth ccm hid_generic usbhid hid xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables deflate ctr twofish_generic twofish_avx_x86_64 twofish_x86_64_3way twofish_x86_64 twofish_common camellia_generic camellia_aesni_avx2 camellia_aesni_avx_x86_64 camellia_x86_64 serpent_avx2 serpent_avx_x86_64 serpent_sse2_x86_64 xts serpent_generic blowfish_generic blowfish_x86_64 blowfish_common cast5_avx_x86_64 cast5_generic cast_common des_generic cmac xcbc rmd160 crypto_null af_key xfrm_algo arc4 uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp iwlmvm kvm_intel mac80211 kvm joydev snd_hda_codec_hdmi serio_raw snd_hda_codec_realtek rtsx_pci_ms memstick iwlwifi btusb bluetooth thinkpad_acpi snd_hda_intel nvram snd_hda_codec cfg80211 snd_seq_midi snd_seq_midi_event snd_hwdep snd_pcm snd_rawmidi lpc_ich snd_seq mei_me snd_page_alloc snd_seq_device mei snd_timer snd soundcore binfmt_misc mac_hid intel_smartconnect cuse parport_pc ppdev lp parport nls_iso8859_1 dm_crypt mmc_block rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd i915 psmouse ahci e1000e libahci rtsx_pci i2c_algo_bit ptp drm_kms_helper pps_core drm wmi video May 13 19:17:45 faire kernel: [35948.162318] CPU: 0 PID: 32245 Comm: kworker/u16:0 Not tainted 3.13.0-24-generic #47-Ubuntu May 13 19:17:45 faire kernel: [35948.162319] Hardware name: LENOVO 20AQCTO1WW/20AQCTO1WW, BIOS GJET71WW (2.21 ) 02/10/2014 May 13 19:17:45 faire kernel: [35948.162330] Workqueue: i915 gen6_force_wake_work [i915] May 13 19:17:45 faire kernel: [35948.162332] 0009 880236459d38 81715ac4 880236459d80 May 13 19:17:45 faire kernel: [35948.162333] 880236459d70 810676bd 880306fb0020 880306fb0028 May 13 19:17:45 faire kernel: [35948.162335] 0246 0200 880236459dd0 May 13 19:17:45 faire kernel: [35948.162335] Call Trace: May 13 19:17:45 faire kernel: [35948.162339] [81715ac4] dump_stack+0x45/0x56 May 13 19:17:45 faire kernel: [35948.162341] [810676bd] warn_slowpath_common+0x7d/0xa0 May 13 19:17:45 faire kernel: [35948.162342] [8106772c] warn_slowpath_fmt+0x4c/0x50 May 13 19:17:45 faire kernel: [35948.162353] [a018ede8] gen6_gt_check_fifodbg.isra.9+0x38/0x50 [i915] May 13 19:17:45 faire kernel: [35948.162363] [a018ee8b] __gen6_gt_force_wake_mt_put+0x2b/0x30 [i915] May 13 19:17:45 faire kernel: [35948.162371] [a018ebb7] gen6_force_wake_work+0x37/0x50 [i915] May 13 19:17:45 faire kernel: [35948.162374] [810838a2] process_one_work+0x182/0x450 May 13 19:17:45 faire kernel: [35948.162376] [81084641] worker_thread+0x121/0x410 May 13 19:17:45 faire kernel: [35948.162377] [81084520] ? rescuer_thread+0x3e0/0x3e0 May 13 19:17:45 faire kernel: [35948.162379] [8108b312] kthread+0xd2/0xf0 May 13 19:17:45 faire kernel: [35948.162381] [8108b240] ? kthread_create_on_node+0x1d0/0x1d0 May 13 19:17:45 faire kernel: [35948.162383] [817263fc] ret_from_fork+0x7c/0xb0 May 13 19:17:45 faire kernel: [35948.162384] [8108b240] ? kthread_create_on_node+0x1d0/0x1d0 May 13 19:17:45 faire kernel: [35948.162384] ---[ end trace 07caaff3206587f4 ]--- May 13 19:17:45 faire kernel: [35948.174438] PM:
[Kernel-packages] [Bug 1308082] [NEW] apparmor oops caused by starting an unprivileged lxc container
Public bug reported: Oops caused when trying to start an lxc unprivileged container. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 2580 F pulseaudio /dev/snd/controlC0: james 2580 F pulseaudio CurrentDesktop: Unity Date: Tue Apr 15 15:00:18 2014 HibernationDevice: RESUME=UUID=db600bbe-faca-41f4-9338-c3e8e227599a InstallationDate: Installed on 2014-04-11 (3 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409) MachineType: LENOVO 20AQCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/10/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET71WW (2.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98405 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AQCTO1WW dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1308082 Title: apparmor oops caused by starting an unprivileged lxc container Status in “linux” package in Ubuntu: New Bug description: Oops caused when trying to start an lxc unprivileged container. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 2580 F pulseaudio /dev/snd/controlC0: james 2580 F pulseaudio CurrentDesktop: Unity Date: Tue Apr 15 15:00:18 2014 HibernationDevice: RESUME=UUID=db600bbe-faca-41f4-9338-c3e8e227599a InstallationDate: Installed on 2014-04-11 (3 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409) MachineType: LENOVO 20AQCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/10/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET71WW (2.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98405 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AQCTO1WW dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1308082/+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 1300144] Re: Requested shutdown results in Reboot
** Package changed: upstart (Ubuntu) = linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1300144 Title: Requested shutdown results in Reboot Status in “linux” package in Ubuntu: Incomplete Bug description: On Lenovo X230 Tablet, and the latest 14.04, when I pick Shutdown from my desktop menu, the machine shuts down and then almost immediately boots up again, by itself. Instead, it should shutdown and stay down. Because this can cause the hardware to overheat when I turn my machine off and put it in its bag, I suggest this is high priority for the LTS. (I've no idea whether upstart is the right package. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: upstart 1.12.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 31 06:31:13 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-03-11 (19 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140218) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=63d5fa0d-9ba0-4641-bdfa-c45adfb938b5 ro quiet splash vt.handoff=7 SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System UpstartRunningSessionVersion: init (upstart 1.12.1) UpstartRunningSystemVersion: init (upstart 1.12.1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300144/+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 1296659] Re: occasional kernel oops seen in trusty virtualbox VM
** Attachment added: virtualbox-kernel-oops.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1296659/+attachment/4040675/+files/virtualbox-kernel-oops.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/1296659 Title: occasional kernel oops seen in trusty virtualbox VM Status in “linux” package in Ubuntu: New Bug description: Occasionally seen in Virtualbox VM. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-19-generic 3.13.0-19.39 ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6 Uname: Linux 3.13.0-19-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Mon Mar 24 10:58:45 2014 HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312 InstallationDate: Installed on 2010-10-21 (1250 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) MachineType: LENOVO 2516CTO ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-19-generic root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro quiet splash intel_pstate=enable RelatedPackageVersions: linux-restricted-modules-3.13.0-19-generic N/A linux-backports-modules-3.13.0-19-generic N/A linux-firmware 1.126 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-11-01 (142 days ago) dmi.bios.date: 08/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET72WW (1.32 ) dmi.board.name: 2516CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2516CTO dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1296659/+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 1296659] Re: occasional kernel oops seen in trusty virtualbox VM
Simply booting a VM without 'quiet' and 'splash' shows the oops - I've only noticed it a couple of times. Just tried 10 boots and didn't hit it again though. (Note that I cannot compare virtualbox's behaviour with kvm due to bug 1268906). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1296659 Title: occasional kernel oops seen in trusty virtualbox VM Status in “linux” package in Ubuntu: Confirmed Bug description: Occasionally seen in Virtualbox VM. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-19-generic 3.13.0-19.39 ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6 Uname: Linux 3.13.0-19-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Mon Mar 24 10:58:45 2014 HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312 InstallationDate: Installed on 2010-10-21 (1250 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) MachineType: LENOVO 2516CTO ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-19-generic root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro quiet splash intel_pstate=enable RelatedPackageVersions: linux-restricted-modules-3.13.0-19-generic N/A linux-backports-modules-3.13.0-19-generic N/A linux-firmware 1.126 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-11-01 (142 days ago) dmi.bios.date: 08/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET72WW (1.32 ) dmi.board.name: 2516CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2516CTO dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1296659/+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 1295112] [NEW] Unable to install 64-bit kernel on 64-bit-capable system installed with 32-bit userland+kernel
Public bug reported: $ arch i686 $ dpkg -l linux-generic Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---== ii linux-generic 3.13.0.18.22 i386 Complete Generic Linux kernel and headers $ sudo dpkg --add-architecture amd64 $ sudo apt-get update $ sudo apt-get install linux-generic:amd64 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. linux-generic:amd64 : Depends: linux-headers-generic:amd64 (= 3.13.0.18.22) but it is not going to be installed E: Unable to correct problems, you have held broken packages. $ sudo apt-get install linux-generic:amd64 linux-headers-generic:amd64 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. linux-headers-generic:amd64 : Depends: linux-headers-3.13.0-18-generic:amd64 but it is not going to be installed E: Unable to correct problems, you have held broken packages. $ sudo apt-get install linux-generic:amd64 linux-headers-generic:amd64 linux-headers-3.13.0-18-generic:amd64 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. linux-headers-3.13.0-18-generic:amd64 : Depends: linux-headers-3.13.0-18:amd64 but it is not installable E: Unable to correct problems, you have held broken packages. $ sudo apt-get install linux-generic:amd64 linux-headers-generic:amd64 linux-headers-3.13.0-18-generic:amd64 linux-headers-3.13.0-18:amd64 Reading package lists... Done Building dependency tree Reading state information... Done Package linux-headers-3.13.0-18:amd64 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'linux-headers-3.13.0-18:amd64' has no installation candidate $ cjwatson identified the issue: 12:52:11 cjwatson the bug is that linux-headers-3.13.0-18 isn't Multi- Arch: foreign fwiw ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-18-generic 3.13.0-18.38 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 3834 F pulseaudio /dev/snd/controlC0: james 3834 F pulseaudio /dev/snd/pcmC0D0p: james 3834 F...m pulseaudio CurrentDesktop: Unity Date: Thu Mar 20 12:52:29 2014 HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312 InstallationDate: Installed on 2010-10-21 (1246 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) MachineType: LENOVO 2516CTO ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro quiet splash intel_pstate=enable RelatedPackageVersions: linux-restricted-modules-3.13.0-18-generic N/A linux-backports-modules-3.13.0-18-generic N/A linux-firmware 1.126 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-11-01 (138 days ago) dmi.bios.date: 08/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET72WW (1.32 ) dmi.board.name: 2516CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias:
[Kernel-packages] [Bug 1295112] Re: Unable to install 64-bit kernel on 64-bit-capable system installed with 32-bit userland+kernel
$ sudo apt-get install linux-generic:amd64 linux-headers-generic:amd64 linux-headers-3.13.0-18-generic:amd64 linux-headers-3.13.0-18 Reading package lists... Done Building dependency tree Reading state information... Done linux-headers-3.13.0-18 is already the newest version. Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. linux-headers-3.13.0-18-generic:amd64 : Depends: linux-headers-3.13.0-18:amd64 but it is not installable E: Unable to correct problems, you have held broken packages. $ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1295112 Title: Unable to install 64-bit kernel on 64-bit-capable system installed with 32-bit userland+kernel Status in “linux” package in Ubuntu: New Bug description: $ arch i686 $ dpkg -l linux-generic Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---== ii linux-generic 3.13.0.18.22 i386 Complete Generic Linux kernel and headers $ sudo dpkg --add-architecture amd64 $ sudo apt-get update $ sudo apt-get install linux-generic:amd64 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. linux-generic:amd64 : Depends: linux-headers-generic:amd64 (= 3.13.0.18.22) but it is not going to be installed E: Unable to correct problems, you have held broken packages. $ sudo apt-get install linux-generic:amd64 linux-headers-generic:amd64 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. linux-headers-generic:amd64 : Depends: linux-headers-3.13.0-18-generic:amd64 but it is not going to be installed E: Unable to correct problems, you have held broken packages. $ sudo apt-get install linux-generic:amd64 linux-headers-generic:amd64 linux-headers-3.13.0-18-generic:amd64 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. linux-headers-3.13.0-18-generic:amd64 : Depends: linux-headers-3.13.0-18:amd64 but it is not installable E: Unable to correct problems, you have held broken packages. $ sudo apt-get install linux-generic:amd64 linux-headers-generic:amd64 linux-headers-3.13.0-18-generic:amd64 linux-headers-3.13.0-18:amd64 Reading package lists... Done Building dependency tree Reading state information... Done Package linux-headers-3.13.0-18:amd64 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'linux-headers-3.13.0-18:amd64' has no installation candidate $ cjwatson identified the issue: 12:52:11 cjwatson the bug is that linux-headers-3.13.0-18 isn't Multi-Arch: foreign fwiw ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-18-generic 3.13.0-18.38 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1:
[Kernel-packages] [Bug 1295112] Re: Unable to install 64-bit kernel on 64-bit-capable system installed with 32-bit userland+kernel
Yes: $ sudo apt-get install linux-generic:amd64 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. linux-generic:amd64 : Depends: linux-headers-generic:amd64 (= 3.13.0.18.22) but it is not going to be installed E: Unable to correct problems, you have held broken packages. $ sudo apt-get install linux-image:amd64 Reading package lists... Done Building dependency tree Reading state information... Done Package linux-image:amd64 is a virtual package provided by: linux-image-3.13.0-18-lowlatency:amd64 3.13.0-18.38 linux-image-3.13.0-18-generic:amd64 3.13.0-18.38 You should explicitly select one to install. E: Package 'linux-image:amd64' has no installation candidate $ sudo apt-get install linux-image-3.13.0-18-generic:amd64 Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: fdutils:amd64 linux-doc-3.13.0:amd64 linux-source-3.13.0:amd64 linux-tools:amd64 linux-headers-3.13.0-18-generic:amd64 The following packages will be REMOVED linux-generic linux-image linux-image-3.13.0-18-generic linux-image-extra-3.13.0-18-generic linux-image-generic linux-image-generic-pae linux-image-server The following NEW packages will be installed linux-image-3.13.0-18-generic:amd64 0 to upgrade, 1 to newly install, 7 to remove and 11 not to upgrade. Need to get 14,9 MB of archives. After this operation, 104 MB disk space will be freed. That last operation looks wrong as apt seems to want to remove my 32-bit (??) kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1295112 Title: Unable to install 64-bit kernel on 64-bit-capable system installed with 32-bit userland+kernel Status in “linux” package in Ubuntu: Confirmed Bug description: $ arch i686 $ dpkg -l linux-generic Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---== ii linux-generic 3.13.0.18.22 i386 Complete Generic Linux kernel and headers $ sudo dpkg --add-architecture amd64 $ sudo apt-get update $ sudo apt-get install linux-generic:amd64 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. linux-generic:amd64 : Depends: linux-headers-generic:amd64 (= 3.13.0.18.22) but it is not going to be installed E: Unable to correct problems, you have held broken packages. $ sudo apt-get install linux-generic:amd64 linux-headers-generic:amd64 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. linux-headers-generic:amd64 : Depends: linux-headers-3.13.0-18-generic:amd64 but it is not going to be installed E: Unable to correct problems, you have held broken packages. $ sudo apt-get install linux-generic:amd64 linux-headers-generic:amd64 linux-headers-3.13.0-18-generic:amd64 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. linux-headers-3.13.0-18-generic:amd64 : Depends: linux-headers-3.13.0-18:amd64 but it
[Kernel-packages] [Bug 1268906] Re: cpu soft lockup running kvm
Still a problem on 3.13.0-17-generic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1268906 Title: cpu soft lockup running kvm Status in “linux” package in Ubuntu: Confirmed Status in “qemu-kvm” package in Ubuntu: Confirmed Bug description: Ran twice - first time running kvm killed my system. The second time, I just got lots of kernel oops messages in dmesg. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-2-generic 3.13.0-2.17 ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7 Uname: Linux 3.13.0-2-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.1-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 3250 F pulseaudio /dev/snd/controlC0: james 3250 F pulseaudio /dev/snd/pcmC0D0p: james 3250 F...m pulseaudio CurrentDesktop: Unity Date: Tue Jan 14 10:29:20 2014 HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312 InstallationDate: Installed on 2010-10-21 (1181 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) MachineType: LENOVO 2516CTO ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-2-generic root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-2-generic N/A linux-backports-modules-3.13.0-2-generic N/A linux-firmware1.121 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-11-01 (73 days ago) dmi.bios.date: 08/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET72WW (1.32 ) dmi.board.name: 2516CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2516CTO dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+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 955287] Re: Ubuntu should handle hot CPUs by taking preemptive action and warning users
Hi Colin - thanks, yes running thermald has improved the situation immensely! I do still very occasionally see overheats, although they are extremely rare now and I suspect may be more related to my fans needing a clean :-) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/955287 Title: Ubuntu should handle hot CPUs by taking preemptive action and warning users Status in “linux” package in Ubuntu: Fix Released Bug description: If the kernel detects your CPU(s) is/are too hot currently (see bug 751689), the kernel calls /sbin/poweroff. This will provide a graceful system shutdown. If /sbin/poweroff fails, the kernel just forcibly shuts the system down. However, both strategies are last resorts and are called when the system temperature has reached a critical level. However, the kernel seems to emit an ACPI event when it detects the CPU(s) are merely hot. I suggest we consider adding an acpi hook to attempt to avoid a critical scenario. Currently, the user experience when critical gets hit is not good - the system just shuts down with no warning whatsoever. This is alarming in the extreme to users. Ideas: - proactively attempt to kill off power hogging processes (use powertop?) - ramp fans to maximum and present the user with a warning window explaining what is happening. - present the user with a window of high-power processes and ask *them* to select the processes they'd like to kill off in an effort to avoid a system shutdown. Problems: - it is unclear (to me atleast) how close (in terms of degrees centigrade) hot and critical are (is it different for all CPUs ?) As such, it is unclear how long (time) it might take for a system that is hot to go critical and just shutdown. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: acpi-support 0.140 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9 Uname: Linux 3.2.0-18-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 1.94.1-0ubuntu2 Architecture: i386 Date: Wed Mar 14 17:22:09 2012 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=fr_CA.UTF8 SHELL=/bin/bash SourcePackage: acpi-support UpgradeStatus: Upgraded to precise on 2012-01-12 (62 days ago) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.94.1-0ubuntu2 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 3788 F pulseaudio /dev/snd/controlC0: james 3788 F pulseaudio james 10267 F alsamixer Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf242 irq 45' Mixer name : 'Conexant CX20585' Components : 'HDA:14f15069,17aa214c,00100302 HDA:14f12c06,17aa2122,0010' Controls : 9 Simple ctrls : 6 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xcdefc000 irq 16' Mixer name : 'Nvidia GPU 0b HDMI/DP' Components : 'HDA:10de000b,10de0101,00100100' Controls : 24 Simple ctrls : 4 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 6IHT37WW-1.12' Mixer name : 'ThinkPad EC 6IHT37WW-1.12' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) MachineType: LENOVO 2516CTO NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=fr_CA.UTF8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic-pae root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro acpi_sleep=nonvs console=ttyUSB0,115200n8r console=tty quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9 RelatedPackageVersions: linux-restricted-modules-3.2.0-18-generic-pae N/A linux-backports-modules-3.2.0-18-generic-pae N/A linux-firmware1.71 StagingDrivers: mei Tags: precise staging Uname: Linux 3.2.0-18-generic-pae i686 UpgradeStatus: Upgraded to precise on 2012-01-12 (62 days ago) UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare sbuild dmi.bios.date: 08/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET72WW (1.32 )
[Kernel-packages] [Bug 1263140] Re: reboot does not terminate at computer shutdown
Please can those affected attach the requested logs in comment #3 ? ** Changed in: upstart (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1263140 Title: reboot does not terminate at computer shutdown Status in “linux” package in Ubuntu: Incomplete Status in “upstart” package in Ubuntu: Incomplete Bug description: Ubuntu 13.10 Shutdown and rebbot whether via terminal or GUI buttons hangs and does not shut off power on my PC. I have to hold down the power button to do full power off, ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: upstart 1.10-0ubuntu7 Uname: Linux 3.12.0-031200-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Thu Dec 19 13:45:25 2013 ExecutablePath: /sbin/reboot InstallationDate: Installed on 2013-10-19 (61 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True OmitPids: 1130 941 755 11955 732 713 699 12012 819 719 12041 755 11955 732 713 699 12012 819 719 ProcCmdline: /sbin/poweroff ProcEnviron: ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.12.0-031200-generic root=UUID=99ee33d3-3574-42e4-9b82-5f0f954cfc69 ro quiet splash acpi=force vt.handoff=7 SourcePackage: upstart Title: reboot does not terminate at computer shutdown UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System UpstartRunningSystemVersion: init (upstart 1.10) modified.conffile..etc.default.whoopsie: [modified] mtime.conffile..etc.default.whoopsie: 2013-10-22T11:31:34.550082 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1263140/+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 1268906] Re: cpu soft lockup running kvm
I think the switch to 3.13 may have borked kvm for me. I'll try to confirm that tomorrow... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1268906 Title: cpu soft lockup running kvm Status in “linux” package in Ubuntu: Confirmed Status in “qemu-kvm” package in Ubuntu: Confirmed Bug description: Ran twice - first time running kvm killed my system. The second time, I just got lots of kernel oops messages in dmesg. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-2-generic 3.13.0-2.17 ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7 Uname: Linux 3.13.0-2-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.1-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 3250 F pulseaudio /dev/snd/controlC0: james 3250 F pulseaudio /dev/snd/pcmC0D0p: james 3250 F...m pulseaudio CurrentDesktop: Unity Date: Tue Jan 14 10:29:20 2014 HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312 InstallationDate: Installed on 2010-10-21 (1181 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) MachineType: LENOVO 2516CTO ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-2-generic root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-2-generic N/A linux-backports-modules-3.13.0-2-generic N/A linux-firmware1.121 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-11-01 (73 days ago) dmi.bios.date: 08/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET72WW (1.32 ) dmi.board.name: 2516CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2516CTO dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+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 1274143] Re: kernel backtrace triggered by rt2800usb driver
Hi Joseph - see dmesg.txt.gz for the stack traces. I cannot recreate this issue on demand I'm afraid and have not see it since raising this bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1274143 Title: kernel backtrace triggered by rt2800usb driver Status in “linux” package in Ubuntu: Incomplete Bug description: Issue occurred when using a WiPi USB adapter (wlan1). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-5-generic 3.13.0-5.20 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 3768 F pulseaudio /dev/snd/controlC0: james 3768 F pulseaudio /dev/snd/pcmC0D0p: james 3768 F...m pulseaudio CurrentDesktop: Unity Date: Wed Jan 29 14:56:07 2014 HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312 InstallationDate: Installed on 2010-10-21 (1196 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) MachineType: LENOVO 2516CTO ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro quiet splash intel_pstate=enable RelatedPackageVersions: linux-restricted-modules-3.13.0-5-generic N/A linux-backports-modules-3.13.0-5-generic N/A linux-firmware1.122 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-11-01 (88 days ago) dmi.bios.date: 08/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET72WW (1.32 ) dmi.board.name: 2516CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2516CTO dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1274143/+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 1274143] Re: kernel backtrace triggered by rt2800usb driver
** Attachment added: sudo lshw -c network https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1274143/+attachment/3961769/+files/lsusb_-c_network.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/1274143 Title: kernel backtrace triggered by rt2800usb driver Status in “linux” package in Ubuntu: New Bug description: Issue occurred when using a WiPi USB adapter (wlan1). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-5-generic 3.13.0-5.20 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 3768 F pulseaudio /dev/snd/controlC0: james 3768 F pulseaudio /dev/snd/pcmC0D0p: james 3768 F...m pulseaudio CurrentDesktop: Unity Date: Wed Jan 29 14:56:07 2014 HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312 InstallationDate: Installed on 2010-10-21 (1196 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) MachineType: LENOVO 2516CTO ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro quiet splash intel_pstate=enable RelatedPackageVersions: linux-restricted-modules-3.13.0-5-generic N/A linux-backports-modules-3.13.0-5-generic N/A linux-firmware1.122 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-11-01 (88 days ago) dmi.bios.date: 08/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET72WW (1.32 ) dmi.board.name: 2516CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2516CTO dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1274143/+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 1274143] [NEW] kernel backtrace triggered by rt2800usb driver
Public bug reported: Issue occurred when using a WiPi USB adapter (wlan1). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-5-generic 3.13.0-5.20 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 3768 F pulseaudio /dev/snd/controlC0: james 3768 F pulseaudio /dev/snd/pcmC0D0p: james 3768 F...m pulseaudio CurrentDesktop: Unity Date: Wed Jan 29 14:56:07 2014 HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312 InstallationDate: Installed on 2010-10-21 (1196 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) MachineType: LENOVO 2516CTO ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro quiet splash intel_pstate=enable RelatedPackageVersions: linux-restricted-modules-3.13.0-5-generic N/A linux-backports-modules-3.13.0-5-generic N/A linux-firmware1.122 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-11-01 (88 days ago) dmi.bios.date: 08/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET72WW (1.32 ) dmi.board.name: 2516CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2516CTO dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty ** Attachment added: dmesg.txt.gz https://bugs.launchpad.net/bugs/1274143/+attachment/3961751/+files/dmesg.txt.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1274143 Title: kernel backtrace triggered by rt2800usb driver Status in “linux” package in Ubuntu: New Bug description: Issue occurred when using a WiPi USB adapter (wlan1). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-5-generic 3.13.0-5.20 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 3768 F pulseaudio /dev/snd/controlC0: james 3768 F pulseaudio /dev/snd/pcmC0D0p: james 3768 F...m pulseaudio CurrentDesktop: Unity Date: Wed Jan 29 14:56:07 2014 HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312 InstallationDate: Installed on 2010-10-21 (1196 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) MachineType: LENOVO 2516CTO ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro quiet splash intel_pstate=enable RelatedPackageVersions: linux-restricted-modules-3.13.0-5-generic N/A linux-backports-modules-3.13.0-5-generic N/A linux-firmware1.122 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-11-01 (88 days ago) dmi.bios.date: 08/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET72WW (1.32 ) dmi.board.name: 2516CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2516CTO dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1274143/+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 1268906] Re: cpu soft lockup running kvm
Serge has just identified that the trigger for this bug is running kvm with '-net user': without this option, no issues. ** Changed in: qemu-kvm (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1268906 Title: cpu soft lockup running kvm Status in “linux” package in Ubuntu: Confirmed Status in “qemu-kvm” package in Ubuntu: Confirmed Bug description: Ran twice - first time running kvm killed my system. The second time, I just got lots of kernel oops messages in dmesg. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-2-generic 3.13.0-2.17 ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7 Uname: Linux 3.13.0-2-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.1-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 3250 F pulseaudio /dev/snd/controlC0: james 3250 F pulseaudio /dev/snd/pcmC0D0p: james 3250 F...m pulseaudio CurrentDesktop: Unity Date: Tue Jan 14 10:29:20 2014 HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312 InstallationDate: Installed on 2010-10-21 (1181 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) MachineType: LENOVO 2516CTO ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-2-generic root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-2-generic N/A linux-backports-modules-3.13.0-2-generic N/A linux-firmware1.121 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-11-01 (73 days ago) dmi.bios.date: 08/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET72WW (1.32 ) dmi.board.name: 2516CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2516CTO dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+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 1268906] Re: cpu soft lockup running kvm
Latest series of oopses running on a fully updated trusty system. ** Attachment added: dmesg.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+attachment/3958887/+files/dmesg.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/1268906 Title: cpu soft lockup running kvm Status in “linux” package in Ubuntu: Confirmed Status in “qemu-kvm” package in Ubuntu: Confirmed Bug description: Ran twice - first time running kvm killed my system. The second time, I just got lots of kernel oops messages in dmesg. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-2-generic 3.13.0-2.17 ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7 Uname: Linux 3.13.0-2-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.1-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 3250 F pulseaudio /dev/snd/controlC0: james 3250 F pulseaudio /dev/snd/pcmC0D0p: james 3250 F...m pulseaudio CurrentDesktop: Unity Date: Tue Jan 14 10:29:20 2014 HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312 InstallationDate: Installed on 2010-10-21 (1181 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) MachineType: LENOVO 2516CTO ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-2-generic root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-2-generic N/A linux-backports-modules-3.13.0-2-generic N/A linux-firmware1.121 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-11-01 (73 days ago) dmi.bios.date: 08/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET72WW (1.32 ) dmi.board.name: 2516CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2516CTO dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+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 1268906] Re: cpu soft lockup running kvm
Same problem running with -vnc :7 ** Attachment added: dmesg.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+attachment/395/+files/dmesg.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/1268906 Title: cpu soft lockup running kvm Status in “linux” package in Ubuntu: Confirmed Status in “qemu-kvm” package in Ubuntu: Confirmed Bug description: Ran twice - first time running kvm killed my system. The second time, I just got lots of kernel oops messages in dmesg. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-2-generic 3.13.0-2.17 ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7 Uname: Linux 3.13.0-2-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.1-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 3250 F pulseaudio /dev/snd/controlC0: james 3250 F pulseaudio /dev/snd/pcmC0D0p: james 3250 F...m pulseaudio CurrentDesktop: Unity Date: Tue Jan 14 10:29:20 2014 HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312 InstallationDate: Installed on 2010-10-21 (1181 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) MachineType: LENOVO 2516CTO ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-2-generic root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-2-generic N/A linux-backports-modules-3.13.0-2-generic N/A linux-firmware1.121 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-11-01 (73 days ago) dmi.bios.date: 08/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET72WW (1.32 ) dmi.board.name: 2516CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2516CTO dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+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 1268906] Re: cpu soft lockup running kvm
To be clear, my host system is a 64-bit capable first-gen i7, but is actually running fully 32-bit. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1268906 Title: cpu soft lockup running kvm Status in “linux” package in Ubuntu: Confirmed Status in “qemu-kvm” package in Ubuntu: Confirmed Bug description: Ran twice - first time running kvm killed my system. The second time, I just got lots of kernel oops messages in dmesg. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-2-generic 3.13.0-2.17 ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7 Uname: Linux 3.13.0-2-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.1-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 3250 F pulseaudio /dev/snd/controlC0: james 3250 F pulseaudio /dev/snd/pcmC0D0p: james 3250 F...m pulseaudio CurrentDesktop: Unity Date: Tue Jan 14 10:29:20 2014 HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312 InstallationDate: Installed on 2010-10-21 (1181 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) MachineType: LENOVO 2516CTO ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-2-generic root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-2-generic N/A linux-backports-modules-3.13.0-2-generic N/A linux-firmware1.121 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-11-01 (73 days ago) dmi.bios.date: 08/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET72WW (1.32 ) dmi.board.name: 2516CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2516CTO dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+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 1268906] Re: cpu soft lockup running kvm
Latest trusty desktop image (dated 24 Jan) results in the oops when running with kvm as: $ kvm --enable-kvm -cdrom ubuntu_trusty-desktop-i386.iso -boot d -m 1024 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1268906 Title: cpu soft lockup running kvm Status in “linux” package in Ubuntu: Confirmed Status in “qemu-kvm” package in Ubuntu: Confirmed Bug description: Ran twice - first time running kvm killed my system. The second time, I just got lots of kernel oops messages in dmesg. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-2-generic 3.13.0-2.17 ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7 Uname: Linux 3.13.0-2-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.1-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 3250 F pulseaudio /dev/snd/controlC0: james 3250 F pulseaudio /dev/snd/pcmC0D0p: james 3250 F...m pulseaudio CurrentDesktop: Unity Date: Tue Jan 14 10:29:20 2014 HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312 InstallationDate: Installed on 2010-10-21 (1181 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) MachineType: LENOVO 2516CTO ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-2-generic root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-2-generic N/A linux-backports-modules-3.13.0-2-generic N/A linux-firmware1.121 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-11-01 (73 days ago) dmi.bios.date: 08/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET72WW (1.32 ) dmi.board.name: 2516CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2516CTO dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+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 1256949] Re: Dell Latitude E5420 doesn't boot if killswitch is turned to radio off
Sounds like the original driver had caused the kernel to become totally unresponsive. Glad the problem has been resolved for you. Please could you attach the output of sudo lshw -c network to this bug so we can see the details of your broadcom wireless card? 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/1256949 Title: Dell Latitude E5420 doesn't boot if killswitch is turned to radio off Status in “linux” package in Ubuntu: Incomplete Status in “upstart” package in Ubuntu: Incomplete Bug description: Ubuntu 12.04.3, Dell E5420. Boots fine with killswitch to radio on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1256949/+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 1269717] Re: shutdown now does not shutdown
This sounds like a kernel issue relating to your hardware. ** Package changed: upstart (Ubuntu) = linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1269717 Title: shutdown now does not shutdown Status in “linux” package in Ubuntu: Incomplete Bug description: when typing in sudo shutdown now in a terminal, instead of shutting down, the computer shows a root prompt and never shuts down. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269717/+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 1268880] Re: unable to toggle microphone mute on T410 / unable to unload thinkpad_acpi module
Still a problem with 3.13.0-5-generic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1268880 Title: unable to toggle microphone mute on T410 / unable to unload thinkpad_acpi module Status in “linux” package in Ubuntu: Confirmed Bug description: I recently pressed the physical microphone mute button on my Lenovo T410. However, I am now unable to unmute it. The orange light next to the mic mute button comes on when the kernel boots, but pressing it has no effect. Possibly related to this, I am now unable to unload the thinkpad_acpi kernel module (required to run the fan in disengaged mode to work around the long-standing bug 751689) as it seems to be permanently hooked into the sound drivers: $ sudo modprobe -r thinkpad_acpi modprobe: FATAL: Module thinkpad_acpi is in use. $ sudo lsmod|grep thinkpad_acpi thinkpad_acpi 69003 1 nvram 14027 1 thinkpad_acpi snd60871 23 snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_conexant,snd_pcm,snd_seq,snd_rawmidi,snd_hda_codec,snd_hda_intel,thinkpad_acpi,snd_seq_device,snd_seq_midi $ sudo modprobe -r thinkpad_acpi snd_hwdep snd_timer snd_hda_codec_hdmi snd_hda_codec_conexant snd_pcm snd_seq snd_rawmidi snd_hda_codec snd_hda_intel thinkpad_acpi snd_seq_device snd_seq_midi modprobe: FATAL: Module thinkpad_acpi is in use. $ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-2-generic 3.13.0-2.17 ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7 Uname: Linux 3.13.0-2-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.1-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 3261 F pulseaudio /dev/snd/controlC0: james 3261 F pulseaudio /dev/snd/pcmC0D0p: james 3261 F...m pulseaudio CurrentDesktop: Unity Date: Tue Jan 14 08:52:57 2014 HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312 InstallationDate: Installed on 2010-10-21 (1181 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) MachineType: LENOVO 2516CTO ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-2-generic root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-2-generic N/A linux-backports-modules-3.13.0-2-generic N/A linux-firmware1.121 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-11-01 (73 days ago) dmi.bios.date: 08/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET72WW (1.32 ) dmi.board.name: 2516CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2516CTO dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268880/+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 1268906] Re: cpu soft lockup running kvm
dmesg from 3.13.0-5-generic kernel. ** Attachment added: dmesg.3.13.0-5-generic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+attachment/3954151/+files/dmesg.3.13.0-5-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1268906 Title: cpu soft lockup running kvm Status in “linux” package in Ubuntu: Confirmed Status in “qemu-kvm” package in Ubuntu: New Bug description: Ran twice - first time running kvm killed my system. The second time, I just got lots of kernel oops messages in dmesg. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-2-generic 3.13.0-2.17 ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7 Uname: Linux 3.13.0-2-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.1-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 3250 F pulseaudio /dev/snd/controlC0: james 3250 F pulseaudio /dev/snd/pcmC0D0p: james 3250 F...m pulseaudio CurrentDesktop: Unity Date: Tue Jan 14 10:29:20 2014 HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312 InstallationDate: Installed on 2010-10-21 (1181 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) MachineType: LENOVO 2516CTO ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-2-generic root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-2-generic N/A linux-backports-modules-3.13.0-2-generic N/A linux-firmware1.121 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-11-01 (73 days ago) dmi.bios.date: 08/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET72WW (1.32 ) dmi.board.name: 2516CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2516CTO dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+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 1256949] Re: Dell Latitude E5420 doesn't boot if killswitch is turned to radio off
At this point, I'd suggest temporarily disabling the network-manager upstart job (which will of course disable networking): echo manual | sudo tee /etc/init/network-manager.override Does this give a reliable boot? To undo this change simply delete the override file: sudo rm /etc/init/network-manager.override Also, what is the contents of your modules file?: $ cat /etc/modules -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1256949 Title: Dell Latitude E5420 doesn't boot if killswitch is turned to radio off Status in “linux” package in Ubuntu: Incomplete Status in “upstart” package in Ubuntu: Incomplete Bug description: Ubuntu 12.04.3, Dell E5420. Boots fine with killswitch to radio on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1256949/+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 1263738] Re: login console 0 in user namespace container is not configured right
@Serge - perfectly happy to change that, in fact... @Stéphane - could you review and test lp:~jamesodhunt/upstart/kmsg- noctty? 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/1263738 Title: login console 0 in user namespace container is not configured right Status in Upstart: New Status in “linux” package in Ubuntu: Confirmed Status in “lxc” package in Ubuntu: Triaged Status in “linux” source package in Trusty: Confirmed Status in “lxc” source package in Trusty: Triaged Bug description: When you create a container in a private user namespace, when you start the container without the '-d' flag, that console is not properly set up. Logging in gives you -bash: no job control in this shell and hitting ctrl-c reboots the container. Consoles from 'lxc-console -n $container' behave correctly. This may be a kernel issue, as discussed here: http://lists.linuxcontainers.org/pipermail/lxc- devel/2013-October/005843.html so also marking this as affecting the kernel. This can be worked around, but really needs to be fixed before trusty is frozen. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1263738/+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 1256949] Re: Dell Latitude E5420 doesn't boot if killswitch is turned to radio off
@meamy: Please can you try booting again with --debug - your attachment in #14 looks like you booted with --verbose instead? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1256949 Title: Dell Latitude E5420 doesn't boot if killswitch is turned to radio off Status in “linux” package in Ubuntu: Incomplete Status in “upstart” package in Ubuntu: Incomplete Bug description: Ubuntu 12.04.3, Dell E5420. Boots fine with killswitch to radio on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1256949/+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 1256949] Re: Dell Latitude E5420 doesn't boot if killswitch is turned to radio off
Other things to try... When the system freezes: 1) Can you still toggle the caps-lock light by pressing the caps-lock key? 2) Can you reboot by holding down *all* of the following keys combos (do all of them): alt + sysrq + s alt + sysrq + u alt + sysrq + b Also, would it be possible to try re-installing with a 13.10 / 14.04 image to see if the behaviour is different? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1256949 Title: Dell Latitude E5420 doesn't boot if killswitch is turned to radio off Status in “linux” package in Ubuntu: Incomplete Status in “upstart” package in Ubuntu: Incomplete Bug description: Ubuntu 12.04.3, Dell E5420. Boots fine with killswitch to radio on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1256949/+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 1263738] Re: login console 0 in user namespace container is not configured right
** Changed in: upstart Assignee: (unassigned) = James Hunt (jamesodhunt) ** Changed in: upstart Status: New = Fix Committed ** Also affects: upstart (Ubuntu) Importance: Undecided Status: New ** Changed in: upstart (Ubuntu Trusty) Status: New = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1263738 Title: login console 0 in user namespace container is not configured right Status in Upstart: Fix Committed Status in “linux” package in Ubuntu: Confirmed Status in “lxc” package in Ubuntu: Triaged Status in “upstart” package in Ubuntu: Confirmed Status in “linux” source package in Trusty: Confirmed Status in “lxc” source package in Trusty: Triaged Status in “upstart” source package in Trusty: Confirmed Bug description: When you create a container in a private user namespace, when you start the container without the '-d' flag, that console is not properly set up. Logging in gives you -bash: no job control in this shell and hitting ctrl-c reboots the container. Consoles from 'lxc-console -n $container' behave correctly. This may be a kernel issue, as discussed here: http://lists.linuxcontainers.org/pipermail/lxc- devel/2013-October/005843.html so also marking this as affecting the kernel. This can be worked around, but really needs to be fixed before trusty is frozen. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1263738/+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 1268880] Re: unable to toggle microphone mute on T410 / unable to unload thinkpad_acpi module
Still a problem with 3.13.0-4-generic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1268880 Title: unable to toggle microphone mute on T410 / unable to unload thinkpad_acpi module Status in “linux” package in Ubuntu: Confirmed Bug description: I recently pressed the physical microphone mute button on my Lenovo T410. However, I am now unable to unmute it. The orange light next to the mic mute button comes on when the kernel boots, but pressing it has no effect. Possibly related to this, I am now unable to unload the thinkpad_acpi kernel module (required to run the fan in disengaged mode to work around the long-standing bug 751689) as it seems to be permanently hooked into the sound drivers: $ sudo modprobe -r thinkpad_acpi modprobe: FATAL: Module thinkpad_acpi is in use. $ sudo lsmod|grep thinkpad_acpi thinkpad_acpi 69003 1 nvram 14027 1 thinkpad_acpi snd60871 23 snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_conexant,snd_pcm,snd_seq,snd_rawmidi,snd_hda_codec,snd_hda_intel,thinkpad_acpi,snd_seq_device,snd_seq_midi $ sudo modprobe -r thinkpad_acpi snd_hwdep snd_timer snd_hda_codec_hdmi snd_hda_codec_conexant snd_pcm snd_seq snd_rawmidi snd_hda_codec snd_hda_intel thinkpad_acpi snd_seq_device snd_seq_midi modprobe: FATAL: Module thinkpad_acpi is in use. $ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-2-generic 3.13.0-2.17 ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7 Uname: Linux 3.13.0-2-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.1-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 3261 F pulseaudio /dev/snd/controlC0: james 3261 F pulseaudio /dev/snd/pcmC0D0p: james 3261 F...m pulseaudio CurrentDesktop: Unity Date: Tue Jan 14 08:52:57 2014 HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312 InstallationDate: Installed on 2010-10-21 (1181 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) MachineType: LENOVO 2516CTO ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-2-generic root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-2-generic N/A linux-backports-modules-3.13.0-2-generic N/A linux-firmware1.121 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-11-01 (73 days ago) dmi.bios.date: 08/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET72WW (1.32 ) dmi.board.name: 2516CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2516CTO dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268880/+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 1263738] Re: login console 0 in user namespace container is not configured right
I haven't been able to find where in upstart this is happening, but on the kernel side I can tell that it's due to an open() without O_NOCTTY. Upstart does not open /dev/console without O_NOCTTY afaics. Are you sure your kernel debug is showing pid 1 is doing this? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1263738 Title: login console 0 in user namespace container is not configured right Status in Upstart: New Status in “linux” package in Ubuntu: Confirmed Status in “lxc” package in Ubuntu: Triaged Status in “linux” source package in Trusty: Confirmed Status in “lxc” source package in Trusty: Triaged Bug description: When you create a container in a private user namespace, when you start the container without the '-d' flag, that console is not properly set up. Logging in gives you -bash: no job control in this shell and hitting ctrl-c reboots the container. Consoles from 'lxc-console -n $container' behave correctly. This may be a kernel issue, as discussed here: http://lists.linuxcontainers.org/pipermail/lxc- devel/2013-October/005843.html so also marking this as affecting the kernel. This can be worked around, but really needs to be fixed before trusty is frozen. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1263738/+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 955287] Re: Ubuntu should handle hot CPUs by taking preemptive action and warning users
Hi Colin - thanks, I'm now running thermald but cannot really stress my system due to o/s bug 1268906 (kvm always makes it overheat unless fans are disengaged. That is currently not possible on my T410 btw due to bug 1268880 - will that impact thermald's abilities? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/955287 Title: Ubuntu should handle hot CPUs by taking preemptive action and warning users Status in “linux” package in Ubuntu: Incomplete Bug description: If the kernel detects your CPU(s) is/are too hot currently (see bug 751689), the kernel calls /sbin/poweroff. This will provide a graceful system shutdown. If /sbin/poweroff fails, the kernel just forcibly shuts the system down. However, both strategies are last resorts and are called when the system temperature has reached a critical level. However, the kernel seems to emit an ACPI event when it detects the CPU(s) are merely hot. I suggest we consider adding an acpi hook to attempt to avoid a critical scenario. Currently, the user experience when critical gets hit is not good - the system just shuts down with no warning whatsoever. This is alarming in the extreme to users. Ideas: - proactively attempt to kill off power hogging processes (use powertop?) - ramp fans to maximum and present the user with a warning window explaining what is happening. - present the user with a window of high-power processes and ask *them* to select the processes they'd like to kill off in an effort to avoid a system shutdown. Problems: - it is unclear (to me atleast) how close (in terms of degrees centigrade) hot and critical are (is it different for all CPUs ?) As such, it is unclear how long (time) it might take for a system that is hot to go critical and just shutdown. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: acpi-support 0.140 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9 Uname: Linux 3.2.0-18-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 1.94.1-0ubuntu2 Architecture: i386 Date: Wed Mar 14 17:22:09 2012 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=fr_CA.UTF8 SHELL=/bin/bash SourcePackage: acpi-support UpgradeStatus: Upgraded to precise on 2012-01-12 (62 days ago) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.94.1-0ubuntu2 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 3788 F pulseaudio /dev/snd/controlC0: james 3788 F pulseaudio james 10267 F alsamixer Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf242 irq 45' Mixer name : 'Conexant CX20585' Components : 'HDA:14f15069,17aa214c,00100302 HDA:14f12c06,17aa2122,0010' Controls : 9 Simple ctrls : 6 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xcdefc000 irq 16' Mixer name : 'Nvidia GPU 0b HDMI/DP' Components : 'HDA:10de000b,10de0101,00100100' Controls : 24 Simple ctrls : 4 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 6IHT37WW-1.12' Mixer name : 'ThinkPad EC 6IHT37WW-1.12' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) MachineType: LENOVO 2516CTO NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=fr_CA.UTF8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic-pae root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro acpi_sleep=nonvs console=ttyUSB0,115200n8r console=tty quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9 RelatedPackageVersions: linux-restricted-modules-3.2.0-18-generic-pae N/A linux-backports-modules-3.2.0-18-generic-pae N/A linux-firmware1.71 StagingDrivers: mei Tags: precise staging Uname: Linux 3.2.0-18-generic-pae i686 UpgradeStatus: Upgraded to precise on 2012-01-12 (62 days ago) UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare sbuild dmi.bios.date: 08/27/2010 dmi.bios.vendor: LENOVO
[Kernel-packages] [Bug 1268906] Re: cpu soft lockup running kvm
Same problem with 3.13.0-4-generic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1268906 Title: cpu soft lockup running kvm Status in “linux” package in Ubuntu: Confirmed Status in “qemu-kvm” package in Ubuntu: New Bug description: Ran twice - first time running kvm killed my system. The second time, I just got lots of kernel oops messages in dmesg. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-2-generic 3.13.0-2.17 ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7 Uname: Linux 3.13.0-2-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.1-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 3250 F pulseaudio /dev/snd/controlC0: james 3250 F pulseaudio /dev/snd/pcmC0D0p: james 3250 F...m pulseaudio CurrentDesktop: Unity Date: Tue Jan 14 10:29:20 2014 HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312 InstallationDate: Installed on 2010-10-21 (1181 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) MachineType: LENOVO 2516CTO ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-2-generic root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-2-generic N/A linux-backports-modules-3.13.0-2-generic N/A linux-firmware1.121 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-11-01 (73 days ago) dmi.bios.date: 08/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET72WW (1.32 ) dmi.board.name: 2516CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2516CTO dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+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 1268880] Re: unable to toggle microphone mute on T410 / unable to unload thinkpad_acpi module
Problem still present with 3.13.0-031300rc8-generic kernel. Note that with that kernel I get the following message at boot time: tpm_tis 00:09: A TPM error (6) occurred attempting to read a pcr value -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1268880 Title: unable to toggle microphone mute on T410 / unable to unload thinkpad_acpi module Status in “linux” package in Ubuntu: Incomplete Bug description: I recently pressed the physical microphone mute button on my Lenovo T410. However, I am now unable to unmute it. The orange light next to the mic mute button comes on when the kernel boots, but pressing it has no effect. Possibly related to this, I am now unable to unload the thinkpad_acpi kernel module (required to run the fan in disengaged mode to work around the long-standing bug 751689) as it seems to be permanently hooked into the sound drivers: $ sudo modprobe -r thinkpad_acpi modprobe: FATAL: Module thinkpad_acpi is in use. $ sudo lsmod|grep thinkpad_acpi thinkpad_acpi 69003 1 nvram 14027 1 thinkpad_acpi snd60871 23 snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_conexant,snd_pcm,snd_seq,snd_rawmidi,snd_hda_codec,snd_hda_intel,thinkpad_acpi,snd_seq_device,snd_seq_midi $ sudo modprobe -r thinkpad_acpi snd_hwdep snd_timer snd_hda_codec_hdmi snd_hda_codec_conexant snd_pcm snd_seq snd_rawmidi snd_hda_codec snd_hda_intel thinkpad_acpi snd_seq_device snd_seq_midi modprobe: FATAL: Module thinkpad_acpi is in use. $ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-2-generic 3.13.0-2.17 ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7 Uname: Linux 3.13.0-2-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.1-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 3261 F pulseaudio /dev/snd/controlC0: james 3261 F pulseaudio /dev/snd/pcmC0D0p: james 3261 F...m pulseaudio CurrentDesktop: Unity Date: Tue Jan 14 08:52:57 2014 HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312 InstallationDate: Installed on 2010-10-21 (1181 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) MachineType: LENOVO 2516CTO ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-2-generic root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-2-generic N/A linux-backports-modules-3.13.0-2-generic N/A linux-firmware1.121 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-11-01 (73 days ago) dmi.bios.date: 08/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET72WW (1.32 ) dmi.board.name: 2516CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2516CTO dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268880/+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 1268906] Re: cpu soft lockup running kvm
Alas, same issue using kernel 3.13.0-031300rc8-generic. ** Changed in: linux (Ubuntu) Status: Incomplete = 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/1268906 Title: cpu soft lockup running kvm Status in “linux” package in Ubuntu: New Status in “qemu-kvm” package in Ubuntu: New Bug description: Ran twice - first time running kvm killed my system. The second time, I just got lots of kernel oops messages in dmesg. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-2-generic 3.13.0-2.17 ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7 Uname: Linux 3.13.0-2-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.1-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 3250 F pulseaudio /dev/snd/controlC0: james 3250 F pulseaudio /dev/snd/pcmC0D0p: james 3250 F...m pulseaudio CurrentDesktop: Unity Date: Tue Jan 14 10:29:20 2014 HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312 InstallationDate: Installed on 2010-10-21 (1181 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) MachineType: LENOVO 2516CTO ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-2-generic root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-2-generic N/A linux-backports-modules-3.13.0-2-generic N/A linux-firmware1.121 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-11-01 (73 days ago) dmi.bios.date: 08/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET72WW (1.32 ) dmi.board.name: 2516CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2516CTO dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+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 1268880] Re: unable to toggle microphone mute on T410 / unable to unload thinkpad_acpi module
Regression seems to have been introduced in 3.13. I've tested with a few kernels and narrowed it to: 3.13.0-1-generic: BAD 3.11.0-2-generic : OK -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1268880 Title: unable to toggle microphone mute on T410 / unable to unload thinkpad_acpi module Status in “linux” package in Ubuntu: Incomplete Bug description: I recently pressed the physical microphone mute button on my Lenovo T410. However, I am now unable to unmute it. The orange light next to the mic mute button comes on when the kernel boots, but pressing it has no effect. Possibly related to this, I am now unable to unload the thinkpad_acpi kernel module (required to run the fan in disengaged mode to work around the long-standing bug 751689) as it seems to be permanently hooked into the sound drivers: $ sudo modprobe -r thinkpad_acpi modprobe: FATAL: Module thinkpad_acpi is in use. $ sudo lsmod|grep thinkpad_acpi thinkpad_acpi 69003 1 nvram 14027 1 thinkpad_acpi snd60871 23 snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_conexant,snd_pcm,snd_seq,snd_rawmidi,snd_hda_codec,snd_hda_intel,thinkpad_acpi,snd_seq_device,snd_seq_midi $ sudo modprobe -r thinkpad_acpi snd_hwdep snd_timer snd_hda_codec_hdmi snd_hda_codec_conexant snd_pcm snd_seq snd_rawmidi snd_hda_codec snd_hda_intel thinkpad_acpi snd_seq_device snd_seq_midi modprobe: FATAL: Module thinkpad_acpi is in use. $ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-2-generic 3.13.0-2.17 ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7 Uname: Linux 3.13.0-2-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.1-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 3261 F pulseaudio /dev/snd/controlC0: james 3261 F pulseaudio /dev/snd/pcmC0D0p: james 3261 F...m pulseaudio CurrentDesktop: Unity Date: Tue Jan 14 08:52:57 2014 HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312 InstallationDate: Installed on 2010-10-21 (1181 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) MachineType: LENOVO 2516CTO ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-2-generic root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-2-generic N/A linux-backports-modules-3.13.0-2-generic N/A linux-firmware1.121 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-11-01 (73 days ago) dmi.bios.date: 08/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET72WW (1.32 ) dmi.board.name: 2516CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2516CTO dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268880/+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 1268880] Re: unable to toggle microphone mute on T410 / unable to unload thinkpad_acpi module
** 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/1268880 Title: unable to toggle microphone mute on T410 / unable to unload thinkpad_acpi module Status in “linux” package in Ubuntu: Confirmed Bug description: I recently pressed the physical microphone mute button on my Lenovo T410. However, I am now unable to unmute it. The orange light next to the mic mute button comes on when the kernel boots, but pressing it has no effect. Possibly related to this, I am now unable to unload the thinkpad_acpi kernel module (required to run the fan in disengaged mode to work around the long-standing bug 751689) as it seems to be permanently hooked into the sound drivers: $ sudo modprobe -r thinkpad_acpi modprobe: FATAL: Module thinkpad_acpi is in use. $ sudo lsmod|grep thinkpad_acpi thinkpad_acpi 69003 1 nvram 14027 1 thinkpad_acpi snd60871 23 snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_conexant,snd_pcm,snd_seq,snd_rawmidi,snd_hda_codec,snd_hda_intel,thinkpad_acpi,snd_seq_device,snd_seq_midi $ sudo modprobe -r thinkpad_acpi snd_hwdep snd_timer snd_hda_codec_hdmi snd_hda_codec_conexant snd_pcm snd_seq snd_rawmidi snd_hda_codec snd_hda_intel thinkpad_acpi snd_seq_device snd_seq_midi modprobe: FATAL: Module thinkpad_acpi is in use. $ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-2-generic 3.13.0-2.17 ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7 Uname: Linux 3.13.0-2-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.1-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 3261 F pulseaudio /dev/snd/controlC0: james 3261 F pulseaudio /dev/snd/pcmC0D0p: james 3261 F...m pulseaudio CurrentDesktop: Unity Date: Tue Jan 14 08:52:57 2014 HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312 InstallationDate: Installed on 2010-10-21 (1181 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) MachineType: LENOVO 2516CTO ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-2-generic root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-2-generic N/A linux-backports-modules-3.13.0-2-generic N/A linux-firmware1.121 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-11-01 (73 days ago) dmi.bios.date: 08/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET72WW (1.32 ) dmi.board.name: 2516CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2516CTO dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268880/+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 1268880] [NEW] unable to toggle microphone mute on T410 / unable to unload thinkpad_acpi module
Public bug reported: I recently pressed the physical microphone mute button on my Lenovo T410. However, I am now unable to unmute it. The orange light next to the mic mute button comes on when the kernel boots, but pressing it has no effect. Possibly related to this, I am now unable to unload the thinkpad_acpi kernel module (required to run the fan in disengaged mode to work around the long-standing bug 751689) as it seems to be permanently hooked into the sound drivers: $ sudo modprobe -r thinkpad_acpi modprobe: FATAL: Module thinkpad_acpi is in use. $ sudo lsmod|grep thinkpad_acpi thinkpad_acpi 69003 1 nvram 14027 1 thinkpad_acpi snd60871 23 snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_conexant,snd_pcm,snd_seq,snd_rawmidi,snd_hda_codec,snd_hda_intel,thinkpad_acpi,snd_seq_device,snd_seq_midi $ sudo modprobe -r thinkpad_acpi snd_hwdep snd_timer snd_hda_codec_hdmi snd_hda_codec_conexant snd_pcm snd_seq snd_rawmidi snd_hda_codec snd_hda_intel thinkpad_acpi snd_seq_device snd_seq_midi modprobe: FATAL: Module thinkpad_acpi is in use. $ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-2-generic 3.13.0-2.17 ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7 Uname: Linux 3.13.0-2-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.1-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 3261 F pulseaudio /dev/snd/controlC0: james 3261 F pulseaudio /dev/snd/pcmC0D0p: james 3261 F...m pulseaudio CurrentDesktop: Unity Date: Tue Jan 14 08:52:57 2014 HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312 InstallationDate: Installed on 2010-10-21 (1181 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) MachineType: LENOVO 2516CTO ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-2-generic root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-2-generic N/A linux-backports-modules-3.13.0-2-generic N/A linux-firmware1.121 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-11-01 (73 days ago) dmi.bios.date: 08/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET72WW (1.32 ) dmi.board.name: 2516CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2516CTO dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1268880 Title: unable to toggle microphone mute on T410 / unable to unload thinkpad_acpi module Status in “linux” package in Ubuntu: New Bug description: I recently pressed the physical microphone mute button on my Lenovo T410. However, I am now unable to unmute it. The orange light next to the mic mute button comes on when the kernel boots, but pressing it has no effect. Possibly related to this, I am now unable to unload the thinkpad_acpi kernel module (required to run the fan in disengaged mode to work around the long-standing bug 751689) as it seems to be permanently hooked into the sound drivers: $ sudo modprobe -r thinkpad_acpi modprobe: FATAL: Module thinkpad_acpi is in use. $ sudo lsmod|grep thinkpad_acpi thinkpad_acpi 69003 1 nvram 14027 1 thinkpad_acpi snd60871 23 snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_conexant,snd_pcm,snd_seq,snd_rawmidi,snd_hda_codec,snd_hda_intel,thinkpad_acpi,snd_seq_device,snd_seq_midi $ sudo modprobe -r thinkpad_acpi snd_hwdep snd_timer snd_hda_codec_hdmi snd_hda_codec_conexant snd_pcm snd_seq snd_rawmidi snd_hda_codec snd_hda_intel thinkpad_acpi snd_seq_device snd_seq_midi modprobe: FATAL: Module thinkpad_acpi is in use. $ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-2-generic 3.13.0-2.17 ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7 Uname: Linux 3.13.0-2-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.1-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 3261 F pulseaudio /dev/snd/controlC0: james 3261 F pulseaudio /dev/snd/pcmC0D0p: james 3261 F...m pulseaudio CurrentDesktop: Unity Date: Tue Jan 14 08:52:57 2014 HibernationDevice:
[Kernel-packages] [Bug 1268906] Re: cpu soft lockup running kvm
See CurrentDmesg.txt for lots of errors such as: [ 1688.474887] Call Trace: [ 1688.474914] [f8bae0f3] kvm_vcpu_ioctl+0x433/0x4d0 [kvm] [ 1688.474924] [c108064f] ? wake_up_state+0xf/0x20 [ 1688.474931] [c10b9795] ? wake_futex+0x65/0x90 [ 1688.474937] [c10babed] ? futex_wake+0x13d/0x160 [ 1688.474942] [c10bbe4b] ? do_futex+0xeb/0x660 [ 1688.474966] [f8badcc0] ? vcpu_put+0x30/0x30 [kvm] [ 1688.474972] [c1186012] do_vfs_ioctl+0x2e2/0x4d0 [ 1688.474977] [c10b7819] ? tick_program_event+0x29/0x30 [ 1688.474983] [c1075eb2] ? hrtimer_interrupt+0x142/0x2b0 [ 1688.474988] [c10bc44c] ? SyS_futex+0x8c/0x140 [ 1688.474993] [c1186260] SyS_ioctl+0x60/0x80 [ 1688.475002] [c1646147] syscall_call+0x7/0xb [ 1688.475009] [c164] ? __ticket_unlock_slowpath+0x13/0x31 ** Also affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1268906 Title: cpu soft lockup running kvm Status in “linux” package in Ubuntu: New Status in “qemu-kvm” package in Ubuntu: New Bug description: Ran twice - first time running kvm killed my system. The second time, I just got lots of kernel oops messages in dmesg. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-2-generic 3.13.0-2.17 ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7 Uname: Linux 3.13.0-2-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.1-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 3250 F pulseaudio /dev/snd/controlC0: james 3250 F pulseaudio /dev/snd/pcmC0D0p: james 3250 F...m pulseaudio CurrentDesktop: Unity Date: Tue Jan 14 10:29:20 2014 HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312 InstallationDate: Installed on 2010-10-21 (1181 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) MachineType: LENOVO 2516CTO ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-2-generic root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-2-generic N/A linux-backports-modules-3.13.0-2-generic N/A linux-firmware1.121 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-11-01 (73 days ago) dmi.bios.date: 08/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET72WW (1.32 ) dmi.board.name: 2516CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2516CTO dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+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 1263140] Re: reboot does not terminate at computer shutdown
Thanks for reporting this issue. It sounds like a kernel issue. Also, it looks like you are running a custom kernel? ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1263140 Title: reboot does not terminate at computer shutdown Status in “linux” package in Ubuntu: Incomplete Status in “upstart” package in Ubuntu: New Bug description: Ubuntu 13.10 Shutdown and rebbot whether via terminal or GUI buttons hangs and does not shut off power on my PC. I have to hold down the power button to do full power off, ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: upstart 1.10-0ubuntu7 Uname: Linux 3.12.0-031200-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Thu Dec 19 13:45:25 2013 ExecutablePath: /sbin/reboot InstallationDate: Installed on 2013-10-19 (61 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True OmitPids: 1130 941 755 11955 732 713 699 12012 819 719 12041 755 11955 732 713 699 12012 819 719 ProcCmdline: /sbin/poweroff ProcEnviron: ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.12.0-031200-generic root=UUID=99ee33d3-3574-42e4-9b82-5f0f954cfc69 ro quiet splash acpi=force vt.handoff=7 SourcePackage: upstart Title: reboot does not terminate at computer shutdown UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System UpstartRunningSystemVersion: init (upstart 1.10) modified.conffile..etc.default.whoopsie: [modified] mtime.conffile..etc.default.whoopsie: 2013-10-22T11:31:34.550082 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1263140/+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 1256949] Re: Dell Latitude E5420 doesn't boot if killswitch is turned to radio off
@meamy - ok, I am starting to suspect this is either a kernel or graphics card issue. Adding linux to bug. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1256949 Title: Dell Latitude E5420 doesn't boot if killswitch is turned to radio off Status in “linux” package in Ubuntu: New Status in “upstart” package in Ubuntu: Incomplete Bug description: Ubuntu 12.04.3, Dell E5420. Boots fine with killswitch to radio on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1256949/+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 1235649] Re: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch
** Changed in: upstart Assignee: (unassigned) = James Hunt (jamesodhunt) ** Changed in: upstart Status: New = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch Status in Upstart: Fix Committed Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: Confirmed Status in “upstart” package in Ubuntu: In Progress Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: Invalid Status in “unity” source package in Saucy: Confirmed Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235649/+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 1247769] Re: kernel headers do not define OVERLAYFS_SUPER_MAGIC
Hi Joseph, Due to the headaches introduced by bug 882147 (which effectively guarantees that tests will fail erroneously), we are changing the Upstart tests to detect a /tmp overlayfs filesystem and display a warning. One approach is to make use of OVERLAYFS_SUPER_MAGIC to check /tmp. See below for the discussion: https://code.launchpad.net/~jamesodhunt/upstart/check-for- overlayfs/+merge/191393 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1247769 Title: kernel headers do not define OVERLAYFS_SUPER_MAGIC Status in “linux” package in Ubuntu: In Progress Status in “linux” source package in Precise: In Progress Status in “linux” source package in Quantal: In Progress Status in “linux” source package in Raring: In Progress Status in “linux” source package in Saucy: In Progress Status in “linux” source package in Trusty: In Progress Bug description: Include file /usr/include/linux/magic.h is missing the following: #define OVERLAYFS_SUPER_MAGIC 0x794c764f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1247769/+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 1247769] [NEW] kernel headers do not define OVERLAYFS_SUPER_MAGIC
Public bug reported: Include file /usr/include/linux/magic.h is missing the following: #define OVERLAYFS_SUPER_MAGIC 0x794c764f ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1247769 Title: kernel headers do not define OVERLAYFS_SUPER_MAGIC Status in “linux” package in Ubuntu: Incomplete Bug description: Include file /usr/include/linux/magic.h is missing the following: #define OVERLAYFS_SUPER_MAGIC 0x794c764f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1247769/+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 1244312] Re: [regression 13.10] Can't reboot (but can shut down)
@Rebecca: yes, but the man page is referring to bugs in the reboot command. That commands calls the reboot system call and that is where the problem lies (in the kernel). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1244312 Title: [regression 13.10] Can't reboot (but can shut down) Status in “linux” package in Ubuntu: Confirmed Status in “upstart” package in Ubuntu: New Bug description: Since upgrading to 13.10, attempting to restart (with either shutdown -r now or the system menu item) hangs with a reboot: restarting system message instead of actually rebooting, but shutting down still turns the system off. WORKAROUND: adding reboot=p to the kernel command line (https://wiki.ubuntu.com/Kernel/KernelBootParameters) avoids this bug. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: upstart 1.10-0ubuntu7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Thu Oct 24 17:25:08 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2012-01-25 (637 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MarkForUpload: True ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=b491a34a-6045-4ad4-a2b8-b9ca018c5d41 ro quiet splash SourcePackage: upstart UpgradeStatus: Upgraded to saucy on 2013-10-21 (2 days ago) UpstartBugCategory: System UpstartRunningSessionVersion: init (upstart 1.10) UpstartRunningSystemVersion: init (upstart 1.10) modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Permission denied: '/etc/at.deny'] modified.conffile..etc.init.d.networking: [modified] mtime.conffile..etc.init.d.networking: 2013-08-26T23:19:11 --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: palmer 2534 F pulseaudio /dev/snd/controlC0: palmer 2534 F pulseaudio /dev/snd/pcmC0D0p: palmer 2534 F...m pulseaudio DistroRelease: Ubuntu 13.10 EcryptfsInUse: Yes InstallationDate: Installed on 2012-01-25 (638 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: Dell Inc. Latitude E6520 MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=b491a34a-6045-4ad4-a2b8-b9ca018c5d41 ro quiet splash ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 Tags: saucy Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-21 (3 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 10/18/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0J4TFW dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0J4TFW:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6520 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: palmer 2534 F pulseaudio /dev/snd/controlC0: palmer 2534 F pulseaudio DistroRelease: Ubuntu 13.10 EcryptfsInUse: Yes InstallationDate: Installed on 2012-01-25 (638 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: Dell Inc. Latitude E6520 MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=b491a34a-6045-4ad4-a2b8-b9ca018c5d41 ro quiet splash ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 Tags: saucy Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-21 (3 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 10/18/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0J4TFW dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0J4TFW:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name:
[Kernel-packages] [Bug 1244312] Re: [regression 13.10] Can't reboot (but can shut down)
Hi Rebecca, Thanks for reporting this. The screenshot shows this to be a kernel issue, not an Upstart one. Reassigning... ** Package changed: upstart (Ubuntu) = linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1244312 Title: [regression 13.10] Can't reboot (but can shut down) Status in “linux” package in Ubuntu: New Bug description: Since upgrading to 13.10, attempting to restart (with either shutdown -r now or the system menu item) hangs with a reboot: restarting system message instead of actually rebooting, but shutting down still turns the system off. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: upstart 1.10-0ubuntu7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Thu Oct 24 17:25:08 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2012-01-25 (637 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MarkForUpload: True ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=b491a34a-6045-4ad4-a2b8-b9ca018c5d41 ro quiet splash SourcePackage: upstart UpgradeStatus: Upgraded to saucy on 2013-10-21 (2 days ago) UpstartBugCategory: System UpstartRunningSessionVersion: init (upstart 1.10) UpstartRunningSystemVersion: init (upstart 1.10) modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Permission denied: '/etc/at.deny'] modified.conffile..etc.init.d.networking: [modified] mtime.conffile..etc.init.d.networking: 2013-08-26T23:19:11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1244312/+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 1235649] Re: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch
** Changed in: upstart (Ubuntu) Status: Fix Released = Incomplete ** Changed in: upstart (Ubuntu) Status: Incomplete = In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch Status in Upstart: New Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: In Progress Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: Invalid Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235649/+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 1235649] Re: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch
We already have bug 1203595 for having the Session Init connect to the D-Bus session bus. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch Status in Upstart: New Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: Invalid Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235649/+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 1235649] Re: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch
FWICS D-Bus is behaving as designed: since the client has not called dbus_connection_set_wakeup_main_function(), and since D-Bus messaging is reliable, all libdbus is able to do when a signal is sent to a connection is cache any messages the client has not yet processed in the hope that at some future point it might consume them. The key part of the D-Bus code that explains this is dbus_connection_send_preallocated_unlocked_no_update(): -- /* Now we need to run an iteration to hopefully just write the messages * out immediately, and otherwise get them queued up */ _dbus_connection_do_iteration_unlocked (connection, NULL, DBUS_ITERATION_DO_WRITING, -1); /* If stuff is still queued up, be sure we wake up the main loop */ if (connection-n_outgoing 0) _dbus_connection_wakeup_mainloop (connection); -- As shown, the messages (signals in the case of Upstart) are added to the client connection queue, but since the client called dbus_connection_open() rather than nih_dbus_connect(), no mainloop handler is registered to allow the client to deal with the signals sent to it. From the upstart perspective, a fix is to call dbus_connection_has_messages_to_send() and ignore that connection if the client still has unprocessed messages (patch attached). From the D-Bus perspective, it would be useful to introduce a new public API: dbus_bool_t dbus_connection_has_wakeup_main_function (DBusConnection *connection); This would allow Upstart and other D-Bus server applications to detect erroneous client connections. ** Patch added: bug-1235649.diff https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1235649/+attachment/3879222/+files/bug-1235649.diff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch Status in Upstart: New Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: Invalid Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235649/+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 1235649] Re: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch
TBC, using the patch on #69 results in no memory bloat. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch Status in Upstart: New Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: Invalid Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235649/+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 1235649] Re: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch
Hi Steve, The trace in #59 was produced by: - Running Upstart via valgrind which upstart linked against debug builds of nih and dbus. - Running a single instance of the test program (#51). - Running spam.sh (#52). - Waiting until init was consuming ~200MB, then sending SIGTERM to the init/valgrind process. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch Status in Upstart: New Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: New Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: New Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235649/+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 1235649] Re: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch
Another valgrind log taken using the same precedure as above. However, this time I waited until the init process was consuming over 2GB of RAM. Top showed: PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 15329 james 20 0 2463m 2,0g 12m R 100,0 26,1 6:51.59 memcheck-x86-li Once again, the biggest offender by a huge margin is dbus: ==15329== 1,153,679,208 bytes in 12,025 blocks are still reachable in loss record 208 of 208 ==15329==at 0x402BB88: realloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) ==15329==by 0x408E778: dbus_realloc (dbus-memory.c:678) ==15329==by 0x408F08C: reallocate_for_length (dbus-string.c:349) ==15329==by 0x408F12B: set_length (dbus-string.c:390) ==15329==by 0x408F1A9: open_gap (dbus-string.c:411) ==15329==by 0x408FA67: copy (dbus-string.c:1198) ==15329==by 0x408FCCE: _dbus_string_copy_len (dbus-string.c:1368) ==15329==by 0x408DCF8: marshal_len_followed_by_bytes (dbus-marshal-basic.c:726) ==15329==by 0x408DD95: marshal_string (dbus-marshal-basic.c:758) ==15329==by 0x408DF60: _dbus_marshal_write_basic (dbus-marshal-basic.c:840) ==15329==by 0x4075CD7: _dbus_type_writer_write_basic_no_typecode (dbus-marshal-recursive.c:1601) ==15329==by 0x40768BB: _dbus_type_writer_write_basic (dbus-marshal-recursive.c:2323) ==15329== ==15329== LEAK SUMMARY: ==15329==definitely lost: 28 bytes in 1 blocks ==15329==indirectly lost: 24 bytes in 1 blocks ==15329== possibly lost: 133,265 bytes in 315 blocks ==15329==still reachable: 1,154,753,166 bytes in 18,194 blocks ==15329== suppressed: 0 bytes in 0 blocks ** Attachment added: vg-20131015.log.gz https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1235649/+attachment/3878397/+files/vg-20131015.log.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch Status in Upstart: New Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: New Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: New Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235649/+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 1235649] Re: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch
** Attachment added: spam_dbus_server.sh https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1235649/+attachment/3878665/+files/spam_dbus_server.sh -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch Status in Upstart: New Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: Invalid Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235649/+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 1235649] Re: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch
** Attachment added: test_nih_dbus_client.c https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1235649/+attachment/3878664/+files/test_nih_dbus_client.c -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch Status in Upstart: New Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: Invalid Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235649/+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 1235649] Re: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch
I can now recreate the memory bloat using a basic NIH D-Bus server program and associated client program. 1) Run the server as: $ ./test_nih_dbus_server unix:abstract=/com/hunt/james/foo com.hunt.james.Foo /com/hunt/james/Foo 2) Run the client as: $ ./test_nih_dbus_client unix:abstract=/com/hunt/james/foo com.hunt.james.Foo 3) Run the updated spammer as: $ ./spam_dbus_server.sh 4) Run top and watch the memory used by test_nih_dbus_server creep up. The problem seems to be caused by the call to notify_clients() - this sends a signal to every connected client every time the spam_dbus_server.sh sends its data to the server. Commenting out the call to notify_clients() stop the memory bloating issue. The function echo_handled() that is called by notify_clients() is analogous to control_emit_event_emitted() in Upstart parlance. Again, running valgrind on the server shows the same stack traces as above: ==30015== 91,750,175 bytes in 7,617 blocks are still reachable in loss record 164 of 164 ==30015==at 0x402BB88: realloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) ==30015==by 0x408E778: dbus_realloc (dbus-memory.c:678) ==30015==by 0x408F08C: reallocate_for_length (dbus-string.c:349) ==30015==by 0x408F12B: set_length (dbus-string.c:390) ==30015==by 0x408F1A9: open_gap (dbus-string.c:411) ==30015==by 0x408FA67: copy (dbus-string.c:1198) ==30015==by 0x408FCCE: _dbus_string_copy_len (dbus-string.c:1368) ==30015==by 0x408DCF8: marshal_len_followed_by_bytes (dbus-marshal-basic.c:726) ==30015==by 0x408DD95: marshal_string (dbus-marshal-basic.c:758) ==30015==by 0x408DF60: _dbus_marshal_write_basic (dbus-marshal-basic.c:840) ==30015==by 0x4075CD7: _dbus_type_writer_write_basic_no_typecode (dbus-marshal-recursive.c:1601) ==30015==by 0x40768BB: _dbus_type_writer_write_basic (dbus-marshal-recursive.c:2323) ** Attachment added: test_nih_dbus_server.c https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1235649/+attachment/3878663/+files/test_nih_dbus_server.c -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch Status in Upstart: New Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: Invalid Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235649/+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 1235649] Re: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch
Valgrind log from test_nih_dbus_server.c run using 'valgrind --num- callers=100 ...'. ** Attachment added: vg-test_nih_dbus_server.log.gz https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1235649/+attachment/3878682/+files/vg-test_nih_dbus_server.log.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch Status in Upstart: New Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: Invalid Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235649/+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 1235649] Re: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch
Just got a much more interesting valgrind run. Juicy excerpt: ==9366== 147,560 bytes in 1,190 blocks are still reachable in loss record 187 of 188 ==9366==at 0x402B965: calloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) ==9366==by 0x408E730: dbus_malloc0 (dbus-memory.c:572) ==9366==by 0x407983B: dbus_message_new_empty_header (dbus-message.c:1153) ==9366==by 0x4079D0F: dbus_message_new_method_return (dbus-message.c:1319) ==9366==by 0x80835F5: control_emit_event_reply (com.ubuntu.Upstart.c:2098) ==9366==by 0x806BC6C: event_finished (event.c:501) ==9366==by 0x806B26F: event_poll (event.c:259) ==9366==by 0x4044B63: nih_main_loop (main.c:609) ==9366==by 0x804D507: main (main.c:688) ==9366== ==9366== 228,394,752 bytes in 2,386 blocks are still reachable in loss record 188 of 188 ==9366==at 0x402BB88: realloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) ==9366==by 0x408E778: dbus_realloc (dbus-memory.c:678) ==9366==by 0x408F08C: reallocate_for_length (dbus-string.c:349) ==9366==by 0x408F12B: set_length (dbus-string.c:390) ==9366==by 0x408F1A9: open_gap (dbus-string.c:411) ==9366==by 0x408FA67: copy (dbus-string.c:1198) ==9366==by 0x408FCCE: _dbus_string_copy_len (dbus-string.c:1368) ==9366==by 0x408DCF8: marshal_len_followed_by_bytes (dbus-marshal-basic.c:726) ==9366==by 0x408DD95: marshal_string (dbus-marshal-basic.c:758) ==9366==by 0x408DF60: _dbus_marshal_write_basic (dbus-marshal-basic.c:840) ==9366==by 0x4075CD7: _dbus_type_writer_write_basic_no_typecode (dbus-marshal-recursive.c:1601) ==9366==by 0x40768BB: _dbus_type_writer_write_basic (dbus-marshal-recursive.c:2323) ==9366== ==9366== LEAK SUMMARY: ==9366==definitely lost: 28 bytes in 1 blocks ==9366==indirectly lost: 24 bytes in 1 blocks ==9366== possibly lost: 12,907 bytes in 290 blocks ==9366==still reachable: 228,607,834 bytes in 3,732 blocks ==9366== suppressed: 0 bytes in 0 blocks ** Attachment added: vg.log https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1235649/+attachment/3877842/+files/vg.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/1235649 Title: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch Status in Upstart: New Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: New Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: New Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235649/+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 1235649] Re: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch
Note that the following call on the server side does not resolve the issue: while (dbus_connection_dispatch (connection) == DBUS_DISPATCH_DATA_REMAINS) ; -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch Status in Upstart: New Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: New Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: New Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235649/+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 1235649] Re: uevent spam causes session upstart to consume massive amounts of memory on Ubuntu Touch
The problem is not observed when the only connections to upstart are the standard upstart bridges (since they use nih_dbus_connect()). For reference, here is nih_dbus_setup() which includes one or more calls that unity seemingly should be calling itself: http://bazaar.launchpad.net/~ubuntu- branches/ubuntu/saucy/libnih/saucy/view/head:/nih- dbus/dbus_connection.c#L202 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes session upstart to consume massive amounts of memory on Ubuntu Touch Status in Upstart: New Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: New Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: New Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235649/+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 1235649] Re: uevent spam causes session upstart to consume massive amounts of memory on Ubuntu Touch
This problem can now be demonstrated with a single connection to upstart that makes the following calls: dbus_connection_open() nih_dbus_proxy_new () The problem is not seen if the app instead calls: - nih_dbus_connect (upstart_session, disconnect_handler) - nih_dbus_proxy_new () - nih_main_loop() Or, - nih_dbus_connect (upstart_session, NULL) - nih_dbus_proxy_new () - nih_main_loop() Specifically, the problem appears to be that when an app calls dbus_connection_open(), one or more of the functions in nih_dbus_setup() should be being called to allow libdbus to interrupt the apps main loop and request callbacks are run to clean up resources. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes session upstart to consume massive amounts of memory on Ubuntu Touch Status in Upstart: New Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: New Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: New Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235649/+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 1235649] Re: uevent spam causes session upstart to consume massive amounts of memory on Ubuntu Touch
C program to trigger this bug. Run it in an environment with UPSTART_SESSION set (such as a desktop/Touch environment), then run the about-to-be attached spam.sh script. ** Attachment added: trigger-bug-1235649.c https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1235649/+attachment/3872618/+files/trigger-bug-1235649.c -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch Status in Upstart: New Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: New Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: New Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235649/+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 1235649] Re: uevent spam causes session upstart to consume massive amounts of memory on Ubuntu Touch
Run as: $ spam.sh session_init_pid ** Attachment added: spam.sh https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1235649/+attachment/3872619/+files/spam.sh -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch Status in Upstart: New Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: New Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: New Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235649/+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 1235649] Re: uevent spam causes session upstart to consume massive amounts of memory on Ubuntu Touch
Program attached in #51 demonstrates the incorrect calling behaviour. To demonstrate the correct behaviour change the #if0/else/endif such that rather than calling dbus_connection_open(), the program calls nih_dbus_connect(). nih_dbus_connect(): No memory growth. dbus_connection_open(): Memory growth. ** Summary changed: - uevent spam causes session upstart to consume massive amounts of memory on Ubuntu Touch + uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch Status in Upstart: New Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: New Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: New Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235649/+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 1235649] Re: uevent spam causes session upstart to consume massive amounts of memory on Ubuntu Touch
Persistent D-Bus connections are as expected (1 / bridge and 1 for unity-panel-service). Ephemeral D-Bus connections are being handled correctly and removed from the control_conns list. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes session upstart to consume massive amounts of memory on Ubuntu Touch Status in “linux” package in Ubuntu: Incomplete Status in “systemd” package in Ubuntu: New Status in “upstart” package in Ubuntu: Confirmed Status in “linux” source package in Saucy: Incomplete Status in “systemd” source package in Saucy: New Status in “upstart” source package in Saucy: Confirmed Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235649/+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 1235649] Re: uevent spam causes session upstart to consume massive amounts of memory on Ubuntu Touch
Still unclear why memory is being cached in Upstart address space, but I'm starting to think this might be a libdbus issue. What is triggering the memory rise though is unity-panel-service: stopping this from running results in no memory increase within the Session Init. ** Also affects: unity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes session upstart to consume massive amounts of memory on Ubuntu Touch Status in “linux” package in Ubuntu: Incomplete Status in “systemd” package in Ubuntu: New Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Confirmed Status in “linux” source package in Saucy: Incomplete Status in “systemd” source package in Saucy: New Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Confirmed Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235649/+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 1235649] Re: uevent spam causes session upstart to consume massive amounts of memory on Ubuntu Touch
Right - recall that I am testing on i386 as I don't have mako/maguro :) However, note that on Touch, the upstart code in unity8 (plugins/Unity/Indicators/indicatorsmanager.cpp) is almost identical to the upstart code in unity-panel-service (unity/services/panel- service.c). Is it possible to somehow disable the loading of /usr/lib/i386-linux- gnu/unity8/qml/Unity/Indicators/libIndicatorsQml.so in the unity8-private package on mako/maguro to see if that stops the memory bloat? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes session upstart to consume massive amounts of memory on Ubuntu Touch Status in “linux” package in Ubuntu: Incomplete Status in “systemd” package in Ubuntu: New Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Confirmed Status in “linux” source package in Saucy: Incomplete Status in “systemd” source package in Saucy: New Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Confirmed Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235649/+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 1235649] Re: uevent spam causes session upstart to consume massive amounts of memory on Ubuntu Touch
Re #41, interesting that unity-panel-service *is* installed on Touch image though :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes session upstart to consume massive amounts of memory on Ubuntu Touch Status in “linux” package in Ubuntu: Incomplete Status in “systemd” package in Ubuntu: New Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Confirmed Status in “linux” source package in Saucy: Incomplete Status in “systemd” source package in Saucy: New Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Confirmed Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235649/+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 1235649] Re: session upstart leaks massive amounts of memory on Ubuntu Touch
** Changed in: upstart (Ubuntu Saucy) Assignee: (unassigned) = James Hunt (jamesodhunt) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1235649 Title: session upstart leaks massive amounts of memory on Ubuntu Touch Status in “linux” package in Ubuntu: Confirmed Status in “upstart” package in Ubuntu: Confirmed Status in “linux” source package in Saucy: Confirmed Status in “upstart” source package in Saucy: Confirmed Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235649/+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 1235649] Re: session upstart leaks massive amounts of memory on Ubuntu Touch
Valgrinding the session init shows that most of the memory is correctly freed at quiesce time. ** Attachment added: valgrind session init consuming ~250MB (with suppressions) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235649/+attachment/3866119/+files/valgrind-250M.log.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1235649 Title: session upstart leaks massive amounts of memory on Ubuntu Touch Status in “linux” package in Ubuntu: Confirmed Status in “upstart” package in Ubuntu: Confirmed Status in “linux” source package in Saucy: Confirmed Status in “upstart” source package in Saucy: Confirmed Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235649/+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 1235649] Re: session upstart leaks massive amounts of memory on Ubuntu Touch
Valgrind run as: valgrind -v -v -v -v --show-reachable=yes --track-origins=yes --leak- check=full init --debug --user ** Attachment added: valgrind session init consuming ~500MB (no suppressions) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235649/+attachment/3866123/+files/valgrind-500M-no-suppressions.log.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1235649 Title: session upstart leaks massive amounts of memory on Ubuntu Touch Status in “linux” package in Ubuntu: Confirmed Status in “upstart” package in Ubuntu: Confirmed Status in “linux” source package in Saucy: Confirmed Status in “upstart” source package in Saucy: Confirmed Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235649/+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 1235649] Re: uevent spam causes session upstart to consume massive amounts of memory on Ubuntu Touch
The problem is triggered by init/control.c:control_emit_event_emitted(). It looks like Upstart itself is clearing up memory, but either dbus isn't, or upstart is missing a dbus unref call. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes session upstart to consume massive amounts of memory on Ubuntu Touch Status in “linux” package in Ubuntu: Incomplete Status in “systemd” package in Ubuntu: New Status in “upstart” package in Ubuntu: Confirmed Status in “linux” source package in Saucy: Incomplete Status in “systemd” source package in Saucy: New Status in “upstart” source package in Saucy: Confirmed Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235649/+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