15-march.img hangs at boot on BB-Green

[Nicola Mingotti]

-----

The only other useful info I have so far is that this only happens with
the GENERIC kernel. If you build a kernel using the BEAGLEBONE config
it boots normally.

------

Ian, I found this reference to achieve what you say:
http://blog.khubla.com/freebsd/building-a-beaglebone-freebsd-kernel

Can you tell me if it is still valid, post is from 2013.

And I see in that webpage ARCH is set to "armv6", instead on the imges 
filenames
I download usually for BeagleBone I read "armv7".  e.g.
FreeBSD-12.0-CURRENT-arm-armv7-BEAGLEBONE-20180315-r331001.img

Then, I do not understand one point, this image i am using now:
FreeBSD-12.0-CURRENT-arm-armv7-BEAGLEBONE-20180315-r331001.img
has a GENERIC kernel or it has the BEAGLEBONE config ?

bye
Nicola









On 03/19/18 23:53, Ian Lepore wrote:
> On Mon, 2018-03-19 at 10:53 +0100, Nicola Mingotti wrote:
>> Hi,
>>
>> With latest 15-March img relase I am able to boot on BeagleBone Green
>> but still, the boot precess hangs at this point, it seems Ethernet related.
>>
>> ------------------------ last messages I see on serial console
>> ----------------------
>> cpswss0: <3-port Switch Ethernet Subsystem> mem
>> 0x4a100000-0x4a1007ff,0x4a101200-0x4a1012ff irq 38,39,40,41 on simplebus0
>> cpswss0: CPSW SS Version 1.12 (0)
>> cpswss0: Initial queue size TX=128 RX=384
>> cpswss0: Unable to fill RX queue
>> cpsw0:  on cpswss0
>> --------------------------------------------------------------------------------------------------
>>
>> Bye
>> Nicola
> Today I finally found some time to do some testing with this. It
> appears to have broken with r328916 on Feb 6. From then through r328981
> the kernel page faults early in boot. Starting with r328982 the fault
> is fixed but we get this new problem with the "Unable to fill RX queue"
> followed by a hang. The "unable to fill" is caused by an
> m_getcl(M_NOWAIT) returning NULL. The hang is caused by a
> malloc(M_WAITOK) in if_alloc() hanging forever.
>
> The only other useful info I have so far is that this only happens with
> the GENERIC kernel. If you build a kernel using the BEAGLEBONE config
> it boots normally.
>
> I don't really know what to do next to debug further. I can insert a
> kdb_enter() right before the if_alloc() call that hangs, but I don't
> know what to look for in the debugger.
>
> -- Ian
>

-- 
--------------------------
Dr. Nicola Mingotti
R&D - Borghi Srl
CTO - BondInsider
--------------------------