NetBSD and xserver and core dump and no drivers

Jeremy C. Reed reed at reedmedia.net
Wed May 24 17:58:23 PDT 2006


I have no drivers installed (yet).

On NetBSD/i386 3.99.18 (-current), latest Xorg core dumps. The log has:

(II) PCI-to-ISA bridge:
(II) Bus -1: bridge is at (0:17:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is 
set)
(--) PCI:*(1:0:0) unknown vendor (0x1106) unknown chipset (0x3122) rev 3, 
Mem @ 
0xd8000000/26, 0xde000000/24, BIOS @ 0xdfef0000/16

   *** If unresolved symbols were reported above, they might not
   *** be the reason for the server aborting.

Fatal server error:
Caught signal 11.  Server aborting


gdb backtrace is:

#0  0xbba276bb in kill () from /usr/lib/libc.so.12
#1  0xbbab3e49 in abort () from /usr/lib/libc.so.12
#2  0x08097f66 in ddxGiveUp () at xf86Init.c:1259
#3  0x0817824b in AbortServer () at log.c:408
#4  0x08178512 in FatalError (
    f=0x8187c80 "Caught signal %d.  Server aborting\n") at log.c:554
#5  0x080b7462 in xf86SigHandler (signo=11) at xf86Events.c:1495
#6  <signal handler called>
#7  0x080af313 in fixup_video_driver_list (drivers=0x0) at 
xf86Config.c:461
#8  0x080af499 in GenerateDriverlist (dirname=0x818721f "drivers", 
    drivernames=0x81a87c8 "") at xf86Config.c:514
#9  0x080af4e8 in xf86DriverlistFromCompile () at xf86Config.c:564
#10 0x080a9e8d in DoConfigure () at xf86Configure.c:782
#11 0x08097b06 in InitOutput (pScreenInfo=0x81b3880, argc=2, 
argv=0xbfbfeb74)
    at xf86Init.c:397
#12 0x0806bc1b in main (argc=2, argv=0xbfbfeb74, envp=0xbfbfeb80) at 
main.c:372
#13 0x0806b7a6 in ___start ()

ktrace shows:

  2582      1 Xorg     RET   write 1
  2582      1 Xorg     CALL  __stat30(0xbfbfe190,0xbfbfe100)
  2582      1 Xorg     NAMI  "/usr/local/lib/xorg/modules/drivers/netbsd/"
  2582      1 Xorg     RET   __stat30 -1 errno 2 No such file or directory
  2582      1 Xorg     CALL  __stat30(0xbfbfe190,0xbfbfe100)
  2582      1 Xorg     NAMI  "/usr/local/lib/xorg/modules/drivers"
  2582      1 Xorg     RET   __stat30 -1 errno 2 No such file or directory
  2582      1 Xorg     PSIG  SIGSEGV caught handler=0x80b73e8 mask=(): 
code=SEGV
_MAPERR, addr=0x0, trap=6)
  2582      1 Xorg     CALL  
__sigaction_sigtramp(SIGSEGV,0xbfbfe19c,0xbfbfe17c,
0xbba6887c,2)
  2582      1 Xorg     RET   __sigaction_sigtramp 0
  2582      1 Xorg     CALL  write(2,0x81b0a40,0x70)
  2582      1 Xorg     GIO   fd 2 wrote 112 bytes
       "
           *** If unresolved symbols were reported above, they might not
           *** be the reason for the server aborting.




Xorg should close cleanly without coredump when it detects a problem.



Jeremy C. Reed

p.s. Maybe the Version and Release Date should be updated for the current 
(MAIN) code so it is not misleading.

p.p.s I will install some drivers now ...



More information about the xorg mailing list