<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Yun Fu&#039;s Worklog &#187; system</title>
	<atom:link href="http://www.fuyun.org/category/system/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.fuyun.org</link>
	<description>a system engineer&#039;s blog</description>
	<lastBuildDate>Fri, 09 Apr 2010 17:41:55 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Weird Boot Error: virbr0 starting userspace STP failed</title>
		<link>http://www.fuyun.org/2010/02/weird-boot-error-virbr0-starting-userspace-stp-failed/</link>
		<comments>http://www.fuyun.org/2010/02/weird-boot-error-virbr0-starting-userspace-stp-failed/#comments</comments>
		<pubDate>Tue, 02 Feb 2010 06:58:07 +0000</pubDate>
		<dc:creator>Yun Fu</dc:creator>
				<category><![CDATA[system]]></category>

		<guid isPermaLink="false">http://www.fuyun.org/?p=258</guid>
		<description><![CDATA[I suddenly could not boot my Linux box (Fedora 11) today. It showed some error messages as follows,

virbr0: starting userspace STP failed, starting kernel STP
ADDRCONF(NETDEV_UP): eth0: link is not ready
e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None
0000:00:19.0: eth0: 10/100 speed: disabling TSO
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

In the beginning, I thought [...]]]></description>
			<content:encoded><![CDATA[<p>I suddenly could not boot my Linux box (Fedora 11) today. It showed some error messages as follows,</p>
<pre class="brush: plain;">
virbr0: starting userspace STP failed, starting kernel STP
ADDRCONF(NETDEV_UP): eth0: link is not ready
e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None
0000:00:19.0: eth0: 10/100 speed: disabling TSO
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
</pre>
<p>In the beginning, I thought it is related to network or libvirtd. But I did not solve the problem by turning off libvirtd. I did not change anything in my last boot. But I updated Fedora packages using Software Update. However, I did not pay attention what I updated. By searching on web, I found some people talked about this issue after upgrading video drivers. I felt it may be the same reason.</p>
<p>My video card is Nvidia. I used nvidia linux driver (NVIDIA-Linux-x86-190.42-pkg1.run) downloaded from nvidia web site. To give it a try, I decided to reinstall it. So I boot at runlevel 3, and run the driver installer NVIDIA-Linux-x86-190.42-pkg1.run again in text mode. It rebuilt the driver and reset xorg.conf. Then, the problem was fixed.</p>
<p>After that, I found that there are actually a lot of errors in /var/log/Xorg.?.log such as</p>
<pre class="brush: plain;">
NVIDIA: Failed to load the NVIDIA kernel module. Please check
your system's kernel log for additional error messages.
</pre>
<p>Also, /var/log/messages log has error message as follows.</p>
<pre class="brush: plain;">
WARNING: GdmLocalDisplayFactory: maximum number of X display failures
reached: check X server log for errors
init:prefdm main process terminated with status 1
</pre>
<p>So this weird boot error is really caused by video driver. The errors related to virbr0 were just coincident errors that showed up after X failed to start. I checked my logs. Such errors have been there for every boot. I just did not see them. Now I turn off libvirtd service.</p>
<p>FYI, to boot into runlevel 3 in this hanging case. Select the linux image entry to boot in GRUB, press &#8216;e&#8217;.  In next screen, move to the kernel line, press &#8216;e&#8217;.  In my case, it ends up with &#8216;rhgb quiet&#8217;, which is redhat graphic boot. Delete &#8216;rhgb, quite&#8217;, replace it with &#8216;3&#8242;. Then press &#8216;b&#8217;. It will boot to runlevel 3 without starting those daemons or X window. Just log in as root and reinstall the video driver. If runlevel 3 does not work, try single user mode, i.e. replace &#8216;rhgb quite&#8217; with &#8217;single&#8217;.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.fuyun.org/2010/02/weird-boot-error-virbr0-starting-userspace-stp-failed/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
