panic: run_interrupt_driven_config_hooks: waited to long on 10.1-PRERELEASE + RPI-B

Thu Sep 18 14:18:25 UTC 2014

On 09/12/14 18:30, Ian Lepore wrote:
> 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 at 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: <Software, Yarrow> initialized
>> kbd0 at kbdmux0
>> ofwbus0: <Open Firmware Device Tree>
>> simplebus0: <Flattened device tree simple bus> mem 0x20000000-0x20ffffff
>> on ofwbus0
>> intc0: <BCM2835 Interrupt Controller> mem 0xb200-0xb3ff on simplebus0
>> systimer0: <BCM2835 System Timer> 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: <BCM2708/2835 Watchdog> mem 0x10001c-0x100027 on simplebus0
>> gpio0: <BCM2708/2835 GPIO controller> 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: <GPIO controller> on gpio0
>> gpiobus0: <OFW GPIO bus> on gpio0
>> gpioled0: <GPIO led> at pin(s) 16 on gpiobus0
>> iichb0: <BCM2708/2835 BSC controller> mem 0x205000-0x20501f irq 61 on
>> simplebus0
>> iicbus0: <OFW I2C bus> on iichb0
>> iic0: <I2C generic I/O> on iicbus0
>> iichb1: <BCM2708/2835 BSC controller> mem 0x804000-0x80401f irq 61 on
>> simplebus0
>> iicbus1: <OFW I2C bus> on iichb1
>> iic1: <I2C generic I/O> on iicbus1
>> spi0: <BCM2708/2835 SPI controller> mem 0x204000-0x20401f irq 62 on
>> simplebus0
>> spibus0: <OFW SPI bus> on spi0
>> bcm_dma0: <BCM2835 DMA Controller> mem 0x7000-0x7fff,0xe05000-0xe05fff
>> irq 24,25,26,27,28,29,30,31,32,33,34,35,36 on simplebus0
>> mbox0: <BCM2835 VideoCore Mailbox> mem 0xb880-0xb8bf irq 1 on simplebus0
>> sdhci_bcm0: <Broadcom 2708 SDHCI controller> mem 0x300000-0x3000ff irq
>> 70 on simplebus0
>> mmc0: <MMC/SD bus> on sdhci_bcm0
>> uart0: <PrimeCell UART (PL011)> mem 0x201000-0x201fff irq 65 on simplebus0
>> uart0: console (115200,n,8,1)
>> dwcotg0: <DWC OTG 2.0 integrated USB controller> mem 0x980000-0x99ffff
>> irq 17 on simplebus0
>> usbus0 on dwcotg0
>> fb0: <BCM2835 VT framebuffer driver> on ofwbus0
>> simplebus1: <Flattened device tree simple bus> 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: <DWCOTG> at usbus0
>> uhub0: <DWCOTG OTG Root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus0
>> mmcsd0: 4GB <SDHC SA04G 1.0 SN 1A93CC12 MFG 07/2012 by 2 TM> at mmc0
>> 50.0MHz/4bit/65535-block
>> fb0: 656x416(0x0 at 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: <vendor 0x0424> at usbus0
>> uhub1: <vendor 0x0424 product 0x9514, class 9/0, rev 2.00/2.00, addr 2>
>> on usbus0
>> uhub1: MTT enabled
>> uhub1: 5 ports with 4 removable, self powered
>> random: unblocking device.
>> ugen0.3: <vendor 0x0424> at usbus0
>> smsc0: <vendor 0x0424 product 0xec00, rev 2.00/2.00, addr 3> on usbus0
>> smsc0: chip 0xec00, rev. 0002
>> miibus0: <MII bus> on smsc0
>> ukphy0: <Generic IEEE 802.3u media interface> PHY 1 on miibus0
>> ukphy0:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
>> ue0: <USB Ethernet> 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
>
>
>
Hello again,

The last snapshot of 10.1 has the same problem. Just to make sure, I'll 
test it with another raspberry later.

Here is the complete boot log http://pastebin.com/SEX64FNv

I'd like to highlight this (again):

VT: initialize with new VT driver "fb".
device_attach: fbd0 attach returned 6
fb0: Failed to attach fbd device

and this (in the backtrace):

undefinedinstruction() at undefinedinstruction+0x298
          pc = 0xc04a8300  lr = 0xc0496684 (exception_exit)
          sp = 0xc075ed50  fp = 0xc075eda8
          r4 = 0xc04eebec  r5 = 0xc075edfc
          r6 = 0xc04f11f2  r7 = 0xc064a100
          r8 = 0xc06625e0  r9 = 0xc06630c0
         r10 = 0xc0649f60

Maybe this problem is related to the compiler?

Thanks!