Hi, Clemens and others.
On Nov 25 2016, Clemens Ladisch wrote:
> Rogério Brito wrote:
> > [ 130.007219] evbug: Event. Dev: input6, Type: 0, Code: 0, Value: 0
>
> The evbug module is intended for debugging; it dumps all input events
> into syslog. If you do not want these messages, do not
Hi, Clemens and others.
On Nov 25 2016, Clemens Ladisch wrote:
> Rogério Brito wrote:
> > [ 130.007219] evbug: Event. Dev: input6, Type: 0, Code: 0, Value: 0
>
> The evbug module is intended for debugging; it dumps all input events
> into syslog. If you do not want these messages, do not
On Fri, Nov 25, 2016 at 02:53:00PM -0200, Rogério Brito wrote:
> Here is part from /proc/interrupts that contains interrupt 18 *without*
> irqpoll:
>
> ---
>CPU0 CPU1 CPU2 CPU3
> 0: 47 0 0 0
On Fri, Nov 25, 2016 at 02:53:00PM -0200, Rogério Brito wrote:
> Here is part from /proc/interrupts that contains interrupt 18 *without*
> irqpoll:
>
> ---
>CPU0 CPU1 CPU2 CPU3
> 0: 47 0 0 0
Hi, Clemens and Borislav.
On Nov 25 2016, Clemens Ladisch wrote:
> Rogério Brito wrote:
> > * I have never been able to boot this computer of mine without the option
> > irqpoll---otherwise, I get the nobody cared message.
>
> The "nobody cared" message indicates that there were too many
Hi, Clemens and Borislav.
On Nov 25 2016, Clemens Ladisch wrote:
> Rogério Brito wrote:
> > * I have never been able to boot this computer of mine without the option
> > irqpoll---otherwise, I get the nobody cared message.
>
> The "nobody cared" message indicates that there were too many
On Fri, Nov 25, 2016 at 02:05:48PM -0200, Rogério Brito wrote:
> In fact, I have quite a few computers that are not running Linux that well
> at this moment and I guess that lack of report from final users (or,
> perhaps, reports being lost in the way) prevents those problems from getting
> fixed.
On Fri, Nov 25, 2016 at 02:05:48PM -0200, Rogério Brito wrote:
> In fact, I have quite a few computers that are not running Linux that well
> at this moment and I guess that lack of report from final users (or,
> perhaps, reports being lost in the way) prevents those problems from getting
> fixed.
Rogério Brito wrote:
> [ 130.007219] evbug: Event. Dev: input6, Type: 0, Code: 0, Value: 0
The evbug module is intended for debugging; it dumps all input events
into syslog. If you do not want these messages, do not load this module.
(If it is loaded automatically, you have an actual bug.)
Rogério Brito wrote:
> [ 130.007219] evbug: Event. Dev: input6, Type: 0, Code: 0, Value: 0
The evbug module is intended for debugging; it dumps all input events
into syslog. If you do not want these messages, do not load this module.
(If it is loaded automatically, you have an actual bug.)
Dear Boris and Clemens,
First of all, thank you very much for your replies. They are very much
appreciated.
On Nov 25 2016, Borislav Petkov wrote:
> On Thu, Nov 24, 2016 at 09:39:57PM -0200, Rogério Brito wrote:
> > Before I go on describing the problems that I have, I want to say that I can
> >
Dear Boris and Clemens,
First of all, thank you very much for your replies. They are very much
appreciated.
On Nov 25 2016, Borislav Petkov wrote:
> On Thu, Nov 24, 2016 at 09:39:57PM -0200, Rogério Brito wrote:
> > Before I go on describing the problems that I have, I want to say that I can
> >
Rogério Brito wrote:
> * I have never been able to boot this computer of mine without the option
> irqpoll---otherwise, I get the nobody cared message.
The "nobody cared" message indicates that there were too many interrupts
that no driver felt responsible for, so the kernel has disabled that
Rogério Brito wrote:
> * I have never been able to boot this computer of mine without the option
> irqpoll---otherwise, I get the nobody cared message.
The "nobody cared" message indicates that there were too many interrupts
that no driver felt responsible for, so the kernel has disabled that
On Thu, Nov 24, 2016 at 09:39:57PM -0200, Rogério Brito wrote:
> Before I go on describing the problems that I have, I want to say that I can
> bisect the kernel, apply patches and give feedback for the problems that I
> am seeing.
Good. We're going to need them.
Please checkout lates Linus
On Thu, Nov 24, 2016 at 09:39:57PM -0200, Rogério Brito wrote:
> Before I go on describing the problems that I have, I want to say that I can
> bisect the kernel, apply patches and give feedback for the problems that I
> am seeing.
Good. We're going to need them.
Please checkout lates Linus
16 matches
Mail list logo
