Bug 141238

Created attachment 61889 [details]
hwinfo.txt

Please try to boot in runlevel 3 (no X-server running). Just add a 3 to the boot options for that. Log in and try to shutdown the machine with the command: "init 0". You may also want to play around with the halt/shutdown commands and some parameters (see man poweroff -> not sure if the params could make a big difference, Pavel may know).
IIRC the machine should shutdown if the X-server is not running!
Please verify and we could ask the X-Server guys what could go wrong here.

I try it but my laptop don't switch off , i have to press power off button.

Hello, i had the same problem on an Amilo 1650G Latop. Please try my workaround:
Open the menu.lst file in /boot and delete the entry "gfxmenu". Reboot the machine , shtudown - e.g. via Power button -. Now the Laptop must switch off.

regards,
Holger

That's interesting, seems as if on my tests I did not only stop X-server but also deleted that unnecessary gfxmenu stuff in menu.lst which actually let the machine shut down.

Steffen, Torsten, any idea what this could be or how to fix it?
Sounds like some graphics card early low level stuff?
Who shall I assign this one? I cannot do that.

I try to delete gfxmenu entry from menu.lst but if i do this , when i shutdown my laptop , my laptop reboot.

If it depends on graphics mode of *bootloader*... well, that's weird. It looks like something HP can solve (are there newer BIOS versions available?)

Hi Raul, 
please have a look at Bug 141021, that's my bug report. I did some "research" and maybe it is not enough only to change the menu.lst. I did modify also the boot process concerning the loadable modules at parameter "INITRD_MODULES" - here i deleted al files related with ACPI. Maybe it is also a must to change the DSDT table from your bios. A Howto can you find here http://acpi.sourceforge.net/dsdt/index.php. You can test also the shutdown process by insterting init=/bin/bash as a boot parameter. A minimum amount of kernel modules will be loaded at this time. After booting, you can shutdown the laptop "by hand" via "halt" or "shutdwon -h now". May you have to unload more modules as i with my amilo.

To the SuSE guys:
BIOS:
I can only speak for my FSC Bios, but this is realy rudimentary. Here is absoluty nothing adjustable for ACPI/APM/Power Management and there is no update available. Maybe this different on other machines.

Holger

gfxboot doesn't (shouldn't) leave any traces. In particular it switches back
to textmode before starting the kernel.

There were, however, problems with some ATI graphics hardware bug
in <= sl 10.0 & gfxboot. In that case 10.1 might do better.

Another thing that comes to mind is that gfxboot does something with
'profiles' on laptops, that may make a difference, too.

What are "profiles" and how does gfxboot interact with them?

It adds a profile=foo entry to the kernel options if asked to. That's then
later evaluated by some startup scripts or so.

Is there any developer working on this bug?

No, because the bug is in NEEDINFO state, waiting for you to provide info.

Question was if there are bios updates available for your system.

And I'll add a question, too. Will it shut down properly if you boot with init=/bin/bash? Change state back to assigned when you answer question.

Before Suse 10 , I try Ubuntu 5.10 for AMD64 and my laptop shutdown perfectly , so there is no problem with my hardware , bios , etc.

I attach my hardware info in hwinfo.txt file.

I try to to boot in runlevel 3 and get the same error , my laptop don't switch off.

I also try to delete gfxmenu entry from menu.lst but when i shutdown my laptop reboot automatically.

Now , i try to boot with init=/bin/bash and doesn't shutdown or do anything.

What kind of new info is needed?

I heard that the picture for gfxmenu was too big, could this be related to the reports that the gfxmenu entry modifies shutdown behaviour, Steffen?

Do you still know the kernel version of Ubuntu 5.10?

I have no ideas anymore...
I also have a similar machine here with shutdown problems, but it shuts off nicely after deleting gfxmenu (or maybe it was due some X-configurations?).
It could be worth to try another graphics driver, maybe vesafb?

Do you see any ACPI errors in dmesg? (dmesg |grep -i ACPI)
Posting dmesg would be nice, maybe someone sees anything.

Those ATI chipsets have more problems AFAIK, do you see the time running too fast? (watch -n1 date). If yes, does no_timer_check boot option fix that? If yes, maybe shutdown also works now?

-> Assigning to Steffen, I have no idea who could fix that...
-> CCing some X-people, maybe they have heard about such a thing or have some options to try?

No, the picture is not too big.

Raul, with gfxmenu enabled you can press ESC at boot time and leave
the graphics. Does that make a difference?

Anyway Raul says that even without gfxboot it doesn't power off. So I don't
see how I can help.

>Do you still know the kernel version of Ubuntu 5.10?
2.6.12-9-amd64-generic

>Do you see any ACPI errors in dmesg? (dmesg |grep -i ACPI)
>Posting dmesg would be nice, maybe someone sees anything.

I attach dmesg report

>Those ATI chipsets have more problems AFAIK, do you see the time running too
>fast? (watch -n1 date)

(watch -n1 date) works perfectly

>Raul, with gfxmenu enabled you can press ESC at boot time and leave
>the graphics. Does that make a difference?

I usually press ESC to show background messages and there is no difference

Created attachment 63625 [details]
dmesg_report.txt

> I usually press ESC to show background messages and there is no difference

Not kernel graphics. I mean in *grub*.

>Not kernel graphics. I mean in *grub*.

I try to press ESC at boot time , leave grapchics mode , select suse 10 and then system load kernel graphics and there is no difference.

You mean it reboots or it just doesn't power off?

> You mean it reboots or it just doesn't power off?

Doesn't power off

Ok, then I've no idea. Maybe you could try 10.1?

> Ok, then I've no idea. Maybe you could try 10.1?

10.1 is still in beta stage.

So there is no planned to be fixed this bug?

Maybe a kernel update to latest stable version , like 2.6.15.1 would fix the problem.

Is planned a new kernel update throw Yast (YOU)?

As soon as the problem is found ... There are dozens of hints in the net about AMD  Turion64 (and ATI chipsets) talking about the problem.
Also the time is running too fast and top shows 50% Soft-IRQ (on new kernels at least) context processing.
These are currently known problems with a lot of these machines on Debian, Slackware probably on all distries... as soon as some smart guy finds/fix it we will include it in our kernel. It depends how potentially dangereous and big the patch is whether it finds it way into 10.0.
If you find any workaround or fix for one of the above problems, please let us know (you also might want to google for Acer Ferrari, same chipset, same problems).

Can you make sure you have an ATI chipset (lspci), please.
Is it possible for you to give it a test with the latest OpenSuse Beta4 version?
If yes, try to comment out grub graphics, just add a # at the beginning of the line like:
#gfxmenu (hd0,1)/boot/message
also try:
disable_timer_pin_1 boot param.

Created attachment 69812 [details]
lspci.txt

>Can you make sure you have an ATI chipset (lspci), please.

Yes i have ATI chipset , I attach lspci result.

>Is it possible for you to give it a test with the latest OpenSuse Beta4
>version?

Sorry , I need a stable system , at the moment i don't think to try Beta.

Decreasing severity, please increase again if you still see this on current Betas.

This is fixed for 10.1.
This won't be backported to 10.0, as these APIC changes are rather unsafe (you never know which other machine you break with it).
disable_timer_pin_1 boot param could also do the trick for 10.0, not sure whether this is all needed.
If you should still see this bug on 10.1, please reopen and increase severity to major.

I was wrong, disable_timer_pin_1 (not needed anymore for 10.1) does not help and the bug is still present (I can reproduce this here with an ACER Ferrari).
Disabling gfxmenu in /boot/grub/menu.lst helps here.

Does this problem still remain in latest version?
Not sure whether the update kernel for 10.1 is already out (should be the same kernel provided with SLED/SLES 10 and should be a 2.6.16.21 kernel).
Can you please update to that kernel as soon as it is out and report back whether the problem still exists.

Last message of customer: 22. Feb 2006 -> closing, this should be fixed anyway.