[Openchrome-devel] [Bug 95420] Driver 0.4.0 crashes with recent linux kernel version

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Jun 14 21:09:51 UTC 2016


--- Comment #26 from Kevin Brace <kevinbrace at gmx.com> ---
(In reply to Tolsti from comment #25)

Hi Torsten,

> Hello Kevin,
> do not worry, I am a linux admin, so I do not mind helping with this problem
> (and helping to get my own linux at home running again).
> Your hint with the memory begin already mapped was pretty good: viafb was
> using it. So I disabled the video driver with the kernel parameter 
> "video=vesa:off vga=normal"
> The driver is working fine again.

Okay, this basically exonerates OpenChrome, but it is still not nice having
this problem.
I will file a bug report with bugzilla.kernel.org regarding this bug in the
next 24 hours.
    I saw this part of the dmesg that caught my attention.

. . .
[    1.656374] io scheduler deadline registered
[    1.656455] io scheduler cfq registered (default)
[    1.656657] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[    1.656703] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
[    1.656730] vesafb: mode is 1280x800x32, linelength=5120, pages=0
[    1.656733] vesafb: scrolling: redraw
[    1.656736] vesafb: Truecolor: size=0:8:8:8, shift=0:16:8:0
[    1.656767] vesafb: framebuffer at 0xf4000000, mapped to 0xffffc90000400000,
using 4032k, total 4032k
[    1.711655] Console: switching to colour frame buffer device 160x50
[    1.766240] fb0: VESA VGA frame buffer device
[    1.766341] GHES: HEST is not enabled!
[    1.766508] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    1.787091] 00:04: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a
[    1.787657] Linux agpgart interface v0.103
. . .

You are right.
VESA FB device driver is claiming address 0xf4000000.
This is the same address OpenChrome will try to claim later on.

. . .
[    15.506] (II) Module vgahw: vendor="X.Org Foundation"
[    15.507]    compiled for 1.18.3, module version = 0.1.0
[    15.507]    ABI class: X.Org Video Driver, version 20.0
[    15.507] (--) CHROME(0): Probed amount of VideoRAM = 16384 kB
[    15.507] (II) CHROME(0): Entered viaMapMMIO.
[    15.507] (--) CHROME(0): Mapping MMIO at address 0xFB000000 with size 52
[    15.507] (--) CHROME(0): Mapping 2D Host BitBLT space at address 0xFB200000
with size 2048 KB.
[    15.507] (--) CHROME(0): Mapping the frame buffer at address 0xF4000000
with size 16384 KB.
[    15.507] (EE) CHROME(0): Unable to map the frame buffer.
Error: Invalid argument (22)
[    15.507] (II) CHROME(0): Exiting viaMapMMIO.
[    15.507] (II) CHROME(0): VIAFreeRec
[    15.507] (II) CHROME(0): VIAFreeScreen
[    15.507] (II) UnloadModule: "openchrome"
[    15.507] (II) UnloadSubModule: "vgahw"
[    15.507] (II) Unloading vgahw
[    15.507] (EE) Screen(s) found, but none have a usable configuration.
[    15.507] (EE) 
Fatal server error:
[    15.507] (EE) no screens found(EE) 
[    15.507] (EE) 
Please consult the The X.Org Foundation support 
         at http://wiki.x.org
 for help. 
[    15.507] (EE) Please also check the log file at "/var/log/Xorg.0.log" for
additional information.
[    15.507] (EE) 
[    15.528] (EE) Server terminated with error (1). Closing log file.

For now, if you wanted to use OpenChrome with Linux 4.5 or later, please
disable VESA frame buffer device driver.
    One "good" thing about this bug you reported is that it allowed issues with
the DDX error handling code to be exercised.
I do go into this issue all the time, but I took over the development of this
project only this February, and I think it is fair to say that previous
developers did not really think through when they wrote many portions of the
code, particularly DDX and display controller initialization.
I have been spending a lot of time cleaning up the code so that it is more
readable and maintainable.
I knew I had to eventually clean up the portions of the code that caused all
the segmentation faults, however, most of the time the old code did not cause
issues, so it was assigned to be a low priority item.
It appears that segmentation fault is no longer happening, and that is what I
    This bug is interesting since there was a report of OpenChrome not booting
if viafb was not loaded (Bug 94797).
This person was using Linux 4.4 kernel.
The bug is still open, and I plan to contact this person for more testing.
    Anyway, I will move the bug report to bugzilla.kernel.org very soon, and
deal with it over there.
Now that OpenChrome is exonerated, I will turn the latest OpenChrome into
Version 0.5 RC2 (Release Candidate 2) in the next few days.

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/openchrome-devel/attachments/20160614/41bad213/attachment-0001.html>

More information about the Openchrome-devel mailing list