Big is still there:
[1.456717] [ cut here ]
[1.456719] Could not determine valid watermarks for inherited state
[1.456767] WARNING: CPU: 2 PID: 176 at
/build/linux-hwe-jW5mjG/linux-hwe-4.15.0/drivers/gpu/drm/i915/intel_display.c:14537
intel_modeset_init+0x1011
This is quite late, but to let everyone know: later releases of 4.8
screwed up everything again. Lockups after user switching. Falled back
to the 4.4 branch, where
[87274.633194] [ cut here ]
[87274.633227] WARNING: CPU: 3 PID: 22315 at
/build/linux-dKXp7o/linux-4.4.0/driv
I would have been working on that but for now have no time at all and,
honestly, too little motivation. 4.8 kernel works like a charm.
--
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/1583817
Here are relevant links:
https://bugzilla.redhat.com/show_bug.cgi?id=1372924
https://lkml.org/lkml/2016/8/29/105
** Bug watch added: Red Hat Bugzilla #1372924
https://bugzilla.redhat.com/show_bug.cgi?id=1372924
--
You received this bug notification because you are a member of Kernel
Packages
Well, I have tested:
ilya@thinkpad:~$ uname -a
Linux thinkpad 4.8.0-040800rc4-generic #201608312129 SMP Thu Sep 1 01:31:59 UTC
2016 x86_64 x86_64 x86_64 GNU/Linux
Installation was smooth except the complaints about missing firmware---I
dismissed these warnings. A new kernel hang after the very
Remind me, how to do that?
--
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/1583817
Title:
WARNING: CPU: 1 PID: 865 at
/home/kernel/COD/linux/drivers/gpu/drm/drm_irq.c:1326
drm_wait_on
Bug is still there with the most recent update:
ilya@thinkpad:~$ uname -a
Linux thinkpad 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:01:55 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
It can be triggered by VT switching *after* some time the system is up.
Below is the piece of dmesg log:
[175890.5
The problem is *not* fixed by other updates at the time of writing the
post---the fully updated system (16.04.1@thinkpad x220) has the same
issue.
It is invariably happening when the "Switch user" capability is
employed, in other words when a second instance of Xord is in use. The
laptop actually
Sorry for being grumpy, but something has be done with kernel quality
assurance. 4.4 kernel apparently has multiple issues---in my case I have
troubles on both 16.04 & 14.04 Ubuntus. They are:
1. blank virtual consoles after some time on 14.04.5@Asus Zenbook UX301 CA
2. Random Xorg lockups on 1
9 matches
Mail list logo