Will do.
--
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/1718107
Title:
task-size-overrun test will hang on IBM s390x zKVM / zVM
Status in Ubuntu on IBM z Systems:
Confirmed
Status in
> one bug at a time, please.
Absolutely! I just mentioned the "GRO implementation" because I wondered
if it might have been related. I should have googled up better on it
beforehand, that would have enlightened me that it wasn't.
I've tested the v4.4-wily kernel in the first link
(4.4.0-040400-ge
I have the same problem on 4.4.0-97 and 4.4.0-96 with a Nvidia GTX 1070.
I've tried nvidia drivers 374, 384, 387, but none allow me to boot
4.4.0-97.
The only solution is to uninstall nvidia-* and then I can boot 4.4.0-97.
--
You received this bug notification because you are a member of Kernel
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-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verificati
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-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verificati
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-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verificati
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 the problem still exists,
change the tag 'verifica
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-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verificati
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 the problem still exists,
change the tag 'verifica
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-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verificati
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 the problem still exists,
change the tag 'verifica
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 the problem still exists,
change the tag 'verifica
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 the problem still exists,
change the tag 'verifica
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-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verificati
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 the problem still exists,
change the tag 'verifica
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-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verificati
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 the problem still exists,
change the tag 'verifica
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 the problem still exists,
change the tag 'verifica
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 the problem still exists,
change the tag 'verifica
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-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verificati
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-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verificati
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-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verificati
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-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verificati
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 the problem still exists,
change the tag 'verifica
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 the problem still exists,
change the tag 'verifica
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-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verificati
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-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verificati
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-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verificati
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-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verificati
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-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verificati
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 the problem still exists,
change the tag 'verifica
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-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verificati
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 the problem still exists,
change the tag 'verifica
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => 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/1722335
Title:
linux: 3.13.0-134.183 -prop
** Changed in: kernel-sru-workflow
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1722335
Title:
linux: 3.13.0-134.183 -proposed tracker
Status in
> The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1721856
The _all package seems to be damaged/truncated. I'm getting `dpkg-deb:
error: unexpected end of file in archive member header in linux-
headers-4.12.0-041200_4.12.0-041200.201710171537_all.deb` and the
package
Public bug reported:
This bug is for tracking the 3.13.0-135.184 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-wor
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-trusty in Ubuntu.
https://bugs.launchpad.net/bugs/1722336
Title:
linux-lts-trusty
For the record since I forgot to comment previously: kernel in #21
(mainline kernel with suspicious patch reverted) does boot fine with
nouveau.
(However just reverting it will probably cause other regressions)
--
You received this bug notification because you are a member of Kernel
Packages, wh
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Description changed:
This bug is for tracking the 3.13.0-135.184 upload package. This bug
will contain status and testing results related to that upload.
For an explanation of the tasks and the associat
Public bug reported:
I have the feeling I reported this before but I can't find the original
issue. I'm experiencing freezes almost every time the screen is locked,
and sometimes even after the screen is off (but this happens much less
often).
I had this issue before, at some point it started to
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1724513
and then change the status of the bug to 'Confirmed'.
If, due to the nature
*** This bug is a duplicate of bug 1724500 ***
https://bugs.launchpad.net/bugs/1724500
** This bug has been marked a duplicate of bug 1724500
linux: 3.13.0-135.184 -proposed tracker
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to l
Reassigning to powertop package for a first look - I upgraded a PC
laptop to 17.10, and I am seeing two usb devices (camera and keyboard)
flagged as 100% busy and major consumers of power in powertop (whereas
they were not before the upgrade).
--
You received this bug notification because you are
** Changed in: kernel-sru-workflow
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-trusty in Ubuntu.
https://bugs.launchpad.net/bugs/1722336
Title:
linux-lts-trusty: 3.13.0-134.183~precise
Hey friend,
I've visited a nice place just lately, it really was cool! Take a look
http://www.gayfm.org/inc/contrib/simplepie/test/hear.php?UE80MDU1MjVAYnVncy5sYXVuY2hwYWQubmV0
Yours sincerely, Heinrich
-
>From time to time this website may also include links to other websites.
These links ar
> PIOTR from comment 6! You've got it working on 16.04!? Get at me, bro!
I downgraded linux-firmware to 1.157.8 and it's still working on 16.04
with the latest kernel (I use HWE). Any next version for Xenial causes
SYSASSERT when connecting to 5 GHz networks.
Here's the deb file of the version I
** Changed in: linux (Ubuntu Trusty)
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/1720867
Title:
Trusty NVMe boot fails on some systems
Sta
Tested with Gerald's patch. It can fix the task-size-overrun hang issue on
s390x.
Test report could be found here: http://pastebin.ubuntu.com/25765114/
I will check with powerpc later. Thanks
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty
--
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/1716491
Title:
New PMU fixes for marked events.
Status i
** 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) => Thadeu Lima de
Souza Cascardo (cascardo)
** Changed in: kernel-sru-workflow/prepare-packa
apport information
** Tags added: apport-collected xenial
** Description changed:
I have the feeling I reported this before but I can't find the original
issue. I'm experiencing freezes almost every time the screen is locked,
and sometimes even after the screen is off (but this happens muc
Bear in mind I've used the mainline kernel while getting the files via
apport, not the faulty one.
--
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/1724513
Title:
Freezes when screen is lo
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1724513/+attachment/4974771/+files/ProcEnviron.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: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1724513/+attachment/4974770/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
Public bug reported:
I'm unable to enter my password on the screen to unlock the disk during
boot using kernels 4.10.0-35 and 4.10.0-37. Using the 4.9.45-040945
mainline kernel seems to work fine.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bu
the failing test was added by bug 1385330
--
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/1723223
Title:
linux-lts and linux-hwe autopkgtests fail due to version mismatch
Status in linux
Public bug reported:
This bug is for tracking the 3.13.0-135.184~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
** Affects: kerne
Public bug reported:
This is on a Intel Compute Stick STK1AW32SC (Atom x5-Z830) using
elementaryos-0.4.1-20170814 (Xenial 16.04 LTS) and bcmwl-kernel-source
6.30.223.271+bdcom-0ubuntu1~1.1
The default kernel does not provice all required drivers to operate all
hardware. Currently installed is HWE
I have to correct my earlier statement (comment 14), the linux-firmware
package update didn't fix the problem after all - it seemed to work for
a while, but I was mistaken. Now, however, I've gotten it working. The
correct fix is to add the following line to the end of
/etc/modprobe.d/iwlwifi.conf
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Description changed:
This bug is for tracking the 3.13.0-135.184~precise1 upload package.
This bug will contain status and testing results related to that upload.
For an explanation of the tasks and the
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1724564
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Sounds like this is probably a problem in the graphics driver. When you
boot in recovery mode you're getting a reduced-functionality graphics
environment, which means that the logs that were attached don't show us
anything about what happens when you try to boot normally. Could you
attach the /var/
*** This bug is a duplicate of bug 1724562 ***
https://bugs.launchpad.net/bugs/1724562
** This bug has been marked a duplicate of bug 1724562
linux-lts-trusty: 3.13.0-135.184~precise1 -proposed tracker
--
You received this bug notification because you are a member of Kernel
Packages, whic
** 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) => Thadeu Lima de
Souza Cascardo (cascardo)
** Changed in: kernel-sru-workflow/prepare-packa
** Also affects: linux-lts-trusty (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: linux-lts-trusty (Ubuntu Precise)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-trus
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Trusty)
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.launchpa
** Tags removed: kernel-release-tracking-bug-live
--
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/1724162
Title:
linux: -proposed tracker
Status in Kernel SRU Workflow:
Invalid
Status
** Changed in: kernel-sru-workflow/snap-certification-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/snap-certification-testing
Assignee: Canonical Kernel Team (canonical-kernel-team) => Canonical
Hardware Certification (canonical-hw-cert)
--
You received this b
** Changed in: kernel-sru-workflow/snap-certification-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/snap-certification-testing
Assignee: Canonical Kernel Team (canonical-kernel-team) => Canonical
Hardware Certification (canonical-hw-cert)
** Changed in: kernel-s
** Changed in: kernel-sru-workflow/snap-release-to-edge
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1722299
Title:
linux: 4.4.0-98.121 -proposed tracker
Public bug reported:
An upstream commit added Intel cpu model/microcode checks to disable
TSC_DEADLINE due to cpu errata:
commit bd9240a18edfbfa72e957fc2ba831cf1f13ea073
Author: Peter Zijlstra
Date: Wed May 31 17:52:03 2017 +0200
x86/apic: Add TSC_DEADLINE quirk due to errata
That commi
Public bug reported:
[Environment]
Reproducible <= 4.12 that means all our supported series + HWE
(including edge).
Distributor ID: Ubuntu
Description:Ubuntu 16.04.3 LTS
Release:16.04
Codename: xenial
Linux 4.10.0-33-generic #37~16.04.1-Ubuntu SMP Fri Aug 11 14:07:24 UTC
2017
But it should run automatically, not manually...
On Wed, 18 Oct 2017 at 08:11 Matt Robinson <1723...@bugs.launchpad.net>
wrote:
> As per the last comment by Emanuele Cisbani (cisba), I re-installed
> 4.10.0-37 (the original source of video problems with synaptic.
>
> Then did: sudo apt install --
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** 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/1724564
Title:
Cannot enter password to unlo
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** 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/1724362
Title:
Not booting - 17.10 Beta 2
Status
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
Do you plan on submitting an SRU request to the kernel team mailing
list?
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Also affects: linux (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Stat
** Changed in: linux (Ubuntu)
Status: In Progress => Incomplete
** Changed in: linux (Ubuntu Zesty)
Status: In Progress => Incomplete
** Also affects: dkms (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
The only .deb package you need to install is:
linux-image-4.12.0-041200-generic_4.12.0-041200.201710171537_amd64.deb
--
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/1721856
Title:
Suspend
** Description changed:
This bug is for tracking the 3.13.0-135.184~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
A few days have passed but my installation still has issues. It didn't
occur in Debian 9 or Debian Testing but it does in Ubuntu 17.10 and
Ubuntu 17.04. Strange.
As a workaround I'll use my phone as an external wireless network
adapter (connected through USB) so I can at least
suspend/reboot/shutd
Hopefully it won't take long to 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/1723644
Title:
NetworkManager/wicd hang, might be driver issue
Status in linux package in Ubuntu:
Commit 2a8a98673c13 is in Xenial -proposed, kernel version:
Ubuntu-4.4.0-98.121. It looks like you tested with version
4.4.0-62-generic. Can you try testing with the -proposed Xenial kernel:
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed.
An
@jsalisbury,
Yes, I do plan to submit this as an SRU request to the kernel ML.
--
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/1724614
Title:
[KVM] Lower the default for halt_poll_ns to
Public bug reported:
This bug is for tracking the 4.13.0-1002.2 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
As this bug is about the use of noirqdistrib, this could affect other
targets besides multipath devices. So unmarking this as duplicate of the
multipath bug. Also, changing the title to indicate better what it is
about.
** This bug is no longer a duplicate of bug 1635597
Ubuntu16.10:talclp1: Kd
** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty
--
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/1698470
Title:
[Zesty][Yakkety] rtl8192e bug fixes
Statu
** Tags removed: verification-needed-xenial verification-needed-zesty
** Tags added: verification-done-xenial verification-done-zesty
--
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/1720359
** Changed in: makedumpfile (Ubuntu Xenial)
Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de
Souza Cascardo (cascardo)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.laun
--- Comment on attachment From maur...@br.ibm.com 2017-01-23 12:10
EDT---
This patch fixes the issue. The noirqdistrib is a necessary parameter for ppc64
platform as stated in kdump docs
https://www.kernel.org/doc//Documentation/kdump/kdump.txt
With this fix crash kernel uses the corre
Sorry, I missed Robie's comment yesterday. Upstream seems
inactive/dead. Nothing from Lennart on
https://bugs.freedesktop.org/buglist.cgi?product=libatasmart since 2011.
No commits to http://git.0pointer.net/libatasmart.git since 2012. I
didn't see any indication the development had been picked
Public bug reported:
Installed O.S. on Samsung NC10. Display worked O.K. in text mode so the
install went smoothly. When the system is rebooted, however, switching
to graphics mode results in the below described screen corruption:-
Left Hand Side 80% of screen black with a blue of white pixels a
** Description changed:
This bug is for tracking the 3.13.0-135.184 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 pr
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Description changed:
This bug is for tracking the 4.13.0-1002.2 upload package. This bug will
contain status and testing results related to that upload.
For an explanation of the tasks and the associate
Here is a photo of the problem.
** Attachment added: "Here is a photo of the problem."
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724639/+attachment/4975110/+files/Display-problem.JPG
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
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/1724639
Title:
Graphics problem - 80% of the
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.14 kernel[
Hi Seth,
Thanks for coming back to me on this issue.
And you are spot on I made the change to custom.conf you mentioned above
and it has booted straight up into Ubuntu looking normal again.
I have attached kern.log file... please excuse all the BTRFS errors in
there i'm having issues with a cor
I installed this kernel on my Ubuntu 17.10 Arful Awkward, but it does not seem
to work since kernel 4.10 is too old for my Lenovo Yoga 720-15.
(Link:
https://launchpad.net/ubuntu/zesty/amd64/linux-image-4.10.0-38-generic/4.10.0-38.42
)
Could you please publish a kernel 4.13 for artful, since i
1 - 100 of 181 matches
Mail list logo
