From: Daniel Eisenbud <eisenbud@cs.swarthmore.edu>
To: Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: mesh SCSI bus locks hard on 7500 when burning a CD-R in dao mode
Date: Mon, 29 Jan 2001 18:20:35 -0500 [thread overview]
Message-ID: <20010129182034.A25828@allspice.cs.swarthmore.edu> (raw)
In-Reply-To: <Pine.LNX.4.30.0101291528550.2636-100000@opal.biophys.uni-duesseldorf.de>; from schmitz@mail.biophys.uni-duesseldorf.de on Mon, Jan 29, 2001 at 03:29:16PM +0100
On Mon, Jan 29, 2001 at 03:29:16PM +0100, Michael Schmitz <schmitz@mail.biophys.uni-duesseldorf.de> wrote:
> > > > So put just that one line redirecting log output to /dev/tty7 into
> > > > syslog.conf temporarily and kill -1 syslogd before starting the test.
> > >
> > > I'll try this variation in a few minutes.
> >
> > This worked, but I didn't get any useful log output until I started
> > getting error 600 from the SCSI midlevel and errors from ext2fs. I'm
> > going to try again, making sure that I have dmesg set as high as
>
> Please report the precise message text.
Here is what appears to be the relevant part of the log. I have more of
it, which I can send to anyone if they need more context. Note that in
the full log, there are _no_ _more_ messages from the mesh driver ever
after the last one you see in this segment. It just crawls into a
corner and dies.
Note that this is from turning mesh debugging on for all hosts in
mesh.c, and turning on SCSI debugging by compiling in the option and
then doing "echo scsi log all > /proc/scsi/scsi".
-Daniel
Jan 29 10:42:50 cumulonimbus kernel: sg_unlink_reserve: req->use_sg=0
Jan 29 10:42:50 cumulonimbus kernel: sg_write: dev=2, count=78
Jan 29 10:42:50 cumulonimbus kernel: Open returning 1
Jan 29 10:42:50 cumulonimbus kernel: sg_write: scsi opcode=0x5d, cmd_size=10
Jan 29 10:42:50 cumulonimbus kernel: sg_start_req: max_buff_size=32
Jan 29 10:42:50 cumulonimbus kernel: sg_link_reserve: size=32
Jan 29 10:42:50 cumulonimbus kernel: sg_write_xfer: num_write_xfer=32, use_sg=0
Jan 29 10:42:50 cumulonimbus kernel: Activating command for device 3 (1)
Jan 29 10:42:50 cumulonimbus kernel: scsi_do_cmd (host = 0, channel = 0 target = 3, buffer =c3490000, bufflen = 32, done = c00e149c, timeout = 20050, retries = 1)
Jan 29 10:42:50 cumulonimbus kernel: command : 5d 00 00 00 00 00 00 00 20 00
Jan 29 10:42:50 cumulonimbus kernel: internal_cmnd (host = 0, channel = 0, target = 3, command = c033c245, buffer = c3490000,
Jan 29 10:42:50 cumulonimbus kernel: bufflen = 32, done = c00e149c)
Jan 29 10:42:50 cumulonimbus kernel: queuecommand : routine at c00e39f4
Jan 29 10:42:50 cumulonimbus kernel: mesh_start: c033c200 ser=1518 tgt=3 cmd= 5d 0 0 0 0 0 0 0 20 0 use_sg=0 buffer=c3490000 bufflen=32
Jan 29 10:42:50 cumulonimbus kernel: leaving internal_cmnd()
Jan 29 10:42:50 cumulonimbus kernel: Leaving scsi_do_cmd()
Jan 29 10:42:50 cumulonimbus kernel: mesh: sending 1 msg bytes: c0
Jan 29 10:42:50 cumulonimbus kernel: sg_read: dev=2, count=36
Jan 29 10:42:50 cumulonimbus kernel: Open returning 1
Jan 29 10:46:10 cumulonimbus kernel: Command timed out active=1 busy=1 failed=1
Jan 29 10:46:11 cumulonimbus kernel: Error handler waking up
Jan 29 10:46:11 cumulonimbus kernel: scsi_unjam_host: Checking to see if we need to request sense
Jan 29 10:46:11 cumulonimbus kernel: Command to ID 3 timedout
Jan 29 10:46:11 cumulonimbus kernel: Total of 0+1 commands on 1 devices require eh work
Jan 29 10:46:11 cumulonimbus kernel: scsi_unjam_host: Checking to see if we want to try abort
Jan 29 10:46:11 cumulonimbus kernel: scsi_unjam_host: Checking to see if we want to try BDR
Jan 29 10:46:11 cumulonimbus kernel: scsi_unjam_host: Try hard bus reset
Jan 29 10:46:11 cumulonimbus kernel: scsi_unjam_host: Try hard host reset
Jan 29 10:46:11 cumulonimbus kernel: scsi_unjam_host: Take device offline
Jan 29 10:46:11 cumulonimbus kernel: Finishing command for device 3 6000000
Jan 29 10:46:11 cumulonimbus kernel: scsi_unjam_host: Returning
Jan 29 10:46:11 cumulonimbus kernel: Clearing timer for command c033c200
Jan 29 10:46:11 cumulonimbus kernel: scsi_error.c: Waking up host to restart
Jan 29 10:46:11 cumulonimbus kernel: Calling request function to restart things...
Jan 29 10:46:11 cumulonimbus last message repeated 2 times
Jan 29 10:46:11 cumulonimbus kernel: scsi_error.c: device offline - report as SUCCESS
Jan 29 10:46:11 cumulonimbus kernel: Command finished 1 0 0x6000000
Jan 29 10:46:11 cumulonimbus kernel: Notifying upper driver of completion for device 3 6000000
Jan 29 10:46:11 cumulonimbus kernel: sg__done: dev=2, scsi_stat=0, res=0x6000000
Jan 29 10:46:11 cumulonimbus kernel: Deactivating command for device 3 (active=0, failed=0)
Jan 29 10:46:11 cumulonimbus kernel: Error handler sleeping
Jan 29 10:46:11 cumulonimbus kernel: sg_finish_rem_req: res_used=1
Jan 29 10:46:11 cumulonimbus kernel: sg_unlink_reserve: req->use_sg=0
--
Daniel E. Eisenbud
eisenbud@cs.swarthmore.edu
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-01-29 23:20 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
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 [this message]
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=20010129182034.A25828@allspice.cs.swarthmore.edu \
--to=eisenbud@cs.swarthmore.edu \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=schmitz@opal.biophys.uni-duesseldorf.de \
/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).