Date: Tue, 27 Mar 2001 22:27:40 +0200 From: Mark Murray <mark@grondar.za> To: John Baldwin <jhb@FreeBSD.org> Cc: obrien@FreeBSD.org, alpha@FreeBSD.org, Andrew Gallatin <gallatin@cs.duke.edu> Subject: Re: dump(8) (vfs_object_create() panics: found the problem) Message-ID: <200103272026.f2RKQTf80723@gratis.grondar.za> In-Reply-To: <XFMail.010327115639.jhb@FreeBSD.org> ; from John Baldwin <jhb@FreeBSD.org> "Tue, 27 Mar 2001 11:56:39 PST." References: <XFMail.010327115639.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Ok, as I said earlier, only the pointer to the vnop function table is > spammed, the rest of the vnode is ok. I tracked this down to the big > /dev/random overhaul commits of March 11. Removing 'device random' > from my kernel gets rid of the panic but breaks ssh. :( A kernel just > before the Mar 11 /dev/random commits boots fine, and one just after > panics. :( Hopefully Mark can trace down where the data corruption is > coming from. I'm willing to test any patches. Very weird. Please comment out all the *rijndael* function calls in hash.c and see if that fixes anything? (I'm suspecting a stack-smash in the rijndael encryption routines). M -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200103272026.f2RKQTf80723>