Bug 14595

This may be a dumb question, but are you sure it's actually powering down the first time ?

What you describe would match a hung X (black screen) and incomplete shutdown.

What happens if you press and hold the power button after the first shutdown before you try to reboot ?  If that works, it sounds like you're hanging in poweroff.  You could try hitting ESC when the Mageia splashscreen shows up during the first shutdown; that will put it back into console mode and give you some idea of how far shutdown is getting.

CC: (none) => ftg

I am sure the laptop is powering down, or at least the led on it turns off and there is no noise of fan or hard disk.

I forgot to say that if, instead of turning it off, I click on reboot, there is no problem at all, it boots properly.

The laptop is a Toshiba Satellite C660-10D (http://www.toshiba.eu/discontinued-products/satellite-c660-10d/). It is the first time I have problems with it and Mageia.

Any idea on where the problem could be? Shall I better ask in the forum?

Well, it seems an upstream bug, because I tested a live USB of openSuse 13.2 which was released a couple of weeks ago, and the problem is also there.

So now I have more or less clear it is an upstrem bug, but of what component? Any idea?

Thank you

I've never heard of a bug that could survive a true poweroff, although I've run into situations where a reboot doesn't reset a hardware device in quite the same way that a poweroff does.

The only remaining thing I can think of is that some of the desktops/environments in Mageia have shutdown dialogs that ask you to choose what grub/lilo option you want for the next boot, rather than wait to have you choose at actual boot time.  The next boot usually undoes the one-time setting that the shutdown dialog sets, so if it's setting a boot option improperly, you could be booting garbage, and the garbage could be getting cleared by the unsuccessful reboot so that the next one works.

This is a longshot, as I would expect this feature more on reboot than poweroff, but at least on both rather than just poweroff.

What bootloader are you using ?  Do you ever see a shutdown dialog that asks you to choose ahead of time ?

If you have your machine set to boot from a CD or USB or floppy ahead of the hard disk, and you insert a bootable medium, does the bootable medium boot reliably without exhibiting the problem ?

(In reply to Frank Griffin from comment #4)
> I've never heard of a bug that could survive a true poweroff, although I've
> run into situations where a reboot doesn't reset a hardware device in quite
> the same way that a poweroff does.


Well, IINM it doesn't survive a true poweroff:

(In reply to Pana Sum from comment #0)

> 
> If I turn off the laptop, and before turning it on again I unplug it and
> remove the batteries, it will boot properly.
>

CC: (none) => marja11

That's why I asked for the intermediate test in comment#1 (do the software poweroff and then hold the power button down for good measure).  That falls between software poweroff and physically removing all power.

If that works, then the current kernel has an issue with software poweroff on his hardware.  If it doesn't work, it's probably a hardware problem on his end.

In the latter case, I guess the diagnostic procedure would be to disconnect as much hardware as possible (physically remove the CD/DVD drive, remove any USB devices, disable the network both wired and wifi, etc.), leaving only the harddisk, and retest.  If it works then, re-add the devices one by one until you find the one that isn't being correctly reset by software poweroff.

To test the harddisk, do as I suggested above.  Remove the harddisk, boot from the most current rescue CD/DVD, do a software poweroff, and then reboot the system again from the rescue CD/DVD.  If the problem doesn't occur, it's either the harddisk itself of something about the cauldron kernel vs. the rescue kernel.

To test the display itself, run XFdrake as root and uncheck the box that says Start X At Boot, and retry the test which will now reboot to a tty login.  If that works, the problem is the state in which X is leaving the display.

Hi, I have been doing some tests, disconnecting hardware using the BIOS, and the problem seems to be in the LAN. If in my BIOS I disable the built-in LAN the problem no longer appears. It could be a workaround because I use Wi-Fi and I don't need the wired connection, but it could be interesting to find out why in Mageia 4 it works well.

According to harddrake it is a RTL8101E/RTL8102E PCI Express Fast Ethernet controller, and it is using the module âr8169.

I installed 3.14.24-desktop-1.mga4 from Mageia 4 in my Mageia 5 beta installation and the problem is gone, so it seems a problem in the kernel.

Is there any way to look for changes related to the module r8169 between this kernel and the one used in cauldron?

(In reply to Pana Sum from comment #0)

> 
> I turn off my laptop using KDE, and the next time I want to turn it on, it
> only shows a black screen (it doesn't even show the BIOS). When this happens
> I have to turn the computer off by pressing 5 secs the button and then it
> boots ok.
> 
> If I turn off the laptop, and before turning it on again I unplug it and
> remove the batteries, it will boot properly.
> 
> It does not happen with Mageia 4 nor Windows. It happens with Mageia 5 beta
> 1 in a clean install.
> 
(In reply to Pana Sum from comment #7)
> Hi, I have been doing some tests, disconnecting hardware using the BIOS, and
> the problem seems to be in the LAN. If in my BIOS I disable the built-in LAN
> the problem no longer appears.  
....
> According to harddrake it is a RTL8101E/RTL8102E PCI Express Fast Ethernet
> controller, and it is using the module âr8169.

With different Realtek LAN adapters, but with the same module, the problem doesn't exist. Your card or BIOS must have something special :-/

(In reply to Pana Sum from comment #8)
> I installed 3.14.24-desktop-1.mga4 from Mageia 4 in my Mageia 5 beta
> installation and the problem is gone, so it seems a problem in the kernel.
> 
> Is there any way to look for changes related to the module r8169 between
> this kernel and the one used in cauldron?

Which was the last Mageia 5 kernel you tried with?

How exactly do you shutdown? Which button(s) and/or menu item or command(s) do you use?

CC: (none) => tmb
Source RPM: (none) => kernel

kernel-desktop-3.18.0-2.mga5 is the last I used but the problem happened before it, I can not remember with which kernel it began to happen.

I use KDE and to shutdown I just click on the menu and then on Shutdown

Is this still valid in Mageia 5 RC?

Keywords: (none) => NEEDINFO, UPSTREAM
Assignee: bugsquad => tmb

Yes, it is.

Just for the records, since this laptop seems to be the only one suffering from this issue, it still happens with Mageia 6 sta 1.

Does shutting down with the "poweroff" command work better?

It is the same result. I tried "poweroff" and also "shutdown -hP now".

Mass-reassigning all bugs with "kernel" in the Source RPM field that are assigned to tmb, to the kernel packagers group, because tmb is currently MIA.

Assignee: tmb => kernel