kern/52916: vinum causes panic after start/stop/... cycle, easy
to reproduce
Greg 'groggy' Lehey
grog at FreeBSD.org
Wed Jun 4 00:30:13 PDT 2003
The following reply was made to PR kern/52916; it has been noted by GNATS.
From: Greg 'groggy' Lehey <grog at FreeBSD.org>
To: Pawel Malachowski <pawmal at unia.3lo.lublin.pl>
Cc: FreeBSD-gnats-submit at 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 at 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--
More information about the freebsd-bugs
mailing list