Default Comment by Bridge
** Attachment added: "BridgeTest"
https://bugs.launchpad.net/bugs/1580951/+attachment/4703253/+files/test.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/15
I want to get it
--
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/1580951
Title:
Upgrade libseccomp from 2.2.3 ->2.3.1
Status in linux package in Ubuntu:
Invalid
Bug description:
==
Take it
--
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/1580951
Title:
Upgrade libseccomp from 2.2.3 ->2.3.1
Status in linux package in Ubuntu:
Invalid
Bug description:
== Comment:
Bridge bugproxy add comment
--
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/1580951
Title:
Upgrade libseccomp from 2.2.3 ->2.3.1
Status in linux package in Ubuntu:
Invalid
Bug descrip
Bridge test attachment for LTC bridge
** Attachment added: "Bridge TTT WOW"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1580951/+attachment/4703261/+files/test.xml
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubun
Default Comment by Bridge
** Attachment added: "BridgeTest"
https://bugs.launchpad.net/bugs/1580951/+attachment/4703242/+files/test.txt
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
You have been subscribed to a public bug:
== Comment: #1 - Heinz-Werner Seeck -
2016-05-11 05:09:09 ==
Please upgrade package libseccomp.
The new version 2.3.1 is available on github
https://github.com/seccomp/libseccomp/releases
== Comment: #2 - Heinz-Werner Seeck -
2016-05-11 05:10:59 ==
?
--- Comment From balb...@au1.ibm.com 2016-07-17 21:43 EDT---
I tried the kernel at http://people.canonical.com/~kamal/lp1573062/lp1573062.1/
and it worked fine for me
--- Comment From balb...@au1.ibm.com 2016-07-19 01:04 EDT---
Looks like I got a failure with the run on
http://pe
For the record that I had kernel tested on three systems:
Intel - 8086:1916
https://certification.canonical.com/hardware/201603-20843/submission/111744/
https://certification.canonical.com/hardware/201508-19149/submission/111756/
Intel - 8086:191b
I'm not able to finish testing on this one, this
I have always encountered this issues after fresh install of ubuntu (ubuntu
14.04, ubuntu 15.10, ubuntu 16.04) and after update or upgrade, this problem
has still remained. There was no prior kernel version where I was not having
this problem.
As you requested, I tested the latest v4.7 kernel bu
** Tags added: 201508-19027 taipei-lab
--
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/1603862
Title:
[i915_bpo] tainted kernel: lspci, udevadm crashed
Status in linux package in Ubuntu:
Same problem. Reverted to 4.4.0-28. Didn't try mainline as -28 was
sufficient.
--
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/1603719
Title:
NFS client: access problems after updating to
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
** Changed in: kernel-sru-workflow/prepare-package-lbm
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-lbm
Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee
(sforshee)
** Changed in: kernel-sru-workflow/promote-to-proposed
** 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) => Seth Forshee
(sforshee)
** Changed in: kernel-sru-workflow/prepare-package-signed
On Mon, Jul 18, 2016 at 2:48 PM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:
> Does booting back into the Trusty kernel on the Xenial installed system
> make the bug go away?
>
Yes. I've done multiple reboot experiments now and have learned the bug
only happens about 80% of the time
Attached is the kern.log from the Firestone PowerNV server. This one is
failing with stack traces which only started after we started testing
patched kernels.
The Habanero PowerNV failed with the typical locked up console and
OOM's.
** Attachment added: "kern.log"
https://bugs.launchpad.net/u
https://lists.ubuntu.com/archives/kernel-team/2016-July/079193.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/1603449
Title:
[LTCTest][Opal][OP820] Machine crashed with Oops: Kernel
BTW, I am having the issue in 14.04, after upgrading to kernel
3.19.0-65-generic. Booting with 3.19.0-64-generic and reinstalling
bcmwl-kernel-source fixes the problem.
I think we need proper instructions to sign the module, or an automated
step that takes care of that for us.
--
You received th
I tried to test the kernel that you mentioned, but unfortunately, I get
an error (can't create /sys/kernel/uevent_helper), so I couldn't start
the system with that kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
ht
I tried to solve it by following the instructions in
http://askubuntu.com/questions/760671/could-not-load-vboxdrv-after-
upgrade-to-ubuntu-16-04-and-i-want-to-keep-secur (with 'wl' as the
module) with no luck
--
You received this bug notification because you are a member of Kernel
Packages, which
Given that your apport output is from the previous kernel, this line is
very suggestive:
[ 18.073838] fglrx: module verification failed: signature and/or
required key missing - tainting kernel
The 3.13.0-92 kernel is the first one in this series which implements
Ubuntu's updated SecureBoot poli
--- Comment From gws...@au1.ibm.com 2016-07-18 21:21 EDT---
Yeah, There is only one patch should be backported and it should fix the kernel
crash. The patch is backported to Ubuntu-4.4.0-31.50 and attached. Note I
checked out the base kernel code from below git repo:
git://kernel.ubuntu.
--- Comment (attachment only) From gws...@au1.ibm.com 2016-07-18 21:15
EDT---
** Attachment added: "Backported fix to Ubuntu-4.4.0-31.50"
https://bugs.launchpad.net/bugs/1603449/+attachment/4703137/+files/0001-powerpc-eeh-Fix-invalid-cached-PE-primary-bus.patch
--
You received this
** 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) => Seth Forshee
(sforshee)
--
You received this bug notification because you are a member o
> From a terminal window please run:
> apport-collect 1603655
> and then change the status of the bug to 'Confirmed'.
...okay? As I said, I apt-get removed linux-
image-3.13.0-92-generic:amd64, so the system information *now* will show
that it's not installed. The information just posted is the st
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1603655/+attachment/4703125/+files/PulseList.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/
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1603655/+attachment/4703117/+files/CurrentDmesg.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
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1603655/+attachment/4703126/+files/UdevDb.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/1603655
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1603655/+attachment/4703123/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1603655/+attachment/4703115/+files/BootDmesg.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/
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1603655/+attachment/4703128/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1603655/+attachment/4703116/+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/1603655
Ti
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1603655/+attachment/4703127/+files/UdevLog.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/1603
apport information
** Tags added: apport-collected
** Description changed:
Last night, Ubuntu Software Updater installed a round of updates.
I shut down my computer, and when I booted this morning, the GUI failed to
load or run at all.
I switched to a terminal with Ctrl+Alt+F1, which work
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1603655/+attachment/4703124/+files/ProcModules.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/b
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1603655/+attachment/4703119/+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/1603655
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1603655/+attachment/4703121/+files/ProcCpuinfo.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/b
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1603655/+attachment/4703120/+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/1603655
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1603655/+attachment/4703122/+files/ProcEnviron.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/b
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1603655/+attachment/4703118/+files/IwConfig.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/16
Jsalisbury,
Your suggetion fits what I first attempted in order to correct the problem.
The report presented here, above, followed that correction attempt. I used
Bleachbit to clear out the issue after sudo apt-get update -f (-m) [the dash m
was added following failure with -f alone] also fa
** 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) => Seth Forshee
(sforshee)
** Description changed:
This bug is for tracking the
12.04 was the last release that will support non-PAE. The default (and
boot) kernel for 12.04 and newer 32 bit is now the PAE kernel, so there
is no easy way to install a non-PAE kernel.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification beca
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 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 th
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 kernel[0
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 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 th
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
** Cha
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 kernel[0
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 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 th
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 kernel[0
Thank you for providing a patch, and making Ubuntu better.
Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?
People
Thank you for providing a patch, and making Ubuntu better.
Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?
People
Thank you for providing a patch, and making Ubuntu better.
Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?
People
Thank you for providing a patch, and making Ubuntu better.
Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?
People
Thank you for providing a patch, and making Ubuntu better.
Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?
People
Thank you for providing a patch, and making Ubuntu better.
Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?
People
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: zfs-linux (Ubuntu)
Status: Confirmed => Triaged
** Tags added: xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https
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 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 th
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 kernel[0
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 kernel[0
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Tags added: kernel-da-key
--
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/1602299
Title:
bcache is unstable on ppc64el
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 kernel[0
Thanks for the update. I'll mark this bug as invalid per your comment.
If the bug does happen again, just change the status back to confirmed.
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received
It might be best to upgrade to 16.04(Xenial) since Vivid is now EOL.
--
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/1603397
Title:
booting new 3.19.0-65, monitor stays in power save
Sta
Adding ath10k/QCA6174/hw2.1/board-pci-168c:0041:17aa:3545.bin (from the
working board.bin in this thread) seems to fix it, though:
e6adc90ecaf55edc656990c6c50193ac board-pci-168c:0041:17aa:3545.bin
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
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/1603397
Title:
booting new 3.19.0-65, monitor stays in power save
Status in
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 perf
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => Confirmed
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: New => Confirmed
** Description changed:
This bug
Would it be possible for you to test the latest upstream stable kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v4.4 stable kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel d
Acting on Cyril's suggestion above, I downloaded the Debian 8.0-2 source
package, rebuilt it locally, and installed it. It seems to have fixed
the problem for me. So perhaps the problem really is in the Ubuntu
delta?
--
You received this bug notification because you are a member of Kernel
Package
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"
** Tags added: kernel-da-key
** Changed in: linux (Ubuntu)
S
Hm, not fixed for me. still seeing firmware crashes. :(
** Changed in: linux-firmware (Ubuntu Xenial)
Status: Fix Released => Confirmed
** Changed in: linux-firmware (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Kerne
Do you have a machine that could be used to test some kernels? If so,
we can perform a kernel bisect to identify the commit that caused the
regression.
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => Tr
** Tags added: kernel-key
--
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/1602577
Title:
[arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel
Status in linux package in
On 19/07/16 06:49, Joseph Salisbury wrote:
> Does booting back into the prior kernel make the bug go away?
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => High
>
> ** Tags added: kernel-da-key
>
The bug has gone away. It was there a couple of times and then it did
not reappear.
-
** 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/1603483
Title:
[Xenial] Include Huawei PCIe SSD hio kernel
Guo Wen Shan - how about if you take a stab at the backports for these 2
patches, 'cause I don't think they make sense for a 4.4 kernel.
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Ch
First off, sorry if this comment is redundant.
I cannot say for sure whether the issue happened after an update. I run
apt-get upgrade very often and thus cannot peg it down to an update. I
have definitely not upgraded (dist-upgrade) my Ubuntu version.
I will give the latest kernel a shot, but, I
I don't think I can run apport-collect. So far, I've had it happen about
3-4 times over 30 hours of uptime. If it does happen again, _and_ I'm
able to start a vnc session, _and_ said vnc session works, I will
definitely update this bug report with the logs.
--
You received this bug notification b
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => Confirmed
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: New => Confirmed
** Description changed:
This bug
Backport packages from packages here can be worked on, the following tracking
bugs were opened for them:
linux-lts-vivid (14.04.1) - bug 1604159
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Changed in: kernel-sru-workflow/prepare-package-meta
Statu
** 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) => Seth Forshee
(sforshee)
** Description changed:
This bug is for tracking the
Public bug reported:
This bug is for tracking the 3.19.0-66.74~14.04.1 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
-- swm properties --
This version is working correctly.
--
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/1571798
Title:
Broadwell ECRC Support missing in Ubuntu
Status in linux package in Ubuntu:
In Progres
Attached, @jjo reports positive bcache smoke test results with the lts-x
'hio' test kernel.
** Attachment added: "hio-bcache-test-result-jjo.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603483/+attachment/4703082/+files/hio-bcache-test-result-jjo.txt
--
You received this bug no
Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?
People affected by this bug are probably wondering why the kernel t
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 kernel[0
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 kernel[0
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 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 th
Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?
People affected by this bug are probably wondering why the kernel t
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bug
Does booting back into the Trusty kernel on the Xenial installed system
make the bug go away?
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to lin
Public bug reported:
This bug is for tracking the 3.19.0-66.74 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: kernel-sru-workf
Does booting back into the prior kernel make the bug go away?
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launc
I built the next test kernel, up to the following commit:
134cd00d766fc7014b53d9cea67a6bcb894ae51e
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1571798
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on y
Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?
People affected by this bug are probably wondering why the kernel t
Can you also test the latest upstream 4.4 kernel? This will tell us if
the fix in mainline was already sent to stable or not. The 4.4.15
kernel can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.15
--
You received this bug notification because you are a member of Kernel
** 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) => Andy Whitcroft
(apw)
** Changed in: kernel-development-work
Public bug reported:
This bug is for tracking the 3.13.0-93.140~precise1 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
-- swm properties
1 - 100 of 207 matches
Mail list logo
