Bug 119831

for ubuntu 16.04 default kernel, you need acpi=off to boot, right?
what about 4.6 kernel? what about 4.7-rc2 kernel? does the same workaround work?

Please remove "quiet splash" boot options, and reboot without acpi=off, what can you see in the screen? can you get the kernel log when the system hangs during boot?

Hi,
Yes, since my install (for install from a liveCD, I need it too in boot options).
I put my daily kern.log without "acpi=off quiet splash" with 4.6 kernel.
I try with the lastest in few hours.
Thanks

Created attachment 220781 [details]
kern.log from 4.6 kernel

This is kern.log from 4.6 kernel without "acpi=off quiet splash" options.

(In reply to Sam from comment #3)
> Created attachment 220781 [details]
> kern.log from 4.6 kernel
> 
> This is kern.log from 4.6 kernel without "acpi=off quiet splash" options.

hmmm, I guess the kernel freezes at 44s when the nouveau debug trace log occurs, right?
can you please check if the kernel can boot with nouveau built out?

Created attachment 220911 [details]
kern.log from 4.7-rc4 kernel

Hi,
This is my kern.log from the latest kernel (4.7 rc4) without "acpi=off quiet splash" options.
Without "acpi=off" option, boot freezes at gdm start.

Thanks

what if you add boot option "nomodeset"?
what if you built nouveau driver out and boot into text mode?

Created attachment 221071 [details]
kern.log from 4.7-rc4 kernel with nomodeset

Hi,
I boot with only "nomodeset" option (so with "nomodeset" and without "acpi=off quiet splash" options) and my touchpad works (and I have my battery infos).
But, in my GUI (Gnome-shell), I haven't effects for all menus/windows transitions : ie, when I click on a menu, I have like a grey screen and, then, my normal screen with the menu (not easy to explain).
For the others tests (build nouveau driver and boot in text mode), if you can explain me how to do that (for the nouveau driver, I try, but it doesn't work ; I think this driver problem comes from acpi).

Thanks

Re,

My effect problem isn't just for menus or windows transition, it's for all animation, including video (like a 15fps video). So, it's a problem with my video card (I use only Intel HD for the moment).
I'll make some new tests.
Thanks

This seems to be a graphics issue to me.
Reassign to the graphics expert.

[   14.841410] nouveau 0000:01:00.0: DRM: evicting buffers...
[   14.841411] nouveau 0000:01:00.0: DRM: waiting for kernel channels to go idle...
[   14.841425] nouveau 0000:01:00.0: DRM: suspending client object trees...
[   14.844180] nouveau 0000:01:00.0: DRM: suspending kernel object tree...
[   16.953255] pci_raw_set_power_state: 36 callbacks suppressed
[   16.953262] nouveau 0000:01:00.0: Refused to change power state, currently in D3
[   17.028340] nouveau 0000:01:00.0: Refused to change power state, currently in D3
[   17.044404] nouveau 0000:01:00.0: Refused to change power state, currently in D3
[   17.044421] nouveau 0000:01:00.0: DRM: resuming kernel object tree...
[   17.044479] nouveau 0000:01:00.0: pci: failed to adjust cap speed
[   17.044496] nouveau 0000:01:00.0: pci: failed to adjust lnkctl speed

Created attachment 222951 [details]
kern.log from 4.7-rc7 kernel no-option and nomodeset option

Hi,
I try latest kernel (4.7-rc7) and :
- in a normal boot, I have again my problems
- with nomodeset option, all seem to work normaly (I have my battery state, touchpad works fine, Fn + keys work, ...).

So, this new kernel version is better for my problems if I put nomodeset option.

Thanks

Hello,

You could use `nouveau.runpm=0` on the kernel command line to prevent the NVIDIA card from auto-suspending, that should "get rid" of the fail to resume error.

FYI, with nomodeset you are disabling both GPU drivers. This is mostly responsible for the lost of effects in your DE, as your DE could prefer to not use effects if there is no 3D hardware acceleration available. If you want to try disabling only Nouveau, use `nouveau.modeset=0` on the kernel command line.

Could you attach the Xorg.log from a run without `acpi=off` and `nomodeset` please? When you say that boot freezes when gdm starts, I guess switching to a tty does not work, nor pressing the power button of your laptop, or trying to connect over SSH from another computer?

Created attachment 222991 [details]
kern.log + Xorg.log from 4.7-rc7 kernel with nouveau.runpm=0

Re,
I post kern.log and Xorg.log with nouveau.runpm=0 option in boot.
This new option is better again than nomodeset option :
- I have my luminosity option and Fn shortcut for luminosity works great
- my touchpad sensivity is very great to work (with nomodeset option, I need to overwrite sensivity parameters).

When I boot without option (without nomodeset and acpi=off), my boot freezes and I can't open a ssh connection or tty. So, I haven't log to show you because they are overwrited with the next boot (if you can explain me how to make more log to Xorg, I can do it).
Thanks

Eh sorry, completely forgot that you answered.

So, you usually have a Xorg.0.log and a Xorg.0.log.old, with the former one being the log for the current session, and the latter one, of the previous session.
If you use systemd, you can get the previous kernel log using `journalctl -b -1`.

By the way, you should remove the xf86-video-nouveau driver as it does not support your chipset. X will, and already does, fallback to the modesetting driver.

It might be related to https://bugs.freedesktop.org/show_bug.cgi?id=94725. Could you try if that patch https://bugs.freedesktop.org/attachment.cgi?id=122653 helps?

The lockup issue was reported for a similar model (MSI GE62 6QE) in Bug 156341. To workaround that issue on that specific machine, he had to boot with:

 acpi_osi=! acpi_osi="Windows 2009"

Sam, can you upload the tarball (with acpidump and others) according to
https://bugs.launchpad.net/lpbugreporter/+bug/752542?