http://bugzilla.novell.com/show_bug.cgi?id=619754 http://bugzilla.novell.com/show_bug.cgi?id=619754#c1 Russ Fineman changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |upscope@nwi.net --- Comment #1 from Russ Fineman 2010-07-03 18:38:32 UTC --- Forgot: Could be related to bugs 619752 or 588881 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=619754 http://bugzilla.novell.com/show_bug.cgi?id=619754#c yang xiaoyu changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xyyang@novell.com AssignedTo|bnc-team-screening@forge.pr |werner@novell.com |ovo.novell.com | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=619754 http://bugzilla.novell.com/show_bug.cgi?id=619754#c4 --- Comment #4 from Russ Fineman 2010-07-05 15:46:02 UTC --- Thanks for the reply. I Tried what you suggested. Initially I forgot to disable quiet. Did Alt/CTL/F1, got to cmd line login. Logged in as root. The last message on screen was: (shutdown -h now logged in as Root): The system will halt immediately [2461 647304] Power Down It hung here had to use power button to shutdown. Rebooted, went to YaST --> System-->Sysconfig-->bootloader-->Append and removed quiet. went back to desktop and did alt/ctl/F1 and system went to the ksplashx splash screen and hung. Did not go to Terminal. No Activity Check splash is set to no and quiet is removed. Should I have removed quiet like I did or should I have actually modified grub/menu.1st? I'll try again with quiet back in and if I get to terminal I'll shutdown and attach log or post it on pastebin and send url. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=619754 http://bugzilla.novell.com/show_bug.cgi?id=619754#c6 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |upscope@nwi.net --- Comment #6 from Dr. Werner Fink 2010-07-06 08:01:12 UTC --- OK ... now, does this mean that the shutdown -h now stops at the very last line executing the final halt command? The option -h is for halt, the option -r is for reboot, the option -P is a modifier for -h and stands for doing power off after halt. You may try shutdown -h -P now if this does not work your hardware or the BIOS/CMOS of your hardware has a problem with the system call used by halt to inform the kernel to switch into power off. That could be a problem with ACPI configuration of the kernel or the BIOS or of both. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=619754 http://bugzilla.novell.com/show_bug.cgi?id=619754#c8 Russ Fineman changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|upscope@nwi.net | --- Comment #8 from Russ Fineman 2010-07-06 22:58:50 UTC --- Konquer restarted it self. should read: After Power Failure <stay off> Wake on LAN from S5 <stay off> ACPS Suspend state <S3 State> EIST <enable> C2 State <enable> Wake system from S5 <Disable> Do not think its BIOS since 11.2 still shuts down normally with Widget and cmd line shutdown cmd. Setup is: sda openSUSE 11.2 sdb openSUSE 11.3 Where is the APCI config file located? ?etc/acpi/power_button has: code -------- # care about the power button event=button/power.* action=/usr/lib/acpid/power_button --------- The script does exist in /usr/lib.No version in /usr/lib64 code ------------ Beginning part of script: #!/bin/bash # # check if a X session is running and active. # If not, shut down the system # # Copyright (C) 2008 Holger Macht # # This file is released under the GPLv2. # EXEC="/sbin/shutdown -h now" # check if we have pm-profiler and an active profile. If so, $EXEC can be # overwritten by the active profile's configuration /etc/pm-profiler.conf > /dev/null 2>&1 if [ "$?" = "0" ]; then . /etc/pm-profiler/$PM_PROFILER_PROFILE/config >/dev/null 2>&1 fi [ -z "$POWER_BUTTON_HOOK" ] || EXEC="$POWER_BUTTON_HOOK" # iterate over all sessions. If a active X session is found, do nothing while read A; do ------------- The command shown is what I use on 11.2 with the additional option -t 5, also works with out it. I checked power management under Config desktop and 11.2 and 11.3 look the same. I know this worked on MS6 withKDE 4.5 (RC?). It has not worked on MS 7 or RC1 or now RC2. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=619754 http://bugzilla.novell.com/show_bug.cgi?id=619754#c10 --- Comment #10 from Russ Fineman 2010-07-07 17:37:05 UTC --- I even tried this a a different user, does same thing. If its a kernel problem where can we report it so they look at it? I appreciate all your help. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=619754 http://bugzilla.novell.com/show_bug.cgi?id=619754#c11 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |upscope@nwi.net --- Comment #11 from Thomas Renninger 2010-07-08 12:56:22 UTC --- Can you boot into single user mode or runlevel 1 (by passing "S" or "1" as a boot option). Then log in as root and try: init 0 or "shutdown -h now" If this works you can try the same with some more drivers loaded, e.g. runlevel "3". If this does not work we already know that a specific driver causes that. You can also increase the acpi debug level: echo 0xF >/sys/module/acpi/parameters/debug_level echo 0xFFFFFFFF >/sys/module/acpi/parameters/debug_layer and then shut down. ACPI should finally switch the machine off at the very end, it might help to see the last message with increased debug output. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=619754 http://bugzilla.novell.com/show_bug.cgi?id=619754#c13 --- Comment #13 from Russ Fineman 2010-07-08 17:18:02 UTC --- Reference comments 11 & 12 1.tried S with shutdown command and then init 0 both gave same failure. 2. tried 1 same result as above. 3. enabled additional logging, started with 1, issued shutdown command, got following for last three lines: [ 279.083185] SMP Alternatives : Switching to UP code [ 279.088899] Power Down [ 279.089234] hwsleep -0314 [00] enter sleep state : Entering sleep state (S5) Powered down with button and went into BIOS on reboot. Power section has following setting ( same as earlier. After Power Failure <Stay Off> Wake on LAN from S5 <Stay Off> ACPS Suspend State <S3 State> EIST <Enable> C2 State <Enable> Wake System from S5 <Disable> As far as I know nothing has changed in the BIOS since system is new. Has latest update, that is necessary. I think there is one later one avaible from Intel but I don't see the problem it fixes. Like I said this was working in MS6. Failed after install of MS7, now on RC2. I am attaching acpidump. Thanks for all of the help from everyone!! -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=619754 http://bugzilla.novell.com/show_bug.cgi?id=619754#c15 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |upscope@nwi.net --- Comment #15 from Thomas Renninger 2010-07-09 09:02:19 UTC --- I compared Milestone 6 and Milestone 7 differences and cannot see anything obvious. Can you try a vanilla (without SUSE patches) kernel from here please: ftp://ftp.suse.com/pub/projects/kernel/kotd/openSUSE-11.3/x86_64/kernel-vanilla.rpm and a Milestone 6 kernel I copied here (may take some hours until it shows up): ftp.suse.com/pub/people/trenn/milestone6_kernel/kernel-desktop-2.6.34-6.1.x86_64.rpm Best you install the kernels with rpm -ivh xy.rpm Eventually you need --force or --nodeps Then these kernels are installed additionally and you can remove them and/or switch back to the original kernel easily. Possibly you have to adjust the default entry in /boot/grub/menu.lst Best is you double check that you have booted the right kernel before doing the shutdown test with "uname -r". This should tell us: - whether this is a mainline regression introduced between 2.6.34-rc5 and rc7/final - whether it's really kernel related or whether some userspace modifications trigger this issue -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=619754 http://bugzilla.novell.com/show_bug.cgi?id=619754#c17 Russ Fineman changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|upscope@nwi.net | --- Comment #17 from Russ Fineman 2010-07-10 13:45:39 UTC --- (In reply to comment #15)

I compared Milestone 6 and Milestone 7 differences and cannot see anything obvious. Can you try a vanilla (without SUSE patches) kernel from here please: ftp://ftp.suse.com/pub/projects/kernel/kotd/openSUSE-11.3/x86_64/kernel-vanilla.rpm and a Milestone 6 kernel I copied here (may take some hours until it shows up): ftp.suse.com/pub/people/trenn/milestone6_kernel/kernel-desktop-2.6.34-6.1.x86_64.rpm

Best you install the kernels with rpm -ivh xy.rpm Eventually you need --force or --nodeps

Then these kernels are installed additionally and you can remove them and/or switch back to the original kernel easily. Possibly you have to adjust the default entry in /boot/grub/menu.lst Best is you double check that you have booted the right kernel before doing the shutdown test with "uname -r".

This should tell us: - whether this is a mainline regression introduced between 2.6.34-rc5 and rc7/final - whether it's really kernel related or whether some userspace modifications trigger this issue

Sorry I did not get back to you yesterday. I download and installed both kernels mentioned above. Did one, tested then download and did other one. Results were negative. Below in order of testing. MS6 Kernel 1. Downloaded, had to use --force. 2. Booted and it went to a command line log-in Logged in with my user ID 3. checked version uname -r 2.6.34-rc5-6-desktop 4. Entered command "sudo /sbin/shutdown -h now" (no quotes) It went thru shutdown and stopped with: [ 237.899946] Power Down 5. Waited ten minutes and used power switch to turn off system Vanilla Kernel Same basic results. 1. Downloaded, had to use --force. 2. Booted and it went to a command line log-in Logged in with my user ID 3. uname -r 2.6.34.1-0.0.8.5f291ff-vanilla 4. Entered command "sudo /sbin/shutdown -h now" (no quotes) It went thru shutdown and stopped with: [ 295.869061] Power Down 5. Waited ten minutes and used power switch to turn off system I would suspect its not a regression. Since I get same results on RC2 with another user I created, and with run level 1 and S as root. Is it possible that I got something in the Build 0694 iso thats bad. Even though I have downloaded it three times and it passed all checks except the check Media on the created DVD. It passes check media in YaST and all three check sums. Is it worth installing RC2 again? Or is Build 702 where it can be downloaded before Friday? Hope you have a good weekend. Thanks again. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=619754 http://bugzilla.novell.com/show_bug.cgi?id=619754#c19 --- Comment #19 from Russ Fineman 2010-07-12 15:54:31 UTC --- Thanks for your response. What I was going to do is want for 11.3 release on Friday and install it on a completely new disc. I'm sure 11.2 still works as the way I log off is to use the Widget or shutdown command to restart the computer and select my 11.2 system. Get to The login screen and select menu shutdown (or I log in and click on the widget to shutdown) and the system goes thru the shutdown and turns off the power with no problem. There have been no changes to my BIOS. I went into the BIOS for the first time this year the other day when I was checking the power settings. No new devices have been added. I also have started getting weid issues with my postscript printer (won't print PS at all) Prints OK from 11.2) I read on the VirtualBox list that there is a known bug in the 2.6 kernel that corrputs the ext4 formatted drives. I was wondering if this is a possibility? I'm looking for more info on that. On the acpi command above does it become permenent and If some how do I change it back? I have not updated my KDE or anything on my 11.2 since this problem started. Its pretty much bare bones at this point except for Kmail and OpenOffice. I will try some of your suggestions later today. Thats for your continuing help. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=619754 http://bugzilla.novell.com/show_bug.cgi?id=619754#c21 --- Comment #21 from Russ Fineman 2010-07-16 15:29:12 UTC --- Thomas sorry for taking so long to get back to you. Had a newsletter to get out, did not want to corrupt something here on RC2. I finally finished Wed. On thursday I installed a brand new 1TB internal disc, and installed the new released version of 11.3 from the downloaded DVD. Installed with no problems. Spent yesterday and this morning early straighting out the menu.ist stuff, and retesting all the about steps to see why I still cannot power down. Same result as 11.3-RC2. Went thru the Intel motherboard manual and all setting are correct except for the changes made for the boot sequence. What I have now is three systems: 1 TB Disc 11.3-Released version 320 GB Disc 11.3 RC2 320 GB Disc 11.2 Below are the 11.2 interrupts you asked about: Below are 11.3 interrupts from 11.3 RC2: 11.3 less /proc/interrupts CPU0 CPU1 0: 214971 230280 IO-APIC-edge timer 1: 1 1 IO-APIC-edge i8042 3: 1 1 IO-APIC-edge 8: 28 22 IO-APIC-edge rtc0 9: 0 0 IO-APIC-fasteoi acpi 12: 2 2 IO-APIC-edge i8042 16: 57865 118 IO-APIC-fasteoi pata_marvell, nvidia 17: 3599 6180 IO-APIC-fasteoi ehci_hcd:usb1, uhci_hcd:usb5 18: 0 0 IO-APIC-fasteoi uhci_hcd:usb3, uhci_hcd:usb8 19: 2 1 IO-APIC-fasteoi uhci_hcd:usb7, ohci1394 21: 0 0 IO-APIC-fasteoi uhci_hcd:usb4 23: 989 358 IO-APIC-fasteoi ehci_hcd:usb2, uhci_hcd:usb6 27: 11974 19430 PCI-MSI-edge ahci 28: 6532 66 PCI-MSI-edge eth0 29: 359 409 PCI-MSI-edge hda_intel NMI: 0 0 Non-maskable interrupts LOC: 184298 181515 Local timer interrupts SPU: 0 0 Spurious interrupts PMI: 0 0 Performance monitoring interrupts PND: 0 0 Performance pending work RES: 204644 200594 Rescheduling interrupts CAL: 1121 121 Function call interrupts TLB: 5800 5797 TLB shootdowns TRM: 0 0 Thermal event interrupts THR: 0 0 Threshold APIC interrupts MCE: 0 0 Machine check exceptions MCP: 28 28 Machine check polls ERR: 1 MIS: 0 /proc/interrupts lines 1-30 11.2 less /proc/interrupts CPU0 CPU1 0: 35669 44365 IO-APIC-edge timer 1: 1 1 IO-APIC-edge i8042 3: 1 1 IO-APIC-edge 8: 30 25 IO-APIC-edge rtc0 9: 0 0 IO-APIC-fasteoi acpi 12: 0 4 IO-APIC-edge i8042 16: 8227 64 IO-APIC-fasteoi pata_marvell, nvidia 17: 1371 1689 IO-APIC-fasteoi ehci_hcd:usb1, uhci_hcd:usb5 18: 0 0 IO-APIC-fasteoi uhci_hcd:usb3, uhci_hcd:usb8 19: 2 1 IO-APIC-fasteoi uhci_hcd:usb7, ohci1394 21: 0 0 IO-APIC-fasteoi uhci_hcd:usb4 22: 460 238 IO-APIC-fasteoi HDA Intel 23: 77287 520 IO-APIC-fasteoi ehci_hcd:usb2, uhci_hcd:usb6 27: 5133 5743 PCI-MSI-edge ahci 28: 167 31 PCI-MSI-edge eth0 NMI: 0 0 Non-maskable interrupts LOC: 38153 4468 Local timer interrupts SPU: 0 0 Spurious interrupts CNT: 0 0 Performance counter interrupts PND: 0 0 Performance pending work RES: 9942 24160 Rescheduling interrupts CAL: 180 1078 Function call interrupts TLB: 594 619 TLB shootdowns TRM: 0 0 Thermal event interrupts THR: 0 0 Threshold APIC interrupts MCE: 0 0 Machine check exceptions MCP: 1 1 Machine check polls ERR: 1 MIS: 0 also when I try the S or 1 logon. The echo command says the directory or final are not there. If I just boot up and use dolphing both debug files are in correct directory. I am logged in as root since it starts by asking for root password. Did notice two other things on boot that may effect this, I'm not sure. 0n 11.3 if I start normal or single step thru the boot proces nscd fails. On 11.2 if I start normal fuse.boot fails, if I single step it does Not fail. restart and going to 11.2 allows normal shutdown, so I not sure how it can be BIOS or hardware unless some command or script has changed. Thanks again for your help. Not sure what next steps should be? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=619754 http://bugzilla.novell.com/show_bug.cgi?id=619754#c23 Alberto Passalacqua changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |albert.passalacqua@gmail.co | |m --- Comment #23 from Alberto Passalacqua 2010-07-17 00:10:24 UTC --- This affects also a Dell Latitude E6410, Intel i7 CPU, with 11.3 final. I tested what has been suggested above, and the only different behavior I found is with SysReq keys. If I use Alt-SysReq-o (poweroff), the system reboots instead of getting stuck as reported in comment #20. Also here openSUSE 11.2 can shutdown correctly. I did some testing with a distribution with kernel 2.6.32, and also there the system reacts properly to the shutdown / halt commands. Thanks. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=619754 http://bugzilla.novell.com/show_bug.cgi?id=619754#c24 --- Comment #24 from Alberto Passalacqua 2010-07-17 12:28:19 UTC --- Some research led me to find this: https://bugzilla.kernel.org/show_bug.cgi?id=16114 So I tried the kernel of the day on the build service (2.6.35-rc5-10-default), and the system started to behave properly for what concerns poweroff. Would it be possible to push an official update, since openSUSE 11.3 has been out for only 2 days? It would be great :) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=619754 http://bugzilla.novell.com/show_bug.cgi?id=619754#c26 Rafael Wysocki changed: What |Removed |Added ---------------------------------------------------------------------------- InfoProvider|rjw@novell.com |gregkh@novell.com --- Comment #26 from Rafael Wysocki 2010-07-19 22:39:21 UTC --- The GPE fixes have already been submitted to -stable. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=619754 http://bugzilla.novell.com/show_bug.cgi?id=619754#c28 --- Comment #28 from Joerg Riechardt 2010-07-20 14:35:55 UTC --- Same with a TUSL2-C with i815. After 'shutdown -h now' the system goes down, but instead of switching power off, it reboots. With openSUSE 11.2 and many versions before no problem. On 11.3 I tried several kernels. 2.6.34-12-default and 2.6.34-12-desktop have the problem. 2.6.35-rc5 and 2.6.34.1 same problem. 2.6.32.16 is ok. 2.6.33.6 is ok too. So for me the GPE fixes do not resolve the problem. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=619754 http://bugzilla.novell.com/show_bug.cgi?id=619754#c30 --- Comment #30 from Rafael Wysocki 2010-07-20 22:27:28 UTC --- Also, can anyone affected please test the latest KOTD kernel from: http://ftp.suse.com/pub/projects/kernel/kotd/master/ (that matches your architecture/flavour)? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=619754 http://bugzilla.novell.com/show_bug.cgi?id=619754#c32 --- Comment #32 from Joerg Riechardt 2010-07-21 01:55:08 UTC --- linux-b37t:~ # uname -r 2.6.35-rc5-0.0.133.adac04b-desktop linux-b37t:~ # dmesg | grep -e acpi [ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) [ 2.210990] ACPI: acpi_idle registered with cpuidle Problem continues. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=619754 http://bugzilla.novell.com/show_bug.cgi?id=619754#c34 --- Comment #34 from Rafael Wysocki 2010-07-21 20:16:09 UTC --- (In reply to comment #33)

Just checked dmesg on my RC2 install. There are quite a few references to ACPI but most look normal. Below are the couple I think look bad and also a seg fault with HAlprobe. Don't think its related. Tomorrow Ill check the released version. 11.2 still functions normal.

These messages:

[ 0.365602] pcieport 0000:00:01.0: Requesting control of PCIe PME from ACPI BIOS [ 0.365615] pcieport 0000:00:01.0: Failed to receive control of PCIe PME service: no _OSC support [ 0.365621] pcie_pme: probe of 0000:00:01.0:pcie01 failed with error -13 [ 0.365626] pcieport 0000:00:1c.0: Requesting control of PCIe PME from ACPI BIOS [ 0.365631] pcieport 0000:00:1c.0: Failed to receive control of PCIe PME service: no _OSC support [ 0.365635] pcie_pme: probe of 0000:00:1c.0:pcie01 failed with error -13 [ 0.365640] pcieport 0000:00:1c.4: Requesting control of PCIe PME from ACPI BIOS [ 0.365645] pcieport 0000:00:1c.4: Failed to receive control of PCIe PME service: no _OSC support [ 0.365650] pcie_pme: probe of 0000:00:1c.4:pcie01 failed with error -13

are not to worry about. They only mean the BIOS didn't allow us to do something we wanted and that's harmless. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=619754 http://bugzilla.novell.com/show_bug.cgi?id=619754#c36 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |albert.passalacqua@gmail.co | |m --- Comment #36 from Thomas Renninger 2010-08-06 10:49:40 UTC --- Alberto: Can you confirm that your system can be powered down since 2.6.35-rc5-13-desktop reliably while it could not with the 11.3 kernel. There seem to be at least two problems: - Joerg reports his system reboots instead of powering down and he still sees the problem in 2.6.35-rc5 - Alerberto's (and Russ') system does not switch off, but this problem seem to be fixed in 2.6.35 (at least since rc5). Alberto/Russ: Could you try latest 11.3 update kernel from here: ftp://ftp.suse.com/pub/projects/kernel/kotd/openSUSE-11.3/x86_64 The latest stable kernel patches came two days ago (including some gpe fixes): Wed Aug 4 01:10:18 CEST 2010 - gregkh@suse.de - Update to 2.6.34.2 Best double check whether the downloaded rpm really includes these: rpm -qp --changelog kernel-xy.rpm |less If this works, I'd like to close this bug. Joerg: you would have to open another one if your problem persists. Mixing up different problems in one bugreport is evil. Others searching for this problem get totally confused, it's also hard for people trying to solve the issue, if they have to read this from scratch and have to differ several problems... -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=619754 http://bugzilla.novell.com/show_bug.cgi?id=619754#c38 --- Comment #38 from Alberto Passalacqua 2010-08-06 20:24:09 UTC --- Hi Thomas, the link you provided is not recognized as a valid repository in YaST, and even going to the main directory ftp://ftp.suse.com/pub/projects/kernel/kotd/openSUSE-11.3 does not work. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=619754 http://bugzilla.novell.com/show_bug.cgi?id=619754#c40 --- Comment #40 from Russ Fineman 2010-08-06 22:20:40 UTC --- I just tried 2.6.35 -rc6 from http://download.opensuse.org/repositories/Kernel%3a/HEAD/openSUSE_11.3/ as I was not allowed to log into the repo mentioned above. Several issues: occurred: 1 YaST install the kernel as a separate kernel install on boot menu instead of updating the 2.6.12 kernel (Did not show as kernel update, had to go to version tab and select it. 2. Went to run level three to install NVIDIA Drivers, they installed but as added a desktop kernel(2.6.12) to my boot menu. 3, back to command line in run level three, verified kernel version with uname -a, it was 2.6.35. The typed: shutdown -h now as root. system went to same hang as before {Power Down some numbers} and stays there at least for 20 minutes. This my original system so at least RC6 from /Kernel/HEAD repo. does not fix. If my 11.2 drive is still Ok I'll try it and also see if I can use repo in comment 39. I do know powerdown works in 11.2 on my old system (Micron 866MHZ Petimum III) As I installed the latest version of 11.2 yesterday as a backup for some of my production work, slow as the devil but reliable. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=619754 http://bugzilla.novell.com/show_bug.cgi?id=619754#c42 --- Comment #42 from Russ Fineman 2010-08-07 03:46:09 UTC --- Just confirmed that 2.6.34.2.2 DOES NOT fix my shutdown problem. Using YaST I added repo http://download.opensuse.org/repositories/Kernel:/openSUSE-11.3/openSUSE_11.... Selected 2.6.34.2.2 for all installed kernel options, wound up with new entries in grub menu instead of the kernel upgrade, actually YaSt considered it a down grade. Also the Nvidia driver would not work with 2,2 (using Nvidia nvidia-gfxG02-kmp-default-256.35_k2.6.34.0_12-14.1.x86_64 x11-video-nvidiaG02-256.35-15.1.x86_64 Re installed 2.6.34.3 Still cannot power down. Any next steps to test? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=619754 https://bugzilla.novell.com/show_bug.cgi?id=619754#c44 --- Comment #44 from Rafael Wysocki 2010-08-22 20:26:00 UTC --- (In reply to comment #42)

Just confirmed that 2.6.34.2.2 DOES NOT fix my shutdown problem. Using YaST I added repo http://download.opensuse.org/repositories/Kernel:/openSUSE-11.3/openSUSE_11.... Selected 2.6.34.2.2 for all installed kernel options, wound up with new entries in grub menu instead of the kernel upgrade, actually YaSt considered it a down grade. Also the Nvidia driver would not work with 2,2 (using Nvidia

nvidia-gfxG02-kmp-default-256.35_k2.6.34.0_12-14.1.x86_64 x11-video-nvidiaG02-256.35-15.1.x86_64

Re installed 2.6.34.3 Still cannot power down.

Any next steps to test?

1. Please test the next 2.6.34.y kernel update. 2. Please try to boot into runlevel 3 and check if "shutdown -h now" still fails. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=619754 https://bugzilla.novell.com/show_bug.cgi?id=619754#c46 Rafael Wysocki changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |upscope@nwi.net --- Comment #46 from Rafael Wysocki 2010-08-27 19:27:14 UTC --- Is it possible/practical to build an kernel.org kernel from scratch and install it on your system? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=619754 https://bugzilla.novell.com/show_bug.cgi?id=619754#c48 --- Comment #48 from Russ Fineman 2010-08-27 21:29:39 UTC --- Jf some one gives me the steps to do it I can do it under 11.4 testbed. Cannot afford to risk my 11.3 system at this time. Possibly could do it as second kernel on 11.3 system and not touch present kernel becuse only major problem is shutdown on 11.3. I'm willing to try. I have never done it before with guidance I can probably do it. My 11.4 is 2.6.34-14.8-desktop. It also does not shutdown. Let me know what to do. (upscope@nwi.net) if you would like to send the instructions instead of posting them here. I'll keep checking this bug for your input. I had 41 years of computer experience in Field Service, Data Center Management and development engineering but not much in programming or compiling programs etc. willing to learn and have some time. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=619754 https://bugzilla.novell.com/show_bug.cgi?id=619754#c50 --- Comment #50 from Rafael Wysocki 2010-08-30 22:13:01 UTC --- @Jeff: The "build from scratch" part of my question was more important. :-) @Russ: The procedure is the following: 1. Get the kernel sources. My favorite way is to use git for this purpose: $ git clone \ git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git linux-2.6 (you'll need to install git packages to use that). Then, your kernel source will be located in the linux-2.6 subdirectory of the current directory. 2. Go to the kernel source directory and do: $ zcat /proc/config.gz > .config (this creates a kernel source configuration file matching SUSE kernel's config). 3. Run "make" (if you have a multicore CPU, use "make -jN", where N is the number of CPU cores in the system plus one, to speed up things). 4. If the build is successful, run "make modules_install" 5. Run $ cat include/generated/utsrelease.h and write down the string in quotes (this is the new kernel version string). 6. Run as root: # export KERNEL_VERSION="string in quotes from step 5." # cp arch/x86/boot/bzImage /boot/vmlinuz-$KERNEL_VERSION && \ cp System.map /boot/System.map-$KERNEL_VERSION # mkinitrd -k vmlinuz-$KERNEL_VERSION -i initrd-$KERNEL_VERSION 7. Add the new kernel entry to /boot/grub/menu.lst Basically, copy one of the existing entries and replace all instances of the kernel version in it (eg. 2.6.34-12-desktop) with $KERNEL_VERSION from step 6. 8. Reboot and select the new kernel from the list. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=619754 https://bugzilla.novell.com/show_bug.cgi?id=619754#c52 --- Comment #52 from Thomas Renninger 2010-08-31 09:56:08 UTC --- If you do not have that much of disc space (5G>) you may want modify the line: CONFIG_DEBUG_INFO=y to # CONFIG_DEBUG_INFO is not set in .config. I ran into this recently when compiling on my private machine which has not that huge partitions. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=619754 https://bugzilla.novell.com/show_bug.cgi?id=619754#c54 --- Comment #54 from Russ Fineman 2010-08-31 18:07:51 UTC --- (In reply to comment #52)

If you do not have that much of disc space (5G>) you may want modify the line: CONFIG_DEBUG_INFO=y to # CONFIG_DEBUG_INFO is not set in .config. I ran into this recently when compiling on my private machine which has not that huge partitions.

I am compiling this in my home directory (200GB) and according to My Computer it has 168GB available as of a few minutes ago. I did do a make clean after trying this yesterday. Should there be any answers to the questions? I just hit enter and accepted the default. I'll try again later today. Thanks for the continuing help. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=619754 https://bugzilla.novell.com/show_bug.cgi?id=619754#c56 --- Comment #56 from Russ Fineman 2010-09-01 02:21:03 UTC --- Referencing comment 50. I am ready to do the second part of step 6. cp arch/x86/xxxx. I notice the is also a x86_64 with a link to the x86 folder (linux-2.6). Do I need to create that link also? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=619754 https://bugzilla.novell.com/show_bug.cgi?id=619754#c58 --- Comment #58 from Thomas Renninger 2010-09-01 12:37:48 UTC --- Created an attachment (id=386830) --> (http://bugzilla.novell.com/attachment.cgi?id=386830) Install script for a built kernel Chmod the file so that it gets executable, go to the main directory where your built kernel is and just call it. Note: This script is not well maintained, it has additional features which may need some manual workarounds to work properly. But for you scenario it should work just fine. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=619754 https://bugzilla.novell.com/show_bug.cgi?id=619754#c60 --- Comment #60 from Russ Fineman 2010-09-01 22:27:50 UTC --- still having a problem installing. If I try script you sent from inside the build directory I get the following error: <code> ------- sudo install 2.6.36-rc3-6-default install: missing destination file operand after `2.6.36-rc3-6-default' Is the destination /boot? There is already two files in /boot from manual execution of the commands. -rw-r--r-- 1 root root 1885043 2010-09-01 11:31 System.map-2-6.36-rc3-6-default -rw-r--r-- 1 root root 3410704 2010-09-01 10:27 vmlinuz-2.6.36-rc3-6-default there is no config -, symsets- 0r initrd- file. Should't they be there? Where do I execute the mkinitrd command? mkinitrd -k vmlinuz-$KERNEL_VERSION -i initrd-$KERNEL_VERSION it gives error in ~/linux-2.6 directory. Kernel image: /boot/vmlinuz- Initrd image: /boot/initrd- Could not find map /boot/System.map, please specify a correct file with -M. There was an error generating the initrd (9) Sorry to be such a pest but I am learning alot. Thanks for your continuing support!! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=619754 https://bugzilla.novell.com/show_bug.cgi?id=619754#c62 --- Comment #62 from Russ Fineman 2010-09-02 00:18:50 UTC --- When I did the export I did have the kernel version there. I then did the two copy commands and there is a system map and a vmlinux file in /boot with the correct kernel version in the name. I will start at step 6 in the morning and execute the mkinitrd from /boot as root. I thought I did that but I do it again Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=619754 https://bugzilla.novell.com/show_bug.cgi?id=619754#c64 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |upscope@nwi.net --- Comment #64 from Thomas Renninger 2010-09-03 16:45:59 UTC --- I expect you run into bug #636741, that's also the reason why my script does not work anymore. Only happens since 2.6.35 and if you work in git environment, a stupid feature IMO. Simply also specify the System.map file should do the trick: mkinitrd -k vmlinuz-2.6.36-rc3-6-default -i initrd-2.6.36-rc3-6-default -M System_map-2.6.36-rc3-6-default -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=619754 https://bugzilla.novell.com/show_bug.cgi?id=619754#c66 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |upscope@nwi.net --- Comment #66 from Thomas Renninger 2010-09-04 11:32:20 UTC ---

Just tried the above after correcting System_map to actual name System.map. Hm, you renamed it to System.map? Best rename or copy it again from your git compilation dir: cp System.map /boot/System.map-2.6.36-rc3-6-default cd /boot mkinitrd -k vmlinuz-2.6.36-rc3-6-default -i initrd-2.6.36-rc3-6-default -M System.map-2.6.36-rc3-6-default vmlinuz-... and System.map-... must exist, initrd gets generated.

-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=619754 https://bugzilla.novell.com/show_bug.cgi?id=619754#c68 --- Comment #68 from Thomas Renninger 2010-09-06 13:54:13 UTC --- Strange, does it work if you specific everything with absolute path names (-k /boot/... -i /boot/... -M /boot/...)? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=619754 https://bugzilla.novell.com/show_bug.cgi?id=619754#c70 --- Comment #70 from Russ Fineman 2010-09-08 15:56:07 UTC --- Thomas just to keep you up todate: Finally got time this morning and ran mkinitrd with full path name. Results: linux-98qc:/boot # mkinitrd -k /boot/vmlinuz-2.6.36-rc3-6-default -i /boot/initrd-2.6.36-rc3-6-default -M /boot/System.map-2.6.36-rc3-6-default Kernel image: /boot/vmlinuz-2.6.36-rc3-6-default Initrd image: /boot/initrd-2.6.36-rc3-6-default Root device: /dev/disk/by-id/ata-ST31000528AS_9VP6KV4Y-part2 (/dev/sdc2) (mounted on / as ext4) Resume device: /dev/disk/by-id/ata-ST31000528AS_9VP6KV4Y-part1 (/dev/sdc1) Kernel Modules: scsi_mod libata libahci ahci pata_marvell ata_generic thermal_sys processor thermal fan crc16 jbd2 ext4 pata_opti ata_piix pata_sil680 pata_cs5530 pata_artop pcmcia_core pcmcia pata_pcmcia pata_pdc2027x pata_cmd64x sata_mv sata_qstor sata_promise pata_hpt366 pata_optidma pdc_adma pata_amd pata_jmicron pata_via pata_efar pata_pdc202xx_old pata_it8213 sata_nv pata_ninja32 pata_mpiix pata_acpi sata_sil sata_svw sata_sx4 pata_sch pata_rdc pata_ali pata_sis sata_sis pata_ns87415 pata_netcell pata_cmd640 pata_hpt3x3 pata_rz1000 pata_sc1200 pata_it821x pata_ns87410 sata_uli sata_via pata_oldpiix sata_sil24 pata_serverworks pata_radisys pata_sl82c105 pata_triflex pata_hpt37x pata_atp867x sata_inic162x pata_atiixp pata_cypress sata_vsc pata_cs5520 pata_hpt3x2n pata_piccolo sd_mod usbcore mmc_core ssb ohci-hcd ehci-hcd uhci-hcd usbhid Features: block usb resume.userspace resume.kernel Bootsplash: openSUSE (1280x1024) 49617 blocks linux-98qc:/boot # ls Trash-0 config-2.6.34-12-desktop symsets-2.6.34-12-default.tar.gz vmlinux-2.6.34-12-default.gz System.map-2.6.34-12-default grub symsets-2.6.34-12-desktop.tar.gz vmlinux-2.6.34-12-desktop.gz System.map-2.6.34-12-desktop initrd symsets-2.6.34-12-xen.tar.gz vmlinux-2.6.34-12-xen.gz System.map-2.6.36-rc3-6-default initrd-2.6.34-12-default symtypes-2.6.34-12-default.gz vmlinuz backup_mbr initrd-2.6.34-12-desktop symtypes-2.6.34-12-desktop.gz vmlinuz-2.6.34-12-default boot initrd-2.6.36-rc3-6-default symtypes-2.6.34-12-xen.gz vmlinuz-2.6.34-12-desktop boot.readme lost+found symvers-2.6.34-12-default.gz vmlinuz-2.6.36-rc3-6-default config-2.6.34-12-default message Should I have the config-xxxx and symsets-xxx files? Will modify grub/menu.lst later this morning and try boot. Hopefully it will work. My 11.4 does same thing but has kernel 2.6.34.14-default. Hopefully I can try .36 today, Hear the latest update fixes a few problems including Nvidia driver. Will post later. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=619754 https://bugzilla.novell.com/show_bug.cgi?id=619754#c72 --- Comment #72 from Russ Fineman 2010-10-24 17:12:59 UTC --- Sorry I have been out of touch. Injury my back and have been laid up. My 11.3 system is now at 2.6.34.7-0.4-default, KDE 4.5.2 Release 10 and Nvidia: nvidia-gfxG02-kmp-default-260.19.12_k2.6.34.0_12-22.1.x86_64 x11-video-nvidiaG02-260.19.12-23.1.x86_64 nvidia-texture-tools-2.0.6-7.2.x86_64 nvidia-settings-256.35-0.pm.1.1.x86_64 My 11.4 system is at MS1. openSUSE 11.3. and 11.4 have problem. My 11.2 system still shutsdown correctly. Of the three systems (Same system Hardware, each on separate disks). The one thing I have noticed is after a Kernel upgrade (11.3) and install 11.4 MS1 The first time I click shutdown or use command instead of clicking it shuts down properly. The next time it hangs at the power down message. This is true on both systems. Like something is not being reset or set (possibly in BIOS){Common to all true openSUSE versions}. Will try getting kernel on 11.4 to latest and test this week since I can now move around. Thanks -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=619754 https://bugzilla.novell.com/show_bug.cgi?id=619754#c74 --- Comment #74 from Russ Fineman 2011-01-10 16:58:07 UTC --- Additional info. This problem also is experienced on 11.4 MS 1, 2 and 3. Did fresh install of 11.4 MS4 and powerdown worked. Lately did update from 11.4 to 11.5 using YaST and powerdown now fails again. Note: after reboot the first time after update or install, ythe shutdown command works, then next time a reboot occurs it fails. Only version this was not true for was 11.4 MS 4, it worked everytime. Today my configurations are: 11.3 is: openSUSE 11.3 (2.6.34.7-0.7-default)|KDE 4.5.5 Release 1| Intel core2duo 2.5 MHZ,|8GB DDR3|GeForce 8400GS Nvidia 260.19.29| 11.4 is: openSUSE 11.4 MS5 (2.6.37-rc7-desktop)|Platform Version Version 4.5.95 (4.6 RC2)|Intel core2duo 2.5 MHZ,|8GB DDR3|GeForce 8400GS (NVIDIA-Linux-x86_64-260.19.21) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=619754 https://bugzilla.novell.com/show_bug.cgi?id=619754#c76 Russ Fineman changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|upscope@nwi.net | --- Comment #76 from Russ Fineman 2011-11-25 17:34:17 UTC --- (In reply to comment #75)

What it the state here for 11.4 or better 12.1 release versions? If this is still a 12.1 problem, it's worth looking at it.

Just found this message. I have been running 12.1 since ms1, now on released version and the system has shutdown correctly since ms1. 11.4 still has the problem even though its been updated. I'm not sure its worth looking into unless someone else has the problem or unless it develops in 12.1 after an upgrade. My system is now: openSUSE 12.1(Linux 3.1.0-1.2-desktop x86_64)|KDE Platform Version 4.7.3 (4.7.3) Release "10"|Intel core2duo 2.5 MHZ, |8GB DDR3|GeForce 8400GS (NVIDIA-Linux-x86_64-285.05.09) Thanks for your help so far. Will start new bug if this occurs again. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.