Re: looking for warn quota tools
David Taylor wrote: FWIW: It's kind of a dumb idea to send email warning about a condition which is caused by having too much email. We did this on the InterJet, and it was actually a pretty dumb thing to do; you end up with a recursive problem that's unsolvable -- you basically have to let certain cenders be priviledged for the delivery of the messages, which means hacking both the MDA (deliver) and warnquota. In that case, why not just hack pop3d/imapd/whatever to display a 'virtual' e-mail of some type when the user connects. It could be complicated to avoid simply generating a new message every time the user connects without storing the time the last warning was received, I guess. I already suggested that at the end of my email from which you are quoting. 8-). Another issue is that quota enforcement only occurs *after* you exceed the quota, not *when* you exceed the quota. This is because email messages must be treated as atomic units; so if you are within 3k of a 100k quota, and you get an 80k message, you can't not accept it. Why not? I can't see how you can't just bounce it. You may have accepted it, but that doesn't guaranteee delivery, just that you won't drop it on the floor. The quotas in the Cyrus IMAP are implemented differently than you appear to believe they are. I've already indicated why messages must be treated as atomic units, and that quotas are enforced after the fact, because that's often the only time that you can have an accurate size measurement available. Your idea of bouncing the message to the sender is flawed, unless you are willing to drop the message on the floor. Consider the case of two accounts. The first account is over quota. It sends a message to the second account. The message would put that account over quota (this scenario is to pay homage to your idea that you could bounce instead of determine after the fact; even so, if both accounts are over quota, the same logic applies). So you bounce the message back to the first account. Only the first account can not accept the bounce, because it is over quota. Thus you must explicitly allow administrative messages to bypass quota, in your scenario, if you accept responsibility for a message that it turns out that it's impossible for you to deliver. So... you avoid being screwed at one level, only to be screwed as a result of a cascade failure. The way HotMail handles this condition is to drop email that it has accepted to delivery, if it can't be delivered to the user because of them being over quota. But since it has already accepted the email for delivery (by sending 250 OK to the remote SMTP client or MTA, it has pledged to deliver the message, or give failure notification, so the message So why not give failure notification? I thought I made this clear: because the addresses are responded to as valid before the message size is known. The only recourse is to fail the message atomically, regardless of the number of recipients, after the size is known -- after the DATA command, the 354 Continue response, and the acceptance of data, followed by the ., but *before* you return a 250 OK or, in your suggested case, a 451 One of the recipients specified has exceeded quota. Please see RFC-1870 SMTP Service Extension for Message Size Declaration and RFC-2821 Simple Mail Transfer Protocol (SMTP). It's only in the case that the SIZE extension is utilized, the sender has not lied, and another delivery does not complete simultaneously before the message is complete, that permits you to do what you want. Even so, it rtequires the much tighter MSA/MTA/MDA coupling I described previously. For this to work, you would have to serialize access to maildrops by receiver SMTPs (this is an intractable problem), AND you would need to reject mail sent without the SIZE extension, or mail whose actual size exceeded that specified by the SIZE extension (you are not permitted to do this last, since the SIZE extension is defined, by standard, to be advisory, not regulatory). This is on top of the other coupling requirements. Your performance would go into the toilet very quickly, if you did this, particularly your agregate througput for a random (standard) message load. -- It's possible to construct examples, but this is not a mailing list for discussion of SMTP server and protocol issues. Probably it would be a good idea to take this discussion to http://www.imc.org/ , one of the mailing lists specific to your SMTP server software, or one of the IETF lists, e.g. http://www.imc.org/ietf-smtp/index.html ; the archive hoted there goes all the way back to 27 Dec 1990. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: looking for warn quota tools
Terry Lambert wrote: For this to work, you would have to serialize access to maildrops by receiver SMTPs (this is an intractable problem), AND you would need to reject mail sent without the SIZE extension, or mail whose actual size exceeded that specified by the SIZE extension (you are not permitted to do this last, since the SIZE extension is defined, by standard, to be advisory, not regulatory). This is on top of the other coupling requirements. To elaborate a little on why this is bad, consider the delivery of a message to (A,B,C) that lock maildrops, but occurs concurrently with another deliver to (C,H,I,J,K,L,M,N,O,P,A). Thus, a deadlock may occur during the locking stage. The problem with this is that for each RCPT TO: line, you must respond with a success/failure notification to the peer SMTP server, so if you depend upon the locking occurring, then the only method you have of rejecting in the case noted above is to fail the DATA request, since the MAIL FROM: and one or more RCPT TO: have already been accepted. Thus the very design of the protocol is antithetical to the locking of maildrops to provide the enforcement which you seek. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
sparc64 tinderbox failure
Thu Jun 13 07:00:00 GMT 2002 cvs [update aborted]: /home/ncvs/CVSROOT: Permission denied To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Support for USB devices out-of-the-box in -current?
On 13 Jun, Daniel O'Connor wrote: By who ? The USB maintainer.. Who's name escapes me at this point :) Josef Karthauser [EMAIL PROTECTED] Bye, Alexander. -- The dark ages were caused by the Y1K problem. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
Dag-Erling Smorgrav [EMAIL PROTECTED] writes: Thu Jun 13 07:00:00 GMT 2002 cvs [update aborted]: /home/ncvs/CVSROOT: Permission denied Mike, looks like the /work/repo isn't mounted on bowie. Can you fix this before the next run (7 am GMT tomorrow)? DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Bluetooth stack for FreeBSD
Hackers, Another developer snapshot is available at http://www.geocities.com/m_evmenkin/ngbt-fbsd-20020613.tar.gz This release is for -current DP1 only. I had to downgrade back to DP1 due to huge amount of changes in -current. Brief list of changes - Basic support for USB devices. I got myself a 3Com USB Bluetooth dongle (aka ToothBrush :) - Make everything GCC 3.X friendly. - Minor bug fixes As always, i would like to get some feedback. I'm very interested to hear from people who familiar with FreeBSD kernel, Netgraph, Bluetooth and/or USB. thanks, max __ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Bluetooth stack for FreeBSD
Julian, I was just discussing this with people here at USENIX and I'd like to start the process for committing this. Oh, gee, thanks :) but, i'm not so sure about committing. There are several important bits and pieces that needed to be done. First of all, i do want to see properly tested code with all documentation in the tree. I cannot say this about current snapshots. Things that MUST be fixed *before* commiting (IMO) sorted by priority - Documentation, examples man pages - Multiple control hooks for HCI/L2CAP nodes - HCI/L2CAP tools Do you think it deserves a separate directory under netgraph, or maybe a netbluetooth directory. I'd rather not put it under netbluetooth, because it is a Netgraph specific code. It probably makes sense to put it somewhere under netgraph directory. the documentation needs to be made 'commit-ready' too, as well as some examples ready to put in /usr/share/examples/netgraph. yeah, i know... i really should spend some time and write all documentation. thanks, max __ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Crash after world/kernel upgrade
An Tue, Jun 11, 2002 at 11:06:44AM -0700, Edwin Culp schreib : Quoting Steve Ames [EMAIL PROTECTED]: | On Tue, Jun 11, 2002 at 10:51:25PM +0530, Sid Carter wrote: | An Tue, Jun 11, 2002 at 04:58:39PM +0200, Thomas Ugland schreib : I get blown away with network setup with a Fatal trap 12, too. I've cvsuped and rebuilt twice with no change. Hi, Tell me about it. Luckily, I am able to get to FreeBSD after a fresh cvsup and make kernel. But I keep getting these errors from dmesg. -- Jun 14 00:36:27 calvin kernel: /usr/src/sys/vm/uma_core.c:1327: could sleep with process lock locked from /usr/src/sys/kern/kern_prot.c:511 Jun 14 00:36:30 calvin kernel: /usr/src/sys/vm/uma_core.c:1327: could sleep with process lock locked from /usr/src/sys/kern/kern_prot.c:511 Jun 14 00:36:31 calvin kernel: /usr/src/sys/vm/uma_core.c:1327: could sleep with process lock locked from /usr/src/sys/kern/kern_prot.c:613 Jun 14 00:36:33 calvin kernel: /usr/src/sys/vm/uma_core.c:1327: could sleep with process lock locked from /usr/src/sys/kern/kern_prot.c:867 Jun 14 00:36:38 calvin kernel: /usr/src/sys/vm/uma_core.c:1327: could sleep with process lock locked from /usr/src/sys/kern/kern_prot.c:867 Jun 14 00:36:55 calvin last message repeated 5 times Jun 14 00:37:21 calvin kernel: /usr/src/sys/vm/uma_core.c:1327: could sleep with inp locked from /usr/src/sys/netinet/tcp_input.c:631 Jun 14 00:40:00 calvin kernel: /usr/src/sys/vm/uma_core.c:1327: could sleep with process lock locked from /usr/src/sys/kern/kern_prot.c:613 -- I have to yet to start any further apps, cause I just rebooted. Let me see how long I can stay without a reboot. Regards Sid -- I've known him as a man, as an adolescent and as a child -- sometimes on the same day. Sid Carter FreeBSD oder Debian GNU/Linux. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Crash after world/kernel upgrade
An Fri, Jun 14, 2002 at 12:43:51AM +0530, Sid Carter schreib : An Tue, Jun 11, 2002 at 11:06:44AM -0700, Edwin Culp schreib : Quoting Steve Ames [EMAIL PROTECTED]: | On Tue, Jun 11, 2002 at 10:51:25PM +0530, Sid Carter wrote: | An Tue, Jun 11, 2002 at 04:58:39PM +0200, Thomas Ugland schreib : I get blown away with network setup with a Fatal trap 12, too. I've cvsuped and rebuilt twice with no change. I have to yet to start any further apps, cause I just rebooted. Hi, And this are some messages I get when I started fetchmail. - Jun 14 00:44:00 calvin kernel: /usr/src/sys/vm/uma_core.c:1327: could sleep with process lock locked from /usr/src/sys/kern/kern_prot.c:511 Jun 14 00:44:04 calvin kernel: acquiring duplicate lock of same type: inp Jun 14 00:44:04 calvin kernel: 1st inp @ /usr/src/sys/netinet/tcp_input.c:631 Jun 14 00:44:04 calvin kernel: 2nd inp @ /usr/src/sys/netinet/tcp_usrreq.c:144 Jun 14 00:45:00 calvin kernel: /usr/src/sys/vm/uma_core.c:1327: could sleep with process lock locked from /usr/src/sys/kern/kern_prot.c:613 - Of course, previously my machine used to crash and reboot, whenever I started fetchmail with similar errors as pasted above. uname -a FreeBSD calvin 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Fri Jun 14 05:46:24 IST 2002 root@:/usr/obj/usr/src/sys/GENERIC i386 Regards Sid -- I've known him as a man, as an adolescent and as a child -- sometimes on the same day. Sid Carter FreeBSD oder Debian GNU/Linux. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Nouvelle adhérente =?iso-8859-1?q?=20=3A pr=E9sentation=2E?=
On Thu, Jun 13, 2002 at 11:33:24AM +0200 or thereabouts, Charles Sabourdin may have written : première SDL sur recompillation de noyeaux et ajoute de driver. C'est vrai que c'est un truc tout bête mais qui apportera certainement beaucoup. Mmmh... Je sais pas si tu te sens bien de faire 4 heures sur le noyau et les modules sans perdre aucun des spectateurs. Perso, je le sens moyen. Et celle d'octobre, sur Faut-t-il avoir peur de la ligne de commande Mais c'est toujours une proposition personnel, et personne n'a encore valider ces proposition. Donc autant faire un SDL spécial démythification avec au programme la ligne de commande et le noyau (les deux d'un coup, sachant que l'un aide un peu pour l'autre)... Enfin, on a encore un peu de temps pour fixer ça. Quoique, ce serait bien si on pouvait en profiter pour prendre un rythme de croisière et fixer les programmes (complets) avec un peu d'avance, histoire d'être dans les temps pour les C.P. (surtout pour les mensuels). L'idéal étant de fixer le programme de celui de septembre avant de partir (voire celui d'après) pour le filer aux mags pdt les vacances et avoir tout plein de pub dans les mags de septembre =) Vincent -- Vincent TOUGAIT mailto:[EMAIL PROTECTED] http://www.gcu-squad.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Broken world in rtld-elf...
On Thu, Jun 13, 2002 at 12:26:05PM +1000, Bruce Evans wrote: rtld still uses asms with the old, broken/fragile 0 constraint. This constraint is especially broken/fragile if things are pessimized by compiling without optimizations. D'oh! Is there any chance of sticking a warning in the makefile if -O0 (or whatever else would cause it to not compile) is present? - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Crash after world/kernel upgrade
On 13-Jun-2002 Sid Carter wrote: An Tue, Jun 11, 2002 at 11:06:44AM -0700, Edwin Culp schreib : Quoting Steve Ames [EMAIL PROTECTED]: | On Tue, Jun 11, 2002 at 10:51:25PM +0530, Sid Carter wrote: | An Tue, Jun 11, 2002 at 04:58:39PM +0200, Thomas Ugland schreib : I get blown away with network setup with a Fatal trap 12, too. I've cvsuped and rebuilt twice with no change. Hi, Tell me about it. Luckily, I am able to get to FreeBSD after a fresh cvsup and make kernel. But I keep getting these errors from dmesg. s/errors/warnings/. If they were errors your kernel would panic. They are warnings of problems but your machine should still run fine. The duplicate lock of inp is a fairly big problem you should send to hsu@. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ 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: Crash after world/kernel upgrade
Jun 11 22:34:47 calvin kernel: lock order reversal Jun 11 22:34:47 calvin kernel: 1st 0xd311c2f8 inp (inp) @ /usr/src/sys/netinet/tcp_usrreq.c:581 Jun 11 22:34:47 calvin kernel: 2nd 0xc04a5340 Giant (Giant) @ /usr/src/sys/kern/subr_trap.c:76 Jun 11 22:34:47 calvin kernel: exclusive sleep mutex inp r = 0 (0xd311c2f8) locked @ /usr/src/sys/netinet/tcp_usrreq.c:581 Jun 11 22:34:47 calvin kernel: panic: system call shutdown returning with mutex(s) held Some of the networking lock debug messages are supurious, but this one is real and was fixed late Tuesday night. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
HEADS UP: rc.d is in the tree
I've imported the excellent work by Mike Makonnen into the tree. Please note that it should be fully functional but there are some parts that need some looking at: atm ipfilter some others that I'm forgetting Hopefully Mike will chime in with some others. Please try out the functionality by putting rc_ng=YES into your rc.conf and post any problems you might have. -gordon To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Total lockup
Edwin Culp wrote: Quoting Munish Chopra [EMAIL PROTECTED]: | On Wed, Jun 12, 2002 at 06:14:24PM +0200, John Angelmo wrote: | Hello | | I updated world yesterday afternoon now everything bootsup just fine | But after I have done dhclient and my card (rl0 or wi0) got an IP an I | want to check it with ifconfig I get a total lockup this appens if I try | to use startx after I have aquierd an IP | | anyone got any idea? | | /John | | This is currently being covered in another thread on this list (unless | someone picks it up here again that is). | Today's current seems to be ok. I had the same problem yesterday, booted a 5 day old kernel, did a cvsup, made a new world and kernel, rebooted and haven't had any problems, yet. ed To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message Well the only way for me to get the not to lock when I try to access the network is too boot with ACPI_ENABLE=no and load an old kernel but then I get a kernel panic when I try to write something to the system (with cvsup for example) Does anyone have any idea how to solve this? /John To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Crash after world/kernel upgrade
Duplicate inp warnings occur whenever 2 inp locks are held, even though they're on different inps, because all the inp locks are named inp. I've investigated a couple of these already and they were all places where we intended to grab two inp locks. So, for the most part, these warning are harmless. As John said though, panics are serious, so if you get any of those, please report them to me directly, as I only monitor this list periodically. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Crash after world/kernel upgrade
On 13-Jun-2002 Jeffrey Hsu wrote: Duplicate inp warnings occur whenever 2 inp locks are held, even though they're on different inps, because all the inp locks are named inp. I've investigated a couple of these already and they were all places where we intended to grab two inp locks. So, for the most part, these warning are harmless. As John said though, panics are serious, so if you get any of those, please report them to me directly, as I only monitor this list periodically. How do you define the order between teh two inp locks to ensure you don't end up deadlocking? That is why the warning is there. Unless you have a well-defined lock order between inp locks you can easily get into deadlocks. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ 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: HEADS UP: rc.d is in the tree
On Thu, 13 Jun 2002 15:37:55 -0700 (PDT) Gordon Tetlow [EMAIL PROTECTED] wrote: I've imported the excellent work by Mike Makonnen into the tree. Please note that it should be fully functional but there are some parts that need some looking at: atm ipfilter some others that I'm forgetting Hopefully Mike will chime in with some others. I've been having some problems with named not starting properly since I synced up all the scripts with the NetBSD bits. I'm not sure exactly what it is, that it doesn't like (the order in which it was started changed), but I'll be taking a look at it in a bit. Cheers, Mike Makonnen To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Broken world in rtld-elf...
Alex Zepeda wrote:
On Thu, Jun 13, 2002 at 12:26:05PM +1000, Bruce Evans wrote:
rtld still uses asms with the old, broken/fragile 0 constraint. This
constraint is especially broken/fragile if things are pessimized by
compiling without optimizations.
D'oh!
Is there any chance of sticking a warning in the makefile if -O0 (or
whatever else would cause it to not compile) is present?
GCCVERS=`gcc -v 21 | grep version | cut -d -f 3`
.if ${GCCVERS} = 3.1
.BEGIN:
echo Optimization with GCC 3.1 is often broken! 2
.endif
Oh... you wanted to grep -O out of the CFLAGS and CXXFLAGS?
How to do that should be obvious from the above...
-- Terry
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: Broken world in rtld-elf...
* Terry Lambert [EMAIL PROTECTED] escriurères
Alex Zepeda wrote:
On Thu, Jun 13, 2002 at 12:26:05PM +1000, Bruce Evans wrote:
rtld still uses asms with the old, broken/fragile 0 constraint. This
constraint is especially broken/fragile if things are pessimized by
compiling without optimizations.
D'oh!
Is there any chance of sticking a warning in the makefile if -O0 (or
whatever else would cause it to not compile) is present?
GCCVERS=`gcc -v 21 | grep version | cut -d -f 3`
.if ${GCCVERS} = 3.1
.BEGIN:
echo Optimization with GCC 3.1 is often broken! 2
.endif
Oh... you wanted to grep -O out of the CFLAGS and CXXFLAGS?
How to do that should be obvious from the above...
Errr, it was with 0 level optimisation that is the problem, not a real
level. Read carefully what bde said, and look at hte warnings and how
GCC deals with the code in question.
Also, your example is very wrong, read make(1)'s section on dealing with
variables.
--
Juli Mallett [EMAIL PROTECTED] FreeBSD: The Power To Serve
Perception is prejudice / Don't classify me / Accept me as me / Not what you see
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: Broken world in rtld-elf...
Juli Mallett wrote: Errr, it was with 0 level optimisation that is the problem, not a real level. Read carefully what bde said, and look at hte warnings and how GCC deals with the code in question. Also, your example is very wrong, read make(1)'s section on dealing with variables. I know my example is very wrong; though it could be used to grep for optimizer flags, where it could not be used for what I jokingly said it could be used for... I guess it was too subtle. Question: -O0 fails to produce good code; how do I check and warn if -O0 is being used? Answer: Fix -O0, or grep its use and complain about it Answer 2: Make its use an argument error to the compiler, until it is fixed Answer 3: Quit munging the Makefiles, when they will just need to be unmunged later, and the problem goes away if you change the compiler -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Broken world in rtld-elf...
* Terry Lambert [EMAIL PROTECTED] escriurères
Juli Mallett wrote:
Errr, it was with 0 level optimisation that is the problem, not a real
level. Read carefully what bde said, and look at hte warnings and how
GCC deals with the code in question.
Also, your example is very wrong, read make(1)'s section on dealing with
variables.
I know my example is very wrong; though it could be used to grep
for optimizer flags, where it could not be used for what I jokingly
said it could be used for... I guess it was too subtle.
Question:
-O0 fails to produce good code; how do I check and warn if
-O0 is being used?
Answer:
Fix -O0, or grep its use and complain about it
.if ${MACHINE_ARCH} == i386
CFLAGS:= $(CFLAGS:N-O0)
.endif
I think.
Answer 2:
Make its use an argument error to the compiler, until it is
fixed
-O0 isn't broken, it just doesn't handle this construct right, and the issue
is known.
Answer 3:
Quit munging the Makefiles, when they will just need to be
unmunged later, and the problem goes away if you change
the compiler
NetBSD and OpenBSD do this to work around crappy toolchains all the time.
Most of the time it's to *enable* -O0 though, ironically :)
--
Juli Mallett [EMAIL PROTECTED] FreeBSD: The Power To Serve
Perception is prejudice / Don't classify me / Accept me as me / Not what you see
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
i386 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/i386/obj/local0/scratch/tinderbox/src/i386/usr/include -- stage 4: building libraries -- === lib/compat === lib/libalias === lib/libatm === lib/libbind === lib/libbz2 === lib/libc === lib/libc_r /local0/scratch/tinderbox/src/lib/libc_r/uthread/uthread_cap_get_fd.c:30:28: sys/capability.h: No such file or directory /local0/scratch/tinderbox/src/lib/libc_r/uthread/uthread_cap_set_fd.c:30:28: sys/capability.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /local0/scratch/tinderbox/src/lib/libc_r. *** Error code 1 Stop in /local0/scratch/tinderbox/src/lib. *** Error code 1 Stop in /local0/scratch/tinderbox/src. *** Error code 1 Stop in /local0/scratch/tinderbox/src. *** Error code 1 Stop in /local0/scratch/tinderbox/src. *** Error code 1 Stop in /local0/scratch/tinderbox/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Crash after world/kernel upgrade
An Thu, Jun 13, 2002 at 02:19:52PM -0700, Jeffrey Hsu schreib : Duplicate inp warnings occur whenever 2 inp locks are held, even though they're on different inps, because all the inp locks are named inp. I've investigated a couple of these already and they were all places where we intended to grab two inp locks. So, for the most part, these warning are harmless. As John said though, panics are serious, so if you get any of those, please report them to me directly, as I only monitor this list periodically. Hi, Just came today and my computer has rebooted, asking me for the power-on password. These are the warnings or panic messages I see. --- Jun 14 10:25:00 calvin kernel: /usr/src/sys/vm/uma_core.c:1327: could sleep with process lock locked from /usr/src/sys/kern/kern_prot.c:613 Jun 14 10:30:00 calvin kernel: /usr/src/sys/vm/uma_core.c:1327: could sleep with process lock locked from /usr/src/sys/kern/kern_prot.c:613 Jun 14 10:36:08 calvin syslogd: kernel boot file is /boot/kernel/kernel Jun 14 10:36:08 calvin kernel: panic: lock (sleep mutex) inp not locked @ /usr/src/sys/netinet/tcp_subr.c:1069 Jun 14 10:36:08 calvin kernel: Jun 14 10:36:08 calvin kernel: syncing disks... panic: bremfree: bp 0xc764e1a0 not locked Jun 14 10:36:08 calvin kernel: Uptime: 9h53m57s Jun 14 10:36:08 calvin kernel: pfs_vncache_unload(): 1 entries remaining Jun 14 10:36:08 calvin kernel: Terminate ACPI Jun 14 10:36:08 calvin kernel: Automatic reboot in 15 seconds - press a key on the console to abort Jun 14 10:36:08 calvin kernel: Rebooting... --- Regards Sid -- I've known him as a man, as an adolescent and as a child -- sometimes on the same day. Sid Carter FreeBSD oder Debian GNU/Linux. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
cost of vidcontrol -m ?
http://www.freebsd.org/cgi/query-pr.cgi?pr=conf/39125 presents an interesting hypothesis, namely that vidcontrol -m ought to be enabled by default in usbd.conf. I tend to agree with that premise, but before I commit it I was curious as to what the cost of doing this would be. Specifically, I have a usb mouse, but I spend almost all my time in X, so when I need the copy/paste stuff in the console, I just run vidcontrol by hand. It would be more convenient to have it just work, but I'd hate to screw over low resource users in the proces... Doug -- We have known freedom's price. We have shown freedom's power. And in this great conflict, ... we will see freedom's victory. - George W. Bush, President of the United States State of the Union, January 28, 2002 Do YOU Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cost of vidcontrol -m ?
In the last episode (Jun 13), Doug Barton said: http://www.freebsd.org/cgi/query-pr.cgi?pr=conf/39125 presents an interesting hypothesis, namely that vidcontrol -m ought to be enabled by default in usbd.conf. I tend to agree with that premise, but before I commit it I was curious as to what the cost of doing this would be. Specifically, I have a usb mouse, but I spend almost all my time in X, so when I need the copy/paste stuff in the console, I just run vidcontrol by hand. It would be more convenient to have it just work, but I'd hate to screw over low resource users in the proces... If the mouse is not moving, I can't imagine it has any cost. -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Crash after world/kernel upgrade
An Fri, Jun 14, 2002 at 10:44:59AM +0530, Sid Carter schreib : An Thu, Jun 13, 2002 at 02:19:52PM -0700, Jeffrey Hsu schreib : Duplicate inp warnings occur whenever 2 inp locks are held, even though they're on different inps, because all the inp locks are named inp. I've investigated a couple of these already and they were all places where we intended to grab two inp locks. So, for the most part, these warning are harmless. As John said though, panics are serious, so if you get any of those, please report them to me directly, as I only monitor this list periodically. Just came today and my computer has rebooted, asking me for the power-on password. These are the warnings or panic messages I see. Jun 14 10:36:08 calvin kernel: syncing disks... panic: bremfree: bp 0xc764e1a0 not locked Jun 14 10:36:08 calvin kernel: Uptime: 9h53m57s Jun 14 10:36:08 calvin kernel: pfs_vncache_unload(): 1 entries remaining Jun 14 10:36:08 calvin kernel: Terminate ACPI Hi, Similar Crash happened again. Jun 14 11:30:32 calvin syslogd: kernel boot file is /boot/kernel/kernel Jun 14 11:30:32 calvin kernel: Memory modified after free 0xd3fc5500(252) Jun 14 11:30:32 calvin kernel: panic: Most recently used by kqueue Jun 14 11:30:32 calvin kernel: Jun 14 11:30:32 calvin kernel: Jun 14 11:30:32 calvin kernel: syncing disks... panic: bremfree: bp0xc767f070 n ot locked Jun 14 11:30:32 calvin kernel: Uptime: 53m5s Jun 14 11:30:32 calvin kernel: Terminate ACPI Jun 14 11:30:32 calvin kernel: Automatic reboot in 15 seconds - press a key on the console to abort Regards Sid -- I've known him as a man, as an adolescent and as a child -- sometimes on the same day. Sid Carter FreeBSD oder Debian GNU/Linux. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
