Warner,
rev 1.33 of cardbus.c for me is a regression - it will again cause kldload
to hang if the card is inserted, until I eject the card. This doesn't happen
with rev 1.32.
Also, one of the last commits introduced another minor issue for me. When I
eject the card, I get:
cbb0: bad Vcc
On Sun, Feb 09, 2003 at 10:06:54AM -0700, M. Warner Losh wrote:
Maybe something more like the following would be closer to correct:
Yes, that seems to work. After changing carbus.c as you suggested,
kldload'ing sbp.ko and inserting the card results in:
brian# cbb0: card inserted:
Warner-san,
I confirmed that the following problem occurs not only for fwochi
but also for if_rl, if_xl, if_dc and ahc_pci.
After kldload if_rl, I got wi0 timeout.
(I don't even have those hardware.)
All drivers above supports both pci and cardbus...
Do you have any idea?
/\ Hidetoshi
P.S. With full debugs
hw.cbb.debug: 1
hw.cardbus.debug: 1
hw.cardbus.cis_debug: 1
hw.pccard.debug: 1
hw.pccard.cis_debug: 1
I see the following sequence of events in my /var/log/messages:
Feb 9 09:52:35 hammer sudo: imp : TTY=ttyp1 ; PWD=/dell/imp ; USER=root ;
COMMAND=/sbin/kldload if_rl
shimokawa-san,
This sounds like an interrupt storm of some sort. There are
indications from other sources that there may be an interrupt in the
cardbus bridge that isn't being properly cleared for reasons as yet
unknown. It doesn't seem to happen on all the machines, since my
laptop is
At Sun, 09 Feb 2003 10:06:54 -0700 (MST),
M. Warner Losh wrote:
Feb 9 09:52:40 hammer kernel: cbb_pcic_socket_enable:
Feb 9 09:52:40 hammer kernel: cbb1: cbb_power: CARD_VCC_0V and CARD_VPP_0V [44]
Feb 9 09:52:40 hammer kernel: cbb1: cbb_power: CARD_VCC_5V and CARD_VPP_VCC [15
]
Feb 9
At Sun, 09 Feb 2003 10:06:54 -0700 (MST),
M. Warner Losh wrote:
Feb 9 09:52:40 hammer kernel: cbb_pcic_socket_enable:
Feb 9 09:52:40 hammer kernel: cbb1: cbb_power: CARD_VCC_0V and CARD_VPP_0V [44]
Feb 9 09:52:40 hammer kernel: cbb1: cbb_power: CARD_VCC_5V and CARD_VPP_VCC [15
]
Feb 9
On Wed, Jan 29, 2003 at 02:14:14PM -0800, Terry Lambert wrote:
I expect that the attach of the device creates an interrupt if
the system is already up. This would indicate that it was an
order of operations problem in the driver registration for a
live piece of hardware. Probably, it needs
Andrea Campi wrote:
On Wed, Jan 29, 2003 at 02:14:14PM -0800, Terry Lambert wrote:
I expect that the attach of the device creates an interrupt if
the system is already up. This would indicate that it was an
order of operations problem in the driver registration for a
live piece of
On Sat, Jan 25, 2003 at 11:55:01AM -0700, M. Warner Losh wrote:
This sounds like it might be an interrupt storm. I'm not sure if the
fwohci driver is failing to clear an interrupt source, or if the
cardbus bridge is failing. Have you connected a fw device to the
firewire card?
I've been
At Wed, 29 Jan 2003 12:49:51 +0100,
Andrea Campi wrote:
On Sat, Jan 25, 2003 at 11:55:01AM -0700, M. Warner Losh wrote:
This sounds like it might be an interrupt storm. I'm not sure if the
fwohci driver is failing to clear an interrupt source, or if the
cardbus bridge is failing. Have
Andrea Campi wrote:
On Sat, Jan 25, 2003 at 11:55:01AM -0700, M. Warner Losh wrote:
This sounds like it might be an interrupt storm. I'm not sure if the
fwohci driver is failing to clear an interrupt source, or if the
cardbus bridge is failing. Have you connected a fw device to the
Hi Warner and Hidetoshi,
On Saturday, Jan 25, 2003, at 19:55 Europe/Rome, M. Warner Losh wrote:
This sounds like it might be an interrupt storm. I'm not sure if the
fwohci driver is failing to clear an interrupt source, or if the
cardbus bridge is failing. Have you connected a fw device to
hmm, I have no problem with my FireWire CardBus card.
If you can get traceback in DDB, please send it to me.
cardbus0: Resource not specified in CIS: id=10, size=800
cardbus0: Resource not specified in CIS: id=14, size=4000
fwohci1: Texas Instruments TSB43AA22 mem
This sounds like it might be an interrupt storm. I'm not sure if the
fwohci driver is failing to clear an interrupt source, or if the
cardbus bridge is failing. Have you connected a fw device to the
firewire card?
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe
Hi all,
I'm having a bad time trying to get a firewire cardbus adapter to work.
First of all, let me say that I'm under no pressure - I just bought it to
test our firewire implementation but I have no pressing need for it.
Anyway, new kernel from last night, when I insert the card I get the
16 matches
Mail list logo
