From: srikanth krishnakar <skrishnakar@gmail.com>
To: kgdb-bugreport@lists.sourceforge.net
Cc: Jason Wessel <jason.wessel@windriver.com>
Subject: "Info threads" hangs in Linux-2.6.29 with KGDBOE
Date: Tue, 9 Jun 2009 23:38:40 +0530 [thread overview]
Message-ID: <6213bc560906091108j2526efeep1dc9397123df5e0@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2064 bytes --]
Hi All,
*ISSUE *: "*Info threads*" hangs in KGDBOE
Kernel : Linux-2.6.29
Bug found in Architectures: PowerPC (ppc32), x86
-------
While trying to run kernel* Linux-2.6.29* on* PowerPC* Xilinx target
with *KGDBOE
*enabled. Further issues arise when I run "*info threads*" after
connecting to the target. following is the error:
(gdb) target remote udp:10.161.2.35:6443
warning: The remote protocol may be unreliable over UDP.
Some events may be lost, rendering further debugging impossible.
Remote debugging using udp:10.161.2.35:6443
kgdb_breakpoint () at kernel/kgdb.c:1803
1803 arch_kgdb_breakpoint();
(gdb) info threads
[New Thread -2]
[New Thread 2]
[New Thread 3]
[New Thread 4]
[New Thread 5]
[New Thread 6]
[New Thread 59]
[New Thread 67]
[New Thread 101]
[New Thread 102]
[New Thread 103]
[New Thread 104]
[New Thread 105]
14 Thread 105 (nfsiod) __switch_to (prev=<value optimized out>,
new=0xcf89c100) at arch/powerpc/kernel/process.c:411
13 Thread 104 (aio/0) __switch_to (prev=<value optimized out>,
new=0xcf82f4e0) at arch/powerpc/kernel/process.c:411
12 Thread 103 (kswapd0) __switch_to (prev=<value optimized out>,
new=0xcf82f4e0) at arch/powerpc/kernel/process.c:411
11 Thread 102 (pdflush) __switch_to (prev=<value optimized out>,
new=0xcf82e880) at arch/powerpc/kernel/process.c:411
10 Thread 101 (pdflush) Ignoring packet error, continuing...
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Finally kernel dies, after these error messages. This issue is not found
till Linux-2.6.28.10 kernel version, KGDBOE works fine in x86 & PowerPC. Now
the bug is seen in x86 (32bit) and PowerPC from kernel version Linux-2.6.29
Hope this should not be raw_smp_processor_id issue ! The CPU ID returned in
both arch's is 0. Which patch in netpoll* or any net device has caused this
issue.
One more thing to notice in x86 or PowerPC the kernel dies exactly after
reply of four threads/packets.
Thanks,
Srikanth Krishnakar
[-- Attachment #2: Type: text/html, Size: 2831 bytes --]
reply other threads:[~2009-06-09 18:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6213bc560906091108j2526efeep1dc9397123df5e0@mail.gmail.com \
--to=skrishnakar@gmail.com \
--cc=jason.wessel@windriver.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).