http://defect.opensolaris.org/bz/show_bug.cgi?id=6113
--- Comment #3 from J?rgen Keil <jk at tools.de> 2009-01-15 07:35:06 --- (In reply to comment #2) > When you mentioned snv_106, are you meaning onnv_106 tag in the ON source > tree? It is an SX:CE 104 install, which i bfu'ed to post onnv_105 bits (but not yet the final onnv_106), compiled from source. My set of ON sources also includes a few custom changes, but not in the area of the cpudrv module. I could bfu to nightly 2009-1-14, but I don't expect that the panic would change much. I think I also got this panic on older releases than build 106, so this shouldn't be a new issue in build 106. > If so, I saw the different code path from yours. > > main() > -> cpupm_post_startup() > ----> cpupm_init_topspeed() -> ppm_init_topspeed() > ------> ppm_redefine_topspeed() -> ... Hmm, no, I see main() --> cpupm_port_startup() ----> ppm`ppm_init_topspeed() ------> ppm`ppm_redefine_topspeed() --------> ppm`ppm_set_topspeed() ----------> cpudrv`cpudrv_pm_set_topspeed(ctx = XXXX, plat_level = 6) It seems that the loop in cpudrv_pm_set_topspeed() is unable to find the correct cpudrv_pm_spd_t entry that matches plat_level / pm_level... -- Configure bugmail: http://defect.opensolaris.org/bz/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
