Re: a place for configuration files
Andrzej Cuber wrote: ... In RedHat and Fedora distributions all configuration files are located at /etc. I am very new to FreeBSD but I found it difficult. After installing desired package I have to add it to /etc/rc.conf in order to start it as a service and then I have to look for configuration folder in /usr/local/etc. Is there any reason why the configuration files are placed in those different locations? If you want to be consistent you could add to /etc/rc.conf rc_conf_files=/etc/rc.conf /etc/rc.conf.local /usr/local/etc/rc.conf Then your startup variables could go into /usr/local/etc/rc.conf and all your ports config stuff would live in /usr/local/etc hierarchy. There maybe a problem if /usr/local/etc/rc.conf is on another partition not available early enough in startup process. Caveat emptor. and that's where early_late_divider=something comes in handy (thanks Doug B.) in my case I have early_late_divider=amd since /usr/local is am-utils mounted. danny ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
6.1-PRERELEASE SMP 2nd CPU idle
Dear All, today I have: 11 root 1 171 52 0K 8K CPU1 0 0:00 100.00% idle: cpu1 12 root 1 171 52 0K 8K RUN0 86.2H 43.95% idle: cpu0 cpu0 utilization so high but cpu1 utilization so low, any clue or tips how to utilize cpu1 ? regards, -dikshie- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ad4: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - on FreeBSD 6-STABLE
Have you tried it with a livecd or something? +++ Peter van Heusden [freebsd] [24/03/06 09:51 +0200]: Hi After my previous email about the SETFEATURES SET TRANSFER MODE timeout on (msgid [EMAIL PROTECTED] , 17 March 14:18 GMT + 2 on freebsd-stable), I installed FreeBSD 6.1 BETA 4 and upgraded to a 6-STABLE kernel, running the box in 'safe' mode to do so. I now, however, get a slightly different error message: ad4: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly ad4: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly ad4: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly ad4: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly ad4: WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing request directly ad4: WARNING - SET_MULTI taskqueue timeout - completing request directly ad4: FAILURE - WRITE_DMA timed out LBA=32804495 (The address after LBA is not always the same) This is with ad4 as a Seagate ST320423A on a Promise PDC20262 UDMA66 controller. Any suggestions? Thanks, Peter ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- b1tt3r -- You know, like sugar? Sam Stein Computer TeXnician/Programmer pgphwwtCAfkE4.pgp Description: PGP signature
pxe booting a Proliant DL145 (dual core amd) (fwd)
---BeginMessage--- From [EMAIL PROTECTED] Sun Mar 19 13:53:53 2006 Return-path: [EMAIL PROTECTED] Received: from mx2.freebsd.org ([216.136.204.119]) by cs.huji.ac.il with esmtp id 1FKwTm-000M0h-CF for [EMAIL PROTECTED]; Sun, 19 Mar 2006 13:53:50 +0200 Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id BCB2156B76; Sun, 19 Mar 2006 11:53:27 + (GMT) (envelope-from [EMAIL PROTECTED]) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 0E12116A44C; Sun, 19 Mar 2006 11:53:26 + (UTC) (envelope-from [EMAIL PROTECTED]) X-Original-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4DF7116A400 for [EMAIL PROTECTED]; Sun, 19 Mar 2006 11:53:18 + (UTC) (envelope-from [EMAIL PROTECTED]) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB69643D46 for [EMAIL PROTECTED]; Sun, 19 Mar 2006 11:53:17 + (GMT) (envelope-from [EMAIL PROTECTED]) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1FKwTE-00066c-VH for [EMAIL PROTECTED]; Sun, 19 Mar 2006 13:53:16 +0200 X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 19 Mar 2006 13:53:16 +0200 From: Danny Braniss [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] Subject: pxe booting a Proliant DL145 (dual core amd) X-BeenThere: [EMAIL PROTECTED] X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform freebsd-amd64.freebsd.org List-Unsubscribe: http://lists.freebsd.org/mailman/listinfo/freebsd-amd64, mailto:[EMAIL PROTECTED] List-Archive: http://lists.freebsd.org/pipermail/freebsd-amd64 List-Post: mailto:[EMAIL PROTECTED] List-Help: mailto:[EMAIL PROTECTED] List-Subscribe: http://lists.freebsd.org/mailman/listinfo/freebsd-amd64, mailto:[EMAIL PROTECTED] Sender: [EMAIL PROTECTED] Errors-To: [EMAIL PROTECTED] X-Bogosity: Unsure [50.0%] X-Authentication-Warning: Sender is not authenticated Hi, It seems that the pxe boot is running on more than once cpu! on the serial console i get: Consoles: serial port bootflags=2 bootinfo=0 --- my debug output BIOS drive C: is disk0 !PXE version 2.1, real mode entry point @91c8:00da BIOS 523kB/2095232kB available memory FreeBSD/i386 bootstrap loader, Revision 1.1 ([EMAIL PROTECTED], Sun Mar 19 13:16:17 IST 2006) pxe_open: server addr: 132.65.16.112 pxe_open: server path: /d/8 pxe_open: gateway ip: 132.65.80.1 and it gets stuck. on the VGA monitor: Consoles: internal video/keyboard bootflags=0 bootinfo=0--- my debug output BIOS drive C: is disk0 BIOS 523kB/2095232kB available memory FreeBSD/i386 bootstrap loader, Revision 1.1 ([EMAIL PROTECTED], Sun Mar 19 13:16:17 IST 2006) Can't work out which disk we are booting from Guessed BIOS device 0x not found by probes, defaulting to disk0: can't load 'kernel' Type '?' for a list of commands, 'help' for more detailed help. OK how can i get pxe boot to work? thanks, danny ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to [EMAIL PROTECTED] ---End Message--- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Reading via mmap stinks (Re: weird bugs with mmap-ing via NFS)
On Thu, 2006-Mar-23 15:16:11 -0800, Matthew Dillon wrote: FreeBSD. To determine which of the two is more likely, you have to run a smaller data set (like 600MB of data on a system with 1GB of ram), and use the unmount/mount trick to clear the cache before each grep test. On an amd64 system running about 6-week old -stable, both behave pretty much identically. In both cases, systat reports that the disk is about 96% busy whilst loading the cache. In the cache case, mmap is significantly faster. The test data is 2 copies of OOo_2.0.2rc2_src.tar.gz concatenated. turion% ls -l /6_i386/var/tmp/test -rw-r--r-- 1 peter wheel 586333684 Mar 24 19:24 /6_i386/var/tmp/test turion% /usr/bin/time -l grep dfhfhdsfhjdsfl /6_i386/var/tmp/test 21.69 real 0.16 user 0.68 sys 1064 maximum resident set size 82 average shared memory size 95 average unshared data size 138 average unshared stack size 119 page reclaims 0 page faults 0 swaps 4499 block input operations 0 block output operations 0 messages sent 0 messages received 0 signals received 4497 voluntary context switches 3962 involuntary context switches [umount/remount /6_i386/var] turion% /usr/bin/time -l grep --mmap dfhfhdsfhjdsfl /6_i386/var/tmp/test 21.68 real 0.41 user 0.51 sys 1068 maximum resident set size 80 average shared memory size 93 average unshared data size 136 average unshared stack size 17836 page reclaims 18081 page faults 0 swaps 23 block input operations 0 block output operations 0 messages sent 0 messages received 0 signals received 18105 voluntary context switches 169 involuntary context switches The speed gain with mmap is clearly evident when the data is cached and the CPU clock wound right down (99MHz ISO 2200MHz): turion% /usr/bin/time grep --mmap dfhfhdsfhjdsfl /6_i386/var/tmp/test 12.15 real 7.98 user 2.95 sys turion% /usr/bin/time grep --mmap dfhfhdsfhjdsfl /6_i386/var/tmp/test 12.28 real 7.92 user 2.94 sys turion% /usr/bin/time grep --mmap dfhfhdsfhjdsfl /6_i386/var/tmp/test 13.16 real 8.03 user 2.89 sys turion% /usr/bin/time grep dfhfhdsfhjdsfl /6_i386/var/tmp/test 17.09 real 6.37 user 8.92 sys turion% /usr/bin/time grep dfhfhdsfhjdsfl /6_i386/var/tmp/test 17.36 real 6.35 user 9.37 sys turion% /usr/bin/time grep dfhfhdsfhjdsfl /6_i386/var/tmp/test 17.54 real 6.37 user 9.39 sys -- Peter Jeremy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: gnokii on FreeBSD 6.0 and Dell PE 2850
Mar 22 08:41:38 nefarian kernel: sio0: 2 more silo overflows (total 16) This is often related to interrupt contention. Probably your new machine shares the IRQ of /dev/cuad0 with other devices. If another device hangs on the IRQ for too long, the cuad0 silo will overflow and you are losing characters, which probably cause the gnokii conversation with the phone to fail. Try tweaking your BIOS so that cuad0 doesn't share interrupts. I've seen other suggestions, such as fiddling with HZ and modifying sio.c but this one is probably the simplest. HTH Helge ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
New sysinstall in 6.1-PRE. make own release
Hi, all I need building my own install server and want install my custom world, custom kernel and other in non-interactive mode. With 6.1-beta3 it work in mass (I not try install my kernel). With 6.1-beta4 and more fresh I can't get non-interactive installation. 1. I can't find how to select timezone non-interactive. 2. I can't good variant for installing my own kernel (now I use command=/dist/my.custom.installer system /dist/my.custom.installer -- simple script: #!/bin/sh cd /dist/kernels ./install.sh OILSPACE1 rm -rf /boot/kernel ln -s /boot/OILSPACE1 /boot/kernel but it's hack. Also I have question about making my own release. I can't understand, how to create my own loader.conf for pxeboot. Default not work -- machine panic with no init diagnose. Reason -- need string in loader.conf: vfs.root.mountfrom=ufs:/dev/md0c (I need some another strings for my own loader.conf) For creating release I use command: make release BUILDNAME=6.1-PRERELEASE CHROOTDIR=/usr/release \ CVSROOT=/home/ncvs EXTSRCDIR=/usr/src KERNELS=OILSPACE1 \ LOCAL_PATCHES=/usr/src_local_patches NO_FLOPPIES=yes NO_ISOS=yes \ NODOC=yes NOPORTS=yes RELEASETAG=RELENG_6 KERNELS_BASE=OILSPACE1 \ GENERIC My local patches -- only new unionfs currently. install.cfg I put in /usr/src/release directory. Can anybody help me with auto-select timezone, right way for installing kernel and place in source tree for PXE loader.conf? WBR -- Dmitriy Kirhlarov OILspace, 26 Leninskaya sloboda, bld. 2, 2nd floor, 115280 Moscow, Russia P:+7 495 105 7247 ext.203 F:+7 495 105 7246 E:[EMAIL PROTECTED] OILspace - The resource enriched - www.oilspace.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: New sysinstall in 6.1-PRE. make own release
On Friday, 24 March 2006 at 17:09:36 +0300, Dmitriy Kirhlarov wrote: Hi, all I need building my own install server and want install my custom world, custom kernel and other in non-interactive mode. With 6.1-beta3 it work in mass (I not try install my kernel). With 6.1-beta4 and more fresh I can't get non-interactive installation. 1. I can't find how to select timezone non-interactive. You can find your timezone file in /usr/share/zoneinfo directory and copy it to /etc/localtime file. Next if your CMOS clock is set to local time you need to create empty file /etc/wall_cmos_clock. 2. I can't good variant for installing my own kernel (now I use command=/dist/my.custom.installer system /dist/my.custom.installer -- simple script: #!/bin/sh cd /dist/kernels ./install.sh OILSPACE1 rm -rf /boot/kernel ln -s /boot/OILSPACE1 /boot/kernel but it's hack. Also I have question about making my own release. I can't understand, how to create my own loader.conf for pxeboot. Default not work -- machine panic with no init diagnose. Reason -- need string in loader.conf: vfs.root.mountfrom=ufs:/dev/md0c (I need some another strings for my own loader.conf) For creating release I use command: make release BUILDNAME=6.1-PRERELEASE CHROOTDIR=/usr/release \ CVSROOT=/home/ncvs EXTSRCDIR=/usr/src KERNELS=OILSPACE1 \ LOCAL_PATCHES=/usr/src_local_patches NO_FLOPPIES=yes NO_ISOS=yes \ NODOC=yes NOPORTS=yes RELEASETAG=RELENG_6 KERNELS_BASE=OILSPACE1 \ GENERIC My local patches -- only new unionfs currently. install.cfg I put in /usr/src/release directory. Can anybody help me with auto-select timezone, right way for installing kernel and place in source tree for PXE loader.conf? WBR -- Dmitriy Kirhlarov OILspace, 26 Leninskaya sloboda, bld. 2, 2nd floor, 115280 Moscow, Russia P:+7 495 105 7247 ext.203 F:+7 495 105 7246 E:[EMAIL PROTECTED] OILspace - The resource enriched - www.oilspace.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- = Best regards, Nikolay Pavlov. --- = ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: New sysinstall in 6.1-PRE. make own release
Dmitriy Kirhlarov wrote: Hi, all I need building my own install server and want install my custom world, custom kernel and other in non-interactive mode. With 6.1-beta3 it work in mass (I not try install my kernel). With 6.1-beta4 and more fresh I can't get non-interactive installation. 1. I can't find how to select timezone non-interactive. 2. I can't good variant for installing my own kernel (now I use command=/dist/my.custom.installer system /dist/my.custom.installer -- simple script: #!/bin/sh cd /dist/kernels ./install.sh OILSPACE1 rm -rf /boot/kernel ln -s /boot/OILSPACE1 /boot/kernel but it's hack. It seems simpler to just setup OILSPACE1 as the GENERIC kernel on your install iso so everything else would work as intended. Doing that would require a small change to release/Makefile to make GENERIC a name you can set from the command line. I'm not sure when the custom installer script gets run but be sure to look at install.c:installFixupKernel as it might explain some of your problems. There was also a bug in the install.sh script that was fixed after BETA4. In general the recent changes for packaging+installing kernels should simplify _adding_ custom kernels to an install but not replacing GENERIC and/or SMP kernel configurations. Also I have question about making my own release. I can't understand, how to create my own loader.conf for pxeboot. Default not work -- machine panic with no init diagnose. Reason -- need string in loader.conf: vfs.root.mountfrom=ufs:/dev/md0c (I need some another strings for my own loader.conf) For creating release I use command: make release BUILDNAME=6.1-PRERELEASE CHROOTDIR=/usr/release \ CVSROOT=/home/ncvs EXTSRCDIR=/usr/src KERNELS=OILSPACE1 \ LOCAL_PATCHES=/usr/src_local_patches NO_FLOPPIES=yes NO_ISOS=yes \ NODOC=yes NOPORTS=yes RELEASETAG=RELENG_6 KERNELS_BASE=OILSPACE1 \ GENERIC KERNELS_BASE was not intended to be overridden as sysinstall has builtin knowledge about GENERIC and SMP. KERNELS is documented as a knob to set to add additional kernel configurations to an iso. My local patches -- only new unionfs currently. install.cfg I put in /usr/src/release directory. Can anybody help me with auto-select timezone, right way for installing kernel and place in source tree for PXE loader.conf? I don't know about the timezone setting. Hopefully the above helps with setting up a custom kernel. FWIW I used qemu to test the release+sysinstall changes (in case you aren't aware of it). Sam ___ 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-PRERELEASE SMP 2nd CPU idle
On Fri, Mar 24, 2006 at 03:25:42PM +0700, Dikshie wrote: Dear All, today I have: 11 root 1 171 52 0K 8K CPU1 0 0:00 100.00% idle: cpu1 12 root 1 171 52 0K 8K RUN0 86.2H 43.95% idle: cpu0 cpu0 utilization so high but cpu1 utilization so low, any clue or tips how to utilize cpu1 ? Is it really a second CPU, or hyperthreading on a single CPU? Kris pgp1b0wRWBxM0.pgp Description: PGP signature
Re: Reading via mmap stinks (Re: weird bugs with mmap-ing via NFS)
:On an amd64 system running about 6-week old -stable, both behave :pretty much identically. In both cases, systat reports that the disk :is about 96% busy whilst loading the cache. In the cache case, mmap :is significantly faster. : :... :turion% ls -l /6_i386/var/tmp/test :-rw-r--r-- 1 peter wheel 586333684 Mar 24 19:24 /6_i386/var/tmp/test :turion% /usr/bin/time -l grep dfhfhdsfhjdsfl /6_i386/var/tmp/test : 21.69 real 0.16 user 0.68 sys :[umount/remount /6_i386/var] :turion% /usr/bin/time -l grep --mmap dfhfhdsfhjdsfl /6_i386/var/tmp/test : 21.68 real 0.41 user 0.51 sys :The speed gain with mmap is clearly evident when the data is cached and :the CPU clock wound right down (99MHz ISO 2200MHz): :... :-- :Peter Jeremy That pretty much means that the read-ahead algorithm is working. If it weren't, the disk would not be running at near 100%. Ok. The next test is to NOT do umount/remount and then use a data set that is ~2x system memory (but can still be mmap'd by grep). Rerun the data set multiple times using grep and grep --mmap. If the times for the mmap case blow up relative to the non-mmap case, then the vm_page_alloc() calls and/or vm_page_count_severe() (and other tests) in the vm_fault case are causing the read-ahead to drop out. If this is the case the problem is not in the read-ahead path, but probably in the pageout code not maintaining a sufficient number of free and cache pages. The system would only be allocating ~60MB/s (or whatever your disk can do), so the pageout thread ought to be able to keep up. If the times for the mmap case do not blow up, we are back to square one and I would start investigating the disk driver that Mikhail is using. -Matt Matthew Dillon [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 sysinstall in 6.1-PRE. make own release
On Fri, Mar 24, 2006 at 06:57:51PM +0200, Nikolay Pavlov wrote: On Friday, 24 March 2006 at 17:09:36 +0300, Dmitriy Kirhlarov wrote: Hi, all I need building my own install server and want install my custom world, custom kernel and other in non-interactive mode. With 6.1-beta3 it work in mass (I not try install my kernel). With 6.1-beta4 and more fresh I can't get non-interactive installation. 1. I can't find how to select timezone non-interactive. You can find your timezone file in /usr/share/zoneinfo directory and copy it to /etc/localtime file. Next if your CMOS clock is set to local time you need to create empty file /etc/wall_cmos_clock. I mean automatic answer for sysinstall, for disabling dialog Country Selection. By. Dmitriy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Temperature monitoring in FreeBSD 4/5/6
Stephan Koenig writes: | Does anyone know of an easy way to get temperature information out of | a Dell PowerEdge 1550/1650/1750/1850/2650/2850 running FreeBSD4/5/6? | | Something that has a very simple CLI that just outputs the temperature | without any formatting, or a library/sysctl, would be ideal. For now manually back port the ipmi device driver and then install the latest ipmitool from ports. Then you can run ipmitool via the local interfaces. Interface that are support are SMIC and KCS. SSIF is in progress and dealing with some strange ACPI defintions that put a hole in the address space of the HW :-( I haven't really looked at the BT interface yet. Doug A. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Is login.conf.db now required?
Hi! I updated world to today's 6.1 and my syslog is filling up with: Mar 24 15:08:29 aldan sshd[2163]: login_getclass: unknown class 'root' The /etc/login.conf did not change since November. I never had login.conf.db -- it was always optional. Did that just change, or is something else broken here? The only radical change I made today was setting NO_NIS to yes. Thanks! -mi ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nve timeout (and down) regression?
On Thu, 23 Mar 2006 14:34:24 -0800 Kevin Oberman [EMAIL PROTECTED] wrote: Date: Thu, 23 Mar 2006 21:59:56 + (UTC) From: Bjoern A. Zeeb [EMAIL PROTECTED] On Thu, 23 Mar 2006, JoaoBR wrote: On Thursday 23 March 2006 15:59, Bjoern A. Zeeb wrote: nve did not worked on 6.0R (for me) but cvsup to stable resolved the case (for me) in end of dezember since a month or so with recent releng_6 the problem came back, timeouts and stopping rx/tx did you do more updates in the timeframe from december to about a month ago? if the problem was gone and is back now any (exact) dates to narrow down the timeframe where the problem came back would be very helpful. nve0: NVIDIA nForce MCP9 Networking Adapter port 0xbc00-0xbc07 mem 0xfebfa000-0xfebfafff irq 22 at device 10.0 on pci0 nve0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfebfa000 nve0: Ethernet address 00:0a:48:1d:c6:97 miibus1: MII bus on nve0 nve0: bpf attached nve0: Ethernet address: 00:0a:48:1d:c6:97 nve0: [MPSAFE] This happens w/o any real activity on that interface (which goes into an Allied Telesyn switch): ... Mar 24 19:39:54 worf kernel: nve0: device timeout (1) Mar 24 19:39:54 worf kernel: nve0: link state changed to DOWN Mar 24 19:39:55 worf kernel: nve0: link state changed to UP Mar 24 19:40:14 worf kernel: nve0: device timeout (1) Mar 24 19:40:14 worf kernel: nve0: link state changed to DOWN Mar 24 19:40:15 worf kernel: nve0: link state changed to UP Mar 24 19:40:33 worf kernel: nve0: device timeout (2) Mar 24 19:40:33 worf kernel: nve0: link state changed to DOWN Mar 24 19:40:34 worf kernel: nve0: link state changed to UP Mar 24 19:45:52 worf kernel: nve0: device timeout (1) Mar 24 19:45:52 worf kernel: nve0: link state changed to DOWN Mar 24 19:45:53 worf kernel: nve0: link state changed to UP . FreeBSD worf.tecnik93.com 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #0: Tue Mar 21 01:39:15 EET 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC amd64 -- IOnut - Unregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect BOFH excuse #442: Trojan horse ran out of hay ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Reading via mmap stinks (Re: weird bugs with mmap-ing via NFS)
Matthew Dillon wrote:
It is possible that the kernel believes the VM system to be too loaded
to issue read-aheads, as a consequence of your blowing out of the system
caches.
See attachment for the snapshot of `systat 1 -vm' -- it stays like that for
the most of the compression run time with only occasional flushes to the
amrd0 device (the destination for the compressed output).
Bakul Shah followed up:
May be the OS needs reclaim-behind for the sequential case?
This way you can mmap many many pages and use a much smaller
pool of physical pages to back them. The idea is for the VM
to reclaim pages N-k..N-1 when page N is accessed and allow
the same process to reuse this page.
Although it may hard for the kernel to guess, which pages it can reclaim
efficiently in the general case, my issuing of madvise with MADV_SEQUENTIONAL
should've given it a strong hint.
It is for this reasons, that I very much prefer the mmap API to read/write
(against Matt's repeated advice) -- there is a way to advise the kernel,
which there is not with the read. Read also requires fairly large buffers in
the user space to be efficient -- *in addition* to the buffers in the kernel.
Managing such buffers properly makes the program far messier _and_
OS-dependent, than using the mmap interface has to be.
I totally agree with Matt, that FreeBSD's (and probably DragonFly's too) mmap
interface is better than others', but, it seems to me, there is plenty of
room for improvement. Reading via mmap should never be slower, than via read
-- it should be just a notch faster, in fact...
I'm also quite certain, that fulfulling my demands would add quite a bit of
complexity to the mmap support in kernel, but hey, that's what the kernel is
there for :-)
Unlike grep, which seems to use only 32k buffers anyway (and does not use
madvise -- see attachment), my program mmaps gigabytes of the input file at
once, trusting the kernel to do a better job at reading the data in the most
efficient manner :-)
Peter Jeremy wrote:
On an amd64 system running about 6-week old -stable, both ['grep' and 'grep
--mmap' -mi] behave pretty much identically.
Peter, I read grep's source -- it is not using madvise (because it hurts
performance on SunOS-4.1!) and reads in chunks of 32k anyway. Would you care
to look at my program instead? Thanks:
http://aldan.algebra.com/mzip.c
(link with -lz and -lbz2).
Matthew Dillon wrote:
[...]
If the times for the mmap case do not blow up, we are back to square
one and I would start investigating the disk driver that Mikhail is
using.
On the machine, where both mzip and the disk run at only 50%, the disk is a
plain SATA drive (mzip's state goes from RUN to vnread and back).
Thanks, everyone!
-mi
Index: grep.c
===
RCS file: /home/ncvs/src/gnu/usr.bin/grep/grep.c,v
retrieving revision 1.31.2.1
diff -U2 -r1.31.2.1 grep.c
--- grep.c 26 Oct 2005 21:13:30 - 1.31.2.1
+++ grep.c 24 Mar 2006 19:52:05 -
@@ -427,9 +427,8 @@
PROT_READ | PROT_WRITE, MAP_PRIVATE | MAP_FIXED,
bufdesc, bufoffset)
- != (caddr_t) -1))
+ != MAP_FAILED))
{
- /* Do not bother to use madvise with MADV_SEQUENTIAL or
- MADV_WILLNEED on the mmapped memory. One might think it
- would help, but it slows us down about 30% on SunOS 4.1. */
+ if (madvise(readbuf, mmapsize, MADV_SEQUENTIAL))
+ warn(madvise);
fillsize = mmapsize;
}
@@ -441,4 +440,6 @@
other process has an advisory read lock on the file.
There's no point alarming the user about this misfeature. */
+ if (mmapsize)
+ warn(mmap);
bufmapped = 0;
if (bufoffset != initial_bufoffset
18 usersLoad 0.46 0.53 0.60 24 бер 15:15
Mem:KBREALVIRTUAL VN PAGER SWAP PAGER
Tot Share TotShareFree in out in out
Act 18338645880 2775855245268 92216 count 240
All 18811885992 1432466k52864 pages 3413
Interrupts
Proc:r p d s wCsw Trp Sys Int Sof Fltcow2252 total
1 2101 1605 2025 197 4222 2018 251432 wireirq1: atkb
506156 act irq6: fdc0
3.0%Sys 0.0%Intr 45.2%User 0.0%Nice 51.9%Idl 1038216 inact irq15: ata
|||||||||| 89252 cache irq17: fwo
= 2964 freeirq20: nve
daefr irq21: ohc
Namei Name-cacheDir-cache prcfr 241 irq22: ehc
Calls hits% hits% 951 react11 irq25: em0
pdwak irq29: amr
618 zfod
Re: nve timeout (and down) regression?
Date: Fri, 24 Mar 2006 22:33:17 +0200 From: Ion-Mihai Tetcu [EMAIL PROTECTED] On Thu, 23 Mar 2006 14:34:24 -0800 Kevin Oberman [EMAIL PROTECTED] wrote: Date: Thu, 23 Mar 2006 21:59:56 + (UTC) From: Bjoern A. Zeeb [EMAIL PROTECTED] On Thu, 23 Mar 2006, JoaoBR wrote: On Thursday 23 March 2006 15:59, Bjoern A. Zeeb wrote: nve did not worked on 6.0R (for me) but cvsup to stable resolved the case (for me) in end of dezember since a month or so with recent releng_6 the problem came back, timeouts and stopping rx/tx did you do more updates in the timeframe from december to about a month ago? if the problem was gone and is back now any (exact) dates to narrow down the timeframe where the problem came back would be very helpful. nve0: NVIDIA nForce MCP9 Networking Adapter port 0xbc00-0xbc07 mem 0xfebfa000-0xfebfafff irq 22 at device 10.0 on pci0 nve0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfebfa000 nve0: Ethernet address 00:0a:48:1d:c6:97 miibus1: MII bus on nve0 nve0: bpf attached nve0: Ethernet address: 00:0a:48:1d:c6:97 nve0: [MPSAFE] This happens w/o any real activity on that interface (which goes into an Allied Telesyn switch): ... Mar 24 19:39:54 worf kernel: nve0: device timeout (1) Mar 24 19:39:54 worf kernel: nve0: link state changed to DOWN Mar 24 19:39:55 worf kernel: nve0: link state changed to UP Mar 24 19:40:14 worf kernel: nve0: device timeout (1) Mar 24 19:40:14 worf kernel: nve0: link state changed to DOWN Mar 24 19:40:15 worf kernel: nve0: link state changed to UP Mar 24 19:40:33 worf kernel: nve0: device timeout (2) Mar 24 19:40:33 worf kernel: nve0: link state changed to DOWN Mar 24 19:40:34 worf kernel: nve0: link state changed to UP Mar 24 19:45:52 worf kernel: nve0: device timeout (1) Mar 24 19:45:52 worf kernel: nve0: link state changed to DOWN Mar 24 19:45:53 worf kernel: nve0: link state changed to UP . FreeBSD worf.tecnik93.com 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #0: Tue Mar 21 01:39:15 EET 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC amd64 Note that we are running on i386 running am an AMD64 platform. I updated my system (which was happy on Feb. 15 code) to March 13 code and I am still running fine. No errors at all. Also, another system was updated to RELENG_6 yesterday and it is also running clean. Again, all systems are identical dual core AMD64 systems running i386 code. (We would like to run amd64, but OpenOffice.org still does not run on it and we need that.) Only the system in Iowa with the AT switch is seeing problems. Even if there is no traffic, it is possible that something that is negotiated by the switch is triggering the problem. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Reading via mmap stinks (Re: weird bugs with mmap-ing via NFS)
May be the OS needs reclaim-behind for the sequential case? This way you can mmap many many pages and use a much smaller pool of physical pages to back them. The idea is for the VM to reclaim pages N-k..N-1 when page N is accessed and allow the same process to reuse this page. Although it may hard for the kernel to guess, which pages it can reclaim efficiently in the general case, my issuing of madvise with MADV_SEQUENTIONAL should've given it a strong hint. Yes, that is what I was saying. If mmap read can be made as efficient as the use of read() for this most common case, there are benefits. In effect we set up a fifo that rolls along the mapped address range and the kernel processing and the user processing are somewhat decoupled. Reading via mmap should never be slower, than via read -- it should be just a notch faster, in fact... Depends on the cost of mostly redundant processing of N read() syscalls versus the cost of setting up and tearing down multiple v2p mappings -- presumably page faults can be avoided if the kernel fills in pages ahead of when they are first accessed. The cost of tlbmiss is likely minor. Probably the breakeven point is just a few read() calls. I'm also quite certain, that fulfulling my demands would add quite a bit of complexity to the mmap support in kernel, but hey, that's what the kernel is there for :-) An interesting thought experiment is to assume the system has *no* read and write calls and see how far you can get with the present mmap scheme and what extensions are needed to get back the same functionality. Yes, assume mmap friends even for serial IO! I am betting that mmap can be simplified. [Proof by handwaving elided; this screen is too small to fit my hands :-)] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Is login.conf.db now required?
Mikhail Teterin wrote: Hi! I updated world to today's 6.1 and my syslog is filling up with: Mar 24 15:08:29 aldan sshd[2163]: login_getclass: unknown class 'root' The /etc/login.conf did not change since November. I never had login.conf.db -- it was always optional. Did that just change, or is something else broken here? The only radical change I made today was setting NO_NIS to yes. Thanks! I had similar problems when I disabled NIS too. I'm not sure if your problem is the same, but I fixed mine by editing /etc/nsswitch.conf and replacing all occurrences of nis with files. Apparently there are some things that don't respect NO_NIS and therefore keep trying to use it anyway. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Temperature monitoring in FreeBSD 4/5/6
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, Doug Ambrisko wrote: Stephan Koenig writes: | Does anyone know of an easy way to get temperature information out of | a Dell PowerEdge 1550/1650/1750/1850/2650/2850 running FreeBSD4/5/6? | | Something that has a very simple CLI that just outputs the temperature | without any formatting, or a library/sysctl, would be ideal. Since it wasn't mentioned yet, the OpenBSD folks have a driver for the Dell OMSA, ems(4). http://www.openbsd.org/cgi-bin/man.cgi?query=esmapropos=0sektion=0manpath=OpenBSD+Currentarch=i386format=html It'll do the job you want, and some more :) I was wondering wether this could be ported to FreeBSD... hm... would be great :) I know this doesn't help you now, but, anyway... regards, Marian -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFEJI6hgAq87Uq5FMsRAmUEAKCaNWnptzloU5Rf100EqBNEzqRdOQCdGp0P F2gpdsSYuxUlSYHst/NeLVE= =eI2m -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: nve timeout (and down) regression?
On Fri, 24 Mar 2006 12:55:41 -0800 Kevin Oberman [EMAIL PROTECTED] wrote: Date: Fri, 24 Mar 2006 22:33:17 +0200 From: Ion-Mihai Tetcu [EMAIL PROTECTED] On Thu, 23 Mar 2006 14:34:24 -0800 Kevin Oberman [EMAIL PROTECTED] wrote: Date: Thu, 23 Mar 2006 21:59:56 + (UTC) From: Bjoern A. Zeeb [EMAIL PROTECTED] On Thu, 23 Mar 2006, JoaoBR wrote: On Thursday 23 March 2006 15:59, Bjoern A. Zeeb wrote: nve did not worked on 6.0R (for me) but cvsup to stable resolved the case (for me) in end of dezember since a month or so with recent releng_6 the problem came back, timeouts and stopping rx/tx did you do more updates in the timeframe from december to about a month ago? if the problem was gone and is back now any (exact) dates to narrow down the timeframe where the problem came back would be very helpful. nve0: NVIDIA nForce MCP9 Networking Adapter port 0xbc00-0xbc07 mem 0xfebfa000-0xfebfafff irq 22 at device 10.0 on pci0 nve0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfebfa000 nve0: Ethernet address 00:0a:48:1d:c6:97 miibus1: MII bus on nve0 nve0: bpf attached nve0: Ethernet address: 00:0a:48:1d:c6:97 nve0: [MPSAFE] This happens w/o any real activity on that interface (which goes into an Allied Telesyn switch): ... Mar 24 19:39:54 worf kernel: nve0: device timeout (1) Mar 24 19:39:54 worf kernel: nve0: link state changed to DOWN Mar 24 19:39:55 worf kernel: nve0: link state changed to UP Mar 24 19:40:14 worf kernel: nve0: device timeout (1) Mar 24 19:40:14 worf kernel: nve0: link state changed to DOWN Mar 24 19:40:15 worf kernel: nve0: link state changed to UP Mar 24 19:40:33 worf kernel: nve0: device timeout (2) Mar 24 19:40:33 worf kernel: nve0: link state changed to DOWN Mar 24 19:40:34 worf kernel: nve0: link state changed to UP Mar 24 19:45:52 worf kernel: nve0: device timeout (1) Mar 24 19:45:52 worf kernel: nve0: link state changed to DOWN Mar 24 19:45:53 worf kernel: nve0: link state changed to UP . FreeBSD worf.tecnik93.com 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #0: Tue Mar 21 01:39:15 EET 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC amd64 Note that we are running on i386 running am an AMD64 platform. I just enabled the nve0 on my desktop (I'm using sk0, it's a Asus A8N-SLI Deluxe motherboard, both interfaces connected to the same 8-port Surecom switch - talking about very inexpensive :) and it seems to work OK. nve0: NVIDIA nForce MCP9 Networking Adapter port 0xb000-0xb007 mem 0xca10-0xca100fff irq 23 at device 10.0 on pci0 nve0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xca10 nve0: Ethernet address 00:15:f2:39:09:08 miibus1: MII bus on nve0 nve0: bpf attached nve0: Ethernet address: 00:15:f2:39:09:08 nve0: [MPSAFE] FreeBSD it.buh.tecnik93.com 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #0: Fri Feb 24 07:01:54 EET 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/IT6_B_P i386 I updated my system (which was happy on Feb. 15 code) to March 13 code and I am still running fine. No errors at all. Also, another system was updated to RELENG_6 yesterday and it is also running clean. Again, all systems are identical dual core AMD64 systems running i386 code. (We would like to run amd64, but OpenOffice.org still does not run on it and we need that.) Both my systems are single core single CPU. Only the system in Iowa with the AT switch is seeing problems. Even if there is no traffic, it is possible that something that is negotiated by the switch is triggering the problem. Possibly, but I think I remember seeing the same w/o cable plugged-in; I'll try to remember to test this for a a few minutes when I'll be on-site next week. -- IOnut - Unregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect BOFH excuse #266: All of the packets are empty ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nve timeout (and down) regression?
在 Friday 24 March 2006 02:40，JoaoBR 写道： The other patch cited in the message has never been made: diff -u -r1.7.2.4 if_nve.c --- if_nve.c9 Oct 2005 04:18:17 - 1.7.2.4 +++ if_nve.c27 Oct 2005 09:58:45 - @@ -727,7 +727,7 @@ DEBUGOUT(NVE_DEBUG_INIT, nve: nve_init_rings - entry\n); - sc-cur_rx = sc-cur_tx = sc-pending_rxs = sc-pending_txs = 0; + sc-cur_rx = sc-cur_tx = sc-pending_rxs = 0; and I did this part and my NIC is running, as I said still lot of collisions caused by it but it is running João This change causes my NIC to not work anymore, though I still saw timeout without this change, I think this varies from hardware revision to revision, unpredictable at all. David Xu ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
