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$[EMAIL PROTECTED]>, 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 [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
