Re: [Fwd: cvs commit: src/lib/libc/stdio findfp.c]
Yes, at least half way through an installworld, xsane works again :-) Thanks. Hi, Please check to see if it would solve your problems with fopen(). -Maxim Original Message Subject: cvs commit: src/lib/libc/stdio findfp.c Date: Wed, 7 Feb 2001 09:34:50 -0800 (PST) From: Maxim Sobolev [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED] sobomax 2001/02/07 09:34:49 PST Modified files: lib/libc/stdio findfp.c Log: Fix a f^Hdamn typo, which prevented to fopen() more that 17 files at once. Tested by: knu, sobomax and other #bsdcode'rs Revision ChangesPath 1.9 +2 -2 src/lib/libc/stdio/findfp.c -- Brian [EMAIL PROTECTED]brian@[uk.]FreeBSD.org http://www.Awfulhak.org brian@[uk.]OpenBSD.org Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Kernel Panic from Yesterday's CVSup
Seriously, that's ok, I only want to check if I get the same panic. And give
feedback of course.
Here I am again. Didn't get as far as a login prompt, I have a panic when qmail
starts up:
lock order reversal
1st lockmgr last acquired @ ../../kern/kern_lock.c:239
2nd 0xc02630c0 uidinfo hash @ ../../kern/kern_resource.c:727
3rd 0xc0261080 lockmgr @ ../../kern/kern_lock.c:239
panic: mutex_enter: recursion on non-recursive mutex process lock @
+../../kern/kern_lock.c:260
Debugger("panic")
Stopped at Debugger+0x46: pushl %ebx
db trace
Debugger(c0213d83) at Debugger+0x46
panic(c0212cc0,c029,c021195a,104,c65d6964) at panic+0x70
witness_enter(c65d6964,0,c021195a,104,c65d6964) at witness_enter+0x1b2
_mtx_enter(c65d6964,0,c021195a,104) at _mtx_enter+0x154
lockmgr(c026849c,1,0,c65d6840,c0a6691c) at lockmgr+0xad
kernacc(c027bd40,4,1,c023c500,0c0212497,34d) at kernacc+0x54
mtx_validate(c0a6691c,1) at mtx_validate+0x59
mtx_init(c0a6691c,c02138cc,0,0,57) at mtx_init+0x13
uicreate(57,c65d6964,c0a6d0c0,c65e0f30,c014f13a) at uicreate+0x8a
uifind(57,c65d6964,0,c02135b0,586) at uifind+0x33
change_ruid(c65d6840,57,c65d6840,0,1) at change_ruid+0x46
setuid(c65d6840,c65e0f80,bfbffd80,bfbffd7c,bfbffd90) at setuid+0x3a
syscall2(2f,2f,2f,bfbffd90,bfbffd7c) at syscall2+0x29c
Xint0x80_syscall() at Xint0x80_syscall+0x23
--- syscall 0x17, eip = 0x280a039c, esp 0xbfbffcdc, ebp = 0xbfbffcf8
At least I think it's qmail, looking at the `ps' output...
--
The best things in life are free, but the
expensive ones are still worth a look.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Regarding your suggestion to multiopen.com
Hi, ma'am. We really appreciate your funding proposal. Our management department will go over the deal for a couple of days. Thanks. Best Regards http://www.multiopen.com [EMAIL PROTECTED] Michael Sussman To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Kernel Panic from Yesterday's CVSup
ISA bus cannot share interrupts at all. Full stop[*]. Most pccard/cardbus bridges operate in a mode where they use ISA interrupts, so cannot share interrupts at all. The hardware just won't work if you try. NEWCARD tries to kick the cardbus bridge into full PCI mode, where you can share interrupts, since all the interrupts are going through the PCI hardware chain which does support interrupt sharing. Thanks for expressing in a proper way what I was trying to say ;-) Will try again with cardbus and report. So are you saying it SHOULD work (as far as my chipset is behaving, I suppose)? Bye, Andrea -- "One world, one web, one program" -- Microsoft promotional ad "Ein Volk, ein Reich, ein Fuehrer" -- Adolf Hitler To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: What's changed recently with vmware/linuxemu/file I/O
On Wed, Feb 07, 2001 at 10:07:06PM -0500, Robert Watson wrote:
On 7 Feb 2001, Dag-Erling Smorgrav wrote:
Brian Somers [EMAIL PROTECTED] writes:
Indeed. I've been doing a ``make build'' on an OpenBSD-current vm
for three days (probably about 36 hours excluding suspends) on a
366MHz laptop with a ATA33 disk.
Would it be possible for someone experiencing this slowdown to try to
narrow down the day (or even the week) on which it occurred?
I've experienced a substantial slowdown in VMware since bumping forwards
from -STABLE on my workstation. As I recently commented on -emulation,
I've also been experiencing 30-40 second hangs of the system during VMware
startup and occasional serious slowdown while running, which may be
related to the fairly intensive VM activity for page wiring and the like,
or possible poor interaction with the ATA driver. I also get messages on
the order of the following:
The slowdown during start up appears to be in biowr; this is probably
because of IDE write caching being switched off. More seriously
the vmware hangs during various phases of it's boot process.
i.e:
714 root -14 0 123M 79192K inode0:45 25.29% 25.29% vmware
When this happens the whole machine freezes also. Processes run, but
new processes don't get forked. The whole machine appears to be I/O
bound. (What's the 'inode' state?)
The problem is definitely solved by enabling ATA_ENABLE_WC in the kernel
config. What's unclear to me is why the hang in 'inode' with it
switched off. I understand that biowr's would take longer, which is
vmware does as it brings up the virtual machine, but why the hanging
and freezing in 'inode'?
Joe
RCS file: /home/ncvs/src/sys/dev/ata/ata-disk.c,v
retrieving revision 1.91
retrieving revision 1.92
diff -u -r1.91 -r1.92
--- ata-disk.c 2001/01/19 13:53:54 1.91
+++ ata-disk.c 2001/01/29 18:00:35 1.92
@@ -25,7 +25,7 @@
* (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
* THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*
- * $FreeBSD: src/sys/dev/ata/ata-disk.c,v 1.91 2001/01/19 13:53:54 peter Exp $
+ * $FreeBSD: src/sys/dev/ata/ata-disk.c,v 1.92 2001/01/29 18:00:35 sos Exp $
*/
#include "opt_global.h"
@@ -133,10 +133,15 @@
0, 0, 0, 0, ATA_C_F_ENAB_RCACHE, ATA_WAIT_INTR))
printf("ad%d: enabling readahead cache failed\n", adp-lun);
+#if defined(ATA_ENABLE_WC) || defined(ATA_ENABLE_TAGS)
if (ata_command(adp-controller, adp-unit, ATA_C_SETFEATURES,
0, 0, 0, 0, ATA_C_F_ENAB_WCACHE, ATA_WAIT_INTR))
printf("ad%d: enabling write cache failed\n", adp-lun);
-
+#else
+if (ata_command(adp-controller, adp-unit, ATA_C_SETFEATURES,
+ 0, 0, 0, 0, ATA_C_F_DIS_WCACHE, ATA_WAIT_INTR))
+ printf("ad%d: disabling write cache failed\n", adp-lun);
+#endif
/* use DMA if drive controller supports it */
ata_dmainit(adp-controller, adp-unit,
ata_pmode(AD_PARAM), ata_wmode(AD_PARAM), ata_umode(AD_PARAM));
PGP signature
Re: What's changed recently with vmware/linuxemu/file I/O
Josef Karthauser wrote:
The slowdown during start up appears to be in biowr; this is probably
because of IDE write caching being switched off. More seriously
the vmware hangs during various phases of it's boot process.
Write caching is incompaible with soft updates.
The drive must NEVER report that something is on disk when it really is not!
i.e:
714 root -14 0 123M 79192K inode0:45 25.29% 25.29% vmware
When this happens the whole machine freezes also. Processes run, but
new processes don't get forked. The whole machine appears to be I/O
bound. (What's the 'inode' state?)
this sounds like a differnt starvation problem.
when it's happenning, what does 'iostat 1' show?
(how many transactions per second?)
I believe that vmware mmaps a region of memory and then somehow syncs
it to disk. (It is certainly doing something like it here).
The problem is definitely solved by enabling ATA_ENABLE_WC in the kernel
config. What's unclear to me is why the hang in 'inode' with it
switched off. I understand that biowr's would take longer, which is
vmware does as it brings up the virtual machine, but why the hanging
and freezing in 'inode'?
maybe syncing mmapped regions locks out other types of activity?
Matt?
+#else
+if (ata_command(adp-controller, adp-unit, ATA_C_SETFEATURES,
+ 0, 0, 0, 0, ATA_C_F_DIS_WCACHE, ATA_WAIT_INTR))
+ printf("ad%d: disabling write cache failed\n", adp-lun);
+#endif
we used to do this on the interjet because we ran soft updates.
--
__--_|\ Julian Elischer
/ \ [EMAIL PROTECTED]
( OZ) World tour 2000-2001
--- X_.---._/
v
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: What's changed recently with vmware/linuxemu/file I/O
On Thu, Feb 08, 2001 at 04:08:12AM -0800, Julian Elischer wrote: Josef Karthauser wrote: 714 root -14 0 123M 79192K inode0:45 25.29% 25.29% vmware When this happens the whole machine freezes also. Processes run, but new processes don't get forked. The whole machine appears to be I/O bound. (What's the 'inode' state?) this sounds like a differnt starvation problem. when it's happenning, what does 'iostat 1' show? (how many transactions per second?) It looks like below. Joe tty ad0 fd0 cpu tin tout KB/t tps MB/s KB/t tps MB/s us ni sy in id 0 179 8.00 67 0.53 0.00 0 0.00 0 0 0 2 98 0 59 8.00 68 0.53 0.00 0 0.00 0 0 0 2 98 0 60 8.00 68 0.53 0.00 0 0.00 0 0 0 2 98 0 60 8.00 67 0.53 0.00 0 0.00 2 0 0 2 97 0 59 8.00 66 0.52 0.00 0 0.00 1 0 2 2 95 0 60 8.00 68 0.53 0.00 0 0.00 1 0 1 2 97 0 60 8.00 68 0.53 0.00 0 0.00 0 0 1 2 98 0 60 8.00 67 0.53 0.00 0 0.00 0 0 1 1 98 0 59 8.00 66 0.52 0.00 0 0.00 0 0 0 2 98 79 60 8.00 67 0.53 0.00 0 0.00 0 0 1 2 98 183 60 8.00 68 0.53 0.00 0 0.00 0 0 3 2 95 143 60 8.00 67 0.53 0.00 0 0.00 0 0 3 3 94 197 59 8.00 67 0.53 0.00 0 0.00 1 0 1 2 97 48 60 8.00 68 0.53 0.00 0 0.00 0 0 0 2 98 8 60 8.00 67 0.53 0.00 0 0.00 0 0 2 2 96 228 59 8.00 66 0.52 0.00 0 0.00 1 0 2 2 96 40 60 8.00 67 0.53 0.00 0 0.00 0 0 2 2 96 0 60 8.00 68 0.53 0.00 0 0.00 1 0 1 2 97 0 60 8.00 67 0.53 0.00 0 0.00 1 0 1 3 95 0 59 8.00 67 0.53 0.00 0 0.00 1 0 1 2 97 tty ad0 fd0 cpu tin tout KB/t tps MB/s KB/t tps MB/s us ni sy in id 0 179 8.00 68 0.53 0.00 0 0.00 0 0 2 2 97 0 60 8.00 67 0.53 0.00 0 0.00 1 0 1 2 96 0 59 8.00 67 0.53 0.00 0 0.00 0 0 0 3 97 0 60 8.00 67 0.53 0.00 0 0.00 0 0 0 2 98 0 60 8.00 68 0.53 0.00 0 0.00 1 0 0 2 98 0 60 8.00 67 0.53 0.00 0 0.00 0 0 0 2 98 0 59 8.00 68 0.53 0.00 0 0.00 1 0 0 2 98 0 60 8.00 67 0.53 0.00 0 0.00 0 0 0 2 98 0 60 8.00 68 0.53 0.00 0 0.00 0 0 1 2 98 0 59 8.00 67 0.53 0.00 0 0.00 0 0 2 2 95 0 60 8.00 68 0.53 0.00 0 0.00 0 0 1 3 96 0 60 8.00 68 0.53 0.00 0 0.00 2 0 1 2 95 0 60 8.00 67 0.53 0.00 0 0.00 0 0 0 2 98 0 59 8.00 68 0.53 0.00 0 0.00 0 0 0 2 98 0 60 8.00 67 0.53 0.00 0 0.00 0 0 0 2 98 0 60 8.00 68 0.53 0.00 0 0.00 0 0 0 2 98 0 59 8.00 66 0.52 0.00 0 0.00 0 0 0 2 98 0 60 8.00 66 0.52 0.00 0 0.00 0 0 0 2 98 0 60 8.00 67 0.53 0.00 0 0.00 0 0 0 2 98 0 60 8.00 68 0.53 0.00 0 0.00 0 0 0 2 98 PGP signature
Re: od driver for -CURRENT
From: Bernd Walter [EMAIL PROTECTED] Date: Wed, 7 Feb 2001 17:11:57 +0100 On Tue, Feb 06, 2001 at 11:21:12PM +0900, [EMAIL PROTECTED] wrote: Today I tried with 4.2-RELEASE (sorry not -current) and, 1. Boot up the 4.2-RELEASE with GENERIC kernel. 2. Connect MO drive with PC Card SCSI(ncv). 3. Insert PC Card without medium in the MO drive. 4. The pccardd automatically run camcontrol rescan. 5. Message says that da0 is 0MB capacity. 6. Run fdisk da0 7. got panic with divided by zero. Probably divided by zero is caused at line 737 or 748 in the scsi_low_action() in cam/scsi/scsi_low.c because of ccg-block_size or secs_per_cylinder is zero. I tried with same drive and another SCSI card (ahc0) in 4.2-RELEASE. No problem were found. I watched the diffs between da.c and od.c. It seems like some fault in scsi_low.c. Hmm, my fault Sorry for claiming `da'. By the way, in Japanese users mailing list, some said that `da' does not check whether a medium is writerable or not (write protected). If you mount a write protected medium with -rw, it will lead bad condition when you do umount. I never used fdisk on a removeable disk as I only needed them for FreeBSD. : It looks like fdisk triggers the bug. I used fdisk just to check if there is a slice or not. Fdisk did not make problem. // Noriaki Mitsunaga // To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: What's changed recently with vmware/linuxemu/file I/O
Josef Karthauser wrote: On Thu, Feb 08, 2001 at 04:08:12AM -0800, Julian Elischer wrote: Josef Karthauser wrote: 714 root -14 0 123M 79192K inode0:45 25.29% 25.29% vmware When this happens the whole machine freezes also. Processes run, but new processes don't get forked. The whole machine appears to be I/O bound. (What's the 'inode' state?) this sounds like a differnt starvation problem. when it's happenning, what does 'iostat 1' show? (how many transactions per second?) It looks like below. Looks like some way of clustering this might achieve a lot. what does systat -vmstat or vmstat 1 show? Better still, I guess we could do a linux-truss and see what it's doing... Joe tty ad0 fd0 cpu tin tout KB/t tps MB/s KB/t tps MB/s us ni sy in id 0 179 8.00 67 0.53 0.00 0 0.00 0 0 0 2 98 0 59 8.00 68 0.53 0.00 0 0.00 0 0 0 2 98 0 60 8.00 68 0.53 0.00 0 0.00 0 0 0 2 98 0 60 8.00 67 0.53 0.00 0 0.00 2 0 0 2 97 -- __--_|\ Julian Elischer / \ [EMAIL PROTECTED] ( OZ) World tour 2000-2001 --- X_.---._/ v To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: What's changed recently with vmware/linuxemu/file I/O
Julian Elischer [EMAIL PROTECTED] writes: I believe that vmware mmaps a region of memory and then somehow syncs it to disk. (It is certainly doing something like it here). Theory: VMWare mmaps a region of memory corresponding to the virtual machine's "physical" RAM, then touches every page during startup. Unless some form of clustering is done, this causes 16384 write operations for a 64 MB virtual machine... DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: What's changed recently with vmware/linuxemu/file I/O
On Thu, Feb 08, 2001 at 04:58:17AM -0800, Julian Elischer wrote: Looks like some way of clustering this might achieve a lot. what does systat -vmstat or vmstat 1 show? Better still, I guess we could do a linux-truss and see what it's doing... I believe that it's strace under linux. If someone can provide me with a binary of this tool I'll happily run it here and see what vmware's doing. Joe PGP signature
Re: What's changed recently with vmware/linuxemu/file I/O
On Thu, Feb 08, 2001 at 02:47:59PM +, Josef Karthauser wrote: what does systat -vmstat or vmstat 1 show? Better still, I guess we could do a linux-truss and see what it's doing... I believe that it's strace under linux. If someone can provide me with a binary of this tool I'll happily run it here and see what vmware's doing. You could use FreeBSD ktrace and then the linux_kdump port. David. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
problems with playback via pcm device
i have Ensoniq ES1371-based soundcard supported by pcm driver and experience some problems. the sound played is interruped by clicks and distorsions, and they appear more often when the disk activity is high. during playback the kernel generates messages like 'pcm0: hwptr went backwards 64 - 32'. any ideas? here is my dmesg: Copyright (c) 1992-2001 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 5.0-CURRENT #2: Thu Feb 8 18:19:26 MSK 2001 [EMAIL PROTECTED]:/garbage/src/sys/compile/CAMEL Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 550023689 Hz CPU: AMD Athlon(tm) Processor (550.02-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x621 Stepping = 1 Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR AMD Features=0xc040AMIE,DSP,3DNow! real memory = 134135808 (130992K bytes) avail memory = 125829120 (122880K bytes) Preloaded elf kernel "kernel" at 0xc03de000. Pentium Pro MTRR support enabled Using $PIR table, 8 entries at 0xc00f15e0 npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge at pcibus 0 on motherboard pci0: PCI bus on pcib0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: display, VGA at 0.0 (no driver attached) isab0: PCI-ISA bridge at device 4.0 on pci0 isa0: ISA bus on isab0 atapci0: VIA 82C686 ATA66 controller port 0xd800-0xd80f at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: serial bus, USB at 4.2 (no driver attached) pci0: serial bus, USB at 4.3 (no driver attached) pcm0: AudioPCI ES1371 port 0xa400-0xa43f irq 9 at device 9.0 on pci0 ahc0: Adaptec aic7850 SCSI adapter port 0xa000-0xa0ff mem 0xe180-0xe1800fff irq 5 at device 10.0 on pci0 aic7850: Single Channel A, SCSI Id=7, 3/255 SCBs xl0: 3Com 3c905B-TX Fast Etherlink XL port 0x9800-0x987f mem 0xe100-0xe17f irq 10 at device 11.0 on pci0 xl0: Ethernet address: 00:10:5a:74:c4:6c miibus0: MII bus on xl0 xlphy0: 3Com internal media interface on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5" drive on fdc0 drive 0 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 psm0: PS/2 Mouse flags 0x8000 irq 12 on atkbdc0 psm0: model NetMouse/NetScroll Optical, device ID 0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 unknown: PNP0401 can't assign resources unknown: PNP0501 can't assign resources unknown: PNP0501 can't assign resources unknown: PNP0700 can't assign resources unknown: PNP0f13 can't assign resources unknown: PNP0303 can't assign resources atspeaker0: AT speaker at port 0x61 on isa0 IP packet filtering initialized, divert enabled, rule-based forwarding disabled, default to deny, logging limited to 200 packets/entry by default ncp_load: [210-213] ad0: 8223MB ST38410A [16708/16/63] at ata0-master UDMA66 acd0: CDROM CREATIVE CD5220 at ata1-master using WDMA2 Waiting 5 seconds for SCSI devices to settle Mounting root from ufs:/dev/ad0s1a xl0: promiscuous mode enabled /dev/vmmon: Module vmmon: registered with major=200 minor=0 tag=$Name: build-570 $ /dev/vmmon: Module vmmon: initialized sincerely, ilya naumov (at work) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Kernel Panic from Yesterday's CVSup
In message [EMAIL PROTECTED] Andrea Campi writes: : Will try again with cardbus and report. So are you saying it SHOULD work : (as far as my chipset is behaving, I suppose)? Cardbus works, more or less, on -current right now. Some cards just work, other cards need help. I keep meaning to do a survey, but haven't found the time to do it yet. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
atomic_ question
Are atomic_* implementations allowed to spin/sleep? The question is because some platforms don't have atomic operations for adding and so on (e.g. sparcv8). The only way to implement them on these platforms is to use a lock. Now I'm wonder if the use of a sleep mutex is allowed or is a simple spinning lock the sensefull choice. One of the results is that there is no mutex/lock allocated specially for this purpose and there is a need to allocate one globaly for all. -- B.Walter COSMO-Project http://www.cosmo-project.de [EMAIL PROTECTED] Usergroup [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: od driver for -CURRENT
On Thu, Feb 08, 2001 at 21:42:59 +0900, [EMAIL PROTECTED] wrote: From: Bernd Walter [EMAIL PROTECTED] Date: Wed, 7 Feb 2001 17:11:57 +0100 On Tue, Feb 06, 2001 at 11:21:12PM +0900, [EMAIL PROTECTED] wrote: Today I tried with 4.2-RELEASE (sorry not -current) and, 1. Boot up the 4.2-RELEASE with GENERIC kernel. 2. Connect MO drive with PC Card SCSI(ncv). 3. Insert PC Card without medium in the MO drive. 4. The pccardd automatically run camcontrol rescan. 5. Message says that da0 is 0MB capacity. 6. Run fdisk da0 7. got panic with divided by zero. Probably divided by zero is caused at line 737 or 748 in the scsi_low_action() in cam/scsi/scsi_low.c because of ccg-block_size or secs_per_cylinder is zero. I tried with same drive and another SCSI card (ahc0) in 4.2-RELEASE. No problem were found. I watched the diffs between da.c and od.c. It seems like some fault in scsi_low.c. Hmm, my fault Sorry for claiming `da'. No problem. :) By the way, in Japanese users mailing list, some said that `da' does not check whether a medium is writerable or not (write protected). If you mount a write protected medium with -rw, it will lead bad condition when you do umount. Hmm, can you demonstrate the problem? The write-protect check in the od driver is one of the things that the da driver doesn't have. I figured it wouldn't really be necessary, since any attempted writes would be returned with errors. Ken -- Kenneth Merry [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Overview of machine dependend routines
Is there an overview available which defines all machine dependend routines that are needed. By looking into the code it's not always obvious if a given function is one called by the MI code or if it's only a helper function inside. I asume the definitions from "Inside 4.4BSD" are outdated in some cases. -- B.Walter COSMO-Project http://www.cosmo-project.de [EMAIL PROTECTED] Usergroup [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
kernel trap 12 with interrupts disabled
Hi, if I run a program compiled with gcc's function profiling option I get "kernel trap 12 with interrupts disabled". If I run it withhin X11, the machine deadlocks hard (no response from the numlock led on the keyboard), withhin a virtual console I get a lot of "kernel trap ..." and the program runs fine. -current as of Feb. 6, ~2pm UTC. Bye, Alexander. -- I believe the technical term is "Oops!" http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kernel trap 12 with interrupts disabled
Alexander Leidinger wrote: Hi, if I run a program compiled with gcc's function profiling option I get "kernel trap 12 with interrupts disabled". The same is here. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: problems with playback via pcm device
In message [EMAIL PROTECTED] Ilya Naumov writes: : during playback the kernel generates messages like 'pcm0: hwptr went : backwards 64 - 32'. any ideas? : FreeBSD 5.0-CURRENT #2: Thu Feb 8 18:19:26 MSK 2001 Interrupt latency in current really sucks right now. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Kernel Panic from Yesterday's CVSup
On 08-Feb-01 Andrea Campi wrote: Seriously, that's ok, I only want to check if I get the same panic. And give feedback of course. Here I am again. Didn't get as far as a login prompt, I have a panic when qmail starts up: Turn MUTEX_DEBUG off. It appears to be broken atm. -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Fibre Channel Hardware List...
I've just put up a simple Fibre Channel "Suggest Hardware Matrix" as the beginnings of what one might expect for Fibre Channel in FreeBSD- see http://people.freebsd.org/~mjacob/Fibre_Channel_Hardware.txt Suggestions welcome! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Fibre Channel Hardware List...
I've just put up a simple Fibre Channel "Suggest Hardware Matrix" as the beginnings of what one might expect for Fibre Channel in FreeBSD- see http://people.freebsd.org/~mjacob/Fibre_Channel_Hardware.txt Suggestions welcome! As you asked, just suggestions here from someone who is putting FC stuff together for my own :-) - "Very expensive (in my opinion)" - if you mention "expensive"-"not expensive", I would propose to add rough price estimations too - this might be of interest for beginners imho. "I have used lots of different Seagate and a few IBM drives and typically have had few problems with them." - and absolutely nothing about single channel vs dual channel, issues with putting them together etc ? What's up with "1026Gbit" - is it really true ? Regards, Andrei To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Fibre Channel Hardware List...
On Thu, Feb 08, 2001 at 08:44:33PM +0100, Andrei A. Dergatchev wrote: "I have used lots of different Seagate and a few IBM drives and typically have had few problems with them." - and absolutely nothing about single channel vs dual channel, issues with putting them together etc ? What's up with "1026Gbit" - is it really true ? No, it should be 1.062 Gbit (the current fullspeed FC). Dual speed is coming soon. Don't ask for prices :-( -- | / o / / _ Arnhem, The Netherlandsemail: [EMAIL PROTECTED] |/|/ / / /( (_) Bultehttp://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Fibre Channel Hardware List...
cool! I'll update page momentarily with corrections! I've just put up a simple Fibre Channel "Suggest Hardware Matrix" as the beginnings of what one might expect for Fibre Channel in FreeBSD- see http://people.freebsd.org/~mjacob/Fibre_Channel_Hardware.txt Suggestions welcome! As you asked, just suggestions here from someone who is putting FC stuff together for my own :-) - "Very expensive (in my opinion)" - if you mention "expensive"-"not expensive", I would propose to add rough price estimations too - this might be of interest for beginners imho. "I have used lots of different Seagate and a few IBM drives and typically have had few problems with them." - and absolutely nothing about single channel vs dual channel, issues with putting them together etc ? What's up with "1026Gbit" - is it really true ? Regards, Andrei To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Fibre Channel Hardware List...
Oh, yeah, about this, 2300 support is comint "real soon" -this will be 2GBit. On Thu, Feb 08, 2001 at 08:44:33PM +0100, Andrei A. Dergatchev wrote: "I have used lots of different Seagate and a few IBM drives and typically have had few problems with them." - and absolutely nothing about single channel vs dual channel, issues with putting them together etc ? What's up with "1026Gbit" - is it really true ? No, it should be 1.062 Gbit (the current fullspeed FC). Dual speed is coming soon. Don't ask for prices :-( To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Fibre Channel Hardware List...
Oh, yeah, about this, 2300 support is comint "real soon" -this will be 2GBit. Thanks ! And for the page too - very good and useful !! For poor owners of 2GB-ready Seagates, I wonder can you advise on any affordable 2GB enclosure ? Everything affordable I saw is a bit old and 1GB-only. Of course, I don't now if it will make any real difference - will burst speed twice as fast or what ? Would be really nice to hear from someone knowledgeable :-) Thanks again ! Regards, Andrei To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Fibre Channel Hardware List...
Oh, yeah, about this, 2300 support is comint "real soon" -this will be 2GBit. Thanks ! And for the page too - very good and useful !! For poor owners of 2GB-ready Seagates, I wonder can you advise on any affordable 2GB enclosure ? Everything affordable I saw is a bit old and 1GB-only. Of course, I don't now if it will make any real difference - will burst speed twice as fast or what ? Would be really nice to hear from someone knowledgeable :-) About the 2Gb drives, sorry! I have no clue as yet about this! Thanks again ! You're welcome! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Fibre Channel Hardware List...
Matthew Jacob wrote: Oh, yeah, about this, 2300 support is comint "real soon" -this will be 2GBit. [my perhaps poorly worded question] About the 2Gb drives, sorry! I have no clue as yet about this! Sorry for the confusion, I meant drives capable of 2 Gbit/s, which the 2300 will supposingly support. My question was that many enclosure support 1 Gbit/s, right ? So, I was wondering have you heard about those which support 2 [Gbit/s] ? Because one do need to have something in between the 2300 card and Cheetah-4 FC drive, right :-) ? Adapter in a case of 1 drive only, I presume, and enclosure in the case of multiple drives. Thanks again ! You're welcome! Regards, Andrei To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Fibre Channel Hardware List...
On Thu, 8 Feb 2001, Andrei A. Dergatchev wrote: Matthew Jacob wrote: Oh, yeah, about this, 2300 support is comint "real soon" -this will be 2GBit. [my perhaps poorly worded question] About the 2Gb drives, sorry! I have no clue as yet about this! Sorry for the confusion, I meant drives capable of 2 Gbit/s, which the 2300 will supposingly support. My question was that many enclosure support 1 Gbit/s, right ? So, I was wondering have you heard about those which support 2 [Gbit/s] ? I've heard that Ancor has one. I think that Brocade has one too. I have had access as yet to neither. Because one do need to have something in between the 2300 card and Cheetah-4 FC drive, right :-) ? Adapter in a case of 1 drive only, I presume, and enclosure in the case of multiple drives. Yes. I have no idea who is, as yet, building enclosures with 2Gb interfaces either. This is much like Ultra3- it took at least a year after Ultra3 came out (with disks ready to go) to find a JBOD that would be Ultra3 to the JBOD itself. -matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: atomic_ question
On 2001-Feb-08 18:21:07 +0100, Bernd Walter [EMAIL PROTECTED] wrote: Are atomic_* implementations allowed to spin/sleep? The atomic_* operations are the primitives used to build all the higher level locking functions. Therefore you are not allowed to sleep. As for spinning: You can't implement them using a `normal' spinlock. Some architectures, eg the Alpha, don't have RMW primitives. The Alpha has load-locked and store-conditional instructions which let you build atomic operations - you need to spin between the load and store if the store fails. The store will only fail if you took an interrupt between the load and store or if another master updated the location between your load and store. Look into /sys/alpha/alpha/atomic.s for code. The only way to implement them on these platforms is to use a lock. Except that locks are built using the atomic_* functions. Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Fibre Channel Hardware List...
Hi, On Thu, 8 Feb 2001, Matthew Jacob wrote: On Thu, 8 Feb 2001, Andrei A. Dergatchev wrote: Sorry for the confusion, I meant drives capable of 2 Gbit/s, which the 2300 will supposingly support. My question was that many enclosure support 1 Gbit/s, right ? So, I was wondering have you heard about those which support 2 [Gbit/s] ? I've heard that Ancor has one. I think that Brocade has one too. I have had access as yet to neither. It's true, we at Qlogic (formerly Ancor) do have a 2Gb switch in the works. We demoed said switch at Comdex. It's pretty impressive watching your data stream by at 198MB/second! Interestingly enough, said switch runs Linux as the underlying OS (if I had been at Ancor 1 month before I got here, we'd be running FreeBSD instead!) -- Kyle Mestery / Qlogic Corporation \ [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: atomic_ question
On Fri, Feb 09, 2001 at 07:57:50AM +1100, Peter Jeremy wrote: On 2001-Feb-08 18:21:07 +0100, Bernd Walter [EMAIL PROTECTED] wrote: Are atomic_* implementations allowed to spin/sleep? The atomic_* operations are the primitives used to build all the higher level locking functions. Therefore you are not allowed to sleep. As for spinning: You can't implement them using a `normal' spinlock. Some architectures, eg the Alpha, don't have RMW primitives. The Alpha has load-locked and store-conditional instructions which let you build atomic operations - you need to spin between the load and store if the store fails. The store will only fail if you took an interrupt between the load and store or if another master updated the location between your load and store. Look into /sys/alpha/alpha/atomic.s for code. The alpha way of doing it is very similar to sparcv9. But the alpha code and the code neccesary for sparcv9 has a difference compared to normal spinning. If you get interrupted the interupt code can modify the same value without getting blocked while the interrupted code simply needs another cycle. On sparcv8 you don't have an operation doing conditionaly stores and you don't have RMW operations. The only way to do is to have a global lock variable on which you spin until the current client finishes. That means you can't use them in interrupt code! I saw that some implementations for atomic code for sparcv8 disables interrupts before fetching the lock to suround this problem. Do we grant usuage of the atomic functions in interrupt code? If yes there is a need to disable interrupts! I'm not talking about interrupt threads. -- B.Walter COSMO-Project http://www.cosmo-project.de [EMAIL PROTECTED] Usergroup [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: atomic_ question
On 08-Feb-01 Bernd Walter wrote: Do we grant usuage of the atomic functions in interrupt code? If yes there is a need to disable interrupts! I'm not talking about interrupt threads. Yes, we use spin mutexes to schedule ithreads, and we use other atomic operations in IPI handlers. -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: What's changed recently with vmware/linuxemu/file I/O
On Thu, Feb 08, 2001 at 04:58:17AM -0800, Julian Elischer wrote: =20 Looks like some way of clustering this might achieve a lot. =20 what does systat -vmstat or vmstat 1 show? Better still, I guess we could do a linux-truss and see what it's doing... I believe that it's strace under linux. If someone can provide me with a binary of this tool I'll happily run it here and see what vmware's doing. Joe The problem seems to have gone away after this (kindly pointed out to me by Maxim after my other post about xsane dropping cores): : Subject: cvs commit: src/lib/libc/stdio findfp.c : Date: Wed, 7 Feb 2001 09:34:50 -0800 (PST) : From: Maxim Sobolev [EMAIL PROTECTED] : To: [EMAIL PROTECTED], [EMAIL PROTECTED] : : sobomax 2001/02/07 09:34:49 PST : : Modified files: : lib/libc/stdio findfp.c : Log: : Fix a f^Hdamn typo, which prevented to fopen() more that 17 files at once. : : Tested by: knu, sobomax and other #bsdcode'rs : : Revision ChangesPath : 1.9 +2 -2 src/lib/libc/stdio/findfp.c -- Brian [EMAIL PROTECTED]brian@[uk.]FreeBSD.org http://www.Awfulhak.org brian@[uk.]OpenBSD.org Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
TI-RPC status (99% done)
Hi all, I have reworked my patches and I run now successfully CURRENT with them, make buildworld has been sucessfull and everything seems to work so far. http://www.attic.ch/patches/rpc.diff_02082001-2.sh.tgz Can't we commit this to CURRENT now ? I'd like to see a history of my changes, I don't have the patch in cvs here, and I'd like that others see the changes too and can tell me if they are correct. These are the changes I have done on this release. # rpc.diff_02082001-2: # Added IPPROT_ST to rpcinfo and rpcbind to correct # output of 'rpcinfo -p'. All Unix socket connections # are correctly displayed as 'local' instead of garbage. # # Corrected rpcinfo.8 to be correctly displayed. I had # to convert all .Nm "" to .Nm # # Fixed some .rej, some man-pages have been updated. # # Removed again some _THREAD_SAFE definitions to make # it fit to the new CURRENT libc-format. More on this # will follow this week. Just go into you CURRENT Source tree and run the patch.sh, then make world and run mergemaster after (to copy all needed files like netconfig and the patches defaults/rc.conf Thank you for your time you spend on the patch. Martin Martin Blapp, [EMAIL PROTECTED] Improware AG, UNIX solution and service provider Zurlindenstrasse 29, 4133 Pratteln, Switzerland Phone: +41 79 370 26 05, Fax: +41 61 826 93 01 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: atomic_ question
On 2001-Feb-08 22:21:32 +0100, Bernd Walter [EMAIL PROTECTED] wrote: On sparcv8 you don't have an operation doing conditionaly stores and you don't have RMW operations. The only way to do is to have a global lock variable on which you spin until the current client finishes. The SPARC architecture supports SMP so there must be some synchronisation primitive that works between processors (disabling interrupts only works on the current processor). Normally the same primitive can be used to synchronise accesses within the same processor. I know the older SPARC's had a test-and-set instruction which was locked RMW - there must be something similar in v8 and v9. Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
/usr/src/UPDATING
Hi Warner, Can you add a remark about the devfs and vinum conflict to UPDATING ? I had serious problems today, because I have been bitten by this conflict. Devfs is now in GENERIC-KERNEL in CURRENT, and if you upgrade and have vinum set up on on /usr, you cannot mount it - no way. mkdir: /dev/vinum: Operation not supported mkdir: /dev/vinum: Operation not supported mkdir: /dev/vinum: Operation not supported mkdir: /dev/vinum: Operation not supported Can't create /dev/vinum/Control: No such file or directory Can't create /dev/vinum/control: No such file or directory Can't create /dev/vinum/controld: No such file or directory Can't get vinum config: Bad file descriptor Can't open /dev/vinum/Control: Bad file descriptor It is not possible to unmount devfs, so only way is to boot an old kernel (if it works) or boot a cd-rom. This should be definitly in UPDATING. You have to compile a Kernel without devfs. Possible Text: Remove "option devfs" from your KERNEL-CONFIG if you are using vinum and you upgrade from STABLE. Else you cannot mount your vinum-volumes. Martin Martin Blapp, [EMAIL PROTECTED] Improware AG, UNIX solution and service provider Zurlindenstrasse 29, 4133 Pratteln, Switzerland Phone: +41 79 370 26 05, Fax: +41 61 826 93 01 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: atomic_ question
On Fri, Feb 09, 2001 at 11:00:04AM +1100, Peter Jeremy wrote: On 2001-Feb-08 22:21:32 +0100, Bernd Walter [EMAIL PROTECTED] wrote: On sparcv8 you don't have an operation doing conditionaly stores and you don't have RMW operations. The only way to do is to have a global lock variable on which you spin until the current client finishes. The SPARC architecture supports SMP so there must be some synchronisation primitive that works between processors (disabling interrupts only works on the current processor). Normally the same primitive can be used to synchronise accesses within the same processor. I know the older SPARC's had a test-and-set instruction which was locked RMW - there must be something similar in v8 and v9. sparcv8 has: LDSTUB - which is a atomic load into register and store 0xff SWAP - which exchanges a register with memory atomicly sparcv9 has additionaly the Comapare And Set (CAS) operation which makes it similar in use as alpha. I can't speak for sparcv7 and older but maybe you are refering to sparcv9 with it's CAS operation as an "older" SPARC or have a vendor specific extension in mind. Disabling interrupts will work fine because the reason is to avoid deadlocks. The only thing needed is that the processor holding the lock can't be interrupted until it's finished. If another CPU want's the same lock it can spinwait because the other CPU still gets the chance to release the lock. No doubt the available primitives are enough - but I wanted to know if its neccessary to go the complete ugly way. The sparv8 way for FreeBSDs atomic_ is now clear to me: disable ints for the CPU in question fetch the lock do the real work wmb unlock restore ints Thank you all for making this clear. -- B.Walter COSMO-Project http://www.cosmo-project.de [EMAIL PROTECTED] Usergroup [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: atomic_ question
* Bernd Walter [EMAIL PROTECTED] [010208 09:21] wrote: Are atomic_* implementations allowed to spin/sleep? The question is because some platforms don't have atomic operations for adding and so on (e.g. sparcv8). Actually, you can use atomic_* on sparc, but you're limited to 24 bits. The only way to implement them on these platforms is to use a lock. Now I'm wonder if the use of a sleep mutex is allowed or is a simple spinning lock the sensefull choice. Either one would work. -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
buildworld failed
Dunno whether this happens only to me, but in my machine, latest -CURRENT buildworld target failed with this message: === share/monetdef grep -v '^#' /usr/src/share/monetdef/en_US.ISO_8859-1.src en_US.ISO_8859-1.out grep -v '^#' /usr/src/share/monetdef/nl_NL.ISO_8859-1.src nl_NL.ISO_8859-1.out grep -v '^#' /usr/src/share/monetdef/ru_RU.KOI8-R.src ru_RU.KOI8-R.out === share/msgdef grep -v '^#' /usr/src/share/msgdef/en_US.ISO_8859-1.src en_US.ISO_8859-1.out grep -v '^#' /usr/src/share/msgdef/nl_NL.ISO_8859-1.src nl_NL.ISO_8859-1.out grep -v '^#' /usr/src/share/msgdef/ru_RU.KOI8-R.src ru_RU.KOI8-R.out === share/numericdef make: don't know how to make nl_NL.ISO_8859-1.out. Stop *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error /john To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: What's changed recently with vmware/linuxemu/file I/O
Dag-Erling Smorgrav writes:
Julian Elischer [EMAIL PROTECTED] writes:
I believe that vmware mmaps a region of memory and then somehow syncs
it to disk. (It is certainly doing something like it here).
Theory: VMWare mmaps a region of memory corresponding to the virtual
machine's "physical" RAM, then touches every page during startup.
Unless some form of clustering is done, this causes 16384 write
operations for a 64 MB virtual machine...
Pretty much. But the issue is that this should never hit the disk
unless we're under memory pressure because it is mapped MAP_NOSYNC
(actually the file is unlinked prior to the mmap() and a heuristic in
vm_mmap() detects this and sets MAP_NOSYNC).
The real problem is that our MAP_NOSYNC doesn't fully work in at least
one major case. As I understand it, the technique we use is to set
the MAP_ENTRY_NOSYNC in the map entry at mmap time. On a write fault,
PG_NOSYNC is set in the page's flags. A lazy msync will skip
PG_NOSYNC pages.
The problem comes when a page is read from prior to being written
to. The page gets mapped in read/write and we don't take a write
fault, so the PG_NOSYNC flag never gets set. (This accounts for the
flurry of disk i/o shortly after vmware starts). When the pages get
sunk to disk, the vnode is locked and the application will freeze in a
"vmpfw"
The following patch sets PG_NOSYNC on faults other than write faults.
This seems to work for my test program, and for vmware (I've only very
briefly tested it). Assuming that it is correct, the code around it
should be reorganized somewhat. This is against -stable, as I don't
have any -current i386s..
Index: vm_fault.c
===
RCS file: /home/ncvs/src/sys/vm/vm_fault.c,v
retrieving revision 1.108.2.2
diff -u -r1.108.2.2 vm_fault.c
--- vm_fault.c 2000/08/04 22:31:11 1.108.2.2
+++ vm_fault.c 2001/02/08 23:04:02
@@ -804,6 +804,10 @@
}
vm_page_dirty(fs.m);
vm_pager_page_unswapped(fs.m);
+ } else {
+ if ((fs.entry-eflags MAP_ENTRY_NOSYNC)
+ (fs.m-dirty == 0))
+ vm_page_flag_set(fs.m, PG_NOSYNC);
}
}
Cheers,
Drew
--
Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin
Duke University Email: [EMAIL PROTECTED]
Department of Computer Science Phone: (919) 660-6590
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
RE: buildworld failed
On 09-Feb-01 John Indra wrote: Dunno whether this happens only to me, but in my machine, latest -CURRENT buildworld target failed with this message: That has been fixed, you want to cvsup and try again. -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: What's changed recently with vmware/linuxemu/file I/O
David Malone wrote: On Thu, Feb 08, 2001 at 02:47:59PM +, Josef Karthauser wrote: what does systat -vmstat or vmstat 1 show? Better still, I guess we could do a linux-truss and see what it's doing... I believe that it's strace under linux. If someone can provide me with a binary of this tool I'll happily run it here and see what vmware's doing. You could use FreeBSD ktrace and then the linux_kdump port. David. I believe truss can do linux binaries which is why I mantionned it. (but I have never done it) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message -- __--_|\ Julian Elischer / \ [EMAIL PROTECTED] ( OZ) World tour 2000-2001 --- X_.---._/ v To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Fibre Channel Hardware List...
"Kyle A.D. Mestery" wrote: It's true, we at Qlogic (formerly Ancor) do have a 2Gb switch in the works. We demoed said switch at Comdex. It's pretty impressive watching your data stream by at 198MB/second! Interestingly enough, said switch runs Linux as the underlying OS (if I had been at Ancor 1 month before I got here, we'd be running FreeBSD instead!) that's easy to fix: Can you please send me all your changes and drivers for linux in your product? You may email them to "[EMAIL PROTECTED]" or put them up at a generally accessible web server for our perusal.. -- __--_|\ Julian Elischer / \ [EMAIL PROTECTED] ( OZ) World tour 2000-2001 --- X_.---._/ v To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kernel trap 12 with interrupts disabled
On Thu, 8 Feb 2001, Alexander Leidinger wrote: if I run a program compiled with gcc's function profiling option I get "kernel trap 12 with interrupts disabled". This happens with the standard profiling option -pg. Pagefaults occur in copyin() (called from addupc_task() which is called from ast()) while sched_lock is held. This is not good. Incrementing the profiling counters is supposed to be pushed to ordinary process context so that things like copyin() can work (they have to be able to fault in pages, so they have to be able to sleep...), so using sched_lock to lock things here is wrong. If I run it withhin X11, the machine deadlocks hard (no response from the numlock led on the keyboard), withhin a virtual console I get a lot of "kernel trap ..." and the program runs fine. It's surprising that it doesn't always deadlock. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
