From: Daniel Jacobowitz <drow@false.org>
To: Paul.Mackerras@cs.anu.edu.au
Cc: brad@pht.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: scsi hangs [drow@cs.cmu.edu: Re: CD-writers] (fwd)
Date: Sun, 17 Jan 1999 15:29:14 -0500 [thread overview]
Message-ID: <19990117152914.A12471@drow.res.cmu.edu> (raw)
In-Reply-To: <199901041138.WAA00533@tango.anu.edu.au>; from Paul Mackerras on Mon, Jan 04, 1999 at 10:38:45PM +1100
On Mon, Jan 04, 1999 at 10:38:45PM +1100, Paul Mackerras wrote:
> Brad Midgley <brad@pht.com> wrote:
>
> > i have tried out the current vger kernel and i'd characterize it as "five
> > times" as stable. meaning i can copy 125 megabytes from a jaz on the
> > external bus to a drive on the internal bus before it crashes--with
> > 2.1.130 i could only copy about 25 megabytes before it crashed. the error
> > when it crashes is always:
>
> Actually, I'm not sure that the vger version had the locking exactly
> right before. The version in vger is now the same as the version
> currently in the official tree, and I am moderately confident it's OK.
> If you can reproduce it with that version, I really will have to dig
> deeper.
>
> We will never get the sd.c patch into the official version because it
> breaks SMP machines. I know because that's what happened on my SMP
> powermac. :-)
I don't have the exact messages, but attempting to use an external CDR
(boot drive on MESH, burner on 53c94) locks up with a bunch of illegal
sense requests. Then it tries to reset the external bus, times out,
claims to try harder, and more or less locks up.
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-17 20:29 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
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 [this message]
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=19990117152914.A12471@drow.res.cmu.edu \
--to=drow@false.org \
--cc=Paul.Mackerras@cs.anu.edu.au \
--cc=brad@pht.com \
--cc=linuxppc-dev@lists.linuxppc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).