Bug 253656

Summary: setting up a bridge causes gnome to hang
Product: [Fedora] Fedora Reporter: Bryan Kearney <bkearney>
Component: bridge-utilsAssignee: David Woodhouse <dwmw2>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 7CC: triage
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-06-17 02:12:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
output of sysreport none

Description Bryan Kearney 2007-08-21 00:35:45 UTC
I am running a current (as of 20-August-2007) fedora machine. it is an ibm
thinkpad T60p. I have been attempting to set up a bridge interface in order to
support kvm work. When I have the following files in my
/etc/swysconfig/network-scripts directory I do not get a graphical login. The
machine hangs up before then. I have to reboot the machine to run level 3 in
order to fix the problem.

ifcfg-eth0
----------
# Intel Corporation 82573L Gigabit Ethernet Controller
DEVICE=eth0
#BOOTPROTO=dhcp
HWADDR=00:16:41:12:5D:FF
IPV6_AUTOCONF=yes
ONBOOT=yes
TYPE=Ethernet
USERCTL=yes
IPV6INIT=yes
PEERDNS=yes
BRIDGE=br0

ifcfg-br0
---------
TYPE=Bridge
DEVICE=br0
BOOTPROTO=dhcp
ONBOOT=yes
#DELAY=0
#GCINT=0

Comment 1 David Woodhouse 2007-08-21 06:58:43 UTC
Define 'hangs up'. With SysRq-P and SysRq-T traces. Other than X, what else is
different in runlevel 3 on your system?

Comment 2 Bryan Kearney 2007-08-21 12:55:43 UTC
Hangs up in that I see it get through all the the boot messages, it attempts to
switch to the login screen, and then I get a blank screen. No ability to enter
keyboard commands (e.g. I can not switch run levels, caps lock, nothing). The
following services are different between 3 and 5


NetworkManager is on
atieventsd is on
gpm is off
readahead_later is on

I have the following xintd services:
xinetd based services:
        chargen-dgram:  off
        chargen-stream: off
        cvs:            off
        daytime-dgram:  off
        daytime-stream: off
        discard-dgram:  off
        discard-stream: off
        echo-dgram:     off
        echo-stream:    off
        rsync:          off
        tcpmux-server:  off
        tftp:           off
        time-dgram:     off
        time-stream:    off


I will update the results of sysreport.



Comment 3 Bryan Kearney 2007-08-21 12:57:14 UTC
Created attachment 161966 [details]
output of sysreport

Comment 4 Bug Zapper 2008-05-14 14:03:46 UTC
This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '7'.

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 Fedora version prior to Fedora 7'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 Fedora 7 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 Fedora please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you.

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 Fedora release includes newer upstream software that fixes bugs or makes them obsolete. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists.

Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs:
http://docs.fedoraproject.org/release-notes/

The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Bug Zapper 2008-06-17 02:12:15 UTC
Fedora 7 changed to end-of-life (EOL) status on June 13, 2008. 
Fedora 7 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 Fedora please feel free to reopen this bug against that version.

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