From: Sebastian Frei <Sebastian@schnapsleichen.de>
To: linux-scsi@vger.kernel.org
Subject: dc395x.c: Please, contact ... to help improve support ...
Date: Wed, 8 Mar 2006 13:36:37 +0100 [thread overview]
Message-ID: <200603081336.37840.Sebastian@schnapsleichen.de> (raw)
Hello,
(please CC, I'm not subscribed)
I got during a backup the following messages in the system log:
Mar 8 03:44:08 PINGUIN dc395x: sg_update_list: sg_to_virt failed
Mar 8 03:44:08 PINGUIN dc395x: sg_update_list: sg_to_virt failed
Mar 8 03:44:08 PINGUIN drivers/scsi/dc395x.c: Please, contact
<linux-scsi@vger.kernel.org> to help improve support
for your system.
Mar 8 03:44:08 PINGUIN dc395x: sg_update_list: sg_to_virt failed
Mar 8 03:44:08 PINGUIN dc395x: sg_update_list: sg_to_virt failed
Mar 8 03:44:08 PINGUIN dc395x: sg_update_list: sg_to_virt failed
Mar 8 03:44:08 PINGUIN dc395x: sg_update_list: sg_to_virt failed
Mar 8 03:46:30 PINGUIN dc395x: sg_update_list: sg_to_virt failed
Mar 8 03:46:30 PINGUIN dc395x: sg_update_list: sg_to_virt failed
Mar 8 04:36:21 PINGUIN dc395x: sg_update_list: sg_to_virt failed
Mar 8 04:36:21 PINGUIN dc395x: sg_update_list: sg_to_virt failed
Mar 8 04:39:22 PINGUIN dc395x: sg_update_list: sg_to_virt failed
Mar 8 04:39:22 PINGUIN dc395x: sg_update_list: sg_to_virt failed
Mar 8 04:39:22 PINGUIN dc395x: sg_update_list: sg_to_virt failed
Mar 8 04:39:22 PINGUIN dc395x: sg_update_list: sg_to_virt failed
Mar 8 04:39:22 PINGUIN dc395x: sg_update_list: sg_to_virt failed
Mar 8 04:39:22 PINGUIN dc395x: sg_update_list: sg_to_virt failed
Mar 8 04:39:22 PINGUIN dc395x: sg_update_list: sg_to_virt failed
Mar 8 04:39:22 PINGUIN dc395x: sg_update_list: sg_to_virt failed
It is an opteron, 1GB RAM, a Tekram DC-315U controller with a HP DDS4 tape
drive, connected with a narrow->wide SCSI adaptor.
Some info:
Linux PINGUIN 2.6.15.6 #15 Mon Mar 6 11:30:52 CET 2006 x86_64 x86_64 x86_64
GNU/Linux
Mar 7 19:31:01 PINGUIN dc395x: Tekram DC395(U/UW/F), DC315(U) - ASIC
TRM-S1040 v2.05, 2004/03/08
Mar 7 19:31:01 PINGUIN GSI 19 sharing vector 0xC1 and IRQ 19
Mar 7 19:31:01 PINGUIN ACPI: PCI Interrupt 0000:00:0e.0[A] -> GSI 19 (level,
low) -> IRQ 19
Mar 7 19:31:01 PINGUIN dc395x: Used settings: AdapterID=07, Speed=0(20.0MHz),
dev_mode=0x57
Mar 7 19:31:01 PINGUIN dc395x: AdaptMode=0x0f, Tags=4(16),
DelayReset=1s
Mar 7 19:31:01 PINGUIN dc395x: Connectors: int50 Termination: Auto Low High
Mar 7 19:31:01 PINGUIN dc395x: Performing initial SCSI bus reset
Mar 7 19:31:01 PINGUIN scsi0 : Tekram DC395(U/UW/F), DC315(U) - ASIC
TRM-S1040 v2.05, 2004/03/08
Mar 7 19:31:01 PINGUIN dc395x: Target 03: Sync: 48ns Offset 15 (20.8 MB/s)
Mar 7 19:31:01 PINGUIN Vendor: HP Model: C5683A Rev: C111
Mar 7 19:31:01 PINGUIN Type: Sequential-Access ANSI SCSI
revision: 02
Mar 7 19:31:01 PINGUIN st: Version 20050830, fixed bufsize 1048576, s/g segs
256
Mar 7 19:31:01 PINGUIN st 0:0:3:0: Attached scsi tape st0<4>st0: try direct
i/o: yes (alignment 512 B), max page re
achable by HBA 1048575
Some things I should do ?
S.
next reply other threads:[~2006-03-08 12:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-08 12:36 Sebastian Frei [this message]
2006-03-08 20:30 ` dc395x.c: Please, contact ... to help improve support Guennadi Liakhovetski
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=200603081336.37840.Sebastian@schnapsleichen.de \
--to=sebastian@schnapsleichen.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.