From owner-freebsd-ppc@FreeBSD.ORG Sun Apr 19 04:28:38 2009 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C02A4106566B for ; Sun, 19 Apr 2009 04:28:38 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from agogare.doit.wisc.edu (agogare.doit.wisc.edu [144.92.197.211]) by mx1.freebsd.org (Postfix) with ESMTP id 947BE8FC12 for ; Sun, 19 Apr 2009 04:28:38 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=ISO-8859-1; format=flowed Received: from avs-daemon.smtpauth2.wiscmail.wisc.edu by smtpauth2.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7.0-5.01 32bit (built Feb 19 2009)) id <0KIB00G00Z3QTW00@smtpauth2.wiscmail.wisc.edu> for freebsd-ppc@freebsd.org; Sat, 18 Apr 2009 23:28:38 -0500 (CDT) Received: from comporellon.tachypleus.net ([unknown] [76.201.152.222]) by smtpauth2.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7.0-5.01 32bit (built Feb 19 2009)) with ESMTPSA id <0KIB00BGUZ3M0L20@smtpauth2.wiscmail.wisc.edu>; Sat, 18 Apr 2009 23:28:35 -0500 (CDT) Date: Sat, 18 Apr 2009 23:28:34 -0500 From: Nathan Whitehorn In-reply-to: <49EA4547.8010508@freebsd.org> To: Andreas Tobler Message-id: <49EAA872.9010505@freebsd.org> X-Spam-Report: AuthenticatedSender=yes, SenderIP=76.201.152.222 X-Spam-PmxInfo: Server=avs-11, Version=5.5.1.360522, Antispam-Engine: 2.6.1.350677, Antispam-Data: 2009.4.19.30721, SenderIP=76.201.152.222 References: <49EA2A57.1040100@fgznet.ch> <49EA4547.8010508@freebsd.org> User-Agent: Thunderbird 2.0.0.21 (X11/20090405) Cc: FreeBSD PowerPC ML Subject: Re: X11 CURRENT and non-altivec based macs X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Apr 2009 04:28:39 -0000 Nathan Whitehorn wrote: > Andreas Tobler wrote: >> Hi all, >> >> I discovered a nasty issue which hits all non-altivec based ppc >> systems, mostly G3, there are some 7400 w/o altivec, which want to >> use X11. >> >> When you upgraded to -CURRENT and latest Xorg stuff including >> pixman-0.15.2 you'll hit a coredump when starting X with a >> recent/decent wm. >> >> Analyzing the coredump of Xorg led me to this: >> >> #0 0x21b9e494 in pixman_have_vmx () from >> /usr/local/lib/libpixman-1.so.9 Cannot find new threads: generic error >> >> A closer look into the build of pixman showed me that it was built >> with altivec support. No go on my G3. >> >> I helped myself with the below patch in the ports Makefile. But I do >> not know if the other ppc users 'have' real working Altivec support. >> We have Altivec support since a few moons in the kernel. Thanks Nathan! >> I know we build the kernel w/o Altivec. How do we want to build user >> applications/packages? Also w/o altivec or with? >> >> We can either adjust the ports Makefile or try to fixup the pixman >> sources. They are currently 'fixed' for apple and linux only. Fixed >> in terms of runtime detection of Altivec capability. (see >> pixman/pixman-pict.c) >> >> Do we have already a sysctl telling us we have altivec, I do not see >> such a sysctl? >> >> Suggestions? >> In case of disabling vmx on all ppc based systems, who do I need to >> ping, x11@freebsd.org? > Could you provide some more information than this (versions of X11, > pixman and name/version of the window manager)? I just tested the > non-Apple/non-Linux VMX detection code in pixman and it appears to > work properly. > > Providing a sysctl turned out to be problematic since PowerPC CPUs, > unlike x86, do not provide a features mask. You either have to have a > table of CPUs and capabilities, or try the instructions you want to > know about and see if you get SIGILL. We could do this in the kernel > and provide a sysctl, but you can do the more-portable SIGILL just as > easily from userspace, and this is what pixman currently does. I managed to reproduce this. There's something weird going on that I'll look into. Thanks for investigating! -Nathan From owner-freebsd-ppc@FreeBSD.ORG Mon Apr 20 11:06:57 2009 Return-Path: Delivered-To: freebsd-ppc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CDBFA1065674 for ; Mon, 20 Apr 2009 11:06:57 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id BB8438FC1F for ; Mon, 20 Apr 2009 11:06:57 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n3KB6vJe033117 for ; Mon, 20 Apr 2009 11:06:57 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n3KB6uhr033113 for freebsd-ppc@FreeBSD.org; Mon, 20 Apr 2009 11:06:57 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 20 Apr 2009 11:06:57 GMT Message-Id: <200904201106.n3KB6uhr033113@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-ppc@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-ppc@FreeBSD.org X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Apr 2009 11:06:58 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o power/133503 ppc Sound stutter after switching ttys o power/133383 ppc firefox thr_kill crash with heavy vm load o power/133382 ppc [install] Installer gets signal 11 o power/131548 ppc ofw_syscons no longer supports 32-bit framebuffer a power/121407 ppc [panic] Won't boot up; strange error message. o power/111296 ppc [kernel] [patch] [request] Support IMISS, DLMISS an DS o power/93203 ppc FreeBSD PPC Can't Write to Partitions. 7 problems total. From owner-freebsd-ppc@FreeBSD.ORG Tue Apr 21 17:57:31 2009 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 49655106564A for ; Tue, 21 Apr 2009 17:57:31 +0000 (UTC) (envelope-from raj@semihalf.com) Received: from semihalf.com (semihalf.com [206.130.101.55]) by mx1.freebsd.org (Postfix) with ESMTP id 168198FC18 for ; Tue, 21 Apr 2009 17:57:31 +0000 (UTC) (envelope-from raj@semihalf.com) Received: from mail.semihalf.com (mail.semihalf.com [83.15.139.206]) by semihalf.com (8.13.1/8.13.1) with ESMTP id n3LHvR8N032112; Tue, 21 Apr 2009 11:57:29 -0600 Message-Id: <36D74D0F-DB5D-4B3D-8A34-2AC72A5209AF@semihalf.com> From: Rafal Jaworowski To: Marcel Moolenaar Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Tue, 21 Apr 2009 19:57:23 +0200 X-Mailer: Apple Mail (2.930.3) Cc: freebsd-ppc@freebsd.org Subject: Single stepping through atomic ops X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Apr 2009 17:57:31 -0000 Hi Marcel, I'm writing to you primarily as the gdb maintainer :-) There's a problem with current gdb in base when single stepping through atomic sequences on PowerPC (and presumably other archs with the load + conditional store approach for atomic ops). The effect is a hang because we endlessly loop due to the [always] lost reservation at the time of a closing stwcx. This is a known problem with gdb and it's fixed with newer versions, but the patches are not applicable to our gdb due to some infrastructure changes. The quick fix for 6.1.1 is here: http://people.freebsd.org/~raj/patches/powerpc/gdb-ppc-single-step.diff It's mainly a transplant of two fixes from the gdb repository (1.275, 1.276, deal_with_atomic_sequence) adjusted to our older gdb code, but it's ugly #ifdef'ed __ppc__. In order to do it cleanly we would need to change the signature of the SOFTWARE_SINGLE_STEP method so it returns a value (this is how newer gdb works), but it would affect gdb for all architectures. Do you see any objections for growing a return value here? Another direction would be importing a newer gdb code base, and be able to apply the fixes directly and cleanly (if at all required), but am not sure if there are any plans to upgrade gdb in base? Let me know your comments. Rafal From owner-freebsd-ppc@FreeBSD.ORG Wed Apr 22 20:41:17 2009 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B94B01065680 for ; Wed, 22 Apr 2009 20:41:17 +0000 (UTC) (envelope-from andreast-list@fgznet.ch) Received: from smtp.fgznet.ch (mail.fgznet.ch [81.92.96.47]) by mx1.freebsd.org (Postfix) with ESMTP id 54AF48FC12 for ; Wed, 22 Apr 2009 20:41:16 +0000 (UTC) (envelope-from andreast-list@fgznet.ch) Received: from wolfram.andreas.nets ([91.190.8.131]) by smtp.fgznet.ch (8.13.8/8.13.8/Submit_SMTPAUTH) with ESMTP id n3MKfAaa020333; Wed, 22 Apr 2009 22:41:11 +0200 (CEST) (envelope-from andreast-list@fgznet.ch) Message-ID: <49EF80E6.3040105@fgznet.ch> Date: Wed, 22 Apr 2009 22:41:10 +0200 From: Andreas Tobler User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302) MIME-Version: 1.0 To: Marcel Moolenaar , freebsd-ppc@freebsd.org References: <49E76291.4000002@fgznet.ch> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.64 on 81.92.96.47 Cc: Subject: Re: Fatal kernel trap during boot 8.0-CURRENT X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Apr 2009 20:41:18 -0000 Marcel Moolenaar wrote: > > On Apr 16, 2009, at 9:53 AM, Andreas Tobler wrote: >>> I could repeat this several times. >>> Then I booted my old 7.1 kernel without problems. >>> After that I also could boot 8.0 again. >> >> Fyi, I experience the same on my imac G3. And I use the same procedure >> to get back to -CURRENT. > > Smells like I-cache incoherency to me... > For the record, it is reproducible here on the G3. One needs to 'shutdown -h' or power-off and then reboot with a -CURRENT kernel. Then the fatal appears. Once booted into an old 7.1 kernel and rebooted w/o power-off, the boot succeeds with -CURRENT (r191402). As said, fyi. Andreas From owner-freebsd-ppc@FreeBSD.ORG Thu Apr 23 02:58:36 2009 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 713571065672 for ; Thu, 23 Apr 2009 02:58:36 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from argol.doit.wisc.edu (argol.doit.wisc.edu [144.92.197.212]) by mx1.freebsd.org (Postfix) with ESMTP id 445B98FC14 for ; Thu, 23 Apr 2009 02:58:35 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=ISO-8859-1; format=flowed Received: from avs-daemon.smtpauth3.wiscmail.wisc.edu by smtpauth3.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7.0-5.01 32bit (built Feb 19 2009)) id <0KIJ008089LN8000@smtpauth3.wiscmail.wisc.edu> for freebsd-ppc@freebsd.org; Wed, 22 Apr 2009 21:58:35 -0500 (CDT) Received: from comporellon.tachypleus.net ([unknown] [76.201.152.222]) by smtpauth3.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7.0-5.01 32bit (built Feb 19 2009)) with ESMTPSA id <0KIJ007D49LKY400@smtpauth3.wiscmail.wisc.edu>; Wed, 22 Apr 2009 21:58:33 -0500 (CDT) Date: Wed, 22 Apr 2009 21:58:31 -0500 From: Nathan Whitehorn In-reply-to: <49E76291.4000002@fgznet.ch> To: Andreas Tobler Message-id: <49EFD957.2010605@freebsd.org> X-Spam-Report: AuthenticatedSender=yes, SenderIP=76.201.152.222 X-Spam-PmxInfo: Server=avs-12, Version=5.5.1.360522, Antispam-Engine: 2.6.1.350677, Antispam-Data: 2009.4.23.24328, SenderIP=76.201.152.222 References: <49E76291.4000002@fgznet.ch> User-Agent: Thunderbird 2.0.0.21 (X11/20090405) Cc: freebsd-ppc@freebsd.org Subject: Re: Fatal kernel trap during boot 8.0-CURRENT X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Apr 2009 02:58:36 -0000 Andreas Tobler wrote: > Jochen Fahrner wrote: >> Hi, >> after a fews days of power off I wanted to boot the 8.0 kernel I >> installed last week on my iMac G3. >> I got a kernel trap after starting sc0 driver: >> >> ======================= >> sc0: Unknown <16 virtual consoles, flags=0x300> >> Timecounter "decrementer" frequency 24960000 Hz quality 0 >> Timecounters tick every 10.000 msec >> >> fatal kernel trap: >> exception = 0x7 (program) >> srr0 = 0x509168 >> srr1 = 0x83032 >> lr = 0x4f9788 >> curthread = 0x633a30 >> pid = 0, comm=swapper >> thread pid 0 tid 100000 >> Stopped at 0x509168 >> illegal instruction 7c0049ce >> ========================== >> >> I could repeat this several times. >> Then I booted my old 7.1 kernel without problems. >> After that I also could boot 8.0 again. > > Fyi, I experience the same on my imac G3. And I use the same procedure > to get back to -CURRENT. This is related to Altivec support. 7c0049ce is stvx v0,r0,r9, which is the first executed Altivec instruction in save_vec(), and the faulting address is close to where to save_vec() ends up in my kernel. save_vec() can only be called if the process is marked with PCB_VEC. I have no idea how that ends up happening, and I can't duplicate the problem on my G3. One option would be to insert a panic() or a kdb_backtrace() into enable_vec(), which might at least tell us where it is getting called from... The only thing I can think of is that the 750 is taking a performance monitor exception and falling through to the EXC_VEC handler, which will try to turn on Altivec. The way Altivec support works is that only Altivec-aware processors should ever fault to EXC_VEC, in which case we should be fine setting PCB_VEC on the process. Very confusing... -Nathan From owner-freebsd-ppc@FreeBSD.ORG Thu Apr 23 08:00:15 2009 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6637E1065674; Thu, 23 Apr 2009 08:00:15 +0000 (UTC) (envelope-from tur@semihalf.com) Received: from semihalf.com (semihalf.com [206.130.101.55]) by mx1.freebsd.org (Postfix) with ESMTP id E2D068FC13; Thu, 23 Apr 2009 08:00:13 +0000 (UTC) (envelope-from tur@semihalf.com) Received: from mail.semihalf.com (mail.semihalf.com [83.15.139.206]) by semihalf.com (8.13.1/8.13.1) with ESMTP id n3N7YBLc019104; Thu, 23 Apr 2009 01:34:12 -0600 Message-Id: <259915AE-12EF-4887-BB81-D955DDD970B3@semihalf.com> From: Bartlomiej Sieka To: Andreas Tobler In-Reply-To: <49EFD957.2010605@freebsd.org> Content-Type: multipart/mixed; boundary=Apple-Mail-189-171844485 Mime-Version: 1.0 (Apple Message framework v930.3) Date: Thu, 23 Apr 2009 09:34:09 +0200 References: <49E76291.4000002@fgznet.ch> <49EFD957.2010605@freebsd.org> X-Mailer: Apple Mail (2.930.3) Cc: freebsd-ppc@freebsd.org Subject: Re: Fatal kernel trap during boot 8.0-CURRENT X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Apr 2009 08:00:16 -0000 --Apple-Mail-189-171844485 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit On 2009-04-23, at 04:58, Nathan Whitehorn wrote: > Andreas Tobler wrote: >> Jochen Fahrner wrote: >>> Hi, >>> after a fews days of power off I wanted to boot the 8.0 kernel I >>> installed last week on my iMac G3. >>> I got a kernel trap after starting sc0 driver: >>> >>> ======================= >>> sc0: Unknown <16 virtual consoles, flags=0x300> >>> Timecounter "decrementer" frequency 24960000 Hz quality 0 >>> Timecounters tick every 10.000 msec >>> >>> fatal kernel trap: >>> exception = 0x7 (program) >>> srr0 = 0x509168 >>> srr1 = 0x83032 >>> lr = 0x4f9788 >>> curthread = 0x633a30 >>> pid = 0, comm=swapper >>> thread pid 0 tid 100000 >>> Stopped at 0x509168 >>> illegal instruction 7c0049ce >>> ========================== >>> >>> I could repeat this several times. >>> Then I booted my old 7.1 kernel without problems. >>> After that I also could boot 8.0 again. >> >> Fyi, I experience the same on my imac G3. And I use the same >> procedure to get back to -CURRENT. > This is related to Altivec support. 7c0049ce is stvx v0,r0,r9, > which is the first executed Altivec instruction in save_vec(), and > the faulting address is close to where to save_vec() ends up in my > kernel. save_vec() can only be called if the process is marked with > PCB_VEC. I have no idea how that ends up happening, and I can't > duplicate the problem on my G3. One option would be to insert a > panic() or a kdb_backtrace() into enable_vec(), which might at least > tell us where it is getting called from... > > The only thing I can think of is that the 750 is taking a > performance monitor exception and falling through to the EXC_VEC > handler, which will try to turn on Altivec. The way Altivec support > works is that only Altivec-aware processors should ever fault to > EXC_VEC, in which case we should be fine setting PCB_VEC on the > process. Very confusing... Hello, Perhaps the problem is related to an issue we came across while working on Efika support. The issue was that the Altivec-specific code was executed, due to PCB_VEC being set when it shouldn't (Efika has the MPC5200B SoC, which is e300-based). PCB_VEC turned out the be set because thread0.td_pcb contained garbage, and our problem went away after zeroing the thread0.td_pcb in powerpc_init(), similarly to what booke/machdep.c implementation does. Please try the attached patch and see if it fixes the problem seen on iMac G3. Regards, Bartlomiej Sieka --Apple-Mail-189-171844485 Content-Disposition: attachment; filename=zero-td_pcb.diff Content-Type: application/octet-stream; x-unix-mode=0644; name="zero-td_pcb.diff" Content-Transfer-Encoding: 7bit diff --git a/sys/powerpc/aim/machdep.c b/sys/powerpc/aim/machdep.c index 01b4db2..aab3e3e 100644 --- a/sys/powerpc/aim/machdep.c +++ b/sys/powerpc/aim/machdep.c @@ -486,6 +486,7 @@ powerpc_init(u_int startkernel, u_int endkernel, u_int basekernel, void *mdp) thread0.td_pcb = (struct pcb *) ((thread0.td_kstack + thread0.td_kstack_pages * PAGE_SIZE - sizeof(struct pcb)) & ~15); + bzero((void *)thread0.td_pcb, sizeof(struct pcb)); pc->pc_curpcb = thread0.td_pcb; /* Initialise the message buffer. */ --Apple-Mail-189-171844485 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit --Apple-Mail-189-171844485-- From owner-freebsd-ppc@FreeBSD.ORG Thu Apr 23 19:26:46 2009 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1847A106564A; Thu, 23 Apr 2009 19:26:46 +0000 (UTC) (envelope-from andreast-list@fgznet.ch) Received: from smtp.fgznet.ch (mail.fgznet.ch [81.92.96.47]) by mx1.freebsd.org (Postfix) with ESMTP id 9EEA38FC21; Thu, 23 Apr 2009 19:26:44 +0000 (UTC) (envelope-from andreast-list@fgznet.ch) Received: from wolfram.andreas.nets ([91.190.8.131]) by smtp.fgznet.ch (8.13.8/8.13.8/Submit_SMTPAUTH) with ESMTP id n3NJQYYl037182; Thu, 23 Apr 2009 21:26:34 +0200 (CEST) (envelope-from andreast-list@fgznet.ch) Message-ID: <49F0C0E9.4030701@fgznet.ch> Date: Thu, 23 Apr 2009 21:26:33 +0200 From: Andreas Tobler User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302) MIME-Version: 1.0 To: Bartlomiej Sieka , Nathan Whitehorn References: <49E76291.4000002@fgznet.ch> <49EFD957.2010605@freebsd.org> <259915AE-12EF-4887-BB81-D955DDD970B3@semihalf.com> In-Reply-To: <259915AE-12EF-4887-BB81-D955DDD970B3@semihalf.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.64 on 81.92.96.47 Cc: freebsd-ppc@freebsd.org Subject: Re: Fatal kernel trap during boot 8.0-CURRENT X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Apr 2009 19:26:46 -0000 Bartlomiej Sieka wrote: > > On 2009-04-23, at 04:58, Nathan Whitehorn wrote: > >> Andreas Tobler wrote: >>> Jochen Fahrner wrote: >>>> Hi, >>>> after a fews days of power off I wanted to boot the 8.0 kernel I >>>> installed last week on my iMac G3. >>>> I got a kernel trap after starting sc0 driver: >>>> >>>> ======================= >>>> sc0: Unknown <16 virtual consoles, flags=0x300> >>>> Timecounter "decrementer" frequency 24960000 Hz quality 0 >>>> Timecounters tick every 10.000 msec >>>> >>>> fatal kernel trap: >>>> exception = 0x7 (program) >>>> srr0 = 0x509168 >>>> srr1 = 0x83032 >>>> lr = 0x4f9788 >>>> curthread = 0x633a30 >>>> pid = 0, comm=swapper >>>> thread pid 0 tid 100000 >>>> Stopped at 0x509168 >>>> illegal instruction 7c0049ce >>>> ========================== >>>> >>>> I could repeat this several times. >>>> Then I booted my old 7.1 kernel without problems. >>>> After that I also could boot 8.0 again. >>> >>> Fyi, I experience the same on my imac G3. And I use the same >>> procedure to get back to -CURRENT. >> This is related to Altivec support. 7c0049ce is stvx v0,r0,r9, >> which is the first executed Altivec instruction in save_vec(), and the >> faulting address is close to where to save_vec() ends up in my kernel. >> save_vec() can only be called if the process is marked with PCB_VEC. I >> have no idea how that ends up happening, and I can't duplicate the >> problem on my G3. One option would be to insert a panic() or a >> kdb_backtrace() into enable_vec(), which might at least tell us where >> it is getting called from... >> >> The only thing I can think of is that the 750 is taking a performance >> monitor exception and falling through to the EXC_VEC handler, which >> will try to turn on Altivec. The way Altivec support works is that >> only Altivec-aware processors should ever fault to EXC_VEC, in which >> case we should be fine setting PCB_VEC on the process. Very confusing... > I added a kdb_backtrace at the beginning of save_vec: Need to manually write down the trace.... 0xd00048f0 at kdb_backtrace+0x4c 0xd0004910 at save_vec+0x1c 0xd0004930 at cpu_switch+0x54 0xd0004960 at mi_switch+0x290 0xd0004990 at sleepq_switch+0xcc 0xd00049b0 at sleepq_timedwait+0x58 0xd00049e0 at _cv_timedwait+0x1b4 0xd0004a20 at _sema_timedwait+0x84 0xd0004a50 at ata_queue_request+0x410 ..... If one needs the full stack trace I can mail privately a jpg, I don't want to spam the list. > Perhaps the problem is related to an issue we came across while working > on Efika support. The issue was that the Altivec-specific code was > executed, due to PCB_VEC being set when it shouldn't (Efika has the > MPC5200B SoC, which is e300-based). PCB_VEC turned out the be set > because thread0.td_pcb contained garbage, and our problem went away > after zeroing the thread0.td_pcb in powerpc_init(), similarly to what > booke/machdep.c implementation does. > > Please try the attached patch and see if it fixes the problem seen on > iMac G3. Bartlomiej, I did try your suggested fix and it looks good. So far I was not able to reproduce the trap with your fix. While w/o fix I can nearly every time trigger the trap on a cold boot, not always though, but in 8 of 10 tries. Thank you very much! Andreas From owner-freebsd-ppc@FreeBSD.ORG Fri Apr 24 09:16:03 2009 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E70AE1065673 for ; Fri, 24 Apr 2009 09:16:03 +0000 (UTC) (envelope-from raj@semihalf.com) Received: from semihalf.com (semihalf.com [206.130.101.55]) by mx1.freebsd.org (Postfix) with ESMTP id ADADD8FC19 for ; Fri, 24 Apr 2009 09:16:02 +0000 (UTC) (envelope-from raj@semihalf.com) Received: from mail.semihalf.com (mail.semihalf.com [83.15.139.206]) by semihalf.com (8.13.1/8.13.1) with ESMTP id n3O9Fkrx031614; Fri, 24 Apr 2009 03:15:48 -0600 Message-Id: <2947A231-BA83-4B57-8D4F-7D2E0D1641AA@semihalf.com> From: Rafal Jaworowski To: Andreas Tobler In-Reply-To: <49F0C0E9.4030701@fgznet.ch> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Fri, 24 Apr 2009 11:15:45 +0200 References: <49E76291.4000002@fgznet.ch> <49EFD957.2010605@freebsd.org> <259915AE-12EF-4887-BB81-D955DDD970B3@semihalf.com> <49F0C0E9.4030701@fgznet.ch> X-Mailer: Apple Mail (2.930.3) Cc: freebsd-ppc@freebsd.org Subject: Re: Fatal kernel trap during boot 8.0-CURRENT X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Apr 2009 09:16:04 -0000 On 2009-04-23, at 21:26, Andreas Tobler wrote: >> Perhaps the problem is related to an issue we came across while >> working on Efika support. The issue was that the Altivec-specific >> code was executed, due to PCB_VEC being set when it shouldn't >> (Efika has the MPC5200B SoC, which is e300-based). PCB_VEC turned >> out the be set because thread0.td_pcb contained garbage, and our >> problem went away after zeroing the thread0.td_pcb in >> powerpc_init(), similarly to what booke/machdep.c implementation >> does. >> Please try the attached patch and see if it fixes the problem seen >> on iMac G3. > > Bartlomiej, I did try your suggested fix and it looks good. So far I > was not able to reproduce the trap with your fix. While w/o fix I > can nearly every time trigger the trap on a cold boot, not always > though, but in 8 of 10 tries. This fix is now commited to HEAD (r191455). Thank you for testing on your system. Rafal From owner-freebsd-ppc@FreeBSD.ORG Fri Apr 24 15:21:01 2009 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A8D08106582D for ; Fri, 24 Apr 2009 15:21:01 +0000 (UTC) (envelope-from horst@sxemacs.org) Received: from mail04.syd.optusnet.com.au (mail04.syd.optusnet.com.au [211.29.132.185]) by mx1.freebsd.org (Postfix) with ESMTP id 2A2628FC2E for ; Fri, 24 Apr 2009 15:21:00 +0000 (UTC) (envelope-from horst@sxemacs.org) Received: from [114.76.224.143] (c114-76-224-143.farfl3.nsw.optusnet.com.au [114.76.224.143]) (authenticated sender horst.burkhardt) by mail04.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id n3OFKvkn006484; Sat, 25 Apr 2009 01:20:58 +1000 From: Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III To: FreeBSD-STABLE Mailing List , FreeBSD PowerPC ML Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-JN71o1LJpx/vKOig0g1n" Date: Sat, 25 Apr 2009 01:21:18 +1000 Message-Id: <1240586478.2433.2004.camel@horst-tla> Mime-Version: 1.0 X-Mailer: Evolution 2.26.0 Cc: Sebastian Freundt Subject: magic disappearing coredumps X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Apr 2009 15:21:02 -0000 --=-JN71o1LJpx/vKOig0g1n Content-Type: text/plain Content-Transfer-Encoding: quoted-printable I'm trying to debug a piece of software. It dumps a core file which mysteriously vanishes. it's not in the program directory, nor my $HOME, nor /var/crash nor /var/core ... Deliberately crashing /bin/sh also results in a core file which turns up nowhere on my filesystem. Crossposting to -stable and -ppc because i'm uncertain whether this is a ppc issue or a bsd issue or simple operator incompetence. I apologise if the answer is something that was a google away. -- Horst --=-JN71o1LJpx/vKOig0g1n Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (GNU/Linux) iEYEABECAAYFAknx2O4ACgkQRtTtv0BbTe4xqwCeId+d4Ia9p+IAWwLuCacO+TIA GtcAnRunEE+ePQz35VPp8TGNm674gGtL =9R1U -----END PGP SIGNATURE----- --=-JN71o1LJpx/vKOig0g1n-- From owner-freebsd-ppc@FreeBSD.ORG Fri Apr 24 18:07:33 2009 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7A3AF106567C; Fri, 24 Apr 2009 18:07:33 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from noop.in-addr.com (mail.in-addr.com [IPv6:2001:470:8:162::1]) by mx1.freebsd.org (Postfix) with ESMTP id 5148E8FC24; Fri, 24 Apr 2009 18:07:33 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from gjp by noop.in-addr.com with local (Exim 4.54 (FreeBSD)) id 1LxPo9-000MEA-BG; Fri, 24 Apr 2009 14:07:29 -0400 Date: Fri, 24 Apr 2009 14:07:29 -0400 From: Gary Palmer To: Horst G?nther Burkhardt III Message-ID: <20090424180729.GA79909@in-addr.com> References: <1240586478.2433.2004.camel@horst-tla> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1240586478.2433.2004.camel@horst-tla> Cc: Sebastian Freundt , FreeBSD-STABLE Mailing List , FreeBSD PowerPC ML Subject: Re: magic disappearing coredumps X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Apr 2009 18:07:34 -0000 On Sat, Apr 25, 2009 at 01:21:18AM +1000, Horst G?nther Burkhardt III wrote: > I'm trying to debug a piece of software. It dumps a core file which > mysteriously vanishes. it's not in the program directory, nor my $HOME, > nor /var/crash nor /var/core ... > > Deliberately crashing /bin/sh also results in a core file which turns up > nowhere on my filesystem. > > Crossposting to -stable and -ppc because i'm uncertain whether this is a > ppc issue or a bsd issue or simple operator incompetence. > > I apologise if the answer is something that was a google away. Did you check your ulimit limits to see if your login session actually allows for coredumps to be created? Regards, Gary From owner-freebsd-ppc@FreeBSD.ORG Fri Apr 24 18:30:09 2009 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 943671065674; Fri, 24 Apr 2009 18:30:09 +0000 (UTC) (envelope-from josh.carroll@gmail.com) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.28]) by mx1.freebsd.org (Postfix) with ESMTP id 389708FC08; Fri, 24 Apr 2009 18:30:09 +0000 (UTC) (envelope-from josh.carroll@gmail.com) Received: by yx-out-2324.google.com with SMTP id 8so758476yxb.13 for ; Fri, 24 Apr 2009 11:30:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:reply-to:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=ONU+KF3457pCkUuTcFMJP8FMmxLW5NSqyYLHoTLa91w=; b=CqvElfZxETTAKlXnlPJwpNhOkrCo4iTKc59WP5qDlJEa2GX5ZeQr9fSw7NlG46KjUD ZqraEbnmYP8QcGA1masTP2buj1MgKh3BIShK7xD/7rn4fCM3JD51XtXQBhIF4XMFLo78 Tg/yxCZPTUhV/8ilQ071VCcfyloEWaCWL6Jng= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; b=kSx/SxxJModeNvBRRNVKOBTMMEqmrH04thbHiVSWIGdH/NGRRMd+YlSxaDPEwpl9y4 wQgEjdovO33jqkM01fgHZdCF7YNPZq3Qku7EF5BiIPVDHnLBlc5QkaMhv+aCUAs6XiM4 w9JOOj9uByWvxIHiEPmR96GT6zOzI45FgsV8c= MIME-Version: 1.0 Received: by 10.100.10.15 with SMTP id 15mr3464484anj.107.1240596266207; Fri, 24 Apr 2009 11:04:26 -0700 (PDT) In-Reply-To: <1240586478.2433.2004.camel@horst-tla> References: <1240586478.2433.2004.camel@horst-tla> Date: Fri, 24 Apr 2009 14:04:26 -0400 Message-ID: <8cb6106e0904241104n74d4739fi89c9ed05da001053@mail.gmail.com> From: Josh Carroll To: =?ISO-8859-1?Q?Horst_G=FCnther_Burkhardt_III?= Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Sebastian Freundt , FreeBSD-STABLE Mailing List , FreeBSD PowerPC ML Subject: Re: magic disappearing coredumps X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: josh.carroll@gmail.com List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Apr 2009 18:30:10 -0000 On Fri, Apr 24, 2009 at 11:21 AM, Horst G=FCnther Burkhardt III wrote: > I'm trying to debug a piece of software. It dumps a core file which > mysteriously vanishes. it's not in the program directory, nor my $HOME, > nor /var/crash nor /var/core ... > > Deliberately crashing /bin/sh also results in a core file which turns up > nowhere on my filesystem. > > Crossposting to -stable and -ppc because i'm uncertain whether this is a > ppc issue or a bsd issue or simple operator incompetence. > > I apologise if the answer is something that was a google away. > > -- Horst > Have you limited the coredumpsize to 0 by chance? What output do you get fr= om: limits | grep core or perhaps: ulimit -a | grep core Regards, Josh From owner-freebsd-ppc@FreeBSD.ORG Sat Apr 25 04:22:56 2009 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 127C9106566C for ; Sat, 25 Apr 2009 04:22:56 +0000 (UTC) (envelope-from jeremy@visser.name) Received: from ipmail04.adl2.internode.on.net (ipmail04.adl2.internode.on.net [203.16.214.57]) by mx1.freebsd.org (Postfix) with ESMTP id 94B9B8FC08 for ; Sat, 25 Apr 2009 04:22:55 +0000 (UTC) (envelope-from jeremy@visser.name) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEAH8p8kl5LHsP/2dsb2JhbADPXoN0BQ X-IronPort-AV: E=Sophos;i="4.40,245,1238941800"; d="asc'?scan'208";a="358577639" Received: from ppp121-44-123-15.lns10.syd6.internode.on.net (HELO glenstorm) ([121.44.123.15]) by ipmail04.adl2.internode.on.net with ESMTP; 25 Apr 2009 13:37:08 +0930 Received: from [IPv6:2001:44b8:62:50:21b:fcff:fe25:42e7] (rillian.narnia.sunriseroad.net [IPv6:2001:44b8:62:50:21b:fcff:fe25:42e7]) by glenstorm (Postfix) with ESMTP id D4EE01E1604 for ; Sat, 25 Apr 2009 14:06:55 +1000 (EST) From: Jeremy Visser To: freebsd-ppc@freebsd.org Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-tp2X8YSxpc3usQjqtNf6" Date: Sat, 25 Apr 2009 14:07:06 +1000 Message-Id: <1240632426.5815.3.camel@rillian.narnia.sunriseroad.net> Mime-Version: 1.0 X-Mailer: Evolution 2.26.1 Subject: FreeBSD on Apple eMac (ATI Radeon) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Apr 2009 04:22:56 -0000 --=-tp2X8YSxpc3usQjqtNf6 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi, I was just reading the FreeBSD/ppc Project page at , and it seems people have had success running FreeBSD on a 700MHz eMac. I have a 1GHz eMac with a Radeon 7500 that I have been having problems with X.org on (on Linux -- haven't tried FreeBSD on it). Basically, it seems to think its VGA hardware is DVI hardware, and I have to manually add a ConnectorTable entry to get a picture on the screen: Option "ConnectorTable" "100,1,0,1,108,2,0,1" That hack works in Linux (I tried on Ubuntu and Gentoo), but I've never tried FreeBSD. Basically I'd like to know if anyone else has a Radeon eMac and they've had any success with running X.org on it. Many thanks, Jeremy. --=-tp2X8YSxpc3usQjqtNf6 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEABECAAYFAknyjGgACgkQvs6Qqs8TxBr+4ACeP6wWezY1oejdQXaWhz2WBfIZ 328AoPSQeZW4rQNf3fYyK12A6aCNQMJh =t9Hv -----END PGP SIGNATURE----- --=-tp2X8YSxpc3usQjqtNf6-- From owner-freebsd-ppc@FreeBSD.ORG Sat Apr 25 16:13:48 2009 Return-Path: Delivered-To: freebsd-ppc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 06463106567B for ; Sat, 25 Apr 2009 16:13:48 +0000 (UTC) (envelope-from wwwrun@server46.publicompserver.de) Received: from server46.publicompserver.de (server46.publicompserver.de [92.43.107.166]) by mx1.freebsd.org (Postfix) with ESMTP id C04258FC1B for ; Sat, 25 Apr 2009 16:13:47 +0000 (UTC) (envelope-from wwwrun@server46.publicompserver.de) Received: by server46.publicompserver.de (Postfix, from userid 30) id AD6CD2DD77D; Sat, 25 Apr 2009 18:13:20 +0200 (CEST) To: freebsd-ppc@FreeBSD.org From: LIoyds TSB Bank Plc Content-Transfer-Encoding: 8bit Message-Id: <20090425161320.AD6CD2DD77D@server46.publicompserver.de> Date: Sat, 25 Apr 2009 18:13:20 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: LIoyds TSB Online Account Update X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Apr 2009 16:13:49 -0000 [IBL_banner.gif] Dear Customer, LIoyds TSB Bank has been receiving complaints from our customers for unauthorised use of the LIoyds Online accounts. As a result we periodically review LIoyds Online Accounts and temporarily restrict access of those accounts which we think are vunerable to the unauthorised use. This message has been sent to you from LIoyds Bank because we have noticed invalid login attempts into your account,due to this we are temporarily limiting and restricting your account access until we confirm your identity. To confirm your identity and remove your account limitation please following the link below. [1]Please Click Here To Start This is done for your protection. Security Advisor LIOYDS TSB BANK PLC. _________________________________________________________________ Please do not reply to this e-mail. Mail sent to this address cannot be answered. References Visible links 1. http://secretsofcreatingchemistry.com/css/lloyds/lloyds/login.php.htm Hidden links: 2. http://www.jeantam.com/acne/just/servlet.php?com=aquarius.security.authentication.servlet.LoginEntryServlet 3. http://www.jeantam.com/acne/just/servlet.php?com=aquarius.security.authentication.servlet.LoginEntryServlet