Hi,

On 03/24/08 15:51, Emmanuel De Paepe wrote:
It seems that I'm not alone with this issue.

Is your other machine also using an 'ASUS' motherboard or is it another 
manufacturer?

Because I see both our machines have the same CPU (Q6600), the same amount of 
RAM (4GB) and the same brand of motherboard: ASUS (P5KR and T3P5G965)

I see one big difference between Solaris 10 and SXDE:
When it is not going into poweroff after an 'init 5' a single short push on the 
power button suffices for Solaris 10. For SXDE I have to push the button for 
several seconds to switch the computer off.

For my old AMD sempron Packard Bell PC I don't see any issues, at least not for 
Solaris 10.

I believe the final power off request, assuming we get to the point of making
that request, will be made via ACPI.  I suspect Solaris performs the
same steps for all boards that support ACPI, so while this could
be a Solaris bug I'd suggest a first step would be to try any
available BIOS update.

I'd also suggest booting with the kernel debugger loaded - add -k to the
grub line in /boot/grub/menu.lst:

        title snv_86
        root (hd0,0,a)
        kernel$ /platform/i86pc/kernel/$ISADIR/unix -k
        module$ /platform/i86pc/$ISADIR/boot_archive

On shutdown (and only once you're at vga text mode - don't do this
while X is running) if it fails to poweroff after apparently
running all shutdown methods then drop into the debugger
with F1-A and see what ::cpuinfo says (likely that the
idle loop is running - we're waiting for something
to complete).  It would also be interesting to do
a $c to see the current stack, a ::ptree to see that
all but a few processes are gone, and if some non-system
ones (not sched etc) are hanging around then
::threadlist -v so we can see all their stacks.
Without a serial console you will, unfortunately,
have to note down what appears to be pertinent output.

Cheers

Gavin

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
opensolaris-discuss mailing list
[email protected]

Reply via email to