FreeBSDDesktop / DEPRECATED-freebsd-base-graphics

Fork of FreeBSD's base repository to work on graphics-stack-related projects
Other
49 stars 13 forks source link

glitches and not working linux apps #175

Closed michal800106 closed 6 years ago

michal800106 commented 6 years ago

Hello I have problems with running linux applications on freebsd. I have build system (world and kernel) from drm-next branch.

And for example I have weird glitches in skype4 login window. skype4

And I'm not able to login. I'm not a fan of skype app, but my company uses it and I want to use Freebsd as my main system - in work too.

I have loaded modules as below:

# kldstat
Id Refs Address            Size     Name
 1   50 0xffffffff80200000 1e510c8  kernel
 2    1 0xffffffff82053000 3be8f0   zfs.ko
 3    2 0xffffffff82412000 d3c8     opensolaris.ko
 4    3 0xffffffff82420000 88708    vboxdrv.ko
 5    1 0xffffffff82619000 c3cb     linprocfs.ko
 6    3 0xffffffff82626000 80fc     linux_common.ko
 7    1 0xffffffff8262f000 fda5     tmpfs.ko
 8    1 0xffffffff8263f000 3bc8     ums.ko
 9    2 0xffffffff82643000 2a2f     vboxnetflt.ko
10    2 0xffffffff82646000 ca8f     netgraph.ko
11    1 0xffffffff82653000 4669     ng_ether.ko
12    1 0xffffffff82658000 3f96     vboxnetadp.ko
13    2 0xffffffff8265c000 b09306   nvidia.ko
14    2 0xffffffff83166000 43fe0    linux.ko
15    1 0xffffffff831aa000 b75cf    nvidia-modeset.ko
16    1 0xffffffff83262000 3dff7    linux64.ko

My graphic card:

vgapci0@pci0:1:0:0:     class=0x030000 card=0x84461043 chip=0x11c610de rev=0xa1 hdr=0x00
    vendor     = 'NVIDIA Corporation'
    device     = 'GK106 [GeForce GTX 650 Ti]'
    class      = display
    subclass   = VGA

In dmesg I see some errors:

linux: pid 3790 (skype): syscall inotify_init not implemented
linux: pid 3790 (skype): ioctl fd=33, cmd=0x8b01 ('\M^K',1) is not implemented
linux: pid 3790 (skype): ioctl fd=33, cmd=0x8b01 ('\M^K',1) is not implemented
linux: pid 3790 (skype): ioctl fd=33, cmd=0x8b01 ('\M^K',1) is not implemented
linux: pid 3790 (skype): ioctl fd=33, cmd=0x8b01 ('\M^K',1) is not implemented
linux: pid 3790 (skype): futex stuff in thread_detach failed.
linux: pid 3790 (skype): futex stuff in thread_detach failed.
linux: pid 3790 (skype): ioctl fd=24, cmd=0x8b01 ('\M^K',1) is not implemented
linux: pid 3790 (skype): ioctl fd=24, cmd=0x8b01 ('\M^K',1) is not implemented
linux: pid 3790 (skype): ioctl fd=24, cmd=0x8b01 ('\M^K',1) is not implemented
linux: pid 3790 (skype): ioctl fd=24, cmd=0x8b01 ('\M^K',1) is not implemented
linux: pid 3790 (skype): ioctl fd=24, cmd=0x8b01 ('\M^K',1) is not implemented
linux: pid 3790 (skype): ioctl fd=24, cmd=0x8b01 ('\M^K',1) is not implemented
linux: pid 3790 (skype): ioctl fd=24, cmd=0x8b01 ('\M^K',1) is not implemented
linux: pid 3790 (skype): ioctl fd=24, cmd=0x8b01 ('\M^K',1) is not implemented
lock order reversal:
 1st 0xfffff8004486e490 filedesc structure (filedesc structure) @ /usr/src/sys/kern/kern_descrip.c:1234
 2nd 0xfffff800b00ac068 zfs (zfs) @ /usr/src/sys/kern/vfs_subr.c:5045
stack backtrace:
#0 0xffffffff80acbcf3 at witness_debugger+0x73
#1 0xffffffff80acbb72 at witness_checkorder+0xe02
#2 0xffffffff80a3f44e at lockmgr_lock_fast_path+0x1ae
#3 0xffffffff81020510 at VOP_LOCK1_APV+0xe0
#4 0xffffffff80b44cc6 at _vn_lock+0x66
#5 0xffffffff80a20c69 at knlist_remove_kq+0x99
#6 0xffffffff80b3a8b8 at filt_vfsdetach+0x28
#7 0xffffffff80a2172c at knote_fdclose+0x14c
#8 0xffffffff80a14a85 at closefp+0x65
#9 0xffffffff80ef689b at amd64_syscall+0x79b
#10 0xffffffff80ed522b at Xfast_syscall+0xf
jbeich commented 6 years ago

As of freebsd/freebsd-ports@690be662c5ee this repo is out of date compared to graphics/drm-next-kmod which has #166 fixed. For non-graphical issues better report via bugzilla where you can CC emulation@ if it's related to running Linux apps.

net-im/skype4 was probably "retired" on 2017-07-01 by Microsoft while the new Electron-based client (similar to Chrome) still doesn't work due to missing Linux syscalls. Maybe @xmj knows more.

nomadlogic commented 6 years ago

It's also worth noting that the user is reporting an issue with an Nvidia GPU which isn't part of the work that the drm-next branch is focused on. Closing out this issue as it does not apply to the code in the repo.