Steve Ames <[EMAIL PROTECTED]> writes:
> *grin* I certainly haven't ruled out the possibility of crack induced
> hysteria. I'm reading the kerneldebug handbook section and will get
> some traces.
Take a look at the "making the most of a kernel panic" entry in the
FAQ (incidentially, that entry wa
On Fri, Oct 20, 2000 at 02:36:48AM +0200, Dag-Erling Smorgrav wrote:
> Steve Ames <[EMAIL PROTECTED]> writes:
> > On Thu, Oct 19, 2000 at 06:15:23PM -0400, Bosko Milekic wrote:
> > > On Thu, 19 Oct 2000, Steve Ames wrote:
> > > I'm running -CURRENT from approximately 4 days ago and I am not
> >
Steve Ames <[EMAIL PROTECTED]> writes:
> On Thu, Oct 19, 2000 at 06:15:23PM -0400, Bosko Milekic wrote:
> > On Thu, 19 Oct 2000, Steve Ames wrote:
> > I'm running -CURRENT from approximately 4 days ago and I am not
> > noticing this.
> It doesn't happen every time. But if you use the command
On Thu, Oct 19, 2000 at 06:15:23PM -0400, Bosko Milekic wrote:
> On Thu, 19 Oct 2000, Steve Ames wrote:
> > admin# sockstat | grep -v '*.*'
> > close(fstat):
> >
> > The OS locked up after that.
>
> I'm running -CURRENT from approximately 4 days ago and I am not
> noticing this.
It does
On Thu, 19 Oct 2000, Steve Ames wrote:
> admin# sockstat | grep -v '*.*'
> close(fstat):
>
> The OS locked up after that.
I'm running -CURRENT from approximately 4 days ago and I am not
noticing this.
> That's just not normal :) Could someone give me the quick and dirty
> on how I c
admin# sockstat | grep -v '*.*'
close(fstat):
The OS locked up after that.
That's just not normal :) Could someone give me the quick and dirty
on how I can provide additional details? This is on -CURRENT from
10/16.
The hardware is:
Dual P3-500Mhz, 512M RAM.
The kernel file is:
machine
