[Kernel-packages] [Bug 1513648] Re: [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in ips_enabled (expected 1, found 0)

2015-11-14 Thread Patrik Jansson
I have now downloaded and installed kernel 4.3.0 as requested and this seems to have fixed the problem. I have added the corresponding tags but I'm not sure about the "spelling" of the version numbers. Another example in the standard text would be helpful (there was no match on the pattern "X.Y-rc

[Kernel-packages] [Bug 1513648] Re: [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in ips_enabled (expected 1, found 0)

2015-11-14 Thread Patrik Jansson
** Tags added: kernel-fixed-upstream kernel-fixed- upstream-4.3.0-040300-generic -- 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/1513648 Title: [drm:intel_pipe_config_compare [i915]] *ERR

Re: [Kernel-packages] [Bug 1513648] Re: [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in ips_enabled (expected 1, found 0)

2015-11-11 Thread Patrik Jansson
patrikj@etyd:~$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date A16 09/01/2015 onsdag 11 november 2015 skrev Christopher M. Penalver < christopher.m.penal...@gmail.com>: > Patrik Jansson, could you please provide the output of the following > term

Re: [Kernel-packages] [Bug 1513648] Re: [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in ips_enabled (expected 1, found 0)

2015-11-10 Thread Patrik Jansson
The bug appeared after upgrade from Ubuntu 15.04 to 15.10 or possibly after some refular update after that. I have now upgraded to the lates BIOS (A16) but the problem remains. Should I re-run something to report potentially updated files? Below are the (this time two) "cut here" sections. Kind

[Kernel-packages] [Bug 1513648] [NEW] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in ips_enabled (expected 1, found 0)

2015-11-05 Thread Patrik Jansson
Public bug reported: A few seconds after boot I get this message in the log (and wifi does not activate). Many things still work, but the system acts a bit confused. Sometimes it gets almost unsusable until reboot (and then there are more of those "cut here" sections in the log). Kind regards,