Hopefully future kernel releases don't need the nouveau.modeset=0
option. But until then, 17.10 is rock solid (been full time on it for
the past 3+ weeks) without issues. Kudos to the Ubuntu and Canonical
teams for doing such a great job.
On Fri, Oct 20, 2017 at 7:15 AM, Hagen Kuehn
This is a re-write of my previous response, as I should have reviewed it
before submitting. I have simply been too excited! ;-)
@Kai-Heng Feng and @Anmar Queja
I have upgraded to Ubuntu 17.10 and used the suggested nouveau.modeset=0
kernel boot option.
It works perfectly. I can indeed see many
@Kai-Heng Feng and @Anmar Queja
I have upgraded to Ubuntu 17.10 and used the suggested nouveau.modeset=0 kernel
boot option.
It works perfectly. I can indeed see many improvement. Most and foremost
Wayland is working as far as I can see!
The only hiccup I had was with the laptop suspending
Hi Anmar & Kai-Heng,
this issue affects 16.04 LTS too, and right now the only workaround is to run
the good old 4.8 (and skip all the 4.10 upgrades).
When do you think 4.13 will be ported in 16.04? Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which
I agree with Kai-Heng. 17.04 is getting old and given all the good
work that went into the 17.10 release, I recommend you switch to it
Hagen.
BTW, in 17.10, there is a problem on the XPS 15
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718936) booting
from live CD and general use. You
Hagen,
That means there are some kernel commits that prevent kernel from booting.
Unless you want to do a bisect in the current bisection, otherwise I would
suggest move to 4.13 based Artful (17.10) kernel. The Artful release is
imminent.
--
You received this bug notification because you are
I have tested with provided kernel at
http://people.canonical.com/~khfeng/lp1697556/3/
The test setup was the same as previously.
Short answer: It does not work.
Long answer: I can see the icon circling for a while. While this happens
I cannot toggle between the boot text output and the
Again, try this:
http://people.canonical.com/~khfeng/lp1697556/3/
$ git bisect log
git bisect start 'drivers/gpu/drm/nouveau'
# old: [a351e9b9fc24e982ec2f0e76379a49826036da12] Linux 4.11
git bisect old a351e9b9fc24e982ec2f0e76379a49826036da12
# new: [2ea659a9ef488125eb46da6eb571de5eae5c43f6]
I have tested with kernel 4.10.0-lp1697556
http://people.canonical.com/~khfeng/lp1697556/2/ with the default kernel
parameters and with the same hardware setup as previously.
Short answer: It works.
Long answer: The login screen is displayed on built in monitor, while
the laptop is closed. The
$ git bisect log
git bisect start 'drivers/gpu/drm/nouveau'
# old: [a351e9b9fc24e982ec2f0e76379a49826036da12] Linux 4.11
git bisect old a351e9b9fc24e982ec2f0e76379a49826036da12
# new: [2ea659a9ef488125eb46da6eb571de5eae5c43f6] Linux 4.12-rc1
git bisect new 2ea659a9ef488125eb46da6eb571de5eae5c43f6
I have tested with kernel 4.11.0-rc1-lp1697556 with the default kernel
with the same hardware setup as previously.
Short answer: It works.
Long answer: The login screen is displayed on built in monitor, while
the laptop is closed. The login works. Network issues but they are not
relevant to this
To find the patch that fixes the issue, we need to bisect the kernel. Here's
the first one:
http://people.canonical.com/~khfeng/lp1697556/1/
Please check if this freeze or not.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Your question:
"so what's the result on v4.12-rc1, without "nomodeset"?"
Short answer: It does not freeze.
Detailed answer:
With v4.12-rc1, by using the default kernel arguments (i.e. without
"nomodeset"), it does not freeze. It shows the login screen on the closed
laptop, which you pointed
** Attachment added: "Kernel 4.12-rc1 log using default kernel argument"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/+attachment/4957550/+files/kernel.log.4.12-rc1WithDefaultKernelArguments.log
--
You received this bug notification because you are a member of Kernel
Sorry to ask again - so what's the result on v4.12-rc1, without
"nomodeset"?
--
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/1697556
Title:
Computer freezes after login -
** Attachment added: "Kernel 4.11.12 log when using blacklist nouveau arguments"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/+attachment/4957292/+files/kernel.log.4.11.12.blacklist.nouveau.log
--
You received this bug notification because you are a member of Kernel
Packages,
** Attachment added: "Kernel 4.11.12 log using default kernel arguments"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/+attachment/4957290/+files/kernel.log.4.11.12.WithDefaultKernelArguments.log
--
You received this bug notification because you are a member of Kernel
** Attachment added: "Kernel 4.11.12 log using nomodeset argument"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/+attachment/4957291/+files/kernel.log.4.11.12.nomodeset.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
@Kai-Heng
In answer to your question "Can you confirm v4.11 freezes but v4.12-rc1
doesn't?", I can confirm that 4.11.12 freezes. Kernel log shows "NMI
watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [kworker/3:1:70]".
Below are the test details along with the corresponding kernel log
output.
Let's focus on the freeze (nouveau) first. We can solve the docking
output (i915) later.
Can you confirm v4.11 freezes but v4.12-rc1 doesn't?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@Kai-Heng
Concerning your question:
v4.12-rc1 with NOMODESET -> Successfully logged in.
v4.12-rc2 with NOMODESET -> Successfully logged in.
v4.12-rc5 without NOMODESET-> Successfully logged in.
Can I say that -rc2 has freeze but -rc5 doesn't freeze?
I would say that neither of those two kernels
There are two separate issues:
1. The original issue, freeze. Your test result:
v4.12-rc1 with NOMODESET -> Successfully logged in.
v4.12-rc2 with NOMODESET -> Successfully logged in.
v4.12-rc5 without NOMODESET-> Successfully logged in.
Can I say that -rc2 has freeze but -rc5 doesn't freeze?
2.
@Kai-Heng
Here are the test results when starting the kernel with "blacklist=nouveau
modprobe.blacklist=nouveau".
The Dell XPS 9560 is connected to Dell Thunderbolt Dock TB16 with the external
monitor and the external keyboard being connected to the docking station.
Short answer:
v4.12-rc1 ->
@Hagen,
Can you test it by only blacklisting nouveau? i915 should still be loaded.
You can do that by adding "blacklist=nouveau modprobe.blacklist=nouveau" to
your kernel parameter.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
With disk encryption enabled is more of an issue, because the Nvidia
drivers need something on the encrypted partition and thus fails to
boot.
The only kernel I have successfully booted after 4.8 was 4.13. I am
currently running 4.13 with disk encryption, Nvidia drivers from the PPA
and the
@Hagen Kuehn
When I try to add nomodeset on the 4.10.0-35-generic kernel, my laptop freezes
on the disk encryption screen. I tried it with a usb3 dock and hdmi monitor
attached and without any peripherals.
--
You received this bug notification because you are a member of Kernel
Packages, which
@Kai-Heng Feng (kaihengfeng)
Based on your suggestion I have tested with the below mainline kernels as well
as the current 17.04 kernel.
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc1/
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc2/
Correct me if I am wrong: 4.11 is bad but 4.12-rc5 works.
So, can you try 4.12-rc1, 4.12-rc2?
4.12-rc3 and 4.12-rc4 don't have any changes to nouveau so you can skip them.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@Hagen Kuehn (hag-k)
Thanks for your suggestions, I will pay more attention next time I will
add a comment.
I just want to say that after I changed the bug status to "Fix Released" I
could not change back to "Confirmed" because all the status was grayed and
disabled. So I added my comment
@dani_bs(sdaniele78)
I trust you commented and changed the state of the bug with good intent.
Please accept my apology for being so direct... it was a complete fail.
Both links referenced do not provide any solution. One link mentions to
alter the "acpi_osi kernel parameters" without details
Back to 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/1697556
Title:
Computer freezes after login - 4.10.0-22-generic
Status in linux package in Ubuntu:
Confirmed
Bug
** Changed in: linux (Ubuntu)
Status: Fix Released => 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/1697556
Title:
Computer freezes after login - 4.10.0-22-generic
Sorry, I involuntarily changed the state to "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/1697556
Title:
Computer freezes after login - 4.10.0-22-generic
Status in
I think is the same problem of kernel 4.10 described here:
-
https://askubuntu.com/questions/941211/ubuntu-16-04-freezes-with-4-10-kernel-and-nouveau-driver
- https://askubuntu.com/questions/939417/ubuntu-16-04-freezes-with-4-10-kernel
Kernel 4.8 works good.
** Changed in: linux (Ubuntu)
I just checked the the 17.10 live images on my XPS 15 (9560) and the
kernel still doesn't boot without using "nomodeset" kernel boot arg.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I have reviewed the kernel source code that was committed between the
Ubuntu-4.10.0-21.23 and Ubuntu-4.10.0-22.24 and I believe commit
b93843fcde501b9264ac5dbe2c980eb0b479 introduced bug #1697556.
Commit b93843fcde501b9264ac5dbe2c980eb0b479 corresponds to
For reference; 4.13.0-041300-generic also BOOTS fine on my machine which
fails with 4.9, 4.10 and 4.11.
I didn't try 4.12 but Hagen says it works fine. Hopefully we can figure
out where the fix is so it can be back-ported to stable kernels.
--
You received this bug notification because you are
John: Sorry, I forgot to mention, I installed the drivers from the
"Additional Drivers" menu (I run Gnome), and also from "the" PPA.
--
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/1697556
John: I tried 4.10.0-33-generic, I tried 32-generic, and several
versions before. I'm running the latest firmware from Dell, 1.3.4 I
believe, and had something older before that.
Almost every time I boot with nvidia installed it freezes at the FDE
prompt, and I can't enter my password. If I don't
Same issue here.
Dell XPS 15 9560, Ubuntu 16.04 (with the latest software updates), using
Nouveau driver and the latest firmware available from Dell.
With kernel 4.10.0-33, the computer freezes after I enter the password of the
login screen.
With kernel 4.8.0-58 the computer works well.
--
You
Well, I'm running 4.10.0-33-generic, and although sometimes I have to
login twice, and it has frozen on a couple of occasions, it's pretty
much okay. So I'm not sure what exactly is different about my combo than
yours, except maybe the firmware version I'm running on the 9560.
--
You received
When you had the nvidia drivers installed, can you confirm how you
installed them?
--
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/1697556
Title:
Computer freezes after login -
I have the same issue on my Dell XPS 9560. It has been running fine in
"intel" graphics mode up until and including kernel 4.8. With 4.10 and
4.11 it either freezes pre-boot, before I even reach the FDE password
prompt, or, if I uninstall the nvidia drivers, it freezes at some point
after.
Can confirm this issue on my Dell XPS 9560. I downloaded iso of ubuntu
16.04 made it bootable and i tried to boot into installation menu but i
got stuck on loading screen, before it showed up error with noveau and
cant create kernel channel, 22. Any fix please.
--
You received this bug
Well, I'm using 4.10.0.28 and nvidia-381 on my XPS 15 9560 and I'm able
to login.
I did update to the latest BIOS version too though (1.34), so maybe that
had an effect, IDK.
It did complain about a plymouthd crash, and I got it to send a report,
so don't know if that will help.
In line with comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/comments/11,
the workarounds suggested with
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/comments/9
do not work with kernel 4.10.0-28 either. The computer freezes just
before the login screen appears.
I have tested the suggested workarounds that were given with comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/comments/9
in conjunction with kernel 4.10.0-24. Those two workarounds basically
suggest not to use the nouveau driver but instead the Nvidia drivers.
Those
Same here, with Dell XPS 15 (ngg9x) too
--
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/1697556
Title:
Computer freezes after login - 4.10.0-22-generic
Status in linux package in
Can confirm on Dell XPS 15 with 4.10.0-26. This is also the same issue
as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1696665 and
another workaround is described here:
https://rileymacdonald.ca/2017/06/26/ubuntu-broken-boot-on-dell-xps-15
-after-kernel-update-upgrade/
--
You received
I'm confirming this issue on a DELL XPS 15 as well. It's still present
with 4.10.0.24.
My workaround is to bot 4.10.0.21
--
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/1697556
Title:
In answer to your question
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/comments/6
I have tested with Kernel 4.12.0, and DID NOT ENCOUNTER this problem.
linux-headers-4.12.0-041200rc5_4.12.0-041200rc5.201706112031_all.deb
Can you also see if this bug happens with the latest mainline kernel?
It can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc5
** Tags added: needs-bisect
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
In answer to your qeustion
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/comments/3
* Yes, the problem is NOT encountered when using Kernel linux-
image-4.10.0-21-generic 4.10.0-21.23.
* The problem is encountered when using 4.10.0-22-generic
In response to your request
** 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.
https://bugs.launchpad.net/bugs/1697556
Title:
Computer freezes after login - 4.10.0-22-generic
Status in linux package in
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.10 stable kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel
Does this issue go away if you boot with the prior kernel version?
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is
56 matches
Mail list logo
