Date: Tue, 7 Aug 2001 17:09:45 -0400 From: "Viren R. Shah" <viren@cigital.com> To: Jonathan Chen <jon@spock.org> Cc: freebsd-bugs@FreeBSD.org Subject: Re: misc/28203: NEWCARD won't recognize my cardbus controllers or my Xircom Realport 10/100+56k card Message-ID: <15216.22809.812694.468954@aop.cigital.com> In-Reply-To: <20010807142823.A70032@enterprise.spock.org> References: <15210.56924.536714.812107@aop.cigital.com> <20010804032632.A25279@enterprise.spock.org> <15216.9560.513790.149857@aop.cigital.com> <20010807142823.A70032@enterprise.spock.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> "JC" == Jonathan Chen <jon@spock.org> writes:
JC> On Tue, Aug 07, 2001 at 01:28:56PM -0400, Viren R. Shah wrote:
>> pcic0 failed to probe at port 0x3e0 iomem 0xd0000 on isa0
>> pcic1: not probed (disabled)
JC> You should make sure "device pcic" and "device card" are not in your kernel
JC> config.
Will do so in the future.
>> pccbb0: card inserted: event=0x00000000, state=30000820
>> cardbus0: cardbus_attach_card
>> pccbb0: pccbb_power: CARD_VCC_0V and CARD_VPP_0V [44]
>> pccbb0: pccbb_power: CARD_VCC_3V and CARD_VPP_VCC [11]
>> pccbb0: pccbb_power: CARD_VCC_0V and CARD_VPP_0V [44]
>> pccbb0: card activation failed
>> cardbus1: detach_card: no card to detach!
>> pccbb1: pccbb_power: CARD_VCC_0V and CARD_VPP_0V [44]
JC> This doesn't look right... it should at least say *something* between
JC> cardbus_attach_card and card activation failed. I'll look into it.
I think it's always been that way for me.
>> The machine boots and attaches the cardbus controllers just
>> fine. However, upon re-insertion of the Xircom card (they were in the
>> slot at boot time), the machine panics. I'll attach the relevant
>> portions of my messages log.
JC> Any problems with inserting the xircom card if it wasn't in the slot at
JC> bootup?
Well, if the card isn't in the slot at bootup, then when the card is
inserted for the first time, I just get a "card activation failed"
message. The machine is still running at this point. However, now if I
remove and re-insert the card, I get the same panic.
>> I realize that this doesn't help much, but if you want me to copy down
>> any details of the panic (such as getting a stack trace), let me know.
JC> This doesn't help too much. If you can, a stack trace would be much
JC> appreciated.
Here's a stack trace. If you need more information, and you tell me
what I need to do in DDB, I'll gladly do it.
pccbb0: card inserted: event = 0x00000000, state = 30000820
cardbus0: cardbus_attach_card
pccbb0: pccbb_power: CARD_VCC_0V and CARD_VPP_0V [44]
pccbb0: pccbb_power: CARD_VCC_3V and CARD_VPP_VCC [11]
found -> vendor = 0x115d, dev = 0x003, revid = 0x03
class = 02-00-00, hdrtype = 0x00, mfdev = 1
cmdreg = 0x0000, statreg = 0x0210, cachelnsz = 8 (dwords)
lattimer = 0xa8 (5040ns), mingnt = 0x14 (5000ns), maxlat = 0x28 (10000ns)
intpin=a, irq=0
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x14
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc018ab0e
stack pointer = 0x10:0xcc2858bc
frame pointer = 0x10:0xcc2858d8
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 6 (pccbb0)
kernel: type 12 trap, code = 0
Stopped at cardbus_read_tuple_init+0x1ba: movl 0x14(%eax), %eax
db> trace
cardbus_read_tuple_init(c16a7700, c17f1a00, cc28590c, cc285910, c17f1a00) at cardbus_read_tuple_init+0x1ba
cardbus_parse_cis(c16a7700, c17f1a00, cc285d34) at cardbus_parse_cis+0xa4
cardbus_do_cis(c16a7700, c17f1a00, c17f1a00, c17f1980, c15d9120) at cardbus_do_cis+0x33
cardbus_attach_card(c16a7700) at cardbus_attach_card+0x235
pccbb_insert(c0e3a600, c035d6c, cbad7540, 0, cc285f94) at pccbb_insert+0x9e
pccbb_event_thread(c0e3a600, cc285fa8) at pccbb_event+0x146
fork_exit(c0357d6c, c0e3a600, cc285fa8) at fork_exit+0xb4
fork_trampoline() at fork_trampoline+0x8
Hope that helps.
>> Right. Before the patch you sent, I was using 2 patches (one for
>> pci_pci.c and the other for sio.c) to get my laptop to a working
>> state.
>>
>> When I applied your patch(es), I did not apply the ones that I had.
JC> I will get your changes to sio.c committed into -CURRENT.
The sio.c patch was something I modified from someone else's patch for
another card (tho I can't remember who).
JC> Thanks for your help. I don't have too much time this very instance, but
JC> I'll look into these problems when I get a chance.
No problem. Thanks for looking into it.
JC> -Jon
Viren
--
Viren Shah viren@cigital.com
"Being lovingly pummelled is the happiest thing in the world. Envy abounds."
-- Rob Craven
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15216.22809.812694.468954>