Bug 728315

Summary:	udev error binding udev control socket
Product:	[openSUSE] openSUSE 11.4	Reporter:	Don Hughes <support>
Component:	Kernel	Assignee:	Robert Milasan <rmilasan>
Status:	VERIFIED INVALID	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P5 - None
Version:	Factory
Target Milestone:	---
Hardware:	x86-64
OS:	openSUSE 11.4
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Don Hughes 2011-11-04 13:42:51 UTC

User-Agent:       Mozilla/5.0 (Windows NT 5.1; rv:7.0.1) Gecko/20100101 Firefox/7.0.1

After upgrading to udev 173-12.1 my system fails to boot.  The log has an error udev[553] error binding udev control socket.  if I

init 2
boot.udev stop
boot.udev start
init 3

the system will start sufficiently to connect to the network and make changes. 

Reverting to an earlier version of udev corrected the problem

Reproducible: Always

Steps to Reproduce:
1.boot system
2.
3.
Actual Results:  
System displays errors and fails to boot correctly

Expected Results:  
System boots without errors

Comment 1 Jeff Mahoney 2012-03-26 03:08:45 UTC

This isn't a kernel issue. Redirecting to udev maintainer.

Comment 2 Robert Milasan 2012-03-26 07:14:17 UTC

Can you enable debug in udev and attach it in the bug?
Thank you.

Comment 3 Don Hughes 2012-04-02 14:47:26 UTC

This test system is no longer available.  I can no longer reproduce the problem.

Comment 4 Robert Milasan 2012-04-02 14:56:00 UTC

Hi, tried to reproduce it also, but used the stable version from openSUSE 11.4 which is udev 168 not udev 173.

BTW: how did you get version 173? If it's not from the stable repo openSUSE 11.4, this is not a valid bug then.

Comment 5 Don Hughes 2012-04-02 15:55:55 UTC

From the 12.1 repo.  I was running a test to see if there would be any problems upgrading from 11.4 to 12.1

I added 12.1 to the available repos and then did an 'update all selected if new version available' in yast2.  I then reviewed the list of updates for items likely to impact my production systems and tried them a few at a time.  This is a process that I have followed in the past, and I seldom have any surprises when I finally do an official update of my systems from one version to another.

As an aside, I have had major issues with 12.1 - especially the new Gnome - and will be sticking with 11.4.

Comment 6 Robert Milasan 2012-04-03 07:31:25 UTC

Well, this is not a bug, there is some difference between udev 168 and udev 173, so the bug at the moment is not applicable.

I will close it as INVALID, but if you see this again, please open a new bug and add the necessary info, like debug info and so on.

Thank you.