Gavin Maltby <[EMAIL PROTECTED]> wrote:
> On 07/31/06 00:08, Joerg Schilling wrote:
>
> > While this patch did not help, I am now able to boot the newer Solaris
> > kernels on this system.
> >
> > What I did:
> >
> > I did replace the 2 Opteron 242 by 2 Opteron 275 borrowed from AMD.
> >
> > So
On 07/31/06 00:08, Joerg Schilling wrote:
While this patch did not help, I am now able to boot the newer Solaris
kernels on this system.
What I did:
I did replace the 2 Opteron 242 by 2 Opteron 275 borrowed from AMD.
So it looks like newer Solaris versions have problems with older
Opteron chi
Joerg Schilling <[EMAIL PROTECTED]> wrote:
> Hi Gavin,
...
> > boot kmdb -d as before
> >
> > set breakpoint at module init:
> >
> > ::bp cpu.AuthenticAMD.15`ao_init
> >
> > when the breakpoint triggers change the model limit from 0x40 to 0x0
> >
> > ao_model_limit/W0
> >
> > You'll hit that break
Hi Gavin,
sorry for the long delay.
Gavin Maltby <[EMAIL PROTECTED]> wrote:
> Hi Joerg,
>
> On 05/30/06 23:51, Joerg Schilling wrote:
> [cut]
> > kmdb: stop at cpu.AuthenticAMD.15`ao_nb_cfg
> > kmdb: target stopped at:
> > cpu.AuthenticAMD.15`ao_nb_cfg: pushl %ebp
> > [1]> ao_nb_cfg_add/X
> >
Gavin Maltby <[EMAIL PROTECTED]> wrote:
> OK let's try divide-and-conquer at a higher level. We'll stop the
> cpu.AuthenticAMD.15 module from initializing thereby forcing us
> to fall back to the generic cpu module (as used on Intel cpus
> and any AMD family 0xf systems not explicitly supported b
Joerg Schilling <[EMAIL PROTECTED]> wrote:
> Gavin Maltby <[EMAIL PROTECTED]> wrote:
>
> > if the BIOS enabled it) do the following from kmdb:
> >
> > boot kmdb -d
> > ::bp cpu.AuthenticAMD.15`ao_nb_cfg - add breakpoint
> > :c - wait for breakpoint to hit
> > ao_nb_cfg_add/X - confirm current valu
Gavin Maltby <[EMAIL PROTECTED]> wrote:
> On 05/30/06 22:14, Joerg Schilling wrote:
> >>> The machine currently runs fine with Build 30.
> >> Hmmm, it sounds like you have a memory dimm producing
> >> an uncorrectable ECC error and prior to build 34 the
> >
> > This is most unlikely as the machi
On 05/30/06 22:14, Joerg Schilling wrote:
Gavin Maltby <[EMAIL PROTECTED]> wrote:
Joerg Schilling wrote:
The machine currently runs fine with Build 30.
Hmmm, it sounds like you have a memory dimm producing
an uncorrectable ECC error and prior to build 34 the
This is most unlikely as the ma
Hi Joerg,
On 05/30/06 23:51, Joerg Schilling wrote:
[cut]
kmdb: stop at cpu.AuthenticAMD.15`ao_nb_cfg
kmdb: target stopped at:
cpu.AuthenticAMD.15`ao_nb_cfg: pushl %ebp
[1]> ao_nb_cfg_add/X
cpu.AuthenticAMD.15`ao_nb_cfg_add:
cpu.AuthenticAMD.15`ao_nb_cfg_add: a000105
[1]>
Gavin Maltby <[EMAIL PROTECTED]> wrote:
> if the BIOS enabled it) do the following from kmdb:
>
> boot kmdb -d
> ::bp cpu.AuthenticAMD.15`ao_nb_cfg - add breakpoint
> :c - wait for breakpoint to hit
> ao_nb_cfg_add/X - confirm current value is 0xa05
> - we bitwise-or 0x100 int
Hi
On 05/30/06 23:18, Joerg Schilling wrote:
Gavin Maltby <[EMAIL PROTECTED]> wrote:
ereport.cpu.amd.dc.inf_l2_ecc1 ena=114f86052e1 detector=[ version=0 scheme=
So this is not an external ECC error but an CPU internal problem?
Yes. One event in isolation is nothing to worry about.
Gavin Maltby <[EMAIL PROTECTED]> wrote:
> > ereport.cpu.amd.dc.inf_l2_ecc1 ena=114f86052e1 detector=[ version=0
> > scheme=
> > "hc" hc-list=[...] ] bank-status=d4514136 bank-number=0
> > addr=c83bb80
> > addr-valid=1 syndrome=a2 syndrome-type="E" ip=0 privileged=1
>
> That's a si
On 05/30/06 22:14, Joerg Schilling wrote:
- boot kmdb -d and before starting up do
- ::bp cpu.AuthenticAMD.15`ao_mca_init
Before doing this test, I would like to
show a stack trace that did take me a day to produce
as usually the machine just hangs for 5 seconds and then
reboots from
Gavin Maltby <[EMAIL PROTECTED]> wrote:
> Joerg Schilling wrote:
>
> > The machine currently runs fine with Build 30.
>
> Hmmm, it sounds like you have a memory dimm producing
> an uncorrectable ECC error and prior to build 34 the
This is most unlikely as the machine still does not
produce and pr
Gavin Maltby <[EMAIL PROTECTED]> wrote:
> Joerg Schilling wrote:
>
> > The machine currently runs fine with Build 30.
>
> Hmmm, it sounds like you have a memory dimm producing
> an uncorrectable ECC error and prior to build 34 the
> detector/disposition were not enabled/correct so
> you got away w
Joerg Schilling wrote:
The machine currently runs fine with Build 30.
Hmmm, it sounds like you have a memory dimm producing
an uncorrectable ECC error and prior to build 34 the
detector/disposition were not enabled/correct so
you got away with it. Try disabling ECC if the bios
allows, or enab
Gavin Maltby <[EMAIL PROTECTED]> wrote:
> Joerg Schilling wrote:
>
> > I did just try to install the SX Build 39 DVD on my Dual Opteron (2x 242)
> > PC with MSI K8T Master2-FAR7 board.
> >
> > When booting in -v mode, the last thing I see is the
> >
> > cpumod: Authentic AMD
> >
> >
Joerg Schilling wrote:
I did just try to install the SX Build 39 DVD on my Dual Opteron (2x 242)
PC with MSI K8T Master2-FAR7 board.
When booting in -v mode, the last thing I see is the
cpumod: Authentic AMD
message and then stops for a while and reboots. Booting with -kv
does not re
Hi,
I did just try to install the SX Build 39 DVD on my Dual Opteron (2x 242)
PC with MSI K8T Master2-FAR7 board.
When booting in -v mode, the last thing I see is the
cpumod: Authentic AMD
message and then stops for a while and reboots. Booting with -kv
does not result in a jump
19 matches
Mail list logo
