Re: is it possible to have a NULL procp for an NFS request?

:Matthew Jacob <[EMAIL PROTECTED]> writes: :> Hmm. The client wasn't following symlinks. : :You sure? What happens is when you queue up an nfs operation provoked :by following a symlink. I couldn't figure any other way of making :that happen. : :> The patch seems simple enough, but it probably

Re: is it possible to have a NULL procp for an NFS request?

I'm pretty sure that the server had no symlinks in that filesystem. On 23 Dec 2000, Assar Westerlund wrote: > Matthew Jacob <[EMAIL PROTECTED]> writes: > > Hmm. The client wasn't following symlinks. > > You sure? What happens is when you queue up an nfs operation provoked > by following a sym

Re: is it possible to have a NULL procp for an NFS request?

Matthew Jacob <[EMAIL PROTECTED]> writes: > Hmm. The client wasn't following symlinks. You sure? What happens is when you queue up an nfs operation provoked by following a symlink. I couldn't figure any other way of making that happen. > The patch seems simple enough, but it probably shouldn't

Re: is it possible to have a NULL procp for an NFS request?

Hmm. The client wasn't following symlinks. The patch seems simple enough, but it probably shouldn't just swallow the error. It looks like the last phk simplification lost some of the functionality of the previous code- that I can fix. On 23 Dec 2000, Assar Westerlund wrote: > Matthew Jacob <

Re: is it possible to have a NULL procp for an NFS request?

Matthew Jacob <[EMAIL PROTECTED]> writes: > I had a panic just now: > > db> t > tprintf() at tprintf+0x7c > nfs_msg() at nfs_msg+0x28 > nfs_timer() at nfs_timer+0x1fc > softclock() at softclock+0x4f4 > sithd_loop() at sithd_loop+0x18c > exception_return() at exception_return Yes, this is possibl

is it possible to have a NULL procp for an NFS request?

I had a panic just now: db> t tprintf() at tprintf+0x7c nfs_msg() at nfs_msg+0x28 nfs_timer() at nfs_timer+0x1fc softclock() at softclock+0x4f4 sithd_loop() at sithd_loop+0x18c exception_return() at exception_return This is where it's saying the server isn't responding... and as best as I can

Repeatable Hang -current SMP and lpd

I tried to post this before, but, I think it got lost. I have a repeatable hang with -current when attempting to print a region from emacs. This happened after 2 1/2 days uptime. The system is frozen. The mouse does not move the pointer. The keyboard does nothing - pressing Caps Lock does not

New PCM changes cause panic

New changes to the sound system PCM cause a panic on current kernel when using the rsynth port. Fatal trap 18: integer divide fault while in kernel mode cpuid = 1; lapic.id = 0c00 instruction pointer = 0x8:0xc01714d1 stack pointer = 0x10:0xcb06fd90 frame pointer = 0x10

bridge code doesn't work like the man page says

>Submitter-Id: current-users >Originator: Joost Bekkers >Organization: >Confidential: no >Synopsis: bridge/firewall doesn't work as in bridge(4) >Severity: serious >Priority: medium >Category: kern >Release:FreeBSD 4.2-RELEASE i386 >Class: sw-b

$B!V%a!<%k%"%I%l%9G/Kv%-%c%s%Z!<%s!W(B

$BFMA3$N%a!<%k@?$K<:NiCW$7$^$9(B $B6=L#$r$*;}$A$G$J$$>l9g$O!"@?$K62$lF~$j$^$9$,!":o=|$/$@$5$$(B $B$"$J$?$N!"%$%s%?!<%M%C%H%S%8%M%9$,!"$h$jHtLv$9$k$3$H$NpJs$rAw$i$;$F$$$?$@$-$^$7$?(B $B%$%s%?!<%M%C%H%a!<%k$O(B,$B$3$l$+$i$N%S%8%M%9$r?d?J$7$F$$$/$N$K(B $BI,MWIT2D7g$J$b$N$G$9!#(B $B%S%8

ffs_valloc: dup alloc panics with stable/current

Tomi Vainio - Sun Finland - writes: > > We got old Mylex DAC960PD-Ultra-raid-adapter and have tried to use it > with FreeBSD 4.2-stable and 5.0-current. Adapter is configured with > three luns 5+5*9G, 8+8*9G (raid5) and 1+1*2G (mirrored boot disk). > All 9G disks are quite old Seagate Barrac