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: Wed, 12 Jan 2005 03:58:20 -0500 [thread overview]
Message-ID: <200501120358.20963.andrex@alumni.utexas.net> (raw)
In-Reply-To: <Pine.LNX.4.60.0501112252560.11812@poirot.grange>
> > 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 didn't expect disabling highmem to fix _this_ error. But do you still
> see the "dc395x: sg_update_list: sg_to_virt failed" message with 900M?
> Perhaps, the most interesting test would be with my patch...
OK. Yes, with mem=900M, the 'sg_to_virt failed' messages all went away. Will
test the patch when I can.
> ...well, could you just keep the log for now, maybe we'll have a look at
> it later, I'd just first try to fix the highmem problem, before trying to
> figure out what's going on with your tape drive. BTW, when it worked, you
> already had 1G RAM in the PC, right?
Right.
next prev parent reply other threads:[~2005-01-12 8:58 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
2005-01-11 22:16 ` Guennadi Liakhovetski
2005-01-12 8:58 ` Andrew Schulman [this message]
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=200501120358.20963.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