i386 tinderbox failure
To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: could sleep with "pcm0:play:0" locked
> > I got this message (after fifo fix kernel): > > May 21 13:54:35 waterblue kernel: ../../../vm/uma_core.c:1324: could sleep wi th "pcm0:play:0" locked from ../../../dev/sound/pcm/dsp.c:734 Me to. Also, starting XFree causes a panic. -Seth To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: multi default routes in freebsd !?
Oleg Chebotarev wrote: > Does anyone know when FreeBSD will > support multiple default routes > or multiple routes to the same network thru different interfaces? I have two default routes. One is IP address "A". The other is IP address "B". To which IP address do I forward a random packet? Shouldn't you just use BGP instead? That's what it was designed to support. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
rio500 usb support
I just started playing w/ this. While it seems to work, connecting the rio, disconnecting it, and then reconnecting causes a panic when it trys to re-make the /dev entry. I don't see a usb mailing list, so where should I take this? -Seth To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
could sleep with "pcm0:play:0" locked
I got this message (after fifo fix kernel): May 21 13:54:35 waterblue kernel: ../../../vm/uma_core.c:1324: could sleep with "pcm0:play:0" locked from ../../../dev/sound/pcm/dsp.c:734 May 21 13:54:35 waterblue kernel: ../../../vm/uma_core.c:1324: could sleep with "pcm0:play:0" locked from ../../../dev/sound/pcm/dsp.c:690 May 21 13:54:35 waterblue kernel: ../../../vm/uma_core.c:1324: could sleep with "pcm0:play:0" locked from ../../../dev/sound/pcm/dsp.c:765 May 21 13:54:35 waterblue kernel: ../../../vm/uma_core.c:1324: could sleep with "pcm0:play:0" locked from ../../../dev/sound/pcm/dsp.c:353 May 21 13:55:00 waterblue kernel: ../../../vm/uma_core.c:1324: could sleep with "process lock" locked from ../../../kern/kern_prot.c:511 May 21 13:55:00 waterblue kernel: ../../../vm/uma_core.c:1324: could sleep with "process lock" locked from ../../../kern/kern_prot.c:613 -- Jun Kuriyama <[EMAIL PROTECTED]> // IMG SRC, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
multi default routes in freebsd !?
Does anyone know when FreeBSD will support multiple default routes or multiple routes to the same network thru different interfaces? Thank you, Oleg __ Do You Yahoo!? LAUNCH - Your Yahoo! Music Experience http://launch.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: src/sys/crypto/missing
On Mon, May 20, 2002 at 09:46:06PM +0200, Martin Kacerovsky wrote: > Hi, > I've just CVSUPed sources of kernel (I had a snapshot) and there's no > crypto directory in src/sys and make writes error : > > make: don't know how to make /usr/src/sys/crypto/rijndael/rijndael-alg-fst.c. Stop > > what should I do? copy the old crypto directory into new source tree ? > or is the mistake somewhere else? You're using an incomplete cvsupfile. Kris msg38596/pgp0.pgp Description: PGP signature
src/sys/crypto/missing
Hi, I've just CVSUPed sources of kernel (I had a snapshot) and there's no crypto directory in src/sys and make writes error : make: don't know how to make /usr/src/sys/crypto/rijndael/rijndael-alg-fst.c. Stop what should I do? copy the old crypto directory into new source tree ? or is the mistake somewhere else? Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: tcsh
On 2002-05-19 20:34, Riccardo Torrini wrote:
> On 19-May-2002 (18:27:40/GMT) Riccardo Torrini wrote:
>
> > I have "set implicitcd". But it would be honoured only when a
> > directory is specified on a line itself, not after a pipe (IMHO).
>
> Or (even better), when a directory is followed by a "/" ?
It's all a matter of what `implicit' means to you, I guess.
By adding a slash ("/") you're making it a tiny bit `explicit' IMHO :)
--
Giorgos Keramidas- http://www.FreeBSD.org
[EMAIL PROTECTED] - The Power to Serve
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: SRA login failed -- bug?
Marcel Moolenaar writes: > > I see this as well - on both -STABLE and -CURRENT. I do you have two > > accounts you can try? I generally find that while the SRA login will > > refuse one account, a different account can log in fine, without > > reconnecting the telnet. > > Ok, now that I have confirmation, I'll see if I can zoom in on the > problem. Does anybody have a informed opinion as to where to start: > server or client? I haven't seen this for a while because I started using ssh exclusively a while back -- so this info may be out of date... but when I did see it, ISTR that there was often an error message on the server.. -Archie __ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SRA login failed -- bug?
On Mon, May 20, 2002 at 09:35:31AM +0100, Gavin Atkinson wrote: > > I see this as well - on both -STABLE and -CURRENT. I do you have two > accounts you can try? I generally find that while the SRA login will > refuse one account, a different account can log in fine, without > reconnecting the telnet. I have multiple accounts, but have not tried to login with another user while the first "locks". For some reason I never saw a reason to think it had a more global effect. And yes, I do see it on -stable as well (forgot to mention). Ok, now that I have confirmation, I'll see if I can zoom in on the problem. Does anybody have a informed opinion as to where to start: server or client? -- Marcel Moolenaar USPA: A-39004 [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[no subject]
subscribe freebsd-current To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
nbuf calculation broken (was: deadlock waiting for newbuf)
nbuf on that 256M machine is only 50.
All other values depend on it.
If have neither configure NBUF in my kernconfig nor do I have set
kern.nbuf in loader(8).
In sys/kern/vfs_bio.c kern_vfs_bio_buffer_alloc() we have:
if (nbuf == 0) {
int factor = 4 * BKVASIZE / 1024;
nbuf = 50;
if (physmem_est > 4096)
nbuf += min((physmem_est - 4096) / factor,
65536 / factor);
if (physmem_est > 65536)
nbuf += (physmem_est - 65536) * 2 / (factor * 5);
if (maxbcache && nbuf > maxbcache / BKVASIZE)
nbuf = maxbcache / BKVASIZE;
}
BKVASIZE should be OK.
That means physmem_est must be < 4096 when kern_vfs_bio_buffer_alloc()
is called.
This points to vm_ksubmap_init() or below.
--
B.Walter COSMO-Project http://www.cosmo-project.de
[EMAIL PROTECTED] Usergroup [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: SRA login failed -- bug?
In article <[EMAIL PROTECTED]>, Marcel Moolenaar <[EMAIL PROTECTED]> wrote: > I sometimes cannot get passed SRA secure login, even though credentials > are given correctly: > > Connected to athlon.pn.xcllnt.net. > Escape character is '^]'. > Trying SRA secure login: > User (marcel): > Password: > [ SRA login failed ] > : > (repeat last 3 lines -- Ad nauseam) > > The problem is not a faulty password or username, but appears to be > something that behaves much the same as uninitialized variables. > Most of the time SRA secure login works ok, but it does occasionally > reject the login. It is not possible to login at all when SRA rejects > a login. It's a permanent state and the only way around it is to > ^C and re-telnet, which BTW occasionally fails as well... > > I haven't seen anything on this topic, so I'd like to hear if > others are experiencing this as well and if this is a security > "feature", a bug or misconfiguration. Yes, I see this sometimes too, even in -stable. I agree with your conjecture -- it acts like there's an uninitialized variable that sometimes starts out with an unworkable value. John -- John Polstra John D. Polstra & Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: deadlock waiting for newbuf
On Mon, May 20, 2002 at 03:37:26PM +0200, Bernd Walter wrote: > ~Stopped at siointr1+0x174: br zero,siointr1+0x2dc > db> ps > pid proc addruid ppid pgrp flag stat wmesg wchan cmd > 338 fe0007450b10 fe000746c0000 229 229 000 3 newbuf >fc578cd4 sshd [...] > This happened with source from today on alpha (PC164/ev56). > I had not enough space for a crashdump and will add a new disk later > today. How got the values that low? This is a 256M PC164 current from today [62]cicely9# sysctl vfs | grep dirty vfs.numdirtybuffers: 8 vfs.lodirtybuffers: 8 vfs.hidirtybuffers: 16 This is on a NoName running 11th may -current with only 64M: [52]cicely10> sysctl vfs | grep dirty vfs.numdirtybuffers: 5 vfs.lodirtybuffers: 132 vfs.hidirtybuffers: 264 -- B.Walter COSMO-Project http://www.cosmo-project.de [EMAIL PROTECTED] Usergroup [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new zero copy sockets patches available
Kenneth D. Merry writes: > > As a related question, will this work with the broadcom gigabit (bge) > > driver, which is the Tigon III? If not, what would it take to get > > it working? > > Unfortunately, it won't work with the Tigon III. > > If you can get firmware source for the Tigon III, I can probably get header > splitting working. (The only way it wouldn't work is if they've offloaded > most of the packet processing into the hardware.) I don't want this to sound too much like an advertisement, but since I now work for Myricom, I feel obligated to point out that the other adapters that this can be made to work with are Myricom Myrinet interfaces (*) Anyway, if this gets committed, I will enhance the Myricom GM-2 firmware to support page-flipping receives. I think my boss will approve the work. With FreeBSD & gm-2, we now see roughly 1.8Gb/sec from iperf, but the receiver's CPU is maxed out. It would be nice to have some room left over to actually do something with the data ;) > The send side code will work on any NIC, and you can kludge up special case > header splitting on the receive side if the NIC allows you to break jumbo > frames into multiple chunks of data. (This is what Drew originally did for > the Tigon II -- you just size the initial chunk of data so that it'll just > hold the ethernet header, IP header, TCP header and TCP options, and the > payload will "magically" end up page aligned. This doesn't work for > protocols other than TCP, and it won't work if your TCP header changes in > length.) This mostly doesn't work for TCP at all. It does work for the client-side zero-copy NFS read-response work I did where I page-flip the received frame into the buffer cache. This was something of a hack, because I don't actually parse the rpcs, I just guess that the data starts at a certain offset into the packet (which it does, 99% of the time). Cheers, Drew (*) 2Gb/sec + 2Gb/sec. See http://www.myri.com/myrinet/product_list.html. Before your jaw hits the floor at the price per adapter, take into account how cheap the switches are when compared to high-density gigabit ethernet switches. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new zero copy sockets patches available
Terry Lambert writes: > To do the work, you'd have to do it on your own, after licensing > the firmware, after signing an NDA. Unlike the rather public > Tigon II firmware, the Tigon III doesn't have a lot of synergy > or interesting work going for it. Most people doing interesting > work tend to use Tigon II cards, because of this. It also requires a good contact at Broadcom. Some people I know at another institution are willing to sign an NDA and still cannot get the firmware from Broadcom. Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
can't install current on Viao FX-290
Hi all, I'm a FreeBSD veteran, but -current newbie. I can't seem to install it on my laptop. I've downloaded the developer release, and several current.freebsd.jp iso's, and for every one, they won't recognize my cdrom. It is a UDJA710 according to my -stable dmesg. I am using a triple boot hd, Win2k, -stable, and hopefully someday -current on ad0s3. I also have Plug and Play turned off in my bios. Is there a way to print out that dmesg from the iso boots? I'm sure thats the only way you can help. I also tried installing via FTP, but after connecting to an ftp server, it claims not to be able to download any of the components. I get an individual error message for each component of the install. Thanks, Rob. -- - The Numeric Python EM Project www.pythonemproject.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
deadlock waiting for newbuf
~Stopped at siointr1+0x174: br zero,siointr1+0x2dc db> ps pid proc addruid ppid pgrp flag stat wmesg wchan cmd 338 fe0007450b10 fe000746c0000 229 229 000 3 newbuf fc578cd4 sshd 337 fe0007451098 fe000745a0000 263 8 0004000 3 newbuf fc578cd4 thttpd 336 fe0007451620 fe00074520000 335 336 010 3 newbuf fc578cd4 cron 335 fe00071af098 fe00074360000 224 224 000 3 ppwait fe00071af098 cron 334 fe00071af620 fe000742c0000 0 0 204 3 nfsidl fc5d7e30 nfsiod 19 333 fe0007304000 fe00074240000 0 0 204 3 nfsidl fc5d7e28 nfsiod 18 332 fe0007304588 fe000741c0000 0 0 204 3 nfsidl fc5d7e20 nfsiod 17 331 fe0007304b10 fe00074140000 0 0 204 3 nfsidl fc5d7e18 nfsiod 16 330 fe0007305098 fe000740c0000 0 0 204 3 nfsidl fc5d7e10 nfsiod 15 329 fe0007305620 fe00074040000 0 0 204 3 nfsidl fc5d7e08 nfsiod 14 328 fe0007306000 fe00073fc0000 0 0 204 3 nfsidl fc5d7e00 nfsiod 13 327 fe0007306588 fe00073f40000 0 0 204 3 nfsidl fc5d7df8 nfsiod 12 326 fe0007306b10 fe00073ec0000 0 0 204 3 nfsidl fc5d7df0 nfsiod 11 325 fe0007307098 fe00073e40000 0 0 204 3 nfsidl fc5d7de8 nfsiod 10 324 fe0007307620 fe00073dc0000 0 0 204 3 nfsidl fc5d7de0 nfsiod 9 323 fe0007308000 fe000730a0000 0 0 204 3 nfsidl fc5d7dd8 nfsiod 8 322 fe0006488b10 fe0006ea20000 0 0 204 3 nfsidl fc5d7dd0 nfsiod 7 321 fe00071ae000 fe00071c40000 0 0 204 3 nfsidl fc5d7dc8 nfsiod 6 320 fe00071ad098 fe00071dc0000 0 0 204 3 nfsidl fc5d7dc0 nfsiod 5 319 fe00071ac000 fe00071f40000 0 0 204 3 nfsidl fc5d7db8 nfsiod 4 318 fe0007118000 fe000711e0000 279 318 0004002 3 newbuf fc578cd4 mv 279 fe0007119620 fe00071fc0000 277 279 2004002 3 pause fe00071fc000 tcsh 277 fe00071acb10 fe00071e4000 1007 273 277 2004002 3 pause fe00071e4000 tcsh 273 fe0007118b10 fe00072160000 229 229 100 3 select fc5d0da0 sshd 272 fe0007118588 fe000721e0000 1 272 0004002 3 flswai fc578cd4 getty 263 fe00071ae588 fe00071bc0000 1 8 0004002 3wait fe00071ae588 sh 235 fe00071ac588 fe00071ec000 25 1 235 2000100 3 pause fe00071ec000 sendmail 232 fe00071ad620 fe00071d20000 1 232 100 3 select fc5d0da0 sendmail 229 fe00071aeb10 fe00071b40000 1 229 000 3 select fc5d0da0 sshd 227 fe0007116000 fe000714a0000 1 227 000 3 select fc5d0da0 lpd 224 fe0007116588 fe00071420000 1 224 000 3 nanslp fc578968 cron 222 fe0007114000 fe00071760000 1 222 000 3 select fc5d0da0 inetd 217 fe0007117098 fe0007131 1 217 100 3 newbuf fc578cd4 rwhod 214 fe0007115620 fe00071540000 213 213 100 3 select fc5d0da0 rpc.lockd 213 fe0007115098 fe000715c0000 1 213 000 3 select fc5d0da0 rpc.lockd 211 fe0007114588 fe000716e0000 1 211 000 3 select fc5d0da0 rpc.statd 210 fe0007114b10 fe00071640000 205 205 100 3 select fc5d0da0 rpc.lockd 205 fe0007116b10 fe000713a0000 1 205 000 3 select fc5d0da0 rpc.lockd 203 fe0007117620 fe00071280000 1 203 000 3 select fc5d0da0 rpc.statd 201 fe0006eda588 fe0006ef40000 197 197 000 3nfsd fe00070dbc00 nfsd 200 fe0006ed1098 fe0006f1e0000 197 197 000 3nfsd fe0007104000 nfsd 199 fe0006488588 fe0006ebc0000 197 197 000 3nfsd fe0007103400 nfsd 198 fe0006edb098 fe0006ee40000 197 197 000 3nfsd fe0007102e00 nfsd 197 fe0006eda000 fe0006efc0000 1 197 000 3 select fc5d0da0 nfsd 195 fe0006ed0b10 fe0006f260000 1 195 000 3 select fc5d0da0 mountd 191 fe0006ed1620 fe0006f040000 1 191 000 3 newbuf fc578cd4 ypbind 189 fe0006ed fe0006f3a0000 1 189 000 3 select fc5d0da0 rpcbind 186 fe0006edb620 fe0006edc0000 1 186 000 3 select fff
Re: Perl script rewrites - progress (2)
[...] > ### > Extracting splain (with variable substitutions) > ../miniperl -I../lib perlcc.PL > Extracting perlcc (with variable substitutions) > ../miniperl -I../lib dprofpp.PL > Extracting dprofpp (with variable substitutions) > > Making x2p stuff > make: don't know how to make . Stop > *** Error code 2 > > Stop in /usr/ports/lang/perl5/work/perl-5.6.1. > *** Error code 1 > > Stop in /usr/ports/lang/perl5. > ### [...] > No more perl in the base, perl in ports don't build. Hmmm Who said > there wasn't a conspiracy against perl? :-) [...] I'm facing the same problem compiling perl from ports, but I still have perl in the base system -- i t h a s t o s t a r t s o m e w h e r e i t h a s t o s t a r t s o m e t i m e w h a t b e t t e r p l a c e t h a n h e r e w h a t b e t t e r t i m e t h a n n o w msg38583/pgp0.pgp Description: PGP signature
lock order reversal (process lock @ kern_exec.c)
Here is a message of lock order reversal (just fresh current): lock order reversal 1st 0xe853eb18 process lock (process lock) @ ../../../kern/kern_exec.c:316 2nd 0xc0324400 filelist lock (filelist lock) @ ../../../kern/kern_descrip.c:1112 -- Jun Kuriyama <[EMAIL PROTECTED]> // IMG SRC, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SRA login failed -- bug?
On Sun, 19 May 2002, Marcel Moolenaar wrote: > I sometimes cannot get passed SRA secure login, even though credentials > are given correctly: > > Connected to athlon.pn.xcllnt.net. > Escape character is '^]'. > Trying SRA secure login: > User (marcel): > Password: > [ SRA login failed ] > : > (repeat last 3 lines -- Ad nauseam) > > I haven't seen anything on this topic, so I'd like to hear if > others are experiencing this as well and if this is a security > "feature", a bug or misconfiguration. I see this as well - on both -STABLE and -CURRENT. I do you have two accounts you can try? I generally find that while the SRA login will refuse one account, a different account can log in fine, without reconnecting the telnet. I'm glad someone else has seen this, i thought i was going mad... Gavin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
