From owner-freebsd-alpha Tue Mar 27 12:26:42 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from gratis.grondar.za (grouter.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 47C3837B719; Tue, 27 Mar 2001 12:26:36 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (root@gratis.grondar.za [196.7.18.133]) by gratis.grondar.za (8.11.1/8.11.1) with ESMTP id f2RKQTf80723; Tue, 27 Mar 2001 22:26:32 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <200103272026.f2RKQTf80723@gratis.grondar.za> To: John Baldwin Cc: obrien@FreeBSD.org, alpha@FreeBSD.org, Andrew Gallatin Subject: Re: dump(8) (vfs_object_create() panics: found the problem) References: In-Reply-To: ; from John Baldwin "Tue, 27 Mar 2001 11:56:39 PST." Date: Tue, 27 Mar 2001 22:27:40 +0200 From: Mark Murray Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > 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