openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Zev Weiss <zev@bewilderbeest.net>
To: openbmc@lists.ozlabs.org, linux-aspeed@lists.ozlabs.org
Cc: Andrew Jeffery <andrew@aj.id.au>,
	Jammy Huang <jammy_huang@aspeedtech.com>,
	Eddie James <eajames@linux.ibm.com>,
	Joel Stanley <joel@jms.id.au>
Subject: Log spam from aspeed-video driver
Date: Mon, 24 Oct 2022 20:28:54 -0700	[thread overview]
Message-ID: <Y1dX9r9ybGjBrW0k@hatter.bewilderbeest.net> (raw)

Hi all,

Since the recent update of the OpenBMC kernel to 6.0, I've been seeing a 
lot of new log noise from aspeed-video driver when the host is powered 
off after having been on:

     [  335.526279] aspeed-video 1e700000.video: Timed out; first mode detect
     [  335.544172] aspeed-video 1e700000.video: No signal; don't start frame
     [  337.165555] aspeed-video 1e700000.video: Timed out; first mode detect
     [  337.186214] aspeed-video 1e700000.video: No signal; don't start frame
     [  338.815501] aspeed-video 1e700000.video: Timed out; first mode detect
     [  338.834008] aspeed-video 1e700000.video: No signal; don't start frame

It just emits that pair of messages continuously, about every 1.6 
seconds.

Looking through the commit history of the driver, it looks like that 
stems from commit a3de90afe392 ("media: aspeed: use 
v4l2_info/v4l2_warn/v4l2_dbg for log"), which converted a bunch of print 
calls from dev_dbg() to various v4l2_*() calls.  Reverting to the old 
5.15 kernel (which didn't include that change), I found by enabling the 
dev_dbg() prints via sysfs (and cranking up the console loglevel) that 
the conditions triggering those messages have been happening all along, 
I just hadn't been seeing them because the debug prints were disabled by 
default.

I should note that aside from the dmesg spam I don't see any functional 
problems with the driver; obmc-ikvm works as expected.

Was switching those dev_dbg() calls to v4l2_warn() instead of v4l2_dbg() 
intentional?  Does this indicate some latent bug that should be fixed, 
or should they just be converted to v4l2_dbg()?


Thanks,
Zev


             reply	other threads:[~2022-10-25  3:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-25  3:28 Zev Weiss [this message]
2022-11-09 22:48 ` Log spam from aspeed-video driver Zev Weiss
2022-11-09 23:54 ` Joel Stanley
2022-11-10  2:24   ` Jammy Huang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y1dX9r9ybGjBrW0k@hatter.bewilderbeest.net \
    --to=zev@bewilderbeest.net \
    --cc=andrew@aj.id.au \
    --cc=eajames@linux.ibm.com \
    --cc=jammy_huang@aspeedtech.com \
    --cc=joel@jms.id.au \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=openbmc@lists.ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).