From owner-freebsd-hackers@FreeBSD.ORG Sun Jun 19 16:35:52 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 72F001065675 for ; Sun, 19 Jun 2011 16:35:52 +0000 (UTC) (envelope-from ansarm@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 457CB8FC26 for ; Sun, 19 Jun 2011 16:35:52 +0000 (UTC) Received: by pzk27 with SMTP id 27so3977727pzk.13 for ; Sun, 19 Jun 2011 09:35:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=MKV1/ERAcJtZk4ZV+xPqTCS1zA5Rispt68sln2EyiHI=; b=W+tfsT0Re7HbzObVRpY2d2NwMoRkMmqcXsSGrSXWEylwCDl60n1FRQHVlYMy/N2LCj Scf8fY+GnewfRPewzjWEdFeK9d1FVsa9sWMsehrGPSCkD7yc5WouHZr9OI1SX4CGtkGQ F7k7pz8qMwljTWz9uPERiAMiIAyhbonIrsx6I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=ToziGIJXT7scYZ9DaBbe0+RQO5tPzhJ/DS1IW74CIk8ZkjgfDSd4s3pbop0JaCOBMH cAet8r6HG/Nomguj3e2nTWeQNBiDqEAcdF9c5Omi54WcJvXatRf80cHhJyUlTqabVSfC 7F5XnrJjw7c16He456XG+Z9NsNOjDG+/4dsC4= MIME-Version: 1.0 Received: by 10.68.28.133 with SMTP id b5mr1577259pbh.264.1308501350067; Sun, 19 Jun 2011 09:35:50 -0700 (PDT) Received: by 10.68.58.227 with HTTP; Sun, 19 Jun 2011 09:35:49 -0700 (PDT) In-Reply-To: References: <4DF8DC3A.5050703@astart.com> Date: Sun, 19 Jun 2011 12:35:49 -0400 Message-ID: From: Ansar Mohammed To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Fwd: Shooting trouble on a PCI bus hang X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Jun 2011 16:35:52 -0000 I appreciate that. The system works fine with NetBSD, LInux and Windows XP, so I doubt its hardware. Interesting though that OpenBSD has the same issue. A question about the debug kernel load process: as it hangs on * pci_print_verbose* in pci.c, can I deduce that this is the exact code segment that is the issue? On Wed, Jun 15, 2011 at 12:22 PM, Patrick Powell wrote: > 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 > > ______________________________**_________________ > 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 " >