All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@w.ods.org>
To: Marc Giger <gigerstyle@gmx.ch>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux on UltraSparcII E450
Date: Sat, 17 Apr 2004 12:06:30 +0200	[thread overview]
Message-ID: <20040417100630.GG596@alpha.home.local> (raw)
In-Reply-To: <20040417105303.7936e413@vaio.gigerstyle.ch>

Hmmm, I believe you forgot to tell which kernel version you used, and how
you configured it :-)

Willy

On Sat, Apr 17, 2004 at 10:53:03AM +0200, Marc Giger wrote:
> Hi All,
> 
> Last week I had the honor to install Linux on a E450 with 2 cpu's. All
> went fine at first. Long compiling sessions were no problem for the
> machine. Later we installed 16 additional SCSI disks and we built 
> 4 x Soft-RAID5 groups with 4 disks each.
> After some time during the sync processes the machine stops responding.
> Simply dead. The same thing happens after every boot when the sync
> process is in action.
> 
> My question now is: Is it a hardware or a kernel problem? I now it isn't
> a simple question with the given infos.
> Is it possible that the 4 parallel sync processes are to much for the
> SCSI (standard LSI) controllers?
> I assume that the kernel RAID5 code is stable on sparc?!
> 
> Thank you
> 
> Regards
> 
> Marc
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

  reply	other threads:[~2004-04-17 10:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-17  8:53 Linux on UltraSparcII E450 Marc Giger
2004-04-17 10:06 ` Willy Tarreau [this message]
2004-04-17 12:15   ` Marc Giger
2004-04-17 13:20 ` Ben Collins

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=20040417100630.GG596@alpha.home.local \
    --to=w@w.ods.org \
    --cc=gigerstyle@gmx.ch \
    --cc=linux-kernel@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.