From getelson@softhome.net Sun Feb  2 07:35:57 2003
Received: with ECARTIS (v1.0.0; list kdb); Sun, 02 Feb 2003 07:36:00 -0800 (PST)
Received: from jive.SoftHome.net (jive.SoftHome.net [66.54.152.27])
	by oss.sgi.com (8.12.5/8.12.5) with SMTP id h12FZu3v009342
	for <kdb@oss.sgi.com>; Sun, 2 Feb 2003 07:35:56 -0800
Received: (qmail 11269 invoked by uid 417); 2 Feb 2003 15:43:25 -0000
Received: from slide-.softhome.net (HELO softhome.net) (172.16.2.21)
  by shunt-smtp-out-0 with SMTP; 2 Feb 2003 15:43:25 -0000
Received: from localhost (localhost [127.0.0.1])
  (uid 417)
  by softhome.net with local; Sun, 02 Feb 2003 08:43:25 -0700
From: getelson@softhome.net
To: kdb@oss.sgi.com
Reply-To: Gregory <getelson@softhome.net>
Date: Sun, 02 Feb 2003 08:43:25 -0700
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Sender: getelson@softhome.net
X-Originating-IP: [194.29.35.12]
Message-ID: <courier.3E3D3C9D.00007BAF@softhome.net>
X-archive-position: 228
Subject: (no subject)
X-ecartis-version: Ecartis v1.0.0
Sender: kdb-bounce@oss.sgi.com
Errors-to: kdb-bounce@oss.sgi.com
X-original-sender: getelson@softhome.net
Precedence: bulk
X-list: kdb

Hello, 

I try to "port" a kdb patch to the redhat kernel 2.4.18-5.
Meanwile it looks pretty stable exept this problem:
`ss' command terminates the kdb shell without producing any output.
Next attempt to re-enter kdb shell will hang a system. 

I'm looking for any advise about a couse of such behaviour. 

I work with PII SMP architecture.
Kdb patch files I use are:
 kdb-v2.3-2.4.18-common-2
 kdb-v2.3-2.4.18-i386-3 

Here is the log  of the `ss' command with all kdb debugging flags enabled: 

Entering kdb (current=0xc1e7a000, pid 0) on processor 1 due to Keyboard 
Entry 

[1]kdb> mm kdb_flags 0x5f0000 

0xc039d07c = 0x5f0000 

[1]kdb> ss 

state: kdb_main_loop 3 cpu 1 value -1003 initial 1 state 1000429 

state: kdb 10 cpu 1 value 1 initial 1 state 1000429 

state: kdb 11 cpu 1 value 1 initial 1 state 1000029 

state: kdb 13 cpu 1 value 1 initial 1 state 1000029 

state: kdb 14 cpu 1 value 1 initial 1 state 1000028 

state: kdb 17 cpu 1 value 8 initial 1 state 1000028 

Warning: get_irqlock on cpu 1 while kdb is running, may hang 

Warning: get_irqlock on cpu 1 while kdb is running, may hang 

Warning: get_irqlock on cpu 1 while kdb is running, may hang 

Warning: get_irqlock on cpu 1 while kdb is running, may hang 

Warning: get_irqlock on cpu 1 while kdb is running, may hang 

Warning: get_irqlock on cpu 1 while kdb is running, may hang 

Warning: get_irqlock on cpu 1 while kdb is running, may hang
Warning: get_irqlock on cpu 1 while kdb is running, may hang 

Warning: get_irqlock on cpu 1 while kdb is running, may hang 

Warning: get_irqlock on cpu 1 while kdb is running, may hang 

sh-2.05a#
/**
******************** <re-entry point > ****************************
**/
state: kdb 1 cpu 1 value 8 initial 1 state 1000028
state: kdb 3 cpu 1 value 8 initial 1 state 1000028
kdb: Debugger re-entered on cpu 1, new reason = 8
    Not executing a kdb command
    No longjmp available for recovery
    Cannot recover, allowing event to proceed 

From kaos@sgi.com Sun Feb  2 14:18:30 2003
Received: with ECARTIS (v1.0.0; list kdb); Sun, 02 Feb 2003 14:18:33 -0800 (PST)
Received: from mail.ocs.com.au (mail.ocs.com.au [203.34.97.2])
	by oss.sgi.com (8.12.5/8.12.5) with SMTP id h12MIR3v013562
	for <kdb@oss.sgi.com>; Sun, 2 Feb 2003 14:18:28 -0800
Received: (qmail 31049 invoked from network); 2 Feb 2003 22:25:53 -0000
Received: from ocs3.intra.ocs.com.au (192.168.255.3)
  by mail.ocs.com.au with SMTP; 2 Feb 2003 22:25:53 -0000
Received: by ocs3.intra.ocs.com.au (Postfix, from userid 16331)
	id 56140300087; Mon,  3 Feb 2003 09:25:50 +1100 (EST)
Received: from ocs3.intra.ocs.com.au (localhost [127.0.0.1])
	by ocs3.intra.ocs.com.au (Postfix) with ESMTP id 304638F
	for <kdb@oss.sgi.com>; Mon,  3 Feb 2003 09:25:49 +1100 (EST)
X-Mailer: exmh version 2.4 06/23/2000 with nmh-1.0.4
From: Keith Owens <kaos@sgi.com>
To: kdb@oss.sgi.com
Subject: Re: ss problems in kdb v2.3-2.4.18
In-reply-to: Your message of "Sun, 02 Feb 2003 08:43:25 PDT."
             <courier.3E3D3C9D.00007BAF@softhome.net> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 03 Feb 2003 09:25:44 +1100
Message-ID: <26895.1044224744@ocs3.intra.ocs.com.au>
X-archive-position: 229
X-ecartis-version: Ecartis v1.0.0
Sender: kdb-bounce@oss.sgi.com
Errors-to: kdb-bounce@oss.sgi.com
X-original-sender: kaos@sgi.com
Precedence: bulk
X-list: kdb

On Sun, 02 Feb 2003 08:43:25 -0700, 
getelson@softhome.net wrote:
>I try to "port" a kdb patch to the redhat kernel 2.4.18-5.
>Meanwile it looks pretty stable exept this problem:
>`ss' command terminates the kdb shell without producing any output.
>Next attempt to re-enter kdb shell will hang a system. 
>Kdb patch files I use are:
> kdb-v2.3-2.4.18-common-2
> kdb-v2.3-2.4.18-i386-3 

There were bugs in the single step code in the v2.3 patches, fixed in
kdb v2.5-2.4.19-common-1 (2002-11-14).


From kaos@sgi.com Sun Feb  2 16:59:51 2003
Received: with ECARTIS (v1.0.0; list kdb); Sun, 02 Feb 2003 16:59:56 -0800 (PST)
Received: from rj.sgi.com (rj.sgi.com [192.82.208.96])
	by oss.sgi.com (8.12.5/8.12.5) with SMTP id h130xp3v015537
	for <kdb@oss.sgi.com>; Sun, 2 Feb 2003 16:59:51 -0800
Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130])
	by rj.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with SMTP id h12N7PG8023242
	for <kdb@oss.sgi.com>; Sun, 2 Feb 2003 15:07:26 -0800
Received: from kao2.melbourne.sgi.com (kao2.melbourne.sgi.com [134.14.55.180]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id MAA04451; Mon, 3 Feb 2003 12:05:57 +1100
Received: by kao2.melbourne.sgi.com (Postfix, from userid 16331)
	id 67433300087; Mon,  3 Feb 2003 12:05:55 +1100 (EST)
Received: from kao2.melbourne.sgi.com (localhost [127.0.0.1])
	by kao2.melbourne.sgi.com (Postfix) with ESMTP
	id DE4418F; Mon,  3 Feb 2003 12:05:55 +1100 (EST)
X-Mailer: exmh version 2.4 06/23/2000 with nmh-1.0.4
From: Keith Owens <kaos@sgi.com>
To: jim.houston@attbi.com
Cc: kdb@oss.sgi.com
Subject: Re: kdb ack_APIC_irq() why? 
In-reply-to: Your message of "Sat, 18 Jan 2003 19:32:06 CDT."
             <3E29F206.C8D088CB@attbi.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 03 Feb 2003 12:05:50 +1100
Message-ID: <29024.1044234350@kao2.melbourne.sgi.com>
X-archive-position: 230
X-ecartis-version: Ecartis v1.0.0
Sender: kdb-bounce@oss.sgi.com
Errors-to: kdb-bounce@oss.sgi.com
X-original-sender: kaos@sgi.com
Precedence: bulk
X-list: kdb

On Sat, 18 Jan 2003 19:32:06 -0500, 
Jim Houston <jim.houston@attbi.com> wrote:
>I have been spending too much time reading IA32 System Programming Guide:
>
>   http://www.intel.com/design/pentium4/manuals/245472.htm
>
>in particular section 8.8.5.  I believe that kdb may be doing
>interrupt acknowledge writes to the EOI register which are not
>needed.  It is using NMI delivery, and section 8.8.5 says that
>the EOI write should not be done for NMI interrupts.

That explicit restriction was not in 24319202.pdf, although it was
implied.

>I have never seen any problems, but it seems that kdb
>could be acknowledging random interrupts which don't belong to 
>it.
>
>I tried taking the ack_APIC_irq() out of do_ack_apic_irq(), and 
>kdb works correctly.

Thanks for the info.  I am redesigning the kdb ipi code to try normal
interrupts first, then nmi if there is no response, so ack_APIC_irq()
will still be need in some cases.  kdb v3.0 will still call
ack_APIC_irq, even for nmi, the next major version will handle nmi
differently.


From kaos@sgi.com Sun Feb  2 21:22:02 2003
Received: with ECARTIS (v1.0.0; list kdb); Sun, 02 Feb 2003 21:22:07 -0800 (PST)
Received: from rj.sgi.com (rj.sgi.com [192.82.208.96])
	by oss.sgi.com (8.12.5/8.12.5) with SMTP id h135M03v016807
	for <kdb@oss.sgi.com>; Sun, 2 Feb 2003 21:22:00 -0800
Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130])
	by rj.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with SMTP id h133TZG8002531
	for <kdb@oss.sgi.com>; Sun, 2 Feb 2003 19:29:36 -0800
Received: from kao2.melbourne.sgi.com (kao2.melbourne.sgi.com [134.14.55.180]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id QAA06473; Mon, 3 Feb 2003 16:28:09 +1100
Received: by kao2.melbourne.sgi.com (Postfix, from userid 16331)
	id A50F7300087; Mon,  3 Feb 2003 16:28:08 +1100 (EST)
Received: from kao2.melbourne.sgi.com (localhost [127.0.0.1])
	by kao2.melbourne.sgi.com (Postfix) with ESMTP
	id 260768F; Mon,  3 Feb 2003 16:28:08 +1100 (EST)
X-Mailer: exmh version 2.4 06/23/2000 with nmh-1.0.4
From: Keith Owens <kaos@sgi.com>
To: kdb@oss.sgi.com
Cc: linux-kernel@vger.kernel.org
Subject: Announce: kdb v3.0 is available for kernel 2.4.20
Date: Mon, 03 Feb 2003 16:28:02 +1100
Message-ID: <32006.1044250082@kao2.melbourne.sgi.com>
X-archive-position: 231
X-ecartis-version: Ecartis v1.0.0
Sender: kdb-bounce@oss.sgi.com
Errors-to: kdb-bounce@oss.sgi.com
X-original-sender: kaos@sgi.com
Precedence: bulk
X-list: kdb

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Content-Type: text/plain; charset=us-ascii

ftp://oss.sgi.com/projects/kdb/download/v3.0/

  kdb-v3.0-2.4.20-common-1.bz2
  kdb-v3.0-2.4.20-i386-1.bz2
  kdb-v3.0-2.4.20-ia64-021210-1.bz2

Changelog extracts since v2.5-2.4.20.  A special thanks goes to Sonic
Zhang for adding command history and editing to kdb, and pestering me
until I found time to accept it.

2.4.20-common-1

2003-02-03 Keith Owens  <kaos@sgi.com>

	* Register kdb commands early.
	* Decode oops via kallsyms if it is available.
	* Update copyright notices to 2003.
	* Add defcmd/endefcmd to allow users to package their own macros.
	* kdb commands that fail are ignored when prefixed with '-'.
	* Add selection options to bta command.
	* Add btc command (switch to each cpu and backtrace).
	* Do real time detection of dead cpus.
	* Clear ip adjusted flag when leaving kdb.
	* Clean up ps command.
	* Print ps output for each task when backtracing.
	* Bump to version v3.0 to reduce confusion between kdb and kernel
	  version numbers.
	* Add kdba_local_arch_setup/kdba_local_arch_cleanup to correct
	  keyboard freeze.  Ashish Kalra.
	* Refuse multiple breakpoints at the same address.
	* Add fl (file_lock) command, from XFS development tree.
	* Correct inode_pages, from XFS development tree.
	* Add command history and editing.  Sonic Zhang.
	* Extend command history and editing to handle vt100 escape sequences.
	* Allow tab completion at start of line.
	* Touch nmi watchdog on long running bta and btc commands.
	* Clean up ps output and standardize with bta codes.
	* Correctly handle escaped characters in commands.
	* Update man pages for btc and command history/editing.
	* kdb v3.0-2.4.20-common-1.

2.4.20-i386-1

2003-02-03 Keith Owens  <kaos@sgi.com>

	* Register kdb commands early.
	* Handle KDB_ENTER() when kdb=off.
	* Optimize __kdba_getarea_size when width is a constant.
	* Decode oops via kallsyms if it is available.
	* Update copyright notices to 2003.
	* Handle call *disp32(%reg) in backtrace.
	* Correct keyboard freeze.  Ashish Kalra.
	* Add command history and editing.  Sonic Zhang.
	* kdb_toggleled is conditional on KDB_BLINK_LED.  Bernhard Fischer.
	* Allow tab on serial line for symbol completion.
	* Ignore KDB_ENTER() when kdb is already running.
	* kdb v3.0-2.4.20-i386-1.

2.4.20-ia64-021210-1

2003-02-03 Keith Owens  <kaos@sgi.com>

	* Register kdb commands early.
	* Handle KDB_ENTER() when kdb=off.
	* Optimize __kdba_getarea_size when width is a constant.
	* Decode oops via kallsyms if it is available.
	* Update copyright notices to 2003.
	* Add commands to dump struct pt_regs and switch_stack.
	* Handle padding from unw_init_running for switch_stack.
	* Add dummy kdba_local_arch_setup/kdba_local_arch_cleanup.
	* Warning for pod mode.
	* Add command history and editing.  Sonic Zhang.
	* kdb_toggleled is conditional on KDB_BLINK_LED.  Bernhard Fischer.
	* Allow tab on serial line for symbol completion.
	* Ignore KDB_ENTER() when kdb is already running.
	* kdb v3.0-2.4.20-ia64-021210-1.


v3.0/README

Starting with kdb v2.0 there is a common patch against each kernel which
contains all the architecture independent code plus separate architecture
dependent patches.  Apply the common patch for your kernel plus at least
one architecture dependent patch, the architecture patches activate kdb.

The naming convention for kdb patches is :-

 vx.y    The version of kdb.  x.y is updated as new features are added to kdb.
 -v.p.s  The kernel version that the patch applies to.  's' may include -pre,
	 -rc or whatever numbering system the kernel keepers have thought up this
	 week.
 -common The common kdb code.  Everybody needs this.
 -i386   Architecture dependent code for i386.
 -ia64   Architecture dependent code for ia64, etc.
 -n      If there are multiple kdb patches against the same kernel version then
	 the last number is incremented.

To build kdb for your kernel, apply the common kdb patch which is less
than or equal to the kernel v.p.s, taking the highest value of '-n'
if there is more than one.  Apply the relevant arch dependent patch
with the same value of 'vx.y-v.p.s-', taking the highest value of '-n'
if there is more than one.

For example, to use kdb for i386 on kernel 2.4.20, apply
  kdb-v3.0-2.4.20-common-<n>            (use highest value of <n>)
  kdb-v3.0-2.4.20-i386-<n>              (use highest value of <n>)
in that order.  To use kdb for ia64-021210 on kernel 2.4.20, apply
  kdb-v3.0-2.4.20-common-<n>            (use highest value of <n>)
  kdb-v3.0-2.4.20-ia64-021210-<n>       (use highest value of <n>)
in that order.

Use patch -p1 for all patches.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Exmh version 2.1.1 10/15/1999

iD8DBQE+Pf3fi4UHNye0ZOoRAsr0AJoCXacxDmlrp779EpIZ8kYLnDz9bQCgxqa7
fLFWChCxxjJomc4sl00s+uo=
=ZdNo
-----END PGP SIGNATURE-----


From foris@mr.mr.med.ge.com Thu Feb  6 14:19:14 2003
Received: with ECARTIS (v1.0.0; list kdb); Thu, 06 Feb 2003 14:19:20 -0800 (PST)
Received: from ext-ch1gw-3.online-age.net (ext-ch1gw-3.online-age.net [216.34.191.37])
	by oss.sgi.com (8.12.5/8.12.5) with SMTP id h16MJD3v013681
	for <kdb@oss.sgi.com>; Thu, 6 Feb 2003 14:19:14 -0800
Received: from int-ch1gw-2.online-age.net (int-ch1gw-2 [3.159.232.66])
	by ext-ch1gw-3.online-age.net (8.12.3/8.9.1/990426-RLH) with ESMTP id h16MQsj0016141
	for <kdb@oss.sgi.com>; Thu, 6 Feb 2003 17:26:54 -0500 (EST)
Received: from uswaumsxb4medge.med.ge.com (localhost [127.0.0.1])
	by int-ch1gw-2.online-age.net (8.12.3/8.12.3/990426-RLH) with ESMTP id h16MQmiZ011252
	for <kdb@oss.sgi.com>; Thu, 6 Feb 2003 17:26:48 -0500 (EST)
Received: by USWAUMSXB4MEDGE with Internet Mail Service (5.5.2656.59)
	id <1FHG0W18>; Thu, 6 Feb 2003 16:26:40 -0600
Received: from ct.ct.med.ge.com ([3.70.56.18]) by uswaumsxbhmedge.med.ge.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2656.59)
	id 1FHJC18T; Thu, 6 Feb 2003 16:26:25 -0600
Received: from med.ge.com ([3.57.108.2])
	by ct.ct.med.ge.com (8.8.8+Sun/8.8.8) with ESMTP id QAA26331
	for <kdb@oss.sgi.com>; Thu, 6 Feb 2003 16:26:22 -0600 (CST)
From: "Foris, Jim (MED)" <foris@mr.mr.med.ge.com>
To: kdb@oss.sgi.com
Message-ID: <3E42E2C7.90904@med.ge.com>
Date: Thu, 06 Feb 2003 16:33:43 -0600
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021218
X-Accept-Language: en-us, en
MIME-Version: 1.0
Subject: using kdb on Red Hat/SGI linux-2.4.18-18SGI_XFS_1.2pre5
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-archive-position: 232
X-ecartis-version: Ecartis v1.0.0
Sender: kdb-bounce@oss.sgi.com
Errors-to: kdb-bounce@oss.sgi.com
X-original-sender: foris@mr.mr.med.ge.com
Precedence: bulk
X-list: kdb

KDB is a wonderful tool,  but I am having problems using the version shipped with
the linux-2.4.18-18SGI_XFS_1.2pre5 kernel (out of the XFS project at oss.sgi.com).

First, I am not getting any symbols out of the stack backtraces.

Second, I am not able to break into a system hang - making the debugger
useless for what I really need it for.

In previous versions (namely, linux-2.4.18-4SGI_XFS_1.1) I was able to fix the
break-in problem by applying an apic patch that distributed interrupts so that
everything was not going through CPU0.  This patch does not work with the
2.4.18-18 Red Hat kernel, though...... so.....

Is there any new patch recommended to help debug CPU0 hangs on the
Red Hat 2.4.18 (current) distributions ?

Is there anything I need to do special to get symbols in the KDB tracebacks
(like configure in stack frame pointers, maybe?) ?

Is there anything that anyone could recommend that I read which would
help me figure this stuff out ?

Thanks,

Jim Foris

From kaos@sgi.com Thu Feb  6 14:43:09 2003
Received: with ECARTIS (v1.0.0; list kdb); Thu, 06 Feb 2003 14:43:11 -0800 (PST)
Received: from mail.ocs.com.au (mail.ocs.com.au [203.34.97.2])
	by oss.sgi.com (8.12.5/8.12.5) with SMTP id h16Mh63v014195
	for <kdb@oss.sgi.com>; Thu, 6 Feb 2003 14:43:08 -0800
Received: (qmail 7401 invoked from network); 6 Feb 2003 22:50:52 -0000
Received: from ocs3.intra.ocs.com.au (192.168.255.3)
  by mail.ocs.com.au with SMTP; 6 Feb 2003 22:50:52 -0000
Received: by ocs3.intra.ocs.com.au (Postfix, from userid 16331)
	id 0BC1A300087; Fri,  7 Feb 2003 09:50:49 +1100 (EST)
Received: from ocs3.intra.ocs.com.au (localhost [127.0.0.1])
	by ocs3.intra.ocs.com.au (Postfix) with ESMTP
	id 036708F; Fri,  7 Feb 2003 09:50:48 +1100 (EST)
X-Mailer: exmh version 2.4 06/23/2000 with nmh-1.0.4
From: Keith Owens <kaos@sgi.com>
To: "Foris, Jim (MED)" <foris@mr.mr.med.ge.com>
Cc: kdb@oss.sgi.com
Subject: Re: using kdb on Red Hat/SGI linux-2.4.18-18SGI_XFS_1.2pre5 
In-reply-to: Your message of "Thu, 06 Feb 2003 16:33:43 MDT."
             <3E42E2C7.90904@med.ge.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 07 Feb 2003 09:50:43 +1100
Message-ID: <21932.1044571843@ocs3.intra.ocs.com.au>
X-archive-position: 233
X-ecartis-version: Ecartis v1.0.0
Sender: kdb-bounce@oss.sgi.com
Errors-to: kdb-bounce@oss.sgi.com
X-original-sender: kaos@sgi.com
Precedence: bulk
X-list: kdb

On Thu, 06 Feb 2003 16:33:43 -0600, 
"Foris, Jim (MED)" <foris@mr.mr.med.ge.com> wrote:
>Second, I am not able to break into a system hang - making the debugger
>useless for what I really need it for.

Use the nmi watchdog, boot with nmi_watchdog=1.

>Is there anything I need to do special to get symbols in the KDB tracebacks
>(like configure in stack frame pointers, maybe?) ?

kallsyms is automatically included.  What does your backtrace look like?


From foris@mr.mr.med.ge.com Thu Feb  6 15:07:56 2003
Received: with ECARTIS (v1.0.0; list kdb); Thu, 06 Feb 2003 15:07:59 -0800 (PST)
Received: from ext-nj2gw-2.online-age.net (ext-nj2gw-2.online-age.net [216.35.73.164])
	by oss.sgi.com (8.12.5/8.12.5) with SMTP id h16N7t3v014828
	for <kdb@oss.sgi.com>; Thu, 6 Feb 2003 15:07:56 -0800
Received: from int-nj2gw-1.online-age.net (int-nj2gw-1 [3.159.236.65])
	by ext-nj2gw-2.online-age.net (8.12.3/8.9.1/990426-RLH) with ESMTP id h16NFZOi012744;
	Thu, 6 Feb 2003 18:15:36 -0500 (EST)
Received: from uswaumsxb4medge.med.ge.com (localhost [127.0.0.1])
	by int-nj2gw-1.online-age.net (8.12.3/8.12.3/990426-RLH) with ESMTP id h16NFRnC025917;
	Thu, 6 Feb 2003 18:15:30 -0500 (EST)
Received: by USWAUMSXB4MEDGE with Internet Mail Service (5.5.2656.59)
	id <1FHG0YKM>; Thu, 6 Feb 2003 17:15:20 -0600
Received: from ct.ct.med.ge.com ([3.70.56.18]) by uswaumsxbhmedge.med.ge.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2656.59)
	id 1FHJC3M3; Thu, 6 Feb 2003 17:15:08 -0600
Received: from med.ge.com ([3.57.108.2])
	by ct.ct.med.ge.com (8.8.8+Sun/8.8.8) with ESMTP id RAA29587;
	Thu, 6 Feb 2003 17:15:04 -0600 (CST)
From: "Foris, Jim (MED)" <foris@mr.mr.med.ge.com>
To: Keith Owens <kaos@sgi.com>
Cc: "Foris, Jim (MED)" <foris@mr.med.ge.com>, kdb@oss.sgi.com
Message-ID: <3E42EE31.1090001@med.ge.com>
Date: Thu, 06 Feb 2003 17:22:25 -0600
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021218
X-Accept-Language: en-us, en
MIME-Version: 1.0
Subject: Re: using kdb on Red Hat/SGI linux-2.4.18-18SGI_XFS_1.2pre5
References: <21932.1044571843@ocs3.intra.ocs.com.au>
In-Reply-To: <21932.1044571843@ocs3.intra.ocs.com.au>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-archive-position: 234
X-ecartis-version: Ecartis v1.0.0
Sender: kdb-bounce@oss.sgi.com
Errors-to: kdb-bounce@oss.sgi.com
X-original-sender: foris@mr.mr.med.ge.com
Precedence: bulk
X-list: kdb

Keith Owens wrote:
> On Thu, 06 Feb 2003 16:33:43 -0600, 
> "Foris, Jim (MED)" <foris@mr.mr.med.ge.com> wrote:
> 
>>Second, I am not able to break into a system hang - making the debugger
>>useless for what I really need it for.
> 
> 
> Use the nmi watchdog, boot with nmi_watchdog=1.
> 

Did that... made no difference.

We think it is because CPU0 handles all NMIs.... so if it dies,
so does the NMI watchdog.

> 
>>Is there anything I need to do special to get symbols in the KDB tracebacks
>>(like configure in stack frame pointers, maybe?) ?
> 
> 
> kallsyms is automatically included.  What does your backtrace look like?
>

Here is a section from a crash:


[1]kdb> bt
ESP        EIP        Function (args)
0xc46cde28 0xc01ed880 <unknown>+0xc01ed880
                                kernel <unknown> 0x0 0x0 0x0
0xc46cde2c 0xc46cdde0 <unknown>+0xc46cdde0
                                kernel <unknown> 0x0 0x0 0x0



From kaos@sgi.com Thu Feb  6 15:54:05 2003
Received: with ECARTIS (v1.0.0; list kdb); Thu, 06 Feb 2003 15:54:08 -0800 (PST)
Received: from rj.sgi.com (rj.sgi.com [192.82.208.96])
	by oss.sgi.com (8.12.5/8.12.5) with SMTP id h16Ns43v015487
	for <kdb@oss.sgi.com>; Thu, 6 Feb 2003 15:54:05 -0800
Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130])
	by rj.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with SMTP id h16M1tG8023378
	for <kdb@oss.sgi.com>; Thu, 6 Feb 2003 14:01:57 -0800
Received: from kao2.melbourne.sgi.com (kao2.melbourne.sgi.com [134.14.55.180]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id LAA22778; Fri, 7 Feb 2003 11:00:26 +1100
Received: by kao2.melbourne.sgi.com (Postfix, from userid 16331)
	id D1D4D300087; Fri,  7 Feb 2003 11:00:25 +1100 (EST)
Received: from kao2.melbourne.sgi.com (localhost [127.0.0.1])
	by kao2.melbourne.sgi.com (Postfix) with ESMTP
	id AD2898F; Fri,  7 Feb 2003 11:00:25 +1100 (EST)
X-Mailer: exmh version 2.4 06/23/2000 with nmh-1.0.4
From: Keith Owens <kaos@sgi.com>
To: "Foris, Jim (MED)" <foris@mr.mr.med.ge.com>
Cc: kdb@oss.sgi.com
Subject: Re: using kdb on Red Hat/SGI linux-2.4.18-18SGI_XFS_1.2pre5 
In-reply-to: Your message of "Thu, 06 Feb 2003 17:22:25 MDT."
             <3E42EE31.1090001@med.ge.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 07 Feb 2003 11:00:20 +1100
Message-ID: <23389.1044576020@kao2.melbourne.sgi.com>
X-archive-position: 235
X-ecartis-version: Ecartis v1.0.0
Sender: kdb-bounce@oss.sgi.com
Errors-to: kdb-bounce@oss.sgi.com
X-original-sender: kaos@sgi.com
Precedence: bulk
X-list: kdb

On Thu, 06 Feb 2003 17:22:25 -0600, 
"Foris, Jim (MED)" <foris@mr.mr.med.ge.com> wrote:
>Keith Owens wrote:
>> Use the nmi watchdog, boot with nmi_watchdog=1.
>
>Did that... made no difference.
>
>We think it is because CPU0 handles all NMIs.... so if it dies,
>so does the NMI watchdog.

NMI should be broadcast.  Before the system hangs, cat /proc/interrupts.
The NMI count on each cpu must be non-zero and increasing continuously
if the nmi watchdog is working.

>[1]kdb> bt
>ESP        EIP        Function (args)
>0xc46cde28 0xc01ed880 <unknown>+0xc01ed880
>                                kernel <unknown> 0x0 0x0 0x0
>0xc46cde2c 0xc46cdde0 <unknown>+0xc46cdde0
>                                kernel <unknown> 0x0 0x0 0x0

That is wierd.  grep kallsyms System.map and insmod -nm some_module_name.


From foris@mr.mr.med.ge.com Fri Feb  7 07:23:32 2003
Received: with ECARTIS (v1.0.0; list kdb); Fri, 07 Feb 2003 07:23:35 -0800 (PST)
Received: from ext-ch1gw-1.online-age.net (ext-ch1gw-1.online-age.net [216.34.191.35])
	by oss.sgi.com (8.12.5/8.12.5) with SMTP id h17FNV3v013674
	for <kdb@oss.sgi.com>; Fri, 7 Feb 2003 07:23:32 -0800
Received: from int-ch1gw-1.online-age.net (int-ch1gw-1 [3.159.232.65])
	by ext-ch1gw-1.online-age.net (8.12.3/8.9.1/990426-RLH) with ESMTP id h17FVEh5022355;
	Fri, 7 Feb 2003 10:31:15 -0500 (EST)
Received: from uswaumsxb4medge.med.ge.com (localhost [127.0.0.1])
	by int-ch1gw-1.online-age.net (8.12.3/8.12.3/990426-RLH) with ESMTP id h17FV0xQ025719;
	Fri, 7 Feb 2003 10:31:09 -0500 (EST)
Received: by USWAUMSXB4MEDGE with Internet Mail Service (5.5.2656.59)
	id <1FHHA696>; Fri, 7 Feb 2003 09:30:52 -0600
Received: from ct.ct.med.ge.com ([3.70.56.18]) by uswaumsxbhmedge.med.ge.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2656.59)
	id 1FHJGWBZ; Fri, 7 Feb 2003 09:30:35 -0600
Received: from med.ge.com ([3.57.108.2])
	by ct.ct.med.ge.com (8.8.8+Sun/8.8.8) with ESMTP id JAA24346;
	Fri, 7 Feb 2003 09:30:32 -0600 (CST)
From: "Foris, Jim (MED)" <foris@mr.mr.med.ge.com>
To: Keith Owens <kaos@sgi.com>
Cc: "Foris, Jim (MED)" <foris@mr.med.ge.com>, kdb@oss.sgi.com
Message-ID: <3E43D2D7.9090609@med.ge.com>
Date: Fri, 07 Feb 2003 09:37:59 -0600
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021218
X-Accept-Language: en-us, en
MIME-Version: 1.0
Subject: Re: using kdb on Red Hat/SGI linux-2.4.18-18SGI_XFS_1.2pre5
References: <23389.1044576020@kao2.melbourne.sgi.com>
In-Reply-To: <23389.1044576020@kao2.melbourne.sgi.com>
Content-Type: multipart/mixed;
 boundary="------------090606010908060004020909"
X-archive-position: 236
X-ecartis-version: Ecartis v1.0.0
Sender: kdb-bounce@oss.sgi.com
Errors-to: kdb-bounce@oss.sgi.com
X-original-sender: foris@mr.mr.med.ge.com
Precedence: bulk
X-list: kdb

This is a multi-part message in MIME format.
--------------090606010908060004020909
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Keith Owens wrote:
> On Thu, 06 Feb 2003 17:22:25 -0600, 
> "Foris, Jim (MED)" <foris@mr.mr.med.ge.com> wrote:
> 
>>Keith Owens wrote:
>>
>>>Use the nmi watchdog, boot with nmi_watchdog=1.
>>
>>Did that... made no difference.
>>
>>We think it is because CPU0 handles all NMIs.... so if it dies,
>>so does the NMI watchdog.
> 
> 
> NMI should be broadcast.  Before the system hangs, cat /proc/interrupts.
> The NMI count on each cpu must be non-zero and increasing continuously
> if the nmi watchdog is working.

You are right; interrupts are being shared now. (see attached interrupts.txt).
> 
> 
>>[1]kdb> bt
>>ESP        EIP        Function (args)
>>0xc46cde28 0xc01ed880 <unknown>+0xc01ed880
>>                               kernel <unknown> 0x0 0x0 0x0
>>0xc46cde2c 0xc46cdde0 <unknown>+0xc46cdde0
>>                               kernel <unknown> 0x0 0x0 0x0
> 
> 
> That is wierd.  grep kallsyms System.map and insmod -nm some_module_name.
See attached grep.txt and insmod.txt for results.
> 



--------------090606010908060004020909
Content-Type: text/plain;
 name="grep.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="grep.txt"

c012c150 t kallsyms_get_module_list
c012c200 T kallsyms_symbol_to_address
c012c4b0 T kallsyms_address_to_symbol
c012c670 T kallsyms_sections
c0300d80 ? __kstrtab___start___kallsyms
c0300dc0 ? __kstrtab___stop___kallsyms
c0300de0 ? __kstrtab_kallsyms_address_to_symbol
c030dbf0 ? __ksymtab___start___kallsyms
c030dbf8 ? __ksymtab___stop___kallsyms
c030dc00 ? __ksymtab_kallsyms_address_to_symbol
c03a01a3 A __start___kallsyms
c03a01a3 A __stop___kallsyms
c046b2a4 b kallsyms_module_list

--------------090606010908060004020909
Content-Type: text/plain;
 name="insmod.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="insmod.txt"

Using /lib/modules/2.4.18-18SGI_XFS_1.2pre5smp/kernel/drivers/scsi/sg.o
Sections:       Size      Address   Align
.this           00000060  12340000  2**2
.text           000061c0  12340060  2**4
.fixup          00000207  12346220  2**0
.rodata.str1.1  000004ce  12346427  2**0
.rodata.str1.32 00000b80  12346900  2**5
__ex_table      000001d8  12347480  2**2
.rodata         00000050  12347660  2**4
.kstrtab        000000d0  123476b0  2**0
.kmodtab        0000000c  12347780  2**2
__ksymtab       00000030  1234778c  2**2
__archdata      00000000  123477c0  2**4
__kallsyms      00000cfa  123477c0  2**2
.data           00000160  123484c0  2**5
.bss            00000004  12348620  2**2

Symbols:
00000000 a sg.c
12340000 d __this_module
12340000 D __insmod_sg_O/lib/modules/2.4.18-18SGI_XFS_1.2pre5smp/kernel/drivers/scsi/sg.o_M3E431261_V132114
12340060 t gcc2_compiled.
12340060 T __insmod_sg_S.text_L25024
12340060 t .text
12340060 t sg_open
123402f0 t sg_release
12340400 t sg_read
123407a0 t sg_new_read
123408d0 t sg_write
12340b80 t sg_new_write
12340dc0 t sg_common_write
12341020 t sg_ioctl
12341d90 t sg_poll
12341ea0 t sg_fasync
12341f10 t sg_rb_correct4mmap
12342040 t sg_vma_nopage
12342130 t sg_mmap
12342270 t sg_cmd_done_bh
12342610 t sg_detect
12342620 t sg_init
12342750 t sg_attach
123429c0 t sg_finish
123429d0 t sg_detach
12342bf0 t init_sg
12342bf0 t init_module
12342c20 t cleanup_module
12342c20 t exit_sg
12342c70 t sg_start_req
12342d60 t sg_finish_rem_req
12342dd0 t sg_build_sgat
12342e60 t sg_unmap_and
12342ec0 t sg_build_dir
12343130 t sg_build_indi
12343350 t sg_write_xfer
123436a0 t sg_u_iovec
12343730 t sg_get_sgat_msa
12343760 t sg_remove_scat
12343880 t sg_read_xfer
12343bc0 t sg_read_oxfer
12343cd0 t sg_build_reserve
12343d40 t sg_link_reserve
12343e60 t sg_unlink_reserve
12343f10 t sg_get_rq_mark
12343f80 t sg_get_nth_request
12343fc0 t sg_add_request
12344090 t sg_remove_request
12344130 t sg_get_nth_sfp
12344170 t sg_add_sfp
123442a0 t __sg_remove_sfp
12344360 t sg_remove_sfp
123444a0 t sg_res_in_use
123444e0 t sg_low_malloc
123447e0 t sg_malloc
12344980 t sg_low_free
12344a20 t sg_free
12344a70 t sg_ms_to_jif
12344ac0 t sg_allow_access
12344af0 t sg_last_dev
12344b40 t sg_get_dev
12344b90 t sg_proc_init
12344c30 t sg_proc_cleanup
12344c90 t sg_proc_adio_read
12344d10 t sg_proc_adio_info
12344d80 t sg_proc_adio_write
12344e30 t sg_proc_dressz_read
12344eb0 t sg_proc_dressz_info
12344f20 t sg_proc_dressz_write
12344fd0 t sg_proc_debug_read
12345050 t sg_proc_debug_info
12345790 t sg_proc_dev_read
12345810 t sg_proc_dev_info
12345920 t sg_proc_devhdr_read
123459a0 t sg_proc_devhdr_info
12345a00 t sg_proc_devstrs_read
12345a80 t sg_proc_devstrs_info
12345b60 t sg_proc_host_read
12345be0 t sg_proc_host_info
12345cf0 t sg_proc_hosthdr_read
12345d70 t sg_proc_hosthdr_info
12345dd0 t sg_proc_hoststrs_read
12345e50 t sg_proc_hoststrs_info
12345fd0 t sg_proc_version_read
12346050 t sg_proc_version_info
123460c0 t sg_jif_to_ms
12346110 t sg_alloc_kiovec
12346130 t sg_free_kiovec
12346146 t .text.lock.sg
12346220 t .fixup
12346427 r .rodata.str1.1
12346900 r .rodata.str1.32
12347480 r __ex_table
12347660 r .rodata
12347660 R __insmod_sg_S.rodata_L80
123484c0 d .data
123484c0 d sg_version_str
123484c0 D __insmod_sg_S.data_L352
123484c4 d sg_version_num
123484c8 D sg_big_buff
123484cc d def_reserved_size
123484d0 d sg_allow_dio
123484d4 d sg_pool_secs_avail
123484d8 d sg_dev_arr_lock
123484e0 d sg_template
12348528 d sg_dev_arr
1234852c d sg_mmap_vm_ops
12348540 d sg_fops
12348588 d sg_registered.0
1234858c d allow_ops
12348598 d sg_proc_sgp
1234859c d sg_proc_sg_dirname
123485a0 d sg_proc_leaf_names
123485c8 d sg_proc_leaf_reads
123485f0 d sg_proc_leaf_writes
12348620 D __insmod_sg_S.bss_L4
12348620 d .bss
12348620 d dummy_cmdp

--------------090606010908060004020909
Content-Type: text/plain;
 name="interrupts.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="interrupts.txt"

           CPU0       CPU1       CPU2       CPU3       
  0:     192726     192480     196369     196640    IO-APIC-edge  timer
  1:        161        161        161        161    IO-APIC-edge  keyboard
  2:          0          0          0          0          XT-PIC  cascade
  8:          1          0          0          0    IO-APIC-edge  rtc
 12:        498        528        500        503    IO-APIC-edge  PS/2 Mouse
 15:          3          2          2          3    IO-APIC-edge  ide1
 16:         95         92         97         94   IO-APIC-level  usb-uhci, eth2
 17:       3049       3038       3053       3047   IO-APIC-level  nvidia
 18:          0          0          0          0   IO-APIC-level  usb-uhci
 19:          0          0          0          0   IO-APIC-level  usb-uhci
 22:          0          0          0          0   IO-APIC-level  Digi DBX2
 26:       2385       2195       2313       2548   IO-APIC-level  ioc0
 27:         15          2          9         14   IO-APIC-level  ioc1
 48:         15          3         17         13   IO-APIC-level  qla1280
NMI:          1          1          2          2 
LOC:     778042     778037     778039     778018 
ERR:          0
MIS:          0

--------------090606010908060004020909--

From kaos@sgi.com Fri Feb  7 17:51:11 2003
Received: with ECARTIS (v1.0.0; list kdb); Fri, 07 Feb 2003 17:51:16 -0800 (PST)
Received: from mail.ocs.com.au (mail.ocs.com.au [203.34.97.2])
	by oss.sgi.com (8.12.5/8.12.5) with SMTP id h181p83v023592
	for <kdb@oss.sgi.com>; Fri, 7 Feb 2003 17:51:09 -0800
Received: (qmail 1162 invoked from network); 8 Feb 2003 01:58:58 -0000
Received: from ocs3.intra.ocs.com.au (192.168.255.3)
  by mail.ocs.com.au with SMTP; 8 Feb 2003 01:58:58 -0000
Received: by ocs3.intra.ocs.com.au (Postfix, from userid 16331)
	id 91A1B3000B8; Sat,  8 Feb 2003 12:58:55 +1100 (EST)
Received: from ocs3.intra.ocs.com.au (localhost [127.0.0.1])
	by ocs3.intra.ocs.com.au (Postfix) with ESMTP
	id 5F97E8F; Sat,  8 Feb 2003 12:58:55 +1100 (EST)
X-Mailer: exmh version 2.4 06/23/2000 with nmh-1.0.4
From: Keith Owens <kaos@sgi.com>
To: "Foris, Jim (MED)" <foris@mr.med.ge.com>, kdb@oss.sgi.com
Subject: Re: using kdb on Red Hat/SGI linux-2.4.18-18SGI_XFS_1.2pre5 
In-reply-to: Your message of "Fri, 07 Feb 2003 09:37:59 MDT."
             <3E43D2D7.9090609@med.ge.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 08 Feb 2003 12:58:50 +1100
Message-ID: <4491.1044669530@ocs3.intra.ocs.com.au>
X-archive-position: 237
X-ecartis-version: Ecartis v1.0.0
Sender: kdb-bounce@oss.sgi.com
Errors-to: kdb-bounce@oss.sgi.com
X-original-sender: kaos@sgi.com
Precedence: bulk
X-list: kdb

On Fri, 07 Feb 2003 09:37:59 -0600, 
"Foris, Jim (MED)" <foris@mr.mr.med.ge.com> wrote:
>>>[1]kdb> bt
>>>ESP        EIP        Function (args)
>>>0xc46cde28 0xc01ed880 <unknown>+0xc01ed880
>>>                               kernel <unknown> 0x0 0x0 0x0
>>>0xc46cde2c 0xc46cdde0 <unknown>+0xc46cdde0
>>>                               kernel <unknown> 0x0 0x0 0x0
>> 
>> 
>> That is wierd.  grep kallsyms System.map and insmod -nm some_module_name.
>
>c03a01a3 A __start___kallsyms
>c03a01a3 A __stop___kallsyms

There is the problem, your kernel has no data in the kallasyms section
(__start___kallsyms == __stop___kallsyms).  The empty kernel kallsyms
in turn stops modules from loading kallsyms.  This is a build problem
with your system, it works for other people.

Make sure that you have the current version of modules (2.4.22), that
your build is not overriding the KALLSYMS environment variable and that
kallsyms is being run as part of the vmlinux build.  If there is no
obvious problem, edit the top level Makefile and delete this line

	@rm -f $(TMPPREFIX).tmp_vmlinux* $(TMPPREFIX).tmp_kallsyms*

make vmlinux then ls -l .tmp_vmlinux* .tmp_kallsyms*


From sonic.zhang@intel.com Fri Feb  7 20:15:48 2003
Received: with ECARTIS (v1.0.0; list kdb); Fri, 07 Feb 2003 20:15:54 -0800 (PST)
Received: from hermes.fm.intel.com (fmr01.intel.com [192.55.52.18])
	by oss.sgi.com (8.12.5/8.12.5) with SMTP id h184Fm3v024358
	for <kdb@oss.sgi.com>; Fri, 7 Feb 2003 20:15:48 -0800
Received: from petasus.fm.intel.com (petasus.fm.intel.com [10.1.192.37])
	by hermes.fm.intel.com (8.11.6/8.11.6/d: outer.mc,v 1.51 2002/09/23 20:43:23 dmccart Exp $) with ESMTP id h184Kko24032
	for <kdb@oss.sgi.com>; Sat, 8 Feb 2003 04:20:46 GMT
Received: from pdsmsxvs01.pd.intel.com (pdsmsxvs01.pd.intel.com [172.16.12.122])
	by petasus.fm.intel.com (8.11.6/8.11.6/d: inner.mc,v 1.28 2003/01/13 19:44:39 dmccart Exp $) with SMTP id h184ITR06713
	for <kdb@oss.sgi.com>; Sat, 8 Feb 2003 04:18:29 GMT
Received: from pdsmsx17.pd.intel.com ([172.16.12.121])
 by pdsmsxvs01.pd.intel.com (NAVGW 2.5.2.11) with SMTP id M2003020812233908616
 for <kdb@oss.sgi.com>; Sat, 08 Feb 2003 12:23:39 +0800
Received: by pdsmsx17.pd.intel.com with Internet Mail Service (5.5.2653.19)
	id <1AW1Z678>; Sat, 8 Feb 2003 12:22:33 +0800
Message-ID: <957BD1C2BF3CD411B6C500A0C944CA2602E9552D@pdsmsx32.pd.intel.com>
From: "Zhang, Sonic" <sonic.zhang@intel.com>
To: "KDB (E-mail)" <kdb@oss.sgi.com>
Subject: 1 bug cause the kdb-3.0-2.4.20 patch fail to compile
Date: Sat, 8 Feb 2003 12:21:25 +0800 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="gb2312"
X-archive-position: 238
X-ecartis-version: Ecartis v1.0.0
Sender: kdb-bounce@oss.sgi.com
Errors-to: kdb-bounce@oss.sgi.com
X-original-sender: sonic.zhang@intel.com
Precedence: bulk
X-list: kdb

Hi,

	After I applied the kdb-3.0-2.4.20 patch to kernel 2.4.20, I failed
to compile the new kernel with USB keyboard supported in KDB. I find one
type is used before defined in file arch/i386/kdb/kdba_io.c. I changed the
type and compile the kernel successfully.
	Please see my change.

--- linux/arch/i386/kdb/kdba_io.c	Sat Feb  8 12:07:19 2003
+++ linux-tmp/arch/i386/kdb/kdba_io.c	Sat Feb  8 12:09:01 2003
@@ -90,7 +90,7 @@
     		return -1;
 
 	/* Transfer char if they are present */
-	(*kdb_usb_infos.poll_func)(kdb_usb_infos.uhci, (urb_t
*)kdb_usb_infos.urb);
+	(*kdb_usb_infos.poll_func)(kdb_usb_infos.uhci, (struct urb
*)kdb_usb_infos.urb);
 
 	spec = kdb_usb_infos.buffer[0];
 	keycode = kdb_usb_infos.buffer[2];


*************************************
Sonic Zhang
  
Software Engineer
Intel China Software Lab

Tel: 021-52574545-1667 
iNet: 8-752-1667 
*************************************
 

From kaos@sgi.com Fri Feb  7 21:07:28 2003
Received: with ECARTIS (v1.0.0; list kdb); Fri, 07 Feb 2003 21:07:30 -0800 (PST)
Received: from mail.ocs.com.au (mail.ocs.com.au [203.34.97.2])
	by oss.sgi.com (8.12.5/8.12.5) with SMTP id h1857P3v024598
	for <kdb@oss.sgi.com>; Fri, 7 Feb 2003 21:07:27 -0800
Received: (qmail 2663 invoked from network); 8 Feb 2003 05:15:17 -0000
Received: from ocs3.intra.ocs.com.au (192.168.255.3)
  by mail.ocs.com.au with SMTP; 8 Feb 2003 05:15:17 -0000
Received: by ocs3.intra.ocs.com.au (Postfix, from userid 16331)
	id 913393000B8; Sat,  8 Feb 2003 16:15:15 +1100 (EST)
Received: from ocs3.intra.ocs.com.au (localhost [127.0.0.1])
	by ocs3.intra.ocs.com.au (Postfix) with ESMTP
	id 58C928F; Sat,  8 Feb 2003 16:15:15 +1100 (EST)
X-Mailer: exmh version 2.4 06/23/2000 with nmh-1.0.4
From: Keith Owens <kaos@sgi.com>
To: "Zhang, Sonic" <sonic.zhang@intel.com>
Cc: "KDB (E-mail)" <kdb@oss.sgi.com>
Subject: Re: 1 bug cause the kdb-3.0-2.4.20 patch fail to compile 
In-reply-to: Your message of "Sat, 08 Feb 2003 12:21:25 +0800."
             <957BD1C2BF3CD411B6C500A0C944CA2602E9552D@pdsmsx32.pd.intel.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 08 Feb 2003 16:15:10 +1100
Message-ID: <6339.1044681310@ocs3.intra.ocs.com.au>
X-archive-position: 239
X-ecartis-version: Ecartis v1.0.0
Sender: kdb-bounce@oss.sgi.com
Errors-to: kdb-bounce@oss.sgi.com
X-original-sender: kaos@sgi.com
Precedence: bulk
X-list: kdb

On Sat, 8 Feb 2003 12:21:25 +0800 , 
"Zhang, Sonic" <sonic.zhang@intel.com> wrote:
>	After I applied the kdb-3.0-2.4.20 patch to kernel 2.4.20, I failed
>to compile the new kernel with USB keyboard supported in KDB. I find one
>type is used before defined in file arch/i386/kdb/kdba_io.c. I changed the
>type and compile the kernel successfully.
>	Please see my change.
>
>--- linux/arch/i386/kdb/kdba_io.c	Sat Feb  8 12:07:19 2003
>+++ linux-tmp/arch/i386/kdb/kdba_io.c	Sat Feb  8 12:09:01 2003
>@@ -90,7 +90,7 @@
>     		return -1;
> 
> 	/* Transfer char if they are present */
>-	(*kdb_usb_infos.poll_func)(kdb_usb_infos.uhci, (urb_t
>*)kdb_usb_infos.urb);
>+	(*kdb_usb_infos.poll_func)(kdb_usb_infos.uhci, (struct urb
>*)kdb_usb_infos.urb);
> 
> 	spec = kdb_usb_infos.buffer[0];
> 	keycode = kdb_usb_infos.buffer[2];

Thanks, nobody has volunteered to support the usb code in kdb.  I have
given up with the usb code and planning to remove it.

Your mailer is still mangling patches, the wrapped lines are from your
end.

BTW, are you happy with the command editting in v3.0, especially my
changes to add vt100 sequences?


From sonic.zhang@intel.com Fri Feb  7 23:06:23 2003
Received: with ECARTIS (v1.0.0; list kdb); Fri, 07 Feb 2003 23:06:28 -0800 (PST)
Received: from hermes.jf.intel.com (fmr05.intel.com [134.134.136.6])
	by oss.sgi.com (8.12.5/8.12.5) with SMTP id h1876M3v025199
	for <kdb@oss.sgi.com>; Fri, 7 Feb 2003 23:06:23 -0800
Received: from talaria.jf.intel.com (talaria.jf.intel.com [10.7.209.7])
	by hermes.jf.intel.com (8.11.6/8.11.6/d: outer.mc,v 1.51 2002/09/23 20:43:23 dmccart Exp $) with ESMTP id h187CGi16533
	for <kdb@oss.sgi.com>; Sat, 8 Feb 2003 07:12:16 GMT
Received: from pdsmsxvs01.pd.intel.com (pdsmsxvs01.pd.intel.com [172.16.12.122])
	by talaria.jf.intel.com (8.11.6/8.11.6/d: inner.mc,v 1.28 2003/01/13 19:44:39 dmccart Exp $) with SMTP id h186rYd19870
	for <kdb@oss.sgi.com>; Sat, 8 Feb 2003 06:53:34 GMT
Received: from pdsmsx17.pd.intel.com ([172.16.12.121])
 by pdsmsxvs01.pd.intel.com (NAVGW 2.5.2.11) with SMTP id M2003020815140917239
 ; Sat, 08 Feb 2003 15:14:09 +0800
Received: by pdsmsx17.pd.intel.com with Internet Mail Service (5.5.2653.19)
	id <1AW1Z9KS>; Sat, 8 Feb 2003 15:13:03 +0800
Message-ID: <957BD1C2BF3CD411B6C500A0C944CA2602E95584@pdsmsx32.pd.intel.com>
From: "Zhang, Sonic" <sonic.zhang@intel.com>
To: Keith Owens <kaos@sgi.com>
Cc: "KDB (E-mail)" <kdb@oss.sgi.com>
Subject: RE: 1 bug cause the kdb-3.0-2.4.20 patch fail to compile 
Date: Sat, 8 Feb 2003 15:11:54 +0800 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-archive-position: 240
X-ecartis-version: Ecartis v1.0.0
Sender: kdb-bounce@oss.sgi.com
Errors-to: kdb-bounce@oss.sgi.com
X-original-sender: sonic.zhang@intel.com
Precedence: bulk
X-list: kdb

Hi,

	Yes, your addition to VT100 character sequence works well. 
	But I wonder why you don't add these translation in architecture
dependent function "static int get_serial_char(void);". I think it is better
to return the meaningful ASCII characters in these architecture dependent
functions.

	Regards.

	Sonic Zhang


-----Original Message-----
From: Keith Owens [mailto:kaos@sgi.com]
Sent: 2003?2?8? 13:15
To: Zhang, Sonic
Cc: KDB (E-mail)
Subject: Re: 1 bug cause the kdb-3.0-2.4.20 patch fail to compile 


On Sat, 8 Feb 2003 12:21:25 +0800 , 
"Zhang, Sonic" <sonic.zhang@intel.com> wrote:
>	After I applied the kdb-3.0-2.4.20 patch to kernel 2.4.20, I failed
>to compile the new kernel with USB keyboard supported in KDB. I find one
>type is used before defined in file arch/i386/kdb/kdba_io.c. I changed the
>type and compile the kernel successfully.
>	Please see my change.
>
>--- linux/arch/i386/kdb/kdba_io.c	Sat Feb  8 12:07:19 2003
>+++ linux-tmp/arch/i386/kdb/kdba_io.c	Sat Feb  8 12:09:01 2003
>@@ -90,7 +90,7 @@
>     		return -1;
> 
> 	/* Transfer char if they are present */
>-	(*kdb_usb_infos.poll_func)(kdb_usb_infos.uhci, (urb_t
>*)kdb_usb_infos.urb);
>+	(*kdb_usb_infos.poll_func)(kdb_usb_infos.uhci, (struct urb
>*)kdb_usb_infos.urb);
> 
> 	spec = kdb_usb_infos.buffer[0];
> 	keycode = kdb_usb_infos.buffer[2];

Thanks, nobody has volunteered to support the usb code in kdb.  I have
given up with the usb code and planning to remove it.

Your mailer is still mangling patches, the wrapped lines are from your
end.

BTW, are you happy with the command editting in v3.0, especially my
changes to add vt100 sequences?

From kaos@sgi.com Fri Feb  7 23:47:18 2003
Received: with ECARTIS (v1.0.0; list kdb); Fri, 07 Feb 2003 23:47:23 -0800 (PST)
Received: from mail.ocs.com.au (mail.ocs.com.au [203.34.97.2])
	by oss.sgi.com (8.12.5/8.12.5) with SMTP id h187lF3v025327
	for <kdb@oss.sgi.com>; Fri, 7 Feb 2003 23:47:16 -0800
Received: (qmail 3355 invoked from network); 8 Feb 2003 07:55:07 -0000
Received: from ocs3.intra.ocs.com.au (192.168.255.3)
  by mail.ocs.com.au with SMTP; 8 Feb 2003 07:55:07 -0000
Received: by ocs3.intra.ocs.com.au (Postfix, from userid 16331)
	id 742703000B8; Sat,  8 Feb 2003 18:55:05 +1100 (EST)
Received: from ocs3.intra.ocs.com.au (localhost [127.0.0.1])
	by ocs3.intra.ocs.com.au (Postfix) with ESMTP
	id 5DEF28F; Sat,  8 Feb 2003 18:55:05 +1100 (EST)
X-Mailer: exmh version 2.4 06/23/2000 with nmh-1.0.4
From: Keith Owens <kaos@sgi.com>
To: "Zhang, Sonic" <sonic.zhang@intel.com>
Cc: "KDB (E-mail)" <kdb@oss.sgi.com>
Subject: Re: 1 bug cause the kdb-3.0-2.4.20 patch fail to compile 
In-reply-to: Your message of "Sat, 08 Feb 2003 15:11:54 +0800."
             <957BD1C2BF3CD411B6C500A0C944CA2602E95584@pdsmsx32.pd.intel.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 08 Feb 2003 18:55:00 +1100
Message-ID: <7243.1044690900@ocs3.intra.ocs.com.au>
X-archive-position: 241
X-ecartis-version: Ecartis v1.0.0
Sender: kdb-bounce@oss.sgi.com
Errors-to: kdb-bounce@oss.sgi.com
X-original-sender: kaos@sgi.com
Precedence: bulk
X-list: kdb

On Sat, 8 Feb 2003 15:11:54 +0800 , 
"Zhang, Sonic" <sonic.zhang@intel.com> wrote:
>	Yes, your addition to VT100 character sequence works well. 
>	But I wonder why you don't add these translation in architecture
>dependent function "static int get_serial_char(void);". I think it is better
>to return the meaningful ASCII characters in these architecture dependent
>functions.

(1) vt100 is a global definition, not architecture specific.

(2) The timing algorithms for vt100 mean that you need a global view of
    all input sources to determine if the current character is part of
    the current vt100 sequence or something else from another data
    source.


From getelson@softhome.net Wed Feb 12 00:01:45 2003
Received: with ECARTIS (v1.0.0; list kdb); Wed, 12 Feb 2003 00:02:01 -0800 (PST)
Received: from jive.SoftHome.net (jive.SoftHome.net [66.54.152.27])
	by oss.sgi.com (8.12.5/8.12.5) with SMTP id h1C81i3v011010
	for <kdb@oss.sgi.com>; Wed, 12 Feb 2003 00:01:45 -0800
Received: (qmail 4686 invoked by uid 417); 12 Feb 2003 08:09:55 -0000
Received: from slide-.softhome.net (HELO softhome.net) (172.16.2.21)
  by shunt-smtp-out-0 with SMTP; 12 Feb 2003 08:09:55 -0000
Received: from localhost (localhost [127.0.0.1])
  (uid 417)
  by softhome.net with local; Wed, 12 Feb 2003 01:09:55 -0700
From: getelson@softhome.net
To: kdb@oss.sgi.com
Subject: kdb patch for 2.2.14
Date: Wed, 12 Feb 2003 01:09:55 -0700
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Sender: getelson@softhome.net
X-Originating-IP: [194.29.36.33]
Message-ID: <courier.3E4A0153.0000718B@softhome.net>
X-archive-position: 242
X-ecartis-version: Ecartis v1.0.0
Sender: kdb-bounce@oss.sgi.com
Errors-to: kdb-bounce@oss.sgi.com
X-original-sender: getelson@softhome.net
Precedence: bulk
X-list: kdb

Hello, 

Where can I find a kdb patch for 2.2.14 kernel? 

Gregory

From sonic.zhang@intel.com Wed Feb 12 00:55:27 2003
Received: with ECARTIS (v1.0.0; list kdb); Wed, 12 Feb 2003 00:55:31 -0800 (PST)
Received: from caduceus.fm.intel.com (fmr02.intel.com [192.55.52.25])
	by oss.sgi.com (8.12.5/8.12.5) with SMTP id h1C8tQ3v011502
	for <kdb@oss.sgi.com>; Wed, 12 Feb 2003 00:55:27 -0800
Received: from talaria.fm.intel.com (talaria.fm.intel.com [10.1.192.39])
	by caduceus.fm.intel.com (8.11.6/8.11.6/d: outer.mc,v 1.51 2002/09/23 20:43:23 dmccart Exp $) with ESMTP id h1C8vcc14944
	for <kdb@oss.sgi.com>; Wed, 12 Feb 2003 08:57:38 GMT
Received: from pdsmsxvs01.pd.intel.com (pdsmsxvs01.pd.intel.com [172.16.12.122])
	by talaria.fm.intel.com (8.11.6/8.11.6/d: inner.mc,v 1.28 2003/01/13 19:44:39 dmccart Exp $) with SMTP id h1C95MD08897
	for <kdb@oss.sgi.com>; Wed, 12 Feb 2003 09:05:22 GMT
Received: from pdsmsx17.pd.intel.com ([172.16.12.121])
 by pdsmsxvs01.pd.intel.com (NAVGW 2.5.2.11) with SMTP id M2003021217033413954
 for <kdb@oss.sgi.com>; Wed, 12 Feb 2003 17:03:34 +0800
Received: by pdsmsx17.pd.intel.com with Internet Mail Service (5.5.2653.19)
	id <1AW191F0>; Wed, 12 Feb 2003 17:02:27 +0800
Message-ID: <957BD1C2BF3CD411B6C500A0C944CA2602FB01E9@pdsmsx32.pd.intel.com>
From: "Zhang, Sonic" <sonic.zhang@intel.com>
To: "KDB (E-mail)" <kdb@oss.sgi.com>
Cc: "WangFrank (E-mail)" <frank.wang@intel.com>,
   "XieMay (E-mail)"
	 <may.xie@intel.com>
Subject: I fix a bug in kdb-v3.0-2.4.20, which cause the hardware breakpoi
	nts fail to work.
Date: Wed, 12 Feb 2003 17:01:17 +0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_000_01C2D275.4D96CBD0"
X-archive-position: 243
X-ecartis-version: Ecartis v1.0.0
Sender: kdb-bounce@oss.sgi.com
Errors-to: kdb-bounce@oss.sgi.com
X-original-sender: sonic.zhang@intel.com
Precedence: bulk
X-list: kdb

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_000_01C2D275.4D96CBD0
Content-Type: text/plain;
	charset="gb2312"

Hi,
	I have reported this bug for kdb-v2.5-2.4.19 before. It still exist
in kdb-v3.0-2.4.20.

	The following lines are in my former mail. 
----------------------------------------------------------------------------
----
Hi,

	I find this bug in KDB patch "kdb-v2.5-2.4.19" together with
pristine kernel 2.4.19.
	This bug doesn't happen on "bp" or "bpa".

	The steps to reproduce:
	1. Enter KDB by key "Pause"
	2. bph printk (or bpha printk)
	3. go
	4. insmod testkdb.o ( This is my test module, which prints messages
by "printk" in the initialization routine. Compile file "testkdb.c" before
do the test.)
	
	The result:
	Fail to trap into KDB at the breakpoint.
----------------------------------------------------------------------------
----


	Now, I find the root cause and attach a patch file for kernel 2.4.20
with kdb-v3.0-2.4.20 patches.

	In the signal handler in file "arch/i386/kernel/signal.c", the debug
register dr7 is set with the corresponding field in the task structure of
the current process. This field is used by a user space debugger such as
gdb. It replaces the value set by KDB, which cause the KDB hardware break
point fails to work. 

		
		/* Reenable any watchpoints before delivering the
		 * signal to user space. The processor register will
		 * have been cleared if the watchpoint triggered
		 * inside the kernel.
		 */
		__asm__("movl %0,%%db7"	: : "r"
(current->thread.debugreg[7]));


	I changed these code lines. I allow the kernel signal handle to
change dr7 only when KDB is in the kernel and the variable kdb_on != 0. That
means KDB can't work together with any user space debugger. The user must
make sure he exit any user space debugger before enable the KDB.

	What do you think about my change?
	Please refer to the attachment.

	Thanks


*************************************
Sonic Zhang
  
Software Engineer
Intel China Software Lab

Tel: 021-52574545-1667 
iNet: 8-752-1667 
*************************************
 


------_=_NextPart_000_01C2D275.4D96CBD0
Content-Type: application/octet-stream;
	name="kdb-signal-v3.0-2.4.20-i386-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="kdb-signal-v3.0-2.4.20-i386-1"

--- linux-kdb-tmp/arch/i386/kernel/signal.c	Thu Feb 13 16:17:37 2003=0A=
+++ linux-kdb/arch/i386/kernel/signal.c	Thu Feb 13 16:16:29 2003=0A=
@@ -20,6 +20,11 @@=0A=
 #include <linux/stddef.h>=0A=
 #include <linux/tty.h>=0A=
 #include <linux/personality.h>=0A=
+=0A=
+#ifdef CONFIG_KDB=0A=
+#include <linux/kdb.h>=0A=
+#endif /* CONFIG_KDB */=0A=
+=0A=
 #include <asm/ucontext.h>=0A=
 #include <asm/uaccess.h>=0A=
 #include <asm/i387.h>=0A=
@@ -695,7 +700,12 @@=0A=
 		 * have been cleared if the watchpoint triggered=0A=
 		 * inside the kernel.=0A=
 		 */=0A=
+#ifdef CONFIG_KDB=0A=
+		if(!kdb_on)=0A=
+			__asm__("movl %0,%%db7"	: : "r" (current->thread.debugreg[7]));=0A=
+#else /* CONFIG_KDB*/=0A=
 		__asm__("movl %0,%%db7"	: : "r" (current->thread.debugreg[7]));=0A=
+#endif /* CONFIG_KDB*/=0A=
 =0A=
 		/* Whee!  Actually deliver the signal.  */=0A=
 		handle_signal(signr, ka, &info, oldset, regs);=0A=

------_=_NextPart_000_01C2D275.4D96CBD0--

From kaos@sgi.com Wed Feb 12 01:18:14 2003
Received: with ECARTIS (v1.0.0; list kdb); Wed, 12 Feb 2003 01:18:19 -0800 (PST)
Received: from mail.ocs.com.au (mail.ocs.com.au [203.34.97.2])
	by oss.sgi.com (8.12.5/8.12.5) with SMTP id h1C9IB3v015007
	for <kdb@oss.sgi.com>; Wed, 12 Feb 2003 01:18:13 -0800
Received: (qmail 829 invoked from network); 12 Feb 2003 09:26:21 -0000
Received: from ocs3.intra.ocs.com.au (192.168.255.3)
  by mail.ocs.com.au with SMTP; 12 Feb 2003 09:26:21 -0000
Received: by ocs3.intra.ocs.com.au (Postfix, from userid 16331)
	id BCA0C3000B8; Wed, 12 Feb 2003 20:26:18 +1100 (EST)
Received: from ocs3.intra.ocs.com.au (localhost [127.0.0.1])
	by ocs3.intra.ocs.com.au (Postfix) with ESMTP
	id 412F08F; Wed, 12 Feb 2003 20:26:18 +1100 (EST)
X-Mailer: exmh version 2.4 06/23/2000 with nmh-1.0.4
From: Keith Owens <kaos@sgi.com>
To: getelson@softhome.net
Cc: kdb@oss.sgi.com
Subject: Re: kdb patch for 2.2.14 
In-reply-to: Your message of "Wed, 12 Feb 2003 01:09:55 PDT."
             <courier.3E4A0153.0000718B@softhome.net> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 12 Feb 2003 20:26:12 +1100
Message-ID: <20054.1045041972@ocs3.intra.ocs.com.au>
X-archive-position: 244
X-ecartis-version: Ecartis v1.0.0
Sender: kdb-bounce@oss.sgi.com
Errors-to: kdb-bounce@oss.sgi.com
X-original-sender: kaos@sgi.com
Precedence: bulk
X-list: kdb

On Wed, 12 Feb 2003 01:09:55 -0700, 
getelson@softhome.net wrote:
>Where can I find a kdb patch for 2.2.14 kernel? 

The oldest kdb was against 2.2.18.

ftp://oss.sgi.com/projects/kdb/download/ix86/kdb-v1.5-2.2.18.gz


From kaos@sgi.com Wed Feb 12 01:35:07 2003
Received: with ECARTIS (v1.0.0; list kdb); Wed, 12 Feb 2003 01:35:13 -0800 (PST)
Received: from mail.ocs.com.au (mail.ocs.com.au [203.34.97.2])
	by oss.sgi.com (8.12.5/8.12.5) with SMTP id h1C9Z43v015135
	for <kdb@oss.sgi.com>; Wed, 12 Feb 2003 01:35:05 -0800
Received: (qmail 936 invoked from network); 12 Feb 2003 09:43:14 -0000
Received: from ocs3.intra.ocs.com.au (192.168.255.3)
  by mail.ocs.com.au with SMTP; 12 Feb 2003 09:43:14 -0000
Received: by ocs3.intra.ocs.com.au (Postfix, from userid 16331)
	id 805523000B8; Wed, 12 Feb 2003 20:43:11 +1100 (EST)
Received: from ocs3.intra.ocs.com.au (localhost [127.0.0.1])
	by ocs3.intra.ocs.com.au (Postfix) with ESMTP
	id 0157F8F; Wed, 12 Feb 2003 20:43:10 +1100 (EST)
X-Mailer: exmh version 2.4 06/23/2000 with nmh-1.0.4
From: Keith Owens <kaos@sgi.com>
To: "Zhang, Sonic" <sonic.zhang@intel.com>
Cc: "KDB (E-mail)" <kdb@oss.sgi.com>,
   "WangFrank (E-mail)" <frank.wang@intel.com>,
   "XieMay (E-mail)" <may.xie@intel.com>
Subject: Re: I fix a bug in kdb-v3.0-2.4.20, which cause the hardware breakpoi nts fail to work. 
In-reply-to: Your message of "Wed, 12 Feb 2003 17:01:17 +0800."
             <957BD1C2BF3CD411B6C500A0C944CA2602FB01E9@pdsmsx32.pd.intel.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 12 Feb 2003 20:43:04 +1100
Message-ID: <20146.1045042984@ocs3.intra.ocs.com.au>
X-archive-position: 245
X-ecartis-version: Ecartis v1.0.0
Sender: kdb-bounce@oss.sgi.com
Errors-to: kdb-bounce@oss.sgi.com
X-original-sender: kaos@sgi.com
Precedence: bulk
X-list: kdb

On Wed, 12 Feb 2003 17:01:17 +0800, 
"Zhang, Sonic" <sonic.zhang@intel.com> wrote:
>	I changed these code lines. I allow the kernel signal handle to
>change dr7 only when KDB is in the kernel and the variable kdb_on != 0. That
>means KDB can't work together with any user space debugger. The user must
>make sure he exit any user space debugger before enable the KDB.

I tried that in early versions of kdb but the users complained too
much.  It meant that they could not do any debugging on kernels with
kdb compiled in.

Both i386 and ia64 can generate traps when a breakpoint is changed.
What about using that trap to detect a change of hardware breakpoint
and rejecting the user request if kdb is already using that breakpoint
register?  That would only prevent use of gdb if kdb was actually using
a hardware register, instead of banning all gdb use on a kdb enabled
kernel.

We should also change kdb to use breakpoint registers from the top down
instead of bottom up.  That would minimize conflicts with gdb.


From bsuparna@in.ibm.com Wed Feb 12 06:11:41 2003
Received: with ECARTIS (v1.0.0; list kdb); Wed, 12 Feb 2003 06:11:45 -0800 (PST)
Received: from ausmtp02.au.ibm.com (ausmtp02.au.ibm.COM [202.135.136.105])
	by oss.sgi.com (8.12.5/8.12.5) with SMTP id h1CEBX3x003358
	for <kdb@oss.sgi.com>; Wed, 12 Feb 2003 06:11:41 -0800
Received: from d23rh902.au.ibm.com (d23rh902.au.ibm.com [9.185.167.101])
	by ausmtp02.au.ibm.com (8.12.6/8.12.6) with ESMTP id h1CEJvaE162230;
	Thu, 13 Feb 2003 01:19:58 +1100
Received: from d23m0062.in.ibm.com (d23av02.au.ibm.com [9.185.167.107])
	by d23rh902.au.ibm.com (8.12.3/NCO/VER6.5) with ESMTP id h1CEJWXD097542;
	Thu, 13 Feb 2003 01:19:33 +1100
X-Priority: 1 (High)
Subject: Re: I fix a bug in kdb-v3.0-2.4.20, which cause the hardware breakpoi nts
 fail to work.
To: Keith Owens <kaos@sgi.com>
Cc: "WangFrank (E-mail)" <frank.wang@intel.com>,
   "KDB (E-mail)" <kdb@oss.sgi.com>, kdb-bounce@oss.sgi.com,
   "XieMay (E-mail)" <may.xie@intel.com>,
   "Zhang, Sonic" <sonic.zhang@intel.com>
X-Mailer: Lotus Notes Release 5.07a  May 14, 2001
Message-ID: <OFC740D690.83F7034A-ON65256CCB.004E2547@in.ibm.com>
From: "Suparna Bhattacharya" <bsuparna@in.ibm.com>
Date: Wed, 12 Feb 2003 19:38:06 +0530
X-MIMETrack: Serialize by Router on d23m0062/23/M/IBM(Release 5.0.9a |January 7, 2002) at
 12/02/2003 07:38:09 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
X-archive-position: 246
X-ecartis-version: Ecartis v1.0.0
Sender: kdb-bounce@oss.sgi.com
Errors-to: kdb-bounce@oss.sgi.com
X-original-sender: bsuparna@in.ibm.com
Precedence: bulk
X-list: kdb


Perhaps you are already aware of this, but thought I'd mention that the
debug register allocation patch which we used for watchpoint support in
dprobes/kprobes, also addressed this very same problem. It modifies ptrace
and any other facility (e.g dprobes, kdb if present) to use the allocation
interface. It distinguishes between local (per-process) and global (kernel
level - i.e. kdb/dprobes etc) uses of breakpoint registers -  allocates
breakpoint registers top down for the global case (like you suggest), and
makes sure that they don't get overwritten during a context switch.

The following link points to a patch for 2.5 kernel, but should be easy to
put up a 2.4 version, if it helps, since its already part of the dprobes
patch we have for 2.4.20 (http://www-124.ibm.com/linux/projects/dprobes/).

http://www-124.ibm.com/linux/patches/?patch_id=703

Regards
Suparna

  Suparna Bhattacharya
  Linux Technology Center
  IBM Software Lab, India
  6th floor, DLF Square, Gurgaon
  E-mail : bsuparna@in.ibm.com
  Phone :  91-124-6560303, Extn: 744



                                                                                                           
                      Keith Owens                                                                          
                      <kaos@sgi.com>           To:       "Zhang, Sonic" <sonic.zhang@intel.com>            
                      Sent by:                 cc:       "KDB (E-mail)" <kdb@oss.sgi.com>, "WangFrank      
                      kdb-bounce@oss.sg         (E-mail)" <frank.wang@intel.com>, "XieMay (E-mail)"        
                      i.com                     <may.xie@intel.com>                                        
                                               Subject:  Re: I fix a bug in kdb-v3.0-2.4.20, which cause   
                                                the hardware breakpoi nts fail to work.                    
                      02/12/03 03:13 PM                                                                    
                                                                                                           
                                                                                                           



On Wed, 12 Feb 2003 17:01:17 +0800,
"Zhang, Sonic" <sonic.zhang@intel.com> wrote:
>            I changed these code lines. I allow the kernel signal handle
to
>change dr7 only when KDB is in the kernel and the variable kdb_on != 0.
That
>means KDB can't work together with any user space debugger. The user must
>make sure he exit any user space debugger before enable the KDB.

I tried that in early versions of kdb but the users complained too
much.  It meant that they could not do any debugging on kernels with
kdb compiled in.

Both i386 and ia64 can generate traps when a breakpoint is changed.
What about using that trap to detect a change of hardware breakpoint
and rejecting the user request if kdb is already using that breakpoint
register?  That would only prevent use of gdb if kdb was actually using
a hardware register, instead of banning all gdb use on a kdb enabled
kernel.

We should also change kdb to use breakpoint registers from the top down
instead of bottom up.  That would minimize conflicts with gdb.







From sonic.zhang@intel.com Wed Feb 12 17:49:53 2003
Received: with ECARTIS (v1.0.0; list kdb); Wed, 12 Feb 2003 17:49:56 -0800 (PST)
Received: from hermes.jf.intel.com (fmr05.intel.com [134.134.136.6])
	by oss.sgi.com (8.12.5/8.12.5) with SMTP id h1D1nq3v025391
	for <kdb@oss.sgi.com>; Wed, 12 Feb 2003 17:49:53 -0800
Received: from petasus.jf.intel.com (petasus.jf.intel.com [10.7.209.6])
	by hermes.jf.intel.com (8.11.6/8.11.6/d: outer.mc,v 1.51 2002/09/23 20:43:23 dmccart Exp $) with ESMTP id h1D1u6609384
	for <kdb@oss.sgi.com>; Thu, 13 Feb 2003 01:56:06 GMT
Received: from pdsmsxvs01.pd.intel.com (pdsmsxvs01.pd.intel.com [172.16.12.122])
	by petasus.jf.intel.com (8.11.6/8.11.6/d: inner.mc,v 1.28 2003/01/13 19:44:39 dmccart Exp $) with SMTP id h1D1sOO07529
	for <kdb@oss.sgi.com>; Thu, 13 Feb 2003 01:54:25 GMT
Received: from pdsmsx17.pd.intel.com ([172.16.12.121])
 by pdsmsxvs01.pd.intel.com (NAVGW 2.5.2.11) with SMTP id M2003021309575826646
 ; Thu, 13 Feb 2003 09:57:58 +0800
Received: by pdsmsx17.pd.intel.com with Internet Mail Service (5.5.2653.19)
	id <1AW198NK>; Thu, 13 Feb 2003 09:56:50 +0800
Message-ID: <957BD1C2BF3CD411B6C500A0C944CA2602FB0306@pdsmsx32.pd.intel.com>
From: "Zhang, Sonic" <sonic.zhang@intel.com>
To: Keith Owens <kaos@sgi.com>
Cc: "KDB (E-mail)" <kdb@oss.sgi.com>
Subject: RE: I fix a bug in kdb-v3.0-2.4.20, which cause the hardware brea
	kpoi nts fail to work. 
Date: Thu, 13 Feb 2003 09:55:45 +0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-archive-position: 247
X-ecartis-version: Ecartis v1.0.0
Sender: kdb-bounce@oss.sgi.com
Errors-to: kdb-bounce@oss.sgi.com
X-original-sender: sonic.zhang@intel.com
Precedence: bulk
X-list: kdb

Hi,

	I don't think the user can't do any debugging on kernels with KDB
compiled in, because the user can disable KDB by echo "0" to
"/proc/sys/kernel/kdb". The user can switch between KDB and GDB by a command
line. The only problem is that KDB can't work with GDB simultaneously. Does
any user really want to debug his code with KDB and GDB at one time?

	Regards.

	Sonic Zhang



-----Original Message-----
From: Keith Owens [mailto:kaos@sgi.com]
Sent: 2003?2?12? 17:43
To: Zhang, Sonic
Cc: KDB (E-mail); WangFrank (E-mail); XieMay (E-mail)
Subject: Re: I fix a bug in kdb-v3.0-2.4.20, which cause the hardware
breakpoi nts fail to work. 


On Wed, 12 Feb 2003 17:01:17 +0800, 
"Zhang, Sonic" <sonic.zhang@intel.com> wrote:
>	I changed these code lines. I allow the kernel signal handle to
>change dr7 only when KDB is in the kernel and the variable kdb_on != 0.
That
>means KDB can't work together with any user space debugger. The user must
>make sure he exit any user space debugger before enable the KDB.

I tried that in early versions of kdb but the users complained too
much.  It meant that they could not do any debugging on kernels with
kdb compiled in.

Both i386 and ia64 can generate traps when a breakpoint is changed.
What about using that trap to detect a change of hardware breakpoint
and rejecting the user request if kdb is already using that breakpoint
register?  That would only prevent use of gdb if kdb was actually using
a hardware register, instead of banning all gdb use on a kdb enabled
kernel.

We should also change kdb to use breakpoint registers from the top down
instead of bottom up.  That would minimize conflicts with gdb.

From kaos@sgi.com Wed Feb 12 18:12:57 2003
Received: with ECARTIS (v1.0.0; list kdb); Wed, 12 Feb 2003 18:12:59 -0800 (PST)
Received: from rj.sgi.com (rj.sgi.com [192.82.208.96])
	by oss.sgi.com (8.12.5/8.12.5) with SMTP id h1D2Cu3v026080
	for <kdb@oss.sgi.com>; Wed, 12 Feb 2003 18:12:57 -0800
Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130])
	by rj.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with SMTP id h1D0LDG8031619
	for <kdb@oss.sgi.com>; Wed, 12 Feb 2003 16:21:14 -0800
Received: from kao2.melbourne.sgi.com (kao2.melbourne.sgi.com [134.14.55.180]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id NAA22644; Thu, 13 Feb 2003 13:19:44 +1100
Received: by kao2.melbourne.sgi.com (Postfix, from userid 16331)
	id C9D39300087; Thu, 13 Feb 2003 13:19:35 +1100 (EST)
Received: from kao2.melbourne.sgi.com (localhost [127.0.0.1])
	by kao2.melbourne.sgi.com (Postfix) with ESMTP
	id 8D1288F; Thu, 13 Feb 2003 13:19:35 +1100 (EST)
X-Mailer: exmh version 2.4 06/23/2000 with nmh-1.0.4
From: Keith Owens <kaos@sgi.com>
To: "Zhang, Sonic" <sonic.zhang@intel.com>
Cc: "KDB (E-mail)" <kdb@oss.sgi.com>
Subject: Re: I fix a bug in kdb-v3.0-2.4.20, which cause the hardware brea kpoi nts fail to work. 
In-reply-to: Your message of "Thu, 13 Feb 2003 09:55:45 +0800."
             <957BD1C2BF3CD411B6C500A0C944CA2602FB0306@pdsmsx32.pd.intel.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 13 Feb 2003 13:19:30 +1100
Message-ID: <30608.1045102770@kao2.melbourne.sgi.com>
X-archive-position: 248
X-ecartis-version: Ecartis v1.0.0
Sender: kdb-bounce@oss.sgi.com
Errors-to: kdb-bounce@oss.sgi.com
X-original-sender: kaos@sgi.com
Precedence: bulk
X-list: kdb

On Thu, 13 Feb 2003 09:55:45 +0800, 
"Zhang, Sonic" <sonic.zhang@intel.com> wrote:
>	I don't think the user can't do any debugging on kernels with KDB
>compiled in, because the user can disable KDB by echo "0" to
>"/proc/sys/kernel/kdb". The user can switch between KDB and GDB by a command
>line. The only problem is that KDB can't work with GDB simultaneously. Does
>any user really want to debug his code with KDB and GDB at one time?

You are forgetting that people want kdb always on to get debugging
information when the machine gets an error like BUG(), panic() or oops.
Manually turning kdb on/off is only useful when you can reproduce a
problem, it is no good for catching intermittent errors.


From sonic.zhang@intel.com Wed Feb 12 18:45:40 2003
Received: with ECARTIS (v1.0.0; list kdb); Wed, 12 Feb 2003 18:45:44 -0800 (PST)
Received: from hermes.jf.intel.com (fmr05.intel.com [134.134.136.6])
	by oss.sgi.com (8.12.5/8.12.5) with SMTP id h1D2jd3v026737
	for <kdb@oss.sgi.com>; Wed, 12 Feb 2003 18:45:39 -0800
Received: from petasus.jf.intel.com (petasus.jf.intel.com [10.7.209.6])
	by hermes.jf.intel.com (8.11.6/8.11.6/d: outer.mc,v 1.51 2002/09/23 20:43:23 dmccart Exp $) with ESMTP id h1D2prS29522
	for <kdb@oss.sgi.com>; Thu, 13 Feb 2003 02:51:53 GMT
Received: from pdsmsxvs01.pd.intel.com (pdsmsxvs01.pd.intel.com [172.16.12.122])
	by petasus.jf.intel.com (8.11.6/8.11.6/d: inner.mc,v 1.28 2003/01/13 19:44:39 dmccart Exp $) with SMTP id h1D2oCu01136
	for <kdb@oss.sgi.com>; Thu, 13 Feb 2003 02:50:12 GMT
Received: from pdsmsx17.pd.intel.com ([172.16.12.121])
 by pdsmsxvs01.pd.intel.com (NAVGW 2.5.2.11) with SMTP id M2003021310534629881
 ; Thu, 13 Feb 2003 10:53:46 +0800
Received: by pdsmsx17.pd.intel.com with Internet Mail Service (5.5.2653.19)
	id <1AW10AJ9>; Thu, 13 Feb 2003 10:52:37 +0800
Message-ID: <957BD1C2BF3CD411B6C500A0C944CA2602FB035D@pdsmsx32.pd.intel.com>
From: "Zhang, Sonic" <sonic.zhang@intel.com>
To: Keith Owens <kaos@sgi.com>
Cc: "KDB (E-mail)" <kdb@oss.sgi.com>
Subject: RE: I fix a bug in kdb-v3.0-2.4.20, which cause the hardware brea
	 kpoi nts fail to work. 
Date: Thu, 13 Feb 2003 10:51:32 +0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-archive-position: 249
X-ecartis-version: Ecartis v1.0.0
Sender: kdb-bounce@oss.sgi.com
Errors-to: kdb-bounce@oss.sgi.com
X-original-sender: sonic.zhang@intel.com
Precedence: bulk
X-list: kdb


Yes, your concern are correct. 

It seems the way to completely exclude this problem is to revise system call
ptrace to use the same break point allocation mechanism as KDB does. Or use
any common break point allocation routines, if they will be in the future
kernel.

As a temporary method, I suggest to add a switch "kdbhdr" to
"/proc/sys/kernel/". If echo 1 to it, KDB hardware debug feature is enabled,
while 0 means this feature is disabled. The default value should be set to
0.

Is it acceptable?

Thanks.

Sonic Zhang

-----Original Message-----
From: Keith Owens [mailto:kaos@sgi.com]
Sent: 2003?2?13? 10:20
To: Zhang, Sonic
Cc: KDB (E-mail)
Subject: Re: I fix a bug in kdb-v3.0-2.4.20, which cause the hardware brea
kpoi nts fail to work. 


On Thu, 13 Feb 2003 09:55:45 +0800, 
"Zhang, Sonic" <sonic.zhang@intel.com> wrote:
>	I don't think the user can't do any debugging on kernels with KDB
>compiled in, because the user can disable KDB by echo "0" to
>"/proc/sys/kernel/kdb". The user can switch between KDB and GDB by a
command
>line. The only problem is that KDB can't work with GDB simultaneously. Does
>any user really want to debug his code with KDB and GDB at one time?

You are forgetting that people want kdb always on to get debugging
information when the machine gets an error like BUG(), panic() or oops.
Manually turning kdb on/off is only useful when you can reproduce a
problem, it is no good for catching intermittent errors.

From sonic.zhang@intel.com Wed Feb 12 23:53:53 2003
Received: with ECARTIS (v1.0.0; list kdb); Wed, 12 Feb 2003 23:53:56 -0800 (PST)
Received: from hermes.jf.intel.com (fmr05.intel.com [134.134.136.6])
	by oss.sgi.com (8.12.5/8.12.5) with SMTP id h1D7rp3v008584
	for <kdb@oss.sgi.com>; Wed, 12 Feb 2003 23:53:52 -0800
Received: from talaria.jf.intel.com (talaria.jf.intel.com [10.7.209.7])
	by hermes.jf.intel.com (8.11.6/8.11.6/d: outer.mc,v 1.51 2002/09/23 20:43:23 dmccart Exp $) with ESMTP id h1D806B12633
	for <kdb@oss.sgi.com>; Thu, 13 Feb 2003 08:00:06 GMT
Received: from pdsmsxvs01.pd.intel.com (pdsmsxvs01.pd.intel.com [172.16.12.122])
	by talaria.jf.intel.com (8.11.6/8.11.6/d: inner.mc,v 1.28 2003/01/13 19:44:39 dmccart Exp $) with SMTP id h1D7evo07151
	for <kdb@oss.sgi.com>; Thu, 13 Feb 2003 07:40:57 GMT
Received: from pdsmsx17.pd.intel.com ([172.16.12.121])
 by pdsmsxvs01.pd.intel.com (NAVGW 2.5.2.11) with SMTP id M2003021316015714107
 ; Thu, 13 Feb 2003 16:01:57 +0800
Received: by pdsmsx17.pd.intel.com with Internet Mail Service (5.5.2653.19)
	id <1AW10NPM>; Thu, 13 Feb 2003 16:00:49 +0800
Message-ID: <957BD1C2BF3CD411B6C500A0C944CA2602FB049B@pdsmsx32.pd.intel.com>
From: "Zhang, Sonic" <sonic.zhang@intel.com>
To: "KeithOwens (E-mail)" <kaos@sgi.com>
Cc: "KDB (E-mail)" <kdb@oss.sgi.com>
Subject: About KDB global and local hardware breakpoint support in IA32.
Date: Thu, 13 Feb 2003 15:59:45 +0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_000_01C2D335.DFAB2D20"
X-archive-position: 250
X-ecartis-version: Ecartis v1.0.0
Sender: kdb-bounce@oss.sgi.com
Errors-to: kdb-bounce@oss.sgi.com
X-original-sender: sonic.zhang@intel.com
Precedence: bulk
X-list: kdb

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_000_01C2D335.DFAB2D20
Content-Type: text/plain;
	charset="gb2312"

Hi,

	I have read the code of KDB global and local hardware breakpoint
support. I find that although KDB command bpha and bph are provided for
global and local hardware breakpoints, their functions are not implemented
for IA32. 

	Current implementation in kdb-v3.0-2.4.20 sees a local breakpoint as
an equivalence of a global breakpoint. All CPUs share the same data
structure for hardware debug registers. And each CPU sets its debug register
for a hardware breakpoint, no matter whether it is a local one of the other
CPUs. So I tried to improve this feature to distinguish local and global
hardware breakpoints. Now, the user can create different local hardware
breakpoints for different CPUs. The global hardware breakpoints are still
dealt with in each CPUs.

	KDB_MAXHARDBPT <= Max hardware breakpoints <= KDB_MAXHARDBPT *
NR_CPUS

/*
 * Table describing processor architecture hardware
 * breakpoint registers.
 */
- kdbhard_bp_t	kdb_hardbreaks[KDB_MAXHARDBPT];
+ kdbhard_bp_t	kdb_hardbreaks[KDB_MAXHARDBPT][NR_CPUS];


	Besides, I think the name of routines "kdb_bp_install_global()",
"kdb_bp_install_local()", "kdb_bp_remove_global()" and
"kdb_bp_remove_local()" are not coincide with their functions in "kdb()".
The "global" routines actually only install or remove debug instruction,
such as "int3", while the "local" ones only deal with CPU specific debug
registers. So, I changed string "local" into "dbreg" and string "global"
into "dbinst". I also changed a little of their logic.

	Do you have any ideas about my consideration? I have tested my patch
on a server with 2 PIII CPUs basically.

	Please refer to the attachments. It works with kernel 2.4.20 and
kdb-v3.0-2.4.20.

	Thank you.


*************************************
Sonic Zhang
  
Software Engineer
Intel China Software Lab

Tel: 021-52574545-1667 
iNet: 8-752-1667 
*************************************
 


------_=_NextPart_000_01C2D335.DFAB2D20
Content-Type: application/octet-stream;
	name="kdb-smphdr-v3.0-2.4.20-i386-1.patch"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="kdb-smphdr-v3.0-2.4.20-i386-1.patch"

--- linux-kdb-tmp/include/asm-i386/kdbprivate.h	Fri Feb 14 11:12:50 =
2003=0A=
+++ linux-kdb/include/asm-i386/kdbprivate.h	Fri Feb 14 11:13:39 2003=0A=
@@ -73,7 +73,7 @@=0A=
 	unsigned int	bph_length:2;	/* 0=3D1, 1=3D2, 2=3DBAD, 3=3D4 (bytes) =
*/=0A=
 } kdbhard_bp_t;=0A=
 =0A=
-extern kdbhard_bp_t	kdb_hardbreaks[/* KDB_MAXHARDBPT */];=0A=
+extern kdbhard_bp_t	kdb_hardbreaks[/* KDB_MAXHARDBPT */][/* NR_CPUS =
*/];=0A=
 =0A=
 #define IA32_BREAKPOINT_INSTRUCTION	0xcc=0A=
 =0A=
=0A=
--- linux-kdb-tmp/arch/i386/kdb/kdba_bp.c	Fri Feb 14 11:14:18 2003=0A=
+++ linux-kdb/arch/i386/kdb/kdba_bp.c	Fri Feb 14 11:27:51 2003=0A=
@@ -49,7 +49,7 @@=0A=
  * breakpoint registers.=0A=
  */=0A=
=0A=
-kdbhard_bp_t	kdb_hardbreaks[KDB_MAXHARDBPT];=0A=
+kdbhard_bp_t	kdb_hardbreaks[KDB_MAXHARDBPT][NR_CPUS];=0A=
=0A=
 /*=0A=
  * kdba_db_trap=0A=
@@ -583,7 +583,7 @@=0A=
  *	Associate a hardware register with a breakpoint.=0A=
  *=0A=
  * Parameters:=0A=
- *	None.=0A=
+ *	cpu	the cpuid, -1 means global.=0A=
  * Outputs:=0A=
  *	None.=0A=
  * Returns:=0A=
@@ -595,14 +595,39 @@=0A=
  */=0A=
=0A=
 kdbhard_bp_t *=0A=
-kdba_allocbp(kdbhard_bp_t *bph, int *diagp)=0A=
+kdba_allocbp(kdbhard_bp_t *bph, int cpu, int *diagp)=0A=
 {=0A=
-	int i;=0A=
-	kdbhard_bp_t *newbph;=0A=
+	int i,j;=0A=
+	kdbhard_bp_t *newbph=3DNULL;=0A=
=0A=
-	for(i=3D0,newbph=3Dkdb_hardbreaks; i < KDB_MAXHARDBPT; i++, newbph++) =
{=0A=
-		if (newbph->bph_free) {=0A=
-			break;=0A=
+	*diagp =3D 0;=0A=
+=0A=
+	if(cpu>=3DNR_CPUS)=0A=
+		return NULL;=0A=
+=0A=
+	if(cpu>=3D0) {=0A=
+		for(i=3D0; i < KDB_MAXHARDBPT; i++) {=0A=
+			if (kdb_hardbreaks[i][cpu].bph_free) {=0A=
+				newbph=3D&(kdb_hardbreaks[i][cpu]);=0A=
+				/* Mark entry allocated.*/=0A=
+				newbph->bph_free =3D 0;=0A=
+				break;=0A=
+			}=0A=
+		}=0A=
+	}=0A=
+	else {=0A=
+		for(i=3D0; i < KDB_MAXHARDBPT; i++) {=0A=
+			for(j=3D0; j < NR_CPUS; j++) {=0A=
+				if(!kdb_hardbreaks[i][j].bph_free)=0A=
+					break;=0A=
+			}=0A=
+			if(j =3D=3D NR_CPUS) {=0A=
+				newbph=3D&(kdb_hardbreaks[i][smp_processor_id()]);=0A=
+				/* Mark entries allocated.*/=0A=
+				for(j=3D0; j < NR_CPUS; j++)=0A=
+					kdb_hardbreaks[i][j].bph_free =3D 0;=0A=
+				break;=0A=
+			}=0A=
 		}=0A=
 	}=0A=
=0A=
@@ -611,8 +636,6 @@=0A=
 		return NULL;=0A=
 	}=0A=
=0A=
-	*diagp =3D 0;=0A=
-=0A=
 	/*=0A=
 	 * Copy data from template.  Can't just copy the entire template=0A=
 	 * here because the register number in kdb_hardbreaks must be=0A=
@@ -623,11 +646,6 @@=0A=
 	newbph->bph_mode =3D bph->bph_mode;=0A=
 	newbph->bph_length =3D bph->bph_length;=0A=
=0A=
-	/*=0A=
-	 * Mark entry allocated.=0A=
-	 */=0A=
-	newbph->bph_free =3D 0;=0A=
-=0A=
 	return newbph;=0A=
 }=0A=
=0A=
@@ -637,7 +655,7 @@=0A=
  *	Deallocate a hardware breakpoint=0A=
  *=0A=
  * Parameters:=0A=
- *	None.=0A=
+ *	cpu	the cpuid, -1 means global.=0A=
  * Outputs:=0A=
  *	None.=0A=
  * Returns:=0A=
@@ -648,9 +666,15 @@=0A=
  */=0A=
=0A=
 void=0A=
-kdba_freebp(kdbhard_bp_t *bph)=0A=
+kdba_freebp(kdbhard_bp_t *bph, int cpu)=0A=
 {=0A=
-	bph->bph_free =3D 1;=0A=
+	int i;=0A=
+	if(cpu>=3D0)=0A=
+		bph->bph_free =3D 1;=0A=
+	else {=0A=
+		for(i=3D0; i<NR_CPUS; i++)=0A=
+			kdb_hardbreaks[bph->bph_data][i].bph_free =3D 1;=0A=
+	}=0A=
 }=0A=
=0A=
 /*=0A=
@@ -677,8 +701,7 @@=0A=
 void=0A=
 kdba_initbp(void)=0A=
 {=0A=
-	int i;=0A=
-	kdbhard_bp_t *bph;=0A=
+	int i,j;=0A=
=0A=
 	/*=0A=
 	 * Clear the hardware breakpoint table=0A=
@@ -686,10 +709,11 @@=0A=
=0A=
 	memset(kdb_hardbreaks, '\0', sizeof(kdb_hardbreaks));=0A=
=0A=
-	for(i=3D0,bph=3Dkdb_hardbreaks; i<KDB_MAXHARDBPT; i++, bph++) {=0A=
-		bph->bph_reg =3D i;=0A=
-		bph->bph_free =3D 1;=0A=
-	}=0A=
+	for(i=3D0; i<KDB_MAXHARDBPT; i++)=0A=
+		for(j=3D0; j<NR_CPUS ; j++) {=0A=
+		kdb_hardbreaks[i][j].bph_reg =3D i%KDB_MAXHARDBPT;=0A=
+		kdb_hardbreaks[i][j].bph_free =3D 1;=0A=
+		}=0A=
 }=0A=
=0A=
 /*=0A=
@@ -731,15 +755,15 @@=0A=
 	}=0A=
 	if (!KDB_STATE(SSBPT))=0A=
 		bp->bp_delay =3D 0;=0A=
-	if (!bp->bp_installed) {=0A=
-		if (bp->bp_hardtype) {=0A=
-			kdba_installdbreg(bp);=0A=
-			bp->bp_installed =3D 1;=0A=
-			if (KDB_DEBUG(BP)) {=0A=
-				kdb_printf("kdba_installbp hardware reg %ld at " kdb_bfd_vma_fmt =
"\n",=0A=
-					   bp->bp_hard->bph_reg, bp->bp_addr);=0A=
-			}=0A=
-		} else if (bp->bp_delay) {=0A=
+	if (bp->bp_hardtype) {=0A=
+		kdba_installdbreg(bp);=0A=
+		bp->bp_installed =3D 1;=0A=
+		if (KDB_DEBUG(BP)) {=0A=
+			kdb_printf("kdba_installbp hardware reg %ld at " kdb_bfd_vma_fmt =
"\n",=0A=
+				   bp->bp_hard->bph_reg, bp->bp_addr);=0A=
+		}=0A=
+	} else if (!bp->bp_installed) {=0A=
+		if (bp->bp_delay) {=0A=
 			if (KDB_DEBUG(BP))=0A=
 				kdb_printf("kdba_installbp delayed bp\n");=0A=
 			kdba_handle_bp(regs, bp);=0A=
@@ -784,20 +808,19 @@=0A=
 	if (KDB_DEBUG(BP)) {=0A=
 		kdb_printf("kdba_removebp bp_installed %d\n", bp->bp_installed);=0A=
 	}=0A=
-	if (bp->bp_installed) {=0A=
-		if (bp->bp_hardtype) {=0A=
-			if (KDB_DEBUG(BP)) {=0A=
-				kdb_printf("kdb: removing hardware reg %ld at " kdb_bfd_vma_fmt =
"\n",=0A=
-					   bp->bp_hard->bph_reg, bp->bp_addr);=0A=
-			}=0A=
-			kdba_removedbreg(bp);=0A=
-		} else {=0A=
-			if (KDB_DEBUG(BP))=0A=
-				kdb_printf("kdb: restoring instruction 0x%x at " kdb_bfd_vma_fmt =
"\n",=0A=
-					   bp->bp_inst, bp->bp_addr);=0A=
-			if (kdb_putword(bp->bp_addr, bp->bp_inst, 1))=0A=
-				return(1);=0A=
-		}=0A=
+	if (bp->bp_hardtype) {=0A=
+		if (KDB_DEBUG(BP)) {=0A=
+			kdb_printf("kdb: removing hardware reg %ld at " kdb_bfd_vma_fmt =
"\n",=0A=
+				   bp->bp_hard->bph_reg, bp->bp_addr);=0A=
+		}=0A=
+		kdba_removedbreg(bp);=0A=
+		bp->bp_installed =3D 0;=0A=
+	} else if (bp->bp_installed) {=0A=
+		if (KDB_DEBUG(BP))=0A=
+			kdb_printf("kdb: restoring instruction 0x%x at " kdb_bfd_vma_fmt =
"\n",=0A=
+				   bp->bp_inst, bp->bp_addr);=0A=
+		if (kdb_putword(bp->bp_addr, bp->bp_inst, 1))=0A=
+			return(1);=0A=
 		bp->bp_installed =3D 0;=0A=
 	}=0A=
 	return(0);=0A=

------_=_NextPart_000_01C2D335.DFAB2D20
Content-Type: application/octet-stream;
	name="kdb-smphdr-v3.0-2.4.20-common-1.patch"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="kdb-smphdr-v3.0-2.4.20-common-1.patch"

--- linux-kdb-tmp/kdb/kdbmain.c	Fri Feb 14 10:57:05 2003=0A=
+++ linux-kdb/kdb/kdbmain.c	Fri Feb 14 10:59:33 2003=0A=
@@ -1552,7 +1552,7 @@=0A=
 		local_bh_disable();=0A=
 	}=0A=
 	if (!KDB_STATE(KDB_CONTROL)) {=0A=
-		kdb_bp_remove_local();=0A=
+		kdb_bp_remove_dbreg();=0A=
 		kdba_disable_lbr();=0A=
 		KDB_STATE_SET(KDB_CONTROL);=0A=
 	}=0A=
@@ -1600,7 +1600,7 @@=0A=
 		 * Remove the global breakpoints.  This is only done=0A=
 		 * once from the initial processor on initial entry.=0A=
 		 */=0A=
-		kdb_bp_remove_global();=0A=
+		kdb_bp_remove_dbinst();=0A=
 =0A=
 		/*=0A=
 		 * If SMP, stop other processors.  The other processors=0A=
@@ -1625,7 +1625,7 @@=0A=
 	}=0A=
 =0A=
 	if (KDB_STATE(GO1)) {=0A=
-		kdb_bp_remove_global();		/* They were set for single-step purposes =
*/=0A=
+		kdb_bp_remove_dbinst();		/* They were set for single-step purposes =
*/=0A=
 		KDB_STATE_CLEAR(GO1);=0A=
 		reason =3D KDB_REASON_SILENT;	/* Now silently go */=0A=
 	}=0A=
@@ -1650,7 +1650,7 @@=0A=
 	    !KDB_STATE(RECURSE)) {=0A=
 		KDB_DEBUG_STATE("kdb 12", result);=0A=
 		kdba_enable_lbr();=0A=
-		kdb_bp_install_local(regs);=0A=
+		kdb_bp_install_dbreg(regs);=0A=
 		local_bh_enable();=0A=
 		KDB_STATE_CLEAR(KDB_CONTROL);=0A=
 	}=0A=
@@ -1666,7 +1666,7 @@=0A=
 		 * once from the initial processor on go.=0A=
 		 */=0A=
 		KDB_DEBUG_STATE("kdb 14", reason);=0A=
-		kdb_bp_install_global(regs);=0A=
+		kdb_bp_install_dbinst(regs);=0A=
 		if (!KDB_STATE(GO1)) {=0A=
 			/*=0A=
 			 * Release all other cpus which will see KDB_STATE(LEAVING) is =
set.=0A=
=0A=
=0A=
=0A=
--- linux-kdb-tmp/include/linux/kdbprivate.h	Fri Feb 14 11:11:28 =
2003=0A=
+++ linux-kdb/include/linux/kdbprivate.h	Fri Feb 14 11:26:22 2003=0A=
@@ -122,8 +122,8 @@=0A=
 extern void 		kdba_initbp(void);=0A=
 extern void		kdba_printbp(kdb_bp_t *);=0A=
 extern void		kdba_printbpreg(kdbhard_bp_t *);=0A=
-extern kdbhard_bp_t	*kdba_allocbp(kdbhard_bp_t *, int *);=0A=
-extern void		kdba_freebp(kdbhard_bp_t *);=0A=
+extern kdbhard_bp_t	*kdba_allocbp(kdbhard_bp_t *, int , int *);=0A=
+extern void		kdba_freebp(kdbhard_bp_t *, int);=0A=
 extern int		kdba_parsebp(int, const char**, int *, kdb_bp_t*);=0A=
 extern char 		*kdba_bptype(kdbhard_bp_t *);=0A=
 extern void		kdba_setsinglestep(struct pt_regs *);=0A=
@@ -249,10 +249,10 @@=0A=
 	 * Breakpoint handling - External interfaces=0A=
 	 */=0A=
 extern void kdb_initbptab(void);=0A=
-extern void kdb_bp_install_global(struct pt_regs *);=0A=
-extern void kdb_bp_install_local(struct pt_regs *);=0A=
-extern void kdb_bp_remove_global(void);=0A=
-extern void kdb_bp_remove_local(void);=0A=
+extern void kdb_bp_install_dbinst(struct pt_regs *);=0A=
+extern void kdb_bp_install_dbreg(struct pt_regs *);=0A=
+extern void kdb_bp_remove_dbinst(void);=0A=
+extern void kdb_bp_remove_dbreg(void);=0A=
=0A=
 	/*=0A=
 	 * Breakpoint handling - Internal to kdb_bp.c/kdba_bp.c=0A=
=0A=
=0A=
--- linux-kdb-tmp/kdb/kdb_bp.c	Fri Feb 14 11:00:10 2003=0A=
+++ linux-kdb/kdb/kdb_bp.c	Fri Feb 14 11:10:33 2003=0A=
@@ -47,7 +47,7 @@=0A=
 kdb_bp_t	kdb_breakpoints[KDB_MAXBPT];=0A=
=0A=
 /*=0A=
- * kdb_bp_install_global=0A=
+ * kdb_bp_install_dbinst=0A=
  *=0A=
  *	Install global kdb_breakpoints prior to returning from the=0A=
  *	kernel debugger.  This allows the kdb_breakpoints to be set=0A=
@@ -68,26 +68,26 @@=0A=
  */=0A=
=0A=
 void=0A=
-kdb_bp_install_global(struct pt_regs *regs)=0A=
+kdb_bp_install_dbinst(struct pt_regs *regs)=0A=
 {=0A=
 	int i;=0A=
=0A=
 	for(i=3D0; i<KDB_MAXBPT; i++) {=0A=
 		if (KDB_DEBUG(BP)) {=0A=
-			kdb_printf("kdb_bp_install_global bp %d bp_enabled %d bp_global =
%d\n",=0A=
+			kdb_printf("kdb_bp_install_dbinst bp %d bp_enabled %d bp_global =
%d\n",=0A=
 				i, kdb_breakpoints[i].bp_enabled, =
kdb_breakpoints[i].bp_global);=0A=
 		}=0A=
 		if (kdb_breakpoints[i].bp_enabled=0A=
-		 && kdb_breakpoints[i].bp_global) {=0A=
+		 && !kdb_breakpoints[i].bp_forcehw) {=0A=
 			kdba_installbp(regs, &kdb_breakpoints[i]);=0A=
 		}=0A=
 	}=0A=
 }=0A=
=0A=
 /*=0A=
- * kdb_bp_install_local=0A=
+ * kdb_bp_install_dbreg=0A=
  *=0A=
- *	Install local kdb_breakpoints prior to returning from the=0A=
+ *	Install debug register kdb_breakpoints prior to returning from =
the=0A=
  *	kernel debugger.  This allows the kdb_breakpoints to be set=0A=
  *	upon functions that are used internally by kdb, such as=0A=
  *	printk().=0A=
@@ -106,28 +106,29 @@=0A=
  */=0A=
=0A=
 void=0A=
-kdb_bp_install_local(struct pt_regs *regs)=0A=
+kdb_bp_install_dbreg(struct pt_regs *regs)=0A=
 {=0A=
 	int i;=0A=
=0A=
 	for(i=3D0; i<KDB_MAXBPT; i++) {=0A=
 		if (KDB_DEBUG(BP)) {=0A=
-			kdb_printf("kdb_bp_install_local bp %d bp_enabled %d bp_global %d =
cpu %d bp_cpu %d\n",=0A=
+			kdb_printf("kdb_bp_install_dbreg bp %d bp_enabled %d bp_global %d =
cpu %d bp_cpu %d\n",=0A=
 				i, kdb_breakpoints[i].bp_enabled, kdb_breakpoints[i].bp_global,=0A=
 				smp_processor_id(), kdb_breakpoints[i].bp_cpu);=0A=
 		}=0A=
 		if (kdb_breakpoints[i].bp_enabled=0A=
-		 && kdb_breakpoints[i].bp_cpu =3D=3D smp_processor_id()=0A=
-		 && !kdb_breakpoints[i].bp_global){=0A=
+		 && kdb_breakpoints[i].bp_hardtype=0A=
+		 && (kdb_breakpoints[i].bp_cpu =3D=3D smp_processor_id()=0A=
+		 || kdb_breakpoints[i].bp_global)){=0A=
 			kdba_installbp(regs, &kdb_breakpoints[i]);=0A=
 		}=0A=
 	}=0A=
 }=0A=
=0A=
 /*=0A=
- * kdb_bp_remove_global=0A=
+ * kdb_bp_remove_dbinst=0A=
  *=0A=
- * 	Remove global kdb_breakpoints upon entry to the kernel =
debugger.=0A=
+ * 	Remove debug instruction upon entry to the kernel debugger.=0A=
  *=0A=
  * Parameters:=0A=
  *	None.=0A=
@@ -141,17 +142,17 @@=0A=
  */=0A=
=0A=
 void=0A=
-kdb_bp_remove_global(void)=0A=
+kdb_bp_remove_dbinst(void)=0A=
 {=0A=
 	int i;=0A=
=0A=
 	for(i=3DKDB_MAXBPT-1; i>=3D0; i--) {=0A=
 		if (KDB_DEBUG(BP)) {=0A=
-			kdb_printf("kdb_bp_remove_global bp %d bp_enabled %d bp_global =
%d\n",=0A=
+			kdb_printf("kdb_bp_remove_dbinst bp %d bp_enabled %d bp_global =
%d\n",=0A=
 				i, kdb_breakpoints[i].bp_enabled, =
kdb_breakpoints[i].bp_global);=0A=
 		}=0A=
 		if (kdb_breakpoints[i].bp_enabled=0A=
-		 && kdb_breakpoints[i].bp_global) {=0A=
+		 && !kdb_breakpoints[i].bp_forcehw) {=0A=
 			kdba_removebp(&kdb_breakpoints[i]);=0A=
 		}=0A=
 	}=0A=
@@ -159,9 +160,9 @@=0A=
=0A=
=0A=
 /*=0A=
- * kdb_bp_remove_local=0A=
+ * kdb_bp_remove_dbreg=0A=
  *=0A=
- * 	Remove local kdb_breakpoints upon entry to the kernel debugger.=0A=
+ * 	Remove debug resiter upon entry to the kernel debugger.=0A=
  *=0A=
  * Parameters:=0A=
  *	None.=0A=
@@ -175,19 +176,20 @@=0A=
  */=0A=
=0A=
 void=0A=
-kdb_bp_remove_local(void)=0A=
+kdb_bp_remove_dbreg(void)=0A=
 {=0A=
 	int i;=0A=
=0A=
 	for(i=3DKDB_MAXBPT-1; i>=3D0; i--) {=0A=
 		if (KDB_DEBUG(BP)) {=0A=
-			kdb_printf("kdb_bp_remove_local bp %d bp_enabled %d bp_global %d =
cpu %d bp_cpu %d\n",=0A=
+			kdb_printf("kdb_bp_remove_dbreg bp %d bp_enabled %d bp_global %d =
cpu %d bp_cpu %d\n",=0A=
 				i, kdb_breakpoints[i].bp_enabled, kdb_breakpoints[i].bp_global,=0A=
 				smp_processor_id(), kdb_breakpoints[i].bp_cpu);=0A=
 		}=0A=
 		if (kdb_breakpoints[i].bp_enabled=0A=
-		 && kdb_breakpoints[i].bp_cpu =3D=3D smp_processor_id()=0A=
-		 && !kdb_breakpoints[i].bp_global){=0A=
+		 && kdb_breakpoints[i].bp_hardtype=0A=
+		 && (kdb_breakpoints[i].bp_cpu =3D=3D smp_processor_id()=0A=
+		 || kdb_breakpoints[i].bp_global)){=0A=
 			kdba_removebp(&kdb_breakpoints[i]);=0A=
 		}=0A=
 	}=0A=
@@ -353,7 +355,10 @@=0A=
 	 * attempt to allocate a hardware register for it.=0A=
 	 */=0A=
 	if (!bp->bp_template.bph_free) {=0A=
-		bp->bp_hard =3D kdba_allocbp(&bp->bp_template, &diag);=0A=
+		if(bp->bp_global)=0A=
+			bp->bp_hard =3D kdba_allocbp(&bp->bp_template, -1, &diag);=0A=
+		else=0A=
+			bp->bp_hard =3D kdba_allocbp(&bp->bp_template, bp->bp_cpu, =
&diag);=0A=
 		if (diag) {=0A=
 			bp->bp_enabled =3D 0;=0A=
 			return diag;=0A=
@@ -455,7 +460,10 @@=0A=
 		switch (cmd) {=0A=
 		case KDBCMD_BC:=0A=
 			if (bp->bp_hardtype) {=0A=
-				kdba_freebp(bp->bp_hard);=0A=
+				if(bp->bp_global)=0A=
+					kdba_freebp(bp->bp_hard, -1);=0A=
+				else=0A=
+					kdba_freebp(bp->bp_hard, bp->bp_cpu);=0A=
 				bp->bp_hard =3D 0;=0A=
 				bp->bp_hardtype =3D 0;=0A=
 			}=0A=
@@ -477,7 +485,10 @@=0A=
 			 */=0A=
 			if (!bp->bp_template.bph_free=0A=
 			 && !bp->bp_hardtype) {=0A=
-				bp->bp_hard =3D kdba_allocbp(&bp->bp_template, &diag);=0A=
+				if(bp->bp_global)=0A=
+					bp->bp_hard =3D kdba_allocbp(&bp->bp_template, -1, &diag);=0A=
+				else=0A=
+					bp->bp_hard =3D kdba_allocbp(&bp->bp_template, bp->bp_cpu, =
&diag);=0A=
 				if (diag) {=0A=
 					bp->bp_enabled =3D 0;=0A=
 					return diag;=0A=
@@ -503,7 +514,10 @@=0A=
 			 * to it.=0A=
 			 */=0A=
 			if (bp->bp_hardtype) {=0A=
-				kdba_freebp(bp->bp_hard);=0A=
+				if(bp->bp_global)=0A=
+					kdba_freebp(bp->bp_hard, -1);=0A=
+				else=0A=
+					kdba_freebp(bp->bp_hard, bp->bp_cpu);=0A=
 				bp->bp_hard =3D 0;=0A=
 				bp->bp_hardtype =3D 0;=0A=
 			}=0A=
=0A=

------_=_NextPart_000_01C2D335.DFAB2D20--

From kaos@sgi.com Thu Feb 13 01:53:28 2003
Received: with ECARTIS (v1.0.0; list kdb); Thu, 13 Feb 2003 01:53:31 -0800 (PST)
Received: from mail.ocs.com.au (mail.ocs.com.au [203.34.97.2])
	by oss.sgi.com (8.12.5/8.12.5) with SMTP id h1D9rP3v016655
	for <kdb@oss.sgi.com>; Thu, 13 Feb 2003 01:53:26 -0800
Received: (qmail 27360 invoked from network); 13 Feb 2003 10:01:39 -0000
Received: from ocs3.intra.ocs.com.au (192.168.255.3)
  by mail.ocs.com.au with SMTP; 13 Feb 2003 10:01:39 -0000
Received: by ocs3.intra.ocs.com.au (Postfix, from userid 16331)
	id E3DA5300087; Thu, 13 Feb 2003 21:01:36 +1100 (EST)
Received: from ocs3.intra.ocs.com.au (localhost [127.0.0.1])
	by ocs3.intra.ocs.com.au (Postfix) with ESMTP
	id CB5DC8F; Thu, 13 Feb 2003 21:01:36 +1100 (EST)
X-Mailer: exmh version 2.4 06/23/2000 with nmh-1.0.4
From: Keith Owens <kaos@sgi.com>
To: "Zhang, Sonic" <sonic.zhang@intel.com>
Cc: "KDB (E-mail)" <kdb@oss.sgi.com>
Subject: Re: About KDB global and local hardware breakpoint support in IA32. 
In-reply-to: Your message of "Thu, 13 Feb 2003 15:59:45 +0800."
             <957BD1C2BF3CD411B6C500A0C944CA2602FB049B@pdsmsx32.pd.intel.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 13 Feb 2003 21:01:31 +1100
Message-ID: <3596.1045130491@ocs3.intra.ocs.com.au>
X-archive-position: 251
X-ecartis-version: Ecartis v1.0.0
Sender: kdb-bounce@oss.sgi.com
Errors-to: kdb-bounce@oss.sgi.com
X-original-sender: kaos@sgi.com
Precedence: bulk
X-list: kdb

On Thu, 13 Feb 2003 15:59:45 +0800, 
"Zhang, Sonic" <sonic.zhang@intel.com> wrote:
>	Current implementation in kdb-v3.0-2.4.20 sees a local breakpoint as
>an equivalence of a global breakpoint. All CPUs share the same data
>structure for hardware debug registers. And each CPU sets its debug register
>for a hardware breakpoint, no matter whether it is a local one of the other
>CPUs.

Where do you get that from?  kdb_bp_install_local() is

void
kdb_bp_install_local(struct pt_regs *regs)
{
	int i;

	for(i=0; i<KDB_MAXBPT; i++) {
		if (KDB_DEBUG(BP)) {
			kdb_printf("kdb_bp_install_local bp %d bp_enabled %d bp_global %d cpu %d bp_cpu %d\n",
				i, kdb_breakpoints[i].bp_enabled, kdb_breakpoints[i].bp_global,
				smp_processor_id(), kdb_breakpoints[i].bp_cpu);
		}
		if (kdb_breakpoints[i].bp_enabled
		 && kdb_breakpoints[i].bp_cpu == smp_processor_id()
		 && !kdb_breakpoints[i].bp_global){
			kdba_installbp(regs, &kdb_breakpoints[i]);
		}
	}
}

That function is called for each cpu as it leaves kdb.  It only
installs local breakpoints for the current cpu.

kdb_bp() has
	if (hardware && !global) {
		bp->bp_global = 0;
		bp->bp_cpu = smp_processor_id();
	}
marking local breakpoints by their cpu number.


From Hui_Ning@3com.com Fri Feb 14 09:57:16 2003
Received: with ECARTIS (v1.0.0; list kdb); Fri, 14 Feb 2003 09:57:19 -0800 (PST)
Received: from topaz.3com.com (topaz.3com.com [192.156.136.158])
	by oss.sgi.com (8.12.5/8.12.5) with SMTP id h1EHvF3v028514
	for <kdb@oss.sgi.com>; Fri, 14 Feb 2003 09:57:15 -0800
Received: from opal.3com.com (opal.3com.com [139.87.50.117])
	by topaz.3com.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h1EI57U08334
	(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified NO)
	for <kdb@oss.sgi.com>; Fri, 14 Feb 2003 10:05:08 -0800 (PST)
Received: from hqsmtp01.3com.com (hqsmtp01.ops.3com.com [139.87.49.79])
	by opal.3com.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id h1EI5Z819776
	for <kdb@oss.sgi.com>; Fri, 14 Feb 2003 10:05:35 -0800 (PST)
Subject: public key for patches
To: kdb@oss.sgi.com
From: Hui_Ning@3com.com
Date: Fri, 14 Feb 2003 12:07:33 -0600
Message-ID: <OF8A4CA952.46BE6B6D-ON86256CCD.00636958@3com.com>
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
X-archive-position: 252
X-ecartis-version: Ecartis v1.0.0
Sender: kdb-bounce@oss.sgi.com
Errors-to: kdb-bounce@oss.sgi.com
X-original-sender: Hui_Ning@3com.com
Precedence: bulk
X-list: kdb

hello,


somehow I can't receive the public key. Is there any way I can get
decrypted patches?

thanks

hui


From Thomas.Duffy.99@alumni.brown.edu Fri Feb 14 10:50:44 2003
Received: with ECARTIS (v1.0.0; list kdb); Fri, 14 Feb 2003 10:50:52 -0800 (PST)
Received: from kathmandu.sun.com (kathmandu.sun.com [192.18.98.36])
	by oss.sgi.com (8.12.5/8.12.5) with SMTP id h1EIoh3v032442
	for <kdb@oss.sgi.com>; Fri, 14 Feb 2003 10:50:44 -0800
Received: from engmail2sun.Eng.Sun.COM ([129.144.134.19])
	by kathmandu.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA19441
	for <kdb@oss.sgi.com>; Fri, 14 Feb 2003 11:59:05 -0700 (MST)
Received: from phys-ha1sun-1 (phys-ha1sun-1.Eng.Sun.COM [129.144.135.11])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h1EIx4VL015136
	for <kdb@oss.sgi.com>; Fri, 14 Feb 2003 10:59:05 -0800 (PST)
Received: from biznatch (biznatch.Eng.Sun.COM [129.144.24.170])
 by ha1sun-mail1.eng.sun.com (iPlanet Messaging Server 5.2 (built Feb 21 2002))
 with ESMTP id <0HAB0075GBEGFU@ha1sun-mail1.eng.sun.com> for kdb@oss.sgi.com;
 Fri, 14 Feb 2003 10:59:04 -0800 (PST)
Date: Fri, 14 Feb 2003 10:59:31 -0800
From: Thomas Duffy <Thomas.Duffy.99@alumni.brown.edu>
Subject: Re: public key for patches
In-reply-to: <OF8A4CA952.46BE6B6D-ON86256CCD.00636958@3com.com>
To: kdb@oss.sgi.com
Message-id: <1045249170.13711.12.camel@biznatch>
Organization: 
MIME-version: 1.0
X-Mailer: Ximian Evolution 1.2.2
Content-type: text/plain
Content-transfer-encoding: 7BIT
References: <OF8A4CA952.46BE6B6D-ON86256CCD.00636958@3com.com>
X-archive-position: 253
X-ecartis-version: Ecartis v1.0.0
Sender: kdb-bounce@oss.sgi.com
Errors-to: kdb-bounce@oss.sgi.com
X-original-sender: Thomas.Duffy.99@alumni.brown.edu
Precedence: bulk
X-list: kdb

On Fri, 2003-02-14 at 10:07, Hui_Ning@3com.com wrote:
> hello,
> 
> 
> somehow I can't receive the public key. Is there any way I can get
> decrypted patches?

the patches are not encrypted.  they are bzip2'ed.  keith signs the
patches and puts the signature in a different file named <patchname>.asc

-tduffy

-- 
Thomas Duffy <Thomas.Duffy.99@alumni.brown.edu>


From kaos@sgi.com Fri Feb 14 13:45:37 2003
Received: with ECARTIS (v1.0.0; list kdb); Fri, 14 Feb 2003 13:45:40 -0800 (PST)
Received: from mail.ocs.com.au (mail.ocs.com.au [203.34.97.2])
	by oss.sgi.com (8.12.5/8.12.5) with SMTP id h1ELjY3v023075
	for <kdb@oss.sgi.com>; Fri, 14 Feb 2003 13:45:36 -0800
Received: (qmail 7472 invoked from network); 14 Feb 2003 21:53:53 -0000
Received: from ocs3.intra.ocs.com.au (192.168.255.3)
  by mail.ocs.com.au with SMTP; 14 Feb 2003 21:53:53 -0000
Received: by ocs3.intra.ocs.com.au (Postfix, from userid 16331)
	id 0FB90300087; Sat, 15 Feb 2003 08:53:47 +1100 (EST)
Received: from ocs3.intra.ocs.com.au (localhost [127.0.0.1])
	by ocs3.intra.ocs.com.au (Postfix) with ESMTP
	id 4D3EA8F; Sat, 15 Feb 2003 08:53:47 +1100 (EST)
X-Mailer: exmh version 2.4 06/23/2000 with nmh-1.0.4
From: Keith Owens <kaos@sgi.com>
To: Hui_Ning@3com.com
Cc: kdb@oss.sgi.com
Subject: Re: public key for patches 
In-reply-to: Your message of "Fri, 14 Feb 2003 12:07:33 MDT."
             <OF8A4CA952.46BE6B6D-ON86256CCD.00636958@3com.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 15 Feb 2003 08:53:40 +1100
Message-ID: <22779.1045259620@ocs3.intra.ocs.com.au>
X-archive-position: 254
X-ecartis-version: Ecartis v1.0.0
Sender: kdb-bounce@oss.sgi.com
Errors-to: kdb-bounce@oss.sgi.com
X-original-sender: kaos@sgi.com
Precedence: bulk
X-list: kdb

On Fri, 14 Feb 2003 12:07:33 -0600, 
Hui_Ning@3com.com wrote:
>somehow I can't receive the public key. Is there any way I can get
>decrypted patches?

The patches are not encrypted, just compressed with bzip2.  The .asc
files are detached signatures, using my private key.  You can verify
the signatures with my public key which can be obtained from one of
several PGP/GPG public keyserevrs.  For example,
http://www.keyserver.net/en/ and search for 0x27B464EA.


From sonic.zhang@intel.com Sun Feb 16 19:07:09 2003
Received: with ECARTIS (v1.0.0; list kdb); Sun, 16 Feb 2003 19:07:13 -0800 (PST)
Received: from hermes.jf.intel.com (fmr05.intel.com [134.134.136.6])
	by oss.sgi.com (8.12.5/8.12.5) with SMTP id h1H3783v010011
	for <kdb@oss.sgi.com>; Sun, 16 Feb 2003 19:07:09 -0800
Received: from talaria.jf.intel.com (talaria.jf.intel.com [10.7.209.7])
	by hermes.jf.intel.com (8.11.6/8.11.6/d: outer.mc,v 1.51 2002/09/23 20:43:23 dmccart Exp $) with ESMTP id h1H3DdT16875
	for <kdb@oss.sgi.com>; Mon, 17 Feb 2003 03:13:39 GMT
Received: from pdsmsxvs01.pd.intel.com (pdsmsxvs01.pd.intel.com [172.16.12.122])
	by talaria.jf.intel.com (8.11.6/8.11.6/d: inner.mc,v 1.28 2003/01/13 19:44:39 dmccart Exp $) with SMTP id h1H2sA923611
	for <kdb@oss.sgi.com>; Mon, 17 Feb 2003 02:54:11 GMT
Received: from pdsmsx17.pd.intel.com ([172.16.12.121])
 by pdsmsxvs01.pd.intel.com (NAVGW 2.5.2.11) with SMTP id M2003021711153213682
 ; Mon, 17 Feb 2003 11:15:32 +0800
Received: by pdsmsx17.pd.intel.com with Internet Mail Service (5.5.2653.19)
	id <1AWFC4SJ>; Mon, 17 Feb 2003 11:14:22 +0800
Message-ID: <957BD1C2BF3CD411B6C500A0C944CA260309B4EE@pdsmsx32.pd.intel.com>
From: "Zhang, Sonic" <sonic.zhang@intel.com>
To: Keith Owens <kaos@sgi.com>
Cc: "KDB (E-mail)" <kdb@oss.sgi.com>
Subject: RE: About KDB global and local hardware breakpoint support in IA3
	2. 
Date: Mon, 17 Feb 2003 11:13:18 +0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-archive-position: 255
X-ecartis-version: Ecartis v1.0.0
Sender: kdb-bounce@oss.sgi.com
Errors-to: kdb-bounce@oss.sgi.com
X-original-sender: sonic.zhang@intel.com
Precedence: bulk
X-list: kdb

Hi,

	I am sorry, I didn't explain it very clearly.

	In current implementation for i386, a table for hardware breakpoints
is defined as follows:

	kdbhard_bp_t	kdb_hardbreaks[KDB_MAXHARDBPT];

	This means all CPUs share the same data structure of hardware
breakpoints. For example, the breakpoint in DR0 of each CPU refers to
kdb_hardbreaks[0], DR1 refers to kdb_hardbreaks[1], etc. The
kdb_hardbreaks[0] is installed to each CPU, when the CPU leaves KDB. Then,
all hardware breakpoints are global. And you can not create a local one for
one CPU and a different local one for the other CPU. So I change this data
structure into:
	kdbhard_bp_t	kdb_hardbreaks[KDB_MAXHARDBPT][NR_CPUS];


	In addition, each CPU executes kdb_bp_install_local() and
kdb_bp_remove_local() in kdb(), while only the initial CPU executes
kdb_bp_install_global() and kdb_bp_remove_global(). That means only the
initial CPU can install and remove a global breakpoint. But a hardware
global breakpoint must be installed and removed by each CPU itself. So, I
guess that you consider the global breakpoint the same as a instruction
breakpoint. Don't you think it doesn't accord with the definition of KDB
commands "bpa" and "bpha".  That's why I rename the string "local" with
"dbreg" and "global" with "inst".

	Thanks.

	Regards.

	Sonic Zhang


-----Original Message-----
From: Keith Owens [mailto:kaos@sgi.com]
Sent: 2003?2?13? 18:02
To: Zhang, Sonic
Cc: KDB (E-mail)
Subject: Re: About KDB global and local hardware breakpoint support in IA32.



On Thu, 13 Feb 2003 15:59:45 +0800, 
"Zhang, Sonic" <sonic.zhang@intel.com> wrote:
>	Current implementation in kdb-v3.0-2.4.20 sees a local breakpoint as
>an equivalence of a global breakpoint. All CPUs share the same data
>structure for hardware debug registers. And each CPU sets its debug
register
>for a hardware breakpoint, no matter whether it is a local one of the other
>CPUs.

Where do you get that from?  kdb_bp_install_local() is

void
kdb_bp_install_local(struct pt_regs *regs)
{
	int i;

	for(i=0; i<KDB_MAXBPT; i++) {
		if (KDB_DEBUG(BP)) {
			kdb_printf("kdb_bp_install_local bp %d bp_enabled %d
bp_global %d cpu %d bp_cpu %d\n",
				i, kdb_breakpoints[i].bp_enabled,
kdb_breakpoints[i].bp_global,
				smp_processor_id(),
kdb_breakpoints[i].bp_cpu);
		}
		if (kdb_breakpoints[i].bp_enabled
		 && kdb_breakpoints[i].bp_cpu == smp_processor_id()
		 && !kdb_breakpoints[i].bp_global){
			kdba_installbp(regs, &kdb_breakpoints[i]);
		}
	}
}

That function is called for each cpu as it leaves kdb.  It only
installs local breakpoints for the current cpu.

kdb_bp() has
	if (hardware && !global) {
		bp->bp_global = 0;
		bp->bp_cpu = smp_processor_id();
	}
marking local breakpoints by their cpu number.

From my_goal@rediffmail.com Mon Feb 24 12:04:52 2003
Received: with ECARTIS (v1.0.0; list kdb); Mon, 24 Feb 2003 12:05:26 -0800 (PST)
Received: from rediffmail.com (webmail27.rediffmail.com [203.199.83.37] (may be forged))
	by oss.sgi.com (8.12.5/8.12.5) with SMTP id h1OK4n3v003553
	for <kdb@oss.sgi.com>; Mon, 24 Feb 2003 12:04:51 -0800
Received: (qmail 26833 invoked by uid 510); 24 Feb 2003 20:04:04 -0000
Date: 24 Feb 2003 20:04:04 -0000
Message-ID: <20030224200404.26832.qmail@webmail27.rediffmail.com>
Received: from unknown (128.107.248.220) by rediffmail.com via HTTP; 24 feb 2003 20:04:04 -0000
MIME-Version: 1.0
From: "sudharsan  vijayaraghavan" <my_goal@rediffmail.com>
Reply-To: "sudharsan  vijayaraghavan" <my_goal@rediffmail.com>
To: kdb@oss.sgi.com
Subject: KDB question ???
Content-type: text/plain;
	format=flowed
Content-Disposition: inline
X-archive-position: 256
X-ecartis-version: Ecartis v1.0.0
Sender: kdb-bounce@oss.sgi.com
Errors-to: kdb-bounce@oss.sgi.com
X-original-sender: my_goal@rediffmail.com
Precedence: bulk
X-list: kdb

Hi ,

Please advice me how to use kdb .. Also let me know how to use the 
same
to debug modules inserted by me using "insmod".

Please get me a pointer to some useful links which discuss about 
the usage of kdb to debug kernel source as well as modules 
inserted using insmod.

Am facing a dump when i try invoking my own system call which has 
been registered in the module inserted by me.

Thanks in advance,
Sudharsan.



From kaos@sgi.com Mon Feb 24 12:46:24 2003
Received: with ECARTIS (v1.0.0; list kdb); Mon, 24 Feb 2003 12:46:38 -0800 (PST)
Received: from mail.ocs.com.au (mail.ocs.com.au [203.34.97.2])
	by oss.sgi.com (8.12.5/8.12.5) with SMTP id h1OKkL3v004532
	for <kdb@oss.sgi.com>; Mon, 24 Feb 2003 12:46:22 -0800
Received: (qmail 27013 invoked from network); 24 Feb 2003 20:46:17 -0000
Received: from ocs3.intra.ocs.com.au (192.168.255.3)
  by mail.ocs.com.au with SMTP; 24 Feb 2003 20:46:17 -0000
Received: by ocs3.intra.ocs.com.au (Postfix, from userid 16331)
	id 8DCB2300087; Tue, 25 Feb 2003 07:46:13 +1100 (EST)
Received: from ocs3.intra.ocs.com.au (localhost [127.0.0.1])
	by ocs3.intra.ocs.com.au (Postfix) with ESMTP
	id 5B3488F; Tue, 25 Feb 2003 07:46:13 +1100 (EST)
X-Mailer: exmh version 2.4 06/23/2000 with nmh-1.0.4
From: Keith Owens <kaos@sgi.com>
To: "sudharsan vijayaraghavan" <my_goal@rediffmail.com>
Cc: kdb@oss.sgi.com
Subject: Re: KDB question ??? 
In-reply-to: Your message of "24 Feb 2003 20:04:04 -0000."
             <20030224200404.26832.qmail@webmail27.rediffmail.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 25 Feb 2003 07:46:08 +1100
Message-ID: <9228.1046119568@ocs3.intra.ocs.com.au>
X-archive-position: 257
X-ecartis-version: Ecartis v1.0.0
Sender: kdb-bounce@oss.sgi.com
Errors-to: kdb-bounce@oss.sgi.com
X-original-sender: kaos@sgi.com
Precedence: bulk
X-list: kdb

On 24 Feb 2003 20:04:04 -0000, 
"sudharsan vijayaraghavan" <my_goal@rediffmail.com> wrote:
>Please advice me how to use kdb

See Documentation/kdb in the kdb common patch.

>Am facing a dump when i try invoking my own system call which has 
>been registered in the module inserted by me.

System calls are not supported in modules.  This is a Linus restriction.


From rukiah@indosat.net.id Tue Feb 25 09:33:18 2003
Received: with ECARTIS (v1.0.0; list kdb); Tue, 25 Feb 2003 09:33:27 -0800 (PST)
Received: from jktsm04 ([202.155.50.23])
	by oss.sgi.com (8.12.5/8.12.5) with SMTP id h1PHXG3v019757
	for <kdb@oss.sgi.com>; Tue, 25 Feb 2003 09:33:17 -0800
Received: from gappi-lez7hp4tz ([202.155.52.149]) by imsmta4.indosat.net.id
 (iPlanet Messaging Server 5.2 HotFix 1.09 (built Jan  7 2003))
 with ESMTP id <0HAV0034XLC610@imsmta4.indosat.net.id> for kdb@oss.sgi.com;
 Wed, 26 Feb 2003 00:46:43 +0700 (JAVT)
Date: Wed, 26 Feb 2003 00:32:32 +0700
From: Henry Lienardi <rukiah@indosat.net.id>
Subject: Re: KOMISI RP.35.000 SETIAP PENJUALAN
To: Kesempatan Usaha Online2 <rukiah@indosat.net.id>
Message-id: <411-220032225173232104@gappi-lez7hp4tz>
MIME-version: 1.0
Content-type: multipart/alternative;
 boundary="Boundary_(ID_FdcHGumGSNJBn8cj2iIvvA)"
X-archive-position: 258
X-ecartis-version: Ecartis v1.0.0
Sender: kdb-bounce@oss.sgi.com
Errors-to: kdb-bounce@oss.sgi.com
X-original-sender: rukiah@indosat.net.id
Precedence: bulk
X-list: kdb


--Boundary_(ID_FdcHGumGSNJBn8cj2iIvvA)
Content-type: text/plain; charset=windows-1252
Content-transfer-encoding: quoted-printable


=20

KOMISI RP=2E35=2E000 SETIAP PENJUALAN

Tahukah Anda bahwa Bisnis melalui internet merupakan tren yang sedang berk=
embang di Indonesia? Cobalah simak dua kutipan berikut ini:

 =93Business Intelligence Report (BIRO) menunjukkan bahwa di Indonesia sek=
itar 60% responden yang disurvey sudah terbiasa berkorespondensi lewat e-m=
ail dan siap bertransaksi secara online=2E=94

 =93Majalah Warta Ekonomi (edisi No=2E25/XIII/25 Juni 2001) menulis bahwa =
30% perusahaan UKM di wilayah Jabotabek telah menggunakan website sebagai =
media promosi mereka=2E=94

 Internet sudah mulai dimanfaatkan sebagai media pemasaran baik oleh perus=
ahaan besar maupun kecil=2E=20

 Dan, melalui email ini, kami ingin memperkenalkan kepada Anda sebuah peru=
sahaan kecil yang menjalankan bisnisnya hanya melalui internet=2E Dan, bag=
aimana Anda juga bisa berperan dalam perusahaan ini serta mendapatkan peng=
hasilan yang bagus=2E

=20

PROYEKSI PENGHASILAN ANDA

 Perusahaan ini menjual produknya seharga Rp=2E70=2E000 dan Anda diberikan=
 komisi 50% atau Rp=2E35=2E000 untuk setiap penjualan=2E=20

Berapa besarkah penghasilan yang bisa Anda peroleh dalam sebulan? Sebenarn=
ya tidak ada batasan, semuanya tergantung pada usaha dan kemauan Anda=2E

Sebagai perkiraan, silahkan Anda menyimak proyeksi dibawah ini:=20

1 penjualan/ hari           =3D Rp=2E 1=2E050=2E000/ bulan

2 penjualan/ hari           =3D Rp=2E 2=2E100=2E000/ bulan

5 penjualan/ hari           =3D Rp=2E 5=2E250=2E000/ bulan

Sebenarnya, kalau Anda bisa menjual sebuah saja dalam sehari dan mendapatk=
an Rp=2E1=2E050=2E000 sudah sangat lumayan, bukan? Apalagi kalau =85=2E=2E=
?

=20

 PRODUK YANG PASTI LAKU DIJUAL

Produk yang akan Anda promosikan adalah sebuah paket informasi & software=2E=
 Produk intinya adalah sebuah software (39 links) yang mampu melipat-ganda=
kan kecepatan kerja sebuah komputer=2E Pengguna komputer akan sangat mengh=
argai software ini=2E Dan, ada banyak sekali pengguna komputer sekarang=2E=
 Asal Anda bisa menjelaskan dengan baik manfaat produk ini, kemungkinan be=
sar mereka akan membeli=2E=20

Dalam produk unggulan ini, Anda juga akan menemukan ratusan tips komputer=2E=
 Pengguna komputer juga akan sangat mengharga tips-tips ini karena bisa me=
mbantu mereka semakin mahir menggunakan komputer baik untuk bekerja maupun=
 untuk hiburan=2E

Dan, produk ini juga menyertakan informasi bagaimana cara mendapatkan soft=
ware apapun secara gratis di internet=2E Mereka yang suka berselancar di i=
nternet tahu bahwa software di internet dijual dengan harga mahal=2E Banya=
k pecandu internet akan senang apabila diberitahu alamat situs dimana semu=
a software bisa diperoleh secara gratis=2E Anda akan dengan mudah menjual =
informasi ini kepada mereka=2E

=20

BIAYA MENGIKUTI BISNIS ONLINE INI

Berapa biaya yang harus Anda keluarkan untuk mengikuti program ini? Tidak =
ada! Tetapi, Anda  perlu membeli produk tersebut untuk dipelajari=2E Anda =
hanya bisa mempromosikan sesuatu yang Anda tahu dengan baik=2E Download so=
ftware tersebut dan dipakai=2E Lihat bagaimana ia melipat-gandakan kecepat=
an kerja komputer Anda, kecepatan sambungan ke internet, dan lain-lain=2E =
Harganya hanya Rp=2E70=2E000! Jangan khawatir dengan angka kecil ini=2E Mo=
dal Anda sudah kembali dengan melakukan dua penjualan=2E Selanjutnya, seti=
ap penjualan adalah keuntungan bersih Anda=2E

Kami juga akan mengajari Anda bagaimana melakukan promosi melalui internet=
=2E Kami akan berikan contoh naskah iklan yang bisa Anda kirimkan ke teman=
-teman=2E Kami akan tunjukkan di mana Anda bisa memasang iklan secara grat=
is di internet=2E Kami bahkan akan memberi Anda sebuah software pengirim e=
mail massal secara gratis=2E Kami ingin Anda berhasil=2E

=20

JANGAN MENUNGGU! MULAI BISNIS INI SEKARANG JUGA!

Apakah Anda akan sia-siakan kesempatan ini? Kunjungi situs kami dan Anda p=
asti akan terkesan dan TERTARIK!

Sekarang silahkan kirim sebuah email ke mailto:infopenting@GetResponse=2Ec=
om dan dalam waktu 30 detik, Anda akan mendapatkan informasi lengkap untuk=
 memulai bisnis internet ini=2E

=20

Salam Hangat,

Henry Lienardi

=20

=20

--Boundary_(ID_FdcHGumGSNJBn8cj2iIvvA)
Content-type: text/html; charset=windows-1252
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<META http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dwindows-=
1252">
</HEAD>
<BODY>
<P align=3Dcenter><FONT color=3D#800040><STRONG><FONT=20
size=3D5><FONT face=3DArial></FONT></FONT></STRONG></FONT>&nbsp;</P>
<P align=3Dcenter><FONT color=3D#800040><STRONG><FONT=20
size=3D5><FONT face=3DArial>KOMISI RP=2E35=2E000 SETIAP PENJUALAN<?xml:nam=
espace prefix=20
=3D o ns =3D "urn:schemas-microsoft-com:office:office"=20
/><o:p></o:p></FONT></FONT></STRONG></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial>Tahukah Anda bahwa Bisnis melalui =
internet=20
merupakan tren yang sedang berkembang di <?xml:namespace prefix =3D st1 ns=
 =3D=20
"urn:schemas-microsoft-com:office:smarttags"=20
/><st1:country-region><st1:place>Indonesia</st1:place></st1:country-region=
>?=20
Cobalah simak dua kutipan berikut ini:</FONT></P>
<P class=3DMsoNormal><FONT face=3DArial><o:p>&nbsp;</o:p></FONT><FONT=20
face=3DArial>=93Business Intelligence Report (BIRO) menunjukkan bahwa di=20=

<st1:country-region><st1:place>Indonesia</st1:place></st1:country-region>=20=

sekitar 60% responden yang disurvey sudah terbiasa berkorespondensi lewat =
e-mail=20
dan siap bertransaksi secara online=2E=94</FONT></P>
<P class=3DMsoNormal><FONT face=3DArial><o:p>&nbsp;</o:p></FONT><FONT=20
face=3DArial>=93Majalah Warta Ekonomi (edisi No=2E25/XIII/25 Juni 2001) me=
nulis bahwa=20
30% perusahaan UKM di wilayah Jabotabek telah menggunakan website sebagai =
media=20
promosi mereka=2E=94</FONT></P>
<P class=3DMsoNormal><FONT face=3DArial><o:p>&nbsp;</o:p></FONT><FONT=20
face=3DArial>Internet sudah mulai dimanfaatkan sebagai media pemasaran bai=
k oleh=20
perusahaan besar maupun kecil=2E </FONT></P>
<P class=3DMsoNormal><FONT face=3DArial><o:p>&nbsp;</o:p></FONT><FONT=20
face=3DArial>Dan, melalui email ini, kami ingin memperkenalkan kepada Anda=
 sebuah=20
perusahaan kecil yang menjalankan bisnisnya hanya melalui internet=2E Dan,=
=20
bagaimana Anda juga bisa berperan dalam perusahaan ini serta mendapatkan=20=

penghasilan yang bagus=2E</FONT></P>
<P class=3DMsoNormal><FONT face=3DArial><o:p>&nbsp;</o:p></FONT></P>
<P align=3Dcenter class=3DMsoNormal><FONT color=3D#800040 face=3DArial=20
size=3D4><STRONG>PROYEKSI PENGHASILAN ANDA</STRONG></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial><o:p>&nbsp;</o:p></FONT><FONT=20
face=3DArial>Perusahaan ini menjual produknya seharga Rp=2E70=2E000 dan An=
da diberikan=20
komisi 50% atau Rp=2E35=2E000 untuk setiap penjualan=2E </FONT></P>
<P class=3DMsoNormal><FONT face=3DArial>Berapa besarkah penghasilan yang b=
isa Anda=20
peroleh dalam sebulan? Sebenarnya tidak ada batasan, semuanya tergantung p=
ada=20
usaha dan kemauan Anda=2E</FONT></P>
<P class=3DMsoNormal><FONT face=3DArial>Sebagai perkiraan, silahkan Anda m=
enyimak=20
proyeksi dibawah ini: </FONT></P>
<P align=3Dcenter class=3DMsoNormal><STRONG><FONT color=3D#800040 face=3DA=
rial>1=20
penjualan/ hari<SPAN=20
style=3D"mso-tab-count: 1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;=20
</SPAN>=3D Rp=2E 1=2E050=2E000/ bulan</FONT></STRONG></P>
<P align=3Dcenter class=3DMsoNormal><STRONG><FONT color=3D#800040 face=3DA=
rial>2=20
penjualan/ hari<SPAN=20
style=3D"mso-tab-count: 1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;=20
</SPAN>=3D Rp=2E 2=2E100=2E000/ bulan</FONT></STRONG></P>
<P align=3Dcenter class=3DMsoNormal><STRONG><FONT color=3D#800040 face=3DA=
rial>5=20
penjualan/ hari<SPAN=20
style=3D"mso-tab-count: 1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;=20
</SPAN>=3D Rp=2E 5=2E250=2E000/ bulan</FONT></STRONG><FONT face=3DArial></=
FONT></P>
<P align=3Dleft class=3DMsoNormal><FONT face=3DArial>Sebenarnya, kalau And=
a bisa=20
menjual sebuah saja dalam sehari dan mendapatkan Rp=2E1=2E050=2E000 sudah =
sangat=20
lumayan, bukan? Apalagi kalau =85=2E=2E?</FONT></P>
<P align=3Dcenter class=3DMsoNormal><FONT face=3DArial><o:p></o:p></FONT>&=
nbsp;</P>
<P align=3Dcenter class=3DMsoNormal><FONT=20
face=3DArial><o:p>&nbsp;</o:p></FONT><STRONG><FONT color=3D#800040 face=3D=
Arial=20
size=3D4>PRODUK YANG PASTI LAKU DIJUAL</FONT></STRONG></P>
<P class=3DMsoNormal><FONT face=3DArial>Produk yang akan Anda promosikan a=
dalah=20
sebuah paket informasi &amp; software=2E Produk intinya adalah sebuah soft=
ware (39=20
links) yang mampu melipat-gandakan kecepatan kerja sebuah komputer=2E Peng=
guna=20
komputer akan sangat menghargai software ini=2E Dan, ada banyak sekali pen=
gguna=20
komputer sekarang=2E Asal Anda bisa menjelaskan dengan baik manfaat produk=
 ini,=20
kemungkinan besar mereka akan membeli=2E </FONT></P>
<P class=3DMsoNormal><FONT face=3DArial>Dalam produk unggulan ini, Anda ju=
ga akan=20
menemukan ratusan tips komputer=2E Pengguna komputer juga akan sangat meng=
harga=20
tips-tips ini karena bisa membantu mereka semakin mahir menggunakan komput=
er=20
baik untuk bekerja maupun untuk hiburan=2E</FONT></P>
<P class=3DMsoNormal><FONT face=3DArial>Dan, produk ini juga menyertakan i=
nformasi=20
bagaimana cara mendapatkan software apapun secara gratis di internet=2E Me=
reka=20
yang suka berselancar di internet tahu bahwa software di internet dijual d=
engan=20
harga mahal=2E Banyak pecandu internet akan senang apabila diberitahu alam=
at situs=20
dimana semua software bisa diperoleh secara gratis=2E Anda akan dengan mud=
ah=20
menjual informasi ini kepada mereka=2E</FONT></P>
<P class=3DMsoNormal><FONT face=3DArial><o:p>&nbsp;</o:p></FONT><FONT=20
face=3DArial></FONT></P>
<P align=3Dcenter class=3DMsoNormal><STRONG><FONT color=3D#800040 face=3DA=
rial=20
size=3D4>BIAYA MENGIKUTI BISNIS ONLINE INI</FONT></STRONG></P>
<P align=3Dleft class=3DMsoNormal><FONT face=3DArial>Berapa biaya yang har=
us Anda=20
keluarkan untuk mengikuti program ini? Tidak ada! Tetapi, Anda<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>perlu membeli produk tersebut un=
tuk=20
dipelajari=2E Anda hanya bisa mempromosikan sesuatu yang Anda tahu dengan =
baik=2E=20
Download software tersebut dan dipakai=2E Lihat bagaimana ia melipat-ganda=
kan=20
kecepatan kerja komputer Anda, kecepatan sambungan ke internet, dan lain-l=
ain=2E=20
Harganya hanya Rp=2E70=2E000! Jangan khawatir dengan angka kecil ini=2E Mo=
dal Anda=20
sudah kembali dengan melakukan dua penjualan=2E Selanjutnya, setiap penjua=
lan=20
adalah keuntungan bersih Anda=2E</FONT></P>
<P align=3Dleft class=3DMsoNormal><FONT face=3DArial>Kami juga akan mengaj=
ari Anda=20
bagaimana melakukan promosi melalui internet=2E Kami akan berikan contoh n=
askah=20
iklan yang bisa Anda kirimkan ke teman-teman=2E Kami akan tunjukkan di man=
a Anda=20
bisa memasang iklan secara gratis di internet=2E Kami bahkan akan memberi =
Anda=20
sebuah software pengirim email massal secara gratis=2E Kami ingin Anda=20
berhasil=2E</FONT></P>
<P class=3DMsoNormal><FONT face=3DArial><o:p>&nbsp;</o:p></FONT><FONT=20
face=3DArial></FONT></P>
<P align=3Dcenter class=3DMsoNormal><STRONG><FONT color=3D#ff0000 face=3DA=
rial>JANGAN=20
MENUNGGU! MULAI BISNIS INI SEKARANG JUGA!</FONT></STRONG></P>
<P align=3Dleft class=3DMsoNormal><FONT face=3DArial>Apakah Anda akan sia-=
siakan=20
kesempatan ini? Kunjungi situs kami dan Anda pasti akan terkesan dan=20
TERTARIK!</FONT></P>
<P class=3DMsoNormal><FONT face=3DArial>Sekarang silahkan kirim sebuah ema=
il ke <A=20
href=3D"mailto:infopenting@GetResponse=2Ecom"><FONT=20
color=3D#0080ff><STRONG>mailto:infopenting@GetResponse=2Ecom</STRONG></FON=
T></A>&nbsp;dan=20
dalam waktu 30 detik, Anda akan mendapatkan informasi lengkap untuk memula=
i=20
bisnis internet ini=2E</FONT></P>
<P class=3DMsoNormal><FONT face=3DArial><o:p>&nbsp;</o:p></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial>Salam Hangat,</FONT></P>
<P class=3DMsoNormal><FONT face=3DArial>Henry Lienardi</FONT></P>
<P class=3DMsoNormal>&nbsp;</P>
<P class=3DMsoNormal>&nbsp;</P>
</BODY>
</HTML>

--Boundary_(ID_FdcHGumGSNJBn8cj2iIvvA)--

From rukiah@indosat.net.id Tue Feb 25 19:27:58 2003
Received: with ECARTIS (v1.0.0; list kdb); Tue, 25 Feb 2003 19:28:04 -0800 (PST)
Received: from jktsm04 ([202.155.50.23])
	by oss.sgi.com (8.12.5/8.12.5) with SMTP id h1Q3Ru3v009508
	for <kdb@oss.sgi.com>; Tue, 25 Feb 2003 19:27:58 -0800
Received: from gappi-lez7hp4tz ([202.155.52.188]) by imsmta4.indosat.net.id
 (iPlanet Messaging Server 5.2 HotFix 1.09 (built Jan  7 2003))
 with ESMTP id <0HAW0050FCMA2Q@imsmta4.indosat.net.id> for kdb@oss.sgi.com;
 Wed, 26 Feb 2003 10:36:32 +0700 (JAVT)
Date: Wed, 26 Feb 2003 10:21:57 +0700
From: Henry Lienardi <rukiah@indosat.net.id>
Subject: Re: KOMISI RP.35.000 SETIAP PENJUALAN
To: Kesempatan Usaha Online2 <rukiah@indosat.net.id>
Message-id: <411-2200323263215730@gappi-lez7hp4tz>
MIME-version: 1.0
Content-type: multipart/alternative;
 boundary="Boundary_(ID_9/Y7q+r+GGGq9/2QvFstmA)"
X-archive-position: 259
X-ecartis-version: Ecartis v1.0.0
Sender: kdb-bounce@oss.sgi.com
Errors-to: kdb-bounce@oss.sgi.com
X-original-sender: rukiah@indosat.net.id
Precedence: bulk
X-list: kdb


--Boundary_(ID_9/Y7q+r+GGGq9/2QvFstmA)
Content-type: text/plain; charset=windows-1252
Content-transfer-encoding: quoted-printable


=20

KOMISI RP=2E35=2E000 SETIAP PENJUALAN

Tahukah Anda bahwa Bisnis melalui internet merupakan tren yang sedang berk=
embang di Indonesia? Cobalah simak dua kutipan berikut ini:

 =93Business Intelligence Report (BIRO) menunjukkan bahwa di Indonesia sek=
itar 60% responden yang disurvey sudah terbiasa berkorespondensi lewat e-m=
ail dan siap bertransaksi secara online=2E=94

 =93Majalah Warta Ekonomi (edisi No=2E25/XIII/25 Juni 2001) menulis bahwa =
30% perusahaan UKM di wilayah Jabotabek telah menggunakan website sebagai =
media promosi mereka=2E=94

 Internet sudah mulai dimanfaatkan sebagai media pemasaran baik oleh perus=
ahaan besar maupun kecil=2E=20

 Dan, melalui email ini, kami ingin memperkenalkan kepada Anda sebuah peru=
sahaan kecil yang menjalankan bisnisnya hanya melalui internet=2E Dan, bag=
aimana Anda juga bisa berperan dalam perusahaan ini serta mendapatkan peng=
hasilan yang bagus=2E

=20

PROYEKSI PENGHASILAN ANDA

 Perusahaan ini menjual produknya seharga Rp=2E70=2E000 dan Anda diberikan=
 komisi 50% atau Rp=2E35=2E000 untuk setiap penjualan=2E=20

Berapa besarkah penghasilan yang bisa Anda peroleh dalam sebulan? Sebenarn=
ya tidak ada batasan, semuanya tergantung pada usaha dan kemauan Anda=2E

Sebagai perkiraan, silahkan Anda menyimak proyeksi dibawah ini:=20

1 penjualan/ hari           =3D Rp=2E 1=2E050=2E000/ bulan

2 penjualan/ hari           =3D Rp=2E 2=2E100=2E000/ bulan

5 penjualan/ hari           =3D Rp=2E 5=2E250=2E000/ bulan

Sebenarnya, kalau Anda bisa menjual sebuah saja dalam sehari dan mendapatk=
an Rp=2E1=2E050=2E000 sudah sangat lumayan, bukan? Apalagi kalau =85=2E=2E=
?

=20

 PRODUK YANG PASTI LAKU DIJUAL

Produk yang akan Anda promosikan adalah sebuah paket informasi & software=2E=
 Produk intinya adalah sebuah software (39 links) yang mampu melipat-ganda=
kan kecepatan kerja sebuah komputer=2E Pengguna komputer akan sangat mengh=
argai software ini=2E Dan, ada banyak sekali pengguna komputer sekarang=2E=
 Asal Anda bisa menjelaskan dengan baik manfaat produk ini, kemungkinan be=
sar mereka akan membeli=2E=20

Dalam produk unggulan ini, Anda juga akan menemukan ratusan tips komputer=2E=
 Pengguna komputer juga akan sangat mengharga tips-tips ini karena bisa me=
mbantu mereka semakin mahir menggunakan komputer baik untuk bekerja maupun=
 untuk hiburan=2E

Dan, produk ini juga menyertakan informasi bagaimana cara mendapatkan soft=
ware apapun secara gratis di internet=2E Mereka yang suka berselancar di i=
nternet tahu bahwa software di internet dijual dengan harga mahal=2E Banya=
k pecandu internet akan senang apabila diberitahu alamat situs dimana semu=
a software bisa diperoleh secara gratis=2E Anda akan dengan mudah menjual =
informasi ini kepada mereka=2E

=20

BIAYA MENGIKUTI BISNIS ONLINE INI

Berapa biaya yang harus Anda keluarkan untuk mengikuti program ini? Tidak =
ada! Tetapi, Anda  perlu membeli produk tersebut untuk dipelajari=2E Anda =
hanya bisa mempromosikan sesuatu yang Anda tahu dengan baik=2E Download so=
ftware tersebut dan dipakai=2E Lihat bagaimana ia melipat-gandakan kecepat=
an kerja komputer Anda, kecepatan sambungan ke internet, dan lain-lain=2E =
Harganya hanya Rp=2E70=2E000! Jangan khawatir dengan angka kecil ini=2E Mo=
dal Anda sudah kembali dengan melakukan dua penjualan=2E Selanjutnya, seti=
ap penjualan adalah keuntungan bersih Anda=2E

Kami juga akan mengajari Anda bagaimana melakukan promosi melalui internet=
=2E Kami akan berikan contoh naskah iklan yang bisa Anda kirimkan ke teman=
-teman=2E Kami akan tunjukkan di mana Anda bisa memasang iklan secara grat=
is di internet=2E Kami bahkan akan memberi Anda sebuah software pengirim e=
mail massal secara gratis=2E Kami ingin Anda berhasil=2E

=20

JANGAN MENUNGGU! MULAI BISNIS INI SEKARANG JUGA!

Apakah Anda akan sia-siakan kesempatan ini? Kunjungi situs kami dan Anda p=
asti akan terkesan dan TERTARIK!

Sekarang silahkan kirim sebuah email ke mailto:infopenting@GetResponse=2Ec=
om dan dalam waktu 30 detik, Anda akan mendapatkan informasi lengkap untuk=
 memulai bisnis internet ini=2E

=20

Salam Hangat,

Henry Lienardi

=20

=20

--Boundary_(ID_9/Y7q+r+GGGq9/2QvFstmA)
Content-type: text/html; charset=windows-1252
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<META http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dwindows-=
1252">
</HEAD>
<BODY>
<P align=3Dcenter><FONT color=3D#800040><STRONG><FONT=20
size=3D5><FONT face=3DArial></FONT></FONT></STRONG></FONT>&nbsp;</P>
<P align=3Dcenter><FONT color=3D#800040><STRONG><FONT=20
size=3D5><FONT face=3DArial>KOMISI RP=2E35=2E000 SETIAP PENJUALAN<?xml:nam=
espace prefix=20
=3D o ns =3D "urn:schemas-microsoft-com:office:office"=20
/><o:p></o:p></FONT></FONT></STRONG></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial>Tahukah Anda bahwa Bisnis melalui =
internet=20
merupakan tren yang sedang berkembang di <?xml:namespace prefix =3D st1 ns=
 =3D=20
"urn:schemas-microsoft-com:office:smarttags"=20
/><st1:country-region><st1:place>Indonesia</st1:place></st1:country-region=
>?=20
Cobalah simak dua kutipan berikut ini:</FONT></P>
<P class=3DMsoNormal><FONT face=3DArial><o:p>&nbsp;</o:p></FONT><FONT=20
face=3DArial>=93Business Intelligence Report (BIRO) menunjukkan bahwa di=20=

<st1:country-region><st1:place>Indonesia</st1:place></st1:country-region>=20=

sekitar 60% responden yang disurvey sudah terbiasa berkorespondensi lewat =
e-mail=20
dan siap bertransaksi secara online=2E=94</FONT></P>
<P class=3DMsoNormal><FONT face=3DArial><o:p>&nbsp;</o:p></FONT><FONT=20
face=3DArial>=93Majalah Warta Ekonomi (edisi No=2E25/XIII/25 Juni 2001) me=
nulis bahwa=20
30% perusahaan UKM di wilayah Jabotabek telah menggunakan website sebagai =
media=20
promosi mereka=2E=94</FONT></P>
<P class=3DMsoNormal><FONT face=3DArial><o:p>&nbsp;</o:p></FONT><FONT=20
face=3DArial>Internet sudah mulai dimanfaatkan sebagai media pemasaran bai=
k oleh=20
perusahaan besar maupun kecil=2E </FONT></P>
<P class=3DMsoNormal><FONT face=3DArial><o:p>&nbsp;</o:p></FONT><FONT=20
face=3DArial>Dan, melalui email ini, kami ingin memperkenalkan kepada Anda=
 sebuah=20
perusahaan kecil yang menjalankan bisnisnya hanya melalui internet=2E Dan,=
=20
bagaimana Anda juga bisa berperan dalam perusahaan ini serta mendapatkan=20=

penghasilan yang bagus=2E</FONT></P>
<P class=3DMsoNormal><FONT face=3DArial><o:p>&nbsp;</o:p></FONT></P>
<P align=3Dcenter class=3DMsoNormal><FONT color=3D#800040 face=3DArial=20
size=3D4><STRONG>PROYEKSI PENGHASILAN ANDA</STRONG></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial><o:p>&nbsp;</o:p></FONT><FONT=20
face=3DArial>Perusahaan ini menjual produknya seharga Rp=2E70=2E000 dan An=
da diberikan=20
komisi 50% atau Rp=2E35=2E000 untuk setiap penjualan=2E </FONT></P>
<P class=3DMsoNormal><FONT face=3DArial>Berapa besarkah penghasilan yang b=
isa Anda=20
peroleh dalam sebulan? Sebenarnya tidak ada batasan, semuanya tergantung p=
ada=20
usaha dan kemauan Anda=2E</FONT></P>
<P class=3DMsoNormal><FONT face=3DArial>Sebagai perkiraan, silahkan Anda m=
enyimak=20
proyeksi dibawah ini: </FONT></P>
<P align=3Dcenter class=3DMsoNormal><STRONG><FONT color=3D#800040 face=3DA=
rial>1=20
penjualan/ hari<SPAN=20
style=3D"mso-tab-count: 1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;=20
</SPAN>=3D Rp=2E 1=2E050=2E000/ bulan</FONT></STRONG></P>
<P align=3Dcenter class=3DMsoNormal><STRONG><FONT color=3D#800040 face=3DA=
rial>2=20
penjualan/ hari<SPAN=20
style=3D"mso-tab-count: 1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;=20
</SPAN>=3D Rp=2E 2=2E100=2E000/ bulan</FONT></STRONG></P>
<P align=3Dcenter class=3DMsoNormal><STRONG><FONT color=3D#800040 face=3DA=
rial>5=20
penjualan/ hari<SPAN=20
style=3D"mso-tab-count: 1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;=20
</SPAN>=3D Rp=2E 5=2E250=2E000/ bulan</FONT></STRONG><FONT face=3DArial></=
FONT></P>
<P align=3Dleft class=3DMsoNormal><FONT face=3DArial>Sebenarnya, kalau And=
a bisa=20
menjual sebuah saja dalam sehari dan mendapatkan Rp=2E1=2E050=2E000 sudah =
sangat=20
lumayan, bukan? Apalagi kalau =85=2E=2E?</FONT></P>
<P align=3Dcenter class=3DMsoNormal><FONT face=3DArial><o:p></o:p></FONT>&=
nbsp;</P>
<P align=3Dcenter class=3DMsoNormal><FONT=20
face=3DArial><o:p>&nbsp;</o:p></FONT><STRONG><FONT color=3D#800040 face=3D=
Arial=20
size=3D4>PRODUK YANG PASTI LAKU DIJUAL</FONT></STRONG></P>
<P class=3DMsoNormal><FONT face=3DArial>Produk yang akan Anda promosikan a=
dalah=20
sebuah paket informasi &amp; software=2E Produk intinya adalah sebuah soft=
ware (39=20
links) yang mampu melipat-gandakan kecepatan kerja sebuah komputer=2E Peng=
guna=20
komputer akan sangat menghargai software ini=2E Dan, ada banyak sekali pen=
gguna=20
komputer sekarang=2E Asal Anda bisa menjelaskan dengan baik manfaat produk=
 ini,=20
kemungkinan besar mereka akan membeli=2E </FONT></P>
<P class=3DMsoNormal><FONT face=3DArial>Dalam produk unggulan ini, Anda ju=
ga akan=20
menemukan ratusan tips komputer=2E Pengguna komputer juga akan sangat meng=
harga=20
tips-tips ini karena bisa membantu mereka semakin mahir menggunakan komput=
er=20
baik untuk bekerja maupun untuk hiburan=2E</FONT></P>
<P class=3DMsoNormal><FONT face=3DArial>Dan, produk ini juga menyertakan i=
nformasi=20
bagaimana cara mendapatkan software apapun secara gratis di internet=2E Me=
reka=20
yang suka berselancar di internet tahu bahwa software di internet dijual d=
engan=20
harga mahal=2E Banyak pecandu internet akan senang apabila diberitahu alam=
at situs=20
dimana semua software bisa diperoleh secara gratis=2E Anda akan dengan mud=
ah=20
menjual informasi ini kepada mereka=2E</FONT></P>
<P class=3DMsoNormal><FONT face=3DArial><o:p>&nbsp;</o:p></FONT><FONT=20
face=3DArial></FONT></P>
<P align=3Dcenter class=3DMsoNormal><STRONG><FONT color=3D#800040 face=3DA=
rial=20
size=3D4>BIAYA MENGIKUTI BISNIS ONLINE INI</FONT></STRONG></P>
<P align=3Dleft class=3DMsoNormal><FONT face=3DArial>Berapa biaya yang har=
us Anda=20
keluarkan untuk mengikuti program ini? Tidak ada! Tetapi, Anda<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>perlu membeli produk tersebut un=
tuk=20
dipelajari=2E Anda hanya bisa mempromosikan sesuatu yang Anda tahu dengan =
baik=2E=20
Download software tersebut dan dipakai=2E Lihat bagaimana ia melipat-ganda=
kan=20
kecepatan kerja komputer Anda, kecepatan sambungan ke internet, dan lain-l=
ain=2E=20
Harganya hanya Rp=2E70=2E000! Jangan khawatir dengan angka kecil ini=2E Mo=
dal Anda=20
sudah kembali dengan melakukan dua penjualan=2E Selanjutnya, setiap penjua=
lan=20
adalah keuntungan bersih Anda=2E</FONT></P>
<P align=3Dleft class=3DMsoNormal><FONT face=3DArial>Kami juga akan mengaj=
ari Anda=20
bagaimana melakukan promosi melalui internet=2E Kami akan berikan contoh n=
askah=20
iklan yang bisa Anda kirimkan ke teman-teman=2E Kami akan tunjukkan di man=
a Anda=20
bisa memasang iklan secara gratis di internet=2E Kami bahkan akan memberi =
Anda=20
sebuah software pengirim email massal secara gratis=2E Kami ingin Anda=20
berhasil=2E</FONT></P>
<P class=3DMsoNormal><FONT face=3DArial><o:p>&nbsp;</o:p></FONT><FONT=20
face=3DArial></FONT></P>
<P align=3Dcenter class=3DMsoNormal><STRONG><FONT color=3D#ff0000 face=3DA=
rial>JANGAN=20
MENUNGGU! MULAI BISNIS INI SEKARANG JUGA!</FONT></STRONG></P>
<P align=3Dleft class=3DMsoNormal><FONT face=3DArial>Apakah Anda akan sia-=
siakan=20
kesempatan ini? Kunjungi situs kami dan Anda pasti akan terkesan dan=20
TERTARIK!</FONT></P>
<P class=3DMsoNormal><FONT face=3DArial>Sekarang silahkan kirim sebuah ema=
il ke <A=20
href=3D"mailto:infopenting@GetResponse=2Ecom"><FONT=20
color=3D#0080ff><STRONG>mailto:infopenting@GetResponse=2Ecom</STRONG></FON=
T></A>&nbsp;dan=20
dalam waktu 30 detik, Anda akan mendapatkan informasi lengkap untuk memula=
i=20
bisnis internet ini=2E</FONT></P>
<P class=3DMsoNormal><FONT face=3DArial><o:p>&nbsp;</o:p></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial>Salam Hangat,</FONT></P>
<P class=3DMsoNormal><FONT face=3DArial>Henry Lienardi</FONT></P>
<P class=3DMsoNormal>&nbsp;</P>
<P class=3DMsoNormal>&nbsp;</P>
</BODY>
</HTML>

--Boundary_(ID_9/Y7q+r+GGGq9/2QvFstmA)--

From rukiah@indosat.net.id Tue Feb 25 19:43:37 2003
Received: with ECARTIS (v1.0.0; list kdb); Tue, 25 Feb 2003 19:43:41 -0800 (PST)
Received: from jktsm04 ([202.155.50.23])
	by oss.sgi.com (8.12.5/8.12.5) with SMTP id h1Q3hZ3v009610
	for <kdb@oss.sgi.com>; Tue, 25 Feb 2003 19:43:36 -0800
Received: from gappi-lez7hp4tz ([202.155.52.188]) by imsmta4.indosat.net.id
 (iPlanet Messaging Server 5.2 HotFix 1.09 (built Jan  7 2003))
 with ESMTP id <0HAW005BDDJN4X@imsmta4.indosat.net.id> for kdb@oss.sgi.com;
 Wed, 26 Feb 2003 10:56:52 +0700 (JAVT)
Date: Wed, 26 Feb 2003 10:42:13 +0700
From: Henry Lienardi <rukiah@indosat.net.id>
Subject: Re: KOMISI RP.35.000 SETIAP PENJUALAN
To: Kesempatan Usaha Online2 <rukiah@indosat.net.id>
Message-id: <411-22003232634213630@gappi-lez7hp4tz>
MIME-version: 1.0
Content-type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id h1Q3hZ3v009610
X-archive-position: 260
X-ecartis-version: Ecartis v1.0.0
Sender: kdb-bounce@oss.sgi.com
Errors-to: kdb-bounce@oss.sgi.com
X-original-sender: rukiah@indosat.net.id
Precedence: bulk
X-list: kdb


KOMISI RP.35.000 SETIAP PENJUALAN

Tahukah Anda bahwa Bisnis melalui internet merupakan tren yang sedang berkembang di Indonesia? Cobalah simak dua kutipan berikut ini:

"Business Intelligence Report (BIRO) menunjukkan bahwa di Indonesia sekitar 60% responden yang disurvey sudah terbiasa berkorespondensi lewat e-mail dan siap bertransaksi secara online."

"Majalah Warta Ekonomi (edisi No.25/XIII/25 Juni 2001) menulis bahwa 30% perusahaan UKM di wilayah Jabotabek telah menggunakan website sebagai media promosi mereka."

Internet sudah mulai dimanfaatkan sebagai media pemasaran baik oleh perusahaan besar maupun kecil. 

Dan, melalui email ini, kami ingin memperkenalkan kepada Anda sebuah perusahaan kecil yang menjalankan bisnisnya hanya melalui internet. Dan, bagaimana Anda juga bisa berperan dalam perusahaan ini serta mendapatkan penghasilan yang bagus.

PROYEKSI PENGHASILAN ANDA

Perusahaan ini menjual produknya seharga Rp.70.000 dan Anda diberikan komisi 50% atau Rp.35.000 untuk setiap penjualan. 

Berapa besarkah penghasilan yang bisa Anda peroleh dalam sebulan? Sebenarnya tidak ada batasan, semuanya tergantung pada usaha dan kemauan Anda.

Sebagai perkiraan, silahkan Anda menyimak proyeksi dibawah ini: 
1 penjualan/ hari	= Rp. 1.050.000/ bulan
2 penjualan/ hari	= Rp. 2.100.000/ bulan
5 penjualan/ hari	= Rp. 5.250.000/ bulan

Sebenarnya, kalau Anda bisa menjual sebuah saja dalam sehari dan mendapatkan Rp.1.050.000 sudah sangat lumayan, bukan? Apalagi kalau …..?


PRODUK YANG PASTI LAKU DIJUAL

Produk yang akan Anda promosikan adalah sebuah paket informasi & software. Produk intinya adalah sebuah software (39 links) yang mampu melipat-gandakan kecepatan kerja sebuah komputer. Pengguna komputer akan sangat menghargai software ini. Dan, ada banyak sekali pengguna komputer sekarang. Asal Anda bisa menjelaskan dengan baik manfaat produk ini, kemungkinan besar mereka akan membeli. 

Dalam produk unggulan ini, Anda juga akan menemukan ratusan tips komputer. Pengguna komputer juga akan sangat mengharga tips-tips ini karena bisa membantu mereka semakin mahir menggunakan komputer baik untuk bekerja maupun untuk hiburan.

Dan, produk ini juga menyertakan informasi bagaimana cara mendapatkan software apapun secara gratis di internet. Mereka yang suka berselancar di internet tahu bahwa software di internet dijual dengan harga mahal. Banyak pecandu internet akan senang apabila diberitahu alamat situs dimana semua software bisa diperoleh secara gratis. Anda akan dengan mudah menjual informasi ini kepada mereka.


BIAYA MENGIKUTI BISNIS ONLINE INI

Berapa biaya yang harus Anda keluarkan untuk mengikuti program ini? Tidak ada! Tetapi, Anda  perlu membeli produk tersebut untuk dipelajari. Anda hanya bisa mempromosikan sesuatu yang Anda tahu dengan baik. Download software tersebut dan dipakai. Lihat bagaimana ia melipat-gandakan kecepatan kerja komputer Anda, kecepatan sambungan ke internet, dan lain-lain. Harganya hanya Rp.70.000! Jangan khawatir dengan angka kecil ini. Modal Anda sudah kembali dengan melakukan dua penjualan. Selanjutnya, setiap penjualan adalah keuntungan bersih Anda.

Kami juga akan mengajari Anda bagaimana melakukan promosi melalui internet. Kami akan berikan contoh naskah iklan yang bisa Anda kirimkan ke teman-teman. Kami akan tunjukkan di mana Anda bisa memasang iklan secara gratis di internet. Kami bahkan akan memberi Anda sebuah software pengirim email massal secara gratis. Kami ingin Anda berhasil.


JANGAN MENUNGGU! MULAI BISNIS INI SEKARANG JUGA!

Apakah Anda akan sia-siakan kesempatan ini? Kunjungi situs kami dan Anda pasti akan terkesan dan TERTARIK!

Sekarang silahkan kirim sebuah email ke infopenting@GetResponse.com dan dalam waktu 30 detik, Anda akan mendapatkan informasi lengkap untuk memulai bisnis internet ini.


Salam Hangat,

Henry Lienardi




From robt@pacificcodeworks.com Wed Feb 26 10:42:35 2003
Received: with ECARTIS (v1.0.0; list kdb); Wed, 26 Feb 2003 10:42:44 -0800 (PST)
Received: from mail.pacificcodeworks.com (mail.pacificcodeworks.com [205.179.60.130])
	by oss.sgi.com (8.12.5/8.12.5) with SMTP id h1QIgW3v011146
	for <kdb@oss.sgi.com>; Wed, 26 Feb 2003 10:42:33 -0800
Received: from mail.pacificcodeworks.com by mail.pacificcodeworks.com
          id aa22367; 26 Feb 2003 10:38 PST
Message-ID: <3E5D0B5B.7070705@PacificCodeWorks.com>
Date: Wed, 26 Feb 2003 10:45:47 -0800
From: Rob Tarte <robt@pacificcodeworks.com>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.0.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: kdb@oss.sgi.com
Subject: KDB_REASON_CALL
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-archive-position: 261
X-ecartis-version: Ecartis v1.0.0
Sender: kdb-bounce@oss.sgi.com
Errors-to: kdb-bounce@oss.sgi.com
X-original-sender: robt@pacificcodeworks.com
Precedence: bulk
X-list: kdb

Hi,

It seems that KDB_REASON_CALL doesn't give a stack backtrace anymore.
I noticed kdb_local() used to build a register context with functions 
like kdb_getcurrentframe()
and kdba_setpc().  Now the code just says "kdb() called with no 
registers, restricted function".
Any particular reason?  Do I have the wrong patch?

I have applied the following patches to the linux-2.4.20 tree:

kdb-v2.5-2.4.20-common-1
kdb-v2.5-2.4.20-i386-1

BTW.  Great work on the debugger.

Thanks,

Rob

-- 
Rob Tarte
Pacific CodeWorks
1347 Pacific Ave., Suite 202
Santa Cruz, CA 95060
(p) 831-426-7582
(f) 831-426-7584



From kaos@sgi.com Wed Feb 26 16:23:53 2003
Received: with ECARTIS (v1.0.0; list kdb); Wed, 26 Feb 2003 16:23:58 -0800 (PST)
Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101])
	by oss.sgi.com (8.12.5/8.12.5) with SMTP id h1R0Nq3v021182
	for <kdb@oss.sgi.com>; Wed, 26 Feb 2003 16:23:52 -0800
Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130])
	by zok.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with SMTP id h1R0NiKp001642
	for <kdb@oss.sgi.com>; Wed, 26 Feb 2003 16:23:45 -0800
Received: from kao2.melbourne.sgi.com (kao2.melbourne.sgi.com [134.14.55.180]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id LAA04120; Thu, 27 Feb 2003 11:22:28 +1100
Received: by kao2.melbourne.sgi.com (Postfix, from userid 16331)
	id 7F6DC3000B8; Thu, 27 Feb 2003 11:22:27 +1100 (EST)
Received: from kao2.melbourne.sgi.com (localhost [127.0.0.1])
	by kao2.melbourne.sgi.com (Postfix) with ESMTP
	id 484628F; Thu, 27 Feb 2003 11:22:27 +1100 (EST)
X-Mailer: exmh version 2.4 06/23/2000 with nmh-1.0.4
From: Keith Owens <kaos@sgi.com>
To: Rob Tarte <robt@PacificCodeWorks.com>
Cc: kdb@oss.sgi.com
Subject: Re: KDB_REASON_CALL 
In-reply-to: Your message of "Wed, 26 Feb 2003 10:45:47 -0800."
             <3E5D0B5B.7070705@PacificCodeWorks.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 27 Feb 2003 11:22:21 +1100
Message-ID: <9768.1046305341@kao2.melbourne.sgi.com>
X-archive-position: 262
X-ecartis-version: Ecartis v1.0.0
Sender: kdb-bounce@oss.sgi.com
Errors-to: kdb-bounce@oss.sgi.com
X-original-sender: kaos@sgi.com
Precedence: bulk
X-list: kdb

On Wed, 26 Feb 2003 10:45:47 -0800, 
Rob Tarte <robt@PacificCodeWorks.com> wrote:
>It seems that KDB_REASON_CALL doesn't give a stack backtrace anymore.
>I noticed kdb_local() used to build a register context with functions 
>like kdb_getcurrentframe()
>and kdba_setpc().  Now the code just says "kdb() called with no 
>registers, restricted function".
>Any particular reason?  Do I have the wrong patch?

For i386, kdb can sort of generate a stack frame, but it was always
flakey.  For ia64 it is not possible to generate a stack frame from
REASON_CALL.  Trying to support an environment without struct pt_regs
was causing lots of kdb problems and bugs, so I dropped the support.  I
strongly recommend that yoiu use KDB_ENTER() instead.  That generates
an interrupt and has registers.


From edie.dong@intel.com Fri Feb 28 00:47:32 2003
Received: with ECARTIS (v1.0.0; list kdb); Fri, 28 Feb 2003 00:47:36 -0800 (PST)
Received: from hermes.jf.intel.com (fmr05.intel.com [134.134.136.6])
	by oss.sgi.com (8.12.5/8.12.5) with SMTP id h1S8lSeA002439
	for <kdb@oss.sgi.com>; Fri, 28 Feb 2003 00:47:28 -0800
Received: from petasus.jf.intel.com (petasus.jf.intel.com [10.7.209.6])
	by hermes.jf.intel.com (8.11.6/8.11.6/d: outer.mc,v 1.51 2002/09/23 20:43:23 dmccart Exp $) with ESMTP id h1S7GHp13253
	for <kdb@oss.sgi.com>; Fri, 28 Feb 2003 07:16:17 GMT
Received: from pdsmsxvs01.pd.intel.com (pdsmsxvs01.pd.intel.com [172.16.12.122])
	by petasus.jf.intel.com (8.11.6/8.11.6/d: inner.mc,v 1.28 2003/01/13 19:44:39 dmccart Exp $) with SMTP id h1S7ETH02403
	for <kdb@oss.sgi.com>; Fri, 28 Feb 2003 07:14:30 GMT
Received: from pdsmsx17.pd.intel.com ([172.16.12.121])
 by pdsmsxvs01.pd.intel.com (NAVGW 2.5.2.11) with SMTP id M2003022815180929728
 for <kdb@oss.sgi.com>; Fri, 28 Feb 2003 15:18:10 +0800
Received: by pdsmsx17.pd.intel.com with Internet Mail Service (5.5.2653.19)
	id <FZRXDK56>; Fri, 28 Feb 2003 15:16:53 +0800
Message-ID: <957BD1C2BF3CD411B6C500A0C944CA26032998EC@pdsmsx32.pd.intel.com>
From: "Dong, Edie" <edie.dong@intel.com>
To: kdb@oss.sgi.com
Subject: multiple breakpoint at same place
Date: Fri, 28 Feb 2003 15:15:53 +0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="gb2312"
X-archive-position: 263
X-ecartis-version: Ecartis v1.0.0
Sender: kdb-bounce@oss.sgi.com
Errors-to: kdb-bounce@oss.sgi.com
X-original-sender: edie.dong@intel.com
Precedence: bulk
X-list: kdb

Hi,
     If set multiple breapoint at same address, kdb will fail to go through
this
point. Disable multiple break at same address is easy to implement, is there
any special consideration for this problem?
eddie

From kitaplist@yahoo.com Fri Feb 28 06:34:38 2003
Received: with ECARTIS (v1.0.0; list kdb); Fri, 28 Feb 2003 06:34:46 -0800 (PST)
Received: from mega1 ([212.253.69.186])
	by oss.sgi.com (8.12.5/8.12.5) with SMTP id h1SEYGeB019952
	for <kdb@oss.sgi.com>; Fri, 28 Feb 2003 06:34:34 -0800
Date: Fri, 28 Feb 2003 06:34:34 -0800
Message-Id: <200302281434.h1SEYGeB019952@oss.sgi.com>
From: kitaplist@yahoo.com
Subject: www.ilrehberi.com FIRMANIZI KAYDEDINIZ
To: kdb@oss.sgi.com
Content-Type: text/plain;
	charset="US-ASCII";
	charset="US-ASCII";
X-archive-position: 264
X-ecartis-version: Ecartis v1.0.0
Sender: kdb-bounce@oss.sgi.com
Errors-to: kdb-bounce@oss.sgi.com
X-original-sender: kitaplist@yahoo.com
Precedence: bulk
X-list: kdb

 charset="US-ASCII";
	charset="US-ASCII";
	charset="US-ASCII";
	charset="US-ASCII"
Reply-To: kitaplist@yahoo.com
Date: Fri, 28 Feb 2003 16:34:26 +0200
X-Priority: 3
X-Library: Indy 9.00.10
X-Mailer: Foxmail


 FIRMANIZI KOLAYCA KAYDEDINIZ

http://www.ilrehberi.com

http://www.sectorguide.com

Turkiye e-mal portfuyune sahip olmak için,

http://www.mailrehberi.com

tesekkurler

From kaos@sgi.com Fri Feb 28 06:46:21 2003
Received: with ECARTIS (v1.0.0; list kdb); Fri, 28 Feb 2003 06:46:25 -0800 (PST)
Received: from mail.ocs.com.au (mail.ocs.com.au [203.34.97.2])
	by oss.sgi.com (8.12.5/8.12.5) with SMTP id h1SEkIeA020422
	for <kdb@oss.sgi.com>; Fri, 28 Feb 2003 06:46:20 -0800
Received: (qmail 2340 invoked from network); 28 Feb 2003 14:46:15 -0000
Received: from ocs3.intra.ocs.com.au (192.168.255.3)
  by mail.ocs.com.au with SMTP; 28 Feb 2003 14:46:15 -0000
Received: by ocs3.intra.ocs.com.au (Postfix, from userid 16331)
	id 908CD3001F4; Sat,  1 Mar 2003 01:46:10 +1100 (EST)
Received: from ocs3.intra.ocs.com.au (localhost [127.0.0.1])
	by ocs3.intra.ocs.com.au (Postfix) with ESMTP id 680EC8F
	for <kdb@oss.sgi.com>; Sat,  1 Mar 2003 01:46:10 +1100 (EST)
X-Mailer: exmh version 2.4 06/23/2000 with nmh-1.0.4
From: Keith Owens <kaos@sgi.com>
To: kdb@oss.sgi.com
Subject: Re: multiple breakpoint at same place 
In-reply-to: Your message of "Fri, 28 Feb 2003 15:15:53 +0800."
             <957BD1C2BF3CD411B6C500A0C944CA26032998EC@pdsmsx32.pd.intel.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 01 Mar 2003 01:46:05 +1100
Message-ID: <2711.1046443565@ocs3.intra.ocs.com.au>
X-archive-position: 265
X-ecartis-version: Ecartis v1.0.0
Sender: kdb-bounce@oss.sgi.com
Errors-to: kdb-bounce@oss.sgi.com
X-original-sender: kaos@sgi.com
Precedence: bulk
X-list: kdb

On Fri, 28 Feb 2003 15:15:53 +0800, 
"Dong, Edie" <edie.dong@intel.com> wrote:
>     If set multiple breapoint at same address, kdb will fail to go through
>this
>point. Disable multiple break at same address is easy to implement, is there
>any special consideration for this problem?

kdb v3.0 refuses multiple breakpoints at the same address.