** Also affects: linux (Ubuntu Trusty)
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/1655476
Title:
linux: 3.13.0-108.155 -proposed tracker
** Also affects: linux (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Precise)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Also affects: linux (Ubuntu Vivid)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Vivid)
Status: New => Confirmed
--
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)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
--- Comment From hbath...@in.ibm.com 2017-01-13 01:20 EDT---
(In reply to comment #12)
> Hello,
>
> First of all, two of the listed crash patches are in the 7.1.5-1ubuntu2
> package awaiting in zesty-proposed. It is blocked there by an FTBS on z390x.
> But even with those patches, it still
I got hit by this too a while back. I don't expect a simple system
upgrade to break my system. I ended up having to continue using an out-
of-date kernel for some time as a result.
It's still not fixed with nvidia-367 and 4.4.0-59-generic. But manually
editing /etc/default/grub and removing
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/3.13.0-108.155~precise1-generic/onza__3.13.0-108.155~precise1__2017-01-13_04-12-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-trusty in
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.9.0-13.14-generic/ms10-35-mcdivittB0-kernel__4.9.0-13.14__2017-01-13_04-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.
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/3.13.0-108.155~precise1-generic/onza__3.13.0-108.155~precise1__2017-01-13_03-47-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-trusty in
** Changed in: kernel-development-workflow/prepare-package-meta
Status: Confirmed => Fix Released
** Changed in: kernel-development-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner
(timg-tpi)
** Changed in:
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/3.19.0-80.88-generic/onza__3.19.0-80.88__2017-01-13_03-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.
** Changed in: hwe-next
Status: New => Fix Committed
--
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/1635177
Title:
mfd: intel-lpss: Add default I2C device properties for Apollo
Is linux-lts-vivid still supported? I'd expect it to be replaced by
linux-lts-xenial by now.
Thanks
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-vivid in Ubuntu.
https://bugs.launchpad.net/bugs/1655580
Title:
package
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/3.19.0-80.88-generic/modoc__3.19.0-80.88__2017-01-13_02-59-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: 1, failed: 0;
http://kernel.ubuntu.com/testing/3.19.0-80.88-generic/onza__3.19.0-80.88__2017-01-13_02-57-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 a duplicate of bug 1580659 ***
https://bugs.launchpad.net/bugs/1580659
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1580659, so it is being marked as such. Please
Already enabled proposed ,what are need to install kernel packages and
update?
--
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/1646277
Title:
Xenial server 16.04.x will have a black
** Changed in: kernel-development-workflow/prepare-package
Status: Confirmed => Fix Released
** Changed in: kernel-development-workflow/prepare-package
Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner
(timg-tpi)
--
You received this bug notification because
About this issue was happened during OS installation ,As you said
install test the 4.10-rc3 kernel under OS.but how to check and identify
the SSD modle is correctly?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1656112
Title:
Power S822LC (8335-GTB)
This test has been run dozens of times across multiple machines and
deployments and reboots. It is completely reproducible.
--
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/1652132
Title:
Public bug reported:
Upon running the virtualization test from the certification test suite,
the kvm guest test fails with the following error:
kvm_init_vcpu failed: Invalid argument
This same test works on multiple other IBM Power 8 and Openpower
servers. kvm-ok tells us that kvm
--- Comment From gcwil...@us.ibm.com 2017-01-12 17:23 EDT---
*** Bug 148837 has been marked as a duplicate of this bug. ***
--
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/1643652
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team (canonical-kernel-team) => John Donnelly
(jpdonnelly)
** Changed in: kernel-sru-workflow/promote-to-proposed
--- Comment From ru...@us.ibm.com 2017-01-12 16:29 EDT---
FYI: I just pulled the latest kdump-tools (1:1.6.1-1) for Zesty. The changes
look good. Thanks again.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-signed
Assignee: Canonical Kernel Team (canonical-kernel-team) => John Donnelly
(jpdonnelly)
--
You received this bug notification because
** Changed in: kernel-development-workflow/prepare-package-signed
Status: Confirmed => Fix Released
** Changed in: kernel-development-workflow/prepare-package-signed
Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner
(timg-tpi)
** Description changed:
This bug
The linux-
image-3.13.0-101-generic_3.13.0-101.148~lp1649326Commit5bd4d89ffc2_amd64.deb
(with linux-image-
extra-3.13.0-101-generic_3.13.0-101.148~lp1649326Commit5bd4d89ffc2_amd64.deb)
kernel failed with the "failed to get file info size/failed to alloc
highmem for files" messages noted earlier.
You can rebuild the kernel by following these steps
https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel
the file you will need to edit is here
drivers/usb/serial/ch341.c
&&
http://lxr.free-electrons.com/source/drivers/usb/serial/ch341.c
I'm sure you can recompile things by module but from
This systems was running 14.04 before I wiped and reinstalled. Never had
any issue with it.
I just did a "apt-get install linux-generic-hwe-16.04-edge", so I'm
running on 4.8.0 now. It'll take some days to see if the issue comes
returns.
--
You received this bug notification because you are a
Please do not send me emails
On 12/01/2017 20:31, Brad Figg wrote:
> ** Changed in: kernel-sru-workflow/prepare-package-signed
> Status: Confirmed => Fix Released
>
> ** Changed in: kernel-sru-workflow/prepare-package-signed
> Assignee: Canonical Kernel Team (canonical-kernel-team)
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team (canonical-kernel-team) => John Donnelly
(jpdonnelly)
** Changed in: kernel-sru-workflow/promote-to-proposed
Derivative packages from packages here can be worked on, the following tracking
bugs were opened for them:
linux-raspi2 - bug 1656087
linux-snapdragon - bug 1656089
Backport packages from packages here can be worked on, the following tracking
bugs were opened for them:
linux-lts-xenial
Public bug reported:
This bug is for tracking the 4.4.0-60.81 upload package. This bug will
contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
** Affects:
Sorry for the delay. I skipped commit b9d249e8 in the bisect.
I built the next test kernel, up to the following commit:
5bd4d89ffc2f0fe54b752f2dc05706d277459089
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1649326
Can you test that kernel and report back if
@jsalisbury
I can't find my USB3 flash (as in comment #44) which reappears after removal.
But you can search this thread - Precise is mentioned 19 times; Trusty - 29
times.
So bug still exists in Precise and Trusty.
--
You received this bug notification because you are a member of Kernel
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-signed
Assignee: Canonical Kernel Team (canonical-kernel-team) => John Donnelly
(jpdonnelly)
--
You received this bug notification because
@flocculant, thanks for testing! I can submit and SRU request for both
Xenial and Yakkety.
Can anyone confirm that this bug does in fact affect Precise and/or
Trusty?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Lo, the next step is to fully commit bisect from kernel 3.13 to 4.4 in
order to identify the last good kernel commit, followed immediately by
the first bad one. This will allow for a more expedited analysis of the
root cause of your issue. Could you please do this following
Thanks Joseph, it's working fine. We can close this out, I don't see a
point in pushing to get this specific kernel issue with 4.4.0-22
resolved by Canonical. I'll work with my manager to get the bug closed
out on our end internally.
Should I set this to won't fix or invalid?
--
You received
Bug reported upstream:
https://bugzilla.kernel.org/show_bug.cgi?id=192471
--
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/1655065
Title:
Regression: Suspend broken on Thinkpad P50 with
Kernel 4.8.0-32 introduced changes from the mainline kernels 4.8.7,
4.8.8, 4.8.9, 4.8.10 and 4.8.11 . In my testing, 4.8.8 works fine and
suspend is broken starting with 4.8.9. Furthermore, suspend is still
broken with the latest 4.8 kernel which is 4.8.17 (therefore the tag
kernel-fixed-upstream
I see the patch was already submitted for SRU per comment #9, so no need
to test the kernel posted in comment #11.
--
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/1655683
Title:
kernel
I built the next test kernel, up to the following commit:
50f208e18014589971583a8495987194724d56e4
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1650336
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on
I built a Trusty test kernel with the patch. The test kernel can be downloaded
from:
http://kernel.ubuntu.com/~jsalisbury/lp1655683/
Can you test this kernel and see if it resolves this bug?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => John Donnelly
(jpdonnelly)
** Description changed:
This bug is for tracking
--- Comment From bjki...@us.ibm.com 2017-01-11 15:09 EDT---
Paul - since this is tracking the interrupt race condition fixes coming from
your team, reassigning.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
*** This bug is a duplicate of bug 1579205 ***
https://bugs.launchpad.net/bugs/1579205
** This bug has been marked a duplicate of bug 1579205
CONFIG_NR_CPUS=256 is too low
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Alternately, as this may have been caused by my recent NVMe patches, can those
affeected by this please test with this kernel PPA which is 4.4.0-59 with my
patches reverted:
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1626894
--
You received this bug notification because you are a member
Public bug reported:
Generic Linux kernel flavor is official Ubuntu Server Linux kernel flavor.
It is supposed to be run on both workstations and servers.
Generic kernel configuration supports max 256 CPUs:
root@ubuntu02:~# grep CONFIG_NR_CPUS /boot/config-$(uname -r)
CONFIG_NR_CPUS=256
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1656033
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
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1655123/+attachment/4803488/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1655123/+attachment/4803486/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1655123/+attachment/4803485/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1655123/+attachment/4803484/+files/Lsusb.txt
--
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/1655123
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1655123/+attachment/4803490/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1655123/+attachment/4803481/+files/CRDA.txt
--
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/1655123
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1655123/+attachment/4803489/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1655123/+attachment/4803483/+files/Lspci.txt
--
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/1655123
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1655123/+attachment/4803482/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
> Kernel 4.4.0-59.80 pushed to cloud and MAAS images and retested on
failing systems.
Chris, this isn't the right bug for you. Please use your new bug
1653797.
** Changed in: linux (Ubuntu Xenial)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a
This is a perfect Kernel. In bios mode, its a one line splash screen.
--
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/1655123
Title:
Kernel 4.10 stalls on restart
Status in linux
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1655123/+attachment/4803487/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Description changed:
For rc2 and rc3, the machine stalls on first restart only (no tty) and
runs OK after (no shutdown problems). Same result when removing the
lowest Kernel (all of them). Canonical Kernel permanently stalls on
restart but runs OK. Plus, the
Thanks to you,
Got both Designer keyboard and Mouse working on Ubuntu 16.04
comment #34 solves the issue.
notice: without upgrading to v5.40 only the designer mouse will work
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in
It was not possible to create or handle the tracking bugs for the following
packages (their tracking bugs based on this update must be handled manually):
linux-lts-zesty (16.04.1)
** Changed in: kernel-development-workflow/prepare-package
Status: New => Confirmed
** Changed in:
Public bug reported:
This bug is for tracking the 4.9.0-13.14 upload package. This bug will
contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
kernel-phase:Packaging
** Changed in: linux (Ubuntu Zesty)
Status: New => Fix Committed
--
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/1655956
Title:
Zesty update to v4.9.3 stable release
Status in
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.10
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.10
Default Comment by Bridge
** Attachment added: "Patched binaries of crash and makedumpfile tools"
https://bugs.launchpad.net/bugs/1655625/+attachment/4803462/+files/patched_binaries.tar.gz
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Once the system is installed, can you test the 4.10-rc3 kernel? It can
be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc3/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Would it be possible for you to test the -proposed kernel and post back if it
resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.
Thank you in advance!
--
You received this bug notification because you are a member of
** Changed in: crash (Ubuntu Xenial)
Assignee: (unassigned) => Louis Bouchard (louis-bouchard)
** Changed in: makedumpfile (Ubuntu)
Assignee: (unassigned) => Louis Bouchard (louis-bouchard)
** Changed in: makedumpfile (Ubuntu Xenial)
Assignee: (unassigned) => Louis Bouchard
Does booting back with the Xenial kernel make the bug go away?
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
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.10
** 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
+
We discussed this feature in July 2014 and decided then to disable it.
Unless there have been significant changes to the implementation I see
no reason to reverse our decision.
https://lists.ubuntu.com/archives/kernel-team/2014-July/045006.html
** Changed in: linux (Ubuntu)
Status:
The Ubuntu kernel is now up to: 4.4.0-59.80
Can you apply the latest updates and see if this bug still exists?
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Tags added: kernel-da-key
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this
Nope, task removed.
** No longer affects: lxc (Ubuntu)
** No longer affects: lxc (Ubuntu Wily)
--
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/1542049
Title:
lxc: ADT exercise test
You may need to run the following from a terminal:
sudo apt-get install -f
sudo apt-get clean
sudo apt-get update
Then re-install the package or updates.
If that does not resolve your issue, please mark the bug as "Confirmed"
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
**
I built a Xenial test kernel with the following two commits reverted:
c630ec12d831 mm, oom: rework oom detection
57e9ef475661 mm: throttle on IO only when there are too many dirty and
writeback pages
This test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1655842/
Can
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/1655986
Title:
lowlatency kernel is lacking
Hello,
First of all, two of the listed crash patches are in the 7.1.5-1ubuntu2
package awaiting in zesty-proposed. It is blocked there by an FTBS on
z390x. But even with those patches, it still fails so I assume that the
other three patches are also needed.
But while trying to test your solution
Between 2017-01-05 and about 2017-01-10 EST we had 17 recorded crashes
on the neutron node.
After patching as described above, we have had no crashes.
Not being particularly familiar with kernel internals, or the details of
the skb data structure, I was not able to confirm explicitly the cause
Hi,
I'm in too. But my case is a little bit different and I don't see how can I
apply any patch.
I try to install Linux Mint 18.1 with my brand new Kingston 256GB SSD. When I
check the SSD with Disks it's OK, but the utility shows 100 Celsius temperature.
Then I begin the installation, choose
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => John Donnelly
(jpdonnelly)
** Description changed:
This bug is for tracking
Public bug reported:
Actual behavior:
$ sudo latencytop
mount: none is already mounted or /sys/kernel/debug busy
Please enable the CONFIG_LATENCYTOP configuration in your kernel.
Exiting...
$ grep -i latencytop /boot/config-`uname -r`
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
# CONFIG_LATENCYTOP is not
For the sake of cleanup - is there anything left in lxc to do?
--
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/1542049
Title:
lxc: ADT exercise test failing with linux-4.4.0-3.17
Status
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/1655978
Title:
Bluetooth not working in
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => Triaged
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => High
** Changed
Kernel update to 4.8.0-34 did not make any difference.
Help please.
--
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/1655356
Title:
NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s!
Public bug reported:
Bluetooth not working in Ubuntu 16.4 LTS
Dear,
I want to send files from my phone to my Laptop and vice versa through
Bluetooth. But the Bluetooth on my system doesn't work. When I turn on
the Bluetooth switch in System Settings > Bluetooth, nothing happens and
also the
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
For those that are still affected by this bug, can you please test the
following kernel:
http://kernel.ubuntu.com/~jsalisbury/lp1626894/d2b59ee-reverted/
** Tags removed: kernel-da-key
** Tags added: kernel-key
--
You received this bug notification because you are a member of Kernel
Packages,
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
** Description changed:
+ SRU Justification
+
+ Impact: The -22 firmware for iwlwifi introduces regressions with some
+ hardware versus earlier firmware versions. As no newer firmware is
+ available, the only fix is to revert back to the older firmware which
+ does work.
+
+ Test Case: Using
** Description changed:
+ SRU Justification
+
+ Impact: The usbduxsigma firmware is out of date and causes the driver to
+ fail. This is fixed by updating the firmware from upstream linux-
+ firmware.
+
+ Test Case: Using the driver with the old firmware fails. Using it with
+ the new firmware
** Changed in: linux (Ubuntu Xenial)
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.launchpad.net/bugs/1633193
Title:
Oops on EEH hit during tg3 probe
Status in
--- Comment From heinz-werner_se...@de.ibm.com 2017-01-12 07:24 EDT---
IBM Bugzilla -> closed
--
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/1634034
Title:
kvm default ubuntu
1 - 100 of 111 matches
Mail list logo
