Date: Fri, 24 Mar 2000 15:19:29 -0700 (MST) From: Nate Williams <nate@yogotech.com> To: Bill Fumerola <billf@chc-chimes.com> Cc: mobile@FreeBSD.ORG, imp@FreeBSD.ORG, Brandon Martus <bmartus@jade.chc-chimes.com> Subject: Re: pcic hangups Message-ID: <200003242219.PAA10551@nomad.yogotech.com> In-Reply-To: <20000324163004.C25438@jade.chc-chimes.com> References: <20000324163004.C25438@jade.chc-chimes.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200003242219.PAA10551>