Date: Wed, 20 Dec 2000 18:40:04 -0700 (MST) From: Nate Williams <nate@yogotech.com> To: Mike Smith <msmith@FreeBSD.ORG> Cc: nate@yogotech.com (Nate Williams), freebsd-stable@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: 4.1.1 and 4.2 halt when booting, Gigabyte GA-6BXU Message-ID: <14913.24436.738115.150910@nomad.yogotech.com> In-Reply-To: <200012210146.eBL1kZa01218@mass.osd.bsdi.com> References: <14913.23812.1233.305120@nomad.yogotech.com> <200012210146.eBL1kZa01218@mass.osd.bsdi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > > I was > > > > wondering if anyone knew of a way to fix this, or if > > > > it will be fixed in the base system, or if there is > > > > some way to completely disable PNP in 4.2. > > > > > > There are no known problems with PnP in 4.2, so there's nothing that's > > > going to be fixed unless we can characterise your problem here. > > > > I'm confused. Others have reported numerous bugs and/or misfeatures > > with the current code (including it failing on at least one ThinkPad > > laptop). > > There's a great deal of confusion between "ISA PnP", "BIOS PnP", and > "Side-effects of BIOS PnP", as well as "reports that something might be > failing" and "known problems". Obviously. :) > The Thinkpad problem appears to be a side-effect of calling the BIOS PnP > interface, but hasn't been characterised. The problem above may or may > not actually be PnP related at all. There are bugs in the PnP > implementation that I've left out of the discussion here because they're > not really relevant to the issue. Thanks for clarifying! > Perhaps it would be fairer to say "if what you're reporting is really > a lockup during the ISA PnP probe, then there are no known problems > related to that feature and thus no plans to fix it at this time". Except that it locks up, so there is apparently a problem (if this is indeed the case). Just because it works for most people doesn't mean it's not broken. When I maintained the laptop stuff, too often it was easy to claim 'broken laptops' for our bugs, but more often than not the bugs turned out to be FreeBSD doing something that 'most laptops didn't seem to mind', but was in fact wrong. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14913.24436.738115.150910>