Dell XPS-15 with GTX 1050 user reporting in, for me just deleting xorg.conf and
rebooting worked (using nvidia-390).
I had upgraded from 17.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053
T
As reported upstream, when I used the drm-tip kernel I didn't see the FIFO
error message in the logs again (but still had random power downs).
I'm running the mainline kernel 4.15.0-041500rc8-generic and also don't see any
of the described issues anymore (although I still have 1-2 random shutdown
So I was just able to reproduce the shut-down issue with the kernel
4.14.0-041400rc8-generic and the debugging flags enabled.
I submitted a kern.log to the upstream bug report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
1) Currently trying to reproduce
2) I know, I'm trying to reproduce the issue with "drm.debug=0x1e
log_buf_len=1M" added right now, and will add the information later
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Some updates:
* I cross posted the issue to the freedesktop bugtracker here:
https://bugs.freedesktop.org/show_bug.cgi?id=103643
* I got my docking station firmware updated, it is now at 2.33.00.
Unfortunately I was not able to determine what the previous version was
* I'm running with the curren
Ok, I'll install the drm-tip kernel from http://kernel.ubuntu.com
/~kernel-ppa/mainline/drm-tip/current/ , try to reproduce it there, and
report it to Intel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
1) It's a lenovo ThinkPad Ultra Dock Type 40A2 20V
I didn't know docking stations had firmwares up until now. Is there a way to
find out via Ubuntu? Otherwise I have to talk to my company helpdesk about it.
2) Ok, will report it there. Do I have to try with another kernel again? Since
the /drm-in
Today I installed 4.14.0-041400rc8-generic
I had a crash again, this time the computer did not power down but I came back
to a completely frozen lock screen (only visible on the main monitor, not the
secondary screens), so I had to hard reboot.
I'll attach kern.log and syslog
** Attachment adde
Syslog from todays crash with 4.14.0-041400rc8-generic
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/+attachment/5005424/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Regarding your other questions:
1) The issues have not happened without locking so far. Everything works
smoothly when I don't lock (so that's why my workaround is to not lock the
screen when I'm only away for short, although it's against company policies...)
2) When docked in the docking station
So if I got you right, additionally you want me to install the latest
mainline 4.14-rc8, reproduce the bug there and then attach kern.log and
syslog here?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
The kern.log
** Attachment added: "kern.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/+attachment/5004796/+files/kern.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727662
So I used the kernel at drm-intel-nightly/current/
It ran fine the whole day, but now I saw again that the notebook was shut down
after locking the screen and coming back after half an hour.
But I'm not sure if it's the same bug, since I don't see any of the error
messages previously reported in
1) I forgot to mention that I removed "i915.enable_rc6=0" after I tried the
first mainline kernel. So everything after that was already with RC6 enabled.
2) I'll try to reproduce it with the latest mainline kernel on Monday and
attach the requested files.
4) I can't hear the fan and the temperat
Here the screen lock settings in English again.
** Attachment added: "screen-lock-settings.png"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/+attachment/5003089/+files/screen-lock-settings.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
Note that I usually lock the screen manually via the top right menu when
I leave the computer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727662
Title:
Crashes after unlock: [drm:intel_cpu_fifo_
Here a screenshot of the energy settings (switched language to english).
I'm not sure if there is any other setting where I could influence the
behaviour.
** Attachment added: "energy-settings.png"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/+attachment/5003088/+files/energy-s
Automatic locking is set to on after 3 minutes.
** Attachment added: "lockscreen.png"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/+attachment/5003087/+files/lockscreen.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Somebody else seems to have a similar problem:
https://bugzilla.redhat.com/show_bug.cgi?id=1506339
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727662
Title:
Crashes after unlock: [drm:intel_cpu_f
I updated my BIOS to the current version
~ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
JBET66WW (1.30 )
09/13/2017
It didn't fix the [Firmware Bug] lines in the syslog though
Also the actual bug still appears. There seem to be some lines in the log that
I haven't seen be
Oh, right now I'm running on the BIOS version
JBET51WW (1.16 )
07/08/2015
That's indeed a lot behind the current one. I'll try to update and report back.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
Tried it now with kernel 4.14.0-041400rc7-generic and it still appears.
(Notebook sits in dock, locked the screen, let it sit for 45 minutes,
came back to computer being shut down).
In /var/log/syslog I find
Nov 1 10:01:05 xxx kernel: [ 404.329288]
[drm:intel_cpu_fifo_underrun_irq_handler [i91
Hi
1) When using the current kernels 4.13.0-16-generic or 4.13.0-16-lowlatency it
is insofar reproducible, that it happens most of the time (I'd say more than
50%).
But not every time, that's why I'm not confident to say the bug is fixed after
one or two unlocks.
2) Yes, I think it only happens
So I tried to reproduce it with the kernel v4.14-rc6
(bb176f67090ca54869fc1262c913aa69d2ede070)
I tried to get that error for an hour with some lock/unlock, suspend and
hibernate cycles but it didn't appear.
Unfortunately I can't test it for a whole working day, since the internet is
not working
Another thing I found in /var/log/kern.log inbetween the FIFI underrun
messages is this:
Oct 26 09:32:02 ako-notebook kernel: [58379.446230] [ cut here
]
Oct 26 09:32:02 ako-notebook kernel: [58379.446267] WARNING: CPU: 2 PID: 2653
at /build/linux-XO_uEE/linux-4.13.0/driv
Ok, I reported a new bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1695989
Title:
i915 *ERROR* CPU pipe A FIFO underrun - graphic gl
One thing that I tried was disabling RC6 in grub, but that didn't seem to help:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_rc6=0"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727662
Title:
Public bug reported:
I upgraded from Ubtuntu 17.04 to Ubuntu 17.10 and this bug started appearing
(didn't have this with the versions before).
When I lock my screen on my Lenovo T450s and the notebook sits in the dock (two
external screens attached), one of the three things happen when I come ba
I upgraded to Ubuntu 17.10 and this bug started appearing (didn't have this
with the versions before).
When I lock my screen on my Lenovo T450s and the notebook sits in the dock, one
of the three things happen when I come back after some time and try to unlock:
* Most of the time the computer was
*** This bug is a duplicate of bug 1373639 ***
https://bugs.launchpad.net/bugs/1373639
The linked bug doesn't exist...
https://bugs.launchpad.net/bugs/1373639
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Here as well, fresh install of 14.04 on a Dell Latitude notebook (Intel
graphics) with the internal screen and two external screens being in use.
Happens randomly as it seems.
Only one time I didn't get password field but at least the cogwheel icon on the
top right, so I could select "switch use
No, it's not specific to laptops.
I have this issue only on my desktop PC (using a Microsoft Explorer mouse).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1238410
Title:
Inconsistent cursor visibil
I'm also affected by this #969489 which I solved by always restarting lightdm
in my /etc/rc.local
But still I get a Xorg crashreport after starting once in a while, so maybe
those two bugs are also related?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 751605 ***
https://bugs.launchpad.net/bugs/751605
I can confirm that this bug occurs to me since yesterday. It only
affects Firefox, all other Applications behave as intended. So I'm not
sure that it's really a duplicate of bug 751605.
--
You received this
34 matches
Mail list logo
