irqbalance crashes when CPUs are taken offline manually

Bug #1500006 reported by Martin Vysny
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
irqbalance (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

I have the following stuff in my /etc/rc.local, to disable hyperthreading:

echo 0 >/sys/devices/system/cpu/cpu1/online
echo 1 >/sys/devices/system/cpu/cpu2/online
echo 0 >/sys/devices/system/cpu/cpu3/online
echo 1 >/sys/devices/system/cpu/cpu4/online
echo 0 >/sys/devices/system/cpu/cpu5/online
echo 1 >/sys/devices/system/cpu/cpu6/online
echo 0 >/sys/devices/system/cpu/cpu7/online

HT cannot be disabled in my bios, unfortunately. With this stuff in /etc/rc.local, irqbalance tend to crash.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: irqbalance 1.0.6-3ubuntu1.1
ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
Uname: Linux 3.19.0-28-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.5
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Sep 26 13:47:54 2015
InstallationDate: Installed on 2014-03-07 (567 days ago)
InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 (20130423.1)
SourcePackage: irqbalance
UpgradeStatus: Upgraded to vivid on 2015-05-02 (146 days ago)

Revision history for this message
Martin Vysny (vyzivus) wrote :
Revision history for this message
Robie Basak (racb) wrote :

Importance: Low since this is an unusual user configuration which I don't think is likely to affect many users.

It might be worth testing the latest upstream release and reporting upstream if it is affected.

summary: - irqbalance crashes
+ irqbalance crashes when CPUs are taken offline manually
Changed in irqbalance (Ubuntu):
importance: Undecided → Low
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in irqbalance (Ubuntu):
status: New → Confirmed
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

This is dormant for way too long, and IMHO should be reported upstream and linked here.
Once upstream has a fix it will be picked up by the next merge and from there be considered as an SRU.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.