[Letux-kernel] compile problems

H. Nikolaus Schaller hns at goldelico.com
Tue Jul 24 19:22:46 CEST 2018


Hi,

> Am 24.07.2018 um 19:09 schrieb Andreas Kemnade <andreas at kemnade.info>:
> 
> On Tue, 24 Jul 2018 08:28:00 +0200
> "H. Nikolaus Schaller" <hns at goldelico.com> wrote:
> 
> 
>>>> And I haven't seen the iio related error. Maybe something spurious or
>>>> is it repeatable for you? Then it could be an effect based on different
>>>> boot procedure (assuming you boot through serial/usb - I did boot from
>>>> U-Boot with Josuas and your DFU fixes in NAND and kernel on µSD).
>>>> 
>>> My X setup tries to talk with the accelerometer but then ignores it. Maybe that is different
>>> 
>>> [   246.821] (II) config/udev: Adding input device accelerometer-iio-input-bridge (/dev/input/event6)
>>> [   246.821] (II) No input driver specified, ignoring this device.
>>> [   246.821] (II) This device may have been added with another device file.
>>> [   246.822] (II) config/udev: Adding input device accelerometer-iio-input-bridge (/dev/input/js0)
>>> [   246.822] (II) No input driver specified, ignoring this device.
>>> [   246.822] (II) This device may have been added with another device
>>> file.
>>> 
>>> Maybe that is not the case in your setup. xxd /dev/input/event6 (or wherever the bridge is) spits out
>>> data in earlier kernels but not in 4.18-rc6.
>> 
>> For me it works:
>> 
>> root at letux:~# evtest /dev/input/event3
>> Input driver version is 1.0.1
>> Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
>> Input device name: "accelerometer-iio-input-bridge"
>> Supported events:
>>  Event type 0 (EV_SYN)
>>  Event type 3 (EV_ABS)
>>    Event code 0 (ABS_X)
>>      Value     16
>>      Min     -511
>>      Max      511
>>    Event code 1 (ABS_Y)
>>      Value     -1
>>      Min     -511
>>      Max      511
>>    Event code 2 (ABS_Z)
>>      Value    246
>>      Min     -511
>>      Max      511
>> Properties:
>> Testing ... (interrupt to exit)
>> Event: time 1532413320.083504, type 3 (EV_ABS), code 1 (ABS_Y), value 0
>> Event: time 1532413320.083504, -------------- EV_SYN ------------
>> Event: time 1532413320.194400, type 3 (EV_ABS), code 0 (ABS_X), value 28
>> Event: time 1532413320.194400, type 3 (EV_ABS), code 1 (ABS_Y), value 2
>> Event: time 1532413320.194400, type 3 (EV_ABS), code 2 (ABS_Z), value 243
>> Event: time 1532413320.194400, -------------- EV_SYN ------------
>> Event: time 1532413320.304318, type 3 (EV_ABS), code 0 (ABS_X), value 27
>> Event: time 1532413320.304318, type 3 (EV_ABS), code 2 (ABS_Z), value 242
>> Event: time 1532413320.304318, -------------- EV_SYN ------------
>> Event: time 1532413320.413718, type 3 (EV_ABS), code 1 (ABS_Y), value 1
>> Event: time 1532413320.413718, type 3 (EV_ABS), code 2 (ABS_Z), value 241
>> Event: time 1532413320.413718, -------------- EV_SYN ------------
>> Event: time 1532413320.963586, type 3 (EV_ABS), code 2 (ABS_Z), value 240
>> Event: time 1532413320.963586, -------------- EV_SYN ------------
>> Event: time 1532413321.072619, type 3 (EV_ABS), code 2 (ABS_Z), value 241
>> Event: time 1532413321.072619, -------------- EV_SYN ------------
>> Event: time 1532413321.182996, type 3 (EV_ABS), code 1 (ABS_Y), value 0
>> Event: time 1532413321.182996, -------------- EV_SYN ------------
>> Event: time 1532413321.294349, type 3 (EV_ABS), code 1 (ABS_Y), value 1
>> Event: time 1532413321.294349, -------------- EV_SYN ------------
>> Event: time 1532413321.403687, type 3 (EV_ABS), code 0 (ABS_X), value 28
>> Event: time 1532413321.403687, -------------- EV_SYN ------------
>> Event: time 1532413321.623738, type 3 (EV_ABS), code 0 (ABS_X), value 27
>> Event: time 1532413321.623738, type 3 (EV_ABS), code 2 (ABS_Z), value 240
>> Event: time 1532413321.623738, -------------- EV_SYN ------------
>> Event: time 1532413321.734023, type 3 (EV_ABS), code 0 (ABS_X), value 28
>> Event: time 1532413321.734023, type 3 (EV_ABS), code 2 (ABS_Z), value 241
>> Event: time 1532413321.734023, -------------- EV_SYN ------------
>> Event: time 1532413321.843331, type 3 (EV_ABS), code 0 (ABS_X), value 27
>> Event: time 1532413321.843331, type 3 (EV_ABS), code 2 (ABS_Z), value 240
>> Event: time 1532413321.843331, -------------- EV_SYN ------------
>> ^C
>> root at letux:~# uname -a
>> Linux letux 4.18.0-rc6-letux+ #2551 SMP PREEMPT Mon Jul 23 08:05:46 CEST 2018 armv7l GNU/Linuxroot at letux:~# dmesg|fgrep input
>> [    3.208038] input: gpio-keys as /devices/platform/gpio-keys/input/input0
>> [    3.216705] input: gpio-keys-wwan-wakeup as /devices/platform/gpio-keys-wwan-wakeup/input/input1
>> [    3.237121] input: antenna-detect as /devices/platform/antenna-detect/input/input2
>> [   10.392486] input: twl4030_pwrbutton as /devices/platform/68000000.ocp/48070000.i2c/i2c-0/0-0048/48070000.i2c:twl at 48:pwrbutton/input/input3
>> [   10.425750] input: twl4030:vibrator as /devices/platform/68000000.ocp/48070000.i2c/i2c-0/0-0048/48070000.i2c:twl at 48:audio/twl4030-vibra/input/input4
>> [   10.461761] input: accelerometer-iio-input-bridge as /devices/virtual/input/input5
>> [   10.683471] input: TSC2007 Touchscreen as /devices/platform/68000000.ocp/48072000.i2c/i2c-1/1-0048/input/input6
>> root at letux:~#
>> 
>> But that doesn't solve your problem. It looks as if the kernel is generally
>> not running stable on your device and showing spurious bugs. Either in bitmap
>> console, or here in iio.
>> 
>> Could you please try my compiled binary to exclude a compiler issue?
>> 
>> http://download.goldelico.com/letux-kernel/letux-4.18-rc6/
> 
> Just if it got lost: no display problems seen with rc6.
> 
> same behavior with your binaries:
> # dmesg | head
> [    0.000000] Booting Linux on physical CPU 0x0
> [    0.000000] Linux version 4.18.0-rc6-letux+ (hns at iMac.fritz.box)
> (gcc version 4.9.2 (GCC)) #2555 SMP PREEMPT Mon Jul 23 15:05:50 CEST
> 2018
> 
> 
> I found out something else. booting is quite slow.
> [    9.990753] wlcore: loaded
> [   10.224548] voice ctl route: 0
> [   51.311065] random: crng init done
> [  225.707885] EXT4-fs (mmcblk0p6): re-mounted. Opts: (null)
> [  226.091583] EXT4-fs (mmcblk0p6): re-mounted. Opts: errors=remount-ro
> That caused the impression that the device is hung.

Ok. I also have such effects sometimes - but it seems to be dhcpd which does
not always find network devices.

> 
> and
> root at gta04:/var/log# ps auxww | grep accel
> root      1243 88.8  0.1   1984  1056 ?        R    18:45
> 12:00 /lib/udev/accelerometer /devices/virtual/input/input6

Hm. What is /lib/udev/accelerometer ?

Never heard of it. But according to

https://github.com/lu-zero/udev/blob/master/src/accelerometer/accelerometer.c

it seems to be a daemon that tries to handle device orientation. I didn't know
that this exists. BTW: if such a daemon is "standard" this is a good argument
why we need such an iio-input-bridge in the kernel...

> 
> That is from
> 
> Package: udev
> Version: 215-17+deb8u7
> 
> Ok, renaming it gives a fast boot.
> Then I run evtest and my cpu is busy again. And the oops is there.

Ok, at least this should make debugging easier if you can boot and have
a clear trigger for the problem.

BR,
Nikolaus


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.goldelico.com/pipermail/letux-kernel/attachments/20180724/8230ed64/attachment.asc>


More information about the Letux-kernel mailing list