From owner-freebsd-bugs Tue Aug 7 11:28:40 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from enterprise.spock.org (cm-24-29-85-81.nycap.rr.com [24.29.85.81]) by hub.freebsd.org (Postfix) with ESMTP id 9C61C37B40C for ; Tue, 7 Aug 2001 11:28:30 -0700 (PDT) (envelope-from jon@enterprise.spock.org) Received: (from jon@localhost) by enterprise.spock.org serial EF600Q3T-B7F; Tue, 7 Aug 2001 14:28:23 -0400 (EDT) (envelope-from jon)$ Date: Tue, 7 Aug 2001 14:28:23 -0400 From: Jonathan Chen To: "Viren R. Shah" 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: <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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: telnet/1.1x In-Reply-To: <15216.9560.513790.149857@aop.cigital.com>; from viren@cigital.com on Tue, Aug 07, 2001 at 01:28:56PM -0400 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, Aug 07, 2001 at 01:28:56PM -0400, Viren R. Shah wrote: Content-Description: message body text > pccbb0: irq 11 at device 15.0 on pci2 > pcib2: device pccbb0 requested unsupported memory range 0x0-0xffffffff (decoding 0xf4000000-0xfbffffff, 0xfff00000-0xfffff) > pcib2: device pccbb0 requested decoded memory range 0xf4000000-0xffffffff > pccbb0: PCI Memory allocated: f4000000 > cardbus0: on pccbb0 > pccard0: <16-bit PCCard bus> on pccbb0 > pccbb1: irq 11 at device 15.1 on pci2 > pcib2: device pccbb1 requested unsupported memory range 0x0-0xffffffff (decoding 0xf4000000-0xfbffffff, 0xfff00000-0xfffff) > pcib2: device pccbb1 requested decoded memory range 0xf4000000-0xffffffff > pccbb1: PCI Memory allocated: f4001000 > cardbus1: on pccbb1 > pccard1: <16-bit PCCard bus> on pccbb1 This looks fine. > pcic0 failed to probe at port 0x3e0 iomem 0xd0000 on isa0 > pcic1: not probed (disabled) You should make sure "device pcic" and "device card" are not in your kernel config. > 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] This doesn't look right... it should at least say *something* between cardbus_attach_card and card activation failed. I'll look into it. > 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. Any problems with inserting the xircom card if it wasn't in the slot at bootup? > Aug 7 12:56:36 slithytove /boot/kernel/kernel: Fatal trap 12: page fault while in kernel mode > Aug 7 12:56:36 slithytove /boot/kernel/kernel: fault virtual address = 0x14 > Aug 7 12:56:36 slithytove /boot/kernel/kernel: fault code = supervisor read, page not present > Aug 7 12:56:36 slithytove /boot/kernel/kernel: instruction pointer = 0x8:0xc018ab0e > Aug 7 12:56:36 slithytove /boot/kernel/kernel: stack pointer = 0x10:0xcc2858bc > Aug 7 12:56:36 slithytove /boot/kernel/kernel: frame pointer = 0x10:0xcc2858d8 > Aug 7 12:56:36 slithytove /boot/kernel/kernel: code segment = base 0x0, limit 0xfffff, type 0x1b > Aug 7 12:56:36 slithytove /boot/kernel/kernel: = DPL 0, pres 1, def32 1, gran 1 > Aug 7 12:56:36 slithytove /boot/kernel/kernel: processor eflags = interrupt enabled, resume, IOPL = 0 > Aug 7 12:56:36 slithytove /boot/kernel/kernel: current process = 6 (pccbb0) > Aug 7 12:56:36 slithytove /boot/kernel/kernel: Waiting (max 60 seconds) for system process `bufdaemon' to stop...../../../kern/kern_synch.c:377: sleeping with "pccbb0" locked from ../../../dev/pccbb/pccbb.c:632 > Aug 7 12:56:36 slithytove /boot/kernel/kernel: lock order reversal > Aug 7 12:56:36 slithytove /boot/kernel/kernel: 1st 0xc0e3a618 pccbb0 @ ../../../dev/pccbb/pccbb.c:632 > Aug 7 12:56:37 slithytove /boot/kernel/kernel: 2nd 0xc04dc5c0 Giant @ ../../../kern/kern_synch.c:475 > Aug 7 12:56:37 slithytove /boot/kernel/kernel: stopped > Aug 7 12:56:37 slithytove /boot/kernel/kernel: Waiting (max 60 seconds) for system process `syncer' to stop...../../../kern/kern_synch.c:377: sleeping with "pccbb0" locked from ../../../dev/pccbb/pccbb.c:632 > Aug 7 12:56:37 slithytove /boot/kernel/kernel: stopped > 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. This doesn't help too much. If you can, a stack trace would be much appreciated. > 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. I will get your changes to sio.c committed into -CURRENT. Thanks for your help. I don't have too much time this very instance, but I'll look into these problems when I get a chance. -Jon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message