Re: nullfs broken on powerpc
FWIW, it is not 'call doadump', it is just 'dump' for some time. I think calling doadump does not work. When I tested my dump changes against head a week ago ddb call doadump() provided the same functionality as it always has. Cheers ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: buildworld failure
The module makefile needs to be updated evidently. Just add it to the dependencies until rwatson gets around to fixing it. On Sun, Aug 14, 2011 at 11:50 PM, Alexander Best arun...@freebsd.org wrote: hi there, has anybody seen this buildworld failure? === sys/modules/portalfs (depend) @ - /usr/git-freebsd-head/sys machine - /usr/git-freebsd-head/sys/amd64/include x86 - /usr/git-freebsd-head/sys/x86/include awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -p awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -q awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -h rm -f .depend CC='clang' mkdep -f .depend -a -nostdinc -DSTRIP_FBSDID -D_KERNEL -DKLD_MODULE -I. -I@ -I@/contrib/altq /usr/git-freebsd-head/sys/modules/portalfs/../../fs/portalfs/portal_vfsops.c /usr/git-freebsd-head/sys/modules/portalfs/../../fs/portalfs/portal_vnops.c /usr/git-freebsd-head/sys/modules/portalfs/../../fs/portalfs/portal_vnops.c:41:10: fatal error: 'opt_capsicum.h' file not found #include opt_capsicum.h ^ 1 error generated. mkdep: compile failed *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error cheers. alex ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Kernel panic rtfree 2
It would help to know your configuration. Also, can you furnish us with a core? On Fri, Aug 12, 2011 at 9:02 AM, Andrey Smagin samsp...@mail.ru wrote: Before all upgrade system never crash. After upgrade system month ago happens every day Kernel panic rtfree 2 at rtfree route_output sosend_generic soo_write dofilewrite kernwrite write syscallenter syscall Xfast_syscall Now I upgraded to FreeBSD 9.0-BETA1 #32 r224760M and problem exist. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Recent sys/vm/ changes and nvidia-driver
On Sat, May 8, 2010 at 2:39 PM, Brandon Gooch jamesbrandongo...@gmail.com wrote: On Sat, May 8, 2010 at 4:20 PM, b. f. bf1...@googlemail.com wrote: On 05/08/10 13:36, Alan Cox wrote: Doug Barton wrote: On 05/05/10 11:56, Alan Cox wrote: I'm afraid that I would advise waiting a few days. This round of changes are not yet complete. What performance differences, if any, can we expect on uniprocessors from the vm page lock-related changes? Kip's original post on -arch mentioned some performance improvements and no significant regressions, but on a dual 4-core machine. Alan (or Kip): Is there a document available that describes the work being done on the VM system? I would like to -- or like make and attempt to -- read such a document... Hey b. f., to which post on -arch are you referring? there is no document. The basic idea is straightforward, but there are some unpleasant edges to cope with. http://www.mavetju.org/mail/view_message.php?list=freebsd-archid=3155260thread=no -Kip ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Device permissions with DEVFS
Sorry, if I'm repeating something already said, but the tone of your mail would indicate that I'm not. This doesn't sound like an intrinsic limitation of devfs, just an issue with how it is structured now. There should just be a central file for all the devices which devfs sucks in at build (or maybe boot) time specifying the appropriate permissions and any other configuration information. --- Bruce Evans [EMAIL PROTECTED] wrote: On Mon, 18 Nov 2002, Kris Kennaway wrote: Something that needs to be addressed before 5.0 is the insecure default permissions on many devices. For example, on my system, the following devices have insecure permissions on 5.0 (but not on 4.x with the default MAKEDEV settings): crw-r--r-- 1 root operator 117, 0 Nov 18 14:49 acd0 Hrmph. I have been dropping hints about this for a couple of years. crw-rw-rw- 1 root wheel 21, 1 Nov 18 14:49 psm0 Another problem is that it is hard to check for errors if you don't have the hardware, since devfs only creates nodes for existing devices (MAKEDEV doesn't create everything either, but MAKEDEV all gets closer; it's also easier to scan through MAKDEV than through hundreds of device drivers). crw-rw-rw- 1 root wheel 30, 3 Nov 14 21:30 dsp0.0 crw-rw-rw- 1 root wheel 30, 0x00010003 Nov 8 23:38 dsp0.1 crw-rw-rw- 1 root wheel 30, 5 Nov 8 23:38 dspW0.0 crw-rw-rw- 1 root wheel 30, 0x00010005 Nov 8 23:38 dspW0.1 crw-rw-rw- 1 root wheel 30, 11 Nov 8 23:38 dspr0.0 These have the same permissions on 4.x, but they're still insecure (unprivileged users can read from a microphone). I dropped a hint about this 7.5 years in MAKEDEV rev.1.87 (snd_security_hole). I might have fixed this if I had any sound devices. I'm sure there are others I have missed. Could everyone please check their /dev (better, check the kernel source)? I have noticed the following: acd track devices have the same permissions bugs as ordinary acd devices, and ownership bugs too. The cuaa devices for the rp driver have bogus ownerships and permissions in both MAKEDEV and devfs. IIRC, the permissions are 600 in MAKDEV and 666 in devfs, but should be 660; the ownership is root:wheel in both but should be uucp:dialer. (If MAKEDEV or devfs created an instance of each type of device, then bugs like this would be easier to see using ls -l /dev/cua*; all cua devices should have the same default ownerships and permissions. Similarly for disk devices except there is no simple pattern like cua* for them.) lpctl* doesn't even have the correct name in devfs, so its one user (lptcontrol(8)) can't find it. ata has bogus group operator in devfs (it has mode 600 so it can't be accessed by group operator). MAKEDEV has a few nonsense groups like this too. In general, control devices should not be accessible by group operator since access generally gives write-like access. mdctl uses a hard-coded magic minor number in both MAKEDEV and devfs. The dkminor() function in MAKDEV and dk[make]minor() functions in the kernel exist to reduce such magic. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message __ Do you Yahoo!? Yahoo! Web Hosting - Let the expert host your site http://webhosting.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Softupdate panic: softdep_update_inodeblock: update failed
It may not be memory corruption. I get this panic on various versions of STABLE on different pieces of hardware. See 42235 and 42277. -Kip --- Martin Blapp [EMAIL PROTECTED] wrote: Hi, If I were you I'd start swapping memory modules, because I'm not having Already did that. I even used ECC ram. any trouble with -CURRENT and I havn't seen anyone else having trouble. Did you try to build a huge project ? If I don't compile anything big and load the machine it works perfectly. Did you compile your kernel with any wierd optimizations? No. And this system works perfectly before after I turned on PG_G. The instability began after gcc3.2 import. Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message __ Yahoo! - We Remember 9-11: A tribute to the more than 3,000 lives lost http://dir.remember.yahoo.com/tribute To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Majordomo has major shortcomings was Re: Your misleading, no LYINGmessage to me
I am inclined to agree. An obscure company like Lyris would not be making money hand over fist if majordomo were that great. -Kip On Mon, 3 Jan 2000, Jesper Skriver wrote: On Sun, Jan 02, 2000 at 09:59:28PM -0600, wrote: He is just expressing his point. From what I can tell someone removed him from the list with no reason and now he is angry. I probably would be too. Please cool it, it has happened to me more than once, and I believe I havn't insulted any on these mailinglists, it's probably a "feature" of majordomo, as I've also seen it here with some of our mailing lists, this one just had a particular bad timing ... /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk Work:Network manager @ AS3292 (Tele Danmark DataNetworks) Private: Geek@ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. 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
latest version of threads library
I would like to use the latest threads source because my application does not work correctly with the signal handling bugs in 3.x's threads. However, it does not appear that I can change it without replacing all of libc. Is this correct? Or is there some simple change I can make to the files in libc that include pthread_private.h when compiled in libc_r? I am running: FreeBSD io.lyris.com 3.4-RELEASE FreeBSD 3.4-RELEASE #0: Mon Dec 27 15:20:33 PST 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/KMM i386 Thanks. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [Majordomo@FreeBSD.ORG: Majordomo results: which]
Any pointers to web pages on setting up a killfile? The signal to noise ratio on this list is dropping rapidly. -Kip To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: One final note and a bite me to you
Grow up. -Kip On Sun, 2 Jan 2000, Karl Denninger wrote: Just for those of you who think this whole "magical unsubscribe" is a "fluke"; All unsubscribes and subscribes to FreeBSD's lists must be authenticated. Majordomo is set to confirm all transactions. Whoever did this did it directly by logging into Freefall and editing the mailing list files themselves, or otherwise forged the request so as to get the "key" for the response. Have a nice year folks. THIS time, with only other people to benefit from my participation here, I'm not willing to play. Some of you will remember that about two years ago a SIMILAR forged unsubscribe was sent in for me during a heated discussion right here on this list. Theo was right in splitting off from you folks. I should have followed him a couple of years ago and done my own split. Now, its simply not worth it. This makes twice - and that's enough for me. As for you Paol, perhaps some day you'll stop trying to bullshit people. Occasionally when you do that you run into someone who has AT LEAST a single class in physical science and understands the uncertainty of measurements. -- -- Karl Denninger ([EMAIL PROTECTED]) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! 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: latest version of threads library
Do you know what the timeline is on this integration? -Kip On Sun, 2 Jan 2000, Daniel Eischen wrote: Kip Macy [EMAIL PROTECTED] wrote: Sorry for sending this again but when I first sent it -current was embroiled in a flame war. I would like to use the latest threads source because my application does not work correctly with the signal handling bugs in 3.x's threads. However, it does not appear that I can change it without replacing all of libc. Is this correct? Or is there some simple change I can make to the files in libc that include pthread_private.h when compiled in libc_r? Hmm, I think the only thing that will bite you in bringing in -currents libc_r are the socket.h changes that went in around Nov 24, 1999. I haven't tried it myself... YMMV Someone is working on merging -current libc_r into -stable, so perhaps if you want to hold out a little longer, it'll get done for you. Dan Eischen [EMAIL PROTECTED] 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: Proposed patch to fix VN device (again)
This is unwontedly personal and has no place in a public mailing list. Please keep your replies confined to technical content (or your concerns about the lack thereof) and keep always in mind that getting emotional serves only to generate heat when what's needed is light. - Jordan And it undermines even the strongest of technical arguments. -Kip To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sysinstall: is it really at the end of its lifecycle?
Most people I have shown the FreeBSD installer are much more impressed with it than Redhat's snazzy GUI. -Kip On Tue, 14 Dec 1999, jack wrote: Today Mike Smith wrote: Given the primary mission of sysinstall is to load FreeBSD, I'd go so far as to say that developing an X version would be wasting valuable developer resources (IMHO, of course). It's a painful tradeoff between functionality and flash. The latter is an unfortunate necessity if we are to avoid looking hopelessly outdated. Not arguing the point in reguard to the "unwashed masses", but when an NT[hates it]/Novell admin watched me install FreeBSD last week his opinion of sysinstall was that it was about the cleanest and most straight forward install program he's seen. Guess he, like I, is more concerned with functionality than flash. :) -- Jack O'NeillSystems Administrator / Systems Analyst [EMAIL PROTECTED] Crystal Wind Communications, Inc. Finger [EMAIL PROTECTED] for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages /dev/null -- 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: Threads and my new job.
I will admit that I have had odd behaviours with threads in developing Lyris on FreeBSD that I have not seen on Solaris, NT, or Linux. I will see things like what appears to be the thread scheduler stop scheduling threads and just do a busy wait. I have not tracked it down any further for lack of time. -Kip On Wed, 24 Nov 1999, Nick Hilliard wrote: Why do we need to smite the Linux database servers? With threads in their current state they already outperform Linux's native threads by ~50x for things like sending mail. I would assume that the differences in database performance is similar. The threads ( the old nfs issues which have now thankfully been fixed) in their current state led bCandid to write about the Cyclone news router: : Issues the w/FreeBSD kernel and buggy threads have required our development : team to wait until improvements to the OS can be made. We did have a beta : posted on our website for a while but have since removed it. disclaimer: I am not a thread hacker. Nick 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: Threads and my new job.
Jason, you are my savior. Go forth and do much to create Truly Kick Ass Threading. Give me my tools to smite these Linux database servers once and for all! :-) Why do we need to smite the Linux database servers? With threads in their current state they already outperform Linux's native threads by ~50x for things like sending mail. I would assume that the differences in database performance is similar. -Kip To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: People getting automatically unsub'ed from -arch
I know that this is not the place to hype one's own wares, but if your lists have fewer than 200 people, why not just use the free version of lyris. One of its many features is sophisticated bounce handling. -Kip On Mon, 11 Oct 1999, Sean Eric Fagan wrote: In article [EMAIL PROTECTED] you write: only one comment. i remove people from the lists whenever their email bounces. the threshhold is approximately 30 messages in a 24 hour period. mail may bounce due to DNS problems, mail box full, MTA misconfiguration. i also remove people that send vacation messages to the list. oh, and spammers. My mail _has not bounced_. And yet I have been removed. several people with recurring email delivery problems have written a script to monitor their subscriptions for them. Goody for them. Since I do not have recurring email delivery problems, there is no reason why I should go out of my way. And, interestingly enough, I'm not the only person this has happened to, and all you can do is blame every single one of them for having "recurring email delivery problems." When are you going to realize there is a problem and admit it? When are you going to get it _fixed_? Or is your life easier if there is nobody on any of the lists? 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
freebsd-uthread.c
In three places in your code you do the following or something similar: ptr = (CORE_ADDR) cached_pthread.nxt; struct pthread has no member nxt in either -current or -stable and your patch did not add it to pthread_private.h What did you mean for this to be? Thanks. -Kip To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
3.3RC install errors
I am sorry if I am repeating something that has already been fixed - I just did buildworld which completed without errors - however, when I did installworld it ended with the following: snip vm/vm_object.h - vm/vm_object.ph vm/vm_page.h - vm/vm_page.ph vm/vm_pageout.h - vm/vm_pageout.ph vm/vm_pager.h - vm/vm_pager.ph vm/vm_param.h - vm/vm_param.ph vm/vm_prot.h - vm/vm_prot.ph vm/vm_zone.h - vm/vm_zone.ph vm/vnode_pager.h - vm/vnode_pager.ph *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 3.3RC install errors
Thanks, that fixed it.
-Kip
On Tue, 7 Sep 1999, Adam Strohl wrote:
I get this on 4.0-C its because of this thing in
gnu/usr.bin/perl/utils/h2ph if I remeber correctly. I just removed the
directory from the utils Makefile ("when in doubt comment it out") and
everything works, though I don't work with perl much.
That being said, I've held off mentioning it as I wasn't sure that it
wasn't due to an error on my part. 4.0-C has been doing this for the last
2-3 weeks, up until my last cvsup about 2 days ago.
Let me know if anyone needs more specific info/what you need, I'd be happy
to help.
- ( Adam Strohl ) -
- UNIX Operations/Systems http://www.digitalspark.net -
- adams (at) digitalspark.netxxx.xxx. x -
- ( DigitalSpark.NET )--- -
On Tue, 7 Sep 1999, Kip Macy wrote:
I am sorry if I am repeating something that has already been fixed -
I just did buildworld which completed without errors - however, when I did
installworld it ended with the following:
snip
vm/vm_object.h - vm/vm_object.ph
vm/vm_page.h - vm/vm_page.ph
vm/vm_pageout.h - vm/vm_pageout.ph
vm/vm_pager.h - vm/vm_pager.ph
vm/vm_param.h - vm/vm_param.ph
vm/vm_prot.h - vm/vm_prot.ph
vm/vm_zone.h - vm/vm_zone.ph
vm/vnode_pager.h - vm/vnode_pager.ph
*** Error code 1
Stop.
*** Error code 1
Stop.
*** Error code 1
Stop.
*** Error code 1
Stop.
*** Error code 1
Stop.
*** Error code 1
Stop.
*** Error code 1
Stop.
*** Error code 1
Stop.
*** Error code 1
Stop.
*** Error code 1
Stop.
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
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: gdb-4.17 in FreeBSD 4.0-CURRENT
I tried doing the same on FreeBSD 3.2-STABLE but when I run it it complains that it is unable to find dynamic linker breakpoint function and then it stops with a SIGTRAP. Any ideas what might be wrong? Thanks. -Kip On Fri, 20 Aug 1999, Richard Cownie wrote: I managed to build gdb-4.17 in FreeBSD 4.0, here's how to do it: 1) gdb-4.17/configure --host=i386-unknown-freebsdelf4.0 Have to specify the host explicitly, otherwise it doesn't realize it needs to use ELF. 2) in gdb-4.17/Makefile, add "-DSVR4_SHARED_LIBS" to definition of CFLAGS 3) in gdb-4.17/gdb/solib.c, add #include "elf/common.h" (after #include "elf/external.h") 4) in gdb-4.17/gdb/infptrace.c, add #define U_REGS_OFFSET 0x1fa8 I figured out this number the hard way by searching all the valid PT_READ_U addresses and comparing the results with PT_GETREGS - found locations where eip and esp values matched up. Doubtless there's a better way to get the right value. Then it should all build (and perhaps work). The same hacks probably apply to gdb-4.18 and gdb-current (but so far gdb-4.17 is the most useful version I've seen for debugging C++). Richard Cownie ([EMAIL PROTECTED]) 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: gdb-4.17 in FreeBSD 4.0-CURRENT
on 3.2-R gdb-4.18 will core dump without fail when I try to read a core file generated by the C++ program I am developing - gdb-4.17 does not have this problem. -Kip On Tue, 31 Aug 1999, Alex Zepeda wrote: On Sun, 22 Aug 1999, Richard Cownie wrote: On Sat, 21 Aug 1999, David O'Brien wrote: Are you saying 4.17 is better than 4.18 for debugging C++? Or are you saying you didn't know FreeBSD comes with gdb: gdb-4.18 is badly broken on all platforms (at least for C++). You can't call methods from the gdb command line, and also it frequently freezes to the point where you have to kill the window. gdb-4.17 is much better for C++. Really? I don't use gdb much so, I wouldn't know, but I've seen reports that KOffice is undebugable with 4.17 (gdb segfaults), but is with 4.18. Hmm. - alex 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
