Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 3 Oct 97 21:17 CDT
From:      uhclem.bsd@nemesis.lonestar.org
To:        FreeBSD-gnats-submit@FreeBSD.ORG
Subject:   kern/4685: Some SCSI retry messages formatted differently - FDIV072
Message-ID:  <m0xHJmX-000txrC@nemesis.lonestar.org>
Resent-Message-ID: <199710040630.XAA00484@hub.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         4685
>Category:       kern
>Synopsis:       Some SCSI retry messages formatted differently - FDIV072
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Oct  3 23:30:01 PDT 1997
>Last-Modified:
>Originator:     Frank Durda IV
>Organization:
None
>Release:        FreeBSD 2.2.5-971003-BETA
>Environment:

Pentium 133 system, 128Meg, PCI 2940 or 2940U SCSI, as follows:

All entries Oct  3	(and "/kernel" has been stripped for readability)
17:05:11 cabal1: FreeBSD 2.2.5-971003-BETA #0: Fri 16:51:38 CDT 1997
17:05:11 cabal1:     uhclem.bsd@handsoff:/usr/src/sys.new/sys/compile/CABAL1
17:05:11 cabal1: CPU: Pentium (132.96-MHz 586-class CPU)
17:05:11 cabal1:   Origin = "GenuineIntel"  Id = 0x52c  Stepping=12
17:05:11 cabal1:   Features=0x1bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8>
17:05:11 cabal1: real memory  = 134217728 (131072K bytes)
17:05:11 cabal1: avail memory = 129269760 (126240K bytes)
17:05:11 cabal1: ahc0: aic7880 Single Channel, SCSI Id=7, 16 SCBs
17:05:11 cabal1: (ahc0:0:0): "QUANTUM FIREBALL ST4.3S 0F0C" type 0 fixed SCSI 2
17:05:11 cabal1: sd0(ahc0:0:0): Direct-Access 4136MB (8471232 512 byte sectors)
17:05:11 cabal1: (ahc0:3:0): "SEAGATE ST19171N 0017" type 0 fixed SCSI 2
17:05:11 cabal1: sd1(ahc0:3:0): Direct-Access 8683MB (17783112 512 byte sectors)

>Description:

For most read (or alleged) errors, the SCSI driver returns a two-line message
like this:

18:42:19 cabal1: sd1(ahc0:3:0): RECOVERED ERROR info:0x468f80 asc:17,1 Recovered data with retries field replaceable unit: ea sks:80,1
18:42:19 cabal1: , retries:4

The problem here is that sometimes the second message ", retries:4"
gets separated from the first line by one or more lines in the log,
particularly on a system receiving syslog info from several terminal
servers or other application.

This second bit of the SCSI error message should be part of the first
message, or the second line should repeat the device information as in
"sd1(ahc0:3:0): retries:4".


Also, there is at least one similar error message in the SCSI driver that
is split across three lines:

19:44:33 cabal1: sd1(ahc0:3:0): RECOVERED ERROR info:0x4b8a77 asc:18,1
19:44:33 cabal1: sd1(ahc0:3:0):  Recovered data with error correction & retries applied field replaceable unit: ea sks:80,1
19:44:33 cabal1: , retries:4

I actually think this second layout where the description is on the second line
is easier to read, but even in this case the trailing ", retries:4" info
needs to be put on the end of one of the other lines.

The leading space on the second (and third) lines of the messages should
be cleaned up while working in the neighborhood too.

>How-To-Repeat:

Get the SCSI driver to report some disk errors, or something it thinks
are disk errors.

>Fix:
	
>Audit-Trail:
>Unformatted:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m0xHJmX-000txrC>