From owner-freebsd-hackers Mon Apr 10 11:30:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from auemail2.firewall.lucent.com (auemail2.lucent.com [192.11.223.163]) by hub.freebsd.org (Postfix) with ESMTP id BD3E137B71B for ; Mon, 10 Apr 2000 11:30:08 -0700 (PDT) (envelope-from gcorcoran@lucent.com) Received: from auemail2.firewall.lucent.com (localhost [127.0.0.1]) by auemail2.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id OAA09452 for ; Mon, 10 Apr 2000 14:30:02 -0400 (EDT) Received: from mhmail.mh.lucent.com (h135-3-115-8.lucent.com [135.3.115.8]) by auemail2.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id OAA09440 for ; Mon, 10 Apr 2000 14:30:02 -0400 (EDT) Received: from lucent.com by mhmail.mh.lucent.com (8.8.8+Sun/EMS-1.5 sol2) id OAA16405; Mon, 10 Apr 2000 14:30:01 -0400 (EDT) Message-ID: <38F21FFB.79E2B0B7@lucent.com> Date: Mon, 10 Apr 2000 14:39:55 -0400 From: "Gary T. Corcoran" Organization: Lucent Microelectronics - Modem and Multimedia Systems X-Mailer: Mozilla 4.06 [en] (Win98; U) MIME-Version: 1.0 To: FreeBSD Hackers Subject: Fatal trap 12 in arpintr in FreeBSD 4.0-Release Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I mentioned the other day, after installing FreeBSD 4.0-Release I started getting random spontaneous reboots while in X (after running FreeBSD 3.4-Release for 2 months without any problems). Now that I've started debugging my driver, I enabled DDB, and now instead of rebooting I'm crashing into DDB (when my driver isn't loaded)... (I'm also crashing with my driver, but that's another story :) I left my machine sit at the console login prompt over the weekend, and today found it had crashed into DDB, showing a "Fatal trap 12: page fault while in kernel mode", which happened at arpintr+0x9C. And I'm fairly sure this is exactly the same trap I saw a couple of times since enabling DDB. I'm completely new to using DDB, but a "trace" showed that arpintr was called from swi_net_next, which was called from Xresume11 (??), the trace then shows "--- interrupt", having been called from default_halt(). Oh, and the "current process" was "Idle". (Is Xresume11 part of X-Windows??) Just to be clear: X was *not* running, this was a console login prompt, and no "user programs" were running in the background. Does this make sense to anyone? I've seen some other reports of "spontaneous reboots" with 4.0 on the -stable list - perhaps this is the cause for those people as well? As I said, I'm new to debugging on BSD, so if the above isn't sufficient info for someone familiar with the code to find the problem, give me explicit instructions and maybe I can provide more info... Gary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message