https://bugzilla.novell.com/show_bug.cgi?id=812592 https://bugzilla.novell.com/show_bug.cgi?id=812592#c Jeff Mahoney <jeffm@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel-maintainers@forge.pr |bpetkov@suse.com |ovo.novell.com | -- 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=812592 https://bugzilla.novell.com/show_bug.cgi?id=812592#c3 --- Comment #3 from Diego Ercolani <diego.ercolani@gmail.com> 2013-07-15 20:24:21 UTC --- Created an attachment (id=548052) --> (http://bugzilla.novell.com/attachment.cgi?id=548052) dmidecode GA-990XA-UD3 -- 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=812592 https://bugzilla.novell.com/show_bug.cgi?id=812592#c5 --- Comment #5 from Diego Ercolani <diego.ercolani@gmail.com> 2013-07-15 20:25:16 UTC --- Created an attachment (id=548054) --> (http://bugzilla.novell.com/attachment.cgi?id=548054) export-db -- 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=812592 https://bugzilla.novell.com/show_bug.cgi?id=812592#c7 --- Comment #7 from Diego Ercolani <diego.ercolani@gmail.com> 2013-07-16 23:03:11 UTC --- casaregno:~ # cat /proc/driver/rtc rtc_time : 23:00:34 rtc_date : 2013-07-16 alrm_time : 18:00:00 alrm_date : 2013-07-17 alarm_IRQ : no alrm_pending : no update IRQ enabled : no periodic IRQ enabled : no periodic IRQ frequency : 1024 max user IRQ frequency : 64 24hr : yes periodic_IRQ : no update_IRQ : no HPET_emulated : yes BCD : yes DST_enable : no periodic_freq : 1024 batt_status : okay casaregno:~ # rtcwake -s 120 rtcwake: suspend to "standby" unavailable casaregno:~ # cat /proc/driver/rtc rtc_time : 23:00:57 rtc_date : 2013-07-16 alrm_time : 18:00:00 alrm_date : 2013-07-17 alarm_IRQ : no alrm_pending : no update IRQ enabled : no periodic IRQ enabled : no periodic IRQ frequency : 1024 max user IRQ frequency : 64 24hr : yes periodic_IRQ : no update_IRQ : no HPET_emulated : yes BCD : yes DST_enable : no periodic_freq : 1024 batt_status : okay casaregno:~ # rtcwake -s 300 rtcwake: suspend to "standby" unavailable casaregno:~ # cat /proc/driver/rtc rtc_time : 23:02:13 rtc_date : 2013-07-16 alrm_time : 18:00:00 alrm_date : 2013-07-17 alarm_IRQ : no alrm_pending : no update IRQ enabled : no periodic IRQ enabled : no periodic IRQ frequency : 1024 max user IRQ frequency : 64 24hr : yes periodic_IRQ : no update_IRQ : no HPET_emulated : yes BCD : yes DST_enable : no periodic_freq : 1024 batt_status : okay casaregno:~ # -- 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=812592 https://bugzilla.novell.com/show_bug.cgi?id=812592#c9 --- Comment #9 from Borislav Petkov <bpetkov@suse.com> 2013-07-17 09:39:07 UTC --- Hmm, you can't even set the alarm properly: rtcwake: suspend to "standby" unavailable We have a similar issue with another machine and this looks more and more like a BIOS bug. But you're already running the latest BIOS so... You can try to revert the patch I mentioned in comment #2 to confirm. If you don't know how to do that, let me know and I'll build a kernel for you. HTH. -- 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=812592 https://bugzilla.novell.com/show_bug.cgi?id=812592#c11 --- Comment #11 from Borislav Petkov <bpetkov@suse.com> 2013-07-17 14:24:11 UTC --- Try this one here: http://beta.suse.com/private/bpetkov/kernel-default-3.7.10-0.x86_64.rpm -- 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=812592 https://bugzilla.novell.com/show_bug.cgi?id=812592#c13 --- Comment #13 from Borislav Petkov <bpetkov@suse.com> 2013-07-18 14:48:06 UTC --- Ok, good. What does cat /sys/class/dmi/id/sys_vendor cat /sys/class/dmi/id/product_name say? 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=812592 https://bugzilla.novell.com/show_bug.cgi?id=812592#c15 Robin Klitscher <robnk@xtra.co.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |robnk@xtra.co.nz --- Comment #15 from Robin Klitscher <robnk@xtra.co.nz> 2013-07-18 23:02:22 UTC --- I have pretty much the same problem. Can't poweroff an oS 12.3 system without holding in the physical "Off" button to prevent the machine cycling into reboot. Happens always. Only main differences seem to be that this is not an upgrade to, but a fresh install of, oS 12.3 64-bit (KDE 4.10.5) onto a new machine (Intel Core i7 4770 on an Intel DH87MC motherboard); and that it's dual-boot alongside a new installation of Win 7 64-bit. Both Win 7 and oS 12.3 are fully updated, the latter from stable repositories. The significant thing about this would have to be that the problem occurs only from oS 12.3. Shutdown from Win 7 proceeds to conclusion as it should. I can find no reason for this behaviour in the Intel Visual BIOS (legacy boot, not UEFI) and, since the problem occurs with oS 12.3 and not with Win 7, it seems pretty clear that the problem lies with openSUSE 12.3. -- 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=812592 https://bugzilla.novell.com/show_bug.cgi?id=812592#c17 --- Comment #17 from Robin Klitscher <robnk@xtra.co.nz> 2013-07-18 23:54:41 UTC --- (In reply to comment #16)

Do you have some option in the BIOS which says something about wakeup machine.. whatever and that option is enabled?

If you disable it, does the machine remain off?

Sorry; No such option that I can find. But even if there were it would not necessarily explain why I can shutdown properly from Win 7 while from oS 12.3 on the same machine it always reboots.

Can you try this kernel here:

http://beta.suse.com/private/bpetkov/kernel-default-3.7.10-0.x86_64.rpm

Slightly reluctant to do that unless strictly necessary. Is it?

What does

cat /sys/class/dmi/id/sys_vendor cat /sys/class/dmi/id/product_name

say?

Nothing in either case. Just a blank return. The files exist at 4kb each, but there doesn't appear to be anything readable in them.

That should be all for now :)

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=812592 https://bugzilla.novell.com/show_bug.cgi?id=812592#c19 --- Comment #19 from Robin Klitscher <robnk@xtra.co.nz> 2013-07-19 22:27:04 UTC --- Yes; I understand about trying the alternative kernel, but was just being cautious. I've now installed your 3.7.10-0.x86_64 and booted to it. Tried shutdown -h from the commandline, but there was no change in behaviour - the machine didn't poweroff, but rebooted as before. (Had to issue the shutdown command from the commandline because I use the nVidia proprietary video drivers and they wouldn't compile against that kernel). Here's the contents of dmidecode.log (please excuse my ignorance, but is there another way of uploading this kind of stuff???): # dmidecode 2.11 SMBIOS 2.7 present. 81 structures occupying 3305 bytes. Table at 0x000EB8B0. Handle 0x0000, DMI type 0, 24 bytes BIOS Information Vendor: Intel Corp. Version: MCH8710H.86A.0047.2013.0606.1508 Release Date: 06/06/2013 Address: 0xF0000 Runtime Size: 64 kB ROM Size: 6656 kB Characteristics: PCI is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported BIOS ROM is socketed EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported BIOS boot specification is supported Function key-initiated network boot is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 4.6 Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: Product Name: Version: Serial Number: UUID: 331C1E90-92BE-E211-89D3-505054503030 Wake-up Type: Power Switch SKU Number: To be filled by O.E.M. Family: To be filled by O.E.M. Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: Intel Corporation Product Name: DH87MC Version: AAG74242-401 Serial Number: BTMC32000MF1 Asset Tag: To be filled by O.E.M. Features: Board is a hosting board Board is replaceable Location In Chassis: To be filled by O.E.M. Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 Handle 0x0003, DMI type 3, 22 bytes Chassis Information Manufacturer: Type: Desktop Lock: Not Present Version: Serial Number: Asset Tag: Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: None OEM Information: 0x00000000 Height: Unspecified Number Of Power Cords: 1 Contained Elements: 0 SKU Number: To be filled by O.E.M. Handle 0x0004, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J1A1 Internal Connector Type: None External Reference Designator: PS2Mouse External Connector Type: PS/2 Port Type: Mouse Port Handle 0x0005, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J1A1 Internal Connector Type: None External Reference Designator: Keyboard External Connector Type: PS/2 Port Type: Keyboard Port Handle 0x0006, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J2A1 Internal Connector Type: None External Reference Designator: TV Out External Connector Type: Mini Centronics Type-14 Port Type: Other Handle 0x0007, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J2A2A Internal Connector Type: None External Reference Designator: COM A External Connector Type: DB-9 male Port Type: Serial Port 16550A Compatible Handle 0x0008, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J2A2B Internal Connector Type: None External Reference Designator: Video External Connector Type: DB-15 female Port Type: Video Port Handle 0x0009, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J3A1 Internal Connector Type: None External Reference Designator: USB1 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x000A, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J3A1 Internal Connector Type: None External Reference Designator: USB2 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x000B, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J3A1 Internal Connector Type: None External Reference Designator: USB3 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x000C, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J9A1 - TPM HDR Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x000D, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J9C1 - PCIE DOCKING CONN Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x000E, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J2B3 - CPU FAN Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x000F, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J6C2 - EXT HDMI Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x0010, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J3C1 - GMCH FAN Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x0011, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J1D1 - ITP Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x0012, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J9E2 - MDC INTPSR Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x0013, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J9E4 - MDC INTPSR Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x0014, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J9E3 - LPC HOT DOCKING Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x0015, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J9E1 - SCAN MATRIX Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x0016, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J9G1 - LPC SIDE BAND Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x0017, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J8F1 - UNIFIED Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x0018, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J6F1 - LVDS Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x0019, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J2F1 - LAI FAN Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x001A, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J2G1 - GFX VID Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x001B, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J1G6 - AC JACK Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x001C, DMI type 9, 17 bytes System Slot Information Designation: PCIe X16 Type: x16 PCI Express 2 x16 Current Usage: In Use Length: Long ID: 6 Characteristics: 3.3 V is provided Opening is shared PME signal is supported Bus Address: 0000:00:01.0 Handle 0x001D, DMI type 10, 10 bytes On Board Device 1 Information Type: Video Status: Disabled Description: Intel(R) HD Graphics Device On Board Device 2 Information Type: Ethernet Status: Enabled Description: Intel(R) WGI217V Gigabit Network Device On Board Device 3 Information Type: Sound Status: Enabled Description: ALC892-GR Handle 0x001E, DMI type 11, 5 bytes OEM Strings String 1: To Be Filled By O.E.M. Handle 0x001F, DMI type 12, 5 bytes System Configuration Options Option 1: To Be Filled By O.E.M. Handle 0x0020, DMI type 24, 5 bytes Hardware Security Power-On Password Status: Disabled Keyboard Password Status: Disabled Administrator Password Status: Disabled Front Panel Reset Status: Disabled Handle 0x0021, DMI type 32, 20 bytes System Boot Information Status: No errors detected Handle 0x0022, DMI type 34, 11 bytes Management Device Description: LM78-1 Type: LM78 Address: 0x00000000 Address Type: I/O Port Handle 0x0023, DMI type 26, 22 bytes Voltage Probe Description: LM78A Location: <OUT OF SPEC> Status: <OUT OF SPEC> Maximum Value: Unknown Minimum Value: Unknown Resolution: Unknown Tolerance: Unknown Accuracy: Unknown OEM-specific Information: 0x00000000 Nominal Value: Unknown Handle 0x0024, DMI type 36, 16 bytes Management Device Threshold Data Lower Non-critical Threshold: 1 Upper Non-critical Threshold: 2 Lower Critical Threshold: 3 Upper Critical Threshold: 4 Lower Non-recoverable Threshold: 5 Upper Non-recoverable Threshold: 6 Handle 0x0025, DMI type 35, 11 bytes Management Device Component Description: To Be Filled By O.E.M. Management Device Handle: 0x0022 Component Handle: 0x0022 Threshold Handle: 0x0023 Handle 0x0026, DMI type 28, 22 bytes Temperature Probe Description: LM78A Location: <OUT OF SPEC> Status: <OUT OF SPEC> Maximum Value: Unknown Minimum Value: Unknown Resolution: Unknown Tolerance: Unknown Accuracy: Unknown OEM-specific Information: 0x00000000 Nominal Value: Unknown Handle 0x0027, DMI type 36, 16 bytes Management Device Threshold Data Lower Non-critical Threshold: 1 Upper Non-critical Threshold: 2 Lower Critical Threshold: 3 Upper Critical Threshold: 4 Lower Non-recoverable Threshold: 5 Upper Non-recoverable Threshold: 6 Handle 0x0028, DMI type 35, 11 bytes Management Device Component Description: To Be Filled By O.E.M. Management Device Handle: 0x0022 Component Handle: 0x0025 Threshold Handle: 0x0026 Handle 0x0029, DMI type 27, 15 bytes Cooling Device Temperature Probe Handle: 0x0026 Type: <OUT OF SPEC> Status: <OUT OF SPEC> Cooling Unit Group: 1 OEM-specific Information: 0x00000000 Nominal Speed: Unknown Or Non-rotating Description: Cooling Dev 1 Handle 0x002A, DMI type 36, 16 bytes Management Device Threshold Data Lower Non-critical Threshold: 1 Upper Non-critical Threshold: 2 Lower Critical Threshold: 3 Upper Critical Threshold: 4 Lower Non-recoverable Threshold: 5 Upper Non-recoverable Threshold: 6 Handle 0x002B, DMI type 35, 11 bytes Management Device Component Description: To Be Filled By O.E.M. Management Device Handle: 0x0022 Component Handle: 0x0028 Threshold Handle: 0x0029 Handle 0x002C, DMI type 27, 15 bytes Cooling Device Temperature Probe Handle: 0x0026 Type: <OUT OF SPEC> Status: <OUT OF SPEC> Cooling Unit Group: 1 OEM-specific Information: 0x00000000 Nominal Speed: Unknown Or Non-rotating Description: Not Specified Handle 0x002D, DMI type 36, 16 bytes Management Device Threshold Data Lower Non-critical Threshold: 1 Upper Non-critical Threshold: 2 Lower Critical Threshold: 3 Upper Critical Threshold: 4 Lower Non-recoverable Threshold: 5 Upper Non-recoverable Threshold: 6 Handle 0x002E, DMI type 35, 11 bytes Management Device Component Description: To Be Filled By O.E.M. Management Device Handle: 0x0022 Component Handle: 0x002B Threshold Handle: 0x002C Handle 0x002F, DMI type 29, 22 bytes Electrical Current Probe Description: ABC Location: <OUT OF SPEC> Status: <OUT OF SPEC> Maximum Value: Unknown Minimum Value: Unknown Resolution: Unknown Tolerance: Unknown Accuracy: Unknown OEM-specific Information: 0x00000000 Nominal Value: Unknown Handle 0x0030, DMI type 36, 16 bytes Management Device Threshold Data Handle 0x0031, DMI type 35, 11 bytes Management Device Component Description: To Be Filled By O.E.M. Management Device Handle: 0x0022 Component Handle: 0x002E Threshold Handle: 0x002C Handle 0x0032, DMI type 26, 22 bytes Voltage Probe Description: LM78A Location: Power Unit Status: OK Maximum Value: Unknown Minimum Value: Unknown Resolution: Unknown Tolerance: Unknown Accuracy: Unknown OEM-specific Information: 0x00000000 Nominal Value: Unknown Handle 0x0033, DMI type 28, 22 bytes Temperature Probe Description: LM78A Location: Power Unit Status: OK Maximum Value: Unknown Minimum Value: Unknown Resolution: Unknown Tolerance: Unknown Accuracy: Unknown OEM-specific Information: 0x00000000 Nominal Value: Unknown Handle 0x0034, DMI type 27, 15 bytes Cooling Device Temperature Probe Handle: 0x0033 Type: Power Supply Fan Status: OK Cooling Unit Group: 1 OEM-specific Information: 0x00000000 Nominal Speed: Unknown Or Non-rotating Description: Cooling Dev 1 Handle 0x0035, DMI type 29, 22 bytes Electrical Current Probe Description: ABC Location: Power Unit Status: OK Maximum Value: Unknown Minimum Value: Unknown Resolution: Unknown Tolerance: Unknown Accuracy: Unknown OEM-specific Information: 0x00000000 Nominal Value: Unknown Handle 0x0036, DMI type 39, 22 bytes System Power Supply Power Unit Group: 1 Location: To Be Filled By O.E.M. Name: To Be Filled By O.E.M. Manufacturer: To Be Filled By O.E.M. Serial Number: To Be Filled By O.E.M. Asset Tag: To Be Filled By O.E.M. Model Part Number: To Be Filled By O.E.M. Revision: To Be Filled By O.E.M. Max Power Capacity: Unknown Status: Present, OK Type: Switching Input Voltage Range Switching: Auto-switch Plugged: Yes Hot Replaceable: No Input Voltage Probe Handle: 0x0032 Cooling Device Handle: 0x0034 Input Current Probe Handle: 0x0035 Handle 0x0037, DMI type 41, 11 bytes Onboard Device Reference Designation: CPU Type: Video Status: Disabled Type Instance: 1 Bus Address: 0000:00:02.0 Handle 0x0038, DMI type 41, 11 bytes Onboard Device Reference Designation: U10 Type: Ethernet Status: Enabled Type Instance: 1 Bus Address: 0000:00:19.0 Handle 0x0039, DMI type 41, 11 bytes Onboard Device Reference Designation: AU1 Type: Sound Status: Enabled Type Instance: 1 Bus Address: 0000:00:1b.0 Handle 0x003A, DMI type 4, 42 bytes Processor Information Socket Designation: CPU 1 Type: Central Processor Family: Core i7 Manufacturer: Intel(R) Corp. ID: C3 06 03 00 FF FB EB BF Signature: Type 0, Family 6, Model 60, Stepping 3 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) DE (Debugging extension) PSE (Page size extension) TSC (Time stamp counter) MSR (Model specific registers) PAE (Physical address extension) MCE (Machine check exception) CX8 (CMPXCHG8 instruction supported) APIC (On-chip APIC hardware supported) SEP (Fast system call) MTRR (Memory type range registers) PGE (Page global enable) MCA (Machine check architecture) CMOV (Conditional move instruction supported) PAT (Page attribute table) PSE-36 (36-bit page size extension) CLFSH (CLFLUSH instruction supported) DS (Debug store) ACPI (ACPI supported) MMX (MMX technology supported) FXSR (FXSAVE and FXSTOR instructions supported) SSE (Streaming SIMD extensions) SSE2 (Streaming SIMD extensions 2) SS (Self-snoop) HTT (Multi-threading) TM (Thermal monitor supported) PBE (Pending break enabled) Version: Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz Voltage: 1.2 V External Clock: 100 MHz Max Speed: 3800 MHz Current Speed: 3400 MHz Status: Populated, Enabled Upgrade: Socket BGA1155 L1 Cache Handle: 0x003C L2 Cache Handle: 0x003B L3 Cache Handle: 0x003D Serial Number: Not Specified Asset Tag: Fill By OEM Part Number: Fill By OEM Core Count: 4 Core Enabled: 4 Thread Count: 8 Characteristics: 64-bit capable Handle 0x003B, DMI type 7, 19 bytes Cache Information Socket Designation: CPU Internal L2 Configuration: Enabled, Not Socketed, Level 2 Operational Mode: Write Back Location: Internal Installed Size: 1024 kB Maximum Size: 1024 kB Supported SRAM Types: Unknown Installed SRAM Type: Unknown Speed: Unknown Error Correction Type: Single-bit ECC System Type: Unified Associativity: 8-way Set-associative Handle 0x003C, DMI type 7, 19 bytes Cache Information Socket Designation: CPU Internal L1 Configuration: Enabled, Not Socketed, Level 1 Operational Mode: Write Back Location: Internal Installed Size: 256 kB Maximum Size: 256 kB Supported SRAM Types: Unknown Installed SRAM Type: Unknown Speed: Unknown Error Correction Type: Single-bit ECC System Type: Other Associativity: 8-way Set-associative Handle 0x003D, DMI type 7, 19 bytes Cache Information Socket Designation: CPU Internal L3 Configuration: Enabled, Not Socketed, Level 3 Operational Mode: Write Back Location: Internal Installed Size: 8192 kB Maximum Size: 8192 kB Supported SRAM Types: Unknown Installed SRAM Type: Unknown Speed: Unknown Error Correction Type: Single-bit ECC System Type: Unified Associativity: 16-way Set-associative Handle 0x003E, DMI type 16, 23 bytes Physical Memory Array Location: System Board Or Motherboard Use: System Memory Error Correction Type: None Maximum Capacity: 32 GB Error Information Handle: Not Provided Number Of Devices: 4 Handle 0x003F, DMI type 17, 34 bytes Memory Device Array Handle: 0x003E Error Information Handle: Not Provided Total Width: 64 bits Data Width: 64 bits Size: 8192 MB Form Factor: DIMM Set: None Locator: DIMM 3 Bank Locator: Channel A Slot 0 Type: DDR3 Type Detail: Synchronous Speed: 1600 MHz Manufacturer: Transcend Serial Number: 00092415 Asset Tag: 9876543210 Part Number: JM1600KLH-8G Rank: 2 Configured Clock Speed: 1600 MHz Handle 0x0040, DMI type 20, 35 bytes Memory Device Mapped Address Starting Address: 0x00000000000 Ending Address: 0x001FFFFFFFF Range Size: 8 GB Physical Device Handle: 0x003F Memory Array Mapped Address Handle: 0x0047 Partition Row Position: Unknown Interleave Position: 1 Interleaved Data Depth: 2 Handle 0x0041, DMI type 17, 34 bytes Memory Device Array Handle: 0x003E Error Information Handle: Not Provided Total Width: 64 bits Data Width: 64 bits Size: 8192 MB Form Factor: DIMM Set: None Locator: DIMM 1 Bank Locator: Channel A Slot 1 Type: DDR3 Type Detail: Synchronous Speed: 1600 MHz Manufacturer: Transcend Serial Number: 00092415 Asset Tag: 9876543210 Part Number: JM1600KLH-8G Rank: 2 Configured Clock Speed: 1600 MHz Handle 0x0042, DMI type 20, 35 bytes Memory Device Mapped Address Starting Address: 0x00400000000 Ending Address: 0x005FFFFFFFF Range Size: 8 GB Physical Device Handle: 0x0041 Memory Array Mapped Address Handle: 0x0047 Partition Row Position: Unknown Interleave Position: 1 Interleaved Data Depth: 2 Handle 0x0043, DMI type 17, 34 bytes Memory Device Array Handle: 0x003E Error Information Handle: Not Provided Total Width: 64 bits Data Width: 64 bits Size: 8192 MB Form Factor: DIMM Set: None Locator: DIMM 4 Bank Locator: Channel B Slot 0 Type: DDR3 Type Detail: Synchronous Speed: 1600 MHz Manufacturer: Transcend Serial Number: 00092415 Asset Tag: 9876543210 Part Number: JM1600KLH-8G Rank: 2 Configured Clock Speed: 1600 MHz Handle 0x0044, DMI type 20, 35 bytes Memory Device Mapped Address Starting Address: 0x00200000000 Ending Address: 0x003FFFFFFFF Range Size: 8 GB Physical Device Handle: 0x0043 Memory Array Mapped Address Handle: 0x0047 Partition Row Position: Unknown Interleave Position: 2 Interleaved Data Depth: 2 Handle 0x0045, DMI type 17, 34 bytes Memory Device Array Handle: 0x003E Error Information Handle: Not Provided Total Width: 64 bits Data Width: 64 bits Size: 8192 MB Form Factor: DIMM Set: None Locator: DIMM 2 Bank Locator: Channel B Slot 1 Type: DDR3 Type Detail: Synchronous Speed: 1600 MHz Manufacturer: Transcend Serial Number: 00092415 Asset Tag: 9876543210 Part Number: JM1600KLH-8G Rank: 2 Configured Clock Speed: 1600 MHz Handle 0x0046, DMI type 20, 35 bytes Memory Device Mapped Address Starting Address: 0x00600000000 Ending Address: 0x007FFFFFFFF Range Size: 8 GB Physical Device Handle: 0x0045 Memory Array Mapped Address Handle: 0x0047 Partition Row Position: Unknown Interleave Position: 2 Interleaved Data Depth: 2 Handle 0x0047, DMI type 19, 31 bytes Memory Array Mapped Address Starting Address: 0x00000000000 Ending Address: 0x007FFFFFFFF Range Size: 32 GB Physical Array Handle: 0x003E Partition Width: 4 Handle 0x0058, DMI type 131, 64 bytes OEM-specific Type Header and Data: 83 40 58 00 35 00 00 00 00 00 00 00 00 00 00 00 F8 00 4A 8C 00 00 00 00 01 20 00 00 00 00 09 00 41 05 02 00 00 00 00 00 C8 00 3B 15 00 00 00 00 00 00 00 00 66 00 00 00 76 50 72 6F 00 00 00 00 Handle 0x0059, DMI type 13, 22 bytes BIOS Language Information Language Description Format: Long Installable Languages: 1 en|US|iso8859-1 Currently Installed Language: en|US|iso8859-1 Handle 0x005C, DMI type 9, 17 bytes System Slot Information Designation: PCIe x1 Type: x1 PCI Express 2 x1 Current Usage: Available Length: Short ID: 7 Characteristics: 3.3 V is provided Opening is shared PME signal is supported Bus Address: 0000:00:1c.5 Handle 0x005D, DMI type 9, 17 bytes System Slot Information Designation: PCIe x1 Type: x1 PCI Express 2 x1 Current Usage: Available Length: Short ID: 5 Characteristics: 3.3 V is provided Opening is shared PME signal is supported Bus Address: 0000:00:1c.6 Handle 0x005E, DMI type 9, 17 bytes System Slot Information Designation: PCIe x4 Type: x4 PCI Express 2 x4 Current Usage: Available Length: Short ID: 4 Characteristics: 3.3 V is provided Opening is shared PME signal is supported Bus Address: 0000:00:1c.1 Handle 0x005F, DMI type 9, 17 bytes System Slot Information Designation: PCI Type: 32-bit PCI Current Usage: Available Length: Short ID: 3 Characteristics: 3.3 V is provided Opening is shared PME signal is supported Bus Address: 0000:03:00.0 Handle 0x0060, DMI type 9, 17 bytes System Slot Information Designation: PCI Type: 32-bit PCI Current Usage: Available Length: Short ID: 2 Characteristics: 3.3 V is provided Opening is shared PME signal is supported Bus Address: 0000:03:01.0 Handle 0x0061, DMI type 9, 17 bytes System Slot Information Designation: PCI Type: 32-bit PCI Current Usage: Available Length: Short ID: 1 Characteristics: 3.3 V is provided Opening is shared PME signal is supported Bus Address: 0000:03:02.0 Handle 0x0062, DMI type 127, 4 bytes End Of Table -- 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=812592 https://bugzilla.novell.com/show_bug.cgi?id=812592#c21 --- Comment #21 from Robin Klitscher <robnk@xtra.co.nz> 2013-07-22 22:19:40 UTC --- (In reply to comment #20)

(In reply to comment #19)

...

Yes; I understand about trying the alternative kernel, but was just being cautious.

About what exactly?

Nothing rational - just being over-conservative.

...

I've now installed your 3.7.10-0.x86_64 and booted to it. Tried shutdown -h from the commandline, but there was no change in behaviour - the machine didn't poweroff, but rebooted as before.

Which means this is a different issue. Because the patch I was testing fixes the issue on two other boxes.

...

(Had to issue the shutdown command from the commandline because I use the nVidia proprietary video drivers and they wouldn't compile against that kernel).

Well, you know we can't help you with proprietary drivers installed, right?

Perhaps so. But the point I was making still holds. Without the proprietary nVidia drivers loaded - or any video drivers for that matter - the errant shutdown behaviour remains unchanged from the commandline. Which suggests, does it not, that the problem lies elsewhere in the system than with video drivers or the GUI?

...

Here's the contents of dmidecode.log (please excuse my ignorance, but is there another way of uploading this kind of stuff???):

Yep, there's "Add an attachment" link in the bugzilla with which you can upload files.

Sorry; I see it now but failed to find it previously.

...

# dmidecode 2.11 SMBIOS 2.7 present. 81 structures occupying 3305 bytes. Table at 0x000EB8B0.

Handle 0x0000, DMI type 0, 24 bytes BIOS Information

...

<etc>

Great, those are simply strings full of 0x20 chars, i.e. spaces. Talk about the notorious crappiness of DMI tables...

Ok, so your BIOS looks recent. Did this box shutdown properly with any kernel and without the proprietary drivers?

The desktop board is new - Intel DH87MC - purchased two weeks ago. The BIOS is updated to the latest available - 6 Jun 2013 (it's Intel's new "Visual BIOS", which offers a GUI-style interface rather than the traditional text-based interface; and it takes a little getting used to). But to answer your question, right from the beginning the machine has powered off properly from Win 7, but not from oS 12.3. This has been the case whether the video be the default nouveau drivers or the proprietary nVidia drivers; no difference. It has also been the case with any of the stable kernel updates offered by the oS 12.3 Update channel (currently 3.7.10-1.16-desktop); and now also with your 3.7.10-0-default

Also, what happens if you boot the kernel with "acpi=off", does it shutdown properly then?

Sadly, no; not with either the default 3.7.10-1.16 kernel, or your 3.7.10-0. But the behaviour changes a bit. The system "halts", but then doesn't progress to power off - just sits there, power still on but unresponsive until I use the physical "Off".

Thanks.

And thanks to you, too. -- 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=812592 https://bugzilla.novell.com/show_bug.cgi?id=812592#c23 --- Comment #23 from Robin Klitscher <robnk@xtra.co.nz> 2013-07-26 08:27:51 UTC --- (In reply to comment #22)

Ok, so we still don't know if any Linux kernel has powered down your machine properly. So let's try the upstream one:

http://download.opensuse.org/repositories/Kernel:/vanilla/standard/x86_64/

See if this one works.

Also, try different methods like

* shutdown -h now * halt -p * poweroff

...

Thanks.

OK; I've done all that using the various shutdown commands and parameter options, both with the default 3.7.10-1.16 kernel and with the upstream "vanilla" 3.11.rc2 version you suggested. None of it made any difference - I still get a reboot instead of a poweroff. The fact that the incorrect behaviour occurs under openSUSE 12.3 (64-bit) but not under Win 7 (64-bit) strongly suggests that it's not down to a setting I'm missing in BIOS. But I now have some further information which might or might not be useful. I get the same bad behaviour under Stephen Shiau's latest Clonezilla Live, whether loaded from CD or from hard drive. But then, confusingly, under Patrick Verner's Parted Magic loaded into RAM from his CD, shutdown proceeds to full power-off completion as it should. So we have it working properly in Win 7 and the latest Slackware-based Parted Magic, but not working in openSUSE 12.1 or Debian-based Clonezilla. Curiouser and curiouser; but is there a clue in there somewhere? -- 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=812592 https://bugzilla.novell.com/show_bug.cgi?id=812592#c25 --- Comment #25 from Robin Klitscher <robnk@xtra.co.nz> 2013-07-27 03:00:46 UTC --- (In reply to comment #24)

For starters, which kernel are you using with Parted Magic? You could try to build that exact kernel and boot it on oS. If it works, then we can start bisecting it from there.

Feel free to ask if you have any questions how to do that exactly.

OK; with Parted Magic up and running, uname -r returns 3.8.14-pmagic64 Beyond that, I understand what you're saying but am not sure how to do it. It's years - more than 10 and in RedHat 7 or thereabouts - since I last compiled a custom kernel. So I'm in loose territory somewhere between a geek and an ordinary ignorant user, but closer to the latter, and could do with some help on how to go about this. -- 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=812592 https://bugzilla.novell.com/show_bug.cgi?id=812592#c27 Borislav Petkov <bpetkov@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bpoirier@suse.com --- Comment #27 from Borislav Petkov <bpetkov@suse.com> 2013-07-30 18:10:53 UTC --- Definitely interesting. Can you add "ignore_loglevel debug" on the kernel command line and boot * the oS 12.3 and * the parted magic kernels, once with "Wake on LAN from S4/S5" enabled and once with that same option disabled. Each time you do that, please do dmesg > dmesg-[some-unique-name].log and zip those 4 log files and upload the archive to the bugzilla. It could be that depending on WOL settings, the card is doing different things when powering down the PHY (that would actually need dmesg on powerdown too but for that you'd need some sort of console like serial. Perhaps we can see something in the logs now too). @Benjamin: Does comment #26 ring any bells? 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=812592 https://bugzilla.novell.com/show_bug.cgi?id=812592#c29 --- Comment #29 from Robin Klitscher <robnk@xtra.co.nz> 2013-07-31 00:38:58 UTC --- Done per #27 The filenames should be self-evident. "wol off/on" refers to the mainboard's "Wake on LAN from S4/S5" switch only. The wol property of the embedded ethernet device was left enabled througout. I hope the contents are useful - and thank you for your perseverance -- 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=812592 https://bugzilla.novell.com/show_bug.cgi?id=812592#c31 --- Comment #31 from Robin Klitscher <robnk@xtra.co.nz> 2013-08-02 06:44:56 UTC --- (In reply to comment #30)

...

(In reply to comment #25)

Before we go any further, some new information.

On the vague chance that the problem might have something to do with wake-on-LAN, I'd previously tried disabling WOL at the level of the onboard NIC (Intel I217V Gigabit ethernet controller).

Through which interface had you done this?

Within Intel's new Visual BIOS interface under "Advanced" there is there is a page called Devices -> Add-in configuration -> Ethernet Network Connection -> Configure. This opens yet another page which shows the various configurable items for the onboard NIC, one of which is enable/disable Wake on LAN. So the answer to your question, I guess, is the BIOS interface. (As I indicated previously, however, there is also the mainboard switch labelled "Wake on LAN from S4/S5" which offers three choices - Normal Boot; PXE Boot; and Do Nothing (or similar). -- 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=812592 https://bugzilla.novell.com/show_bug.cgi?id=812592#c Borislav Petkov <bpetkov@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |robnk@xtra.co.nz -- 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=812592 https://bugzilla.novell.com/show_bug.cgi?id=812592#c34 --- Comment #34 from Robin Klitscher <robnk@xtra.co.nz> 2013-08-07 01:06:26 UTC --- (In reply to comment #33)

Robin,

I recently reported a similar issue to the e1000-devel ML but am not able to reproduce it anymore. Intel people had a couple of good suggestions, willing to give them a try: http://marc.info/?l=linux-kernel&m=137530520232101&w=2

Thanks.

Borislav, I'm not entirely clear about whether you are suggesting I should switch discussion to the ML you mention, or simply try the things mentioned in the post you cite. Whatever; for the record I've tried disconnecting the LAN cable as mentioned. It made no difference. With "Wake on LAN from S4/S5" selected to "Normal Boot" I still get an uncommanded reboot irrespective of whether the LAN cable is connected or disconnected; or whether the built-in ethernet controller's WOL setting is set to on or off. The only condition where the machine shuts down on poweroff is with the mainboard's "Wake on LAN from S4/S5" set to "Stay Off". As to the other suggestions in the e1000-devel ML post, the BIOS is at the latest level (from Intel; 0047 dated 6 June). And I can't find a "Runtime Power Management" item (or believably similar) anywhere in the Visual BIOS menus. Regards, Robin -- 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=812592 https://bugzilla.novell.com/show_bug.cgi?id=812592#c36 --- Comment #36 from Robin Klitscher <robnk@xtra.co.nz> 2013-08-08 10:43:48 UTC --- (In reply to comment #35)

Hello Robin,

Here are two packages for you to test: 1) kernel-pmagic In comment 23 you mentionned that shutdown from Parted Magic works well and in comment 25 you mentionned that it is running kernel 3.8.14-pmagic64. However, I couldn't find such a kernel. There is no 3.8.14 from the kernel.org linux-3.8.y branch and looking over the Parted Magic changelog (http://partedmagic.com/doku.php?id=changelog) there is no mention of it either.

Yes; you are quite right. I misreported the output from uname -r; it should have been 3.8.13, not 3.8.14. Mea culpa - sorry about that.

<snip>

The kernel is built from the following obs project https://build.opensuse.org/project/show/home:benjamin_poirier:bnc812592 and the rpm should appear here once obs has published it: http://download.opensuse.org/repositories/home:/benjamin_poirier:/bnc812592/

All I can find there is a noarch source rpm - should there be a full binary rpm? <snip>

The package is build from the following obs project https://build.opensuse.org/project/show/home:benjamin_poirier:branches:drive... and the rpm should appear here once obs has published it: http://download.opensuse.org/repositories/home:/benjamin_poirier:/branches:/...

and so far all I get from the latter URL is "Error 404" -- 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=812592 https://bugzilla.novell.com/show_bug.cgi?id=812592#c38 --- Comment #38 from Robin Klitscher <robnk@xtra.co.nz> 2013-08-09 03:42:33 UTC --- (In reply to comment #35)

Please give it a try in your 12.3 installation and report feedback. With this kernel, `modinfo e1000e` should report srcversion: 70E6653BA1595F95B1A8575

The kernel is built from the following obs project https://build.opensuse.org/project/show/home:benjamin_poirier:bnc812592 and the rpm should appear here once obs has published it: http://download.opensuse.org/repositories/home:/benjamin_poirier:/bnc812592/

OK; I downloaded the "pmagic" kernel RPM and installed it (also downloaded the devel package, but it wouldn't install because of dependency problems). "modinfo e1000e" returned the above src version correctly.

2) intel-e1000e This is a kernel module package (kmp) with the out-of-tree intel e1000e driver built from the sf.net project sources. This is the driver mentionned in the email thread linked to in comment 33.

Please try it with the default 12.3 kernel. Install the packages (intel-e1000e and intel-e1000e-kmp), shutdown and then boot. At this point, check that `modinfo e1000e` says srcversion: E08BFA31FFBE6A8F2869CB9 then shutdown and report feedback.

The package is build from the following obs project https://build.opensuse.org/project/show/home:benjamin_poirier:branches:drive... and the rpm should appear here once obs has published it: http://download.opensuse.org/repositories/home:/benjamin_poirier:/branches:/...

Also downloaded and installed both the e1000e rpms as requested (I used the "default" version - OK?). Again the srcversion was correct. I booted to the original openSUSE 12.3 kernel (3.7.10-1.16-desktop) with the two e1000e packages installed and active, but I still got the uncommanded reboot after poweroff. And I booted to the installed pmagic 3.8.13 kernel, both with and without the replacement e1000e packages. There was no improvement - I still got the reboot after poweroff. (Just for the record and by way of confirmation, I also booted from the PartedMagic CD and tried shutdown -h. It worked as advertised - no reboot.)

Note that once you install this kmp it will override the e1000e module for all kernel versions. So you should uninstall the package once you are done with it.

Done. -- 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=812592 https://bugzilla.novell.com/show_bug.cgi?id=812592#c40 --- Comment #40 from Robin Klitscher <robnk@xtra.co.nz> 2013-08-09 23:56:13 UTC --- (In reply to comment #39) Thank you. I've done all that, and although the results don't seem very helpful I hope they have some meaning! 1. "ethtool eth0" returns the following in both 12.3 and parted magic: Supports Wake-on: pumbg Wake-on: g I confirm that "ethtool -s eth0 wol d" under 12.3 does change the wol setting from "g" to "d". But it makes no difference to the shutdown behaviour - I still get a reboot from "shutdown -h now". [Comment: From previous experience with another machine and an earlier version of openSUSE and using an add-in PCI ethernet card, I remember that I had to alter one of the shutdown scripts to ensure that the desired wol setting survived the shutdown process itself. But that was under sysvinit, and I've no idea whether a similar kind of thing might apply under systemd] 2. I haven't attached the output files for "ethregs" because it returns only the one identical line in each case, including 12.3 with the standard kernel, 12.3 with the parted kernel, and parted magic itself under chroot. The line is simply: "unknown device id=0x153b" [General comment: Strictly as an amateur in these things I'd thought the fact that, since the peripheral on/off wol settings for the embedded ethernet controller in the BIOS have no effect at all on the reboot-from-shutdown behaviour, but that the problem seems to turn exclusively on the mainboard "Wake on LAN from S4/S5" switch setting, there's a pretty strong suggestion that the cause lies somewhere other than in the eth0 settings themselves.] Thank you again for listening. Robin -- 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=812592 https://bugzilla.novell.com/show_bug.cgi?id=812592#c42 --- Comment #42 from Felix Miata <mrmazda@earthlink.net> 2013-10-20 09:51:35 UTC --- Created an attachment (id=564148) --> (http://bugzilla.novell.com/attachment.cgi?id=564148) uname -a, ifconfig -a, ethtool eth0, lspci -vv, hwinfo, dmidecode output I installed 12.3 alongside Vista on an i945/ICH7 Toshiba laptop that is not mine a couple of days ago. It would not shutdown from the KDM login menu, until after reading here, I changed the old fashioned AMI v1.70 BIOS setting "Critical Battery Wake-Up" from enabled to disabled. Instead of shutdown it would just shut KDM down leaving a login prompt on tty1. -- 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=812592 https://bugzilla.novell.com/show_bug.cgi?id=812592#c44 --- Comment #44 from Robin Klitscher <robnk@xtra.co.nz> 2013-12-26 20:39:24 UTC --- I've upgraded from oS 12.3 64-bit to 13.1 64-bit by way of clean install, not update, now running kernel 3.11.6-4-desktop on the same machine (i7-4770 CPU on system board Intel DM87MC). Have also upgraded the BIOS from version 0047 to 0153 because the release notes mention "Fixed issue with Wake on LAN." Despite all this I still have the problem that shutting the machine down with "Wake on LAN from S4/S5" set to "Normal Boot" invariably results in reboot, not poweroff. So we're no further ahead, it seems! Robin K -- 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=812592 https://bugzilla.novell.com/show_bug.cgi?id=812592#c46 --- Comment #46 from Robin Klitscher <robnk@xtra.co.nz> 2013-12-28 10:18:32 UTC --- Sure. And I've done just that - disabled WOL from S4/S5 Respectfully, however, that's not really the point. Two things: 1. I want to be able to start this machine remotely, and can't do so with that switch turned off. 2. The behaviour is an aberration and that's reason enough on its own to want the flaw to be fixed, whether the cause be oS-related or BIOS-related. But I can wait ...... Regards, Robin -- 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=812592 https://bugzilla.novell.com/show_bug.cgi?id=812592#c48 Borislav Petkov <bpetkov@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |NORESPONSE --- Comment #48 from Borislav Petkov <bpetkov@suse.com> 2014-03-05 22:05:30 UTC --- Issue seems forgotten, closing. Feel free to reopen if still of interest. -- 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=812592 https://bugzilla.novell.com/show_bug.cgi?id=812592#c50 Diego Ercolani <diego.ercolani@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |REOPENED Resolution|NORESPONSE | --- Comment #50 from Diego Ercolani <diego.ercolani@gmail.com> 2014-03-06 13:08:44 UTC --- The same here, the bugreport I have opened was (and actually is) related to the behave of my motherboard that doesn't shutdown by stock suse kernel. Actually I have kernel-*-3.11.10-7.1.x86_64 under 13.1 and I have the same behaviour. he only solution I have is to circumvent with a "halt" entry in grub2 and grub2-reboot 'halt' before issuing a shutdown. Thank you -- 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=812592 https://bugzilla.novell.com/show_bug.cgi?id=812592#c Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO CC| |tiwai@suse.com InfoProvider| |diego.ercolani@gmail.com -- 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=812592 https://bugzilla.novell.com/show_bug.cgi?id=812592#c53 --- Comment #53 from Robin Klitscher <robnk@xtra.co.nz> 2014-03-18 02:31:51 UTC --- (In reply to comment #51) I finally got around to installing 3.11.10-33.g17fc0f0-desktop (oS 13.1) Sadly, it made no difference - with WOL from S4/S5 enabled in BIOS, the shutdown command results in reboot, not power off. But I'll live with it ...... Robin -- 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=812592 https://bugzilla.novell.com/show_bug.cgi?id=812592#c55 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |robnk@xtra.co.nz --- Comment #55 from Takashi Iwai <tiwai@suse.com> 2014-03-18 07:15:25 UTC --- Any chance to test the recent upstream kernel (e.g. 3.13.x or 3.14-rc) for verifying whether the issue was already fixed in upstream? You can install the kernel from OBS Kernel:stable or Kernel:HEAD repo in addition to the running one. If the problem persists, we should report it rather to the upstream bugzilla. -- 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=812592 https://bugzilla.novell.com/show_bug.cgi?id=812592#c Swamp Workflow Management <swamp@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| |obs:running:2807:important -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=812592 Swamp Workflow Management <swamp@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|obs:running:2807:important | -- You are receiving this mail because: You are on the CC list for the bug.