Re: invisible.ca/arm

[Jared McNeill <jmcneill%invisible.ca@localhost>]

Thanks! I see the same panic on armv7, I’ll add this to my list.

> On Feb 19, 2018, at 5:35 PM, Andreas Drewke <andreas%drewke.net@localhost> wrote:
> 
> Hi,
> 
> I got it. Just used another camera that was able to record more than 30FPS.
> 
> The panic sais:
> 	panic: kernel diagnostic „then <= now“ failed: file „Users/jmcneill/netbsd/rpi64wip/sys/arch/arm/cortex/gimr.c“, line 314 -IBIG (not sure about IBIG or 1816 or l916)
> 	Mutex error: mutex_vector_enter.519: assertion failed: !cpu_intr_p()
> 
> I guess thats enough, if something is missing I can provide the frame from the video as well.
> 
> I am super curious when it will be fixed.
> 
> Best regards
> Andreas
> 
>> Am 19.02.2018 um 21:58 schrieb Andreas Drewke <andreas%drewke.net@localhost>:
>> 
>> Hi Jared,
>> 
>> thank you very much! I will try if I have time again. Latest on next sunday.
>> 
>> Best regards
>> Andreas
>> 
>> 
>> Am 19.02.2018 um 13:51 schrieb Jared McNeill:
>>> I eventually saw a similar crash after ~6 hrs of heavy load.
>>> 
>>> Probably the easiest way to capture the message is to modify the code that prints “Skipping crash dump on recursive panic” and add an infinite loop after it.
>>> 
>>> Build tools and a kernel from this tree (rpi64wip branch): https://github.com/ryo/netbsd-src
>>> 
>>> Add the loop here: https://nxr.netbsd.org/xref/src/sys/kern/subr_prf.c#306
>>> 
>>> Cheers,
>>> Jared
>>> 
>>> 
>>>> On Feb 19, 2018, at 5:33 AM, Andreas Drewke <andreas%drewke.net@localhost <mailto:andreas%drewke.net@localhost>> wrote:
>>>> 
>>>> Hi,
>>>> 
>>>> I have again the same error when having the WIFI dongle connected.
>>>> I ve just tried again to capture it. Its not working with video cam. When screen starts scrolling due to the error messages nothing is readable on screen.
>>>> 
>>>> I am sorry. Is there maybe another way to get that message?
>>>> 
>>>> Best regards
>>>> Andreas
>>>> 
>>>>> Am 19.02.2018 um 00:13 schrieb Andreas Drewke <andreas%drewke.net@localhost <mailto:andreas%drewke.net@localhost>>:
>>>>> 
>>>>> Hi,
>>>>> 
>>>>>> Only one CPU supported so far. The arm64 code is still new, give it time :)
>>>>> Ahhhh. No worries. Sorry. I did not knew that. I have time.
>>>>> 
>>>>>> I’m using a USB wifi adapter:
>>>>> Nice. I will try mine now too. Maybe the error disappears.
>>>>> 
>>>>> I can of course try to catch that error message I am experiencing with that ethernet dongle. But can take some time too.
>>>>> 
>>>>> Can I anywhere read about progress of ARM64 port in future? I would like to be kept updated about this NetBSD-arm64@PineBook thing.
>>>>> Any try images from time to time.
>>>>> 
>>>>> Best regards
>>>>> Andreas
>>>>> 
>>>>>> Am 19.02.2018 um 00:07 schrieb Jared McNeill <jmcneill%invisible.ca@localhost <mailto:jmcneill%invisible.ca@localhost>>:
>>>>>> 
>>>>>> Only one CPU supported so far. The arm64 code is still new, give it time :)
>>>>>> 
>>>>>> I’m using a USB wifi adapter:
>>>>>> 
>>>>>> urtwn0 at uhub4 port 2
>>>>>> urtwn0: Realtek (0x7392) 802.11n WLAN Adapter (0x7811), rev 2.00/2.00, addr 4
>>>>>> urtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R, address 80:1f:02:94:40:12
>>>>>> urtwn0: 1 rx pipe, 2 tx pipes
>>>>>> urtwn0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
>>>>>> urtwn0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>>> On Feb 18, 2018, at 7:05 PM, Andreas Drewke <andreas%drewke.net@localhost <mailto:andreas%drewke.net@localhost>> wrote:
>>>>>>> 
>>>>>>> Hi,
>>>>>>> 
>>>>>>> Now it does not crash anymore.
>>>>>>> But looks like it booted with 1 CPU only.
>>>>>>> 
>>>>>>> "sysctl -a | grep cpu“ shows not 4 and „top“ always show "1 on CPU“. Hmm.
>>>>>>> 
>>>>>>> How can I safely find out how many CPUs are in use?
>>>>>>> 
>>>>>>> Now it crashed again after plug in my USB ethernet dongle after 15 minutes. I will try a different USB device. I have a WIFI dongle here. Maybe its related to that ethernet dongle.
>>>>>>> VIdeo was running but blurred to much. Could not read anything. Will try again.
>>>>>>> 
>>>>>>> Ill keep you updated.
>>>>>>> 
>>>>>>> How do you gain access to the internet from your pinebook?
>>>>>>> 
>>>>>>> Best regards
>>>>>>> Andreas
>>>>>>> 
>>>>>>>> Am 18.02.2018 um 23:18 schrieb Andreas Drewke <andreas%drewke.net@localhost <mailto:andreas%drewke.net@localhost>>:
>>>>>>>> 
>>>>>>>> Hi,
>>>>>>>> 
>>>>>>>>> Did it get stuck in that loop with ddb.onpanic=1 ?
>>>>>>>> Yes. I enabled that.
>>>>>>>> 
>>>>>>>>> No X server yet. It seems it’s not enabled in the build, and I just learned today that I can’t build xsrc from macOS. I’ll fix it but I need to setup a build environment w/ case sensitive FS first.
>>>>>>>> Having a X server running would be really nice.
>>>>>>>> 
>>>>>>>> Best regards
>>>>>>>> Andreas
>>>>>>>> 
>>>>>>>>> Am 18.02.2018 um 23:16 schrieb Jared McNeill <jmcneill%invisible.ca@localhost <mailto:jmcneill%invisible.ca@localhost>>:
>>>>>>>>> 
>>>>>>>>> Did it get stuck in that loop with ddb.onpanic=1 ?
>>>>>>>>> 
>>>>>>>>> Mine has a urtwn(4) plugged in, and I flipped the “enable UART on headphone jack” switch inside, but no other changes apart from that. It’s a 14” model FWIW.
>>>>>>>>> 
>>>>>>>>> No X server yet. It seems it’s not enabled in the build, and I just learned today that I can’t build xsrc from macOS. I’ll fix it but I need to setup a build environment w/ case sensitive FS first.
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>>> On Feb 18, 2018, at 6:12 PM, Andreas Drewke <andreas%drewke.net@localhost <mailto:andreas%drewke.net@localhost>> wrote:
>>>>>>>>>> 
>>>>>>>>>> Hi,
>>>>>>>>>> 
>>>>>>>>>>> Do you have any extra devices plugged in? Using the original AC adapter?
>>>>>>>>>> Original AC adapter, nothing plugged in.
>>>>>>>>>> 
>>>>>>>>>>> Looks like it’s stuck in a loop there. Any way you can capture the first message printed?
>>>>>>>>>> I can try to make a video then I can jump to the frame that shows first message. Will be some work. But I can try. Give me an hour.
>>>>>>>>>> 
>>>>>>>>>>> Mine has been running for ~3 hrs on an arm64 kernel extracting pkgsrc, no panics yet..
>>>>>>>>>> Sounds nice.
>>>>>>>>>> 
>>>>>>>>>> Will a XServer be running? Or does it require some extra work?
>>>>>>>>>> 
>>>>>>>>>> Best regards
>>>>>>>>>> Andeas
>>>>>>>>>> 
>>>>>>>>>>> Am 18.02.2018 um 23:05 schrieb Jared McNeill <jmcneill%invisible.ca@localhost <mailto:jmcneill%invisible.ca@localhost>>:
>>>>>>>>>>> 
>>>>>>>>>>> Looks like it’s stuck in a loop there. Any way you can capture the first message printed?
>>>>>>>>>>> 
>>>>>>>>>>> Do you have any extra devices plugged in? Using the original AC adapter?
>>>>>>>>>>> 
>>>>>>>>>>> Mine has been running for ~3 hrs on an arm64 kernel extracting pkgsrc, no panics yet..
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>>> On Feb 18, 2018, at 5:15 PM, Andreas Drewke <andreas%drewke.net@localhost <mailto:andreas%drewke.net@localhost>> wrote:
>>>>>>>>>>>> 
>>>>>>>>>>>> Hi,
>>>>>>>>>>>> 
>>>>>>>>>>>> It boots!!! Looks nice.
>>>>>>>>>>>> 
>>>>>>>>>>>> But it crashes after 2 mins. Please see attached a photo. Please keep me updated somehow. I am willing to try new builds of course. If I can help just tell me.
>>>>>>>>>>>> 
>>>>>>>>>>>> <IMG_20180218_221138163.jpg>
>>>>>>>>>>>> 
>>>>>>>>>>>> Best regards
>>>>>>>>>>>> Andreas
>>>>>>>>>>>> 
>>>>>>>>>>>>> Am 18.02.2018 um 22:09 schrieb Jared McNeill <jmcneill%invisible.ca@localhost <mailto:jmcneill%invisible.ca@localhost>>:
>>>>>>>>>>>>> 
>>>>>>>>>>>>> I seem to have better luck when it is plugged in to AC. You can try holding the power button for a bit (I think the light patterns change) to reset the management processor as well.
>>>>>>>>>>>>> 
>>>>>>>>>>>>>> On Feb 18, 2018, at 5:07 PM, Andreas Drewke <andreas%drewke.net@localhost <mailto:andreas%drewke.net@localhost>> wrote:
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> Hi Jared,
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> Just did that. My PineBook is kidding me now. It does just not enable the display for an half an hour now.
>>>>>>>>>>>>>> Any hint how to trick the PineBook to boot the display??? :DDD
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> Best regards
>>>>>>>>>>>>>> Andreas
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> Am 18.02.2018 um 21:41 schrieb Jared McNeill <jmcneill%invisible.ca@localhost <mailto:jmcneill%invisible.ca@localhost>>:
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> Arg, wrong dtb on that image. The fixed dts is in head but not the branch that contains arm64 support.
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> Please replace dtb/allwinner/sun50i-a64-pinebook.dtb on the MSDOS partition with the attached one and let me know if it works.
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> Cheers,
>>>>>>>>>>>>>>> Jared
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> <sun50i-a64-pinebook.dtb>
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> On Feb 18, 2018, at 4:13 PM, Andreas Drewke <andreas%drewke.net@localhost <mailto:andreas%drewke.net@localhost>> wrote:
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> In /etc/sysctl.conf change ddb.onpanic to 1 and reboot.. bad default imho. Next time it crashes it should drop you to a debugger instead of rebooting.
>>>>>>>>>>>>>>>> I will try that.
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> NetBSD arm64@pinebook does boot but shows pixel garbage. I have a video if you are interested.
>>>>>>>>>>>>>>>> Damn.
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> Best regards
>>>>>>>>>>>>>>>> Andreas
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> Am 18.02.2018 um 21:03 schrieb Andreas Drewke <andreas%drewke.net@localhost <mailto:andreas%drewke.net@localhost>>:
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> I will test now if new build still crashes a) with USB hub attached b) or not and report here.
>>>>>>>>>>>>>>>>> Current build of NetBSD arm32@PineBook crashes here after 15 minutes uptime without having USB devices attached. Again without any messages.
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> I will try now the arm64 build.
>>>>>>>>>>>>>>>>> I am super curious.
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> Best regards
>>>>>>>>>>>>>>>>> Andreas
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> Am 18.02.2018 um 20:50 schrieb Andreas Drewke <andreas%drewke.net@localhost <mailto:andreas%drewke.net@localhost>>:
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> Hi Jared,
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> I’ll start doing board specific images once arm64 support is merged into CVS and the auto build servers start generating builds. I don’t think think this is very far off.
>>>>>>>>>>>>>>>>>> That is amazing.
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> I’ll send you a build to try in the meantime.
>>>>>>>>>>>>>>>>>> That is even more amazing.
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> I will test now if new build still crashes a) with USB hub attached b) or not and report here.
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> One question: Are ARM32 packages available somewhere? I do not read anymore about it on http://invisible <http://invisible/>.ca/arm
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> Best regards
>>>>>>>>>>>>>>>>>> Andreas
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> Am 18.02.2018 um 20:31 schrieb Jared McNeill <jmcneill%invisible.ca@localhost <mailto:jmcneill%invisible.ca@localhost>>:
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> On Feb 18, 2018, at 3:20 PM, Andreas Drewke <andreas%drewke.net@localhost <mailto:andreas%drewke.net@localhost>> wrote:
>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>> I’m testing a 64-bit kernel on my Pinebook today, so far things are looking promising.
>>>>>>>>>>>>>>>>>>>> That sounds nice!!! Can I test or something? Will builds be available somewhere? I am excited to hear that.
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> I’ll start doing board specific images once arm64 support is merged into CVS and the auto build servers start generating builds. I don’t think think this is very far off.
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> I’ll send you a build to try in the meantime.
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> Cheers,
>>>>>>>>>>>>>>>>>>> Jared
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>> 
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>>> 
>> 
>