panic with cdrecord -- anybody else seeing this? [backtrace obtained]

[John Reynolds]

[ On Monday, October 13, Marius Strobl wrote: ]
> 
> And
> http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/57611
> 
> The latter is a bit more detailed and correct (it's not limited to ATAPI
> burners). It also doesn't seem to be limited to cdrecord, the latest
> ntpd also causes a panic when using mlockall(2) as reported on this list,
> however the backtrace looks different.
> Btw., the cdrtools-devel port contains a workaround.

Thanks. I haven't tried cdrtools-devel in "a while" so I probably didn't see
the work-around that was committed. I will try it and report back as to if it
works (to further narrow down the mlockall(2) bit....).

-Jr

-- 
John & Jennifer Reynolds  johnjen at reynoldsnet.org        www.reynoldsnet.org
Structural / Physical Design - ICG/PNG SCD     jreynold at sedona.ch.intel.com
Running FreeBSD since 2.1.5-RELEASE.               FreeBSD: The Power to Serve!
"Unix is user friendly, it's just particular about the friends it chooses."