From owner-freebsd-current  Tue Oct 30 16: 9:20 2001
Delivered-To: freebsd-current@freebsd.org
Received: from btclick.com (mta02.btfusion.com [62.172.195.247])
	by hub.freebsd.org (Postfix) with ESMTP id 2E0E437B40C
	for <freebsd-current@FreeBSD.ORG>; Tue, 30 Oct 2001 16:09:11 -0800 (PST)
Received: from heather.plazza.uk ([213.120.117.63]) by
          btclick.com (Netscape Messaging Server 4.05) with ESMTP id
          GM1N3804.ZAW for <freebsd-current@FreeBSD.ORG>; Wed, 31 Oct 2001
          00:09:08 +0000 
Received: from localhost (localhost [127.0.0.1])
	by heather.plazza.uk (8.11.6/8.11.6) with ESMTP id f9V0AFR01546
	for <freebsd-current@FreeBSD.ORG>; Wed, 31 Oct 2001 00:10:15 GMT
	(envelope-from n_hibma@FreeBSD.ORG)
Date: Wed, 31 Oct 2001 00:10:14 +0000 (GMT)
From: Nick Hibma <n_hibma@FreeBSD.ORG>
X-X-Sender: <n_hibma@heather.plazza.uk>
To: <freebsd-current@FreeBSD.ORG>
Subject: Re: WARNING: Driver mistake: destroy_dev on 154/0
In-Reply-To: <XFMail.011030133559.jhb@FreeBSD.org>
Message-ID: <20011031000621.V697-100000@heather.plazza.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG


Yes. I have no idea why phk has not done this.

As this is a purposeful panicing of systems that worked fine before, I
presume that someone is keeping track of the problems that are occurring
and going to do something about it? Or is this a bad case of 'someone
else's problem'?

Nick

On Tue, 30 Oct 2001, John Baldwin wrote:

>
> On 30-Oct-01 Poul-Henning Kamp wrote:
> > In message <000801c1617c$9599ad00$fe02010a@twoflower.liebende.de>, Jan
> > Stocker
> > writes:
> >>Ive updated the first time my system to current (Oct-28, with cvsup). After
> >>a make
> >>buildword and installworld, i made a new GENERIC kernel and copied the file
> >>GENERIC.hints to /boot/device.hints and installed the new kernel. I ve
> >>updated all files in /etc and remade all devices. Now a bootup hangs:
> >>
> >>a) The kernel is loading
> >>b) acpi.ko is loading
> >>c) "Pentium Pro MTRR support enable"
> >>d) "WARNING: Driver mistake: destroy_dev on 154/0"
> >>
> >>next is a kernel panic "dont do that"
> >
> > Remove the asr driver from your kernel config until somebody
> > fixes its use of destroy_dev()
>
> Maybe we should remove it from GENERIC?
>
> Warner, do you think we need an updating entry for this?
>
>


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