> On Mon, 4 Feb 2008, Dennis Clarke wrote:
>>
>>> When unix/genunix is loaded, set "kmem_flags" to 0xf via
>>>
>>> kmem_flags/W f
OKay .. so CONTENTS|REDZONE|TEST|AUDIT == 0x8|0x4|0x2|0x1 == 0xf
gotcha ..
With moddebug I'll use 0xe000 for even more verbosity fun :-)
>> well .. if I look
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
:original error text
>> kernel memory allocator: buffer freed to wrong cache
>> buffer was allocated from kmem_alloc_320,
>> caller attempting free to kmem_alloc_8.
>> buffer=d36f2400 bufctl=0 cache: kmem_alloc_8
>>
>> panic[cpu1]/thread=d3738de0: kernel heap corruption detected
>>
>> d3738cc0 ge
Hi Dennis,
Best would be not only to boot kmdb, but also to use the "-ad" boot
options to have kmdb prompt you.
When unix/genunix is loaded, set "kmem_flags" to 0xf via
kmem_flags/W f
That'll allow better diagnosis, see the memory debugging section of the
modular debugger guide.
Bye,
With SXCE snv_81 this happens during install.
Here are the details :
1. Solaris Interactive (default)
2. Custom JumpStart
3. Solaris Interactive Text (Desktop session)
4. Solaris Interactive Text (Console session)
5. Apply driver updates
6. Single
