Re: 6.1 to 6.2
On Mar 13, 2007, at 4:58, Matthew Herzog wrote: Hello. The 6.1 install is intact on disk0 and still works fine. I copied my ipfilter and ipnat config files to the new system after building an ipf/ipnat enabled kernel on the 6.2 install but the machine is not acting as a gateway. In fact, I can't even ssh into it from inside or outside Does issuing ipf -F a -f /etc/ipf.rules help? It solved a similar looking problem for me on my amd64 home gateway. I could still log into the server from my LAN, but not all of my rules were active somehow. Reloading the rule-set from a shell (after each reboot) helped. If it does, I guess there's an rc-order problem somewhere? As a temporary workaround (haven't tried yet) you could add that line to rc.local. Note: My server runs a 6-STABLE from shortly after 6.2-RELEASE. -- Alban Hertroys If you throw your hands up in the air, how're you gonna catch them? !DSPAM:74,45f65bb99411478922070! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Xorg and ATI card query.
On Mon, 12 Mar 2007 18:40:07 + Yann Golanski [EMAIL PROTECTED] mentioned: I have an ATI Radeon X1950 Sapphire and I am trying to get X/FreeBSD working with it. My system is a clean install of FreBSD. I've managed to get VESA to work but cannot get much more than that. fglrx gives me an error at compile time since I do not have /usr/X11R6/bin/moc installed. Would an install of Xorg 7 be useful here? What else can I try? I know I could use Linux and the ATI drivers but I'd rather use FreeBSD if possible. FreeBSD nightwatch.neverness.org 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan 12 11:05:30 UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP i386 Find attached the dmesg, xorg.conf and /var/log/xorg.0.log files. If anyone wants more information let me know. I am happy to beta-test software to get this to work. AFAIK, opensource Xorg ati drivers doesn't work with anything beyond x1800. flgrx is only linux binary, however, so you couldn't use it for FreeBSD. -- Stanislav Sedov ST4096-RIPE pgpUWYOFF10xP.pgp Description: PGP signature
Re: Xorg and ATI card query.
Stanislav Sedov wrote: AFAIK, opensource Xorg ati drivers doesn't work with anything beyond x1800. That would be x800. No x1k and problems with onboard video. -- ./lxnt ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Xorg and ATI card query.
On Tuesday 13 March 2007 07:21, Stanislav Sedov wrote: On Mon, 12 Mar 2007 18:40:07 + AFAIK, opensource Xorg ati drivers doesn't work with anything beyond x1800. flgrx is only linux binary, however, so you couldn't use it for FreeBSD. Actually.. http://www.fglrx-freebsd.com/index.php Unfortunately there is no amd64 version and I lack the clue to make one. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgp12D5gpejcU.pgp Description: PGP signature
Re: Xen Dom0, are we making progress?
Nikolas Britton wrote: On 3/12/07, Andras Gót [EMAIL PROTECTED] wrote: Nikolas Britton wrote: On 3/12/07, Ronald Klop [EMAIL PROTECTED] wrote: On Mon, 12 Mar 2007 20:16:32 +0100, Nikolas Britton [EMAIL PROTECTED] wrote: Is FreeBSD making any progress in Xen Dom0 / Intel VT support? I'd really like to consolidate some underutilized FreeBSD servers. Are their any alternative solutions that will enable me to do this kind of stuff with FreeBSD, or would it be better to go with Solaris Dom0 + FreeBSD DomU? http://docs.freebsd.org/44doc/papers/jail/jail.html google: jail freebsd Yes I'd like to know more about jails, is there a high level / executive summary type document that I can read somewhere? From what I remember jails are mostly designed to partition stuff... for security reasons. What I'd really love to do is split up each service (httpd, postgres, samba/nfs, ldap/nis, asterisk, etc.) into discrete virtual machines. It's too much work trying to make them all play nice on one system, especially during upgrades. As it is right now I don't upgrade any services once a system is in production use. Hi, For first read man jail. :) Apache, bind, mysql and postfix run fine in a jail. For postgres you've to turn on the jail.ipc. This is basicly not so bad, but definitely reduces security. For samba/nfs/ldap/nis and asterisk I don't have the experience, but if they not need ipc, they'll run fine out of the box. In jails I suggest that you mount your ports tree with some nullfs mount. With this you'll save some hd capacity. (The installed port list is in /var, not in /usr/ports.) In jails you can't do resource control, so keep that in mind. Is their anyway to transfer jails on the fly between systems... For example, say I wanted to transfer the http service to a more powerful box because load was too high, can you do stuff like this? You could export the jail file system via nfs, or use some other form of shared storage to share the file system. I have seen systems that put the jail IP address onto the loop back interface and then use OSPF to advertise the service to your border routers. If your storage subsystem supports if (NFS will) you can have both jails up and running at the same time and then just change the routing advertisements to move the service. Just an idea, I have never tried it, but I did see some fail over project that used the methods above. The project advertised the fact that not only can you move services between hosts but also you can move them between physical sites if your routers all run ospf. Tom ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Background process
On Thu, Mar 08, 2007 at 04:14:22PM -0800, Doug Barton wrote: No one has offered what I think is the most sensible option, which is to check the documentation for your program to see if it has a command line option to background itself properly. I'm not familiar with moinmoin, but I have a hard time believing that it doesn't have this capability. I've run moinmoin: it's a cgi script (wiki). It gets called from a web server, usually Apache. There's no call to be running it from the command line at all, that I'm aware of. Could be it isn't installed or configured properly. The config script is installed by the port, and it's pretty nicely commented. Cheers, -- Andrew ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: any success with new sun M2 product variant for X4100 and X2100
On Thu, Mar 08, 2007 at 10:45:15PM +0100, Jens Fallesen wrote: The primary NICs are Broadcom, the secondary ones are Nvidia as part of the chipset (FreeBSD does not recognise those). I've been running the nfe driver with the ciphy patch for probably greater than six months on my NVidia nForce4-based Athlon X2 system. I don't understand why it hasn't been rolled into -stable yet. Admittedly I haven't tested nve for a while, but the comment above doesn't instill confidence. Without the ciphy patch none of the drivers even detect carrier, which means that the base system still doesn't include those bits... Cheers, -- Andrew ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
hylaFAX on FreeBSD notify script
Dear hylaFAX _and_ FreeBSD friends, Running HylaFAX 4.3.2 on FreeBSD 6.2 produces following error: nawk -f bin/b64-encode.awk /tmp/tmp-50791/body.txt WW91ciBqb2IgdG8gKzMxMTgxMjU2MzUyIHdhcyBjb21wbGV0ZWQgc3VjY2Vzc2Z1bGx5LgoK ICAgICAgICAgICAgUGFnZXM6IDIKICAgICAgICAgUmVjZWl2ZXI6ICszMSAxODEgMjYxMzUy CiAgICAgICAgICBRdWFsaXR5OiAxOTYKICAgICAgIFBhZ2UgV2lkdGg6IDIwOSAobW0pCiAg ICAgIFBhZ2UgTGVuZ3RoOiAyOTYKICAgICAgU2lnbmFsIFJhdGU6IDk2MDAgYml0L3MKICAg ICAgRGF0YSBGb3JtYXQ6IDItRCBNUgogUmVtb3RlIEVxdWlwbWVudDogdW5rbm93biAtIGlu ZGV0ZXJtaW5hdGUgCiAgIFJlbW90ZSBTdGF0aW9uOiAKICAgICAgICAgIERpYWxvZ3M6IDEg KGV4Y2hhbmdlcyB3aXRoIHJlbW90ZSBkZXZpY2UpCiAgICAgICAgICAgIENhbGxzOiAxICh0 b3RhbCBwaG9uZSBjYWxscyBwbGFjZWQpCiAgICAgICAgICAgIE1vZGVtOiBhbnkKICAgU3Vi bWl0dGVkIEZyb206IG5lcHR1bnVzLnJvbXBlbi5ubAogICAgICAgICAgICBKb2JJRDogMTky CiAgICAgICAgICBHcm91cElEOiAxOTIKICAgICAgICAgICBDb21tSUQ6IGMwMDAwMDc5MzMK ClByb2Nlc3NpbmcgdGltZSB3YXMgMToyNy4KCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoK CgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoK CgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoK CgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoK ... ... ... The encoding ends up in a loop! The workaround is to use gawk instead of nawk on FreeBSD for the b64-encoding. I forgot about the differences between awk, nawk and gawk on FreeBSD, but it could be related to a special implementation of awk under FreeBSD. I will try to replace nawk by gawk in setup.cache. If I don't post a next message you can assume that it works. -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, De jrus wah, Willy * W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 653 27 16 23 e-mail: [EMAIL PROTECTED] Powered by (__) \\\'',) \/ \ ^ .\._/_) www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.1 to 6.2
Hmm. The rc subsystem is supposed to handle the order, i.e. you should never need to think about the order of services in rc.conf. I can't help thinking I am missing something in the kernel. Do you have any kernel modules running? On 3/13/07, Alban Hertroys [EMAIL PROTECTED] wrote: On Mar 13, 2007, at 4:58, Matthew Herzog wrote: Hello. The 6.1 install is intact on disk0 and still works fine. I copied my ipfilter and ipnat config files to the new system after building an ipf/ipnat enabled kernel on the 6.2 install but the machine is not acting as a gateway. In fact, I can't even ssh into it from inside or outside Does issuing ipf -F a -f /etc/ipf.rules help? I can't remember. If I had a dime for every time I have had to run that command since I discovered netbsd in 1999 I'd be wealthy. Heh. My ipfilter rules and pretty liberal and I do not have DEFAULT_BLOCK in the kernel. It solved a similar looking problem for me on my amd64 home gateway. I could still log into the server from my LAN, but not all of my rules were active somehow. Reloading the rule-set from a shell (after each reboot) helped. If it does, I guess there's an rc-order problem somewhere? As a temporary workaround (haven't tried yet) you could add that line to rc.local. Note: My server runs a 6-STABLE from shortly after 6.2-RELEASE. -- Alban Hertroys If you throw your hands up in the air, how're you gonna catch them? !DSPAM:667,45f65bba9417165217099! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [hylafax-users] notify script on FreeBSD 6.2
On Tue, Mar 13, 2007 at 08:23:15AM -0400, Aidan Van Dyk wrote: * Willy Offermans [EMAIL PROTECTED] [070313 07:51]: Dear hylaFAX friends, Running HylaFAX 4.3.2 on FreeBSD 6.2 produces following error: nawk -f bin/b64-encode.awk /tmp/tmp-50791/body.txt The encoding ends up in a loop! The workaround is to use gawk instead of nawk on FreeBSD for the b64-encoding. I forgot about the differences between awk, nawk and gawk on FreeBSD, but it could be related to a special implementation of awk under FreeBSD. I will try to replace nawk by gawk in setup.cache. If I don't post a next message you can assume that it works. Any chance I could get access to a freebsd account with nawk? We'ld certainly like to get it working. But seeing as you're using the fallback awk encoder, is it true that you don't have any of mimencode, base64-encode, or uuencode installed on your system? If you do, did you re-run faxsetup? a. Dear Aidan, Sure you can have access to the FreeBSD machine. If I can contribute to the ``development'' of hylaFAX, although in a very passive manner, I'm always willing to do so. If you can send me your IP address and possible username in private, I can make an account for you. However I have to tell you that this is a production machine and although it is only a small network, it is very precious to me and the users. If you need an account, be cautious. Indeed I found a possible error in setup.cache MIMENCODE='base64-encode' I do not have a program called base64-encode, it is called base64 under FreeBSD, I guess. So I will play with the settings for AWK='/usr/local/bin/gawk' or AWK='/usr/bin/nawk' and MIMENCODE='base64-encode'. How can I trigger that base64 is used instead of bin/b64-encode.awk? Probably I find myself a solution if I look carefully. mimencode is neither installed nor a FreeBSD port. It could be part of a port, I will look it up. uuencode is properly installed. Some googling learned met that nawk is a newer awk. An enhanced version of AWK, with dynamic regular expressions, additional built-ins ... Most probably you can install it on a linux machine as well, assuming that you have access to a linux machine. It seems __not__ to be a FreeBSD implementation of awk. -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, De jrus wah, Willy * W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 653 27 16 23 e-mail: [EMAIL PROTECTED] Powered by (__) \\\'',) \/ \ ^ .\._/_) www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD mysql Benchmark on 4BSD/ULE scheduler and i386/amd64
You can view my benchmark here: https://manuelmartini.it/bench/mysql/ m. signature.asc Description: PGP signature
6.2-STABLE deadlock?
At work, amoungst my stable of old computers running FreeBSD, I have a Fujitsu M800 - a 4 Zeon SMP processor with 4 GB of memory. This primarily runs Nagios and a small and lightly used MySQL database, along with a few inbound FTP transfers per minute. It has a Mylex card based disc subsystem, ruling out crash dumps. At some point during 5.5-STABLE this machine started to occasionally hang while performing its daily application housekeeping - closing and restarting Apache and Nagios, and dumping the database. Upgrading to 6.2-STABLE appeared to solve the problem, with no problems visible while running 1,000 cycles of the sequence which seemed to provoke the problem. cvsup for this version of the kernel and userland was run at 01:20 GMT on 06 March. However, shortly after 15:15 last Sunday afternoon the machine hung again out of the blue. kdb diagnostics were taken some 12 hours later, and look somewhat odd. Maybe it was left to fester for too long. ps etc output at http://www.stade.co.uk/crash/console which contains boot to boot serial console output, including some output from test cycles. I'd be grateful for any expert comments on the ps etc output. Supporting stuff. [EMAIL PROTECTED] ~/crash]# df Filesystem1K-blocks UsedAvail Capacity Mounted on /dev/mlxd0s1a50763070074 39694615%/ devfs 110 100%/dev /dev/mlxd0s1f 63541498 44355014 1410316676%/home /dev/mlxd0s1e 16244334 6784900 815988845%/usr /dev/mlxd0s1d 1012974 117456 81448213%/var /dev/md0 1646 32 1484 2%/home/topftp/instances /dev/md1 253678 132 233252 0%/tmp [EMAIL PROTECTED] ~]# find /var -inum 23 -ls 234 -rw-r--r--1 daemon daemon 60 Mar 12 20:22 /var/rwho/whod.xjamesfriis Problem stopped http and FTP logging soon after 15:14 on Sunday 11, diagnostics taken and machine rebooted around 04:30 on Monday 12. 172.19.112.92 - - [11/Mar/2007:15:14:53 +] GET / HTTP/1.0 200 688 - check_http/1.89 (nagios-plugins 1.4.3) time passes 172.19.112.92 - - [12/Mar/2007:04:44:14 +] GET / HTTP/1.0 200 688 - check_http/1.89 (nagios-plugins 1.4.3) Mar 11 15:15:35 beastie ftpd[91652]: connection from appsupcen (10.208.1.134) Mar 11 15:15:35 beastie ftpd[91652]: FTP LOGIN FROM appsupcen as topftp Mar 11 15:15:35 beastie ftpd[91652]: session root changed to /home/topftp/instances Mar 11 15:15:35 beastie ftpd[91652]: put in.env_status.html.gz = 592 bytes (wd: /topftp/appsupcen; chrooted) time passes Mar 11 15:15:35 beastie ftpd[91652]: rename in.env_status.html.gz env_status.html.gz (wd: /topftp/appsupcen; chrooted) Mar 12 04:44:31 beastie ftpd[1161]: connection from appsupcen (10.208.1.134) Mar 12 04:44:31 beastie ftpd[1161]: FTP LOGIN FROM appsupcen as topftp Mar 12 04:44:31 beastie ftpd[1161]: session root changed to /home/topftp/instances Mar 12 04:44:31 beastie ftpd[1161]: mkdir topftp/appsupcen (wd: /; chrooted) Support diary: 15:20 Beastie seems like its crashed and down; 16:54 Beastie is now longer pingable by rjmon1; 04:30 - 04:43 (support person quoting from the documentation I'd provided about what to do after a hang) Type return tilde hash (CR~#) which will make cu send a break signal to beastie, and should cause beastie to drop into the ddb kernel debugger. In the following, you may see more prompts. Type space at each for the next page. Type these debugger commands ps show pcpu show allpcpu show locks show alllocks show lockedvnods trace alltrace 04:43 - beastie now back up and working now by typing call cpu_reset() after the above commands to reboot beastie. AW: preserved and inspected diagnostic output. It looks very unlike that for previous crashes (without a serial console) where a noticable feature was many ftpd processes in a UFS state. Possibly things happened in the 12 hour period between the onset of the problem on Sunday afternoon and the diagnostics being taken on Monday morning. -- Adrian Wontroba Adrian's Birthday Celebration: Crewe Limelight, Saturday 17 March. David Hughes and Tiny Tin Lady. Free but ticketed - email me your postal address if you want to come. No under 18s. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Background process
On Thu, Mar 08, 2007 at 04:14:22PM -0800, Doug Barton wrote: I've run moinmoin: it's a cgi script (wiki). It gets called from a web server, usually Apache. There's no call to be running it from the command line at all, that I'm aware of. I run moinmoin in standalone mode, so it has its own http server. Thanks to everybody for their answer, I installed and used screen now it works ok for me. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Testing UFS/Snapshots/Quotas on -STABLE
Hello, I would like to test 6.2-STABLE's ability to handle UFS2, quotas, and snapshots. In particular, I would like to make sure the deadlock issue is resolved, (http://people.freebsd.org/~kib/quotagiant/quotas-20060428-1252.patch) In addition, it appears that compiling support for quotas in the kernel will force the Giant lock on UFS and I want to make sure I won't have a performance regression on the filesystem. Can anyone recommend a testing regime? I have a -STABLE production machine in mind that needs quotas enabled, is running sysutils/freebsd-snapshot, and has several large filesystems (100GB+). I'm not sure I want to test on this machine, however. Thanks for your help. -- Regards, Doug ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cvs commit: src/share/man/man4 Makefile watchdog.4 src/share/man/man9 watchdog.9 src/sys/arm/xscale/i80321 i80321_wdog.c src/sys/dev/ichwd ichwd.c src/sys/dev/ipmi ipmi.c src/sys/dev/mk48txx mk48t
At 05:42 PM 3/9/2007, Mike Tancsa wrote:
Hi,
The commit below to ichwd.c, breaks the watchdog on a
number of Intel boards I tried it against. (ICH5 and ICH7) The
module loads, but the box never reboots after sending a sig 11 to watchdogd
ichwd module loaded
ichwd0: Intel 82801EB/ER watchdog timer on isa0
Reverting to the version of ichwd.c prior to your commit unbreaks it
and the watchdog works once again in that the box reboots after
killing watchdogd.
Hi,
I think the issue is that in the commit you wiped out the part where
the dog gets enabled ?
This diff against what you committed gets it working once again
--- ichwd.c.old Tue Feb 20 17:56:27 2007
+++ ichwd.c Tue Mar 13 10:19:12 2007
@@ -178,6 +178,16 @@
struct ichwd_softc *sc = arg;
unsigned int timeout;
+/* disable / enable */
+if (!(cmd WD_ACTIVE)) {
+if (sc-active)
+ichwd_tmr_disable(sc);
+*error = 0;
+return;
+}
+if (!sc-active)
+ichwd_tmr_enable(sc);
+
/* convert from power-of-two-ns to WDT ticks */
cmd = WD_INTERVAL;
timeout = ((uint64_t)1 cmd) / ICHWD_TICK;
@@ -189,8 +199,6 @@
ichwd_tmr_reload(sc);
*error = 0;
} else {
- if (sc-active)
- ichwd_tmr_disable(sc);
if (cmd 0)
*error = EINVAL;
}
---Mike
At 05:56 PM 2/20/2007, Nick Hibma wrote:
n_hibma 2007-02-20 22:56:29 UTC
FreeBSD src repository
Modified files:(Branch: RELENG_6)
share/man/man4 Makefile watchdog.4
share/man/man9 watchdog.9
sys/arm/xscale/i80321 i80321_wdog.c
sys/dev/ichwdichwd.c
sys/dev/ipmi ipmi.c
sys/dev/mk48txx mk48txx.c
sys/dev/watchdog watchdog.c
sys/i386/i386elan-mmcr.c
sys/kern kern_clock.c
sys/sys watchdog.h
usr.sbin/watchdogd watchdog.8 watchdogd.c
Log:
MFC the following commits:
Align the interfaces for the various watchdogs and make the interface
behave as expected.
Also:
- Return an error if WD_PASSIVE is passed in to the ioctl as only
WD_ACTIVE is implemented at the moment. See sys/watchdog.h for an
explanation of the difference between WD_ACTIVE and WD_PASSIVE.
- Remove the I_HAVE_TOTALLY_LOST_MY_SENSE_OF_HUMOR define. If you've
lost your sense of humor, than don't add a define.
Specific changes:
i80321_wdog.c
Don't roll your own passive watchdog tickle as this would defeat the
purpose of an active (userland) watchdog tickle.
ichwd.c / ipmi.c:
WD_ACTIVE means active patting of the watchdog by a userland process,
not whether the watchdog is active. See sys/watchdog.h.
kern_clock.c:
(software watchdog) Remove a check for WD_ACTIVE as this does not make
sense here. This reverts r1.181.
Revision ChangesPath
1.371 +1 -0 src/share/man/man4/Makefile
1.8 +69 -25src/share/man/man4/watchdog.4
1.4 +7 -1 src/share/man/man9/watchdog.9
1.3 +15 -11src/sys/arm/xscale/i80321/i80321_wdog.c
1.7 +12 -30src/sys/dev/ichwd/ichwd.c
1.8 +8 -17 src/sys/dev/ipmi/ipmi.c
1.8 +3 -1 src/sys/dev/mk48txx/mk48txx.c
1.4 +4 -1 src/sys/dev/watchdog/watchdog.c
1.33 +9 -9 src/sys/i386/i386/elan-mmcr.c
1.193 +3 -3 src/sys/kern/kern_clock.c
1.4 +0 -4 src/sys/sys/watchdog.h
and
Don't exit from watchdogd on receiving a signal if we cannot
stop the watchdog.
That'll require -KILL. This avoids resetting your system on one of the
watchdogs that you cannot disable.
Revision ChangesPath
1.15 +18 -11src/usr.sbin/watchdogd/watchdogd.c
Reviewed by:phk
RevisionChangesPath
1.320.2.25 +1 -0 src/share/man/man4/Makefile
1.6.8.2 +69 -25src/share/man/man4/watchdog.4
1.3.8.1 +7 -1 src/share/man/man9/watchdog.9
1.2.2.1 +15 -11src/sys/arm/xscale/i80321/i80321_wdog.c
1.5.2.2 +12 -30src/sys/dev/ichwd/ichwd.c
1.3.2.5 +6 -17 src/sys/dev/ipmi/ipmi.c
1.6.2.2 +3 -1 src/sys/dev/mk48txx/mk48txx.c
1.2.8.1 +9 -2 src/sys/dev/watchdog/watchdog.c
1.31.2.2+9 -9 src/sys/i386/i386/elan-mmcr.c
1.178.2.4 +3 -3 src/sys/kern/kern_clock.c
1.3.8.1 +0 -4 src/sys/sys/watchdog.h
1.6.2.1 +5 -4 src/usr.sbin/watchdogd/watchdog.8
1.10.2.2+19 -13src/usr.sbin/watchdogd/watchdogd.c
___
cvs-all@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/cvs-all
To unsubscribe, send any mail to [EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
Re: Xorg and ATI card query.
On Tue, Mar 13, 2007 at 08:03:33PM +1030, Daniel O'Connor wrote: On Tuesday 13 March 2007 07:21, Stanislav Sedov wrote: On Mon, 12 Mar 2007 18:40:07 + AFAIK, opensource Xorg ati drivers doesn't work with anything beyond x1800. flgrx is only linux binary, however, so you couldn't use it for FreeBSD. Actually.. http://www.fglrx-freebsd.com/index.php Unfortunately there is no amd64 version and I lack the clue to make one. I looked at this last week. I have an amd64 Dell machine with an X1300 card. I did manage to get the flgrx 8.23.7 Linux amd64 driver to load as a driver in the FreeBSD version of X - basically I downloaded the Linux version, extracted the archive, grabbed the fglrx_drv.so file and put it in /usr/X11R6/lib/modules/drivers and then told X to load it. It seemed to be working, but was too old to support a X1300 card. I suspect it would work OK with less recent cards. I then tried to get a newer version working, but the fglrx_drv.so from newer ATI releases are linked against a whole bunch of crud (libstdc++, libgcc_s, ). I tried fudging the linker to make it load the FreeBSD versions of these, which got me a bit further, but the Linux versions of these libraries were too different for me to be able to get them to work. The drivers for xorg 6.8.0 looked a little more promising as they weren't linked against so many other libraries. However, I gave up before building a 6.8.0 server and used the vesa driver. David. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cvs commit: src/share/man/man4 Makefile watchdog.4 src/share/man/man9 watchdog.9 src/sys/arm/xscale/i80321 i80321_wdog.c src/sys/dev/ichwd ichwd.c src/sys/dev/ipmi ipmi.c src/sys/dev/mk48txx mk
At 11:32 AM 3/13/2007, Nick Hibma wrote:
Hi,
I think the issue is that in the commit you wiped out the part
where the dog gets enabled ?
This diff against what you committed gets it working once again
Yes, the enable is missing. The (untested) fix should be:
Yup, the patch below works for me!
---Mike
--- ichwd.c~Tue Feb 20 23:56:27 2007
+++ ichwd.c Tue Mar 13 16:31:11 2007
@@ -183,8 +183,11 @@
timeout = ((uint64_t)1 cmd) / ICHWD_TICK;
if (cmd 0 cmd = 63
timeout = ICHWD_MIN_TIMEOUT timeout =
ICHWD_MAX_TIMEOUT) {
- if (timeout != sc-timeout)
+ if (timeout != sc-timeout) {
+ if (!sc-active)
+ ichwd_tmr_enable(sc);
ichwd_tmr_set(sc, timeout);
+ }
ichwd_tmr_reload(sc);
*error = 0;
Nick
--- ichwd.c.old Tue Feb 20 17:56:27 2007
+++ ichwd.c Tue Mar 13 10:19:12 2007
@@ -178,6 +178,16 @@
struct ichwd_softc *sc = arg;
unsigned int timeout;
+/* disable / enable */
+if (!(cmd WD_ACTIVE)) {
+if (sc-active)
+ichwd_tmr_disable(sc);
+*error = 0;
+return;
+}
+if (!sc-active)
+ichwd_tmr_enable(sc);
+
/* convert from power-of-two-ns to WDT ticks */
cmd = WD_INTERVAL;
timeout = ((uint64_t)1 cmd) / ICHWD_TICK;
@@ -189,8 +199,6 @@
ichwd_tmr_reload(sc);
*error = 0;
} else {
- if (sc-active)
- ichwd_tmr_disable(sc);
if (cmd 0)
*error = EINVAL;
}
---Mike
At 05:56 PM 2/20/2007, Nick Hibma wrote:
n_hibma 2007-02-20 22:56:29 UTC
FreeBSD src repository
Modified files:(Branch: RELENG_6)
share/man/man4 Makefile watchdog.4
share/man/man9 watchdog.9
sys/arm/xscale/i80321 i80321_wdog.c
sys/dev/ichwdichwd.c
sys/dev/ipmi ipmi.c
sys/dev/mk48txx mk48txx.c
sys/dev/watchdog watchdog.c
sys/i386/i386elan-mmcr.c
sys/kern kern_clock.c
sys/sys watchdog.h
usr.sbin/watchdogd watchdog.8 watchdogd.c
Log:
MFC the following commits:
Align the interfaces for the various watchdogs and make the interface
behave as expected.
Also:
- Return an error if WD_PASSIVE is passed in to the ioctl as only
WD_ACTIVE is implemented at the moment. See sys/watchdog.h for an
explanation of the difference between WD_ACTIVE and WD_PASSIVE.
- Remove the I_HAVE_TOTALLY_LOST_MY_SENSE_OF_HUMOR define. If you've
lost your sense of humor, than don't add a define.
Specific changes:
i80321_wdog.c
Don't roll your own passive watchdog tickle as this would defeat the
purpose of an active (userland) watchdog tickle.
ichwd.c / ipmi.c:
WD_ACTIVE means active patting of the watchdog by a
userland process,
not whether the watchdog is active. See sys/watchdog.h.
kern_clock.c:
(software watchdog) Remove a check for WD_ACTIVE as this
does not make
sense here. This reverts r1.181.
Revision ChangesPath
1.371 +1 -0 src/share/man/man4/Makefile
1.8 +69 -25src/share/man/man4/watchdog.4
1.4 +7 -1 src/share/man/man9/watchdog.9
1.3 +15 -11src/sys/arm/xscale/i80321/i80321_wdog.c
1.7 +12 -30src/sys/dev/ichwd/ichwd.c
1.8 +8 -17 src/sys/dev/ipmi/ipmi.c
1.8 +3 -1 src/sys/dev/mk48txx/mk48txx.c
1.4 +4 -1 src/sys/dev/watchdog/watchdog.c
1.33 +9 -9 src/sys/i386/i386/elan-mmcr.c
1.193 +3 -3 src/sys/kern/kern_clock.c
1.4 +0 -4 src/sys/sys/watchdog.h
and
Don't exit from watchdogd on receiving a signal if we cannot
stop the watchdog.
That'll require -KILL. This avoids resetting your system on one of the
watchdogs that you cannot disable.
Revision ChangesPath
1.15 +18 -11src/usr.sbin/watchdogd/watchdogd.c
Reviewed by:phk
RevisionChangesPath
1.320.2.25 +1 -0 src/share/man/man4/Makefile
1.6.8.2 +69 -25src/share/man/man4/watchdog.4
1.3.8.1 +7 -1 src/share/man/man9/watchdog.9
1.2.2.1 +15 -11src/sys/arm/xscale/i80321/i80321_wdog.c
1.5.2.2 +12 -30src/sys/dev/ichwd/ichwd.c
1.3.2.5 +6 -17 src/sys/dev/ipmi/ipmi.c
1.6.2.2 +3 -1 src/sys/dev/mk48txx/mk48txx.c
1.2.8.1 +9 -2 src/sys/dev/watchdog/watchdog.c
1.31.2.2+9 -9 src/sys/i386/i386/elan-mmcr.c
1.178.2.4 +3 -3 src/sys/kern/kern_clock.c
1.3.8.1 +0 -4 src/sys/sys/watchdog.h
1.6.2.1 +5 -4 src/usr.sbin/watchdogd/watchdog.8
1.10.2.2+19 -13src/usr.sbin/watchdogd/watchdogd.c
Re: Testing UFS/Snapshots/Quotas on -STABLE
On Tue, Mar 13, 2007 at 09:50:54AM -0500, Doug Poland wrote: Hello, I would like to test 6.2-STABLE's ability to handle UFS2, quotas, and snapshots. In particular, I would like to make sure the deadlock issue is resolved, (http://people.freebsd.org/~kib/quotagiant/quotas-20060428-1252.patch) This patch is for Giant removal around UFS with QUOTAS, is outdated and contains known bugs. Please, wait several days until I finally commit stuff into the HEAD. After that, I most likely will backport the patch. In addition, it appears that compiling support for quotas in the kernel will force the Giant lock on UFS and I want to make sure I won't have a performance regression on the filesystem. See above. Can anyone recommend a testing regime? I have a -STABLE production machine in mind that needs quotas enabled, is running sysutils/freebsd-snapshot, and has several large filesystems (100GB+). I'm not sure I want to test on this machine, however. Thanks for your help. pgpX2HmTNO535.pgp Description: PGP signature
Re: Testing UFS/Snapshots/Quotas on -STABLE
On Tue, Mar 13, 2007 at 09:50:54AM -0500 I heard the voice of Doug Poland, and lo! it spake thus: In addition, it appears that compiling support for quotas in the kernel will force the Giant lock on UFS and I want to make sure I won't have a performance regression on the filesystem. I can tell you that the impact will range from negligable to significant, depending on the particular workload. I have a RELENG_6 box that, for hysterical raisins, has the ports tree on a partition with quotas, and a large 'portsnap update' gets VERY jerky. -- Matthew Fuller (MF4839) | [EMAIL PROTECTED] Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cvs commit: src/share/man/man4 Makefile watchdog.4 src/share/man/man9 watchdog.9 src/sys/arm/xscale/i80321 i80321_wdog.c src/sys/dev/ichwd ichwd.c src/sys/dev/ipmi ipmi.c src/sys/dev/mk48txx mk48t
Hi,
I think the issue is that in the commit you wiped out the part where the dog
gets enabled ?
This diff against what you committed gets it working once again
Yes, the enable is missing. The (untested) fix should be:
--- ichwd.c~Tue Feb 20 23:56:27 2007
+++ ichwd.c Tue Mar 13 16:31:11 2007
@@ -183,8 +183,11 @@
timeout = ((uint64_t)1 cmd) / ICHWD_TICK;
if (cmd 0 cmd = 63
timeout = ICHWD_MIN_TIMEOUT timeout = ICHWD_MAX_TIMEOUT) {
- if (timeout != sc-timeout)
+ if (timeout != sc-timeout) {
+ if (!sc-active)
+ ichwd_tmr_enable(sc);
ichwd_tmr_set(sc, timeout);
+ }
ichwd_tmr_reload(sc);
*error = 0;
Nick
--- ichwd.c.old Tue Feb 20 17:56:27 2007
+++ ichwd.c Tue Mar 13 10:19:12 2007
@@ -178,6 +178,16 @@
struct ichwd_softc *sc = arg;
unsigned int timeout;
+/* disable / enable */
+if (!(cmd WD_ACTIVE)) {
+if (sc-active)
+ichwd_tmr_disable(sc);
+*error = 0;
+return;
+}
+if (!sc-active)
+ichwd_tmr_enable(sc);
+
/* convert from power-of-two-ns to WDT ticks */
cmd = WD_INTERVAL;
timeout = ((uint64_t)1 cmd) / ICHWD_TICK;
@@ -189,8 +199,6 @@
ichwd_tmr_reload(sc);
*error = 0;
} else {
- if (sc-active)
- ichwd_tmr_disable(sc);
if (cmd 0)
*error = EINVAL;
}
---Mike
At 05:56 PM 2/20/2007, Nick Hibma wrote:
n_hibma 2007-02-20 22:56:29 UTC
FreeBSD src repository
Modified files:(Branch: RELENG_6)
share/man/man4 Makefile watchdog.4
share/man/man9 watchdog.9
sys/arm/xscale/i80321 i80321_wdog.c
sys/dev/ichwdichwd.c
sys/dev/ipmi ipmi.c
sys/dev/mk48txx mk48txx.c
sys/dev/watchdog watchdog.c
sys/i386/i386elan-mmcr.c
sys/kern kern_clock.c
sys/sys watchdog.h
usr.sbin/watchdogd watchdog.8 watchdogd.c
Log:
MFC the following commits:
Align the interfaces for the various watchdogs and make the interface
behave as expected.
Also:
- Return an error if WD_PASSIVE is passed in to the ioctl as only
WD_ACTIVE is implemented at the moment. See sys/watchdog.h for an
explanation of the difference between WD_ACTIVE and WD_PASSIVE.
- Remove the I_HAVE_TOTALLY_LOST_MY_SENSE_OF_HUMOR define. If you've
lost your sense of humor, than don't add a define.
Specific changes:
i80321_wdog.c
Don't roll your own passive watchdog tickle as this would defeat the
purpose of an active (userland) watchdog tickle.
ichwd.c / ipmi.c:
WD_ACTIVE means active patting of the watchdog by a userland
process,
not whether the watchdog is active. See sys/watchdog.h.
kern_clock.c:
(software watchdog) Remove a check for WD_ACTIVE as this does not
make
sense here. This reverts r1.181.
Revision ChangesPath
1.371 +1 -0 src/share/man/man4/Makefile
1.8 +69 -25src/share/man/man4/watchdog.4
1.4 +7 -1 src/share/man/man9/watchdog.9
1.3 +15 -11src/sys/arm/xscale/i80321/i80321_wdog.c
1.7 +12 -30src/sys/dev/ichwd/ichwd.c
1.8 +8 -17 src/sys/dev/ipmi/ipmi.c
1.8 +3 -1 src/sys/dev/mk48txx/mk48txx.c
1.4 +4 -1 src/sys/dev/watchdog/watchdog.c
1.33 +9 -9 src/sys/i386/i386/elan-mmcr.c
1.193 +3 -3 src/sys/kern/kern_clock.c
1.4 +0 -4 src/sys/sys/watchdog.h
and
Don't exit from watchdogd on receiving a signal if we cannot stop the
watchdog.
That'll require -KILL. This avoids resetting your system on one of the
watchdogs that you cannot disable.
Revision ChangesPath
1.15 +18 -11src/usr.sbin/watchdogd/watchdogd.c
Reviewed by:phk
RevisionChangesPath
1.320.2.25 +1 -0 src/share/man/man4/Makefile
1.6.8.2 +69 -25src/share/man/man4/watchdog.4
1.3.8.1 +7 -1 src/share/man/man9/watchdog.9
1.2.2.1 +15 -11src/sys/arm/xscale/i80321/i80321_wdog.c
1.5.2.2 +12 -30src/sys/dev/ichwd/ichwd.c
1.3.2.5 +6 -17 src/sys/dev/ipmi/ipmi.c
1.6.2.2 +3 -1 src/sys/dev/mk48txx/mk48txx.c
1.2.8.1 +9 -2 src/sys/dev/watchdog/watchdog.c
1.31.2.2+9 -9 src/sys/i386/i386/elan-mmcr.c
1.178.2.4 +3 -3 src/sys/kern/kern_clock.c
1.3.8.1 +0 -4 src/sys/sys/watchdog.h
1.6.2.1 +5 -4 src/usr.sbin/watchdogd/watchdog.8
1.10.2.2+19 -13src/usr.sbin/watchdogd/watchdogd.c
___
cvs-all@freebsd.org mailing list
Re: [hylafax-users] notify script on FreeBSD 6.2
Dear Aidan, On Tue, Mar 13, 2007 at 09:38:46AM -0400, Aidan Van Dyk wrote: * Willy Offermans [EMAIL PROTECTED] [070313 09:27]: Dear Aidan, Sure you can have access to the FreeBSD machine. If I can contribute to the ``development'' of hylaFAX, although in a very passive manner, I'm always willing to do so. If you can send me your IP address and possible username in private, I can make an account for you. However I have to tell you that this is a production machine and although it is only a small network, it is very precious to me and the users. If you need an account, be cautious. Of course - I'll be coming from testbed.hylafax.org, and would use the following SSH key: ssh-rsa B3NzaC1yc2EBIwAAAQEA8+JLWJF/OP9niTz0fQYqg/T5tF/xQMBLlk+QNq3YXKtoiRhBMwLT1NPySqJzii9BpiSo04Kne62Ij7Q09boLBznmjWp9V7k4ocwqm9xBJ2w8KzYa4zRYcL1417iKsQh5AU7+ZZtavTNPhif0jHFetljnK1gkMZvLTYAjwOtyS4dTs4ygT18NlmPd4/v9o7on7RlFvZSQOI1eeN4RGOR1xwCY7CBos7qPk2t+ijbXbbMnsU8+ackfLjcY3eKb3/46yBol+4Yl5o8jPabPc+PQiH+yAl6rlhTPQMhpQgdxR7JpQqbQFnphanlEU6G6A/pFBIAcpvILo+viswk9OzdI3Q== [EMAIL PROTECTED] I need some time to change the firewall, please be patient. Indeed I found a possible error in setup.cache MIMENCODE='base64-encode' I do not have a program called base64-encode, it is called base64 under FreeBSD, I guess. So I will play with the settings for AWK='/usr/local/bin/gawk' or AWK='/usr/bin/nawk' and MIMENCODE='base64-encode'. How can I trigger that base64 is used instead of bin/b64-encode.awk? Probably I find myself a solution if I look carefully. mimencode is neither installed nor a FreeBSD port. It could be part of a port, I will look it up. uuencode is properly installed. Hmm.. We only check for base64-encode, not base64. But we can add a check for base64 as well. If you set BASE64ENCODE=/usr/bin/base64 (or the correct path) in setup.cache, then the mime encode functions in common-functions should use it. I encounter some problems with that: sun# grep BASE64ENCODE bin/* bin/common-functions:# rather than separate $BASE64ENCODE and $QPENCODE bin/common-functions: if [ -n $BASE64ENCODE ]; then bin/common-functions: # $BASE64ENCODE may contain parameters bin/common-functions: cmd=`programOfCommand $BASE64ENCODE` bin/common-functions: (eval $BASE64ENCODE) $1 2$ERRORSTO sun# grep BASE64ENCODE etc/* It looks like I have an old setup.cache file, although I have run faxsetup. Aha indeed I have to add BASE64ENCODE='/usr/local/bin/base64' to the etc/setup.cache file. That works! So probably you have to test for base64 as well! Does your uuencode support the -m flag to do base64 mime encoding? Basically, in faxsetup, we look for: 1) mimencode 2) base64-encode 3) uuencode -m if any of these are found, BASE64ENCODE is set to what was found. In common functions, if BASE64ENCODE is good, we use it, and if it isn't, we fall back to the awk based b64-encode.awk, which we hoped would work on anything ;-) Ohoh, setting BASE64ENCODE='/usr/bin/uuencode -m' in etc/setup.cache did produce a notification e-mail, but the attached pdf file is totally empty. So this does not work either. Some googling learned met that nawk is a newer awk. An enhanced version of AWK, with dynamic regular expressions, additional built-ins ... Most probably you can install it on a linux machine as well, assuming that you have access to a linux machine. It seems __not__ to be a FreeBSD implementation of awk. It doesn't seem to be packaged for debian. Resume, there is some work to do with respect to BASE64ENCODE and nawk, base64 and uuencode under FreeBSD. mimencode still needs to be tested. I will contact you as soon as possible dear Aidan. -- Aidan Van Dyk [EMAIL PROTECTED] Senior Software Developer +1 215 825-8700 x8103 iFAX Solutions, Inc.http://www.ifax.com/ -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, De jrus wah, Willy * W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 653 27 16 23 e-mail: [EMAIL PROTECTED] Powered by (__) \\\'',) \/ \ ^ .\._/_) www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Testing UFS/Snapshots/Quotas on -STABLE
On Tue, March 13, 2007 10:46, Kostik Belousov wrote: On Tue, Mar 13, 2007 at 09:50:54AM -0500, Doug Poland wrote: I would like to test 6.2-STABLE's ability to handle UFS2, quotas, and snapshots. In particular, I would like to make sure the deadlock issue is resolved, This patch is for Giant removal around UFS with QUOTAS, is outdated and contains known bugs. Please, wait several days until I finally commit stuff into the HEAD. After that, I most likely will backport the patch. Thanks, I can wait some more :) -- Regards, Doug ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Xen Dom0, are we making progress?
Kip Macy wrote: On 3/12/07, Ivan Voras [EMAIL PROTECTED] wrote: Nikolas Britton wrote: Free Solaris DVD software kits (Free shipping too): http://www.sun.com/solaris/freemedia Or NetBSD: http://www.netbsd.org/Ports/xen/ Heh, you're still confused about what list your on. I know you were working on Xen support in FreeBSD, but web about it (http://www.fsmware.com/xenofreebsd/7.0/STATUS) has one year old info (support planned in FreeBSD 6.1). So is there any progress, or Xen will not be in any near future release? Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD mysql Benchmark on 4BSD/ULE scheduler and i386/amd64
Martin wrote: You can view my benchmark here: https://manuelmartini.it/bench/mysql/ Interesting results. The performance improvements talked about at http://jeffr-tech.livejournal.com/6268.html#cutid1 are not yet included in 7-current so the results might improve :) signature.asc Description: OpenPGP digital signature
Re: FreeBSD mysql Benchmark on 4BSD/ULE scheduler and i386/amd64
On Tue, Mar 13, 2007 at 03:42:06PM -0400, Craig Rodrigues wrote: On Tue, Mar 13, 2007 at 03:47:29PM +0100, Martin wrote: You can view my benchmark here: https://manuelmartini.it/bench/mysql/ Can you add links your kernel config file for each configuration you tested? It looks like your 6.2 configuration does not have WITNESS enabled, but your 7.0 configuration does. Also some more discussion would be useful, e.g. you appear to be testing on different machines so the most important thing to understand is how, or whether, the hardware differs. You do link to the dmesgs, but it's hard to process this into a summary form whereas you presumably know the details. I am also unfamiliar with the benchmark itself, can you give me a pointer to the software? If it is doing disk I/O then you may be mostly measuring the speed of your disks, which is why the previous paragraph is so important to understand. Kris P.S. Also, making this available by http instead of https would be great, your SSL certificates are expired, unsigned and misconfigured so you have to go through 3 dialogue boxes to load the page. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD mysql Benchmark on 4BSD/ULE scheduler and i386/amd64
Il giorno Tue, 13 Mar 2007 15:42:06 -0400 Craig Rodrigues [EMAIL PROTECTED] ha scritto: On Tue, Mar 13, 2007 at 03:47:29PM +0100, Martin wrote: You can view my benchmark here: https://manuelmartini.it/bench/mysql/ Can you add links your kernel config file for each configuration you tested? It looks like your 6.2 configuration does not have WITNESS enabled, but your 7.0 configuration does. I use GENERIC kernel file for 6.2 and GENERIC on 7 and I removed WITNESS signature.asc Description: PGP signature
Re: FreeBSD mysql Benchmark on 4BSD/ULE scheduler and i386/amd64
Il giorno Tue, 13 Mar 2007 15:57:57 -0400 Kris Kennaway [EMAIL PROTECTED] ha scritto: On Tue, Mar 13, 2007 at 03:42:06PM -0400, Craig Rodrigues wrote: On Tue, Mar 13, 2007 at 03:47:29PM +0100, Martin wrote: You can view my benchmark here: https://manuelmartini.it/bench/mysql/ Can you add links your kernel config file for each configuration you tested? It looks like your 6.2 configuration does not have WITNESS enabled, but your 7.0 configuration does. Also some more discussion would be useful, e.g. you appear to be testing on different machines so the most important thing to understand is how, or whether, the hardware differs. You do link to the dmesgs, but it's hard to process this into a summary form whereas you presumably know the details. I use the same hw (3 dell 1435 server) I am also unfamiliar with the benchmark itself, can you give me a pointer to the software? I used sql-bench /usr/ports/databases/mysql50-server/work/mysql-5.0.33/sql-bench/ (at this time) the default Makefile of port have --without-bench options so u need to make manually If it is doing disk I/O then you may be mostly measuring the speed of your disks, which is why the previous paragraph is so important to understand. the disk was the same of 3 test signature.asc Description: PGP signature
ntpd(8) exits quietly after fork()
ntpd won't continue running on my stratum 2 server (making our other systems a tad untrustworthy as time goes by). $ uname -a FreeBSD ezekiel.daleco.biz 6.2-RELEASE FreeBSD 6.2-RELEASE #5: Sat Jan 20 16:41:42 CST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 using ktrace and kdump I get this prior to exit: 12195 ntpd NAMI /var/run/logpriv 12195 ntpd RET connect 0 12195 ntpd CALL sendto(0x4,0xbfbfdd50,0x3e,0,0,0) 12195 ntpd GIO fd 4 wrote 62 bytes 13Mar 13 13:32:06 ntpd: logging to file /home/kadmin/ntp.log 12195 ntpd RET sendto 62/0x3e 12195 ntpd CALL clock_gettime(0,0xbfbfeb08) 12195 ntpd RET clock_gettime 0 12195 ntpd CALL sigaction(0x1,0xbfbfeac0,0xbfbfeae0) 12195 ntpd RET sigaction 0 12195 ntpd CALL fork 12195 ntpd RET fork 12196/0x2fa4 12195 ntpd CALL exit(0) After this, I can't `pgrep ntpd` or find a pid with ps -aux. I've found nothing in the logs; even using -l $HOME/ntp.log. A windows box complains no response using Softros' NTS. `ntpq -p here shows ntpq -p remote refid st t when poll reach delay offset jitter ezekiel.daleco. .INIT.16 u 148 102400.0000.000 4000.00 I can confirm that ntpd will continue to run if called with -n (do not fork). I've started a buildworld cycle. Any other suggestions? Can I do anything else debugging wise? Machine is about as close to production as we get, so rebuild with a debug kernel isn't something we'd really want to do, I think Thanks, Kevin Kinsey -- Computer programmers do it byte by byte. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Don't buy AMD products (was Re: Xorg and ATI card query.)
We need to start hounding on AMD to publish the developer documentation for all radeon chipsets. I for one will not buy any AMD or ATI components until they decide to fix the problem. Here's the email address of AMD's president: [EMAIL PROTECTED] Give him your two cents. On 3/12/07, Daniel O'Connor [EMAIL PROTECTED] wrote: On Tuesday 13 March 2007 05:10, Yann Golanski wrote: I have an ATI Radeon X1950 Sapphire and I am trying to get X/FreeBSD working with it. My system is a clean install of FreBSD. I've managed to get VESA to work but cannot get much more than that. There is no open source support for this card (alas). It's VESA or fglrx. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Don't buy AMD products (was Re: Xorg and ATI card query.)
On Tue, Mar 13, 2007 at 02:58:34PM -0500, Nikolas Britton wrote: We need to start hounding on AMD to publish the developer documentation for all radeon chipsets. I for one will not buy any AMD or ATI components until they decide to fix the problem. Here's the email address of AMD's president: [EMAIL PROTECTED] Give him your two cents. Boycotting their hardware due to lack-of public developer docs is extreme but justified. Everyone has the right to do that if they desire. But in my opinion, mailing the president of AMD is really not the way to go about this. That methodology invites angry people sending him flames, which does nothing but destroy the image of a mature, reliable open-source community. Besides, chances are it's not Meyer who's making these decisions (re: proprietary hardware / NDA-only documentation), but a few select individuals at ATI who are fuelled off of paranoia (the most common defence being fear nVidia/other competitors will steal their technology). Really sounds like the decision of a legal dept. and not a CEO. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networkinghttp://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Don't buy AMD products (was Re: Xorg and ATI card query.)
On 3/13/07, Jeremy Chadwick [EMAIL PROTECTED] wrote: On Tue, Mar 13, 2007 at 02:58:34PM -0500, Nikolas Britton wrote: We need to start hounding on AMD to publish the developer documentation for all radeon chipsets. I for one will not buy any AMD or ATI components until they decide to fix the problem. Here's the email address of AMD's president: [EMAIL PROTECTED] Give him your two cents. Boycotting their hardware due to lack-of public developer docs is extreme but justified. Everyone has the right to do that if they desire. But in my opinion, mailing the president of AMD is really not the way to go about this. That methodology invites angry people sending him flames, which does nothing but destroy the image of a mature, reliable open-source community. Besides, chances are it's not Meyer who's making these decisions (re: proprietary hardware / NDA-only documentation), but a few select individuals at ATI who are fuelled off of paranoia (the most common defence being fear nVidia/other competitors will steal their technology). Really sounds like the decision of a legal dept. and not a CEO. Right, flaming never helps, but then I don't think the intention was to have anyone flame, 'raising awareness' is a better goal :) AMD has people that work on Linux (I interviewed with them some years back), maybe using that route to get to the decision makers? Cheers, Jack ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Don't buy AMD products (was Re: Xorg and ATI card query.)
On Mar 13, 2007, at 16:33 , Jeremy Chadwick wrote: On Tue, Mar 13, 2007 at 02:58:34PM -0500, Nikolas Britton wrote: We need to start hounding on AMD to publish the developer documentation for all radeon chipsets. I for one will not buy any AMD or ATI components until they decide to fix the problem. Besides, chances are it's not Meyer who's making these decisions (re: proprietary hardware / NDA-only documentation), but a few select individuals at ATI who are fuelled off of paranoia (the most common defence being fear nVidia/other competitors will steal their technology). Really sounds like the decision of a legal dept. and not a CEO. Hounding on AMD won't help right now regardless; they're still finding out what kind of mess they've acquired, making changes to it is a long way off. :) -- brandon s. allbery [solaris,freebsd,perl,pugs,haskell] [EMAIL PROTECTED] system administrator [openafs,heimdal,too many hats] [EMAIL PROTECTED] electrical and computer engineering, carnegie mellon university KF8NH ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD mysql Benchmark on 4BSD/ULE scheduler and i386/amd64
On Tue, Mar 13, 2007 at 09:13:56PM +0100, Martin wrote: Il giorno Tue, 13 Mar 2007 15:42:06 -0400 Craig Rodrigues [EMAIL PROTECTED] ha scritto: On Tue, Mar 13, 2007 at 03:47:29PM +0100, Martin wrote: You can view my benchmark here: https://manuelmartini.it/bench/mysql/ Can you add links your kernel config file for each configuration you tested? It looks like your 6.2 configuration does not have WITNESS enabled, but your 7.0 configuration does. I use GENERIC kernel file for 6.2 and GENERIC on 7 and I removed WITNESS How about INVARIANTS? This has a 10-20% cost depending on workload. Kris pgps2qZXwgb28.pgp Description: PGP signature
Re: FreeBSD mysql Benchmark on 4BSD/ULE scheduler and i386/amd64
On Tue, Mar 13, 2007 at 09:19:08PM +0100, Martin wrote: Also some more discussion would be useful, e.g. you appear to be testing on different machines so the most important thing to understand is how, or whether, the hardware differs. You do link to the dmesgs, but it's hard to process this into a summary form whereas you presumably know the details. I use the same hw (3 dell 1435 server) I am also unfamiliar with the benchmark itself, can you give me a pointer to the software? I used sql-bench /usr/ports/databases/mysql50-server/work/mysql-5.0.33/sql-bench/ (at this time) the default Makefile of port have --without-bench options so u need to make manually Hmm. This seems to be a single-user test, so while it's presumably testing some relevant basic ingredients of database performance it's probably not a realistic measure of server performance. i.e. if you really only have a maximum of one client accessing your database then your 4-core system is being more than 75% wasted :) If it is doing disk I/O then you may be mostly measuring the speed of your disks, which is why the previous paragraph is so important to understand. the disk was the same of 3 test OK, cool. The difference between i386 and amd64 is actually kind of surprising. I would have expected amd64 to be slower. One thing that is missing is an estimate of standard deviation of the data points: some benchmarks have very high variance, meaning the numbers vary a lot between runs; this makes direct comparison more difficult without statistical work. In FreeBSD the /usr/src/tools/tools/ministat utility is excellent for this purpose. Kris pgpprt9gQ9Ai2.pgp Description: PGP signature
Re: Don't buy AMD products (was Re: Xorg and ATI card query.)
Please be very careful. The only real alternative (Intel comes and goes) is Nvidia whose driver is binary-only for i386 (no amd64 support) and has a history for being notoriously buggy. I only buy ATI because of the problems I keep seeing people have with the Nvidia driver. I have a friend who has basically abandoned his dual-head Nvidia card due to recurring issues. -Kip On 3/13/07, Nikolas Britton [EMAIL PROTECTED] wrote: We need to start hounding on AMD to publish the developer documentation for all radeon chipsets. I for one will not buy any AMD or ATI components until they decide to fix the problem. Here's the email address of AMD's president: [EMAIL PROTECTED] Give him your two cents. On 3/12/07, Daniel O'Connor [EMAIL PROTECTED] wrote: On Tuesday 13 March 2007 05:10, Yann Golanski wrote: I have an ATI Radeon X1950 Sapphire and I am trying to get X/FreeBSD working with it. My system is a clean install of FreBSD. I've managed to get VESA to work but cannot get much more than that. There is no open source support for this card (alas). It's VESA or fglrx. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD mysql Benchmark on 4BSD/ULE scheduler and i386/amd64
On Tue, Mar 13, 2007 at 09:13:56PM +0100, Martin wrote: I use GENERIC kernel file for 6.2 and GENERIC on 7 and I removed WITNESS You did not remove WITNESS in all your configs. I see this message: WARNING: WITNESS option enabled, expect reduced performance. in the dmesg output of two of your tests. Can you just publish the exact kernel config in the results table that you used, to make it easier to figure out your exact configuration, instead of guessing? -- Craig Rodrigues [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd(8) exits quietly after fork()
Hi, Kevin-- On Mar 13, 2007, at 1:14 PM, Kevin Kinsey wrote: ntpd won't continue running on my stratum 2 server (making our other systems a tad untrustworthy as time goes by). $ uname -a FreeBSD ezekiel.daleco.biz 6.2-RELEASE FreeBSD 6.2-RELEASE #5: Sat Jan 20 16:41:42 CST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/ sys/GENERIC i386 using ktrace and kdump I get this prior to exit: [ ... ] The logging paths seen in the ktrace are rather non-standard-- perhaps ntpd doesn't have the right permissions to write to them? Normally, ntpd logs to the NTP facility and critical messages might appear in /var/log/messages, so additional clues are probably there. Showing your ntp.conf file would also help, but if you'd like to see an example of a working stratum-2 conf file which has been in use for quite some time: 1-pi# cat /etc/ntp.conf # /etc/ntp.conf, configuration for ntpd driftfile /etc/ntp.drift statsdir /var/log/ntp/ statistics sysstats filegen sysstats file sysstats type week enable #logconfig =syncevents +sysevents # +allclock #statistics loopstats peerstats clockstats #filegen loopstats file loopstats type day enable #filegen peerstats file peerstats type day enable #filegen clockstats file clockstats type day enable server time.nist.gov maxpoll 12 server bonehed.lcs.mit.edu maxpoll 12 server sundial.columbia.edu maxpoll 12 server wwv.otc.psu.edu maxpoll 12 #peer pi.codefab.com maxpoll 12 peer pong.codefab.com maxpoll 12 peer shot.codefab.com maxpoll 12 peer ns1.pkix.net maxpoll 12 restrict default nomodify restrict localhost #discard average 9 minimum 2 #restrict default limited restrict 64.152.61.123 kod # ...list of bad clients being fed kod or ignore trimmed... 2-pi# grep ntp /etc/syslog.conf ntp.debug /var/log/ntp/ntp.log 3-pi# ntpq -p remote refid st t when poll reach delay offset jitter == -time.nist.gov .ACTS. 1 u 41m 68m 37 49.991 7.961 0.580 *bonehed.lcs.mit .CDMA. 1 u 204 68m 377 20.057 -2.610 6.201 +hickory.cc.colu 128.59.39.48 2 u 245 68m 377 25.537 -1.196 7.415 -otc1.psu.edu.WWV.1 u 276 68m 377 36.047 -21.679 0.037 +pong18.145.0.30 2 u 274 1024 3770.257 -3.274 2.857 +shot65.212.71.1032 u 495 1024 3770.343 1.467 0.664 -ns1 129.6.15.29 2 u 929 1024 3760.389 -5.890 0.769 For more details, one could also see: http://ntp1.codefab.com/ntpstats/ntp_stats.txt http://www.pool.ntp.org/scores/199.103.21.227 -- -Chuck ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Don't buy AMD products (was Re: Xorg and ATI card query.)
Kip Macy writes: | Please be very careful. The only real alternative (Intel comes and | goes) is Nvidia whose driver is binary-only for i386 (no amd64 | support) and has a history for being notoriously buggy. I only buy ATI | because of the problems I keep seeing people have with the Nvidia | driver. I have a friend who has basically abandoned his dual-head | Nvidia card due to recurring issues. One thing that is a plus with nv is that X has some support for it, whereas, the newer ati cards have no support :-( I was a fan of ati since it was easier to get support. Now I'm starting to lean towards Nvidia :-( Doug A. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd(8) exits quietly after fork()
Chuck Swiger wrote: Hi, Kevin-- On Mar 13, 2007, at 1:14 PM, Kevin Kinsey wrote: ntpd won't continue running on my stratum 2 server (making our other systems a tad untrustworthy as time goes by). $ uname -a FreeBSD ezekiel.daleco.biz 6.2-RELEASE FreeBSD 6.2-RELEASE #5: Sat Jan 20 16:41:42 CST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 using ktrace and kdump I get this prior to exit: [ ... ] The logging paths seen in the ktrace are rather non-standard-- perhaps ntpd doesn't have the right permissions to write to them? Normally, ntpd logs to the NTP facility and critical messages might appear in /var/log/messages, so additional clues are probably there. The ktrace is on ntpd -C /etc/ntp.conf -l $HOME/ntp.log --- I'd seen nothing at all in /var/log/messages (was running tail on it while restarting it several times), so I pointed it there. The full ktrace is rather long, any point to posting it? It did complain about some missing files, but seemed to accept others and go on. Here's most of the complaints in snippage form snip 12195 ktrace NAMI /sbin/ntpd 12195 ktrace RET execve -1 errno 2 No such file or directory 12195 ktrace CALL execve(0xbfbfe710,0xbfbfec5c,0xbfbfec74) 12195 ktrace NAMI /bin/ntpd 12195 ktrace RET execve -1 errno 2 No such file or directory snip 12195 ntpd CALL open(0x280a2c48,0,0x1b6) 12195 ntpd NAMI /etc/libmap.conf 12195 ntpd RET open -1 errno 2 No such file or directory snip 12195 ntpd NAMI /etc/malloc.conf 12195 ntpd RET readlink -1 errno 2 No such file or directory These don't seem to be related, but IANAE ;-) Grepping ntp in /etc/syslog.conf returns nada, so that would explain why there's nothing there. I did get status 2040 in $HOME/ntp.log, so I'm guessing bad driftfile was the issue? Showing your ntp.conf file would also help, but if you'd like to see an example of a working stratum-2 conf file which has been in use for quite some time: Nice, ty. Mine's simple: $ cat /etc/ntp.conf server time.nist.gov server navobs1.wustl.edu driftfile /var/ntpd.drift I've got it running fine now in FG (-n) option, and the slaves are happy ATM. I guess I could give it a ;-) It did complain that sanity limit was exceeded after I started it with -n, which would explain this, maybe? However, it was exiting prior to any mention of this previously, and I was *quite certain* that this box did the DST thing just fine, aside from sendmail logging behind as discussed in a thread on questions. If it's noise, I apologize. Buildworld should finish soon, and I'll monkey around with the driftfile meantime; we'll see if the issue persists. Oh, and edit syslog.conf and HUP. But, it'd been working fine for ages without all that. Either way, thanks for the reply! Kevin Kinsey -- Function reject. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd(8) exits quietly after fork()
On Mar 13, 2007, at 3:46 PM, Kevin Kinsey wrote: The ktrace is on ntpd -C /etc/ntp.conf -l $HOME/ntp.log --- I'd seen nothing at all in /var/log/messages (was running tail on it while restarting it several times), so I pointed it there. The full ktrace is rather long, any point to posting it? It did complain about some missing files, but seemed to accept others and go on. Here's most of the complaints in snippage form snip 12195 ktrace NAMI /sbin/ntpd 12195 ktrace RET execve -1 errno 2 No such file or directory 12195 ktrace CALL execve(0xbfbfe710,0xbfbfec5c,0xbfbfec74) 12195 ktrace NAMI /bin/ntpd 12195 ktrace RET execve -1 errno 2 No such file or directory snip 12195 ntpd CALL open(0x280a2c48,0,0x1b6) 12195 ntpd NAMI /etc/libmap.conf 12195 ntpd RET open -1 errno 2 No such file or directory snip 12195 ntpd NAMI /etc/malloc.conf 12195 ntpd RET readlink -1 errno 2 No such file or directory These don't seem to be related, but IANAE ;-) It seems to be having problems locating the ntpd binary to fork/exec it as a child? Is it possible the path in the /etc/rc.d/ntpd script isn't sane? ntpd should be in /usr/sbin/ntpd Grepping ntp in /etc/syslog.conf returns nada, so that would explain why there's nothing there. I did get status 2040 in $HOME/ntp.log, so I'm guessing bad driftfile was the issue? Showing your ntp.conf file would also help, but if you'd like to see an example of a working stratum-2 conf file which has been in use for quite some time: Nice, ty. Mine's simple: $ cat /etc/ntp.conf server time.nist.gov server navobs1.wustl.edu driftfile /var/ntpd.drift I've got it running fine now in FG (-n) option, and the slaves are happy ATM. I guess I could give it a ;-) It did complain that sanity limit was exceeded after I started it with -n, which would explain this, maybe? You might try checking ntpq -p and seeing whether your offset is too large. In that case, killing ntpd, running ntpdate -b time.nist.gov, and then restarting ntpd might help. However, it was exiting prior to any mention of this previously, and I was *quite certain* that this box did the DST thing just fine, aside from sendmail logging behind as discussed in a thread on questions. ntpd operates against GMT/UTC, and doesn't care about DST issues at all, fortunately. :-) Either way, thanks for the reply! You're welcome... -- -Chuck ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Don't buy AMD products (was Re: Xorg and ATI card query.)
On Tue, 13 Mar 2007, Doug Ambrisko wrote: Kip Macy writes: | Please be very careful. The only real alternative (Intel comes and | goes) is Nvidia whose driver is binary-only for i386 (no amd64 | support) and has a history for being notoriously buggy. I only buy ATI | because of the problems I keep seeing people have with the Nvidia | driver. I have a friend who has basically abandoned his dual-head | Nvidia card due to recurring issues. One thing that is a plus with nv is that X has some support for it, whereas, the newer ati cards have no support :-( I was a fan of ati since it was easier to get support. Now I'm starting to lean towards Nvidia :-( I used to find nvidia drivers very buggy, but the recent drivers have greatly impressed me. Stephen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD mysql Benchmark on 4BSD/ULE scheduler and i386/amd64
On Mar 13, 2007, at 22:45, Kris Kennaway wrote: I used sql-bench /usr/ports/databases/mysql50-server/work/mysql-5.0.33/sql-bench/ (at this time) the default Makefile of port have --without-bench options so u need to make manually Hmm. This seems to be a single-user test, so while it's presumably testing some relevant basic ingredients of database performance it's probably not a realistic measure of server performance. i.e. if you really only have a maximum of one client accessing your database then your 4-core system is being more than 75% wasted :) Sorry, couldn't resist... This being mysql, the number of processors isn't going to matter much, no matter how many connections you have. Mysql doesn't scale very well to multiple cpu's. I've had my doubts about this benchmark from the beginning of this thread, I don't see the point of benchmarks using mysql - especially if it's not even clear whether myIsam or Innodb was used. If this benchmark means anything, I'm sure there are benchmarks that better suit the purpose (with the exception of benchmarking mysql performance for a single connection). What are we actually trying to benchmark here? In my experience mysql as a database accepts invalid data, doesn't comply to the SQL standards much and isn't very fast at real-life database queries - among other things. It doesn't compare[1] to a tuned PostgreSQL database, which I think is a considerably more interesting benchmark. And of course that would include multiple simultaneous connections. Not to say that PostgreSQL is the ultimate benchmark instead of mysql, just a better one. Of course they both have their uses, but IMO mysql is loosing terrain fast. [1] I really mean it doesn't compare. PostgreSQL provides more (and IMHO better) features, and can be faster under the right circumstances (usually complex queries or concurrent writes). It also scales almost linearly to the number of cpu's, provided there are enough simultaneous connections. -- Alban Hertroys Priest to alien: We want to know, is there a higher being?. Alien: Well, actually that's why we're here, we're sheer out of virgins. !DSPAM:74,45f741509413780612645! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Xen Dom0, are we making progress?
I know you were working on Xen support in FreeBSD, but web about it (http://www.fsmware.com/xenofreebsd/7.0/STATUS) has one year old info (support planned in FreeBSD 6.1). So is there any progress, or Xen will not be in any near future release? Basically Xen did not mature in the fashion that I anticipated. As far as I can tell it is really only good for server consolidation for large Linux distro vendors. You need to have what amounts to a private branch. The xen developers don't appear to understand the importance of interface versioning. They broke ABI compatibility going from 3.0.2 - 3.0.3 (trivial to fix, but that is not the point). When last I worked on it, they had one branch that was in constant flux and another branch that only received minor bug fixes and was 18 months behind from a functionality standpoint (think 5.x / 4.x). There are numerous other logging / supportability issues that I think are only addressed by the major distros. As it stood 6 months ago, unless you understood the internals of various bits of the code, there was no way of diagnosing failures due to a misconfiguration. This is not to say that it isn't cool technology, but rather that isn't going to be useful for the things I wanted to use it for so my time is being directed elsewhere. If I ever have a need for EC2 I may look at it again. One of the guys who ported FreeBSD to the xbox has expressed interest - so something may yet come of it. I'm happy to provide technical support to an individual who is largely self-sustaining in working on the code. -Kip ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Don't buy AMD products (was Re: Xorg and ATI card query.)
Kip Macy a écrit : Please be very careful. The only real alternative (Intel comes and goes) is Nvidia whose driver is binary-only for i386 (no amd64 support) and has a history for being notoriously buggy. I only buy ATI because of the problems I keep seeing people have with the Nvidia driver. I have a friend who has basically abandoned his dual-head Nvidia card due to recurring issues. Hmm... I abandoned ATI GPU because of notoriously buggy issues. I have no problem with my nvidia GPUs (even in dualhead, at the time I tried it). Cheers, -- http://scipy.org/FredericPetit ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Don't buy AMD products (was Re: Xorg and ATI card query.)
Please be very careful. The only real alternative (Intel comes and goes) is Nvidia whose driver is binary-only for i386 (no amd64 support) and has a history for being notoriously buggy. I only buy ATI because of the problems I keep seeing people have with the Nvidia driver. I have a friend who has basically abandoned his dual-head Nvidia card due to recurring issues. Hmm... I abandoned ATI GPU because of notoriously buggy issues. I have no problem with my nvidia GPUs (even in dualhead, at the time I tried it). Good data point. I'm not taking sides. What dual head card are you using? I'm ordering the parts for a shuttle box now - if Nvidia works better I'll go with it. -Kip ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD mysql Benchmark on 4BSD/ULE scheduler and i386/amd64
On Wed, Mar 14, 2007 at 01:27:22AM +0100, Alban Hertroys wrote: On Mar 13, 2007, at 22:45, Kris Kennaway wrote: I used sql-bench /usr/ports/databases/mysql50-server/work/mysql-5.0.33/sql-bench/ (at this time) the default Makefile of port have --without-bench options so u need to make manually Hmm. This seems to be a single-user test, so while it's presumably testing some relevant basic ingredients of database performance it's probably not a realistic measure of server performance. i.e. if you really only have a maximum of one client accessing your database then your 4-core system is being more than 75% wasted :) Sorry, couldn't resist... This being mysql, the number of processors isn't going to matter much, no matter how many connections you have. Mysql doesn't scale very well to multiple cpu's. This might be standard dogma, but it also appears not to be true: http://people.freebsd.org/~kris/scaling/mysql.html It doesn't compare[1] to a tuned PostgreSQL database, which I think is a considerably more interesting benchmark. And of course that would include multiple simultaneous connections. On the same test postgresql is indeed faster, I haven't finished benchmarking it yet though. Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD mysql Benchmark on 4BSD/ULE scheduler and i386/amd64
Alban Hertroys wrote: Sorry, couldn't resist... Being a troll? This being mysql, the number of processors isn't going to matter much, no matter how many connections you have. Mysql doesn't scale very well to multiple cpu's. You seem to have been paying no attention at all to any of the mysql performance benchmarks and optimisation efforts that have being going on recently. Not to say that PostgreSQL is the ultimate benchmark instead of mysql, just a better one. Of course they both have their uses, but IMO mysql is loosing terrain fast. Any benchmark which looks to closely emulate real life work is valid, just be because you dont use or like a particular product doesnt make it any less suitable for testing / benchmarking. I'm sure if you took a survey of how many people are using mysql vs PostgreSQL it would show that the former is much more popular DB. No this doesnt make it better but it does make it a more suitable candidate for performance work as the benefits will benefit more people and more systems. Obviously this doesnt mean that optimisations for DB X wont benefit DB Y, or other apps for that matter, as its likely they will. [1] I really mean it doesn't compare. PostgreSQL provides more (and IMHO better) features, and can be faster under the right circumstances (usually complex queries or concurrent writes). It also scales almost linearly to the number of cpu's, provided there are enough simultaneous connections. It also has a known bottleneck to its performance on FreeBSD see earlier comments in other threads by Kris on this which clearly limits any benefit gained from using it as a benchmark. Steve This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Don't buy AMD products (was Re: Xorg and ATI card query.)
On Tue, 13 Mar 2007 14:17:00 -0800 (PST) Doug Ambrisko [EMAIL PROTECTED] wrote: One thing that is a plus with nv is that X has some support for it, whereas, the newer ati cards have no support :-( I was a fan of ati since it was easier to get support. Now I'm starting to lean towards Nvidia :-( Does anyone know if there are *any* contemporary graphics cards that have 3D acceleration supported by some flavour of open-source x.org? Doesn't have to be a super-fast 'leet gamer system to be better than a non-accelerated frame buffer. Matrox used to have a reputation for goodness (I used to have a G400 or the like), but it's been a long time... (I'm currently using a lowish-end NVidia card under the x.org nv driver, but it has issues (of which no 3D accel is but one...) Cheers, -- Andrew ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd(8) exits quietly after fork()
In the last episode (Mar 13), Kevin Kinsey said: ntpd won't continue running on my stratum 2 server (making our other systems a tad untrustworthy as time goes by). $ uname -a FreeBSD ezekiel.daleco.biz 6.2-RELEASE FreeBSD 6.2-RELEASE #5: Sat Jan 20 16:41:42 CST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 using ktrace and kdump I get this prior to exit: 12195 ntpd NAMI /var/run/logpriv 12195 ntpd RET connect 0 12195 ntpd CALL sendto(0x4,0xbfbfdd50,0x3e,0,0,0) 12195 ntpd GIO fd 4 wrote 62 bytes 13Mar 13 13:32:06 ntpd: logging to file /home/kadmin/ntp.log 12195 ntpd RET sendto 62/0x3e 12195 ntpd CALL clock_gettime(0,0xbfbfeb08) 12195 ntpd RET clock_gettime 0 12195 ntpd CALL sigaction(0x1,0xbfbfeac0,0xbfbfeae0) 12195 ntpd RET sigaction 0 12195 ntpd CALL fork 12195 ntpd RET fork 12196/0x2fa4 12195 ntpd CALL exit(0) It seems you're missing the -i flag to ktrace, which means you aren't tracing the child of this fork operation. This ktrace output looks a lot like the code in ntpd.c:ntpdmain(), in which ntpd forks, the parent immediately exits, and the child continues. -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
adduser error
dear users, i have problem with my fresh FreeBSD 6.2 RELEASE i can not adduser to this machine, the error logs was: ns1# pw adduser zen -g wheel -d /home/zen -s /bin/csh pwd_mkdb: corrupted entry pwd_mkdb: at line #12 pwd_mkdb: /etc/master.passwd: Inappropriate file type or format pw: user 'zen' disappeared during update ns1# pw adduser zen -g wheel -d /home/zen -s /bin/csh pwd_mkdb: corrupted entry pwd_mkdb: at line #12 pwd_mkdb: /etc/master.passwd: Inappropriate file type or format pw: user 'zen' disappeared during update please help regarding this problem TIA Zen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Don't buy AMD products (was Re: Xorg and ATI card query.)
On 3/13/07, Nikolas Britton [EMAIL PROTECTED] wrote: We need to start hounding on AMD to publish the developer documentation for all radeon chipsets. I for one will not buy any AMD or ATI components until they decide to fix the problem. Here's the email address of AMD's president: [EMAIL PROTECTED] Give him your two cents. On 3/12/07, Daniel O'Connor [EMAIL PROTECTED] wrote: On Tuesday 13 March 2007 05:10, Yann Golanski wrote: I have an ATI Radeon X1950 Sapphire and I am trying to get X/FreeBSD working with it. My system is a clean install of FreBSD. I've managed to get VESA to work but cannot get much more than that. There is no open source support for this card (alas). It's VESA or fglrx. Since AMD/ATI doesn't make a native driver for FreeBSD, I only buy notebooks with nvidia, and I told my friends about this. We as FreeBSD users could write about this in our blogs and pages, which will widespread the word about the driver issues in better way, as long as more users aware of this, this will force AMD/ATI to look into the issue deeper, and work it out. This would be better than emailing the AMD CEO IMHO. -- Regards, -Abdullah Ibn Hamad Al-Marri Arab Portal http://www.WeArab.Net/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
