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]> :c
PCI-device: pci1106,[EMAIL PROTECTED], hci13940
hci13940 is /[EMAIL PROTECTED],0/pci1106,[EMAIL PROTECTED]
Here the machine hangs infinitely and I am unable to go into
kmdb via ~# from tip.
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 by the
model range we specify).
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 breakpoint for each cpu - repeat for each.
If that fails as before then we know I'm barking up the wrong tree
with our NB config stuff. If it does boot then we can do some more
thinking on the next steps. I'd suggest maybe we nop out the
call to ao_pcicfg_write made from ao_nb_cfg - then we can see what
value the BIOS had installed (ao_nb_cfg reads and preserves that)
and not overwrite it at all.
Cheers
Gavin
_______________________________________________
opensolaris-discuss mailing list
[email protected]
