[Bug 240294] x11-drivers/xf86-video-ast does not work on FreeBSD 12

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240294

            Bug ID: 240294
           Summary: x11-drivers/xf86-video-ast does not work on FreeBSD 12
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: x11 at FreeBSD.org
          Reporter: darius at dons.net.au
             Flags: maintainer-feedback?(x11 at FreeBSD.org)
          Assignee: x11 at FreeBSD.org

Hi,
I have this port on a Supermicro X11SSH-F and it doesn't work, it hands the X
server (kill -9 required to recover).

I did some debugging and found it is stuck here..
0x0000000801ae1d86 in ASTGetDRAMInfo (pScrn=0x801af7000) at ast_vgatool.c:439
439         } while (*(volatile ULONG *) (pAST->MMIOVirtualAddr + 0x10000) !=
0x01);

(gdb) print/x *(volatile ULONG *) (pAST->MMIOVirtualAddr + 0x10000)
$2 = 0xffffffff

Reading around this area also reads 0xffffffff all the time.

ie it is like that memory is not correctly mapped.
I added some debugging to the mapping process in ASTMapMMIO:
[ 71021.555] (II) AST(0): pci_device_map_range Addr 0xdf000000 size 0x20000,
err 0 result 0x01b30000

But when I check ASTGetDRAMInfo()..
(gdb) print/x pAST->MMIOVirtualAddr
$2 = 0x801b30000

(gdb) print/x *(0x01b30000)
Cannot access memory at address 0x1b30000

The mappings look to match dmesg:
vgapci0: <VGA-compatible display> port 0xc000-0xc07f mem
0xde000000-0xdeffffff,0xdf000000-0xdf01ffff irq 18 at device 0.0 on pci4

Curiously on the working machine with an identical motherboard with FreeBSD 11
it is at a different location:
vgapci0: <VGA-compatible display> port 0xd000-0xd07f mem
0xf6000000-0xf6ffffff,0xf7000000-0xf701ffff irq 16 at device 0.0 on pci4

I extracted the values from the working system and hard coded them into the
FreeBSD 12 one and while it starts it is very slow (same speed as VESA)

The VESA driver is significantly slower than I expect, I am not sure if that is
related or just it sucking harder in new systems..

-- 
You are receiving this mail because:
You are the assignee for the bug.