desktop random freezes in feisty

Bug #131973 reported by vista killer
14
Affects Status Importance Assigned to Milestone
Ubuntu
Fix Released
Undecided
Justin M. Wray

Bug Description

I have random freezes in my dekstop.The strange thing is that the mouse is still working and amarok is still playing music!!
I use and beryl in my system.

Revision history for this message
vista killer (vistakiller) wrote :

i forget to write this.My system is a cpu itnel 6600,Asus P5N32-E sli with 680i chipset,nvidia 8800gts with the latest nvidia official driver

Revision history for this message
vista killer (vistakiller) wrote :
Download full text (3.1 KiB)

here is my /var/log/messages the time when it happens
Aug 12 12:57:01 spiros kernel: [ 9331.230169] Inbound IN=ppp0 OUT= MAC= SRC=68.102.194.30 DST=77.49.29.27 LEN=91 TOS=0x00 PREC=0x00 TTL=122 ID=52167 PROTO=UDP SPT=35612 DPT=44730 LEN=71
Aug 12 12:57:04 spiros kernel: [ 9334.248436] Inbound IN=ppp0 OUT= MAC= SRC=203.161.96.117 DST=77.49.29.27 LEN=91 TOS=0x00 PREC=0x00 TTL=119 ID=42810 PROTO=UDP SPT=8000 DPT=44730 LEN=71
Aug 12 12:57:05 spiros kernel: [ 9335.010251] Inbound IN=ppp0 OUT= MAC= SRC=85.83.18.168 DST=77.49.29.27 LEN=93 TOS=0x00 PREC=0x00 TTL=114 ID=29134 PROTO=UDP SPT=20982 DPT=44730 LEN=73
Aug 12 12:57:06 spiros kernel: [ 9336.509853] Inbound IN=ppp0 OUT= MAC= SRC=81.56.43.144 DST=77.49.29.27 LEN=91 TOS=0x00 PREC=0x00 TTL=48 ID=44938 PROTO=UDP SPT=41118 DPT=44730 LEN=71
Aug 12 12:57:08 spiros kernel: [ 9337.998487] Inbound IN=ppp0 OUT= MAC= SRC=209.62.223.84 DST=77.49.29.27 LEN=91 TOS=0x00 PREC=0x00 TTL=118 ID=3604 PROTO=UDP SPT=32459 DPT=44730 LEN=71
Aug 12 12:57:13 spiros kernel: [ 9343.380020] Inbound IN=ppp0 OUT= MAC= SRC=81.132.162.215 DST=77.49.29.27 LEN=91 TOS=0x00 PREC=0x00 TTL=111 ID=28654 PROTO=UDP SPT=56321 DPT=44730 LEN=71
Aug 12 12:57:16 spiros kernel: [ 9346.222546] Inbound IN=ppp0 OUT= MAC= SRC=87.203.214.231 DST=77.49.29.27 LEN=91 TOS=0x00 PREC=0x00 TTL=115 ID=39504 PROTO=UDP SPT=32855 DPT=44730 LEN=71
Aug 12 12:57:18 spiros kernel: [ 9348.472021] Inbound IN=ppp0 OUT= MAC= SRC=67.177.134.53 DST=77.49.29.27 LEN=91 TOS=0x00 PREC=0x00 TTL=119 ID=17225 PROTO=UDP SPT=32479 DPT=44730 LEN=71
Aug 12 12:57:22 spiros kernel: [ 9352.056370] Inbound IN=ppp0 OUT= MAC= SRC=82.233.178.109 DST=77.49.29.27 LEN=91 TOS=0x00 PREC=0x00 TTL=112 ID=13133 PROTO=UDP SPT=43797 DPT=44730 LEN=71
Aug 12 12:57:24 spiros kernel: [ 9353.970366] Inbound IN=ppp0 OUT= MAC= SRC=85.157.231.76 DST=77.49.29.27 LEN=93 TOS=0x00 PREC=0x00 TTL=115 ID=33145 PROTO=UDP SPT=49287 DPT=44730 LEN=73
Aug 12 12:57:24 spiros kernel: [ 9354.289838] Inbound IN=ppp0 OUT= MAC= SRC=24.24.93.72 DST=77.49.29.27 LEN=91 TOS=0x00 PREC=0x00 TTL=47 ID=46327 PROTO=UDP SPT=16892 DPT=44730 LEN=71
Aug 12 12:57:24 spiros kernel: [ 9354.415641] Inbound IN=ppp0 OUT= MAC= SRC=62.143.114.202 DST=77.49.29.27 LEN=91 TOS=0x02 PREC=0x00 TTL=115 ID=47823 PROTO=UDP SPT=64210 DPT=44730 LEN=71
Aug 12 12:57:27 spiros kernel: [ 9357.575668] Inbound IN=ppp0 OUT= MAC= SRC=219.90.242.74 DST=77.49.29.27 LEN=91 TOS=0x00 PREC=0x00 TTL=54 ID=37275 PROTO=UDP SPT=33186 DPT=44730 LEN=71
Aug 12 12:57:29 spiros kernel: [ 9358.724857] Inbound IN=ppp0 OUT= MAC= SRC=64.231.157.86 DST=77.49.29.27 LEN=91 TOS=0x00 PREC=0x00 TTL=117 ID=45215 PROTO=UDP SPT=49000 DPT=44730 LEN=71
Aug 12 12:57:30 spiros kernel: [ 9360.151958] Inbound IN=ppp0 OUT= MAC= SRC=68.102.194.30 DST=77.49.29.27 LEN=70 TOS=0x00 PREC=0x00 TTL=122 ID=55074 PROTO=UDP SPT=35612 DPT=44730 LEN=50
Aug 12 12:57:31 spiros kernel: [ 9361.437592] Inbound IN=ppp0 OUT= MAC= SRC=89.12.237.142 DST=77.49.29.27 LEN=91 TOS=0x00 PREC=0x00 TTL=118 ID=54986 PROTO=UDP SPT=4661 DPT=44730 LEN=71
Aug 12 12:57:31 spiros kernel: [ 9361.531436] Inbound IN=ppp0 OUT= MAC= SRC=86.1.7.4 DST=77.49.29.27 LEN=70 TOS=0x00 PREC=0x00 TTL=115 ID=25103 PROTO=UDP SPT=2...

Read more...

Revision history for this message
Justin M. Wray (wray-justin) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

We have instructions on debugging some types of problems: http://wiki.ubuntu.com/DebuggingProcedures

Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. Also include an strace if possible. This will greatly help us in tracking down your problem.

In addition, Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

Thanks,
Justin M. Wray

Revision history for this message
durilka (durilka) wrote :

Hi,

This looks like klogd service being bloated by thousands of iptable logs. Actually it's strange that system logging lags the system but anyway, probably the quick fix is to edit couple of files in /etc/ipmasq/rules and comment lines like
$IPTABLES -A INPUT -j LOG -i ${j%%:*} -s $IPOFIF/$NMOFIF

to look like

#$IPTABLES -A INPUT -j LOG -i ${j%%:*} -s $IPOFIF/$NMOFIF

Here are the files:
I15lospoof.def
I70masq.def
ZZZdenyandlog.def

Beware! Commenting this gives you no chance in tracking crack attacks/attempts.

And btw. I've commented them, but have no idea if this will work. We'll see.

Revision history for this message
Justin M. Wray (wray-justin) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Thanks in advance.

The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Gutsy Gibbon. It would help us greatly if you could test with it so we can work on getting it fixed in the actively developed release. You can find out more about the development release at [WWW] http://www.ubuntu.com/testing/

Thanks,
Justin M. Wray

Revision history for this message
durilka (durilka) wrote :

Hi Justin,

I've had it in the Gibbon. It happened on my home computer and it's the one I don't see really often, it's more for the family - they use it heavily. But at least I confirm that the problem exists in Gutsy Gibbon(more or less recent +-1 week) at least on x86_64. I'll try to check if this still happens after I've disabled logging of iptables activity and if they're really related.

By the way, why is it linked to beryl? It should be actually compiz, but I have it switched off since it doesn't work for me properly on my dual-monitor setup. So i don't think it's about desktop effects.

Cheers.

Changed in meta-gnome2:
status: Incomplete → In Progress
Revision history for this message
durilka (durilka) wrote :

Okay, so far i haven't seen the slowdown since disabled the logging in ipfilters.

Sascha.

Revision history for this message
Justin M. Wray (wray-justin) wrote :

Okay, go ahead and give this till mid next week, if you are still not having a problem, I'll close the ticket.

Thanks,
Justin M. Wray

Changed in meta-gnome2:
status: In Progress → Fix Committed
Revision history for this message
Riccardo Lucchese (riccardo.lucchese) wrote :

Hi

I experienced such problems for months now, both on a AMD Athlon with nv5200(running proprietary drivers) and on a laptop with a centrino and a radeon 9600M(os drivers).

It used to happen under whatever kind of load (and to shot it down: I don't run compiz).

Since beginning the problem was 100% "fixed" on the laptop passing noacpi nolapic parameters to kernel(both feisty and gusty).
On the desktop I tried many different things until know but nothing wasn't enough (it used to freeze also without any X server running :D)

After a bit of lkml reading I came to this:
http://lkml.org/lkml/2007/8/21/435
[he is experiencing both mouse-only-freezes and *total*-hard-freezes :D]

On both machines I'm running gusty now and I solved completely the problem by launching ASAP after login:
sudo /etc/init.d/powernowd stop

I've read that in many threads is asked to debug the crash :), but actually there is nothing I can do in my case: no way to get into the pc, no ssh, no ping, no nothing...

(an already opened ssh session from a remote client to the freezing machine also freezes at the same time:) )

Hope to hear soon about ideas on how to fix this and how I may help,
Thanks!
Riccardo

Revision history for this message
Riccardo Lucchese (riccardo.lucchese) wrote :

ps to previous entry:
I forgot to say that if I apt-get --purge remove powernowd the machine still freezes at reboot :)
re-installing powernowd and stopping it at every login keeps the machine running good 100%.
Very interesting, isn't it?

Revision history for this message
durilka (durilka) wrote :

Riccardo,

Looks like powernowd has two parts. Kernel module(s) and the client daemon or whatever. If apt-get removal doesn't help you - your problem is kernel modules. Oops. I have similar case with some of the kernel modules, computer hangs when playing video and the problem is one of the kernel modules. Unfortunately I don't know which and even though I have lots of them blacklisted they get automatically loaded. Like you, after booting I have to run script which does bunch of rmmod's and that helps.

Justin, I guess I can say that I have no more freezes. Only deadhangs, but that's another story ;-=--)

Cheers,
Ale.

Revision history for this message
IVIisterX (doellies) wrote :

Hi alltogether,

I have the problem with freezes at random times too.
My configuration is:
ASUS P4C800 Deluxe Mainboard BIOS-Version: 1019.002 AMI-BIOS, Intel P4 2,6 GHz, 1024 MB RAM, ATI 9700 PRO, 160 GB Hitachi SATA-HDD as bootmedium, USB Keyboard and USB Maus from Logitech.
I found out, that the freezes are associated with the following settings:

Without any changes at the "Ubuntu Feisty Fawn Alternate"-installation my machine freezes with the Kernel 2.6.20-15-generic, 2.6.20-16-generic and 2.6.20-16-386. To get more stability I have to change
1. The Bios-Setting ACPI 2.0 support from disabled to enabled.
2. Uninstall powernowd
3. Install the ATI-driver 8.39.4
With these settings and Kernel 2.6.20-15-generic my machine runs without any freezes; with the kernels 2.6.20-16-generic and 2.6.20-16-386 my machine freezes within 30 minutes max.

If I add the additional kernel parameters noapic nolapic irqpoll ht=on my machine freezes a few minutes after reboot with various programs.
If I uninstall the restricted graphics driver my machine freezes a few minutes after disabling and with all kernels above-mentioned and various programs.

While I am writing this comment I test the "sudo /etc/init.d/powernowd stop" with kernel 2.6.20-16-generic - it still works.

Best regards

IVIr.X

Revision history for this message
vista killer (vistakiller) wrote :

in the last week i notice that if i left the desktop with screensaver the system freeze very often

Revision history for this message
IVIisterX (doellies) wrote :

Hi vista killer!

Uses the screensaver OpenGL?

IVIr.X

Revision history for this message
Riccardo Lucchese (riccardo.lucchese) wrote :

Yes, you are right durilka: basically there are some kmodules that enable cpu frequency scaling and the userspace daemons. Therefore is it interesting that removing powernowd the machine still freezes.

 !!! Before a few months ago I never experienced such problems: so there must be some commit (possibly to the kernel modules [and some random ACPI code]) that broke my configuration and many others.

Revision history for this message
vista killer (vistakiller) wrote :

yes i use openGL screensaver

Revision history for this message
IVIisterX (doellies) wrote :

Hello vista killer!

I think there is a problem with the graphics driver, which is additional to the powernowd trigger responsible for the freezes.

In the german forum - post http://forum.ubuntuusers.de/topic/88548/195/ - a user reports that the newest nvidia drivers were responsible for his freezes. Only a downgrade from version "NVIDIA-Linux-x86_64-100.14.11-pkg2.run" to "NVIDIA-Linux-x86_64-100.14.09-pkg2.run" did succeed; his machine doesn't freeze anymore.
Perhaps this a possibility to solve your problem.

Best regards

IVIr.X

Revision history for this message
vista killer (vistakiller) wrote :

Thanks MisterX.The strange is that the same problem affects and ati users

Revision history for this message
semijoyful (semijoyful) wrote :

Hi, all!
I am a new Ubuntu (Feisty Fawn) user. Here's information about my system off the top of my head:
Dual boot PC (XP, Ubuntu)
Pentium 4 HT 3.2GHz
Elite Xpress Motherboard w/on board express ATI
Express AGP Nvidia Ge-Force
I believe the kernel is the newest one.

Right out of the gate, my computer has been experiencing hard freezes. The first time that I got one was when I was just accessing restricted drivers. This is not the only time, however. I can expereince these random freezes at any point that Ubuntu is running. I want to make this work, but if the OS causes me to re-boot my whole system before I can even finish a task, I am not sure my willingness will last long. I am new at this, and I'm curious if one can get me on the right track to solving this problem.
Greatly appreciative in advanced,

semijoyful

Revision history for this message
bootsbradford (mark-bradford1) wrote :

I am experiencing exactly the same thing as described here. These are my basic specs:

Dell Dimension 8400
Intel(R) Pentium(R) 4 CPU 3.40GHz
RADEON X600/X550 Series
Ubuntu Feisty (Studio)/XP Dual Boot
Ubuntu Kernel 2.6.20-16-low latency (though crashed with all others on Feisty as well)

The tell-tale signs are a complete look-up, with the exception of the mouse still being moveable and music (e.g. from Amarok) still playing.

Revision history for this message
likemindead (likemindead) wrote :

I'm getting freezes every time I boot. I've attached my /var/log/messages if that'll help any. I'm at my wits end. My old HP desktop, which I'm on right now, is running Feisty without any hitches. But my 2 years newer Acer laptop is nothing but trouble. Any help would be greatly appreciated. I don't want to have to go back to M$ XP on my laptop. :-(

Revision history for this message
semijoyful (semijoyful) wrote : Re: [Bug 131973] Re: desktop random freezes in feisty

I lay out my cards right now. I am not too savvy of a linux user, but I
like the spirit of it. Here's something that helped me out. I am hoping
that this isn't something that you have tried yet.
http://ubuntuforums.org/showthread.php?t=412125&highlight=feisty+fawn+freezes&page=61

FYI, here's my current stats on my setup:

Tripple boot sys:

Ubuntu Studio -using kernel 2.6.20-15-generic
Fedora 7
XP

Pentium 4 HT @3.2GHz
1G of DDR RAM

Video: E-VGA AGP Nvidia Ge-Force 4000
Audio: E-MU 0404 PCI (no drivers available by manuf. or Alsa)

Good luck! semijoyful

On 9/2/07, likemindead <email address hidden> wrote:
>
> I'm getting freezes every time I boot. I've attached my
> /var/log/messages if that'll help any. I'm at my wits end. My old HP
> desktop, which I'm on right now, is running Feisty without any hitches.
> But my 2 years newer Acer laptop is nothing but trouble. Any help would
> be greatly appreciated. I don't want to have to go back to M$ XP on my
> laptop. :-(
>
>
> ** Attachment added: "messages"
> http://launchpadlibrarian.net/9094803/messages
>
> --
> desktop random freezes in feisty
> https://bugs.launchpad.net/bugs/131973
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
"We are skylights to all we know and who know of us." -KRY

Revision history for this message
IVIisterX (doellies) wrote :

Hello altogether!

I made the kernel update to version 16.31 and updated the Ati-driver by Envy to version 8.40.4; since this time my system runs pretty stable.
But after 10 days without any freezes by multiple starts every day i had two freezes at friday evening. The first 8 minutes after start; the second 9 minutes after reset. Since another reset my system is working without any additional freezes up to the moment.
I guess furthermore, that there are some periodical processes which are responsible for the freezes. Is there perhaps anything else like the periodical harddisc checking? Does anyone else know something about periodical actions?

IVIr.X

Revision history for this message
semijoyful (semijoyful) wrote :

Just to fill you in, I have been able to maintain a pretty stable system.
Since my last post on Ubuntu Forums thread concerning the Feisty Fawn
Freezes. When I mean stable, I mean that my system goes long spans without
freezing. I notice that the freezing is almost certain if I have desktop
effects enabled. The other time that I experience it is during several
Firefox sessions being open at a time. I have a feeling things will
continue to improve with Gutsy. FYI, I also have been testing Fedora 7 on
the same system with random freezing as well.
Sincerely,

semijoyful

On 9/16/07, IVIisterX <email address hidden> wrote:
>
>
> Hello altogether!
>
> I made the kernel update to version 16.31 and updated the Ati-driver by
> Envy to version 8.40.4; since this time my system runs pretty stable.
> But after 10 days without any freezes by multiple starts every day i had
> two freezes at friday evening. The first 8 minutes after start; the second 9
> minutes after reset. Since another reset my system is working without any
> additional freezes up to the moment.
> I guess furthermore, that there are some periodical processes which are
> responsible for the freezes. Is there perhaps anything else like the
> periodical harddisc checking? Does anyone else know something about
> periodical actions?
>
> IVIr.X
>
> --
> desktop random freezes in feisty
> https://bugs.launchpad.net/bugs/131973
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
"We are skylights to all we know and who know of us." -KRY

Revision history for this message
IVIisterX (doellies) wrote :

Hi, everyone!

Because my machine has no freezes with kernel 2.6.20-16.32-386 and MESA with indirect rendering, I made the following interesting test:

On the page [url]http://www.unixboard.de/vb3/showthread.php?t=33850[/url] I found an instructions manual to get direct rendering with MESA. After configuring and restarting my system I had really direct rendering with MESA. But both kernels 2.6.20-16.32-generic and 2.6.20-16.32-386 freeze a few minutes after restart and using firefox. So I had to reinstall the ATI driver 8.40.4 with envy.

In this context I have a question:

If I change the AGPmode in the xorg.conf file to "4", the ATI Catalyst Control Center shows an 8x AGPmode under kernel 2.6.20-16.32-generic and an 0x AGPmode under kernel 2.6.20-16.32-386. Why does the driver overwrite the xorg.conf settings and where is perhaps a possibility to change this setting?

Thanks and Greetz

IVIr.X

Revision history for this message
Erik (erik-erikwickstrom) wrote :

I'm still having these problems after upgrading to Gutsy.

I have a Pentium D 830 with an ATI radeon X600 (RV380). I was using the open source radeon DRI drivers with aiglx to run compiz-fusion. Yesterday I decided to try switching back to the restricted ATI driver and xgl. Haven't had a crash since. So the radeon driver or aiglx might be part of the puzzle.

Revision history for this message
NinjaKirk (ninjakirk) wrote :

You may be onto something there. I have not had any crashes in Gutsy since
I initiated the restricted drivers. Interestingly enough, I was using
restricted drivers with 7.04, and that was still giving me freeze issues.
It wasn't until I made changes suggested by |V|isterX in the Ubuntu forums
that I was able to stabilize my system. I am sure you have looked there
already, but that string can be found by searching "Feisty Fawn Freezes."
It appears as though some of these issues have been worked on in Ubuntu
latest 7.10. Good luck to everything...hope the restricted drivers work
well for you.
Sincerely,

NinjaKirk (formerly semijoyful)

On 10/19/07, Erik <email address hidden> wrote:
>
> I'm still having these problems after upgrading to Gutsy.
>
> I have a Pentium D 830 with an ATI radeon X600 (RV380). I was using the
> open source radeon DRI drivers with aiglx to run compiz-fusion.
> Yesterday I decided to try switching back to the restricted ATI driver
> and xgl. Haven't had a crash since. So the radeon driver or aiglx
> might be part of the puzzle.
>
> --
> desktop random freezes in feisty
> https://bugs.launchpad.net/bugs/131973
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
"We are skylights to all we know and who know of us." -KRY

Revision history for this message
Martijn (martijn-kessels) wrote :

Random freezes here too using a Toshiba Satellite A200 with onboard Intel graphics card, running up to date Gutsy Gibbon, Compiz and AWM. I can reproduce the freeze by selecting text in a webbrowser (tested with Firefox, Konqueror and Epiphany) and dragging text to the desktop. Mouse still works, sound keeps on playing, no response at all to keyboard input. Pretty much like bootsbradford reports.

Revision history for this message
Martijn (martijn-kessels) wrote :

Should have checked this first: With Compiz disabled I can not reproduce this freeze. I will move this issue to where it belongs: Compiz.

Revision history for this message
Mike Gerwitz (mikegerwitz) wrote :

I do not believe this problem is caused by compiz. I experienced random lockups both with compiz enabled and disabled. I have an nVidia graphics card and use the restricted drivers. No specific action causes the freeze - it's happened while I was in the middle of typing, while the computer was left idle (I originally thought that was the problem), while no programs at all were running, etc. This occurred in Gnome, using Gutsy. I have not tried any other window managers.

Revision history for this message
Mike Gerwitz (mikegerwitz) wrote :

Excuse me, I posted specs for the wrong computer ;) This occurs on my Toshiba Satellite A10-S169, which uses an onboard Intel graphics card. The computer using Gutsy with the nvidia drivers runs very smoothly with no freezing.

Revision history for this message
Mike Gerwitz (mikegerwitz) wrote :

Update: I left my laptop idle at the login screen (GDM) and, sure enough, it froze. Therefore no window manager is a problem. I did not experience this problem with previous versions of Ubuntu.

Przemek K. (azrael)
Changed in ubuntu:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.