Re: 2.6 kernel causing X to hang?

From: Bob Billson (reb_at_bhive.dhs.org)
Date: 04/16/04

  • Next message: Olle Eriksson: "Re: Audio HOWTO?" 
    Date: Fri, 16 Apr 2004 08:25:36 -0400
To: debian-user@lists.debian.org

    > > a couple days ago, i upgraded from the 2.4.6 kernel to the 2.6.4
    > > kernel.  figured out a couple problems, and all seemed smooth.
    > >
    > > however, twice today -- both initially while using a java IDE -- X has
    > > frozen, leaving whatever was last on the screen displayed up there and
    > > not showing the results of me doing anything to it.

    I can echo similar problems since switching to 2.6.4 and now 2.6.5. This
    is on a Debian box running the testing tree. I more often experience the
    lock-up when GDM is running and no users logged it. Sometimes when I try
    to log in via X the machine will lock up tight as soon as I hit ENTER after
    entering my password. GDM never exits and I can't get to any virtual
    console. Sometimes the magic SysRq works to reboot, sometimes not. And
    sometimes the machine is locked up and I can't type my user name.
    It seems to be totally random when it happens.

    And to make it more interesting, sometimes (though less often) X will lock
    up while I'm using it.

    I'm not sure if this is a kernel or X problem. It never happens if I
    switch back to 2.4.25.

                bob 

    -- 
  bob billson        email: reb@bhive.dhs.org          ham: kc2wz   /)
                            reb@elbnet.com             beekeeper -8|||}
  "Níl aon tinteán mar do thinteán féin." --Dorothy    Linux geek   \)
-- 
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
  • Next message: Olle Eriksson: "Re: Audio HOWTO?"

    Relevant Pages

    • Re: Now working... gdm??? Re: Couldnt load XKB keymap... Cant switch to terminal mode
      ... Or is K.W. actually claiming that he must have gdm in order to be able ... I can run fluxbox w/o gdm and no switching allowed. ... duplicating the stanza that specifies the nv/nvidia driver and replacing ... Is the kbd package a replacement for console-tools? ...
      (Debian-User)
    • Re: Now working... gdm??? Re: Couldnt load XKB keymap... Cant switch to terminal mode
      ... Or is K.W. actually claiming that he must have gdm in order to be able ... I can run fluxbox w/o gdm and no switching allowed. ... duplicating the stanza that specifies the nv/nvidia driver and replacing ... your full-featured nvidia driverby the vesa generic .. ...
      (Debian-User)
    • Re: New cpu_switch() and cpu_throw().
      ... I checked in the new version of cpu_switchfor amd64 today after ... it's switched out and acquire a lock when it's switched in. ... switching into a thread that is set to the blocked_lock another cpu is ... As we discussed, we can just use sfence rather than atomics on amd64, however, x86 will need atomics since you can't rely on the presence of *fence. ...
      (freebsd-arch)
    • Re: Ranging and Pioneer
      ... Don't think about switching the transmitter on and off. ... command the spacecraft to continuously downlink the contents of some ... lock on to that modulating waveform. ...
      (sci.astro.research)
    • New cpu_switch() and cpu_throw().
      ... For every architecture we need to support a new features in cpu_switchand cpu_throwbefore they can support per-cpu schedlock. ... I'm soliciting help or advice in implementing these on platforms other than x86, and amd64, especially on ia64 where things are implemented in C! ... we have to release a thread's lock when it's switched out and acquire a lock when it's switched in. ... If we're switching into a thread that is set to the blocked_lock another cpu is about to set it to our current cpu's lock via the mtx argument mentioned above. ...
      (freebsd-arch)