From owner-freebsd-arm@FreeBSD.ORG Sun Sep 7 06:15:27 2014 Return-Path: Delivered-To: freebsd-arm@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 6E014FC8; Sun, 7 Sep 2014 06:15:27 +0000 (UTC) Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "funkthat.com", Issuer "funkthat.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1BCC8179E; Sun, 7 Sep 2014 06:15:26 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id s876F9hF049359 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 6 Sep 2014 23:15:10 -0700 (PDT) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id s876F9nw049358; Sat, 6 Sep 2014 23:15:09 -0700 (PDT) (envelope-from jmg) Date: Sat, 6 Sep 2014 23:15:09 -0700 From: John-Mark Gurney To: Warner Losh Subject: Re: Cubieboard: Spurious interrupt detected Message-ID: <20140907061508.GY82175@funkthat.com> Mail-Followup-To: Warner Losh , Ian Lepore , "freebsd-arm@freebsd.org" , ticso@cicely.de References: <2279481.3MX4OEDuCl@quad> <20140905215702.GL3196@cicely7.cicely.de> <1409958716.1150.321.camel@revolution.hippie.lan> <20140906011526.GT82175@funkthat.com> <1409967197.1150.339.camel@revolution.hippie.lan> <20140906045403.GU82175@funkthat.com> <1410015268.1150.351.camel@revolution.hippie.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Sat, 06 Sep 2014 23:15:10 -0700 (PDT) Cc: "freebsd-arm@freebsd.org" , ticso@cicely.de, Ian Lepore X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Sep 2014 06:15:27 -0000 Warner Losh wrote this message on Sat, Sep 06, 2014 at 14:20 -0600: > > On Sep 6, 2014, at 8:54 AM, Ian Lepore wrote: > > > On Fri, 2014-09-05 at 23:45 -0700, Adrian Chadd wrote: > >> The device itself may have FIFOs and internal busses that also need to > >> be flushed. > >> > > > > The question isn't whether or not it's sufficient, because it's > > necessary. The device driver knows what its hardware requirements are > > and should meet them. It doesn't not know what its parent bus > > requirements are, and that's why it must call bus_space_barrier() to > > handle architecture needs above the level of the device itself. > > Yea, all that bus_space_barrier() does is say ?We?ve made sure that > the CPU and all other bridges between the CPU and the device have > any buffered writes pushed to the device.? If the device has additional FIFOs > and other things, that?s 100% on the device writer. Except that doesn't happen right now... bus_space_barrier on amd64 does a locked stack access, but that won't cause any write buffers on bridges to flush... > >>> I was just looking at i386's implementation of bus_space_barrier and > >>> it just does a stack access... This won't be sufficient to clear any > >>> PCI bridges that may have the write still pending... > >> > >> Right. The memory barrier semantics right now don't at all guarantee > >> that bus and device FIFOs have actually been flushed. > >> > > The fact that some architectures don't implement bus_space_barrier() in > > a way that's useful for that architecture is just a bug. It doesn't > > change the fact that bus_space_barrier() is currently our only defined > > MI interface to barriers in device space. I agree... Now if you convince people on the correct way to fix bus_space_barrier to do the correct thing, then I don't have a problem having drivers use bus_space_barrier... My only issue is that as things are now, adding bus_space_barrier will not fix PCI devices... > Agreed. But PCI defines that reads flush out all prior writes. > > >> So I don't think doing it using the existing bus space barrier > >> semantics is 'right'. For interrupts, it's highly likely that we do > >> actually need device drivers to read from their interrupt register to > >> ensure the update has been posted before returning. That's better than > >> causing entire L2 cache flushes. > >> > > > > Where did you see code that does an "entire L2 cache flush"? You > > didn't, you just saw a function name and made assumptions about what it > > does. The fact is, it does what is necessary for the architecture. It > > also happens to do what a write-then-read does on armv6, but that's > > exactly the sort of assumption that should NOT be written into MI > > code. > > Yea, a bus barrier just means a temporal ordering. The exact strength > of that guarantee is a bit fuzzy, but generally it means we know things > are done. L2 is usually not an issue, because we have the devices mapped > uncached. > > As for reading the ISR, that is device dependent. When using MSI things are > different because the status is pushed to the host and you get the info from reading > the host memory. Ideally, you?d want to write to ack them without having to do > a read over PCIe, but even that?s not always required (and on such devices > they would correct without bus barriers). Newer devices have been designed > to avoid round-trips over the PCIe bus and having semantics that matter. > > >> Question is - can we expose this somehow as a generic device method, > >> so the higher bus layers can actually do something with it, or should > >> we just leave it to device drivers to correctly do? > >> > > > > In what way is that not EXACTLY whas bus_space_barrier() is defined to > > do? > > > > I've got to say, I don't understand all this pushback. We have one > > function defined already that's intended to be the machine-independant > > way to ensure that any previous access to hardware using bus_space reads > > and writes has completed, so why all this argument that it is not the > > function to use? The argument isn't that it's not the function to use, the argument is that the function is broken, or doesn't do what it says in the docs... Actually, the docs don't guarantee that the writes will be completed after the call, the docs say: All of the specified type(s) of operation which are done to the region before the barrier operation are guaranteed to complete before any of the specified type(s) of operation done after the barrier. So that means a following read will return correct results... so, per bus_space_barrier docs, all ISRs should probably be: write to clear ISR bus_space_barrier read to clear ISR so that the write w/ bus_space_barrier is known to complete So, sounds like we still need the read even w/ the bus_space_barrier. Now it could be our docs are wrong, but in that case, they should be fixed... > I agree with Ian here. If we?ve messed up, we need to fix that. But for the most > part, devices that are in embedded land actually do the right thing (more often > than not). If we?re doing something wrong on coherent architectures that accidentally > works, we should fix that. > > I may disagree with Ian about the need for some of the flushing based on the notion > that we should fix the drivers. I feel it just makes the problem persist. Things should > be more visibly broken. Ian thinks things should work, and I have a hard time arguing > with that position even if I disagree :). -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-arm@FreeBSD.ORG Sun Sep 7 17:56:30 2014 Return-Path: Delivered-To: freebsd-arm@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 0D2F66D7 for ; Sun, 7 Sep 2014 17:56:30 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E8AA21862 for ; Sun, 7 Sep 2014 17:56:29 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s87HuTBM047649 for ; Sun, 7 Sep 2014 17:56:29 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 193437] New: Cubieboard2: lock order reversal on poweroff Date: Sun, 07 Sep 2014 17:56:30 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: che@bein.link X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Sep 2014 17:56:30 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193437 Bug ID: 193437 Summary: Cubieboard2: lock order reversal on poweroff Product: Base System Version: 11.0-CURRENT Hardware: Any OS: Any Status: Needs Triage Severity: Affects Only Me Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: che@bein.link Gave poweroff command to my cubieboard, it begins to power off, syncs disks and I get the following: All buffers synced. lock order reversal: 1st 0xc3d8c274 ufs (ufs) @ /home/che/freebsd-src/head/sys/kern/vfs_mount.c:1223 2nd 0xc3d8c5d4 devfs (devfs) @ /home/che/freebsd-src/head/sys/kern/vfs_subr.c:2137 KDB: stack backtrace: db_trace_self() at db_trace_self pc = 0xc0509484 lr = 0xc02347e0 (X_db_symbol_values+0x11c) sp = 0xebbcaa00 fp = 0xebbcab18 r10 = 0xc3d8c5d4 X_db_symbol_values() at X_db_symbol_values+0x11c pc = 0xc02347e0 lr = 0xc0370d60 (kdb_backtrace+0x38) sp = 0xebbcab20 fp = 0xebbcab28 r4 = 0xc0639a94 r5 = 0xc0550f1e r6 = 0xc0573682 r7 = 0xc0572c46 kdb_backtrace() at kdb_backtrace+0x38 pc = 0xc0370d60 lr = 0xc038c608 (witness_checkorder+0xe58) sp = 0xebbcab30 fp = 0xebbcab80 r4 = 0xc055e3ff witness_checkorder() at witness_checkorder+0xe58 pc = 0xc038c608 lr = 0xc031adb8 (__lockmgr_args+0x8b4) sp = 0xebbcab88 fp = 0xebbcabf0 r4 = 0x00000100 r5 = 0x00080500 r6 = 0x00000859 r7 = 0xc3d8c5f4 r8 = 0xc3d8c5d4 r9 = 0x00080000 r10 = 0xc057367f __lockmgr_args() at __lockmgr_args+0x8b4 pc = 0xc031adb8 lr = 0xc03d18b0 (vop_stdlock+0x3c) sp = 0xebbcabf8 fp = 0xebbcac08 r4 = 0xebbcac28 r5 = 0xc0613f40 r6 = 0x00000000 r7 = 0x00080500 r8 = 0xebbcac28 r9 = 0xc05512fb r10 = 0x00000859 vop_stdlock() at vop_stdlock+0x3c pc = 0xc03d18b0 lr = 0xc052ba20 (VOP_LOCK1_APV+0xd8) sp = 0xebbcac10 fp = 0xebbcac20 VOP_LOCK1_APV() at VOP_LOCK1_APV+0xd8 pc = 0xc052ba20 lr = 0xc03efc14 (_vn_lock+0x44) sp = 0xebbcac28 fp = 0xebbcac58 r4 = 0xc3d8c5a0 r5 = 0xc3d45500 r6 = 0xc057367f _vn_lock() at _vn_lock+0x44 pc = 0xc03efc14 lr = 0xc03e048c (vget+0x60) sp = 0xebbcac60 fp = 0xebbcac80 r4 = 0xc3d8c5a0 r5 = 0xc3d45500 r6 = 0x00080500 r7 = 0xc3d45514 r8 = 0xc3a87640 r9 = 0xc05512fb r10 = 0x00000000 vget() at vget+0x60 pc = 0xc03e048c lr = 0xc02952b8 (devfs_allocv+0xf8) sp = 0xebbcac88 fp = 0xebbcacb0 r4 = 0xc08de4ac r5 = 0xc3d45500 r6 = 0xc3d6f100 r7 = 0xc3d45514 r8 = 0x00080500 devfs_allocv() at devfs_allocv+0xf8 pc = 0xc02952b8 lr = 0xc0294d80 (devfs_unmount_final+0x4ec) sp = 0xebbcacb8 fp = 0xebbcacc8 r4 = 0xebbcace8 r5 = 0xc3d8a560 r6 = 0xc3d45500 r7 = 0x00000000 r8 = 0xc3a87640 r9 = 0x00080000 r10 = 0x00080000 devfs_unmount_final() at devfs_unmount_final+0x4ec pc = 0xc0294d80 lr = 0xc03d9c78 (dounmount+0x3a0) sp = 0xebbcacd0 fp = 0xebbcad18 r4 = 0xc3d8c240 r5 = 0x00001000 r6 = 0xc0572c43 dounmount() at dounmount+0x3a0 pc = 0xc03d9c78 lr = 0xc03e2688 (vfs_unmountall+0x48) sp = 0xebbcad20 fp = 0xebbcad40 r4 = 0xc3a87640 r5 = 0xc055e3ff r6 = 0xc0562bd0 r7 = 0xc3d8a560 r8 = 0xc06141e0 r9 = 0xc056a980 r10 = 0xc0573d14 vfs_unmountall() at vfs_unmountall+0x48 pc = 0xc03e2688 lr = 0xc03377b4 (kern_reboot+0x4d4) sp = 0xebbcad48 fp = 0xebbcada8 r4 = 0xc0620474 r5 = 0x00000000 r6 = 0xc0562bd0 r7 = 0xd91156a8 r8 = 0xc062b610 r9 = 0x00004008 r10 = 0xc08dfa9c kern_reboot() at kern_reboot+0x4d4 pc = 0xc03377b4 lr = 0xc03372d8 (sys_reboot+0x44) sp = 0xebbcadb0 fp = 0xebbcadb8 r4 = 0xebbcae18 r5 = 0xc3a84640 r6 = 0x00000000 r7 = 0x00000000 r8 = 0x0000001f r9 = 0xebbcae10 r10 = 0x0000001e sys_reboot() at sys_reboot+0x44 pc = 0xc03372d8 lr = 0xc051f4ec (swi_handler+0x290) sp = 0xebbcadc0 fp = 0xebbcae58 r4 = 0xc3a87640 swi_handler() at swi_handler+0x290 pc = 0xc051f4ec lr = 0xc050b0fc (swi_exit) sp = 0xebbcae60 fp = 0xbffff938 r4 = 0x000de700 r5 = 0x000dc0c0 r6 = 0x00000034 r7 = 0x00000037 r8 = 0x0000001f r9 = 0x0000000e swi_exit() at swi_exit pc = 0xc050b0fc lr = 0xc050b0fc (swi_exit) sp = 0xebbcae60 fp = 0xbffff938 Unable to unwind further Uptime: 5m47s The operating system has halted. Please press any key to reboot. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-arm@FreeBSD.ORG Sun Sep 7 17:56:52 2014 Return-Path: Delivered-To: freebsd-arm@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 EE858715 for ; Sun, 7 Sep 2014 17:56:52 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D612B1867 for ; Sun, 7 Sep 2014 17:56:52 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s87HuqvS048233 for ; Sun, 7 Sep 2014 17:56:52 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 193437] Cubieboard2: lock order reversal on poweroff Date: Sun, 07 Sep 2014 17:56:53 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: che@bein.link X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: rep_platform Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Sep 2014 17:56:53 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193437 Maxim Filimonov changed: What |Removed |Added ---------------------------------------------------------------------------- Hardware|Any |arm -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-arm@FreeBSD.ORG Sun Sep 7 18:01:13 2014 Return-Path: Delivered-To: freebsd-arm@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 1643578D; Sun, 7 Sep 2014 18:01:13 +0000 (UTC) Received: from mail-wi0-x22d.google.com (mail-wi0-x22d.google.com [IPv6:2a00:1450:400c:c05::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 398C5188A; Sun, 7 Sep 2014 18:01:12 +0000 (UTC) Received: by mail-wi0-f173.google.com with SMTP id cc10so1566155wib.12 for ; Sun, 07 Sep 2014 11:01:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=AG7jPUP5GOQW453Rv6J5WZXUBb6dtuexfMIe+WQdf8U=; b=V4aqyjpR8xRPAt3yH1S+zGcWHlCWWFWgei+aDgHbaqOTqroWr52uA7xNPPaMIqNR+W Yu/+PsK3BE5nTWb/RNbMSMEkc/UoX4Eip+B2pbZmT6ROaxDGAOmlrS+o1yEA5rbCIcns IuzMuvpo2NwbpNxEs4/Ml0FNGM84RYRVrsX6twlIFm1nNal6Xe7Qms0JlVBN3e7LT6Vi xozMAw4N22ho/pwOPgFhCCOdAXCokMybxLq718348vm0tR0BLk+yujNnE7IEYi5t9ymY fo+HhDQGKG2jEZjadx22DAB5eTjVli2H5sG8WhtWw15AgaEV4lKoYhfqMwJWf5YGp9k1 RtLQ== MIME-Version: 1.0 X-Received: by 10.194.19.165 with SMTP id g5mr29180956wje.65.1410112870408; Sun, 07 Sep 2014 11:01:10 -0700 (PDT) Received: by 10.180.87.228 with HTTP; Sun, 7 Sep 2014 11:01:10 -0700 (PDT) Date: Sun, 7 Sep 2014 22:01:10 +0400 Message-ID: Subject: Android Emulator for FreeBSD + FreeBSD/ARM port From: Alexander Tarasikov To: "freebsd-arm@freebsd.org" , freebsd-hackers@freebsd.org, freebsd-emulation@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: Gavin Atkinson X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Sep 2014 18:01:13 -0000 Hi, FreeBSD crowd! During summer as part of GSoC program I was working on porting FreeBSD to the Android Emulator. Besides, I have ported Android Emulator to run natively on x86_64 as opposed to using linuxulator for 32-bit support. As for the kernel side, I have implemented the support for the following hardware: *IRQ, Timer, UART *MMC *Ethernet *Framebuffer (using NEWCONS) It allows to mount rootfs and boot up to login prompt with raspberry pi sd card image. As for the emulator, it's a bit complicated. FreeBSD boots fine if you launch the emulator on Linux or Mac OS X. I have fixed some parts of the build system and headers to make it compile and pass the tests on FreeBSD. Unfortunately, the GUI doesn't work right now and only console output (virtual UART) works. If anyone is interested, I would like that you read my blog post, review my kernel commit and suggest ways to improve and push the changes upstream. As for the Emulator, I think we can get it running with GUI and everything because it just has too many "#ifdef __linux__" stuff around the code which should compile and run on FreeBSD as well, we just need to gradually uncomment each of these sections. Relevant links: [kernel code commit] https://github.com/astarasikov/freebsd/commit/514be1f08a552f54abef83232498559c72e1d33b [README, compilation instructions] https://github.com/astarasikov/freebsd/blob/android_goldfish_arm_master/sys/arm/goldfish/README [Emulator with patches] https://github.com/astarasikov/qemu/tree/l-preview-freebsd [blog] http://allsoftwaresucks.blogspot.ru/2014/09/gsoc-results-or-how-i-nearly-wasted.html -- Regards, Alexander From owner-freebsd-arm@FreeBSD.ORG Sun Sep 7 20:32:50 2014 Return-Path: Delivered-To: freebsd-arm@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 50B184CE; Sun, 7 Sep 2014 20:32:50 +0000 (UTC) Received: from mail-qg0-x22f.google.com (mail-qg0-x22f.google.com [IPv6:2607:f8b0:400d:c04::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D29EA18EC; Sun, 7 Sep 2014 20:32:49 +0000 (UTC) Received: by mail-qg0-f47.google.com with SMTP id i50so310928qgf.34 for ; Sun, 07 Sep 2014 13:32:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=qjD/4mZXcqXbD3kRE4IBtfypR4RkfZJMeb+AvZdW7hA=; b=pO1by0zuUmKP+MGh5rTmgAnihkJkSf/CfejD9VLFVUYvbD41tdPJdz3KAY/6BYlUZW S1RYKfYh4BJ4HwzdqPcvhCH8b0tcPVMbv72Vkm66OxTb/XXEBzRUklbLNX6huUyIbPJJ jlpG/fQoMQWusCEpWWnkPkRZCg5fWMo+4bpGI7HDDipV73Qz16ZTwjQnJtsIhafCt8qg ULA9TGHrncuwsezw53bgytOw2Bl4673en6ifdFTUbgy1PEP46joVcUocQWOsuWoDSVf3 av0Xz7MPr9JsGLz1u4kT+QvQg9zVcO2STdVS5Nc9ayWqrH6niqhKlZQLkid13fbNCjwd h4jA== MIME-Version: 1.0 X-Received: by 10.224.151.69 with SMTP id b5mr36549971qaw.37.1410121968853; Sun, 07 Sep 2014 13:32:48 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.39.139 with HTTP; Sun, 7 Sep 2014 13:32:48 -0700 (PDT) In-Reply-To: References: Date: Sun, 7 Sep 2014 13:32:48 -0700 X-Google-Sender-Auth: xUycw52RJnT7I_ozjXhKuDhMrQA Message-ID: Subject: Re: Android Emulator for FreeBSD + FreeBSD/ARM port From: Adrian Chadd To: Alexander Tarasikov Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-hackers@freebsd.org" , "freebsd-arm@freebsd.org" , Gavin Atkinson , freebsd-emulation@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Sep 2014 20:32:50 -0000 On 7 September 2014 11:01, Alexander Tarasikov wrote: > Hi, FreeBSD crowd! > > During summer as part of GSoC program I was working on porting FreeBSD > to the Android Emulator. Cool! > Besides, I have ported Android Emulator to run natively on x86_64 as opposed to > using linuxulator for 32-bit support. Double cool! > As for the kernel side, I have implemented the support for the > following hardware: > *IRQ, Timer, UART > *MMC > *Ethernet > *Framebuffer (using NEWCONS) Triple cool! > It allows to mount rootfs and boot up to login prompt with raspberry > pi sd card image. > > As for the emulator, it's a bit complicated. FreeBSD boots fine if you > launch the emulator on Linux or Mac OS X. I have fixed some parts of > the build system and headers to make it compile and pass the tests on > FreeBSD. Unfortunately, the GUI doesn't work right now and only > console output (virtual UART) works. > > If anyone is interested, I would like that you read my blog post, > review my kernel commit and suggest ways to improve and push the > changes upstream. As for the Emulator, I think we can get it running > with GUI and everything because it just has too many "#ifdef > __linux__" stuff around the code which should compile and run on > FreeBSD as well, we just need to gradually uncomment each of these > sections. > > Relevant links: > [kernel code commit] > https://github.com/astarasikov/freebsd/commit/514be1f08a552f54abef83232498559c72e1d33b > [README, compilation instructions] > https://github.com/astarasikov/freebsd/blob/android_goldfish_arm_master/sys/arm/goldfish/README > [Emulator with patches] > https://github.com/astarasikov/qemu/tree/l-preview-freebsd > [blog] http://allsoftwaresucks.blogspot.ru/2014/09/gsoc-results-or-how-i-nearly-wasted.html This work is awesome. I'll see if I can spin it up! -a From owner-freebsd-arm@FreeBSD.ORG Tue Sep 9 00:30:17 2014 Return-Path: Delivered-To: freebsd-arm@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 B032DDD3 for ; Tue, 9 Sep 2014 00:30:17 +0000 (UTC) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "raven.bwct.de", Issuer "BWCT" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3FAF4BAF for ; Tue, 9 Sep 2014 00:30:16 +0000 (UTC) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id s890TxK9065001 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Tue, 9 Sep 2014 02:30:00 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id s890TsY6005783 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Sep 2014 02:29:54 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id s890Ts80024821; Tue, 9 Sep 2014 02:29:54 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id s890TsJh024820; Tue, 9 Sep 2014 02:29:54 +0200 (CEST) (envelope-from ticso) Date: Tue, 9 Sep 2014 02:29:54 +0200 From: Bernd Walter To: freebsd-arm@freebsd.org Subject: Re: Crochet partition alignment Message-ID: <20140909002954.GB24276@cicely7.cicely.de> Reply-To: ticso@cicely.de Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, FAKE_REPLY_C=1.486, T_RP_MATCHES_RCVD=-0.01 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de Cc: Bernd Walter X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Sep 2014 00:30:17 -0000 [67]wandboard# gpart list Geom name: mmcsd0 modified: false state: OK fwheads: 255 fwsectors: 63 last: 61497343 first: 63 entries: 4 scheme: MBR Providers: 1. Name: mmcsd0s1 Mediasize: 52416000 (50M) Sectorsize: 512 Stripesize: 4194304 Stripeoffset: 30208 Mode: r1w1e1 attrib: active rawtype: 12 length: 52416000 offset: 8418816 type: !12 index: 1 end: 118817 start: 16443 2. Name: mmcsd0s2 Mediasize: 31425805312 (29G) Sectorsize: 512 Stripesize: 4194304 Stripeoffset: 2114560 Mode: r1w1e2 rawtype: 165 length: 31425805312 offset: 60834816 type: freebsd index: 2 end: 61497343 start: 118818 Consumers: 1. Name: mmcsd0 Mediasize: 31486640128 (29G) Sectorsize: 512 Stripesize: 4194304 Stripeoffset: 0 Mode: r2w2e5 Geom name: mmcsd0s2 modified: false state: OK fwheads: 255 fwsectors: 63 last: 61378525 first: 0 entries: 8 scheme: BSD Providers: 1. Name: mmcsd0s2a Mediasize: 31425757184 (29G) Sectorsize: 512 Stripesize: 4194304 Stripeoffset: 2162688 Mode: r1w1e1 rawtype: 7 length: 31425757184 offset: 48128 type: freebsd-ufs index: 1 end: 61378525 start: 94 Consumers: 1. Name: mmcsd0s2 Mediasize: 31425805312 (29G) Sectorsize: 512 Stripesize: 4194304 Stripeoffset: 2114560 Mode: r1w1e2 There are 63 sectors per track in MBR table. s1 starts at sector 16443 in track 261. This is an uneven 512 byte sector number, so it starts at 512 Byte alignment only. Leaves the question why 261 tracks are left out when it still isn't aligned? s2, which is what I care most about, starts at 118818. This is even, but only once divideable by 2. It is at a 1024 alignment - still not the needed >= 4k for SD cards. Inside s2 the a partition starts at 48128 (+118818 from provider). Again lost space. By itself it would be a 512k alignment - more than perfect, though I don't think it requires such a big waste, but with the mmcsd0s2 provider alignemt it's still only 1k. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@FreeBSD.ORG Tue Sep 9 01:51:50 2014 Return-Path: Delivered-To: freebsd-arm@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 180BB778 for ; Tue, 9 Sep 2014 01:51:50 +0000 (UTC) Received: from mail-pa0-f47.google.com (mail-pa0-f47.google.com [209.85.220.47]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2A71F1139 for ; Tue, 9 Sep 2014 01:14:08 +0000 (UTC) Received: by mail-pa0-f47.google.com with SMTP id ey11so5952712pad.20 for ; Mon, 08 Sep 2014 18:14:02 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=gugulCANxzDmPzurqlntpb0PV5sUM6mN4u5++GXkaEE=; b=lXh4aYFMRYwiGZPA44MDUB3AJxxLk7+x4TIoKBbeoJKRs5PT9uF5txEdjD/H1HyHOy Of8Z5WK95+mfm0bRLVD/5br+oCoKW2Bme3BlGAWBqNVwjY+qF8IP/BYHKYZtykr2KDaa uZ+w2RE+A66uUGl7SXPoM8Ut3S8ANmmuKIrgB6+3LzFIYPSJn8z4uc84zAqpeRqoJ8er O0v/rXLfo2qSFvTmiAUK0k3y9mHei8P075x/sh+5RLrg50X7r3u2o/P7ozt1Xa9OeHhD 9chETUmgVpbTmKaUq1DRWFd9/ynrh481/mVMceA47HPFtOK5QGYP6V45I36fHmlx3V1a OXFw== X-Gm-Message-State: ALoCoQk1ATywzhly0ZD5+DJjKPiZaoG+phqBJv/FjCSszid/qdIL+Z5pNnIrZcT4qpa6F7d6LPBO X-Received: by 10.70.92.36 with SMTP id cj4mr9921794pdb.156.1410224915602; Mon, 08 Sep 2014 18:08:35 -0700 (PDT) Received: from [192.168.1.100] (c-24-6-220-224.hsd1.ca.comcast.net. [24.6.220.224]) by mx.google.com with ESMTPSA id ig4sm9908406pbb.55.2014.09.08.18.08.34 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 08 Sep 2014 18:08:34 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: Crochet partition alignment From: Tim Kientzle In-Reply-To: <20140909002954.GB24276@cicely7.cicely.de> Date: Mon, 8 Sep 2014 18:08:33 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <5053828F-435E-4ED0-AF8E-F0D4F9C3BF5C@kientzle.com> References: <20140909002954.GB24276@cicely7.cicely.de> To: ticso@cicely.de X-Mailer: Apple Mail (2.1878.6) Cc: freebsd-arm@freebsd.org, Bernd Walter X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Sep 2014 01:51:50 -0000 Do you disagree with this commit? = https://github.com/kientzle/crochet-freebsd/commit/3f4818b6ad668eb4a1d7a55= bd1634719a18d7729 If so, what do you propose here? Cheers, Tim From owner-freebsd-arm@FreeBSD.ORG Tue Sep 9 02:01:02 2014 Return-Path: Delivered-To: freebsd-arm@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 30C2B923 for ; Tue, 9 Sep 2014 02:01:02 +0000 (UTC) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "raven.bwct.de", Issuer "BWCT" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B36CF1768 for ; Tue, 9 Sep 2014 02:01:01 +0000 (UTC) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id s8920rTx066537 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 9 Sep 2014 04:00:53 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id s8920lwB008139 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Sep 2014 04:00:47 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id s8920k02025763; Tue, 9 Sep 2014 04:00:46 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id s8920kQH025762; Tue, 9 Sep 2014 04:00:46 +0200 (CEST) (envelope-from ticso) Date: Tue, 9 Sep 2014 04:00:46 +0200 From: Bernd Walter To: Tim Kientzle Subject: Re: Crochet partition alignment Message-ID: <20140909020046.GC24276@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <20140909002954.GB24276@cicely7.cicely.de> <5053828F-435E-4ED0-AF8E-F0D4F9C3BF5C@kientzle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5053828F-435E-4ED0-AF8E-F0D4F9C3BF5C@kientzle.com> X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de Cc: freebsd-arm@freebsd.org, Bernd Walter , ticso@cicely.de X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Sep 2014 02:01:02 -0000 On Mon, Sep 08, 2014 at 06:08:33PM -0700, Tim Kientzle wrote: > Do you disagree with this commit? > > https://github.com/kientzle/crochet-freebsd/commit/3f4818b6ad668eb4a1d7a55bd1634719a18d7729 > > If so, what do you propose here? No sorry - no serious problem exists. It was my fault - I took the wrong numbers. You request 64k alignment for the UFS partition and that's what we get. I added 118818 of the slice and 48128 for the partition. This was adding two different things - first number is sector offset and the later is byte offset. In fact it is 118818 + 94, which is perfectly 64k aligned. 94 sectors is the smallest loss to get to the next 64k - perfect. The msdosfs slice is unaligned but it isn't updated very often, so it's probably Ok with that. There is still that big 8M gap in front of the msdos slice, which I can't explain with crochet. You request an 63 Byte alignment for that slice - odd requirement IMHO, but should be fullfilled starting with second 63 sector track. But this would be just ~32k and not 8M. Not that this 8M loss is important with nGbyte media, but still unexpected. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@FreeBSD.ORG Tue Sep 9 04:03:05 2014 Return-Path: Delivered-To: freebsd-arm@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 4A772A6B for ; Tue, 9 Sep 2014 04:03:05 +0000 (UTC) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "raven.bwct.de", Issuer "BWCT" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D0A9A8DA for ; Tue, 9 Sep 2014 04:03:04 +0000 (UTC) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id s8942lGw067888 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Tue, 9 Sep 2014 06:02:47 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id s8942g8D009084 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Sep 2014 06:02:42 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id s8942gfN026295; Tue, 9 Sep 2014 06:02:42 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id s8942gLh026294; Tue, 9 Sep 2014 06:02:42 +0200 (CEST) (envelope-from ticso) Date: Tue, 9 Sep 2014 06:02:42 +0200 From: Bernd Walter To: freebsd-arm@freebsd.org Subject: compile error in atomic.h when compiling c++ Message-ID: <20140909040224.GA26202@cicely7.cicely.de> Reply-To: ticso@cicely.de Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de Cc: Bernd Walter X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Sep 2014 04:03:05 -0000 System is r271289M with clang. [114]wandboard# cat test.cc #include #include int main(int argc, char *argv[]) { return 0; } [115]wandboard# c++ -Wall test.cc In file included from test.cc:2: /usr/include/machine/atomic.h:286:8: error: expected identifier [new] "r" (newval) ^ /usr/include/machine/atomic.h:286:11: error: expected expression [new] "r" (newval) ^ 2 errors generated. Exit 1 I assume it has problems with "new" used here, which is a special keyword in C++. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@FreeBSD.ORG Tue Sep 9 13:51:55 2014 Return-Path: Delivered-To: freebsd-arm@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 5DBCDCED for ; Tue, 9 Sep 2014 13:51:55 +0000 (UTC) Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 312F2DB4 for ; Tue, 9 Sep 2014 13:51:55 +0000 (UTC) Received: from [73.34.117.227] (helo=ilsoft.org) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1XRLpp-000EOZ-Fi; Tue, 09 Sep 2014 13:51:53 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id s89Dpq0H024067; Tue, 9 Sep 2014 07:51:52 -0600 (MDT) (envelope-from ian@FreeBSD.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 73.34.117.227 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1/T1ATAscuRhhR1JIWK3jZF X-Authentication-Warning: paranoia.hippie.lan: Host revolution.hippie.lan [172.22.42.240] claimed to be [172.22.42.240] Subject: Re: compile error in atomic.h when compiling c++ From: Ian Lepore To: Bernd Walter In-Reply-To: <20140909040224.GA26202@cicely7.cicely.de> References: <20140909040224.GA26202@cicely7.cicely.de> Content-Type: text/plain; charset="us-ascii" Date: Tue, 09 Sep 2014 07:51:51 -0600 Message-ID: <1410270711.1150.409.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Sep 2014 13:51:55 -0000 On Tue, 2014-09-09 at 06:02 +0200, Bernd Walter wrote: > System is r271289M with clang. > > [114]wandboard# cat test.cc > #include > #include > > int > main(int argc, char *argv[]) > { > return 0; > } > > [115]wandboard# c++ -Wall test.cc > In file included from test.cc:2: > /usr/include/machine/atomic.h:286:8: error: expected identifier > [new] "r" (newval) > ^ > /usr/include/machine/atomic.h:286:11: error: expected expression > [new] "r" (newval) > ^ > 2 errors generated. > Exit 1 > > I assume it has problems with "new" used here, which is a special > keyword in C++. > My bad, fixed in r271310. Jeez, I used to be able to call myself "mostly a C++ programmer" and would automatically not make such a mistake. For the past couple years it seems all I've written is C. -- Ian From owner-freebsd-arm@FreeBSD.ORG Wed Sep 10 11:16:47 2014 Return-Path: Delivered-To: freebsd-arm@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 BAFBDA07 for ; Wed, 10 Sep 2014 11:16:47 +0000 (UTC) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "raven.bwct.de", Issuer "BWCT" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0B1CCC0 for ; Wed, 10 Sep 2014 11:16:46 +0000 (UTC) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id s8ABGM8j032273 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Wed, 10 Sep 2014 13:16:22 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id s8ABGGmj029347 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 10 Sep 2014 13:16:16 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id s8ABGGml034458; Wed, 10 Sep 2014 13:16:16 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id s8ABGG8s034457; Wed, 10 Sep 2014 13:16:16 +0200 (CEST) (envelope-from ticso) Date: Wed, 10 Sep 2014 13:16:16 +0200 From: Bernd Walter To: freebsd-arm@freebsd.org Subject: buildworld selfbuild failure Message-ID: <20140910111616.GA31990@cicely7.cicely.de> Reply-To: ticso@cicely.de Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de Cc: Bernd Walter X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Sep 2014 11:16:47 -0000 The same source code was used to build with crochet and is running on the system. It's a Wandboard Quad with a -j8 buildworld run. Source tree is on NFS /usr/obj on local SD. =2E.. --- lib_tputs.So --- cc -fpic -DPIC -O -pipe -I. -I/usr/obj/home/builder/arm-build/head/lib/= ncurses/ncurses/../ncurses -I/home/builder/arm-build/head/lib/ncurses/ncurs= es/../ncurses -I/home/builder/arm-build/head/lib/ncurses/ncurses/../ncurses= -I/home/builder/arm-build/head/lib/ncurses/ncurses/../../../contrib/ncurse= s/include -I/home/builder/arm-build/head/lib/ncurses/ncurses/../../../contr= ib/ncurses/ncurses -Wall -DNDEBUG -DHAVE_CONFIG_H -DFREEBSD_NATIVE -DTERMIO= S -std=3Dgnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unuse= d-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-u= ninitialized -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-un= used-const-variable -Wno-tautological-compare -Wno-unused-value -Wno-parent= heses-equality -Wno-unused-function -Wno-enum-conversion -Qunused-arguments= -c /home/builder/arm-build/head/lib/ncurses/ncurses/../../../contrib/ncurs= es/ncurses/tinfo/lib_tputs.c -o lib_tputs.So --- lib/ncurses/ncursesw__L --- --- free_ttype.So --- cc -fpic -DPIC -O -pipe -D_XOPEN_SOURCE_EXTENDED -DENABLE_WIDEC -I. -I/= usr/obj/home/builder/arm-build/head/lib/ncurses/ncursesw/../ncursesw -I/hom= e/builder/arm-build/head/lib/ncurses/ncursesw/../ncursesw -I/home/builder/a= rm-build/head/lib/ncurses/ncursesw/../ncurses -I/home/builder/arm-build/hea= d/lib/ncurses/ncursesw/../../../contrib/ncurses/include -I/home/builder/arm= -build/head/lib/ncurses/ncursesw/../../../contrib/ncurses/ncurses -Wall -DN= DEBUG -DHAVE_CONFIG_H -DFREEBSD_NATIVE -DTERMIOS -std=3Dgnu99 -Wsystem-head= ers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototy= pes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-si= gn -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-tau= tological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-f= unction -Wno-enum-conversion -Qunused-arguments -c /home/builder/arm-build/= head/lib/ncurses/ncursesw/../../../contrib/ncurses/ncurses/tinfo/free_ttype= =2Ec -o free_ttype.So --- kerberos5/lib/libheimsqlite__L --- cc: error: unable to execute command: Bus error (core dumped) cc: error: clang frontend command failed due to signal (use -v to see invoc= ation) FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512 Target: armv6--freebsd11.0-gnueabi Thread model: posix cc: note: diagnostic msg: PLEASE submit a bug report to https://bugs.freebs= d.org/submit/ and include the crash backtrace, preprocessed source, and ass= ociated run script. cc: note: diagnostic msg: Error generating preprocessed source(s). *** [sqlite3.o] Error code 254 make[4]: stopped in /home/builder/arm-build/head/kerberos5/lib/libheimsqlite --- lib/msun__L --- A failure has been detected in another branch of the parallel make make[4]: stopped in /home/builder/arm-build/head/lib/msun --- lib/ncurses/ncursesw__L --- A failure has been detected in another branch of the parallel make make[4]: stopped in /home/builder/arm-build/head/lib/ncurses/ncursesw --- lib/ncurses/ncurses__L --- A failure has been detected in another branch of the parallel make make[4]: stopped in /home/builder/arm-build/head/lib/ncurses/ncurses --- kerberos5/lib/libheimsqlite__L --- 1 error make[4]: stopped in /home/builder/arm-build/head/kerberos5/lib/libheimsqlite --- secure/lib/libcrypto__L --- A failure has been detected in another branch of the parallel make make[4]: stopped in /home/builder/arm-build/head/secure/lib/libcrypto A failure has been detected in another branch of the parallel make make[3]: stopped in /home/builder/arm-build/head *** [libraries] Error code 2 make[2]: stopped in /home/builder/arm-build/head 1 error make[2]: stopped in /home/builder/arm-build/head *** [_libraries] Error code 2 make[1]: stopped in /home/builder/arm-build/head 1 error make[1]: stopped in /home/builder/arm-build/head *** [buildworld] Error code 2 make: stopped in /home/builder/arm-build/head 1 error make: stopped in /home/builder/arm-build/head 71773.091u 36752.279s 2:47:24.86 1080.4% -40+98k 2728+6318io 4153pf+= 0w Exit 2 [170]wandboard# gdb /usr/obj/home/builder/arm-build/head/tmp/usr/bin/cc cc.= core=20 GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain condition= s. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "armv6-marcel-freebsd"...(no debugging symbols f= ound)... Core was generated by `cc'. Program terminated with signal 10, Bus error. #0 0x008dc410 in clang::SrcMgr::ContentCache::getBuffer () (gdb) bt #0 0x008dc410 in clang::SrcMgr::ContentCache::getBuffer () #1 0x00914330 in clang::SourceManager::getBuffer () #2 0x00912260 in clang::Preprocessor::EnterSourceFile () #3 0x008f70e8 in clang::Preprocessor::EnterMainSourceFile () #4 0x0030e760 in clang::ParseAST () #5 0x000411bc in clang::ASTFrontendAction::ExecuteAction () #6 0x001c0998 in clang::CodeGenAction::ExecuteAction () #7 0x00040a38 in clang::FrontendAction::Execute () #8 0x00060120 in clang::CompilerInstance::ExecuteAction () #9 0x00010340 in $a () #10 0x00010340 in $a () (gdb)=20 Retry without -j: CC=3D'cc ' mkdep -f .depend -a -I/home/builder/arm-build/head/kerberos5/= lib/libheimsqlite/../../../crypto/heimdal/lib/sqlite -DHAVE_CONFIG_H -I/hom= e/builder/arm-build/head/kerberos5/lib/libheimsqlite/../../include -std=3Dg= nu99 /home/builder/arm-build/head/kerberos5/lib/libheimsqlite/../../../cr= ypto/heimdal/lib/sqlite/sqlite3.c Stack dump: 0. Program arguments: /usr/obj/home/builder/arm-build/head/tmp/usr/bin= /cc -cc1 -triple armv6--freebsd11.0-gnueabi -Eonly -disable-free -main-file= -name sqlite3.c -mrelocation-model static -mdisable-fp-elim -mconstructor-a= liases -target-cpu arm1176jzf-s -target-feature +soft-float -target-feature= +soft-float-abi -target-feature -neon -target-abi aapcs-linux -msoft-float= -mfloat-abi soft -resource-dir /usr/obj/home/builder/arm-build/head/tmp/us= r/bin/../lib/clang/3.4.1 -dependency-file - -MT sqlite3.o -sys-header-deps = -D HAVE_CONFIG_H -I /home/builder/arm-build/head/kerberos5/lib/libheimsqlit= e/../../../crypto/heimdal/lib/sqlite -I /home/builder/arm-build/head/kerber= os5/lib/libheimsqlite/../../include -isysroot /usr/obj/home/builder/arm-bui= ld/head/tmp -std=3Dgnu99 -fno-dwarf-directory-asm -fdebug-compilation-dir /= usr/obj/home/builder/arm-build/head/kerberos5/lib/libheimsqlite -ferror-lim= it 19 -fmessage-length 132 -mstackrealign -fno-signed-char -fobjc-runtime= =3Dgnustep -fdiagnostics-show-option -fcolor-diagnostics -vectorize-slp -x = c /home/builder/arm-build/head/kerberos5/lib/libheimsqlite/../../../crypto/= heimdal/lib/sqlite/sqlite3.c=20 cc: error: unable to execute command: Bus error (core dumped) cc: error: clang frontend command failed due to signal (use -v to see invoc= ation) FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512 Target: armv6--freebsd11.0-gnueabi Thread model: posix cc: note: diagnostic msg: PLEASE submit a bug report to https://bugs.freebs= d.org/submit/ and include the crash backtrace, preprocessed source, and ass= ociated run script. cc: error: unable to execute command: Bus error (core dumped) cc: note: diagnostic msg: Error generating preprocessed source(s). mkdep: compile failed *** Error code 1 Stop. make[4]: stopped in /home/builder/arm-build/head/kerberos5/lib/libheimsqlite *** Error code 1 Stop. make[3]: stopped in /home/builder/arm-build/head *** Error code 1 Stop. make[2]: stopped in /home/builder/arm-build/head *** Error code 1 Stop. make[1]: stopped in /home/builder/arm-build/head *** Error code 1 Stop. make: stopped in /home/builder/arm-build/head 24569.709u 5898.985s 6:06:54.09 138.4% 116+219k 2557+11302io 77pf+0w Exit 1 [175]wandboard#=20 [180]wandboard# date Wed Sep 10 10:20:14 UTC 2014 [181]wandboard# gdb /usr/obj/home/builder/arm-build/head/tmp/usr/bin/cc cc.= core GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain condition= s. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "armv6-marcel-freebsd"...(no debugging symbols f= ound)... Core was generated by `cc'. Program terminated with signal 10, Bus error. #0 0x008dc410 in clang::SrcMgr::ContentCache::getBuffer () (gdb) bt #0 0x008dc410 in clang::SrcMgr::ContentCache::getBuffer () #1 0x00914330 in clang::SourceManager::getBuffer () #2 0x00912260 in clang::Preprocessor::EnterSourceFile () #3 0x008f70e8 in clang::Preprocessor::EnterMainSourceFile () #4 0x00013ac8 in clang::PreprocessOnlyAction::ExecuteAction () #5 0x00040a38 in clang::FrontendAction::Execute () #6 0x00060120 in clang::CompilerInstance::ExecuteAction () #7 0x00010340 in $a () #8 0x00010340 in $a () It's not obvious from -j8 run, but it happened when compiling in the same directory, maybe even the same file. --=20 B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@FreeBSD.ORG Wed Sep 10 20:54:03 2014 Return-Path: Delivered-To: freebsd-arm@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 6C6C7F01 for ; Wed, 10 Sep 2014 20:54:03 +0000 (UTC) Received: from nm18.bullet.mail.bf1.yahoo.com (nm18.bullet.mail.bf1.yahoo.com [98.139.212.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 214FAB8B for ; Wed, 10 Sep 2014 20:54:02 +0000 (UTC) Received: from [98.139.212.153] by nm18.bullet.mail.bf1.yahoo.com with NNFMP; 10 Sep 2014 20:52:02 -0000 Received: from [98.139.212.196] by tm10.bullet.mail.bf1.yahoo.com with NNFMP; 10 Sep 2014 20:52:02 -0000 Received: from [127.0.0.1] by omp1005.mail.bf1.yahoo.com with NNFMP; 10 Sep 2014 20:52:02 -0000 X-Yahoo-Newman-Property: ymail-5 X-Yahoo-Newman-Id: 404624.92135.bm@omp1005.mail.bf1.yahoo.com Received: (qmail 32373 invoked by uid 60001); 10 Sep 2014 20:52:02 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com.br; s=s1024; t=1410382322; bh=24MPYuZ1YIqKBSnlmxUcravdJNn69xe0BTCJoA13GBc=; h=Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=XElx1kyEn8ZY7O0jCvVjXEcIyjj+/r016zqqOtgijTy/xP7seTAeLssKTFI38rNijJvqN74Zh4zvRtCGgRMaCIcSPmx4jI4oAWQVwR3TSdYp1BHBVUvtXGgs1yTNoM5ZHE6i0fEFLRix/ziyfXGCRnoG+XzHNm9NOaOe+xmBe4M= X-YMail-OSG: D.FCaz4VM1mmMW4YCn_b5UgSfUlFxXefY7akfv_I1mvtNoj Ph2GJovfiZtoLBGbjphAhRaPxXGyOOrv.bW8998rNBDfOm0qyKttlJklFkJL IlHFNI0NTq8rWJEDcu3SNSBBOxA9IZ3pECbQxij5jMbN00WqYwCXQqEKW7SK m0t3fsdkvP9dVjtJatFrYjB7SsXj0AQVQ_STNcTanMf5p.OWVL8HTAEPK7Eo y1YKl31vcQVWNKMnGgm9HaXcNSDfDaZS5_v2Pt33qOWR5ftsf8qKykaYD.hb CXmrNvYu1N3togbMcnS8qc0q8sBIQ.SI_urMnccgLsdp3jptNrPd7zvDD.n1 V4AX4Pn6MNvCGjeRf_YOmgv9y48wblPVonSVvZgYoAhgIFO4ORA3oe5iGOKP UiSEyPj0TmSsMVEnh.jFODPy1WD221vSf7IEdFFzGxQrHkgfcfr5dIu6KbJJ pdm5MnHLV74C0jlQ6vbL_vWKxCKSW5sre2wp5TvFSA1tp8B9MNDP3qcXp0l_ UsFrLT61hi1qWjZ9gFdMz8keOKhVUFI1Wk_ZzFFR2BDuwlrUSaspHd9ZeD2z kQXFWzZibWfeHOEdEPyJEJ_Xe7l6ZR0WQ9U0fP7g9fB0dxMjU5a8EoJ3QS1v Boz0wbUiMxTNA9bX5QFbGiqLCnBcRSDHBfDTdTVAS3BQclW8syIWzcMqjyoC S Received: from [186.233.159.114] by web162003.mail.bf1.yahoo.com via HTTP; Wed, 10 Sep 2014 13:52:02 PDT X-Rocket-MIMEInfo: 002.001, SGkgYWxsLAoKSSB1cGRhdGVkIG15IHN5c3RlbSBvbiByYXNwYmVycnkgdG8gMTAuMC1QUkVSRUxFQVNFIChyMjcxNDAwKSBhbmQgbm93IHRoZSBzeXN0ZW0gaXMgc3RvcHBpbmcgYXQgdGhpcyBwb2ludCBbMV0uClRoaXMgaXMgYSBrbm93biBwcm9ibGVtPwoKU29ycnkgdGhlIGJhZCBxdWFsaXR5IHBpY3R1cmUuLi4KClsxXSAtIGh0dHBzOi8vd3d3LmRyb3Bib3guY29tL3NjL3I4OWhzMndhbDdkcG40NC9BQUJDS3FKekFCN0Z6bEh1Z2ZVdlFyVXZhATABAQEB X-Mailer: YahooMailWebService/0.8.203.696 Message-ID: <1410382322.23950.YahooMailNeo@web162003.mail.bf1.yahoo.com> Date: Wed, 10 Sep 2014 13:52:02 -0700 From: Danilo Egea Reply-To: Danilo Egea Subject: panic: run_interrupt_driven_config_hooks: waited to long on 10.1-PRERELEASE + RPI-B To: freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Sep 2014 20:54:03 -0000 Hi all,=0A=0AI updated my system on raspberry to 10.0-PRERELEASE (r271400) = and now the system is stopping at this point [1].=0AThis is a known problem= ?=0A=0ASorry the bad quality picture...=0A=0A[1] - https://www.dropbox.com/= sc/r89hs2wal7dpn44/AABCKqJzAB7FzlHugfUvQrUva From owner-freebsd-arm@FreeBSD.ORG Wed Sep 10 21:00:00 2014 Return-Path: Delivered-To: freebsd-arm@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 5CE22173 for ; Wed, 10 Sep 2014 21:00:00 +0000 (UTC) Received: from nm17.bullet.mail.bf1.yahoo.com (nm17.bullet.mail.bf1.yahoo.com [98.139.212.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0D3B4BD0 for ; Wed, 10 Sep 2014 20:59:59 +0000 (UTC) Received: from [98.139.214.32] by nm17.bullet.mail.bf1.yahoo.com with NNFMP; 10 Sep 2014 20:56:37 -0000 Received: from [98.139.212.196] by tm15.bullet.mail.bf1.yahoo.com with NNFMP; 10 Sep 2014 20:56:37 -0000 Received: from [127.0.0.1] by omp1005.mail.bf1.yahoo.com with NNFMP; 10 Sep 2014 20:56:37 -0000 X-Yahoo-Newman-Property: ymail-5 X-Yahoo-Newman-Id: 116020.96680.bm@omp1005.mail.bf1.yahoo.com Received: (qmail 64051 invoked by uid 60001); 10 Sep 2014 20:56:37 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com.br; s=s1024; t=1410382597; bh=jZVqEWwHhJm9k9+4MFLRwY/mFvSegRfTE4b5IYPaCFc=; h=References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=RFloCDJhJMwhqkT+DGlxeCdwMOPA9wgFJ3nFReuvfjiI6NhDhJho2AGXPBki9er6AqFvriFEW228HV9p4bkjTiFlvTIgX9a9nmL0v/tTorc7gOOJMhmrZzua67YH/9X9ad9lA3e1ArAxYcawyJ62+39eZW2flK0NFeHpWQuM7gg= X-YMail-OSG: n_wjb0UVM1mtQ6xldrI3aFFRnanl08jsgkEkmvuJBCcHZ.N kafo4aZA_wK3aM4KSEDIcE.fwNwfZRt4CgSTIKzYmr0WwUj8zhbaSyDw4GVn .5ladRgaT64hjfkLCMYIJO2.3sVis18D0iNbZJrKnTbh8czsgBWMcnjHxC.2 .8VL9CNPeTbEH3rrYnBuMogM1cT3Cl2lG.yeDsmU6PKzGMjYb5w8WSlVGvon C6JsiabfDnyN2Bc.U3XKe_2v19n0fcXZgj6yFSe4cYY3Zz.wBLIFq2nGq3ET jFP7vz7eC6X8VK1_qDSGvDphB04W7JtfHft7vizoNWv.R.mcMEiYaj0xzHCW KO65BYgPLGqBVViah9uDd1RbVgNE4Q8FyMTCG7NfDcETgFu0ZZeQ6HiFzIkO b2A7apoGymJDVqtIu8CTYp4tD71IzmPWdUYQC9q9vsJ8etq7RYU4fZBhmAZC 4nQekJisnOK2IHY2AeQ6v6usoLRH4ehALTpk9vd6MaBp2AUDviwDGykLnoyg AEYeOAzzHT05PxQWXYdtc.mxxH0_0tFqAzxmweluvB1Te_0lfbIM0bNtWEXL mJK33gnt.uMpmSb_S0afXhlcocfBFc58L2qsyI2gTmLPgWIsHIHMgx4LS_30 XhXsFRJdXFkXZ2ZGgrzUD4R_gc_d59Pz.OfaV5RQMDcDcFWPZfQaqtQ-- Received: from [186.233.159.114] by web162005.mail.bf1.yahoo.com via HTTP; Wed, 10 Sep 2014 13:56:36 PDT X-Rocket-MIMEInfo: 002.001, SGkgYWxsLAoKCgoKCgpJIHVwZGF0ZWQgbXkgc3lzdGVtIG9uIHJhc3BiZXJyeSB0byAxMC4wLVBSRVJFTEVBU0UgKHIyNzE0MDApIGFuZCBub3cgdGhlIHN5c3RlbSBpcyBzdG9wcGluZyBhdCB0aGlzIHBvaW50IFsxXS4KVGhpcyBpcyBhIGtub3duIHByb2JsZW0_CgpTb3JyeSB0aGUgYmFkIHF1YWxpdHkgcGljdHVyZS4uLgoKWzFdIC0gaHR0cHM6Ly93d3cuZHJvcGJveC5jb20vc2Mvcjg5aHMyd2FsN2RwbjQ0L0FBQkNLcUp6QUI3RnpsSHVnZlV2UXJVdmEKCgoKT29wcywgc29ycnkuIFRoZSBjb3JyZWN0IGkBMAEBAQE- X-Mailer: YahooMailWebService/0.8.203.696 References: <1410382322.23950.YahooMailNeo@web162003.mail.bf1.yahoo.com> Message-ID: <1410382596.45838.YahooMailNeo@web162005.mail.bf1.yahoo.com> Date: Wed, 10 Sep 2014 13:56:36 -0700 From: Danilo Egea Reply-To: Danilo Egea Subject: Re: panic: run_interrupt_driven_config_hooks: waited to long on 10.1-PRERELEASE + RPI-B To: "freebsd-arm@freebsd.org" In-Reply-To: <1410382322.23950.YahooMailNeo@web162003.mail.bf1.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Sep 2014 21:00:00 -0000 Hi all,=0A=0A=0A=0A=0A=0A=0AI updated my system on raspberry to 10.0-PREREL= EASE (r271400) and now the system is stopping at this point [1].=0AThis is = a known problem?=0A=0ASorry the bad quality picture...=0A=0A[1] - https://w= ww.dropbox.com/sc/r89hs2wal7dpn44/AABCKqJzAB7FzlHugfUvQrUva=0A=0A=0A=0AOops= , sorry. The correct is 10.1-PRERELEASE, of course.=0A From owner-freebsd-arm@FreeBSD.ORG Wed Sep 10 21:04:55 2014 Return-Path: Delivered-To: freebsd-arm@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 49CA848A for ; Wed, 10 Sep 2014 21:04:55 +0000 (UTC) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 06AFEC92 for ; Wed, 10 Sep 2014 21:04:54 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 4CE941FE027; Wed, 10 Sep 2014 23:04:51 +0200 (CEST) Message-ID: <5410BCEA.8060100@selasky.org> Date: Wed, 10 Sep 2014 23:04:42 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Danilo Egea , "freebsd-arm@freebsd.org" Subject: Re: panic: run_interrupt_driven_config_hooks: waited to long on 10.1-PRERELEASE + RPI-B References: <1410382322.23950.YahooMailNeo@web162003.mail.bf1.yahoo.com> <1410382596.45838.YahooMailNeo@web162005.mail.bf1.yahoo.com> In-Reply-To: <1410382596.45838.YahooMailNeo@web162005.mail.bf1.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Sep 2014 21:04:55 -0000 On 09/10/14 22:56, Danilo Egea wrote: > Hi all, > > > > > > > I updated my system on raspberry to 10.0-PRERELEASE (r271400) and now the system is stopping at this point [1]. > This is a known problem? > > Sorry the bad quality picture... > > [1] - https://www.dropbox.com/sc/r89hs2wal7dpn44/AABCKqJzAB7FzlHugfUvQrUva > > > > Oops, sorry. The correct is 10.1-PRERELEASE, of course. Hi, What does "bt" say? --HPS From owner-freebsd-arm@FreeBSD.ORG Wed Sep 10 21:11:49 2014 Return-Path: Delivered-To: freebsd-arm@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 D00CC8B2 for ; Wed, 10 Sep 2014 21:11:49 +0000 (UTC) Received: from nm43-vm1.bullet.mail.bf1.yahoo.com (nm43-vm1.bullet.mail.bf1.yahoo.com [216.109.114.220]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7FACDD6C for ; Wed, 10 Sep 2014 21:11:48 +0000 (UTC) Received: from [66.196.81.172] by nm43.bullet.mail.bf1.yahoo.com with NNFMP; 10 Sep 2014 21:08:20 -0000 Received: from [98.139.212.213] by tm18.bullet.mail.bf1.yahoo.com with NNFMP; 10 Sep 2014 21:08:20 -0000 Received: from [127.0.0.1] by omp1022.mail.bf1.yahoo.com with NNFMP; 10 Sep 2014 21:08:19 -0000 X-Yahoo-Newman-Property: ymail-5 X-Yahoo-Newman-Id: 990768.38047.bm@omp1022.mail.bf1.yahoo.com Received: (qmail 63876 invoked by uid 60001); 10 Sep 2014 21:08:19 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com.br; s=s1024; t=1410383299; bh=omt5re7elK4Kj3LFldkJazTN4Z/ynpGzxHFfIizziTU=; h=References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=3BXUpeQ0rvhMaErFIKE5OLbHzOP+VR722DN2bU0JeiV8T3zwBDwgOOBsna0uCWVQOKiAPJ5QNSodbkmZnwhyVfAAD5wFoJ+w7ENMnYc+QiBYsp1q5Dhe3/8oFycD5H848IeJ3XdCwjifn69TsFUEfkpXWegRDTq1Gxwq5rX/0cs= X-YMail-OSG: Vtwic9AVM1mive_E_aQ9AEqUwCBJvHOtxX8NMM1pzNQO1dK QM6b6OCcHAoeOPrOd0OVEvB.ozyx2RjrX8W9E1Bh2aQMnnWCeV4gxt.Mk7NR qjPzHqLEnalp7LIEdfspfqq5lXNTc9gE53ekER4gJ3ercgQ9fc59CRNvnfou iHYcqlkzfaUElLK1pBBxXWRScNyhJLRjRenR11hH.pNnNDQCDVLHBeRyyxYf yb8ph6c6iURBaEROf6OW9sg7i0acXMvrFMexFdSEG.2FQDhJJzgQrWknQyFN tl088b.LNKVTyi494kUuIRXmp1..hybLSbYmHn3cj91.QldjrdH0YVJHPuK. 3dqNG.SRmOML1Zkj76QVLcItIo5i0hkkvkjE7rhiWho7ifu69enuBD1TO8X0 5e.DSQQG6HDd0seQuFgyYCE1KTwOjXVB3reLvFYaVVOmP_gt6t0Z6IQ6xlzs rTVKBpQ_8aDV217p32jfCfeCE3BI7Nbl.lyz7kv_zeIrklkEP.XGATSeR3wo 3De_5IRrZ8.YrF_DyDCHx.FaTwUlbnBVjabqeR64zSwy5foa00mjIKi9gTWk _2iHpKZA_fh.Uh5qj0jHZ4qd4kXoOrbi2CdYAZNtNde9LeO7hote6NdUyhyn kr0KG0TRrrd_BVLjPM57kBE0UhFdtK1DkzXaZlXcsKZ1OPpg0F3OzYczEMWj dmg-- Received: from [186.233.158.209] by web162004.mail.bf1.yahoo.com via HTTP; Wed, 10 Sep 2014 14:08:19 PDT X-Rocket-MIMEInfo: 002.001, T24gMDkvMTAvMTQgMjI6NTYsIERhbmlsbyBFZ2VhIHdyb3RlOgoKCgo.IEhpIGFsbCwKPgo.Cj4KPgo.Cj4KPiBJIHVwZGF0ZWQgbXkgc3lzdGVtIG9uIHJhc3BiZXJyeSB0byAxMC4wLVBSRVJFTEVBU0UgKHIyNzE0MDApIGFuZCBub3cgdGhlIHN5c3RlbSBpcyBzdG9wcGluZyBhdCB0aGlzIHBvaW50IFsxXS4KPiBUaGlzIGlzIGEga25vd24gcHJvYmxlbT8KPgo.IFNvcnJ5IHRoZSBiYWQgcXVhbGl0eSBwaWN0dXJlLi4uCj4KPiBbMV0gLSBodHRwczovL3d3dy5kcm9wYm94LmNvbS9zYy9yODloczJ3YWw3ZHABMAEBAQE- X-Mailer: YahooMailWebService/0.8.203.696 References: <1410382322.23950.YahooMailNeo@web162003.mail.bf1.yahoo.com> <1410382596.45838.YahooMailNeo@web162005.mail.bf1.yahoo.com> <5410BCEA.8060100@selasky.org> Message-ID: <1410383299.82284.YahooMailNeo@web162004.mail.bf1.yahoo.com> Date: Wed, 10 Sep 2014 14:08:19 -0700 From: Danilo Egea Reply-To: Danilo Egea Subject: Re: panic: run_interrupt_driven_config_hooks: waited to long on 10.1-PRERELEASE + RPI-B To: Hans Petter Selasky , "freebsd-arm@freebsd.org" In-Reply-To: <5410BCEA.8060100@selasky.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Sep 2014 21:11:49 -0000 On 09/10/14 22:56, Danilo Egea wrote:=0A=0A=0A=0A> Hi all,=0A>=0A>=0A>=0A>= =0A>=0A>=0A> I updated my system on raspberry to 10.0-PRERELEASE (r271400) = and now the system is stopping at this point [1].=0A> This is a known probl= em?=0A>=0A> Sorry the bad quality picture...=0A>=0A> [1] - https://www.drop= box.com/sc/r89hs2wal7dpn44/AABCKqJzAB7FzlHugfUvQrUva=0A>=0A>=0A>=0A> Oops, = sorry. The correct is 10.1-PRERELEASE, of course.=0A=0A=0AHi,=0A=0AWhat doe= s "bt" say?=0A=0A--HPS=0A=0AThis is another problem, the usb keyboard is no= t working at this point.=0A From owner-freebsd-arm@FreeBSD.ORG Wed Sep 10 21:20:00 2014 Return-Path: Delivered-To: arm@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 B6655CC6 for ; Wed, 10 Sep 2014 21:20:00 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 90D5BDC6 for ; Wed, 10 Sep 2014 21:20:00 +0000 (UTC) Received: from ralph.baldwin.cx (pool-173-70-85-31.nwrknj.fios.verizon.net [173.70.85.31]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 9C890B964 for ; Wed, 10 Sep 2014 17:19:59 -0400 (EDT) From: John Baldwin To: arm@freebsd.org Subject: NEW_PCIB and arm take 3 (4?) Date: Wed, 10 Sep 2014 17:19:55 -0400 Message-ID: <74248385.OR9iBtFISv@ralph.baldwin.cx> User-Agent: KMail/4.10.5 (FreeBSD/10.0-STABLE; KDE/4.10.5; amd64; ; ) MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Wed, 10 Sep 2014 17:19:59 -0400 (EDT) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Sep 2014 21:20:00 -0000 The plan for NEW_PCIB was for it to be a temporary option that would eventually become the default on all platforms. I have long had patches to provide the one step of infrastructure (namely implementing "real" bus_activate_resource methods) for various arm chipsets, but I haven't been able to get anyone to review or test them. I'm about at the point of just committing them in a week barring any specific reports from testers or reviewers. You can read more about what NEW_PCIB is at: https://wiki.freebsd.org/NEW_PCIB These patches aim to implement step 2 from that wiki page. However, I have no way to test them (and to be honest, I haven't recently tested to see if they will compile. I will ensure make universe passes before pushing them in if it comes down to that.) http://people.freebsd.org/~jhb/patches/arm_activate2.patch As I noted previously, I don't know how to properly fix i80321_pci in large part because I do not understand what it is doing. Warner had previously suggested just dropping it and if the consensus is to do that, I'd be much obliged for someone to make it so. -- John Baldwin From owner-freebsd-arm@FreeBSD.ORG Wed Sep 10 21:30:41 2014 Return-Path: Delivered-To: arm@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 C3124266; Wed, 10 Sep 2014 21:30:41 +0000 (UTC) Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "funkthat.com", Issuer "funkthat.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 86F85F36; Wed, 10 Sep 2014 21:30:40 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id s8ALUdkG041914 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 10 Sep 2014 14:30:39 -0700 (PDT) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id s8ALUdwT041913; Wed, 10 Sep 2014 14:30:39 -0700 (PDT) (envelope-from jmg) Date: Wed, 10 Sep 2014 14:30:39 -0700 From: John-Mark Gurney To: John Baldwin Subject: Re: NEW_PCIB and arm take 3 (4?) Message-ID: <20140910213039.GB82175@funkthat.com> Mail-Followup-To: John Baldwin , arm@freebsd.org References: <74248385.OR9iBtFISv@ralph.baldwin.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <74248385.OR9iBtFISv@ralph.baldwin.cx> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Wed, 10 Sep 2014 14:30:40 -0700 (PDT) Cc: arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Sep 2014 21:30:41 -0000 John Baldwin wrote this message on Wed, Sep 10, 2014 at 17:19 -0400: > The plan for NEW_PCIB was for it to be a temporary option that would > eventually become the default on all platforms. I have long had patches to > provide the one step of infrastructure (namely implementing "real" > bus_activate_resource methods) for various arm chipsets, but I haven't been > able to get anyone to review or test them. I'm about at the point of just > committing them in a week barring any specific reports from testers or > reviewers. > > You can read more about what NEW_PCIB is at: > > https://wiki.freebsd.org/NEW_PCIB > > These patches aim to implement step 2 from that wiki page. However, I have no > way to test them (and to be honest, I haven't recently tested to see if they > will compile. I will ensure make universe passes before pushing them in if it > comes down to that.) > > http://people.freebsd.org/~jhb/patches/arm_activate2.patch > > As I noted previously, I don't know how to properly fix i80321_pci in large > part because I do not understand what it is doing. Warner had previously > suggested just dropping it and if the consensus is to do that, I'd be much > obliged for someone to make it so. As before, I can test on AVILA (ixp425)... What's the best way to test the patch? Just apply, build, boot and verify that things come up sanely? If so, I'll have results for you soon.. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-arm@FreeBSD.ORG Thu Sep 11 06:51:17 2014 Return-Path: Delivered-To: arm@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 7E7C4596; Thu, 11 Sep 2014 06:51:17 +0000 (UTC) Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "funkthat.com", Issuer "funkthat.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3F5D37BA; Thu, 11 Sep 2014 06:51:16 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id s8B6pFUI048900 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 10 Sep 2014 23:51:15 -0700 (PDT) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id s8B6pE4W048899; Wed, 10 Sep 2014 23:51:14 -0700 (PDT) (envelope-from jmg) Date: Wed, 10 Sep 2014 23:51:14 -0700 From: John-Mark Gurney To: John Baldwin , arm@freebsd.org Subject: Re: NEW_PCIB and arm take 3 (4?) Message-ID: <20140911065114.GJ82175@funkthat.com> Mail-Followup-To: John Baldwin , arm@freebsd.org References: <74248385.OR9iBtFISv@ralph.baldwin.cx> <20140910213039.GB82175@funkthat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140910213039.GB82175@funkthat.com> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Wed, 10 Sep 2014 23:51:15 -0700 (PDT) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Sep 2014 06:51:17 -0000 John-Mark Gurney wrote this message on Wed, Sep 10, 2014 at 14:30 -0700: > John Baldwin wrote this message on Wed, Sep 10, 2014 at 17:19 -0400: > > The plan for NEW_PCIB was for it to be a temporary option that would > > eventually become the default on all platforms. I have long had patches to > > provide the one step of infrastructure (namely implementing "real" > > bus_activate_resource methods) for various arm chipsets, but I haven't been > > able to get anyone to review or test them. I'm about at the point of just > > committing them in a week barring any specific reports from testers or > > reviewers. > > > > You can read more about what NEW_PCIB is at: > > > > https://wiki.freebsd.org/NEW_PCIB > > > > These patches aim to implement step 2 from that wiki page. However, I have no > > way to test them (and to be honest, I haven't recently tested to see if they > > will compile. I will ensure make universe passes before pushing them in if it > > comes down to that.) > > > > http://people.freebsd.org/~jhb/patches/arm_activate2.patch > > > > As I noted previously, I don't know how to properly fix i80321_pci in large > > part because I do not understand what it is doing. Warner had previously > > suggested just dropping it and if the consensus is to do that, I'd be much > > obliged for someone to make it so. > > As before, I can test on AVILA (ixp425)... What's the best way to > test the patch? Just apply, build, boot and verify that things come > up sanely? > > If so, I'll have results for you soon.. Ok, tested, and my AVILA board comes up fine and see the ath board I have on it... $ pciconf -lv ath0@pci0:0:2:0: class=0x028000 card=0x2091168c chip=0x0029168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'AR922X Wireless Network Adapter' class = network -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-arm@FreeBSD.ORG Thu Sep 11 14:05:51 2014 Return-Path: Delivered-To: freebsd-arm@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 2FFB430D for ; Thu, 11 Sep 2014 14:05:51 +0000 (UTC) Received: from mho-01-ewr.mailhop.org (mho-03-ewr.mailhop.org [204.13.248.66]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 025B6FC6 for ; Thu, 11 Sep 2014 14:05:50 +0000 (UTC) Received: from [73.34.117.227] (helo=ilsoft.org) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1XS50J-000LhS-04; Thu, 11 Sep 2014 14:05:43 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id s8BE5fEq029103; Thu, 11 Sep 2014 08:05:41 -0600 (MDT) (envelope-from ian@FreeBSD.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 73.34.117.227 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1849CRc11dorh/3+SjDnnfU X-Authentication-Warning: paranoia.hippie.lan: Host revolution.hippie.lan [172.22.42.240] claimed to be [172.22.42.240] Subject: Re: panic: run_interrupt_driven_config_hooks: waited to long on 10.1-PRERELEASE + RPI-B From: Ian Lepore To: Danilo Egea In-Reply-To: <1410382322.23950.YahooMailNeo@web162003.mail.bf1.yahoo.com> References: <1410382322.23950.YahooMailNeo@web162003.mail.bf1.yahoo.com> Content-Type: text/plain; charset="us-ascii" Date: Thu, 11 Sep 2014 08:05:41 -0600 Message-ID: <1410444341.1150.439.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Sep 2014 14:05:51 -0000 On Wed, 2014-09-10 at 13:52 -0700, Danilo Egea wrote: > Hi all, > > I updated my system on raspberry to 10.0-PRERELEASE (r271400) and now the system is stopping at this point [1]. > This is a known problem? > > Sorry the bad quality picture... > > [1] - https://www.dropbox.com/sc/r89hs2wal7dpn44/AABCKqJzAB7FzlHugfUvQrUva I sync'd to the same stable-10 revision and built a fresh world and kernel and it boots fine. The big difference is that I don't use a video console, just serial. I don't know if that's a factor in why you see a hang or not. -- Ian From owner-freebsd-arm@FreeBSD.ORG Fri Sep 12 16:00:09 2014 Return-Path: Delivered-To: freebsd-arm@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 A44FA906 for ; Fri, 12 Sep 2014 16:00:09 +0000 (UTC) Received: from nm2-vm1.bullet.mail.bf1.yahoo.com (nm2-vm1.bullet.mail.bf1.yahoo.com [98.139.213.158]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4AD881E9 for ; Fri, 12 Sep 2014 16:00:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com.br; s=s2048; t=1410537602; bh=1K1tNlQk6OYOnYM8W439cnZZymdLO23+z2ctIo0zJSk=; h=Received:Received:Received:DKIM-Signature:X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:From:Subject; b=lpawOx+GCtGO1HvtH65lsBUw/vXeZT3VMXHihr7ujXqF88UUafAPG9QAD+ZYkOEetJw3Mt1En0zxUl/a0QJv8SDSvSMzgXQe0zVGIzGeewIeA3YxXpTuZ0v2ch/w20eN4VOZbUF2vK2eanmP3o08yX8GozIEhZ3ZiEFwXWGdOumOzYtmUGLCppPuYyqVuL71W5hyjut+7ZmSV/RA/NewMShLlSAV9aTPd+ciioUJmoRXPZ8HgiLCx5LkzAOCm2hqJXGsty/yoovpXmzJ9Lo4L0liJmgTsvsFc73K5+zWSCWlGuFuxRb5j6kUpZ9CCHCGvAi4yFuxJ9TGCr/uXWC+Ug== DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s2048; d=yahoo.com.br; b=fiRqfoTojFxclZd133GOJYA0M+aUnGAbdTXA39QON2TAz2Oh/wVSwomK97eKxKpPjiBiNXD/HMdh29a9BYF9XKOH0fOeMDYj85RZJT1wqbk0x0F76nwrmCCOTWyR0Xbkqduf6X5qaMhm5bSZU6B+aEeL5HPdr/5WCBdOTjOslIgIle4wvMOn3eu0UI8EWCNwjQII3ybPYLeX9iJwMnsQM2X6ePAxb222LxU4Lcy5CHUnYf+joFGlUaztI6uugUR+6c7VTThPMzlVZinbZXzcuL4dPmHt1FGLCPl2WuInDF2/1KNjT+t+3gcb+yrjPFKNRAB3sl1wIZa3OwusbbUITw==; Received: from [98.139.215.140] by nm2.bullet.mail.bf1.yahoo.com with NNFMP; 12 Sep 2014 16:00:02 -0000 Received: from [98.139.211.197] by tm11.bullet.mail.bf1.yahoo.com with NNFMP; 12 Sep 2014 16:00:02 -0000 Received: from [127.0.0.1] by smtp206.mail.bf1.yahoo.com with NNFMP; 12 Sep 2014 16:00:02 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com.br; s=s1024; t=1410537602; bh=1K1tNlQk6OYOnYM8W439cnZZymdLO23+z2ctIo0zJSk=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type; b=VV6whCyFZb8qzsSknn0TIMA3MYpuJLZx4CGe4aTqP1LxxqR/AbItIUvZ7UXRflPE0C/yZKB9chxhm1oZuSgKp0JTv5gcuGEV8JvtH4YAxwODsnH0waxzcOlrXJyh3gaPZKLclxkJYDHgh3P4+f08s4Bpb1QHB3+QUpNGmOFUI9s= X-Yahoo-Newman-Id: 422912.93115.bm@smtp206.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: 1GTxKj4VM1nJARn6KlpMP0EdYauG3e.WlcJCeOFeVj0fsxQ E9vRD1nVpSsWAiHzvg3Y3QHYgXfnVjK3eiXvIq8i5yzFwE53gGpLN5c2THRi PmzgbpJrQ0gI_sKijgS9zFJRwANxgH4U9sGEYUh2G20lIDuuQx2.VDruXhTM FUDNY9VJz9v5m9dLPboIkts1ZRQ4XevYVWiisCEv.YYLtBc983mF2DJwizo9 kQVDzZwFwa_emoQ396KJqTC5Lr0y9RAf009z9m3qLHlAKfAsJluvqm0dBQlx MfUDJpOewC.ovE20demBfqcqFIo7wld4l1ohv1fYbpIFyX6S7jnTC0X6D9M0 d6ws0Xk.G4TCypktY41FNjjXZ7A2DA93dAJKPD4U.3zYLXOxzGflORyzqp2d 1h0Sb8rAJu55IsK6ccck2OjVFesvdxsS6s3Q0lVUB715G3Z0Y.qCe3GSqzEp aChWiaLB6P5InR9kujDzptDHHE2Sn1R.z.j7rQpSLXyQzFqF2_qtY1YLQhAD ZAHf4enHdZXEg4vPJie4.DoZUyTvL9Hlm01nhXRl_3qzm2oINWHELkz1T.9N RkKIpmczMCbm1is.4wN7so82HuUbDLPLadG2qLBSl8muLBtuco876bzg9ySo 0SFeZ_NBU3IIWf0_Uflrj.U0tPfIQfIyvUp3DH4jVsWFGF.DAz.ll2tNlbaz fO_jw5Kr2cgFFGEje0dZH4TRARvtq3mMWyyNfNEMnMPUcx0g- X-Yahoo-SMTP: 51p0rh2swBCh3zxf6sJkNseoFwQzw1o- Message-ID: <54131929.10208@yahoo.com.br> Date: Fri, 12 Sep 2014 13:02:49 -0300 From: Danilo Egea Gondolfo User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: Ian Lepore Subject: Re: panic: run_interrupt_driven_config_hooks: waited to long on 10.1-PRERELEASE + RPI-B References: <1410382322.23950.YahooMailNeo@web162003.mail.bf1.yahoo.com> <1410444341.1150.439.camel@revolution.hippie.lan> In-Reply-To: <1410444341.1150.439.camel@revolution.hippie.lan> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Sep 2014 16:00:09 -0000 On 09/11/14 11:05, Ian Lepore wrote: > On Wed, 2014-09-10 at 13:52 -0700, Danilo Egea wrote: >> Hi all, >> >> I updated my system on raspberry to 10.0-PRERELEASE (r271400) and now the system is stopping at this point [1]. >> This is a known problem? >> >> Sorry the bad quality picture... >> >> [1] - https://www.dropbox.com/sc/r89hs2wal7dpn44/AABCKqJzAB7FzlHugfUvQrUva > I sync'd to the same stable-10 revision and built a fresh world and > kernel and it boots fine. The big difference is that I don't use a > video console, just serial. I don't know if that's a factor in why you > see a hang or not. > > -- Ian > > > Ok, now I have a serial cable. Now it's freezing and I can't run a "bt". I noticed these lines: "VT: initialize with new VT driver "fb". device_attach: fbd0 attach returned 6 fb0: Failed to attach fbd device" With other kernel config I got this bt: http://pastebin.com/FUVCwt7B Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel]... Using DTB provided by U-Boot at address 0x0x100. Kernel entry at 0x100100... Kernel args: (null) KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2014 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.1-BETA1 #0 r271466: Fri Sep 12 11:41:47 BRT 2014 root@danilo:/home/danilo/Mestrado/Sources/crochet-freebsd/work/obj/arm.armv6/home/danilo/Sources/freebsd-10-stable/sys/RPI-B arm FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512 VT: init without driver. CPU: ARM1176JZ-S rev 7 (ARM11J core) Supported features: ARM_ISA THUMB2 JAZELLE ARMv4 Security_Ext WB enabled LABT branch prediction enabled 16KB/32B 4-way instruction cache 16KB/32B 4-way write-back-locking-C data cache real memory = 536866816 (511 MB) avail memory = 482893824 (460 MB) random device not loaded; using insecure entropy random: initialized kbd0 at kbdmux0 ofwbus0: simplebus0: mem 0x20000000-0x20ffffff on ofwbus0 intc0: mem 0xb200-0xb3ff on simplebus0 systimer0: mem 0x3000-0x3fff irq 8,9,10,11 on simplebus0 Event timer "BCM2835 Event Timer 3" frequency 1000000 Hz quality 1000 Timecounter "BCM2835 Timecounter" frequency 1000000 Hz quality 1000 bcmwd0: mem 0x10001c-0x100027 on simplebus0 gpio0: mem 0x200000-0x2000af irq 57,59,58,60 on simplebus0 gpio0: read-only pins: 46,47,48,49,50,51,52,53. gpio0: reserved pins: 48,49,50,51,52,53. gpioc0: on gpio0 gpiobus0: on gpio0 gpioled0: at pin(s) 16 on gpiobus0 iichb0: mem 0x205000-0x20501f irq 61 on simplebus0 iicbus0: on iichb0 iic0: on iicbus0 iichb1: mem 0x804000-0x80401f irq 61 on simplebus0 iicbus1: on iichb1 iic1: on iicbus1 spi0: mem 0x204000-0x20401f irq 62 on simplebus0 spibus0: on spi0 bcm_dma0: mem 0x7000-0x7fff,0xe05000-0xe05fff irq 24,25,26,27,28,29,30,31,32,33,34,35,36 on simplebus0 mbox0: mem 0xb880-0xb8bf irq 1 on simplebus0 sdhci_bcm0: mem 0x300000-0x3000ff irq 70 on simplebus0 mmc0: on sdhci_bcm0 uart0: mem 0x201000-0x201fff irq 65 on simplebus0 uart0: console (115200,n,8,1) dwcotg0: mem 0x980000-0x99ffff irq 17 on simplebus0 usbus0 on dwcotg0 fb0: on ofwbus0 simplebus1: on ofwbus0 simplebus1: could not get ranges device_attach: simplebus1 attach returned 6 Timecounters tick every 10.000 msec usbus0: 480Mbps High Speed USB v2.0 ugen0.1: at usbus0 uhub0: on usbus0 mmcsd0: 4GB at mmc0 50.0MHz/4bit/65535-block fb0: 656x416(0x0@0,0) 16bpp fb0: pitch 1312, base 0x5e006000, screen_size 545792 fbd0 on fb0 VT: initialize with new VT driver "fb". device_attach: fbd0 attach returned 6 fb0: Failed to attach fbd device uhub0: 1 port with 1 removable, self powered ugen0.2: at usbus0 uhub1: on usbus0 uhub1: MTT enabled uhub1: 5 ports with 4 removable, self powered random: unblocking device. ugen0.3: at usbus0 smsc0: on usbus0 smsc0: chip 0xec00, rev. 0002 miibus0: on smsc0 ukphy0: PHY 1 on miibus0 ukphy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ue0: on smsc0 ue0: Ethernet address: b8:27:eb:60:d9:9b run_interrupt_driven_hooks: still waiting after 60 seconds for bcm_fb_init run_interrupt_driven_hooks: still waiting after 120 seconds for bcm_fb_init run_interrupt_driven_hooks: still waiting after 180 seconds for bcm_fb_init run_interrupt_driven_hooks: still waiting after 240 seconds for bcm_fb_init run_interrupt_driven_hooks: still waiting after 300 seconds for bcm_fb_init From owner-freebsd-arm@FreeBSD.ORG Fri Sep 12 20:35:12 2014 Return-Path: Delivered-To: arm@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 2F49B64B for ; Fri, 12 Sep 2014 20:35:12 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 07CC7632 for ; Fri, 12 Sep 2014 20:35:12 +0000 (UTC) Received: from ralph.baldwin.cx (pool-173-70-85-31.nwrknj.fios.verizon.net [173.70.85.31]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 68BCAB977; Fri, 12 Sep 2014 16:35:10 -0400 (EDT) From: John Baldwin To: John-Mark Gurney Subject: Re: NEW_PCIB and arm take 3 (4?) Date: Fri, 12 Sep 2014 16:34:36 -0400 Message-ID: <2090192.XxU5luGasi@ralph.baldwin.cx> User-Agent: KMail/4.10.5 (FreeBSD/10.0-STABLE; KDE/4.10.5; amd64; ; ) In-Reply-To: <20140911065114.GJ82175@funkthat.com> References: <74248385.OR9iBtFISv@ralph.baldwin.cx> <20140910213039.GB82175@funkthat.com> <20140911065114.GJ82175@funkthat.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Fri, 12 Sep 2014 16:35:10 -0400 (EDT) Cc: arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Sep 2014 20:35:12 -0000 On Wednesday, September 10, 2014 11:51:14 PM John-Mark Gurney wrote: > John-Mark Gurney wrote this message on Wed, Sep 10, 2014 at 14:30 -0700: > > John Baldwin wrote this message on Wed, Sep 10, 2014 at 17:19 -0400: > > > The plan for NEW_PCIB was for it to be a temporary option that would > > > eventually become the default on all platforms. I have long had patches > > > to > > > provide the one step of infrastructure (namely implementing "real" > > > bus_activate_resource methods) for various arm chipsets, but I haven't > > > been > > > able to get anyone to review or test them. I'm about at the point of > > > just > > > committing them in a week barring any specific reports from testers or > > > reviewers. > > > > > > You can read more about what NEW_PCIB is at: > > > https://wiki.freebsd.org/NEW_PCIB > > > > > > These patches aim to implement step 2 from that wiki page. However, I > > > have no way to test them (and to be honest, I haven't recently tested > > > to see if they will compile. I will ensure make universe passes before > > > pushing them in if it comes down to that.) > > > > > > http://people.freebsd.org/~jhb/patches/arm_activate2.patch > > > > > > As I noted previously, I don't know how to properly fix i80321_pci in > > > large > > > part because I do not understand what it is doing. Warner had > > > previously > > > suggested just dropping it and if the consensus is to do that, I'd be > > > much > > > obliged for someone to make it so. > > > > As before, I can test on AVILA (ixp425)... What's the best way to > > test the patch? Just apply, build, boot and verify that things come > > up sanely? > > > > If so, I'll have results for you soon.. > > Ok, tested, and my AVILA board comes up fine and see the ath board > I have on it... > > $ pciconf -lv > ath0@pci0:0:2:0: class=0x028000 card=0x2091168c chip=0x0029168c rev=0x01 > hdr=0x00 vendor = 'Atheros Communications Inc.' > device = 'AR922X Wireless Network Adapter' > class = network Perfect, thanks! -- John Baldwin From owner-freebsd-arm@FreeBSD.ORG Fri Sep 12 21:30:55 2014 Return-Path: Delivered-To: freebsd-arm@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 0C382938; Fri, 12 Sep 2014 21:30:55 +0000 (UTC) Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BFC8CC47; Fri, 12 Sep 2014 21:30:54 +0000 (UTC) Received: from [73.34.117.227] (helo=ilsoft.org) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1XSYQZ-0005IV-AI; Fri, 12 Sep 2014 21:30:47 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id s8CLUkRO032042; Fri, 12 Sep 2014 15:30:46 -0600 (MDT) (envelope-from ian@FreeBSD.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 73.34.117.227 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1+tE0+o+NsP2RiZzdKd+iJz X-Authentication-Warning: paranoia.hippie.lan: Host revolution.hippie.lan [172.22.42.240] claimed to be [172.22.42.240] Subject: Re: panic: run_interrupt_driven_config_hooks: waited to long on 10.1-PRERELEASE + RPI-B From: Ian Lepore To: Danilo Egea Gondolfo In-Reply-To: <54131929.10208@yahoo.com.br> References: <1410382322.23950.YahooMailNeo@web162003.mail.bf1.yahoo.com> <1410444341.1150.439.camel@revolution.hippie.lan> <54131929.10208@yahoo.com.br> Content-Type: text/plain; charset="us-ascii" Date: Fri, 12 Sep 2014 15:30:45 -0600 Message-ID: <1410557445.1150.473.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-arm@freebsd.org, Aleksandr Rybalko X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Sep 2014 21:30:55 -0000 On Fri, 2014-09-12 at 13:02 -0300, Danilo Egea Gondolfo wrote: > On 09/11/14 11:05, Ian Lepore wrote: > > On Wed, 2014-09-10 at 13:52 -0700, Danilo Egea wrote: > >> Hi all, > >> > >> I updated my system on raspberry to 10.0-PRERELEASE (r271400) and now the system is stopping at this point [1]. > >> This is a known problem? > >> > >> Sorry the bad quality picture... > >> > >> [1] - https://www.dropbox.com/sc/r89hs2wal7dpn44/AABCKqJzAB7FzlHugfUvQrUva > > I sync'd to the same stable-10 revision and built a fresh world and > > kernel and it boots fine. The big difference is that I don't use a > > video console, just serial. I don't know if that's a factor in why you > > see a hang or not. > > > > -- Ian > > > > > > > Ok, now I have a serial cable. > > Now it's freezing and I can't run a "bt". > > I noticed these lines: > "VT: initialize with new VT driver "fb". > device_attach: fbd0 attach returned 6 > fb0: Failed to attach fbd device" > > With other kernel config I got this bt: http://pastebin.com/FUVCwt7B > > Hit [Enter] to boot immediately, or any other key for command prompt. > Booting [/boot/kernel/kernel]... > Using DTB provided by U-Boot at address 0x0x100. > Kernel entry at 0x100100... > Kernel args: (null) > KDB: debugger backends: ddb > KDB: current backend: ddb > Copyright (c) 1992-2014 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 10.1-BETA1 #0 r271466: Fri Sep 12 11:41:47 BRT 2014 > root@danilo:/home/danilo/Mestrado/Sources/crochet-freebsd/work/obj/arm.armv6/home/danilo/Sources/freebsd-10-stable/sys/RPI-B > arm > FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512 > VT: init without driver. > CPU: ARM1176JZ-S rev 7 (ARM11J core) > Supported features: ARM_ISA THUMB2 JAZELLE ARMv4 Security_Ext > WB enabled LABT branch prediction enabled > 16KB/32B 4-way instruction cache > 16KB/32B 4-way write-back-locking-C data cache > real memory = 536866816 (511 MB) > avail memory = 482893824 (460 MB) > random device not loaded; using insecure entropy > random: initialized > kbd0 at kbdmux0 > ofwbus0: > simplebus0: mem 0x20000000-0x20ffffff > on ofwbus0 > intc0: mem 0xb200-0xb3ff on simplebus0 > systimer0: mem 0x3000-0x3fff irq 8,9,10,11 on > simplebus0 > Event timer "BCM2835 Event Timer 3" frequency 1000000 Hz quality 1000 > Timecounter "BCM2835 Timecounter" frequency 1000000 Hz quality 1000 > bcmwd0: mem 0x10001c-0x100027 on simplebus0 > gpio0: mem 0x200000-0x2000af irq > 57,59,58,60 on simplebus0 > gpio0: read-only pins: 46,47,48,49,50,51,52,53. > gpio0: reserved pins: 48,49,50,51,52,53. > gpioc0: on gpio0 > gpiobus0: on gpio0 > gpioled0: at pin(s) 16 on gpiobus0 > iichb0: mem 0x205000-0x20501f irq 61 on > simplebus0 > iicbus0: on iichb0 > iic0: on iicbus0 > iichb1: mem 0x804000-0x80401f irq 61 on > simplebus0 > iicbus1: on iichb1 > iic1: on iicbus1 > spi0: mem 0x204000-0x20401f irq 62 on > simplebus0 > spibus0: on spi0 > bcm_dma0: mem 0x7000-0x7fff,0xe05000-0xe05fff > irq 24,25,26,27,28,29,30,31,32,33,34,35,36 on simplebus0 > mbox0: mem 0xb880-0xb8bf irq 1 on simplebus0 > sdhci_bcm0: mem 0x300000-0x3000ff irq > 70 on simplebus0 > mmc0: on sdhci_bcm0 > uart0: mem 0x201000-0x201fff irq 65 on simplebus0 > uart0: console (115200,n,8,1) > dwcotg0: mem 0x980000-0x99ffff > irq 17 on simplebus0 > usbus0 on dwcotg0 > fb0: on ofwbus0 > simplebus1: on ofwbus0 > simplebus1: could not get ranges > device_attach: simplebus1 attach returned 6 > Timecounters tick every 10.000 msec > usbus0: 480Mbps High Speed USB v2.0 > ugen0.1: at usbus0 > uhub0: on usbus0 > mmcsd0: 4GB at mmc0 > 50.0MHz/4bit/65535-block > fb0: 656x416(0x0@0,0) 16bpp > fb0: pitch 1312, base 0x5e006000, screen_size 545792 > fbd0 on fb0 > VT: initialize with new VT driver "fb". > device_attach: fbd0 attach returned 6 > fb0: Failed to attach fbd device > uhub0: 1 port with 1 removable, self powered > ugen0.2: at usbus0 > uhub1: > on usbus0 > uhub1: MTT enabled > uhub1: 5 ports with 4 removable, self powered > random: unblocking device. > ugen0.3: at usbus0 > smsc0: on usbus0 > smsc0: chip 0xec00, rev. 0002 > miibus0: on smsc0 > ukphy0: PHY 1 on miibus0 > ukphy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > ue0: on smsc0 > ue0: Ethernet address: b8:27:eb:60:d9:9b > run_interrupt_driven_hooks: still waiting after 60 seconds for bcm_fb_init > run_interrupt_driven_hooks: still waiting after 120 seconds for bcm_fb_init > run_interrupt_driven_hooks: still waiting after 180 seconds for bcm_fb_init > run_interrupt_driven_hooks: still waiting after 240 seconds for bcm_fb_init > run_interrupt_driven_hooks: still waiting after 300 seconds for bcm_fb_init This looks like it's somehow related to the the frame buffer driver or the new vt(4) driver. I'm cc'ing Aleksander who knows more than I do about that stuff. :) -- Ian From owner-freebsd-arm@FreeBSD.ORG Fri Sep 12 23:05:00 2014 Return-Path: Delivered-To: freebsd-arm@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 347F2A0E for ; Fri, 12 Sep 2014 23:05:00 +0000 (UTC) Received: from nm46.bullet.mail.ne1.yahoo.com (nm46.bullet.mail.ne1.yahoo.com [98.138.120.53]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E5BA587E for ; Fri, 12 Sep 2014 23:04:59 +0000 (UTC) Received: from [127.0.0.1] by nm46.bullet.mail.ne1.yahoo.com with NNFMP; 12 Sep 2014 23:04:52 -0000 Received: from [98.138.101.132] by nm46.bullet.mail.ne1.yahoo.com with NNFMP; 12 Sep 2014 23:02:08 -0000 Received: from [98.138.89.245] by tm20.bullet.mail.ne1.yahoo.com with NNFMP; 12 Sep 2014 23:02:08 -0000 Received: from [127.0.0.1] by omp1059.mail.ne1.yahoo.com with NNFMP; 12 Sep 2014 23:02:08 -0000 X-Yahoo-Newman-Property: ymail-4 X-Yahoo-Newman-Id: 953601.85661.bm@omp1059.mail.ne1.yahoo.com Received: (qmail 55850 invoked by uid 60001); 12 Sep 2014 23:02:08 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1410562928; bh=t2NOtZJ6/zKQSdvXLfjDUHQsr0tA/sPRSXzWZ/Yd2oM=; h=Message-ID:Date:From:Subject:To:MIME-Version:Content-Type; b=cQr3pcXcD37zx8osIpskSftkOzNb2Na46P6trwXqFzgJaE7ceFnT3I5mXfAFP5bouvxixF0XvyhbupqgTt5Va6o66uMiJ8zpovtPGbpUqDmrct++9CbWb6JJOl18Zd7Rn7vPJyLnXnwi+WvsukaB7wNG6W9R+1lsmzHvvSVgh0o= X-YMail-OSG: cwVfxYsVM1kZcpErfMop.zphsUGEXbuJ3ZDGikgIUyZA1Ym a.VtuUqKsaTsrGBYvtkFYnoCoe2BSu3JG6BuSFWB2j_JgmhlJGH0HkX_PJU1 4JBhe3jaBgt2CVXxJmQoTmTw4RxuwkFGDMQdujD4s5XdGtQtwpVe6ywGsRlV uBuAJCceAfyUSb5Fk2WupFmBiXitKqqX7L0RSQnPn54K4kTUDTIOx6gO8Hq1 6cJdgNaTO4M_CAyr9A0J_SYBq4CRvbYcDz2BuMqIMTCLAKu_f3kV3T4erhhZ BF_60codXJD1co4VLUWS4zn7UIcGoDC0ZtqGV652jrnxCqxGZWfHu1qa8EFl _7qPCOfrjeO13x6y4p_CF9lDS942LeeNpw5UlsJZq4KQ38_9TvSMMgfDMYro BlK7KXOl9uDkEB31GOu.AAm58OceTprPhQBgw.l77i7I8SoanaSheLLRaNa8 nOFogFRbGKGUsqGRVGtE_FzvDg5USKkx29QJZtLZjM.0FMSjUJf5SIOBFD22 xZf64W44gPk4vflNmN0N_.ilUs43.w4UJWyvibZNpx4h0wKiuYeBthTtoJNf mInpgl4H35dImbFBL0nmZlibMwdvFSYw5q1VuSymvSqZdA_jN__G3zol5GOE JAd5PhYBu2WDktIBRt7STRP4jCz6x Received: from [64.26.171.99] by web122404.mail.ne1.yahoo.com via HTTP; Fri, 12 Sep 2014 16:02:08 PDT X-Rocket-MIMEInfo: 002.001, SGksDQoNCkkgYW0gd29uZGVyaW5nIGlmIHRoZSBzdGF0ZSBvZiBTRCBjYXJkIHN1cHBvcnQgb24gU2hlZXZhcGx1ZyBmb3IgRnJlZUJTRCBoYXMgc2VlbiBhbnkgY2hhbmdlcw0KbGF0ZWx5LiBUaGUgbGF0ZXN0IG5ld3MgSSBoYXZlIGlzIGZyb20gYSB5ZWFyIGFnbzoNCg0KaHR0cHM6Ly9mb3J1bXMuZnJlZWJzZC5vcmcvdmlld3RvcGljLnBocD8mdD00MTU5Mg0KDQpPciBpZiB0aGVyZSBhcmUgYW55IHdvcmthcm91bmQgdG8gbWFrZSBpdCB3b3JrLCBJJ2QgcmVhbGx5IGFwcHJlY2lhdGUgaXQuDQoNClRoYW4BMAEBAQE- X-Mailer: YahooMailClassic/735 YahooMailWebService/0.8.203.696 Message-ID: <1410562928.1909.YahooMailBasic@web122404.mail.ne1.yahoo.com> Date: Fri, 12 Sep 2014 16:02:08 -0700 From: Faraz Vahabzadeh Subject: SD card support on Sheevaplug To: freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Sep 2014 23:05:00 -0000 Hi, I am wondering if the state of SD card support on Sheevaplug for FreeBSD has seen any changes lately. The latest news I have is from a year ago: https://forums.freebsd.org/viewtopic.php?&t=41592 Or if there are any workaround to make it work, I'd really appreciate it. Thanks, Raz From owner-freebsd-arm@FreeBSD.ORG Sat Sep 13 15:10:42 2014 Return-Path: Delivered-To: freebsd-arm@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 E238F873 for ; Sat, 13 Sep 2014 15:10:42 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C292B1D4 for ; Sat, 13 Sep 2014 15:10:42 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s8DFAgEo069432 for ; Sat, 13 Sep 2014 15:10:42 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 193608] New: cubieboard2: kernel crash on disconnect/connect serial console Date: Sat, 13 Sep 2014 15:10:42 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: che@bein.link X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Sep 2014 15:10:43 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193608 Bug ID: 193608 Summary: cubieboard2: kernel crash on disconnect/connect serial console Product: Base System Version: 11.0-CURRENT Hardware: arm OS: Any Status: Needs Triage Severity: Affects Only Me Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: che@bein.link Using my cubieboard2, I disconnected serial and connected it back. Here's what I got: [19:07:28] ]che@quad:~[$ sudo cu -s 115200 -l /dev/ttyU0 Connected FreeBSD/arm (cubie) (ttyu0) login: ~ [EOT] [19:07:33] ]che@quad:~[$ sudo cu -s 115200 -l /dev/ttyU0 /dev/ttyU0: No such file or directory link down [19:07:44] ]che@quad:~[$ sudo cu -s 115200 -l /dev/ttyU0 Connected Bad character in number KDB: reentering KDB: stack backtrace: db_trace_self() at db_trace_self pc = 0xc0509f5c lr = 0xc02347dc (X_db_symbol_values+0x11c) sp = 0xebbd68b8 fp = 0xebbd69d0 r10 = 0xc0639aa4 X_db_symbol_values() at X_db_symbol_values+0x11c pc = 0xc02347dc lr = 0xc0371188 (kdb_reenter+0x60) sp = 0xebbd69d8 fp = 0xebbd69e0 r4 = 0xc0639ac0 r5 = 0xc0639aa4 r6 = 0x00000008 r7 = 0x00000009 kdb_reenter() at kdb_reenter+0x60 pc = 0xc0371188 lr = 0xc0232394 (db_error+0x24) sp = 0xebbd69e8 fp = 0xebbd69e8 r4 = 0x00000069 r5 = 0xc06276f0 db_error() at db_error+0x24 pc = 0xc0232394 lr = 0xc0234194 (db_read_token+0x230) sp = 0xebbd69f0 fp = 0xebbd6a08 db_read_token() at db_read_token+0x230 pc = 0xc0234194 lr = 0xc0231f88 (db_command_loop+0xa0) sp = 0xebbd6a10 fp = 0xebbd6ab0 r4 = 0xc0546bcc r5 = 0xc0563b71 r6 = 0xc08de1a8 r7 = 0xebbd6c98 r8 = 0x00000001 r9 = 0xc05f8688 db_command_loop() at db_command_loop+0xa0 pc = 0xc0231f88 lr = 0xc0231f48 (db_command_loop+0x60) sp = 0xebbd6ab8 fp = 0xebbd6ac8 r4 = 0xc0546bcc r5 = 0xc0563b71 r6 = 0xc08de1a8 r7 = 0xebbd6c98 r8 = 0x00000001 r9 = 0xc05f8688 r10 = 0xc0639aa4 db_command_loop() at db_command_loop+0x60 pc = 0xc0231f48 lr = 0xc0234910 (X_db_symbol_values+0x250) sp = 0xebbd6ad0 fp = 0xebbd6bf0 r4 = 0x00000000 r5 = 0xc08de1b4 r6 = 0xc0639ac8 X_db_symbol_values() at X_db_symbol_values+0x250 pc = 0xc0234910 lr = 0xc0371580 (kdb_trap+0x15c) sp = 0xebbd6bf8 fp = 0xebbd6c18 r4 = 0x00000000 r5 = 0x00000001 r6 = 0xc0639ac8 r7 = 0xebbd6c98 kdb_trap() at kdb_trap+0x15c pc = 0xc0371580 lr = 0xc0520aa0 (undefinedinstruction+0x2c4) sp = 0xebbd6c20 fp = 0xebbd6c90 r4 = 0x00000000 r5 = 0x00000000 r6 = 0xc052072c r7 = 0xe7ffffff r8 = 0xc3a86960 r9 = 0xc0370c70 r10 = 0xebbd6c98 undefinedinstruction() at undefinedinstruction+0x2c4 pc = 0xc0520aa0 lr = 0xc050bc44 (exception_exit) sp = 0xebbd6c98 fp = 0xebbd6cf0 r4 = 0x00000001 r5 = 0xebbd6d80 r6 = 0xc391b174 r7 = 0x00060000 r8 = 0x00000001 r9 = 0xc05fc588 r10 = 0xc391b000 exception_exit() at exception_exit pc = 0xc050bc44 lr = 0xc0370c60 (kdb_break+0x50) sp = 0xebbd6ce8 fp = 0xebbd6cf0 r0 = 0xc0639ab4 r1 = 0x00000000 r2 = 0x00000001 r3 = 0x60000193 r4 = 0x00000001 r5 = 0xebbd6d80 r6 = 0xc391b174 r7 = 0x00060000 r8 = 0x00000001 r9 = 0xc05fc588 r10 = 0xc391b000 r12 = 0x00000000 kdb_break() at kdb_break+0x64 pc = 0xc0370c74 lr = 0xc026379c (uart_bus_attach+0x608) sp = 0xebbd6cf8 fp = 0xebbd6d38 r4 = 0x00000000 uart_bus_attach() at uart_bus_attach+0x608 pc = 0xc026379c lr = 0xc03093d4 (intr_event_handle+0x7c) sp = 0xebbd6d40 fp = 0xebbd6d60 r4 = 0xc3959100 r5 = 0xebbd6d80 r6 = 0xc08e784c r7 = 0xc3a86960 r8 = 0x00000000 r9 = 0xc055da58 r10 = 0xc3b14180 intr_event_handle() at intr_event_handle+0x7c pc = 0xc03093d4 lr = 0xc050d0f4 (arm_irq_handler+0x60) sp = 0xebbd6d68 fp = 0xebbd6d78 r4 = 0xebbd6d80 r5 = 0x00000021 r6 = 0xc08e784c r7 = 0xc08daa4c r8 = 0x0000055a r9 = 0x00000000 r10 = 0xc055d92e arm_irq_handler() at arm_irq_handler+0x60 pc = 0xc050d0f4 lr = 0xc050bc44 (exception_exit) sp = 0xebbd6d80 fp = 0xebbd6dd8 r4 = 0xc3a86960 r5 = 0xc0638e14 r6 = 0x00000000 r7 = 0xc055d92e exception_exit() at exception_exit pc = 0xc050bc44 lr = 0xc050d8d4 (spinlock_exit+0x14) sp = 0xebbd6dd0 fp = 0xebbd6dd8 r0 = 0x00000000 r1 = 0x000000c0 r2 = 0x600001d3 r3 = 0x60000113 r4 = 0xc3a86960 r5 = 0xc0638e14 r6 = 0x00000000 r7 = 0xc055d92e r8 = 0x0000055a r9 = 0x00000000 r10 = 0xc055d92e r12 = 0x00000000 spinlock_exit() at spinlock_exit+0x40 pc = 0xc050d900 lr = 0xc03243ec (__mtx_unlock_spin_flags+0xd4) sp = 0xebbd6de0 fp = 0xebbd6df8 r4 = 0xc0638e24 __mtx_unlock_spin_flags() at __mtx_unlock_spin_flags+0xd4 pc = 0xc03243ec lr = 0xc0309d20 (db_dump_intr_event+0x864) sp = 0xebbd6e00 fp = 0xebbd6e38 r4 = 0xc3910f70 r5 = 0xc3a86960 r6 = 0xc3959b00 r7 = 0xc0608c20 r8 = 0xc08df1f0 db_dump_intr_event() at db_dump_intr_event+0x864 pc = 0xc0309d20 lr = 0xc0306b04 (fork_exit+0xa0) sp = 0xebbd6e40 fp = 0xebbd6e58 r4 = 0xc3a86960 r5 = 0xc3a84000 r6 = 0xc0309b28 r7 = 0xc3910f70 r8 = 0xebbd6e60 r9 = 0x00000000 r10 = 0x00000000 fork_exit() at fork_exit+0xa0 pc = 0xc0306b04 lr = 0xc050bbd4 (swi_exit) sp = 0xebbd6e60 fp = 0x00000000 r4 = 0xc0309b28 r5 = 0xc3910f70 r6 = 0x00000000 r7 = 0x00000000 r8 = 0x00000000 swi_exit() at swi_exit pc = 0xc050bbd4 lr = 0xc050bbd4 (swi_exit) sp = 0xebbd6e60 fp = 0x00000000 Unable to unwind further db> -- You are receiving this mail because: You are the assignee for the bug.