Re: Searching for users of netncp and nwfs to help debug 5.0 problems
Martijn Pronk wrote: Robert Watson wrote: The build of netncp is currently broken on 5.0-CURRENT, and I'd like to see this fixed before 5.0-RELEASE. Unfortunately, we're having a lot of trouble finding a test environment, which is the natural and immediate follow-on to the compile fixes :-). Was wondering if anyone with FreeBSD kernel debugging experience and some time on their hands was interested in helping resolve this issue over the next week or two. I can test this next week at work, however, I don't normally use netncp nwfs, so it may take me a while. I'll get back on this next week. I tried to build a kernel with options IPX, NCP and NWFS, but it failed with the following error: cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I. -I/home/src/sys -I/home/src/sys/dev -I/home/src/sys/contrib/dev/acpica -I/home/src/sys/contrib/ipfilter -D_KERNEL -include opt_global.h -fno-common -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding /home/src/sys/netncp/ncp_conn.c In file included from /home/src/sys/netncp/ncp_conn.c:46: /home/src/sys/netncp/ncp_conn.h:174: field `nc_lock' has incomplete type /home/src/sys/netncp/ncp_conn.h:193: confused by earlier errors, bailing out *** Error code 1 I guess struct lock can't be found. I hope someone can do something with this. HTH, Martijn To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Searching for users of netncp and nwfs to help debug 5.0 problems
Nate Lawson wrote: On Tue, 26 Nov 2002, Hiten Pandya wrote: On Tue, Nov 26, 2002 at 08:10:50PM +0100, Martijn Pronk wrote the words in effect of: In file included from /home/src/sys/netncp/ncp_conn.c:46: /home/src/sys/netncp/ncp_conn.h:174: field `nc_lock' has incomplete type /home/src/sys/netncp/ncp_conn.h:193: confused by earlier errors, bailing out *** Error code 1 I guess struct lock can't be found. I hope someone can do something with this. Once you change the sys/lock.h line in ncp_conn.h to sys/lockmgr.h, you will see a lot of struct proc related errors springing up. The motto of this message is, that fixing that line will not make it compile. We need to make sys/netncp use struct thread instead of struct proc. This is easy in some parts of the code, and on some its just a little tricky, but not hard. Somebody did update the prototypes to netncp, but forgot to change the logic, for lockmgr calls, example, its last argument is a struct thread etc. I was going to work on this task at one point in time, but now that my school exam timetable has changed, I will not be able to do it; for the next 2/3 months anyway. If someone wants to give a go at this task, then they are most welcome to take my place. I thought Julian volunteered to do this a while back. If he is not, I can pick this up and make it compile but I have no equipment to test it on. If you can at least make it compile then I can test it at my work. Can you tell me when you're done? Martijn To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Searching for users of netncp and nwfs to help debug 5.0 problems
Robert Watson wrote: The build of netncp is currently broken on 5.0-CURRENT, and I'd like to see this fixed before 5.0-RELEASE. Unfortunately, we're having a lot of trouble finding a test environment, which is the natural and immediate follow-on to the compile fixes :-). Was wondering if anyone with FreeBSD kernel debugging experience and some time on their hands was interested in helping resolve this issue over the next week or two. Hi Robert, I can test this next week at work, however, I don't normally use netncp nwfs, so it may take me a while. I'll get back on this next week. Martijn To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: rpc.lockd problems
Andrew P. Lentvorski wrote: Can you produce a packet trace for Kris? This would give him a known good trace so that he can point out the differences from his particular configuration, or, alternatively, he could file a bug report with the Linux folks. Ok, here is a but of output from tcpudmp, first is the locking of the file, later the unlocking of the file. (Beware, long lines ahead...) [This is when the locking begins-- I'm not sure if the RPC packets should be included...] 21:05:36.681339 dhcp157.in-10.sillywalks.org.49445 pluto.in-10.sillywalks.org.lockd: udp 196 (ttl 64, id 14737, len 224) 0x 4500 00e0 3991 4011 aa4c c0a8 0a9dE...9...@..L 0x0010 c0a8 0a42 c125 0fcd 00cc e277 3ddd 99f0...B.%.w=... 0x0020 0002 0001 86b5 0004 0x0030 0007 0001 0028 3dd7 f690...(=... 0x0040 0006 626f 656b 6a65 03e8boekje.. 0x0050 .. 21:05:36.684128 pluto.in-10.sillywalks.org.826 dhcp157.in-10.sillywalks.org.sunrpc: udp 84 (DF) (ttl 255, id 23949, len 112) 0x 4500 0070 5d8d 4000 ff11 87bf c0a8 0a42E..p].@B 0x0010 c0a8 0a9d 033a 006f 005c c339 b296 4aab.:.o.\.9..J. 0x0020 0002 0001 86a0 0002 0x0030 0003 0001 001c 3dd8 0492=... 0x0040 0005 706c 7574 6f00 pluto... 0x0050 21:05:36.685941 dhcp157.in-10.sillywalks.org.sunrpc pluto.in-10.sillywalks.org.826: [udp sum ok] udp 28 (ttl 64, id 14738, len 56) 0x 4500 0038 3992 4011 aaf3 c0a8 0a9dE..89...@... 0x0010 c0a8 0a42 006f 033a 0024 64b9 b296 4aab...B.o.:.$d...J. 0x0020 0001 0x0030 03d1 21:05:36.688612 pluto.in-10.sillywalks.org.825 dhcp157.in-10.sillywalks.org.977: udp 92 (DF) (ttl 255, id 23950, len 120) 0x 4500 0078 5d8e 4000 ff11 87b6 c0a8 0a42E..x].@B 0x0010 c0a8 0a9d 0339 03d1 0064 012b b296 4aac.9...d.+..J. 0x0020 0002 0001 86b5 0004 0x0030 000c 0001 001c 3dd8 0492=... 0x0040 0005 706c 7574 6f00 pluto... 0x0050 -- [The next part is when I close the file] -- 21:05:39.077292 dhcp157.in-10.sillywalks.org.49445 pluto.in-10.sillywalks.org.lockd: udp 180 (ttl 64, id 14742, len 208) 0x 4500 00d0 3996 4011 aa57 c0a8 0a9dE...9...@..W 0x0010 c0a8 0a42 c125 0fcd 00bc e1bd 3ddd 99f1...B.%..=... 0x0020 0002 0001 86b5 0004 0x0030 0009 0001 0028 3dd7 f693...(=... 0x0040 0006 626f 656b 6a65 03e8boekje.. 0x0050 .. 21:05:39.078515 pluto.in-10.sillywalks.org.825 dhcp157.in-10.sillywalks.org.977: udp 92 (DF) (ttl 255, id 12356, len 120) 0x 4500 0078 3044 4000 ff11 b500 c0a8 0a42E..x0D@B 0x0010 c0a8 0a9d 0339 03d1 0064 0026 b296 4aad.9...d...J. 0x0020 0002 0001 86b5 0004 0x0030 000e 0001 001c 3dd8 0494=... 0x0040 0005 706c 7574 6f00 pluto... 0x0050 - I hope this is enough info for you, if you need a real dump to look at yourself, just let me know, I'll put it online then. HTH, Martijn To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: rpc.lockd problems
Martijn Pronk wrote: My program is just anything that attempts to obtain a lock on a file on the NFS filesystem. vi does this when opening an existing file, as does mutt when opening a mailbox. Well, that sure simplifies the problem of running your program. ;) Thanks for the info, I will try that tonight after I get back home from the first day of the EuroBSDcon. OK, I tested it with a Solaris 8 NFS server with -current as a client, and locking does indeed work. (At least, vi didn't show the word UNLOCKED in the bottom line after I enabled rpc.lockd) However, I had some starting problems with rpc.lockd. Aparently it requires that rpc.statd also is running. Since I didn't had these things enabled in rc.conf, I started them manually. rpc.lockd quits silently without logging anything about what happened. The manualpage does mention that rpc.lockd typically runs in conjunction with rpc.statd As I don't see a direct requirement in this line, I didn't realize it was required. HTH, Martijn To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message