Re: pcic/pccard hang?

> 
> Hmmm, are you running with PCI or ISA interrupts?  I think that I have
> a bug in the OLDCARD code that doesn't like most sony laptops.  You'll
> have to work around it by doing hw.pcic.intr_path=1.
> 
> Warner
> 

 Perhaps it's time for more information.

 Here's the things I've tried:

	set hw.pcic.intr_path=1
		Causes the "hang" to occur as soon as the card is
		inserted, instead of when pccardd tries to read the CIS

	set hw.pcic.intr_path=1
	set hw.pcic.irq=10
		IRQ=10 was the IRQ used under 4.1-RELEASE, setting
		this (along with hw.pcic.intr_path=1) causes a panic 
		at boot:
		   pcic0: PCI Memory allocated: 0x44000000
		   pcic0: Can't route ISA CSC interrupt
		   panic: resource_list_release: can't find resource

	set hw.pcic.irq=10
		Without setting hw.pcic.intr_path=1, the machine
		will boot - but the IRQ used for pcic0 is 9, here's
		the messages:

		   pci_cfgintr_liked: linked (60) to hard-routed irq 9
		   pci_cfgintr: 0:12 INTA routed to irq 9
		   pcic0: <Ricoh RL5C478 PCI-CardBus Bridge> irq 9 at device 12.0 on pci0
		   pccard0: <PC Card bus (classic)> on pcic0
		   pci_cgintr_linked: linked (61) to hard-routed irq 9
		   pci_cfgintr: 0:12 INTB routed to irq 9
		   pcic1: <Ricoh RL5C478 PCI-CardBus Bridge> irq 9 at device 12.1 on pci0
		   pcic1: PCI Memory allocated: 0x44001000
		   pccard1: <PC Card bus (classic)> on pcic1

		And - when I insert the card, I get the hang.

		The messages I see are:
		  pccard: card inserted, slot 0
		  pccardd[41]: Card "PCMCIA"("FastEhternet") [V] [1.0] matched "PCMCIA"("FastEthernet") [(null)] [(null)]
		  ed1 at port 0x300-0x31f irq 9 flags 0x30000 slot 0 on pccard0
		      ***hang***
		      <then, remove card>
		      -beeps (both the inserting & removing beeps) -
		  ed1: address 01:02:00:ff:15:12, type NE2000 (16 bit)
		  ed1: SmartLink inserted.
		  ed1: detached
		  pccard: card removed, slo 0
		  ed1: SmartLink removed

	"default" kernel (no setting):
		same messages/behaviour as the hw.pcic.irq=10 case


   I'm wondering if this "hard-routed irq 9" is the culprit, as
 I'm pretty sure it should be irq 10.  Does that come from a 
 kernel config?

   And - I'm pretty handy at debugging the kernel, if you could
 just point me to the area, I can sprinkle some printf()s around 
 to see where the hang occurs.

	- Many Thanks for all your help! -
		- Dave Riveres -

--
[email protected]                        Work: (919) 676-0847
Get your mainframe programming tools at http://www.dignus.com


To Unsubscribe: send mail to [email protected]
with "unsubscribe freebsd-mobile" in the body of the message