On Tue, 2006-07-11 at 14:08, Matty wrote: > On Tue, 11 Jul 2006, Michael Corcoran wrote: > > > Ryan, > > > > Without a corefile, it's hard to say for sure, but this exact stack back > > trace is also listed in CR 6315232 which was closed as a duplicate of > > 6223281 which was closed as a duplicate of 6286341 which made it into an > > earlier version of S10. > > > > I'm assuming it's impossible to get a core file? > > Hi Mike, > > Is there a procedure for getting a core file during the installation?
Good question. I asked around a bit and it seems like there's not a good way for doing this. The best suggestion I got was to run the install with kmdb enabled so that live debugging could take place. I'm a bit rusty about install, but I believe you can get a shell by either exiting out of the shell or starting up a terminal window, and then typing "mdb -K" in it would bring you to kmdb and a ":c" would continue and you could restart the install (possibly suninstall) to do the actual install which you expect to panic. Then when you panic, you'd be at kmdb and be able to do some live debugging. Of course debugging a problem like this probably isn't trivial and would take quite a bit of time. Other than that, this seems like a bit of a diagnosability problem which is easily worked around in house (letting the experts have access to the console of the machine to debug via kmdb) but will be hard for customers without (and often even with) kernel debugging skills to overcome. Anyone know if it'd be possible to setup a dedicated dump device during the install which you'd be able to get a core file off of by starting up another install, exiting out of the installer and running savecore (possibly with a few other needed commands)? > CentOS 4.0 installed and is running on the machine, so I am wondering > what the Solaris kernel didn't like about the hardware platform. Since the > box is now in production, I can't take it down to test things out. If you > want the motherboard and CPU information, I would be glad to provide it. > If you could send the motherboard and CPU information, that'd be great as we can try to see if anyone inside of Sun has a similar configuration or at least be aware of a possibility of a problem with this hardware config. Others may see this as well and at least we'd have more information which might be helpful. Thanks, Mike > Thanks for your reply, > - Ryan > -- > UNIX Administrator > http://daemons.net/~matty > > _______________________________________________ > opensolaris-code mailing list > [email protected] > http://mail.opensolaris.org/mailman/listinfo/opensolaris-code _______________________________________________ opensolaris-code mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
