SCIENTIFIC-LINUX-USERS Archives

May 2014

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Ian Williams <[log in to unmask]>
Reply To:
Ian Williams <[log in to unmask]>
Date:
Tue, 20 May 2014 07:00:49 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (47 lines)
Hi Todd,

The freeze took place at random.

The network-manager app caused inconsistencies in NIC naming, which appeared
to propagate to the udev persistent net rules.

Best wishes,

Ian

On Mon, 19 May 2014 11:34:20 -0700, ToddAndMargo <[log in to unmask]> wrote:

>On 05/18/2014 05:21 AM, Ian Williams wrote:
>> Hi Todd,
>>
>> I think I may have had the same problem on a 64bit system.
>>
>> The computer seems to freeze at boot, while the "starting udev" message is
>> displayed.
>>
>> The problem was not related to hardware in the machine, it was related to an
>> incorrectly configured NIC. I edited the configuration file
>> /etc/sysconfig/network-scripts/ifcfg-eth0. In my case it was due to an
>> incorrect hardware address and the BOOTP directive.
>>
>> I hope this information can help you further diagnose the problem.
>>
>> Best wishes,
>>
>> Ian
>
>Hi Ian,
>
>What the freeze reproducible every boot, or was
>it random?
>
>Many thanks,
>-T
>
>--
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>Computers are like air conditioners.
>They malfunction when you open windows
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>=========================================================================

ATOM RSS1 RSS2