https://bugzilla.novell.com/show_bug.cgi?id=353252 User jeffm@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=353252#c12 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |drankinatty@suddenlinkmail.com --- Comment #12 from Jeff Mahoney <jeffm@novell.com> 2008-02-20 13:18:04 MST --- The Oops in the initial description was caused by buffer_mapping (inode->i_data.assoc_mapping) being NULL in remove_inode_buffers(). spin_lock hits it and derefs the NULL pointer to find the lock. The Oops in comment #3 was caused by the buffer head being NULL, and it's accessing bh->b_data (0x19 = 25). NULL in this case likely means 0x1. I haven't decoded the others because I'm not really sure how we should proceed here. You're getting Oopses all over the kernel in *core* data paths. These paths are well tested, and more importantly used by every Linux user every day. I know you've said you've tried using different memory, etc - but I'd stil like to see the results of a memtest run. Also, is this system overclocked? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.