Indeed, it seems like the kernel linked above breaks dockerd.
dmesg with "general protection fault" and stacktrace. all docker
commands hang.
https://pastebin.ubuntu.com/p/VRbFSmPkPs/
:(
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Perfect, no need to change tags anymore.
Now that at least 2 persons verified the bug is fixed with the -proposed
kernel, the SRU process will follow its course now and the fixed linux
will land in the archives in due time: there is a mandatory 7 days wait
time, so it should hit the archives next
For all other subscribers to this bug, now is the time to help :)
Enable -proposed on affected systems:
$ echo "deb http://archive.ubuntu.com/ubuntu/ eoan-proposed main" >>
/etc/apt/source.list
Update apt sources:
$ apt update
Install the linux kernel (and friends) from -proposed:
$ sudo apt
I can confirm that the problem is fix in the -proposed kernel
(5.3.0-52-generic).
Marking verification-done.
** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Reverting the status of that bug to confirmed was a bit premature :)
My previous comment already mentions 5.3.0-51-generic not being fixed
(before it being marked fix commited).
>From IRC:
"we should get a eoan/linux kernel in -proposed at the latest by
tomorrow, when that happens an automated
For the record, this still happens with the latest Eoan kernel
(5.3.0-51-generic).
[ 68.285097] i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0
[ 68.286107] i915 :00:02.0: Resetting rcs0 for hang on rcs0
[ 76.301387] i915 :00:02.0: Resetting rcs0 for hang on rcs0
--
A bug has been filed upstream here:
https://bugs.freedesktop.org/show_bug.cgi?id=103351
** Bug watch added: freedesktop.org Bugzilla #103351
https://bugs.freedesktop.org/show_bug.cgi?id=103351
--
You received this bug notification because you are a member of Kernel
Packages, which is
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,
I just tested 4.15-rc5 and the problem still persists.
A (bit painful) workaround if you don't have a choice:
- Boot liveCD, enable "expert mode" (F6 at boot menu"
- Edit the boot line to have "blacklist=nouveau
modprobe.blacklist=nouveau" BOTH before AND after the "--" at the end of
the line.
Blacklisting nouveau allows a full boot (at a very low screen
resolution, obviously).
Kernel at #16 fails to boot.
--
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/1723619
Title:
Ubuntu
The kernel at #14 fails to boot.
--
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/1723619
Title:
Ubuntu Desktop ISO fails to boot with nouveau on a displayport
Status in Release Notes
As discussed on IRC kaihengfeng and I will sync up tomorrow and bissect
the problem together.
--
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/1723619
Title:
Ubuntu Desktop ISO fails to
Tested all mainline kernels I could find for 4.13-rc*:
- 4.13-rc1: DisplayPort setup boots. Login screen appears. Choosing the
default option (wayland) results in broken desktop
(https://photos.app.goo.gl/xisx9EgTKTFoLXmJ3). Choosing the xorg
fallback works perfectly.
- 4.13-rc2: DisplayPort
I've done further testing as you suggested. Here's a breakdown of my
findings:
I tested the following kernel versions on 4k + displayport (installed
from launchpad librarian, with their matching -extra package and an
"update-grub"):
- 4.12.0-12: Boots. System seems to crash after a few seconds
Switching the faulty system to using HDMI + 1080p succeeded. Updating
bug description.
** Summary changed:
- Ubuntu Desktop ISO fails to boot with nouveau
+ Ubuntu Desktop ISO fails to boot with nouveau on a displayport
** Description changed:
On the latest daily artful image (/current as of
Another machine (GTX950m on an integrated screen) boots as well.
>From my limited understanding of the error message in the screenshot -
perhaps the problem is that the screen is connected to displayport (the
GT 640 uses HDMI).
The failing system has a 4k screen connected to displayport.
--
The livecd boots fine on another machine of mine with a nvidia GT 640
(so, an older generation), fromt eh same daily and same image burn.
I am out of extra hardware to try this on.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
I cannot run apport-collect because the livecd doesn't boot :(
--
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/1723619
Title:
Ubuntu Desktop ISO fails to boot with nouveau
Status in
Public bug reported:
On the latest daily artful image (/current as of 2017-01-14), the
following occurs on a system with nVidia graphics (on my system, a
GTX970): https://photos.app.goo.gl/gLUva3Vgvtv0lAmj2
Steps to reproduce:
- Download latest daily image, check checksums, burn to USB
- Boot
Could somebody summarize that the instructions to get this working on
wily are? Thanks a lot
--
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/1383184
Title:
Atheros Qualcomm Killer N1525
20 matches
Mail list logo
