From owner-freebsd-current Sun Jul 21 0:15: 1 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5C03E37B400; Sun, 21 Jul 2002 00:14:42 -0700 (PDT) Received: from dastardly.newsbastards.org.72.27.172.IN-addr.ARPA.NetScum.dyndns.dk (dclient217-162-144-23.hispeed.ch [217.162.144.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id DFF5C43E42; Sun, 21 Jul 2002 00:14:39 -0700 (PDT) (envelope-from bounce@dcf77-zeit.netscum.dyndns.dk) Received: from beerswilling.netscum.dyndns.dk (ipv6.NetScum.dyndns.dk [2002:d9a2:9017:0:200:c0ff:fefc:19aa]) by dastardly.newsbastards.org.72.27.172.IN-addr.ARPA.NetScum.dyndns.dk (8.11.6/8.11.6-SPAMMERS-DeLiGHt) with ESMTP id g6L7EYS00480 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified NO); Sun, 21 Jul 2002 09:14:37 +0200 (CEST) (envelope-from bounce@dcf77-zeit.netscum.dyndns.dk) Received: (from root@localhost) by beerswilling.netscum.dyndns.dk (8.11.6/SMI-4.1-R00T0WNED) id g6L7EYi00479; Sun, 21 Jul 2002 09:14:34 +0200 (CEST) (envelope-from bounce@dcf77-zeit.netscum.dyndns.dk) Date: Sun, 21 Jul 2002 09:14:34 +0200 (CEST) Message-Id: <200207210714.g6L7EYi00479@beerswilling.netscum.dyndns.dk> From: BOUWSMA Beery Organization: Men not wearing any pants that dont shave To: freebsd-current@freebsd.org, freebsd-fs@freebsd.org Subject: UFS2 panic (and other issues) at mount with unusual `newfs' values X-Hacked: via telnet to your port 25, what else? X-Internet-Access-Provided-By: CABAL MODEM (all hail CABAL) X-NetScum: Yes X-One-And-Only-Real-True-Fluffy: No Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG [IPv6-only address above; strip the obvious for IPv4-only mail] [sent to both -current and the -fs list, for no particular reason] Howdy, -current as of about a day ago. Decided to make a monster UFS2 disk to see if it works. It seems that any -f fsize value larger than 8192 given to `newfs' creates a UFS2 filesystem that causes a panic when mounted, even read-only. This appears true for `-b 16384 -f 16384', `-b 32768 -f 16384', and `-b 65536' with both -f 16384 and 32768. Using a value of 8192 for -f with 65536 and 32768 for -b seems in most cases to create a filesystem I can use, regardless of what other parameters I give, so the mount-time panic can be readily repeated. First of all, `newfs' normally coredumps as I observed earlier when a too-large blocksize is given. As the case for a too-small blocksize and fragment size is detected and twiddled in mkfs.c now, I suggest that the same be done for too large, rather than dumping core. The following patch to src/sbin/newfs/mkfs.c can do this: --- mkfs.c-ORIG Fri Jul 19 18:58:40 2002 +++ mkfs.c Sun Jul 21 00:00:44 2002 @@ -196,10 +196,15 @@ if (sblock.fs_bsize < MINBSIZE) { printf("increasing block size from %d to minimum (%d)\n", sblock.fs_bsize, MINBSIZE); sblock.fs_bsize = MINBSIZE; } + if (sblock.fs_bsize > MAXBSIZE) { + printf("decreasing block size from %d to maximum (%d)\n", + sblock.fs_bsize, MAXBSIZE); + sblock.fs_bsize = MAXBSIZE; + } if (sblock.fs_bsize < sblock.fs_fsize) { printf("increasing block size from %d to fragment size (%d)\n", sblock.fs_bsize, sblock.fs_fsize); However, there's a problem, in that bsize, from which sblock.fs_bsize is obtained, has already been used to set a number of other values in newfs.c. So it's probably better to do the check at the time the value is supplied, by this patch to newfs/newfs.c: --- newfs.c-ORIG Fri Jun 21 23:24:53 2002 +++ newfs.c Sun Jul 21 07:12:49 2002 @@ -186,7 +186,8 @@ optarg); break; case 'b': - if ((bsize = atoi(optarg)) < MINBSIZE) + if ((bsize = atoi(optarg)) < MINBSIZE || + bsize > MAXBSIZE) errx(1, "%s: bad block size", optarg); break; case 'c': This, unfortunately, doesn't give a clue as to what the minimum and maximum permissible values are, but I didn't see a simple way of doing this without recomputing all the values (like maxcontig) that depend on bsize, after adjusting it. And speaking of which, since the value for sblock.fs_bsize can be adjusted (theoretically, in what used to be exit() statements long ago), I'm wondering how right it is that the uncorrected bsize gets used before correction to calculate other values. Hmmm. You'll see a result of this in the example I give below (for maxcontig) Still, it's possible to create a new filesystem without real problems, that panics upon mount (even read-only), using values that are theoretically within range, such as the following first commandline I used: /usr/local/obj/5.0-CURRENT/usr/src/sbin/newfs/newfs -U -N -O 2 -i 1549357135 -b 131072 -f 32768 -g 134217728 -h 128 -m 0 -o space /dev/ad2s1e Superficially, the new filesystem looked fine... decreasing block size from 131072 to maximum (65536) ^^^ [my first, but improper, hack] Maxcontig raised to 131072 ^^^ [should not happen, because of my improper hack] density reduced from 1549357135 to 44585039 /dev/ad2s1e: 156334.5MB (320172992 sectors) block size 65536, fragment size 32768 using 15 cylinder groups of 10881.06MB, 174097 blks, 512 inodes. with soft updates super-block backups (for fsck -b #) at: 256, 22284672, 44569088, 66853504, 89137920, 111422336, 133706752, 155991168, 178275584, 200560000, 222844416, 245128832, 267413248, 289697664, 311982080 [00:51:10]root@dastardly.newsbastards.org:~{520}# tunefs -p /dev/ad2s1e tunefs: soft updates: (-n) enabled tunefs: maximum contiguous block count: (-a) 2 tunefs: maximum blocks per file in a cylinder group: (-e) 16384 tunefs: average file size: (-f) 134217728 tunefs: average number of files in a directory: (-s) 128 tunefs: minimum percentage of free space: (-m) 0% tunefs: optimization preference: (-o) space # size offset fstype [fsize bsize bps/cpg] c: 320172993 0 unused 0 0 # (Cyl. 0 - 317631*) e: 320172993 0 4.2BSD 32768 65536 20514 # (Cyl. 0 - 317631*) But as soon as I attempt to mount the filesystem, read-only, *POW* instant panic. Details: panic: bwrite: buffer is not busy??? panic messages: --- panic: vm_fault: fault on nofault entry, addr: c2f9a000 syncing disks... panic: bwrite: buffer is not busy??? Uptime: 46m16s pfs_vncache_unload(): 1 entries remaining Dumping 72 MB #2 0xc01ec2e5 in panic () at /usr/src/sys/kern/kern_shutdown.c:493 #3 0xc022003f in bwrite (bp=0xc2a872c8) at /usr/src/sys/kern/vfs_bio.c:797 #4 0xc0221391 in vfs_bio_awrite (bp=0xc2a872c8) at /usr/src/sys/kern/vfs_bio.c:1637 #5 0xc01c725c in spec_fsync (ap=0xc6dd474c) at /usr/src/sys/fs/specfs/spec_vnops.c:403 #6 0xc01c6e4b in spec_vnoperate (ap=0x0) at /usr/src/sys/fs/specfs/spec_vnops.c:121 #7 0xc0299279 in ffs_sync (mp=0xc0a65600, waitfor=2, cred=0xc0a55e80, td=0xc0365a80) at vnode_if.h:463 #8 0xc022f0d0 in sync (td=0xc0365a80, uap=0x0) at /usr/src/sys/kern/vfs_syscalls.c:127 #9 0xc01ebdc1 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:254 #10 0xc01ec2e5 in panic () at /usr/src/sys/kern/kern_shutdown.c:493 #11 0xc02a7b97 in vm_fault (map=0xc0834000, vaddr=3271139328, fault_type=1 '\001', fault_flags=0) at /usr/src/sys/vm/vm_fault.c:259 #12 0xc02debc5 in trap_pfault (frame=0xc6dd4938, usermode=0, eva=3271139328) at /usr/src/sys/i386/i386/trap.c:747 #13 0xc02de741 in trap (frame= {tf_fs = 24, tf_es = 16, tf_ds = 16, tf_edi = -1050185728, tf_esi = -10238 27968, tf_ebp = -958576032, tf_isp = -958576284, tf_ebx = -1023836160, tf_edx = -1049891840, tf_ecx = 6144, tf_eax = -26357760, tf_trapno = 12, tf_err = 0, tf_e ip = -1070738998, tf_cs = 8, tf_eflags = 66070, tf_esp = -1047358696, tf_ss = 0} ) at /usr/src/sys/i386/i386/trap.c:445 #14 0xc02d16e8 in calltrap () at {standard input}:98 #15 0xc0297772 in ffs_mount (mp=0xc1918400, path=0xc1922180 "/mnt", data=---Can' t read userspace from dump, or kernel process--- ) at /usr/src/sys/ufs/ffs/ffs_vfsops.c:350 #16 0xc0229941 in vfs_mount (td=0xc1565840, fstype=0xc14c8ad0 "ufs", fspath=0xc1922180 "/mnt", fsflags=1, fsdata=0xbfbff090) at /usr/src/sys/kern/vfs_mount.c:944 #17 0xc0229156 in mount (td=0xc1565840, uap=0xc6dd4d14) at /usr/src/sys/kern/vfs_mount.c:709 #18 0xc02df199 in syscall (frame= {tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 134809385, tf_esi = -1077939 888, tf_ebp = -1077939960, tf_isp = -958575244, tf_ebx = 0, tf_edx = 0, tf_ecx = -1077940224, tf_eax = 21, tf_trapno = 12, tf_err = 2, tf_eip = 134524503, tf_cs = 31, tf_eflags = 582, tf_esp = -1077940164, tf_ss = 47}) at /usr/src/sys/i386/i386/trap.c:1049 #19 0xc02d171d in syscall_with_err_pushed () at {standard input}:128 ---Can't read userspace from dump, or kernel process--- Here's a slightly cleaner dump, with different parameters used when doing the newfs... panic: vm_fault: fault on nofault entry, addr: c308a000 panic messages: --- panic: vm_fault: fault on nofault entry, addr: c308a000 syncing disks... 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1: dev:ad2s1e, flags:20000220, blkno:128, lblkno:128 giving up on 1 buffers Uptime: 32m50s pfs_vncache_unload(): 1 entries remaining Dumping 72 MB #3 0xc02a7b97 in vm_fault (map=0xc0834000, vaddr=3272122368, fault_type=1 '\001', fault_flags=0) at /usr/src/sys/vm/vm_fault.c:259 #4 0xc02debc5 in trap_pfault (frame=0xc731b938, usermode=0, eva=3272122368) at /usr/src/sys/i386/i386/trap.c:747 #5 0xc02de741 in trap (frame= {tf_fs = 24, tf_es = 16, tf_ds = 16, tf_edi = -1047912448, tf_esi = -10228 44928, tf_ebp = -953042336, tf_isp = -953042588, tf_ebx = -1022853120, tf_edx = -1047557376, tf_ecx = 6144, tf_eax = -25067520, tf_trapno = 12, tf_err = 0, tf_e ip = -1070738998, tf_cs = 8, tf_eflags = 66070, tf_esp = -1048027536, tf_ss = 0} ) at /usr/src/sys/i386/i386/trap.c:445 #6 0xc02d16e8 in calltrap () at {standard input}:98 #7 0xc0297772 in ffs_mount (mp=0xc172a400, path=0xc1662300 "/mnt", data=---Can' t read userspace from dump, or kernel process--- ) at /usr/src/sys/ufs/ffs/ffs_vfsops.c:350 #8 0xc0229941 in vfs_mount (td=0xc16cef00, fstype=0xc14c8920 "ufs", fspath=0xc1662300 "/mnt", fsflags=1, fsdata=0xbfbff070) at /usr/src/sys/kern/vfs_mount.c:944 #9 0xc0229156 in mount (td=0xc16cef00, uap=0xc731bd14) at /usr/src/sys/kern/vfs_mount.c:709 #10 0xc02df199 in syscall (frame= {tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 134809385, tf_esi = -1077939 920, tf_ebp = -1077939992, tf_isp = -953041548, tf_ebx = 0, tf_edx = 0, tf_ecx = ---Type to continue, or q to quit--- -1077940480, tf_eax = 21, tf_trapno = 12, tf_err = 2, tf_eip = 134524503, tf_cs = 31, tf_eflags = 582, tf_esp = -1077940196, tf_ss = 47}) at /usr/src/sys/i386/i386/trap.c:1049 #11 0xc02d171d in syscall_with_err_pushed () at {standard input}:128 ---Can't read userspace from dump, or kernel process--- (kgdb) Using fsize of 8192 with bsize of 65536 did *not* result in a panic, even with other values like [07:30:05]root@dastardly.newsbastards.org:~{512}# /usr/local/obj/5.0-CURRENT/us r/src/sbin/newfs/newfs -U -O 2 -i 14864463 -b 65536 -f 8192 -g 134217728 -h 12 8 -m 0 -o space /dev/ad2s1e /dev/ad2s1e: 156334.5MB (320172992 sectors) block size 65536, fragment size 8192 using 44 cylinder groups of 3628.00MB, 58048 blks, 256 inodes. with soft updates super-block backups (for fsck -b #) at: 256, 7430400, 14860544, 22290688, 29720832, 37150976, 44581120, 52011264, 59441408, 66871552, 74301696, 81731840, 89161984, 96592128, 104022272, 111452416, 118882560, 126312704, 133742848, 141172992, 148603136, 156033280, 163463424, 170893568, 178323712, 185753856, 193184000, 200614144, 208044288, 215474432, 222904576, 230334720, 237764864, 245195008, 252625152, 260055296, 267485440, 274915584, 282345728, 289775872, 297206016, 304636160, 312066304, 319496448 This one mounted fine, and seems to be about the `best' I can do at the moment. Yeah yeah yeah, I know the fine manpage sez The optimal block:fragment ratio is 8:1. Other ratios are possible, but are not recommended, and may produce poor results. but I've used such values with UFS-not-2 with no real problems. If anyone's wondering about such a thing, when i attempt to mount this disk under -stable (without UFS2), it sees the original old UFS filesystem I had created several days ago on this disk as if the UFS2 filesystem never was created. Whether this might have anything to do with the panics I see, well, I thought I should mention that before doing the -O 2 UFS2 newfs'ing, I had created a normal filesystem, should that mean anything. And obviously, I won't be able to do anything with this UFS2 filesystem under -stable, yet... thanks barry bouwsma To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 21 1:33:38 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2ED2937B400 for ; Sun, 21 Jul 2002 01:33:37 -0700 (PDT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1EF9443E67 for ; Sun, 21 Jul 2002 01:33:36 -0700 (PDT) (envelope-from ache@pobrecita.freebsd.ru) Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.12.5/8.12.5) with ESMTP id g6L8XEvm006087; Sun, 21 Jul 2002 12:33:19 +0400 (MSD) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.12.5/8.12.5/Submit) id g6L8XBOx006086; Sun, 21 Jul 2002 12:33:11 +0400 (MSD) (envelope-from ache) Date: Sun, 21 Jul 2002 12:33:09 +0400 From: "Andrey A. Chernov" To: Bruce Evans Cc: Bakul Shah , current@FreeBSD.ORG Subject: Re: suspend bug Message-ID: <20020721083307.GA6009@nagual.pp.ru> References: <20020721141841.H18880-100000@gamplex.bde.org> <20020721145145.R19118-100000@gamplex.bde.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020721145145.R19118-100000@gamplex.bde.org> User-Agent: Mutt/1.5.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Jul 21, 2002 at 14:54:00 +1000, Bruce Evans wrote: > > The bug is actually in su. It happens with a pre-KSEIII kernel. Backing > out rev.1.54 of su.c (which was apparently supposed to fix a related bug > tcsh's fg command) fixes it. Feel free to back it out when kernel will be fixed. As workaround it is more useful at this moment, since "suspend + fg" it fixes is more common thing, then "stop $$ + fg" -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 21 3:26:44 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8A9D737B400 for ; Sun, 21 Jul 2002 03:26:38 -0700 (PDT) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6956C43E4A for ; Sun, 21 Jul 2002 03:26:37 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id UAA31678; Sun, 21 Jul 2002 20:26:11 +1000 Date: Sun, 21 Jul 2002 20:30:14 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: "Andrey A. Chernov" Cc: Bakul Shah , Subject: Re: suspend bug In-Reply-To: <20020721083307.GA6009@nagual.pp.ru> Message-ID: <20020721202537.U19918-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 21 Jul 2002, Andrey A. Chernov wrote: > On Sun, Jul 21, 2002 at 14:54:00 +1000, Bruce Evans wrote: > > > > The bug is actually in su. It happens with a pre-KSEIII kernel. Backing > > out rev.1.54 of su.c (which was apparently supposed to fix a related bug > > tcsh's fg command) fixes it. > > Feel free to back it out when kernel will be fixed. As workaround it is > more useful at this moment, since "suspend + fg" it fixes is more common > thing, then "stop $$ + fg" Er, there is no kernel bug here AFAIK. I don't really understand rev.1.54 of su.c. Is it related to the PAM brokenness that is worked around in rev.1.53? Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 21 4:11:28 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CA2EE37B400 for ; Sun, 21 Jul 2002 04:11:22 -0700 (PDT) Received: from dilbert.robbins.dropbear.id.au (153.a.004.mel.iprimus.net.au [210.50.36.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id C0DB743E3B for ; Sun, 21 Jul 2002 04:11:12 -0700 (PDT) (envelope-from tim@robbins.dropbear.id.au) Received: from dilbert.robbins.dropbear.id.au (cld63yozd1h80imf@localhost [127.0.0.1]) by dilbert.robbins.dropbear.id.au (8.12.3/8.12.3) with ESMTP id g6LBB7Eu037499 for ; Sun, 21 Jul 2002 21:11:07 +1000 (EST) (envelope-from tim@dilbert.robbins.dropbear.id.au) Received: (from tim@localhost) by dilbert.robbins.dropbear.id.au (8.12.3/8.12.3/Submit) id g6LB9oCD037428 for current@FreeBSD.ORG; Sun, 21 Jul 2002 21:09:50 +1000 (EST) Date: Sun, 21 Jul 2002 21:09:49 +1000 From: Tim Robbins To: current@FreeBSD.ORG Subject: Re: suspend bug Message-ID: <20020721210949.A37074@dilbert.robbins.dropbear.id.au> References: <20020721083307.GA6009@nagual.pp.ru> <20020721202537.U19918-100000@gamplex.bde.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020721202537.U19918-100000@gamplex.bde.org>; from bde@zeta.org.au on Sun, Jul 21, 2002 at 08:30:14PM +1000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Jul 21, 2002 at 08:30:14PM +1000, Bruce Evans wrote: > On Sun, 21 Jul 2002, Andrey A. Chernov wrote: > > > On Sun, Jul 21, 2002 at 14:54:00 +1000, Bruce Evans wrote: > > > > > > The bug is actually in su. It happens with a pre-KSEIII kernel. Backing > > > out rev.1.54 of su.c (which was apparently supposed to fix a related bug > > > tcsh's fg command) fixes it. > > > > Feel free to back it out when kernel will be fixed. As workaround it is > > more useful at this moment, since "suspend + fg" it fixes is more common > > thing, then "stop $$ + fg" > > Er, there is no kernel bug here AFAIK. I don't really understand rev.1.54 > of su.c. Is it related to the PAM brokenness that is worked around in > rev.1.53? Suspending chpass and vipw does not work correctly (like it does in 4.6.1), either: $ chpass #Changing user information for tim. *snip* *^Z* [1] + Stopped chpass $ fg chpass [1] + Stopped chpass $ fg chpass #Changing user information for tim. I don't know if this is KSE-related or was introduced in the recent modifications to src/lib/libutil/pw_util.c. crontab -e behaves correctly when suspended. Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 21 4:21:44 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E253F37B401 for ; Sun, 21 Jul 2002 04:21:31 -0700 (PDT) Received: from web20903.mail.yahoo.com (web20903.mail.yahoo.com [216.136.226.225]) by mx1.FreeBSD.org (Postfix) with SMTP id 165E343E5E for ; Sun, 21 Jul 2002 04:21:31 -0700 (PDT) (envelope-from bsddiy@yahoo.com) Message-ID: <20020721112130.22708.qmail@web20903.mail.yahoo.com> Received: from [218.108.153.138] by web20903.mail.yahoo.com via HTTP; Sun, 21 Jul 2002 04:21:30 PDT Date: Sun, 21 Jul 2002 04:21:30 -0700 (PDT) From: David Xu Subject: Re: suspend bug To: Tim Robbins , "current@FreeBSD.ORG" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I knew the bug, is this patch works for you? --- kern_sig.c.old Sun Jul 21 15:38:00 2002 +++ kern_sig.c Sun Jul 21 16:31:02 2002 @@ -1657,7 +1657,7 @@ #endif break; /* == ignore */ } -#if 0 + /* * If there is a pending stop signal to process * with default action, stop here, @@ -1679,16 +1679,10 @@ PROC_UNLOCK(p->p_pptr); mtx_lock_spin(&sched_lock); stop(p); - PROC_UNLOCK(p); - DROP_GIANT(); - p->p_stats->p_ru.ru_nivcsw++; - mi_switch(); mtx_unlock_spin(&sched_lock); - PICKUP_GIANT(); - PROC_LOCK(p); break; } else -#endif + if (prop & SA_IGNORE) { /* * Except for SIGCONT, shouldn't get here. ----- Original Message ----- From: "Tim Robbins" To: Sent: Sunday, July 21, 2002 7:09 PM Subject: Re: suspend bug > On Sun, Jul 21, 2002 at 08:30:14PM +1000, Bruce Evans wrote: > > > On Sun, 21 Jul 2002, Andrey A. Chernov wrote: > > > > > On Sun, Jul 21, 2002 at 14:54:00 +1000, Bruce Evans wrote: > > > > > > > > The bug is actually in su. It happens with a pre-KSEIII kernel. Backing > > > > out rev.1.54 of su.c (which was apparently supposed to fix a related bug > > > > tcsh's fg command) fixes it. > > > > > > Feel free to back it out when kernel will be fixed. As workaround it is > > > more useful at this moment, since "suspend + fg" it fixes is more common > > > thing, then "stop $$ + fg" > > > > Er, there is no kernel bug here AFAIK. I don't really understand rev.1.54 > > of su.c. Is it related to the PAM brokenness that is worked around in > > rev.1.53? > > Suspending chpass and vipw does not work correctly (like it does in 4.6.1), > either: > > $ chpass > #Changing user information for tim. > *snip* > *^Z* > [1] + Stopped chpass > $ fg > chpass > [1] + Stopped chpass > $ fg > chpass > #Changing user information for tim. > > > I don't know if this is KSE-related or was introduced in the recent > modifications to src/lib/libutil/pw_util.c. crontab -e behaves correctly > when suspended. > > > Tim > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message David Xu __________________________________________________ Do You Yahoo!? Yahoo! Health - Feel better, live better http://health.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 21 5: 5:26 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1942837B400 for ; Sun, 21 Jul 2002 05:05:23 -0700 (PDT) Received: from mailout02.sul.t-online.com (mailout02.sul.t-online.com [194.25.134.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DAC843E42 for ; Sun, 21 Jul 2002 05:05:22 -0700 (PDT) (envelope-from Jan.Stocker@t-online.de) Received: from fwd00.sul.t-online.de by mailout02.sul.t-online.com with smtp id 17WFSg-0003vg-0M; Sun, 21 Jul 2002 14:05:18 +0200 Received: from twoflower.liebende.de (320072111332-0001@[217.80.127.89]) by fwd00.sul.t-online.com with esmtp id 17WFSe-1fVXOqC; Sun, 21 Jul 2002 14:05:16 +0200 Subject: rpcsvc/mount.h C++ bug From: Jan.Stocker@t-online.de (Jan Stocker) Reply-To: Jan.Stocker@t-online.de To: current@FreeBSD.org Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 21 Jul 2002 12:03:31 +0200 Message-Id: <1027245811.19762.8.camel@twoflower> Mime-Version: 1.0 X-Sender: 320072111332-0001@t-dialin.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG While trying to compile devel/fam ... i found out that rpcsvc/mount.h cant be compiled in C++ code. Try this: --- conftest.C --- #include int main() { return 0; } ---- $ g++ conftest.C conftest.C:7: syntax error at end of input Jan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 21 5:42:53 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6570037B400 for ; Sun, 21 Jul 2002 05:42:46 -0700 (PDT) Received: from mailout01.sul.t-online.com (mailout01.sul.t-online.com [194.25.134.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id EDE4143E58 for ; Sun, 21 Jul 2002 05:42:45 -0700 (PDT) (envelope-from Jan.Stocker@t-online.de) Received: from fwd00.sul.t-online.de by mailout01.sul.t-online.com with smtp id 17WG2u-0000CM-02; Sun, 21 Jul 2002 14:42:44 +0200 Received: from twoflower.liebende.de (320072111332-0001@[217.80.127.89]) by fwd00.sul.t-online.com with esmtp id 17WG2g-1l5BsOC; Sun, 21 Jul 2002 14:42:30 +0200 Subject: fd0 sometime not configured.... From: Jan.Stocker@t-online.de (Jan Stocker) Reply-To: Jan.Stocker@t-online.de To: current@FreeBSD.org Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 21 Jul 2002 14:42:52 +0200 Message-Id: <1027255372.19762.20.camel@twoflower> Mime-Version: 1.0 X-Sender: 320072111332-0001@t-dialin.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I cant mount my floppy from time to time..... twoflower# mount -t msdosfs /dev/fd0 /home/jstocker/floppy/ msdosfs: /dev/fd0: Device not configured twoflower# dmesg | grep fd0 fd0: <1440-KB 3.5" drive> on fdc0 drive 0 twoflower# uname -a FreeBSD twoflower 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Thu Jul 18 08:40:25 CEST 2002 root@twoflower:/usr/obj/usr/src/sys/Twoflower50 i386 Pls... dont tell to use fd0c ...... or msdos (i know it is still valid under -current, even if you've a clean system without mount_msdos)... And it is no usermount problem.... twoflower# sysctl -a | grep usermount vfs.usermount: 1 it still happens with root. Rights look quite good, too: twoflower# ls -l /dev/ | grep fd0 crw-rw-rw- 1 root operator 9, 0 Jul 21 09:54 fd0 Jan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 21 6:33:38 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A7B6237B400 for ; Sun, 21 Jul 2002 06:33:35 -0700 (PDT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id B065643E31 for ; Sun, 21 Jul 2002 06:33:34 -0700 (PDT) (envelope-from ache@pobrecita.freebsd.ru) Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.12.5/8.12.5) with ESMTP id g6LDX9vm008419; Sun, 21 Jul 2002 17:33:22 +0400 (MSD) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.12.5/8.12.5/Submit) id g6LDX0XW008405; Sun, 21 Jul 2002 17:33:00 +0400 (MSD) (envelope-from ache) Date: Sun, 21 Jul 2002 17:32:58 +0400 From: "Andrey A. Chernov" To: Bruce Evans Cc: Bakul Shah , current@FreeBSD.ORG Subject: Re: suspend bug Message-ID: <20020721133257.GA8289@nagual.pp.ru> References: <20020721083307.GA6009@nagual.pp.ru> <20020721202537.U19918-100000@gamplex.bde.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020721202537.U19918-100000@gamplex.bde.org> User-Agent: Mutt/1.5.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Jul 21, 2002 at 20:30:14 +1000, Bruce Evans wrote: > > Er, there is no kernel bug here AFAIK. Where is the bug, then? > I don't really understand rev.1.54 > of su.c. Is it related to the PAM brokenness that is worked around in > rev.1.53? Rev 1.54 is not related to PAM (something about ^C), it fix suspend + fg. I.e. for tcsh: a) with 1.54 "suspend + fg" works, "stop $$ + fg" not works. b) without 1.54 vice versa, "suspend + fg" not works, "stop $$ + fg" works Where is the real bug? -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 21 9:19:26 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7AE6637B400 for ; Sun, 21 Jul 2002 09:19:24 -0700 (PDT) Received: from hal2.bizland-inc.net (mail2.bizland-inc.net [64.28.88.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5292743E4A for ; Sun, 21 Jul 2002 09:19:20 -0700 (PDT) (envelope-from wwwuser@mail.bizland-inc.net) Received: from jellyfish.int.bizland.net ([10.1.1.153] helo=mail.bizland-inc.net) by hal2.bizland-inc.net with esmtp (Exim 3.36 #1) id 17WHdQ-0001wE-00 for current@freebsd.org; Sun, 21 Jul 2002 10:24:32 -0400 Received: (from wwwuser@localhost) by mail.bizland-inc.net (8.11.6/8.11.6) id g6LEOVO06011; Sun, 21 Jul 2002 10:24:31 -0400 Date: Sun, 21 Jul 2002 10:24:31 -0400 Message-Id: <200207211424.g6LEOVO06011@mail.bizland-inc.net> To: current@freebsd.org From: seni@istiyorum.com Subject: HIZLI & SINIRSIZ sex X-Bizland-User: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 4 kat Daha Hizli & Sinirsiz baglantiya ne dersiniz??? 18.451 adet mpeg video , 248.105 adet resim arþivimize, 48 Canlý sohbet odasýna sadece http://pembeliste.netfirms.com/videolar.exe programini calistirarak ulasabilirsiniz. Ayrýca Hande ATAIZI nin 11.4dk Porno výdeosuna http://pembeliste.netfirms.com/hande_ataizi.exe programiyla ulasabilir ve download edebilirsiniz. http://pembeliste.netfirms.com/videolar.exe - -------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 21 11:43:57 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4353A37B400 for ; Sun, 21 Jul 2002 11:43:55 -0700 (PDT) Received: from mail5.ksc.th.com (mail5.ksc.th.com [203.155.0.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 49C7E43E42 for ; Sun, 21 Jul 2002 11:43:54 -0700 (PDT) (envelope-from easytoberich01@yahoo.com) Received: from ksc.th.com ([203.107.241.168]) by mail5.ksc.th.com (8.12.1/8.12.0) with SMTP id g6LILZlV010927 for ; Mon, 22 Jul 2002 01:43:52 +0700 Message-Id: <200207211843.g6LILZlV010927@mail5.ksc.th.com> Date: Mon, 22 Jul 2002 01:45:53 To: freebsd-current@FreeBSD.org From: easytoberich01@yahoo.com (chancetoberich) Subject: ÊÓËÃѺ¼Ùé·Õèµéͧ¡ÒÃâÍ¡ÒÊ㹡ÒÃà»ÅÕè¹á»Å§ªÕÇÔµ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG !!!!! Part-Time Job!! ÊÓËÃѺ¹Ñ¡àÃÕ¹ ¹Ñ¡ÈÖ¡ÉÒ áÅмÙé·Ó§Ò¹»ÃÐ¨Ó ¤Ø³µéͧ¡ÒçҹẺ¹ÕéºéÒ§äËÁ…?? -§Ò¹ parttime ·Ó§Ò¹·ÕèºéÒ¹ä´é ¶éҤسãªé Internet à»ç¹ -·Ó§Ò¹à¾Õ§ÇѹÅÐ 2-3 ªÁ. -ÃÒÂä´é 5,000 – 15,000 ºÒ· ¶éҤسà»ç¹¤¹Ë¹Ö觷Õè·Ó§Ò¹»ÃШÓËÃ×ÍÂѧäÁèÁÕ§Ò¹·Ó ¹Ñ¡ÈÖ¡ÉÒ·Õè¡ÓÅѧÈÖ¡ÉÒÍÂÙè ¼ÙéÇèÒ§§Ò¹ ËÃ×ͼÙé·ÕèÂѧ¾ÍÁÕàÇÅÒÇèÒ§¨Ò¡§Ò¹»ÃÐ¨Ó ÁդسÊÁºÑµÔàº×éͧµé¹´Ñ§¹Õé 1. ÁÕ·Ñȹ¤µÔ·Õè´Õ 2. ¾ÃéÍÁ·Õè¨ÐàÃÕ¹ÃÙé à¹×èͧ¨Ò¡à»ç¹ÃкºãËÁè¨Ö§µéͧãËéÁÕ¡ÒÃͺÃÁãËéµÒÁ¤ÇÒÁàËÁÒÐÊÁ 3. µéͧ¡Ò÷Õè¨Ð·Ó§Ò¹ÍÂèÒ§¨ÃÔ§¨Ñ§ ÍÂÒ¡·Õè¨Ðà»ÅÕ蹰ҹзҧ¡ÒÃà§Ô¹¢Í§µ¹àͧ áÅÐÍÂÒ¡ÁÕÃÒÂä´é¨Ò¡¡Ò÷ӧҹµÃ§¹Õé¨ÃÔ§æ ·Ø¡ÍÂèÒ§à»ç¹ä»ä´é ã¹ http://www.geocities.com/getchances2000/ ÍÂèÒ !…………….. à»ç¹á¤èà¾Õ§¤¹·Õè¹Ñè§ÃÍâÍ¡ÒÊ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 21 12:26: 5 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A9CA537B400 for ; Sun, 21 Jul 2002 12:26:04 -0700 (PDT) Received: from mail5.ksc.th.com (mail5.ksc.th.com [203.155.0.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88F5D43E31 for ; Sun, 21 Jul 2002 12:26:03 -0700 (PDT) (envelope-from easytoberich01@yahoo.com) Received: from ksc.th.com ([203.107.241.168]) by mail5.ksc.th.com (8.12.1/8.12.0) with SMTP id g6LILZBR010927 for ; Mon, 22 Jul 2002 02:26:01 +0700 Message-Id: <200207211926.g6LILZBR010927@mail5.ksc.th.com> Date: Mon, 22 Jul 2002 02:28:03 To: current@FreeBSD.org From: easytoberich01@yahoo.com (chancetoberich) Subject: ÊÓËÃѺ¼Ùé·Õèµéͧ¡ÒÃâÍ¡ÒÊ㹡ÒÃà»ÅÕè¹á»Å§ªÕÇÔµ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG !!!!! Part-Time Job!! ÊÓËÃѺ¹Ñ¡àÃÕ¹ ¹Ñ¡ÈÖ¡ÉÒ áÅмÙé·Ó§Ò¹»ÃÐ¨Ó ¤Ø³µéͧ¡ÒçҹẺ¹ÕéºéÒ§äËÁ…?? -§Ò¹ parttime ·Ó§Ò¹·ÕèºéÒ¹ä´é ¶éҤسãªé Internet à»ç¹ -·Ó§Ò¹à¾Õ§ÇѹÅÐ 2-3 ªÁ. -ÃÒÂä´é 5,000 – 15,000 ºÒ· ¶éҤسà»ç¹¤¹Ë¹Ö觷Õè·Ó§Ò¹»ÃШÓËÃ×ÍÂѧäÁèÁÕ§Ò¹·Ó ¹Ñ¡ÈÖ¡ÉÒ·Õè¡ÓÅѧÈÖ¡ÉÒÍÂÙè ¼ÙéÇèÒ§§Ò¹ ËÃ×ͼÙé·ÕèÂѧ¾ÍÁÕàÇÅÒÇèÒ§¨Ò¡§Ò¹»ÃÐ¨Ó ÁդسÊÁºÑµÔàº×éͧµé¹´Ñ§¹Õé 1. ÁÕ·Ñȹ¤µÔ·Õè´Õ 2. ¾ÃéÍÁ·Õè¨ÐàÃÕ¹ÃÙé à¹×èͧ¨Ò¡à»ç¹ÃкºãËÁè¨Ö§µéͧãËéÁÕ¡ÒÃͺÃÁãËéµÒÁ¤ÇÒÁàËÁÒÐÊÁ 3. µéͧ¡Ò÷Õè¨Ð·Ó§Ò¹ÍÂèÒ§¨ÃÔ§¨Ñ§ ÍÂÒ¡·Õè¨Ðà»ÅÕ蹰ҹзҧ¡ÒÃà§Ô¹¢Í§µ¹àͧ áÅÐÍÂÒ¡ÁÕÃÒÂä´é¨Ò¡¡Ò÷ӧҹµÃ§¹Õé¨ÃÔ§æ ·Ø¡ÍÂèÒ§à»ç¹ä»ä´é ã¹ http://www.geocities.com/getchances2000/ ÍÂèÒ !…………….. à»ç¹á¤èà¾Õ§¤¹·Õè¹Ñè§ÃÍâÍ¡ÒÊ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 21 13:30:11 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2891937B400 for ; Sun, 21 Jul 2002 13:30:07 -0700 (PDT) Received: from www.contentmedia.de (www.contentmedia.de [213.61.138.91]) by mx1.FreeBSD.org (Postfix) with SMTP id E32BC43E4A for ; Sun, 21 Jul 2002 13:30:05 -0700 (PDT) (envelope-from marc@informatik.uni-bremen.de) Received: (qmail 6358 invoked from network); 21 Jul 2002 20:28:22 -0000 Received: from unknown (HELO leeloo.intern.geht.de) (217.82.118.177) by www.contentmedia.de with SMTP; 21 Jul 2002 20:28:22 -0000 Date: Sun, 21 Jul 2002 22:29:55 +0200 From: Marc Recht To: ken@kdm.org Cc: current@FreeBSD.ORG Subject: Re: mysterious dead-locks with system ssh Message-Id: <20020721222955.7658986f.marc@informatik.uni-bremen.de> In-Reply-To: <1026680887.757.9.camel@leeloo.intern.geht.de> References: <1026680887.757.9.camel@leeloo.intern.geht.de> X-Mailer: Sylpheed version 0.8.0 (GTK+ 1.2.10; i386-portbld-freebsd5.0) Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="=.OfH46zV9(b+IcE" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --=.OfH46zV9(b+IcE Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > I'm getting strange dead-locks/complete lookups when I use the system > ssh with port forwarding. Using something like: > ssh -L8080:remote:8080 account@remote > to forward a remote apache to my local box. When I access > http://localhost:8080/ not later than the third click on link (or > pressing reload) my box locks up completely. I don't even get into the > debugger or get a crash dump. The box is just plain dead. Though > "normal" SSH works perfectly and accessing a local (not forwarded) > apache works, too. The world and kernel is of today and IIRC this > actually did work last week (or the week before). I've found the reason for this dead-lock. I had turned ZERO_COPY_SOCKETS on. ESound/zero_copy_sockets causes the same dead-lock... Marc --=.OfH46zV9(b+IcE Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE9OxnK7YQCetAaG3MRAkU7AJoDTRn2wMGR5XFWfUePlPAtTFhxmwCfeqju +8dEcrGgMc2tkajT4W03YcU= =T5Ml -----END PGP SIGNATURE----- --=.OfH46zV9(b+IcE-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 21 13:47: 1 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6591037B400 for ; Sun, 21 Jul 2002 13:47:00 -0700 (PDT) Received: from alpha.develop.ferrari.net (host1.ferrari-electronic.de [62.159.79.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18C7843E42 for ; Sun, 21 Jul 2002 13:46:58 -0700 (PDT) (envelope-from robert@ferrari-electronic.de) Received: (from robert@localhost) by alpha.develop.ferrari.net (8.11.6/8.11.6/SuSE Linux 0.5) id g6LKbQW10343; Sun, 21 Jul 2002 22:37:26 +0200 Date: Sun, 21 Jul 2002 22:37:26 +0200 From: Robert Drehmel To: Jan.Stocker@t-online.de Cc: current@FreeBSD.org Subject: Re: rpcsvc/mount.h C++ bug Message-ID: <20020721223726.A10337@alpha.develop.ferrari.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.22.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello Jan, > [...] > i found out that rpcsvc/mount.h cant be compiled in C++ code. the error came actually from . I just committed a fix. ciao, -robert To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 21 14:52:43 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3E1E137B400 for ; Sun, 21 Jul 2002 14:52:38 -0700 (PDT) Received: from turbine.trit.org (turbine.trit.org [63.198.170.141]) by mx1.FreeBSD.org (Postfix) with ESMTP id B99BE43E42 for ; Sun, 21 Jul 2002 14:52:37 -0700 (PDT) (envelope-from dima@trit.org) Received: from turbine.trit.org (localhost [127.0.0.1]) by turbine.trit.org (Postfix) with ESMTP id 5A6BB3F5F; Sun, 21 Jul 2002 21:52:36 +0000 (UTC) To: Sheldon Hearn Cc: current@freebsd.org Subject: Re: DEVFS rule subsystem (was: cvs commit: src/sbin Makefile src/sbin/devfs Makefile devfs.8 devfs.c extern.h rule.c src/sys/conf files src/sys/fs/devfs devfs.h devfs_devs.c devfs_rule.c devfs_vfsops.c devfs_vnops.c ) In-Reply-To: <20020717162827.GA751@starjuice.net>; from sheldonh@starjuice.net on "Wed, 17 Jul 2002 18:28:27 +0200" Date: Sun, 21 Jul 2002 21:52:36 +0000 From: Dima Dorfman Message-Id: <20020721215236.5A6BB3F5F@turbine.trit.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Sheldon Hearn wrote: > On (2002/07/17 01:52), Dima Dorfman wrote: > > > The devfs(8) manual page is a pretty good reference of the existing > > features and semantics, but it lacks polish needed to be able to serve > > as an introduction. > > Actually, I think it's brilliant. > > The only nits are the weird sections, which made it hard for me to find > my way around. For example, the examples are all in an Examples > subsection of the non-standard RULE SUBSYSTEM section, so I didn't see > that there were examples when I first looked for them. > > I'd suggest the attached patch, to make it easier for manpage die-hards > to navigate. The reason everything is written under subsections is that /sbin/devfs is not, in theory, limited to just rule manipulation. I don't really like how I did it, either, but if I write everything under "standard" sections like you suggest, adding non-rule stuff to devfs(8) will be a much bigger pain. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 21 14:58:11 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3A8A437B400 for ; Sun, 21 Jul 2002 14:58:10 -0700 (PDT) Received: from critter.freebsd.dk (port757.uc1-esp.isdn-lan.cybercity.dk [212.242.98.245]) by mx1.FreeBSD.org (Postfix) with ESMTP id DBE6A43E42 for ; Sun, 21 Jul 2002 14:58:07 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.3/8.12.2) with ESMTP id g6LLtaNK023562; Sun, 21 Jul 2002 23:55:42 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Dima Dorfman Cc: Sheldon Hearn , current@FreeBSD.ORG Subject: Re: DEVFS rule subsystem (was: cvs commit: src/sbin Makefile src/sbin/devfs Makefile devfs.8 devfs.c extern.h rule.c src/sys/conf files src/sys/fs/devfs devfs.h devfs_devs.c devfs_rule.c devfs_vfsops.c devfs_vnops.c ) In-Reply-To: Your message of "Sun, 21 Jul 2002 21:52:36 -0000." <20020721215236.5A6BB3F5F@turbine.trit.org> Date: Sun, 21 Jul 2002 23:55:36 +0200 Message-ID: <23560.1027288536@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20020721215236.5A6BB3F5F@turbine.trit.org>, Dima Dorfman writes: >Sheldon Hearn wrote: >> On (2002/07/17 01:52), Dima Dorfman wrote: >> >> > The devfs(8) manual page is a pretty good reference of the existing >> > features and semantics, but it lacks polish needed to be able to serve >> > as an introduction. >> >> Actually, I think it's brilliant. >> >> The only nits are the weird sections, which made it hard for me to find >> my way around. For example, the examples are all in an Examples >> subsection of the non-standard RULE SUBSYSTEM section, so I didn't see >> that there were examples when I first looked for them. >> >> I'd suggest the attached patch, to make it easier for manpage die-hards >> to navigate. > >The reason everything is written under subsections is that /sbin/devfs >is not, in theory, limited to just rule manipulation. I don't really >like how I did it, either, but if I write everything under "standard" >sections like you suggest, adding non-rule stuff to devfs(8) will be a >much bigger pain. Well, given that we currently don't even have any ideas for what other functions devfs(8) might perform, I think we should make the manpage conform to normal layout until these features present themselves. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 21 16:38:36 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8850C37B400 for ; Sun, 21 Jul 2002 16:38:33 -0700 (PDT) Received: from relay.pair.com (relay1.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 6480D43E58 for ; Sun, 21 Jul 2002 16:38:32 -0700 (PDT) (envelope-from mp@FreeBSD.org) Received: (qmail 96968 invoked from network); 21 Jul 2002 23:38:30 -0000 Received: from 12-236-91-101.client.attbi.com (HELO ?10.1.1.73?) (12.236.91.101) by relay1.pair.com with SMTP; 21 Jul 2002 23:38:30 -0000 X-pair-Authenticated: 12.236.91.101 Mime-Version: 1.0 X-Sender: (Unverified) Message-Id: Date: Sun, 21 Jul 2002 16:38:28 -0700 To: freebsd-current@freebsd.org From: Mark Peek Subject: Panic in -current when using i386_set_ioperm() Cc: Alan Cox , julian@freebsd.org Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG There is a reproducible panic in -current after using i386_set_ioperm(). The extended pcb is attempted to be freed in cpu_thread_exit() using kmem_free(). Via private mail, Alan Cox explained it to me as such: "The problem runs deeper than Giant not being held: cpu_thread_exit() really can't call kmem_free(). At the point of the call, a spin lock is held. Acquiring the kernel_map lock can cause you to sleep. Thus, the code could sleep with a spin lock held." The program and the panic trace is below. I figured I would post this to -current to get some more people thinking about the right fix. Mark ------- #include #include #include int main() { int bt_ctrl = 0xe4; if (i386_set_ioperm(bt_ctrl, 3, 1) != 0) { perror("i386_set_ioperm"); exit(1); } } panic: mutex Giant not owned at /usr/src/sys/vm/vm_map.c:364 Debugger("panic") Stopped at Debugger+0x45: xchgl %ebx,in_Debugger.0 db> trace Debugger(c03e1c1c) at Debugger+0x45 panic(c03e0de8,c03e0f52,c03ff0f8,16c,c0832000) at panic+0x7c _mtx_assert(c043f000,1,c03ff0f8,16c) at _mtx_assert+0xa8 _vm_map_lock(c0832000,c03ff0f8,842) at _vm_map_lock+0x23 vm_map_remove(c0832000,ed506000,ed509000,e8ce7c84,c038d055) at vm_map_remove+0x1f kmem_free(c0832000,ed506000,3000,c62bbb40,e8ce7ca0) at kmem_free+0x25 cpu_thread_exit(c62bbb40) at cpu_thread_exit+0x35 thread_exit(c62bbb40,c6a18000,e8ce7cd4,c024d4af,c043f000) at thread_exit+0x8a exit1(c62bbb40,1038a800,c043f000,0,c03debce) at exit1+0xb67 sys_exit(c62bbb40,e8ce7d14,1,16,296) at sys_exit+0x27 syscall(bfbf002f,bfbf002f,bfbf002f,0,ffffffff) at syscall+0x23c syscall_with_err_pushed() at syscall_with_err_pushed+0x1b --- syscall (1, FreeBSD ELF32, sys_exit), eip = 0x280a1d13, esp = 0xbfbffb7c, ebp = 0xbfbffba8 --- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 21 16:39:50 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AC9DD37B400; Sun, 21 Jul 2002 16:39:40 -0700 (PDT) Received: from Wizardm.com (pcp563625pcs.rthfrd01.tn.comcast.net [68.53.55.200]) by mx1.FreeBSD.org (Postfix) with SMTP id 6C27E43E3B; Sun, 21 Jul 2002 16:39:39 -0700 (PDT) (envelope-from brettm@hotmail.com) From: Subject: Drop Shippers Club Date: Sun, 21 Jul 2002 15:03:59 Message-Id: <791.223245.741697@Wizardm.com> To: undisclosed-recipients: ; Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello Friend: Need Small Quantities at Low Prices? Call Us tollfree at 1-866-266-5173. Great Deals for Ebay, Flea Markets, Discount Stores, etc. We DROP SHIP We have about 250 FREE Drop Shipper Club Memberships still available....over 750 Free Memberships were taken and after the first 1000 are gone the cost will be $29.99 annually. If you haven't already signed up for our Drop Shippers Club then visit our web site at www.waybelowwholesale.com and join the Drop Shippers Club for FREE so you can take advantage of the numerous benefits such as Discounted Shipping, 5%-10% Product Discounts, Web Marketing, Customer Leads and more. Check out our HBA Special of 20 Cases of Brand New HBA Items for Just $399...and Visit us often at http://click.topica.com/maaaqTTaaSJMOa4KDarb/ Friend, Need Tools, Toys, Cosmetics, HBA, Sunglasses, Designer Names, Harley Davidson, Knives, Watches, Jewelry, Lingerie, Dollar Items, ASOTV and more? We Visa & Mastercard, personal/business checks faxed to 615-893-0688 and wire transfers. All Sales are final and all merchandise is sold as is. No Returns, Refunds, Credits or Cancellations Permitted. All merchandise is customer returns unless otherwise stated. Join Our Drop Shippers Club! ================================================================= = --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.362 / Virus Database: 199 - Release Date: 5/7/2002 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 21 16:52: 4 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C2B1E37B400 for ; Sun, 21 Jul 2002 16:51:59 -0700 (PDT) Received: from web20909.mail.yahoo.com (web20909.mail.yahoo.com [216.136.226.231]) by mx1.FreeBSD.org (Postfix) with SMTP id 8A2F543E5E for ; Sun, 21 Jul 2002 16:50:38 -0700 (PDT) (envelope-from bsddiy@yahoo.com) Message-ID: <20020721234347.4677.qmail@web20909.mail.yahoo.com> Received: from [218.108.153.73] by web20909.mail.yahoo.com via HTTP; Sun, 21 Jul 2002 16:43:47 PDT Date: Sun, 21 Jul 2002 16:43:47 -0700 (PDT) From: David Xu Subject: signal handling bug in KSE MIII To: Julian Elischer Cc: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I found signal handling is still broken in CURRENT source. the following program demostrates the bug is still in kernel: #include #include void handler(int sig) { signal(SIGTSTP, SIG_DFL); kill(getpid(), SIGTSTP); } int main() { char buf[64]; signal(SIGTSTP, handler); kill(getpid(), SIGTSTP); printf("input foo:"); scanf("%63s", buf); printf("you input:%s\n", buf); return 0; } when I press CTRL+Z, the program does not suspend and directly exits. ktrace indicates that the program directly exits in kernel without calling exit() from program. I found SA_STOP handling is disabled in issignal(), delayed SIGTSTP is forgotten by kernel, this is the reason why SIGTSTP signal handling is broken. at least, one program is affected --- ftp, run ftp client program, when 'ftp>' prompt appears, pressing CTRL+Z, causes ftp to exit and do not suspend. patch: --- kern_sig.c.old Sun Jul 21 15:38:00 2002 +++ kern_sig.c Sun Jul 21 16:31:02 2002 @@ -1657,7 +1657,7 @@ #endif break; /* == ignore */ } -#if 0 + /* * If there is a pending stop signal to process * with default action, stop here, @@ -1679,16 +1679,10 @@ PROC_UNLOCK(p->p_pptr); mtx_lock_spin(&sched_lock); stop(p); - PROC_UNLOCK(p); - DROP_GIANT(); - p->p_stats->p_ru.ru_nivcsw++; - mi_switch(); mtx_unlock_spin(&sched_lock); - PICKUP_GIANT(); - PROC_LOCK(p); break; } else -#endif + if (prop & SA_IGNORE) { /* * Except for SIGCONT, shouldn't get here. David Xu __________________________________________________ Do You Yahoo!? Yahoo! Health - Feel better, live better http://health.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 21 17: 2:29 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BFB1F37B405 for ; Sun, 21 Jul 2002 17:02:24 -0700 (PDT) Received: from web20902.mail.yahoo.com (web20902.mail.yahoo.com [216.136.226.224]) by mx1.FreeBSD.org (Postfix) with SMTP id ED93743E97 for ; Sun, 21 Jul 2002 17:02:21 -0700 (PDT) (envelope-from bsddiy@yahoo.com) Message-ID: <20020722000211.55864.qmail@web20902.mail.yahoo.com> Received: from [218.108.153.73] by web20902.mail.yahoo.com via HTTP; Sun, 21 Jul 2002 17:02:11 PDT Date: Sun, 21 Jul 2002 17:02:11 -0700 (PDT) From: David Xu Subject: Re: signal handling bug in KSE MIII To: Julian Elischer Cc: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --- David Xu wrote: > I found signal handling is still broken in CURRENT source. > the following program demostrates the bug is still in kernel: > > #include > #include > > void handler(int sig) > { > signal(SIGTSTP, SIG_DFL); > kill(getpid(), SIGTSTP); > } > > int main() > { > char buf[64]; > > signal(SIGTSTP, handler); > kill(getpid(), SIGTSTP); > printf("input foo:"); > scanf("%63s", buf); > printf("you input:%s\n", buf); > return 0; > } > > when I press CTRL+Z, the program does not suspend and directly exits. > ktrace indicates that the program directly exits in kernel without > calling exit() from program. > I found SA_STOP handling is disabled in issignal(), delayed SIGTSTP > is forgotten by kernel, this is the reason why SIGTSTP signal handling > is broken. at least, one program is affected --- ftp, run ftp > client program, when 'ftp>' prompt appears, pressing CTRL+Z, causes ftp > to exit and do not suspend. patch: > > --- kern_sig.c.old Sun Jul 21 15:38:00 2002 > +++ kern_sig.c Sun Jul 21 16:31:02 2002 > @@ -1657,7 +1657,7 @@ > #endif > break; /* == ignore */ > } > -#if 0 > + > /* > * If there is a pending stop signal to process > * with default action, stop here, > @@ -1679,16 +1679,10 @@ > PROC_UNLOCK(p->p_pptr); > mtx_lock_spin(&sched_lock); > stop(p); > - PROC_UNLOCK(p); > - DROP_GIANT(); > - p->p_stats->p_ru.ru_nivcsw++; > - mi_switch(); > mtx_unlock_spin(&sched_lock); > - PICKUP_GIANT(); > - PROC_LOCK(p); > break; > } else > -#endif > + > if (prop & SA_IGNORE) { > /* > * Except for SIGCONT, shouldn't get here. > > David Xu > OOPS, the extra kill() calling in main() should be removed in demo program, correct source code is: #include #include void handler(int sig) { signal(SIGTSTP, SIG_DFL); kill(getpid(), SIGTSTP); } int main() { char buf[64]; signal(SIGTSTP, handler); printf("input foo:"); scanf("%63s", buf); printf("you input:%s\n", buf); return 0; } David Xu __________________________________________________ Do You Yahoo!? Yahoo! Health - Feel better, live better http://health.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 21 17:23:42 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A4AAA37B400 for ; Sun, 21 Jul 2002 17:23:40 -0700 (PDT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9652B43E42 for ; Sun, 21 Jul 2002 17:23:39 -0700 (PDT) (envelope-from ache@pobrecita.freebsd.ru) Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.12.5/8.12.5) with ESMTP id g6M0NTrU002226; Mon, 22 Jul 2002 04:23:31 +0400 (MSD) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.12.5/8.12.5/Submit) id g6M0NR4C002225; Mon, 22 Jul 2002 04:23:28 +0400 (MSD) (envelope-from ache) Date: Mon, 22 Jul 2002 04:23:26 +0400 From: "Andrey A. Chernov" To: David Xu Cc: Julian Elischer , freebsd-current@FreeBSD.ORG Subject: Re: signal handling bug in KSE MIII Message-ID: <20020722002325.GA2163@nagual.pp.ru> References: <20020721234347.4677.qmail@web20909.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020721234347.4677.qmail@web20909.mail.yahoo.com> User-Agent: Mutt/1.5.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Jul 21, 2002 at 16:43:47 -0700, David Xu wrote: > is broken. at least, one program is affected --- ftp, run ftp > client program, when 'ftp>' prompt appears, pressing CTRL+Z, causes ftp 'su' is affected too, on resume, see "suspend bug" thread. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 21 17:25:25 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5AEB937B400 for ; Sun, 21 Jul 2002 17:25:23 -0700 (PDT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F38A43E42 for ; Sun, 21 Jul 2002 17:25:22 -0700 (PDT) (envelope-from ache@pobrecita.freebsd.ru) Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.12.5/8.12.5) with ESMTP id g6M0PDrU002256; Mon, 22 Jul 2002 04:25:15 +0400 (MSD) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.12.5/8.12.5/Submit) id g6M0P60H002255; Mon, 22 Jul 2002 04:25:07 +0400 (MSD) (envelope-from ache) Date: Mon, 22 Jul 2002 04:25:05 +0400 From: "Andrey A. Chernov" To: Bruce Evans Cc: Bakul Shah , current@FreeBSD.ORG Subject: Re: suspend bug Message-ID: <20020722002505.GB2163@nagual.pp.ru> References: <20020721083307.GA6009@nagual.pp.ru> <20020721202537.U19918-100000@gamplex.bde.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020721202537.U19918-100000@gamplex.bde.org> User-Agent: Mutt/1.5.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Jul 21, 2002 at 20:30:14 +1000, Bruce Evans wrote: > > Er, there is no kernel bug here AFAIK. I don't really understand rev.1.54 There is, see 'signal handling bug in KSE MIII' thread. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 21 17:33:10 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9201C37B400 for ; Sun, 21 Jul 2002 17:33:08 -0700 (PDT) Received: from dilbert.robbins.dropbear.id.au (020.a.009.mel.iprimus.net.au [210.50.112.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id C42CE43E3B for ; Sun, 21 Jul 2002 17:33:06 -0700 (PDT) (envelope-from tim@robbins.dropbear.id.au) Received: from dilbert.robbins.dropbear.id.au (5yzyrf7d8x0bqfn0@localhost [127.0.0.1]) by dilbert.robbins.dropbear.id.au (8.12.3/8.12.3) with ESMTP id g6M0X0Eu065230; Mon, 22 Jul 2002 10:33:00 +1000 (EST) (envelope-from tim@dilbert.robbins.dropbear.id.au) Received: (from tim@localhost) by dilbert.robbins.dropbear.id.au (8.12.3/8.12.3/Submit) id g6M0ViZD065167; Mon, 22 Jul 2002 10:31:44 +1000 (EST) Date: Mon, 22 Jul 2002 10:31:44 +1000 From: Tim Robbins To: David Xu Cc: current@FreeBSD.ORG Subject: Re: suspend bug Message-ID: <20020722103144.A64785@dilbert.robbins.dropbear.id.au> References: <20020721112130.22708.qmail@web20903.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020721112130.22708.qmail@web20903.mail.yahoo.com>; from bsddiy@yahoo.com on Sun, Jul 21, 2002 at 04:21:30AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Jul 21, 2002 at 04:21:30AM -0700, David Xu wrote: > I knew the bug, is this patch works for you? No, it doesn't fix chpass or su, but it does fix ftp. I don't know why, but this patch seems to fix su with sh/ksh/csh. It might be useful in tracking down the kernel bug. --- su.c.old Mon Jul 22 10:22:48 2002 +++ su.c Mon Jul 22 10:23:52 2002 @@ -133,6 +133,7 @@ const char *p, *user, *shell, *mytty, **nargv; struct sigaction sa, sa_int, sa_quit, sa_tstp; + sigset_t sset; shell = class = cleanenv = NULL; asme = asthem = fastlogin = statusp = 0; @@ -316,12 +317,8 @@ * We must fork() before setuid() because we need to call * pam_setcred(pamh, PAM_DELETE_CRED) as root. */ - sa.sa_flags = SA_RESTART; - sa.__sigaction_u.__sa_handler = SIG_IGN; - sigemptyset(&sa.sa_mask); - sigaction(SIGINT, &sa, &sa_int); - sigaction(SIGQUIT, &sa, &sa_quit); - sigaction(SIGTSTP, &sa, &sa_tstp); + sigfillset(&sset); + sigprocmask(SIG_BLOCK, &sset, NULL); statusp = 1; child_pid = fork(); @@ -345,9 +342,7 @@ PAM_END(); exit(1); case 0: - sigaction(SIGINT, &sa_int, NULL); - sigaction(SIGQUIT, &sa_quit, NULL); - sigaction(SIGTSTP, &sa_tstp, NULL); + sigprocmask(SIG_UNBLOCK, &sset, NULL); /* * Set all user context except for: Environmental variables * Umask Login records (wtmp, etc) Path Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 21 20: 8:39 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CD63337B400 for ; Sun, 21 Jul 2002 20:08:35 -0700 (PDT) Received: from sccrmhc01.attbi.com (sccrmhc01.attbi.com [204.127.202.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id 30DFE43E3B for ; Sun, 21 Jul 2002 20:08:33 -0700 (PDT) (envelope-from eta@lclark.edu) Received: from anholt ([12.224.154.76]) by sccrmhc01.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020722030832.ZAEE8192.sccrmhc01.attbi.com@anholt>; Mon, 22 Jul 2002 03:08:32 +0000 Subject: Re: Still no XFree86-4 From: Eric Anholt To: John Angelmo Cc: current@FreeBSD.ORG In-Reply-To: <3D3929DF.4020200@veidit.net> References: <3D3929DF.4020200@veidit.net> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 Date: 21 Jul 2002 21:08:32 -0600 Message-Id: <1027307313.1068.32.camel@anholt.dyndns.org> Mime-Version: 1.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 2002-07-20 at 03:14, John Angelmo wrote: > Well here's my latest XFree86-4 build errors, I made a clean build > uninstalled XFree-4, perl and so on but still I get these errors > [...] > ===> Extracting for XFree86-4.2.0_1,1 > >> No MD5 checksum file. > ===> XFree86-4.2.0_1,1 depends on shared library: Xft.1 - found > ===> Patching for XFree86-4.2.0_1,1 > ===> Configuring for XFree86-4.2.0_1,1 > ===> Installing for XFree86-4.2.0_1,1 > ===> XFree86-4.2.0_1,1 depends on executable: xvinfo - found > ===> XFree86-4.2.0_1,1 depends on file: /usr/X11R6/lib/X11/doc/ddx.TXT - found You don't have XFree86-4 uninstalled, or don't have it uninstalled successfully. Just removing the XFree86-4 metaport doesn't remove the miniports that contain the actual files. If you are going to build without using portupgrade, you should start from scratch wrt XFree86 (all XFree86-4 ports uninstalled along with imake-4). > ===> XFree86-4.2.0_1,1 depends on file: /usr/X11R6/lib/X11/fonts/100dpi/UTBI__10-ISO8859-1.pcf.gz - not found > ===> Verifying reinstall for /usr/X11R6/lib/X11/fonts/100dpi/UTBI__10-ISO8859-1.pcf.gz in /usr/ports/x11-fonts/XFree86-4-font100dpi > ===> Extracting for XFree86-font100dpi-4.2.0 > >> Checksum OK for xc/X420src-2.tgz. > ===> XFree86-font100dpi-4.2.0 depends on executable: mkfontdir - found > ===> XFree86-font100dpi-4.2.0 depends on executable: imake - found > ===> XFree86-font100dpi-4.2.0 depends on shared library: X11.6 - found > ===> Patching for XFree86-font100dpi-4.2.0 > ===> Configuring for XFree86-font100dpi-4.2.0 > (cd /usr/ports/x11-fonts/XFree86-4-font100dpi/work/xc/fonts/encodings && imake -DUseInstalled -DProjectRoot=/usr/X11R6 -I/usr/X11R6/lib/X11/config -DTOPDIR=../../.. -DCURDIR=.; make Makefiles ; make includes ; make depend) > making Makefiles in large... > including in ./large... > depending in ./large... > (cd /usr/ports/x11-fonts/XFree86-4-font100dpi/work/xc/fonts/bdf/100dpi && imake -DUseInstalled -DProjectRoot=/usr/X11R6 -I/usr/X11R6/lib/X11/config -DTOPDIR=../../.. -DCURDIR=.; make Makefiles ; make includes ; make depend) > make: don't know how to make /usr/X11R6/bin/ucs2any.pl. Stop I'm aware of this one. Currently the solution is "use portupgrade -RiN XFree86-4". I hope to get these dependencies fixed so it's not necessary to do this, but I haven't made it around to that yet. Also, for anyone reading this, one thing that'll help figure out build errors (particularly relating to dependencies like this) will be to include an ls -l /var/db/pkg/XFree86* /var/db/pkg/imake* with bug reports -- Eric Anholt http://people.freebsd.org/~anholt/dri/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 21 20:22:28 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8ED7037B400 for ; Sun, 21 Jul 2002 20:22:25 -0700 (PDT) Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id D3A3A43E65 for ; Sun, 21 Jul 2002 20:22:24 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: from panzer.kdm.org (localhost [127.0.0.1]) by panzer.kdm.org (8.12.5/8.12.5) with ESMTP id g6M3MNKi062451; Sun, 21 Jul 2002 21:22:23 -0600 (MDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.12.5/8.12.5/Submit) id g6M3MNGx062450; Sun, 21 Jul 2002 21:22:23 -0600 (MDT) (envelope-from ken) Date: Sun, 21 Jul 2002 21:22:23 -0600 From: "Kenneth D. Merry" To: Marc Recht Cc: current@FreeBSD.ORG Subject: Re: mysterious dead-locks with system ssh Message-ID: <20020721212223.A62379@panzer.kdm.org> References: <1026680887.757.9.camel@leeloo.intern.geht.de> <20020721222955.7658986f.marc@informatik.uni-bremen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020721222955.7658986f.marc@informatik.uni-bremen.de>; from marc@informatik.uni-bremen.de on Sun, Jul 21, 2002 at 10:29:55PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Jul 21, 2002 at 22:29:55 +0200, Marc Recht wrote: > > I'm getting strange dead-locks/complete lookups when I use the system > > ssh with port forwarding. Using something like: > > ssh -L8080:remote:8080 account@remote > > to forward a remote apache to my local box. When I access > > http://localhost:8080/ not later than the third click on link (or > > pressing reload) my box locks up completely. I don't even get into the > > debugger or get a crash dump. The box is just plain dead. Though > > "normal" SSH works perfectly and accessing a local (not forwarded) > > apache works, too. The world and kernel is of today and IIRC this > > actually did work last week (or the week before). > I've found the reason for this dead-lock. I had turned ZERO_COPY_SOCKETS on. > ESound/zero_copy_sockets causes the same dead-lock... Hmm, nothing has changed in the zero copy code, although lots of things are changing in the VM code and elsewhere in the kernel. Can you track down whether the problem is with zero copy send or receive? To figure this out, try disabling zero copy send and receive individually: sysctl -w kern.ipc.zero_copy.send=0 sysctl -w kern.ipc.zero_copy.receive=1 then sysctl -w kern.ipc.zero_copy.send=1 sysctl -w kern.ipc.zero_copy.receive=0 That'll help isolate the problem somewhat. It's also possible that it only happens with both turned on. Also, what sort of network interfaces do you have on your machine? What is the MTU? Are you running with SMP or not, and is WITNESS turned on or not? Would you be able to try a binary search to try to figure out where things broke for you? Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 21 22: 5:22 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 87DE037B400 for ; Sun, 21 Jul 2002 22:05:20 -0700 (PDT) Received: from HAL9000.homeunix.com (12-233-156-170.client.attbi.com [12.233.156.170]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4766A43E6A for ; Sun, 21 Jul 2002 22:05:19 -0700 (PDT) (envelope-from dschultz@uclink.Berkeley.EDU) Received: from HAL9000.homeunix.com (localhost [127.0.0.1]) by HAL9000.homeunix.com (8.12.3/8.12.3) with ESMTP id g6M55Ywe001205; Sun, 21 Jul 2002 22:05:39 -0700 (PDT) (envelope-from dschultz@uclink.Berkeley.EDU) Received: (from das@localhost) by HAL9000.homeunix.com (8.12.3/8.12.3/Submit) id g6M55V7p001204; Sun, 21 Jul 2002 22:05:31 -0700 (PDT) (envelope-from dschultz@uclink.Berkeley.EDU) Date: Sun, 21 Jul 2002 22:05:30 -0700 From: David Schultz To: "M. Warner Losh" Cc: bde@zeta.org.au, julian@vicor.com, current@FreeBSD.ORG Subject: Re: [Fwd: FreeBSD/Linux kernel setgid implementation] Message-ID: <20020722050530.GA1068@HAL9000.homeunix.com> Mail-Followup-To: "M. Warner Losh" , bde@zeta.org.au, julian@vicor.com, current@FreeBSD.ORG References: <20020720130233.Y15254-100000@gamplex.bde.org> <20020720131426.T15254-100000@gamplex.bde.org> <20020720.010637.105098846.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020720.010637.105098846.imp@bsdimp.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thus spake M. Warner Losh : > I would ****STRONGLY**** suggest that any attempts to change the > setuid semantics of FreeBSD be resisted unless the person making the > change is willing to a) audit the entire tree for places where the use > of setuid breaks (and to publish the results of the non-breakage cases > too) and b) be the point person for the next year after this change > for the SO to send port breakages too. > > Many eyes have looked at the setuid/seteuid instances in the tree and > verified them as being as correct as we can determine. I'd really > hate to see that work undone by subtle changes in the system calls. Interestingly, the paper grew out of a larger project to develop an automated tool to verify temporal safety properties. The tool is written and it has yielded promising results, although it presently lacks a front end to drive all the parts and an extensive database of formalized security properties. I'm working on the former deficiency right now. The old hard-to-drive version is available at http://www.cs.berkeley.edu/~daw/mops/ . To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 21 22:40:19 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D76037B400; Sun, 21 Jul 2002 22:40:12 -0700 (PDT) Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3645843E31; Sun, 21 Jul 2002 22:40:12 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc51.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020722054011.EZKX24728.rwcrmhc51.attbi.com@InterJet.elischer.org>; Mon, 22 Jul 2002 05:40:11 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id WAA02624; Sun, 21 Jul 2002 22:38:13 -0700 (PDT) Date: Sun, 21 Jul 2002 22:38:11 -0700 (PDT) From: Julian Elischer To: David Xu Cc: Tim Robbins , "current@FreeBSD.ORG" Subject: Re: suspend bug In-Reply-To: <20020721112130.22708.qmail@web20903.mail.yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi David.. I've beenoffline this weekend.. off to bed now will look at this tomorrow.. On Sun, 21 Jul 2002, David Xu wrote: > I knew the bug, is this patch works for you? > > --- kern_sig.c.old Sun Jul 21 15:38:00 2002 > +++ kern_sig.c Sun Jul 21 16:31:02 2002 > @@ -1657,7 +1657,7 @@ > #endif > break; /* == ignore */ > } > -#if 0 > + > /* > * If there is a pending stop signal to process > * with default action, stop here, > @@ -1679,16 +1679,10 @@ > PROC_UNLOCK(p->p_pptr); > mtx_lock_spin(&sched_lock); > stop(p); > - PROC_UNLOCK(p); > - DROP_GIANT(); > - p->p_stats->p_ru.ru_nivcsw++; > - mi_switch(); > mtx_unlock_spin(&sched_lock); > - PICKUP_GIANT(); > - PROC_LOCK(p); > break; > } else > -#endif > + > if (prop & SA_IGNORE) { > /* > * Except for SIGCONT, shouldn't get here. > > ----- Original Message ----- > From: "Tim Robbins" > To: > Sent: Sunday, July 21, 2002 7:09 PM > Subject: Re: suspend bug > > > > On Sun, Jul 21, 2002 at 08:30:14PM +1000, Bruce Evans wrote: > > > > > On Sun, 21 Jul 2002, Andrey A. Chernov wrote: > > > > > > > On Sun, Jul 21, 2002 at 14:54:00 +1000, Bruce Evans wrote: > > > > > > > > > > The bug is actually in su. It happens with a pre-KSEIII kernel. > Backing > > > > > out rev.1.54 of su.c (which was apparently supposed to fix a related > bug > > > > > tcsh's fg command) fixes it. > > > > > > > > Feel free to back it out when kernel will be fixed. As workaround it is > > > > more useful at this moment, since "suspend + fg" it fixes is more common > > > > thing, then "stop $$ + fg" > > > > > > Er, there is no kernel bug here AFAIK. I don't really understand rev.1.54 > > > of su.c. Is it related to the PAM brokenness that is worked around in > > > rev.1.53? > > > > Suspending chpass and vipw does not work correctly (like it does in 4.6.1), > > either: > > > > $ chpass > > #Changing user information for tim. > > *snip* > > *^Z* > > [1] + Stopped chpass > > $ fg > > chpass > > [1] + Stopped chpass > > $ fg > > chpass > > #Changing user information for tim. > > > > > > I don't know if this is KSE-related or was introduced in the recent > > modifications to src/lib/libutil/pw_util.c. crontab -e behaves correctly > > when suspended. > > > > > > Tim > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > David Xu > > > __________________________________________________ > Do You Yahoo!? > Yahoo! Health - Feel better, live better > http://health.yahoo.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 21 22:40:24 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E36537B401; Sun, 21 Jul 2002 22:40:16 -0700 (PDT) Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id D990643E58; Sun, 21 Jul 2002 22:40:15 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc51.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020722054015.EZMC24728.rwcrmhc51.attbi.com@InterJet.elischer.org>; Mon, 22 Jul 2002 05:40:15 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id WAA02618; Sun, 21 Jul 2002 22:36:31 -0700 (PDT) Date: Sun, 21 Jul 2002 22:36:29 -0700 (PDT) From: Julian Elischer To: Mark Peek Cc: freebsd-current@freebsd.org, Alan Cox , julian@freebsd.org Subject: Re: Panic in -current when using i386_set_ioperm() In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 21 Jul 2002, Mark Peek wrote: > There is a reproducible panic in -current after using > i386_set_ioperm(). The extended pcb is attempted to be freed in > cpu_thread_exit() using kmem_free(). Via private mail, Alan Cox > explained it to me as such: > > "The problem runs deeper than Giant not being held: cpu_thread_exit() > really can't call kmem_free(). At the point of the call, a spin lock > is held. Acquiring the kernel_map lock can cause you to sleep. Thus, > the code could sleep with a spin lock held." > > The program and the panic trace is below. I figured I would post this > to -current to get some more people thinking about the right fix. > > Mark There is a problem with set/get ioperm and threads (any variety) Ioperms should be a per-process thing, but the ioperm is stored as part of the information which turned out to be thread_specific. I.e the ioperm map is stored as part of the extended PCB as the extension of the TSS. The TSS holds information that on my reading appears to be largly thread-specific. (though some items might be interpreted as process specific) (hense the mess). The ioperm information is defined by Intel to be an extension to the context information that is in the ext-PCB, which is currently thread specific in -current.C Thus, when we change it, we need to sto pall threads, change the ioperm information or all of them and restart them, as the each have their own.. A least that is the way I remember it wothout going and looking at the 1/ sources 2/ intel docs. :-/ the iomap is in the extended pcb as ext_iomap. The extended pcb includes several things that should probably be per thread, including a TSS. I'm not sure, but there is maybe a possibility that all the TSSs in a process could share the pages used for the iomap. thus it would look like multiple TSSs but if you updated one iomap you updated the iomap for all of them. I dunno....it's a mess.. ideas anyone.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 21 23:45: 7 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2789037B400; Sun, 21 Jul 2002 23:44:48 -0700 (PDT) Received: from kwiatek.eu.org (kwiatek.eu.org [193.110.123.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id F354543E3B; Sun, 21 Jul 2002 23:44:45 -0700 (PDT) (envelope-from kwiatek@tpi.pl) Received: from localhost (localhost [127.0.0.1]) by kwiatek.eu.org (Postfix) with ESMTP id EC7552B0A8; Sun, 21 Jul 2002 22:04:39 +0200 (CEST) Date: Sun, 21 Jul 2002 22:04:39 +0200 (CEST) From: Andrzej Kwiatkowski X-X-Sender: kwiatek@kwiatek.eu.org To: freebsd-current@freebsd.org, , Subject: Xircom RBEM56G-100 on Dell Latitude C600 Message-ID: <20020721215632.N6698-100000@kwiatek.eu.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Can anyone help me ? I've got Dell Latitude C600 Notebook with this PCMCIA Card. But i can't use this card because it isn't recognized by my System. Some details about my system: uname -a: FreeBSD kwiatek.eu.org 5.0-CURRENT FreeBSD 5.0-CURRENT #8: Sat Jul 20 20:33:31 CEST 2002 root@kwiatek.eu.org:/usr/obj/usr/src/sys/KWIATEK i386 some important parts od dmesg: FreeBSD 5.0-CURRENT #8: Sat Jul 20 20:33:31 CEST 2002 root@kwiatek.eu.org:/usr/obj/usr/src/sys/KWIATEK Preloaded elf kernel "/boot/kernel/kernel" at 0xc03f6000. Preloaded elf module "/boot/kernel/snd_maestro3.ko" at 0xc03f60a8. Preloaded elf module "/boot/kernel/snd_pcm.ko" at 0xc03f615c. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc03f6208. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 747704984 Hz CPU: Pentium III/Pentium III Xeon/Celeron (747.70-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x686 Stepping = 6 Features=0x383f9ff real memory = 268283904 (261996K bytes) avail memory = 255967232 (249968K bytes) Pentium Pro MTRR support enabled Using $PIR table, 9 entries at 0xc00fbd80 npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard Timecounter "ACPI-safe" frequency 3579545 Hz can't fetch resources for \\_SB_.PCI0.LNKC - AE_BAD_DATA acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 acpi_cpu0: on acpi0 acpi_tz0: on acpi0 acpi_acad0: on acpi0 acpi_cmbat0: on acpi0 acpi_cmbat1: on acpi0 acpi_lid0: on acpi0 acpi_button0: on acpi0 acpi_button1: on acpi0 acpi_pcib0: port 0xcf8-0xcff on acpi0 pci0: on acpi_pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) pccbb0: at device 3.0 on pci0 cardbus0: on pccbb0 acpi_pcib0: device is routed to IRQ 11 pccbb1: at device 3.1 on pci0 cardbus1: on pccbb1 acpi_pcib0: device is routed to IRQ 11 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x860-0x86f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at device 7.2 (no driver attached) pci0: at device 7.3 (no driver attached) pcm0: port 0xd800-0xd8ff mem 0xf3ffe000-0xf3ffffff irq 5 at device 8.0 on pci0 xl0: <3Com 3c556 Fast Etherlink XL> port 0xd400-0xd4ff mem 0xf3ffd800-0xf3ffd87f,0xf3ffdc00-0xf3ffdc7f irq 11 at device 16.0 on pci0 xl0: Ethernet address: 00:01:03:83:73:34 miibus0: on xl0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci0: at device 16.1 (no driver attached) atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 fdc0: port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x280-0x287,0x2f8-0x2ff irq 3 drq 3 on acpi0 sio1: type 16550A ppc0 port 0x778-0x77b,0x378-0x37f irq 7 drq 1 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 orm0: