HS20 Blade Center installation problem
Installation of FreeBSD 6.0 on IBM HS20 Blade Center stops at: atkbdc: Keyboard controller (i8042) at port 0x60, 0x64 on isa0 atkbd0: AT Keyboard flags 0x1 irq1 on atkbdc0 The same problem is with different type of installation (Default, Safe Mode, With USB Keyboard). Does anyone have solution for this problem? WebMax! - Internet Crna Gora Service ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sound skipping problems
Hi, Thanks for the tip, this seems to do the trick. Tested it with /usr/ports/sysutils/stress: [EMAIL PROTECTED](ttyp7:42:0):/shared# stress --cpu 8 --io 4 --vm 2 --vm-bytes 128M --hdd 4 --timeout 10m stress: info: [2439] dispatching hogs: 8 cpu, 4 io, 2 vm, 4 hdd and heard no more skips. Greetings, Sebastiaan van Erk Markus Trippelsdorf wrote: On Sun, Nov 06, 2005 at 12:39:02PM +0100, Sebastiaan van Erk wrote: Hi, I have major sound skipping problems on FreeBSD 6.0. I checked the mailing list archives and found a related thread: ... Does anybody have any ideas of what I could do to solve this problem? You could try to set hint.pcm.0.buffersize=16384 in /boot/loader.conf . It solved the problem for me. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sound skipping problems
Hi, Thank you for your reply! I tried the patch, but unfortunately when I reboot with the patch (which cleanly applies and compiles), audio stops working. The device (pcm0) is still there, the mixer is set ok, and everything looks normal, just no sound comes out of the speakers. I have no idea why the patch doesn't work, but if you want any more information I'll be happy to supply it to you. The sound skipping seems at least fixed by just increasing the buffer size, but don't know how reliable this workaround is compared to a structural workaround. Furthermore I don't know if this message is relevant, but it seems the snd_8233 driver doesn't like my audio codec very much: pcm0: VIA VT8237 port 0xec00-0xecff irq 22 at device 17.5 on pci0 pcm0: [GIANT-LOCKED] pcm0: Unknown AC97 Codec (id = 0x56494170) Greetings, Sebastiaan van Erk Ariff Abdullah wrote: On Sun, 06 Nov 2005 12:39:02 +0100 Sebastiaan van Erk [EMAIL PROTECTED] wrote: Hi, I have major sound skipping problems on FreeBSD 6.0. I checked the mailing list archives and found a related thread: http://lists.freebsd.org/pipermail/freebsd-current/2005-June/051103.html To quote Jeff Roberson: I have a patch that should greatly improve the sound skipping problems people have under heavy io load. Several people sent me traces that showed the buf daemon running for hundreds of milliseconds with Giant held, which can hold up the pcm code. The patch is available at: http://www.chesapeake.net/~jroberson/flushbuf.diff The problems are definately correlated to io load, however I can't say that I have HEAVY io loads. A simple: # sync;sync;sync; will already cause the sound to skip. I have DMA enabled on all drives, and it seems the above patch is already merged into FreeBSD 6.0-STABLE. This leaves me at a loss, and I don't know what else to try... Does anybody have any ideas of what I could do to solve this problem? Recompile your kernel with options PREEMPTION, and apply this patch: http://people.freebsd.org/~ariff/snd_RELENG_6_0_20051030_058.diff -- Ariff Abdullah MyBSD http://www.MyBSD.org.my (IPv6/IPv4) http://staff.MyBSD.org.my (IPv6/IPv4) http://tomoyo.MyBSD.org.my (IPv6/IPv4) ___ 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]
timecounter and Hz quality in kern RELENG_6
Hello, i be very surprised about the performance of RELENG_6. Congratulations to the entire Team for this very good work. Now i have 2 Machines installed with 6.0-RC1, and i have seen that on both machines the Hz is differntly with GENERIC-Kernel. Machine A is an Sempron 2400+ that runs as 2500+ (i have tuned the clock to best RAM-Performace) Machine B is an Duron 700MHz On Machine A i got an Hz from 2000 effectively systat -vmstat 1 show me 2000 IRQ/s on clk sysctl say's 1000i think, but not sure On Machine B i got an Hz from 1000 effectively systat-vmstat 1 show me 1000 IRQ/s on clk After digging in the source i have found that timec.c have an routine for computing the so called Hz quality. Can anyone explain me the mystics behind Hz quality, and why or how this quality is computed and what are the efforts? My knowledge is not deep enough to know these details. thanks best regards michael ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel: calcru: runtime went backwards
Stephen Montgomery-Smith wrote: Giovanni P. Tirloni wrote: Try this, http://www.freebsd.org/doc/en/books/faq/book.html#CALCRU-NEGATIVE Thank you. I must admit that I missed this. Unfortunately all the suggestions in this FAQ seem to be out of date - none of the suggested sysctls or kernel config options seem to apply to FreeBSD 6. Stephen I have the same problem after the switch to 6.0 from 5.4 : http://lists.freebsd.org/pipermail/freebsd-stable/2005-November/019171.html I've set the kern.timecounter sysctl to i8254 as suggested by Joseph Koshy. Now it seems that i get these messages rarely, maybe onece a day. Before this i get maybe 4-5 daily. Now it clearly looks that this has something to do with excessive thread usage. --niki ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic with cdrecord
on 05/11/2005 20:36 Manfred Lotz said the following: I agree. Happened to me as well under FreeBSD 6.0. burncd was hanging when trying to fixate and never came back. I personally don't see this problem, but I am still curious - has any of you guys tried to debug this problem ? E.g. attaching with gdb and checking where exaclty burncd hangs/loops etc. I am sure that there should exist a PR for this problem, so maybe collecting all available (useful) information under would help to make resolution closer. -- Andriy Gapon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /create/symlink failed: no inodes free
On Sun, 2005-11-06 at 20:02 -0600, Stephen Hurd wrote: Matt Smith wrote: Trying to put FBSD 6.0-Stable on a box and the error in the subject line (/create/symlink failed: no inodes free) comes up right after the filesystems are made and the transfer over FTP starts. What causes this error? I've found this tends to happen if the install is aborted then restarted. Indeed. http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/45565 Gavin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.x, 6.x and CPUTYPE
On Mon, Nov 07, 2005 at 04:21:56PM +1000, Joel Hatton wrote: I've noticed that some CPU definitions have changed in /etc/make.conf between 5 and 6. For good or for bad, I have up until now been building 5.x for both p3 and p4 architectures with 'i686' but this particular definition's removal from 6.x has given me cause to rethink my strategy. I'd like to know: Joel, thanks for pointing this out, I hadn't noticed this until I saw your message. I always build my production servers with CPUTYPE=i686 so they can be transplanted to any machine with a PPro or better processor (or even qemu if necessary). Looking at bsd.cpu.mk, it appears that i686 *IS* still accepted (for 5.x compat?) and is just aliased to CPUTYPE=pentiumpro. Craig ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
6.0 on Thinkpad T41
I still have a freeze upon shutting down the system, and also reboot. Tried Googling on this but no help :( ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: timecounter and Hz quality in kern RELENG_6
Michael Schuh [EMAIL PROTECTED] wrote:
i be very surprised about the performance of RELENG_6.
Congratulations to the entire Team for this very good work.
Now i have 2 Machines installed with 6.0-RC1, and i have seen that on
both machines the Hz is differntly with GENERIC-Kernel.
sysctl kern.clockrate tells you the HZ value.
In FreeBSD 6 the dafult is 1000, unless you change
it via options HZ=x in your kernel configuration.
The values from systat(1) or vmstat(8) are not reliable,
because the counters are only 32bit and can overflow.
For example, one machine here with HZ=1000 reports only
428 in vmstat -i:
$ sysctl kern.boottime ; date +%s ; vmstat -i | grep clk
kern.boottime: { sec = 1123867316, usec = 744735 } Fri Aug 12 19:21:56 2005
1131378875
clk irq0 3216967596428
Dividing the counter value by the uptime (in seconds)
seems to confirm the bogus rate of 428:
$ runtime='( 1131378875 - 1123867316 )'
$ echo '3216967596 / $runtime' | bc
428
But the 32bit counter has already overflowed once, so
we have to add 2^32. This gives the correct value:
$ echo '( 3216967596 + 2 ^ 32 ) / $runtime' | bc
1000
After digging in the source i have found that timec.c have an routine for
computing the so called Hz quality.
During boot, the kernel probes several time counters and
assigns quality values. Typically you have three of
them (i8254, ACPI, TPC). The time counter with the
highest quality value will be used for timing by default,
but you can change it via sysctl if you know what you are
doing. Type sysctl kern.timecounter and see the result.
Can anyone explain me the mystics behind Hz quality,
and why or how this quality is computed and what are the
efforts?
The reason for that is to have a time counter that is as
precise and reliable as possible. For example, TPC has
issues on SMP and power-managed machines, therefore it is
not as reliable as ACPI, so usually the ACPI timecounter
has higher quality (although it takes more clock cycles
to query it).
Oh, there's also a timecounter called dummy, which does
not count time at all. :-) It exists for debugging
purposes only, AFAIK, and has a negative quality value,
so it is never selected automatically.
Best regards
Oliver
--
Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing
Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd
Any opinions expressed in this message may be personal to the author
and may not necessarily reflect the opinions of secnetix in any way.
When your hammer is C++, everything begins to look like a thumb.
-- Steve Haflich, in comp.lang.c++
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: timecounter and Hz quality in kern RELENG_6
On Monday, 7. November 2005 17:10, Oliver Fromme wrote: Michael Schuh [EMAIL PROTECTED] wrote: i be very surprised about the performance of RELENG_6. Congratulations to the entire Team for this very good work. Now i have 2 Machines installed with 6.0-RC1, and i have seen that on both machines the Hz is differntly with GENERIC-Kernel. sysctl kern.clockrate tells you the HZ value. In FreeBSD 6 the dafult is 1000, unless you change it via options HZ=x in your kernel configuration. ... or via the kern.hz loader tunable. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpwaIEvNrLHP.pgp Description: PGP signature
Re: /create/symlink failed: no inodes free
On 11/7/05, Gavin Atkinson [EMAIL PROTECTED] wrote: On Sun, 2005-11-06 at 20:02 -0600, Stephen Hurd wrote: Matt Smith wrote: Trying to put FBSD 6.0-Stable on a box and the error in the subject line (/create/symlink failed: no inodes free) comes up right after the filesystems are made and the transfer over FTP starts. What causes this error? I've found this tends to happen if the install is aborted then restarted. Indeed. http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/45565 Gavin Can one of you post a followup to the bug stating that it's still present in the most recent version of the OS? I'm hoping that the bug wasn't just forgotten but 3 years is a long time, I think there are a lot of things I've forgotten in that period. :) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
OT: Failure notices from blogger.com
I recently started to get failure notices from [EMAIL PROTECTED] when I post on the freebsd-stable mailing list. What is that all about? Is somebody redirecting all mail on the list to a blog via post-by-mail? If so, FYI: blogger.com does not like pgp signatures and it insists on telling me about it again and again. I'm not particularly amused. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpYh2s5PAPCL.pgp Description: PGP signature
loader.conf setting ignored
Hello all, I am trying to turn on geom debug at boot in order to help figure out my gvinum problem, but I can't seem to set the variable from loader.conf. I can, however, set the variable from the loader prompt. My loader.conf looks like: geom_vinum_load=YES kern.geom.debugflags=1 I verified that my loader.rc contains these lines: include /boot/loader.4th start Any ideas on why debugflags cannot be set from loader.conf? I tried googling and found many references to people using it this way. Any help would be greatly appreciated. Thanks. - Ben ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: AGP ceased to work on eMachines M5310 laptop
On Sunday 06 November 2005 02:20 pm, Mike Jakubik wrote: The AGP does not seem to be detected on this laptop any more, i am positive that DRM used to work just fine on an earlier 5.x version. This is what happens why i try to load X. drm0: ATI Radeon RS100 Mobility U1 port 0x9000-0x90ff mem 0xe000-0xefff,0xd010-0xd010 irq 10 at device 5.0 on pci1 info: [drm] Initialized radeon 1.16.0 20050311 on minor 0 error: [drm:pid557:radeon_cp_init] *ERROR* radeon_cp_init called without lock held error: [drm:pid557:drm_unlock] *ERROR* Process 557 using kernel context 0 (EE) RADEON(0): [agp] AGP failed to initialize. Disabling the DRI. Here are the specifications for the laptop http://emachines.com/support/product_support.html?cat=notebooksubc at=M-Seriesmodel=M5310 Please send me 'pciconf -lv' output. Thanks, Jung-uk Kim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.0 on Thinkpad T41
On Mon, 07 Nov 2005 22:33:52 +0700 Justinus Andjarwirawan [EMAIL PROTECTED] wrote: I still have a freeze upon shutting down the system, and also reboot. Tried Googling on this but no help :( Is this a fresh installation or an upgrade from a previous version of FreeBSD? I upgraded my T41 this weekend (from 5.4-stable, with cvsup) and haven't seen any ill effects so far(but I haven't used it much either). I'm running 6.0-stable, with the GENERIC kernel, on a wired network. I haven't tried the wireless (ath) network yet. Are you using anything that could be considered special? Like Bluetooth, wireless? Does your T41 have any special hardware inside? Please provide more information. -- Regards, Torfinn Ingolfsen, Norway ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OT: Failure notices from blogger.com
On Mon, 07 Nov 2005 17:48:42 +0100 Michael Nottebrock [EMAIL PROTECTED] wrote: If so, FYI: blogger.com does not like pgp signatures and it insists on telling me about it again and again. I'm not particularly amused. FYI2: it doesn't like application/octet-stream attachments either. -- Regards, Torfinn Ingolfsen, Norway ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: loader.conf setting ignored
Write kern.geom.debugflags=1 it in to sysctl.conf and then try again. On Monday 07 November 2005 20:49, Ben Kelly wrote: My loader.conf looks like: kern.geom.debugflags=1 -- Elkhanzade Sarkhan Azerin ISP, U.Hajibeyov 36, Baku Systems Administrator Phone work : +994124982533 e-mail : [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: 6-stable unstable with HighPoint HPT372N UDMA133 controller
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 | I wrote: | | cvsup'd and built: FreeBSD 6.0-STABLE #4: Fri Nov 4 18:07:30 EST 2005 | | ~ [ .. ] | | | Nov 6 16:43:27 mail kernel: DOH! ata_alloc_request failed! | | Nov 6 16:43:27 mail kernel: FAILURE - out of memory in | ata_raid_init_request | | Nov 6 16:43:27 mail last message repeated 7 times | | Nov 6 16:43:27 mail kernel: Looking at the output of sysctl -a on a now almost idle machine I see: ITEMSIZE LIMIT USEDFREE REQUESTS ~ [ .. ] ata_composit:192,0, 12296,124,62341 ata_request: 200,0, 24592,108, 920945 ~ .. shouldn't these be freed at some point if there's minimal disk activity (and few dirty buffers, systat -vm says there are 7)? Or am I misreading this? Michael -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (MingW32) iD8DBQFDb4psiJykeV6HPMURAprwAKCF+Jdg+dXR0GzKwMDrDeK/nZ2NuQCgtjx7 o3k3GyYggzprYCtrw+4TQ8o= =ZgWJ -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: loader.conf setting ignored
On Monday 07 November 2005 12:05 pm, Sarxan Elxanzade wrote: Write kern.geom.debugflags=1 it in to sysctl.conf and then try again. Thanks for the quick reply. I moved the setting to /etc/sysctl.conf and this did result in the debugflags being set correctly. Unfortunately, though, it appears this occurs too late to see geom debug for the boot process. (Which makes sense since geom is probably needed to read in sysctl.conf.) I guess this is just something that cannot be done without console access to the loader prompt? Thanks again. On Monday 07 November 2005 20:49, Ben Kelly wrote: My loader.conf looks like: kern.geom.debugflags=1 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.x, 6.x and CPUTYPE
Hello Joel, Sunday, November 6, 2005, 10:21:56 PM, you wrote: Hi, I've noticed that some CPU definitions have changed in /etc/make.conf between 5 and 6. For good or for bad, I have up until now been building 5.x for both p3 and p4 architectures with 'i686' but this particular definition's removal from 6.x has given me cause to rethink my strategy. I'd like to know: Should I use 'i386' and build once for all, or use p3/p4 defs and build once for each? And if the latter, why? (does this give any worthwhile performance increase?) i386 will guarantee you that it should work on any PC, while p3/p4 will tell compiler to try using instructions available in pentium 3 or pentium 4. I don't have any performance stats to prove that, but in theory the code should be faster when you use p3 or p4 instead of i386. If I don't specify a CPUTYPE at all, will this be auto-detected in some way (which would probably not suit me) or will it fall back to i386? I'm afraid it will fall back to value that will produce code that can run on any PC (which is i386). Actually it won't provide any flag to gcc, but gcc will assume i386. Is this a consistent requirement for world/kernel/ports? Finally, when building on a single host, but where multiple requirements are being met, is it possible to define different make.conf files for make or is it easier to just edit this file before each build? As long as you defined the variable in this way e.g.: CPUTYPE?=i686 (the question mark is not a typo) This is actually recommended way to assign values like this one. You can pass this argument in make command e.g. make buildworld CPUTYPE=i686 make buildworld CPUTYPE=p4 etc. If you don't give argument, then whatever you have in /etc/make.conf will be assumed as a default value. -- Best regards, Derekmailto:[EMAIL PROTECTED] CCNA, SCSA, SCNA, LPIC, MCP certified http://www.takeda.tk Profanity is the language all programmers know best. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: three button mouse issues
Stephen Montgomery-Smith wrote: My laptop has two mice - the touchpad and a usb mouse. I would like the touchpad moused to run with the -3 flag and the usb moused to run without -3. But I can only get neither or both to run with -3 by the appropriate settings in /etc/rc.conf. Any ideas? (Apart from manually killing and restarting one of the moused processes?) Stephen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] i believe u can do it since 6.0, something like this: moused_psm0_flags=-3 martin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OT: Failure notices from blogger.com
On Mon, Nov 07, 2005 at 05:48:42PM +0100, Michael Nottebrock wrote: I recently started to get failure notices from [EMAIL PROTECTED] when I post on the freebsd-stable mailing list. Looks like everybody who signs his email gets them. What is that all about? Is somebody redirecting all mail on the list to a blog via post-by-mail? Looks that way. Would the person who set this up be as kind as to; a) educate blogger.com on the virtues of signed messages. b) nix the reply messages c) preferably both. If so, FYI: blogger.com does not like pgp signatures and it insists on telling me about it again and again. I'm not particularly amused. Bogofilter procmail to the rescue. Delivering annoying messages directly to /dev/null :-) Roland -- R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text. public key: http://www.xs4all.nl/~rsmith/pubkey.txt pgpu6TfBM5IFv.pgp Description: PGP signature
Re: timecounter and Hz quality in kern RELENG_6
Oliver Fromme wrote:
Michael Schuh [EMAIL PROTECTED] wrote:
i be very surprised about the performance of RELENG_6.
Congratulations to the entire Team for this very good work.
Now i have 2 Machines installed with 6.0-RC1, and i have seen that on
both machines the Hz is differntly with GENERIC-Kernel.
sysctl kern.clockrate tells you the HZ value.
In FreeBSD 6 the dafult is 1000, unless you change
it via options HZ=x in your kernel configuration.
The values from systat(1) or vmstat(8) are not reliable,
because the counters are only 32bit and can overflow.
For example, one machine here with HZ=1000 reports only
428 in vmstat -i:
$ sysctl kern.boottime ; date +%s ; vmstat -i | grep clk
kern.boottime: { sec = 1123867316, usec = 744735 } Fri Aug 12 19:21:56 2005
1131378875
clk irq0 3216967596428
Dividing the counter value by the uptime (in seconds)
seems to confirm the bogus rate of 428:
$ runtime='( 1131378875 - 1123867316 )'
$ echo '3216967596 / $runtime' | bc
428
But the 32bit counter has already overflowed once, so
we have to add 2^32. This gives the correct value:
$ echo '( 3216967596 + 2 ^ 32 ) / $runtime' | bc
1000
After digging in the source i have found that timec.c have an routine for
computing the so called Hz quality.
During boot, the kernel probes several time counters and
assigns quality values. Typically you have three of
them (i8254, ACPI, TPC). The time counter with the
highest quality value will be used for timing by default,
but you can change it via sysctl if you know what you are
doing. Type sysctl kern.timecounter and see the result.
are those quality values preset (i.e. TSC = 800) or are they computed
(during boot) somehow? and if the latter, how pls??
Can anyone explain me the mystics behind Hz quality,
and why or how this quality is computed and what are the
efforts?
The reason for that is to have a time counter that is as
precise and reliable as possible. For example, TPC has
issues on SMP and power-managed machines, therefore it is
not as reliable as ACPI, so usually the ACPI timecounter
has higher quality (although it takes more clock cycles
to query it).
Oh, there's also a timecounter called dummy, which does
not count time at all. :-) It exists for debugging
purposes only, AFAIK, and has a negative quality value,
so it is never selected automatically.
Best regards
Oliver
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.x, 6.x and CPUTYPE
On 11/7/05, Joel Hatton [EMAIL PROTECTED] wrote: Finally, when building on a single host, but where multiple requirements are being met, is it possible to define different make.conf files for make or is it easier to just edit this file before each build? That is what I do when I build 5.x, 6.x, and 7-CURRENT on the same server by creating multiple make.conf files. You just need to define the _MAKE_CONF variable for the appropriate OS that you are building: make _MAKE_CONF=/etc/make.conf.6x [build|install]world make _MAKE_CONF=/etc/make.conf.6x [build|install]kernel If your installing the build on another host, you just have to make sure that the /etc/make.conf.* on the build server matches the /etc/make.conf on the target system. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: loader.conf setting ignored
It looks like console access is necessary. But may be someone prompt another solution. On Monday 07 November 2005 22:10, Ben Kelly wrote: On Monday 07 November 2005 12:05 pm, Sarxan Elxanzade wrote: Write kern.geom.debugflags=1 it in to sysctl.conf and then try again. Thanks for the quick reply. I moved the setting to /etc/sysctl.conf and this did result in the debugflags being set correctly. Unfortunately, though, it appears this occurs too late to see geom debug for the boot process. (Which makes sense since geom is probably needed to read in sysctl.conf.) I guess this is just something that cannot be done without console access to the loader prompt? Thanks again. On Monday 07 November 2005 20:49, Ben Kelly wrote: My loader.conf looks like: kern.geom.debugflags=1 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- Elkhanzade Sarkhan Azerin ISP, U.Hajibeyov 36, Baku Systems Administrator Phone work : +994124982533 e-mail : [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
6.0-RELEASE panic: page fault
dies (reproductively) shortly on make kernel / other cpu+disk intense
operation. stock GENERIC kernel, I have savecore if anyone's
interested.
Unread portion of the kernel message buffer:
kernel trap 12 with interrupts disabled
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x109d04a0
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc0657d4d
stack pointer = 0x28:0xe6a68a88
frame pointer = 0x28:0xe6a68a8c
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= resume, IOPL = 0
current process = 45 (bufdaemon)
trap number = 12
panic: page fault
Uptime: 50m12s
Dumping 2047 MB (2 chunks)
chunk 0: 1MB (159 pages) ... ok
chunk 1: 2047MB (523968 pages) 2031 2015 1999 1983 1967 1951 1935
1919 1903 1887 1871 1855 1839 1823 1807 1791 1775 1759 1743 1727 1711
1695 1679 1663 1647 1631 1615 1599 1583 1567 1551 1535 1519 1503 1487
1471 1455 1439 1423 1407 1391 1375 1359 1343 1327 1311 1295 1279 1263
1247 1231 1215 1199 1183 1167 1151 1135 1119 1103 1087 1071 1055 1039
1023 1007 991 975 959 943 927 911 895 879 863 847 831 815 799 783 767
751 735 719 703 687 671 655 639 623 607 591 575 559 543 527 511 495
479 463 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223
207 191 175 159 143 127 111 95 79 63 47 31 15
#0 doadump () at pcpu.h:165
165 __asm __volatile(movl %%fs:0,%0 : =r (td));
(kgdb) backtrace
#0 doadump () at pcpu.h:165
#1 0xc0638202 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:399
#2 0xc0638498 in panic (fmt=0xc084e5a2 %s) at
/usr/src/sys/kern/kern_shutdown.c:555
#3 0xc0807c30 in trap_fatal (frame=0xe6a68a48, eva=278725792) at
/usr/src/sys/i386/i386/trap.c:831
#4 0xc08073d2 in trap (frame=
{tf_fs = -1067122680, tf_es = -1064239064, tf_ds = -1064239064,
tf_edi = -680455776, tf_esi = -1017617664, tf_ebp = -425293172, tf_isp
= -425293196, tf_ebx = -1017932160, tf_edx = -1017932160, tf_ecx =
278725676, tf_eax = -1017617632, tf_trapno = 12, tf_err = 0, tf_eip =
-1067090611, tf_cs = 32, tf_eflags = 65539, tf_esp = -1017617664,
tf_ss = -425293136})
at /usr/src/sys/i386/i386/trap.c:267
#5 0xc07f6dca in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#6 0xc0657d4d in turnstile_setowner (ts=0xc3539680, owner=0x109d042c)
at /usr/src/sys/kern/subr_turnstile.c:417
#7 0xc0658044 in turnstile_wait (lock=0xc6175294, owner=0x109d042c)
at /usr/src/sys/kern/subr_turnstile.c:576
#8 0xc062fa6c in _mtx_lock_sleep (m=0xc6175294, tid=3277349632,
opts=0, file=0x0, line=0)
at /usr/src/sys/kern/kern_mutex.c:553
#9 0xc067f663 in vfs_setdirty (bp=0xd77111a0) at
/usr/src/sys/kern/vfs_bio.c:
#10 0xc0680f68 in vfs_busy_pages (bp=0xd77111a0, clear_modify=1) at
/usr/src/sys/kern/vfs_bio.c:3293
#11 0xc067c945 in bufwrite (bp=0xd77111a0) at /usr/src/sys/kern/vfs_bio.c:822
#12 0xc067e3bf in vfs_bio_awrite (bp=0xd77111a0) at buf.h:399
#13 0xc067f169 in flushbufqueues (flushdeps=0) at
/usr/src/sys/kern/vfs_bio.c:2107
#14 0xc067ec6b in buf_daemon () at /usr/src/sys/kern/vfs_bio.c:1981
#15 0xc0623080 in fork_exit (callout=0xc067eb7c buf_daemon, arg=0x0,
frame=0xe6a68d38) at /usr/src/sys/kern/kern_fork.c:789
#16 0xc07f6e2c in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:208
(kgdb)
Copyright (c) 1992-2005 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 6.0-RELEASE #0: Thu Nov 3 09:36:13 UTC 2005
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC
Timecounter i8254 frequency 1193182 Hz quality 0
CPU: Intel(R) Pentium(R) 4 CPU 1.60GHz (1595.16-MHz 686-class CPU)
Origin = GenuineIntel Id = 0xf12 Stepping = 2
Features=0x3febfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM
real memory = 2147221504 (2047 MB)
avail memory = 2096414720 (1999 MB)
npx0: [FAST]
npx0: math processor on motherboard
npx0: INT 16 interface
acpi0: D850GB G285010A on motherboard
acpi0: Power Button (fixed)
pci_link0: ACPI PCI Link LNKA irq 11 on acpi0
pci_link1: ACPI PCI Link LNKB irq 10 on acpi0
pci_link2: ACPI PCI Link LNKC irq 0 on acpi0
pci_link3: ACPI PCI Link LNKD irq 5 on acpi0
pci_link4: ACPI PCI Link LNKE irq 0 on acpi0
pci_link5: ACPI PCI Link LNKF irq 3 on acpi0
pci_link6: ACPI PCI Link LNKG irq 14 on acpi0
pci_link7: ACPI PCI Link LNKH irq 9 on acpi0
Timecounter ACPI-fast frequency 3579545 Hz quality 1000
acpi_timer0: 24-bit timer at 3.579545MHz port 0x408-0x40b on acpi0
cpu0: ACPI CPU on acpi0
acpi_button0: Power Button on acpi0
pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0
pci0: ACPI PCI bus on pcib0
agp0: Intel 82850 host to AGP bridge mem 0xf800-0xfbff at
device 0.0 on pci0
pcib1: PCI-PCI bridge at device 1.0 on pci0
pci1: PCI bus on pcib1
pci1: display, VGA at device
Re: OT: Failure notices from blogger.com
Michael Nottebrock wrote: I recently started to get failure notices from [EMAIL PROTECTED] when I post on the freebsd-stable mailing list. Same here. What is that all about? Is somebody redirecting all mail on the list to a blog via post-by-mail? I guess something auto-posts FreeBSD mailing list posts to some blog hosted at blogger.com. I've simply mailed [EMAIL PROTECTED] with a complaint, since that seems to be the only address related to blogger.com that doesn't bounce. :) IMHO they should never auto-generate error or bounce reports in response to bulk email, so that's what I told them in my complaint. You may want to join in... signature.asc Description: OpenPGP digital signature
Re: OT: Failure notices from blogger.com
Dimitry Andric wrote: Michael Nottebrock wrote: What is that all about? Is somebody redirecting all mail on the list to a blog via post-by-mail? I guess something auto-posts FreeBSD mailing list posts to some blog hosted at blogger.com. I found this in the blogger.com FAQ: The Mail-to-Blogger feature turns any email account into a blog-posting application. In Settings | Email you can create a Mail-to-Blogger address which you will use to send posts via email to your blog http://help.blogger.com/bin/answer.py?answer=135topic=38 So someone probably subscribed one or more @blogger.com addresses to this, and other FreeBSD mailing lists. If this mail-to-blogger stuff doesn't work properly, would the list admin(s) please be so kind to unsubscribe these blogger.com users from all FreeBSD mailing lists? IMHO these unsolicited error messages are just as bad as out of office spam. signature.asc Description: OpenPGP digital signature
Re: 6.0-RELEASE panic: page fault
I think I need to recall my report - I took another person's word for memory is tested and good, which appeared to be not quite right after I double checked that with memtest86+. On 11/7/05, Vlad [EMAIL PROTECTED] wrote: dies (reproductively) shortly on make kernel / other cpu+disk intense operation. stock GENERIC kernel, I have savecore if anyone's interested. Unread portion of the kernel message buffer: kernel trap 12 with interrupts disabled -- Vlad ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6-stable unstable with HighPoint HPT372N UDMA133 controller
On 07/11/2005, at 18:10, Michael Butler wrote: | I wrote: | | cvsup'd and built: FreeBSD 6.0-STABLE #4: Fri Nov 4 18:07:30 EST 2005 | | ~ [ .. ] | | | Nov 6 16:43:27 mail kernel: DOH! ata_alloc_request failed! | | Nov 6 16:43:27 mail kernel: FAILURE - out of memory in | ata_raid_init_request | | Nov 6 16:43:27 mail last message repeated 7 times | | Nov 6 16:43:27 mail kernel: Looking at the output of sysctl -a on a now almost idle machine I see: ITEMSIZE LIMIT USEDFREE REQUESTS ~ [ .. ] ata_composit:192,0, 12296,124,62341 ata_request: 200,0, 24592,108, 920945 ~ .. shouldn't these be freed at some point if there's minimal disk activity (and few dirty buffers, systat -vm says there are 7)? Or am I misreading this? That does indeed look wrong. However I cant reproduce the problem here on any of the machines I have 6.0 on, and I dont think a memory leeak that severe would have survived this far, but I've been wrong many times before... I'll look into it as soon as I have a little more time than today.. - Søren ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
carp + ipfw problem
Hello all, I'm trying to configure a firewall with carp + ipfw, but I encountered the strange problem. Packets are bypassing carp interface, instead ipfw log shows packet flow to/from physical interface, e.g.: FreeBSD host 5.4-RELEASE-p7 FreeBSD 5.4-RELEASE-p7 #6: Tue Sep 27 16:32:30 AZST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/FIREWALL i386 # ifconfig fxp1 fxp1: flags=9943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,LINK0,MULTICAST mtu 1500 options=8VLAN_MTU inet 192.168.28.1 netmask 0xff00 broadcast 192.168.28.255 media: Ethernet 100baseTX full-duplex status: active # ifconfig carp1 carp1: flags=41UP,RUNNING mtu 1500 inet 192.168.28.2 netmask 0xff00 carp: MASTER vhid 4 advbase 1 advskew 0 # ipfw show 1 0 0 check-state 2 0 0 allow ip from any to any via lo0 00010 0 0 allow log icmp from any to any 00020 4 344 allow log tcp from any to any 00030 0 0 allow log udp from any to any 65534 0 0 allow ip from any to any 65535 0 0 deny ip from any to any When I ping the IP address assigned to carp1 interface from host within the same network # ping 192.168.28.2 PING 192.168.28.2 (192.168.28.2): 56 data bytes 64 bytes from 192.168.28.2: icmp_seq=0 ttl=64 time=0.511 ms I received in secure.log following: Nov 8 01:54:46 border kernel: ipfw: 10 Accept ICMP:8.0 192.168.28.3 192.168.28.2 in via fxp1 Nov 8 01:54:46 border kernel: ipfw: 10 Accept ICMP:8.0 192.168.28.3 192.168.28.2 in via fxp1 Nov 8 01:54:46 border kernel: ipfw: 10 Accept ICMP:0.0 192.168.28.2 192.168.28.3 out via fxp1 Nov 8 01:54:46 border kernel: ipfw: 10 Accept ICMP:0.0 192.168.28.2 192.168.28.3 out via fxp1 The same situation with the tcp protocol. Kernel's conf is in the attach. May I missed something? -- Best regards, Elkhanzade Sarkhan machine i386 cpu I586_CPU ident FIREWALL options SCHED_4BSD # 4BSD scheduler options INET# InterNETworking options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options PSEUDOFS# Pseudo-filesystem framework options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV# install a CDEV entry in /dev options ADAPTIVE_GIANT # Giant mutex is adaptive. # AMD K6 options CPU_WT_ALLOC options NO_MEMORY_HOLE device apic# I/O APIC device isa device eisa device pci # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device atapist # ATAPI tape drives options ATA_STATIC_ID # Static device numbering # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device vga # VGA video card driver device sc # Floating point support - do not disable. device npx # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support device fxp # Intel EtherExpress PRO/100B (82557, 82558) # Pseudo devices. device loop# Network loopback device mem # Memory and kernel memory devices device io # I/O device device random # Entropy device device ether # Ethernet support device pty # Pseudo-ttys (telnet etc) #device carp #device pf #device pflog #device pfsync device bpf # Berkeley packet filter options IPFIREWALL options IPFIREWALL_FORWARD device carp___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OT: Failure notices from blogger.com
On Mon, Nov 07, 2005 at 05:48:42PM +0100, Michael Nottebrock wrote: I recently started to get failure notices from [EMAIL PROTECTED] when I post on the freebsd-stable mailing list. What is that all about? Is somebody redirecting all mail on the list to a blog via post-by-mail? If so, FYI: blogger.com does not like pgp signatures and it insists on telling me about it again and again. I'm not particularly amused. I'm seeing this too from questions@, and since I was unable to contact a human at blogger.com (postmaster@ returns a postfix error, and no other contact email is provided on their site) I just procmailed all blogger.com emails to /dev/null. Kris pgpc0TB6Wolnk.pgp Description: PGP signature
Fwd: carp + ipfw problem
Just realized that my replay address is not working :-( Sorry for double posting. -- Forwarded Message -- Subject: carp + ipfw problem Date: Tuesday 08 November 2005 02:10 From: Sarxan Elxanzade [EMAIL PROTECTED] To: [EMAIL PROTECTED], Max Laier [EMAIL PROTECTED] Cc: Rauf Kuliyev [EMAIL PROTECTED] Hello all, I'm trying to configure a firewall with carp + ipfw, but I encountered the strange problem. Packets are bypassing carp interface, instead ipfw log shows packet flow to/from physical interface, e.g.: FreeBSD host 5.4-RELEASE-p7 FreeBSD 5.4-RELEASE-p7 #6: Tue Sep 27 16:32:30 AZST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/FIREWALL i386 # ifconfig fxp1 fxp1: flags=9943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,LINK0,MULTICAST mtu 1500 options=8VLAN_MTU inet 192.168.28.1 netmask 0xff00 broadcast 192.168.28.255 media: Ethernet 100baseTX full-duplex status: active # ifconfig carp1 carp1: flags=41UP,RUNNING mtu 1500 inet 192.168.28.2 netmask 0xff00 carp: MASTER vhid 4 advbase 1 advskew 0 # ipfw show 1 0 0 check-state 2 0 0 allow ip from any to any via lo0 00010 0 0 allow log icmp from any to any 00020 4 344 allow log tcp from any to any 00030 0 0 allow log udp from any to any 65534 0 0 allow ip from any to any 65535 0 0 deny ip from any to any When I ping the IP address assigned to carp1 interface from host within the same network # ping 192.168.28.2 PING 192.168.28.2 (192.168.28.2): 56 data bytes 64 bytes from 192.168.28.2: icmp_seq=0 ttl=64 time=0.511 ms I received in secure.log following: Nov 8 01:54:46 border kernel: ipfw: 10 Accept ICMP:8.0 192.168.28.3 192.168.28.2 in via fxp1 Nov 8 01:54:46 border kernel: ipfw: 10 Accept ICMP:8.0 192.168.28.3 192.168.28.2 in via fxp1 Nov 8 01:54:46 border kernel: ipfw: 10 Accept ICMP:0.0 192.168.28.2 192.168.28.3 out via fxp1 Nov 8 01:54:46 border kernel: ipfw: 10 Accept ICMP:0.0 192.168.28.2 192.168.28.3 out via fxp1 The same situation with the tcp protocol. Kernel's conf is in the attach. May I missed something? -- Best regards, Elkhanzade Sarkhan --- -- Elkhanzade Sarkhan Azerin ISP, U.Hajibeyov 36, Baku Systems Administrator Phone work : +994124982533 e-mail : [EMAIL PROTECTED] machine i386 cpu I586_CPU ident FIREWALL options SCHED_4BSD # 4BSD scheduler options INET# InterNETworking options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options PSEUDOFS# Pseudo-filesystem framework options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV# install a CDEV entry in /dev options ADAPTIVE_GIANT # Giant mutex is adaptive. # AMD K6 options CPU_WT_ALLOC options NO_MEMORY_HOLE device apic# I/O APIC device isa device eisa device pci # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device atapist # ATAPI tape drives options ATA_STATIC_ID # Static device numbering # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device vga # VGA video card driver device sc # Floating point support - do not disable. device npx # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support device fxp # Intel EtherExpress PRO/100B (82557, 82558) # Pseudo devices. device loop# Network loopback device mem # Memory and kernel memory devices device io # I/O device device random # Entropy device device ether # Ethernet support device pty # Pseudo-ttys (telnet etc) #device carp #device pf #device pflog #device pfsync device bpf # Berkeley packet filter options IPFIREWALL options IPFIREWALL_FORWARD device carp___ freebsd-stable@freebsd.org mailing list
Fwd: carp + ipfw problem
It too late now, may be I need to get some sleep. Sorry again... -- Forwarded Message -- Subject: carp + ipfw problem Date: Tuesday 08 November 2005 02:10 From: Sarxan Elxanzade [EMAIL PROTECTED] To: [EMAIL PROTECTED], Max Laier [EMAIL PROTECTED] Cc: Rauf Kuliyev [EMAIL PROTECTED] Hello all, I'm trying to configure a firewall with carp + ipfw, but I encountered the strange problem. Packets are bypassing carp interface, instead ipfw log shows packet flow to/from physical interface, e.g.: FreeBSD host 5.4-RELEASE-p7 FreeBSD 5.4-RELEASE-p7 #6: Tue Sep 27 16:32:30 AZST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/FIREWALL i386 # ifconfig fxp1 fxp1: flags=9943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,LINK0,MULTICAST mtu 1500 options=8VLAN_MTU inet 192.168.28.1 netmask 0xff00 broadcast 192.168.28.255 media: Ethernet 100baseTX full-duplex status: active # ifconfig carp1 carp1: flags=41UP,RUNNING mtu 1500 inet 192.168.28.2 netmask 0xff00 carp: MASTER vhid 4 advbase 1 advskew 0 # ipfw show 1 0 0 check-state 2 0 0 allow ip from any to any via lo0 00010 0 0 allow log icmp from any to any 00020 4 344 allow log tcp from any to any 00030 0 0 allow log udp from any to any 65534 0 0 allow ip from any to any 65535 0 0 deny ip from any to any When I ping the IP address assigned to carp1 interface from host within the same network # ping 192.168.28.2 PING 192.168.28.2 (192.168.28.2): 56 data bytes 64 bytes from 192.168.28.2: icmp_seq=0 ttl=64 time=0.511 ms I received in secure.log following: Nov 8 01:54:46 border kernel: ipfw: 10 Accept ICMP:8.0 192.168.28.3 192.168.28.2 in via fxp1 Nov 8 01:54:46 border kernel: ipfw: 10 Accept ICMP:8.0 192.168.28.3 192.168.28.2 in via fxp1 Nov 8 01:54:46 border kernel: ipfw: 10 Accept ICMP:0.0 192.168.28.2 192.168.28.3 out via fxp1 Nov 8 01:54:46 border kernel: ipfw: 10 Accept ICMP:0.0 192.168.28.2 192.168.28.3 out via fxp1 The same situation with the tcp protocol. Kernel's conf is in the attach. May I missed something? -- Best regards, Elkhanzade Sarkhan --- -- Elkhanzade Sarkhan Azerin ISP, U.Hajibeyov 36, Baku Systems Administrator Phone work : +994124982533 e-mail : [EMAIL PROTECTED] machine i386 cpu I586_CPU ident FIREWALL options SCHED_4BSD # 4BSD scheduler options INET# InterNETworking options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options PSEUDOFS# Pseudo-filesystem framework options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV# install a CDEV entry in /dev options ADAPTIVE_GIANT # Giant mutex is adaptive. # AMD K6 options CPU_WT_ALLOC options NO_MEMORY_HOLE device apic# I/O APIC device isa device eisa device pci # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device atapist # ATAPI tape drives options ATA_STATIC_ID # Static device numbering # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device vga # VGA video card driver device sc # Floating point support - do not disable. device npx # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support device fxp # Intel EtherExpress PRO/100B (82557, 82558) # Pseudo devices. device loop# Network loopback device mem # Memory and kernel memory devices device io # I/O device device random # Entropy device device ether # Ethernet support device pty # Pseudo-ttys (telnet etc) #device carp #device pf #device pflog #device pfsync device bpf # Berkeley packet filter options IPFIREWALL options IPFIREWALL_FORWARD device carp___ freebsd-stable@freebsd.org mailing list
Tun and ALTQ
Resend...
Please, does anyone have any ideas...
What is the status of the tun0 driver and ALTQ ?
I have FreeBSD 6.0-RELEASE and have tried it without success. Why 6.0 ?
Don't know... curious maybe... if you think, that 5.4 will work better,
I'll reinstall it.
The tun0 is because od xDSL ( PPPoE )
It seems like packets won't match queue. Look at the pfctl output ( look
at the bucy rules -- he is a huge consumer and the primary uplink is
out for a week, xDSL is only backup and he consumes all the avail
bandwidth )
THIS IFACE IS TUN0 ( pppoe )
queue root_em0 bandwidth 1Gb priority 0 cbq( wrr root ) {std_ext, bucy_out}
[ pkts: 76053 bytes:7390221 dropped pkts: 0 bytes:
0 ]
[ qlength: 0/ 50 borrows: 0 suspends: 0 ]
[ measured: 199.0 packets/s, 146.71Kb/s ]
queue std_ext bandwidth 384Kb cbq( default )
[ pkts: 76053 bytes:7390221 dropped pkts: 0 bytes:
0 ]
[ qlength: 0/ 50 borrows: 0 suspends: 59 ]
[ measured: 199.0 packets/s, 146.71Kb/s ]
THIS ONE IS PROBLEMATIC - Won't match
queue bucy_out bandwidth 128Kb
[ pkts: 0 bytes: 0 dropped pkts: 0 bytes:
0 ]
[ qlength: 0/ 50 borrows: 0 suspends: 0 ]
[ measured: 0.0 packets/s, 0 b/s ]
queue root_em1 bandwidth 1Gb priority 0 cbq( wrr root ) {std_int, bucy_in}
[ pkts: 91920 bytes: 100394990 dropped pkts: 0 bytes:
0 ]
[ qlength: 0/ 50 borrows: 0 suspends: 0 ]
[ measured: 260.4 packets/s, 2.37Mb/s ]
queue std_int bandwidth 2Mb cbq( default )
[ pkts: 50302 bytes: 58076735 dropped pkts: 0 bytes:
0 ]
[ qlength: 0/ 50 borrows: 0 suspends: 2359 ]
[ measured: 194.6 packets/s, 1.89Mb/s ]
queue bucy_in bandwidth 900Kb
[ pkts: 41618 bytes: 42318255 dropped pkts:446 bytes:
433317 ]
[ qlength: 0/ 50 borrows: 0 suspends: 7440 ]
[ measured:65.8 packets/s, 475.89Kb/s ]
queue root_dc0 bandwidth 10Mb priority 0 cbq( wrr root ) {std_int_wifi_in}
[ pkts: 3967 bytes:1730908 dropped pkts: 0 bytes:
0 ]
[ qlength: 0/ 50 borrows: 0 suspends: 0 ]
[ measured: 2.6 packets/s, 4.17Kb/s ]
queue std_int_wifi_in bandwidth 5Mb cbq( default )
[ pkts: 3967 bytes:1730908 dropped pkts: 0 bytes:
0 ]
[ qlength: 0/ 50 borrows: 0 suspends: 0 ]
[ measured: 2.6 packets/s, 4.17Kb/s ]
This are the rules:
##
# QUEUEING: rule-based bandwidth control.
###
# TOLE JE NAS ODHODNI PROMET VEN - UPLOAD
altq on em0 cbq bandwidth 100% queue { std_ext,bucy_out }
queue std_ext bandwidth 384Kb cbq(default)
queue bucy_out bandwidth 128Kb
#
# TOLE JE NAS DOHODNI PROMER NOTRI - DOWNLOAD
altq on em1 cbq bandwidth 100% queue { std_int,bucy_in }
queue std_int bandwidth 2Mb cbq(default)
queue bucy_in bandwidth 900Kb
# QUEUE rule
pass in log on em1 from 10.0.100.0/24 to any queue bucy_out
pass out log on em1 from any to 10.0.100.0/24 queue bucy_in
Many thanks for any informations. I have changed the various eth cards,
from dc cards to em gigabit cards, etc, etc. Without success. I know,
that there has been some issues with tun0 on OpenBSD, but that was a
little time ago.
Cuk
--
NetInet d.o.o. http://www.NetInet.si
Private: http://cuk.nu
MountainBikeSlovenia team: http://mtb.si
Slovenian FreeBSD mirror admin http://www2.si.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: AGP ceased to work on eMachines M5310 laptop
On Monday 07 November 2005 05:18 pm, Mike Jakubik wrote: On Mon, November 7, 2005 11:49 am, Jung-uk Kim wrote: Please send me 'pciconf -lv' output. Here it is, thanks. -- [EMAIL PROTECTED]:0:0:class=0x06 card=0x chip=0xcab01002 rev=0x13 hdr=0x00 vendor = 'ATI Technologies Inc' device = 'A3/U1 S2K CPU to PCI Bridge' class= bridge subclass = HOST-PCI The driver exists on -CURRENT but it was not MFC'd before release. http://docs.freebsd.org/cgi/mid.cgi?200509170336.j8H3alVZ083992 Jung-uk Kim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: New user confused by need to do huge upgrade
On Monday 07 November 2005 15:49, Alistair wrote: Hello, All I am a user of Linux for many years (and an aged BSD sysadmin from 1985-1989), but laterly mainly use Gentoo. FreeBSD seemed to be a good alternative, so I get the 6.0 release a few days after it was released. Being a Gentoo person, I like the ports system, but with limited time on my hands, I also like the compiled packages. I can get a working system from packages then compile my own ports as need or want be. Or so I thought. I installed from two CDs, and got a working KDE system. Now, I want to do Firefox from ports with my own make.conf for P4 optimisation. Good! So, I sync with the sources using cvsup (just like emerge --sync) change to the Firefox ports directory, type make and enter dependency hell like has never been known before. Everything that depends upon GTK2 must be updated before Firefox can be compiled! If you don't want to do an entire upgrade of gnome2 or KDE but just get Firefox right install sysutils/portmanager (version 0.3.2 is in ports right now) then run portmanager www/firefox It will upgrade the dependencies that just pertain to firefox first then either upgrade firefox or install it if you don't have it yet. When version 0.3.3 of portmanager gets into the ports tree (pr is submitted) you can do the entire kde/gnome upgrade with just portmanager -u -Mike I thought that FreeBSD would be more stable than Gentoo and Linux distros in general. I now find that there is the most major release step (5.4 to 6.0) and within a matter of a few days later, both Gnome and KDE are subject to huge updates that require many hours (or maybe days - it's not done yet) of CPU time. Maybe I am missing something. However, I just cannot see why this is right. What I thought that FreeBSD would give me that Gentoo did not is a coherent system within which deveopment was co-ordinated. Instead, I seem to find the opposite. The core group can offer a major release of the OS, while missing the fact that two hugely important development groups are just days off their own major releases. Maybe there is a level of sanity I am missing as a newcomer to BSD, but I would really like someone to tell me where to find it so that I can stop having to use this bloody Windows laptop to post here ;-) Regards A ___ 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: New user confused by need to do huge upgrade
Alistair wrote: Hello, All Hi, Maybe there is a level of sanity I am missing as a newcomer to BSD, but I would really like someone to tell me where to find it so that I can stop having to use this bloody Windows laptop to post here ;-) Have a look at the sysutils/portupgrade port - that should solve all your problems in a jiffy (or however long it takes to recompile/redownload the packages/ports you need :) Regards, Søren Klintrup ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: New user confused by need to do huge upgrade
On Tue, 08 Nov 2005 00:49:18 +0100, Alistair [EMAIL PROTECTED] wrote: Hello, All I am a user of Linux for many years (and an aged BSD sysadmin from 1985-1989), but laterly mainly use Gentoo. FreeBSD seemed to be a good alternative, so I get the 6.0 release a few days after it was released. Being a Gentoo person, I like the ports system, but with limited time on my hands, I also like the compiled packages. I can get a working system from packages then compile my own ports as need or want be. Or so I thought. I installed from two CDs, and got a working KDE system. Now, I want to do Firefox from ports with my own make.conf for P4 optimisation. Good! So, I sync with the sources using cvsup (just like emerge --sync) change to the Firefox ports directory, type make and enter dependency hell like has never been known before. Everything that depends upon GTK2 must be updated before Firefox can be compiled! I thought that FreeBSD would be more stable than Gentoo and Linux distros in general. I now find that there is the most major release step (5.4 to 6.0) and within a matter of a few days later, both Gnome and KDE are subject to huge updates that require many hours (or maybe days - it's not done yet) of CPU time. Maybe I am missing something. However, I just cannot see why this is right. What I thought that FreeBSD would give me that Gentoo did not is a coherent system within which deveopment was co-ordinated. Instead, I seem to find the opposite. The core group can offer a major release of the OS, while missing the fact that two hugely important development groups are just days off their own major releases. The portstree is tagged for a release, so if you cvsup to the tag for the release, you get the 'supported' ports. If you cvsup to the most recent portstree there is always a change for a big update. The idea behind the KDE/GNOME update is to commit the stuff after the 6.0-RELEASE in stead of before too have stable KDE/GNOME packages in the release. BTW: use the port sysutils/portupgrade. This fixes a lot of dependency troubles. BTW2: if you cvsup to the latest portstree, you can't expect everything to be available in packages. In FreeBSD ports are the focus, packages come next (currently). BTW3: http://www.freshports.org/ Ronald. -- Ronald Klop Amsterdam, The Netherlands ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Sendmail not compiling with make world in 6.0
I get this error when trying to do a make world with FreeBSD 6.0. === libexec/mail.local (all) cc -O2 -fno-strict-aliasing -pipe -I/usr/src/libexec/ mail.local/../../contrib/sendmail/include -I. -I/usr/local/include/ sasl1 -DSASL -c /usr/src/libexec/mail.local/../../contrib/sendmail/ mail.local/mail.local.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/libexec/ mail.local/../../contrib/sendmail/include -I. -I/usr/local/include/ sasl1 -DSASL -L/usr/local/lib -o mail.local mail.local.o /usr/obj/ usr/src/libexec/mail.local/../../lib/libsm/libsm.a -lsasl /usr/obj/usr/src/tmp/usr/bin/ld: warning: libcrypt.so.2, needed by / usr/local/lib/libsasl.so, not found (try using -rpath or -rpath-link) /usr/obj/usr/src/tmp/usr/bin/ld: warning: libpam.so.2, needed by /usr/ local/lib/libsasl.so, not found (try using -rpath or -rpath-link) /usr/local/lib/libsasl.so: undefined reference to `pam_end' /usr/local/lib/libsasl.so: undefined reference to `pam_authenticate' /usr/local/lib/libsasl.so: undefined reference to `crypt' /usr/local/lib/libsasl.so: undefined reference to `pam_start' *** Error code 1 Stop in /usr/src/libexec/mail.local. *** Error code 1 I have the following in my /etc/make.conf SENDMAIL_CFLAGS=-I/usr/local/include/sasl1 -DSASL SENDMAIL_LDFLAGS=-L/usr/local/lib SENDMAIL_LDADD=-lsasl Any clues on why this is failing with 6.0? It worked in 5.4 no problem... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: New user confused by need to do huge upgrade
I installed from two CDs, and got a working KDE system. Now, I want to do Firefox from ports with my own make.conf for P4 optimisation. Good! So, I sync with the sources using cvsup (just like emerge --sync) change to the Firefox ports directory, type make and enter dependency hell like has never been known before. Everything that depends upon GTK2 must be updated before Firefox can be compiled! I thought that FreeBSD would be more stable than Gentoo and Linux distros in general. I now find that there is the most major release step (5.4 to 6.0) and within a matter of a few days later, both Gnome and KDE are subject to huge updates that require many hours (or maybe days - it's not done yet) of CPU time. Maybe I am missing something. However, I just cannot see why this is right. What I thought that FreeBSD would give me that Gentoo did not is a coherent system within which deveopment was co-ordinated. Instead, I seem to find the opposite. The core group can offer a major release of the OS, while missing the fact that two hugely important development groups are just days off their own major releases. Maybe there is a level of sanity I am missing as a newcomer to BSD, but I would really like someone to tell me where to find it so that I can stop having to use this bloody Windows laptop to post here ;-) Heh, essentially the problem is this... before a release, the ports tree is stabalized... everything builds and works together, broken dependencies are fixed, all is good with the world. This is the ports tree which is included in the release. After the release, More Stuff (tm) is added/updated/etc. By doing a cvsup, you asked for the newest version of all the ports, one which is not necessarily stable... dependencies may be broken, things may not work etc. Doing a cvsup in ports is like tracking -STABLE for ports. If you had not done the cvsup, FF would have built and installed nicely. IMHO, CVSupping ports is subject to the same caveats as tracking -STABLE (See section 20.2.2 in the handbook) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Tun and ALTQ
On Tue, Nov 08, 2005 at 12:00:32AM +0100, Marko Cuk wrote:
Resend...
Please, does anyone have any ideas...
What is the status of the tun0 driver and ALTQ ?
I have FreeBSD 6.0-RELEASE and have tried it without success. Why 6.0 ?
Don't know... curious maybe... if you think, that 5.4 will work better,
I'll reinstall it.
The tun0 is because od xDSL ( PPPoE )
It seems like packets won't match queue. Look at the pfctl output ( look
at the bucy rules -- he is a huge consumer and the primary uplink is
out for a week, xDSL is only backup and he consumes all the avail
bandwidth )
THIS IFACE IS TUN0 ( pppoe )
queue root_em0 bandwidth 1Gb priority 0 cbq( wrr root ) {std_ext, bucy_out}
[ pkts: 76053 bytes:7390221 dropped pkts: 0 bytes:
0 ]
[ qlength: 0/ 50 borrows: 0 suspends: 0 ]
[ measured: 199.0 packets/s, 146.71Kb/s ]
No it isn't, it's em0. You probably want to be using ALTQ on tun0.
I've done it; it works
--
Brian Fundakowski Feldman \'[ FreeBSD ]''\
[EMAIL PROTECTED] \ The Power to Serve! \
Opinions expressed are my own. \,,\
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sendmail not compiling with make world in 6.0
On Mon, Nov 07, 2005 at 07:28:06PM -0500, sammy!!! wrote: I get this error when trying to do a make world with FreeBSD 6.0. === libexec/mail.local (all) cc -O2 -fno-strict-aliasing -pipe -I/usr/src/libexec/ mail.local/../../contrib/sendmail/include -I. -I/usr/local/include/ sasl1 -DSASL -c /usr/src/libexec/mail.local/../../contrib/sendmail/ mail.local/mail.local.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/libexec/ mail.local/../../contrib/sendmail/include -I. -I/usr/local/include/ sasl1 -DSASL -L/usr/local/lib -o mail.local mail.local.o /usr/obj/ usr/src/libexec/mail.local/../../lib/libsm/libsm.a -lsasl /usr/obj/usr/src/tmp/usr/bin/ld: warning: libcrypt.so.2, needed by / usr/local/lib/libsasl.so, not found (try using -rpath or -rpath-link) /usr/obj/usr/src/tmp/usr/bin/ld: warning: libpam.so.2, needed by /usr/ local/lib/libsasl.so, not found (try using -rpath or -rpath-link) /usr/local/lib/libsasl.so: undefined reference to `pam_end' /usr/local/lib/libsasl.so: undefined reference to `pam_authenticate' /usr/local/lib/libsasl.so: undefined reference to `crypt' /usr/local/lib/libsasl.so: undefined reference to `pam_start' *** Error code 1 Stop in /usr/src/libexec/mail.local. *** Error code 1 I have the following in my /etc/make.conf SENDMAIL_CFLAGS=-I/usr/local/include/sasl1 -DSASL SENDMAIL_LDFLAGS=-L/usr/local/lib SENDMAIL_LDADD=-lsasl Any clues on why this is failing with 6.0? It worked in 5.4 no problem... You're still using your libsasl from 5.4. The warnings pretty unequivocally showed that it can't find the libraries it was originally linked against. -- Brian Fundakowski Feldman \'[ FreeBSD ]''\ [EMAIL PROTECTED] \ The Power to Serve! \ Opinions expressed are my own. \,,\ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.x, 6.x and CPUTYPE
I always build my production servers with CPUTYPE=i686 so they can be transplanted to any machine with a PPro or better processor (or even qemu if necessary). Thanks, Craig. I'm glad to hear that I'm not alone in pursuing this method. Do you know of any particular disadvantages of continuing with this less-than-optimised model - I guess I mean, is this something that is likely to break or become uneconomical at some point? cheers, joel -- Joel Hatton -- Security Analyst| Hotline: +61 7 3365 4417 AusCERT - Australia's national CERT | Fax: +61 7 3365 7031 The University of Queensland| WWW: www.auscert.org.au Qld 4072 Australia | Email: [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: 5.x, 6.x and CPUTYPE
I always build my production servers with CPUTYPE=i686 so they can be transplanted to any machine with a PPro or better processor (or even qemu if necessary). Thanks, Craig. I'm glad to hear that I'm not alone in pursuing this method. Do you know of any particular disadvantages of continuing with this less-than-optimised model - I guess I mean, is this something that is likely to break or become uneconomical at some point? For packages, it's a good idea to make a build jail... in case of static linking goodness. I had packages bite me when I was building them all on a system with a CPUTYPE=p3 world. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: AGP ceased to work on eMachines M5310 laptop
Jung-uk Kim wrote: On Monday 07 November 2005 05:18 pm, Mike Jakubik wrote: On Mon, November 7, 2005 11:49 am, Jung-uk Kim wrote: Please send me 'pciconf -lv' output. Here it is, thanks. -- [EMAIL PROTECTED]:0:0:class=0x06 card=0x chip=0xcab01002 rev=0x13 hdr=0x00 vendor = 'ATI Technologies Inc' device = 'A3/U1 S2K CPU to PCI Bridge' class= bridge subclass = HOST-PCI The driver exists on -CURRENT but it was not MFC'd before release. http://docs.freebsd.org/cgi/mid.cgi?200509170336.j8H3alVZ083992 Any ideas why? I can remember DRM working on an earlier 5.x however, which has me confused. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.x, 6.x and CPUTYPE
On Tue, Nov 08, 2005 at 12:05:13PM +1000, Joel Hatton wrote: Thanks, Craig. I'm glad to hear that I'm not alone in pursuing this method. Do you know of any particular disadvantages of continuing with this less-than-optimised model - I guess I mean, is this something that is likely to break or become uneconomical at some point? It won't break; after all the release binaries are targeted for 386 (or maybe 486 now) in order to be able to run on anything. You might need to update make.conf with the pentiumpro name just in case they ever drop the i686 alias, but that's about it. You might not get quite as good performance as if you compiled for exactly your CPU (keep in mind we're probably talking about 1-2% at most unless you have a VERY specific workload that SSE could benefit), but IMO it's more than worth it to be able to plug the hard drives into a similar machine and have things Just Work. Personally, I pick i686 (pentiumpro) as a good middle ground. The features optimized for by that are present in every modern x86-architecture CPU: P2, P3, P4, Athlon, etc. So it's unlikely you'll run into something older than that. Also, the ppro has most of the features that really affect performance -- i.e. the gap between 386/486 and 686 is a lot bigger than the gap between 686 and P3/P4. P3s/P-M and Athlons especially are fairly smart and will optimize a lot of things at runtime. P4s are probably where you'll see the biggest performance hit -- that's where Intel tried to push a lot off it off on the compiler. Craig ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel Crash using GDB
On Sat, Nov 05, 2005 at 10:30:01PM -0500, Rod Taylor wrote: Upgraded FreeBSD to 6.0 Release. Upgraded Gnome to 2.12, Abiword 2.4.1 Abiword is crashes while trying to save files for some unknown reason so I recompiled it WITH_DEBUG=YES. Open abiword from command line (abiword ) and attach and GDB process to the abiword process. Click Save in Abiword, which usually crashes Abiword but with GDB attached the kernel panics and reboots immediately. I'm not really sure what to do now but I can reproduce the crash every time. Try running AbiWord using another computer as your X server, and make the FreeBSD 6 machine stay at the console so it can potentially hit DDB/KDB. A serial console is also helpful sometimes. -- Brian Fundakowski Feldman \'[ FreeBSD ]''\ [EMAIL PROTECTED] \ The Power to Serve! \ Opinions expressed are my own. \,,\ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OT: Failure notices from blogger.com
On Mon, Nov 07, 2005 at 10:39:08PM +0100, Dimitry Andric wrote: ... So someone probably subscribed one or more @blogger.com addresses to this, and other FreeBSD mailing lists. %../bin/find_member blogger.com %../bin/find_member @blogger.com % Apparently someone is subscribed via an address that is forwarded to blogger.com. Unfortunately, that's the point where I no longer have control. I could block all mail from blogger.com to mx1.freebsd.org, but some folks might take exception However: IMO, this is all off-topic to the freebsd-stable list. Such meta-comments about list contents are welcome at [EMAIL PROTECTED], which is where I have hinted that replies should go. Peace, david (current hat: [EMAIL PROTECTED]) -- David H. Wolfskill [EMAIL PROTECTED] Prediction is difficult, especially if it involves the future. -- Niels Bohr See http://www.catwhisker.org/~david/publickey.gpg for public key. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.x, 6.x and CPUTYPE
Craig Boston wrote: On Tue, Nov 08, 2005 at 12:05:13PM +1000, Joel Hatton wrote: Thanks, Craig. I'm glad to hear that I'm not alone in pursuing this method. Do you know of any particular disadvantages of continuing with this less-than-optimised model - I guess I mean, is this something that is likely to break or become uneconomical at some point? It won't break; after all the release binaries are targeted for 386 (or maybe 486 now) in order to be able to run on anything. You might need to update make.conf with the pentiumpro name just in case they ever drop the i686 alias, but that's about it. Yes. Note that you should choose the lowest common denominator for the hardware you possibly might want to run the binaries on. pentium or pentiumpro are also good candidates in that they are well-tested targets compared with the p4 or Althon targets. You might not get quite as good performance as if you compiled for exactly your CPU (keep in mind we're probably talking about 1-2% at most unless you have a VERY specific workload that SSE could benefit), but IMO it's more than worth it to be able to plug the hard drives into a similar machine and have things Just Work. Agreed, although the performance difference depends a lot on the tasks being done. Disabling the cpu I386_CPU statement in the kernel conf seems to be more important than the difference between specifying a compiler architecture or leaving it to the default. Personally, I pick i686 (pentiumpro) as a good middle ground. The features optimized for by that are present in every modern x86-architecture CPU: P2, P3, P4, Athlon, etc. So it's unlikely you'll run into something older than that. Also, the ppro has most of the features that really affect performance -- i.e. the gap between 386/486 and 686 is a lot bigger than the gap between 686 and P3/P4. Agreed. The gap in performance is 386/486 486/586 later models. P3s/P-M and Athlons especially are fairly smart and will optimize a lot of things at runtime. P4s are probably where you'll see the biggest performance hit -- that's where Intel tried to push a lot off it off on the compiler. The P4 can benefit significantly sometimes from a compiler that knows how to schedule for it and the underlying microcode which actually implements the x86 instructions, rather than just for a generic pentium, but most of the time there isn't much difference between using pentium and pentium4. -- -Chuck ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: New user confused by need to do huge upgrade
On Mon, Nov 07, 2005 at 11:54:37PM +, Alistair wrote: Hello, All I am a user of Linux for many years (and an aged BSD sysadmin from 1985-1989), but laterly mainly use Gentoo. FreeBSD seemed to be a good alternative, so I get the 6.0 release a few days after it was released. Being a Gentoo person, I like the ports system, but with limited time on my hands, I also like the compiled packages. I can get a working system from packages then compile my own ports as need or want be. Or so I thought. I installed from two CDs, and got a working KDE system. Now, I want to do Firefox from ports with my own make.conf for P4 optimisation. Good! So, I sync with the sources using cvsup (just like emerge --sync) change to the Firefox ports directory, type make and enter dependency hell like has never been known before. Everything that depends upon GTK2 must be updated before Firefox can be compiled! I thought that FreeBSD would be more stable than Gentoo and Linux distros in general. I now find that there is the most major release step (5.4 to 6.0) and within a matter of a few days later, both Gnome and KDE are subject to huge updates that require many hours (or maybe days - it's not done yet) of CPU time. Maybe I am missing something. However, I just cannot see why this is right. What I thought that FreeBSD would give me that Gentoo did not is a coherent system within which deveopment was co-ordinated. Instead, I seem to find the opposite. The core group can offer a major release of the OS, while missing the fact that two hugely important development groups are just days off their own major releases. There was not a lack of communication. The updates to Gnome and KDE were intentionally delayed to happen *after* 6.0 was out. The reason for this is simply that they were not ready in time to make it into 6.0. The FreeBSD project has a policy of not allowing major changes to the ports tree while in the process of preparing for a new release. This is to make sure that the ports tree is in a known good state when the release happens. The Gnome and KDE teams could probably have updated their ports before 6.0 was released, but at that time the ports tree was frozen in preparation for the release. After 6.0 was out and the freeze was lifted, the ports were updated. Think of it this way: Do you really want binary packages that are brand new and almost untested to be included in the release, or do you want slightly older but well-tested programs to be included? The FreeBSD project has chosen the latter policy, which means that the Gnome and KDE updates did not make it into 6.0. A pattern that has been true for most FreeBSD releases is that in the days before the source/ports tree is frozen in preparation for a new release there is a flurry of last-minute commits to make sure they get into the release. Then after the release is out, and the freeze is lifted, there is a new flurry of commits when all the changes that have been pent up during the freeze are finally allowed into the tree. Maybe there is a level of sanity I am missing as a newcomer to BSD, but I would really like someone to tell me where to find it so that I can stop having to use this bloody Windows laptop to post here ;-) -- Insert your favourite quote here. Erik Trulsson [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD6 /bin/tcsh ls-F : Floating exception (core dumped)
tcsh 6.14.00 of FreeBSD 6-STABLE will crash by ls-F built-in command.
% /bin/tcsh
% cd /SOMEWHERE
% ls-F
Floating exception (core dumped)
If login shell is /bin/tcsh, this results in unintentional logout.
This problem occurs for example,
1. charset of filename is ja_JP.eucJP
2. LANG is not ja_JP.eucJP
3. run ls-F
This is not only the case.
GDB stack trace:
-
(gdb) where
#0 0x0806e947 in print_by_column (dir=0x80b9b94, items=0x8167c08, count=331,
no_file_suffix=1)
at /usr/src/bin/csh/../../contrib/tcsh/tw.parse.c:2071
#1 0x0806d993 in tw_list_items (looking=4, numitems=331, list_max=0)
at /usr/src/bin/csh/../../contrib/tcsh/tw.parse.c:1394
#2 0x0806e107 in t_search (word=0x80b9b94, wp=0x0, command=LIST,
max_word_length=0, looking=4, list_max=80, pat=0x80b9b94, suf=0)
at /usr/src/bin/csh/../../contrib/tcsh/tw.parse.c:1706
#3 0x0808119b in dolist (v=0x8135cbc, c=0x81677e8)
at /usr/src/bin/csh/../../contrib/tcsh/tc.func.c:251
#4 0x08056a2d in func (t=0x81677e8, bp=0x80909e0)
at /usr/src/bin/csh/../../contrib/tcsh/sh.func.c:152
#5 0x08065ab7 in execute (t=0x81677e8, wanttty=50551, pipein=0x0,
pipeout=0x0, do_glob=1)
at /usr/src/bin/csh/../../contrib/tcsh/sh.sem.c:650
#6 0x08065dd3 in execute (t=0x81652a8, wanttty=50551, pipein=0x0,
pipeout=0x0, do_glob=1)
at /usr/src/bin/csh/../../contrib/tcsh/sh.sem.c:721
#7 0x0804d081 in process (catch=1)
at /usr/src/bin/csh/../../contrib/tcsh/sh.c:2180
#8 0x0804bd8b in main (argc=0, argv=0xbfbfeb74)
at /usr/src/bin/csh/../../contrib/tcsh/sh.c:1362
-
signal comes from tw.parse.c:
columns = TermH / maxwidth; /* PWP: terminal size change */
^^^
There are cases when maxwidth == 0 !!!
maxwidth is computed by ...
maxwidth = max(maxwidth, (unsigned int) NLSStringWidth(items[i]));
and NLSStringWidth() is defined in tc.nls.c
int
NLSStringWidth(Char *s)
{
int w = 0;
while (*s)
w += wcwidth(*s++);
return w;
}
wcwidth() returns -1 when char is not printable depending LANG.
If LANG is not matched with coding set used as filenames,
wcwidth() will return -1.
So, int NLSStringWidth() might return negative value such as -1 or -2.
As a result, the next sentence in tw.parse.c
maxwidth += no_file_suffix ? 1 : 2; /* for the file tag and space */
makes maxwidth=0.
Here is a tiny patch.
-
--- tc.nls.c.orgTue Nov 8 14:13:22 2005
+++ tc.nls.cTue Nov 8 14:04:54 2005
@@ -89,8 +89,10 @@
NLSStringWidth(Char *s)
{
int w = 0;
-while (*s)
- w += wcwidth(*s++);
+while (*s) {
+ int tmp = wcwidth(*s++);
+ w += (tmp0) ? tmp : 0;
+}
return w;
}
-
--
---
TOMITA Yoshinori
(Fujitsu Laboratories Ltd., Kawasaki, Japan)
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD6 /bin/tcsh ls-F : Floating exception (core dumped)
On Tue, Nov 08, 2005 at 02:46:28PM +0900, TOMITA Yoshinori wrote: tcsh 6.14.00 of FreeBSD 6-STABLE will crash by ls-F built-in command. Here is a tiny patch. Thanks, but tcsh is a third-party utility that isn't separately maintained in FreeBSD; you should submit your patch to the tcsh authors for incorporation in the next release, and it can then be imported back into FreeBSD. Kris pgpnVTIPSYU4W.pgp Description: PGP signature
Re: New user confused by need to do huge upgrade
Alistair wrote: Hello, All I am a user of Linux for many years (and an aged BSD sysadmin from 1985-1989), but laterly mainly use Gentoo. FreeBSD seemed to be a good alternative, so I get the 6.0 release a few days after it was released. Being a Gentoo person, I like the ports system, but with limited time on my hands, I also like the compiled packages. I can get a working system from packages then compile my own ports as need or want be. Or so I thought. I installed from two CDs, and got a working KDE system. Now, I want to do Firefox from ports with my own make.conf for P4 optimisation. Good! So, I sync with the sources using cvsup (just like emerge --sync) change to the Firefox ports directory, type make and enter dependency hell like has never been known before. Everything that depends upon GTK2 must be updated before Firefox can be compiled! I thought that FreeBSD would be more stable than Gentoo and Linux distros in general. I now find that there is the most major release step (5.4 to 6.0) and within a matter of a few days later, both Gnome and KDE are subject to huge updates that require many hours (or maybe days - it's not done yet) of CPU time. Maybe I am missing something. However, I just cannot see why this is right. What I thought that FreeBSD would give me that Gentoo did not is a coherent system within which deveopment was co-ordinated. Instead, I seem to find the opposite. The core group can offer a major release of the OS, while missing the fact that two hugely important development groups are just days off their own major releases. Maybe there is a level of sanity I am missing as a newcomer to BSD, but I would really like someone to tell me where to find it so that I can stop having to use this bloody Windows laptop to post here ;-) Check out the UPDATING notes for anything about KDE cat /usr/ports/UPDATING | grep -A 13 -B 3 kde | grep -A 14 20051105 Update your ports tree, then portupgrade your KDE packages, portupgrade -Rk /var/db/pkg/kde-3.4.2 Go to sleep and wake up with the latest KDE and feel good about the fact that you aren't stealing from SCO compared to using Gentoo Linux :) Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
