Trying to get through this revdep-rebuild first after the openmotif security patch. I'm planning on letting memtest run tonight. I've definitely got some kind of problem:
mm/memory.c:110: bad pmd 000001001d9873b8(0000000000002000). mm/memory.c:110: bad pmd 0000010000002000(ffffffff804e6097). mm/memory.c:110: bad pmd 0000010000002010(000000000009fbff). mm/memory.c:110: bad pmd 0000010000002018(0000000080000200). mm/memory.c:110: bad pmd 0000010000002020(ffffffff8056ac20). mm/memory.c:110: bad pmd 0000010000002028(0000010000002040). mm/memory.c:110: bad pmd 0000010000002038(00101000b8e0220f). mm/memory.c:110: bad pmd 0000010000002040(ffffffff804e5b46). mm/memory.c:110: bad pmd 0000010000002048(000000000009fc00). mm/memory.c:110: bad pmd 0000010000002050(000000000009ffff). mm/memory.c:110: bad pmd 0000010000002058(0000000080000200). mm/memory.c:110: bad pmd 0000010000002060(ffffffff8056ac20). mm/memory.c:110: bad pmd 0000010000002068(ffffffff805612e0). .......on and on....... On Tue, 15 Feb 2005 08:29:57 -0800, Mike <[EMAIL PROTECTED]> wrote: > Drew, > > Did you run memtest86? > > Regards, > > -Mike > > > On Tue, 15 Feb 2005 10:30:33 -0500, Drew Kirkpatrick > <[EMAIL PROTECTED]> wrote: > > This is looking like a hardware problem, but I'd like to run it by > > ya'll. I'm having internal compiling errors while emerging packages, > > and I just noticed this in my dmesg: > > > > mm/memory.c:110: bad pmd 000001001d9973b8(0000000000002000). > > as[28923]: segfault at 0000000000002018 rip 000000000040c5c0 rsp > > 0000007fbfffd3e0 error 4 > > x86_64-pc-linux[2332]: segfault at 0000000000002000 rip > > 00000000004036f0 rsp 0000007fbfffd440 error 4 > > swap_free: Unused swap offset entry 00000020 > > shadowcat(drew)> > > > > This memory sticks going bad? I've got two sticks of crucial balistix > > in an Asus A8V. Anyone think this might be somethign else besides bad > > memory (it's not new, it's been running solid for a while). Thanks in > > advance! > > > > -Drew > > > > -- > > [email protected] mailing list > > > > > > -- > Thanks, > > -Mike > -- [email protected] mailing list
