Control: tag -1 moreinfo On 30 May 2019 14:37:26 +0200 Bardot Jérôme <bardot.jerome@gmail.com> wrote: > Le 29/05/2019 à 21:14, Bernhard Übelacker a écrit : > > You might also want to look through "dmesg -T" output > > if there is anything related to nouveau in the given time. > > That might also be helpful for the maintainer. > I add the output for previous execution (there is 2 minutes between > falkon log and dmesg log because first time i didn’t had LC_ALL=C ) and > re add previous log for libdrm-nouveau This bug is quite old and it would be useful to know whether the issue still exists. I looked at your dmesg log and I'd recommend to update your BIOS and make sure you have the latest intel-microcode package installed. - BIOS A19 05/17/2016 You were running BIOS A19 (2016-05-27) and according to [1] there's now an A28 version from 2019-07-15. Once you've done that you can check the 'health' of your system with the following commands: - dmesg --level emerg,alert,crit - dmesg --level emerg,alert,crit,err - dmesg --level emerg,alert,crit,err,warn Doing it in that sequence allows you to focus on the most important issues first before looking into the 'minor' ones. Getting results on the 1st command is pretty bad. On the last one is to some extend expected, but may be worth looking into nonetheless. HTH [1] https://www.dell.com/support/home/en-us/product-support/product/precision-t1700-workstation/drivers
Attachment:
signature.asc
Description: This is a digitally signed message part.