You were right, it was fixed. Just tried the snapshot dated 9/5 and X is working. I guess there just wasn't a new snapshot with the fix.
Tim. On Thu, Sep 4, 2014 at 8:03 PM, trondd <tro...@gmail.com> wrote: > Let me know if there is some way I can help debug this. > Here is the X log: > > [ 143.915] (--) Using wscons driver on /dev/ttyC1 in pcvt compatibility > mode (version 3.32) > [ 144.389] > X.Org X Server 1.15.2 > Release Date: 2014-06-27 > [ 144.537] X Protocol Version 11, Revision 0 > [ 144.612] Build Operating System: OpenBSD 5.6 zaurus > [ 144.688] Current Operating System: OpenBSD zaurus.home.com 5.6 > GENERIC#30 zaurus > [ 144.773] Build Date: 01 August 2014 08:04:09AM > [ 144.847] > [ 144.922] Current version of pixman: 0.32.6 > [ 144.996] Before reporting problems, check http://wiki.x.org > to make sure that you have the latest version. > [ 144.996] Markers: (--) probed, (**) from config file, (==) default > setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > [ 145.304] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Sep 3 > 00:32:38 2014 > [ 145.481] (==) Using config file: "/etc/X11/xorg.conf" > [ 145.555] (==) No Layout section. Using the first Screen section. > [ 145.581] (==) No screen section available. Using defaults. > [ 145.582] (**) |-->Screen "Default Screen Section" (0) > [ 145.582] (**) | |-->Monitor "<default monitor>" > [ 145.596] (==) No device specified for screen "Default Screen Section". > Using the first device section listed. > [ 145.596] (**) | |-->Device "Wsdisplay0" > [ 145.597] (==) No monitor specified for screen "Default Screen Section". > Using a default monitor configuration. > [ 145.600] (==) Disabling SIGIO handlers for input devices > [ 145.601] (==) Automatically adding devices > [ 145.602] (==) Automatically enabling devices > [ 145.602] (==) Not automatically adding GPU devices > [ 146.237] (==) FontPath set to: > /usr/X11R6/lib/X11/fonts/misc/, > /usr/X11R6/lib/X11/fonts/TTF/, > /usr/X11R6/lib/X11/fonts/OTF/, > /usr/X11R6/lib/X11/fonts/Type1/, > /usr/X11R6/lib/X11/fonts/100dpi/, > /usr/X11R6/lib/X11/fonts/75dpi/ > [ 146.237] (==) ModulePath set to "/usr/X11R6/lib/modules" > [ 146.238] (II) The server relies on wscons to provide the list of input > devices. > If no devices become available, reconfigure wscons or disable > AutoAddDevices. > [ 146.263] (II) Loader magic: 0x1f6c3c > [ 146.263] (II) Module ABI versions: > [ 146.264] X.Org ANSI C Emulation: 0.4 > [ 146.264] X.Org Video Driver: 15.0 > [ 146.264] X.Org XInput driver : 20.0 > [ 146.265] X.Org Server Extension : 8.0 > [ 146.359] Initializing built-in extension Generic Event Extension > [ 146.434] Initializing built-in extension SHAPE > [ 146.509] Initializing built-in extension MIT-SHM > [ 146.584] Initializing built-in extension XInputExtension > [ 146.659] Initializing built-in extension XTEST > [ 146.738] Initializing built-in extension BIG-REQUESTS > [ 146.828] Initializing built-in extension SYNC > [ 146.919] Initializing built-in extension XKEYBOARD > [ 147.009] Initializing built-in extension XC-MISC > [ 147.099] Initializing built-in extension SECURITY > [ 147.174] Initializing built-in extension XINERAMA > [ 147.249] Initializing built-in extension XFIXES > [ 147.323] Initializing built-in extension RENDER > [ 147.398] Initializing built-in extension RANDR > [ 147.473] Initializing built-in extension COMPOSITE > [ 147.548] Initializing built-in extension DAMAGE > [ 147.623] Initializing built-in extension MIT-SCREEN-SAVER > [ 147.698] Initializing built-in extension DOUBLE-BUFFER > [ 147.773] Initializing built-in extension RECORD > [ 147.848] Initializing built-in extension DPMS > [ 147.923] Initializing built-in extension Present > [ 147.998] Initializing built-in extension X-Resource > [ 148.073] Initializing built-in extension XVideo > [ 148.149] Initializing built-in extension XVideo-MotionCompensation > [ 148.224] Initializing built-in extension XFree86-VidModeExtension > [ 148.299] Initializing built-in extension XFree86-DGA > [ 148.374] Initializing built-in extension XFree86-DRI > [ 148.449] Initializing built-in extension DRI2 > [ 148.451] (II) LoadModule: "glx" > [ 148.557] (II) Loading /usr/X11R6/lib/modules/extensions/libglx.so > [ 148.695] (II) Module glx: vendor="X.Org Foundation" > [ 148.696] compiled for 1.15.2, module version = 1.0.0 > [ 148.696] ABI class: X.Org Server Extension, version 8.0 > [ 148.697] (==) AIGLX enabled > [ 148.773] Loading extension GLX > [ 148.774] (II) LoadModule: "wsfb" > [ 148.780] (II) Loading /usr/X11R6/lib/modules/drivers/wsfb_drv.so > [ 148.831] (II) Module wsfb: vendor="X.Org Foundation" > [ 148.831] compiled for 1.15.2, module version = 0.4.1 > [ 148.832] ABI class: X.Org Video Driver, version 15.0 > [ 148.834] (II) wsfb: driver for wsdisplay framebuffer: wsfb > [ 148.835] (WW) Falling back to old probe method for wsfb > [ 148.841] (II) wsfb(0): using /dev/ttyC1 > [ 148.858] (EE) Segmentation fault at address 0x10 > [ 148.935] (EE) > Fatal server error: > [ 149.008] (EE) Caught signal 11 (Segmentation fault). Server aborting > [ 149.084] (EE) > [ 149.158] (EE) > Please consult the The X.Org Foundation support > at http://wiki.x.org > for help. > [ 149.229] (EE) Please also check the log file at "/var/log/Xorg.0.log" > for additional information. > [ 149.303] (EE) > [ 149.453] (EE) Server terminated with error (1). Closing log file. > > > > On Thu, Sep 4, 2014 at 8:04 AM, trondd <tro...@gmail.com> wrote: > >> Appreciate it. >> >> I didn't have time to grab the log last night, but it crashes right after >> loading the wsfb driver. Signal 11, address 0x10. Was working on trying >> to build with debug symbols and getting a core dump. >> >> Tim. >> >> >> On Thu, Sep 4, 2014 at 5:14 AM, Alexandre Ratchov <a...@caoua.org> wrote: >> >>> On Wed, Sep 03, 2014 at 04:44:48PM -0400, trondd wrote: >>> > Just tried a recent snapshot and X still crashes at startup. It's been >>> > broken since the 5.5 release on the Zaurus. >>> > >>> > Someone had mentioned it was fixed [1], but it isn't as of Aug 28th. >>> > >>> > Is there someone able to look into this? I can help debug. It'd be >>> great >>> > if X was working again for 5.6. >>> > >>> >>> May be it was broken again, or maybe you're seeing another bug. I >>> tested the code tagged for 5.6, and X worked fine on my C3200. I'll >>> try a recent snapshot when I get some time. >>> >> >> >
