From owner-freebsd-current@FreeBSD.ORG Tue Jul 12 01:29:20 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 7E6D5106566B; Tue, 12 Jul 2011 01:29:20 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 65-241-43-4.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 006BC14FA0F; Tue, 12 Jul 2011 01:29:19 +0000 (UTC) Message-ID: <4E1BA36F.5060504@FreeBSD.org> Date: Mon, 11 Jul 2011 18:29:19 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110706 Thunderbird/5.0 MIME-Version: 1.0 To: John Baldwin References: <4E100086.7080105@FreeBSD.org> <201107071720.50203.jhb@freebsd.org> <4E16C463.9020604@FreeBSD.org> <201107080919.58210.jhb@freebsd.org> In-Reply-To: <201107080919.58210.jhb@freebsd.org> X-Enigmail-Version: 1.2pre OpenPGP: id=1A1ABC84 Content-Type: multipart/mixed; boundary="------------070402020403010903060407" Cc: freebsd-current@freebsd.org Subject: Re: cardbus panic: end address is not aligned X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jul 2011 01:29:20 -0000 This is a multi-part message in MIME format. --------------070402020403010903060407 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 07/08/2011 06:19, John Baldwin wrote: > Hmm, well that's odd. It didn't grow it enough it seems. > >>> Also, can you boot your machine, then do 'sysctl debug.bootverbose=1', insert >>> the card and record the messages in dmesg when it does? (You can likely get >>> those out of kgdb.) I tried your patch, and got some odd results. The good news is, no crash. However it did not actually enable the cards, with or without if_ath being loaded before inserting them. Here is the dmesg output with debug.bootverbose=1. This is with inserting and removing first one card, then the other. pcib5: attempting to grow memory window for (0x88000000-0xffffffff,0x10000) back candidate range: 0x88000000-0x8800ffff pcib5: grew memory window to 0x80000000-0x880fffff pcib5: allocated memory range (0x88000000-0x8800ffff) for rid 10 of pci0:4:0:0 found-> vendor=0x168c, dev=0x0023, revid=0x01 domain=0, bus=4, slot=0, func=0 class=02-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0000, statreg=0x02b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=18 cardbus0: at device 0.0 (no driver attached) map[10]: type Memory, range 32, base 0, size 16, memory disabled pcib5: allocated memory range (0x88000000-0x8800ffff) for rid 10 of pci0:4:0:0 found-> vendor=0x168c, dev=0x0023, revid=0x01 domain=0, bus=4, slot=0, func=0 class=02-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0000, statreg=0x02b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=18 cardbus0: at device 0.0 (no driver attached) pcib5: allocated memory range (0x88000000-0x8800ffff) for rid 10 of pci0:4:0:0 unknown: Lazy allocation of 0x10000 bytes rid 0x10 type 3 at 0x88000000 cbb0: Opening memory: cbb0: Normal: 0x88000000-0x8800ffff cbb0: Opening memory: cbb0: Opening memory: cbb0: Normal: 0x88000000-0x8800ffff cbb0: Opening memory: found-> vendor=0x168c, dev=0x0013, revid=0x01 domain=0, bus=4, slot=0, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0002, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x0a (2500 ns), maxlat=0x1c (7000 ns) intpin=a, irq=18 powerspec 2 supports D0 D3 current D0 cardbus0: at device 0.0 (no driver attached) pci0:4:0:0: Transition from D0 to D3 > The real messages I will want to see are in the dmesg. Also, getting the > output of 'devinfo -r' before you insert the card would also be helpful so > I can see what it is growing from. Attached. Thanks for looking into this, Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ --------------070402020403010903060407 Content-Type: text/plain; name="devinfo" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="devinfo" nexus0 apic0 ram0 I/O memory addresses: 0x0-0x9efff 0x100000-0x7fe813ff acpi0 Interrupt request lines: 9 I/O ports: 0x20-0x21 0x2e-0x2f 0x4e-0x4f 0x86 0x92 0xa0-0xa1 0xb2 0xb3 0x4d0-0x4d1 0x809 0x910-0x91f 0x920-0x92f 0x930-0x97f 0xc80-0xcaf 0xcbc-0xcbf 0xcc0-0xcff 0x1000-0x1005 0x1006-0x1007 0x1008-0x1059 0x1060-0x107f 0x1080-0x10bf 0x10c0-0x10df 0xf400-0xf4fe I/O memory addresses: 0x9fc00-0x9ffff 0xc0000-0xcffff 0xe0000-0xfffff 0x7fe81400-0x7fefffff 0x7ff00000-0x7fffffff 0xf0000000-0xf3ffffff 0xf4000000-0xf4003fff 0xf4004000-0xf4004fff 0xf4005000-0xf4005fff 0xf4006000-0xf4006fff 0xf4008000-0xf400bfff 0xfec00000-0xfec0ffff 0xfed20000-0xfed3ffff 0xfed45000-0xfed9ffff 0xfee00000-0xfee0ffff 0xffa80000-0xffa83fff 0xffb00000-0xffffffff cpu0 ACPI I/O ports: 0x1014 0x1016 est0 acpi_perf0 cpufreq0 coretemp0 cpu1 ACPI I/O ports: 0x1014 0x1016 est1 acpi_perf1 cpufreq1 coretemp1 acpi_acad0 battery0 battery1 acpi_lid0 acpi_button0 acpi_button1 acpi_sysresource0 pcib0 pci0 hostb0 pcib1 I/O memory addresses: 0xd0000000-0xdfffffff 0xed000000-0xefefffff pci1 vgapci0 Interrupt request lines: 16 pcib1 memory window: 0xed000000-0xedffffff 0xee000000-0xeeffffff pcib1 prefetch window: 0xd0000000-0xdfffffff vgapm0 nvidia0 hdac0 Interrupt request lines: 256 I/O memory addresses: 0xefffc000-0xefffffff pcm0 pcib2 pci11 pcib3 I/O memory addresses: 0xecf00000-0xecffffff pci12 wpi0 Interrupt request lines: 17 pcib3 memory window: 0xecfff000-0xecffffff pcib4 I/O memory addresses: 0xece00000-0xecefffff pci9 uhci0 Interrupt request lines: 20 I/O ports: 0xbf80-0xbf9f usbus0 uhub0 uhci1 Interrupt request lines: 21 I/O ports: 0xbf60-0xbf7f usbus1 uhub1 uhci2 Interrupt request lines: 22 I/O ports: 0xbf40-0xbf5f usbus2 uhub2 ums0 uhci3 Interrupt request lines: 23 I/O ports: 0xbf20-0xbf3f usbus3 uhub3 ehci0 Interrupt request lines: 20 ACPI I/O memory addresses: 0xffa80000-0xffa803ff usbus4 uhub4 uhub5 uhub6 pcib5 I/O memory addresses: 0x80000000-0x800fffff pci3 cbb0 Interrupt request lines: 18 pcib5 memory window: 0x80000000-0x80000fff cardbus0 pccard0 isab0 isa0 sc0 vga0 I/O ports: 0x3c0-0x3df I/O memory addresses: 0xa0000-0xbffff orm0 ACPI I/O memory addresses: 0xc0000-0xcffff atapci0 I/O ports: 0x170-0x177 0x1f0-0x1f7 0x376 0x3f6 0xbfa0-0xbfaf ata0 Interrupt request lines: 14 ad0 atapicam0 ata1 Interrupt request lines: 15 acd0 atapicam1 acpi_sysresource1 acpi_sysresource2 psmcpnp0 atkbdc0 Interrupt request lines: 1 I/O ports: 0x60 0x62 0x64 0x66 atkbd0 psm0 Interrupt request lines: 12 atrtc0 Interrupt request lines: 8 I/O ports: 0x70-0x71 0x72-0x77 attimer0 Interrupt request lines: 0 I/O ports: 0x40-0x43 0x50-0x53 acpi_sysresource3 atdma0 DMA request lines: 4 I/O ports: 0x0-0xf 0x10-0x1f 0x80-0x85 0x87-0x8f 0x90-0x91 0x93-0x9f 0xc0-0xdf fpupnp0 I/O ports: 0xf0-0xff hpet0 Interrupt request lines: 20 I/O memory addresses: 0xfed00000-0xfed003ff uart0 Interrupt request lines: 4 I/O ports: 0x3f8-0x3ff pci_link0 pci_link1 pci_link2 pci_link3 pci_link4 pci_link5 pci_link6 pci_link7 acpi_tz0 acpi_timer0 ACPI I/O ports: 0x1008-0x100b --------------070402020403010903060407--