On Tue, Jul 7, 2015 at 11:16 AM, Ming Lei <email address hidden> wrote:
> Looks there are two kinds of translation fault from irqbalance:
>
> 1) happend in place_irq_in_node() which can reproduce in vivid package
>
> 2) the 2nd one happened in glib2, which is built by myself, because
> irqbalance can choose to use its own local glib if there isn't glib2 available,
> and the glib2 does exist in my server in which I build irqbalance.
Both of two above reports can be fixed by the following irqbalance commit:
On Tue, Jul 7, 2015 at 11:16 AM, Ming Lei <email address hidden> wrote:
> Looks there are two kinds of translation fault from irqbalance:
>
> 1) happend in place_irq_in_node() which can reproduce in vivid package
>
> 2) the 2nd one happened in glib2, which is built by myself, because
> irqbalance can choose to use its own local glib if there isn't glib2 available,
> and the glib2 does exist in my server in which I build irqbalance.
Both of two above reports can be fixed by the following irqbalance commit:
NUMA is not available fix
https:/ /github. com/Irqbalance/ irqbalance/ commit/ a3c812eb6cd627c d3fae45b8345538 558b86973c
Looks stress-ng can't only find kernel bug, but also userspace
issue, :-)
Thanks,
Ming