*** This bug is a duplicate of bug 1878045 ***
https://bugs.launchpad.net/bugs/1878045
Fix also mentioned here:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1878045/comments/7
** This bug has been marked a duplicate of bug 1878045
doing dist-upgrade got error related do Broadcom
*** This bug is a duplicate of bug 1878045 ***
https://bugs.launchpad.net/bugs/1878045
The problem is due to 0028-add-support-for-linux-5.6.patch having many
of a/src/src/... instead of a/src/...
Fixing that patch solves this for me.
--
You received this bug notification because you are a
I replace Core2 Duo to ryzen 3.
** 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/1860196
Title:
kernel-5.3.0-26 could
@lou +1
Sorry for my Google translate.
This bug is very many years old. This is *Bug 12309* !!! Why didn't anyone
remember?
I'm tired of him. Was in the early 2010s for 512 MB of RAM. Was in the early
2010s for 512 MB of RAM. and 2 GB of RAM. Mid 2010s with 4GB of RAM. And for
the past
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@kasper93
I still have the metallic sound issue, after did 3 steps you list in
#99. (No problem without pulseaudio.)
It must be that a certain detail has not been handled properly. Do you
know what it is?
I have to put this line in /etc/modprobe.d/alsa-base.conf, without it, the
sound card
@Mike,
For wifi issue, could you help to turn off the power save of wifi and check it
again.
#Setting->Power->Wifi(wifi can be turned off to save power)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@Mike,
I also tried chromium and the issue still can be triggered.
Would you please file a bug to chromium first !?
https://bugs.chromium.org/p/chromium/issues/list
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The -proposed kernel (4.4.0-191-generic) can fix this issue.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
** Changed in: hwe-next
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which
No, it's still too risky to enable this feature in oem-5.6.
Maybe we'll enable this on 5.10 kernel.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
** Changed in: linux-oem-5.6 (Ubuntu Focal)
Status: In Progress => Won't Fix
--
You received this bug notification
Not an issue here on my optimus laptop (slightly aged as latest laptop
is nvidia only
$ uname -a && xrandr --verbose |grep PRIME && sudo cat
/sys/module/nvidia_drm/parameters/modeset
Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-48-generic #52~18.04.1-Ubuntu SMP Thu Sep
10 12:50:22 UTC 2020 x86_64
Next one:
https://people.canonical.com/~alexhung/LP1896482/937d1d5d752513b8/
--
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/1896482
Title:
acpi event detection crashes
Status in linux
** Summary changed:
- Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide
band speech support.
+ Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide
band speech support (Bluetooth A2DP codecs ).
--
You received this bug notification because you
** Tags removed: need-duplicate-check
--
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/1896853
Title:
package linux-headers-5.4.0-48 5.4.0-48.52 failed to install/upgrade:
unable to
This change was made by a bot.
** 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/1896853
Title:
package
Public bug reported:
occurred while patching was taking place
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-headers-5.4.0-48 5.4.0-48.52
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture:
that one also seems to be good.
On Wed, 23 Sep 2020, Alex Hung wrote:
> Next one is @
> https://people.canonical.com/~alexhung/LP1896482/c271d18b523bb58e/
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1896482
>
>
Problem still exists with 450 drivers on Ubuntu 20.04.1.
Linux bdp 5.4.0-49-generic #53-Ubuntu SMP Fri Sep 18 09:54:57 UTC 2020 x86_64
x86_64 x86_64 GNU/Linux
TU117GLM [Quadro T1000 Mobile]
450.66-0ubuntu0.20.04.1
eDP-1-1 connected (normal left inverted right x axis y axis)
PRIME
** Also affects: nvidia-graphics-drivers-450 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1857271
Title:
Next one is @
https://people.canonical.com/~alexhung/LP1896482/c271d18b523bb58e/
--
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/1896482
Title:
acpi event detection crashes
Status in
Hello @shaynagar, thank you very much for reporting! We will look into
this asap.
More details: 4.4.0-190-generic is fine, 4.4.0-191-generic contains the
regression.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => High
** Description changed:
- This is a POTENTIAL REGRESSION.
+ [Impact]
- This issue occurs on one of the AWS instance "t2.medium"
+ The new
Thanks! I've submitted a version to intel-gfx mailing list as [RFC PATCH
1/1] Remove DPCD Aux Backlight Control PWM_PIN check after discussions
with Redhat's Lyude Paul.
https://lists.freedesktop.org/archives/intel-
gfx/2020-September/248938.html
--
You received this bug notification because
Hello, facing the same issue (obviously).
I appear to have the MSFT0001:00 04F3:3186, ordered in France, so this
model does not seems to be limited to china (R7000 variant).
Blacklisting done nothing. I have seen the chinese blog but I'm a little
lost with this, is it supposed to work with my
I am trying to follow the directions in the automated comment #68 -->
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875199/comments/68
however I am unsure of how to change the status of this issue to
properly confirm the fix. If anyone else could provide some additional
guidance (or
I can confirm that when using the updated 'proposed' kernel (version
5.4.0-49-generic) that audio output works properly on my Intel NUC8CCHK
test system.
Thank you to everyone that helped identify and fix this issue, your
efforts are much appreciated.
--
You received this bug notification
this one seems to be good
On Wed, 23 Sep 2020, Alex Hung wrote:
> @jcline-physics,
>
> Thanks for testing. The next is available @
> https://people.canonical.com/~alexhung/LP1896482/31be3e3551d09f20/
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => In Progress
>
> ** Changed in:
The problem persists on 5.4.0-48 sadly, I still need to select advanced in
grub, selecting 5.4.0-42 for the touchpad to work.
*➜ ~ xinput --list*
*5.4.0-42*
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag
** Description changed:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating
--- Comment From geral...@de.ibm.com 2020-09-23 15:37 EDT---
(In reply to comment #161)
> While working on this bug a patched kernel was created and made available
> here:
> https://people.canonical.com/~fheimes/lp1896726/
> But it's a patched groovy kernel only, since the commit/patch
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
What is the scope of the fix? I assume of course that it means the
touchpad is now usable, but does it also enable the option for turning
off "tap to click" in Ubuntu Settings? I ask because this option is not
available in the Windows 10 installation that was preinstalled on my
Thinkbook 15 IIL.
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either
@jcline-physics,
Thanks for testing. The next is available @
https://people.canonical.com/~alexhung/LP1896482/31be3e3551d09f20/
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Alex Hung (alexhung)
--
You
While working on this bug a patched kernel was created and made available here:
https://people.canonical.com/~fheimes/lp1896726/
But it's a patched groovy kernel only, since the commit/patch doesn't cleanly
apply to focal master-next:
git apply --stat
I also have Lenovo Legion 5 15ARH05H, 82B1000AUS and would like to help
out with adding support for this device. Any advice on how to get
started?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: snapd (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/1895144
Title:
ubuntu-server CET gap analysis
Status in golang-defaults
This might be a duplicate of bug 1875577
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1891867
Title:
zfs not correctly imported at boot
Status in zfs-linux package in Ubuntu:
Kernel 5.4.0-48 fixes the problem. The TouchPad is recognized correctly
and touch pad, buttons, and track point work. Thank you.
--
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/1895202
There was more discussion at https://github.com/snapcore/pc-
amd64-gadget/issues/48, but no I don't think this has changed, we still
have the serial tty in the kernel cmdline at the very least.
Last we talked about it in a meeting, Claudio measured that indeed the
UC20 kernel regressed as
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bcmwl (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1896348
Patches submitted to SRU:
https://lists.ubuntu.com/archives/kernel-team/2020-September/113701.html
https://lists.ubuntu.com/archives/kernel-team/2020-September/113702.html
https://lists.ubuntu.com/archives/kernel-team/2020-September/113703.html
--
You received this bug notification because you
Public bug reported:
please remove the build dependency on python3-venv. It's gone upstream.
** Affects: linux (Ubuntu)
Importance: High
Status: Confirmed
** Affects: linux-aws (Ubuntu)
Importance: High
Status: Confirmed
** Tags: rls-gg-incoming
** Also affects:
Thank you Kai-Heng Feng - you're awesome.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1853277
Title:
Lenovo ThinkBook 14-IML Touchpad not showing up in
I was on kernel version 5.4.0.47-generic and was using the rtl8822be
repo of mid-kid on github. I didn't even need to boot on windoes first
to get wifi working, it was all fine, however when I updated to
5.4.0.48-generic that one stopped working, therefore I tried installing
the kernel above
The kworker processes are generic in that they can do work for many kernel
parts,
so a particular kworker/number unfortunately doesn't help much to understand the
actual thing that the kworker was doing; we'll need the stack traces for that.
:)
Yes, if and once the issue starts happening again,
Hello, I have exactly the same issue as the creator of this bug. I have
a Lenovo Legion 5 15ARH05H, model number 82B1000AUS
(https://psref.lenovo.com/Detail/Legion/Lenovo_Legion_5_15ARH05H?M=82B1000AUS),
and my touchpad is listed as MSFT0001:00 04F3:3186, not 04F3:3140.
How can I help add support
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either
** Description changed:
AWS RDMA/efa driver: add support for new AWS EFA '0xefa1' devices.
[Impact]
The following 4 mainline commits are required to support the new device
features and ID:
d4f9cb5c5b22 RDMA/efa: Add EFA 0xefa1 PCI ID
a5d87b698547 RDMA/efa: User/kernel
The same day after I have reported this problem, kworker stopped consuming CPU.
I am pretty sure it was kworker/5 a problem.
Now I have executed "top" command, typed L and search string kworker and
all of the kworker processes are 0 CPU consumption (see attachment).
I think this problem
Public bug reported:
AWS RDMA/efa driver: add support for new AWS EFA '0xefa1' devices.
[Impact]
The following 4 mainline commits are required to support the new device
features and ID:
d4f9cb5c5b22 RDMA/efa: Add EFA 0xefa1 PCI ID
a5d87b698547 RDMA/efa: User/kernel compatibility handshake
** Description changed:
+ SRU Justification:
+ ==
+
+ [Impact]
+
+ * With focal (and even eoan) it is no longer possible to run the
+ updateconfigs Debian build rule (needed in case of kernel option
+ updates) on all supported arhitectures.
+
+ * Changes upstream led to the
Public bug reported:
Microsoft would like to request a change to the time keeping method in
the Azure images.
We would like to request that an Azure image uses the Azure host for
time sync by default. This will require the use of the Chrony package.
The Chrony package would need to be
okay, so that kernel has the problem again.
On Wed, 23 Sep 2020, Alex Hung wrote:
> Thanks mfo for helping out how to disable secure boot and install kernel
>
> I uploaded a test kernel @
> https://people.canonical.com/~alexhung/LP1896482/0a8c35897f60b202/
>
> There are 17 patches so it
ok, that's not such a big problem. I'll keep all the versions' deb
packages in separate directories so I can easily switch back to one of
them if needed.
On Wed, 23 Sep 2020, Mauricio Faria de Oliveira wrote:
> Hi Jim,
>
> You can install on top of the previous ones without removing them
This bug was fixed in the package linux - 5.8.0-19.20
---
linux (5.8.0-19.20) groovy; urgency=medium
* groovy/linux: 5.8.0-19.20 -proposed tracker (LP: #1895120)
* Please switch default, hwe, oem kernel flavours governor to
CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y , such that
This bug was fixed in the package linux - 5.8.0-19.20
---
linux (5.8.0-19.20) groovy; urgency=medium
* groovy/linux: 5.8.0-19.20 -proposed tracker (LP: #1895120)
* Please switch default, hwe, oem kernel flavours governor to
CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y , such that
This bug was fixed in the package linux - 5.8.0-19.20
---
linux (5.8.0-19.20) groovy; urgency=medium
* groovy/linux: 5.8.0-19.20 -proposed tracker (LP: #1895120)
* Please switch default, hwe, oem kernel flavours governor to
CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y , such that
This bug was fixed in the package linux - 5.8.0-19.20
---
linux (5.8.0-19.20) groovy; urgency=medium
* groovy/linux: 5.8.0-19.20 -proposed tracker (LP: #1895120)
* Please switch default, hwe, oem kernel flavours governor to
CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y , such that
This bug was fixed in the package linux - 5.8.0-19.20
---
linux (5.8.0-19.20) groovy; urgency=medium
* groovy/linux: 5.8.0-19.20 -proposed tracker (LP: #1895120)
* Please switch default, hwe, oem kernel flavours governor to
CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y , such that
This bug was fixed in the package linux - 5.8.0-19.20
---
linux (5.8.0-19.20) groovy; urgency=medium
* groovy/linux: 5.8.0-19.20 -proposed tracker (LP: #1895120)
* Please switch default, hwe, oem kernel flavours governor to
CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y , such that
This bug was fixed in the package linux - 5.8.0-19.20
---
linux (5.8.0-19.20) groovy; urgency=medium
* groovy/linux: 5.8.0-19.20 -proposed tracker (LP: #1895120)
* Please switch default, hwe, oem kernel flavours governor to
CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y , such that
This bug was fixed in the package linux - 5.8.0-19.20
---
linux (5.8.0-19.20) groovy; urgency=medium
* groovy/linux: 5.8.0-19.20 -proposed tracker (LP: #1895120)
* Please switch default, hwe, oem kernel flavours governor to
CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y , such that
** Also affects: linux (Ubuntu Groovy)
Importance: Undecided
Status: Triaged
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Groovy)
Status: Triaged => Fix Committed
** Changed in: linux (Ubuntu Focal)
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
--
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/1896216
Title:
[Ubuntu 20.10] zPCI DMA tables and bitmap leak on
@Markus - did the patch
5d6059f8ec cpu_map: Distinguish Cascadelake-Server from Skylake-Server
really work for you without the changes to support stepping applies?
Or does your own build have much more applied to make it work?
--
You received this bug notification because you are a member of
I agree Markus.
Not only does the Focal qemu miss the related changes, I also dived deeper
through the "what exactly happened" to be sure.
The added patches I picked make it more obvious (test breaks) that we would
need cpu model "stepping" ranges to work. This would add the need for much more
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1896760
and then change the status of the bug to 'Confirmed'.
If, due to the
Hi Jim,
You can install on top of the previous ones without removing them first.
The versioning of the test packages used the same 5.4.0-47 number,
so unfortunately they will keep overwriting themselves (including
the original/non-test 5.4.0-47 kernel.)
I'd think this is why you only see two
Ugh. It turns out an antenna lead had come unhooked. With that remedied,
things look much better now.
Sorry for the noise.
--
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/1896303
Title:
Thanks Andrea for looking into this.
Added a cloud-init task for tracking.
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: cloud-init (Ubuntu)
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in:
4.15 doesn't contain 1901b91f9982 ("IB/core: Fix potential NULL pointer
dereference in pkey cache") and thus doesn't need the fix.
5.4 and 5.8 require the fix because they contain 1901b91f9982 and the
fix will only be included in 5.9.
** Also affects: linux-azure (Ubuntu Focal)
Importance:
Hi, if I install this on top of the previous one using dpkg -i * will that
be sufficient? Or do I have to remove the previous packages first?
It seems like my grub configuration is somehow set to keeping only two
kernels in the boot list. It would be nice if it would keep them all so I
don't
Public bug reported:
[Impact]
Running the current armhf raspi kernel on Pi 3 and 2 results in wasting
~70MB of memory because of LPAE, HIGHMEM and VMSPLIT_3G. That's a
significant waste of memory particularly on a Pi 3A+ which only has
512MB to begin with. Additionally, with HIGHMEM enabled, CMA
Public bug reported:
Mellanox has made a patch to fix DPDK failure in Azure with ConnextX3
pro:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
next.git/commit/drivers/infiniband/hw/mlx4?h=next-20200908=ec78b3bd66bc9a015505df0ef0eb153d9e64b03b
Older kernels don't need this patch. It
--- Comment From hegdevas...@in.ibm.com 2020-09-23 07:45 EDT---
(In reply to comment #6)
> built and tested kernel versions available on:
> https://people.canonical.com/~patriciasd/kernel-lp1893897/
Looks good.
Thanks!
-Vasant
--
You received this bug notification because you are a
@Koba,
You're right, it doesn't happen on Firefox. This only happen on Chrome.
But its a bit weird since it does not happen on fedora.
I connected with 5g, but happen with 2.4g too. Would you like some logs?
--
You received this bug notification because you are a member of Kernel
Packages,
** Description changed:
This is a POTENTIAL REGRESSION.
-
- This issue only occurs on one of the AWS instance "t2.medium"
+ This issue occurs on one of the AWS instance "t2.medium"
Steps:
- 1. Deploy this instance with AWS kernel (4.4.0-1115)
-
+ 1. Deploy this instance with AWS
** Also affects: linux (Ubuntu Groovy)
Importance: Undecided
Assignee: Frank Heimes (fheimes)
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Frank Heimes (fheimes)
--
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
Hmm, I spoke too soon ... :-/
Some of the self tests failed due to the changes - I'll fix them up and ping
again once the builds complete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
--- Comment From heinz-werner_se...@de.ibm.com 2020-09-23 05:27 EDT---
Severity adapted to critical. Please be aware of that. Many thx
** Tags removed: severity-medium
** Tags added: severity-critical
--
You received this bug notification because you are a member of Kernel
Packages,
yes i did reboot i tried installing linux-
image-5.9.0-rc4+_5.9.0-rc4+-4_amd64.deb and now it is working like charm
i wanted to know if there will be any update in kernal then what patch
or how should i do that ??
BTW thanks to all u guys thankyou very very much
--
You received this bug
Daniel, I have only faced that bug once, so far it hasn't happened
again, so I have no idea how to reproduce it. Should I open a new bug
anyway? Under mutter and the NVIDIA drivers?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Gaurav, did you reboot into the patched kernel?
And what is the output of "uname -r" in a terminal (after rebooting),
does that show that you are running the patched kernel now?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
--- Comment From heinz-werner_se...@de.ibm.com 2020-09-23 04:54 EDT---
This problem exist also with the current 5.4.0.48 kernel!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** 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/1896725
Title:
Kernel panic with AWS 4.4.0-1115-aws
Status in linux
The patch/commit mentioned landed in linux-next (just tagged with
next-20200921).
** Changed in: ubuntu-z-systems
Importance: Undecided => Medium
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Changed in: linux (Ubuntu)
@Dmitry i installed the kernel but nothing changed here.
what should i try now?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1853277
Title:
Lenovo ThinkBook 14-IML Touchpad
Thanks for the test of the new kernel Markus!
I have respun the qemu build (the old one was outdated by a massive stable
update - too bad this wasn't part of 4.2.1 already) with the patches we had
before applied on top.
Further I have reviewed the suggested libvirt changes and added a build
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1896726
Title:
[UBUNTU 20.04.1]Secure guest (qemu) crash
Gaurav, for starters install the Kai's patched kernel from here:
https://people.canonical.com/~khfeng/lp1853277-final/
...and report if your touchpad works with it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
** Summary changed:
- Secure guest (qemu) crash during boot (mostly) but also while running
workload (rare) (secure execution)
+ [UBUNTU 20.04.1]Secure guest (qemu) crash during boot (mostly) but also while
running workload (rare) (secure execution)
--
You received this bug notification
1 - 100 of 110 matches
Mail list logo
