From owner-freebsd-stable@FreeBSD.ORG Sun Sep 6 10:11:43 2009 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A32061065670; Sun, 6 Sep 2009 10:11:43 +0000 (UTC) (envelope-from tejblum@yandex-team.ru) Received: from archeopterix.yandex.ru (archeopterix.yandex.ru [93.158.136.52]) by mx1.freebsd.org (Postfix) with ESMTP id 5CBE28FC0C; Sun, 6 Sep 2009 10:11:43 +0000 (UTC) Received: from tejblum.pp.ru (dhcp250-245.yandex.ru [87.250.250.245]) by archeopterix.yandex.ru (Postfix) with ESMTPS id B19E459D948; Sun, 6 Sep 2009 13:53:55 +0400 (MSD) Message-ID: <4AA386B1.9020501@yandex-team.ru> Date: Sun, 06 Sep 2009 13:53:53 +0400 From: Dmitrij Tejblum User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.17) Gecko/20081109 SeaMonkey/1.1.12 MIME-Version: 1.0 To: stable@freebsd.org, jhb@freebsd.org References: <200909061102.40450.thierry.herbelot@free.fr> In-Reply-To: <200909061102.40450.thierry.herbelot@free.fr> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Thierry Herbelot Subject: Re: Panic in recent 7.2-Stable 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, 06 Sep 2009 10:11:43 -0000 Thierry Herbelot wrote: > Hello, > > I'm having a panic with the latest kernel build of my -Stable file server > (sources cvsupped around yesterday evening, CEST). The panic happens soon > after entering multi-user : > > panic: vm_phys_paddr_to_vm_page: paddr 0xf0000 is not in any segment > KDB: enter: panic > [thread pid 1005 tid 100154 ] > Stopped at kdb_enter_why+0x3a: movl $0,kdb_why > db> where > Tracing pid 1005 tid 100154 td 0x8ecad480 > kdb_enter_why(80ba731f,80ba731f,80bc1ad6,fb301a94,fb301a94,...) at > kdb_enter_why+0x3a > panic(80bc1ad6,f0000,0,8ecad480,0,...) at panic+0xd1 > vm_phys_paddr_to_vm_page(f0000,f0000,fb301ad8,1,80a36a78,...) at > vm_phys_paddr_to_vm_page+0x4d > dev_pager_getpages(92b8d980,fb301c04,1,0,fb301bcc,...) at > dev_pager_getpages+0xe1 > vm_fault(89267bfc,33d90000,1,0,89b0b50c,...) at vm_fault+0x1020 > trap_pfault(202,7,8583b900,80cd9800,89b0eb00,...) at trap_pfault+0x15b > trap(fb301d38) at trap+0x247 > Similar panic here. I believe, the panic introduced in SVN revision 196838. For us, the panic is caused by the `dmidecode' program. The dmidecode program mmap /dev/mem at offset 0xf0000 and reads on...