On Sun, 2010-02-07 at 11:42 +0200, Gilboa Davara wrote: > On Fri, 2010-02-05 at 19:30 -0430, Patrick O'Callaghan wrote: > > On Fri, 2010-02-05 at 17:51 +0000, Bryn M. Reeves wrote: > > > > [<ffffffff8110456d>] path_put+0x1a/0x27 > > > > [<ffffffff81095ba9>] audit_free_names+0x5b/0x7a > > > > [<ffffffff81095da1>] audit_syscall_exit+0xb3/0x14c > > > > [<ffffffff81011ea8>] sysret_audit+0x14/0x1e > > > > > > Are the crashes you're seeing always in this set of functions (same > > > backtrace) or are you getting variations? > > > > I started seeing wierd behaviour (NFS failures, sudden crash of KDE > > etc.) so I ran memtest and discovered some bad RAM in the 3-4Gb range. > > > > I've rebooted using mem=2000M and we'll see what happens. > > > > poc > > > > poc, > > mem=2000m may not help, as your BIOS/chipset might be interleaving > memory from multiple banks. Of course, but if so the interleaving would also apply when running memtest. IOW if memtest tells me the lower and upper addresses for errors are (say) 2200M and 3600M, and marks banks 3 and 4 as being the origin of these, then setting mem=2000M will avoid them, no matter what the interleaving is. Identifying which DIMMS they are is of course another matter, which is why I did it this way before starting to pull DIMMs (it's very easy to confuse yourself doing that). > I'd know more if you post your hardware configuration. (CPU, > Motherboard, number of DIMMs, etc.) Intel D865GLC, Core 2 Duo 6400 @ 2.13GHz. There are 4x1GB DDR-2 sticks. > In general, you should disable interleaving in BIOS (if you > chipset/bios/CPU supports it) and fire up memtest (found on the Fedora > ISO's and at http://www.memtest.org/) I ran memtest (several passes) limited to 2000M and it found no errors. poc -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
