Arch Linux

danvari

Member

Registered: 2007-08-14

Posts: 44

V86d segfault

hey!

I have got the following problem: Sometimes when i switch from X to console (strg+alt+F*), v86d segfaults and i will not see anything. i have to switch back to X and then back to console. With sometimes i mean every second time (more or less). the output of dmesg:

v86d[533]: segfault at 7f5d91344000 ip 00000000004008d8 sp 00007fff1944c640 error 7 in v86d (deleted)[400000+18000]
uvesafb: mode switch failed (eax=0x4f02, err=1)
v86d[2087]: segfault at 7f3ebda61000 ip 00000000004014a8 sp 00007fff1adc4b40 error 7 in v86d[400000+1a000]
uvesafb: mode switch failed (eax=0x4f02, err=1)
v86d[2232]: segfault at 7f53026e0282 ip 00000000004014b8 sp 00007fff01e03370 error 7 in v86d[400000+1a000]
uvesafb: mode switch failed (eax=0x4f02, err=1)
v86d[2407]: segfault at 7f25e3406000 ip 00000000004014b8 sp 00007fffefecd280 error 7 in v86d[400000+1a000]
uvesafb: mode switch failed (eax=0x4f02, err=1)
v86d[2490]: segfault at 7fb3943ed000 ip 00000000004014b8 sp 00007fffddec88a0 error 7 in v86d[400000+1a000]
uvesafb: mode switch failed (eax=0x4f02, err=1)
v86d[2517]: segfault at 7fb7528f4000 ip 00000000004014a8 sp 00007fff8bf3c770 error 7 in v86d[400000+1a000]
uvesafb: mode switch failed (eax=0x4f02, err=1)

my uvesafb config:

options uvesafb mode_option=1400x1050-16 scroll=ywrap

hwinfo --framebuffer:

02: None 00.0: 11001 VESA Framebuffer                           
  [Created at bios.459]
  Unique ID: rdCR.gPoPaTNz350
  Hardware Class: framebuffer
  Model: "NVIDIA G72 Board - e463h0v"
  Vendor: "NVIDIA Corporation"
  Device: "G72 Board - e463h0v"
  SubVendor: "NVIDIA"
  SubDevice: 
  Revision: "Chip Rev"
  Memory Size: 256 MB
  Memory Range: 0xd0000000-0xdfffffff (rw)
  Mode 0x0300: 640x400 (+640), 8 bits
  Mode 0x0301: 640x480 (+640), 8 bits
  Mode 0x0303: 800x600 (+800), 8 bits
  Mode 0x0305: 1024x768 (+1024), 8 bits
  Mode 0x0307: 1280x1024 (+1280), 8 bits
  Mode 0x030e: 320x200 (+640), 16 bits
  Mode 0x030f: 320x200 (+1280), 24 bits
  Mode 0x0311: 640x480 (+1280), 16 bits
  Mode 0x0312: 640x480 (+2560), 24 bits
  Mode 0x0314: 800x600 (+1600), 16 bits
  Mode 0x0315: 800x600 (+3200), 24 bits
  Mode 0x0317: 1024x768 (+2048), 16 bits
  Mode 0x0318: 1024x768 (+4096), 24 bits
  Mode 0x031a: 1280x1024 (+2560), 16 bits
  Mode 0x031b: 1280x1024 (+5120), 24 bits
  Mode 0x0330: 320x200 (+320), 8 bits
  Mode 0x0331: 320x400 (+320), 8 bits
  Mode 0x0332: 320x400 (+640), 16 bits
  Mode 0x0333: 320x400 (+1280), 24 bits
  Mode 0x0334: 320x240 (+320), 8 bits
  Mode 0x0335: 320x240 (+640), 16 bits
  Mode 0x0336: 320x240 (+1280), 24 bits
  Mode 0x033d: 640x400 (+1280), 16 bits
  Mode 0x033e: 640x400 (+2560), 24 bits
  Mode 0x0347: 1400x1050 (+1400), 8 bits
  Mode 0x0348: 1400x1050 (+2800), 16 bits
  Config Status: cfg=new, avail=yes, need=no, active=unknown

mkinitcpio.conf:

...
HOOKS="base udev autodetect pata scsi sata filesystems keymap v86d"
...

[root@myhost stephan]# pacman -Q v86d
v86d 0.1.9-7

any ideas?

skottish

Forum Fellow

From: Here

Registered: 2006-06-16

Posts: 7,942

Re: V86d segfault

The v86d hook should be before the filesystems and keymaps hook. It's probably best to put it right after the udev hook.