[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080408112149.GA4326@localhost.ift.unesp.br>
Date: Tue, 8 Apr 2008 08:21:50 -0300
From: "Carlos R. Mafra" <crmafra2@...il.com>
To: Srivatsa Vaddagiri <vatsa@...ux.vnet.ibm.com>
Cc: Ken Moffat <zarniwhoop@...world.com>, Ingo Molnar <mingo@...e.hu>,
"Rafael J. Wysocki" <rjw@...k.pl>,
lkml <linux-kernel@...r.kernel.org>, a.p.zijlstra@...llo.nl,
aneesh.kumar@...ux.vnet.ibm.com, dhaval@...ux.vnet.ibm.com,
Balbir Singh <balbir@...ibm.com>, skumar@...ux.vnet.ibm.com
Subject: Re: Regression in gdm-2.18 since 2.6.24
On Tue 8.Apr'08 at 14:20:27 +0530, Srivatsa Vaddagiri wrote:
> On Mon, Apr 07, 2008 at 12:48:33AM +0100, Ken Moffat wrote:
> > Well, I found your analysis convincing. Unfortunately, my hardware
> > disagreed. Testing -rc8 with CONFIG_GROUP_SCHED disabled (a test is
> > a mixture of 5 attempts to restart and 5 to shutdown):
> >
> > 1. the base version success is 4/10
> >
> > 2. increasing the granularity by a factor of 10 as you requested,
> > success is 8/10
>
> This makes me think that we are just exposing a timing related problem
> in gdm here.
I can see the same issue in my desktop with kdm, but I've never had
the energy to bisect or look further into it, so I just type halt or
reboot in xterm :-(
But the fact is that a few days ago I tried rebooting through kdm button,
but it left me with a console login screen (and no reboot).
It also happened a few times before too (and I am always using a
uptodated 2.6.25-rcX kernel).
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists