From: Daniel Jacobowitz <drow@false.org>
To: satadru pramanik <satadru@umich.edu>
Cc: Brad Midgley <brad@pht.com>, linuxppc-dev@lists.linuxppc.org
Subject: Re: scsi hangs [drow@cs.cmu.edu: Re: CD-writers] (fwd)
Date: Sat, 2 Jan 1999 20:14:32 -0500 [thread overview]
Message-ID: <19990102201432.A736@drow.res.cmu.edu> (raw)
In-Reply-To: <Pine.SOL.4.05.9901021800540.29365-100000@asteroids.rs.itd.umich.edu>; from satadru pramanik on Sat, Jan 02, 1999 at 06:04:01PM -0500
On Sat, Jan 02, 1999 at 06:04:01PM -0500, satadru pramanik wrote:
> Please let me know!!! And if this _does- fix the problem, it should go to
> linus asap, before 2.2 gets finalized. This certainly is a problem for
> me, and I can't imagine seeing a 2.2 final kernel that hangs on serious
> scsi activity. ( it crashes my web server every ten minutes.)
>
>
> On Sat, 2 Jan 1999, Brad Midgley wrote:
>
>
> paul,
>
> what was the result of testing this patch? i see it isn't present at vger.
> but does it make scsi activity safer? does it need more testing? should i
> test it as-is?
>
> dan, have you figured out a setup to burn cd's without panics?
I am not at my machine for another week, but judging from what I have
heard - the patch does make it safer, is certainly a good idea to
apply, and yet still does not resolve the issue. I need to find out
how it affects my machine - expect this as soon as I can.
Meanwhile, Satadru, I suggest you invest in an internal drive - or try
using all your devices on the same scsi controller, which I have heard
might help.
Dan
/--------------------------------\ /--------------------------------\
| Daniel Jacobowitz |__| CMU, CS class of 2002 |
| Debian GNU/Linux Developer __ Part-Time Systems Programmer |
| dan@debian.org | | drow@cs.cmu.edu |
\--------------------------------/ \--------------------------------/
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
next prev parent reply other threads:[~1999-01-03 1:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.3.95.990102113010.4424A-100000@pacific.pht.com>
1999-01-02 19:14 ` scsi hangs [drow@cs.cmu.edu: Re: CD-writers] (fwd) Brad Midgley
1999-01-02 23:04 ` satadru pramanik
1999-01-03 1:14 ` Daniel Jacobowitz [this message]
1999-01-03 6:33 ` Paul Mackerras
1999-01-04 5:50 ` Brad Midgley
1999-01-04 9:35 ` Geert Uytterhoeven
1999-01-04 11:38 ` Paul Mackerras
1999-01-17 20:29 ` Daniel Jacobowitz
1999-01-18 20:29 ` Brad Midgley
1999-02-04 0:54 ` Brad Midgley
1999-02-04 1:42 ` Paul Mackerras
1999-02-04 5:56 ` rsync kernel is incomplete Brad Midgley
1999-02-04 6:11 ` Paul Mackerras
1999-02-04 9:29 ` VALETTE Eric
1999-02-04 22:14 ` Brad Midgley
1999-02-04 23:59 ` Paul Mackerras
1999-02-05 5:33 ` modes "default" unfit for general use? Brad Midgley
1999-02-11 18:43 ` scsi hangs [drow@cs.cmu.edu: Re: CD-writers] (fwd) Daniel Jacobowitz
1999-01-19 3:25 ian reinhart geiser
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=19990102201432.A736@drow.res.cmu.edu \
--to=drow@false.org \
--cc=brad@pht.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=satadru@umich.edu \
/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.