From owner-freebsd-bugs@FreeBSD.ORG Wed Jun 4 00:30:13 2003 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3603037B401 for ; Wed, 4 Jun 2003 00:30:13 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF4F243F3F for ; Wed, 4 Jun 2003 00:30:12 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h547UCUp027189 for ; Wed, 4 Jun 2003 00:30:12 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h547UCBT027188; Wed, 4 Jun 2003 00:30:12 -0700 (PDT) Date: Wed, 4 Jun 2003 00:30:12 -0700 (PDT) Message-Id: <200306040730.h547UCBT027188@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: "Greg 'groggy' Lehey" Subject: Re: kern/52916: vinum causes panic after start/stop/... cycle, easy to reproduce X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Greg 'groggy' Lehey List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jun 2003 07:30:13 -0000 The following reply was made to PR kern/52916; it has been noted by GNATS. From: Greg 'groggy' Lehey To: Pawel Malachowski Cc: FreeBSD-gnats-submit@FreeBSD.org Subject: Re: kern/52916: vinum causes panic after start/stop/... cycle, easy to reproduce Date: Wed, 4 Jun 2003 16:57:26 +0930 --L4xCDQ7GT+ph8Lmk Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tuesday, 3 June 2003 at 22:39:16 -0000, Pawel Malachowski wrote: > >> Number: 52916 >> Category: kern >> Synopsis: vinum causes panic after start/stop/... cycle, easy to r= eproduce >> Confidential: no >> Severity: critical >> Priority: high >> Responsible: freebsd-bugs >> State: open >> Quarter: >> Keywords: >> Date-Required: >> Class: sw-bug >> Submitter-Id: current-users >> Arrival-Date: Tue Jun 03 15:40:06 PDT 2003 >> Closed-Date: >> Last-Modified: >> Originator: Pawe=B3 Ma=B3achowski >> Release: FreeBSD 4.8-STABLE i386 >> Organization: > ZiN >> Environment: > FreeBSD 4.8-RELEASE FreeBSD 4.8-RELEASE #0: Thu Apr 3 10:53:38 GMT 2003 > root@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/GENERIC i386 > > >> Description: > Both 4.8-RELEASE and fresh 4.8-STABLE (on two different machines) catch > kernel panic when I try something like: > vinum start;vinum stop;vinum start;vinum stop;vinum start;vinum stop > > It is very easy to reproduce. I was not able to reproduce it. > 4.8-STABLE was compiled with debug symbols, unfortunately there is > no crashdump. What's the problem? Do you have crash dumps enabled? > Panic message from 4.8-STABLE (vinum as kld): > > vinum: loaded > vinum: no drives found > vinum: unloaded > vinum: loaded > vinum: no drives found > vinum: unloaded > vinum: loaded > > > Fatal trap 12: page fault while in kernel mode Sorry, this doesn't help at all. At the very least I'd need to know what the EIP address was. > fault virtual address =3D 0xb7 > fault code =3D supervisor read, page not present > instruction pointer =3D 0x8:0xc01bedc8 This one. > So I compiled vinum statically into kernel, > > # vinum start;vinum stop;vinum start;vinum stop; > ** no drives found: No such file or directory > Can't unload vinum: No such file or directory > ** no drives found: No such file or directory > Can't unload vinum: No such file or directory > > and it crashed again with message like this: > > vinum: no drives found > vinum: no drives found You shouldn't be able to stop Vinum with a statically compiled module. > Also note: > kldload vinum;kldunload vinum;kldload vinum;kldunload vinum; > doesn't produce panic on my machine. That's something, I suppose. > I caught first panic when I tried `vinum stop' while reviving > subdisk I assume this is something else. I'd really like to find out what's happening here; we have two separate reports of a bug I haven't seen before, but I can't reproduce it here, neither with 4.7-RELEASE nor with the current 4.8-STABLE. Any further information would be welcome. Greg -- See complete headers for address and phone numbers --L4xCDQ7GT+ph8Lmk Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQE+3Z9eIubykFB6QiMRAtO0AJwOhVFbjS8nNxFEf3n16qf87B7ZhwCeK/b+ YWYdOtlHzheJYPswiForaqs= =V5qj -----END PGP SIGNATURE----- --L4xCDQ7GT+ph8Lmk--