Hi,
On Mon, Aug 24, 2015 at 5:19 PM, Stephen Boyd wrote:
> Can you add the backtrace?
Good point. Done.
> Perhaps it would be better to add a different function for the kgdb call
> site? Then it's explicit what's going on without us having to figure out
> when in_dbg_master() is true.
Kees,
On Tue, Aug 25, 2015 at 9:50 AM, Kees Cook wrote:
> On Mon, Aug 24, 2015 at 5:19 PM, Stephen Boyd wrote:
>> On 08/24/2015 04:58 PM, Douglas Anderson wrote:
>>>
>>> If we're in kgdb then the machine is already stopped. Trying to stop
>>> it again will cause us to try to sleep, which is
On Mon, Aug 24, 2015 at 5:19 PM, Stephen Boyd wrote:
> On 08/24/2015 04:58 PM, Douglas Anderson wrote:
>>
>> If we're in kgdb then the machine is already stopped. Trying to stop
>> it again will cause us to try to sleep, which is not allowed while in
>> kgdb. To avoid this problem, only stop
On Mon, Aug 24, 2015 at 5:19 PM, Stephen Boyd sb...@codeaurora.org wrote:
On 08/24/2015 04:58 PM, Douglas Anderson wrote:
If we're in kgdb then the machine is already stopped. Trying to stop
it again will cause us to try to sleep, which is not allowed while in
kgdb. To avoid this problem,
Hi,
On Mon, Aug 24, 2015 at 5:19 PM, Stephen Boyd sb...@codeaurora.org wrote:
Can you add the backtrace?
Good point. Done.
Perhaps it would be better to add a different function for the kgdb call
site? Then it's explicit what's going on without us having to figure out
when in_dbg_master()
Kees,
On Tue, Aug 25, 2015 at 9:50 AM, Kees Cook keesc...@chromium.org wrote:
On Mon, Aug 24, 2015 at 5:19 PM, Stephen Boyd sb...@codeaurora.org wrote:
On 08/24/2015 04:58 PM, Douglas Anderson wrote:
If we're in kgdb then the machine is already stopped. Trying to stop
it again will cause us
On 08/24/2015 04:58 PM, Douglas Anderson wrote:
If we're in kgdb then the machine is already stopped. Trying to stop
it again will cause us to try to sleep, which is not allowed while in
kgdb. To avoid this problem, only stop the machine when we're not in
kgdb.
Reported-by: Aapo Vienamo
If we're in kgdb then the machine is already stopped. Trying to stop
it again will cause us to try to sleep, which is not allowed while in
kgdb. To avoid this problem, only stop the machine when we're not in
kgdb.
Reported-by: Aapo Vienamo
Suggested-by: Kees Cook
Signed-off-by: Douglas
On 08/24/2015 04:58 PM, Douglas Anderson wrote:
If we're in kgdb then the machine is already stopped. Trying to stop
it again will cause us to try to sleep, which is not allowed while in
kgdb. To avoid this problem, only stop the machine when we're not in
kgdb.
Reported-by: Aapo Vienamo
If we're in kgdb then the machine is already stopped. Trying to stop
it again will cause us to try to sleep, which is not allowed while in
kgdb. To avoid this problem, only stop the machine when we're not in
kgdb.
Reported-by: Aapo Vienamo avien...@nvidia.com
Suggested-by: Kees Cook
10 matches
Mail list logo