From: Daniel Eisenbud <eisenbud@cs.swarthmore.edu>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: mesh SCSI bus locks hard on 7500 when burning a CD-R in dao mode
Date: Sun, 28 Jan 2001 00:11:47 -0500 [thread overview]
Message-ID: <20010128001147.B9218@allspice.cs.swarthmore.edu> (raw)
In-Reply-To: <20010128000929.A9218@allspice.cs.swarthmore.edu>; from eisenbud@cs.swarthmore.edu on Sun, Jan 28, 2001 at 12:09:29AM -0500
[-- Attachment #1: Type: text/plain, Size: 1082 bytes --]
Oops, I forgot to actually attach the file. If anyone wants to see this
and has trouble with reading MIME attachments, just email me and I'll
send you a plaintext copy -- I figured I compress and attach it to spare
the whole list a 20K email.
-Daniel
On Sun, Jan 28, 2001 at 12:09:29AM -0500, Daniel Eisenbud <eisenbud@cs.swarthmore.edu> wrote:
> Attached is strace output from cdrdao. I honsetly can't make much of
> it, but maybe someone else will be able to? I'm not sure if it hung in
> the last read or the last write. I think it was the last read, because
> strace printed part of that line and then its output file (which I put
> on a ramdisk, and tarred to a floppy from there, so I wouldn't have to
> copy it by hand once my SCSI bus was useless) didn't change for a while,
> and then the read line finished printing. There's probably a way to
> make strace print timestamps, and I'll do that tomorrow (as well as
> doing this with cdrecord in both disk-at-once and track-at-once modes to
> be able to compare them.
--
Daniel E. Eisenbud
eisenbud@cs.swarthmore.edu
[-- Attachment #2: cdrdao.log.0.gz --]
[-- Type: application/x-gunzip, Size: 3016 bytes --]
next prev parent reply other threads:[~2001-01-28 5:11 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-26 19:48 mesh SCSI bus locks hard on 7500 when burning a CD-R in dao m ode Amit Chaudhary
2001-01-26 20:12 ` Daniel Eisenbud
2001-01-26 20:50 ` Michael Schmitz
2001-01-26 21:04 ` mesh SCSI bus locks hard on 7500 when burning a CD-R in dao mode Daniel Eisenbud
2001-01-26 21:32 ` Michael Schmitz
2001-01-27 21:31 ` Daniel Eisenbud
2001-01-28 0:59 ` Daniel Eisenbud
2001-01-28 1:25 ` Daniel Eisenbud
2001-01-28 2:34 ` Daniel Eisenbud
2001-01-28 5:09 ` Daniel Eisenbud
2001-01-28 5:11 ` Daniel Eisenbud [this message]
2001-01-28 7:16 ` Daniel Eisenbud
2001-01-28 7:17 ` Daniel Eisenbud
2001-01-28 20:24 ` scsi debug info before and after mesh locks up Daniel Eisenbud
2001-01-29 14:29 ` mesh SCSI bus locks hard on 7500 when burning a CD-R in dao mode Michael Schmitz
2001-01-29 23:20 ` Daniel Eisenbud
2001-01-30 21:28 ` Michael Schmitz
2001-01-30 21:35 ` Daniel Eisenbud
2001-01-30 21:46 ` Michael Schmitz
2001-01-30 21:57 ` Daniel Eisenbud
2001-01-31 16:40 ` Chris Boot
2001-02-01 16:50 ` Daniel Eisenbud
2001-02-02 7:38 ` SOLVED: " Daniel Eisenbud
2001-02-02 12:58 ` Michael Schmitz
2001-02-02 15:14 ` Daniel Eisenbud
2001-02-05 12:41 ` Benjamin Herrenschmidt
2001-02-03 4:19 ` Paul Mackerras
2001-02-03 16:14 ` Daniel Eisenbud
2001-02-03 16:27 ` Daniel Eisenbud
2001-02-03 18:48 ` PATCH: " Daniel Eisenbud
2001-02-04 21:37 ` SOLVED: " Michael Schmitz
2001-02-05 8:28 ` Geert Uytterhoeven
2001-01-31 7:10 ` Geert Uytterhoeven
2001-01-29 14:28 ` Michael Schmitz
-- strict thread matches above, loose matches on Subject: below --
2001-01-27 2:23 Iain Sandoe
2001-01-27 21:38 ` Daniel Eisenbud
2001-01-28 1:05 Iain Sandoe
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=20010128001147.B9218@allspice.cs.swarthmore.edu \
--to=eisenbud@cs.swarthmore.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 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).