From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1LqFgs-0002no-4E for garchives@archives.gentoo.org; Sat, 04 Apr 2009 23:54:22 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 1455CE0412; Sat, 4 Apr 2009 23:54:21 +0000 (UTC) Received: from ey-out-1920.google.com (ey-out-1920.google.com [74.125.78.144]) by pigeon.gentoo.org (Postfix) with ESMTP id CA8C4E0412 for ; Sat, 4 Apr 2009 23:54:20 +0000 (UTC) Received: by ey-out-1920.google.com with SMTP id 4so277249eyg.10 for ; Sat, 04 Apr 2009 16:54:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :user-agent:references:in-reply-to:mime-version:content-type :content-transfer-encoding:message-id; bh=2NUDEKUVbsGPMRXfpPHDd7+cscWSoxEEqgFnZE+yqqM=; b=Jq4ouqa8v5nY4Y+hvqGgl0ggg/1aYAMb0TDSssTWaddKgFLdHaWnyOqdKauPq1AoXJ JU+TWDmvLuYXeiICasPX8KC7Y0vAZiHzherlsP016Mw8LKTvy6j86ZVH/F2CYMFZIbIB V8HgbzIvCYcIGvBl/LlO2Rx24QXO9C7Fiwtd0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=from:to:subject:date:user-agent:references:in-reply-to:mime-version :content-type:content-transfer-encoding:message-id; b=S0YB0iFMmzvORpVpp4xrUkir1bNUf7o20ZYJ94N2vd+vTd6lYdekM+Bvk0SOuDCug/ ocvQVKxBNCk0H/mI7tfI3IdzR+SmFjWn77uCCqcGuTIbHK+7TFxzAyXSYhu30yYvAWXp ZAG5RlC3YaN3pBkwJy2LUvg2gVJfJXdbrcp8w= Received: by 10.210.39.8 with SMTP id m8mr1704782ebm.59.1238889260285; Sat, 04 Apr 2009 16:54:20 -0700 (PDT) Received: from energy.localnet (energy.heim10.tu-clausthal.de [139.174.197.94]) by mx.google.com with ESMTPS id 20sm3686774ewy.41.2009.04.04.16.54.19 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 04 Apr 2009 16:54:19 -0700 (PDT) From: Volker Armin Hemmann To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Another Jacked up mess on update - hal daemon Date: Sun, 5 Apr 2009 01:54:18 +0200 User-Agent: KMail/1.11.90 (Linux/2.6.28.5r4; KDE/4.2.68; x86_64; ; ) References: <877i20nfzz.fsf@newsguy.com> In-Reply-To: <877i20nfzz.fsf@newsguy.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200904050154.18568.volkerarmin@googlemail.com> X-Archives-Salt: 7c1fdf72-d33a-4cc9-bd6e-3ce12cc677e4 X-Archives-Hash: 2c9ce3313744d970d1ccdbdecf4f0bc5 On Sunday 05 April 2009, Harry Putnam wrote: > Once again I find myself with a big mess following an update world. > This time I was probably out of date by more than 1 mnth, probably > less than 2. > > On first reboot the bootup proceeds well into level 3, right up to > starting hal daemon. > > There is sets.... forever. > > Since its past the point where sshd is started I can ssh into the > machine. > > I thought to maybe stop hald then attempt a restart. It appears > halting hald did allow the boot to continue, but it will not start. > > Consequently I have no mouse or keyboard at the login prompt. > > But I can ssh into the box. > > What should I supply here to allow someone to help diagnose the > problem? > > Recent info on hal from `qlop --list|grep hal' > > Sun Feb 15 10:52:16 2009 >>> app-misc/hal-info-20090202 > Sun Feb 15 10:54:45 2009 >>> sys-apps/hal-0.5.11-r8 > Fri Apr 3 09:23:58 2009 >>> sys-apps/hal-0.5.12_rc1 > Fri Apr 3 09:24:12 2009 >>> app-misc/hal-info-20090330 > > Running 2.6.28-r1 kernel for currently. > > I wasn't sure what to look for in in dmesg but saw nothing that > appeared related. > > There was trouble during the update with glibc. > > When I added --skip-first --keep-going to the command line: > > emerge -vuD --skip-first --keep-going world > > Then the update completed. > > I actually didn't really intend to reboot when I did, I was working on > a different machine and forgot I'd just completed an update so > shutdown by ssh from a remote when I quit for the day. I do know the > update had finished since I did look in on it from time to time. > > On next boot, the problem with hal daemon reported above started. and you did etc-update/cfg-update after the update? Have you read the messages with elogv? Same hal versions here - no problems at all.