Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Andrew Linfoot" <andy@derfel99.freeserve.co.uk>
To: <linux@cthulhu.engr.sgi.com>
Subject: Re: File corruption
Date: Fri, 25 Jun 1999 15:34:15 +0100	[thread overview]
Message-ID: <002701bebf17$cd9e4fd0$0a02030a@snafu> (raw)
In-Reply-To: 19990625002853.D17220@uni-koblenz.de

I have been running 2.2.1 on my indy for about 3 weeks now and have
encountered problems like this,
in fact i am surprised at how stable the box is, i have been doing some
quite large builds of qt, kde and the like too. If this is reproducible then
i would be prepared to experiment on one of my boxes.

The only gripe i have is that the scsi driver breaks when i attach external
devices, any ideas?

Andy
----- Original Message -----
From: Ralf Baechle <ralf@uni-koblenz.de>
To: <linux@cthulhu.engr.sgi.com>
Sent: Thursday, June 24, 1999 11:28 PM
Subject: Re: File corruption


> On Wed, Jun 23, 1999 at 01:49:23AM +0200, Ulf Carlsson wrote:
>
> > > And under which kernel version did this start to happen?
> >
> > 2.2.1 I think.
>
> Are you shure?  The problem Alan is tracking started to hit from 2.2.7 on.
> If 2.2.1 already starts making these kind of troubles then we probably
> track two different problems.
>
> > Unfortunately I don't have IRIX.  However, I have a 133 MHz R4600 CPU
with 512 k
> > board cache.  I have two 1 Gb SCSI driver connected.
>
> Is this a low-mem configuration?  The problem Alan is tracking apparently
> seems to hit low mem systems more often.
>
>   Ralf
>

WARNING: multiple messages have this Message-ID (diff)
From: "Andrew Linfoot" <andy@derfel99.freeserve.co.uk>
To: linux@cthulhu.engr.sgi.com
Subject: Re: File corruption
Date: Fri, 25 Jun 1999 15:34:15 +0100	[thread overview]
Message-ID: <002701bebf17$cd9e4fd0$0a02030a@snafu> (raw)
Message-ID: <19990625143415.lcfbBD2uf9k7HTqqdw0jXKsswy8SnARim_SQ_UsvtiQ@z> (raw)
In-Reply-To: 19990625002853.D17220@uni-koblenz.de

I have been running 2.2.1 on my indy for about 3 weeks now and have
encountered problems like this,
in fact i am surprised at how stable the box is, i have been doing some
quite large builds of qt, kde and the like too. If this is reproducible then
i would be prepared to experiment on one of my boxes.

The only gripe i have is that the scsi driver breaks when i attach external
devices, any ideas?

Andy
----- Original Message -----
From: Ralf Baechle <ralf@uni-koblenz.de>
To: <linux@cthulhu.engr.sgi.com>
Sent: Thursday, June 24, 1999 11:28 PM
Subject: Re: File corruption


> On Wed, Jun 23, 1999 at 01:49:23AM +0200, Ulf Carlsson wrote:
>
> > > And under which kernel version did this start to happen?
> >
> > 2.2.1 I think.
>
> Are you shure?  The problem Alan is tracking started to hit from 2.2.7 on.
> If 2.2.1 already starts making these kind of troubles then we probably
> track two different problems.
>
> > Unfortunately I don't have IRIX.  However, I have a 133 MHz R4600 CPU
with 512 k
> > board cache.  I have two 1 Gb SCSI driver connected.
>
> Is this a low-mem configuration?  The problem Alan is tracking apparently
> seems to hit low mem systems more often.
>
>   Ralf
>

  parent reply	other threads:[~1999-06-25 14:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <19990622032859.B6955@thepuffingroup.com>
     [not found] ` <19990622152145.A1059@uni-koblenz.de>
1999-06-22 23:49   ` File corruption Ulf Carlsson
1999-06-24 22:28     ` Ralf Baechle
1999-06-25 13:31       ` Ulf Carlsson
1999-06-25 18:08         ` Thomas Bogendoerfer
1999-06-25 14:34       ` Andrew Linfoot [this message]
1999-06-25 14:34         ` Andrew Linfoot
1999-06-25 16:59         ` Ulf Carlsson
1999-06-25 17:11           ` Andrew Linfoot
1999-06-25 17:11             ` Andrew Linfoot
1999-06-28 10:39             ` Ralf Baechle
1999-06-28  9:34         ` Ralf Baechle

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='002701bebf17$cd9e4fd0$0a02030a@snafu' \
    --to=andy@derfel99.freeserve.co.uk \
    --cc=linux@cthulhu.engr.sgi.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox