scar a écrit :
BERTRAND Joël wrote on 09/11/2014 12:41 PM:
Hello,
scar a écrit :
how can i test RAM and other hardware,
for example?
You can use diag_switch? = true and diag_level = max (with a null
modem serial line).
i set these options but it doesn't seem to do anything... i s
BERTRAND Joël wrote on 09/11/2014 12:41 PM:
> Hello,
>
> scar a écrit :
>> how can i test RAM and other hardware,
>> for example?
>
> You can use diag_switch? = true and diag_level = max (with a null
> modem serial line).
i set these options but it doesn't seem to do anything... i see a
Mark Morgan Lloyd a écrit :
BERTRAND Joël wrote:
Hermann Lauer a écrit :
On Sun, Sep 14, 2014 at 07:44:31PM +0200, BERTRAND Jo??l wrote:
hmm well where will this info usually show up? in the system/kernel
logs? if it's not showing up then that means the freezes must be
caused
by something ot
BERTRAND Joël wrote:
Hermann Lauer a écrit :
On Sun, Sep 14, 2014 at 07:44:31PM +0200, BERTRAND Jo??l wrote:
hmm well where will this info usually show up? in the system/kernel
logs? if it's not showing up then that means the freezes must be
caused
by something other than ECC errors?
Hermann Lauer a écrit :
On Sun, Sep 14, 2014 at 07:44:31PM +0200, BERTRAND Jo??l wrote:
hmm well where will this info usually show up? in the system/kernel
logs? if it's not showing up then that means the freezes must be caused
by something other than ECC errors?
On console and syste
On Sun, Sep 14, 2014 at 07:44:31PM +0200, BERTRAND Jo??l wrote:
> >hmm well where will this info usually show up? in the system/kernel
> >logs? if it's not showing up then that means the freezes must be caused
> >by something other than ECC errors?
>
> On console and system logs. Freezes c
scar a écrit :
BERTRAND Joël wrote on 09/13/2014 03:37 PM:
If I remember, ECC errors are corrected by psycho. Psycho (and
schizo) return some information about memory error like "corrected" or
"uncorrectable" errors. If you only see "corrected" errors, you have to
change a memory module, bu
BERTRAND Joël wrote on 09/13/2014 03:37 PM:
> If I remember, ECC errors are corrected by psycho. Psycho (and
> schizo) return some information about memory error like "corrected" or
> "uncorrectable" errors. If you only see "corrected" errors, you have to
> change a memory module, but system sh
scar a écrit :
and now that i think harder, i think i do remember seeing some ECC
errors in the system log back when i was running SunOS. maybe the RAM
does have some issues but the ECC was properly handled by SunOS so i
never experienced any problems. can anyone speak about ECC handling
with D
hi thank you all for the responses. sounds like i need to try older 2.6
kernel... hopefully can do this with apt-get because i dont want to
reinstall OS. BSD is an OS i am scared of :) but have been wanting to
try it again so perhaps will take the plunge again and try NetBSD if i
cannot get some
Mark Morgan Lloyd a écrit :
BERTRAND Joël wrote:
Mark Morgan Lloyd a écrit :
Aaro Koskinen wrote:
Hi,
On Thu, Sep 11, 2014 at 09:41:09PM +0200, BERTRAND Joël wrote:
BUT : for several months, Linux/Sparc64 is unfortunately not stable
anymore
(or completely broken). After 2.6.35 kernel, I can
BERTRAND Joël wrote:
Mark Morgan Lloyd a écrit :
Aaro Koskinen wrote:
Hi,
On Thu, Sep 11, 2014 at 09:41:09PM +0200, BERTRAND Joël wrote:
BUT : for several months, Linux/Sparc64 is unfortunately not stable
anymore
(or completely broken). After 2.6.35 kernel, I can see random
deadlock on
all my
Mark Morgan Lloyd a écrit :
Aaro Koskinen wrote:
Hi,
On Thu, Sep 11, 2014 at 09:41:09PM +0200, BERTRAND Joël wrote:
BUT : for several months, Linux/Sparc64 is unfortunately not stable
anymore
(or completely broken). After 2.6.35 kernel, I can see random
deadlock on
all my sparc64 (sun4v _and_
Aaro Koskinen wrote:
Hi,
On Thu, Sep 11, 2014 at 09:41:09PM +0200, BERTRAND Joël wrote:
BUT : for several months, Linux/Sparc64 is unfortunately not stable anymore
(or completely broken). After 2.6.35 kernel, I can see random deadlock on
all my sparc64 (sun4v _and_ sun4u). Now, I run NetBSD or
Hello,
On Fri, Sep 12, 2014 at 03:03:40AM +0300, Aaro Koskinen wrote:
> On Thu, Sep 11, 2014 at 09:41:09PM +0200, BERTRAND Joël wrote:
> > BUT : for several months, Linux/Sparc64 is unfortunately not stable anymore
> > (or completely broken). After 2.6.35 kernel, I can see random deadlock on
> > a
Hi,
On Thu, Sep 11, 2014 at 09:41:09PM +0200, BERTRAND Joël wrote:
> BUT : for several months, Linux/Sparc64 is unfortunately not stable anymore
> (or completely broken). After 2.6.35 kernel, I can see random deadlock on
> all my sparc64 (sun4v _and_ sun4u). Now, I run NetBSD or Solaris 10. But
>
Hi Scar,
When you say you are experiencing hard freezes, can you give a time frame?
>From you email it sounds like this:
* Installed Wheezy (works 100% perfectly?)
* Some time passes
* Now, it hard freezes (at boot? after a minute? after an hour? one week?)
I don't have problems with my Sun Ultr
Hello,
scar a écrit :
hi i have an Ultra-5 which has been housed in a datacenter for several
years. It used to be running SunOS 5.9 and i didn't experience any
problems with it. As that OS became obsolete, I installed Wheezy on the
box not too long ago but now am experiencing hard free
18 matches
Mail list logo