From: Andrew Schulman <andrex@alumni.utexas.net>
To: linux-scsi@vger.kernel.org
Subject: Re: dc395x: can't write to tape
Date: Tue, 11 Jan 2005 10:19:06 -0500 [thread overview]
Message-ID: <200501111019.06281.andrex@alumni.utexas.net> (raw)
In-Reply-To: <Pine.LNX.4.60.0501072057500.6238@poirot.grange>
> > > > Jan 5 22:50:18 helium kernel: dc395x: sg_update_list: sg_to_virt
> > > > failed
> > >
> > > This doesn't look good. However, after a brief look at the code, I
> > > cannot say what exactly went wrong there. Jamie?
> >
> > I didn't mention it before, but I've gotten that particular message for a
> > long time, even when the tape drive used to work.
>
> Could you try disabling highmem either try a kernel without highmem
> support, or boot with mem=900M, or remove a part of your RAM (if you
> don't have to saw your RAMs for that:-)), maybe, booting with highmem=0,
> or with nohighio.
Okay, I finally got to this. Rebooted with mem=900M. Unfortunately tar fails
as before:
tar: /dev/st0: Wrote only 0 of 10240 bytes
tar: Error is not recoverable: exiting now
I had rebuilt dc395x with
#define DEBUG_MASK (DBG_0|DBG_1|DBG_SG|DBG_FIFO|DBG_PIO)
uncommented in dc395x.c. Here's what I got:
# tail -40 /var/log/kern.log
Jan 11 06:29:18 helium kernel: dc395x: srb_done: (pid#4596449) <02-0>
Jan 11 06:29:18 helium kernel: dc395x: srb_done: srb=f6aa2eec sg=0(0/1)
buf=e7c64000 addr=e7c64000
Jan 11 06:29:18 helium kernel: dc395x: srb_done: AUTO_REQSENSE1
Jan 11 06:29:18 helium kernel: dc395x: pci_unmap_srb_sense: buffer=12a69452
Jan 11 06:29:18 helium kernel: dc395x: ReqSense: MEDIUM_ERROR cmnd=0x10 <02-0>
stat=0 scan=1 sense=0x03 ASC=0x0c ASCQ=0x00 (0x00000000 0x00000000)
Jan 11 06:29:18 helium kernel: dc395x: srb_done: AUTO_REQSENSE2
Jan 11 06:29:18 helium kernel: dc395x: srb_going_remove: (pid#4596449) <02-0>
srb=f6aa2eec
Jan 11 06:29:18 helium kernel: dc395x: srb_done: (pid#4596449) done
result=0x08000002
Jan 11 06:29:18 helium kernel: dc395x: srb_free_insert: srb=f6aa2eec
Jan 11 06:29:18 helium kernel: st0: Error with sense data: Current st0: sense
= 70 3
Jan 11 06:29:18 helium kernel: ASC= c ASCQ= 0
Jan 11 06:29:18 helium kernel: Raw sense data:0x70 0x00 0x03 0x00 0x00 0x00
0x00 0x0a 0x00 0x00 0x00 0x00 0x0c 0x00 0x00 0x00 0x00 0x00
Jan 11 06:29:18 helium kernel: st0: Error on write filemark.
Jan 11 06:29:18 helium kernel: dc395x: queue_command: (pid#4596450) <02-0>
cmnd=0x01
Jan 11 06:29:18 helium kernel: dc395x: srb_get_free: srb=f6aa2f2c
Jan 11 06:29:18 helium kernel: dc395x: build_srb: (pid#4596450) <02-0>
Jan 11 06:29:18 helium kernel: dc395x: build_srb: [0] len=0 buf=e7c64000
use_sg=0 !MAP=277c0000
Jan 11 06:29:18 helium kernel: dc395x: start_scsi: (pid#4596450) <02-0>
srb=f6aa2f2c
Jan 11 06:29:18 helium kernel: dc395x: srb_going_append: (pid#4596450) <02-0>
srb=f6aa2f2c
Jan 11 06:29:18 helium kernel: dc395x: queue_command: (pid#4596450) done
Jan 11 06:29:18 helium kernel: dc395x: msgin_phase1: (pid#4596450)
Jan 11 06:29:18 helium kernel: dc395x: msgin_phase0: (pid#4596450)
Jan 11 06:29:18 helium kernel: dc395x: msgin_phase0: (pid#4596450) SAVE
POINTER rem=0 Ignore
Jan 11 06:29:18 helium kernel: dc395x: msgin_phase1: (pid#4596450)
Jan 11 06:29:18 helium kernel: dc395x: msgin_phase0: (pid#4596450)
Jan 11 06:29:18 helium kernel: dc395x: disconnect: (pid#4596450)
Jan 11 06:30:41 helium kernel: dc395x: reselect: acb=f6aa21e4
Jan 11 06:30:41 helium kernel: dc395x: reselect: select <2>
Jan 11 06:30:41 helium kernel: dc395x: status_phase1: (pid#4596450) <02-0>
Jan 11 06:30:41 helium kernel: dc395x: status_phase0: (pid#4596450) <02-0>
Jan 11 06:30:41 helium kernel: dc395x: disconnect: (pid#4596450)
Jan 11 06:30:41 helium kernel: dc395x: srb_done: (pid#4596450) <02-0>
Jan 11 06:30:41 helium kernel: dc395x: srb_done: srb=f6aa2f2c sg=0(0/0)
buf=e7c64000 addr=e7c64000
Jan 11 06:30:41 helium kernel: dc395x: srb_going_remove: (pid#4596450) <02-0>
srb=f6aa2f2c
Jan 11 06:30:41 helium kernel: dc395x: srb_done: (pid#4596450) done
result=0x00000000
Jan 11 06:30:41 helium kernel: dc395x: srb_free_insert: srb=f6aa2f2c
The log file is 2.8 GB uncompressed after this operation. Let me know if it
would be helpful to see more of it and I can post it (or part of it) on my
web site for download.
> > > > Jan 5 22:50:18 helium kernel: st0: Error with sense data: Info
> > > > fld=0x67, Current st0: sense = f0 4
> > >
> > > Sense key 4 - hardware error.
I notice that the sense key is 3 this time.
> Still, your tape problem seems to be unrelated. Do you have a chance to
> test it in another system / with another controller?
Not now, although I may replace the controller just as something to try. That
would be much cheaper than a new tape drive.
I have your other suggestions and will get to them as soon as I have time.
A.
next prev parent reply other threads:[~2005-01-11 15:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 10:18 dc395x: can't write to tape Andrew Schulman
2005-01-06 21:48 ` Guennadi Liakhovetski
2005-01-07 10:52 ` Andrew Schulman
2005-01-07 20:13 ` Guennadi Liakhovetski
2005-01-08 21:42 ` Guennadi Liakhovetski
2005-01-11 15:19 ` Andrew Schulman [this message]
2005-01-11 22:16 ` Guennadi Liakhovetski
2005-01-12 8:58 ` Andrew Schulman
2005-01-09 5:33 ` Jamie Lenehan
2005-01-09 11:42 ` Guennadi Liakhovetski
2005-01-09 12:51 ` Jamie Lenehan
2005-01-22 23:20 ` Guennadi Liakhovetski
2005-01-27 1:13 ` Andrew Schulman
2005-01-27 20:45 ` Guennadi Liakhovetski
2005-02-06 22:11 ` [PATCH] dc395x fix memory mapping (was Re: dc395x: can't write to tape) Guennadi Liakhovetski
2005-02-21 22:01 ` Guennadi Liakhovetski
2005-02-23 10:16 ` Jamie Lenehan
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=200501111019.06281.andrex@alumni.utexas.net \
--to=andrex@alumni.utexas.net \
--cc=linux-scsi@vger.kernel.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