Date: Mon, 13 Oct 2003 05:26:59 -0700 From: John Reynolds <johnjen@reynoldsnet.org> To: Marius Strobl <marius@alchemy.franken.de> Cc: current@freebsd.org Subject: Re: panic with cdrecord -- anybody else seeing this? [backtrace obtained] Message-ID: <16266.39443.651696.361978@whale.home-net> In-Reply-To: <20031013073935.B6508@newtrinity.zeist.de> References: <16266.165.855721.885956@whale.home-net> <20031013041808.GA33468@rot13.obsecurity.org> <20031013073935.B6508@newtrinity.zeist.de>
next in thread | previous in thread | raw e-mail | index | archive | help
[ 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."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16266.39443.651696.361978>