public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Schulman <andrex@alumni.utexas.net>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-scsi@vger.kernel.org, Jamie Lenehan <lenehan@twibble.org>
Subject: Re: dc395x: can't write to tape
Date: Fri, 7 Jan 2005 05:52:57 -0500	[thread overview]
Message-ID: <200501070552.57607.andrex@alumni.utexas.net> (raw)
In-Reply-To: <Pine.LNX.4.60.0501062138580.7568@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.  I reported on it several months 
ago on this list 
(http://marc.theaimsgroup.com/?l=linux-scsi&m=108039964822342&w=2) in 
connection with a balky CD burner, which I've since junked.  After some work 
and upgrading my kernel, I got the CD burner working again, but the flood of 
sg_to_virt failed messages continued.  Jaime finally recommended that I just 
disable them, which I did until I got rid of the CD burner.  Maybe 
relevant...

> > 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.
>
> > Jan  5 22:50:18 helium kernel: ASC=80 ASCQ=98
>
> Additional sense code 0x80 - vendor specific.
>
> So, the sense codes indicate a hardware problem on the tape drive, but the
> first message might mean a software bug. You don't have highmem on that
> machine (> 1GB RAM), do you?

CONFIG_HIGHMEM4G is enabled in the kernel, and I have 1 GiB of RAM.

Thanks,
Andrew.

  reply	other threads:[~2005-01-07 10:52 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 [this message]
2005-01-07 20:13     ` Guennadi Liakhovetski
2005-01-08 21:42       ` Guennadi Liakhovetski
2005-01-11 15:19       ` Andrew Schulman
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=200501070552.57607.andrex@alumni.utexas.net \
    --to=andrex@alumni.utexas.net \
    --cc=g.liakhovetski@gmx.de \
    --cc=lenehan@twibble.org \
    --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