Journal of errors can be seen is this bug #1656489 for the same
installation. Sorry for sending info from the non-sudoer account.
--
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
Ti
** Description changed:
The following log comes from the installer syslog file. Since at least
- Dec.16th a message is present in all variants of Ubuntu on startup.
- Since then, in BIOS mode, all installers have opened in try Ubuntu.
+ Dec.16th a message is present in all variants of Ubuntu on
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1656489/+attachment/4804160/+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
Journal from admin account.
--
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/1656489
Title:
AMD A10 [Firmware Bug]: APIC id mismatch / All Variants
Zesty/Ubiquity
Status in linux packa
apport information
** Description changed:
The following log comes from the installer syslog file. Since at least
Dec.16th a message is present in all variants of Ubuntu on startup.
Since then, in BIOS mode, all installers have opened in try Ubuntu.
There is no incidence on the instal
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1656489/+attachment/4804158/+files/ProcEnviron.txt
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which
Public bug reported:
The following log comes from the installer syslog file. Since at least
Dec.16th a message is present in all variants of Ubuntu on startup.
Since then, in BIOS mode, all installers have opened in try Ubuntu.
There is no incidence on the installation except for xubuntu. In th
[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
[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
[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
** 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.
https://bugs.launchpad.net/bugs/1635447
Title:
Upgraded or Live USB 16.10 hangs at boot up blank purple screen
Status in linux packag
@Joseph, I've installed v4.10-rc3 via Ukuu and my laptop boots up
successfully.
~$ uname -a
Linux chengdu 4.10.0-041000rc3-generic #201701081831 SMP Sun Jan 8 23:33:02 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
Everything seems work normal, even though I noticed some message about
b43, but the WIFI
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-60.81-lowlatency/onza__4.4.0-60.81__2017-01-14_03-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/bug
The bug is also present in bios mode alongside rs1. CKT 4.10.0-1.3 stalls on
first restart and magic key works to restart again. As in UEFI mode the HDD is
noisy, too noisy to keep it on board. Grub was OK for this test.
That ends this bug report. Thanks!
--
You received this bug notificati
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1655123/+attachment/4804138/+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/1655123
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1655123/+attachment/4804131/+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: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1655123/+attachment/4804136/+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: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1655123/+attachment/4804134/+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: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1655123/+attachment/4804135/+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: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1655123/+attachment/4804130/+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: "CRDA.txt"
https://bugs.launchpad.net/bugs/1655123/+attachment/4804129/+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
Ti
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1655123/+attachment/4804137/+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: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1655123/+attachment/4804132/+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: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1655123/+attachment/4804133/+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
** 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 boot
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-60.81-lowlatency/onza__4.4.0-60.81__2017-01-14_02-52-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/bug
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-60.81-generic/onza__4.4.0-60.81__2017-01-14_02-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/1
I've tested this with kernel 4.10-rc3 in a local VirtualBox VM (Ubuntu
Server 16.04), with the same fstab error as above, and am able to
confirm most of the symptoms described by the reporter.
When attempting to 'mount -a', it presents the expected "wrong
filesystem type" error, but doesn't render
Looking at the file Christopher linked to earlier states this:
"Organization: Intel Open Source Technology Center
The Baytrail SOC has a built-in feature to demote core
and module C6 to shallower idle states.
Based on work in the Android copy of the Linux kernel tree,
this feature was disabled s
Christopher, the latest kernels don't freeze as much as the older ones.
Do you want me to go back to an older kernel that froze up a lot to test
the intel_idle.max_cstate=1 ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to the bug report.
Okay i have just removed Vincent's patched kernel. I will try and
proceed and test Christopher's request to follow his steps to test his
stuff.
Vincent i will add that your patch seemed to work well, though i did
have it lock up once. Only once that i can remember though.
--
You received this bu
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-60.81-generic/onza__4.4.0-60.81__2017-01-14_01-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.
https://bugs.launchpad.net/bugs/1
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-60.81-generic/ms10-35-mcdivittB0-kernel__4.4.0-60.81__2017-01-14_01-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
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-60.81-generic/modoc__4.4.0-60.81__2017-01-14_02-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/
I also tried to enable hibernation, same issue with NVME drives using
hibernation as when using suspend. Skylake truly is a mess on Linux :/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-59.80-generic/kernel01__4.4.0-59.80__2017-01-14_01-36-00/results-index.html
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-59.80-generic/s2lp3__4.4.0-59.80__2017-01-14_01-36-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/
As I suspected, issue is still present with the 4.10 kernels. Tried it
on a separate clean install using 16.10 upgrading the kernel to
v4.10-rc3 mainline
This warning is present for 4.10 as well as for older kernels on the Alienware
15 R2
update-initramfs: Generating /boot/initrd.img-4.10.0-04100
** 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)
--
You received this bug notification because you are a membe
Christopher, *-rc versions are the release Candidates, once I installed
it (http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc5) to check the
same bug (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641152)
in November and ended up without WiFi. I can't work on *-rc.
The bug reproduced a
** Description changed:
Ubuntu 16.10 on a Alienware 15 R2 when resuming from suspend the NVME
- devices and the network devices area gone.
+ devices and network devices are gone.
I can force the devices to re-appear issuing echo 1 >
/sys/bus/pci/rescan, that was what I did to be able to s
(New kernel is still compiling...)
I just did a test with a fully-patched, newly spun-up Ubuntu Server
14.04 AWS instance, and the behavior seems to be present with kernel
3.13.0-107. I can't verify all of the symptoms described by the
reporter, because I don't have physical access; but I get "co
Artem V L, the latest mainline kernel is presently 4.10-rc3 (not 4.9.x).
Despite this, regarding your hardware specifically, how often would it
be reproducible on average when using the Ubuntu kernel (ex. linux-
image-generic 4.4.0.53)?
--
You received this bug notification because you are a mem
The linux-image-3.13.0-031300 kernel boots fine, Joseph.
--
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/1649326
Title:
EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.1
** 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)
** Description changed:
This bug is for track
Thanks for your attention on this bug, Joseph. I'm compiling the new
kernel, now, and will let you know as soon as I have a test result.
As far as I know, all 16.04 kernel versions exhibit this problem; but I
haven't done any testing on Ubuntu 15.X.
--
You received this bug notification because
I think we know almost the entire story now. See LP: #1656391
The one piece still missing is what changed. Very clearly the armhf
container tests passed for several months, and then stopped working. My
best guess is that they switched from using privileged containers to
unprivileged containers.
Christopher, I've installed the latest mainline kernel
(4.9.3-040903-generic #201701120631) and performed quick stress testing.
At the moment everything works fine, but as me and nico mentioned, this
bug is not always reproducable even on the kernels where it definitely
exists. I will work on this
nico (nicolas-pourcelot), it will help immensely if you filed a new report with
Ubuntu, using the default repository kernel (not mainline/upstream/3rd party)
via a terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
For more on why this is helpful, please see
https://wiki.ubuntu.
https://lists.ubuntu.com/archives/kernel-team/2017-January/081840.html
** Changed in: linux (Ubuntu Yakkety)
Status: New => In Progress
** Changed in: linux (Ubuntu Yakkety)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Also affects: linux (Ubuntu Zesty)
Importance: High
https://lists.ubuntu.com/archives/kernel-team/2017-January/081830.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) => Tim
Can you test v3.13 final:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-trusty/
If it fails, we can "Reverse" bisect between v3.13 and v3.14-rc1. If
v3.13 final boots fine, then that would indicate an Ubuntu specific
SAUCE patch causing the bug.
--
You received this bug notification becau
This v4.10-rc3 kernel is now available. Can you give that version a test:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc3
Also, was there a prior kernel version that did not exhibit this bug? If so,
we can perform a kernel bisect to find the offending commit.
** Changed in: linux (Ub
Guillaume, roots, Stéphane, can you also test with my PPA kernel from
comment 30? It would help to know if your NVMe failures are also due to
the patches we're reverting, or some other problem.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** 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)
--
You received this bug notification because you are a membe
It appears these workaround patches introduced NVMe initialization
problems on some non-Xen systems, see bug 1626894. I sent patches to
revert this for xenial and yakkety. Instead, this problem should be
fixed by a patch to Xen kernel code, in bug 1656831.
** Changed in: linux (Ubuntu)
St
I work for a major educational system that utilizes Ubuntu Server
(14.04, 16.04 LTS) instances on the Amazon Web Services cloud for
critical infrastructure. This bug has come up a few times, where an
admin has a typo or other error in /etc/fstab, pertaining to a non-OS
filesystem (like an EFS data
linux-image-3.14.0-031400rc1-generic also boots fine.
--
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/1649326
Title:
EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13
Can you next test v3.14-rc1:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-rc1-trusty/
--
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/1649326
Title:
EFI stub loader broken in kern
LP: #1656391
And it's reproducible in an amd64 container run locally. So probably
some change in the images or lxc. Maybe a new missing dependency?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.
linux-image-3.14.0-031400-generic also boots fine.
--
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/1649326
Title:
EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13
se
Ok scratch comment #13, must have been half asleep when I read comment
#12 , is there a status change I need to make for Trusty to move this
along? Thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launc
Thanks for testing! Can you next test 3.14 final:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-trusty/
--
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/1649326
Title:
EFI stub loa
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
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
Can you see if this is also happening with the latest Zesty kernel? All
the packages are available from:
https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/ppa/+build/11837051
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to li
Dear Sir,
please , do not send me Bug reports : It is impossible for me to
unsuscribe (bug) so I write to you. I thank you.
On 13/01/2017 19:33, Joseph Salisbury wrote:
> ** Changed in: linux (Ubuntu)
> Status: Incomplete => Fix Released
>
--
You received this bug notification because
** Changed in: linux (Ubuntu Zesty)
Status: Incomplete => Won't Fix
--
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/1648449
Title:
NVMe drives in Amazon AWS instance fail to initia
Dear Sir,
please , do not send me Bug reports : It is impossible for me to
unsuscribe (bug) so I write to you. I thank you.
On 13/01/2017 18:56, Mic Gotschall wrote:
> Public bug reported:
>
> Installed Ubuntu on my laptop, and replaced the old Operating System
> (Windows 10). The touchpad was
** Changed in: linux (Ubuntu)
Status: Triaged => Incomplete
--
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/1649584
Title:
Kernel update 3.13.0-105 causes SATA errors that end up r
Public bug reported:
[Impact]
This bug fixes the root problem reported in bug 1648449, so its
description can be mostly reused here:
On an Amazon AWS instance that has NVMe drives, the NVMe drives fail to
initialize, and so aren't usable by the system. If one of the NVMe
drives contains the root
** 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.net/bugs/1655437
Title:
16.04 fails to boot with kernel 4.4.0-22-generic
St
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
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
The bisect reported commit 50f208e18014589971583a8495987194724d56e4 as
the first bad commit. I built a Xenial test kernel with this commit
reverted. It can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1650336/
Can you test this kernel and see if it resolves this bug?
Note, you n
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/1656372
Title:
HP touchpad does not detected
Public bug reported:
Installed Ubuntu on my laptop, and replaced the old Operating System
(Windows 10). The touchpad was working fine on Windows, and when I plug
in a mouse via USB it works as well. When I used the command "cat
/proc/bus/input/devices" a touchpad does not come up at all. I've been
@thornyon, why did you marked this bug as fix released? As far as I can
see, linux-firmware still doesn't ship kbl_dmc_ver1.bin.
I'd like to benefit from lower power usage that should come with this
firmware.
--
You received this bug notification because you are a member of Kernel
Packages, whic
--- Comment From cls...@us.ibm.com 2017-01-13 11:51 EDT---
Thanks Gavin for working in this set of patches.
Here are the upstream commits for this issue:
>From f40ec3c748c6912f6266c56a7f7992de61b255ed Mon Sep 17 00:00:00 2001
From: Gavin Shan
Date: Wed, 26 Oct 2016 12:15:35 +1100
Subject:
The linux-image-3.16.0-031600-generic kernel boots fine.
--
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/1649326
Title:
EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.1
Abalan, you're subscribed to the "linux in Ubuntu" package, which is why
you're receiving bug reports:
https://bugs.launchpad.net/~fyma/+packagebugs
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
Abalan, you have also subscribed to the package "Linux in Ubuntu" as
shown here:
https://bugs.launchpad.net/~fyma/+packagebugs
Because of this, you will receive bug notifications for EVERY bug filed
against "Linux". YOu will need to unsubscribe from this package if you
do not wish to receive th
Can you also test the latest upstream 4.4 kernel? This will tell us if
the fix in 4.10-rc3 was already cc'd to stable. It can be downloaded
from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.42/
--
You received this bug notification because you are a member of Kernel
Packages, which is s
*** This bug is a duplicate of bug 1655041 ***
https://bugs.launchpad.net/bugs/1655041
** Tags removed: architecture-ppc64 targetmilestone-inin---
** Tags added: architecture-ppc64le targetmilestone-inin14042
--
You received this bug notification because you are a member of Kernel
Packages,
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?
--
You
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
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/1653843
Title:
Bluetooth 04ca:3018 not working correctly
Status in linux
I replayed the bisect results and it looks like the following commit
also needs to be tested:
[92923ca3aacef63c92dc297a75ad0c6dfe4eab37] mm: meminit: only set page
reserved in the memblock region
Were you able to also test this commit?
--
You received this bug notification because you are a mem
Hello Joseph, do you need me to test just kernel-image and headers? or
all debs in that dir, thanks for clarification.
-Andrew
--
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
Abalan, Please view the bug page and at the top on the Right Hand side,
you should see a box that says the following, or something similar:
You have subscriptions that may cause you to receive notifications, but you are
not directly subscribed to this bug's notifications.
Mute bug mailMute h
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => High
--
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/1654708
Title:
Trying to reinstall ZFS on Xenial. Cannot mount exist
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => High
--
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/1642096
Title:
zfs-dkms 0.6.5.6-0ubuntu14: zfs kernel module failed
Can you see if the latest 4.4 upstream kernel also fixes this bug? That
will tell us if the fix in mainline was already cc'd to stable. It can
be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.42/
--
You received this bug notification because you are a member of Kernel
Pac
Can you also give the latest upstream 4.8 kernel a test? That will tell
us if the fix in 4.10-rc2 was also cc'd to stable. It can be downloaded
from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8.17/
--
You received this bug notification because you are a member of Kernel
Packages, which
** Changed in: linux (Ubuntu Xenial)
Assignee: Kamal Mostafa (kamalmostafa) => Dan Streetman (ddstreet)
** Changed in: linux (Ubuntu Yakkety)
Assignee: (unassigned) => Dan Streetman (ddstreet)
--
You received this bug notification because you are a member of Kernel
Packages, which is s
@jsalisbury, Thank you for the suggestions. I don't have the xenial
kernel handy as I have the habit of running apt-get autoremove after
upgrades. However, I will try the latest upstream kernel over this
weekend and report the results.
--
You received this bug notification because you are a membe
Thanks for the update. That means we should start testing prior to 4.4.
Can you test 3.16 final:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16-utopic/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
** Tags removed: 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/1418339
Title:
kernel set the wrong max_sectors_kb for 4K disks(sd.c)
Status in linux package in Ubuntu:
Do we happen to know what commits(Other than 69973b8308) are in 4.9 and
newer that are also needed in 4.8?
Do you want me to build a Yakkety test kernel with commit 69973b8308?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubun
** Tags removed: kernel-da-key needs-reverse-bisect
--
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/1554613
Title:
Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU)
Statu
Yeah, ddstreet's -59 kernel boots just fine and sees my NVMe drives.
Let me know if I can help.
--
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/1626894
Title:
nvme drive probe failure
St
Joseph, please note the following from the original bug report:
I have NOT encountered the problem with Xenial and its 4.4.0-series
kernels (last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series
kernels (last tested: 4.8.0-30-generic). I have not yet tested Trusty
with kernels from series
Are you able to test various kernels? If so, it might be good to test
the mainline kernel to see if the bug is already fixed in mainline. It
is available from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc3
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Also affect
1 - 100 of 135 matches
Mail list logo
