Hello Stan,
Thx for this very clear explanation.
I am now sure my so small server do not require irqbalance.
--
Guy
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
Le 09/05/2013 17:34, Stan Hoeppner a écrit :
Or simply cron a stop/start of irqbalance some x minutes after bootup.
Thank you Stan
I tryied restarting irqbalance on my running system with
/etc/init.d/irqbalance restart
But the warning still appears in the log...
I think I will wait for an
On 5/10/2013 3:39 AM, Guy Marcenac wrote:
Le 09/05/2013 17:34, Stan Hoeppner a écrit :
Or simply cron a stop/start of irqbalance some x minutes after bootup.
Thank you Stan
I tryied restarting irqbalance on my running system with
/etc/init.d/irqbalance restart
But the warning still
Hello,
I have just upgraded to wheezy.
In my daemon .log, I noticed these warnings
May 9 10:00:15 kim2 /usr/sbin/irqbalance: WARNING: MSI interrupts found
in /proc/interrupts
May 9 10:00:15 kim2 /usr/sbin/irqbalance: But none found in sysfs, you
need to update your kernel
May 9 10:00:15
On 05/09/2013 01:05 PM, Guy Marcenac wrote:
Hello,
I have just upgraded to wheezy.
In my daemon .log, I noticed these warnings
May 9 10:00:15 kim2 /usr/sbin/irqbalance: WARNING: MSI interrupts found
in /proc/interrupts
May 9 10:00:15 kim2 /usr/sbin/irqbalance: But none found in sysfs,
to update your kernel
May 9 10:00:15 kim2 /usr/sbin/irqbalance: Until then, IRQs will be
improperly classified
See:
https://code.google.com/p/irqbalance/source/detail?r=1523a7830cb2670cb531a5fdea86885eaa648eafpath=/procinterrupts.c
The rescan patch is not included in Wheezy irqbalance 1.0.3-3
is not included in Wheezy irqbalance 1.0.3-3. What is
happening is that your device MSIs aren't being registered before
irqbalance does its initial scan, so it doesn't find them in sysfs.
This rescan patch was designed to allow for recreating the IRQ map after
a hotplug event, such as a CPU
7 matches
Mail list logo
