[CentOS] Lockups with kernel-2.6.32-358.0.1.el6.i686
m.roth at 5-cent.us
m.roth at 5-cent.usFri Mar 8 16:34:18 UTC 2013
- Previous message: [CentOS] Lockups with kernel-2.6.32-358.0.1.el6.i686
- Next message: [CentOS] Lockups with kernel-2.6.32-358.0.1.el6.i686
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Kwan Lowe wrote: > On Fri, Mar 8, 2013 at 11:25 AM, <m.roth at 5-cent.us> wrote: >> >> Right, but I've always *seen* error messages, dmesg, and, if mcelogd is >> actually working (I can't figure out why it seems to on some machines, >> and not on others, or why it doesn't keep running), it's in there. The times >> we've had lockups, there's been nothing. > > That's the frustrating thing.. Not a single error message. It also > appears unrelated to system load as I went through 4 hours of the > Phoronix test suite that pegged all 8 cores, Unigine Valley benchmark > for several loops, memtest.. All passed. But at night it locked up > when there was no load. Ok, so there was nothing in /var/log/dmesg? Have you tried running mcelogd? mark
- Previous message: [CentOS] Lockups with kernel-2.6.32-358.0.1.el6.i686
- Next message: [CentOS] Lockups with kernel-2.6.32-358.0.1.el6.i686
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the CentOS mailing list