Great. With upstream version below,
carlos@carlosLT:~$ uname -a
Linux carlosLT 4.5.0-040500rc1-generic #201601241731 SMP Sun Jan 24 22:33:12
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
and I have three errors now:
carlos@carlosLT:~$ dmesg | grep ERROR
[ 39.837796] [drm:intel_set_cpu_fifo_underrun
OK. I'll do that now ...
--
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/1535879
Title:
It looks to be the (expired ) bug #1451632 drm:intel fifo
Status in linux package in Ubuntu:
Inc
Thanks form the A17 INFO Christopher.
After BIOS update the
carlos@carlosLT:~$ sudo dmidecode -s bios-version && sudo dmidecode -s
bios-release-date
A17
08/19/2015
A restart, and, I still have the same issue: No improvement.
carlos@carlosLT:~$ dmesg | grep drm:intel
[1.595212] [drm:intel_s
That's right... the problem is in Raring (the host).
There is no problem in the Saucy VM. It enters suspend mode and wakes up with
both kernels (3.11.0-3 and upstreams 3.11.0-031100rc6 and daily-build) with no
problems.
However, when I try to suspend the host (raring, kernel 3.8.0-30) having th
Hi Joseph.
On the host machine (raring, which is, I believe, the origin of the
problem) or on the VM (Saucy) ?
I will try first on the host and try to replicate the error. Then I'll
do the same for saucy.
Cheers,
Carlos
On 23/08/13 17:05, Joseph Salisbury wrote:
> Would it be possible for you t
Public bug reported:
It's a KernelOops ...under a VM (KVM, host Raring).
After suspending the host, and wake him up everything collapsed (host, VM).
Then after a hard restart of the host, the saucy VM came with this error.
I've no idea where the problem is. But it is true that on the last few week
6 matches
Mail list logo
