xfs
[Top] [All Lists]

Re: Fixed? xfs_alloc_lookup kernel oopses... Stupidity wins again!

To: Stuart Levy <slevy@xxxxxxxxxxxxx>
Subject: Re: Fixed? xfs_alloc_lookup kernel oopses... Stupidity wins again!
From: Steve Lord <lord@xxxxxxx>
Date: 04 Mar 2002 15:02:44 -0600
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <200203042058.OAA03586@xxxxxxxxxxxxxxxxxx>
References: <200203042058.OAA03586@xxxxxxxxxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
On Mon, 2002-03-04 at 14:58, Stuart Levy wrote:
> I'd been getting frequent (every hour or two under heavy load)
> NULL-pointer kernel Oopses in xfs_alloc_lookup,
> using Jan 23 2.4.17 snapshot patch, and also with the full
> CVS 2.4.18-xfs, compiled either with gcc 2.95.3 or 2.91.66.  
> 
> Realized over the weekend that the machine has 1GB of RAM,
> but I hadn't built the kernel with CONFIG_HIGHMEM!
> Booted the existing kernel with mem=800M -- seemed to help --
> and rebuilt 2.4.18-xfs with CONFIG_HIGHMEM (i.e. "4GB").
> It hasn't crashed since then either.  Workload hasn't been
> terribly heavy, but I think it would have died by now
> if the old symptom hadn't been fixed.
> 
> Sorry to have bothered you all with this
> 
>    Stuart Levy, slevy@xxxxxxxxxxxxx

Well, seems a little odd that running a non-highmem kernel on a highmem
box would cause this. It should ignore the memory it cannot get to. Keep
us posted if things fall over again.

Good to get something knocked off the list though.

Steve


-- 

Steve Lord                                      voice: +1-651-683-3511
Principal Engineer, Filesystem Software         email: lord@xxxxxxx


<Prev in Thread] Current Thread [Next in Thread>