Skip to contentSkip to conversation

log spammed from dvb_frontend_get_frequency_limits

DISCUSSION Hans-Peter Jansen 2 participants 2 messages May 28, 2019 Media (V4L/DVB)

lore
Share & tools
lore
#0 lore raw

Hi,

my syslog is continuously spammed with:

2019-05-28T18:45:39.275180+02:00 kernel: [ 5666.337560] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:45:39.279201+02:00 kernel: [ 5666.343778] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:45:39.283157+02:00 kernel: [ 5666.347610] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:45:39.287130+02:00 kernel: [ 5666.351431] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:45:39.291215+02:00 kernel: [ 5666.356031] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:45:41.263233+02:00 kernel: [ 5666.359820] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:46:00.295235+02:00 kernel: [ 5687.357185] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:46:00.297391+02:00 kernel: [ 5687.362397] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:46:00.307104+02:00 kernel: [ 5687.367207] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:46:00.311125+02:00 kernel: [ 5687.374543] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:46:00.319201+02:00 kernel: [ 5687.378651] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:46:06.583637+02:00 kernel: [ 5687.387209] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:46:36.019149+02:00 kernel: [ 5708.370301] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:46:42.335100+02:00 kernel: [ 5729.394246] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:46:42.339235+02:00 kernel: [ 5729.403914] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:46:42.343145+02:00 kernel: [ 5729.408136] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:46:42.347206+02:00 kernel: [ 5729.411843] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:46:42.359164+02:00 kernel: [ 5729.416573] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:46:49.159286+02:00 kernel: [ 5729.428030] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:47:03.343190+02:00 kernel: [ 5750.387217] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:47:03.347127+02:00 kernel: [ 5750.410850] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:47:03.351173+02:00 kernel: [ 5750.415379] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:47:03.355154+02:00 kernel: [ 5750.419946] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:47:03.363228+02:00 kernel: [ 5750.424626] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:47:04.516165+02:00 kernel: [ 5750.429455] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000

Linux kernel 5.1.5

According to https://github.com/torvalds/linux/blob/master/drivers/media/dvb-core/dvb_frontend.c#L908
this is to be expected, but for what reason?

The system is running VDR 2.2.0 with a Digital Devices Max S8.

Shouldn't this dprintk() be converted to dev_dbg(), since it doesn't buy much for usual operation, does it?

While at it, do you have any idea, how to avoid these:

2019-05-28T18:56:11.099140+02:00 kernel: [ 6298.161481] dmxdev: DVB (dvb_dmxdev_filter_start): could not set feed
2019-05-28T18:56:11.099154+02:00 kernel: [ 6298.161487] dvb_demux: dvb_demux_feed_del: feed not in list (type=1 state=0 pid=ffff)

It's significantly less frequent compared to the former call, but also quite nagging.

Thanks for consideration.

Cheers,
Pete

#1 lore raw
Quoted 5 lines · Hans-Peter Jansen

Hi,

my syslog is continuously spammed with:

2019-05-28T18:45:39.275180+02:00 kernel: [ 5666.337560] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000

-snip-

A fix for this is in the queue:
https://git.linuxtv.org/media_tree.git/commit/?h=fixes&id=eb96e57b913ff668b8b804178cdc509f9b3d4472

Thanks,
Sean

Quoted 48 lines
2019-05-28T18:45:39.279201+02:00 kernel: [ 5666.343778] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:45:39.283157+02:00 kernel: [ 5666.347610] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:45:39.287130+02:00 kernel: [ 5666.351431] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:45:39.291215+02:00 kernel: [ 5666.356031] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:45:41.263233+02:00 kernel: [ 5666.359820] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:46:00.295235+02:00 kernel: [ 5687.357185] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:46:00.297391+02:00 kernel: [ 5687.362397] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:46:00.307104+02:00 kernel: [ 5687.367207] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:46:00.311125+02:00 kernel: [ 5687.374543] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:46:00.319201+02:00 kernel: [ 5687.378651] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:46:06.583637+02:00 kernel: [ 5687.387209] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:46:36.019149+02:00 kernel: [ 5708.370301] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:46:42.335100+02:00 kernel: [ 5729.394246] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:46:42.339235+02:00 kernel: [ 5729.403914] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:46:42.343145+02:00 kernel: [ 5729.408136] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:46:42.347206+02:00 kernel: [ 5729.411843] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:46:42.359164+02:00 kernel: [ 5729.416573] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:46:49.159286+02:00 kernel: [ 5729.428030] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:47:03.343190+02:00 kernel: [ 5750.387217] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:47:03.347127+02:00 kernel: [ 5750.410850] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:47:03.351173+02:00 kernel: [ 5750.415379] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:47:03.355154+02:00 kernel: [ 5750.419946] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:47:03.363228+02:00 kernel: [ 5750.424626] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000
2019-05-28T18:47:04.516165+02:00 kernel: [ 5750.429455] dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 0...0, frontend: 300000000...2350000000

Linux kernel 5.1.5

According to https://github.com/torvalds/linux/blob/master/drivers/media/dvb-core/dvb_frontend.c#L908
this is to be expected, but for what reason?

The system is running VDR 2.2.0 with a Digital Devices Max S8.

Shouldn't this dprintk() be converted to dev_dbg(), since it doesn't buy much for usual operation, does it?

While at it, do you have any idea, how to avoid these:

2019-05-28T18:56:11.099140+02:00 kernel: [ 6298.161481] dmxdev: DVB (dvb_dmxdev_filter_start): could not set feed
2019-05-28T18:56:11.099154+02:00 kernel: [ 6298.161487] dvb_demux: dvb_demux_feed_del: feed not in list (type=1 state=0 pid=ffff)

It's significantly less frequent compared to the former call, but also quite nagging.

Thanks for consideration.

Cheers,
Pete