Re: AuthenticAMD, cpufreq and SunFire X2200
On Fri, Jul 11, 2008 at 11:05:36PM +0300, Danny Braniss wrote: no AMD datasheets, but here goes acpidump: I think we need more than the dump of the tables. Try acpidump -dt. it was a acpidump -dt, but now I also notice: acpidump -dt /tmp/acpi acpidump: RSDT entry 3 (sig OEMB) is corrupt iasl tmp file (read): No such file or directory RTFM! or read the error message :-) It seems that acpidump writes in the current directory (but does not complain if it fails) but does complain when it can't read! I was running as root, but from my NFS mounted home dir. anyways, this one is slightly bigger: ftp://ftp.cs.huji.ac.il/users/danny/freebsd/x2200.asl cheers, danny ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: AMD Geode LX crypto accelerator (glxsb) - invalid engine cryptodev
Hello, I'm having trouble with the OpenSSL benchmark. It isn't able to load cryptodev. Output attached. Any pointers? Thanks. - Tom$ openssl speed -engine cryptodev -elapsed -evp aes-128-cbc aes-128-cbc invalid engine cryptodev 11286:error:25066067:DSO support routines:DLFCN_LOAD:could not load the shared library:/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/dso/dso_dlfcn.c:162:filename(/usr/lib/engines/libcryptodev.so): Cannot open /usr/lib/engines/libcryptodev.so 11286:error:25070067:DSO support routines:DSO_load:could not load the shared library:/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/dso/dso_lib.c:244: 11286:error:260B6084:engine routines:DYNAMIC_LOAD:dso not found:/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/engine/eng_dyn.c:450: 11286:error:2606A074:engine routines:ENGINE_by_id:no such engine:/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/engine/eng_list.c:415:id=cryptodev 11286:error:25066067:DSO support routines:DLFCN_LOAD:could not load the shared library:/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/dso/dso_dlfcn.c:162:filename(libcryptodev.so): Shared object libcryptodev.so not found, required by openssl 11286:error:25070067:DSO support routines:DSO_load:could not load the shared library:/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/dso/dso_lib.c:244: 11286:error:260B6084:engine routines:DYNAMIC_LOAD:dso not found:/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/engine/eng_dyn.c:450: You have chosen to measure elapsed time instead of user CPU time. To get the most accurate results, try to run this program when this computer is idle. Doing aes-128 cbc for 3s on 16 size blocks: 981606 aes-128 cbc's in 3.00s Doing aes-128 cbc for 3s on 64 size blocks: 258602 aes-128 cbc's in 3.00s Doing aes-128 cbc for 3s on 256 size blocks: 65471 aes-128 cbc's in 3.00s Doing aes-128 cbc for 3s on 1024 size blocks: 16451 aes-128 cbc's in 3.00s Doing aes-128 cbc for 3s on 8192 size blocks: 2058 aes-128 cbc's in 3.00s Doing aes-128-cbc for 3s on 16 size blocks: 913121 aes-128-cbc's in 3.00s Doing aes-128-cbc for 3s on 64 size blocks: 249883 aes-128-cbc's in 3.00s Doing aes-128-cbc for 3s on 256 size blocks: 64875 aes-128-cbc's in 3.00s Doing aes-128-cbc for 3s on 1024 size blocks: 16367 aes-128-cbc's in 3.00s Doing aes-128-cbc for 3s on 8192 size blocks: 2058 aes-128-cbc's in 3.00s OpenSSL 0.9.8e 23 Feb 2007 built on: Sun Feb 24 16:11:39 UTC 2008 options:bn(64,32) md2(int) rc4(idx,int) des(ptr,risc1,16,long) aes(partial) blowfish(idx) compiler: cc available timing options: USE_TOD HZ=128 [sysconf value] timing function used: gettimeofday The 'numbers' are in 1000s of bytes per second processed. type 16 bytes 64 bytes256 bytes 1024 bytes 8192 bytes aes-128 cbc 5234.72k 5516.54k 5586.44k 5614.71k 5617.06k aes-128-cbc 4868.70k 5330.56k 5535.58k 5586.03k 5617.14k $ uname -a FreeBSD router.local 7.0-RELEASE-p2 FreeBSD 7.0-RELEASE-p2 #0: Wed Jun 18 07:33:20 UTC 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 $ openssl engine (padlock) VIA PadLock (no-RNG, no-ACE) (dynamic) Dynamic engine loading support $ dmesg |grep glx glxsb0: AMD Geode LX Security Block (AES-128-CBC,RNG) mem 0xefff4000-0xefff7fff irq 9 at device 1.2 on pci0 $ kldstat Id Refs AddressSize Name 16 0xc040 906578 kernel 21 0xc2553000 3000 pflog.ko 31 0xc2556000 33000pf.ko 41 0xc2e07000 5000 glxsb.ko 51 0xc2e0c000 23000crypto.ko 61 0xc2e2f000 a000 zlib.ko ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: AMD Geode LX crypto accelerator (glxsb) - invalid engine cryptodev
-On [20080712 21:28], tomrapier ([EMAIL PROTECTED]) wrote:
I'm having trouble with the OpenSSL benchmark. It isn't able to load
cryptodev. Output attached.
Any pointers?
$ kldstat
Id Refs AddressSize Name
16 0xc040 906578 kernel
21 0xc2553000 3000 pflog.ko
31 0xc2556000 33000pf.ko
41 0xc2e07000 5000 glxsb.ko
51 0xc2e0c000 23000crypto.ko
61 0xc2e2f000 a000 zlib.ko
How about: kldload cryptodev?
[21:30] [EMAIL PROTECTED] (0) {0} % sudo kldload cryptodev
Password:
(~)
[21:31] [EMAIL PROTECTED] (0) {0} % openssl speed -engine cryptodev -elapsed
-evp aes-128-cbc aes-128-cbc
engine cryptodev set.
You have chosen to measure elapsed time instead of user CPU time.
To get the most accurate results, try to run this
program when this computer is idle.
Doing aes-128 cbc for 3s on 16 size blocks: 7539390 aes-128 cbc's in 3.00s
--
Jeroen Ruigrok van der Werven asmodai(-at-)in-nomine.org / asmodai
イェルーン ラウフロック ヴァン デル ウェルヴェン
http://www.in-nomine.org/ | http://www.rangaku.org/ | GPG: 2EAC625B
Yet each man kills the thing he loves...
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: AMD Geode LX crypto accelerator (glxsb) - invalid engine cryptodev
On 12-Jul-2008 21:35:54 +0200, you wrote: -On [20080712 21:28], tomrapier ([EMAIL PROTECTED]) wrote: I'm having trouble with the OpenSSL benchmark. It isn't able to load cryptodev. Output attached. Any pointers? $ kldstat Id Refs AddressSize Name 16 0xc040 906578 kernel 21 0xc2553000 3000 pflog.ko 31 0xc2556000 33000pf.ko 41 0xc2e07000 5000 glxsb.ko 51 0xc2e0c000 23000crypto.ko 61 0xc2e2f000 a000 zlib.ko How about: kldload cryptodev? Great, that fixed it. - Tom___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Re: Hardware support for AMD Geode CS5536 audio?
Bruce, This is Andrew Gray. I am running an Alix-1C board with the CS5536 on it. This board is very nice. It's only about $138 and it has a good standard clone AWARD bios that we are all used to (unlike say, the Soekris boards). It uses only 5 watts and has everthing including 21 GPIO pins. (except is doesn't have a Freebsd sound driver yet. Also 3.3V SB audigy SB0090 PCI sound cards don't seem to work in its 3.3V PCI slot). It has serial ports (COM1 2) for debug and it has plenty of RAM. It runs at 500 Mhz, so it is fast enough to compile a sound driver. (It takes about 20 seconds). It has a 44-pin laptop IDE interface (ribbon cable has smaller spacing), so you need a 44 pin to 40 pin adapter cable if you want to run a regular HD, and you must power the regular hard drive from SOME OTHER power supply. ALternatively, you can put a 4 meg compact flash in its bay, and just use it as a flash HD. This works fine: http://www.mini-box.com/Alix-1C-Board-1-LAN-1-MINI-PCI?sc=8category=754 A question for you? Do Freebsd 4.6 drivers still work on freebsd 6.2 and 7.0? Are you working on this CS5536 driver? Do you have hardware yet? Andrew Gray ancelgray AT y a h o o dot c o m -- This message was sent on behalf of [EMAIL PROTECTED] at openSubscriber.com http://www.opensubscriber.com/message/freebsd-hackers@freebsd.org/8451180.html ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Help with copytree code
On Sun, 6 Jul 2008 13:26:21 -0800 Beech Rintoul [EMAIL PROTECTED] mentioned: I'd just like to thank stas@ and everyone who replied with suggestions, code etc. I believe that I now have something workable and it's been submitted to portmgr for review and possible inclusion in bsd.port.mk along with some new features of my own. Hopefully, this will fix a long standing problem with copytree_*. Have you filled the PR so we could review/comment? -- Stanislav Sedov ST4096-RIPE ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Pls sanity check my semtimedop(2) implementation
Hi,
Below is a semtimedop(2) implementation that I'm using for FreeBSD. I
was hoping someone could look it over and tell me if they think the
implementation is sound.
The code seems to work ok but when stressing the FreeBSD build of my app
I have managed to provoke errors related to concurrency (usually when a
SIGALRM goes off). The Linux build works flawlessesly so I'm wondering
about this one critical function that is different.
Do you think it would make any difference if I used
ITIMER_VIRTUAL / SIGVTALRM instead of ITIMER_REAL / SIGALRM?
Or perhaps I should be using a different implementation entirely?
Mike
int
_semtimedop(int semid,
struct sembuf *array,
size_t nops,
struct timespec *_timeout)
{
struct timeval timeout, before, after;
struct itimerval value, ovalue;
struct sigaction sa, osa;
int ret;
if (_timeout) {
timeout.tv_sec = _timeout-tv_sec;
timeout.tv_usec = _timeout-tv_nsec / 1000;
if (gettimeofday(before, NULL) == -1) {
return -1;
}
memset(value, 0, sizeof value);
value.it_value = timeout;
memset(sa, 0, sizeof sa);
/* signal_print writes the signal info to a log file
*/
sa.sa_sigaction = signal_print;
sa.sa_flags = SA_SIGINFO;
sigemptyset(sa.sa_mask);
sigaction(SIGALRM, sa, osa);
if (setitimer(ITIMER_REAL, value, ovalue) == -1) {
sigaction(SIGALRM, osa, NULL);
return -1;
}
}
ret = semop(semid, array, nops);
if (_timeout) {
sigaction(SIGALRM, osa, NULL);
if (setitimer(ITIMER_REAL, ovalue, NULL) == -1) {
return -1;
}
}
if (ret == -1) {
if (_timeout) {
struct timeval elapsed;
if (gettimeofday(after, NULL) == -1) {
return -1;
}
_timeval_diff(after, before, elapsed);
if (timercmp(elapsed, timeout, =))
errno = EAGAIN;
}
return -1;
}
return 0;
}
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Help with copytree code
On Saturday 12 July 2008, Stanislav Sedov said: On Sun, 6 Jul 2008 13:26:21 -0800 Beech Rintoul [EMAIL PROTECTED] mentioned: I'd just like to thank stas@ and everyone who replied with suggestions, code etc. I believe that I now have something workable and it's been submitted to portmgr for review and possible inclusion in bsd.port.mk along with some new features of my own. Hopefully, this will fix a long standing problem with copytree_*. Have you filled the PR so we could review/comment? No, portmgr (Pav) has it and is reviewing. I'll chat with him and see if he wants me to file a pr. Meanwhile I'll be happy to send it to anyone who wants it. The FreeBSD server will just strip it off and I'm moving webservers today so I can't post it for a while. Beech -- --- Beech Rintoul - FreeBSD Developer - [EMAIL PROTECTED] /\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://www.freebsd.org X - NO Word docs in e-mail | Latest Release: / \ - http://www.FreeBSD.org/releases/7.0R/announce.html --- ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
SCHED_4BSD bad interactivity on 7.0 vs 6.3
Hi folks, Hopefully this is a good list for this topic. It seems like there has been a regression in interactivity from 6.3-RELEASE to 7.0-RELEASE when using the SCHED_4BSD scheduler. After upgrading my single-cpu amd64 box, 7.0 has much worse latency. When running a kernel compile, there is a noticeable lag to echo my typing or scroll my browser windows, and playing an mp3 frequently cuts out for a second or two. This did not happen on 6.3-RELEASE. I wrote a small program which forks two processes that run gettimeofday() in a tight loop to see how long they get scheduled out. On 6.3 the maximum latency is usually under 100 ms. On 7.0 it is 500 ms or more even when nothing else is running on the system. When a compile is also running it is sometimes 1400 ms or more. SCHED_ULE is much better, so I've switched over. But it's not the default yet, and most people are still going to be using SCHED_4BSD. It used to be acceptable but now it isn't. Does anyone know why it's regressed so badly? -- Nate Eldredge [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SCHED_4BSD bad interactivity on 7.0 vs 6.3
Nate Eldredge wrote: Hi folks, Hopefully this is a good list for this topic. It seems like there has been a regression in interactivity from 6.3-RELEASE to 7.0-RELEASE when using the SCHED_4BSD scheduler. After upgrading my single-cpu amd64 box, 7.0 has much worse latency. When running a kernel compile, there is a noticeable lag to echo my typing or scroll my browser windows, and playing an mp3 frequently cuts out for a second or two. This did not happen on 6.3-RELEASE. Are you sure it's not the x.org server bug that was present in the version shipped with 7.0? Update to the latest version and see if your X interactivity improves. Kris I wrote a small program which forks two processes that run gettimeofday() in a tight loop to see how long they get scheduled out. On 6.3 the maximum latency is usually under 100 ms. On 7.0 it is 500 ms or more even when nothing else is running on the system. When a compile is also running it is sometimes 1400 ms or more. SCHED_ULE is much better, so I've switched over. But it's not the default yet, and most people are still going to be using SCHED_4BSD. It used to be acceptable but now it isn't. Does anyone know why it's regressed so badly? ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
