From owner-freebsd-current@FreeBSD.ORG Sat Jul 20 11:20:57 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id B1A5460B; Sat, 20 Jul 2013 11:20:57 +0000 (UTC) (envelope-from oliver.pntr@gmail.com) Received: from mail-ob0-x22f.google.com (mail-ob0-x22f.google.com [IPv6:2607:f8b0:4003:c01::22f]) by mx1.freebsd.org (Postfix) with ESMTP id 75C19DC8; Sat, 20 Jul 2013 11:20:57 +0000 (UTC) Received: by mail-ob0-f175.google.com with SMTP id xn12so6496886obc.34 for ; Sat, 20 Jul 2013 04:20:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=YePN99PcJCQogF935GC6MW5bG/eH8QchDUoKk554w+A=; b=U9Qjq6qOkIyiiOAhXwAzFScmOaRFwaHCrQ1jIxv649IixB0iXz1QtLCmCvfxYbZvqx CBSQwH6sreP/FMDmuDhejNMvKgV6IoY6zX9XDT3VGLDzcPyZw756oQCdV6lOT0TFBeNP agqr96XEWg6EPMw2jmkPg3TLlAufE0Rrnw1jflHP99uO/TAX9qwl/TTEL6wt3ofHGjuB 5gUlyQMaK++yr5Fi/Yi1jhOJv6pPeSQZPeRnBnim75E4GsU5p4Zp8urPZks07CX4iKci Z45gDNQyI3bzpVtL+1H8DPo01j8ausN5rD18Y+qe7DfZeLuQBIq5bAdvM5nlU0ZkAAK3 Seog== MIME-Version: 1.0 X-Received: by 10.60.102.41 with SMTP id fl9mr21196335oeb.37.1374319256472; Sat, 20 Jul 2013 04:20:56 -0700 (PDT) Received: by 10.182.227.231 with HTTP; Sat, 20 Jul 2013 04:20:56 -0700 (PDT) In-Reply-To: <51EA5166.4020508@entel.upc.edu> References: <51E6EB0A.2060407@entel.upc.edu> <51EA5166.4020508@entel.upc.edu> Date: Sat, 20 Jul 2013 13:20:56 +0200 Message-ID: Subject: Re: Panic when starting X with Intel KMS From: Oliver Pinter To: =?ISO-8859-1?Q?Gustau_P=E9rez_i_Querol?= Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org, kib@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Jul 2013 11:20:57 -0000 On 7/20/13, Gustau P=E9rez i Querol wrote: > Al 17/07/2013 21:05, En/na Gustau P=E9rez i Querol ha escrit: >> Hi, >> >> I'm having panics or hard freezes when starting X with an Intel >> video card. The machine is able to start old X+twm without problems >> but when I try gnome3 (in normal or fallback mode, doesn't matter) the >> machine panics or hard freezes. >> >> This doesn't happen when running X with vesa. With vesa the gnome >> is able to start in fallback (no composition) mode. Also, an old i386 >> with an nvidia card is able to run that gnome3 with composition so I'd >> say it has to do with the intel card. >> >> These are the specs of the machine: >> >> FreeBSD 10.0-CURRENT #4 r+3dc57aa: Wed Jul 17 15:13:07 CEST 2013 >> root@portgus:/usr/obj/usr/src/sys/CUSTOM amd64 >> FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610 >> RAM: 8GB >> Video Card: Intel chipid=3D0x00468086 >> >> The debugging knobs in the kernel config are there. I can also >> confirm that I can break to the debugger with CTRL+ALT+ESC before >> starting X. The world was build without debug symbols. >> >> Because the machine runs with an Intel card, I had to use my $work >> dockstation to obtain a serial port and do the debug via serial port >> with another machine. >> >> When starting X, either the machine freezes hard (and so no >> CTRL+ALT+ESC) or the machine panics. It has never executed X without >> panics or freezes. >> >> I was able to obtain a core dump, the results are at: >> >> https://dl.dropboxusercontent.com/u/2094962/core.txt.4 >> >> I was unable to dive any further because the dump only shows the >> kernel side of things. The bt only seems to show the kernel side and >> the user side of things seems to be corrupt. >> >> Any other info I can obtain from the machine in the moment of the >> panic, let me know. I can easy do the debug via serial port. >> >> Gus >> > > Reading the backtrace I see this: > > panic: pmap_release: pmap resident count -398580 !=3D 0 > > which comes from amd64/amd64/pmap.c:1936. I suspect that > pmap->pm_stats.resident_count being negative is a bug. > > Can this be caused by a userspace process? If that's possible, any > idea why I get a corrupted stack an thus I'm not able to find the root > of the problem. Added kib@ to CC. > > G. > > > -- > Salut i for=E7a, > > Gustau > > -------------------------------------------------------------------------= -- > Prou top-posting : http://ca.wikipedia.org/wiki/Top-posting > Stop top-posting : http://en.wikipedia.org/wiki/Posting_style=09 > > O O O Gustau P=E9rez i Querol > O O O Unitat de Gesti=F3 dels departaments > O O O Matem=E0tica Aplicada IV i Enginyeria Telem=E0tica > > Universitat Polit=E8cnica de Catalunya > Edifici C3 - Despatx S101-B > UPC Campus Nord UPC > C/ Jordi Girona, 1-3 > 08034 - Barcelona > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= "