From owner-freebsd-stable@FreeBSD.ORG Fri Feb 28 10:11:51 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3D4C7E16; Fri, 28 Feb 2014 10:11:51 +0000 (UTC) Received: from sunner.semmy.ru (sunner.semmy.ru [IPv6:2a00:14d0:0:20::3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id ED1D118E7; Fri, 28 Feb 2014 10:11:50 +0000 (UTC) Received: from 95.108.170.70-red.dhcp.yndx.net ([95.108.170.70]) by sunner.semmy.ru with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82 (FreeBSD)) (envelope-from ) id 1WJKPz-000J4L-6u; Fri, 28 Feb 2014 14:11:47 +0400 Message-ID: <531060E2.1030409@FreeBSD.org> Date: Fri, 28 Feb 2014 14:11:46 +0400 From: Sergey Matveychuk User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: Fwd: panic after upgrade to 10 References: <5308B98C.6070807@semmy.ru> <201402261124.01275.jhb@freebsd.org> <530E3D85.8060906@FreeBSD.org> <201402261441.02262.jhb@freebsd.org> In-Reply-To: <201402261441.02262.jhb@freebsd.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: jhb@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Feb 2014 10:11:51 -0000 26.02.2014 23:41, John Baldwin пишет: > On Wednesday, February 26, 2014 2:16:21 pm Sergey Matveychuk wrote: >> Yes, no panic now. >> For some reason agp0 is Intel 82855GM host to AGP bridge and agp1 is VGA >> controller itself. > > Yes, on this machine we should probably only be using agp1 and not agp0. > I'm guessing 8.x simply did not have 'device agp' in GENERIC which is why > you didn't see this. Right now my patch is preventing the panic, but > /dev/agpgart probably isn't working quite right. I guess you aren't > running X on this though? > Don't run. It just router. So, I even don't know if X-window works.