Hi,
If you are seeing the below stacktrace, then you are seeing this bug
6896160 Disabling driver via "-B disable-xxx=true" on grub boot line
results in panic
The workaround is simple
*Do not* use -B disable-xxxx
Instead do the following:
beadm mount <build127-BE> /mnt
<remove pcieb line from /mnt/etc/name_to_major>
bootadm update-archive -R /mnt
beadm unmount /mnt
and reboot
Vikram
ffffff01eaca5790 unix:die+e7 ()
ffffff01eaca58c0 unix:trap+19ff ()
ffffff01eaca58d0 unix:cmntrap+1ca ()
ffffff01eaca59d0 unix:strcmp+16 ()
ffffff01eaca5a00 genunix:in_drvwalk+3d ()
ffffff01eaca5a50 genunix:e_ddi_assign_instance+dc ()
ffffff01eaca5a90 genunix:init_node+24d ()
ffffff01eaca5ae0 genunix:i_ndi_config_node+139 ()
ffffff01eaca5b10 genunix:i_ndi_init_hw_children+56 ()
ffffff01eaca5b70 genunix:config_immediate_children+a3 ()
ffffff01eaca5bc0 genunix:devi_config_common+a6 ()
ffffff01eaca5c40 genunix:mt_config_thread+5d ()
ffffff01eaca5c50 unix:thread_start+8 ()
Then the bug is
Scott Gifford wrote:
Hi,
Thought I'd add my $.02 - same panic, different VMware platform.
I'm also seeing the same panic when booting 127 in a VM on ESX 4.0. The
virtual machine hardware version is 7 (like workstation).
I was running 126 fine by disabling the pcieb driver and just updated to 127
this morning. I checked the /etc/path_to_inst file and found no pcieb
references either. I didn't try the -a switch, but doubt it will work any
better for me.
Scott
--
===============================================================================
"What counts is not necessarily the size of the dog in the fight; it's the size of the fight in the dog." - Dwight D. Eisenhower
===============================================================================
_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
