From owner-freebsd-scsi@FreeBSD.ORG  Sun Jul 27 23:09:11 2003
Return-Path: <owner-freebsd-scsi@FreeBSD.ORG>
Delivered-To: freebsd-scsi@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id AEA6237B401; Sun, 27 Jul 2003 23:09:11 -0700 (PDT)
Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id E34CC43F3F; Sun, 27 Jul 2003 23:09:09 -0700 (PDT)
	(envelope-from bde@zeta.org.au)
Received: from gamplex.bde.org (katana.zip.com.au [61.8.7.246])
	by mailman.zeta.org.au (8.9.3p2/8.8.7) with ESMTP id QAA15322;
	Mon, 28 Jul 2003 16:08:54 +1000
Date: Mon, 28 Jul 2003 16:08:53 +1000 (EST)
From: Bruce Evans <bde@zeta.org.au>
X-X-Sender: bde@gamplex.bde.org
To: "Justin T. Gibbs" <gibbs@scsiguy.com>
In-Reply-To: <2851045408.1059363460@aslan.scsiguy.com>
Message-ID: <20030728160837.T2380@gamplex.bde.org>
References: <20030728092953.L8406-100000@hewey.af.speednet.com.au>
 <2851045408.1059363460@aslan.scsiguy.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: "'freebsd-scsi@freebsd.org'" <freebsd-scsi@freebsd.org>
cc: aic7xxx@freebsd.org
cc: Andy Farkas <andyf@speednet.com.au>
Subject: Re: AIC7902 w/ seagate U320 drive issue on releng-4 (and current)
X-BeenThere: freebsd-scsi@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: SCSI subsystem <freebsd-scsi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
	<mailto:freebsd-scsi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-scsi>
List-Post: <mailto:freebsd-scsi@freebsd.org>
List-Help: <mailto:freebsd-scsi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
	<mailto:freebsd-scsi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Jul 2003 06:09:12 -0000

On Sun, 27 Jul 2003, Justin T. Gibbs wrote:

> > Dear scsi gurus, please fix the above messages.
>
> It is not a problem with the driver, but with syslog.  I'd be
> happy to review and commit a fix to syslog should you provide it.

The problem seems to be in both the kernel and the driver.  '<' at the
beginning of a line means the beginning of an encoded priority, so
drivers shouldn't use '<<<' to ornate messages.  Encoded priorities have
the form '<'{<digit>}'>', so "<<< Message >>>" is a syntax error.
syslogd's parsing of encoding priorities is a little sloppy.  I think
it inteprets '<'<non-digit> as priority 0 and discards the first '<'.
Priority 0 == LOG_EMERG is a little different from the default kernel
priority of DEVSPRI = LOG_KERN | LOG_CRIT == LOG_CRIT.

Removing the newline accidentally avoids the problem by misformatting
"<<<" to not start on a new line.

Bruce