Le Sunday 17 July 2005 18:29, M. Warner Losh a écrit : > Thierry, > > Thanks for the traces and such. I'm happy to report that I've > recreated the problem here and I committed what I hope is a fix last > night. It fixes me mostly (there's still some interrupt storm > messages, however). I need to find some way to get rid of those, or > at least discover where they are coming from. I think it is a power > up issue related to the card asserting its interrupt line > prematurely. Hello, I'm reporting that the latest kernel works as expected : thanks *a lot* for the quick resolution of the issue. > Warner TfH PS : extract from the non-verbose, debug messages ... cbb0: <RF5C478 PCI-CardBus Bridge> at device 12.0 on pci0 cbb0: Found memory at 80000000 cbb0: Secondary bus is 0 cbb0: Secondary bus set to 2 subbus 3 cardbus0: <CardBus bus> on cbb0 pccard0: <16-bit PCCard bus> on cbb0 cbb1: <RF5C478 PCI-CardBus Bridge> at device 12.1 on pci0 cbb1: Found memory at 80001000 cbb1: Secondary bus is 0 cbb1: Secondary bus set to 4 subbus 5 cardbus1: <CardBus bus> on cbb1 pccard1: <16-bit PCCard bus> on cbb1 ... Status is 0x30000006 Status is 0x30000410 cbb1: card inserted: event=0x00000000, state=30000410 cbb_pcic_socket_enable: cbb1: cbb_power: 5V cbb_pcic_socket_enable: ... ed1: <CNet CN40BC Ethernet> at port 0x100-0x11f irq 9 function 0 config 32 on pccard1 ed1: [GIANT-LOCKED] ed1: Ethernet address: 00:80:ad:8e:82:60 ed1: if_start running deferred for Giant ed1: type NE2000 (16 bit)Received on Mon Jul 18 2005 - 02:41:20 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:39 UTC