v86d crashed with SIGSEGV

[Teräslilja]

Binary package hint: v86d

1)
Description: Ubuntu intrepid (development branch)
Release: 8.10

2) 0.1.5-1ubuntu2

3) normal login

4) v86d crashed

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Dependencies:
 libgcc1 1:4.3.1-8ubuntu3
 gcc-4.3-base 4.3.1-8ubuntu3
 findutils 4.4.0-2ubuntu3
 libc6 2.8~20080505-0ubuntu6
DistroRelease: Ubuntu 8.10
ExecutablePath: /sbin/v86d
NonfreeKernelModules: nvidia
Package: v86d 0.1.5-1ubuntu2
ProcAttrCurrent: unconfined
ProcCmdline: /sbin/v86d
ProcEnviron: PATH=/sbin:/bin
Signal: 11
SourcePackage: v86d
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: v86d crashed with SIGSEGV
Uname: Linux 2.6.26-5-generic x86_64
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:?? ()
?? ()
?? ()
?? ()
?? ()

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

[Christian Roessner (christian-roessner-net)]

I hope I can confirm this bug (Not sure, if it is the same bug). After installing v86d, recreating the initramfs and rebooting, my pc speaker started making a lot of beeps. The screen kept black and after I logged into my gnome session, I found this in dmesg:

[ 1.980092] v86d[1094]: segfault at 0 ip 0000000000402069 sp 00007fff35237eb0 error 4 in v86d[400000+1a000]
[ 2.751750] Program usplash tried to access /dev/mem between 0->e00000.
[ 6.812016] uvesafb: Getting VBE info block failed (eax=0x4f00, err=1)
[ 6.812019] uvesafb: vbe_init() failed with -22
[ 6.812023] uvesafb: probe of uvesafb.0 failed with error -22

No idea, how to backtrace this.

[Christian Roessner (christian-roessner-net)]

What about the newer version at:

http://dev.gentoo.org/~spock/projects/uvesafb/

[Roman Yepishev (rye)]

Appeared after trying to fix #246269

Acer Aspire 5520, nVidia GeForce 8400M G, 32 bit Ubuntu Intrepid (current):
Even when no kernel parameters are passed, the screen becomes blank after passing GRUB until GDM starts.
v86d is installed and present in initramfs.

dmesg:

[ 3.282132] v86d[1018]: segfault at 0 ip 08049cd1 sp bfb630c0 error 4 in v86d[8048000+17000]
...
[ 7.657022] uvesafb: Getting VBE info block failed (eax=0x4f00, err=1)
[ 7.657030] uvesafb: vbe_init() failed with -22
[ 7.657040] uvesafb: probe of uvesafb.0 failed with error -22

v86d is the only segfaulted application during startup.

After switching back to ttys from X i get extremely stretched terminal font in 40x24 mode.

Any idea how to emulate v86d kernel call after the boot process?

[iponeverything (cookema)]

I hope that it is not my imagination and I am not sure how they are related, but I have not had v86d segfault on me since applying the fix for Bug #269651. (see post - James Westby, 2008-10-20)

Before this v86d would segfault at once very fresh session. (the lack of v86d didn't affect much, just losing the tail -vf of my logs that I had on tty8 and my virtual consoles.)

[Evgeni Golov (evgeni)]

Is this one still reproducible with current karmic and v86d 0.1.9?

[dino99 (9d9)]

That version has died long ago; no more supported