tag 546291 moreinfo kthxbye On Sun, Sep 20, 2009 at 21:24:15 +0200, a...@users.sourceforge.net wrote:
> Hi, > > Sorry for the delay. > > On Mon, 14 Sep 2009, Josselin Mouette wrote: > > > Le dimanche 13 septembre 2009 à 09:36 +0200, a...@users.sourceforge.net > > a écrit : > >> I don't believe the problem is X's fault because it does not occur in > >> GDM's graphical > >> login screen even if I leave the computer in this state for days; neither > >> can it be the > >> kernel's fault because it does not happen in console mode (i.e. without > >> GDM and X). It > >> only occurs in a graphical user session. > > I have narrowed it down: it only occurs in _my_ GDM session. If I create a > new user and > login as this user, the problem does not occur. > > > Actually it could be your CPU or RAM. Please run a full memtest86, at least. > > The memory checked out alright. It would seem like a hradware problem, though > --- if it > were not limited to my sessions. It has nothing to do with load, either --- > the memory > test put the CPUs under quite some stress, and temperatures soared --- > without causing any > problems. Then I did some video encoding with a lot of load as well as memory > and harddisk > usage --- again without any problems. > > > In all cases a hardware lockup cannot be caused solely by userland. > > I do realise that. That is why I believe it must be some program with suid > rights --- like > GDM. > Even for programs running as root, a power down without proper shutdown should never happen. Do you still have this problem today? If so maybe dmesg or syslog has a clue? Cheers, Julien
signature.asc
Description: Digital signature
