** Also affects: initramfs-tools
Importance: Undecided
Status: New
** No longer affects: initramfs-tools
** Also affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
I still haven't been able to reproduce this. If you can reproduce this
easily, maybe I can provide some kernels to be tested?
I'll keep trying to reproduce here. I compared my VM settings to why is
in the bug description, and I have the same config, except the region.
I wouldn't think that
I modified your script to perform 5000 reboots. I'm up to 3508 reboots
now without hitting the bug. I'll let it run for a while longer. I'll
also compare our environments to see if there is a difference.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Confirmed
** Changed in: linux (Ubuntu)
Status: In Progress => Confirmed
** Changed in: linux (Ubuntu)
Assignee: Joseph Salisbury (jsalisbury) => (unassigned)
** Changed in: linux (Ubuntu Bionic)
** Package changed: linux (Ubuntu) => apport (Ubuntu)
** Changed in: apport (Ubuntu)
Status: Confirmed => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1799118
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19
I started a kernel bisect between v4.14 final and v4.15-rc1. The kernel
bisect will require testing of about 7-10 test kernels.
I built the first test kernel, up to the following commit:
1be2172e96e33bfa22a5c7a651f768ef30ce3984
The test kernel can be downloaded from:
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Bionic)
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1701297
Title:
NTP reload failure (unable to
** Tags added: kernel-key
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/796588
Title:
Fine-grained network mediation
Status in AppArmor:
In Progress
Status in
** Changed in: iproute2 (Ubuntu)
Status: Expired => Triaged
** Changed in: iproute2 (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
** Package changed: linux (Ubuntu) => apport (Ubuntu)
** Changed in: apport (Ubuntu)
Status: Confirmed => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1790253
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1788321
Title:
swapon failed: invalid argument
** Tags added: kernel-key
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided => Critical
** Changed in: linux (Ubuntu)
Assignee: (unassigned) =>
** Changed in: intel
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1591833
Title:
[Featue] Upgrade Openssl for Intel QAT
Thanks for filing this bug. This project is being shut down as it’s not
actively monitored by any team or individual. This bug will not be
deleted but will be closed as <>. If this bug is something
that is still affecting a product in Ubuntu, you can take one of the
following steps to report
Do you have a way to reproduce this issue, or was it a one time event?
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1782893
Title:
Bluetooth not
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
** Also affects: linux (Ubuntu Cosmic)
Importance: High
Status: Triaged
** Tags added: kernel-da-key
** Also affects: lxc (Ubuntu)
Importance: Undecided
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Also affects: klibc (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Medium
Status: Confirmed
** Also affects: systemd (Ubuntu Bionic)
Importance:
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-March/090976.html
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tar in Ubuntu.
https://bugs.launchpad.net/bugs/1757565
Title:
btrfs and tar sparse
** Description changed:
+
+ == SRU Justification ==
+ This bug causes btrfs and tar sparse to truncate archives. This bug has been
+ fixed in v4.15-rc3 by commit e3b8a4858566, which has a prereq commit of
f48bf66b662e.
+
+ These commits were cc'd to upstream stable and are already in Bionic.
That's great news. I'll SRU those two commits to the Artful kernel.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tar in Ubuntu.
https://bugs.launchpad.net/bugs/1757565
Title:
btrfs and tar sparse truncate archives
I built an Artful test kernel with commit e3b8a48. It also needed
commit f48bf66b6 as a prereq.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1757565
Can you test this kernel and see if it resolves this bug?
Note, to test this kernel, you need to install both
It looks like that commit landed in -rc3:
git describe --contains e3b8a48
v4.15-rc3~3^2~11
However, -rc2 is good, correct? I'll have a look at the other btrfs
commits in -rc2 and see if any stick out.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Hmm, even though git describe returns that tag, it seem s-rc2 has that
commit.
I'll still build an Artful test kernel with that commit to see if it
fixes the bug and figure out the tagging in the background.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Thanks for doing all the leg work. I'll build a test kernel with that
commit and post it shortly.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tar in Ubuntu.
https://bugs.launchpad.net/bugs/1757565
Title:
btrfs and tar
That would indicate the fix is in from v4.15-rc2 -> 4.15 Final. I'll
review the commits in that range, but there are probably thousands of
them. It will help to narrow it down further. Could you test the 4.15
release candidates on the following page to find the last good kernel
and first bad
@Scott, will that upstream commit make it so the kernel fix we are
looking for is not required?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tar in Ubuntu.
https://bugs.launchpad.net/bugs/1757565
Title:
btrfs and tar
Thanks for the info, Ryan.
We know that 4.15-rc1 is BAD and 4.15.7 is GOOD, so the fix came in some
where in between.
Can you next test v4.15 Final:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
The Bionic 4.15.0-12 kernel is based off of upstream 4.15.7. Can you
test that kernel as well? That will tell us if the fix in Bionic is an
Ubuntu SAUCE patch or a 4.15 stable update.
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15.7/
--
You received this bug notification because you are
Status: New
** Changed in: linux (Ubuntu Artful)
Status: New => Triaged
** Changed in: linux (Ubuntu Artful)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Artful)
** Package changed: linux (Ubuntu) => apparmor (Ubuntu)
** Changed in: apparmor (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
Commit 2a8a98673c13 has been in Xenial and Artful for some time now.
Can you confirm this bug is now resolved with the latest updates.
** Changed in: linux (Ubuntu Artful)
Status: In Progress => Fix Released
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Released
** No longer affects: linux (Ubuntu Zesty)
** No longer affects: procps (Ubuntu Zesty)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1717224
Title:
virsh start of
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.15 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.15 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.15 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
Commit 2a8a98673c13 has been in Xenial since Ubuntu-4.4.0-98.121. If
you can confirm the bug is now fixed since this kernel version, I'll
mark the bug as Fix Released.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps
** Tags removed: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1739672
Title:
Regression in getaddrinfo(): calls block for much longer on Bionic
One way to tell if this bug is due to the kernel, is to boot with some
prior kernel versions and see if the bug goes away.
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Touch
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Incomplete
** Changed in: linux (Ubuntu Zesty)
Status: In Progress => Incomplete
** Changed in: linux (Ubuntu Artful)
Status: In Progress => Incomplete
** Changed in: linux (Ubuntu)
Status: In Progress =>
** Changed in: linux (Ubuntu Xenial)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Zesty)
Status: Triaged => In Progress
** Changed in: linux (Ubu
Submitted SRU requests:
https://lists.ubuntu.com/archives/kernel-team/2017-December/088680.html
https://lists.ubuntu.com/archives/kernel-team/2017-December/088682.html
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd
Thanks for testing and the patch, Ryan. I can submit and SRU request.
We should also send this upstream for inclusion in the mainline kernel.
Is that something you think you can do? If not, I can do it for you.
--
You received this bug notification because you are a member of Ubuntu
Touch
I built Xenial, Zesty and Bionic test kernels with your patch. They can
also be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1729145/
Can those that can reproduce this bug give this test kernel a try?
Zesty required upstream commit 4b758df21 as a prereq. Zesty never got it,
since
I attached an update to your patch, Ryan.
I added a subject, commit log and couple of missing semi colons /
parenthesis.
Can you look it over and see if you approve of the log and subject?
I'll see if it applies to the other Ubuntu releases and builds on them
as well.
** Patch added:
In the final patch we submit for SRU, it will also include your Signed-
off-by, I just forgot to add it in the attached one.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
I built an Artful test kernel with the path provided by Ryan. The test
kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1729145/
Can those that can reproduce this bug give this test kernel a try?
--
You received this bug notification because you are a member of Ubuntu
It looks like env[] was declared in bch_cached_dev_emit_change(), but
not in bch_cached_dev_run().
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1729145
Title:
@Ryan
I tried to build an Artful test kernel with your patch. However, there
were compilation errors:
ubuntu-artful/drivers/md/bcache/super.c:868:9: error: 'env' undeclared (first
use in this function); did you mean '_end'?
kfree(env[1]);
^~~
_end
Did you have any issues
** Tags removed: kernel-key
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1733321
Title:
network-manager ADT tests fail with on ppc64el with artful/linux
** Tags removed: kernel-da-key
** Tags added: kernel-key
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1729145
Title:
/dev/bcache/by-uuid links not created after reboot
** Package changed: linux (Ubuntu) => apparmor (Ubuntu)
** Changed in: apparmor (Ubuntu)
Status: Confirmed => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
** Package changed: linux (Ubuntu) => apparmor (Ubuntu)
** Changed in: apparmor (Ubuntu)
Status: Confirmed => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
** Package changed: linux (Ubuntu) => pulseaudio (Ubuntu)
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1728573
Title:
request to pull in an upstream bug fix for
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.14
Commit 2a8a98673c13 is in Xenial -proposed, kernel version:
Ubuntu-4.4.0-98.121. It looks like you tested with version
4.4.0-62-generic. Can you try testing with the -proposed Xenial kernel:
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed.
ogress
** Changed in: linux (Ubuntu Zesty)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Assign
I'll build an Artful test kernel with commit 2a8a98673c13 and post it
shortly.
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph
@Dimitri, yes I'll submit an SRU request.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/696435
Title:
wait-for-root fails to detect nbd root
Status in linux package in
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1722897
Title:
Unexpected behavior with Wayland desktop
Status in xorg package in Ubuntu:
New
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/696435
Title:
wait-for-root fails to detect nbd root
Status in linux package in Ubuntu:
Fix
I built a Xenial test kernel with a pick of commit 37091fd. The test
kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp696435/
To test the kernel, be sure to install both the linux-image and linux-
image-extra .deb packages.
--
You received this bug notification because
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Xenial)
Assignee: Canonical Kernel (canonical-kernel) => Joseph Salisbury
(jsalisbury)
--
You received
** Changed in: linux (Ubuntu)
Status: Triaged => Incomplete
** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1379536
Title:
It is possible. I've added a systemd bug task.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
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 Ubuntu
Touch seeded packages, which is subscribed to debconf in Ubuntu.
https://bugs.launchpad.net/bugs/1701770
Title:
package
*** This bug is a duplicate of bug 1699108 ***
https://bugs.launchpad.net/bugs/1699108
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 Ubuntu
Touch seeded packages, which is
Thanks for the update, Mark. Would you say this bug is resolved?
** Changed in: xorg (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
@Mark Harris, it's been a while since the last comment. Does this bug
still exist with the lastest updates?
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
** Package changed: linux (Ubuntu) => busybox (Ubuntu)
** Changed in: busybox (Ubuntu)
Status: Confirmed => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to busybox in Ubuntu.
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Package changed: linux (Ubuntu) => click-apparmor (Ubuntu)
** Changed in: click-apparmor (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.11
** Tags added: kernel-da-key
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1684481
Title:
KVM guest
** Tags removed: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1408106
Title:
attach_disconnected not sufficient for overlayfs
Status in AppArmor:
In
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.11 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.11 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
** Tags removed: kernel-key
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1655735
Title:
Incompatible libdevmapper 1.02.136 (2016-11-05) and
Does the error go away if you boot a Xenial test kernel on this machine
and re-run the test? That will tell us if it is a kernel regression.
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Tags added: kernel-key
--
You received this bug notification because you are a member
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.10 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
Did this issue start happening after an update/upgrade? Was there a
kernel version where you were not having this particular problem? This
will help determine if the problem you are seeing is the result of a
regression, and when this regression was introduced. If this is a
regression, we can
Vivid)
** No longer affects: e2fsprogs (Ubuntu Xenial)
** No longer affects: e2fsprogs (Ubuntu Yakkety)
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigne
in: linux (Ubuntu Trusty)
Importance: Undecided => High
** Changed in: linux (Ubuntu Trusty)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Trusty)
Assignee: Tim Gardner (timg-tpi) => Joseph Salisbury (jsalisbury)
--
You received this bug notification be
** Changed in: linux (Ubuntu Xenial)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Xenial)
Assignee: Tim Gardner (timg-tpi) => Joseph Salisbury (jsalisbury)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/1619918
Title:
lsattr 32bit does not work on 64bit
We started a Reverse bisect in comment #17. However, it appears the
hardware is no longer avaiable.
As mentioned in comment #22, this is fixed in Yakkety. You could use
that kernel, but if you can reproduce the bug, we can continue the
reverse bisect? That would allow us to identify the commit
** Changed in: initramfs-tools (Ubuntu Vivid)
Status: In Progress => Fix Released
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
** Tags removed: verification-needed-vivid
** Tags added: verification-done-vivid
--
You received this bug notification because you
I started a Reverse kernel bisect between v4.4 final and v4.5-rc1. The
kernel bisect will require testing of about 7-10 test kernels.
I built the first test kernel, up to the following commit:
1289ace5b4f70f1e68ce785735b82c7e483de863
The test kernel can be downloaded from:
** Also affects: bridge-utils (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Yakkety)
Importance: High
Status: Confirmed
** Also affects: bridge-utils (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux
It looks like we can perform a reverse bisect between 4.4 final and
4.5-rc1. Can you give 4.4 final a test, just to confirm it exhibits the
bug and it wasn't introduced in on of the stable updates in 4.4? 4.4
final can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-wily/
Per comment #10, the bug was fixed somewhere between upstream 4.4 and
4.6. To narrow it down further, so we can perform a reverse bisect can
you test the 4.5 final kernel:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-wily/
If 4.5 is good, maybe test 4.5-rc1:
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.8
Can you also see if this bug happens with the latest upstream stable 4.4
kernel? It can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.19/
If it does still happen with 4.4.19, we can perform a reverse bisect to
find the fix that is in 4.8-rc3.
--
You received this bug
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.8 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.8
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.7
1 - 100 of 175 matches
Mail list logo
