Running kernel-2.6.32-358.2.1.el6.i686 for a couple of days now with no
problem.
--
Ian Pilcher arequip...@gmail.com
Sometimes there's nothing left to do but crash and burn...or die
On Sun, Mar 3, 2013 at 11:02 PM, Ian Pilcher wrote:
> I updated my home server with the 6.4 CR packages, and I've experienced
> 3 or 4 hard lockups since. The server is a fanless VIA C7
> "CentaurHauls" system with a 1GHz CPU underclocked to 800MHz and 1GB of
> RAM. It has a dual-port Intel 8254
On Fri, Mar 8, 2013 at 5:04 PM, Steve Thompson wrote:
>
> Just a wild idea: is the NIC in the system that freezes a Broadcom and in
> the other system something else? If so, disable_msi=1 may help.
NICs are now both ThinkPenguin cards with an Atheros chipset.. At
this point, the systems are iden
On Fri, Mar 8, 2013 at 2:12 PM, Les Mikesell wrote:
>> I will try your suggestion of trying a separate set of banks in the
>> off chance that those slots are faulty.
>
> I had one a few years ago where it took about 3 days for memtest to
> catch the bad RAM but even after fixing that there were r
On Fri, 8 Mar 2013, Kwan Lowe wrote:
> Yes, latest BIOS installed. I have 2 of these also with similar
> configurations except for the NIC. One works perfectly the other has
> constant freezes. The working one has a slightly older BIOS so I'm
> thinking of downgrading the giltchy one.
Just a wild
On 03/08/2013 09:38 AM, Kwan Lowe wrote:
> On Thu, Mar 7, 2013 at 8:51 PM, Johnny Hughes wrote:
>
>> I have 2 of these motherboards (ASUS M5A99X EVO R2.0) that I am using in
>> CentOS development and testing. I am not seeing this issue .. I have
>> "M5A99X EVO R2.0 BIOS 1503" dated "2013/01/31 u
On 08.Mär.2013, at 19:28, Kwan Lowe wrote:
> On Fri, Mar 8, 2013 at 12:33 PM, SilverTip257 wrote:
>
>> If it's not memory related (test this memory in another system) then it is
>> probably a motherboard failure. I've seen weird symptoms where the system
>> will boot fine, but once the Linux ke
On Fri, Mar 8, 2013 at 12:28 PM, Kwan Lowe wrote:
>
>> If it's not memory related (test this memory in another system) then it is
>> probably a motherboard failure. I've seen weird symptoms where the system
>> will boot fine, but once the Linux kernel begins to build its cache it
>> triggers a lo
Kwan Lowe wrote:
> On Fri, Mar 8, 2013 at 12:33 PM, SilverTip257
> wrote:
>
>> If it's not memory related (test this memory in another system) then it
>> is probably a motherboard failure. I've seen weird symptoms where the
>> system will boot fine, but once the Linux kernel begins to build its
c
On Mar.08.2013 11:27 AM, Kwan Lowe wrote:
> On Fri, Mar 8, 2013 at 10:51 AM, Gerry Reno wrote:
>> Nearly every time we've had lockup problems it has come down to bad or
>> failing memory.
>>
>> I've even had memory cause problems where it would pass a quick memtest but
>> ultimately would fail i
On Fri, Mar 8, 2013 at 12:33 PM, SilverTip257 wrote:
> If it's not memory related (test this memory in another system) then it is
> probably a motherboard failure. I've seen weird symptoms where the system
> will boot fine, but once the Linux kernel begins to build its cache it
> triggers a lock
SilverTip257 wrote:
> On Fri, Mar 8, 2013 at 11:27 AM, Kwan Lowe wrote:
>
>> On Fri, Mar 8, 2013 at 10:51 AM, Gerry Reno wrote:
>> >
>> > Nearly every time we've had lockup problems it has come down to bad or
>> failing memory.
>> >
>> > I've even had memory cause problems where it would pass a q
On Fri, Mar 8, 2013 at 11:27 AM, Kwan Lowe wrote:
> On Fri, Mar 8, 2013 at 10:51 AM, Gerry Reno wrote:
> >
> > Nearly every time we've had lockup problems it has come down to bad or
> failing memory.
> >
> > I've even had memory cause problems where it would pass a quick memtest
> but ultimately
On 03/08/2013 11:46 AM, Kwan Lowe wrote:
> On Fri, Mar 8, 2013 at 11:34 AM, wrote:
>> Ok, so there was nothing in /var/log/dmesg? Have you tried running mcelogd?
> Nothing in dmesg, but I have not run mcelogd. I will try that tonight.
> Thanks!
> ___
On Fri, Mar 8, 2013 at 11:34 AM, wrote:
> Ok, so there was nothing in /var/log/dmesg? Have you tried running mcelogd?
Nothing in dmesg, but I have not run mcelogd. I will try that tonight. Thanks!
___
CentOS mailing list
CentOS@centos.org
http://lists
Kwan Lowe wrote:
> On Fri, Mar 8, 2013 at 11:25 AM, 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'
On Fri, Mar 8, 2013 at 11:25 AM, 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
On Fri, Mar 8, 2013 at 10:51 AM, Gerry Reno wrote:
>
> Nearly every time we've had lockup problems it has come down to bad or
> failing memory.
>
> I've even had memory cause problems where it would pass a quick memtest but
> ultimately would fail if you left it running
> the tests overnight.
T
Gerry Reno wrote:
> On 03/08/2013 10:43 AM, m.r...@5-cent.us wrote:
>> Kwan Lowe wrote:
>>> On Thu, Mar 7, 2013 at 8:51 PM, Johnny Hughes
>>> wrote:
>>
>>> As far as logging goes, any idea what sort of failures could cause
>>> such a lockup? I.e., if memory was failing, would the system still be
On 03/08/2013 10:43 AM, m.r...@5-cent.us wrote:
> Kwan Lowe wrote:
>> On Thu, Mar 7, 2013 at 8:51 PM, Johnny Hughes wrote:
>
>> As far as logging goes, any idea what sort of failures could cause
>> such a lockup? I.e., if memory was failing, would the system still be
>> able to log? As the mouse
Kwan Lowe wrote:
> On Thu, Mar 7, 2013 at 8:51 PM, Johnny Hughes wrote:
> As far as logging goes, any idea what sort of failures could cause
> such a lockup? I.e., if memory was failing, would the system still be
> able to log? As the mouse is frozen and kernel sysrq has no effect,
> I'm still le
On Thu, Mar 7, 2013 at 8:51 PM, Johnny Hughes wrote:
> I have 2 of these motherboards (ASUS M5A99X EVO R2.0) that I am using in
> CentOS development and testing. I am not seeing this issue .. I have
> "M5A99X EVO R2.0 BIOS 1503" dated "2013/01/31 update".
>
> Do you have the latest BIOS?
Thank
On 03/07/2013 12:52 PM, Kwan Lowe wrote:
> On Sun, Mar 3, 2013 at 11:02 PM, Ian Pilcher wrote:
>> I updated my home server with the 6.4 CR packages, and I've experienced
>> 3 or 4 hard lockups since. The server is a fanless VIA C7
>> "CentaurHauls" system with a 1GHz CPU underclocked to 800MHz an
On Sun, Mar 3, 2013 at 11:02 PM, Ian Pilcher wrote:
>
> I updated my home server with the 6.4 CR packages, and I've experienced
> 3 or 4 hard lockups since. The server is a fanless VIA C7
> "CentaurHauls" system with a 1GHz CPU underclocked to 800MHz and 1GB of
> RAM. It has a dual-port Intel 82
On Sun, Mar 3, 2013 at 11:02 PM, Ian Pilcher wrote:
> I updated my home server with the 6.4 CR packages, and I've experienced
> 3 or 4 hard lockups since. The server is a fanless VIA C7
> "CentaurHauls" system with a 1GHz CPU underclocked to 800MHz and 1GB of
> RAM. It has a dual-port Intel 825
I updated my home server with the 6.4 CR packages, and I've experienced
3 or 4 hard lockups since. The server is a fanless VIA C7
"CentaurHauls" system with a 1GHz CPU underclocked to 800MHz and 1GB of
RAM. It has a dual-port Intel 82546GB NIC in its single PCI slot. (It
also has an on-board Rea
26 matches
Mail list logo
