Re: SOLVED :-) Re: Wierd time changes
Mark, No clue from sysctl -a. Yes, I've looked through archives and google. Since I don't see a lot of performance improvement from using the second CPU, I will leave this issue alone for now. Hopefully, someone will post a sweet solution to this bugging issue. Thanks for your help, Denis > Only to try with different value for kern.timecounter.method, but that's > just a guess. Does the output from ''sysctl -a kern.timecounter'' yield > any clues? > > Apart from that I really can't be of any help. I take it you've done the > obvious and searched the mailing list and Google? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SOLVED :-) Re: Wierd time changes
Denis R. wrote: Hi Mark! Gee, who would have thought that it was the keyboard. Thanks for your ideas. I recompiled the kernel (Compaq SP700 dual PII-450) following the NOTES guidelines and your email, with these enabled: # To make an SMP kernel, the next two are needed options SMP # Symmetric MultiProcessor Kernel device apic# I/O APIC options NO_MIXED_MODE options BROKEN_KEYBOARD_RESET options EISA_SLOTS=12 and in /boot/loader.conf kern.timecounter.method=1 I still got the broken time (10 second test lasts 22 seconds). The server also hung upon the 'reboot' command while releasing the CPU1. Since it is I had that (hanging) at one point; IIRC it was NO_MIXED_MODE that caused it. a production server, I switched back to my single CPU kernel. If you have any other suggestions, I'd appreciate the input. Only to try with different value for kern.timecounter.method, but that's just a guess. Does the output from ''sysctl -a kern.timecounter'' yield any clues? Apart from that I really can't be of any help. I take it you've done the obvious and searched the mailing list and Google? Regards, Mark Thanks, Denis I've solved it and I bet you can't guess what it was - it was the fscking keyboard!!! After spending the last 8 hours building kernels (about 20) with unnecessary stuff removed and trying various options documented in /sys/i386/conf/NOTES I finally nailed it down. What made me wonder was a kernel option BROKEN_KEYBOARD_RESET ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
re: SOLVED :-) Re: Wierd time changes
Hi Mark! Gee, who would have thought that it was the keyboard. Thanks for your ideas. I recompiled the kernel (Compaq SP700 dual PII-450) following the NOTES guidelines and your email, with these enabled: # To make an SMP kernel, the next two are needed options SMP # Symmetric MultiProcessor Kernel device apic# I/O APIC options NO_MIXED_MODE options BROKEN_KEYBOARD_RESET options EISA_SLOTS=12 and in /boot/loader.conf kern.timecounter.method=1 I still got the broken time (10 second test lasts 22 seconds). The server also hung upon the 'reboot' command while releasing the CPU1. Since it is a production server, I switched back to my single CPU kernel. If you have any other suggestions, I'd appreciate the input. Thanks, Denis >>> I've solved it and I bet you can't guess what it was - it was the fscking keyboard!!! After spending the last 8 hours building kernels (about 20) with unnecessary stuff removed and trying various options documented in /sys/i386/conf/NOTES I finally nailed it down. What made me wonder was a kernel option BROKEN_KEYBOARD_RESET ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
