Upstream fix 40249c6962075c040fd071339acae524f18bfac9, this has already
been picked up by Sash Levin for 5.8, 5.4, 4.19, 4.14, 4.9 and 4.8 on
backport stable AUTOSEL. Lets wait for that fix to trickle into the SRU
process.
** Changed in: linux (Ubuntu)
Status: Won't Fix => In Progress
--
** Bug watch added: Linux Kernel Bug Tracker #208885
https://bugzilla.kernel.org/show_bug.cgi?id=208885
** Also affects: linux via
https://bugzilla.kernel.org/show_bug.cgi?id=208885
Importance: Unknown
Status: Unknown
** Description changed:
+ Running:
+
+ sudo lcov --zerocounte
Ah, earlier on boot I'm seeing:
[8.808508] virtio_blk virtio3: [vda] 209715200 512-byte logical blocks (107
GB/100 GiB)
[8.808649] [ cut here ]
[8.815777] vda: detected capacity change from 0 to 107374182400
[8.816623] WARNING: CPU: 3 PID: 212 at mm/page_all
Launchpad has imported 3 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=208885.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help
Fix applied in risc-v groovy with commit
4fc484ffd959e0d897d073296cfcfafdf473e407
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launc
This is due to using gcc-10.2. Building with gcc-9 is fine. This
compiler support for GCOV will be disabled, see
https://lkml.org/lkml/2020/9/2/934
So, marking this as Won't Fix because there is a workaround and 10.2 is
not looking favourably for GCOV support at the moment.
** Changed in: linux (
6 matches
Mail list logo
