Multiple drm_ioctl messages coming in since 3.8.11 to 3.8.13 upgrade

GoogleGroups
1

I have upgraded today my BBB from 3.8.11 to 3.8.13, and i now get huge volume of the following messages in DMESG:
I did not have these message before… any idea what they are related to? Can i stop them somehow?

[ 258.682179] [drm:drm_ioctl], ret = -38
[ 258.713158] [drm:drm_ioctl], pid=235, cmd=0xc01864b1, nr=0xb1, dev 0xe200, auth=1
[ 258.713216] [drm:drm_ioctl], ret = -38
[ 261.609417] [drm:output_poll_execute], [CONNECTOR:5:HDMI-A-1] status updated from 1 to 1
[ 261.836412] [drm:drm_ioctl], pid=235, cmd=0xc01864b1, nr=0xb1, dev 0xe200, auth=1
[ 261.836462] [drm:drm_ioctl], ret = -38
[ 261.868696] [drm:drm_ioctl], pid=235, cmd=0xc01864b1, nr=0xb1, dev 0xe200, auth=1
[ 261.868755] [drm:drm_ioctl], ret = -38
[ 262.059642] [drm:drm_ioctl], pid=235, cmd=0xc01864b1, nr=0xb1, dev 0xe200, auth=1
[ 262.059690] [drm:drm_ioctl], ret = -38
[ 262.471276] [drm:drm_ioctl], pid=235, cmd=0xc01864b1, nr=0xb1, dev 0xe200, auth=1
[ 262.471326] [drm:drm_ioctl], ret = -38
[ 262.502293] [drm:drm_ioctl], pid=235, cmd=0xc01864b1, nr=0xb1, dev 0xe200, auth=1
[ 262.502350] [drm:drm_ioctl], ret = -38
[ 265.627155] [drm:drm_ioctl], pid=235, cmd=0xc01864b1, nr=0xb1, dev 0xe200, auth=1
[ 265.627206] [drm:drm_ioctl], ret = -38
[ 265.658980] [drm:drm_ioctl], pid=235, cmd=0xc01864b1, nr=0xb1, dev 0xe200, auth=1
[ 265.659038] [drm:drm_ioctl], ret = -38
[ 271.146100] [drm:drm_ioctl], pid=235, cmd=0xc01864b1, nr=0xb1, dev 0xe200, auth=1
[ 271.146146] [drm:drm_ioctl], ret = -38
[ 271.640665] [drm:output_poll_execute], [CONNECTOR:5:HDMI-A-1] status updated from 1 to 1
[ 273.819832] [drm:drm_ioctl], pid=235, cmd=0xc01864b1, nr=0xb1, dev 0xe200, auth=1
[ 273.819880] [drm:drm_ioctl], ret = -38
[ 274.169075] [drm:drm_ioctl], pid=235, cmd=0xc01864b1, nr=0xb1, dev 0xe200, auth=1
[ 274.169123] [drm:drm_ioctl], ret = -38
[ 274.349132] [drm:drm_ioctl], pid=235, cmd=0xc01864b1, nr=0xb1, dev 0xe200, auth=1
[ 274.349179] [drm:drm_ioctl], ret = -38
[ 274.818999] [drm:drm_ioctl], pid=235, cmd=0xc01864b1, nr=0xb1, dev 0xe200, auth=1
[ 274.819046] [drm:drm_ioctl], ret = -38
[ 275.629292] [drm:drm_ioctl], pid=235, cmd=0xc01864b1, nr=0xb1, dev 0xe200, auth=1
[ 275.629341] [drm:drm_ioctl], ret = -38

dmesg.txt (1.96 KB)

2

Have a look at the contents of the file /media/BEAGLEBONE/uEnv.txt. This adds a drm debug parameter to the kernel command line.

optargs=quiet drm.debug=7

I removed the drm entry, saved the file and rebooted. However, it didn’t seem to want to boot up again correctly and I needed to hit the reset button. Once it had rebooted, /media/BEAGLEBONE was empty. I had to manually mount /dev/mmcblk0p1.

Good luck.

Joshua

3

I can confirm removing “drm.debug=7” from /media/BEAGLEBONE/uEnv.txt and rebooting stops the following messages in dmesg:
[ 90.968971] [drm:output_poll_execute], [CONNECTOR:5:HDMI-A-1] status updated from 2 to 2

I didn’t have any issues with rebooting, but I edited uEnv.txt on the BBB.
FYI /media/BEAGLEBONE can take a little bit of time to mount after boot so it may appear empty for a bit.
-Dale

4

UPDATE: I’ve removed the ‘quiet drm.debug=7’ from the uEnv.txt file and those messages stopped!