Re: troubles with recent -current
On Wed, 25 Sep 2002, Mikhail Teterin wrote: : 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. Same here. cvsup'd this afternoon. 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. I can replicate this at will... simply doing a man or more will freeze that virtual terminal. Darren Henderson [EMAIL PROTECTED] [EMAIL PROTECTED] 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: 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: 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: 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
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
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: 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