From owner-freebsd-stable@FreeBSD.ORG  Fri Nov  7 10:56:42 2003
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 0780316A4CE; Fri,  7 Nov 2003 10:56:42 -0800 (PST)
Received: from smtp.atlantis.dp.ua (smtp.atlantis.dp.ua [193.108.46.231])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 8FF9B43F75; Fri,  7 Nov 2003 10:56:39 -0800 (PST)
	(envelope-from dmitry@atlantis.dp.ua)
Received: from smtp.atlantis.dp.ua (smtp.atlantis.dp.ua [193.108.46.231])
	by smtp.atlantis.dp.ua (8.12.6p2/8.12.6) with ESMTP id hA7IuRvx041239;
	Fri, 7 Nov 2003 20:56:27 +0200 (EET)
	(envelope-from dmitry@atlantis.dp.ua)
Date: Fri, 7 Nov 2003 20:56:27 +0200 (EET)
From: Dmitry Pryanishnikov <dmitry@atlantis.dp.ua>
To: freebsd-stable@freebsd.org
Message-ID: <20031107204321.I38571@atlantis.atlantis.dp.ua>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: Dmitry Morozovsky <marck@rinet.ru>
cc: sos@freebsd.org
Subject: Re: panic at ata-dma: transfer active on this device!
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Nov 2003 18:56:42 -0000


Hello!

Dmitry Morozovsky <marck@rinet.ru> wrote:
> Dear Soeren,
>
> I've got almost reproducible panic at one of our machine (possibly related
> to next-to-failing disk). Backtraces from kernel dump (when kernel is able
> to re-init ata0, otherwise dump is unavailable, of course) look as follow.
> ad0: 39266MB <IC35L040AVER07-0> [79780/16/63] at ata0-master tagged UDMA100

 It looks as a duplicated PR kern/57174. IMHO to avoid such questions in
future the following steps should be made:

1. Add the entry to 4.9-RELEASE Errata (and/or UPDATING) about broken tagged
   queueing in ata(4).

2. Fix ata(4)+tagged queueing in -STABLE, test the fix, optionally MFS it to
   RELENG_4_9.

I understand that (2) would be rather difficult, but I think that (1) should
be done ASAP!

Sincerely, Dmitry
-- 
Atlantis ISP, System Administrator
e-mail:  dmitry@atlantis.dp.ua
nic-hdl: LYNX-RIPE