[src/netbsd-2-0]: src/doc Process tickets:

[jdc <jdc%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/d8daa775bb32
branches:  netbsd-2-0
changeset: 564656:d8daa775bb32
user:      jdc <jdc%NetBSD.org@localhost>
date:      Fri Jan 07 16:00:57 2005 +0000

description:
Process tickets:
        #1030 - prevent panics on DIAGNOSTIC kernels
        #1043 - xen fixes for idle state
        #1045 - xen fixes for halt

diffstat:

 doc/CHANGES-2.0.1 |  32 +++++++++++++++++++++++++++++++-
 1 files changed, 31 insertions(+), 1 deletions(-)

diffs (43 lines):

diff -r 356dae574c79 -r d8daa775bb32 doc/CHANGES-2.0.1
--- a/doc/CHANGES-2.0.1 Fri Jan 07 15:57:27 2005 +0000
+++ b/doc/CHANGES-2.0.1 Fri Jan 07 16:00:57 2005 +0000
@@ -1,4 +1,4 @@
-#      $NetBSD: CHANGES-2.0.1,v 1.1.2.3 2005/01/07 15:02:26 jdc Exp $
+#      $NetBSD: CHANGES-2.0.1,v 1.1.2.4 2005/01/07 16:00:57 jdc Exp $
 
 A complete list of changes from the NetBSD 2.0 release to the NetBSD 2.0.1 
 release.
@@ -76,3 +76,33 @@
        PR#28486.
        [hira, ticket #1029]
 
+sys/net/if_media.c                     1.23
+
+       As pointed out by Greg Troxel, ifmedia_entrys were allocated with
+       malloc_type M_IFADDR and freed with malloc_type M_DEVBUF.  This
+       causes a panic(9) in DIAGNOSTIC kernels.  Add malloc_type M_IFMEDIA
+       and use it for both malloc'ing and free'ing ifmedia_entrys.
+       [dyoung, ticket #1030]
+
+sys/arch/xen/i386/locore.S             1.7
+
+       HYPERVISOR_yield is one of the hypervisor calls that's "overloaded";
+       it does different things depending what's in %ebx.
+
+       We weren't setting %ebx here *at all*; so we did not get
+       SCHEDOP_yield, which was what was wanted; so unpredictable things
+       happened, notably immediate return to the NetBSD idle loop, in
+       other words spinning on CPU.
+
+       Michael Kukat caught this one and suggested this fix on port-xen.
+       [tls, ticket #1043]
+
+sys/arch/xen/i386/machdep.c            1.11
+
+       Terminate the domain on RB_HALT, not just on reboot.  This avoids
+       looping around a cngetc() that will never return while "halted",
+       which is rude, and which also requires domain 0 to not just restart
+       us, but kill us first.  Suggestion from Michael Kukat (though this
+       change is not the same as the one he suggested).
+       [tls, ticket #1045]
+