Tons of spam in syslog from irqbalance on the raspi3
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
irqbalance (Ubuntu) |
Fix Released
|
Medium
|
Dave Jones | ||
Bionic |
Fix Released
|
Medium
|
Unassigned | ||
Cosmic |
Fix Released
|
Low
|
Unassigned |
Bug Description
[Impact]
The scanning code for /proc/interrupts has an issue whereby, if the system doesn't contain a pci bus, all other interrupts are skipped in their addition to the irq database. This means nothing gets balanced, and we constantly just rescan. This also causes constant spam appearing in the device's syslog.
[Test Case]
* Flash a Raspberry Pi 3 device with the current beta image [1].
* Boot it up and notice the irqbalance spam in the syslog
* Update irqbalance from -proposed and reboot
* Confirm no additional irqbalance spam appears in syslog
Please note that we do not intend to build raspi3 images for cosmic so validation of this bug on this platform cannot be performed. A sanity-check of the binaries needs to be sufficient for verification.
[Regression Potential]
Fix comes from upstream's 1.5 version so it have a relatively small regression potential (already in Debian and disco). But possible regressions can appear in the irq classification code, with interrupts not getting scanned.
Fixed in 1.5.0. Also, uploading packages prepared by Dave for both bionic and disco - although we can only validate this on a bionic device. Disco synced for SRU consistency across upgrades.