I have textdumps for two vm_page_unwire panics.
The first one occurred while copying data from one msdosfs to another,
both mounted through amd:
The second one happened when SIGTERM was sent to amd, while there was
heavy tmpfs load (building chromium). No file systems were mounted through
amd at the time:
The second case is easy to reproduce, I have a 100% panic quota for this
The core trouble is that the issue even occurs /after/ there was heavy
tmpfs load in the past, while amd was running. Again without any actual
mounts happening. So there is a panic for every system shutdown/reboot.
How-To-Repeat: Set WRKDIRPREFIX to a tmpfs (I do not know whether the tmpfs is necessary,
but it certainly helps avoiding excessive filesystem damage).
# cd /usr/ports/www/chromium
Wait till the configure phase is over and the port is actually compiling.
# service amd stop
While chromium is still compiling.
I have not been able to reproduce this panic.
Suggested adding "-S" to amd(8) as a workaround.
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.
Can I somehow provide more useful data? Maybe my use of nullfs also plays
> 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@mobileKamikaze:/var/run/automounter.amd.mnt /var/run/automounter.amd.mnt nfs rw 0 0
From my make.conf:
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
Q: What is the most annoying thing on usenet and in e-mail?
For bugs matching the following criteria:
Status: In Progress Changed: (is less than) 2014-06-01
Reset to default assignee and clear in-progress tags.
Mail being skipped