All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: <pau@readysoft.es>
To: ultralinux@vger.kernel.org
Subject: Re: bug in 2.2.13pre7 on Ultras (more oops)
Date: Wed, 15 Sep 1999 07:42:23 +0000	[thread overview]
Message-ID: <marc-linux-ultrasparc-93738196125019@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-93738047523759@msgid-missing>

On Wed, 15 Sep 1999, David S. Miller wrote:

>    From: pau@readysoft.es
>    Date: Wed, 15 Sep 1999 09:23:15 +0200 (CEST)
> 
>    > Also, are you getting correctable ECC memory errors in your
>    > kernel logs before this happens?  I am very close to starting to
>    > encourage
> 
>    If it should log anything, I don't get it. No errors in the logs or
>    the console but the ones I include.
> 
> What kernel are you running?  Maybe you are running a kernel which
> just ignores the CEE errors and does not log them, current 2.2.x
> kernels log all correctable ECC memory errors in the dmesg logs.

2.2.13pre7 + raid5 patches + ncr patch from Gerard Roudier
Tha machine sill runs ultrapenguin and the kernel is compiled on
ultrapenguin -see at the gcc compiler-.

# uname -a                                                    
Linux ultratest 2.2.13pre7 #1 Mon Sep 13 10:24:05 CEST 1999 sparc64
unknown

# dmesg
PROMLIB: Sun IEEE Boot Prom 3.10.6 1998/12/08 13:30
Linux version 2.2.13pre7 (root@ursa) (gcc version egcs-2.92.11 19980921
(gcc2 ss-980609 experimental)) #1 Mon Sep 13 10:24:05 CEST 1999
ARCH: SUN4U                                                                     

Pau

  parent reply	other threads:[~1999-09-15  7:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-15  7:23 bug in 2.2.13pre7 on Ultras (more oops) pau
1999-09-15  7:34 ` David S. Miller
1999-09-15  7:42 ` pau [this message]
1999-09-15  8:10 ` David S. Miller
1999-09-15 10:10 ` pau

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-linux-ultrasparc-93738196125019@msgid-missing \
    --to=pau@readysoft.es \
    --cc=ultralinux@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.