Eric Saxe wrote:
> Dennis Clarke wrote:
>
>>> Dennis, was this an Intel or AMD based system?
>>>
>>>
>> Actually neither .. it is a low power appliance motherboard based on VIA
>> technology.
>>
>>
> I see. If you can provide me access to a crash dump somehow, that would
> b
> Dennis Clarke wrote:
>>> Dennis Clarke wrote:
>>>
This seems to be an opportunity to employ some code early in the boot
phase
and to perhaps print out some debugging info at that time.
The question is .. where and what to debug.
>>> Can you send me the output o
Dennis Clarke wrote:
>> Dennis Clarke wrote:
>>
>>> This seems to be an opportunity to employ some code early in the boot
>>> phase
>>> and to perhaps print out some debugging info at that time.
>>>
>>> The question is .. where and what to debug.
>>>
>>>
>> Can you send me the output of
> Dennis Clarke wrote:
>> This seems to be an opportunity to employ some code early in the boot
>> phase
>> and to perhaps print out some debugging info at that time.
>>
>> The question is .. where and what to debug.
>>
> Can you send me the output of:
>
> # echo "cpuid_info0::print" | mdb -k
# e
Dennis Clarke wrote:
> This seems to be an opportunity to employ some code early in the boot phase
> and to perhaps print out some debugging info at that time.
>
> The question is .. where and what to debug.
>
Can you send me the output of:
# echo "cpuid_info0::print" | mdb -k
Those are the te
> Dennis Clarke wrote:
>>> Jürgen Keil wrote:
> cpu0: x86 (CentaurHauls 6A9 family 6 model 10 step 9 clock 1200 MHz)
> cpu0: VIA Esther processor 1200MHz
>
Could be missing / broken or incomplete VIA/CentaurHauls x86 cpu
support:
>>> I'm suspecting that you are correct J
Dennis Clarke wrote:
>> Jürgen Keil wrote:
cpu0: x86 (CentaurHauls 6A9 family 6 model 10 step 9 clock 1200 MHz)
cpu0: VIA Esther processor 1200MHz
>>> Could be missing / broken or incomplete VIA/CentaurHauls x86 cpu support:
>>>
>> I'm suspecting that you are correct Jürgen. Accordin
> Jürgen Keil wrote:
>>
>>> cpu0: x86 (CentaurHauls 6A9 family 6 model 10 step 9 clock 1200 MHz)
>>> cpu0: VIA Esther processor 1200MHz
>>>
>>
>> Could be missing / broken or incomplete VIA/CentaurHauls x86 cpu support:
>>
> I'm suspecting that you are correct Jürgen. According to:
> http://en
Jürgen Keil wrote:
>
>> cpu0: x86 (CentaurHauls 6A9 family 6 model 10 step 9 clock 1200 MHz)
>> cpu0: VIA Esther processor 1200MHz
>>
>
> Could be missing / broken or incomplete VIA/CentaurHauls x86 cpu support:
>
I'm suspecting that you are correct Jürgen. According to:
http://en.wi
Dennis Clarke wrote:
>> Dennis, was this an Intel or AMD based system?
>>
>
> Actually neither .. it is a low power appliance motherboard based on VIA
> technology.
>
I see. If you can provide me access to a crash dump somehow, that would
be helpful. Otherwise, if you can reproduce this...
> Eric Saxe wrote:
>> Dennis Clarke wrote:
>>
Hmm, startup_memlist+3f5 passes these as parameters to
page_coloring_init(),
so if we trust the parameters shown in the stack backtrace, we have
pagecolor_memsz =
page_coloring_init(l2cache_sz, l2cache_
> Dennis Clarke wrote:
>>> Hmm, startup_memlist+3f5 passes these as parameters to
>>> page_coloring_init(),
>>> so if we trust the parameters shown in the stack backtrace, we have
>>>
>>> pagecolor_memsz =
>>> page_coloring_init(l2cache_sz, l2cache_linesz,
>>> l2cache_assoc);
>
Eric Saxe wrote:
> Dennis Clarke wrote:
>
>>> Hmm, startup_memlist+3f5 passes these as parameters to page_coloring_init(),
>>> so if we trust the parameters shown in the stack backtrace, we have
>>>
>>> pagecolor_memsz =
>>> page_coloring_init(l2cache_sz, l2cache_linesz, l2ca
Dennis Clarke wrote:
>> Hmm, startup_memlist+3f5 passes these as parameters to page_coloring_init(),
>> so if we trust the parameters shown in the stack backtrace, we have
>>
>> pagecolor_memsz =
>> page_coloring_init(l2cache_sz, l2cache_linesz, l2cache_assoc);
>>
>>fec3
> Gavin wrote:
>> On 07/07/07 18:55, Dennis Clarke wrote:
>> > after BFU of snv_68 :
>> >
>> > module /platform/i86pc/kernel//unix: text at [0xfe80, 0xfe8d4a8b]
>> data at 0xfec0
>> > module /kernel/genunix: text at [0xfe8d4a90, 0xfead88ff] data at
>> 0xfec4cdc0
>> >
>> > panic[cpu0]/threa
Gavin wrote:
> On 07/07/07 18:55, Dennis Clarke wrote:
> > after BFU of snv_68 :
> >
> > module /platform/i86pc/kernel//unix: text at [0xfe80, 0xfe8d4a8b] data
> > at 0xfec0
> > module /kernel/genunix: text at [0xfe8d4a90, 0xfead88ff] data at 0xfec4cdc0
> >
> > panic[cpu0]/thread=fec1f2e
>
>
> On 07/07/07 18:55, Dennis Clarke wrote:
>> after BFU of snv_68 :
>>
>> module /platform/i86pc/kernel//unix: text at [0xfe80, 0xfe8d4a8b] data
>> at 0xfec0
>> module /kernel/genunix: text at [0xfe8d4a90, 0xfead88ff] data at
>> 0xfec4cdc0
>>
>> panic[cpu0]/thread=fec1f2e0: assertion fa
On 07/07/07 18:55, Dennis Clarke wrote:
> after BFU of snv_68 :
>
> module /platform/i86pc/kernel//unix: text at [0xfe80, 0xfe8d4a8b] data
> at 0xfec0
> module /kernel/genunix: text at [0xfe8d4a90, 0xfead88ff] data at 0xfec4cdc0
>
> panic[cpu0]/thread=fec1f2e0: assertion failed: l2c
> after BFU of snv_68 :
>
> module /platform/i86pc/kernel//unix: text at [0xfe80, 0xfe8d4a8b] data at
> 0xfec0
> module /kernel/genunix: text at [0xfe8d4a90, 0xfead88ff] data at 0xfec4cdc0
>
> panic[cpu0]/thread=fec1f2e0: assertion failed: l2cache_assoc ?
> (l2cache_sz / l2cache_ass
after BFU of snv_68 :
module /platform/i86pc/kernel//unix: text at [0xfe80, 0xfe8d4a8b] data
at 0xfec0
module /kernel/genunix: text at [0xfe8d4a90, 0xfead88ff] data at 0xfec4cdc0
panic[cpu0]/thread=fec1f2e0: assertion failed: l2cache_assoc ?
(l2cache_sz / l2cache_assoc) : 0x1000)) &
20 matches
Mail list logo
