Date: Wed, 08 Aug 2001 10:27:43 -0600 From: Warner Losh <imp@harmony.village.org> To: Per Andersson <pa@cdg.chalmers.se> Cc: mobile@freebsd.org Subject: Re: pccard patches problem Message-ID: <200108081627.f78GRh123212@harmony.village.org> In-Reply-To: Your message of "Wed, 08 Aug 2001 17:53:39 %2B0200." <Pine.GSO.4.33.0108081714410.3429-500000@wilfer4.cdg.chalmers.se> References: <Pine.GSO.4.33.0108081714410.3429-500000@wilfer4.cdg.chalmers.se>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <Pine.GSO.4.33.0108081714410.3429-500000@wilfer4.cdg.chalmers.se> Per Andersson writes: : I have some trouble with your patches, I have applied them against -stable : from august 6:th about 11:00 UTC. I'm running on a Thinkpad 570E and the : behavior I see is quite strange. : If I use slot 0 it "almost" works, the system doesn't "recognise" a card by : itself when I insert it but if I do a "pccardc power 0 1" it finds it and : assigns I/O adresse and a driver. Network cards doesn't seem to work at : all and with modemcards I only get data from them when I send something, : I guess all this is some interrupt problem. : If I then do a "pccardc power 0 0" it detaches the card, but if I just : remove it the system doesn't notice. OK. Given the date that you updated, the insert/remove part of this is understandible. I didn't MFC the fixes for that on TI chipsets until 14:47 UTC. It also sounds like the cards aren't getting their interrupts for some reason. Not sure why. Maybe my patches will fix it, or maybe not. It will definitely fix the card insert/remove problems. Maybe you could update to Aug 7th or later -stable and try again. If it still fails, can you send me pciconf -r pci0:2:0 0:0xff pciconf -r pci0:2:1 0:0xff pccardc rdreg so I can look at all the register settings. Maybe something isn't getting setup properly that defaults to what we want on my laptop. I notice you have a TI-1450 chipset. I have the TI-4451, which is very close to yours except it also has the firewire interface in it too. Also, make sure that you are using the patched pccardd (but it looks like you may be, but I'm just trying to cover all bases.). : If I use slot 1, the system freezes and I have to power it off to recover, : no output on the console. If I have a card in slot 1 when booting it freezes : just after printing "pccard1: <PC Card bus (classic)> on pcic1" Again, sounds like an interrupt problem of some sort. Since it freezes just after printing the pcic child attachment, my guess is that it is enabling interrupts that are being routed somewhere else and we're not fielding them. This surprises me a little since I'd only expect that behavior on machines where pcic0 and pcic1 have different irqs and it appears that your machine assigns 11 to both. Warner 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?200108081627.f78GRh123212>