From owner-freebsd-mobile Fri Mar 24 14:19:38 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.79.126]) by hub.freebsd.org (Postfix) with ESMTP id 0839537BD85; Fri, 24 Mar 2000 14:19:32 -0800 (PST) (envelope-from nate@yogotech.com) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.79.115]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id PAA05074; Fri, 24 Mar 2000 15:19:29 -0700 (MST) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id PAA10551; Fri, 24 Mar 2000 15:19:29 -0700 (MST) (envelope-from nate) Date: Fri, 24 Mar 2000 15:19:29 -0700 (MST) Message-Id: <200003242219.PAA10551@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Bill Fumerola Cc: mobile@FreeBSD.ORG, imp@FreeBSD.ORG, Brandon Martus Subject: Re: pcic hangups In-Reply-To: <20000324163004.C25438@jade.chc-chimes.com> References: <20000324163004.C25438@jade.chc-chimes.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > A friend of mine recently let me poke around on his laptop after he > said really freaky things were happening with his laptop. Here's the > scoop: > > There is only one (physical) slot on this laptop. The controller may support 2, > the controller may think it has two, but I assure you there is one slot. > > If a card is in this physical slot during boot, the boot hangs: > > --- interrupt, eip = 0xc01ddd77, esp = 0xc0269fa0, ebp = 0xc0269fb0 --- > putb1(c028cfc0,3,60,c028cfc0,3) at putb1+0x23 > pcic_reset(c0829800,40000000,c04b0c90,0,ffffffff) at pcic_reset+0x64 > softclock(0,c0236bce,c0232de7,0,0) at softclock+0xd1 > splz_swi(5,58c,1,8021bf,68747541) at splz_swi+0x14 > idle_loop() at idle_loop+0x13 > > Which after applying my kernel-stupid mind to pcic.c tells me that during > pcic_reset() timeout() is never returning or is in some inifinite loop or > another equally bad thing. Try setting one of the APM flags that is related to broken statclock, which can cause these kinds of problems. If the statclock is broken, you may not get woken up, since the clock isn't working as advertised. I don't remember which flag it is, but you should be able to look at the documentation to find it. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message