Re: Trouble Building CURRENT on STABLE, cpp seg. fault
On 2002-09-24 18:00, Lars Eggert [EMAIL PROTECTED] wrote: Alexander Kabaev wrote: On Tue, 24 Sep 2002 00:00:45 -0700 Crist J. Clark [EMAIL PROTECTED] wrote: Not too sure about that. Now I'm getting SIGSEGV again, You are right. There was a stupid mistake in the latest version, sorry. Could you try yet another patch? http://people.freebsd.org/~kan/gcc-cpp.diff FYI, I saw the same error as Crist when building -current under 4.6, and with your patch, the buildworld/buildkernel succeeded. Ditto. I have managed to build a current world on RELENG_4 only with Alexander's patch. -- FreeBSD: The power to Serve -- http://www.FreeBSD.org FreeBSD 5.0-CURRENT #0: Tue Sep 24 04:56:12 EEST 2002 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: i386 tinderbox failure
The next one will pass. On Tue, 24 Sep 2002, Dag-Erling Smorgrav wrote: -- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree -- stage 2: rebuilding the object tree -- stage 2: build tools -- stage 3: cross tools -- stage 4: populating /home/des/tinderbox/i386/obj/local0/scratch/des/src/i386/usr/include -- stage 4: building libraries -- stage 4: make dependencies -- stage 4: building everything.. -- Kernel build for GENERIC started on Tue Sep 24 22:18:51 PDT 2002 -- === xe cc1: warnings being treated as errors /local0/scratch/des/src/sys/kern/vfs_mount.c: In function `checkdirs': /local0/scratch/des/src/sys/kern/vfs_mount.c:1141: warning: implicit declaration of function `vrefcnt' *** Error code 1 Stop in /local0/scratch/des/obj/local0/scratch/des/src/sys/GENERIC. *** Error code 1 Stop in /local0/scratch/des/src. *** Error code 1 Stop in /local0/scratch/des/src. 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
Kernel panic
My latest panic.. Sep 25 11:39:48 leeloo kernel: ../../../vm/uma_core.c:1307: could sleep with pcm0:play:1 locked from ../../../dev/sound/pcm/dsp.c:696 Sep 25 11:39:48 leeloo kernel: ../../../vm/uma_core.c:1307: could sleep with pcm0:play:1 locked from ../../../dev/sound/pcm/dsp.c:696 Sep 25 11:39:48 leeloo kernel: ../../../vm/uma_core.c:1307: could sleep with pcm0:play:1 locked from ../../../dev/sound/pcm/dsp.c:748 Sep 25 11:39:48 leeloo kernel: ../../../vm/uma_core.c:1307: could sleep with pcm0:play:1 locked from ../../../dev/sound/pcm/dsp.c:748 Sep 25 11:39:48 leeloo kernel: ../../../vm/uma_core.c:1307: could sleep with pcm0:play:1 locked from ../../../dev/sound/pcm/dsp.c:673 Sep 25 11:49:40 leeloo kernel: acquiring duplicate lock of same type: inp Sep 25 11:49:40 leeloo kernel: 1st inp ../../../netinet/udp_usrreq.c:288 Sep 25 11:49:40 leeloo kernel: 2nd inp ../../../netinet/udp_usrreq.c:288 Sep 25 12:05:19 leeloo syslogd: kernel boot file is /boot/kernel/kernel Sep 25 12:05:19 leeloo kernel: Sep 25 12:05:19 leeloo kernel: Sep 25 12:05:19 leeloo kernel: Fatal trap 12: page fault while in kernel mode Sep 25 12:05:19 leeloo kernel: fault virtual address = 0x4 Sep 25 12:05:19 leeloo kernel: fault code= supervisor read, page not present Sep 25 12:05:19 leeloo kernel: instruction pointer = 0x8:0xc020acd2 Sep 25 12:05:19 leeloo kernel: stack pointer = 0x10:0xe8c64678 Sep 25 12:05:19 leeloo kernel: frame pointer = 0x10:0xe8c6467c Sep 25 12:05:19 leeloo kernel: code segment = base 0x0, limit 0xf, type 0x1b Sep 25 12:05:19 leeloo kernel: = DPL 0, pres 1, def32 1, gran 1 Sep 25 12:05:19 leeloo kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Sep 25 12:05:19 leeloo kernel: current process = 39662 (vim) Sep 25 12:05:19 leeloo kernel: trap number = 12 Sep 25 12:05:19 leeloo kernel: panic: page fault Sep 25 12:05:19 leeloo kernel: Sep 25 12:05:19 leeloo kernel: syncing disks... panic: bremfree: bp 0xd381a080 not locked Sep 25 12:05:19 leeloo kernel: Uptime: 2h22m51s Sep 25 12:05:19 leeloo kernel: pfs_vncache_unload(): 1 entries remaining Sep 25 12:05:19 leeloo kernel: Dumping 1535 MB Sep 25 12:05:19 leeloo kernel: ata0: resetting devicesannel.c:6Copyright (c) 1992-2002 The FreeBSD Project. leeloo# nm kernel.debug | grep c020ac c020ac70 T __setugid c020ac80 T groupmember c020acc0 T suser_cred Please let me know if I could do something to provide more details. I've a kernel.debug file around. BTW, a coredump wasn't written to the disk though there's enough space available. Is there problem with that in current -current? Marc msg43373/pgp0.pgp Description: PGP signature
Re: cvs commit: src/sys/sys lockmgr.h
I tried booting a kernel with lock checking enabled and got the
following panic:
panic: mutex vnode interlock owned at vnode_if.h:24
panic()
_mtx_assert()
VOP_ISLOCKED()
vop_unlock_pre()
vput()
kern_mkdir()+0x9e - the first call to vput() to handle the found case?
start_init()
fork_exit()
fork_trampoline()
I believe there is a logic error in the VOP_UNLOCK() assertion logic.
In vput(), there is the following code:
VI_LOCK(vp);
/* Skip this v_writecount check if we're going to panic below. */
KASSERT(vp-v_writecount vp-v_usecount || vp-v_usecount 1,
(vput: missed vn_close));
if (vp-v_usecount 1) {
vp-v_usecount--;
VOP_UNLOCK(vp, LK_INTERLOCK, td);
return;
}
which looks reasonable. VOP_UNLOCK() starts off with the following
code:
struct vop_unlock_args a;
int rc;
a.a_desc = VDESC(vop_unlock);
a.a_vp = vp;
a.a_flags = flags;
a.a_td = td;
#ifdef DEBUG_VFS_LOCKS
vop_unlock_pre(a);
#endif
Then vop_unlock_pre() contains the following code:
if (a-a_flags LK_INTERLOCK)
ASSERT_VI_LOCKED(a-a_vp);
ASSERT_VOP_LOCKED(a-a_vp, VOP_UNLOCK);
Since the LK_INTERLOCK flag is passed to VOP_UNLOCK() and
vop_unlock_pre(), we test the VI_LOCKED assertion. We get into
trouble with ASSERT_VOP_LOCKED, though, because ASSERT_VOP_LOCKED()
calls VOP_ISLOCKED(), which contains the code:
a.a_desc = VDESC(vop_islocked);
a.a_vp = vp;
a.a_td = td;
ASSERT_VI_UNLOCKED(vp);
We'll definitely blow up here because we're making the exact opposite
assertion.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
alpha tinderbox failure
-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree -- stage 2: rebuilding the object tree -- stage 2: build tools -- stage 3: cross tools -- stage 4: populating /home/des/tinderbox/alpha/obj/h/des/src/alpha/usr/include -- stage 4: building libraries -- stage 4: make dependencies -- stage 4: building everything.. -- Kernel build for GENERIC started on Wed Sep 25 03:16:07 PDT 2002 -- Kernel build for GENERIC completed on Wed Sep 25 03:42:24 PDT 2002 -- Kernel build for LINT started on Wed Sep 25 03:42:24 PDT 2002 -- === vinum cc1: warnings being treated as errors /h/des/src/sys/coda/coda_venus.c: In function `venus_ioctl': /h/des/src/sys/coda/coda_venus.c:277: warning: cast from pointer to integer of different size /h/des/src/sys/coda/coda_venus.c:292: warning: cast from pointer to integer of different size /h/des/src/sys/coda/coda_venus.c: In function `venus_readlink': /h/des/src/sys/coda/coda_venus.c:380: warning: cast from pointer to integer of different size /h/des/src/sys/coda/coda_venus.c: In function `venus_readdir': /h/des/src/sys/coda/coda_venus.c:637: warning: cast from pointer to integer of different size *** Error code 1 Stop in /h/des/obj/h/des/src/sys/LINT. *** Error code 1 Stop in /h/des/src. *** Error code 1 Stop in /h/des/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
When will be released the Developer Preview #2 ?
-- JFRH. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
panic in latest build
I just build latest -CURRENT on my laptop. The error is: panic: vrele: negative ref cnt Debugger(panic) Stopped at Debugger+0x54: xchgl %ebx,in_Debugger.0 I did the following: After bootup - logged in as root. touch'ed /var/log/xferlog and hit ctrl-d, to logout. (That is when the panic occured) After rebooting, and login - and out again, the panic persists. Any ideas ? /mich -- Best Regards, Michael Landin Hostbaek FreeBSDCluster.org - an International Community */ PGP-key available upon request /* To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: panic in latest build
Michael Hostbaek wrote: I just build latest -CURRENT on my laptop. The error is: panic: vrele: negative ref cnt Debugger(panic) Stopped atDebugger+0x54: xchgl %ebx,in_Debugger.0 I did the following: After bootup - logged in as root. touch'ed /var/log/xferlog and hit ctrl-d, to logout. (That is when the panic occured) I got a similar panic just following Jeff's rather complicated vfs kernel patches last night. I decided to wait and try again in a day or so to let the experts hash it out ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Journaled filesystem in CURRENT
Does CURRENT support journaled filesystem ? P.S. please, CC me, i'm not subscribed To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Who broke sort(1) ?
Funny, this argument suddenly reminds me of the Hitch Hikers Guide to the Galexy :-) Bob On Tue, Sep 24, 2002 at 05:01:29PM -0400, Garrett Wollman wrote: On Tue, 24 Sep 2002 13:30:11 -0700, Peter Wemm [EMAIL PROTECTED] said: Oh man, this is going to suck. There are thousands and thousands of third party scripts that use +n syntax. I am most unhappy with this change. :-( The time to complain about it was back in 1992when the old syntax was labeled ``deprecated'' by P1003.2, or in 1999 when the revision cycle was just heating up. Old deprecated features were automatically dropped leading up to the 2001 revision, unless someone could make a case for their retention. That case wasn't made in the case of `sort', and as a result the Standard no longer permits the old syntax. It's not like people didn't have nine years' advance warning to fix their scripts. FreeBSD supported `-k' in 1.0; see http://www.freebsd.org/cgi/cvsweb.cgi/src/gnu/usr.bin/sort/Attic/sort.c?rev=1.1content-type=text/x-cvsweb-markup. -GAWollman To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- Bob WillcoxWe seem to have forgotten the simple truth that [EMAIL PROTECTED] reason is never perfect. Only non-sense attains Austin, TX perfection. -- Poul Henningsen [1894-1967] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Panic in VFS subsystem with very recent CURRENT
VAIO Z600TEK, PIII/700, 20 GB, 256 MB. cvsup from three hours ago, whicle rebooting I get this: panic: vrele: missed vn_close Debugger(panic) Stopped at Debugger+0x45:xchgl%ebx,in_Debugger.0 db trace Debugger at Debugger+0x45 panic at panic+0x9f vrele at vrele+0x13b vn_close at vn_close+0x58 vn_closefile at vn_closefile+0x1e fdrop_locked at frop_locked+0x12e fdrop at fdrop+0x24 closef at closef+0x9f fdfree at fdfree+0x83 exit1 at exit1+0x2c2 sys_exit atsys_exit+0x27 syscall at syscall+0x235 Xint0x80_syscall Any idea? I should have a dump shortly if anyone's interested. -- Ollivier ROBERT -=- Eurocontrol EEC/ITM -=- [EMAIL PROTECTED] FreeBSD caerdonn.eurocontrol.fr 5.0-CURRENT #46: Wed Jan 3 15:52:00 CET 2001 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Who broke sort(1) ?
In message [EMAIL PROTECTED], Bob Willcox writes: Funny, this argument suddenly reminds me of the Hitch Hikers Guide to the Galexy :-) I've gone of the idea of progress, it's over rated. :-) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | 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 [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Panic in VFS subsystem with very recent CURRENT
On Wed, 25 Sep 2002, Ollivier Robert wrote: VAIO Z600TEK, PIII/700, 20 GB, 256 MB. cvsup from three hours ago, whicle rebooting I get this: panic: vrele: missed vn_close Debugger(panic) Stopped at Debugger+0x45:xchgl%ebx,in_Debugger.0 db trace Debugger at Debugger+0x45 panic at panic+0x9f vrele at vrele+0x13b vn_close at vn_close+0x58 vn_closefile at vn_closefile+0x1e fdrop_locked at frop_locked+0x12e fdrop at fdrop+0x24 closef at closef+0x9f fdfree at fdfree+0x83 exit1 at exit1+0x2c2 sys_exit atsys_exit+0x27 syscall at syscall+0x235 Xint0x80_syscall Any idea? I should have a dump shortly if anyone's interested. A dump would be good. Some more information on your configuration too please. What filesystems were mounted? You said you were rebooting? Had you done anything significant with the box? Thanks, Jeff To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: panic in latest build
On Wed, 25 Sep 2002, walt wrote: Michael Hostbaek wrote: I just build latest -CURRENT on my laptop. The error is: panic: vrele: negative ref cnt Debugger(panic) Stopped at Debugger+0x54: xchgl %ebx,in_Debugger.0 I did the following: After bootup - logged in as root. touch'ed /var/log/xferlog and hit ctrl-d, to logout. (That is when the panic occured) I got a similar panic just following Jeff's rather complicated vfs kernel patches last night. I decided to wait and try again in a day or so to let the experts hash it out ;-) I'll look at it a bit later today. Can you give me some more info? What filesystems did you have mounted? Any kernel options that are not in GENERIC? Thanks, Jeff To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Journaled filesystem in CURRENT
On Wed, Sep 25, 2002 at 04:19:34PM +0300, Anton Yudin wrote: Does CURRENT support journaled filesystem ? There are not journaling file systems in current at this time. Efforts to port both xfs and jfs are underway. -- Brooks -- Any statement of the form X is the one, true Y is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 msg43385/pgp0.pgp Description: PGP signature
Re: Trouble Building CURRENT on STABLE, cpp seg. fault
On Tue, Sep 24, 2002 at 06:13:33PM -0400, Alexander Kabaev wrote: Nope, still getting it. I was able to reproduce the crash with your config file and unpatched GCC, however crash does not happen when I use the patch. Are you using make buildkernel or old config/make method? Since I'm building a CURRENT kernel on a STABLE box, I think buildkernel is the only practical choice. With the latest patch, today's automated build ran fine. Thanks. -- Crist J. Clark | [EMAIL PROTECTED] | [EMAIL PROTECTED] http://people.freebsd.org/~cjc/| [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Journaled filesystem in CURRENT
If I may add a comment here... You already *have* a kind of journaled filesystem for some time now. Please read Soft Updates vs. Journalling Filesystems from M.K. McKusick (www.mckusick.com). I'm really sad if see the efforts done especially for porting JFS to FreeBSD, which has already under Linux a more than poor performance. The only reason for porting JFS is IMHO to be able to mount JFS Volumes under FreeBSD - if that's worth the effort... Why begging for 'Journaling' if you have 'Journaling next generation'? -- Ciao/BSD - Matthias Matthias Schuendehuette msch [at] snafu.de, Berlin (Germany) Powered by FreeBSD 4.7-RC To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Panic in VFS subsystem with very recent CURRENT
On Wed, 25 Sep 2002, David Wolfskill wrote: panic: vrele: missed vn_close cpuid = 0; lapic.id = Debugger(panic) Stopped at Debugger+0x55: xchgl %ebx,in_Debugger.0 db tr Debugger(c036903a,0,c0372831,d7b9cb70,1) at Debugger+0x55 panic(c0372831,0,c03724c2,810,c4439200) at panic+0x11f vrele(c44545c8,c039a9c0,c44545c8,3,c4456400) at vrele+0x19b vn_close(c44545c8,3,c4456400,c4078900,d7b9cc44) at vn_close+0x5d vn_closefile(c4209078,c4078900,c03657a0,72a,0) at vn_closefile+0x30 fdrop_locked(c4209078,c4078900,c03657a0,668,c4078900) at fdrop_locked+0x17c fdrop(c4209078,c4078900,c03ef8c0,c03f1838,246) at fdrop+0x3e closef(c4209078,c4078900,c03657a0,342,c4209078) at closef+0xac close(c4078900,d7b9cd10,c03915a9,418,1) at close+0x158 syscall(bfbf002f,2f,bfbf002f,bfbfedcd,bfbfedfd) at syscall+0x2ee Xint0x80_syscall() at Xint0x80_syscall+0x1d --- syscall (6, FreeBSD ELF32, close), eip = 0x280f7a9b, esp = 0xbfbfed9c, ebp = 0xbfbfef38 --- Also from david, vprint output: 0xc44545c8: tag devfs, type VCHR, usecount 1, writecount 1, refcount 0, What's interesting here is that we're about to drop our reference but we have not decremented the writecount. I'm sure it's a simple logic error somewhere. I'll have to wait until tonight to look for it. If anyone finds it in the mean time they are welcome to commit a fix. Thanks, Jeff To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Journaled filesystem in CURRENT
* De: Matthias Schuendehuette [EMAIL PROTECTED] [ Data: 2002-09-25 ] [ Subjecte: Re: Journaled filesystem in CURRENT ] If I may add a comment here... You already *have* a kind of journaled filesystem for some time now. Please read Soft Updates vs. Journalling Filesystems from M.K. McKusick (www.mckusick.com). I'm really sad if see the efforts done especially for porting JFS to FreeBSD, which has already under Linux a more than poor performance. The only reason for porting JFS is IMHO to be able to mount JFS Volumes under FreeBSD - if that's worth the effort... Why begging for 'Journaling' if you have 'Journaling next generation'? People concentrating on interoperability uses of filesystems are out of their minds to be writing them in-kernel, when they could be running them from userland as userland nfs servers, accessing the raw disks. All we need is to make this a default part of the system, add a libuserfs to provide an abstraction layer, and tada. Let me know when there's a JFS4NFS and I'll give a damn, cause then I can use it everywhere I'd need to. FWIW, background fsck and softdep and ufs2 will give you all of the good stuff you *see* from using a journaled fs, without the corruption of a whole disk, like my girlfriend's laptop went through, running with Linnex XFS. juli. -- Juli Mallett [EMAIL PROTECTED] | FreeBSD: The Power To Serve Will break world for fulltime employment. | finger [EMAIL PROTECTED] http://people.FreeBSD.org/~jmallett/ | Support my FreeBSD hacking! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
troubles with recent -current
Hi! I'm experiencing an increasing amount of problems here, and will try to list them below. Some of this may be well known already, but, hopefully, something will be usefull. Unless I set rc_ng to NO, the ypbind will not start, even though enable_nis_client is set and Starting ypbind is displayed on boot. Attempts to shutdown gracefully result in panic -- negative refcount in vnrele (vfrele?) in vnclose() called from vnclosefile() -- can not be more precise without the serial console and another machine. X-server was working fine up to a few weeks ago. With Sep 17th kernel it began crashing every few days. With today's kernel the whole machine reboots after a few minutes in X11, although it can go through kernel (and/or XFree86-4) build in text only mode. I rebuilt XFree86-4-libraries and -Server to be sure, but it is not helping :-\ sc (or tty*?) appears to be broken -- every once in a while a particular virtual terminal gets locked out. If root was logged in on it, the syslog messages still appear, but there is no cursor and no input. The sure way to replicate is to try to login somewhere with ssh. After the password prompt, the tty is disabled. Actually, I just replicated this with vt instead of sc. Except that in sc-mode, once you leave the tty (with Alt-Fx), you can not get back to it. With vt you can. Exiting elm will hose the tty with vt (TERM set to pcvt25). Running mergemaster with sc will hose the tty too eventually. Actually, ssh does the same to xterm too -- and that's the way to reboot the whole machine. For whatever reason, with vt instead of sc, the Alt key is not usable under X11 -- I usually move windows around with Alt-left-mbutton, which does not work now. Could be a pilot error, of course, for I've never used vt before. -mi To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Panic in VFS subsystem with very recent CURRENT
According to Jeff Roberson: A dump would be good. Some more information on your configuration too I'll send it tomorrow (CET time). please. What filesystems were mounted? You said you were rebooting? Had you done anything significant with the box? Filesystems are /, /usr, /var and /local (which has /home, /src and all that). The machine was rebooting with the new kernel and it paniced while launching the perforce server (p4d). -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] FreeBSD keltia.freenix.fr 5.0-CURRENT #80: Sun Jun 4 22:44:19 CEST 2000 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: troubles with recent -current
I thought it was just me, but since last week sometime I have been seeing several strange crashes in X. It usually has something to do with the keyboard. X will bomb out saying it caught a sig11, and the message in my system log shows a sig6. At first I thought this was due to using XFree that I had built with ICC, but I reverted that and lowered the optimizations and I still see it. My kernel is from Sept 21, and i was going to update last night until I saw all those scary VFS commits come down the pipe. On Wed, 25 Sep 2002, Mikhail Teterin wrote: X-server was working fine up to a few weeks ago. With Sep 17th kernel it began crashing every few days. With today's kernel the whole machine reboots after a few minutes in X11, although it can go through kernel (and/or XFree86-4) build in text only mode. I rebuilt XFree86-4-libraries and -Server to be sure, but it is not helping :-\ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Who broke sort(1) ?
One possible solution to the sort problem: * Continue to accept the old syntax for now, but add a warning message, something like: Warning: sort +N is deprecated, use -k instead. * After a year, drop support for the old syntax. After staring at warning messages for a year, few people will be able to claim ignorance. The messages will serve both to advertise the change and to flag those scripts that rely on the old syntax. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: troubles with recent -current
Mikhail Teterin wrote: Unless I set rc_ng to NO, the ypbind will not start, even though enable_nis_client is set and Starting ypbind is displayed on boot. Do you have rpcbind_enable set? ypbind needs the portmapper and will silently exit if it isn't running. Lars -- Lars Eggert [EMAIL PROTECTED] USC Information Sciences Institute smime.p7s Description: S/MIME Cryptographic Signature
Re: panic in latest build
Michael Hostbaek wrote: I just build latest -CURRENT on my laptop. The error is: panic: vrele: negative ref cnt Debugger(panic) Stopped at Debugger+0x54: xchgl %ebx,in_Debugger.0 I did the following: After bootup - logged in as root. touch'ed /var/log/xferlog and hit ctrl-d, to logout. (That is when the panic occured) I got a similar panic just following Jeff's rather complicated vfs kernel patches last night. I decided to wait and try again in a day or so to let the experts hash it out ;-) Just as another data-point, I'm seeing this too. Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: troubles with recent -current
In the last episode (Sep 25), Lars Eggert said:
Mikhail Teterin wrote:
Unless I set rc_ng to NO, the ypbind will not start, even though
enable_nis_client is set and Starting ypbind is displayed on boot.
Do you have rpcbind_enable set? ypbind needs the portmapper and will
silently exit if it isn't running.
Ooh. bug! rc.d/ypbind should have the same check all the other
rpcbind-dependant scripts have:
ypserv_precmd()
{
case ${OSTYPE} in
FreeBSD)
if ! checkyesno rpcbind_enable \
! /etc/rc.d/rpcbind forcestatus 1/dev/null 21
then
force_depend rpcbind || return 1
fi
;;
esac
... }
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: troubles with recent -current
On Wed, 25 Sep 2002, Mikhail Teterin wrote: Hi! I'm experiencing an increasing amount of problems here, and will try to list them below. Some of this may be well known already, but, hopefully, something will be usefull. Unless I set rc_ng to NO, the ypbind will not start, even though enable_nis_client is set and Starting ypbind is displayed on boot. Locally, I discovered that the hard dependency of ypbind on rpcbind now seems to be broken. Try setting rpcbind_enable=YES explicitly in rc.conf and see if that helps. Gordon already has a bug report from me on this and has plans to resolve it. This is true of some other RPC dependencies also. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects [EMAIL PROTECTED] Network Associates Laboratories To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: troubles with recent -current
Dan Nelson wrote:
Ooh. bug! rc.d/ypbind should have the same check all the other
rpcbind-dependant scripts have:
ypserv_precmd() { case ${OSTYPE} in FreeBSD) if ! checkyesno
rpcbind_enable \ ! /etc/rc.d/rpcbind forcestatus 1/dev/null 21
then force_depend rpcbind || return 1 fi ;; esac ... }
I think there might be another (unrelated) bug in rc_run_script in
/etc/rc.subr. The eval unset line unsets the wrong variable when _arg
is faststart during boot. I think it should unset the start
variables, not the faststart ones which don't exist.
Lars
--
Lars Eggert [EMAIL PROTECTED] USC Information Sciences Institute
smime.p7s
Description: S/MIME Cryptographic Signature
terry, contact me.. (your email bounces)
that's all folks... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: TekRam 395U[W] is ready for commit
On Wed, Sep 25, 2002 at 09:47:36PM +, attila! wrote: David: DC395U on CURRENT from Houchard's driver works like a champ on 'da' (ZIP 100) and 'cd (Creative DVD-RAM) devices; I haven't had an 'sa' device since my Exabyte died. I've been beating on the driver for 10 days and it looks good --works as advertised on the oldest kernel I have around (20 Feb 2002), and at least 5 kernels this month. I would say it's worth committing; can you take it from here? Hi, A commit for this driver is planned by Joerg Wunsch, according to freebsd-scsi. It is not this one, if I remember well Joerg said Tekram driver needed some fixes (and this one is just the one provided by Tekram updated a bit), but I don't know what this fixes are. By the way the version you downloaded is not the last one, which may be found at http://www.ci0.org/trm (I don't really remember what the diff are, certainly mainly style changes). Cheers. Olivier Houchard To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
alpha tinderbox failure
-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree -- stage 2: rebuilding the object tree -- stage 2: build tools -- stage 3: cross tools -- stage 4: populating /home/des/tinderbox/alpha/obj/h/des/src/alpha/usr/include -- stage 4: building libraries -- stage 4: make dependencies -- stage 4: building everything.. -- Kernel build for GENERIC started on Wed Sep 25 15:20:33 PDT 2002 -- Kernel build for GENERIC completed on Wed Sep 25 15:51:18 PDT 2002 -- Kernel build for LINT started on Wed Sep 25 15:51:19 PDT 2002 -- === vinum cc1: warnings being treated as errors /h/des/src/sys/coda/coda_venus.c: In function `venus_ioctl': /h/des/src/sys/coda/coda_venus.c:277: warning: cast from pointer to integer of different size /h/des/src/sys/coda/coda_venus.c:292: warning: cast from pointer to integer of different size /h/des/src/sys/coda/coda_venus.c: In function `venus_readlink': /h/des/src/sys/coda/coda_venus.c:380: warning: cast from pointer to integer of different size /h/des/src/sys/coda/coda_venus.c: In function `venus_readdir': /h/des/src/sys/coda/coda_venus.c:637: warning: cast from pointer to integer of different size *** Error code 1 Stop in /h/des/obj/h/des/src/sys/LINT. *** Error code 1 Stop in /h/des/src. *** Error code 1 Stop in /h/des/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: panic in latest build
Jeff Roberson wrote: Can you give me some more info? What filesystems did you have mounted? Any kernel options that are not in GENERIC? I had ext2 mounted in addition to the usual BSD/softupdates and swap partition. I had just rebooted the new kernel, started X/gnome with an gnome-terminal and had just typed su, entered the password and hit enter. At that point the xterminal froze, and the cursor where the password was entered started flickering very rapidly (loop?). I switched to a pseudo-terminal and tried logging as root to kill the xterminal and got the same freeze after entering the password, and the machine panicked at that point and rebooted. Sorry I don't recall the error message but it didn't seem familiar. CD9660 (compiled in) SC_TWOBUTTON_MOUSE RANDOM_IP_ID LINPROCFS COMPAT_LINUX CPU_ENABLE_SSE CPU_ATHLON_SSE_HACK To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: troubles with recent -current
On Wed, 25 Sep 2002, Mikhail Teterin wrote: [...] Unless I set rc_ng to NO, the ypbind will not start, even though enable_nis_client is set and Starting ypbind is displayed on boot. Locally, I discovered that the hard dependency of ypbind on rpcbind now seems to be broken. Try setting rpcbind_enable=YES explicitly in rc.conf and see if that helps. Gordon already has a bug report from me on this and has plans to resolve it. This is true of some other RPC dependencies also. Thanks, but I have much bigger troubles at the moment :-( The workaround for this one is simple -- rc_ng=NO... FWIW, this -- introducing this sort of instability just two months before the scheduled release -- is a lot more damaging than the stupid trolls, IMO. The finger-breakers should consider leaving the troll alone and switching to super-gluing the pointy hats to the apropriate skulls :-| -mi To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: troubles with recent -current
On Wed, 25 Sep 2002, Mikhail Teterin wrote: Thanks, but I have much bigger troubles at the moment :-( The workaround for this one is simple -- rc_ng=NO... FWIW, this -- introducing this sort of instability just two months before the scheduled release -- is a lot more damaging than the stupid trolls, IMO. The finger-breakers should consider leaving the troll alone and switching to super-gluing the pointy hats to the apropriate skulls :-| There are probably going to be a few nits involved in the VFS changes, but there are a number of serious bugs being fixed here. I've been running into a bug on some boxes involving a race condition that occurs when newsyslog runs on a busy system resulting in a inode deadlock. It also may be that many of the problems were bumping into now may merely be existing bugs that are now more visible. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects [EMAIL PROTECTED] Network Associates Laboratories To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
X server crashes?
I notice several people complaining about crashing X servers recently. I'm seeing them also for about 2 weeks or so, usually mozilla-related. I've seen this error message following at least two or three of these crashes: Fatal server error: Beziers this big not yet supported. Anyone else seeing the same message? -- WTF is a bezier? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: X server crashes?
walt ([EMAIL PROTECTED]) wrote: WTF is a bezier? A bezier is a type of curve drawn by endpoints and anchor points to bend it. -- Eric Hodel - [EMAIL PROTECTED] - http://segment7.net All messages signed with fingerprint: FEC2 57F1 D465 EB15 5D6E 7C11 332A 551C 796C 9F04 msg43407/pgp0.pgp Description: PGP signature
Re: cvs commit: src/sys/sys lockmgr.h
On Wed, 25 Sep 2002, Don Lewis wrote: I tried booting a kernel with lock checking enabled and got the following panic: panic: mutex vnode interlock owned at vnode_if.h:24 Yeah, sorry, there was a bit of my patch that I forgot to commit. It's in there now. Thanks! Jeff To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: X server crashes?
On Wed, 25 Sep 2002, walt wrote: Date: Wed, 25 Sep 2002 16:45:16 -0700 From: walt [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: X server crashes? I notice several people complaining about crashing X servers recently. I'm seeing them also for about 2 weeks or so, usually mozilla-related. I've seen this error message following at least two or three of these crashes: Fatal server error: Beziers this big not yet supported. Anyone else seeing the same message? Yes. They started after the last round of KSE-kernel changes which also required changes to libc_r. Bye! Michael Reifenberger ^.*Plaut.*$, IT, R/3 Basis, GPS To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: X server crashes?
On Thu, Sep 26, 2002 at 02:51:05AM +0200, Michael Reifenberger wrote: Yes. They started after the last round of KSE-kernel changes which also required changes to libc_r. I reckon that they're libc_r bugs as well. Linux-Opera has been causing X11 to coredump. With a kernel from 24 hours ago however X no longer crashes, but Opera spends a lot of time in 'select' whilst starting and appears to hang. Joe -- As far as the laws of mathematics refer to reality, they are not certain; and as far as they are certain, they do not refer to reality. - Albert Einstein, 1921 msg43410/pgp0.pgp Description: PGP signature
Re: X server crashes?
Yep, I'm seeing this using the new native Opera binary, when doing some font-related things. On Wed, 25 Sep 2002, Eric Hodel wrote: walt ([EMAIL PROTECTED]) wrote: WTF is a bezier? A bezier is a type of curve drawn by endpoints and anchor points to bend it. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: X server crashes?
Michael Reifenberger wrote: On Wed, 25 Sep 2002, walt wrote: Date: Wed, 25 Sep 2002 16:45:16 -0700 From: walt [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: X server crashes? I notice several people complaining about crashing X servers recently. I'm seeing them also for about 2 weeks or so, usually mozilla-related. I've seen this error message following at least two or three of these crashes: Fatal server error: Beziers this big not yet supported. Anyone else seeing the same message? Yes. They started after the last round of KSE-kernel changes which also required changes to libc_r. I got it too: Fatal server error: Beziers this big not yet supported This was a few days ago. I was typing something at the time. Mozilla was running but it is an old linux binary, not a freebsd-native binary. Unless exmh/wish or xterm are threaded, I think that clears libc_r. This machine has not had an X server crash in over 6 months - until that one. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] All of this is for nothing if we don't go to the stars - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: troubles with recent -current
On Wed, 25 Sep 2002, Mikhail Teterin wrote: FWIW, this -- introducing this sort of instability just two months before the scheduled release -- is a lot more damaging than the stupid trolls, IMO. The finger-breakers should consider leaving the troll alone and switching to super-gluing the pointy hats to the apropriate skulls :-| There are probably going to be a few nits involved in the VFS changes, but there are a number of serious bugs being fixed here. I've been running into a bug on some boxes involving a race condition that occurs when newsyslog runs on a busy system resulting in a inode deadlock. It also may be that many of the problems were bumping into now may merely be existing bugs that are now more visible. I'm sure we made progress. But it would be better, if the few nits were noticed and fixed before committing. They are impossible not to bump into -- judging by the others' responses -- unless, of course, the developers do not routinely use -current as their primary OS. Something we all should be doing now, that the long promised release date is only two months away. -mi To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: panic in latest build
Jeff Roberson wrote: I'll look at it a bit later today. Can you give me some more info? 24 hours later: I just compiled another new kernel. This time all I did was log in as root and unmount the ext2 filesystem, which gets mounted automatically at boot. Then I hit ctrl-D and got this: panic: vrele: negative refcnt syncing discspanic: bdwrite: buffer is not busy pfs_vncache_unload(): 1 entries remaining rebooting... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
VFS panic is now fixed.
The VFS panic that was introduced in my recent commits has been fixed. I accidentally commited extra stuff from my tree that was not entirely correct. Thank you all for the error reports and debugging assistance. Jeff To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: troubles with recent -current
On Wed, 25 Sep 2002, Mikhail Teterin wrote: There are probably going to be a few nits involved in the VFS changes, but there are a number of serious bugs being fixed here. I've been running into a bug on some boxes involving a race condition that occurs when newsyslog runs on a busy system resulting in a inode deadlock. It also may be that many of the problems were bumping into now may merely be existing bugs that are now more visible. I'm sure we made progress. But it would be better, if the few nits were noticed and fixed before committing. They are impossible not to bump into -- judging by the others' responses -- unless, of course, the developers do not routinely use -current as their primary OS. Something we all should be doing now, that the long promised release date is only two months away. The VFS patch was posted at least a week or two ago, and I've been running it on one of my own machines for at least a few days without problems. Inevitably in the committing of any large set of changes, there will be nits, and they seem to be resolving themselves pretty quickly (just saw two jeffr commits that were things missed in merging the patchset). Robert N M Watson FreeBSD Core Team, TrustedBSD Projects [EMAIL PROTECTED] Network Associates Laboratories To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: X server crashes?
That precisely describes my crashes. _always_ when i was typing something. On Wed, 25 Sep 2002, Peter Wemm wrote: This was a few days ago. I was typing something at the time. Mozilla was running but it is an old linux binary, not a freebsd-native binary. Unless exmh/wish or xterm are threaded, I think that clears libc_r. This machine has not had an X server crash in over 6 months - until that one. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] All of this is for nothing if we don't go to the stars - JMS/B5 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
panic: pipe buffer gone
this is on a UP machine running a -current from ~19 sep. Two nights in a row it has died with: panic: pipe buffer gone Debugger(panic) Stopped at Debugger+0x54: xchgl %ebx,in_Debugger.0 db trace Debugger(c048d71c,c0538440,c0492060,e2f38c04,1) at Debugger+0x54 panic(c0492060,0,c0491fbf,36f,c02f55b0) at panic+0xab pipe_write(c67c2ec4,e2f38c7c,c22ab280,0,c6596780) at pipe_write+0x6c0 dofilewrite(c6596780,c67c2ec4,1,805d000,62) at dofilewrite+0xe5 write(c6596780,e2f38d10,c04b0c69,418,3) at write+0x69 syscall(2f,2f,2f,1,0) at syscall+0x2be Xint0x80_syscall() at Xint0x80_syscall+0x1d --- syscall (4, FreeBSD ELF32, write), eip = 0x8048f67, esp = 0xbfbff36c, ebp = 0xbfbff3f8 --- exclusive sleep mutex pipe mutex r = 0 (0xc7096d80) locked @ ../../../kern/sys_pipe.c:879 -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | 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 [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: VFS panic is now fixed.
Jeff Roberson wrote: The VFS panic that was introduced in my recent commits has been fixed... The obvious problems (at least) are gone now, thanks. In fact, even the X server didn't make fun of my Big Beziers this time around. -- Maybe now's the time to buy a lottery ticket. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: X server crashes?
I use kde3 with Konq and it crashes too on my laptop when i have multiple browsers open. Its usually my friends or girlfriend who crash it with all their browsers, but i haven't noticed much of a problem with Konquer. On Wed, 2002-09-25 at 16:45, walt wrote: I notice several people complaining about crashing X servers recently. I'm seeing them also for about 2 weeks or so, usually mozilla-related. I've seen this error message following at least two or three of these crashes: Fatal server error: Beziers this big not yet supported. Anyone else seeing the same message? -- WTF is a bezier? 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
