Re: pg_dump strangeness - Mailing list pgsql-general

From Lane Rollins
Subject Re: pg_dump strangeness
Date
Msg-id 004b01c2e85e$b2d04a40$fd03000a@Lanedell
Whole thread Raw
In response to Re: pg_dump strangeness  (Stephen Robert Norris <srn@commsecure.com.au>)
List pgsql-general
The problem seems to be either bad mainboard or memory. The machine
decided it was going to start crashing very regularly and finally
stopped even booting. I ended up moving the raid board, drives and one
of the sticks of memory to another box and so far it's still running.

I'll try running the memory tests tomorrow. I'm not stuck in meetings
all day.

Thanks for the help and suggestions,
-Lane

> -----Original Message-----
> From: pgsql-general-owner@postgresql.org [mailto:pgsql-general-
> owner@postgresql.org] On Behalf Of Stephen Robert Norris
> Sent: Tuesday, March 11, 2003 9:19 PM
> To: Neil Conway
> Cc: Lane Rollins; PostgreSQL General
> Subject: Re: [GENERAL] pg_dump strangeness
>
> On Tue, 2003-03-11 at 16:57, Neil Conway wrote:
> > On Mon, 2003-03-10 at 19:15, Lane Rollins wrote:
> > > Mar 10 02:34:08internal kernel: Unable to handle kernel NULL
pointer
> > > dereference at virtual address 00000020
> >
> > Looks like a kernel bug -- there's not much we can do to help,
AFAIK.
> > Have you tried applying any errata that RH have put out for your
kernel,
> > and/or reporting the problem to the appropriate source? (lkml, RH,
etc.)
> >
> > Cheers,
> >
> > Neil
>
> It could also be bad memory - try memtest86 for an hour or two.
>
>     Stephen



pgsql-general by date:

Previous
From: Stephen Robert Norris
Date:
Subject: Re: pg_dump strangeness
Next
From: Mohd Ghalib Akhtar
Date:
Subject: socket error