All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@uni-koblenz.de>
To: Andrew Linfoot <andy@derfel99.freeserve.co.uk>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: File corruption
Date: Mon, 28 Jun 1999 11:34:54 +0200	[thread overview]
Message-ID: <19990628113454.A735@uni-koblenz.de> (raw)
In-Reply-To: <002701bebf17$cd9e4fd0$0a02030a@snafu>; from Andrew Linfoot on Fri, Jun 25, 1999 at 03:34:15PM +0100

On Fri, Jun 25, 1999 at 03:34:15PM +0100, Andrew Linfoot wrote:

> 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?

There is nothings special with external devices, so if they result in
crashes you should double check that cabeling and termination are ok.

  Ralf

  parent reply	other threads:[~1999-06-28 21:48 UTC|newest]

Thread overview: 15+ 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
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 [this message]
2002-09-30 19:52 File Corruption jeff leads
2002-10-01  6:10 ` Oleg Drokin
2002-10-02  4:07   ` jeff leads
2002-10-02  6:30     ` Oleg Drokin

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=19990628113454.A735@uni-koblenz.de \
    --to=ralf@uni-koblenz.de \
    --cc=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 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.