This bug was fixed in the package irqbalance - 0.56-0ubuntu1
---
irqbalance (0.56-0ubuntu1) maverick; urgency=low
* New upstream release, this release offers better support for 2.3.35.
* debian/irqbalance.upstart: Dont respawn. (LP: #594509)
* debian/patches/do-irqbalance-pid.pa
Same problem here, started in kernel 2.6.35-2-generic, previous kernels
don't effect.
--
irqbalance main process ended, respawning
https://bugs.launchpad.net/bugs/594509
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
this seems to only be happening on my amd64 maverick desktop, but not on
my i386 lucid laptop, both 1x Core2 Duo.
both have the same irqbalance (0.55+20091017-3ubuntu3), but obv.
different kernels
--
irqbalance main process ended, respawning
https://bugs.launchpad.net/bugs/594509
You received th
** Changed in: irqbalance (Ubuntu Maverick)
Status: Triaged => Confirmed
--
irqbalance main process ended, respawning
https://bugs.launchpad.net/bugs/594509
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
** Also affects: irqbalance (Ubuntu Maverick)
Importance: High
Assignee: Chuck Short (zulcss)
Status: Triaged
** Changed in: irqbalance (Ubuntu Maverick)
Milestone: None => maverick-alpha-2
--
irqbalance main process ended, respawning
https://bugs.launchpad.net/bugs/594509
You
Removing "respawn" from /etc/init/irqbalance.conf should fix it.
** Changed in: irqbalance (Ubuntu)
Importance: Undecided => High
** Changed in: irqbalance (Ubuntu)
Status: New => Triaged
** Changed in: irqbalance (Ubuntu)
Assignee: (unassigned) => Chuck Short (zulcss)
--
irqbal
How can I fix this?
--
irqbalance main process ended, respawning
https://bugs.launchpad.net/bugs/594509
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/ma
Yeah, setting irqbalance to respawn isn't a good idea. If there's only
one core, irqbalance will terminate immediately. If there's only one CPU
(possibly with multiple cores), irqbalance goes into oneshot mode and
will terminate after ~10 seconds of runtime (SLEEP_INTERVAL is 10
seconds and then th
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/50363103/Dependencies.txt
--
irqbalance main process ended, respawning
https://bugs.launchpad.net/bugs/594509
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
u
