From owner-freebsd-current@FreeBSD.ORG Sat Sep 2 13:19:01 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 401C216A4E1 for ; Sat, 2 Sep 2006 13:19:01 +0000 (UTC) (envelope-from eculp@bafirst.com) Received: from 72-12-2-214.wan.networktel.net (72-12-2-214.wan.networktel.net [72.12.2.214]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8EE4943D79 for ; Sat, 2 Sep 2006 13:18:53 +0000 (GMT) (envelope-from eculp@bafirst.com) Received: from localhost (localhost [127.0.0.1]) (uid 80) by 72-12-2-214.wan.networktel.net with local; Sat, 02 Sep 2006 08:18:52 -0500 id 00095801.44F984BC.000149A1 Received: from dsl-189-129-2-180.prod-infinitum.com.mx (dsl-189-129-2-180.prod-infinitum.com.mx [189.129.2.180]) by mail.bafirst.com (Horde MIME library) with HTTP; Sat, 02 Sep 2006 08:18:52 -0500 Message-ID: <20060902081852.d18fktn1ck80ss00@mail.bafirst.com> Date: Sat, 02 Sep 2006 08:18:52 -0500 From: eculp@bafirst.com To: freebsd-current@freebsd.org References: <1157154024.835.6.camel@atomizer.opensourcebeef.net> <7579f7fb0609011848p1ecc9d4dh47eb259cc3441ddb@mail.gmail.com> In-Reply-To: <7579f7fb0609011848p1ecc9d4dh47eb259cc3441ddb@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=_44se4tiiales" Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) 4.1-cvs Subject: Re: LSI 1030 mpt doesn't work if I build a new kernel 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: Sat, 02 Sep 2006 13:19:01 -0000 This message is in MIME format. --=_44se4tiiales Content-Type: text/plain; charset=ISO-8859-1; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit Quoting Matthew Jacob : > Can you tell me more precisely what hardware you have? It looks like I'm not the only one suffering with this but mine is on a colocated machine in another country and I haven't been able to see the errors but I haven't been able to boot a new kernel and am still using kernel.old from June 16, 2006. Since all I know from here is that it doesn't boot. It is a dell 2650 and I've attached a boot message for a reboot yesterday with the old kernel after failing to boot with the new one. Any help appreciated, ed With the old kernel I'm seeing a lot of the following messages that I have no idea what they mean much less how to fix them or even if I should ignore them, but just in case: mpt0: port 0xec00-0xecff mem 0xdfdf0000-0xdfdfffff,0xdfde0000-0xdfdeffff irq 34 at device 5.0 on pci2 ...skipping... (da0:mpt0:0:0:0): tagged openings now 140 (da0:mpt0:0:0:0): Retrying Command (da0:mpt0:0:0:0): Queue Full (da0:mpt0:0:0:0): tagged openings now 139 (da0:mpt0:0:0:0): Retrying Command (da0:mpt0:0:0:0): Queue Full (da0:mpt0:0:0:0): tagged openings now 138 (da0:mpt0:0:0:0): Retrying Command (da0:mpt0:0:0:0): Queue Full (da0:mpt0:0:0:0): tagged openings now 137 > > On 9/1/06, Rod Person wrote: >> I've been struggling with this for a month or two now. >> >> I installed FreeBSD current 7 with a march snapshot and this work good, >> but I've tried to build a new kernel for the 2 month period and building >> a kernel causes the mpt driver to panic on boot. >> >> Here is so of the boot message: >> >> mpt1: [GIANT-LOCKED] >> mpt1: MPI Version=1.2.14.0 >> mpt1: mpt_wait_req(4) timed out >> mpt1: read_cfg_header timed out >> mpt1: mpt_wait_req(6) timed out >> mpt1: port 0 enable timed out >> mpt1: failed to enable port 0 >> >> then this repeats until the system hangs: >> >> mpt0: Address Reply: >> SCSI Target Command Buffer Reply @ 0xffffffffacc7a200 >> IOC Status Success >> IOCLogInfo 0x00000000 >> MsgLength 0x05 >> MsgFlags 0x00 >> MsgContext 0x0003005d >> mpt0: Reply Frame Ignored >> mpt0: Default Handler Called: req=0xffffffff80e49050:95 >> reply_descriptor=dc913980 frame=0xffffffffacc7a300 >> mpt0: Address Reply: >> >> I was wondering if this is a known problem or if there are any hints on >> correcting this? >> >> Rod >> >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >> > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > --=_44se4tiiales Content-Type: application/octet-stream; name="dmesg.boot" Content-Disposition: attachment; filename="dmesg.boot" Content-Transfer-Encoding: 7bit Copyright (c) 1992-2006 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 7.0-CURRENT #140: Fri Jun 16 06:09:11 CDT 2006 eculp@bafirst.com:/usr/obj/usr/src/sys/ECscsi Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.00GHz (2992.71-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf41 Stepping = 1 Features=0xbfebfbff Features2=0x641d AMD Features=0x20100000 Logical CPUs per core: 2 real memory = 3220963328 (3071 MB) avail memory = 3150901248 (3004 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 6 cpu3 (AP): APIC ID: 7 ioapic0: Changing APIC ID to 8 ioapic1: Changing APIC ID to 9 ioapic1: WARNING: intbase 32 != expected base 24 ioapic2: Changing APIC ID to 10 ioapic2: WARNING: intbase 64 != expected base 56 ioapic3: Changing APIC ID to 11 ioapic3: WARNING: intbase 96 != expected base 88 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 32-55 on motherboard ioapic2 irqs 64-87 on motherboard ioapic3 irqs 96-119 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 2.0 on pci0 pci1: on pcib1 pcib2: at device 0.0 on pci1 pci2: on pcib2 mpt0: port 0xec00-0xecff mem 0xdfdf0000-0xdfdfffff,0xdfde0000-0xdfdeffff irq 34 at device 5.0 on pci2 mpt0: [GIANT-LOCKED] mpt0: MPI Version=1.2.12.0 mpt1: port 0xe800-0xe8ff mem 0xdfdd0000-0xdfddffff,0xdfdc0000-0xdfdcffff irq 33 at device 5.1 on pci2 mpt1: [GIANT-LOCKED] mpt1: MPI Version=1.2.12.0 pcib3: at device 0.2 on pci1 pci3: on pcib3 pcib4: at device 3.0 on pci0 pci4: on pcib4 pcib5: at device 0.0 on pci4 pci5: on pcib5 pcib6: at device 0.2 on pci4 pci6: on pcib6 pcib7: at device 4.0 on pci0 pci7: on pcib7 pcib8: at device 5.0 on pci0 pci10: on pcib8 pcib9: at device 0.0 on pci10 pci11: on pcib9 em0: port 0xccc0-0xccff mem 0xdf8e0000-0xdf8fffff irq 64 at device 7.0 on pci11 em0: Ethernet address: 00:11:43:ef:bc:a7 em0: [FAST] pcib10: at device 0.2 on pci10 pci12: on pcib10 em1: port 0xbcc0-0xbcff mem 0xdf6e0000-0xdf6fffff irq 65 at device 8.0 on pci12 em1: Ethernet address: 00:11:43:ef:bc:a8 em1: [FAST] pcib11: at device 6.0 on pci0 pci13: on pcib11 pci0: at device 29.0 (no driver attached) pci0: at device 29.1 (no driver attached) pci0: at device 29.2 (no driver attached) pci0: at device 29.7 (no driver attached) pcib12: at device 30.0 on pci0 pci16: on pcib12 vgapci0: port 0x9c00-0x9cff mem 0xd0000000-0xd7ffffff,0xdf2f0000-0xdf2fffff irq 18 at device 13.0 on pci16 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio0: [FAST] pmtimer0 on isa0 orm0: at iomem 0xc0000-0xcafff,0xcb000-0xcbfff,0xcc000-0xcffff,0xd0000-0xd0fff,0xec000-0xeffff pnpid ORM0000 on isa0 ppc0: at port 0x278-0x27f irq 7 on isa0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 ppc0: [GIANT-LOCKED] sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec acd0: CDROM at ata0-master UDMA33 Waiting 5 seconds for SCSI devices to settle ses0 at mpt0 bus 0 target 6 lun 0 ses0: Fixed Processor SCSI-2 device ses0: 3.300MB/s transfers ses0: SAF-TE Compliant Device SMP: AP CPU #3 Launched! SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! da0 at mpt0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled da0: 70007MB (143374650 512 byte sectors: 255H 63S/T 8924C) Trying to mount root from ufs:/dev/da0s1a em0: Link is Down em1: Link is Down em0: Link is up 100 Mbps Full Duplex Linux ELF exec handler installed em1: Link is up 100 Mbps Full Duplex em1: link state changed to UP --=_44se4tiiales--