Bug 796849

Summary: "/etc/init.d/network start" will result an instant system freeze.
Product: [Fedora] Fedora Reporter: Ivo Sarak <ivo>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: rawhideCC: gansalmon, itamar, johannbg, jonathan, kernel-maint, madhu.chinakonda, metherid, mschmidt, notting, plautrba, systemd-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-05-20 12:18:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
lspci on that system
none
dmesg on that computer none

Description Ivo Sarak 2012-02-23 18:38:17 UTC
Description of problem:

Because of the bug https://bugzilla.redhat.com/show_bug.cgi?id=796837 I edited out NetworkManager as a manager of my LAN adapters. But as soon as I issue "/etc/init.d/network start" the system will report as calling systemctl and that is it. System will experience instant system freeze. Power reset of the motherboard will not start up the computer (fans are running, but display will remain blank and even the EFI BIOS will not go up). Even the short time powering off the system will not remedy it. 

Version-Release number of selected component (if applicable):

systemd-43-1.fc17.x86_64
systemd-43-1.fc17.i686
kernel 3.3.0-0.rc3.git2.2.fc18.x86_64 
systemd-sysv-43-1.fc17.x86_64

How reproducible:

Always.

Steps to Reproduce:
1. Remove the NetworkManager as a manager of network devices;
2. Issue a "/etc/init.d/network start".
  
Actual results:

Instant system freeze.

Expected results:

No freeze and bringing up of the network devices.

Additional info:

Base Board Information
        Manufacturer: ASRock
        Product Name: A75M-HVS
BIOS Information
        Vendor: American Megatrends Inc.
        Version: P1.60
        Release Date: 10/28/2011
CPU: AMD A6-3500 APU with Radeon(tm) HD Graphics

01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI
Express Gigabit Ethernet controller (rev 06)
02:05.0 Ethernet controller: Intel Corporation 82541PI Gigabit Ethernet
Controller (rev 05)

Also, if to issue "ifconfig" and "route add" commands manually then those network settings are being accepted, interfaces will get running and there is no network issues to report about.

Comment 1 Michal Schmidt 2012-02-23 19:41:09 UTC
It can be a hardware problem or a kernel bug.
Please attach the output of 'dmesg' and 'lspci -vvnn'.

Comment 2 Ivo Sarak 2012-02-23 23:53:25 UTC
Created attachment 565417 [details]
lspci on that system

Comment 3 Ivo Sarak 2012-02-23 23:54:49 UTC
Created attachment 565418 [details]
dmesg on that computer

Comment 4 Josh Boyer 2012-04-30 21:04:04 UTC
Are you still seeing this bug with the 3.3 final release, or a 3.4-rc4 kernel?

Comment 5 Ivo Sarak 2012-05-20 04:19:40 UTC
It seems to be fine. Only thing network related I see is a constant complaining about IPv6 RA default route as being unable to be added, but somehow IPv6 routes are fine and working.

Comment 6 Josh Boyer 2012-05-20 12:18:44 UTC
Thanks for letting us know.