mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Andrew Morton <akpm@osdl.org>, Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6 kgdb without serial port
Date: Fri, 26 Dec 2003 13:18:15 -0800	[thread overview]
Message-ID: <2380000.1072473494@[10.10.2.4]> (raw)
In-Reply-To: <20031226110851.29ce9fa5.akpm@osdl.org>

>> > > 2.6 kgdb patches in -mm tree seem to contain kgdb-over-ethernet stuff,
>> > > but still require me to fill in serial port interrupt/address. Is
>> > > there easy way to make it work without serial port? [This notebook has
>> > > none :-(].
>> > 
>> > That's a bit ugly, but things should still work OK?  Give it some random
>> > UART address but specify an ethernet connection at boot time - the kgdb
>> > stub should never touch the UART.
>> 
>> I found out what was biting me: using 2.95 with kgdb is bad idea. 2.95
>> with kgdb means reboot just after uncompressing kernel -- pretty nasty
>> to debug. Please apply,
> 
> I've been using 2.95.3 on and off for ages, no problems?

2.95.4 seems to work as well, or did last time I tried it. 
Pavel, what version exactly were you using?

early_printk might help debugging, if you're interested.
ftp://ftp.kernel.org/pub/linux/kernel/people/mbligh/patches/2.6.0/2.6.0-mjb1/200-early_printk

M.

  reply	other threads:[~2003-12-26 21:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-15 20:06 Pavel Machek
2003-12-16  6:34 ` Andrew Morton
2003-12-16 10:30   ` crypto-loop + highmen -> random crashes in -test11 Soeren Sonnenburg
2003-12-16 11:40     ` Andrew Morton
2003-12-18  8:30       ` Soeren Sonnenburg
2003-12-16 22:45     ` bill davidsen
2003-12-26 18:27   ` 2.6 kgdb without serial port Pavel Machek
2003-12-26 19:08     ` Andrew Morton
2003-12-26 21:18       ` Martin J. Bligh [this message]
2003-12-27 10:30       ` Pavel Machek

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='2380000.1072473494@[10.10.2.4]' \
    --to=mbligh@aracnet.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.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

all inboxes | Powered by JetHome®