AST2500 video engine for KVM trips BMC watchdog

[Jae Hyun Yoo]

Hi Eddie,

On 8/13/2021 1:37 PM, Eddie James wrote:
> I'm trying to solve a problem when the screensaver on the host is
> activated. It seems to continually trigger the mode detection interrupt
> on the BMC. In combination with the user-space application continually
> trying to determine the resolution, it trips the BMC kernel watchdog
> and resets the system. Here are the logs I've captured:
> 
> [ 2049.076692] aspeed-video 1e700000.video: Resolution changed;
> resetting
> [ 2050.091133] aspeed-video 1e700000.video: Timed out; first mode
> detect
> [ 2051.121593] aspeed-video 1e700000.video: Timed out when stopping
> streaming
> [ 2052.121203] aspeed-video 1e700000.video: Timed out; first mode
> detect
> [ 2052.393164] aspeed-video 1e700000.video: Got resolution: 1024x768
> [ 2052.399561] aspeed-video 1e700000.video: Max compressed size: 80000
> [ 2053.343096] aspeed-video 1e700000.video: Resolution changed;
> resetting
> [ 2053.350151] aspeed-video 1e700000.video: Engine busy; don't start
> frame
> [ 2054.361159] aspeed-video 1e700000.video: Timed out; first mode
> detect
> [ 2054.609677] aspeed-video 1e700000.video: Got resolution: 1024x768
> [ 2054.615983] aspeed-video 1e700000.video: Max compressed size: 80000
> [ 2055.409583] aspeed-video 1e700000.video: Resolution changed;
> resetting
> [ 2055.432802] aspeed-video 1e700000.video: No signal; don't start
> frame
> [ 2056.421155] aspeed-video 1e700000.video: Timed out; first mode
> detect
> [ 2056.676215] aspeed-video 1e700000.video: Got resolution: 1024x768
> [ 2056.682516] aspeed-video 1e700000.video: Max compressed size: 80000
> [ 2057.459454] aspeed-video 1e700000.video: Resolution changed;
> resetting
> [ 2057.480919] aspeed-video 1e700000.video: No signal; don't start
> frame
> [ 2058.471187] aspeed-video 1e700000.video: Timed out; first mode
> detect
> [ 2058.726108] aspeed-video 1e700000.video: Got resolution: 1024x768
> [ 2058.732382] aspeed-video 1e700000.video: Max compressed size: 80000
> [ 2059.526704] aspeed-video 1e700000.video: Resolution changed;
> resetting
> [ 2059.548747] aspeed-video 1e700000.video: No signal; don't start
> frame
> [ 2060.541146] aspeed-video 1e700000.video: Timed out; first mode
> detect
> [ 2060.792620] aspeed-video 1e700000.video: Got resolution: 1024x768
> [ 2060.798801] aspeed-video 1e700000.video: Max compressed size: 80000
> [ 2061.592870] aspeed-video 1e700000.video: Resolution changed;
> resetting
> [ 2061.615523] aspeed-video 1e700000.video: No signal; don't start
> frame
> [ 2062.611126] aspeed-video 1e700000.video: Timed out; first mode
> detect
> [ 2062.859185] aspeed-video 1e700000.video: Got resolution: 1024x768
> [ 2062.865483] aspeed-video 1e700000.video: Max compressed size: 80000
> [ 2063.659056] aspeed-video 1e700000.video: Resolution changed;
> resetting
> [ 2063.680423] aspeed-video 1e700000.video: No signal; don't start
> frame
> [ 2064.671148] aspeed-video 1e700000.video: Timed out; first mode
> detect
> [ 2064.925696] aspeed-video 1e700000.video: Got resolution: 1024x768
> [ 2064.931949] aspeed-video 1e700000.video: Max compressed size: 80000
> [ 2065.708903] aspeed-video 1e700000.video: Resolution changed;
> resetting
> [ 2065.716196] aspeed-video 1e700000.video: Engine busy; don't start
> frame
> [ 2066.721161] aspeed-video 1e700000.video: Timed out; first mode
> detect
> [ 2066.975563] aspeed-video 1e700000.video: Got resolution: 1024x768
> [ 2066.981842] aspeed-video 1e700000.video: Max compressed size: 80000
> [ 2067.758808] aspeed-video 1e700000.video: Resolution changed;
> resetting
> [ 2067.766511] aspeed-video 1e700000.video: Engine busy; don't start
> frame
> [ 2068.771128] aspeed-video 1e700000.video: Timed out; first mode
> detect
> [ 2069.025462] aspeed-video 1e700000.video: Got resolution: 1024x768
> [ 2069.031803] aspeed-video 1e700000.video: Max compressed size: 80000
> [ 2069.808665] aspeed-video 1e700000.video: Resolution changed;
> resetting
> 
> Jae, or anyone else, do you have any ideas to solve this? I'm surprised
> it's enough to stop pinging the watchdog, but that is what happens...

Does it mean that this issue blocks watchdog feeding in BMC kernel?
Can you please share more detail information about the host OS, current
resolution, reproduction steps and etc.?

Thanks,
Jae

> 
> Thanks,
> Eddie
>