Re: 2.2.15pre17 oops --- find_buffer+104/144

From: Matthias Andree (ma@dt.e-technik.uni-dortmund.de)
Date: Tue Apr 11 2000 - 16:22:11 EST

Next message: Zack Brown: "Re: Patch Archive"
Previous message: Kurt Roeckx: "2.3.99-pre4: Oops on boot."
Next in thread: Alex Buell: "Re: 2.2.15pre17 oops --- find_buffer+104/144"
Reply: Alex Buell: "Re: 2.2.15pre17 oops --- find_buffer+104/144"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Alex Buell <alex.buell@tahallah.demon.co.uk> writes:

> It sure would be nice to have some form of CRC checking to detect problems
> of this nature. I know it would kill performance though.

Get ECC RAM. Then figure out how to enable parity checking or correction
AND find how if and if so, how, Linux tells you that there has been
trouble with the RAM.

-- Matthias Andree

Where do you think you're going today?

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/

Next message: Zack Brown: "Re: Patch Archive"
Previous message: Kurt Roeckx: "2.3.99-pre4: Oops on boot."
Next in thread: Alex Buell: "Re: 2.2.15pre17 oops --- find_buffer+104/144"
Reply: Alex Buell: "Re: 2.2.15pre17 oops --- find_buffer+104/144"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sat Apr 15 2000 - 21:00:17 EST