From owner-freebsd-ports@FreeBSD.ORG Wed Dec 4 18:02:43 2013 Return-Path: Delivered-To: freebsd-ports@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 E52DB7EF; Wed, 4 Dec 2013 18:02:43 +0000 (UTC) Received: from mail-ea0-x22e.google.com (mail-ea0-x22e.google.com [IPv6:2a00:1450:4013:c01::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 547C4138B; Wed, 4 Dec 2013 18:02:43 +0000 (UTC) Received: by mail-ea0-f174.google.com with SMTP id b10so10686510eae.5 for ; Wed, 04 Dec 2013 10:02:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :mime-version:content-type:content-transfer-encoding; bh=+okTjSLbMVhgu8zJiW1Jh510NBCi87KrrWuCwRmFbjs=; b=tk5B3ggqNv4/ewgamXuk0hhamBsplglET41KHcEEu+ySTj7o6pcw+Pqkpv8Y1wzUQ4 R+JJ56ovdGs02l61NCGd/I2Q9cW86uHy1cuWSygezq9X+RacJV9ND+q7cXNDiC25TprM DyRGGUuxKqtNRVuHLCcwOJbAM0pV3iSiPtinB9HPyOhUV1ux1Yd2ozk0jmyhmU3065xp wuJR2erh+dosuXzMHk0eGm5wUv3MfiqbKLExPdylDkLID6C1sZfMjQuWmBDTGzSDyzLZ aYH1+5+M+bMdwocjyqpbBC4I5zaYOYbCojln8mlW1QrIUiuDhoa9R7wVPHdAKH/OWL6V 6SXw== X-Received: by 10.15.50.68 with SMTP id k44mr2902041eew.85.1386180161786; Wed, 04 Dec 2013 10:02:41 -0800 (PST) Received: from ernst.home (p578E2E5E.dip0.t-ipconnect.de. [87.142.46.94]) by mx.google.com with ESMTPSA id b41sm73564119eef.16.2013.12.04.10.02.40 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Wed, 04 Dec 2013 10:02:40 -0800 (PST) Date: Wed, 4 Dec 2013 19:02:38 +0100 From: Gary Jennejohn To: Cy Schubert Subject: Re: tcl & tk ports on FreeBSD 10 amd64 Message-ID: <20131204190238.7f2884b3@ernst.home> In-Reply-To: <201312040532.rB45Wu6r005147@slippy.cwsent.com> References: <201312040532.rB45Wu6r005147@slippy.cwsent.com> X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.17; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: gljennjohn@gmail.com List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Dec 2013 18:02:44 -0000 On Tue, 03 Dec 2013 21:32:56 -0800 Cy Schubert wrote: > Hi, > > Sorry for cross posting but this concerns both lists. > > Over the last month or so I've been upgrading my prod infrastructure from 9 > to 10. It's mostly complete except for a number of issues. One issue, just > solved today (circumvented is a better word), is exmh crashing 10.0 on > amd64 while on i386 there are no issues with exmh. > > It appears that the tcl and tk ports (all three of them, 8.4, 8.5, and 8.6) > will panic 10.0 on amd64 (but not i386) when the ports are built with > threading support. > > I haven't had a chance to look at the dump yet but I had a hunch to test > the ports without threading support enabled, making the panic go away. If I > don't get to it in time, here is what I haveFatal trap 9: general > protection fault while in kernel mode > cpuid = 2; apic id = 02 > instruction pointer = 0x20:0xffffffff80957aeb > stack pointer = 0x28:0xfffffe00f17f9980 > frame pointer = 0x28:0xfffffe00f17f99a0 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 11 (idle: cpu2) > trap number = 9 > timeout stopping cpus > panic: general protection fault > cpuid = 2 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame > 0xfffffe00f17f9510 > kdb_backtrace() at kdb_backtrace+0x39/frame 0xfffffe00f17f95c0 > panic() at panic+0x153/frame 0xfffffe00f17f9640 > trap_fatal() at trap_fatal+0x3a2/frame 0xfffffe00f17f96a0 > trap() at trap+0x7bf/frame 0xfffffe00f17f98c0 > calltrap() at calltrap+0x8/frame 0xfffffe00f17f98c0 > --- trap 0x9, rip = 0xffffffff80957aeb, rsp = 0xfffffe00f17f9980, rbp = > 0xfffffe > 00f17f99a0 --- > cpu_idle_hlt() at cpu_idle_hlt+0x2b/frame 0xfffffe00f17f99a0 > cpu_idle() at cpu_idle+0x93/frame 0xfffffe00f17f99c0 > sched_idletd() at sched_idletd+0x1ee/frame 0xfffffe00f17f9a70 > fork_exit() at fork_exit+0x9a/frame 0xfffffe00f17f9ab0 > fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe00f17f9ab0 > --- trap 0, rip = 0, rsp = 0xfffffe00f17f9b70, rbp = 0 --- > Uptime: 4m42s > Dumping 522 out of 5932 MB:..4%..13%..22%..31%..43%..53%..62%..71%..83%..92% > so far, > > Tcl/tk are tickling some bug somewhere. > > Before anyone suggests memory, I've been able to reproduce this on an Intel > Core i3 machine with 6 GB and an AMD X2 5000+, also with 6 GB, both in > amd64 mode. Both systems are dual (or multi) boot. The bug does not exhibit > itself in i386 mode. It also doesn't exhibit itself when tcl/tk are built > without thread support. > > The only application I know of which tickles the bug is mail/exmh2 (I'm the > maintainer) when using a threaded tcl/tk. > > My 11-CURRENT partition on my laptop is still i386 so I haven't been able > to reproduce it under 11 with amd64. > I used to use exmh all the time but then I started having problems with it so I switched to claws-mail. Anyway, I just installed exmh2 with threaded tcl/tk on FreeBSD 11.0-CURRENT FreeBSD 11.0-CURRENT #9 r258676: Wed Nov 27 09:57:24 CET 2013 amd64 CPU is a AMD Phenom(tm) II X6 1090T with 8GB of memory. Didn't have any crashes doing some cursory tests - mostly reading some e-mails downloaded with getmail. Didn't try editing or sending any mails. -- Gary Jennejohn