From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 15 16:49:26 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EB42B106566B for ; Wed, 15 Jun 2011 16:49:25 +0000 (UTC) (envelope-from papowell@astart.com) Received: from astart2.astart.com (99-111-96-109.uvs.sndgca.sbcglobal.net [99.111.96.109]) by mx1.freebsd.org (Postfix) with ESMTP id BBFBF8FC08 for ; Wed, 15 Jun 2011 16:49:25 +0000 (UTC) Received: from laptop_81.private (localhost [127.0.0.1]) by astart2.astart.com (8.14.4/8.14.4) with ESMTP id p5FGME66011135 for ; Wed, 15 Jun 2011 09:22:14 -0700 (PDT) (envelope-from papowell@astart.com) Message-ID: <4DF8DC3A.5050703@astart.com> Date: Wed, 15 Jun 2011 09:22:18 -0700 From: Patrick Powell Organization: Astart Technologies User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110312 Thunderbird/3.1.9 MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Shooting trouble on a PCI bus hang X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: papowell@astart.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Jun 2011 16:49:26 -0000 On 06/14/11 20:52, Ansar Mohammed wrote: > Hello All, > I have a system that is intermitently hanging during the initial PCI bus > scan during boot. I have turned on verbose logging and I cannot break to > debugger as its a hang. Can someone guide me to the relevant code section > where PCI bus enumeration occurs so that I may modify the kernel source to > output even more debug info. > > My hang occurs at the end of this partial dmesg output. > > Thank you! > > pci0: on pcib0 > pci0: domain=0, physical bus=0 > found-> vendor=0x100b, dev=0x0028, revid=0x21 > > domain=0, bus=0, slot=1, func=0 > class=06-00-00, hdrtype=0x00, mfdev=1 > cmdreg=0x0005, statreg=0x0220, cachelnsz=8 (dwords) > lattimer=0xf8 (7440 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > map[10]: type I/O Port, range 32, base 0xac1c, size 2, enabled > > found-> vendor=0x100b, dev=0x0030, revid=0x00 > > domain=0, bus=0, slot=1, func=1 > class=03-00-00, hdrtype=0x00, mfdev=0 > cmdreg=0x0003, statreg=0x0220, cachelnsz=8 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > map[10]: type Memory, range 32, base 0x41000000, size 24, enabled > map[14]: type Memory, range 32, base 0x40ffc000, size 14, enabled > map[18]: type Memory, range 32, base 0x40ff8000, size 14, enabled > map[1c]: type Memory, range 32, base 0x40ff4000, size 14, enabled > > found-> vendor=0x10ec, dev=0x8139, revid=0x10 > > domain=0, bus=0, slot=14, func=0 > class=02-00-00, hdrtype=0x00, mfdev=0 > cmdreg=0x0007, statreg=0x0290, cachelnsz=0 (dwords) > lattimer=0x40 (1920 ns), mingnt=0x20 (8000 ns), maxlat=0x40 (16000 ns) > intpin=a, irq=11 > powerspec 2 supports D0 D1 D2 D3 current D0 > map[10]: type I/O Port, range 32, base 0xef00, size 8, enabled > map[14]: type Memory, range 32, base 0xeff00000, size 8, enabled > > $PIR: 0:14 INTA routed to irq 11 > found-> vendor=0x1022, dev=0x2090, revid=0x03 > > domain=0, bus=0, slot=15, func=0 > class=06-01-00, hdrtype=0x00, mfdev=1 > cmdreg=0x0009, statreg=0x02a0, cachelnsz=8 (dwords) > lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > map[10]: type I/O Port, range 32, base 0x6000, size 3, enabled map[14]: type > I/O Port, range 32, base 0x6100, size 8, enabled map[18]: type I/O Port, > range 32, base 0x6200, size 6, enabled map[1c]: type I/O Port, range 32, > base 0, size 5, enabled map[20]: type I/O Port, range 32, base 0x9d00, size > 7, enabled map[24]: type I/O Port, range 32, base 0x9c00, size 6, enabled > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > Before you do anything else, get another set of hardware and try the same thing on it. I had a similar problem that turned out to be a bad SATA controller. It was only by accident that we had two identical systems, one good and one bad. -- Patrick Powell Astart Technologies papowell@astart.com 1530 Jamacha Road, Suite X, Network and System San Diego, CA 92019 Consulting 858-874-6543 Web Site: www.astart.com