DragonFly bugs List (threaded) for 2004-07
Re: PANIC, screen shot included, ffs related
On Sat, 24 Jul 2004 23:10:45 -0400
Dan Janowski <danj@xxxxxxxxx> wrote:
> This is a just loaded system running 1.0A from the distribution ISOs.
> Sorry about the image snafu.
Just to add a datapoint: this is not unique. Someone on IRC (I forget
who, at the moment) reported a 'dup alloc' panic from a 1.0 system. I
suggested they run the drive manufacturer's diagnostic to rule out a bad
disk (since that was what bit me personally a while ago :) but I'm not
sure I heard anything from them since then. ISTR it was a Toshiba
(And for trivia's sake, the attachment with a MIME type of
application/applefile didn't work for me, because of the resource fork I
imagine, but the attachment right alongside it with a MIME type of
image/gif did :)
> On Jul 24, 2004, at 22:23, Matthew Dillon wrote:
> > :
> > :Dan Janowski wrote:
> > :
> > :> I was doing a pkg_add at the time. This machine is still running
> > at the
> > :> db> prompt. Let me know if there is something I can do at the
> > debugger
> > :> to help. If this is enough, let me know so I can reboot.
> > :
> > :The screen shot doesn't work here.
> > :
> > :Sascha
> > It's not a GIF, even though the extension says it is. Just
> > remove the extension and gimp will auto-detect whatever the
> > format is.
> > In anycase, I was able to bring it up. We have seen dup allocs
> > before, though I had hoped that the mountlist race I fixed on
> > July 10th would also fix the dup alloc panic. This fix did make
> > it into the release.
> > So, the quesion Dan is how old were the sources you built the
> > kernel from?
> > -Matt
> > Matthew Dillon
> > <dillon@xxxxxxxxxxxxx>