[Bug 1690395] Re: CPU fan always on with kernel 4.10.0.20.22 (zesty) on a X1 Carbon 5th gen
Nevermind, closing. I can't reproduce this anymore, so it was probably not related to the kernel version. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690395 Title: CPU fan always on with kernel 4.10.0.20.22 (zesty) on a X1 Carbon 5th gen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690395] Re: CPU fan always on with kernel 4.10.0.20.22 (zesty) on a X1 Carbon 5th gen
** Attachment removed: "WifiSyslog.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690395/+attachment/4875693/+files/WifiSyslog.txt ** Attachment removed: "IwConfig.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690395/+attachment/4875683/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690395 Title: CPU fan always on with kernel 4.10.0.20.22 (zesty) on a X1 Carbon 5th gen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690395] Re: CPU fan always on with kernel 4.10.0.20.22 (zesty) on a X1 Carbon 5th gen
Here's the output of fwts fan: Results generated by fwts: Version V17.03.00 (2017-03-16 03:24:38). Some of this work - Copyright (c) 1999 - 2017, Intel Corp. All rights reserved. Some of this work - Copyright (c) 2010 - 2017, Canonical. Some of this work - Copyright (c) 2016 - 2017, IBM. Some of this work - Copyright (c) 2017, ARM Ltd. This test run on 12/05/17 at 08:27:40 on host Linux locrian 4.10.0-20-generic #22-Ubuntu SMP Thu Apr 20 09:22:42 UTC 2017 x86_64. Command: "fwts fan". Running tests: fan. fan: Simple fan tests. Test 1 of 2: Test fan status. Test how many fans there are in the system. Check for the current status of the fan(s). PASSED: Test 1, Fan cooling_device5 of type iwlwifi has max cooling state 19 and current cooling state 0. PASSED: Test 1, Fan cooling_device3 of type Processor has max cooling state 10 and current cooling state 0. PASSED: Test 1, Fan cooling_device1 of type Processor has max cooling state 10 and current cooling state 0. FAILED [MEDIUM] NoFanCurState: Test 1, Fan present but has no cur_state present. PASSED: Test 1, Fan cooling_device2 of type Processor has max cooling state 10 and current cooling state 0. PASSED: Test 1, Fan cooling_device0 of type Processor has max cooling state 10 and current cooling state 0. Test 2 of 2: Load system, check CPU fan status. Test how many fans there are in the system. Check for the current status of the fan(s). Loading CPUs for 20 seconds to try and get fan speeds to change. Fan cooling_device3 current state did not change from value 0 while CPUs were busy. Fan cooling_device1 current state did not change from value 0 while CPUs were busy. Fan cooling_device2 current state did not change from value 0 while CPUs were busy. Fan cooling_device0 current state did not change from value 0 while CPUs were busy. ADVICE: Did not detect any change in the CPU related thermal cooling device states. It could be that the devices are returning static information back to the driver and/or the fan speed is automatically being controlled by firmware using System Management Mode in which case the kernel interfaces being examined may not work anyway. 5 passed, 1 failed, 0 warning, 0 aborted, 0 skipped, 0 info only. 5 passed, 1 failed, 0 warning, 0 aborted, 0 skipped, 0 info only. Test Failure Summary Critical failures: NONE High failures: NONE Medium failures: 1 fan: Fan present but has no cur_state present. Low failures: NONE Other failures: NONE Test |Pass |Fail |Abort|Warn |Skip |Info | ---+-+-+-+-+-+-+ fan|5|1| | | | | ---+-+-+-+-+-+-+ Total: |5|1|0|0|0|0| ---+-+-+-+-+-+-+ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690395 Title: CPU fan always on with kernel 4.10.0.20.22 (zesty) on a X1 Carbon 5th gen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690395] [NEW] CPU fan always on with kernel 4.10.0.20.22 (zesty) on a X1 Carbon 5th gen
Public bug reported: Once the CPU fan is turned on, it never turns back down, even when things have already cooled down and CPU usage is low (<2%) for 5+ minutes. The same cannot be reproduced with the previous kernel version (4.10.0.19.21), on the same machine. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-20-generic 4.10.0-20.22 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fkung 2121 F pulseaudio CurrentDesktop: GNOME Date: Fri May 12 08:19:29 2017 HibernationDevice: RESUME=UUID=8e5a26ba-3ea3-4831-88ba-66803bdf9d45 InstallationDate: Installed on 2017-04-06 (35 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 138a:0097 Validity Sensors, Inc. Bus 001 Device 003: ID 04f2:b5ce Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HR000FUS ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-20-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-20-generic N/A linux-backports-modules-4.10.0-20-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-05-04 (7 days ago) dmi.bios.date: 12/26/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET21W (1.06 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HR000FUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1MET21W(1.06):bd12/26/2016:svnLENOVO:pn20HR000FUS:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HR000FUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20HR000FUS dmi.product.version: ThinkPad X1 Carbon 5th dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690395 Title: CPU fan always on with kernel 4.10.0.20.22 (zesty) on a X1 Carbon 5th gen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1475434] Re: ipvlan module causes kernel crashes (backport fixes from upstream)
I failed to mention that I also had linux-image-extra-3.19.0-26-generic and linux-headers-3.19.0-26 from vivid-proposed, but it is probably not relevant: $ uname -r 3.19.0-26-generic $ apt-cache policy linux-image-extra-3.19.0-26 linux-image-extra-3.19.0-26-generic: Installed: 3.19.0-26.27 Candidate: 3.19.0-26.27 Version table: *** 3.19.0-26.27 0 400 http://us.archive.ubuntu.com/ubuntu/ vivid-proposed/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy linux-image-3.19.0-26 linux-image-3.19.0-26-lowlatency: Installed: (none) Candidate: 3.19.0-26.27 Version table: 3.19.0-26.27 0 400 http://us.archive.ubuntu.com/ubuntu/ vivid-proposed/main amd64 Packages linux-image-3.19.0-26-generic: Installed: 3.19.0-26.27 Candidate: 3.19.0-26.27 Version table: *** 3.19.0-26.27 0 400 http://us.archive.ubuntu.com/ubuntu/ vivid-proposed/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy linux-headers-3.19.0-26 linux-headers-3.19.0-26: Installed: 3.19.0-26.27 Candidate: 3.19.0-26.27 Version table: *** 3.19.0-26.27 0 400 http://us.archive.ubuntu.com/ubuntu/ vivid-proposed/main amd64 Packages 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1475434 Title: ipvlan module causes kernel crashes (backport fixes from upstream) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1475434] Re: ipvlan module causes kernel crashes (backport fixes from upstream)
I tested linux-image-3.19.0-26-generic from vivid-proposed and it works as expected. I can't reproduce the kernel crashes with it. Now, I'd love to see a version available for trusty (in trusty- proposed?) as well, as linux-generic-lts-vivid. ** Tags removed: verification-needed-vivid ** Tags added: verification-done-vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1475434 Title: ipvlan module causes kernel crashes (backport fixes from upstream) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1475434] Re: ipvlan module causes kernel crashes (backport fixes from upstream)
We tested the test kernel and it worked as expected. We can not reproduce the kernel crashes anymore with it. Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1475434 Title: ipvlan module causes kernel crashes (backport fixes from upstream) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1475434] [NEW] ipvlan module causes kernel crashes (backport fixes from upstream)
Public bug reported: Kernel version 3.19, currently being used as the vivid LTS kernel, includes support for ipvlan. But at its current state it is unusable as simply removing an interface with an ip address attached will cause a kernel crash. The fix is already upstream: https://github.com/torvalds/linux/commit/27705f7085ce2e124fac4c280ce824962cc90bb6 Reproducing this is easy (requires a recent version of iproute2, with support for ipvlan, such as the one in debian/experimental): ip netns add ns0 ip link add link eth0 ipvl0 type ipvlan mode L3 ip link set dev ipvl0 netns ns0 ip netns exec ns0 bash ip link set dev ipvl0 up ip -4 addr add 192.168.0.10/24 dev ipvl0 ip link del dev ipvl0 The last line will cause a kernel crash, with a calltrace that looks like this: https://gist.github.com/fabiokung/b360cb2f3bdf2fb36c8b Can we get the fixes backported to the 3.19 LTS kernel from vivid? Ideally we would like to have the whole patchset backported: https://github.com/torvalds/linux/commit/d91e9015c78af1dc1f8ac4fdcf6118dbc2401668 and https://github.com/torvalds/linux/commit/8172ba51e257fdd353010cd7caaa37c8bc9eb44a ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Description changed: - Kernel version 3.19, currently in the vivid LTS kernel, includes support - for ipvlan. But at its current state it is almost unusable as simply - removing an interface with an ip address attached will cause a kernel - crash. The fix is already upstream: + Kernel version 3.19, currently being used an the vivid LTS kernel, + includes support for ipvlan. But at its current state it is unusable as + simply removing an interface with an ip address attached will cause a + kernel crash. The fix is already upstream: https://github.com/torvalds/linux/commit/27705f7085ce2e124fac4c280ce824962cc90bb6 Reproducing this is easy (requires a recent version of iproute2, with support for ipvlan, such as the one in debian/experimental): ip netns add ns0 ip link add link eth0 ipvl0 type ipvlan mode L3 ip link set dev ipvl0 netns ns0 ip netns exec ns0 bash ip link set dev ipvl0 up ip -4 addr add 192.168.0.10/24 dev ipvl0 ip link del dev ipvl0 The last line will cause a kernel crash, with a calltrace that looks like this: https://gist.github.com/fabiokung/b360cb2f3bdf2fb36c8b Can we get the fixes backported to the 3.19 LTS kernel from vivid? Ideally we would like to have the whole patchset backported: https://github.com/torvalds/linux/commit/d91e9015c78af1dc1f8ac4fdcf6118dbc2401668 and https://github.com/torvalds/linux/commit/8172ba51e257fdd353010cd7caaa37c8bc9eb44a -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1475434 Title: ipvlan module causes kernel crashes (backport fixes from upstream) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475434/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1475434] Re: ipvlan module causes kernel crashes (backport fixes from upstream)
Got the wrong package initially. ** Package changed: iproute2 (Ubuntu) = linux-meta-lts-vivid (Ubuntu) ** Description changed: - Kernel version 3.19, currently being used an the vivid LTS kernel, + Kernel version 3.19, currently being used as the vivid LTS kernel, includes support for ipvlan. But at its current state it is unusable as simply removing an interface with an ip address attached will cause a kernel crash. The fix is already upstream: https://github.com/torvalds/linux/commit/27705f7085ce2e124fac4c280ce824962cc90bb6 Reproducing this is easy (requires a recent version of iproute2, with support for ipvlan, such as the one in debian/experimental): ip netns add ns0 ip link add link eth0 ipvl0 type ipvlan mode L3 ip link set dev ipvl0 netns ns0 ip netns exec ns0 bash ip link set dev ipvl0 up ip -4 addr add 192.168.0.10/24 dev ipvl0 ip link del dev ipvl0 The last line will cause a kernel crash, with a calltrace that looks like this: https://gist.github.com/fabiokung/b360cb2f3bdf2fb36c8b Can we get the fixes backported to the 3.19 LTS kernel from vivid? Ideally we would like to have the whole patchset backported: https://github.com/torvalds/linux/commit/d91e9015c78af1dc1f8ac4fdcf6118dbc2401668 and https://github.com/torvalds/linux/commit/8172ba51e257fdd353010cd7caaa37c8bc9eb44a -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1475434 Title: ipvlan module causes kernel crashes (backport fixes from upstream) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1475434] Re: ipvlan module causes kernel crashes (backport fixes from upstream)
Got the wrong package initially. ** Package changed: iproute2 (Ubuntu) = linux-meta-lts-vivid (Ubuntu) ** Description changed: - Kernel version 3.19, currently being used an the vivid LTS kernel, + Kernel version 3.19, currently being used as the vivid LTS kernel, includes support for ipvlan. But at its current state it is unusable as simply removing an interface with an ip address attached will cause a kernel crash. The fix is already upstream: https://github.com/torvalds/linux/commit/27705f7085ce2e124fac4c280ce824962cc90bb6 Reproducing this is easy (requires a recent version of iproute2, with support for ipvlan, such as the one in debian/experimental): ip netns add ns0 ip link add link eth0 ipvl0 type ipvlan mode L3 ip link set dev ipvl0 netns ns0 ip netns exec ns0 bash ip link set dev ipvl0 up ip -4 addr add 192.168.0.10/24 dev ipvl0 ip link del dev ipvl0 The last line will cause a kernel crash, with a calltrace that looks like this: https://gist.github.com/fabiokung/b360cb2f3bdf2fb36c8b Can we get the fixes backported to the 3.19 LTS kernel from vivid? Ideally we would like to have the whole patchset backported: https://github.com/torvalds/linux/commit/d91e9015c78af1dc1f8ac4fdcf6118dbc2401668 and https://github.com/torvalds/linux/commit/8172ba51e257fdd353010cd7caaa37c8bc9eb44a -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1475434 Title: ipvlan module causes kernel crashes (backport fixes from upstream) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475434/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1475434] [NEW] ipvlan module causes kernel crashes (backport fixes from upstream)
Public bug reported: Kernel version 3.19, currently being used as the vivid LTS kernel, includes support for ipvlan. But at its current state it is unusable as simply removing an interface with an ip address attached will cause a kernel crash. The fix is already upstream: https://github.com/torvalds/linux/commit/27705f7085ce2e124fac4c280ce824962cc90bb6 Reproducing this is easy (requires a recent version of iproute2, with support for ipvlan, such as the one in debian/experimental): ip netns add ns0 ip link add link eth0 ipvl0 type ipvlan mode L3 ip link set dev ipvl0 netns ns0 ip netns exec ns0 bash ip link set dev ipvl0 up ip -4 addr add 192.168.0.10/24 dev ipvl0 ip link del dev ipvl0 The last line will cause a kernel crash, with a calltrace that looks like this: https://gist.github.com/fabiokung/b360cb2f3bdf2fb36c8b Can we get the fixes backported to the 3.19 LTS kernel from vivid? Ideally we would like to have the whole patchset backported: https://github.com/torvalds/linux/commit/d91e9015c78af1dc1f8ac4fdcf6118dbc2401668 and https://github.com/torvalds/linux/commit/8172ba51e257fdd353010cd7caaa37c8bc9eb44a ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Description changed: - Kernel version 3.19, currently in the vivid LTS kernel, includes support - for ipvlan. But at its current state it is almost unusable as simply - removing an interface with an ip address attached will cause a kernel - crash. The fix is already upstream: + Kernel version 3.19, currently being used an the vivid LTS kernel, + includes support for ipvlan. But at its current state it is unusable as + simply removing an interface with an ip address attached will cause a + kernel crash. The fix is already upstream: https://github.com/torvalds/linux/commit/27705f7085ce2e124fac4c280ce824962cc90bb6 Reproducing this is easy (requires a recent version of iproute2, with support for ipvlan, such as the one in debian/experimental): ip netns add ns0 ip link add link eth0 ipvl0 type ipvlan mode L3 ip link set dev ipvl0 netns ns0 ip netns exec ns0 bash ip link set dev ipvl0 up ip -4 addr add 192.168.0.10/24 dev ipvl0 ip link del dev ipvl0 The last line will cause a kernel crash, with a calltrace that looks like this: https://gist.github.com/fabiokung/b360cb2f3bdf2fb36c8b Can we get the fixes backported to the 3.19 LTS kernel from vivid? Ideally we would like to have the whole patchset backported: https://github.com/torvalds/linux/commit/d91e9015c78af1dc1f8ac4fdcf6118dbc2401668 and https://github.com/torvalds/linux/commit/8172ba51e257fdd353010cd7caaa37c8bc9eb44a -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1475434 Title: ipvlan module causes kernel crashes (backport fixes from upstream) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448800] Re: Please update iproute2 to the latest version
It is worth mentioning that wily currently does not seem to include a version of iproute2 with support for ipvlan either. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448800 Title: Please update iproute2 to the latest version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1448800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448800] Re: Please update iproute2 to the latest version
It is worth mentioning that wily currently does not seem to include a version of iproute2 with support for ipvlan either. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1448800 Title: Please update iproute2 to the latest version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1448800/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1172919] Re: inet_diag and user namespaces on Lucid
Edit: fixed the lkml link (https://lkml.org/lkml/2012/8/13/525) ** Description changed: Tracking a problem with http://raindrops.bogomips.org/ running in LXC containers, I noticed that it fails only when the netlink calls happen inside a different net namespace. Apparently it has been already fixed in the upstream 2.6 kernel: - https://lkml.org/lkml/2012/8/13/408 + https://lkml.org/lkml/2012/8/13/525 Please consider applying the fix above in the linux-ec2 branch as well. I just confirmed that the lastest available version for lucid as of today (2.6.32-351.64) does not include the fix. Thanks, Fabio -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1172919 Title: inet_diag and user namespaces on Lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-ec2/+bug/1172919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1172919] [NEW] inet_diag and user namespaces on Lucid
Public bug reported: Tracking a problem with http://raindrops.bogomips.org/ running in LXC containers, I noticed that it fails only when the netlink calls happen inside a different net namespace. Apparently it has been already fixed in the upstream 2.6 kernel: https://lkml.org/lkml/2012/8/13/408 Please consider applying the fix above in the linux-ec2 branch as well. I just confirmed that the lastest available version for lucid as of today (2.6.32-351.64) does not include the fix. Thanks, Fabio ** Affects: linux-ec2 (Ubuntu) Importance: Undecided Status: New ** Tags: inet-diag namespaces netlink netns userns -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1172919 Title: inet_diag and user namespaces on Lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-ec2/+bug/1172919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1078408] Re: Upgrading in chroot fails as postinst calls invoke-rc.d
I've also been hit by this bug while debootstrap'ing a precise chroot image from a lucid box with: debootstrap --arch amd64 --variant=buildd \ --components=main,universe,precise-updates,precise-security \ --include ubuntu-standard,ubuntu-minimal,linux-image-virtual,ssh,git,ruby1.9.3 \ precise /tmp/root/ http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ `apt-get -y upgrade` fails there for the same reason reported here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1078408 Title: Upgrading in chroot fails as postinst calls invoke-rc.d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1078408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 851723] Re: dpkg aborted with malloc failed (-1541383818 bytes): Cannot allocate memory message
The problem is that when you do need to install big deb files, there is not any viable alternative. I need to install a 600Mb debs in machines with only 512MB memory available. +1 to apply the patches for Lucid too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/851723 Title: dpkg aborted with malloc failed (-1541383818 bytes): Cannot allocate memory message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/851723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 929941] Re: Kernel deadlock in scheduler on multiple EC2 instance types
We started with 30 instances running with the -proposed ec2 kernel, in our production environment. We plan to gradually boot more and update this ticket once we collect enough instance hours to be confident that this bug is not present in that version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/929941 Title: Kernel deadlock in scheduler on multiple EC2 instance types To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-ec2/+bug/929941/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 929941] Re: Kernel deadlock in scheduler on multiple EC2 instance types
We are very confident that this bug is not present in the v1 kernel, as we have been only running instances with that kernel for some months now, and we have not seen these issues anymore. Me and noav were some of the original reporters of this bug. We can help testing the kernel currently in -proposed, but as others have already commented, one week would not be enough to collect enough instance hours. Two weeks would give us much more confidence. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/929941 Title: Kernel deadlock in scheduler on multiple EC2 instance types To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-ec2/+bug/929941/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
