From owner-freebsd-stable@FreeBSD.ORG Fri Feb 28 20:36:55 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E97DFBE7; Fri, 28 Feb 2014 20:36:55 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C1473156C; Fri, 28 Feb 2014 20:36:55 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 8CF5BB94E; Fri, 28 Feb 2014 15:36:53 -0500 (EST) From: John Baldwin To: Sergey Matveychuk Subject: Re: Fwd: panic after upgrade to 10 Date: Fri, 28 Feb 2014 14:01:03 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20130906; KDE/4.5.5; amd64; ; ) References: <5308B98C.6070807@semmy.ru> <201402261441.02262.jhb@freebsd.org> <531060E2.1030409@FreeBSD.org> In-Reply-To: <531060E2.1030409@FreeBSD.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <201402281401.03688.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Fri, 28 Feb 2014 15:36:53 -0500 (EST) Cc: freebsd-stable@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 20:36:56 -0000 On Friday, February 28, 2014 5:11:46 am Sergey Matveychuk wrote: > 26.02.2014 23:41, John Baldwin =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > > 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 V= GA > >> 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 w= hy > > 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? > > >=20 > Don't run. It just router. So, I even don't know if X-window works. Yes, that's totally fair. Can you test my second patch and see if it creates a /dev/agpgart that points to /dev/agp0? Can you also see if you are able to use rm and ln to move the link to /dev/agp1? =2D-=20 John Baldwin