Messages in this thread | | | Date | Wed, 24 Nov 1999 20:09:13 +0000 (GMT) | From | Alex Buell <> | Subject | Re: LoadsaOops in <select_dcache> |
| |
On Wed, 24 Nov 1999, Simon Kirby wrote:
> On Tue, Nov 23, 1999 at 07:41:43PM +0000, Alex Buell wrote: > > > How does one determine if this is due to hardware problems or due to > > software problems? I copied and burned a CD last night, all went well, > > left machine running over night. At 8:30am this morning, logged on, > > machine locked up during making a ppp call, rebooted, fscked with no > > filesystem problems, and found these in the logs. > > select_dcache and find_buffer are (were) the two most common functions > I've seen that will produce an Oops with bad memory. select_dcache has > been removed in newer kernels, but either way, I'd be willing to bet that > the Oops you got is probably from (more?) RAM problems...
I've been running the memtest program continuously all day today. No problems. It has to be a problem somewhere else, probably a nasty one hiding in the ide-scsi eumlation layer since the last thing I did was to copy a CD and burn a CD the night before.
I recall that a IDe SMP race was fixed in the 2.2.14pre patches.
Cheers, Alex --
Legalise cannabis today! Got GnuPG? Ask me for public key.
http://www.tahallah.demon.co.uk - updated!
- 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/
| |