I have isolated the kernel configuration differences down to:

doug@v32-serv03:~/kernel/linux-3.12.0$ diff config_def config_05
781c781
< CONFIG_X86_SYSFB=y
---
> # CONFIG_X86_SYSFB is not set
4869c4869
< CONFIG_FB_BOOT_VESA_SUPPORT=y
---
> # CONFIG_FB_BOOT_VESA_SUPPORT is not set
4900c4900
< CONFIG_FB_VESA=y
---
> # CONFIG_FB_VESA is not set

Where config_def is the default kernel configuration for the current
Trusty kernel and config_05 has 3 reversions back to the way they were
for Saucy. Each reversion by itself is not enough, they have to both (I
lump the two VESA ones into one, because one can not change one without
the other) be reverted.

Note that the console display does not work when the reversions are
done, and hasn't worked for most reversion attempts during this work. I
use ssh to access the computer.

Anticipated question: Why weren't display display issues mentioned
previously? It's kind of an important point?

Answer: Video display issues are very common on this computer when I
start messing with kernels, so I didn't think it was significant
earlier.


** Changed in: linux (Ubuntu)
       Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1254920

Title:
  CPU utilization / accounting issues

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1254920/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to