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 an assembler symbol related to > simplelock()), but this isn't of much help. Actually, this info was from Lester Igo, not Viren. Sorry for the misattributation. Eivind. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- repeatable crash in -current (softupdates, NFS) Viren R.Shah
- Re: repeatable crash in -current (softupdates, NFS) Eivind Eklund
- Re: repeatable crash in -current (softupdates, NF... Lester Igo
- Re: repeatable crash in -current (softupdates, NF... Viren R.Shah
- Re: repeatable crash in -current (softupdates... Matthew Dillon
- Re: repeatable crash in -current (softupd... Eivind Eklund
- Re: repeatable crash in -current (so... Eivind Eklund
- Re: repeatable crash in -current (so... Matthew Dillon
- Re: repeatable crash in -current... Matthew Dillon
- Re: repeatable crash in -cur... Viren R.Shah
- Re: repeatable crash in -cur... Viren R.Shah
- Re: repeatable crash in -cur... Matthew Dillon
- Re: repeatable crash in -current (softupdates, NFS) Greg Lehey
- Re: repeatable crash in -current (softupdates, NF... Viren R.Shah
- Re: repeatable crash in -current (softupdates... Matthew Dillon
- Re: repeatable crash in -current (softupd... Julian Elischer
- Re: repeatable crash in -current (so... Matthew Dillon
