From owner-freebsd-bugs  Mon Sep 18  1:53:12 2000
Delivered-To: freebsd-bugs@freebsd.org
Received: from tuminfo2.informatik.tu-muenchen.de (tuminfo2.informatik.tu-muenchen.de [131.159.0.81])
	by hub.freebsd.org (Postfix) with ESMTP
	id 3C10437B43C; Mon, 18 Sep 2000 01:53:10 -0700 (PDT)
Received: from atrbg11.informatik.tu-muenchen.de ([131.159.9.196] HELO atrbg11.informatik.tu-muenchen.de ident: SOCKFAULT1 [port 1143]) by tuminfo2.informatik.tu-muenchen.de with SMTP id <110652-245>; Mon, 18 Sep 2000 10:53:02 +0000
Received: by atrbg11.informatik.tu-muenchen.de (Postfix, from userid 20455)
	id 90CA013607; Mon, 18 Sep 2000 10:52:49 +0200 (CEST)
From: Daniel Lang <dl@leo.org>
To: grog@FreeBSD.org
Cc: freebsd-bugs@FreeBSD.org, freebsd-gnats-submit@freebsd.org
Subject: Re: kern/21148: multiple crashes while using vinum
Illegal-Object: Syntax error in Message-ID: value found on tuminfo2.informatik.tu-muenchen.de:
	Message-ID:	<20000918105249.F7763@atrbg11.informatik.tu-muenchen.>
									     ^-illegal subdomain in domain, propably extra '.' at the end of the address
References: <200009100106.SAA58198@freefall.freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <200009100106.SAA58198@freefall.freebsd.org>; from grog@FreeBSD.org on Sun, Sep 10, 2000 at 03:08:11AM +0000
X-Geek: GCS d-- s: a- C++ UB++++$ P+++$ L- E W+++(--) N+ o K w--- O? M- V@ PS+(++) PE--(+) Y+ PGP+ t++ 5@ X R+(-) tv+ b+ DI++ D++ G++ e+++ h---(-) r++>+++ y
Date:	Mon, 18 Sep 2000 10:52:52 +0000
Message-Id: <20000918085310.3C10437B43C@hub.freebsd.org>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Hi,

to further trace the problem, as the crash-dumps seemed not
to produce any usable stack traces, I hooked the box up to a
remote debugging session with DDB/GDB.
(No problem to panic the box, as described).

As far as I can tell, the crash did not happen inside the
vinum-module. This may be the cause, why your .gdbinit scripts
don't seem to apply, I guess.
The crash happened inside the ata driver, but it seems that a 
former valid pointer is overwritten somehow, so that it contains
garbage, which leads to the crash
(I assume that the 'struct ata_softc' is corrupted).

This probably comes from a buffer overrun somewhere else, that
writes into already allocated memory. Unfortunately such errors
are very difficult to trace (well at least for my experience).
Since the error only appears on the system with a vinum RAID-5
and only and reproducible while accessing this filesystem,
I (possibly naive) assume it must be a problem with vinum.

Unfortunatelty I guess we are stuck here, since I am not able
to produce more data that could help with the problem.

However I would grant access to the machine and the debugger,
if someone would like to inspect the situation personally.

Best regards,
 Daniel Lang
-- 
IRCnet: Mr-Spock              - Truth lies in the eye of the beholder - 
*Daniel Lang * dl@leo.org * +49 89 289 25735 * http://www.leo.org/~dl/*


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message