Gentoo Archives: gentoo-user

From: Fernando Rodriguez <frodriguez.developer@×××××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Re: problem which makes gnome unusable
Date: Sat, 07 Nov 2015 21:48:09
Message-Id: BLU437-SMTP24607E401706532A1711AA8D170@phx.gbl
In Reply to: [gentoo-user] Re: problem which makes gnome unusable by walt
1 On Friday, November 06, 2015 1:46:08 PM walt wrote:
2 > On Fri, 06 Nov 2015 14:45:43 -0500
3 > covici@××××××××××.com wrote:
4 >
5 > > Hi. I am having a very bad problem which makes gnome unusable --
6 > > once I get into the virtual console where the xserver is displaying
7 > > gnome, console 12 in my case, I can never get out of that console --
8 > > control-alt-f1 or anything does not work. If I try to ssh in from
9 > > somewhere else, I cannot stop gdm because the x server will not stop
10 > > -- even kill -9 will not stop it and I have to reboot the system.
11 >
12 > The part about kill -9 failing is exactly the problem I had with the
13 > 3.18.x kernel series a while ago. I know this problem must be hardware
14 > specific because some distros are still shipping 3.18 kernels as the
15 > default, and I'll bet others in this mailing list are using it without
16 > problems too. I had some scary problems with that kernel version
17 > that were very difficult to diagnose until I just rebooted with an
18 > older kernel and the scary problems vanished. The 4.2 series seems
19 > okay so far on my VMs. (Even my gentoo VMs had some minor problems with
20 > 3.18.x)
21
22 I've been using 3.18.x for a while now and I only had a very similar problem
23 when I updated to 3.18.23 about a week or so ago. Everytime I ran sudo the
24 desktop would become unresponsive and if I tried to switch to another VT it
25 would freeze completely. I didn't tried to ssh in, but the SysRq keys worked
26 for rebooting. I could reproduce it everytime with 3.18.23 so I went back to
27 3.18.22. There where two updates to the sudo package since then and yesterday
28 I tried booting 3.18.23 and it worked fine so it was the sudo-1.8.12 and kernel
29 3.18.23 combo that caused it. Now I'm using 3.18.24 without problems. I use
30 kde and ati-drivers.
31
32 --
33 Fernando Rodriguez