sysfs: cannot create duplicate filename '/bus/platform/devices/4a300000.pruss'

[Hartley Sweeten]

Hello all,

I was trying the bone-debian-9.1-lxqt-armhf-2017-08-31-4gb.img.xz with a Newhaven NHD-7.0CTP-CAPE-N. It boots up fine and the screen and capacitive touchscreen work great. But I noticed this WARNING in the dmesg:

[   31.517455] ------------[ cut here ]------------

[   31.517513] WARNING: CPU: 0 PID: 347 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x78/0x88

[   31.517520] sysfs: cannot create duplicate filename '/bus/platform/devices/4a300000.pruss'

[   31.517526] Modules linked in: pruss_soc_bus(+) joydev evdev uio_pdrv_genirq uio usb_f_mass_storage 8021q garp mrp stp llc usb_f_acm u_serial usb_f_ecm usb_f_rndis u_ether libcomposite iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_filter spidev pru_rproc pruss_intc pruss tieqep ip_tables x_tables

[   31.517659] CPU: 0 PID: 347 Comm: systemd-udevd Not tainted 4.9.76-ti-r91 #1

[   31.517665] Hardware name: Generic AM33XX (Flattened Device Tree)

[   31.517705] [<c0114468>] (unwind_backtrace) from [<c010dd20>] (show_stack+0x20/0x24)

[   31.517731] [<c010dd20>] (show_stack) from [<c0744720>] (dump_stack+0x80/0x94)

[   31.517747] [<c0744720>] (dump_stack) from [<c013e358>] (__warn+0xf8/0x110)

[   31.517760] [<c013e358>] (__warn) from [<c013e3c8>] (warn_slowpath_fmt+0x58/0x74)

[   31.517772] [<c013e3c8>] (warn_slowpath_fmt) from [<c0367410>] (sysfs_warn_dup+0x78/0x88)

[   31.517788] [<c0367410>] (sysfs_warn_dup) from [<c03677e8>] (sysfs_do_create_link_sd+0xc4/0xcc)

[   31.517802] [<c03677e8>] (sysfs_do_create_link_sd) from [<c0367828>] (sysfs_create_link+0x38/0x44)

[   31.517820] [<c0367828>] (sysfs_create_link) from [<c08d15c0>] (bus_add_device+0x130/0x1b8)

[   31.517834] [<c08d15c0>] (bus_add_device) from [<c08cf114>] (device_add+0x298/0x5d0)

[   31.517852] [<c08cf114>] (device_add) from [<c0af2680>] (of_device_add+0x44/0x4c)

[   31.517867] [<c0af2680>] (of_device_add) from [<c0af2d98>] (of_platform_device_create_pdata+0x94/0xcc)

[   31.517879] [<c0af2d98>] (of_platform_device_create_pdata) from [<c0af30c0>] (of_platform_bus_create+0x174/0x30c)

[   31.517891] [<c0af30c0>] (of_platform_bus_create) from [<c0af342c>] (of_platform_populate+0x84/0x120)

[   31.517924] [<c0af342c>] (of_platform_populate) from [<bf15c2d4>] (pruss_soc_bus_probe+0x12c/0x290 [pruss_soc_bus])

[   31.517973] [<bf15c2d4>] (pruss_soc_bus_probe [pruss_soc_bus]) from [<c08d4db8>] (platform_drv_probe+0x60/0xc0)

[   31.517987] [<c08d4db8>] (platform_drv_probe) from [<c08d2798>] (driver_probe_device+0x2b4/0x440)

[   31.517999] [<c08d2798>] (driver_probe_device) from [<c08d2a24>] (__driver_attach+0x100/0x10c)

[   31.518009] [<c08d2a24>] (__driver_attach) from [<c08d02b4>] (bus_for_each_dev+0x8c/0xd0)

[   31.518020] [<c08d02b4>] (bus_for_each_dev) from [<c08d1f68>] (driver_attach+0x2c/0x30)

[   31.518031] [<c08d1f68>] (driver_attach) from [<c08d199c>] (bus_add_driver+0x16c/0x26c)

[   31.518043] [<c08d199c>] (bus_add_driver) from [<c08d3804>] (driver_register+0x88/0x104)

[   31.518054] [<c08d3804>] (driver_register) from [<c08d4d04>] (__platform_driver_register+0x50/0x58)

[   31.518071] [<c08d4d04>] (__platform_driver_register) from [<bf15f020>] (pruss_soc_bus_driver_init+0x20/0xc0 [pruss_soc_bus])

[   31.518093] [<bf15f020>] (pruss_soc_bus_driver_init [pruss_soc_bus]) from [<c0101d28>] (do_one_initcall+0x64/0x1a0)

[   31.518117] [<c0101d28>] (do_one_initcall) from [<c0273014>] (do_init_module+0x74/0x3d0)

[   31.518136] [<c0273014>] (do_init_module) from [<c01e13d8>] (load_module+0x1f40/0x2614)

[   31.518149] [<c01e13d8>] (load_module) from [<c01e1d58>] (SyS_finit_module+0xdc/0x110)

[   31.518167] [<c01e1d58>] (SyS_finit_module) from [<c0109120>] (__sys_trace_return+0x0/0x10)

[   31.518175] ---[ end trace 714a7bf4a57d0f0d ]---

This warning shows up with the 4.9.45-ti-r57 kernel from the image and with the 4.9.76-ti-r91 kernel after doing a sudo /opt/scripts/tools/update_kernel.sh.

Is this a known issue in the kernel or do I have something setup incorrectly?

This is the output from the versions.sh script:

$ sudo /opt/scripts/tools/version.sh 

git:/opt/scripts/:[714e162ba98cf3d2897e7fc95e951c6df15a7d0a]

eeprom:[A335BNLT00C05014BBBK0A84]

model:[TI_AM335x_BeagleBone_Black]

dogtag:[BeagleBoard.org Debian Image 2017-08-31]

bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2018.01-00002-gcc9c2d1992]

kernel:[4.9.76-ti-r91]

nodejs:[v6.11.2]

uboot_overlay_options:[enable_uboot_overlays=1]

uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo]

uboot_overlay_options:[enable_uboot_cape_universal=1]

pkg:[bb-cape-overlays]:[4.4.20170728.0-0rcnee1~stretch+20170728]

pkg:[bb-wl18xx-firmware]:[1.20170829-0rcnee1~stretch+20170829]

pkg:[firmware-ti-connectivity]:[20170823-1rcnee0~stretch+20170830]

dmesg | grep pinctrl-single

[    1.362988] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568

[    1.750855] pinctrl-single 44e10800.pinmux: pin PIN95 already requested by ocp:P9_19_pinmux; cannot claim for 4819c000.i2c

[    1.762096] pinctrl-single 44e10800.pinmux: pin-95 (4819c000.i2c) status -22

[    1.769223] pinctrl-single 44e10800.pinmux: could not request pin 95 (PIN95) from group pinmux_bb_i2c2_pins  on device pinctrl-single

END

I also notices this on the serial console when the board boots:

Starting kernel ...

[    0.000925] clocksource_probe: no matching clocksources found

[    1.369280] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle

[    1.648806] omap_voltage_late_init: Voltage driver support not added

[    1.656162] PM: Cannot get wkup_m3_ipc handle

[    1.750855] pinctrl-single 44e10800.pinmux: pin PIN95 already requested by ocp:P9_19_pinmux; cannot claim for 4819c000.i2c

[    1.762096] pinctrl-single 44e10800.pinmux: pin-95 (4819c000.i2c) status -22

[    1.769223] pinctrl-single 44e10800.pinmux: could not request pin 95 (PIN95) from group pinmux_bb_i2c2_pins  on device pinctrl-single

[    1.781311] omap_i2c 4819c000.i2c: Error applying setting, reverse things back

[    1.792167] PM: Cannot get wkup_m3_ipc handle

Do I need to change something?

Also, is there any documentation on what packages can be safely removed from this image for the BeagleBone Black? The image is pretty bloated:

$ df | grep /dev/mmc

/dev/mmcblk1p1   3704040 2927544    568624  84% /

Regards,

Hartley

[Robert Nelson]

On Wed, Jan 17, 2018 at 1:31 PM, Hartley Sweeten <biggu...@gmail.com> wrote:
> Hello all,
>
> I was trying the bone-debian-9.1-lxqt-armhf-2017-08-31-4gb.img.xz with a
> Newhaven NHD-7.0CTP-CAPE-N. It boots up fine and the screen and capacitive
> touchscreen work great. But I noticed this WARNING in the dmesg:
>

> This warning shows up with the 4.9.45-ti-r57 kernel from the image and with
> the 4.9.76-ti-r91 kernel after doing a sudo
> /opt/scripts/tools/update_kernel.sh.
>
> Is this a known issue in the kernel or do I have something setup
> incorrectly?
>
> This is the output from the versions.sh script:
>
> $ sudo /opt/scripts/tools/version.sh
> git:/opt/scripts/:[714e162ba98cf3d2897e7fc95e951c6df15a7d0a]
> eeprom:[A335BNLT00C05014BBBK0A84]
> model:[TI_AM335x_BeagleBone_Black]
> dogtag:[BeagleBoard.org Debian Image 2017-08-31]
> bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot
> 2018.01-00002-gcc9c2d1992]
> kernel:[4.9.76-ti-r91]
> nodejs:[v6.11.2]
> uboot_overlay_options:[enable_uboot_overlays=1]
> uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo]

In /boot/uEnv.txt comment out:

from:
uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo

to:
#uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo

v4.9.x-ti uses remoteproc_pruss and you can't switch to the other
"uio_pruss" option..

> uboot_overlay_options:[enable_uboot_cape_universal=1]
> pkg:[bb-cape-overlays]:[4.4.20170728.0-0rcnee1~stretch+20170728]
> pkg:[bb-wl18xx-firmware]:[1.20170829-0rcnee1~stretch+20170829]
> pkg:[firmware-ti-connectivity]:[20170823-1rcnee0~stretch+20170830]
> dmesg | grep pinctrl-single
> [ 1.362988] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size
> 568
> [ 1.750855] pinctrl-single 44e10800.pinmux: pin PIN95 already requested
> by ocp:P9_19_pinmux; cannot claim for 4819c000.i2c
> [ 1.762096] pinctrl-single 44e10800.pinmux: pin-95 (4819c000.i2c) status
> -22
> [ 1.769223] pinctrl-single 44e10800.pinmux: could not request pin 95
> (PIN95) from group pinmux_bb_i2c2_pins on device pinctrl-single
> END

^ this is caused by :
pkg:[bb-cape-overlays]:[4.4.20170728.0-0rcnee1~stretch+20170728] (it's
too old)

run:

sudo apt update ; sudo apt upgrade bb-cape-overlay

and reboot:

> I also notices this on the serial console when the board boots:
>
> Starting kernel ...
>
> [ 0.000925] clocksource_probe: no matching clocksources found
> [ 1.369280] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle
> [ 1.648806] omap_voltage_late_init: Voltage driver support not added
> [ 1.656162] PM: Cannot get wkup_m3_ipc handle
> [ 1.750855] pinctrl-single 44e10800.pinmux: pin PIN95 already requested
> by ocp:P9_19_pinmux; cannot claim for 4819c000.i2c
> [ 1.762096] pinctrl-single 44e10800.pinmux: pin-95 (4819c000.i2c) status
> -22
> [ 1.769223] pinctrl-single 44e10800.pinmux: could not request pin 95
> (PIN95) from group pinmux_bb_i2c2_pins on device pinctrl-single
> [ 1.781311] omap_i2c 4819c000.i2c: Error applying setting, reverse things
> back
> [ 1.792167] PM: Cannot get wkup_m3_ipc handle
>
> Do I need to change something?
>
> Also, is there any documentation on what packages can be safely removed from
> this image for the BeagleBone Black? The image is pretty bloated:
>
> $ df | grep /dev/mmc
> /dev/mmcblk1p1 3704040 2927544 568624 84% /

If you want "x11 and the lcd screen" you can use the "2gb" lxqt image:

https://rcn-ee.net/rootfs/bb.org/testing/2018-01-14/stretch-lxqt-2gb/

If you don't care about x11, and just using the fb on the lcd screen,
grab the iot or console variant:

https://rcn-ee.net/rootfs/bb.org/testing/2018-01-14/stretch-iot/

https://rcn-ee.net/rootfs/bb.org/testing/2018-01-14/stretch-console/

Regards,

--
Robert Nelson
https://rcn-ee.com/

[Hartley Sweeten]

On Wednesday, January 17, 2018 at 12:42:03 PM UTC-7, RobertCNelson wrote:

If you want "x11 and the lcd screen" you can use the "2gb" lxqt image:

https://rcn-ee.net/rootfs/bb.org/testing/2018-01-14/stretch-lxqt-2gb/

If you don't care about x11, and just using the fb on the lcd screen,
grab the iot or console variant:

https://rcn-ee.net/rootfs/bb.org/testing/2018-01-14/stretch-iot/

https://rcn-ee.net/rootfs/bb.org/testing/2018-01-14/stretch-console/

Hi Robert,

Would it be possible to add a link to the BeagleBoard.org "lastest images" page to your "testing" repos?

It would be nice if the link was obvious, maybe right after between "official" images and the "older" images.

For some reason I always forget where they are... ;-)

Regards,

Hartley 

[Robert Nelson]

They are also linked from:

https://elinux.org/Beagleboard:BeagleBoneBlack_Debian

(which is the link that shows up when you login to your board over serial.)

I update the links every week..

[mfv...@gmail.com]

Also trying to get the "config-pin P9_12 in" to work, so followed the instruction to upgrade the bb-cape-overlays . 

Running fresh 9.1 LXQT with NH7C LCD , executing commands

sudo apt update ; sudo apt upgrade bb-cape-overlays breaks the install.

Errors were encountered while processing:

 /tmp/apt-dpkg-install-6yp8BP/035-chromium_63.0.3239.84-1~deb9u1rcnee0~stretch+20171227_armhf.deb

E: Sub-process /usr/bin/dpkg returned an error code (1)

You might want to run 'apt --fix-broken install' to correct these.

The following packages have unmet dependencies:

 chromium : Depends: chromium-common (= 60.0.3112.78-1rcnee0~stretch+20170806) but 61.0.3163.100-2rcnee0~stretch+20170927 is installed

E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).

debian@beaglebone:~$ sudo apt --fix-broken install

dpkg: error processing archive /var/cache/apt/archives/chromium_63.0.3239.84-1~deb9u1rcnee0~stretch+20171227_armhf.deb (--unpack):

 trying to overwrite '/usr/lib/chromium/natives_blob.bin', which is also in package chromium-common 61.0.3163.100-2rcnee0~stretch+20170927

dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

Errors were encountered while processing:

 /var/cache/apt/archives/chromium_63.0.3239.84-1~deb9u1rcnee0~stretch+20171227_armhf.deb

E: Sub-process /usr/bin/dpkg returned an error code (1)

Still not clear to me why a fresh install seems to load the cape-universal but the results not visible in /sys/class/gpio , I only see :

debian@beaglebone:/sys/class/gpio$ ls -la

total 0

drwxrwxr-x  2 root gpio    0 Jan 27 19:16 .

drwxr-xr-x 58 root root    0 Jan  1  2000 ..

-rw-rw----  1 root gpio 4096 Jan 27 19:16 export

lrwxrwxrwx  1 root gpio    0 Jan 27 19:16 gpiochip0 -> ../../devices/platform/ocp/44e07000.gpio/gpio/gpiochip0

lrwxrwxrwx  1 root gpio    0 Jan 27 19:16 gpiochip32 -> ../../devices/platform/ocp/4804c000.gpio/gpio/gpiochip32

lrwxrwxrwx  1 root gpio    0 Jan 27 19:16 gpiochip64 -> ../../devices/platform/ocp/481ac000.gpio/gpio/gpiochip64

lrwxrwxrwx  1 root gpio    0 Jan 27 19:16 gpiochip96 -> ../../devices/platform/ocp/481ae000.gpio/gpio/gpiochip96

-rw-rw----  1 root gpio 4096 Jan 27 19:16 unexport

 
Can you help?  Thanks, Maurice

debian@beaglebone:/opt/scripts/tools$ sudo ./version.sh

git:/opt/scripts/:[2ce750d881941c5189db9e189af90517e11c079f]

eeprom:[A335BNLT000C1750BBBG0502]

dogtag:[BeagleBoard.org Debian Image 2017-08-31]

bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 2017.09-rc2-00002-g7c9353]

kernel:[4.9.45-ti-r57]

nodejs:[v6.12.3]

uboot_overlay_options:[enable_uboot_overlays=1]

pkg:[bb-cape-overlays]:[4.4.20180126.0-0rcnee0~stretch+20180126]

pkg:[bb-wl18xx-firmware]:[1.20170829-0rcnee2~stretch+20180104]

pkg:[firmware-ti-connectivity]:[20170823-1rcnee0~stretch+20170830]

debian@beaglebone:/opt/scripts/tools$ sudo nano /boot/uEnv.txt

#Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0

uname_r=4.9.45-ti-r57

#uuid=

#dtb=

###U-Boot Overlays###

###Documentation: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays

###Master Enable

enable_uboot_overlays=1

###

###Overide capes with eeprom

#uboot_overlay_addr0=/lib/firmware/<file0>.dtbo

#uboot_overlay_addr1=/lib/firmware/<file1>.dtbo

#uboot_overlay_addr2=/lib/firmware/<file2>.dtbo

#uboot_overlay_addr3=/lib/firmware/<file3>.dtbo

###

###Additional custom capes

#uboot_overlay_addr4=/lib/firmware/<file4>.dtbo

#uboot_overlay_addr5=/lib/firmware/<file5>.dtbo

#uboot_overlay_addr6=/lib/firmware/<file6>.dtbo

#uboot_overlay_addr7=/lib/firmware/<file7>.dtbo

###

###Custom Cape

#dtb_overlay=/lib/firmware/<file8>.dtbo

###

###Disable auto loading of virtual capes (emmc/video/wireless/adc)

#disable_uboot_overlay_emmc=1

#disable_uboot_overlay_video=1

#disable_uboot_overlay_audio=1

#disable_uboot_overlay_wireless=1

#disable_uboot_overlay_adc=1

###

###PRUSS OPTIONS

###pru_rproc (4.4.x-ti kernel)

#uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-4-TI-00A0.dtbo

###pru_uio (4.4.x-ti & mainline/bone kernel)

#uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo

###

###Cape Universal Enable

#enable_uboot_cape_universal=1

###

###Debug: disable uboot autoload of Cape

#disable_uboot_overlay_addr0=1

#disable_uboot_overlay_addr1=1

#disable_uboot_overlay_addr2=1

#disable_uboot_overlay_addr3=1

###

###U-Boot fdt tweaks...

#uboot_fdt_buffer=0x60000

###U-Boot Overlays###

cmdline=coherent_pool=1M net.ifnames=0 quiet

#In the event of edid real failures, uncomment this next line:

#cmdline=coherent_pool=1M net.ifnames=0 quiet video=HDMI-A-1:1024x768@60e

##Example v3.8.x

#cape_disable=capemgr.disable_partno=

#cape_enable=capemgr.enable_partno=

##Example v4.1.x

#cape_disable=bone_capemgr.disable_partno=

#cape_enable=bone_capemgr.enable_partno=cape_universal

##enable Generic eMMC Flasher:

##make sure, these tools are installed: dosfstools rsync

#cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh

Op woensdag 17 januari 2018 20:42:03 UTC+1 schreef RobertCNelson: