Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 20 Jun 2011 08:49:10 -0400
From:      John Baldwin <jhb@freebsd.org>
To:        freebsd-hackers@freebsd.org
Cc:        Ansar Mohammed <ansarm@gmail.com>
Subject:   Re: Fwd: Shooting trouble on a PCI bus hang
Message-ID:  <201106200849.10862.jhb@freebsd.org>
In-Reply-To: <BANLkTinhOxLXzg=zH9TMHX13ppSfcX%2By4Q@mail.gmail.com>
References:  <BANLkTinGGTpwGdUFSW7jNHmpR8fyYoGd6Q@mail.gmail.com> <BANLkTimrYbXSaZtRtZ5%2BPst_S=X9nu8uHA@mail.gmail.com> <BANLkTinhOxLXzg=zH9TMHX13ppSfcX%2By4Q@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sunday, June 19, 2011 12:35:49 pm Ansar Mohammed wrote:
> 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?

Well, if that was the last device on the bus it might be in a device driver
probe routine.  You can try adding more printfs to device_probe(), etc. to 
output each driver name as it probes each device perhaps.

-- 
John Baldwin



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201106200849.10862.jhb>