*** This bug is a duplicate of bug 1637520 ***
https://bugs.launchpad.net/bugs/1637520
Is it really a good idea to mark this well-described bug as a duplicate
of something that just describes a solution?
I find one of the most valuable things we can do to propel the community
forward is to ha
That's fine but I go on holiday tomorrow for a couple of weeks so it
will have to wait till I get back. Will let you know as soon as I have
the results.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpa
tests ran: 18, failed: 0;
http://kernel.ubuntu.com/testing/3.13.0-103.150~precise1-generic/onibi__3.13.0-103.150~precise1__2016-11-30_00-08-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 Ubunt
The verification of the Stable Release Update for linux 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 re
This bug was fixed in the package linux - 3.2.0-116.158
---
linux (3.2.0-116.158) precise; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1640549
* xen:balloon errors in 14.04 beta (LP: #1304001)
- xen/balloon: cancel ballooning if adding new memory fail
This bug was fixed in the package linux - 3.2.0-116.158
---
linux (3.2.0-116.158) precise; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1640549
* xen:balloon errors in 14.04 beta (LP: #1304001)
- xen/balloon: cancel ballooning if adding new memory fail
The verification of the Stable Release Update for linux 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 re
after applying the 3 patchset from :
https://www.redhat.com/archives/dm-devel/2016-June/msg00399.html
https://www.redhat.com/archives/dm-devel/2016-June/msg00400.html
https://www.redhat.com/archives/dm-devel/2016-June/msg00401.html
building the ubuntu kernel fails :
apt-get source -b linux-image-
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/3.13.0-103.150~precise1-generic/onza__3.13.0-103.150~precise1__2016-11-30_00-45-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 Ubuntu
Alternatively, you can do it without install new kernel + load the
updated kernel driver. This is useful if you wanna run on stock kernel
or we want to test different version of thinkpad_acpi.c
1. download "thinkpad_acpi.tar"
2. run "tar -xvf thinkpad_acpi.tar"
3. run "cd thinkpad_acpi"
4. compil
The deb package can be found @
http://people.canonical.com/~alexhung/LP1644670/
--
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/1644670
Title:
cannot use tablet mode lid sensor on yoga 46
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/3.13.0-103.150~precise1-generic/onza__3.13.0-103.150~precise1__2016-11-30_00-15-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 Ubuntu
nevermind. I managed to build kernel package.
--
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/1644670
Title:
cannot use tablet mode lid sensor on yoga 460
Status in linux package in Ubun
I can confirm this bug for Xubuntu 16.04
Kmoc's workaround does not help.
Please tell me how I can assist with further information.
--
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/998310
T
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-firmware (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/3.13.0-103.150~precise1-generic/onibi__3.13.0-103.150~precise1__2016-11-29_23-48-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 Ubunt
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/3.13.0-103.150~precise1-generic/dwalin__3.13.0-103.150~precise1__2016-11-29_23-38-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 Ubun
tests ran: 2, failed: 0;
http://kernel.ubuntu.com/testing/4.9.0-3.4-generic/gonzo__4.9.0-3.4__2016-11-29_23-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.
https://bugs.launchpad.net/bugs/1642
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/3.13.0-103.150~precise1-generic/onibi__3.13.0-103.150~precise1__2016-11-29_23-27-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 Ubunt
Public bug reported:
On laptops with Kaby Lake processors and Sunrise point chipsets
(System76 Lemu7), updating to the current (1.157.5) version of the
linux-firmware package and then updating initramfs causes sound issues.
This can manifest in two ways:
1: Volume hotkeys and controls appear to w
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/3.13.0-103.150~precise1-generic/dwalin__3.13.0-103.150~precise1__2016-11-29_23-21-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 Ubun
> Did you install squashfuse in your container?
Thanks, that was the missing link. Works after installing squashfuse.
For anyone else wondering, instructions are in the description of
lp:1630789.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscri
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/3.13.0-103.150~precise1-generic/onza__3.13.0-103.150~precise1__2016-11-29_23-13-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 Ubuntu
tests ran: 141, failed: 0;
http://kernel.ubuntu.com/testing/4.9.0-3.4-generic/gonzo__4.9.0-3.4__2016-11-29_22-16-00/results-index.html
--
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/1642
Those are just warnings "W: Possible" that can be ignored.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1642709
Title:
linux-firmware on Trusty is missing i915 binaries
Statu
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/3.13.0-103.150~precise1-generic/onza__3.13.0-103.150~precise1__2016-11-29_22-51-00/results-index.html
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => Invalid
** Tags added: regression-testing-passe
Thanks!
--
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/1644394
Title:
Botched backport breaks level triggered EOIs in QEMU guests with
--machine kernel_irqchip=split
Status in linux p
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-
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/1645876
Title:
*ERROR* CPU pipe A and B FIFO
--- Comment From mauri...@br.ibm.com 2016-11-29 17:04 EDT---
Hi Canonical
(@hendrix @timg-tpi)
Attaching proper backports of the 3 patches [1] for 16.04.x.
Built and verified on top of ubuntu-xenial.git master-next -- currently,
52.73 at 44b1707bf297 ("kvm/irqchip: kvm_arch_irq_routing_up
--- Comment on attachment From mauri...@br.ibm.com 2016-11-29 17:00
EDT---
Backport for 16.04 --
0002-powerpc-implement-the-DMA_ATTR_NO_WARN-attribute.patch
** Attachment added: "Backport for 16.04 --
0002-powerpc-implement-the-DMA_ATTR_NO_WARN-attribute.patch"
https://bugs.launch
--- Comment on attachment From mauri...@br.ibm.com 2016-11-29 17:00
EDT---
Backport for 16.04 -- 0003-nvme-use-the-DMA_ATTR_NO_WARN-attribute.patch
** Attachment added: "Backport for 16.04 --
0003-nvme-use-the-DMA_ATTR_NO_WARN-attribute.patch"
https://bugs.launchpad.net/bugs/163312
--- Comment on attachment From mauri...@br.ibm.com 2016-11-29 16:59
EDT---
Backport for 16.04 --
0001-dma-mapping-introduce-the-DMA_ATTR_NO_WARN-attribute.patch
** Attachment added: "Backport for 16.04 --
0001-dma-mapping-introduce-the-DMA_ATTR_NO_WARN-attribute.patch"
https://bug
** Changed in: linux (Ubuntu)
Assignee: Taco Screen team (taco-screen-team) => Canonical Kernel Team
(canonical-kernel-team)
--
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/1645390
Ti
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1645876/+attachment/4784867/+files/version.log
--
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/164
Public bug reported:
I have an external monitor attached to my laptop and am using a ThinkPad
OneLink+ docking station.
I repeatedly have issues where if I lock the screen and unlock it,
windows return to the incorrect window (my laptop window). I also have
crossed out icons (red circle with a li
> Is there any update on this issue?
I'm still debugging, but can give a summary of the problem, at least on
the system I'm working on.
First, to address:
> One is the vfree WARNING which indicates that the error paths are not quite
> right
this is a trival fix to the error handling path; it's
tests ran: 141, failed: 0;
http://kernel.ubuntu.com/testing/4.9.0-3.4-generic/gonzo__4.9.0-3.4__2016-11-29_20-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.
https://bugs.launchpad.net/bugs/1642
--- Comment From b...@us.ibm.com 2016-11-29 16:31 EDT---
Are these three patches also in Xenial?
[PATCH 1/3] UBUNTU: SAUCE: (noup) target/user: Use sense_reason_t in
tcmu_queue_cmd_ring
[PATCH 2/3] UBUNTU: SAUCE: (noup) target/user: Return an error if cmd data size
is too large
[PATCH 3/
Default Comment by Bridge
** Attachment added: "Traceback.txt"
https://bugs.launchpad.net/bugs/1639920/+attachment/4784845/+files/Traceback.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.ne
Default Comment by Bridge
** Attachment added: "modified.conffile..etc.apport.crashdb.conf.txt"
https://bugs.launchpad.net/bugs/1639920/+attachment/4784846/+files/modified.conffile..etc.apport.crashdb.conf.txt
--
You received this bug notification because you are a member of Kernel
Packages,
Actually, I believe it has not been released yet. The fix is in the
changelog for 4.4.0-48.69, but the latest release of the xenial LTS
kernel is 4.4.0-47.68 where the bug can still be reproduced.
Specifically:
* Xenial update to v4.4.25 stable release (LP: #1634153)
- timekeeping: Fix __kti
Default Comment by Bridge
** Attachment added: "ProcPpc64.tar.gz"
https://bugs.launchpad.net/bugs/1639920/+attachment/4784844/+files/ProcPpc64.tar.gz
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launch
Can you see if the commit that fixes this in minline has alread been
sent to upstream 4.4 stable? It can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.35/
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xen
tests ran: 64, failed: 0;
http://kernel.ubuntu.com/testing/4.9.0-3.4-generic/beketov__4.9.0-3.4__2016-11-29_20-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.
https://bugs.launchpad.net/bugs/16
Thanks for the update and sorry for the delay.
I'll start a kernel bisect between v4.8-rc8 and v4.8 final. A bisect
will required testing about 10 kernels, but will tell us the commit that
introduced this regression.
Could you also test the v4.9-rc7 kernel to see if this bug is already fixed in
This kernel was also good
--
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/1642739
Title:
Kernel panic on shutdown
Status in linux package in Ubuntu:
Confirmed
Status in linux source pa
** Changed in: linux (Ubuntu)
Status: Triaged => Invalid
** Changed in: linux-ppc (Ubuntu)
Status: Triaged => Invalid
--
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/1279403
** Changed in: linux (Ubuntu Xenial)
Status: Incomplete => Fix Released
** Changed in: linux (Ubuntu)
Status: Incomplete => 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
** Changed in: zfs-linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1624844
Title:
Ubuntu 16.04 breaks boot with wrong zpool.ca
Sorry for the delay, and thanks for testing. It looks like we have to
test older kernels to find the last good one and first bad one. Can you
test the following:
3.14: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-trusty/
4.0: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-vivid/
4.2:
*** This bug is a duplicate of bug 1637520 ***
https://bugs.launchpad.net/bugs/1637520
** This bug has been marked a duplicate of bug 1637520
Yakkety update to v4.8.5 stable release
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to l
** Attachment added: "bug 1644919 - error message install kernel"
https://bugs.launchpad.net/bugs/1644919/+attachment/4784829/+files/bug%201644919%20-%20error%20message%20install%20kernel
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
I can build a test kernel with the V2 version of the patch.
Has there been any response from upstream on the patch? It doesn't look like
it landed in mainline as of yet.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Xen
I'll try out the latest upstream kernel tonight.
The computer started out with Windows 10 and it was super buggy and I
wanted to give Ubuntu a shot. I installed this kernel via USB. I have
not tried a previous version of Ubuntu yet.
Some additional behavior notes:
Currently when I resume from a
--- Comment From b...@us.ibm.com 2016-11-29 14:40 EDT---
I have updated to verification-done-yakkety
** Tags removed: verification-needed-yakkety
** Tags added: verification-done-xenial verification-done-yakkety
--
You received this bug notification because you are a member of Kernel
Pac
tests ran: 18, failed: 15;
http://kernel.ubuntu.com/testing/4.9.0-3.4-generic/gonzo__4.9.0-3.4__2016-11-29_19-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.
https://bugs.launchpad.net/bugs/164
tests ran: 10, failed: 1;
http://kernel.ubuntu.com/testing/4.9.0-3.4-generic/pepe__4.9.0-3.4__2016-11-29_19-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.
https://bugs.launchpad.net/bugs/16420
tests ran: 18, failed: 1;
http://kernel.ubuntu.com/testing/4.9.0-3.4-generic/lagalla__4.9.0-3.4__2016-11-29_19-06-00/results-index.html
--
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/16
tests ran: 18, failed: 1;
http://kernel.ubuntu.com/testing/4.9.0-3.4-generic/gonzo__4.9.0-3.4__2016-11-29_18-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.
https://bugs.launchpad.net/bugs/1642
** 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.
https://bugs.launchpad.net/bugs/1642299
Title:
Fix Kernel Crashing under IBM Virtual Scsi Driver
Status
tests ran: 19, failed: 1;
http://kernel.ubuntu.com/testing/4.9.0-3.4-generic/fozzie__4.9.0-3.4__2016-11-29_18-56-00/results-index.html
--
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/164
Hi Joseph,
Many thanks for this. Install was unsuccessful and no change to behaviur
(see below)
Have just tried but bug 1573206 (unable to install third-party deb
files) didn't run the *.deb file in software update
gdebi crashed also when I tried to run from there
See attached *.txt file - du
No, this issue appears also if I boot from the kernel that I was running
prior to 29.11.2016. But now I restored BIOS configuration to BIOS
default and it has resumed also on battery power - but it also two times
crashed. I am not sure that is not hardware issue - tomorrow I will test
start live Ub
https://lists.ubuntu.com/archives/kernel-team/2016-November/081180.html
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Ti
No, I'm sorry, this is a typo: I need to add tag 'kernel-bug-exists-
upstream'.
These messages are not editable, are they?
--
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/1645011
Title:
tests ran: 10, failed: 0;
http://kernel.ubuntu.com/testing/4.9.0-3.4-generic/pepe__4.9.0-3.4__2016-11-29_17-56-00/results-index.html
--
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/16420
This was a fresh install to a brand new laptop that took place 2 days
before the bug was filed.
Please tell me how to add the tag 'kernel-fixed-upstream'.
Thank you!
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a mem
Those updates should get applied during this stable release cycle. Here
is the current schedule:
Current cycle: 25-Nov through 17-Dec
25-Nov Last day for kernel commits for this cycle
28-Nov - 03-Dec Kernel prep wee
OK, so reboot and try again:
sebastian@bnasws02[0r/0s]:~
$ uptime
19:42:56 up 1 min, 1 user, load average: 1.50, 0.67, 0.25
sebastian@bnasws02[0r/0s]:~
$ uname -a
Linux bnasws02 4.9.0-040900rc7-generic #201611271731 SMP Sun Nov 27 22:33:44
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
sebastian@bnas
Yes, it worked in the past on 14.04.
After installing upstream 4.9.0-040900rc7-generic it also works right
after rebooting the machine:
sebastian@bnasws02[0r/0s]:~
$ uname -a
Linux bnasws02 4.9.0-040900rc7-generic #201611271731 SMP Sun Nov 27 22:33:44
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
seba
** Description changed:
System:Kernel: 4.4.0-47-generic x86_64 (64 bit gcc: 5.4.0)
-Desktop: MATE 1.14.1 (Gtk 3.18.9-1ubuntu3.1)
-Distro: Linux Mint 18 Sarah
+ Desktop: MATE 1.14.1 (Gtk 3.18.9-1ubuntu3.1)
+ Distro: Linux Mint 18 Sarah
Machine:
Did you install squashfuse in your container?
--
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/1611078
Title:
Support snaps inside of lxd containers
Status in Snappy:
Fix Released
Statu
I installed
linux-image-4.9.0-040900rc7-generic_4.9.0-040900rc7.201611271731_amd64.deb
Bug exists.
--
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/1645011
Title:
CyPS/2 Cypress Trackpad
Awesome, thanks Colin!
--
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/1637619
Title:
ext4dist strange timings on ubuntu 16.04
Status in Linux:
New
Status in linux package in Ubuntu:
So the fix apparently landed in Xenial updates under a generic updates
bug number:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1624037
The commit in Xenial is:
commit 8faecee97860f66fdcc67de58803b1fb4e0b0848
Author: John Stultz john.stu...@linaro.org
Date: Tue Aug 23 16:08:21 2016 -0700
Dear Joseph, I tried with kernel
4.9.0-040900rc7_4.9.0-040900rc7.201611271731_all.deb but bug still exists.
Regards,
Diego Veas
On 29/11/16 14:34, Joseph Salisbury wrote:
> Did this issue start happening after an update/upgrade? Was there a
> prior kernel version where you were not having th
tests ran: 18, failed: 1;
http://kernel.ubuntu.com/testing/4.9.0-3.4-generic/amura__4.9.0-3.4__2016-11-29_17-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.
https://bugs.launchpad.net/bugs/1642
Default Comment by Bridge
** Attachment added: "Patch v2"
https://bugs.launchpad.net/bugs/1645826/+attachment/4784821/+files/0001-powerpc-eeh-Remove-EEH_PE_PRI_BUS-in-full-hotplug-recovery.patch
** Changed in: ubuntu
Assignee: (unassigned) => Taco Screen team (taco-screen-team)
** Packa
Can you see if this new regression is also occurring with the current mainline
kernel:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc7/
Commit 4c63c2454eff996 fixes the original bug, but introduced a new bug.
Testing mainline will tell us if the new bug is already fixed in
mainline. If it
You have been subscribed to a public bug:
== Comment: #26 - Andrew Donnellan - 2016-11-24 19:55:52 ==
Ubuntu kernel team, please apply the following fixup to the Xenial kernel tree.
--
>From 631804b1548b035cada4b2c14ab708310a8aa607 Mon
@Emsi, right now there are only Xenial and Yakkety test kernels with all
the updated patches. I will have a Trusty test kernel available
shortly.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/
Thanks for the update, Chris. I'll submit SRU request for Yakkety,
Xenial and Vivid. I'm still getting some build failures with Trusty and
Precise, but should have test kernels for them shortly.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscrib
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.9.0-3.4-generic/rumford__4.9.0-3.4__2016-11-29_18-07-00/results-index.html
--
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/16
Hi Canonical,
Is there any update on this issue?
Thanks,
Dexter
--
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/1639920
Title:
NVMe detection failed during bootup
Status in linux pack
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.9.0-3.4-generic/michael__4.9.0-3.4__2016-11-29_18-07-00/results-index.html
--
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/16
Tried with Joe's kernel above:
ubuntu@brief-badger:~$ uname -a
Linux brief-badger 4.9.0-040900rc6-generic #201611201731 SMP Sun Nov 20
22:33:21 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
** Attachment added: "c6320p_info_kernel_4.9-rc6.tgz"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/16
Dear Joseph,
this issue started after a new installation (I bought my computer with
Windows 10). I'll try the upstream kernel.
Regards,
Diego Veas
On 29/11/16 14:34, Joseph Salisbury wrote:
> Did this issue start happening after an update/upgrade? Was there a
> prior kernel version where yo
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1643558
Title:
bnx2x driver crash
Status in linux package in Ubuntu:
Xiong, the BIOS level on the machine is 1.0.0 . Where would I get the
latest BIOS?
--
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/1643087
Title:
Yakkety failures on Xeon Phi (Dell Power
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.9.0-3.4-generic/gonzo__4.9.0-3.4__2016-11-29_17-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.
https://bugs.launchpad.net/bugs/1642
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.9.0-3.4-generic/fozzie__4.9.0-3.4__2016-11-29_17-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.
https://bugs.launchpad.net/bugs/164
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.9 kernel[0
** Changed in: linux (Ubuntu Xenial)
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.
https://bugs.launchpad.net/bugs/1645278
Title:
Upstream stable 4.4.34 and 4.8.10 regressio
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)
Status: Confirmed => Incomplete
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
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.laun
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
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.laun
** Package changed: linux-lts-xenial (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Changed in: linux (Ubuntu)
Importance: Medium => High
** Also affects: linux (Ubuntu Xenial)
Impo
** Changed in: linux (Ubuntu Xenial)
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.
https://bugs.launchpad.net/bugs/1642299
Title:
Fix Kernel Crashing under IBM Virtual Scsi
** Changed in: linux (Ubuntu Xenial)
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/1645453
Title:
Xenial update to v4.4.35 stable release
Status in
201 - 300 of 375 matches
Mail list logo
