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


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/da6e2f66-ab7d-4149-b25b-99cced5935a5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to