[oi-dev] lightdm failed repeatedly

[Carsten Grzemba]

Am 03.11.24 22:26 schrieb Gary Mills  <gary_mills at fastmail.fm>: 
> 
> On Sun, Nov 03, 2024 at 08:10:26AM +0100, Marcel Telka wrote:
> > 
> > The segfault happened here (apparently rax is zero):
> > 
> > > display_server_stopped_cb+0x2a9::dis
> > display_server_stopped_cb+0x27b:jne -0x154 <display_server_stopped_cb+0x12d>
> > display_server_stopped_cb+0x281:nopl 0x0(%rax)
> > display_server_stopped_cb+0x288:movq -0x38(%rbp),%rdi
> > display_server_stopped_cb+0x28c:movl $0x41a2e8,%esi <PLT:g_object_unref>
> > display_server_stopped_cb+0x291:call -0x1450e <PLT:g_list_free_full>
> > display_server_stopped_cb+0x296:movl 0x44(%r14),%edx
> > display_server_stopped_cb+0x29a:testl %edx,%edx
> > display_server_stopped_cb+0x29c:jne -0x1dd <display_server_stopped_cb+0xc5>
> > display_server_stopped_cb+0x2a2:movq (%r12),%rax
> > display_server_stopped_cb+0x2a6:movq %r12,%rdi
> > display_server_stopped_cb+0x2a9:call *0xc8(%rax) <------------- HERE
> > display_server_stopped_cb+0x2af:movq %rax,%rdi
> > display_server_stopped_cb+0x2b2:testq %rax,%rax
> > display_server_stopped_cb+0x2b5:je +0xe <display_server_stopped_cb+0x2c5>
> > display_server_stopped_cb+0x2b7:call +0x4724 <session_get_display_server>
> > display_server_stopped_cb+0x2bc:cmpq %rax,%r13
> > display_server_stopped_cb+0x2bf:jne -0x200 <display_server_stopped_cb+0xc5>
> > display_server_stopped_cb+0x2c5:call -0x83da <logger_get_type>
> > display_server_stopped_cb+0x2ca:movq %r12,%rdi
> > display_server_stopped_cb+0x2cd:movq %rax,%rsi
> > display_server_stopped_cb+0x2d0:call -0x146bd <PLT:g_type_check_instance_cast>
> 
> That may be a secondary error. The first one may be in the VESA
> driver. Here's what I see in /mnt/var/log/Xorg.0.log:
> 
> [ 84.601] (II) VESA(0): initializing int10
> [ 84.601] (EE) VESA(0): V_BIOS address 0x0 out of range
> ...
> [ 84.601] (EE) Screen(s) found, but none have a usable configuration.
> [ 84.601] (EE)
> Fatal server error:
> [ 84.601] (EE) no screens found(EE)
> [ 84.601] (EE)
> Please consult the Project OpenIndiana support
>  at http://openindiana.org
>  for help.
> [ 84.601] (EE) Please also check the log file at "/var/log/Xorg.0.log" for
> +additional information.
> [ 84.601] (EE)
> [ 84.638] (EE) Server terminated with error (1). Closing log file.
>  
> It seems that the VESA driver got an error and terminated. The intel
> driver was never tried. Note that this is a BIOS boot, not an UEFI boot.
> 
> For comparison, here's part of /var/log/Xorg.0.log for the old BE:
> 
> [ 97.894] (II) VESA(0): initializing int10
> [ 97.900] (II) VESA(0): Primary V_BIOS segment is: 0xc000
> [ 97.905] (II) VESA(0): VESA BIOS detected
> [ 97.905] (II) VESA(0): VESA VBE Version 3.0
> [ 97.905] (II) VESA(0): VESA VBE Total Mem: 65472 kB
> [ 97.905] (II) VESA(0): VESA VBE OEM: Intel(R) CFL Mobile/Desktop Graphics
> +Chipset Accelerated VGA BIOS
> [ 97.905] (II) VESA(0): VESA VBE OEM Software Rev: 0.0
> ...
> [ 98.100] (II) VESA(0): Setting up VESA Mode 0x17F (1600x900)
> [ 98.200] (==) VESA(0): Default visual is TrueColor
> [ 98.207] (==) VESA(0): Backing store enabled
> [ 98.218] (==) VESA(0): DPMS enabled
> 
> -- -Gary Mills- -refurb- -Winnipeg, Manitoba, Canada-
> 

I have a similar problem on my laptop since May 2024. There the result is a wrong resolution 1024x768, no crash. The background of the problem here is the updated DRM package. 

The updated DRM software do not use anymore the old intel driver (i915).


Carsten
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20241105/6bb25e76/attachment.html>