Re: Announce: kdb v4.4 is available for kernel 2.6.16

Keith Owens <[email protected]>
Newsgroups gmane.linux.ports.ia64,gmane.linux.kernel.debugging,gmane.linux.kernel
Message-ID <[email protected]>
Keith Owens (on Tue, 21 Mar 2006 16:59:24 +1100) wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>KDB (Linux Kernel Debugger) has been updated for kernel 2.6.16.
>
>ftp://oss.sgi.com/projects/kdb/download/v4.4/
>ftp://ftp.ocs.com.au/pub/mirrors/oss.sgi.com/projects/kdb/download/v4.4/
>
>Note:  Due to a spam attack, the [email protected] mailing list is now
>subscriber only.  If you reply to this mail, you may wish to trim
>[email protected] from the cc: list.

Updates to kdb v4.4-2.6.16-{common,i386,ia64}-1, moving to -2.  Mainly
to get more forceful with stuck cpus on IA64, where the "non-maskable"
interrupt is masked by local_irq_disable().

We finally get decent backtraces on stuck IA64 cpus.  It took a long
time to get there, KDB could not change until the base kernel could
cope with INIT and recover correctly.

2006-03-22 Keith Owens  <[email protected]>

	* Add some more xpc flags.  Dean Nelson, SGI.
	* Replace open coded counter references with atomic_read().
	* Pass early_uart_console to early_uart_setup().  Francois
	  Wellenreiter, Bull.
	* Replace open code with for_each_online_cpu().
	* If cpus do not come into kdb after a few seconds then let
	  architectures send a more forceful interrupt.
	* Close a timing race with KDB_ENTER_SLAVE.
	* kdb v4.4-2.6.16-common-2.

2006-03-24 Keith Owens  <[email protected]>

	* Define a dummy kdba_wait_for_cpus().
	* kdb v4.4-2.6.16-i386-2.

2006-03-24 Keith Owens  <[email protected]>

	* Use INIT to interrupt cpus that do not respond to a normal kdb IPI.
	* Remove KDBA_MCA_TRACE from arch/ia64/kernel/mca.c.
	* kdb v4.4-2.6.16-ia64-2.

-
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.