By any chance, do you have an NVidia TNT2 adapter? Even if not, the fact that it is triggered by X events makes me think this might be related to bug #275911 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=275911
If this is the case, currently only solution is to downgrade all X packages to 4.3.0.dfsg.1-7. It's available from snapshot.debian.org (2004/09/07 snapshot) Can you ssh from another machine when your machine is stuck? If yes - try to see if there's any process clogging your CPU, and strace -p it. ----- Original Message ----- From: "Omer Zak" <[EMAIL PROTECTED]> To: "Linux-IL mailing list" <[EMAIL PROTECTED]> Sent: Thursday, December 02, 2004 2:18 AM Subject: Frequent lock-ups of Debian Testing Linux when connected to theInternet > Recently I have been experiencing very frequent lock-ups of my PC. I > had to press the RESET button to release the lockup. When the lockup > occurs, neither the keyboard nor the mouse respond. > > My software configuration: > Kernel: 2.6.8-1-686 > pptp-linux 1.5.0-4 > pptpd 1.2.1-2 > xfree86 4.3.0.dfsg.1-8 > Mozilla 1.7.3-5 > evolution 1.4.6-5 > epiphany 1.2.9-2 > iptables 1.2.11-8 > > The lockup usually occurs when I click on the window of an application > (usually both Mozilla, evolution and epiphany are open as well as GNOME > Terminal 2.6.1, on Gnome desktop). > > When the lockup occurs, the PC (which has two network cards) also ceases > to route packets between the ADSL modem and the intranet. So the > problem does not affect only the X-Window server. > > I found nothing useful in /var/log files. I tried top -b > ~/tmp/xxx & > and there were no hints in the resulting xxx file (which was only 9.3MB > long when the last lockup happened). > > df and df -i both exhibit plenty of free space and inodes. > Swap space is not used at all (the PC has 512MB memory, of which 410MB > are in use at this moment). > > The recent rise in frequency of lockups hints at some persistent > resource depletion, but I do not see any obvious depletion of persistent > resources. > > Any clues? > Is it a known problem of kernel 2.6.8 (after having been patched by > Debian)? > What can I do to trap the failure which causes the kernel to lockup? > Thanks, > --- Omer > -- > My own blog is at http://www.livejournal.com/users/tddpirate/ > > My opinions, as expressed in this E-mail message, are mine alone. > They do not represent the official policy of any organization with which > I may be affiliated in any way. > WARNING TO SPAMMERS: at http://www.zak.co.il/spamwarning.html > > > ================================================================= > To unsubscribe, send mail to [EMAIL PROTECTED] with > the word "unsubscribe" in the message body, e.g., run the command > echo unsubscribe | mail [EMAIL PROTECTED] > > ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
