From owner-freebsd-hackers Wed May 10 15:57:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 7ACC837B9C6 for ; Wed, 10 May 2000 15:57:50 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA55949; Wed, 10 May 2000 16:57:45 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA95984; Wed, 10 May 2000 16:57:23 -0600 (MDT) Message-Id: <200005102257.QAA95984@harmony.village.org> To: Peter Jeremy Subject: Re: Can NMI drop a hanging FreeBSD kernel into DDB? Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 11 May 2000 07:01:43 +1000." <00May11.070143est.115219@border.alcanet.com.au> References: <00May11.070143est.115219@border.alcanet.com.au> Date: Wed, 10 May 2000 16:57:23 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <00May11.070143est.115219@border.alcanet.com.au> Peter Jeremy writes: : I thought the PCI bus was isolated from the CPU<->memory bus so this : couldn't occur. The trap handler should start OK, but just can't do : any I/O because the PCI bus is hung. I'm not sure why things happen this way. I just know that I've not been able to get a NMI to break into the debugger when certain hardware that I've worked on in the past when it desided to hang. I don't know if that's because this also hung the host bridge so that no interrupt code could fetch it from memory, or what the deal was. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message