mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ramagudi Naziir" <naziirr@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: mpm@selenic.com, kgdb-bugreport@lists.sourceforge.net,
	jason.wessel@windriver.com
Subject: a problem with NETPOLL/KGDBoE
Date: Thu, 6 Dec 2007 20:22:15 +0200	[thread overview]
Message-ID: <dfb262380712061022h43eab6eaxe231b1f81f54d433@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1812 bytes --]

Hi all,

It's probably only me, but I can't connect to a kgdb host because
of bouncing ICMP unreachables. I'll be glad if you could take a look
to see if it's a bug or not.

Details:
- running a cloned  version of kgdb_2.6.23 branch of Jason's
git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/linux-2.6-kgdb.git

- "modprobe kgdboe kgdboe='@10.0.0.28/,@10.0.0.11/'" works fine,
and var/log/messages get filled with six kgdboe network configuration
messages (local port 6443, local ip 10.0.0.28, interface eth0,
remote port 6442, remote ip 10.0.0.11, remote mac ff:ff:ff:ff:ff:ff).

- "netstat -aun" does not show an open 6643 UDP port (should it ?)

- When trying to connect via remote gdb, I get a connection refused:

(gdb) target remote udp:10.0.0.28:6433
warning: The remote protocol may be unreliable over UDP.
Some events may be lost, rendering further debugging impossible.
Remote debugging using udp:10.0.0.28:6433
Remote communication error: Connection refused.

- tcpdump ouput shows two UDP messages traveling to the kgdb host
only to immediately invoke ICMP unreachables:

19:30:53.424248 IP 10.0.0.11.32785 > 10.0.0.28.6433: UDP, length 5
19:30:53.424323 IP 10.0.0.11.32785 > 10.0.0.28.6433: UDP, length 14
19:30:53.426292 IP 10.0.0.28 > 10.0.0.11: ICMP 10.0.0.28 udp port 6433
unreachable, length 41
19:30:53.427542 IP 10.0.0.28 > 10.0.0.11: ICMP 10.0.0.28 udp port 6433
unreachable, length 50

- Network between 10.0.0.28 and 10.0.0.11 is just fine; I successfully work
on NFS mounts (with 10.0.0.28 as a client)

- the kgdb host has selinux=0 and  iptables with accept-all policies

- i386 (running inside a bridged qemu/vmplayer host)

- config attached

If you have any idea how to further debug this problem,
or maybe if you know if I did something wrong,
please share !

Thanks,
naziir.

[-- Attachment #2: .config.gz --]
[-- Type: application/x-gzip, Size: 21063 bytes --]

             reply	other threads:[~2007-12-06 18:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-06 18:22 Ramagudi Naziir [this message]
2007-12-06 18:34 ` Matt Mackall
2007-12-06 19:13   ` Ramagudi Naziir
2007-12-19 16:22   ` Ramagudi Naziir
2007-12-19 16:35     ` Jason Wessel
2007-12-19 16:43       ` Ramagudi Naziir
2007-12-19 17:28     ` Matt Mackall

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=dfb262380712061022h43eab6eaxe231b1f81f54d433@mail.gmail.com \
    --to=naziirr@gmail.com \
    --cc=jason.wessel@windriver.com \
    --cc=kgdb-bugreport@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.com \
    /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

all inboxes | Powered by JetHome®