public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: George Anzinger <george@mvista.com>
To: "Amit S. Kale" <amitkale@emsyssoft.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	KGDB bugreports <kgdb-bugreport@lists.sourceforge.net>,
	Pavel Machek <pavel@suse.cz>, Matt Mackall <mpm@selenic.com>,
	discuss@x86-64.org
Subject: Re: KGDB 2.0.3 with fixes and development in ethernet interface
Date: Fri, 16 Jan 2004 12:48:51 -0800	[thread overview]
Message-ID: <40084E33.1070003@mvista.com> (raw)
In-Reply-To: <200401161759.59098.amitkale@emsyssoft.com>

Amit S. Kale wrote:
> Hi,
> 
> KGDB 2.0.3 is available at 
> http://kgdb.sourceforge.net/kgdb-2/linux-2.6.1-kgdb-2.0.3.tar.bz2
> 
> Ethernet interface still doesn't work. It responds to gdb for a couple of 
> packets and then panics. gdb log for ethernet interface is pasted below.
> 
> It panics and enter kgdb_handle_exception recursively and silently. To see the 
> panic on screen make kgdb_handle_exception return immediately if 
> kgdb_connected is non-zero. 
> 
> Panic trace is pasted below. It panics in skb_release_data. Looks like skb 
> handling will have to changed to be have kgdb specific buffers.

Well, this is one step to independence.  That would imply a small memory 
allocator in kgdb itself.  A good thing IMHO.

-- 
George Anzinger   george@mvista.com
High-res-timers:  http://sourceforge.net/projects/high-res-timers/
Preemption patch: http://www.kernel.org/pub/linux/kernel/people/rml


  parent reply	other threads:[~2004-01-16 20:49 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-16 12:29 KGDB 2.0.3 with fixes and development in ethernet interface Amit S. Kale
2004-01-16 12:58 ` Pavel Machek
2004-01-16 14:07   ` Christoph Hellwig
2004-01-16 14:24     ` Amit S. Kale
2004-01-16 14:17   ` Amit S. Kale
2004-01-16 14:45     ` Pavel Machek
2004-01-16 13:05 ` [discuss] " Andi Kleen
2004-01-16 14:21   ` Amit S. Kale
2004-01-16 14:45     ` Pavel Machek
2004-01-16 15:12       ` Amit S. Kale
2004-01-16 14:47     ` Pavel Machek
2004-01-16 15:15       ` Amit S. Kale
2004-01-16 15:52         ` Pavel Machek
2004-01-17  6:27           ` KGDB documentation [Re: [discuss] KGDB 2.0.3 with fixes and development in ethernet interface] Amit S. Kale
2004-01-17  9:00             ` George Anzinger
2004-01-16 18:39     ` [discuss] KGDB 2.0.3 with fixes and development in ethernet interface Matt Mackall
2004-01-16 16:13 ` Pavel Machek
2004-01-16 20:48 ` George Anzinger [this message]
2004-01-16 21:51 ` Pavel Machek
2004-01-17  1:23   ` George Anzinger
2004-01-17  9:29     ` Amit S. Kale
2004-01-17 19:54       ` George Anzinger
2004-01-21 13:46         ` Amit S. Kale
2004-01-21 18:39           ` Daniel Jacobowitz
2004-01-21 23:14             ` George Anzinger
2004-01-22  5:49             ` Amit S. Kale
2004-01-22 20:33               ` Daniel Jacobowitz
2004-01-21 23:00           ` George Anzinger
2004-01-22  5:09             ` Amit S. Kale
2004-01-22 17:20               ` Tom Rini
2004-01-22 22:54                 ` George Anzinger
2004-01-22 22:57                   ` Daniel Jacobowitz
2004-01-23 19:10               ` Tom Rini

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=40084E33.1070003@mvista.com \
    --to=george@mvista.com \
    --cc=amitkale@emsyssoft.com \
    --cc=discuss@x86-64.org \
    --cc=kgdb-bugreport@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.com \
    --cc=pavel@suse.cz \
    /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