do_page_fault(): sending SIGSEGV to fast-gpio for invalid read access from 00000600

Luciano S.

@fossette , great ... then pls. go on to communicate here in the Forum ... you do a great job to show the others where to look ... but stop asking for something (more work) for Onion.io.

If you have solutions for their problems post them on git-hub as pull request. If you really want you can also try to make your "Known issues" and propose as pull request. But don't for get to do the maintenance for this section. You will see it is a lot of work/time you will miss for other tasks

</end_of_discussion>
<start_doing_it>
Thats how opensource community works!
</start_doing_it>```

Lazar Demin

@Luciano-S @fossette @Kit-Bishop @WereCatf
we actually have KERNEL_DEVMEM and KERNEL_DEVKMEM enabled, the firmware just stopped mapping /dev/mem a little while ago. Haven't had the time to dive into it tho!

A known issues page and changelog is in the works!

Lazar Demin

@Luciano-S @fossette @Kit-Bishop @WereCatf

Update: the firmware changelog and known issues listing is up! See the docs site: https://docs.onion.io/omega2-docs/firmware-reference.html

Will try to carve out time this week to look into this /dev/mem issue.

WereCatf

@Lazar-Demin Well, that's a start. I still would like to have access to the actual sources you build the firmware-images from, so maybe I could be of help.

Johannes

@Lazar-Demin
Any update relating to the fast-gpio thing?

Thanks

Costas Costas

@Lazar-Demin
Any update relating to the fast-gpio thing?

Thanks

Endre Czirbesz

@Lazar-Demin It was working fine in 0.1.6 b137, and not working since 0.1.6 b138 (up to 0.1.9-b157). Whatever was changed between 137 and 138, that would by bmy main suspect.

Michael Westberg

Anyone heard of any updates to this issue? Seems like the onion people only now and then comments and then its all quiet for a long time or forever.

Michael Westberg

@Lazar-Demin @administrators @Global-Moderators
Hi Lazar, I am sure you guys are busy with the shipping and interruptions you had etc. I still wonder how you handle software support during this period? There seems to several issues out there that should be pretty straight forward to solve and not take much of your time but stops many people in doing their work. Have you guys consider being somewhat more open about what prevents you from just fixing these issues ASAP? I see that there are several images being built continuously but not any updates to the issues?

While I, hopefully, have your attention. Do you know the reason why Onion has elected to not build with POSIX Messaging Queues enabled (mqueue)? This is an essential part of messaging between threads and processes and is enabled in the Kernel by default by most Linux distros. It would only require to enable the flag CONFIG_POSIX_MQUEUE when building. This one flag is enabled by default but NOT enabled in Onion builds.

Enabling this feature would open up a lot of possible IPC features on your device.

Thanks,

Michael

Lazar Demin

Ok, b160 fixes the missing /dev/mem device so fast-gpio will now work correctly!.
Also, we're now building the firmware with POSIX Messaging Queues enabled!

The issue was that our kernel config was setup to enable DEVMEM and DEV_KMEM, but for some reason the regular buildroot config had that disabled.

We're getting a better handle on the remaining shipments and the customer support backlog so we'll be spending more time actually making the Omega better in March. We hear what you guys are saying in terms of the community working the make the firmware better, so we will be open sourcing the firmware sometime in March as well

Thank you all for your continued patience and support for a young company

WereCatf

@Lazar-Demin said in do_page_fault(): sending SIGSEGV to fast-gpio for invalid read access from 00000600:

Ok, b160 fixes the missing /dev/mem device so fast-gpio will now work correctly!.
Also, we're now building the firmware with POSIX Messaging Queues enabled!

The issue was that our kernel config was setup to enable DEVMEM and DEV_KMEM, but for some reason the regular buildroot config had that disabled.

What, already? Amazing, it's only been several months now!

Jo Kritzinger

@Lazar-Demin Thanks for that. Can you also add the command line devmem for us tinkerers please.

Luciano S.

@Jo-Kritzinger , just update to b160 firmware! Then it should work ... or did I misunderstand you?

Jo Kritzinger

@Luciano-S. there is also a command called devmem that pokes a hole through the os and allows you to directly access the memory, great for accessing hardware registers. Read the article "WS281x, SK6812 driver for the Omega2?" posted by @luz. in there he uses the command to investigate pwm.

Chris Stratton

@Jo-Kritzinger

there is also a command called devmem that pokes a hole through the os and allows you to directly access the memory

Actually it is the kernel driver that creates the /dev/mem device which is the hole through the usual OS restrictions .

The devmem tool merely provides an easy way to make use of that from the command line.

Jo Kritzinger

@Chris-Stratton Thanks for clearing that up Chris. Where is the devmem tool?

Chris Stratton

@Jo-Kritzinger said in do_page_fault(): sending SIGSEGV to fast-gpio for invalid read access from 00000600:

@Chris-Stratton Thanks for clearing that up Chris. Where is the devmem tool?

It's usually provided as part of busybox, if it is present in the build I'd expect it to be in the path by default, it may well be in /sbin or another usual location for binaries. If it is provided by busybox then the devmem file entry will probably just be a simlink to the busybox executable and busybox devemem ..... may also work.

Jo Kritzinger

@Chris-Stratton I did a find / -name devmem which resulted in zero hits. I don't know (yet - new to linux world) how to make a custom build and that's why I asked @Lazar-Demin to include it in the build. I'd be grateful if you could guide me how to add it myself.

WereCatf

@Jo-Kritzinger Basically, you need someone to provide you with the LEDE SDK or you need to compile LEDE yourself in order to be able to configure custom settings for busybox and to compile it with them. Or, you can hope for the Onion-devs to include devmem in their images and just grab the version I compiled at https://dl.dropboxusercontent.com/u/11811685/omega2-stuff/devmem as a temporary solution.

Jo Kritzinger

@WereCatf So a wget into /tmp folder and a opkg install? I'll give it a go, thank you.