@Christopher M. Penalver:
The newest kernel 4.9-rc5-generic gives a kernel panic at boot.
"stack guard page was hit at ..."
What to do now?
--
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/
** Summary changed:
- Need a patched 4.9 kernel to compile nvidia drivers
+ [ 4.9 ] Greeter loop with a nvidia driver
** Description changed:
- As the unstable kernel ppa now has 4.9 kernel, i've installed it on a
- system using a nvidia-370/375 driver, but both fails at compile dkms
- time.
-
Public bug reported:
I noticed a forever-looping test of linuxinfo on i386 this morning. This
test upgrades the kernel to 4.9 in -proposed; as soon as that reboots,
the VM never comes back. nova console-log shows:
[1.581188] Freeing unused kernel memory: 996K (dcc37000 - dcd3)
[1.5825
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1642192
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
** Changed in: hwe-next
Status: New => Triaged
--
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/1642114
Title:
ThinkPad T460 hotkeys stop working in Ubuntu 16.04
Status in HWE Next
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
** 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/1642192
Title:
i386 4.9 in -proposed fails to boot in cloud instances
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from
Hi
I've worked out I had a problem with micro usb cable. Ive replaced the cables
and it is working fine now. sorry about all the trouble. Thanks Koli
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.
Hi, all resolved, it was due to a faulty micro usb cable. Sorry about all the
trouble and thanks.
Koli
--
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/1641075
Title:
connected my android
DimanNe
See https://workingninja.com/installing-asus-bt400-raspberry-pi-raspbian-wheezy
It will show how to get the firmware needed for the broadcom bluetooth device
and see if the issue still exists after the firmware install
--
You received this bug notification because you are a member of Ker
You have been subscribed to a public bug:
== Comment: #0 - Breno Henrique Leitao - 2016-10-20
08:51:24 ==
Hello Canonical,
There are important kernel modules that are required on POWER systems,
and they are currently on the linux-image-extra packages.
So, in this case, every Power system needs
Got the same problem with Logitech RX250 on Xubuntu 16.04.01
--
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/1581088
Title:
Middle mouse (wheel-click) button stopped working after upgrad
Public bug reported:
== Comment: #0 - Breno Henrique Leitao - 2016-10-20
08:51:24 ==
Hello Canonical,
There are important kernel modules that are required on POWER systems,
and they are currently on the linux-image-extra packages.
So, in this case, every Power system needs to install the -extr
Thats kernel 4.4.07.68
--
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/1581088
Title:
Middle mouse (wheel-click) button stopped working after upgrade to
16.04
Status in linux package i
@acarbura yes it does
--
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/1566302
Title:
Ubuntu 16.04: Suspend freezes the system after upgrade to linux image
4.4.0-16
Status in linux pack
Hi Joseph
The problem happens both during install, and during a regular boot (for
example if I enable iommu post install and then reboot).
Happy to try new kernel versions for testing.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linu
OK tried with:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc5/
still see the same issue with intel_iommu=on; booted fine prior to
enabling.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
I've installed latest mainline build and awaits the issue... I have
definitely seen the issue with the 4.9-rc4 mainline build, but the rc5
just yet... I'll be back with an update in a few days.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
(I also tried a firmware upgrade for the storage controller to the
latest version - no luck).
** Tags added: kernel-bug-exists-upstream-4.9-rc5
--
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
@penalvch I guess better times are around the corner "Cypress just
bought Broadcom's wifi business and published all their datasheets
https://news.ycombinator.com/item?id=12965348";
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Also in my case I solved it by disabling WMM, not sure how to solve this
for this ticket... Since it's really environment related.
--
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/1575321
Ti
You have been subscribed to a public bug:
Support ST Micro lps22hb pressure sensor and lng2dm 3-axis femto
accelerometer sensor in Ubuntu kernel
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Shrirang Bagul (shrirang-bagul)
Status: New
--
ST Micro lps22hb pressure
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Changed in: linux (Ubuntu)
Assignee: Taco Screen team (taco-screen-team) => Canonical Kernel Team
(canonical-kernel-team)
--
You received this bug notification b
Public bug reported:
Support ST Micro lps22hb pressure sensor and lng2dm 3-axis femto
accelerometer sensor in Ubuntu kernel
This bug is used for tracking purposes, please do not triage.
** Affects: linux (Ubuntu)
Importance: Critical
Assignee: Shrirang Bagul (shrirang-bagul)
S
issue does not occur anymore for xenial (Ubuntu-4.4.0-49.70)
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
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
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Eric Desrochers (slashd)
--
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/1640786
Title:
netfilter regression introducing a per
** Tags added: originate-from-1636730 plano
** Changed in: hwe-next
Status: New => In Progress
** Changed in: hwe-next
Importance: Undecided => Critical
** Changed in: hwe-next
Assignee: (unassigned) => Shrirang Bagul (shrirang-bagul)
--
You received this bug notification becaus
After upgrade to 16.10, this problem is back but the freezes do not
occur as frequently as they did in 16.04 before my '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/1536721
Title:
You have been subscribed to a public bug:
Kernel crashes running large amounts of deployment using Ibmvscsis driver.
Contact Information = Bryant Ly/b...@us.ibm.com
Stack trace output:
[ 1780.861532] Faulting instruction address: 0xc0583de0
[ 1780.861542] Oops: Kernel access of bad
Default Comment by Bridge
** Attachment added: "ibmvscsis: Issues from Dan Carpenter/Smatch"
https://bugs.launchpad.net/bugs/1642299/+attachment/4778205/+files/0006-ibmvscsis-Issues-from-Dan-Carpenter-Smatch.patch
** Changed in: ubuntu
Assignee: (unassigned) => Taco Screen team (taco-scr
I've run the updated kernel in -proposed through the kernel team zfs
test suite and I observed no regressions. Marking it as verified.
** Tags removed: verification-needed-yakkety
** Tags added: verification-done-yakkety
--
You received this bug notification because you are a member of Kernel
Pa
I'm adding the kernel to this, as I'm fairly certain the kernel is
responsible for what modules are built into the default initramfs'.
In this case it looks like cdc_ether and usbnet need to be added into
the initramfs in order to solve a case like this.
I'm not sure if this should be done in the
Hello, I had the same problem, but I could solved my case:
Gigabyte Notebook with hybrid Intel + Nvidia GTX 765M card with PRIME not
working with (K)Ubuntu 16.04 with any version of the proprietary NVIDIA driver.
When prime-select switched to nvidia gives a black screen, set to intel worked.
NVi
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1639202
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
** Tags removed: verification-needed-trusty
** Tags added: verification-done-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/1636625
Title:
Syntax error extra parenthesis linux-hea
Tested against upstream fwts that utilizes this in-kernel driver module
and it works successfully. Marking as verified.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Tags removed: verification-needed-yakkety
** Tags added: 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/1637473
Title:
cleanup primary tree for linux-hwe lay
** Tags removed: verification-needed-yakkety
** Tags added: 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/1637303
Title:
Move some device drivers build from ke
** Tags removed: verification-needed-yakkety
** Tags added: verification-done-yakkety
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
htt
looks OK for yakkety in -proposed too.
** Tags removed: verification-needed-yakkety
** Tags added: 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/1636517
Title:
Hi, Just wondered if anyone was looking at the above. My Meizu MX4 is
now on OTA-13 and although the car can see the phone and identifies it
as an MX4 it will not pair with the phone. I can understand that it may
not be possible to use the high end feature of the Jaguar blue-tooth
connection but I
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Changed in: linux (Ubuntu)
Assignee: Taco Screen team (taco-screen-team) => Canonical Kernel Team
(canonical-kernel-team)
--
You received this bug notification bec
Public bug reported:
I have a Lenovo Thinkpad X250 and I was running 16.04 and regularly
using a Panasonic PT-FIV430 FW430 WXGA projector with no issues. Once I
upgraded to 16.10 the operating system no longer detects the projector
through VGA (or if I use a mini-display adapter to connect to the
Kernel 4.8 just make 16.04 proposed repository. Does it happen on Ubuntu
16.04 with kernel 4.8?
--
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/1616107
Title:
Kernel oops + system freeze
Default Comment by Bridge
** Tags added: architecture-ppc64le bugnameltc-148746 severity-high
targetmilestone-inin---
** Attachment added: "sosreport from the iaos1 host."
https://bugs.launchpad.net/bugs/1616107/+attachment/4778262/+files/sosreport-iaos1-20161115131621.tar.xz
--
You receive
--- Comment From ru...@us.ibm.com 2016-11-16 13:27 EDT---
Reversed mirrored as we can still replicate this with 4.4.0-47. I'll give the
proposed 4.8 kernel a try later today.
Regardless of whether the bnx2x vlan filter init error is resolved, it
seems that the nbp_vlan_flush() routine ne
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/1642356
Title:
Ubuntu 16.10 no longer connect
Default Comment by Bridge
** Attachment added: "sosreport from the iaos1 host."
https://bugs.launchpad.net/bugs/1616107/+attachment/4778284/+files/sosreport-iaos1-20161115131621.tar.xz
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to l
--- Comment From cdead...@us.ibm.com 2016-11-16 13:36 EDT---
cde00 (cdead...@us.ibm.com) added native attachment
/tmp/AIXOS06682471/JournalErrors.txt on 2016-11-16 12:33:12
cde00 (cdead...@us.ibm.com) added native attachment
/tmp/AIXOS06682471/shutdown-problem-power8 on 2016-11-16 12:33:1
Default Comment by Bridge
** Attachment added: "shutdown-problem-power8"
https://bugs.launchpad.net/bugs/1616107/+attachment/4778285/+files/shutdown-problem-power8
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https
Public bug reported:
Modules under the drivers/staging hierarchy get little attention when it
comes to vulnerabilities. It is possible that memory mapping tricks that
expose kernel internals would go unnoticed. Therefore, do not sign
staging modules so that they cannot be loaded in a secure boot
e
The kernel in #57 did not include the patches, but the kernel in comment
#59 is current mainline and it DOES have the patches.
I noticed the comment does not have the download link. It is:
http://kernel.ubuntu.com/~jsalisbury/lp1626436/mailine-with-two-commits/
I just wanted to confirm the mainl
1 - 100 of 203 matches
Mail list logo