I will try to see what I can do. Leaving town tomorrow for a long
weekend. If not, I can work on it Sunday when I get back.
--
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/1682184
Title:
Public bug reported:
At boot I consistently get the error message:
"INFO: task systemd-udevd:179 blocked for more than 120 seconds."
This is under 16.04 on a Dell Optiplex 9020. See the attached image for
a full call trace when booting in Recovery Mode.
I want the system to boot to the GUI,
Good news:
For the people that are not able to compile a custom kernel, I provide
the download links of the binarys for you:
- Linux 4.10.3 AMD64 with Ubuntu patches
- Compiled from official ubuntu "linux-source-4.10.0" package
- AMD GPIO PIN Control removed
- No other changes from default
Ups I posted the wrong URL to my custom kernel:
http://www.nextized.net/repo/linux/ubuntu-
linux-4.10.3_ryzen01_amd64_generic.tar.gz
- Linux 4.10.3 AMD64 with Ubuntu patches
- Compiled from official ubuntu "linux-source-4.10.0" package
- AMD GPIO PIN Control removed
- No other changes from
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1682331
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a
I'd like to perform a bisect to figure out what commit caused this regression.
We need to identify the earliest kernel where the issue started happening as
well as the latest kernel that did not have this issue.
Can you test the following kernels and report back? We are looking for
the first
And in some cases squashfuse may not have the proper dep of fuse. And
you may need to manually:
apt install fuse # in addition to squashfuse
looks like squashfuse is missing a dependency on "fuse"
which is part of the official Ubuntu images but not in the community
images
so if you use "lxc
If it doesn't exist in 4.10 then it's either one of our "sauce" patches
or one of the 4.10 stable updates. We should be able to run a bisect to
find out what broke it though, which for you will basically mean testing
a series of kernels to help us zero in on the change which causes this
issue.
--
tests ran: 2, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-48.51-generic/rumford__4.8.0-48.51__2017-04-13_20-00-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Package changed: ubuntu => linux (Ubuntu)
--
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/1682331
Title:
Cannot get lowest brightness with kernel 4.4.0-53-generic
Status in Linux
tests ran: 64, failed: 2;
http://kernel.ubuntu.com/testing/4.8.0-48.51-generic/ms10-34-mcdivittB0-kernel__4.8.0-48.51__2017-04-13_19-23-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 64, failed: 2;
http://kernel.ubuntu.com/testing/4.8.0-48.51-generic/ms10-35-mcdivittB0-kernel__4.8.0-48.51__2017-04-13_19-23-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
You have been subscribed to a public bug:
I have been using kernel 3.16/3.19 in my Dell Laptop for a long time
with Linux Mint 17 and previous versions and the problem here had never
happened until LM18.
Very often I set the lowest possible brightness, for example at night,
or while I am flying
I built a test kernel with a pick of commit e9c18ae6eb2b. It can be downloaded
from:
http://kernel.ubuntu.com/~jsalisbury/lp1682561/
I'll submit an SRU request as soon as it's confirmed a fix for the bug.
--
You received this bug notification because you are a member of Kernel
Packages, which
Hitting this with zesty
Linux doe 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 2017 x86_64
x86_64 x86_64 GNU/Linux
--
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/1521173
tests ran: 64, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-48.51-generic/archytas__4.8.0-48.51__2017-04-13_19-15-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 141, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-48.51-generic/rumford__4.8.0-48.51__2017-04-13_18-46-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 64, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-48.51-generic/hainzel__4.8.0-48.51__2017-04-13_19-03-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 64, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-48.51-generic/gonzo__4.8.0-48.51__2017-04-13_18-51-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Also affects: linux (Ubuntu Zesty)
Importance: Undecided
Status: Confirmed
** Also affects: linux (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Repeatable in 4.11-rc6, and I'm yet to receive guidance to the tracing
problem discussed above. Have also asked for support in different forums
with no results.
** Tags removed: kernel-bug-exists-upstream-4.10-rc5
** Tags added: kernel-bug-exists-upstream-4.11-rc6
--
You received this bug
** Tags removed: verification-needed-xenial verification-needed-yakkety
** Tags added: verification-done-xenial verification-done-yakkety
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 2, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-48.51-generic/ms10-35-mcdivittB0-kernel__4.8.0-48.51__2017-04-13_18-54-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 2, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-48.51-generic/ms10-34-mcdivittB0-kernel__4.8.0-48.51__2017-04-13_18-55-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Mainline v4.10 seems to have fixed the issue.
However, now I am getting a Bluetooth error on startup. This does not
seem to impact actual use though as I can still do an audio sync and
stream to my main receiver.
Up and running for over an hour with VirtualBox, MySQL, Eclipse,
Thunderbird and
tests ran: 2, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-48.51-generic/archytas__4.8.0-48.51__2017-04-13_18-47-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 2, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-48.51-generic/hainzel__4.8.0-48.51__2017-04-13_18-37-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Unfortunately this is another critical issue.
--
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/1682561
Title:
[Hyper-V] hv: util: move waiting for release to hv_utils_transport
itself
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
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/1672550
Title:
i40e Intel X710 error during device
Public bug reported:
We are observing call traces with the -73 and -74 proposed kernels that
look like this:
[ 240.408061] INFO: task kworker/14:1:179 blocked for more than 120 seconds.
[ 240.412299] Not tainted 4.4.0-73-generic #94-Ubuntu
[ 240.415546] "echo 0 >
tests ran: 141, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-48.51-generic/ms10-34-mcdivittB0-kernel__4.8.0-48.51__2017-04-13_17-40-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This appears to affect 4.4, 4.8, and 4.10
--
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/1682561
Title:
[Hyper-V] hv: util: move waiting for release to hv_utils_transport
itself
tests ran: 141, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-48.51-generic/ms10-35-mcdivittB0-kernel__4.8.0-48.51__2017-04-13_17-39-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 141, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-48.51-generic/archytas__4.8.0-48.51__2017-04-13_17-48-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 19, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-48.51-generic/rumford__4.8.0-48.51__2017-04-13_17-27-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 141, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-48.51-generic/hainzel__4.8.0-48.51__2017-04-13_17-36-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tested on Trusty with the -proposed 3.13.0-117-generic and
4.4.0-74-generic #95~14.04.1 HWE kernel, ran 16 xattr stressors for 5
minutes, no failure, passed.
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are
tests ran: 141, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-48.51-generic/gonzo__4.8.0-48.51__2017-04-13_16-50-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I've installed the v4.10 mainline.
painter@merlin:~$ uname -a
Linux merlin 4.10.0-041000-generic #201702191831 SMP Sun Feb 19 23:33:19 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
Will monitor and see if there are any more system crashes. I will update
in a few hours.
Thanks!
--
You received this
tests ran: 19, failed: 1;
http://kernel.ubuntu.com/testing/4.8.0-48.51-generic/archytas__4.8.0-48.51__2017-04-13_16-38-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 14, failed: 1;
http://kernel.ubuntu.com/testing/4.8.0-48.51-generic/ms10-34-mcdivittB0-kernel__4.8.0-48.51__2017-04-13_16-50-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 14, failed: 1;
http://kernel.ubuntu.com/testing/4.8.0-48.51-generic/ms10-35-mcdivittB0-kernel__4.8.0-48.51__2017-04-13_16-50-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 19, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-48.51-generic/hainzel__4.8.0-48.51__2017-04-13_16-26-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hello, I tested the patch using a testing kernel from Joseph Salisbury
and it completely fixed the bug. Later, I was unable to boot to 4.8.0-42
which came with updates. I do not know why. I have never before
experienced such a problem.
What can I do to try it again better?
--
You received this
If you have a system currently running yakkety or that upgraded to you
yakkety you could look to see how many kernels the modules were built
for e.g. here's a yakkety system of mine:
[ 9:05AM 10517 ] [ bdmurray@impulse:/tmp ]
$ grep "Building for" /var/log/dist-upgrade/apt-term.log
Building
Adding some miscellaneous data points.
I'm still unable to reproduce this outside of a lgw01 compute node that
Laney set up for me, running xenial with qemu 1:2.5+dfsg-5ubuntu10.10
and linux 4.4.0-72. It doesn't happen on every host. I'm still
experimenting to see if I can reproduce this on some
Sweet, thanks adconrad!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1681566
Title:
nvidia-375 DKMS module not recompiled on upgrade to 17.04
Status in dkms package in Ubuntu:
Fix
tested on Yakkety with the -proposed 4.8.0-48-geneirc kernel, ran 16
xattr stressors for 5 minutes, no failure, passed.
** Tags removed: verification-needed-yakkety
** Tags added: verification-done-yakkety
--
You received this bug notification because you are a member of Kernel
Packages, which
For reference this is the daily build which is reported to resolve the
issues:
git://git.launchpad.net/~ubuntu-kernel-test/ubuntu/+source/linux/+git/mainline-crack
cod/tip/daily/2017-04-13 (b9b3322f13f350587f17f0a76f008830e3a420d3)
--
You received this bug notification because you are a
Shouldn't we also fix yakkety and company?
Are we sure upgrade will use the new dkms?
(probably yes, because all postinst are done after all package upgrade,
right?)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
Could you try the 4.10 mainline build and see if the bug exists there?
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10/
If that one fails for you we have a straight-forward path for bisecting
to find out what fixed the issue.
** Changed in: linux (Ubuntu)
Status: Confirmed =>
Hi,
kernel works fine with the patch on IPv6.
Thanks
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tested on xenial with the -proposed 4.4.0-74-generic kernel, ran 16
xattr stressors for 5 minutes, no failure, passed.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is
The verification of the Stable Release Update for dkms has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
This bug was fixed in the package dkms - 2.3-3ubuntu1
---
dkms (2.3-3ubuntu1) zesty; urgency=medium
* 0013-postinst-Fix-newest-kernel-detection.patch: dkms_common.postinst: We
were passing a list of kernels to get_newest_kernel(), when it expected a
single kernel as its
Also, after using the dkms from proposed, after update I see:
ubuntu@yakkety2:~$ grep "Building for" /var/log/dist-upgrade/apt-term.log
Building for 4.8.0-45-generic 4.10.0-19-generic
Building for 4.8.0-45-generic 4.10.0-19-generic
Building for architecture x86_64
** Tags removed:
I installed dkms from zesty-proposed and then upgraded from Y to Z.
bdmurray@clean-yakkety-amd64:~$ do-release-upgrade -d
Checking for a new Ubuntu release
Get:1 Upgrade tool signature [836 B]
Get:2 Upgrade tool [1,268 kB]
Fetched 1,269 kB in 0s (0 B/s)
authenticate 'zesty.tar.gz' against
I've been using the script from #57 in 16.04 & 16.10, but in 17.04 I
switched to GNOME and now the script fails since it cannot find an a2dp
sink. After some research, it seems that the problem is with GDM
starting its own pulseaudio process
tests ran: 16, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-48.51-generic/archytas__4.8.0-48.51__2017-04-13_16-10-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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-
trusty' to 'verification-done-trusty'. 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-
yakkety' to 'verification-done-yakkety'. 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-
xenial' to 'verification-done-xenial'. 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-
yakkety' to 'verification-done-yakkety'. 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-
xenial' to 'verification-done-xenial'. 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-
yakkety' to 'verification-done-yakkety'. 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-
yakkety' to 'verification-done-yakkety'. 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-
xenial' to 'verification-done-xenial'. 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-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
tests ran: 141, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-48.51-generic/gonzo__4.8.0-48.51__2017-04-13_15-38-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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-
xenial' to 'verification-done-xenial'. 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-
yakkety' to 'verification-done-yakkety'. 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-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag
tests ran: 16, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-48.51-generic/ms10-34-mcdivittB0-kernel__4.8.0-48.51__2017-04-13_16-20-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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-
xenial' to 'verification-done-xenial'. 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-
trusty' to 'verification-done-trusty'. 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-
xenial' to 'verification-done-xenial'. 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-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag
I think comment #9 was caused by either an error in some script or
incorrect reference.
** Tags removed: verification-needed-vivid
--
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/1678009
tests ran: 16, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-48.51-generic/ms10-35-mcdivittB0-kernel__4.8.0-48.51__2017-04-13_16-20-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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-
xenial' to 'verification-done-xenial'. 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-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag
@Andre,
I believe what happens here is filed at LP: #1678184.
Kernel parameter 'nvme_core.default_ps_max_latency_us=0' can workaround the
issue as a temporary fix.
Please also try other value I suggested in comment #6 in LP: #1678184.
--
You received this bug notification because you are a
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-
yakkety' to 'verification-done-yakkety'. 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-
yakkety' to 'verification-done-yakkety'. 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-
yakkety' to 'verification-done-yakkety'. 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-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag
tests ran: 37, failed: 4;
http://kernel.ubuntu.com/testing/4.8.0-48.51-generic/rumford__4.8.0-48.51__2017-04-13_15-50-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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-
yakkety' to 'verification-done-yakkety'. 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-
xenial' to 'verification-done-xenial'. 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-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Yakkety)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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-
xenial' to 'verification-done-xenial'. 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-
yakkety' to 'verification-done-yakkety'. 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-
xenial' to 'verification-done-xenial'. 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-
xenial' to 'verification-done-xenial'. 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-
trusty' to 'verification-done-trusty'. 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-
yakkety' to 'verification-done-yakkety'. 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-
yakkety' to 'verification-done-yakkety'. 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-
yakkety' to 'verification-done-yakkety'. 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-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
101 - 200 of 366 matches
Mail list logo
