From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC 0/4] ARM/KGDB: Some fixes for SMP machines
Date: Thu, 8 Jul 2010 09:48:56 +0100 [thread overview]
Message-ID: <004701cb1e7a$66a78890$33f699b0$@deacon@arm.com> (raw)
In-Reply-To: <20100707171222.GA16448@oksana.dev.rtsoft.ru>
Hi Anton,
> It appears that KGDB can easily hang SMP ARM machines.
Yep. As pointed out at:
http://lkml.org/lkml/2010/4/8/214
Commit ae6bf53e broke kgdb on SMP systems because it incorrectly assumes
that atomic_{inc,dec} imply barriers. Until this is fixed, it will never
work reliably on ARM. Try reverting the patch [this doesn't completely
resolve the situation, but it might help].
> 1. I'm testing with I/D caches disabled. With enabled caches,
> ARMv6K still locks-up. I'll test ARMv7 soon, and will try
> to debug cache issues on ARMv6K.
This patch might help if you're using the ARM11MPCore:
http://lists.infradead.org/pipermail/linux-arm-kernel/2010-May/016567.html
Hope that helps,
Will
next prev parent reply other threads:[~2010-07-08 8:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-07 17:12 [PATCH RFC 0/4] ARM/KGDB: Some fixes for SMP machines Anton Vorontsov
2010-07-07 17:12 ` Anton Vorontsov
2010-07-07 17:13 ` [PATCH RFC 1/4] ARM: kgdb: Must poll for IPIs during busy-waiting Anton Vorontsov
2010-07-07 17:13 ` Anton Vorontsov
2010-07-07 17:13 ` [PATCH RFC 2/4] ARM: kgdb: Disable preemption before re-enabling interrupts Anton Vorontsov
2010-07-07 17:13 ` Anton Vorontsov
2010-07-07 17:13 ` [PATCH RFC 3/4] net: Implement napi_try_disable() Anton Vorontsov
2010-07-07 17:13 ` Anton Vorontsov
2010-07-07 17:13 ` [PATCH RFC 4/4] kgdb: Quiesce IO back-end before rounding up secondary CPUs Anton Vorontsov
2010-07-07 17:13 ` Anton Vorontsov
2010-07-07 17:54 ` [PATCH RFC 0/4] ARM/KGDB: Some fixes for SMP machines Anton Vorontsov
2010-07-07 17:54 ` Anton Vorontsov
2010-07-08 8:48 ` Will Deacon
2010-07-08 8:48 ` Will Deacon [this message]
2010-07-08 8:48 ` Will Deacon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='004701cb1e7a$66a78890$33f699b0$@deacon@arm.com' \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.