[Bug 812592] New: poweroff/shutdown of an upgraded (from 12.1 to 12.3) system make only a reboot
https://bugzilla.novell.com/show_bug.cgi?id=812592 https://bugzilla.novell.com/show_bug.cgi?id=812592#c0 Summary: poweroff/shutdown of an upgraded (from 12.1 to 12.3) system make only a reboot Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: diego.ercolani@gmail.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0 systemd-195-13.14.1.x86_64 kernel-desktop-devel-3.7.10-1.1.1.x86_64 libkde4-4.10.0-1.2.1.x86_64 I've upgraded (with zypper dup) my home system from 12.1 to 12.3 and make an effort to have a coherent system but now I'm facing a problem regarding system shutdown as if I do a 1) kde shutdown 2) halt -p from shutdown 3) push the powerbutton to invoke ACPI shutdown system, only reboot and isn't possible to shutdown the system without: 1) pushing longer the power button 2) do an "halt" from the grub2 console Since I have other systems installed freshly from 12.3 and this is the only system that is doing this, I think something had gone wrong in upgrade of systemd files. So, I need you help to correct the behaviour as I can't find any document describing the shutdown architecture of opensuse 12.3 Thank you Reproducible: Always Steps to Reproduce: 1. 2. 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#c1
Diego Ercolani
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c
Jeff Mahoney
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c2
Borislav Petkov
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c3
--- Comment #3 from Diego Ercolani
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c4
--- Comment #4 from Diego Ercolani
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c5
--- Comment #5 from Diego Ercolani
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c6
--- Comment #6 from Borislav Petkov
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c7
--- Comment #7 from Diego Ercolani
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c8
--- Comment #8 from Diego Ercolani
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c9
--- Comment #9 from Borislav Petkov
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c10
--- Comment #10 from Diego Ercolani
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c11
--- Comment #11 from Borislav Petkov
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c12
--- Comment #12 from Diego Ercolani
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c13
--- Comment #13 from Borislav Petkov
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c14
--- Comment #14 from Diego Ercolani
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c15
Robin Klitscher
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c16
--- Comment #16 from Borislav Petkov
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c17
--- Comment #17 from Robin Klitscher
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#c18
--- Comment #18 from Borislav Petkov
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?
No, no one is forcing you to do anything - I'm just trying to verify whether your machine is affected by the same issue and if your machine doesn't reboot with this kernel, then we'll know.
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.
Strange. Can you upload dmidecode > dmidecode.log please? 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
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c20
--- Comment #20 from Borislav Petkov
Yes; I understand about trying the alternative kernel, but was just being cautious.
About what exactly?
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?
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.
# 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:
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? Also, what happens if you boot the kernel with "acpi=off", does it shutdown properly then? 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#c21
--- Comment #21 from Robin Klitscher
(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#c22
--- Comment #22 from Borislav Petkov
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c23
--- Comment #23 from Robin Klitscher
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#c24
--- Comment #24 from Borislav Petkov
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?
Yes, there is. Assuming this is a kernel issue, Parted Magic is using a good kernel while the Clonezilla and oS aren't. What would be nice is if we can find out now which exact patch is causing this issue. 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. 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#c25
--- Comment #25 from Robin Klitscher
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#c26
--- Comment #26 from Robin Klitscher
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c27
Borislav Petkov
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c28
--- Comment #28 from Robin Klitscher
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c29
--- Comment #29 from Robin Klitscher
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c30
--- Comment #30 from Benjamin Poirier
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
Might be interesting to see if that ever reports anything else.
(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? (In reply to comment #27)
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 netconsole could be useful here.
Perhaps we can see something in the logs now too).
@Benjamin: Does comment #26 ring any bells?
Alas, no. I'd speculate that the linux driver perhaps programs the card in such a way that it sends PME events spuriously. -- 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
(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#c33
--- Comment #33 from Borislav Petkov
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c
Borislav Petkov
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c
Borislav Petkov
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c34
--- Comment #34 from Robin Klitscher
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#c35
--- Comment #35 from Benjamin Poirier
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c36
--- Comment #36 from Robin Klitscher
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#c37
--- Comment #37 from Benjamin Poirier
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?
Sigh, yes. I've fixed the package and the rpm is there now.
<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"
Sorry, I had neglected the "Publish" flag in OBS. Both tests should be good to go now! -- 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
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#c39
--- Comment #39 from Benjamin Poirier
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c40
--- Comment #40 from Robin Klitscher
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c41
--- Comment #41 from Borislav Petkov
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c42
--- Comment #42 from Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c43
Diego Ercolani
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c44
--- Comment #44 from Robin Klitscher
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c45
Borislav Petkov
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c46
--- Comment #46 from Robin Klitscher
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c47
--- Comment #47 from Borislav Petkov
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c48
Borislav Petkov
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c49
--- Comment #49 from Robin Klitscher
Issue seems forgotten, closing. Feel free to reopen if still of interest.
Not forgotten, really. Just that it's probably not worth bothering all those people about it at this time. I'll live with it unless and until it becomes intrusive. Thanks.... 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#c50
Diego Ercolani
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c51
--- Comment #51 from Borislav Petkov
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c
Takashi Iwai
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c52
Diego Ercolani
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c53
--- Comment #53 from Robin Klitscher
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c54
--- Comment #54 from Robin Klitscher
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c55
Takashi Iwai
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c57
Borislav Petkov
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c
Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=812592
https://bugzilla.novell.com/show_bug.cgi?id=812592#c58
--- Comment #58 from Swamp Workflow Management
http://bugzilla.novell.com/show_bug.cgi?id=812592
Swamp Workflow Management
participants (1)
-
bugzilla_noreply@novell.com