Well, I haven't responded because there wasn't enough information for me to even be able to speculate reasonably.

Most recent code: yes/no CAM: yes/no Soft updates: yes/no SCSI: yes/no AIC SCSI: yes/no backed off clock.c change: yes/no ELF: yes/no other mutating subsystem: yes/no (this one is hard to track) Trap address: _______________ nm /kernel | sort -n: _______________ _______________ _______________ (include only lines immediately proceeding and following the the trap address; this should be scripted by someone who cares).

currently running program: _______________ stack traceback up to panic: _______________ _______________ _______________ (include only sufficient information to get to the point where the panic occurred, since se all know about the 12 or so things panic calls).

Also, if you can identify a particular kernel subsystem from this, you should contact the maintainer of that subsystem directly for best response.

There is a lot of activity in -current, and I'm having a hard time identifying where your problem begins and stale/bad code ends, which is why I haven't responded.

To Unsubscribe: send mail to majo...@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message