Bug 7488 - systemctrl restart network.service sometimes fails until rtl8192ce module is removed and reloaded
Summary: systemctrl restart network.service sometimes fails until rtl8192ce module is ...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2012-09-16 08:59 CEST by Jeff Robins
Modified: 2013-11-23 16:14 CET (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Jeff Robins 2012-09-16 08:59:02 CEST
"systemctrl restart network.service" sometimes fails until the rtl8192ce module is removed and then reloaded manually.  After that the first call works and subsequent calls don't work either.


I was having problems with my network not being restored after a hibernation.  I tried using Network Center to start the connection, but that didn't work.  I ran "systemctrl restart network.service" and it reported that it failed.  I ran "systemctrl status network.service" and I get a bunch of lines that say "RTNETLINK answers: File exists".

I removed the rtl8192ce module, reloaded it and then ran "systemctrl restart network.service" and everything worked.  I was able to run "systemctrl restart network.service" again and repeat the problem.  Only removing and reloading the module would allow the wireless to work.

Of course, now that I've started writing this bug report, the problem seems to have gone away. The only other thing I did was ssh into a remote system.  I did double check that I was running the command on the correct system.

--Jeff
Comment 1 Samuel Verschelde 2013-09-06 18:37:23 CEST
Hi, is this problem still happening?

CC: (none) => stormi

Samuel Verschelde 2013-09-06 18:37:28 CEST

Keywords: (none) => NEEDINFO

Comment 2 Manuel Hiebel 2013-10-22 12:11:16 CEST
This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad
Comment 3 Manuel Hiebel 2013-11-23 16:14:36 CET
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no
longer maintained, which means that it will not receive any further security or
bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.