On Mon, 4 Feb 2008, Dennis Clarke wrote: [ ... ] >> Hi Dennis, >> >> Best would be not only to boot kmdb, but also to use the "-ad" boot >> options to have kmdb prompt you. > > I must recall how to do that. I think one must simple edit the GRUB menu.lst > entry and specify -kad -B console=ttya or something like that.
Yes. > >> When unix/genunix is loaded, set "kmem_flags" to 0xf via >> >> kmem_flags/W f > > well .. if I look here : > > panic[cpu1]/thread=d3738de0: kernel heap corruption detected > > d3738cc0 genunix:kmem_error+416 (6, d3036030, d36f24) > d3738cf0 genunix:kmem_slab_free+21a (d3036030, d36f2400) > d3738d20 genunix:kmem_magazine_destroy+b9 (d3036030, d459ed80,) > d3738d58 genunix:kmem_cache_magazine_purge+8d (d3036030) > d3738d78 genunix:kmem_cache_magazine_resize+23 (d3036030, 0, 0, 0, ) > d3738dc8 genunix:taskq_thread+176 (d36d8f08, 0) > d3738dd8 unix:thread_start+8 () > > I see kmem_slab_free there and I'm guessing that this page will help: > > http://docs.sun.com/app/docs/doc/817-2543/modules-24?l=en&q=kmem_flags&a=view > > The dcmd ::kmem_log seems reasonable .. if i can get to that point. Will only tell you what you need if you had kmem_flags set. Are you trying to install a debug build ? If so, kmem debugging active is the case by default. Good luck! FrankH. _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
