[beagleboard] kern.log getting spammed with omap_hsmmc invalid cookie message

[eblumster]

Hello

I am using a BeagleBone Black for some remote data reading purposes.

Every once and a while the device space will completely fill up very 
rapidly and it seems like the culprit is kern.log (and syslog) getting 
spammed with the same message:

ubuntu@BBB-00946:/var/log$ tail -f kern.log
Mar 20 21:36:26 BBB-00946 kernel: [10458038.623874] omap_hsmmc 
481d8000.mmc: [omap_hsmmc_pre_dma_transfer] invalid cookie: 
data->host_cookie 1 host->next_data.cookie -2146723116
Mar 20 21:36:26 BBB-00946 kernel: [10458038.624084] omap_hsmmc 
481d8000.mmc: [omap_hsmmc_pre_dma_transfer] invalid cookie: 
data->host_cookie 1 host->next_data.cookie -2146723115
Mar 20 21:36:26 BBB-00946 kernel: [10458038.624292] omap_hsmmc 
481d8000.mmc: [omap_hsmmc_pre_dma_transfer] invalid cookie: 
data->host_cookie 1 host->next_data.cookie -2146723114
Mar 20 21:36:26 BBB-00946 kernel: [10458038.624672] omap_hsmmc 
481d8000.mmc: [omap_hsmmc_pre_dma_transfer] invalid cookie: 
data->host_cookie 1 host->next_data.cookie -2146723113
Mar 20 21:36:26 BBB-00946 kernel: [10458038.636575] omap_hsmmc 
481d8000.mmc: [omap_hsmmc_pre_dma_transfer] invalid cookie: 
data->host_cookie 1 host->next_data.cookie -2146723112
Mar 20 21:36:26 BBB-00946 kernel: [10458038.659169] omap_hsmmc 
481d8000.mmc: [omap_hsmmc_pre_dma_transfer] invalid cookie: 
data->host_cookie 1 host->next_data.cookie -2146723111
Mar 20 21:36:26 BBB-00946 kernel: [10458038.661684] omap_hsmmc 
481d8000.mmc: [omap_hsmmc_pre_dma_transfer] invalid cookie: 
data->host_cookie 1 host->next_data.cookie -2146723110
Mar 20 21:36:26 BBB-00946 kernel: [10458038.671142] omap_hsmmc 
481d8000.mmc: [omap_hsmmc_pre_dma_transfer] invalid cookie: 
data->host_cookie 1 host->next_data.cookie -2146723109
Mar 20 21:36:26 BBB-00946 kernel: [10458038.672614] omap_hsmmc 
481d8000.mmc: [omap_hsmmc_pre_dma_transfer] invalid cookie: 
data->host_cookie 1 host->next_data.cookie -2146723108
Mar 20 21:36:26 BBB-00946 kernel: [10458038.676891] omap_hsmmc 
481d8000.mmc: [omap_hsmmc_pre_dma_transfer] invalid cookie: 
data->host_cookie 1 host->next_data.cookie -2146723107
Mar 20 21:36:26 BBB-00946 kernel: [10458038.677989] omap_hsmmc 
481d8000.mmc: [omap_hsmmc_pre_dma_transfer] invalid cookie: 
data->host_cookie 1 host->next_data.cookie -2146723106
Mar 20 21:36:26 BBB-00946 kernel: [10458038.683226] omap_hsmmc 
481d8000.mmc: [omap_hsmmc_pre_dma_transfer] invalid cookie: 
data->host_cookie 1 host->next_data.cookie -2146723105
Mar 20 21:36:26 BBB-00946 kernel: [10458038.683726] omap_hsmmc 
481d8000.mmc: [omap_hsmmc_pre_dma_transfer] invalid cookie: 
data->host_cookie 1 host->next_data.cookie -2146723104
Mar 20 21:36:26 BBB-00946 kernel: [10458038.683957] omap_hsmmc 
481d8000.mmc: [omap_hsmmc_pre_dma_transfer] invalid cookie: 
data->host_cookie 1 host->next_data.cookie -2146723103
Mar 20 21:36:26 BBB-00946 kernel: [10458038.684170] omap_hsmmc 
481d8000.mmc: [omap_hsmmc_pre_dma_transfer] invalid cookie: 
data->host_cookie 1 host->next_data.cookie -2146723102
Mar 20 21:36:26 BBB-00946 kernel: [10458038.684557] omap_hsmmc 
481d8000.mmc: [omap_hsmmc_pre_dma_transfer] invalid cookie: 
data->host_cookie 1 host->next_data.cookie -2146723101
...

clearing the log file and rebooting the system fixes the issue at least for 
awhile but I would like to understand what is happening.

Does anybody know where this is coming from and what the best way to deal 
with it is?

some system info
ubuntu@BBB-00946:/var/log$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.5 LTS
Release: 16.04
Codename: xenial

ubuntu@BBB-00946:/var/log$ uname -a
Linux BBB-00946 4.14.24-ti-r37 #1 SMP Thu Mar 8 00:36:50 UTC 2018 armv7l 
armv7l armv7l GNU/Linux

let me know if there is any other info I can provide.

thanks
- Eric

-- 
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/44301c55-9c1d-4e5b-ab6a-b3abbbdfbadf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Trouble flashing a new Beagle board

[poughkeepsiebob]

I recently bought a BeagleBone Green model to replace one with a bad 
network card. It's meant to be connected to a KiwiSDR radio receiver.
(see http://www.kiwisdr.com). I've downloaded the Kiwi software image on to 
an SD card, but whenever I boot the board (either powered by USB or 
connected to the radio board) the SD card flashing never finishes. It just 
stays blinking on and off. 

   Actually, I'd like to copy the whole image from the BeagleBone that had 
the network issue to the new one, as it has all of my configuration as well 
as the software, but failing that, is there another way to copy the data 
directly to the board?

-- 
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/995b0e8c-ccd7-43fc-9021-896d4b645b8d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: gig ethernet

[graham]

Is that a POE switch? Or a POE port being used on the switch.
That could make bad things happen.
I run all my Beagles on a Cisco Gb managed switch without problems.
Of course they negotiate back to 100 Mb.
--- Graham

== 

On Wednesday, March 20, 2019 at 4:04:15 PM UTC-5, Wulf Man wrote:
>
> Has anybody had any issues connecting a beaglebone to a gig switch ? 
> We plugged a unit into a trendnet 4 port gig switch and the beaglebone 
> does a reboot over and over. I traced it to R137 connecting ethernet port 
> pins 5 and 4 to VDD_PHYA which is the beaglebone VDD_3V3B through an 
> inductor 
> shorting out the supply. 
>
> It seems to me that the switch should not do this. 
> Unfortunately the unit is 2000 miles away. 
>
> any thoughts ? 
>
>

-- 
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/c745c365-52f4-4511-83ba-95b05bd8a6ed%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] gig ethernet

[evilwulfie]

Has anybody had any issues connecting a beaglebone to a gig switch ?
We plugged a unit into a trendnet 4 port gig switch and the beaglebone
does a reboot over and over. I traced it to R137 connecting ethernet port
pins 5 and 4 to VDD_PHYA which is the beaglebone VDD_3V3B through an 
inductor

shorting out the supply.

It seems to me that the switch should not do this.
Unfortunately the unit is 2000 miles away.

any thoughts ?

--
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/b19c9c50-f271-0a9b-08a2-3e284772fce1%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] GPIO input error : Set gpio mode failed, missing file or invalid permissions.

[gupta niks]

I'm using Adafruit_BBIO python library for GPIO Input. Cape Universal.dtb 
is disabled.
Output works fine but INput throws the error. *ValueError: Set gpio mode 
failed, missing file or invalid permissions.*
Below is dts for the gpio input

/dts-v1/;

/ {
compatible = "ti,beaglebone", "ti,beaglebone-black";
part-number = "gpiotest-00A0";
version = "00A0";

fragment@0 {
target = <0x>;

__overlay__ {

gpiotest_Pins {
pinctrl-single,pins = <0x2c 0x37 0x8c 0x37 0x20 0x37 0xcc 
0x37 0xc8 0x37>;
linux,phandle = <0x1>;
phandle = <0x1>;
};
};
};

fragment@1 {
target = <0x>;

__overlay__ {

helper {
compatible = "bone-pinmux-helper";
pinctrl-names = "default";
pinctrl-0 = <0x1>;
status = "okay";
};
};
};

__fixups__ {
am33xx_pinmux = "/fragment@0:target:0";
ocp = "/fragment@1:target:0";
};

__local_fixups__ {

fragment@1 {

__overlay__ {

helper {
pinctrl-0 = <0x0>;
};
};
};
};
};


Please suggest the issue and help with the solution.
Thank You.

-- 
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/744bb7b5-4a96-455d-8406-79a87b3cf174%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] How use SGX / PowerVR on BBB in 2019 ?

[devminnov]

Hi Robert,

Thank you very much, it's a very good news!

I edited the wiki page's to add "Fast installation with deb files 

".
I reconfigured all packages with --libdir and --prefix arguments to not 
need to edit the config file /etc/ld.so.conf.d/arm-linux-gnueabihf.conf.
I built deb package with checkinstall command's but there are no 
documentations files or dependency... I still have a lot to learn about 
linux ^^

Le mardi 19 mars 2019 22:04:32 UTC+1, RobertCNelson a écrit :
>
> Hi Rémi, 
>
> On Sun, Mar 17, 2019 at 10:22 PM > wrote: 
> > 
> > I detail how use the new SGX drivers, the link is here: 
> > https://elinux.org/BeagleBoneBlack/SGX_%2B_Qt_EGLFS_%2B_Weston 
> > 
> > What do you think Robert? Do you think that the SGX drivers /GBM and 
> Weston patched can appear in an official version of the BeagleBone? 
> > 
> > I think it's important to have these tools especially with the arrival 
> of the next generation of BeagleBone. Many people need the GUI. 
> > 
> > I hope this will help some people. 
>
> This is awesome, what you've done! 
>
> I'll start packing some of the bits you utilized, so we can get this 
> out into the apt repo.. 
>
> Regards, 
>
> -- 
> Robert Nelson 
> https://rcn-ee.com/ 
>

-- 
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/fb0cda5d-e006-4049-9bd8-bcc03a1dcc54%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BB blue: make-microSD-flasher-from-eMMC produces a fs with all sort of errors

[ithinu]

I attach a log with the output of 
/opt/scripts/tools/eMMC/beaglebone-black-make-microSD-flasher-from-eMMC.sh 
and a fragment of output of e2fsck -f /dev/mmcblk0p1.

BBB can boot from it, then it gets slowly worse until halt. Still, BBB 
works normally with its eMMC. One of the reasons might be, that 
/dev/mmcblk0p1 is reported as having 4GB or 16GB, depending on the software.



Unattached inode 793363
Connect to /lost+found? yes

Inode 793363 ref count is 2, should be 1.  Fix? yes

Unattached inode 793364
Connect to /lost+found? yes

Inode 793364 ref count is 2, should be 1.  Fix? yes

Unattached inode 793365
Connect to /lost+found? yes

Inode 793365 ref count is 2, should be 1.  Fix? yes

Unattached inode 793366
Connect to /lost+found? yes

Inode 793366 ref count is 2, should be 1.  Fix? yes

Unattached inode 793367
Connect to /lost+found? yes

Inode 793367 ref count is 2, should be 1.  Fix? yes

Unattached inode 793368
Connect to /lost+found? yes

Inode 793368 ref count is 2, should be 1.  Fix? yes

Unattached inode 793369
Connect to /lost+found? yes

Inode 793369 ref count is 2, should be 1.  Fix? yes

Unattached inode 793370
Connect to /lost+found? yes

Inode 793370 ref count is 2, should be 1.  Fix? yes

Inode 793421 ref count is 1, should be 2.  Fix? yes

Inode 794552 ref count is 6, should be 4.  Fix? yes

Inode 794553 ref count is 6, should be 4.  Fix? yes

Inode 794554 ref count is 6, should be 4.  Fix? yes

Inode 794555 ref count is 6, should be 4.  Fix? yes

Unattached inode 794592
Connect to /lost+found? yes

Inode 794592 ref count is 2, should be 1.  Fix? yes

Unattached inode 794600
Connect to /lost+found? yes

Inode 794600 ref count is 2, should be 1.  Fix? yes

Unattached inode 794601
Connect to /lost+found? yes

Inode 794601 ref count is 2, should be 1.  Fix? yes

Unattached inode 794605
Connect to /lost+found? yes

Inode 794605 ref count is 2, should be 1.  Fix? yes


-- 
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/ef06a8ba-88e7-4e07-9a5b-72e28ef21b8e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
/opt/scripts/tools/eMMC/beaglebone-black-make-microSD-flasher-from-eMMC.sh 


Starting eMMC Flasher from microSD media
Version: [1.20180412: all ssh regneration override...]



Prepare environment for flashing
Starting at Fri Nov  4 11:31:15 UTC 2016

==> sysctl: vm.min_free_kbytes=[2653]
==> sysctl: setting: [sysctl -w vm.min_free_kbytes=16384]
vm.min_free_kbytes = 16384

==> Determining root drive
==> console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 
root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 
quiet

==> root_drive=[/dev/mmcblk1p1]
> Root drive identified at /dev/mmcblk1p1
==> Determining boot drive
==> Figuring out Source and Destination devices
> Source identified: [/dev/mmcblk1]
> Destination identified: [/dev/mmcblk0]
> Unmounting auto-mounted partitions
==> Figuring out machine
> Machine is TI_AM335x_BeagleBone_Blue
> Machine is compatible with BeagleBone Black

5 4 3 2 1 


Checking running system
==> Copying: [/dev/mmcblk1] -> [/dev/mmcblk0]
==> lsblk:

NAME MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
mmcblk0  179:00 14.9G  0 disk 
└─mmcblk0p1  179:10 14.9G  0 part 
mmcblk1  179:80  3.6G  0 disk 
└─mmcblk1p1  179:90  3.6G  0 part /
mmcblk1boot0 179:16   04M  1 disk 
mmcblk1boot1 179:24   04M  1 disk 
mmcblk1rpmb  179:32   04M  0 disk 

==> df -h | grep rootfs:

==> updating: /boot/initrd.img-4.14.71-ti-r80
update-initramfs: Generating /boot/initrd.img-4.14.71-ti-r80
WARNING: Setting CRYPTSETUP in /etc/initramfs-tools/initramfs.conf is 
deprecated and will stop working in the future. Use 
/etc/cryptsetup-initramfs/conf-hook instead.
cryptsetup: WARNING: failed to detect canonical device of /dev/mmcblk1p1
cryptsetup: WARNING: could not determine root device from /etc/fstab
==> Giving you time to check...
10 9 8 7 6 5 4 3 2 1 

[beagleboard] Re: How to use GPIO as spi chipselect.

[Dave]

Thank you;

I should have thought of that. 

I probably did not because other systems I work with have linux drivers 
that allow configuring any GPIO as a chip select. 

I did think of bit-banging the SPI, This use is not especially high speed. 
Frankly I do not know why the device is SPI. 

-- 
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/551b9aa7-98f9-474c-a043-c62c129025bc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Connecting BBBW with a network

[Lakshana R]

Thanks for correcting me. I'll follow that way hereafter.

On Tue, Mar 19, 2019 at 8:48 PM Dennis Lee Bieber 
wrote:

> On Tue, 19 Mar 2019 18:19:01 +0530, Lakshana R
>  declaimed the
> following:
>
> >Hey,
> >Thanks for reaching out.
> >I get the following information while entering the command you gave me.
> >Is there any problem with the hardware?
> >[image: Screenshot (67).png]
> >
>
> Please -- in the future don't inflict large low-resolution screen
> grabs
> on us... It's a text console -- select the text, copy, and paste into the
> message. It is painful having to save a 30+kB attachment to the computer,
> find the saved file, then open it with a graphics viewer/editor (and later
> delete the attachment), when text is less than 2kB of data. The image is
> also limited to the size of your console whereas text selection can use the
> scroll-back buffer and get a lot more lines.
>
> Based upon the error messages, there is nothing wrong with the
> hardware... But lots wrong with the configuration files (it appears to be
> looking for a configuration file for some VPN connection which is not
> found)
>
> Your image also does not show the results of the version data R.
> Nelson
> requested...
>
>
> >> -- Forwarded message -
> >> From: Robert Nelson 
>
> 
> >>
> >> Let's see your board details:
> >>
> >> sudo /opt/scripts/tools/version.sh
>
> NOTICE how much easier it is to view when cut as text and not as an image
> (I do not have a BBBW, just plain BBB -- and looks like I'm behind a
> release)
> -=-=-=-
> debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh
> [sudo] password for debian:
> git:/opt/scripts/:[31292bce1d4b35b497cc7a013d6d57e7e1f4f5c4]
> eeprom:[A335BNLT000C0615BBBK0412]
> model:[TI_AM335x_BeagleBone_Black]
> dogtag:[BeagleBoard.org Debian Image 2018-06-17]
> bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot
> 2018.03-2-gac9cce7c6a]:[location: dd MBR]
> kernel:[4.14.49-ti-r54]
> nodejs:[v6.17.0]
> uboot_overlay_options:[enable_uboot_overlays=1]
>
> uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo]
> uboot_overlay_options:[enable_uboot_cape_universal=1]
> pkg check: to individually upgrade run: [sudo apt install --only-upgrade
> ]
> pkg:[bb-cape-overlays]:[4.4.20190227.0-0rcnee0~stretch+20190227]
> pkg:[bb-wl18xx-firmware]:[1.20190227.1-0rcnee0~stretch+20190227]
> pkg:[kmod]:[23-2rcnee1~stretch+20171005]
> pkg:[roboticscape]:[0.4.4-git20180608.0-0rcnee0~stretch+20180609]
> pkg:[firmware-ti-connectivity]:[20180825+dfsg-1rcnee1~stretch+20181217]
> groups:[debian : debian adm kmem dialout cdrom floppy audio dip video
> plugdev users systemd-journal i2c bluetooth netdev cloud9ide gpio pwm eqep
> admin spi tisdk weston-launch xenomai]
> cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1
> root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait coherent_pool=1M
> net.ifnames=0 quiet]
> dmesg | grep pinctrl-single
> [1.053586] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size
> 568
> dmesg | grep gpio-of-helper
> [1.060716] gpio-of-helper ocp:cape-universal: ready
> END
> debian@beaglebone:~$
> -=-=-=-=-
>
>
> --
> Wulfraed Dennis Lee Bieber AF6VN
> wlfr...@ix.netcom.comHTTP://wlfraed.home.netcom.com/
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/KiASpaKctaM/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/i5129epos06pd4in79kcltni267i1mev93%404ax.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAO7uA9o0ROEQadXeCk1JTe0MrYOuOASbS3vHPrCTErtReXbc2Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.