From owner-freebsd-current@FreeBSD.ORG Sat Aug 30 10:28:51 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6584F16A4BF for ; Sat, 30 Aug 2003 10:28:51 -0700 (PDT) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id D105143FBD for ; Sat, 30 Aug 2003 10:28:50 -0700 (PDT) (envelope-from bleez@comcast.net) Received: from gravy.homeunix.net ([68.81.196.221]) by comcast.net (rwcrmhc12) with ESMTP id <20030830172515014000t9rhe>; Sat, 30 Aug 2003 17:25:15 +0000 Received: from gravy.homeunix.net (gravy.homeunix.net [192.168.1.2]) by gravy.homeunix.net (8.12.9/8.12.9) with ESMTP id h7UHPEGF000469; Sat, 30 Aug 2003 13:25:14 -0400 (EDT) (envelope-from bleez@comcast.net) Date: Sat, 30 Aug 2003 13:25:14 -0400 (EDT) From: Bryan Liesner To: Kenneth Culver Message-ID: <20030830131232.T462@gravy.homeunix.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: more hints X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Aug 2003 17:28:51 -0000 If I remove "device pmtimer" from my config, I get a consistent panic, or variation of: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0135b0a7 stack pointer = 0x10:0xd68f2c48 frame pointer = 0x10:0xd68f2c64 code segment = base 0x0 limit 0xffff, type 0x1b processor eflags = interrupt enabled, resume, IOPL=0 current process = 12 (swi7: tty:sio clock) trap number = 12 panic page fault ... This is with leaving my USB 2.0 drive turned on during boot time. If I use the same kernel (sans pmtimer) , but boot with my USB drive turned off, all is well. Or, I can put pmtimer back in the kernel and boot with the drive turned on, but sooner or later I'll get some type of panic. Some kind of timimg issue?. I think all of these panics have something to do with leaving the USB drive on at boot time. It seems like I don't have any issues if it stays turned off. That's probably why we're not seeing any reports, I doubt a lot of folks are using a USB 2.0 HD along with ehci... Again, all this started shortly after July 14th. The USB DMA changes may have something to do with this... -- ============================================================= = Bryan D. Liesner LeezSoft Communications, Inc. = = A subsidiary of LeezSoft Inc. = = bleez@comcast.net Home of the Gipper = =============================================================