Date: Tue, 6 Dec 2005 09:47:34 -0800 (PST)
From: Zwane Mwaikambo <zwane@arm.linux.org.uk>
To: matthew-lkml@newtoncomputing.co.uk
cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.27 crashed: any ideas?
In-Reply-To: <20051206111625.GA6542@newtoncomputing.co.uk>
Message-ID: <Pine.LNX.4.64.0512060944480.13220@montezuma.fsmlabs.com>
References: <20051206111625.GA6542@newtoncomputing.co.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1461
Lines: 28

On Tue, 6 Dec 2005, matthew-lkml@newtoncomputing.co.uk wrote:

> Our main user-facing Linux machine at work crashed a couple of times over the
> last few days, both with the same error. It's been up and stable for the last
> 80ish days (from when it was upgraded to Debian sarge), and had no problems
> before that with the same kernel.
> 
> Machine is an HP DL740 with four Xeon 2Ghz CPUs and 4Gb RAM (5Gb RAID 5).
> 
> I've put both outputs that our console logger saved, and the result from running
> them through ksymoops, at http://www.le.ac.uk/cc/mcn4/problem/
> 
> I realise the kernel is tainted. It's a locally compiled Debian kernel. I think
> the non-free module is the qla SAN card driver, but I'm not sure (is there a way
> of finding out what exactly tainted the kernel?)
> 
> The strange thing is that both times it seemed to crash in cfi_probe, which
> looks like something to do with Compact Flash / MTDs. Something we don't use.

You're probably using a bad System.map, all we do know is that the oops is 
occuring in a module. Can you try rerunning ksymoops using the System.map 
in your kernel build directory? Or, cat /proc/modules before it oopses and 
then we can compare the faulting address.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/