Date: Fri, 16 Apr 2004 15:52:41 +0300 From: Niki Denev <nike_d@cytexbg.com> To: freebsd-current@freebsd.org Subject: Re: ndis0 hangs system hard (cvsup'ed today) Message-ID: <20040416125241.GB695@phobos.totalterror.net> In-Reply-To: <20040415.141141.55831932.imp@bsdimp.com> References: <20040415173533.GB38378@kaktusas.org> <20040415181057.GA41370@kaktusas.org> <20040415.141141.55831932.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Apr 15, 2004 at 02:11:41PM -0600, M. Warner Losh wrote: > In message: <20040415181057.GA41370@kaktusas.org> > Paulius Bulotas <paulius@kaktusas.org> writes: > : cvsuped '2 days ago' and here I am using wireless again ;) > : > Any ideas? > : > I'll try to revert last changes to ndis... > > hw.pci.do_powerstates=0 might be a good first step. It is starting to > look like something is broken there, but it is unclear what. > > Warner > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > With today cvsupped machine (ThinkPad X31), with hw.pci.do_powerstate=1 i get a panic every time i try to kldload if_ndis (Intel 2100 3B). with powerstate=0 everything seems to be ok. A few days ago i posted about this panic, but then i was not sure what was causing it, but today after several tests, it seems that 'powerstate' must be causing it. Maybe i will put 'hw.pci.do_powerstate=0' in my loader.conf for now. :( -- Niki Denev
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040416125241.GB695>