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