On Sat, Nov 02, 2024 at 11:23:50PM +0100, Marcel Telka wrote:
>
> I do have simlar warnings for ages (see below) and lightdm works okay (no
> cores). So I suggest to do the core file analysis to find what's happening.
This system uses this CPU:
The physical processor has 4 virtual processors (0-3)
x86 (GenuineIntel 906EB family 6 model 158 step 11 clock 3600 MHz)
Intel(r) Core(tm) i3-9100 CPU @ 3.60GHz
It also uses Intel's built-in graphics, unlike my other system that
use an ATI Radeon card.
Ah, I see this error in /mnt/var/log/Xorg.0.log :
[ 84.638] (EE) Server terminated with error (1). Closing log file.
I suppose the driver stopped working.
Here's what I got with mdb on the core file:
<root@intel># mdb /mnt/core
Loading modules: [ libc.so.1 ld.so.1 ]
> ::status
debugging core file of lightdm (64-bit) from intel
initial argv: /usr/sbin/lightdm
threading model: native threads
status: process terminated by SIGSEGV (Segmentation Fault), addr=c8
> ::stack
display_server_stopped_cb+0x2a9()
libgobject-2.0.so.0.8200.2`_g_closure_invoke_va+0xd0()
libgobject-2.0.so.0.8200.2`signal_emit_valist_unlocked+0x1173()
libgobject-2.0.so.0.8200.2`g_signal_emit_valist+0x3d()
libgobject-2.0.so.0.8200.2`g_signal_emit+0x7d()
libgobject-2.0.so.0.8200.2`g_closure_invoke+0xc5()
libgobject-2.0.so.0.8200.2`signal_emit_unlocked_R.isra.0+0xb86()
libgobject-2.0.so.0.8200.2`signal_emit_valist_unlocked+0x10c1()
libgobject-2.0.so.0.8200.2`g_signal_emit_valist+0x3d()
libgobject-2.0.so.0.8200.2`g_signal_emit+0x7d()
libglib-2.0.so.0.8200.2`g_child_watch_dispatch+0x66()
libglib-2.0.so.0.8200.2`g_main_dispatch+0xb6()
libglib-2.0.so.0.8200.2`g_main_context_iterate_unlocked.isra.0+0x2a8()
libglib-2.0.so.0.8200.2`g_main_loop_run+0x117()
main+0xcc7()
_start_crt+0x87()
_start+0x18()
> ^d
--
-Gary Mills- -refurb- -Winnipeg, Manitoba, Canada-
_______________________________________________
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev
