From owner-freebsd-current@FreeBSD.ORG  Sun Aug 31 08:54:21 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 EFAEC16A4BF
	for <freebsd-current@freebsd.org>;
	Sun, 31 Aug 2003 08:54:21 -0700 (PDT)
Received: from mailhub.yumyumyum.org (dsl092-171-091.wdc2.dsl.speakeasy.net
	[66.92.171.91])	by mx1.FreeBSD.org (Postfix) with ESMTP id BE5A043FE9
	for <freebsd-current@freebsd.org>;
	Sun, 31 Aug 2003 08:54:20 -0700 (PDT)
	(envelope-from culverk@yumyumyum.org)
Received: by mailhub.yumyumyum.org (Postfix, from userid 1001)
	id 2F5DE67; Sun, 31 Aug 2003 11:53:58 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
	by mailhub.yumyumyum.org (Postfix) with ESMTP
	id 2354918; Sun, 31 Aug 2003 11:53:58 -0400 (EDT)
Date: Sun, 31 Aug 2003 11:53:58 -0400 (EDT)
From: Kenneth Culver <culverk@yumyumyum.org>
To: Bryan Liesner <bleez@comcast.net>
In-Reply-To: <20030830131232.T462@gravy.homeunix.net>
Message-ID: <20030831115238.Y35538@alpha.yumyumyum.org>
References: <20030830131232.T462@gravy.homeunix.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-current@freebsd.org
Subject: Re: 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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 31 Aug 2003 15:54:22 -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...
>
I'll have time tomorrow to look at the commit logs, so I'll check out what
changes went in, then make patches for each one that is likely to be a
problem, and then submit them to you. That will allow you to pinpoint the
exact commit that caused the problem.

Ken