From owner-freebsd-mobile Thu Jan 27 19:32:25 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 165BF15985 for ; Thu, 27 Jan 2000 19:32:17 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id WAA22846; Thu, 27 Jan 2000 22:32:15 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id WAA46817; Thu, 27 Jan 2000 22:31:45 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 27 Jan 2000 22:31:45 -0500 (EST) To: Warner Losh Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: pc card removal lockup In-Reply-To: <200001280256.TAA51227@harmony.village.org> References: <14479.50958.672619.722352@grasshopper.cs.duke.edu> <14478.22223.436708.406272@grasshopper.cs.duke.edu> <200001270029.RAA04459@harmony.village.org> <200001280256.TAA51227@harmony.village.org> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14481.3158.953005.86162@grasshopper.cs.duke.edu> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Warner Losh writes: > In message <14479.50958.672619.722352@grasshopper.cs.duke.edu> Andrew Gallatin writes: > : Hmm.. why? I thought that PCIC_RESUME_RESET was to be used when your > : pccards were not found when your machine resumes. But suspend/resume > : works great! (and, in fact, is the only way I can remove cards w/o > : rebooting). > > The theory was that the pcic wasn't properly getting reset after the > suspend/resume. To clarify: I can make the machine lock when removing ep0 immediately after booting the machine. I do not need to suspend/resume to see the problem. > It sounds like your irq for the pcic may be wrong. It also sounds > like we can't get away with polling mode as default. More on why > below. What does the pcic-pci line on your laptop say? You may have > already posted this, if so please forgive me. pcic-pci0: port 0x3e0-0x3e3 at device 4.0 on pci0 PCI Config space: 00: 11001013 04000183 060500ee 00000000 10: 000003e1 00000000 00000000 00000000 20: 00000000 00000000 00000000 00000000 30: 00000000 00000000 00000000 000001ff 40: 00000000 00000000 00000000 00000000 50: 00000000 00000000 00000000 00000000 60: 00000000 00000000 00000000 00000000 70: 00000000 00000000 00000000 00000000 80: 00000000 00000000 00000000 00000000 90: 00000000 00000000 00000000 00000000 Cardbus Socket registers: 00: 04000000: f2202000: 807c0003: 52000100: 10: 00f5d200: 0400007c: 00057d00: f80002f0: ExCa registers: 00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > : I was complaining only about the machine locking up when I remove ep0 > : while the machine is up & running. > > Before or after a suspend? Before. > However, I'm seeing a different problem on my laptop. It is a Sony > VAIO PCG-505TS. It has a Ricoh RL5C475 and an unknown host to pci > bridge. Looks like I have the PIIX4 chipset. > > I'm seeing that the machine wedges tight. It doesn't call the > interrupt routine at all before the wedge. I think this is a classic > example of the level interrupt turning on and nothing reading or > acknowledging it, which causes infinite interrupt. > > I'm going to have to look at the pci bios stuff to see if there's > something there that can be used for this. > > Warner Thanks for your help, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message