On Mon, 29 Nov 1999, Matthew Dillon wrote:
>
> :
> :>
> :> makeoptions DEBUG="-g"
> :>
> :Easier option..
> :config -g
>
> Actually no. How many people remember to type options after 'config' ?
> Especially if you are juggling more then one kernel config, trying to
> reme
:I compiled a kernel with it, and no panic!! Here's what I get instead:
:
:[vshah@jabberwock] ~> rm index.html
:rm: index.html: No such file or directory
:2220 [6:41pm]
:[vshah@jabberwock] ~> ln -s public_html/index.html ./index.ht
Matt> I've added a little cleanup to this patch. Viren, please try this
Matt> patch.
I compiled a kernel with it, and no panic!! Here's what I get instead:
[vshah@jabberwock] ~> rm index.html
rm: index.html: No such file or directory
2220 [6:41pm]
> "Matt" == Matthew Dillon <[EMAIL PROTECTED]> writes:
Matt> I've added a little cleanup to this patch. Viren, please try this
Matt> patch.
Matt> -Matt
Matt> Matthew Dillon
Matt>
:I think I (well, Alfred Perlstein) have found what the problem is - in
:nfs_symlink, newvp isn't initialized for NFSv2. Unfortunately, I have
:zero clue about how to fix that - Alfred believes the checks for NFSv3
:may not be necessary - myself, I find the NFS code almost totally
:incomprehensi
:> Eivind, I'm not sure that change you made is legal. People use
:> symlink creation the same way they use O_EXCL file creation - as a
:> locking mechanism. In fact, in NFSv2 O_EXCL file creation is not
:> atomic (I'm pretty sure) and symlink was the *only* method available.
:
:
:OK, here's a -current system from today (11/29) morning [4am EST] with
:kernel compiled with DDB and -g.
:
:Tried doing a simple symlink over a NFS mounted filesystem:
:
:fatal trap 12: page fault while in kernel mode
:fault virtual address = 0x4
:fault code= supervisor read, page no
On Mon, Nov 29, 1999 at 11:56:31PM +0100, Eivind Eklund wrote:
> I've been peering over the code, and I am unable to find anything
> wrong :-( I've also gotten panic information and symbol information
> from Viren, but this hasn't made me any wiser - the failure was in
> setlock (which seems to be
On Mon, Nov 29, 1999 at 01:52:29PM -0800, Matthew Dillon wrote:
> :
> : Eivind> I *think* I know what this is due to - please upgrade
> : Eivind> src/sys/nfs/nfs_vnops.c to revision 1.146 (which I just
> : Eivind> committed) and try again.
> :
> :Tried it. Doesn't work. :-( It still crashes when c
> "Matt" == Matthew Dillon <[EMAIL PROTECTED]> writes:
Matt> The problem is a NULL pointer dereference somewhere... please
Matt> nm your kernel binary and extract out all elements with c0163
Matt> in them. e.g. nm /kernel | fgrep c0163 | sort.
OK, here's a -current system f
:
:>
:> makeoptions DEBUG="-g"
:>
:Easier option..
:config -g
Actually no. How many people remember to type options after 'config' ?
Especially if you are juggling more then one kernel config, trying to
remember which ones you intend to compile -g and which ones you don't
>
> makeoptions DEBUG="-g"
>
Easier option..
config -g
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
:not having DDB compiled into the kernel I can't answer that. However
:I'm willing to give any suggestions a go.
:
: >> [BTW: the server hasn't crashed, it's only the FreeBSD client that
: >> crashes]
:
: Greg> Do you mean the client process or the client operating system?
:
:The client OS -- imme
:
: Eivind> I *think* I know what this is due to - please upgrade
: Eivind> src/sys/nfs/nfs_vnops.c to revision 1.146 (which I just
: Eivind> committed) and try again.
:
:Tried it. Doesn't work. :-( It still crashes when creating a symbolic
:link on a NFS mounted filesystem. [This is unfortunate i
> "Greg" == Greg Lehey <[EMAIL PROTECTED]> writes:
Greg> On Saturday, 27 November 1999 at 10:26:15 -0500, Viren R.Shah wrote:
>>
>> I'm running a -current system from Nov 26th (approx 4am EST).
>>
>> I can currently reliably crash the system by doing:
>>
>> ln -s /home/users/vshah/p
> "Eivind" == Eivind Eklund <[EMAIL PROTECTED]> writes:
Eivind> On Sat, Nov 27, 1999 at 10:26:15AM -0500, Viren R.Shah wrote:
>>
>> I'm running a -current system from Nov 26th (approx 4am EST).
>>
>> I can currently reliably crash the system by doing:
>>
>> ln -s /home/users/vshah/p
On Saturday, 27 November 1999 at 10:26:15 -0500, Viren R.Shah wrote:
>
> I'm running a -current system from Nov 26th (approx 4am EST).
>
> I can currently reliably crash the system by doing:
>
> ln -s /home/users/vshah/public_html/index.html /home/users/vshah/index.html
>
>
> The crash only works
On Sat, 27 Nov 1999, Eivind Eklund wrote:
> On Sat, Nov 27, 1999 at 10:26:15AM -0500, Viren R.Shah wrote:
> >
> > I'm running a -current system from Nov 26th (approx 4am EST).
> >
> > I can currently reliably crash the system by doing:
> >
> > ln -s /home/users/vshah/public_html/index.html /ho
On Sat, Nov 27, 1999 at 10:26:15AM -0500, Viren R.Shah wrote:
>
> I'm running a -current system from Nov 26th (approx 4am EST).
>
> I can currently reliably crash the system by doing:
>
> ln -s /home/users/vshah/public_html/index.html /home/users/vshah/index.html
>
>
> The crash only works w
I'm running a -current system from Nov 26th (approx 4am EST).
I can currently reliably crash the system by doing:
ln -s /home/users/vshah/public_html/index.html /home/users/vshah/index.html
The crash only works when I do it on a NFS mounted filesystem. I'm
using NFSv2/UDP. The server is a 3.
20 matches
Mail list logo
