** 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
--
You received this bug notificat
Derivative packages from packages here can be worked on, the following tracking
bugs were opened for them:
linux-raspi2 - bug 1611238
linux-snapdragon - bug 1611239
Backport packages from packages here can be worked on, the following tracking
bugs were opened for them:
linux-lts-xenial (14.04.1)
Meanwhile ALSA 1.1.2 is out for alsa-utils and alsa-lib, see http://www
.alsa-project.org/main/index.php/Changes_v1.1.1_v1.1.2
** Summary changed:
- Upgrade to 1.1.1 that was released in March 2016
+ Upgrade to 1.1.2 that was released in August 2016
--
You received this bug notification because
Public bug reported:
This bug is for tracking the 3.19.0-67.75 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
--- 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
Public bug reported:
This bug is for tracking the 3.19.0-67.75~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 --
Backport packages from packages here can be worked on, the following tracking
bugs were opened for them:
linux-lts-vivid (14.04.1) - bug 1611259
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Changed in: kernel-sru-workflow/prepare-package-meta
Statu
Public bug reported:
Kernel shipped with Ubuntu 16.04.1 cannot recognize fakeRaid created
from Ubuntu 14.04. I've tried three ways but none of them work.
1. Update 14.04.4 to 16.04.1
2. Fresh install 16.04.1
3. Update kernel to linux-images-4.4.0-34-generic only
The result is that the mapper was
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1611277
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 commen
Public bug reported:
This bug is for tracking the 3.13.0-94.141 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-work
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1611277/+attachment/4717391/+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
apport information
** Tags added: apport-collected trusty
** Description changed:
Kernel shipped with Ubuntu 16.04.1 cannot recognize fakeRaid created
from Ubuntu 14.04. I've tried three ways but none of them work.
1. Update 14.04.4 to 16.04.1
2. Fresh install 16.04.1
3. Update kern
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1611277/+attachment/4717395/+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: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1611277/+attachment/4717390/+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: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1611277/+attachment/4717396/+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
Public bug reported:
This bug is for tracking the 3.13.0-94.141~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
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1611277/+attachment/4717398/+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: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1611277/+attachment/4717397/+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: "CRDA.txt"
https://bugs.launchpad.net/bugs/1611277/+attachment/4717389/+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/1611277
Ti
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1611277/+attachment/4717394/+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/1611277/+attachment/4717393/+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/1611277
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1611277/+attachment/4717399/+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/1611277
Derivative packages from packages here can be worked on, the following tracking
bugs were opened for them:
linux-keystone - bug 1611289
Backport packages from packages here can be worked on, the following tracking
bugs were opened for them:
linux-lts-trusty (precise1) - bug 1611290
** Changed i
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1611277/+attachment/4717388/+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: "Lspci.txt"
https://bugs.launchpad.net/bugs/1611277/+attachment/4717392/+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/1611277
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1611277/+attachment/4717400/+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/1611
** 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
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1611277/+attachment/4717401/+files/WifiSyslog.txt
** Description changed:
Kernel shipped with Ubuntu 16.04.1 cannot recognize fakeRaid created
from Ubuntu 14.04. I've tried three ways but none of the
You have been subscribed to a public bug:
Internal Test only
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Tags: architecture-s39064 bugnameltc-144632 severity-low
targetmilestone-inin1610
--
Test Featu
Public bug reported:
Internal Test only
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Tags: architecture-s39064 bugnameltc-144632 severity-low
targetmilestone-inin1610
** Tags added: architecture-s39064
Looks 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/1611298
Title:
Test Feature to verify the Bugzilla-LP bride to create Private LP
entries
Status in linux package in Ubuntu:
However, this was not a private bug. And skipper-screen-team are not
added to the subscribers of the bug report.
--
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/1611298
Title:
Test Featur
Regarding "lubuntu freezes now sometimes and is not of the most stable one"
This is most likely nothing to do with the bug title concerning "a non-pae
processor".
Freezing may have a hardware cause; for example a laptop that ran okay for a
while but did freeze was found to have a fan that was to
/mvac21dellCompaqNx6325FanDust.jpg
Freezing may have a hardware cause; for example a laptop that ran okay
for a while but did freeze was found to have a fan that was totally
clogged up with compressed dust. After cleaning it runs Xubuntu 14.04
for months (with overnight hibernation) with no stab
** Attachment added: "htop ram usage (16.04.1 LTS) gnome"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1572801/+attachment/4717412/+files/htop.png
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
I'm not sure what your asking or saying? but i have attached a couple of
screen shots of my systems idle ram usage i understand Removing
evolution completely is messy, but disabling is relatively
straightforward.
Of course this should have been done using dpkg divert and whatever, to
not confuse a
** Attachment added: "ram usage idle after workaround!"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1572801/+attachment/4717411/+files/dtop.png
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
Public bug reported:
This bug is for tracking the 3.2.0-108.149 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-work
Public bug reported:
This bug is for tracking the 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 --
kernel-stable-maste
Public bug reported:
This bug is for tracking the 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 --
kernel-stable-maste
This tracking bug was opened to be worked from linux-3.2.0-108.149
update (bug 1611303)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-ti-omap4 in Ubuntu.
https://bugs.launchpad.net/bugs/1611312
Title:
linux-ti-omap4: -proposed
Derivative packages from packages here can be worked on, the following tracking
bugs were opened for them:
linux-ti-omap4 - bug 1611312
linux-armadaxp - bug 1611313
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Changed in: kernel-sru-workflow/prepare-packa
This tracking bug was opened to be worked from linux-3.2.0-108.149
update (bug 1611303)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1611313
Title:
linux-armadaxp: -proposed
** 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
ok thanks, I hope it will be fixed before 16.10 is releases because it
will use linux 4.8 by default.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1595765
Title:
bcmwl-kernel-source 6.
Following the guide on https://wiki.ubuntu.com/Kernel/MainlineBuilds I
have installed kernel 4.7.0-040700-generic. The system has currently
been up for 3 days and 5 hours (suspended multiple times) without
freezing. I've not installed Chrome yet.
I noticed the cursor would stutter just before a fr
You have been subscribed to a public bug:
== Comment: #0 - PAVAMAN SUBRAMANIYAM - 2016-07-13
01:28:56 ==
---Problem Description---
Machine crashed with Oops: Kernel access of bad area, sig: 11 [#1]
---uname output---
Linux ltc-garri2 4.4.0-30-generic #49-Ubuntu SMP Fri Jul 1 10:00:36 UTC 2016
This warning means that the driver references the firmware but that it
isn't installed. Intel has not yet pushed out this firmware to upstream
linux-firmware, once they have done so it will make it's way into
Ubuntu. I'll also point out that we don't officially support any
4.8-based kernels yet, an
** Package changed: kernel-package (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/1603449
Title:
[LTCTest][Opal][OP820] Machine crashed with Oops: Kernel acces
** Changed in: linux (Ubuntu Vivid)
Status: Fix Released => Fix Committed
** Changed in: linux (Ubuntu Xenial)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
So running the upstream 4.7.0 kernel and had 0 failures out of 31 runs
so it's pretty safe to assume that this isn't an affect upstream.
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu
** Tags removed: kernel-da-key
** 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/1573062
Title:
memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
It wasn't expected that the system would not boot. The 4.8-rc1 kernel
is now available, can you give it a try:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc1/
** Tags removed: kernel-key
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Kern
** Tags removed: kernel-key
** 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/1610320
Title:
stress-ng memory testing causes Arm64 system to hang
Status in lin
--- Comment From heinz-werner_se...@de.ibm.com 2016-08-09 10:12 EDT---
This is the commit. does that help?
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/xenial/commit/?h=master-
next&id=ab72705a2737c90c03d24b91afa10ef1b7403448
--
You received this bug notification b
Public bug reported:
[Impact]
For interrupt controller that doesn't support irq_disable and hardware
with level interrupt, an extra interrupt may be pending. This patch fixes
the issue by setting IRQ_DISABLE_UNLAZY flag for the interrupt line,
as suggested by,
'commit e9849777d0e2 ("genirq: Add f
The upstream commit that fixes this is:
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/net/ethernet/apm/xgene?id=b5d7a06906a4875524f5c61c0b312828bf6737de
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linu
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1611399
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 commen
The standard kernel config for 16.04 has:
...
CONFIG_MEMCG=y
CONFIG_MEMCG_SWAP=y
# CONFIG_MEMCG_SWAP_ENABLED is not set
...
I've not re-compiled with CONFIG_MEMCG_SWAP_ENABLED set to see if it
fixes the issue.
--
You received this bug notification because you are a member of Kernel
Packages, wh
You have been subscribed to a public bug:
After upgrading to the current kernel (4.4.0-34-generic) I am not able
to log in to my Kubuntu 16.04 at a Lenovo T430 while it is mounted to a
docking station.
Ubuntu boots until I need to enter the passphrase for my crypted disk,
but anyhow the system th
Hauke, as you're saying that the kernel is the cause of your problems
I'm reassigning this bug against the kernel.
You also say that using your laptop in a docking station is when
problems occur, another reason to reassign against the kernel - see
https://wiki.ubuntu.com/Bugs/FindRightPackage#Hard
@David, yes with few exceptions the kernel gets backported to Trusty HWE
after it's released for Xenial. As an example, the 4.4.0-34 kernel was
just released for Xenial and is also in Trusty as HWE already.
--
You received this bug notification because you are a member of Kernel
Packages, which
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1611283
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 commen
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
Comment #4 should have said the "latest v4.8 kernel"
--
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/1611283
Title:
entering crypto passphrase while notebook is mounted to docking
stati
Linux xavier 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC
2016 x86_64 x86_64 x86_64 GNU/Linux
Ubuntu 16.04.1 LTS (Xenial Xerus). Using external monitor and laptop lip
closed.
[52362.767655] WARNING: CPU: 0 PID: 2811 at
/build/linux-dcxD3m/linux-4.4.0/drivers/gpu/drm/i915/intel_display
Comment #17 should have said the "latest v4.8 kernel"
--
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/1611277
Title:
Kernel Shipped With Ubuntu 16.04.1 Cannot Recognize fakeRaid
Status i
** 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
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
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
Adding log (nonworking-rmmod.txt) from when unloading the module too...
** Attachment added: "nonworking-rmmod.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1600624/+attachment/4717654/+files/nonworking-rmmod.txt
--
You received this bug notification because you are a member of
Attached to this comment is a debug log (non-working-state_modprobe.txt)
from the brcmfmac module while loading it but network-card failing to
come up as it should.
Module loaded with:
$ cat /etc/modprobe.d/brcmfmac.conf
options brcmfmac debug=0xff roamoff=1
** Attachment added: "non-workin
Will attempt to capture some more logs when the card is working and when
goes into the problematic state.
--
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/1600624
Title:
MacBook wifi doesn
git://kernel.ubuntu.com/rtg/ubuntu-trusty.git arm64-efi-lp1608854
I backported EFI functionality for arm64 and amd64 from Utopic (v3.16)
to Trusty (v3.13) because much of the arch dependent infrastructure in
v3.16 is required in order to support signed module enforcement with a
MOK managed key ove
tests ran: 10, failed: 10;
http://kernel.ubuntu.com/testing/4.4.0-30.49/s2lp6g002__4.4.0-30.49__2016-08-09_16-25-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/160
Is testing the upstream kernel able to reverse back to the original
state just like I install the 4.4.0-34-generic on Ubuntu 14.04.4?
After the trial, am I able to remove the upstream kernel with apt-get
remove and purge? Thanks.
--
You received this bug notification because you are a member of
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.8 kernel[0
tests ran: 5, failed: 5;
http://kernel.ubuntu.com/testing/4.4.0-30.49/s2lp6g002__4.4.0-30.49__2016-08-09_16-31-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/1609
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.8 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.8 kernel[0
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.8 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.8 kernel[0
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 => Medium
**
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.8 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.8 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix th
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
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.8 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.8 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix th
tests ran: 32, failed: 32;
http://kernel.ubuntu.com/testing/4.4.0-30.49/s2lp6g002__4.4.0-30.49__2016-08-09_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.
https://bugs.launchpad.net/bugs/160
tests ran: 10, failed: 2;
http://kernel.ubuntu.com/testing/4.4.0-30.49/kernel02__4.4.0-30.49__2016-08-09_16-25-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/16099
tests ran: 19, failed: 17;
http://kernel.ubuntu.com/testing/4.4.0-30.49/s2lp6g002__4.4.0-30.49__2016-08-09_16-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.
https://bugs.launchpad.net/bugs/160
tests ran: 10, failed: 1;
http://kernel.ubuntu.com/testing/4.6.0-10.12/dwalin__4.6.0-10.12__2016-08-09_16-34-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/1609913
tests ran: 1, failed: 1;
http://kernel.ubuntu.com/testing/4.4.0-30.49/s2lp6g002__4.4.0-30.49__2016-08-09_16-53-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/1609
@faulpeltz, so it sounds like we can confirm the latest commit to pass
in 3.13.0-34 is 95d1181?
If that is the case, it might be worthwhile for me to build a test
kernel with d215f91 as tip of the tree and a second kernel with 71425a9
as the tip. Just let me know if you could test those two addit
Yes, you can remove the mainline kernel with dpkg --purge
--
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/1611277
Title:
Kernel Shipped With Ubuntu 16.04.1 Cannot Recognize fakeRaid
Stat
1 - 100 of 175 matches
Mail list logo
