View previous topic :: View next topic |
Author |
Message |
nialv7 n00b
Joined: 19 Feb 2014 Posts: 2
|
Posted: Wed Feb 19, 2014 5:24 pm Post subject: |
|
|
I think the flood of power_supply messages indicates some process is constantly reading the power_supply uevent file.
And it's a little bit weird that if i stop systemd-journald, the flood goes away.
And I think this problem is far from "[SOLVED]" |
|
Back to top |
|
|
nialv7 n00b
Joined: 19 Feb 2014 Posts: 2
|
Posted: Wed Feb 19, 2014 5:40 pm Post subject: |
|
|
A better workaround is to disable CONFIG_POWER_SUPPLY_DEBUG in your kernel. Though this doesn't solve the real problem. |
|
Back to top |
|
|
Bartlomiej_G n00b
Joined: 27 Mar 2014 Posts: 1
|
Posted: Thu Mar 27, 2014 11:50 am Post subject: |
|
|
Either delete those lines:
drivers/power/power_supply_sysfs.c:272: dev_dbg(dev, "uevent\n");
drivers/power/power_supply_sysfs.c-275- dev_dbg(dev, "No power supply yet\n");
drivers/power/power_supply_sysfs.c-279- dev_dbg(dev, "POWER_SUPPLY_NAME=%s\n", psy->name);
or change them to e.g. pr_debug("uevent\n"); If You wish to keep some output,
or disable CONFIG_POWER_SUPPLY_DEBUG in your config file as suggested by nialv7.
I have the same behaviour with CONFIG_I2C_DEBUG_CORE flag when using I2C eeprom on embedded system, I`ve spent 2 weeks figuring out what is wrong and how to omit the situation.
dev_dbg triggers journald to read uevent file, which invokes dev_dbg -> generating an cyclic graph (loop)
I wonder whether this should be reported as a bug in kernel or in systemd-journal |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|