Easy Mode GPIO PWM on U3

Post Reply
mdrjr
Site Admin
Posts: 11698
Joined: Fri Feb 22, 2013 11:34 pm
languages_spoken: english, portuguese
ODROIDs: -
Location: Brazil
Contact:

Easy Mode GPIO PWM on U3

Unread post by mdrjr » Fri May 16, 2014 7:32 am

Starting for today (20140515) I'm including on the kernel software pwm support for GPIO's.
So, you need to update your kernel to take advantage of this.

As explained here: http://forum.odroid.com/viewtopic.php?f=80&t=4894

You can choose one of the 3 GPIO's or if you have the IO Shield any of the 16 GPIO's on the shield for that.

Its simple as cake..

Code: Select all

root@odroid:~# cd /sys/class/soft_pwm/
root@odroid:/sys/class/soft_pwm# echo 204 > export 
root@odroid:/sys/class/soft_pwm# cd pwm204
root@odroid:/sys/class/soft_pwm/pwm204# ls
counter  period  power  pulse  pulses  subsystem  uevent
root@odroid:/sys/class/soft_pwm/pwm204# echo 1000 > period 
root@odroid:/sys/class/soft_pwm/pwm204# echo 100 > pulse
root@odroid:/sys/class/soft_pwm/pwm204# 
See? now your gpio is a PWM output. And you can get ~20kHz on it.
All values of period/pulse are in uSeconds (microseconds).
u3_soft_pwm_scope.jpg
u3_soft_pwm_scope.jpg (109.73 KiB) Viewed 12319 times

arcltd
Posts: 7
Joined: Mon Jun 09, 2014 1:16 am
languages_spoken: english
ODROIDs: U3 + U3 sheild
Location: Bristol, UK
Contact:

Re: Easy Mode GPIO PWM on U3

Unread post by arcltd » Mon Jun 09, 2014 4:14 am

Hi

I'm hoping to get my U3 and IO shield board this week and I want to be able to read voltages through the ADC, I've looked through the magazine February issue and a few other posts but not seen any direct examples of how to read the ADC, can you offer any advice before my stuff turns up.

Thanks
Andy

mdrjr
Site Admin
Posts: 11698
Joined: Fri Feb 22, 2013 11:34 pm
languages_spoken: english, portuguese
ODROIDs: -
Location: Brazil
Contact:

Re: Easy Mode GPIO PWM on U3

Unread post by mdrjr » Mon Jun 09, 2014 7:15 am

arcltd wrote:Hi

I'm hoping to get my U3 and IO shield board this week and I want to be able to read voltages through the ADC, I've looked through the magazine February issue and a few other posts but not seen any direct examples of how to read the ADC, can you offer any advice before my stuff turns up.

Thanks
Andy
Please create your own thread and we'll take from there :9

Respectech
Posts: 279
Joined: Wed Nov 13, 2013 9:20 am
languages_spoken: English, German, some Ukrainian, some Spanish
ODROIDs: All the ODROIDs!!

Well, the ones released since the U2.
Location: California
Contact:

Re: Easy Mode GPIO PWM on U3

Unread post by Respectech » Mon Jul 07, 2014 12:27 pm

I was having trouble remembering what the port numbers were for the GPIO pins on the I/O Board. I found them in the February 2014 issue of ODROID Magazine, pg 33:

"16 Ports are mapped to GPIO #289~#304 (I/O Shield pin number P00~P07, P10~P17)"

Respectech
Posts: 279
Joined: Wed Nov 13, 2013 9:20 am
languages_spoken: English, German, some Ukrainian, some Spanish
ODROIDs: All the ODROIDs!!

Well, the ones released since the U2.
Location: California
Contact:

Re: Easy Mode GPIO PWM on U3

Unread post by Respectech » Tue Jul 08, 2014 7:07 am

Just a note that it is important to not push it much faster than 1000/100 microseconds for the period/pulse as it can lock up the terminal and cause other weird behavior.

1,000,000 microseconds = 1 second
100,000 microseconds = 0.1 second

1000 microseconds = 0.001 seconds = 1KHz
50 microseconds = 0.000050 seconds = 20KHz

I wasn't able to get it to work properly with even a period/pulse of 1000/100 (10KHz), but greater values seemed to work fine.

alben
Posts: 9
Joined: Fri Jul 18, 2014 6:02 am
languages_spoken: english
ODROIDs: U3
Contact:

Re: Easy Mode GPIO PWM on U3

Unread post by alben » Sun Jul 27, 2014 4:18 pm

Hi,

thank you for this new easy approach.

To push GPIO even further, is there any solution to use GPIO entries as Interrupt ?
We only have
root@odroid:/sys/class/soft_pwm/pwm204# ls
counter period power pulse pulses subsystem uevent
but 'edge' that is generally used for interrupts does not appear.

Is there another solution ?
The idea would be to add sensors (PIR sensors for example) that would start applications on alarms.

Thank you for any hint.
Alex

User avatar
Digimaster
Posts: 220
Joined: Tue Feb 26, 2013 4:16 pm
languages_spoken: english, russian
ODROIDs: U2, X2, U3, C1, C2, XU4 × 300+
Location: Moscow, Russia
Contact:

Re: Easy Mode GPIO PWM on U3

Unread post by Digimaster » Sun Jul 27, 2014 4:23 pm

At least it can be emulated by software.
Use pthreads lib to read gpio status in separate thread, or just a fork with pipe to signal main application.

alben
Posts: 9
Joined: Fri Jul 18, 2014 6:02 am
languages_spoken: english
ODROIDs: U3
Contact:

Re: Easy Mode GPIO PWM on U3

Unread post by alben » Sun Jul 27, 2014 8:36 pm

Digimaster wrote:At least it can be emulated by software.
Use pthreads lib to read gpio status in separate thread, or just a fork with pipe to signal main application.
Hi, thank you for the hint.
But is it a battery saving approach ? Interrupts do not imply threads waiting for an even.

There is another possible approach : using a gpio counter that regularly run callback that would checks the gpio pin state... is it possible on this plateforme ?

Which solution is the most battery saving ?
Thanks

User avatar
Digimaster
Posts: 220
Joined: Tue Feb 26, 2013 4:16 pm
languages_spoken: english, russian
ODROIDs: U2, X2, U3, C1, C2, XU4 × 300+
Location: Moscow, Russia
Contact:

Re: Easy Mode GPIO PWM on U3

Unread post by Digimaster » Mon Jul 28, 2014 7:30 pm

Sure, timers can be used as well. Btw threads is good enough for power saving.
It can check gpio from time to time going sleep in between, so it can be 99,9% in sleeping state.

alben
Posts: 9
Joined: Fri Jul 18, 2014 6:02 am
languages_spoken: english
ODROIDs: U3
Contact:

Re: Easy Mode GPIO PWM on U3

Unread post by alben » Tue Jul 29, 2014 4:14 pm

Digimaster wrote:Sure, timers can be used as well. Btw threads is good enough for power saving.
It can check gpio from time to time going sleep in between, so it can be 99,9% in sleeping state.
Yep, this is a very good argument, i will play with this solution, thanks.

One last question : any news about the ioshield support (gpio access, etc.) from Android ?

Thanks

User avatar
odroid
Site Admin
Posts: 29678
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Contact:

Re: Easy Mode GPIO PWM on U3

Unread post by odroid » Tue Jul 29, 2014 4:50 pm

alben wrote: One last question : any news about the ioshield support (gpio access, etc.) from Android ?
Refer this link.
http://forum.odroid.com/viewtopic.php?f=51&t=5846

chens
Posts: 20
Joined: Thu Jul 24, 2014 3:51 pm
languages_spoken: english
ODROIDs: odroid xu,odroid xu3,odroid u3,odroid xu_lite
Contact:

Re: Easy Mode GPIO PWM on U3

Unread post by chens » Wed Apr 29, 2015 1:55 am

is there any example(c/c++) code ? i need do it in my code.

mdrjr
Site Admin
Posts: 11698
Joined: Fri Feb 22, 2013 11:34 pm
languages_spoken: english, portuguese
ODROIDs: -
Location: Brazil
Contact:

Re: Easy Mode GPIO PWM on U3

Unread post by mdrjr » Tue Jun 16, 2015 6:15 am

use fopen() and fwrite() on the files above.

netstv
Posts: 12
Joined: Fri Feb 20, 2015 9:13 am
languages_spoken: english
ODROIDs: ODROID-U3
Contact:

Re: Easy Mode GPIO PWM on U3

Unread post by netstv » Sat Jun 27, 2015 2:46 am

I have set everything up with the latest ODRIOD U3 and rev 0.5 of the io shield board.

I have a setup script file:

Code: Select all

#!/bin/bash

# The i2c-4 is not loaded by default.  So need to load it.
modprobe i2c_gpio_custom bus0=4,200,199

# now load the gpio module
sudo modprobe gpio-pca953x

# Set the I2C address of the module
echo tca6416 0x20 > /sys/devices/platform/i2c-gpio.4/i2c-4/new_device

cd /sys/class/soft_pwm
echo 289 > export
Then I try to do:

echo 1000 > period and I get a crash.

Code: Select all

root@odroid:/sys/class/soft_pwm/pwm289# echo 1000 > period
root@odroid:/sys/class/soft_pwm/pwm289#[  200.766884] ------------[ cut here ]------------
[  200.771293] WARNING: at kernel/mutex.c:198 __mutex_lock_slowpath+0x2c0/0x344()
[  200.778485] Modules linked in: gpio_pca953x i2c_gpio_custom ipv6 rfcomm bnep bluetooth smsc95xx usbnet gpio_keys fuse vfat fat
[  200.789852] [<c0014f78>] (unwind_backtrace+0x0/0xf8) from [<c0024b64>] (warn_slowpath_common+0x4c/0x64)
[  200.799217] [<c0024b64>] (warn_slowpath_common+0x4c/0x64) from [<c0024b98>] (warn_slowpath_null+0x1c/0x24)
[  200.808844] [<c0024b98>] (warn_slowpath_null+0x1c/0x24) from [<c0428c9c>] (__mutex_lock_slowpath+0x2c0/0x344)
[  200.818732] [<c0428c9c>] (__mutex_lock_slowpath+0x2c0/0x344) from [<c0428d2c>] (mutex_lock+0xc/0x24)
[  200.827840] [<c0428d2c>] (mutex_lock+0xc/0x24) from [<bf0fc1c4>] (pca953x_gpio_set_value+0x1c/0x70 [gpio_pca953x])
[  200.838165] [<bf0fc1c4>] (pca953x_gpio_set_value+0x1c/0x70 [gpio_pca953x]) from [<c01ea750>] (__gpio_set_value+0x60/0xb0)
[  200.849086] [<c01ea750>] (__gpio_set_value+0x60/0xb0) from [<c01ed310>] (soft_pwm_hrtimer_callback+0xcc/0x19c)
[  200.859060] [<c01ed310>] (soft_pwm_hrtimer_callback+0xcc/0x19c) from [<c0044220>] (__run_hrtimer.isra.20+0x44/0xd0)
[  200.869467] [<c0044220>] (__run_hrtimer.isra.20+0x44/0xd0) from [<c0044980>] (hrtimer_interrupt+0x108/0x2b4)
[  200.879267] [<c0044980>] (hrtimer_interrupt+0x108/0x2b4) from [<c0044b90>] (hrtimer_peek_ahead_timers+0x10/0x18)
[  200.889414] [<c0044b90>] (hrtimer_peek_ahead_timers+0x10/0x18) from [<c002bc1c>] (__do_softirq+0xc8/0x188)
[  200.899040] [<c002bc1c>] (__do_softirq+0xc8/0x188) from [<c002bd08>] (run_ksoftirqd+0x2c/0x44)
[  200.907627] [<c002bd08>] (run_ksoftirqd+0x2c/0x44) from [<c00485f8>] (smpboot_thread_fn+0x164/0x238)
[  200.916734] [<c00485f8>] (smpboot_thread_fn+0x164/0x238) from [<c004043c>] (kthread+0xa4/0xb0)
[  200.925319] [<c004043c>] (kthread+0xa4/0xb0) from [<c000e398>] (ret_from_fork+0x14/0x3c)
[  200.933381] ---[ end trace 9d951ee46edea562 ]---

I know the gpio is setup properly to my device because if I just set the GPIO,

Code: Select all

for gpio_n in `seq 289 304`
do
echo $gpio_n > /sys/class/gpio/export
done

If I call the above for loop setting up the /sys/class/gpio/gpio289
and then try to export the echo 289 > /sys/class/soft_pwm/export

I get

Code: Select all

echo: write error: Device or resource busy
I haven't looked at the code yet, going to do that shortly, but I'm thinking I'm setting something up incorrectly...

Is there something I'm missing where I need to setup the GPIO as an output?

Thanks for any help you can give me.

-stv

mdrjr
Site Admin
Posts: 11698
Joined: Fri Feb 22, 2013 11:34 pm
languages_spoken: english, portuguese
ODROIDs: -
Location: Brazil
Contact:

Re: Easy Mode GPIO PWM on U3

Unread post by mdrjr » Sat Jun 27, 2015 7:16 am

If you don't use the softpwm and poke the gpio's manually it works?

netstv
Posts: 12
Joined: Fri Feb 20, 2015 9:13 am
languages_spoken: english
ODROIDs: ODROID-U3
Contact:

Re: Easy Mode GPIO PWM on U3

Unread post by netstv » Mon Jun 29, 2015 2:52 am

Yes that is correct.

So I know the GPIO is setup properly and that everything at that point works.

mdrjr
Site Admin
Posts: 11698
Joined: Fri Feb 22, 2013 11:34 pm
languages_spoken: english, portuguese
ODROIDs: -
Location: Brazil
Contact:

Re: Easy Mode GPIO PWM on U3

Unread post by mdrjr » Mon Jun 29, 2015 7:29 am

I need to test that.. when I wrote that guide I didn't tested the softpwm using the IO expansion board.

netstv
Posts: 12
Joined: Fri Feb 20, 2015 9:13 am
languages_spoken: english
ODROIDs: ODROID-U3
Contact:

Re: Easy Mode GPIO PWM on U3

Unread post by netstv » Tue Jul 28, 2015 6:20 am

Hi Mdrjr --

Have you tried to load the tca6416 with the latest 3.8.13.30 kernel?

I'm having problems with it and I want to debug and figure out the PWM issue. Being that I only work on this in my spare time, I thought I'd ask you while I'm trying to figure out what is going on.... Once I get it loading, I'm sure I'll figure out what is going on with the PWM.

I have setup the tca6416 as was described in the magazine article (I think Feb '14). So I have created an /etc/modules/tca6416.conf which calls a script /usr/sbin/tca6416init.sh file that I created.

Works great with the 3.8.13.28 zImage but when I change it to the 3.8.13.30 zImage it fails.

I'm still hunting down what the actual error is, but there has to be something that I need to do to the kernel config (just a guess).

BTW: I do have the proper /lib/modules loaded just an FYI.

Thanks in advance..

-stv

mdrjr
Site Admin
Posts: 11698
Joined: Fri Feb 22, 2013 11:34 pm
languages_spoken: english, portuguese
ODROIDs: -
Location: Brazil
Contact:

Re: Easy Mode GPIO PWM on U3

Unread post by mdrjr » Tue Jul 28, 2015 6:48 am

Hello netstv,

This is how I set it up here:

Code: Select all

modprobe i2c-dev
modprobe i2c_gpio_custom bus0=4,200,199
echo tca6416 0x20 > /sys/devices/platform/i2c-gpio.4/i2c-4/new_device

netstv
Posts: 12
Joined: Fri Feb 20, 2015 9:13 am
languages_spoken: english
ODROIDs: ODROID-U3
Contact:

Re: Easy Mode GPIO PWM on U3

Unread post by netstv » Tue Jul 28, 2015 6:54 am

Yup...

and then I do:

Code: Select all

root@odroid: cd /sys/class/soft_pwm
root@odroid:/sys/class/soft_pwm# echo 289 > export
-bash: echo: write error: Unknown error 517
now I'm trying to find out what in the heck that error 517 is.

mdrjr
Site Admin
Posts: 11698
Joined: Fri Feb 22, 2013 11:34 pm
languages_spoken: english, portuguese
ODROIDs: -
Location: Brazil
Contact:

Re: Easy Mode GPIO PWM on U3

Unread post by mdrjr » Tue Jul 28, 2015 7:01 am

GPIO's from the shield are base 340.

GPIO1 on the shield is 341
GPIO2 is 342... and so on..

netstv
Posts: 12
Joined: Fri Feb 20, 2015 9:13 am
languages_spoken: english
ODROIDs: ODROID-U3
Contact:

Re: Easy Mode GPIO PWM on U3

Unread post by netstv » Wed Jul 29, 2015 2:25 am

Oh duh! Your right.. .but now I screwed up my zImage and it doesn't boot...

I'll keep you up to date on my progress :ugeek:

User avatar
odroid
Site Admin
Posts: 29678
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Contact:

Re: Easy Mode GPIO PWM on U3

Unread post by odroid » Wed Jul 29, 2015 10:35 am


netstv
Posts: 12
Joined: Fri Feb 20, 2015 9:13 am
languages_spoken: english
ODROIDs: ODROID-U3
Contact:

Re: Easy Mode GPIO PWM on U3

Unread post by netstv » Wed Jul 29, 2015 1:00 pm

Yeah I know.. if you see from my earlier posts I have it right.. I was just ... well being stupid.

vbextreme
Posts: 80
Joined: Sat Jul 19, 2014 6:43 pm
languages_spoken: english,italiano
ODROIDs: U3,IO shields,Wi-Fi
Contact:

Re: Easy Mode GPIO PWM on U3

Unread post by vbextreme » Thu Sep 10, 2015 11:40 pm

max precision pwm at 10khz?
Easy framework framework for c language
EasyGCC Color output of gcc
MagixCubic cli puzzle game
Bigt Google translate for bash with notify

Bilboed
Posts: 17
Joined: Sun Apr 14, 2013 8:36 pm
languages_spoken: english
ODROIDs: U2, U3 and Show
Contact:

Re: Easy Mode GPIO PWM on U3

Unread post by Bilboed » Sun Mar 18, 2018 6:12 am

I am trying to use easy mode pwm on a U3 io_shield (Ubuntu 14.04 LTS) .

The GPIO on the shield works perfectly but pwm does not. Almost every time I set the pwm period (echo 7812 > period) I get a kernel panic. Once or twice it has worked. It would appear there is a conflict of some sort.

Code: Select all

uname -a
Linux solar-srvr 3.8.13.30 #1 SMP PREEMPT Wed Mar 4 17:26:56 BRT 2015 armv7l armv7l armv7l GNU/Linux

 modprobe i2c-gpio-custom bus0=4,200,199
 modprobe gpio-pca953x
 echo tca6416 0x20 > /sys/devices/platform/i2c-gpio.4/i2c-4/new_device
 cd /sys/class/soft_pwm
 echo 342 > export
 cd pwm_342
dmesg up to this point

Code: Select all

[  229.938181] Custom GPIO-based I2C driver version 0.1.1
[  229.939152] i2c-gpio i2c-gpio.4: using pins 200 (SDA) and 199 (SCL)
[  276.141247] pca953x 4-0020: interrupt support not compiled in
[  276.143914] i2c i2c-4: new_device: Instantiated device tca6416 at 0x20
[  306.806405] CPU2: Booted secondary processor
[  308.010306] CPU2: shutdown
[  312.215195] Registered device pwm342
then "echo 7812 > period" followed by dmesg

Code: Select all

[ 1667.724068] ------------[ cut here ]------------
[ 1667.724168] WARNING: at drivers/gpio/gpiolib.c:1791 __gpio_set_value+0xa0/0xb0()
[ 1667.724198] Modules linked in: gpio_pca953x i2c_gpio_custom cpufreq_ondemand cpufreq_userspace cpufreq_conservative cpufreq_powersave ipv6 rtl8192cu cdc_acm smsc95xx usbnet dm_multipath dm_mod gpio_keys vfat fat
[ 1667.724492] [<c0014e68>] (unwind_backtrace+0x0/0xf8) from [<c00248ec>] (warn_slowpath_common+0x4c/0x64)
[ 1667.724556] [<c00248ec>] (warn_slowpath_common+0x4c/0x64) from [<c0024920>] (warn_slowpath_null+0x1c/0x24)
[ 1667.724617] [<c0024920>] (warn_slowpath_null+0x1c/0x24) from [<c01e90dc>] (__gpio_set_value+0xa0/0xb0)
[ 1667.724692] [<c01e90dc>] (__gpio_set_value+0xa0/0xb0) from [<c01ebc5c>] (soft_pwm_hrtimer_callback+0xcc/0x19c)
[ 1667.724770] [<c01ebc5c>] (soft_pwm_hrtimer_callback+0xcc/0x19c) from [<c0043d78>] (__run_hrtimer.isra.20+0x44/0xd0)
[ 1667.724833] [<c0043d78>] (__run_hrtimer.isra.20+0x44/0xd0) from [<c0044460>] (hrtimer_interrupt+0xfc/0x298)
[ 1667.724893] [<c0044460>] (hrtimer_interrupt+0xfc/0x298) from [<c0044660>] (hrtimer_peek_ahead_timers+0x10/0x18)
[ 1667.724961] [<c0044660>] (hrtimer_peek_ahead_timers+0x10/0x18) from [<c002b878>] (__do_softirq+0xc8/0x188)
[ 1667.725027] [<c002b878>] (__do_softirq+0xc8/0x188) from [<c002b964>] (run_ksoftirqd+0x2c/0x44)
[ 1667.725141] [<c002b964>] (run_ksoftirqd+0x2c/0x44) from [<c004804c>] (smpboot_thread_fn+0x164/0x238)
[ 1667.725233] [<c004804c>] (smpboot_thread_fn+0x164/0x238) from [<c003ffc8>] (kthread+0xa4/0xb0)
[ 1667.725305] [<c003ffc8>] (kthread+0xa4/0xb0) from [<c000e2d8>] (ret_from_fork+0x14/0x3c)
[ 1667.725338] ---[ end trace 86f1af438124bc63 ]---
[ 1667.725367] ------------[ cut here ]------------
[ 1667.725882] WARNING: at kernel/mutex.c:198 __mutex_lock_slowpath+0x2c0/0x344()
[ 1667.732108] Modules linked in: gpio_pca953x i2c_gpio_custom cpufreq_ondemand cpufreq_userspace cpufreq_conservative cpufreq_powersave ipv6 rtl8192cu cdc_acm smsc95xx usbnet dm_multipath dm_mod gpio_keys vfat fat
[ 1667.750356] [<c0014e68>] (unwind_backtrace+0x0/0xf8) from [<c00248ec>] (warn_slowpath_common+0x4c/0x64)
[ 1667.760406] [<c00248ec>] (warn_slowpath_common+0x4c/0x64) from [<c0024920>] (warn_slowpath_null+0x1c/0x24)
[ 1667.770056] [<c0024920>] (warn_slowpath_null+0x1c/0x24) from [<c0424624>] (__mutex_lock_slowpath+0x2c0/0x344)
[ 1667.779956] [<c0424624>] (__mutex_lock_slowpath+0x2c0/0x344) from [<c04246b4>] (mutex_lock+0xc/0x24)
[ 1667.789015] [<c04246b4>] (mutex_lock+0xc/0x24) from [<bf1651c4>] (pca953x_gpio_set_value+0x1c/0x70 [gpio_pca953x])
[ 1667.799451] [<bf1651c4>] (pca953x_gpio_set_value+0x1c/0x70 [gpio_pca953x]) from [<c01e909c>] (__gpio_set_value+0x60/0xb0)
[ 1667.810405] [<c01e909c>] (__gpio_set_value+0x60/0xb0) from [<c01ebc5c>] (soft_pwm_hrtimer_callback+0xcc/0x19c)
[ 1667.820310] [<c01ebc5c>] (soft_pwm_hrtimer_callback+0xcc/0x19c) from [<c0043d78>] (__run_hrtimer.isra.20+0x44/0xd0)
[ 1667.830731] [<c0043d78>] (__run_hrtimer.isra.20+0x44/0xd0) from [<c0044460>] (hrtimer_interrupt+0xfc/0x298)
[ 1667.840391] [<c0044460>] (hrtimer_interrupt+0xfc/0x298) from [<c0044660>] (hrtimer_peek_ahead_timers+0x10/0x18)
[ 1667.850487] [<c0044660>] (hrtimer_peek_ahead_timers+0x10/0x18) from [<c002b878>] (__do_softirq+0xc8/0x188)
[ 1667.860080] [<c002b878>] (__do_softirq+0xc8/0x188) from [<c002b964>] (run_ksoftirqd+0x2c/0x44)
[ 1667.868593] [<c002b964>] (run_ksoftirqd+0x2c/0x44) from [<c004804c>] (smpboot_thread_fn+0x164/0x238)
[ 1667.877740] [<c004804c>] (smpboot_thread_fn+0x164/0x238) from [<c003ffc8>] (kthread+0xa4/0xb0)
[ 1667.886278] [<c003ffc8>] (kthread+0xa4/0xb0) from [<c000e2d8>] (ret_from_fork+0x14/0x3c)
[ 1667.894268] ---[ end trace 86f1af438124bc64 ]---

Any help would be appreciated.

Post Reply

Return to “Hardware and peripherals”

Who is online

Users browsing this forum: No registered users and 1 guest