Bug 12884

Summary: Hot to panic FreeBSD-3.2-Release
Product: Base System Reporter: jhs <jhs>
Component: kernAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 3.2-RELEASE   
Hardware: Any   
OS: Any   

Description jhs freebsd_committer freebsd_triage 1999-07-30 09:50:01 UTC 
	How to panic the kernel:

Fix: 

Maybe AMD should at startup do
		chmod a-w o-w /a ; chown 0 /a
How-To-Repeat: 	amd -p -k i386 -l syslog -a /a /host /etc/amd.map # from rc.conf
	grep `hostname -s` /etc/exports # note removing hostname 
					# does not prevent a crash
	ln -s .. /a/`hostname -s`
	wall warn all users we are about to crash
	echo now see	panic: lockmgr: locking against myself
	ls /host/`hostname -s`	# panic occurs

	OK, it's silly to do
	 	ln -s .. /a/`hostname -s`
	but it's unfortunate that it panics.
		(I did the ln on a spare box while experimenting to try to
		find some way to have /host/* mount the other hosts,
		but /host/`hostname -s` just be root (or better "..")
		as I use sitewide addresses like /host/some_host/usr3/.....
		& I want the access to be a more efficient ufs direct
		in the one case where the  host happens to be local -
		I haven't found a solution to that yet BTW)
Comment 1 Søren Schmidt freebsd_committer freebsd_triage 2001-05-30 10:10:11 UTC 
State Changed
From-To: open->closed

This is belived to be fixed, upgrade and get back to us if problem still persists.