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 1Re5it-0000Tu-A6 for garchives@archives.gentoo.org; Fri, 23 Dec 2011 14:03:47 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 95B8421C056; Fri, 23 Dec 2011 14:03:33 +0000 (UTC) Received: from mail-gy0-f181.google.com (mail-gy0-f181.google.com [209.85.160.181]) by pigeon.gentoo.org (Postfix) with ESMTP id CBB1F21C124 for ; Fri, 23 Dec 2011 14:02:34 +0000 (UTC) Received: by ghrr19 with SMTP id r19so2947680ghr.40 for ; Fri, 23 Dec 2011 06:02:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=Jy8+Hh7EffstWlA/AJ5QG8f1dfo50gXz7ej3VzhuWnQ=; b=w4IUPfF1QwXIJhLe62KDIaXIbycGc0HF49GoBMxJqQS0Cw93cEogRHOxBaYSrTcgTB DcIsuszeZGKDU9/1E6PYI/5qrv6ydbKxkcD8b5DRV0TdsMCp3MilmyZyTj/znLCUvhvA q1ItWy/2pZaIJVe8CCDoi0Y7t1djlMfEwXW1Y= Received: by 10.236.115.40 with SMTP id d28mr20909901yhh.37.1324648954353; Fri, 23 Dec 2011 06:02:34 -0800 (PST) Received: from [192.168.2.5] (adsl-65-0-122-130.jan.bellsouth.net. [65.0.122.130]) by mx.google.com with ESMTPS id c10sm20473787yhj.2.2011.12.23.06.02.32 (version=SSLv3 cipher=OTHER); Fri, 23 Dec 2011 06:02:33 -0800 (PST) Message-ID: <4EF489F7.5030503@gmail.com> Date: Fri, 23 Dec 2011 08:02:31 -0600 From: Dale User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20111022 Firefox/7.0.1 SeaMonkey/2.4.1 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 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] GDM kbd/mouse lockup after emerge --update on a stable amd64 platform - need hints to cure References: <4EF2E40E.3030403@gmail.com> <20111222135813.42263034@weird.wonkology.org> <4EF415B1.4080100@gmail.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: 1aa44bd6-81ee-465e-ab1e-fac3a147f2de X-Archives-Hash: ccfb236d957e252ff65c5c02c818d3f7 Michael Mol wrote: > I still don't know the SysReq magic. I've just ssh'd in. If I can't do > that, it usually means something hardlocked. This is from a post Neil made many ages ago. Notice the random sig too. "Hold down Atl, hold down SysRq, press each of the keys in turn. The usual full sequence is R-E-I-S-U-B Reboot Even If System Utterly Broken By ${DEITY} - this tagline picker is spooky at times :-O -- Neil Bothwick System halted - Press all keys at once to continue." Me again, don't forget to include the options in the kernel config too. Should look like this: root@fireball / # zcat /proc/config.gz | grep -i sysrq CONFIG_MAGIC_SYSRQ=y root@fireball / # When it locks up to the point that those keys don't work, grip the plug firmly and pull. I usually get to about the E and sometimes the I before I find myself at a console. Another thing, it is best if you use that to go all the way down to single user mode, make sure no processes are running that shouldn't with top or something then go back to regular default mode. I say that because sometimes there is plenty of cruft left hanging around. It stops services but the services still have run and lock files and it leads to errors. You could also just reboot too. >> There are quite a few of these commands that gets posted from time to time. >> As a hint, I have a text file in my /root directory that contains the >> commands and a description. I just cat and grep the file when I need to. I >> wouldn't recommend a user directory tho. If for someone reason only root is >> mounted, then you can get to /root but not /home if it is a separate >> partition. You, and other Gentooers, may want to think about doing >> something like this. >> >> Hope this helps in some small way. > Funny thing is, I thought I'd taken care of it. It didn't crop up for > me until xscreensaver kicked in, which crashed X due to differeing ABI > versions between what was already running and what xscreensaver tried > to get linked in. Guess I should remember to restart X. :) > Yea, some updates are tricky. A good while back, I could upgrade all of KDE and not logout until it is done. Now I have to logout at least a couple times or things get buggy. I guess things are pretty tight between programs nowadays. Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words! Miss the compile output? Hint: EMERGE_DEFAULT_OPTS="--quiet-build=n"