Re: MAGIC with HP KVM - someone will help?
Nop, sorry. I don't use KVMs. Perhaps the PS2 to USB converter is doing something bad. that was my first idea BUT: 1) i know for a friend that on some motherboards (it was embedded VIA based CPU) geli doesn't work at typing password. 2) in my case (as well as his case) problems happen everytime kernel function cngets is used, it maybe after being unable to mount root in a kernel prompt. The problem IS FreeBSD specific AND some hardware specific. this seems like an interaction between FreeBSD and some hardware (timings?). Really have no idea. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: MAGIC with HP KVM - someone will help?
100% HIT! yes i have on of those that have PS/2 reset issues On Fri, 22 Jun 2012, Mark Felder wrote: On Wed, 20 Jun 2012 01:14:09 -0500, Wojciech Puchar woj...@wojtek.tensor.gdynia.pl wrote: As this KVM have PS/2 connectors to keyboard and mouse i added USB to dual-PS/2 converter. http://geekhack.org/showwiki.php?title=PS2-to-USB+adapters You probably have a ps/2 converter that's known to be super buggy ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: Fast syscalls via sysenter
On 2012/06/21 20:11, John Baldwin wrote: On Monday, June 18, 2012 2:56:30 pm Daniil Cherednik wrote: Hi! I am trying to continue the work started by DavidXu on implemention of fast syscalls via sysenter/sysexit. http://people.freebsd.org/~davidxu/sysenter/kernel/ I have ported it on FreeBSD9. It looks like it works. Unfortunately I am a beginner in kernel so I have some questions: 1. see http://people.freebsd.org/~davidxu/sysenter/kernel/kernel.patch /* * If %edx was changed, we can not use sysexit, because it * needs %edx to restore userland %eip. */ if (orig_edx != frame.tf_edx) td-td_pcb-pcb_flags |= PCB_FULLCTX; What is the reason why we have to do this additional check? In http://people.freebsd.org/~davidxu/sysenter/kernel/sysenter.s we store %edx to the stack in pushl %edx /* ring 3 next %eip */ and we restore the register in popl%edx/* ring 3 %eip */ Some system calls return two return values (pipe(2)) or return a 64-bit off_t (lseek(2)). Those system calls change %edx's value and need that changed value to make it out to userland. 2. see http://people.freebsd.org/~davidxu/sysenter/kernel/sysenter.s movlPCPU(CURPCB),%esi callsyscall Why do we movl PCPU(CURPCB),%esi before calling syscall? syscall is just c- function. No clue on this one, looks like it is not needed. [kib@ is cc'ed] I implemented the sysenter syscall long time ago, it indeed can reduce system call overhead on i386. I think it might be the time to implement linux like vdso syscall now based on the work kib@ recently has done, though I don''t know how to hook it into kib's code. I quick googled it, and found they put some data into aux vector: http://www.trilithium.com/johan/2005/08/linux-gate/ http://www.takatan.net/lxr/source/arch/um/os-Linux/elf_aux.c?a=x86_64#L40 Regards, David Xu ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: MAGIC with HP KVM - someone will help?
On Jun 23, 2012 7:04 AM, Wojciech Puchar woj...@wojtek.tensor.gdynia.pl wrote: 100% HIT! yes i have on of those that have PS/2 reset issues Unfortunately even good adaptors have their share of problems. I refuse to move from the keyboard I have currently, and occasionally keys get 'stuck' but it's so obvious when it happens it's no big hardship. I have a Belkin adaptor one by the way, and it works very well with FreeBSD apart from that issue, if that's any help. Chris ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: MAGIC with HP KVM - someone will help?
yes i have on of those that have PS/2 reset issues Unfortunately even good adaptors have their share of problems. as for now i already planned to rearrange boot sequence of this server and /etc/rc so network would be temporarily up and sshd active until i log in and geli attach needed devices. I refuse to move from the keyboard I have currently, and occasionally keys get 'stuck' but it's so obvious when it happens it's no big hardship. I have a Belkin adaptor one by the way, and it works but the PROBABLY FReeBSD specific is that some configuration, not only USB to PS/2 adapters, have problems only when kernel cngets routine. my friend switched to linux, in spite of lower performance, on his dedicated fileserver machine with VIA processor, only because keyboard didn't work when geli asked for password at boot, or - for whatever reason - in kernel command prompt activated. it works every other case properly. I would like to help fixing a problem, but not even have idea how. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: MAGIC with HP KVM - someone will help?
At 17:09 23/06/2012, you wrote: my friend switched to linux, in spite of lower performance, on his dedicated fileserver machine with VIA processor, only because keyboard didn't work when geli asked for password at boot, or - for whatever reason - in kernel command prompt activated. I don't know but here you have another idea, perhaps geli asks for password and stops boot sequence before the usb stack is loaded and keyboard is recognized. it works every other case properly. I would like to help fixing a problem, but not even have idea how. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: MAGIC with HP KVM - someone will help?
I don't know but here you have another idea, perhaps geli asks for password and stops boot sequence before the usb stack is loaded and keyboard is recognized. no. it is recognized and keyboard. in my case - keyboard works but if i type too fast (which is faster than about one key per second ;) it stops working it works every other case properly. I would like to help fixing a problem, but not even have idea how. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: MAGIC with HP KVM - someone will help?
Wojciech writes: 1) i know for a friend that on some motherboards (it was embedded VIA based CPU) geli doesn't work at typing password. 2) in my case (as well as his case) problems happen everytime kernel function cngets is used, it maybe after being unable to mount root in a kernel prompt. The problem IS FreeBSD specific AND some hardware specific. this seems like an interaction between FreeBSD and some hardware (timings?). Really have no idea. I refuse to move from the keyboard I have currently, and occasionally keys get 'stuck' but it's so obvious when it happens it's no big hardship. I have a Belkin adaptor one by the way, and it works but the PROBABLY FReeBSD specific is that some configuration, not only USB to PS/2 adapters, have problems only when kernel cngets routine. my friend switched to linux, in spite of lower performance, on his dedicated fileserver machine with VIA processor, only because keyboard didn't work when geli asked for password at boot, or - for whatever reason - in kernel command prompt activated. it works every other case properly. This reminds me of a problem I have when using a RS-232 console. When the loader is sitting there waiting for a few seconds to see if you will type something, it doesn't always notice keystrokes. I would have to hold the key down (letting it autorepeat) and then it would usually notice. This problem does not happen with the PS/2 keyboard. (no KVM, no USB adapters) If it is a timing problem, perhaps it is related? ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: Fast syscalls via sysenter
On Sat, Jun 23, 2012 at 02:17:53PM +0800, David Xu wrote: On 2012/06/21 20:11, John Baldwin wrote: On Monday, June 18, 2012 2:56:30 pm Daniil Cherednik wrote: Hi! I am trying to continue the work started by DavidXu on implemention of fast syscalls via sysenter/sysexit. http://people.freebsd.org/~davidxu/sysenter/kernel/ I have ported it on FreeBSD9. It looks like it works. Unfortunately I am a beginner in kernel so I have some questions: 1. see http://people.freebsd.org/~davidxu/sysenter/kernel/kernel.patch /* * If %edx was changed, we can not use sysexit, because it * needs %edx to restore userland %eip. */ if (orig_edx != frame.tf_edx) td-td_pcb-pcb_flags |= PCB_FULLCTX; What is the reason why we have to do this additional check? In http://people.freebsd.org/~davidxu/sysenter/kernel/sysenter.s we store %edx to the stack in pushl %edx /* ring 3 next %eip */ and we restore the register in popl%edx/* ring 3 %eip */ Some system calls return two return values (pipe(2)) or return a 64-bit off_t (lseek(2)). Those system calls change %edx's value and need that changed value to make it out to userland. 2. see http://people.freebsd.org/~davidxu/sysenter/kernel/sysenter.s movlPCPU(CURPCB),%esi callsyscall Why do we movl PCPU(CURPCB),%esi before calling syscall? syscall is just c- function. No clue on this one, looks like it is not needed. [kib@ is cc'ed] I implemented the sysenter syscall long time ago, it indeed can reduce system call overhead on i386. I think it might be the time to implement linux like vdso syscall now based on the work kib@ recently has done, though I don''t know how to hook it into kib's code. I quick googled it, and found they put some data into aux vector: http://www.trilithium.com/johan/2005/08/linux-gate/ http://www.takatan.net/lxr/source/arch/um/os-Linux/elf_aux.c?a=x86_64#L40 Yes, intent is to eventually switch to VDSO from current situation were libc is aware of shared page content. This was extensively discussed in flame that resulted in me writing the current gettimeofday(2) patch. It was arch@ several weeks ago, AFAIR. Committed gettimeofday() code structure allows for VDSO interposing without breaking normal symbol visibility rules. I do not see a sense in implementing syscall or sysenter support for i386 kernel. On the other hand, using syscall for 32bit binaries on amd64 looks reasonable. pgp459emKisb7.pgp Description: PGP signature
Re: tcsh's exit codes
rank1see...@gmail.com wrote: There is something wrong with tcsh shell: # mergemaster -V | grep '\--run-updates' Returned exit code 1 # mergemaster -V | grep -q '\--run-updates' Returned exit code 141 I believe this has been a feature of csh and tcsh since the dark ages. Negative status codes propagate through pipelines (and through backtick sub-commands as well). In fact the returned $status value is the value of the last command that returned an error (non-zero) status code. This makes it easy to determine if a pipeline command sequence has failed. The 141 status code indicates a sigpipe: the pipeline was not completely read (as described in the grep manual for this case). This also is the common exit code when using head(1) for example. This error-propagation behaviour can be suppessed with 'unset anyerror' in tcsh. In that case it should work as you expect. But note that your commands are no longer compatible with 'good old' csh behaviour then. Regards, Johan pgpPINcqryZSe.pgp Description: PGP signature
Re: MAGIC with HP KVM - someone will help?
This reminds me of a problem I have when using a RS-232 console. When the loader is sitting there waiting for a few seconds to see if you will type something, it doesn't always notice keystrokes. I would have to hold the key down (letting it autorepeat) and then it would usually notice. This problem does not happen with the PS/2 keyboard. (no KVM, no USB adapters) If it is a timing problem, perhaps it is related? probably not. keyboard workd in loader perfectly. As well as it works perfectly after mounting root ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
