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 1844021
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Public bug reported:
Since upgrading the kernel above 4.4.0-154, starting with 4.4.0-157,
suspend does not work for me anymore. Never had such an issue in the
last 6 years.
This is the relevant output when suspend fails:
[ 328.25] PM: Suspending system (mem)
[ 328.288902] Suspending console
As of kernel 62 the bug seems to have disappeared. This is great.
I love my 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/1841446
Title:
[Kernel] [loop] [xubuntu] [18.04] Bug
I've built a test kernel that provides a new package linux-tools-
dev-. This is probably not what you ultimately want but would
that help in any way?
To install it:
$ sudo add-apt-repository ppa:juergh/kernel
$ sudo apt install linux-tools-dev-5.0.0-29
$ dpkg -L linux-tools-dev-5.0.0-29
/.
/usr
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
** Changed in: linux (Ubuntu)
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/1842726
Title:
Random freezes on 4.15.0-60
Status in linux package
(In reply to txrx from comment #651)
> I was able to update my BIOS to version 18, but my system still locks up.
> I tried the following with the new BIOS:
> - use factory defaults
> - disable SMT
> - disable SMT with Typical Current Idle
> - all of the above with SVM disabled/enabled
> Right n
I was able to update my BIOS to version 18, but my system still locks up.
I tried the following with the new BIOS:
- use factory defaults
- disable SMT
- disable SMT with Typical Current Idle
- all of the above with SVM disabled/enabled
Right now I set the power supply idle control to "Low ..."
** Changed in: linux
Status: Confirmed => 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/1840236
Title:
Horizontal corrupted line at top of screen caused by framebuffer
Yes, basically whatever turns off fbc would work. Thank you.
--
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/1840236
Title:
Horizontal corrupted line at top of screen caused by framebuffe
Reporter, please also try as suggested using i915.enable_fbc=0 if issue
still exists.
--
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/1840236
Title:
Horizontal corrupted line at top of sc
marking this as dup. WIP on that has been already a while to understand
cause of it.
*** This bug has been marked as a duplicate of bug 103167 ***
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
Ah, so suggested workaround using i915.enable_fbc=0 also works?
--
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/1840236
Title:
Horizontal corrupted line at top of screen caused by framebu
Likely identical, especially if disabling fbc from command line works.
--
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/1840236
Title:
Horizontal corrupted line at top of screen caused by
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubunt
Public bug reported:
just tried to change the driver on Ubuntu 19.10
ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: libnvidia-compute-390 390.129-0ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
Uname: Linux 5.3.0-10-generic x86_64
NonfreeKernelModules: nvidia_uvm nv
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
My team has encountered this as well and it affects both our on-premise Linux
as well as Azure VMs kernels. Last versions which were working for us are:
- In azure case 5.0.0-1016-azure
- In case of on-premise 5.0.0-25-generic
After upgrading to 5.0.0.-1018-azure and 5.0.0-28, respectively, both s
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
@apolitech please do not hijack this bug for a completely unrelated
problem. If you believe yours is legit kernel issue then raise a new
ticket at https://bugs.launchpad.net/ubuntu/+source/linux/+filebug.
--
You received this bug notification because you are a member of Kernel
Packages, which is
23 matches
Mail list logo
