« December 2009
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
  
       
Today
XML

Neat blogs

Navigation

Editing

Powered by Roller Weblogger.

statcounter.com

clustrmaps.com

Locations of visitors to this page

technorati.com

20070406 Friday April 06, 2007
Getting a locked up Gnome session

So I installed snv_61 on my home desktop. The first thing that went was my rge0 stopped working. My nge0 and nge1 are still not working, so I slapped an iprb0 in place of the rge0. And right after that, I started getting a blank screen (bottom menu bar but no screen icons) on Gnome. The only clue I have is: "The application gnome-volume-manager has crashed."

Except I get that all the time. Okay, what do I see in dmesg:

Apr  5 23:26:33 kanigix svc.startd[7]: [ID 652011 daemon.warning] svc:/system/hal:default: Method "/lib/svc/method/svc-hal start" failed with exit status 95.
Apr  5 23:26:33 kanigix svc.startd[7]: [ID 748625 daemon.error] system/hal:default failed fatally: transitioned to maintenance (see 'svcs -xv' for details)

It turns out that the 95 just means a fatal error. Since svc-hal is script, lets see what is causing it to whine:

[tdh@kanigix ~]> svcs -xv
svc:/system/hal:default (Hardware Abstraction Layer daemon)
 State: maintenance since Thu Apr 05 23:26:33 2007
Reason: Start method exited with $SMF_EXIT_ERR_FATAL.
   See: http://sun.com/msg/SMF-8000-KS
   See: man -M /usr/man -s 1M hal
   See: /var/svc/log/system-hal:default.log
Impact: 1 dependent service is not running:
        svc:/system/filesystem/rmvolmgr:default
[tdh@kanigix ~]> tail /var/svc/log/system-hal:default.log
[ Apr  5 23:22:20 Executing start method ("/lib/svc/method/svc-hal start") ]
hal failed to start: error 2
[ Apr  5 23:26:33 Method "start" exited with status 95 ]
[tdh@kanigix ~]> file /usr/lib/hal/hald
/usr/lib/hal/hald:      ELF 32-bit LSB executable 80386 Version 1 [FPU], dynamically linked, not stripped, no debugging information available

Okay, we need to find out why hald is returning 2, which should be ENOENT. It looks like parent_wait_for_child() is the code killing me. Why? Hmm, either 250s has expired or something else is going on. I'm getting an answer pretty quick, so that isn't it.

One of my SATA drives is not showing up when I boot - the bios is no longer detecting it. Could I have lost a drive? WinXP shows 6 disks - my boot, 4 internal SATA, and the external SATA. It is reporting the external SATA drive as USB. It was being reported as an internal drive earlier.

I pulled the drive - I had been using it for a dump device. And now I have a working system. Still get the warning message about the gnome-volume-manager!


Originally posted on Kool Aid Served Daily
Copyright (C) 2007, Kool Aid Served Daily

Trackback URL: http://blogs.sun.com/tdh/entry/getting_a_locked_up_gnome
Comments:

Post a Comment:

Name:
E-Mail:
URL:

Your Comment:

HTML Syntax: NOT allowed