The shutdown/suspend problem stopped for the after disabling the TTL
chip in the security tab in the BIOS
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2059738
Title:
Kernel 6.8 - Shutd
Today I tried disabling the bluetooth in the BIOS, without success. I
also tried the Mainline Kernel 6.10 and LTS Kernel 6.6.47, also without
success.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.
It happens with my ThinkPad T460 as well. It apperars to be a problem in
6.8 Kernel, as described in this workaround:
https://github.com/pop-os/pop/issues/3269#issuecomment-2282823931
The problem do not manifest in Fedora 40 with Kernel 6.10 or in Ubuntu
23.10 with older Kernel.
** Bug watch add
It looks like this bug is related to leaking of the PKRU bit.
Applying the patch from Proxmox mentioned in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036675
resolves the issue
** Summary changed:
- 5.15.0-76: Qemu live migration causes VMs to crash but works with HWE kernel
+ 5.15.0-7
I'm also affected with an iGPU on my amd cpu.
I attached my 'lspci -'. I'm currently using the working '-32'
kernel.
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+attachment/5655908/+files/lspci.txt
--
You received this bug notification b
I can confirm that disabling PSR fixes the problem on my laptop (see bug
#2008053). Thanks a lot to @vanvugt for suggesting the workaround. When
there is a real fix for this issue in Ubuntu 22.04, I will try to re-
enable PSR and check if it works.
--
You received this bug notification because yo
About the 5G support:
nm-applet reports LTE, but it does work on 5G.
I just got 400+ Mbps yesterday when testing, which obviously is not LTE.
Might just be a naming issue there.
The sleep issue persists however, latest tests with 6.1.12 are the same as
before.
--
You received this bug notificati
Regarding
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990700/comments/13:
I'm still seeing the same issue on Ubuntu 22.10 with mainline kernel 6.1.8 and
6.1.9.
Did this somehow get kicked again, or am I misinterpreting the kernel-versions?
Dmesg states:
[ 93.276679] mtk_t7xx :57:
Could be closed meanwhile. I needed to shut kvm down on this system and
can not get/generate the required reports/infos any more. It has been
working with e1000 drivers last.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I also can confirm that this kernel version is now working as expected.
thanks for quick solution!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1996740
Title:
5.15.0-53-generic no lon
Public bug reported:
/usr/share/doc/ubuntu-fan/README.gz (ubuntu-fan/README) reads:
"More information on the Fan, including more detailed configuration
information, can be found at http://www.ubuntu.com/fan.";
However, the aforementioned URL (with and without trailing dot) does not exist.
Is thi
From analysis of our setup at work, it should be the JMicron SATA Controller.
It works with kernel 5.8 (Ubuntu 20.04) and fails with kernel 5.15 (Ubuntu
22.04).
No other kernel versions tested yet.
We already contacted our manufacturer (Icy Dock), but no feedback yet.
--
You received this bug n
#7 0x77d8ee40 in __libc_start_main () from
/lib/x86_64-linux-gnu/libc.so.6
#8 0x5795 in ?? ()
I have compiled libusb-1.0.26 into my $HOME and pointed
LD_LIBRARY_PATH to it. Then I get the expected result:
ink -p usb
ink 0.5.3 (c) 2018 Markus Heinz
hp deskjet 5
/libc.so.6
#8 0x5795 in ?? ()
I have compiled libusb-1.0.26 into my $HOME and pointed LD_LIBRARY_PATH
to it. Then I get the expected result:
ink -p usb
ink 0.5.3 (c) 2018 Markus Heinz
hp deskjet 5550
Black: 0%
Color: 0
Hi Juerg,
Installing the new firmware fixes it.Got some error messages but now I am on
5-13.0-28
Thank you for the support.
** Attachment added: "Screenshot_2022-02-09_22-51-01.png"
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1960159/+attachment/5560088/+files/Screenshot_20
Confirming this problem.
The work-around does not work for me.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-465 in Ubuntu.
https://bugs.launchpad.net/bugs/1933880
Title:
systemd-logind crash when suspend with
The relevant part of the kern.log is already within the description. As
the server is in production we needed to return to previous kernel.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, whic
Public bug reported:
After upgrading a machine from Ubuntu Bionic to Ubuntu Focal yesterday,
the following error message showed up in the syslog:
Oct 2 23:14:52 desktop01 dbus-daemon[1764]: [session uid=0 pid=1760]
Activated service 'org.bluez.obex' failed: Failed to execute program
org.bluez.ob
** Description changed:
Crash dialog show up on reboot right after kernel update + reinstalling
using:
apt purge nvidia-driver-460 # enforce a fresh install
apt install nvidia-driver-460
+
+ Besides the crash dialog, I did not notice any problems so far; e.g. no
+ visual impact, nvidia
Public bug reported:
Crash dialog show up on reboot right after kernel update + reinstalling
using:
apt purge nvidia-driver-460 # enforce a fresh install
apt install nvidia-driver-460
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-kernel-source-460 460.91.03-0ubuntu0.20.04.1
Pr
I do see an update of bluez to 5.58
https://git.launchpad.net/ubuntu/+source/bluez/commit/?id=f0877af285d9360c02762de34a79ed11c72a84ca
5.58, but no changes that would add meshctl.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ub
I do see an update to 5.88 with
https://git.launchpad.net/ubuntu/+source/bluez/commit/?id=f0877af285d9360c02762de34a79ed11c72a84ca,
but I do not see the binary meshctl being added.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in U
Public bug reported:
bluez has added a new tool for BT mesh handling.
Debian has a new binary package: https://packages.debian.org/bullseye
/bluez-meshd
Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973579
** Affects: bluez (Ubuntu)
Importance: Undecided
Status: Ne
: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: markus 1534 F pulseaudio
Date: Sun Mar 7 16:03:46 2021
ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie
sollten es nochmal installieren, bevor Sie die Konfiguration versuchen
Hi Juul,
these two flags are only present when SVM is enabled (which is unfortunately
default in Ubuntu).
We worked around this issue by modifying the target domain XML in live
migration to disable both flags if they are not present on the source side
(e.g. host running with older kernel).
I am
On focal (5.4.0-56-generic) we are starting to see massive file system
corruptions on systems updated to this kernel version.
These systems are using LVM with discards and thin provisioning on 6 or 8 NVMe
drives in a RAID10 near configuration. We are currently downgrading all systems
back to 5.4
Public bug reported:
While I have found previous reports of this check failing, they are all
resolved years ago.
So I guess this is something for upstream.
device-mapper: btree spine: node_check failed: csum 544691913 != wanted
1983069109
[ cut here ]
kernel BUG at drive
It seems one of the patches also introduced a regression:
* lp-1887490-cpu_map-Add-missing-AMD-SVM-features.patch
adds various SVM-related flags. Specifically npt and nrip-save are now expected
to be present by default as shown in the updated testdata.
This however breaks migration from instances
Same tests as above. Still working as intended
** Tags removed: patch verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Well, for me it's more or less a noop because we have been running a
version with these patches for some time now. But nevertheless I haven't
encountered any problems using your build/patch series. Host
capabilities are correctly detected as EPYC-Rome and I can (still) start
an instance with the EP
0ubuntu1.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: markus 1653 F pulseaudio
/dev/snd/controlC0: markus 1653 F pulseaudio
CurrentDesktop: Unity
Date: Tue Aug 4 21:24:03 2015
HibernationDevice: RESUME=UUI
Note the fixup patch removing monitor flag:
https://gitlab.com/libvirt/libvirt/-/commit/3bf6f9fe22dfbd3c1dcc614b31f2f4fe8b71a2f2
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1887490
Tit
The new qemu version works as expected together with 5.4.0-49 kernel
required for xsaves
# grep -e 'model name' -e 'flags' /proc/cpuinfo
model name : AMD EPYC-Rome Processor
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush mmx fxsr sse sse2 h
Thanks. It does not look like the "regression" preventing proposed
migration is caused by the qemu changes.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1887490
Title:
Add/Backport EPY
The second one is: https://bugs.launchpad.net/qemu/+bug/1849644
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1887490
Title:
Add/Backport EPYC-v3 and EPYC-Rome CPU model
Status in libv
Actually no. It builds and does not have any downsides, but does not
resolve the issue. Sorry for that. When I looked at the history of
cpu_map and this patch, I did not see that it would require further
patches to actually make it work.
So that would leave it at these four patches:
Add-pschange-m
Thanks for the update. It looks like your libvirt build fails.
Most likely due to the following patch missing:
https://github.com/libvirt/libvirt/commit/58691208e2063285d981a620873d48ddf8df8be5
That patch adds the CooperLake test data (wrongly as CascadeLake-
Server), which is later fixed in
ht
With the 5.4.0-49 from focal-proposed the xsaves flag can now be passed
into instances.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1887490
Title:
Add/Backport EPYC-v3 and EPYC-Rome C
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1887490
Title:
Add/Backport EPYC-v3 and EPYC-Rome CPU mod
Is there anything I can do, regarding the backport of 52297436199d into
focal kernel?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1887490
Title:
Add/Backport EPYC-v3 and EPYC-Rome CPU
I see the same problem with Ubuntu 18 and Kernel 4.15.0-115 and 117.
Massive trouble on ocfs2 based mounts. Writing isn't possible. A serious
issue as all clustered systems are not working. Processes trying to
write on the filesystem are hanging without any chance to kill them
except a reboot.
Lin
Plain qemu with the EPYC-Rome model works without any problems. I
already get xsave, xsaveopt, xsavec and xsaveerptr with the current
focal kernel, which also means that gcc finally uses znver1 (for v3) and
znver2 (for Rome) optimizations.
Libvirt would require cherrypicking a number of commits to
Kernel 5.4.0-1012.12 fixes the issue.
** Changed in: linux-raspi (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/1880607
Title:
Ra
Public bug reported:
After upgrading my Raspberry Pi 4 from Eoan to Focal (arm64), it now
runs awfully slow with dmesg showing loots of these warnings:
[ 3821.602211] [ cut here ]
[ 3821.603018] WARNING: CPU: 2 PID: 25391 at drivers/mmc/host/sdhci.c:1101
sdhci_prepare
fix was included in 4.4.0-177.207 (xenial), 4.15.0-92.93 (bionic),
5.3.0-46.38 (eoan), 5.4.0-15.18 (focal)
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubu
BT device is in the wrong mode / on the wrong profile.
Solution is here: https://askubuntu.com/questions/889737/video-not-
playing-in-web-browser-with-bluetooth-headphones-connected-how-can-i
wget
https://gist.github.com/pylover/d68be364adac5f946887b85e6ed6e7ae/archive/d698974910bbb7d016ec0ad08c1
Patch has been backported to all stable kernel releases, e.g. 4.19:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-4.19.y&id=1fac9f574cd2536abcdd645ee23d35c0e819d7ec
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
** Description changed:
I have Raspberry 4 with USB GPS dongle and use gpsd use the dongle. When
I stop gpsd, kernel throws mem abort and gpsd process is stuck.
$ sudo systemctl status gpsd
● gpsd.service - GPS (Global Positioning System) Daemon
-Loaded: loaded (/etc/systemd/system/
I downgraded gpsd to
$ apt-cache policy gpsd
gpsd:
Installed: 3.17-7
Candidate: 3.17-7
Version table:
*** 3.17-7 500
500 http://ports.ubuntu.com/ubuntu-ports eoan/universe arm64 Packages
100 /var/lib/dpkg/status
And this issue is still occurring.
I've added also latest dme
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1862647/+attachment/5327055/+files/Dependencies.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-raspi2 in Ubuntu.
https://bugs.l
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1862647/+attachment/5327056/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-raspi2 in Ubuntu.
ht
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1862647/+attachment/5327057/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-raspi2 in Ubuntu.
https://bugs.lau
Public bug reported:
I have Raspberry 4 with USB GPS dongle and use gpsd use the dongle. When
I stop gpsd, kernel throws mem abort and gpsd process is stuck.
$ sudo systemctl status gpsd
● gpsd.service - GPS (Global Positioning System) Daemon
Loaded: loaded (/etc/systemd/system/gpsd.service; d
The patch is merged upstream and will be in 5.6.
https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git/commit/?h=dm-5.6&id=4feaef830de7ffdd8352e1fe14ad3bf13c9688f8
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/md?id=e9f8ca0ae7b7bc9a032b42992
Patch posted at
https://www.redhat.com/archives/dm-devel/2020-January/msg00021.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1777398
Title:
dm thin block allocation failure
Status
Had the same issue with an Evoo 11.6" tablet (Atom Cherry Trail, sold by
Walmart) and fixed it by just removing the hid_multitouch kernel module...
Without it, the touch pad works fine for me with Lubuntu 19.04 (with a 5.0.0
kernel)...
--
You received this bug notification because you are a mem
This was fixed in #1847163.
** Changed in: linux-raspi2 (Ubuntu Eoan)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1843207
Title:
Doesn't boo
The DTB is also missing from the package.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1843207
Title:
Doesn't boot on Raspberry Pi 4
Status in linux-raspi2 package in Ubuntu:
Public bug reported:
linux-raspi2 from Eoan (19.10) doesn't boot on Raspberry Pi 4 due to
missing kernel modules for the new hardware components. It would be nice
if these got included. Also it only boots the kernel when the Pi is
configured for 1GB RAM or less. (Then gets stuck on missing root FS
*** This bug is a duplicate of bug 1825699 ***
https://bugs.launchpad.net/bugs/1825699
affected:
find . -iname firmware_id | xargs cat
> PNP: LEN0071 PNP0303
> PNP: LEN2036 PNP0f13
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Unfortunately still present in mainline 5.0.13 kernel:
[ cut here ]
kernel BUG at drivers/md/persistent-data/dm-space-map-disk.c:178!
invalid opcode: [#1] SMP PTI
CPU: 5 PID: 1675751 Comm: kworker/u128:1 Not tainted 5.0.13-050013-generic
#201905051330
Hardware name: Q
Still present in 4.15.0-47-generic even though a number of dm/thin fixes
have been backported
kernel: [1120717.622665] Modules linked in: cpuid xt_CHECKSUM xt_nat
iptable_nat nf_nat_ipv4 dm_snapshot veth dummy bridge nf_conntrack_ipv6
nf_defrag_ipv6 ip6table_filter ip6_tables xt_CT iptable_raw i
Currently testing 5.0.10 as we think the issue is related to thin trying
to reallocate a discarded block not working correctly
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/md?id=cffd425b90147296c627dfb13f7ea8f361d962b2
** Changed in: linux (Ubuntu)
Sta
> Incomplete → Expired
Are you serious? It is happening everyday without the work around. What
information are you missing, dear Janitor?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/157
> When changing the power management behavior for a closed lid (AC and
Battery) to not suspend, I have no issues. I can then dock and undock.
So this would be a work around.
The workaround can even be improved. Only disabling the Suspend on
closed lid for AC is enough to fix the issues. I can then
> when I wanted to start a new session while docked.
I mean a new X session.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1575334
Title:
Docking thinkpad laptop causes a complete sys
I think I'm also affected by this issue (Thinkpad T450s). When changing
the power management behavior for a closed lid (AC and Battery) to not
suspend, I have no issues. I can then dock and undock. So this would be
a work around.
This issue is clearly related to the suspending behavior of a closed
I just installed the 4.15.0.45.47 kernel from the -proposed repo and it
seems to work like a charm :D
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1813902
Title:
Lenovo Thinkpad
Public bug reported:
When notebook is in docking station the kernel crashes after bootup and logon
in GDM.
If notebook is in standalone mode without any external devices connected
everything works.
Tried to step back to Kernel 4.15.0-43-generic and everything works like
a charm.
Description:
There are two different commits of newer date in the current mainline
kernel, which seem to fix timeout problems related to i40e.
i40e: Fix for Tx timeouts when interface is brought up if DCB is enabled
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v4.20-rc3&id=fa38e
This issue is still present. Possibly fixed by upstream commit
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/md?id=a685557fbbc3122ed11e8ad3fa63a11ebc5de8c3
https://www.redhat.com/archives/dm-devel/2018-April/msg00022.html
kernel: [8860597.921484] kernel BUG at
proposed kernel for trusty still resolves this like test-kernel from #7
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1788563
Title:
L1TF mitigation not effective in some CPU and RAM co
still unresolved in 4.19rc3
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1778475
Title:
i40e: restore workaround for removing default MAC filter
Status in linux package in Ubuntu:
I
kernel from #7 resolves this on trusty as well (according to sysfs)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1788563
Title:
L1TF mitigation not effective in some CPU and RAM combin
This happens pretty much on all Ubuntu kernels with the initial L1TF
implementation, so xenial, bionic and cosmic are also affected.
https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.4.154
https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.18.6
--
You received this bug notification
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1789834
Title:
off-by-one bug in L1TF mitigation
Status in linux package in
Public bug reported:
due to an off-by-one bug in the L1TF patch, the "rare" case of systems still
vulnerable
is more frequent.
This typically happens on Nehalem+ destop/entry-level server systems
with 32G memory installed.
Originally this was reported in OpenSUSE, but I can confirm this is also
Maybe keep this in mind: Before I upgraded to the Kernel 4.18.5 I have
created a snapshot. So maybe if someone wants me to do some further
testing I am able to revert the changes and do so.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to l
I really was not expecting that this will work but today I was able to
successfully update the Kernel to 4.18.5. And furthermore for the first
time this machine exist, I was able to reboot and shutdown the system
without killing my hypervisor and rebooting the host.
** Tags added: kernel-fixed-ups
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1787423/+attachment/5176382/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1787423
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1787423/+attachment/5176381/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1787423/+attachment/5176377/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1787423/+attachment/5176379/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1787423/+attachment/5176378/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1787423/+attachment/5176380/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1787423/+attachment/5176383/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1787423/+attachment/5176376/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Tags added: apport-collected bionic
** Description changed:
My problem is, that my Hyper-V Guest (Ubuntu Server 18.04.1) is stuck at
the state "Stopping" when I shut down the guest. When this happens I am
not capable of doing any actions regarding this guest. The only
Public bug reported:
My problem is, that my Hyper-V Guest (Ubuntu Server 18.04.1) is stuck at
the state "Stopping" when I shut down the guest. When this happens I am
not capable of doing any actions regarding this guest. The only solution
is to shutdown the other guests and kill the vmms.exe.
I r
If I'm not mistaken, the fix has been released with the latest kernel
update that was pushed for the L1TF issue. So this bug should be "fix
released"
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
I have the same issue with KDE neon and Nvidia 396.51 on a Dell XPS 15
9570 (GTX 1050 Ti). Restarting sddm fixes the issue but is really
annoying.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-375 in Ubuntu.
https
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1778486
Title:
x86/kvm: fix LAPIC timer drift when gues
Does it make sense to try the mainline kernel, since the error is
obviously fixed with 18.04? Unfortunately, I also do not know how to try
the mainline kernel. Can I test this with a live image (I do not want to
destroy my production machine)? Is the mainline kernel compatible with
17.10?
--
You
Thanks Joseph.
I tested the kernel with OpenBSD and FreeBSD virtual machines and this
patch seems to fix the timing issues.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1778486
Title:
Apparently not, but this was the only mentioning of this bug and the it
can be reproduced just the same way (bonding + vlan)
But after trying the mainline 4.18rc2 kernel, the bug is still present
their. So it needs to be fixed upstream first (again).
For reference:
# uname -a
Linux hostname 4.18
Public bug reported:
OpenBSD guests encounter timing issues when running under bionic kernel.
This issue is actually present since 4.10 and is fixed by:
https://patchwork.kernel.org/patch/10411125/
See also
https://www.spinics.net/lists/kvm/msg161311.html
** Affects: linux (Ubuntu)
Impor
Public bug reported:
Ubuntu Bionic kernel (4.15.0-23) lacks upstream patch for i40e which
results in forced promiscous mode when adding a vlan.
[ 10.847381] i40e :3d:00.0: Error I40E_AQ_RC_EINVAL adding RX filters on
PF, promiscuous mode forced on
Steps to reproduce and patch here:
http
Hi Joseph,
sure, but running an rc- kernel is not ideal for production systems, so I can
only give this limited exposure on a few canary systems.
I hope we can find a way to deterministically trigger this, to confirm a fix.
--
You received this bug notification because you are a member of Kern
g is fixed from
version 18.04 on, so I will update to Xubuntu 18.04.1 soon.
Thank you for your efforts
Markus
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1754759
Title:
LAN connec
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1777398
Title:
dm thin block allocation failure
Status in linux packa
1 - 100 of 357 matches
Mail list logo
