kern/181590: [vm] [panic] amd(8) related vm_page_unwire panics

Dominic Fandrey kamikaze at bsdforen.de
Mon Sep 2 07:20:02 UTC 2013


The following reply was made to PR kern/181590; it has been noted by GNATS.

From: Dominic Fandrey <kamikaze at bsdforen.de>
To: Peter Holm <peter at holm.cc>
Cc: bug-followup at FreeBSD.org
Subject: Re: kern/181590: [vm] [panic] amd(8) related vm_page_unwire panics
Date: Mon, 02 Sep 2013 09:15:59 +0200

 On 02/09/2013 08:13, Peter Holm wrote:
 > I have not been able to reproduce this panic.
 
 Well, thank you for trying any way!
 
 > Suggested adding "-S" to amd(8) as a workaround.
 
 Done already:
 http://svnweb.freebsd.org/ports/head/sysutils/automounter/Makefile?revision=325726&view=markup
 
 Can I somehow provide more useful data? Maybe my use of nullfs also plays
 a part.
 
 > mount -p
 /dev/ufs/5root		/			ufs	rw,noatime 	1 1
 devfs			/dev			devfs	rw,multilabel 	0 0
 /dev/ufs/5stor		/pool/5stor		ufs	rw,noatime 	2 2
 /pool/5stor/usr		/usr			nullfs	rw,noatime 	0 0
 /pool/5stor/var		/var			nullfs	rw,noatime 	0 0
 /usr/home/root		/root			nullfs	rw,noatime 	0 0
 tmpfs			/var/log		tmpfs	rw		0 0
 tmpfs			/var/run		tmpfs	rw		0 0
 tmpfs			/tmp			tmpfs	rw		0 0
 pid62791 at mobileKamikaze:/var/run/automounter.amd.mnt /var/run/automounter.amd.mnt nfs	rw		0 0
 
 From my make.conf:
 .if !${.CURDIR:M/tmp/obj/*}
 WRKDIRPREFIX=           /tmp/obj/${HOST}/${ARCH}
 .endif
 
 -- 
 A: Because it fouls the order in which people normally read text.
 Q: Why is top-posting such a bad thing?
 A: Top-posting.
 Q: What is the most annoying thing on usenet and in e-mail? 


More information about the freebsd-bugs mailing list