Date: Fri, 21 Feb 1997 18:30:01 -0800 (PST) From: Mike Pritchard <mpp> To: freebsd-bugs Subject: Re: kern/1661 Message-ID: <199702220230.SAA14699@freefall.freebsd.org>
index | next in thread | raw e-mail
The following reply was made to PR kern/1661; it has been noted by GNATS. From: Mike Pritchard <mpp> To: freebsd-gnats-submit Cc: Subject: Re: kern/1661 Date: Fri, 21 Feb 1997 18:27:42 -0800 (PST) Feedback from the originator: Gene Stark wrote: > From gene@starkhome.cs.sunysb.edu Fri Feb 21 18:22:45 1997 > Date: Fri, 21 Feb 1997 21:08:53 -0500 (EST) > From: Gene Stark <gene@starkhome.cs.sunysb.edu> > Message-Id: <199702220208.VAA18539@starkhome.cs.sunysb.edu> > To: freefall.freebsd.org!mpp@bsd7.cs.sunysb.edu > In-reply-to: Mike Pritchard's message of Fri, 21 Feb 1997 16:19:44 -0800 (PST) <199702220019.QAA06967@freefall.freebsd.org> > Subject: FreeBSD PR# 1661 > > >Are you still seeing the problem reported in your FreeBSD problem report? > >Have you tried later versions, such as FreeBSD 2.2 BETA or GAMMA > >or FreeBSD 3.0-current? Any other information you could provide would > >be helpful. If you are still seeing the problem, what version > >of FreeBSD are you running right now? > > Yes, I am still seeing a similar problem, but not the particular one I > originally reported, as I have patched that. The patch I supplied with my > bug report fixed the highly repeatable initial hang at the beginning > of a dump, but I still experience somewhat more erratic timing-dependent > hangs of a similar nature in many cases. When I was looking through > the driver some months ago in generating the patch I sent in, I believe > I noted other race conditions in the driver as well, which are probably > what are getting exercised now. > > The structure of the driver was such that it was very difficult to > trace through and determine at which points interrupts were enabled > and disabled. My conclusion was that the easiest thing to do might be > to restructure the driver so this was more clear. Unfortunately, I didn't > have the time to do this. In its current state, the driver is pretty > useless to me because more often than not a long dump will hang. > > The latest system I have tried it on is 2.1.5. However it looks like > the problems were in the driver itself, so unless the driver has been fixed, > I would expect similar problems to exist in later FreeBSD versions. > > - Gene Stark > -- Mike Pritchard mpp@FreeBSD.org "Go that way. Really fast. If something gets in your way, turn"home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199702220230.SAA14699>