[Bug 1868551] Re: Screen freezes : NULL pointer dereference i915_active_acquire since Linux 5.4
I did not manage to compile the kernel the Ubuntu way https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel Is this doc still relevant for Linux 5.4 and 20.04 / Focal? I included the patch I ported to the latest version of ubuntu-focal git clone git://kernel.ubuntu.com/ubuntu/ubuntu-focal.git ** Patch added: "ubuntu-focal-1868551-i915_active_acquire.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868551/+attachment/5341878/+files/ubuntu-focal-1868551-i915_active_acquire.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868551 Title: Screen freezes : NULL pointer dereference i915_active_acquire since Linux 5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868551] Re: Screen freezes : NULL pointer dereference i915_active_acquire since Linux 5.4
I managed to build, install and boot the Linux Kernel 5.4 patched with the above patch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868551 Title: Screen freezes : NULL pointer dereference i915_active_acquire since Linux 5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868551] Re: Screen freezes : NULL pointer dereference i915_active_acquire since Linux 5.4
** Attachment removed: "WifiSyslog.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868551/+attachment/5340470/+files/WifiSyslog.txt ** Attachment removed: "RfKill.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868551/+attachment/5340468/+files/RfKill.txt ** Attachment removed: "AlsaInfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868551/+attachment/5340454/+files/AlsaInfo.txt ** Attachment removed: "CRDA.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868551/+attachment/5340455/+files/CRDA.txt ** Attachment removed: "IwConfig.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868551/+attachment/5340457/+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/1868551 Title: Screen freezes : NULL pointer dereference i915_active_acquire since Linux 5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868551] Re: Screen freezes : NULL pointer dereference i915_active_acquire since Linux 5.4
Q: Is there an upstream commit? A: Not that I am aware of https://gitlab.freedesktop.org/drm/intel/issues/827 A month ago: Hi, when will this make it's way into Kernel 5.4? -- The Boy from the MAD show ;-) You can check if you had the same type crash of your Ubuntu 20.04 (soon LTS) zgrep -h i915_active_acquire /var/log/kern.log* RIP: 0010:i915_active_acquire+0xe/0x80 [i915] I had about one or two crash / freeze of Ubuntu 20.04 per week on my Dell XPS 13 connected to an external monitor. Initially, I thought it was related to the instability of the hardware itself but at the end it seems to be an Intel i915 graphics kernel driver bug or regression on Linux Kernel 5.4. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868551 Title: Screen freezes : NULL pointer dereference i915_active_acquire since Linux 5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868551] Re: Screen freezes : NULL pointer dereference i915_active_acquire since Linux 5.4
zgrep -h i915_active_acquire /var/log/kern.log* kern.log* | cut -d ' ' -f1-3,5,9- ** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868551/+attachment/5342403/+files/kern.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868551 Title: Screen freezes : NULL pointer dereference i915_active_acquire since Linux 5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868551] Re: Screen freezes : NULL pointer dereference i915_active_acquire since Linux 5.4
Seems to be fixed in the latest 5.5
http://kobi.wang/v5.x/ChangeLog-5.5
drm/i915: Hold reference to intel_frontbuffer as we track activity
Since obj->frontbuffer is no longer protected by the struct_mutex, as we
are processing the execbuf, it may be removed. Mark the
intel_frontbuffer as rcu protected, and so acquire a reference to
the struct as we track activity upon it.
Closes: https://gitlab.freedesktop.org/drm/intel/issues/827
Fixes: 8e7cb1799b4f ("drm/i915: Extract intel_frontbuffer active tracking")
Signed-off-by: Chris Wilson
Link:
https://patchwork.freedesktop.org/patch/msgid/20191218104043.3539458-1-ch...@chris-wilson.co.uk
(cherry picked from commit da42104f589d979bbe402703fd836cec60befae1)
I am not sure that is a good idea to ship Ubuntu 20.04 LTS with Linux
Kernel 5.4 branch unless you backport 5.5 patches as many people rely on
bult-in Intel GPU in their workstation and the Intel graphics kernel
driver is not very stable
https://linuxreviews.org/Linux_Kernel_5.5_Will_Not_Fix_The_Frequent_Intel_GPU_Hangs_In_Recent_Kernels
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949369
https://bugzilla.redhat.com/show_bug.cgi?id=1805278
https://bugs.archlinux.org/task/65392
Google "i915_active_acquire"+"i915_vma_move_to_active"
Google link:https://gitlab.freedesktop.org/drm/intel/issues/827
commit e85ade1f50aae464ce196672faa7a099fd1721ed
Author: Chris Wilson
Date: Wed Dec 18 10:40:43 2019 +
** Bug watch added: Debian Bug tracker #949369
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949369
** Bug watch added: Red Hat Bugzilla #1805278
https://bugzilla.redhat.com/show_bug.cgi?id=1805278
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868551
Title:
Screen freezes : NULL pointer dereference i915_active_acquire since
Linux 5.4
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868551/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868551] Re: Screen freezes : NULL pointer dereference i915_active_acquire since Linux 5.4
With the above patch, I still have the screen freeze but without Kernel oops.
I will compile and my own Linux Kernel 4.15 (18.04 LTS) for Ubuntu 20.04 (soon
LTS) as
Intel Graphics i915 is unusable on my Dell XPS 13 connected to external
screen and XFCE4
i915 :00:02.0: GPU HANG: ecode 9:1:0x, hang on rcs0
i915 :00:02.0: Resetting rcs0 for hang on rcs0
[drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out:
{request: 0001, RESET_CTL: 0001}
i915 :00:02.0: Resetting chip for hang on rcs0
[drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out:
{request: 0001, RESET_CTL: 0001}
[drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out:
{request: 0001, RESET_CTL: 0001}
Asynchronous wait on fence i915:xfwm4[1901]:57922 timed out
(hint:intel_atomic_commit_ready+0x0/0x54 [i915])
Asynchronous wait on fence i915:xfwm4[1901]:57922 timed out
(hint:intel_atomic_commit_ready+0x0/0x54 [i915])
i915 :00:02.0: Resetting rcs0 for hang on rcs0
i915 :00:02.0: Resetting rcs0 for hang on rcs0
...
i915 :00:02.0: GPU recovery timed out, cancelling all in-flight rendering.
i915 :00:02.0: Resetting chip for hang on rcs0
i915 :00:02.0: Resetting rcs0 for hang on rcs0
i915 :00:02.0: Resetting rcs0 for hang on rcs0
Asynchronous wait on fence i915:xfwm4[1901]:57926 timed out
(hint:intel_atomic_commit_ready+0x0/0x54 [i915])
Asynchronous wait on fence i915:xfwm4[1901]:57926 timed out
(hint:intel_atomic_commit_ready+0x0/0x54 [i915])
i915 :00:02.0: Resetting rcs0 for hang on rcs0
i915 :00:02.0: Resetting rcs0 for hang on rcs0
...
i915 :00:02.0: GPU recovery timed out, cancelling all in-flight rendering.
i915 :00:02.0: Resetting chip for hang on rcs0
i915 :00:02.0: Resetting rcs0 for hang on rcs0
[drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out:
{request: 0001, RESET_CTL: 0001}
i915 :00:02.0: Resetting chip for hang on rcs0
[drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out:
{request: 0001, RESET_CTL: 0001}
[drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out:
{request: 0001, RESET_CTL: 0001}
i915 :00:02.0: Resetting rcs0 for hang on rcs0
i915 :00:02.0: Resetting rcs0 for hang on rcs0
Asynchronous wait on fence i915:xfwm4[1901]:5792a timed out
(hint:intel_atomic_commit_ready+0x0/0x54 [i915])
Asynchronous wait on fence i915:xfwm4[1901]:5792a timed out
(hint:intel_atomic_commit_ready+0x0/0x54 [i915])
i915 :00:02.0: Resetting rcs0 for hang on rcs0
i915 :00:02.0: Resetting rcs0 for hang on rcs0
...
i915 :00:02.0: GPU recovery timed out, cancelling all in-flight rendering.
i915 :00:02.0: Resetting chip for hang on rcs0
i915 :00:02.0: Resetting rcs0 for hang on rcs0
...
Asynchronous wait on fence i915:xfwm4[1901]:5792e timed out
(hint:intel_atomic_commit_ready+0x0/0x54 [i915])
Asynchronous wait on fence i915:xfwm4[1901]:5792e timed out
(hint:intel_atomic_commit_ready+0x0/0x54 [i915])
i915 :00:02.0: Resetting rcs0 for hang on rcs0
i915 :00:02.0: Resetting rcs0 for hang on rcs0
...
i915 :00:02.0: GPU recovery timed out, cancelling all in-flight rendering.
i915 :00:02.0: Resetting chip for hang on rcs0
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
i915 :00:02.0: Resetting rcs0 for hang on rcs0
i915 :00:02.0: Resetting rcs0 for hang on rcs0
Asynchronous wait on fence i915:xfwm4[1901]:57932 timed out
(hint:intel_atomic_commit_ready+0x0/0x54 [i915])
Asynchronous wait on fence i915:xfwm4[1901]:57932 timed out
(hint:intel_atomic_commit_ready+0x0/0x54 [i915])
i915 :00:02.0: Resetting rcs0 for hang on rcs0
i915 :00:02.0: Resetting rcs0 for hang on rcs0
...
i915 :00:02.0: Resetting rcs0 for hang on rcs0
i915 :00:02.0: GPU recovery timed out, cancelling all in-flight rendering.
i915 :00:02.0: Resetting chip for hang on rcs0
i915 :00:02.0: GPU recovery timed out, cancelling all in-flight rendering.
i915 :00:02.0: Resetting chip for hang on rcs0
i915 :00:02.0: Resetting rcs0 for hang on rcs0
Asynchronous wait on fence i915:xfwm4[1901]:57936 timed out
(hint:intel_atomic_commit_ready+0x0/0x54 [i915])
Asynchronous wait on fence i915:xfwm4[1901]:57936 timed out
(hint:intel_atomic_commit_ready+0x0/0x54 [i915])
i915 :00:02.0: Resetting rcs0 for hang on rcs0
i915 :00:02.0: Resetting rcs0 for hang on rcs0
...
i915 :00:02.0: GPU recovery timed out, cancelling all in-flight rendering.
i915 :00:02.0: Resetting chip for hang on rcs0
i915 :00:02.0: Resetting rcs0 for hang on rcs0
i915 :00:02.0: Resetting rcs0 for hang on rcs0
Asynchronous wait on fence i915:xfwm4[1901]:57938 timed out
(hint:intel_atomic_commit_ready+0x0/0x54 [i915])
Asynchronous wait on fence i915:xfwm4[1901]:57938 timed out
(hint:intel_atomic_commit_ready+0x0/0x54 [i915])
i915 :00:02.0: Rese
[Bug 1868551] Re: Screen freezes : NULL pointer dereference i915_active_acquire since Linux 5.4
I am testing with Linux Kernel 5.5.13-050513-generic from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5.13/ as older kernels (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954817#17 ** Bug watch added: Debian Bug tracker #954817 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954817 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868551 Title: Screen freezes : NULL pointer dereference i915_active_acquire since Linux 5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868551] Re: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire
** Summary changed: - Screen freezes : NULL pointer dereference i915_active_acquire since Linux 5.4 + Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868551 Title: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868551] Re: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire
So far no crash, freeze of any kind with Linux 5.5.13 compared to the unstability of Ubuntu 20.04 with Linux 5.4 on Dell XPS 13 with 10th Generation Intel Core i7-10510U CPU (Comet Lake) I guess the patches are part of Linux v5.5.12 and later https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5.12/CHANGES Chris Wilson (1): drm/i915/execlists: Track active elements during dequeue Matt Roper (1): drm/i915: Handle all MCR ranges Caz Yokoyama (1): Revert "drm/i915/tgl: Add extra hdc flush workaround" Maybe Canonical should backport those patches to 5.4 or switch to 5.5 branch before Ubuntu 20.04 General Availability? https://lkml.org/lkml/2020/3/22/419 https://lkml.org/lkml/2020/3/19/1779 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868551 Title: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868551] Re: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire
Linux Kernel 5.5.x (>5.5.12) is working fine ** Changed in: linux (Ubuntu) Status: Confirmed => New ** Information type changed from Public to Private -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868551 Title: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1701068] Re: motd.ubuntu.com currently shows media item (HBO's Silicon Valley using Ubuntu)
motd-news is part base-files so it cannot be removed from Ubuntu Desktop, Server or Core. if you need to report a bug use https://bugs.launchpad.net/ubuntu/+source/base-files/+filebug On my point of view, motd-news is a Telemetry tool hidden in a Message of the Day (MOTD) serving Ads for Canonical products (kubernetes, snap, lxd, etc.). On top of that it represents a risk of security and privacy because curl is launched as root and your IP and private information such as CPU model, CPU usage (idle time), uptime, Kernel version are transmitted without consent (and regardless of any kind of approval) to Canonical. https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1701068 Title: motd.ubuntu.com currently shows media item (HBO's Silicon Valley using Ubuntu) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1701068/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
** Attachment added: "motd.ubuntu.com current Advertising for Canonical Products" https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+attachment/5389475/+files/ubuntu-desktop-2004-translate.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
** Attachment added: "motd-news ENABLED by default with telemetry every 12h Without Consent" https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+attachment/5389471/+files/ubuntu-desktop-2004-terminal2.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
** Attachment added: "Privacy has not opt-out for motd-news hidden telemetry in User-Agent" https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+attachment/5389470/+files/ubuntu-desktop-2004-privacy.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
** Attachment added: "Trying to remove motd-news via base-files will kill Ubuntu" https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+attachment/5389481/+files/ubuntu-desktop-2004-system-failure2.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
** Attachment added: "No, don't send system info NOT RESPECTED BY MOTD-NEWS" https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+attachment/5389468/+files/ubuntu-desktop-2004-optout.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
** Attachment added: "motd-news exfiltrate system information via User-Agent and IP Address every 12 hours Without Consent" https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+attachment/5389482/+files/ubuntu-desktop-2004-motd-news.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
** Attachment added: "Legal Notice DOES NOT COVER "motd-news" sending IP address, Uptime, Idle time every 12h motd-news.service started during installation Ubuntu Desktop 20.04 Without Consent" https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+attachment/5389469/+files/ubuntu-desktop-2004-legal.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
** Attachment added: "Sample motd.ubuntu.com Ads from 2020" https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+attachment/5389477/+files/ubuntu-desktop-2004-waybackmachine2.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
** Attachment added: "motd.ubuntu.com is up since 2017" https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+attachment/5389476/+files/ubuntu-desktop-2004-waybackmachine.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
** Attachment added: "Sample motd.ubuntu.com Ads from 2017" https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+attachment/5389478/+files/ubuntu-desktop-2004-waybackmachine3.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
** Attachment added: "motd-news is unremovable" https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+attachment/5389480/+files/ubuntu-desktop-2004-system-failure1.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
** Attachment added: "Sample motd.ubuntu.com Ads from 2019" https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+attachment/5389479/+files/ubuntu-desktop-2004-waybackmachine4.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
** Attachment added: "motd.ubuntu.com hosted in the Amazon EC2 cloud in Dublin, Leinster, Ireland" https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+attachment/5389474/+files/ubuntu-desktop-2004-terminal4.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
No updates from Canonical's legal departement "A picture is worth a thousand words" ** Attachment added: "motd-news.service started during installation Ubuntu Desktop 20.04 Without Consent" https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+attachment/5389467/+files/ubuntu-desktop-2004.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
** Attachment added: "motd-news force to run via motd-news.service and motd-news.timer" https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+attachment/5389472/+files/ubuntu-desktop-2004-terminal3.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
https://news.softpedia.com/news/canonical-under-fire-for-putting-ads-in-the-ubuntu-motd-530372.shtml Article like "Canonical Under Fire for Putting Ads in the Ubuntu MOTD" miss the point that motd-news is not only displaying Advertising in the login prompt but it a Privacy Nightmare because it has an hidden Telemetry feature which is enabled by default Without Consent and leak IP Address, System critical informations (Kernel Version, Uptime, CPU Vendor, CPU Model, Idle Time, Uptime) every 12 hours via User-Agent from curl on all Ubuntu Desktop and Ubuntu Server including the current version of Ubuntu. On top of that, motd-news is also a security nightmare as it runs curl as root which can be exploited to gain root on any servers, laptops etc. I recommend that all Ubuntu users open a Terminal and execute the following sudo sed -i -r 's/(ENABLED)=.+/\1=0/' /etc/default/motd-news sudo apt-get -qq -y purge curl N.B. curl is not installed if you explicitly select Ubuntu Minimal during the installation of Ubuntu Desktop so motd-news cannot contact motd.ubuntu.com without curl even if ENABLED=1 by default GDPR : EU's General Data Protection Regulation since daily reporting of computer's infos are proceeded without the user's consent. Cf. GDPR application comments [https://gdpr.eu/eu-gdpr-personal-data/], in particular with respect to Recital 30 [https://gdpr.eu/recital-30 -online-identifiers-for-profiling-and-identification/] Internet protocol (IP) addresses; information that is related to an individual’s tools, applications, or devices, like their computer. Canonical Ltd. has handled my personal information without concent. By collecting twice a day the following informations: - The public IP address where Ubuntu system is used (part of the log of the HTTPS server) - Date / Time when collected (part of the log of the HTTPS server) - Harware info such as CPU Vendor and Model (via /proc/cpuinfo) - The distribution version (via /etc/lsb-release) - The operating system (via uname -o) - The Linux kernel release (via uname -r) - The computer architecture aka machine hardware name (via uname -m) - Cloud Hosting: cloud identifier such as aws, gce, azure, lxd (via cloud-id part of cloud-init) - Total number of seconds the system has been up (via /proc/uptime) - The sum of how much time each core has spent idle in seconds (via /proc/uptime) - Version of curl software (launched as root which is a bad IT practice and a security risk) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
** Tags added: bionic cosmic disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
This ticket should be updated to Security issue +250 points I highly doubt that this Motd News "feature" is compliant with EU's General Data Protection Regulation since daily reporting of computer's infos are proceeded without the user's consent. Cf. GDPR application comments [https://gdpr.eu/eu-gdpr-personal-data/], in particular with respect to Recital 30 [https://gdpr.eu/recital-30-online-identifiers- for-profiling-and-identification/] Internet protocol (IP) addresses; information that is related to an individual’s tools, applications, or devices, like their computer. Daily report of computer's private infos without the users consent It affects Ubuntu Servers and Desktop (including roaming computers like laptops) since at least 18.04 LTS and also the current 20.04 LTS Sensible data sent - IP address of the computer running Ubuntu - Date of the HTTPS query - Kernel Version - CPU Vendor and Model - Uptime - Cloud identifier - Version of Curl so version of Ubuntu running ... $curl_ver $lsb $platform $cpu $uptime $cloud_id Sample from our PC Engines running Ubuntu 18.04 LTS: ``` curl/7.58.0-2ubuntu3.8 GNU/Linux/4.15.0-101-generic/x86_64 AMD/GX-412TC/SOC uptime/692518.54/2755023.47 cloud_id/unknown ``` https://motd.ubuntu.com/ ``` * MicroK8s gets a native Windows installer and command-line integration. https://ubuntu.com/blog/microk8s-installers-windows-and-macos ``` The perfect opportunity to map all Ubuntu Linux users worldwide on a daily basis? https://gdpr.eu/eu-gdpr-personal-data/ https://gdpr.eu/checklist/ See also https://askubuntu.com/questions/1105825/why-lubuntu-18-04-calls-amazon-servers-motd-ubuntu-com -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
Anyone privacy-conscious using any version of Ubuntu should do this in a shell ASAP sudo sed -i -r 's/(ENABLED)=.+/\1=0/' /etc/default/motd-news -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
Thanks security-conscious Dustin Kirkland for this great bash script
("I've insisted on shell here for transparency! - Dustin ")
and other contributions like NSA's SELinux or security sensible
software like Pollinate (Entropy-as-a-Service in the cloud) via
https://entropy.ubuntu.com
Packing so many sensible info inside User-Agent sent daily by default
from all Ubuntu to https://motd.ubuntu.com is brillant!
less /etc/update-motd.d/50-motd-news
```
#50-motd-news - print the live news from the Ubuntu wire
#Copyright (C) 2016-2017 Canonical Ltd.
#Copyright (C) 2016-2017 Dustin Kirkland
##
# This program could be rewritten in C or Golang for faster performance.
# Or it could be rewritten in Python or another higher level language
# for more modularity.
# However, I've insisted on shell here for transparency!
# - Dustin
##
# Curl browser version, for debug purposes
curl_ver="$(dpkg -l curl | awk '$1 == "ii" { print($3); exit(0); }')"
# Distribution version, for messages releated to this Ubuntu release
. /etc/lsb-release
lsb=$(echo "$DISTRIB_DESCRIPTION" | sed -e "s/ /\//g")
codename="$DISTRIB_CODENAME"
# Kernel version and CPU type, for messages related to a particular revision or
hardware
platform="$(uname -o)/$(uname -r)/$(uname -m)"
arch="$(uname -m)"
cpu="$(grep -m1 "^model name" /proc/cpuinfo | sed -e "s/.*: //" -e
"s:\s\+:/:g")"
cloud_id="unknown"
if [ -x /usr/bin/cloud-id ]; then
/usr/bin/cloud-id > "$CLOUD" 2>/dev/null
if [ $? -eq 0 ]; then
# sanitize it a bit, just in case
cloud_id=$(cut -c -40 "${CLOUD}" | tr -c -d '[:alnum:]')
if [ -z "${cloud_id}" ]; then
cloud_id="unknown"
fi
fi
fi
# Some messages may only be pertinent before or after some amount of uptime
read up idle < /proc/uptime
uptime="uptime/$up/$idle"
# Piece together the user agent
USER_AGENT="curl/$curl_ver $lsb $platform $cpu $uptime cloud_id/$cloud_id"
...
# Fetch and print the news motd
if curl --connect-timeout "$WAIT" --max-time "$WAIT" -A "$USER_AGENT"
-o- "$u" >"$NEWS" 2>"$ERR"; then
```
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867424
Title:
motd-news transmitting private hardware data without consent or
knowledge in background
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
Well known... https://twitter.com/search?q=ubuntu%20motd-news&src=typed_query&f=live -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
Part of the base OS ... resistance is futile dpkg -L base-files | grep motd-news /etc/default/motd-news /etc/update-motd.d/50-motd-news /lib/systemd/system/motd-news.service /lib/systemd/system/motd-news.timer sudo grep news /var/log/syslog Jun 4 04:44:22 mbx 50-motd-news[94986]: * MicroK8s gets a native Windows installer and command-line integration. Jun 4 04:44:22 mbx 50-motd-news[94986]: https://ubuntu.com/blog/microk8s-installers-windows-and-macos Jun 4 04:44:22 mbx systemd[1]: motd-news.service: Succeeded. Jun 4 08:57:00 mbx systemd[1]: motd-news.timer: Succeeded. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
Please give the Message of the Day (MOTD) every time I get online on the Internet or I reboot my Ubuntu computer ... Hold on, connecting to Amazon Cloud (Amazon Data Services) motd.ubuntu.com ... Your message of the day is Building Trust is Hard, Breaking Trust is Easy In exchange, please give me your User-Agent will all your private informations so I know who you are (IP, Ubuntu Cloud ID, Linux Kernel Version, Curl version, etc.) GET /bionic/x86_64 HTTP/1.1 Host: motd.ubuntu.com User-Agent: curl/7.58.0-2ubuntu3.8 Ubuntu/18.04.3/LTSGNU/Linux/4.15.0-72-generic /x86_64 Intel(R)/Core(TM)/i5-8500B/CPU/@/3.00GHz uptime/108266.13/21 2047.71 cloud_id/unknown Accept: */* https://ma.ttias.be/what-exactly-being-sent-ubuntu-motd/ [Unit] Description=Message of the Day After=network-online.target Documentation=man:update-motd(8) [Service] Type=oneshot ExecStart=/etc/update-motd.d/50-motd-news --force -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
Thanks Canonical for this great Telemetry master piece hidden in a Daily "News" (Message of the Day) deep inside the core of Ubuntu. I found it active on all the Ubuntu laptop of my friends and coworkers, all Ubuntu servers from local ISP and my work. As well as on all Ubuntu flavours and Ubuntu derived Linux distros. It is also present in cloud-init images of major cloud providers, and all Docker images from Docker Registry based on Ubuntu. What a (s)hell for transparency! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
This is more than just a Telemetry, It as a Trojan in Ubuntu Distro. A remote code-execution (RCE) vulnerability in all Ubuntu of the world! Why? Simple curl is launched as root (not the best practice!), and Ubuntu Distro fetch https://motd.ubuntu.com multiple times per day if someone (like 3-letters or 4 letters) controls this Amazon Web server knowing the version of curl (provided by the script) exploit any local known vulnerability present in curl or use a curl zero day it will have "root" access to any Ubuntu Server or Desktop, Laptop of the world! Proof of Concept Add the following before the for calling curl in /etc/update-motd.d/50 -motd-news date +'%Y-%m-%d %H:%M:%S' >> /tmp/test whoami >> /tmp/test echo $USER_AGENT >> /tmp/test wait 12 hours... or 12:00 / 00:00 or reboot cat /tmp/test 2020-06-05 12:00:00 root curl/7.68.0-1ubuntu2 Ubuntu/20.04/LTS GNU/Linux/**-generic/x86_64 Intel(R)/Core(TM)/i7-**/CPU/@/*GHz uptime/70.55/921.20 cloud_id/unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
motd-news is present in Nvidia Jetson Nano (derived from Ubuntu) and Ubuntu for Raspberry Pi. It is enabled by default and also calling Home Ubuntu via Amazon Cloud. motd-news is also present in Ubuntu Core 18 for embedded systems (like Tesla Car) but unlike Ubuntu Server and Desktop Distro it is not enabled by default. I don't have a Tesla car to verify if it is enabled or not. unxz ubuntu-core-18-amd64.img.xz sudo mount -o loop,offset=$((106496*512)) ubuntu-core-18-amd64.img /mnt/ sudo unsquashfs -d /tmp/core18 /mnt/system-data/var/lib/snapd/seed/snaps/core18_1668.snap /tmp/core18/etc/default/motd-news /tmp/core18/etc/update-motd.d/50-motd-news /tmp/core18/lib/systemd/system/timers.target.wants/motd-news.timer /tmp/core18/var/lib/systemd/deb-systemd-helper-enabled/motd-news.timer.dsh-also /tmp/core18/var/lib/systemd/deb-systemd-helper-enabled/timers.target.wants/motd-news.timer sudo grep ENABLED /tmp/core18/etc/default/motd-news ENABLED=0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
The original request for motd-news came from Dustin Kirkland on 2016-10-30 https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1637800 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
I recommend the following action points to restore a bit of trust in Ubuntu Product after the introduction of motd-news by Dustin Kirkland (Ex- VP Product at Canonical) - Run all motd scripts including motd-news AND curl as non privileged account -- not as root - Move motd-news functionality from base-files to a removable package called motd-news - Set ENABLED to 0 by default on all Ubuntu Distos or at least ask the user consent (during install and later with cloud-init) - Remove private information from User-Agent (uptime, kernel version, curl version, type of cloud) and stop using HTTPS Header such User-Agent as proxy to exfiltrate sensible infos from Ubuntu - Make the code behind https://motd.ubuntu.com auditable, signed and open source - Check the logs of https://motd.ubuntu.com if it has been compromised the last 3 years if it is the case report it so people can reinstall their Ubuntu Server, Desktop, Laptop to restore trust Currently Ubuntu users are trapped as they can only disable motd-news but not uninstall it and any software update of base-files could bring back the security issue. Anyone who has access to motd.ubuntu.com (or via DNS + MITM) could in theory execute code on any Ubuntu if a serious vulnerability in curl has been found or if the user did not update curl. Running curl as root, reporting the curl version and the kernel version give all the information needed to implemented a persistent backdoor in any Ubuntu worldwide. sudo apt-get purge base-files WARNING: The following essential packages will be removed. This should NOT be done unless you know exactly what you are doing! base-files bash 0 upgraded, 0 newly installed, 5 to remove and 26 not upgraded. After this operation, 4,525 kB disk space will be freed. You are about to do something potentially harmful. To continue type in the phrase 'Yes, do as I say!' ?] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
I don't think it was safe decision to link the security of Ubuntu base OS to curl running as root every 12 hours via motd-news just to display Ads for products and not important security messages like suggested in the original ticket (1637800). Just imagine the consequence of https://motd.ubuntu.com being compromised starts to redirect to a TFTP URL and send private memory contents from root account every 12 hours or if curl has a new vulnerability such as buffer overflow discovered automatically by Google's OSS-Fuzz and not yet patched within 30 days by curl maintainers or by Ubuntu Security Team. https://curl.haxx.se/docs/CVE-2017-1000100.html A malicious HTTP(S) server could redirect a vulnerable libcurl-using client to a crafted TFTP URL (if the client hasn't restricted which protocols it allows redirects to) and trick it to send private memory contents to a remote server over UDP. https://bugs.chromium.org/p/oss- fuzz/issues/list?q=curl&can=1&sort=-reported ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-1000100 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
The usage of motd-news as Advertising media for Canonical products is well documented. Now we need to know if Canonical share the crafted User-Agent with sensible info in it with third party and use it for telemetry like Microsoft Windows 10. Samples output of motd-news mirrored in both login prompt via motd and syslog - MicroK8s gets a native Windows installer and command-line integration. https://ubuntu.com/blog/microk8s-installers-windows-and-macos - How HBO's Silicon Valley built "Not Hotdog" with mobile TensorFlow, Keras & React Native on Ubuntu - Overheard at KubeCon: "microk8s.status just blew my mind". https://microk8s.io/docs/commands#microk8s.status https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1701068 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1637800] Re: add a motd script for news
motd-news vs privacy / security / telemetry https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1637800 Title: add a motd script for news To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1637800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
All messages received over a year (Ubuntu 18.04): * Congrats to the Kubernetes community on 1.16 beta 1! Now available * Kata Containers are now fully integrated in Charmed Kubernetes 1.16! * Keen to learn Istio? It's included in the single-package MicroK8s. * Kubernetes 1.18 GA is now available! See https://microk8s.io for docs or * Latest Kubernetes 1.18 beta is now available for your laptop, NUC, cloud * MicroK8s 1.15 is out! It has already been installed on more * MicroK8s 1.15 is out! Thanks to all 40 contributors, you get the latest * MicroK8s passes 9 million downloads. Thank you to all our contributors! * Multipass 1.0 is out! Get Ubuntu VMs on demand on your Linux, Windows or * Multipass 1.1 adds proxy support for developers behind enterprise * Overheard at KubeCon: "microk8s.status just blew my mind". * 'snap info' now shows the freshness of each channel. * Ubuntu 20.04 LTS is out, raising the bar on performance, security, * Ubuntu's Kubernetes 1.14 distributions can bypass Docker and use containerd None of them are about security and none of them are customized using uptime, ubuntu version, kernel version, curl version, ip, ... Why do pack all this into User-Agent which can be linked to public IP every 12 hours? ** Attachment added: "motd-news.txt" https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+attachment/5381565/+files/motd-news.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
Privacy: Ubuntu users don't have the opportunity to opt-out from motd-news before all the private infos and telemetry are sent via User-Agent. So even if people change ENABLED=1 to ENABLED=0 in /etc/default/motd-news they only stop future leaks but the initial leak has already been done in background after the boot via systemd/motd-news service. I repeat, this doesn't look GRPD-compliant at all. There is no prior consent ever asked for. The GDPR was adopted on 14 April 2016, and became enforceable beginning 25 May 2018. motd-news has been designed in 2017 and is enabled by default on all Ubuntu Server, Ubuntu Desktop, Ubuntu Flavors (such as Mate, Raspberry), Ubuntu derived such as Nvidia Jetson Nano without prior consent. Security: Run curl as root every 12h are you serious? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
https://github.com/curl/curl/issues/5557 ** Bug watch added: github.com/curl/curl/issues #5557 https://github.com/curl/curl/issues/5557 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
Maybe as manager of the Ubuntu Server team, you should ask to improve motd-news software to not curl as root. You should also improve landscape and landscape on premises level of access so any users cannot list all processes and reboot any servers or execute shell script as root. Good luck, I think we are done with Ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
By the current design, you don't give choice to the Ubuntu users as they cannot opt-out BEFORE the laptop or server contacts motd.ubuntu.com sending the telemetry. By implementing it as essential package, you don't let user remove it but only disable it when it is too late. The same apply to landscape, you don't give choice to disable some dangerous features like executing very powerful script, list all processes, etc. This is why, we decided to stop using landscape (both in the cloud and on premises). It will be your responsibility as Ubuntu Server manager, if motd.ubuntu.com gets compromised and motd-news is exploited because it runs curl as root and all Ubuntu servers could get compromised at the same time within 12 hours. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
And don't tell me that the fact that Canonical use motd as Telemetry was done transparently, with clear documentation... most users complain only about the advertising but don't realize that the motd-news is used as telemetry tool but seems to act as a advertising / news purpose and the risk of the bad design decision of running curl as root. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
Best practices by Dustin Kirkland https://manpages.ubuntu.com/manpages/focal/en/man5/update-motd.5.html - No mention of curl running as root - No mention of the exfiltration of private data done via User-Agent - No mention of the novel concept of advertising via motd - No mention of using motd-news as telemetry - No mention that motd-news is part of core Ubuntu "base-files" and cannot be removed Feel free to guide me to the correct info on your website or update your documentation. Additional discussions on Twitter https://twitter.com/lusis/status/880446088083329024 https://twitter.com/astarrb/status/880170781841514496 https://twitter.com/lelff/status/1210619413885575168 https://twitter.com/hessu/status/1269994718018056199 https://twitter.com/nikitonsky/status/1073714951104184320 https://twitter.com/wamdamdam/status/1044197012353298433 https://twitter.com/marcodavids/status/1245054456955314178 ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
I have decided to contact ICO (Information Commissioner's Office). Because Canonical Ltd. has handled my personal information (IP address, Hardware CPU, Choice of Cloud Hosting, and various meta-data) and the one of the company I work for without concent. The same apply to all users of Ubuntu (persons, companies, governements) worldwide on a daily basis. By collecting twice a day the following informations: - The public IP address where Ubuntu system is used (part of the log of the HTTPS server) - Date / Time when collected (part of the log of the HTTPS server) - Harware info such as CPU Vendor and Model (via /proc/cpuinfo) - The distribution version (via /etc/lsb-release) - The operating system (via uname -o) - The Linux kernel release (via uname -r) - The computer architecture aka machine hardware name (via uname -m) - Cloud Hosting: cloud identifier such as aws, gce, azure, lxd (via cloud-id part of cloud-init) - Total number of seconds the system has been up (via /proc/uptime) - The sum of how much time each core has spent idle in seconds (via /proc/uptime) - Version of curl software (launched as root which is a bad IT practice and a security risk) On top of that by making motd-news unremovable in the core of Ubuntu's base-files (like it was the case for Internet Explorer in Windows or the Telemery in Windows 10), they enforce the telemetry before you can disable it or opt-out from it. Fell free to fill your own complaint or contact your local information commissioner as this ticket is marked as Won't Fix by the manager of the Ubuntu Server team. https://ico.org.uk/make-a-complaint/your-personal-information-concerns /personal-information-complaint/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
I will first contact the Data Protection Officer (DPO) of Canonical Group Limited dataprotect...@canonical.com https://ubuntu.com/legal/data-privacy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
FYI Canonical's legal departement is reviewing motd-news "feature" (such as telemetry) and will provide updated information next week. All motd-news related tickets https://bugs.launchpad.net/ubuntu/+source/base- files/+bugs?field.searchtext=motd- news&orderby=-datecreated&search=Search&field.status%3Alist=NEW&field.status%3Alist=OPINION&field.status%3Alist=INVALID&field.status%3Alist=WONTFIX&field.status%3Alist=EXPIRED&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=FIXRELEASED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE "Canonical has launched the Ubuntu Appliance initiative which aims to transform Raspberry Pi devices or personal computers into secure, self- updating solutions" (source 9to5linux). I checked nextcloud- core18-pi.img (and core18_1753.snap), motd-news is still present but turned off by default -- Good! ENABLED=0 in the file /etc/default/motd- news. I hope Canonical will apply "Secure by design" motto to the rest of Ubuntu products https://ubuntu.com/appliance -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868551] Re: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.32/CHANGES https://patchwork.ozlabs.org/project/ubuntu- kernel/patch/20200407222740.7671-2-sultan.alsa...@canonical.com/ Note that this bug only affects 5.4 and has since been fixed in 5.5. Normally, a backport of the fix from 5.5 would be in order, but the patch set that fixes this deadlock involves massive changes that are neither feasible nor desirable for backporting [1][2][3]. Therefore, this small patch was made to address the deadlock specifically for 5.4. ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868551 Title: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868551] Re: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire
As 5.5 is more stable on my Dell XPS 13 than 5.4 with Intel iGPU (i915)
I did the following one-liner to install the latest version of Linux Kernel 5.5
on Ubuntu 20.04
which curl >/dev/null 2>&1 || sudo apt-get install -qq -y curl; for
version in $(curl -sL https://kernel.ubuntu.com/~kernel-ppa/mainline/ |
tac | grep -Pom1 '(?<=")v5\.5\.[0-9]+/'); do for deb in $(curl -sL
https://kernel.ubuntu.com/~kernel-ppa/mainline/${version} | grep -Pom4
'(?<=")linux-(headers|image-
unsigned|modules)-5\.5\.[^"]+[0-9]+(-generic_5\.5\.|_5\.5\.)[^"]+.(amd64|all)\.deb');
do curl -sLo ${deb} https://kernel.ubuntu.com/~kernel-
ppa/mainline/${version}/${deb}; debs="${debs} ${deb}"; done; sudo dpkg
-i ${debs}; done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868551
Title:
Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4)
i915_active_acquire
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868551/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868551] Re: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire
Regarding #28
"on 20.04 LTS and v5.6 is not working properly with WiFi."
When I first tested Kernel 5.6 branch, the WiFi was broken because of this:
https://linuxreviews.org/Linux_5.6.2_Is_Released_With_Intel_Wifi_Fix
Now it is working again with the current 5.6 branch.
Kernel 5.5 is now EOL (as of 5.5.19 end of April)
https://en.wikipedia.org/wiki/Linux_kernel_version_history#Releases_5.x.y
Intel should do better QA for their iGPU and WiFi
and try to port it to all stable LTS branches aka 5.4.x and 5.6.x
If you still have issues with Intel i915 on 5.4.x, you can use
the following one-liner to install 5.6.x
which curl >/dev/null 2>&1 || sudo apt-get install -qq -y curl; for
version in $(curl -sL https://kernel.ubuntu.com/~kernel-ppa/mainline/ |
tac | grep -Pom1 '(?<=")v5\.6\.[0-9]+/'); do for deb in $(curl -sL
https://kernel.ubuntu.com/~kernel-ppa/mainline/${version} | grep -Pom4
'(?<=")linux-(headers|image-
unsigned|modules)-5\.6\.[^"]+[0-9]+(-generic_5\.6\.|_5\.6\.)[^"]+.(amd64|all)\.deb');
do curl -sLo ${deb} https://kernel.ubuntu.com/~kernel-
ppa/mainline/${version}/${deb}; debs="${debs} ${deb}"; done; sudo dpkg
-i ${debs}; done
If you need to go back to legacy Ubuntu 20.04 LTS Kernel and remove
Linux Kernel 5.5 and 5.6
dpkg --get-selections | awk '/linux-.*-5\.[5-6]/ { print $1 }' | xargs
echo sudo apt-get purge -y
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868551
Title:
Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4)
i915_active_acquire
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868551/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
https://ico.org.uk/make-a-complaint/your-personal-information-concerns/ To: ICO Dear Information Commissioner’s Office, I confirm that I want to proceed with the creation of the case about Canonical's motd-news as Canonical don't want to remediate the privacy issue of sending by default hardware details and public IP of all Ubuntu Desktop and Ubuntu Server twice a day, every day of the year. Next to this message, you will find the final answer from Canonical. https://ubuntu.com/legal/motd The following are my comments on their legal information. "The purpose of sending the system information is so that Canonical can tailor the message returned by https://motd.canonical.com."; This is wrong motd.canonical.com does not exist and is part of motd-news. The server used by Ubuntu is https://motd.ubuntu.com lynx -mime_header https://motd.canonical.com Looking up motd.canonical.com Unable to locate remote host motd.canonical.com. Alert!: Unable to connect to remote host. The evidence is part of the Ticket https://launchpadlibrarian.net/487032881/ubuntu-desktop-2004-motd-news.png "None of this data can be used to identify a machine or user." "Along with this data, the IP address and other network information is transmitted to facilitate communication on the internet from the Ubuntu machine to Canonical. This information is not stored by Canonical." This is wrong as Canonical is using Apache and the default is to store IP address in the access log https://httpd.apache.org/docs/current/logs.html Common Log Format (%h) This is the IP address of the client (remote host) which made the request to the server. If HostnameLookups is set to On, then the server will try to determine the hostname and log it in place of the IP address. However, this configuration is not recommended since it can significantly slow the server. Instead, it is best to use a log post-processor such as logresolve to determine the hostnames. The IP address reported here is not necessarily the address of the machine at which the user is sitting. If a proxy server exists between the user and the server, this address will be the address of the proxy, rather than the originating machine. lynx -mime_header https://motd.ubuntu.com HTTP/1.1 200 OK Date: Mon, 13 Jul 2020 06:05:38 GMT Server: Apache/2.4.18 (Ubuntu) Last-Modified: Mon, 13 Jul 2020 06:00:50 GMT Accept-Ranges: bytes Content-Length: 215 Vary: Accept-Encoding Connection: close Content-Type: text/plain * "If you've been waiting for the perfect Kubernetes dev solution for macOS, the wait is over. Learn how to install Microk8s on macOS." https://www.techrepublic.com/article/how-to-install-microk8s-on- macos/ "You can disable this service as follows:" "/etc/default/motd-news has an ENABLED=1 setting that if set to 0 will turn off this functionality." I assume 80% of Ubuntu Desktop users will not know how to disable motd-news because they need a Terminal and sudo access. A regular editor running a default user will not allow to edit this file as super user. So this doc is useless. On top of that Canonical send motd-news information before the user can even opt out during the installation of Ubuntu Desktop and during the first boot of the Ubuntu Desktop operating system so setting it is only useful to stop it but the harm is already done and data already sent to Canonical. Evidence https://launchpadlibrarian.net/487031151/ubuntu- desktop-2004.png For more information read https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424 Please also note that https://ubuntu.com/legal/motd title is not searchable in their search engine and is not part of the legal notice during the installation of Ubuntu Evidence (picture in attachment) and https://launchpadlibrarian.net/487031391/ubuntu-desktop-2004-legal.png "No, don't send system info" is not respected https://launchpadlibrarian.net/487031210/ubuntu-desktop-2004-optout.png https://launchpadlibrarian.net/487032881/ubuntu-desktop-2004-motd-news.png Privacy does not have an option to opt out from motd-news https://launchpadlibrarian.net/487031529/ubuntu-desktop-2004-privacy.png Forwarded Message Subject: Re: Unremovable motd-news used as Telemetry and Advertising tool without explicit consent Date: Fri, 10 Jul 2020 12:00:29 +0100 Dear Guy Thank you for your patience. Please now see the legal notice for MOTD on Canonical's website: https://ubuntu.com/legal/motd I can assure you that no access to or storage of IP address data is made. Canonical takes data protection compliance very seriously and we continue to review how we can improve this and other services. Many thanks Director of Legal & Company Secretary Canonical Blue Fin Building, 5th Floor 110 Southwark Street, SE1 0SU Ubuntu - Linux for Human Beings www.canonical.com -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
I added https://ubuntu.com/legal/motd to Archive.org's Internet Wayback Machine https://web.archive.org/web/20200713070037/https://ubuntu.com/legal/motd ** Attachment added: "canonical-legal-motd.pdf" https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+attachment/5392271/+files/canonical-legal-motd.pdf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
On my point of view, it's NOT enough to implement a legal notice https://ubuntu.com/legal/motd with technical errors and it is not possible to verify that Canonical does not store the IP address of Ubuntu users in Apache log (the default) and/or database without an external auditor (PwC, EY, KPMG, etc.). Nothing has been done regarding the consent of the user. I except one of the following two options to be implemented by Canonical. (A) Ask for consent during the installation of the operating system Ubuntu and before sharing my personal information via the motd-news software used for Telemetry, Tracking, Advertising purpose instead of providing meaningful "security messages or other news" on a daily basis. (B) Or disable it by default via ENABLED=0 in the file /etc/default/motd- news and move motd-news software outside "base-files" package and make it user removable. If Canonical doesn't takes data protection seriously by implementing technical measures such as stop calling motd-news during installation and after automatically without consent and implement an easy way to opt out for people without technical knowledge in linux shell then ICO will need to evaluate the choice of Canonical of enforcing Telemetry hidden in motd-news's User-Agent without asking user consent and not respecting "No, don't send system info" choice of the user during the installation wizard, sending beacons with IP address, system info twice a day, every day from all Ubuntu Desktop and Ubuntu Server installations worldwide. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868551] Re: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire
I tested the test kernel 5.4 for about a day without issue but all my computers using Intel GPU are using by default kernel 5.5. I don't want to change that. If you want to follow other users having the same kind of issues with different i915 bugs on different Linux distro follow comments on https://linuxreviews.org/Linux_Kernel_5.5_Will_Not_Fix_The_Frequent_Intel_GPU_Hangs_In_Recent_Kernels -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868551 Title: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721987] Re: No sound from right audio channel
This is my backport of Tomas Espeleta's patch to Linux 4.15.18 (linux- source-4.15.0 / 4.15.0-45.48 available on Ubuntu 18.04.2 LTS) ** Patch added: "huawei-matebook-x-right-speaker-work-4.15.0.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721987/+attachment/5241510/+files/huawei-matebook-x-right-speaker-work-4.15.0.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721987 Title: No sound from right audio channel To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1721987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1411030] Re: backport support for unix domain sockets
https://httpd.apache.org/docs/trunk/mod/mod_proxy_fcgi.html 14.04 LTS has Apache 2.4.7 so you cannot use this : # Requires Apache 2.4.9 or later SetHandler "proxy:unix:/var/run/php5-fpm.sock|fcgi://localhost/" # Requires Apache 2.4.10 and later SetHandler "proxy:fcgi://127.0.0.1:9000" So with 14.04 LTS you need to 1. Configure each VirtualHost with ProxyPassMatch ^/(.*\.php(/.*)?)$ fcgi://127.0.0.1:9000/your_path_to/htdocs/$1 2. In PHP5-FPM, use TCP instead of Unix Domain Socket (/etc/php5/fpm/pool.d/www.conf) listen = 127.0.0.1:9000 The alternative is to use mod_fastcgi but it's part of multiverse (disabled by default /etc/apt/sources.list) See also http://events.linuxfoundation.org/sites/events/files/slides/AC2014-FastCGI.pdf 16.04 LTS is out but not all PHP applications are compatible with PHP 7 (like ibm_db2 is not yet ready https://bugs.php.net/bug.php?id=69852) ** Bug watch added: bugs.php.net/ #69852 http://bugs.php.net/bug.php?id=69852 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1411030 Title: backport support for unix domain sockets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1411030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1527062] Re: XFS Deadlock on 4.2+
FYI I still have the issue on 3.13.0-91-generic (and 3.13.0-88-generic) on a busy NFS server using XFS. I have this issue since 2015... INFO: task kworker/1:2:31748 blocked for more than 120 seconds. Not tainted 3.13.0-91-generic #138-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. kworker/1:2 D 88023f433180 0 31748 2 0x Workqueue: xfs-log/dm-5 xfs_log_worker [xfs] 88012f31fb70 0046 880035983000 00013180 88012f31ffd8 00013180 880035983000 88012f31fcb8 88012f31fcc0 7fff 880035983000 8802317e9528 Call Trace: [] schedule+0x29/0x70 [] schedule_timeout+0x279/0x310 [] wait_for_completion+0xa6/0x150 [] ? wake_up_state+0x20/0x20 [] flush_work+0xed/0x1b0 [] ? wake_up_worker+0x30/0x30 [] xlog_cil_force_lsn+0x3f/0x170 [xfs] ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1527062 Title: XFS Deadlock on 4.2+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1527062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1557612] [NEW] evolution: e-data-server Error opening directory '/usr/lib/evolution-data-server/credential-modules'
Public bug reported: After updating evolution to 3.18.5.1-1ubuntu1 on Ubuntu 16.04, it stopped working: $ evolution (evolution:4688): e-data-server-WARNING **: e_module_load_all_in_directory: Error opening directory '/usr/lib/evolution-data-server/credential-modules': No such file or directory My workaround: sudo apt-get install evolution-data-server-online-accounts Then it worked again. Maybe you need to add "Depends: evolution-data-server-online-accounts (>= 3.18.5)" to evolution package or remove the new depency. ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Package changed: linux (Ubuntu) => evolution (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1557612 Title: evolution: e-data-server Error opening directory '/usr/lib/evolution- data-server/credential-modules' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1557612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1585614] Re: libc on 2016-05-25 causes Apache not to restart, libm.so.6: symbol __strtold_nan, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
Same issue This morning, a security update for libc has been automatically deployed on all our servers running 14.04 LTS. unattended-upgrades-dpkg_2016-05-26_06:36:05.829399.log:Unpacking libc6-dev:amd64 unattended-upgrades-dpkg_2016-05-26_06:36:05.829399.log:Unpacking libc-dev-bin unattended-upgrades-dpkg_2016-05-26_06:36:05.829399.log:Unpacking libc-bin unattended-upgrades-dpkg_2016-05-26_06:36:05.829399.log:Unpacking libc6:amd64 unattended-upgrades-dpkg_2016-05-26_06:36:05.829399.log:Unpacking multiarch-support On one of our web servers (only one??) Apache (2.4.7-1ubuntu4.9) has stopped working after the unattended upgrades of libc6. When Apache received the signal SIGUSR1. This did not impact any other web server with identical version of all softwares (aligned with Ansible) ?! -- at least in the beginning of the day... Later on at 12:52 we did "apachectl graceful" on all our web servers and all apache servers stopped responding until we restart them with "service apache2 restart". [Thu May 26 06:35:36.222660 2016] [mpm_worker:notice] [pid 6318:tid 140737354041216] AH00297: SIGUSR1 received. Doing graceful restart [Thu May 26 06:35:36.231321 2016] [:alert] [pid 16293:tid 140737354041216] (4)Interrupted system call: FastCGI: read() from pipe failed (0) [Thu May 26 06:35:36.231395 2016] [:alert] [pid 16293:tid 140737354041216] (4)Interrupted system call: FastCGI: the PM is shutting down, Apache seems to have disappeared - bye apache2: Syntax error on line 140 of /etc/apache2/apache2.conf: Syntax error on line 2 of /etc/apache2/mods-enabled/security2.load: Cannot load libxml2.so.2 into server: /lib/x86_64-linux-gnu/libm.so.6: symbol __strtold_nan, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1585614 Title: libc on 2016-05-25 causes Apache not to restart, libm.so.6: symbol __strtold_nan, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1585614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1486914] [NEW] shoreall won't start, wrong runlevels
Public bug reported:
Ubuntu 14.04 LTS and 15.04
Steps to reproduce:
apt-get install shorewall
vi /etc/default/shorewall
replace
startup=0
with
startup=1
cp -va
/usr/share/doc/shorewall/examples/one-interface/{interfaces,policy,rules,zones}
/etc/shorewall/
shorewall check
shorewall safe-restart
iptables -L -n # all rules are there
reboot
iptables -L -n # all rules are gone #FAIL
Workaround:
vi /etc/init.d/shorewall
replace
# Default-Start: S
# Default-Stop: 0 6
with
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
sudo rm -fv /etc/rc?.d/*shorewall*
sudo update-rc.d shorewall defaults
References:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773392
http://ubuntuforums.org/showthread.php?t=2275224
https://help.ubuntu.com/community/ShorewallBasics
** Affects: shorewall (Ubuntu)
Importance: Undecided
Status: New
** Tags: init shorewall
** Package changed: shorewall-common (Ubuntu) => shorewall (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1486914
Title:
shoreall won't start, wrong runlevels
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shorewall/+bug/1486914/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1486914] Re: shoreall won't start, wrong runlevels
** Description changed:
-
Ubuntu 14.04 LTS and 15.04
Steps to reproduce:
apt-get install shorewall
- vi /etc/default/shorewall
+ vi /etc/default/shorewall
replace
startup=0
with
startup=1
cp -va
/usr/share/doc/shorewall/examples/one-interface/{interfaces,policy,rules,zones}
/etc/shorewall/
+ shorewall check
shorewall safe-restart
iptables -L -n # all rules are there
reboot
iptables -L -n # all rules are gone #FAIL
Workaround:
- vi /etc/init.d/shorewall
+ vi /etc/init.d/shorewall
+
replace
+
# Default-Start: S
+ # Default-Stop: 0 6
+
with
+
# Default-Start: 2 3 4 5
+ # Default-Stop: 0 1 6
+
sudo rm -fv /etc/rc?.d/*shorewall*
sudo update-rc.d shorewall defaults
References:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773392
http://ubuntuforums.org/showthread.php?t=2275224
https://help.ubuntu.com/community/ShorewallBasics
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1486914
Title:
shoreall won't start, wrong runlevels
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shorewall/+bug/1486914/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1463023] Re: systemd Timed out waiting for device swap and file system check
Please note that my swap is NOT encrypted so it's not related to bug 1440098 or 953875 ** Package changed: cryptsetup (Ubuntu) => systemd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1463023 Title: systemd Timed out waiting for device swap and file system check To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1463023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1463023] [NEW] systemd Timed out waiting for device swap and file system check
Public bug reported: My Ubuntu 15.04 did not start --or took so long that I switched back to upstart! ISSUE: (systemd during the boot) Timed out waitingfor device dev-disk-by\x2duuid-... (swap) Dependency failed for /dev/disk/by-uuid/... (swap) Dependency failed for Swap. Timed out waiting for device dev-sdaX.device(swap) Dependency failed for Swap Partition. Failed to start udev Wait for Complete Device Initialization. See "systemctl status systemd-udev-settle.service" for details. Starting File System Check on Root Device... Starting Copy rules generated while the root was ro... (1 of 2) A start job is running for File System Check on Root Device (3min 28s / no limit) ... No tainted 3.19.0-18-generic #18-Ubuntu "echo 0> /proc/sys/kernel/hung_task_timeout_secs" disables this message. INFO: task systemd-udevd:336 blocked for more than 120 seconds. ... INFO: task systemd-udevd:338 blocked for more than 120 seconds. ... INFO: task systemd-udevd:346 blocked for more than 120 seconds. ... (1 of 2) A start job is running for File System Check on Root Device (4min 3s / no limit) WORKAROUND: apt-get -qq -y install upstart-sysv # switch back to upstart http://linux.softpedia.com/blog/Ubuntu-15-04-Users-Can-Switch-Off-Systemd-and-Use-Upstart-479373.shtml P.S. don't ask me to go back to systemd-sysv... I am fine with upstart TECHNICAL DETAILS: $ lsb_release -r Release:15.04 $ uname -r 3.19.0-18-generic $ sudo dmidecode -s system-product-name MacBookPro8,2 $ grep "^GRUB_CMDLINE_LINUX_DEFAULT" /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="transparent_hugepage=always intel_iommu=on acpi_irq_nobalance cgroup_enable=memory swapaccount=1 libata.force=noncq modeset=1 hybridopts=ON,IGD,OFF i915.modeset=0 radeon.modeset=1 radeon.dpm=1 radeon.audio=1 i915.lvds_channels=2 quirks.mbp_force_ahci=1 acpi_backlight=vendor reboot=pci" $ cat /etc/fstab # # / was on /dev/sda5 during installation UUID=6619a7e9-4b94-4e9b-8dbe-4110f89dde74 / ext4 errors=remount-ro 0 1 # swap was on /dev/sda6 during installation UUID=813e9dc2-c678-4959-ac89-e6660f886942 noneswapsw 0 0 # lsblk -f NAME FSTYPE LABELUUID MOUNTPOINT sda ├─sda1 vfatEFI 67E3-17ED ├─sda2 hfsplus Macintosh HD 2ba5bbc1-fff0-36ea-ade4-140386274279 ├─sda3 hfsplus Recovery HD 9e776f16-ceb4-37e6-b4ce-4e75c1db5444 ├─sda4 ├─sda5 ext4 6619a7e9-4b94-4e9b-8dbe-4110f89dde74 / └─sda6 swap 813e9dc2-c678-4959-ac89-e6660f886942 [SWAP] sr0 # blkid /dev/sda1: LABEL="EFI" UUID="67E3-17ED" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="5d71ff71-9843-473d-90e7-4c780c8a494d" /dev/sda2: UUID="2ba5bbc1-fff0-36ea-ade4-140386274279" LABEL="Macintosh HD" TYPE="hfsplus" PARTLABEL="Macintosh HD" PARTUUID="4e4c2249-24f8-4229-9325-d4aafd7ac093" /dev/sda3: UUID="9e776f16-ceb4-37e6-b4ce-4e75c1db5444" LABEL="Recovery HD" TYPE="hfsplus" PARTLABEL="Recovery HD" PARTUUID="a986e3e1-ed3b-44bb-a75b-87b54434380d" /dev/sda5: UUID="6619a7e9-4b94-4e9b-8dbe-4110f89dde74" TYPE="ext4" PARTUUID="9d860cb1-1334-4f79-a07a-01b8818c4aab" /dev/sda6: UUID="813e9dc2-c678-4959-ac89-e6660f886942" TYPE="swap" PARTUUID="bf1271f6-8d51-4510-8979-666c9546f1f3" /dev/sda4: PARTUUID="2b731a42-bd29-4548-8f0e-a9889ee9486b" ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: swap systemd systemd-boot ** Attachment added: "IMG_20150608_114616.jpg" https://bugs.launchpad.net/bugs/1463023/+attachment/4411529/+files/IMG_20150608_114616.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1463023 Title: systemd Timed out waiting for device swap and file system check To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1463023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1463023] Re: systemd Timed out waiting for device swap and file system check
> Please attach /etc/fstab from your system, and show the output of 'swapon' > when booted with upstart. @vorlon content of fstab see "Bug Description" $ sudo swapon NAME TYPE SIZE USED PRIO /dev/sda6 partition 7.9G 11.5M -1 Ok, I will try to go back to systemd for science ;-) $ sudo apt-get install systemd-sysv @pitti I will try that. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1463023 Title: systemd Timed out waiting for device swap and file system check To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1463023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1463023] Re: systemd Timed out waiting for device swap and file system check
@pitti I am unable to reproduce it with 3.19.0-20 nor 3.19.0-18. So I installed back systemd-sysv and I will do the debug stuff next time I have the issue. I guess the issue was related to a strange state of swap or the disk and after booting once with upstart something fixed it. fsck?? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1463023 Title: systemd Timed out waiting for device swap and file system check To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1463023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1463023] Re: systemd Timed out waiting for device swap and file system check
It could be related that ext4 was in a bad state and systemd was not able to use it then upstart executed fsck to fix it and now I can again use systemd. # /var/log/syslog.4.gz $ zgrep -h "fsck" /var/log/*.gz Jun 8 08:43:06 mbp kernel: [1788385.038996] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. Jun 8 10:48:10 mbp systemd-fsck[971]: /dev/sda5: clean, 448286/17760256 files, 35731755/71025664 blocks Jun 8 10:48:10 mbp kernel: [4.748519] systemd[1]: Listening on fsck to fsckd communication Socket. Jun 8 10:48:10 mbp kernel: [4.750175] systemd[1]: Starting fsck to fsckd communication Socket. Jun 8 11:08:54 mbp systemd-fsck[943]: /dev/sda5: clean, 447436/17760256 files, 35695088/71025664 blocks Jun 8 11:08:54 mbp kernel: [3.809333] systemd[1]: Listening on fsck to fsckd communication Socket. Jun 8 11:08:54 mbp kernel: [3.809392] systemd[1]: Starting fsck to fsckd communication Socket. Jun 8 11:11:50 mbp systemd-fsck[946]: /dev/sda5: clean, 447438/17760256 files, 35715637/71025664 blocks Jun 8 11:11:50 mbp kernel: [3.736279] systemd[1]: Listening on fsck to fsckd communication Socket. Jun 8 11:11:50 mbp kernel: [3.737878] systemd[1]: Starting fsck to fsckd communication Socket. zgrep -h systemd /var/log/syslog.4.gz > systemd-2015-06-08.log ** Attachment added: "systemd-2015-06-08.log" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1463023/+attachment/4413674/+files/systemd-2015-06-08.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1463023 Title: systemd Timed out waiting for device swap and file system check To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1463023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1267059] Re: "Unattended-Upgrade::Remove-Unused-Dependencies" does not work
I agree with @Jamiejellicoe this ticket should be rated as "Security issue" (250) but we are close that (236)... Having /boot full can lead to kernel, inird image or grub.conf corruption and on top of that it's blocking new security updates to be applied. When /boot is full you cannot even purge old kernel before /boot has a minimum disk space. So my workaround is to echo -n > /boot/initrd.img- some old kernel's inird images so I have enough free space to cleanup old kernel, header, etc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1267059 Title: "Unattended-Upgrade::Remove-Unused-Dependencies" does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1267059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1253155] Re: Failure to validate module signature at boot time
Same issue $ lsb_release -r Release:14.04 $ uname -r 3.13.0-52-generic May 10 00:40:40 kernel: [...] Request for unknown module key 'Magrathea: Glacier signing key: 1981bc916ffc00599231ec5630e666e0256fd6f1' err -11 May 10 00:40:40 kernel: [...] ipt_REJECT: module verification failed: signature and/or required key missing - tainting kernel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1253155 Title: Failure to validate module signature at boot time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1253155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1227912] Re: instance fails to boot with qemu guest agent set in image metadata
I had the same issue when AppArmor is active (default)
and when I try to enable qemu guest agent inside your
guest :
virsh start test
error: Failed to start domain test
error: internal error: process exited while connecting to monitor:
qemu-system-x86_64: -chardev
socket,id=charchannel0,path=/var/lib/libvirt/qemu/test-virtio.sock,server,nowait:
Failed to bind socket: Permission denied
qemu-system-x86_64: -chardev
socket,id=charchannel0,path=/var/lib/libvirt/qemu/test-virtio.sock,server,nowait:
chardev: opening backend "socket" failed
audit: type=1400 audit(...): apparmor="DENIED" operation="mknod" profile
="libvirt-74c30212-4631-4498-a684-c62db8b2dc21"
name="/var/lib/libvirt/qemu/test-virtio.sock" pid=10291 comm="qemu-
system-x86" requested_mask="c" denied_mask="c" fsuid=106 ouid=106
I am using qemu guest agent to be able to call guest-fstrim
virsh qemu-agent-command '{"execute":"guest-fstrim"}'
guest-fstrim is doing fstrim on all partitions if discard has been
enabled with virtio-scsi (free up deleted blocks)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1227912
Title:
instance fails to boot with qemu guest agent set in image metadata
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1227912/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1227912] Re: instance fails to boot with qemu guest agent set in image metadata
Is it possible to apply this patch to libvirt-bin package and allow to write to /var/lib/libvirt/qemu/ ? For me it makes sense because disabling AppArmor for OpenStack is not a good idea so you will be exposed to security issues like Venom https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/VENOM << Additionally, the QEMU process is confined by an AppArmor profile that significantly lessens the impact of a vulnerability such as VENOM by reducing the host environment's attack surface >> $ dpkg -S /etc/apparmor.d/abstractions/libvirt-qemu libvirt-bin: /etc/apparmor.d/abstractions/libvirt-qemu ** Patch added: "Fix for" https://bugs.launchpad.net/nova/+bug/1227912/+attachment/4404897/+files/apparmor_libvirt-qemu.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1227912 Title: instance fails to boot with qemu guest agent set in image metadata To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1227912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480923] [NEW] lvm thin corruption after lvresize
Public bug reported: lvm2 version 2.02.98-6ubuntu2 After doing a lvextend of a LVM Thin Pool, I had a corruption all sub LVM Thin Volumes and lost all of them. Then tried to dump/repair the tmeta and end up with empty thin volumes (no more filesystem signature on them). To sum up The thin_pool was 2T and I tried to increased it to 3T... As fare as I know, none of the partitions were full but I increased the main thin pool as it was close to the sum of all sub thin volumes. I assume that using LVM Thin is still not stable on 14.04 LTS right? I guess that lvm2 2.02.98 does not properly handle the metadata resize of a thin pool right? (maybe add a warning somewhere in doc?) I managed to recover some files from the raw thin_pool (tdata/tpool) with scalapel but that is it. Do you known any other tools to recovery lvm thin volumes or partition/data on it? Errors attempt to access beyond end of device dm-6: rw=0, want=7753528, limit=262144 attempt to access beyond end of device dm-6: rw=0, want=7753528, limit=262144 attempt to access beyond end of device dm-6: rw=0, want=7753528, limit=262144 attempt to access beyond end of device dm-6: rw=0, want=7753528, limit=262144 /dev/mainvg/thin_rsnapshot: read failed after 0 of 4096 at 2199023190016: Input/output error /dev/mainvg/thin_rsnapshot: read failed after 0 of 4096 at 2199023247360: Input/output error /dev/mainvg/thin_rsnapshot: read failed after 0 of 4096 at 0: Input/output error /dev/mainvg/thin_rsnapshot: read failed after 0 of 4096 at 4096: Input/output error /dev/mainvg/thin_archive: read failed after 0 of 4096 at 805306302464: Input/output error /dev/mainvg/thin_archive: read failed after 0 of 4096 at 805306359808: Input/output error /dev/mainvg/thin_archive: read failed after 0 of 4096 at 0: Input/output error /dev/mainvg/thin_archive: read failed after 0 of 4096 at 4096: Input/output error lvs LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert thin_archive mainvg Vwi-aotz- 500.00g thin_pool 94.65 thin_rsnapshot mainvg Vwi-aotz- 1.50t thin_pool 94.01 thin_pool mainvg twi-a-tz- 3.00t 71.65 lvresize -L 2T /dev/mapper/mainvg-thin_rsnapshot /dev/mainvg/thin_rsnapshot: read failed after 0 of 4096 at 1649267376128: Input/output error /dev/mainvg/thin_rsnapshot: read failed after 0 of 4096 at 1649267433472: Input/output error /dev/mainvg/thin_archive: read failed after 0 of 4096 at 536870846464: Input/output error /dev/mainvg/thin_archive: read failed after 0 of 4096 at 536870903808: Input/output error Extending logical volume thin_rsnapshot to 2.00 TiB Logical volume thin_rsnapshot successfully resized ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: lvm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480923 Title: lvm thin corruption after lvresize To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1480923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480923] Re: lvm thin corruption after lvresize
** Package changed: update-manager (Ubuntu) => lvm2 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480923 Title: lvm thin corruption after lvresize To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1480923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480923] Re: lvm thin corruption after lvresize
** Description changed: lvm2 version 2.02.98-6ubuntu2 - After doing a lvextend of a LVM Thin Pool, I had a corruption all sub - LVM Thin Volumes and lost all of them. Then tried to dump/repair the + After doing a lvresize of a LVM Thin Pool, I had a corruption all sub + LVM Thin Volumes and lost all of them. Then tried to dump/repair the tmeta and end up with empty thin volumes (no more filesystem signature on them). To sum up The thin_pool was 2T and I tried to increased it to 3T... - As fare as I know, none of the partitions were full but I increased the main + As fare as I know, none of the partitions were full but I increased the main thin pool as it was close to the sum of all sub thin volumes. I assume that using LVM Thin is still not stable on 14.04 LTS right? - I guess that lvm2 2.02.98 does not properly handle the metadata resize + I guess that lvm2 2.02.98 does not properly handle the metadata resize of a thin pool right? (maybe add a warning somewhere in doc?) - I managed to recover some files from the raw thin_pool (tdata/tpool) with scalapel - but that is it. + Maybe related to + http://comments.gmane.org/gmane.linux.kernel.device-mapper.devel/19190 + https://www.redhat.com/archives/lvm-devel/2013-June/msg00371.html + + I managed to recover some files from the raw thin_pool (tdata/tpool) with scalapel + but that is it. Do you known any other tools to recovery lvm thin volumes or partition/data on it? Errors - attempt to access beyond end of device - dm-6: rw=0, want=7753528, limit=262144 - attempt to access beyond end of device - dm-6: rw=0, want=7753528, limit=262144 - attempt to access beyond end of device - dm-6: rw=0, want=7753528, limit=262144 - attempt to access beyond end of device - dm-6: rw=0, want=7753528, limit=262144 + attempt to access beyond end of device + dm-6: rw=0, want=7753528, limit=262144 + attempt to access beyond end of device + dm-6: rw=0, want=7753528, limit=262144 + attempt to access beyond end of device + dm-6: rw=0, want=7753528, limit=262144 + attempt to access beyond end of device + dm-6: rw=0, want=7753528, limit=262144 - /dev/mainvg/thin_rsnapshot: read failed after 0 of 4096 at 2199023190016: Input/output error - /dev/mainvg/thin_rsnapshot: read failed after 0 of 4096 at 2199023247360: Input/output error - /dev/mainvg/thin_rsnapshot: read failed after 0 of 4096 at 0: Input/output error - /dev/mainvg/thin_rsnapshot: read failed after 0 of 4096 at 4096: Input/output error - /dev/mainvg/thin_archive: read failed after 0 of 4096 at 805306302464: Input/output error - /dev/mainvg/thin_archive: read failed after 0 of 4096 at 805306359808: Input/output error - /dev/mainvg/thin_archive: read failed after 0 of 4096 at 0: Input/output error - /dev/mainvg/thin_archive: read failed after 0 of 4096 at 4096: Input/output error + /dev/mainvg/thin_rsnapshot: read failed after 0 of 4096 at 2199023190016: Input/output error + /dev/mainvg/thin_rsnapshot: read failed after 0 of 4096 at 2199023247360: Input/output error + /dev/mainvg/thin_rsnapshot: read failed after 0 of 4096 at 0: Input/output error + /dev/mainvg/thin_rsnapshot: read failed after 0 of 4096 at 4096: Input/output error + /dev/mainvg/thin_archive: read failed after 0 of 4096 at 805306302464: Input/output error + /dev/mainvg/thin_archive: read failed after 0 of 4096 at 805306359808: Input/output error + /dev/mainvg/thin_archive: read failed after 0 of 4096 at 0: Input/output error + /dev/mainvg/thin_archive: read failed after 0 of 4096 at 4096: Input/output error lvs - LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert - thin_archive mainvg Vwi-aotz- 500.00g thin_pool 94.65 - thin_rsnapshot mainvg Vwi-aotz- 1.50t thin_pool 94.01 - thin_pool mainvg twi-a-tz- 3.00t 71.65 + LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert + thin_archive mainvg Vwi-aotz- 500.00g thin_pool 94.65 + thin_rsnapshot mainvg Vwi-aotz- 1.50t thin_pool 94.01 + thin_pool mainvg twi-a-tz- 3.00t 71.65 lvresize -L 2T /dev/mapper/mainvg-thin_rsnapshot - /dev/mainvg/thin_rsnapshot: read failed after 0 of 4096 at 1649267376128: Input/output error - /dev/mainvg/thin_rsnapshot: read failed after 0 of 4096 at 1649267433472: Input/output error - /dev/mainvg/thin_archive: read failed after 0 of 4096 at 536870846464: Input/output error - /dev/mainvg/thin_archive: read failed after 0 of 4096 at 536870903808: Input/output error - Extending logical volume thin_rsnapshot to 2.00 TiB - Logical volume thin_rsnapshot successfully resized + /dev/mainvg/thin_rsnapshot: read failed after 0 of 4096 at 1649267376128: Input/output error + /dev/mainvg
[Bug 1089195] Re: linux-headers will eat your inodes on LTS.
My workaround:
dpkg --get-selections | grep 'linux-'
dpkg --get-selections | awk '/linux-(headers|image)-[0-9]\./ { print $1 }' |
grep -v "$(uname -r | sed -e 's/-generic//')" | sort -r -V -t- -k3 | tail -n+4
| xargs -r apt-get -qq -y purge
apt-get -qq -y install linux-{headers,image}-$(uname -r)
dpkg --get-selections | grep 'linux-'
# (optional)
# apt-get -qq -y install linux-{headers,image}-generic-lts-utopic 2>/dev/null
|| apt-get -qq -y install linux-{headers,image}-generic-lts-trusty
Until a backport is available for LTS 14.04/12.04 see
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1267059
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1089195
Title:
linux-headers will eat your inodes on LTS.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1089195/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1492146] Re: igb Detected Tx Unit Hang
This bug should be a top priority because people will suffer from it as soon as
they reboot
their 14.04 LTS with an Intel Gigabit NIC and the "current" Utopic kernel
(3.16.0-48-generic).
I had the same problem with HP ProLiant DL380e Gen8 which an Intel I350 Gigabit
NIC
(Hewlett-Packard Company Ethernet 1Gb 4-port 366i Adapter)
It was hard to get a shell with 30-50% packets drop and igb driver resetting
ALL NICs...
"blind-typing" on the shell and wait 1-2 minutes to get the output... of dmesg
;-)
I updated the kernel of 14.04 LTS from Utopic to Vivid and everything is
working again.
Workaround is:
screen -S kernel
apt-get -y purge linux-{headers,image,image-extra}-3.16.0-48-generic
apt-get -y install linux-image-generic-lts-vivid linux-headers-generic-lts-vivid
reboot
Output of dmesg:
igb :02:00.1 em2: igb: em2 NIC Link is Up 1000 Mbps Full Duplex, Flow
Control: RX
igb :02:00.1: Detected Tx Unit Hang
Tx Queue <3>
TDH <0>
TDT <0>
next_to_use <4>
next_to_clean<0>
buffer_info[next_to_clean]
time_stamp <100039540>
next_to_watch
jiffies <1000397b6>
desc.status <0>
igb :02:00.1 em2: Reset adapter
igb :02:00.2 em3: Reset adapter
igb :02:00.0 em1: Reset adapter
igb :02:00.0 em1: igb: em1 NIC Link is Up 100 Mbps Full Duplex, Flow
Control: RX
igb :02:00.1 em2: igb: em2 NIC Link is Up 1000 Mbps Full Duplex, Flow
Control: RX
igb :02:00.1: Detected Tx Unit Hang
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492146
Title:
igb Detected Tx Unit Hang
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1492146/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1488024] Re: [Regression] From 3.16.0-45 to -47: Intel IGB Tx Unit Hang network adapter reset problem prevents stable network connection
Same bug as https://bugs.launchpad.net/ubuntu/+source/linux-lts- utopic/+bug/1492146 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1488024 Title: [Regression] From 3.16.0-45 to -47: Intel IGB Tx Unit Hang network adapter reset problem prevents stable network connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1488024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1492146] Re: igb Detected Tx Unit Hang
Same bug as https://bugs.launchpad.net/ubuntu/+source/linux-lts- utopic/+bug/1488024 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1492146 Title: igb Detected Tx Unit Hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1492146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1492146] Re: igb Detected Tx Unit Hang
Maybe it's another kernel regression with Intel NIC and TSO so you can try this : # tso => tcp-segmentation-offload # gso => generic-segmentation-offload # gro => generic-receive-offload # sg => scatter-gather # ufo => udp-fragmentation-offload (Cannot change) # lro => large-receive-offload (Cannot change) ethtool -K em1 tso off gso off gro off sg off ethtool -K em2 tso off gso off gro off sg off ethtool -K em3 tso off gso off gro off sg off ethtool -K em4 tso off gso off gro off sg off # ethtool -K eth0 tso off gso off gro off sg off # ... Add this to each iface in /etc/network/interfaces pre-up /sbin/ethtool -K $IFACE tso off gso off gro off sg off || true -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1492146 Title: igb Detected Tx Unit Hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1492146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1492146] Re: igb Detected Tx Unit Hang
If directly related to igb module maybe this LP: #1465653 https://lists.ubuntu.com/archives/kernel-team/2015-June/058671.html https://lists.ubuntu.com/archives/kernel-team/2015-June/058586.html https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465653 if not directly related to igb modules maybe something linked to hv_netvsc (Microsot Hyper-V Network Virtual Service Consumer) LP: #1454892 http://lists.openwall.net/netdev/2015/09/01/18 http://marc.info/?l=linux-netdev&m=140900971718712&w=2 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1454892 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1492146 Title: igb Detected Tx Unit Hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1492146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1492146] Re: igb Detected Tx Unit Hang
@boot0user I agree with you. The best workaround for now is to update
kernel to Vivid!
# Physical Server (with EFI):
sudo apt-get -y purge linux-{headers,image}-3.16.0-48-generic
sudo apt-get -y install linux-signed-generic-lts-vivid
sudo reboot
uname -r # 3.19.0-26-generic
sudo apt-get -y purge linux-signed-generic-lts-utopic
sudo apt-get -y purge linux-{image,headers}-generic-lts-utopic
# Physical Server (without EFI, but signed is also fine):
sudo apt-get -y purge linux-{headers,image}-3.16.0-48-generic
sudo apt-get -y install linux-generic-lts-vivid
sudo reboot
uname -r # 3.19.0-26-generic
sudo apt-get -y purge linux-generic-lts-utopic
sudo apt-get -y purge linux-{image,headers}-generic-lts-utopic
# Virtual Server:
sudo apt-get -y purge linux-{headers,image,image-extra}-3.16.0-48-generic
sudo apt-get -y install linux-virtual-lts-vivid
sudo reboot
uname -r # 3.19.0-26-generic
sudo apt-get -y purge linux-virtual-lts-utopic
sudo apt-get -y purge linux-{image,headers}-virtual-lts-utopic
# (optional)
# If you want to clean old kernels after the reboot (issue 1267059, 1089195) :
dpkg --get-selections | awk '/linux-(headers|image)-[0-9]\./ { print $1 }' \
| sort -r -V -t- -k3 | tail -n+4 \
| grep -v "$(uname -r | sed -e 's/-generic//')" \
| xargs -r apt-get -qq -y purge
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492146
Title:
igb Detected Tx Unit Hang
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1492146/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1493888] Re: FGLRX incompatible with kernel 4.2
Same problem on iMac15,1 with Radeon R9 M295X Mac Edition and 4.2.0-7-generic (wily / 15.10) Two partial workarounds: - downgrade to 4.1.0-3-generic and install fglrx-updates but bluetooth will not work --broken with this kernel* http://www.spinics.net/lists/linux-bluetooth/msg64098.html - use 4.2.0-7-generic but remove fglrx-updates (fglrx-amdcccle etc.) bluetooth will work but no radeon hardware acceleration (No Steam, etc.) In my case I need to choose between bluetooth devies and 3d graphics (radeaon) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1493888 Title: FGLRX incompatible with kernel 4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1493888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1495442] [NEW] XFS: kernel hangs multiple times in xlog_cil_force_lsn
Public bug reported: Ubuntu 14.04.3 LTS with Kernel 3.19.0-26-generic One of our servers running rsnapshot and nfs-kernel-server on XFS partitions crashed or hanged two sundays in a raw. Kernel 3.19.0-26-generic hangs multiple times (same time) in xlog_cil_force_lsn (XFS). I assume this bug is not related with bug report 979498. I had also this issue with kernel 3.16.0-46-generic or 3.13.0-57-generic but I have no log during the crash to determine which of the above kernel was running. I switched to kernel 3.19.0-26-generic because 3.16.0-48-generic was not working well with Intel Gigabit -- tx hang (bug 1492146) INFO: task kthreadd:2 blocked for more than 120 seconds. Tainted: G C 3.19.0-26-generic #28~14.04.1-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. kthreaddD 8802362eb3a8 0 2 0 0x 8802362eb3a8 8802362c09d0 00013e80 8802362ebfd8 00013e80 880235c28000 8802362c09d0 88020001 8802362eb500 7fff 8802362eb4f8 8802362c09d0 Call Trace: [] schedule+0x29/0x70 [] schedule_timeout+0x20c/0x280 [] ? update_curr+0xe4/0x180 [] wait_for_completion+0xa4/0x170 [] ? wake_up_state+0x20/0x20 [] flush_work+0xed/0x1c0 [] ? destroy_worker+0x90/0x90 [] xlog_cil_force_lsn+0x7e/0x1f0 [xfs] [] ? __free_pages+0x27/0x30 [] ? __free_slab+0xd0/0x1f0 [] _xfs_log_force_lsn+0x5e/0x2d0 [xfs] [] xfs_log_force_lsn+0x2e/0x90 [xfs] [] ? xfs_iunpin_wait+0x19/0x20 [xfs] [] __xfs_iunpin_wait+0x8d/0x120 [xfs] [] ? autoremove_wake_function+0x40/0x40 [] xfs_iunpin_wait+0x19/0x20 [xfs] [] xfs_reclaim_inode+0x7c/0x340 [xfs] [] xfs_reclaim_inodes_ag+0x257/0x370 [xfs] [] xfs_reclaim_inodes_nr+0x33/0x40 [xfs] [] xfs_fs_free_cached_objects+0x15/0x20 [xfs] [] super_cache_scan+0x169/0x170 [] shrink_node_slabs+0x1d6/0x370 [] shrink_zone+0x20a/0x240 [] do_try_to_free_pages+0x155/0x440 [] ? zone_watermark_ok+0x1f/0x30 [] try_to_free_pages+0xba/0x150 [] __alloc_pages_nodemask+0x61b/0xa60 [] alloc_kmem_pages_node+0x6a/0x130 [] ? copy_process.part.26+0xf3/0x1c00 [] copy_process.part.26+0x113/0x1c00 [] ? dequeue_task_fair+0x44e/0x660 [] ? put_prev_entity+0x31/0x3f0 [] ? pick_next_task_fair+0x19c/0x880 [] ? kthread_create_on_node+0x1c0/0x1c0 [] ? put_prev_task_fair+0x2f/0x50 [] do_fork+0xd5/0x340 [] kernel_thread+0x26/0x30 [] kthreadd+0x15a/0x1c0 [] ? kthread_create_on_cpu+0x60/0x60 [] ret_from_fork+0x58/0x90 [] ? kthread_create_on_cpu+0x60/0x60 10:17:01 xyz CRON[59020]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) 11:17:01 xyz CRON[59177]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) 12:00:01 xyz CRON[59282]: (root) CMD (/usr/bin/rsnapshot -c /etc/rsnapshot.conf hourly) 12:03:05 xyz kernel: [616881.456247] INFO: task kthreadd:2 blocked for more than 120 seconds. 12:03:05 xyz kernel: [616881.456587] Tainted: G C 3.19.0-26-generic #28~14.04.1-Ubuntu ... 12:03:05 xyz kernel: [616881.457934] INFO: task kswapd0:57 blocked for more than 120 seconds. 12:03:05 xyz kernel: [616881.458271] Tainted: G C 3.19.0-26-generic #28~14.04.1-Ubuntu ... 12:03:05 xyz kernel: [616881.485629] INFO: task nfsd:2002 blocked for more than 120 seconds. 12:03:05 xyz kernel: [616881.492761] Tainted: G C 3.19.0-26-generic #28~14.04.1-Ubuntu ... 12:03:05 xyz kernel: [616881.523050] INFO: task snmpd:2155 blocked for more than 120 seconds. 12:03:05 xyz kernel: [616881.530783] Tainted: G C 3.19.0-26-generic #28~14.04.1-Ubuntu ... 12:03:05 xyz kernel: [616881.562789] INFO: task kworker/1:0:59030 blocked for more than 120 seconds. 12:03:05 xyz kernel: [616881.571082] Tainted: G C 3.19.0-26-generic #28~14.04.1-Ubuntu ... 12:03:05 xyz kernel: [616881.605747] INFO: task kworker/3:1H:59110 blocked for more than 120 seconds. 12:03:05 xyz kernel: [616881.615112] Tainted: G C 3.19.0-26-generic #28~14.04.1-Ubuntu ... 12:03:05 xyz kernel: [616881.652107] INFO: task rm:59284 blocked for more than 120 seconds. 12:03:05 xyz kernel: [616881.661441] Tainted: G C 3.19.0-26-generic #28~14.04.1-Ubuntu ... 12:05:05 xyz kernel: [617001.782228] INFO: task kswapd0:57 blocked for more than 120 seconds. 12:05:05 xyz kernel: [617001.791580] Tainted: G C 3.19.0-26-generic #28~14.04.1-Ubuntu ... 12:05:05 xyz kernel: [617001.828636] INFO: task irqbalance:1353 blocked for more than 120 seconds. 12:05:05 xyz kernel: [617001.838019] Tainted: G C 3.19.0-26-generic #28~14.04.1-Ubuntu ... 12:05:05 xyz kernel: [617001.875425] INFO: task nfsd:2002 blocked for more than 120 seconds. 12:05:05 xyz kernel: [617001.884799] Tainted: G C 3.19.0-26-generic #28~14.04.1-Ubuntu ... REFERENCES http://marc.info/?l=linux-xfs&w=2&r=1&s=xlog_cil_force_lsn%2B0x7e%2F0x1f0
[Bug 1495442] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1495442/+attachment/4463952/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1495442 Title: XFS: kernel hangs multiple times in xlog_cil_force_lsn To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1495442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1495442] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1495442/+attachment/4463956/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1495442 Title: XFS: kernel hangs multiple times in xlog_cil_force_lsn To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1495442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1495442] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1495442/+attachment/4463955/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1495442 Title: XFS: kernel hangs multiple times in xlog_cil_force_lsn To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1495442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1495442] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1495442/+attachment/4463958/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1495442 Title: XFS: kernel hangs multiple times in xlog_cil_force_lsn To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1495442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1495442] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1495442/+attachment/4463957/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1495442 Title: XFS: kernel hangs multiple times in xlog_cil_force_lsn To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1495442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1495442] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1495442/+attachment/4463954/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1495442 Title: XFS: kernel hangs multiple times in xlog_cil_force_lsn To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1495442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1495442] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1495442/+attachment/4463951/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1495442 Title: XFS: kernel hangs multiple times in xlog_cil_force_lsn To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1495442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1495442] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1495442/+attachment/4463950/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1495442 Title: XFS: kernel hangs multiple times in xlog_cil_force_lsn To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1495442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1495442] Re: XFS: kernel hangs multiple times in xlog_cil_force_lsn
apport information ** Tags added: apport-collected staging trusty ** Description changed: Ubuntu 14.04.3 LTS with Kernel 3.19.0-26-generic One of our servers running rsnapshot and nfs-kernel-server on XFS partitions crashed or hanged two sundays in a raw. Kernel 3.19.0-26-generic hangs multiple times (same time) in xlog_cil_force_lsn (XFS). I assume this bug is not related with bug report 979498. I had also this issue with kernel 3.16.0-46-generic or 3.13.0-57-generic but I have no log during the crash to determine which of the above kernel was running. I switched to kernel 3.19.0-26-generic because 3.16.0-48-generic was not working well with Intel Gigabit -- tx hang (bug 1492146) INFO: task kthreadd:2 blocked for more than 120 seconds. Tainted: G C 3.19.0-26-generic #28~14.04.1-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. kthreaddD 8802362eb3a8 0 2 0 0x 8802362eb3a8 8802362c09d0 00013e80 8802362ebfd8 00013e80 880235c28000 8802362c09d0 88020001 8802362eb500 7fff 8802362eb4f8 8802362c09d0 Call Trace: [] schedule+0x29/0x70 [] schedule_timeout+0x20c/0x280 [] ? update_curr+0xe4/0x180 [] wait_for_completion+0xa4/0x170 [] ? wake_up_state+0x20/0x20 [] flush_work+0xed/0x1c0 [] ? destroy_worker+0x90/0x90 [] xlog_cil_force_lsn+0x7e/0x1f0 [xfs] [] ? __free_pages+0x27/0x30 [] ? __free_slab+0xd0/0x1f0 [] _xfs_log_force_lsn+0x5e/0x2d0 [xfs] [] xfs_log_force_lsn+0x2e/0x90 [xfs] [] ? xfs_iunpin_wait+0x19/0x20 [xfs] [] __xfs_iunpin_wait+0x8d/0x120 [xfs] [] ? autoremove_wake_function+0x40/0x40 [] xfs_iunpin_wait+0x19/0x20 [xfs] [] xfs_reclaim_inode+0x7c/0x340 [xfs] [] xfs_reclaim_inodes_ag+0x257/0x370 [xfs] [] xfs_reclaim_inodes_nr+0x33/0x40 [xfs] [] xfs_fs_free_cached_objects+0x15/0x20 [xfs] [] super_cache_scan+0x169/0x170 [] shrink_node_slabs+0x1d6/0x370 [] shrink_zone+0x20a/0x240 [] do_try_to_free_pages+0x155/0x440 [] ? zone_watermark_ok+0x1f/0x30 [] try_to_free_pages+0xba/0x150 [] __alloc_pages_nodemask+0x61b/0xa60 [] alloc_kmem_pages_node+0x6a/0x130 [] ? copy_process.part.26+0xf3/0x1c00 [] copy_process.part.26+0x113/0x1c00 [] ? dequeue_task_fair+0x44e/0x660 [] ? put_prev_entity+0x31/0x3f0 [] ? pick_next_task_fair+0x19c/0x880 [] ? kthread_create_on_node+0x1c0/0x1c0 [] ? put_prev_task_fair+0x2f/0x50 [] do_fork+0xd5/0x340 [] kernel_thread+0x26/0x30 [] kthreadd+0x15a/0x1c0 [] ? kthread_create_on_cpu+0x60/0x60 [] ret_from_fork+0x58/0x90 [] ? kthread_create_on_cpu+0x60/0x60 10:17:01 xyz CRON[59020]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) 11:17:01 xyz CRON[59177]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) 12:00:01 xyz CRON[59282]: (root) CMD (/usr/bin/rsnapshot -c /etc/rsnapshot.conf hourly) 12:03:05 xyz kernel: [616881.456247] INFO: task kthreadd:2 blocked for more than 120 seconds. 12:03:05 xyz kernel: [616881.456587] Tainted: G C 3.19.0-26-generic #28~14.04.1-Ubuntu ... 12:03:05 xyz kernel: [616881.457934] INFO: task kswapd0:57 blocked for more than 120 seconds. 12:03:05 xyz kernel: [616881.458271] Tainted: G C 3.19.0-26-generic #28~14.04.1-Ubuntu ... 12:03:05 xyz kernel: [616881.485629] INFO: task nfsd:2002 blocked for more than 120 seconds. 12:03:05 xyz kernel: [616881.492761] Tainted: G C 3.19.0-26-generic #28~14.04.1-Ubuntu ... 12:03:05 xyz kernel: [616881.523050] INFO: task snmpd:2155 blocked for more than 120 seconds. 12:03:05 xyz kernel: [616881.530783] Tainted: G C 3.19.0-26-generic #28~14.04.1-Ubuntu ... 12:03:05 xyz kernel: [616881.562789] INFO: task kworker/1:0:59030 blocked for more than 120 seconds. 12:03:05 xyz kernel: [616881.571082] Tainted: G C 3.19.0-26-generic #28~14.04.1-Ubuntu ... 12:03:05 xyz kernel: [616881.605747] INFO: task kworker/3:1H:59110 blocked for more than 120 seconds. 12:03:05 xyz kernel: [616881.615112] Tainted: G C 3.19.0-26-generic #28~14.04.1-Ubuntu ... 12:03:05 xyz kernel: [616881.652107] INFO: task rm:59284 blocked for more than 120 seconds. 12:03:05 xyz kernel: [616881.661441] Tainted: G C 3.19.0-26-generic #28~14.04.1-Ubuntu ... 12:05:05 xyz kernel: [617001.782228] INFO: task kswapd0:57 blocked for more than 120 seconds. 12:05:05 xyz kernel: [617001.791580] Tainted: G C 3.19.0-26-generic #28~14.04.1-Ubuntu ... 12:05:05 xyz kernel: [617001.828636] INFO: task irqbalance:1353 blocked for more than 120 seconds. 12:05:05 xyz kernel: [617001.838019] Tainted: G C 3.19.0-26-generic #28~14.04.1-Ubuntu ... 12:05:05 xyz kernel: [617001.8
[Bug 1495442] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1495442/+attachment/4463953/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1495442 Title: XFS: kernel hangs multiple times in xlog_cil_force_lsn To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1495442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1495442] Re: XFS: kernel hangs multiple times in xlog_cil_force_lsn
The bug doesn't seem to impact 3.13.0-63-generic. (the server is in production we don't really want to test 4.2 unstable) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1495442 Title: XFS: kernel hangs multiple times in xlog_cil_force_lsn To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1495442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1413540] Re: Trusty soft lockup issues with nested KVM
I still have the same issue with kernel 3.16.0-36-generic or 3.13.0-51-generic (proposed-updates) # KVM HOST (3.16.0-36-generic) sudo apt-get install linux-signed-generic-lts-utopic/trusty-proposed # KVM GUEST (3.16.0-36-generic) sudo apt-get install linux-virtual-lts-utopic/trusty-proposed apt-get install cloud-installer cloud-install [ 1196.920613] kvm: vmptrld (null)/7800 failed [ 1196.920953] vmwrite error: reg 401e value 31 (err 1) [ 1196.921243] CPU: 23 PID: 5240 Comm: qemu-system-x86 Not tainted 3.16.0-36-generic #48~14.04.1-Ubuntu [ 1196.921244] Hardware name: HP ProLiant DL380 Gen9, BIOS P89 11/03/2014 [ 1196.921245] 88202018fb58 81764a5f 880fe496 [ 1196.921248] 88202018fb68 c0a9320d 88202018fb78 c0a878bf [ 1196.921250] 88202018fba8 c0a8e1cf 880fe496 [ 1196.921252] Call Trace: [ 1196.921262] [] dump_stack+0x45/0x56 [ 1196.921277] [] vmwrite_error+0x2c/0x2e [kvm_intel] [ 1196.921280] [] vmcs_writel+0x1f/0x30 [kvm_intel] [ 1196.921283] [] free_nested.part.73+0x5f/0x170 [kvm_intel] [ 1196.921286] [] vmx_free_vcpu+0x33/0x70 [kvm_intel] [ 1196.921305] [] kvm_arch_vcpu_free+0x44/0x50 [kvm] [ 1196.921312] [] kvm_arch_destroy_vm+0xf2/0x1f0 [kvm] [ 1196.921318] [] ? synchronize_srcu+0x1d/0x20 [ 1196.921323] [] kvm_put_kvm+0x10e/0x220 [kvm] [ 1196.921328] [] kvm_vcpu_release+0x18/0x20 [kvm] [ 1196.921331] [] __fput+0xe4/0x220 [ 1196.921333] [] fput+0xe/0x10 [ 1196.921337] [] task_work_run+0xc4/0xe0 [ 1196.921342] [] do_exit+0x2b8/0xa60 [ 1196.921345] [] ? __unqueue_futex+0x32/0x70 [ 1196.921347] [] ? futex_wait+0x126/0x290 [ 1196.921349] [] ? check_preempt_curr+0x85/0xa0 [ 1196.921351] [] do_group_exit+0x3f/0xa0 [ 1196.921353] [] get_signal_to_deliver+0x1d0/0x6f0 [ 1196.921357] [] do_signal+0x48/0xad0 [ 1196.921359] [] ? __switch_to+0x167/0x590 [ 1196.921361] [] do_notify_resume+0x69/0xb0 [ 1196.921364] [] int_signal+0x12/0x17 [ 1196.921365] vmwrite error: reg 2800 value (err -255) [ 1196.921733] CPU: 23 PID: 5240 Comm: qemu-system-x86 Not tainted 3.16.0-36-generic #48~14.04.1-Ubuntu [ 1196.921734] Hardware name: HP ProLiant DL380 Gen9, BIOS P89 11/03/2014 [ 1196.921735] 88202018fb58 81764a5f 880fe496 [ 1196.921736] 88202018fb68 c0a9320d 88202018fb78 c0a878bf [ 1196.921737] 88202018fba8 c0a8e1e0 880fe496 [ 1196.921739] Call Trace: [ 1196.921741] [] dump_stack+0x45/0x56 [ 1196.921744] [] vmwrite_error+0x2c/0x2e [kvm_intel] [ 1196.921746] [] vmcs_writel+0x1f/0x30 [kvm_intel] [ 1196.921748] [] free_nested.part.73+0x70/0x170 [kvm_intel] [ 1196.921751] [] vmx_free_vcpu+0x33/0x70 [kvm_intel] [ 1196.921757] [] kvm_arch_vcpu_free+0x44/0x50 [kvm] [ 1196.921763] [] kvm_arch_destroy_vm+0xf2/0x1f0 [kvm] [ 1196.921765] [] ? synchronize_srcu+0x1d/0x20 [ 1196.921770] [] kvm_put_kvm+0x10e/0x220 [kvm] [ 1196.921774] [] kvm_vcpu_release+0x18/0x20 [kvm] [ 1196.921775] [] __fput+0xe4/0x220 [ 1196.921777] [] fput+0xe/0x10 [ 1196.921778] [] task_work_run+0xc4/0xe0 [ 1196.921780] [] do_exit+0x2b8/0xa60 [ 1196.921782] [] ? __unqueue_futex+0x32/0x70 [ 1196.921783] [] ? futex_wait+0x126/0x290 [ 1196.921784] [] ? check_preempt_curr+0x85/0xa0 [ 1196.921786] [] do_group_exit+0x3f/0xa0 [ 1196.921788] [] get_signal_to_deliver+0x1d0/0x6f0 [ 1196.921790] [] do_signal+0x48/0xad0 [ 1196.921791] [] ? __switch_to+0x167/0x590 [ 1196.921793] [] do_notify_resume+0x69/0xb0 [ 1196.921795] [] int_signal+0x12/0x17 [ 1270.766540] device vnet3 entered promiscuous mode [ 1270.865885] device vnet4 entered promiscuous mode [ 1273.824576] kvm: zapping shadow pages for mmio generation wraparound [ 1447.725335] kvm [6152]: vcpu0 unhandled rdmsr: 0x606 uvt-kvm create \ --memory 16384 \ --disk 100 \ --cpu 2 \ --ssh-public-key-file uvt-authorized_keys \ --template uvt-template.xml \ test release=trusty arch=amd64 2 SandyBridge Intel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1413540 Title: Trusty soft lockup issues with nested KVM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1413540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
