** Tags added: cscc
--
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/1751268
Title:
bionic desktop does not boot with external monitor attached -
[drm:ironlake_crtc_enable [i915]]
** Changed in: linux
Status: Incomplete => Won't 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/1751268
Title:
bionic desktop does not boot with external monitor attached -
Closing this issue as NOTOUTBUG.
--
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/1751268
Title:
bionic desktop does not boot with external monitor attached -
[drm:ironlake_crtc_enable
Alec, any updates here? Did you get any chance to bisect the results?
Priority is updated as the issue isn't in drmtip.
--
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/1751268
Title:
Bisecting is a manual process, since it's some option (or combination
thereof) enabled in Fedora's .config that's the problem rather than a
bad commit which git can help with.
You're right in that it's not drm-tip itself. In fact, while the
original weirdness manifested itself in drm, it also
drm-tip works, nothing in dmesg to indicate failure. Pretty much the
only way to get progress is to get a bisect result.
--
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/1751268
Title:
nuts. Going to 4.20.15-200.fc29.x86_64 failed again... and backing up
to 4.20.13-200 also failed. Tricked by a race condition into thinking
that that version actually worked? Bad interaction with some other
update applied since? Dunno.
drm-tip (now at 5.1-rc3) continues to work.
Fedora 29 is
Just accidentally booted into fedora's 4.20.13-200.fc29.x86_64 (have
been happily running the drm-tip)... and it worked!
Will try reading changelogs to get some clues.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Not sure if helpful, but I had similar issue - machine would not boot if
(only) using external monitors. My computer is a Dell Latitude 5590; it
had previously booted, upon power up, with the machine closed, thus
using only external monitors.
In order to diagnose, I started to roll back updates,
** Changed in: linux (Ubuntu)
Assignee: Joseph Salisbury (jsalisbury) => (unassigned)
** Changed in: linux (Ubuntu Bionic)
Assignee: Joseph Salisbury (jsalisbury) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Sorry for the long silence. Going has been slow: it takes a while to do
a tweak/test/reboot/hang cycle. Especially since the disk controller
gets munged upon the bug happening, even persisting across a power cycle
(!) about 50% of the time (I have no idea how such a thing is even
possible).
ok, all's not wine and roses. When exiting X, it goes into the same
style lockup as used to happen on boot. Which includes crashing so hard
that often times (but not all the time) the BIOS can't find the boot
disk after the next power cycle.
At least the bug moving further back in the chain
(In reply to Alec Habig from comment #36)
> ok, all's not wine and roses. When exiting X, it goes into the same style
> lockup as used to happen on boot. Which includes crashing so hard that
> often times (but not all the time) the BIOS can't find the boot disk after
> the next power cycle.
>
>
So since last week, kernel-4.18.7-100.fc27.x86_64 came out on the Fedora
updates repo. Tried it just now in the process of looking at the next
batch of options differences... and it didn't crash! And all the other
drivers I need on this laptop are enabled (which wasn't the case with
your drm-tip
I do: even with the current Fedora Kernel (4.17.19) and the latest
Lenovo BIOS (which got updated recently, presumably for spectre
mitigation). Just verified this when booting this morning (accidentally
chose the wrong kernel in grub).
I have made little progress on narrowing down which kernel
Alec, do you still have the boot failure?
--
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/1751268
Title:
bionic desktop does not boot with external monitor attached -
Launchpad has imported 33 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=105811.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
** Changed in: linux
Status: Confirmed => Incomplete
--
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/1751268
Title:
bionic desktop does not boot with external monitor attached -
** Changed in: linux
Status: Unknown => Confirmed
** Changed in: linux
Importance: Unknown => Medium
--
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/1751268
Title:
bionic
Similar Fedora F27 bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1557416
freedesktop.org bug:
https://bugs.freedesktop.org/show_bug.cgi?id=105811
** Bug watch added: Red Hat Bugzilla #1557416
https://bugzilla.redhat.com/show_bug.cgi?id=1557416
** Bug watch added: freedesktop.org
** Tags removed: kernel-key
** 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/1751268
Title:
bionic desktop does not boot with external monitor attached -
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Incomplete
--
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/1751268
Title:
bionic desktop does not boot with external
We can perform a kernel bisect to identify the commit that introduced
this regression. We first need to identify the last kernel that did not
have this bug and the first that did.
Can you next test the following kernels:
v4.14-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc1/
v4.14
4.13.0-32.35: Boot
4.15.0-10.11: Does not boot
4.16.0-041600rc3.201802261351: Does not boot
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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.16
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: artful
--
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/1751268
Title:
bionic
Public bug reported:
Ubuntu Desktop Bionic up to date
System doesn't boot with an external monitor attached.
There is this message in the journal (full journal attached for this
boot)
fbcon: inteldrmfb (fb0) is primary device
[drm:ironlake_crtc_enable [i915]] *ERROR* mode set failed: pipe A
27 matches
Mail list logo
