Re: mpt: Unable to memory map registers
On Tuesday, June 19, 2012 9:03:57 am Andrey Zonov wrote: On Mon, Jun 18, 2012 at 6:26 PM, John Baldwin j...@freebsd.org wrote: On Saturday, June 16, 2012 6:10:47 am Andrey Zonov wrote: On 6/15/12 9:24 PM, John Baldwin wrote: On Friday, June 15, 2012 2:12:06 am Andrey Zonov wrote: On 6/13/12 7:10 PM, John Baldwin wrote: On Tuesday, June 12, 2012 5:57:34 pm Andrey Zonov wrote: On 6/13/12 12:51 AM, John Baldwin wrote: On Tuesday, June 12, 2012 3:53:09 pm Andrey Zonov wrote: On 6/12/12 10:06 PM, John Baldwin wrote: [snip] Ok, I've added some more debugging. The patch is a bit larger now and you can fetch it from www.freebsd.org/~jhb/patches/pcib_debug.patch New dmesg is in attach. Sheesh, found another bug (wasn't masking 'front' properly). Try updated patch (same URL). Great! It works! Excellent. I've committed the 2 bugs needed to fix your box. However, there is another bug that this exposed that I'd like you to test. Can you update to the latest HEAD, apply the updated pcib_debug.patch, and boot with 'hw.pci.pcib_clear=1' set from the loader? That should exercise the bug I'm worried about and see if my fixes for that (recursively growing windows) works correctly. Attached. Hmm, it doesn't seem like hw.pci.pcib_clear was set (the pcibX devices still tried to allocate their initial windows). Ooops. Thanks. Unfortunately, this didn't actually exercise what I wanted, but that is ok. However, this did uncover another bug it seems: pcib7: ACPI PCI-PCI bridge at device 0.3 on pci5 pci6: ACPI PCI bus on pcib7 pci6: domain=0, physical bus=6 found- vendor=0x1000, dev=0x0054, revid=0x02 pcib3: attempting to grow I/O port window for (0xd000-0xdfff,0x1000) front candidate range: 0xd000-0xdfff pcib3: bus_adjust_resource(0xc000, 0xefff) pci0: bus_adjust_resource(pcib3, 0x1c, 0xc000, 0xefff) pcib0: bus_adjust_resource(pcib3, 0x1c, 0xc000, 0xefff) acpi0: bus_adjust_resource(pcib3, 0x1c, 0xc000, 0xefff) nexus0: bus_adjust_resource(pcib3, 0x1c, 0xc000, 0xefff) pcib3: grew I/O port window to 0xc000-0xefff pcib3: allocated I/O port range (0xd000-0xdfff) for rid 1c of pcib7 pcib7: allocated initial I/O port window of 0xd000-0xdfff This grew the range too large resulting in this failure later on: pcib9: failed to allocate initial I/O port window (0xc000-0xcfff,0x1000) Can you try the updated pcib_debug.patch? It has some more printf's for this case. Sure. Ok, found the bug, thanks! -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: mpt: Unable to memory map registers
On Saturday, June 16, 2012 6:10:47 am Andrey Zonov wrote: On 6/15/12 9:24 PM, John Baldwin wrote: On Friday, June 15, 2012 2:12:06 am Andrey Zonov wrote: On 6/13/12 7:10 PM, John Baldwin wrote: On Tuesday, June 12, 2012 5:57:34 pm Andrey Zonov wrote: On 6/13/12 12:51 AM, John Baldwin wrote: On Tuesday, June 12, 2012 3:53:09 pm Andrey Zonov wrote: On 6/12/12 10:06 PM, John Baldwin wrote: [snip] Ok, I've added some more debugging. The patch is a bit larger now and you can fetch it from www.freebsd.org/~jhb/patches/pcib_debug.patch New dmesg is in attach. Sheesh, found another bug (wasn't masking 'front' properly). Try updated patch (same URL). Great! It works! Excellent. I've committed the 2 bugs needed to fix your box. However, there is another bug that this exposed that I'd like you to test. Can you update to the latest HEAD, apply the updated pcib_debug.patch, and boot with 'hw.pci.pcib_clear=1' set from the loader? That should exercise the bug I'm worried about and see if my fixes for that (recursively growing windows) works correctly. Attached. Hmm, it doesn't seem like hw.pci.pcib_clear was set (the pcibX devices still tried to allocate their initial windows). Ooops. Thanks. Unfortunately, this didn't actually exercise what I wanted, but that is ok. However, this did uncover another bug it seems: pcib7: ACPI PCI-PCI bridge at device 0.3 on pci5 pci6: ACPI PCI bus on pcib7 pci6: domain=0, physical bus=6 found- vendor=0x1000, dev=0x0054, revid=0x02 pcib3: attempting to grow I/O port window for (0xd000-0xdfff,0x1000) front candidate range: 0xd000-0xdfff pcib3: bus_adjust_resource(0xc000, 0xefff) pci0: bus_adjust_resource(pcib3, 0x1c, 0xc000, 0xefff) pcib0: bus_adjust_resource(pcib3, 0x1c, 0xc000, 0xefff) acpi0: bus_adjust_resource(pcib3, 0x1c, 0xc000, 0xefff) nexus0: bus_adjust_resource(pcib3, 0x1c, 0xc000, 0xefff) pcib3: grew I/O port window to 0xc000-0xefff pcib3: allocated I/O port range (0xd000-0xdfff) for rid 1c of pcib7 pcib7: allocated initial I/O port window of 0xd000-0xdfff This grew the range too large resulting in this failure later on: pcib9: failed to allocate initial I/O port window (0xc000-0xcfff,0x1000) Can you try the updated pcib_debug.patch? It has some more printf's for this case. -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: mpt: Unable to memory map registers
On 6/15/12 9:24 PM, John Baldwin wrote: On Friday, June 15, 2012 2:12:06 am Andrey Zonov wrote: On 6/13/12 7:10 PM, John Baldwin wrote: On Tuesday, June 12, 2012 5:57:34 pm Andrey Zonov wrote: On 6/13/12 12:51 AM, John Baldwin wrote: On Tuesday, June 12, 2012 3:53:09 pm Andrey Zonov wrote: On 6/12/12 10:06 PM, John Baldwin wrote: [snip] Ok, I've added some more debugging. The patch is a bit larger now and you can fetch it from www.freebsd.org/~jhb/patches/pcib_debug.patch New dmesg is in attach. Sheesh, found another bug (wasn't masking 'front' properly). Try updated patch (same URL). Great! It works! Excellent. I've committed the 2 bugs needed to fix your box. However, there is another bug that this exposed that I'd like you to test. Can you update to the latest HEAD, apply the updated pcib_debug.patch, and boot with 'hw.pci.pcib_clear=1' set from the loader? That should exercise the bug I'm worried about and see if my fixes for that (recursively growing windows) works correctly. Attached. Hmm, it doesn't seem like hw.pci.pcib_clear was set (the pcibX devices still tried to allocate their initial windows). Ooops. -- Andrey Zonov MP Configuration Table version 1.4 found at 0x800fcb70 Table 'FACP' at 0xdffb0290 Table 'APIC' at 0xdffb0390 APIC: Found table at 0xdffb0390 APIC: Using the MADT enumerator. MADT: Found CPU APIC ID 0 ACPI ID 1: enabled SMP: Added CPU 0 (AP) MADT: Found CPU APIC ID 4 ACPI ID 2: enabled SMP: Added CPU 4 (AP) MADT: Found CPU APIC ID 1 ACPI ID 3: enabled SMP: Added CPU 1 (AP) MADT: Found CPU APIC ID 5 ACPI ID 4: enabled SMP: Added CPU 5 (AP) MADT: Found CPU APIC ID 2 ACPI ID 5: enabled SMP: Added CPU 2 (AP) MADT: Found CPU APIC ID 6 ACPI ID 6: enabled SMP: Added CPU 6 (AP) MADT: Found CPU APIC ID 3 ACPI ID 7: enabled SMP: Added CPU 3 (AP) MADT: Found CPU APIC ID 7 ACPI ID 8: enabled SMP: Added CPU 7 (AP) Copyright (c) 1992-2012 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.0-CURRENT #0 r237018M: Sat Jun 16 09:40:07 UTC 2012 r...@dst-dev.yandex.ru:/usr/obj/usr/src/sys/head amd64 Preloaded elf kernel /boot/kernel/kernel at 0x80fdc000. Calibrating TSC clock ... TSC clock: 2826305989 Hz CPU: Intel(R) Xeon(R) CPU E5440 @ 2.83GHz (2826.31-MHz K8-class CPU) Origin = GenuineIntel Id = 0x1067a Family = 6 Model = 17 Stepping = 10 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0xc0ce3bdSSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,SSE4.1,XSAVE,OSXSAVE AMD Features=0x20100800SYSCALL,NX,LM AMD Features2=0x1LAHF TSC: P-state invariant, performance statistics real memory = 34359738368 (32768 MB) Physical memory chunk(s): 0x0001 - 0x0009bfff, 573440 bytes (140 pages) 0x0010 - 0x001f, 1048576 bytes (256 pages) 0x01028000 - 0xdff9, 3740762112 bytes (913272 pages) 0xdffae000 - 0xdffa, 8192 bytes (2 pages) 0x0001 - 0x0007e2ea0fff, 29576794112 bytes (7220897 pages) avail memory = 33113063424 (31579 MB) INTR: Adding local APIC 0 as a target Event timer LAPIC quality 400 ACPI APIC Table: 090808 APIC1308 INTR: Adding local APIC 0 as a target INTR: Adding local APIC 1 as a target INTR: Adding local APIC 2 as a target INTR: Adding local APIC 3 as a target INTR: Adding local APIC 4 as a target INTR: Adding local APIC 5 as a target INTR: Adding local APIC 6 as a target INTR: Adding local APIC 7 as a target FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs FreeBSD/SMP: 2 package(s) x 4 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 cpu4 (AP): APIC ID: 4 cpu5 (AP): APIC ID: 5 cpu6 (AP): APIC ID: 6 cpu7 (AP): APIC ID: 7 x86bios: IVT 0x00-0x0004ff at 0xfe00 x86bios: SSEG 0x098000-0x098fff at 0xff800029 x86bios: EBDA 0x09e000-0x09 at 0xfe09e000 x86bios: ROM 0x0a-0x0fefff at 0xfe0a APIC: CPU 0 has ACPI ID 1 APIC: CPU 1 has ACPI ID 3 APIC: CPU 2 has ACPI ID 5 APIC: CPU 3 has ACPI ID 7 APIC: CPU 4 has ACPI ID 2 APIC: CPU 5 has ACPI ID 4 APIC: CPU 6 has ACPI ID 6 APIC: CPU 7 has ACPI ID 8 WARNING: VIMAGE (virtualized network stack) is a highly experimental feature. ULE: setup cpu 0 ULE: setup cpu 1 ULE: setup cpu 2 ULE: setup cpu 3 ULE: setup cpu 4 ULE: setup cpu 5 ULE: setup cpu 6 ULE: setup cpu 7 ACPI: RSDP 0xf9960 00024 (v02 ACPIAM) ACPI: XSDT 0xdffb0100 00074 (v01 090808 XSDT1308 20080908 MSFT 0097) ACPI: FACP 0xdffb0290 000F4 (v03 090808 FACP1308 20080908 MSFT 0097) ACPI: DSDT 0xdffb04d0 05414 (v01 CLSea CLSea007 0007 INTL 20051117) ACPI: FACS 0xdffbe000 00040 ACPI: APIC 0xdffb0390 000AA
Re: mpt: Unable to memory map registers
On 6/13/12 7:10 PM, John Baldwin wrote: On Tuesday, June 12, 2012 5:57:34 pm Andrey Zonov wrote: On 6/13/12 12:51 AM, John Baldwin wrote: On Tuesday, June 12, 2012 3:53:09 pm Andrey Zonov wrote: On 6/12/12 10:06 PM, John Baldwin wrote: [snip] Ok, I've added some more debugging. The patch is a bit larger now and you can fetch it from www.freebsd.org/~jhb/patches/pcib_debug.patch New dmesg is in attach. Sheesh, found another bug (wasn't masking 'front' properly). Try updated patch (same URL). Great! It works! Excellent. I've committed the 2 bugs needed to fix your box. However, there is another bug that this exposed that I'd like you to test. Can you update to the latest HEAD, apply the updated pcib_debug.patch, and boot with 'hw.pci.pcib_clear=1' set from the loader? That should exercise the bug I'm worried about and see if my fixes for that (recursively growing windows) works correctly. Attached. -- Andrey Zonov MP Configuration Table version 1.4 found at 0x800fcb70 Table 'FACP' at 0xdffb0290 Table 'APIC' at 0xdffb0390 APIC: Found table at 0xdffb0390 APIC: Using the MADT enumerator. MADT: Found CPU APIC ID 0 ACPI ID 1: enabled SMP: Added CPU 0 (AP) MADT: Found CPU APIC ID 4 ACPI ID 2: enabled SMP: Added CPU 4 (AP) MADT: Found CPU APIC ID 1 ACPI ID 3: enabled SMP: Added CPU 1 (AP) MADT: Found CPU APIC ID 5 ACPI ID 4: enabled SMP: Added CPU 5 (AP) MADT: Found CPU APIC ID 2 ACPI ID 5: enabled SMP: Added CPU 2 (AP) MADT: Found CPU APIC ID 6 ACPI ID 6: enabled SMP: Added CPU 6 (AP) MADT: Found CPU APIC ID 3 ACPI ID 7: enabled SMP: Added CPU 3 (AP) MADT: Found CPU APIC ID 7 ACPI ID 8: enabled SMP: Added CPU 7 (AP) Copyright (c) 1992-2012 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.0-CURRENT #0 r237018: Thu Jun 14 11:18:43 MSK 2012 r...@dst-dev.yandex.ru:/usr/obj/place/home/zont/head/sys/stable10 amd64 Preloaded elf kernel /boot/kernel/kernel at 0x80fdc000. Calibrating TSC clock ... TSC clock: 2826309738 Hz CPU: Intel(R) Xeon(R) CPU E5440 @ 2.83GHz (2826.31-MHz K8-class CPU) Origin = GenuineIntel Id = 0x1067a Family = 6 Model = 17 Stepping = 10 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0xc0ce3bdSSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,SSE4.1,XSAVE,OSXSAVE AMD Features=0x20100800SYSCALL,NX,LM AMD Features2=0x1LAHF TSC: P-state invariant, performance statistics real memory = 34359738368 (32768 MB) Physical memory chunk(s): 0x0001 - 0x0009bfff, 573440 bytes (140 pages) 0x0010 - 0x001f, 1048576 bytes (256 pages) 0x01028000 - 0xdff9, 3740762112 bytes (913272 pages) 0xdffae000 - 0xdffa, 8192 bytes (2 pages) 0x0001 - 0x0007e2ea0fff, 29576794112 bytes (7220897 pages) avail memory = 33113063424 (31579 MB) INTR: Adding local APIC 0 as a target Event timer LAPIC quality 400 ACPI APIC Table: 090808 APIC1308 INTR: Adding local APIC 0 as a target INTR: Adding local APIC 1 as a target INTR: Adding local APIC 2 as a target INTR: Adding local APIC 3 as a target INTR: Adding local APIC 4 as a target INTR: Adding local APIC 5 as a target INTR: Adding local APIC 6 as a target INTR: Adding local APIC 7 as a target FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs FreeBSD/SMP: 2 package(s) x 4 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 cpu4 (AP): APIC ID: 4 cpu5 (AP): APIC ID: 5 cpu6 (AP): APIC ID: 6 cpu7 (AP): APIC ID: 7 x86bios: IVT 0x00-0x0004ff at 0xfe00 x86bios: SSEG 0x098000-0x098fff at 0xff800029 x86bios: EBDA 0x09e000-0x09 at 0xfe09e000 x86bios: ROM 0x0a-0x0fefff at 0xfe0a APIC: CPU 0 has ACPI ID 1 APIC: CPU 1 has ACPI ID 3 APIC: CPU 2 has ACPI ID 5 APIC: CPU 3 has ACPI ID 7 APIC: CPU 4 has ACPI ID 2 APIC: CPU 5 has ACPI ID 4 APIC: CPU 6 has ACPI ID 6 APIC: CPU 7 has ACPI ID 8 WARNING: VIMAGE (virtualized network stack) is a highly experimental feature. ULE: setup cpu 0 ULE: setup cpu 1 ULE: setup cpu 2 ULE: setup cpu 3 ULE: setup cpu 4 ULE: setup cpu 5 ULE: setup cpu 6 ULE: setup cpu 7 ACPI: RSDP 0xf9960 00024 (v02 ACPIAM) ACPI: XSDT 0xdffb0100 00074 (v01 090808 XSDT1308 20080908 MSFT 0097) ACPI: FACP 0xdffb0290 000F4 (v03 090808 FACP1308 20080908 MSFT 0097) ACPI: DSDT 0xdffb04d0 05414 (v01 CLSea CLSea007 0007 INTL 20051117) ACPI: FACS 0xdffbe000 00040 ACPI: APIC 0xdffb0390 000AA (v01 090808 APIC1308 20080908 MSFT 0097) ACPI: MCFG 0xdffb0490 0003C (v01 090808 OEMMCFG 20080908 MSFT 0097) ACPI: OEMB 0xdffbe040 00071 (v01 090808 OEMB1308 20080908 MSFT 0097) ACPI: HPET 0xdffb58f0
Re: mpt: Unable to memory map registers
On Friday, June 15, 2012 2:12:06 am Andrey Zonov wrote: On 6/13/12 7:10 PM, John Baldwin wrote: On Tuesday, June 12, 2012 5:57:34 pm Andrey Zonov wrote: On 6/13/12 12:51 AM, John Baldwin wrote: On Tuesday, June 12, 2012 3:53:09 pm Andrey Zonov wrote: On 6/12/12 10:06 PM, John Baldwin wrote: [snip] Ok, I've added some more debugging. The patch is a bit larger now and you can fetch it from www.freebsd.org/~jhb/patches/pcib_debug.patch New dmesg is in attach. Sheesh, found another bug (wasn't masking 'front' properly). Try updated patch (same URL). Great! It works! Excellent. I've committed the 2 bugs needed to fix your box. However, there is another bug that this exposed that I'd like you to test. Can you update to the latest HEAD, apply the updated pcib_debug.patch, and boot with 'hw.pci.pcib_clear=1' set from the loader? That should exercise the bug I'm worried about and see if my fixes for that (recursively growing windows) works correctly. Attached. Hmm, it doesn't seem like hw.pci.pcib_clear was set (the pcibX devices still tried to allocate their initial windows). -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: mpt: Unable to memory map registers
On Tuesday, June 12, 2012 5:57:34 pm Andrey Zonov wrote: On 6/13/12 12:51 AM, John Baldwin wrote: On Tuesday, June 12, 2012 3:53:09 pm Andrey Zonov wrote: On 6/12/12 10:06 PM, John Baldwin wrote: [snip] Ok, I've added some more debugging. The patch is a bit larger now and you can fetch it from www.freebsd.org/~jhb/patches/pcib_debug.patch New dmesg is in attach. Sheesh, found another bug (wasn't masking 'front' properly). Try updated patch (same URL). Great! It works! Excellent. I've committed the 2 bugs needed to fix your box. However, there is another bug that this exposed that I'd like you to test. Can you update to the latest HEAD, apply the updated pcib_debug.patch, and boot with 'hw.pci.pcib_clear=1' set from the loader? That should exercise the bug I'm worried about and see if my fixes for that (recursively growing windows) works correctly. -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: mpt: Unable to memory map registers
On 6/13/12 7:10 PM, John Baldwin wrote: On Tuesday, June 12, 2012 5:57:34 pm Andrey Zonov wrote: On 6/13/12 12:51 AM, John Baldwin wrote: On Tuesday, June 12, 2012 3:53:09 pm Andrey Zonov wrote: On 6/12/12 10:06 PM, John Baldwin wrote: [snip] Ok, I've added some more debugging. The patch is a bit larger now and you can fetch it from www.freebsd.org/~jhb/patches/pcib_debug.patch New dmesg is in attach. Sheesh, found another bug (wasn't masking 'front' properly). Try updated patch (same URL). Great! It works! Excellent. I've committed the 2 bugs needed to fix your box. However, there is another bug that this exposed that I'd like you to test. Can you update to the latest HEAD, apply the updated pcib_debug.patch, and boot with 'hw.pci.pcib_clear=1' set from the loader? That should exercise the bug I'm worried about and see if my fixes for that (recursively growing windows) works correctly. Thanks John. I'm building HEAD now... What about 9.0? If I just apply r237008 it would be work? -- Andrey Zonov ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: mpt: Unable to memory map registers
On Wednesday, June 13, 2012 3:29:45 pm Andrey Zonov wrote: On 6/13/12 7:10 PM, John Baldwin wrote: On Tuesday, June 12, 2012 5:57:34 pm Andrey Zonov wrote: On 6/13/12 12:51 AM, John Baldwin wrote: On Tuesday, June 12, 2012 3:53:09 pm Andrey Zonov wrote: On 6/12/12 10:06 PM, John Baldwin wrote: [snip] Ok, I've added some more debugging. The patch is a bit larger now and you can fetch it from www.freebsd.org/~jhb/patches/pcib_debug.patch New dmesg is in attach. Sheesh, found another bug (wasn't masking 'front' properly). Try updated patch (same URL). Great! It works! Excellent. I've committed the 2 bugs needed to fix your box. However, there is another bug that this exposed that I'd like you to test. Can you update to the latest HEAD, apply the updated pcib_debug.patch, and boot with 'hw.pci.pcib_clear=1' set from the loader? That should exercise the bug I'm worried about and see if my fixes for that (recursively growing windows) works correctly. Thanks John. I'm building HEAD now... What about 9.0? If I just apply r237008 it would be work? Yes, I believe so. -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: mpt: Unable to memory map registers
On Monday, June 11, 2012 5:01:18 pm Andrey Zonov wrote: On 6/12/12 12:19 AM, John Baldwin wrote: On Monday, June 11, 2012 11:25:38 am Andrey Zonov wrote: On 6/11/12 6:19 PM, John Baldwin wrote: On Saturday, June 09, 2012 3:06:19 pm Andrey Zonov wrote: On 6/9/12 9:35 PM, Marius Strobl wrote: On Sat, Jun 09, 2012 at 12:58:05PM +0400, Andrey Zonov wrote: On 6/8/12 10:27 PM, John Baldwin wrote: On Friday, June 08, 2012 11:48:50 am Andrey Zonov wrote: On Fri, Jun 8, 2012 at 7:19 PM, John Baldwinj...@freebsd.org wrote: On Friday, June 08, 2012 3:14:19 am Andrey Zonov wrote: On 6/7/12 10:02 PM, Andrey Zonov wrote: Hi, I just upgraded a few machines from 8.2-STABLE (r221983) to 9.0- STABLE (r234600) and now they can't find any disk because SAS controller cannot initialize with the following diagnostic: mpt0:LSILogic SAS/SATA Adapter port 0xd000-0xd0ff irq 26 at device 3.0 on pci6 mpt0: 0x4000 bytes of rid 0x14 res 3 failed (0, 0x). mpt0: Unable to memory map registers. mpt0: Giving Up. pciconf -lv: mpt0@pci0:6:3:0: class=0x01 card=0x81dd1043 chip=0x00541000 rev=0x02 hdr=0x00 vendor = 'LSI Logic / Symbios Logic' device = 'SAS1068 PCI-X Fusion-MPT SAS' class = mass storage subclass = SCSI I tried to boot to latest HEAD and found the same problem. I also tried to build kernel with mpt driver from my 8.2. Controller didn't initialize with the same diagnostic. So it looks like the problem is not in mpt driver. Any help would be appreciated. +jhb@ Hi John, Could you please help me with the problem above? It looks like the problem is in PCI code and you changed things there. Can you get a verbose dmesg? Yes, it's in attach. Can you get the output of 'devinfo -u' and 'devinfo -rv' from a broken kernel? Attached. Can you also try setting 'debug.acpi.disable=sysres' in the loader? Didn't help. That's probably due to a typo, the corret loader tunable is debug.acpi.disabled=sysres (note the 'd'). This helps, thanks! Please explain what this means. Well, it's working around a bug in your BIOS, but in this case FreeBSD should have coped fine and it didn't. Please try using this patch without that tunable and get a verbose dmesg please: Unfortunately didn't work. Ah, it did work a bit, but it uncovered a larger bug. I didn't make the PCI-PCI bridge driver recursively grow windows. Try this: Still no luck. Ok, I've added some more debugging. The patch is a bit larger now and you can fetch it from www.freebsd.org/~jhb/patches/pcib_debug.patch -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: mpt: Unable to memory map registers
On 6/12/12 10:06 PM, John Baldwin wrote: [snip] Ok, I've added some more debugging. The patch is a bit larger now and you can fetch it from www.freebsd.org/~jhb/patches/pcib_debug.patch New dmesg is in attach. -- Andrey Zonov MP Configuration Table version 1.4 found at 0x800fcb70 Table 'FACP' at 0xdffb0290 Table 'APIC' at 0xdffb0390 APIC: Found table at 0xdffb0390 APIC: Using the MADT enumerator. MADT: Found CPU APIC ID 0 ACPI ID 1: enabled SMP: Added CPU 0 (AP) MADT: Found CPU APIC ID 4 ACPI ID 2: enabled SMP: Added CPU 4 (AP) MADT: Found CPU APIC ID 1 ACPI ID 3: enabled SMP: Added CPU 1 (AP) MADT: Found CPU APIC ID 5 ACPI ID 4: enabled SMP: Added CPU 5 (AP) MADT: Found CPU APIC ID 2 ACPI ID 5: enabled SMP: Added CPU 2 (AP) MADT: Found CPU APIC ID 6 ACPI ID 6: enabled SMP: Added CPU 6 (AP) MADT: Found CPU APIC ID 3 ACPI ID 7: enabled SMP: Added CPU 3 (AP) MADT: Found CPU APIC ID 7 ACPI ID 8: enabled SMP: Added CPU 7 (AP) Copyright (c) 1992-2012 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.0-STABLE #0 r+fffa9c7-dirty: Tue Jun 12 22:58:33 MSK 2012 r...@dst-dev.yandex.ru:/usr/obj/usr/src/sys/stable9-amd64-dtrace amd64 Preloaded elf kernel /boot/kernel.test/kernel at 0x80f1b000. Calibrating TSC clock ... TSC clock: 2826307647 Hz CPU: Intel(R) Xeon(R) CPU E5440 @ 2.83GHz (2826.31-MHz K8-class CPU) Origin = GenuineIntel Id = 0x1067a Family = 6 Model = 17 Stepping = 10 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0xc0ce3bdSSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,SSE4.1,XSAVE,OSXSAVE AMD Features=0x20100800SYSCALL,NX,LM AMD Features2=0x1LAHF TSC: P-state invariant, performance statistics real memory = 34359738368 (32768 MB) Physical memory chunk(s): 0x0001 - 0x0009bfff, 573440 bytes (140 pages) 0x0010 - 0x001f, 1048576 bytes (256 pages) 0x00f67000 - 0xdff9, 3741552640 bytes (913465 pages) 0xdffae000 - 0xdffa, 8192 bytes (2 pages) 0x0001 - 0x0007e2ea7fff, 29576822784 bytes (7220904 pages) avail memory = 33113874432 (31579 MB) Event timer LAPIC quality 400 ACPI APIC Table: 090808 APIC1308 INTR: Adding local APIC 1 as a target INTR: Adding local APIC 2 as a target INTR: Adding local APIC 3 as a target INTR: Adding local APIC 4 as a target INTR: Adding local APIC 5 as a target INTR: Adding local APIC 6 as a target INTR: Adding local APIC 7 as a target FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs FreeBSD/SMP: 2 package(s) x 4 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 cpu4 (AP): APIC ID: 4 cpu5 (AP): APIC ID: 5 cpu6 (AP): APIC ID: 6 cpu7 (AP): APIC ID: 7 APIC: CPU 0 has ACPI ID 1 APIC: CPU 1 has ACPI ID 3 APIC: CPU 2 has ACPI ID 5 APIC: CPU 3 has ACPI ID 7 APIC: CPU 4 has ACPI ID 2 APIC: CPU 5 has ACPI ID 4 APIC: CPU 6 has ACPI ID 6 APIC: CPU 7 has ACPI ID 8 x86bios: IVT 0x00-0x0004ff at 0xfe00 x86bios: SSEG 0x098000-0x098fff at 0xff800029 x86bios: EBDA 0x09e000-0x09 at 0xfe09e000 x86bios: ROM 0x0a-0x0fefff at 0xfe0a WARNING: VIMAGE (virtualized network stack) is a highly experimental feature. ULE: setup cpu 0 ULE: setup cpu 1 ULE: setup cpu 2 ULE: setup cpu 3 ULE: setup cpu 4 ULE: setup cpu 5 ULE: setup cpu 6 ULE: setup cpu 7 ACPI: RSDP 0xf9960 00024 (v02 ACPIAM) ACPI: XSDT 0xdffb0100 00074 (v01 090808 XSDT1308 20080908 MSFT 0097) ACPI: FACP 0xdffb0290 000F4 (v03 090808 FACP1308 20080908 MSFT 0097) ACPI: DSDT 0xdffb04d0 05414 (v01 CLSea CLSea007 0007 INTL 20051117) ACPI: FACS 0xdffbe000 00040 ACPI: APIC 0xdffb0390 000AA (v01 090808 APIC1308 20080908 MSFT 0097) ACPI: MCFG 0xdffb0490 0003C (v01 090808 OEMMCFG 20080908 MSFT 0097) ACPI: OEMB 0xdffbe040 00071 (v01 090808 OEMB1308 20080908 MSFT 0097) ACPI: HPET 0xdffb58f0 00038 (v01 090808 OEMHPET 20080908 MSFT 0097) ACPI: ASF! 0xdffb5928 00083 (v32 AMIASF E7230ASF 0001 INTL 20051117) ACPI: EINJ 0xdffb59b0 00130 (v01 AMIER AMI_EINJ 20080908 MSFT 0097) ACPI: BERT 0xdffb5b40 00030 (v01 AMIER AMI_BERT 20080908 MSFT 0097) ACPI: ERST 0xdffb5b70 001B0 (v01 AMIER AMI_ERST 20080908 MSFT 0097) ACPI: HEST 0xdffb5d20 000A8 (v01 AMIER AMI_HEST 20080908 MSFT 0097) MADT: Found IO APIC ID 8, Interrupt 0 at 0xfec0 ioapic0: Routing external 8259A's - intpin 0 MADT: Found IO APIC ID 9, Interrupt 24 at 0xfec88000 MADT: Found IO APIC ID 10, Interrupt 48 at 0xfec89000 MADT: Interrupt override: source 0, irq 2 ioapic0: Routing IRQ 0 - intpin 2 MADT: Interrupt override: source 9, irq 9 ioapic0: intpin 9 trigger: level lapic: Routing NMI -
Re: mpt: Unable to memory map registers
On Tuesday, June 12, 2012 3:53:09 pm Andrey Zonov wrote: On 6/12/12 10:06 PM, John Baldwin wrote: [snip] Ok, I've added some more debugging. The patch is a bit larger now and you can fetch it from www.freebsd.org/~jhb/patches/pcib_debug.patch New dmesg is in attach. Sheesh, found another bug (wasn't masking 'front' properly). Try updated patch (same URL). -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: mpt: Unable to memory map registers
On 6/13/12 12:51 AM, John Baldwin wrote: On Tuesday, June 12, 2012 3:53:09 pm Andrey Zonov wrote: On 6/12/12 10:06 PM, John Baldwin wrote: [snip] Ok, I've added some more debugging. The patch is a bit larger now and you can fetch it from www.freebsd.org/~jhb/patches/pcib_debug.patch New dmesg is in attach. Sheesh, found another bug (wasn't masking 'front' properly). Try updated patch (same URL). Great! It works! dmesg as always attached. -- Andrey Zonov Physical memory chunk(s): 0x0001 - 0x0009bfff, 573440 bytes (140 pages) 0x0010 - 0x001f, 1048576 bytes (256 pages) 0x00f67000 - 0xdff9, 3741552640 bytes (913465 pages) 0xdffae000 - 0xdffa, 8192 bytes (2 pages) 0x0001 - 0x0007e2ea7fff, 29576822784 bytes (7220904 pages) avail memory = 33113874432 (31579 MB) Event timer LAPIC quality 400 ACPI APIC Table: 090808 APIC1308 INTR: Adding local APIC 1 as a target INTR: Adding local APIC 2 as a target INTR: Adding local APIC 3 as a target INTR: Adding local APIC 4 as a target INTR: Adding local APIC 5 as a target INTR: Adding local APIC 6 as a target INTR: Adding local APIC 7 as a target FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs FreeBSD/SMP: 2 package(s) x 4 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 cpu4 (AP): APIC ID: 4 cpu5 (AP): APIC ID: 5 cpu6 (AP): APIC ID: 6 cpu7 (AP): APIC ID: 7 APIC: CPU 0 has ACPI ID 1 APIC: CPU 1 has ACPI ID 3 APIC: CPU 2 has ACPI ID 5 APIC: CPU 3 has ACPI ID 7 APIC: CPU 4 has ACPI ID 2 APIC: CPU 5 has ACPI ID 4 APIC: CPU 6 has ACPI ID 6 APIC: CPU 7 has ACPI ID 8 x86bios: IVT 0x00-0x0004ff at 0xfe00 x86bios: SSEG 0x098000-0x098fff at 0xff800029 x86bios: EBDA 0x09e000-0x09 at 0xfe09e000 x86bios: ROM 0x0a-0x0fefff at 0xfe0a WARNING: VIMAGE (virtualized network stack) is a highly experimental feature. ULE: setup cpu 0 ULE: setup cpu 1 ULE: setup cpu 2 ULE: setup cpu 3 ULE: setup cpu 4 ULE: setup cpu 5 ULE: setup cpu 6 ULE: setup cpu 7 ACPI: RSDP 0xf9960 00024 (v02 ACPIAM) ACPI: XSDT 0xdffb0100 00074 (v01 090808 XSDT1308 20080908 MSFT 0097) ACPI: FACP 0xdffb0290 000F4 (v03 090808 FACP1308 20080908 MSFT 0097) ACPI: DSDT 0xdffb04d0 05414 (v01 CLSea CLSea007 0007 INTL 20051117) ACPI: FACS 0xdffbe000 00040 ACPI: APIC 0xdffb0390 000AA (v01 090808 APIC1308 20080908 MSFT 0097) ACPI: MCFG 0xdffb0490 0003C (v01 090808 OEMMCFG 20080908 MSFT 0097) ACPI: OEMB 0xdffbe040 00071 (v01 090808 OEMB1308 20080908 MSFT 0097) ACPI: HPET 0xdffb58f0 00038 (v01 090808 OEMHPET 20080908 MSFT 0097) ACPI: ASF! 0xdffb5928 00083 (v32 AMIASF E7230ASF 0001 INTL 20051117) ACPI: EINJ 0xdffb59b0 00130 (v01 AMIER AMI_EINJ 20080908 MSFT 0097) ACPI: BERT 0xdffb5b40 00030 (v01 AMIER AMI_BERT 20080908 MSFT 0097) ACPI: ERST 0xdffb5b70 001B0 (v01 AMIER AMI_ERST 20080908 MSFT 0097) ACPI: HEST 0xdffb5d20 000A8 (v01 AMIER AMI_HEST 20080908 MSFT 0097) MADT: Found IO APIC ID 8, Interrupt 0 at 0xfec0 ioapic0: Routing external 8259A's - intpin 0 MADT: Found IO APIC ID 9, Interrupt 24 at 0xfec88000 MADT: Found IO APIC ID 10, Interrupt 48 at 0xfec89000 MADT: Interrupt override: source 0, irq 2 ioapic0: Routing IRQ 0 - intpin 2 MADT: Interrupt override: source 9, irq 9 ioapic0: intpin 9 trigger: level lapic: Routing NMI - LINT1 lapic: LINT1 trigger: edge lapic: LINT1 polarity: high ioapic0 Version 2.0 irqs 0-23 on motherboard ioapic1 Version 2.0 irqs 24-47 on motherboard ioapic2 Version 2.0 irqs 48-71 on motherboard cpu0 BSP: ID: 0x VER: 0x00050014 LDR: 0x DFR: 0x lint0: 0x00010700 lint1: 0x0400 TPR: 0x SVR: 0x01ff timer: 0x000100ef therm: 0x0001 err: 0x00f0 pmc: 0x00010400 kbd: new array size 4 kbd1 at kbdmux0 mem: memory nfslock: pseudo-device null: null device, zero device random: entropy source, Software, Yarrow cpuctl: access to MSR registers/cpuid info. io: I/O acpi0: 090808 XSDT1308 on motherboard PCIe: Memory Mapped configuration base @ 0xe000 ioapic0: routing intpin 9 (ISA IRQ 9) to lapic 0 vector 48 ACPI: Executed 1 blocks of module-level executable AML code acpi0: Power Button (fixed) acpi0: reservation of fed1c000, 4000 (3) failed acpi0: reservation of fed2, 25000 (3) failed acpi0: reservation of fed45000, 5b000 (3) failed acpi0: reservation of feda, 2 (3) failed acpi0: reservation of fec01000, 7f000 (3) failed acpi0: reservation of fec8, 6000 (3) failed acpi0: reservation of fec86000, a000 (3) failed acpi0: reservation of ff00, 40 (3) failed acpi0: reservation of ff40, 40 (3) failed acpi0: reservation of ff80, 40 (3) failed acpi0: reservation of ffc0, 40 (3) failed acpi0: reservation of fec0, 1000 (3) failed acpi0: reservation of fee0, 1000 (3) failed acpi0: reservation of 0, a (3) failed acpi0:
Re: mpt: Unable to memory map registers
On Saturday, June 09, 2012 3:06:19 pm Andrey Zonov wrote:
On 6/9/12 9:35 PM, Marius Strobl wrote:
On Sat, Jun 09, 2012 at 12:58:05PM +0400, Andrey Zonov wrote:
On 6/8/12 10:27 PM, John Baldwin wrote:
On Friday, June 08, 2012 11:48:50 am Andrey Zonov wrote:
On Fri, Jun 8, 2012 at 7:19 PM, John Baldwinj...@freebsd.org wrote:
On Friday, June 08, 2012 3:14:19 am Andrey Zonov wrote:
On 6/7/12 10:02 PM, Andrey Zonov wrote:
Hi,
I just upgraded a few machines from 8.2-STABLE (r221983) to 9.0-
STABLE
(r234600) and now they can't find any disk because SAS controller
cannot
initialize with the following diagnostic:
mpt0:LSILogic SAS/SATA Adapter port 0xd000-0xd0ff irq 26 at
device
3.0 on pci6
mpt0: 0x4000 bytes of rid 0x14 res 3 failed (0, 0x).
mpt0: Unable to memory map registers.
mpt0: Giving Up.
pciconf -lv:
mpt0@pci0:6:3:0: class=0x01 card=0x81dd1043 chip=0x00541000
rev=0x02
hdr=0x00
vendor = 'LSI Logic / Symbios Logic'
device = 'SAS1068 PCI-X Fusion-MPT SAS'
class = mass storage
subclass = SCSI
I tried to boot to latest HEAD and found the same problem. I also
tried
to build kernel with mpt driver from my 8.2. Controller didn't
initialize with the same diagnostic. So it looks like the problem is
not
in mpt driver.
Any help would be appreciated.
+jhb@
Hi John,
Could you please help me with the problem above? It looks like the
problem is in PCI code and you changed things there.
Can you get a verbose dmesg?
Yes, it's in attach.
Can you get the output of 'devinfo -u' and 'devinfo -rv' from a broken
kernel?
Attached.
Can you also try setting 'debug.acpi.disable=sysres' in the loader?
Didn't help.
That's probably due to a typo, the corret loader tunable is
debug.acpi.disabled=sysres (note the 'd').
This helps, thanks! Please explain what this means.
Well, it's working around a bug in your BIOS, but in this case FreeBSD should
have coped fine and it didn't. Please try using this patch without that
tunable and get a verbose dmesg please:
Index: sys/dev/pci/pci_pci.c
===
--- pci_pci.c (revision 236888)
+++ pci_pci.c (working copy)
@@ -893,9 +893,9 @@ pcib_grow_window(struct pcib_softc *sc, struct pci
if (start rman_get_start(w-res)) {
if (rman_first_free_region(w-rman, start_free, end_free) !=
0 || start_free != rman_get_start(w-res))
- end_free = rman_get_start(w-res) - 1;
+ end_free = rman_get_start(w-res);
if (end_free end)
- end_free = end;
+ end_free = end + 1;
/* Move end_free down until it is properly aligned. */
end_free = ~(align - 1);
--
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: mpt: Unable to memory map registers
On 6/11/12 6:19 PM, John Baldwin wrote:
On Saturday, June 09, 2012 3:06:19 pm Andrey Zonov wrote:
On 6/9/12 9:35 PM, Marius Strobl wrote:
On Sat, Jun 09, 2012 at 12:58:05PM +0400, Andrey Zonov wrote:
On 6/8/12 10:27 PM, John Baldwin wrote:
On Friday, June 08, 2012 11:48:50 am Andrey Zonov wrote:
On Fri, Jun 8, 2012 at 7:19 PM, John Baldwinj...@freebsd.orgwrote:
On Friday, June 08, 2012 3:14:19 am Andrey Zonov wrote:
On 6/7/12 10:02 PM, Andrey Zonov wrote:
Hi,
I just upgraded a few machines from 8.2-STABLE (r221983) to 9.0-
STABLE
(r234600) and now they can't find any disk because SAS controller
cannot
initialize with the following diagnostic:
mpt0:LSILogic SAS/SATA Adapterport 0xd000-0xd0ff irq 26 at
device
3.0 on pci6
mpt0: 0x4000 bytes of rid 0x14 res 3 failed (0, 0x).
mpt0: Unable to memory map registers.
mpt0: Giving Up.
pciconf -lv:
mpt0@pci0:6:3:0: class=0x01 card=0x81dd1043 chip=0x00541000
rev=0x02
hdr=0x00
vendor = 'LSI Logic / Symbios Logic'
device = 'SAS1068 PCI-X Fusion-MPT SAS'
class = mass storage
subclass = SCSI
I tried to boot to latest HEAD and found the same problem. I also
tried
to build kernel with mpt driver from my 8.2. Controller didn't
initialize with the same diagnostic. So it looks like the problem is
not
in mpt driver.
Any help would be appreciated.
+jhb@
Hi John,
Could you please help me with the problem above? It looks like the
problem is in PCI code and you changed things there.
Can you get a verbose dmesg?
Yes, it's in attach.
Can you get the output of 'devinfo -u' and 'devinfo -rv' from a broken
kernel?
Attached.
Can you also try setting 'debug.acpi.disable=sysres' in the loader?
Didn't help.
That's probably due to a typo, the corret loader tunable is
debug.acpi.disabled=sysres (note the 'd').
This helps, thanks! Please explain what this means.
Well, it's working around a bug in your BIOS, but in this case FreeBSD should
have coped fine and it didn't. Please try using this patch without that
tunable and get a verbose dmesg please:
Index: sys/dev/pci/pci_pci.c
===
--- pci_pci.c (revision 236888)
+++ pci_pci.c (working copy)
@@ -893,9 +893,9 @@ pcib_grow_window(struct pcib_softc *sc, struct pci
if (start rman_get_start(w-res)) {
if (rman_first_free_region(w-rman,start_free,end_free) !=
0 || start_free != rman_get_start(w-res))
- end_free = rman_get_start(w-res) - 1;
+ end_free = rman_get_start(w-res);
if (end_free end)
- end_free = end;
+ end_free = end + 1;
/* Move end_free down until it is properly aligned. */
end_free= ~(align - 1);
Unfortunately didn't work.
--
Andrey Zonov
MP Configuration Table version 1.4 found at 0x800fcb70
Table 'FACP' at 0xdffb0290
Table 'APIC' at 0xdffb0390
APIC: Found table at 0xdffb0390
APIC: Using the MADT enumerator.
MADT: Found CPU APIC ID 0 ACPI ID 1: enabled
SMP: Added CPU 0 (AP)
MADT: Found CPU APIC ID 4 ACPI ID 2: enabled
SMP: Added CPU 4 (AP)
MADT: Found CPU APIC ID 1 ACPI ID 3: enabled
SMP: Added CPU 1 (AP)
MADT: Found CPU APIC ID 5 ACPI ID 4: enabled
SMP: Added CPU 5 (AP)
MADT: Found CPU APIC ID 2 ACPI ID 5: enabled
SMP: Added CPU 2 (AP)
MADT: Found CPU APIC ID 6 ACPI ID 6: enabled
SMP: Added CPU 6 (AP)
MADT: Found CPU APIC ID 3 ACPI ID 7: enabled
SMP: Added CPU 3 (AP)
MADT: Found CPU APIC ID 7 ACPI ID 8: enabled
SMP: Added CPU 7 (AP)
Copyright (c) 1992-2012 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 9.0-STABLE #0 r+fffa9c7-dirty: Mon Jun 11 18:51:03 MSK 2012
r...@dst-dev.yandex.ru:/usr/obj/usr/src/sys/stable9-amd64-dtrace amd64
Preloaded elf kernel /boot/kernel.test/kernel at 0x80f1b000.
Calibrating TSC clock ... TSC clock: 2826308242 Hz
CPU: Intel(R) Xeon(R) CPU E5440 @ 2.83GHz (2826.31-MHz K8-class CPU)
Origin = GenuineIntel Id = 0x1067a Family = 6 Model = 17 Stepping = 10
Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE
Features2=0xc0ce3bdSSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,SSE4.1,XSAVE,OSXSAVE
AMD Features=0x20100800SYSCALL,NX,LM
AMD Features2=0x1LAHF
TSC: P-state invariant, performance statistics
real memory = 34359738368 (32768 MB)
Physical memory chunk(s):
0x0001 - 0x0009bfff, 573440 bytes (140 pages)
0x0010 - 0x001f, 1048576 bytes (256 pages)
0x00f67000 - 0xdff9, 3741552640 bytes (913465 pages)
0xdffae000 - 0xdffa, 8192 bytes (2 pages)
0x0001 -
Re: mpt: Unable to memory map registers
On Monday, June 11, 2012 11:25:38 am Andrey Zonov wrote:
On 6/11/12 6:19 PM, John Baldwin wrote:
On Saturday, June 09, 2012 3:06:19 pm Andrey Zonov wrote:
On 6/9/12 9:35 PM, Marius Strobl wrote:
On Sat, Jun 09, 2012 at 12:58:05PM +0400, Andrey Zonov wrote:
On 6/8/12 10:27 PM, John Baldwin wrote:
On Friday, June 08, 2012 11:48:50 am Andrey Zonov wrote:
On Fri, Jun 8, 2012 at 7:19 PM, John Baldwinj...@freebsd.org
wrote:
On Friday, June 08, 2012 3:14:19 am Andrey Zonov wrote:
On 6/7/12 10:02 PM, Andrey Zonov wrote:
Hi,
I just upgraded a few machines from 8.2-STABLE (r221983) to 9.0-
STABLE
(r234600) and now they can't find any disk because SAS controller
cannot
initialize with the following diagnostic:
mpt0:LSILogic SAS/SATA Adapterport 0xd000-0xd0ff irq 26 at
device
3.0 on pci6
mpt0: 0x4000 bytes of rid 0x14 res 3 failed (0, 0x).
mpt0: Unable to memory map registers.
mpt0: Giving Up.
pciconf -lv:
mpt0@pci0:6:3:0: class=0x01 card=0x81dd1043 chip=0x00541000
rev=0x02
hdr=0x00
vendor = 'LSI Logic / Symbios Logic'
device = 'SAS1068 PCI-X Fusion-MPT SAS'
class = mass storage
subclass = SCSI
I tried to boot to latest HEAD and found the same problem. I also
tried
to build kernel with mpt driver from my 8.2. Controller didn't
initialize with the same diagnostic. So it looks like the problem is
not
in mpt driver.
Any help would be appreciated.
+jhb@
Hi John,
Could you please help me with the problem above? It looks like the
problem is in PCI code and you changed things there.
Can you get a verbose dmesg?
Yes, it's in attach.
Can you get the output of 'devinfo -u' and 'devinfo -rv' from a broken
kernel?
Attached.
Can you also try setting 'debug.acpi.disable=sysres' in the loader?
Didn't help.
That's probably due to a typo, the corret loader tunable is
debug.acpi.disabled=sysres (note the 'd').
This helps, thanks! Please explain what this means.
Well, it's working around a bug in your BIOS, but in this case FreeBSD
should
have coped fine and it didn't. Please try using this patch without that
tunable and get a verbose dmesg please:
Unfortunately didn't work.
Ah, it did work a bit, but it uncovered a larger bug. I didn't make the
PCI-PCI bridge driver recursively grow windows. Try this:
Index: sys/dev/pci/pci_pci.c
===
--- pci_pci.c (revision 236888)
+++ pci_pci.c (working copy)
@@ -113,23 +113,27 @@ DRIVER_MODULE(pcib, pci, pcib_driver, pcib_devclas
/*
* Is a resource from a child device sub-allocated from one of our
- * resource managers?
+ * resource managers? If so, return the associated window.
*/
-static int
+static struct pcib_window *
pcib_is_resource_managed(struct pcib_softc *sc, int type, struct resource *r)
{
switch (type) {
case SYS_RES_IOPORT:
- return (rman_is_region_manager(r, sc-io.rman));
+ if (rman_is_region_manager(r, sc-io.rman))
+ return (sc-io);
+ break;
case SYS_RES_MEMORY:
/* Prefetchable resources may live in either memory rman. */
if (rman_get_flags(r) RF_PREFETCHABLE
rman_is_region_manager(r, sc-pmem.rman))
- return (1);
- return (rman_is_region_manager(r, sc-mem.rman));
+ return (sc-pmem);
+ if (rman_is_region_manager(r, sc-mem.rman))
+ return (sc-mem);
+ break;
}
- return (0);
+ return (NULL);
}
static int
@@ -871,6 +875,10 @@ pcib_grow_window(struct pcib_softc *sc, struct pci
goto updatewin;
}
+ /* Nothing to do if the request fits in the current window. */
+ if (start = rman_get_start(w-res) end = rman_get_end(w-res))
+ return (ENOSPC);
+
/*
* See if growing the window would help. Compute the minimum
* amount of address space needed on both the front and back
@@ -881,6 +889,10 @@ pcib_grow_window(struct pcib_softc *sc, struct pci
* edge of the window, grow from the inner edge of the free
* region. Otherwise grow from the window boundary.
*
+* As a special case, if the new region is an exact region
+* that is a superset of the current window, align the ends
+* and make a single adjust request to our parent.
+*
* XXX: Special case: if w-res is completely empty and the
* request size is larger than w-res, we should find the
* optimal aligned buffer containing w-res and allocate that.
@@ -890,12 +902,22 @@ pcib_grow_window(struct pcib_softc *sc, struct pci
attempting to grow %s window for (%#lx-%#lx,%#lx)\n,
w-name, start, end, count);
align =
Re: mpt: Unable to memory map registers
On 6/12/12 12:19 AM, John Baldwin wrote: On Monday, June 11, 2012 11:25:38 am Andrey Zonov wrote: On 6/11/12 6:19 PM, John Baldwin wrote: On Saturday, June 09, 2012 3:06:19 pm Andrey Zonov wrote: On 6/9/12 9:35 PM, Marius Strobl wrote: On Sat, Jun 09, 2012 at 12:58:05PM +0400, Andrey Zonov wrote: On 6/8/12 10:27 PM, John Baldwin wrote: On Friday, June 08, 2012 11:48:50 am Andrey Zonov wrote: On Fri, Jun 8, 2012 at 7:19 PM, John Baldwinj...@freebsd.org wrote: On Friday, June 08, 2012 3:14:19 am Andrey Zonov wrote: On 6/7/12 10:02 PM, Andrey Zonov wrote: Hi, I just upgraded a few machines from 8.2-STABLE (r221983) to 9.0- STABLE (r234600) and now they can't find any disk because SAS controller cannot initialize with the following diagnostic: mpt0:LSILogic SAS/SATA Adapter port 0xd000-0xd0ff irq 26 at device 3.0 on pci6 mpt0: 0x4000 bytes of rid 0x14 res 3 failed (0, 0x). mpt0: Unable to memory map registers. mpt0: Giving Up. pciconf -lv: mpt0@pci0:6:3:0: class=0x01 card=0x81dd1043 chip=0x00541000 rev=0x02 hdr=0x00 vendor = 'LSI Logic / Symbios Logic' device = 'SAS1068 PCI-X Fusion-MPT SAS' class = mass storage subclass = SCSI I tried to boot to latest HEAD and found the same problem. I also tried to build kernel with mpt driver from my 8.2. Controller didn't initialize with the same diagnostic. So it looks like the problem is not in mpt driver. Any help would be appreciated. +jhb@ Hi John, Could you please help me with the problem above? It looks like the problem is in PCI code and you changed things there. Can you get a verbose dmesg? Yes, it's in attach. Can you get the output of 'devinfo -u' and 'devinfo -rv' from a broken kernel? Attached. Can you also try setting 'debug.acpi.disable=sysres' in the loader? Didn't help. That's probably due to a typo, the corret loader tunable is debug.acpi.disabled=sysres (note the 'd'). This helps, thanks! Please explain what this means. Well, it's working around a bug in your BIOS, but in this case FreeBSD should have coped fine and it didn't. Please try using this patch without that tunable and get a verbose dmesg please: Unfortunately didn't work. Ah, it did work a bit, but it uncovered a larger bug. I didn't make the PCI-PCI bridge driver recursively grow windows. Try this: Still no luck. -- Andrey Zonov MP Configuration Table version 1.4 found at 0x800fcb70 Table 'FACP' at 0xdffb0290 Table 'APIC' at 0xdffb0390 APIC: Found table at 0xdffb0390 APIC: Using the MADT enumerator. MADT: Found CPU APIC ID 0 ACPI ID 1: enabled SMP: Added CPU 0 (AP) MADT: Found CPU APIC ID 4 ACPI ID 2: enabled SMP: Added CPU 4 (AP) MADT: Found CPU APIC ID 1 ACPI ID 3: enabled SMP: Added CPU 1 (AP) MADT: Found CPU APIC ID 5 ACPI ID 4: enabled SMP: Added CPU 5 (AP) MADT: Found CPU APIC ID 2 ACPI ID 5: enabled SMP: Added CPU 2 (AP) MADT: Found CPU APIC ID 6 ACPI ID 6: enabled SMP: Added CPU 6 (AP) MADT: Found CPU APIC ID 3 ACPI ID 7: enabled SMP: Added CPU 3 (AP) MADT: Found CPU APIC ID 7 ACPI ID 8: enabled SMP: Added CPU 7 (AP) Copyright (c) 1992-2012 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.0-STABLE #1 r+fffa9c7-dirty: Tue Jun 12 00:44:04 MSK 2012 r...@dst-dev.yandex.ru:/usr/obj/usr/src/sys/stable9-amd64-dtrace amd64 Preloaded elf kernel /boot/kernel.test/kernel at 0x80f1b000. Calibrating TSC clock ... TSC clock: 2826313691 Hz CPU: Intel(R) Xeon(R) CPU E5440 @ 2.83GHz (2826.31-MHz K8-class CPU) Origin = GenuineIntel Id = 0x1067a Family = 6 Model = 17 Stepping = 10 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0xc0ce3bdSSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,SSE4.1,XSAVE,OSXSAVE AMD Features=0x20100800SYSCALL,NX,LM AMD Features2=0x1LAHF TSC: P-state invariant, performance statistics real memory = 34359738368 (32768 MB) Physical memory chunk(s): 0x0001 - 0x0009bfff, 573440 bytes (140 pages) 0x0010 - 0x001f, 1048576 bytes (256 pages) 0x00f67000 - 0xdff9, 3741552640 bytes (913465 pages) 0xdffae000 - 0xdffa, 8192 bytes (2 pages) 0x0001 - 0x0007e2ea7fff, 29576822784 bytes (7220904 pages) avail memory = 33113874432 (31579 MB) Event timer LAPIC quality 400 ACPI APIC Table: 090808 APIC1308 INTR: Adding local APIC 1 as a target INTR: Adding local APIC 2 as a target INTR: Adding local APIC 3 as a target INTR: Adding local APIC 4 as a target INTR: Adding local APIC 5 as a target INTR: Adding local APIC 6 as a target INTR: Adding local APIC 7 as a target FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs FreeBSD/SMP: 2 package(s) x 4 core(s) cpu0
Re: mpt: Unable to memory map registers
On 6/8/12 10:27 PM, John Baldwin wrote: On Friday, June 08, 2012 11:48:50 am Andrey Zonov wrote: On Fri, Jun 8, 2012 at 7:19 PM, John Baldwinj...@freebsd.org wrote: On Friday, June 08, 2012 3:14:19 am Andrey Zonov wrote: On 6/7/12 10:02 PM, Andrey Zonov wrote: Hi, I just upgraded a few machines from 8.2-STABLE (r221983) to 9.0-STABLE (r234600) and now they can't find any disk because SAS controller cannot initialize with the following diagnostic: mpt0:LSILogic SAS/SATA Adapter port 0xd000-0xd0ff irq 26 at device 3.0 on pci6 mpt0: 0x4000 bytes of rid 0x14 res 3 failed (0, 0x). mpt0: Unable to memory map registers. mpt0: Giving Up. pciconf -lv: mpt0@pci0:6:3:0: class=0x01 card=0x81dd1043 chip=0x00541000 rev=0x02 hdr=0x00 vendor = 'LSI Logic / Symbios Logic' device = 'SAS1068 PCI-X Fusion-MPT SAS' class = mass storage subclass = SCSI I tried to boot to latest HEAD and found the same problem. I also tried to build kernel with mpt driver from my 8.2. Controller didn't initialize with the same diagnostic. So it looks like the problem is not in mpt driver. Any help would be appreciated. +jhb@ Hi John, Could you please help me with the problem above? It looks like the problem is in PCI code and you changed things there. Can you get a verbose dmesg? Yes, it's in attach. Can you get the output of 'devinfo -u' and 'devinfo -rv' from a broken kernel? Attached. Can you also try setting 'debug.acpi.disable=sysres' in the loader? Didn't help. -- Andrey Zonov # devinfo -rv nexus0 apic0 ram0 I/O memory addresses: 0x0-0x9fbff 0x10-0xdff9 0xdffae000-0xdffa 0x1-0x81fff acpi0 Interrupt request lines: 9 I/O ports: 0x10-0x1f 0x22-0x3f 0x44-0x4f 0x50-0x5f 0x60 0x62-0x63 0x64 0x65-0x6f 0x72-0x7f 0x80 0x84-0x86 0x88 0x8c-0x8e 0x90-0x9f 0xa2-0xbf 0xe0-0xef 0x480-0x4bf 0x4d0-0x4d1 0x800-0x87f 0xa00-0xa0f 0xa10-0xa1f I/O memory addresses: 0xc-0xc 0xe-0xf 0xe000-0xefff 0xfe00-0xfebf 0xfec0-0x cpu0 pnpinfo _HID=none _UID=0 at handle=\_PR_.P001 acpi_throttle0 coretemp0 est0 p4tcc0 cpufreq0 cpu1 pnpinfo _HID=none _UID=0 at handle=\_PR_.P002 coretemp1 est1 p4tcc1 cpufreq1 cpu2 pnpinfo _HID=none _UID=0 at handle=\_PR_.P003 coretemp2 est2 p4tcc2 cpufreq2 cpu3 pnpinfo _HID=none _UID=0 at handle=\_PR_.P004 coretemp3 est3 p4tcc3 cpufreq3 cpu4 pnpinfo _HID=none _UID=0 at handle=\_PR_.P005 coretemp4 est4 p4tcc4 cpufreq4 cpu5 pnpinfo _HID=none _UID=0 at handle=\_PR_.P006 coretemp5 est5 p4tcc5 cpufreq5 cpu6 pnpinfo _HID=none _UID=0 at handle=\_PR_.P007 coretemp6 est6 p4tcc6 cpufreq6 cpu7 pnpinfo _HID=none _UID=0 at handle=\_PR_.P008 coretemp7 est7 p4tcc7 cpufreq7 pcib0 pnpinfo _HID=PNP0A08 _UID=0 at handle=\_SB_.PCI0 I/O ports: 0xcf8-0xcff pci0 hostb0 pnpinfo vendor=0x8086 device=0x4003 subvendor=0x1043 subdevice=0x82aa class=0x06 at slot=0 function=0 pcib1 pnpinfo vendor=0x8086 device=0x4021 subvendor=0x8086 subdevice=0x8086 class=0x060400 at slot=1 function=0 handle=\_SB_.PCI0.NPE1 pci11 pcib2 pnpinfo vendor=0x8086 device=0x4025 subvendor=0x8086 subdevice=0x8086 class=0x060400 at slot=5 function=0 handle=\_SB_.PCI0.NPE5 pci10 pcib3 pnpinfo vendor=0x8086 device=0x4029 subvendor=0x8086 subdevice=0x8086 class=0x060400 at slot=9 function=0 handle=\_SB_.PCI0.NPES I/O ports: 0xd000-0xefff I/O memory addresses: 0xfdf0-0xfdff pci5 pcib4 pnpinfo vendor=0x8086 device=0x3500 subvendor=0x subdevice=0x class=0x060400 at slot=0 function=0 handle=\_SB_.PCI0.NPES.SPE4 pcib3 I/O port window: 0xe000-0xefff pcib3 memory window: 0xfdf0-0xfdff pci7 pcib5 pnpinfo vendor=0x8086 device=0x3510 subvendor=0x subdevice=0x class=0x060400 at slot=0 function=0 handle=\_SB_.PCI0.NPES.SPE4.SPE1 pci9 pcib6 pnpinfo vendor=0x8086 device=0x3518 subvendor=0x subdevice=0x class=0x060400 at slot=2 function=0 handle=\_SB_.PCI0.NPES.SPE4.P8PC pcib4 I/O port window: 0xe000-0xefff pcib4 memory window: 0xfdf0-0xfdff pci8 em0 pnpinfo
Re: mpt: Unable to memory map registers
On Sat, Jun 09, 2012 at 12:58:05PM +0400, Andrey Zonov wrote: On 6/8/12 10:27 PM, John Baldwin wrote: On Friday, June 08, 2012 11:48:50 am Andrey Zonov wrote: On Fri, Jun 8, 2012 at 7:19 PM, John Baldwinj...@freebsd.org wrote: On Friday, June 08, 2012 3:14:19 am Andrey Zonov wrote: On 6/7/12 10:02 PM, Andrey Zonov wrote: Hi, I just upgraded a few machines from 8.2-STABLE (r221983) to 9.0-STABLE (r234600) and now they can't find any disk because SAS controller cannot initialize with the following diagnostic: mpt0:LSILogic SAS/SATA Adapter port 0xd000-0xd0ff irq 26 at device 3.0 on pci6 mpt0: 0x4000 bytes of rid 0x14 res 3 failed (0, 0x). mpt0: Unable to memory map registers. mpt0: Giving Up. pciconf -lv: mpt0@pci0:6:3:0: class=0x01 card=0x81dd1043 chip=0x00541000 rev=0x02 hdr=0x00 vendor = 'LSI Logic / Symbios Logic' device = 'SAS1068 PCI-X Fusion-MPT SAS' class = mass storage subclass = SCSI I tried to boot to latest HEAD and found the same problem. I also tried to build kernel with mpt driver from my 8.2. Controller didn't initialize with the same diagnostic. So it looks like the problem is not in mpt driver. Any help would be appreciated. +jhb@ Hi John, Could you please help me with the problem above? It looks like the problem is in PCI code and you changed things there. Can you get a verbose dmesg? Yes, it's in attach. Can you get the output of 'devinfo -u' and 'devinfo -rv' from a broken kernel? Attached. Can you also try setting 'debug.acpi.disable=sysres' in the loader? Didn't help. That's probably due to a typo, the corret loader tunable is debug.acpi.disabled=sysres (note the 'd'). Marius ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: mpt: Unable to memory map registers
On 6/9/12 9:35 PM, Marius Strobl wrote: On Sat, Jun 09, 2012 at 12:58:05PM +0400, Andrey Zonov wrote: On 6/8/12 10:27 PM, John Baldwin wrote: On Friday, June 08, 2012 11:48:50 am Andrey Zonov wrote: On Fri, Jun 8, 2012 at 7:19 PM, John Baldwinj...@freebsd.org wrote: On Friday, June 08, 2012 3:14:19 am Andrey Zonov wrote: On 6/7/12 10:02 PM, Andrey Zonov wrote: Hi, I just upgraded a few machines from 8.2-STABLE (r221983) to 9.0-STABLE (r234600) and now they can't find any disk because SAS controller cannot initialize with the following diagnostic: mpt0:LSILogic SAS/SATA Adapter port 0xd000-0xd0ff irq 26 at device 3.0 on pci6 mpt0: 0x4000 bytes of rid 0x14 res 3 failed (0, 0x). mpt0: Unable to memory map registers. mpt0: Giving Up. pciconf -lv: mpt0@pci0:6:3:0: class=0x01 card=0x81dd1043 chip=0x00541000 rev=0x02 hdr=0x00 vendor = 'LSI Logic / Symbios Logic' device = 'SAS1068 PCI-X Fusion-MPT SAS' class = mass storage subclass = SCSI I tried to boot to latest HEAD and found the same problem. I also tried to build kernel with mpt driver from my 8.2. Controller didn't initialize with the same diagnostic. So it looks like the problem is not in mpt driver. Any help would be appreciated. +jhb@ Hi John, Could you please help me with the problem above? It looks like the problem is in PCI code and you changed things there. Can you get a verbose dmesg? Yes, it's in attach. Can you get the output of 'devinfo -u' and 'devinfo -rv' from a broken kernel? Attached. Can you also try setting 'debug.acpi.disable=sysres' in the loader? Didn't help. That's probably due to a typo, the corret loader tunable is debug.acpi.disabled=sysres (note the 'd'). This helps, thanks! Please explain what this means. -- Andrey Zonov ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: mpt: Unable to memory map registers
On 6/7/12 10:02 PM, Andrey Zonov wrote: Hi, I just upgraded a few machines from 8.2-STABLE (r221983) to 9.0-STABLE (r234600) and now they can't find any disk because SAS controller cannot initialize with the following diagnostic: mpt0: LSILogic SAS/SATA Adapter port 0xd000-0xd0ff irq 26 at device 3.0 on pci6 mpt0: 0x4000 bytes of rid 0x14 res 3 failed (0, 0x). mpt0: Unable to memory map registers. mpt0: Giving Up. pciconf -lv: mpt0@pci0:6:3:0: class=0x01 card=0x81dd1043 chip=0x00541000 rev=0x02 hdr=0x00 vendor = 'LSI Logic / Symbios Logic' device = 'SAS1068 PCI-X Fusion-MPT SAS' class = mass storage subclass = SCSI I tried to boot to latest HEAD and found the same problem. I also tried to build kernel with mpt driver from my 8.2. Controller didn't initialize with the same diagnostic. So it looks like the problem is not in mpt driver. Any help would be appreciated. +jhb@ Hi John, Could you please help me with the problem above? It looks like the problem is in PCI code and you changed things there. -- Andrey Zonov ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: mpt: Unable to memory map registers
On Friday, June 08, 2012 3:14:19 am Andrey Zonov wrote: On 6/7/12 10:02 PM, Andrey Zonov wrote: Hi, I just upgraded a few machines from 8.2-STABLE (r221983) to 9.0-STABLE (r234600) and now they can't find any disk because SAS controller cannot initialize with the following diagnostic: mpt0: LSILogic SAS/SATA Adapter port 0xd000-0xd0ff irq 26 at device 3.0 on pci6 mpt0: 0x4000 bytes of rid 0x14 res 3 failed (0, 0x). mpt0: Unable to memory map registers. mpt0: Giving Up. pciconf -lv: mpt0@pci0:6:3:0: class=0x01 card=0x81dd1043 chip=0x00541000 rev=0x02 hdr=0x00 vendor = 'LSI Logic / Symbios Logic' device = 'SAS1068 PCI-X Fusion-MPT SAS' class = mass storage subclass = SCSI I tried to boot to latest HEAD and found the same problem. I also tried to build kernel with mpt driver from my 8.2. Controller didn't initialize with the same diagnostic. So it looks like the problem is not in mpt driver. Any help would be appreciated. +jhb@ Hi John, Could you please help me with the problem above? It looks like the problem is in PCI code and you changed things there. Can you get a verbose dmesg? -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: mpt: Unable to memory map registers
On Friday, June 08, 2012 11:48:50 am Andrey Zonov wrote: On Fri, Jun 8, 2012 at 7:19 PM, John Baldwin j...@freebsd.org wrote: On Friday, June 08, 2012 3:14:19 am Andrey Zonov wrote: On 6/7/12 10:02 PM, Andrey Zonov wrote: Hi, I just upgraded a few machines from 8.2-STABLE (r221983) to 9.0-STABLE (r234600) and now they can't find any disk because SAS controller cannot initialize with the following diagnostic: mpt0: LSILogic SAS/SATA Adapter port 0xd000-0xd0ff irq 26 at device 3.0 on pci6 mpt0: 0x4000 bytes of rid 0x14 res 3 failed (0, 0x). mpt0: Unable to memory map registers. mpt0: Giving Up. pciconf -lv: mpt0@pci0:6:3:0: class=0x01 card=0x81dd1043 chip=0x00541000 rev=0x02 hdr=0x00 vendor = 'LSI Logic / Symbios Logic' device = 'SAS1068 PCI-X Fusion-MPT SAS' class = mass storage subclass = SCSI I tried to boot to latest HEAD and found the same problem. I also tried to build kernel with mpt driver from my 8.2. Controller didn't initialize with the same diagnostic. So it looks like the problem is not in mpt driver. Any help would be appreciated. +jhb@ Hi John, Could you please help me with the problem above? It looks like the problem is in PCI code and you changed things there. Can you get a verbose dmesg? Yes, it's in attach. Can you get the output of 'devinfo -u' and 'devinfo -rv' from a broken kernel? Can you also try setting 'debug.acpi.disable=sysres' in the loader? -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
