[Bug 790863] Re: Unable to start lxc container after update to 2.6.32-32
This bug was fixed in the package linux - 2.6.32-38.83 --- linux (2.6.32-38.83) lucid-proposed; urgency=low [Herton R. Krzesinski] * Release Tracking Bug - LP: #911405 [ Upstream Kernel Changes ] * Revert clockevents: Set noop handler in clockevents_exchange_device() - LP: #911392 * Linux 2.6.32.52 - LP: #911392 linux (2.6.32-38.82) lucid-proposed; urgency=low [Herton R. Krzesinski] * Release Tracking Bug - LP: #910906 [ Tetsuo Handa ] * SAUCE: netns: Add quota for number of NET_NS instances. [ Tim Gardner ] * [Config] CONFIG_NET_NS=y - LP: #790863 [ Upstream Kernel Changes ] * Revert core: Fix memory leak/corruption on VLAN GRO_DROP, CVE-2011-1576 * hfs: fix hfs_find_init() sb-ext_tree NULL ptr oops, CVE-2011-2203 - LP: #899466 - CVE-2011-2203 * net: ipv4: relax AF_INET check in bind() - LP: #900396 * KEYS: Fix a NULL pointer deref in the user-defined key type, CVE-2011-4110 - LP: #894369 - CVE-2011-4110 * i2c-algo-bit: Generate correct i2c address sequence for 10-bit target - LP: #902317 * eCryptfs: Extend array bounds for all filename chars - LP: #902317 * PCI hotplug: shpchp: don't blindly claim non-AMD 0x7450 device IDs - LP: #902317 * ARM: 7161/1: errata: no automatic store buffer drain - LP: #902317 * ALSA: lx6464es - fix device communication via command bus - LP: #902317 * SUNRPC: Ensure we return EAGAIN in xs_nospace if congestion is cleared - LP: #902317 * timekeeping: add arch_offset hook to ktime_get functions - LP: #902317 * p54spi: Add missing spin_lock_init - LP: #902317 * p54spi: Fix workqueue deadlock - LP: #902317 * nl80211: fix MAC address validation - LP: #902317 * gro: reset vlan_tci on reuse - LP: #902317 * staging: usbip: bugfix for deadlock - LP: #902317 * staging: comedi: fix oops for USB DAQ devices. - LP: #902317 * Staging: comedi: fix signal handling in read and write - LP: #902317 * USB: whci-hcd: fix endian conversion in qset_clear() - LP: #902317 * usb: ftdi_sio: add PID for Propox ISPcable III - LP: #902317 * usb: option: add SIMCom SIM5218 - LP: #902317 * USB: usb-storage: unusual_devs entry for Kingston DT 101 G2 - LP: #902317 * SCSI: scsi_lib: fix potential NULL dereference - LP: #902317 * SCSI: Silencing 'killing requests for dead queue' - LP: #902317 * cifs: fix cifs stable patch cifs-fix-oplock-break-handling-try-2.patch - LP: #902317 * sched, x86: Avoid unnecessary overflow in sched_clock - LP: #902317 * x86/mpparse: Account for bus types other than ISA and PCI - LP: #902317 * oprofile, x86: Fix crash when unloading module (nmi timer mode) - LP: #902317 * genirq: Fix race condition when stopping the irq thread - LP: #902317 * tick-broadcast: Stop active broadcast device when replacing it - LP: #902317 * clockevents: Set noop handler in clockevents_exchange_device() - LP: #902317 * Linux 2.6.32.50 - LP: #902317 * nfsd4: permit read opens of executable-only files - LP: #833300 * ipv6: Allow inet6_dump_addr() to handle more than 64 addresses - LP: #863394 * ALSA: sis7019 - give slow codecs more time to reset - LP: #907774 * ALSA: hda/realtek - Fix Oops in alc_mux_select() - LP: #907774 * ARM: davinci: dm646x evm: wrong register used in setup_vpif_input_channel_mode - LP: #907774 * oprofile: Free potentially owned tasks in case of errors - LP: #907774 * oprofile: Fix locking dependency in sync_start() - LP: #907774 * percpu: fix chunk range calculation - LP: #907774 * xfrm: Fix key lengths for rfc3686(ctr(aes)) - LP: #907774 * linux/log2.h: Fix rounddown_pow_of_two(1) - LP: #907774 * jbd/jbd2: validate sb-s_first in journal_get_superblock() - LP: #907774 * hfs: fix hfs_find_init() sb-ext_tree NULL ptr oops - LP: #907774 * export __get_user_pages_fast() function - LP: #907774 * oprofile, x86: Fix nmi-unsafe callgraph support - LP: #907774 * oprofile, x86: Fix crash when unloading module (timer mode) - LP: #907774 * ext4: avoid hangs in ext4_da_should_update_i_disksize() - LP: #907774 * USB: cdc-acm: add IDs for Motorola H24 HSPA USB module. - LP: #907774 * Linux 2.6.32.51 - LP: #907774 -- Herton Ronaldo Krzesinski herton.krzesin...@canonical.com Tue, 03 Jan 2012 16:51:53 -0200 ** Changed in: linux (Ubuntu Lucid) Status: Fix Committed = Fix Released ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2011-1576 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2011-2203 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2011-4110 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/790863 Title: Unable to start lxc container after
[Bug 790863] Re: Unable to start lxc container after update to 2.6.32-32
** Branch linked: lp:ubuntu/lucid-proposed/linux-ec2 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/790863 Title: Unable to start lxc container after update to 2.6.32-32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/790863/+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 790863] Re: Unable to start lxc container after update to 2.6.32-32
** Branch linked: lp:ubuntu/maverick-proposed/linux-mvl-dove -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/790863 Title: Unable to start lxc container after update to 2.6.32-32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/790863/+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 790863] Re: Unable to start lxc container after update to 2.6.32-32
** Changed in: linux (Ubuntu Lucid) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/790863 Title: Unable to start lxc container after update to 2.6.32-32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/790863/+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 790863] Re: Unable to start lxc container after update to 2.6.32-32
I changed by error the fix from comitted to released ... Sorry ! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/790863 Title: Unable to start lxc container after update to 2.6.32-32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/790863/+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 790863] Re: Unable to start lxc container after update to 2.6.32-32
This bug is awaiting verification that the kernel in -proposed solves the problem (2.6.32-38.83). Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lucid' to 'verification-done-lucid'. If verification is not done by one week from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Changed in: linux (Ubuntu Lucid) Status: Fix Released = Fix Committed ** Tags added: verification-needed-lucid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/790863 Title: Unable to start lxc container after update to 2.6.32-32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/790863/+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 790863] Re: Unable to start lxc container after update to 2.6.32-32
** Tags removed: kernel-key needs-upstream-testing -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/790863 Title: Unable to start lxc container after update to 2.6.32-32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/790863/+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 790863] Re: Unable to start lxc container after update to 2.6.32-32
We need to get this kernel tested so that it can be included on the next Lucid point release DVD. Please test if you can. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/790863 Title: Unable to start lxc container after update to 2.6.32-32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/790863/+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 790863] Re: Unable to start lxc container after update to 2.6.32-32
Verified. Tag updated to verification-done-lucid ** Tags removed: verification-needed-lucid ** Tags added: verification-done-lucid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/790863 Title: Unable to start lxc container after update to 2.6.32-32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/790863/+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 790863] Re: Unable to start lxc container after update to 2.6.32-32
The final patch has a non-zero initial value for max_netns_count, plus it prints a warning once when the number of allocated network name spaces exceeds max_netns_count. ** Changed in: linux (Ubuntu Lucid) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/790863 Title: Unable to start lxc container after update to 2.6.32-32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/790863/+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 790863] Re: Unable to start lxc container after update to 2.6.32-32
** Patch added: (V2) UBUNTU: SAUCE: netns: Add quota for number of NET_NS instances. https://bugs.launchpad.net/ubuntu/lucid/+source/linux/+bug/790863/+attachment/2639885/+files/0001-UBUNTU-SAUCE-netns-Add-quota-for-number-of-NET_NS-in.patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/790863 Title: Unable to start lxc container after update to 2.6.32-32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/790863/+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 790863] Re: Unable to start lxc container after update to 2.6.32-32
So far so good. My container is running fine along with everything else. I'll keep running this build and report if I see any issues, but I think it's good. Let me know if there's anything else I need to test. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/790863 Title: Unable to start lxc container after update to 2.6.32-32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/790863/+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 790863] Re: Unable to start lxc container after update to 2.6.32-32
Where have all my testers gone? This patch isn't going in without some feedback. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/790863 Title: Unable to start lxc container after update to 2.6.32-32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/790863/+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 790863] Re: Unable to start lxc container after update to 2.6.32-32
Ok, my containers do start up again and seem to behave ok. I'm happy to test this for a more extended period of time. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/790863 Title: Unable to start lxc container after update to 2.6.32-32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/790863/+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 790863] Re: Unable to start lxc container after update to 2.6.32-32
Where have all my testers gone? This patch isn't going in without some feedback. Hmm.. Half a year... To Debian I guess -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/790863 Title: Unable to start lxc container after update to 2.6.32-32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/790863/+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 790863] Re: Unable to start lxc container after update to 2.6.32-32
Tim, Thanks for getting a test version out! I've been swamped the last few weeks but I can test it out this weekend and post my results. I also admit I thought this was a VSFTP patch (from Jamie's note) when I skimmed it the first time, not a new kernel. Oops :) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/790863 Title: Unable to start lxc container after update to 2.6.32-32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/790863/+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 790863] Re: Unable to start lxc container after update to 2.6.32-32
vsftpd (2.2.2-3ubuntu6.3) lucid-security; urgency=low * SECURITY UPDATE: remote DoS via network namespaces - debian/patches/12-CVE-2011-2189.patch: only use network namespaces on 2.6.36 and higher kernels - patch based on Debian's patch - CVE-2011-2189 ** Changed in: vsftpd (Ubuntu Lucid) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/790863 Title: Unable to start lxc container after update to 2.6.32-32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/790863/+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 790863] Re: Unable to start lxc container after update to 2.6.32-32
Test kernels at http://kernel.ubuntu.com/~rtg/790863.1 Corresponding sources at git://kernel.ubuntu.com/rtg/ubuntu-lucid.git config-ns-790863, tag 790863.1 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/790863 Title: Unable to start lxc container after update to 2.6.32-32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/790863/+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 790863] Re: Unable to start lxc container after update to 2.6.32-32
Don't forget to do something like: echo 4096 | sudo tee /proc/sys/net/core/netns_max before attempting to fork with CLONE_NEWNET. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/790863 Title: Unable to start lxc container after update to 2.6.32-32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/790863/+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 790863] Re: Unable to start lxc container after update to 2.6.32-32
This parameter must be set before LXC containers starts? It can be setted via sysctl.conf? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/790863 Title: Unable to start lxc container after update to 2.6.32-32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/790863/+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 790863] Re: Unable to start lxc container after update to 2.6.32-32
vsftpd needs this patch from Debian's 10-remote-dos.patch 2.3.4-1. vsftpd in precise already has this. ** Also affects: vsftpd (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: vsftpd (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Critical Status: Confirmed ** Also affects: vsftpd (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Lucid) Status: New = Confirmed ** Changed in: linux (Ubuntu Lucid) Importance: Undecided = Critical ** Changed in: linux (Ubuntu Precise) Status: Confirmed = Fix Released ** Changed in: linux (Ubuntu Lucid) Importance: Critical = High ** Changed in: vsftpd (Ubuntu Lucid) Status: New = Triaged ** Changed in: vsftpd (Ubuntu Lucid) Importance: Undecided = High ** Changed in: linux (Ubuntu Precise) Importance: Critical = High ** Changed in: vsftpd (Ubuntu Precise) Status: New = Fix Released ** Changed in: vsftpd (Ubuntu Precise) Importance: Undecided = High ** Changed in: vsftpd (Ubuntu Lucid) Assignee: (unassigned) = Jamie Strandboge (jdstrand) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/790863 Title: Unable to start lxc container after update to 2.6.32-32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/790863/+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 790863] Re: Unable to start lxc container after update to 2.6.32-32
** Changed in: vsftpd (Ubuntu Lucid) Status: Triaged = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/790863 Title: Unable to start lxc container after update to 2.6.32-32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/790863/+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 790863] Re: Unable to start lxc container after update to 2.6.32-32
Tetsuo - I'll forward your patch for review on the Ubuntu kernel team mailling list. If accepted, then I'm OK with restoring CONFIG_NET_NS. The most common OOM cause (vsftpd) will have been ameliorated with the application of the patch for CVE-2011-2189 , and your patch should prohibit fatal OOM conditions. ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2011-2189 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/790863 Title: Unable to start lxc container after update to 2.6.32-32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/790863/+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 790863] Re: Unable to start lxc container after update to 2.6.32-32
** Changed in: linux (Ubuntu Lucid) Assignee: (unassigned) = Tim Gardner (timg-tpi) ** Changed in: linux (Ubuntu Lucid) Status: Confirmed = In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/790863 Title: Unable to start lxc container after update to 2.6.32-32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/790863/+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
