All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Brad Midgley <brad@pht.com>
Cc: Paul.Mackerras@cs.anu.edu.au, linuxppc-dev@lists.linuxppc.org,
	geiseri@msoe.edu
Subject: Re: scsi hangs [drow@cs.cmu.edu: Re: CD-writers] (fwd)
Date: Thu, 11 Feb 1999 13:43:29 -0500	[thread overview]
Message-ID: <19990211134328.A16812@drow.res.cmu.edu> (raw)
In-Reply-To: <Pine.LNX.3.95.990203174811.1985A-100000@pacific.pht.com>; from Brad Midgley on Wed, Feb 03, 1999 at 05:54:38PM -0700


On Wed, Feb 03, 1999 at 05:54:38PM -0700, Brad Midgley wrote:
> i did a successful burn today! woohoo!
> 
> cdrecord: fifo was 0 times empty and 13164 times full, min fill was 92%.
> 
> the solution was to move the hard drive with the data on it to the
> internal scsi bus on my 7500. the burner (a ricoh) is still on the
> 53c94. 
> 
> so... the 53c94 driver currently doesn't allow enough access to regular
> hard drives when you're using the generic device. i don't know how this
> relates to disconnect/reconnect or the scheduler. 
> 
> it isn't going to be an option for everybody to move their source drives
> to another bus but at least we know burning works in some configurations. 

This is interesting - my failed burns were from internal HD to external
burner.  They do work now, though, with Paul's evil interrupt-disabling
patch to sd.c.  I couldn't track down why the interrupts were
incorrectly enabled...

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

  parent reply	other threads:[~1999-02-11 18:43 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
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               ` Daniel Jacobowitz [this message]
1999-01-19  3:25 scsi hangs [drow@cs.cmu.edu: Re: CD-writers] (fwd) 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=19990211134328.A16812@drow.res.cmu.edu \
    --to=drow@false.org \
    --cc=Paul.Mackerras@cs.anu.edu.au \
    --cc=brad@pht.com \
    --cc=geiseri@msoe.edu \
    --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 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.