Quaker Fang wrote:
>> My main concern was and is on the freeze. Also this time, as the beep
>> started, I could still write and post the message. But no more 'ps'. I could
>> close the terminals, but could not open any other; but still navigate with
>> the mouse to other applications, and even open a gedit ('Text Editor').
>> Around 10 minutes later name resolution stopped, though I could still
>> mouse-click to other windows. Finally a few more minutes into the scenario,
>> mouse clicks also would not work, the keyboard would be dead. Another hard
>> reset was on the order.
>>
>> There *is* a serious problem with a driver that reproducibly brings down a
>> system. plug-unplug/plumb-unplumb or not.
>>
> Wrong, these "freezing" has nothing related with driver, you can try
> without rum driver, only "rge0", you will encounter same problem.
> This phenomenon is a well known issue, you can go to
> "networking-discuss at opensolaris.org" for more information, there are
> more experts.
Could you elaborate the "well known" issue? For example,
unplumbing an interface should not freeze the system.
In fact, if unplumb does not return for a reasonable
time frame, it is a bug somewhere.
It is different from the name resolution issue. For
example, "ifconfig rum1 drop" means setting the IP address
of rum1 interface to "drop." So ifconfig will try to
resolve the name "drop." But if the hosts entry in
/etc/nsswitch.conf is dns, it may cause a problem since
the system will try to resolve the name from a DNS server,
which is not reachable since the network is not up. So
the ifconfig command seems to hang, but it is actually
waiting for the DNS server's reply which it will never
get.
--
K. Poon.
kacheong.poon at sun.com
