From owner-freebsd-stable@FreeBSD.ORG Sun Nov 16 08:22:49 2008 Return-Path: Delivered-To: FreeBSD-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 24F9A1065680 for ; Sun, 16 Nov 2008 08:22:49 +0000 (UTC) (envelope-from rorya+freebsd.org@TrueStep.com) Received: from Tserver.TrueStep.com (Tserver.TrueStep.com [64.253.96.188]) by mx1.freebsd.org (Postfix) with ESMTP id A470C8FC0A for ; Sun, 16 Nov 2008 08:22:48 +0000 (UTC) (envelope-from rorya+freebsd.org@TrueStep.com) Received: from Cypher.TrueStep (Cypher.TrueStep [10.101.1.8]) (authenticated bits=0) by Tserver.TrueStep.com (8.14.3/8.14.3) with ESMTP id mAG8MdVw034854 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 16 Nov 2008 03:22:45 -0500 (EST) (envelope-from rorya+freebsd.org@TrueStep.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=TrueStep.com; s=default; t=1226823765; bh=0YjGTkXW3zdiI7BXxIPgTgDew0KOoE0R7hTb3jN JaOs=; h=Cc:Message-Id:From:To:In-Reply-To:Content-Type: Content-Transfer-Encoding:Mime-Version:Subject:Date:References; b=lF7Yd6p7xCG8CrHT02HMgP1Q2/qIdn4SydvXv5zU6C8/DvgVPVYRL2rvhfTcigeT0 4UPXW7gqKhDxu08FWlPDAtOV0WAzE6pzAZrk9qJcNiUVlf5ykbp7CGohXsBMdDZB5Y4 0qpqsGJmsgczkP3Y2ezxxhfQw5w/QJJX+Tnu9Vw= Message-Id: <9C64A87F-1359-4694-8238-6C4D4B025BE3@TrueStep.com> From: Rory Arms To: Ken Smith In-Reply-To: <1226078239.37011.37.camel@bauer.cse.buffalo.edu> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Date: Sun, 16 Nov 2008 03:22:39 -0500 References: <9592E887-75F3-473F-9581-F9C22A9936A6@TrueStep.com> <1226078239.37011.37.camel@bauer.cse.buffalo.edu> X-Mailer: Apple Mail (2.929.2) Cc: FreeBSD-stable@FreeBSD.org Subject: Re: 6.4-RC2 crashes after a few minutes of uptime X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Nov 2008 08:22:49 -0000 On 2008-11-07, at 12:17 , Ken Smith wrote: > On Fri, 2008-11-07 at 00:00 -0500, Rory Arms wrote: >> Well, if I can assist with further debugging, let me know. > > The person who followed up with a list of things that *may* have made > the problem go away mentioned one of the things was disabling powerd. > Do you have that enable, and if yes would you mind disabling it to see > if that's the culprit? Ken, Ok, guess something is amiss with the CD-ROM drive on this notebook, as in GNOME, it flashes an icon of a CD on the desktop from time to time, as if it has detected a disc in the drive. But of course there is no disc in the drive. I believe it did the same with 6.3 though, but as said before didn't ever panic due to this issue. So, some anecdotal info, after running RC2 for a few days now. It seems the pattern is that it seems to always panic a few minutes after a first cold boot, but then seems to remain stable after the second boot. Odd, as with 6.3 this didn't happen. So, I happened to catch a panic while working in the syscons console after one of these cold boots. As far as I can tell, the panic does have something to do with the the CD-ROM drive, as right after I saw this message on the console, it immediately paniced: acd0: WARNING - PREVENT_ALLOW read data overrun 18>0 and then the panic is as follows: kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode fault virtual address = 0x78 fault code = supervisor read, page not present instruction pointer = 0x20:0xc06d39b9 stack pointer = 0x28:0xca865c10 frame pointer = 0x28:0xca865c14 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = 19 (swi6: task queue) trap number = 12 panic: page fault Uptime: 1h9m7s Physical memory: 179MB Dumping 43MB: 28 12 Dump complete This is also the computer, as you may recall, that I can't ever get kgdb(1) to open the core dump file. Note the uptime on that particular boot was 1h because I pretty much let it sit idle after booting. So, gdm loaded and then I switched to syscons, logged in, and then pretty much let it idle, till it paniced. Hope that helps, - rory