Current problem reports assigned to freebsd-emulation@FreeBSD.org
Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description o kern/153990 emulation [hyper-v]: Will not install into Hyper-V on Server 200 o kern/153887 emulation [linux] Linux emulator not understand STB_GNU_UNIQUE b o kern/153243 emulation [ibcs2] Seg fault whne running COFF binary using iBCS2 o ports/151714 emulation print/acroread9 not usable due to lack of support in t a bin/150262 emulation [patch] truss(1) -f doesn't follow descendants of the a kern/150186 emulation [parallels] [panic] Parallels Desktop: CDROM disconnec o kern/149168 emulation [linux] [patch] Linux sendmsg / recvmsg / etc fixes fo o ports/148097 emulation [patch] suggested addition to linux_base-* packages to o ports/148096 emulation emulators/linux_base-* can not be built from ports on o kern/147793 emulation [vmware] [panic] cdrom handling, panic, possible race o kern/146237 emulation [linux] Linux binaries not reading directories mounted f kern/144763 emulation [linux] [panic] Kernel panic when start linux binaries p kern/144584 emulation [linprocfs][patch] bogus values in linprocfs o ports/142837 emulation [patch] emulators/linux_base-* packages fails to insta o kern/140156 emulation [linux] cdparanoia fails to read drive data f kern/138944 emulation [parallels] [regression] Parallels no longer works in o kern/138880 emulation [linux] munmap segfaults after linux_mmap2 stresstest s ports/136321 emulation x11-toolkits/linux-pango: please update linux based po o ports/135337 emulation [PATCH] emulators/linux_base-f10: incorrect bash usage s kern/133144 emulation [linux] linuxulator 2.6 crashes with nvidias libGL.so. o kern/129169 emulation [linux] [patch] Linux Emulation ENOTCONN error using n o kern/126232 emulation [linux] Linux ioctl TCGETS (0x5401) always fails o kern/86619 emulation [linux] linux emulator interacts oddly with cp a kern/72920 emulation [linux]: path prefixing is not done on unix domain s o kern/41543 emulation [patch] [request] easier wine/w23 support o kern/39201 emulation [linux] [patch] ptrace(2) and rfork(RFLINUXTHPN) confu o kern/36952 emulation [patch] [linux] ldd(1) command of linux does not work o kern/21463 emulation [linux] Linux compatability mode should not allow setu o kern/11165 emulation [ibcs2] IBCS2 doesn't work correctly with PID_MAX 29 problems total. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: Call for Testers: VirtualBox 4.0.4
Al 18/02/11 15:17, En/na Bernhard Froehlich ha escrit: Hi Testers. A few of you have probably wondered what happened to our VirtualBox efforts for FreeBSD. Well it took a bit longer then expected and a few problems were found that needed to be resolved first but most of the things are looking fine now and almost all patches have been pushed upstream with 4.0.4 so here we are now. We will continue to work on VirtualBox for FreeBSD and upstream is also very helpful to us but we could need a few more hands to better keep up with the work and especially improve and fix the Guest Additions. So if you want to help please contact us or have a look at our Todo list. This result wouldn't have been possible without the continuous help of the VirtualBox Developers and a lot of people from the FreeBSD community! (names in alphabetical order and probably missed a few, sorry for that!) Hi, I have tested the last 4.0.4 and works fine. Thanks for your efforts ! The only problem I've found is that I can not seem to be able to see all the traffic flowing in a host-only interface. According to the documentation, I would be able to see all the traffic in a vboxnetX itnerface. I tried with linux, with it I'm able to see that all traffic (I have to do an 'ifconfig vboxnet0' by hand before launching the virtual machines connected with the vboxnet0 network) between two virtual machines connected to a vboxnet0 host-only interface. Regards, Gustau ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Panic from linux emulation (flashplugin)
I'm sending this to both stable and emulation lists, but I'm not subscribed to the emulation list so please cc: me there. Hi guys, I'm told this is known but I can't find any information. I'm running the checkout for RELENG_8_2 from Thursday and the issue I'm having on my amd64 Desktop is that every time I play a flash video (my only real use of linux emulation) it causes a kernel panic. This happens in Opera, Firefox, and Chromium. Another user in Freenode's ##freebsd said he is experiencing this too. I've seen nothing mentioned on the freebsd-emulation mailing list. Any thoughts? Thanks, Mark Relevant info: 10:56:08 skeletor:~ uname -a FreeBSD skeletor.feld.me 8.2-RELEASE FreeBSD 8.2-RELEASE #1: Thu Feb 17 13:03:46 CST 2011 r...@mwi1.coffeenet.org:/usr/obj/usr/src/sys/GENERIC amd64 10:57:11 skeletor:~ sudo kldstat Password: Id Refs AddressSize Name 1 53 0x8010 c9fe20 kernel 21 0x80da 24d98snd_hda.ko 34 0x80dc5000 75668sound.ko 41 0x80e3b000 13b98snd_uaudio.ko 51 0x80e4f000 f080 aio.ko 61 0x80e5f000 ffb0 ahci.ko 71 0x80e6f000 52d8 atapicam.ko 81 0x80e75000 d08de0 nvidia.ko 93 0x81b7e000 42558linux.ko 103 0x81bc1000 45ed0vboxdrv.ko 111 0x81e22000 3ee0 linprocfs.ko 122 0x81e26000 28ae vboxnetflt.ko 132 0x81e29000 8d44 netgraph.ko 141 0x81e32000 1532 ng_ether.ko 151 0x81e34000 d0c vboxnetadp.ko 161 0x81e35000 a1c pflog.ko 171 0x81e36000 2bd81pf.ko 181 0x81e62000 a8ea fuse.ko I was running linux-f10-flashplugin10 10.2r152 ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: Can vm_mmap()/vm_map_remove() be called with giant held? (linuxolator dvb patches)
On Sat, Feb 19, 2011 at 07:57:44PM +0200, Kostik Belousov wrote:
On Fri, Feb 18, 2011 at 09:55:42PM +0100, Juergen Lock wrote:
I have finally got back to this and did the style and vm_map_remove()
return value handling fixes, updated the patches in-place:
http://people.freebsd.org/~nox/dvb/linux-dvb.patch
(for head)
http://people.freebsd.org/~nox/dvb/linux-dvb-8.patch
(for 8.)
On Sun, Jan 30, 2011 at 12:54:48AM +0100, Juergen Lock wrote:
On Sat, Jan 29, 2011 at 10:51:05PM +0200, Kostik Belousov wrote:
On Sat, Jan 29, 2011 at 09:10:00PM +0100, Juergen Lock wrote:
Hi!
I was kinda hoping to be able to post a correct patch in public but
getting an answer to ${Subject} seems to be more difficult than I
thought... :) So, does anyone here know? copyout_map() and
You do not need Giant locked for vm_map* functions.
The question was more do I need to drop it first before calling them...
copyout_unmap() are copied from ksyms_map() from sys/dev/ksyms/ksyms.c
- should there maybe be global versions instead of two static copies
each, and what would be good names? And giant is taken by
linux_ioctl()
Would you make a patch for this ?
Heh if you want me to... Where should they go and are my name choices
ok?
I haven't done this yet so people can keep patching linux.ko in-place
without having to build a new kernel too...
Separate build of linux.ko is not quite supported action. I would greatly
prefer to have the move of these two functions before the rest of the
patch comes in. Together with conversion of other users.
I propose to put it into vm/vm_glue.c.
Ok, new patches are here:
http://people.freebsd.org/~nox/dvb/linux-dvb-2nd.patch
(for head, also copied below)
http://people.freebsd.org/~nox/dvb/linux-dvb-2nd-8.patch
(for 8.)
in the same source file before calling the parts I added. So here
comes the patch, it is to add support for dvb ioctls to the
linuxolator
as discussed on -emulation earlier in this thread:
http://lists.freebsd.org/pipermail/freebsd-multimedia/2011-January/011575.html
(patch also at:
http://people.freebsd.org/~nox/dvb/linux-dvb.patch
and a version for 8, which is what I tested with w_scan on dvb-s2
and dvb-t, and Andrew Gallatin also tested it with SageTV:
http://people.freebsd.org/~nox/dvb/linux-dvb-8.patch
)
+ /*
+ * Map somewhere after heap in process memory.
+ */
+ PROC_LOCK(td-td_proc);
+ *addr = round_page((vm_offset_t)vms-vm_daddr +
+ lim_max(td-td_proc, RLIMIT_DATA));
+ PROC_UNLOCK(td-td_proc);
Are you sure that this is needed ? Why not leave the address selection
to the VM ?
I don't know, maybe sys/dev/ksyms/ksyms.c has a reason?
How would I leave the address selection to the VM? Just trying
to initialize *addr to (vm_offset_t)NULL there caused the patch to
stop working.
I believe you should do
*addr = 0;
vm_mmap(map, addr);
vm_mmap() needs more args, but other than that thats basically what I
tested, and it didn't work.
Thanx, :)
Juergen
And here comes the patch for head:
Index: src/sys/vm/vm_extern.h
===
RCS file: /home/scvs/src/sys/vm/vm_extern.h,v
retrieving revision 1.99
diff -u -p -r1.99 vm_extern.h
--- src/sys/vm/vm_extern.h 27 Dec 2010 07:12:22 - 1.99
+++ src/sys/vm/vm_extern.h 20 Feb 2011 17:15:42 -
@@ -83,16 +79,16 @@ void vmspace_exitfree(struct proc *);
void vnode_pager_setsize(struct vnode *, vm_ooffset_t);
int vslock(void *, size_t);
void vsunlock(void *, size_t);
void vm_object_print(/* db_expr_t */ long, boolean_t, /* db_expr_t */ long,
char *);
int vm_fault_quick(caddr_t v, int prot);
struct sf_buf *vm_imgact_map_page(vm_object_t object, vm_ooffset_t offset);
void vm_imgact_unmap_page(struct sf_buf *sf);
void vm_thread_dispose(struct thread *td);
int vm_thread_new(struct thread *td, int pages);
void vm_thread_swapin(struct thread *td);
void vm_thread_swapout(struct thread *td);
+int copyout_map(struct thread *td, vm_offset_t *addr, size_t sz);
+int copyout_unmap(struct thread *td, vm_offset_t addr, size_t sz);
#endif /* _KERNEL */
#endif /* !_VM_EXTERN_H_ */
Index: src/sys/vm/vm_glue.c
===
RCS file: /home/scvs/src/sys/vm/vm_glue.c,v
retrieving revision 1.248
diff -u -p -r1.248 vm_glue.c
--- src/sys/vm/vm_glue.c9 Jan 2011 12:50:44 - 1.248
+++ src/sys/vm/vm_glue.c20 Feb 2011 17:23:48 -
@@ -81,6 +81,7 @@ __FBSDID($FreeBSD: src/sys/vm/vm_glue.c
#include sys/kernel.h
#include sys/ktr.h
#include
Re: Call for Testers: VirtualBox 4.0.4
I am not sure if this is a general bug in vbox or FreeBSD specific: When some previous snapshot is being deleted through the GUI and progress dialog is up, my Solaris VM window doesn't get mouse events. After deletion was done and I clicked on the tabs of the terminal in the VM, X-server there crashed. Yuri ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: Panic from linux emulation (flashplugin)
In article op.vq9kcoyl34t2sn@tech304 you write: I'm sending this to both stable and emulation lists, but I'm not subscribed to the emulation list so please cc: me there. Hi guys, I'm told this is known but I can't find any information. I'm running the checkout for RELENG_8_2 from Thursday and the issue I'm having on my amd64 Desktop is that every time I play a flash video (my only real use of linux emulation) it causes a kernel panic. This happens in Opera, Firefox, and Chromium. Another user in Freenode's ##freebsd said he is experiencing this too. I've seen nothing mentioned on the freebsd-emulation mailing list. Any thoughts? Well it works for me, just tested with native ff, linux ff and linux opera... (other than youtube seems to be overloaded at this time, videos pause a lot.) Thanks, Mark Relevant info: 10:56:08 skeletor:~ uname -a FreeBSD skeletor.feld.me 8.2-RELEASE FreeBSD 8.2-RELEASE #1: Thu Feb 17 13:03:46 CST 2011 r...@mwi1.coffeenet.org:/usr/obj/usr/src/sys/GENERIC amd64 10:57:11 skeletor:~ sudo kldstat Password: Id Refs AddressSize Name 1 53 0x8010 c9fe20 kernel 21 0x80da 24d98snd_hda.ko 34 0x80dc5000 75668sound.ko 41 0x80e3b000 13b98snd_uaudio.ko 51 0x80e4f000 f080 aio.ko 61 0x80e5f000 ffb0 ahci.ko 71 0x80e6f000 52d8 atapicam.ko 81 0x80e75000 d08de0 nvidia.ko 93 0x81b7e000 42558linux.ko 103 0x81bc1000 45ed0vboxdrv.ko 111 0x81e22000 3ee0 linprocfs.ko 122 0x81e26000 28ae vboxnetflt.ko 132 0x81e29000 8d44 netgraph.ko 141 0x81e32000 1532 ng_ether.ko 151 0x81e34000 d0c vboxnetadp.ko 161 0x81e35000 a1c pflog.ko 171 0x81e36000 2bd81pf.ko 181 0x81e62000 a8ea fuse.ko I was running linux-f10-flashplugin10 10.2r152 I see you use the nvidia blob (I use radeon with xorg drivers), did you rebuild the nvidia driver port after upgrading to 8.2? Or maybe this has something to do with the vdpau support that was added to flash with the last update and that others reported as possibly not working properly on FreeBSD... If you did rebuild nvidia try mv.ing /compat/linux/usr/lib/libvdpau.so.1 away temporarily and see if that fixes the panics, if yes its probably an nvidia issue. And even if not I guess you need to collect a backtrace or at least a textdump of the panic, see here about how to get a dump: http://www.freebsd.org/doc/en/books/developers-handbook/book.html#KERNELDEBUG-OBTAIN If the dumping/savecore/crashinfo script worked you should get a new /var/crash/core.txt.X file with the backtrace (among other things) after the next boot. Good luck, :) Juergen ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: Panic from linux emulation (flashplugin)
On Mon, 21 Feb 2011 13:24:25 -0600, Juergen Lock n...@jelal.kn-bremen.de wrote: I see you use the nvidia blob (I use radeon with xorg drivers), did you rebuild the nvidia driver port after upgrading to 8.2? Or maybe this has something to do with the vdpau support that was added to flash with the last update and that others reported as possibly not working properly on FreeBSD... Aha! This is probably it! I just upgraded my workstation at work to 8.2 (also nvidia) and I am not having the crash but I also don't have that newer flash version that includes vdpau support. I will downgrade the flash version at home and report back. It would possibly also be wise to contact the maintainer and have him mark the port as BROKEN or conflicting or something if you're running nvidia so people don't run into this issue. Thanks, Mark ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: Panic from linux emulation (flashplugin)
On Mon, Feb 21, 2011 at 02:48:19PM -0600, Mark Felder wrote: On Mon, 21 Feb 2011 13:24:25 -0600, Juergen Lock n...@jelal.kn-bremen.de wrote: I see you use the nvidia blob (I use radeon with xorg drivers), did you rebuild the nvidia driver port after upgrading to 8.2? Or maybe this has something to do with the vdpau support that was added to flash with the last update and that others reported as possibly not working properly on FreeBSD... Aha! This is probably it! I just upgraded my workstation at work to 8.2 (also nvidia) and I am not having the crash but I also don't have that newer flash version that includes vdpau support. I will downgrade the flash version at home and report back. So on the box that got the panic the nvidia driver port was rebuilt after the src/kernel upgrade? It would possibly also be wise to contact the maintainer and have him mark the port as BROKEN or conflicting or something if you're running nvidia so people don't run into this issue. The maintainer is emulation@... :) But yes if its confirmed and can't be fixed we should probably patch the flash binary to stop it from trying to load libvdpau (like by patching the filename to something nonexisting?) Juergen ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: Panic from linux emulation (flashplugin)
On Mon, 21 Feb 2011 16:39:49 -0600, Juergen Lock n...@jelal.kn-bremen.de wrote: So on the box that got the panic the nvidia driver port was rebuilt after the src/kernel upgrade? Correct. The maintainer is emulation@... But yes if its confirmed and can't be fixed we should probably patch the flash binary to stop it from trying to load libvdpau (like by patching the filename to something nonexisting?) I was talking about the maintainer of the flashplugin in ports. That would be Nox. I have sent him an email. Regards, Mark ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: Panic from linux emulation (flashplugin)
On Mon, 21 Feb 2011 16:42:59 -0600, Mark Felder f...@feld.me wrote: I was talking about the maintainer of the flashplugin in ports. That would be Nox. I have sent him an email. Oh dear I take that back. He was the last person to submit an update, not the maintainer. Whoops! Mark ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
