Re: anyone seen these outside of alpha? or on non-SMP?
On Mon, Jun 04, 2001 at 09:37:36PM -0700, Matthew Jacob wrote: It's an easy fix except if it's your root fs- turn off softupdates. Yeah that's the solution -- just keep disabling features. How far do we go? Disable FFS, disable the VM system. Well, I might be left with enough to get a printf() to display something. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: anyone seen these outside of alpha? or on non-SMP?
On Mon, Jun 04, 2001 at 09:37:36PM -0700, Matthew Jacob wrote: It's an easy fix except if it's your root fs- turn off softupdates. Yeah that's the solution -- just keep disabling features. How far do we Oh, c'mon Dave, take a pill... It's only 'til Kirk gets back from rafting... go? Disable FFS, disable the VM system. Well, I might be left with enough to get a printf() to display something. Nope- no console device... What we'll be able to do is to blink the keyboard LEDs in morse code though F...Y ... D O To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
nss_ldap
Hello, I'm trying to get nss_ldap work. But it is looking for some includes, which I haven't (nss_common.h, nss_dbdefs.h). And I can not find any installation howto. There is some mention about FreeBSD in README, but nothing particular to this problem. Patches for nss_ldap on nectar.com are for older release. What do I really need to get it work? I have 5.0-20010531-CURRENT, nss_ldap-153, openldap-2.0.11 (20010524). pam_ldap is working correctly... Please help. Ladislav Kostal To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
FreeBSD/powerpc commit candidate for review
After considration of the last patchset I put up, I decided to get the stuff in a slightly cleaner condition before I committed. The results are now at: http://people.freebsd.org/~benno/commit/powerpc.diff There's still a lot of commented or #if 0'd out code, but I've cleaned up a lot of warnings, did a style pass of sorts and also managed to get VM initialising properly. =) You can see the current boot messages from my iMac at: http://jeamland.net/~benno/powerpc-boot.txt It hangs after the mountroot prompt. I'd like to commit this around the end of this week. Replies have been set to go to freebsd-ppc. -- Benno Rice [EMAIL PROTECTED] PGP signature
Re: panic in procfs code
On Tue, 05 Jun 2001 12:21:46 +0200, Daniel Rock [EMAIL PROTECTED] said: Daniel Hi, Daniel I just noticed: Doing a simple cat /proc/$$/map panics the system: (snip) Daniel _mtx_unlock_sleep(c049c9c0,0,c03b01a0,f2) at _mtx_unlock_sleep+0xa3 Daniel lockmgr(c55fadb0,10001,c049c9c0,c55f4100) at lockmgr+0x9d Daniel procfs_domap(c55f4100,c55f4320,c0c90da0,c6eefefc,c0cc3180) at Daniel procfs_domap+0x88 Lock and unlock of vm_mtx around vm_map_(un)lock_read() in procfs_domap() are missing. The attached patch should fix the bug. Index: fs/procfs/procfs_map.c === RCS file: /home/naklab/tanimura/rina2/CVS/FreeBSD/sys/fs/procfs/procfs_map.c,v retrieving revision 1.1.1.1.8.1 diff -u -r1.1.1.1.8.1 procfs_map.c --- fs/procfs/procfs_map.c 2001/05/27 02:39:08 1.1.1.1.8.1 +++ fs/procfs/procfs_map.c 2001/06/05 12:16:06 @@ -87,6 +87,8 @@ if (uio-uio_offset != 0) return (0); + mtx_lock(vm_mtx); + error = 0; if (map != curproc-p_vmspace-vm_map) vm_map_lock_read(map); @@ -169,12 +171,17 @@ error = EFBIG; break; } + mtx_unlock(vm_mtx); error = uiomove(mebuffer, len, uio); + mtx_lock(vm_mtx); if (error) break; } if (map != curproc-p_vmspace-vm_map) vm_map_unlock_read(map); + + mtx_unlock(vm_mtx); + return error; } -- Seigo Tanimura [EMAIL PROTECTED] [EMAIL PROTECTED]
nsrexecd in FreeBSD current
Gentlemen, I try to run (any) legato client on fBSD -current and so far had no success. All clients i tried (nwclient from ports, nwclient from release 3) exit on a siganl 11: luna /boot/kernel/kernel: pid 16940 (nsrexecd), uid 0: exited on signal 11 (core dumped) Strange enough even the original linux legato client with compat_linux crashes with the same error Any hint ? Thanks in advance, --Armin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
buildworld failed
for the past two weeks. Am I missing any HEADSUP's? Here's the error message: - === gnu/usr.bin/perl/x2p/a2pl Extracting config.h (with variable substitutions) Extracting cflags (with variable substitutions) Extracting writemain (with variable substitutions) Extracting myconfig (with variable substitutions) rm -f .depend mkdep -f .depend -a -I/usr/src/gnu/usr.bin/perl/x2p/a2pl/../../../../../contr ib/perl5/x2p -I/usr/local/obj/usr/src/gnu/usr.bin/perl/x2p/a2pl -I/usr/local/obj /usr/src/gnu/usr.bin/perl/x2p/a2pl/temp -I/usr/obj/usr/src/i386/usr/include /us r/src/gnu/usr.bin/perl/x2p/a2pl/../../../../../contrib/perl5/x2p/a2p.c /usr/src/ gnu/usr.bin/perl/x2p/a2pl/../../../../../contrib/perl5/x2p/hash.c /usr/src/gnu/u sr.bin/perl/x2p/a2pl/../../../../../contrib/perl5/x2p/str.c /usr/src/gnu/usr.bin /perl/x2p/a2pl/../../../../../contrib/perl5/x2p/util.c /usr/src/gnu/usr.bin/perl /x2p/a2pl/../../../../../contrib/perl5/x2p/walk.c cd /usr/src/gnu/usr.bin/perl/x2p/a2pl; make _EXTRADEPEND echo a2p: /usr/obj/usr/src/i386/usr/lib/libc.a .depend === gnu/usr.bin/perl/x2p/s2pl === gnu/usr.bin/perl/x2p/find2pl === gnu/usr.bin/perl/BSDPAN === gnu/usr.sbin 1 error *** Error code 2 1 error *** Error code 2 1 error To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: Problems booting recent -current
On 05-Jun-01 Tony Fleisher wrote: On Mon, 4 Jun 2001, John Baldwin wrote: On 03-Jun-01 Tony Fleisher wrote: I just tried to boot a -current kernel cvsupped at Sat Jun 2 14:11:35 PDT 2001, and was thrown the following error trying to boot to single-user (transcribed by hand): src/sys/kern/kern_sync.c:385 sleeping with eventhandler locked from src/sys/kern/subr_eventhandler:159 It would be helpful to know what eventhandler was being fired perhaps.. Any suggestions on how I may be able to determine this? Printf's perhaps. :) In the eventhandler code you might be able to output the hex address of the eventhandler list you are parsing. When it blows up, write down the address, then do a 'nm' on the kernel to find the symbol name associated with that address. That will let you know what eventlist was the problematic one. You can also print out the address of each handler as it is called and then look up those addresses in the kernel as well. sys/kern/subr_eventhandler.c is where you would want to do this. -- 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: nsrexecd in FreeBSD current
This is really a 'ports' issue... I don't know why this happens. It was suggested that it was probably a bug in nsrexecd- malloc maybe. Possibly. It doesn't always happen, as it's happily running right now on at least one i386 running -current (June 3) and one alpha (June 2)- but don't let the dates spoof you as these systems were fine a month ago as well. Since all nsrexecd does is open a socket range and start listening so that a remote server can connect and do NSR style authentication, and that nsrexecd has been reported to die right away if it dies at all, one can presume that each instance does just about the same thing. I don't know why it's actually dying- and I don't have a debug version of it built to really debug. I also consider -current to be more or less 'unsupported'- I sure as hell wouldn't commit any data worth backing up to a system running it. At the point in time that -current gets a bit more stable, I'll probably build a new version anyway (it's time- the current client version is pretty old by now). If it reproducibly starts dying for me, I'll probably debug it then. -matt Gentlemen, I try to run (any) legato client on fBSD -current and so far had no success. All clients i tried (nwclient from ports, nwclient from release 3) exit on a siganl 11: luna /boot/kernel/kernel: pid 16940 (nsrexecd), uid 0: exited on signal 11 (core dumped) Strange enough even the original linux legato client with compat_linux crashes with the same error Any hint ? Thanks in advance, --Armin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FreeBSD/powerpc commit candidate for review
On Tue, 5 Jun 2001, Benno Rice wrote: After considration of the last patchset I put up, I decided to get the stuff in a slightly cleaner condition before I committed. The results are now at: http://people.freebsd.org/~benno/commit/powerpc.diff There's still a lot of commented or #if 0'd out code, but I've cleaned up a lot of warnings, did a style pass of sorts and also managed to get VM initialising properly. =) You can see the current boot messages from my iMac at: http://jeamland.net/~benno/powerpc-boot.txt It hangs after the mountroot prompt. I'd like to commit this around the end of this week. Replies have been set to go to freebsd-ppc. Congratulations on the progress so far! You probably want to fix the $FreeBSD$ in md_var.h and maybe change/delete the alpha specific stuff there. Come to think about it, there are several cases where the $FreeBSD$ header still shows the location where the file was copied from. The cvs scripts should stop you from committing these files until that is fixed. I notice that reloc.h is just the copyright message. I guess you ought to use your own copyright here instead of John Birrell's. Come to think of it, the same thing could be said of alpha/include/reloc.h. Perhaps this header could be removed entirely if the contents of i386/include/reloc.h found a better home. Other than those minor comments, I think it looks ready to commit. -- Doug Rabson Mail: [EMAIL PROTECTED] Phone: +44 20 8348 6160 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: panic in procfs code
Date: Tue, 05 Jun 2001 21:39:59 +0900 From: Seigo Tanimura [EMAIL PROTECTED] Daniel Hi, Daniel I just noticed: Doing a simple cat /proc/$$/map panics the system: (snip) Daniel _mtx_unlock_sleep(c049c9c0,0,c03b01a0,f2) at _mtx_unlock_sleep+0xa3 Daniel lockmgr(c55fadb0,10001,c049c9c0,c55f4100) at lockmgr+0x9d Daniel procfs_domap(c55f4100,c55f4320,c0c90da0,c6eefefc,c0cc3180) at Daniel procfs_domap+0x88 Lock and unlock of vm_mtx around vm_map_(un)lock_read() in procfs_domap() are missing. The attached patch should fix the bug. I looked at the patch, and it seemed reasonable, so I applied it just before my daily build of -CURRENT, and: m133[1] cat /proc/$$/map 0x8048000 0x80f2000 165 0 0xce84bc60 r-x 6 3 0x0 COW NC vnode 0x80f2000 0x80f7000 5 0 0xce8c7f00 rw- 1 0 0x2180 COW NNC vnode 0x80f7000 0x814a000 28 0 0xce8e1ea0 rw- 1 0 0x2180 COW NNC default 0x814a000 0x815b000 17 0 0xce8c7c60 rwx 1 0 0x2180 COW NNC default 0x815b000 0x815d000 2 0 0xce8e1900 rwx 1 0 0x2180 COW NNC default 0x815d000 0x8191000 52 0 0xce8e1840 rwx 1 0 0x2180 NCOW NNC default 0x280f2000 0x280f3000 1 0 0xce8e1360 rwx 1 0 0x2180 COW NNC default 0xbfbe 0xbfc0 14 0 0xce8c7c00 rwx 1 0 0x2180 COW NNC default m133[2] uname -a FreeBSD m133.whistle.com 5.0-CURRENT FreeBSD 5.0-CURRENT #23: Tue Jun 5 08:57:03 PDT 2001 [EMAIL PROTECTED]:/common/C/obj/usr/src/sys/LAPTOP_30W i386 m133[3] so it looks good to me, david -- David H. Wolfskill [EMAIL PROTECTED] As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Reproduceable data corruption using bzip2 + current libc (cvsup'ed on Friday)
Hi, I don't know what's going on, but on my -CURRENT system bzip2 produces corrupt archives when I'm trying to compress big tar archive of compiled XFree86. First my guess was that it is a hardware problem, but the problem disappears when I'm using libc.so.4 and bzip2 copied from my 4-STABLE box. I'll try to recompile world and see if it helps, but the problem looks really *weird*. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: anyone seen these outside of alpha? or on non-SMP?
] Data modified on freelist: word 2 of object 0xfe000190b780 size 72 ] previous type inodedep (0xd6adc0de != 0xdeadc0de) ] ... ] Data modified on freelist: word 2 of object 0xfe0001806700 size 72 ] previous type pagedep (0xd6adc0de != 0xdeadc0de) ] ] ] Anyone seen these on non-SMP? On i386? Yes. I have seen this on 4.3, after opening more than 32,767 network connections, only in my case the problem occurred in the close, after the credential structure reference count overflowed. There will probably be significantly more of these problems in -current, since much of the recent locking work has been a bit less than comprehensive, so there are probably free races in a lot of places that used to be implicitly protected via past serialization through the BGL. There are exactly 12 structures 72 bytes long in the FreeBSD kernel: struct rusage= 72 struct nameidata= 72 struct ifpppstatsreq = 72 struct ifpppcstatsreq = 72 struct sadb_comb = 72 struct ddpcb = 72 struct atmsetreq = 72 struct linkinfo = 72 struct ng_one2many_config = 72 struct ng_ppp_mp_state = 72 struct ipfw_dyn_rule = 72 struct secasvar = 72 Despite the obvious involvement os the soft updates code (there is a reference counted object reference underflow, which resulted in the data being in use after nominally being freed), my money is on the struct rusage on a process exit. This implies a race condition in the sync'ing of data for files being resource-tracking closed as a result of the process exit triggering a dependency failure. My guess would be that the inode in question is a directory inode, and that there are temp files there, or a lot of open files, but that is just a ballpark guess. -- My first suggestion would be to turn the printf() as a result of INVARIANTS (which is where the message is coming from, in the kern_malloc.c code) into a true panic, since what you are seeing isundoubtedly a cascade failure. This will (if you have the debugger enabled) let you examine the object that is being spam'med before it gets stepped on into illegibility. Knowing the size will let you catch the allocation. -- Note that in the message referenced by David, the errors were on different objects; I'll guess at decoding them, as well: May 27 18:52:06 xor /boot/kernel/kernel: Data modified on freelist: word 2 of object 0xc1a60100 size 64 previous type pagedep (0xd6adc0de != 0xdeadc0de) May 27 18:52:06 xor /boot/kernel/kernel: Data modified on freelist: word 2 of object 0xc16f02c0 size 64 previous type pagedep (0xd6adc0de != 0xdeadc0de) May 27 18:52:06 xor /boot/kernel/kernel: Data modified on freelist: word 2 of object 0xc1a60480 size 52 previous type pagedep (0xd6adc0de != 0xdeadc0de) ...these are 64 and 52 bytes each -- different structures. Here are the probables: struct iodone_chain= 52 struct lockf= 52 struct protosw= 52 struct attr_calling = 52 struct ng_bpf_hookprog = 52 struct mrtstat = 52 struct ipprotosw = 52 struct udpstat = 52 struct ip6protosw = 52 struct ostat= 64 struct ifaliasreq = 64 struct at_aliasreq = 64 struct attr_traffic = 64 struct atm_sock_stat = 64 struct ng_type = 64 struct ng_pptpgre_stats = 64 struct in_aliasreq = 64 struct in6_prefixreq = 64 struct ip6_pktopts = 64 ...my ballpark bets, again, would be: struct lockf= 52 struct ostat= 64 Terry Lambert [EMAIL PROTECTED] --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
f77's (and cc's?) profiling
Hi, Can someone give me a hint why f77's profiling doesn't pick up any time data? Is this easy to fix? TIA -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: nss_ldap
Howdy, The FreeBSD support for nss_ldap is only via the BIND IRS interface. See the README.IRS file supplied with nss_ldap on how to get this working on FreeBSD. To actually utilise the nsswitch features, you'll need to get the -current patches on nectar.com and get them compiling and working on -current. Then use the nss_ldap version on nectar.com along with the patches. Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Ladislav Kostal Sent: Tuesday, 5 June 2001 20:57 To: [EMAIL PROTECTED] Subject: nss_ldap Hello, I'm trying to get nss_ldap work. But it is looking for some includes, which I haven't (nss_common.h, nss_dbdefs.h). And I can not find any installation howto. There is some mention about FreeBSD in README, but nothing particular to this problem. Patches for nss_ldap on nectar.com are for older release. What do I really need to get it work? I have 5.0-20010531-CURRENT, nss_ldap-153, openldap-2.0.11 (20010524). pam_ldap is working correctly... Please help. Ladislav Kostal 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: usr.sbin/pim6[sd]d will be removed soon.
Here's a quick question that just popped into my mind. I cvsup my -stable and my
-current box every night and every once in a while I install a new world.
What happens with a (previously installed) /usr/sbin/pim6[sd]d ? Will 'make
(install)world' remove it ?
If not, what system is in place (if any) to accomplish this in order to get a really
clean system ?
Mm.. I feel VERY newbie-like by asking this, because I use FBSD over 3 years now, but
I hope someone will help me out with an answer on this.
With regards,
Stephan van Beerschoten
On Sun, 03 Jun 2001, Hajimu UMEMOTO wrote:
Hi,
I heared from itojun that usr.sbin/pim6[sd]d has non-BSD license and
does not allow fee-based redistribution. So, I will remove them from
the tree soon. NetBSD was already done.
Could someone please make them ports? ftp.kame.net:~ftp/pub/kame/misc
has pim6[sd]-*.tar.gz.
--
Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan
[EMAIL PROTECTED] [EMAIL PROTECTED] ume@{,jp.}FreeBSD.org
http://www.imasy.org/~ume/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
--
Stephan van Beerschoten [SVB21-RIPE] [EMAIL PROTECTED]
PGP fingerprint: 4557 9761 B212 FB4C 778D 3529 C42A 2D27
To err is human, to forgive is Not Company Policy
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
