** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Committed
**
Public bug reported:
Description:Ubuntu 16.04.6 LTS
Release:16.04
Package version: 7.7+13ubuntu3.1
Fresh system install with Ubuntu 16.04 crashes the system after some
time. We are running high CPU intensive jobs, but CPU usage never
crosses 80%.
ProblemType: Bug
DistroRelease:
** Description changed:
This bug report is a Feature Freeze Exception request on behalf of the
Kubuntu team for KDE Frameworks 5.62.0 (updated from 5.61.0).
https://www.kde.org/announcements/kde-frameworks-5.62.0.php
As is usual with a KDE Frameworks release, this is a mixture of
** Changed in: kernel-sru-workflow/prepare-package
Assignee: (unassigned) => Paolo Pisati (p-pisati)
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: (unassigned) => Paolo Pisati (p-pisati)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
This bug report is a Feature Freeze Exception request on behalf of the
Kubuntu team for KDE Frameworks 5.62.0 (updated from 5.61.0).
https://www.kde.org/announcements/kde-frameworks-5.62.0.php
As is usual with a KDE Frameworks release, this is a mixture of new some
new
Launchpad has imported 7 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=1411398.
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
(In reply to Mikhail Novosyolov from comment #54)
>
> So, something was fixed in upstream, backported to LTS kernel 4.19 and to
> Ubuntu kernel. I don't know what. And that issue is 100% not in BTRFS but is
> another problem or another aspect of the problem.
>
I can suspect commit
(In reply to howaboutsynergy from comment #55)
> On an unrelated note(but since btrfs was thought to be a problem at some
> point), I've discovered that btrfs with zstd:5 (or worse zstd:15) can cause
> (at least) mouse cursor stuttering(like it was skipping frames), while
> zstd:1 doesn't(likely
On an unrelated note(but since btrfs was thought to be a problem at some
point), I've discovered that btrfs with zstd:5 (or worse zstd:15) can
cause (at least) mouse cursor stuttering(like it was skipping frames),
while zstd:1 doesn't(likely because of the low CPU usage during
compression),
** Summary changed:
- bionic/linux-gcp: -proposed tracker
+ bionic/linux-gcp: 5.0.0-1016.16~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Recently, about since kernel 5.2.7, the issue is either gone or present to much
less extent.
Right now I'm running kernel 5.2.11 and finally I can keel Firefox and
VirtualBox running at the same time, with 3G+ in swap, and the system does not
freeze.
Could anyone affected by this issue try
(In reply to ValdikSS from comment #53)
> Recently, about since kernel 5.2.7, the issue is either gone or present to
> much less extent.
> Right now I'm running kernel 5.2.11 and finally I can keel Firefox and
> VirtualBox running at the same time, with 3G+ in swap, and the system does
> not
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-xenial
** Tags added: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
On 12/09/2019 17:38, Ubuntu SRU Bot wrote:
> All autopkgtests for the newly accepted kwin (4:5.12.9.1-0ubuntu0.1) for
> bionic have finished running.
> The following regressions have been reported in tests triggered by the
> package:
>
> ubiquity/unknown (armhf)
This was just an armhf test
Thanks for reporting this issue - this sounds like it might be suitable
as a StableReleaseUpdate - in particular the Regressions section
https://wiki.ubuntu.com/StableReleaseUpdates#Regressions sounds relevant
in this case. Could you please adapt this bug report following the
template in
** Also affects: ldm-ubuntu-themes (Ubuntu)
Importance: Undecided
Status: New
** Also affects: lubuntu-default-settings (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: kubuntu-settings (Ubuntu)
Status: New => Confirmed
** Changed in: kubuntu-settings (Ubuntu)
Importance: Undecided => Medium
** Changed in: kubuntu-settings (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
*** This bug is a duplicate of bug 1611737 ***
https://bugs.launchpad.net/bugs/1611737
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Ubuntu 16.04 LTS upgrade path is to 16.10 OR the next LTS, ie. 18.04
LTS. To jump to the development release, you should
Summary D vs E:
- no suffix
=> works equally in both releases
=> same opcodes in all .code segments
- suffix "w"
=> works equally in both releases
=> opcodes in .code32/.code64 differ from .code16 (660f..)
=> .code16 matches the non-suffix opcodes (0f..)
- suffix "l"
=> failures in
*** This bug is a duplicate of bug 1611737 ***
https://bugs.launchpad.net/bugs/1611737
Public bug reported:
Calculating the changes
Could not calculate the upgrade
An unresolvable problem occurred while calculating the upgrade.
If none of this applies, then please report this bug using
Result Eoan:
### Testing suffix '' ###
.code16
push %gs
push %fs
pop %gs
pop %fs
.code32
push %gs
push %fs
pop %gs
pop %fs
.code64
push %gs
push %fs
pop %gs
pop %fs
push.out: file format elf64-x86-64
Disassembly of section .text:
<.text>:
0: 0f a8
Slightly extending on that test by Valentine I really think this is a change in
binutils behavior.
Attaching a script to test which I then will add logs from Disco (older 2.32)
and Eoan (2.32.51).
The script does:
- test pop/push with suffixes "" w l q
- test this in code 16/32/64 blocks
**
Result Disco:
### Testing suffix '' ###
.code16
push %gs
push %fs
pop %gs
pop %fs
.code32
push %gs
push %fs
pop %gs
pop %fs
.code64
push %gs
push %fs
pop %gs
pop %fs
push.out: file format elf64-x86-64
Disassembly of section .text:
<.text>:
0: 0f a8
Fix proposed to branch: stable/queens
Review: https://review.opendev.org/681965
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728527
Title:
hostmonitor can not monitor pacemaker_remote node via
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
301 - 327 of 327 matches
Mail list logo
