This bug was fixed in the package linux - 3.19.0-18.18
---
linux (3.19.0-18.18) vivid; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1456732
[ Upstream Kernel Changes ]
* Revert "drm/i915: remove intel_pipe_set_base() (v4)"
- LP: #1453593
linux (3.19
This bug was fixed in the package linux - 3.16.0-38.52
---
linux (3.16.0-38.52) utopic; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1452623
[ Stefan Bader ]
* SAUCE: vesafb: Set mtrr:3 (write-combining) as default
- LP: #1434581
[ Upstream Kernel
This bug was fixed in the package linux - 3.13.0-53.88
---
linux (3.13.0-53.88) trusty; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1454785
[ Upstream Kernel Changes ]
* mmc: card: Don't access RPMB partitions for normal read/write
- LP: #1454013
linux
This bug was fixed in the package linux - 3.19.0-17.17
---
linux (3.19.0-17.17) vivid; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1452000
[ Damien Lespiau ]
* SAUCE: i915_bpo: drm/i915/skl: Fix stepping check for a couple of W/As
- LP: #1449469
* SAUC
I tried all three kernels on a Dell R320 with no kernel command line
options and they all resolve the issue.
** Tags removed: verification-needed-trusty verification-needed-utopic
verification-needed-vivid
** Tags added: verification-done-trusty verification-done-utopic
verification-done-vivid
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
utopic' to 'verification-done-utopic'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from tod
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
** Changed in: linux (Ubuntu Trusty)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1434581
Title:
Console extremely slow with 3.13 and newer kernels for cer
** Changed in: linux (Ubuntu Utopic)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1434581
Title:
Console extremely slow with 3.13 and newer kernels for cer
** Changed in: linux (Ubuntu Vivid)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1434581
Title:
Console extremely slow with 3.13 and newer kernels for cert
That kernel flag works. Thanks for pushing this along.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1434581
Title:
Console extremely slow with 3.13 and newer kernels for certified
servers with Ma
SRU Justification:
Impact: After dropping a sauce patch to make vesafb a module we
accidentally dropped a change to make mtrr:3 (write-combining remap
range) the default. This results in a performance degradation for
graphics cards that have no drm framebuffer driver (especially on higher
resoluti
Ah, that now makes sense. And since I could reach and search the older
git trees today I found that we had only one SAUCE patch to vesafb in
Saucy/13.10. Which was a combination of previous patches but titled as
modularization patch. So having vesafb as a module was special and since
Trusty/14.04 w
I added the change from the SAUCE patch in May of 2011 to 3.13.0-48 and
rebuilt. It fixes the problem.
-static int mtrr __read_mostly; /* disable mtrr */
+static int mtrr __read_mostly = 3; /* disable mtrr */
I've attached the kernel, 3-13.0-48.80+testfb.
** Attachmen
Both of your finds are interesting considering the vesafb SAUCE patches
seem to be making a change to mtrr.
https://lists.ubuntu.com/archives/kernel-team/2011-May/015600.html
https://lists.ubuntu.com/archives/kernel-team/2013-March/027111.html
--
You received this bug notification because you a
Hm, interesting. When booting with 3.11 from Saucy, scrolling seems
quicker (my interactivity local is buggered by a keyboard monitor switch
which some day I should replace), at least I could not really read what
scrolled by while I could with 3.13. And looking at /proc/mtrr I found a
write-combini
So at least I can confirm that a boot with 3.13 and vesafb set to
1280x1024 by grub (the default otherwise was 640x480) scrolls by quite
slowly. I need to get a pre-3.12 there to get to see the before state.
Looking at the code in 3.13, I see only one change to vesafb that came
related to introduc
3.11.x and earlier versions from mainline give me no display -- just a
black screen on boot. The system does work, and I posted a dmesg from
that boot earlier (dmesg110.txt is the name of the file.) So there's
definitely some sort of SAUCE patch or patches that make vesafb work
with those kernels,
I think he was guessing that there might be additional patches, but if you
tried the mainline builds for 3.11.x we can rule that out. The mainline builds
are without any special driver patches for that reason. It looks like some kind
of regression in vesafb (either due to changing that or someth
3.11.0-12 does not have the bug, while 3.12.0-1 with SYSFB=n does. It
looks like 3.12 is when simplefb was implemented (as you noted in a
previous post) and when vesafb was integrated.
Based on Joseph Salisbury's comment #24 above noting that the older
Ubuntu kernels had SAUCE patches to make vesa
Thanks, that'll help if your host has the G200 based IPMI card.
Mainline kernels before 3.13 don't work at all, and the versions of 3.13
built with SYSFB=y are fine while the ones with SYSFB=n are not.
Comments 15 and 19.
I downloaded the source for 3.11.0-12, 3.12.0-1 and 3.13.0-1 from
(https://
Ok, I try whether I can see a similar regression on a host I got at home
when I get there. If that does not work or if you want to try out
beforehand, http://kernel.ubuntu.com/~kernel-ppa/mainline/ has a number
of builds between so you might try 3.12 (with simplefb blacklisted) to
get a closer rang
Yep, one machine, three kernels.
I didn't have /etc/default/openipmi since I don't have the openipmi
package installed. I tried installing it and flipping those off, also I
tried blacklisting ipmi_si and ipmi_devintf. Unfortunately, there was no
change.
I can install and post logs for just about
No kernel change. Basically changes to /etc/default/grub are used when
running update-grub to create the grub configuration. Leaving
GRUB_TERM=console commented out causes grub to initialize some higher
resolution graphics framebuffer mode. And (not quite sure) it might be
that about some point in
** Attachment added: "[Correction] dmesg - Ubuntu 12.04 kernel v3.13.0-49
SYSFB=y"
https://bugs.launchpad.net/ubuntu/trusty/+source/linux/+bug/1434581/+attachment/4378621/+files/dmesg%201204%20313%20sysfby.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
** Attachment added: "dmesg - Ubuntu 12.04 kernel v3.13.0-49 SYSFB=y"
https://bugs.launchpad.net/ubuntu/trusty/+source/linux/+bug/1434581/+attachment/4378618/+files/fb1204313sysfby.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Attachment added: "dmesg - Ubuntu 12.04 Kernel v3.13.0-48 SYSFB=n"
https://bugs.launchpad.net/ubuntu/trusty/+source/linux/+bug/1434581/+attachment/4378600/+files/dmesg%201204%20313%20sysfbn.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
** Attachment added: "dmesg - Ubuntu 12.04 Kernel v3.2"
https://bugs.launchpad.net/ubuntu/trusty/+source/linux/+bug/1434581/+attachment/4378599/+files/dmesg%201204%2032.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
Understood. I agree that not completely breaking virtual machines in
some hypervisors is important. While I'm required to use bare-metal
installs on these systems, I depend on VMs as much as the next person.
There has to be an alternate solution.
Are you suggesting there's a kernel change needed t
SYSFB/simpleframebuffer did not exist before 3.12 (iirc). When having
CONFIG_X86_SYSFB=N there is no way to force it since it does not get
built (as before). And given the other issues I do not think we should.
The difference with vesafb is not necessarily in code (and as that has
been around for
That's correct, the VESA framebuffer (vesafb) is what I saw on lsmod on
older kernels. I can do any other testing you'd like with different
kernels or versions of Ubuntu as the system I'm doing this on is purely
test. Pre-setting the desired resolution results in a slow console and
setting GRUB_TER
I would have to do more testing, but it does not look like the simple
framebuffer driver ever got fixed to release the memory resource and so, as
soon as we turn on that, we will have the old issue of VMs (using cirrus
default gfx) coming up with no graphical console at all.
That said, the simpl
I built 3.13.0-48.80 with CONFIG_X86_SYSFB=y since it was set to n in
3.13.0-7.24. This resolves the issue. I can upload the built kernel if
necessary.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/143
** Tags added: latest-bios-2.3.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1434581
Title:
Console extremely slow with 3.13 and newer kernels for certified
servers with Matrox G200er2 or simila
3.13.0-1 that you linked does not have the bug.
3.13.0-6.23 does not have it: https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/ppa/+build/5537054
3.13.0-7.24 appears to be a failed build, but maybe one of the commits
is related:
https://launchpad.net/ubuntu/+source/linux/3.13.0-7.24/
Vesafb was a module in the 3.11 and older kernels. It is now built into
the kernel, which is why that file does not exist.
There some vesa specific SAUCE patches in Ubuntu that are not upstream,
so that may be why the upstream kernels don't work.
We could bisect between the Ubuntu kernels instea
I tested more mainline kernels: 3.2.0 through 3.10.0. The corresponding
Ubuntu kernels (ex: lts-quantal 3.5.0-54 vs mainline 3.5.0) work
properly. The ones from mainline all black screen.
If I go to / and do find . -name vesafb.ko only the Ubuntu kernels from
3.11 and earlier have the file.
Was t
** Attachment added: "dmesg12rc1.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1434581/+attachment/4354502/+files/dmesg12rc1.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1434581
T
** Attachment added: "dmesg120.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1434581/+attachment/4354501/+files/dmesg120.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1434581
Title
** Attachment added: "dmesg110.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1434581/+attachment/4354500/+files/dmesg110.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1434581
Title
I tried more kernels this morning, and unfortunately my results weren't
so good.
All of the v3.12-rc# kernels, v3.11.0 and v3.11.10.15 give me a black
screen. The system does boot and function, but I am blind. I'm attaching
the dmesg from v3.12.0, v3.12-rc1 and v3.11.0.
The last versions of 3.8 (
Chris, the output is:
2.3.3
07/10/2014
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1434581
Title:
Console extremely slow with 3.13 and newer kernels for certified
servers with Matrox G200er2 or
Mike Jester, could you please provide the output of the following terminal
command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-4.0
Can you test the following two Upstream kernels:
v3.11 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-saucy/
v3.12-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc1-saucy/
We can bisect between these two versions if 3.11 final is good and
v3.12-rc1 had the bug.
** Tags a
In an attempt to narrow it down, I downloaded some more kernels from
mainline to test. I reloaded the machine with 12.04 and tried 3.11.0-26
(via linux-generic-lts-saucy meta) and 3.12.0 from the mainline
repository. 3.12.0 is slow like 3.13 and 3.11.0-26 performs fine as
noted in the original rep
** Tags added: needs-bisect
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1434581
Title:
Console extremely slow with 3.13 and newer kernels for certified
servers with Matrox G200er2 or similar
To
I updated the BIOS to 2.3.3, and I used kernel 4.0-rc5 that was posted
this morning. No change. Running dpkg -l is still a slideshow.
I removed the bios-outdated tag, let me know if I need to do another
collect.
** Tags removed: bios-outdated-2.3.3
--
You received this bug notification because
** Tags added: bios-outdated-2.3.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1434581
Title:
Console extremely slow with 3.13 and newer kernels for certified
servers with Matrox G200er2 or simi
I can do that on Monday when I'm back in the office no problem. This is
a test machine so I can do just about anything with it. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1434581
Title:
C
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.0 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix th
** 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/1434581
Title:
Console extremely slow with 3.13 and newer kernels for certified
s
apport information
** Tags added: apport-collected trusty
** Description changed:
When I first came across this issue I thought it was the same as bug
#1316035 (https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1316035), but this bug seems to be about X and it is
reporting xorg
53 matches
Mail list logo
