*** This bug is a duplicate of bug 1814555 ***
https://bugs.launchpad.net/bugs/1814555
When I booted Kubuntu, the hard drive light flashed a few times, but
otherwise nothing happened; just a black screen. Had to push the
hardware restart button to get going again. Next boot I selected
*** This bug is a duplicate of bug 1814555 ***
https://bugs.launchpad.net/bugs/1814555
@P.D. This issue will now be tracked under Bug #1814555
Under that bug, a test kernel was provided with the problematic fix
removed (comment #8), and that seems to have positive testing results.
Feel free
*** This bug is a duplicate of bug 1814555 ***
https://bugs.launchpad.net/bugs/1814555
** This bug has been marked a duplicate of bug 1814555
Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot)
--
You received this bug notification because you are a member of Kernel
Packages,
I just stumbled across Bug #1814555
That looks like the exact same problem (i915 driver causing the boot to
fail). They even identified the same source commit.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I looked up the "325f8e18c8ac drm/i915/ringbuffer: Delay after
EMIT_INVALIDATE for gen4/gen5" commit and it looks like the Tails distro
had the same issue with that commit
https://redmine.tails.boum.org/code/issues/16224
--
You received this bug notification because you are a member of Kernel
@kmously I can confirm that that kernel does NOT fix my problem, aka the
system does not boot up with that kernel.
--
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/1813657
Title:
@P.D. That's surprising. In that case, it means the offending commit is
"325f8e18c8ac drm/i915/ringbuffer: Delay after EMIT_INVALIDATE for
gen4/gen5". I was expecting the offending commit to be "d8370b8fbadf
drm/i915/execlists: Force write serialisation into context image vs
execution" because
@kmously Unfortunately, the eighth kernel 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/1813657
Title:
4.18.0-14 doesn't boot past grub
Status in linux package in
I'll test the 8th one when it becomes available.
--
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/1813657
Title:
4.18.0-14 doesn't boot past grub
Status in linux package in Ubuntu:
@kmously The seventh kernel doesn't boot up.
--
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/1813657
Title:
4.18.0-14 doesn't boot past grub
Status in linux package in Ubuntu:
@P.D.: I also have the eighth (and final) kernel almost ready for you.
It is based on commit:
325f8e18c8ac drm/i915/ringbuffer: Delay after EMIT_INVALIDATE for
gen4/gen5
and it should be available at:
https://kernel.ubuntu.com/~kmously/1813657/kernel-kmously-325f8e1-2dRL
in about 40 minutes.
@P.D. Thanks for the feedback.
I have the seventh kernel for you based on commit:
d8370b8fbadf drm/i915/execlists: Force write serialisation into context
image vs execution
You can download the test kernel from:
https://kernel.ubuntu.com/~kmously/1813657/kernel-kmously-d8370b8-MWga/
Please
@kmously The sixth kernel boots up 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/1813657
Title:
4.18.0-14 doesn't boot past grub
Status in linux package in Ubuntu:
Confirmed
@P.D. Thanks for the feedback.
I have the sixth kernel for you based on commit:
1ab407cbd9c3 (tag: sixth-bisect) drm/i915: Mark pin flags as u64
You can download the test kernel from:
https://kernel.ubuntu.com/~kmously/1813657/kernel-kmously-1ab407c-XRVe/
Please let me know if this kernel
@Jan Schnackenberg: Thanks for that feedback and helpful and analysis.
The Spectre-related change looked suspicious at first. However, if that
was indeed the cause of your issue, then it's almost certainly a
different issue than the one described in this bug report and
experienced by @P.D., since
@P.D. Thanks for the feedback.
I have the fifth kernel for you based on commit:
ce68bab41c06 drm/i915: Fix ilk+ watermarks when disabling pipes
You can download the test kernel from:
https://kernel.ubuntu.com/~kmously/1813657/kernel-kmously-ce68bab-GzyB/
Please let me know if this kernel
@kmously The fifth kernel boots up 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/1813657
Title:
4.18.0-14 doesn't boot past grub
Status in linux package in Ubuntu:
Confirmed
@kmously The fourth kernel 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/1813657
Title:
4.18.0-14 doesn't boot past grub
Status in linux package in Ubuntu:
Confirmed
@Khaled El Mously: I could try your kernels tomorrow (I hope). Can you
please tell me which packages I'd need to install? That's quite a list
of files there. ;)
I'm currently guessing the packages with these "base-names":
linux-headers-4.18.0-14
linux-headers-4.18.0-14-generic
Uhm... Sorry for that, I seem to have triggered some keyboard shortcut.
To continue:
1. Additional line in 4.18.0-14
Line 355: [0.034459] Spectre V2 : Spectre v2 cross-process SMT mitigation:
Enabling STIBP
2. Additional line in 4.18.0-14
Line 590: [0.124079] pci :00:02.0: BIOS left
** Attachment added: "dmesg output for failing kernel 4.18.0-14"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813657/+attachment/5236564/+files/dmesg_4.18.0-14.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Attachment added: "dmesg output for working kernel 4.18.0-13"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813657/+attachment/5236563/+files/dmesg_4.18.0-13.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
I'm currently seeing this issue on my fathers computer.
After starting 4.18.0-14 the screen goes blank and nothing seems to
happen anymore. Booting wiht 4.18.0-13 works without issues.
I noticed, that after some time I can SSH into the machine. So I dumped
dmesg with 4.18.0-14 and 4.18.0-13.
@Martin Barlow: It's hard to say if it's the same issue or not. One way
we can find out would be if you test the same kernels that I'm building
for @P.D. to try to bisect this issue. If your problem is caused by the
same commit that is causing @P.D.'s problem, then it's likely the same
issue. And
@P.D. OK, now I have the fourth kernel for you based on commit:
aa4fa5c8c67b net: hns3: Remove tx budget to clean more TX descriptors in
a napi
You can download the test kernel from:
https://kernel.ubuntu.com/~kmously/1813657/kernel-kmously-aa4fa5c-Yud2/
Please let me know if this kernel
I believe i have same issue from 4.18.0-13 to 4.18.0-14 on lenovo T410.
on boot last thing i see is
"Loading initial ramdisk ..."
On subsequent boot on different kernel from syslog i can see an OOPS and
stack trace. Attaching. Let me know if i can assist or if its separate
issue.
** Attachment
@P.D. Sorry, please disregard the last message. (I used the wrong commit
to build that kernel).
I will update shortly with a new kernel to test.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@P.D. Great, thanks for the feedback.
I have the fourth kernel for you based on commit:
b5970159440d ARM: 8809/1: proc-v7: fix Thumb annotation of
cpu_v7_hvc_switch_mm
You can download the test kernel from:
https://kernel.ubuntu.com/~kmously/1813657/kernel-kmously-b597015-sFIG/
Please let me
@kmously That kernel boots up fine, and you were right about the video
driver problem, it was solved by installing the modules-extra package.
(Atleast for that kernel)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@P.D. Thanks for the info.
I have the third kernel for you based on commit:
94785f13e73c efi/arm/libstub: Pack FDT after populating it
You can download the test kernel from:
https://kernel.ubuntu.com/~kmously/1813657/kernel-kmously-94785f1-kUm4/
Please let me know if this kernel shows the
@kmously That kernel does not boot up.
--
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/1813657
Title:
4.18.0-14 doesn't boot past grub
Status in linux package in Ubuntu:
Confirmed
@P.D. Thanks for the info.
We're only concerned with the boot issue here. The video driver problem
could be due to a missing module that needs to be installed (e.g. from
linux-modules-extra ) or a dkms driver.
I have the second test kernel for you based on commit
5a7784d6a34f scsi: hisi_sas:
@kmously That kernel you provided booted up but it doesn't seem like the
intel video drivers worked in that kernel (everything was low
resolution, and my desktop environment cinnamon ran in software
rendering mode). I only installed these packages though:
@edwintorok: I don't know if it's certain that the issue you're seeing
is necessarily the same issue described in the bug report, but feel free
to test the same kernels as well and report your result. If you see
different results from P.D. then we can continue the investigation of
the second
@P.D. Thanks for following up.
There are 869 commits between 4.18.0-13 and 4.18.0-14, so it should take
up to 10 attempts to bisect the issue.
I have the first test kernel for you based on commit
40208c782496 9p locks: fix glock.client_id leak in do_lock
You can download the test kernel from:
Feb 4 15:22:03 mama-tata-laptop kernel: [1.81]
[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO
underrun
Feb 4 15:22:03 mama-tata-laptop kernel: [1.822564] [drm] RC6 disabled,
disabling runtime PM support
Feb 4 15:22:03 mama-tata-laptop kernel: [
I tried to file a bug, but launchpad keeps timing out (see
https://bugs.launchpad.net/ubuntu/+bug/1814585).
I think I have the same problem on Ubuntu 18.10.
4.18.0-13 was fine, 4.18.0-14 always crashes with BUG on boot.
--
You received this bug notification because you are a member of Kernel
>From older, working kernels. Note that the FIFO underrun error is
present in these successful boots too (I've been seeing it for years),
but it never crashes before on that.
** Attachment added: "good kern.log"
Attached is dmesg after booting the faulty kernel in recovery mode.
** Attachment added: "dmesg.4.18.0-14-generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813657/+attachment/5234586/+files/dmesg.4.18.0-14-generic
--
You received this bug notification because you are a member
Can you provide a new dmesg output from 4.18 kernel since you discovered
you are able to boot on recovery mode? Just dump it somewhere so you can
recover it once booted graphically with another kernel.
Basically once you are in front of the recovery screen, select the
option to enable network,
5.0-rc4 mainline kernel boots up fine.
** 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/1813657
Title:
4.18.0-14 doesn't boot past grub
Status in
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.0-rc4 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
Recovery mode does boot with the problematic kernel, so I can drop into
a root shell. Regular mode doesn't work.
--
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/1813657
Title:
4.18.0-14
Nevermind, it does say "loading ramdisk", it just gets stuck doing it. I
have a video of the problem if you want.
--
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/1813657
Title:
4.18.0-14
Ok, I'll install 4.18.0-13 again.
When I mean "it doesn't boot past grub", I mean when I hit enter to boot
from the grub screen, it stays on the grub screen, so I see just my grub
background forever, and I see my disk activity light blinking a bit. I
don't think it even said it was loading the
@P.D.: OK, I recommend switching to 4.18.0-13, since we'll be assuming
that it's our last "good" kernel and we'll try to narrow down what's the
issue between 4.18.0-13 and 4.18.0-14.
When you say "doesn't boot past grub" - what exactly do you see after
grub? Just a blank screen? Any kernel logs
@kmously I reverted back to 4.15 because I don't know of anything in
4.18 that would benefit me over 4.15, but I'm willing to test custom
kernels because I want this to be fixed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
@P.D.: Thanks for the bug report.
If 4.18.0-13 worked fine, why did you need to revert to a 4.15 kernel?
Would you be able to test some custom kernels that I provide you so we
can try to narrow down the change that caused this? It should take 1-10
bisections to find out.
Thanks
--
You
apport information
** Tags added: apport-collected tessa
** Description changed:
4.18.0-14 doesn't boot past grub for me in thinkpad t510i. 4.18.0-13
worked fine. I had to revert back to 4.15 kernel. I'm using a distro
that is based off of Ubuntu 18.04.
System info:
CPU:
49 matches
Mail list logo
