Hello,
there is this WARNING coming "Trying to free already-free IRQ"
but that warning suggests that we are either calling free_irq twice
or
request_irq has not been made.
bu the problem was, free_irq was being called with invalid/NULL device id.
but the warning is misleading which does not hint
akikb...@gmail.com]
Sent: Friday, May 08, 2015 10:42 AM
To: Oza (Pawandeep) Oza
Cc: pawandeep oza; linux-kernel@vger.kernel.org; malayasen rout
Subject: Re: [KERNEL BUG] do_timer/tick_handover_do_timer 3.10.17
On Fri, 2015-05-08 at 04:16 +, Oza (Pawandeep) Oza wrote:
> So Mike, is this reaso
s in this path"
Regards,
-Oza
-----Original Message-
From: Oza (Pawandeep) Oza
Sent: Thursday, May 07, 2015 2:17 PM
To: 'Mike Galbraith'
Cc: pawandeep oza; linux-kernel@vger.kernel.org; malayasen rout
Subject: RE: [KERNEL BUG] do_timer/tick_handover_do_timer 3.10.17
Oh ok.
So the re
-Original Message-
From: Mike Galbraith [mailto:umgwanakikb...@gmail.com]
Sent: Thursday, May 07, 2015 2:00 PM
To: Oza (Pawandeep) Oza
Cc: pawandeep oza; linux-kernel@vger.kernel.org; malayasen rout
Subject: Re: [KERNEL BUG] do_timer/tick_handover_do_timer 3.10.17
On Thu, 2015-05-07 at 07:05 +
u == cpu)
Regards,
-Oza
-Original Message-----
From: Oza (Pawandeep) Oza
Sent: Thursday, May 07, 2015 12:36 PM
To: 'Mike Galbraith'
Cc: pawandeep oza; linux-kernel@vger.kernel.org; malayasen rout
Subject: RE: [KERNEL BUG] do_timer/tick_handover_do_timer 3.10.17
: )
Well, I am not
-Original Message-
From: Mike Galbraith [mailto:umgwanakikb...@gmail.com]
Sent: Thursday, May 07, 2015 12:25 PM
To: Oza (Pawandeep) Oza
Cc: pawandeep oza; linux-kernel@vger.kernel.org; malayasen rout
Subject: Re: [KERNEL BUG] do_timer/tick_handover_do_timer 3.10.17
On Thu, 2015-05-07 at 05:58 +
[mailto:umgwanakikb...@gmail.com]
Sent: Thursday, May 07, 2015 11:25 AM
To: Oza (Pawandeep) Oza
Cc: pawandeep oza; linux-kernel@vger.kernel.org; malayasen rout
Subject: Re: [KERNEL BUG] do_timer/tick_handover_do_timer 3.10.17
On Thu, 2015-05-07 at 05:12 +, Oza (Pawandeep) Oza wrote:
> But after Cr
Crash.
But after Crash, jiffies do not increment.
Regards,
-Oza
-Original Message-
From: Mike Galbraith [mailto:umgwanakikb...@gmail.com]
Sent: Thursday, May 07, 2015 10:39 AM
To: Oza (Pawandeep) Oza
Cc: pawandeep oza; linux-kernel@vger.kernel.org; malayasen rout
Subject: Re: [KERNEL BUG
-
From: Mike Galbraith [mailto:umgwanakikb...@gmail.com]
Sent: Thursday, May 07, 2015 8:53 AM
To: pawandeep oza
Cc: linux-kernel@vger.kernel.org; malayasen rout; Oza (Pawandeep) Oza
Subject: Re: [KERNEL BUG] do_timer/tick_handover_do_timer 3.10.17
On Wed, 2015-05-06 at 22:57 +0530, pawandeep
Hi,
Linux version 3.10.17
Problem Statement: The timekeeping/do_timer seems to be stopped and
the core (in this case it is core0) which is aborting is stuck in the
loop which relies on jiffies.
The root cause/Reason:
we have tickless kernel, so cpu goes to deep idle state, and stop
sched tick.
Hi,
Linux version 3.10.17
Problem Statement: The timekeeping/do_timer seems to be stopped and
the core (in this case it is core0) which is aborting is stuck in the
loop which relies on jiffies.
The root cause/Reason:
we have tickless kernel, so cpu goes to deep idle state, and stop
sched tick.
Hi,
Linux version 3.10.17
Problem Statement: The timekeeping/do_timer seems to be stopped and
the core (in this case it is core0) which is aborting is stuck in the
loop which relies on jiffies.
The root cause/Reason:
we have tickless kernel, so cpu goes to deep idle state, and stop
sched tick.
12 matches
Mail list logo
